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
Related
I had my wife's EVO 3D working fine on VipeRom2.1 I think and when i tried to update it to 2.5 it went into a reboot loop. I cleared everything by formatting the system and clearing the cache and data and nothing. I tried a different rom, MeanRom and same thing. Right before it seems like it is going to get me to the unlock screen, reboot. I can get into the bootloader and the recovery just fine but no matter what i install, reboot, reboot, reboot.
Evo 3D
twrp 1.03
Recovery 2e
HBOOT 1.5
Any assistance would be greatly appreciated.
jschauf said:
I had my wife's EVO 3D working fine on VipeRom2.1 I think and when i tried to update it to 2.5 it went into a reboot loop. I cleared everything by formatting the system and clearing the cache and data and nothing. I tried a different rom, MeanRom and same thing. Right before it seems like it is going to get me to the unlock screen, reboot. I can get into the bootloader and the recovery just fine but no matter what i install, reboot, reboot, reboot.
Evo 3D
twrp 1.03
Recovery 2e
HBOOT 1.5
Any assistance would be greatly appreciated.
Click to expand...
Click to collapse
What software is your phone on ? The 2.08 or 2.17?
jschauf said:
I had my wife's EVO 3D working fine on VipeRom2.1 I think and when i tried to update it to 2.5 it went into a reboot loop. I cleared everything by formatting the system and clearing the cache and data and nothing. I tried a different rom, MeanRom and same thing. Right before it seems like it is going to get me to the unlock screen, reboot. I can get into the bootloader and the recovery just fine but no matter what i install, reboot, reboot, reboot.
Evo 3D
twrp 1.03
Recovery 2e
HBOOT 1.5
Any assistance would be greatly appreciated.
Click to expand...
Click to collapse
Did you change/update your radios at all?
I am not sure of the software version. I tried going back to unrooted stock with RUU_Shooter_U_HTC_ARA_1.24.415.2_Radio_10.55.9020.00_10.13.9020.29_M_release_208706_signed and it gave me a version error.
I am running radio 0.97.10.0808 according to the relocked screen that I am getting while trying to restore to unlocked sprint stock.
And now I see the difference in radio and the version in the restore file.
Thanks for the assistance, my Epic Touch 4g has been so simple to tinker with, this thing is a pain in the rear.
The RUU you installed was for the GSM version of the phone, re-run the CDMA version. The GSM version is called Shooter_U whereas the sprint version is just called Shooter.
I'm guessing this would be a good place to start?
http://www.scottsroms.com/downloads.php?do=cat&id=4
I will try this one when I get home today. Hopefully I can get it back stock and then start over and get a functional custom ROM working.
The wife was not to happy I blew up her phone yesterday trying to update it, I am guessing she is not going to let me "fix" it again.
Yupp, install one of them, not sure which one will allow you to do the HTC unlock though.
I think I figured out what I did wrong in the first place. Someone please correct me if I am wrong. I forgot that 1.5 S-ON can't just install the ROM from the standard recovery method like I can with my Epic Touch 4G. I think I need follow the "How to Flash Any ROM or Kernel You Want" instructions from http://forum.xda-developers.com/showthread.php?t=1239821. I just booted to recovery and tried to install the ROM. Does this sound about right?
jschauf said:
I think I figured out what I did wrong in the first place. Someone please correct me if I am wrong. I forgot that 1.5 S-ON can't just install the ROM from the standard recovery method like I can with my Epic Touch 4G. I think I need follow the "How to Flash Any ROM or Kernel You Want" instructions from http://forum.xda-developers.com/showthread.php?t=1239821. I just booted to recovery and tried to install the ROM. Does this sound about right?
Click to expand...
Click to collapse
I didn't look at the link you posted. But with hboot 1.5 you can not write to the boot partition from recovery. In order to do this you need to extract the boot img from the ROM your gonna flash and fastboot flash boot boot.img then fastboot boot recovery.img will take you to recovery and flash ROM from there
Sent from my PG86100 using XDA App
mteezey said:
I didn't look at the link you posted. But with hboot 1.5 you can not write to the boot partition from recovery. In order to do this you need to extract the boot img from the ROM your gonna flash and fastboot flash boot boot.img then fastboot boot recovery.img will take you to recovery and flash ROM from there
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
You actually dont need to do both. If you just do a fastboot boot recovery.img it will give you complete access, including flashing the kernal. So after you type that command, it will load a the custom recovery and when you flash the rom, it will flash the kernel included with the rom as well. FYI you need to do a fastboot boot recovery.img each time you want to flash a kernel. If you arent changing kernals then you can just go into recovery as you normally would and flash a rom. If you want to flash a kernal without hooking up to a computer, then read into Flash Image GUI.
JayDaKissEP said:
You actually dont need to do both. If you just do a fastboot boot recovery.img it will give you complete access, including flashing the kernal. So after you type that command, it will load a the custom recovery and when you flash the rom, it will flash the kernel included with the rom as well. FYI you need to do a fastboot boot recovery.img each time you want to flash a kernel. If you arent changing kernals then you can just go into recovery as you normally would and flash a rom. If you want to flash a kernal without hooking up to a computer, then read into Flash Image GUI.
Click to expand...
Click to collapse
This is what I thought, The first one I tried was the newest version of ViperRom. I first tried to just flash over top of the existing rom with the hope I would not have to reset everything and make her start over with how she had it setup, I guess the newest version had a newer kernel. Hopefully I am able to get it back to a functional state this afternoon.
jschauf said:
This is what I thought, The first one I tried was the newest version of ViperRom. I first tried to just flash over top of the existing rom with the hope I would not have to reset everything and make her start over with how she had it setup, I guess the newest version had a newer kernel. Hopefully I am able to get it back to a functional state this afternoon.
Click to expand...
Click to collapse
I believe that does have the anthrax kernel havent downloadedthe new version. However i know some people have been having problems with roms that are based off the new OTA if their phones still have the old firmware. Definatly flash teh kernel/boot via fastboot recovery that should take care of the problem.
Correction not anthrax.
I got everything back working yesterday, I guess doing it correct the first time will save me some headache. I just need to remeber to start recovery from windows instead of from the bootloader screen. Thanks for the assistance.
Hello,
I have an unlocked EVO 3D with HBOOT 1.5 S-on.
I flashed the phone and replaced InfectedRom with Warm Two Point Three. After installing new rom and reseting, phone is now stuck on HTC startup screen.
Please help!!! I appreciate and welcome all feedback. Thank you
kongfooey said:
Hello,
I have an unlocked EVO 3D with HBOOT 1.5 S-on.
I flashed the phone and replaced InfectedRom with Warm Two Point Three. After installing new rom and reseting, phone is now stuck on HTC startup screen.
Please help!!! I appreciate and welcome all feedback. Thank you
Click to expand...
Click to collapse
Did you wipe all the way? Also what is your software 2.17 or 2.08 ? Did you fastboot boot recovery.img when you flashed?
kongfooey said:
Hello,
I have an unlocked EVO 3D with HBOOT 1.5 S-on.
I flashed the phone and replaced InfectedRom with Warm Two Point Three. After installing new rom and reseting, phone is now stuck on HTC startup screen.
Please help!!! I appreciate and welcome all feedback. Thank you
Click to expand...
Click to collapse
You need to flash boot.img/kernel using fastboot or Flash image GUI or else you will face issues if the ROM uses kernel other than your current one.
This is the limitation of HTC unlock method (S-ON)
mnomaanw said:
You need to flash boot.img/kernel using fastboot or Flash image GUI or else you will face issues if the ROM uses kernel other than your current one.
This is the limitation of HTC unlock method (S-ON)
Click to expand...
Click to collapse
Thank you!
I flashed the boot.img using fastboot as you suggested. Now the phone is stuck in an endless loop between powering off and the HTC startup logo.
It appears that I am getting closer to fixing the problem but I am still stuck. Can you help further please?
Thanks again!
mnomaanw said:
You need to flash boot.img/kernel using fastboot or Flash image GUI or else you will face issues if the ROM uses kernel other than your current one.
This is the limitation of HTC unlock method (S-ON)
Click to expand...
Click to collapse
Thanks for your reply.
I did wipe all the way. How do I tell whether I have 2.08 or 2.17. if the phone not able to start up?
I flashed boot.img using fastboot. I just realized that the bootloader when doing and Hboot tries to load the image indicates no image or wrong image.
I am either missing a step or did something wrong.
Please help!
did you make a backup of Infected before you flashed?
When you say you installed Warm did you install and actually get it fully booted and set up your home screens and all that and it only stuck on the first reboot after? or was it right after you flashed warm?
Really if you made a backup of infected or what you were running before you should be able to restore that via recovery then boot up normal. Then use FlashImageGUI to flash the kernel needed for Warm, then reboot into recovery mode and flash the other portion of the Rom from the custom recovery.
Unfortunately, I did not back up Infected or other previous roms. I didn't know that I should, I only backed up my apps using Titanium. I now know better.
Still stuck in loop mode. I have been searching the forums for some possible solutions but so far nothing has worked.
I am up the creek without a paddle...
kongfooey said:
I used Titanium Backup to back up apps etc. is that the same as backing up the rom (Infected)?
If I had the backup how do I recover using recovery? I have been reading other posts in the forum and have tried some of the suggestions. I wiped the data and cache.
I am up the creek without a paddle...
Click to expand...
Click to collapse
na TiBackup isn't the same as backing up the Rom itself.
Full backups are done from within the custom recovery...
the boot.img you pushed via fastboot earlier. where did you get it from?
Silly me... I realized that Titanium backup was not the correct backup after I posted.
I took the image from the Warm zip file. I initially thought the problem was fixed until I realized that the phone is in an endless loop...
Still looping
kongfooey said:
Silly me... I realized that Titanium backup was not the correct backup after I posted.
I took the image from the Warm zip file. I initially thought the problem was fixed until I realized that the phone is in an endless loop...
Still looping
Click to expand...
Click to collapse
well to be honest I would just go back and start form scratch at this point since pushing the kernel via fastboot somehow didn't take for you nor did clearing cache's after the fact.
after pushing the kernel via fastboot, have you tried doing that again, and then going into recovery and flashing the rom again? If that doesn't work you might as well just go back to stock and push stock kernel flash stock rooted OTA, boot up, and use FlashImageGUI to push the Warm kernel then go back to flashing the Warm rom in recovery...
really before pushing the stock kernel if you wanna test to see if your initial push of Warm kernel even took fully just fully wipe data and try flashing infected again in recovery. If it boots fine then you know your fastboot push didn't take before to begin with...
Edit:
before i even really get more into this. does Warm even use another kernel beside the stock one? If they dont then all of this could of resulted from a bad download of the rom itself being flashed...
Sgt. Slaughter, I salute you...
I played around with your suggestions. Got it working... I flashed a different boot.img and it solved the problem. I may have gotten a bad Warm rom...
Thanks again!!!
Note: if you took/installed the latest update (2.17.651.5) you won't be able to use roms based off earlier firmware/kernels (ie 2.08.651.2 or 651.3) b/c of kernel differences (I think I've read that somewhere).
I believe Warmtwopointthree and Infected are not using the latest base/kernel.
Edit: saw you posted right before me. So what kernel/boot.img did you use?
kongfooey said:
Sgt. Slaughter, I salute you...
I played around with your suggestions. Got it working... I flashed a different boot.img and it solved the problem. I may have gotten a bad Warm rom...
Thanks again!!!
Click to expand...
Click to collapse
Nice good to hear. Fact you had your phone even semi-booting makes solving anything wrong with it usually trial and error and ends up not being so bad to fix...
I used boot.img from OTXE Titan HD ODEXed New Beats!
I need to educate myself a bit more about the differences between kernel and .imgs etc...
Thanks for your response. I greatly appreciate!!
I'm having a very similar issue, I rooted my Evo using Revolutionary and installed CW Recovery and everything was fine so I tried installing ZR3D and part way through the install, my phone turned off and now it wont get past the HTC boot screen. I went into CW Recovery but nothing is working, no matter what option I choose [even Turn off phone or reboot] it gives me the CW logo but nothing happens.
I have HBOOT 1.49.1107 with S-Off
Try reflashing your recovery threw hboot.
#Root-Hack_Mod*Always\
StoneCold448 said:
I'm having a very similar issue, I rooted my Evo using Revolutionary and installed CW Recovery and everything was fine so I tried installing ZR3D and part way through the install, my phone turned off and now it wont get past the HTC boot screen. I went into CW Recovery but nothing is working, no matter what option I choose [even Turn off phone or reboot] it gives me the CW logo but nothing happens.
I have HBOOT 1.49.1107 with S-Off
Click to expand...
Click to collapse
Can you boot into Fast boot? If so, try connecting your phone to a computer and flashing a recovery through there. Then try to install the ROM.
Sent from my PG86100 using Tapatalk 2 Beta-6
coal686 said:
Can you boot into Fast boot? If so, try connecting your phone to a computer and flashing a recovery through there. Then try to install the ROM.
Click to expand...
Click to collapse
Thanks for your help
Ok... So a couple of days ago, I was having bootloop issues on Ineffabilis 1.3 using the Anthrax kernel. After doing a battery pull, I booted into the bootloader and then to recovery and found that my roommate, while playing with my phone, had flashed the ClockworkMod Recovery, I suppose through the Rom Manager app.
I figured it would be ok to do a full wipe and re-flash the rom since flashing the stock kernel didn't stop the bootlooping and I would just flash AmonRa back when I was done to do a backup.
Well, after doing a factory reset from CWM and getting errors thereafter trying to flash the superwipe and Ineffabilis, I rebooted the phone and skipped through the setup to get to the restart menu to get into the bootloader again to flash AmonRa. I was able to flash it, but now every time I try to get into the recovery whether from the restart menu, ADB, or through the fastboot menu, it automatically restarts the phone as soon as the recovery is loaded and goes back to the OS.
Has anyone experienced this and is there any way to fix it to get back into it?
Sounds like you have a ph image on your sd card. Just delete it and you should be fine
sent from ics land
I've long since removed all PH files from my phone, internal and external sdcard included, and even if there were that's never stopped my from booting directly into recovery from the restart menu or through ADB.
I've even gone as far as removing the external sdcard with the same result. It just boots into recovery and as soon as it loads for that split second, it automatically reboots to the HTC screen and back to Android.
I still have root and my phone isn't bricked. I just can't flash any roms or kernels in the future when we get our official ics update. WTB my EVO 3D's hboot 1.4 back...
Sent from my ADR6425LVW using XDA
ojdidit84 said:
I've long since removed all PH files from my phone, internal and external sdcard included, and even if there were that's never stopped my from booting directly into recovery from the restart menu or through ADB.
I've even gone as far as removing the external sdcard with the same result. It just boots into recovery and as soon as it loads for that split second, it automatically reboots to the HTC screen and back to Android.
I still have root and my phone isn't bricked. I just can't flash any roms or kernels in the future when we get our official ics update. WTB my EVO 3D's hboot 1.4 back...
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
what happens when you try to go to recovery...
i would just reflash a recoveyr in fastboot. cant hurt.
What it does is as soon as it boots to recovery, I see it load the recovery and then as soon as it loads, it's as if the phone automatically selects the reboot option and goes back through the normal boot no matter which method I use to boot into recovery.
I've done the fastboot method which flashed successfully, tried to re-flash clockwork using rom manager, scott's tool, adb & fastboot, also used scott's flash tool which was also successful and it just seems as if recovery mode is borked somehow and using these methods to go back to AmonRa produce the same result. I'm usually good at figuring these things out myself since I've been rooting and flashing since my first Sprint HTC Hero, EVO 4G, 3D, Epic 4G/Touch and I've never had anything like this happen before. Completely stumped .
Have done a search and haven't found anyone with the same issue so I have nothing prior to go off of. The phone works fine for now so I'm in no hurry since I still have root and thankfully Titanium Backup for my apps. Not sure what to try next at this point.
ojdidit84 said:
What it does is as soon as it boots to recovery, I see it load the recovery and then as soon as it loads, it's as if the phone automatically selects the reboot option and goes back through the normal boot no matter which method I use to boot into recovery.
I've done the fastboot method which flashed successfully, tried to re-flash clockwork, also used scott's flash tool which was also successful and it just seems as if recovery mode is borked somehow. I'm usually good at figuring these things out myself since I've been rooting and flashing since my first Sprint HTC Hero, EVO 4G, 3D, Epic 4G/Touch and I've never had anything like this happen before. Completely stumped .
Have done a search and haven't found anyone with the same issue so I have nothing prior to go off of. The phone works fine for now so I'm in no hurry since I still have root and thankfully Titanium Backup for my apps. Not sure what to try next at this point.
Click to expand...
Click to collapse
From hboot, choose factory reset and see if it boots you into recovery. I had a similar issue after running the new RUU, once I chose that it booted into custom recovery and i was able to reboot and then afterwards had no trouble accessing recovery.
mjh68 said:
From hboot, choose factory reset and see if it boots you into recovery. I had a similar issue after running the new RUU, once I chose that it booted into custom recovery and i was able to reboot and then afterwards had no trouble accessing recovery.
Click to expand...
Click to collapse
Ok. I'll give that a whirl in the morning and see if it solves the problem.
Bump... I'm stuck with this issue...
Hi,
Spent the last two days trying everything I could think of to get a custom recovery loaded on my rezound with no luck. Have searched everywhere and short of trying to hex edit some code nothing has worked.
I was on a custom ICS rom and applied the 4.03.605.2 RUU (hboot 2.27). Was S-ON with unlocked bootloader. I locked the bootloader, installed RUU successfully, unlocked the bootloader with my token. I tried flashing amon-ra, CWM, TWRP many versions of each by fastboot and hboot (PH98IMG). The custom recovery is successfully written in each case, but i can't successfully boot into the recovery partition either from fastboot or hboot menu option. I can write the recovery.img file from the RUU zip, and all is good. Ultimately, I am just trying to install a custom ROM/root my device.
I tried the above advice about performing a factory reset. No Dice. So for now, I am stuck in Verizon bloatware land, and very unhappy about it.
Suggestions welcome. Thanks everyone.
phaedrus43 said:
Hi,
Spent the last two days trying everything I could think of to get a custom recovery loaded on my rezound with no luck. Have searched everywhere and short of trying to hex edit some code nothing has worked.
I was on a custom ICS rom and applied the 4.03.605.2 RUU (hboot 2.27). Was S-ON with unlocked bootloader. I locked the bootloader, installed RUU successfully, unlocked the bootloader with my token. I tried flashing amon-ra, CWM, TWRP many versions of each by fastboot and hboot (PH98IMG). The custom recovery is successfully written in each case, but i can't successfully boot into the recovery partition either from fastboot or hboot menu option. I can write the recovery.img file from the RUU zip, and all is good. Ultimately, I am just trying to install a custom ROM/root my device.
I tried the above advice about performing a factory reset. No Dice. So for now, I am stuck in Verizon bloatware land, and very unhappy about it.
Suggestions welcome. Thanks everyone.
Click to expand...
Click to collapse
Hook up to PC. the phone can actually adb when turned off. or make sure ROM is booted with ADB turned on. It should connect to adb. Does it? Then your command would be "adb reboot recovery" after you have flashed a custom recovery. So what does it do when you try to enter recovery?
Thanks. Did try that, but not with phone off. I'll try both for good measure and let you know. Thank you fly...
Sent from my ADR6425LVW using xda app-developers app
Flyhalf205 said:
Hook up to PC. the phone can actually adb when turned off. or make sure ROM is booted with ADB turned on. It should connect to adb. Does it? Then your command would be "adb reboot recovery" after you have flashed a custom recovery. So what does it do when you try to enter recovery?
Click to expand...
Click to collapse
Hi Fly,
I was unable to get adb to see the phone when it was off with either a custom recovery or the stock recovery. When I rebooted to recovery from adb with a custom recovery installed, it attempts to boot to the recovery partition but fails and boots back to the OS (this is true when using adb, fastboot, and hboot to boot to recovery). When i reinstalled the stock recovery, it successfully boots to recovery using all methods.
i have tried other custom recovery versions, TWRP (preferred), AMON-RA, CWM Recovery...
annoyed.
Thanks Fly. Any other ideas?
phaedrus43 said:
Hi Fly,
I was unable to get adb to see the phone when it was off with either a custom recovery or the stock recovery. When I rebooted to recovery from adb with a custom recovery installed, it attempts to boot to the recovery partition but fails and boots back to the OS (this is true when using adb, fastboot, and hboot to boot to recovery). When i reinstalled the stock recovery, it successfully boots to recovery using all methods.
i have tried other custom recovery versions, TWRP (preferred), AMON-RA, CWM Recovery...
annoyed.
Thanks Fly. Any other ideas?
Click to expand...
Click to collapse
I'm out of ideas. Since your s-on you can't go down to the OTA RUU and try there. Maybe someone else can spread some light.
Well one more idea. Boot your phone into Fastboot. Plug into computer and download a custom recovery to your computer. The command to use is "fastboot boot recovery.img"
If that does work then download http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip and flash it inside of recovery. That will give you root inside your stock rom at least.
Flyhalf205 said:
I'm out of ideas. Since your s-on you can't go down to the OTA RUU and try there. Maybe someone else can spread some light.
Well one more idea. Boot your phone into Fastboot. Plug into computer and download a custom recovery to your computer. The command to use is "fastboot boot recovery.img"
If that does work then download http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip and flash it inside of recovery. That will give you root inside your stock rom at least.
Click to expand...
Click to collapse
Hi Fly,
Nothing doing. Can't flash the attached in stock recovery, can't boot into any recoveries with stock flashed or with custom recovery flashed. Seems there must be some new security built into the new RUU? I did note one thing. When I first flash the RUU the hboot banner says relocked (as i have to relock to install an RUU). However, as soon as I flash anything to the recovery partition it adds a new white on black banner that says tampered. Now, i have seen that before when I s-off'd my rezound previously (returned to verizon for audio problems). I never did s-off this particular phone. I don't recall my first phone flagging a new recovery or this phone flagging a new recovery on the old firmware (i could be wrong though as i don't spend a lot of time in hboot).
Still hoping to put a custom recovery on this. Any other way to load a custom rom? i really want to run Neo's AOKP, as I had that on here before I RUU'd. In fact, i got into this position because I was going to s-off the phone, but I had a custom rom. I started looking for RUU's to restore to stock because controlbear wouldn't work with custom rom. Instead of installing an early ICS again, i opted to install the latest RUU.
I searched the forums high and low and wasn't really able to find anyone with this problem. I wonder if there is something wrong with the RUU? I checked the MD5sum and it matched. When flashing recovery i checked the mainver too, so it isn't that... I'm stumped.
This phone wasn't real popular and is gettting old now (man, the lifecycle on phones suck, I had my N1 through many roms and AOSP releases! These new phones are gone in 6 months, a year tops). I doubt anyone is going to trouble themselves to crack a new HBOOT on this phone (this is 2.27).
Only other things i can think (and I haven't tried yet) is trying zergRushing it for temp root to at least remove/freeze the bloat like I did with this phone when I first got it. Or if I can just get a rom installed without a custom recovery I don't flash as often as I used to and figure an upgrade isn't long off. Or if i could downgrade the hboot or install jb hboot...
Would love it if someone had something new to try.
Thanks so much again Fly and happy holidays.
Success! (but how?)
Ok Fly,
I don't get it... not at all. I tried, just for the hell of it, a little more tonight and my phone was happy to flashboot boot TWRP 2.2.2.1 SPECIFICALLY. I was unable to get other versions working or other custom recoveries. I have no IDEA why. I can only think that the recovery partition is too small for some recovery.imgs? but 2.2.2.1 is actually bigger than 2.3.3.0 that you compiled for the rezound. Anyway, i have ROOT! now, my first step before I dork with anything is to S-Off this bad boy so i can move around a little more. I will probably still leave the locked bootloader after that, just to keep me from n00bing up. Haven't tried flashing the twrp recovery yet, don't want to goof up my S-off chances or not give you a chance to ask a question.
If you want some forensics to help others out, please let me know. I am gonna leave this phone alone for a day in case you have questions. There HAS to be some lesson in here. Totally random to me. (last thought) i was running 2.2.2.1 before I ran the RUU... wonder if that has something to do with it?
Thanks again Fly.
phaedrus43 said:
Ok Fly,
I don't get it... not at all. I tried, just for the hell of it, a little more tonight and my phone was happy to flashboot boot TWRP 2.2.2.1 SPECIFICALLY. I was unable to get other versions working or other custom recoveries. I have no IDEA why. I can only think that the recovery partition is too small for some recovery.imgs? but 2.2.2.1 is actually bigger than 2.3.3.0 that you compiled for the rezound. Anyway, i have ROOT! now, my first step before I dork with anything is to S-Off this bad boy so i can move around a little more. I will probably still leave the locked bootloader after that, just to keep me from n00bing up. Haven't tried flashing the twrp recovery yet, don't want to goof up my S-off chances or not give you a chance to ask a question.
If you want some forensics to help others out, please let me know. I am gonna leave this phone alone for a day in case you have questions. There HAS to be some lesson in here. Totally random to me. (last thought) i was running 2.2.2.1 before I ran the RUU... wonder if that has something to do with it?
Thanks again Fly.
Click to expand...
Click to collapse
Anytime :fingers-crossed:
Crazy how things work like this. But the recovery partition shouldn't be to small to flash a custom recovery. Good luck. Just sounds like one of those rare things that happens.
I am a complete noob. Sprint Evo 3d 1.5 s-on, I have been running Viper IC3D for a month now, loving it,should have stuck with that. I wanted to try one of the Jelly Bean Roms, specifically the Team D.I.R.T. one, but I didn't want to have to keep flashing the two roms back and forth. Found out about Boot Manager Pro on here, and found a thread about using it with hboot 1.5 s-on. followed the instructions, booted into D.I.R.T. rom. fiddled with it, decided to go back to my phone rom. Boot Manager kept unexpectedly closing on me, wouldn't stay open long enough to do anything. So I went into recovery and restored my nandroid of Viper. But D.I.R.T. loaded! Said screw it, and wiped and reflashed Viper. D.I.R.T. loaded! Couldn't get anything but that ROM to load no matter what I did. Uninstalled Boot Manager, nothing but D.I.R.T.So I hunted around here and found a thread that said if all else failed, to manually remove Bootloader from sd and go from there. Did that, and it soft bricked my phone. I can get into recovery, but no matter what I do when I reboot it hangs in HTC white boot screen. I cannot afford another phone and don't get an upgrade til next year. Please Say there is a solution to this! I cried all last night, couldn't sleep, and I'm crying again. Side note, i accidentally erased half the C; Drive on my laptop trying things I found on another android forum,and system restore didn't work. So I'm back here, and I'm scared to try anything else, but I have to do something. Help!!!!!!
Flash the kernel. All will be well.
Viper rom should include boot.img.
Extract it to sdk-tools folder.
Open terminal, cd to sdk-tools directory.
Hold volume plus down on phone. Hit power button on fastboot option.
Plug in phone to computer. It should say fastboot usb on phone screen now. If not, install htc drivers.
Go to terminal. Type "fastboot flash boot boot.img
Should see some stuff happen on computer screen, phone will reboot.
Do that then report back.
Sent from my PG86100 using Tapatalk 2
can I do this using my rootevo3dnew package? I had a bad experience trying to install android sdk
You don't install sdk-tools. It's just a bunch if exe's in a folder.
That other thing you said, never heard of it.
Sent from my PG86100 using Tapatalk 2
Marta9227 said:
can I do this using my rootevo3dnew package? I had a bad experience trying to install android sdk
Click to expand...
Click to collapse
Yes you can, as long as you have fastboot and adb in there you'll be good, just put the boot.img in the same folder
Sent from my EVO 3DMA with a little "Common Sense"
please read my post carefully again and again it will solve your problem, I had the same problem
http://forum.xda-developers.com/showthread.php?t=1853065
I'm doomed. I was able to flash CWM this way, although it didn't help me at all. But I tried to flash the boot img and it didn't work. Didn't seem to recognize the command.
I'm cdma s-on? So basically you relocked and flashed an RUU and then relocked?
try to relock and flash with RUU it will work
At first when you were unable to boot back to phone rom, you should have went into recovery and flash the update.zip located in the sdcard/bootmanager/phonerom.
Anyway try to flash back to viperrom again then boot your recovery via fast boot since you are not s-off. And flash the update.zip from the phone rom folder. If everything fails just relock your bootloader and use the ruu.exe and you should be fine.
Marta9227 said:
I'm doomed. I was able to flash CWM this way, although it didn't help me at all. But I tried to flash the boot img and it didn't work. Didn't seem to recognize the command.
Click to expand...
Click to collapse
The command is: fastboot flash boot c:\(navigate to the sdk map with boot.img)\boot.img
For instance. for me it's c:\Users\(my name)\boot.img
Because i have my sdk and boot.img in my User map.
I believe boot manager creates the files for the second rom on the sd card. maybe thats why the D.I.R.T rom is loading.. My advice, try a different sdcard and see if the viper rom starts (you still might have to flash the boot.img via adb because of s-on)
I have no idea where the files for second rom are created so maybe if someone else could help out here. Then it should be a simple matter of deleting the second rom from the sd card and then go ahead and flash your viper rom.
http://init2winitapps.com/stories/BMManual.html
^^ this tell you all you need to know about dual booting.
Thanks to everyone! Relocked and ran RUU safely back to stock now debating if I have the guts to unlock again lol
Sent from my PG86100 using xda app-developers app
Do it!
Do it! The RUU will save you anyways lol
Should I do the stock ics ota first? I know that will make me hboot 1.58. Can I still HTC dev unlock 1.58? And can I get a new code? Didn't save the old one
Sent from my PG86100 using xda app-developers app
Yes you will have to get new code from htcdev. Though i wouldn't recommend updating hboot cause its known to cause some issues with some roms
Hey everyone,
So I have successfully HTC Unlocked my Rezound bootloader, installed Amon Ra, and then installed and booted the CM9 unofficial. Problem was that CM9 wasn't quite as cooperative as I'd hoped - it is unofficial, after all, and so I decided to abandon that in favor of Nils' Business ROM. Here's where I ran into issues.
I have tried everything in every order I can find online and think of, including Nils' writeup. So, for the life of me, I cannot get the leaked ICS RUU to boot (4.03.605.2 as listed in his instructions on XDA). Install runs fine every time I do it from the relocked (I checked) stock HBOOT, all steps included. Every time it reboots (and I've tried forcing it back into hboot to do the install a second time) it just goes to the white HTC screen and starts boot looping. Tried it a million ways, no go. Also worth noting - the stock recovery doesn't install properly, either. Some'fin is hinky, here.
So I've tried just "assuming" it went fine anyhow and then proceeding with the install for Nils' ROM and same deal, no go, although with one difference. With Nils' ROM, it does display the boot splash screen "Nils Business ROM" or what have you about 1 out of every 4 "boots" in the loop cycle, and then reboots again.
I think I am going to perform S-OFF tomorrow if I have the time, and then try it again using the S-OFF instructions, but I would sincerely appreciate any help from you all. Honestly, I'm at near wit's end with this device, and I don't want to be, I enjoy this chase too much, but I *really* want the reward at the end of it, lol.
Any help is deeply appreciated.
- Katie
Re: [Q]
I'm guessing because of the corrupted recovery, you have a bad download of the RUU. Try re downloading and check the md5 hash for a match. The ruu should reboot itself after the first pass and end up in bootloader again for the second pass.... If not then after the first pass just hold down power + vol down to get back to bootloader.
Hope this helps
Sent from my ADR6425LVW using xda app-developers app
Make sure that you have a booting ROM before you s-off. You will cause yourself all kinds of heartache if you don't.
Using an sd card reader on a pc, check md5 of your RUU zip file. If it checks out good, put the sd back in your rez and do an hboot power on and accept the update again. Report back with your findings. Also you will need to re-unlock your hboot after and install your recovery again.
Snuzzo said:
Using an sd card reader on a pc, check md5 of your RUU zip file. If it checks out good, put the sd back in your rez and do an hboot power on and accept the update again. Report back with your findings. Also you will need to re-unlock your hboot after and install your recovery again.
Click to expand...
Click to collapse
Hey, thanks. Yeah, the RUU does check out just fine against an MD5SUM.
nm.... just read your original post again and you say you did relock the phone. I was hoping it was something simple like that that was overlooked.
Carry on...
feralicious said:
Nothing to see here, folks, move along.
Click to expand...
Click to collapse
Right now, I cannot S-OFF because it requires a working stock image, and I'll be lucky to get anything more than CM9 unofficial working here.
You're too fast, now my bad post lives on...
So, when theh RUU failed, you unlocked again, flashed a custom recovery and tried to flash Nils' ROM?
Do you have a nandroid you can try to restore? Even if its the cm9 ROM at least to see if you can get it back to a working phone?
feralicious said:
You're too fast, now my bad post lives on...
So, when theh RUU failed, you unlocked again, flashed a custom recovery and tried to flash Nils' ROM?
Do you have a nandroid you can try to restore? Even if its the cm9 ROM at least to see if you can get it back to a working phone?
Click to expand...
Click to collapse
Well that's the trick. CM9 didn't work well enough to even be worth backing up. I'm trying to reinstall it again now just to see if I get there - and it looks like I will. Once I'm back up with that, I'm not sure where to go from there. The phone barely worked under CM9. Really hoping to get Nils' ROM on there, since it gives all the nice features of a stock device without the bloatware. Even if I never get S-OFF, I'll be perfectly happy with just Nils' software.
How about this... did you wipe everything before running the RUU? There's CleanWipe in the Development forum you can flash it from recovery and it will wipe everything 5 times!
This shouldn't make any difference, but there's also a different RUU, the OTA that's not global. You might try that one instead. I'm convinced that sometimes things are just voodoo even when they should be completely logical. That's definitely the case at work on the Avid systems I use.
Here's the link to it:
http://androidfiles.org/ruu/?dir=Vigor
feralicious said:
How about this... did you wipe everything before running the RUU? There's CleanWipe in the Development forum you can flash it from recovery and it will wipe everything 5 times!
This shouldn't make any difference, but there's also a different RUU, the OTA that's not global. You might try that one instead. I'm convinced that sometimes things are just voodoo even when they should be completely logical. That's definitely the case at work on the Avid systems I use.
Here's the link to it:
http://androidfiles.org/ruu/?dir=Vigor
Click to expand...
Click to collapse
I did try wiping everything first. No luck. I will try the CleanWipe tomorrow, because right now, whatever my issues are, I'm being prevented from solving them since I can't S-OFF and I can't even seem to get a working ROM to make the phone worth having! Ugh.
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Flyhalf205 said:
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Click to expand...
Click to collapse
Oh yeah! Try that. Someone else was having trouble and did it that way and it worked. Here's instructions, just make sure you use PH98IMG and not whatever is used in the instructions since it was written up for a different phone.
http://androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
Also, once you get your phone back to stock make a nandroid as soon as you flash the recovery again so you'll have that to go back to if you have any more issues.
Flyhalf205 said:
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Click to expand...
Click to collapse
Thank you, your magnanimity! Seriously, lol, you're gracing my thread just by being here. :victory:
feralicious said:
Oh yeah! Try that. Someone else was having trouble and did it that way and it worked. Here's instructions, just make sure you use PH98IMG and not whatever is used in the instructions since it was written up for a different phone.
http://androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
Also, once you get your phone back to stock make a nandroid as soon as you flash the recovery again so you'll have that to go back to if you have any more issues.
Click to expand...
Click to collapse
Thanks for the clicky, Feralicious. Same results, unfortunately. I'm going to try doing the RUU flash of Nils' ROM instead. Do you guys know where I can get the ICS firmware by itself? I cannot be sure that it's actually flashed right, unfortunately.
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Flyhalf205 said:
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Click to expand...
Click to collapse
I'll do that stuff and let you know. Thank you!
Yes, I am on 2.27 HBOOT.
Point of interest, though possibly unsurprising. When I send the lock command, it locks and reboots, but says "Failed" in my command window screen. Sure this is probably normal since the phone might just reboot before responding to the computer, but possibly an issue.
I believe that is the image I tried before, but I'll do it again both ways to be certain and report back soon! :good:
ncc74656m said:
Yes, I am on 2.27 HBOOT.
Point of interest, though possibly unsurprising. When I send the lock command, it locks and reboots, but says "Failed" in my command window screen. Sure this is probably normal since the phone might just reboot before responding to the computer, but possibly an issue.
I believe that is the image I tried before, but I'll do it again both ways to be certain and report back soon! :good:
Click to expand...
Click to collapse
My DNA said something about failing when I locked it. But it locked just fine.
Since it is failing.
fastboot oem rebootRUU
fastboot oem lock ----if unlocked
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
Should work Maybe
Flyhalf205 said:
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
Click to expand...
Click to collapse
Ok, so, this part including a factory reset got me to "HTC Quietly Brilliant" screen, but then it bootloops again. Tried factory resetting again to no avail. Trying the second part.
Flyhalf205 said:
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
Click to expand...
Click to collapse
Same thing as before unfortunately. :/ Performed a factory reset afterwards to be safe - no go. Everything shows OK though in both this and the above install. *shrug*
Flyhalf205 said:
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Click to expand...
Click to collapse
Proceeding with another attempt at installing CM9, I guess. Maybe the first one got hosed. If I get it booting in any form, I'll Nandroid it before trying anything else.
ncc74656m said:
Proceeding with another attempt at installing CM9, I guess. Maybe the first one got hosed. If I get it booting in any form, I'll Nandroid it before trying anything else.
Click to expand...
Click to collapse
I really wouldn't see why you would need a Sense rom to get s-off. I would imagine it would just need su and busybox installed. But nandroid then try a sense rom again. Make sure you flash the boot.img through fastboot