Database Info

Custom recovery failing ?

hello i have flashed twrp multiple times to my device after witnessing this and it just hasn't worked. I have tried re downloading and flashing that but no look. Basically what is happening is when i boot into my recovery the twrp logo/ boot screen comes on and keeps flashing on and off, can you tell me how to fix this please

ahuby09 said:
hello i have flashed twrp multiple times to my device after witnessing this and it just hasn't worked. I have tried re downloading and flashing that but no look. Basically what is happening is when i boot into my recovery the twrp logo/ boot screen comes on and keeps flashing on and off, can you tell me how to fix this please
Click to expand...
Click to collapse
1. Are you rooted?
2. If so, are you installing it via TWRPManager app or fastboot?
3. Make sure update recovery is unchecked in developer options.
4. If all of these are good to go, I would recommend a clean flash, booting into Android, turn on adb reboot to bootloader, fastboot flash recovery enterimgfilehere. Root after this, and install TWRP manager app. Install the write patch. Make sure update recovery is unchecked in dev. options.
5. If all of this fails, download a toolkit (with correct drivers) and let it do the work for you.
Hope this helps.

How long have you had the device? If it is new, unlock the device.

HTC one A9 boot loop

So I decided I wanted to try to root my HTC One A9 today, I unlocked my bootloader, worked fine, installed TWRP, worked fine, attempted to install superSU, and now I'm stuck in a boot loop, I tried to do a reset through TWRP, that didn't work, still in loop, so I decided to install CWM recovery, but when I boot to recovery mode, i get red text that says "Failed to boot to recovery mode". So after that I decided to try to reinstall TWRP just to try that again, but now my phone isn't connected to my computer, but it's not because anything is corrupted, it's because I can't get past the boot screen to actually make my phone trust my computer. Any tips?

PHYN1X said:
So I decided I wanted to try to root my HTC One A9 today, I unlocked my bootloader, worked fine, installed TWRP, worked fine, attempted to install superSU, and now I'm stuck in a boot loop, I tried to do a reset through TWRP, that didn't work, still in loop, so I decided to install CWM recovery, but when I boot to recovery mode, i get red text that says "Failed to boot to recovery mode". So after that I decided to try to reinstall TWRP just to try that again, but now my phone isn't connected to my computer, but it's not because anything is corrupted, it's because I can't get past the boot screen to actually make my phone trust my computer. Any tips?
Click to expand...
Click to collapse
What version of SuperSU did you attempt to install? It sounds like you may have used a version that didn't patch dm verity and attempted to install to system, or something went wrong with the installation process.
I suggest you boot to download mode and flash the latest RUU for your version. You'd then have a clean slate to flash TWRP and the latest SuperSU to.

PHYN1X said:
So I decided I wanted to try to root my HTC One A9 today, I unlocked my bootloader, worked fine, installed TWRP, worked fine, attempted to install superSU, and now I'm stuck in a boot loop, I tried to do a reset through TWRP, that didn't work, still in loop, so I decided to install CWM recovery, but when I boot to recovery mode, i get red text that says "Failed to boot to recovery mode". So after that I decided to try to reinstall TWRP just to try that again, but now my phone isn't connected to my computer, but it's not because anything is corrupted, it's because I can't get past the boot screen to actually make my phone trust my computer. Any tips?
Click to expand...
Click to collapse
I would also suggest starting over with the RUU for your model. Once you get TWRP back however you may want to take a look at this thread http://forum.xda-developers.com/one-a9/development/rom-a9-base-roms-recovery-flashable-t3282335 for some pre-rooted stock ROMS. I'm running the Sprint one with Xposed/GravityBox right now and it's great.

CSnowRules said:
What version of SuperSU did you attempt to install? It sounds like you may have used a version that didn't patch dm verity and attempted to install to system, or something went wrong with the installation process.
I suggest you boot to download mode and flash the latest RUU for your version. You'd then have a clean slate to flash TWRP and the latest SuperSU to.
Click to expand...
Click to collapse
I used 2.46
I ordered a micro sd to usb stick so I'll be able to actually get the RUU file onto the sd card so it can flash it, I have to do it the SD card way because it isnt recignized by my computer because it doesnt trust it

Did you try re-installing drivers and flashing new recovery with fastboot?

PHYN1X said:
I used 2.46
I ordered a micro sd to usb stick so I'll be able to actually get the RUU file onto the sd card so it can flash it, I have to do it the SD card way because it isnt recignized by my computer because it doesnt trust it
Click to expand...
Click to collapse
I believe SuperSU 2.46 was your problem and that a RUU is not required to fix this. The older SuperSU broke the dm-verity for your system partition, which is enforced by your kernel. Flash SuperSU 2.76 (the latest stable release). This will automatically patch your boot partition. You will not be able to take an OTA until flashing the stock system image, though.
You just need to fastboot flash TWRP back to your device, first (fastboot flash recovery twrp.img) just like the first time from download mode--not the bootloader. Unlike ADB, your phone doesn't need to trust your computer.
If fastboot doesn't work, check what creusset said.
creusset said:
Did you try re-installing drivers and flashing new recovery with fastboot?
Click to expand...
Click to collapse

