Database Develop

Unroot Hboot 1.54 S-on

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"

[Q] Help me unbrick my htc one please?

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

HTC one Kinda dead (I think) (resolved)

hey. I updated the recovery on one of my htc ones. after the fastboot flash command completed i booted into recovery but the recovery splash screen just comes up and then the phone reboots... Tried a few other but it is the same. The phone wont boot either.. So basically im stuck in the bootloader with a hboot 1.44, cid, is on VODAP001 its never had s-off and I cant find a voda ruu with a high enough hboot to flash!! any ideas anyone?
Edit: Must of been something on the internal emulated sd.. i locked the bootloader, unlocked, installed official recovery them clockwork mod and its booting to the recovery menu.. now how to I explaint o the gf ive just wiped all of her photos off the phone

Am out of ideas

I have an htc one m7, i tried installing arhd today , after flashing it through twrp phone wont boot pass htc one. Now am stuck, i have s-on and i have unlocked bootloader, now i dont know how to get my phone to boot up, my cid is htc_039 and i cant find any ruu for it and my sideload dosent work via recovery because my internal memory can not be mounted, i have tried with twrp, cwm and even philz recovery and still no lock with sideload. Now i can only boot into recovery and bootloader. What do i do

indigold said:
I have an htc one m7, i tried installing arhd today , after flashing it through twrp phone wont boot pass htc one. Now am stuck, i have s-on and i have unlocked bootloader, now i dont know how to get my phone to boot up, my cid is htc_039 and i cant find any ruu for it and my sideload dosent work via recovery because my internal memory can not be mounted, i have tried with twrp, cwm and even philz recovery and still no lock with sideload. Now i can only boot into recovery and bootloader. What do i do
Click to expand...
Click to collapse
check the Frequently Asked Question sticky page 3

Flash TWRP 2.6.3.3 and then flash ARHD again.
Then let it restart. Remember the first boot can take a while....sometimes 5 minutes sometimes 10. Just wait patiently.

Continually booting into bootloader

My HTC One m7 was unlocked with s-off and had the android revolution hd 90.1 custom rom and twrp 2.8 . I adb sideloaded the guru_bootloader_reset_1.0 and removed the tampered warning and locked the bootloader. I then decided to go to s-on and it now just continually boots into bootloader. Such a long time time since I used it, am I right that 1 needed to leave the s-off as off for the android revolution rom to work? it won't boot into recovery and when I go into cmd and do adb devices nothing is showing as connected. Any ideas?

repoman_1966 said:
My HTC One m7 was unlocked with s-off and had the android revolution hd 90.1 custom rom and twrp 2.8 . I adb sideloaded the guru_bootloader_reset_1.0 and removed the tampered warning and locked the bootloader. I then decided to go to s-on and it now just continually boots into bootloader. Such a long time time since I used it, am I right that 1 needed to leave the s-off as off for the android revolution rom to work? it won't boot into recovery and when I go into cmd and do adb devices nothing is showing as connected. Any ideas?
Click to expand...
Click to collapse
When s-on you need at least an unlocked bootloader to boot custom software.
Only fastboot commands are working from bootloader
Btw going back s-on was a really bad idea. Now you'll need to unlock your bootloader so your phone can boot back to ARHD (you'll lose all your data) or flash a ruu (you'll lose all data).