Related
Hello,
I have flashed to Cyanogenmod successfully via fastboot USB method. Has worked for a week. Now my phone just reboots. Figured it was the ROM, so did fastboot USB method again to install Synergy ROM (latest). The GUI didn't even finish loading, and it rebooted. Flashed back to Cyanogenmod, same thing. I've wiped before EACH flash.
I am so lost and wish to revert back to stock ROM and do this all over again, HOWEVER, I've done RUU recovery method from Sprint and it doesn't work. Loading the PG86IMG.zip from the root of the SD card doesn't really render results.
I've checked forums, and really couldn't find a solid way of doing this. If I missed or overlooked something, please point me to it and I'll gladly read it.
I am running HBOOT 1.50, which has been widely been perceived as a royal pain. I bought the phone used and came like that.
How would I do this?
alucardromero said:
Hello,
I have flashed to Cyanogenmod successfully via fastboot USB method. Has worked for a week. Now my phone just reboots. Figured it was the ROM, so did fastboot USB method again to install Synergy ROM (latest). The GUI didn't even finish loading, and it rebooted. Flashed back to Cyanogenmod, same thing. I've wiped before EACH flash.
I am so lost and wish to revert back to stock ROM and do this all over again, HOWEVER, I've done RUU recovery method from Sprint and it doesn't work. Loading the PG86IMG.zip from the root of the SD card doesn't really render results.
I've checked forums, and really couldn't find a solid way of doing this. If I missed or overlooked something, please point me to it and I'll gladly read it.
I am running HBOOT 1.50, which has been widely been perceived as a royal pain. I bought the phone used and came like that.
How would I do this?
Click to expand...
Click to collapse
If you wish to revert back to stock, loading the RUU is the best method.
Can you elaborate on what error you received you tried loading the PG86IMG.zip through the bootloader?
RUU are found here: http://goo-inside.me/shooter/ruu
Yep, I used that one. I don't get an error. It reads it ( obviously by the progress bar ) but doesn't give me an option to update or anything. Just passes it by as if it wasn't there.
*slaps head* I shouldn't have messed with this phone at all.
Also, I did managed to lock up the phone again. I used Sprint RUU again, successful. However, I still have boot loops as the GUI loads in Android.
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.
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.
Hello All,
Here is my situation - hopefully there is someone out there that can give me a little help.
I unlocked the boot loader using HTC method, installed TWRP, and then SuperSU. I did a backup with the TWRP, everything was working ok - except I kept getting an error message about the binaries being out of date on the SuperSu. Every time I tried to update them the the update would fail. So.... I went to the play store and installed an updated SuperSu, still no luck same issue.
About that time in the middle of a reboot - the phone got to the white HTC screen and just froze. Finally held the power button down till it started to reboot - got it into recovery and restored the backup. Same issue - goes to white screen and stops - I have left it for over a half hour -nothing...???
I have tried multiple ways of restoring the backup as far as wiping the cach, ect - still nothing.
Help!
Here is a quick update on this
I can still get into recovery - I can mount the sd card and transfer to it and I can still use ADB. so... I found a stock rom flash that was 3.15.651.6 copied it to the sd card then flashed it. Now the phone continually tries to boot reboot, gets to the white screen before going into fast boot - freezes then reboots itself.
Is it a brick? Any suggestions?
What is your hboot version? Are you s-off? What version of twrp are you on, and more importantly, where did you get the twrp from?
Thanks for responding!
HBOOT - 2.09.0000
S-On
TWRP - 2.4.1.0
Radio 1.13.11.0030
OpenDSP-v31.1.0.45.0015 EMMC-Boot
I got the TWRP from a Windriod setup I had used previously to set up old 4g lte about a year ago.
At this point I would be happy to just put it all back stock and then start over. I have never used a RUU but I have read you can install them from fastboot after running a few commands to make it recognize the phone. Has anyone ever done that?
Also - how would I know I was getting the correct RUU for this phone and where would I get it from?
When you're s-on, you have to flash the kernel separately, via adb fastboot.
I think that's what's keeping your phone from booting. Save a copy of the zip to your pc. Unzip the file, then flash the boot.img to your phone while it's in fastboot.
It should boot just fine now. But for the love of God, get s-off afterwards. You might also want to ruu to the new partition format, but that's a matter of preference.
Well , unfortunately that didn't do it.
I have tried a couple of times and also reloaded the zip and re-flashed. I think the problem is that if you watch TWRP as it is installing the zip - it gets to "installing kernel" and then crashes and reboots. I didn't notice it the first time, I thought it was finishing and rebooting but is actually crashing.
Ideas??
Wonder if I could make my own zip file without the kernel folder and flash that?
Or maybe its time to RUU through flashboot and start over?
MrBillH said:
Wonder if I could make my own zip file without the kernel folder and flash that?
Or maybe its time to RUU through flashboot and start over?
Click to expand...
Click to collapse
I would RUU to the most recent Android version and get S-off if I were you.
I have never used the RUU before, I have a couple of questions about it
1) Can you RUU through fastboot
2) How would I know what version to use and where can I get one that I know is good?
MrBillH said:
I have never used the RUU before, I have a couple of questions about it
1) Can you RUU through fastboot
2) How would I know what version to use and where can I get one that I know is good?
Click to expand...
Click to collapse
1) Yes you can.
2) Click the top link in my sig. Scroll down to the bottom of the first post and look for the link to the Android 4.3 RUU. For installation instructions refer to the RUU section in the same post.
Perfect! Thank you vey much - phone is up and flying again!
I am now unlocked with twrp 2.4.1.0 and SuperSu 2.16
I also updated the software after the RUU to 3.17.651.9.7 - what method of S-off would you recommend and where can I find it?
Sounds like you used the wrong RUU, but at any rate, so long as your phone is up and running, that's all that matters. Hit the top link in my sig again and find the S-off method that corresponds to your current firmware version (Rumrunner or Firewater should work). Links to both exploits are provided in the thread.