Database Develop

Backing up stock firmware

Hello ! I have an Htc One m7 sim unlocked but Vodafone Romania branded. i tried revone and it does the job very well (s off, unlock bootloader) and i want to backup my firmware because i can' t find ruu for romanian vodafone branded. Cidgetter reports htc_032 , and maincid htc_001. I searched but besides nandroid backup , there is nothing else. Any advise, i would like to be sure that i can rever back to delivered version

alekz2604 said:
Hello ! I have an Htc One m7 sim unlocked but Vodafone Romania branded. i tried revone and it does the job very well (s off, unlock bootloader) and i want to backup my firmware because i can' t find ruu for romanian vodafone branded. Cidgetter reports htc_032 , and maincid htc_001. I searched but besides nandroid backup , there is nothing else. Any advise, i would like to be sure that i can rever back to delivered version
Click to expand...
Click to collapse
go into fastboot and instead of flashing a custom recovery, merely boot it.
Put the custom recovery in the same folder as adb, and then boot your phone into bootloader by pressing volume down and power when booting up. Plug it into the computer and it should say "fastboot usb" on the screen in red. Then type "fastboot boot recovery.img", replacing recovery with whatever yours is called. Then, just do a nandroid backup, and you have a backup of a completely stock htc one. if you ever need to revert, go back into recovery and restore using that nandroid. IF, for some reason, once you restore and you still have a custom recovery (happened to me), merely open your nandroid, remove the recovery image, place it in the adb folder, and type "fastboot flash recovery recovery.img" in the bootloader and youre good.
Just remember that you can remove the tampered and unlocked flags using revone, but s-off is permanent (i believe).

First of all thank you for the reply.
I tried revone with my stock phone and it dit s-off , bootloader unlock and then i locked bootloare ( locked not relocked) and s-on back
My big question is where i would get my stock recovery to flash it back in case of warranty claim. I understand that once i flash a custom recovery to make a nandroid backup, i overwrite the stock recovery
my mistake...i tried with your comand and i got "booting.... failed (remote not allowed)
2ND edit
after I did s-off and unlocked the bootloader I could boot the recovery, now it's backing up..THANK YOU

alekz2604 said:
First of all thank you for the reply.
I tried revone with my stock phone and it dit s-off , bootloader unlock and then i locked bootloare ( locked not relocked) and s-on back
My big question is where i would get my stock recovery to flash it back in case of warranty claim. I understand that once i flash a custom recovery to make a nandroid backup, i overwrite the stock recovery
my mistake...i tried with your comand and i got "booting.... failed (remote not allowed)
2ND edit
after I did s-off and unlocked the bootloader I could boot the recovery, now it's backing up..THANK YOU
Click to expand...
Click to collapse
ahahaha no problem . Now once that nandroid is done, its a COMPLETE backup of your stock phone, so when you need it, restore that nandroid from recovery. I tried this once, and for some reason, i still had custom recovery after restoring the nandroid, but this can be easily solved by what i said in the last post, just take the recovery out of the nandroid, and flash it in bootloader.

alekz2604 said:
First of all thank you for the reply.
I tried revone with my stock phone and it dit s-off , bootloader unlock and then i locked bootloare ( locked not relocked) and s-on back
My big question is where i would get my stock recovery to flash it back in case of warranty claim. I understand that once i flash a custom recovery to make a nandroid backup, i overwrite the stock recovery
my mistake...i tried with your comand and i got "booting.... failed (remote not allowed)
2ND edit
after I did s-off and unlocked the bootloader I could boot the recovery, now it's backing up..THANK YOU
Click to expand...
Click to collapse
Alternatively you could point out your version-main from fastboot getvar and someone would post you a link for suitable stock recovery flashable image.

It works, first i did s-off and bootloader unlock then i booted with twrp recovery, made a backup of all that i could select. After this i put supercid and flashed europe unbranded, afterwards i reboot with twrp recovery and i restored the backup and all went back to default. After that i did s-on and locked the bootloader.
Thank you for your help

alekz2604 said:
It works, first i did s-off and bootloader unlock then i booted with twrp recovery, made a backup of all that i could select. After this i put supercid and flashed europe unbranded, afterwards i reboot with twrp recovery and i restored the backup and all went back to default. After that i did s-on and locked the bootloader.
Thank you for your help
Click to expand...
Click to collapse
nooo problem

[GUIDE] Returning to 100% Stock for O2-UK Customers

