Related
First I want to thank all from this site for all the work you've done!
OK, got a G2 few days ago rooted it using rage method, updated radio to 26.04.02.17 (read that solved some problems with cyanogen's 6.1.1 ROM), installed 6.1.1 ROM and all was well... Then I decided to upgrade hboot (for no particular reason) to 0.85.005 with fastboot. After install it rebooted and noticed I now have SHIP S-ON ...and it wouldn't boot..got stuck on HTC splash screen. So I say oops...pull battery and go into recovery and do a restore to a rooted stock ROM. Was successful but was hoping it would give me root back but no joy. Then tried to install 6.1.1 from ROM manager but no joy. (no surprise with S_ON) So I'm wondering:
Why did hboot update change it to S-ON?
Why didn't my restore restore S_OFF? ( thought restore re-wrote everything)
AND..where do I go from here? Should I just use rage again to get root?
Any help would be greatly appreciated!!
Again, thanks to all!!
Edit: OK just realized I still have root access threw terminal emulator???
How can this be with S-ON??
So I guess I still have root so I tried to install cyogen 6.1.1 from sd card using revovery.
all seems to go well, says its complete but when I reboot, it gets stuck on HTC splash screen
Also tried gfree and this method http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
got to 2nd to last command:
# /data/local/tmp/root
and get
# mkdir failed for /system/xbin, file exists
Anyone??
That sounds like the stock *DZ* hboot, not the G2 one. If so, you're lucky you didn't brick your phone. I wouldn't switch hboots between DZ/G2 unless you were flashing the whole ROM.
The fact that it's a stock one explains why you have S-ON, if you only had S-OFF via the eng hboot before.
What you need to do is run gfree, as you say, to get proper radio S-OFF.
S-ON/S-OFF has nothing to do with root. So you can still be S-ON and have root.
If you did a nandroid restore through Clockwork then as far as I'm aware that doesn't include a restore/backup of hboot.
You won't be able to flash another custom ROM/recovery until you get S-OFF back again.
That "mkdir" error message is normal, just ignore it. But gfree doesn't work with CM 6.1.1. It will work on 6.1 but there are some incompatible kernels too.
I suggest installing the eng hboot (the correct one for your phone, see the Wiki) to get S-OFF (but be careful doing this, e.g the checksums). Then revert to a ROM that is compatible with gfree and run gfree to get radio S-OFF. Then you can revert back to 6.1.1 or whatever you want.
steviewevie said:
That sounds like the stock *DZ* hboot, not the G2 one. If so, you're lucky you didn't brick your phone. I wouldn't switch hboots between DZ/G2 unless you were flashing the whole ROM.
The fact that it's a stock one explains why you have S-ON, if you only had S-OFF via the eng hboot before.
What you need to do is run gfree, as you say, to get proper radio S-OFF.
S-ON/S-OFF has nothing to do with root. So you can still be S-ON and have root.
If you did a nandroid restore through Clockwork then as far as I'm aware that doesn't include a restore/backup of hboot.
You won't be able to flash another custom ROM/recovery until you get S-OFF back again.
That "mkdir" error message is normal, just ignore it. But gfree doesn't work with CM 6.1.1. It will work on 6.1 but there are some incompatible kernels too.
I suggest installing the eng hboot (the correct one for your phone, see the Wiki) to get S-OFF (but be careful doing this, e.g the checksums). Then revert to a ROM that is compatible with gfree and run gfree to get radio S-OFF. Then you can revert back to 6.1.1 or whatever you want.
Click to expand...
Click to collapse
Thanks for responding! Especially after this post has turned into more of a rambling blog as I learn more.
I tried to run gfree to get s-off and it doesn't work, stays s-on. Thought it was because of the "mkdir" error message I was getting. Then tried to install eng hboot using the whole G2 ROOT INSTRUCTIONS here:
http://forum.xda-developers.com/showthread.php?t=834228
Everything goes smooth except for the"mkdir failed for /system/xbin. file exists"
When I reboot, still have:
VISION PVT SHIP S-ON
hboot-0.85.0005
Any ideas??
Again thanks for any help and suggestions!
Just noticed the first commands in the G2 ROOT INSTRUCTIONS have a "$" sigh ie: "$ adb push su /sdcard/su"
Does this mean you should run "adb shell" first? If that.s the case, I get "adb: permission denied" although I do see su on sdcard.
(I know I'm really grasping here )
No, you don't run "adb shell" before running those adb commands, because "adb shell" will give you a command prompt on your phone, and those adb push commands need running from your PC's command prompt. That "$" prompt shown in the guide can be confusing, because it's being run from a PC running Linux, which has a $ prompt. If you have Windows then you will have some sort of "C:\" prompt.
If you are only installing the eng hboot though, you don't need to do all that, since you already have root. Skip to the "Perm Root" section in that guide that you linked, and do everything up to and including the "dd" command. Then the sync and reboot bit (skip over the "root" script).
Although check what message you get from the insmod command. We might have a problem here, because if you're on CM 6.1.1 (that's what you're on, right ?) then gfree won't work and I don't know if either of those wpthis modules (OTA and pre-OTA) will work properly on CM 6.1.1.
The insmod is crucial because unless that command gives you the "right" error message as shown in the procedure, it won't disable the NAND write protection and so won't let you write the hboot permanently.
A bit offtopic, but maybe someone will find this helpful: in many tutorials for *NIX (Linux, OSX, BSD etc.) users you'll find that what you need to type in a command prompt (terminal) starts with either $ or #.
While that may be confusing for Windows users, it is a hint as to whether you are supposed to run the commands as a simple user (the prompt shows a $) or as the administrator (or root) user (in which case, the prompt shows a #).
steviewevie said:
No, you don't run "adb shell" before running those adb commands, because "adb shell" will give you a command prompt on your phone, and those adb push commands need running from your PC's command prompt. That "$" prompt shown in the guide can be confusing, because it's being run from a PC running Linux, which has a $ prompt. If you have Windows then you will have some sort of "C:\" prompt.
If you are only installing the eng hboot though, you don't need to do all that, since you already have root. Skip to the "Perm Root" section in that guide that you linked, and do everything up to and including the "dd" command. Then the sync and reboot bit (skip over the "root" script).
Although check what message you get from the insmod command. We might have a problem here, because if you're on CM 6.1.1 (that's what you're on, right ?) then gfree won't work and I don't know if either of those wpthis modules (OTA and pre-OTA) will work properly on CM 6.1.1.
The insmod is crucial because unless that command gives you the "right" error message as shown in the procedure, it won't disable the NAND write protection and so won't let you write the hboot permanently.
Click to expand...
Click to collapse
ahhhh..thanx for clarifying "$" issue for me.
I am NOT on CM 6.1.1
I have stock OTA rom right now (with root), sorry for the misunderstanding
OK,this is exact error message I get:
insmod: init_module '/data/local/wpthis-OTA.ko' failed (function not implemented)
After I run dd=..... I get
2048+0 records in
2048+0records out
1048576 bytes transferred in 0.079 secs (13273113bytes/sec)
So all looks perfect to me, but I still get stuck with:
....S-ON
hboot-0.85.0005
does the "insmod" being in error message mean anything?
In any event, at least I still have a working phone and learned alot more
(like you said..I'm very lucky I didn't brick it flashing this hboot update)
That's the "correct" error message from insmod. But weird stuff is going on here, which isn't too suprising if you have the wrong hboot for your phone.
I'm getting confused, I thought you were on CM 6.1.1. I also thought your phone was stuck in a boot loop, but you seem to be able to still run commands as root, so presumly it boots ok now ?
steviewevie said:
That's the "correct" error message from insmod. But weird stuff is going on here, which isn't too suprising if you have the wrong hboot for your phone.
I'm getting confused, I thought you were on CM 6.1.1. I also thought your phone was stuck in a boot loop, but you seem to be able to still run commands as root, so presumly it boots ok now ?
Click to expand...
Click to collapse
Sorry for the misunderstanding, I had CM 6.1.1 on when I flashed wrong hboot. After that it would get stuck on HTC screen when trying to boot up into CM 6.1.1
So I booted into recovery and did a restore which luckily worked. Which now I have no idea why that worked looking back other than because it was a legit stock ROM, so it allowed it. Is this the case??
Last night I actually tried to un-root and get everything back to stock (including hboot) via this method:
ttp://theunlockr.com/2010/12/01/how-to-unroot-the-t-mobile-g2-htc-vision/
but got stuck on "dd if=/sdcard
/miscnew.img of=/dev/block/mmcblk0p17" with a read only ermision denied message
which I wasn't surprised because I have S=ON
I need to replace my current handset, I understand you have to unroot before doing so or get charged. I followed the instructions step by step, Installed a stock rooted ROM, Flashed PC10img.zip, etc but when i boot into the bootloader i still see S-Off. I do not have root access but the S-On is making me paranoid about ordering a replacement. Any reports or fixes for this?
You may want to specify which rooting method you performed on your phone (e.g. Rage, VISIONary). I will need to unroot my phone soon as I'm expecting a replacement, and I believe I've seen a couple different ways of successfully unrooting the phone. Interested to hear what others have to say about your issue.
dustrho said:
You may want to specify which rooting method you performed on your phone (e.g. Rage, VISIONary). I will need to unroot my phone soon as I'm expecting a replacement, and I believe I've seen a couple different ways of successfully unrooting the phone. Interested to hear what others have to say about your issue.
Click to expand...
Click to collapse
Originally used the RAGE method, but i ran the program Gfree over it to get the SIM card unlock also.
Veiger said:
Originally used the RAGE method, but i ran the program Gfree over it to get the SIM card unlock also.
Click to expand...
Click to collapse
There is an option in gfree to turn secu_flag on or off, here is the options from the Wiki, just re-run gfree commands with the -s option:
Code:
gfree usage:
gfree [-h|-?|--help] [-v|--version] [-s|--secu_flag on|off]
-h | -? | --help: display this message
-v | --version: display program version
[COLOR="red"]-s[/COLOR] | --secu_flag on|off: turn secu_flag[COLOR="Red"] on [/COLOR]or [COLOR="red"]off[/COLOR]
-c | --cid <CID>: set the CID to the 8-char long CID
-S | --sim_unlock: remove the SIMLOCK
-f | --free_all: same as --secu_flag off --sim_unlock --cid 11111111
Wiki link:
http://forum.xda-developers.com/wik...Subsidy_Unlock.2C_SuperCID.2C_and_Radio_S-OFF
joemm said:
There is an option in gfree to turn secu_flag on or off, here is the options from the Wiki, just re-run gfree commands with the -s option:
Code:
gfree usage:
gfree [-h|-?|--help] [-v|--version] [-s|--secu_flag on|off]
-h | -? | --help: display this message
-v | --version: display program version
[COLOR="red"]-s[/COLOR] | --secu_flag on|off: turn secu_flag[COLOR="Red"] on [/COLOR]or [COLOR="red"]off[/COLOR]
-c | --cid <CID>: set the CID to the 8-char long CID
-S | --sim_unlock: remove the SIMLOCK
-f | --free_all: same as --secu_flag off --sim_unlock --cid 11111111
Wiki link:
http://forum.xda-developers.com/wik...Subsidy_Unlock.2C_SuperCID.2C_and_Radio_S-OFF
Click to expand...
Click to collapse
Thanks a ton
Never mind got it to work
Unfortunately I formated my sdcard after i have rooted my Desire Z. Can i just enter "./gfree -s on" to make an image with s-on again and load it via "dd if=/sdcard/partition7-gfree-s-on.img of=/dev/block/mmcblk0p7"? Will this work to get s-on permanently?
Edit: I tried it and after "./gfree -s on" I entered "reboot bootloader" which showed me s-on. But I still had root. Then I entered the second line "dd if..." and after I pressed return the phone rebooted. Still had root after this reboot. So I clicked "unroot" in Visionary and the phone was unrooted.
But: When I received the systemupdate I was unable to install it. The phone reboots, starts installing and I get a triangle with an exclamation mark in after a couple seconds of progressing. ClockworkMod Recovery gives me this message when I press the power button:
"Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Can someone help me please?
pl4cid said:
Unfortunately I formated my sdcard after i have rooted my Desire Z. Can i just enter "./gfree -s on" to make an image with s-on again and load it via "dd if=/sdcard/partition7-gfree-s-on.img of=/dev/block/mmcblk0p7"? Will this work to get s-on permanently?
Click to expand...
Click to collapse
"./gfree -s on" will edit your radio config partition (7) to make it S-ON. No need to dd anything after that. The only thing you have lost through losing your part7 backup is the ability to re-lock the SIM, if there was a lock there in the first place.
Edit: I tried it and after "./gfree -s on" I entered "reboot bootloader" which showed me s-on. But I still had root. Then I entered the second line "dd if..." and after I pressed return the phone rebooted. Still had root after this reboot. So I clicked "unroot" in Visionary and the phone was unrooted.
Click to expand...
Click to collapse
gfree doesn't unroot, gfree can set S-OFF/S-ON etc, change the CID etc. But to unroot you need to do other stuff (like flash a stock ROM or just remove the su binary and Superuser app).
But: When I received the systemupdate I was unable to install it. The phone reboots, starts installing and I get a triangle with an exclamation mark in after a couple seconds of progressing. ClockworkMod Recovery gives me this message when I press the power button:
"Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Can someone help me please?
Click to expand...
Click to collapse
That's the stock recovery rather than clockwork. What system update are you talking about, the 1.72 OTA for the DZ ? Or are you trying to flash a whole ROM from SD card ?
steviewevie said:
"./gfree -s on" will edit your radio config partition (7) to make it S-ON. No need to dd anything after that. The only thing you have lost through losing your part7 backup is the ability to re-lock the SIM, if there was a lock there in the first place.
gfree doesn't unroot, gfree can set S-OFF/S-ON etc, change the CID etc. But to unroot you need to do other stuff (like flash a stock ROM or just remove the su binary and Superuser app).
That's the stock recovery rather than clockwork. What system update are you talking about, the 1.72 OTA for the DZ ? Or are you trying to flash a whole ROM from SD card ?
Click to expand...
Click to collapse
Yes you guess right, I want to install the 1.72 OTA. So what shall I do? I got the DZ unlocked and unbranded. The OTA is already downloaded. Is it enough to delete the binaries and the SU-App or are there any other things to prepare.
Thanks in advance for your help
Sent from my HTC Vision using XDA App
pl4cid said:
Yes you guess right, I want to install the 1.72 OTA. So what shall I do? I got the DZ unlocked and unbranded. The OTA is already downloaded. Is it enough to delete the binaries and the SU-App or are there any other things to prepare.
Click to expand...
Click to collapse
You realise you will lose root by applying that update and will not be able to root again at 1.72 ? Not until someone figures out a way to root that ROM ? And if you have gone back to S-ON you will not be able to downgrade after going to the OTA either ?
steviewevie said:
You realise you will lose root by applying that update and will not be able to root again at 1.72 ? Not until someone figures out a way to root that ROM ? And if you have gone back to S-ON you will not be able to downgrade after going to the OTA either ?
Click to expand...
Click to collapse
Hey my friend, thanks for this really helpful news. That was new to me and in this case I deserve root accessibility Thanks a lot again and have a nice day!
Sent from my HTC Vision using XDA App
READ THIS:
i have removed the dead multiupload links that have for some reason been causing an extreme amount of confusion. i thot the "mirror" following each link was self explanitory,but apparently not.
from this point forward,i will no longer respond to "links are dead" posts or PMs if i check them and find them to be working.
in other words,yes,the links are working.
___________________________________________________________________
the return to stock thread from 5/17 is outdated. it still works,but afterward youll need to allow your phone to OTA to mr2 if you want to be on the current firmware.
between the newer firmware,and having to execute extra steps if rotoed with revolutionary,the old thread seems to be causing some confusuion. i thot maybe it would help if i threw it up here as well
its geared toward a revolutionary rooter who doesnt have adb set up,so sorry if its a little insulting to more advanced users
last and not least,if you rooted old skool,and just need to flash mr2 files,just skip the part detailing getting the old 1.04.2000 eng hboot back. go directly to: Putting current stock firmware and s-on back onto the phone
as soon as the GB OTA hits for realeek i will update this with those files.
*please read all directions first. post up any questions you have before doing anythingyou are messing with your bootloader,wich is a vital part of your phones operation. screwing it up WILL make your phone an expensive paperweight.
how to unroot
the revolutionary method of rooting uses a sneeky hboot exploit,and replaces your stock 1.04.0000 or 1.05.0000 bootloader with a modified permanent hboot. it not only gives you all the same fashboot flash abilities as the original engineering bootloader,but it very effectively blocks other hboots for overwriting it. its good,as you will remain s-off if you accidentally flash a full RUU,or accept an OTA,but makes it a little trickier to remove.
for the time being, removal requires ADB to be set up and running and some commands entered in "fastboot" to to allow the permanent hboot to be overwritten. once an "s-on" tool is release,ill take th is part of this guide down.
if you rooted the old skool manual way and have adb setup and working,you can use this guide to remove the permanent hboot.
with Revolutionary,will come a new wave of rooters that have no clue what adb,or fastboot even are. for you folks, Sele and the crew in the "rescue sguad" at HTC Thunderbolt Forum have come up with a really clever way to get the adb basics,and the eng bootloader to flash,with minimal setup and confusion. with their permission,im borrowing it for our guide here.
*WARNING* no siginture or file checks will be done flashing the new bootloader in hboot or fastboot.fastboot will literally flash "lets golf" as a bootloader if you tell it to. DO NOT mess with your hboot unless absolutely neccessary to return to stock for warranty purposes. if youre just tired of being rooted,flash the gingerbread ruu to get back to unrooted firmware and factory recovery. leaving the revolutionary s-off bootloader in place is the safest,and best option,and will not affect your ability to recieve OTAs.
*AGAIN- if youre just following this procedure because youre tired of being rooted,skip this next section and leave the permanent hboot in place. jump to "Putting current stock firmware and s-on back onto the phone" and flash only the first "PG05IMG_no_hboot_2.11.605.9" file(you can flash the 2nd file too if you want,but the permanent hboot will block it )
Setting up adb and removing the permanent hboot if youve never used adb before
1)if you no longer have the htc drivers that you installed when rooting with revolutionary,download them again from here on revolutionarys website.
2)next download *link removed (mirror)to somewhere convenient that youll be able to find it,like your desktop,or a "downloads" folder. it contains the old eng 1.40.2000 s-off hboot,and the bare minumum tools to install it.
3)the following directions were using windows 7 and chrome browser. other OS may be slightly different-the end result is you want unzipped,inside tbolt folder to be on the root of your C: drive.
-find the tbolt.zipdownload
-click on tbolt.zip download and open it.
-inside tbolt.zip,there is a folder labled tbolt. drag it to the root of C:. inside tbolt is the unpermanent hboot and some adb tools.
4) charge your Thunderbolt to 100%
5)click on then "start" bubble in the lower left corner of your screen. type "command" in the search window and hit enter. this will open a small black command window.
6)enter the following command(by typing or copy/paste):
Code:
cd c:\tbolt
you should see your promt in the window change to: c:\tbolt>
7)enter the follwing command:
Code:
md5sums hbooteng.nb0
check the output on the command window. THIS IS VERY IMPORTANT. the command must equal exactly 6991368ee2deaf182048a3ed9d3c0fcb if it does not,STOP!. delete the tbolt.zip download,and the unzipped tbolt folder from C:,re download and try it again. again,do not procede if the output in your command number does not equal it exactly.
8)once the number matches,you can continue. copy and paste the following codes into the command window:
Code:
adb devices
the output should be your phones serial number
now enter:
Code:
adb reboot bootloader
this will cause your phone to boot into FASTBOOT mode,wich is a white screen with colored letters.
now enter:
Code:
fastboot devices
the result again,should be your phones serial number.
9) now youre ready to enter the command to unlock the permanent hboot and flash the new,non permanent one.
to unlock,enter:
Code:
fastboot oem mw 8d08ac54 1 31302E30
write the new hboot:
Code:
fastboot flash hboot hbooteng.nb0
if you select bootloader at this point from the fastboot menu, youll still see the permanent s-off hboot,so select reboot with the volume rocker and power button and let the phone reboot. after it boots,you can adb reboot bootloader again,or power off, then power on/vol down and check that your pink "UNLOCKED" or "REVOLUTIONARY" is gone and you have the old 1.49.2000 bootloader.
here is what you should see in the command window,the red are my inputs:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="Red"]cd c:\tbolt[/COLOR]
c:\tbolt>[COLOR="red"]md5sums hbooteng.nb0[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\tbolt\]
hbooteng.nb0 6991368ee2deaf182048a3ed9d3c0fcb
c:\tbolt>[COLOR="red"][COLOR="red"]adb devices[/COLOR][/COLOR]
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT126S005970 device
c:\tbolt>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\tbolt>[COLOR="red"]fastboot devices[/COLOR]
HT126S005970 fastboot
c:\tbolt>[COLOR="red"]fastboot oem mw 8d08ac54 1 31302E30[/COLOR]
...
OKAY [ 0.006s]
finished. total time: 0.006s
c:\tbolt>[COLOR="red"]fastboot flash hboot hbooteng.nb0[/COLOR]
sending 'hboot' (1024 KB)...
OKAY [ 0.183s]
writing 'hboot'...
OKAY [ 0.219s]
finished. total time: 0.403s
c:\tbolt>
Putting current stock firmware and s-on back onto the phone
after getting the bootloader back to the original s-off,engineering 1.04.2000 hboot download these 2 files:
1) PG05IMG_no_hboot_2.11.605.19.zip
mirror: https://rapidshare.com/files/271867813/PG05IMG_no_hboot_2.11.605.19.zip
md5: 334909756073760b3d7316e51a4ce837
2) *link removedPG05IMG_hboot_ONLY_2.11.605.19.zip
mirror:http://www.mediafire.com/?0z0rlzh9lrnh0qs
md5: d26b3253358407d459c654e6729a39ca
rename PG05IMG_no_hboot_2.11.605.19.zip to "PG05IMG",move to your sd card,and flash in hboot.
this is important! you must flash the PG05IMG_no_hboot_2.11.605.19.zip first
after successfully flashing that,you will be on unrooted gingerbread with an eng s-off bootloader. delete the PG05IMG file from your sd card. now place the PG05IMG_hboot_ONLY_2.11.605.19.zip on your sd card. check the md5. once youve verified it matches,you can rename PG05IMG and flash it.
again, only flash the hboot file after you have successfully flashed the rom.
now you are 100% stock on latest firmware. unrooted gingerbread 2.11.605.19 with *locked* 1.05.0000 s-on bootloader.
as always,be as cautious as possible doing hboot flashes,and follow directions in the http://androidforums.com/thunderbolt-all-things-root/353591-how-some-root-terminology.html to flash these files if youre unfamiliar with hboot flashing.
*please start a new thread before attempting this if any part of this confuses you. without a bootloader your phone is a paperweight,so we want to help you prior to making any mistakes
last and not least: if you have non working hard buttons,or no screen,see the directions in this thread on AF
Nice
Awesome Found that there is also another way you can use the same method from the original root instructions.
adb push yourhbootfilenamehere /data/local/
adb shell
dd if=/data/local/yourhbootfilenamehere of=/dev/block/mmcblk0p18
Then just put the stock image on your sd card and use
adb reboot bootloader
and flash your stock firmware
Hope this helps anyone looking for a slightly quicker way
Not sure if this is a problem but...
After I un-rooted last night and ran the 2.11.605.5 RUU, I now get a bright pink message at the bootloader saying *** LOCKED ***. Anyways, the device now states S-ON and I am running stock. Is the LOCKED message something to be concerned about?
no the locked message is just something new they put into it some people think it means they might put it in the list of officially unlockable devices soon check it out here htcdev.com/bootloader
ellis90009 said:
Awesome Found that there is also another way you can use the same method from the original root instructions.
adb push yourhbootfilenamehere /data/local/
adb shell
dd if=/data/local/yourhbootfilenamehere of=/dev/block/mmcblk0p18
Then just put the stock image on your sd card and use
adb reboot bootloader
and flash your stock firmware
Hope this helps anyone looking for a slightly quicker way
Click to expand...
Click to collapse
while i dont know that youll save any time doing it this way, this is certainly anotehr way to skin the cat if you have adb set up,and are fairly savy at using it,as there are alot of small details youre leaving out.
also i need to add a couple of things:
1)you will need to reboot your phone between
Code:
dd if=/data/local/yourhbootfilenamehere of=/dev/block/mmcblk0p18
and
Code:
adb reboot bootloader
as,rebooting imediately to bootloader will take you back to the revolutionary one. the new hboot is written on reboot.
2)be extremely careful with this. if you choose to flash a stock hboot rather than the engineering one,you risk a security warning if you flash the wrong hboot overtop of the wrong custom firmware. youll then be stuck with an s-on hboot and only be able to run newer RUUs to try and fix it.
if you really want to use this method,the safest way would be to run the RUU first. youll have to get a temp root shell(zergRush prolly will work),then run the command to replace the hboot that matches the firmware that you flashed.
CaptainStrange said:
Is the LOCKED message something to be concerned about?
Click to expand...
Click to collapse
as was said,this is just the new hboot. it does contain htcdev unlocksupport. thos that doesnt neccessarily mean they will ever give us a key not that it matters anyway,htcs "official unlock"only unlocks system,boot,and recovery,and is still an s-on hboot. better than nothing i guess,but since we have revolutionary and other root methods,theres no advantage to using the official unlock fomr htc.
updated OP for unroot to GB 2.11.605.5
This should be stickied. Thanks Scotty
Thanks for this. I am going to be upgrading my TB to a Droid RAZR and wanted to revert to complete stock, S-ON, unrooted for selling it on eBay. This worked perfectly.
just to be cleared to just go back to unrooted stock to receive future ota's is just follow this: will this take my s-off off..also can I reroot with revolutionary later..
the reason i want to go back to stock is the ota update notifications are getting annoying and persistent..
Putting current stock firmware and s-on back onto the phone
after getting the bootloader back to the original s-off,engineering 1.04.2000 hboot download these 2 files:
1)PG05IMG_2.11.605.5_no_hboot.zip
md5: b7ebb0b208f704c84f1224de16e61a8e
2)PG05IMG_2.11.605.5_hboot_ONLY
md5: e6df3ae14523508868dc811ecc5d4b07
rename PG05IMG_2.11.605.5_no_hboot.zip to "PG05IMG",move to your sd card,and flash in hboot.
this is important! you must flash the PG05IMG_2.11.605.5_no_hboot.zip first
after successfully flashing that,you will be on unrooted gingerbread with an eng s-off bootloader. delete the PG05IMG file from your sd card. now place the PG05IMG_2.11.605.5_hboot_ONLY on your sd card. check the md5. once youve verified it matches,you can rename PG05IMG and flash it.
again, only flash the hboot file after you have successfully flashed the rom.
now you are 100% stock on latest firmware. unrooted gingerbread 2.11.605.5 with *locked* 1.05.000 s-on bootloader.
as always,be as cautious as possible doing hboot flashes. again,please post any questions before doing anything
Did you root with revolutionary? If you currently have the 1.04.2000 Eng hboot,then yes. That will get you to stock unrooted gb. If you plan to re-root,there are stock,rooted roms you can flash in recovery,that will also stop the ota notices.
Sent from my ADR6400L using XDA Premium App
Thanks so much. Appreciate
Sent from my Nexus S using xda premium
So is there anyway to accomplish this without being able to turn the phone on? Dropped my T-Bolt over the weekend, phone looks fine but the power button is now recessed. Tried popping it back out, etc. and no dice.
Tried setting up ADB, but it isn't recognizing my device. Not sure if USB Debugging was on before, but now I have no way of checking. Tried a few tricks I read online to get the phone to power on without the power button, but none have worked.
Thoughts?
id prolly not worry about it. if it wont power on,they wont know its rooted. i believe any hardware thats not working is fixed,then the phone is flashed with current firmware.
i do not believe they will fix the phone,then turn it on to try and catch you being rooted.
either way,since you dropped it,youre looking at an insurance claim anyway. and they could care less if its rooted or not
after doing that, can I roll back it to be S-OFF/ROOT?
edited to reflect the fact that I'm an idiot who just essily fixed the problem
Problems...
So i rooted with the Original root method I do believe and have had this phone for awhile, I followed the steps as stated but after I flash the H Boot and reboot to do the first PG05IMG I get No image, wrong image, so on and so forth... I have no idea what has happened, I even grabbed another Img file from Bliynd but it still does the same...
Never had a phone do this before, its like it see's the IMG but will not load/flash it... Any help would be awesome man, sry for the trouble...
Helpful info (?)
Mecha XD ENG S-OFF
Hboot-1.04.2000 (PG0510000)
MICROP-/
Radio-1.39.00.0627r
eMMC-boot
Feb 23 2011, 20:36:02
See attachment for pic of happenings lol So much easier
There is one more line of no Image or what not after whats on the pic, I guess I took it a lil to fast...
be careful! do not just blindly flash different images or RUUs. you need to use the files i listed,and make sure you flash them in the correct order.
if the PG05IMG is on the root of the sd card there are only 2 reasons its not found:
1)sd card not FAT32
2)incorrectly named
the phone must see "PG05IMG.zip" exactly. due to the way windows usually adds and hides file extension,its common to inadvertantely name to "PG05IMG.zip.zip" or in lesser cases just "PG05IMG". note that that is a zero,not a capital O
figure out which of those 2 is your prollem and your files will flash.
a1exus said:
after doing that, can I roll back it to be S-OFF/ROOT?
Click to expand...
Click to collapse
after doing what?
I know this is beyond dumb but since rooting with recovery anything I flashed was from cwr. How do I flash pg05img.zip from hboot? Will the phone then boot up allowing me to delete the file from file manager app or do I have to delete the first pg05img.zip from the computer?
Ok, so I originally rooted my phone using the ADB method. I used your stock RUU to unroot with S-off still off. My question is what is the easiest way to get root back with s-off already off and the original root bootloader?
I've been meaning to write this guide for a little while, and someone needing it recently posted a question asking how, so I figured I'd get off my ass and do it.
This will work for Vision, Ace and Glacier devices.
NOTE: This will only work if you are TRUE S-OFF
You will need ADB set up and running to finish this off.
Also, make sure you're on charge only mode.
Flashing one of the roms provided will have that as default
Section 1: Download the appropriate rom for your device.
Obtain an appropriate rom from http://thetable.poseidon.feralhosting.com/VISION/VISION/
these are stock roms with the only change being "persist.service.adb.enable = 1" added so /system/build.prop
I modified these roms for people with broken screens/digitzers, so if you're phone is perfectly functional, go ahead and grab a rom from UNMODDED dir. Just enable adb debugging once its flashed
Section 2: Flash the rom via fastboot RUU mode.
If you don't have a fastboot executable, download the zip attached to this post, and run the one appropriate for your OS
Make sure the fastboot executable and the rom are in the same directory, and you're command prompt/terminal is pointed to that directory.
Also, make sure you don't have a PC10IMG/PD98IMG/PG15IMG on your sdcard
A. Make sure phone is powered off
B. Hold Volume Down, and press Power to run phone on
C. Wait a minute or so (while hboot scans for updates) then press Power ONCE
D. Verify you are in fastboot mode by running:
Code:
fastboot-[OS] devices
this will return your serial number if you are in fastboot mode
E. Reboot to RUU mode
Code:
fastboot-[OS] oem rebootRUU
F. Flash the rom
Code:
fastboot-[OS] flash zip [NAME].zip
This will start flashing the rom to your device.
IT (MOST PROBABLY) WILL FAIL
REPEAT THE LAST COMMAND
Code:
fastboot-[OS] flash zip [NAME].zip
G. Reboot Phone
Code:
fastboot-[OS] reboot
Section 3: Return to S-ON and original CID
A. Obtain temp-root
Download the attached psneuter and gfree zips
Code:
> adb push psneuter /data/local/tmp
> adb push gfree /data/local/tmp
> adb shell
$ cd /data/local/tmp
$ chmod 755 *
$ ./psneuter
This will kick you out of adb shell
B. Restore S-ON
If you have your part7backup-xxxxxxx.bin (check sdcard):
Code:
> adb shell
# /data/local/tmp/gfree -r /sdcard/part7backup-xxxxxxx.bin
(replace the xxxxxxx's with the correct numbers)
Rejoice! You are back to S-ON!
If you do not have your part7backup:
Find your original cid:
Code:
> adb shell
# dd if=/dev/block/mmcblk0p17 bs=1 count=8 2>/dev/null; echo
Restore S-ON and CID
Code:
# /data/local/tmp/gfree -s on -c ORIGINAL_CID
Section 4: Rejoice! And Optionally flash an official stock rom
Completely stock/unmodded roms can be found at http://thetable.poseidon.feralhosting.com/VISION/VISION/UNMODDED/
Flash them same as Section 2.
If you have any issues, need help, etc. Please join #G2ROOT on freenode
There are normally people on there all the time, but please either hang around, or come back if no one responds
Credits:
scotty2 for psneuter
scotty2 and Guhl for gfree
Setherio for the fastboot collection zip
pierre_ja for making me make those rom.zips
laga_ for how to make those rom.zips
anyone else I may've forgotten
-Nipqer
This guide is officially supported by #g2root. If you need help, join irc freenode, #g2root.
Donate to EFF
Possible errors using gfree
Hello Nipqer, cool tutorial!
An possible addition for using gfree: Make sure that the phone is in "charge only" mode. I heard that this solved some problems in the past when using "gfree -s on -c OIGINAL_CID".
Best regards,
Catherall
-----------------
HTC Desire Z with currently installed ROMs:
Virtuous Affinity 2.0.5
PyroMod's CyanogenMod 7.2 Nightly
CyanogenMod 7.1
Virtuous G-Lite 2.0.1
MIUI 1.7.22
Virtuous Quattro RC3
Added that info, charge only mode will be default anyway if they flash one of the provided roms.
-Nipqer
In step 1 For a T-Mobile G2 using http://www.ratherphallic.co.cc/ the rom I would download is 'G2_PC10IMG.zip' correct?
Also in step 2 can I flash the rom via fastboot w/o adb??? I think I rename the zip file to PC10IMG.zip correct?
Yes, use the G2_PC10IMG.
If you use fastboot, it doesn't matter how the rom is named.
If you use hboot however, then yeah it needs to be named PC10IMG.zip, and yeah, it just goes on the root of your sdcard
-Nipqer
Sent from my HTC Vision using xda premium
nice guide!
Ty for the information.
Nice guide with good downloadlink.
Hey Nipqer thank you so much, this definitely needs to be more known and used. It's the second time I need to send the phone back and I couldn't understand what to do and which files to use because the guide is for g2 and there are everywhere menaces like don't flash this/that/all pc10img with s/off.
Then pierre_ja linked me your guide and did it in ten minutes...
Edit: the bad thing is that I haven't been able to find this searching everywhere in the web....
Sent from my HTC Vision using XDA
Perfect! Thanks a lot.
When the flashing of stock rom fails it says this?
FAILED (remote: 43 main version check fail)
So its enough just to run the command again?
Hmm, that error means you're not true (radio) s-off
to resolve it you'll need to run misc_version as per this guide http://forum.xda-developers.com/showthread.php?t=1178912
-Nipqer
You were right. I was trying to flash stock rom after S-ON. The only reason I wanted to flash version w/o adb debugging on was because I couldnt update using classic Settings/Info/Update software. Everytime I got stuck on screen with red rectangle. When booting to hboot I had on top line with pink background "Locked (OOW)". I flashed stock ROM over RUU and it vanished. Everything is ok now. Fully updated stock phone.
I think I messed up things by flashing htcdev.zip. If I understand this is for people who used oficial htc unlocking method. I flashed my device back in 2011 even before it was release so I didnt know about this option.
i keep getting error message everytime i try to flash the PC10IMG.zip file doing it tru fastboot. also when i try the none adb it loads up at the boatloader but just goes back to boatloader screen . any ideas?
Whats the error message your getting?
-Nipqer
error: cannot load 'PC10IMG.zip'
i put the zip file in the same directory . platform tools
Nipqer you are the f***ing MAN thanks alot. you saved my phone. now going for a warranty. again thank you . thank you thank you.
Returning to Stock w/o S-ON
Thank you for the great guide Nipqer.
I am running CM7.2 RC version with true s-off.
I want to go back to the Stock ROM with the latest Updates but with S-OFF.
How do i achieve that???
Just download a stock rom and flash it.
S-OFF will stay no matter what you do, until you re run gfree to remove it.
If you flash a stock rom from www.ratherphallic.co.cc you should get OTA's (thought I can't guarantee that), or you could download a stock gingerbread rom from www.shipped-roms.com
-Nipqer
Sent from my HTC Vision using xda premium
Getting an error= remote : 53 image unzipping failed
after that not able to switch on the phone or anything.
was flashing Vision_DZ_1.34.405.5_PC10IMG.zip
Please Help !!!
hmm, the phone should be able to turn on fine, if it failed opening the rom to flash then it wouldn't of changed anything.
Can you run an md5 check on the downloaded rom? it might be corrupted.
Otherwise, just try a different rom.
-Nipqer
Nipqer said:
hmm, the phone should be able to turn on fine, if it failed opening the rom to flash then it wouldn't of changed anything.
Can you run an md5 check on the downloaded rom? it might be corrupted.
Otherwise, just try a different rom.
-Nipqer
Click to expand...
Click to collapse
I tried the modded rom and it worked.....thanks a lot Nipqer
This Guide will help you reset your HTC One back to 100% stock form with no trace of modifications. S-Off Required!
In order for you to be able to reset your device to complete stock it will require that you have S-Off.
For those that still have S-On and cannot gain S-Off due to having one of the updated firmwares there is not much you can do other than restore a stock rom and stock recovery. S-On users can find my 2.24.401.x stock rom with recovery included here:
http://www.htc1guru.com/2013/09/gurureset-aroma/
I am working on more versions now.
If you restore one of the stock Nandroid backups with a 1.2x version, you will probably have issues with the touch screen not working since the updated touchscreen drivers in the newer firmware updates, prevent the touch screen from working in the stock level 4.1.2 software. Keep checking the Download section for Guru Resets as I will be adding more stock rom versions.
If you have a working touch screen on the stock software, after restoring the stock kernel and stock recovery, your bootloader will show RELOCKED instead of LOCKED once you lock it.
I have easily unlocked bootloader, got S-off and super CID for many different HTC One devices from a few carriers, but that is because they came with hboot 1.44 so revone worked without issues to gain S-Off. If you buy a new phone now, regardless if what firmware version and/or software it come with, after you unlock the bootloader be sure the first thing you do is to make a Nandroid backup of your phone in its stock form. If it is a stock Nandroid on the newer 2.24.401.x base, please contact me as I would love to host it as many people could use that if not s-off.
If you are lucky enough to buy a new phone that comes with early hboot 1.44, I advise you get S-off right after you make that stock Nandroid backup. S-off really comes in handy for so many things. There is no danger of bricking your phone unless you start flashing things you don;t understand and other actions without fully understanding the repercussions. If you are unsure about something then just make a post and someone here should be able to provide you with the correct information.
If you don’t know what these terms mean do a search, they have been answered many, many times. Here are some quick links to some common items for modifications::
–Easily unlock bootloader, flash custom recovery, flash ROM, and ADB sideload (in case you forgot to copy your ROM to your phone) plus much more:
http://forum.xda-developers.com/showthread.php?t=2242635
–Easily get S-off by using revone (We will also use this tool reset Security back to S-On)
http://forum.xda-developers.com/showthread.php?t=2314582
***I advise you to get S-off before doing anything else and keep S-off unless you are going to return the device. The latest OTA/firmware contains an hboot that revone will not currently unlock, but if you have s-off you can downgrade your hboot if needed***
–Easily get Super CID
http://forum.xda-developers.com/showthread.php?t=2317536
Now you can do some of these things easily:
*Remove red warning from boot screen + custom hboot:
http://forum.xda-developers.com/showthread.php?t=2316726
http://forum.xda-developers.com/showthread.php?t=2156368
*Flash custom splash screens:
http://forum.xda-developers.com/showthread.php?t=2324746
*Flash new firmware:
Concise and easy for noobs: http://forum.xda-developers.com/showpost.php?p=43551752&postcount=5082
Also http://forum.xda-developers.com/showpost.php?p=43328416&postcount=33758
Post #2 has the download for the custom firmware to flash without screwing anything else up:
http://forum.xda-developers.com/showthread.php?t=2182823
______________________________________________________________________________________
Resetting your device to stock
—————————————————————————
So now for the good stuff. You totally modded the hell out of your One and something happens where you need to return the device to your carrier/vendor. First thing, always go to your carrier/vendor for hardware exchanges NOT direct to HTC. For the most part US carriers don’t care much about modded software on the devices in regards to warranty but HTC does. However just because the person in the device exchange center doesn’t check for root, doesn’t mean someone won’t flag your phone when repairing it. So why take the chance, it only takes a few minutes to return to 100% stock.
Secondly unless your device is totally unusable, I advise you to call the ATT(or your carrier) warranty number and they will send you a replacement and a return shipping label, and then you have 12 days to return it. This way you can access data and settings on your first device if needed and make sure that everything is cool with your replacement before you reset your first device to stock and send it back.
As it is required for most of the modifications mentioned above these steps require that you have your devices drivers installed on your PC and also ADB. If you need help setting up ADB: http://forum.xda-developers.com/showthread.php?t=1427008
---Instructions for returning to 100% stock from S-off:
Before we begin please note that these instructions are for a device with S-off and the stock CID. Your CID should be stock unless you changed it in order to get a specific country/region OTA or as a lot do for flashing ease and just use Super CID.
In order to run the RUU to reset everything to stock, the CID will have to match the device for which the RUU was intended.
So you can’t really mess anything up because if your CID is not correct the RUU will not run and not flash anything.
**-Technically if you have S-off you can run any RUU and it should run fine but your phones image won’t be stock from your carrier if not the correct RUU. I like to set the stock CID back now so we don’t forget. However if using another variant/RUU, since you are s-off, you can do this step after running the RUU.**
If you have stock CID or the CID matches the RUU you can proceed to step 1.
If you have any other CID you need to change it before beginning. In this example I am talking about the US ATT variant for which he stock CID is CWS__001
Code:
adb reboot-bootloader
Phone should boot to the bootloader. Now run:
Code:
fastboot oem writecid CWS__001
Now verify that the stock CID shows on the bootloader screen by running:
Code:
fastboot reboot-bootloader
Reboot device if CID on bootloader screen shows the stock CID. If not retry
*****The next step will wipe the entire contents of the device which includes all of your data. Be sure to back it up to a PC so you can transfer it onto the new device if needed.*****
These instructions are assuming you are running a Windows OS. If you are not then these exe RUU’s won’t be of much use. You will have to use the RUU.zip files which can accomplish the same results as a RUU from flashing in fastboot. You can replace step 1 below with these steps:
Restoring using a RUU.zip
Download the RUU.zip file and place in your ADB/fastboot folder. I would recommend renaming the zip file to something simple like ruu.zip.
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
Code:
adb reboot-bootloader
Now use these fastboot commands:
Code:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the ruu.zip file:
Code:
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
Code:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
Code:
fastboot reboot
or
Code:
fastboot reboot-bootloader
**Notes about the RUU.zip method. You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first. If you are running the RUU.zip as base to downgrade all your firmware because you are going to then going to restore a stock Nandroid so the RUU might not be made for your MID, so you may need to edit the android-info.txt inside the ruu.zip to include your MID or CID.
Restoring using a RUU.exe
1. - Now we need to download the RUU (ROM Update Utility) that flash our device back to mostly stock. It can be downloaded HERE for US AT&T users. Other carriers should be able to find their appropriate RUU in this thread:
http://forum.xda-developers.com/showthread.php?t=2428276 or here: http://www.htc1guru.com/downloads/
If there is not a RUU for your phone, but there is a Stock Nandroid backup, you should still complete the step above. Just make note of your original CID and change yours to CWS__001 so the RUU will run. This will reset all your firmware and other modifications (like modified hboot and splash screens) back to the default stock level regardless of region.
Once downloaded run the RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe and it will guide you through resetting the device. After it finishes your device will be almost back to stock. It will have the stock images for recovery, boot, ROM, radio, firmware hboot, etc.
Stock Nandroid restores will require these additional steps before proceeding to step 2:
When you ran the RUU (Either EXE or ZIP) all data was wiped and your custom recovery was reset back to stock, It is recommended to keep this stock recovery in place and use a command that only works on the hboot 1.44 (which you know have form the RUU)
Download the latest version of the recovery that matches the stock Nandroid backup (Either CWM or TWRP) and place it in your ADB/fastboot folder.
Now use this command to boot that custom recovery without installing it:
Code:
fastboot boot TWRP.img or fastboot boot CWM.img
It should load the custom recovery. Now make a test backup and allow it to complete.
Now boot your phone (Do not take OTA updates if prompted) and look to see where exactly the recovery placed the backup. You can install a simple file manager from the play store for this. Take note of the location and folder structure that the recovery has used for the backup.
Now copy the downloaded stock backup files from your PC to that location in the last step. Be sure the folders are in the correct place.
Now reboot into the bootloader and then boot the custom recovery again using that same command as before:
Code:
fastboot boot TWRP.img or fastboot boot CWM.img
Restore the backup and reboot when finished. Important – Do not accept any OTA updates until the complete phone reset process is finished.
Now delete all your backup files and installed applications by doing a factory reset from Settings – Backup and Reset – Erase All Data From Phone. Software and firmware on your phone should be back to stock and you can continue with the next step in the guide.
**Before continuing with the guide make sure you have changed your CID back to stock if you changed it to a non stock one in order to run a RUU to downgrade firmware.**
******If you continue with the next 2 steps to lock the bootloader and you do not have a stock hboot, you will instantly BRICK your device. Shouldn't be an issue if the RUU ran correctly, however you may want to boot into the bootloader and verify that it shows version 1.44.0000 for the hboot. Also your custom recovery should be gone and back to stock (If you boot into the stock recovery it will just look like a red warning triangle with no options). If you are still able to boot into your custom recovery, it is a sign that not all partitions have been flashed back to stock and you should find out why before proceeding]******
Now that we have lots of users who have S-Off from other methods than revone, mainly the new rumrunner method here are the generic instructions for any S-Off device and not just for user with revone:
Before you can proceed with the 2 following threads for removing Tampered and then Locking you need to have Superuser installed. There are links to how to do this in each thread. You can also use this toolkit. Just remember to delete the SuperUser and busybox apk if installed before you return the phone.
2. - First remove the Tampered Flag. Instructions are in this thread
http://forum.xda-developers.com/showthread.php?t=2477792
3. - Second Lock the bootloader. Instructions are in this thread
http://forum.xda-developers.com/showthread.php?t=2475914
The older REVONE commands/instructions for Tampered and Locking:
I recommended using revone to gain S-off, so that is how we will undo it. If you don't still have it we will need the revone file again. It can be downloaded here: http://revolutionary.io/revone (From thread: http://forum.xda-developers.com/showthread.php?t=2314582and http://forum.xda-developers.com/showthread.php?t=2315467)
Push revone to your device:
Put the downloaded revone file in your adb/fastboot folder and push it using this command:
Code:
adb push revone /data/local/tmp/
open a adb shell by typing:
Code:
adb shell
Now change to that directory:
Code:
cd /data/local/tmp
Now set permissions
Code:
chmod 755 revone
Now re-lock the bootloader:
Code:
./revone -l
Remove Tampered flag:
Code:
./revone -t
The newer revisions of revone don't do the actual locking any longer but it should output the command you need to run to fully re-lock:
Type exit to exit the adb shell session and issue the command to re-lock the device:
Code:
fastboot oem writesecureflag 3
Now verify that it worked by booting into the bootloader:
Code:
adb reboot bootloader
You should see it say LOCKED at the top and S-On, just like it was out of the box!
I doubt anyone at the warranty repair center is going to snoop around a device that says Locked and S-On, but I like to cleanup and remove the revone file.
Just reboot the phone and skip over the setup wizard
Now start another adb shell session:
Code:
adb shell
Now change back to the folder where we put revone
Code:
cd /data/local/tmp
Now run this command to delete the revone file
Code:
rm revone
Now since you had to install SuperUser to perform the previous 2 steps make sure you unroot by deleting the Superuser.apk and busybox.apk (If installed) from the /system/app folder and also the su binary from /system/xbin on your phone.
If you ran a RUU your systems firmware and software is all reset back to stock. If you restored via Stock ROM reset or Nandroid you should be running the stock software but it could be on non stock (version mismatch) firmware.
In either case your bootloader should display Locked and no Tampered just like out of the box. Now all that’s left is to S-On. To do that issue this fastboot command:
Code:
fastboot oem writesecureflag 3
Done - device should be just like it was out of the box with no indication of any modding.
*******I am not responsible for any problems you encounter. I am simply informing you of what is needed to complete a restoration to Stock. Read all steps and commands carefully and perform them in the correct order.********
Credits/Thanks
Thanks to all those with threads I mentioned that contain great info and support. Especially scotty1223 for his Tampered removal and Locking threads.
This Guide is always available at my site: http://www.htc1guru.com/guides/return-stock-guide/
[EDIT]9-10-13 Post overhaul with how to combine Nandroid and RUU process to reset.
[EDIT]10-19-13 Post was changed to reflect new S-off, so changed the Tampered and Locking steps from revone
Great guide, this should be a sticky!
Kindly excuse me and no offense to the OP. But if you have S-OFF, all you have to do is change your CID back to your original and then run the RUU and you are nearly done Next thing is you have to lock the bootloader and have S-ON and that is it. You are now back to stock.
Very helpful guide. But it can't be said enough times YOU WILL BRICK YOUR DEVICE going S-ON with a non-stock HBOOT
The guide does mention this in the relevant section, but it should probably be noted somewhere near the top of the OP. In big red letters.
Sent from my HTC One using xda app-developers app
NxNW said:
Very helpful guide. But it can't be said enough times YOU WILL BRICK YOUR DEVICE going S-ON with a non-stock HBOOT
The guide does mention this in the relevant section, but it should probably be noted somewhere near the top of the OP. In big red letters.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
That's why I think it's safer to just run the RUU because that will flash the stock HBOOT and then you can have S-ON back without the worry of bricking the device.
Nice work. But this block is incorrect and may lead to problems:
crushalot said:
2. - You will need the stock splash screen so we need to do the same procedure as above with the stock splash screen. Download the stock splash screen here: http://d-h.st/F7H (From thread:http://forum.xda-developers.com/showthread.php?t=2324746)
Rename the file so it has no spaces like stock_splash.zip and put it in your ADB/fastboot folder.
Reboot into bootloader:
Code:
adb reboot bootloader
Now run this command:
Code:
fastboot oem rebootRUU
You should see the screen turn to a silver HTC logo. Now run this command:
Code:
fastboot flash zip stock_splash.zip
If you get an output in the console that says "(bootloader) ...... Successful" proceed to next step. If any errors use this thread for troubleshooting: http://forum.xda-developers.com/showthread.php?t=2324746
Click to expand...
Click to collapse
Those splashes in my thread are designed to be flashed in recovery. They will not work in RUU mode because the zip file is constructed incorrectly for it. Best approach would be to just flash the stock splash in recovery in step one.
Alternatively, keep the instructions as is and use the stock splash from this post: http://forum.xda-developers.com/showpost.php?p=42374127&postcount=1
iElvis said:
Nice work. But this block is incorrect and may lead to problems:
Those splashes in my thread are designed to be flashed in recovery. They will not work in RUU mode because the zip file is constructed incorrectly for it. Best approach would be to just flash the stock splash in recovery in step one.
Alternatively, keep the instructions as is and use the stock splash from this post: http://forum.xda-developers.com/showpost.php?p=42374127&postcount=1
Click to expand...
Click to collapse
Yes, you are right sorry. So many threads I messed up the link. Kinda the reason I wanted to put all this in one place. I will update the OP and revise the first few steps to make it easier since the RUU should include the stock hboot and splash.
Thanks for all the feedback.
I thought you needed SU permission to run revone? Am I mistaken?
Do you need root access to push revone to the /data/local/tmp directory?
After running the RUU.exe file, wouldn't you lose root?
I just want to double check.
Dan37tz said:
I thought you needed SU permission to run revone? Am I mistaken?
Do you need root access to push revone to the /data/local/tmp directory?
After running the RUU.exe file, wouldn't you lose root?
I just want to double check.
Click to expand...
Click to collapse
No you don't need root to use it as it has a root hack in the binary itself. That's why in ieftm's post on the usage of revone to S-off has optional wording on step 3
"3. (optional) If your device is unlocked and rooted please switch to root using su."
However I can confirm that it has worked better for me when I didn't run it as SU.
No you do not need root to push files using adb, well at least not to /data. You probably would to push to /system
Correct, after running the RUU you lose root. That is why I manually flashed the hboot and splash back myself while still on my rooted rom with utilities and most importantly a recovery in which I could use to get back running and try again if something failed.
Rex2369 said:
Kindly excuse me and no offense to the OP. But if you have S-OFF, all you have to do is change your CID back to your original and then run the RUU and you are nearly done Next thing is you have to lock the bootloader and have S-ON and that is it. You are now back to stock.
Click to expand...
Click to collapse
Thanks updated post to simplify.
NxNW said:
Very helpful guide. But it can't be said enough times YOU WILL BRICK YOUR DEVICE going S-ON with a non-stock HBOOT
The guide does mention this in the relevant section, but it should probably be noted somewhere near the top of the OP. In big red letters.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks but the updated post now avoids the possibility as we just let RUU flash all stock parts
Rex2369 said:
That's why I think it's safer to just run the RUU because that will flash the stock HBOOT and then you can have S-ON back without the worry of bricking the device.
Click to expand...
Click to collapse
Thanks. Reflected in updated OP
Very nice!!! Concise and to the point!!! THANK YOU !!!
It worked like a charm, I have AT&T Version, had S-ON, SuperCID, 1.29.401.12 firmware (not AT&T), and custom ROM. This brought me back right to Stock.
Now back to AT&T, my camera lens on the inside for some reason got hazy with a hue to it after having the phone for about a month.
To the OP you have done well. Hope to see more tutorials from you.
Sent from my HTC One
great guide!
TIP for Mac Users: I couldn't get the RUU to run in Windows 7 or Windows 8 VMware environments, but Windows XP did the trick.
Use VMWare with Windows XP Pro SP3.
what ruu i need for HTC_001?
what ruu i need for HTC_001?
So running RUU does not remove S-OFF? Also does updating from stock 4.1.2 to 4.2.2 with the official OTA remove S-OFF? I want to try the OTA but I'm a bit paranoid about losing the lovely S-OFF .
No running the RUU does not remove S-off. It just resets everything else except bootloader and Security (S-off) back to stock form.
The 4.2.2 OTA does not remove remove S-off, however if you have s-off I would recommend running a custom ROM as they are already way better than the stock 4.2.2 rom.
If you want a pure stock like rom that is 4.2.2 based and better than the HTC version I would recommend ARHD or RGUI. If you like to be able to customize things a little but stay close to stock then TrickDroid is they way to go. If you really like to tinker and customize than Viper will blow your mind.
tomer861 said:
what ruu i need for HTC_001?
Click to expand...
Click to collapse
from the CID, I assume your in Europe somewhere. What is your location and carrier?
Others that I saw with that CID said there is no RUU for that CID yet. I am not sure is that has changed or not. You will have to read through this thread:
http://forum.xda-developers.com/showthread.php?p=39588860
They at least have a nandroid backup of a HTC__001 so you could restore that and as long as your hboot, splash screen and firmware are stock, you could proceed with relocking.
isnt it possible to get completly back to the way it was by putting back a nandroid backup by clockwork? (by starting clockwork, not with the flashed version)
borgqueenx said:
isnt it possible to get completly back to the way it was by putting back a nandroid backup by clockwork? (by starting clockwork, not with the flashed version)
Click to expand...
Click to collapse
Not impossible. I just went back to stock on my first HTC One using TWRP. After restoring I flashed the stock recovery, used revone to lock the bootloader and put S-ON.