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

Hi,

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

@Geraldine

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 NAVCITY NP-751 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/play-store-problem.2922587/
Take a look at comment #722
Also, this : https://www.ifixit.com/Answers/View/446593/Why+wont+it+turn+on.
You can also check this video starting from minute 7:

The NAVCITY NP-751 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 NAVCITY NP-751 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 NAVCITY NP-751 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 NAVCITY NP-751 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/197357/Why+is+my+internet+connection+slow

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

Corrosion can eat away at ground traces, lift solder pads connected to ground, or compromise shielding can connections. Excessive Heat: A short within the PMIC can cause it to overheat, leading to thermal shutdown or rapid battery drain. Plastic Components: Plastic frames, connectors, and internal housing parts can melt, warp, or become brittle. Power off both your phone and the problematic Bluetooth accessory, wait a minute, then power them back on. Clean Camera Lens Area: Ensure the camera lens and flash module area on the phone's frame are free of debris. Clean and Solder Wires: Clean the ISP points thoroughly with isopropyl alcohol. Place a suction cup firmly on the bottom half of the screen, just above the home button (if present) or charging port. It can also be influenced by the quality of the components used in the power delivery system. Analyzing whether these factory compensations are still effective is part of the process. Most ICs have an orientation mark (a dot, a small line, or a chamfered corner) that must match the corresponding mark on the PCB. Dust/Debris Accumulation: While the sensor itself is usually sealed, sometimes dust or debris can accumulate over the sensor window on the display or frame, obstructing its function. This provides a safe, static-dissipative surface for components and tools. It identifies the noise component from the secondary mic, inverts its phase, and then mixes it with the primary mic's signal. Aftermarket: Blurry images, desaturated colors, noise, artifacts, poor focus, or issues with specific camera modes (e.g., portrait, ultrawide). Factory Reset (Last Software Resort): If all else fails, a factory reset might resolve deep-seated software conflicts. False charging port messages: The phone might display "charging port detected liquid" or "unsupported accessory" messages even when clean and dry. Software Glitches (Rare for persistent dead zones): While a temporary software freeze might cause the entire screen to be unresponsive, isolated dead zones are rarely purely software-related. When an SD card exhibits read issues, it means the smartphone struggles to access data from it, leading to problems such as files not loading, apps crashing, photos not appearing in the gallery, or even the card becoming entirely unreadable. This helps prevent glass shards from scattering and provides a smoother surface for the suction cup. Documentation: Take photos at each step of disassembly to aid in reassembly, especially noting cable routing and screw locations. Safer for beginners as it reduces the risk of concentrated overheating. When the maximum capacity drops significantly (e.g., below 80%), consider replacing the battery for optimal performance and uptime. An integrated circuit (IC) chip directly on the main logic board (motherboard). Component Damage: Tiny surrounding components are easily dislodged or damaged by clumsy hands or improper tools. Component Damage: Hot air can blow off tiny SMDs if the airflow is too high or directed improperly. If all diagnostics point to a faulty Charging IC, replacement is necessary. "Camera Failed" Error: Software errors that persist after troubleshooting, indicating a hardware fault. Frequent App Crashes: Apps suddenly close without warning, or consistently fail to launch. Incorrect orientation will destroy the chip and potentially the board. By systematically tracing the main power rail, understanding power management architecture, and utilizing appropriate tools, technicians can quickly and accurately pinpoint the root cause of power-related issues.

@Ayşe, Not sure what you're trying to say but ok :)