Develop Bugs

Custom recovery issues! Help please!

Guys here's the thing. Android N on my N5X. When trying to install TWRP 3.0.2.2 through Nexus Root Toolkit it first boots up the recovery then when I reboot to system and back there is no TWRP. But it remains there when I use the Root button which roots and installs custom recovery. So when I have root I have TWRP. Can't I have TWRP without root I wonder?

Suren Manukyan said:
Guys here's the thing. Android N on my N5X. When trying to install TWRP 3.0.2.2 through Nexus Root Toolkit it first boots up the recovery then when I reboot to system and back there is no TWRP. But it remains there when I use the Root button which roots and installs custom recovery. So when I have root I have TWRP. Can't I have TWRP without root I wonder?
Click to expand...
Click to collapse
Doesnt the toolkit have a check box to install a script or whatever to patch the system so the recovery wont be over written? Mine has it in flash recovery option!

I'm experiencing this issue as well. I tried to install TWRP after installing that October security updates. I wonder if there's something in the update that is preventing TWRP from installing?

hilla_killa said:
Doesnt the toolkit have a check box to install a script or whatever to patch the system so the recovery wont be over written? Mine has it in flash recovery option!
Click to expand...
Click to collapse
It has something called perm.flash.recovery.zipor something which is described to do the thing you said but the problem is when the phone gets the" flash perm.flash.recovery.zip" it does nothing. It does nothing even when I try to flash it manually when I get the "trial" TWRP which disappears after rebooting.

Had the same problem. I solved it by using the old fashioned way, with fastboot commands found on the TWRP page: https://twrp.me/devices/lgnexus5x.html
Of course, I used the last image: twrp-3.0.2-2-bullhead.img

Unable to recover OxygenOS on Oneplus3

Hello everyone,
This morning, I wanted to recover OxygenOS on my Oneplus3. I'm currently running Cyanogenmod 13.
I used the following guide: "[GUIDE] How to Unroot your OnePlus 3 / 3T and go back completely to stock" (Since I'm a newb, I can't post the link. But Google will get you there)
I booted into fastboot, issued the fastboot flash recovery recovery_op3.img and fastboot oem lock commands from my Linux termina, and rebooted in recovery mode.
In recovery mode, I then erased the cache and all that, selected the "Upgrade android from USB" and issued the adb sideload ota.zip command. This is where my problems began.
After running the command, I got the error "error: protocol fault (no status)". I tried to look this error up, but couldn't find useful information.
I started to panic a bit, fearing that my phone would be bricked. However, after booting back into fastboot mode, unlocking OEM, and rebooting, my phone would boot back into Cyanogenmod 13 (A clean install).
So now I don't have a bricked phone. However, I really would like to go back to OxygenOS, so my question is whether anyone knows how to solve my problem.
Summary:
Running Linux (Debian 8) on my PC;
Running Cyanogenmod13 on my Phone;
Want to recover OxygenOS, but adb sideload gave me "error: protocol fault (no status)";
Tried running the adb sideload command as root, however that did not work;
Can still use the Cyanogenmod13.

I've seen that error once before. I had to disconnect the phone, kill the ADB process, reconnect the phone and restart ADB to get it to work.
That worked for me. Hope that helps.
Sent from my OnePlus 3 using XDA Labs

Tybalt said:
I've seen that error once before. I had to disconnect the phone, kill the ADB process, reconnect the phone and restart ADB to get it to work.
That worked for me. Hope that helps.
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
Hey, thanks for responding.
I forgot to mention that I also tried killing the adb process several times, using the adb kill-server command and by killing the process sending SIGKILL.
Another thing I tried was using another Debian machine, which is my laptop. Still, those things did not solve my issue.

Never relock your boot loader, most bricks are due to relocking.
Flash twrp, flash oxygen os ,boot, enable everything,if you want complete stock, flash stock recovery ,flash oxygen os boot to complete stock os.