TWRP not working?

Hi guys I'm trying to fix my phone.. seems like my phone is stuck on the your device is booting now... I have tried to flash TWRP but it also seems to stay on that but in recovery mode which never loads. I think I might have accidentally wipe my phone and flashed the following https://forum.xda-developers.com/showpost.php?p=69342186&postcount=926 update.zip and the ROM. I was on Android 6 and EMUI 4.0. My phone was rooted and right now the bootloader is unlocked. So I tried flashing TWRP through ADB. I also tried to unbrick my mate 8 L29 with the Italian knife which used to work just fine I think because I had the USB debugging enabled. But since I wiped my data to flash the rom and update.zip I'm guessing now the USB debugging is disabled? So I get this error. http://i783.photobucket.com/albums/yy117/SaranghaeK/Untitled_zpskew9nghc.png sorry I tried to add the image but I could not do it. So is the usb debugging being the culprit if so is there a way to fix it? Sorry for the LOONG msg :x

minipink said:
Hi guys I'm trying to fix my phone.. seems like my phone is stuck on the your device is booting now... I have tried to flash TWRP but it also seems to stay on that but in recovery mode which never loads. I think I might have accidentally wipe my phone and flashed the following https://forum.xda-developers.com/showpost.php?p=69342186&postcount=926 update.zip and the ROM. I was on Android 6 and EMUI 4.0. My phone was rooted and right now the bootloader is unlocked. So I tried flashing TWRP through ADB. I also tried to unbrick my mate 8 L29 with the Italian knife which used to work just fine I think because I had the USB debugging enabled. But since I wiped my data to flash the rom and update.zip I'm guessing now the USB debugging is disabled? So I get this error. http://i783.photobucket.com/albums/yy117/SaranghaeK/Untitled_zpskew9nghc.png sorry I tried to add the image but I could not do it. So is the usb debugging being the culprit if so is there a way to fix it? Sorry for the LOONG msg :x
Click to expand...
Click to collapse
Download TWRP Recovery 3.0.3
http://www.sillanwali.com/downloads/twp-3.0.3.img

Stuck in CrashDump Mode

I just purchased a new OnePlus 7 Pro yesterday and immediately set about rooting it. This is the process I followed:
fastboot oem unlock
fastboot flash boot twrp-3.3.1-4-guacamole.img
TWRP: Install > Select Storage > Internal Storage > Magisk-v20.3.zip
TWRP: Wipe > Format Data
I rebooted and was confused when I wasn't rooted. It seemed the last step had undone my root, so I went back into TWRP and installed Magisk again this time without formatting data. When I rebooted I had root and all was well.
However, there was an OEM update available that warned me it would remove root if I installed it. I found this guide to install an OEM update without losing root, which basically says to download the update via Oxygen Updater and then install it from TWRP. On step 6 is says to select the "Inject TWRP after install" option, but this didn't exist in my TWRP. I went ahead without it, thinking maybe it was enabled by default in my newer version of TWRP. The installation seemed to go without a hitch, but when I rebooted after I was stuck in fastboot. I couldn't boot my phone, nor could I get back into TWRP or regular recovery, only fastboot.
I tried flashing TWRP again using fastboot, but to no avail. I also tried running fastboot -w, but was still stuck in fastboot. I did some more research and found this comment which made it seem like all I had to do was download 10.0-GM21AA-OnePlus7ProOxygen_21.O.20_OTA_020_all_1909172051_db7a3f61-FASTBOOT from here and then run flash-all.bat. Once I did so I ended up stuck on the following screen:
Code:
QUALCOMM CrashDump Mode
--------------------------
dm-verify device corrupted Force Dump
kernel_restart
I can't seem to do anything at all with my device; not even turn it off. I tried holding the power button down for nearly a minute and no response from the phone. Is there any hope at all for my phone or have I properly destroyed it?

https://forum.xda-developers.com/oneplus-7-pro/help/mistake-kernel-error-t4029743
Same thing happened to me and I searched around a bit and found resolution. You can try what I did or try msm tool but search first as crashdump error is becoming common issue it seems
I held both volume buttons until restart and let go of one of them to get into recovery and then boot to boot loader if needed

Thank you so much! I thought I'd corrupted fastboot and permanently bricked the phone.
Once I was in fastboot I used tool all in one to flash 9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip onto my phone by picking Flash Factory Images, and now it's back up and running.
jasons1004 said:
I held both volume buttons until restart and let go of one of them to get into recovery and then boot to boot loader if needed
Click to expand...
Click to collapse
This was the magic trick I needed to know. Holding both volume buttons didn't quite work for me. I held them both down for over a minute and nothing happened. Then I tried holding down the power button and that seemed to work after several seconds. I didn't hold down volume down quickly enough the first time, so I had to do it again. I held both volume buttons and the power button for over a minute, but again, nothing. I tried a couple more times and got it to work. Haven't been able to figure out exactly what causes it to exit the CrashDump mode, but the volume buttons together seems to be the important part.