Hi All,
I have merely followed the instructions of other devs here to get my phone back to complete stock O2. I believe this guide could work for other carrier based models as well
Mods - Feel free to post this wherever or make any changes.
These are the steps I took to get back to S-ON, reset the ***TAMPERED*** flag and lock the bootloader. The reason why I post this is because I had several issues getting back to stock, and this is for anyone who is having the same issues
I had several scary messages when going back to S-ON when I thought I was completely stock, which included the "Security Warning" message in bootloader when running fastboot oem writesecureflag 3. I also had a message when booting up the stock ROM in 3.62.206.1 saying "TAMPER DETECTED - REBOOTING after trying fastboot oem writesecureflag 3. Once in bootloader, the tampered message re-appeared and I was S-ON and LOCKED. After running all the steps, I have been able to reboot several times and factory reset without the ***TAMPERED*** reappearing
Step 1: Getting S-off
If you are using bootloader 1.44 - Use Revone http://forum.xda-developers.com/showthread.php?t=2314582
For bootloaders 1.5x you should download the Sunshine app at http://theroot.ninja/
The closer you are to stock ROM/stock kernel the better. To S-off it will cost you a mere $25, but it works in 5 mins and no need for computers/adb commands
Step 2: Remove ***TAMPERED***
After getting S-OFF, reset the ***TAMPERED*** flag and lock the bootloader using the following commands from these posts http://forum.xda-developers.com/showthread.php?p=46183050#post46183050 and http://forum.xda-developers.com/showthread.php?t=2477792 (credit to scotty1223)
To LOCK the Bootloader
To LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
Click to expand...
Click to collapse
To reset the TAMPER in bootloader
Enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
Click to expand...
Click to collapse
Step 3: Downgrade your Hboot to 1.44
Download the Hboot 1.44 from http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
Before flashing, The android-info.txt file needs modified by clicking into the file (not extracting it) and changing the model ID to whatever your model is. This can be checked by running the command fastboot getvar all and checking the model ID number
Now flash the Hboot. To do this, boot to bootloader screen using the command adb reboot-bootloader
Type the following commands:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
After it finishes, execute the command again to complete the flash:
fastboot flash zip 1.29.401.12_hboot_1.44.zip
Fastboot reboot
Step 4: Run an earlier RUU from 1.29.xxx.xx
We need to run and earlier RUU first. For now, change CID to HTC__032
Download RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed from thanks to crushalot, http://d-h.st/Gt8. This will reset the phone back to complete stock, but not stock for the original CID O2___001. Once the RUU installs, reboot into bootloader and run the following command
fastboot oem writecid O2___001.
Check your bootloader and you should see the phone is still S-OFF and the CID is now for O2.
Step 5: Getting S-OFF again
This is if for some reason the phone has gone back to S-ON. To be honest, I did this step anyways just to be safe. Download, push and flash revone using the commands on the toolkit and ensure that the phone is not ***TAMPERED***
Using Revone, Unlock the bootloader - adb reboot bootloader to check it is unlocked
Step 6: Restoring an earlier backup
Download M7 CWM Nandroid Backup CID O2__102 1.27.206.1 2013-03-30 from crushalot's page on XDA and extract the file to the PC until you have a folder with a date on it and time (2013-03-11.17.58.27)
Make a new folder in your HTC one called clockworkmod. Inside here place a new folder called backup (all lower case). Place the backup here
Also, download http://forum.xda-developers.com/showthread.php?t=2200628 and place onto your SD Card. Once you flash the nandroid backup, go ahead and flash this. It will fix the missing preload apps (calculator, flashlight etc) which happens when unlocking the bootloader, and if these apps are missing can cause future OTA's to fail
Download CWM recovery and rename to CWMTG.img and place in your adb folder. You can also download Hassoon's Toolkit and copy the recovery from there if you like. At this point, ensure your bootloader is UNLOCKED.
From the fasboot menu, type the following
Fastboot boot CWMTG.img
This will boot into the recovery without installing it. Restore the nandroid backup you downloaded earlier and install the preload fix. Reboot
Step 7: Restoring stock recovery, Locking the Bootloader and install updates via OTA
Download the stock recovery for O2 from here http://d-h.st/l1q and flash via fastboot
Once booted up, lock the bootloader using Revone and remove tampered (run the command anyway even if it doesn't say ***TAMPERED***. Check for OTA - The one I got was for 2.24.206.1
Step 8: Returning to S-ON
Verify that the bootloader is LOCKED, not ***TAMPERED*** and hboot is 1.54 with the OS confirming your firmware
Type the command: Fastboot oem writesecureflag 3
Enjoy complete stock and continue with the OTA's
If I helped in any way just click thanks!

Hi,
I followed your instructions up to point 13 - which is where the first problems in your instructions start. The page you are referring to doesn't exist anymore. Unfortunately you also didn't mention what exactly needs to be downloaded, which means people don't know what they have to look for. All I found was "trickdroid". Is that the one you were referring to?
14 - my bootloader is still unlocked, however I followed these instrucktions
16 - I am unable to boot any other image. During the steps you posted - which I followed - at some stage my system went S-ON. Revone is unable to map memory (and noone actually is able to answer me what that means even though there are many people that seem to have that issue) and rumrunner also is not capable anymore of bypassing the S-ON.
I don't know why I can't boot a recovery image, I assume it is because of the S-ON? There is for a millisecond a bootscreen with a red error message text, however I can't read it, because it's too fast.
So I am basically two steps away from getting back to stock and I don't know what to do so I can boot into the recovery image.
HTC One / O2 / hboot 1.44
Could anyone help me with this? I really don't know what to do and I have no experience whatsoever. And I don't wanna break my phone more than it is already

dispereo said:
Hi,
I followed your instructions up to point 13 - which is where the first problems in your instructions start. The page you are referring to doesn't exist anymore. Unfortunately you also didn't mention what exactly needs to be downloaded, which means people don't know what they have to look for. All I found was "trickdroid". Is that the one you were referring to?
14 - my bootloader is still unlocked, however I followed these instrucktions
16 - I am unable to boot any other image. During the steps you posted - which I followed - at some stage my system went S-ON. Revone is unable to map memory (and noone actually is able to answer me what that means even though there are many people that seem to have that issue) and rumrunner also is not capable anymore of bypassing the S-ON.
I don't know why I can't boot a recovery image, I assume it is because of the S-ON? There is for a millisecond a bootscreen with a red error message text, however I can't read it, because it's too fast.
So I am basically two steps away from getting back to stock and I don't know what to do so I can boot into the recovery image.
HTC One / O2 / hboot 1.44
Could anyone help me with this? I really don't know what to do and I have no experience whatsoever. And I don't wanna break my phone more than it is already
Click to expand...
Click to collapse
Don't know why the links don't post correctly - 13: http://forum.xda-developers.com/showthread.php?t=2200628

dispereo said:
Hi,
I followed your instructions up to point 13 - which is where the first problems in your instructions start. The page you are referring to doesn't exist anymore. Unfortunately you also didn't mention what exactly needs to be downloaded, which means people don't know what they have to look for. All I found was "trickdroid". Is that the one you were referring to?
14 - my bootloader is still unlocked, however I followed these instrucktions
16 - I am unable to boot any other image. During the steps you posted - which I followed - at some stage my system went S-ON. Revone is unable to map memory (and noone actually is able to answer me what that means even though there are many people that seem to have that issue) and rumrunner also is not capable anymore of bypassing the S-ON.
I don't know why I can't boot a recovery image, I assume it is because of the S-ON? There is for a millisecond a bootscreen with a red error message text, however I can't read it, because it's too fast.
So I am basically two steps away from getting back to stock and I don't know what to do so I can boot into the recovery image.
HTC One / O2 / hboot 1.44
Could anyone help me with this? I really don't know what to do and I have no experience whatsoever. And I don't wanna break my phone more than it is already
Click to expand...
Click to collapse
I also had the failed map memory error. Only way I could fix it was by repeating the command until it worked. Only happened once bit I'm aware of this being an issue
As for booting into the recovery image - is the image in your fastboot folder? And are you typing fastboot boot CWMTG.img (or whatever name.img)
Wt is the status of the bootloader?

stovie_steve said:
I also had the failed map memory error. Only way I could fix it was by repeating the command until it worked. Only happened once bit I'm aware of this being an issue
As for booting into the recovery image - is the image in your fastboot folder? And are you typing fastboot boot CWMTG.img (or whatever name.img)
Wt is the status of the bootloader?
Click to expand...
Click to collapse
Also the red error message is because you are booting into a custom recovery and this is normal. It would also say entering recovery at the top of the screen. Are you using the CWMTG.img from hasoon's toolkit in your fastboot/adb folder?

stovie_steve said:
I also had the failed map memory error. Only way I could fix it was by repeating the command until it worked. Only happened once bit I'm aware of this being an issue
As for booting into the recovery image - is the image in your fastboot folder? And are you typing fastboot boot CWMTG.img (or whatever name.img)
Wt is the status of the bootloader?
Click to expand...
Click to collapse
I've been repeating it over and over again (rough guess, about 15x) and it doesn't work. Still the map memory error.
I put the recovery-clockwork-6.0.4.3-m7ul.img (and I tried 2 others on their website) in the c:\android (where my adb/fastboot exe are in)
My bootloader says "unlocked" (however I manually unlocked again, just in case) - no change.
I entered fastboot boot recovery-clockwork-6.0.4.3-m7ul.img and then it just reboots (assuming it crashes and has the failsafe reboot)
---------- Post added at 02:18 AM ---------- Previous post was at 02:10 AM ----------
stovie_steve said:
Also the red error message is because you are booting into a custom recovery and this is normal. It would also say entering recovery at the top of the screen. Are you using the CWMTG.img from hasoon's toolkit in your fastboot/adb folder?
Click to expand...
Click to collapse
No I downloaded it manually. Because you say "fastboot boot" it won't flash it. But Hasoon's tool says "flash recovery" which sounds to me like overwriting (flashing) the current original, that would be thing i don't want. So i am a bit confused there.

dispereo said:
I've been repeating it over and over again (rough guess, about 15x) and it doesn't work. Still the map memory error.
I put the recovery-clockwork-6.0.4.3-m7ul.img (and I tried 2 others on their website) in the c:\android (where my adb/fastboot exe are in)
My bootloader says "unlocked" (however I manually unlocked again, just in case) - no change.
I entered fastboot boot recovery-clockwork-6.0.4.3-m7ul.img and then it just reboots (assuming it crashes and has the failsafe reboot)
---------- Post added at 02:18 AM ---------- Previous post was at 02:10 AM ----------
No I downloaded it manually. Because you say "fastboot boot" it won't flash it. But Hasoon's tool says "flash recovery" which sounds to me like overwriting (flashing) the current original, that would be thing i don't want. So i am a bit confused there.
Click to expand...
Click to collapse
What I did was pull the recovery image from hasoon's toolkit, not download the recovery image from the website. If you download the toolkit and go to the directory where you downloaded it there is a folder called recoveries where I copied the image to my adb folder. I did NOT use the toolkit as this involved flashing it so please try it that way instead of downloading it from the website
As for manually unlocking again - how to you do this without revone working? And put of curiosity are you using the toolkit to push/flash revone? If so I would reboot the phone between every step and try it again
Try that and see

stovie_steve said:
What I did was pull the recovery image from hasoon's toolkit, not download the recovery image from the website. If you download the toolkit and go to the directory where you downloaded it there is a folder called recoveries where I copied the image to my adb folder. I did NOT use the toolkit as this involved flashing it so please try it that way instead of downloading it from the website
As for manually unlocking again - how to you do this without revone working? And put of curiosity are you using the toolkit to push/flash revone? If so I would reboot the phone between every step and try it again
Try that and see
Click to expand...
Click to collapse
I got to 17 now (had to adjust minor things to get that work, thanks for your help!) and the problem is, my phone obviously doesn't support revone anymore as it doesn't have the permissions. Can I lock manually (with the HTC Dev command?) and I haven't had a ****TAMPERED**** since I installed the RUU.zip, do I still need to do 17. remove the tampered flag ? If so, how to do that with revone not having the permissions?
Almost there... almost there... *nervous*

So, I updated, I couldn't wait for a reply.
Now I've got "relocked" in the hboot, which is the way HTC Dev intended it (as far as I understand). Is there a way to get rid of that afterwards?

dispereo said:
So, I updated, I couldn't wait for a reply.
Now I've got "relocked" in the hboot, which is the way HTC Dev intended it (as far as I understand). Is there a way to get rid of that afterwards?
Click to expand...
Click to collapse
you should set it to LOCKED (not relocked), using either revone or http://forum.xda-developers.com/showthread.php?t=2475914 (or any of the other method available)

Thanks! Will have a look into that. So my phone updated without an issue now, and I am on Android 4.3 actually which made me wonder... if I ever do have to do a factory reset, what's the phone being reset to? Do you know that by chance?

dispereo said:
Thanks! Will have a look into that. So my phone updated without an issue now, and I am on Android 4.3 actually which made me wonder... if I ever do have to do a factory reset, what's the phone being reset to? Do you know that by chance?
Click to expand...
Click to collapse
Factory reset will just wipe everything (rephrase DATA) off your phone, it will not change ROM, firmware or anything like that, so it will remain on 4.3

nkk71 said:
Factory reset will just wipe everything (rephrase DATA) off your phone, it will not change ROM, firmware or anything like that, so it will remain on 4.3
Click to expand...
Click to collapse
Awesome, thanks for that. Phew. So now I am just stuck on a "re-locked" bootloader because rumrunner can't seem to find a way to get S-OFF again, as hboot 1.55 was installed. So i prolly got to wait until someone found a way to do that.
Thanks A LOT (!!!) for your help!

dispereo said:
Awesome, thanks for that. Phew. So now I am just stuck on a "re-locked" bootloader because rumrunner can't seem to find a way to get S-OFF again. So i prolly got to wait until someone found a way to do that.
Thanks A LOT (!!!) for your help!
Click to expand...
Click to collapse
No problem
As for rumrunner it should work on 4.3 (ie base 3.62.xxx.x), if it's currently not, the guys are updating it quite frequently, but if I recall correctly, it's best to have unlocked bootloader and ROOT.
Cheers

nkk71 said:
No problem
As for rumrunner it should work on 4.3 (ie base 3.62.xxx.x), if it's currently not, the guys are updating it quite frequently, but if I recall correctly, it's best to have unlocked bootloader and ROOT.
Cheers
Click to expand...
Click to collapse
I found a major issue here... when you boot it up and are in the setup screen, it says in red:
This is a test device. Tell HTC is automatically enabled so that HTC can collect critical information about the device during testing. It is not possible to turn this feature off on this phone.
Where did that come from? That sucks...

dispereo said:
I found a major issue here... when you boot it up and are in the setup screen, it says in red:
This is a test device. Tell HTC is automatically enabled so that HTC can collect critical information about the device during testing. It is not possible to turn this feature off on this phone.
Where did that come from? That sucks...
Click to expand...
Click to collapse
That usually comes if you have S-Off, I though you said you went back S-On

nkk71 said:
That usually comes if you have S-Off, I though you said you went back S-On
Click to expand...
Click to collapse
I did! Weird... I am repeating the procedure again.
---------- Post added at 07:32 PM ---------- Previous post was at 07:09 PM ----------
dispereo said:
I did! Weird... I am repeating the procedure again.
Click to expand...
Click to collapse
The bootloader is definitely unlocked as I just did it manually again with the HTC Dev unlock_token.bin.
The locking procedure from the website you posted:
C:\Android>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $ echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1
seek=33796
dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 <
/dev/block/mmcblk0p3: cannot open for write: Permission denied
1|[email protected]:/ $
Rumrunner:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (28/120)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (6/120)
Waiting for ADB (27/120)
ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
Press ENTER to exit
---------- Post added at 07:37 PM ---------- Previous post was at 07:32 PM ----------
dispereo said:
I did! Weird... I am repeating the procedure again.
---------- Post added at 07:32 PM ---------- Previous post was at 07:09 PM ----------
The bootloader is definitely unlocked as I just did it manually again with the HTC Dev unlock_token.bin.
The locking procedure from the website you posted:
C:\Android>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $ echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1
seek=33796
dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 <
/dev/block/mmcblk0p3: cannot open for write: Permission denied
1|[email protected]:/ $
Rumrunner:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (28/120)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (6/120)
Waiting for ADB (27/120)
ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
Press ENTER to exit
Click to expand...
Click to collapse
And someone had the same question here:
http://forum.xda-developers.com/showthread.php?t=2470957
Apparently with 1.55 it's not possible to get S-OFF (even though I didn't go S-ON at any stage, at least not myself...)

