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
So after unlocking the boot loader today and loading up the stock rooted OTA rom my phone started randomly boot looping. It was sitting on my desk then randomly rebooted and now its been doing the same thing despite my best tries to fix it.
I had Amon Ra recovery installed initially, then flashed CWM via Rom manager. At this point I can't boot into recovery (or factory reset). It all happens very quickly, but it looks like the recovery menu loads up then the phone reboots. I am able to get into fastboot and reflash any of the recovery img's. I've tried the Amon Ra newest, the CWM normal and touch recovery and none of them will let me in. I've tried to get into recover with the 4G sim out and with the SD card out.
The phone does boot into an OS but after about 10 seconds it reboots. I did some digging and thought it might be the older bootloop issue with the network type. It does it with the sim out and in airplane mode so I'm not all that confident that its that issue.
At this point I am looking at tried to re-stock via Hboot RUU's. I have the P98IMG-1.02.605.6.zip on an SD card and that does flash but at the end of the verification it tells me "the main version is older." So I'm either looking for another package that will let me re-stock and give it a try again... or open to any other suggestions?
Hoping the phone isn't totally hosed, though based on what I can still get into I think there may be hope yet.
Anyone?
thanks in advance!
Have you tried CleanFlash? Also you are getting the mainver because you updated with the OTA. Google ruu_vigor. You are looking for the one that starts with 2.01.
Sent from my VTAB1008 using xda premium
This may help...
Get the 2.____.11 RUU from the 'Vigor Shipped' post in development. Follow the directions in the word file in post 2 from here:
http://forum.xda-developers.com/showthread.php?t=1487981
And then flash that RUU in HBOOT.
I had 99 problems with the RUU exe and spent the last week trying to get it to take. That tip to extract the PH file finally got me there. It fixed all kinds of issues for me and got me to stock.
Don't forget to relock.
(I think if you ran the ICS leak RUU you may still have issues, but you could follow those steps with that RUU as well probably and it would hopefully get you cleaned up)
Thanks for the help so far.
I got the newer RUU and got it flashed via hboot after i relocked. *edit* after the second time flashing it it seems to be working.
You guys rock.
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.
I have a new HTC Evo LTE and HBOOT 1.15.000 Radio 1.05.11.0606and do not have S-OFF.
I installed Fresh 5.2.1 and had problems, when back and did a wipe including system and installed 5.2.1 again and it didn't work. After doing that I went back, wiped system again, and then restored the backup I previously made. Now the backup sometimes loads, sometimes doesn't, but even when it does I have no radio. I am going to try to install a stock rom through recovery or fresh 5.1.1 and HOPE I get radio back.
Any other suggestions of what I could do?
jeggen said:
I have a new HTC Evo LTE and HBOOT 1.15.000 Radio 1.05.11.0606and do not have S-OFF.
I installed Fresh 5.2.1 and had problems, when back and did a wipe including system and installed 5.2.1 again and it didn't work. After doing that I went back, wiped system again, and then restored the backup I previously made. Now the backup sometimes loads, sometimes doesn't, but even when it does I have no radio. I am going to try to install a stock rom through recovery or fresh 5.1.1 and HOPE I get radio back.
Any other suggestions of what I could do?
Click to expand...
Click to collapse
So now I'm just in a boot loop. I relocked, installed stock recovery and ran RUU. When I did that I booted just long enough that I could almost slide the ring to unlock before I rebooted. Then the device just constantly reboots.
I unlocked again, installed TWRP 2.2.2.0 in case there was a bug causing flashing issues. Recovery boots just fine now. I flashed Stock Rooted DeOdexed 1.22.651.3 from here since that was the version I had before this whole fiasco. I'm going to try to restore backup again but don't know how to get out of this horrible mess. Worse part about it is that it's my wife's phone! Help please!
You might need to run a different RUU. I'm not too experienced with that kind of issue though.
"We're coming from a pure power source"
metalfan78 said:
You might need to run a different RUU. I'm not too experienced with that kind of issue though.
"We're coming from a pure power source"
Click to expand...
Click to collapse
I reflashed stock recovery, relocked bootloader (fastboot oem lock), ran RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.22.651.3_Radio_1. 05.11.0606_NV_SPCS_2.45_003_release_268323_signed. exe), and still had the boot loop problem. RUU said it completed but the bootloader still said "relocked". Isn't RUU supposed to totally wipe and restore the entire device?
I recall on my old EVO there was a zip you could place in the SDcard that the bootloader automatically looked for and would use to reflash to factory everything. Is there a way to do this with the EVO 4g LTE?
Is it possible that radios/firmware somehow got borked even though I am on S-ON? Is there a way to reflash them from bootloader?
Just thinking through ideas I'd try next and something that could possibly help recover or at least put me in a position to go back to Sprint for help.
Could have been a bad download. I think there is info on re locking in the development sticky section. It might give you some more information on what to do next.
"We're coming from a pure power source"
Just an update. Flashed again a stock ROM and installed the boot.img from stock using fastboot to be sure it was in place. (fastboot flash boot boot.img). That didn't work, still had boot loop where the phone loads enough to show the background and then restarts.
Used the PJ75IMG.zip file and attempted to install automatically in bootloader (from here) <-- Didn't install says "Main Version is older! Update Fail!
I then installed stock recovery and locked bootloader. Bootloader now shows "*** TAMPERED*** and *** RELOCKED***.
Ran RUU <-- Have a hard time doing anything since it doesn't boot up long enough to connect. Eventually RUU will fail with a connection error. I haven't been able to run RUU from HBOOT either and without the device stable long enough I'm not sure how to get RUU to run on the phone.
Still only boot far enough to see the background screen (wallpaper) and then reboot.
I'll gladly give $20 to anyone who offers a workable solution, paid either to you, or dev/charity of your choice if you don't want it.
This all started when I installed Fresh 5.2.1. Not sure if it was the fresh install or using TWRP to wipe data/cache and I also wiped system. Was that a mistake?
I just don't understand why I can't flash back even to stock. Since I'm relocked and never had S-OFF I don't understand how I was able to do something that can't be undone by flashing. I've flashed phones dozens of times so am comfortable with the process and just can't understand what went wrong and how to recover.
Is there an updated version of the PJ75IMG.zip file I could use?
Would it work to flash CM10 & the boot.img using fastboot?
jeggen said:
Just an update. Flashed again a stock ROM and installed the boot.img from stock using fastboot to be sure it was in place. (fastboot flash boot boot.img). That didn't work, still had boot loop where the phone loads enough to show the background and then restarts.
Used the PJ75IMG.zip file and attempted to install automatically in bootloader (from here) <-- Didn't install says "Main Version is older! Update Fail!
I then installed stock recovery and locked bootloader. Bootloader now shows "*** TAMPERED*** and *** RELOCKED***.
Ran RUU <-- Have a hard time doing anything since it doesn't boot up long enough to connect. Eventually RUU will fail with a connection error. I haven't been able to run RUU from HBOOT either and without the device stable long enough I'm not sure how to get RUU to run on the phone.
Still only boot far enough to see the background screen (wallpaper) and then reboot.
I'll gladly give $20 to anyone who offers a workable solution, paid either to you, or dev/charity of your choice if you don't want it.
This all started when I installed Fresh 5.2.1. Not sure if it was the fresh install or using TWRP to wipe data/cache and I also wiped system. Was that a mistake?
I just don't understand why I can't flash back even to stock. Since I'm relocked and never had S-OFF I don't understand how I was able to do something that can't be undone by flashing. I've flashed phones dozens of times so am comfortable with the process and just can't understand what went wrong and how to recover.
Is there an updated version of the PJ75IMG.zip file I could use?
Would it work to flash CM10 & the boot.img using fastboot?
Click to expand...
Click to collapse
I sent you a PM
Sent from my EVO using xda premium
I'm back up and running. With a kind and helpful tech we ran RUU again (twice) and still had boot loop. I was going to give up on it but we went into the default recover and cleared data and factory reset and it seems to be back to normal again and working fine.
Sent from my MB855 using Tapatalk 2
jeggen said:
I'm back up and running. With a kind and helpful tech we ran RUU again (twice) and still had boot loop. I was going to give up on it but we went into the default recover and cleared data and factory reset and it seems to be back to normal again and working fine.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
Awesome glad you got it fixed.
Sent from my EVO using xda premium