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

Hi,

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

@Bridget

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 SKYKEY Iri 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/571600/No+clue+how+to+get+proper+values+for+the+thermistors.
Take a look at comment #819
Also, this : https://www.ifixit.com/Answers/View/485559/Trouble+with+new+battery+installment.
You can also check this video starting from minute 8:

The SKYKEY Iri 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 SKYKEY Iri 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 SKYKEY Iri 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 SKYKEY Iri 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/279060/reset+my+phone+plz

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

If basic checks don't resolve the issue, the problem likely lies with internal hardware. Destruction During Opening: To open a water-resistant phone, heat is applied to soften the adhesive, and then prying tools are used to cut or separate the gasket. Physical Protection: Offers some minimal physical protection to the delicate ICs underneath. The proliferation of counterfeit smartphone components stems from several factors: Random application crashes are a common and frustrating issue that can plague any smartphone user, regardless of brand or operating system. The physical volume buttons on your smartphone are crucial for adjusting media playback, ringtone volume, and in some cases, even serving as a camera shutter button or a quick-launch shortcut. An error caused by a faulty barometric pressure sensor can lead to a range of perplexing issues that might not immediately point to this specific component, requiring systematic and advanced diagnostic techniques. Carefully slide the pick around the perimeter of the phone, gradually separating the adhesive. This includes laptops, smart TVs, smart speakers, other phones, and any Bluetooth accessories. Depending on your phone model, you will either heat and remove the display assembly or the back cover first. Gently clean the headphone jack (if present) with a wooden toothpick or compressed air to remove lint or debris that might be triggering the sensor. If the phone has recently been exposed to humidity or a minor splash, check for condensation inside the camera lens (front or rear) or under the display. Use a specialized screen press or multiple small, even clamps around the entire perimeter of the device. Result: By keeping the image stable on the sensor, OIS allows for longer exposure times without motion blur, significantly improving photo quality in low-light conditions and producing sharper images in general. Power and Volume Button Flex Cables: To prevent movement and ensure consistent button actuation. Another issue can be trapped dust, which necessitates repeating the cleaning steps. This can indicate frame damage that would prevent a new display from sitting flush. Loose Components: Parts like cameras, speakers, or internal brackets can become loose, leading to rattling noises or poor performance. For a smartphone repair technician, troubleshooting this problem requires a systematic approach, moving from simple software fixes to more complex hardware diagnostics, ultimately identifying the root cause and restoring functionality. The most direct indicators are error messages such as "SD card not detected," "SD card corrupted," "unformatted SD card," or "SD card unreadable." Beyond explicit error messages, users might notice files or entire folders missing, photos and videos appearing as grey boxes or displaying error codes, or apps installed on the SD card failing to launch or crashing frequently. Position it centrally, at a comfortable height for prolonged viewing, with sufficient clearance for your hands to work underneath. The "Zero Insertion Force" refers to the initial insertion of the flat flexible cable before the locking mechanism is engaged. For example, `adb logcat | grep -E "crash|fatal|error|warn|WifiManager"` Rule out a bad battery: While less likely to affect only wireless charging, a severely degraded battery can sometimes cause charging issues. Create a Gap: Apply a suction cup near the bottom of the screen (or back). Super Glue (CA glue) / Epoxy: For bonding to the screwdriver (extreme caution needed). French Repairability Index (Indice de Réparabilité): Mandated by French law since 2021, this index uses a 10-point scale based on five criteria: If software and environmental factors are ruled out, a hardware problem is likely. New damage to internal components: If a function isn't working (e.g., wireless charging), you may have damaged a flex cable or connector during disassembly/reassembly. Restart the Device: A simple reboot can often clear temporary software glitches that might be interfering with button input.

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