Okay so I had twrp installed and could not do the ota for 4.3. Ended up taking 3 days total to get unlocked, s-off, and stock ruu(I work 58+ hrs a week.) so I saw something about fastboot boot "recovery.img" have not been able to execute this properly when I do phone freezes on fastboot then boots to stock recovery when I reset it with an exclamation mark. I'm trying to temp boot into custom recovery and push su.zip any ideas? Thanks.
Sent from my HTCONE using XDA Premium HD app
Related
I was running ARHD 10.1 and flashed TeamSeven's kernel in Clockwork Recovery. Went to reboot and the phone just boot loops, no big deal right. So when I put the phone back into bootloader screen and tried to boot into recovery it boots for about .50 seconds into my custom recovery then boots back to the Fastboot HTC Screen. Im unable to get into my custom recovery. Ive tried using the All in one tool to flash different recoverys and have been successful in doing so, I know this because they boot for the .50 seconds into TWRP or Clockwork then goes back into the HTC Fastboot screen. Does anybody have any ideas? How can I fix this? I tried to sideload a rom but it seems it will not let me until im able to get into my custom recovery.
Have you used ADB to delete cache, Then re-flash a recovery ? Then full wipe etc and clean install a Rom ?
Sent from my HTC One using Tapatalk 2
jthornton71707 said:
I was running ARHD 10.1 and flashed TeamSeven's kernel in Clockwork Recovery. Went to reboot and the phone just boot loops, no big deal right. So when I put the phone back into bootloader screen and tried to boot into recovery it boots for about .50 seconds into my custom recovery then boots back to the Fastboot HTC Screen. Im unable to get into my custom recovery. Ive tried using the All in one tool to flash different recoverys and have been successful in doing so, I know this because they boot for the .50 seconds into TWRP or Clockwork then goes back into the HTC Fastboot screen. Does anybody have any ideas? How can I fix this? I tried to sideload a rom but it seems it will not let me until im able to get into my custom recovery.
Click to expand...
Click to collapse
type fastboot erase cache from PC while phone is in fastboot. you should be able to get into recovery afterwards. If not, flash another recovery from fastboot. fastboot flash recovery RECOVERYNAME.img
Hey guys I just rooted and flash a rom on my phone lastnight, nwo today i went to boot into recovery to show a friend and when I chose recovery from the bootloader the recovery just flashed on the screen and the phone reboot to the "this phone is for development purposes,,,,,etc" I trying reflashing the recovery using the tool kit and still nothing. Any help would be appreciated.
Edit
I just flashed the twrp and it seems to be working again and not the CWM recovery
biglo said:
Hey guys I just rooted and flash a rom on my phone lastnight, nwo today i went to boot into recovery to show a friend and when I chose recovery from the bootloader the recovery just flashed on the screen and the phone reboot to the "this phone is for development purposes,,,,,etc" I trying reflashing the recovery using the tool kit and still nothing. Any help would be appreciated.
Click to expand...
Click to collapse
Go into fastboot and command
fastboot erase cache
Then try accessing recovery again...
Edit: or if you're using the toolkit, I think that has an option to erase cache if you can't get the command to work
Sent from my HTC One using xda premium
so, i just flashed the modified firmware.zip for 3.09 with twrp recovery, and everything was a success, until i rebooted..now im stuck in a bootloop.
bootloop as in the splashscreen when you turn on the device shows, and then it restarts
i followed everything right, relocked bootloader, etc etc
im soff, i once flashed a custom hboot (without the warning text), but i dont think that should be a problem with soff..
i have super cid, so what did i do wrong? and what can i do to fix it?
i was thinking of flashing cwm and restoring a previous backup i made, but when i try flashing it, it says "not allowed', so i cant even get cwm recovery.
so basically my question is, how do i get out of this bootloop after flashing the latest firmware.zip?
Maybe you can't flash a recovery because you are relocked?
Sent from my HTC One X using xda app-developers app
Stefan0vic said:
Maybe you can't flash a recovery because you are relocked?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
twrp flashed fine..just cant get cwm to flash..so that shouldnt be the problem. regardless, how can i get out of this bootlooop
You can't flash cwm because you relocked the boot loader.
You're stuck in a bootloop because you can't have a locked boot loader and custom recovery. It will always cause a bootloop.
Unlock the boot loader and it will boot fine.
Sent from my HTC One using XDA Premium 4 mobile app
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 flashing the new OTA from adb, and it failed at 70%.
Stock image, locked bootloader, not TWRP, not rooted
Now on bootup, I see nothing but the google logo.
I can reboot to bootloader/recovery mode, but can't flash anything since I hadn't unlocked the bootloader. Any way to proceed? Can I flash another bootloader that will let me unlock from fastboot?
Bootloader can only be unlocked after allowing it in the developers options. Perhaps you can boot into TWRP from the bootloader, fastboot boot xxx. Where xxx is the name of the TWRP IMG. You may be able to side load the OTA that way and flash it. I'm not 100% sure of that though.
Larzzzz82 said:
Bootloader can only be unlocked after allowing it in the developers options. Perhaps you can boot into TWRP from the bootloader, fastboot boot xxx. Where xxx is the name of the TWRP IMG. You may be able to side load the OTA that way and flash it. I'm not 100% sure of that though.
Click to expand...
Click to collapse
How do I push TWRP to the device? I can't flash recovery (it's still stock).
You don't. If you've got fastboot working, just type, fastboot boot (the name of the TWRP IMG) and it should boot on the device.
Sent from my Nexus 6 using Tapatalk
Larzzzz82 said:
You don't. If you've got fastboot working, just type, fastboot boot (the name of the TWRP IMG) and it should boot on the device.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I was getting errors when trying to boot from the twrp image. But I figured out that I can boot to recovery, select update from adb, and get adb running again.
I was able to reflash the OTA, looks like it's working now.
I guess the lesson for today is that I should just leave the bootloader unlocked.
Thanks for the help
Excellent!
Sent from my Nexus 6 using Tapatalk
Javi_in_1080p said:
I was errors when trying to boot from the twrp image. But I figured out that I can boot to recovery, select update from adb, and get adb running again.
I was able to reflash the OTA, looks like it's working now.
I guess the lesson for today is that I should just leave the bootloader unlocked.
Thanks for the help
Click to expand...
Click to collapse
That's the 1st commandment! Leave the bootloader unlocked.
Sent from my Pixel XL using Tapatalk