Okay, lemme get this clear that I'm not a pro in all this stuff. Infact, I'm a total idiot.
I have tried to flash a lot of ROMs on my Moto G5 (cedric) but only 3 of them have worked, namely:
1) Pixel Expirience 7.1.2
2) Ressurection Remix 7.1.2
3) Viper OS 7.1.2
I don't know whats the problem and whether it is with my phone or the ROMs. Also, even after i used these ROMs, the apps which need root access weren't working and yes i did select the Root Access setting to ADB only(cause thats was the only option other than Off). Plz help me guys.....
Astitva_ said:
Okay, lemme get this clear that I'm not a pro in all this stuff. Infact, I'm a total idiot.
I have tried to flash a lot of ROMs on my Moto G5 (cedric) but only 3 of them have worked, namely:
1) Pixel Expirience 7.1.2
2) Ressurection Remix 7.1.2
3) Viper OS 7.1.2
I don't know whats the problem and whether it is with my phone or the ROMs. Also, even after i used these ROMs, the apps which need root access weren't working and yes i did select the Root Access setting to ADB only(cause thats was the only option other than Off). Plz help me guys.....
Click to expand...
Click to collapse
First you need to say how you have done the flashing of roms and which rom didn't flash, or what error you got while installing the rom. And second is you need to install magisk manager to gain root access with twrp, by enabling the root access in developer option won't give you root access you need to install it via twrp.
riyan65 said:
First you need to say how you have done the flashing of roms and which rom didn't flash, or what error you got while installing the rom. And second is you need to install magisk manager to gain root access with twrp, by enabling the root access in developer option won't give you root access you need to install it via twrp.
Click to expand...
Click to collapse
I tried flashing them through TWRP. They all were based on Oreo 8.1. I tried Lineage, Invicta, Viper, RR and pixel expirience. As for the error, i don't really know what error it was but Lineage and RR were stuck on the boot loader and the rest just didnt flash.....
Astitva_ said:
I tried flashing them through TWRP. They all were based on Oreo 8.1. I tried Lineage, Invicta, Viper, RR and pixel expirience. As for the error, i don't really know what error it was but Lineage and RR were stuck on the boot loader and the rest just didnt flash.....
Click to expand...
Click to collapse
Chance are you are using the wrong twrp
64bit roms require you to use the 64bit twrp
See the first post of the lineageos thread for the 64bit twrp
Or you can test out the 64bit twrp that uses my encryption edits
https://forum.xda-developers.com/g5/help/help-testing-build-twrp-arm64-t3874472
If you want to root flash the latest version of Magisk and then install the magisk manager app manually if it's not installed
TheFixItMan said:
Chance are you are using the wrong twrp
64bit roms require you to use the 64bit twrp
See the first post of the lineageos thread for the 64bit twrp
Or you can test out the 64bit twrp that uses my encryption edits
https://forum.xda-developers.com/g5/help/help-testing-build-twrp-arm64-t3874472
If you want to root flash the latest version of Magisk and then install the magisk manager app manually if it's not installed
Click to expand...
Click to collapse
I'm sorry but i didn't get what you said. I'm really sorry but I'm really a noob. I would like it if you helped me out a bit....
Astitva_ said:
I'm sorry but i didn't get what you said. I'm really sorry but I'm really a noob. I would like it if you helped me out a bit....
Click to expand...
Click to collapse
All custom oero roms for this device are 64 bit
You need to flash them with a twrp that has been compiled for 64bit twrp use
My official twrp is for 32bit roms only and will not flash 64bit roms - you will get error 7 or I think error 256 or something like that
Flash the 64bit twrp if you want to flash 64bit custom roms - process is the same as if flashing the official twrp via fastboot but you obviously use the 64bit twrp image instead
As mentioned link to 64bit twrp is on the lineageos 15.1 thread first page or try the version in the link I posted in previous post
TheFixItMan said:
All custom oero roms for this device are 64 bit
You need to flash them with a twrp that has been compiled for 64bit twrp use
My official twrp is for 32bit roms only and will not flash 64bit roms - you will get error 7 or I think error 256 or something like that
Flash the 64bit twrp if you want to flash 64bit custom roms - process is the same as if flashing the official twrp via fastboot but you obviously use the 64bit twrp image instead
As mentioned link to 64bit twrp is on the lineageos 15.1 thread first page or try the version in the link I posted in previous post
Click to expand...
Click to collapse
So, I can directly flash the new twrp like i flash the roms right?? Also, what can i do for project treble in my phone...i mean, i cant find redwolf for moto g5(cedric)
Astitva_ said:
So, I can directly flash the new twrp like i flash the roms right?? Also, what can i do for project treble in my phone...i mean, i cant find redwolf for moto g5(cedric)
Click to expand...
Click to collapse
You flash twrp via fastboot commands
fastboot flash recovery recovery.img
Although it is technically possible to flash twrp via twrp if you select image flash & select recovery as the image you are flashing but I'd stick with the fastboot method
I don't own this device anymore so no idea about files that are no longer available
TheFixItMan said:
You flash twrp via fastboot commands
fastboot flash recovery recovery.img
Although it is technically possible to flash twrp via twrp if you select image flash & select recovery as the image you are flashing but I'd stick with the fastboot method
I don't own this device anymore so no idea about files that are no longer available
Click to expand...
Click to collapse
Okay, so i flashed the twrp...but still therom isnt flashing....should i upload the rom so that you can see it?
basically;
if a rom has [64bit] in the title, then it's 64 bit, if it is then you need a 64bit recovery which you can easily find on the forum. you dont even need to know what that means.
Astitva_ said:
Okay, so i flashed the twrp...but still therom isnt flashing....should i upload the rom so that you can see it?
Click to expand...
Click to collapse
Just link to the rom on xda and give the twrp error
The rom either isn't for this device eg you are trying to flash a moto g5 plus or s rom or you are using the wrong twrp or you haven't formatted system data cache before flashing the rom
Related
Hello my friends, I'm new here and I have some problems with my device moto G5 xt1670, actually I unlocked the bootloader and intalled the TWRP 64 bit for install some rom 8.1.0 but when I installed that TWRP my device's brick, actually I solve that problem and I want to install a Rom for my device plis help me with some rom and twrp for my device plisssss
You do not give very clear information, Did you want to format? Have you formatted/Wiped your device yet? Can you boot to TWRP 64?, If you were going into this thinking you wont need to format, It'll be hard buddy, If you did wipe everything AND formatted data, make sure that happened! Connect your phone to PC through a Data cable (official USB cable recommended), and put your custom ROM, Now if you go to install you should see a lonely file that is your ROM, unless you put GAPPS zip file too, enjoy.
also, if you do not have TWRP, Or you cannot boot, try going back to bootloader, connect phone to PC with the USB, open CMD in fastboot folder, and type "fastboot flash recovery (you can drag the recovery file to the CMD)", let us say the file is in your ADB/Fastboot folder, then you can just type "fastboot flash recovery twrp.img" which i assume twrp.img is the file's name, Take note that you remove the quotes when actually typing it
Thanks so much for your answer dude, I'm not very good with my english, but I know how install a rom, my problem is the TWRP, when I installed the TWRP 64bit my device don't running again, I think that TWRP is not compatible with my device. I'd like to know that TWRP is the right one for my device, if you could help bro, I would be very grateful. I'd also like to know what rom I can install, since the 64 bit ones do not work for me
SARFACE said:
Thanks so much for your answer dude, I'm not very good with my english, but I know how install a rom, my problem is the TWRP, when I installed the TWRP 64bit my device don't running again, I think that TWRP is not compatible with my device. I'd like to know that TWRP is the right one for my device, if you could help bro, I would be very grateful. I'd also like to know what rom I can install, since the 64 bit ones do not work for me
Click to expand...
Click to collapse
Obviously if you flash the 64bit twrp your stock rom will no longer boot (unless you disable dm-verity)
Obviously the twrp is compatible if twrp loads
And of course make sure that the rom you are installing is 64bit - if not use the official 32bit version of twrp
The process is the same for flashing any rom (unless otherwise stated)
Format data if you have encryption enabled & reboot to recovery
Advance wipe
Wipe system data cache art/devik cache
Flash rom zip
Flash gapps (optional make sure it's right version)
Flash magisk (optional if you want to root)
Wipe delvik/art cache
Restart
Some roms you may have to disable welcome screen to boot or install slightly different
Read the thread
TheFixItMan said:
Obviously if you flash the 64bit twrp your stock rom will no longer boot (unless you disable dm-verity)
Obviously the twrp is compatible if twrp loads
And of course make sure that the rom you are installing is 64bit - if not use the official 32bit version of twrp
The process is the same for flashing any rom (unless otherwise stated)
Format data if you have encryption enabled & reboot to recovery
Advance wipe
Wipe system data cache art/devik cache
Flash rom zip
Flash gapps (optional make sure it's right version)
Flash magisk (optional if you want to root)
Wipe delvik/art cache
Restart
Some roms you may have to disable welcome screen to boot or install slightly different
Read the thread
Click to expand...
Click to collapse
That means that if I can install the 64 bit TWRP on my device even if it is ARM ?, if so could you give me a guide on how to install the 64 bit TWRP without error of the rom stock (which does not start after to install the TWRP), I appreciate your time, I will be aware of your response, thanks.
SARFACE said:
That means that if I can install the 64 bit TWRP on my device even if it is ARM ?, if so could you give me a guide on how to install the 64 bit TWRP without error of the rom stock (which does not start after to install the TWRP), I appreciate your time, I will be aware of your response, thanks.
Click to expand...
Click to collapse
Like I said - only use 64bit twrp with 64bit roms
Stock rom on this device is NOT 64bit so use the official 32bit twrp
If you want to use a 64bit look in the Dev section for 64bit custom roms
Full instructions are on the official twrp thread in the Dev section
This applies to the flashing of any recovery - the process is the same
Also read the faqs of the official twrp thread as your question regarding booting stock rom once you have flashed twrp is answered there
The official twrp is 32bit - you will not be able to flash 64bit roms with it hence you need to use the unofficial 64bit twrp if you plan to flash a 64bit rom
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
TheFixItMan said:
Like I said - only use 64bit twrp with 64bit roms
Stock rom on this device is NOT 64bit so use the official 32bit twrp
If you want to use a 64bit look in the Dev section for 64bit custom roms
Full instructions are on the official twrp thread in the Dev section
This applies to the flashing of any recovery - the process is the same
Also read the faqs of the official twrp thread as your question regarding booting stock rom once you have flashed twrp is answered there
The official twrp is 32bit - you will not be able to flash 64bit roms with it hence you need to use the unofficial 64bit twrp if you plan to flash a 64bit rom
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
Click to expand...
Click to collapse
Thx so much for your answer dude, actually I installed the TWRP 32 bits 2 weeks ago and 1 ROM viper 7.1.2 and works perfectly but I need Oreo jajajaja x) Thank you, you solved many doubts
after I installed magisk I can not install any rom custom the only rom that works and the backup I made in twrp of the official rom
Does anyone know how to solve it?
I do not really understand what you are saying here, just wipe everything in twrp and flash rom. Magisk cannot survive a wipe.
What do I do to get back ROM with these errors?
I already did this I cleaned everything in twrp no more rom installs of the error 7 and also of the error in the fastboot to return stock rom error in the bootloader and the original recovery does not install also as if it did not have space .... the twrp has approximately 16mb and the recovery stock has 20mb and only recovery with 16mb
cleberkorg said:
I already did this I cleaned everything in twrp no more rom installs of the error 7 and also of the error in the fastboot to return stock rom error in the bootloader and the original recovery does not install also as if it did not have space .... the twrp has approximately 16mb and the recovery stock has 20mb and only recovery with 16mb
Click to expand...
Click to collapse
Twrp for our device is 15/16mb. Are you sure you have the 64 bit twrp? That would give error 7 if using standard release of twrp with the now 64bit ROMs.
continues to give error 7
I already tested several twpr of 64bits more anyway it continues to give error 7
I would fastboot flash the stock rom again. Back up storage first because it will be wiped.
Cupcake 1.5 said:
Twrp for our device is 15/16mb. Are you sure you have the 64 bit twrp? That would give error 7 if using standard release of twrp with the now 64bit ROMs.
Click to expand...
Click to collapse
my moto z2 play is working because I backed up by twrp my problem and the following when I try to install any custom rom it of the error in twrp in both x86 and x64 of the error and how much I try to install the stock rom by the error fastboot in the boot and no recovery all rom stock oreo the recovery is with 20megas and not for this reason ..... besides these problem every time I reboot the device connect direct by recovery ai I have to boot through fastboot and click on start for the android link
cleberkorg said:
my moto z2 play is working because I backed up by twrp my problem and the following when I try to install any custom rom it of the error in twrp in both x86 and x64 of the error and how much I try to install the stock rom by the error fastboot in the boot and no recovery all rom stock oreo the recovery is with 20megas and not for this reason ..... besides these problem every time I reboot the device connect direct by recovery ai I have to boot through fastboot and click on start for the android link
Click to expand...
Click to collapse
I can not make blankflash have any tutorials? I can not install the driver cualcomm how does the procedure?
cleberkorg said:
I can not make blankflash have any tutorials? I can not install the driver cualcomm how does the procedure?
Click to expand...
Click to collapse
I have no information on making blank flash but, there should be something on it in the q&a or guide part of this forum.
I used to be on resurrection remix 7.1.2, but I flashed stock ROM so I could do a clean flash with another ROM. I used Xiaomi unlock tool to unlock bootloader again, then flashed TWRP thru ADB in fastboot. After that I went into recovery, wipe data,cache etc and tried to flash dotos 3.0, but it gave me error 7. I repeated same process with zirconium android 9.0, same thing I'm using latest TWRP, y do I get error 7?? I definitely have the right model etc
Hey mate, have you tried using a vendor based custom recovery? . Is your Twrp vendor based? ( you'll be able to see cust/vendor partition in the advanced wipe menu).
I was messing around today with Dot0s 3.0 and regular Twrp too and found out that i couldn't install any pie roms on regular Twrp. I was previously using batik recovery. So you might be able to flash on it. Let me know if you try it.
Edit : I got the same error 7 on pretty much all oreo and pie roms.
jeevan bk said:
Hey mate, have you tried using a vendor based custom recovery? . Is your Twrp vendor based? ( you'll be able to see cust/vendor partition in the advanced wipe menu).
I was messing around today with Dot0s 3.0 and regular Twrp too and found out that i couldn't install any pie roms on regular Twrp. I was previously using batik recovery. So you might be able to flash on it. Let me know if you try it.
Edit : I got the same error 7 on pretty much all oreo and pie roms.
Click to expand...
Click to collapse
Ah, thanks man. I've been only using regular TWRP, I'll use batik in a bit
Flash old firmware and then upgrade
Arathergreendroid said:
Ah, thanks man. I've been only using regular TWRP, I'll use batik in a bit
Click to expand...
Click to collapse
Flashing Nougat firmware first and then custom recovery worked.
See https://forum.xda-developers.com/xiaomi-redmi-5a/how-to/rollback-downgrade-to-miui-nougat-t3938904
This is work for me.. just extract your cusrom and then go to Meta-Inf > google , edit the updater script. and delete line "get prop ......." all of that line.
so the first line must " ui_print ("Target: ........"); "
save
and select all files from your cusrom, create zip, copy to sd card, install via Recovery
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!
Hi, I got myself an used Motorola Moto G7 play (XT1952-1) with Android 10 Stock update (Build QPYS30.52-22-8-9) and just can't successfully install TWRP on it. What I did:
- Bootloader unlocked
- TWRP temporary loaded with fastboot (fastboot boot twrp.img)
- In TWRP 'Iinstall' selected the matching TWRP .zip and it said it was installed in both slots a and b.
But then, when I select 'restart to bootloader' and try to launch recovery, I get a bootloop (black screen with (N/A) in the top left corner. The OS as such still starts normally. So I guess the main problem here is the bootloop when trying to launch recovery...?
I tried installing over booted TWRP with unmodified boot.img and with Magisk patched boot.img, same result. The G7 play does not have a separate revovery partition, recovery is included in the boot.img
I used the TWRP files (EU) and instructions from here:
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
My stock firmware is XT1952-1_CHANNEL_RETEU_10_QPYS30.52-22-8-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Am I missing something? I've now searched for days (most info is outdated, taken from other places/Motorola phones with just 'G7 play' added, or is ambiguous); so can anyone *PLEASE* help me? Does anyone have a G7 play of the same type with Android 10 Stock who has successfully installed TWRP and was able to access the Recovery afterward without being stuck in a loop?
I also can't create a TWRP backup with a fastboot booted TWRP because system (and internal SD too) seems to be encrypted, and I don't seem to be able to deactivate this in the phone. Is this normal? Some places say that TWRP can decrypt when it's installed permanently...
Or could anybody patch the boot.img in above Firmware and add TWRP for me so I can just flash the boot.img?
Thanks in advance... please reply noob-friendly.
Still need a patched boot.img? Attached you'll find a boot.img with TWRP installed. I followed your links to get boot.img + twrp.img.
NO MAGISK INSTALLED!!!​Please patch before flashing if Magisk is already installed.
I put a log of the repack command into the zip that is showing the checksums of the boot header. Just to have a proof.
WoKoschekk said:
Still need a patched boot.img? Attached you'll find a boot.img with TWRP installed.
Click to expand...
Click to collapse
Thanks for trying to help, but this boot.img behaves exactly like the one I made by following the installation instructions on the TWRP website. I flashed it, restarted bootloader, then tried to go into recovery, and it bootloops (black screen with N/A in the top left corner).
But what I need is a boot.img with a WORKING TWRP recovery (that can actually be launched when recovery is selected...
Any idea why this won't work, why TWRP won't start?
@Alonso_Quixana Try the attached one. It's a boot.img patched with twrp + recovery_dtbo. The recovery_dtbo is part of the twrp.img but TWRP's installer.zip doesn't take it into account while repacking the patched boot.img. Maybe (hopefully!) that's the reason why you're able to boot TWRP but not to install it permanently.
Please try also - in any case! - the patched installer.zip that comes with a recovery_dtbo.
Sadly, you can't flash TWRP on stock ROM, in case you did sucessfully, ROM will not boot and that can cause SIM and VoLTE issues, i did flash it on mine and now VoLTE doesn't work on my phone, you can only boot it in case you want to flash an custom ROM, flash it then reboot into recovery to install GApps on the Custom Recovery that the ROM does install, but since all of the ROMs are arm64, i don't recommend it since you will have constant app restarting when changing from one app to another app
chuy19312 said:
Sadly, you can't flash TWRP on stock ROM, in case you did sucessfully, ROM will not boot and that can cause SIM and VoLTE issues, i did flash it on mine and now VoLTE doesn't work on my phone, you can only boot it in case you want to flash an custom ROM, flash it then reboot into recovery to install GApps on the Custom Recovery that the ROM does install, but since all of the ROMs are arm64, i don't recommend it since you will have constant app restarting when changing from one app to another app
Click to expand...
Click to collapse
Thanks for replying...
I've seen so-called tutorials on Youtube where someone actually succeeded in installing TWRP on his Moto G7 play (but did not mention which Android version was on the phone), and the TWRP developers too claim that their version for Moto G7 play would work, it even got an official update for Android 10 (alas they never reply to direct e-mails, those snooty guys)... some on XDA even said the flashing of a 'dirty port' worked for them. Were they all mistaken? Or did it work on Android 9? Are all XDA threads and internet posts / Youtube videos misleading / lying?
Are you REALLY sure that there is no way to install TWRP on a Moto G7 play (to be able to create a working backup of the encrypted data partition)? A 'full restorable backup of everything' is what I need...
I'm not sure about Android 10 Stock Rom, but it seems to be a 32bit system on a 64bit Kernel?
Alonso_Quixana said:
I'm not sure about Android 10 Stock Rom, but it seems to be a 32bit system on a 64bit Kernel?
Click to expand...
Click to collapse
It's a 32bit system on a 64bit CPU (Snapdragon 632). That's not unusual for Motorola devices. Open a terminal app and execute uname -a.
Alonso_Quixana said:
Thanks for replying...
I've seen so-called tutorials on Youtube where someone actually succeeded in installing TWRP on his Moto G7 play (but did not mention which Android version was on the phone), and the TWRP developers too claim that their version for Moto G7 play would work, it even got an official update for Android 10 (alas they never reply to direct e-mails, those snooty guys)... some on XDA even said the flashing of a 'dirty port' worked for them. Were they all mistaken? Or did it work on Android 9? Are all XDA threads and internet posts / Youtube videos misleading / lying?
Are you REALLY sure that there is no way to install TWRP on a Moto G7 play (to be able to create a working backup of the encrypted data partition)? A 'full restorable backup of everything' is what I need...
I'm not sure about Android 10 Stock Rom, but it seems to be a 32bit system on a 64bit Kernel?
Click to expand...
Click to collapse
I think it only works on certain Moto G7 Play variations or even only on Android 9, also, another way to install TWRP is installing an Custom ROM then flashing an flashable zip of TWRP_11 by SyberHexen on Custom ROM's Recovery
Link to TWRP_11 Flashable Zip
channel-twrp-installer-3.6.2_11.0_RC-1.0.zip | by SyberHexen for Moto G7 Play
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
In my case, flashing TWRP, even by following some tutorials made my MetroPCS Moto G7 Play to stop booting and also, VoLTE stopped working, fortunately, i had an EFS backup to restore my IMEI
Android 10 Stock Rom is an Arm (32 bits) ROM, every Custom ROM i tested are Arm64, but i don't recommend any of them since you will get constant app rebooting and notification problems since this is an 2 GB RAM device