Develop Bugs

in need of assistance on android 9.0 kernel & rooting issue

I flashed twrp recovery then i did not reboot i flashed a kernel witch is 9.0 compatiable then flashed magisk now I am stuck on a white screen with the Google G with a loading bar any help would be great

WoZzYDoesitbest said:
I flashed twrp recovery then i did not reboot i flashed a kernel witch is 9.0 compatiable then flashed magisk now I am stuck on a white screen with the Google G with a loading bar any help would be great
Click to expand...
Click to collapse
Just extract and fastboot flash the original boot.img from the factory image. You'll have to open the nested zipfile in the image file to get to it. Once you flash it, you should be back where you started and able to boot system. Retrace your steps and found out what you did wrong. Which kernel? As a side note, you should first fastboot boot the TWRP.img file and then while you are in TWRP, you flash the TWRP zip file. You can also use TWRP (boot) to queue up TWRP, Kernel, and Magisk and they will all flash in that sequence saving some time. There are also sticky guides on how to do this.

v12xke said:
Just extract and fastboot flash the original boot.img from the factory image. You'll have to open the nested zipfile in the image file to get to it. Once you flash it, you should be back where you started and able to boot system. Retrace your steps and found out what you did wrong. Which kernel? As a side note, you should first fastboot boot the TWRP.img file and then while you are in TWRP, you flash the TWRP zip file. You can also use TWRP (boot) to queue up TWRP, Kernel, and Magisk and they will all flash in that sequence saving some time. There are also sticky guides on how to do this.
Click to expand...
Click to collapse
Yeah appreciate it i figured it out last night this phone drives me nuts

How to revert back to stock system image

I flashed the Android GSI (Generic System Image) but now I want to go back to Oxygen OS how do I go back.....I tried just flashing the zip for Oxygen OS but it keeps bootlooping so I figured since I flagged a new system image it wouldn't work so how do I flash the Oxygen OS system image???
Help I'm really confused can't find anything online

Abhaypraseeth said:
I flashed the Android GSI (Generic System Image) but now I want to go back to Oxygen OS how do I go back.....I tried just flashing the zip for Oxygen OS but it keeps bootlooping so I figured since I flagged a new system image it wouldn't work so how do I flash the Oxygen OS system image???
Help I'm really confused can't find anything online
Click to expand...
Click to collapse
On recovery wipe everything and format data then flash oos zip and magisk if you want to keep root and TWRP!! That's all

intoxicated.mad said:
On recovery wipe everything and format data then flash oos zip and magisk if you want to keep root and TWRP!! That's all
Click to expand...
Click to collapse
Ok I'll try that over the weekend thanks!

intoxicated.mad said:
On recovery wipe everything and format data then flash oos zip and magisk if you want to keep root and TWRP!! That's all
Click to expand...
Click to collapse
It didn't work

Abhaypraseeth said:
I flashed the Android GSI (Generic System Image) but now I want to go back to Oxygen OS how do I go back.....I tried just flashing the zip for Oxygen OS but it keeps bootlooping so I figured since I flagged a new system image it wouldn't work so how do I flash the Oxygen OS system image???
Help I'm really confused can't find anything online
Click to expand...
Click to collapse
Can you explain what the Android GSI is and where it gets flashed to? What OOS version were you on before you flashed the AGSI?

Abhaypraseeth said:
It didn't work
Click to expand...
Click to collapse
I think you need to head towards unbrick tool

shadeau said:
Can you explain what the Android GSI is and where it gets flashed to? What OOS version were you on before you flashed the AGSI?
Click to expand...
Click to collapse
Android GSI stands for Generic System Image and its a system image that can be installed on treble supported devices such as OnePlus 5T I installed it to get Pie for my phone...this was before Pie for OnePlus 5T was released and I had OOS 5.1.6 before I installed Android GSI

intoxicated.mad said:
I think you need to head towards unbrick tool
Click to expand...
Click to collapse
Does the unbricking tool include a system image?
Abhaypraseeth said:
Android GSI stands for Generic System Image and its a system image that can be installed on treble supported devices such as OnePlus 5T I installed it to get Pie for my phone...this was before Pie for OnePlus 5T was released and I had OOS 5.1.6 before I installed Android GSI
Click to expand...
Click to collapse
I'm going to guess that you might need a stock system image to flash. If you made a backup of one in TWRP before flashing the AGSI then you can just flash that. Otherwise you can see if the unbricking tool works. There's an all-in-one till tool for the 5T but it didn't look like it has a factory image. Worst case I can extract one for you (I would clean flash a ROM and extract the image since my current one has Magisk injected). Just let me know if the other fixes don't work.

shadeau said:
Does the unbricking tool include a system image?
I'm going to guess that you might need a stock system image to flash. If you made a backup of one in TWRP before flashing the AGSI then you can just flash that. Otherwise you can see if the unbricking tool works. There's an all-in-one till tool for the 5T but it didn't look like it has a factory image. Worst case I can extract one for you (I would clean flash a ROM and extract the image since my current one has Magisk injected). Just let me know if the other fixes don't work.
Click to expand...
Click to collapse
I have a system image extracted from OSS 5.1.6 I tried flashing that too but still says no OS installed and also I tried installing through Aroma installer but still booted back to TWRP

