Database Develop

[Q] Need help with TWRP boot loop

Boot loop
Moto x 1060 rooted on 4.2.2 with TWRP 2.7.7.1 installed. I tried to restore. TWRP says restore completed but when I try to reboot into the loop I go. I can access TWRP but nothing else. I have two TWRP recoveries but neither works. My computer doesn't see the phone when connected, so I can't flash. Any help would be greatly appreciated.

Clownlike said:
Boot loop
Moto x 1060 rooted on 4.2.2 with TWRP 2.7.7.1 installed. I tried to restore. TWRP says restore completed but when I try to reboot into the loop I go. I can access TWRP but nothing else. I have two TWRP recoveries but neither works. My computer doesn't see the phone when connected, so I can't flash. Any help would be greatly appreciated.
Click to expand...
Click to collapse
why do u tried to restore if u have TWRP??
try to put in fastmode and flash the firmware again clean
or put in twrp and wipe cache,userdata and dalvik cache
hope that helps u

When I restore with TWRP it shows successful. Then when I boot it goes into a loop. I have 2 recoveries and they both do that. MY computer does not recognize it so I cannot flash.

Clownlike said:
When I restore with TWRP it shows successful. Then when I boot it goes into a loop. I have 2 recoveries and they both do that. MY computer does not recognize it so I cannot flash.
Click to expand...
Click to collapse
Your computer should recognize it in fastboot mode (NOT TWRP) - you need to be the bootloader screen (AP Fastboot Mode). Follow the guide in general "Return to 100% stock" to flash the entire SBF for your carrier. DO NOT ATTEMPT TO DOWNGRADE. Only flash the version you are currently on or higher.
Everything you need is in that thread, including the necessary drivers. If your phone isn't getting recognized it is either because you do not have the drivers installed, OR you are trying to connect when booted in to TWRP. Once again, this is wrong. You restore using your PC from the BOOTLOADER screen, NOT TWRP.

101
When I am in boot loader mode and try to connect with RSD Lite the phone is seen as "fast boot" connected but nothing I flash works. I have done this before and the phone was recognized but after installing TWRP it is not, nor can I flash anything, it says failed.

Thanks Sam. I got RED lite to work and all is well. Again, many thanks

Clownlike said:
Thanks Sam. I got RED lite to work and all is well. Again, many thanks
Click to expand...
Click to collapse
Excellent! Glad to help. As you probably already know, you can now flash TWRP back on and re-root. Good Luck! :good:
P.S. I sent you a private message - please check your PMs.

samwathegreat said:
Excellent! Glad to help. As you probably already know, you can now flash TWRP back on and re-root. Good Luck! :good:
P.S. I sent you a private message - please check your PMs.
Click to expand...
Click to collapse
I cannot flash or install SuperSu or TWRP. I don't really want to install TWRP because that caused the original problem. I need SuperSu but when I try to install it says "there is no SU binary installed". Phone says device is unlocked and Status code 3 and I get the bootloader unlocked warning screen. Should I reflash 4.2.2 and start over?

Clownlike said:
I cannot flash or install SuperSu or TWRP. I don't really want to install TWRP because that caused the original problem. I need SuperSu but when I try to install it says "there is no SU binary installed". Phone says device is unlocked and Status code 3 and I get the bootloader unlocked warning screen. Should I reflash 4.2.2 and start over?
Click to expand...
Click to collapse
TWRP does not cause problems - likely your issue was un-related. You cannot install SuperSU without TWRP. You do need to flash TWRP - use the latest version from here: http://techerrata.com/browse/twrp2/ghost
After you flash it, type: fastboot reboot-bootloader and immediately boot into TWRP. Click exit and it will offer to root for you.
If you insist, you can flash stock recovery back on afterwards which will remove TWRP.

Requesting Oneplus 3t stock recovery