This time I tried doing the OEM updates first, thinking that attempting to install them manually is what caused my problem. First I installed the 10.0.3.GM21AA update, then after rebooting I installed the 10.3.0.GM21AA update. At this point it said my system was up to date, so I want ahead and booted into fastboot and ran fastboot flash boot twrp-3.3.1-4-guacamole.img. No errors, but no TWRP either. My phone was stuck in fastboot again.
Is it necessary to stick with 9.5.13 if I want root? Is there some way to get TWRP to work with 10?

altayh said:
This time I tried doing the OEM updates first, thinking that attempting to install them manually is what caused my problem. First I installed the 10.0.3.GM21AA update, then after rebooting I installed the 10.3.0.GM21AA update. At this point it said my system was up to date, so I want ahead and booted into fastboot and ran fastboot flash boot twrp-3.3.1-4-guacamole.img. No errors, but no TWRP either. My phone was stuck in fastboot again.
Is it necessary to stick with 9.5.13 if I want root? Is there some way to get TWRP to work with 10?
Click to expand...
Click to collapse
Just use tool to flash 9 then after first boot fasboot flash whatever 10 build you can find. Then after first boot of 10 try boot twrp and install twrp.
Honestly I just used the tool to root and flash recovery. There is a button for that and just pick your files. Good luck

altayh said:
This time I tried doing the OEM updates first, thinking that attempting to install them manually is what caused my problem. First I installed the 10.0.3.GM21AA update, then after rebooting I installed the 10.3.0.GM21AA update. At this point it said my system was up to date, so I want ahead and booted into fastboot and ran fastboot flash boot twrp-3.3.1-4-guacamole.img. No errors, but no TWRP either. My phone was stuck in fastboot again.
Is it necessary to stick with 9.5.13 if I want root? Is there some way to get TWRP to work with 10?
Click to expand...
Click to collapse
You need to use a more recent versions of TWRP with Android 10. Current unofficial version -74 should work. So in your current condition, you should be able to simply boot TWRP (using the correct version), flash TWRP installer zip (if you want TWRP installed), flash Magisk (current version is 20.3) and reboot and you should have root again.
Easiest way I've found to install the OTA updates, is to simply install the update through the phone settings, do NOT reboot immediately after the update, go into Magisk Manager, flash TWRP installer zip as if it were a Magisk module (optional, if you want TWRP installed), then install Magisk picking the option "Install to inactive slot (after OTA)". Than just reboot, and you should be updated and with root.

redpoint73 said:
You need to use a more recent versions of TWRP with Android 10. Current unofficial version -74 should work. So in your current condition, you should be able to simply boot TWRP (using the correct version), flash TWRP installer zip (if you want TWRP installed), flash Magisk (current version is 20.3) and reboot and you should have root again.
Click to expand...
Click to collapse
Ah, I was using the Official TWRP App to get the images so I was under the impression that twrp-3.3.1-4-guacamole.img was the latest. I assume you're saying I should use TWRP 3.3.1-74 Unified Unofficial Q by mauronofrio from over here instead.
redpoint73 said:
Easiest way I've found to install the OTA updates, is to simply install the update through the phone settings, do NOT reboot immediately after the update, go into Magisk Manager, flash TWRP installer zip as if it were a Magisk module (optional, if you want TWRP installed), then install Magisk picking the option "Install to inactive slot (after OTA)". Than just reboot, and you should be updated and with root.
Click to expand...
Click to collapse
This is good to know. Thanks.

Just to follow up, I applied the available OTAs through the phone settings (up to bulid 10.3.0.GM21AA) and then followed the More articulated but fully functional instructions to install TWRP 3.3.1-74 Unified Unofficial Q. Everything went well and I'm now up to date and rooted. Thanks again to both of you!

altayh said:
I assume you're saying I should use TWRP 3.3.1-74 Unified Unofficial Q by mauronofrio from over here instead.
Click to expand...
Click to collapse
That is the correct TWRP to use ("Unofficial" version -74), as it appears you have already determined.
I don't know why the "official" versions have fallen so far behind. It's been months stuck on version -4, so it seems that they have stopped going "official" for some reason. No matter, the unofficial versions are working fine (and in fact required for Android 10 as you now know), so the "official" tag seems like a technicality.

On these OnePlus phones I don't know why they love Qualcomm Crashdump mode. I fixed it sort of like you, but this worked 100%. You hold all 3 buttons (power, vol up, vol down) and you bypass the crashdump (takes several seconds 5 maybe 10), just quickly let go so you'll be in fastboot mode and can work your magic to fix the damn thing....
I even contacted OnePlus on an 8 they had no idea what to do...

Fastboot flash boot recovery.img <-- bad idea
Fastboot boot recovery.img <-- provit

Bricked or fixable?

Hi so I was installing a new rom, that twrp was having problems installing, so I had wiped the system already, I tried to update twrp to the newest version, and now it's stuck on the nvidia logo, the next problem is I can't get it to go into fastboot, I think years ago I had Installed a custom bootloader, when I try to enter fastboot it just goes back to the bootloader menu
Any possible fix or is it actually bricked?

edit the bootloader is nvtboot?

ok so i had to update the "android" drivers in device manager for fastboot, Not ADB. managed to flash recovery and a image. if anyone else has the same problem