dispereo said:
Apparently with 1.55 it's not possible to get S-OFF (even though I didn't go S-ON at any stage, at least not myself...)
Click to expand...
Click to collapse
I'm 100% sure that before rumrunner was changed to a universal toolkit, there were quite a few packages for base 3.xx (hboot 1.55) including 3.62.401.x and they worked.
But like your output said:
ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
Click to expand...
Click to collapse
you would need to flash a ROM with ROOT (maybe a Guru Reset) compatible with your firmware for it to work. (obviously you need to be unlocked to flash ROM)
Also, going from S-Off to S-On on hboot 1.55 will result in "tamper detected - rebooting" and showing TAMPERED again, so you'll need to do that before hboot 1.55 (at least I'm well over 50% sure of that by now).
If the universal rumrunner tool really does not work for you at this time, I'm sure they're fixing it and it will be along soon.
EDIT: fastboot oem writesecureflag 3 is what makes you go S-On, and you have to do it, no way it's done by itself

nkk71 said:
I'm 100% sure that before rumrunner was changed to a universal toolkit, there were quite a few packages for base 3.xx (hboot 1.55) including 3.62.401.x and they worked.
But like your output said:
you would need to flash a ROM with ROOT (maybe a Guru Reset) compatible with your firmware for it to work. (obviously you need to be unlocked to flash ROM)
Also, going from S-Off to S-On on hboot 1.55 will result in "tamper detected - rebooting" and showing TAMPERED again, so you'll need to do that before hboot 1.55 (at least I'm well over 50% sure of that by now).
If the universal rumrunner tool really does not work for you at this time, I'm sure they're fixing it and it will be along soon.
EDIT: fastboot oem writesecureflag 3 is what makes you go S-On, and you have to do it, no way it's done by itself
Click to expand...
Click to collapse
I might have done that, even though I thought I left that out. However, my bootloader says ***** relocked ***** , that's all. It doesn't say ***** tampered ***** (that definitely disappeared after putting the ruu.zip on, I didn't have to do anything. i was wondering about that because you specifially mention it in your walkthrough but for me it disappeared automatically right at the start of the procedure.)

dispereo said:
I might have done that, even though I thought I left that out.
Click to expand...
Click to collapse
No way to go S-On without doing it yourself, no big deal, as long as you can unlock again.
dispereo said:
It doesn't say ***** tampered ***** (that definitely disappeared after putting the ruu.zip on
Click to expand...
Click to collapse
In theory, as long as you have stock ROM and stock recovery, the tampered should not show up, even if unlocked (S-On or S-Off), however for some, it did stay, even under those conditions. no real idea why. repeating myself: tampered should go away as soon as you have stock recovery.
dispereo said:
i was wondering about that because you specifially mention it in your walkthrough
Click to expand...
Click to collapse
Not my guide, it's @stovie_steve guide. I'm just visiting :cyclops:
So if you want to start over again, you need to get unlocked, flash a ROM compatible with your current firmware, which has root, and use rumrunner to get s-off.
I'm off for tonight see you guys around....

[Q] Disaster Recovery - Can't get past bootloader screen

Hi,
My goal was to revert my HTC One to stock, no tampered, no locked, etc. After hours of trying to find a solution to S-Off, I was finally successful with gaining S-Off, Removing the Tampered Flag, Re-locking, and returning to S-On.
I'm not entirely sure what happened next. I think I most have chosen "reboot" so that I could get back in and apply a new RUU.
Instead, my phone returned to bootloader, with a surprise reappearance of the "Tampered" flag, and a new one now, "Security Warning".
Attempts to reboot simply return me to bootloader. Attempts to access Recovery return me to bootloader. Attempts to power down work. And when I power on again it returns me to bootloader.
What. The. Hell. Happened.
Thanks in advance for any help.

Additional Details: Here are the steps I took to achieve each change:
S-Off - Rumrunner - Successful
Remove Tampered - Via this thread:
Code:
adb devices
adb shell
su
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
exit
adb reboot bootloader
Reset Lock Status -
Code:
./revone -l
(the directions I had stated "-L" but capital wasn't recognized, and lowercase worked.
Reset S-On -
Code:
fastboot oem writesecureflag 3

Looks like something screwed up. Once you are S-OFF, you do not need to lock the bootloader or S-ON to run RUU. It is (was) your get out of jail card.
Can you select factory reset from the bootloader menu? What is the result? If no go, then unlock bootloader, flash custom recovery, restore backup and/or flash custom rom, and restart the process.
Also what RUU were you trying to run, and why? Warranty related?

SaHiLzZ said:
Looks like something screwed up. Once you are S-OFF, you do not need to lock the bootloader or S-ON to run RUU. It is (was) your get out of jail card.
Can you select factory reset from the bootloader menu? What is the result? If no go, then unlock bootloader, flash custom recovery, restore backup and/or flash custom rom, and restart the process.
Also what RUU were you trying to run, and why? Warranty related?
Click to expand...
Click to collapse
Thanks for the reply. I was going to do T-mobile's trade-in program (every 6 months), but need the phone back to stock or they won't accept.
When I chose factory reset, it returned me to the bootloader.
My guess is it is freaking out because I relocked everything but still have a custom ROM.
Thanks for the advice, now time to hunt through the threads to figure out how to do all those things again. It has been a while, I've been unlocked for ages.

Your best bet will be to flash a ruu from tmobile based on 1.44hboot. As the new 1.55 hboot may not like being s-on.
So, in very short.
1. unlock bootloader,
2. flash custom recovery,
3. restore backup and/or flash custom rom (adb push/sideload/otg cable)
4. S-OFF
5. Run http://www.htc1guru.com/dld/ruu-zip...0-20-10-40-1150-04-release-324846-signed-zip/
6. Figure out how to lock bootloader.. using nkk71's guide

[Q] fastboot boot recovery.img on hboot 1.56

Just got my One back from warranty repair. Looks like they either gave me a new main board or updated my device, I'm on the latest Bell 4.19.666.8 with hboot 1.56.
I figured I would get a full nandroid backup of the phone at stock 4.4.2, but I can't seem to get fastboot boot to work. Don't want to flash the recovery as I want to get a backup of the stock one.
with the phone in FASTBOOT USB, I ran
$ fastboot boot openrecovery-twrp-2.7.0.0-m7.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.311s]
booting...
OKAY [ 0.000s]
finished. total time: 1.311s
But the device just sits at the fastboot screen and does nothing. It doesn't even respond to fastboot commands anymore so I have to force power off and reboot.
I saw on the Nexus 4 forum that on that phone you now have to specify a kernel command line with fastboot boot - something like
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Is this true for the One too? If so, what is the command line? I'm guessing lge.kcal is specific to LG devices.

ergosteur said:
Just got my One back from warranty repair. Looks like they either gave me a new main board or updated my device, I'm on the latest Bell 4.19.666.8 with hboot 1.56.
I figured I would get a full nandroid backup of the phone at stock 4.4.2, but I can't seem to get fastboot boot to work. Don't want to flash the recovery as I want to get a backup of the stock one.
with the phone in FASTBOOT USB, I ran
$ fastboot boot openrecovery-twrp-2.7.0.0-m7.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.311s]
booting...
OKAY [ 0.000s]
finished. total time: 1.311s
But the device just sits at the fastboot screen and does nothing. It doesn't even respond to fastboot commands anymore so I have to force power off and reboot.
I saw on the Nexus 4 forum that on that phone you now have to specify a kernel command line with fastboot boot - something like
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Is this true for the One too? If so, what is the command line? I'm guessing lge.kcal is specific to LG devices.
Click to expand...
Click to collapse
"fastboot boot ..." only worked on hboot 1.44.
and I can't answer about the N4 method if that would work or not; but I kinda doubt it.

