Trouble flashing TWRP - Moto Z2 Force Questions & Answers

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.

Related

Flash stock recovery

Hi,
i want to return my tablet but before unrooting I want to flash stock recovery. How can I do it? I don't find it anywhere.
Thanks !
http://www.androidfilehost.com/?fid=23060877489996699
Were you able to flash the stock recovery?
I've fasboot flashed it several times and sitll have TWRP.
flar2 said:
Were you able to flash the stock recovery?
I've fasboot flashed it several times and sitll have TWRP.
Click to expand...
Click to collapse
I had this issue on my old Nexus. Erasing the partition before reflashing worked for me. Are you able to flash another custom recovery like CWM over TWRP?
Username invalid said:
I had this issue on my old Nexus. Erasing the partition before reflashing worked for me. Are you able to flash another custom recovery like CWM over TWRP?
Click to expand...
Click to collapse
I didn't try flashing a different recovery. I was going to try using dd to write to the partition.
Do you happen to know which partition the recovery is on?
According to TWRP the partition is:
/dev/block/mmcblk0p25
BTW are you sure your stock recovery img is stock recovery and not twrp masquerading as stock recovery due to some mixup somewhere? where/how did you get your stock recovery img?

No twrp after flashing 3.2.5

I m running on 3.2.6 rooted and with twrp last night i try to flash 3.2.5 community build got an error 7 than i flash any other rom fingreprint scanner stops working after that i read some threads and than i flash 3.2.4 fingreprint works again but when i m trying to flash twrp it booted up with official twrp but after restart it again replace twrp with stock recovery what should i do to get twrp again??
I tried to flash modified twrp but only a blink of black screen and restart.
I tried to flash official twrp from bootloader i select reboot recovery it boots into twrp but it says unable to mount system and after restart it replaced again with stock oss recovery.
I am running on 3.2.4 right now but stuck it on 3.2.4 not able to falsh ota after downloading the ota of 40 mb it gives me some error so please someone helps here how do i get twrp becoz i need root.
rakesh595160 said:
I m running on 3.2.6 rooted and with twrp last night i try to flash 3.2.5 community build got an error 7 than i flash any other rom fingreprint scanner stops working after that i read some threads and than i flash 3.2.4 fingreprint works again but when i m trying to flash twrp it booted up with official twrp but after restart it again replace twrp with stock recovery what should i do to get twrp again??
I tried to flash modified twrp but only a blink of black screen and restart.
I tried to flash official twrp from bootloader i select reboot recovery it boots into twrp but it says unable to mount system and after restart it replaced again with stock oss recovery.
I am running on 3.2.4 right now but stuck it on 3.2.4 not able to falsh ota after downloading the ota of 40 mb it gives me some error so please someone helps here how do i get twrp becoz i need root.
Click to expand...
Click to collapse
Flash full 3.2.6 zip instead
Followed by flashing official twrp
Stop messing up with 3.5.2 (please revise your thread title, 3.2.5 is not 3.5.2)
Or can download flashify and download latest trwp and flash, unless u keep the community build then there is a diff trwp version floating around here
otonieru said:
Flash full 3.2.6 zip instead
Followed by flashing official twrp
Stop messing up with 3.5.2 (please revise your thread title, 3.2.5 is not 3.5.2)
Click to expand...
Click to collapse
How i flash full 3.2.6?? No twrp here
Bradl79 said:
Or can download flashify and download latest trwp and flash, unless u keep the community build then there is a diff trwp version floating around here
Click to expand...
Click to collapse
Flashify only works with root and for root i need twrp so here thats not possible.
rakesh595160 said:
How i flash full 3.2.6?? No twrp here
Click to expand...
Click to collapse
You can boot into twrp without flashing it.
while on OOS 3.2.6 flash the *modified* TWRP and then flash that community build 3.5.2 not 3.2.5. as community build needs that modified twrp to work.. if you wanna revert to other roms.. flash stock OOS 3.2.6 and then flash twrp official and your all good to go..
if you want easy way to get twrp on your phone use that " Tool all in one" it can be found in xda.
Hope that works for you as it worked for me! Cheers!
rakesh595160 said:
I m running on 3.2.6 rooted and with twrp last night i try to flash 3.2.5 community build got an error 7 than i flash any other rom fingreprint scanner stops working after that i read some threads and than i flash 3.2.4 fingreprint works again but when i m trying to flash twrp it booted up with official twrp but after restart it again replace twrp with stock recovery what should i do to get twrp again??
I tried to flash modified twrp but only a blink of black screen and restart.
I tried to flash official twrp from bootloader i select reboot recovery it boots into twrp but it says unable to mount system and after restart it replaced again with stock oss recovery.
I am running on 3.2.4 right now but stuck it on 3.2.4 not able to falsh ota after downloading the ota of 40 mb it gives me some error so please someone helps here how do i get twrp becoz i need root.
Click to expand...
Click to collapse
I'm in this same boat. I am curious if you found an answer. After splash screen my phone will only boot into a black screen. No recovery mode. I've tried reflashing official twrp from fastboot and it says it was successful but phone still wont enter recovery.
kennonk said:
I'm in this same boat. I am curious if you found an answer. After splash screen my phone will only boot into a black screen. No recovery mode. I've tried reflashing official twrp from fastboot and it says it was successful but phone still wont enter recovery.
Click to expand...
Click to collapse
which rom are you on now?
galaxy16 said:
which rom are you on now?
Click to expand...
Click to collapse
I was trying out freedom 1.7, but had recently wiped system to prepare to reinstall another rom when phone stopped booting to recovery. Now I dont have a bootable rom or recovery.
---------- Post added at 05:25 PM ---------- Previous post was at 05:21 PM ----------
kennonk said:
I was trying out freedom 1.7, but had recently wiped system to prepare to reinstall another rom when phone stopped booting to recovery. Now I dont have a bootable rom or recovery.
Click to expand...
Click to collapse
When I flash official twrp in fastboot I get:
target reported max download size of 442499072 bytes
sending 'recovery' (18964 KB)...
OKAY [ 0.506s]
writing 'recovery'...
OKAY [ 0.147s]
finished. total time: 0.653s
But it still won't go into recovery. I guess I am going to have to find a windows PC and use the unbrick tool unless anyone has a suggestion.
kennonk said:
I was trying out freedom 1.7, but had recently wiped system to prepare to reinstall another rom when phone stopped booting to recovery. Now I dont have a bootable rom or recovery.
---------- Post added at 05:25 PM ---------- Previous post was at 05:21 PM ----------
When I flash official twrp in fastboot I get:
target reported max download size of 442499072 bytes
sending 'recovery' (18964 KB)...
OKAY [ 0.506s]
writing 'recovery'...
OKAY [ 0.147s]
finished. total time: 0.653s
But it still won't go into recovery. I guess I am going to have to find a windows PC and use the unbrick tool unless anyone has a suggestion.
Click to expand...
Click to collapse
Dont flash official twrp, flash the modified twrp.. Flash to OOS 326 or 324.. Then flash official twrp and your good to go..
galaxy16 said:
Dont flash official twrp, flash the modified twrp.. Flash to OOS 326 or 324.. Then flash official twrp and your good to go..
Click to expand...
Click to collapse
That got me back to working recovery...thank you very much
So if I want to go back to official at some point is there a way?
kennonk said:
That got me back to working recovery...thank you very much
So if I want to go back to official at some point is there a way?
Click to expand...
Click to collapse
happy to help! yes you can get back to official twrp after flashing oos 3.2.4 or 3.2.6.. because for the community build 3.5.2 only that modded twrp will work..
rakesh595160 said:
How i flash full 3.2.6?? No twrp here
Click to expand...
Click to collapse
fastboot boot recovery yourtwrpnamehere.img
then flash your 3.2.6 then
fastboot flash recovery yourtwrpnamehere.img
otonieru said:
fastboot boot recovery yourtwrpnamehere.img
then flash your 3.2.6 then
fastboot flash recovery yourtwrpnamehere.img
Click to expand...
Click to collapse
Can somebuddy give me the link to the modified recovery the one i download is only showing black screen nothing comes after that so need the perfect one.
rakesh595160 said:
Can somebuddy give me the link to the modified recovery the one i download is only showing black screen nothing comes after that so need the perfect one.
Click to expand...
Click to collapse
Check on the blu_sp*rk kernel thread.
I have this same problem...
I flashed the community build (3.5) and can now no longer boot into TWRP. I attempted to flash it this way...
Placed recovery in tools folder (with fastboot and adb etc.) and opened a command window. I typed fastboot flash recovery recovery.img and it flashes fine, but when I boot I get the splash screen and then nothing. What am i doing wrong? I have tried both official and modded TWRP.
Same thing happens with me no modded one works for me too.
In 3.2.6 when we try to flash any other rom it will break the fingreprint scanner dont know why both the update these problems hope the will fix them soon.