Does anyone have the default OP3t recovery.img?
The device cannot boot into any recovery versions I have installed (TWRP or the stock recovery). The only way to access TWRP is from ADB on my computer by typing "fastboot boot [twrp.img]".
Ive tried installing TWRP through ADB to see if flashing it again will mount it properly, but nothing has worked. I can boot into the OS still, but the only way to access recovery is (as i said) through ADB.
Anyone know how to fix this? I was thinking that reflashing the default recovery.img would fix this problem, but not overly sure about even that.
I tried to install the latest OTA patch from TWRP that people have been saying fixes the bootloader issues, but that left with "updater error 7".

nicnaknic said:
Does anyone have the default OP3t recovery.img?
The device cannot boot into any recovery versions I have installed (TWRP or the stock recovery). The only way to access TWRP is from ADB on my computer by typing "fastboot boot [twrp.img]".
Ive tried installing TWRP through ADB to see if flashing it again will mount it properly, but nothing has worked. I can boot into the OS still, but the only way to access recovery is (as i said) through ADB.
Anyone know how to fix this? I was thinking that reflashing the default recovery.img would fix this problem, but not overly sure about even that.
I tried to install the latest OTA patch from TWRP that people have been saying fixes the bootloader issues, but that left with "updater error 7".
Click to expand...
Click to collapse
I have it here: https://drive.google.com/drive/folders/0B4tnYt16-NAUQm02dHhDaWlyQUE

nicnaknic said:
Does anyone have the default OP3t recovery.img?
The device cannot boot into any recovery versions I have installed (TWRP or the stock recovery). The only way to access TWRP is from ADB on my computer by typing "fastboot boot [twrp.img]".
Ive tried installing TWRP through ADB to see if flashing it again will mount it properly, but nothing has worked. I can boot into the OS still, but the only way to access recovery is (as i said) through ADB.
Anyone know how to fix this? I was thinking that reflashing the default recovery.img would fix this problem, but not overly sure about even that.
I tried to install the latest OTA patch from TWRP that people have been saying fixes the bootloader issues, but that left with "updater error 7".
Click to expand...
Click to collapse
I believe if you re-lock your phone, the phone can factory reset and get re-flash stock recovery itself. btw,have you check the OTA zip file and make sure it was not damage when you downloaded it.

can you help me man i need that file but seems to be that link in not correct, can you give me the correct link pls i am stuck

Can't you just download the stock firmware and flash through ODIN? Then you will have stock recovery and everything.
EDIT:
Cancel my suggestion. ODIN is only for Samsung phones. My bad!

nicnaknic said:
Does anyone have the default OP3t recovery.img?
The device cannot boot into any recovery versions I have installed (TWRP or the stock recovery). The only way to access TWRP is from ADB on my computer by typing "fastboot boot [twrp.img]".
Ive tried installing TWRP through ADB to see if flashing it again will mount it properly, but nothing has worked. I can boot into the OS still, but the only way to access recovery is (as i said) through ADB.
Anyone know how to fix this? I was thinking that reflashing the default recovery.img would fix this problem, but not overly sure about even that.
I tried to install the latest OTA patch from TWRP that people have been saying fixes the bootloader issues, but that left with "updater error 7".
Click to expand...
Click to collapse
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_3.5.4/
Scroll right to the bottom and look for oxygen recovery.

manor7777 said:
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_3.5.4/
Scroll right to the bottom and look for oxygen recovery.
Click to expand...
Click to collapse
that link doesnt work, when i try to download it states no file attatched

TWRP Install Being Rejected??

