Database Info

[Q] Getting back recovery and root after OTA to CM12s

Hello,
I have recived the OTA today and I flashed it and now I dont have a custom recovery and root. What steps do I need to take to get those things back? I have tried to use this guide https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/ but after flashing recovery.img through ADB I still have normal CM recovery.

Go to Developer Options in Settings and disable the "update CM recovery" option.
Transmitted via Bacon

It has been disabled the whole time

Ok. So you say you're flashing the recovery through adb but that's impossible so I'm assuming you're flashing with fastboot, right?
Transmitted via Bacon

I'm not really good in those names.. I have isnerted a screenshot from this program.

xamilek555 said:
I'm not really good in those names.. [emoji14] I have isnerted a screenshot from this program.
Click to expand...
Click to collapse
Looks ok. Where are you getting the recovery from? Did you rename it to "recovery.img" for a reason?
Transmitted via Bacon

I've got that file from TWRP website and I renamed it to recovery.img. I have succesfully booted into this recovery with a command "fastboot boot recovery.img" which allowed me to flash root and xposed form it but after rebooting the phone the old recovery remains...

I have the same problem. Flash TWRP says it's flashed OK, but when I reboot to recovery it's still stock.

Linnyuk said:
I have the same problem. Flash TWRP says it's flashed OK, but when I reboot to recovery it's still stock.
Click to expand...
Click to collapse
Try updating the Android SDK. That's what worked for me. ?
Sent from my A0001 using Xparent BlueTapatalk 2

I've downloaded fresh verison today so it isnt the solution in my case :/
Somebody gave me this solution and it worked!
fastboot erase recovery
fastboot reboot-bootloader
fastboot flash recovery recovery.img

xamilek555 said:
I've downloaded fresh verison today so it isnt the solution in my case :/
Somebody gave me this solution and it worked!
fastboot erase recovery
fastboot reboot-bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Same situation here...this solution isn't working for me, same problem, always Cyanogen based recovery...

After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.

mozyman said:
After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.
Click to expand...
Click to collapse
It works! I think it because of the dev settings into CM12S which force the recovery to be CM12S' one.
Thanks

Messatsu said:
It works! I think it because of the dev settings into CM12S which force the recovery to be CM12S' one.
Thanks
Click to expand...
Click to collapse
I'm having the same problem, can someone go over start to finish how they fixed this issue?

What worked for me
I previously had TWRP installed, wiped and did the C12S flash but didn't flash SuperSu before rebooting. This removed TWRP and brought me to Cynogen Recovery whenever going into recovery mode (Vol Dwn + Power). This also removed the root from my phone. To fix this took some digging and I came up with the following solutions as long as you had TWRP installed at one point. If not then unlock your boot loader and re install. I named my TWRP File Recovery just to keep things simple, but whatever your TWRP Filename is put that in at #5.
1) Enter Fastboot Mode (Vol Up + Power)
2) On your computer open command prompt (Ctrl R)
3) Plug your phone in
4) Type the following minus the quotes
"cd desktop/android-sdk-windows/platform-tools"
5) fastboot boot recovery.img
This will boot your TWRP, you can then go to flash your SuperSu file and you're done!

im having this issue too : /

mozyman said:
After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.
Click to expand...
Click to collapse
I've tried so many things today, this is the only thing that worked. Thank You!

mozyman said:
After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.
Click to expand...
Click to collapse
It works! I had the issue and this procedure solved it ! Thanks !!! :good::good::good:

Hi all,
I have just installed CM12s on my OPO and it was meant to install TWRP but each time i go into recovery to install SuperSU its still CM Recovery
1) Enter Fastboot Mode (Vol Up + Power)
2) On your computer open command prompt (Ctrl R)
3) Plug your phone in
4) Type the following minus the quotes
"cd desktop/android-sdk-windows/platform-tools"
5) fastboot boot recovery.img
Click to expand...
Click to collapse
I have done that and yey TWRP appeared and i Installed SuperUser but when i clicked on the app it said there was an issue with the binary, so i thought i would reboot into recovery and install it again...but CM recovery appeared again
Originally Posted by mozyman
After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.
Click to expand...
Click to collapse
I thought i would give that a try but nothing seems to happen, the screen just goes black. Im reboting my OPO and when the white OPO logo appears im holding the buttons down....is this too soon or too late?
Originally Posted by xamilek555
I've downloaded fresh verison today so it isnt the solution in my case :/
Somebody gave me this solution and it worked!
fastboot erase recovery
fastboot reboot-bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I have even attempted to do that but it doesnt seem to work....
Can someone help me out here....

