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

Hi,

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

@Dee

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 Alcatel OT-C652 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-please-help-me.2121765/
Take a look at comment #884
Also, this : https://www.ifixit.com/Answers/View/7522/Change+Logic+Board+500MHz+to+Logic+Board+900MHz.
You can also check this video starting from minute 7:

The Alcatel OT-C652 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 Alcatel OT-C652 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 Alcatel OT-C652 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 Alcatel OT-C652 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/camera-prob-xu.2285449/

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

Magnifying Lamp/Microscope (optional but helpful): For close inspection of connectors and fine details. However, be aware this will likely trigger FRP/iCloud locks if not already removed. While the act of soldering itself is widely understood, a crucial, yet frequently overlooked, step is the meticulous cleaning of flux residue after the solder joint is made. Ensure the surface is perfectly clean and dry for optimal adhesion of the new flex cable. Sometimes, these changes are not perfectly optimized for all hardware variations, leading to inefficiencies. Smartphone micro-repair, particularly logic board component-level repair, is an art form that demands extreme precision, steady hands, and crucially, the right tools. For users, the key is to isolate the problem to the sensor itself, while hardware repair beyond external inspection is typically best entrusted to qualified professionals.8. Modern flagship smartphones integrate a combination of passive cooling solutions: With the right technique and careful handling, it's a very achievable fix that can restore full functionality to a smartphone.6. In more severe cases, the phone might not acknowledge the charger at all, or it might only charge when held at a very specific, awkward angle. Once you have located the battery connector, perform a thorough visual inspection using your magnifying aid. A misaligned front camera can lead to a host of issues, ranging from degraded photo quality to complete malfunction of associated sensors. Charging Port Flex: The flex cable containing the charging port, microphone, and sometimes headphone jack may have a serial number. If your phone's internal storage is almost full, the system works harder to manage data, which can generate heat. While some issues might point to complex internal damage, many common audio problems can be diagnosed and fixed with basic troubleshooting steps. Precision Screwdriver Set and Plastic Pry Tools: For phone disassembly. Computer not recognizing the device: If the charging IC also handles USB data lines, its failure can prevent the phone from being recognized by a computer. Be aware of the location of flex cables, especially along the side where the display usually opens like a book (often the right side for iPhones or bottom for Androids). Diagnosis: If no continuity, the flex cable has a broken trace, and the entire flex cable needs replacement. ERM motors are relatively inexpensive and robust but tend to be bulkier, less precise in their haptic feedback, and slower to start and stop. Ensure the adapter is compatible with your phone's fast charging capabilities if applicable. Visual Inspection: Once you have access to the area, visually inspect the existing LED flash module. Use these to monitor ALS readings under different lighting conditions. Flex Cable Replacement: In most cases of damage (tears, severely corroded switches, open/shorted switches), the entire button flex cable needs to be replaced. Feedback Loop: This precise angular velocity data is fed instantly to a dedicated OIS controller. This process is model-specific and requires downloading the correct firmware, drivers, and a flashing tool (e.g., Odin for Samsung, MiFlash for Xiaomi). Visual Inspection: Examine the entire charging port flex cable for any signs of damage: tears, creases, corrosion (especially if liquid damage is suspected), or loose connections at the motherboard end. Physical Impacts: Drops, bumps, or bending can deform the frame, crack glass, or loosen adhesive seals, even if superficially the phone looks fine. It's important to clarify the terminology: "water-resistant" typically means the device can withstand splashes or light rain, while "waterproof" implies it can be submerged to a certain depth for a specific duration. By carefully diagnosing the problem, using the correct replacement part, and meticulously following these steps, you can restore your smartphone's essential charging and data transfer capabilities, extending its lifespan and utility.

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