Hello,
I am new to this forum, but have done a bit of unlocking and installing custom roms on other phones (mostly OPO's, both my old one and friends). But this new OP 3T I just got is giving me some troubles I have not encountered before. I would LOVE to put this into the correct forum, but of course with my being new to this forum...rules...
I am following the standard install over on the TWRP site and on the OP3T, the install finishes and then I reboot and I get a screen that says:
"Your device has been unlocked and can't be trusted. If you don't want to see this screen, please lock your device by "fastboot oem lock" an erase userdata..."
I have never seen this before. Can someone give me a idea what could be going on here? Do I need to re-lock it? What did OP do to their phones!!?!
Oh and also, I am planning on installing LineageOS. Any reason I shouldn't?
Thanks!

Blenderite said:
Hello,
I am new to this forum, but have done a bit of unlocking and installing custom roms on other phones (mostly OPO's, both my old one and friends). But this new OP 3T I just got is giving me some troubles I have not encountered before. I would LOVE to put this into the correct forum, but of course with my being new to this forum...rules...
I am following the standard install over on the TWRP site and on the OP3T, the install finishes and then I reboot and I get a screen that says:
"Your device has been unlocked and can't be trusted. If you don't want to see this screen, please lock your device by "fastboot oem lock" an erase userdata..."
I have never seen this before. Can someone give me a idea what could be going on here? Do I need to re-lock it? What did OP do to their phones!!?!
Oh and also, I am planning on installing LineageOS. Any reason I shouldn't?
Thanks!
Click to expand...
Click to collapse
Is nothing wrong with your device ..What you get is a warning that your bootloader is unlocked ...
You gonna get this every time you want to boot to your ROM or to twrp....
You can proceed further to install any ROM that you like...
I think you can find a guide on XDA forums to disable this warning if you want...

cultofluna said:
Is nothing wrong with your device ..What you get is a warning that your bootloader is unlocked ...
You gonna get this every time you want to boot to your ROM or to twrp....
You can proceed further to install any ROM that you like...
I think you can find a guide on XDA forums to disable this warning if you want...
Click to expand...
Click to collapse
Ok I tried that and a new problem came up!! When I try to reboot into recovery, I do not get TWRP, but the stock recovery that was there originally! Unless they have completely changed the look of TWRP. I will try to upload a picture of it if that helps.

You can't get rid of the bootloader-unlocked warning without re-locking your bootloader, which you really should not do while you have a custom recovery installed.
Are you sure you've flashed TWRP and not just booted it it from a local file on your computer? Try using fastboot to wipe recovery first before flashing TWRP.

Anova's Origin said:
You can't get rid of the bootloader-unlocked warning without re-locking your bootloader, which you really should not do while you have a custom recovery installed.
Are you sure you've flashed TWRP and not just booted it it from a local file on your computer? Try using fastboot to wipe recovery first before flashing TWRP.
Click to expand...
Click to collapse
I followed the Fastboot method on this page (rules won't let me post the link normally): twrp. me/devices/oneplus3t.html

Blenderite said:
I followed the Fastboot method on this page (rules won't let me post the link normally): twrp. me/devices/oneplus3t.html
Click to expand...
Click to collapse
Right on that page (last paragraph of fastboot install method), you will see:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
I had a heck of a time with this myself (even reading the above). Even rebooting (after flash TWRP) to recovery (power+vol down), the TWRP install would still not "stick". Had to try multiple times. I also rooted with SuperSU 2.79 at some point in that process, which may or may not have helped TWRP to finally "stick".

redpoint73 said:
Right on that page (last paragraph of fastboot install method), you will see:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
I had a heck of a time with this myself (even reading the above). Even rebooting (after flash TWRP) to recovery (power+vol down), the TWRP install would still not "stick". Had to try multiple times. I also rooted with SuperSU 2.79 at some point in that process, which may or may not have helped TWRP to finally "stick".
Click to expand...
Click to collapse
I tried this once before, but after your suggestion to try it several times, it finally worked! Thanks!!

Flash TWRP, reboot, press the volume down key before the phone boots, go into recovery, you should see TWRP flash screen, that usually works but I'm glad you got it going

twrps not installing

is there any reason why flashing twrps via ADB would send z5 pro gt into boot loop into bootloader unable to access the custom recovry or phone needing to do emergency flashing via qfil to stock firmware i did previously use trwps on device to flash files and to sign boot to always boot twrps recovery when trying to access recovery mode . (before bootlooping)
affter bootlooping and fixing via qfil i have been unable to successful install trwps if i do it bootloop to bootloader.
whats the difference between "meta" / "flat" options in qfil
tried locked and unlocked bootloader on both 10.5.304 and 11.1.021 also tried to go straight to recovery mode affter twrps flashing on both firmware same thing lead me bootloop needing to qfill to 10.5.30
another question can i qfil flash to 11.1.021 straight away without having having to qfil 10.5.30 then ota updating to 11.1.021..
thanks in advance

leerh said:
is there any reason why flashing twrps via ADB would send z5 pro gt into boot loop into bootloader unable to access the custom recovry or phone needing to do emergency flashing via qfil to stock firmware i did previously use trwps on device to flash files and to sign boot to always boot twrps recovery when trying to access recovery mode . (before bootlooping)
affter bootlooping and fixing via qfil i have been unable to successful install trwps if i do it bootloop to bootloader.
whats the difference between "meta" / "flat" options in qfil
tried locked and unlocked bootloader on both 10.5.304 and 11.1.021 also tried to go straight to recovery mode affter twrps flashing on both firmware same thing lead me bootloop needing to qfill to 10.5.30
another question can i qfil flash to 11.1.021 straight away without having having to qfil 10.5.30 then ota updating to 11.1.021..
thanks in advance
Click to expand...
Click to collapse
Okay ?
The point is ? I must unlock , install twrp and flashing via ota ?
Flash via qfil done and isn't working
My touchscreen still have thats issue

IamRdw said:
Okay
The point is ? I must unlock , install twrp and flashing via ota ?
Flash via qfil done and isn't working
My touchscreen still have thats issue
Click to expand...
Click to collapse
if you want OTA(over the air) updates you need to lock bootloader. otherwise the updater will say something like phone has been rooted and they cant provide you an update
https://forum.xda-developers.com/z5-pro-gt/how-to/installing-ota-update-11-5-141-via-twrp-t4050027

http://anago.2ch.sc/test/read.cgi/sm...ne/1577014188/ theres a lot of information on this link here are some highlights for me
_____________________________________
>> Crash dump loop of 113 ROM burnt Z5PROGT can be restored by burning CNROM for the time being,
Even if I tried it again, it was useless, so if I look at the syntax at the time of batch execution, it seems that vbmeta.img is not burned.
It says unrecognised option `--disable-verification '.
This time, the boot loader loop only started, and TWRP couldn't start.
This time it may be packed
__________________________________________
>> 117
I'm sorry I want to confirm.
Where did you use the fastboot command?
①fastboot --disable-verification flash vbmeta vbmeta.img
②fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
It is ① that I instructed, but it looks like there are two kinds when I check it on the net.
He seemed to have hit it without knowing it.
Excuse me, can you hit both again?
________________________________________
>> 150
>> I burned 113 ZUI11 version Gro ROM.
I re-added TWRP, but when I started it, it was usable normally, so I could add Magisk,
After that, it only seems to be unavoidable that it only starts up in normal recovery mode.
It is troublesome to do it every time you want to use TWRP, but it can't be helped.
__________________________________________________ _______
this helped Solved

Unbrick and clean install Rom for zuk z2 pro

I think my zuk z2 pro is (half) bricked. It was working fine with prevous aex rom but I thought it was time to update rom.
I have copied the rom to phone and started in twrp recovery to install aosp rom and got error 7.
I have tried to get in fastboot to update twrp 3.4.0-0 and wiped data, cache, dalvik etc. Then I got the same error 7 and vendor message in twrp when I try install aosp rom.
Qfil not worked for me. Download fail: Switch To EDL FailFAiled to Swit to Emergency Download mode.
With adb I get now error: device '(null)' not found.
What can I do now after tried different steps. I don't know which is the best step and how to unbrick?
-install another twrp?
-How to transfer and install rom now, by recovery, adb/fasboot, qfil?
-Need stock firmware or doesn't matter?
My phone is rooted.
I appreciate any tips and help.

delimavi said:
I think my zuk z2 pro is (half) bricked. It was working fine with prevous aex rom but I thought it was time to update rom.
I have copied the rom to phone and started in twrp recovery to install aosp rom and got error 7.
I have tried to get in fastboot to update twrp 3.4.0-0 and wiped data, cache, dalvik etc. Then I got the same error 7 and vendor message in twrp when I try install aosp rom.
Qfil not worked for me. Download fail: Switch To EDL FailFAiled to Swit to Emergency Download mode.
With adb I get now error: device '(null)' not found.
What can I do now after tried different steps. I don't know which is the best step and how to unbrick?
-install another twrp?
-How to transfer and install rom now, by recovery, adb/fasboot, qfil?
-Need stock firmware or doesn't matter?
My phone is rooted.
I appreciate any tips and help.
Click to expand...
Click to collapse
Try to install twrp 3.2.1.0.
delimavi said:
I think my zuk z2 pro is (half) bricked. It was working fine with prevous aex rom but I thought it was time to update rom.
I have copied the rom to phone and started in twrp recovery to install aosp rom and got error 7.
I have tried to get in fastboot to update twrp 3.4.0-0 and wiped data, cache, dalvik etc. Then I got the same error 7 and vendor message in twrp when I try install aosp rom.
Qfil not worked for me. Download fail: Switch To EDL FailFAiled to Swit to Emergency Download mode.
With adb I get now error: device '(null)' not found.
What can I do now after tried different steps. I don't know which is the best step and how to unbrick?
-install another twrp?
-How to transfer and install rom now, by recovery, adb/fasboot, qfil?
-Need stock firmware or doesn't matter?
My phone is rooted.
I appreciate any tips and help.
Click to expand...
Click to collapse
Try to roll back twrp 3.2.1.0-0. I couldn't install any rom with last twrp. Everything is fine until I used twrp 3.2.1.0-0.

delimavi said:
I think my zuk z2 pro is (half) bricked. It was working fine with prevous aex rom but I thought it was time to update rom.
I have copied the rom to phone and started in twrp recovery to install aosp rom and got error 7.
I have tried to get in fastboot to update twrp 3.4.0-0 and wiped data, cache, dalvik etc. Then I got the same error 7 and vendor message in twrp when I try install aosp rom.
Qfil not worked for me. Download fail: Switch To EDL FailFAiled to Swit to Emergency Download mode.
With adb I get now error: device '(null)' not found.
What can I do now after tried different steps. I don't know which is the best step and how to unbrick?
-install another twrp?
-How to transfer and install rom now, by recovery, adb/fasboot, qfil?
-Need stock firmware or doesn't matter?
My phone is rooted.
I appreciate any tips and help.
Click to expand...
Click to collapse
I replied to your double-post already in the other thread:
tiggerle666 said:
As far as I understand, you still can access fastboot mode on startup and flash new versions of twrp?
I just had a bricked phone again, it took me many hours to find out, what went wrong:
The main problem is that when you connect the phone with USB, it shows up as COM 900 and not as COM 9008.
In my case, I the different button combinations didn't work to change that mode (but sometimes it is possible look for an older post of me). If this doesn't help, you need to use a deepflash-usb cable (basically you remove the isolation of the green and black wire and hold them together) while plugging in and simulatously press power + vol down. Then your phone will switch to 9008. Now you should be able to use QFIL. In my case the installation of QFIL was broken and I just had to reinstall it (before, it always had many error messages). And you have to start the download process in QFIL very quick after you connected your phone in 9008 mode.
You don't need adb at this stage, the command "fastbood -i 0x2b4c flash recovery twrp_xyz.img" would just be enough to flash your twrp.
Hope this helps, just reply if you need anything and I'll try to help!
Click to expand...
Click to collapse