dont flash Ota 35 - Oppo Find 7 and 7a

I just flashed ota 35 from baidu site and it changes partition layout some how on my qhd 9076 and installs colors stock recovery, which wont allow any zip, not including oppo updater script (which arent present in our normal zip´s (gapps/super su etc.) but worse it wont allow flashing twrp through fastboot any more... it says flashed ok but still only stock recovery present
And there´s no gapps in update zip from oppo, so it levees you locked with stock recovery, no gapps, no super su binaries!!!
This suks big time, dunno what oppo is thinking/making with this sort of update
was lucky i had x9006x9076coloros_2.0.0i_full-.zip on my sd? solved it and it allowed me to flash twrp through fastboot again and restore backup.
**edit: what....? never had to use that command before, but thanks a lot Entropy512 **
So this means, every time you update ota from baidu now, you have to unlock bootloader, first, then fastboot twrp, then install gapps + super su, phyy :silly:

spoonymoon said:
I just flashed ota 35 from baidu site and it changes partition layout some how on my qhd 9076 and installs colors stock recovery, which wont allow any zip, not including oppo updater script (which arent present in our normal zip´s (gapps/super su etc.) but worse it wont allow flashing twrp through fastboot any more... it says flashed ok but still only stock recovery present
And there´s no gapps in update zip from oppo, so it levees you locked with stock recovery, no gapps, no super su binaries!!!
This suks big time, dunno what oppo is thinking/making with this sort of update
was lucky i had x9006x9076coloros_2.0.0i_full-1.zip on my sd? solved it and it allowed me to flash twrp through fastboot again and restore backup.
Click to expand...
Click to collapse
fastboot oem unlock
Google mandated a move to Nexus-style (locked by default but user-unlockable) bootloader locking with 4.4

Entropy512 said:
fastboot oem unlock
Google mandated a move to Nexus-style (locked by default but user-unlockable) bootloader locking with 4.4
Click to expand...
Click to collapse
Oem unlock don't make any difference, still locked, wont flash twrp, even it claims both oem unlock and flashing twrp.img went ok....but still stock recovery!?
They must have made some partition changes in 35, because when flashing through twrp, it gives two errors can't wipe data , but it don't give any flashing fail error, then when booting up it fc setup and won't continue , then booting into recovery again it's stock! ! Then flashing 35 through stock recovery, there's no errors and system boots up!
As said don't flash 35 you'll regret it

Think 34 is also similar in what you described.

To Entropy512......
What do you think will happen if we delete the new ´recovery dir (just including install_recovery.sh file) completly and replaced boot image from older ota version´s ? eks. from 33 which is not locked, i know because i flashed it and all ok and then put in 35 ota??
would it work you think? i dont have the guts to try...hehe
thx in advance

Try this. Download tantrums recovery flasher, unpack the zip on your computer, then in the "rec" folder go to "oppo" and extract the one other than "stock"
Now copy the modded recovery into the folder which contains fastboot.exe
And then "fastboot boot recovery.img"
the modded recovery will boot and then via that recovery, flash the tantrums recovery flasher. Aroma installer will start, then select twrp and flash what ever you like!

Related

[DEV] recovery

attached is a semi-working recovery, you can flash it with "fastboot flash recovery recovery.img".
update: the recovery can flash boot.img's too, if the custom rom uses "dd" instead of "write_raw_image" to flash the boot.img. i hope mike updates his rom
don't use anything except for "install from sdcard"
i take no responibility for any harm to your device or data
it's basicaly a repacked cwm recovery combined with the stock 1.26 recovery kernel/ramdisk with modifications to init.rc
it is intented for developers wanting to toy around with custom roms, until someone makes a real recovery
no support nor updates will be made for this
is it tested or not yet.
I've tested it
ok thanks, since currently there is no other option to unlock bootloader other than htcdev & lack of RUU sources is too risky to flash custom recovery at this point. so technically it will skip zip package signature check? so we can start working on working custom rom.
You can always flash the stock recovery again ith fastboot
The reason why this recovery is useful is because i dont have to repack system qnd userdata images with ext4. Plus, you can update the userdata partition. Flashing with fastboot erases it
looks nice!
could you maybe share your knowledge about creating this recovery? i'm trying the same for the one s but can't get it packed together correctly...
blubbers said:
You can always flash the stock recovery again ith fastboot
The reason why this recovery is useful is because i dont have to repack system qnd userdata images with ext4. Plus, you can update the userdata partition. Flashing with fastboot erases it
Click to expand...
Click to collapse
Understand. My concern is no RUU for my device available yet & im afraid to use from other region stock rom Thanks for ur effort.
Do I have to unlock my phone to install this recovery?
moom999 said:
Do I have to unlock my phone to install this recovery?
Click to expand...
Click to collapse
yes, there are only 2 ways of installing a recovery.
fastboot and adb
fastboot requires you to unlock in order to "fastboot flash recovery"
and in order to possibly do it through adb you need root and in order to get root at the minute you need to be able to flash an insecure boot image through fastboot, which again, you need to unlock in order to "fastboot flash boot"
Hi blubbers,
There is a guy on general thread who wants to dump a developer phone. It's s4 not tegra but might help.
http://forum.xda-developers.com/showthread.php?p=24496390
sent from my HTC one X using tapatalk

Possible to restore recovery and re-lock bootloader without data lost

So I brought oneplus 3t for my father from china so it running hydrogen OS but now we moved back to Australia it would more sensible to change to google services for apps download and updates so i flashed Oxygen OS something stable but I was wondering how should re lock boot loader and maybe flash to stock recovery (Optional) to have boot up message and maybe encryption enabled.
DrUnknownEMC said:
So I brought oneplus 3t for my father from china so it running hydrogen OS but now we moved back to Australia it would more sensible to change to google services for apps download and updates so i flashed Oxygen OS something stable but I was wondering how should re lock boot loader and maybe flash to stock recovery (Optional) to have boot up message and maybe encryption enabled.
Click to expand...
Click to collapse
You need to have usb debugging enabled in your phone and adb tools installed in your pc before you do this.
For locking bootloader :
Connect the phone to computer,
Restart the phone in bootloader mode
Open command prompt window
Check connection by typing fastboot devices . You should see your device listed
Type fastboot oem lock
Reboot once the process completes. Be aware this will wipe your phone and ALL data will be lost.
It is advisable to keep boot loader unlocked.
For stock recovery :
Download stock recovery image from the forum
Save it in the same folder where your adb is installed in windows. The file name should be recovery.img
Reboot into bootloader mode
Open command prompt and
Type fastboot flash recovery recovery.img
Stock recovery to be installed before you lock bootloader
DrUnknownEMC said:
So I brought oneplus 3t for my father from china so it running hydrogen OS but now we moved back to Australia it would more sensible to change to google services for apps download and updates so i flashed Oxygen OS something stable but I was wondering how should re lock boot loader and maybe flash to stock recovery (Optional) to have boot up message and maybe encryption enabled.
Click to expand...
Click to collapse
a cautionary warning regarding the above reply to you, don't' relock the bootloader while you're on a custom recovery and/or kernel, and also while you have changes to the system (installed any mods or deleted any files form system folder)
so in theory it's possible,
1- you need to sideload a full stock rom (download from oneplus website) it's better to be stable not beta (you should have adb drivers installed and stock recovery, sideload will insure you have stock everything)
2- after you successfully sideloaded a full stock rom and make a full boot to system, you can follow the above re-lock instructions.
theduke7 said:
a cautionary warning regarding the above reply to you, don't' relock the bootloader while you're on a custom recovery and/or kernel, and also while you have changes to the system (installed any mods or deleted any files form system folder)
so in theory it's possible,
1- you need to sideload a full stock rom (download from oneplus website) it's better to be stable not beta (you should have adb drivers installed and stock recovery, sideload will insure you have stock everything)
2- after you successfully sideloaded a full stock rom and make a full boot to system, you can follow the above re-lock instructions.
Click to expand...
Click to collapse
Currently it running oxygen OS from their website like full rom.zip, i know when you flash new recovery you will factory wipe the phone which i don't really wants. Are they like patch to remove boot up warning? because last time i check there wasn't one.
DrUnknownEMC said:
Currently it running oxygen OS from their website like full rom.zip, i know when you flash new recovery you will factory wipe the phone which i don't really wants. Are they like patch to remove boot up warning? because last time i check there wasn't one.
Click to expand...
Click to collapse
A new recovery does not wipe your phone.
There is no patch to remove the boot warning. The only way is to lock boot loader <- this will wipe your phone and data.
If your phone runs well, it is better you keep it as it is. Why fix something that's not broken ?

Stock recovery automatically replace

Goodmorning, I've a strange problem with flashing recovery.
I used lastest fastboot
I've flashed the recovery (fastboot flash...) Then booted into it directly (fastboot boot recovery...) And obviously problems with mounting data.
The real problem is that when I reboot system , twrp is automatically erased and stock recovery is mounted.
I've tried everything, new recovery,new fastboot...
Please help me
That's standard with a lot of OEM ROMS on many different phones. You can flash magisk or SuperSU to preserve your flashed twrp.
sbeaber4 said:
That's standard with a lot of OEM ROMS on many different phones. You can flash magisk or SuperSU to preserve your flashed twrp.
Click to expand...
Click to collapse
That won't work, the no-verity-opt zip is needed to preserve twrp or it will always revert back to the stock one.
Go here
https://forum.xda-developers.com/mi-mix-2/how-to/guide-mi-mix-2-unroot-restore-recovery-t3770690
And DL the TWRP & no-verity-opt-encrypt 1.6
follow the directions starting with
Open a command prompt and verify your device appears in fastboot
Then run
Code:
fastboot flash recovery C:\Twrp__chinese_Android8.img
Click to expand...
Click to collapse
Pitrino said:
Goodmorning, I've a strange problem with flashing recovery.
I used lastest fastboot
I've flashed the recovery (fastboot flash...) Then booted into it directly (fastboot boot recovery...) And obviously problems with mounting data.
The real problem is that when I reboot system , twrp is automatically erased and stock recovery is mounted.
I've tried everything, new recovery,new fastboot...
Please help me
Click to expand...
Click to collapse
- flash latest twrp https://twrp.me/xiaomi/xiaomimimix2.html
- reboot to recovery with hardware keys (volume-up + power) immediately after flashing
That solved the problem for me.

[Recovery][TWRP] Mi 8 Lite TWRP-3.2.3 Multilanguage from 4pda

RECOVERY information:
Name Version: Xiaomi Mi 8 Lite Multilanguage TWRP
Download:
DOWNLOAD
MOD EDIT: Link removed, side is containing warez
How to install:
Fastboot just run .bat file to install it from fastboot mode
TWRP.img can be flashed manually from fastboot
all credits goes to @wzsx150, and poison-74 (4pda)
U know if this is compatible with latest Miui EU rom?
Is data decryptable?
Not entire related to Platina but Mi8 SE users are having trouble with twrp and miui eu.
Thanks.
Have downloaded and installed file recovery.img with twrp, works ok with xiaomi.eu rom.
I have MIUI 10 xiaomi.eu 9.1.10 android 9
lucainno said:
Have downloaded and installed file recovery.img with twrp, works ok with xiaomi.eu rom.
I have MIUI 10 xiaomi.eu 9.1.10 android 9
Click to expand...
Click to collapse
Can you enter in twrp and see if data folder is avalable?
Or it ask a password?
Go recovery no enter password, press cancell .
Before wipe Save All data to PC
(this action wipe All data and internal Memory) Wipe data factory reset and reboot phone
install update recovery.img multilanguage
Please help me, how enter to twrp recovery on Mi8 Lite ? I try all buttons combinations and nothing.
Power of phone
Press Vol + and Power for 5 seconds for enter recovery
Hi guys, I just went from Redmi5 Plus to Mi8 lite, unfortunately I have to wait for the famous 360 hours in the meantime I'm downloading what I need on the R5Plus was available Orange Fox recovery, which automatically decrypted the partitions without having to install lazy Flasch later, here how does this TWRP mod do this?
I would like to install the Xiaomi Eu as soon as I unlock the bootloader I am currently on last Global Stable 10.2.2.0 a help thanks.
It's work on android pie beta global 9.3.1?
this should be a new one:
MOD EDIT: Link removed, side is containing warez
This build does not work with Pie - can someone update the initial post?
excuse me sir, ust want to ask, after flashing twrp 1003 version why after reboot always revert to stock recovery, is there any to fix it, thanks
edit : i already fix it
falqon said:
excuse me sir, ust want to ask, after flashing twrp 1003 version why after reboot always revert to stock recovery, is there any to fix it, thanks
edit : i already fix it
Click to expand...
Click to collapse
Could you please share how you fixed it?
Just upgraded the ROM to 10.3.2.0 and now TWRP recovery always reverted to stock recovery after reboot.
reflash your twrp via adb and when u type "fastboot reboot" press and hold Volume Up until enter twrp, and then try to reboot recovery via twrp. i can't share youtube link, afk right now
falqon said:
reflash your twrp via adb and when u type "fastboot reboot" press and hold Volume Up until enter twrp, and then try to reboot recovery via twrp. i can't share youtube link, afk right now
Click to expand...
Click to collapse
Done this several times, but I didn't use hard buttons, instead i used fastboot boot recovery.img command to reboot to recovery after flashing recovery. I also tried rebooting to recovery from twrp without problem, but after rebooted to system, twrp reverted to stock recovery, everytime.
I didn't have this problem with MIUI 10.3.1.0 with the same TWRP.
edit : I'm using TWRP 0330 btw, and somehow there was no swipe to allow modification confirmation when the phone rebooted to twrp for the 1st time after flashing twrp.
Wonder why.
ne0t said:
Done this several times, but I didn't use hard buttons, instead i used fastboot boot recovery.img command to reboot to recovery after flashing recovery. I also tried rebooting to recovery from twrp without problem, but after rebooted to system, twrp reverted to stock recovery, everytime.
I didn't have this problem with MIUI 10.3.1.0 with the same TWRP.
edit : I'm using TWRP 0330 btw, and somehow there was no swipe to allow modification confirmation when the phone rebooted to twrp for the 1st time after flashing twrp.
Wonder why.
Click to expand...
Click to collapse
check your display panel via device hardware info on playstore, mine is synaptic, not all twrp version work on this panel, i'm using twrp 3.2.3-1003 btw
https://www.youtube.com/watch?v=7eeiSm7rzZY
falqon said:
check your display panel via device hardware info on playstore, mine is synaptic, not all twrp version work on this panel, i'm using twrp 3.2.3-1003 btw
https://www.youtube.com/watch?v=7eeiSm7rzZY
Click to expand...
Click to collapse
Tks, but I don't have problem with TWRP 0330, it works fine, including touch screen, the problem is TWRP get replaced by Stock Recovery everytime I boot my my phone to system.
I don't want to root my phone, just like to have TWRP recovery around so I can use it to flash hosts file for ads blocking and some other things.
Someone told me i need to flash lazyflasher...I'm going to do it later ..
ne0t said:
Tks, but I don't have problem with TWRP 0330, it works fine, including touch screen, the problem is TWRP get replaced by Stock Recovery everytime I boot my my phone to system.
I don't want to root my phone, just like to have TWRP recovery around so I can use it to flash hosts file for ads blocking and some other things.
Someone told me i need to flash lazyflasher...I'm going to do it later ..
Click to expand...
Click to collapse
Boot to recovery through fastboot and then flash the image or the zip through TWRP, then to flash it reboot again to TWRP before to boot up to system.
SubwayChamp said:
Boot to recovery through fastboot and then flash the image or the zip through TWRP, then to flash it reboot again to TWRP before to boot up to system.
Click to expand...
Click to collapse
Tried that too, actually more, boot to recovery from fastboot with fastboot boot recovery.img command and also hard button, boot to recovery from twrp recovery, flash recovery.img, boot to twrp recovery again twice, but stock recovery still came back.
ne0t said:
Tried that too, actually more, boot to recovery from fastboot with fastboot boot recovery.img command and also hard button, boot to recovery from twrp recovery, flash recovery.img, boot to twrp recovery again twice, but stock recovery still came back.
Click to expand...
Click to collapse
No. don´t try to boot to recovery from fastboot after to flash it, don´t flash it through fastboot.
Do the next three steps and see what happens but do it exactly the same or won´t worth the try:
- In fastboot delete recovery partition by typing fastboot erase recovery
- Then reboot to recovery (don´t flash it yet) by typing fastboot boot twrp.img (rename recovery image firstly to twrp)
- Now once in TWRP flash the zip or image to the recovery partition, when you finish go to Reboot options within TWRP and choose recovery to boot to it before to boot up to system. If you boot at this instance to TWRP then the issue have to be solved, reboot normally to system.
Edit: If this way the problem is not solved then after to install TWRP flash Magisk that can prevent it to be overwritten.

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!

Categories

Resources