nkk71 said:
"fastboot boot ..." only worked on hboot 1.44.
and I can't answer about the N4 method if that would work or not; but I kinda doubt it.
Click to expand...
Click to collapse
OK, thanks. Should I even bother trying to back up the stock recovery or just go ahead and flash a custom one? Would there be any way to do it without hboot 1.44? I see that temproot doesn't work on stock 4.4.2.

ergosteur said:
OK, thanks. Should I even bother trying to back up the stock recovery or just go ahead and flash a custom one? Would there be any way to do it without hboot 1.44? I see that temproot doesn't work on stock 4.4.2.
Click to expand...
Click to collapse
Couldn't find stock recovery 4.19.666.8, but if it's for future OTAs then any stock recovery 4.19.xxx.x should work (maybe even 3.xx.666.x)
This is a good source for stock recoveries [Recovery]Collection of Stock Recovery
If you're using a stock recovery that is not a 100% match, then the OTA would just hang, and you have to manually reboot for it to continue.... you can check my guide under CWM method about info on that.
There's also @SaHiLzZ guide for Canadian users: http://forum.xda-developers.com/showthread.php?t=2529225
Or do you need it for some other reason?

nkk71 said:
Couldn't find stock recovery 4.19.666.8, but if it's for future OTAs then any stock recovery 4.19.xxx.x should work (maybe even 3.xx.666.x)
This is a good source for stock recoveries [Recovery]Collection of Stock Recovery
If you're using a stock recovery that is not a 100% match, then the OTA would just hang, and you have to manually reboot for it to continue.... you can check my guide under CWM method about info on that.
There's also @SaHiLzZ guide for Canadian users: http://forum.xda-developers.com/showthread.php?t=2529225
Or do you need it for some other reason?
Click to expand...
Click to collapse
I was thinking more for archival purposes- Just in case. I restored my phone back to stock twice for warranty, your guide was very helpful.
I think I'll just go ahead and flash CWM/TWRP, my warranty is done anyway.

