Stuck in Recovery/Bootloader - Sprint HTC EVO 4G LTE

I have S-off, Unlocked Bootloader, and my EVO is rooted. I have HBOOT 2.09
I tried to install Vanir so I flashed the Gapps 4.4 in TWRP which seemed to work, then I tried to flash Vanir after and got an error.
Now no matter what I do I boot right into recovery and can't seem to figure my way out. Clearly I'm in over my head so if someone could just help me get back to stock at least I would really appreciate it. Thanks

Did you install the proper twrp for kitkat.. if so just try flashing the Rom first then let it boot up and sit for a minute.. then boot back into recovery and flash gapps this works for me..
Sent from my EVO using Tapatalk

It's 2.6.3 twrp, and whenever I tried to install the ROM it gave me an error message.

MrScrufff said:
I have S-off, Unlocked Bootloader, and my EVO is rooted. I have HBOOT 2.09
I tried to install Vanir so I flashed the Gapps 4.4 in TWRP which seemed to work, then I tried to flash Vanir after and got an error.
Now no matter what I do I boot right into recovery and can't seem to figure my way out. Clearly I'm in over my head so if someone could just help me get back to stock at least I would really appreciate it. Thanks
Click to expand...
Click to collapse
Even though you use TWRP 2.6.3.0, it has to be a modded one that allows SELinux support.
Click Me -Flash the Recovery in the OP of this thread
If you have a working fastboot and adb environment on your computer you can flash it by going to to fastboot USB in the bootloader of your phone, and make sure your phone is connected to your PC properly.
Place the .img file in your adb and fastboot folder and then open a command prompt from that location.
then type fastboot flash recovery "recoveryfilename.img" and ofcourse replace recoveryfilename with the actual filename.
after that reboot into recovery and try reflashing Vanir.
This is the method I use to flash recoveries, its fairly simple and fast in my opinion.
Hope this helps.

Link420able said:
Even though you use TWRP 2.6.3.0, it has to be a modded one that allows SELinux support.
Click Me -Flash the Recovery in the OP of this thread
If you have a working fastboot and adb environment on your computer you can flash it by going to to fastboot USB in the bootloader of your phone, and make sure your phone is connected to your PC properly.
Place the .img file in your adb and fastboot folder and then open a command prompt from that location.
then type fastboot flash recovery "recoveryfilename.img" and ofcourse replace recoveryfilename with the actual filename.
after that reboot into recovery and try reflashing Vanir.
This is the method I use to flash recoveries, its fairly simple and fast in my opinion.
Hope this helps.
Click to expand...
Click to collapse
Thanks, I just ran the RUU and went back to stock and everything's good

MrScrufff said:
Thanks, I just ran the RUU and went back to stock and everything's good
Click to expand...
Click to collapse
Ah ok. Glad you got everything sorted out.

Good deal.

Sometimes an RUU is all you have left. A powerful option no doubt.

Related

Cannot boot into rom/ cannot boot into recovery HELP!