Backup youre working rom..
First, you need unlocked bootloader.
1.Flash twrp 3.0.4.1 or twrp-3.1.0 x v.26 blu_spark. Reboot to recovery.
2.Clean flash (wipe data-dalvik-system-cache) Oxygen OS, since you come from a custom rom. Flash SuperSu or Magisk, if you want root. Reflash recovery. Reboot to recovery.
If youre phone does not boot in recovery, press Power till phone vibrates. Press vol. down & choose:
1. Select Bootloader. Flash recovery from PC. Safest way to flash recovery.
or
2.Select recovery. Reflash recovery. Reboot recovery.
After you are sure that you got a working recovery reboot to system.

null0seven said:
Backup youre working rom..
First, you need unlocked bootloader.
1.Flash twrp 3.0.4.1 or twrp-3.1.0 x v.26 blu_spark. Reboot to recovery.
2.Clean flash (wipe data-dalvik-system-cache) Oxygen OS, since you come from a custom rom. Flash SuperSu or Magisk, if you want root. Reflash recovery. Reboot to recovery.
If youre phone does not boot in recovery, press Power till phone vibrates. Press vol. down & choose:
1. Select Bootloader. Flash recovery from PC. Safest way to flash recovery.
or
2.Select recovery. Reflash recovery. Reboot recovery.
After you are sure that you got a working recovery reboot to system.
Click to expand...
Click to collapse
Thanks for responding.
Since I don't understand everything yet, I will spend this evening looking up everything in detail, before I start giving it another try. Do you perhaps know of a tutorial about this specific situation? I don't want to bother you by questioning everything you stated in your instructions. They seem clear enough to be able to be looked up on Google :laugh:
drmuruga said:
Never relock your boot loader, most bricks are due to relocking.
Flash twrp, flash oxygen os ,boot, enable everything,if you want complete stock, flash stock recovery ,flash oxygen os boot to complete stock os.
Click to expand...
Click to collapse
Thanks for responding.
By the steps after "if you want complete stock", do you mean that I should keep the bootloader unlocked, and then perform the same steps as in the tutorial that I used?
EDIT:
@ null0seven: I found these steps online as I was looking up some things you said (I don't have much time since I will celebrate eastern with my family today)
Rooted Users or users with ROMs other than OxygenOS having new bootloader (Official CM 13,CM 13 Based ROMs dated later than 04 June 2016,H2OS Marshmallow)​
Step 1 :- Download the OxygenOS 3.0.2 full zip from the top of the post.
Step 2 :- Boot into TWRP.Wipe Dalvik,System,Data and Cache.After that,flash OxygenOS 3.0.2.
Step 3 :- [OPTIONAL] Flash SuperSU from here :- https://www.androidfilehost.com/?fid=24459283995297946
Step 4 -> Reboot System.
Of course, this is about an old version of OxygenOS. But it looks the same as you said.
I think this, combined with your instructions, will make it a bit clearer. Still one question: What do you mean exactly by flashing?

dvbeck
https://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733

Unable to encrypt after root

Hi everyone.
I had a issue and i really want help
I had unlock the OEM,and after installing the twrp and format data (to remove the forced encrypt), i had flash the Disable_Dm-Verity_ForceEncrypt zip file.
Okay, after that i have restarted the device and configure as my away to use, after that, booted on recovery again and flashed the magisk.
But i wanna encrypt my device, and when i go to configs->security and encrypt area, says that my device its not encrypted. Okay, i followed the steps and when i gonna try to encrypt the device, the process start and... some seconds after, the phone just restart and nothing has done.
The onlys changes that i have made on system is: root and flashed a splash.img(without that stupid warning of unlocked bootloader)
I really want to encrypt my device, so, if i get stolen, the thief wont get my user data.
Can anyone help me?

Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.

marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Thanks sir, i will try!

marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?

mrkeitsuke said:
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
Click to expand...
Click to collapse
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.

marstonpear said:
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
Click to expand...
Click to collapse
I want to stick with the stock rom rooted, with the twrp installed and the user data encrypted
So i can flash things through TWRP even i have encrypt enabled?
@edit
dont worry about bootloader, i will keep unlocked

It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.

a1291762 said:
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
Click to expand...
Click to collapse
:highfive: i had done this and... i think its working!!! :crying::crying::crying:
(crying for emotion, almost thirty factory resets to get an good result :crying::crying::crying
Anyway, if anything bad occurs, i will update here, thanks a1291762 and marstonpear

Pixel 3a XL soft #BRICK - please help

On my way to installing LineageOS I tried to downgrade Android version 11 -> 10. Unfortunately I used the WRONG INCOMPATIBLE firmware files from google's website (I think for 3 XL), that's why I have a brick now. ''Device is corrupt and no bootup possible.''
Access to Fastboot and STOCK Recovery Mode is possible.
Bootloader is Locked Now (it *was* unlocked before for flashing the firmware)
ADB is not working (since I'm getting stuck on ''google'' symbol when booting up I can't go to Developer Settings)
Factory Preset from Recovery Mode fails: ''can't send spi messages.'' Same Brick occurs.
With No Access to ADB (is it possible to set up from fastboot mode without enabling it in den Developer Options?) I can't try stuff.
And with the bootloader locked no way to flash a new Rom right?
I have NO IDEA what to do next, any IDEAS??
Thank you!!
#brick

Since you can get to recovery you should download the latest ota and sideload it from recovery.

https://developers.google.com/android/images
you should flash the stock image from recovery. Basically unzip it all and just run "flash-all.bat"

41rw4lk said:
Since you can get to recovery you should download the latest ota and sideload it from recovery.
Click to expand...
Click to collapse
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?

dadu1257 said:
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
Click to expand...
Click to collapse
You need the BL unlocked to flash unsigned/unofficial images, so make sure yours is unlocked. That being said, I'm not sure how solid twrp is for our device, I've never tried it. Twrp was/is a little iffy for android 10 never mind 11. Most around here just use fastboot to do what needs to be done. Most of it is pretty quick and painless, and twrp is not really necessary.

dadu1257 said:
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
Click to expand...
Click to collapse
I'm pretty sure you would have to downgrade to android 9 (pie) and install a custom kernel to get twrp to install. Unless you want to rock android pie - like I currently am (Bootlegger's 9 - I like my smartbar customizations) - it's best to give up on TWRP and just use fastboot commands for android 10 and up.
If you do decide to downgrade to pie the elementalX kernel (ElementalX-P3a-1.06) works fine with twrp and is available on their site. Temp boot twrp via fastboot, flash kernel, flash twrp zip file, reboot to recovery and flash magisk zip for root (if you want root). But it may be hard to find older pie ROMs out in the wild to flash since devs have dropped support and will be focused on android 10/11.

teemothay said:
I'm pretty sure you would have to downgrade to android 9 (pie) and install a custom kernel to get twrp to install. Unless you want to rock android pie - like I currently am (Bootlegger's 9 - I like my smartbar customizations) - it's best to give up on TWRP and just use fastboot commands for android 10 and up.
If you do decide to downgrade to pie the elementalX kernel (ElementalX-P3a-1.06) works fine with twrp and is available on their site. Temp boot twrp via fastboot, flash kernel, flash twrp zip file, reboot to recovery and flash magisk zip for root (if you want root). But it may be hard to find older pie ROMs out in the wild to flash since devs have dropped support and will be focused on android 10/11.
Click to expand...
Click to collapse
Unlike most of the LineageOS Tutorials out there is used the Custom Recovery from Lineage to install LIneageOS! It was super easy, a few ADB commands and here it is. No Root, no TWRP whatsoever.
Follow wiki lineageos devices website instructions. Here you may also find the recovery data.
Thx guys/girls!

