I'm having a bit of trouble erasing the recovery off my Verizon HTC M8. Yes, I am Unlocked/S-OFF.
My trouble is when I reboot into fastboot I can erase/flash every partition on my phone EXCEPT the recovery...it says remote failed? I'm just trying to get a fresh install of TWRP. I can flash twrp just fine via fastboot but I was wondering if anyone else has had this problem.
I can flash my GF's G3 via fastboot erase recovery the fastboot flash twrp.img but my phone el-borko.
Any ideas?
Related
Hey I just got a tf300 for cheap and decided to put a rom on it. I got twrp installed and got root access. The version of twrp was too old and when I updated it and got into twrp I was prompted for a password. I figured something was wrong with the version of twrp I installed and I could go go back to the previous version of twrp by using fastboot but I am unable to get into fast boot.
I hold power and volume down but it boots right into twrp. I'm not able to get it to boot normally either it just boots into twrp. Has anybody run into this or have any ideas why I can't get power + volume down to bring up the recovery menu?
EDIT: Oh and adb doesn't see any devices either.
EDIT #2: It seems that my pc kind of recognizes that something is installed. It shows up on Device Manager as "Transformer" with the yellow exclamation point. I haven't been able to find any drivers that work with it. Anyone have a link?
EDIT #3: Ok I forced the universal naked drivers to install and adb devices now shows tf300 in recovery. When I put in adb reboot bootloader it comes up with the rck android and wipe data. I used fastboot to load my original twrp blob that was working fine. I get:
I:\tf300>fastboot -i 0x0b05 f
sending 'recovery' (6448 KB).
OKAY [ 1.895s]
writing 'recovery'...
OKAY [ 2.862s]
finished. total time: 4.757s
But when I go into recovery its still the version of twrp that was causing issues and it still asks for a password.
I figured i'd do a fastboot erase of boot, cache, recovery, system, userdata and then fastboot the original twrp blob but I get:
I:\tf300>fastboot erase boot
< waiting for device >
EDIT #4: It seems that adb recognizes by device but fastboot does not. Entering fastboot devices returns blank. Anyone know if this is an issue with the driver?
Anyone?
Ok after a couple of hours of hair pulling I figured it out.
Fastboot was definitely not working witht tf300 due to drivers. Since I couldn't find any drivers for windows. I booted up my trusty linux server, installed android-tools-fastboot and voila sudo fastboot devices shows the tf300t.
Reloading twrp did not work so I tried formatting the partitions by doing the following:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc (The first couple of times I did this, I missed this one which caused bootloader to hang when installing twrp)
fastboot erase cache
I then installed the working version of twrp I had originally by:
fastboot –i 0x0b05 flash recovery twrp.blob
I then rebooted into recovery and twrp works great without any password prompt or errors that it could not access the partitions.
I user twrp to flash 2.7.01 version of twrp and rebooted, I then used twrp to flash CM11 snapshot M7 and gapps, cleared cache and davlik and then rebooted.
The CM spinning animation took a while but then it booted into CM.
The topics I got all this info from are too numerous to mention. I hope this helps anyone that has ran into the same situation.
Long story short I bricked my phone when trying to flash recovery using toolkit. Now my phone won't turn on and recovery is gone as well. Somehow my PC can recognize the phone in fastboot mode although there's nothing showing on the screen.
So I tried the method in this thread:
http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696
It shows I flashed everything and it shows green color in the tool but when I checked the partitions, boot.img, recovery.img, userdata.img, system.img, etc are still broken. At that time the bootloader was still unlocked.
Since my computer can still see the phone in fastboot so I tried to flash the original image in fastboot. Again everything went through with no error but the phone still wouldn't turn on and the partitions are still same broken/corrupted. However the bootloader became locked after this. So now I end up with no more solutions. Since bootloader says locked(although boot.img is actually corrupted) I can't flash or do anything in fastboot command.
So I guess I'm really SOL right now... My only hope right now is maybe there will be USB JTAG or Nand flasher but I don't know if anyone can repair that right now.
Any suggestions?
fastboot oem unlock
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
Now use twrp or cwm or whatever
fastboot boot recovery nameofrecovery.img
If your phone boots to recovery you may consider running e2fsck against data and cache partitions through adb shell
Best of luck
Bootloop to fastboot after being on dp3, and restoring carbon. I tried fastboot boot twrp.img, but it fails....I also tried fastboot flash it, it does, but still reboots to fastboot. Any suggestions?
I assume you had TWRP installed when this condition occurred, and trying to boot TWRP just sent you to fastboot?
What was the exact error message when trying to fastboot boot TWRP?
suzook said:
Bootloop to fastboot after being on dp3, and restoring carbon. I tried fastboot boot twrp.img, but it fails....I also tried fastboot flash it, it does, but still reboots to fastboot. Any suggestions?
Click to expand...
Click to collapse
try this one
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
had the same problem and it helped
redpoint73 said:
I assume you had TWRP installed when this condition occurred, and trying to boot TWRP just sent you to fastboot?
What was the exact error message when trying to fastboot boot TWRP?
Click to expand...
Click to collapse
It sends the file...then I get a remote error. I tried fastboot flash too. It completed, but still boots to fastboot. Guess msm tool is needed. This phone is a pita.
I cannot get twrp to boot.....Phone refuses to boot it. WTF???
Have you tried this specifically?
Code:
fastboot flash boot recoveryname.img
I was stuck in fastboot yesterday after doing a TWRP restore. The issue was I did a backup and restore including boot and system/vendor.
My thread from a few days ago: https://forum.xda-developers.com/oneplus-7-pro/help/please-help-fastboot-boot-loop-twrp-t3949952
i.Design said:
Have you tried this specifically?
Code:
fastboot flash boot recoveryname.img
I was stuck in fastboot yesterday after doing a TWRP restore. The issue was I did a backup and restore including boot and system/vendor.
My thread from a few days ago: https://forum.xda-developers.com/oneplus-7-pro/help/please-help-fastboot-boot-loop-twrp-t3949952
Click to expand...
Click to collapse
LOL...Um, yes.
Use the All-In-One Tool and flash a fastboot firmware zip (you can find downloads in the software itself). After flashing your back on OOS and can use fastboot to boot TWRP again, then install or restore your rom
Hello guys, as we known that it is unable to use command in fastboot to boot into TWRP if we are on Android 10 (both OOS and Custom rom) at the moment, so here is the simple command allow us to do that if you want to roll back android 9 or any rom by TWRP
fastboot flash boot_a <twrp name.img>
fastboot flash boot_b <twrp name.img>
fastboot reboot
Your phone will automatically boot into TWRP, so you can flash another rom
Can anyone confirm this works?
I tried something similar when I first installed OOS 10, and I successfully booted TWRP, but I ended up getting a bootloop (stuck at the g.co/ABH warning thing) when I rebooted to system. I don't know if I did something wrong, or flashing twrp to both boot partitions caused it.
I would try again, but I'm on a critical work trip until the end of the month, so my phone's uptime is expected to be 100% until then.
worked for me while anything else didnt
LazerH said:
worked for me while anything else didnt
Click to expand...
Click to collapse
Does it wipe your data?
Didn't work for me. My boot image was patched already this is probably why.
ok, I tried this, but as reported above, now also stuck on this same: "I tried something similar when I first installed OOS 10, and I successfully booted TWRP, but I ended up getting a bootloop (stuck at the g.co/ABH warning thing) when I rebooted to system. I don't know if I did something wrong, or flashing twrp to both boot partitions caused it."
How do I resrore operation for my phone? (help?)
Well, I met this issue before, and ended up with using this method to successfully boot into twrp.
This issue seems to appear on OOS, when I using `fastboot boot xxx.img` on other ROM like omni, I'm able to boot into twrp, thanks!
can someone help me please. my phone is stuck in a fastboot bootloop. everything I try doesn't work.
fastboot boot TWRP.img NOTHING
tried your solution above and still nothing
Still stuck in fastboot this is what I get:
PS C:\Users\Les Brown\Desktop\OnePlus 6> fastboot boot twrp-3.3.1-17-enchilada-Q-mauronofrio.img
downloading 'boot.img'...
OKAY [ 0.617s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.655s
@killathenoob Download DECRYPTED OOS 10.3.0 with this help if you don't really know what to do with this.
For others people (and you if you want to root or just install TWRP after fresh OOS10 Decrypted install) don't forget to OEM unlock before doing anything.
Download this
Copy "twrp-3.3.1-17-enchilada-installer-mauronofrio.zip" into internal storage of your OP6
Power it OFF
Power it ON in fastboot mode
Launch "Boot TWRP.bat"
Connect your OP6 to your PC and wait for TWRP to boot
Install twrp-3.3.1-17-enchilada-installer-mauronofrio.zip
Reboot to recovery and install magisk if you need to.
Source
Hope I helped a bit.
Merry Christmas guys,
I have a really unusual situation.
First time that I have tried all tricks I know and I can't get myself out of this difficult situation.
I was trying to update Magisk with a patched boot file and after a reboot I was not being able anymore to access the system but only this black screen with the Crashdump Mode is appearing.
I can access the Fastboot screen, but no way to reboot to the TWRP recovery or to flash another boot.img, even through some pc flashing utilities.
Is there anything to try through another slot or something else?
I also tried:
fastboot flash boot_a boot.img
and I get this error:
FAILED (remote: Flashing is not allowed for Critical Partitions)
But my bootloader is unlocked and other commands like fastboot reboot works normally.
After I flashed through fastboot the images of boot, abl, dtbo, fw I can only access the TWRP recovery where everything is decrypted.
Any other ideas?
Try booting temporary into TWRP by using this command
fastboot boot twrp.img
If you can't use MSMDownloadTool