Lost Radio - Sprint HTC EVO 4G LTE

I have a new HTC Evo LTE and HBOOT 1.15.000 Radio 1.05.11.0606and do not have S-OFF.
I installed Fresh 5.2.1 and had problems, when back and did a wipe including system and installed 5.2.1 again and it didn't work. After doing that I went back, wiped system again, and then restored the backup I previously made. Now the backup sometimes loads, sometimes doesn't, but even when it does I have no radio. I am going to try to install a stock rom through recovery or fresh 5.1.1 and HOPE I get radio back.
Any other suggestions of what I could do?

jeggen said:
I have a new HTC Evo LTE and HBOOT 1.15.000 Radio 1.05.11.0606and do not have S-OFF.
I installed Fresh 5.2.1 and had problems, when back and did a wipe including system and installed 5.2.1 again and it didn't work. After doing that I went back, wiped system again, and then restored the backup I previously made. Now the backup sometimes loads, sometimes doesn't, but even when it does I have no radio. I am going to try to install a stock rom through recovery or fresh 5.1.1 and HOPE I get radio back.
Any other suggestions of what I could do?
Click to expand...
Click to collapse
So now I'm just in a boot loop. I relocked, installed stock recovery and ran RUU. When I did that I booted just long enough that I could almost slide the ring to unlock before I rebooted. Then the device just constantly reboots.
I unlocked again, installed TWRP 2.2.2.0 in case there was a bug causing flashing issues. Recovery boots just fine now. I flashed Stock Rooted DeOdexed 1.22.651.3 from here since that was the version I had before this whole fiasco. I'm going to try to restore backup again but don't know how to get out of this horrible mess. Worse part about it is that it's my wife's phone! Help please!

You might need to run a different RUU. I'm not too experienced with that kind of issue though.
"We're coming from a pure power source"

metalfan78 said:
You might need to run a different RUU. I'm not too experienced with that kind of issue though.
"We're coming from a pure power source"
Click to expand...
Click to collapse
I reflashed stock recovery, relocked bootloader (fastboot oem lock), ran RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.22.651.3_Radio_1. 05.11.0606_NV_SPCS_2.45_003_release_268323_signed. exe), and still had the boot loop problem. RUU said it completed but the bootloader still said "relocked". Isn't RUU supposed to totally wipe and restore the entire device?
I recall on my old EVO there was a zip you could place in the SDcard that the bootloader automatically looked for and would use to reflash to factory everything. Is there a way to do this with the EVO 4g LTE?
Is it possible that radios/firmware somehow got borked even though I am on S-ON? Is there a way to reflash them from bootloader?
Just thinking through ideas I'd try next and something that could possibly help recover or at least put me in a position to go back to Sprint for help.

Could have been a bad download. I think there is info on re locking in the development sticky section. It might give you some more information on what to do next.
"We're coming from a pure power source"

Just an update. Flashed again a stock ROM and installed the boot.img from stock using fastboot to be sure it was in place. (fastboot flash boot boot.img). That didn't work, still had boot loop where the phone loads enough to show the background and then restarts.
Used the PJ75IMG.zip file and attempted to install automatically in bootloader (from here) <-- Didn't install says "Main Version is older! Update Fail!
I then installed stock recovery and locked bootloader. Bootloader now shows "*** TAMPERED*** and *** RELOCKED***.
Ran RUU <-- Have a hard time doing anything since it doesn't boot up long enough to connect. Eventually RUU will fail with a connection error. I haven't been able to run RUU from HBOOT either and without the device stable long enough I'm not sure how to get RUU to run on the phone.
Still only boot far enough to see the background screen (wallpaper) and then reboot.
I'll gladly give $20 to anyone who offers a workable solution, paid either to you, or dev/charity of your choice if you don't want it.
This all started when I installed Fresh 5.2.1. Not sure if it was the fresh install or using TWRP to wipe data/cache and I also wiped system. Was that a mistake?
I just don't understand why I can't flash back even to stock. Since I'm relocked and never had S-OFF I don't understand how I was able to do something that can't be undone by flashing. I've flashed phones dozens of times so am comfortable with the process and just can't understand what went wrong and how to recover.
Is there an updated version of the PJ75IMG.zip file I could use?
Would it work to flash CM10 & the boot.img using fastboot?

jeggen said:
Just an update. Flashed again a stock ROM and installed the boot.img from stock using fastboot to be sure it was in place. (fastboot flash boot boot.img). That didn't work, still had boot loop where the phone loads enough to show the background and then restarts.
Used the PJ75IMG.zip file and attempted to install automatically in bootloader (from here) <-- Didn't install says "Main Version is older! Update Fail!
I then installed stock recovery and locked bootloader. Bootloader now shows "*** TAMPERED*** and *** RELOCKED***.
Ran RUU <-- Have a hard time doing anything since it doesn't boot up long enough to connect. Eventually RUU will fail with a connection error. I haven't been able to run RUU from HBOOT either and without the device stable long enough I'm not sure how to get RUU to run on the phone.
Still only boot far enough to see the background screen (wallpaper) and then reboot.
I'll gladly give $20 to anyone who offers a workable solution, paid either to you, or dev/charity of your choice if you don't want it.
This all started when I installed Fresh 5.2.1. Not sure if it was the fresh install or using TWRP to wipe data/cache and I also wiped system. Was that a mistake?
I just don't understand why I can't flash back even to stock. Since I'm relocked and never had S-OFF I don't understand how I was able to do something that can't be undone by flashing. I've flashed phones dozens of times so am comfortable with the process and just can't understand what went wrong and how to recover.
Is there an updated version of the PJ75IMG.zip file I could use?
Would it work to flash CM10 & the boot.img using fastboot?
Click to expand...
Click to collapse
I sent you a PM
Sent from my EVO using xda premium

