[SOLVED] I'm looking for ICELL I555 repair guide or schematics (free) - Phones & Tablets Forum

Hi,

I'm hoping you can help me out with my ICELL I555. It's started acting up, and I'm looking for a detailed service manual with boardviews and schematics to properly diagnose and repair it. I need to take precise voltage measurements around the board, so having the right documentation would be very helpful.

Thanks in advance for your help.

Selected Answer

I actually found that service manual on a tech Discord server a while back. A really helpful member there shared a direct link to their blog and I've saved it. I'm happy to pass it along here. Hopefully, these boardviews and schematics help you fix your phone, just like they got me through my repair. Looks like we have the same model.

@Hala

Absolute legend! That's exactly the info I was searching for. This is going to save me so much time probing in the dark. Seriously, thanks a ton for sharing the link!

Hi there,

I also have the ICELL I555 and just downloaded the manual you shared. I'm pretty new to board-level phone repair, and this is a bit intimidating with all the tiny test points and the schematics. Could you point me in the right direction on how to start troubleshooting this ? Any advice on the first few things I should check would be a massive help.

Thanks so much for your time

General advices: start by checking the voltage at the battery connector on the board. With a known-good battery connected, you should see a steady voltage between 3.7V and 4.2V. After that, a great next step is to check the main power management IC (PMIC) for shorts. Using your multimeter in diode mode, check for shorts on the large input capacitors surrounding the PMIC.

Here are a few useful references for troubleshooting your device:
https://www.ifixit.com/Answers/View/665285/Randomly+shuts+down+and+randomly+starts+again.+A+1466
Take a look at comment #394
Also, this : https://xdaforums.com/t/q-bell-galaxy-s4-stock-rom.2417944/.
You can also check this video starting from minute 5:

The ICELL I555 service manual and boardviews from the link above were exactly what I've been searching for. I couldn't find a complete, free copy anywhere else. Seriously, thank you for sharing this you're a lifesaver!

Hi everyone, I'm working on a ICELL I555 with a no power issue and need some guidance with my measurements.
I'm detecting 3.3V on the VREG_MAIN line (pin 1 of the PMIC), which looks good, but I'm getting 0V on the VDD_CPU line (pin 8) where the schematics indicate I should see about 0.9V.
Since this is a core voltage for the application processor, could this missing rail be why the device shows no signs of life?
What's the best procedure to diagnose this further? Should I check for shorts on the CPU rail first, or look at the PMIC's enable signals?
I've already verified the main 3.3V and 1.8V power rails are present and stable.

My ICELL I555 was working perfectly until yesterday when it suddenly went completely dead. Now it won't respond to the power button, doesn't vibrate, and shows no signs of life even when connected to a charger. I'm worried there might be a serious issue.

I have a decent multimeter, a basic soldering iron, and a healthy dose of patience. While I've successfully replaced iPhone batteries and charging ports, this will be my first attempt at actual diagnosis. The sheer density of BGA chips and microscopic components is honestly a bit overwhelming.

I'm particularly curious about the alcohol trick I've seen online where you apply isopropyl to the board and look for evaporation hotspots to locate shorts. Is this actually a reliable method for beginners, or are there better approaches I should try first with just a multimeter?

I learned this lesson the hard way last month with mine, it was declared "dead" by two different shops. The phone showed absolutely no signs of life - no charging indicator, no vibration, nothing. Before diving into complex board work, I decided to try one more basic test: wireless charging.

To my complete surprise, it actually heated up on the charging pad! This single discovery completely changed my diagnostic path. It turned out the issue wasn't with the main board or processor, but with the notoriously fragile USB-C port that had failed completely. A $15 replacement part and some careful soldering brought it back to life.

The moral? Always exhaust every external testing method before opening the device. Test wireless charging if available, try different charging methods, and don't assume the worst case scenario. Sometimes the most "dead" devices have the simplest solutions hiding in plain sight.

I suspect my issue might be related to that cheap, third-party fast charger I used at the airport last week... Now the device gets extremely hot during charging, the screen flickers at low brightness, and sometimes it randomly shuts down at 30% battery. Could this have damaged the power management IC or battery calibration?

If your ICELL I555 starts acting up, random reboots, fast battery drain, or connectivity issues, there are several diagnostic steps you can take before assuming the worst:

