Related
So after unlocking the boot loader today and loading up the stock rooted OTA rom my phone started randomly boot looping. It was sitting on my desk then randomly rebooted and now its been doing the same thing despite my best tries to fix it.
I had Amon Ra recovery installed initially, then flashed CWM via Rom manager. At this point I can't boot into recovery (or factory reset). It all happens very quickly, but it looks like the recovery menu loads up then the phone reboots. I am able to get into fastboot and reflash any of the recovery img's. I've tried the Amon Ra newest, the CWM normal and touch recovery and none of them will let me in. I've tried to get into recover with the 4G sim out and with the SD card out.
The phone does boot into an OS but after about 10 seconds it reboots. I did some digging and thought it might be the older bootloop issue with the network type. It does it with the sim out and in airplane mode so I'm not all that confident that its that issue.
At this point I am looking at tried to re-stock via Hboot RUU's. I have the P98IMG-1.02.605.6.zip on an SD card and that does flash but at the end of the verification it tells me "the main version is older." So I'm either looking for another package that will let me re-stock and give it a try again... or open to any other suggestions?
Hoping the phone isn't totally hosed, though based on what I can still get into I think there may be hope yet.
Anyone?
thanks in advance!
Have you tried CleanFlash? Also you are getting the mainver because you updated with the OTA. Google ruu_vigor. You are looking for the one that starts with 2.01.
Sent from my VTAB1008 using xda premium
This may help...
Get the 2.____.11 RUU from the 'Vigor Shipped' post in development. Follow the directions in the word file in post 2 from here:
http://forum.xda-developers.com/showthread.php?t=1487981
And then flash that RUU in HBOOT.
I had 99 problems with the RUU exe and spent the last week trying to get it to take. That tip to extract the PH file finally got me there. It fixed all kinds of issues for me and got me to stock.
Don't forget to relock.
(I think if you ran the ICS leak RUU you may still have issues, but you could follow those steps with that RUU as well probably and it would hopefully get you cleaned up)
Thanks for the help so far.
I got the newer RUU and got it flashed via hboot after i relocked. *edit* after the second time flashing it it seems to be working.
You guys rock.
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.
I am at my wits end here. This phone is driving me crazy. It seems like the only ROM's I can get to work are ones that use Aroma installer. I don't know what part of the Aroma installer is what makes it work, but I would really like to know because I want to try NeWt's and/or AOSP.
I am S-ON
I am on whatever firmware gets installed with the Nil's business ICS Sense 4.0 Aroma installer. (I don't know how to check my firmware, I imagine it's easy to check and/or install new firmware, but I can't seem to find a thread about firmwares anywhere. All I can find is Kernels/Roms)
I tried newt's first. I wiped everything, installed the rom. Then I rebooted to bootloader and did fastboot flash boot boot.img (the boot.img I pulled out of the rom's .zip) it flashed that, then I rebooted. The result: Stuck at HTC logo.
No idea what caused that, but I decided I'd go for ICS AOSP instead. I installed that, following the same process as above, and in this scenario I get stuck at the CM9 bootlogo infinitely (bootloop).
I'm sorry if I seem really frustrated, but honestly it's because I am. I've never had this much of a problem getting custom roms to work on any phone I've ever had. I really hope it's something I'm just missing, because I feel like a moron. I can't get any of these roms to even boot, and that's just sad...
PLEASE HELP!
bigbabys said:
I am at my wits end here. This phone is driving me crazy. It seems like the only ROM's I can get to work are ones that use Aroma installer. I don't know what part of the Aroma installer is what makes it work, but I would really like to know because I want to try NeWt's and/or AOSP.
I am S-ON
I am on whatever firmware gets installed with the Nil's business ICS Sense 4.0 Aroma installer. (I don't know how to check my firmware, I imagine it's easy to check and/or install new firmware, but I can't seem to find a thread about firmwares anywhere. All I can find is Kernels/Roms)
I tried newt's first. I wiped everything, installed the rom. Then I rebooted to bootloader and did fastboot flash boot boot.img (the boot.img I pulled out of the rom's .zip) it flashed that, then I rebooted. The result: Stuck at HTC logo.
No idea what caused that, but I decided I'd go for ICS AOSP instead. I installed that, following the same process as above, and in this scenario I get stuck at the CM9 bootlogo infinitely (bootloop).
I'm sorry if I seem really frustrated, but honestly it's because I am. I've never had this much of a problem getting custom roms to work on any phone I've ever had. I really hope it's something I'm just missing, because I feel like a moron. I can't get any of these roms to even boot, and that's just sad...
PLEASE HELP!
Click to expand...
Click to collapse
First off, no firmware will be installed with a rom, but this is a good place to start. With you being s-off, even a kernel won't be installed with a custom rom unless you flash the boot.img in hboot (or fastboot flash). My suspicion is that you are still on GB firmware. This can be alleviated by installing a patch. However, I think it in your best interest to re-lock, flash the newest RUU (found at androidpolice), and unlock again. That way, you will have updated to ICS firmware (therefore making it easier to run ICS based ROMS).
Do you have a working ROM right now that you can rever to so we can get some information off of it?
iamwalterwhite said:
First off, no firmware will be installed with a rom, but this is a good place to start. With you being s-off, even a kernel won't be installed with a custom rom unless you flash the boot.img in hboot (or fastboot flash). My suspicion is that you are still on GB firmware. This can be alleviated by installing a patch. However, I think it in your best interest to re-lock, flash the newest RUU (found at androidpolice), and unlock again. That way, you will have updated to ICS firmware (therefore making it easier to run ICS based ROMS).
Do you have a working ROM right now that you can rever to so we can get some information off of it?
Click to expand...
Click to collapse
Well, it's funny you should say that. I DID, or so I thought. I got fed up and restored a backup. How even my backup won't boot. I have no idea how that is even possible. Do I need to re-lock the device to install an RUU? What you are saying sounds like exactly what I need (to get on ICS firmware) so if you could tell me the easiest way to do that, I'll get started right away, haha.
Anyways, the backup I tried to restore was viper rez 1.03, and my hboot version is 2.11.0000. I cant' boot a rom at all.
bigbabys said:
Well, it's funny you should say that. I DID, or so I thought. I got fed up and restored a backup. How even my backup won't boot. I have no idea how that is even possible. Do I need to re-lock the device to install an RUU? What you are saying sounds like exactly what I need (to get on ICS firmware) so if you could tell me the easiest way to do that, I'll get started right away, haha.
Anyways, the backup I tried to restore was viper rez 1.03, and my hboot version is 2.11.0000. I cant' boot a rom at all.
Click to expand...
Click to collapse
If you can't boot a rom at all, then I can't tell you exactly which firmware you are on. With your hboot version, though, it looks like you are on GB firmware. Yes, you need to relock to run the RUU. Relock, run the RUU (found here: http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ ), unlock again, flash AR 3.15, then move onto ICS goodness.
iamwalterwhite said:
If you can't boot a rom at all, then I can't tell you exactly which firmware you are on. With your hboot version, though, it looks like you are on GB firmware. Yes, you need to relock to run the RUU. Relock, run the RUU (found here: http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ ), unlock again, flash AR 3.15, then move onto ICS goodness.
Click to expand...
Click to collapse
Ok, I relocked, put the PH98IMG on my sdcard, I loaded up the bootloader, pressed power, and it loaded PH98IMG.zip (took a while, said loading) then after it finished loading it said checking PH98IMG.zip (which also took a while) but after that, nothing happened. It just went back to the bootloader main menu... what am I doing wrong?
bigbabys said:
Ok, I relocked, put the PH98IMG on my sdcard, I loaded up the bootloader, pressed power, and it loaded PH98IMG.zip (took a while, said loading) then after it finished loading it said checking PH98IMG.zip (which also took a while) but after that, nothing happened. It just went back to the bootloader main menu... what am I doing wrong?
Click to expand...
Click to collapse
Wow, I just can't catch a break. Turns out, the RUU I downloaded was corrupt. So I got one that works, flashes the RUU, re-locked, reinstalled recovery, and flashed NeWt's and guess what. Hangs at HTC logo. WTF!
Edit: My hboot is 2.27.0000 now...
I just flashed that CM9 with the table being flipped over and it seems to boot okay. So I'm not sure what happened with newts. Oh well, I'm calling it a night. Been at this for over 5 hours (yea I know, that's insane)
bigbabys said:
Wow, I just can't catch a break. Turns out, the RUU I downloaded was corrupt. So I got one that works, flashes the RUU, re-locked, reinstalled recovery, and flashed NeWt's and guess what. Hangs at HTC logo. WTF!
Edit: My hboot is 2.27.0000 now...
I just flashed that CM9 with the table being flipped over and it seems to boot okay. So I'm not sure what happened with newts. Oh well, I'm calling it a night. Been at this for over 5 hours (yea I know, that's insane)
Click to expand...
Click to collapse
You didn't say if you flashed the boot.img from Newt? You should have if you are s-on.
bigbabys said:
Wow, I just can't catch a break. Turns out, the RUU I downloaded was corrupt. So I got one that works, flashes the RUU, re-locked, reinstalled recovery, and flashed NeWt's and guess what. Hangs at HTC logo. WTF!
Edit: My hboot is 2.27.0000 now...
I just flashed that CM9 with the table being flipped over and it seems to boot okay. So I'm not sure what happened with newts. Oh well, I'm calling it a night. Been at this for over 5 hours (yea I know, that's insane)
Click to expand...
Click to collapse
Hahaha, "CM9 with the table flipped over"! I'm sure that's how you felt after 5 hours. Not to make light of how frustrating that can be, but I'm glad you've got something working again.
topgun1953 said:
You didn't say if you flashed the boot.img from Newt? You should have if you are s-on.
Click to expand...
Click to collapse
For both installs, I did a flashboot boot amonrarecovery.img so that it could write to the boot partition. (A nifty little trick courtesy of scotty over at androidforums.com ) however, not wanting to rule out the possibility that maybe that little trick was the cause of the issue, I extraced the boot.img and did a fastboot flash boot boot.img to make sure. However it still was hanging at the HTC logo. That's when I tried the cm9 rom, and used the trick, and it worked fine.
I have no idea why NeWtS didnt' work for me. I can't post in the thread specifically for it yet, but as far as I know I did everything correct this time, so I'm at a loss.
iamwalterwhite said:
Hahaha, "CM9 with the table flipped over"! I'm sure that's how you felt after 5 hours. Not to make light of how frustrating that can be, but I'm glad you've got something working again.
Click to expand...
Click to collapse
Oh believe me, I'm just as glad My original plan was to flash a ROM real fast before going out with some friends. I figured worst case scenario I could flash a backup. But I didn't realize you can't restore a nandroid from recovery if you are S-ON without manually writing the boot image again. So I made myself a nice paperweight and spent the entire night fixing it I'd like to find out what went wrong with NeWts, but to be honest I tinkered with cm9 most of last night and I think I'm happy with it. It's so smooth. And to be honest, I have low expecations for every sense rom now since every single one I tried has the autofocus issue.
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
I had been running CM10.0 for a while when it decided to lose my internal SD card. I think it has somethin gto do with TWRP and unmounting/remounting sdcards. In any case... I decided to flash CM10.1 just because it would be something to do and maybe it would solve the problem.
It got stuck at the splash screen.
I flashed back to CM10.0 and cleared cache/dalvik and got the same result. At this point I was S-On.
I re-locked and RUU'd. Everything seemed to work fine (including the sdcard issue). Sweet .
I unlocked it (HTC-Dev), flashed TWRP 2.4.4.0, flashed CM10.1 and it gets stuck on the splash screen.
Long story short, I RUU'd and updated everything OTA (1210 radio, etc).
I then used dirty Racun (with Baby Racun) and wen't S-Off.
This put me at 2.09 (was there already) and radio 1119, with S-Off.
I then flashed TWRP 2.4.4.0 again...
So ....
I'm S-Off, Unlocked, Radio 1119, HBoot 2.09, 3.15.651.16...
If I flash CM10.1, then Gapps from 20130312 I still get stuck at the cm boot screen. Same thing happens with the latest nightly, the M2 and the 10.0 that I was running before.
Any ideas? I've serached the forum (the best I could... I can't get any results unless I try to make a thread and just take a look at the "related results" it comes up with)...
I just tried flashing the boot.img from the CM10.1 nightly through fastboot directly and nothing doing. Same issue.
So I was in the middle of running the RUU found at unlimited.io here --> (Won't let me post a URL yet... The 2.09 RUU anyway...) which I've done a few times during this project to get back to a stock ROM. I just do a few of the middle steps starting with locking the device and it happened to reboot into the OS instead of fastboot this time when I locked it...
And it booted into CM10.1...
WTH?
Well whatever... Anyway...
I'm going to make a backup and then try to unlock (HTC Dev token) the recovery and then if that works I'll be good to go...
Weird...
I know this is a little late, but did you try flashing another ROM besides CM? It shouldn't matter, really...just a thought.
How long were you stuck at the boot animation? Did you try using an older twrp?
Sent from my EVO using xda premium
Thank you for the reply...
Once I got into CM10.1 I realized I couldn't send texts... so I messed around with APN's etc, and finally came across an "error 16..." thread that indicated that my phone had been newly locked out of the sprint network due to the S-Off state. So I called Sprint and had that solved in a few moments...
But I had already RUU'd and updated everything to stock, S-Off, re-locked...
So I thought "Sweet... now that I know what that solution is I'll go for CM10.1 again..."
Now I'm stuck at the boot screen again . I tried what seemed to have worked before (fastboot oem relock) and that doesn't seem to have done the trick this time.
Still kicking at it though .
To answer you questions... I tried TWRP 2.4.4.0 and TWRP 2.3.1.0, and as far as how long it sat in the boot animation... I left until the battery died once...