After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.
Click to expand...
Click to collapse
it works thank you...!!

Can't flash twrp need help!

Okay so I received my opo today and wanted to unlock and root etc.. I managed to install drivers and download a toolkit which managed to unlock my bootloader but wouldn't flash the recovery so I attempted it manually via fastboot and after flashing it would reboot to a back screen then vibrate and reboot to system.. Been doing that all night? Any ideas? many thanks in advance new to this phone

Exactly what recovery version are you trying to flash? What OS is on the phone? Get rid of the toolkit, they're nothing but trouble.

Twrp 2.8.1. And its running android 4.4.4 cyanogen mod.. I have mate haha. I take it fastboot and adb are installed correctly as it shows my opo after typing fastboot devices and it unlocked my boot loader soo I'm confused

daviss101 said:
Twrp 2.8.1. And its running android 4.4.4 cyanogen mod.. I have mate haha. I take it fastboot and adb are installed correctly as it shows my opo after typing fastboot devices and it unlocked my boot loader soo I'm confused
Click to expand...
Click to collapse
Try flashing the recovery again, followed by this command
Code:
fastboot erase cache
Then:
Code:
fastboot reboot
Then try booting into recovery.
PS. You've unchecked the "update CM recovery" option in Developer Options, right?

same problem for me. tried manually installing any custom recovery, tried two different toolkits. it flashes and reboots, but then you can never enter the recovery app. even attempting to put stock back fails. i attempted the format the cache and that didn't do a thing for me. basically had to enable cm recovery updates and reset to factory in the os. after that i was back to scratch at least.

I was able to figure it out. Appears the version of TWRP is quite particular for some reason. Once I tried the latest build from here dl dot twrp dot me/bacon/ the problem was solved. Thanks for the tip @snickler

GrizzlyD said:
I was able to figure it out. Appears the version of TWRP is quite particular for some reason. Once I tried the latest build from here dl dot twrp dot me/bacon/ the problem was solved. Thanks for the tip @snickler
Click to expand...
Click to collapse
No problemo. ^_^

[Q] cm11 -> cm12 flashing issues

so, i recently updated my oneplus one from cm11 to cm12.1 and when cm12 loaded in, i got a repeated message that com.android.phone has stopped and the quick settings bar displayed that i had no sim card in. so i tried reflashing, and the same problem. i redownloaded and reflashed... same problem.
so, i went into twrp and performed a full wipe, thinking that i'd push a new zip using twrp's mount function. the problem is, when i went to mount, no drive appeared on my computer. and when i went to fastboot to flash it manually, fastboot said that 'Image is not a boot image' . the same thing happens whenever i try to re-flash recovery as well. so how can i get an os back on the system if fastboot won't cooperate and twrp is essentially useless?
tldr; no os on oneplus one, fastboot wont flash boot image, twrp mount and twrp adb wont do anything. What do?

ItsDeadEnd said:
so, i recently updated my oneplus one from cm11 to cm12.1 and when cm12 loaded in, i got a repeated message that com.android.phone has stopped and the quick settings bar displayed that i had no sim card in. so i tried reflashing, and the same problem. i redownloaded and reflashed... same problem.
so, i went into twrp and performed a full wipe, thinking that i'd push a new zip using twrp's mount function. the problem is, when i went to mount, no drive appeared on my computer. and when i went to fastboot to flash it manually, fastboot said that 'Image is not a boot image' . the same thing happens whenever i try to re-flash recovery as well. so how can i get an os back on the system if fastboot won't cooperate and twrp is essentially useless?
tldr; no os on oneplus one, fastboot wont flash boot image, twrp mount and twrp adb wont do anything. What do?
Click to expand...
Click to collapse
What's the exact command you're using with fastboot? Are you only attempting to flash the boot.img? If so, why only that?

Heisenberg said:
What's the exact command you're using with fastboot? Are you only attempting to flash the boot.img? If so, why only that?
Click to expand...
Click to collapse
I am using "fastboot flash boot [zip]" i also tried "fastboot update [zip]", neither of which worked