I'm back up and running. With a kind and helpful tech we ran RUU again (twice) and still had boot loop. I was going to give up on it but we went into the default recover and cleared data and factory reset and it seems to be back to normal again and working fine.
Sent from my MB855 using Tapatalk 2

jeggen said:
I'm back up and running. With a kind and helpful tech we ran RUU again (twice) and still had boot loop. I was going to give up on it but we went into the default recover and cleared data and factory reset and it seems to be back to normal again and working fine.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
Awesome glad you got it fixed.
Sent from my EVO using xda premium

Related

[Q] Unable to boot into recovery

Ok... So a couple of days ago, I was having bootloop issues on Ineffabilis 1.3 using the Anthrax kernel. After doing a battery pull, I booted into the bootloader and then to recovery and found that my roommate, while playing with my phone, had flashed the ClockworkMod Recovery, I suppose through the Rom Manager app.
I figured it would be ok to do a full wipe and re-flash the rom since flashing the stock kernel didn't stop the bootlooping and I would just flash AmonRa back when I was done to do a backup.
Well, after doing a factory reset from CWM and getting errors thereafter trying to flash the superwipe and Ineffabilis, I rebooted the phone and skipped through the setup to get to the restart menu to get into the bootloader again to flash AmonRa. I was able to flash it, but now every time I try to get into the recovery whether from the restart menu, ADB, or through the fastboot menu, it automatically restarts the phone as soon as the recovery is loaded and goes back to the OS.
Has anyone experienced this and is there any way to fix it to get back into it?
Sounds like you have a ph image on your sd card. Just delete it and you should be fine
sent from ics land
I've long since removed all PH files from my phone, internal and external sdcard included, and even if there were that's never stopped my from booting directly into recovery from the restart menu or through ADB.
I've even gone as far as removing the external sdcard with the same result. It just boots into recovery and as soon as it loads for that split second, it automatically reboots to the HTC screen and back to Android.
I still have root and my phone isn't bricked. I just can't flash any roms or kernels in the future when we get our official ics update. WTB my EVO 3D's hboot 1.4 back...
Sent from my ADR6425LVW using XDA
ojdidit84 said:
I've long since removed all PH files from my phone, internal and external sdcard included, and even if there were that's never stopped my from booting directly into recovery from the restart menu or through ADB.
I've even gone as far as removing the external sdcard with the same result. It just boots into recovery and as soon as it loads for that split second, it automatically reboots to the HTC screen and back to Android.
I still have root and my phone isn't bricked. I just can't flash any roms or kernels in the future when we get our official ics update. WTB my EVO 3D's hboot 1.4 back...
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
what happens when you try to go to recovery...
i would just reflash a recoveyr in fastboot. cant hurt.
What it does is as soon as it boots to recovery, I see it load the recovery and then as soon as it loads, it's as if the phone automatically selects the reboot option and goes back through the normal boot no matter which method I use to boot into recovery.
I've done the fastboot method which flashed successfully, tried to re-flash clockwork using rom manager, scott's tool, adb & fastboot, also used scott's flash tool which was also successful and it just seems as if recovery mode is borked somehow and using these methods to go back to AmonRa produce the same result. I'm usually good at figuring these things out myself since I've been rooting and flashing since my first Sprint HTC Hero, EVO 4G, 3D, Epic 4G/Touch and I've never had anything like this happen before. Completely stumped .
Have done a search and haven't found anyone with the same issue so I have nothing prior to go off of. The phone works fine for now so I'm in no hurry since I still have root and thankfully Titanium Backup for my apps. Not sure what to try next at this point.
ojdidit84 said:
What it does is as soon as it boots to recovery, I see it load the recovery and then as soon as it loads, it's as if the phone automatically selects the reboot option and goes back through the normal boot no matter which method I use to boot into recovery.
I've done the fastboot method which flashed successfully, tried to re-flash clockwork, also used scott's flash tool which was also successful and it just seems as if recovery mode is borked somehow. I'm usually good at figuring these things out myself since I've been rooting and flashing since my first Sprint HTC Hero, EVO 4G, 3D, Epic 4G/Touch and I've never had anything like this happen before. Completely stumped .
Have done a search and haven't found anyone with the same issue so I have nothing prior to go off of. The phone works fine for now so I'm in no hurry since I still have root and thankfully Titanium Backup for my apps. Not sure what to try next at this point.
Click to expand...
Click to collapse
From hboot, choose factory reset and see if it boots you into recovery. I had a similar issue after running the new RUU, once I chose that it booted into custom recovery and i was able to reboot and then afterwards had no trouble accessing recovery.
mjh68 said:
From hboot, choose factory reset and see if it boots you into recovery. I had a similar issue after running the new RUU, once I chose that it booted into custom recovery and i was able to reboot and then afterwards had no trouble accessing recovery.
Click to expand...
Click to collapse
Ok. I'll give that a whirl in the morning and see if it solves the problem.
Bump... I'm stuck with this issue...
Hi,
Spent the last two days trying everything I could think of to get a custom recovery loaded on my rezound with no luck. Have searched everywhere and short of trying to hex edit some code nothing has worked.
I was on a custom ICS rom and applied the 4.03.605.2 RUU (hboot 2.27). Was S-ON with unlocked bootloader. I locked the bootloader, installed RUU successfully, unlocked the bootloader with my token. I tried flashing amon-ra, CWM, TWRP many versions of each by fastboot and hboot (PH98IMG). The custom recovery is successfully written in each case, but i can't successfully boot into the recovery partition either from fastboot or hboot menu option. I can write the recovery.img file from the RUU zip, and all is good. Ultimately, I am just trying to install a custom ROM/root my device.
I tried the above advice about performing a factory reset. No Dice. So for now, I am stuck in Verizon bloatware land, and very unhappy about it.
Suggestions welcome. Thanks everyone.
phaedrus43 said:
Hi,
Spent the last two days trying everything I could think of to get a custom recovery loaded on my rezound with no luck. Have searched everywhere and short of trying to hex edit some code nothing has worked.
I was on a custom ICS rom and applied the 4.03.605.2 RUU (hboot 2.27). Was S-ON with unlocked bootloader. I locked the bootloader, installed RUU successfully, unlocked the bootloader with my token. I tried flashing amon-ra, CWM, TWRP many versions of each by fastboot and hboot (PH98IMG). The custom recovery is successfully written in each case, but i can't successfully boot into the recovery partition either from fastboot or hboot menu option. I can write the recovery.img file from the RUU zip, and all is good. Ultimately, I am just trying to install a custom ROM/root my device.
I tried the above advice about performing a factory reset. No Dice. So for now, I am stuck in Verizon bloatware land, and very unhappy about it.
Suggestions welcome. Thanks everyone.
Click to expand...
Click to collapse
Hook up to PC. the phone can actually adb when turned off. or make sure ROM is booted with ADB turned on. It should connect to adb. Does it? Then your command would be "adb reboot recovery" after you have flashed a custom recovery. So what does it do when you try to enter recovery?
Thanks. Did try that, but not with phone off. I'll try both for good measure and let you know. Thank you fly...
Sent from my ADR6425LVW using xda app-developers app
Flyhalf205 said:
Hook up to PC. the phone can actually adb when turned off. or make sure ROM is booted with ADB turned on. It should connect to adb. Does it? Then your command would be "adb reboot recovery" after you have flashed a custom recovery. So what does it do when you try to enter recovery?
Click to expand...
Click to collapse
Hi Fly,
I was unable to get adb to see the phone when it was off with either a custom recovery or the stock recovery. When I rebooted to recovery from adb with a custom recovery installed, it attempts to boot to the recovery partition but fails and boots back to the OS (this is true when using adb, fastboot, and hboot to boot to recovery). When i reinstalled the stock recovery, it successfully boots to recovery using all methods.
i have tried other custom recovery versions, TWRP (preferred), AMON-RA, CWM Recovery...
annoyed.
Thanks Fly. Any other ideas?
phaedrus43 said:
Hi Fly,
I was unable to get adb to see the phone when it was off with either a custom recovery or the stock recovery. When I rebooted to recovery from adb with a custom recovery installed, it attempts to boot to the recovery partition but fails and boots back to the OS (this is true when using adb, fastboot, and hboot to boot to recovery). When i reinstalled the stock recovery, it successfully boots to recovery using all methods.
i have tried other custom recovery versions, TWRP (preferred), AMON-RA, CWM Recovery...
annoyed.
Thanks Fly. Any other ideas?
Click to expand...
Click to collapse
I'm out of ideas. Since your s-on you can't go down to the OTA RUU and try there. Maybe someone else can spread some light.
Well one more idea. Boot your phone into Fastboot. Plug into computer and download a custom recovery to your computer. The command to use is "fastboot boot recovery.img"
If that does work then download http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip and flash it inside of recovery. That will give you root inside your stock rom at least.
Flyhalf205 said:
I'm out of ideas. Since your s-on you can't go down to the OTA RUU and try there. Maybe someone else can spread some light.
Well one more idea. Boot your phone into Fastboot. Plug into computer and download a custom recovery to your computer. The command to use is "fastboot boot recovery.img"
If that does work then download http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip and flash it inside of recovery. That will give you root inside your stock rom at least.
Click to expand...
Click to collapse
Hi Fly,
Nothing doing. Can't flash the attached in stock recovery, can't boot into any recoveries with stock flashed or with custom recovery flashed. Seems there must be some new security built into the new RUU? I did note one thing. When I first flash the RUU the hboot banner says relocked (as i have to relock to install an RUU). However, as soon as I flash anything to the recovery partition it adds a new white on black banner that says tampered. Now, i have seen that before when I s-off'd my rezound previously (returned to verizon for audio problems). I never did s-off this particular phone. I don't recall my first phone flagging a new recovery or this phone flagging a new recovery on the old firmware (i could be wrong though as i don't spend a lot of time in hboot).
Still hoping to put a custom recovery on this. Any other way to load a custom rom? i really want to run Neo's AOKP, as I had that on here before I RUU'd. In fact, i got into this position because I was going to s-off the phone, but I had a custom rom. I started looking for RUU's to restore to stock because controlbear wouldn't work with custom rom. Instead of installing an early ICS again, i opted to install the latest RUU.
I searched the forums high and low and wasn't really able to find anyone with this problem. I wonder if there is something wrong with the RUU? I checked the MD5sum and it matched. When flashing recovery i checked the mainver too, so it isn't that... I'm stumped.
This phone wasn't real popular and is gettting old now (man, the lifecycle on phones suck, I had my N1 through many roms and AOSP releases! These new phones are gone in 6 months, a year tops). I doubt anyone is going to trouble themselves to crack a new HBOOT on this phone (this is 2.27).
Only other things i can think (and I haven't tried yet) is trying zergRushing it for temp root to at least remove/freeze the bloat like I did with this phone when I first got it. Or if I can just get a rom installed without a custom recovery I don't flash as often as I used to and figure an upgrade isn't long off. Or if i could downgrade the hboot or install jb hboot...
Would love it if someone had something new to try.
Thanks so much again Fly and happy holidays.
Success! (but how?)
Ok Fly,
I don't get it... not at all. I tried, just for the hell of it, a little more tonight and my phone was happy to flashboot boot TWRP 2.2.2.1 SPECIFICALLY. I was unable to get other versions working or other custom recoveries. I have no IDEA why. I can only think that the recovery partition is too small for some recovery.imgs? but 2.2.2.1 is actually bigger than 2.3.3.0 that you compiled for the rezound. Anyway, i have ROOT! now, my first step before I dork with anything is to S-Off this bad boy so i can move around a little more. I will probably still leave the locked bootloader after that, just to keep me from n00bing up. Haven't tried flashing the twrp recovery yet, don't want to goof up my S-off chances or not give you a chance to ask a question.
If you want some forensics to help others out, please let me know. I am gonna leave this phone alone for a day in case you have questions. There HAS to be some lesson in here. Totally random to me. (last thought) i was running 2.2.2.1 before I ran the RUU... wonder if that has something to do with it?
Thanks again Fly.
phaedrus43 said:
Ok Fly,
I don't get it... not at all. I tried, just for the hell of it, a little more tonight and my phone was happy to flashboot boot TWRP 2.2.2.1 SPECIFICALLY. I was unable to get other versions working or other custom recoveries. I have no IDEA why. I can only think that the recovery partition is too small for some recovery.imgs? but 2.2.2.1 is actually bigger than 2.3.3.0 that you compiled for the rezound. Anyway, i have ROOT! now, my first step before I dork with anything is to S-Off this bad boy so i can move around a little more. I will probably still leave the locked bootloader after that, just to keep me from n00bing up. Haven't tried flashing the twrp recovery yet, don't want to goof up my S-off chances or not give you a chance to ask a question.
If you want some forensics to help others out, please let me know. I am gonna leave this phone alone for a day in case you have questions. There HAS to be some lesson in here. Totally random to me. (last thought) i was running 2.2.2.1 before I ran the RUU... wonder if that has something to do with it?
Thanks again Fly.
Click to expand...
Click to collapse
Anytime :fingers-crossed:
Crazy how things work like this. But the recovery partition shouldn't be to small to flash a custom recovery. Good luck. Just sounds like one of those rare things that happens.

[Q] Bootloop that's not fixed by CDMA/LTE Auto Setting

Hey, I hope you guys can help me out.
I have a rezound here, that is bootlooping. It will stay booted into android for maybe 15 seconds then freezes, and reboots. I searched and saw a fix that involved changing the phone setting to CDMA/LTE evda Auto, and it was already apparently on that setting.
It wasn't letting me factory reset it, even from the bootloader menu. It would look like it was factory resetting, but then still not be factory reset. The only way I could get it to factory reset was by unlocking the bootloader through HTC DEV...but that didn't fix the issue. (Warranty was already void anyway because the void screw was tampered with)
What should I try next? I've flashed a rom on an evo 3d where I had to load a custom recovery through the bootloader, so I figured there was probably something similar on the rezound...but this has S-ON and revolutionary doesn't seem to available for rezound yet...and I don't think I could flash clockwork quick enough since it freezes after like 10-15 seconds.
Any input? I'd really like to get this phone working...thanks!
Once you unlock you should install Amon Ra recovery with fastboot. The thread is http://forum.xda-developers.com/showthread.php?t=1339679
Well I flashed recovery via fastboot, and flashed CleanRom ICS (after loading the one zip file needed prior to flashing ICS Roms, and of course after backup and after wiping everything a few times) and its the same thing...gets into android and reboots after 10 seconds or so.
gdawson6 said:
Well I flashed recovery via fastboot, and flashed CleanRom ICS (after loading the one zip file needed prior to flashing ICS Roms, and of course after backup and after wiping everything a few times) and its the same thing...gets into android and reboots after 10 seconds or so.
Click to expand...
Click to collapse
Im having the same problem. I have tried several different roms at this point and my phone is still bootlooping..
Anyone got any ideas?? Im desperate to get this thing working!
Have you guys tried to manually install the kernel from fastboot?
phylo1 said:
Im having the same problem. I have tried several different roms at this point and my phone is still bootlooping..
Anyone got any ideas?? Im desperate to get this thing working!
Click to expand...
Click to collapse
Just boot to bootloader and run the ruu for 2.11 from windows or figureout how to get the ph98img.zip of gingerbread or one of the leaks onto the root of the sdcard and flash that in the bootloader. If not s-off you should still be able to lock the bootloader using adb.
The reboots should NOT be affecting the bootloader or flash a backup from recovery. Just start fresh.
Sent from my ADR6425LVW using Tapatalk 2
Run an RUU. EXE version is preferable.

need help for stock return

I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
I had much the same problem with my cdma, hboot 1.5, S-On shooter. When I was S-On none of the ICS roms would work. The all bootlooped on me. If you follow the rooting method found here on xda, it will get you back to a stock Rooted GB Rom.
go into hboot -> fastboot USB-> run command dos -> fastboot cwm-4.0.1.4-shooter.IMG -> flash the 2.17 firmware-> enjoy.
I had to S-off with Juopunutbear, then re-run that root/flash to get past the bootloops.
Sent from my Shooter using xda app-developers app
Unfortunately I have tried that and it still is not working.
My only suggestion would be to try it a few times, other then that, its above my head.
Sent from my shooter using xda app-developers app
rookiemistake said:
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
Click to expand...
Click to collapse
Have you tried one of the ruu exe files that you run from your computer? If you are trying to go stock, you should be able to relock the bootloader and run the ruu and that's it.
Sent from my ICS 3VO with Tapatalk 2
First of all I want to thank everyone that has been attempting to assist me with my problem. I have tried to relock since I am on htcdev unlock and then run an ruu force via my computer. I get an installation aborted error when trying to flash pg86img via recovery. I don't know what else to say.
You can't flash a bootloader zip from recovery. You have to flash it from hboot. Also make sure the zip is named correctly "PG86IMG.zip" without the quotes. Also make sure the zip is on the root of your sd as in not in any folders. Once you've named the zip correctly and placed it correctly then power off the phone. Hold down the volume down button and tap the power button. You should boot into the bootloader wait until the phone recognizes the zip and follow the on screen instructions. Hopefully this helps.
#Root-Hack_Mod*Always\=LTE
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
rookiemistake said:
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
Click to expand...
Click to collapse
To get the ota release (if it ever comes ) I do believe you will need to be locked and running the existing gingerbread rom. While I am not positive, I think the system uses the props file to determine if an update is applicable, and it will likely not recognize the teamgenesis rom version as being upgradeable.
Now I will likely get flames for saying this, but if you want to put the meanrom v2.4 of ICS on the phone, it can be done with s-on, you just need to follow the correct process. I ran that rom for a while, and it is very stock like, stable, and has a few enhancements that you will not find on a non-rooted stock rom. I never found anything wrong or not working with that rom.
To get it to load, first I downloaded flashimagegui from market, put the meanrom zip file on the sd card and made sure I had a recovery that I could get into. I am using TWRP v2.1.1, lots of folks talk about others like ext4, and I am only going to say use whichever you like, after all it is your phone.
Then with the phone unlocked via the htc method, I started the flashimage app, and browsed to the meanrom file. It extracted the kernel and flashed it. Once that was done, with clear cache buttons selected, rebooted to recovery, and used the install menu selection of TWRP to again flash the same rom file. Once it flashed the file, selected clear cache and dalvik just to be safe, selected reboot system, and it worked great.
Have a great weekend.
So, apparently I am still doing something wrong. I have put the pg86img on the root, relocked to the bootloader, and let it run it's course. However, it will get through with reading it and stops and does not finish anything with loading the system information. I have also tried to run the ruu via usb connection. I keep running into a c++ issue saying runtime error. I have wiped everything and thankfully I did make a backup of the rom and other information that I was runing so I can currently fall back on that.
I am on hboot 1.5, 2.17, and teamgenesis ICS rom for evo 3d.
Apparently there have been rumors that Sprint has finally released the ICS OTA, not that it really matters anymore, but I have run into a few interesting glitches, such as WIFI not staying connected while asleep or disconnecting.
If I have to I am willing to pay to do a netmeeing with someone in order to be able to fix this.
Sorry if it sounds like I am getting frustrated, but I have tried every walkthrough that I have found and have not had any luck with any of them.
Please help.
I forgot to say I am s-on

[Q] Unab;e to install ICS RUU before installing Nils' Business

Hey everyone,
So I have successfully HTC Unlocked my Rezound bootloader, installed Amon Ra, and then installed and booted the CM9 unofficial. Problem was that CM9 wasn't quite as cooperative as I'd hoped - it is unofficial, after all, and so I decided to abandon that in favor of Nils' Business ROM. Here's where I ran into issues.
I have tried everything in every order I can find online and think of, including Nils' writeup. So, for the life of me, I cannot get the leaked ICS RUU to boot (4.03.605.2 as listed in his instructions on XDA). Install runs fine every time I do it from the relocked (I checked) stock HBOOT, all steps included. Every time it reboots (and I've tried forcing it back into hboot to do the install a second time) it just goes to the white HTC screen and starts boot looping. Tried it a million ways, no go. Also worth noting - the stock recovery doesn't install properly, either. Some'fin is hinky, here.
So I've tried just "assuming" it went fine anyhow and then proceeding with the install for Nils' ROM and same deal, no go, although with one difference. With Nils' ROM, it does display the boot splash screen "Nils Business ROM" or what have you about 1 out of every 4 "boots" in the loop cycle, and then reboots again.
I think I am going to perform S-OFF tomorrow if I have the time, and then try it again using the S-OFF instructions, but I would sincerely appreciate any help from you all. Honestly, I'm at near wit's end with this device, and I don't want to be, I enjoy this chase too much, but I *really* want the reward at the end of it, lol.
Any help is deeply appreciated.
- Katie
Re: [Q]
I'm guessing because of the corrupted recovery, you have a bad download of the RUU. Try re downloading and check the md5 hash for a match. The ruu should reboot itself after the first pass and end up in bootloader again for the second pass.... If not then after the first pass just hold down power + vol down to get back to bootloader.
Hope this helps
Sent from my ADR6425LVW using xda app-developers app
Make sure that you have a booting ROM before you s-off. You will cause yourself all kinds of heartache if you don't.
Using an sd card reader on a pc, check md5 of your RUU zip file. If it checks out good, put the sd back in your rez and do an hboot power on and accept the update again. Report back with your findings. Also you will need to re-unlock your hboot after and install your recovery again.
Snuzzo said:
Using an sd card reader on a pc, check md5 of your RUU zip file. If it checks out good, put the sd back in your rez and do an hboot power on and accept the update again. Report back with your findings. Also you will need to re-unlock your hboot after and install your recovery again.
Click to expand...
Click to collapse
Hey, thanks. Yeah, the RUU does check out just fine against an MD5SUM.
nm.... just read your original post again and you say you did relock the phone. I was hoping it was something simple like that that was overlooked.
Carry on...
feralicious said:
Nothing to see here, folks, move along.
Click to expand...
Click to collapse
Right now, I cannot S-OFF because it requires a working stock image, and I'll be lucky to get anything more than CM9 unofficial working here.
You're too fast, now my bad post lives on...
So, when theh RUU failed, you unlocked again, flashed a custom recovery and tried to flash Nils' ROM?
Do you have a nandroid you can try to restore? Even if its the cm9 ROM at least to see if you can get it back to a working phone?
feralicious said:
You're too fast, now my bad post lives on...
So, when theh RUU failed, you unlocked again, flashed a custom recovery and tried to flash Nils' ROM?
Do you have a nandroid you can try to restore? Even if its the cm9 ROM at least to see if you can get it back to a working phone?
Click to expand...
Click to collapse
Well that's the trick. CM9 didn't work well enough to even be worth backing up. I'm trying to reinstall it again now just to see if I get there - and it looks like I will. Once I'm back up with that, I'm not sure where to go from there. The phone barely worked under CM9. Really hoping to get Nils' ROM on there, since it gives all the nice features of a stock device without the bloatware. Even if I never get S-OFF, I'll be perfectly happy with just Nils' software.
How about this... did you wipe everything before running the RUU? There's CleanWipe in the Development forum you can flash it from recovery and it will wipe everything 5 times!
This shouldn't make any difference, but there's also a different RUU, the OTA that's not global. You might try that one instead. I'm convinced that sometimes things are just voodoo even when they should be completely logical. That's definitely the case at work on the Avid systems I use.
Here's the link to it:
http://androidfiles.org/ruu/?dir=Vigor
feralicious said:
How about this... did you wipe everything before running the RUU? There's CleanWipe in the Development forum you can flash it from recovery and it will wipe everything 5 times!
This shouldn't make any difference, but there's also a different RUU, the OTA that's not global. You might try that one instead. I'm convinced that sometimes things are just voodoo even when they should be completely logical. That's definitely the case at work on the Avid systems I use.
Here's the link to it:
http://androidfiles.org/ruu/?dir=Vigor
Click to expand...
Click to collapse
I did try wiping everything first. No luck. I will try the CleanWipe tomorrow, because right now, whatever my issues are, I'm being prevented from solving them since I can't S-OFF and I can't even seem to get a working ROM to make the phone worth having! Ugh.
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Flyhalf205 said:
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Click to expand...
Click to collapse
Oh yeah! Try that. Someone else was having trouble and did it that way and it worked. Here's instructions, just make sure you use PH98IMG and not whatever is used in the instructions since it was written up for a different phone.
http://androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
Also, once you get your phone back to stock make a nandroid as soon as you flash the recovery again so you'll have that to go back to if you have any more issues.
Flyhalf205 said:
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Click to expand...
Click to collapse
Thank you, your magnanimity! Seriously, lol, you're gracing my thread just by being here. :victory:
feralicious said:
Oh yeah! Try that. Someone else was having trouble and did it that way and it worked. Here's instructions, just make sure you use PH98IMG and not whatever is used in the instructions since it was written up for a different phone.
http://androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
Also, once you get your phone back to stock make a nandroid as soon as you flash the recovery again so you'll have that to go back to if you have any more issues.
Click to expand...
Click to collapse
Thanks for the clicky, Feralicious. Same results, unfortunately. I'm going to try doing the RUU flash of Nils' ROM instead. Do you guys know where I can get the ICS firmware by itself? I cannot be sure that it's actually flashed right, unfortunately.
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Flyhalf205 said:
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Click to expand...
Click to collapse
I'll do that stuff and let you know. Thank you!
Yes, I am on 2.27 HBOOT.
Point of interest, though possibly unsurprising. When I send the lock command, it locks and reboots, but says "Failed" in my command window screen. Sure this is probably normal since the phone might just reboot before responding to the computer, but possibly an issue.
I believe that is the image I tried before, but I'll do it again both ways to be certain and report back soon! :good:
ncc74656m said:
Yes, I am on 2.27 HBOOT.
Point of interest, though possibly unsurprising. When I send the lock command, it locks and reboots, but says "Failed" in my command window screen. Sure this is probably normal since the phone might just reboot before responding to the computer, but possibly an issue.
I believe that is the image I tried before, but I'll do it again both ways to be certain and report back soon! :good:
Click to expand...
Click to collapse
My DNA said something about failing when I locked it. But it locked just fine.
Since it is failing.
fastboot oem rebootRUU
fastboot oem lock ----if unlocked
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
Should work Maybe
Flyhalf205 said:
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
Click to expand...
Click to collapse
Ok, so, this part including a factory reset got me to "HTC Quietly Brilliant" screen, but then it bootloops again. Tried factory resetting again to no avail. Trying the second part.
Flyhalf205 said:
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
Click to expand...
Click to collapse
Same thing as before unfortunately. :/ Performed a factory reset afterwards to be safe - no go. Everything shows OK though in both this and the above install. *shrug*
Flyhalf205 said:
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Click to expand...
Click to collapse
Proceeding with another attempt at installing CM9, I guess. Maybe the first one got hosed. If I get it booting in any form, I'll Nandroid it before trying anything else.
ncc74656m said:
Proceeding with another attempt at installing CM9, I guess. Maybe the first one got hosed. If I get it booting in any form, I'll Nandroid it before trying anything else.
Click to expand...
Click to collapse
I really wouldn't see why you would need a Sense rom to get s-off. I would imagine it would just need su and busybox installed. But nandroid then try a sense rom again. Make sure you flash the boot.img through fastboot

possibly useful info for those who have unlocked and relocked this device

I did this a while ago because i was going to try rooting, then changed my mind. Anyway, no I'll effects, until recently when, T-Mobile pushed out a software update. Tried doing the update (numerous times), but nothing happened. Called T-Mobile; no help. Forgot about it since I read it was a minor update. Anyway, since my phone had been using up batteries very fast, I decided to do a factory reset. Strangely, this did not work either. Again t-mobile ; no help. Then got the idea to unlock the boot loader again and see what happens. That worked. Was able to wipe the phone. Then with the bootloader unlocked, I again attempted to do the software update. Phone rebooted and went right into 4ext recovery and after the update failed at first, giving me a message that the ext. Sd card could not be found. I used 4ext to mount the ext SD, which was not mounted. The update successfully completed. Apparently, with the phone in relocked state, many things seem to be not possible.
joep229 said:
I did this a while ago because i was going to try rooting, then changed my mind. Anyway, no I'll effects, until recently when, T-Mobile pushed out a software update. Tried doing the update (numerous times), but nothing happened. Called T-Mobile; no help. Forgot about it since I read it was a minor update. Anyway, since my phone had been using up batteries very fast, I decided to do a factory reset. Strangely, this did not work either. Again t-mobile ; no help. Then got the idea to unlock the boot loader again and see what happens. That worked. Was able to wipe the phone. Then with the bootloader unlocked, I again attempted to do the software update. Phone rebooted and went right into 4ext recovery and after the update failed at first, giving me a message that the ext. Sd card could not be found. I used 4ext to mount the ext SD, which was not mounted. The update successfully completed. Apparently, with the phone in relocked state, many things seem to be not possible.
Click to expand...
Click to collapse
You must have done something wrong I was on ARHD then I relocked bootloader and ran the stock ruu then booted up and downloaded and installed the update. All worked first time no issues at all.
Sent from my HTC_Amaze_4G using xda app-developers app
dntipwn said:
You must have done something wrong I was on ARHD then I relocked bootloader and ran the stock ruu then booted up and downloaded and installed the update. All worked first time no issues at all.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thanks for the response, but can't imagine what I could I have done wrong? All I did when trying to install the update was click the 'update now' box. phone simply rebooted to recovery and did nothing else. Navigated to 'reboot'. Phone rebooted and update was still there un-installed. Checked software version; unchanged. When trying to do system restore, tried it from security menu and also tried booting direct to recovery. Highlighted 'system restore', pushed power button. Both ways and the phone simply rebooted with everything still intact!!
P.S. Didn't know ARHD works with Amaze 4g? Would love to try it, but a little anxious about doing wire thing to get to s-off. It's my only phone. Is it risky?
joep229 said:
Thanks for the response, but can't imagine what I could I have done wrong? All I did when trying to install the update was click the 'update now' box. phone simply rebooted to recovery and did nothing else. Navigated to 'reboot'. Phone rebooted and update was still there un-installed. Checked software version; unchanged. When trying to do system restore, tried it from security menu and also tried booting direct to recovery. Highlighted 'system restore', pushed power button. Both ways and the phone simply rebooted with everything still intact!!
P.S. Didn't know ARHD works with Amaze 4g? Would love to try it, but a little anxious about doing wire thing to get to s-off. It's my only phone. Is it risky?
Click to expand...
Click to collapse
Well I'm pretty sure that with the locked bootloader and stock Rom there won't be any issues I was not rooted or any of that. And I'm not S-off. I didn't mess with any of that wire crap just make sure you have 4ext recovery and have smart flash enabled in the options and you can flash all the Roms you want. Just make sure before every Rom flash you make sure the smart flash is enabled unless you configure it to stay on.
Sent from my HTC_Amaze_4G using xda app-developers app
My strange problems are continuing. Yesterday I was finally able to do a factory reset and update the software on my phone. Now for some strange reason, I can no longer enable WiFi or Bluetooth. It's as if since I told T-mobile that I had unlocked, and relocked my phone, they sent a signal to my phone to totally screw it up.!!!
joep229 said:
My strange problems are continuing. Yesterday I was finally able to do a factory reset and update the software on my phone. Now for some strange reason, I can no longer enable WiFi or Bluetooth. It's as if since I told T-mobile that I had unlocked, and relocked my phone, they sent a signal to my phone to totally screw it up.!!!
Click to expand...
Click to collapse
Ok well what i would do in this situation would be to just start over fresh. First download the newest ruu we have from here for tmobile: http://forum.xda-developers.com/showthread.php?t=1617644, which would be this one: RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip and make sure you rename it PH85IMG.zip and place that on your externel sd card. Once you do that make sure you phones boot loader is locked (i use hansoons tool kit for all this) once boot loader is locked (says relocked) then you can boot into I think its called hboot (the screen where is says locked/relocked/unlocked/) by powering phone off then pushing Vol down key and power at the same time and hold it will bring you to a screen where it will start reading the file you just put on you sd card and ask if you want to update. Vol up for yes and vol down for no select yes and it will do its thing and it will ask to press power button to reset and the will boot up to stock ICS and everything should work fine.
Thank you so much. Actually had to do it a little differently. Downloaded the ruu and renamed it. Put it in the data subfolder of all-in-one kit. Used Hasoon's to reboot to bootloader. Then flashed the ruu using Hasoon's. Same thing, I guess. Anyway, everything works now. I put the PH85IMG.zip in the root of the sdcard. any idea why rebooting to the bootloader did not find it and start the flash? Says PH85IMG.zip not found.
dntipwn said:
Well I'm pretty sure that with the locked bootloader and stock Rom there won't be any issues I was not rooted or any of that. And I'm not S-off. I didn't mess with any of that wire crap just make sure you have 4ext recovery and have smart flash enabled in the options and you can flash all the Roms you want. Just make sure before every Rom flash you make sure the smart flash is enabled unless you configure it to stay on.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
dntipwn - you said you didn't mess with the wire crap. Were you able to flash ARHD to your phone with s-on? Can you give me some tips?
joep229 said:
dntipwn - you said you didn't mess with the wire crap. Were you able to flash ARHD to your phone with s-on? Can you give me some tips?
Click to expand...
Click to collapse
Yes all you have do is first unlock bootloader, then you will need to flash a 4ext recovery, after that root is needed. The easiest way its to use hansoons tool. After all that our done you will need to download super wipe.zip from the arhd page and the room of choice I actually get better battery on NRG stock rom. Boot into recovery flash super wipe it will reboot then flash the rom reboot which will take about 5 to 10 mins. After it boots up I like to let it sit without touching it for 10mins reboot then set up the phone then reboot again and you should be set.
Sent from my SCH-I905 using xda app-developers app
The key of you are s-on is to enable smart flash in 4ext. Its under settings in recovery
Sent from my HTC Ruby using xda app-developers app
I just successfully reverted my Amaze to sufficient stock to effect the download; download was already on the device but wouldn't install. Here were my steps.
Flashed stock recovery from CWM by extracting recovery.img from firmware.zip inside the OTA update zip.Rebooted into HBOOT, entered FASTBOOT.
=> fastboot flash recovery recovery.img
Attempted to apply the update from Recovery. Fail.
Initiated update from Settings | About Phone | Software updates. Update rebooted the phone...
Update complained about a mismatch in build.prop. Oops; I forgot that I'd edited it to override the "HTCLinkify" fix for Apple.
=> Edited /system/build.prop, removed ro.da1.method=enabled line, reverted ro.da1.enabled=false to true.
Rebooted.
Initiated the software update again, which it downloaded.
Started the update again, which rebooted the phone, updated without interruption, and rebooted into the new version (confirmed by popup and Settings | About phone | Software information).
=> Success.
I did not have to relock the bootloader. At this point I'd reflash recovery to CWM or TWRP again, but this was done on a phone which has a defective charging circuit, so I'm relocking the bootloader and returning it to T-Mobile.

Categories

Resources