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

Hi,

I'm hoping you can help me out with my Acer Liquid mini E310. 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.



>>>> Acer Liquid mini E310 maintenance guide & schematics (pdf + fz)

Good luck

Discussion Starter - #3 - 1 week ago

@Kris

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 Acer Liquid mini E310 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/495610/Why+does+my+gameboy+pocket+only+work+when+plugged+in
Take a look at comment #641
Also, this : https://xdaforums.com/t/q-help-in-add-the-blacklight-fix-source.1700624/.
You can also check this video starting from minute 1:


The Acer Liquid mini E310 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 Acer Liquid mini E310 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 Acer Liquid mini E310 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 Acer Liquid mini E310 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/601269/Does+my+gaming+laptop+use+it's+keyboard+as+vents

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

Lifted Pad (on motherboard): The metal pad on the motherboard to which the connector pin connects becomes detached from the PCB, but the copper trace leading to it might still be intact. Corrupted File System: The file system on the `/system` partition (often EXT4) can become corrupted due to improper shutdowns, failed flashing attempts, or software bugs. Connector Seating: Ensure the cable's connector is fully and evenly seated in its ZIF (Zero Insertion Force) or other socket on the logic board or sub-board. While focusing heat on the SoC, nearby sensitive components are also at risk. Hold the phone as steadily as possible (or use a mini tripod for absolute stillness as a baseline). Installing ZIP Files: Flashing mods, root packages (like Magisk), custom themes, or other system-level modifications packaged as ZIP files. Safe Mode: While not directly for updates, booting into Safe Mode after a failed update can sometimes provide temporary access to settings to troubleshoot, though often the phone won't even reach Safe Mode if the OS is significantly corrupted. Clean with Soldering Iron and Braid: Using a fine-tip soldering iron and desoldering braid, carefully clean all the pads on the motherboard. If a phone is stuck in a boot loop due to a corrupted OS, reinstalling firmware is often the only solution. The components and pads are often measured in fractions of a millimeter. If the microphone works perfectly in Safe Mode, you can then incrementally uninstall recently installed applications until the problem is resolved, pinpointing the specific app causing the conflict. If software troubleshooting and external component checks fail, persistent inaccuracies often point to a degrading battery that requires replacement. Reading Schematics: Board-level repair heavily relies on schematic diagrams and boardview software. For iOS devices, while this method of hard reset isn't typically used to wipe data (iOS resets are done via settings or iTunes), if you ever encountered a device needing a DFU restore for severe issues, data loss would also occur. Also, test general device functionality to ensure no components were accidentally damaged or left disconnected. Patience, practice, and the right tools are key to mastering this technique. Before fully sealing the phone, temporarily connect the screen and battery to the logic board. If the flickering temporarily stops or changes when you apply pressure, it could indicate a loose display flex cable or an issue with the screen's connection to the logic board. This methodical tracing, guided by the schematic, allows you to pinpoint precisely where the fault lies, be it a shorted capacitor, a damaged IC, or a broken trace. Caution: Restoring a damaged EFS backup can further complicate issues. Tinning: Tin a chisel or blade soldering iron tip with a small amount of solder. Try wiggling them or gently cleaning around them with a soft brush (or a small amount of isopropyl alcohol on a cotton swab) to dislodge any debris that might be causing them to stick. Pre-Reassembly Test (Optional but Recommended): At this point, you can temporarily reconnect the battery and display flex cables (without fully seating the display) and power on the phone to test if the new Taptic Engine is functioning correctly. Then, in `Settings > System > Developer Options`, enable "USB Debugging" and "OEM Unlocking" (if you plan to unlock the bootloader). Keep liquids away: Do not spray or pour any liquid directly into the charging port. If you're in an area with poor signal, consider putting the phone in Airplane Mode with Wi-Fi enabled, or simply toggling off mobile data when on Wi-Fi. Reinstall Front Camera (if removed): If the front camera was removed, carefully place it back into position and reconnect its flex cable. Removing damaged integrated circuits (ICs) from a smartphone motherboard is a delicate and critical procedure in micro-soldering, requiring precision, specialized tools, and a thorough understanding of thermal dynamics. ISP (In-System Programming) Adapters: These allow reading/writing to chips without physically removing them from the board, by connecting to specific test points (ISP points) on the motherboard. Blocked Vents/Impeded Airflow: Though phones don't have active fans, thick cases can trap heat, and blocked grilles (if any) can prevent passive heat dissipation.

1 - 13 of 13 Posts

Page top