First of all i've been searching for a way to fix this for hours now without a solution.
My problem is as follows:
i installed official miui beta and got stuck with a boot loop, i was running 4text recovery but i wanted to try something different so i flashed twrp recovery in fastboot. however whenever i try to go into recovery now it just reboots and goes into boot loop again, so i cannot access recovery or boot into my rom.
I have tried flashing several recoverys via fastboot but each time it just reboots and does not enter recovery.
i have also tried rebooting into recovery using fastboot reboot recovery and adb reboot recovery but still it didn't work.
i have flashed another boot.img but now it just gets stuck on miui screen instead of boot loop
is there any way i can get any recoverys to work? i have tried looking for a 4text recovery.img as 4text was the last recovery to work but i can only seem to find the app that flashes it.
i have also tried flashing a rom through fastboot by typing fasboot flash zip rom.zip but it just says failure.
i am now downloading RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_radio_11.77.3504.00U_11.25.3504. and am going to try rename it to PG86IMG and update through bootloader after relocking it and then unlocking it again but i am not sure that will work.
in short i flashed a new recovery but it just reboots device when i try and enter it and the rom i am on happens to be stuck on boot loop so i cannot get in rom or recovery and flashing a new recovery does not work.
BTW i am S-ON HBOOT-1.49.0018
sorry for the lengthy post and also any grammatical errors as i am tired
Comments withdrawn
zcink said:
The whole problem, which is always the problem is you are S-ON. The MIUI rom will NOT run unless you install the newest firmware. You cannot install the newest firmware with S-ON because it is locked up in a partition that you cannot access unless you go s-off.
Has nothing to do with the recovery. I've been using 4ext recovery pretty much the whole time I've owned my EVO 3d and never had one single problem with it.
There are roms you can run with s-on but not the MIUI one.
Click to expand...
Click to collapse
cool, didn't know that, my problem now then is how can i reflash a different rom, bearing in mind that i cannot access recovery? do you think putting the pg86img stock ruu thingy on my sd and letting bootloader install that will work?
powellyable said:
cool, didn't know that, my problem now then is how can i reflash a different rom, bearing in mind that i cannot access recovery? do you think putting the pg86img stock ruu thingy on my sd and letting bootloader install that will work?
Click to expand...
Click to collapse
I do believe that if you are s-on, you should be able to relock the phone and then run the rru from your computer.
sonza said:
I do believe that if you are s-on, you should be able to relock the phone and then run the rru from your computer.
Click to expand...
Click to collapse
My next step was to relock it and run the ruu through bootloader, can you do it through computer/fastboot?
Sorry, I haven't been on the forum for a while.
Read the following link,
http://forum.xda-developers.com/showthread.php?t=1194053&highlight=relock
It should help you with the process.
The rru file you have should be an executable file that the name ends with "signed.exe" if memory serves. I do believe you can run this from your windows desktop if you are using windows. The link above has the adb command to use to relock the phone.
Once you are up and running again, you can install an ics rom even if you have s-on. I am running one but there are a few steps you need to do in the correct order so you don't end up where you are.
Good luck and have a great weekend!
Here is another good link to do what you are wanting to do.
http://forum.xda-developers.com/showthread.php?t=1578977
This might be even easier for you.
Comments withdrawn

[Q] Possible bricked device... Any help greatly appreciated.

