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.
I had followed this video ht tp://w ww.youtub e.com /watch?v=hQtUxEL8pd8 and did everything correctly. When I go to boot my phone up it shows the blue android boot animation then the green HTC animation then restarts.
Hboot 1.57
Somehow my recovery got deleted.
Clockworkmod recovery is installed.
I just don't know what to do
Is there a way I can just undo everything and go back to the stock rom?
Edit: Tried ViperROM and it's doing the exact same thing.
Make sure you are wiping everything except sdcard and then flash the rom. Maybe even try changing recoveries to 4ext.
Sent from my PG86100 using Tapatalk 2
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Jsparta26 said:
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Click to expand...
Click to collapse
I'm S-on, will it matter? And also I do mean 1.57. And one more thing. Does it matter if I boot up into a recovery using the command prompt? Also I'm not sure what kernel it is. I guess the one that's in the zip folder? Also sorry for slow responses I've been working days. Any chance you'll be on tomorrow around 7pm central?
Update: I reformatted everything and tried reinstalling Viperrom through CWM but no dice still boots up and resets. Got 4ext installed. Working from there.
Update: 4EXT is the best recovery I've ever seen and I'm never using CWM again.
Update: I installed VIperROM through 4ext and it's still restarting itself.
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Jsparta26 said:
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Click to expand...
Click to collapse
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I? Also i youtubed bootloop to see if it is really what's wrong and I came up with this video. ht tp ://www .y outube.co m/watch?v=OKXTD1-fqbc and my phones doing more than that. It's booting up all the way then once the screen and dock begins to load it restarts.
IAnb3rlin said:
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I?
Click to expand...
Click to collapse
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Jsparta26 said:
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Click to expand...
Click to collapse
How do I flash a kernel? I'm not really sure what one is, I just know it's really important.
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Jsparta26 said:
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Click to expand...
Click to collapse
I formatted everything using 4ext and installed a rom i also flashed the boot img just incase and it still restarted.
Here's the steps I took.
1. Format everything.
2. Download the.zip file and copy to SD card.
3. Load the recovery and enable smartflash.
4. Installed the rom.
5. Flashed the boot.img
6. Also tried without flashing the boot img.
And just to clarify. I'm installing ViperROM. And I only need the .zip file, correct?
I ended up using RUU to fix it and go back to the stock rom/ect, Then locked the bootloader unlocked it and flashed superuser and rooted it then got s-off using the wire trick. But after I rebooted it keeps taking me back to the jbear bootup logo and when I try to flash a recovery it doesn't load I just get the htc logo then jbear logo then it restarts. I followed this guide.htt p://w ww.yo utube.co m/ watch?v =tRj47iFQvbE I found here on the xda forums.
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Jsparta26 said:
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Click to expand...
Click to collapse
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
IAnb3rlin said:
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
Click to expand...
Click to collapse
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Jsparta26 said:
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Edit: just realized your using virgin mobile correct? I believe the reason your phone kept bootlooping with viper ROM was because of hboot. Try flashing a different hboot with the same method as the ruu and recovery.
Click to expand...
Click to collapse
I downloaded root checker and apparently I'm not root anymore. Yes I'm VM. I'm trying to rename the recovery and update it using the SD card now.
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
IAnb3rlin said:
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
Click to expand...
Click to collapse
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Jsparta26 said:
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Click to expand...
Click to collapse
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
IAnb3rlin said:
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
Click to expand...
Click to collapse
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Jsparta26 said:
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Click to expand...
Click to collapse
I just ended up unlocking the boot loader again and installing the recovery that way. Then saw this.. oh well lol. I really do appreciate the help. . I'm going to try to install viperrom again, and double backup this time! I'll let you know how it goes.
If I am S-On, is there a way to set it up so that i don't have to manually flash the boot.img every time? Btw, I am using TWRP
TRWP includes HTC Dumlock which makes it easier, but you'll always have to do some level of extra work when you're s-on. That's just the facts of life with HTC.
gleggie said:
If I am S-On, is there a way to set it up so that i don't have to manually flash the boot.img every time? Btw, I am using TWRP
Click to expand...
Click to collapse
S-off your phone, it's the only way to allow boot.img to be installed automatically along with a rom/kernel installer/etc..
Check out the second section of the TWRP OP: http://forum.xda-developers.com/showthread.php?t=1902381
It basically replaces your bootloader with a copy of recovery that is allowed to flash boot.img files directly, after which you have to replace the default boot again before you can boot. It lets you flash a kernel completely PC free, but it doesn't necessarily make it easier or simpler. There are still extra steps involved if you are s-on.
mjones73 said:
S-off your phone, it's the only way to allow boot.img to be installed automatically along with a rom/kernel installer/etc..
Click to expand...
Click to collapse
If you don't flash often I don't recommend going s-off. It makes it easier to brick the phone.
feralicious said:
If you don't flash often I don't recommend going s-off. It makes it easier to brick the phone.
Click to expand...
Click to collapse
I was just pointing out the only way to avoid manually flashing boot.img is to s-off.
Personally I've been s-off since the day the process was released and I've flashed numerous roms without issue.
Phone is currently bootlooping, so it's a softbrick. Tried installing MIUI like I normally would on my HTC One V, but apparently this phone is not as simple.
I'm running HBOOT-1.57.0000, S-ON, no way to get onto an operating system so all I have to work with is my recovery and fastboot. I was wondering if I could restore this phone so it's in working condition, stock, at best. I didn't drop $149 on this phone in order for it to be broken, but I doubt it's anything big if I can still turn it on.
This is a CDMA phone on Virgin Mobile.
LithGFX said:
Phone is currently bootlooping, so it's a softbrick.
Click to expand...
Click to collapse
Your phone is not a "softbrick". That term gets misused almost daily in these forums and for future reference here is my understanding of the "brick" modes:
1. Soft brick - a phone that won't boot at all (bootloader, recovery or Android) but shows some signs of life such as a glowing power led or the "QHUSB-DLOAD" status when connected to a PC which may or may not be recoverable
2. Hard brick - a phone that shows absolutely no signs of life and is confirmed not recoverable after trying all known methods to revive it
Other people may have slight different definitions but most would agree that the boot loop you described is not any type of "brick". I don't meant to pick on you but the "brick" term gets so overused and abused that I wanted to take this opportunity to clarify a little based on what I've experienced.
Back to your problem, I believe it is caused by not having a properly flash boot partition (kernel) and/or a ROM (you didn't specify which version of MIUI) that is incompatible with your current bootloader (hboot).
To recover your phone, download a "stockish" ROM like Harmonia then flash it after starting recovery using the following fastboot command:
fastboot boot recovery.img
Click to expand...
Click to collapse
If you are using 4EXT recovery make sure the FastBoot/S-ON option is disabled in the tools menu, then "format all partitions except SD card" in the wipe/format menu and flash the ROM.zip.
Reboot after the flash completes and you should have a working phone again.
ramjet73
ramjet73 said:
Your phone is not a "softbrick". That term gets misused almost daily in these forums and for future reference here is my understanding of the "brick" modes:
1. Soft brick - a phone that won't boot at all (bootloader, recovery or Android) but shows some signs of life such as a glowing power led or the "QHUSB-DLOAD" status when connected to a PC which may or may not be recoverable
2. Hard brick - a phone that shows absolutely no signs of life and is confirmed not recoverable after trying all known methods to revive it
Other people may have slight different definitions but most would agree that the boot loop you described is not any type of "brick". I don't meant to pick on you but the "brick" term gets so overused and abused that I wanted to take this opportunity to clarify a little based on what I've experienced.
Back to your problem, I believe it is caused by not having a properly flash boot partition (kernel) and/or a ROM (you didn't specify which version of MIUI) that is incompatible with your current bootloader (hboot).
To recover your phone, download a "stockish" ROM like Harmonia then flash it after starting recovery using the following fastboot command:
If you are using 4EXT recovery make sure the FastBoot/S-ON option is disabled in the tools menu, then "format all partitions except SD card" in the wipe/format menu and flash the ROM.zip.
Reboot after the flash completes and you should have a working phone again.
ramjet73
Click to expand...
Click to collapse
Alright thanks, I have a non-stock boot, by the way. Would I be able to just flash the boot.img that's in the ROM (I assume it's going to be there like most) to be on the safe side? I usually did that when I had a questionable kernel from a previous ROM on my One V.
LithGFX said:
I'm running HBOOT-1.57.0000, S-ON
Click to expand...
Click to collapse
LithGFX said:
Alright thanks, I have a non-stock boot, by the way. Would I be able to just flash the boot.img that's in the ROM (I assume it's going to be there like most) to be on the safe side? I usually did that when I had a questionable kernel from a previous ROM on my One V.
Click to expand...
Click to collapse
Hmmm....
You said you have hboot 1.57.0000 in the OP which is the Virgin Mobile stock hboot and not compatible with anything but ICS Sense based ROM's.
I don't think flashing the boot.img is going to fix anything if that kernel is incompatible with your hboot. The reason I recommended Harmonia is because I know it's compatible with the hboot you quoted and I'm sure it will give you a working phone, but you're welcome to try whatever you want.
ramjet73
ramjet73 said:
Hmmm....
You said you have hboot 1.57.0000 in the OP which is the Virgin Mobile stock hboot and not compatible with anything but ICS Sense based ROM's.
I don't think flashing the boot.img is going to fix anything if that kernel is incompatible with your hboot. The reason I recommended Harmonia is because I know it's compatible with the hboot you quoted and I'm sure it will give you a working phone, but you're welcome to try whatever you want.
ramjet73
Click to expand...
Click to collapse
Oh, to respond to the other post about which version of MIUI, it was this one:
http://forum.xda-developers.com/showthread.php?t=2047911
But, I was wondering if I should flash the boot.img from Harmonia's ZIP is because I'd think that the old boot.img I have on here already would not work well with it.
LithGFX said:
Oh, to respond to the other post about which version of MIUI, it was this one:
But, I was wondering if I should flash the boot.img from Harmonia's ZIP is because I'd think that the old boot.img I have on here already would not work well with it.
Click to expand...
Click to collapse
That's what I thought. The MIUI ROM you linked is JB based and won't boot with the 1.57 hboot. However, you already flashed that ROM so you need to flash an entire replacement ROM, not just the boot partition.
I've already outlined what is needed in my first post above, but if you want to try to recover another way someone else is going to have to help you.
ramjet73
ramjet73 said:
That's what I thought. The MIUI ROM you linked is JB based and won't boot with the 1.57 hboot. However, you already flashed that ROM so you need to flash an entire replacement ROM, not just the boot partition.
I've already outlined what is needed in my first post above, but if you want to try to recover another way someone else is going to have to help you.
ramjet73
Click to expand...
Click to collapse
What I'm going to do is flash the ROM you provided me with. I'm kind of unhappy right now because I'm having to wait an hour due to these highly limited server speeds. But I can try. I tried to use my restore and that failed, though, and that was stock.
ramjet73 said:
That's what I thought. The MIUI ROM you linked is JB based and won't boot with the 1.57 hboot. However, you already flashed that ROM so you need to flash an entire replacement ROM, not just the boot partition.
I've already outlined what is needed in my first post above, but if you want to try to recover another way someone else is going to have to help you.
ramjet73
Click to expand...
Click to collapse
The phone is still bootlooping, anything else I can do to try to fix it? I installed the ROM, that's it so far.
EDIT: Fixed bootloop by flashing new kernel. Thanks so much for the help, ramjet. You saved me my money.
LithGFX said:
The phone is still bootlooping, anything else I can do to try to fix it? I installed the ROM, that's it so far.
EDIT: Fixed bootloop by flashing new kernel. Thanks so much for the help, ramjet. You saved me my money.
Click to expand...
Click to collapse
Glad you got it working.
The kernel should have flashed correctly with the ROM if you started recovery via "fastboot boot" and had SmartFlash disabled in 4EXT , but the important thing is that you are back up and running now.
ramjet73
ramjet73 said:
Glad you got it working.
The kernel should have flashed correctly with the ROM if you started recovery via "fastboot boot" and had SmartFlash disabled in 4EXT , but the important thing is that you are back up and running now.
ramjet73
Click to expand...
Click to collapse
The kernel didn't end up flashing correctly so I had to do it from fastboot, but I was up and working.
Now I need to figure out how to flash a ROM like MeanROM because right now, it's boot looping.
I am selling one of my Rezounds I need to return it to mostly stock.
Before installing the latest Infection rom I was on the current OTA rom. Basically I think all I need to do is reflash the stock recovery image and the current OTA rom and if needed go back to locked. Problem is, I don't have a copy of the recovery.img from the current OTA rom. Can anybody link me to it. Thanks
Sent from my Infected Rezound
Here is a post with the full OTApkg.zip for 4.05.605.14:
http://forum.xda-developers.com/showpost.php?p=40757466&postcount=19
If you extract the firmware.zip, there is the recovery.img which you can either put into a custom ph98img.zip and run in hboot or flash it from your computer using adb stuff. I recently had to restore my Rez back to stock as it is getting returned to Verizon for a replacement. I used the ph98img route to reinstall recovery after unrooting. I also then had to S-on the phone so I had to make sure it was bone stock so the S-on didn't brick it.
ETA: I'm not sure if that full OTApkg.zip will be enough to get you back to stock but what I had done in the past was to flash this stock rooted rom with Amonra 3.16 http://forum.xda-developers.com/showpost.php?p=40941755&postcount=1 ( I was already on 4.05.605.14), do the full unroot option using the supersu app that was already there, and then flash the stock recovery and I was back to fully stock.
---------- Post added at 12:32 PM ---------- Previous post was at 12:09 PM ----------
Any chance your phone was S-off?
mikeyk101 said:
Here is a post with the full OTApkg.zip for 4.05.605.14:
http://forum.xda-developers.com/showpost.php?p=40757466&postcount=19
If you extract the firmware.zip, there is the recovery.img which you can either put into a custom ph98img.zip and run in hboot or flash it from your computer using adb stuff. I recently had to restore my Rez back to stock as it is getting returned to Verizon for a replacement. I used the ph98img route to reinstall recovery after unrooting. I also then had to S-on the phone so I had to make sure it was bone stock so the S-on didn't brick it.
ETA: I'm not sure if that full OTApkg.zip will be enough to get you back to stock but what I had done in the past was to flash this stock rooted rom with Amonra 3.16 http://forum.xda-developers.com/showpost.php?p=40941755&postcount=1 ( I was already on 4.05.605.14), do the full unroot option using the supersu app that was already there, and then flash the stock recovery and I was back to fully stock.
---------- Post added at 12:32 PM ---------- Previous post was at 12:09 PM ----------
Any chance your phone was S-off?
Click to expand...
Click to collapse
Thanks... I am S-ON but that should really be all I need... I don't really need to go 100% pure stock, but if I can get it close that will work. Replacing the recovery image and leaving it S-ON, then flash the Stock OTA Rooted ROM from this thread: http://forum.xda-developers.com/showthread.php?t=2260154 and I think I will be close enough to sell it. If someone wants it with a custom ROM I can just leave TWRP and Infection, or whatever ROM they want, but I just need a quick option to return to "stock" if the buyer wants.
acejavelin said:
Thanks... I am S-ON but that should really be all I need... I don't really need to go 100% pure stock, but if I can get it close that will work. Replacing the recovery image and leaving it S-ON, then flash the Stock OTA Rooted ROM from this thread: http://forum.xda-developers.com/showthread.php?t=2260154 and I think I will be close enough to sell it. If someone wants it with a custom ROM I can just leave TWRP and Infection, or whatever ROM they want, but I just need a quick option to return to "stock" if the buyer wants.
Click to expand...
Click to collapse
You may want to flash the rooted stock before replacing the recovery back to stock. I don't know if the stock recovery will allow it...
mikeyk101 said:
You may want to flash the rooted stock before replacing the recovery back to stock. I don't know if the stock recovery will allow it...
Click to expand...
Click to collapse
The beauty of being unlocked is it doesn't matter... All I need to do is go into fastboot and use "fastboot boot recovery.img" for TWRP and I can flash anything, irregardless of what the installed recovery allows. But thanks for the warning, this is probably what I would do anyway.
Doh!, I completely forgot about that way... Yup, that would work as well
I'm trying to give this phone to my buddy. Haven't used it since I got the S4, and he is still using a Dinc. I tried what was listed here, but it's only made things worse. I was on Stock 4.03.605 (leaked Global RUU) unlocked, rooted, s-on. I tried updating the firmware with the OTAzip. I made the PH98IMG.zip, and ran it through the bootloader. It only updated Hboot from 2.7 to 2.8. It did NOT give me 4.05.605 like I was looking for. I tried to run the Global Stock rom but got stuck in a white HTC screen. The only thing I can make work right now is a viperrom, but wifi will not turn on. I was hoping to give this to him as close to stock, but without wifi, it's not going to be very useful.
Currently I have it locked s-on with stock recovery, but I can unlock and put amon ra back on it. I use a mac so commands are a bit different for me, but I know the basics and what to on the mac (mostly). Any help would be appreciated. I tried to run the leaked global RUU again to reset it, but because the Hboot updated, it won't run it. I can't find an RUU for 4.05.605
318sugarhill said:
I'm trying to give this phone to my buddy. Haven't used it since I got the S4, and he is still using a Dinc. I tried what was listed here, but it's only made things worse. I was on Stock 4.03.605 (leaked Global RUU) unlocked, rooted, s-on. I tried updating the firmware with the OTAzip. I made the PH98IMG.zip, and ran it through the bootloader. It only updated Hboot from 2.7 to 2.8. It did NOT give me 4.05.605 like I was looking for. I tried to run the Global Stock rom but got stuck in a white HTC screen. The only thing I can make work right now is a viperrom, but wifi will not turn on. I was hoping to give this to him as close to stock, but without wifi, it's not going to be very useful.
Currently I have it locked s-on with stock recovery, but I can unlock and put amon ra back on it. I use a mac so commands are a bit different for me, but I know the basics and what to on the mac (mostly). Any help would be appreciated. I tried to run the leaked global RUU again to reset it, but because the Hboot updated, it won't run it. I can't find an RUU for 4.05.605
Click to expand...
Click to collapse
My circumstance was very specific, this thread was not really intended to be a guide to take any version of software to another, I already had the firmware (HBoot & radios) for 4.5.605.14, just needed a few pieces to get back to "stockish"... There are other ways to return to stock for different software versions and this thread doesn't address any of those.
The OTApkg.zip is only for going from 3.14.605.13 to 4.5.605.14, no other combinations of versions will work properly. I am surprised that HBoot updated... what radios are you on now? If the radios updated then you might be OK, you can just unlock, then fastboot boot recovery.img of TWRP and flash in the stock/rooted 4.5.605.14 ROM (NOT an RUU, but just the ROM), otherwise you could be in a situation where you need to S-OFF and flash radios and tweak from there. If your HBoot updated then the leaked RUU won't work either, you could be in a tight spot.
BTW, the reason Viper won't work is you likely have a kernel mismatch, to install a ROM on an S-ON Rezound you need to flash the boot.img separately, that is where the kernel is, but that also requires you to be unlocked by HTCdev.
acejavelin said:
My circumstance was very specific, this thread was not really intended to be a guide to take any version of software to another, I already had the firmware (HBoot & radios) for 4.5.605.14, just needed a few pieces to get back to "stockish"... There are other ways to return to stock for different software versions and this thread doesn't address any of those.
The OTApkg.zip is only for going from 3.14.605.13 to 4.5.605.14, no other combinations of versions will work properly. I am surprised that HBoot updated... what radios are you on now? If the radios updated then you might be OK, you can just unlock, then fastboot boot recovery.img of TWRP and flash in the stock/rooted 4.5.605.14 ROM (NOT an RUU, but just the ROM), otherwise you could be in a situation where you need to S-OFF and flash radios and tweak from there. If your HBoot updated then the leaked RUU won't work either, you could be in a tight spot.
BTW, the reason Viper won't work is you likely have a kernel mismatch, to install a ROM on an S-ON Rezound you need to flash the boot.img separately, that is where the kernel is, but that also requires you to be unlocked by HTCdev.
Click to expand...
Click to collapse
Damn....I have tried to flash the kernel (boot.img) through the fastboot command, but it never works right and leaves me stuck with a white HTC screen. Again, if it's bricked, it's not the end of the world for me as I upgraded to the S4, but my buddy was looking forward to 4g.
Basebands are 2.23.10.0123r, and 2.23.10.0124r
Well I think you're in luck, you have the firmware for the latest software installed... hboot and radios match for 4.5.605.14, all you need now is to unlock and flash a correct ROM! Working so I can't grab link right now, just get unlocked via HTCdev and post when that's done... all isn't list yet!
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
acejavelin said:
Well I think you're in luck, you have the firmware for the latest software installed... hboot and radios match for 4.5.605.14, all you need now is to unlock and flash a correct ROM! Working so I can't grab link right now, just get unlocked via HTCdev and post when that's done... all isn't list yet!
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Click to expand...
Click to collapse
I just unlocked again..I don't need the HTCdev site anymore. The token and all that jazz is all saved to an android folder on the my macHD. I downloaded TRWP. Should I flash that next?
318sugarhill said:
I just unlocked again..I don't need the HTCdev site anymore. The token and all that jazz is all saved to an android folder on the my macHD. I downloaded TRWP. Should I flash that next?
Click to expand...
Click to collapse
If you wish..
Actually installing a custom recovery is not required as long as you can fastboot boot the recovery image.
Did you want to return to mostly stock, or did you want to run a custom ROM like Infection Or something else?
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
acejavelin said:
If you wish..
Actually installing a custom recovery is not required as long as you can fastboot boot the recovery image.
Did you want to return to mostly stock, or did you want to run a custom ROM like Infection Or something else?
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Click to expand...
Click to collapse
I was looking for stock. 4.05.605 is ideal so he can play with it if he wishes. I don't want to have to field questions once its his. I don't mind helping him, but I don't want to cause him issues he's not looking for.
I have the image downloaded. How do I fastboot boot the recovery? Just ./fastboot boot recovery.img (as i have renamed the img as recovery.img)
Use this one
http://forum.xda-developers.com/showthread.php?t=2260154
[ROM] OTA-Global-Stock-4.05.605.14 710RD-Rooted 5/1/13
Flash ROM, extract boot.img and flash then should be goof to go.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
acejavelin said:
Use this one
http://forum.xda-developers.com/showthread.php?t=2260154
[ROM] OTA-Global-Stock-4.05.605.14 710RD-Rooted 5/1/13
Flash ROM, extract boot.img and flash then should be goof to go.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Click to expand...
Click to collapse
I tried this earlier, but I get the white HTC screen lockup. When you say extract boot.img, you mean unzip the download, pull out the boot.img and put it in my android folder to fastboot flash correct? The command I use is ./fastboot flash boot boot.img. It appears everything works, but it never boots. Just gets stuck in the white screen.
I'm downloading it now, should be about 14 more minutes. I will try it all again, and see what happens. Fingers crossed. let me know if my commands are wrong or I'm missing anything. the ./ is needed for mac.
If you load TWRP via Fastboot boot it will flash boot.img for you, if you load if from hboot you have to flash manually.
Before flashing ROM, download and flash the CleanWipe x5 script found in a thread on the development forum.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
acejavelin said:
If you load TWRP via Fastboot boot it will flash boot.img for you.
Before flashing ROM, download and flash the CleanWipe x5 script found in a thread on the development forum.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Click to expand...
Click to collapse
I flashed twrp via fastboot flash recovery. I'm missing something. what is fastboot boot for TWRP?
318sugarhill said:
I flashed twrp via fastboot flash recovery. I'm missing something. what is fastboot boot for TWRP?
Click to expand...
Click to collapse
That works, just requires extra steps. I don't flash recovery anymore, you can go into fastboot on the phone, then execute fastboot boot recovery.img from PC, this gives an unlocked HTC phone temporary S-OFF saving steps of flashing boot.img seperately and avoiding the dreaded Tampered flag (if it hasn't been set).
Lots of ways to skin a cat I guess.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
acejavelin said:
That works, just requires extra steps. I don't flash recovery anymore, you can go into fastboot on the phone, then execute fastboot boot recovery.img from PC, this gives an unlocked HTC phone temporary S-OFF saving steps of flashing boot.img seperately and avoiding the dreaded Tampered flag (if it hasn't been set).
Lots of ways to skin a cat I guess.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Click to expand...
Click to collapse
I have the tampered flag. But I don't care about that. I'm long past warranty anyway. But when I use the command ./fastboot boot recovery.img it says cannot load "recovery.img"
318sugarhill said:
I have the tampered flag. But I don't care about that. I'm long past warranty anyway. But when I use the command ./fastboot boot recovery.img it says cannot load "recovery.img"
Click to expand...
Click to collapse
You need to extract the recovery.img file from the TWRP zip and put it in the fastboot directory.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app