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] Stuck on boot after KK update

This is for my friend's ATT One. Bone stock, unrooted, S-On, no changes made to the device from the store. He took the OTA for Kit Kat and was running fine, then his phone rebooted on him a couple days later and won't go past the white HTC boot screen.
Two problems: First, I cannot use ADB, as it does not detect his phone. When I plug in his phone, it says drivers failed to install for HTC MTP device. I also have an HTC One, unlocked, S-Off, etc., and when I plug mine in, it's detected and ADB works just fine like always (so it's not that I need to reinstall drivers).
Problem 2: the phone seems to hang trying to do a factory reset from the bootloader menu, or from the stock recovery menu. It will start the reset, reboot to the white HTC screen then hang. I left it for more than an hour twice. Nothing doing.
Is there a way to reflash/restore his phone without wiping his sdcard? He's OK losing the data partition, but wiping sdcard is last resort. Using an RUU .exe will wipe his sdcard, as will unlocking his bootloader to try to install a custom recovery. Just not really sure what tools I have at my disposal with a stock recovery and no adb. Will fastboot flashing a rom.zip extracted from the ATT RUU also wipe his sdcard? Or does that only happen with the RUU .exe? Any ideas appreciated..

Shott3r said:
This is for my friend's ATT One. Bone stock, unrooted, S-On, no changes made to the device from the store. He took the OTA for Kit Kat and was running fine, then his phone rebooted on him a couple days later and won't go past the white HTC boot screen.
Click to expand...
Click to collapse
Did you tried wiping /cache?
Shott3r said:
Two problems: First, I cannot use ADB, as it does not detect his phone.
Click to expand...
Click to collapse
ADB can only be used when phone is booted+usb debug on or via custom recovery
Shott3r said:
He's OK losing the data partition
Click to expand...
Click to collapse
I hope so, factory reset is a /data wipe... probably already wiped from your first attempt to factory reset
Shott3r said:
but wiping sdcard is last resort. Using an RUU .exe will wipe his sdcard
Click to expand...
Click to collapse
And the available ruu.exe for at&t is a downgrade in version so it will require s-off.
Shott3r said:
Will fastboot flashing a rom.zip extracted from the ATT RUU also wipe his sdcard? Or does that only happen with the RUU .exe? Any ideas appreciated..
Click to expand...
Click to collapse
you can't flash a rom directly from fastboot. You can flash a rom via a custom recovery or flash a ruu.zip from RUUmode (fastboot oem rebootRUU).
Unfortunately I think there is no way to save /sdcard. You will need to unlock bootloader to flash a custom recovery.
easy way:
flash twrp custom recovery
flash guru reset rom for your version
or
flash twrp custom recovery
flash and use arhd rom
or the long way:
flash twrp
flash arhd
s-off
flash ruu.zip

alray said:
Did you tried wiping /cache?
...
you can't flash a rom directly from fastboot. You can flash a rom via a custom recovery or flash a ruu.zip from RUUmode (fastboot oem rebootRUU).
Unfortunately I think there is no way to save /sdcard. You will need to unlock bootloader to flash a custom recovery.
...
Click to expand...
Click to collapse
I did erase cache first thing. Regarding flashing the ruu.zip from RUUmode, my question is whether flashing the ruu.zip will erase the sdcard? Also does it even matter, since he has KK firmware, and is S-On? Will the ruu.zip from Jellybean 4.3 even flash on his (current) KK firmware?
Any ideas on why the factory reset would hang? Cuz that's best case scenario is to simply factory reset, but it seems not to work presently.

Shott3r said:
I did erase cache first thing. Regarding flashing the ruu.zip from RUUmode, my question is whether flashing the ruu.zip will erase the sdcard? Also does it even matter, since he has KK firmware, and is S-On? Will the ruu.zip from Jellybean 4.3 even flash on his (current) KK firmware?
Any ideas on why the factory reset would hang? Cuz that's best case scenario is to simply factory reset, but it seems not to work presently.
Click to expand...
Click to collapse
ruu will wipe everything.
and no you can't use ruu with s-on because its a downgrade in version.

Is there any way that you know of to get access to the sdcard in the circumstance I've described to try to rescue some files before I set about with the rescue? Doubt it, but just asking.

Shott3r said:
Is there any way that you know of to get access to the sdcard in the circumstance I've described to try to rescue some files before I set about with the rescue? Doubt it, but just asking.
Click to expand...
Click to collapse
maybe you could use remote recovery booting (booting a custom recovery without installing it). Not sure if it still can be done (think it was disabled in 4.2.2)
fastboot boot name_of_recovery.img
then use adb from recovery to copy sdcard content to your computer
adb pull /sdcard C:\somefolder
If you can't boot from a remote recovery, then I think you can say goodbye to those files in your /sdcard

updated from hboot 1.55 to 1.57, now boot looping

As thread says, now boot looping. Did fastboot reboot at the end of the upgrade and phone tried to reboot then stayed off.
Trying to go into recovery but that blacks out for me as well.
saw this thread pop up in the "similar threads" field as i was creating this post so guess i should give it a go? http://forum.xda-developers.com/showthread.php?t=1936852
basically says to just reinstall a custom recovery and flash a new rom and i'm all set (i think).
you need unlock device again and flash custom recovery
1)Unlock your device
2)flash custom recovery
3)flash rom
Click to expand...
Click to collapse
If that's the case my phone still says i'm unlocked. So yeah, not sure what to do here. Thanks in advance for any help.

