I need help with figuring how to solve my problem. Whenever I try to reboot it boots straight to hboot/fastboot. I can't update my system because of it. Can't unlock because it freezes at the screen where I choose to unlock or not. What should I do??
What have you done to your phone so far?
Have you unlocked your bootloader?
Have you installed TWRP Recovery?
Have you rooted your phone?
Have you flashed any new roms or kernels?
Can you still access your recovery? (TWRP or stock - stock is just black screen with a red triangle in the middle)
Please give a detailed description of the things you have done, the results of each of these things if any, and when your phone started rebooting straight to HBoot.
Also, is your phone the 32 bit US model, or the 64 bit Europian/Australian model?
There's still a chance your device's firmware is recoverable, but you probably shouldn't try anything until you get some advice from someone who has a lot of knowledge and a detailed description of how you ended up where you're at.
Good luck!
What have you done to your phone so far? I have unlocked it before, but end up re-locking it after failing to root it.
Have you unlocked your bootloader? I did and relocked it.
Have you installed TWRP Recovery? Couldn't and Can't
Have you rooted your phone? No
Have you flashed any new roms or kernels? No
Can you still access your recovery? (TWRP or stock - stock is just black screen with a red triangle in the middle) I can't enter recovery.
I have no .img files when entering hboot. I can't unlock because it freezes after choosing the unlock option. It shows entering recovery at the stop and a discalimer message at the botto and goes no where
How to fix the issue
The first thing is to do is to relock the boot loader by typing 'fastboot oem lock' and the appropriate RUU for your device and carrier and open the RUU and reflash the device and it will be good as new
bcbradley12 said:
The first thing is to do is to relock the boot loader by typing 'fastboot oem lock' and the appropriate RUU for your device and carrier and open the RUU and reflash the device and it will be good as new
Click to expand...
Click to collapse
You should not just lock the boot loader without first reinstalling the stock recovery! When you go to use the RUU if it doesn't see the stock recovery it's going to fail... First reinstall the stock recovery and then OEM lock then you can use the RUU!
P.S. I have no idea why you're replying to some post from 2014... This post was almost a year ago lmao...
You don't have to have stock recover I did it with TWRP Recovery and it put stock recovery for you
bcbradley12 said:
You don't have to have stock recover I did it with TWRP Recovery and it put stock recovery for you
Click to expand...
Click to collapse
OK but why are you replying to and worried about a post from a year ago?!?
Related
Hi all,
Got a sensation XL here which isn't rooted, nor has it been altered in anyway, not sure what happened to it to be honest and it's not actually mine either.
It's still s-on, I can get to the bootloader no problem, but factory reset just doesn't do anything, it just puts it back in the boot loop.
Any ideas?
Thanks.
PS: I'm thinking it's bricked.
Lock the bootloader (if that's been unlocked) and then try flashing the RUU to put it back to factory.
You're in england, so unless it's branded, the RUU you need is in the RUU thread in the dev forum, and it's 1.05.401.x that you want.
MinecraftZombi.es said:
Lock the bootloader (if that's been unlocked) and then try flashing the RUU to put it back to factory.
You're in england, so unless it's branded, the RUU you need is in the RUU thread in the dev forum, and it's 1.05.401.x that you want.
Click to expand...
Click to collapse
It's not been unlocked, it's just a stock handset, not branded, so with the official ruu, how do i flash it?
Thanks for replying m8.
make sure htc sync is installed on a PC (just for the drivers, you don't want to actually use it)
Plug the phone in via the USB (Direct, not through a hub)
Run RUU file on PC.
that should be it.
Thanks pal, fingers crossed eh.
Will let you know if it worked.
It didn't work
Tried both of the Europe RUU's but it still hasn't worked, says signature error?
Both of the files took an hour to download each.
Seriously hating this now
Any other ideas??
Thanks.
if that hasn't worked, next thing i'd try is to flash a custom ROM.
Can it get into fastboot?
If so, i'd unlock the bootloader, install the recovery and see if you can flash one of the custom ROMs.
MinecraftZombi.es said:
if that hasn't worked, next thing i'd try is to flash a custom ROM.
Can it get into fastboot?
If so, i'd unlock the bootloader, install the recovery and see if you can flash one of the custom ROMs.
Click to expand...
Click to collapse
Yea i went ahead and unlocked it but it's not letting me into the recovery, any ideas?
dladz said:
Yea i went ahead and unlocked it but it's not letting me into the recovery, any ideas?
Click to expand...
Click to collapse
Actually no i didn't i just used the HTC method.
What can i flash to get this thing working man, it's killing me, even factory reset doesn't work? That's just not normal, i'm s-on, i don't think theres an s-off method for the XL yet? Maybe there is.
But i'm really restricted as to what i can do, i've got fastboot and it works fine but besides that i'm lost.
factory reset uses the recovery partition. if that's chuffed, so's your hard reset.
I have attached the stock recovery from 1.05
go into fastboot.
when there, enter
Code:
fastboot flash recovery recovery.img
That should re-flash the recovery as long as your bootloader is unlocked. that might bring it back to life.
if it fails, flash the CWM recovery and then use a custom ROM
download the paul o'brien recovery and then use the same command as above, but using the name of the modaco recovery file
Code:
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img
that should then allow you to flash a custom ROM
Ok so it's not bootlooping now on factory reset, it's just stopped on the white HTC screen after hitting factory reset.
I'll leave it there for a bit and see how it goes, i don't think it's going to progress though.
The device is defo unlocked.
Going into recovery brings it back to the bootloop.
It's different on factory reset just not recovery and neither are progressing, i'll give the other recovery a whirl.
Lol failed battery low
MinecraftZombi.es said:
factory reset uses the recovery partition. if that's chuffed, so's your hard reset.
I have attached the stock recovery from 1.05
go into fastboot.
when there, enter
Code:
fastboot flash recovery recovery.img
That should re-flash the recovery as long as your bootloader is unlocked. that might bring it back to life.
if it fails, flash the CWM recovery and then use a custom ROM
download the paul o'brien recovery and then use the same command as above, but using the name of the modaco recovery file
Code:
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img
that should then allow you to flash a custom ROM
Click to expand...
Click to collapse
Nah m8, none of them worked or changed anything, the only difference being that factory reset on the stock recovery just stayed on the white htc screen, no change besides that.
Any other ideas? and thanks for taking the time to help me too.
I appreciate it.
I'm really not sure what else to suggest. if recovery just isn't loading after being flashed, then it suggests some sort of brick i think...
Even if there's no ROM installed, once a recovery is flashed, you should be able to at least access the recovery and from there install some sort of rom.
I'm beginning to suspect that it is indeed bricked, as you did in the first post.
MinecraftZombi.es said:
I'm really not sure what else to suggest. if recovery just isn't loading after being flashed, then it suggests some sort of brick i think...
Even if there's no ROM installed, once a recovery is flashed, you should be able to at least access the recovery and from there install some sort of rom.
I'm beginning to suspect that it is indeed bricked, as you did in the first post.
Click to expand...
Click to collapse
well i've been looking for some official ruu's to flash, one up from the one i'm on would do it i reckon, or at least give me a starting block.
I tried the test rom from a thread and now i can't find it
Will look again, find it and flash it, the test one didn't work, so i'm going to try a slightly older one.
fingers crossed, again.
Recently, I had saved on my HDD before PirateGhost pulled it, his ICS rom, So I followed the diretions to flash the boot.img before flashing thr rom, so it installed and such, and when it went back to the recovery menu it said installed failed, but the actual program that launched o install the stuff said it was ok..Ok lets fast forward I reboot the device and it starts booting up, and shows the boot animation, then it will freeze and of course bootloop, but me being smart I did a backup before I installed anything and it still bootloops, it doesn't even get to the bootanimation... So this is where I start worrying. So I looked and try to revert back to stock just to see if it will work, I can't even lock my bootloader because it says something about error too many links.>.< I need help and any help is most appreciative!
Did you let the PH39IMG.zip install 2 times? Or did you try to update to the newest H-Boot before you re-locked your bootloader? I saw the same error about too many links when I tried to update H-Boot before I locked the bootloader. When you go into the bootloader what version of H-boot does it show?
I have Hboot 1.83.0014, and after i installed the PH39IMG, I installed a new kernel and a new rom too see if it would work and it booted up and everything it was working, so I tried to restart the phone to restore a backup I had and now my recovery won't even boot up, I can still access bootloader and such
Riomaru said:
I have Hboot 1.83.0014, and after i installed the PH39IMG, I installed a new kernel and a new rom too see if it would work and it booted up and everything it was working, so I tried to restart the phone to restore a backup I had and now my recovery won't even boot up, I can still access bootloader and such
Click to expand...
Click to collapse
Read the instructions again. You have the wrong hboot
Sent from my HTC PH39100 using xda premium
Riomaru said:
I have Hboot 1.83.0014, and after i installed the PH39IMG, I installed a new kernel and a new rom too see if it would work and it booted up and everything it was working, so I tried to restart the phone to restore a backup I had and now my recovery won't even boot up, I can still access bootloader and such
Click to expand...
Click to collapse
That's the old H-Boot. That's why the ICS ROM doesn't flash correctly. You need to lock your bootloader and use the PH39IMG.zip to install the new H-Boot. Ignore the error you get on the command line when relocking. You should get into the bootloader and it should say relocked and have a security warning of some kind. Just let it run the PH39IMG.zip and update. It will run once and turn your phone off. Boot back into the bootloader and let it update again. When it's done you will have to flash recovery again, then the boot.img, and then boot to recovery and flash the ROM.
pside15 said:
Just let it run the PH39IMG.zip and update. It will run once and turn your phone off. Boot back into the bootloader and let it update again. When it's done you will have to flash recovery again, then the boot.img, and then boot to recovery and flash the ROM.
Click to expand...
Click to collapse
The step I bolded isn't necessary. If you wait long enough (30-45 seconds?), the phone powers back on and boots into bootloader on it's own and completes the install without any action required on your part.
anthromatt said:
The step I bolded isn't necessary. If you wait long enough (30-45 seconds?), the phone powers back on and boots into bootloader on it's own and completes the install without any action required on your part.
Click to expand...
Click to collapse
Thanks for the info. I wasn't aware of that. I just booted back to the bootloader manually and everything worked well.
pside15 said:
Thanks for the info. I wasn't aware of that. I just booted back to the bootloader manually and everything worked well.
Click to expand...
Click to collapse
Yeah, I discovered that by accident after about 4 failed attempts to successfully flash. The last time I "forgot" to pull the battery after the phone powered off because I had gone into the kitchen to get coffee. When I returned, it had rebooted itself and was finishing the update.
I couldn't flash the recovery while it was locked so I had to unlock it, but currently I am flashing the rom and I will see what happens
I had success by flashing the RUU first then flashing the new recovery, then finally the Rum Float zip file.
Riomaru said:
I couldn't flash the recovery while it was locked so I had to unlock it, but currently I am flashing the rom and I will see what happens
Click to expand...
Click to collapse
Yes, that is true but you didn't complete the H-Boot update. ICS ROMs won't flash properly on the old H-boot. You need to lock the bootloader to use the PH39IMG.zip to update H-Boot then unlock and flash recovery and then ROM.
pside15 said:
That's the old H-Boot. That's why the ICS ROM doesn't flash correctly. You need to lock your bootloader and use the PH39IMG.zip to install the new H-Boot. Ignore the error you get on the command line when relocking. You should get into the bootloader and it should say relocked and have a security warning of some kind. Just let it run the PH39IMG.zip and update. It will run once and turn your phone off. Boot back into the bootloader and let it update again. When it's done you will have to flash recovery again, then the boot.img, and then boot to recovery and flash the ROM.
Click to expand...
Click to collapse
Ok that did it !!!! Thank so much
Riomaru said:
Ok that did it !!!! Thank so much
Click to expand...
Click to collapse
No problem. Glad you got everything worked out.
I have a soft-bricked Raider and looks like I am having the same problem, I have hboot 1.83.0014 and unlocked. a getver all shows the version-main to be 1.65.666.3 so I google that up and found this ICS image...
OTA_HOLIDAY_ICS_35_S_BM_3.38.666.2-1.65.666.3_release_255932wpop8vtj8tts3ou3.zip
http://forum.xda-developers.com/showthread.php?t=1498003
So it appear I need to lock my bootloader and update the hboot.
When I run oem lock this is what I get.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Unknown error))
finished. total time: 0.022s
I let it sit for 15 minutes but no change.
what do I need to do to get my bootloader relocked?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
I have a Sprint HTC One. I previously unlocked the boot loader and installed clock work mod recovery. I achieved SU and partial Super CID. I tried flashing Viper ROM after relocking the boot loader, which failed. when I went to reboot the phone, I was in boot loader without a system ROM. so I installed the stock ROM and updated firmware. the phone now works. however, I lost su and my custom recovery. I tried to unlock the bootloader , reinstall Viper, but neither will work it fails every time. I am experienced at following instructions on this website, but I lack the knowledge to know exactly what I am doing with each action.
Please help me get either su, custom recovery or the boot loader unlocked. I still have S-off and I am at a loss. Thank you!
patrickgartner said:
I have a Sprint HTC One. I previously unlocked the boot loader and installed clock work mod recovery. I achieved SU and partial Super CID. I tried flashing Viper ROM after relocking the boot loader, which failed. when I went to reboot the phone, I was in boot loader without a system ROM. so I installed the stock ROM and updated firmware. the phone now works. however, I lost su and my custom recovery. I tried to unlock the bootloader , reinstall Viper, but neither will work it fails every time. I am experienced at following instructions on this website, but I lack the knowledge to know exactly what I am doing with each action.
Please help me get either su, custom recovery or the boot loader unlocked. I still have S-off and I am at a loss. Thank you!
Click to expand...
Click to collapse
... simply flash appropriate custom recovery from fastboot. boot into recovery and try to reboot from there and it will ask you if you want to root the device. root it. reboot normally and you will see SU app. open it and update binaries. thats it, you are rooted ...
Failure
Okay, so I appreciate the attention and help, but it fails to install recovery, flash roms, or unlock the bootloader from fastboot. I can flash firmware and run an RUU from my desktop. As well, I can run the Sprint OTA update from the phone, but I have not done that yet. I have hboot 1.55. I have tried to flash things from terminal emulator, but I'm having trouble. I can access and use the phone for Sprint, but the CID says 11111 and won't let me change carriers. Once again, I have S-off.
Thoughts:
Run Sprint update and try to start from scratch, if all else fails, sell it.
Can I flash SU from bootloader? I haven't tried that yet, although I doubt it will work given my other problems.
patrickgartner said:
Okay, so I appreciate the attention and help, but it fails to install recovery, flash roms, or unlock the bootloader from fastboot. I can flash firmware and run an RUU from my desktop. As well, I can run the Sprint OTA update from the phone, but I have not done that yet. I have hboot 1.55. I have tried to flash things from terminal emulator, but I'm having trouble. I can access and use the phone for Sprint, but the CID says 11111 and won't let me change carriers. Once again, I have S-off.
Thoughts:
Run Sprint update and try to start from scratch, if all else fails, sell it.
Can I flash SU from bootloader? I haven't tried that yet, although I doubt it will work given my other problems.
Click to expand...
Click to collapse
... slow down and calm down. i think you are hasting things. dont worry and do whatever you wanna do step by step. its not clear to me what you want to achieve, you wanna switch carriers ? want ota ? want custom rom ? you are s-off but cant flash recovery !!!! please explain exactly what you want and what errors are you getting and doing what
i think you cant have SU from bootloader and certainly terminal emulator doesnt flash recoveries and rom., fastboot does recovery and recovery flashes rom. dont play with your phone like this without proper knowledge. ask whatever doubts you have prior doing anything ...
Straight Talk
You're funny. Yes, I am in a hurry to use my new phone... Ultimately, I want to use it on straight talk. It is S-off, and the boot loader will not unlock, the phone won't flash a recovery and I have lost su. It's the weirdest thing! I haven't had this problem before. Usually you flash stock firmware and ruu and you're back at square one, but not this time.
I would pay you to visit my problem via Teamviewer? Interested?
-Patrick
patrickgartner said:
You're funny. Yes, I am in a hurry to use my new phone... Ultimately, I want to use it on straight talk. It is S-off, and the boot loader will not unlock, the phone won't flash a recovery and I have lost su. It's the weirdest thing! I haven't had this problem before. Usually you flash stock firmware and ruu and you're back at square one, but not this time.
I would pay you to visit my problem via Teamviewer? Interested?
-Patrick
Click to expand...
Click to collapse
... Dear if you wanna network unlock your phone, follow the steps exactly as described.
1. Flash this and only this RUU (first link - http://forum.xda-developers.com/showthread.php?t=2250904 ), no need to relock bootloader if unlocked as you are s-off.
2. Download the recovery for sprint variant and flash it in fastboot mode (fastboot flash recovery recovery.img) (link - http://forum.xda-developers.com/showthread.php?t=2651035).
3. Boot in to recovery and press reboot and then system, it will ask for your permission to root, root it. restart normally and open SU app and update its binaries. phone will reboot itself in recovery and back in normal mode. You will be rooted then. :victory:
then ping me for sim unlock ...
my htc m7 got bricked and stuck in a bootloop after two days of being OTA updated to lollipop, knowing that it's S-on and bootloader locked, now when i try to unlock it through HTCDEv everything goes well but when the phone reboots it would still be locked and won't enter recovery! and when trying to flash a stock firmware instead of rebooting to bootloader (fastboot oem rebootRUU) the phone would reboot to system and stuck in boot loop, any solution to flash the phone back to normal?
If you are using Clockwork Mod, then there should be a way to get back into the rom flash option. Go into your "Power/Volume Down" page, and look for the option to flash from zip. Find the zip you used when ORIGINALLY flashing to your custom rom. Do not try to go to stock at first, work your way backwards. If you can get back to the working custom rom, from there you can use on screen functions to repair the phone back to stock.
yakie47 said:
my htc m7 got bricked and stuck in a bootloop after two days of being OTA updated to lollipop, knowing that it's S-on and bootloader locked, now when i try to unlock it through HTCDEv everything goes well but when the phone reboots it would still be locked and won't enter recovery! and when trying to flash a stock firmware instead of rebooting to bootloader (fastboot oem rebootRUU) the phone would reboot to system and stuck in boot loop, any solution to flash the phone back to normal?
Click to expand...
Click to collapse
Looks like you are having firmware or hardware issue. We often see this problem (not being able to unlock the bootloader) when the phone was relocked with a custom recovery still installed. But it doesn't seem to be your case since your phone is s-on and locked unless you tell me that you did re-locked the bootloader with a custom recovery installed...
Unfortunately the only walk around for this issue is to flash the same version stock firmware.zip in ruu mode which is not accessible in your case.
Why you can't access the ruu mode, I really don't know, it might confirm an firmware issue, maybe with the bootloader. Your not the first one stuck in that situation (not unlockable + ruu mode broken), its not common but you are not the first.
Btw is your phone a GPE or Sense variant? GPE variant have a well known bug which will prevent the bootloader to be unlocked. Does not apply to Sense variants.
I'm afraid there is nothing to do if you can't unlock or access ruu mode. Maybe a jtag repair could work or you'll have to send it for repair.
Sorry
ethanvallivue said:
If you are using Clockwork Mod, then there should be a way to get back into the rom flash option.
Click to expand...
Click to collapse
OP said he was bootloader locked so he can't use a custom recovery.
Go into your "Power/Volume Down" page, and look for the option to flash from zip.
Click to expand...
Click to collapse
There is no such option for HTC devices. To flash stock zip on the M7 you must access RUU mode, OP said RUU mode is broken...
Find the zip you used when ORIGINALLY flashing to your custom rom. Do not try to go to stock at first, work your way backwards. If you can get back to the working custom rom, from there you can use on screen functions to repair the phone back to stock.
Click to expand...
Click to collapse
Don't understand why you are talking about custom roms, did you read the OP?
I appreciate your responds guys and i believe the only option left is the jtag i guess..
Hello team,
I had 4.03 with unlocked BL and TWRP installed. I reinstalled the stock N recovery first. When I use the command "fastboot oem lock" it ask me to say yes and I do, it reboots and flashes the white symbol and reboots, stuck in this bootloop. Anybody seen this before or have a fix? I am trying to restore to stock to sell.
thanks,
Nope I didn't have an issue like you. 2 attempt of going back to stock and never had an issue. Did you successfully flash the stock recovery?
Just use the unbrick meathod it resets everything
kingheri1 said:
Nope I didn't have an issue like you. 2 attempt of going back to stock and never had an issue. Did you successfully flash the stock recovery?
Click to expand...
Click to collapse
Yes- I did flash the stock recovery. But when I do the "fastboot oem lock" it just boot loops- any ideas?
aaronc_98 said:
Hello team,
I had 4.03 with unlocked BL and TWRP installed. I reinstalled the stock N recovery first. When I use the command "fastboot oem lock" it ask me to say yes and I do, it reboots and flashes the white symbol and reboots, stuck in this bootloop. Anybody seen this before or have a fix? I am trying to restore to stock to sell.
thanks,
Click to expand...
Click to collapse
You should never lock the bootloader with non stock recovery or boot image. The security in newer devices is a lot meaner.
There are two ways you can resolve this:
Method 1:
You'll need to unlock the bootloader first. Try getting into fastboot and run "fastboot oem unlock".
If it allows unlocking you're done, just flash everything stock (first the recovery and then OOS 4.0.3 via the ADB option in the recovery). Then, go to fastboot and relock the bootloader. Should work since it worked many times for me.
Method 2:
If it doesn't allow and you're in TWRP you can't do any flashing since the locked bootloader won't allow TWRP to boot.
In this case, contact OnePlus Support via Live Chat and tell them you got a software issue with your phone.
They'll give you links to three files needed for flashing the device. Download those and let them know. They'll flash your device via remote support within a week. No matter what S/W state it is in.
Hope it helps