Database Info

Booting only takes me to TWRP

So, I went through the temp root/S-off routine with WeakSauce and Firewater. Then flashed TWRP over adb. Rebooted to TWRP which asked if I wanted to install SuperSU. I said yes. Rebooted again and came back up in TWRP. Cannot boot to system. Rebooting always takes me back to recovery. Help would be much appreciated!
Oh, and I can also boot to the bootloader, if that helps.

Can you load a rom to the internal memory or on the SD card and then flash and install a new rom?

Same Here
droidmark said:
So, I went through the temp root/S-off routine with WeakSauce and Firewater. Then flashed TWRP over adb. Rebooted to TWRP which asked if I wanted to install SuperSU. I said yes. Rebooted again and came back up in TWRP. Cannot boot to system. Rebooting always takes me back to recovery. Help would be much appreciated!
Oh, and I can also boot to the bootloader, if that helps.
Click to expand...
Click to collapse
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.

I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Sent from my HTC6525LVW using Tapatalk

edited to fix all my auto-correct typing mistakes.
The Stig 04 said:
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Click to expand...
Click to collapse
My understanding is that there's two ways of getting into a custom recovery in adb:
1: "fastboot flash recovery nameofrecovery.img" this will flash over the previous recovery whatever that was. It will stick and you get into the new recovery either through hboot or a ROM's advanced power menu.
2: "fastboot boot nameofrecovery.img" this will boot into the recovery temporarily and allow you flash things. Once you reboot from that temp recovery it will boot using whatever kernel (or other .img file in this case) you have flashed into the boot partition.
The syntax for flashing is "fastboot flash <partition> <name-of-file-to-flash-to-that-partition>"
The syntax for booting an image is "fastboot boot <name-of-the-file-to-boot>"
It sounds like you mixed those 2 together and typed " fastboot flash boot nameofrecovery.img" so when you go to boot your phone now the only thing your phone sees to boot is the recovery. That's why your solution is twofold.
1: Flash the kernel to the boot partition: "fastboot flash boot nameofkernel.img" (sometimes these are just named "boot.img"). This will load the Kernel, modules, and ROM so that your phone will boot properly.
2: flash the recovery to the recovery partition: "fastboot flash recovery nameofrecovery.img" This will permanently install your custom recovery so that you can go back into it next time you want to flash ROMs, make/restore backups, etc.
You should be good to go and will likely never make THAT mistake again. Ask me how I know...

cntryby429 said:
edited to fix all my auto-correct typing mistakes.
My understanding is that there's two ways of getting into a custom recovery in adb:
1: "fastboot flash recovery nameofrecovery.img" this will flash over the previous recovery whatever that was. It will stick and you get into the new recovery either through hboot or a ROM's advanced power menu.
2: "fastboot boot nameofrecovery.img" this will boot into the recovery temporarily and allow you flash things. Once you reboot from that temp recovery it will boot using whatever kernel (or other .img file in this case) you have flashed into the boot partition.
The syntax for flashing is "fastboot flash <partition> <name-of-file-to-flash-to-that-partition>"
The syntax for booting an image is "fastboot boot <name-of-the-file-to-boot>"
It sounds like you mixed those 2 together and typed " fastboot flash boot nameofrecovery.img" so when you go to boot your phone now the only thing your phone sees to boot is the recovery. That's why your solution is twofold.
1: Flash the kernel to the boot partition: "fastboot flash boot nameofkernel.img" (sometimes these are just named "boot.img"). This will load the Kernel, modules, and ROM so that your phone will boot properly.
2: flash the recovery to the recovery partition: "fastboot flash recovery nameofrecovery.img" This will permanently install your custom recovery so that you can go back into it next time you want to flash ROMs, make/restore backups, etc.
You should be good to go and will likely never make THAT mistake again. Ask me how I know...
Click to expand...
Click to collapse
I didn't use fastboot load TWRP, I used the adb method shown on TeamWin's project page for the Verizon M8:
***********
Download - ADB / Terminal method:
Download the newest .img file from here
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.img
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
Then reboot to complete installation.
***********
Thanks all for the other suggestions which I am about to attempt!

I had this happen to me on my Asus EeePad TF101. It seems that TWRP has a bug that prevents it from setting a "boot to system" flag on some devices, causing it to always boot to recovery.
The solution for the TF101 was to reinstall the stock boot image, which appears to align with the instructions already given. Good luck! I know the terrible feeling I had when this happened to my tablet...

