Related
i have an htc evo and i am rooted with simpleroot.i was trying to install cyanogen mod but i keep getting an error when installing.it says something about bootloader.i can install other mods.i tried to unroot and i keep getting error wrong bootloader.i have tried 3 different ruu's and still i get the same problem.i even installed a 2.1 rom and tried to get the update but i get a ! half way thru the download.can someone please help.
Did you follow the unroot guide in dev section?
Sent from my PC36100 using XDA App
yes i have.i tried using the ruu's but i keep getting an error saying wrong bootloader.i dont know what else to do.
If you don't care about losing root, use the 2.2 unofficial RUU file and see if that works.
where do i find that?
i found it but not sure if i wanna lose root.i just wanna be able to flash cyanogen mod.it wont let me but i can flash any other rom..i keep getting an error when flashing rom in recovery.something about bootloader.anybody have any ideas as to why i keep getting that error?
gdiaz76 said:
i found it but not sure if i wanna lose root.i just wanna be able to flash cyanogen mod.it wont let me but i can flash any other rom..i keep getting an error when flashing rom in recovery.something about bootloader.anybody have any ideas as to why i keep getting that error?
Click to expand...
Click to collapse
This is how I was able to unroot:
1. Ran the 1 Click SimpleRoot OTA 1.47.651.1 Edition root program. This downgraded my evo to 1.17.651.1 while still mainting HBOOT .76.2000 (this is very important!)
2. Downloaded one of the RUU files (RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe), connected my evo and launched the update . Ensure you have the latest HTCSync software installed before running the program. I used version 2.0.40
I successfully unrooted my phone, and rooted it back to 1.47.xxx just as an academic exercise.
This should work for you. Also search the forum, there's a ton of info (albeit disorganized) on how to do this.
Useful links:
1 Click SimpleRoot OTA 1.47.651.1 Edition
How To UN ROOT. TUTORIAL. Your Problems are solved!
That's where I run into problems.my hboot is .79.000. I use the ruu and i get errors about wrong bootloader.and simpleroot doesn't work.the step where u type in the website doesn't work.i get a blue Lego block with a question mark.
Which version of SimpleRoot are you using? I used the most recent version of the app (the latest has just 2 buttons NOT 4). Make sure after downloading to use the update option to check for updates. For some strange reason, the Simpleroot app is able to downgrade your HBOOT to .76.2000 (I couldn't achieve that by manually completing steps 1 & 2 of Toastchf method AND running the RUU - it always came up with that error UNTIL I resorted to the SimpleRoot method.) Maybe someone else can chime in. Anyways, give it a try.
This phrase seems to be one of those everyone knows...well except me. What the heck are the EXACT steps to running an RUU?
I am in fastboot with usb showing...then I attempt to double click on the file on my desktop and get an error about it not being a win32 file. Seriously have searched google for hours and the search here is down.
Anyone got the steps to do this?
[A] What exactly is meant by 'run the RUU'?
RUU = Rom Update Utility
http://www.htc.com/uploadedFiles/Common/Software_Download/Detailed_RUU_Instructions_09232009.pdf
Well if this is all you don't know, you are way ahead of me, sheez.
Now root, get nand unlock, install new custom recovery, new PRI, new radio and Burnt 1.2 and you will be good to go, laughing...
An RUU is a Rom Update Utility. It is a program that you run on your desktop that flashes a new ROM image on your phone. So the phrase "run an RUU" literally means to run an RUU. They are version specific. Meaning it is not a program that can flash any ROM for you. There is a different RUU for every OS version.
What file are you clicking on on your desktop that's giving you an error?
[A] What exactly is meant by 'run the RUU'?
I am not quite sure what you are trying to do, but I do have a suggestion. Take a look at regaw_leinad thread on [GUIDE] How to root Android 2.2 on the EVO 4G. He put this out way before unRevoked 3.21. BTW: This was the method I used to root my 2.2 EVO, worked like a charm. Anyway, it's not about the process he used to root an EVO, it's more about all the steps and what does what that you learn going through the process. May help you achieve whatever it is you are trying to do.
Good Luck
the link: http://forum.xda-developers.com/showthread.php?t=765496&page=45
I am already rooted and running a rooted version of 1.47. I have a file called...RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe.
This was in an attempt to try to get a 'more' stock version of 1.47 on my phone so that then I could accept the OTA.
I have all of the sdk loaded and yes I have that fastboot in same folder as the adb...(if that means anything.)
When the first 2.2 rolled out many many people with rooted phones accepted the OTA and lost root. So I know it is possible to load the OTA when you have a rooted phone but for some reason I am getting an error. (In another thread, but it is an apply patch error?)
So again....does running a RUU mean...1)You boot to recovery, 2) You go to fastboot, 3) You plug in USB, 4) After you see Fastboot USB (and phone shows up in device manager) you double click the RUU
Is that the process?
Since I didn't see it mentioned. But when you run the RUU, you lose root. If you want to run a "closer to stock" ROM then download SteelH's ROM, and flash that through Recovery.
No, running a RUU is running a PROGRAM that does the update for you. Run the RUU right now without connecting your phone, it will tell you the steps.
Don't even worry about accepting the OTA. Flash this PC36IMG file and it will bring you completely current.
Hmmm...ok. Metalhead, I'll re-read your post when I get home and probably go in that direction.
Debugguy, that document was pretty good at showing me what I should be seeing, but now I am wondering if the file I got was a windows file or not...because it doesn't do that at all.
Thanks ya'll.
Something that may help, go to the unRevoked web site, some really good "back to stock" info here, may
give you some ideas.
go here: http://www.unrevoked.com/#evo
select (1) unrevoked3, then more
select (2) unrevoked Forever, then more
I have an HTC Incredible that i ran the first unrevoked2 update to get root on my device, then unrevoked3 to get s-off. I then was pushed the 2.2 OTA update, which when done through the phone fail. So, like an idiot of course, I ran the update.zip from clockworkmod and now my device is acting all strange (practically bricked).
After the update, the 'droid' eye loads, then goes to a white HTC page where a small dialogue box goes from 0 to 95% then reboots, repeatedly, until I interrupt this via a battery pull. I then get into my phone, but the camera, sdcard, wifi, etc are not recognized. Eventually I get a force close prompt for 'system' which I can wait or force close, either choice, my device will reboot at max 5 minutes.
I have the following showing at HBOOT
Incredible XC Ship S-ON (i ran the s-on update now)
HBOOT-0.77.0000
...
RADIO-2.15.00.07.28
I'd like to get my phone either running Froyo, or back to the stock ROM, and am in need of help. I've ran several PB31IMG.zip files located through numerous guides and dozens of searches to try and get back to stock, but I either get 'update failed' because of some kind of version check, or the update doesn't work (maybe now because I'm s-on?).
I'm in sad need of help, I found another thread where someone else was in my similar situation on another forum but its old, no one is responding, and the update worked for them and not myself. I'd really appreciate it if someone would walk me through un-screwing my device if possible. Much appreciated.
alright well if i was you i would do this.
turn security back off (s-off)
grab the PB31IMG.zip for 2.2 froyo/ or if you want the ota again grab the 2.1
then it should work fine. but i also see the your hboot is not up to date for froyo so maybe find the PB31IMG.zip for 0.92 hboot. i dont have any idea about where it is located but i have the file for 2.2. but alas, i dont have a place to upload it soo yeeaaah. anyway that is what my first choice would be. choose to follow or not.
p.s. i know i say but alot haha
BTW yes, PB31IMG's wont work because you are s-on. and the ota probably did not work because you had clockworkmod recovery instead of stock recovery. thats all i got for ya. hope my terrible explanations help
Well, this might be more promising.
I did notice that my HBOOT was quite out of date, so amongst all of the files I've downloaded, I'm pretty sure the one that might have done it for me was the RUU update file. I of course re-ran the s-off update from unrevoked-forever, then started hacking away at the RUU update. I downloaded the RUU update from Google, ran it, copied the rom.zip file from the temporary files location, renamed it to PB31IMG.zip, copied it to the root, and then poof, noticed the HBOOT was updated (looks like this could have been the root problem).
Needless to say, i'm back to setting up my device (raw), hope that I can still get to root on my device; but at least I'm back to an operating phone!
OK
Looks like I'm at HBOOT-0.92.0000 with IncredibleC XC ship S-OFF still; RADIO-2.15.00.07.28.
Doesn't look like I have a recovery mode (clockworkmod).
I'm guessing if I'm going to root my device I'll need to re-install clockworkmod? Thanks for any future help.
so you still have the reboot thing, going on
Sent from my ADR6300 using XDA App
tjamscad said:
so you still have the reboot thing, going on
Click to expand...
Click to collapse
No, my device is unbricked (so to speak). Since updating using the full RUU it successfully re-flashed everything. Only problem I have to fix now is rooting my device again.
Well I guess I have my work cut out for me searching how to get my s-off phone rooted again. Anyone got a suggestion?
Sent from my ADR6300 using XDA App
if your phone is s-off then search around for a custom recovery in the pb31img format. flash in bootloader, reboot into recovery and flash the rooted rom of your choice.
So my fix was:
1. Ensure phone is already rooted and S-OFF
2. download RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28.exe
3. Run the RUU file
4. Go to my temporary files location, sort by date, and look for the rom.zip file
5. copy that file off someplace else and rename it PB31IMG.zip, cancel RUU Update program
6. Copy PB31IMG.zip to the root of the SD Card
7. Boot my device holding volume down (HBOOT)
8. Allow the update to proceed (will reboot phone almost immediately to update HBOOT from 0.77 to 0.92)
9. Once update was completed, phone reboots final time after prompt
10. Setup phone again (RUU Update is a clean flash)
Still looking out for better instructions on how to re-root my device other than a manual one, but if I must then I must =) Was hoping that I could use unrevoked3, but the last push didn't work out.
you have to do it manually cause unrevoked doest work on newest ota
I can help you reroot if you need it. Im glad you have everythig else worked out though. Congratulations!
sent from Ioslver
ok well basically load this in bootloader and you are rerooted.
the download link for the file is here:
http://www.mediafire.com/?oj6aqi1ceqpm58g
patalo said:
ok well basically load this in bootloader and you are rerooted.
the download link for the file is here:
http://www.mediafire.com/?oj6aqi1ceqpm58g
Click to expand...
Click to collapse
So that PB31IMG.zip (renamed) will re-install the most recent clockworkmod recovery? I saw some other post which also had a 'payload-update.zip' and a 'su-2.3.2.1-ef-signed.zip' file ... not sure if I'm missing something.
Also, according to their latest release (their = unrevoked), http://unrevoked.com/rootwiki/doku.php/public/unrevoked3 - This supposedly works with all versions of supported phones. Of course, when I go to http://unrevoked.com/rootwiki/doku.php/public/unrevoked2 it says that unrevoked3 doesn't work with stock Android 2.2 phones... which I'm guessing might be my condition since I had to flash the rom.zip file from RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe that I got from google.
Some clarification would be appreciated.
Looks like I'm back to root. Ran the PB31IMG.zip that was about 2.86mb, then payload-update.zip and the Su zip (anyone know where the most recent one is? Says there is an update).
Now to test WiFi tether again, see if I still need that evo driver still.
Sent from my ADR6300 using XDA App
You don't need the payload and stuff. After s-off all you need is the clockworkmod PB31IMG.zip to get root back
sent from Ioslver
The wifi tether has nothig to do with root. On some roms or just sometimes it wont work.
sent from Ioslver
I Have a Question, Would it be Possible to Root the Phone With a Update.zip From Android Recovery, Where it Says (Install From Update.zip)? Either That or Turn S-Off, Or Install Su, Clockwork Recovery...... Something? If Someone Can Help Please Do!! Or If Someone Can Try to Sign a Update.zip For Me With S-Off in it!! (Unrevoked.4Ever) I'd Loveto Find a Easier way that can be Done WITHOUT CONNECTING TO A (USB) PORT PC!!
Technically no. Because rooting your device is getting rid of the stock recovery so you can install rims and whatnot. But you can root through hboot easily with s-off or with s-on use unrevoked.
sent from Ioslver
So I'm wondering if the payload-update.zip was damaging in some way.
In any event, now I'm constantly being nagged about another 17.7mb update from Verizon which of course, like the Android 2.2 update, won't apply via the usual system update message.
I don't know where I can find this file, but it says this:
---
Android Update
Downloaded and verified 17.7 MB
This software update includes the installation of V CAST Apps, Slacker, and many other improvements for your DRIOD Incredible by HTC. ... blah blah blah ...
---
I don't know if this is the infamous 'November' update or not. I know that I updated my rom from the RUU file downloaded from dl.google.com, so its possible that I don't have this patching. Some clarification on what this download is, where I can find it (online or my phone), and if it is possible to apply this update and how (so I don't keep getting annoyed with it).
Thank you for droping in cause I really need your help! I made a huge mistake on it when I tried to unlock the phone.
The gfree method told that it doesn't work with radio higher than 26.03.02.xx but mine is 26.04.xx.xx. So I just did a stupid thing to found an older (official?) RUU and flashed it....
the radio has been downgraded to 26.02.15.xx(almost it) but the ship became s-on!!!!
And I tried the gfree several times on work! The former S-off method is depend on the offical rom so I thought it should not work as well...
What surprise me most is that the rom still has ROOT!! I've used clockmodrecovery to backup several times before the accident. The recovery still works however the radio cannot be flashed now and there is just S-ON!
So many words but I cannot find the point please help me, thank you
Now here is the brief situation:
1. The phone are now with an old radio. s-on and clockworkmod recovery(funny- -)
2. PC10IMG.img to flash radio failed. But by cwm recovery I can flash any rom or backup and restore any roms.
3. Before the situation I've once flashed a 4.02.17(?) radio and seems all gone right. Then I flashed a former radio as mentioned above and it comes here.
Are you sure you still have root ? Was it an official RUU you flashed ? Because all official RUUs will not have root (though you may be able to re-root, depending on the exact version).
A stock RUU/ROM will install a new hboot, and if you only had S-OFF via the eng hboot, you will lose that. Which is why everyone with S-OFF should make sure they have it via gfree.
What version of ROM are you running right now ?
This shouldn't be a new thread though, should be in an existing thread or in the Q&A forum
Thank you for your words! I flashed the RUU and found my rom is kept, just the radio downgraded and s-on...
I'm using the Q'N'D-miui rom...
Now I've tried to install new rom and I managed to install the CM6.1.1 tough the S-ON is still there, doesn't it mean I got the root? I the os I can find the superuser work correctly.
Sorry that I cannot find any similar situation in the forum and I'm new here...So I thought it can be a new thread
you might beable to just flash the spl by completing the last couple of steps ion the original g2 root process. don't quote me on this though, cuz i really don't know what i'm saying.
5. Open up terminal, type in "su" then press enter. Then without exiting type in "insmod /sdcard/wpthis-[YOURVERSION].ko" and press enter. Make sure you use the proper version of wpthis that applies to you. If you got the proper message type in "dd if=/sdcard/hboot-eng.img of=/dev/block/mmcblk0p18". Do not exit terminal in this step at all.
6. Exit terminal and run visionary again to make sure you're rooted.
7. Go back into terminal and type "su" then press enter, then type "sync". Wait about 10 seconds then pull the battery out.
8. Boot into recovery by holding volume down + power off until it comes up.
If it says S-OFF, you're rooted! Good job!
I'm [email protected]@ cuz I'm now using the miui rom not the origin one, which version of wpthis.ko is suitable for me?? Seems that just a mistake on it can bring me a brick...
So [rom] [guide] [kernal] [patch]...not [q]
I'm kinda confused what state your phone is in. Because if you are S-ON you wouldn't be able to flash any custom ROMs at all.
Sent from my HTC Desire Z
actually you might be able to skip the first step and just flash the spl
type in "dd if=/sdcard/hboot-eng.img of=/dev/block/mmcblk0p18". Do not exit terminal in this step at all.
6. Exit terminal and run visionary again to make sure you're rooted.
7. Go back into terminal and type "su" then press enter, then type "sync". Wait about 10 seconds then pull the battery out.
8. Boot into recovery by holding volume down + power off until it comes up.
If it says S-OFF, you're rooted! Good job!
....... if you have access to clockwork, someone could compile an update.zip to replace the spl......
but I'm a noob don't go on my opinion alone...... ask someone responsible for g2root to compile an update.zip for the spl IF you have access to clockwork recovery...
Yes now its s-on and still can be flashed!!
I've never heard before...
to master.peterm:
Now my rom has root... and I've tried the similar way as you said, but when I do the step it seems ok however it doesnt work as I went back into hboot it is still s-on...
I'm very much confused at this point. I know on the mt3gs, they could flash roms with s-on (but, with an eng hboot with test keys and cwm), but doesn't our RUU's all come with official hboots?
I'm not sure if once you're in cwm if it can bypass sig verifications though.
to PanCubano:
That's why I thought I should start a new thread... So strange which conflicts with the conclusion before.
s-on means the system permit no third-party flash right?? As I saw it, it's not right on my phone....backups and new cm rom can be flashed normally but seems that radio cannot be flashed..
And which method of rooting did you use before? Im assuming the rage method with the hacked eng hboot?
the irony of your name and your problem is kinda funny
to thatruth132:
my flashermaster is not this flash but adobe flash...
to PanCubano:
http://forum.xda-developers.com/showthread.php?t=833965
just the usual root method...
First, confirm that you legitimately have root. Download terminal emulator off the market. Open it, type su and hit enter. Superuser should prompt you for permissions. Hit allow and you should see your symbol go from $ to #
If yes, start the rooting method you did from step 2. If that's not the case above, start from step 1.
Since you already were able to sucessfully root the first time around, I still "strongly" suggest you always re-read every step (especially when you get to the dd commands)
Once you finish and can sucessfully confirm S-OFF via rebooting into hboot, come back here and follow the gfree method.
Do not skip out on doing the gfree method. Just because you were able to get s-off again (if you could) it doesn't mean you're done.
Finally I use the unpermroot method to restore the phone into stock state and do the gfree instead to s-off and simunlock the phone...
Thank you all above!! Though there is still no actual explanation of this.
Hey,
I rooted my phone and installed Clockwork mod recovery earlier. I'd like to unroot it, and remove the files from the phone. May send it back due to hinge issue.
I'm not sure where to start. I used the rage/gfree/ADB method on the wiki. I'm on 1.34.
Thanks!
Just re-flash the stock 1.34 ROM/RUU, then get temp root and run gfree with the necessary options to go back to S-ON.
Sent from my HTC Desire Z
Kaph said:
Hey,
I rooted my phone and installed Clockwork mod recovery earlier. I'd like to unroot it, and remove the files from the phone. May send it back due to hinge issue.
I'm not sure where to start. I used the rage/gfree/ADB method on the wiki. I'm on 1.34.
Thanks!
Click to expand...
Click to collapse
You can follow the guide on the wiki http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock but you can skip the "Install the stock image" part because you still have the stock image.
So just start at "radio S-ON and original CID"
Have fun - Guhl
Like Kaph I'm also trying to return to stock, but when I follow the guide on the wiki I get an error.
After I type in gfree -r /sdcard/part7backup.bin and pressing enter I get the following message:
"Error reading input file."
I'd like to try the other method but I don't know my original CID, is there a way to find that out?
I need to return my phone for warranty so help is much appreciated.
Edit: I've already tried reflashing the ROM, I was always running the stock rom without ota and rooted with rage and gfree.
Yeah I've been trying and I keep getting invalid input file.
Also, is there anyway to revert to stock recovery from Clockwork? I think that's hindering things. Unless that's part of the whole process.
Well after some fun I'm back to S-ON with the stock recovery. I'll try applying the OTA now.
But just a massive thanks to djfoo000 and this thread: http://forum.xda-developers.com/showthread.php?t=909755 as I couldn't get the method on the Wiki to work, but doing it in terminal seems to have done the trick and recovery is now showing S-ON. I also used his recovery.img as the versions matched my phone.
On the bright side I'm now a lot more comfortable with adb/etc heh.
My only other question is will all the gfree files and the like stay on the memory, and if so should I use rm to get rid of them? Or do they get deleted upon reboot?
sorry for what may be a stupid comment but will using the ruu not restore to factory?
The reason i ask is that the wiki has the guide for the tmobile g2 and not desire z?!