Related
Hello,
I have an unlocked EVO 3D with HBOOT 1.5 S-on.
I flashed the phone and replaced InfectedRom with Warm Two Point Three. After installing new rom and reseting, phone is now stuck on HTC startup screen.
Please help!!! I appreciate and welcome all feedback. Thank you
kongfooey said:
Hello,
I have an unlocked EVO 3D with HBOOT 1.5 S-on.
I flashed the phone and replaced InfectedRom with Warm Two Point Three. After installing new rom and reseting, phone is now stuck on HTC startup screen.
Please help!!! I appreciate and welcome all feedback. Thank you
Click to expand...
Click to collapse
Did you wipe all the way? Also what is your software 2.17 or 2.08 ? Did you fastboot boot recovery.img when you flashed?
kongfooey said:
Hello,
I have an unlocked EVO 3D with HBOOT 1.5 S-on.
I flashed the phone and replaced InfectedRom with Warm Two Point Three. After installing new rom and reseting, phone is now stuck on HTC startup screen.
Please help!!! I appreciate and welcome all feedback. Thank you
Click to expand...
Click to collapse
You need to flash boot.img/kernel using fastboot or Flash image GUI or else you will face issues if the ROM uses kernel other than your current one.
This is the limitation of HTC unlock method (S-ON)
mnomaanw said:
You need to flash boot.img/kernel using fastboot or Flash image GUI or else you will face issues if the ROM uses kernel other than your current one.
This is the limitation of HTC unlock method (S-ON)
Click to expand...
Click to collapse
Thank you!
I flashed the boot.img using fastboot as you suggested. Now the phone is stuck in an endless loop between powering off and the HTC startup logo.
It appears that I am getting closer to fixing the problem but I am still stuck. Can you help further please?
Thanks again!
mnomaanw said:
You need to flash boot.img/kernel using fastboot or Flash image GUI or else you will face issues if the ROM uses kernel other than your current one.
This is the limitation of HTC unlock method (S-ON)
Click to expand...
Click to collapse
Thanks for your reply.
I did wipe all the way. How do I tell whether I have 2.08 or 2.17. if the phone not able to start up?
I flashed boot.img using fastboot. I just realized that the bootloader when doing and Hboot tries to load the image indicates no image or wrong image.
I am either missing a step or did something wrong.
Please help!
did you make a backup of Infected before you flashed?
When you say you installed Warm did you install and actually get it fully booted and set up your home screens and all that and it only stuck on the first reboot after? or was it right after you flashed warm?
Really if you made a backup of infected or what you were running before you should be able to restore that via recovery then boot up normal. Then use FlashImageGUI to flash the kernel needed for Warm, then reboot into recovery mode and flash the other portion of the Rom from the custom recovery.
Unfortunately, I did not back up Infected or other previous roms. I didn't know that I should, I only backed up my apps using Titanium. I now know better.
Still stuck in loop mode. I have been searching the forums for some possible solutions but so far nothing has worked.
I am up the creek without a paddle...
kongfooey said:
I used Titanium Backup to back up apps etc. is that the same as backing up the rom (Infected)?
If I had the backup how do I recover using recovery? I have been reading other posts in the forum and have tried some of the suggestions. I wiped the data and cache.
I am up the creek without a paddle...
Click to expand...
Click to collapse
na TiBackup isn't the same as backing up the Rom itself.
Full backups are done from within the custom recovery...
the boot.img you pushed via fastboot earlier. where did you get it from?
Silly me... I realized that Titanium backup was not the correct backup after I posted.
I took the image from the Warm zip file. I initially thought the problem was fixed until I realized that the phone is in an endless loop...
Still looping
kongfooey said:
Silly me... I realized that Titanium backup was not the correct backup after I posted.
I took the image from the Warm zip file. I initially thought the problem was fixed until I realized that the phone is in an endless loop...
Still looping
Click to expand...
Click to collapse
well to be honest I would just go back and start form scratch at this point since pushing the kernel via fastboot somehow didn't take for you nor did clearing cache's after the fact.
after pushing the kernel via fastboot, have you tried doing that again, and then going into recovery and flashing the rom again? If that doesn't work you might as well just go back to stock and push stock kernel flash stock rooted OTA, boot up, and use FlashImageGUI to push the Warm kernel then go back to flashing the Warm rom in recovery...
really before pushing the stock kernel if you wanna test to see if your initial push of Warm kernel even took fully just fully wipe data and try flashing infected again in recovery. If it boots fine then you know your fastboot push didn't take before to begin with...
Edit:
before i even really get more into this. does Warm even use another kernel beside the stock one? If they dont then all of this could of resulted from a bad download of the rom itself being flashed...
Sgt. Slaughter, I salute you...
I played around with your suggestions. Got it working... I flashed a different boot.img and it solved the problem. I may have gotten a bad Warm rom...
Thanks again!!!
Note: if you took/installed the latest update (2.17.651.5) you won't be able to use roms based off earlier firmware/kernels (ie 2.08.651.2 or 651.3) b/c of kernel differences (I think I've read that somewhere).
I believe Warmtwopointthree and Infected are not using the latest base/kernel.
Edit: saw you posted right before me. So what kernel/boot.img did you use?
kongfooey said:
Sgt. Slaughter, I salute you...
I played around with your suggestions. Got it working... I flashed a different boot.img and it solved the problem. I may have gotten a bad Warm rom...
Thanks again!!!
Click to expand...
Click to collapse
Nice good to hear. Fact you had your phone even semi-booting makes solving anything wrong with it usually trial and error and ends up not being so bad to fix...
I used boot.img from OTXE Titan HD ODEXed New Beats!
I need to educate myself a bit more about the differences between kernel and .imgs etc...
Thanks for your response. I greatly appreciate!!
I'm having a very similar issue, I rooted my Evo using Revolutionary and installed CW Recovery and everything was fine so I tried installing ZR3D and part way through the install, my phone turned off and now it wont get past the HTC boot screen. I went into CW Recovery but nothing is working, no matter what option I choose [even Turn off phone or reboot] it gives me the CW logo but nothing happens.
I have HBOOT 1.49.1107 with S-Off
Try reflashing your recovery threw hboot.
#Root-Hack_Mod*Always\
StoneCold448 said:
I'm having a very similar issue, I rooted my Evo using Revolutionary and installed CW Recovery and everything was fine so I tried installing ZR3D and part way through the install, my phone turned off and now it wont get past the HTC boot screen. I went into CW Recovery but nothing is working, no matter what option I choose [even Turn off phone or reboot] it gives me the CW logo but nothing happens.
I have HBOOT 1.49.1107 with S-Off
Click to expand...
Click to collapse
Can you boot into Fast boot? If so, try connecting your phone to a computer and flashing a recovery through there. Then try to install the ROM.
Sent from my PG86100 using Tapatalk 2 Beta-6
coal686 said:
Can you boot into Fast boot? If so, try connecting your phone to a computer and flashing a recovery through there. Then try to install the ROM.
Click to expand...
Click to collapse
Thanks for your help
If I did the wire trick to get s-off how will flashing the latest RUU affect me? Wanted to try the latest Ineffabilis rom, but they say you should flash the RUU first. Can someone give me a run down of how this should work? I am unlocked, s-off, ICS firmware, amon ra recovery.
jaxsin said:
If I did the wire trick to get s-off how will flashing the latest RUU affect me? Wanted to try the latest Ineffabilis rom, but they say you should flash the RUU first. Can someone give me a run down of how this should work? I am unlocked, s-off, ICS firmware, amon ra recovery.
Click to expand...
Click to collapse
S-off won't affect your flashing any RUU. Just download the RUU you want to run , put on the external SD card rename to PHIMG98.zip then reboot to bootloader. Press power to access fastboot menu , it will then find the RUU and read it then ask it you want to update. Select volume up to choose yes and let it do its thing. It should automatically run twice , because the first time it just installs the stock recovery, and 2 other parts. Second time it installs the rest including radio's and system image.
When finally done it should reboot and you will be on the stock RUU that you ran. After that , just reflash a custom recovery and either restore a backup rom or flash the rom of your choice.
jaxsin said:
If I did the wire trick to get s-off how will flashing the latest RUU affect me? Wanted to try the latest Ineffabilis rom, but they say you should flash the RUU first. Can someone give me a run down of how this should work? I am unlocked, s-off, ICS firmware, amon ra recovery.
Click to expand...
Click to collapse
mjh68 said:
S-off won't affect your flashing any RUU. Just download the RUU you want to run , put on the external SD card rename to PHIMG98.zip then reboot to bootloader. Press power to access fastboot menu , it will then find the RUU and read it then ask it you want to update. Select volume up to choose yes and let it do its thing. It should automatically run twice , because the first time it just installs the stock recovery, and 2 other parts. Second time it installs the rest including radio's and system image.
When finally done it should reboot and you will be on the stock RUU that you ran. After that , just reflash a custom recovery and either restore a backup rom or flash the rom of your choice.
Click to expand...
Click to collapse
great explanation of how the ruu process is done. One thing to add, back up internal sd before doing this because it will be wiped.
Just to double check, I don't need to lock the phone before flashing RUU?
jaxsin said:
Just to double check, I don't need to lock the phone before flashing RUU?
Click to expand...
Click to collapse
No, the modified jb will let you flash it.
Sent from my ADR6425LVW using Tapatalk 2
So I used a superwipe for the first time in about 6months and now i cant install ROMs. Whenever it boots it goes into a constant bootloop, all i can do is restore backups now. Any Help?
NexusS4gFreak said:
So I used a superwipe for the first time in about 6months and now i cant install ROMs. Whenever it boots it goes into a constant bootloop, all i can do is restore backups now. Any Help?
Click to expand...
Click to collapse
Have you tried doing a normal recovery full wipe or reflashing the recovery?
When that happened to me, I had to flash the ruu.exe. If you're s-off, I recommend it.
Jsparta26 said:
Have you tried doing a normal recovery full wipe or reflashing the recovery?
Click to expand...
Click to collapse
Yes i tried both of them, none worked.
coal686 said:
When that happened to me, I had to flash the ruu.exe. If you're s-off, I recommend it.
Click to expand...
Click to collapse
Can i just run it or do i have to unroot?
NexusS4gFreak said:
Can i just run it or do i have to unroot?
Click to expand...
Click to collapse
It will unroot itself in the process but you can always flash your recovery again and gain root back by flashing your ROM.
NexusS4gFreak said:
Can i just run it or do i have to unroot?
Click to expand...
Click to collapse
Like jsparta said, you lose root when you run it because it puts everything back to stock. But you still remain s-off. So you just have to flash custom hboot, flash custom recovery, and flash custom Rom and you're back in business.
coal686 said:
Like jsparta said, you lose root when you run it because it puts everything back to stock. But you still remain s-off. So you just have to flash custom hboot, flash custom recovery, and flash custom Rom and you're back in business.
Click to expand...
Click to collapse
Cant run RUU, says unknown error and find correct RUU. Im on ViperROM r304
try flashing a new rom+kernel via fastboot
NexusS4gFreak said:
Cant run RUU, says unknown error and find correct RUU. Im on ViperROM r304
Click to expand...
Click to collapse
If I remember right, you're cdma, so try the ruu from ramjet's zip file here: http://forum.xda-developers.com/showthread.php?t=1889438
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 installed the 4.03.605.2 Global RUU per Nils instructions for flashing his ICS ROM, and for some reason I cannot get to the bootloader by pressing down and power now (I even tried up and power, no luck). Luckily I was able to get to it and recovery through ADB so I could complete installation of the ROM. Anyone have any idea why this would be happening? Anything in particular I should look for? I can still get to it through the power menu on the ROM, but it'd be nice to get to the bootloader the normal way in case I ever need to and I don't have access to a computer with adb on it.
Phone is S-ON, bootloader says h-boot 2.27.0000
radio 2.22.10.0801r/2.22.10.0803r
Recovery is AmonRa 3.15
rboddy said:
I installed the 4.03.605.2 Global RUU per Nils instructions for flashing his ICS ROM, and for some reason I cannot get to the bootloader by pressing down and power now (I even tried up and power, no luck). Luckily I was able to get to it and recovery through ADB so I could complete installation of the ROM. Anyone have any idea why this would be happening? Anything in particular I should look for? I can still get to it through the power menu on the ROM, but it'd be nice to get to the bootloader the normal way in case I ever need to and I don't have access to a computer with adb on it.
Phone is S-ON, bootloader says h-boot 2.27.0000
radio 2.22.10.0801r/2.22.10.0803r
Recovery is AmonRa 3.15
Click to expand...
Click to collapse
i would re run the ruu. when you installed it, did it remove amonra? if not then it didnt install correctly.
it should run 2 times.
Ok I'll give that a whirl. Would I be ok backing up my current ROM, running the RUU, then restoring the nand backup? I'm assuming yes, but just figured I'd ask anyways.
rboddy said:
Ok I'll give that a whirl. Would I be ok backing up my current ROM, running the RUU, then restoring the nand backup? I'm assuming yes, but just figured I'd ask anyways.
Click to expand...
Click to collapse
i wouldnt recomend it. thats when the bugs show their face. normally it would be ok but a big update like this i would say do a fresh install of the rom after the ruu and restore data for user apps only.