• Check your charging habits: Using poor-quality chargers or wireless pads can gradually damage your battery and charging circuit, leading to unpredictable behavior.
• Inspect the physical components: A slightly damaged charging port, worn battery, or even accumulated pocket lint can cause issues that seem like major hardware failures.
• Monitor temperature patterns: If your phone gets unusually hot during specific tasks (like camera use or gaming), it could point to a failing component rather than a software issue.
• Use diagnostic tools wisely: Ampere for battery health, phone diagnostic codes (*#0*# on many models), and a thermal camera can reveal problems without opening the device.
• Know when to stop: If you see liquid damage indicators tripped or smell burnt electronics, it's time to consult a professional before causing irreversible damage.

Also visit this link it may help : https://www.ifixit.com/Answers/View/772289/My+replacement+battery+is+filled+with+gas+advice

Here's what I discovered on forums and technical databases:

They are linked to thyroid disruption, developmental problems, and neurological damage. Dust Contamination: Neglecting to thoroughly clean the lens area before applying the new ring will result in dust spots in photos. ESD Protection: Smartphones are highly susceptible to electrostatic discharge. UV Illumination: When UV light (often referred to as "black light") is shone on the motherboard in a darkened environment, the fluorescent dye trapped within the micro-cracks absorbs the UV energy and then re-emits it as visible light, causing the cracks to glow brightly. By systematically working through these troubleshooting steps, you can diagnose and resolve most smartphone Bluetooth issues, restoring your device's full wireless capabilities and reconnecting you to your favorite accessories.How to examine smartphone microphone clarity problems Prioritizing safety throughout the smartphone repair process protects you from injury and your device from further harm. When a smartphone's wireless charging pad becomes damaged, it renders this functionality useless, often without affecting the traditional wired charging. In conclusion, mastering the use of a benchtop power supply for advanced smartphone boot diagnostics is a fundamental skill for serious technicians. Apply a tiny dot of UV solder mask over the jumper wire connection to the pin and cure it. Microphone installed incorrectly (e.g., wrong orientation, mic hole blocked by the component itself). Understanding their function and proper replacement is essential for comprehensive smartphone repair and maintenance. Internal Connections: If comfortable opening the phone (refer to a repair guide), carefully check the digitizer's flex cable connection to the logic board. A new replacement headphone jack module (often part of a flex cable assembly): Ensure it's compatible with your specific phone model. Even Heating: Heat the entire shield evenly, moving the nozzle in small circles. Third-party Repair Tools: Some advanced third-party tools can read component IDs and verify basic compatibility, but they are not as comprehensive as OEM tools. Be extremely careful not to bend the board or damage surrounding components. Creaking or Clicking Sounds: As you gently press or twist the phone (within safe limits, without excessive force), listen for any unusual creaking, clicking, or popping sounds. Tape the Broken Screen (If Still Attached): If the screen is still partially attached and significantly cracked, apply wide strips of clear packing tape across its entire surface. Heat Management: Work quickly and efficiently to avoid overheating the PCB, which can lift other pads or damage adjacent components. Test in Safe Mode (Android): Booting into safe mode temporarily disables third-party applications. Remove screen protector/case: Temporarily remove any screen protectors or cases that might be obstructing or interfering with the touchscreen. By systematically troubleshooting and carefully replacing the combined sensor flex cable, you can restore essential functionalities like automatic brightness adjustment and proper screen behavior during calls. If the heat is unevenly applied, some balls might melt while others remain solid, making the component difficult to remove and increasing the risk of lifting pads from the board. Poorly Seated Components: Air gaps created by misaligned components or poor reassembly hinder heat transfer. Disconnect Flex Cable: Locate the flex cable connecting the Qi coil to the logic board or sub-board. If the phone's CPU (which holds the decryption keys) is dead, the data is essentially locked forever, even if the eMMC/UFS chip is perfectly readable. You might need to remove the mid-frame or specific modules to access them. If cleaning attempts fail and there's a high risk of damage with further attempts. It might be integrated with the front camera or earpiece speaker on a single flex. Discoloration: The mesh might appear darker or discolored in blocked areas.

@Shawn, Not sure what you're trying to say but ok :)