ergosteur said:
I was thinking more for archival purposes- Just in case. I restored my phone back to stock twice for warranty, your guide was very helpful.
I think I'll just go ahead and flash CWM/TWRP, my warranty is done anyway.
Click to expand...
Click to collapse
do go back to warranty you need to set phone to LOCKED, which is only possible with S-Off.
the fastboot oem lock command will set your bootloader to RELOCKED, so they would know you've unlocked it.... so stock recovery is the least of your worries if you want to ever go 100% back to stock.
stick with TWRP 2.6.3.3 or higher, but not 2.7.0.0 which seems to have problems with adb (and if i remember correctly charging when phone is off... though it could be a different one)
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
or 2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
EDIT: forgot to tell you why TWRP: it's compatible with 4.4 ROMs, CWM doesn't seem fully updated yet
Happy flashing :laugh:

HTC One Bricked

Last night i tryed to restore to stock my htc one m7 international because my microphone dont work so i need to go at warranty. I flashed stock rom removed root and anything(i didnt relock the bootloader) and after that i tryed to update firmware(because it was 4.3) to 4.4.3. After firmware was installed.... Surprize , i get stuck at HTC Logo. I tryed to install cwm/twrp and use sideload to push a stock firmware in phone but my phone is recognized in fastboot mode in cmd but when i go in recovery and activate adb sideload and type adb devices cmd sayes No device connected and i get a triangle in device manager. What should i do now? How can i relock bootloader and get a rom on my phone? Im gonna upload a print screen with phone infos. If someone can help me with a step by step tutorial made for noobs i be happyest person in the world.