ItsDeadEnd said:
I am using "fastboot flash boot [zip]" i also tried "fastboot update [zip]", neither of which worked
Click to expand...
Click to collapse
You didn't answer my question, why are you giving that command? There are a dozen or so commands that you're meant to give when flashing with fastboot. The only time you use that command is when you're just trying to flash a kernel.

Heisenberg said:
You didn't answer my question, why are you giving that command? There are a dozen or so commands that you're meant to give when flashing with fastboot. The only time you use that command is when you're just trying to flash a kernel.
Click to expand...
Click to collapse
what commands would you suggest i do then? because those are the only things i used other than the wipe command

ItsDeadEnd said:
what commands would you suggest i do then? because those are the only things i used other than the wipe command
Click to expand...
Click to collapse
Well it depends on what you're trying to do. As I said, the "fastboot flash boot boot.img" command will only flash a kernel. You really shouldn't be messing around with fastboot if you don't actually know what you're doing, that's how phones get bricked. Go to my guide and follow the instructions in section 8:
http://forum.xda-developers.com/showthread.php?t=2839471

[SOLVED]
apparently sometime between me instlling cm11 and installing cm12, my oem got re-locked. which prevented me from flashing anything new.
i ran:
fastboot oem unlock
and fastboot flash boot boot.img
and voila
help thread for those with the same problem
http://forum.xda-developers.com/show....php?t=2839471
thank you for the help!

I somehow broke TWRP

I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.

mattlokk said:
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
Click to expand...
Click to collapse
Did you set:
Allow oem unlock in dev opt.
Fastboot protocol into BL?
Twrp app & manager need root to work.

Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link

thanks for the help, i'll try and work through this soon.

fpozar said:
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
Click to expand...
Click to collapse
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.

mattlokk said:
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
Click to expand...
Click to collapse
Okay so I'm guessing you have stock ROM.
To flash TWRP you have to enter fastboot mode (vol down + power I believe) and flash the twrp image with fastboot flash recovery twrp.img (rename the shield tablet twrp to just twrp.img and place it into your easy adb and fastboot folder)
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck

fpozar said:
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
Click to expand...
Click to collapse
Agreed. This is probably what is happening (as described on the TWRP webpage here:
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.
Alternately, immediately rooting (flash SuperSU or Magisk) right after flashing TWRP, will prevent TWRP from being replaced with stock recovery.
Although the inconsistent fastboot connection, and how much trouble you had flashing TWRP initially, is a bit worrisome. Try using a different cable (maybe the one you are using is not connecting well?) try another USB port on the computer, and don't use a USB hub (connect direct to the PC).

Well, like they say: persistence is key. I kept pushing and trying new things until eventually.... I bricked the device. No, not really, it's working great now on LineageOS.
Thanks again to everyone who helped me out :good:. I'm still not sure exactly what caused TWRP to stop working on my device, however following this guide helped me fix it: https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
The "flash-all.bat" restored everything to stock (including the recovery mode) and after that I was able to flash the latest TWRP and install Lineage.

Can't boot into Recovery

Hey all,
I've got an issue with my phone. I can't get into recovery.
My phone had Bluspark TWRP, was rooted with magisk and was running XXX.
I then updated to new version of OOS via recovery and stupidly re-booted the phone without flashing magisk again.
I then tried to enter recovery to flash magisk and Bluspark was gone.
I've tried re-flashing recovery via terminal, but the phone won't let me.
When I type in 'fastboot devices' in terminal, it says my phone is connected.
As soon as I type in 'fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img' and execute the command, the phone exits fastboot mode and there is some writing in the top left of the screen that says, 'press any key to exit'.
This is the method I used to flash my phone the first time, so I have no idea why it won't work.
Any ideas?
Thanks
EDIT: I'm on 9.01

You needed to flash recovery prior to rebooting the first time.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665

Ducter said:
You needed to flash recovery prior to rebooting the first time.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
What can I do now that it is too late?
If I factory reset, will I be able to flash recovery again?

cubic25 said:
What can I do now that it is too late?
If I factory reset, will I be able to flash recovery again?
Click to expand...
Click to collapse
The link I posted is the only way I could get my phone back functioning after I first started messing with the OnePlus 6 and it's a/b partitioning. It's basically starting over, the a/b setup works fine so long as we educate ourselves first..I had been flashing and tinkering since 08 and stupidly thought it was all the same. Now I know.