Database Users

Lost recovery, cant boot, only fastboot

Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode

You need to run the phone in Qualcomm mode on a PC and run the recovery tool to fix you bootloader.
I did the same and it was a royal ball ache trying to find out how to fix it

Don't do what rosswaa said

Why not?

What you should do is boot your phone into fastboot mode, connect it to your pc. Flash this modified TWRP recovery img to your phone https://www.androidfilehost.com/?fid=24459283995297945. After that you have to flash this modified SuperSU (through the new recovery) https://www.androidfilehost.com/?fid=24459283995297946.
The normal recovery doesn't work in OOS 3.0 (just like in HOS) and it's the SuperSU that gives you the soft brick. A dirty flash of the modified SuperSU should fix it.
I also had your problem and I did what rosswaa said which shouldn't be necessary (I lost all my data and backups).

I didn't lose anything, but I tried doing what you said and my bootloader was screwed so wouldn't take a flashed recovery or anything (yes the modified one)
Wish I hadnt been so excited and just flashed but all sorted now

Hmm okay, if it doesn't work with flashing the new recovery img then do what rosswaa said and after that follow this post https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/

Obviously try what green says first, if it works then happy days

first i am really glad that someone give some advices on me. But since i am a noob, how can i flash twrp in fastboot mode? using command? "fastboot flash recovery xxx.img"? thx

SPiCa39's said:
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
Click to expand...
Click to collapse
1 Install official TWRP 3.x via fastboot twrp.me/devices/oneplustwo.html
Reboot to recovery
2 install this modified version of TWRP
forum.xda-developers.com/oneplus-2/development/recovery-teamwin-recovery-project-3-0-0-t3310713
Reboot to recovery
3 install oos3 (And supersu)
Sorry i can't post link

Fu**ed up during first twrp installation, forgot to flash supersu before reboot

On xiaomi 3s during first twrp installation, forgot to flash supersu before reboot now i am stuck on MI logo, can access fastboot but not twrp. tried re-flashing twrp (wich i can do) but the phone still stuck with no twrp acess, tried to flash fastboot (flash boot twrp.img) also does nothing.ùi am quite the noob, please help?

redsjack said:
On xiaomi 3s during first twrp installation, forgot to flash supersu before reboot now i am stuck on MI logo, can access fastboot but not twrp. tried re-flashing twrp (wich i can do) but the phone still stuck with no twrp acess, tried to flash fastboot (flash boot twrp.img) also does nothing.ùi am quite the noob, please help?
Click to expand...
Click to collapse
Boot into TWRP. Goto Advanced --> Disable DM-Verify. Reboot device. Done.

now i installed the supersu but when i reboot the phone it always boots to TWRP i think because i flashed
fastboot flash boot twrp.img (yes i am a idiot)
if i want to boot the system what should i do?

redsjack said:
now i installed the supersu but when i reboot the phone it always boots to TWRP i think because i flashed
fastboot flash boot twrp.img (yes i am a idiot)
if i want to boot the system what should i do?
Click to expand...
Click to collapse
As far as I read this thread you forgot to turn off the DM-Verify option in TWRP after install and rebooted immediately.....
Hate to break it to you but your currently installed OS is now pretty much dead now. Had the same issue when I first tried it.
You need to install a clean MIUI ROM first via fastboot and MIFlash-Tool. Then proceed to install TWRP again. When TWRP is booted the first time it will ask your permission to Modify the System. Swipe to confirm that (needed for most operations TWRP is able to do).
After you allow the system modify part, you are in TWRPs main menu. Tap on "Advanced", then tap on "Disable DM-Verify". Once again swipe to confirm.
After that, you should be able to have TWRP on your device and should be able to boot normally to MIUI... or you go straight ahead and flash a new Custom Rom.

