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

Hi,

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



>>>> MOVIC F5004 maintenance guide & schematics (pdf + fz)

Good luck

Discussion Starter - #3 - 1 week ago

@Asia

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 MOVIC F5004 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/q-someone-please-help-init-d-script.1542394/
Take a look at comment #381
Also, this : https://www.ifixit.com/Guide/iMac+Intel+21.5-Inch+EMC+2389+Camera+Board+Replacement/6266.
You can also check this video starting from minute 1:


The MOVIC F5004 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 MOVIC F5004 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 MOVIC F5004 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 MOVIC F5004 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/no-network-after-flashing-custom-rom.3311668/

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

It's essentially your phone's fingerprint on a mobile network, used to identify individual devices. Connect to PC: Open a command prompt/terminal in the directory where your firmware files and ADB/Fastboot tools are located. For example, `##4636##` often opens a "Testing" menu where you can access "Phone information." Here, you might find details about the modem, signal strength (dBm), network type, and options to select preferred network types. Reduced Touch Sensitivity: Laggy or unresponsive touch, "ghost touches," or areas of the screen that don't register input. In the intricate world of smartphone thermal management, thermal paste is often the star when it comes to the CPU/SoC. Makeup and Cosmetics: Foundations, powders, and lotions can clog the fine mesh of the earpiece speaker, especially for users who frequently apply makeup. The pixels responsible for displaying these static elements degrade faster than the surrounding pixels. Similarly, try the problematic SIM card in another phone to confirm its functionality. Ultrasonic Triggers: Found on some advanced gaming phones, these use ultrasonic waves to detect finger presses, offering precise and low-latency input without physical movement. Solution: Work on a heat-resistant mat (silicone, ESD-safe mat) or a workbench made of non-flammable material. Connect the programmer's adapter to the designated test points on the motherboard. Ensure all antenna connections are clean, properly aligned, and securely seated. A fully discharged battery can enter a deep discharge state, making it unable to hold a charge or even become unchargeable, while a fully charged battery under high voltage can experience accelerated aging and capacity loss. This is an advanced BGA repair, involving de-soldering, reballing, and re-soldering the baseband IC. Prioritize Carrier Contact: For "SIM card not provisioned," contacting your mobile carrier is often the quickest and most effective solution, as the issue frequently lies with activation or account status. Repeat for all lifted signal and ground pads, ensuring each jumper is properly routed and isolated. Fluctuating voltage or unusually low voltage under load can indicate a struggling battery. Wi-Fi and Bluetooth may or may not work (depending on whether they share components or power with the baseband). If a function connected by a ribbon cable isn't working after a repair (e.g., no touch, no display, camera not detected), the first and most common troubleshooting step is always to re-open the device and carefully inspect and re-seat the relevant flex cable connector. Suction Cup and Pry Tool: Use a suction cup to create a small gap, then carefully insert a thin pry tool (e.g., plastic pick, metal spudger) to separate the display or back glass from the frame. If the display flex cable is torn, the screen might show no image, display lines, have incorrect colors, or suffer from a complete loss of touch functionality. Genuine: Crisp, clear OEM branding, model numbers, safety certifications, and capacity information. Around the perimeter of the back glass or back cover, bonding it to the mid-frame or chassis. Function: Detects magnetic fields, used as a digital compass and for GPS orientation. Anti-Reflective (AR) Coatings: These microscopic layers reduce glare and internal reflections, allowing more light to pass through to the sensor, resulting in clearer, higher-contrast images. Start with a low current limit (e.g., 1A) and gradually increase if needed, watching the heat. This backs up content like images, videos, audio, documents, and even app data (for some apps) within the secure folder. Ensure they are correctly oriented according to the tray's cutouts and markings. Incorrectly seated cables are a common cause of post-repair issues (e.g., non-functional screen, charging problems). IMEI Check: Go to Settings > About Phone (or dial #06#) to check if the IMEI is present.

1 - 13 of 13 Posts

Page top