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..
Related
so i just installed the factory 2.3.3 gingerbread OTA update onto my nexus one witch was one click rooted locked bootloader and it downloaded and installed fine but now i want to root again most likely unlock bootloader way but i cant get into recovery now ? i boot into bootloader mode (hold trackball while turn on phone ) i hit bootloader then recovery and i get the damn green android with the exclamation mark??? anyone no why i cant get into recovery i searched for last hour cant find .......
nexus one not rooted
locked bootloader
OTA gingerbread 2.3.3
s-on
hboot-0.35.0017
AMOLED screen
radio - 5.08.00.04
drawde40599 said:
so i just installed the factory 2.3.3 gingerbread OTA update onto my nexus one witch was one click rooted locked bootloader and it downloaded and installed fine but now i want to root again most likely unlock bootloader way but i cant get into recovery now ? i boot into bootloader mode (hold trackball while turn on phone ) i hit bootloader then recovery and i get the damn green android with the exclamation mark??? anyone no why i cant get into recovery i searched for last hour cant find .......
nexus one not rooted
locked bootloader
OTA gingerbread 2.3.3
s-on
hboot-0.35.0017
AMOLED screen
radio - 5.08.00.04
Click to expand...
Click to collapse
Use fastboot to re-flash recovery img
lcchan1 said:
Use fastboot to re-flash recovery img
Click to expand...
Click to collapse
how exactly do i do that ? fastboot not detecting my device and i thought i read somewhere its because ( S-on ) ?
drawde40599 said:
how exactly do i do that ? fastboot not detecting my device and i thought i read somewhere its because ( S-on ) ?
Click to expand...
Click to collapse
download clockwork recovery from the app store.
Flash its recovery, then boot into recovery after a successful flash.
Out of curiosity, why did you install a non-rooted version of 2.3.3.?
You can get into recovery... what you're seeing is the front of the stock one. Hold volume+ and hit power.
The only way to get root on 2.3.3 currently is to unlock the bootloader and use fastboot. Being S-ON is nothing to do with it, 99% of N1s are.
Rusty! said:
You can get into recovery... what you're seeing is the front of the stock one. Hold volume+ and hit power.
The only way to get root on 2.3.3 currently is to unlock the bootloader and use fastboot. Being S-ON is nothing to do with it, 99% of N1s are.
Click to expand...
Click to collapse
HELL YA !! thank u much
Thread moved to Q&A, a sub-forum dedicated exclusively for questions like these. Please post all further questions here. Do not post new question threads in development, as you are not doing any even remotely related to Android development. That said, I'm glad you were able to figure out your issue.
Downloading clockworkmod will not work. He is not rooted so he can't flash the recovery with it.
Sent from my Nexus One using XDA App
This happened to me 2 days ago (word by word)!!
From Amon Recovery's page, this is what the problem is:
"Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android). More info on this here"
Here: http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638
My problem was even more complicated because I tried flashing froyo without a wipe so my phone started going into boot loop!
Thanks to danger-rat's reply, I was able to get into recovery at least once and then everything came back under control. He said "Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to..."
Here's my thread:
http://forum.xda-developers.com/showthread.php?t=980577
edit: I just realized that you are not able to fastboot either? I was able fastboot and flash recovery onto my phone and then without turning the phone off - I was able to go into recovery straight after flashing amon_recovery.img
passimg back to an earlier version of Android, root, then install a pre-rooted GB...
If you get the "main version is older" error, you're out of luck and your only option is to unlock the bootloader or wait for a new method to be found...
Sent from my Nexus One using XDA App
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.
Can someone help? I have HTC vivid which was rooted and had cwm recovery,I try to update
Butt I can because after installing the ice hboot I try to install cwm recovery to get the stock
Recovery but nothing.I enter the hboot but when I go to recovery the phone it shows a icon like
Hd drive and it is restarting after 30 to 40 second .I reflashed the the file but nothing.the phone
Is locked and very strange it does not show locked but relocked.I do not want to flash the ruu
Directly because I had costum recovery and I do not want to brick my phone.so can someone help?
Please.
The phone is an att USA phone.
dhionisis said:
Can someone help? I have HTC vivid which was rooted and had cwm recovery,I try to update
Butt I can because after installing the ice hboot I try to install cwm recovery to get the stock
Recovery but nothing.I enter the hboot but when I go to recovery the phone it shows a icon like
Hd drive and it is restarting after 30 to 40 second .I reflashed the the file but nothing.the phone
Is locked and very strange it does not show locked but relocked.I do not want to flash the ruu
Directly because I had costum recovery and I do not want to brick my phone.so can someone help?
Please.
The phone is an att USA phone.
Click to expand...
Click to collapse
If you are relocked you will have to unlock again to flash a custom recovery, kernel, and rom. Also, this should have been posted in the general thread.
stock rom
No I am looking to flash the att stock room no costum rom or recovery.I want the stock
Recovery and stock att ics rom.and when I try to unlock
The phone get stock I select yes and press the power button butt nothing happens
The phone freeze and does not respond no matter what I do.so I have
To remove the battery and insert again to start the phone and it only
Goes to hboot.
Did you relock your bootloader by HTCdev before attempting any of this? If not, then all you have to do is boot into fastboot and input the command:
fastboot oem relock
Afterwards just run the RUU.
Dev's move this to general... wrong section buddy next time put it in the General area not development
And cruzin_cruzing's post should help you
stock rom
The phone is locked and I flash ruu butt now I have more serious problem.
The phone is stock at HTC logo with triangle on each corner.I try to.
Reflash nothing it goes up to 34% and it get stock there.
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?!?
I have an AT&T HTC One that was converted a Developer Edition, so it is S-OFF and has an unlocked bootloader, otherwise it is running completely stock non-rooted Lollipop firmware. I want to flash a custom recovery, but the safer side of my mind always tests it by doing "fastboot boot recovery.img" first before flashing it. The problem is on this phone it will load, I can see the green bar on the side of the Hboot screen go up, and fastboot says it sent the file successfully, but it just locks up and does nothing, I have to long-press power for 15 seconds or so to get it to shutdown to get it to respond again.
I have tried several versions of TWRP from here: http://techerrata.com/browse/twrp2/m7 and all have the same results. I am very familiar with using fastboot and adb, so I don't think I am doing anything wrong, but I am scared to flash the recovery image if I can't boot it.
Any ideas?
acejavelin said:
I have an AT&T HTC One that was converted a Developer Edition, so it is S-OFF and has an unlocked bootloader, otherwise it is running completely stock non-rooted Lollipop firmware. I want to flash a custom recovery, but the safer side of my mind always tests it by doing "fastboot boot recovery.img" first before flashing it. The problem is on this phone it will load, I can see the green bar on the side of the Hboot screen go up, and fastboot says it sent the file successfully, but it just locks up and does nothing, I have to long-press power for 15 seconds or so to get it to shutdown to get it to respond again.
I have tried several versions of TWRP from here: http://techerrata.com/browse/twrp2/m7 and all have the same results. I am very familiar with using fastboot and adb, so I don't think I am doing anything wrong, but I am scared to flash the recovery image if I can't boot it.
Any ideas?
Click to expand...
Click to collapse
Only hboot 1.44 will boot recovery .. all the others need to be flashed
TWRP 2.6.3.3 is the most stable
TWRP 2.8.4.0 is what I use with no problems
clsA said:
Only hboot 1.44 will boot recovery .. all the others need to be flashed
Click to expand...
Click to collapse
OK, that makes sense then... I am on 1.61 I think, and when I got it it was on 1.5 something.
Seems odd that being S-off and unlocked prevents fastboot booting to occur... wonder why?
acejavelin said:
OK, that makes sense then... I am on 1.61 I think, and when I got it it was on 1.5 something.
Seems odd that being S-off and unlocked prevents fastboot booting to occur... wonder why?
Click to expand...
Click to collapse
it was patched in the hboot to not allow it
clsA said:
it was patched in the hboot to not allow it
Click to expand...
Click to collapse
I guess I can see why they would do that, sort of, not that I agree... On my old HTC Rezound you could boot recovery and backup, wipe caches, etc, as long as you didn't write to boot/system/etc, without triggering the TAMPERED flag, you had to flash recovery or write to a system partition in order to set that flag. Oh well, Ill flash it up soon and play with it. I am actually kind of liking the stock lollipop Sense ROM, might just leave it like that for a bit though. Just came back from the range and had a little time before work so I was playing with it and it kind of frustrated me.
Thanks for your help and info.