Related
Ok here is the deal
I had untouched HTC One
I flashed http://forum.xda-developers.com/showthread.php?t=2182823 according to guides. Then my wifi and storages stoped working.
So I tried flashing a custom rom: got boot unlocked, got custom recovery, flashed a rom, and it wouldnt boot: the HTC logo on white background and wont go past it, left it all night.
Then i though i'll just go to stock rom before the update. Now i have this:
S-on with hboot 1.54 so i cant get s-off, os 2.24.401.1 that wont boot, and relocked hboot.
Any ideas?
IBeastI said:
Ok here is the deal
I had untouched HTC One
I flashed http://forum.xda-developers.com/showthread.php?t=2182823 according to guides. Then my wifi and storages stoped working.
So I tried flashing a custom rom: got boot unlocked, got custom recovery, flashed a rom, and it wouldnt boot: the HTC logo on white background and wont go past it, left it all night.
Then i though i'll just go to stock rom before the update. Now i have this:
S-on with hboot 1.54 so i cant get s-off, os 2.24.401.1 that wont boot, and relocked hboot.
Any ideas?
Click to expand...
Click to collapse
first unlock your bootloader again through fastboot.
can you access your custom recovery? if yes, "adb sideload" one of mike's stockroms through recovery. guide: http://forum.xda-developers.com/showthread.php?t=2317986
then it should work again
Hi,
My camera had problems focusing so I tried flashing the GPE ROM in hope of it would fix my camera - no luck. Now I need to get it back for repair so I need to get it back to complete stock.
Got my bootloader relocked, and i'm back on the 4.2.2 stock sense 5 ROM since I did a nandroid backup before flashing the GPE ROM. The only problem is now that i'm rooted and have hboot 1.54 with S-on so I cannot run any RUU's.
Is it possible to unroot it and get the stock recovery ?
My version is:
Baseband 4A.17.3250.14
Version 2.24.401.1
Flash the Mike1986's stock rom, and the stock recovery, after relock your bootloader and you will be stock
carljoe said:
Hi,
My camera had problems focusing so I tried flashing the GPE ROM in hope of it would fix my camera - no luck. Now I need to get it back for repair so I need to get it back to complete stock.
Got my bootloader relocked, and i'm back on the 4.2.2 stock sense 5 ROM since I did a nandroid backup before flashing the GPE ROM. The only problem is now that i'm rooted and have hboot 1.54 with S-on so I cannot run any RUU's.
Is it possible to unroot it and get the stock recovery ?
My version is:
Baseband 4A.17.3250.14
Version 2.24.401.1
Click to expand...
Click to collapse
If you flashed the stock ROM you're not rooted.
The problem is probably that you're relocked, with no way of becoming locked.
The best you can do is HTCDev unlock and install stock recovery, then relock again and hope that's close enough.
Or wait for S-OFF on 1.54 or, if you really are "locked" vs "relocked", find or wait for the 2.24.401 RUU.
BenPope said:
If you flashed the stock ROM you're not rooted.
The problem is probably that you're relocked, with no way of becoming locked.
The best you can do is HTCDev unlock and install stock recovery, then relock again and hope that's close enough.
Or wait for S-OFF on 1.54 or, if you really are "locked" vs "relocked", find or wait for the 2.24.401 RUU.
Click to expand...
Click to collapse
you are right, just checked with root checker and I am not rooted. But how do I know which recovery I am running? As of right now nothing happens when I try to enter the recovery in bootloader. I guess it is becaused I just relocked the bootloader?
carljoe said:
you are right, just checked with root checker and I am not rooted. But how do I know which recovery I am running? As of right now nothing happens when I try to enter the recovery in bootloader. I guess it is becaused it is relocked now ?
Click to expand...
Click to collapse
Not sure how to check which recovery. Normally a nandroid has the custom recovery, unless you fastboot boot recovery.img with it stock (which you should, but is usually left out of the guides).
However, somewhere it will say "tampered" (hboot?) if you have unsigned software installed. If it doesn't say tampered, you have stock stuff.
BenPope said:
Not sure how to check which recovery. Normally a nandroid has the custom recovery, unless you fastboot boot recovery.img with it stock (which you should, but is usually left out of the guides).
However, somewhere it will say "tampered" (hboot?) if you have unsigned software installed. If it doesn't say tampered, you have stock stuff.
Click to expand...
Click to collapse
It says tampered and as far as I can understand from other threads, it will keep saying that no matter what I do.
But I didnt fastboot any recovery image, just restored the nandroid backup in my custom recovery.
So I guess I have to unlock the bootloader and flash the stock recovery.
Thank you for your explanations
carljoe said:
It says tampered and as far as I can understand from other threads, it will keep saying that no matter what I do.
But I didnt fastboot any recovery image, just restored the nandroid backup in my custom recovery.
So I guess I have to unlock the bootloader and flash the stock recovery.
Thank you for your explanations
Click to expand...
Click to collapse
I'm pretty sure tampered goes away when all the partitions have signed software, but I'm open to correction. Where does it say that?
Nah, the fastboot boot is the first step after unlocking, before you flash custom recovery, you should boot it and then nandroid and then flash custom recovery and ROM or root. That way your nandroid is actual stock.
Anyway yeah, unlock, flash stock, relock (unless you're "locked" vs "relocked") should be fine.
You can only remove the tampered flag when you are S-Off, obviously not an option at the moment on Hboot 1.54 .. Same goes for changing the relocked back to locked, S-Off needed. As Guich said, check mike1986's threads as he has the stock recovery image to install using fastboot.
When you did your Nandroid backup, did you check to backup recovery? if not you will need to install it again using the command "fastboot flash recovery recovery.img"
im a HTC one user. Currently on a formatted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
ayeyokp said:
im a HTC one user. Currently on a formatted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
Click to expand...
Click to collapse
Flash stock recovery, then run it to flash stock.
ayeyokp said:
im a HTC one user. Currently on Renoir atted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
Click to expand...
Click to collapse
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Click to expand...
Click to collapse
He's on 1.54, he can't go s-off.
OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
Click to expand...
Click to collapse
i have a unlocked bootloader. and i have a s-off too! i achieved s-off through revone only!
OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
Click to expand...
Click to collapse
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
i know that with supercid you can flash any RUU beacuse it bypasses the normal country control during the istallation of the program...
now, i don't know if you cant flash anything with the 1.54 hboot, but i dont think so. according to me, you can try to flash and in the worst case the istallation wont start...but obviously is your phone and your decisone, just as it is your responsability
ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
Since you're S-Off and SuperCID you can flash any RUU, so just go ahead and you won't loose S-Off either.
The 1.54 restrictions only apply if you're not S-Off, because S-On won't allow you to downgrade. Since you're S-Off it will allow the RUU downgrade.
ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
Being s-off means you can flash anything, even stuff not for this phone. So be careful.
Ruu.exe for Asia
http://www.androidruu.com/getdownlo...50.13_10.33.1150.01_release_311678_signed.exe
Or Europe
http://www.androidruu.com/getdownlo...31.27_10.31.1131.05_release_310878_signed.exe
Download the Ruu of your choice to your pc.
Connect phone via usb2 to pc with phone in fastboot usb mode
Run ruu you downloaded , answer questions as appropriate
Approximately ten minutes to have stock Rom and stock recovery
Will retain s off . Can accept ota updates without losing s off
Sent from my HTC One using xda app-developers app
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.
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..