Zallantor said:
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
Click to expand...
Click to collapse
Whew! Thanks!!
Not only did that save my bacon, it had the added benefit of getting me the insecure kernel which I had forgotten about since going through the whole root/S-off/unlock bootloader/insecure kernel routine with my Droid DNA quite a while back.

Zallantor said:
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
Click to expand...
Click to collapse
I was soft bricked and only able to boot into bootloader and recovery and this write up worked for me. Just wanted to say thanks.

Don't use adv/terminal way. It's writing recovery to wrong partition..
Sent from my HTC6525LVW using XDA Premium 4 mobile app

The fastboot command to flash your recovery is:
fastboot flash recovery recovery.img
where "recovery.img" is the name of your recovery.img file on your host computer. Don't use "fastboot flash boot recovery.img", as I believe this will flash your boot partition, not the recovery partition.

hanginwithdaddo said:
The fastboot command to flash your recovery is:
fastboot flash recovery recovery.img
where "recovery.img" is the name of your recovery.img file on your host computer. Don't use "fastboot flash boot recovery.img", as I believe this will flash your boot partition, not the recovery partition.
Click to expand...
Click to collapse
if you flash to anything but the recovery partition your in some trouble.
same goes for anything like this, make sure you know what that .img is and you trust it. someone could have renamed an hboot to recovery and you end up flashing an hboot to your recovery partition because someone was careless with naming of files.

So I need help... I'm stuck in a bootloader loop. And every time I try to do this fix, terminal keeps telling me this:
error: cannot open 'M8VZWbootInsecure.img'
Any ideas?

tim.ton said:
So I need help... I'm stuck in a bootloader loop. And every time I try to do this fix, terminal keeps telling me this:
error: cannot open 'M8VZWbootInsecure.img'
Any ideas?
Click to expand...
Click to collapse
are you on a mac? reboot...
---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------
The Stig 04 said:
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
This is incorrect.
command is:
fastboot flash recovery nameofrecovery.img
additionally, since you can boot into TWRP, have you tried sideloading a rom?
(in TWRP, go to ADVANCED, click SIDELOAD... i think you need to swipe to activate... then from terminal: adb sideload nameofROM.zip)

RBThompsonV said:
are you on a mac? reboot...
---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------
This is incorrect.
command is:
fastboot flash recovery nameofrecovery.img
Click to expand...
Click to collapse
Oh yeah! Lol I knew it was something like that. Thanks!
Sent from my HTC6525LVW using Tapatalk

[Q] New Android update bricked phone.

Just got a notice that there was an Android update, I'm assuming a small patch. But now I'm stuck in at the LG boot logo. I can still boot into TWRP recovery. But no matter what I can't start my phone all the way up. How do I fix this?

gpitner said:
Just got a notice that there was an Android update, I'm assuming a small patch. But now I'm stuck in at the LG boot logo. I can still boot into TWRP recovery. But no matter what I can't start my phone all the way up. How do I fix this?
Click to expand...
Click to collapse
You should never install updates if you have installed a custom recovery.
Did you do a factory reset from recovery? That should fix it.
If doing a factory reset doesn't fix your phone, then you need to flash your stock firmware or a custom rom.
Cheers

What worked for me was from the TWRP terminal command was to type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter,
and type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
However I won' take credit for coming up with this, Weston Madsen over at androidcentral and the IRC xda-devs helped me put it all together. A huge thanks to them!

never do update if you have a custom recovery

[Q] Stuck at twrp

Ok so I am stuck, I recently rooted my device and accepted the ota, big error on my part. I then proceeded to install twrp via adb commands, in Ubuntu... problem not is I am now stuck in twrp 2.6.3.2, and the touch in this version is very jenky, the bottom half doesn't accurately register touch commands. Can anyone help me to restore this device?
-note twrp bypasses download mode
-and factory restore doesn't work
-I was able to flash cloudy g3 but I can't get past twrp
-also I did an advance wipe but still couldn't get anywhere.
Please help!

nicklefloss said:
Ok so I am stuck, I recently rooted my device and accepted the ota, big error on my part. I then proceeded to install twrp via adb commands, in Ubuntu... problem not is I am now stuck in twrp 2.6.3.2, and the touch in this version is very jenky, the bottom half doesn't accurately register touch commands. Can anyone help me to restore this device?
-note twrp bypasses download mode
-and factory restore doesn't work
-I was able to flash cloudy g3 but I can't get past twrp
-also I did an advance wipe but still couldn't get anywhere.
Please help!
Click to expand...
Click to collapse
From the TWRP terminal command type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.