[RR Rom 5.7.4 20161113] Bootloop at starting apps

Hi everyone!
I was on RR 5.7.3. Rooted, unlocked bootloader on 9th July when I was on 3.2.0 or something.
I wanted to install the new 5.7.4 and it required some 3.5.5 CB FW files so I followed this guide:
Download list:
Latest ResurrectionRemix ROM (EX kernel)
OpenGapps 6.0 ARM64
OOS 3.5.5-CE Firmware + Modem
Modified TWRP 3.0.2-22 Recovery
Update instructions (from build 20161008)
1) Create a backup
2) Wipe system + cache + dalvik cache
3) Flash ROM + GApps + OOS 3.5.5 FW/Modem
4) Reboot
5) Flash TWRP 3.0.2-22 via Flashify
6) Done.
Click to expand...
Click to collapse
Installation seems went fine, it installed 143 GAPPS, then it asked me for password to decrypt then it continued installing 28 Google apps (dialer, gnow app etc.). It sometimes vibrates and then again it continues to install those 28 Gapps.
I tried to turn it off: it asks me for password to decrypt, then RR logo is moving, then Optimizing those 28 apps, then "starting apps" and now again the RR logo loading, then optimizing 28 apps, then "starting apps" and again and again in a continuous loop.
Cant' access TWRP obviously, so I decided to boot in fastboot to reinstall twrp:
Code:
sending 'recovery' (18964 KB)...
OKAY [ 0.533s]
writing 'recovery'...
OKAY [ 0.146s]
finished. total time: 0.680s
But again, can't access TWRP. When i choose to boot in recovery it gives me a black screen.
Can anyone help me?
My Problem seems to be similar to yours:
Since flashing CM 14.1 I can't bot into recovery too, get the same black screen. At least I can boot into CM 14.1
Should you find a way to fix the recovery issue, could you tell me how?
jcgruenhage said:
My Problem seems to be similar to yours:
Since flashing CM 14.1 I can't bot into recovery too, get the same black screen. At least I can boot into CM 14.1
Should you find a way to fix the recovery issue, could you tell me how?
Click to expand...
Click to collapse
Yeah!
I found a solution to have twrp back, but I don't know if it can work for you. Try!
Download TWRP 3.0.2-22
So use fastboot to install twrp, there are hundreds guides on google!
EDIT: If you can boot in CM14 i think you could install TWRP img from Flashify! I think it's easier
Blacksyrium said:
Yeah!
I found a solution to have twrp back, but I don't know if it can work for you. Try!
Download TWRP 3.0.2-22
So use fastboot to install twrp, there are hundreds guides on google!
EDIT: If you can boot in CM14 i think you could install TWRP img from Flashify! I think it's easier
Click to expand...
Click to collapse
I tried 3 different TWRP images, but not that one I will try that now ^^
Flashify: Daily limit of 3 flashes reached, buy premium.
Booting via fastboot works though, THANKS A LOT !!
jcgruenhage said:
I tried 3 different TWRP images, but not that one I will try that now ^^
Flashify: Daily limit of 3 flashes reached, buy premium.
Booting via fastboot works though, THANKS A LOT !!
Click to expand...
Click to collapse
hehe! Good bro!
Guys, for those of you who has black screens - try to flash the modified TWRP with ADB - it works perfect

