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.
Related
Hello
i've just installed the twrp recovery on my lg g4 (after unlock the bootloader of course)
and when i try to boot in recovery mode it doesnt work (it shows me an android logo with an exclamation mark)
plz help me :S
thanks
It did not install properly. Same happened to me. Try
fastboot erase recovery
fastboot flash recovery twrp.img
Then try to boot to recovery using twrp manager app
jkoljo said:
It did not install properly. Same happened to me. Try
fastboot erase recovery
fastboot flash recovery twrp.img
Then try to boot to recovery using twrp manager app
Click to expand...
Click to collapse
thanks for your comment!
but i still have this problem...
jkoljo said:
It did not install properly. Same happened to me. Try
fastboot erase recovery
fastboot flash recovery twrp.img
Then try to boot to recovery using twrp manager app
Click to expand...
Click to collapse
After you have installed TWRP via adb you must boot (or stay there) into revocery and falsh the twrp-xxxx.img as "revocery" (buton down right to change from image to recovery).
hannsheinz said:
After you have installed TWRP via adb you must boot (or stay there) into revocery and falsh the twrp-xxxx.img as "revocery" (buton down right to change from image to recovery).
Click to expand...
Click to collapse
thanks man but i cant boot into recovery... this is the problem... Instead of boot into recovery, it shows me a android logo with exclamation mark..
daniel1803 said:
thanks man but i cant boot into recovery... this is the problem... Instead of boot into recovery, it shows me a android logo with exclamation mark..
Click to expand...
Click to collapse
Try this:
adb reboot bootloader
fastboot.exe flash recovery twrp-xxxx.img
fastboot.exe boot twrp-xxxx.img (same filename as above)
Then flash the same twrp-xxx.img file via "install"
After this you can direct boot into revocery with apps like quickboot, or via Vol-Down, Power-On, or direkt via reboot meneu if you use G4 Tweak Box.
If you are on 6.0 the recovery will never boot up. But don't worry, all you need to do is just download kernel package like SimpleGX, from this package copy the boot.img, then flash it via fastboot. After that let the phone boot up, reboot it to bootloader again and flash twrp.img. If you did it properly the twrp will boot up. REMEMBER to flash full kernel package otherwise you can have problems with your device.
Adam Myczkowski said:
If you are on 6.0 the recovery will never boot up. But don't worry, all you need to do is just download kernel package like SimpleGX, from this package copy the boot.img, then flash it via fastboot. After that let the phone boot up, reboot it to bootloader again and flash twrp.img. If you did it properly the twrp will boot up. REMEMBER to flash full kernel package otherwise you can have problems with your device.
Click to expand...
Click to collapse
is it save to flash the SimpleGX kernel without the included modules in the zip file?
because i only manged to flash twrp for h811 on my h815 with v20d and unlocked bootloader... i am confused
the-erazer said:
is it save to flash the SimpleGX kernel without the included modules in the zip file?
because i only manged to flash twrp for h811 on my h815 with v20d and unlocked bootloader... i am confused
Click to expand...
Click to collapse
Never flash recovery for H811 on H815, there is reason why they are different.. You could have bricked your device. Yes flashing this boot.img is completely safe as long as you flash full package later, otherwise you might have problems with software. I've done so many times without any issue, anyway it's not a softbrick, you always reflash the firmware however be aware of that if you do it wrong and get your phone bricked without access to custom recovery there is no way to recovery your data. My G4 is dead but this is caused by the well know bootloop issue (hardware fail).
Adam Myczkowski said:
Never flash recovery for H811 on H815, there is reason why they are different.. You could have bricked your device. Yes flashing this boot.img is completely safe as long as you flash full package later, otherwise you might have problems with software. I've done so many times without any issue, anyway it's not a softbrick, you always reflash the firmware however be aware of that if you do it wrong and get your phone bricked without access to custom recovery there is no way to recovery your data. My G4 is dead but this is caused by the well know bootloop issue (hardware fail).
Click to expand...
Click to collapse
Thanks for the quick answer... I got a replacement and it ships with v20d twrp for h811 was the only solution to get root... Now i have seen your post... Will try it later... I hope it works
Do you know the reason why we have to flash the kernel? Some poeple can flash twrp without...
edit: i have flashed the kernel but flashing twrp dont want to flash...
the result of fastboot is positive but if i want to boot in recovery the screen stays black and then the phone boots up normal to os...
woult it help to kdz the phone to lolipop?
Gesendet von meinem LG-H815 mit Tapatalk
Adam Myczkowski said:
If you are on 6.0 the recovery will never boot up. But don't worry, all you need to do is just download kernel package like SimpleGX, from this package copy the boot.img, then flash it via fastboot. After that let the phone boot up, reboot it to bootloader again and flash twrp.img. If you did it properly the twrp will boot up. REMEMBER to flash full kernel package otherwise you can have problems with your device.
Click to expand...
Click to collapse
the-erazer said:
Thanks for the quick answer... I got a replacement and it ships with v20d twrp for h811 was the only solution to get root... Now i have seen your post... Will try it later... I hope it works
Do you know the reason why we have to flash the kernel? Some poeple can flash twrp without...
Gesendet von meinem LG-H815 mit Tapatalk
Click to expand...
Click to collapse
Install Twrp Manager from the Play Store and then install Twrp 2.8.7.0 from it.
It's working fine on my H815 v20d
Sent from my LG G4
welder73 said:
Install Twrp Manager from the Play Store and then install Twrp 2.8.7.0 from it.
It's working fine on my H815 v20d
Sent from my LG G4
Click to expand...
Click to collapse
I have no idea how did you manage to install TWRP recovery on official 6.0 firmware since TWRP manager requires root and to root android 6.0 you have to have modified boot image...
the-erazer said:
Thanks for the quick answer... I got a replacement and it ships with v20d twrp for h811 was the only solution to get root... Now i have seen your post... Will try it later... I hope it works
Do you know the reason why we have to flash the kernel? Some poeple can flash twrp without...
Gesendet von meinem LG-H815 mit Tapatalk
Click to expand...
Click to collapse
As I mentioned above in android 6.0 google have modified it as the stock kernel does not allow to use unsigned stuff even though your bootloader is unlocked. So only way to root/install recovery on android 6.0 smartphones is to flash modified boot.img that allows to load unsigned things. If you flash recovery without changing stock kernel you'll not brick your device but the recovery will never open, but flashing superSU might brick your device, Autoprimes flashable zips include modified boot.img I suppose.
Adam Myczkowski said:
I have no idea how did you manage to install TWRP recovery on official 6.0 firmware since TWRP manager requires root and to root android 6.0 you have to have modified boot image...
As I mentioned above in android 6.0 google have modified it as the stock kernel does not allow to use unsigned stuff even though your bootloader is unlocked. So only way to root/install recovery on android 6.0 smartphones is to flash modified boot.img that allows to load unsigned things. If you flash recovery without changing stock kernel you'll not brick your device but the recovery will never open, but flashing superSU might brick your device, Autoprimes flashable zips include modified boot.img I suppose.
Click to expand...
Click to collapse
i have no more idea what to do... i have flashed the kernel... and then recovery but when i want to enter recovery nothing happens it doesnt load. after some seconds the phone boots up normal.
before that i have tried twrp manager but the app crashes every time i want to select the recovery to install.
flashify is same as flashing over fastboot.
what is the difference between the 2 versions of twrp? h811 got another kernel than h815 but why can i load this one but the right for h815 not?
the-erazer said:
i have no more idea what to do... i have flashed the kernel... and then recovery but when i want to enter recovery nothing happens it doesnt load. after some seconds the phone boots up normal.
before that i have tried twrp manager but the app crashes every time i want to select the recovery to install.
flashify is same as flashing over fastboot.
what is the difference between the 2 versions of twrp? h811 got another kernel than h815 but why can i load this one but the right for h815 not?
Click to expand...
Click to collapse
I have no idea honestly, try to reflash the firmware. Recovery doesn't load only if you don't flash boot.img properly.
Adam Myczkowski said:
I have no idea how did you manage to install TWRP recovery on official 6.0 firmware since TWRP manager requires root and to root android 6.0 you have to have modified boot image...
As I mentioned above in android 6.0 google have modified it as the stock kernel does not allow to use unsigned stuff even though your bootloader is unlocked. So only way to root/install recovery on android 6.0 smartphones is to flash modified boot.img that allows to load unsigned things. If you flash recovery without changing stock kernel you'll not brick your device but the recovery will never open, but flashing superSU might brick your device, Autoprimes flashable zips include modified boot.img I suppose.
Click to expand...
Click to collapse
Sorry,I thought he already have root.
Btw,you can't root H815 on MM without unlocking the bootloader...
Sent from my LG G4
the-erazer said:
i have no more idea what to do... i have flashed the kernel... and then recovery but when i want to enter recovery nothing happens it doesnt load. after some seconds the phone boots up normal.
before that i have tried twrp manager but the app crashes every time i want to select the recovery to install.
flashify is same as flashing over fastboot.
what is the difference between the 2 versions of twrp? h811 got another kernel than h815 but why can i load this one but the right for h815 not?
Click to expand...
Click to collapse
just for information i have tested to kdz back to lollipop v10b... downgrade was really easy using lgup but the result was twrp doesnt work... same as marshmallow... btw github had a bug ticket for h811 there was the same only vice versa...
daniel1803 said:
Hello
i've just installed the twrp recovery on my lg g4 (after unlock the bootloader of course)
and when i try to boot in recovery mode it doesnt work (it shows me an android logo with an exclamation mark)
plz help me :S
thanks
Click to expand...
Click to collapse
how do u unlock the bootloader on a LG G4 H811 ver 20i
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Darth343 said:
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Click to expand...
Click to collapse
OK use the boot.img and recovery.img made by @janjan HERE. Under the heading ¨Downloads¨ see ¨Xperia XA1¨ and download the KERNEL + RECOVERY the boot.img and recovery.img are compatible with the G3121-G3112-G3125-G3116-G3123 devices on the applicable firmware.
Flash BOTH using fastboot. The boot.img is patched to allow TWRP to boot which it will never do using the stock boot.
If you wish to go back to stock then simply use FlashTool to flash the stock fotakernel.sin and boot.sin contained in the firmware for your device.
Does it works becouse I boot my g3116 from flashtool camand was
Fastboot boot boot.img and then also it's stuck into bootloader
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!
Hello, I need help finding/extracting oneplus 9 Pro Stock Recovery image. I tried extracting from the msm tool .ops file and the payload.bin full ota but it doesn't give me the recovery image. I also tried looking inside boot.img to see if it was in there but no luck. Any help or if anyone has stock image that can hand me the link?
MaybeDontAsk said:
Hello, I need help finding/extracting oneplus 9 Pro Stock Recovery image. I tried extracting from the msm tool .ops file and the payload.bin full ota but it doesn't give me the recovery image. I also tried looking inside boot.img to see if it was in there but no luck. Any help or if anyone has stock image that can hand me the link?
Click to expand...
Click to collapse
It's in the ramdisk in the boot.img. if you want recovery back just flash stock boot.img and go to recovery
twinnfamous said:
It's in the ramdisk in the boot.img. if you want recovery back just flash stock boot.img and go to recovery
Click to expand...
Click to collapse
Where is it at to repack it?
When you use payload dump then you will see the boot.img. flash that boot.img to your phone then you can reboot to stock recovery. Happy modding!
I need the actual recovery.img bro to port orange fox for this device.
MaybeDontAsk said:
I need the actual recovery.img bro to port orange fox for this device.
Click to expand...
Click to collapse
There is no recovery.img only boot.img we have no separate recovery partition. Normally you would just use the twrp device trees to port orange fox
Oh ok
So I just need the tree files from the OnePlus 9 pro twrp download?
Not sure exactly what you need to do what you're trying to do, but maybe this will help you in some way?
OnePlus 9 Pro (lemonadep)
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
[SCRIPT] TWRP device tree generator
Create a TWRP-compatible device tree only from an Android recovery image (or a boot image if the device uses non-dynamic partitions A/B) of your device's stock ROM. It has been confirmed that this script supports images built starting from...
forum.xda-developers.com
On the latest version of A11, running Arter Kernal R12, updated to the latest canary build, and now I am unable to boot into the OS.
Tried restoring a backup I had with TWRP, but still stuck on the boot animation. Any help would be appreciated!!
Try dirty flashing OOS11 OR try flashing the stock.IMG, you can extract it from the ROM package. Could be that some of the modules is failing hence that you're stuck in bootloop.
Adelino80 said:
On the latest version of A11, running Arter Kernal R12, updated to the latest canary build, and now I am unable to boot into the OS.
Tried restoring a backup I had with TWRP, but still stuck on the boot animation. Any help would be appreciated!!
Click to expand...
Click to collapse
You need to match the Kernel with the image of the OS you are on by typing fastboot flash boot boot.img
ekin_strops said:
Try dirty flashing OOS11 OR try flashing the stock.IMG, you can extract it from the ROM package. Could be that some of the modules is failing hence that you're stuck in bootloop.
Click to expand...
Click to collapse
Can I disable the magisk modules by deleting them? if so where can I find them? as for flashing I just need to fastboot boot the correct boot.img?
Switch back to your other slot which should have the stock boot image. Boot into fastboot mode and then run one of these commands depending on which slot you're in. If you don't know, try one, boot up, then try the other. That should get your phone back to a working state.
fastboot --set-active=a
fastboot --set-active=b