jsho31 said:
From the TWRP terminal command type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
Thanks but that doesnt work because my phone doesnt register on ubuntu

nicklefloss said:
Thanks but that doesnt work because my phone doesnt register on ubuntu
Click to expand...
Click to collapse
you use the terminal command via TWRP, not your lcomputer

How to install TWRP after Magisk?

How to install TWRP after Magisk?
I have a OnePlus 6 running Oxygen OS 9.0 and I managed to install Magisk by obtaining the stock boot image and using the magisk manager app to patch it to include magisk, then I flashed the patched boot.img using fastboot and ADB.
The reason I did it this way is that every time I tried to boot with twrp.img in order to flash twrp.zip, I would run into a screen saying Qualcomm CrashDump Mode and TWRP wouldn't boot.
Now I want to install TWRP and I was wondering if there is any way of doing it by using Magisk, so I wouldn't have to boot twrp.img.
Any help would be greatly appreciated.

Same problem here. Already tried to boot every version of TWRP without success.

abrahammurciano said:
How to install TWRP after Magisk?
I have a OnePlus 6 running Oxygen OS 9.0 and I managed to install Magisk by obtaining the stock boot image and using the magisk manager app to patch it to include magisk, then I flashed the patched boot.img using fastboot and ADB.
The reason I did it this way is that every time I tried to boot with twrp.img in order to flash twrp.zip, I would run into a screen saying Qualcomm CrashDump Mode and TWRP wouldn't boot.
Now I want to install TWRP and I was wondering if there is any way of doing it by using Magisk, so I wouldn't have to boot twrp.img.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
If you have magisk manager with working root.... Then YES you can.... Just download Official TWRP app from GPlay... Open it give root permissions and follow the onscreen instructions.... Thats it...and yes use the zip not the img file

James Blode said:
If you have magisk manager with working root.... Then YES you can.... Just download Official TWRP app from GPlay... Open it give root permissions and follow the onscreen instructions.... Thats it...and yes use the zip not the img file
Click to expand...
Click to collapse
But there's no button to flash, I open the app, select flash recovery, select device, but theres no button to flash it.
See screenshot

do you have fastboot and adb installed on your computer? I assume so as you have oem unlocked to flash magisk, correct?
Copy the TWRP file that ends with .img to your desktop
if so, open a command prompt (windows key +R and type cmd press enter)
type "cd desktop" without quotes and press enter
type fastboot boot "twrp.img" (whatever the file name actually is)
Congrats, you are now in TWRP. But wait, there's more! if you reboot to system or other wise leave TWRP at this point you will revert back to stock. to flash recovery onto your device permanently, install the TWRP.ZIP (The ZIP is IMPORTANT) as it changes the boot on the OP6 to have the TWRP image (oh, by the way, there is no recovery partition on OP6 like previous devices [Thanks A/B partition!])
Now you can reboot to your hearts content. remember if you update OOS, you will lose the custom recovery, so flash the TWRP.zip after every update!