dadu1257 said:
Unlike most of the LineageOS Tutorials out there is used the Custom Recovery from Lineage to install LIneageOS! It was super easy, a few ADB commands and here it is. No Root, no TWRP whatsoever.
Follow wiki lineageos devices website instructions. Here you may also find the recovery data.
Thx guys/girls!
Click to expand...
Click to collapse
Cool. No more soft brick for you :good: Congrats on sorting things out. :highfive:

BUT I still cannot install TWRP Recovery on LineageOS 17. I am getting the same problem as quoted below.
I want to perform Nandroid Backups, any other way to that if TWRP doesn't want me? Maybe with a Magisk Root and some app from F Droid?
?
thanks
dadu1257 said:
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
Click to expand...
Click to collapse

dadu1257 said:
BUT I still cannot install TWRP Recovery on LineageOS 17. I am getting the same problem as quoted below.
I want to perform Nandroid Backups, any other way to that if TWRP doesn't want me? Maybe with a Magisk Root and some app from F Droid?
?
thanks
Click to expand...
Click to collapse
Twrp doesn't work very well on android 10 and above, there is a twrp install guide around here, but not much has come from it. When was the last time anyone actually made and used a nandroid backup? Not that backups aren't important, but that's a little antiquated. Besides, most are really trying to backup data, which is a shared partition on A/B devices. Generally, restoring data on A/B devices causes more problems than anything. Most data backups can be done with an app and/or making a backup of your internal storage. As for more sensitive things like your persist partition and whatnot, you can always use the 'dd' command to back those partitions up.
I should clarify, restoring nand backups of data causes more problems on A/B devices, apps that restore data and settings tend to handle it better.

