Forum Phones & Tablets Repair
Discussion Starter - #1 - 1 week ago

Hi,

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


forum selected answer
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.



>>>> MANGO K20 maintenance guide & schematics (pdf + fz)

Good luck

Discussion Starter - #3 - 1 week ago

@Guido

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 MANGO K20 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/781520/Whirlpool+Wric+3c26+Error+Code+10+-+2+-+flashing+light+++number+3
Take a look at comment #1704
Also, this : https://xdaforums.com/t/is-my-battery-dying.4607647/.
You can also check this video starting from minute 4:


The MANGO K20 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 MANGO K20 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.



emoji scratching head

My MANGO K20 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 MANGO K20 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/q-droid-2-milestone-2-or-droid-1-milestone.763918/

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

Improper Cable Insertion: Forcing the cable in the wrong way or at an angle. An alternating current flows through the transmitting coil in the charging pad, creating an oscillating magnetic field. For more advanced diagnosis, especially on Android devices, system logs (Logcat) can be invaluable. You may need to remove a small metal shield or some screws to access it. Damage to Display: Removing the old polarizer without damaging the underlying LCD/OLED panel is exceptionally difficult. Slow Movements: Minimize rapid movements, as they can generate static electricity. This typically involves prying up a ZIF (Zero Insertion Force) connector or a snap-on connector. To prevent electromagnetic interference (EMI) and radio frequency interference (RFI) between these components, and to shield them from external interference, metal "shielding cans" are meticulously soldered over critical areas of the PCB. Check for flickering, dead pixels, touch functionality, and ensure all transferred components (cameras, sensors) work. Crucially, these specks do not disappear when you clean the external surface of the screen, nor do they move when you scroll content on the display; their position is fixed relative to the screen's physical dimensions. If you see visible moisture or condensation under the display glass, especially near the edges or in pockets, it confirms water ingress. Possible Causes: PMIC attempting to boot, but failing to get a response from a critical component (CPU, NAND), or a secondary power rail momentarily shorting. Phone OS: Go to Settings > System > System update (or Software update). Heat Control: Overheating can damage the IC, adjacent components, or delaminate the PCB. Manufacturing Defect: Less common, but sometimes a chip can be faulty from the factory. Attempting such a repair without proper training can easily cause further, irreparable damage to your device. Location: Which specific LCIs are tripped? One in the SIM slot only? Or multiple on the motherboard and flex cables? The more internal and numerous the tripped LCIs, the higher the confidence in significant water damage. Other Motherboard Components: While less common for boot loops, issues with RAM, CPU, or other critical components can also manifest as boot failures. The presence of such debris is a definitive sign that the seal has been compromised, allowing foreign particles to enter the device. No Power At All: After trying all charging and force restart methods, the device remains completely unresponsive. Apply new adhesive strips (recommended for a secure seal and to restore some water resistance). With precise diagnosis, appropriate tools, and meticulous micro-soldering, technicians can successfully restore a device's auditory functions, significantly extending its lifespan. It demands an exceptionally high level of organization, patience, and meticulous attention to detail. Clean the old adhesive residue from the back cover and the phone frame. As you go, gradually peel away more of the protective liner, pressing the gasket firmly into place with your finger or a plastic tool. Factory Reset (Last Resort for Software): If all else fails on the software side, a factory reset might fix deeply embedded software issues, but back up data first. Ensure there's no obstruction or mispositioning when the screen is gently lowered into place. Most modern smartphones have non-removable batteries, but if you can safely open the phone quickly (e.g., easily removable back cover), disconnect the battery flex cable from the motherboard. Thermal Issues: In some cases, a thick layer of flux residue can act as a minor insulator, potentially trapping heat around components that need to dissipate it, although this is less common than other issues. This lamination significantly improves optical clarity, reduces reflections, enhances touch responsiveness, and adds structural integrity to the display unit.

1 - 13 of 13 Posts

Page top