Bear with me, I had an older version and maybe just my method but I had messed up the custom rom I had on so I went to put a new one on and wanted to update TWRP at same time.
I installed the new custom rom, then installed TWRP and correctly clicked recovery.
However now recovery just goes into fastboot mode, I went into the dev settings and put usb debugging on, authorised it but each time it goes into fastboot it is not recognised and when I reboot into phone usb debugging has been disabled.
So now I can't get into recovery to flash a new rom, nor can I put twrp on by fastboot.
Stuck at what to do
Using Havoc OS
Try booting into the recovery from fastboot
Boot into fastboot and type
Fastboot boot recovery.img (recovery.img is the file saved on your pc)
Related
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
Alright so I went to dirty flash a new ROM update but TWRP errored out so I was unable to. I went to update TWRP (I was 2 versions out of date) and it flashed without a problem. However now I can no longer boot into recovery or quickboot but my ROM loads just fine. What the hell is going on?
I actually did NOT correctly flash TWRP. I am still on the older version and still cannot boot into it
flash twrp from fastboot.
1) reboot into bootloader
2) open a terminal inside the folder where you downloaded the recovery .img file
3) type into terminal: fastboot flash recovery recoveryfilename.img
4) reboot into recovery holding power and vol -
I cannot boot into fastboot or the bootloader.
Fixed by flashing older version of TWRP with the app inside of android.
Hello, i installed dotos custom rom and gapps after flashed TWRP without root access (i don't want to root my device), all was good, the custom rom work good, so to day i manage to reinstall the same rom with another time gapps (the cause is for delete some application), all was good , and i read that it's good to make a hard reset for that the rom work nicely (i do it from the setting), i do it but after that the smartphone reboot and stuck on TWRP, i reboot the system from TWRP but don't work, it open all the time TWRP, the recovery menu disaper (i use the key volume"-" and power button don't work it don't enter to the recovery mode), i can only boot to bootloader from TWRP and access fastboot mode:
=>fastboot mode
=>unlocked
i use "fastboot continu" to access system but sim don' work in this way. so i come to you for help, i want that the system work like before, thank for your patience and help.
Reboot into fastboot mode
Have at least minimal ADB interface and fastboot drivers installed
Use a command prompt to cd to ur fastboot drivers normally C:\adb
in the same folder have your TWRP recovery image.
Then use the command fastboot flash recovery [twrpfilename.img]
Then fastboot reboot
Hold power and vol down and once in the boot loader use volume up to select recovery then press power to boot into the recovery mode
Have magisk on your SD card or go to reboot and TWRP will root your device you must never try to unroot a custom ROM because at some point they will all fail and you'll be in this problem.. i have hundreds of different custom ROMs from Android 4 to 8 and not one of them has been flawless they all have issues and big problems in the end, like operating system breaking glitches your best off sticking with stock firmware and modded and debloating urselg
Hello everyone.. I did a twrp flash and installed a custom kernel on my phone. Fastboot was still working at that time. But, when i rebooted to fastboot again to install gcam. My PC does not recognize my phone. It doesnt show my device.
Adb is working
fastboot not. Please help. I want to flash updates.
I currently have no twrp since the twrp.img i updated turned my recovery blank.
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..