Related
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
WARNING: DO AT YOUR OWN RISK. IF YOU DO NOT KNOW ANYTHING ABOUT FASTBOOT, ADB, OR RUUS, DON'T TRY THIS, IT CAN BRICK YOUR PHONE! I WILL NOT BE RESPONSIBLE FOR YOU SCREWING YOUR PHONE UP!
So I ran into a problem recently. My volume up button doesn't work anymore, and without that, there was no way for me to flash the newest leaked radio (have to press volume up to confirm flash in bootloader)
drowe set me on the write path, and after a little more research, I figured it out.
(I use Linux for everything I do with my phone, so all commands are for Linux, but will be very close for Windows)
This guide assumes you have ADB set up, and proper udev rules set up. I will not be showing you how to set up ADB or udev rules, so don't ask. Please Google it.
First, download your desired PG05IMG.zip, and CHECK MD5SUMS!!!!
To do this (only in Linux), in terminal, go to the directory your .zip is in, and type:
Code:
md5sum PG05IMG.zip
It will output the md5sum. Compare it to what it should be. If it doesn't match, DO NOT FLASH IT!
No, with your phone plugged in, do the following commands:
Code:
adb reboot bootloader
(allow to reboot into the bootloader. When complete, it should say "fastboot" in red
Code:
fastboot oem rebootRUU
(allow to reboot. You will see the HTC logo)
Code:
fastboot flash zip PG05IMG.zip
(allow the operation to run. When its finished, it will say "finished." in the terminal)
Code:
fastboot reboot
It will now reboot the phone, and all should be good.
I used this guide as reference when writing this: http://androidforums.com/thunderbolt-all-things-root/480350-easier-way-flash-pg05img-files.html
Hey man, thanks a whole lot for that!! I was able to install the latest radio file onto my phone because my volume up key is broken too. So thank you!!!! It worked like a charm!
meblah741 said:
Hey man, thanks a whole lot for that!! I was able to install the latest radio file onto my phone because my volume up key is broken too. So thank you!!!! It worked like a charm!
Click to expand...
Click to collapse
Not a problem. Glad it helped you.
Sent from my ADR6400L using xda premium
This is gonna be a lengthy tutorial, I'll be very clear and specific in my details and requirements, you are entirely responsible for what you do to your device, I can confirm here works and the end result is a completely stock device which is updateable, etc, any mistakes, missed steps and any other user error is your fault, so read and follow instructions carefully, that is all. Links for files, requirements, etc will be provided at the end of this tutorial.
Let's begin:
Requirements:
1. Nandroid backup of T-Mobile stock 1.27 rom, since we have no ruu to work with, link provided. (credit to whomever uploaded it)
2. CWM recovery along with ROM manager from the playstore, I may or may not make a flashable zip of the nandroid, depends on when I get time to do so.
3. Root and s-off
4. revone s-off tool (bin file to be specific)
5. a pc or some other way of unzipping the nandroid backup, do not use your device to unzip it, it may or may not unzip correctly, chances are you'll waste your time unzipping over and over pointlessly.
6. adb toolkit (mini kit at the end)
7. knowledge on how to use adb, etc is a plus.
8. KNOW HOW TO READ
9. An HTC one that's at least rooted.
10. Patience
Steps:
1. Gather all your required files, take the all in one toolkit I link which contains revone, adb, stock recovery and cwm. You can placed the downloaded nandroid wherever you want to.
2. Unzip the nandroid backup and place it on the internal memory of the device in the "sdcard/clockworkmod/backup/" folder, do not rename the unzipped file.
3. Run the cwm flash script to replace your recovery with cwm touch recovery, device needs to be in android, not fastboot, device will reboot to android upon successfully flashing cwm recovery.
4. Open rom manager and select "Manage and Restore Backups", it should detect the nandroid, select it and choose to restore, let the device reboot and restore the nandroid.
5. Once complete, do a factory reset(optional) and reboot
6. Next step would be to flash the stock recovery by using the script provided followed by the stock hboot, if hboot flashing fails look at the bottom for the step to fix this.
7. now that's we're on stock recovery and stock rom, our next step would be to lock the bootloader and put the device to s-on, this is where it get's technical:
Lock bootloader using revone:
1. open a command prompt then cd to the folder of your mini sdk, example: cd C:/Users/Random Name/Downloads/mini-sdk
2. In the command prompt window push the revone bin file via "adb push revone /data/local/tmp"
3. Open adb shell: adb shell
4. then: cd /data/local/tmp
5. followed by: chmod 755 revone
6. then: ./revone -P
7. once it reports success it should say whether it requires reboot or not: ./revone -s 0 -l (this changes the bootloader status to **Locked**, -t to remove tamper, -u to **Unlocked** and S-Off, -r for **Relocked**, use as required)
8. Bootloader is now back to locked status, type: reboot bootloader
S-On
Device will be in fastboot mode where you should see **Locked** follow below it by S-Off
1. To change it to s-on, in the command prompt type: fastboot oem writesecureflag 3
2. then fastboot reboot
3. Device will boot into android, you will be prompted by a software update, which you can do at your own leisure whether you'd like to or not, your call.
Voila, you're back on Official stock, completely untouched device.
Optional steps, if needed.
Back to Stock CID:
While in fastboot use the command: fastboot oem writecid T-MOB010 (this needs to be done before you s-off) (script provided)
Flashing stock firmware package
Now flashing this package may fail, it is to be done while you're s-off.
You may flash the firmware.zip package via command line by the following commands:
1. fastboot oem rebootRUU
2. fastboot flash zip firmware.zip (this is named tmo.zip in the package)
3. fastboot reboot-bootloader
(was it a success?, if yes, proceed to locking the bootloader and s-on)
IF flashing the firmware package fails, flash the hboot manually via the command below (hboot provided in a separate zip in case of this):
1. fastboot oem rebootRUU
2. fastboot flash zip boot.zip
3. fastboot reboot-bootloader
should this fail as well, run the super cid script, re-do the above steps, then run the stock tmo cid script.
Then proceed with s-on/lock bootloader. There are a few kinks to be worked out, sadly I have not the time to do this at the moment.
Nandroid backup: https://mega.co.nz/#!gpIFGR7L!c5o74Ex6k3wkVlWKWgSrJBrguShtjHXeB6YQPmoqAmM (credit to uploader, I'll look for the correct screen name as soon as I can)
In case of no signal: which shouldn't be flash a radio: http://forum.xda-developers.com/showthread.php?t=2245615
Mini sdk with scripts: http://d-h.st/z8c
Revone: http://forum.xda-developers.com/showthread.php?t=2314582
NOTE: Video coming soon, credits whomever until I give it accordingly, this was put together in a rush, so didn't get the chance to look see at all the screenies, screenshots and video to come.
dark nightmare said:
this is gonna be a lengthy tutorial, i'll be very clear and specific in my details and requirements, you are entirely responsible for what you do to your device, i can confirm here works and the end result is a completely stock device which is updateable, etc, any mistakes, missed steps and any other user error is your fault, so read and follow instructions carefully, that is all. Links for files, requirements, etc will be provided at the end of this tutorial.
Let's begin:
Requirements:
1. Nandroid backup of t-mobile stock 1.27 rom, since we have no ruu to work with, link provided. (credit to whomever uploaded it)
2. Cwm recovery along with rom manager from the playstore, i may or may not make a flashable zip of the nandroid, depends on when i get time to do so.
3. Root and s-off
4. Revone s-off tool (bin file to be specific)
5. A pc or some other way of unzipping the nandroid backup, do not use your device to unzip it, it may or may not unzip correctly, chances are you'll waste your time unzipping over and over pointlessly.
6. Adb toolkit (mini kit at the end)
7. Knowledge on how to use adb, etc is a plus.
8. Know how to read
9. An htc one that's at least rooted.
10. Patience
steps:
1. Gather all your required files, take the all in one toolkit i link which contains revone, adb, stock recovery and cwm. You can placed the downloaded nandroid wherever you want to.
2. Unzip the nandroid backup and place it on the internal memory of the device in the "sdcard/clockworkmod/backup/" folder, do not rename the unzipped file.
3. Run the cwm flash script to replace your recovery with cwm touch recovery, device needs to be in android, not fastboot, device will reboot to android upon successfully flashing cwm recovery.
4. Open rom manager and select "manage and restore backups", it should detect the nandroid, select it and choose to restore, let the device reboot and restore the nandroid.
5. Once complete, do a factory reset(optional) and reboot
6. Next step would be to flash the stock recovery by using the script provided followed by the stock hboot, if hboot flashing fails look at the bottom for the step to fix this.
7. Now that's we're on stock recovery and stock rom, our next step would be to lock the bootloader and put the device to s-on, this is where it get's technical:
Lock bootloader using revone:
1. Open a command prompt then cd to the folder of your mini sdk, example: Cd c:/users/random name/downloads/mini-sdk
2. In the command prompt window push the revone bin file via "adb push revone /data/local/tmp"
3. Open adb shell: Adb shell
4. Then: Cd /data/local/tmp
5. Followed by: Chmod 755 revone
6. Then: ./revone -p
7. Once it reports success it should say whether it requires reboot or not: ./revone -s 0 -l (this changes the bootloader status to **locked**, -t to remove tamper, -u to **unlocked** and s-off, -r for **relocked**, use as required)
8. Bootloader is now back to locked status, type: Reboot bootloader
s-on
device will be in fastboot mode where you should see **locked** follow below it by s-off
1. To change it to s-on, in the command prompt type: Fastboot oem writesecureflag 3
2. Then fastboot reboot
3. Device will boot into android, you will be prompted by a software update, which you can do at your own leisure whether you'd like to or not, your call.
Voila, you're back on official stock, completely untouched device.
Optional steps, if needed.
Back to stock cid:
While in fastboot use the command: Fastboot oem writecid t-mob010 (this needs to be done before you s-off) (script provided)
flashing stock firmware package
now flashing this package may fail, it is to be done while you're s-off.
You may flash the firmware.zip package via command line by the following commands:
1. Fastboot oem rebootruu
2. Fastboot flash zip firmware.zip (this is named tmo.zip in the package)
3. Fastboot reboot-bootloader
(was it a success?, if yes, proceed to locking the bootloader and s-on)
if flashing the firmware package fails, flash the hboot manually via the command below (hboot provided in a separate zip in case of this):
1. Fastboot oem rebootruu
2. Fastboot flash zip boot.zip
3. Fastboot reboot-bootloader
should this fail as well, run the super cid script, re-do the above steps, then run the stock tmo cid script.
Then proceed with s-on/lock bootloader. There are a few kinks to be worked out, sadly i have not the time to do this at the moment.
Nandroid backup: https://mega.co.nz/#!gpifgr7l!c5o74ex6k3wkvlwkwgsrjbrgushtjhxeb6yqpmoqamm (credit to uploader, i'll look for the correct screen name as soon as i can)
in case of no signal: Which shouldn't be flash a radio: http://forum.xda-developers.com/showthread.php?t=2245615
mini sdk with scripts: http://d-h.st/z8c
revone: http://forum.xda-developers.com/showthread.php?t=2314582
note: Video coming soon, credits whomever until i give it accordingly, this was put together in a rush, so didn't get the chance to look see at all the screenies, screenshots and video to come.
Click to expand...
Click to collapse
you the best! Thanks
I assume if i replace the at&t nandroid with a bell nandroid one i can restore to bell following the rest of the steps?
redzone321 said:
I assume if i replace the at&t nandroid with a bell nandroid one i can restore to bell following the rest of the steps?
Click to expand...
Click to collapse
Yup, you just need to know what the bell cid is, in case you changed to super cid.
I'm getting an MD5 mismatch in CWM...should I just try downloading again
mcdsmaster8824 said:
I'm getting an MD5 mismatch in CWM...should I just try downloading again
Click to expand...
Click to collapse
You can try unzipping via computer and not your phone, if you absolutely have to use your phone, you can try zarchiver, otherwise, may be a bad download.
Hi,
Great that we have this thread.
Should flashing back to stock t-mobile firmware be a step in case someone flashed another firmware package during their many travels of flashing their device? I'm thinking some people may have tried out latest firmware packages like 2.17 or 2.24 and I'm thinking flashing a 1.27.531.x nandroid may not work on a higher firmware package?
http://forum.xda-developers.com/showthread.php?t=2355814
TMOUS Custom Firmware Package - 1.27.531.8
Sent from my HTC One using Tapatalk 2
gustav30 said:
Hi,
Great that we have this thread.
Should flashing back to stock t-mobile firmware be a step in case someone flashed another firmware package during their many travels of flashing their device? I'm thinking some people may have tried out latest firmware packages like 2.17 or 2.24 and I'm thinking flashing a 1.27.531.x nandroid may not work on a higher firmware package?
http://forum.xda-developers.com/showthread.php?t=2355814
TMOUS Custom Firmware Package - 1.27.531.8
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I already thought of that, hence the firmware package in the bottom notes.
My bad for not reading all the way through! Glad we have this.
Sent from my HTC One using Tapatalk 4 Beta
Thanks for this great guide!
Would it be possible to add a section for restoring to the stock bootloader for anyone like me who flashed to Google Edition RUU (which replaces boot/recovery/ROM)?
dozybolox13 said:
Thanks for this great guide!
Would it be possible to add a section for restoring to the stock bootloader for anyone like me who flashed to Google Edition RUU (which replaces boot/recovery/ROM)?
Click to expand...
Click to collapse
Bootloader/recovery/stock rom are all a part of this guide buddy, the hboot section is your bootloader, there's the recovery section right there as well (last step before s-on/locked status) and the nandroid that you'll be restoring is the stock rom, once I get time tonight, I'll work on making the nandroid a flashable rom instead to make things easier.
Worked perfectly, thanks!
thank you!
Nandroid backup is "temporary unavailable" on mega - can you post a mirror?
Thanks
Edit: Was able to finally download with megadownloader and restore my device - your guide worked brilliantly, thanks!
I have a problem
Dark Nightmare said:
This is gonna be a lengthy tutorial, I'll be very clear and specific in my details and requirements, you are entirely responsible for what you do to your device, I can confirm here works and the end result is a completely stock device which is updateable, etc, any mistakes, missed steps and any other user error is your fault, so read and follow instructions carefully, that is all. Links for files, requirements, etc will be provided at the end of this tutorial.
Let's begin:
Requirements:
1. Nandroid backup of T-Mobile stock 1.27 rom, since we have no ruu to work with, link provided. (credit to whomever uploaded it)
2. CWM recovery along with ROM manager from the playstore, I may or may not make a flashable zip of the nandroid, depends on when I get time to do so.
3. Root and s-off
4. revone s-off tool (bin file to be specific)
5. a pc or some other way of unzipping the nandroid backup, do not use your device to unzip it, it may or may not unzip correctly, chances are you'll waste your time unzipping over and over pointlessly.
6. adb toolkit (mini kit at the end)
7. knowledge on how to use adb, etc is a plus.
8. KNOW HOW TO READ
9. An HTC one that's at least rooted.
10. Patience
Steps:
1. Gather all your required files, take the all in one toolkit I link which contains revone, adb, stock recovery and cwm. You can placed the downloaded nandroid wherever you want to.
2. Unzip the nandroid backup and place it on the internal memory of the device in the "sdcard/clockworkmod/backup/" folder, do not rename the unzipped file.
3. Run the cwm flash script to replace your recovery with cwm touch recovery, device needs to be in android, not fastboot, device will reboot to android upon successfully flashing cwm recovery.
4. Open rom manager and select "Manage and Restore Backups", it should detect the nandroid, select it and choose to restore, let the device reboot and restore the nandroid.
5. Once complete, do a factory reset(optional) and reboot
6. Next step would be to flash the stock recovery by using the script provided followed by the stock hboot, if hboot flashing fails look at the bottom for the step to fix this.
7. now that's we're on stock recovery and stock rom, our next step would be to lock the bootloader and put the device to s-on, this is where it get's technical:
Lock bootloader using revone:
1. open a command prompt then cd to the folder of your mini sdk, example: cd C:/Users/Random Name/Downloads/mini-sdk
2. In the command prompt window push the revone bin file via "adb push revone /data/local/tmp"
3. Open adb shell: adb shell
4. then: cd /data/local/tmp
5. followed by: chmod 755 revone
6. then: ./revone -P
7. once it reports success it should say whether it requires reboot or not: ./revone -s 0 -l (this changes the bootloader status to **Locked**, -t to remove tamper, -u to **Unlocked** and S-Off, -r for **Relocked**, use as required)
8. Bootloader is now back to locked status, type: reboot bootloader
S-On
Device will be in fastboot mode where you should see **Locked** follow below it by S-Off
1. To change it to s-on, in the command prompt type: fastboot oem writesecureflag 3
2. then fastboot reboot
3. Device will boot into android, you will be prompted by a software update, which you can do at your own leisure whether you'd like to or not, your call.
Voila, you're back on Official stock, completely untouched device.
Optional steps, if needed.
Back to Stock CID:
While in fastboot use the command: fastboot oem writecid T-MOB010 (this needs to be done before you s-off) (script provided)
Flashing stock firmware package
Now flashing this package may fail, it is to be done while you're s-off.
You may flash the firmware.zip package via command line by the following commands:
1. fastboot oem rebootRUU
2. fastboot flash zip firmware.zip (this is named tmo.zip in the package)
3. fastboot reboot-bootloader
(was it a success?, if yes, proceed to locking the bootloader and s-on)
IF flashing the firmware package fails, flash the hboot manually via the command below (hboot provided in a separate zip in case of this):
1. fastboot oem rebootRUU
2. fastboot flash zip boot.zip
3. fastboot reboot-bootloader
should this fail as well, run the super cid script, re-do the above steps, then run the stock tmo cid script.
Then proceed with s-on/lock bootloader. There are a few kinks to be worked out, sadly I have not the time to do this at the moment.
Nandroid backup: https://mega.co.nz/#!gpIFGR7L!c5o74Ex6k3wkVlWKWgSrJBrguShtjHXeB6YQPmoqAmM (credit to uploader, I'll look for the correct screen name as soon as I can)
In case of no signal: which shouldn't be flash a radio: http://forum.xda-developers.com/showthread.php?t=2245615
Mini sdk with scripts: http://d-h.st/z8c
Revone: http://forum.xda-developers.com/showthread.php?t=2314582
NOTE: Video coming soon, credits whomever until I give it accordingly, this was put together in a rush, so didn't get the chance to look see at all the screenies, screenshots and video to come.
Click to expand...
Click to collapse
I tried this on my Htc one and it didn't work. i accidentally formatted my data and when i try to reboot it says no os installed. I tried side loading it, and tried flash zip, but i still could load into any rom. Please help.
ro34po43 said:
I tried this on my Htc one and it didn't work. i accidentally formatted my data and when i try to reboot it says no os installed. I tried side loading it, and tried flash zip, but i still could load into any rom. Please help.
Click to expand...
Click to collapse
What recovery are you using and what rom are you trying to sideload with? If you're gonna safely sideload, use twrp and a stock rom.
Thank you so much for this!
Just out of curiosity, have you had time to upload any screenshots or a video of the process yet?
idonthavetimeforthis said:
Thank you so much for this!
Just out of curiosity, have you had time to upload any screenshots or a video of the process yet?
Click to expand...
Click to collapse
Like your name he doesn't have time for it
thank you
thank you very much for writing this organized tutorial - there could be a little more detail about how to flash the recovery's for those that don't use windows (easy enough to open the bat scripts), but very good and very convenient to have all the files in one place
thanks again
I didn't bother reading the entire thread, so if there's a link I apologize, but I'm another sad soul who took the T-Mobile 1.27.531.11 update. Whomp whomp. Well anywho. In my many attempts to S-Off, I've become well versed in restoring back to stock. So if you're stuck and don't know what to do, PM me and I shall help thee! I will provide links to stock/custom recoveries, the .11 RUU, and walk ya through it
Sent from my HTC One using xda app-developers app
Hi, I am S-off with unlocked bootloader, but I need to return my Verizon HTC 10, so I need to go back to S-on with locked bootloader. I am sure there is a thread on this, but I can't find it. Can anybody point me in the right direction?
legaldeejay said:
Hi, I am S-off with unlocked bootloader, but I need to return my Verizon HTC 10, so I need to go back to S-on with locked bootloader. I am sure there is a thread on this, but I can't find it. Can anybody point me in the right direction?
Click to expand...
Click to collapse
I am assuming you used Sunshine to S-OFF your device. If so, it should be relatively simple to fully restore your phone to stock, just be sure to perform the following steps in order.
Please note that I am in absolutely no way responsible for any damage done to your device as a result of following these instructions. Do not proceed to read the following post or attempt to perform the procedure described below if you do not accept this agreement. I am not responsible for your actions in any manner!
note: all commands are to be entered without quotation or ' ' marks
-Flash a full stock Verizon RUU zip over your current setup to clear any modified flags, unroot, etc. Links and instructions are available in this thread.
**WARNING** It is critically important that you verify that the RUU ("OS") install was successful. I would run a factory reset from the stock recovery AFTER installing the RUU to ensure that you do not encounter any boot loops before proceeding as going S-ON with a borked rom makes for a quick brick. Please heed this precaution seriously! VZW TEC "insurance" plan or similar coverage in case of brick highly recommended! **
-The only way to get back to "Locked" is to run Sunshine again and choose the "S-OFF LOCKED" option that is now available, however you cannot run Sunshine without going back S-ON first. Install the latest Sunshine.apk now, your license should be restored automatically.
-Once you are sure your RUU has completed installing and successfully booted all the way up, connect your phone to your PC with USB Debugging Enabled.
-Download Android Debug Bridge and install to an easy to type directory such as 'c:\adb\'.
-Open a new command prompt (run cmd.exe) and navigate to your adb directory, ie: 'cd c:\adb\' .
-Issue the command 'adb devices' to check that your phone is connected properly and detected by adb, you should see a device identifier come after a short delay.
-Now we must go S-ON so that Sunshine can be run again. Issue the command 'adb reboot-bootloader' and manually enter download mode.
-Once the phone has booted into download mode issue into the command 'fastboot devices' to verify that your phone is detected by the fastboot utility.
-To go back to S-ON, issue the command 'fastboot oem writesecureflag 3' (NO TYPOS!!). The prompt should confirm success at which point you can issue 'fastboot reboot'.
**Boot issues?**->If the phone fails to boot, factory reset through stock menus.
Assuming all is up and running, run Sunshine, and select "S-OFF LOCKED' this time around.
-Once that process is done, use the prompt to reboot back into the bootloader and then enter download mode. All that we have to do is S-ON and we are S-ON Locked!
-Issue 'fastboot oem writesecureflag 3' and once successful, reboot with fastboot.
**Boot issues?**->Lastly factory reset again if data partition read issues soft brick the phone again via the stock menus, I do not believe this will be necessary but it is not a big deal if it turns out to be.
Voila~ You are now S-ON Locked and should not have any tamper flags if you ran the RUU immediately prior to the S-ON process!
Please let me know if you have any questions here or via PM and please do not do anything you are not sure of!! You run a substantial chance of bricking by messing up while reverting to stock! There are tons of resources around here to reference too! Hope this helps~
Edit: anti-liability level +5000 lol
Thank you very much. It is my understanding that you don't need Sunshine to relock. To relock, you only need to enter command: fastboot oem lock