So I am normally using my phone scrolling through social media but it suddenly froze so I tried to hard reset it, but it goes in to a bootloop without any display on the screen. I could tell it is on a bootloop because of the repeating vibration everytime the phone boots up.
My device is Poco F3 (alioth) Running stock MIUI 12.5 bootloader unlocked and rooted with Magisk.
Things I have tried:
Long pressing power button, long pressing both power button and volume down button, long pressing power and volume up button, then long pressing all of them.
Plugging it on my PC but it doesn't even detect it. Tried inputting
Code:
adb devices
and
Code:
fastboot devices
Still doesn't work. I even made sure that my drivers are working so I tried it on my brothers Poco F3 and the PC can detect his phone through ADB commands.
Waiting for a day if it magically turns on again. Nope.
Charging it up because maybe the battery is low. Nope.
At this point my only two choices is opening up the back panel then replugging the battery so it completely turns off and hopefully boots up. But its a risky task since I don't have special tools to open up my phone, and my another choice is just bring it on a service center.
rururi said:
So I am normally using my phone scrolling through social media but it suddenly froze so I tried to hard reset it, but it goes in to a bootloop without any display on the screen. I could tell it is on a bootloop because of the repeating vibration everytime the phone boots up.
My device is Poco F3 (alioth) Running stock MIUI 12.5 bootloader unlocked and rooted with Magisk.
Things I have tried:
Long pressing power button, long pressing both power button and volume down button, long pressing power and volume up button, then long pressing all of them.
Plugging it on my PC but it doesn't even detect it. Tried inputting
Code:
adb devices
and
Code:
fastboot devices
Still doesn't work. I even made sure that my drivers are working so I tried it on my brothers Poco F3 and the PC can detect his phone through ADB commands.
Waiting for a day if it magically turns on again. Nope.
Charging it up because maybe the battery is low. Nope.
At this point my only two choices is opening up the back panel then replugging the battery so it completely turns off and hopefully boots up. But its a risky task since I don't have special tools to open up my phone, and my another choice is just bring it on a service center.
Click to expand...
Click to collapse
If the phone is bootloader locked don't do anything, take it to service center it's out of your hands.
If service center intends to charge you something well you could find some people online with edl accounts to do flashing for you but this sounds like hardware issue if you don't see poco logo ...
Edit: Sry didn't read the post fully - did u try fastboot devices when in fastboot mode - volume down and power ? If it is recognized and bootloader unlocked you can try flashing - go with xiaomi firmware, last thing you want is to be stuck on custom firmware when you take it in for repair - again only if bootloader is unlocked
since your brother pc can recognize, tried fastboot miui.eu on his pc
but I had this problem before and the only solution is to change mainboard on the xiaomi service center.
rururi said:
So I am normally using my phone scrolling through social media but it suddenly froze so I tried to hard reset it, but it goes in to a bootloop without any display on the screen. I could tell it is on a bootloop because of the repeating vibration everytime the phone boots up.
My device is Poco F3 (alioth) Running stock MIUI 12.5 bootloader unlocked and rooted with Magisk.
Things I have tried:
Long pressing power button, long pressing both power button and volume down button, long pressing power and volume up button, then long pressing all of them.
Plugging it on my PC but it doesn't even detect it. Tried inputting
Code:
adb devices
and
Code:
fastboot devices
Still doesn't work. I even made sure that my drivers are working so I tried it on my brothers Poco F3 and the PC can detect his phone through ADB commands.
Waiting for a day if it magically turns on again. Nope.
Charging it up because maybe the battery is low. Nope.
At this point my only two choices is opening up the back panel then replugging the battery so it completely turns off and hopefully boots up. But its a risky task since I don't have special tools to open up my phone, and my another choice is just bring it on a service center.
Click to expand...
Click to collapse
Do you have any clue as to why this happened? Any mods done besides applying Magisk?
If the software got damaged, you could try the EDL Mode but that's difficult. Should be your last resort.
If hardware, then I don't know unfortunately...but then how?
rururi said:
So I am normally using my phone scrolling through social media but it suddenly froze so I tried to hard reset it, but it goes in to a bootloop without any display on the screen. I could tell it is on a bootloop because of the repeating vibration everytime the phone boots up.
My device is Poco F3 (alioth) Running stock MIUI 12.5 bootloader unlocked and rooted with Magisk.
Things I have tried:
Long pressing power button, long pressing both power button and volume down button, long pressing power and volume up button, then long pressing all of them.
Plugging it on my PC but it doesn't even detect it. Tried inputting
Code:
adb devices
and
Code:
fastboot devices
Still doesn't work. I even made sure that my drivers are working so I tried it on my brothers Poco F3 and the PC can detect his phone through ADB commands.
Waiting for a day if it magically turns on again. Nope.
Charging it up because maybe the battery is low. Nope.
At this point my only two choices is opening up the back panel then replugging the battery so it completely turns off and hopefully boots up. But its a risky task since I don't have special tools to open up my phone, and my another choice is just bring it on a service center.
Click to expand...
Click to collapse
If it's recognised by your brothers pc, try that pc for flashing stock fastboot rom using miflash, and don't forget to choose 'flash and wipe' instead of 'flash and lock' in bottom right corner of miflash. Let us know how you get on
Happened today. Random bootloop while under normal use. Also occasionally attempted to trigger the emergency SOS call when power BTN clicks 5 times.
Saved by a solution in poco x3 thread.
The failure mode I experienced was possibly a "sticky" power button.unsure if it's an electrical short or something mechanical in nature tho since it's intermittent triggering of the power button.
Temp fix was some quick clicks of the power button a bunch of times(20-30 clicks?).
Also shut off the emergency sos function.
jowaii89 said:
Happened today. Random bootloop while under normal use. Also occasionally attempted to trigger the emergency SOS call when power BTN clicks 5 times.
Saved by a solution in poco x3 thread.
The failure mode I experienced was possibly a "sticky" power button.unsure if it's an electrical short or something mechanical in nature tho since it's intermittent triggering of the power button.
Temp fix was some quick clicks of the power button a bunch of times(20-30 clicks?).
Also shut off the emergency sos function.
Click to expand...
Click to collapse
Same... it started calling emergency number and wouldn't shut off by holding power button.
Worst device ever
{Mod edit: Inappropriate language edited. Oswald Boelcke}
Related
My G2 won't boot normaly and is acting very straingly. I did a search of other similar problems people have had, but nothing matches what is happening to mine. It started when I noticed my power button and volume up button stoped working. I assumed it was a glitch and thought a reboot might help. Since the power button wasn't functioning, I pulled the battery to reboot it. That's when it stoped working. When I turn it on normaly with the power button, the screen stays off, it vibrates three times, and the led blinks orange untill I put the battery. If I attempt to boot into recovery with the button combination, it does the same. If I attempt to boot into HBoot, it vibrates five times and the led lights up solid green. Here's where things get realy strange. When I plug the phone into the charger while the phone is off, after about five seconds the phone comes on into the recovery bootloader even though when I boot while holding the buttons it dosn't work. I have the ClockworkMod touch recovery installed. From within the recovery I have full access to everything including ADB with root access. When I select the reboot option from recovery, it does the same thing with the vibrating and the blinking led. I tried the key test in the recovery and I discovered that my volume up button only works intermitently and my power button seems to be working fine. I haven't attempted to flash a new rom yet because I'm assuming it must be something else since I can't even access HBoot, and I'm scared if I touch anything I'll loose access to recovery and ADB as well.
Any advice? Could a damaged volume up button contact cause all this to happen? Should I try flashing it from recovery even though I can't access HBoot?
Thread moved to Q & A section, post in the relevant section next time.
in adb try
adb reboot-bootloader
demkantor said:
in adb try
adb reboot-bootloader
Click to expand...
Click to collapse
Just tried it. Screen goes black, vibrates three times, and led blinks orange untill I pull the battey. It was a good Idea though, I didn't think to try that myself.
you know what, are these very quick vibrates? you mentioned there is a problem with your volume rocker (sticky keys?) your phone may be trying to get into the jtag/download mode.
not sure how to use this mode on the vision but tell me if this is the same response you get.
take out battery, hold both volume buttons, plug phone into computer.
it should vibrate three times rapidly and computer should look for driver :
Qualcomm CDMA Technolgies MSM driver
not sure where to get the proper driver for the vision but ive used this mode to root other android phones and i know there is a "unbricking project" for various phones that use this mode.
nothing for the vision that i know of though.
but being you have adb access maybe test a few things first like see if anything is accessible from your emmc
type:
Code:
adb shell
dmesg | grep mmc0
and see what happens
edit:
i can replicate you situation by holding volume up while powering on
you have a stuck volume up key, almost 100% just open up phone and clean it out and you should be just fine!
Hello Everyone
TL;DR Screen doesn't come on at all, battery led only flashes while it is rebooting (More details below), and When plugged in to my windows pc, a bunch of "Local Disk Found" pop up, some of the volumes I can access, most I cannot.
I have searched and searched the internet the past 24 for solutions, and have yet to find one. So imma walk you through what led up to the issue, as well what solutions I have tried.
Yesterday while I was trying to update my rom, I ended up getting stuck in what I thought was a boot loop. I then decided to hard reset my phone and go into recovery in hope to try to reinstall the rom. To my surprise, I could not access the internal sd card in the phone. Data was unmounted in the "Mount" settings and I could not what so ever remount it. After this I tried to side load it, but to no avail.
In response to all my attempts to fix the phone at that point, in frustration, I just said "**** it" and went into factory reset in the bootloader. This is where the hard brick happened. At this point, the screen would not come one, and the battery led was not lit when plugged in. I tried letting my phone charge over night and then, tried the "Battery Recalibrate method". I then tried the "Hold Pwr + Volume up for 10 seconds, then Power + volume Down until you access the bootloader"
After that, I then thought that the firmware was corrupted, so I tried to see if I could push an img to the phone, however fastboot does not see the device. I tried RUU, it does not see the device. I tried the HTC Unbrick method by Dexter that required me to install ubuntu and do some things in terminal, that also did not find the device. And here I am stuck. One thing unique to my situation that I have yet seen reported in the countless threads I have searched, is that when I plug my phone to my pc, a large amount of disk drives are found. Most of them are not accessible, but there are a couple that I can go in and see files for. Windows asks me if I want to format the ones I can't access. When hooked to my pc, I tried the the Power + volume button combinations, the only thing that seems to happen off of this is that my phone seems to reboots, and the battery indicator briefly shows.
Anyways, this is all I can remember. Any help would be GREATLY appreciated. I don't really think it is a hardware related issue since my phone does somewhat boot. However it seems it can't get to a bootloader what so ever.
Try holding power and vol up for a long time, like a minute or more. Try with and without charger attached, and after sitting on charger overnight.
If the bootloader is intact, the phone is likely not truly bricked (recoverable). And I don't see how you could have damaged hboot by the actions you mentioned.
What is the phone's original CID (carrier version) and are you s-on or s-off?
redpoint73 said:
Try holding power and vol up for a long time, like a minute or more. Try with and without charger attached, and after sitting on charger overnight.
If the bootloader is intact, the phone is likely not truly bricked (recoverable). And I don't see how you could have damaged hboot by the actions you mentioned.
What is the phone's original CID (carrier version) and are you s-on or s-off?
Click to expand...
Click to collapse
Verizon is the carrier version, and I am s-off.
Held vol + up for 5 minutes both with and without the charger. One time with the charger into my computer, and another into the wall. When it was in my pc, I can tell its doing nothing but rebooting over and over by the notification sound, and the constant "Found new disk" notifications I got. However still no luck, no screen turns on, no sign of hboot. I'm hoping to have some luck after leaving it on charge overnight and trying again.
TheBizkit said:
Held vol + up for 5 minutes both with and without the charger. One time with the charger into my computer, and another into the wall. When it was in my pc, I can tell its doing nothing but rebooting over and over by the notification sound, and the constant "Found new disk" notifications I got. However still no luck, no screen turns on, no sign of hboot. I'm hoping to have some luck after leaving it on charge overnight and trying again.
Click to expand...
Click to collapse
So still nothing after leaving it on charge overnight and I held vol + up for about 5 minutes. Things seem grim.
I think the proper thing to do when you discovered internal storage was not mountable, would have been to use the TWRP option to format internal storage (in Advanced Wipe options).
But now I'm baffled as to what happened that would have rendered the phone unable to boot into fastboot mode. Fastboot won't recognize the device if you can't boot into fastboot mode, which leaves use kinda stuck.
So you didn't try to flash anything during the course of all this troubleshooting?
What you did - "Hold Pwr + Volume up for 10 seconds, then Power + volume Down until you access the bootloader" is totally wrong
I used to get this bunch of local disk pop-up and this is how I get out the problem
Connect the device to pc, you can hear notification sound on pc that device is connected. Ignore all those bunch of local disk pop-up
Press & hold both power button & volume up button until you hear another notification sound that device is disconnected from PC (that's the indication that device is restarted)
Release both power & volume up button and quickly press & hold volume down button (only this one button)
This should get you on bootloader
redpoint73 said:
I think the proper thing to do when you discovered internal storage was not mountable, would have been to use the TWRP option to format internal storage (in Advanced Wipe options).
But now I'm baffled as to what happened that would have rendered the phone unable to boot into fastboot mode. Fastboot won't recognize the device if you can't boot into fastboot mode, which leaves use kinda stuck.
So you didn't try to flash anything during the course of all this troubleshooting?
Click to expand...
Click to collapse
No, nothing was flashed except the original Rom update that got this snowball rolling (Not saying its the roms fault, most likely mine).
ckpv5 said:
What you did - "Hold Pwr + Volume up for 10 seconds, then Power + volume Down until you access the bootloader" is totally wrong
I used to get this bunch of local disk pop-up and this is how I get out the problem
Connect the device to pc, you can hear notification sound on pc that device is connected. Ignore all those bunch of local disk pop-up
Press & hold both power button & volume up button until you hear another notification sound that device is disconnected from PC (that's the indication that device is restarted)
Release both power & volume up button and quickly press & hold volume down button (only this one button)
This should get you on bootloader
Click to expand...
Click to collapse
This is the one combination I forgot to mention in the op, sorry for that.
But I have tried this, before and after your post, still no luck.
If it worth mentioning, I can just hold power + down and it still reboots over and over. As well as just power. As a matter of fact, all button combinations reboot the phone over and over.
TheBizkit said:
If it worth mentioning, I can just hold power + down and it still reboots over and over. As well as just power. As a matter of fact, all button combinations reboot the phone over and over.
Click to expand...
Click to collapse
I thought the screen was dead? If so, how do you know its rebooting?
redpoint73 said:
I thought the screen was dead? If so, how do you know its rebooting?
Click to expand...
Click to collapse
By it constantly connecting and disconnecting from my pc. If that doesn't mean its rebooting, then I guess I'm mistaken.
TheBizkit said:
By it constantly connecting and disconnecting from my pc. If that doesn't mean its rebooting, then I guess I'm mistaken.
Click to expand...
Click to collapse
Well, it might mean that.
If it in fact is rebooting over and over on its won, simply holding the vol down button for a long time, should put you into bootloader (on the next reboot "cycle"). Again, assuming it is in fact rebooting, and that bootloader is intact.
Hi,
I've got my Pixel on February 2017 from Virgin Megastore in Dubai, all things were going right until last summer after a beach day, I realised that my volume down button does not work anymore and sometimes it still pressed (the button is not pressed physically) which puts my phone on vibrating mode maybe due to humidity or some dirt
I tried many solutions found on the internet: sucking the button, cleaning with Isopropyl alcohol… but no success
This weekend I noticed that my phone consume battery more than normal, tried to restart it but instead of rebooting normally the Fastboot appears
Now I’m stuck in this mode because my volume button down does not work and the power button work like if it is the volume button down, so I can switch between modes (start, power off, barcodes, recovery mode, restart bootloader) but I cannot select none of them
I tried to hold down the power button but it reboots on the same screen
I really don’t know what I can do
Please help me if you have any idea
Thanks in advance
Su fastboot reboot bootloader
Then flash the stock.
It needs USB Debugging to be enabled ? I'm not sure I had enabled it before that when I android starts normally.
Please share with me if you have a tutorial of flashing ROM that would work in my case
Thanks
Just wanted to tell you that I fixed the problem with a “hair dryer”, the volume button down starts working and I could restart the phone normally.
Thank you for you help
Hi.
I have a Xiaomi mi5s 64/3 GB in an endless bootloop. Here are the details:
The phone is:
rooted
bootloader unlocked
developer mode enabled
internal storage *not* encrypted
no MIUI account activated
USB debugging on
running the last EU MIUI 9.x development version (don't remember the exact version) with Android 7.0
has TWRP 3.2.1.0 and supersu 2.82
no password is set for unlocking the screen etc.
For some unknown reason the phone suddenly rebooted yesterday and got into an infinite bootloop cycle. I haven't changed any roms recently or done any such flashing. My google play automatic updates were disabled, but a few days ago I manually updated all the apps.
The only odd thing that happened prior to this bootloop, was that when shooting some photos with the google camera mod (same one I've been using for the past few weeks), 2 images were saved as corrupt unreadable files. But that happened a few hours before the bootloop suddenly started.
The current status is:
1. I cannot turn the power off (tried holding the power button, or power button + vol up and down for a very long time --> nothing).
2. I cannot enter recovery mode using vol up + power.
3. I cannot enter EDL using all 3 buttons.
4. If I hold volume down, it enters fastboot but automatically exits from it within 4 seconds (ADB and miflash cannot detect the device in this short period of time). holding the volume down button for a long time has a repating enter-exit-after-4-seconds from the fastboot graphics.
I waited until the battery was completely dead, than started charging it and the status described above was unchanged.
QUESTION 1 - restoring the internal data is my number one priority - does it seem possible here?
To be exact: I want the DCIM folder with the photos+ videos. What should I try now?
QUESTION 2 - I ordered an EDL cable, but am unsure if it supported for my MIUI version. if the EDL cable works, can I force the phone to enter recovery mode from within EDL?
If so - I guess I can copy the internal data to an external USB OTG flash drive I have (that works well with the phone).
If my data is restored, I will then move onto trying to reflash the phone, but at this point this is the least of my worries...
Thanks all.
Anyone?
Maybe it's a problem with the button? I would disassembly the phone and check the hardware.
bedson87 said:
Maybe it's a problem with the button? I would disassembly the phone and check the hardware.
Click to expand...
Click to collapse
I don't know - the buttons don't seem like they are stuck in any way. When I push them, they click back out as usual.
Update - I created an EDL flash cable by stripping the cable gently, exposing the green and black wires, and looping them together - connecting this cable to the phone didn't help either.
Maybe I need to wait for the battery to die so the phone will turn off, connect this cable to the phone, keep the power button pressed while I connect it to the usb port in my PC... what do you think?
I have the same problem with mi 5s which started after update. Don't know what to do.
Took the phone to a local lab - it was all due to a faulty power button module.
Hi everyone,
So yeah, I probably shouldn't have played around with recovery, bootloaders and custom OS, but my XZ2 Compact was rendered nearly useless by the last Android update, so I tried to install the new official Lineage OS on it. But I failed. Hard.
Symptoms
The phone now only reacts to the power button. When I press it, it displays a battery charge icon for a minute or two, then the screen turns off.
None of the other physical buttons do anything, and the button combinations don't work. As a result, I can't boot to recovery, or even access to fastboot.
The light indicator is on and red.
I let the phone drain its battery, see what happens, and well, nothing. Eventually the screen stops turning on. When I replug the phone, even if I don't touch anything, it will end up showing me the battery icon again, and is stuck in the same loop.
'adb devices' still sees my phone, but with no permissions. 'fastboot devices' doesn't see anything.
On Windows, Emma (Sony's flashing tool) doesn't see the device.
Causes
I was following this tutorial. I went up to "temporarily booting a custom recovery using fastboot". I used the latest LineageOS recovery for my phone, and the flashing worked fine according to the output of the fastboot command. But that's all. Impossible to do anything after that.
Do I now own a glorified paper weight? Or can I save this?
Thanks!
SOLVED! I managed to stop the charging loop with a key combination I discovered: volume up + volume down + power for about 10s. Then was able to load the bootloader and re-flash a recovery, custom ROM etc. Thank you all for your help.
Have you tried to hold vol+, vol- and power button all together for (at minimum) a minute?
I would then try to restore stock firmware with newflasher (you'll find it using Google search or here on xda).
Great, thanks a lot I didn't know this key combination and it allowed me to get out of that charging loop and start the bootloader. Problem solved!
Nice, glad to hear!