thank you.
So i will need to download a new rom (any suggestion on which one is good? i did install twrp because my vendor rom didn't work with local 3g and LTE) and install it with the miui flash tool. Than repeat the twrp installation but disable dm-verify first, (than reinstall super su?),and at the end reboot.
No need to clear anything?

i flashed the global stable rom from the xiaomi flash tool it say successful and took just a second but i am stuck still on mi logo....

Is your phone unlocked?
In fastboot fastboot oem device-info

i unlocked it just one day before with permission message from xiaomi.

Next time used cofface twrp for redmi 3S: http://en.miui.com/thread-244098-1-1.html
Sent from my Redmi 3S using Tapatalk

Ez. Go to fastboot mode, flash again the whole ROM and flash your TWRP again. Don't forget to disable DM-verify. It stuck at logo not because of you forgot to root your device, is because of you forget to disable DM-verify.

Can't install TWRP on OP6T

Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?

¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
I'm having the same problem

¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
3.3.1.-1???...

cultofluna said:
3.3.1.-1???...
Click to expand...
Click to collapse
Affirmative. Fajita 3.3.1-1. See attached screenshot from TWRP.me. Should I be booting into a different version?

¿GotJazz? said:
Affirmative. Fajita 3.3.1-1. See attached screenshot from TWRP.me. Should I be booting into a different version?
Click to expand...
Click to collapse
Those "official" TWRP builds don't work properly on Android 10. Here is a link to the one you need:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482

jp0469 said:
Those "official" TWRP builds don't work properly on Android 10. Here is a link to the one you need:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Click to expand...
Click to collapse
Thanks, @jp0469! This helps a lot!
Just to be clear (and to get to a successful conclusion without a bricked phone), I won't be installing a TWRP installer ZIP file after booting into this TWRP image (The old style method), but instead installing the same TWRP IMG file as a "Recovery RAM Disk", correct?
¿GJ?

¿GotJazz? said:
Thanks, @jp0469! This helps a lot!
Just to be clear (and to get to a successful conclusion without a bricked phone), I won't be installing a TWRP installer ZIP file after booting into this TWRP image (The old style method), but instead installing the same TWRP IMG file as a "Recovery RAM Disk", correct?
¿GJ?
Click to expand...
Click to collapse
Need a little more info before you proceed.
I know you said that you're currently on Android 10.3.0
Are you rooted with Magisk? If not, are you planning on rooting?

jp0469 said:
Need a little more info before you proceed.
I know you said that you're currently on Android 10.3.0
Are you rooted with Magisk? If not, are you planning on rooting?
Click to expand...
Click to collapse
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.

¿GotJazz? said:
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.
Click to expand...
Click to collapse
Stick to good old ones...
Once booted in twrp via fastboot flash the installer zip. It has always worked and will always. Always latest version. And flash Magisk after.

¿GotJazz? said:
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.
Click to expand...
Click to collapse
Put the latest Magisk zip and TWRP installer (zip file) on your phone's internal memory if you don't already have them there. Now you can fastboot boot the TWRP img file (Q version). Next flash the TWRP zip to permanently install TWRP into recovery. Reboot back to recovery to make sure it worked and then flash Magisk to re-gain root.
Reboot

Thanks, guys - The only reason I asked about the alternate "RAM Disk" method was because it was listed as the installation method by the developer on the link that @jp0469 provided earlier.
I'll try the old-fashioned method, since y'all say that it works OK.

I have a brand new hp windows 10 PC and a new op6t converted to international version. Running pie latest oxygen os. I need to get minimal adb fastboot installed so I can install twrp and root. Ik it's a little different process to get twrp on 6t but I need some help. Can someone provide me with the correct fastboot to install

[email protected] said:
I have a brand new hp windows 10 PC and a new op6t converted to international version. Running pie latest oxygen os. I need to get minimal adb fastboot installed so I can install twrp and root. Ik it's a little different process to get twrp on 6t but I need some help. Can someone provide me with the correct fastboot to install
Click to expand...
Click to collapse
I always install the latest directly from Google. There is a link on this page to the latest version of Windows ADB and Fastboot. Just unzip the file you download into a directory of your choice.

Everytime I try to boot twrp It says waiting on device. What's that mean

[email protected] said:
Everytime I try to boot twrp It says waiting on device. What's that mean
Click to expand...
Click to collapse
It mean you didn't install driver on your PC.
---------- Post added at 03:38 AM ---------- Previous post was at 03:35 AM ----------
¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
Type Command: fastboot flash boot
And Use TWRP 3.3.1.30 .

Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
Click to expand...
Click to collapse
same thing happened to me, but my screen went black and i cant seem to turn it back on again. what a day. fml
i really need help, i only have that one phone for daily usage. arghhhh

uncleheng said:
same thing happened to me, but my screen went black and i cant seem to turn it back on again. what a day. fml
i really need help, i only have that one phone for daily usage. arghhhh
Click to expand...
Click to collapse
press volume down,up and power button same time for 10sec your phone will boot to bootloader mode.

After doing the fastboot boot twrp-3.3.1-30-fajita-Q-mauronofrio.img in Fastboot Mode, I installed twrp-3.3.1-30-fajita-installer-mauronofrio.zip in the booted TWRP Recovery Mode, and everything is working fine again.
Thanks, guys!

Hey I am running Android 10.3.7 and am having the same problem, I tried unofficial twrp linked abouve and still stuck on fastboot screen, I think I'm using abd 1.43, if twrp doesn't work is there an alternative? I'm newish to rooting I've rooted other phones but that was back in the good old days where it wasn't complicated. I am running a T-Mobile phone converted to international with bootloader unlocked

About to give up on flashing recovery to OOS 11.1.1.1

I tried "fastboot boot" almost all of KizuYuna's .imgs, tried fastboot boot the lineagerecovery.img. All I get is the fastboot logo and the phone just restarts into OOS... TWRP is same.
About to MSM downgrade to OOS 10 to get recovery working like I did before. Thought it would be better to flash a rom from OOS 11 to get better firmware compatibility but just wont work.

Simply go back to OS 10.3.5 using the MSM Download Tool. Upgrade via OTA to 11..1.1.1, fastboot flash boot magisk_patched-23000_11.1.1.1 from XDA 235Sanders15 post. (you are now rooted with Magisk. Via Magisk install TWRP-Installer-3.5.2_9-0 you are now unrooted but have TWRP installed. Using TWRP flash Magisk v23.0.You are now rooted on OS 11.1.1.1 with TWRP installed. Do not change the Kernel it will cause a Bootloop.

bpambrose said:
Simply go back to OS 10.3.5 using the MSM Download Tool. Upgrade via OTA to 11..1.1.1, fastboot flash boot magisk_patched-23000_11.1.1.1 from XDA 235Sanders15 post. (you are now rooted with Magisk. Via Magisk install TWRP-Installer-3.5.2_9-0 you are now unrooted but have TWRP installed. Using TWRP flash Magisk v23.0.You are now rooted on OS 11.1.1.1 with TWRP installed. Do not change the Kernel it will cause a Bootloop.
Click to expand...
Click to collapse
So you are saying MSM to 10 and then flash official 11.1.1.1 or fastboot flash boot magisk_patched-23000_11.1.1.1 (this is a full 11.1.11.1 OS flash? No need to use twrp from 10?)
Thanks

So I just went thru an Android 10 to 11.1.1.1 upgrade, and it was a bit frustrating. So I'll throw out what I learned along the way.
Note, I have a T-Mobile Variant, so sometimes you need different files/steps for T-Mo.
I flashed the full OTA via Settings > Update > Local Upgrade, which ended up boot-looping.
Via Fastboot, I did fastboot flash boot magisk_patched-23000_11.1.1.1.img; followed by fastboot reboot;
This was still boot-looping, so I shutdown the phone, and booted into recovery, which was now PBRP.
via PBRP, I flashed the full OTA again from my SDCard; then installed PBRP zip;
Reboot to System and got a Successful Boot. Yey.
Reboot to Recovery; Backup Boot.
Reboot to System
Install Magisk App; within Magisk > Install > select my Boot Backup to Patch (per Magisk instructions); I used a file manager to copy to my PC from my phone
Reboot to Fastboot; fastboot flash boot magisk_patched-23000_rJoA.img (the file Magisk created)
Reboot to System; Success!
I guess my morale of the story is, get a clean boot working, go from there. Patch your own boot, don't rely on someone else's.

Fenopy said:
So I just went thru an Android 10 to 11.1.1.1 upgrade, and it was a bit frustrating. So I'll throw out what I learned along the way.
Note, I have a T-Mobile Variant, so sometimes you need different files/steps for T-Mo.
I flashed the full OTA via Settings > Update > Local Upgrade, which ended up boot-looping.
Via Fastboot, I did fastboot flash boot magisk_patched-23000_11.1.1.1.img; followed by fastboot reboot;
This was still boot-looping, so I shutdown the phone, and booted into recovery, which was now PBRP.
via PBRP, I flashed the full OTA again from my SDCard; then installed PBRP zip;
Reboot to System and got a Successful Boot. Yey.
Reboot to Recovery; Backup Boot.
Reboot to System
Install Magisk App; within Magisk > Install > select my Boot Backup to Patch (per Magisk instructions); I used a file manager to copy to my PC from my phone
Reboot to Fastboot; fastboot flash boot magisk_patched-23000_rJoA.img (the file Magisk created)
Reboot to System; Success!
I guess my morale of the story is, get a clean boot working, go from there. Patch your own boot, don't rely on someone else's.
Click to expand...
Click to collapse
So you had to go through all the trouble because you had a bootloop issue when OTA updating to 11? I already got to 11 but am trying to fastboot boot a recovery because I want to flash a custom ROM... When I fastboot boot TWRP.img or LOS Recovery .img it just shows fastboot logo and restarts the phone with no recovery shown..

All Custom ROM installations fail the same way.

I am trying to get a custon ROM to work on my Oneplus 8 Pro (instantnoodlep)
ROMs I tried installing:
Cherish OS 3.9.5
Nameless-AOSP_instantnoodlep-12.1-20220708-0935-Official
What I do:
1. Download recovery provided with the ROM
2. Reboot to bootloader and flash recovery
'fastboot flash recovery recovery.img'
'fastboot reboot recovery'
3. Select apply update/apply from ADB
4. Connect device to PC
5. Sideload rom.zip
'adb sideload rom.zip'
6 Do Factory reset/format data from recovery
7. Restart to system
What happens:
Phone goes to fastboot and stays there.
When I try
fastboot reboot system
or
fastboot reboot recovery
I also land in fastboot again.
The only way to get out of fastboot again is fastboot boot recovery.img, which boots into recovery. When I then reboot into system, my old OOS11 boots up.
Because this is independent of the Custon ROM, there might be another issue. But which one?

You made sure you have latest OOS11 on BOTH slots?

xtcislove said:
You made sure you have latest OOS11 on BOTH slots?
Click to expand...
Click to collapse
Thanks for the response! How do i check that? Both slots of what?

Infraviored said:
Thanks for the response! How do i check that? Both slots of what?
Click to expand...
Click to collapse
When you're booted in OOS 11 just do a local install of the same OOS version that you're on. That will install OOS to the other slot, meaning you'll have the same OOS version on both slots and "should" be able to flash a custom rom.

Infraviored said:
I am trying to get a custon ROM to work on my Oneplus 8 Pro (instantnoodlep)
ROMs I tried installing:
Cherish OS 3.9.5
Nameless-AOSP_instantnoodlep-12.1-20220708-0935-Official
What I do:
1. Download recovery provided with the ROM
2. Reboot to bootloader and flash recovery
'fastboot flash recovery recovery.img'
'fastboot reboot recovery'
3. Select apply update/apply from ADB
4. Connect device to PC
5. Sideload rom.zip
'adb sideload rom.zip'
6 Do Factory reset/format data from recovery
7. Restart to system
What happens:
Phone goes to fastboot and stays there.
When I try
fastboot reboot system
or
fastboot reboot recovery
I also land in fastboot again.
The only way to get out of fastboot again is fastboot boot recovery.img, which boots into recovery. When I then reboot into system, my old OOS11 boots up.
Because this is independent of the Custon ROM, there might be another issue. But which one?
Click to expand...
Click to collapse
U don't need the command fastboot reboot recovery. U can just use the volume buttons to select recovery and press power button to boot to recovery

Nimueh said:
When you're booted in OOS 11 just do a local install of the same OOS version that you're on. That will install OOS to the other slot, meaning you'll have the same OOS version on both slots and "should" be able to flash a custom rom.
Click to expand...
Click to collapse
Another way to set your phone up for a custom rom can be found here. https://wiki.lineageos.org/devices/instantnoodlep/install
Just make sure your booting from a good 00S11 install when you do this.

I had a heck of a time with this two days ago. OP pushed c33, A12 on my phone. It took forever to corrupt both a and b enough to get twrp recovery installed and working to install A11 again. I had to load the recovery on both slots, a and b and I used twrp install to install the OTA to slot a. Right now I have nothing on slot b other that twrp recovery.

king_xerxes said:
I had a heck of a time with this two days ago. OP pushed c33, A12 on my phone. It took forever to corrupt both a and b enough to get twrp recovery installed and working to install A11 again. I had to load the recovery on both slots, a and b and I used twrp install to install the OTA to slot a. Right now I have nothing on slot b other that twrp recovery.
Click to expand...
Click to collapse
Sorted it out by this. Thank you!