Hi All,
Long time lurker and I appreciate all the work everyone does here. It makes owning an android device a great amount of fun...but as you can see by the title of the thread, a great amount of stress as well :laugh:
My device is unlocked and I've used CWM and recenlty noticed that along one of my flashes TWRP 2.4 installed over CWM. All is well because I was meaning to switch over and try this recovery out. Smooth, fast, I like. But I recently installed CM 10.1 using the october version with the JB bootloader because I did not have it. Everything was nice, but I wanted to update CM 10.1 to a more recent UNOFFICIAL build so I flased the 3/20 version on my device. Everything was smooth but the WiFi dropped all the time so I decided to wait out a more stable "official" version of CM 10.1. Take note that I have(had) TWRP 2.4. Now I wanted to stick with JB 4.2.X so I decided to flash Energy's 3/21 build but this hung up on the ASUS screen... So I decided to reflash the rom but first installing the JB bootloader and partitions zip. Still no luck and while exiting TWRP, I noticed that it stated that my device isn't rooted and would I like to root? So I swiped and did it but it seems that the JB bootloader and partitions zip file erased everything on my device, Roms, GAPPS, SU, backups...gone.
The next thing I did was execute Urkels fresh root and fresh start and that seemed to go through all the steps with no issue. When I went back into recovery I noticed that I now have TWRP 2.2.2.1 with a JB bootloader... so what ever I did downgraded TWRP? Ok... Now I wanted to play it safe and stick to the October version of CM 10.1 with the JB bootloader but while flashing the rom (ext SDCARD) i receive an error. I decided to re-execute Urkels fresh root and fresh start and now all my device does is boot into TWRP 2.2.2.1. I can't use fastboot even with holding the power button and vol down.
At this point I feel lost and defeated, I can't use external SD anymore and I can only mount the system. So I decided to see if ADB works. ADB works great in recovery and am able to send files to the device. I sent a ROM to see if I can install but it fails because it can't mount the cache and this is where I am now. Lost... confused and desperate for help :crying: I'll make sure XDA gets a nice donation if anyone can help me out!
What works -
boot to TWRP 2.2.2.1 (thats all)
ADB in recovery
What doesn't-
No rom installed
No backup
No fastboot
My troubleshooting
Again ANY help is appreciated!
Mike
Would I be able to update TWRP within TWRP using a 2.4.4.0 zip file?
TheYoz said:
Would I be able to update TWRP within TWRP using a 2.4.4.0 zip file?
Click to expand...
Click to collapse
This is happening because you are now on 4.2.1 bootloader with an old TWRP which is not compatible with the new bootloader.
When you say you cannot access fast boot do you mean the usb icon is missing? If you do that is part of the new bootloader. As soon as you get to where the icons are you are automatically in fast boot unless you select one of the icons.
I'm out at the moment but if you reply letting me know that you can get to the icons I will post a file when I get back and some instructions to downgrade you to old bootloader and compatible TWRP.
flumpster said:
This is happening because you are now on 4.2.1 bootloader with an old TWRP which is not compatible with the new bootloader.
When you say you cannot access fast boot do you mean the usb icon is missing? If you do that is part of the new bootloader. As soon as you get to where the icons are you are automatically in fast boot unless you select one of the icons.
I'm out at the moment but if you reply letting me know that you can get to the icons I will post a file when I get back and some instructions to downgrade you to old bootloader and compatible TWRP.
Click to expand...
Click to collapse
I figured my TWRP version might have been the culprit...
When I restart and hold the vol down button it normally would activate fastboot, now it goes directly to TWRP, no icons whatso ever. Before I would get the recovery icon, a usb (I think) and an option to wipe data. I can't get to that screen anymore. Is there a command in adb that will allow me to restart to fastboot from recovery? I myself am at work too so I will test anything I can in 3 - 4 hours. Thanks for taking the time to respond! :good:
So basically I won't be able to put TWRP 2.4.4.0 within my current version of TWRP?
TheYoz said:
I figured my TWRP version might have been the culprit...
When I restart and hold the vol down button it normally would activate fastboot, now it goes directly to TWRP, no icons whatso ever. Before I would get the recovery icon, a usb (I think) and an option to wipe data. I can't get to that screen anymore. Is there a command in adb that will allow me to restart to fastboot from recovery? I myself am at work too so I will test anything I can in 3 - 4 hours. Thanks for taking the time to respond! :good:
So basically I won't be able to put TWRP 2.4.4.0 within my current version of TWRP?
Click to expand...
Click to collapse
The version of TWRP you have will not mount the partitions you need to flash anything. You either need to downgrade the bootloader so that version of TWRP will work or get the version of TWRP back on there that was edited to work with the new 4.2.1 bootloader.
When you installed that partition.zip from energy rom it installed the new bootloader and the compatible twrp the same time. To go back he also has a zip that will restore old bootloader and old twrp. This is what you should have done.
What I am worried about now is the fact that you cannot even get to fastboot from the buttons.
Try adb reboot bootloader.
If that lets you in then download this .. http://flumpster.lolcakes.com/android/blob and place it in your fastboot directory.
Now type.
fastboot -i 0x0B05 flash staging blob
wait for it to fully flash and then type
fastboot -i 0x0B05 reboot
Give it about 20 seconds, if it doesn't restart then you will have to hold the power button down for 10 seconds to force a restart.
When it restarts it should now start to fill the blue line on the Asus screen which will flash the old bootloader and compatible TWRP. If it does this then great, just wait until it has finished and it should put you back into twrp where you will be able to install a rom off your external SD.
If it does not do the blue line then we have bigger probs and I hope you have nvflash backup files.
flumpster said:
The version of TWRP you have will not mount the partitions you need to flash anything. You either need to downgrade the bootloader so that version of TWRP will work or get the version of TWRP back on there that was edited to work with the new 4.2.1 bootloader.
When you installed that partition.zip from energy rom it installed the new bootloader and the compatible twrp the same time. To go back he also has a zip that will restore old bootloader and old twrp. This is what you should have done.
What I am worried about now is the fact that you cannot even get to fastboot from the buttons.
Try adb reboot bootloader.
If that lets you in then download this .. http://flumpster.lolcakes.com/android/blob and place it in your fastboot directory.
Now type.
fastboot -i 0x0B05 flash staging blob
wait for it to fully flash and then type
fastboot -i 0x0B05 reboot
Give it about 20 seconds, if it doesn't restart then you will have to hold the power button down for 10 seconds to force a restart.
When it restarts it should now start to fill the blue line on the Asus screen which will flash the old bootloader and compatible TWRP. If it does this then great, just wait until it has finished and it should put you back into twrp where you will be able to install a rom off your external SD.
If it does not do the blue line then we have bigger probs and I hope you have nvflash backup files.
Click to expand...
Click to collapse
Crossing my fingers... I will try what you mentioned and no, I don't have NVFLASH. Something that I have been meaning to do for a few weeks now too. Thanks for the help I will update when I get a chance to try.
Mikw
TheYoz said:
Crossing my fingers... I will try what you mentioned and no, I don't have NVFLASH. Something that I have been meaning to do for a few weeks now too. Thanks for the help I will update when I get a chance to try.
Mikw
Click to expand...
Click to collapse
You cannot do the nvflash process now. You could only do it while on ICS and there is no way back to ICS without having nvflash backups.
flumpster said:
You cannot do the nvflash process now. You could only do it while on ICS and there is no way back to ICS without having nvflash backups.
Click to expand...
Click to collapse
I am able to adb reboot bootloader, and it brings me to fastboot!
I successfully executed the steps you gave me but I didn't get the android screen with the blue line... it went back to TWRP 2.2.2.1. Can I fastboot the new version of TWRP?
TheYoz said:
I am able to adb reboot bootloader, and it brings me to fastboot!
I successfully executed the steps you gave me but I didn't get the android screen with the blue line... it went back to TWRP 2.2.2.1. Can I fastboot the new version of TWRP?
Click to expand...
Click to collapse
Tried one more time with no success... Please let me know if I have any other options since I can get to fastboot via ADB.
I think the reason I am running into this mess is because I didn't download the JB update from ASUS and move the system.blob file according to Urkel fresh start
TheYoz said:
Tried one more time with no success... Please let me know if I have any other options since I can get to fastboot via ADB.
I think the reason I am running into this mess is because I didn't download the JB update from ASUS and move the system.blob file according to Urkel fresh start
Click to expand...
Click to collapse
I have even tried installing the TWRP.blob (newest JB version) file using this method but still reverts to version 2.2.2.1. I'm stumped
TheYoz said:
I have even tried installing the TWRP.blob (newest JB version) file using this method but still reverts to version 2.2.2.1. I'm stumped
Click to expand...
Click to collapse
I was worried about this. I have seen loads of people with the same problem you have over on the tf300 forums.
They can access fastboot thru adb reboot fastboot and it appears to send the file over ok but then it doesn't work.
When you mentioned you couldn't get to fastboot by holding button combo it looked like the same prob as them.
Have a look at this thread. http://forum.xda-developers.com/showthread.php?t=2179874
flumpster said:
I was worried about this. I have seen loads of people with the same problem you have over on the tf300 forums.
They can access fastboot thru adb reboot fastboot and it appears to send the file over ok but then it doesn't work.
When you mentioned you couldn't get to fastboot by holding button combo it looked like the same prob as them.
Have a look at this thread. http://forum.xda-developers.com/showthread.php?t=2179874
Click to expand...
Click to collapse
So I probably need to send it to ASUS or wait for a solution? That is for the TF300 would I be able to use any steps for that device with mine?
Also,
I purchased this in January 2012 from best buy, any possibility I can go through them to have this issue fixed?
TheYoz said:
I have even tried installing the TWRP.blob (newest JB version) file using this method but still reverts to version 2.2.2.1. I'm stumped
Click to expand...
Click to collapse
Flash the .img not the blob that should fix your issue.
Loco0729 said:
Flash the .img not the blob that should fix your issue.
Click to expand...
Click to collapse
I doubt it will but he can try.
No luck flashing the .img file instead. This is the worst
Flumpster thanks a bunch for all of your help. I ended up sending in the tablet, as expected they had to replace the motherboard.:
They quoted me this origionally:
Parts: $165
Labor: $65
Shipping $10
TOTAL $240!!!
I called and complained until my eyes popped out of my head and they ended up replacing the motherboad and shipped it back to me for $150. Now I think I'm going to sell this thing with the dock and buy a Nexus 10. Again, thanks for your help.
Another note... It will probably be a pain to unlock and root this thing again after the RMA im assuming. No more ASUS.

