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.
Related
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.
Alright, so I've got an S-On rooted Rezound and I'm stuck in the boot loop. YES I've read all the posts about logging in and dialing *#etc and also to go into Mobile Network and switch to LTE/CDMA, but I can't dial anything because the phone cuts off before I get a chance, and the LTE switch does nothing. I've tried flashing several different kernels, using the adb method and the PH98IMG methods, I've tried installing several different ROMS, I've done at least 10 different wipes/factory resets, I boot my phone without the cover, SIM card and without the SD card..and I'm still stuck in this boot loop. Someone please help a noob
---- EDIT WITH SOLUTION ----
Here's my "solution" to this issue. I'm sure it's located somewhere in these forums, but I couldn't find it so I imagine others can't either. Essentially, you're going to have to S-Off. Here's the solution:
I believe my recovery started acting funny after I failed to S-Off properly the first time. Amon Ra was all gimmicky and said stuff like "E: can't find cache" and reinstalling the recovery/wiping everything (and I mean everything: external SD, internal SD, cache, partioning SD card etc..) wasn't working. I tried re-installing Amon Ra through command prompt with the adb, I tried reinstalling my ROMS but my phone wasn't having it.
It got to the point all I could boot into was a white HTC screen, so I then tried out Twrp's 2.1 Touchscreen (I wasn't S-Off yet) recovery (I don't have enough posts to post a link yet ) which INITIALLY reported the same "E: can't find cache" errors as Amon Ra, BUT when I wiped my files in Twrp it seemed to actually fix them...I'm not sure exactly what I wiped or formatted that fixed the "E: can't find mount/cache" issues, so try everything.
So my ROM installed but I was still stuck on the white HTC logo. This is where I INSTALLED A NEW KERNEL THROUGH ADB. I wish I knew which kernel I installed, but I have like 10 and I just picked a random one. The point is if you're still stuck at a white HTC screen, install a new kernel.
So I got a recovery on the phone, and then I tried to S-Off again but I didn't have a good ROM installation so that was hanging at the HTC white screen. I then installed CleanROM DE 1.4 and I was able to boot into it, but ran into my initial problem of it crashing after dialing a number and entering infinite reboot. However, it would stay on just long enough for me to run ControlBear's program to S-Off.
So I S-Offed, I downloaded the Gingerbread RUU (the .exe version for Windows), I installed it, and now I can dial numbers and I'm all goodie again. Unfortunately, I honestly think the only way I was escaping my trouble was doing an S-Off, unless they leak a Ice Cream Sanwhich executable for Windows.
TL;DR Install Twerp 2.1 through adb, wipe everything, install CleanROM DE 1.4, install kernel S-Off, run Gingerbread RUU .exe
autotuneuser said:
Alright, so I've got an S-On rooted Rezound and I'm stuck in the boot loop. YES I've read all the posts about logging in and dialing *#etc and also to go into Mobile Network and switch to LTE/CDMA, but I can't dial anything because the phone cuts off before I get a chance, and the LTE switch does nothing. I've tried flashing several different kernels, using the adb method and the P87etc methods, I've tried installing several different ROMS, I've done at least 10 different wipes/factory resets, I boot my phone without the cover, SIM card and without the SD card..and I'm still stuck in this boot loop. Someone please help a noob
Click to expand...
Click to collapse
Have you tried running a RUU to put it back to factory like you just bought it?
I can't tell you how many times I've had to do that to fix stuff.
Magestic12 said:
Have you tried running a RUU to put it back to factory like you just bought it?
I can't tell you how many times I've had to do that to fix stuff.
Click to expand...
Click to collapse
I think I have downloaded the stock RUU..but just to be sure could you possibly link me to the correct one to run? Also I thought it was impossible to go back down from Ice Cream Sandwhich to Gingerbread?
autotuneuser said:
I think I have downloaded the stock RUU..but just to be sure could you possibly link me to the correct one to run? Also I thought it was impossible to go back down from Ice Cream Sandwhich to Gingerbread?
Click to expand...
Click to collapse
It is if you're s-on. Also, what did you mean by "P87etc," are you flashing the files properly?
autotuneuser said:
I think I have downloaded the stock RUU..but just to be sure could you possibly link me to the correct one to run? Also I thought it was impossible to go back down from Ice Cream Sandwhich to Gingerbread?
Click to expand...
Click to collapse
People say a lot of things are impossible, most have the virtue of never being tried.
This is the one I used to fix mine when I screwed up the partitions on my phone. I will warn you, the link in the thread takes you to another site & you have to sign up to download it. Its completely free & legit, but it won't let you download unless you register which is STUPID!
http://forum.xda-developers.com/showthread.php?p=25664508
Let me know if that helps
Oh & BTW I was & still am on the ICS leaks when I did this, so you'll be fine. You will lose everything on your phone though, because it wipes everything. But if you can't use it, that's not really an issue I guess.
tekhna said:
It is if you're s-on. Also, what did you mean by "P87etc," are you flashing the files properly?
Click to expand...
Click to collapse
The PH98IMG file. And I believe I'm flashing the properly..I do it twice; flashboot in adb, it tells me success, I then flash again right there, and then I reboot back to the bootloader and flash again so I do it 3 times in total.
I'm downloading the Vigor executable now. It's going to take a while but I'll report back with my results.
autotuneuser said:
The PH98IMG file. And I believe I'm flashing the properly..I do it twice; flashboot in adb, it tells me success, I then flash again right there, and then I reboot back to the bootloader and flash again so I do it 3 times in total.
I'm downloading the Vigor executable now. It's going to take a while but I'll report back with my results.
Click to expand...
Click to collapse
PH98IMG is not going to help you in this situation. You are going to have to download & run the RUU that I linked in the previous post. Trust me on this, not only have I already tried that before, I've blown my phone up enough times to know.
Magestic12 said:
PH98IMG is not going to help you in this situation. You are going to have to download & run the RUU that I linked in the previous post. Trust me on this, not only have I already tried that before, I've blown my phone up enough times to know.
Click to expand...
Click to collapse
Ok, I went to use the RUU and at first I got error 150, so I read somewhere I should lock my bootloader, so I relocked and now I get error 140, whcih is bootloader verision error. I think that's because I'm on ICS with S-On right? Is there any ICS RUU I can use to restore my phone? I downloaded Vigor_Stock_Doedexed_3.14.605.5 before but it still wasn't working for me.
autotuneuser said:
Ok, I went to use the RUU and at first I got error 150, so I read somewhere I should lock my bootloader, so I relocked and now I get error 140, whcih is bootloader verision error. I think that's because I'm on ICS with S-On right? Is there any ICS RUU I can use to restore my phone? I downloaded Vigor_Stock_Doedexed_3.14.605.5 before but it still wasn't working for me.
Click to expand...
Click to collapse
And as far as this goes yeah you can't use the .exe if your on ICS firmware with s-on and there are no available .exe's for ICS
Sent from my ADR6425LVW using Tapatalk 2
Unless you are already on the gingerbread build, and it sounds like your not, if you are s-on, it simply will not work. My suggestion is to download the latest leak and that should get you going. If it were me, and I aleady did it, download the latest leak here: http://android.thesmallprint.org/ICS.LEAK.3.14.605.5_PH98IMG.zip. Rename it PH98IMG.zip and put it on your external sd card. Should take less than 10 mins to download. Reboot into bootloader and let hboot install it. Make sure you are locked or relocked. After that is installed either delete or change the name of that file. Reboot into bootloader, unlock, and install either amon ra or tpwr and you can reinstall that rooted rom.
what he said
mikey's comments just previous are totally right, but after install, i would recommend
a factory reset, maybe even twice.
your bootloop problem should be cured then...
I was on the latest ICS firmware running an ICS ROM when I had to run the RUU I gave the link for & it worked fine for me.
Here's my suggestion & you can take it for what its worth.
I would download the latest HBoot & Radios & flash them.
Then if you can get into recovery, wipe everything, manually wipe the system, boot, etc. Then after that try running the RUU.
I just did this earlier in the week & it worked fine & my phone was all screwed up because the partitions were mounting to the wrong places & just all messed up.
I am by no means a dev or an expert, I'm just telling you what I did.
WHATEVER YOU CHOSE, YOU DO AT YOUR OWN RISK, but I don't see where you really have a choice.
Let me know if I can be of anymore help as I know what its like to have a phone that's freaking out on you. You can PM me or post here which ever you prefer. If after that we still can't get it fixed, we'll go find a dev to help us.
mikeyk101 said:
Unless you are already on the gingerbread build, and it sounds like your not, if you are s-on, it simply will not work. My suggestion is to download the latest leak and that should get you going. If it were me, and I aleady did it, download the latest leak here: . Rename it PH98IMG.zip and put it on your external sd card. Should take less than 10 mins to download. Reboot into bootloader and let hboot install it. Make sure you are locked or relocked. After that is installed either delete or change the name of that file. Reboot into bootloader, unlock, and install either amon ra or tpwr and you can reinstall that rooted rom.
Click to expand...
Click to collapse
Well now my recovery is saying it can't mount various things like "E: can't mount b dev/block/ blah blah"
And I tried flashing my ROM through Amon recovery but it's saying it can't open the file because it's (bad). I formatted the SD card and I'm still getting the issue. Any ideas?
Did you download the one from the link? You don't flash that PH98IMG.zip in recovery, you boot up into bootloader and let hboot find it. If when you get to your bootloader and it is fastboot, use your volume key and select on bootloader option. Then hboot will find it and ask you if you want to install it. Install it. After that, you will then need to reinstall either amon ra or the other but stay away from clockworkmod. But to reinstall the recovery, you will have to unlock again.
mikeyk101 said:
Did you download the one from the link? You don't flash that PH98IMG.zip in recovery, you boot up into bootloader and let hboot find it. If when you get to your bootloader and it is fastboot, use your volume key and select on bootloader option. Then hboot will find it and ask you if you want to install it. Install it. After that, you will then need to reinstall either amon ra or the other but stay away from clockworkmod. But to reinstall the recovery, you will have to unlock again.
Click to expand...
Click to collapse
I did install in hboot. I then installed Amon so I could flash the ROM and that's what's giving me all those errors.
If all you are after is stock and rooted, try looking at this one: http://forum.xda-developers.com/showthread.php?t=1642217
Since you ran the PH98IMG that I directed you to, you are now on ICS. So follow the directions in that thread for "S-On and ICS".
Installation for S-ON Devices on ICS firmware
•Copy ROM to SD Card AND PH98IMG.zip to ROOT of SD Card
•Reboot to recovery
•wipe data / Factory Reset
•Flash ROM
•Use Developer Menu to reboot to bootloader and flash the boot.img file in the PH98IMG.zip
•Reboot
•Profit!
Edit: The only change I would recommend is to hold off putting that PH98IMG file from that thread on the sd card right away. You will have a hard time getting to recovery if you have that on the card. I would suggest following all the instructions up to and including "Flash ROM". Then I would "return" back to the main Amon Ra screen, make sure you have the data cable connecting your phone to the computer, select "USB-MS Toggle", then select the SD Card, and that will allow you to copy the PH98IMG file to the SD card. Then continue with the rest of the directions. If you do this right, you should be ok.
mikeyk101 said:
If all you are after is stock and rooted, try looking at this one: http://forum.xda-developers.com/showthread.php?t=1642217
Since you ran the PH98IMG that I directed you to, you are now on ICS. So follow the directions in that thread for "S-On and ICS".
Installation for S-ON Devices on ICS firmware
•Copy ROM to SD Card AND PH98IMG.zip to ROOT of SD Card
•Reboot to recovery
•wipe data / Factory Reset
•Flash ROM
•Use Developer Menu to reboot to bootloader and flash the boot.img file in the PH98IMG.zip
•Reboot
•Profit!
Edit: The only change I would recommend is to hold off putting that PH98IMG file from that thread on the sd card right away. You will have a hard time getting to recovery if you have that on the card. I would suggest following all the instructions up to and including "Flash ROM". Then I would "return" back to the main Amon Ra screen, make sure you have the data cable connecting your phone to the computer, select "USB-MS Toggle", then select the Internal_sd, and that will allow you to copy the PH98IMG file to the SD card. Then continue with the rest of the directions. If you do this right, you should be ok.
Click to expand...
Click to collapse
It's the actual recover I believe to be giving me the errors, but I'll try what you said in about 2 days (I need to study for finals). It might be because I tried to S-Off and I installed all of that guys software and it might be making the phone act funny. I'll be much more descriptive about my errors when I post back in 2 days.
I fixed it!!
Ok, so I finally got it working, I'll try to detail my steps for anyone else who ran into similar issues:
I believe my recovery started acting funny after I failed to S-Off properly the first time. Amon Ra was all gimmicky and said stuff like "E: can't find cache" and reinstalling the recovery/wiping everything (and I mean everything: external SD, internal SD, cache, partioning SD card etc..) wasn't working. I tried re-installing Amon Ra through command prompt with the adb, I tried reinstalling my ROMS but my phone wasn't having it.
It got to the point all I could boot into was a white HTC screen, so I then tried out Twrp's 2.1 Touchscreen (I wasn't S-Off yet) recovery (I don't have enough posts to post a link yet ) which INITIALLY reported the same "E: can't find cache" errors as Amon Ra, BUT when I wiped my files in Twrp it seemed to actually fix them...I'm not sure exactly what I wiped or formatted that fixed the "E: can't find mount/cache" issues, so try everything.
So my ROM installed but I was still stuck on the white HTC logo. This is where I INSTALLED A NEW KERNEL THROUGH ADB. I wish I knew which kernel I installed, but I have like 10 and I just picked a random one. The point is if you're still stuck at a white HTC screen, install a new kernel.
So I got a recovery on the phone, and then I tried to S-Off again but I didn't have a good ROM installation so that was hanging at the HTC white screen. I then installed CleanROM DE 1.4 and I was able to boot into it, but ran into my initial problem of it crashing after dialing a number and entering infinite reboot. However, it would stay on just long enough for me to run ControlBear's program to S-Off.
So I S-Offed, I downloaded the Gingerbread RUU (the .exe version for Windows), I installed it, and now I can dial numbers and I'm all goodie again. Unfortunately, I honestly think the only way I was escaping my trouble was doing an S-Off, unless they leak a Ice Cream Sanwhich executable for Windows.
TL;DR Install Twerp 2.1 through adb, wipe everything, install CleanROM DE 1.4, install kernel S-Off, run Gingerbread RUU .exe
I bought the Amaze recently. I didn't like the battery life, so I looked for a remedy from the internet.
My search led me here. I found people changed kernels, disabled bloatware, and controlled CPU speeds. That all sounded great. I found newb-proof articles and tools for GB. [Caution: I'm am fresh off the newb canoe, now entering the Android rapids.]
I tried a few ROMs here. I enjoyed my experience with GB, but ICS was hyped to be so much better.
Once I tried to go to ICS, I found all of the guides didn't work for me.
I have read about a dozen articles here on how to do this process.
The last process I tried to move to ICS from rooted GB goes as follows:
Reset to factory, through bootloader (no backup; is that a problem?)
Put latest OTA file from Football to ext sd directory (not external card, only directory name)
Flash stock recovery
Relock boatloader
Reboot to recovery after taking battery out (to prevent security warning; would that matter?)
See a green refresh symbol then a red triangle (an apparent error)
I am not sure how to do this any better.
The next steps I would take are to unlock (thanks hassoon2000), flash twrp, wipe all cache, install NRG, use either TB or 4ext (suggestions welcome for any other backup program), get go launcher set (suggestions welcome for alternatives), then eat up the fancy sandwich.
If I missed that one post or one detail that you know of, then all the thanks button pushes go to you for your help.
Sent from my HTC_Amaze_4G using XDA Premium App
(Please forgive the double post, I couldn't figure how to edit old posts, now I can't figure how to delete posts.)
Rename ICS ruu from football to "PH85IMG" (u did NOT mention that u did this step) and put the .zip file on the root of your sd. Boot into "relocked" bootloader and push power button to select "bootloader" option.
There are SEVERAL THREADS that explain this.
Sent from my HTC_Amaze_4G
I meant to say I did that, too.
Sent from my HTC_Amaze_4G using XDA Premium App
parsjp said:
I meant to say I did that, too.
Sent from my HTC_Amaze_4G using XDA Premium App
Click to expand...
Click to collapse
Are u tmobile?
If not, search SuperCID thread for your fix
Sent from my HTC_Amaze_4G
I read as many as I could find.
I knew I would go to the bad side if I posted this, but I didn't want this to get lost in old posts.
Another point I forgot, I can't find the "root " folder anymore. I had it before I tried ICS OTA (tmo guy caught me off guard when he said to try the OTA ASAP)
Sent from my HTC_Amaze_4G using XDA Premium App
parsjp said:
I read as many as I could find.
I knew I would go to the bad side if I posted this, but I didn't want this to get lost in old posts.
Another point I forgot, I can't find the "root " folder anymore. I had it before I tried ICS OTA (tmo guy caught me off guard when he said to try the OTA ASAP)
Sent from my HTC_Amaze_4G using XDA Premium App
Click to expand...
Click to collapse
There is no "root" folder... That just means put on your sd card WITHOUT putting it in any folders. U never had a root folder. You need to read more. U obviously have no clue what u are doing. Learning should be do.e before wrecking your $500 phone... Not after
Sent from my HTC_Amaze_4G
1. Download the stock ruu from here
2. Lock your bootloader by using the fastboot command "fastboot oem lock"
3. Reboot to system
4. Flash the stock RUU you downloaded by placing it in the root of your external sd card and renaming it PH85IMG.zip and rebooting to bootloader.
5. Once you have the stock rom reinstalled, set the security lock by using fastboot command " fastboot oem writesecureflag 3
Click to expand...
Click to collapse
I followed the directions in the link in your sig as closely as I can.
I found I can't reboot into system after relocking the bootloader. I assume that's not expected.
Also, to flash the ruu, I need to boot into bootloader, then select recovery to flash. (the recovery leads to a screen that shows a green sync symbol that turns to a red triangle symbol)
Is that last step inferred?
I don't know if this will help, but I was in a similar situation and could not upgrade to ICS. I had clockworkmod and that seemed to be the issue. I had already restored a previous backup but could not flash a stock ruu. It would load and then return to the hboot menu without ever giving the option to install. The fix was to use hasoon's all in one tool to flash the stock recovery. That's all I did. After that the OTA update installed fine. I never relocked the bootloader.
I tried that out, too.
I have the same problem when my phone is relocked with stock or custom recovery. It never boots into system, only fastboot.
I tried it unlocked. It seemed to ast longer on the green refresh symbol, but still went to the red triangle.
The only difference here is that I don't have a backup to restore to like you did.
parsjp said:
I tried that out, too.
I have the same problem when my phone is relocked with stock or custom recovery. It never boots into system, only fastboot.
I tried it unlocked. It seemed to ast longer on the green refresh symbol, but still went to the red triangle.
The only difference here is that I don't have a backup to restore to like you did.
Click to expand...
Click to collapse
Which stock ruu are you trying to install? If it's a stock GB or one of the ICS leaks, rename the file PH85IMG and reboot into bootloader, if it takes you to fastboot volume down to select bootloader and hit power, if it's the stock ICS OTA file, then read my tutorial how to use it on stock recovery.
I used the 2.14.531.3 file from http://forum.xda-developers.com/showthread.php?t=1617644&highlight=ics+ota.
[I'll download it again, in case I had a bad download.]
I believe that is the latest OTA file for ICS.
Is the 1.43.531.3 the GB OTA or the ICS RUU?
I followed what you said:
flash stock recovery
relock phone (fastboot oem lock)
flash rom update in bootloader (rename ruu to ph85img.zip, place on sd card and boot to bootloader)
Click to expand...
Click to collapse
I do not have a separate mSD card (I have one on order), I used the phone's internal memory.
The other difference I see is I named it PH85IMG.zip.
I downloaded the 2.14.531.3 file again.
Named it ph85img.zip. Put it on the root of the internal memory.
Flashed stock recovery.
Relocked the bootloader.
Took the battery out to remove the security warning found on the bootloader after relocking.
Rebooted to bootloader (vol down + power button).
Selected bootloader, then recovery.
Green refresh symbol then red triangle.
Now it boots only into bootloader.
I am going to unlock then stay in my GB house for now.
[edit] I do not want to S-OFF as of right now, but I'm considering it more so than ever.
You didn't actually add the ".zip" did you? Because that's just the file extension and is already there. Rename to PH85IMG
Sent from my...
The Ultimate Guide to Everything Amaze-ing!(Amaze 4g BIBLE!) Updated Often
I did read about the .zip.zip troubles others had.
I have my extensions displayed, as to avoid that problem.
Fair point though.
Edit:
You don't need the stock recovery to go to stock. Just flash the stock ROM.
Click to expand...
Click to collapse
-hassoon2000 http://forum.xda-developers.com/showthread.php?t=1493905&page=29
That started me off in the right direction; details below. Huge thanks to all those that participated here and to NRG and hassoon2000!
DETAILS:
I got the AIO 3.2 tool (had 3.0). Flashed 4ext. Did a Nandroid, system, data and boot.img backup (why not choose all of them?); copied the files to my netbook. Got a 4gb (32 gb in the mail) msd card loaded with ph85img.zip (latest 4.0 RUU for TMo file)and put it in the card.
Used the "boot to bootloader" command. Selected the recovery option.
The phone did what everyone else talked about: the phone went through the update process. Never happened until now.
I didn't lay a brick! Wow, what a relief.
I couldn't find my TiBackup, but there wasn't much on my phone.
Now my NRG'd phone is all set.
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
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