Hey guys, I'd like to know how to uninstall clockwork recovery from my T-Mobile G2 in case I need to bring my phone in for repair.
I know this is an FAQ, but the method to do it with each phone seem to vary slightly.
My T-Mobile G2 has the following:
Persoshoot's OC kernel
Stock post-OTA ROM with permroot
S-OFF
Latest Clockwork Recovery
What would be the easiest and most straightforward way to restore clockwork recovery back to stock (without nuking everything else in the process)? I see threads saying to run flash_image and flashing the OTA_bootv2 Recovery, but IIRC that program isn't installed on the stock ROM by default.
Your help would be greatly appreciated!
If you used gfree to permroot and get radio s-off, you can just flash the pc10img.zip and it will take you back to stock completely: recovery, hboot, s-on, kernel, rom, etc.
If you did permroot by way of one of the old methods (visionary, rage, etc) you can still flash over the pc10img.zip, after some modifications. Refer to this thread on how exactly to do this: http://forum.xda-developers.com/showthread.php?t=831398
If you have to do the latter, make sure you follow the instructions to the T so as to not end up with a paperweight.
If you have the eng hboot and you have adb setup on your PC, then you can use fastboot to flash the stock recovery image (which you can extract from the stock PC10IMG.zip.
Sent from my HTC Desire Z
It never hurts to erase the recovery before you flash a new one... rather than flashing a new one in over top of the old one. Sometimes stuff breaks and thats one reason why.
tazz9690 said:
If you used gfree to permroot and get radio s-off, you can just flash the pc10img.zip and it will take you back to stock completely: recovery, hboot, s-on, kernel, rom, etc.
If you did permroot by way of one of the old methods (visionary, rage, etc) you can still flash over the pc10img.zip, after some modifications. Refer to this thread on how exactly to do this: http://forum.xda-developers.com/showthread.php?t=831398
If you have to do the latter, make sure you follow the instructions to the T so as to not end up with a paperweight.
Click to expand...
Click to collapse
To get permroot, I initially used an old method, but then unrooted. The unroot method I used is actually what's shown in the post you linked to. After unrooting, I did permrooted the "clean" way (the one that's documented on the wiki) using rage to get temproot, then using gfree to do the rest.
Because I used gfree to permroot, I can simply flash pc10img.zip without any problems right? Without needing to hex-edit the misc.img version number to the previous version number? Can I simply rename it update.zip and the HBOOT bootloader will pick it up, or will I have to flash it from within Clockwork Recovery? Why is it safe to flash pci10img.zip if you used the gfree method?
I didn't install the engineering hboot since the instructions said I didn't really need it unless I was a developer.
Keirnoth said:
Because I used gfree to permroot, I can simply flash pc10img.zip without any problems right? Without needing to hex-edit the misc.img version number to the previous version number? Can I simply rename it update.zip and the HBOOT bootloader will pick it up, or will I have to flash it from within Clockwork Recovery? Why is it safe to flash pci10img.zip if you used the gfree method?
Click to expand...
Click to collapse
Yes, that's right, except it shouldn't be called "update.zip", you want to call it "PC10IMG.zip" and place it on the root (top) folder of your SD card, then go into hboot where it should find it and ask if you want to flash it (give it a few seconds to open the file and check it first).
It is safe if you have full radio S-OFF via gfree, because that bypasses a lot of these checks, e.g. the "version is older" check, and also because when it flashes the stock hboot you will still have S-OFF.
It seems as though the OP has had his question answered but I'm also wondering the same question. I have gotten full root by the rage method. What do I do in my situation to get back to stock recovery while maintaining s-off and root. I actually just want to calibrate my battery and go back to clockwork
Lithium Ion batteries cannot be calibrated. There is no need. They dont have a memory like older battery types did, for example, nickel cadiums.
If at all possible, all you would be doing is retraining your phone with that process, not the battery. It is bad for li-ion batteries to be ran completely empty and it is not recommended if you care about the longevity of the battery.
Sent from my HTC Vision using XDA App
Thanks for your reply. I was told by someone that flashing your phone while it is plugged in kinda throws the battery off. I have noticed extremely short battery life after making this mistake so I thought it was needed. Would you still recommend doing it train the phone itself tho? I mean, my battery life is ridiculously short. Like six hours and my battery always depletes while I'm asleep.
Sent from sweet G2
Related
Ok mods, I know this normally isn't the place, but I think this is very important as I'm seeing more and more semi bricks, some of which are not recoverable without HTC signing keys!
So I ask you mods, please don't lock this, if anything it really needs to be a sticky!
That being said, if you are s-off, do NOT flash the signed offical PC10IMG.zip. if you don't have the correct rom on there when you do, as per the unroot thread you will get stuck.
Let me give u an example of what I've been seeing and why its happening so everyone understands. Example: you perm root/s-off your phone. You decide to do some rom playing. You end up boot looping and can't fully boot into android. So u say hey, ill reload pc10 and start over, WRONG.
What happens is s-off does no checks, sigs, version number etc. So when you load it up it starts to flash. Hboot(s-on) is first, then recovery, then radio. Thing is it has to reboot to do radio, so it reboots, at this point your s-on so it does a version check. "Main is older" then it quits before ever touching the system.img or boot.img. at this point you are locked. You have s-on, stock recovery, and can't boot android. Long story short, your screwed.
Now depending on the rom/kernel u had/have installed you may have adb access. At this point you have a small chance of recovering, which is better then some. I just spent the last 5 hours working with someone on a fix and think we got it, but the bat has died and will have to pick back up tomo. If this works or not, I also have one more idea we can try. I will update OP with any fixes we find.
*If your system was bootable when you started this, it may still boot. but you will be s-on, stock recovery, and still on whatever rom you were running. at this point you will have to hex edit to downgrade, or wpthis.ko if there is one for your kernel to get back to s-off.
*ive seen some people saying. i did it, it worked for me, but don't add any supporting info. this is bad for people new to android cause it makes them feel they will be ok. the only way this can work is if you have a version installed as old or older then the official img, or if you take hboot out of the update which then makes it no longer the official update. but my question is why are you flashing this? if you want to fully unroot, then follow the unroot guide. if you just want to go back to stock w/root, grab one of the stock w/root roms.
Long story short, do your rom flashing from recovery. Stay out of hboot unless you are following proven instructions to a T, or being walked though be a "pro". I hope this helps save some people!
* if you just read all this going DAMN, i already did that, then go here:
http://forum.xda-developers.com/showthread.php?t=842495
Sticky this. In big bolt capital letters. I've seen this happen once already, and just saved another phone from this headache.
More people need to know about the DON'T-FLASH-PC10IMG.ZIP
dyndragon said:
Sticky this. In big bolt capital letters. I've seen this happen once already, and just saved another phone from this headache.
More people need to know about the DON'T-FLASH-PC10IMG.ZIP
Click to expand...
Click to collapse
When u say u saved a phone. Do u mean u stopped someone before they did it, or you mean u have a working fix. Pls post fix if u have one. I will post mine as soon as I confirm it.
Btw- I have seen 5 happen in the last 3 days. As I haven't gave up on any yet, some are worse off then others and only 2 have a possible fix in the am, well a fix I know of.
After I permarooted, I decide to flash a Z ROM. I did, and I didn't care for Sense, so I flashed PC10 and didn't have any issues. Mind you, I didn't flash the OTA at that point either. Phone booted up without an issue, I got the OTA almost immediately, and I permarooted again.
Basically, if you applied the OTA, don't flash PC10 to get stock again.
So does that mean the instructions for how to Un-Root are no good?
KronicAnarchy said:
So does that mean the instructions for how to Un-Root are no good?
Click to expand...
Click to collapse
I unrooted my phone, no problems.
No the instructions to unroot are correct because at the beginning you flash an alternate misc.img to change the main version number. I got stuck the other day because my phone wouldnt boot and i couldn't flash the ota because i had removed google goggles and some other system apps so i tried to downgrade using PC10IMG.zip and it cancelled during installation just as stated in the op and i was somehow able to flash the misc.img through fastboot and reflash with PC10IMG.zip
sethrd said:
After I permarooted, I decide to flash a Z ROM. I did, and I didn't care for Sense, so I flashed PC10 and didn't have any issues. Mind you, I didn't flash the OTA at that point either. Phone booted up without an issue, I got the OTA almost immediately, and I permarooted again.
Basically, if you applied the OTA, don't flash PC10 to get stock again.
Click to expand...
Click to collapse
If you did not flash the stock rom before you flashed the pc10, you got lucky. When it reboots half way though, it does a version check, and the rom version you happened to be running must have been an older base. If your phone is bootable and you flash the pc10 OUT OF ORDER it will lock you down that way, ie locked on sense. If anyone wants to go back to stock, just flash one of the stock w/root roms in recovery or via rom manager... trust me on this, there are more people screwing up there phone because of this then anything, just not posting about it. I've been up all hours of the night, helping differnt people the last few days.
KronicAnarchy said:
So does that mean the instructions for how to Un-Root are no good?
Click to expand...
Click to collapse
No the unroot guide is ok. If you notice, the first thing it has you flash is the stock w/root rom. Like I said if you follow proven instructions to a T, you will be ok. That is if you want to go back to non-root only though. If you just want stock with root, flash a stock with root rom via RECOVERY or ROM MANAGER.
Im not to sure how it all works and i just got up a little bit ago .
but since s-off doesnt check the sign couldnt we unpack and repack pc10img with the hboot with s-off?
fastludeh22 said:
Like I said if you follow proven instructions to a T, you will be ok.
Click to expand...
Click to collapse
Well he's edited his post now, and people have followed his instuctions and bricked their phones.
So just to confirm before I brick mine: The instructions in their current form will not brick my phone, right?
I had s-off when running baconbits. I tried to revert back to stock but couldn't. I then flashed pauls prerooted phone rom and tried to install the stock rom back onto the phone. I seems to have removed the s-off and now displays s-on. I am permanently rooted, but fastboot still shows s-on. Was this caused because I tried to flash the pc10img.zip? Now how do i revert back to stock? I don't have a nandroid backup for the stock rom, just paul's which after a recovery still displays s-on. It doesn't loop, I just can't install anything else on there.
I flashed pc10 and it turned S-ON. But when I booted it up I still had root acess, so it was like a temp root but where I could not write to the system. I took the ko file from the perm root and hex edited it to match the kernal on my phone.. boom rooted again and I was able to flash recovery and do a nand restore
I tested it out again by hbooting pc10.. and I was able to obtain s-off by changing the kernal number in the ko file
Sent from my T-Mobile G2 using XDA App
So let me get this straight, in order to flash pc10 safely we MUST have an existing PreRooted STOCK ROM?
No all you have to do is run hexeditor to change build number then you can flash pc10img
Sent from my T-Mobile G2 using Tapatalk
marc91988 said:
No all you have to do is run hexeditor to change build number then you can flash pc10img
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
Exactly. If you actually follow the directions in the thread you will be fine. I've done it more than a few times and have not had any problems yet.
I have also updated the instruction on the unroot guide aswell.
I was running the original Sense rom that was loaded via hboot which kept me at s-off. I was able to revert back to stock using the PC10 zip from here http://forum.xda-developers.com/showthread.php?t=831398 At the time I had no clockwork recovery. Was what I unsafe?
Thanks for the piece of mind. I don't want to unroot just yet, I'm running pretty much the stock rom w/ ota and bacon bits anyway, so........ Still it's nice to know that I can get back to stock should I NEED to.
Okay so I did this and I didn't brick my phone...and still have root/s-off
Did an ota update, after I found out there was perm root I perm root g2 s-off, then I went and downloaded clockwork/rom manager
Created a backup of the current g2, and did a wipe
Then hboot to sense ui (still have root). I went into clockwork create another backup. Played around with desire z rom.
After I decided to go back to stock 2.2 performed a restore with clockwork and now I am back to my original g2 stock.
So am I missing something here?
fryrice8850 said:
Okay so I did this and I didn't brick my phone...and still have root/s-off
Did an ota update, after I found out there was perm root I perm root g2 s-off, then I went and downloaded clockwork/rom manager
Created a backup of the current g2, and did a wipe
Then hboot to sense ui (still have root). I went into clockwork create another backup. Played around with desire z rom.
After I decided to go back to stock 2.2 performed a restore with clockwork and now I am back to my original g2 stock.
So am I missing something here?
Click to expand...
Click to collapse
These people didnt nand back before messing around with stuff
Sent from my T-Mobile G2 using XDA App
Hey I need some help. I have been trying to reformat my phone with the original stock ROM but I cannot get the RUU to work. Every time that I try to use the RUU executable file to reinstall the original ROM it can't detect my phone. I really need help with this my phone is incapacitated right now. If someone could help me find a rom that I could use here that would be fantastic. Thanks
what happened that your phone is not working? are you rooted, s-off? what rom where u on b4?
Sent from my ADR6300 using XDA App
It is S-Off and I am not sure if it is still rooted. I have been switching back and forth from the cyanogen mod and the stock rom, and I tried doing a system restore on the stock rom and it didn't really change anything but I don't think it can do root things anymore. It has been asking me to do a system update but every time I try to install it it fails.
SerenadeX said:
It is S-Off and I am not sure if it is still rooted. I have been switching back and forth from the cyanogen mod and the stock rom, and I tried doing a system restore on the stock rom and it didn't really change anything but I don't think it can do root things anymore. It has been asking me to do a system update but every time I try to install it it fails.
Click to expand...
Click to collapse
Your failed update is probably due to your still having a modified recovery.
Something that could work for you:
>run the .exe for the RUU, then minimize it.
>start/run/type "%temp%" in the dialog box.
>search the output for rom.zip
>move the rom.zip to your sdcard and run it from hboot.
this should go through the rom installation and restore your rom. it's worked a couple times for me when I messed up recoveries.
Good luck!
BTW do you have HTC sync installed on your computer? not having that might be missing the driver for your phone.....just a thought
I tried extracting rom.zip out of the temp directory but the file was corrupted. Maybe the RUU doesn't work at all? I don't know. If you can get me a rom.zip that isn't corrupted that would be fantastic. Thanks!
SerenadeX said:
I tried extracting rom.zip out of the temp directory but the file was corrupted. Maybe the RUU doesn't work at all? I don't know. If you can get me a rom.zip that isn't corrupted that would be fantastic. Thanks!
Click to expand...
Click to collapse
Make sure SD card is formatted to fat32. Rename it so it is PB31IMG.zip(If on Windows and have fileextensions turned off rename it PB31IMG. The .zip will already be added.)
Put on root of SD card meaning not in any folders and boot into hboot. The phone will ask you to update, select yes and wait for it to ask you if you want to reboot.
http://dougpiston.com/files/RUU/bui...and-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
Alright Now i have one last question. That worked wonderfully first thanks for the info. Now i need to reverse unrEVOked forever 's radio fix. Right now its S-OFF and I want to restore it to its original state when I bought it. How do I reverse unrEVOked forever?
SerenadeX said:
Alright Now i have one last question. That worked wonderfully first thanks for the info. Now i need to reverse unrEVOked forever 's radio fix. Right now its S-OFF and I want to restore it to its original state when I bought it. How do I reverse unrEVOked forever?
Click to expand...
Click to collapse
Under the FAQ there's a link to the S-ON tool.
http://unrevoked.com/rootwiki/doku.php/public/forever
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.
SerenadeX said:
Alright Now i have one last question. That worked wonderfully first thanks for the info. Now i need to reverse unrEVOked forever 's radio fix. Right now its S-OFF and I want to restore it to its original state when I bought it. How do I reverse unrEVOked forever?
Click to expand...
Click to collapse
To get s-on you need to have CW recovery. Wish you would have mentioned this before. You need to flash clockwork recovery again then apply the s-on. Then re run the previous PB31IMG.
Wow this is so freaking nuts. Ok so I tried running the S-ON .zip file that they provide using CW Recovery. Problem is now unrEVOked forever doesn't support my radio, radio-1.00.00.02.09. I will try to contact them unless you all have another idea. Thanks for your help so far!
If your still s-off you can flash a supported radio through Hboot much like the get back to stock PB31IMG you just ran. But if you ran the one I provided earlier you should be on a .92 hboot and a 2.15.00.07.28 radio, which is supported for s-on.
Here, download one of the ones that S-ON if compatible with and put it on the root of your sd card, and boot into hboot. Be sure its called PB31IMG.zip, or else it won't work.
http://adrynalyne.us/files/di_radios/
A quick guide for flashing radios:
http://forum.xda-developers.com/showthread.php?t=774155
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.
Ok so I tried updating to a radio compatible with the unrEVOked S-ON update. When I try to run the file the recovery screen blacks out and then goes back to the main menu. It doesn't give me any output as to why that happened or if it even did anything.
You should flash RUUs from within HBOOT, not Recovery. An RUU includes everything from radio, to ROM, to recovery.
You can still do this with S-ON, since it is signed.
I'm not on the RUU I know how to install that. I need to use the S-ON .zip file that i got from unrevoked.com
SerenadeX said:
Ok so I tried updating to a radio compatible with the unrEVOked S-ON update. When I try to run the file the recovery screen blacks out and then goes back to the main menu. It doesn't give me any output as to why that happened or if it even did anything.
Click to expand...
Click to collapse
You don't flash radios in recovery you flash radios in HBOOT. Make sure you rename the file to the proper filename then it should automatically detect it and install it.
Again like I said before, if you simply install the RUU from within HBOOT that would revert everything back to stock including the radio. Then you could run S-ON from within the stock recovery. But if you want to do it the other way so that you run the S-ON patch from within ClockWork that's fine too.
Haha well i have not explained things properly so let me explain where I am at right now very clearly.
Right now I have HBOOT updated using an RUU with a radio that unrEVOked forever works with. I have rooted and installed Clockwork Recovery. Now, I go to install the S-ON using Clockwork and then the screen blacks out and it returns to the Clockwork main menu without giving me any output.
Hopefully that clears things up
Ok sorry I thought you had trouble flashing the radio.
Yes I do believe the S-ON patch is installed within recovery, I just did it a few days ago and it worked fine. I was using the 7.28 radio. I believe I just did a normal .zip install in clockwork.
This sounds stupid, but make sure you're not pushing the power button. In ClockWork you have to push the optical pad to make selections, it's unlike HBOOT. I can't think of anything else.
ok so i got a g2, i permarooted thanks to rage/gfree now i have to send it in, i flashed back to stock rom, tried following http://forum.xda-developers.com/showthread.php?t=835971 to the letter, fastboot runs teh pc10img.zip with no complaints, i even installed the ota afterwards, but yet im still s-off and when i try to boot to recovery it gives me a phone and red triangle...
ive asked in the irc, granted this prolly isnt the best time of the day. im in no hurry as my new phone wont be here for a few days but still would rather have it done as quickly as possible.
TL: DR was on sense with s-off, need to be as factory as possible for returning to tmobile.com for keyboard issues
You're still S-OFF because that guide is an old one, and is based on the old S-OFF method of applying an engineering hboot We really need an updated guide to reflect gfree. I'm not sure that the editing of the misc partition is required now we're using gfree.
There's soon going to be an updated version of gfree to return you to S-ON. But basically you need to restore the radio configuration partition on your phone, which has been edited by gfree. gfree saves the original version of this on your SD card when you run it. See post #209 at http://forum.xda-developers.com/showthread.php?t=855764
I don't know why your stock recovery hasn't restored though, you might have to try flashing that manually on its own ?
Stock recovery you just need to press vol+ and power. Sounds like it flased fine.
Sent from my HTC Vision using XDA App
shabbypenguin said:
when i try to boot to recovery it gives me a phone and red triangle...
Click to expand...
Click to collapse
I believe that is correctly back to stock then. The stock recovery will give you that screen, then you hit Vol + and Power to continue on to the stock recovery screen.
Clockwork Recovery got rid of that nonsense, but it looks like you got everything but the mmcblk07 partition back to stock. Use the backup created by gfree. It puts it on your sdcard, IIRC.
I've been having some issues with my screen recently, probably due to a cable being loose or something like that so I want to send my phone back to be repaired. I have S-OFF and am running CM6.1.1. I have a nandroid backup for the original stock rom, but this is obviously rooted. So have to i get to back to S-On with the original stock room un-rooted so my warranty isn't technically void??
edit: Its a EU desire z,
Restore the backup of the stock ROM that you have.
If you have S-OFF via gfree then you need to un-do that via "gfree -s on".
If you have the eng hboot then you need to dd back the stock hboot (get it out of a PC10IMG.zip file.
Finally you can remove root. Removing the Superuser app will almost certainly be enough, no-one is going to notice anything more.
I flashed a hboot to get s-off, how exactly do i dd back to stock hboot? Do i extract the file from the PC10IMG zip?
jakbjak said:
I flashed a hboot to get s-off, how exactly do i dd back to stock hboot? Do i extract the file from the PC10IMG zip?
Click to expand...
Click to collapse
Yes, extract the stock hboot from the correct PC10IMG.zip file, then you can dd it to your hboot partition just like you originally did with the eng boot.
Or if you just flash a complete stock ROM over the top (the same version as your backup, once the backup has been restored), it will install the stock hboot anyway.
ok still, just to be certain (last thing i want is to brick my phone!!) restore rooted stock rom from the nandroid backup, then get a copy of the original rom i have a flash it? and do i flash it through cwm or the other menu?
jakbjak said:
ok still, just to be certain (last thing i want is to brick my phone!!) restore rooted stock rom from the nandroid backup, then get a copy of the original rom i have a flash it? and do i flash it through cwm or the other menu?
Click to expand...
Click to collapse
If that stock ROM is the same version as your rooted backup that you restored, then yes, that should be fine because the stock ROM will include the stock hboot, to put you back to S-ON via hboot.
If however the stock ROM is an earlier version than your backup, you will have to go through an additional downgrading procedure to safely be able to flash an earlier ROM (or you could end up bricked).
No, you don't flash it via Clockwork. You put the ROM image (not RUU) onto the root folder of your SD card, called "PC10IMG.zip", then boot into hboot (with the phone powered off, hold Volume Down and then press Power until it switches on) and it will open the ROM and ask if you want to flash it.
Cool, that makes sense. Thanks
is this safe to flash on ANY Desire Z?
RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe
(This RUU is exactly the one used in the 1.72 root procedure to downgrade to 1.34)
Like I plan to just execute it on the computer and let it do its thing.
My baseband version:
12.28b.60.140eU_26.03.02.26_M
My rooting route was exactly as the XDA wiki, but stopped short of flashing ENG HBOOT.
I know I can restore my backup ROM, and s-off using gfree. My problem is with CWM recovery because if the people at the shop try to charge it with the power down, they will know I've rooted before due to the phone booting into recovery.
djfoo000 said:
is this safe to flash on ANY Desire Z?
RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe
Like I plan to just execute it on the computer and let it do its thing.
My baseband version
12.28b.60.140eU_26.03.02.26_M
My rooting route was exactly as the XDA wiki, but stopped short of flashing ENG HBOOT.
I know I can restore my backup ROM, and s-off using gfree. My problem is with CWM recovery because if the people at the shop try to charge it with the power down, they will know I've rooted before due to the phone booting into recovery.
Click to expand...
Click to collapse
I belive this is the RUU for the Europe Vision only, so if your Desire Z is not the Europe Vision I would not run this RUU.
Edit: I found this thread on your RUU, I would check it out first before flashing:
http://forum.xda-developers.com/archive/index.php/t-822908.html
In skimming the thread I see someone flashed this on a Bell Desire Z, but they super-cid with gfree first.
Edit 2:Cant you just find the stock recovery.img and then flash it to your phone using the flash_image method from terminal emulator? Since you dont have fastboot. Then re-run gfree with the -s option to get S-on again.
Heres the link to the Flash_image method:
http://forum.xda-developers.com/showthread.php?t=902493&highlight=flash_image
i was thinking of a pseudo-one click method. hahaha
I've just finished downloading the RUU i mentioned.
How do I go about extracting the recovery.img? I tried extracting with 7zip and it says cannot open file.
djfoo000 said:
i was thinking of a pseudo-one click method. hahaha
I've just finished downloading the RUU i mentioned.
How do I go about extracting the recovery.img? I tried extracting with 7zip and it says cannot open file.
Click to expand...
Click to collapse
Just download it myself, good question, not quite sure myself on an RUU since it wants to exe. , thought it might be a simple a unzipping it but ?
Edit : found this:http://lukasz.szmit.eu/2010/04/extracting-rom-files-from-htc-android.html
there's nothing dangerous about it, right? As in the recovery.img extracted from any RUU is not baseband specific or anything? My radio is stock.
djfoo000 said:
there's nothing dangerous about it, right? As in the recovery.img extracted from any RUU is not baseband specific or anything? My radio is stock.
Click to expand...
Click to collapse
Im not gonna lie, I really dont know if the G2 and the Desire Z recovery.img are the same, I know theres a link to the stock G2 recovery image here:
http://forum.xda-developers.com/showthread.php?t=834545&highlight=unroot
hrmm... Just a thought, is that issue worthy of a thread? That whether stock recoveries of G2 and Desire Z are the same, regardless of location of origin (ie Asian/European etc).
You just need to run the RUU but then not press any buttons on the screen, then find the folder where the RUU has extracted temporary files. There will be a standard location on this that depends on your exact OS. Look for the most newly-created folders at this location, and a couple of levels down from there you will find the extracted files, including rom.zip.
Sent from my HTC Desire Z
The same version of Clockwork recovery is used on the G2 and all Desire Zs. So I would have thought you'd be absolutely fine to flash the stock recovery from that DZ RUU onto your own DZ.
Sent from my HTC Desire Z
I need to unroot my phone so I can get a few things fixed on it. There is a thread out there talking about if you have used unrevoked forever to root your phone. Is there a difference between using "unrevoked3" or "unrevoked forever"? It is two different links on the unrevoked website. Or are they just considering the unrevoked method as one? Any help will be appreciated, thanks!
Just go to unrevoked.com and you'll find what you are looking for. There links and stuff to help you out. If you used this method before when you rooted.
Sent from my PC36100 using XDA Premium App
Download the s-on zip, flash it in recovery to get s-on before running the ruu.
Ok, I understand that now.
Now for the PC36IMG file. A lot of people are saying that they are getting errors when they flash this, but I have not seen anyone post a link that is working. What is the newest file that should be used in place of this?
unrevoked3 contains unrevoked forever. Just unroot like you would with any other way, place an s-on zip and a stock rom pc36img on the root of the sd card. Boot into recovery, flash s-on zip, then flash the pc36img stock rom.
So on this website of ruu's, which one is the right one/best to use?
http://goo-inside.me/supersonic/ruu
If you're just getting it fixed, I'd leave s-off so you can get root access back when you get your phone back.
They should still service your phone as long you have stock software. They may do an OTA, but when you get your phone back just flash a recovery then restore a nandroid backup (make one before you unroot).
Sent from my PC36100 using Tapatalk
I thought you could root again after you unroot (well most of the time). So you're basically saying don't flash the S-On, just flash the PC36IMG. That will set me back to a stock rom with root capabilities?
The only issue i'm having is a charging issue. Not sure if it is the port or the battery. But I know if I can't get it to charge again (and can't get back to stock) I'll be screwed with the warranty.
irl5fan said:
I thought you could root again after you unroot (well most of the time). So you're basically saying don't flash the S-On, just flash the PC36IMG. That will set me back to a stock rom with root capabilities?
The only issue i'm having is a charging issue. Not sure if it is the port or the battery. But I know if I can't get it to charge again (and can't get back to stock) I'll be screwed with the warranty.
Click to expand...
Click to collapse
You won't be able to root again if you have s-on and the Gingerbread update. If you leave s-off then you'll be able to flash a PC36IMG of a recovery and be back in business. Even if you don't update to Gingerbread OTA, the Sprint store probably will.
If it's your charging port then they'll have to replace your phone... in which case you'll most likely get a replacement that can't be rooted. If you do get a replacement with 2.3, still check the bootloader to see if it's s-off. A few people have gotten refurbs that were never put back to s-on.
Just flash the PC36IMG of an RUU - the 3.70 one should be fine. If absolutely necessary, you can charge your battery in an external wall charger. I have multiple batteries and use one to charge my extras. I'm not sure if you can get one in stores, I got mine online.
Edit: leaving s-off and flashing an RUU doesn't mean you'll have root access - ie Superuser, root apps, etc - but you will be able to flash a rooted rom later or restore a nandroid backup of your current rooted setup.
Sent from my PC36100 using Tapatalk