Now having a different problem
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
When I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed.
I am stuck in Fastboot now.
How can I get out of that?
I used the boot.img from the google firmware android 10 I built Lineage on. Should I use a boot.img from LineageOS .zip? Is there anything like this?
What is dm-verity?
Can I get to my previous unrooted device?
I have a Pixel 3aXL with LineageOS 17
''bootslot: b
enter reason: error boot prepare''

dadu1257 said:
Now having a different problem
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
When I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed.
I am stuck in Fastboot now.
How can I get out of that?
I used the boot.img from the google firmware android 10 I built Lineage on. Should I use a boot.img from LineageOS .zip? Is there anything like this?
What is dm-verity?
Can I get to my previous unrooted device?
I have a Pixel 3aXL with LineageOS 17
''bootslot: b
enter reason: error boot prepare''
Click to expand...
Click to collapse
Reflash the boot.img from Los17 to get back to proper boot up, then patch Los17 boot.img and flash that to have root.

41rw4lk said:
Reflash the boot.img from Los17 to get back to proper boot up, then patch Los17 boot.img and flash that to have root.
Click to expand...
Click to collapse
Where is the boot.img from Lineage? There is no such file in the Lineage folder I downloaded.

dadu1257 said:
Where is the boot.img from Lineage? There is no such file in the Lineage folder I downloaded.
Click to expand...
Click to collapse
A lot of devs wil upload the boot.img separately when they upload the rom, so wherever you downloaded Los from check there. If you just have a payload.bin file in your zip, you can always dump it and grab the boot.img there. You could always just reflash Los period to get boot back, then us 'dd' command to backup your own boot.img.

custom recovery for lineageos 17 based on android 10?
teemothay said:
I'm pretty sure you would have to downgrade to android 9 (pie) and install a custom kernel to get twrp to install. Unless you want to rock android pie - like I currently am (Bootlegger's 9 - I like my smartbar customizations) - it's best to give up on TWRP and just use fastboot commands for android 10 and up.
If you do decide to downgrade to pie the elementalX kernel (ElementalX-P3a-1.06) works fine with twrp and is available on their site. Temp boot twrp via fastboot, flash kernel, flash twrp zip file, reboot to recovery and flash magisk zip for root (if you want root). But it may be hard to find older pie ROMs out in the wild to flash since devs have dropped support and will be focused on android 10/11.
Click to expand...
Click to collapse
thanks!
I got Lineage 17 w/ Magisk root running now and want to perform a full NANDroid Backup.
After some research it seems crucial to have a custom recovery like TWRP for that. There is the online nandroid thing - but I would need CWM or anything like this to restore?!
So my question is
a) is there another custom recovery (compatible with Pixel 3a XL w/ lineage 17 based on android 10) I can install and perform Nandroid backup with?
b) any other solution to perform this backup and restore? I heard there are cmd commands for that as well , but I'm a noobie not so sure to do that.
of course there are several apps out there to backup data.. but I don't trust ''any'' app to get root permission. In F Droid I couldn't find what I was looking for.
thank you for help!

Can't Install TWRP

I've unlocked my Bootloader and all via beta-test program from DCUnlocker. I wanted to install TWRP & Magisk and I have following every step available from sir Supersonic's guide, but whenever I opened recovery, it always shows stock recovery (eRecovery) even though my CMD states that the flash recovery was succesfull and I never let my phone boot up in order not to replace the TWRP just like any android devices normal recovery procedures.
https://imgur.com/rOdXWSR
can someone find a solution of this problem?