buhanita said:
Last night i tryed to restore to stock my htc one m7 international because my microphone dont work so i need to go at warranty. I flashed stock rom removed root and anything(i didnt relock the bootloader) and after that i tryed to update firmware(because it was 4.3) to 4.4.3. After firmware was installed.... Surprize , i get stuck at HTC Logo. I tryed to install cwm/twrp and use sideload to push a stock firmware in phone but my phone is recognized in fastboot mode in cmd but when i go in recovery and activate adb sideload and type adb devices cmd sayes No device connected and i get a triangle in device manager. What should i do now? How can i relock bootloader and get a rom on my phone? Im gonna upload a print screen with phone infos. If someone can help me with a step by step tutorial made for noobs i be happyest person in the world.
Click to expand...
Click to collapse
For warranty to be valid, you must be 100% stock which mean stock software and firmware including LOCKED (not RE-LOCKED) bootloader and no TAMPERED flag in bootloader. Removing both of them require S-OFF so upgrading firmware was a really bad idea (s-off is harder to achieve on newer version).
Now for your adb issue, it looks like your drivers are not installed correctly (triangle in device manager) install drivers correctly so you can have adb connectivity.
You should take a look at nkk71's guide linked in my sig below.

I solved with adb drivers now i have another problem. I pushed with sideload revolution stock rom (One_6.09.401.5_odexed) and when i try to install it from TWRP i get this : E:Error executing updater binary in zip '/sdcard/sideload.zip'. What can i do ?

