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

Hi,

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

@Noelia

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 GEEPEE 5321 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/ok-gettiready-for-custom-rom-and-thunderrom-v1-5.896965/
Take a look at comment #1553
Also, this : https://www.ifixit.com/Answers/View/885498/Somethings+have+suddenly+gone+missing+in+widgets+&+settings....
You can also check this video starting from minute 6:

The GEEPEE 5321 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 GEEPEE 5321 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 GEEPEE 5321 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 GEEPEE 5321 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/big-problem-fastboot-bootloop.2716239/

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

Aftermarket: May lack OEM branding, have generic markings, or attempt to replicate logos poorly (blurry, misaligned, incorrect fonts). Description: These are black or white adhesive strips with tabs that extend from under the battery. Keep track of screw types and locations, as they often vary in length and diameter. Heat Transfer: The metal shield acts as a heatsink, rapidly dissipating heat. Missing screws can lead to loose components or structural instability. Power Management Integrated Circuit (PMIC): The central hub for power distribution and management. Usage: Use these apps to monitor temperature during different activities: idle, light browsing, heavy gaming, video streaming, and especially during charging. Micro-soldering the Motherboard Connector (Advanced): This is the most challenging and should only be attempted if the motherboard connector itself is visibly damaged (e.g., ripped pads, broken plastic housing, badly bent pins that cannot be straightened) and you possess advanced micro-soldering skills and tools. The phone's OS keeps track of the battery's charge and discharge cycles, learning its full capacity and how quickly it drains. If multiple types are affected, it might indicate a more general internal hardware issue or very strong external environmental interference. Users might also notice that their phone frequently prompts them to "calibrate compass," indicating persistent instability. By following this comprehensive guide, you can confidently undertake this repair, bringing your phone's wireless charging capabilities back to full functionality.## 4. While that shock might be a few thousand volts, the current is low, and you barely feel it. Look for Unevenness: The seam between components should be perfectly uniform and flush. The power button circuit is faulty: The PMIC isn't receiving the power-on signal (refer to Topic 6). Use a multimeter to check for continuity between the BMS output and the battery cell, and check for shorts. Forcing will inevitably lead to broken plastic, bent metal, or torn cables. Corrosion can cause intermittent shorts or open circuits on RF components. Factory Reset (Last Resort for Software): If all software-based troubleshooting fails, a factory reset can eliminate deep-seated software corruption. This method is more applicable to LCD screens than OLEDs due to their different display technologies and the risk of damaging OLED panels with pressure. Stuck High or Stuck Low Data Lines: If a data line (SDA, MOSI, MISO) remains constantly high or low, it indicates a short to VCC or ground, or a problem with the driving/receiving buffer. Reconnect the battery flex cable last, just before securing the back cover. Hold it firmly for the initial set time, then allow it to fully cure for several hours (or as per epoxy instructions). Heat must be applied judiciously to soften the adhesive without damaging the battery or other internal components. Infrared Camera: This specialized camera captures the IR light reflected from the face, including the distorted dot pattern projected by the dot projector. Set your hot air station to the appropriate temperature and airflow (typically 300-350°C for lead-free solder, low-medium airflow, but always practice on donor boards first). Slowly pass the magnet over the edges of the phone's screen or frame, focusing on the area where the smart case magnet would typically sit. ESD-Safe Mat and Wrist Strap: Essential for preventing static discharge. A good stereo microscope (e.g., trinocular with a camera for documentation) with magnification up to 40x or higher is essential for clear visibility of tiny components and solder joints. Identifying smartphone module communication faults requires a methodical approach, starting with software diagnostics and progressing to detailed visual inspection and electronic testing with appropriate tools.

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