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.
Hey, I hope you guys can help me out.
I have a rezound here, that is bootlooping. It will stay booted into android for maybe 15 seconds then freezes, and reboots. I searched and saw a fix that involved changing the phone setting to CDMA/LTE evda Auto, and it was already apparently on that setting.
It wasn't letting me factory reset it, even from the bootloader menu. It would look like it was factory resetting, but then still not be factory reset. The only way I could get it to factory reset was by unlocking the bootloader through HTC DEV...but that didn't fix the issue. (Warranty was already void anyway because the void screw was tampered with)
What should I try next? I've flashed a rom on an evo 3d where I had to load a custom recovery through the bootloader, so I figured there was probably something similar on the rezound...but this has S-ON and revolutionary doesn't seem to available for rezound yet...and I don't think I could flash clockwork quick enough since it freezes after like 10-15 seconds.
Any input? I'd really like to get this phone working...thanks!
Once you unlock you should install Amon Ra recovery with fastboot. The thread is http://forum.xda-developers.com/showthread.php?t=1339679
Well I flashed recovery via fastboot, and flashed CleanRom ICS (after loading the one zip file needed prior to flashing ICS Roms, and of course after backup and after wiping everything a few times) and its the same thing...gets into android and reboots after 10 seconds or so.
gdawson6 said:
Well I flashed recovery via fastboot, and flashed CleanRom ICS (after loading the one zip file needed prior to flashing ICS Roms, and of course after backup and after wiping everything a few times) and its the same thing...gets into android and reboots after 10 seconds or so.
Click to expand...
Click to collapse
Im having the same problem. I have tried several different roms at this point and my phone is still bootlooping..
Anyone got any ideas?? Im desperate to get this thing working!
Have you guys tried to manually install the kernel from fastboot?
phylo1 said:
Im having the same problem. I have tried several different roms at this point and my phone is still bootlooping..
Anyone got any ideas?? Im desperate to get this thing working!
Click to expand...
Click to collapse
Just boot to bootloader and run the ruu for 2.11 from windows or figureout how to get the ph98img.zip of gingerbread or one of the leaks onto the root of the sdcard and flash that in the bootloader. If not s-off you should still be able to lock the bootloader using adb.
The reboots should NOT be affecting the bootloader or flash a backup from recovery. Just start fresh.
Sent from my ADR6425LVW using Tapatalk 2
Run an RUU. EXE version is preferable.
Hello all, I need some help if there are any ideas what could be going on with this phone. I can usually fix my own phone problems, but this one has stumped me...
I bought a rezound dirt cheap that was stuck on the white HTC screen and would not boot into the stock rom. At the time I bought it, it was s-on and I could get in the HBOOT and run fastboot commands.
Since buying it, I have tried many things to get this thing working. I've tried to RUU (with PH98IMG and .exe) and apparently after it completes it is once again in a boot loop on the white HTC screen. I have been able to unlock and flash a custom recovery onto it (amon-ra) and install any cm/aokp rom onto it and boot into that. The only issue with that is when in the rom, my wifi and bluetooth will not connect at all. It wont even toggle on in settings and it is not greyed out. 4G and everything else seems to work ok.
At this time, I'm thinking there is some kind of hardware failure but I'm open to suggestions.
In summary...
I have been able to s-off
I have tried different firmware combos of HBOOTs/radios
I have flashed custom recoveries and roms and can boot into them without wifi or bluetooth
I have been unsuccessful to RUU to anything stock, it'll just boot loop the white HTC screen
Right now, I have installed Tron 2.1 onto it. I did notice post:http://forum.xda-developers.com/showthread.php?t=2272781&highlight=no+wifi
When I go into system/lib, there was no /modules folder. I went ahead and created it and put in bcmdhd.ko and rebooted, but still no go. I'm not sure why the /modules folder was missing, but this reaches the extent of my knowledge on what is supposed to be there.
I believe I have tried everything and done fairly thorough searches to get this phone working properly and am at a loss what to do next. If anybody has a thought of something to try, I'm all for it. Fortunately if this phone doesnt work out, its not a big deal to me.
I don't want this to sound like another "stuck on HTC screen" thread. I have been through all those and this doesn't seem like the same problem.
Your help is greatly appreciated!
tacoman said:
Hello all, I need some help if there are any ideas what could be going on with this phone. I can usually fix my own phone problems, but this one has stumped me...
I bought a rezound dirt cheap that was stuck on the white HTC screen and would not boot into the stock rom. At the time I bought it, it was s-on and I could get in the HBOOT and run fastboot commands.
Since buying it, I have tried many things to get this thing working. I've tried to RUU (with PH98IMG and .exe) and apparently after it completes it is once again in a boot loop on the white HTC screen. I have been able to unlock and flash a custom recovery onto it (amon-ra) and install any cm/aokp rom onto it and boot into that. The only issue with that is when in the rom, my wifi and bluetooth will not connect at all. It wont even toggle on in settings and it is not greyed out. 4G and everything else seems to work ok.
At this time, I'm thinking there is some kind of hardware failure but I'm open to suggestions.
In summary...
I have been able to s-off
I have tried different firmware combos of HBOOTs/radios
I have flashed custom recoveries and roms and can boot into them without wifi or bluetooth
I have been unsuccessful to RUU to anything stock, it'll just boot loop the white HTC screen
Right now, I have installed Tron 2.1 onto it. I did notice post:http://forum.xda-developers.com/showthread.php?t=2272781&highlight=no+wifi
When I go into system/lib, there was no /modules folder. I went ahead and created it and put in bcmdhd.ko and rebooted, but still no go. I'm not sure why the /modules folder was missing, but this reaches the extent of my knowledge on what is supposed to be there.
I believe I have tried everything and done fairly thorough searches to get this phone working properly and am at a loss what to do next. If anybody has a thought of something to try, I'm all for it. Fortunately if this phone doesnt work out, its not a big deal to me.
I don't want this to sound like another "stuck on HTC screen" thread. I have been through all those and this doesn't seem like the same problem.
Your help is greatly appreciated!
Click to expand...
Click to collapse
i would like you to do the following.
flash this http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
2 times. it will make sure we have a solid base to work on.
after that has ran 2 times. boot into the stock rom one time.
after that flash this https://dl.dropboxusercontent.com/u/12405441/new.global.firm.PH98IMG.zip
once this is done let it boot into the rom.
from here you should be good to flash any rom that is out there to date. (note please dont restore any system data, only app data)
ALSO MAKE SURE YOU HAVE 100% battery. doing an ruu can brick the phone if its interrupted.
report back when done
Thanks for replying. I have flashed that RUU several times in a row in the past, but I'm redownloading it now to make sure my copy isnt corrupt. Earlier experience when I double flashed this it still remained a white HTC screen loop.
Currently estimated at 6hrs to download, so I wont be able to reply for a bit with my findings...
tacoman said:
Thanks for replying. I have flashed that RUU several times in a row in the past, but I'm redownloading it now to make sure my copy isnt corrupt. Earlier experience when I double flashed this it still remained a white HTC screen loop.
Currently estimated at 6hrs to download, so I wont be able to reply for a bit with my findings...
Click to expand...
Click to collapse
When the Rezound first came out a bunch of people had boot loop problems because the phone was set to wcdma or some such thing instead of cdma. I'm just a noob hack but that's my memory of it. The cure was to boot without the back cover on which contains the antenna and then change the setting.
Ok, I have re downloaded the AndroidPolice RUU and flashed twice, but was not able to boot into it no matter how long I waited (20 min+). It would just loop the HTC white screen. I then went ahead and flashed your global update firmware and have the same result after waiting (20 min+), it just loops the HTC white screen.
I have tried this process several times last night, but still no progress.
As the phone sits now:
*** UNLOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
tacoman said:
Ok, I have re downloaded the AndroidPolice RUU and flashed twice, but was not able to boot into it no matter how long I waited (20 min+). It would just loop the HTC white screen. I then went ahead and flashed your global update firmware and have the same result after waiting (20 min+), it just loops the HTC white screen.
I have tried this process several times last night, but still no progress.
As the phone sits now:
*** UNLOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
Click to expand...
Click to collapse
You need stock recovery and a locked bootloader
- "Is it dark in there?"
drynyks said:
You need stock recovery and a locked bootloader
- "Is it dark in there?"
Click to expand...
Click to collapse
S/he ran the RUU so they are stock.
Sounds like the symptoms of a kernel issue. Try pulling the boot.img from this stock OTA ROM and flashing it.
http://forum.xda-developers.com/showthread.php?t=2260154
fastboot flash boot boot.img
I have the exact same you. Been this way for months. Maybe once a month BT/Wifi will turn on but only for a few hours maybe. Phone will reboot itself and come back up with the 2 broken again.
feralicious said:
S/he ran the RUU so they are stock.
Sounds like the symptoms of a kernel issue. Try pulling the boot.img from this stock OTA ROM and flashing it.
http://forum.xda-developers.com/showthread.php?t=2260154
fastboot flash boot boot.img
Click to expand...
Click to collapse
Well I finally booted into stock sense after flashing that boot.img which is a big step from before. For a brief moment, it saw wifi networks in my office but when I went to connect to one, wifi died and it no longer sees any wifi network. Bluetooth appears to still be an issue as well, i.e. will not turn on.
Flyhalf205 said:
I have the exact same you. Been this way for months. Maybe once a month BT/Wifi will turn on but only for a few hours maybe. Phone will reboot itself and come back up with the 2 broken again.
Click to expand...
Click to collapse
Unfortunatly that doesnt sound very good for me if you've been battling this wifi/BT problem for months.
synisterwolf said:
i would like you to do the following.
flash this http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
2 times. it will make sure we have a solid base to work on.
after that has ran 2 times. boot into the stock rom one time.
after that flash this https://dl.dropboxusercontent.com/u/12405441/new.global.firm.PH98IMG.zip
once this is done let it boot into the rom.
from here you should be good to flash any rom that is out there to date. (note please dont restore any system data, only app data)
ALSO MAKE SURE YOU HAVE 100% battery. doing an ruu can brick the phone if its interrupted.
report back when done
Click to expand...
Click to collapse
can you explain what you mean by flash the ruu twice once I have saved it to the root of my sd card? Does that just mean get to the bootloader, watch as it reads the the ph98img file and let it do that twice, or do I need to reboot in between, or do I need to put in a command?
fivedezs said:
can you explain what you mean by flash the ruu twice once I have saved it to the root of my sd card? Does that just mean get to the bootloader, watch as it reads the the ph98img file and let it do that twice, or do I need to reboot in between, or do I need to put in a command?
Click to expand...
Click to collapse
when you let hboot flash the zip, the first time is super short. it updates hboot, stock recovery, and splash i think. then it will reboot back to bootloader and ask to be flashed again. this time it will take some time to update because it does the whole system.
---------- Post added at 08:25 AM ---------- Previous post was at 08:24 AM ----------
tacoman said:
Well I finally booted into stock sense after flashing that boot.img which is a big step from before. For a brief moment, it saw wifi networks in my office but when I went to connect to one, wifi died and it no longer sees any wifi network. Bluetooth appears to still be an issue as well, i.e. will not turn on.
Click to expand...
Click to collapse
something doesnt seem right. the RUU would have flashed the boot.img for you. can you link me to the downloaded ruu that you have? also before you run the ruu did you do fastboot oem lock the bootloader?
Edit:
i remember an old trick from the inc days. after the RUU boot back into hboot and do a "factory reset" then boot into the phone. it use to fix the radio errors somewhere getting after a RUU. no clue why we did it. it just worked. try that when you are on stock recovery locked bootloader
Here is the RUU I have re downloaded. It was also the original I used in the past on my other Rezound
https://www.dropbox.com/s/1570h8l0ba1u7qp/rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
I have also tried the RUU 3.14.605.12.exe and a couple other different RUU versions, but have the same issue with that as well. Even on MicroMod777's OTA-Global-Stock-4.05.605.14 710RD-Rooted 5/1/13 flashed through amon-ra, I get the bootloop. I have done these as locked and unlocked bootloader with no difference. I have also tried the factory reset with locked bootloader.... no go with that either.
I was only able to finally boot in to stock by fastboot flashing the boot.img, and that is where this phone sits now. My major issue at this point is I dont have wifi or bluetooth and have dug through numerous posts and tried different things, and nothing is working on it. What was strange as I said in my previous post, the very first time I was able to boot into stock sense by flashing the boot.img, it briefly saw wifi networks but disappeared and disabled as soon as I tried to connect to one. I have not been able to replicate that since then.
On a sidenote and possibly related, since this phone has been sitting at my desk I decided to try and flash Newt's NOS JB v1.0.0 ROM and it bootloops also at the droid eye screen. I never was able to get it going on this phone. My other rezound boots this just fine.
I think I have reached the limits of my android knowledge of what to try on this thing. I am satisfied with it not having wifi/bluetooth since my wife wont be using those features. I would like to understand what the heck is going on though.
Ok, I will try to give as much info as I can, please let me know if there is anything else I should provide. I really appreciate any help and advice as I've been pulling my hair out for the last 3 days, spending 10+ hours trying to get my Amaze back working.
Problem started a few days ago, phone shut off, when it powered back on it was stuck on the White HTC logo. That same day the phone died completely and would not power on at all, not even the amber light. Eventually the amber light would blink the but phone wouldn't charge. I fixed this first issue by jump starting the battery with a 9V battery, something someone suggested on a thread. Worked great to get the phone charging again... but that's it. So basically I have access to the HBOOT/Fastboot and EXT4 Recovery menu's, and there is no OS on the phone, I know for sure now because I wiped the system.
When I try (but fail) to install the RUU 1.41 exe, and it checks the phone, i comes back saying my "current" version on the phone is 2.14.661.2 even though there isn't any OS on there...
Bit more background info. I purchased this phone last year off someone, it was running 4.1.2 and the bootloader was unlocked. It *is S-ON though.
Whatever else this guy did, I'm not sure as this is what I can tell, however the CID pulls up as Telus001? which the guy did tell me it was a Telus phone.
So I'm trying to load the Telus stock rom and I've been getting nowhere and pulling my hair out. I'm 10hrs in and no further then I was. So first I downloaded the Telus RUU 1.41 exe from the stock rom but it gives an Error 43. I tried this with both the bootloader locked again, and unlocked. I then downloaded the OTA 2.14.661 zip from the stock roms, and renamed it to PH85IMG, stuck that on the Ext SD card. Problem is when it boots into the HBOOT it actually see's the file, loads it, then checks it, but then returns me to the main menu. I don't get promted to update. Now I've tried this too with the bootloader unlocked, and locked. So a third go, I extracted the Rom from the 1.41 RUU and made that PH85IMG, tossed it onto the SD card and again this time it actually went further but gave another error.
I have tried to Sideload the above Roms through recovery but they give error's.
In that All In One program there is an option to fix the Mainver error, however when I run that all I get is "Device not found". The phone IS loaded under device manager as HTC Phone as I had installed the drivers. I've tried to google this fix but I can't get anywhere.
Everyone has said on forums that sticking a PH85IMG.zip file on an Ex SD and having it boot into the HBOOT menu will rebuild the phone, but I'm out of idea's how to get there because it loads the rom's, checks them, and then boots me back to the menu. There is only 2 Rom's I can find for Telus, and that's the 1.41 EXE or the OTA 2.14.661.2. My HBOOT version is 1.93.0002, RUBY PVT SHIP S-ON RL.
Thanks in advance for any help/suggestions, desperately just want my phone working again. I feel like I've been to the 4 corner's of google trying to solve this problem.
Strange This should not happen.Also if your phone is running 4.1.2 which should be a custom then that means your phone was updated to ics so the ruu.exe will fail.if you have access to 4ext recovery then you can flash any custom rom to boot your phone.But if you want stock and both of the stock roms for your carrier is not working then the only thing you can do is s-off the phone then use supercid so you can flash any carrier's rom then flash t-mobile ics stock.Tell me if this worked for you.
darkshadow1997 said:
Strange This should not happen.Also if your phone is running 4.1.2 which should be a custom then that means your phone was updated to ics so the ruu.exe will fail.if you have access to 4ext recovery then you can flash any custom rom to boot your phone.But if you want stock and both of the stock roms for your carrier is not working then the only thing you can do is s-off the phone then use supercid so you can flash any carrier's rom then flash t-mobile ics stock.Tell me if this worked for you.
Click to expand...
Click to collapse
Got it going!! Thanks for the suggestions. What did it in the end was this thread --> http://forum.xda-developers.com/showpost.php?p=27058110
I had EXT4 Recovery already, so I used his Zip and just flashed that. Phone came back up and is running great now... if only I had found his thread before the hr's and hr's I've been googling and trying things.