I used HTCDEV.COM to unlock my phone, then flashed a custom recovery (i am hboot 1.58 with latest OTA)...the recovery didn't work so I tried flashing a stock recovery back...I do not think that worked. I relocked my phone and it has been working great for about a week. My battery died and now it is acting like this....
I have tried a factory reset, battery pulls, sd card pulls, reboot etc...to no avail
You Tube dot com /watch?v=imJGRGFNSeM
Ok, after charging for awhile and trying factory resets I found that my recovery image doesn't seem to exist...that is probably the problem but I do not know how to fix that...
any help is much appreciated
you tube dot com/watch?v=AC4TZvHWLG8
ICS back up now after battery/sd card pull and reseat....any ideas how i can I fix? My initial goal was to get a custom rom on the phone to live out the rest of my sprint contract in peace and with better battery life - the end result has been, as of now - a headache
Unlock, flash a new recovery image via adb, then flash your rom. I prefer 4EXT recovery. If you are s-on, you'll need that one and you'll need to enable smart flash in the settings menu.
Sent from my SlimRom jb'd EVO 3D.
aqualls said:
Unlock, flash a new recovery image via adb, then flash your rom. I prefer 4EXT recovery. If you are s-on, you'll need that one and you'll need to enable smart flash in the settings menu.
Sent from my SlimRom jb'd EVO 3D.
Click to expand...
Click to collapse
thank you so much for the reply! I tried that initially, now when I attempt to use adb it says "waiting for device" or something, and wont do it for me...
I TRIED THIS AND FAILED
http://forum.xda-developers.com/showthread.php?t=2074181
I have been unable to run any RUU to downgrade the phone, locked or unlocked
it also says when in boot loader PG86.img or whatever doesn't exist or not found
trey41303 said:
it also says when in boot loader PG86.img or whatever doesn't exist or not found
Click to expand...
Click to collapse
Make sure it's on the root of your SD card and renamed PG86IMG.zip exactly.
Sent from my SlimRom jb'd EVO 3D.
---------- Post added at 10:59 PM ---------- Previous post was at 10:52 PM ----------
Try using Ramjet73's guide. May be best to take to scratch and start over.
http://forum.xda-developers.com/showthread.php?t=1889438
Sent from my SlimRom jb'd EVO 3D.
I'm still stuck
aqualls said:
Make sure it's on the root of your SD card and renamed PG86IMG.zip exactly.
Sent from my SlimRom jb'd EVO 3D.
---------- Post added at 10:59 PM ---------- Previous post was at 10:52 PM ----------
Try using Ramjet73's guide. May be best to take to scratch and start over.
http://forum.xda-developers.com/showthread.php?t=1889438
Sent from my SlimRom jb'd EVO 3D.
Click to expand...
Click to collapse
Following Ramjet73 and failing here too
Relocked the phone several days ago. Unlocked tonight, unable to flash a new recovery image, relocked and tried to run the RUU in that guide.
I've attached some supporting pics
Edit: the pictures failed! the RUU utility errored out and said,
"ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct R"OM Update Utility and Try again."
This is bad right? Where it says FAILED (status read failed (unknown error)?
trey41303 said:
This is bad right? Where it says FAILED (status read failed (unknown error)?
Click to expand...
Click to collapse
That's probably not a problem, but are you Sprint or VM?
ramjet73
ramjet73 said:
That's probably not a problem, but are you Sprint or VM?
ramjet73
Click to expand...
Click to collapse
I'm with sprint now. It's like my recovery image doeant exist, isn't accessible, and can't be replaced. I'm still not sure if the pg86img.zip is the same thong as my recovery but it says it doesn't exist when I go to fastbooot
trey41303 said:
I'm with sprint now. It's like my recovery image doeant exist, isn't accessible, and can't be replaced. I'm still not sure if the pg86img.zip is the same thong as my recovery but it says it doesn't exist when I go to fastbooot
Click to expand...
Click to collapse
OK.
I just noticed you said that you took the latest OTA that came out this month. How and when did you do that? Was it after you were already rooted?
You may need to flash another file to downgrade the main version (mainver) before flashing the RUU but you would need to unlock again before doing that.
ramjet73
ramjet73 said:
OK.
I just noticed you said that you took the latest OTA that came out this month. How and when did you do that? Was it after you were already rooted?
You may need to flash another file to downgrade the main version (mainver) before flashing the RUU but you would need to unlock again before doing that.
ramjet73
Click to expand...
Click to collapse
Took the OTA update the day before I tried the HTCDEV unlock and flashed arecovery IMG over I tried several of them to no avail and it never booted to recovery after that so I just set up the phone and moved on...
trey41303 said:
Took the OTA update the day before I tried the HTCDEV unlock and moved a recovery IMF over. It never booted to recovery after that so I set up the phone and moved on...
Click to expand...
Click to collapse
OK, you'll need to start by unlocking the phone again and then we'll get your recovery installed so you can flash the zip file and RUU.
Can you verify that you can get into "fastboot usb" mode and do the HTC unlock with the same .bin file again?
ramjet73
ramjet73 said:
OK, you'll need to start by unlocking the phone again and then we'll get your recovery installed so you can flash the zip file and RUU.
Can you verify that you can get into "fastboot usb" mode and do the HTC unlock with the same .bin file again?
ramjet73
Click to expand...
Click to collapse
I can do that. Sorry for the slow responses. I joined in 2010 when I got my Hero, but never had trouble rooting and modding it just following the posts. The forum is still making me wait 5 minutes between posts
Pull battery
Replace
Vol Dow + power
When menu comes up press power
Plug phone into computer
Cd c:/android
Fastboot flash unlocktolken Unlock_code.bin
Move the thing on the phone to unlock then select it with the power button...then.....
That's where I get fuzzy
trey41303 said:
I can do that. Sorry for the slow responses. I joined in 2010 when I got my Hero, but never had trouble rooting and modding it just following the posts. The forum is still making me wait 5 minutes between posts
Pull battery
Replace
Vol Dow + power
When menu comes up press power
Plug phone into computer
Cd c:/android
Fastboot flash unlocktolken Unlock_code.bin
Move the thing on the phone to unlock then select it with the power button...then.....
That's where I get fuzzy
Click to expand...
Click to collapse
So you did all of that already?
If so you are ready to flash the recovery. If you have a recovery.img file in the same directory as your ADB/fastboot, put the phone back into "fastboot USB" mode and issue the following commands:
fastboot flash recovery recovery.img
fastboot boot recovery.img
The second command should put you into the recovery.
ramjet73
ramjet73 said:
So you did all of that already?
If so you are ready to flash the recovery. If you have a recovery.img file in the same directory as your ADB/fastboot, put the phone back into "fastboot USB" mode and issue the following commands:
fastboot flash recovery recovery.img
fastboot boot recovery.img
The second command should put you into the recovery.
ramjet73
Click to expand...
Click to collapse
Ok, which recovery should I be using? People say to use 4ext, but I have yet to find that
trey41303 said:
Ok, which recovery should I be using? People say to use 4ext, but I have yet to find that
Click to expand...
Click to collapse
Yea, I'd recommend 4EXT. You can download it from here, then put in your ADB/fastboot directory and rename it to "recovery.img".
ramjet73
ramjet73 said:
Yea, I'd recommend 4EXT. You can download it from here, then put in your ADB/fastboot directory and rename it to "recovery.img".
ramjet73
Click to expand...
Click to collapse
got 4EXT thank you, renamed it recovery.img, placed in my c:/android
tried to fastboot flash and get this response....im face palming here
Phones eye view
Here is my phone in boot loader mode as of now
And the screen showing its unlocked
Did you see the previous pic...seems something is wrong....I am trying to find the instructions I was using to flash a new rom when I found that the initial recovery img didn't work
Seems it said if your "s-off"...do this to flash a new rom, or do this to flash a rom and permanently root/place recovery I g on phone. And I did the latter
Related
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.
I've been trying to root my EVO 4G LTE using various guides from this board, and I'm not having a lot of luck. I have HBOOT 2.09 and it's S-ON. It seems like the easiest way to root the device is to go S-OFF, but then it appears that the device needs to be rooted to get S-OFF. So I'm a little confused at this point. I've unlocked the bootloader and installed TWRP, but when I try to install the SuperSU root utility it gives me an error about mounting partitions and fails. My bootloader screen also displays "TAMPERED" which seems to be a problem but I'm not having a lot of luck finding a way to resolve it.
So... can anyone tell me what my next step is?
Thanks in advance.
Are you using Facepalm, Moonshine, or DirtyRacun? You haven't really provided enough details to help, at this point. What's your software version? I assume you're running the stock ROM?
I was running the stock ROM, I think it was 3.16. I tried using Facepalm but again it seems like it needs root to work which I haven't been able to achieve just yet. I tried installing the ROM from this thread through TWRP but it just hangs on the HTC screen so I'm not sure what's on there now. I can still get into the bootloader and recovery though.
You can't use Facepalm on 3.16 software. Use Moonshine.
Try flashing this stock rooted to get back to a working state: http://d-h.st/users/Captain_Throwback/?fld_id=10308#files
You may need to fastboot flash the boot.img to make sure it fully boots.
OK, I downloaded that ROM and extracted the boot.img. I booted the phone into the bootloader and ran "fastboot flash boot boot.img". It seems to have completed correctly, no errors at least, but now the phone just sits at the HTC screen with the red text at the bottom. Clearly I'm doing something wrong...
Did you flash the ROM too? Or did it reboot on you when you tried?
I just did the boot.img. Should I also do "fastboot flash zip 3.16.651.3_stock_rooted_odex_CPTB.zip"?
davel23 said:
I just did the boot.img. Should I also do "fastboot flash zip 3.16.651.3_stock_rooted_odex_CPTB.zip"?
Click to expand...
Click to collapse
You have to flash the ROM in recovery.
Ok, so I went into recovery which is still TWRP, adb pushed that ROM to the phone then tried to install it. It gives a bunch of error messages about being unable to mount various items, says it's unable to find path for partition [name of the zip] and fails.
Thanks for your help and patience so far...
You do not extract the file, leave it as a zip and do not open it. Move it to your SD card while in fastboot (mount sd) and from there use twrp and select the correct zip to flash. But above all... DO NOT EXTRACT THE FILR
Sent from my EVO using xda app-developers app
roscoepcoltra said:
You do not extract the file, leave it as a zip and do not open it. Move it to your SD card while in fastboot (mount sd) and from there use twrp and select the correct zip to flash. But above all... DO NOT EXTRACT THE FILR
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
He's S-on. He can't flash kernels from recovery with Hboot 2.09.
davel23 said:
Ok, so I went into recovery which is still TWRP, adb pushed that ROM to the phone then tried to install it. It gives a bunch of error messages about being unable to mount various items, says it's unable to find path for partition [name of the zip] and fails.
Thanks for your help and patience so far...
Click to expand...
Click to collapse
I don't understand what you're doing here. Boot to recovery, mount storage, copy the ROM zip over, and then flash it.
Ok, so I mounted storage from recovery, or least I tried to, my PC said it needed to be formatted. So I did so, copied the file over and flashed it which completed successfully this time. My phone now boots properly, I'll give Moonshine a try now. Hopefully I won't need to bug you again, thanks for all the help.
Captain_Throwback said:
You can't use Facepalm on 3.16 software. Use Moonshine.
Try flashing this stock rooted to get back to a working state: http://d-h.st/users/Captain_Throwback/?fld_id=10308#files
You may need to fastboot flash the boot.img to make sure it fully boots.
Click to expand...
Click to collapse
my friend wants to buy im rooted unlocked evo. it is on viper now can I flash this an it will be stock rooted ?
Tigerstown said:
my friend wants to buy im rooted unlocked evo. it is on viper now can I flash this an it will be stock rooted ?
Click to expand...
Click to collapse
Yes.
Captain_Throwback said:
Yes.
Click to expand...
Click to collapse
S-on Ok? Or do I need to moonshine first?
Tigerstown said:
S-on Ok? Or do I need to moonshine first?
Click to expand...
Click to collapse
You need to use Flash Image GUI or fastboot flash the kernel.
FinZ28 said:
You need to use Flash Image GUI or fastboot flash the kernel.
Click to expand...
Click to collapse
Ok I got that app I use that. An for my other one I'm selling is s-off so I can just flash this on that one..it's been fun on the Evo with the helpful fellow xda's on the jewel. But the wife's work now cover half your bill if you have verizon so we had no choice
Captain_Throwback said:
Yes.
Click to expand...
Click to collapse
Omg I just moonshine(easy thing I ever did) this phone my wife didn't want s-off before. So now I'm s-off I will just flash thanks once again throwback. Hope there is someone in vzw htc one thread that breaks down firmware like you.
Sent from my EVO using XDA Premium 4 mobile app
I'm having a little trouble with Moonshine. It reboots the phone a couple of times, gets to step 3 then just keeps printing periods in the program window. I've been reading through the Moonshine thread and it seems other people have had the same problem, but I haven't seen a solid fix yet. Anyone know what I need to do or should I stick with the Moonshine thread?
Hello,
I was recently given a bootlooping Evo 4G Lte. I have been trying to figure out how to get this thing out of a bootloop and havent been able to do it. I, unfortunately, have no history on what happened to this device. Currently, it bootloops on the "Mean Bean" loading screen but will go no further. I can get into the bootloader, which says it is Unlocked, S-On, but I am unable to boot it into a recovery, it just returns back to bootloader. I have tried fastbooting twrp, but it fails (remote: image update error), and I have tried fastbooting the Mean Bean kernel thinking maybe thats all it needs, but that failed as well. Anybody have an insight? Much appreciated! Thanks.
Mike
I would run the 3.17 RUU. Hit the top link in my sig and look at the last post in the thread. You can run it from the bootloader. You'll need to re-root afterwards but it should get your phone back in working condition.
Sent from my HTC EVO 4G LTE
FinZ28 said:
I would run the 3.17 RUU. Hit the top link in my sig and look at the last post in the thread. You can run it from the bootloader. You'll need to re-root afterwards but it should get your phone back in working condition.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Thanks for the quick reply. I downloaded the RUU and ran it. However it sits and says "Waiting for bootloader" then errors out with "USB connection issue". The usb is working. The reason I never ran the RUU in teh first place was because i thought i read that you cant RUU with and unlocked bootloader. Is that not true? or is that my problem?
Mike
Not 100% sure but I will check with someone who used this tool recently and see if they were still unlocked at the time. Were you connected via Fastboot USB? Sounds more like a driver issue.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Shouldn't matter. I know of a couple of users who were having phone issues and had unlocked bootloaders when they ran this tool. Were you connected via Fastboot USB? Sounds more like a driver issue.
Click to expand...
Click to collapse
Yeah I was connected and it said fastboot USB. It said rebooting to bootloader and rebooted, still said fastboot USB. Then it sat at a screen that said "waiting for bootloader" and after a while error ed out.
You can try relocking. You just need to run the command "fastboot oem relock" from a command line while connected via fastboot USB mode.
Sent from my HTC EVO 4G LTE
FinZ28 said:
You can try relocking. You just need to run the command "fastboot oem relock" from a command line while connected via fastboot USB mode.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I have since tried relocking to see if that was it, and it did the same thing.
Mike
Hopefully @YoFayce can shed some light on the matter since he recently used this on his phone.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Hopefully @YoFayce can shed some light on the matter since he recently used this on his phone.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
crazymike1234 said:
I have since tried relocking to see if that was it, and it did the same thing.
Mike
Click to expand...
Click to collapse
you can use the stock RUU and you can leave the bootloader unlocked as it will not affect anything.. it will fix your looping problem (Amongst others) as in gps not working ect.. once your done you will need to fastboot over your TWRP and from there mod as normal Good Luck! and ill be watching if you need any help!
YoFayce said:
you can use the stock RUU and you can leave the bootloader unlocked as it will not affect anything.. it will fix your looping problem (Amongst others) as in gps not working ect.. once your done you will need to fastboot over your TWRP and from there mod as normal Good Luck! and ill be watching if you need any help!
Click to expand...
Click to collapse
Problem is the ruu keeps error in out. I am beginning to think it may still be a driver problem. Someday I will get this done!
Mike
crazymike1234 said:
Problem is the ruu keeps error in out. I am beginning to think it may still be a driver problem. Someday I will get this done!
Mike
Click to expand...
Click to collapse
When in doubt update your android SDK remove the htc drivers reboot install drivers reboot and you should be good to go! Check the integrity of your USB cable and if possible use a rear USB port (More Power) Painful process yes but well worth it.. HTC drivers act strange till you reboot OOOh and make sure your using the proper HTC drivers for windows 32 bit or 64 bit!
YoFayce said:
When in doubt update your android SDK remove the htc drivers reboot install drivers reboot and you should be good to go! Check the integrity of your USB cable and if possible use a rear USB port (More Power) Painful process yes but well worth it.. HTC drivers act strange till you reboot OOOh and make sure your using the proper HTC drivers for windows 32 bit or 64 bit!
Click to expand...
Click to collapse
The drivers seem to be ok, but I am still not able to get any further. The RUU finds my phone, then reboots again to bootloader, but it just sits there saying "Waiting for bootloader" until it errors out due to "USB Connection error". I have tried a few different cables, and different USB ports. Not sure what the problem is but it just wont go any further. I re-unlocked my bootloader with htcdev. I have tried fastbooting a recovery to the phone but it errors out. I just cant get anything to work so I can boot anything. I really just want to get something working...anything! Any other ideas? Thanks.
Mike
use an sd card put a recovery image on the root of the sd boot into bootloader apply the recovery you should then have a recovery if you did it right, go into twrp mount device add a rom flash in recovery viola.
Sinistertensai said:
use an sd card put a recovery image on the root of the sd boot into bootloader apply the recovery you should then have a recovery if you did it right, go into twrp mount device add a rom flash in recovery viola.
Click to expand...
Click to collapse
Sinister,
Thanks for the reply. I put TWRP on the sdcard (named PJ75IMG, right?) and tried to apply that when I rebooted to recovery last night and it failed. It tries to load it but gives a few errors quick (No Image) Did I do it wrong?
Mike
crazymike1234 said:
Sinister,
Thanks for the reply. I put TWRP on the sdcard (named PJ75IMG, right?) and tried to apply that when I rebooted to recovery last night and it failed. It tries to load it but gives a few errors quick (No Image) Did I do it wrong?
Mike
Click to expand...
Click to collapse
make sure the file is just the PJ75IMG no additional text and it should be .zip If I recall correctly. make sure its on the root of the sdcard not internal but sd or external and it should be at the top level e.g. sdcard/ make sure its not in any other folders after you do that hold power and vol down get to hboot screen itll scan and then just follow the instructions.
Sinistertensai said:
make sure the file is just the PJ75IMG no additional text and it should be .zip If I recall correctly. make sure its on the root of the sdcard not internal but sd or external and it should be at the top level e.g. sdcard/ make sure its not in any other folders after you do that hold power and vol down get to hboot screen itll scan and then just follow the instructions.
Click to expand...
Click to collapse
Thats exactly what I did. It is the only thing on the sdcard. It says no gift file, Loading, no image for 4 different things. Then returns to the bootloader.
Mike
crazymike1234 said:
Thats exactly what I did. It is the only thing on the sdcard. It says no gift file, Loading, no image for 4 different things. Then returns to the bootloader.
Mike
Click to expand...
Click to collapse
zip files probably corrupt then. download another do the same process make sure you've got a good file use md5 checks
Sinistertensai said:
zip files probably corrupt then. download another do the same process make sure you've got a good file use md5 checks
Click to expand...
Click to collapse
Hmmm, Ill try download again. I got it from the main TWRP site.
crazymike1234 said:
Hmmm, Ill try download again. I got it from the main TWRP site.
Click to expand...
Click to collapse
careful on the vol down press you might be holding it too long and its canceling the update.
Sinistertensai said:
careful on the vol down press you might be holding it too long and its canceling the update.
Click to expand...
Click to collapse
Well, which recovery file should I be using? When I use the main TWRP ones (ie openrecovery-twrp-2.6.0.0-jewel.img) it gives me the errors like I said above. I now see they have a few labeled like this PJ75IMG-twrp-2.3.1.0-jewel.zip. When I use these, it tries to continue but says "Main Version Is Older. FAILED"
So...I was showing someone at work today how to install custom recovery in goomanager. I wasn't paying attention, went to far & it started to download twrp. I was running a newer version 2.6.3.0 so I tried to cancel the download. Well, that's when my problem started. I rebooted my phone into recovery so I could show him what twrp could do & it was gone. The phone would boot to the splash screen & hang for a few. It would then reboot again back to the splash screen & continue until the phone was back up & running. If I reboot into the bootloader it still says I'm unlocked & s-off. I'm also still rooted. I've tried all the options...fastboot, terminal emulator/adb shell, the PJ75IMG.zip in bootloader, & again thru goomanager. I just can't get it to reinstall. Everything else on the phone works fine. I can connect to my cpu & view all the files on internal storage & the sd card. I'm running Meanbean on hboot 1.19 & baseband 1.12.11.1210.
So what are my options??? I'm not above doing a complete factory reset if needed. Obviously, I'd like to do this without having to start over from scratch if possible.
TIA
buddahj said:
So...I was showing someone at work today how to install custom recovery in goomanager. I wasn't paying attention, went to far & it started to download twrp. I was running a newer version 2.6.3.0 so I tried to cancel the download. Well, that's when my problem started. I rebooted my phone into recovery so I could show him what twrp could do & it was gone. The phone would boot to the splash screen & hang for a few. It would then reboot again back to the splash screen & continue until the phone was back up & running. If I reboot into the bootloader it still says I'm unlocked & s-off. I'm also still rooted. I've tried all the options...fastboot, terminal emulator/adb shell, the PJ75IMG.zip in bootloader, & again thru goomanager. I just can't get it to reinstall. Everything else on the phone works fine. I can connect to my cpu & view all the files on internal storage & the sd card. I'm running Meanbean on hboot 1.19 & baseband 1.12.11.1210.
So what are my options??? I'm not above doing a complete factory reset if needed. Obviously, I'd like to do this without having to start over from scratch if possible.
TIA
Click to expand...
Click to collapse
Open a cmd window from your PC>platform tools folder
Boot into bootloader>fastbootusb
Type fastboot erase cache
Re-Flash twrp > fastboot flash recovery recoverymane.img
Hopefully that will fix your issue
BD619 said:
Open a cmd window from your PC>platform tools folder
Boot into bootloader>fastbootusb
Type fastboot erase cache
Re-Flash twrp > fastboot flash recovery recoverymane.img
Hopefully that will fix your issue
Click to expand...
Click to collapse
I tried it & unfortunately it didn't work. It's still doing the same thing.
After typing in the command: fastboot erase cache
erasing 'cache'...
OKAY [ 0.109s]
finished. total time: 0.109s
After typing in the command: fastboot flash recovery recovery.img
error: cannot load recovery.img' : Unknown error
buddahj said:
I tried it & unfortunately it didn't work. It's still doing the same thing.
After typing in the command: fastboot erase cache
erasing 'cache'...
OKAY [ 0.109s]
finished. total time: 0.109s
After typing in the command: fastboot flash recovery recovery.img
error: cannot load recovery.img' : Unknown error
Click to expand...
Click to collapse
Is the recovery.img file in the folder you are using to run the commands?
BD619 said:
Is the recovery.img file in the folder you are using to run the commands?
Click to expand...
Click to collapse
Yes, it's in the platform-tools folder.
Something else that just happened. I went into Nandroid Manager to see if it would say what recovery I'm running...if any. It said: Detected Recovery: Unknown Click to fix! When I clicked it I got this message.
"It looks like the file last_log at /cache/recovery/last_log does not exist! This file is required to detect installed recovery. To fix this problem please reboot into your recovery then reboot back to system!
What about flashing recovery via Nandroid Manager? I'm a little reluctant to do this since they warn it can brick your phone.
Odd. If you can't get recovery reinstalled I would RUU and go from there. You can use the 3.17 RUU and you'll retain S-off. You'll need to unlock your bootloader, install recovery and flash a ROM once it completes. Might be your best option.
Sent from my HTC EVO 4G LTE
buddahj said:
Yes, it's in the platform-tools folder.
Something else that just happened. I went into Nandroid Manager to see if it would say what recovery I'm running...if any. It said: Detected Recovery: Unknown Click to fix! When I clicked it I got this message.
"It looks like the file last_log at /cache/recovery/last_log does not exist! This file is required to detect installed recovery. To fix this problem please reboot into your recovery then reboot back to system!
What about flashing recovery via Nandroid Manager? I'm a little reluctant to do this since they warn it can brick your phone.
Click to expand...
Click to collapse
I have never heard of Nandroid Manager so can't really answer.
Are you sure everything is spelled correctly in the command?
FinZ28 said:
Odd. If you can't get recovery reinstalled I would RUU and go from there. You can use the 3.17 RUU and you'll retain S-off. You'll need to unlock your bootloader, install recovery and flash a ROM once it completes. Might be your best option.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
If I RUU, what's my best option for unlocking the bootloader? Can you still use HTC dev?
BD619 said:
Are you sure everything is spelled correctly in the command?
Click to expand...
Click to collapse
yes
buddahj said:
If I RUU, what's my best option for unlocking the bootloader? Can you still use HTC dev?
Click to expand...
Click to collapse
Yep.
Sent from my HTC EVO 4G LTE
If I use the 3.17 RUU will it change my hboot? Not that it matters, just curious. You don't happen to have a link for the 3.17 ruu do you? Any thoughts on the viperuu?
buddahj said:
If I use the 3.17 RUU will it change my hboot? Not that it matters, just curious. You don't happen to have a link for the 3.17 ruu do you? Any thoughts on the viperuu?
Click to expand...
Click to collapse
Yep, you'll have the newest Hboot. Doesn't really matter since you're S-off. Hit the top link in my sig and go to the bottom of the first post.
Sent from my HTC EVO 4G LTE
buddahj said:
If I use the 3.17 RUU will it change my hboot? Not that it matters, just curious. You don't happen to have a link for the 3.17 ruu do you? Any thoughts on the viperuu?
Click to expand...
Click to collapse
http://www.htc.com/us/support/htc-evo-4g-lte-sprint/news/
Same hboot as far as I know.
If you are running Moonshine or Rumrunner hboot it may overwrite it but you can just re-flash the hboot again
:good::good: Thanks for the help guys. This looks like something I'll tackle on my next day off. Lol, the way my luck's been running lately this may not go as smoothly as it should.
FinZ28 said:
Yep, you'll have the newest Hboot. Doesn't really matter since you're S-off. Hit the top link in my sig and go to the bottom of the first post.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
He's on 1.19 so it'll update to 2.09. As far as VipeRUU, I don't have an opinion on it. I've used it previously on a phone that had a borked recovery partition and it worked just fine. It's really a matter of personal preference.
Sent from my HTC EVO 4G LTE
---------- Post added at 08:19 PM ---------- Previous post was at 08:16 PM ----------
buddahj said:
:good::good: Thanks for the help guys. This looks like something I'll tackle on my next day off. Lol, the way my luck's been running lately this may not go as smoothly as it should.
Click to expand...
Click to collapse
I ran the 3.17 RUU on my phone the other night just for the heck of it. It takes about ten minutes from start to finish but it's pretty painless.
Sent from my HTC EVO 4G LTE
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
Just curious. When you were showing how to install recovery, how did you go about doing it?
Sent from my HTC EVO 4G LTE
FinZ28 said:
He's on 1.19 so it'll update to 2.09. As far as VipeRUU, I don't have an opinion on it. I've used it previously on a phone that had a borked recovery partition and it worked just fine. It's really a matter of personal preference.
Sent from my HTC EVO 4G LTE
Just curious. When you were showing how to install recovery, how did you go about doing it?
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I was in the goomanager app showing him how you could use it to install open script recovery & accidentally started to download it.
I tried to run the 3.17 Ruu & got an error [158]: image error
It says: The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility & try again.
buddahj said:
I tried to run the 3.17 Ruu & got an error [158]: image error
It says: The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility & try again.
Click to expand...
Click to collapse
Try a different USB port USB2 work the best
BD619 said:
Try a different USB port USB2 work the best
Click to expand...
Click to collapse
I am using USB 2.0. I'll try on my laptop later & update then.
I ended up running the viperuu. I'm now back to being unlocked/rooted with twrp. What a pain in my arse.
Thanks again guys!!!
Hello. I'm having trouble with my HTC Rezound. I had CWM and Clean Rom was running fine but I tried to switch to Venasaur so I could use it on Straight Talk. I had an unlocked boot loader and everything worked before I tried flashing the new rom. Now, My phone won't even turn off unless it's dead.The bootloader says relocked, and it just keeps putting itself in fast boot whether I power it on or not.It says security warning under tampered and relocked. Can anybody please help me out? It would be much appreciated!
Cap'n Jazz said:
Hello. I'm having trouble with my HTC Rezound. I had CWM and Clean Rom was running fine but I tried to switch to Venasaur so I could use it on Straight Talk. I had an unlocked boot loader and everything worked before I tried flashing the new rom. Now, My phone won't even turn off unless it's dead.The bootloader says relocked, and it just keeps putting itself in fast boot whether I power it on or not.It says security warning under tampered and relocked. Can anybody please help me out? It would be much appreciated!
Click to expand...
Click to collapse
Did you try to unlock again and fastboot flash the proper boot.img?
acejavelin said:
Did you try to unlock again and fastboot flash the proper boot.img?
Click to expand...
Click to collapse
No matter how many times I go through the bootloader unlock screen it still says RELOCKED in fastboot.
Cap'n Jazz said:
No matter how many times I go through the bootloader unlock screen it still says RELOCKED in fastboot.
Click to expand...
Click to collapse
Wait... so you get (or have) the unlock token, and push it to the phone via fastboot and it won't unlock? Not to question your abilities, but are you sure your doing it right?
Your using "fastboot flash unlocktoken Unlock_code.bin" and then accepting the terms on the screen of the phone, and it is not unlocking?
acejavelin said:
Wait... so you get (or have) the unlock token, and push it to the phone via fastboot and it won't unlock? Not to question your abilities, but are you sure your doing it right?
Your using "fastboot flash unlocktoken Unlock_code.bin" and then accepting the terms on the screen of the phone, and it is not unlocking?
Click to expand...
Click to collapse
No offense taken! I'm here for help after all, haha. But yes, I have the unlock code.bin, type that into a CMD run from he sdk folder, get the accept screen on the phone, accept and it still says relocked. I dunno what I'm doing wrong, or if the phone is just screwed..
Hmmm... weird, so it must be accepting the token if it is prompting you on the phone to accept the terms on the phones. Guess I have never been in this position where it wouldn't unlock. Did you try going through the entire process on the HTCdev.com again from start to finish? Other than that, I would have to differ this to someone with a little more "hacking" knowledge on the Rezound, like @REV3NT3CH
I hate to say it, but if it won't unlock again, that is bad... really bad, like might be bricked and require a JTAG bad.
Cap'n Jazz said:
No offense taken! I'm here for help after all, haha. But yes, I have the unlock code.bin, type that into a CMD run from he sdk folder, get the accept screen on the phone, accept and it still says relocked. I dunno what I'm doing wrong, or if the phone is just screwed..
Click to expand...
Click to collapse
yes try getting a new unlock.bin...each unlock.bin differs from phone to phone also...for example say you had 2 rezounds...one unlock.bin from one rezound will not work on another
REV3NT3CH said:
yes try getting a new unlock.bin...each unlock.bin differs from phone to phone also...for example say you had 2 rezounds...one unlock.bin from one rezound will not work on another
Click to expand...
Click to collapse
Well I guess I have a paperweight now.. I got a new unlock.bin and it still says relocked :/. Thanks for the help, guys.
[EDIT] It unlocked! I'm not sure why it finally worked! So what do I do from here? I just need to flash the boot.img?
Cap'n Jazz said:
Well I guess I have a paperweight now.. I got a new unlock.bin and it still says relocked :/. Thanks for the help, guys.
[EDIT] It unlocked! I'm not sure why it finally worked! So what do I do from here? I just need to flash the boot.img?
Click to expand...
Click to collapse
Download ROM and TWRP 2.6.3.0
fastboot flash recovery recovery.img
fastboot boot recovery.img
flash rom in TWRP
S-OFF with rumrunner (just to be safe for the future)
acejavelin said:
Download ROM and TWRP 2.6.3.0
fastboot flash recovery recovery.img
fastboot boot recovery.img
flash rom in TWRP
S-OFF with rumrunner (just to be safe for the future)
Click to expand...
Click to collapse
I don't see the rezound in the list of supported devices on the TWRP website?
Cap'n Jazz said:
I don't see the rezound in the list of supported devices on the TWRP website?
Click to expand...
Click to collapse
Rezound is Verizon's name... to the rest of the world and HTC it is called the vigor
Or it's here: http://forum.xda-developers.com/showthread.php?t=1902381
acejavelin said:
Rezound is Verizon's name... to the rest of the world and HTC it is called the vigor
Or it's here: http://forum.xda-developers.com/showthread.php?t=1902381
Click to expand...
Click to collapse
Ah, I see. Thank you for the link. I got TWRP recovery up, but when I try to flash the Venasaur ROM it says failed each time..
Cap'n Jazz said:
Ah, I see. Thank you for the link. I got TWRP recovery up, but when I try to flash the Venasaur ROM it says failed each time..
Click to expand...
Click to collapse
Why Venasaur, it is very old and unsupported for almost 2 years... I would recommend Evervolv (KitKat 4.4.2), Tachyon (4.3 Jellybean), or EclipticRez Revamped v9 (Sense ICS), all are stable and have support.
acejavelin said:
Why Venasaur, it is very old and unsupported for almost 2 years... I would recommend Evervolv (KitKat 4.4.2), Tachyon (4.3 Jellybean), or EclipticRez Revamped v9 (Sense ICS), all are stable and have support.
Click to expand...
Click to collapse
I was looking for a rom that would let me use this phone with Straight Talk. Would any of those work for that?
Tachyon fails too.
Cap'n Jazz said:
I was looking for a rom that would let me use this phone with Straight Talk. Would any of those work for that?
Tachyon fails too.
Click to expand...
Click to collapse
Evervolv should work with a GSM SIM, Edge only, you need to flash the GSM patch for Evervolv though.
What error is it giving you?
EDIT: I don't see any reference to Straight Talk in the Venasaur thread.
Venasaur uses an older update-binary thats now incompatible with the newer builds of TWRP. The fix, flash it twice. I recommend using TWRP 2.5.0.0 for ICS/GB roms, latest for JB/KK.
acejavelin said:
Evervolv should work with a GSM SIM, Edge only, you need to flash the GSM patch for Evervolv though.
What error is it giving you?
EDIT: I don't see any reference to Straight Talk in the Venasaur thread.
Click to expand...
Click to collapse
It just says "E: Unable to open zip file.
Error flashing zip '/sdcard/TACHYON- 1.2.zip'" And Failed in red above the Home button.
Cap'n Jazz said:
It just says "E: Unable to open zip file.
Error flashing zip '/sdcard/TACHYON- 1.2.zip'" And Failed in red above the Home button.
Click to expand...
Click to collapse
Are you copying the ROM file to the external SD card?
You will probably need to do a complete wipe of the phone except external SD card in the Wipe->Advanced menu, I usually do it at least twice. Then go to the Mounts, select external SD and Mount, it should allow you to get to the SD card with your PC via USB, copy the ROM ZIP file over and go back home and Install and browse to the ZIP and flash.
acejavelin said:
Are you copying the ROM file to the external SD card?
You will probably need to do a complete wipe of the phone except external SD card in the Wipe->Advanced menu, I usually do it at least twice. Then go to the Mounts, select external SD and Mount, it should allow you to get to the SD card with your PC via USB, copy the ROM ZIP file over and go back home and Install and browse to the ZIP and flash.
Click to expand...
Click to collapse
I had been using another phone to put the ROM zip on the external SD card. It finally said it installed Evervolv, but when I boot up it just black screens now :/
[EDIT] Now when I try to wipe it says: "E: Unable to mount '/emmc' E: Unable to mount '/emmc' E: Unable to mount internal storage"
Cap'n Jazz said:
I had been using another phone to put the ROM zip on the external SD card. It finally said it installed Evervolv, but when I boot up it just black screens now :/
Click to expand...
Click to collapse
How did you start TWRP, from the phone or via "fastboot boot" command? If you started TWRP from the phone, you need to flash the boot.img manually.