I downloaded some twrp backups and I tried to flash twrp using flashify but I keep getting bootlooped. Idk why it's doing this but in order to get S-OFF I need to get back to stock and the back up is my only chance. My phone bootloops when I've flashed twrp using flashify and I reboot into recovery. Any thoughts on maybe why twrp is making my phone bootloop? Is anyone else having these problems?
That's happened to me a few times as well. What worked for me was to flash twrp through adb or fastboot. You may have to try some older versions of twrp if the current release doesn't work. If I'm remembering correctly I think 2.7.0.1 and 2.8.3.0 worked for me. I believe it depends on what version of android you're currently running. Look here http://teamw.in/project/twrp2/225
To add a bit to what was mentioned above, do fastboot erase cache, and flash TWRP using fastboot.
This solves most issues with TWRP not flashing or booting properly.
Also, make sure you bootloader is UNLOCKED.
iTzz_KAMIKAZE said:
Idk why it's doing this but in order to get S-OFF I need to get back to stock and the back up is my only chance.
Click to expand...
Click to collapse
No, it isn't. You can also relock the bootloader and RUU back to stock.
redpoint73 said:
To add a bit to what was mentioned above, do fastboot erase cache, and flash TWRP using fastboot.
This solves most issues with TWRP not flashing or booting properly.
Also, make sure you bootloader is UNLOCKED.
No, it isn't. You can also relock the bootloader and RUU back to stock.
Click to expand...
Click to collapse
So I just tried to flash the recovery using fastboot with no luck. I followed the directions off of TWRP's thread and even tried it a second time running the "fastboot erase cache" first, still with no luck. Now you mentioned me relocking my bootloader and then RUU back to stock, is there a thread I can go to to try that?
iTzz_KAMIKAZE said:
So I just tried to flash the recovery using fastboot with no luck. I followed the directions off of TWRP's thread and even tried it a second time running the "fastboot erase cache" first, still with no luck. Now you mentioned me relocking my bootloader and then RUU back to stock, is there a thread I can go to to try that?
Click to expand...
Click to collapse
Try a couple older TWRP builds, to see if that helps (as recommended in previous post by johnnyutah22).
You can try RUU, you don't need a thread for that. Relocking the bootloader is a single command:
fastboot oem lock
After that, just run the RUU, its a Windows executable, and very self explanatory. You can find the RUUs linked in my Index thread:
http://forum.xda-developers.com/showthread.php?t=2751432
Related
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
the phone keeps bootlooping to HTC screen. I can get into bootloader but it will not boot into recovery. I have unlocked bootloader via HTC DEV, flashed twrp recovery via fastboot, attempted to flash boot.img via flashboot, etc. tried to relock and run and RUU but that didn't work either.
Any ideas? bricked?
current status:
S-On (because I can't get to a point to get device recognized by adb for moonshine and Dev-Host is down so I can't download the files for facepalm)
Hboot 2.09
Radio: 1.12.11.1210
openDSP-V31.1.0.45.0815
October 18 2012, 15:46:20
What happens when you try to boot to recovery from the bootloader? As far as using a RUU, you're on the latest OTA, so there isn't a RUU for you to use except VipeRUU, but it requires S-off. Furthermore, you'll have to use Moonshine, not Facepalm, to gain S-off once you get your phone up & running.
when I try to boot into recovery from the bootloader it never gets past the htc screen and simply goes straight into a bootloop again.
Can you connect your phone to a PC in fastboot USB mode? It sounds like you need to try and wipe your recovery via fastboot commands, then reinstall recovery. Then follow the instructions in my guide below:
http://forum.xda-developers.com/showthread.php?t=2443108
I recommend using MeanBean ROM. It's S-on friendly-just follow the directions in the ROM thread to get it flashed properly.
yes I can connect via fastboot usb. I have already wiped and flashed both TWRP and clockworkmod recoveries several times in an attempt to get it to load into recovery to be able to flash a rom. No joy on any attempt.
spartansbleedgreen said:
yes I can connect via fastboot usb. I have already wiped and flashed both TWRP and clockworkmod recoveries several times in an attempt to get it to load into recovery to be able to flash a rom. No joy on any attempt.
Click to expand...
Click to collapse
Stay away from ClockWorkMod recovery-it doesn't play well on the EVO LTE and isn't supported. It sounds like your recovery partition may have gotten borked. There is a file around here somewhere that will restore it but I can't recall where it is.
couldn't find anything under the search terms "rebult recovery" and "recovery partition"
any ideas on how to find it?
still haven't found any solution
Try doing a full wipe, then flash the ROM
Sent from my HTC HD2 using xda app-developers app
PM Zarboz about JTAG. That might be your last resort.
EDIT: Actually, I have an idea. What ROM were you on? Have you tried this?
You'll need the firmware zip from the 3.16 update, which I will upload shortly.
UPDATE: 3.16.651.3 Firmware (thanks to xHausx)
You should be able to push this through fastboot and flash. It *should* normalize your partitions and get the stock recovery back. If that works, you should then be able to flash TWRP and get going again.
Thanks
Captain_Throwback said:
PM Zarboz about JTAG. That might be your last resort.
EDIT: Actually, I have an idea. What ROM were you on? Have you tried this?
You'll need the firmware zip from the 3.16 update, which I will upload shortly.
UPDATE: 3.16.651.3 Firmware (thanks to xHausx)
You should be able to push this through fastboot and flash. It *should* normalize your partitions and get the stock recovery back. If that works, you should then be able to flash TWRP and get going again.
Click to expand...
Click to collapse
just got me out of the facepalm death trap. :good:
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.
I was trying to ruu'ing and my sd card would not mount through the android recovery. So i wiped Dev/cache, cache, and system, thinking that it would fix the problem. Now i can not get into recovery mode and factory reset doesn't work and my phone is not being recognized by my PC. Anything i press in bootloader just reboots my device back to bootloader. I also locked my bootloader with the command "fastboot eom lock" i was experimenting and now i can not unlock it it say "relocked". What do i have to do to fix this?
Slax. said:
I was trying to ruu'ing and my sd card would not mount through the android recovery. So i wiped Dev/cache, cache, and system, thinking that it would fix the problem. Now i can not get into recovery mode and factory reset doesn't work and my phone is not being recognized by my PC. Anything i press in bootloader just reboots my device back to bootloader. I also locked my bootloader with the command "fastboot eom lock" i was experimenting and now i can not unlock it it say "relocked". What do i have to do to fix this?
Click to expand...
Click to collapse
If you place a Sense ROM PH98IMG on an external microSD card, does it install? Try that.
I cant seem to find an PH98IMG that will work. At this point do i have to flash boot or install an OTA (3.14.605.12)
I can not flash anything from the recovery. I also can not find an PH98IMG that would work at this point. the only think that im able to do is to get into bootloader which is relocked and i have s-on.
Do i need to unlock my bootloader to get into recovery?
How do i reinstall the whole system file?
Slax. said:
I can not flash anything from the recovery. I also can not find an PH98IMG that would work at this point. the only think that im able to do is to get into bootloader which is relocked and i have s-on.
Do i need to unlock my bootloader to get into recovery?
How do i reinstall the whole system file?
Click to expand...
Click to collapse
What is your current firmware/radio version from the bootloader screen?
My current radio version is 2.23.10.0123r
HBOOT is 2.28.0000
OpenDSP is v14.6.0.7708.00.0507
Slax. said:
My current radio version is 2.23.10.0123r
HBOOT is 2.28.0000
OpenDSP is v14.6.0.7708.00.0507
Click to expand...
Click to collapse
You are on current OTA firmware, and you said you were S-On so you can't RUU, there isn't one available and you can't go down a version.
You need to unlock your boot loader, get a ROM zip (any stable ROM will do, but I suggest Tachyon or Infection), download TWRP/CWM/PhilZ recovery, and you will need working adb/fastboot on a Win7/XP machine (Win 8/8.1 will not work).
Extract boot.IMG from ROM and recovery.IMG (name might vary) from recovery zip and place them in the directory with fastboot. Now start phone and fastboot and boot recovery with 'fastboot boot recovery.img', now in recovery wipe/format everything except external microSD, then Install/flash ROM zip. Reboot.
If you follow these instructions it should just boot now.
If you want stock, there is a ROM zip that the complete stock image with root applied in the development forum, its a page or two back though.
Sent from my Nexus 4 using Tapatalk
What are the TWRP/CWM/PhilZ recovery for?
Custom recovery, you need one, not all three... To wipe/format partitions and install custom zips
Sent from my Nexus 4 using Tapatalk
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.