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.
Related
I bought an evo 3d from a guy today off craiglist and he gave it to me with MIUI loaded onto it. So I figured no problem I will just restore to factory and do what I want to do rooting wise from there. I did a factory restore but it is still running MIUI and I don't know how to get it uninstalled and back to factory. It is running HBOOT 1.50 so I tried to flash a new rom via fastboot-->recovery even though I know that wont leave the rom completely working right but I was just trying to get rid of this MIUI rom. It said it flashed correctly but nothing changed on reboot it is still running MIUI. He gave it to me with the HBOOT unlocked already. Is there anyone that can help me getting a different rom, preferrably one as close to sense as possible running on this thing? I never ran into problems like this with my EVO 4g. Thanks to all!
vtotheinay said:
I bought an evo 3d from a guy today off craiglist and he gave it to me with MIUI loaded onto it. So I figured no problem I will just restore to factory and do what I want to do rooting wise from there. I did a factory restore but it is still running MIUI and I don't know how to get it uninstalled and back to factory. It is running HBOOT 1.50 so I tried to flash a new rom via fastboot-->recovery even though I know that wont leave the rom completely working right but I was just trying to get rid of this MIUI rom. It said it flashed correctly but nothing changed on reboot it is still running MIUI. He gave it to me with the HBOOT unlocked already. Is there anyone that can help me getting a different rom, preferrably one as close to sense as possible running on this thing? I never ran into problems like this with my EVO 4g. Thanks to all!
Click to expand...
Click to collapse
If already unlocked, using fastboot to get into recovery and flashing from there should have worked.
I would fastboot oem lock the device. Then running an ruu to get to stock. Wipe the entire sd card. Then follow htc evo hacks guide to root/unlock. Hboot 1.5.
That will unlock it again and give you your recovery. (I would probably use twrp instead of cwm if I were you).
Once done with that go ahead and flash su and make your nand backup. Should be good to go after that.
Sent from my PG86100 using XDA App
vtotheinay said:
I bought an evo 3d from a guy today off craiglist and he gave it to me with MIUI loaded onto it. So I figured no problem I will just restore to factory and do what I want to do rooting wise from there. I did a factory restore but it is still running MIUI and I don't know how to get it uninstalled and back to factory. It is running HBOOT 1.50 so I tried to flash a new rom via fastboot-->recovery even though I know that wont leave the rom completely working right but I was just trying to get rid of this MIUI rom. It said it flashed correctly but nothing changed on reboot it is still running MIUI. He gave it to me with the HBOOT unlocked already. Is there anyone that can help me getting a different rom, preferrably one as close to sense as possible running on this thing? I never ran into problems like this with my EVO 4g. Thanks to all!
Click to expand...
Click to collapse
If you relock the device, run the RUU first, then fastboot oem lock. You should try the superwipe tool located in the development thread under InfectedROM Eternity, Then try flashing a ROM. There are a few ROMs that are pretty stock, including a basic sense ROM with very few alterations. Head over to development and check them out.
thos25 said:
If already unlocked, using fastboot to get into recovery and flashing from there should have worked.
I would fastboot oem lock the device. Then running an ruu to get to stock. Wipe the entire sd card. Then follow htc evo hacks guide to root/unlock. Hboot 1.5.
That will unlock it again and give you your recovery. (I would probably use twrp instead of cwm if I were you).
Once done with that go ahead and flash su and make your nand backup. Should be good to go after that.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I tried going to fastboot then recovery when I flashed the other rom but like I said it did nothing,. Its actually running TWRP recovery already, but I will try to relock and start over. Thanks guys.
vtotheinay said:
I tried going to fastboot then recovery when I flashed the other rom but like I said it did nothing,. Its actually running TWRP recovery already, but I will try to relock and start over. Thanks guys.
Click to expand...
Click to collapse
Did you do a full wipe?
Twolazyg said:
Did you do a full wipe?
Click to expand...
Click to collapse
yeah I did a factory reset by going through menu-->settings-->about phone-->factory reset and tried factory resetting through recovery mode but as soon as it boots it looks like it has been reset. Unfortunately after I do the touch android character to continue options (sign into google, etc) it just goes straight into miui rather than how a factory evo 3d should look which is running gingerbread. Its so frustrating.
vtotheinay said:
yeah I did a factory reset by going through menu-->settings-->about phone-->factory reset and tried factory resetting through recovery mode but as soon as it boots it looks like it has been reset. Unfortunately after I do the touch android character to continue options (sign into google, etc) it just goes straight into miui rather than how a factory evo 3d should look which is running gingerbread. Its so frustrating.
Click to expand...
Click to collapse
Doing a factory reset is not the same as wiping.
You need to do a full wipe from recovery. Boot into the bootloader by hooking your phone up to the pc, navigate to your adb and fastboot folder and type:
Code:
adb reboot bootloader
Then type:
Code:
fastboot boot recovery.img
Once in recovery flash the superwipe.zip I mentioned before, then flash a ROM.
Check out this thread for information on how to get fastboot and adb, where to put them, and everything else you need to know about flashing with 1.5.
Then, before you do anything with your phone, look here for the superwipe.zip
Twolazyg said:
Doing a factory reset is not the same as wiping.
You need to do a full wipe from recovery. Boot into the bootloader by hooking your phone up to the pc, navigate to your adb and fastboot folder and type:
Code:
adb reboot bootloader
Then type:
Code:
fastboot boot recovery.img
Once in recovery flash the superwipe.zip I mentioned before, then flash a ROM.
Check out this thread for information on how to get fastboot and adb, where to put them, and everything else you need to know about flashing with 1.5.
Then, before you do anything with your phone, look here for the superwipe.zip
Click to expand...
Click to collapse
OH ok I had no idea. Thanks for that. When I click your link and try to download the superwipe zip from the page, the download link just takes me back to the thread link. Do you have a link to DL the superwipe?
vtotheinay said:
OH ok I had no idea. Thanks for that. When I click your link and try to download the superwipe zip from the page, the download link just takes me back to the thread link. Do you have a link to DL the superwipe?
Click to expand...
Click to collapse
Here you go.
Twolazyg said:
Here you go.
Click to expand...
Click to collapse
thanks. im still having a problem cause the phone is running TWRP recovery and the bootloader is unlocked but he wiped the SD card so all the files that should be on it after the unlock and flash of the recovery are gone. Im having a huge problem trying to get this MIUI off the phone. I just want to get it back to running a stock rom so I can activate it on my line and I am not too good with this whole unrooting stuff. Is there a simple way to do it? I tried going through fastboot--recovery then flashing the superwipe but it just ended up causing the phone to be stuck on the white screen on reboot with the green HTC.
vtotheinay said:
thanks. im still having a problem cause the phone is running TWRP recovery and the bootloader is unlocked but he wiped the SD card so all the files that should be on it after the unlock and flash of the recovery are gone. Im having a huge problem trying to get this MIUI off the phone. I just want to get it back to running a stock rom so I can activate it on my line and I am not too good with this whole unrooting stuff. Is there a simple way to do it? I tried going through fastboot--recovery then flashing the superwipe but it just ended up causing the phone to be stuck on the white screen on reboot with the green HTC.
Click to expand...
Click to collapse
After you wipe the hone you need to flash a ROM. When you wipe the phone it is completely blank.
Are you just doing a factory reset and rebooting? If so, that won't get you back to an HTC ROM. You need to wipe and then flash a new ROM. That will get you off of miui.
So you flashed the super wipe and then didn't flash a ROM? You have no OS loaded on your phone. Download a ROM, put it on your sd card, and flash it. Make sure it's a sense ROM since you'll need to be on a sense ROM to activate it. No need to unroot.
Sent from my HTC EVO 3D using Tapatalk
k2buckley said:
Are you just doing a factory reset and rebooting? If so, that won't get you back to an HTC ROM. You need to wipe and then flash a new ROM. That will get you off of miui.
So you flashed the super wipe and then didn't flash a ROM? You have no OS loaded on your phone. Download a ROM, put it on your sd card, and flash it. Make sure it's a sense ROM since you'll need to be on a sense ROM to activate it. No need to unroot.
Sent from my HTC EVO 3D using Tapatalk
Click to expand...
Click to collapse
No I used superwipe and then flashed clean rom 2.9.5 but it got stuck on the white screen on the reboot.
Do I have to use adb to run fastboot and then go into recovery or can I turn the phone off, boot into fastboot by holding power, vol down and going into recovery?
vtotheinay said:
No I used superwipe and then flashed clean rom 2.9.5 but it got stuck on the white screen on the reboot.
Do I have to use adb to run fastboot and then go into recovery or can I turn the phone off, boot into fastboot by holding power, vol down and going into recovery?
Click to expand...
Click to collapse
Since you're on hboot 1.5, you either need to flash using joeykrim's flash image gui app, or you need to put your phone in Gaynor, plug into the computer, and from the command prompt on your computer boot your recovery image. It's something like fastboot boot recovery.img. You will need to search for the exact command. Once you boot into recovery using that method you will be fine, just use recovery like normal. If you don't use one of those two methods you won't be able to flash the boot.img, so the phone won't boot. Good luck.
Sent from my HTC EVO 3D using Tapatalk
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.
So... I flashed scrosler's Stock Rooted RUU 3.14, and once that was cleanly on and working I got into amonra and cleared data, flashed Venasaur 3.1, and then in Hboot ran the 3.14 kernel again.
How did I go wrong and what's the simple fix that will get me with the pokemon? ~thanks <3
(I'm getting bootlooped that is)
You flashed an incompatible kernel. Are you s-on or s-off? If s-off just flash the Rom again in amon ra and reboot phone. No need to install a kernel it will do it for you. If s-on you need the kernel for venasaur Rom which may need to be flashed in fastboot unless someone has made it into a flammable zip. If s-on might as well take the plunge and s-off. It's a very easy process.
sent from my Clean Rezound
I am S-on, as soon as I find something condutable and more reliable than a paperclip i'll probably do S-off haha
I don't think anyway has, I just time getting the image boot file off of the rom and running it in H-boot, I still get a bootloop (I'm genuinely surprised that it didn't work), that's a pretty sticky situation, i'm stuck without a phone until that's solved =(
I repeal that statement, taking the boot.img out and flashing it in hboot worked, wonderful! thanks =)
Question for you?..
Now that that you have your Venusaur 3.1 running..are you having any issues with Wifi?
I did the re-lock, android police ruu, unlock, install recovery, clean wipe x10, install venusaur 3.1, and then installed sense4 boot image for the venusaur rom. However I keep getting Wi-fi Errors, I'm guessing my wifi modules are wrong but I'm just trying to figure out where I may have messed up. I tried flashing the wifi modules provided by http://forum.xda-developers.com/showthread.php?t=1642217 but no go...any ideas?
well i'm fairly curious how you were able to get the sense4 boot image, it gave me a mainver error, I took the boot image out of the rom and ran that.
Which got me in, and wifi isn't giving me a problem surprisingly, but I'm now curious to how your supposed to go 3g with the new setting setup.
My Sd card also can't mount I'm not sure if that's related to 3.14 and pokemon rom or just my terrible flashing
Watercycle, are you still having problems? If you flashed Scott's Rom that is not an ruu. I believe you are still o n the old firmware. You will need to go to nilsp business Rom in the development section and download the old firmware patch (i think it's in the 4th post) then flash in amon ra. You should be set after that.
sent from my Clean Rezound
actually I flashed scott's 3.14 deodex and old firmware patch + boot img before flashing the pokemon and pokemon boot img
I'm currently only struggling with the issue of sd card mount now
Watercycle said:
actually I flashed scott's 3.14 deodex and old firmware patch + boot img before flashing the pokemon and pokemon boot img
I'm currently only struggling with the issue of sd card mount now
Click to expand...
Click to collapse
The patch may still be on your sd card from Scott then and if not go to the thread I suggested. Just boot to recovery and flash the patch again. You will need that patch for any ics Rom you run because you are still on gb firmware. Don't panic your almost there.
sent from my Clean Rezound
how can you tell if your on old gb firmware? =( since it still boots up and works
darnit I thought i was on ics after that full ruu =o
so after having flashed the pokemon in Hboot i flash the old firmware again? (i'm scared it will bootloop me because i finally got it working haha)
ZombieCodeMonkey said:
Question for you?..
Now that that you have your Venusaur 3.1 running..are you having any issues with Wifi?
I did the re-lock, android police ruu, unlock, install recovery, clean wipe x10, install venusaur 3.1, and then installed sense4 boot image for the venusaur rom. However I keep getting Wi-fi Errors, I'm guessing my wifi modules are wrong but I'm just trying to figure out where I may have messed up. I tried flashing the wifi modules provided by http://forum.xda-developers.com/showthread.php?t=1642217 but no go...any ideas?
Click to expand...
Click to collapse
I briefly searched the venasaur thread (which you can do to) and found most people having WiFi issues either had the wrong kernel or just reset their router and bam, WiFi works. I can't help you anymore then that so you may want to ask in that thread.
Edit: did you unzip the Rom and get the boot.IMG there or did you download seperate? If you didn't unzip and take it out of the Rom then try that. You should be good.
sent from my Clean Rezound
What ruu did you use?
sent from my Clean Rezound
Give me like 20 minutes to get back to you...heading home....motorcycle can't multitask at night more obvious to others haha
Sent from my ADR6425LVW using Tapatalk 2
snow, since I sucsessfully was on
This
will flashing the old gingerbread fix my sd mounting or break everything?
sorry I have to be more direct, gotta get some sleep now =)
Watercycle said:
snow, since I sucsessfully was on
This
will flashing the old gingerbread fix my sd mounting or break everything?
sorry I have to be more direct, gotta get some sleep now =)
Click to expand...
Click to collapse
I think so
Watercycle said:
snow, since I sucsessfully was on
This
will flashing the old gingerbread fix my sd mounting or break everything?
sorry I have to be more direct, gotta get some sleep now =)
Click to expand...
Click to collapse
It will fix your sd card. You never ran the ruu if all you flashed was Scott's rooted, deodexd Rom. If you get with me tomorrow I can walk you through the ruu but I think at that point you might as well s-off. Time to find that wire
sent from my Clean Rezound
If you could see your sd card on Scott's Rom it was because of the patch. Make sure you report back. I need some sleep.
sent from my Clean Rezound
Okay...
I re-locked my bootloader using the usual, fastboot oem lock.
then I download the full leaked RUU from Android Police, androidpolice.com/2012/05/07/exclusive-download-htc-rezound-ice-cream-sandwich-build-3-14-605-5-brings-a-handful-of-fixes-and-newer-radios/"
Booted to Hboot with that file on the SD card in the proper name, completely flashed the phone with the Leaked RUU
Once OS loaded, rebooted back to fastboot and used hTcdev.com to unlocked my bootloader again. (I do not have S-Off yet).
Then I downloaded and flashed through fastboot commands the TWRP 2.1.1. Touchscreen recovery.
Once this was done, I downloaded and installed Venusaur 3.1.0 through recovery after performing scot's superwipe x10,
Then fastboot flashed the boot.img for the sense 4.0 roms.
Wi-Fi does not turn on at all...It will state Turning on...but not to long after will give error.
So after all of that I tried grabbing the wifi module.zip from one of the stock rom de-odexed rooted 3.14.605.5 roms, and tried flashing that through recovery and manually adding the file through root explorer..nothing.
Hope that helps clarify.
Also i would through an inquiry to there thread but I don't have enought posts yet to post in development.
ZombieCodeMonkey said:
Okay...
I re-locked my bootloader using the usual, fastboot oem lock.
then I download the full leaked RUU from Android Police, androidpolice.com/2012/05/07/exclusive-download-htc-rezound-ice-cream-sandwich-build-3-14-605-5-brings-a-handful-of-fixes-and-newer-radios/"
Booted to Hboot with that file on the SD card in the proper name, completely flashed the phone with the Leaked RUU
Once OS loaded, rebooted back to fastboot and used hTcdev.com to unlocked my bootloader again. (I do not have S-Off yet).
Then I downloaded and flashed through fastboot commands the TWRP 2.1.1. Touchscreen recovery.
Once this was done, I downloaded and installed Venusaur 3.1.0 through recovery after performing scot's superwipe x10,
Then fastboot flashed the boot.img for the sense 4.0 roms.
Wi-Fi does not turn on at all...It will state Turning on...but not to long after will give error.
So after all of that I tried grabbing the wifi module.zip from one of the stock rom de-odexed rooted 3.14.605.5 roms, and tried flashing that through recovery and manually adding the file through root explorer..nothing.
Hope that helps clarify.
Also i would through an inquiry to there thread but I don't have enought posts yet to post in development.
Click to expand...
Click to collapse
Why are you not s-off? Makes life much easier. What I have concluded is that you need to start over. You have the wrong kernel. Wipe everything then flash the Rom in recovery. You will have had to unzip the Rom on your pc then take the boot.IMG out and flash this in fastboot to the phone. I don't think there is a ph.zip file for this. There are very good directions if you search that thread.
sent from my Clean Rezound
Sorry guys but it's bed time. If you both follow those directions you should be fine. If not get with me in the morning.
sent from my Clean Rezound
I had followed this video ht tp://w ww.youtub e.com /watch?v=hQtUxEL8pd8 and did everything correctly. When I go to boot my phone up it shows the blue android boot animation then the green HTC animation then restarts.
Hboot 1.57
Somehow my recovery got deleted.
Clockworkmod recovery is installed.
I just don't know what to do
Is there a way I can just undo everything and go back to the stock rom?
Edit: Tried ViperROM and it's doing the exact same thing.
Make sure you are wiping everything except sdcard and then flash the rom. Maybe even try changing recoveries to 4ext.
Sent from my PG86100 using Tapatalk 2
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Jsparta26 said:
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Click to expand...
Click to collapse
I'm S-on, will it matter? And also I do mean 1.57. And one more thing. Does it matter if I boot up into a recovery using the command prompt? Also I'm not sure what kernel it is. I guess the one that's in the zip folder? Also sorry for slow responses I've been working days. Any chance you'll be on tomorrow around 7pm central?
Update: I reformatted everything and tried reinstalling Viperrom through CWM but no dice still boots up and resets. Got 4ext installed. Working from there.
Update: 4EXT is the best recovery I've ever seen and I'm never using CWM again.
Update: I installed VIperROM through 4ext and it's still restarting itself.
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Jsparta26 said:
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Click to expand...
Click to collapse
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I? Also i youtubed bootloop to see if it is really what's wrong and I came up with this video. ht tp ://www .y outube.co m/watch?v=OKXTD1-fqbc and my phones doing more than that. It's booting up all the way then once the screen and dock begins to load it restarts.
IAnb3rlin said:
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I?
Click to expand...
Click to collapse
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Jsparta26 said:
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Click to expand...
Click to collapse
How do I flash a kernel? I'm not really sure what one is, I just know it's really important.
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Jsparta26 said:
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Click to expand...
Click to collapse
I formatted everything using 4ext and installed a rom i also flashed the boot img just incase and it still restarted.
Here's the steps I took.
1. Format everything.
2. Download the.zip file and copy to SD card.
3. Load the recovery and enable smartflash.
4. Installed the rom.
5. Flashed the boot.img
6. Also tried without flashing the boot img.
And just to clarify. I'm installing ViperROM. And I only need the .zip file, correct?
I ended up using RUU to fix it and go back to the stock rom/ect, Then locked the bootloader unlocked it and flashed superuser and rooted it then got s-off using the wire trick. But after I rebooted it keeps taking me back to the jbear bootup logo and when I try to flash a recovery it doesn't load I just get the htc logo then jbear logo then it restarts. I followed this guide.htt p://w ww.yo utube.co m/ watch?v =tRj47iFQvbE I found here on the xda forums.
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Jsparta26 said:
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Click to expand...
Click to collapse
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
IAnb3rlin said:
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
Click to expand...
Click to collapse
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Jsparta26 said:
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Edit: just realized your using virgin mobile correct? I believe the reason your phone kept bootlooping with viper ROM was because of hboot. Try flashing a different hboot with the same method as the ruu and recovery.
Click to expand...
Click to collapse
I downloaded root checker and apparently I'm not root anymore. Yes I'm VM. I'm trying to rename the recovery and update it using the SD card now.
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
IAnb3rlin said:
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
Click to expand...
Click to collapse
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Jsparta26 said:
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Click to expand...
Click to collapse
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
IAnb3rlin said:
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
Click to expand...
Click to collapse
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Jsparta26 said:
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Click to expand...
Click to collapse
I just ended up unlocking the boot loader again and installing the recovery that way. Then saw this.. oh well lol. I really do appreciate the help. . I'm going to try to install viperrom again, and double backup this time! I'll let you know how it goes.