I have to send my phone back for a warranty replacement because it won't charge the batteries. Anyways, I'm a bit unclear as to the exact steps required to return my phone to its stock conditions.
I restored my original nandroid backup (with 2.1-update1).
This is what I want to do:
remove root
restore the stock recovery
wipe all data to factory defaults
turn S-OFF back to S-ON
Is this the correct order to do these things? Am I missing anything?
I found how to do #2 at showthread.php?t=756850 and #4 is described on the Unrevoked Forever Wiki.
I do NOT know how to do #1 or #3.
Don't forget to format the internal Phone Storage. You can do that from in Settings.
You need Clockwork to flash S-ON, so do that before restoring stock recovery.
So, if I put back on the stock recovery, will I be unrooted?
Look?
This thread could have been found by searching. The only thing it did not cover is S-ON, which can be found on the unrEVOked forever FAQ
http://forum.xda-developers.com/showthread.php?t=732497
Thanks for your reply. I did multiple searches and have been reading for the last few hours, but obviously didn't find your helpful thread.
Any recommendations on which RUU would be best? Will it also flash my radio back to 1.x?
Thanks!
...
I would take the one right above the HBOOT .79 one ... because that would be the last one with HBOOT .77. I have gotten 3 Incredibles so far (2 warranty replacements for my original) and all 3 came with HBOOT .77.
Please note, that was written long before S-OFF so figure out where in the process S-ON should go.
Thank you very much. I'm downloading the executable now.
Just wanted to make sure that this won't brick the phone since I have a newer radio. Correct?
If I read the Unrevoked Forever instructions properly, I'll need to do the S-ON before running the RUU since the RUU will replace the rooted recovery with the stock recovery. Sound right to you?
Thanks again for your help.
YMMV
While YMMV, running a RUU in the ordinary course should not brick the phone (although pulling out the battery when you lose patience might). It will either run or it wont with your radio. There are other threads to downgrade if you need to.
The double-radio-flash issue was a one time thing when unrEVOked issued a radio ****PATCH**** in their efforts. Applying the Patch to a Patched radio would brick. That has nothing to flashing two radios, although it certainly morphed into that in the hearts and minds of the flasher community.
I think I have figured this .77 .79 HBOOT thang out.
if you had .77 then got the latest 2.1 update OTA you kept .77,
BUT the latest 2.1 RUU changes the HBOOT to .79, so if you got it OTA hboot stayed, if you did RUU you have .79
I think.
Related
Hi guys,
I've been reading through the forums over the past two days but I have to admit it's hard to find what I am looking for now that the G2 forum and the DZ forum are merged, and the search isn't getting me anywhere for this one.
I have Bell Canada Desire Z permarooted and S-OFF'd, with CWMod. I did this before the newer gfree method and from what I can gather this can lead me to some kind of endless loop if I try to flash back to the a Bell RUU or other RUUs for that matter. It also worries me that I can't try new radios, etc.
I am getting very poor battery life compared to others so I want to have my phone replaced. I have an extended warranty from FutureShop so I probably don't even need to reset the phone to stock again (they swap on the spot) but I would like to anyway. It will also allow me to test the battery again with the stock ROM.
So, how do I go about flashing back to the Bell ROM and turning S-ON, and unrooting? Keeping in mind that I used the pre-gfree method. I believe it was Visionary R12 and gtab's guide.
Also as the title implies, I was wondering if it's possible to use the new (better) S-OFF even if I am already S-OFF'd the old way?
Any help is appreciated!
You can use gfree and achieve "real" S-OFF without having to unroot.
Just run it. Worst that'll happen is it fails if you happen to be on a kernel it doesn't like. If this happens, no harm is done, just a reboot.
Just run gfree from where you are, as the previous poster said.
That will put you in a much safer position, where you can get stuck in that boot loop that you can if you've only got the eng hboot.
Then you can flash whichever ROM you want. Then you can undo gfree if you want via its new options (see the Wiki).
Regarding your point about the merger, IMHO this issue isn't anything to do with the DZ specifically, and lots of users are posting about similar stuff with their G2s. It's all the same
Thanks guys,
I've done gfree (which is MUCH easier than the thread and wiki make it look - they need to simplify the text, it's overwhelming to look at given how simple the procedure is) and flashed the Bell RUU.
Now I am just about to root, and use gfree to undo the S-OFF I guess?
Will let you know how that turns out. Thanks again!
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Ganii said:
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Click to expand...
Click to collapse
I'd keep that backup file as it is a dump of your original partition 7 before gfree mods it. You can dd i back and put everything back to how it was, if you ever need to. Do you need to keep it on the phone? No.. store it somewhere on your PC.
With the old "fake" S-OFF you would get stuck if you flashed a stock rom because it would overwrite the engineering HBOOT which was the only thing making your phone think it had S-OFF. With gfree method, you have real S-OFF, so this should be fine.
See http://forum.xda-developers.com/showthread.php?t=838484 for details.
tl;dr You should be fine.
Hm,little bit confused!
The backup I need to get original original partition 7
but not to get S-On.
To get S-On I can use the new gfree method,it`s now
possible with this!
I did the old UBERROOT method with real S-Off!
P.S.I read here about this:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Not 100% sure I understand the question...but:
You don't need that backup file. If you delete it nothing bad will happen. Paranoid people (like me) would copy it to a safe place, but there's no real need.
You can flash whatever roms you like, including stock ones, as long as you have real, radio (gfree) S-OFF.
Hi guys, thanks for the help! I got it all settled, it was easy.
As I mentioned above, I used gfree to do a true S-OFF, which was easy.
Then I ran Bell's RUU and it worked without any issues. I assume the RUU install also flashes the HTC recovery back to the phone, I didn't check but it must..
A little summary for anyone who needs help in the future..
If you rooted/S-OFF'd using a method older than the current rage/gfree method (the one in the wiki) then you need to redo the S-OFF using gfree.
Steps:
Use gfree -f to S-OFF again
Run the stock RUU file on your pc (you need HTC sync installed for this)
Temproot (first part of the wiki guide) the stock ROM
Use gfree -s on to S-ON your phone
Reboot, and everything should appear like stock (aside from still being sim-unlocked).
Were u sucessful in returning your phone to htc after u did the above?
I didn't have to return it to htc, just to future shop, and it was fine.
Sent from my GT-I9000 using XDA App
I am new to the Android development scene (appro 6 months now) and when I first rooted, I neglected to backup my stock ROM. I'm much more comfortable now, but am still confused about a few things. I'd like to have a stock image to rely on if something goes wrong or I need to call for service. Should I unroot and use a RUU or an odex ROM? Do I really even need to unroot? Is it necessary to update my HBOOT image as well? I know this is a lot of questions, but I remember from my days of DSS testing that I wish I had a backup of my original CAM! Is it too late?
I was a little nervous to use the 'unrevoked-forever-s-on'. I can't re-root?
I don't recall which method I used to root. I think toasted. Does it matter?
Currently I have multiple ROMS. Primarily I use Cyanogen, Warm2.2, or Ava. I have 0.76 hboot, and ROM manager premium... I use whichever recovery is necessary.
Suggestions?
Also, how can I be sure which RUU or ROM to use as stock. I am worried that there were updates that blocked rooting with some methods. How do I know which RUU will be the best bet? I remember having to wait for updates to come down from the satellite stream. Does it matter if I use an older RUU then wait for updates, or just use a recent stock posting?
If you need to take your evo in for servicing, its recommended to unroot, for a few reasons. Also, if you unroot, you'd need to run an ruu appropriate to your hboot version. That will send you back to completely stock, so no need to flash a stock rom after that, then you can simply run an OTA update, then take it in.
And yes, if you run an old/incorrect ruu, you'll just get errors.
Thanks! and I clicked thanks too
my hboot is 0.76. what RUU is compatible with that? (I've checked the ROM sticky and there is none) should i just pick most recent RUU and flash the corresponding hboot, then flash that RUU? When I looked at the most recent RUU posting, it says DO NOT FLASH! YOU WILL LOSE ROOT! Do they mean permanently?
I gotta run! I got kids! Thanks again... be back tonight!
lil_bono said:
Thanks! and I clicked thanks too
my hboot is 0.76. what RUU is compatible with that? (I've checked the ROM sticky and there is none) should i just pick most recent RUU and flash the corresponding hboot, then flash that RUU? When I looked at the most recent RUU posting, it says DO NOT FLASH! YOU WILL LOSE ROOT! Do they mean permanently?
I gotta run! I got kids! Thanks again... be back tonight!
Click to expand...
Click to collapse
You lose root, it returns you back to stock, but you can re-root as well.
Thanks. I guess I am over-thinking this...
So I cracked my screen Monday at work but I'm Not to worried about it .I'm going to take it to a service center and shell out the 35 to have the screen replaced. But Here's the thing. I'm having problems unrooting this damn thing. I have All HTC Sync drivers, all ADB Drivers I have tested moving files to and from sd and sys mem via adb. I have the last two Current RUU's and PC36IMG files stock 2.2 no root, no nothing, just as sprint would like us to have it. I have runned unrevoked forever and have run the S-on Tool before flashing but I always keep getting Bootloader Main Version is older and it fails. I can flash any and all roms but I just can't seem to unroot this damn thing. I have tested the new Radio's and the Rooted 2.3.3 release for our phone. Wasn't much to write home about. I flash S-off and I can Flash anything but once i flash S-on I cant get the ruu's or the pc36img to work.. Always with this Main Version is older. Myabe I have to use a certian combo of radio's or something I'm still running the Gingerbread radios.
Little about my phone
Hardware:0004
Baseband: 2.15.00.11.19
Android:3.70.651.1
PRI: 2.15_003
PRL60679
Hboot. 2.10.0001(S-OFF as of right now)
If someone could please PM me of what I may be missing. Thanks everyone Untill then I will continue searching and reading.
1. http://unrevoked.com/rootwiki/doku.php/public/forever ; Scroll down to the FAQs, then download the unrevoked s-on zip. This places the security back on your phone, because rooting makes it s-off, and if s-on, quickest way to tell your phone was rooted.
2. Flash that file from recovery, then boot back into the bootloader [vol+down while turning phone on] and verify until its s-on.
3. http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip ; rename that file to PC36IMG, place on the root of your sdcard [not in a folder] then flash it in the bootloader. When the scan that normally does nothing, it'll detect that file. Apply the update then reboot. That's a stock 3.70 firmware file, it'll take you back to stock, unrooted, s-on.
You shouldn't get the 'main version is older' message, it meant you were using the wrong ruu.
Like mentioned above, you are simply trying to flash a rom that is older than your current HBoot requires basically. PC36IMG for Stock HBOOT 2.10.0001 EVO
Best of luck!
This will set everything back to the way it was before you did anything to the phone. However unlikely, be sure to remove any further traces of your "root" by deleting stuff like Titanium backup, clockwork mod .. and any other Apps that required root to use (like wireless tether)
Thats where backups come in handy, because you can backup your current EVERYTHING (Rom with Clockwork - Apps with Titanium), transfer the folders to your PC, and when you get your phone back.. drag and drop, re-root and recover and you are back to the way you like it.. like nothing changed.
This was probably asked before but I couldn't find anything on my searches...
I need to return my phone since I got a refurb'd but I'm having issues turning it back to S-ON... has anyone returned their phone with S-OFF? Did they attempt to charge your account or something to that effect? I can definitely do the RUU and return it to stock unrooted but the bootloader shows S-OFF as well as the 6.17 Hboot instead of S-ON and 2.16 Hboot...
TIA!
gqukyo said:
This was probably asked before but I couldn't find anything on my searches...
I need to return my phone since I got a refurb'd but I'm having issues turning it back to S-ON... has anyone returned their phone with S-OFF? Did they attempt to charge your account or something to that effect? I can definitely do the RUU and return it to stock unrooted but the bootloader shows S-OFF as well as the 6.17 Hboot instead of S-ON and 2.16 Hboot...
TIA!
Click to expand...
Click to collapse
Well they can't really do anything about us rooting phones since the supreme court says we can do whatever the hell we want to devices we paid for, thanks to the Apple lawsuit. However rooting voids your warranty so I suppose the question is why are you returning. If you are returning it because it's in some way physically defective, you *might* be ok. But if it has malfunctioned, it could bite you in the ass. More information would be helpful.
You should also realize that Sprint has been very inconsistent on this issue. There are those who have had warranty work/returns done and had no issues with it having S-Off and even custom roms still installed. Then there are those who have gotten caught. It should also be pointed out that this is in your contract, so please don't be one of those guys that get denied then RAGE about it on these forums. When you rooted, you clicked a box that said "Your warranty is now void" or at least read that somewhere I am certain! Anyway more info pls, or try it anyway and good luck! Worst thing they will do is give you the phone back and void your warranty totally. You could always toss it in the sink for a few hours then file insurance claim on it.
gqukyo said:
This was probably asked before but I couldn't find anything on my searches...
I need to return my phone since I got a refurb'd but I'm having issues turning it back to S-ON... has anyone returned their phone with S-OFF? Did they attempt to charge your account or something to that effect? I can definitely do the RUU and return it to stock unrooted but the bootloader shows S-OFF as well as the 6.17 Hboot instead of S-ON and 2.16 Hboot...
TIA!
Click to expand...
Click to collapse
I tried returning my Evo with S-Off, and the person who was looking at it recognized it in the bootloader. He said "I personally used Revolutionary too. Sadly, we can't return this."
I was able to find a solution, however. Download the zip file attached to this forum post, rename it to PC36IMG.zip, and place on the root of your SD card. Boot into your bootloader. You will be prompted to update. Choose yes. It should flash quick. When it asks you to reboot, choose yes and reboot back into the bootloader. It should show S-ON with 6.17 HBOOT. From there flash your RUU and you should be back to 2.16 HBOOT with S-ON!
I got a refurb a couple months ago and it arrived S-OFF, so I dunno
Thank you all for your responses. I did try to run the RUU and Captain Throwback's S-ON zip but no luck, I'll probably just unroot and RUU it back to the newest firmware and just return it like that. Since borrowedchief said he received his with S-OFF, its probably a hit or miss as most other things at Sprint...
I just sent my old phone back with S-OFF. My issue though was power cycling. Sprint even credited me the $100 premium for my insurance because they failed to replace my phone before it had water damage. I took the phone in multiple times with no luck. Finally the Tech told me I had good news and bad news. Good news, you are getting a new phone. Bad news you have to pay $100 because you have water damage. The first Rep I talked to said we should have replaced the phone the first time. Credited me the money once they received my old phone.
I just returned my phone a few days ago with the s-off but i did have the original rom on the phone. They didnt say anything to me and when i received the new phone, the s was also off.......
Obviously the official rule is that they dont take them back S-off... Some people get lucky and either get a lazy rep or a rep that wants to be nice... It's a gamble
richp1970 said:
I just returned my phone a few days ago with the s-off but i did have the original rom on the phone. They didnt say anything to me and when i received the new phone, the s was also off.......
Click to expand...
Click to collapse
I returned mine too but the terms state that they have up to 2 billing cycles to charge us for any damages or whatnot... guess we'll see...
Their policies at sprint are now that they service rooted phones meaning with S-off they just RUU back up to the latest and it usually reflashes over ENG hboot and other things meaning that it's just gonna be s-on when you get it.
I rooted my phone and is s-off too and cant get it back to s-on
gqukyo said:
This was probably asked before but I couldn't find anything on my searches...
I need to return my phone since I got a refurb'd but I'm having issues turning it back to S-ON... has anyone returned their phone with S-OFF? Did they attempt to charge your account or something to that effect? I can definitely do the RUU and return it to stock unrooted but the bootloader shows S-OFF as well as the 6.17 Hboot instead of S-ON and 2.16 Hboot...
TIA!
Click to expand...
Click to collapse
Originally Posted by Captain_Throwback
Here I will post my 2.16 hex-edited HBOOT to appear as 6.17. I'm not really a good person to put together a guide, but I can give you this file, which should at least help.
I TAKE NO RESPONSIBILITY IF YOU (SOMEHOW) BRICK YOUR DEVICE. FOLLOW THESE INSTRUCTIONS AT YOUR OWN RISK!!!
Also note that I have 0003 hardware, so there are no guarantees that this will work for you! That being out of the way, let me continue . . .
I used AndroidFlasher to flash this HBoot, as it was extremely easy (just renamed to HBOOT.img). Flashing through Fastboot (directly on the device) might also work, I guess, if you rename the file to PC36IMG, but I didn't try it that way.
I was able to do this successfully on Windows XP 32-bit (I always have issues getting anything to work on my Windows 7 machine), so I'm not sure how (or if) it'll work on Vista or 7 (or on 64-bit versions).
Note that if you're doing this with your device connected to your computer, USB Debugging MUST BE TURNED ON!!
If you want to return to stock, I first recommend flashing a stock ROM. I recommend the most recent Gingerbread update, which can be found in this post (RUU can be found here).
After successfully un-rooting your device by flashing the unrooted ROM from above, now we must re-lock NAND (set S-ON). Basically, you just flash the hboot.img from the attached zip file, and it will set your device HBOOT version to 6.17, and re-lock your NAND (S-ON). Then, you can re-flash the ROM from the above step, and it *should* overwrite the hex-edited HBOOT with the "official" version, and restore your device to stock.
Again, this worked for me, but if it doesn't work for you, don't go blaming me, and calling my method a sham.
Thanks to {ParanoiA} for posting the link to the thread where the hex-editing was mentioned, and thanks to thefredelement (from that thread) for posting a working method!
Maybe someone else can test my method and confirm it works for them & others, and then put a real guide together, for everyone else (like me) that needs to return their device for service after rooting with Revolutionary.
Thanks man! I rooted gingerbread 2.3.3 with revolutionary and try to unroot with unrevoked foreverson.zip but no luck because I didn't use there method to root. Hours and hours of research came accross your thread and all I can say thank you.
*****Very important to complete last step because if you don't you will have S-on but your HBOOT will be 6.1... For my last step I didn't flash using HBOOT I just downloaded RUU most current file because my phone came with 4.24.651.1 I just ran RUU booted back to white screen and HBOOT now shows HBOOT 2.1
Here you should use this method. It was origanally posted by captainthrowback and thanks to him now im back to s-on I was rooted and went back to stock but had s-off and I used this method to go back to s-on and it worked. My evo is on hardware v0004 and it worked fine too. Hope this method works for you to. Good Luck. Have any other questions just ask
So the usb port on my EVO is messed up. Sometimes I have to wiggle it around in order for it to charge and if I move the usb cable it disconnects. This also makes it a hassle to transfer files between my phone and PC. I want to bring in my phone to repair, so I have to unroot it. I just want to make sure I go about this correctly. I want to unroot it and have it still be rootable again. I don't know what information you guys need, I'll give you as much as I can.
Hardware 0003
I rooted it with unrEVOked 3 and I didn't have to use the unrEVOked forever s-off patch, the unrEVOked 3 did that. I rooted it stock (did not update ever). I'm currently running a 2.3.5 rom with HTC Sense 3.5.
Would flashing Forever S-ON and then a PC36IMG through hboot be all I would need to do? Would the phone be rootable again after they repair it?
Yes, put a pc36img of a stock rom on the root of the card, then reboot and run s-on tool. Or run s-on tool and then run a stock ruu.
My radios or anything like that don't matter?
Also can I have a link to a stock PC36IMG? I have one but I don't know if it's 2.2 or 2.3.
Edit: Nvm it's froyo! I will unroot and update you on my progress.
When I attempted to flash S-ON, I got an error:
Unsupported radio version.
I booted into HBOOT, my radio is currently 2.15.00.05.02
How do I downgrade (or upgrade, whatever I need to do) my radio?
vulf search for calkulkin's thread about radios. The thread has every radio starting from the beginning to the newest radio. Take an older one and flash it in recovery. You should be good to go.
Sent from my PC36100 using Tapatalk