*$20 BOUNTY*[Q] How to return to stock rom if I can only enter fastboot mode?

So I flashed cm 10.1 before achieving S-Off. Bootloader unlocked, rooted with TWRP installed. It sits on "quietly brilliant". I can get into fastboot and recovery, but cannot get any files onto my sd card. Can someone help me get back to a stock rooted rom so I can achieve S-Off properly? Or if it's easier, I'll go all the way to complete stock and start over. Any help is greatly appreciated.
IMMEDIATE $20 PAYPAL TO THE PERSON WHO HELPS ME GET THIS PHONE WORKING
striketrue said:
So I flashed cm 10.1 before achieving S-Off. Bootloader unlocked, rooted with TWRP installed. It sits on "quietly brilliant". I can get into fastboot and recovery, but cannot get any files onto my sd card. Can someone help me get back to a stock rooted rom so I can achieve S-Off properly? Or if it's easier, I'll go all the way to complete stock and start over. Any help is greatly appreciated.
Click to expand...
Click to collapse
You most likely need to fastboot flash the kernel (boot.img) so the ROM will boot. Just another reason to get S-off
Sent from my EVO using xda premium
Would it work to flash the stock kernel and then stock RUU? Also, twrp cannot mount my sd card.
striketrue said:
Would it work to flash the stock kernel and then stock RUU? Also, twrp cannot mount my sd card.
Click to expand...
Click to collapse
You have to install the stock recovery first as I recall, then you can RUU.
Sent from my EVO using xda premium
i tried flashing stock recovery from fastboot and i got a "not allowed" message.
Why can't you take out your sd card plug in the pc and place meanbean rom on there. Flash meanbean which will flash the kernel. Then flash stock rooted rom.
Sent from my EVO using Tapatalk 2
Would be better help if I knew more of what is going on. Were you trying to S-OFF with CM10.1 installed? Did you just flash CM10.1 while S-ON and can't get the phone to boot? But anywho... with what I know now:
If you still have the CM10.1 ROM on your phone:
take the boot.img out of the .zip and
fastboot flash boot boot.img
that will install the boot.img / kernel and should allow your phone to boot.
Then you can go back in TWRP and flash a stock ROM.
To flash a ROM in fastboot:
fastboot -w
to wipe you device
fastboot update ROM.zip
that will install your ROM in fastboot mode.
fastboot flash boot boot.img after too I assume.
Or you can even do so by using adb in TWRP:
adb shell
mount data
adb push d:\custom_rom.zip /data/
Wait until the push finishes and restart your device to recovery again with "adb reboot-bootloader"
mount data
mount /data /sdcard (mount the data folder into your sdcard folder)
find your ROM.zip
Confirm the flash by following the on-screen instructions
if no errors then reboot the device
Also, in TWRP with your phone plugged into the computer you should be able to mount the phone to get access to your storage on your computer. Not 100% sure why that would matter or why you need to get to your storage though. I'm pretty sure that's called USB-OTG.
thicklizard said:
Why can't you take out your sd card plug in the pc and place meanbean rom on there. Flash meanbean which will flash the kernel. Then flash stock rooted rom.
Click to expand...
Click to collapse
Also another option.
If you're trying to get the .zip for the boot.img just download the version you need from the computer, open the .zip, pull the boot.img out and do the fastboot command to install the boot.img / kernel.
If you need or want to RUU then you should be able to:
fastboot oem lock
that will obviously relock your device
then you can fastboot oem rebootRUU
then fastboot flash zip RUU.zip (assuming you have your proper RUU already) when on the black HTC screen
after that completes fastboot reboot-bootloader
Then you'll be back to stock and should be able to boot the device, root, or whatever you please.
I think I covered every option. Lol.
Personally, I would just RUU again.
I've done this before with CM10 while trying to gain S-OFF and just RUU'd my device to see what would happen.
Keep in mind: anything can happen. I went into the process knowing there would be a possibility of a fail in which case I would smash the phone and pay $150 to asurion to get another device since I had the protection from Sprint.
TWRP will not mount any storage.
striketrue said:
TWRP will not mount any storage.
Click to expand...
Click to collapse
Did you read my post? lol.
striketrue said:
TWRP will not mount any storage.
Click to expand...
Click to collapse
Reflash twrp it may have gotten corrupted.
Sent from my EVO using Tapatalk 2
Delakit said:
Did you read my post? lol.
Click to expand...
Click to collapse
Sorry, we must've posted at the same time. I tried to flash cm10.1 while s-on and was stuck on "quietly brilliant".
I am going to go through your post and try your suggestions.
striketrue said:
Sorry, we must've posted at the same time. I tried to flash cm10.1 while s-on and was stuck on "quietly brilliant".
I am going to go through your post and try your suggestions.
Click to expand...
Click to collapse
Then you should be able to flash the boot.img using
fastboot flash boot boot.img
and your phone will boot.
WIN. That did it. Message me your paypal email and i'll send your bounty. Now That I'm booted, can you give me the easiest way to achieve s-off to avoid another disaster?
thicklizard, thank you for your help as well.
striketrue said:
WIN. That did it. Message me your paypal email and i'll send your bounty. Now That I'm booted, can you give me the easiest way to achieve s-off to avoid another disaster?
thicklizard, thank you for your help as well.
Click to expand...
Click to collapse
Depends on your firmware. Are you on the full 3.16 which is the latest?
I believe I was completely up to date before this process. Also, my touchscreen does not work. Any ideas?
striketrue said:
I believe I was completely up to date before this process. Also, my touchscreen does not work. Any ideas?
Click to expand...
Click to collapse
Check your PM's.

