Related
I had my wife's EVO 3D working fine on VipeRom2.1 I think and when i tried to update it to 2.5 it went into a reboot loop. I cleared everything by formatting the system and clearing the cache and data and nothing. I tried a different rom, MeanRom and same thing. Right before it seems like it is going to get me to the unlock screen, reboot. I can get into the bootloader and the recovery just fine but no matter what i install, reboot, reboot, reboot.
Evo 3D
twrp 1.03
Recovery 2e
HBOOT 1.5
Any assistance would be greatly appreciated.
jschauf said:
I had my wife's EVO 3D working fine on VipeRom2.1 I think and when i tried to update it to 2.5 it went into a reboot loop. I cleared everything by formatting the system and clearing the cache and data and nothing. I tried a different rom, MeanRom and same thing. Right before it seems like it is going to get me to the unlock screen, reboot. I can get into the bootloader and the recovery just fine but no matter what i install, reboot, reboot, reboot.
Evo 3D
twrp 1.03
Recovery 2e
HBOOT 1.5
Any assistance would be greatly appreciated.
Click to expand...
Click to collapse
What software is your phone on ? The 2.08 or 2.17?
jschauf said:
I had my wife's EVO 3D working fine on VipeRom2.1 I think and when i tried to update it to 2.5 it went into a reboot loop. I cleared everything by formatting the system and clearing the cache and data and nothing. I tried a different rom, MeanRom and same thing. Right before it seems like it is going to get me to the unlock screen, reboot. I can get into the bootloader and the recovery just fine but no matter what i install, reboot, reboot, reboot.
Evo 3D
twrp 1.03
Recovery 2e
HBOOT 1.5
Any assistance would be greatly appreciated.
Click to expand...
Click to collapse
Did you change/update your radios at all?
I am not sure of the software version. I tried going back to unrooted stock with RUU_Shooter_U_HTC_ARA_1.24.415.2_Radio_10.55.9020.00_10.13.9020.29_M_release_208706_signed and it gave me a version error.
I am running radio 0.97.10.0808 according to the relocked screen that I am getting while trying to restore to unlocked sprint stock.
And now I see the difference in radio and the version in the restore file.
Thanks for the assistance, my Epic Touch 4g has been so simple to tinker with, this thing is a pain in the rear.
The RUU you installed was for the GSM version of the phone, re-run the CDMA version. The GSM version is called Shooter_U whereas the sprint version is just called Shooter.
I'm guessing this would be a good place to start?
http://www.scottsroms.com/downloads.php?do=cat&id=4
I will try this one when I get home today. Hopefully I can get it back stock and then start over and get a functional custom ROM working.
The wife was not to happy I blew up her phone yesterday trying to update it, I am guessing she is not going to let me "fix" it again.
Yupp, install one of them, not sure which one will allow you to do the HTC unlock though.
I think I figured out what I did wrong in the first place. Someone please correct me if I am wrong. I forgot that 1.5 S-ON can't just install the ROM from the standard recovery method like I can with my Epic Touch 4G. I think I need follow the "How to Flash Any ROM or Kernel You Want" instructions from http://forum.xda-developers.com/showthread.php?t=1239821. I just booted to recovery and tried to install the ROM. Does this sound about right?
jschauf said:
I think I figured out what I did wrong in the first place. Someone please correct me if I am wrong. I forgot that 1.5 S-ON can't just install the ROM from the standard recovery method like I can with my Epic Touch 4G. I think I need follow the "How to Flash Any ROM or Kernel You Want" instructions from http://forum.xda-developers.com/showthread.php?t=1239821. I just booted to recovery and tried to install the ROM. Does this sound about right?
Click to expand...
Click to collapse
I didn't look at the link you posted. But with hboot 1.5 you can not write to the boot partition from recovery. In order to do this you need to extract the boot img from the ROM your gonna flash and fastboot flash boot boot.img then fastboot boot recovery.img will take you to recovery and flash ROM from there
Sent from my PG86100 using XDA App
mteezey said:
I didn't look at the link you posted. But with hboot 1.5 you can not write to the boot partition from recovery. In order to do this you need to extract the boot img from the ROM your gonna flash and fastboot flash boot boot.img then fastboot boot recovery.img will take you to recovery and flash ROM from there
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
You actually dont need to do both. If you just do a fastboot boot recovery.img it will give you complete access, including flashing the kernal. So after you type that command, it will load a the custom recovery and when you flash the rom, it will flash the kernel included with the rom as well. FYI you need to do a fastboot boot recovery.img each time you want to flash a kernel. If you arent changing kernals then you can just go into recovery as you normally would and flash a rom. If you want to flash a kernal without hooking up to a computer, then read into Flash Image GUI.
JayDaKissEP said:
You actually dont need to do both. If you just do a fastboot boot recovery.img it will give you complete access, including flashing the kernal. So after you type that command, it will load a the custom recovery and when you flash the rom, it will flash the kernel included with the rom as well. FYI you need to do a fastboot boot recovery.img each time you want to flash a kernel. If you arent changing kernals then you can just go into recovery as you normally would and flash a rom. If you want to flash a kernal without hooking up to a computer, then read into Flash Image GUI.
Click to expand...
Click to collapse
This is what I thought, The first one I tried was the newest version of ViperRom. I first tried to just flash over top of the existing rom with the hope I would not have to reset everything and make her start over with how she had it setup, I guess the newest version had a newer kernel. Hopefully I am able to get it back to a functional state this afternoon.
jschauf said:
This is what I thought, The first one I tried was the newest version of ViperRom. I first tried to just flash over top of the existing rom with the hope I would not have to reset everything and make her start over with how she had it setup, I guess the newest version had a newer kernel. Hopefully I am able to get it back to a functional state this afternoon.
Click to expand...
Click to collapse
I believe that does have the anthrax kernel havent downloadedthe new version. However i know some people have been having problems with roms that are based off the new OTA if their phones still have the old firmware. Definatly flash teh kernel/boot via fastboot recovery that should take care of the problem.
Correction not anthrax.
I got everything back working yesterday, I guess doing it correct the first time will save me some headache. I just need to remeber to start recovery from windows instead of from the bootloader screen. Thanks for the assistance.
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
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.
Actually, that's a lie, it does boot, kind of.
HTC Evo 3D GSM.
So I've been S-ON since unlocking my phone. I'm not exactly new to this but this has stumped me. It begun as a problem that affected Android 4.0.4 ROMs only, but it's just happened to my usual ROM, Predator Unity 3D.
I always flash the kernel using fastboot.
HBOOT 1.49.0018, using Revolutionary CWR 4.0.1.4
Basically, it starts to boot. HTC logo on a white screen, then it goes onto a backlighted blank screen, then turns off. Then it turns on again and repeats the process, automatically.
I've tried a lot of stuff, and while putting on PredatorUnity3D again to install a new recovery via an apk, it started doing this on this ROM too. I always wipe data, cache, dalvik cache before installing a new ROM.
So I'd appreciate the help.
I know that it has worked in the past being S-on, but I highly recommend getting s-off. Almost everybody who has had issues with bootlooping like yours (showing the HTC Logo and then rebooting) had the issue go away when the flashed the ROM while s-off.
Just installed Adrenaline 2.0 ROM (http://forum.xda-developers.com/showthread.php?t=1787428&highlight=stuck), following directions to flash in recovery.
I didnt clearly see it stated that the rom did or didnt require a wipe, so to be safe i wiped anyway and did a factory reset just to be sure.
After flashing in recovery, i flashed the S-ON Kernel from post 3, and follow directions to install in hboot.
I can still get into recovery, however now when booting phone sits at the HTC Quietly Rooted screen.
Attempted restoring NAND backup, but phone hangs at the original ICS OTA boot screen "Quietly Brilliant"
Any help is greatly appreciated!
should i just give up and flash a different rom?
Im looking for something thats senseless, running ICS and has good battery life. Any recommendations?
What you are running into are kernel issues. I suggest you S-OFF and you can flash any rom and nand will work for the kernel.
isolatedvirus said:
Just installed Adrenaline 2.0 ROM (http://forum.xda-developers.com/showthread.php?t=1787428&highlight=stuck), following directions to flash in recovery.
I didnt clearly see it stated that the rom did or didnt require a wipe, so to be safe i wiped anyway and did a factory reset just to be sure.
After flashing in recovery, i flashed the S-ON Kernel from post 3, and follow directions to install in hboot.
I can still get into recovery, however now when booting phone sits at the HTC Quietly Rooted screen.
Attempted restoring NAND backup, but phone hangs at the original ICS OTA boot screen "Quietly Brilliant"
Any help is greatly appreciated!
Click to expand...
Click to collapse
it's a lot easier to go into the downloaded rom file. double click on it to enter it, copy the boot.img file and copy it to your adb folder on your pc. if you need more detailed instructions check out post #4: ▼▼▼
http://www.droidforums.net/forum/ht...unlocking-rooting-roming-faq.html#post2083204
jahrize said:
it's a lot easier to go into the downloaded rom file. double click on it to enter it, copy the boot.img file and copy it to your adb folder on your pc. if you need more detailed instructions check out post #4: ▼▼▼
Click to expand...
Click to collapse
thread you linked me to was extremely informative, helped me fix my issue.
And to the user whom suggested i go S-OFF, i definitely plan on doing it, since it seems the benefits far outweigh the cons.
Thanks for the help! My rezound is now up and running like the champ it is xD
If you decide you want someo.e to walk you thru the procedure hit me up on gtalk I'll be more than willing to walk you thru it..
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
famouscollin said:
If you decide you want someo.e to walk you thru the procedure hit me up on gtalk I'll be more than willing to walk you thru it..
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
Click to expand...
Click to collapse
definitely will do. Ill probably contact you either next week or weekend (depending on my schedule)
Thanks for the offer, i appreciate it.
S-ON flashing procedures
isolatedvirus said:
Just installed Adrenaline 2.0 ROM (http://forum.xda-developers.com/showthread.php?t=1787428&highlight=stuck), following directions to flash in recovery.
I didnt clearly see it stated that the rom did or didnt require a wipe, so to be safe i wiped anyway and did a factory reset just to be sure.
After flashing in recovery, i flashed the S-ON Kernel from post 3, and follow directions to install in hboot.
I can still get into recovery, however now when booting phone sits at the HTC Quietly Rooted screen.
Attempted restoring NAND backup, but phone hangs at the original ICS OTA boot screen "Quietly Brilliant"
Any help is greatly appreciated!
Click to expand...
Click to collapse
Sometimes that issue is caused by not having cleared cache and dalvik cache between ROM versions, but you did that with a full wipe. I am S-On too and here is my procedure for flashing a new ROM, hope it helps. Just replace RAGE with Adrenaline or your rom name.
1) Make Nandroid Backup / Backup System and User Apps in Titanium Backup
2) Full Wipe in Amon Ra
3) Flash Latest Version of RAGE in Amon Ra
4) Flash boot.img extracted from RAGE zip
5) Reboot
6) Once verifying everything booted OK, go back to amon ra and flash Neo's latest inverted gapps package
7) Reinstall Titanium Backup, restore User Apps but not system apps.
8) in TiBu, restore system data such as dialer storage on a per-app basis.
isolatedvirus said:
Just installed Adrenaline 2.0 ROM (http://forum.xda-developers.com/showthread.php?t=1787428&highlight=stuck), following directions to flash in recovery.
I didnt clearly see it stated that the rom did or didnt require a wipe, so to be safe i wiped anyway and did a factory reset just to be sure.
After flashing in recovery, i flashed the S-ON Kernel from post 3, and follow directions to install in hboot.
I can still get into recovery, however now when booting phone sits at the HTC Quietly Rooted screen.
Attempted restoring NAND backup, but phone hangs at the original ICS OTA boot screen "Quietly Brilliant"
Any help is greatly appreciated!
Click to expand...
Click to collapse
Did you fastboot flash the boot.img? I believe I had the same issue and that's what I did. But I'm not sure. Maybe someone else can chime in.