Hello,
First time poster, long time reader...since the G1.
I have an HTC Amaze and have searched for several days without finding an answer to my problem. I used Hasoon's toolkit to unlock the bootloader (and root) strictly to allow tethering. I attempted S-Off without success and when I used Hasoon's toolkit to relock the bootloader, adb shell says device not found (USB debugging enabled..I checked many times). The phone is still S-On and has the most updated Tmobile stock firmware downloaded on phone. I decided to perform a factory reset to see if this would fix my 'device not found problem' using Hasoon's toolkit (which it did not). Later I received a notification for an update on my phone (I guess because I did a factory reset). I downloaded the update and tried to install but it said sd card not found. So I then went into ext4 recovery and pushed the update.zip on my phone. Everything worked ok except now WIFI says error and bluetooth won't turn on. I have to admit I am very confused. I just want to go back to a working device and can't seem to find any answers. I flashed an older ruu hoping it would fix my problems but it has not.
Current software: 4.0.3
Kernel: 3.0.16-ga4fb83c
I think what I need to do is relock the bootloader and flash the latest ics firmware from tmobile. Hasoon's tool does not recognize my device so I will have to relock it using another method. Any help would be great.
http://forum.xda-developers.com/showthread.php?p=41278245
All these instructions are for the HTC Amaze. I am on the T-Mobile North American version.
If my instructions below cause thermal nuclear war I am not responsible for what you did or didn't do.
Here is my guide updated.
Obtaining S-Off and being SuperCID allow for this process to run smoothly as well as having 4ext as your recovery.
S-Off http://unlimited.io/juopunutbear.htm
SuperCID http://forum.xda-developers.com/showpost.php?p=25154672&postcount=1
Hasoon's AIO Toolkit helps you accomplish a lot of these steps quickly.
http://d-h.st/8d0
1. RELOCK Amaze (On your computer with htc drivers installed and your device in fastboot and connected to your computer enter
2. Download 2.14.531.3 from here http://d-h.st/z70 CHECK MD5 SUMS!!!!!!!!
3. Renamed it to PH85IMG.zip
4. Place it onto SD-Card
5. Reboot into bootloader.
6. Let bootloader find the update and let it finish its update.
7. Reboot phone.
8. Go to Settings>About Phone>Software update and checked for updates.
9. Download the system update for 30 megs and install the update.
10. Allow devices to finish update
11. Software number is 2.14.531.30 710RD
12. Baseband version is 1.15.550L.08DC_30.80.550L16D
13. Build number 2.14.531.30 CL449991
14. Unlock your device with Hasoons AIO Kit.
15. Update recovery to 4ext. (Use Hasoons AIO toolkit)
16. Download ARHD 4.0 from here
17. CHECK MD5 SUMS!!!!!!!!
18. Place it onto your sd-card
19. Flash in 4ext recovery
20. Let device boot.
21. Enjoy ARHD 4.0
Mgoggles said:
I think what I need to do is relock the bootloader and flash the latest ics firmware from tmobile. Hasoon's tool does not recognize my device so I will have to relock it using another method. Any help would be great.
Click to expand...
Click to collapse
I'll give this a try and let you know if it works. Thanks for replying.
Quick question and update.
I finally was able to relock the bootloader. For some reason hasoon's kit would not recognize my device so I booted into the bootloader and enabled fastboot and then used hasoon's kit to relock the bootloader successfully. From here I am downloading the PH85IMG and putting it on the root of the sd card and then rebooting into bootlader. Do i really need S-off to do this?
100 Thank you's PeterC18st!
I flashed the PH85IMG and my wifi and bluetooth work. I can resume watching playoff hockey now. I will click on the thanks button. Have a great night!
unable to install again
Mgoggles said:
100 Thank you's PeterC18st!
I flashed the PH85IMG and my wifi and bluetooth work. I can resume watching playoff hockey now. I will click on the thanks button. Have a great night!
Click to expand...
Click to collapse
Hi,
I have been trying to update my asian amaze to the 2.14.531.30 version with repeated failure. I tried PeterC18st method, but it still shows the error, ''we have determined that your phone may be running.. bla bla" I am getting this prompt about a software update availability. I had already done SuperCid and SOFF.
I had relocked amaze, flashed http://d-h.st/z70 (i had checked the checksum too) in bootloader. Bootloader finds the file and it installs. When the update is checked, it shows update available, however, after full download, it fails by showing the error, "we have determined that your phone may be running..".
I could update when i had flashed the amaze RUU from http://forum.xda-developers.com/showthread.php?t=2167596. Once the update finished, however, the wifi and bluetooth failed to even start.
Can asian amaze be updatd?
Thanks a lot
@tlz said:
Hi,
I have been trying to update my asian amaze to the 2.14.531.30 version with repeated failure. I tried PeterC18st method, but it still shows the error, ''we have determined that your phone may be running.. bla bla" I am getting this prompt about a software update availability. I had already done SuperCid and SOFF.
I had relocked amaze, flashed http://d-h.st/z70 (i had checked the checksum too) in bootloader. Bootloader finds the file and it installs. When the update is checked, it shows update available, however, after full download, it fails by showing the error, "we have determined that your phone may be running..".
I could update when i had flashed the amaze RUU from http://forum.xda-developers.com/showthread.php?t=2167596. Once the update finished, however, the wifi and bluetooth failed to even start.
Can asian amaze be updatd?
Thanks a lot
Click to expand...
Click to collapse
I had even changed Sid to tmob010 after flash when it failed to update with 11111111 sid. Still the same error. I was on gb and had upgraded to ics with the gb to ics for Asian amaze thread here. So, I believe this phone is currently on American version of software. Can this update be performed on this device
@tlz said:
I had even changed Sid to tmob010 after flash when it failed to update with 11111111 sid. Still the same error. I was on gb and had upgraded to ics with the gb to ics for Asian amaze thread here. So, I believe this phone is currently on American version of software. Can this update be performed on this device
Click to expand...
Click to collapse
Never mind. figured it out myself after a few flashes
PeterC18st said:
http://forum.xda-developers.com/showthread.php?p=41278245
All these instructions are for the HTC Amaze. I am on the T-Mobile North American version.
If my instructions below cause thermal nuclear war I am not responsible for what you did or didn't do.
Here is my guide updated.
Obtaining S-Off and being SuperCID allow for this process to run smoothly as well as having 4ext as your recovery.
S-Off http://unlimited.io/juopunutbear.htm
SuperCID http://forum.xda-developers.com/showpost.php?p=25154672&postcount=1
Hasoon's AIO Toolkit helps you accomplish a lot of these steps quickly.
http://d-h.st/8d0
1. RELOCK Amaze (On your computer with htc drivers installed and your device in fastboot and connected to your computer enter
2. Download 2.14.531.3 from here http://d-h.st/z70 CHECK MD5 SUMS!!!!!!!!
3. Renamed it to PH85IMG.zip
4. Place it onto SD-Card
5. Reboot into bootloader.
6. Let bootloader find the update and let it finish its update.
7. Reboot phone.
8. Go to Settings>About Phone>Software update and checked for updates.
9. Download the system update for 30 megs and install the update.
10. Allow devices to finish update
11. Software number is 2.14.531.30 710RD
12. Baseband version is 1.15.550L.08DC_30.80.550L16D
13. Build number 2.14.531.30 CL449991
14. Unlock your device with Hasoons AIO Kit.
15. Update recovery to 4ext. (Use Hasoons AIO toolkit)
16. Download ARHD 4.0 from here
17. CHECK MD5 SUMS!!!!!!!!
18. Place it onto your sd-card
19. Flash in 4ext recovery
20. Let device boot.
21. Enjoy ARHD 4.0
Click to expand...
Click to collapse
thanks very much
new to amaze and was able to make my friends WiFi and Bluetooth fixed with your help !!!
Related
K… Bought a HTC Amaze 4G through Telus. I travel a lot and need to be able charge the phone on the road so i was using any charger that would fit in the port to charge the device. This gave my serious battery life problems. Brought the phone back to Telus. They gave me a new battery, but i had the same results.
So I,
- Unlocked the bootloader (through HTC.Dev)
- Rooted the phone with HTC Super Tool V3
- Installed Battery Cal App from the market place
- Bumped charged to battery until i figured it was full
- Then reset the Battery Cal file
Once i tested the battery and found it to be like new i,
- Flashed CWM recovery and backed up the phone.
All was well till Telus OTA'ed ICS. I tried to update and could not. I read on all the XDA forums you cannot OTA update with root/custom recovery/blah, blah, blah….
I tried to,
- Unroot with HTC Super Tool V3. Nope
- Unroot with ADB. Nope
- Re-locked the bootloader and unlocked a couple of times trying different things. At this point the phone still worked as a phone. Just would not OTA update.
So i decided to try S-Off with Hasoon's Amaze S-off All In One Kit V1.0. Then maybe flash Energy Rom. I tried for a couple of days. First i had ADB issues. Wiped laptop. New ADB. Then it kept giving me Errorcode: 66732337 ErrorMsg: Still sober. I could not boot the phone anymore. Just to Hboot. After a weekend of this i kept reading and found to get back to stock all i had to do was flash RUU through Hboot. Then i could get the OTA. So I,
- Found RUU_Ruby_TELUS_WWE_1.41.661.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_222694_signed.exe
- Zipped it and renamed it PH85DIAG.zip
- Put it on root of SD card
- Booted in Hboot
Then the phone,
- Loaded the .zip (blue bar on the right)
- Checked the .zip (orange bar on the right)
But it does not return to stock. Then i read this "return to stock" method only works if you are using stock recovery. So i,
- found stock recovery from Telus-1.41-Restore-Flasher
- flash recovery with Fastboot
But the phone still does not return to stock.
At this point the phone only boots to Hboot. It says,
*** RELOCKED ***
*** Security Warning ***
Ruby PVT SHIP S-ON RL
HBOOT-1.90.0006
eMMC-boot
I just want to return to stock and get the Telus OTA. I don't know what i am doing wrong. Do i need lock the bootloader not relock the bootloader. Do i have the wrong Hboot or something.
THX
Have you tried Hasoon's All-in-one Toolkit?
When using the ruu signed exe file, you do not zip it and rename it to anything, simple boot the device into hboot, select fastboot, plug in the usb cable and run the ruu exe file on your pc, follow all on screen instructions then let it update the device, once complete, let it boot full, then check for software update via settings to install the ICS ota from TELUS.
kered424 said:
Have you tried Hasoon's All-in-one Toolkit?
Click to expand...
Click to collapse
I have Hasoon's HTC Amaze All-In-One Kit V3.2. How do i use it to return to stock?
Dark Nightmare said:
When using the ruu signed exe file, you do not zip it and rename it to anything, simple boot the device into hboot, select fastboot, plug in the usb cable and run the ruu exe file on your pc, follow all on screen instructions then let it update the device, once complete, let it boot full, then check for software update via settings to install the ICS ota from TELUS.
Click to expand...
Click to collapse
See.... now i feel like an idiot!!! Ran Telus RUU .exe and it worked like a charm. Anyway, THX guys!!!:good::good: Got my OTA.
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!
Okay, guys, I apologize for what I'm about to ask, but I am now completely lost in the Global Update thread, so I needed to start fresh.
I was rooted and on stock 3.14.605.13. I kept getting annoying update messages from Verizon and tried several forum suggestions to turn them off. Finally I just decided to try to get the update. I was able to unroot and install an RUU back to 3.14.605.12, but now I'm completely stuck. :crying: I'm getting the same Service Unavailable message as others who try to get the small .13 update.
I have downloaded the 3.14.605.13 update zip but can't decipher how to get it installed since the Global Update Thread is now so jumbled.
If anyone has the time to helps us NOOBS (I think I saw several others in my situation), could you please give a step by step rundown of what we need to do? Please start from step 1. For example, do I need to root again now before I can get up to .13?
Finally, if I do get to .13, can I just unroot and get the new global update via Verizon?
hunteditor said:
Okay, guys, I apologize for what I'm about to ask, but I am now completely lost in the Global Update thread, so I needed to start fresh.
I was rooted and on stock 3.14.605.13. I kept getting annoying update messages from Verizon and tried several forum suggestions to turn them off. Finally I just decided to try to get the update. I was able to unroot and install an RUU back to 3.14.605.12, but now I'm completely stuck. :crying: I'm getting the same Service Unavailable message as others who try to get the small .13 update.
I have downloaded the 3.14.605.13 update zip but can't decipher how to get it installed since the Global Update Thread is now so jumbled.
If anyone has the time to helps us NOOBS (I think I saw several others in my situation), could you please give a step by step rundown of what we need to do? Please start from step 1. For example, do I need to root again now before I can get up to .13?
Finally, if I do get to .13, can I just unroot and get the new global update via Verizon?
Click to expand...
Click to collapse
going to need some more information:
1. Are you S-off or S-on
2. Are you dev unlocked, locked, or engineering hboot
3. What hboot are you currently on
Wow, that was fast.
synisterwolf said:
going to need some more information:
1. Are you S-off or S-on
2. Are you dev unlocked, locked, or engineering hboot
3. What hboot are you currently on
Click to expand...
Click to collapse
S-ON
***RELOCKED*** (I did the HTC unlock with a pin code when I originally rooted, but I "unrooted" via a one-click program, so I don't know the correct answer to the lock question). I relocked the bootloader via sdk if that helps.
hboot is 2.25
hunteditor said:
S-ON
***RELOCKED*** (I did the HTC unlock with a pin code when I originally rooted, but I "unrooted" via a one-click program, so I don't know the correct answer to the lock question). I relocked the bootloader via sdk if that helps.
hboot is 2.25
Click to expand...
Click to collapse
you should be good to do the update.
ruu using this zip http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
(place on root of sd card, rename PH98IMG.zip)
it will run 2 times. once with be bootloader and recovery, second time will be the full rom.
this will get you to stock OTA should show up a little while after its all installed and connected to the network.
EDIT:
If updated doesnt show up in a day you should be able to update with this zip: http://forum.xda-developers.com/showpost.php?p=40768590&postcount=35
Okay, I think you're going to be able to get me there ... but ...
I downloaded the zip file and renamed it to PH98IMG.zip. I copied it to the root of both the internal and external cards since I wasn't sure which it needed to be on.
Now how do I execute the RUUx2s? The last one I did to get back to .12 was an .exe file, so that was easy.
I do have SKD and can open a command prompt, so you don't have to go that far back in instructions.
hunteditor said:
Okay, I think you're going to be able to get me there ... but ...
I downloaded the zip file and renamed it to PH98IMG.zip. I copied it to the root of both the internal and external cards since I wasn't sure which it needed to be on.
Now how do I execute the RUUx2s? The last one I did to get back to .12 was an .exe file, so that was easy.
I do have SKD and can open a command prompt, so you don't have to go that far back in instructions.
Click to expand...
Click to collapse
once on root of external sd card. reboot the phone into bootloader
power off device hold vol - and power till you see hboot
hboot will detect it and run for you.
make sure you have 70+ battery before trying this. and do not pull the battery or loose power or it will birck.
Worked like a charm. A million thanks to you.
Donation on the way!
Thanks again for being so patient!
hunteditor said:
Worked like a charm. A million thanks to you.
Donation on the way!
Thanks again for being so patient!
Click to expand...
Click to collapse
wow, thank you kindly. Any time you need help just ask, thats how we all learn.
Okay, hopefully last question.
I downloaded the OTA zip just in case.
If I need to end up doing that manually, do I rename it (and if so to what?) copy it to root and then run hboot?
hunteditor said:
Okay, hopefully last question.
I downloaded the OTA zip just in case.
If I need to end up doing that manually, do I rename it (and if so to what?) copy it to root and then run hboot?
Click to expand...
Click to collapse
just like the ruu rename it to PH98IMG.zip and flash in hboot. again make sure you have enough battery
I want to install an OTA, but I had rooted it using TWRP and then followed so many procedures in trying to restore to stock that I think my phone's wasted. (It's functioning normally, but I can't help the feeling I've done something untowardly to it).
I have been doing a lot of reading, but I apparently suck since nothing seems to make sense (or that everything seems so disconnected). It appears that what could be one long, detailed post about something is to be found in many different posts, but I understand that since there are so many phones and each one probably needs its own way of being handled. So without complaining any further, I'll just let you know what I've done so far, and hopefully someone is able to tell me what the hell is wrong with me. And my phone.
Here's what I have with me right now:
Device: HTC One SV (Boost mobile) - K2_CL, OS- 4.1.2 (the OTA is 4.2.2)
Tampered, relocked, s-on.
adb is installed
fastboot is installed
android SDK with 4.1.2 and 4.2.2 packages installed
htc toolkit utility is installed
recoverytest.img from androidruu files.
revone
All right, I installed adb, fastboot, an htc utility toolkit, downloaded 3 different img files (one says recoverytest.img, which is from androidruu.com/k2_cl, another one was put here on xda by one of the members, and that was simply recovery.img, and another one called HTC_One_Sv_K2_Ul_boot_signed.img <-- this is probably the wrong file since my bootloader screen says k2_Cl).
Prior to this, a few months ago, my phone was rooted. SuperSU was working fine, and one day somehow I lost the root access when SuperSU upgraded. Tried a few methods to upgrade manually but none worked. Not sure if this is of any importance.
So after installing all those above, I did a variety of commands like revone, fastboot flash recovery.img, fastboot oem lock, fastboot flash boot recovery.img, all based on what was mentioned one one thread or another on the forum and mostly all of them gave me some kind of an error.
So I'm stuck now. My phone does nothing. When I reboot from bootloader, it says in red "this is for development purposes only, blah, blah". When I download the update and try installing it, the phone simply restarts. When I try to do factory reset from the hboot, the phone simply goes back into fastboot menu. My phone apparently doesn't have an RUU, only a recoverytest.img.
Here's where I am and I want to do what next. I jsut installed android sdk, and installed 4.1.2 package (which is the current version on my phone), and I want to update to 4.2.2, which is the latest update for htc one sv on boostmobile (installed the package for that in sdk also).
(A lot of people were also asking for cid, mid and phone model, and I have no clue how to make sure that the .img file is the same as my phone's).
I know I am all over the place, and call me a knucklehead, but I genuinely do not understand a lot of the things that are mentioned on the forums. Every thread mentions a process, and within each process is contained a subprocess which I equally do not know.
Thanks for any help with this!
PS: While I go from fastboot usb to hboot, the screen flickers for a couple seconds an dmessages like "sd checking: no image or bad image" appear for a couple seconds and then I see the hboot menu.
Edit:
Here are some, but not all, of the forums/threads I was trying to follow:
http://forums.androidcentral.com/verizon-droid-dna/287135-revone-s-off-root-method-help.html
http://androidforums.com/one-sv-all...root-without-overwriting-recovery-kernel.html
http://forum.xda-developers.com/showpost.php?p=38018890&postcount=78
http://forum.xda-developers.com/showthread.php?t=2292432
http://forum.xda-developers.com/showthread.php?t=2405050
http://forum.xda-developers.com/showpost.php?p=42371333&postcount=1480
http://forums.androidcentral.com/htc-one-sv/279026-htc-one-sv-ruu.html
http://www.androidfiles.org/?developer=K2_CL
http://forum.xda-developers.com/showpost.php?p=43266179&postcount=6
The way I understand how to do this (in layman terms) is as follows:
1. Restore to stock {by first turning S-Off, then lock the bootloader, and then RUU. I cannot get S-off using revone (revone failed, error code 2 or error code -1); the bootloader is "relocked", and I cannot get to do anything with the RUU (iow I don't know what to do with it)}.
2. Restore to factory settings.
3. Download and install the OTA 4.2.2 update.
You don't need to go S-Off to return to stock, just relocked. Here is the RUU for your phone:
http://goo.gl/0cgV6d
Run as admin. Turn off anti-virus. Have more than 30% battery life. Follow instructions as the program loads and accept whatever.
OTA zip:
http://goo.gl/ckfYQj
The RUU worked, thank you so much!
Is this OTA.zip 4.2.2? Or is it a newer version?
ravisoni said:
The RUU worked, thank you so much!
Is this OTA.zip 4.2.2? Or is it a newer version?
Click to expand...
Click to collapse
You're welcome. It is the 4.2.2 update. My understanding is that there is nothing newer. There were reports of a 4.4 update for the Boost variant, but believe it was a mistake, or at least jumping the gun by quite a bit.
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!