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

Hi,

I'm hoping you can help me out with my IRU C112G. 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.

@Dennis

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 IRU C112G 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://xdaforums.com/t/huawei-p9-lite-unable-to-mount-vendor.3704543/
Take a look at comment #587
Also, this : https://www.ifixit.com/Answers/View/90206/How+can+I+fix+my+PS3+controller.
You can also check this video starting from minute 3:

The IRU C112G 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 IRU C112G 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 IRU C112G 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 IRU C112G 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://xdaforums.com/t/i-cant-flash-anything-need-help.4664275/

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

Damaging Other Flex Cables: The interior of a smartphone is packed with delicate flex cables. Cheap aftermarket parts can have poor fitment or be made of inferior materials. Description: Qualcomm Flash Image Loader (QFIL) is part of the Qualcomm Product Support Tools (QPST) suite. Reference Materials: Compare the internal layout of your phone with high-resolution images or repair guides for your specific model. Battery Degradation: A severely degraded battery struggling to provide stable power can sometimes cause display issues, including flickering, especially under load or at lower charge percentages. RAM (Random Access Memory): Usually situated in a package-on-package (PoP) configuration directly on top of or next to the SoC, RAM is volatile memory used for active data and running applications. Isopropyl alcohol (90% or higher) and lint-free cloth: For cleaning residual adhesive. Using a magnifying glass or the zoom function on another phone's camera can help in getting a clearer, more detailed view of the mesh and its condition. This feature provides invaluable peace of mind for users, protecting their devices from accidental splashes, rain, or brief submersion. Update OS and Apps: Ensure your phone's operating system and all installed applications are up to date. This will erase all your data, apps, and settings, returning your phone to its original factory state. Beware of Swollen Batteries: If your phone's back is bulging, it might indicate a swollen battery, which is a fire hazard. Incorrect Settings: Muted volume, active audio enhancements, or accessibility features. Skill Level: These hardware repairs require significant experience with microsoldering, precise temperature control, and a thorough understanding of schematics. Before anything else, carefully inspect the entire perimeter of the mid-frame for any embedded glass shards from the old screen. Custom ROMs/Rooting Issues: Flashing an incompatible custom ROM, kernel, or recovery, or a misstep during the rooting process, is a very common cause of boot loops for enthusiasts. Isopropyl Alcohol (IPA) (>90%) and cotton swabs (for cleaning, if needed) While newer high-end devices have largely transitioned to Universal Flash Storage (UFS), the principles of flash memory degradation and failure symptoms remain relevant, and eMMC is still prevalent in a vast number of devices worldwide. If restarting only while charging: Inspect the charging port (see other topics) for damage or try a different charger/cable. CPUs can safely operate up to ~70-80°C under load, but sustained temperatures above this can be problematic. A camera attached to the trinocular port allows you to capture high-resolution images or video of defects or repair progress. Disconnect Battery First: ALWAYS disconnect the battery FPC connector before attempting to disconnect or connect any other component. If a factory reset through recovery mode doesn't resolve the issue, or if you can't even access recovery mode, flashing the phone's stock firmware (the original operating system provided by the manufacturer) can sometimes help. EMI Shielding: Electronic components, especially high-frequency ones (Wi-Fi, Bluetooth, cellular modem, CPU), generate and are susceptible to electromagnetic interference. Apply Heat: Using a heat gun or hair dryer, gently heat the bent area of the frame. When the voltage across a Zener diode in reverse bias reaches a specific "Zener voltage," it starts conducting current to maintain that voltage across its terminals. Again, watch for flex cables often attached to the back cover (fingerprint sensor, wireless charging coil). Unlike PC BSoDs that often display error codes, smartphone equivalents might just show a solid blue screen, a boot loop ending in blue, or repeated reboots. Disconnect Battery: Locate and disconnect the battery flex cable from the logic board. A professional technician can accurately diagnose the exact point of failure and provide the most effective repair solution, whether it's a simple port replacement or a complex board-level repair.4.

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