Abhaypraseeth said:
I have a system image extracted from OSS 5.1.6 I tried flashing that too but still says no OS installed and also I tried installing through Aroma installer but still booted back to TWRP
Click to expand...
Click to collapse
Have you tried flashing the system image through fastboot?

shadeau said:
Have you tried flashing the system image through fastboot?
Click to expand...
Click to collapse
no i have not
can you tell me the steps (i know how to flash the image in fastboot) but after that how do i flash OOS
EDIT
I tried the unbrick tool and it worked thanks guys for your help

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!

Question (HELP) Flashed Wrong Kernal - Stuck in Fastboot Mode

Hi I recently made a mistake by flashing Arter97 Kernel on my International/Global OP9 which was on android 12.. I am attempting to fast boot the c39 update via platform tools. I am currently stock in fastboot mode, and whenever I attempt to boot the stock 39 img I have the error, " failed to load/authenticate boot image: Load Error" Any help would be appreciated!!
Edit: SOLVED

You can try downloading and falshing the stock boot img. For whatever version of Android you were on. Like android 11,or Android 12. Make sure you get the boot img. That you had before you flashed the kernel. So download the boot img. Specific for your device. if that doesn't work you need to find the msm tool and firmware for your phone and specific model like global, eu.

Adelino80 said:
Hi I recently made a mistake by flashing Arter97 Kernel on my International/Global OP9 which was on android 12.. I am attempting to fast boot the c39 udpate via platform tools. I am currently stock in fastboot mode, and whenever I attempt to fast boot boot the stock img i have the error failed to load/authenticate boot image: Load Error. Any help would be appreciated!!
Click to expand...
Click to collapse
you need not fasboot boot boot.img
use fastboot flash boot boot.img

Soft_M said:
you need not fasboot boot boot.img
use fastboot flash boot boot.img
Click to expand...
Click to collapse
I actually did flash the update to both slots, and it would still be stuck in fast boot mode. I ended up having to use the MSM tool to reset to stock.

brandon79 said:
You can try downloading and falshing the stock boot img. For whatever version of Android you were on. Like android 11,or Android 12. Make sure you get the boot img. That you had before you flashed the kernel. So download the boot img. Specific for your device. if that doesn't work you need to find the msm tool and firmware for your phone and specific model like global, eu.
Click to expand...
Click to collapse
Thanks ended up using the MSM tool. Thank God Oneplus provides us with the tools to flash at a chip level..

Adelino80 said:
Thanks ended up using the MSM tool. Thank God Oneplus provides us with the tools to flash at a chip level..
Click to expand...
Click to collapse
Yes, for that kernel, you need boot, dtbo, & vendor_boot backup to go back to stock or another kernel. Awesome that you already fixed it though, just thought I'd mention.

Samuel Holland said:
Yes, for that kernel, you need boot, dtbo, & vendor_boot backup to go back to stock or another kernel. Awesome that you already fixed it though, just thought I'd mention.
Click to expand...
Click to collapse
Thanks for the information. By any chance how would I normally backup vendor_boot and dtbo partitions which the Arter97 Kernal touches. Can I back that up using TWRP?

You had before you flashed the kernel. So download the boot img. Specific mcdvoice for your device. if that doesn't work you need to find the msm tool and firmware for your phone and specific model like global, eu.

Question TWRP flashing method

Hi all,
I have recently shifted from Samsung A52S to Onpelus 9 PRO.
I'm now a bit confused about flashing method....
I mean :
on Samsung devices, you have to use ODIN ( that is a Fastboot replacement tool ) in order to flash the TWRP and then, on TWRP, you can freely flash any new custom ROM or any other img files, by simply press "INSTALL" button instad of ADB sideload commands.
If I well understood, in order to flash this custom ROM, I have to do that through Fastboot commands before and through TWRP ADB sideload commands after......
My question is : may I flash boot.img / vendor_boot.img / dtbo.img and ROM zip directly through TWRP "INSTALL" button instead ???
If not, can someone kindly explain which is the reason why ?
Sorry for this noob question but I'm doing my first step into Oneplus and I don't want to do a mess.....
Many thanks for the help !

I personally been wanting to know why we no longer can simply flash custom roms via TWRP like we use to. I do believe its got to do with the way the A/B partition works however that does not really answers why we can't just flash via TWRP. Unfortunately, I have not been able to find the answer so I am interested too on why we can't simply flash custom roms in TWRP and have to resort in sideloading or via fastboot. I would think flashing via a zip in TWRP will have less user errors compare to using a command line to do your flashing.
Saying that, I have been flashing via fastboot since I got this phone and even though its a longer process, it only takes a few more minutes.

twrp is not even fully adapted for android 12 or 13 (but who needs twrp anymore?)
I prefer to flash via fastbootd
(is less work for me)

best way is the magisk install

ChrisFeiveel84 said:
twrp is not even fully adapted for android 12 or 13 (but who needs twrp anymore?)
Click to expand...
Click to collapse
twrp is still the only way to backup the whole rom
it exist a non official version for 12/13

TWRP is the best tool to recover files when the OS does not boot. Since there is no ROM or kernel out there that recommend or uses TWRP for flashing. There is little reason to use TWRP unless is for file recovery. This is in respective to OP 9.