Can't install TWRP

I can't get TWRP to install on my phone. I've tried manually fastbooting all three TWRP images that are available from the TWRP website. I tried installing TWRP using the Skipsoft Toolkit. Whatever I do I never get past the TWRP splash screen--no menus ever come up. Since no menus ever come up I can't install the TWRP zip or a custom ROM. I've been trying this for hours and it's driving me crazy. Is there a different procedure to boot into temporary TWRP if you are on the June bootloader? Is there another version of the TWRP image file that I'm missing? Am I supposed to let the TWRP sit there for a really long time? This is driving me completely batty.
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
pcriz said:
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
Click to expand...
Click to collapse
I did. Will give that a try. Thanks.
pcriz said:
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
Click to expand...
Click to collapse
That did the trick! Thanks.
jhs39 said:
That did the trick! Thanks.
Click to expand...
Click to collapse
Np
It took way too long but I installed TWRP, flashed DU, installed ElementalEx, rooted with custom Magisk for Pixel and got the phone to pass Safety Net. Everything seems to be working. However, whenever I go into recovery TWRP doesn't seem to be there. I appear to get the stock recovery which I don't understand. I can still boot into temporary TWRP and flash the TWRP zip and flash other zips on my phone but I can't seem to boot directly into TWRP. Is this normal or did I do something wrong somewhere?
jhs39 said:
It took way too long but I installed TWRP, flashed DU, installed ElementalEx, rooted with custom Magisk for Pixel and got the phone to pass Safety Net. Everything seems to be working. However, whenever I go into recovery TWRP doesn't seem to be there. I appear to get the stock recovery which I don't understand. I can still boot into temporary TWRP and flash the TWRP zip and flash other zips on my phone but I can't seem to boot directly into TWRP. Is this normal or did I do something wrong somewhere?
Click to expand...
Click to collapse
If I recall correctly, after flashing any rom you have to flash twrp again before rebooting. Apparently roms flash an img to our recovery partition that looks similar to a modified CWM.
noidea24 said:
If I recall correctly, after flashing any rom you have to flash twrp again before rebooting. Apparently roms flash an img to our recovery partition that looks similar to a modified CWM.
Click to expand...
Click to collapse
I actually did that. Maybe I was supposed to boot into the rom once, then back into recovery to flash TWRP. There are a lot of different flashing instructions for this phone. It's hard to keep it all straight.
jhs39 said:
I actually did that. Maybe I was supposed to boot into the rom once, then back into recovery to flash TWRP. There are a lot of different flashing instructions for this phone. It's hard to keep it all straight.
Click to expand...
Click to collapse
Booting into the rom, going back into temp TWRP and flashing the TWRP zip seems to have worked --TWRP actually stuck this time and I can boot directly into it now. It's a shame Google made the Pixel XL such a headache to flash on.

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