Related
So in my efforts to update my phone, I downloaded the July 2010 OTA radio. I also tried flashing the sprint radio 2.42.02.10.29
To my surprise, neither of them worked. It's like I am permanently unable to flash a radio. I can flash roms, themes, boot animations and everything else, just not radios. If anyone has any suggestions for this I greatly appreciate it. Here are the radios I've tried to flash and where I got them from.
2.42.01.04.27 from http://forum.xda-developers.com/showthread.php?t=728529
2.42.02.10.29 from http://forum.xda-developers.com/showthread.php?t=853868
Haven't seen anyone else on here ever have this issue except for 1 person and when I checked his post, no one had replied to it and it was almost a year old lol. Any help with this at all ?
spc_hicks09 said:
2.42.02.10.29 from http://forum.xda-developers.com/showthread.php?t=853868
Haven't seen anyone else on here ever have this issue except for 1 person and when I checked his post, no one had replied to it and it was almost a year old lol. Any help with this at all ?
Click to expand...
Click to collapse
So you are saying that you followed those instructions exactly and it did not flash?
In other words, you:
- copied that 2.42.02.10.29.zip file to the root of your SD card;
- you checked the MD5 of that file to make sure that it was fully downloaded;
- restarted in recovery and flashed that .zip file;
- you rebooted the phone and a very different screen appeared;
- it went back to Recovery with a message at the bottom saying "formatting cache..."
- you waited about a minute (it says 5 seconds, but I waited longer) and then rebooted the phone
And your radio baseband version did not update?
That's exactly what I'm saying. I flashed both radios and waited 10-15 on both of them and neither one of them did anything !?! So confused
Sent from my Ginger Tazz using XDA App
Well, if it's any consolation I haven't noticed anything different about that radio. People report that they get more "bars", but that's just a display thing - it doesn't mean that they get better performance or signal from the radio version.
You can try unrooting with btfb0's Flashback21 ROM - there is a version that flashes the current Verizon radio - and then re-root after that and see if it updates the radio for you.
http://forum.xda-developers.com/showthread.php?t=792026
Take the version of that with the radio, obviously.
What bootloader (version) and recovery (version) are on the phone when you perform the flashing operation?
What is the version # of the radio firmware which doesn't get removed/overflashed?
When you complete the flashing operation, are you using the reboot menu item? (I'm presuming you are not pulling the battery or something unusual like that, but thought I would ask for completeness sake)
bftb0
PS If you have the engineering bootloader on your phone (1.49.2000 S-OFF), you can just flash the radio with fastboot from the PC:
Code:
fastboot flash radio radio.img
bftb0 said:
What bootloader (version) and recovery (version) are on the phone when you perform the flashing operation?
What is the version # of the radio firmware which doesn't get removed/overflashed?
When you complete the flashing operation, are you using the reboot menu item? (I'm presuming you are not pulling the battery or something unusual like that, but thought I would ask for completeness sake)
bftb0
PS If you have the engineering bootloader on your phone (1.49.2000 S-OFF), you can just flash the radio with fastboot from the PC:
Code:
fastboot flash radio radio.img
Click to expand...
Click to collapse
At work now but I will check it out when I get home. Im not sure how to check some of the stuff you're talking about so I will need your guidance later if possible.
Sent from my Ginger Tazz using XDA App
bftb0 said:
What bootloader (version) and recovery (version) are on the phone when you perform the flashing operation?
What is the version # of the radio firmware which doesn't get removed/overflashed?
When you complete the flashing operation, are you using the reboot menu item? (I'm presuming you are not pulling the battery or something unusual like that, but thought I would ask for completeness sake)
bftb0
PS If you have the engineering bootloader on your phone (1.49.2000 S-OFF), you can just flash the radio with fastboot from the PC:
Code:
fastboot flash radio radio.img
Click to expand...
Click to collapse
Recovery Version
RA-eris-v1.6.2
On HBOOT screen I see this:
PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.00.04.12
FEB 8 2010, 00:08:56
Radio that will not change or anything is:
2.42.00.04.12 which is the pre July 2010 OTA update Radio
Yes you presumed right, I am "rebooting" through the recovery menu as opposed to pulling the battery or anything else.
Executive summary: just get the engineering bootloader (1.49.2000 S-OFF) installed on your phone, and flash radios using fastboot (being very very careful to verify MD5 signatures). If you are going to be flashing stuff to your phone frequently, you really want the S-OFF bootloader on your phone for disaster recovery reasons anyway.
OK, I ran a fairly long experiment on your behalf, and it went like this:
- flash 2.42.02.10.29.zip from Amon_RA (succeeded; bootloader was 1.49.2000 S-OFF)
- flashed older radio (2.42.00.04.12) image file back into place using fastboot (not Amon_RA)
- Downgraded my bootloader to 1.49.000 S-ON using fastboot
- flash 2.42.02.10.29.zip from Amon_RA (failed; bootloader was 1.49.0000 S-ON)
- Upgraded my bootloader using "erisengspl.zip" + Amon_RA **** back to 1.49.2000 S-OFF
- flash 2.42.02.10.29.zip from Amon_RA (failed; bootloader was 1.49.2000 S-OFF)
- rebooted once (into OS) and then booted into recovery
- flash 2.42.02.10.29.zip from Amon_RA (succeeded; bootloader was 1.49.2000 S-OFF)
So, I was expecting to see that your trouble had something to do with your bootloader version - especially after seeing the first failure that I observed ... but then I was able to get it to both succeed and fail using the same S-OFF (1.49.2000) bootloader - and the only thing which changed was that I rebooted once between the trial that succeeded, and the trial which failed.
At that point, I did not go back and re-run any trials with the 1.49.0000 S-ON bootloader to see if I could get it to suceed - because it was evident that something else was going on.
Some of this is not entirely unexpected. When you flash either of the firmware images (either the radio or the bootloader image files), it is actually the bootloader that does the flashing, not the recovery boot: that's why the recovery tells you to "reboot .... to complete the installation". What the recovery does is to "stage" the image file (in /cache, I suspect), and then write some instructions into the "misc" partition that tell the bootloader what to do the next time the phone resets.
That's why - when things work correctly - the phone momentarily goes dark, you see a graphic image on the screen (that suggests that flashing is taking place), and then the phone reboots again ... and ends up back in the recovery boot !! (You will have to take my word for it, if you don't remember what it looks like). That "flashing" graphic image is put up on the screen by the bootloader; when it finishes up, it chains back to the recovery boot ... and communicates to the recovery (via the either the misc partition or the cache partition), "hey, wipe the /cache partition as soon as you start up". (Note the implications - the next OS reboot will need to rebuild the dalvik-cache(s))
The thing is, "misc" gets written to every time the phone shuts down or boots up - whether we are talking about starting from the OS, from the recovery boot, from fastboot mode, or from RUU mode - and how many different ways are there to reboot?
- battery pull
- fastboot reboot-recovery
- fastboot reboot
- adb shell reboot bootloader
- adb shell reboot recovery
- reboot Amon_RA from menu
- (cold start) -> fastboot mode -> hboot mode -> recovery
- (cold start) -> hboot mode -> recovery
- (cold start) -> recovery
In any event, if you want to tease this all out, with some experimenting around with the way that you get into the recovery boot, you can probably get the flashing method to work. ( For instance, you could probably use an adb shell session with Amon_RA running to "flash_image misc misc.img", where "misc.img" is the image file from jcase's "Flash Any RUU post" - and then use the flashable radio .zip file from within Amon_RA. )
But, as I mentioned above, it is a lot easier to just punt and install radios using fastboot and the S-OFF bootloader. Just be sure you have triple-checked everything before you hit the Enter key.
bftb0
**** EXTREMELY DANGEROUS UNLESS THE EXISTING BOOTLOADER IS 1.49.0000 - "erisengspl.zip" has hard-bricked phones that had 1.46.0000 bootloaders!
I really appreciate all the work man ! I did a search in the forums though and can't find the S-OFF bootloader. As soon as I read your question about the bootloader I was seriously wondering if it was because I have the S-ON bootloader. However, since you got both a success and a fail with the S-ON i'm not sure now what to think. I would like to get the S-OFF bootloader though so if you got a link to that, it would be greatly appreciated. Also again, thank you for the hard work and the time you put into all this man. Your knowledge never ceases to amaze me !
This would be what I want correct ?
http://forum.xda-developers.com/showthread.php?t=725047
Seems like a lot of work to get 1.49.2000 S-OFF
Also, do I have to go back to stock to do this ?
spc_hicks09 said:
I really appreciate all the work man ! I did a search in the forums though and can't find the S-OFF bootloader. As soon as I read your question about the bootloader I was seriously wondering if it was because I have the S-ON bootloader. However, since you got both a success and a fail with the S-ON i'm not sure now what to think. I would like to get the S-OFF bootloader though so if you got a link to that, it would be greatly appreciated. Also again, thank you for the hard work and the time you put into all this man. Your knowledge never ceases to amaze me !
This would be what I want correct ?
http://forum.xda-developers.com/showthread.php?t=725047
Seems like a lot of work to get 1.49.2000 S-OFF
Also, do I have to go back to stock to do this ?
Click to expand...
Click to collapse
You don't need to go back to stock to do that. That post will work. Slightly more effort than necessary, though.
You probably ought to familiarize yourself with the "old-fashioned" method of flashing a PB00IMG.ZIP file (see this post on AF (lots of pictures) for some background). All Eris RUUs, OTAs, and PB00IMG.ZIP files can be found at this XDA post
Because you have the 1.49.0000 S-ON bootloader, your phone would previously have been referred to as a "Leaker" phone. The only thing which stood in the way of "Leakers" applying any PB00IMG.ZIP file is that the "misc" partition contains a version number in it which blocks that from happening. jcase's method in that post you provided a link to is to "patch" the misc image with an older version number, and then you can proceed with any PB00IMG.ZIP file installation after you have patched the "misc" partition.
There is another option available to you, though, but I am reluctant to suggest it to you: because you have the 1.49.0000 bootloader, the "erisengspl.zip" flash method of installing the bootloader should work for you. (IT HAS BRICKED A 1.46.0000 PHONE, and there have been only a few people that have used it - I did it one hour ago, but hey, that's my phone, and there's a huge difference between doing something to your own phone and telling other people to do it).
If you want to try an alternative method, which should be:
- less effort than the URL link you provided
- safer than using "erisengspl.zip"
I could whip up a flashable version of "misc.img" - that way you don't need to fool around with adb commands - you would just flash a zip file that patches misc.img (instead of doing that manually with adb), and then after that just install the Root PB00IMG.ZIP ROM by putting it on the root folder of your SD card and powering up your phone (after you have made Nandroid backups and fully charged your phone, of course).
Say the word and I'll cobble that together.
bftb0
Here you go...
Introducing...
ErisMiscReset_v0.9.zip :
Size: 53,784 bytes
MD5: aeb8f3d9b2ab39379b8ee563c76efee0
Credits: jcase (for the misc.img file); Amon_RA (for the flash_image binary - from his v1.6.2 Eris recovery)
This doesn't do anything special - it just flashes the embedded "misc.img" file (jcase) to the "misc" partition. It could be done the hard way (with adb and the command line), but this makes life a little easier.
bftb0
bftb0 said:
You don't need to go back to stock to do that. That post will work. Slightly more effort than necessary, though.
You probably ought to familiarize yourself with the "old-fashioned" method of flashing a PB00IMG.ZIP file (see this post on AF (lots of pictures) for some background). All Eris RUUs, OTAs, and PB00IMG.ZIP files can be found at this XDA post
Because you have the 1.49.0000 S-ON bootloader, your phone would previously have been referred to as a "Leaker" phone. The only thing which stood in the way of "Leakers" applying any PB00IMG.ZIP file is that the "misc" partition contains a version number in it which blocks that from happening. jcase's method in that post you provided a link to is to "patch" the misc image with an older version number, and then you can proceed with any PB00IMG.ZIP file installation after you have patched the "misc" partition.
There is another option available to you, though, but I am reluctant to suggest it to you: because you have the 1.49.0000 bootloader, the "erisengspl.zip" flash method of installing the bootloader should work for you. (IT HAS BRICKED A 1.47.0000 PHONE, and there have been only a few people that have used it - I did it one hour ago, but hey, that's my phone, and there's a huge difference between doing something to your own phone and telling other people to do it).
If you want to try an alternative method, which should be:
- less effort than the URL link you provided
- safer than using "erisengspl.zip"
I could whip up a flashable version of "misc.img" - that way you don't need to fool around with adb commands - you would just flash a zip file that patches misc.img (instead of doing that manually with adb), and then after that just install the Root PB00IMG.ZIP ROM by putting it on the root folder of your SD card and powering up your phone (after you have made Nandroid backups and fully charged your phone, of course).
Say the word and I'll cobble that together.
bftb0
Click to expand...
Click to collapse
Ok quick question. After doing some digging, I found a post where jcase was working on a flashable zip that would give 1.49.2000 S-OFF. Someone noted that he no longer had an Eris and abandoned the project after pulling it. Well someone else "drewrobinso" picked up where jcase left off and finished the zip and in the post, starting at post 32 he posted that he fixed jcase's file and people after that say it "works perfectly." So I was wondering what your opinion is on this method. It can be found here.
http://forum.xda-developers.com/showthread.php?t=742735&highlight=engineering+bootloader&page=4
Here are the instructions they give for the hboot1492.zip
1) Download hbootupdate.zip
2) Placed it on root of sdcard
3) booted Recovery
4) nand backup
5) flashed hbootupdate.zip
6) rebooted (with menu) after the install of the hboot.zip
7) waited untill it came back to the recovery screen with " formatting cache..." at the bottom.
8) Waited for a few min then pressed reboot from the menu again.
9) waited for it to boot up and rebooted in to hboot as S-OFF was there
10) enjoyed it
spc_hicks09 said:
So I was wondering what your opinion is on this method. It can be found here.
Click to expand...
Click to collapse
Probably equivalent to the "erisengspl.zip" file (I haven't used it or looked at it) - you can find both, unpack them, and compare the differences. They should be extremely similar. I think the reason that jcase pulled his effort is because someone ended up with a brick - but I can't be 100% certain of that.
The thing you should be aware of is the lack of testing that goes into stuff on XDA. That "erisengspl.zip" floated around on XDA for months, and a few people in fact used it successfully. Those few people happened to be "Leakers" (with 1.49.0000 S-ON) on their phones.
The first person to try it with the 1.46.0000 S-ON bootloader on his phone hard-bricked his phone.
I suppose that it will work for you - but, flashing the bootloader is the most dangerous thing you can do to your phone. I prefer to be conservative about it.
LOL, I just realized that I said that after flashing it three times today.
PS we posted 60 seconds apart - look up above your post for a "misc" flasher .zip
bftb0 said:
PS we posted 60 seconds apart - look up above your post for a "misc" flasher .zip
Click to expand...
Click to collapse
Oh lol, sorry about that. Ok so if I use the misc flashable zip, which PB00IMG.ZIP would I want for the S-OFF, Leak 3 or the Root one ? I'll just use the method you're suggesting but I have no idea which PB00IMG.ZIP to use.
Nevermind lol obviously it would be the Root one since it's the only one with the Engineering Bootloader. Ok so if I downloaded the misc reset file and the PB00IMG.ZIP, do I flash the misc reset zip then the PB00IMG or what ?
bftb0 said:
If you want to try an alternative method, which should be:
- less effort than the URL link you provided
- safer than using "erisengspl.zip"
I could whip up a flashable version of "misc.img" - that way you don't need to fool around with adb commands - you would just flash a zip file that patches misc.img (instead of doing that manually with adb), and then after that just install the Root PB00IMG.ZIP ROM by putting it on the root folder of your SD card and powering up your phone (after you have made Nandroid backups and fully charged your phone, of course).
Say the word and I'll cobble that together.
bftb0
Click to expand...
Click to collapse
Nevermind LOL ! I swear as I get older I forget more and more stuff ! You gave me the directions right in your other post hahahaha. Ok so i'm going to charge my phone up then follow the instructions in this post and hopefully a couple hours from now I'll have the S-OFF bootloader. I'll definitely keep you updated once I start the process and hopefully we can get this resolved !!!
Flashed the zip and got the PB00IMG loading now. So far so good !
Now saying 1.49.2000 S-OFF !!!! Now it's going through and loading the system, recovery, radio_v2. Everything says -OK so far !
Rebooting now.......on the Verizon splash screen.............now it's not going anywhere just stuck on the Verizon logo !
Nevermind it booted ! Just took a while to load up !!!! Soon as everything is done loading I will check and see what the HBOOT screen says now.
Software Info:
Firmware - 2.1
Baseband - 2.40.00.01.22
Kernel - 2.6.29-5898f66b [email protected] #1
Build Number - 2.19.605.1 CL123435 test keys
Software Number - 2.19.605.1
Browser Version - WebKit 3.1
PRI Version - 2.11_002
PRL Version - 52219
ERI Version - 5
Rooting now with Eris 1 Click and will post HBOOT info in a few minutes.
spc_hicks09 said:
Nevermind LOL ! I swear as I get older I forget more and more stuff ! You gave me the directions right in your other post hahahaha. Ok so i'm going to charge my phone up then follow the instructions in this post and hopefully a couple hours from now I'll have the S-OFF bootloader. I'll definitely keep you updated once I start the process and hopefully we can get this resolved !!!
Click to expand...
Click to collapse
- Get the Root PB00IMG.ZIP file from this XDA post
- Verify it's size and MD5 signature on the copy you transferred to the root folder on your SD card.
- Put your phone on a charger.
- While it is charging, read through this post on AF (lots of pictures)
- Wait until fully charged, and
- Boot into recovery and make a Nandroid backup.
- (Optional: wipe data/factory reset)
- Flash the ErisMiscReset_v0.9.zip
- Power the phone off
- Boot the phone into HBOOT mode (Vol-Down+End)
- Follow the instructions in that Android Forums thread (PB00IMG.ZIP install)
Note that if you do not do the battery-pull trick, you will be overwriting everything on the phone. (That's OK because you have a backup, right?). If you did the "battery pull trick", you are done.
You can re-root the "root ROM" at that point, or, just skip that and use fastboot on your PC to directly flash the recovery to your phone. Put the phone in fastboot mode (cold-start with Send+End), and then test connectivity to the PC with:
Code:
fastboot devices
You should see your phone ID number if you are communicating correctly. Then,
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
Then, boot into Amon_RA directly by cold-starting the phone with Vol-Up+End, and "wipe data/factory reset" and restore your Nandroid backup.
Finally, you can flash a radio image directly at this point. (Note that we are not talking about a zip file, but the individual "radio.img" file that you would dig out of the 2.42.blahblahblah.zip file). Restart the phone in Fastboot Mode (Send+End) and
Code:
fastboot flash radio radio.img
Don't forget to remove the PB00IMG.ZIP file from the root folder of your SD card - otherwise you will forget about it and the next time you boot into HBOOT mode, the bootloader will start loading it up again.
HTH
bftb0
This explains a lot... Thanks.
I've not been able to figure out why my radio won't update until now.
And it allllllllll WORKED !!!!
HBOOT Info:
PB00100 XC ENG S-OFF
HBOOT-1.49.2000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.40.00.01.22
Jan 24 2010, 22:35:57
Dude you are a frickin genius !!!!! LOL
So now I should be able to update my Radio with either fastboot or adb or just by flashing right ?
You should make a main topic in Developement about your new method to get S-OFF. That was so much more simple than ANYTHING else I found !
Where do I need to have the Radio.img file because I have it in the ADB folder right now, trying to flash through fastboot but it keeps saying "error cannot load radio.img"
spc_hicks09 said:
And it allllllllll WORKED !!!!
Click to expand...
Click to collapse
You've now experienced "old school Eris root".
spc_hicks09 said:
So now I should be able to update my Radio with either fastboot or adb or just by flashing right ?
Click to expand...
Click to collapse
You certainly should be able to do it with fastboot. As I said before, I'm not precisely sure what was causing your Amon_RA installs to fail.
Just make sure you always, always, always verify file MD5 sigs of image files before flashing them with fastboot.
bftb0
Instructions Part 1
This thread is not for discussing general Honeycomb problems so don't post here if it's not related to running this procedure.
Important: Charge your Flyer fully before running this procedure ( see section: problems below)
This version is the release version of HoneyComb from HTC.
If you are on Honeycomb and got there by following other honeycomb install methods than the one in this thread then you MUST follow the steps in part 1.
If you are already S-OFF on gingerbread, or ran *this* procedure previously skip to Part 2.
You must be running a version of gingerbread supported by revolutionary
If you are not on an appropriate gingerbread version, eg. if you have upgraded to honeycomb then downgrade by using an appropriate RUU; to identify your RUU see: here
If you get the following error: "Main Version is older! Update Fail! Press <POWER> to reboot" the instructions are here for windows or here for Mac/Linux
Run revolutionary, there is no reason to install ClockWorkMod recovery at this point, say no when asked.
After following the steps above, you should be on a stock Gingerbread installation with revolutionary S-OFF.
Instructions Part 2
The large download is a stock HoneyComb 3.55.405.1 for 3G and 3.55.1114.31 for WIFI with the following changes:
Rooted
Busybox
Secure flag turned off on the boot image
Stock recovery replaced by CWM
Beginner procedure: If you are a novice using windows
Download the appropriate RUU file:
Code:
3G [URL="http://hyuh.net/files/flyer/RUU_3G_B09.zip"]RUU_3G_B09.zip[/URL]
WIFI [URL="http://hyuh.net/files/flyer/RUU_FLYER_WIFI_B10.zip"]RUU_FLYER_WIFI_B10.zip[/URL]
US-WIFI [url=http://hyuh.net/files/flyer/RUU_FLYER_WIFI_BBUS_B10.zip]RUU_FLYER_WIFI_BBUS_B10.zip[/url]
Extract the downloaded file. Open the extracted folder and run ARUWizard.exe
Click through the wizard and wait for it to complete
You're done, do not do any of the steps below.
Advanced procedures: If you want more control or are using MacOS or Linux
download the file that you require as follows:
If you want a stock rooted HoneyComb ROM
Be warned this is a BIG download :
Code:
MD5 Filename
--------------------------------------------------------------
3G-Wifi: D6BA3D134B9D60C865187F42C66B996B [URL="http://hyuh.net/files/flyer/PG41IMG-3G-B09.zip"]PG41IMG-3G-B09.zip[/URL]
Wifi only: f215eec88fe4b000cc9b3063c0724bdc [URL="http://hyuh.net/files/flyer/PG41IMG-WIFI-B10.zip"]PG41IMG-WIFI-B10.zip[/URL]
US WIFI: 8ffedc67d4c1032e601e81adf0cfebe3 [url=http://hyuh.net/files/flyer/RUU_US_WIFI_B10.zip]RUU_US_WIFI_B10.zip[/url]
If you intend to immediately install a custom HC ROM:
Code:
MD5 Filename
--------------------------------------------------------------
3G-Wifi: f1a04839f7b187887c77b4ab552cc2fb [URL="http://hyuh.net/files/flyer/HC-3g-light.zip"]HC-3G-light.zip[/URL]
Wifi only: 3c3cf126250ba5c9d996262acc334942 [URL="http://hyuh.net/files/flyer/PG41IMG-WIFI-light-B10.zip"]PG41IMG-WIFI-light-B10.zip[/URL]
Install the custom RUU
If you are running this procedure starting from Gingerbread the rom flash WILL fail first time, you must flash twice, if starting from honeycomb it might only require a single pass.
Method1: Using fastboot:
Get fastboot and adb tool for windows here, get Windows fastboot drivers here
Get Fastboot and adb for linux here
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <downloaded file name>
[I][COLOR=Blue]Flashing will fail with Error 90 first time due to hboot change[/COLOR][/I]
fastboot flash zip <downloaded file name>
[I][COLOR=Blue]The on screen indicator on the phone will not reach fully to the right end of the progress bar, this is ok[/COLOR][/I]
fastboot reboot
Method 2: Using bootloader - NOTE I strongly recommend using method 1.
Rename the downloaded file PG41IMG.zip
Transfer the file to the root of your SD card
Reboot to hboot, which will detect and install the update.
Note it will require two passes to complete the upgrade due to hboot change
If you used the full upgrade file (BIG download) you are finished, enjoy.
If you used the light image now restore your nandroid backup or flash your custom ROM now - then you are finished.
Problems
If you encounter problems after this procedure where your device does not boot properly (white screen with HTC logo) . Power-off fully and seek assistance from me. The reason for this is that you may have an invalid combination of hboot and recovery/boot images. In such a scenario a flyer will not charge when powered off. The reason for powering off at this point is to ensure that there is sufficient battery power remaining to fix the problem before you end up in an unrecoverable state. If the battery falls below 30% you will not be able to flash and I will not be able to help you. Do this by booting into fastboot mode then choosing power-down from the menu.
Credits
Paul O'Brien for getting his hands on the early leaks.
Team Revolutionary for the S-OFF and IEF for hboot
attn1 for the revolutionary version of recovery and Paul O'Brien for the patched version.
lpasq, RMarkland for the previous donations that made Wifi testing possible.
History
2011-12-30
Rebase of WIFI version to first official WIFI release 3.55.1114.31
2011-12-03
Files renamed to include build number to track changes.
Rooting fixed, su now works.
2011-12-03
Files renamed to avoid problems during upload.
2011-12-02
Updates PG41IMG.zip files to fix root problems.
2011-12-01
Code:
3.48.405.1 - At the time of update these files had been downloaded 1144 times.
MD5 Filename
--------------------------------------------------------------
3G-Wifi: 2c43cc7af063213ea948abcb249752c1 [URL="http://www.multiupload.com/PVNV5A29LX"]PG41IMG.zip[/URL]
Wifi only: ac7f97703a7d013b188e7fb689a80146 [URL="http://www.multiupload.com/REWO7JN8I7"]PG41IMG.zip[/URL]
3G-Wifi: 8b9f96dadc03c72385fb648fc74d4ef8 [URL="http://www.multiupload.com/GWNGLY5EJK"]HC-3G-light.zip[/URL]
Wifi only: 6acab3919d198933f95d987a0093fbfc [URL="http://www.multiupload.com/QLJBSUNB2G"]HC-Wifi-light.zip[/URL]
Other Information
This method of installation will set your main version to 1.36.100.0 on 3G flyers and 1.36.0001.01 for Wifi models. The reason for this is to make that number lower than any RUU that exists for your device. This simplifies future downgrades by making it unnecessary to ever run the misc_version downgrade procedure.
FAQ
Q: Do I need to flash recovery/root something else after this?
A: No, the procedure will give you root, recovery and busybox.
Q: What does S-OFF give me that HTC unlock doesn't?
A: Full read/write access to all useful partitions.
Q: What else does S-OFF give me that HTC unlock doesn't?
A: The ability to flash custom roms without flashing boot images from booted android.
Q: What else does S-OFF give me that HTC unlock doesn't?
A: The ability to have custom software without having to waive your warranty.
Q: What else does S-OFF give me that HTC unlock doesn't?
A: The ability to install any regional ROMS without a goldcard.
Q: What else does S-OFF give me that HTC unlock doesn't?
A: Greedy much? What else do you want?
Q: Can I return to S-ON for warranty purposes?
A: Yes, a procedure will be in post 3 when I get to it, if you ask in the thread I will not answer this question.
Q: Why do I have to S-OFF in GB before going to HC?
A: Because that's where the exploit works, once we have access to hboot in any version we can patch hboots for later releases.
Q: Can I downgrade to GB by restoring my backup?
A: No
Q: Can I downgrade to GB?
A: Yes, follow the post below this one.
Q: Will this work on the view?
A: No
S-OFF Downgrade
Instructions Part 1
This thread is not for discussing general Honeycomb problems so don't post here if it's not related to running this procedure.
To go completely back to stock and S-ON, follow the instructions here. The instructions in the link will work for either Gingerbread or HoneyComb, make sure you use an RUU for your CID.
Important: Charge your Flyer fully before running this procedure ( see section: problems below)
If you are on Honeycomb and got there by following other honeycomb install methods this procedure is not for you.
You must have a revolutionary hboot to use this procedure.
You must download the gingerbread RUU for your device unless you are going to immediately install a custom ROM or restore a nandroid backup.
Note: There is no FULL version downgrade due to the number of localized versions that exist for the Flyer.
You must download the gingerbread RUU for your device unless you are going to immediately install a custom ROM.
After following the steps above, you should be on a gingerbread compatible base with revolutionary S-OFF and CWM, nothing more or less than that.
Procedure
download the file that you require as follows:
Be warned this is a this is not a complet rom, if you try to boot from it you will just get the wite htc logo screen:
Code:
MD5 Filename
--------------------------------------------------------------
3G-Wifi: 26ea9aa7cdde5c0008446c421c1ac1cc [URL="http://hyuh.net/files/flyer/downgrade/PG41IMG-3G.zip"]PG41IMG-3G.zip[/URL]
Wifi only: e0094cbb3ce14630e1d7e7dcc4274dd8 [URL="http://hyuh.net/files/flyer/downgrade/PG41IMG-WIFI.zip"]PG41IMG-WIFI.zip[/URL]
If you are running this procedure the flash WILL fail first time, you must flash twice
Method1: Using fastboot:
Get fastboot and adb tool for windows here, get Windows fastboot drivers here
Get Fastboot and adb for linux here
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <name of zipfile>
[I][COLOR=Blue]Flashing will fail with Error 90 first time due to hboot change[/COLOR][/I]
fastboot flash zip <name of zipfile>
[I][COLOR=Blue]The on screen indicator on the phone will not reach fully to the right end of the progress bar, this is ok[/COLOR][/I]
fastboot reboot
Method 2: Using bootloader - NOTE I strongly recommend using method 1.
Rename the downloaded file PG41IMG.zip
Transfer the file to the root of your SD card
Reboot to hboot, which will detect and install the update.
Note it will require two passes to complete the upgrade due to hboot change
Credits
scotty1223 for giving me the kick in the ass to get this done Thanks scotty!
hi globatron,
first of all thanks for the hard work..
second, this is the first time i'm gonna root or apply a custom rom on my flyer so would you say this tutorial would be enough for me to do the whole process? or should i look at some other information before applying this?
thanks
Safe to assume this version of hboot will be compatiblewith all hc leaks?
Having s off will allow us to upgrade easier?
Thank you for all your efforts
Sent from my HTC Flyer P510e using xda premium
sarpsuerdas try it, if you get stuck ask questions. If I'm not online most people here have already done things very similar to this and will try to help.
mcord11758, all the ones so far but you never know about future ones, what it will mean for sure is no downgrade to GB if an incompatible hboot comes along, and I'll update then if needed.
awsome! thanks for your hard work. cant wait to get my flyer back so i can install it
is this hboot protecting itself from being overwritten?
I'm assuming no go to the View, correct? Even if you have no use for the 4g modem? =)
Do you suggest running actual ruu or fastboot flash to revert to gb
Sent from my HTC Flyer P510e using xda premium
just to be clear
Im on rooted LeeDroid rom Ginger S Off. I should revert to S on and then move forward?
kturnbull said:
I'm assuming no go to the View, correct? Even if you have no use for the 4g modem? =)
Click to expand...
Click to collapse
Correct (for now)
mcord11758 said:
Do you suggest running actual ruu or fastboot flash to revert to gb
Click to expand...
Click to collapse
Makes no difference really. I always use fastboot because it gives me better feedback but whatever is easiest.
kevinniven said:
Im on rooted LeeDroid rom Ginger S Off. I should revert to S on and then move forward?
Click to expand...
Click to collapse
No, skip to Part 2.
sorry for the novice questions but I got only one question in mind that will decide whether I will install this or not..
after completing the process, will my Flyer be able to use the honeycomb market, download the hc compatible apps and use the stylus as it should be with sketchbook etc?
globatron said:
Correct (for now)
Click to expand...
Click to collapse
You'd make all 4 of us REALLY happy. =)
Yeah!
It worked! It was so extremely easy! I used Method 1 and presto! Here I am! Thanks Globatron! Looks like I will be ising English from the UK, though....Hmmmm....it will be fun reading realize as realise. Lol.
You are AMAZING!
All the hc leaks do not have united states english
Sent from my HTC Flyer P510e using xda premium
Please excuse my ignorance but I am not quite sure what I will gain by doing this. I am currently running FlyHoney V1 on my WiFi BB Flyer and everything is running fine. I appreciate all of the hard work and effort but I just want to better understand this.
tsg2513 said:
Please excuse my ignorance but I am not quite sure what I will gain by doing this. I am currently running FlyHoney V1 on my WiFi BB Flyer and everything is running fine. I appreciate all of the hard work and effort but I just want to better understand this.
Click to expand...
Click to collapse
You get an S-OFF HBOOT with HC, previously you only had an unlocked bootloader via HTC Unlock and S-ON.
I was able to do this successfully with Method 1 (fastboot commands too).
Thank you globatron for your hard work!
Can someone please help me?
I am stuck at the revolutionary stage, unfortunately.. I have a 32 Flyer 3G and the revolutionary just tells me to drink the lemonade again and again.. The firmware is still the stock Flyer ROM with the updates done.. haven't performed any extra modification on it yet..
The details are:
Android 2.3.4
1.0 for Tablet
Software No: 2.23.405.4
I have applied the revolutionary process stage by stage just as it says.. but it can't pass the fastboot stage..
Is the process for downgrading to gingerbread still the same, or can I just restore a gingerbread backup if I want?
Sent from my HTC_Flyer_P512_NA
This Quick And Dirty Evo 3D/V Root & S-OFF (QADERSO) guide is for current Sprint and Virgin Mobile (VM) S-ON users, rooted or not, who want to get to a rooted S-OFF configuration of the Sprint or VM ICS stock ROM. There are many other ROM and bootloader options that can be pursued from there.
I know that there are similar guides available already, but this one is going to be simple with no choices. If you want another recovery or aren't on Sprint or VM go check out one of the other ones, because this is the "Model T" of guides and will get you exactly the following configuration, which I believe is the best base for the Sprint Evo 3D or Virgin Mobile Evo V at this time:
1. Rooted Sprint ICS build 2.89.651.2 or VM ICS build 1.13.652.2
2. 4EXT Recovery with Updater or Control App
3. JuopunutBear S-OFF with JBear Sprint ICS (1.58.5858) bootloader or JBear VM ICS (1.57.5757) bootloader
If you want to modify this configuration and know how, feel free, but I'm only documenting how to get from your current configuration, whatever that is, to the one above. I am providing tips and references if you get stuck, but please don't ask about other configurations, recoveries, etc., in this thread.
Should you decide to modify the procedure, please explain that in any post made in this thread for assistance. That's your choice, but it would help me and any one else trying to provide support in this and other threads to have that information.
There are tips and references for each step at the end of this post in case you get stuck, but if you read all the instructions and follow this procedure carefully, hopefully you won't need them.
Prerequisites:
1. Sprint Evo 3D or Virgin Mobile Evo V phone that is S-ON, on any ROM, rooted or not.
2. Windows PC or notebook to run the utilities and access the websites.
3. MicroUSB to USB cable to connect the phone to the computer.
4. Shielded wire for the JuopunutBear wire trick.
5. Something to drink while the RUU.exe runs for about 10 minutes.
Before you start, download the QADERSO-V2-S.zip (mirror) file (for Sprint users) or QADERSO-V2-VM.zip (mirror) file (for Virgin Mobile users) and unzip it to somewhere on a Windows PC. It includes all the software you need to complete this procedure.
If you would like a Microsoft Word version of this guide and detailed instructions for the JuopunutBear wire trick, you can download it from here. Thanks to mpgrimm2 for putting that together.
Flashing the RUU.exe in Step1 will reset all the partitions on your phone except those on the SD card so I'd also recommend backing up anything you want to keep to the SD card before starting. If you don't have root yet, MyBackup is a good alternative to Titanium Backup and other utilities that require root.
***Step1: Install ICS RUU
If you are using this guide with a new/replacement unrooted phone you can go to Step2 since flashing the RUU returns the phone to the same stock configuration. VM users should apply the OTA update from the "System updates" options in system settings before starting Step2 if it hasn't already been done since that requires a stock configuration.
VM users: If the November VM OTA update (1.14.652.0) was installed and the phone is rooted with a custom recovery and ROM, please see this post for instructions on how to prepare the phone to run the RUU.exe. If both the November and March OTA (2.95.652.5) were installed there is no way to flash the RUU so proceed to Step2, or if already rooted flash a stock rooted ROM from this post then go directly to Step3.
Sprint users: If the March OTA ((2.95.651.5) is installed and the phone is unrooted proceed directly to Step2. If the March OTA is installed and it's rooted see this post for instructions on how to prepare for flashing the RUU.
Click to expand...
Click to collapse
Start by installing the Sprint 2.89.651.2 RUU.exe or Virgin Mobile 1.13.652.2 RUU.exe from Windows. It doesn't take much longer than flashing a stock ROM and includes all the firmware so the phone will be totally in sync with the official ICS build. Flashing the RUU can also resolve problems with the HTC unlock process if the OTA was used to update to the official Sprint ICS version or a custom recovery and ROM have already been flashed.
If you are already HTC unlocked, relock the bootloader using the "fastboot oem lock" command. You should know how to run fastboot commands from a PC if you have already unlocked.
If you have never HTC unlocked or have relocked successfully, connect the phone to the PC via a USB cable in "fastboot USB" mode then run the RUU.exe from the /QADERSO/RUU directory in Windows. The program has a GUI interface and is pretty much self-explanatory, but there is a readme.doc in the same directory that covers the process and possible errors.
VM users: Now would be a good time to download and install the OTA updates since they will flash updated firmware and patches to the stock software, and cannot be installed once a custom recovery is flashed in Step2. Just go to Settings/System updates/HTC Software, press check now, then download each of the two OTA updates (November and March) and follow the instructions to install them. The software patches will be overridden once a custom ROM is flashed, but the firmware updates will remain and should improve radio reception.
Sprint users: Installing the March OTA at this point will avoid having to flash the firmware only zip file for that update after getting S-OFF. To do that go to Settings/System updates/HTC Software, press check now, then download the update and follow the instructions to install it.
Click to expand...
Click to collapse
***End of Step1
***Step2: HTC Unlock, flash 4EXT recovery and superuser
Navigate to the /QADERSO/Root directory and open a command prompt by clicking on the "cmd" file in that directory. If you have HTC Sync installed go to the Windows control panel and uninstall just the sync program but leave the drivers installed. This is required by the JuopunutBear utility in Step3. If you don't have the HTC Sync program or drivers installed and are not using Windows 8, double click the HTCDriver3.0.0.007.exe file in the /QADERSO/Root directory to install only the HTC USB drivers. If you are using Windows 8 and don't have the HTC USB drivers already installed a compatible .exe setup can be downloaded here.
If you have never done the HTC unlock procedure, go to htcdev.com and signup then follow the instructions to get your bootloader unlocked. The programs you need to do the HTC unlock procedure are already in the /QADERSO/Root directory, so you can skip step 5 on the htcdev website.
If you have already HTC unlocked, you know the routine and need to do it again after flashing the RUU. You can use the same unlock_code.bin from your previous unlock.
Put the phone in "fastboot USB" mode by removing/replacing the battery, holding Power+VolumeDown buttons until the bootloader starts up, highlighting the "fastboot" entry by using the VolumeUp/VolumeDown buttons to navigate, selecting it with the Power button, then connecting it to your computer. The "fastboot" status should change to "fastboot USB".
When the phone is in "fastboot USB" mode, enter the following commands from the prompt:
"fastboot devices" (should show the serial number of your phone, beginning with "HT")
"fastboot flash recovery recovery.img"
"fastboot boot recovery.img"
After the phone reboots into 4EXT recovery, select the "toggle usb storage" menu item from 4EXT recovery and copy the SuperSU-v0.96.zip file from the /QADERSO/Root directory on the PC to the root of the SD card on the phone. Eject the SD card from the PC and go back to the main menu of 4EXT.
Flash SuperSU-v0.97.zip from 4EXT recovery using the "Install from sdcard" menu item and selecting it from the root of the SD card. Go back to the main 4EXT menu and select "reboot now" from 4EXT and perform the initial setup of the stock ICS ROM after the boot completes.
Your phone now has the 4EXT custom recovery and a rooted stock ICS ROM with SuperSU.
Once the procedure is complete and you've booted into your rooted, stock configuration, you need to install either 4EXT Recovery Updater from the 4EXT website, or better yet purchase and install 4EXT Recovery Control from the Play Store. Then use the update function in the app you chose to get the current version of 4EXT.
You should start the SuperSU app to make sure it is working properly and updated to the current version. BusyBox also needs to be installed from the Play Store for 4EXT and other root apps and I recommend the installer by Stericson.
***End of Step2
***Step3: Perform JuopunutBear (wire trick) to get S-OFF status
Important Note:
The unlimited.io team has withdrawn support for all Windows versions of the JBear utility (controlbear.exe). Do not go to their IRC channel for support while following this guide as they will not be willing to help anyone using Windows instead of Linux for the wire trick. If you are unable to get S-OFF using this guide you will need to flash the RUU again and go to the the unlimited.io website to download a Linux version and follow their procedures.
Since the JuopunutBear wire trick now requires Ubuntu Linux to use the supported procedure Evo 3D users might also want to consider unknownforce's Ultimate Recovery Tool 3.0 which has recently been updated and streamlined. Unfortunately it won't work for Evo V 4G users since there is no Virgin Mobile GB RUU that can be used as part of that S-OFF process.
Click to expand...
Click to collapse
The wire trick is not difficult, but it can be a little confusing. It would be worth spending a little time reviewing the tips and references for Step3 at this point so the process goes smoothly.
Connect the phone to your PC with your stock rooted ROM booted and the USB debug option on in the developer settings.
Navigate to the /QADERSO/JBear directory, right click on controlbear.exe and "run as administrator", and then follow the prompts on the PC and the phone screen. Make sure to have an insulated wire ready for the wire trick, and select the JBear version of the bootloader when that prompt comes up. Yes, it's really that easy to get S-OFF.
If you flash a stock bootloader later it will show ***LOCKED*** as the status, but that's usually not a problem if the phone is S-OFF. It's actually good since that means there is no indication that the phone was ever unlocked, unlike the ***RELOCKED*** status after doing the HTC unlock/relock. By selecting the JBear version of the bootloader, the same fastboot commands will be available from a PC as with an unlocked bootloader.
You may have to activate your phone again after performing the wire trick. That is normal and should be done automatically from the phone on your first boot if it is required.
***End of Step3
WARNING: When you are S-OFF, PG86IMG.zip files can be flashed from the bootloader without being signed, which means you can flash any bootloader or firmware you want. But be careful and always make sure the stuff you are flashing is designed for your phone, or you may have serious problems if you force something to flash that was designed for another carrier or phone.
If you need to change the bootloader (hboot) version to run GB or AOSP ROM's you can find them in post #7 of mpgrimm2's thread on bootloader differences. There are instructions in this post for how to flash another bootloader with this configuration in place if you used this guide.
The following informational posts have been added to this thread:
1. Troubleshooting RUU.exe problems
2. Security questions about rooting and S-OFF
3. S-ON versus S-OFF
4. Information for users already S-OFF
5. How to change bootloader (hboot) when S-OFF
6. Temp root for current GB users
7. Recovery Comparison: TWRP2 versus 4EXT
8. Returning to stock configuration
9. Information on the Aroma installer
10. Updating 4EXT Recovery
11. QADERSO Version 2 with Virgin Mobile added
12. OTA Updates for Virgin Mobile users
13. OTA Update for Sprint users
14. Information for Linux users
15. JuopunutBear update
Please post any suggestions for making this process simpler and easier in this thread, but I intend to keep this guide as barebones as possible.
Tips and References for Step1: Flashing the RUU.exe
Tips
1. Make sure to put the phone into "fastboot USB" mode in the bootloader by removing/replacing the battery and using VolumeDown+Power to boot into the bootloader. The RUU is also supposed to work if you connect the phone to the PC while booted into Android, but I've found fastboot USB to be more reliable.
2. If you get a 17x error it has something to do with the USB connectivity. Make sure your phone is properly connected to the PC and in "fastboot USB" mode and try again.
3. If the RUU.exe stops in the middle of flashing the update, it's OK to cancel the Windows utility and restart it. This has happended to me a few times when I've had custom bootloaders installed.
References
1. HTC Readme.doc for flashing an RUU.exe is in the /QADERSO/RUU directory.
2. Download for HTC driver installer compatible with Windows 8.
3. The mpgrimm2 guide for flashing RUU's.
Tips and References for Step2: HTC Unlock, Flashing 4EXT Recovery and Superuser
Tips
1. On current Windows systems you can open a command prompt in a specific directory by using Windows Explorer to navigate to that directory and pressing Shift+MouseRightClick on blank area, then selecting "Open a command prompt here".
2. Make sure the phone is in "fastboot USB" mode and the bootloader has been HTC unlocked after flashing the RUU.exe or the fastboot commands will fail.
3. If you need to manually boot into recovery it can be done from the bootloader.
References
1. The HTC unlock overview diagram is in the /QADERSO/Root directory
2. The mpgrimm2 guide for flashing recovery and superuser.
3. The HTC Developer website.
4. The 4EXT Recovery website and HTCEvoHacks installation instructions for 4EXT Recovery Updater with video.
5. Instructions for installing 4EXT apps.
6. The SuperSU XDA thread.
Tips and References for Step3: JuopunutBear (wire trick) S-OFF Method
Tips
1. Watch this zedomax video and this timing video before attempting the wire trick and it will be a lot easier.
2. Make sure to backup your SD card to a PC before using it for the wire trick.
3. Remove the back cover to prepare for the wire trick but make sure to watch the phone's screen for superuser requests that need to be approved.
4. Do not touch the uninsulated part of the wire with your fingers while performing the wire trick.
5. Only short taps are required for the wire trick.
6. If unsuccessful with the wire trick try a smaller capacity SD card.
7. If the SD card used for the wire trick gets corrupted it can be reformatted and restored from the backup on the PC.
References
1. JuopunutBear overview, basic instructions and prerequisites.
2. JuopunutBear instructions and downloads for the Evo 3D.
3. Troubleshooting and Support pages on the unlimited.io website.
4. JuopunutBear thread on XDA.
Thanks for the tutorial, I'll let you know if I run into any issues. This will be the first time I root my Evo3D.
Kiotofl said:
Thanks for the tutorial, I'll let you know if I run into any issues. This will be the first time I root my Evo3D.
Click to expand...
Click to collapse
OK, thanks and good luck!
I've updated the download file and the instructions to include the HTC USB drivers for those that don't have them installed already so everything should be in that file to get you to rooted and S-OFF.
ramjet73
Thanks for this!
you sir, are a god among men. I will try this tonight and post the results.
Thanks!
rino655 said:
you sir, are a god among men. I will try this tonight and post the results.
Thanks!
Click to expand...
Click to collapse
Just wanted to say big thank you for posting this guide!
I managed to get Hboot 1.58 S-off. I had 1 failure with JuopunutBear (wire trick) but after 2nd try I was able to succeed.
One advice I can give is to uninstall all drivers and HTC sync and install HTCDriver3.0.0.007.exe from QADERSO\Root folder.
Everything else went smooth.
I've installed MeanROM ICS v2.6 | Sprint 2.89.651.2 but WiFi tether still does not work it seems like its matter of finding correct profile.
JohnnyBeGood113 said:
Just wanted to say big thank you for posting this guide!
I managed to get Hboot 1.58 S-off. I had 1 failure with JuopunutBear (wire trick) but after 2nd try I was able to succeed.
One advice I can give is to uninstall all drivers and HTC sync and install HTCDriver3.0.0.007.exe from QADERSO\Root folder.
Everything else went smooth.
I've installed MeanROM ICS v2.6 | Sprint 2.89.651.2 but WiFi tether still does not work it seems like its matter of finding correct profile.
Click to expand...
Click to collapse
Thanks!
Are you using the WiFi Tether app that came with MeanROM ICS? What usually works with MeanROM ICS is the generic ICS profile with the routing fix checked. I believe the OP for MeanROM ICS says to check MSS clamping as well, but some of the newer versions of WiFi Tether don't have that option, and I've never needed it.
ramjet73
ramjet73 said:
Thanks!
Are you using the WiFi Tether app that came with MeanROM ICS? What usually works with MeanROM ICS is the generic ICS profile with the routing fix checked. I believe the OP for MeanROM ICS says to check MSS clamping as well, but some of the newer versions of WiFi Tether don't have that option, and I've never needed it.
ramjet73
Click to expand...
Click to collapse
I was trying to get WiFi Tether to work and it would not start correctly it would give "starting softap" and "WiFi interface" error is "Show Log".
I even uninstalled one that came with ROM and installed latest wifi_tether_v3_2-beta2.apk from their site and still would not work.
What worked for me is selecting Menu > Change Device-Profile and selecting Generic ICS/JB (wlan0) and of course selecting "MMS clamping" + "Routing fix"
I was just selecting "Generic" and it would not work.
Hope it helps out someone.
Nice guide Ramjet73. The way u put it together should get everyone around all the common errors.
I will definitely get this linked to my other threads as soon as I can.
Sent from my "Up all night, Sleep all day" EVO3D!
Thanks ramjet73.
This is quite thorough. Very nice.
I'm almost wondering if I might be able to automate some of this somehow. Don't hold me to it though. I don't have a whole lot of time, but if I can, I'll see if I can maybe do that.
I guess then, that I'll "hold" the tenth spot just in case.
Thanks,
~co~
Edit: What in the world am I doing? Sorry ramjet73. Still if I come up with something, I'll message you.
closeone said:
Thanks ramjet73.
This is quite thorough. Very nice.
I'm almost wondering if I might be able to automate some of this somehow. Don't hold me to it though. I don't have a whole lot of time, but if I can, I'll see if I can maybe do that.
I guess then, that I'll "hold" the tenth spot just in case.
Thanks,
~co~
Click to expand...
Click to collapse
That would be great!
It would be nice to have it as automated as possible.
ramjet73
ramjet73 said:
That would be great!
It would be nice to have it as automated as possible.
ramjet73
Click to expand...
Click to collapse
Beat me to my edit. I'll see if I can do something. but, no guarantees.
~co~
Edit: I reedited my edit and put back what was originally there, resulting in this post being edited from its original unedited state as well. <- Meta
This is exactly what I was looking for
I am also looking to do my first root. I am still reading other posts. But, my main questions are around restoring the phone back to stock. I have Best Buy protection and if things go bad, I plan to use them and I am trying to figure out what steps I need to take to ensure I can potentially return back to the stock state before going down this path.
Overall, this is probably the simplest guide I have seen so far. Thanks again.. if you have any pointers for me around EVO 3D on Sprint, please let me know.
Thanks.
rosahas said:
I am also looking to do my first root. I am still reading other posts. But, my main questions are around restoring the phone back to stock. I have Best Buy protection and if things go bad, I plan to use them and I am trying to figure out what steps I need to take to ensure I can potentially return back to the stock state before going down this path.
Overall, this is probably the simplest guide I have seen so far. Thanks again.. if you have any pointers for me around EVO 3D on Sprint, please let me know.
Thanks.
Click to expand...
Click to collapse
If you choose the JuopunutBear bootloader as recommended and leave the bootloader status as ***LOCKED*** going back to complete stock is as easy as running the same 2.89.651.2 RUU.exe again, then issuing the "fastboot oem writesecureflag 3" to set it back to radio S-ON. Verify that you have successfully flashed the stock 1.58 bootloader before issuing that command or you could brick the phone.
ramjet73
ramjet73 said:
If you choose the JuopunutBear bootloader as recommended and leave the bootloader status as ***LOCKED*** going back to complete stock is as easy as running the same 2.89.651.2 RUU.exe again, then issuing the "fastboot oem writesecureflag 3" to set it back to radio S-ON. Verify that you have successfully flashed the stock 1.58 bootloader before issuing that command or you could brick the phone.
ramjet73
Click to expand...
Click to collapse
Question... If you have hboot 1.4, and run flash the latest update that has the new hboot, you ARE S-OFF, but it says LOCKED... Correct? Also, if you were to write the secure flag thing to S-ON, and you have the latest hboot, you are TRULY S-ON like you just bought your phone or never had S-OFF and updated, correct? Or is my hypothesis wrong?
wwjoshdew said:
Question... If you have hboot 1.4, and run flash the latest update that has the new hboot, you ARE S-OFF, but it says LOCKED... Correct? Also, if you were to write the secure flag thing to S-ON, and you have the latest hboot, you are TRULY S-ON like you just bought your phone or never had S-OFF and updated, correct? Or is my hypothesis wrong?
Click to expand...
Click to collapse
Yes, that's pretty much true, assuming you never HTC unlocked the phone or the S-OFF method you used returned the bootloader to the ***LOCKED*** status. I know the JBear method does just that, but I've never done the 1.4 downgrade. At one point mpgrimm2 said his bootloader showed ***UNLOCKED*** and I know he did the downgrade to hboot 1.4 to get S-OFF, so I'm not sure that method resets the bootloader S-OFF status.
In the worst case, if your bootloader is currently ***UNLOCKED*** and your radio is S-OFF, you could flash the RUU then set S-ON, root and do the wire trick to get the bootloader status back to ***LOCKED*** but that's a lot of work. OTOH, if you don't do that you can only set the bootloader status to ***RELOCKED*** with the "fastboot oem lock" command and that leaves a flag to HTC/Sprint that your phone was rooted. That's why I always recommend using a custom bootloader instead of HTC unlocking the stock bootloader if you are radio S-OFF and want to run more of the fastboot commands.
The custom bootloaders will usually mask the bootloader locked/unlocked status with a name like "Revolutionary" or "JuopunutBear" so the only way to verify what you currently have for your bootloader status is to flash a stock bootloader.
ramjet73
I had to reread the middle paragraph 3 times to understand it, but that's my understanding too. My hboot does say unlocked/relocked (RL) on it because I did the HTC Unlock at one point, without the Jbear for s-Off.
Sent from my "Up all night, Sleep all day" EVO3D!
ramjet73 said:
When the phone is in "fastboot USB" mode, enter the following commands from the prompt:
"fastboot devices" (should show the serial number of your phone, beginning with "HT")
"fastboot flash recovery recovery.img"
"fastboot boot recovery.img"
Click to expand...
Click to collapse
I try to enter "fastboot devices" in the Quaderso\root directory, and it tells me
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
What is the problem? I spent 2 hours on something that I will have problems with. Great.
Found out I had to move the files back to the Root Directory. Thanks for an awesome guide!
RevolcFael4 said:
I try to enter "fastboot devices" in the Quaderso\root directory, and it tells me
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
What is the problem? I spent 2 hours on something that I will have problems with. Great.
Click to expand...
Click to collapse
Sounds like you are not in the the \quaderso\root directory when the "fastboot devices" command is being issued from the prompt. See tip #1 for Step2 to open a command prompt in the \qaderso\root directory.
You can also Start/Run "cmd" then use the "cd" command to navigate to the \qaderso\root directory. Either way you should issue a "dir" command from prompt to make sure the contents of the directory are as follows:
C:\tmp\QADERSO\Root>dir
Volume in drive C is OS
Volume Serial Number is 6CF6-A9B2
Directory of C:\tmp\QADERSO\Root
09/16/2012 03:07 AM <DIR> .
09/16/2012 03:07 AM <DIR> ..
09/05/2012 05:52 PM 7,047,406 4EXT_Recovery_Touch_v1.0.0.5_RC6.zip
05/07/2010 12:48 PM 578,611 adb.exe
05/07/2010 12:48 PM 96,256 AdbWinApi.dll
07/16/2011 01:05 PM 183,651 fastboot.exe
07/30/2011 10:31 AM 13,783,568 HTCDriver3.0.0.007.exe
08/14/2012 05:09 PM 7,077,888 recovery.img
09/15/2012 05:53 PM 684,154 SuperSU-v0.96.zip
09/15/2012 06:48 PM 169,793 Unlock_Bootloader_Workflow.pdf
8 File(s) 29,621,327 bytes
2 Dir(s) 291,896,774,656 bytes free
ramjet73
mpgrimm2 said:
I had to reread the middle paragraph 3 times to understand it, but that's my understanding too. My hboot does say unlocked/relocked (RL) on it because I did the HTC Unlock at one point, without the Jbear for s-Off.
Sent from my "Up all night, Sleep all day" EVO3D!
Click to expand...
Click to collapse
Yeah... I NEVER ONCE ran htc dev on my Evo 3D. The moment I bought it, I declined all updates and waited until THIS DAY happened, and S-OFF'd immediately. I knew better than to update, after knowing about all the trouble people had with the shift and the og evo. Updates are bad, mmmk?
Anyways, I S-OFF'd that night and never looked back... Still have 1.4, and don't feel like giving up my virginity to HTC.
YOU KNOW YOU WANT TO CLICK ME!
First, Thanks to everyone that helped me along the way here... The thanks list is in Post #2
Second, The risk obviously here is your own. This tool is provided AS IS, and I am not providing any warranty or guarantee. So it doesn't cover hail damage to your home, Tornado's taking your dog away, or your phone not working properly after using it... (or anything else that you might try to pin on me )
For all of the processes, linux is required... use your own flavor of linux and use the following to set it up:
Extract the files to somewhere (home folder works best)
Gain a root command prompt (# instead of $) (sudo -s works for most)
Set permissions via "chmod 755 ultimate" (possibly 0755 depending on linux flavor)
Then run the tool using ./ultimate
Code:
/=================================================================\
|*******************************************************************|
|****************** EVO 3D Ultimate Recovery Tool ******************|
|*************************** Version 3.1 ***************************|
|*******************************************************************|
| |
| Please Select an Option |
| |
| 1. Create a backup partition from a bricked device |
| 2. Flash a custom partition to a bricked device |
| 3. Downgrade HBOOT |
| 4. Unbrick |
| 5. VM Radio Fix (CDMA ONLY!) |
| 6. Fix radio partition (Manual Radio Fix only) (CDMA ONLY!) |
| 7. Exit |
| |
| |
|*******************************************************************|
|**************** Copyright (C) 2013, Unknownforce *****************|
|*******************************************************************|
\=================================================================/
Latest version is Here.
(3/14/13) - URTLiveCD 1.0 is available Here -> http://d-h.st/blY (This includes URT 3.0)
Recent Updates:
3.1
Added another check to the misc partition detection
3.0
Fixed and re-implemented VM Radio Fix
3.0 ALPHA
Completely Redesigned and Re-Written
New menu interface
Removed the need for hboot/misc image files to be present, they are now embedded in the program and used as necessary
CID issue fixed for GSM devices
Misc detection implemented
GSM/CDMA detection implemented
Removed Radio Fix for now, some bug I can't figure out yet... Meh
Fixed a few missing things from the VM Radio Fix (CDMA Only) (when 3.0 is Final)
Many minor bug fixes
2.5.1
Mistakenly used an older source of URT when coding 2.5, so I re-applied changes from 2.5 to the correct source and re-compiled. (No Difference for GSM, only radio fix was affected.)
2.5
Added support for GSM EVO 3D's! (add -g or --gsm)
No longer beta or RC or alpha or whatever!
Minor cleanup/optimization.
2.3 RC1
Fixed the ghost MEID issues. (This will not fix devices that got it from the first test, please contact me and I'll work with you to fix that)
Fixed some delays and timing in switching between fastboot and adb
Corrected some wording.
2.2 RC4
Second attempt at fixing output errors... Sorry :/
2.2 RC3
Attempt to fix "sh: 1: Syntax error: Bad fd number" error.
Add -f switch to attempt to fix I/O errors on possibly bad sectored emmc's (This will require being in a temp bricked state before using, if this successfully recovers them, I can add this into the process of the radio fix, for now I want to see if it's going to work at all, so it's a manual process for now, to brick device, Be S-OFF, flash custom hboot(anything but stock) and do fastboot oem writesecureflag 3, done) This is ONLY for those having I/O errors when trying to flash radio config. The usage is ./ultimate -f 19 (19 is partition 19/radio_config)
2.2 RC2
Fixed device detection at first step
Logging to log.txt
Fixed device "wait" after rebooting to system, it will now check properly that there is a device to reboot before issuing the command, rather than just rely on time.
2.2 RC1
Initial release to public
Radio Fix
Radio Fix is for CDMA ONLY!See the CDMA Thread -> here
Downgrade/Unbrick
DO NOT BRICK YOUR DEVICE IF YOU ARE S-OFF, THE DEVICE WILL NOT GO INTO EMMC MODE AS EXPECTED, AND YOU WILL HAVE A TRUE BRICK IN YOUR HANDS!!!
If you're already S-OFF, but on a higher version of hboot, you can just downgrade via a sdcard PG86IMG containing the lower hboot, being S-OFF will let it flash anything
For the S-ON Downgrade... Things you'll need...
Linux and basic linux knowledge (not necessary if you use the URTLiveCD)
The RUU ZIP image that MATCHES your current ROM version
You'll also need the 1.20 or 1.22 RUU EXE (All the RUU's can be found here -> http://www.filefactory.com/f/4ef0ef536face67a/)
Download the ultimate3.0.zip listed above or the URTLiveCD if you do not have linux
Backup your apps/data if you need to, this process will wipe EVERYTHING
(If you're already bricked, start from Step 2)
(3/12/13 - PENDING UPDATE
I have not personally tested it, but the idea is sound and if he's done it correctly it should work just fine, If you wish to try it, it is here (Yes, it still uses Linux, but on a bootable CD) -> http://forum.xda-developers.com/showthread.php?t=1563342
First Step
VIDEO OF STEP 1 (video says Step 2, but just start here)
VIDEO OF ENTIRE PROCESS (Done with the battery pull method and on a CDMA device)
BRICK (Yes, I said brick) your device. BUT in a CERTAIN way.
You need to brick your device by corrupting the HBOOT during the HBOOT Update.
(MAKE SURE YOU ARE TRULY S-ON, IF YOU BRICK YOUR DEVICE WHILE S-OFF, THIS IS PERMANENT and CANNOT BE RECOVERED FROM)
(MAKE SURE YOU ARE TRULY S-ON, IF YOU BRICK YOUR DEVICE WHILE S-OFF, THIS IS PERMANENT and CANNOT BE RECOVERED FROM)
(MAKE SURE YOU ARE TRULY S-ON, IF YOU BRICK YOUR DEVICE WHILE S-OFF, THIS IS PERMANENT and CANNOT BE RECOVERED FROM)
(If you are HTC Unlocked, you MUST RELOCK BEFORE starting)
1.) Take your PG86IMG ZIP image from your CURRENT ROM RUU, put it on the root of your SDCard, call it PG86IMG.zip
2.) With the phone on Battery power alone, Reboot to BootLoader, let it detect the zip and read and get to the point where it wants you to press Vol-Up to update. Do not press Update yet.
3.) Here you can do one of two things, the first being a little more easier than that second... (See Videos for examples)
3A.) The battery pull. You can interrupt the flash by pulling the battery at the right time. Tell the device to update, Pull off the battery cover (careful not to let the battery fall out) and then watch the screen and pull the battery out during or just before the orange bar shows up during the BOOTLOADER Updating.
3B.) The power pull. You can also do this by using the power cord to kill the power. Pull off the battery cover (again careful not to drop the battery out right away) then plug the device into AC power. Now pull the battery out. Tell it to update and pull the power cord at the right time.
The "right time" is different for all devices. The idea here is to completely interrupt the hboot flash so that it's corrupt. The best thing to do is to watch for the bar in the upper right hand corner, it will only show for a second (or even shorter)
If done correctly, you can plug in the device (to power or USB) and see the charge light very dim. It will need to be SOLID dim, NOT blinking dim.
The main indications that it worked correctly:
The device no longer turns on at all, no bootloader, no boot screen, nothing.
The SOLID, not blinking, dim light mentioned above.
The charge light no longer lights up when plugged in with a battery.
The device, when plugged into a windows PC, shows up as QHSUSB_DLOAD. (And MMC Storage Controller for the first 5 seconds)
The device is now bricked and ready for the next part.
Second Step
Video above shows this as well.
The next step is the linux part. Do not plug your phone in to the linux box until you are told to do so.
1.) Boot up to Linux (if you use URTLiveCD, skip to step 6)
2.) Extract your ultimate.zip file to the linux PC, Home folder is the best spot and is the easiest to work with.
3.) Open up Terminal, gain root, (su, or sudo -s)(give it your password)
4.) Run the command chmod 755 ultimate (if it's not in your home folder, add the full path to it)
5.) Type ./ultimate and press Enter.
6.) Select option for Downgrade HBOOT.
You will see the below output:
Code:
IMPORTANT: Do not plug in device until TOLD to do so.
Downgrade selected.
Ready to begin? (y/n):
Type y and press Enter.
Then you will see:
Code:
Plug in your device now.
Waiting for device...
[/CODE]
Now... plug the phone in and leave it plugged in, you should see something similar to the below:
Code:
Device Found!
Locating misc partition...
Misc found at partition 31.
Changing misc version...
Writing image file...
SUCCESS!
Flashing hboot and unbricking...
Writing image file...
SUCCESS!
All tasks Completed Successfully! Put your battery back in and boot up!
Press Enter to return to the main menu.
From there, pull your SD Card out (so it doesn't try to update from the PG86IMG.zip...) throw your battery back in, boot up to bootloader. 1.49.0007
(Some people have said that they needed to "let the device sit" for a few minutes here, mine works immediately every time, YMMV)
To get back to a bootable rom and revolutionary, select FASTBOOT, connect it to the PC and run the 1.20 or 1.22 RUU EXE all the way through, (NOT the zip) then just revolutionary (a few times) and have a beer.
A few side notes:
When you run Revolutionary, you might have to do it a few times... I also didn't get to the point where it asked to flash a recovery... so I did this via fastboot, and simply used TWRP 2.0 .img file.
DISCLAIMER This is NOT a guarantee... because I'm sure it could come back... But in basic terms... I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE, I have given you a method that worked for me, and SHOULD work for you, but if your house burns down, your car gets a flat tire, or your phone stops working... You are responsible for any and all of those things.
The Thanks List!
MOVZX
RussianBear
Fuses
Dexter93
TrevE
Crackanug
closeone
USSENTERNCC1701E
jcase
agrabren
chad.goodman
wwjoshdew
The Fer-Shiz-Nizzle
jlechner
The entire Revolutionary team
And pedja1 for getting me the info I needed to get the GSM port done!
FAQ's
Can I do this on Windows?
Currently there is no way to do this on Windows. It's unlikely that there will be a way to do it on windows, Windows USB is too slow and doesn't detect the device the same as Linux does.
Can I do this in (Insert virtual PC software)?
The only one I've heard that works is VMWare, however You're again relying on Windows to pass the device to a virtual machine, which isn't ideal. I know for a fact that VirtualBox does not work, and Cygwin also does not work.
Common Errors
I can't get my phone to brick, I've tried a million times!
Patience is a virtue. This step is the hardest part of all, HTC Designed their phone to be brick proof for a reason. I believe the trick here is to let the device sit on the update screen for a minute or two, then do the update and count out 5 seconds. Also there's the update bar that appears in the upper right hand corner, much like the bar that is there when it's checking the zip file before the update prompt. The INSTANT you see that, pull the power. This is typically 5-6 seconds after it says updating, but only after it's been sitting for a bit... I believe the trick is to let it sit for a bit before pressing Volume up to update.
My PG86IMG.zip is not detected or the phone checks it and it doesn't prompt me to update it
There are several possibilities:
The phone is HTC Unlocked - You must re-lock.
The phone is S-OFF - Don't even try to brick it because you'll permanently brick it.
The phone is Re-locked, but still has a custom rom/recovery on it. - This will show a security warning and not allow the PG86IMG.zip to be flashed. - You must put the phone in FASTBOOT USB and run the RUU exe that matches your software version.
The File is not named correctly, it's PG86IMG.zip (Make sure it's not PG86IMG.zip.zip)
The PG86IMG.zip is either corrupt, not signed properly, or modified in some way. - Download another one.
I press Volume up to Update, and my phone shuts off
First make sure you're using a standard HTC A/C Adapter and cable. These are designed to charge at 1000 mA, other manufacturer's chargers typically only hit 900 mA. The phone needs it all to stay on and update properly without the battery in.
Second, make sure you're not using a higher end SD Card. This will draw too much power and not let the phone update when it comes to that time because the power drain to have the screen on, the sd card powered and the update running is more than what the A/C adapter can output. - My 16GB Class 10, shuts the phone off, my Class 4, 2 GB, does not. YMMV.
Third, if you're stuck with the high end SD card, or think it could be the cause, simply pull it after you pull the battery and BEFORE you press volume Up to update. The phone will still update. However, I don't know if this affects the speed of the update at all... so just watch it the first time and time it, then time your pull accordingly.
I'm getting Permission Denied when trying to run the linux commands
You don't have root, either type su or sudo -s, your prompt should have a # at the end and not a $.
Or, you didn't set the chmod correctly on the ultimate file. This is again chmod 755 ultimate (or /path/to/ultimate)
I get Misc image is missing!!! or HBOOT image is missing!!! or Recovery image is missing!!!
The hboot.img and misc.img and recovery.img files must be in the same location as the ultimate file, they are hard coded into the ultimate tool to be in the same location, their names are also hard coded, so don't rename them.
I'm getting Error 16 after running the radio fix.
This can happen, there are two things, most likely it goes away after attempting to place a few calls. If it doesn't, just remain on the line, and they can fix the problem for you.
wohohoho...great work
I hope the GSM users appreciate the significance of this thread. By working together on porting this tool for the GSM model, unknownforce and pedja1 have made it possible for those of you who have gotten motherboard replacements and can't use the htcdev unlock to get S-OFF and root your phones without the need for that.
Essentially, this is an alternative to the JuopunutBear wire trick that does not require an unlocked bootloader as a prerequisite.
ramjet73
ramjet73 said:
I hope the GSM users appreciate the significance of this thread. By working together on porting this tool for the GSM model, unknownforce and pedja1 have made it possible for those of you who have gotten motherboard replacements and can't use the htcdev unlock to get S-OFF and root your phones without the need for that.
Essentially, this is an alternative to the JuopunutBear wire trick that does not require an unlocked bootloader as a prerequisite.
ramjet73
Click to expand...
Click to collapse
Oh yes, thanks to pedja1. Definitely a perfect test subject.
I'm also going to look into another method of temp-bricking the device, that doesn't require special timing or anything, more of a one-click smash and flash. But that will have to wait until I get my old EVO 3D back in a few days hopefully, when I can start testing on it.
It will be nice to be able to test without it being tied to my own number, Having a second phone is so helpful.
Here's a little preview of 3.0
Unknownforce said:
To get back to a bootable rom and revolutionary, select FASTBOOT, connect it to the PC and run the 1.20 or 1.22 RUU EXE all the way through, (NOT the zip) then just revolutionary (a few times) and have a beer.
Click to expand...
Click to collapse
If you make only RUU to 1.20, then phone start normaly, but with ICS, no IMEI and random reboot. Must do flash 1.20 like PG86IMG. Then all OK. I had this.
---------- Post added at 04:06 AM ---------- Previous post was at 04:02 AM ----------
Unknownforce said:
Here's a little preview of 3.0
Click to expand...
Click to collapse
Windows version?
zemaniel said:
If you make only RUU to 1.20, then phone start normaly, but with ICS, no IMEI and random reboot. Must do flash 1.20 like PG86IMG. Then all OK. I had this.
Click to expand...
Click to collapse
Oh, yes the first time you RUU might not fully flash everything the first time, you might have to do it a couple times.
zemaniel said:
Windows version?
Click to expand...
Click to collapse
Not possible, unfortunately.
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade HBOOT)
A small observation.
Originally ( on ICS before downgrade) my misc partition was 32
After I downgraded to gingerbread with ruu, last partition is 31.
ICS = 32
GB = 31
Whichever last(official ruu or pg86img) you flashed tells you your misc partition
Sent from my HTC EVO 3D X515m using Tapatalk 2
I very want to unlock my phone, but my motherboard has replace.
So I can't unlock by HTCDev.com...
Does any GSM users can use this tool downgrade 1.53.0007 to 1.49.0007?
thanks for your hard work, this is a massive point for evo's modding :highfive:
ray650128 said:
I very want to unlock my phone, but my motherboard has replace.
So I can't unlock by HTCDev.com...
Does any GSM users can use this tool downgrade 1.53.0007 to 1.49.0007?
Click to expand...
Click to collapse
Yes, this will work for just about any version of hboot, you just need the RUU zip image from your ROM you currently are on.
Thank you very much!
I use your tool success downgrade to 1.49.0007.
But now my CID is HTC__621. I can't flash GB rom.
How can I do?
ray650128 said:
Thank you very much!
I use your tool success downgrade to 1.49.0007.
But now my CID is HTC__621. I can't flash GB rom.
How can I do?
Click to expand...
Click to collapse
Hmm, what was your CID before this or what is it supposed to be even?
My CID is HTC__621. But now I type "fastboot getvar cid" command , it show CID is 0202.
Then I type "fastboot oem readcid" command, it show "HTC__621"
But it can't flash "1.20.401.8 PG86IMG" to my phone...(3.28.709.3 too)
ray650128 said:
My CID is HTC__621. But now I type "fastboot getvar cid" command , it show CID is 0202.
Then I type "fastboot oem readcid" command, it show "HTC__621"
But it can't flash "1.20.401.8 PG86IMG" to my phone...(3.28.709.3 too)
Click to expand...
Click to collapse
Have you tried the RUU EXE while in fastboot USB?
ray650128 said:
Thank you very much!
I use your tool success downgrade to 1.49.0007.
But now my CID is HTC__621. I can't flash GB rom.
How can I do?
Click to expand...
Click to collapse
I successfully performed the procedure using URT 2.5.1.
After this I flash PG86IMG.ZIP RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.9020.00_10.13.9020.08_2M_release_203403_signed
where HBoot is 1.49.0007. (using phone botloader)
Then use Revolutionary without Recovery flash - now phone REVOLUTIONARY-HBoot 1.49.0007-S-OFF
Then From PC use RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed - now phone is LOCKED-HBoot 1.53.0007-S-OFF
Then flash PG86IMG.ZIP 4EXT (using phone botloader)
Then from 4EXT flash root-OTA-ICS.zip (using phone botloader and recovery)
All OK. Phone rooted, CID_032. Original CID was also 032. No problem. Check with app CID GETTER from GPlay
zemaniel said:
I successfully performed the procedure using URT 2.5.1.
After this I flash PG86IMG.ZIP RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.9020.00_10.13.9020.08_2M_release_203403_signed
where HBoot is 1.49.0007. (using phone botloader)
Then use Revolutionary without Recovery flash - now phone REVOLUTIONARY-HBoot 1.49.0007-S-OFF
Then From PC use RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed - now phone is LOCKED-HBoot 1.53.0007-S-OFF
Then flash PG86IMG.ZIP 4EXT (using phone botloader)
Then from 4EXT flash root-OTA-ICS.zip (using phone botloader and recovery)
All OK. Phone rooted, CID_032. Original CID was also 032. No problem. Check with app CID GETTER from GPlay
Click to expand...
Click to collapse
OK, so I have a couple confirmed working... but it still doesn't sit right with me that it's not reading the CID correctly.
I'm pretty sure I know why it might have happened (the misc partition stores the CID I believe...) but I can't explain why it didn't happen for some. But I've also fixed that possibility as well in version 3.0.
Anyways, I'm leaving the link down for now, as I don't want anyone else to damage their phone this way.
I'm working on 3.0 right now, which is coming along nicely I might add. I simplified so much of the code, made it much more user friendly, and fixed a lot of the minor bugs and holes in the programming that would allow for unexpected results... Including this CID issue I believe.
Also fixed the way it writes to the log file, so it will be much easier when people can just post their log file. :good:
Once I get my device back and run through as much testing on 3.0 as I can with my own device, I'll release it for you all. :good:
I'm also looking into a better brick method, but I'm not going to release that until I actually test it... I don't know what damage it could do yet. :/
I might ask for some help from some people in the GSM world for copies of certain partitions, but more on that when I have my device back.
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade HBOOT)
No chance of getting this to work on Windows? Unfortunately my linux skills are very limited, and that combined with my lazyness to install it... I hope you get the point.
In any case, this tool seems more than awesome, great job
Sent from my HTC EVO 3D X515m using XDA Premium HD app
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade HBOOT)
posedatull said:
No chance of getting this to work on Windows? Unfortunately my linux skills are very limited, and that combined with my lazyness to install it... I hope you get the point.
In any case, this tool seems more than awesome, great job
Sent from my HTC EVO 3D X515m using XDA Premium HD app
Click to expand...
Click to collapse
Nope windows can't detect certain things like Linux can
Sent from my SPH-L710 using xda app-developers app
Hey, I am trying to root my HTC evo 3d phone with hboot 1.58. I followed all 12 steps on htcdev.com, except on the final step I punch in: fastboot flash unlocktoken Unlock_code.bin and enter, then noting happens. The phone is supposed to reboot with the unlock option..but nothing happens
Also, the phone is Sprint CDMA if that makes any difference, so no sim card
....................................................................................................................................................................
THREAD SUMMARY
K finally got th phone rooted so here is what you have to do. The following applied to my ***locked*** S-ON Sprint HTC Evo3d with hboot 1.58 but should work with any other version higher than hboot 1.40.
The purpose is to get S-OFF(ROOT the phone) and also continue to use your factory HbOOT 1.58 and main version in the end.
1. Brick the phone carefully following steps outlined in unknownforce's [TOOL] Ultimate Recovery Tool 3.1 (Unbrick, Downgrade, VM Radio Fix/Reset). Scroll down to the "Downgrade/Unbrick" section and begin the bricking process with the PG86IMG.zip he mentions in "things you'll need".(place the zip on SD card in the main directory and name it PG86IMG)
2. Once phone is bricked(indicated by SOLID and very dimly lit charge light with the AC charger connected. Also the phone will not turn on or boot), download latest version of URT 3.1(first link in [TOOL] thread), continue to the second step 2 which involves booting up with Linux live boot CD on your PC, OR you can use URTLiveCD 1.0 and you will not need Linux
I did it the hard way an used latest version of URT with Ubuntu v12.04 LiveCD. I would recommend URTLiveCD 1.0 as you will boot straight to the tool and will not need the Ubuntu terminal.
3. After successfully completing downgrade with URT 3.1 downgrade, boot up to your new HBOOT 1.40 bootloader screen and enter fastboot USB mode. CHECK THAT THE MAIN VERSION HAS BEEN LOWERED ALONG WITH THE HBOOT.
Log back into windows
3.(A) If you haven't done this yet, get a fastboot PC command directory to retrieve all phone identification info from the bootloader. I used ROOTEVO3DNEW to check my phone's identity info at this point(though there are many programs that do the same thing). Create a new folder in C:\ and name it rootevo3dnew. Unzip all rootevo3dnew.zip contents into that folder.
Now open the command prompt with the phone connected to PC in fastboot USB. Type cd \rootevo3dnew and enter. Now type the following: "fastboot getvar all" (without quotations) and enter. A list should appear. Check that you have: (bootloader) version-main: 0.01.651.1. If this number is still 2.95.XXX.XXX or something close to it, then YOU MUST BRICK THE PHONE AGAIN. See posts starting at #35 of this thread for a more detailed guide through the second brick. It may be very tricky but very much the same process!!!!!
4. After successfully lowering HBoot to 1.40 and the main-version to 0.01.651.1 you can run the 1.13 RUU.exe found HERE: http://d-h.st/h1p . Connect the phone to fastboot USB and RUN the .exe....after the 1.13 .exe successfully runs, your main version should now be 1.13.651.7...again, checking using your rootevo3dnew tool from 3.(A) above....
5. REVOLUTIONARY S-OFF. Very simple, download for windows(or Linux) and fill in your info and retrieve you BETA key. Run REVOLUTIONARY application (which will run in the command prompt) and after successfully completely revolutionary S-off, YOU ARE ROOTED...continue to step 6
6. RESTORE your main version to 2.95(from 1.13) by running the 2.89 zip (HERE . Place this .zip in your main directory(RENAME IT PG86IMG) on the SD card and let it unzip and install it from the bootloader.
After that, you are pretty much finished!! boot up to android(main version 2.89) and let system updates detect and bring you back to 2.95.xxx.xxx..
....
Download and Install a custom recovery. Rename that .zip PG86IMG and install from bootloader as you did with the 2.89 zip. Now you have a custom recovery where you can backup and restore, install ROMS or other software without having to rename it PG86IMG every time, wipe partitions and lots of other stuff...
Now, download this and place it on your SD main directory. Then, using your new recovery(by selecting "recovery" in bootloader menu), select "install from sdcard" and "choose zip from sdcard", select the SuperSU zip and let it install. Reboot, get to homepage, and install SuperSU from the play store. You now hae an administrative super APP that will let you choose which apps are given root access.
Custom ROMS can be installed the same way from the custom recovery. I am currently using Negalite BluRom and loving it
...
THE 6 STEPS OUTLINED HERE PRETTY MUCH COVER EVERYTHING FROM THIS THREAD
HUGE THANKS TO USERS MPGRIMM2 AND BRIAN706 FOR NEARLY 3 DAYS OF HARD WORK !!
Did you get your motherboard replaced at some point of time?
Can't think of a good sig
donkeykong1 said:
Did you get your motherboard replaced at some point of time?
Can't think of a good sig
Click to expand...
Click to collapse
My what? Yes I swapped out my 67370m dv6 pavilion mainboard for radeon HD 6550m graphics chipset. How did you know?
otto325 said:
My what? Yes I swapped out my 67370m dv6 pavilion mainboard for radeon HD 6550m graphics chipset. How did you know?
Click to expand...
Click to collapse
On the phone?
Can't think of a good sig
donkeykong1 said:
On the phone?
Can't think of a good sig
Click to expand...
Click to collapse
Oh ok, what the hell..No, I just got the phone on ebay for $30, currently locked and I am trying to root it. Some Brittney girl owned according to phone identity info left on the phone
Do I need to downgrade the hboot from 1.58 to 1.4? Sorry I'm really new to smartphones, any help is really appreciated
Just in case it was missed, the phone doesn't reboot upon flashing the unlock token. A prompt should appear on the device and you have to confirm the bootloader unlock.
He asked about the motherboard, because there is an issue if the motherboard has been swapped; sometimes the bootloader will not unlock. I think it's due to mismatched firmware.
Usually running the RUU will solve the issue.
You can download a copy here: https://copy.com/jF1Mm
The only problem is, if the phone had taken the latest Ota update and you are on main version 2.95 instead of 2.89, the RUU will not run because it won't let you downgrade.
You can also check your main version by running a fastboot getvar all.
Is there any chance your device is already s-off from a previous owner? It will say s-on or s-off on the bootloader screen.
If you're lucky enough to already have s-off, you can skip the bootloader unlock altogether.
Brian706 said:
Just in case it was missed, the phone doesn't reboot upon flashing the unlock token. A prompt should appear on the device and you have to confirm the bootloader unlock.
He asked about the motherboard, because there is an issue if the motherboard has been swapped; sometimes the bootloader will not unlock. I think it's due to mismatched firmware.
Usually running the RUU will solve the issue.
You can download a copy here: https://copy.com/jF1Mm
The only problem is, if the phone had taken the latest Ota update and you are on main version 2.95 instead of 2.89, the RUU will not run because it won't let you downgrade.
You can also check your main version by running a fastboot getvar all.
Is there any chance your device is already s-off from a previous owner? It will say s-on or s-off on the bootloader screen.
If you're lucky enough to already have s-off, you can skip the bootloader unlock altogether.
Click to expand...
Click to collapse
THANKS
main version 2.95.651.5. If I factory reset the phone and discard updates, will the main version reset to 2.89 making the RUU possible?
EDIT: factory reset and no updates did not bring main version down to 2.89
***LOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
Also check most recent post (#508) in the guide thread.
http://forum.xda-developers.com/showthread.php?t=1889438&page=51
Factory reset won't affect your main version
As DK mentioned, a factory reset only resets your current build. It would only take you back to the point of the last OTA update.
Unfortunately, you can't lower the mainversion without the bootloader unlocked, so it's a catch 22 there.
As a long shot, you might look into the new towelroot, thought I really don't think it will work for this phone because HTC locks down the /system partition. It would at least be worth looking in to.
As far as the hboot downgrade method (I assume you mean THIS) it was intended to downgrade from 1.50 Gingerbread to 1.40 Gingerbread. I have no idea if it will work to downgrade from 1.58 ICS?? You might want to ask around a little about that.
Okay... I just saw your posts in the other thread, have you actually received the unlock token from HTC?
IE, you received a file via email named Unlock_Code.bin that you placed in your fastboot directory and then typed the command: fastboot flash unlocktoken Unlock_code.bin ??
Also, when you say nothing happens after running the command, something must happen whether it's the intended results or not. Can you tell us what the command prompt returns after running the command? Maybe just copy/paste it here.
There will either be an error or a confirmation after running the command.
Comes up as successful on the command prompt. But the phone does not reboot or direct to the unlock screen. I just remains on the fastboot USB screen and does nothing.
C:\rootevo3dnew>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.153s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.163s
Thanks for that... That's a bummer. Looks to me like you have the motherboard swap issue. It really sucks that you can't RUU.
It looks like someone answered the question in the other thread though about the hboot downgrade method.
So I got the HBOOT downgrade(0.8.2) boot for a disk but it says the phone needs to be bricked before the downgrade..
That's where I'm at now basically, I'm going to do a little more reading on bricking...
Also would be good to have confirmed that this downgrade will work starting with hboot 1.58, so I don't mess anything up
mpgrimm2 may have found found his way over here from from the [Guide] thread
Also I hope I am downloading the correct RUU's. I had to fish them from various searches because the link supplied in Unknownforce's thread is invalid:
2.17 RUU:
http://d-h.st/ru0ow8ps0i01/PG86IMG_2.17.651.5.zip
1.13 RUU:
http://d-h.st/Xrp
mpgrimm2 said:
Well. Post that in Unknownforce's Ultimate Recovery Tool thread so you are not "off topic" here.
I haven't used the Evo3d in a while but you should probably look over my ...
Post 781 in Unknownforce's thread and the follow up posts right after.
Additional info you may need from my
[Guide]My Hboot 1.5x HTC Unlock/recovery/rom/kernel flashing notes 2-13-13
and
Post 11. My Gathered RUU .exe/.zip Links (& How to extract RUU zip yourself)
Click to expand...
Click to collapse
Fyi, I think Unknownforce indicated in one of his first 3 posts that u can brick with the last 2.95 PG86IMG.zip file he linked and then downgrade to 1.13 for s-off. Have to go check...
Keep in mind that you may want to considering posting any issues with the URT/Downgrade tool in Unknownforce's thread if you want any chance of assistance from him.
Bad link in his op but this post has it...
Unknownforce said:
Well, with the 2.95 OTA, they included the HBOOT in the firmware, so it's now much faster of a load time for PG86IMG when doing the brick.
I pulled the new PG86IMG.zip from the OTA update, and it's only 19MB, which takes only 15-20 seconds to fully load and be ready to press volume up to update... this will significantly cut down on the time it takes to downgrade, as you can re-try over and over very quickly now.
Here's the PG86IMG file -> http://d-h.st/3p8
Click to expand...
Click to collapse
And just as a reference for you later I will quote myself from Ramjet73's 2.95 ota update thread
mpgrimm2 said:
ramjet73 and others. I see we still don't have any source for the 2.95.651.6 RUU's. Since I just went ahead and reset my 2 Evo3d's back to stock/S-off as a backup here are the files I had to step through if you want to add or host them directly:
- PG86IMG 2.89.651.2.zip - 449.18 MB
Full RUU.zip for use in bootloader (rename to PG86IMG.zip & place on /sdcard)
- OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.5-2.89.651.2_release_307948lagg6bmccb9c63ip.zip - 51.11 MB
2.89.651.2 update to 2.95.651.5 zip for use in bootloader (rename PG86IMG.zip & place on /sdcard ) or stock recovery (place in /sdcard/download )
This is the last official update that just downloaded to my phone after the other Ruu's/updates that were posted previously
- OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.6-2.95.651.5_release_315505rm3j000awvlstw9z.zip - 10.59 MB
2.95.651.5 update to 2.95.651.6 zip for use in bootloader (rename PG86IMG.zip & place on /sdcard ) or stock recovery (place in /sdcard/download )
Wish someone with HTC/Sprint access would post up the latest full RUU. It was a bit of a pain stepping through the updates, but definitely easier being s-Off. Seems that if someone is S-On with the 2.95.651.6 update and can't get past step 13 of the HTC Unlock or needs to RUU back, their only option is Unknownforce's Hboot Downgrade Ultimate Toolkit and "Brick it Twice" to get back to an earlier version for Revolutionary S-Off and then go through the updates from 2.89 on up.
Hope this helps others.
EDIT:
I may be too tired at the moment to figure this out, but for some darn reason both the official OTA Updates would not flash from the bootloader on a stock 2.89.651.2 phone with S-Off (both phones actually). Didn't matter if it was renamed PG86IMG.zip or left as officially downloaded to sdcard/download and booting into the stock recovery. The MD5 of my 651.5 update file matches Ramjet73's as well. But If I connect to wifi, do a system update, let it download (how I got the files) and reboot automatically, it works fine and updates without issue.
Click to expand...
Click to collapse
Forgive me for being such a noob with this stuff.
I'm reading about hboot 1.58 needing to be bricked twice to be able to run the 1.13 RUU.
So to start, do I place the 18.7mb PG86IMG .zip (from the second quote in your last post) in the "download" folder of the sd card?
The stock
(OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.6-2.95.651.5_release_315505rm3j000awvlstw9z)
Click to expand...
Click to collapse
is there, so do I remove that one and replace it?
I don't think so but just to be sure, I drop the 18.7 PG86IMG zip folder in downloads and begin the brick process, then run the hboot 0.8.2 to downgrade?
*EDIT* ok, place in the MAIN directory. It's working and is unloading the .zip in bootloader
I need a new data sync cable, mine has started intermittently losing connection off and on...going to wait until I have a new one before I go any further.
Also, the latest version of ubuntu that Linux offers did not work. I found an earlier version(12.04) and the boot disk works so I am good to go on that
What is Hboot 0.8.2 ? Are you using Unknownforce's URT 3.1 Tool and following the "Downgrade/Unbrick" section?
This one:
http://forum.xda-developers.com/showthread.php?t=1563342
Yep, that is an outdated/earlier version. You need to use the Ultimate Recovery Tool from Unknownforce's thread as I linked earlier (URT v3.1) and use the LiveCd link.
see here
Sent from my "Up All Night Sleep All Day" Nexus 5!
THANKS
Well I just did a dry run with the Linux boot disk and terminal. Extracted downgrade.zip to HOME folder, ran the commands. I'm getting the correct code returns in the terminal. I got up to the:
Code:
Step 1... Plug in Device while holding down Volume Down key...
Waiting for device...
Just a matter of getting a new data sync cable now and I can do this...
Again thanks for your help, I'm pretty new to this process I've never altered a devices firmware manually before so it's an awesome experience as well..
Will report back in a couple days, hopefully with a newly rooted phone
--------
Also, do you have a direct link to the correct 1.13 RUU EXE to run after the downgrade?
otto325 said:
Also, do you have a direct link to the correct 1.13 RUU EXE to run after the downgrade?
Click to expand...
Click to collapse
Yep. Previously...
mpgrimm2 said:
....
Additional info you may need from my
[Guide]My Hboot 1.5x HTC Unlock/recovery/rom/kernel flashing notes 2-13-13
and
Post 11. My Gathered RUU .exe/.zip Links (& How to extract RUU zip yourself) <<<--- HERE
Click to expand...
Click to collapse
Sent from my "Up All Night Sleep All Day" Nexus 5!