So here was my situation:
I was flashed the wrong piece of software (stupid me) and I was stuck in a boot loop. Unfortunately the volume down button on my HTC one S was not working so a simple boot into bootloader mode did not work!
Furthermore, I couldn't even get the phone OFF! Pressing the power button for minutes on end still ended up in the HTC constantly rebooting itself. (Worst thing ever!).
FIX:
Step 1: Power Off device
Although this may sound very easy to do, I could not get the device powered off via the power button(10-20 secs) so I had too do it the hard way.
Luckily, the One S being a sealed phone isn't actually hard to take apart. Its actually rather simple!
I used a video on youtube to disassemble then took out the battery for about 30 minutes. (Search "HTC ONE S fix" on Youtube and you'll find it. Sorry i can't post any links im a junior member!)
Step 2: Plug the USB cable into your PC
Put the battery in ( if you used the physical battery pull out of course)
With the device completely off plug the cable into the PC and run the command
Code:
adb devices
By doing this my device actually went straight to the recovery screen and the device was recognized on the computer.
Now the recovery screen i got wasnt very helpful as it continuously rebooted and eventually booted back to the white HTC screen.
HOWEVER, the fact that I could use ADB commands gave me hope.
Step 3: Reboot into bootloader using adb command
Code:
adb reboot bootloader
This is where I really saved myself i ran this command and got to the bootloader screen and I was able to actually work with that!
Step 4: Flash/ Restore Backup to your device and get it up and running!
Now there are a couple of ways you can choose to do this depending on your specific situation and resources available:
A) When in bootloader mode you can access the fastboot commands which will allow you to run any flashing commands that you need to rewrite whatever is corrupted (e.g boot.img)
B) If you have a working recovery simply select recovery and boot into recovery and flash either your nandroid backup or a new ROM as a whole
C) This is what i did, I ran a stock RUU which deteccted my phone and in 10 minutes my phone was up and running!!
Now I know this is a rather rare case, but I actually thought my phone was gone and the fact that I got it working really motivated me to put this out there so someone like me may be able to get their phone up and running again!
Forgive me this is probably my first real thread, Hopefully I continue to post how I fix some of the rarest occurrences I always seem to get myself into.
NO MORE BOOTLOOPS! Who says we need volume down buttons? LOL
Related
Hi,
my phone died yesterday because the battery was empty - so I charged it a little but the phone won't turn back on. The only thing I see are the touch buttons flashing when I hold the power button. And when I hold it long enough, the screen just flashes... When I tried to connect it my computer I got the ADB to work - I even managed to get to the recovery one time (i used the command adb reboot recovery for almost a hundred times before it came on). I wiped everything, reinstalled the rom (TrickDroid 4.0.0), but when I tried to reboot it nothing changed... it's still not working. Fastboot is not working.
Is there anything I can do about it?
Thanks.
Mmm, are you using CWM perhaps? If so, once you get the phone into fastboot - flash twrp.
Some suggestions you can try:
keep trying vol- + power untill you get into fastboot, it should work eventually.
Charge the phone a bit, unplug the usb cable, try and boot it <- This worked for me when my phone acted up like this, took a couple of tries though.
Have you tried spamming adb reboot bootloader ? That should also put you into fastboot eventually.
Once in fastboot, reflash the boot.img for the rom as well.
And once it works again, dont let the battery go flat, this seems like quite a common issue when the battery runs out.
Thanks for suggestions - I wrote a script that tired adb reboot bootloader every 20s .. and after like 400 runs it booted - I have no idea what this is about - but I should buy a new phone...
Tahnks again!
Hello All,
This is my first post at this forum.
I've come to a point where I'm on the verge of giving up.
A few days ago my Nexus 5 entered a boot loop without me doing anything special with it - it was just in my pocket.
All see is the google logo for a few seconds , then the screen goes down for a few more, and back to the google logo.
I'm able to go into fastboot by hold down the volume down (only) button when this happens, but the boot loop happens when I choose to boot into recovery mode.
My device has an unlocked bootloader.
I have fast boot access and no ADB (ADB wait-for-device doesn't work).
Went over a tutorial from androidforums.com and flashed a completely new image using fastboot.
The entire process worked, but the phone is still at the same state.
I've read that there is and issue with the power button on these devices - so I tried all methods of knocking it against stuff without success.
I've taken it to a lab nearby and the guy there was sure it was the power button. He said he fixed about 50 of these already - after a few hours he called me up and said he had replaced the power button 3 times and he's giving up.
in short , this is the current situation :
1. Device stuck in bootloop - only google logo is seen
2. can boot into fastboot (and have fastboot access from PC) but can't boot into recovery
3. flushing a stock succeeds but won't help
4. power button seems o.k.
I am about to call this a bricked phone and look for a new one but something inside me tells me that this might still be a software issue and can be fixed.
I would be happy to know if there is a way to know what is failing in the boot sequence. or maybe load a debug application on to the device to check the HW. I've yet to find any help in that direction.
I'm a software eng. working in the cellular comm. field, so I'm up for anything that anyone has in mind.
Thanks,
Ran.
XDA Visitor said:
Hello All,
This is my first post at this forum.
I've come to a point where I'm on the verge of giving up.
A few days ago my Nexus 5 entered a boot loop without me doing anything special with it - it was just in my pocket.
All see is the google logo for a few seconds , then the screen goes down for a few more, and back to the google logo.
I'm able to go into fastboot by hold down the volume down (only) button when this happens, but the boot loop happens when I choose to boot into recovery mode.
My device has an unlocked bootloader.
I have fast boot access and no ADB (ADB wait-for-device doesn't work).
Went over a tutorial from androidforums.com and flashed a completely new image using fastboot.
The entire process worked, but the phone is still at the same state.
I've read that there is and issue with the power button on these devices - so I tried all methods of knocking it against stuff without success.
I've taken it to a lab nearby and the guy there was sure it was the power button. He said he fixed about 50 of these already - after a few hours he called me up and said he had replaced the power button 3 times and he's giving up.
in short , this is the current situation :
1. Device stuck in bootloop - only google logo is seen
2. can boot into fastboot (and have fastboot access from PC) but can't boot into recovery
3. flushing a stock succeeds but won't help
4. power button seems o.k.
I am about to call this a bricked phone and look for a new one but something inside me tells me that this might still be a software issue and can be fixed.
I would be happy to know if there is a way to know what is failing in the boot sequence. or maybe load a debug application on to the device to check the HW. I've yet to find any help in that direction.
I'm a software eng. working in the cellular comm. field, so I'm up for anything that anyone has in mind.
Thanks,
Ran.
Click to expand...
Click to collapse
Hello, and welcome to XDA!
It does sound like a hardware issue and it could be the power button, except for one thing: wouldn't a held down power button in fastboot cause a shutdown as well? Maybe not, but I thought I'd ask that.
At any rate, better to get an opinion from someone who actually has the deivce. Please create an account (so you post in other forums) and then post in this thread (can copy and paste from here):
> Google Nexus 5 > Nexus 5 Q&A, Help & Troubleshooting > [HELP THREAD] Nexus 5
Hope this helps, and good luck!
Hi guys,
I currently have some issues with my beloved N5. I try to be as specific as I can (therefore the text will be a bit longer)
First things first: My device is experiencing the well known "stuck power button problem".
But I also do have problems which are not related to that one (at least thats what I believe).
Overview:
CM 13.1
ElementalX Kernel
TWRP on 3.0.20
Main issue: I can not start my phone regularly. When not plugged in, it just does not respond at all.
If it is plugged in I can get into the bootloader with only pressing Volume down (because the power button is stuck inside). Weird fact #1: in bootloader the power button should work to confirm a specific task like Start, or boot into recovery but it doesnt. Also: the phone is steady in the bootloader and does not keep rebooting.
Therefore I wanted to perform a backup (nandroid or at least all media) and reflash my ROM to see whether it is more of a software issue. I tried booting into TRWP which is not working (device shuts down after Google logo (might be because of the power button issue?).
I know that I can flash the recovery again through adb or the Nexus ToolKit but obviously I want to save my data first.
As far as I know there is no option as adb pull or through the recovery to save those only being in bootloader mode, am I right?
Question: Can I dirty flash without losing data? If thats not the cure, what else could help?
Other facts to know: while running
Code:
adb devices
I get that the
Code:
"adb server version (36) doesnt match this client (35): killing...
but then:
Code:
*daemon started successfully*
(same in Nexus Toolkit).
If I continue with
Code:
adb backup
it says: no devices / emulators found. Altough the nexus toolkit (and fastboot devices) say:
Code:
FASTBOOT: 03181238e07723e0 fastboot
If you made it until here thank you for reading :good: and I would be even more pleased if someone could help.
Best,
McRacoon
I have this problem to , i cant use my volume and power button in ROM / TWRP ,
I got lost, which data you want to save ?
fastboot flash boot recovery.img | fastboot reboot than gets you to recovery from where you can save data.
@Redchi: not really exactly my problem but if you can get into recovery you can use your touchscreen in TRWP?!
@icrunchbanger thanks for your reply.
I want to save all my data like videos, pictures, whatsapp chats etc.
I know how to flash the recovery (again). The question was whether I can save any data without a working recovery (just from the bootloader). Imo it is not possible but maybe you guys know how to do so.
If I reflash the recovery I still can not enter it as the phone reboots itself every 5 seconds due to the stuck power button. The reflashing operation is not finished (Nexus Toolkit says: "Waiting for your device" and times out after a while) and the battery icon pops up every 3 seconds.
Edit: and yes I tried several workarounds to unstuck the power button like flicking against the button, tapping on table, cleaning etc. The only thing I haven't done is tearing the motherboard apart and replacing the whole button itself.
I recommend removing the motherboard, applying pure alcohol around the area, and then quickly pressing and releasing the power button? If this doesn't work, I suggest replacing the power button.
i can use button to get bootloader + TWRP , but my Button volume up down and power cant use in Rom or TWRP, i do no this software or hardware ,? my nexus normaly use but not have button , I use mikey or double tab to wake get screen on , i use apk to get volume , sorry bad english
Hey guys - I hope you're doing well.
I recently got an HTC U12+, but wanted to try using a custom ROM due to all of the bloatware . Unfortunately I think I've ended up bricking my device. Here are some things I've since tried:
- Restoring to the backup I made beforehand in TWRP - restore works without any errors, but then just hangs at the boot screen
- Method 1 from this thread (https://forum.xda-developers.com/u12-plus/how-to/collection-htcu-u12-ruu-firmware-t3794664) - TWRP always says the zip files are corrupted for some reason
- Method 3 from that same thread - this actually worked before, but I tried installing a custom ROM again, somehow messed up again, and now this method no longer works as it just hangs at the "HTC" boot screen for eternity
- Both methods in this thread (https://www.theandroidsoul.com/how-to-install-htc-firmware-ruu-and-zip/) - the first one leads to a "failed remote 99 ru unknown fail terrible mishap" error, and for some reason my PC doesn't see my phone when I try the second despite being able to see it in file manager
- Probably many other methods that I've now forgotten
I know this is a whole lot of information, but I'm in desperate need of some help. I typically like to troubleshoot things myself, but I've been trying to fix this for quite some time now and could definitely use another set of (much more experienced) eyes. I greatly appreciate any help you guys can provide.
Thanks.
Flash RUU with SD card method
Download RUU from here(important:check your CID): https://docs.google.com/spreadsheets/d/1wIRrVQawd5rD-t9VKPQ-SdRK20RcJVZhwD7lhmPIK8w/edit#gid=0
1. rename RUU to 2Q55IMG.zip
2. copy zip in the root of your sd card. - external card / not internal - it will not work
3. reboot to download mode,
4. your device will pick up the zip file and flash it.
5.follow on screen instructions and enjoy your RUU(this method erase all your data)
I'm having an issue with my u12+ where it just continually reboots to a message saying "The boot loader is unlocked and the software integrity cannot be guaranteed. Any data stored on the device maybe available to attackers, do not store sensitive data on this device" and then it shows the white HTC logo that says Powered by Android down the bottom of the screen, it stays like that for about 5 minutes and then reboots and does the same thing over again.
Holding the power down button does nothing, it will not turn off the phone. Holding power and volume down does nothing either. The phone just does this every 6 minutes and reboots and cycle and that's it.
I've tried putting the file 2Q55IMG_IMAGINE_DUGL_O80_SENSE10GP_hTC_Asia_TW_1.53.709.1_Radio_sdm845-000201b-1807311356_release_531499_signed_2_4.zip (renamed to 2Q55IMG.zip) on the root of a 8gb Fat32 formatted SD card, but I just can't get into recovery or download mode.
I've tried holding down all 3 side buttons for minutes, or just the power button, or combination of buttons, they all do nothing to the phone. (it's as tho they are disabled, but sometimes holding a combination of the 3 will make the phone vibrate a little bit, but in no particular time or order)
When the phone is in either state (locked bootloader message or white HTC logo) my Windows 10 PC sees the phone plugged in as a "USB Input Device", not an Android Phone or Android Device. So using ADB or Fastboot commands do not work to it. I've tried to force the driver to the HTC driver but that does not work.
I also tried using the RUU_IMAGINE_UHL_O80_SENSE10GP_NA_Gen_Unlock_1.30.617.2.exe file, but once again it doesn't detect my phone.
Any help would be kindly appreciated.
Cheers!
EDIT: So I was finally able to get into download mode by waiting until the phone done its 6 minute reboot and then holding power down until it vibrated once, then held volume up until it vibrated again, then let go of the power button, I was then able to choose recovery, download etc.
So I managed to get the file 2Q55IMG.zip to install, it said it installed 100% okay. The phone rebooted and now I'm stuck again just at the white HTC logo and Power by Android down the bottom of the screen.
This time the phone is not automatically rebooting itself and no key combinations will make it reboot. I've tried holding them all in certain combinations for periods of time, the phone will not reboot or turn off.
EDIT 2: So maybe I didn't wait long enough after installing the 2Q55IMG.zip file, I finally got the phone to reboot and now I've got a working phone again. happy days :laugh:
whowhatwhen said:
I'm having an issue with my u12+ where it just continually reboots to a message saying "The boot loader is unlocked and the software integrity cannot be guaranteed. Any data stored on the device maybe available to attackers, do not store sensitive data on this device" and then it shows the white HTC logo that says Powered by Android down the bottom of the screen, it stays like that for about 5 minutes and then reboots and does the same thing over again.
Holding the power down button does nothing, it will not turn off the phone. Holding power and volume down does nothing either. The phone just does this every 6 minutes and reboots and cycle and that's it.
I've tried putting the file 2Q55IMG_IMAGINE_DUGL_O80_SENSE10GP_hTC_Asia_TW_1.53.709.1_Radio_sdm845-000201b-1807311356_release_531499_signed_2_4.zip (renamed to 2Q55IMG.zip) on the root of a 8gb Fat32 formatted SD card, but I just can't get into recovery or download mode.
I've tried holding down all 3 side buttons for minutes, or just the power button, or combination of buttons, they all do nothing to the phone. (it's as tho they are disabled, but sometimes holding a combination of the 3 will make the phone vibrate a little bit, but in no particular time or order)
When the phone is in either state (locked bootloader message or white HTC logo) my Windows 10 PC sees the phone plugged in as a "USB Input Device", not an Android Phone or Android Device. So using ADB or Fastboot commands do not work to it. I've tried to force the driver to the HTC driver but that does not work.
I also tried using the RUU_IMAGINE_UHL_O80_SENSE10GP_NA_Gen_Unlock_1.30.617.2.exe file, but once again it doesn't detect my phone.
Any help would be kindly appreciated.
Cheers!
Click to expand...
Click to collapse
with the phone off, turn it on,when you feel first vibration
quick release power key and keep push volume down.
Smartphone should boot in bootloader mode.
can you get into this mode with this guide?
fabrizio b92 said:
with the phone off, turn it on,when you feel first vibration
quick release power key and keep push volume down.
Smartphone should boot in bootloader mode.
can you get into this mode with this guide?
Click to expand...
Click to collapse
Cheer mates, issue sorted. I just updated my comment in my post.
Not sure if I'm game enough again now to try and put LeeDrOiD and Magisk on it.
Please help!
Hello! This is a distress call, because I think I brickered my S10e, through my own fault ...
Trying to install the TWRP according to the instructions given in the Hades Rom, I made two unforgivable mistakes, since years of flashing roms ...
1) I took the wrong installation file (I have the G970F/DS, and flash the beyond2lte file, instead of beyond0lte)
2) I omitted to force boot of TWRP just flashed.
Result: I cannot enter download mode as I did before (the phone does not blink), and trying to enter recovery, out of 20 attempts, it only turned on 2 times and does not go beyond the warning screen that the oem is unlocked, and it is not a safe state. I press power to continue as it says, and the screen turns off. Of course it doesn't start normally with the power button either.
I found out recently that been connected to the PC, it is recognized by it, and I even could access to it though the Windows explorer... Ergo, it's not dead, but the screen is in the infamous "black screen of death". Tried the usb jig emulator, by sugestion of denon480, but it didn't work (see screen capture).
Is there a way to force it into download mode, to flash the correct recovery, or eventually an official firmware? The cell phone is immaculate, I can not resign myself to it turns paperweight !!!!!
I put this here, because the problem was in TWRP recovery flashing, I didn't arrived to the Hades ROM installing process, and this way I can reach more people...
I appreciate any help.
Cheers
https://1drv.ms/u/s!Aqmv5IkqbGj3mwqTWmEd3VJxPPHs?e=V3UVSP
I don't even think it is possible to brick Samsungs like that. Are you following the right steps to download mode? Ergo,
Step 1 – Turn OFF your Galaxy S10.
Step 2 – Now press and hold the following buttons on your phone together: Volume Down + Bixby Button.
Step 3 – Next, plug in one end of the USB-C cable to a computer and the other end to the phone. As soon as you will connect, your phone will power on.
I have the same problem. I do not know if the OEM unlocking has something to do with that as I can not turn on OEM although it is not missing but it is not active and can not be turned on. I tried all the solution available online but it looks like no one knows what to do even the so called experts know nothing at all and the only things they know is the direct easy way. So disappointed
Same problem here... any solutions?