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

Hi,

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

@George

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 SKYCELL QS150 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/alpha-corso-mp5000.3536707/
Take a look at comment #302
Also, this : https://www.ifixit.com/Answers/View/742235/Cable+part+broke+off,+how+to+fix.
You can also check this video starting from minute 10:

The SKYCELL QS150 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 SKYCELL QS150 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 SKYCELL QS150 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 SKYCELL QS150 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/video-review-seidio-innocase-active-x-giveaway.1043492/

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

If all software and carrier checks fail, the problem likely lies with your phone's internal hardware. If the phone experiences unexpected signal drops, random reboots, or other erratic behavior, it might indicate an issue with the shielding or an unrelated problem introduced during the repair process. If a battery is severely swollen, consider professional repair to minimize risk. Disclaimer regarding potential loss of manufacturer warranty or water resistance. Software Issues: Incorrect volume settings, "Do Not Disturb" mode, app-specific issues, OS bugs, or silent profiles. Always consult a specific teardown guide for your exact model (e.g., iFixit.com) for precise instructions. Motherboard Replacement: If the Wi-Fi module is integrated into the SoC and confirmed faulty, or if the damage to the motherboard is too extensive (e.g., lifted pads under the SoC, severe liquid damage), motherboard replacement is typically the only viable solution. Thermal Cycling: Repeated heating and cooling can cause materials to expand and contract, eventually weakening solder joints. A force restart can often resolve minor software glitches or frozen operating systems that prevent the device from booting normally. These are typically complex BGA or QFN chips, often located under metal shields (which might need careful removal). Re-securing Loose Mounts: If the original rubber/foam mount is intact but has simply come loose from its position, use a tiny, precise dab of flexible adhesive (like B7000 or E8000) to re-secure it to the phone's frame or motor housing. Adhesive Very Strong: Continue with gentle prying, using plastic tools. While not directly showing layer separation, it can pinpoint areas of high resistance (due to damaged traces) or component failure, which can be either a cause or a consequence of board stress that also led to delamination. Optional: B-7000 or T-7000 Adhesive Glue: For very stubborn spots or to supplement the pre-cut adhesive for extra security, but use sparingly and carefully. It manages system resources, handles memory, CPU, and device drivers, and facilitates communication between applications and the physical hardware. Faint outlines: Are there subtle ghosting outlines of icons, text, or shapes that were previously on the screen? If you see the Apple logo or "Connect to Computer" screen, you're not in true DFU mode. Common issues include distorted sound, no sound at all, low volume, or crackling noises. Workspace: Set up a clean, well-lit, and static-free workspace using an ESD mat and wrist strap. Without a robust ground, voltages become unstable, and signals become noisy, leading to unpredictable behavior. Follow your phone's specific disassembly guide to carefully open the device (either back cover or screen removal). Heat Gun or Hair Dryer: Use sparingly and very carefully, only to soften adhesive, NOT to heat the battery directly. Every component and phase of a smartphone's operation, from standby to full boot, has a characteristic current signature. Isopropyl alcohol is non-conductive and evaporates quickly, making it ideal for electronics cleaning. If software troubleshooting fails, the problem is likely hardware-related. Locate Display Connector: The display assembly connects to the motherboard via a flex cable, usually secured with a small metal bracket and screws. If you encounter specific iTunes/Finder error codes (e.g., 9, 4013, 4014), it can indicate a hardware issue, often related to the baseband. Preparation: Place the flex cable (or logic board if the connector is on the board) in a holder. The display or back might be under pressure from the swollen battery, so be prepared for it to pop open slightly. This information is then sent to the phone's operating system, which adjusts the screen's backlight level accordingly.

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