[Q] How do I flash cutom roms?

I have rooted the rezound, installed twrp recovery, but now i want to flash this ROM:
http://forum.xda-developers.com/showthread.php?t=2113140
I have this ROM along with the gapps on my SDcard and attempted to flash it. I have done the factory wipe as well as both dalvik and cache wipes to install and proceeded. The ROM and gapps have successfully been installed and i proceeded with the system reboot. The phone boots but stays on the HTC splash screen. I can still access my recovery. What should i do? Thanks.
WoodenDiamond71 said:
I have rooted the rezound, installed twrp recovery, but now i want to flash this ROM:
http://forum.xda-developers.com/showthread.php?t=2113140
I have this ROM along with the gapps on my SDcard and attempted to flash it. I have done the factory wipe as well as both dalvik and cache wipes to install and proceeded. The ROM and gapps have successfully been installed and i proceeded with the system reboot. The phone boots but stays on the HTC splash screen. I can still access my recovery. What should i do? Thanks.
Click to expand...
Click to collapse
Are you s-off or s-on? If you're s-on you need to manually flash the boot.img if you dont know what that is. I can explain later. But if you're s-on you need to manually flash the boot.img. On your computer take the zip. Extract it with any zip. It will give a folder. In the folder there will be a boot.img, take this out. Place it in your adb and fastboot folder. Then boot the phone into fastboot
fastboot flash boot boot.img
Try this first if not we can continue with another plan
Sent from my HTC One M8 running Liquid Smooth Nightlies. S-OFF.
pball52998 said:
Are you s-off or s-on? If you're s-on you need to manually flash the boot.img if you dont know what that is. I can explain later. But if you're s-on you need to manually flash the boot.img. On your computer take the zip. Extract it with any zip. It will give a folder. In the folder there will be a boot.img, take this out. Place it in your adb and fastboot folder. Then boot the phone into fastboot
fastboot flash boot boot.img
Try this first if not we can continue with another plan
Sent from my HTC One M8 running Liquid Smooth Nightlies. S-OFF.
Click to expand...
Click to collapse
I am currently S-ON and i do no know how to install the boot.img. May you give me step by step directions on how to do so? I would greatly appreciate it.
WoodenDiamond71 said:
I am currently S-ON and i do no know how to install the boot.img. May you give me step by step directions on how to do so? I would greatly appreciate it.
Click to expand...
Click to collapse
Sorry I'm replying a little late.. And yes!
1. Take the original zip extract it. Open the folder that it makes, there should be some items in it. One being "boot.img".
2. Take the boot.img and move it to your adb and fastboot folder.
3. From there, put your phone in fastboot (volume down + power, then first option)
4. Make sure phone is picked up
fastboot devices
If your device is picked up, you're good to flash the boot.img
fastboot flash boot boot.img
It'll send the boot.img. write it, all that fun stuff.
fastboot reboot
Be patient as the first boot can take up to 20 minutes. Report back or if I need to reword anything I will.
Sent from my HTC One M8 running Paranoid Android 4.4.4. S-OFF.
Edit: after getting your phone to boot. I would suggest running rumrunner. It will get you S-off. http://rumrunner.us/ go through here. Use the universal .0.5.0 if you have any questions, there is a thread in general about rumrunner working for the rezound. If any other questions. Feel free to ask here or PM me.
@pball52998
I recommend at minimum 3 s-on flashes to get acquainted with fastboot and ph98img flashing. It helps reduce end user error when flashing roms.
Snuzzo said:
@pball52998
I recommend at minimum 3 s-on flashes to get acquainted with fastboot and ph98img flashing. It helps reduce end user error when flashing roms.
Click to expand...
Click to collapse
Good point... Always forget about that for newer users...
Sent from my HTC One M8 running Paranoid Android 4.4.4. S-OFF.
pball52998 said:
Good point... Always forget about that for newer users...
Sent from my HTC One M8 running Paranoid Android 4.4.4. S-OFF.
Click to expand...
Click to collapse
Thanks so much for your help! I finally have the phone booted up and ready to use. One issue though, i cannot access the about phone part in the settings. The settings app tends to crash every time i try to select it. Other than that everything works! Thank you so much.

HELP! Soft Bricked HTC One S!

I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
geek-x said:
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
Click to expand...
Click to collapse
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
geek-x said:
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
Click to expand...
Click to collapse
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
es0tericcha0s said:
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
Click to expand...
Click to collapse
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
geek-x said:
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
Click to expand...
Click to collapse
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
es0tericcha0s said:
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
Click to expand...
Click to collapse
I tried flashing the firmware.zip file from the thread but I got a FAILED: (remote: not allowed) error in command prompt at the end of the process, what did I do wrong?
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
UPDATE:
Thank you so much es0tericcha0s, I really appreciate the support, I got the /data mount issue fixed finally. I just had to flash an older twrp recovery image and then reflashed the new one in fastboot and I could then flash CM successfully.
I can't believe I finally unbricked this phone, its been bricked since Sunday. Once again, es0tericcha0s, Thank you!
geek-x said:
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
Click to expand...
Click to collapse
You might need to RUU back then. If you have issues with the RUU exe, then you can extract the rom.zip and install it like you did the firmware. There are quite a few tutorials on how to extract it, or there might already be a version floating around for your phone.

Categories

Resources