buhanita said:
I solved with adb drivers now i have another problem. I pushed with sideload revolution stock rom (One_6.09.401.5_odexed) and when i try to install it from TWRP i get this : E:Error executing updater binary in zip '/sdcard/sideload.zip'. What can i do ?
Click to expand...
Click to collapse
have you checked MD5 of the rom?
What TWRP version are you using?

Im unsing lastest TWRP version. I didnt check md5 becuase i dont know how to check it... If you can tell me...

What twrp version?

buhanita said:
Im unsing lastest TWRP version. I didnt check md5 becuase i dont know how to check it... If you can tell me...
Click to expand...
Click to collapse
When we are asking "what version" we are expecting an answer with version number
You might want to try to flash your rom with twrp 2.6.3.3 as this is the most stable version.
you can check md5 using WINMD5 app (windows app)
just download it and you'll understand how it works (just drag and drop the file you want to MD5 check)

MD5 checked. 9164269273eb0038b6ae54b3cf61b73c i dont know what is this... im gonna install twrp 2.6.3.3 right now.
EDIT. THX SO MUCH GUYS FOR HELP I INSTALLED 2.6.3.3 and i insalled via sideload stock revolution rom 4.4.3. Now how can i install stock recovery?
L.E. I solved with stock recovery 2. Now its a chance to get relocked and reset tempered status?