My guess is the new kernel/boot.img is not compatible with the rom you are running.
1. You could try a dirty flash of your current rom.(don't wipe anything just flash the rom)
2. Flash a 5.03.651.3 stock rooted rom.
3. Restore a good backup.
4. Run the 5.03.651.3 RUU and start fresh.

BD619 said:
My guess is the new kernel/boot.img is not compatible with the rom you are running.
1. You could try a dirty flash of your current rom.(don't wipe anything just flash the rom)
2. Flash a 5.03.651.3 stock rooted rom.
3. Restore a good backup.
4. Run the 5.03.651.3 RUU and start fresh.
Click to expand...
Click to collapse
Hi, yeah i see.
I went ahead and flashed a TWRP recovery i had labeled as safe and managed to get back into recovery. I'm now on one of my original stock backups which i set right before i went into custom rom mode. So got some functionality back at least.
I will now attempt the RUU process. Please correct me if i'm wrong, but after i complete it, i have to root my phone again? And s-off shouldn't change?

Since you are s-off you don't need to re-lock your bootloader, so all you should need to do after the RUU is re-flash twrp,flash SuperSU if you are going to stay stock rooted or flash a custom rom and you should be good to go.

BD619 said:
Since you are s-off you don't need to re-lock your bootloader, so all you should need to do after the RUU is re-flash twrp,flash SuperSU if you are going to stay stock rooted or flash a custom rom and you should be good to go.
Click to expand...
Click to collapse
awesome, you are the best
thanks again for your help, i would have been in some kind of misery without it lol.

nickhx2 said:
awesome, you are the best
thanks again for your help, i would have been in some kind of misery without it lol.
Click to expand...
Click to collapse
No worries good luck

[Q] help with reverting to stock/updating firmware

Hey everyone,
I have looked everywhere but havent found a way to return to stock. I simply want to return to stock so that i can update my firmware. My details are as follows:
S-ON
Hboot: 1.56
OS-4.19.401.11
my bootloader is unlocked, obviously
I just need someone to direct me in the correct path.
Ive searched a lot but havent gotten far,please, I appreciate any help i can get from.
Thanks

beschier12 said:
Hey everyone,
I have looked everywhere but havent found a way to return to stock. I simply want to return to stock so that i can update my firmware. My details are as follows:
S-ON
Hboot: 1.56
OS-4.19.401.11
my bootloader is unlocked, obviously
I just need someone to direct me in the correct path.
Ive searched a lot but havent gotten far,please, I appreciate any help i can get from.
Thanks
Click to expand...
Click to collapse
You can follow nkk71's guide in my signature.
If you don't want to go completely back to stock just to get OTA you can flash this Guru Reset 4.19.401.11 in TWRP. In Aroma just select stock recovery and radio, when you reboot you will have stock recovery, stock rom. To get the OTA updates, you will have to relock your bootloader. You can use this command in bootloader/FASTBOOT USB:
Code:
fastboot oem lock

majmoz said:
You can follow nkk71's guide in my signature.
If you don't want to go completely back to stock just to get OTA you can flash this Guru Reset 4.19.401.11 in TWRP. In Aroma just select stock recovery and radio, when you reboot you will have stock recovery, stock rom. To get the OTA updates, you will have to relock your bootloader. You can use this command in bootloader/FASTBOOT USB:
Code:
fastboot oem lock
Click to expand...
Click to collapse
Thank you so much! i searched a lot for my versions reset tool. Just one last question. When i update my firmware and OS now and make a nandroid backup, will that nandroid help me revert back to stock after i have rooted my phone again?

beschier12 said:
Thank you so much! i searched a lot for my versions reset tool. Just one last question. When i update my firmware and OS now and make a nandroid backup, will that nandroid help me revert back to stock after i have rooted my phone again?
Click to expand...
Click to collapse
Yes, it will make it a little easier. You will need to make the nandroid backup the first thing when you boot into recovery the first time before you root the phone. Save it to your computer for future use. If you are able to get the stock recovery from the firmware you can use it with your nandroid backup to get you close to stock. You would flash the stock recovery with the same commands as you flashed the custom recovery.

majmoz said:
Yes, it will make it a little easier. You will need to make the nandroid backup the first thing when you boot into recovery the first time before you root the phone. Save it to your computer for future use. If you are able to get the stock recovery from the firmware you can use it with your nandroid backup to get you close to stock. You would flash the stock recovery with the same commands as you flashed the custom recovery.
Click to expand...
Click to collapse
Awesome! Thanks again!

Unroot, relock and remove recovery from HTC One m7 International

Hey,
I wanted to download the OTAs to my phone, and the update goes directly to recovery. I think I have removed root from my device by using the full unroot option of SuperSu after which I factory reset my phone.
How to remove recovery and basically download and update the OTAs?
Cheers!

DragonWinx said:
Hey,
I wanted to download the OTAs to my phone, and the update goes directly to recovery. I think I have removed root from my device by using the full unroot option of SuperSu after which I factory reset my phone.
How to remove recovery and basically download and update the OTAs?
Cheers!
Click to expand...
Click to collapse
It may depend on the current phone OS. With Lolipop you will likely have to RUU the phone, with KitKat you may get away with just flashing stock recovery.
First you will need to post output from "fastboot getvar all" so folks here can help.

Use aroma recovery it will back you to stock recovery , then relock your phone after that you can install ota updates .