Hello there! During my holidays I accidentally slipped into a swimming pool while holding my Mi 9 Lite on my hand :crying: . The device was merged into the water for no more than 2-3 secs but seemed enough to do some damage (apparently). At first the device was in a loop booting again and again in the mi recovery mode, i gave some time to dry it and suck the water off the phone. At the end of that day i tried to turn it on but after the mi logo and the vibration the mi logo seemed to fade out and the screen turned off. I got into the mi recovery mode, did wipe all data, but still the logo died after a few seconds i tried to turn the phone off... I am trying to use fastboot and miflash in order to flash again the stock rom, but no mater what i did, the device is not recognised by the pc. I did manual install the drivers, used adb, set the device as portable device, but still im not able to connect the phone in order to proceed with the flash... Is there a way to fix it because the device seems to work and respond properly (buttons on the recovery menu, the image of the fastboot looks perfect etc..), or it is permanently damaged ?
Vassilis_ said:
Hello there! During my holidays I accidentally slipped into a swimming pool while holding my Mi 9 Lite on my hand :crying: . The device was merged into the water for no more than 2-3 secs but seemed enough to do some damage (apparently). At first the device was in a loop booting again and again in the mi recovery mode, i gave some time to dry it and suck the water off the phone. At the end of that day i tried to turn it on but after the mi logo and the vibration the mi logo seemed to fade out and the screen turned off. I got into the mi recovery mode, did wipe all data, but still the logo died after a few seconds i tried to turn the phone off... I am trying to use fastboot and miflash in order to flash again the stock rom, but no mater what i did, the device is not recognised by the pc. I did manual install the drivers, used adb, set the device as portable device, but still im not able to connect the phone in order to proceed with the flash... Is there a way to fix it because the device seems to work and respond properly (buttons on the recovery menu, the image of the fastboot looks perfect etc..), or it is permanently damaged ?
Click to expand...
Click to collapse
I don't think water damage is covered under the warranty. You could try to point a torch down the USB-C port and see if you see any obvious corrosion blocking the port. If you see some then you could use a toothbrush and some isopropyl alcohol to carefully clean out the port. If that doesn't resolve it then it is likely that the water has gone through your phone and has caused damage to components.
Related
Hello, I have Z3 Compact D5803. The back (glass cover that is bonded factory) was beginning to lift off in the middle and I put a (micro) droplet of glue. The phone was turned off and the procedure was carried out carefully and without any spill. After a few days, I decided to turn it on, however, did not see anything, tried all possible combinations, but it is not working. When I plug it into the wall charger the display lights up momentarily with the Sony logo, lit red LED and then immediately restarts. This thing is going indefinitely, I have even left it plugged for 24 hours, but it keeps boot looping. Detached rear cover to look inside, everything looks fine, not even a trace of my gluing work.
Any ideas?
vessk0 said:
Hello, I have Z3 Compact D5803. The back (glass cover that is bonded factory) was beginning to lift off in the middle and I put a (micro) droplet of glue. The phone was turned off and the procedure was carried out carefully and without any spill. After a few days, I decided to turn it on, however, did not see anything, tried all possible combinations, but it is not working. When I plug it into the wall charger the display lights up momentarily with the Sony logo, lit red LED and then immediately restarts. This thing is going indefinitely, I have even left it plugged for 24 hours, but it keeps boot looping. Detached rear cover to look inside, everything looks fine, not even a trace of my gluing work.
Any ideas?
Click to expand...
Click to collapse
Have you tried the hard reset button ?
Look under the flap where you put the sim, next to it is a tiny button hole, press this.
Didgesteve said:
Have you tried the hard reset button ?
Look under the flap where you put the sim, next to it is a tiny button hole, press this.
Click to expand...
Click to collapse
Yes, nothing happens...
I can only put it in fastboot mode (blue LED on black screen), while it's connected to the PC.
Well If fastboot works then this shouldn't really be much of a problem , simply fastboot flash any kernel with a custom recovery and flash a ROM. If that doesn't work then you might be facing a hardware issue and the best course of action would be to send it in for repair
But there is no way to correctly see it in Windows. Tried to install drivers, but it keeps stay as a "S1Boot Fastboot" device in Windows 10.
vessk0 said:
But there is no way to correctly see it in Windows. Tried to install drivers, but it keeps stay as a "S1Boot Fastboot" device in Windows 10.
Click to expand...
Click to collapse
Can you detect it via ADB? Go to adb ( found in Android SDK ), open command window there and type fastboot devices, something should come up ( Assuming you have the fastboot drivers installed ) You can also use flashtool if you don't have the SDK Installed but install drivers first
vessk0 said:
But there is no way to correctly see it in Windows. Tried to install drivers, but it keeps stay as a "S1Boot Fastboot" device in Windows 10.
Click to expand...
Click to collapse
I think your drivers have not been installed correctly. It is a bit of a hassle in Windows 10 since you need to disable driver signature verification. I successfully installed the drivers from Flashtool after doing this.
i have the same problem but....
but i cannot start recovery nor fastboot not even download mode ( i think fastboot and download mode are the same) please help me
williamzerner said:
but i cannot start recovery nor fastboot not even download mode ( i think fastboot and download mode are the same) please help me
Click to expand...
Click to collapse
Either your battery is completely dead or you have a hardware problem. What happens if you try to charge your phone?
M1chiel said:
Either your battery is completely dead or you have a hardware problem. What happens if you try to charge your phone?
Click to expand...
Click to collapse
When i try to charge my phone the phone does the same thing.... means the phone boots upto the sony logo red led glows up and the the phone restats ... this repeats forever unless battery runs out...
Today I replaced my cracked Redmi 4X screen. The replacement consisted of a screen+digitizer+frame assembly (no messing with a heat gun to detach screen+digitizer from frame). I think it went fairly well, took my time and didn't force anything.
However, when testing the screen halfway through reassembly, it was stuck on the mi logo. I decided to complete the reassembly, thinking maybe it did a hardware test and refused to boot as i hadn't reconnected all parts. No such luck, even when i use the old screen it doesn't boot .
The charging led also doesn't come on when attached to a charger or laptop usb port, which seems weird. I think the battery is about 50% but right now i can't even turn it off. It just reboots when holding the power button. It doesn't enter recovery when I hold the volume-up button. I do get a fastboot logo when booting with the volume-down button. But no response on the USB cable and the logo just stays on exactly like the mi logo in normal boot. I'm not sure but I think fastboot is supposed to show some kind of menu interface? Or is it normal to see a fastboot logo only?
I've read some other posts about Xiaomi phones using different brands of digitizers, having to clear the cache to reset it and accept a different brand, but when I detach the digitizer it doesn't boot either .
I could try a factory reset with mi flash but it requires Windows which i don't have easy access to (if it even detects the phone). Perhaps there's a way to rescue it that doesn't involve losing all data, i might as well just buy a new phone if i have to reinstall/configure everything. anyway.
Any ideas?
Edit: I was suspicious of the power/volume contacts issue, so I lifted the board and was able to flash with EDL and enter the system. I might've messed up the piece while removing it from the older case. I ordered a replacement and I'll see how it goes from there.
Edit: the issue was indeed the flex cable of the side buttons. I replaced it and now it works!
=============
Hey guys, my phone's back cover and screen got shattered recently but it seemed to be working fine. I got some parts from China and assembled it today, I think it all went ok, but now the phone's stuck in an infinite bootloop (Android One screen).
So, the phone's bootloader is locked. I can't do anything through fastboot, even though I can try to send commands. Every command just reboots the phone and returns it to the loop.
After reading a lot here, I heard that my best bet was to enter EDL mode and flash the phone with MiFlash.
I'm able to get to EDL (phone shows up as COM), but after that it all goes downhill, I get a different error for each attempt of flashing: timeout, I/O exception, writing time out, resource in use, port closed, phone disconnected, strange errors, handshake error, reset status error etc.
It begins normally, flashing a few things for half a second, then fails.
I've tried two computers, multiple USB 2 and 3 ports, two images, two versions of MiFlash, three cables.
What do you guys think? This EDL flashing should've worked, but it's keen on failing in every attempt till now.
Funny thing is, while messing with the connectors, once in a few dozen loops the phone actually boots to the system, then reboots after a few seconds!
Also, I should mention that I can't turn off it for good, even if I keep power pressed for 20 seconds or more, it's like the power button is constantly pressed. I also can enter fastboot by only holding volume down while it loops, which is unusual...
Thanks!
valp88 said:
Edit: I was suspicious of the power/volume contacts issue, so I lifted the board and was able to flash with EDL and enter the system. I might've messed up the piece while removing it from the older case. I ordered a replacement and I'll see how it goes from there.
=============
Hey guys, my phone's back cover and screen got shattered recently but it seemed to be working fine. I got some parts from China and assembled it today, I think it all went ok, but now the phone's stuck in an infinite bootloop (Android One screen).
So, the phone's bootloader is locked. I can't do anything through fastboot, even though I can try to send commands. Every command just reboots the phone and returns it to the loop.
After reading a lot here, I heard that my best bet was to enter EDL mode and flash the phone with MiFlash.
I'm able to get to EDL (phone shows up as COM), but after that it all goes downhill, I get a different error for each attempt of flashing: timeout, I/O exception, writing time out, resource in use, port closed, phone disconnected, strange errors, handshake error, reset status error etc.
It begins normally, flashing a few things for half a second, then fails.
I've tried two computers, multiple USB 2 and 3 ports, two images, two versions of MiFlash, three cables.
What do you guys think? This EDL flashing should've worked, but it's keen on failing in every attempt till now.
Funny thing is, while messing with the connectors, once in a few dozen loops the phone actually boots to the system, then reboots after a few seconds!
Also, I should mention that I can't turn off it for good, even if I keep power pressed for 20 seconds or more, it's like the power button is constantly pressed. I also can enter fastboot by only holding volume down while it loops, which is unusual...
Thanks!
Click to expand...
Click to collapse
try to flash it via testpoint
q0kHaN said:
try to flash it via testpoint
Click to expand...
Click to collapse
I managed to flash it through EDL.
However, it seems like the piece that holds flex cable and side buttons is damaged. It's like the power button is always pressed (making the phone reboot over and over) or non-functional at all.
I'll change this piece and see if works properly.
Hello,
Today I didn't notice that I need to charge my phone, so it eventually turned itself off. Later I knew I received an important SMS that I wanted to check but I didn't have the charger at hand so I tried to turn it on twice. Both times the Mi logo showed up, then the phone immediately turned off. The 3rd time I tried to turn it on, nothing happened.
When I was finally able to connect a charger, nothing happened. The screen doesn't turn on, the Mi logo or battery logo doesn't show up, the small LED doesn't react either. The charger was heating up so I knew something is happening so I left my phone there. When the charger started to cool down I knew that the charging is done, so I tried to turn on my phone again but nothing happened.
I have TWRP 3.3.1-0 and LineageOS 16.0 20200422 Nightly installed.
I have tried to press Pwr+VolUp but nothing happened.
I have tried Pwr+VolDn and FASTBOOT showed up. From here I tried to reboot by holding either Pwr or Pwr+VolUp or Pwr+VolDn.
By holding Pwr+VolUp or Pwr+VolDn the device turns off.
By holding the Pwr button, the Mi logo shows up for a split second then the phone turns off.
At this point I stayed in FASTBOOT and connected my phone to my PC and tried to use the Flasher Toolkit Nikel V3 (the tool I used when I installed TWRP and the custom ROM and whenever a LineageOS update bricked the phone) to reboot or boot into recovery, TWRP.
The phone doesn't react to any commands which is really strange, never had this issue before.
If I try fastboot boot twrp-3.3.1-0-santoni.img I get the error "unlock device to use this command." Which is really really strange because I had it unlocked before.
So currently I cannot turn on my phone, I can only reach FASTBOOT and nothing else. My main goal would be to backup data (photos etc), reviving the phone is only secondary.
I was searching the whole day on the internet and couldn't find anything that helped.
Any help is highly appreciated.
Try charging with different USB and charger.
Also you may want to remove the back panel and disconnect the battery connecter from motherboard and reconnect it after few seconds and try charging with charger.
Proceed carefully if you wish to remove back panel in order to not damage any device components to be precise the fingerprint flex cable which is glued to back panel.
This is what helped me to revive my phone but I couldn't find any trusted stock ROM sources so I installed a stock ROM from androidmtk.com and xiaomistockrom.com.
Can someone please tell me if they are safe or not? And if not, can someone please link me a Redmi 4X stock ROM I could use with the XiaoMi Flash Tool?
Also, it seems the phone cannot detect anything in the 2nd SIM slot. How can I fix it?
I have a Pixel 4a that I dropped from coffee-table height onto a wooden floor. The phone landed on an edge and broke the internal screen. The outer glass is undamaged.
Initially there were rainbow lines all over the screen, but after abandoning it for a few days, now nothing shows up on the screen at all. Charged it overnight. Nothing. It does make the device a little warm, though. Powering it on produces no signs of life.
When I took it to uBreakiFix they checked for a minute and said since it doesn't respond to charging (no vibration) and doesn't seem to "power on", it probably has a dead motherboard as well.
However, when connecting it to a Windows laptop, it is reported as "Pixel 4a(5g)" in Settings>Devices, and an "MTP device" shows up in Device Manager.
Since I did not have File-Transfer as the default option for USB, and because ADB was not enabled prior to it breaking, I am left with no real way to test this device.
I also put another SIM into the phone and tried calling it, but it goes to voicemail.
Is this phone dead and ready for recycle-grave? Or is there any hope? Help is much appreciated!
Pull it apart. May have loose connectors.
See what visible damage is there.
No visible damage doesn't mean your in the clear but it's a start. Inspect the battery for swelling, a failed Li.
If it starts responding when you use a pencil eraser to gently push and flex the mobo different ways, push on the BGA chipsets, that's clear sign of a mobo solder fracture or broken trace. You can also try this with the phone together by putting pressure on the case at various points... don't go too nuts with it though.
urover said:
However, when connecting it to a Windows laptop, it is reported as "Pixel 4a(5g)" in Settings>Devices, and an "MTP device" shows up in Device Manager.
Since I did not have File-Transfer as the default option for USB, and because ADB was not enabled prior to it breaking, I am left with no real way to test this device.
Click to expand...
Click to collapse
you can do some things booting twrp (fastboot boot twrp.img) for your pixle 4a provided your phone bootloader is unlocked (fastboot flashing unlock vol down once then power to unlock without screen is the command). i can't remember if it wipes the phone or not. adb devices should see the phone once you boot up twrp. you should also be able to access the phone like a usb drive as well. if you are trying to pull data off it. make sure you have the latest google usb drivers installed from their website https://developer.android.com/studio/run/win-usb
this should give you some sort of start. to see if it even is responsive.