buhanita said:
L.E. I solved with stock recovery 2. Now its a chance to get relocked and reset tempered status?
Click to expand...
Click to collapse
require s-off to be LOCKED again an no TAMPERED flag best you can do with s-on is to be RE-LOCKED with TAMPERED

alray said:
require s-off to be LOCKED again an no TAMPERED flag best you can do with s-on is to be RE-LOCKED with TAMPERED
Click to expand...
Click to collapse
can you give me a tutorial with relock and reset tampered flag? As far i know i cant s-off this phone on hboot 1.57.00 for a moment.

buhanita said:
can you give me a tutorial with relock and reset tampered flag? As far i know i cant s-off this phone on hboot 1.57.00 for a moment.
Click to expand...
Click to collapse
with s-on only thing you can do is to have RELOCKED bootloader and TAMPERED flag will still be there. to relock (not lock) the bootloader:
Code:
fastboot oem lock
if you want the bootloader to be LOCKED (not re-locked) and TAMPERED flag to be removed, you first need s-off (hboot 1.57=firewater or sunshine) then use the guru bootloader reset tool from Crushalot (htc1guru.com). Tool must be used from a custom recovery but the tampered flag should be only removed on hboot 1.44/1.54 or it may reappear after a few reboot.
You can look nkk71's guide, everything explained there

htc m7 pn07110 bricked
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0