TWRP 2.7.0.0 doesnt start after flashing - HTC One S

Hi guys,
I have searched long time to find a solution for my problem...no chance.
At the moment i'm on a jellybean rom(viper) and have s-off and hboot 2.15.
I tried to flash a kitkat and lollipop compatible recovery with fastboot. Cmd writes that the recovery was successfully installed but after trying to start recovery i only get a blackscreen and after three seconds a reboot into the rom. Every recovery before 2.7.0.0 works fine. Same problem with CWM.
I hope that someone can help me.

cryingfreeman86 said:
Hi guys,
I have searched long time to find a solution for my problem...no chance.
At the moment i'm on a jellybean rom(viper) and have s-off and hboot 2.15.
I tried to flash a kitkat and lollipop compatible recovery with fastboot. Cmd writes that the recovery was successfully installed but after trying to start recovery i only get a blackscreen and after three seconds a reboot into the rom. Every recovery before 2.7.0.0 works fine. Same problem with CWM.
I hope that someone can help me.
Click to expand...
Click to collapse
While in recovery (the one that's working for you), mount sdcard and delete the .twrps file from TWRP folder on your sdcard. Then reboot to fasboot and flash again the latest official TWRP. Reboot to recovery and see if it's solved
Sent from nowhere over the air...

I have done that but it doesn't work. Still don't boot. I've tried it several times. Any other solution?

cryingfreeman86 said:
I have done that but it doesn't work. Still don't boot. I've tried it several times. Any other solution?
Click to expand...
Click to collapse
That's strange.... Try to delete the whole TWRP folder in this case, see if it helps
Sent from nowhere over the air...

Finally i have solved the problem by flashing an unbranded original 2.15 hboot. I have found the solution in another thread. Thank you for your help.

Related

[Q] Soft-Bricked - usual solutions don't work

Sorry, for bothering you with this but unfortunately, I have soft-bricked my phone. It's a WIND Canada HTC One S with S4 cpu, CID is GLOBA001 with HBOOT 1.14.0004.
I had Cyanogenmod 10 installed, ran in some problems, tried to find a solution (among others this: http://forum.xda-developers.com/showthread.php?t=1630459 didn't work) and bricked it: boot loop, unmountable /sdcard, no working recovery. I have tried for hours all the tips I found in the forums but none helped. I even downloaded a RUU but I couldn't install it (probably the wrong version).
Current state is: I can only get into the bootloader which is re-locked (by courtesy of one of my repair attempts). Connecting via USB to fastboot works. Nothing else, for all purposes the phone is clean, empty and oh so very much dead.
How do I proceed from here? In the end I want to have working version of Cyanogenmod back.
Thank you in advance, guys!
el_Harmakhis said:
Sorry, for bothering you with this but unfortunately, I have soft-bricked my phone. It's a WIND Canada HTC One S with S4 cpu, CID is GLOBA001 with HBOOT 1.14.0004.
I had Cyanogenmod 10 installed, ran in some problems, tried to find a solution (among others this: http://forum.xda-developers.com/showthread.php?t=1630459 didn't work) and bricked it: boot loop, unmountable /sdcard, no working recovery. I have tried for hours all the tips I found in the forums but none helped. I even downloaded a RUU but I couldn't install it (probably the wrong version).
Current state is: I can only get into the bootloader which is re-locked (by courtesy of one of my repair attempts). Connecting via USB to fastboot works. Nothing else, for all purposes the phone is clean, empty and oh so very much dead.
How do I proceed from here? In the end I want to have working version of Cyanogenmod back.
Thank you in advance, guys!
Click to expand...
Click to collapse
Unlock it first, you can't do anything with it locked.
Darknites said:
Unlock it first, you can't do anything with it locked.
Click to expand...
Click to collapse
Okay, the device is unlocked again. How do I continue?
Thanks a lot, by the way!
el_Harmakhis said:
Okay, the device is unlocked again. How do I continue?
Thanks a lot, by the way!
Click to expand...
Click to collapse
Flash TWRP recovery and try to mount the sd and connect it to the pc.
Darknites said:
Flash TWRP recovery and try to mount the sd and connect it to the pc.
Click to expand...
Click to collapse
Okay, flashing TWRP worked. I then booted into recovery, clicked on "mount" and then "mount usb device". After some driver installs I can no see the internal storage. Apart from a folder for TWRP and .android_secure it's empty. Is this where I now put the Cyanogenmod file and install it via the recovery?
el_Harmakhis said:
Okay, flashing TWRP worked. I then booted into recovery, clicked on "mount" and then "mount usb device". After some driver installs I can no see the internal storage. Apart from a folder for TWRP and .android_secure it's empty. Is this where I now put the Cyanogenmod file and install it via the recovery?
Click to expand...
Click to collapse
Ya place it where you want and then flash it but you will need to fastboot the boot.img file thats in the rom zip, you can use the All-In-One Toolkit to do that.
Darknites said:
Ya place it where you want and then flash it but you will need to fastboot the boot.img file thats in the rom zip, you can use the All-In-One Toolkit to do that.
Click to expand...
Click to collapse
Copying the ROM and then installing via TWRP worked though I saw that TWRP displayed an error, saying it was unable to mount /cache. When I tried to wipe the Cache & Dalvik Cache I got the same error.
Nevertheless I then went ahead and copyed the boot.img (extracted that one from the Cyanogenmod zip) via fastboot and rebooted the device. Now the phone is stuck in the Cyanogenmod boot loop.
el_Harmakhis said:
Copying the ROM and then installing via TWRP worked though I saw that TWRP displayed an error, saying it was unable to mount /cache. When I tried to wipe the Cache & Dalvik Cache I got the same error.
Nevertheless I then went ahead and copyed the boot.img (extracted that one from the Cyanogenmod zip) via fastboot and rebooted the device. Now the phone is stuck in the Cyanogenmod boot loop.
Click to expand...
Click to collapse
Hmm think you going to have flash the stock recovery then do a factory reset in the bootloader then go back to TWRP and copy over the rom again then factory reset in TWRP and then wipe system and then flash the rom. Do not lock the bootloader.
Darknites said:
Hmm think you going to have flash the stock recovery then do a factory reset in the bootloader then go back to TWRP and copy over the rom again then factory reset in TWRP and then wipe system and then flash the rom. Do not lock the bootloader.
Click to expand...
Click to collapse
Okay, I will try that! Where might I get the stock recovery? I don't want to pick the wrong!
el_Harmakhis said:
Okay, I will try that! Where might I get the stock recovery? I don't want to pick the wrong!
Click to expand...
Click to collapse
Go here for it.
Darknites said:
Go here for it.
Click to expand...
Click to collapse
Ha! It finally worked! Thank you very much! Have a nice weekend!
el_Harmakhis said:
Ha! It finally worked! Thank you very much! Have a nice weekend!
Click to expand...
Click to collapse
Np dude, you too.

fastboot flash rom

can i fastboot flash a rom or other zip? i've run into a problem after flashing a rom that wont boot and twrp wont mount data or my internal storage so i cant flash anything else. any help would be appretiated
I dont know how to do it, but have heard you can use the sideload feature of the twrp recovery to flash a rom. Or you could try flashing the new twrp recovery if your not on the new one. The new twrp 2.8.0.3 recovery was released on 9-30-14 last I checked its not updated on xda yet but you can get it on the twrp recovery web site which its on the link below, its the newest one on the bottom of the list.
http://techerrata.com/browse/twrp2/m8_wlv
reaper420 said:
can i fastboot flash a rom or other zip? i've run into a problem after flashing a rom that wont boot and twrp wont mount data or my internal storage so i cant flash anything else. any help would be appretiated
Click to expand...
Click to collapse
worse case scenario, run the RUU, fastboot flash recovery recovery.img then install ROM in recovery.
Honestly, you might as well apply the whole RUU and get yourself back to a working stock before putting another custom ROM back on. Follow the OP in this thread: http://forum.xda-developers.com/showthread.php?t=2873144
I tried every method possible and none worked, I recently cracked my screen so I just took this as a sign and went ahead and got it replaced with insurance. Thanks for all the suggestions
did your recovery constantly reboot into a white htc screen ?
jxcorex28 said:
did your recovery constantly reboot into a white htc screen ?
Click to expand...
Click to collapse
Are you using the correct Vzw version of twrp or cwm?

[Q] TWRP flash says successful... but stock recovery is still there?

Hey Guys. Im running cm12s on my oneplus one, and i would like to switch to oxygenOS because they are getting the touchscreen firmware fixes. Ive flashed recoveries onto multiple phones without this issue before.
I downloaded twrp, booted the phone into fastboot, unlocked it, got the success signal, flashed it, again, success, and then rebooted. Then i powered down and booted to recovery aaaand..... stock recovery. WTF? So i wipe all user data and clear the cache with the stock recovery and try again. Nope. Its still the stock recovery. i dont understand it. I tried with CWM aswell. It says success, so why did it not work? I booted into the OS and checked developer settings, and disabled update recovery and all that, Nevertheless, when i flash TWRP or CWM, it does not work. I dont understand how this could happen.
I followed the steps from the Official guide on the official oneplus forum, It wont let me post a link.
I am using an OEM samsung cable.
Can anyone help me?
fastboot reboot-bootloader ; just after recovery flash.
Orphee said:
fastboot reboot-bootloader ; just after recovery flash.
Click to expand...
Click to collapse
Alright, I've just tried that. After flashing it, i Ran this command and as expected it rebooted back to the bootloader. Nothing else todo there, so i rebooted and booted to the recovery. It STILL boots to the stock recovery! So i tried again, but this time, i flashed it a second time after rebooting to the bootloader, but that still has not worked. is my unit defective? I will try now with another computer.
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon
I figured it out!
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
theangrynoob5 said:
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
Click to expand...
Click to collapse
CM didn't just do that to you, it's happened to every single person who's tried to flash TWRP after taking the Lollipop update, that's why the question is included in the FAQ thread.
XDA Moderator
Transmitted via Bacon

[Q&A] [RECOVERY][TF300T] TWRP 2.8.7.0 touch recovery [2015-06-23]

Q&A for [RECOVERY][TF300T] TWRP 2.8.7.0 touch recovery [2015-06-23]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][TF300T] TWRP 2.8.7.0 touch recovery [2015-06-23]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Does TWRP 2.8 (latest version 2.8.7.0) okay to start out with? Meaning, if we are at the latest version of stock (ASUS build JOP40D.US_epad-10.6.1.27-5-20130902; Android 4.2.1) and we are going to flash a custom rom for the first time, the latest versions of TWRP won't brick our devices?
It could be that I'm just confused because there were lots of older versions that reference individual Android builds (JB vs ICS). And people would say "if you have X version of Android, use Y version of TWRP or you're gonna brick it".
Can't enter twrp but everything ok
Today i flashed 2.8.7.0 img with twrp 2.8.5.0 and than reboot tablet. Than i tried enter the recovery but tablet booting normally.
In bootloader screen click RCK but say "unrecoverable bootloader error 0x00000000
Tried
Flash twrp with adb
Flash twrp with terminal
But not working. Tablet starting normally when i tried enter the recovery.
Tablet working normally. Please help me.
I am using katkiss 5.1.1
Edit: i solved problem with this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
I got sent here, so I'll try again.
I'm a little confused now, because I can't understand what is happening to my tablet. Let me explain step by step what I did, maybe one of you can figure out what is wrong.
I was running CM11 M12 with TWRP 2.8.1.0 and wanted to try the new Android 5.1. I decided to go with the latest Omnirom and found out I needed at least TWRP 2.8.5.0.
So first step would be to update TWRP. When I got at the TWRP website I read that there was something new in TWRP 2.8.4.0, so I decided to first go from .1 to .4 and then go to the latest .7. An upgrade to .4 went fine through Fastboot. Then I thought I could try the new in GUI recovery flasher, but I didn't understand it properly so I chose to go safe and flash the .7 through Fastboot.
I guess that's where I went wrong. The tablet went to recovery just fine, but in TWRP it couldn't access anything anymore. "Unable to mount" on everything. Internal storage was 0. It didn't boot to the ROM anymore.
So after some tinkering, not really sure what I did anymore, I got my access to the FS again. I had the CM11 M12 ROM still in the MicroSD, so I ran the "install ROM procedure" for that one and it booted again.
Only now I don't seem to have a recovery anymore. I can get into Fastboot, but when I send the "fastboot -i 0x0b05 flash staging twrp.blob" the tablet hangs itself. Holding power revives it and it boots to CM11M12 again. I tried to flash different TWRP versions (.4 .5 .6 and .7) but no sigar.
Does anyone have an idea how to get my recovery back?
Edit0: I tried to install the TWRP manager from the store and get a recovery from there, but the app doesn't work. It hangs when I try to tap on the "Recovery version to install" option.
Edit1: I followed the link in the post above and solved it. Next thing I did was flashing the .6 TWRP recovery and it stuck. Time to wrestle with some new roms! Thanks!
Edit2: Back to square one. The TWRP can't see anything in my internal storage. Is my storage memory going dry? "Unable to mount ###" shows up for every partition.
Edit3: And now it can see in my internal memory again... Hardware failure?
2.8.7.0 on tf300t reboot/shutdown does not work
hi, thanks for all your effort!
i just used fastboot to load 2.8.7.0 on a stock tf300t. it seems to work fine with one exception, when I choose reboot system or shutdown, but result in me booting back to twrp immediately. the only way i can shutdow/reboot is to hold the power key for 10s, then press it again to boot
everything else seems to work ok (flashing etc)....
any ideas whats going on?
thanks again
tguadagno said:
hi, thanks for all your effort!
i just used fastboot to load 2.8.7.0 on a stock tf300t. it seems to work fine with one exception, when I choose reboot system or shutdown, but result in me booting back to twrp immediately. the only way i can shutdow/reboot is to hold the power key for 10s, then press it again to boot
everything else seems to work ok (flashing etc)....
any ideas whats going on?
thanks again
Click to expand...
Click to collapse
for me it's the same..
thanks in advance
edy
aoesp3 said:
Today i flashed 2.8.7.0 img with twrp 2.8.5.0 and than reboot tablet. Than i tried enter the recovery but tablet booting normally.
In bootloader screen click RCK but say "unrecoverable bootloader error 0x00000000
Tried
Flash twrp with adb
Flash twrp with terminal
But not working. Tablet starting normally when i tried enter the recovery.
Tablet working normally. Please help me.
I am using katkiss 5.1.1
Edit: i solved problem with this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Click to expand...
Click to collapse
Same problem! hope this works. I bought mine in US so I downloaded V10.6.1.27.5 Only for US SKU (Android 4.2).
After this is it ok to flash the latest TWRP again?
anjeu67 said:
Same problem! hope this works. I bought mine in US so I downloaded V10.6.1.27.5 Only for US SKU (Android 4.2).
After this is it ok to flash the latest TWRP again?
Click to expand...
Click to collapse
Nope. I am using lastest TWRP(2.8.7.0) now.
Hello
Can someone help me please?
For the moment i have TWRP 2.8.0.1 and i want to update it to 2.8.7.0.
First of all, i tried to update it with twrp manager.
So i open twrp manger
The install recovery screen opens and i choose for "Install Recovery".
Then i'm redirected to jmz software and then i got next screen:
Forbidden - you don't have permission to access /tf300t/ on this server.
What i'm i doing wrong?
tguadagno said:
hi, thanks for all your effort!
i just used fastboot to load 2.8.7.0 on a stock tf300t. it seems to work fine with one exception, when I choose reboot system or shutdown, but result in me booting back to twrp immediately. the only way i can shutdow/reboot is to hold the power key for 10s, then press it again to boot
everything else seems to work ok (flashing etc)....
any ideas whats going on?
thanks again
Click to expand...
Click to collapse
Same here... what gives?
Same here also.
ecb116 said:
Same here... what gives?
Click to expand...
Click to collapse
Same problem here,, no answers?

[HELP] Stuck on Recovery Bootloop after OTA Update (CM14.1) , can't access Fastboot

Hi,
Just for you to know:
Model: r7plusf
Recovery: TWRP 3.0.2-0
----------------------------------------
So earlier today I did an OTA update (cm-14.1-20161205-NIGHTLY-r7plus.zip), but couldn't get my phone to boot.
So naturally, I tried wiping Cache and ART cache, but was still bootlooping.
Thought there might be someting wrong with my ROM and data, so I formated data and Installed ROM and GAPPS again after ADB pushing them onto my phone.
Now, and although CM14.1 and GAPPS are successfully installed on my Oppo R7 Plus, I can't boot into the OS. Every time I try reboot system, whether through POWER_BUTTON, RECOVERY or ADB, I just boot into Recovery.
Worst of all, for some unknown reason, I can't get into BOOTLOADER, neither through button combination, nor through Recovery nor ADB.
I found this article (http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386) in the LG G3 thread about executing some shell commands, but I haven't tested testing it with my phone's variables because it might hard brick it...
Please Help!
[EDIT] I now have access to fastboot but still recovery looping like crazy.
I installed the same update via CyanDelta , worked like a charm ! hopefully you get back up and running.
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Same thing happened to me! Where did you get a copy of the stock recovery? Link?
resverse said:
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Click to expand...
Click to collapse
I had the same problem. Can't remember exactly how I resolved it. But I think, I use CM recovery to flash nightly. Then flash TWRP to flash gapps. For some strange reason, using CM recovery also show no enough disk space whenever I try to flash opengapps. But TWRP recovery can flash opengapps successfully.
Don't use the OTA, use adb sideload to flash the nightly next time. So far, adb sideload has not given me any issue to flash nightly.
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
corbalan12 said:
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
Click to expand...
Click to collapse
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
resverse said:
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
Click to expand...
Click to collapse
Thank you very much!!!! I'll try tomorrow and tell you.
I appreciate a lot!
First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.

Categories

Resources