Need help. I have zenfone 5z, my device is working properly, the bootloader is unlocked, and the phone is rooted but I'm not able to get TWRP I'm getting two errors,
1. When using fastboot boot C:\Android\platform-tools\twrp-3.6.2_11-0-Z01RD.img, I'm getting FAILED (remote: 'unknown command').
2. When using fastboot flash recovery C:\Android\platform-tools\twrp-3.6.2_11-0-Z01RD.img, I'm getting FAILED (remote: '(recovery_b) No such partition').
Initially, I was able to boot into TWRP but I didn't understand a few things at that time, so I lost TWRP as it was not permanent. Now, I have tried everything except using a different computer.
Someone had this same issue he resolved it after installing the driver a second time, when the device in bootloader, but it didn't work for me.
I think this is related to partition, but I don't know much about it. So, I flashed stock ROM (factory version) but no result.
I'm very much interested in using Custom ROMs any help would be appreciated.
Klyntar said:
Need help. I have zenfone 5z, my device is working properly, the bootloader is unlocked, and the phone is rooted but I'm not able to get TWRP I'm getting two errors,
1. When using fastboot boot C:\Android\platform-tools\twrp-3.6.2_11-0-Z01RD.img, I'm getting FAILED (remote: 'unknown command').
2. When using fastboot flash recovery C:\Android\platform-tools\twrp-3.6.2_11-0-Z01RD.img, I'm getting FAILED (remote: '(recovery_b) No such partition').
Initially, I was able to boot into TWRP but I didn't understand a few things at that time, so I lost TWRP as it was not permanent. Now, I have tried everything except using a different computer.
Someone had this same issue he resolved it after installing the driver a second time, when the device in bootloader, but it didn't work for me.
I think this is related to partition, but I don't know much about it. So, I flashed stock ROM (factory version) but no result.
I'm very much interested in using Custom ROMs any help would be appreciated.
Click to expand...
Click to collapse
fastboot flash boot
not recovery
Related
Hello,
I bought a htc one x, these days
But it already came with root system and modified, used for 2 days
the unit began to reset itself, and no longer start, was stopped at HTC screen
so I tried to go into bootloader mode, to access recovery mode
but without success, I go into recovery and nothing happens
already tried to flash TWRP and CWM in several different versions, but nothing
the number of errors (fastboot flash recovery recovery.img)
FAILED (remote: not allowed)
FAILED (remote: (00000008))
FAILED (remote: (00120000))
I do not know what to do :/
because with the recovery mode could recover or via Recovery Update
THANKKS!!
Unlock the bootloader !
Mr Hofs said:
Unlock the bootloader !
Click to expand...
Click to collapse
my bootloader is already unlocked
Remote not allowed message is because it's relocked.....usually. if it's unlocked it should work
I finally got around to rooting/etc my Z00AD, only to get stuck at the custom recovery stage.
I have found a dozen other identical cases on the forums, but sadly none have been resolved.
Rooting went swimmingly, and my bootloader also unlocked flawlessly (I believe). The new recovery (TWRP first) flashed over with no issues. Then I rebooted and selected 'recovery' from the fastboot menu, and the phone just reboots back into the fastboot stage. I can boot normally from there, just not to recovery. I have also tried flashing other recoveries, with no luck.
Since the ROM is still stock, I can boot to Android and it re-writes the recovery to stock after my custom recovery fails to boot.
My thoughts are that my bootloader did not unlock properly, even though installation itself seemed to go well. How should I 'redo' that process?
Any other thoughts?
FW Vers. WW Z00AD 2.20.40.195
Thanks everyone
Either reflash the correct recovery (download a fresh file, in case of faulty download) or follow unbricking instructions.
Verstuurd vanaf mijn ASUS_Z00A met Tapatalk
ztoundas said:
I finally got around to rooting/etc my Z00AD, only to get stuck at the custom recovery stage.
I have found a dozen other identical cases on the forums, but sadly none have been resolved.
Rooting went swimmingly, and my bootloader also unlocked flawlessly (I believe). The new recovery (TWRP first) flashed over with no issues. Then I rebooted and selected 'recovery' from the fastboot menu, and the phone just reboots back into the fastboot stage. I can boot normally from there, just not to recovery. I have also tried flashing other recoveries, with no luck.
Since the ROM is still stock, I can boot to Android and it re-writes the recovery to stock after my custom recovery fails to boot.
My thoughts are that my bootloader did not unlock properly, even though installation itself seemed to go well. How should I 'redo' that process?
Any other thoughts?
FW Vers. WW Z00AD 2.20.40.195
Thanks everyone
Click to expand...
Click to collapse
Have you tried booting into fastboot and typing "fastboot oem device-info" without the quotes? It should tell you whether your bootloader is truly unlocked. If it is unlocked I would boot into stock recovery, wipe the cache, and do a factory reset. Then you can try installing twrp again. Have you updated the SuperSu binaries? I'm no expert this is just what I would do.
Same problem here, it seems that 2.20.40.195 is the problem.
I can also do fastboot flash but anything but official recovery won't start and returns to bootloader. fastboot oem device-info returns FAILED (remote: unknown OEM command)
.
Is it possible to downgrade?
willcall said:
Have you tried booting into fastboot and typing "fastboot oem device-info" without the quotes? It should tell you whether your bootloader is truly unlocked.
Click to expand...
Click to collapse
....aaand it wasn't truly unlocked. While I didn't test it using your method, before reading your response I tried re-unlocking the bootloader, and I got the proper white background upon reboot (last attempt I flashed the original black background immediately after I thought I had unlocked the bootloader, thinking it was required. Thus I never had a repeated confirmation I had failed the unlocking).
After ACTUALLY unlocking the bootloader, each further step worked perfect. Running CM13 flawlessly.
2 days later I shattered my screen. oh well. Ordered a new screen, we'll see how I do with a hardware repair...
Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Hi McBad,
you could try the following. I also had some problems to access the recovery.
- Again bring the phone into fastboot, flash the 2.8 recovery and access it
- Do a wipe for factory reset, not just only cache
- after that try to flash the twrp-3.0.1-0-m8ql.img version, the other one worked for me neither
- the try to install the custom ROM LOS13
I hope this will help you.
clone
It would be great if that would work, but flashing a recovery does not work. I flash it, success message, try to access it, vibrates and bootloader pops back instantly. That is the problem.
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Have you tried sideloading twrp ?
McBad said:
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Click to expand...
Click to collapse
Did you use HTC fastboot ?
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Is there any way you could flash twrp 2.8 again? Once in that recovery you have sideloading option which you could use to transfer latest recovery onto your device. Are we talking about the same process?
McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Sideload as follows ....
McBad said:
Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Click to expand...
Click to collapse
You can't install lineage if you haven't upgraded your device with latest official update. I would try reinstaling twrp 2.8, do a wipe of cache, dalvik cache and system, Sideload CM 12; and see how it goes. As well, while in twrp I would try relocking bootloader but only after an unsuccessful attempt to flash said rom. I don't know what your experience with soft bricked devices is, but sometimes it takes a while, different usb cable or usb slot on your PC, correct files in adb folder, re-download of rom or recovery because it easily gets corrupted while downloading. And obviously a fully charged device. Let us know how it goes.
I'm having trouble flashing TWRP on my device. Bootloader is unlocked and I can boot TWRP and use it fully, but when I attempt to flash it onto my recovery partition, it can't find that partition. I get the following error:
PS C:\platform-tools> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (26700 KB)...
OKAY [ 0.563s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.563s
Any help is appreciated.
dave31g said:
I'm having trouble flashing TWRP on my device. Bootloader is unlocked and I can boot TWRP and use it fully, but when I attempt to flash it onto my recovery partition, it can't find that partition. I get the following error:
PS C:\platform-tools> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (26700 KB)...
OKAY [ 0.563s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.563s
Any help is appreciated.
Click to expand...
Click to collapse
Recovery is now in boot. You cannot flash the img. If you do, you'd be in some trouble. Flash the installer zip from the booted twrp.
Uzephi said:
Recovery is now in boot. You cannot flash the img. If you do, you'd be in some trouble. Flash the installer zip from the booted twrp.
Click to expand...
Click to collapse
Thanks. So just to be clear, put the twrp zip on my phone then flash that using my booted twrp?
dave31g said:
Thanks. So just to be clear, put the twrp zip on my phone then flash that using my booted twrp?
Click to expand...
Click to collapse
Yes
I'd like some direction on this as well. I attempted to flash the installer from booted twrp and ended up with the phone only booting into twrp and not going through the regular boot process. This in turn started a **** storm of issues when I tried fix it that lasted for a few days(restored my backup to wrong partition). Thanks to @Kaesberg I did get my phone back in working order and can once again boot into twrp from the bootloader. I would however like some direction on flashing twrp to the phone.
27.1 Tmo
Edit:. Can you tell me which twrp you are flashing, and in the booted twrp do I need to be on a particular partition before flashing,? Do I need to mount anything? Or wipe?
mr.duck254 said:
I'd like some direction on this as well. I attempted to flash the installer from booted twrp and ended up with the phone only booting into twrp and not going through the regular boot process. This in turn started a **** storm of issues when I tried fix it that lasted for a few days(restored my backup to wrong partition). Thanks to @Kaesberg I did get my phone back in working order and can once again boot into twrp from the bootloader. I would however like some direction on flashing twrp to the phone.
27.1 Tmo
Edit:. Can you tell me which twrp you are flashing, and in the booted twrp do I need to be on a particular partition before flashing,? Do I need to mount anything? Or wipe?
Click to expand...
Click to collapse
You might be on a different slot after flashing TWRP. At the reboot screen in TWRP try selecting a different slot and see what happens. If it is booting on a different slot that is set to run everything it will boot loop.
Hmm still can't get it flashed to the phone this way. After booting twrp then flashing the zip, same issue. I see the zip say it is flashing to slot a. Rebooting to part a is just a constant boot into twrp. Switching to booting to part b is just a constant unlocked bootloader warning screen boot loop. Have to flashall and start over to get out of it. Any other suggestions? I'm on the pantheon kernel and am trying the twrp 3.2.1.1 if that helps.
JAWheat411 said:
You might be on a different slot after flashing TWRP. At the reboot screen in TWRP try selecting a different slot and see what happens. If it is booting on a different slot that is set to run everything it will boot loop.
Click to expand...
Click to collapse
mr.duck254 said:
Hmm still can't get it flashed to the phone this way. After booting twrp then flashing the zip, same issue. I see the zip say it is flashing to slot a. Rebooting to part a is just a constant boot into twrp. Switching to booting to part b is just a constant unlocked bootloader warning screen boot loop. Have to flashall and start over to get out of it. Any other suggestions? I'm on the pantheon kernel and am trying the twrp 3.2.1.1 if that helps.
Click to expand...
Click to collapse
I am wondering if it is trying to boot a room that isn't there. I have seen that happen after system gets wiped. You might have to run the flash all again and start over. I know the T-Mobile one was posted.
If this TWRP image was flashed something might have screwed up. You can't flash this image like other devices.
What I did was use the flash all.
Set everything up.
Boot to TWRP in bootloader. ( do not flash )
Now flash the TWRP zip in recovery.
Reboot to recovery.
Flash magisk.
Ok I'll try again step by step. If it doesn't work maybe I can change the installer zip to use the b partition rather than a and see if that helps. Yes magisks, the kernel, Xposed. Everything else works beatifully till I try to actally flash twrp. Here we go again ?. You are using the twrp 3.2.1.1 correct?
JAWheat411 said:
I am wondering if it is trying to boot a room that isn't there. I have seen that happen after system gets wiped. You might have to run the flash all again and start over. I know the T-Mobile one was posted.
If this TWRP image was flashed something might have screwed up. You can't flash this image like other devices.
What I did was use the flash all.
Set everything up.
Boot to TWRP in bootloader. ( do not flash )
Now flash the TWRP zip in recovery.
Reboot to recovery.
Flash magisk.
Click to expand...
Click to collapse
mr.duck254 said:
Ok I'll try again step by step. If it doesn't work maybe I can change the installer zip to use the b partition rather than a and see if that helps. Yes magisks, the kernel, Xposed. Everything else works beatifully till I try to actally flash twrp. Here we go again ?. You are using the twrp 3.2.1.1 correct?
Click to expand...
Click to collapse
Yes that is correct. Booting the TWRP image from their site and flashing the TWRP zip also from their site.
Worked beautifully. I don't know where I was screwed up, But I'm flashed and running smooth as butter now. Thanks for the help bro.
JAWheat411 said:
Yes that is correct. Booting the TWRP image from their site and flashing the TWRP zip also from their site.
Click to expand...
Click to collapse
encryption
Hello my friends, I have a serious problem with my Z2 force, I can not remove the encryption, although I have already searched a lot of forums, tried some zip files via twrp, I did not get any success, if someone could give me a direction, I I would be grateful.
Sorry if the post was on the wrong topic.
Once again I'm sorry for the bad english.
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!