I went to upgrade to the new Revolution ICS kernel a few days ago, my Amaze had already been rooted from HTC on the stock kernel & rom, with CWM (xboarder56).
I believe I made a procedural mistake and corrupted the Rom. So, I tried to start from scratch. But everything I try and do won't get me a boot from anything I do. I tried replaced the stock rom and ICS rom from loading PH85IMG.zip in Hboot. I thought maybe it was a kernel issue, and tried loading the Faux 0.0.8, Stock 1.43 (tmobile), and 1.46 kernels.
I can't even get into CWM now. I don't know what I did but I've been reading the forum for days and still haven't gotten anywhere. The trackball on my backup nexus one is on its way out, not sure how much longer it'll last!
Anyone have any suggestions? I think my next attempt will be flashboot CWM -> stock gingerbread rom -> lock bootloader, and start from scratch.
You don't flash the PH85IMG.zip in recovery...it needs to he flashed in Hboot. There are SOOOOOOO many tutorials about upgrading to the new ICS and can't believe how you botched the upgrade.
So if you can get into Hboot then you're still safe.
Wait....I sent this with Tapatalk?
I did flash PH85IMG.zip in Hboot, I said recovery referring to hboot. Sorry for the confusion.
After loading the RUU from Hboot you should Re-UNlock the bootloader and flash a recovery. Because flashing th RUU in Hboot removes the custom recovery. After you have successfully reflashed a recovery then flash your Rom.
Wait....I sent this with Tapatalk?
Double0EK said:
After loading the RUU from Hboot you should Re-UNlock the bootloader and flash a recovery. Because flashing th RUU in Hboot removes the custom recovery. After you have successfully reflashed a recovery then flash your Rom.
Wait....I sent this with Tapatalk?
Click to expand...
Click to collapse
Thanks bud, that makes sense. I got it working now. Appreciate your help!
Related
ok so i was running leedroid 5.4 with leedroids kernel, on my evo 3d GSM with hboot .0011 Unlocked and S-ON.....things were fine untill i tried to flash some other roms like shooterbeats and infected eternity rom, i was not able to get past the boot logo on both of those roms so i thought maybe it has something to do with my s-on....so i decided to make it s-off....after reading s_superman's thread for about 2 hours on how to downgrade hboot to .007 or 8 and unlock using revolutionary....i gave it a go, and did so sucessfully NOW MY HBOOT IS .007 with S-OFF using revolutionary and CWM but i am not able to FLASH ANY ROMz ON some roms my phone hangs on BOOT logo, and on some roms it restarts after LOGO appears........its really frustrating after so much hard work ,,,what i get in return is this...feel like throwin it outta window....ANY HELP WILL BE MUCH APPRECIATED ON HOW TO RESOLVE THIS issue?
now in recovery it shows "revolutionary HBOOT 1.49.1107 S-OFF RL"
well fortunately for you, sir, all is not lost....
flash twrp recovery 1.1.1.... just to get a start.
i have never had one single issue with twrp 1.1.1. if you are s-off, you can now flash kernels through recovery.
quick recap, flash twrp 1.1.1, reflash ROM, and kernel. both of which from recovery. if you still have booting issues, flash the kernel through adb.
do that, then come back and we'll go from there.
cobraboy85 said:
well fortunately for you, sir, all is not lost....
flash twrp recovery 1.1.1.... just to get a start.
i have never had one single issue with twrp 1.1.1. if you are s-off, you can now flash kernels through recovery.
quick recap, flash twrp 1.1.1, reflash ROM, and kernel. both of which from recovery. if you still have booting issues, flash the kernel through adb.
do that, then come back and we'll go from there.
Click to expand...
Click to collapse
Problem fixed by flashing the same RUU which i used to downgrade hboot before unlocking it with revolutionary, idk how ..but it fixed it...now all is good.... nd in recovery mode... it says "UNLOCKED" WHERE IT used to say revolutionary ....hboot 007 s-off........i didnt know what i was doing ..just wanted to brick it to death so i reflashed that image unexpectedly it fixed everything thanks anyway
You need 4ext custom recovery and yes twrp has issue's
Sent From my EVO 3D x515m s off using xda premium
If I am on gb can I flash the new ics ruu without doing anything else? I have an unlocked bootloader with s-off.
tkryan said:
If I am on gb can I flash the new ics ruu without doing anything else? I have an unlocked bootloader with s-off.
Click to expand...
Click to collapse
It's not technically a RUU but yeah since you're s-off you can flash it. If you're looking to just get the firmware you can flash the separately also.
yes
I installed and everything installed ok but now it just keeps flashing white HTC boot screen.
tkryan said:
I installed and everything installed ok but now it just keeps flashing white HTC boot screen.
Click to expand...
Click to collapse
Did you flash the ZIP file twice in a row? Apparently flashing the PHXXXXX.zip files for ICS don't install everything completely the first time around, you need to do it twice to have a complete install.
It did install twice. I bought this phone used and it already was unlocked with s-off but wifi wasnt working. I was able to flash the gb ruu and the phone is working again but wifi is still broke. I really need somebody that knows what they are doing to tell me what the person before me did. I have had no success flashing other roms either.
Do a factory reset. That should clear up the wifi issue.
I did that with no luck.
Sent from my ADR6350 using XDA
I don't understand why I can flash a gb ruu but not an ics ruu.
Sent from my ADR6350 using XDA
Post what your hboot says at the top of it.
Sent from my ADR6425LVW using xda premium
Unlocked
Vigor PVT SHIP S-OFF RL
HBoot 2.11.0000
Radio 0.95.00.1118r/0.95.00.1223r
OpenDSP-v10.6.0.7611.00.0919
eMMC-boot
Yes you can flash the RUU. Then after that use the jbear modified hboot and you can flash kernels and recoveries via fastboot without having to unlock the bootloader.
I already tried flashing the newest ics ruu and my phone would just keep rebooting from the white HTC screen. I even tried a factory reset.
Every rom I try to flash I just get boot loops. I just installed clean rom with gingerbread patch and it will boot up, then restart, then act like it is going to work and then restart. It even gets to activating and then just keeps rebooting.
The bootloop sounds like a kernel issue, but if you are installing the RUU it should be fine. Maybe you have a bad download. Did you check the MD5?
Hey guys, my 3VO hasn't been acting right lately. I was having trouble booting Agrabrens latest CM10 build for CDMA, it bootlooped, but then i was able to run it again later without issue. Now my phone is having trouble running ICS based Sense roms, the roms bootloop. None of these roms have a 1.58 hboot requirement and i'm running eng hboot. Lately my phone only can run AOSP/AOSP based roms(except for at least one i've tried) without bootloops. Does anyone know what the problem could be?
Juanito216 said:
Hey guys, my 3VO hasn't been acting right lately. I was having trouble booting Agrabrens latest CM10 build for CDMA, it bootlooped, but then i was able to run it again later without issue. Now my phone is having trouble running ICS based Sense roms, the roms bootloop. None of these roms have a 1.58 hboot requirement and i'm running eng hboot. Laterly my phone only can run AOSP/AOSP based roms(except for at least one i've tried) without bootloops. Does anyone know what the problem could be?
Click to expand...
Click to collapse
Sounds like Sense is mad at you for trying AOSP ROM's.
I'm assuming you are S-OFF since you mentioned the ENG bootloader, but have you flashed the 2.89.651.2 (Sprint ICS) firmware yet? My preference would be to flash the whole RUU if you haven't already and then reflash recovery, but there is a .zip file in Virus's OTA thread that contains only the firmware, including hboot 1.58, that can be flashed from your current bootloader. You can always go back to the ENG bootloader once you get past this problem.
ramjet73
Does your recovery bootloop as well? What recovery on are you on?
Details, details.
Mobilemodz said:
Does your recovery bootloop as well? What recovery on are you on?
Details, details.
Click to expand...
Click to collapse
Recovery wouldnt have anything to do with his bootloops unless you flashed the a mod, kernel, or theme that doesnt play nice with the Rom. Like ramjet said, its more than likely a firmware and or hboot issue. Go with ramjet and try his solution.
ramjet73 said:
Sounds like Sense is mad at you for trying AOSP ROM's.
I'm assuming you are S-OFF since you mentioned the ENG bootloader, but have you flashed the 2.89.651.2 (Sprint ICS) firmware yet? My preference would be to flash the whole RUU if you haven't already and then reflash recovery, but there is a .zip file in Virus's OTA thread that contains only the firmware, including hboot 1.58, that can be flashed from your current bootloader. You can always go back to the ENG bootloader once you get past this problem.
ramjet73
Click to expand...
Click to collapse
Thanks bro, flashing the newest boot helped. Iinm I used Viruses zip. Now I'm back on eng hboot.
Sent from my PG86100 using Tapatalk 2
damn im in the same boat right now, tried virus zip and no luck......continuous boot loop.
riassan said:
damn im in the same boat right now, tried virus zip and no luck......continuous boot loop.
Click to expand...
Click to collapse
Edit: for this puppy back in business has to flash full ruu as you mentioned ramjet73 and not I'm 1.58 s-off locked, which really doesn't matter since I can just flash PG86IMG and go back to eng hboot.
Sent from my Galaxy Nexus using xda premium
I don't want to be giving my friend the wrong information. When his sprint 3d was boot 1.5 I took it and soff it for him downgrading to 1.4. Now recently he upgraded to hboot 1.58 and it says relocked at the top. Of course he still has recovery and still is rooted.
My question is since his phone is soff can't he just still flash whatever with no issues? Does he have to do dev unlock again?
I own a rezound and have had many HTC devices and soff has always been the key to everything for me. Any help would be appreciated
With s-off there's no need to unlock his boot loader again. (For example) If he wants to flash an aosp rom, all he's gotta do is downgrade his hboot via boot loader.
Perfect. Already installed JP bear latest hboot and went to twrp. Making a backup now. That's what I was thinking but I wanted some confirmation. Its been a while since I messed with an Evo 3d
Hmmm. It won't flash paranoid android. Even tried the 1.04 eng hboot. Any ideas? Using twrp recovery. Latest radios and 1.04 eng hboot.
stkiswr said:
Hmmm. It won't flash paranoid android. Even tried the 1.04 eng hboot. Any ideas? Using twrp recovery. Latest radios and 1.04 eng hboot.
Click to expand...
Click to collapse
A lot of people have had better luck with 4EXT on the Evo 3D. You can download the Recovery Updater for free from the www.4ext.net website and install the current version of 4EXT Recovery from that app. Then "format all partitions except SD card" in the wipe/format menu of the recovery, and try flashing PA again.
ramjet73
ramjet73 said:
A lot of people have had better luck with 4EXT on the Evo 3D. You can download the Recovery Updater for free from the www.4ext.net website and install the current version of 4EXT Recovery from that app. Then "format all partitions except SD card" in the wipe/format menu of the recovery, and try flashing PA again.
ramjet73
Click to expand...
Click to collapse
K. I'm working on that now. I let you know soon its backing up now. Thank you for the heads up. Do you think I should go back yo the latest jbear hboot? Or just leave the 1.04 eng hboot? He wants to be able to run these jellybean builds that are out
stkiswr said:
K. I'm working on that now. I let you know soon its backing up now. Thank you for the heads up. Do you think I should go back yo the latest jbear hboot? Or just leave the 1.04 eng hboot? He wants to be able to run these jellybean builds that are out
Click to expand...
Click to collapse
Stay with the ENG 1.04 hboot for now. The GB and AOSP based ROM's won't boot with the latest JBear (1.58.5858) so if you want to use a JBear version 1.50.5050 is better.
ramjet73
ramjet73 said:
Stay with the ENG 1.04 hboot for now. The GB and AOSP based ROM's won't boot with the latest JBear (1.58.5858) so if you want to use a JBear version 1.50.5050 is better.
ramjet73
Click to expand...
Click to collapse
Wow thank you for all the help. I just did everything and unfortunately it is just stuck in a never ending splash loop. Doesn't seem like the kernel/boot is being flashed. Made a backup so I should be good. Just sucks doing all the steps and being stuck.
What kernel are you flashing with pa?
Jsparta26 said:
What kernel are you flashing with pa?
Click to expand...
Click to collapse
It doesn't come with a kernel?
stkiswr said:
Wow thank you for all the help. I just did everything and unfortunately it is just stuck in a never ending splash loop. Doesn't seem like the kernel/boot is being flashed. Made a backup so I should be good. Just sucks doing all the steps and being stuck.
Click to expand...
Click to collapse
Are you doing the "format all partitions except SD card" in 4EXT right before flashing the ROM? Make sure to give it plenty of time to boot since sometimes the first boot can take up to 10 minutes.
ramjet73
stkiswr said:
It doesn't come with a kernel?
Click to expand...
Click to collapse
Well go with ramjets suggestion and try format all partitions minus sdcard along with full factory data wipe and cache/dalvik wipe and see if it boots up all the way.( it couldn't hurt to do all the wipes two or three times before you flash the rom). Just to make sure everything was wiped all the way.
Oh yeah. Step by step . It just never gets past splash. I looked into the ROM downloaded and saw a boot IMG but it really seems like a boot issue. Doesn't make a lot of sense to me. Soff, everything in right place, correct recovery and no boot. Not complaining, he still has his backup he is running and it restores backup correctly.
His phone was soff and he upgraded firmware to the 1.58 so it said locked in hboot. I just flashed 3 dif bootloader with no issues. Its def soff.
Ok, try flashing a different kernel. Try the Mac kernel that's located in Mazda's aokp jb thread. I believe buttered toast came with pa that your trying to flash. It could also be a bad download as well. You could always redownload the rom as well to see if that works. You never know about these things sometimes.
stkiswr said:
Oh yeah. Step by step . It just never gets past splash. I looked into the ROM downloaded and saw a boot IMG but it really seems like a boot issue. Doesn't make a lot of sense to me. Soff, everything in right place, correct recovery and no boot. Not complaining, he still has his backup he is running and it restores backup correctly.
His phone was soff and he upgraded firmware to the 1.58 so it said locked in hboot. I just flashed 3 dif bootloader with no issues. Its def soff.
Click to expand...
Click to collapse
You've tried all the standard stuff to get AOSP ROM's to boot on the Evo 3D. At this point I can only suggest that you flash the 2.89.651.2 SPrint ICS RUU from here, then reflash a custom bootloader and recovery. That will make sure everything is in sync and has cleared up this problem for other users.
You don't need to relock the bootloader (although I think you said it is already relocked) when flashing the RUU if the phone is S-OFF.
ramjet73
Yes, I will try to download ROM again and also grab that kernel.
I soff this phone for him when it was hboot 1.50. Then I reverted to 1.40 via brick method to get it soff. He has ran some form of an hboot/radios update because he was told to do that. Now we are working together and I am trying to fix all his stuff and get him setup correctly. I have an soff rezound and am sure his phone isn't seeing the boot.IMG.
Now today his phone said locked or relocked am not sure. I went ahead an changed his hboot to a recommended 1.04eng hboot. Installed 4ext recovery via the app that was linked. I am downloading gangam style cm10 to test just to see if something will boot. It successfully flashed a sense based ROM and booted fine thru an aroma installer that came with the ROM. In the installer I stated it was soff and had no issues. I will try the ROM and it doesn't boot I will jump back to recovery and flash a kernel and see. Thanks very much for all the help
Well, I have done it all. Not much more I can do. He may try to run the ICS ruu later but I just can't get any cm10 jb based ROM to boot. Y'all have been more than helpful catching me back up to speed on the 3d and while I agree this should be flashing alas it is not booting. I am positive its just not accepting the boot img for what ever reason because it never makes it far enough after reboot from recovery. Just endless quick splash screen reboots.
No problem. I just wanted to add that a lot of users are having weird issues with paranoid android. ( I'm subscribed to the thread) so it could be that your phone doesn't like pa for some reason. ( Not a diss on Lens Flare at All) but he's been having some issues with the rom and is more than likely trying to work on it. Hopefully you can get gangnam style up and running or even aokp jb. If none of these work, I would go with ramjets suggestion and run a ruu and then back to Asop.
Edit: guess you already tried them. Hopefully you get some better luck after you try the ruu method. Good luck.
Ok, I don't consider myself too much of a noob, I have rooted my old droid incredible many times...however,
I tried rooting my rezound today and believe I was successful at least in getting my bootloader unlocked...(using Hasoon's AIO kit v3.1)
I tried loading aokp rom and it just stuck on the white HTC screen..I can get into hboot, I tried rebooting many times..I downloaded
RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00.1123r_3161E_9K_QMR_release_233635_signed.zip and copied it to the sd card, renamed it PH98IMG.zip and tried re-flashing to the same stuck white HTC screen.
I am starting to freak out and wish I didn't have to ask for help here, but I am at the end of the rope and don't know what else to do...
Any kind souls out there that can help me?
Thanks in advance...
Being stuck at the white screen means the kernel didn't load when you installed the rom. I'm assuming your phone is still s-on. You need to flash the kernel seperate from the rom using fastboot. Extract the boot.img from the rom zip and flash it from your PC, I believe the option is there in the all in one tool.
If you wan to run the RUU, you need to re-lock your bootloader first and flash it through the bootloader, not recovery.
mjones73 said:
Being stuck at the white screen means the kernel didn't load when you installed the rom. I'm assuming your phone is still s-on. You need to flash the kernel seperate from the rom using fastboot. Extract the boot.img from the rom zip and flash it from your PC, I believe the option is there in the all in one tool.
If you wan to run the RUU, you need to re-lock your bootloader first and flash it through the bootloader, not recovery.
Click to expand...
Click to collapse
Ok, Thanks a ton!!! Will try that now!
Correction-=-
The boot.img flashing DID work...
Now I just have to find the correct stock ROM... The one I tried said it was too old during the recovery...
any thoughts....Any links to a solid recent stock ROM??
Thanks again!!
Edit: ignore me, posted in wrong thread
If you want to stick with Sense 3.6, I recommend this one - http://forum.xda-developers.com/showthread.php?t=1855605
I've download stock one for my rezound from android police website.
Edit: there is the latest one there, v. 4.xx maybe.
Sent From Rezound S-off rooted VenomRez ROM
drumrjoe said:
Correction-=-
The boot.img flashing DID work...
Now I just have to find the correct stock ROM... The one I tried said it was too old during the recovery...
any thoughts....Any links to a solid recent stock ROM??.
Thanks again!!
Click to expand...
Click to collapse
If you want the latest official RUU, here is a link:
(the RUU you tried to use above was a GB one)
http://androidfiles.org/ruu/?dir=Vigor Grab 3.14.605.12
There was a recent OTA to take it to .13 but it's not really necessary.
If you want to go to the global leak RUU here is a link:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Since you are s-on, if you go to the global leak you won't be able to go back to anything official unless you s-off.
The above will have Verizon bloat, so if you want something stock without bloat you can look through the ROMs. I think there's a couple in there.