Related
Is it possible to use the 2.1 RUU after using the 2.2 RUU? I want to downgrade to use unrevoked. Thanks for the help.
If you're S-OFF, you can just root by installing a custom recovery using PB31IMG.zip and flashing a root zip.
Berzerker7 said:
If you're S-OFF, you can just root by installing a custom recovery using PB31IMG.zip and flashing a root zip.
Click to expand...
Click to collapse
yes.
if u are not s-off, the older RUUs are there on the forum, i dont see why not.
redd12345 said:
Is it possible to use the 2.1 RUU after using the 2.2 RUU? I want to downgrade to use unrevoked. Thanks for the help.
Click to expand...
Click to collapse
Watch this video, has instructions and the necessary files to download listed in the information section.
http://www.youtube.com/watch?v=eeuiURZZZds&feature=player_embedded
Easy directions, and brings you back to Stock 2.1, .77 HBOOT and 1.xx Radio. Essentially, the way your phone was when you purchased it.
You backup anything you can, this will wipe your device.
After finishing this process, if you want to go back to the 2.2 RUU with Root...
1. Perform unrEVOked Root Process.
2. Flash unrEVOked forever.
3. Flash Stock Recovery
4. Perform 2.2 RUU (you will lose your root... here)
5. Flash ClockworkMod (you can do this because of the S-OFF function being invoked)
6. Flash a root payload containing su and superuser.apk
7. If you want to go ahead and revert to Stock Android 2e recovery (being prepared for other OTAs in the future)
If you need help feel free to PM me.
Full of win!
rdmerck said:
Watch this video, has instructions and the necessary files to download listed in the information section.
http://www.youtube.com/watch?v=eeuiURZZZds&feature=player_embedded
Easy directions, and brings you back to Stock 2.1, .77 HBOOT and 1.xx Radio. Essentially, the way your phone was when you purchased it.
You backup anything you can, this will wipe your device.
After finishing this process, if you want to go back to the 2.2 RUU with Root...
1. Perform unrEVOked Root Process.
2. Flash unrEVOked forever.
3. Flash Stock Recovery
4. Perform 2.2 RUU (you will lose your root... here)
5. Flash ClockworkMod (you can do this because of the S-OFF function being invoked)
6. Flash a root payload containing su and superuser.apk
7. If you want to go ahead and revert to Stock Android 2e recovery (being prepared for other OTAs in the future)
If you need help feel free to PM me.
Click to expand...
Click to collapse
Thank you all so much!! I'm going to try this later tonight. If I want free tethering after 2.2 with root, do I just install the binaries and the old evo tether (pre) or has that changed too? I read something about changing a setting so Verizon doesn't pick it up.
Been reading through the root guides and notice all the gfree topics. I got perm root using the rage method months ago and was wondering if there were any advantages to the gfree method and if so can I still do the gfree
Sent from my HTC Vision using XDA App
Yes, you can and should use gfree, see the Wiki for details.
The Wiki also has a good explanation of why the S-OFF you have from the eng hboot is effectively only a "fake" S-OFF, and it is much safer to have the full radio S-OFF via gfree.
Sent from my HTC Desire Z
steviewevie said:
Yes, you can and should use gfree, see the Wiki for details.
The Wiki also has a good explanation of why the S-OFF you have from the eng hboot is effectively only a "fake" S-OFF, and it is much safer to have the full radio S-OFF via gfree.
Sent from my HTC Desire Z
Click to expand...
Click to collapse
So I read the wiki and I see what you mean now between the fake s-off and full s-off.
I too did the rage method months ago and am wondering if there are any advantages of using gfree to get the true s-off, besides the safety issue. I have successfully unrooted my G2 using this method: http://forum.xda-developers.com/showthread.php?t=831398 so I am pretty sure that I will not have any troubles if I need to revert to stock in case of a warranty issue.
If I do end up doing a warranty exchange, I will reroot using gfree, but should I run gfree now regardless?
Also, will doing gfree make this process easier of reverting to stock? From reading the wiki, it doesn't specify if I have permarooted using rage if I need to unroot to do the gfree way or if I can just do it over my currently rooted phone.
Or maybe it did and I just missed it XD
Sorry for the length and barrage of questions, but I don't wanna screw this up!
Also, sorry if I thread jacked, didn't mean to, but I didn't see the point in starting a new thread for the same question, just a bit more detailed in questioning.
I went through the whole wiki and had the same questions you saved me a whole lot of typing.
G2 cm6.1.1
tazz9690 said:
I too did the rage method months ago and am wondering if there are any advantages of using gfree to get the true s-off, besides the safety issue. I have successfully unrooted my G2 using this method: http://forum.xda-developers.com/showthread.php?t=831398 so I am pretty sure that I will not have any troubles if I need to revert to stock in case of a warranty issue.
Click to expand...
Click to collapse
The advantages are that full radio S-OFF can help you recover from certain conditions. e.g. on the Desire Z, some users flashed the 1.72 OTA update and found then that they couldn't root it. But those who had radio S-OFF were able to downgrade back to 1.34 and root again. Those with the "fake" S-OFF lost their S-OFF because a stock hboot was flashed, and they couldn't downgrade so are currently stuck without root.
If I do end up doing a warranty exchange, I will reroot using gfree, but should I run gfree now regardless?
Click to expand...
Click to collapse
Yes, I highly recommend that you do.
Also, will doing gfree make this process easier of reverting to stock? From reading the wiki, it doesn't specify if I have permarooted using rage if I need to unroot to do the gfree way or if I can just do it over my currently rooted phone.
Click to expand...
Click to collapse
It doesn't really make any difference to going back to stock. You can undo gfree with certain options to the command (see the Wiki for details). Downgrading with the full radio S-OFF is safer too, because you keep the S-OFF (until you remove it via gfree).
Thank you for the explanation, you sold me on gfree, but I'm not 100% sure on that last part steviewevie. So you are saying that I can run gfree in my current permrooted state with the fake s-off that I have with the hacked hboot? I do not need to unroot first and can just run gfree on top of what I already have?
Sent from my T-Mobile G2 using XDA App
tazz9690 said:
Thank you for the explanation, you sold me on gfree, but I'm not 100% sure on that last part steviewevie. So you are saying that I can run gfree in my current permrooted state with the fake s-off that I have with the hacked hboot? I do not need to unroot first and can just run gfree on top of what I already have?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Yes, you can run gfree on top of your already permrooted and ENG Hboot. That's exactly what I did.
Sent from my T-Mobile G2 using XDA App
Thanks for all the help guys it is appreciated
G2 cm6.1.1
Agreed. I appreciate it as well.
So, I'm looking at the wiki right now, and I don't need to start from the beginning of the process, or do I?
Where exactly did you begin the process joemm?
Sent from my T-Mobile G2 using XDA App
Got it if already permrooted and running a custom kernel you have to flash an older kernel for it to work I had a backup of the stock rom I flashed then push the gfree to data/local ran the commands given and am good to go now thank you all for the help
G2 cm6.1.1
Ok so I ran gfree and it worked great. I just restored my backup of CM6 that I had and everything looks good.
Now final question, do I have to reflash the hboot now that I have true s-off?
I know flashing hboot is unnecessary, but I do use fastboot flash from time to time.
Also, I downloaded the hboot, but when I do a md5 checksum of the extracted file like it does on the wiki, it says md5sum not found. Any reason as to why?
tazz9690 said:
Agreed. I appreciate it as well.
So, I'm looking at the wiki right now, and I don't need to start from the beginning of the process, or do I?
Where exactly did you begin the process joemm?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Start from here:
"gfree version 0.02 and its options
Since the current version 0.02 gfree supports the following options:
Code:
gfree usage:
gfree [-h|-?|--help] [-v|--version] [-s|--secu_flag on|off]
-h | -? | --help: display this message
-v | --version: display program version
-s | --secu_flag on|off: turn secu_flag on or off
-c | --cid <CID>: set the CID to the 8-char long CID
-S | --sim_unlock: remove the SIMLOCK
-f | --free_all: same as --secu_flag off --sim_unlock --cid 11111111
In the following steps the -f will be used to mimic the behavior of the original gfree version that will do radio S-OFF, Super-CID and simunlock in one go.
If you are only interested in permanent root you only need radio S-OFF and then it is sufficient to use
Code:
# ./gfree -s off
instead of
Code:
# ./gfree -f
in the following commands.
And gfree can now also be used to set radio S-ON by using the "-s on" option and to change the CID back to the original value be using i.e. "-c T-MOB010" if you want or have to go back. In addition since version 0.03 gfree can also be used t just to remove the write protection from the emmc and remove the kernels write filter to the radion partitions by using the "-w" option. This is handy if you want to restore your partition 7 backup.
ON YOUR PC:
Unzip gfree_02.zip to a place on your computer. Navigate to where the files are on your computer, and type:
Code:
$ adb push gfree /data/local
Gfree should now be in your phone at /data/local
ON YOUR PHONE:
You should still have terminal emulator up, at a root prompt from earlier.
Now run:
Code:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
# sync
You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:
Code:
# /data/local/tmp/root
# sync
Wait a few seconds for the changes to "take".
Now reboot your phone.
Congratulations! You're perma-rooted, radio S-OFF, and should have read-write access to your /system! But more than that, your phone should also be SIM-unlocked, so that you can use a SIM card from any carrier (T-Mobile, AT&T, Vodofone, etc.) See below for more info about that.
At this point you might consider downloading the 'Rom Manager app from the Android market and using it to install the Clockwork recovery and back up via the nandroid "backup" option should things go terribly wrong for you in the next (optional) step.
Also, gfree created a backup of your original partition 7 at /sdcard/part7backup-<time>.bin -- You might consider copying this to a safe location on your computer!"
For those who want to know where this info comes from its here at the HTC Vision Wiki: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
Thanks, yeah, I bit the bullet and thankfully started from there.
But now I have a new question.
Do have to reflash the hboot now that I have done the gfree method and now have true s-off instead of the fake s-off and the hacked hboot?
Do you know?
tazz9690 said:
Ok so I ran gfree and it worked great. I just restored my backup of CM6 that I had and everything looks good.
Now final question, do I have to reflash the hboot now that I have true s-off?
I know flashing hboot is unnecessary, but I do use fastboot flash from time to time.
Also, I downloaded the hboot, but when I do a md5 checksum of the extracted file like it does on the wiki, it says md5sum not found. Any reason as to why?
Click to expand...
Click to collapse
No you dont have to reflash the ENG Hboot, turn your phone off, then volume-down+power and on the first screen with the skateboarding andriod it will tell you on the first line "ENG S-OFF" which means you still have your ENG. Hboot, so you will be able to use fastboot.
Yeah I saw that but I just wanted to double check my assumption. Thank you for your help! I am all set now and worry free!
Sent from my T-Mobile G2 using XDA App
tazz9690 said:
Yeah I saw that but I just wanted to double check my assumption. Thank you for your help! I am all set now and worry free!
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Yes you are , have fun flashing.
Thank you I will. Now say, that I have to return my phone for warranty, I no longer have to change the version number of the pc10img.zip to revert back to stock like I used to have to do in this thread: http://forum.xda-developers.com/showthread.php?t=831398
since I have true s-off now. I can just flash the pc10img.zip and not have to worry about any repercussions by doing this, correct?
I just ran an experiment on my phone. Even if you rooted using Rage, gfree will still unlock everything.
tazz9690 said:
Thank you I will. Now say, that I have to return my phone for warranty, I no longer have to change the version number of the pc10img.zip to revert back to stock like I used to have to do in this thread: http://forum.xda-developers.com/showthread.php?t=831398
since I have true s-off now. I can just flash the pc10img.zip and not have to worry about any repercussions by doing this, correct?
Click to expand...
Click to collapse
I would say yes, you can just flash the pc10img.zip if you have gfree'd your phone with true radio s-off. I have not personally tried it myself, so again this is just my assumption, but found a few other post to agree with this:
Weaseal said:
If my understanding is correct, none of this matters if you did scotty2's gfree app to get S-OFF, since it doesn't muck with the hboot (rather, it modifies the radio config [NOT the radio]). So if you did that method to root/s-off (as opposed to the 'old'/alternate wpthis-eng-hboot method), you should be safe to flash PC10IMG without bricking. Can someone else sanity-check my logic?
Click to expand...
Click to collapse
steviewevie said:
You are correct. I think the OP is going to try and get this guide updated when he has the time.
Not sure this needs to be sticky at the moment, perhaps until it's been updated ?
Those who only have the eng hboot and not full radio S-OFF via gfree do need to be aware of this though.
Click to expand...
Click to collapse
Found these quotes here:
http://forum.xda-developers.com/showthread.php?t=838484&highlight=gfree&page=6
And heres a quote from someone who said they did flash pc10img after gfree with no issues:
luis86dr said:
I'm gfree'd and have flashed pc10img with no issues. If you have the hacked hboot that's different ballgame.
[G2/HTC Vision]
Click to expand...
Click to collapse
And when he says if you have a hack hboot, he means if that's all you have just root with ENG. Hboot, and not gfree. So it sounds like you should have no problems.
Found this quote from here Post #47:
http://forum.xda-developers.com/showthread.php?t=838484&highlight=gfree&page=5
You are a great man joemm. I appreciate the time you took to find that information.
I also appreciate everyone else who has helped me out in this thread.
Just makes me appreciate this forum even more!
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
Okay so it looks like there is a problem with applying the current perm root instructions to the Telus Desire HD... soliciting input here on how to make a proper root guide for Telus.
Something about the RUU downgrade to an earlier firmware is causing the DHD to lose sound (headset, speaker, everything). The perm-root and radio S-OFF proceeds as normal but sound is gone.
I've suggested that the next step could be to try and flash the Telus Ace RUU after getting radio S-OFF. Still awaiting confirmation as to whether this fixes the sound problem. One person attempted to flash back the Telus radio and this did not fix it. So it's got to be something else. HBOOT maybe?
So my question is, if you're on a higher build number (1.84.661.1) but you also have already achieved radio S-OFF, is there now any way to root the phone or install custom recovery? Without downgrading by RUU again?
Those of you who have experience with the DHD already might have some brilliant ideas, so I thought I'd ask =)
The first thing would be to look at the TELUS firmware and see if there are any drivers that are specific for the phone.
Sent from my Desire HD using Tapatalk
link to the file? thx
Look in the Dev forum for the one with Telus in its name.
This thread is falling off topic though... I'm specifically asking for people who can tell me more detail about what Radio S-OFF does and doesn't allow.
Let's forget this thread and go to the Telus thread in this QA section. The problem is not in hboot or radio, those have nothing to do with sound. The problem is in the ROM, and it's drivers most probably.
There is no way to properly root Telus ROM, so it is not possible to install custom recovery while you are using it. Please check the downgrade thread for my recommendations.
Okay fine, forget I ever mentioned Telus in this thread. Can someone just help me understand the limits of what Radio S-OFF does and doesn't allow?
Allows: more permanent S-OFF, which does not go away when you flash OTA or RUU. Disables write protection in internal memory, so you can flash ROMs. SuperCID allows you to flash anything from any carrier. Disables version checking, so you can sail between newer and older ROMs easily.
Does not allow: fastboot commands in bootloader, such as fastboot flash radio. So you cannot flash a radio & splash1 etc without ENG S-OFF.
jkoljo said:
Allows: more permanent S-OFF, which does not go away when you flash OTA or RUU. Disables write protection in internal memory, so you can flash ROMs. SuperCID allows you to flash anything from any carrier. Disables version checking, so you can sail between newer and older ROMs easily.
Does not allow: fastboot commands in bootloader, such as fastboot flash radio. So you cannot flash a radio & splash1 etc without ENG S-OFF.
Click to expand...
Click to collapse
Okay... so let's say you have radio S-OFF and you're using a newer build that normally wouldn't be rootable. Could you:
- Get the temporary rootshell (which is part of the downgrade instructions anyway)
- From the temporary rootshell, flash_image the custom recovery (which should be writable due to S-OFF)
- Reboot into custom recovery?
You would have to dd the recovery in, but yes that would work. Use command:
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
I still do not get why you would want to downgrade, get S-OFF, go back to Telus, and then get ClockworkMod..
You may have to install busybox to get dd working, in that case call it with "busybox dd if=..."
jkoljo said:
You would have to dd the recovery in, but yes that would work. Use command:
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
I still do not get why you would want to downgrade, get S-OFF, go back to Telus, and then get ClockworkMod..
You may have to install busybox to get dd working, in that case call it with "busybox dd if=..."
Click to expand...
Click to collapse
Well it's a conceivable scenario. Suppose you get your S-OFF, and then later on you have a reason to want to go back to stock RUU. The next time you want to be rooted or flash a custom ROM, wouldn't this be faster than doing a full downgrade first?
Well, ok, but who would want to go back to stock when there are custom roms..
Sometimes flashing a pure stock ROM is the only cure for having gotten a little too exuberant in one's hacking
Sent from my Nexus One using XDA App
Well, full wipe does the same trick.
Sent from my Desire HD using Tapatalk
Hi Guys, I have spent the last 2 days searching this forum and trying to understand what I need to do to bring my phone back to stock but can't seem to figure it out and thought I did post a new thread. Here is what I have,
HTC Evo4G
Android version 4.0.4
Baseband version 2.15.00.12.19
Kernal version 2.6.38.8-evervolv-acies-ics+
Build number MIUI-2.8.3.0 MIUI
If I go into recovery mode (the one that u get when u hold down power and volume down button), here is what I see,
*** RELOCKED ***
SUPERSONIC EVT2 SHIP S-ON
HBOOT 2.18.0001
I have tried to run RUU and each time it comes up with "Error 140: Bootloader version error"
Does anyone know how I can return my phone to stock please.
Which RUU are you trying to run? The RUU's Hboot has to be the same as what you already have, meaning it has to be Hboot 2.18.
designflaw said:
Hi Guys, I have spent the last 2 days searching this forum and trying to understand what I need to do to bring my phone back to stock but can't seem to figure it out and thought I did post a new thread. Here is what I have,
HTC Evo4G
Android version 4.0.4
Baseband version 2.15.00.12.19
Kernal version 2.6.38.8-evervolv-acies-ics+
Build number MIUI-2.8.3.0 MIUI
If I go into recovery mode (the one that u get when u hold down power and volume down button), here is what I see,
*** RELOCKED ***
SUPERSONIC EVT2 SHIP S-ON
HBOOT 2.18.0001
I have tried to run RUU and each time it comes up with "Error 140: Bootloader version error"
Does anyone know how I can return my phone to stock please.
Click to expand...
Click to collapse
You have to downgrade your hboot. to 2.10
FinZ28 said:
Which RUU are you trying to run? The RUU's Hboot has to be the same as what you already have, meaning it has to be Hboot 2.18.
Click to expand...
Click to collapse
Thank you.
accessing said:
You have to downgrade your hboot. to 2.10
Click to expand...
Click to collapse
How do I downgrade my hboot to 2.10?
Download the RUU from this link and run it through your bootloader. I believe you will need to rename it PC36IMG.zip for it to work. Make sure you don't have an extra .zip extension on the end.
http://forum.xda-developers.com/showthread.php?t=1484240
To downgrade your Hboot, you can use Captain Throwback's method for rooting Hboot 2.18. It involves using ADB to upgrade your misc. partition, which would then allow you to downgrade by running an older RUU.
Again, which RUU did you try to use originally?
Generally, since you are relocked s-on you can find a signed ruu file in which you can just flash from your relocked bootloader screen or you can run an ruu exe file from your computer. I do not know if there is a method for downgrading your hboot while on s-on but flashing a signed ruu or running an ruu exe will bring your bootloader down. If that don't work, then i would listen to this guy above my post lol and see if that method works.
FinZ28 said:
Download the RUU from this link and run it through your bootloader. I believe you will need to rename it PC36IMG.zip for it to work. Make sure you don't have an extra .zip extension on the end.
http://forum.xda-developers.com/showthread.php?t=1484240
To downgrade your Hboot, you can use Captain Throwback's method for rooting Hboot 2.18. It involves using ADB to upgrade your misc. partition, which would then allow you to downgrade by running an older RUU.
Again, which RUU did you try to use originally?
Click to expand...
Click to collapse
I've been having the same trouble, and already went through CT's method, but still had S-OFF. I then tried going to recovery and flashing unrevoked-forever-son but didnt work. I also installed RUU...4.65 thru PC, still S-OFF, then downgraded to RUU..3.29 tried to run unrevoked-forever-son again and still S-OFF.
I am able to get to stock rom just not back to S-ON
going cuckoo
UPDATE: Found answer: http://forum.xda-developers.com/showthread.php?p=16949711#post16949711
gellybelly said:
I've been having the same trouble, and already went through CT's method, but still had S-OFF. I then tried going to recovery and flashing unrevoked-forever-son but didnt work. I also installed RUU...4.65 thru PC, still S-OFF, then downgraded to RUU..3.29 tried to run unrevoked-forever-son again and still S-OFF.
I am able to get to stock rom just not back to S-ON
going cuckoo
Click to expand...
Click to collapse
I had the same problem also. It took me hours to figure this out. Before you can down grade to an earlier Hboot, you have to make sure the bootloader is unlocked from htc.devs, make sure that recovery is installed, and the phone has "su" rights superuser rights. It is critical that the phone have superuser installed and you have su rights before before you install these 2 files to your sd card. The first file is flash_image then the next one is mtd-eng. http://themikmik.com/attachment.php?...1&d=1327588554 http://themikmik.com/attachment.php?...1&d=1327588554
Unzip these files and copy it to your sd card. Then make sure your phone is in usb debugging mode, then go into command prompt on your pc, then type adb shell. then you should see a $ dollar sign. Type su and and you should see a # pound sign. Then enter these commands below one step a time.
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
Then you can install your PC36IMG to your sd card then install the it into bootloader or run the RUU from your pc following the instructions on the program. Make sure your phone is charged up. I prefer a full charge so there won't be issues. If you still have concerns, Re post back and let me know where you are stuck. I followed this guide when I had my supersonic: http://forum.xda-developers.com/showthread.php?t=1473373
Thank You and courtesy of Capt Throwback and THC Butterz for these guides.
Thank you
nice thread guys..been looking for this..:good:
FinZ28 said:
Download the RUU from this link and run it through your bootloader. I believe you will need to rename it PC36IMG.zip for it to work. Make sure you don't have an extra .zip extension on the end.
http://forum.xda-developers.com/showthread.php?t=1484240
To downgrade your Hboot, you can use Captain Throwback's method for rooting Hboot 2.18. It involves using ADB to upgrade your misc. partition, which would then allow you to downgrade by running an older RUU.
Again, which RUU did you try to use originally?
Click to expand...
Click to collapse
Jsparta26 said:
Generally, since you are relocked s-on you can find a signed ruu file in which you can just flash from your relocked bootloader screen or you can run an ruu exe file from your computer. I do not know if there is a method for downgrading your hboot while on s-on but flashing a signed ruu or running an ruu exe will bring your bootloader down. If that don't work, then i would listen to this guy above my post lol and see if that method works.
Click to expand...
Click to collapse
Thanks Guys. I downloaded the RUU and tried to run it from my PC. I went through screens and eventually came up with the error Error [140]: Bootloader version error.
Here are the versions I am on,
From:
Image version:
4.24.651.1
To:
Image version:
4.67.651.3
designflaw said:
Thanks Guys. I downloaded the RUU and tried to run it from my PC. I went through screens and eventually came up with the error Error [140]: Bootloader version error.
Here are the versions I am on,
From:
Image version:
4.24.651.1
To:
Image version:
4.67.651.3
Click to expand...
Click to collapse
Boot into fastboot, and from the path where you have fastboot.exe on your computer, run the command:
Code:
fastboot getvar mainver
and then report back what it says. If your main version is 5.07.651.1, then that RUU won't work, and you'll have to unlock again and downgrade your misc partition to flash back to stock. You should really flash a stock ROM while you're unlocked too. Having an ICS ROM on there and relocking and likely what's causing your issues.
chickipaul said:
I had the same problem also. It took me hours to figure this out. Before you can down grade to an earlier Hboot, you have to make sure the bootloader is unlocked from htc.devs, make sure that recovery is installed, and the phone has "su" rights superuser rights. It is critical that the phone have superuser installed and you have su rights before before you install these 2 files to your sd card. The first file is flash_image then the next one is mtd-eng. http://themikmik.com/attachment.php?...1&d=1327588554 http://themikmik.com/attachment.php?...1&d=1327588554
Unzip these files and copy it to your sd card. Then make sure your phone is in usb debugging mode, then go into command prompt on your pc, then type adb shell. then you should see a $ dollar sign. Type su and and you should see a # pound sign. Then enter these commands below one step a time.
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
Then you can install your PC36IMG to your sd card then install the it into bootloader or run the RUU from your pc following the instructions on the program. Make sure your phone is charged up. I prefer a full charge so there won't be issues. If you still have concerns, Re post back and let me know where you are stuck. I followed this guide when I had my supersonic: http://forum.xda-developers.com/showthread.php?t=1473373
Thank You and courtesy of Capt Throwback and THC Butterz for these guides.
Click to expand...
Click to collapse
Captain_Throwback said:
Boot into fastboot, and from the path where you have fastboot.exe on your computer, run the command:
Code:
fastboot getvar mainver
and then report back what it says. If your main version is 5.07.651.1, then that RUU won't work, and you'll have to unlock again and downgrade your misc partition to flash back to stock. You should really flash a stock ROM while you're unlocked too. Having an ICS ROM on there and relocking and likely what's causing your issues.
Click to expand...
Click to collapse
Here is the message I get,
C:\android>fastboot getvar mainver
< waiting for device >
So, what has happened since my last post is that I tried the directions that were given out by chickipaul, however, in trying that I was getting a segmentation error when trying to run '/data/flash_image misc /sdcard/mtd-eng.img' and I read some posts on here that folks having a segmentation error under icecream sandwich should try running the command on gingerbread. Because of that, I tried to put a gingerbread ROM and selected synergy. Now that I have done that, once the phone boots up, it gets to the lock screen Ok. When I try to unlock it, I keep getting messages that some process has died, I click Ok and another message pops up abt another process crashing, and so forth and so forth.
I am hoping that I just need to either install synergy rom again and hope it works Ok or somehow get another gingerbread ROM in there. From there, I could return to stock by installing the RUU. Right now if I run the RUU, the phone never boots into recovery (I think RUU never gets to connect to the phone because of all the processes crashing).
What do u think?
designflaw said:
Here is the message I get,
C:\android>fastboot getvar mainver
< waiting for device >
So, what has happened since my last post is that I tried the directions that were given out by chickipaul, however, in trying that I was getting a segmentation error when trying to run '/data/flash_image misc /sdcard/mtd-eng.img' and I read some posts on here that folks having a segmentation error under icecream sandwich should try running the command on gingerbread. Because of that, I tried to put a gingerbread ROM and selected synergy. Now that I have done that, once the phone boots up, it gets to the lock screen Ok. When I try to unlock it, I keep getting messages that some process has died, I click Ok and another message pops up abt another process crashing, and so forth and so forth.
I am hoping that I just need to either install synergy rom again and hope it works Ok or somehow get another gingerbread ROM in there. From there, I could return to stock by installing the RUU. Right now if I run the RUU, the phone never boots into recovery (I think RUU never gets to connect to the phone because of all the processes crashing).
What do u think?
Click to expand...
Click to collapse
Hi Design Flaw. I just read your current post about what you tried. It sounds like something got corrupted in system files of the phone, that's why your phone is crashing. Question can you get to your bootloader screen by removing the battery for a few seconds, reinstalling the battery then hold volume down and the power button at the same time. If you can get into the bootloader screen where it says on the top of your screen has the Hboot version 2.18 and the S-On. I recommend to unlock the bootloader with your unlock_token file from htc dev first. I will borrow my wife's evo 4g and let her have my evo 3d and try to duplicate the same concern on her phone to help you figure out your phone. Post back here when you have time to work on your phone. I will help you out.
designflaw said:
Here is the message I get,
C:\android>fastboot getvar mainver
< waiting for device >
So, what has happened since my last post is that I tried the directions that were given out by chickipaul, however, in trying that I was getting a segmentation error when trying to run '/data/flash_image misc /sdcard/mtd-eng.img' and I read some posts on here that folks having a segmentation error under icecream sandwich should try running the command on gingerbread. Because of that, I tried to put a gingerbread ROM and selected synergy. Now that I have done that, once the phone boots up, it gets to the lock screen Ok. When I try to unlock it, I keep getting messages that some process has died, I click Ok and another message pops up abt another process crashing, and so forth and so forth.
I am hoping that I just need to either install synergy rom again and hope it works Ok or somehow get another gingerbread ROM in there. From there, I could return to stock by installing the RUU. Right now if I run the RUU, the phone never boots into recovery (I think RUU never gets to connect to the phone because of all the processes crashing).
What do u think?
Click to expand...
Click to collapse
Do you have the HTC Drivers installed? Does your Bootloader say "FASTBOOT USB"? It sounds like either you don't have the drivers installed or you didn't select fastboot from the HBOOT list.
Once it says FASTBOOT USB, then run that command again and post the output.
Unfortunately, you can't downgrade the misc partition while you're on an ICS ROM - that's why you're getting the segmentation fault error.
Flash a stock Gingerbread ROM. Synergy isn't really a good choice.
Captain_Throwback said:
Do you have the HTC Drivers installed? Does your Bootloader say "FASTBOOT USB"? It sounds like either you don't have the drivers installed or you didn't select fastboot from the HBOOT list.
Once it says FASTBOOT USB, then run that command again and post the output.
Unfortunately, you can't downgrade the misc partition while you're on an ICS ROM - that's why you're getting the segmentation fault error.
Flash a stock Gingerbread ROM. Synergy isn't really a good choice.
Click to expand...
Click to collapse
Hey there ... I did not know that I had to run that when I was in bootloader and fastboot usb was being displayed. I was trying to run it when my phone was connected to the PC. I just booted into bootloader and while fastboot usb was up there on the screen, I ran the command and here is what I see,
C:\android>fastboot getvar mainver
mainver: 1.17.651.1
finished. total time: 0.003s
Synergy ROM did not work for me so I had to go back to MIUI.us. Now that I have a working phone and I can copy over files to the phone, I am going to flash urayamashii ROM and see if I can run ruu after that.
Thank you so much for your help!
designflaw said:
Hey there ... I did not know that I had to run that when I was in bootloader and fastboot usb was being displayed. I was trying to run it when my phone was connected to the PC. I just booted into bootloader and while fastboot usb was up there on the screen, I ran the command and here is what I see,
C:\android>fastboot getvar mainver
mainver: 1.17.651.1
finished. total time: 0.003s
Synergy ROM did not work for me so I had to go back to MIUI.us. Now that I have a working phone and I can copy over files to the phone, I am going to flash urayamashii ROM and see if I can run ruu after that.
Thank you so much for your help!
Click to expand...
Click to collapse
If that's your mainver, you should be able to run any RUU or signed PC36IMG.zip.
First though, you need to flash a stock Gingerbread ROM. Every ROM you talk about flashing is not a stock ROM. That's the first thing you need to do. Then you can relock, and I'd run the 4.54 PC36IMG.zip through HBOOT to restore back to stock (you can get it from the "Restore stock" link in my sig).
Captain_Throwback said:
If that's your mainver, you should be able to run any RUU or signed PC36IMG.zip.
First though, you need to flash a stock Gingerbread ROM. Every ROM you talk about flashing is not a stock ROM. That's the first thing you need to do. Then you can relock, and I'd run the 4.54 PC36IMG.zip through HBOOT to restore back to stock (you can get it from the "Restore stock" link in my sig).
Click to expand...
Click to collapse
When you say run 4.54 PC36IMG.zip through HBOOT, what do you mean? If I goto the link that is in your sig and downloaded, that is a RUU and the fullname is PC36IMG_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15.00.0808_NV_2.15_release_220182_signed.zip. Can I just rename it PC136IMG.zip and put in the root folder of sdcard and then from bootloader install it?
designflaw said:
When you say run 4.54 PC36IMG.zip through HBOOT, what do you mean? If I goto the link that is in your sig and downloaded, that is a RUU and the fullname is PC36IMG_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15.00.0808_NV_2.15_release_220182_signed.zip. Can I just rename it PC136IMG.zip and put in the root folder of sdcard and then from bootloader install it?
Click to expand...
Click to collapse
Yes, that's the link, and the procedure to flash it - but you will have to be relocked first for it to work.
And an RUU is not the same as a PC36IMG file, which is why I made the distinction. One is run from a PC, the other is installed directly from the device.
Captain_Throwback said:
Yes, that's the link, and the procedure to flash it - but you will have to be relocked first for it to work.
And an RUU is not the same as a PC36IMG file, which is why I made the distinction. One is run from a PC, the other is installed directly from the device.
Click to expand...
Click to collapse
Thanks again! So, dumb qs here but why RUU won't work when installing from PC (gives incorrect version error) but when installing directly from device, it is Okay?
designflaw said:
Thanks again! So, dumb qs here but why RUU won't work when installing from PC (gives incorrect version error) but when installing directly from device, it is Okay?
Click to expand...
Click to collapse
I have no idea. It should really work either way. Not sure why it doesn't. Though . . . It could be because the device can't reboot into RUU mode because you're not running it from a stock Gingerbread ROM (like I keep saying you need to flash).