Related
I have a secondary Evo 3D on my account that recently took a crap. My friend that was using it took the OTA update and it caused it to be updated to 2.17 but also HBOOT 1.5. So from there I unlocked it via HTC unlock method and installed SupraROM. I don't know the exact details but the phone became stuck in an infinite reboot mode. I tried to do a wipe and install the latest MeanROM but when it would boot the battery indicator would show a red triangle with an exclamation point and reboot within 10 seconds. I swapped batteries with a working 3D so I know it's not the battery. I tried downloading a stock 2.17 rom PG86IMG but it won't recognize or install in bootloader or TWRP (I've tried multiple zips). In bootloader it still shows S-ON and then ***UNLOCKED*** in pink up top.
What would be the best way to recover this phone back to 100% stock? Is it bricked or can it be fixed?
You will have to re lock the bootloader first. From fastboot, type "fastboot oem lock"
After the bootloader is re locked, it will allow the PG86IMG.zip to update the phone
Sent from my HTC Evo 3D using xda premium
Oh man I hope its that simple. Thanks!
EDIT: Nevermind, delete.
The phone is recovered and back to stock! Thanks!
Could you go into more detail please!
The Fer-Shiz-Nizzle said:
You will have to re lock the bootloader first. From fastboot, type "fastboot oem lock"
After the bootloader is re locked, it will allow the PG86IMG.zip to update the phone
Sent from my HTC Evo 3D using xda premium
Click to expand...
Click to collapse
GalaXy S ll [blazerV3] @ 1200x720
bman55 said:
Could you go into more detail please!
GalaXy S ll [blazerV3] @ 1200x720
Click to expand...
Click to collapse
I second this!
Can you go back to STOCK without having to plugin your phone to PC? because my device cannot be recognized!
If you're Hboot 1.50, you need the pc to recognize the phone to use fastboot.
You must use the fastboot command to enter custom recovery correctly to flash kernels/boot.img files that are part of ROMs.
(There is a way to use FlashImage app for the kernel beforehand if the phone will boot to the OS).
You must use the fastboot command to enter custom recovery correctly to format/restore a backup (or the kernel won't get loaded).
You must use the fastboot command to "relock" your phone.
You must "relock" your phone to run the stock RUU.exe's and stock RUU.zip's (PG86IMG.zip).
If you can't get the pc to recognize the phone, try a different PC and especially try SEVERAL usb cables as these tend to go bad.
Additional "Detail" info that may help is in the "guide" in my signature.
Wait where can i get the .zip?
TechnoHacker said:
Wait where can i get the .zip?
Click to expand...
Click to collapse
2.17? See my guide for the links.
Sent from my PG86100 using Tapatalk
Ok, i post it because i think i've read it all and still no fix.
I have 1.5 hboot S-ON HTCUnlocked, custom recovery.
putting the ruu in the SD does not work (unlocked or relocked)
when relocked there is a security warning and the phone doesn't boot, only bootloader.
Stock Rom and htc update just end in the red "!" symbol because i have custom recovery.
I flashed a "stock recovery" i downloaded using fastboot, same problem.
So, does anyone in the same circumstances have succided updating the firmware, antennas, etc?
fcomeba said:
Ok, i post it because i think i've read it all and still no fix.
I have 1.5 hboot S-ON HTCUnlocked, custom recovery.
putting the ruu in the SD does not work (unlocked or relocked)
when relocked there is a security warning and the phone doesn't boot, only bootloader.
Stock Rom and htc update just end in the red "!" symbol because i have custom recovery.
I flashed a "stock recovery" i downloaded using fastboot, same problem.
So, does anyone in the same circumstances have succided updating the firmware, antennas, etc?
Click to expand...
Click to collapse
extract all the .img files from the RUU zip and flash them one by one using fastboot. That should work.
Try to flash in this order (you must be unlocked again): boot, system & userdata. let it boot then access again fastboot and then flash recovery.
lets see what happens.
Thanks
Well I just solve the problem, i expect it help some people in the future.
I had tu relock it again using fastboot oem lock.
download the RUU exe format.
I couldn'y run the OS because relocked and I think the custom roms previously installed by myself messed something so I couldn't start "relocked"
So start the phone in Bootloader (holding down button).
Relock using fastboot oem lock
Once relocked run the RUU app on your computer (It wont read your actual firmware, antennas, etc... just tell you the ones it will update).
Follow the instructions and Voila, your are updated...
So the bottom lines are:
being locked (relocked) no matter what, and run the RUU app because it won't ask for the recovery image installed.
Thanks megabiteg I would like to try your method but my phone is already fixed.
What computer app you talkin about I need to update mine
Sent from my PG86100 using xda premium
search for this
It's like a RUU PC Version.
the one i used was named:
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Google it, i hope you'll find it.
I think WWE_2.17.651.5 is the lastest update, you could also apply an older version, just search for it.
Also follow my instruction, i couldn't get my phone updated with other method
I have directions for both the .exe & zip versions in the guide/flashing notes in my signature. Post 1.5
Sent from my PG86100 using Tapatalk
fcomeba said:
Well I just solve the problem, i expect it help some people in the future.
I had tu relock it again using fastboot oem lock.
download the RUU exe format.
I couldn'y run the OS because relocked and I think the custom roms previously installed by myself messed something so I couldn't start "relocked"
So start the phone in Bootloader (holding down button).
Relock using fastboot oem lock
Once relocked run the RUU app on your computer (It wont read your actual firmware, antennas, etc... just tell you the ones it will update).
Follow the instructions and Voila, your are updated...
So the bottom lines are:
being locked (relocked) no matter what, and run the RUU app because it won't ask for the recovery image installed.
Thanks megabiteg I would like to try your method but my phone is already fixed.
Click to expand...
Click to collapse
I am about to try this because I have been having the exact same problem. I have been trying to update my phone for the past 4 days and I am just about through with trying.
It worked! If any one else needs the .exe here is the link.
goo-inside.me/devs/zanzibar/Shooter/RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed.exe
fcomeba said:
Well I just solve the problem, i expect it help some people in the future.
I had tu relock it again using fastboot oem lock.
download the RUU exe format.
I couldn'y run the OS because relocked and I think the custom roms previously installed by myself messed something so I couldn't start "relocked"
So start the phone in Bootloader (holding down button).
Relock using fastboot oem lock
Once relocked run the RUU app on your computer (It wont read your actual firmware, antennas, etc... just tell you the ones it will update).
Follow the instructions and Voila, your are updated...
So the bottom lines are:
being locked (relocked) no matter what, and run the RUU app because it won't ask for the recovery image installed.
Thanks megabiteg I would like to try your method but my phone is already fixed.
Click to expand...
Click to collapse
There's stickies on this you know.. could've saved yourself a lot of time.
G.Newton said:
There's stickies on this you know.. could've saved yourself a lot of time.
Click to expand...
Click to collapse
Yep, and the guide in my signature that I suggested has links to the stickied threads also.
All, I am sorry I didn't search more, but I am desperate. I go on travel in a few hours.
Long story short, my phone stopped working with 3g, I spent 4-5 hours on phone with sprint trying to fix. THey want it back to the store. It was HTC unlocked with Fresh. I used fastoot to do fastboot OEM lock, the phone rebooted and goes back to the bootloader screen, I can't get it to go back to Android
It says Tampered, Relocked, security warning. Please. Any help. Can I RUU from fastboot?
Yes
As long as you have the boot loader locked you can run the RUU, you can find the RUU in Android Developement.
Hook the phone to your computer, open a command prompt and type "adb reboot recovery" make sure USB debugging is checked. That should get you into TWRP recovery, then go from there.
musicman625 said:
As long as you have the boot loader locked you can run the RUU, you can find the RUU in Android Developement.
Hook the phone to your computer, open a command prompt and type "adb reboot recovery" make sure USB debugging is checked. That should get you into TWRP recovery, then go from there.
Click to expand...
Click to collapse
After relocking the bootloader, I can no longer enter recovery. RUU doesn't seem to want to run because my phone is not up and running (it is already at fastboot prompt). Can I just get it to recognize my phone in fastboot mode somehow?
U need to unlock it again and flash the stock Rom if u relock it with a custom Rom it doesn't allow it to boot
Sent from my EVO using xda premium
adma84 said:
After relocking the bootloader, I can no longer enter recovery. RUU doesn't seem to want to run because my phone is not up and running (it is already at fastboot prompt). Can I just get it to recognize my phone in fastboot mode somehow?
Click to expand...
Click to collapse
As long as you have the proper drivers you should be able to run the RUU from fastboot. While in fastboot if you type 'fastboot devices' (without quotes) is your phone listed?
Sent from my ELTE using Tapatalk 2
dylan6879 said:
U need to unlock it again and flash the stock Rom if u relock it with a custom Rom it doesn't allow it to boot
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Didn't know that was the case. Thanks
crump84 said:
As long as you have the proper drivers you should be able to run the RUU from fastboot. While in fastboot if you type 'fastboot devices' (without quotes) is your phone listed?
Sent from my ELTE using Tapatalk 2
Click to expand...
Click to collapse
RUU is finally running now. Failed several times, and then just started working. I hope it works. Thank you everyone. Will post back
This happened to me as well. The only thing that I did that finally made it work, was to make sure that the path that I performed the fastboot oem lock command in was the path that contained the fastboot file.
When I did this, it would boot into my custom ROM and I was able to run the RUU without any problems.
When I would try to run the RUU from bootloader it would always tell me my battery was low, even though I was over 90%.
Happend to me too . I just ran ruu while in fastboot .
Sent from my EVO using xda premium
Hello,
My amaze 4g is currently running GB with the bullet proof custom rom i found here a couple years ago.
The boot loader is unlocked, and it is S-ON.
I wanted to try and update my phone to an ICS rom such as NRGZ28's energy Rom found here: http://forum.xda-developers.com/showthread.php?t=1362759.
First attempt, I factory reset the phone, cleared cache and cleared dalvik cache and flashed the rom. I chose the option to install it using the stock HTC kernel. The installation went smooth without errors until the final reboot to finalize the installation. The phone gets stuck in the white screen with the green htc logo on it. I recover using Clock Work Mod and everything is back to the old GB setting.
I assume it is because i have an outdated kernel so I go to NRGZ28's thread and download the stock kernel he has posted there. I flashed the kernel using Flash Image GUI apk. This is where the problem happens. After flashing the kernel, the phone is stuck on infinite loop at the above mentioned htc screen.
I flash the energy rom with the newly flashed stock kernel and the phone finally gets past the htc logo screen, but freezes shortly after during the blue animated splash screen and proceeds to repeat this. I can get into boot loader just fine, but am unable to get my phone working again even after a Clock work mod recovery.
please help!!
There is a special process you have to follow when going from GB to ICS, you can't just flash the latest kernel and expect it to work with ICS.
I would do a full wipe/factory reset, then follow the instructions here to upgrade to ICS stock, then you can install whatever ICS ROM you want:
http://forum.xda-developers.com/showpost.php?p=26865752&postcount=27
---------- Post added at 11:33 AM ---------- Previous post was at 11:27 AM ----------
Here is another, possibly more helpful link. It gives step by step instructions, make sure to follow the ones for S=On users (assuming you are S=On).
http://forum.xda-developers.com/showpost.php?p=25215207&postcount=2
I see. Thank you. I will try that right now. I will post an update soon.
o_jake said:
There is a special process you have to follow when going from GB to ICS, you can't just flash the latest kernel and expect it to work with ICS.
I would do a full wipe/factory reset, then follow the instructions here to upgrade to ICS stock, then you can install whatever ICS ROM you want:
http://forum.xda-developers.com/showpost.php?p=26865752&postcount=27
---------- Post added at 11:33 AM ---------- Previous post was at 11:27 AM ----------
Here is another, possibly more helpful link. It gives step by step instructions, make sure to follow the ones for S=On users (assuming you are S=On).
http://forum.xda-developers.com/showpost.php?p=25215207&postcount=2
Click to expand...
Click to collapse
Alright now I'm having a completely unrelated trouble trying to re-lock my bootloader. Yes, I am S-on. I've tried to factory reset but the phone still ends up looping on the htc logo screen. I type in "fastboot oem lock" on sdk but it just hangs at "waiting for device".
DougieJK said:
Alright now I'm having a completely unrelated trouble trying to re-lock my bootloader. Yes, I am S-on. I've tried to factory reset but the phone still ends up looping on the htc logo screen. I type in "fastboot oem lock" on sdk but it just hangs at "waiting for device".
Click to expand...
Click to collapse
Are you able to get into the bootloader, fastboot, or recovery? I'm unsure of which HTC screen you are talking about, if it is the one before trying to boot into Android then I would just ignore it for now. If you're having trouble relocking the bootloader, you might try this toolkit, which includes a tool to relock the bootloader: http://forum.xda-developers.com/showthread.php?t=1493905
All this stuff can probably be found in the HTC Amaze Bible, which you should probably familiarize yourself with before messing around and potentially bricking your phone. http://forum.xda-developers.com/showthread.php?t=1679486
o_jake said:
Are you able to get into the bootloader, fastboot, or recovery? I'm unsure of which HTC screen you are talking about, if it is the one before trying to boot into Android then I would just ignore it for now. If you're having trouble relocking the bootloader, you might try this toolkit, which includes a tool to relock the bootloader: http://forum.xda-developers.com/showthread.php?t=1493905
All this stuff can probably be found in the HTC Amaze Bible, which you should probably familiarize yourself with before messing around and potentially bricking your phone. http://forum.xda-developers.com/showthread.php?t=1679486
Click to expand...
Click to collapse
Yes, it is the screen right before it boots onto your phone's lock screen or main screen. Yes, I can get into the bootloader, fastboot, and the recovery without any problems.
DougieJK said:
Yes, it is the screen right before it boots onto your phone's lock screen or main screen. Yes, I can get into the bootloader, fastboot, and the recovery without any problems.
Click to expand...
Click to collapse
If you can get into the bootloader, fastboot, and recovery, then you should be able to continue the steps and get it working again. Try the Toolkit method of relocking bootloader and continue upgrade to ICS.
o_jake said:
If you can get into the bootloader, fastboot, and recovery, then you should be able to continue the steps and get it working again. Try the Toolkit method of relocking bootloader and continue upgrade to ICS.
Click to expand...
Click to collapse
The all-in-one toolkit is not recognizing my device. Not sure if it's a problem with windows or the toolkit.
Also, it seems the toolkit only works if you are able to actually get to your phone's home screen, which I am unable to do.
So frustrating.....
DougieJK said:
The all-in-one toolkit is not recognizing my device. Not sure if it's a problem with windows or the toolkit.
Also, it seems the toolkit only works if you are able to actually get to your phone's home screen, which I am unable to do.
So frustrating.....
Click to expand...
Click to collapse
Here are some more instructions: http://forum.xda-developers.com/showthread.php?t=1575550&highlight=relock+bootloader
It seems as though the problem is with ADB communicating with your phone. Type in "ADB devices" to see if it is detecting your phone.
Also make sure the file "fastboot.exe" is in the same folder as your ADB file that your command prompt is using.
---------- Post added at 03:12 PM ---------- Previous post was at 03:03 PM ----------
Also are you in bootloader or fastboot when you are trying to do this? I believe you should be in fastboot.
To enter fastboot: Boot into bootloader (hold power and volume down button), scroll down to fastboot, hit the power button.
Now try executing the fastboot command using adb. (remember to make sure fastboot.exe is in same folder as adb)
Alright, so I got it relocked by hooking it up to an old tower. It seems it was an issue with windows not recognizing my phone for some reason.
NOW, there's a new problem. On the bootloader menu, on the top it says "RELOCKED". I choose the recovery option, and it immediately takes me back to the bootloader menu displaying a "Security Warning" message under "RELOCKED".
I am going to cry.:crying:
DougieJK said:
Alright, so I got it relocked by hooking it up to an old tower. It seems it was an issue with windows not recognizing my phone for some reason.
NOW, there's a new problem. On the bootloader menu, on the top it says "RELOCKED". I choose the recovery option, and it immediately takes me back to the bootloader menu displaying a "Security Warning" message under "RELOCKED".
I am going to cry.:crying:
Click to expand...
Click to collapse
This is good... I think. You can now move on to the next step in these instructions: http://forum.xda-developers.com/showthread.php?t=1575550&highlight=relock+bootloader
You have to rename the RUU to what is says in that link, place it on an external SD card, then reboot into bootloader. Then it should automatically install the update (there might be a prompt, just hit yes).
o_jake said:
This is good... I think. You can now move on to the next step in these instructions: http://forum.xda-developers.com/showthread.php?t=1575550&highlight=relock+bootloader
You have to rename the RUU to what is says in that link, place it on an external SD card, then reboot into bootloader. Then it should automatically install the update (there might be a prompt, just hit yes).
Click to expand...
Click to collapse
Yes!!! I finally got it to work! Oh my god thank you so much. Thanks for being so patient with me. I dont know what more i can do do express my gratitude. It just felt amazing to see everything working and falling into place after hours and hours of hopelessness.
So from here on, I assume I just get back onto the boot loader menu, Unlock the boot loader again, then flash the rom I want.
Thank you again.
DougieJK said:
Yes!!! I finally got it to work! Oh my god thank you so much. Thanks for being so patient with me. I dont know what more i can do do express my gratitude. It just felt amazing to see everything working and falling into place after hours and hours of hopelessness.
So from here on, I assume I just get back onto the boot loader menu, Unlock the boot loader again, then flash the rom I want.
Thank you again.
Click to expand...
Click to collapse
You can flash any *ICS* ROM you want. There's another process if you want to go back to GB (though I'm not sure why you would want to).
You should be able to use the Toolkit to unlock the bootloader again, and I would recommend flashing the 4ext recovery while you're at it. From there you should be good!
o_jake said:
You can flash any *ICS* ROM you want. There's another process if you want to go back to GB (though I'm not sure why you would want to).
You should be able to use the Toolkit to unlock the bootloader again, and I would recommend flashing the 4ext recovery while you're at it. From there you should be good!
Click to expand...
Click to collapse
is the 4ext recovery preferred over Clockwork?
DougieJK said:
Alright, so I got it relocked by hooking it up to an old tower. It seems it was an issue with windows not recognizing my phone for some reason.
NOW, there's a new problem. On the bootloader menu, on the top it says "RELOCKED". I choose the recovery option, and it immediately takes me back to the bootloader menu displaying a "Security Warning" message under "RELOCKED".
I am going to cry.:crying:
Click to expand...
Click to collapse
Thats fine now since you are locked you can download the ruu file pertaining to your phone/carrier and put it in the root of your external sd card and boot into the bootloader and it will automatically detect the ruu and start updating. however you must rename the ruu appropriately (depending on which carrier your phone is) for T-Mobile you rename the ruu file ph85img and it detects it automatically. Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
DougieJK said:
is the 4ext recovery preferred over Clockwork?
Click to expand...
Click to collapse
Yeah. You might like it better too.
hatlesssandman said:
Thats fine now since you are locked you can download the ruu file pertaining to your phone/carrier and put it in the root of your external sd card and boot into the bootloader and it will automatically detect the ruu and start updating. however you must rename the ruu appropriately (depending on which carrier your phone is) for T-Mobile you rename the ruu file ph85img and it detects it automatically. Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Yep I was just overreacting. After I renamed the ruu file, everything fell into place and my phone is now functioning with ICS.
So apparently, my phone isn't rooted anymore? is this normal?
Flashed 4ext using the all-in-one tool kit. Nothing happened. Can't run any apps that require root. I'm confused.
Yeah, that's totally normal after flashing an RUU and relocking the bootloader. Just re-root, here's a really easy tool for it: http://theunlockr.com/2012/05/01/how-to-root-htc-amaze-4g/
o_jake said:
Yeah, that's totally normal after flashing an RUU and relocking the bootloader. Just re-root, here's a really easy tool for it: http://theunlockr.com/2012/05/01/how-to-root-htc-amaze-4g/
Click to expand...
Click to collapse
That tool doesn't work for some reason, even though its the tool I used when I first rooted my phone. I just went and did the fastboot flash unlock_code.bin to unlock my phone again.
But for some reason, I can't get 4ext to flash... I went through the steps in the link you provided but my phone doesn't show the app nor am i able to access it through the recovery option from the boot loader menu.
Semi-noob here, would appreciate any help!
S-Off using revone, flashed CWM, and then ROM'd. Found an issue with the phone (wireless charger not working), so need to return to stock before bringing to Verizon. Used adb to S-On, and now, I am STUCK in Fastboot (or is it called Hboot?)!
None of the "options in Fastboot do anything (Bootloader, Reboot, Reboot Bootloader, Factory Reset). I can't get anywhere past Fastboot!
I think my problem was that I did not flash the stock ROM first, before S-on again. The phone no longer goes into Bootloader, so I don't know how to flash a ROM at this point.
Any help would be majorly appreciated! Thank you, oh wise ones...
geeDoh said:
Semi-noob here, would appreciate any help!
S-Off using revone, flashed CWM, and then ROM'd. Found an issue with the phone (wireless charger not working), so need to return to stock before bringing to Verizon. Used adb to S-On, and now, I am STUCK in Fastboot (or is it called Hboot?)!
None of the "options in Fastboot do anything (Bootloader, Reboot, Reboot Bootloader, Factory Reset). I can't get anywhere past Fastboot!
I think my problem was that I did not flash the stock ROM first, before S-on again. The phone no longer goes into Bootloader, so I don't know how to flash a ROM at this point.
Any help would be majorly appreciated! Thank you, oh wise ones...
Click to expand...
Click to collapse
The good news is, if you really are stuck in fastboot, you can still use adb/fastboot commands to get your phone working again. There is an important distinction between fastboot and hboot, though: fastboot is basically the bootloader's "debug" mode, while hboot is the regular bootloader mode. You won't be able to do much if your bootloader says "hboot" above the available options, but if it says "fastboot" or "fastboot usb" you're fine.
You should try to get s-off again (assuming you haven't relocked your bootloader) either via revone or facepalm, then flash a stock rom and proceed from there.
Clarification: if you have relocked your bootloader, unlock, then get s-off.
Used adb to S-On? Meaning what exactly? Did you lock beforehand?
I currently have S-on. I used revone's method to S-off.
I think the problem is that I have relocked the bootloader (phone shows LOCKED) with a custom ROM installed. I think I should have flashed a stock ROM before relocking. Would this have caused the problem I'm having?
I am not sure how to get S-off again, because I am stuck on the FASTBOOT. Selecting Bootloader/Reboot/Reboot Bootloader just returns me to the same screen. When I try to enter any line items (in Terminal), adb says there are no devices connected (this is probably due to the fact that my phone no longer boots to the homescreen). Any suggestions of how to get S-off again??
Thanks...
What method did you use for S-ON? There are guides here that lay out every step needed to return to stock.
Also when in fastboot, you need to use fastboot, not adb. Type in fastboot devices. Does your device ID show?
I would suggest trying to run the RUU. Although it may not work depending on HBOOT version and the fact you are now S-ON.
Can you boot into Recovery? If so, is there a ROM still on the phone? If so, try flashing it...
geeDoh said:
I currently have S-on. I used revone's method to S-off.
I think the problem is that I have relocked the bootloader (phone shows LOCKED) with a custom ROM installed. I think I should have flashed a stock ROM before relocking. Would this have caused the problem I'm having?
I am not sure how to get S-off again, because I am stuck on the FASTBOOT. Selecting Bootloader/Reboot/Reboot Bootloader just returns me to the same screen. When I try to enter any line items (in Terminal), adb says there are no devices connected (this is probably due to the fact that my phone no longer boots to the homescreen). Any suggestions of how to get S-off again??
Thanks...
Click to expand...
Click to collapse
Does the unit show up in device manager? You may need to install a driver.
Phaded said:
What method did you use for S-ON? There are guides here that lay out every step needed to return to stock.
Also when in fastboot, you need to use fastboot, not adb. Type in fastboot devices. Does your device ID show?
I would suggest trying to run the RUU. Although it may not work depending on HBOOT version and the fact you are now S-ON.
Can you boot into Recovery? If so, is there a ROM still on the phone? If so, try flashing it...
Click to expand...
Click to collapse
Oh, using Fastboot gave me my device ID. What can I do now??
I can't get into Recovery from Fastboot USB. The option for Bootloader and Reboot Bootloader are there, but selecting them just returns me to Fastboot USB. I assume this is because I am already S-On again...?
geeDoh said:
Oh, using Fastboot gave me my device ID. What can I do now??
I can't get into Recovery from Fastboot USB. The option for Bootloader and Reboot Bootloader are there, but selecting them just returns me to Fastboot USB. I assume this is because I am already S-On again...?
Click to expand...
Click to collapse
Select bootloader, then recovery. The menus look the same, but they are different.
If you can boot into recovery, what is it? Stock or custom?
Phaded said:
Select bootloader, then recovery. The menus look the same, but they are different.
If you can boot into recovery, what is it? Stock or custom?
Click to expand...
Click to collapse
When I select Bootloader -> Recovery, the HTC screen flashes, then I'm returned to Fastboot USB.
geeDoh said:
When I select Bootloader -> Recovery, the HTC screen flashes, then I'm returned to Fastboot USB.
Click to expand...
Click to collapse
That's because you have unsigned boot.img and/or recovery and relocked the device.
You need to RUU or unlock again to boot to anything.
Any tips on how to unlock again? (and once I am unlocked, i assume I need to load Recovery, and from there, flash a stock ROM?)
geeDoh said:
Any tips on how to unlock again? (and once I am unlocked, i assume I need to load Recovery, and from there, flash a stock ROM?)
Click to expand...
Click to collapse
Run Moonshine.
If that fails, RUU to stock.
You didn't happen to make an unlock_code.bin with htc did you?
No, i didn't. Not even sure what that is...haha...
I'm going to run RUU, and hope that works! Thanks for everyones input...
still no luck! =T
So, I've tried running RUU (this is the RUU file I'm using: RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed), but after it runs for a while (it says it is erasing data, then sending to the phone),
RUU says I am currently on 2.06, so is this the correct RUU file?
Another option for me, other than putting the phone back to stock, is for me to completely brick it. I tried unplugging and powering off the phone while RUU was running, but it still comes back to Fastboot. Suggestions?
Thanks again....
geeDoh said:
So, I've tried running RUU (this is the RUU file I'm using: RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed), but after it runs for a while (it says it is erasing data, then sending to the phone),
RUU says I am currently on 2.06, so is this the correct RUU file?
Another option for me, other than putting the phone back to stock, is for me to completely brick it. I tried unplugging and powering off the phone while RUU was running, but it still comes back to Fastboot. Suggestions?
Thanks again....
Click to expand...
Click to collapse
Just run the RUU. There is only one RUU. You are on 2.06, that's why it tells you that. Let the whole thing run.
You cannot downgrade via RUU. You need to unlock the phone, s-off it (facepalm should suffice) then you can RUU back to 1.15 if you choose.
beaups said:
You cannot downgrade via RUU. You need to unlock the phone, s-off it (facepalm should suffice) then you can RUU back to 1.15 if you choose.
Click to expand...
Click to collapse
Ah forgot he went back to S-On.
Phaded said:
Ah forgot he went back to S-On.
Click to expand...
Click to collapse
I have the same problem. Since it was relocked, the htc dev site can't give the bin file to unlock it again. So I'm stuck in fastboot usb mode and I can't do anything about it. If only I can unlock it again, then I can move on from there.
okyere said:
I have the same problem. Since it was relocked, the htc dev site can't give the bin file to unlock it again. So I'm stuck in fastboot usb mode and I can't do anything about it. If only I can unlock it again, then I can move on from there.
Click to expand...
Click to collapse
Still have the token? Or the email that it got sent in?