I WILL NOT BE RESPONSIBLE IF YOU BRICK YOUR DEVICE OR YOU LOSE YOUR ALREADY UNLOCKED BOOTLOADER
THIS ONLY WILL WORK IF YOU HAVE UNLOCKED YOUR BOOTLOADER BEFORE THE OTA
GOOD LUCK TO ANYONE BRAVE ENOUGH TO TAKE THE PLUNGE
IF YOU ARE S-OFF PLEASE VISIT THIS THREAD
To better explain this guide, what it does is explains how to get the 2.04 OTA firmware without losing your already ***Unlocked*** bootloader. You will have to lock your bootloader, then RUU back to 1.15, re-unlock your bootloader and take the OTA and then re-flash a custom recovery.
This is what I did and it should work (Not a 100% Guarantee) :
Download the 1.15 RUU
Have your ORIGINAL Unlock_code.bin token ready (from when you've unlocked your bootloader on the 1.15 release)
Backup ALL of your sdcard contents as this will completely wipe the device
Have about 30~60 minutes to sit down and do this
[Step 1]:
Boot into Bootloader and if you aren't in fastboot click on fastboot to get there and if it says " fastboot usb " you're good now
[Step 2]:
Enter the following command:
Code:
fastboot oem lock
Then let it do its thing, it might reboot.
[Step 2a]:
Boot back into fastboot then right click RUU and click on " Run as Administrator " then follow the on screen instructions.
[Step 3]:
After the RUU finishes power off the device and then boot back into bootloader again and get to " fastboot usb " then open command prompt and navigate to where you have your " Unlock_code.bin "
[Step 3a]:
Enter the following code:
Code:
fastboot flash unlocktoken Unlock_code.bin
[Step 3b]:
On your device use [Vol Up] to select " Yes " and then [Power] to proceed.
[Step 4]:
Then boot up and go to the " Update System " and check for an update (It should prompt you to take the OTA, do it)
You should now be good to go with the latest firmware and all thats left it to reflash TWRP or CWM and either a ROM of your choice or a Nandroid.
*** TAMPERED ***
*** UNLOCKED ***
Click to expand...
Click to collapse
Here is a good ROM to flash after OTA [ROM][2.04.605.2] Stock Rooted Deodexed Zipaligned Semi-Debloated + Extras
After I completed all of these steps and took the OTA, I did not have to reflash the Unlock_code.bin file to unlock my bootloader it stayed unlocked after I took the OTA but in case yours does not just re-flash the Unlock_code.bin file one more time and it should do the trick.
Here is my proof that it worked for me:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I see that this procedure keeps the bootloader unlocked. So I'm assuming that this will also allow us to reinstall superuser (supersu) again?
ghstrdr1985 said:
I see that this procedure keeps the bootloader unlocked. So I'm assuming that this will also allow us to reinstall superuser (supersu) again?
Click to expand...
Click to collapse
Yes or if you have a nandroid you can also restore that and it will be like it was just with the new firmware
That's all I did was re flash twrp and restored my nandroid and I'm all good
Sent from my HTC6435LVW using XDA Premium HD app
This is not how I did it, but glad it worked for you. I followed the guide here: http://forum.xda-developers.com/showthread.php?t=2017525
I backed up my pics, movies, music and whatnot, then I flashed TWRP 2.4.1.0 and did a Nandroid backup of system and data. TWRP is known on our device to make better backups and restores than CWR. ***NOTE*** flashing the RUU will completely wipe your phone including your backup. Make sure you copy the entire TWRP folder to your PC!!!***
Next, I locked my bootloader using:
Code:
fastboot oem lock
I then flashed the RUU as administrator. When the device boots up don't worry about GPS or signing into Google. Force an OTA update under Settings\About\Software update. Accept the update. It will download and then ask you if you want to apply. Answer yes.
The phone will reboot into stock recovery and start flashing updates. It will reboot the recovery at least once while doing so. Do not touch your phone until it boots into Android automatically. Again, don't worry about GPS or Google login. You SHOULD boot into a message that says the 2.04 update was successful. The first reboot from my "update" did not stick. I had to force another OTA update download and told it to apply again. It worked for me the second time.
Once you have a successful 2.04 update, fastboot into bootloader and unlock your bootloader again with your original unlock_code.bin.
I'm not sure if this applies any more, but step 8 of that guide says to flash the unlocked kernel and recovery. He's referring to the kernel ripped from dsb's s-off dev phone he got from the DNA launch. It allows for root access and custom recoveries to be installed. I'm not sure if this is necessary any more, but it's the only kernel I know that when you flash it, it automatically makes the phone boot into Android and you have the new "Do no not distribute outside of HTC blah blah blah" HTC logo screen. It also makes your bootloader say ***TAMPERED*** again.
I've uploaded it here (Right click and save)
After it boots into Android copy the TWRP directory back from your PC. Reboot into fastboot and flash TWRP and any kernel you want. Restore your backup (system and data.) Flash any kernel modules necessary. Wipe dalvik cache and cache (do not factory reset or wipe system.) Reboot and PROFIT. (Restore your pics, movies, music and whatnot.)
Again, this is how I did it. YMMV.
docnok63 said:
This is not how I did it, but glad it worked for you. I followed the guide here: http://forum.xda-developers.com/showthread.php?t=2017525
I backed up my pics, movies, music and whatnot, then I flashed TWRP 2.4.1.0 and did a Nandroid backup of system and data. TWRP is known on our device to make better backups and restores than CWR. ***NOTE*** flashing the RUU will completely wipe your phone including your backup. Make sure you copy the entire TWRP folder to your PC!!!***
Next, I locked my bootloader using:
Code:
fastboot oem lock
I then flashed the RUU as administrator. When the device boots up don't worry about GPS or signing into Google. Force an OTA update under Settings\About\Software update. Accept the update. It will download and then ask you if you want to apply. Answer yes.
The phone will reboot into stock recovery and start flashing updates. It will reboot the recovery at least once while doing so. Do not touch your phone until it boots into Android automatically. Again, don't worry about GPS or Google login. You SHOULD boot into a message that says the 2.04 update was successful. The first reboot from my "update" did not stick. I had to force another OTA update download and told it to apply again. It worked for me the second time.
I'm not sure if this applies any more, but step 8 of that guide says to flash the unlocked kernel and recovery. He's referring to the kernel ripped from dsb's s-off dev phone he got from the DNA launch. It allows for root access and custom recoveries to be installed. I'm not sure if this is necessary any more, but it's the only kernel I know that when you flash it, it automatically makes the phone boot into Android and you have the new "Do no not distribute outside of HTC blah blah blah" HTC logo screen. It also makes your bootloader say ***TAMPERED*** again.
I've uploaded it here (Right click and save)
After it boots into Android copy the TWRP directory back from your PC. Reboot into fastboot and flash TWRP and any kernel you want. Restore your backup (system and data.) Flash any kernel modules necessary. Wipe dalvik cache and cache (do not factory reset or wipe system.) Reboot and PROFIT. (Restore your pics, movies, music and whatnot.)
Again, this is how I did it. YMMV.
Click to expand...
Click to collapse
Thanks I forgot to add the Fastboot oem lock command...i fixed the op
I based my guide off of my own experience and the exact steps i took, to me its pretty straight forward and took as little effort as possible, it doesnt require flashing as much
That guide is to get back to Stock 1.15 what my guide is, is how to get the OTA 2.04 w/o losing the unlocked bootloader, and i wanted to make a more clean guide and put in in the Q & A section so people would see it if they came here to ask the question. Just trying to be helpful oh and that RUU link in that other guide is for the transformer TF300 Tablet haha
.torrented said:
Thanks I forgot to add the Fastboot oem lock command...i fixed the op
Click to expand...
Click to collapse
You're welcome. You never flashed unsecure.img? What kernel are you using? Do you have the "Do not distribute outside of HTC blah blah blah" in your logo? Does your bootloader say tampered?
docnok63 said:
You're welcome. You never flashed unsecure.img? What kernel are you using? Do you have the "Do not distribute outside of HTC blah blah blah" in your logo? Does your bootloader say tampered?
Click to expand...
Click to collapse
look at where i have "This is my proof" section and no After I RUU'ed I didnt have to flash anything besides the Unlock_code.bin file... I did restore my previous nandroid but it had the same kernel as the ota has
and the only way to get rid of the HTC garbage is to get S-OFF and change some things in the hboot.img
When I click your proof button, nothing happens. All other "show content" work.
The newer kernels may allow root and custom recovery without messing with the HTC boot screen and putting tampered on the bootloader. I just did it to be better safe than sorry.
docnok63 said:
When I click your proof button, nothing happens. All other "show content" work.
The newer kernels may allow root and custom recovery without messing with the HTC boot screen and putting tampered on the bootloader. I just did it to better safe than sorry.
Click to expand...
Click to collapse
Oh well it should have loaded some pictures that I uploaded I'm on the OTA stock kernel. And the the tampered msg I believe is related to using a custom recovery as well as the boot screen msg
Everything seems to be working like all my root apps and such
Sent from my HTC6435LVW using XDA Premium HD app
Ok so I followed the procedures here but cannot re-unlock the bootloader. OTA came through fine. When I attempted to apply the unlock token, the warning screen comes up & I vol+ to yes & press the power button. I let it run its cycle & then adb reboot bootloader to a relocked bootloader. I will attempting this a 3rd time. Do I need to continue doing this until it's unlocked?
ghstrdr1985 said:
Ok so I followed the procedures here but cannot re-unlock the bootloader. OTA came through fine. When I attempted to apply the unlock token, the warning screen comes up & I vol+ to yes & press the power button. I let it run its cycle & then adb reboot bootloader to a relocked bootloader. I will attempting this a 3rd time. Do I need to continue doing this until it's unlocked?
Click to expand...
Click to collapse
I going to assume it is, but I have to ask if it's the token you got from unlocking the first time? I've seen it posted that getting a new token from HTCdev does not work.
Yes it is the original token. 3 times so far hasn't done the trick. I read elsewhere that to just keep doing it until it finally sticks.
docnok63 said:
I going to assume it is, but I have to ask if it's the token you got from unlocking the first time? I've seen it posted that getting a new token from HTCdev does not work.
Click to expand...
Click to collapse
Yes it's the one from the very first time you would have unlocked the bootloader. After the OTA HTC has patched the exploit so you wouldn't even get to the step where you would get an Unlock_code.bin. I believe they patched the SuperCID hack.
ghstrdr1985 said:
Yes it is the original token. 3 times so far hasn't done the trick. I read elsewhere that to just keep doing it until it finally sticks.
Click to expand...
Click to collapse
Yea I've heard this as well, just keep trying. Best of luck to you. Try this, power off the device fully then boot strait into the bootloader and then flash it.
After re-reading the procedures over & over, should I have unlocked the bootloader before OR after the OTA? The reason I ask is because I sent the OTA before trying to unlock the bootloader.
ghstrdr1985 said:
After re-reading the procedures over & over, should I have unlocked the bootloader before OR after the OTA? The reason I ask is because I sent the OTA before trying to unlock the bootloader.
Click to expand...
Click to collapse
First you would have Locked it
Then ran the RUU
Then Unlocked it with your token
Then take the OTA
Then flash a recovery
But I also said that if the OTA locked it back up to run the token again and it should have did the trick(this part im not 100% certain because mine didnt re-lock after I took the OTA (it stayed unlocked)
what do you get in the Command prompt when you run the token? and are you in fastboot when you do it or are you in bootloader when you do it?
As you can see, I didn't try to re-unlock until after getting the OTA. I'm not sure if it matters when you do it, but you have to do it in order to get root access and flash a custom recovery.
Command prompt says it completed successfully. I'm in fastboot usb mode. I suppose I could try the RUU again & unlock the bootloader BEFORE the OTA...or is it too late to run the RUU again?
**EDIT***
Nevermind. It FINALLY unlocked. I think that was the 5th time. Again, I do thank you for all of your support on this. I must say this guide is probably the most straight-forward one here.
ghstrdr1985 said:
Command prompt says it completed successfully. I'm in fastboot usb mode. I suppose I could try the RUU again & unlock the bootloader BEFORE the OTA...or is it too late to run the RUU again?
Click to expand...
Click to collapse
This I've never tried so I can't help you out with it.
.torrented said:
This I've never tried so I can't help you out with it.
Click to expand...
Click to collapse
It's all good. I finally got it to unlock after 5 attempts.:highfive: Thank you, though.
worked for me first time! thanks
Related
Hello
I have (or had) a HTC FLyer with s-off and perma root until yesterday when I decided to upgrade to HC. Until the HTCDEV part, everything went ok, I didn't get any issue.
But during unlock bootloader via HTCDEV, it didn't go as the website directed. When I entered "fastboot oem get_identifier_token", I got a msg like this:
"... INFO [ERR] Command error !!! OKAY [0.007s] finised. total time: 0.008s"
This wasn't normal according to HTCDEv web page, but I somehow went to the next step #15, 'fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img', again everything seemd ok.
Nest step, clockwork mode - recovery THIS IS WHERE I GOT STUCK. When I "click" recovery on bootloader screen it goes to HTC screen and stuck there. I can get back to bootloader screen again by pushing power button long and then vol down - power; but I can no longer continue to CWM, therefore can't flash honeycomb syetem.zip.
When power down and vol-down+power to access bootloader menu, switching between fastboot and bootloader, there's a quick screen (it passes so quick that I couldn't figure out completely) where it says PG41IMG.zip, PG41DIAG etc. not found.
I downloaded the PG41IMG.zip, transferred to the root of the MicroSD card and booted. At the bootloader screen, this time it installed the filen and then later asked me if I wanted to update. Said "yes" with vol- and it updated the system after 5-6 mins.
As the installation ended, device opened but with 2.3.3 (Previous fw was Turkish ROM with 2.3.4 and with this 2.3.3, Turkish language was available only for Germany, Austria and Switzerland and not for Turkey. Then I used RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204108_signed if anything could revert back, nothing but updated to 2.3.4, baseband changed to 20.3501 from 20.3504, still S-off.
BUT
* HBoot is STILL 6.10.1002 and didn't go back old one 1.11.1003
* CANNOT go into recovery mode. (first a phone icone with green arrows appear than a phone icon with red exclamation sign shows up), no recovery or CWM, so cannot go anything other.
I tried to re-install HC, but this time failed in radio writing, stuck there. Not a chance to more since RECOVERY gone.
Now the tablet is working (no brick) with 2.3.4 WWE EU rom.
Any idea how to re-install with CWM working and hboot initial version? What's the best way make a clean system?
Thanks
Once you executed the RUU , you are totally back to stock ,unrooted at the version of whatever RUU you used. I would run the RUU again to get everything back to stock, working. You need to go through the root process and install CWM again as if fresh from the box. If still stuck, go to GlobalTron's Revert to GB thread on this forum.
Thanks DigitalMD for comment.
Actually bootloader screen tells I'm still s-off but guess you're right I should be unrooted. To recover CWM, I've installed su-3.0-beta4-efgh-signed.zip to sdcart, but it doesn't seem to load it.
By the way, I'm still in GB 2.3.4 do I have to still revert back to GB with Globaltron to recover hboot?
Thanks & regards,
It depends. If its booting normally, then no. But you will need to do the install of revolution CWM recovery.
Could you please elaborate on how to re-install CWM recovery?
thanks
I actually do not understand what your current status is.
Does the device boot into normal operation?
If so, what version?
DigitalMD said:
I actually do not understand what your current status is.
Does the device boot into normal operation?
If so, what version?
Click to expand...
Click to collapse
Ok let me try to explain more in details. You know here's the guide I followed
http://android.modaco.com/topic/345950-installing-honeycomb-on-your-flyer-the-complete-guide/
Below photo is where I stuck at #15 after trying to enter recovery mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
At this moment, when I swithced between fastboot and bootloader, there was an error (this screen passes so quick so I couldn't take a complete shot). Here I was completely stuck, tablet didn't turn on at all.
Looking at the above photo, I though I needed PG41img.zip; I downloaded it and copied to rootfolder of sdcard. Then the following case happened:
I said "yes" and it worked for some time and then tablet came back to life. I then used another RUU. And now the tablet is working with this rom (GB 2.3.4). Now the bootloader is as follows:
Ok, now is the PROBLEM. At this status, when I go to RECOVERY and select it by pressing power; first this screen comes;
After this screen show up for a few seconds, then this screen comes and I cannot go any further for CWM.
At this status, if I press power button for 20-30 sec, it opens normally with an error "HTC recovered from a serious error, do you want to send report" etc. and other functions seems to work normal.
Now I would ask;
* How could I fix this issue, recover "recovery" and re-load CWM?
* How can I go back and re-load HC?
By the way, I got errors during bootloader unlock with HTCDEV.
Hope it's more clear now
kego said:
Ok let me try to explain more in details. You know here's the guide I followed
http://android.modaco.com/topic/345950-installing-honeycomb-on-your-flyer-the-complete-guide/
Below photo is where I stuck at #15 after trying to enter recovery mode.
At this moment, when I swithced between fastboot and bootloader, there was an error (this screen passes so quick so I couldn't take a complete shot). Here I was completely stuck, tablet didn't turn on at all.
Looking at the above photo, I though I needed PG41img.zip; I downloaded it and copied to rootfolder of sdcard. Then the following case happened:
I said "yes" and it worked for some time and then tablet came back to life. I then used another RUU. And now the tablet is working with this rom (GB 2.3.4). Now the bootloader is as follows:
Ok, now is the PROBLEM. At this status, when I go to RECOVERY and select it by pressing power; first this screen comes;
After this screen show up for a few seconds, then this screen comes and I cannot go any further for CWM.
At this status, if I press power button for 20-30 sec, it opens normally with an error "HTC recovered from a serious error, do you want to send report" etc. and other functions seems to work normal.
Now I would ask;
* How could I fix this issue, recover "recovery" and re-load CWM?
* How can I go back and re-load HC?
By the way, I got errors during bootloader unlock with HTCDEV.
Hope it's more clear now
Click to expand...
Click to collapse
you can reinstall with fastboot
fastboot flash recovery recovery_name.img
Ok, you need to go through the Revolution root process again and let it download and install CWM recovery.
I am a bit puzzled by the bootloader still being Revolution vs. stock. You might need to run the RUU revert process again.
Then if you want to go to HC , you have to redo that entire process again.
I think you need your original unlock.bin from the HTC site if you want to unlock the step it says to unlock the bootloader.
Basically you are back to total stock unrooted, no CWM recovery.
viera77 said:
you can reinstall with fastboot
fastboot flash recovery recovery_name.img
Click to expand...
Click to collapse
Sorry, which file recovery_name.img should be? Do I have to download an image file?
Thanks.
use this
http://revolutionary.io/
DigitalMD said:
Ok, you need to go through the Revolution root process again and let it download and install CWM recovery.
I am a bit puzzled by the bootloader still being Revolution vs. stock. You might need to run the RUU revert process again.
Then if you want to go to HC , you have to redo that entire process again.
I think you need your original unlock.bin from the HTC site if you want to unlock the step it says to unlock the bootloader.
Basically you are back to total stock unrooted, no CWM recovery.
Click to expand...
Click to collapse
As seen, I am still S-off. In order to do Revolution root, in any case I have to go to recovery but this was is closed?
After PG41IMG.zip update and resurrected the tablet, I used RUU_Flyer_HTC_WWE 2.23.405.3_R_Radio_20.3504.30.08 9BU_3809.07.04.06_M_release_204108_signed
rom to return back to original hboot but didn't work. You mean I have to re-run it?
Unlocking from HTCDEV was actually where eveything started. There's the commend "fastboot oem get_identifier_token". According to HTC guide, I have to get some string to be submitted but I recieved error instead like "command error"
Need some magic wand to roll back everything where it was
Thanks.
DigitalMD said:
use this
http://revolutionary.io/
Click to expand...
Click to collapse
HBOOT now changed to 6.10.1002, so not sure if this will work, since it says it supports only hboots 1.10.0000 and 1.11.0003. But still let me give a try.
Thanks.
I think revolutionary.io also doesn't work
Says waiting for device even the device is connected and show up in device manager.
kego said:
I think revolutionary.io also doesn't work
Says waiting for device even the device is connected and show up in device manager.
Click to expand...
Click to collapse
try with fastboot
http://forum.xda-developers.com/showthread.php?p=14693680
viera77 said:
try with fastboot
http://forum.xda-developers.com/showthread.php?p=14693680
Click to expand...
Click to collapse
viera77, thanks, now that worked!!
Now I can enter recovery CWM.
But still issues with HTCDEV unlock, get the same error. Any idea how to go on HC installation?
kego said:
viera77, thanks, now that worked!!
Now I can enter recovery CWM.
But still issues with HTCDEV unlock, get the same error. Any idea how to go on HC installation?
Click to expand...
Click to collapse
because you have soff (revolutionary)
If you are a beginner, HC to install can be risky
Hello,
True, I am beginner. Actually previously I had Advent Vega and Galaxy Tab and especially Advent, I am a bit familiar to HC. But I found HTC a lot complex compared to these
About s-off and HTCDEV unlock here is Paul's guide:
7. Unlock your Flyer's bootloader with Revolutionary.
.
.
14. You are now in a state where you must unlock the bootloader using the HTC tools - visit http://www.htcdev.com/bootloader/ and follow the instructions (Flyer compatability isn't listed, but it'll work)
I think in any case, Flyer is s-off'ed before doing official unlock. Do I miss something?
Many thanks
Turn on usb debugging on the phone and run revolutionary again.
globatron said:
Turn on usb debugging on the phone and run revolutionary again.
Click to expand...
Click to collapse
USB debugging was always on during all processes, never disabled. And revolutionary didn't work neither. Still "waiting for device..."
Seems I need to do s-on somehow but don't know. DigitalMD suggests to run RUU for unrooted and s-on system but this didn't work for my case. Not sure for root, but still s-off.
FactoryROM Presents:
A lot of you are wondering how to get back to Bone Stock in case something happens during your Flashing
Addiction. You must run this RUU from a Windows based machine. You will also want to run this
executable with Windows Administrative Privileges (right click on RUU and Run as Administrator)
(1) Download this Package (Which is the HTC RUU in Executable Form) : Here
(2) If you have unlocked your HTC DNA, you must first lock the system again.
First boot into Bootloader
Code:
adb reboot bootloader
Once in Bootloader
Code:
fastboot oem lock
(3) Boot back into Bootloader
(4) Run the RUU with Administrative Privledges
(5) Follow the prompts, and Profit
While the Software Re-loads, your device will reset several times. Once everything is
said and done, your device will reboot into a freshly installed, bloated OS.
Let me know if you have any issues.
To Re-Unlock your Device:
(1) Flash RUU
(2) Turn Phone Completely Off
(3) Hold Volume Down Key and Power to Restart to Fastboot
(4) Reflash your Unlock Token (the original one sent from HTC during initial Unlock)
(5) Enter "Yes" at Unlock Warning - System will not Restart
(6) After Restart, Shut Phone Down Completely Again
(7) Reboot into Fastboot and Check your Lock Status - Should now say "Unlocked"
(8) Flash Unlocked Kernel & Recovery Again
(9) Profit
Thanks:
football (for the RUU leak)
Does this make the bootloader say "LOCKED" as opposed to "RELOCKED"?
Despyse said:
Does this make the bootloader say "LOCKED" as opposed to "RELOCKED"?
Click to expand...
Click to collapse
It will say relocked.
Unlock
Will you be able to re unlock?
thom2k said:
Will you be able to re unlock?
Click to expand...
Click to collapse
It's my understanding that once you unlocked your device, the CID is permanently cleared. So yes, you can re-unlock using the HTC tool.
Cannot re unlock
Well I installed the ruu and cannot re unlock I've even tried rerunning the unlock process as well still no go. Any ideas?
thom2k said:
Well I installed the ruu and cannot re unlock I've even tried rerunning the unlock process as well still no go. Any ideas?
Click to expand...
Click to collapse
Did you go back to the HTC site? You shouldn't have to just Justin's workaround again, simply go to the htcdev site and select "other devices" and do what you did before.
I'm in the process of re-locking mine right now, unfortunately the bootloader says:
**TAMPERED**
**RELOCKED**
**SECURITY WARNING**
I don't recall the security warning being there before..
EDIT: After flashing the RUU now it only says **RELOCKED**.
I flashed RUU last night, then had to start from square 1 to re-unlock. Since I had my BIN file from HTCDev, I thought I could just start with the "fastboot flash unlocktoken Unlock_code.bin" command, but it kept erroring out on me.
has anyone retried jcase's unlock method first before trying to re-unlock?
Cannot re unlock
nitsuj17 said:
has anyone retried jcase's unlock method first before trying to re-unlock?
Click to expand...
Click to collapse
I made several attempts with my original unlock bin after that failed I then retried jcase's unlock method to regenerate new bin but failed as well. Are you suggesting I should have retried jcase's unlock method first?
thom2k said:
I made several attempts with my original unlock bin after that failed I then retried jcase's unlock method to regenerate new bin but failed as well. Are you suggesting I should have retried jcase's unlock method first?
Click to expand...
Click to collapse
im not suggesting that you do it, was just curious if anyone had tried
WorldOfJohnboy said:
I flashed RUU last night, then had to start from square 1 to re-unlock. Since I had my BIN file from HTCDev, I thought I could just start with the "fastboot flash unlocktoken Unlock_code.bin" command, but it kept erroring out on me.
Click to expand...
Click to collapse
So you had success re unlocking? If so what do you mean by square 1? Square one on htcdev or jcase exploit
Sent from my HTC Droid DNA
thom2k said:
I made several attempts with my original unlock bin after that failed I then retried jcase's unlock method to regenerate new bin but failed as well. Are you suggesting I should have retried jcase's unlock method first?
Click to expand...
Click to collapse
Wow, I'm confused. Here's what I've done:
Ran JCase's unlock method, rooted
re-locked and flashed RUU
Tried using bin file from 1st unlock to re-unlock, FAILED
Ran JCase's exploit to re-unlock and rooted again
I forget what the error message was when I tried using the Bin file from the first (initial) unlock, but I know it didn't like it.
WorldOfJohnboy said:
Wow, I'm confused. Here's what I've done:
Ran JCase's unlock method, rooted
re-locked and flashed RUU
Tried using bin file from 1st unlock to re-unlock, FAILED
Ran JCase's exploit to re-unlock and rooted again
I forget what the error message was when I tried using the Bin file from the first (initial) unlock, but I know it didn't like it.
Click to expand...
Click to collapse
When i ran the exploit to re-unlock it didn't work for me. Are you saying it has worked for you?
WorldOfJohnboy said:
Wow, I'm confused. Here's what I've done:
Ran JCase's unlock method, rooted
re-locked and flashed RUU
Tried using bin file from 1st unlock to re-unlock, FAILED
Ran JCase's exploit to re-unlock and rooted again
I forget what the error message was when I tried using the Bin file from the first (initial) unlock, but I know it didn't like it.
Click to expand...
Click to collapse
WorldOfJohnboy. Thanks in advance for any light you can shed on this for me/us.......Were you successful in re-unlocking after RUU? I have been wanting to flash back to stock but am waiting to see if anyone has been successful in RE-unlocking. Thanks again if you can help me out :good:
Unlock
JCase is looking @ this here https://twitter.com/TeamAndIRC
Unable to find device in fastboot.
I am trying to return to stock, but here's my dilemma: I am unable to detect my device in fastboot after fastboot oem lock. I have tried uninstalling and reinstalling drivers. I have installed the HTC ones and the PDAnet ones.Fastboot even shows "fastboot usb" but it doesn't bring up the same drivers.
A windows popup says Failed to install device drivers.
With the phone relocked, it will not let me boot back into the Android OS. Trying to enter clockwork recovery just boots back into the bootloader. There is literally nothing I can do. Is it bricked?
Edit: AAAANNNNNDDDDDDD once again it randomly installed the drivers and restored. Not sure if I am going to attempt a re-root considering all the problems I have had with it.
delete
for those still having issues, you can re-unlock after flashing the RUU (havent seen anyone else comment recently, so many of you may know this already)
*need to use your original unlock token, there is no need to reuse jcase's unlock again
follow the 5 steps in the op to flash the RUU
boot to hboot after RUU finishes and reboots
navigate to your fastboot directory
fastboot flash unlocktoken Unlock_code.bin
unlock on your phone
***this will most likely *seem* to work, but fail on the 1st, 2nd, or even 3rd attempts***
after phone reboots boot back to hboot
if it still says "relocked", fastboot the unlock token again
unlock on phone
**repeat until successful
Why must you relock bootloader to flash this? You can't just flash it like a normal ROM?
So looks like people using CDMA i.e. Verizon and running the pre-alpha version of MIUI are having trouble accessing Verizon network. Then, even after reflashing a nandroid they are having trouble. If you are in this situation, then fear not! I have a foolproof solution.
Step 1. Install the stock RUU. This can be found here thanks to andybones!
To perform an RUU flash, do the following. You must have the appropriate HTC drivers installed for Windows. On Linux, you are good to go.
First of all, you MUST relock your bootloader before going through this process. To do so, type:
Code:
fastboot oem lock
Enable adb on your phone.
Type the following to boot your phone in fastboot mode:
Code:
adb reboot bootloader
Then, after placing the RUU zip file in the folder with fastboot executable, type:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <name_of_RUU_zip_file>
where replace <name_of_RUU_zip_file> with the actual name of the zip file. Here, I named it RUU.zip.
Note: If you get the following after you run RUU: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" then you need to rerun the "fastboot flash zip RUU.zip" command (i.e. 3rd command in the above set of commands) again. Press the up arrow and enter.
After you have verified that RUU completed successfully type the following cmd:
Code:
fastboot reboot-bootloader
Step 2. Boot the phone after running the RUU. You will still be unable to access the Verizon Wireless network. Don't panic. Go through the setup process and then go to "Settings>Storage>Factory Data Reset". Then, choose to do a factory reset. Let it finish the process and reboot your phone.
Once rebooted, your phone should now be able to access the Verizon Wireless network and you should be back to normal. Breathe a sigh of relief and go back to being a guinea pig and messing with the phone installing unstable ROMs! :cyclops: Go ahead and flash your favorite recovery, restore a nandroid and enjoy!
Optional Step 3: Now, you may not have to do this. However, I had to do it the first time I went through this process. Somehow, despite the fact that I had recently S-OFFed my phone, after the above process my Bootloader was relocked and I was unable to flash a custom recovery. If this is the case with you, then simply follow the FakeCID procedure to attain HTCDev unlock again. Then you can easily flash your recovery and restore a nandroid!
Happy messing around with your phones!
Thanks go to Team Unlimited.IO for the S-OFF and their tutorials on their site that taught me how to flash an RUU, and also to jose51197 for coming up with the FakeCID procedure.
Cheers! :highfive:
im trying to use the supercid, bc my bootloader is locked like you said. looking at the commands, the process to revert cid requires superuser. theres no super user on stock ruu obviously. but my cid is 1111111111. how can i change it back to vzw__001?
litetaker said:
Somehow, despite the fact that I had recently S-OFFed my phone, after the above process my Bootloader was relocked and I was unable to flash a custom recovery.
Click to expand...
Click to collapse
S-OFF and unlock are independent, you can have S-OFF and locked bootloader. I was under the impression that with S-OFF you can simply unlock the bootloader with
Code:
fastboot oem unlock
Did you try this instead of having to go through the SuperCID process?
---------- Post added at 06:30 PM ---------- Previous post was at 06:27 PM ----------
Linch89 said:
im trying to use the supercid, bc my bootloader is locked like you said. looking at the commands, the process to revert cid requires superuser. theres no super user on stock ruu obviously. but my cid is 1111111111. how can i change it back to vzw__001?
Click to expand...
Click to collapse
Follow the fakecid manual process, but when you get to the point where it says change cid to 11111111, instead change it to VZW__001
C:\Users\Jessica>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.012s]
finished. total time: 0.014s
Linch89 said:
C:\Users\Jessica>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.012s]
finished. total time: 0.014s
Click to expand...
Click to collapse
Yes, you can't perform a bootloader unlock by typing fastboot oem unlock which is strange. I believe if you are already in cid 11111111, then you can simply proceed with the unlocking process. The whole point of the fakecid process is to make your cid 11111111 so that you can use htcdev unlock. I believe you can simply proceed to unlock from the htcdev website..
Anyway, since you have finished step 1 and 2, can you confirm that you have restored network connectivity Linch?
oh yes sir the above method worked 1000000000% thank you so much! ran outta thanks for the day...rain check?
also, im trying to cut the token from the command but every time i do it closes. how do i copy and paste it??
Linch89 said:
oh yes sir the above method worked 1000000000% thank you so much! ran outta thanks for the day...rain check?
also, im trying to cut the token from the command but every time i do it closes. how do i copy and paste it??
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thank you
---------- Post added at 08:16 PM ---------- Previous post was at 08:03 PM ----------
hboot doesnt say dirtyracun anymore lol everything else is great! viper works again! did you restore your cid to vzw__001 or did you leave it as 111111111111111
Linch89 said:
thank you
---------- Post added at 08:16 PM ---------- Previous post was at 08:03 PM ----------
hboot doesnt say dirtyracun anymore lol everything else is great! viper works again! did you restore your cid to vzw__001 or did you leave it as 111111111111111
Click to expand...
Click to collapse
You can keep it either way. I don't see any harm. If you are really interested, you can revert to the original VZW__001 CID.
Some people were having problems keeping their phone with their cid modded
litetaker said:
So looks like people using CDMA i.e. Verizon and running the pre-alpha version of MIUI are having trouble accessing Verizon network. Then, even after reflashing a nandroid they are having trouble. If you are in this situation, then fear not! I have a foolproof solution.
Step 1. Install the stock RUU. This can be found here thanks to andybones!
To perform an RUU flash, do the following. You must have the appropriate HTC drivers installed for Windows. On Linux, you are good to go.
Enable adb on your phone.
Type the following to boot your phone in fastboot mode:
Code:
adb reboot bootloader
Then, after placing the RUU zip file in the folder with fastboot executable, type:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <name_of_RUU_zip_file>
where replace <name_of_RUU_zip_file> with the actual name of the zip file. Here, I named it RUU.zip.
Note: If you get the following after you run RUU: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" then you need to rerun the "fastboot flash zip RUU.zip" command (i.e. 3rd command in the above set of commands) again. Press the up arrow and enter.
After you have verified that RUU completed successfully type the following cmd:
Code:
fastboot reboot-bootloader
Step 2. Boot the phone after running the RUU. You will still be unable to access the Verizon Wireless network. Don't panic. Go through the setup process and then go to "Settings>Storage>Factory Data Reset". Then, choose to do a factory reset. Let it finish the process and reboot your phone.
Once rebooted, your phone should now be able to access the Verizon Wireless network and you should be back to normal. Breathe a sigh of relief and go back to being a guinea pig and messing with the phone installing unstable ROMs! :cyclops: Go ahead and flash your favorite recovery, restore a nandroid and enjoy!
Optional Step 3: Now, you may not have to do this. However, I had to do it the first time I went through this process. Somehow, despite the fact that I had recently S-OFFed my phone, after the above process my Bootloader was relocked and I was unable to flash a custom recovery. If this is the case with you, then simply follow the FakeCID procedure to attain HTCDev unlock again. Then you can easily flash your recovery and restore a nandroid!
Happy messing around with your phones!
Thanks go to Team Unlimited.IO for the S-OFF and their tutorials on their site that taught me how to flash an RUU, and also to jose51197 for coming up with the FakeCID procedure.
Cheers! :highfive:
Click to expand...
Click to collapse
Not to blow up the s-off thread I'm going to post here I'm having issues attempting to flash my ruu using the s-off directions and yours from above but I get nothing no errors no prompts it (cmd) just sits and eventually crashes or locks up. I've never flashed an ruu before please help I'm certain this is important to owning a inc4g
Sent from my all powerful Inc4G
prairiedogn said:
Not to blow up the s-off thread I'm going to post here I'm having issues attempting to flash my ruu using the s-off directions and yours from above but I get nothing no errors no prompts it (cmd) just sits and eventually crashes or locks up. I've never flashed an ruu before please help I'm certain this is important to owning a inc4g
Sent from my all powerful Inc4G
Click to expand...
Click to collapse
did you RELOCK, you have to relock to run ruu
Aldo101t said:
did you RELOCK, you have to relock to run ruu
Click to expand...
Click to collapse
Yes I relocked successfully but cannot flash the ruu.zip everything locks up (the whole computer actually)
Sent from my all powerful Inc4G
prairiedogn said:
Yes I relocked successfully but cannot flash the ruu.zip everything locks up (the whole computer actually)
Click to expand...
Click to collapse
Sounds like a driver issue. Instead of fastboot flash zip ... follow these instructions:
1) Rename ruu.zip to PJ53IMG.zip (make sure you don't get PJ53IMG.zip.zip in windows..).
2) Place the zip file on the root (not in any folders) of your SD card. (not internal storage).
3) Boot to Hboot by holding Volume-Down and Power. (to do this you need to make sure Fast boot is unchecked in Settings > Power)
4) The bootloader will see the image and ask you to to install it
mdmower said:
Sounds like a driver issue. Instead of fastboot flash zip ... follow these instructions:
1) Rename ruu.zip to PJ53IMG.zip (make sure you don't get PJ53IMG.zip.zip in windows..).
2) Place the zip file on the root (not in any folders) of your SD card. (not internal storage).
3) Boot to Hboot by holding Volume-Down and Power. (to do this you need to make sure Fast boot is unchecked in Settings > Power)
4) The bootloader will see the image and ask you to to install it
Click to expand...
Click to collapse
This is possibly a better option. If you can still boot that is.
If your phone is not bootable, then push the RUU.zip onto your SD card using
"adb push PJ53IMG.zip /sdcard/" by renaming it to PJ53IMG.zip first on your computer. Cheers! Hope this works.
litetaker said:
Optional Step 3: Now, you may not have to do this. However, I had to do it the first time I went through this process. Somehow, despite the fact that I had recently S-OFFed my phone, after the above process my Bootloader was relocked and I was unable to flash a custom recovery. If this is the case with you, then simply follow the FakeCID procedure to attain HTCDev unlock again. Then you can easily flash your recovery and restore a nandroid!
Click to expand...
Click to collapse
litetaker said:
Yes, you can't perform a bootloader unlock by typing fastboot oem unlock which is strange. I believe if you are already in cid 11111111, then you can simply proceed with the unlocking process. The whole point of the fakecid process is to make your cid 11111111 so that you can use htcdev unlock. I believe you can simply proceed to unlock from the htcdev website..
Click to expand...
Click to collapse
Sorry to drag this up again, but I think the reason you had to unlock your bootloader is that you never flashed the custom DirtyRacun HBOOT after achieving S-OFF you ran RUU after S-OFF, which overwrites the engineering HBOOT. With the correct HBOOT, HTCDev unlock is not necessary. It can be found on the right side of the page at unlimited.io/fireball.htm.
Just trying to solve a mystery.
Wow I never knew you had to flash the hboot! I was wondering why I had to dev unlock even though I was s off
mdmower said:
Sorry to drag this up again, but I think the reason you had to unlock your bootloader is that you never flashed the custom DirtyRacun HBOOT after achieving S-OFF. With the correct HBOOT, HTCDev unlock is not necessary. It can be found on the right side of the page at unlimited.io/fireball.htm.
Just trying to solve a mystery.
Click to expand...
Click to collapse
You should have the custom hboot installed as part of the DirtyRacun process. Check the hboot version. After DirtyRacun, it should be 1.15.1111, not the stock 1.15.0000.
After DirtyRacun, you should not need to Dev unlock.
Sent from my Fireball using Xparent Blue Tapatalk 2
I had to flash the ruu in order to fix my phone after flashing the screwy miui. That will put the old hboot back on correct?
Linch89 said:
I had to flash the ruu in order to fix my phone after flashing the screwy miui. That will put the old hboot back on correct?
Click to expand...
Click to collapse
Correct, I had the same issue just flash the dirty racun hboot from their website
Sent from my ADR6410LVW using xda app-developers app
So I'm a real noob to rooting, so please be patient. My wife dropped her phone in the washing machine without noticing, and it went through a whole cycle. Long story story, her HTC EVO 3d is dead, and had to buy used one off ebay. Just got it yesterday, it's been rooted with stock 2.3.4 rom. She was never a fan of this, so I looked into getting her a custom ICS rom. Already installed was the Revolutionary CWM recovery from the previous owner. How this differs from regular CWM, I'm not sure. I went ahead and download ROM manager and assumed I flashed the recovery to regular CWM. I then proceeded to reboot with the power and vol down buttons, and was searching the recovery menus again, and I noticed Revolutionary CWM was still on the phone. Then I somehow accidentally installed a custom rom I downloaded on the sd card, into the recovery menu. Well now the phone doesn't go past the HTC logo and I'm at a loss. Any help or am I doomed?
First thing you need to do is pull out the battery, put it back in and hold power+vol down button.
should get you into bootloader. Tell us what it says there. like s-on/off hboot version etc. you probably should be able to access recovery from there as well
How to fix recovery
Im not such an expert on android, rooting etc but that knowlegde I have ill share
As far as I know, I may be wrong, the HBoot version you have wont make a difference,
Try -
- take battery out
- replace battery and hold volume up rfirst and then press and hold power (boots in hboot after +/- 3 seconds)
- now use power, and volume buttons, boot into fafstboot(should just be power button)
- plug usb cable in computer and connect phone
- if you have fastboot, navigate to the exe (fastboot.exe) else just google fastboot download
- google your choice of recovery, 4 ext (i prefer) or cwm,etc its a zip file(extract the recovery.img file) or just a plain recovery.img file
- place this recovery.img file in the exact diractory as fastboot
- now make sure your phone says FASTBOOT USB, ,if it doesnt, check that ur phone is connected, try different usb ports or other cables
- press windows key and 'r' @ the same time, then run cmd
- navigate to fastboot directory
- type " fastboot devices" to check if cmd picks up ur phone , result should be a serial num- mine eg would look like (HN225NM5698)
- then if it did pick up device...
- type " fastboot flash recovery recovery.img " flashes ur custoom recovery u downloaded to ur phone
- now to boot into recovery type " fastboot boot recovery.img " OR to reboot type " fastboot reboot " phone reboots
IF ABOVE INSTRUCTIONS DID NOT SOLVE PROBLEM
try, if possilbe, booting into OS, download ROM manager and flash CWM recovery through that, if that doesnt work
try running a RUU, (remember to change ur CID to match RUU) and lock ur bootloader
if all else fails, follow my post @ ask team derp ur q pg.550, that might help:good:
cybergurken said:
the HBoot version you have wont make a difference,
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@OP
If you want a completely up to date phone just use the latest RUU. It will update everything to the latest.
Then if root is not important leave it. And if you want root then just flash a recovery and then superuser zip.
EDIT : I see you edited it yourself.
EM|NEM said:
First thing you need to do is pull out the battery, put it back in and hold power+vol down button.
should get you into bootloader. Tell us what it says there. like s-on/off hboot version etc. you probably should be able to access recovery from there as well
Click to expand...
Click to collapse
Yes, I'm able to get into both bootloader and Revolutionary CWM Recovery. Bootloader states:
***UNLOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
If you want to run roms w/o problems I'd suggest you get s-off.
http://forum.xda-developers.com/showthread.php?t=1889438
This guide should be sufficient
EM|NEM said:
If you want to run roms w/o problems I'd suggest you get s-off.
http://forum.xda-developers.com/showthread.php?t=1889438
This guide should be sufficient
Click to expand...
Click to collapse
Awesome, I will look into this guide. Should I do the guide step by step or just the wire trick for s-off?
@EM|NEM
Oops My Bad..
How can i forget that i had hboot 1.5 and wasnt able to use revolutionary so i did unknownforce's bricking method.
Thanks.
the wire-trick requires stock rom although some people have managed to get it to work with custom roms. you'll probably need to run the RUU to get back to stock so its best if you follow all the steps.
---------- Post added at 01:16 AM ---------- Previous post was at 01:07 AM ----------
mnomaanw said:
NO WAIT! Why do you want to go the harder way when you already have hboot 1.50, which can be s-offed without wiretrick !
Go to revolutionary.io and set your 3d free.
Dont run the ICS RUU , just run the 2.08 gingerbread ruu again and use revolutionary.
Click to expand...
Click to collapse
isnt a 1.4 hboot required for cdma? i'm not sure about this as i have a gsm device
Ok, so because it's my wife's phone, and she could care less if it's rooted or not, what is my best option here? All she'd like is stock ICS, like on her last non-rooted stock Evo 3D. Would it be best to flash ICS ruu and call it done? Is this the easiet way to get it back to basic ICS as OTA updates won't work?
cmsanchez00 said:
Ok, so because it's my wife's phone, and she could care less if it's rooted or not, what is my best option here? All she'd like is stock ICS, like on her last non-rooted stock Evo 3D. Would it be best to flash ICS ruu and call it done? Is this the easiet way to get it back to basic ICS as OTA updates won't work?
Click to expand...
Click to collapse
Yes sir! OTAs will work after clean RUU flash. And if you ever want to s-off or just unlock through htcdev, you can always do that later.
cmsanchez00 said:
Ok, so because it's my wife's phone, and she could care less if it's rooted or not, what is my best option here? All she'd like is stock ICS, like on her last non-rooted stock Evo 3D. Would it be best to flash ICS ruu and call it done? Is this the easiet way to get it back to basic ICS as OTA updates won't work?
Click to expand...
Click to collapse
If she want stock ics then the ruu well be enough
Sent from my HTC Sensation Z710e using Tapatalk 2
mnomaanw said:
Yes sir! OTAs will work after clean RUU flash. And if you ever want to s-off or just unlock through htcdev, you can always do that later.
Click to expand...
Click to collapse
Awesome, thanks for your help everyone. Appreciate it.
cmsanchez00 said:
Awesome, thanks for your help everyone. Appreciate it.
Just to confirm, I can use either the Gingerbread OR the ICS ruu correct?
Click to expand...
Click to collapse
yes but once you use ICS, you cannot use gingerbread again unless you are s-off.....you can flash same version of gingerbread or an updated version of gingerbread or ICS but you cannot flash old version once you update...in short , you cannot downgrade.
mnomaanw said:
yes but once you use ICS, you cannot use gingerbread again unless you are s-off.....you can flash same version of gingerbread or an updated version of gingerbread or ICS but you cannot flash old version once you update...in short , you cannot downgrade.
Click to expand...
Click to collapse
Perfect. Makes sense.
So I tried flashing ruu but cannot because pc cannot recognize phone, as I can't get it to go past htc logo as it just hangs there. It's basically sitting in a Charge Only mode. I'm only able to access bootloader screen. Sooooo, next option would be to place RUU on sd card and install from there, correct? Does ruu need to be zip file in order to flash in recovery screen? Or can I still use the exe file that's sitting on my desktop?
Boot into boot loader and select fastboot and connect phone to pc ...phone should show fastboot usb.then run the RUU and let it complete the process . It's not necessary to boot into android if you are in fastboot mode.
EDIT : oh sorry I forgot, that you will have to relock the boot loader before using RUU using "fastboot oem lock" command
mnomaanw said:
Boot into boot loader and select fastboot and connect phone to pc ...phone should show fastboot usb.then run the RUU and let it complete the process . It's not necessary to boot into android if you are in fastboot mode.
EDIT : oh sorry I forgot, that you will have to relock the boot loader before using RUU using "fastboot oem lock" command
Click to expand...
Click to collapse
So, here's my issue, I can see FASTBOOT USB show up no problem in bootloader, but my problem is, my pc won't recognize my phone through usb cable. My phone doesn't show up in windows explorer. Before, I could just change the USB from "charge only" to "Disk Drive" and my pc would list my sd card at Drive E. That's my issue, if pc can't see phone, I can't relock bootloader and can't run ruu. Am I missing a step here?
cmsanchez00 said:
So, here's my issue, I can see FASTBOOT USB show up no problem in bootloader, but my problem is, my pc won't recognize my phone through usb cable. My phone doesn't show up in windows explorer. Before, I could just change the USB from "charge only" to "Disk Drive" and my pc would list my sd card at Drive E. That's my issue, if pc can't see phone, I can't relock bootloader and can't run ruu. Am I missing a step here?
Click to expand...
Click to collapse
If you have htc sync on your pc uninstall it and install htc drivers (google it) and restart your pc
Also if you have antivirus disabled it too
Sent from my HTC Sensation Z710e using Tapatalk 2
hanisod said:
If you have htc sync on your pc uninstall it and install htc drivers (google it) and restart your pc
Also if you have antivirus disabled it too
Sent from my HTC Sensation Z710e using Tapatalk 2
Click to expand...
Click to collapse
I don't have HTC sync and I installed the htc drivers. No bueno.
Only way I can get my pc to recognize phone is if I go into recovery and "Mount USB Storage" - this is the only way File Exporer pops up my sd card.
Been a lurker for a while, now I need some input if possible. I have a Thunderbolt whose touchscreen is not fully working, there is a strip about 1/4" wide top to bottom that does not respond to input. I rooted it using trter's Thunderbolt Tool and have been running Santod's ICS. When I decided to return to stock I did not read anything and merely ran trtr's tool and used the unroot option. This has me stuck now with a weird state.
Boot screen:
*** UNLOCKED ***
MECHA XD SHIP S-ON
HBOOT-1.05.0000
MICROP-/
RADIO-1.48.00.0930w_3
eMMC-boot
Jul 19 2011, 14:51:08
4ext recovery is still installed for some reason.
Here are things I have tried:
1. Unroot using trtr's tool - leaves me in a non-booting state with a Security warning and Main Version failure.
2. Used HTCDev unlock and pushed PG05IMG.zip of 2.11.605. This allows me to boot to a seemingly stock ROM.
3. OTA's get pushed, device reboots but OTA's fail to install.
4. Tried recovering Nandroid backups with 4ext, no matter which one I try to restore I get stuck in a boot loop (BAMF SoaB, ICS Santod, Liquid ICS, Multi-source ICS, ICS stock deodex).
5. Tried using 4ext to install the above ROMS directly, along with full wipes and partition formats before each attempt. They seem to install but get stuck in a boot loop on each.
6. Other various combinations of HTCdev, Thunderbolt Tool, FastBoot boot.img pushes, etc. Trtr's tool connecting in booted and fastboot modes fails to unroot or root or change S-ON state.
7. Did step 2 again to get me a working phone (except touch screen problem) until I can figure out WTH is going on.
Current state - the above Boot Screen details, 2.11.605.19 deodexed-signed image, and lucky I have not totally bricked it yet.
Help please? I've googled for the last 3 days and read countless posts and am not sure what to do from here. All I need is to get it back to stock so I can send it back to HTC and get a replacement. I have a working ADB set up and am willing to follow steps exactly or read whatever page you believe I have missed, or call me a dumb n00b, berate me for not reading something, anything... at this point I have no interest in retaining data on the phone or SD card or my dignity, just a stock phone that I can send back.
Thanks all!
Me too
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
That's major coincidence I have exact same problem, down to dead touch screen strip. I've been trying to get unrooted for a week and was supposed to mail the thing back last Friday . .
Here's hoping a solution gets posted. I don't want to pay cuz the insurance refurb was fail, when my warranty service is supposed to be free replacement and it is stupid hardware failure.
All I can say is trter supposedly updated his tool to work with the latest ota, but its been about a week and he hasn't released it yet.
He did say something about having a problem with his host though.
washuai said:
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Click to expand...
Click to collapse
This is how I fixed the security warning when I first got it, using HTCDev unlock. I also used adb fastboot relock to lock back before trying the tool.
washuai said:
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
Click to expand...
Click to collapse
Yep - got that too...
Weird. Guess I'll wait for the new tool and see what it does...
As far as the identical touchscreen issue, this phone is also a refurb, my second with a touchscreen problem. The really weird part is that it works sometimes, particularly after all this work flashing and re-flashing, but I don't think it has anything to do with the ROMS or software, rather the fact that during all this work I am constantly doing battery pulls and SD card swaps and maybe it's because of a flaky ribbon connection or something - if it was not under warranty I would open it up and just try reseating anything I could find inside.
Have you tried to RUU back? It is a way manufacturers refurb or make the software new again without having to figure out what state it is in.
As long as you can get in fastboot it will work... Also could you possibly fastboot an ENG HBOOT? It doesn't show if it's unlocked nor does
it have any of those pink banners up at top.... Those I believe allow you to flash anything you couldn't normally do before... Try that.. Also I
ALWAYS manually push and flash my stuff through ADB and fastboot. It is faster (if you know what you are doing) AND it has better control
over what I am doing. I made a tut on how to flash boot screens (the very first image that comes up when you turn it on) and it is just about
same commands to flash normally stuff.
I run a Linux Box and always use root terminal so I am not certain at what point you would need superuser if any but as follows
#fastboot devices
#fastboot flash zip "name of zip" (no it doesn't have to be called anything specific, it could be called file1.zip)
#fastboot erase [option] /cache /data /system
to force it into the special RUU mode to use HTC's RUU, this is the command
#fastboot oem rebootRUU
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
jnorth said:
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
Click to expand...
Click to collapse
If you can give me today and I'll send you either the link to download the RUU or the exe itself.
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
The ota's don't install because of the custom recovery.
Backups don't work because your s-on and the kernel can be installed.
You may be able to install santod's ota rom in recovery and install the boot.IMG from the rom (kernel) in fasboot = ./fastboot flash boot boot.img
Relock the boot loader and send it in looking like stock.
There is also a way to spoof your main version and downgrade from ICS to GB Ruu stock. That is posted on another site.
Sent from my ConD3m3dPaC-man ADR6425LVW using xda app-developers app
tburns said:
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
Click to expand...
Click to collapse
Working on this now, as soon as I figure out how to get s-off again. Thanks!
http://androidfiles.org/ruu/?developer=Mecha
The RUU's to take you back to stock
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
jnorth said:
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
Click to expand...
Click to collapse
that is what the community is all about , right?
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
you could ALWAYS use an ENG and nobody would be non-the-wiser if you rooted or not! It would look like a developer phone instead..
when it says ***RELOCKED*** it tells anybody and everybody you have been rooted at one point or another (no bueno for warranty)
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
this -SHOULD- take care of the pink banner up at top BE CAREFUL WITH THIS!!!
there again... I run constant root terminal so I do not know if it requires root or not soooo.....
#fastboot oem mw 8d08ac54 1 31302E30
#fastboot flash hboot whateverhbootfile.nb0