Hi all,
I was having some issues sideloading a ROM in TWRP 2.6.3.4, but eventually was able to adb push the ROM in (ViperOne 5.0.0). After that, I got an install failed (which is bad in and of itself, as I have no OS installed currently) and told me to try installing TWRP 2.6.3.3, which I did from it's Aroma menu, and now my phone will not enter into recovery at all! I've tried 2.6.3.4, 2.6.3.3, and now just tried 2.6.3.0.
Any help at all would be extremely appreciated, I may have broken my phone here, and am really worried.
Thanks in advance.
EDIT: I can get 2.6.3.4 working and running, but anything under 2.6.3.4 will not work anymore, even though I just had 2.6.3.0 working on there.
If you can boot to TWRP, either use adb push or adb sideload
fastboot erase cache
BlackHayze said:
EDIT: I can get 2.6.3.4 working and running, but anything under 2.6.3.4 will not work anymore, even though I just had 2.6.3.0 working on there.
Click to expand...
Click to collapse
Make sure you're using the right recovery for you phone; I didnt know ViperOne had recoveries in installer, but I think ViperOne is compatible with GSM and CDMA phones, if that is true, then 2.6.3.3 and .4 are for GSM and 2.6.3.0 is probably for CDMA (Sprint)
I would also recommend flashing recovery yourself using fastboot:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
making sure you get the correct TWRP for you phone model.
nkk71 said:
Make sure you're using the right recovery for you phone; I didnt know ViperOne had recoveries in installer, but I think ViperOne is compatible with GSM and CDMA phones, if that is true, then 2.6.3.3 and .4 are for GSM and 2.6.3.0 is probably for CDMA (Sprint)
I would also recommend flashing recovery yourself using fastboot:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
making sure you get the correct TWRP for you phone model.
Click to expand...
Click to collapse
Yeah I had found a 2.6.3.4 for Sprint that I flashed manually before, and that worked fine as far as starting the recovery up and everything. But, it couldn't install ViperOne correctly, and so ViperOne has an option in the Aroma installer to install a recovery, and since I had never found a 2.6.3.3 file to manually flash, but was on 2.6.3.4 I never even thought that it may not be a recovery built for my phone and it messed everything up.
That's the last time I'm gonna let anything install stuff for me, I always prefer the manual way. I suggest the auto flashers and installers to people like my mom who only really wants root for a certain few features, but I'm usually a manual guy.
Luckily, the RUU worked and I was able to get ViperOne installed on 2.6.3.0.... Sad thing is that's the same recovery I was running before this entire fiasco haha. What a night for me.
I keep getting a No OS installed error on twrp. Yesterday I install a 5.03.651.3 rooted rom through TWRP. I think I deleted the wrong files so I installed a stock 4.06.651.4 from a ruu then I did a ota update to 4.06.651.9. After that I unlocked the bootloader and installed TWRP 2.7.1.1. I have done noting more after that. Can someone please help me fix this problem?
Thanks
TWRP 2.6.3.4
http://forum.xda-developers.com/showthread.php?t=2791126
from HTC One
When I installed TWRP 2.6.3.4 the error stopped showing up. Does that mean that there is a problem with TWRP 2.7.1.1 and my phone is fine?
og style said:
When I installed TWRP 2.6.3.4 the error stopped showing up. Does that mean that there is a problem with TWRP 2.7.1.1 and my phone is fine?
Click to expand...
Click to collapse
yes I not believe on 2.7 version
from HTC One
Thank you for the help
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
ReproOne said:
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
Click to expand...
Click to collapse
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
Thank you for the reply. I thought about taking that approach, but I was really hoping someone would have an answer on why the procedure wasn't working now. My bootloader is still unlocked.
I found this as an approach someone did on the Nexus 4 for a similar issue:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Thoughts?
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
ReproOne said:
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
Click to expand...
Click to collapse
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Thank you for those steps. I do not have an external SD card installed, so I modified it to store the recovery.img on sdcard instead.
Now I can always fastboot flash twrp and then back to stock recovery.
Thank you again!
nfinitefx45 said:
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Click to expand...
Click to collapse
You would need root to do this. Not being able to use "fastboot boot" you would just be backing up the flashed recovery. Possibly towel root temp root, but I would assume it has been patched in newest update.
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
neudof said:
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
Click to expand...
Click to collapse
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
xPhantom said:
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
Click to expand...
Click to collapse
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
neudof said:
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
Click to expand...
Click to collapse
Yes, after the OTA, just flash TWRP back through fastboot and then re-flash SuperSU to get root back.
nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
I just applied the update released today, and I tried to save the recovery.img file before flashing TWRP. However, it kept giving me permission denied. Do you have the recovery.img file from the update released today so I can use it for the next update?
fastboot not working
please any help on how to access fastboot on HTC one m8.
its showing black screen n fastboot mode...
wot can I do 2 annul d problem
rooting problem
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
jinal shah said:
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
Click to expand...
Click to collapse
What's the output in the terminal when you fastboot flash recovery?
rooting problem
It doesn't show any error as such.
In the command window it shows successful.
But when I click on recovery it reboots back to fast boot.
Like for a second it shows the screen which reads 'this build is only for developers'
But then instead of opening Twrp it reboots back to fast boot.
I was having so many issues with my phone that I tried to update but was unable . So i tried to root it and install CM12 as it had lolipop. That failed miserably and now I am stuck with twrp v2.6.3 and no os, no backup, and no RUU. What can i do?
Dcolewizard said:
I was having so many issues with my phone that I tried to update but was unable . So i tried to root it and install CM12 as it had lolipop. That failed miserably and now I am stuck with twrp v2.6.3 and no os, no backup, and no RUU. What can i do?
Click to expand...
Click to collapse
you can't flash CM12 with twrp 2.6.3.3. Everything explained in the CM forum. Update your recovery.
alray said:
you can't flash CM12 with twrp 2.6.3.3. Everything explained in the CM forum. Update your recovery.
Click to expand...
Click to collapse
I had to use HTC all in one-toolkit to update twrp to 2.7.1.1 and it worked Thank!
I'am Already Unlocked Device and How to Export Stock Recovery On HTC One M7 Android 5.0.2 Sense 6 ?
Thank You.
sopont said:
I'am Already Unlocked Device and How to Export Stock Recovery On HTC One M7 Android 5.0.2 Sense 6 ?
Thank You.
Click to expand...
Click to collapse
If you mean how to backup the stock recovery actually installed on your phone, you can't unless you have s-off and its not an easy task. You need to downgrade hboot to 1.44 so you can boot a custom recovery without flashing it (fastboot boot recovery.img) so you can pull the stock recovery from the mmcblk0p34 partition using "dd" commands using an adb shell from the booted custom recovery.
Easiest solution is to extract the stock recovery from the ota update zip file of the same version your phone is actually running.
Maybe your stock recovery version is already available, what version do you need?
alray said:
If you mean how to backup the stock recovery actually installed on your phone, you can't unless you have s-off and its not an easy task. You need to downgrade hboot to 1.44 so you can boot a custom recovery without flashing it (fastboot boot recovery.img) so you can pull the stock recovery from the mmcblk0p34 partition using "dd" commands using an adb shell from the booted custom recovery.
Easiest solution is to extract the stock recovery from the ota update zip file of the same version your phone is actually running.
Maybe your stock recovery version is already available, what version do you need?
Click to expand...
Click to collapse
Hi alray.
Thank you very much.