Denkai said:
do you have fastboot and adb installed on your computer? I assume so as you have oem unlocked to flash magisk, correct?
Copy the TWRP file that ends with .img to your desktop
if so, open a command prompt (windows key +R and type cmd press enter)
type "cd desktop" without quotes and press enter
type fastboot boot "twrp.img" (whatever the file name actually is)
Congrats, you are now in TWRP. But wait, there's more! if you reboot to system or other wise leave TWRP at this point you will revert back to stock. to flash recovery onto your device permanently, install the TWRP.ZIP (The ZIP is IMPORTANT) as it changes the boot on the OP6 to have the TWRP image (oh, by the way, there is no recovery partition on OP6 like previous devices [Thanks A/B partition!])
Now you can reboot to your hearts content. remember if you update OOS, you will lose the custom recovery, so flash the TWRP.zip after every update!
Click to expand...
Click to collapse
Yes I have fastboot and ADB on my computer (Linux btw), and as I mentioned it the first post, I already tried that, except that instead of booting into TWRP after "fastboot boot twrp.img" I got to a screen saying Qualcomm CrashDump mode (see attached image (the image might not be exactly the same as mine, I found that on the internet because I don't have my computer to reproduce it now)).

super odd. maybe your boot image is corrupt? still doesn't explain why fastboot boot isn't working though... Try bluSpark's TWRP image. it's a solid build and I am not having issues with it.
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page17
or you can also try swapping to the other partition by typing 'fastboot --set-active=_a' (or fastboot --set-active=_b) and booting to that recovery.
if that doesn't work for ya, try and restore stock via fastboot is my only suggestion:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665

[/COLOR]
abrahammurciano said:
Yes I have fastboot and ADB on my computer (Linux btw), and as I mentioned it the first post, I already tried that, except that instead of booting into TWRP after "fastboot boot twrp.img" I got to a screen saying Qualcomm CrashDump mode (see attached image (the image might not be exactly the same as mine, I found that on the internet because I don't have my computer to reproduce it now)).
Click to expand...
Click to collapse
I wonder if this problem has been solved? After having Root without TWRP since last year, I decided to flash TWRP now because I miss having a Nandroid backup. But just like op, right after I type in "fastboot boot TWRP.img", I end up with that Qualcomm crash dump error, resulting in a fastboot boot loop every time I restart the phone. My only recourse is to use the MSM flash tool that reflashes everything and returns the phone into factory stock. In the process wiping out all my data. I don't think there's anything corrupted
EDIT: the problem wasn't the procedure; it was the damned bootable TWRP .img files. I downloaded different TWRP.img versions, and they all failed to flash into temporary TWRP, except for this one that I found here: https://drive.google.com/open?id=1CJoBQ5ZuAExv27XLWwLMFYfHoLEu5YFJ You can use this bootable .img to flash any TWRP version compatible with your device

Does it work for Android 10?
oneplus 6 running oxygen os beta 30 with magisk 20.1 without twrp

Borat38 said:
[/COLOR]
I wonder if this problem has been solved? After having Root without TWRP since last year, I decided to flash TWRP now because I miss having a Nandroid backup. But just like op, right after I type in "fastboot boot TWRP.img", I end up with that Qualcomm crash dump error, resulting in a fastboot boot loop every time I restart the phone. My only recourse is to use the MSM flash tool that reflashes everything and returns the phone into factory stock. In the process wiping out all my data. I don't think there's anything corrupted
EDIT: the problem wasn't the procedure; it was the damned bootable TWRP .img files. I downloaded different TWRP.img versions, and they all failed to flash into temporary TWRP, except for this one that I found here: https://drive.google.com/open?id=1CJoBQ5ZuAExv27XLWwLMFYfHoLEu5YFJ You can use this bootable .img to flash any TWRP version compatible with your device
Click to expand...
Click to collapse
Please I need TWRP for Blackview BV9600 pro please share with me if you have a link to a webpage I may find it

James Blode said:
If you have magisk manager with working root.... Then YES you can.... Just download Official TWRP app from GPlay... Open it give root permissions and follow the onscreen instructions.... Thats it...and yes use the zip not the img file
Click to expand...
Click to collapse
Hello I'm having magisk root access and official TWRP app but can't use it for NAndroid backup, how can I use the app for backup and fishing custom ROM?

Need help needed with fastboot(loop)

I've decided to upgrade to OOS11 stable and patch the boot before going into the rom. What I did was:
1. Flash latest TWRP (3.5.2_9-0)
2. Reboot to recovery
3. Flash ONLY OOS11 boot.img
4. Flash TWRP again
5. Install Magisk and Kirisakura-R 1.1.1 kernal (for f2fs support)
6. Reboot to recovery
Here I was going to do the same on other partition but TWRP failed to boot and screen kept flashing but I noticed that ADB was connected so I rebooted to fastboot and flash stock boot I've previously extracted from stock ROM. Now I face another problem, phone doesn't boot anywhere else but fastboot.
I've tried a few stuff to get it back.
# There were some cases where the phone won't boot with bootloader unlocked and stock boot so I managed to patch boot.img with Magisk using an emulator and then flash it.
# Tried booting into TWRP but phone phone would get stuck in "Fastboot mode" screen with fastboot still connected (And taking commands from PC).
# Tried flashing TWRP to boot partition which worked previously but this time the problem stayed and kept booting into fastboot.
A few more points that I should mention,
# I've backed up my entire phone using TWRP so I can unbrick it if I somehow manage to get into TWRP
# I don't have the backup on my computer. It's on the phone.
I absolutely can't lose those data. Yeah, mistake on my side for not backing up on my computer but to my defense, this never happened before so I let my guard down this time.
What options do I have left? Any hint would be appreciated. Thanks for reading