XT1052, Only outdated versions of TWRP and SuperSU working - Moto X Q&A

With my Moto X (Ghost) XT1052 I have strange problems installing custom ROMs and root.
TWRP
If using the latest stable TWRP 2.8.7.0 and trying to install CM13 I get an error message like this:
Code:
This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc, xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcica,x t1060,ghost_verizon; this device is )".
There is a thread about making changes to the updater-script to get around this problem which did not solve the problem for me, and I don't see it as a permanent solution.
What did work was to install an older version, specifically TWRP 2.6.3.1.
Question: Is there a solution to this problem with a specific current build of TWRP or have ro.product.device permanently set?
SuperSU
After flashing the latest SuperSU from TWRP and rebooted, the device just hangs on the boot logo and does not pass.
Using the much older SuperSU 2.63 works without a problem.
Question: Is there any solution to get the latest SuperSU installed?

gotling said:
With my Moto X (Ghost) XT1052 I have strange problems installing custom ROMs and root.
TWRP
If using the latest stable TWRP 2.8.7.0 and trying to install CM13 I get an error message like this:
Code:
This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc, xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcica,x t1060,ghost_verizon; this device is )".
There is a thread about making changes to the updater-script to get around this problem which did not solve the problem for me, and I don't see it as a permanent solution.
What did work was to install an older version, specifically TWRP 2.6.3.1.
Question: Is there a solution to this problem with a specific current build of TWRP or have ro.product.device permanently set?
Click to expand...
Click to collapse
Mate, I installed the unofficial TWRP from the post below, it worked fine in my moto X (XT1058). Try flash the TWRP 3.0.2 via fastboot (using computer).
https://forum.xda-developers.com/moto-x/development/twrp-touch-recovery-unofficial-t3309449
Try to verify the downloaded archives, because they may contain errors and a re download is needed.

Related

[Q] Can't flash under TWRP 2.8.6.0 (PAC-ROM Beta-1 Lollipop 5.1)

Hi,
I'm running on PAC-ROM Beta-1 Lollipop 5.1 under TWRP 2.8.6.0 on Samsung GT-I9105P.
I can't flash the .zip; I'm receiving the following error message:
Code:
[COLOR="Red"]E:Error executing updater binary in zip '/external_sd/xposed-arm-20150308.zip'[/COLOR]
I read somewhere on XDA that disabling USB debugging would help, however, to no avail in my case.
The .apk installs fine, but without the .zip it's no use.
It used to work perfectly under stock 4.2.2.
How do I get Xposed to work?
Many thanks in advance.
I'm having the same issue.
Good to see I'm not alone
(TWRP 2.8.5.4 on TF300)
I think you're trying to install Xposed for Android 5.0 on Android 5.1
You need install this;
http://forum.xda-developers.com/attachment.php?attachmentid=3245467&d=1428192863
forumber2 said:
I think you're trying to install Xposed for Android 5.0 on Android 5.1
You need install this;
http://forum.xda-developers.com/attachment.php?attachmentid=3245467&d=1428192863
Click to expand...
Click to collapse
Thanks for trying, however after installing and activating modules, when trying to reboot I end up being stuck in a bootloop.

Systemless SupeSU and systemless Xposed - No OTA flashes

Hi folks,
i hope i im the right Forum as it seams more a xposed as supersu problem.
I have a Moto X Style rooted with System-less SuperSU 2.78 and Xposed "xposed-v86.1-sdk23" by romracer, Stock ROM 6.0.
Just got a notification that there is a security update available, proceeded but won´t flash. Stops with Error Code 7.
I thought OTA would work with system-less.
Tried also with disable Xposed. Same result. By the way when the phone reboots for flashing it goes into The Recover TWRP 3.0.2 GUI. Anyway i saw the error when switching to the log view.
Any idea whats wrong or i miss?
May i have to restore custom recovery, and if so can i flash the stock recovery with the existing TWRP or do i have to go ADB?
Thanks
Thomas
You have to flash stock recovery image (and probably also boot image) for OTA to work.
Simply use fastboot to flash those. Leave system intact.
Thanks, will do so.

Can't install TWRP after updating to Nougat

I recently updated my EVA-L09 to Android 7.0. Before that, I was rooted and I had TWRP. After I updated, I obviously would need to install TWRP and root again, but when I install it with SRK Tool or even with fastboot, it always goes back to stock recovery. I already tried to flash it by "recovery.img" as well.
Gutito said:
I recently updated my EVA-L09 to Android 7.0. Before that, I was rooted and I had TWRP. After I updated, I obviously would need to install TWRP and root again, but when I install it with SRK Tool or even with fastboot, it always goes back to stock recovery. I already tried to flash it by "recovery.img" as well.
Click to expand...
Click to collapse
that would be because the TWRP in SRK Tools is only for android 6 (EMUI 4.1 - 4.1.1) and not for android 7 (EMUI 5 - 5.1)
the recovery that you need to use in order for twrp to be installed is this one https://github.com/OpenKirin/android_device_huawei_eva/releases/download/3.1.0/twrp-3.1.0-0-eva.img
then once its installed boot up your phone and then type in "adb reboot recovery" and that will then boot your device into TWRP 3.1.0.0
Thank you, it worked!
Another question, but now related to SuperSU.
I am with the 2.79 version of SuperSU and I downloaded the binary .zip of this version and flashed it by twrp. The problem is that it keeps saying ""There is no SU binary installed and SuperSU cannot install it. This is a problem!".
I already got it to work. Thanks btw
Gutito said:
I already got it to work. Thanks btw
Click to expand...
Click to collapse
Could you post how perhaps? I had the same problem as you - the TWRP posted about fixed my first problem but now I can't get SuperSU to install either. Would be interested to know how you fixed it!
kzip said:
Could you post how perhaps? I had the same problem as you - the TWRP posted about fixed my first problem but now I can't get SuperSU to install either. Would be interested to know how you fixed it!
Click to expand...
Click to collapse
I solved it by this post https://forum.xda-developers.com/showpost.php?p=70927601&postcount=456
I ended up not using super su but If you want you can use it instead of the one suggested there
By flashing the file provided in the post, I managed to automatically get access to super user (root)

can´t root with Magisk nor SU

Some days ago I got a brand new XZ2c (single sim) and from the past I know that this forum is the place to go for guides for rooting and for custom roms :good:
So I started a lot of reading articles and than tried this guide:
[RECOVERY][Android 8 / 9][Stock/Custom ROM][XZ2/c/p, XZ3] TWRP 3.3.1-0 [UNofficial] https://forum.xda-developers.com/xp...recovery-twrp-3-2-2-0-touch-recovery-t3821597 and for sure all tools I dl from the links from the guide
btw. my goal is the eXistenZ Pie rom and of course root
1. Update to newest stock firmware before unlocking!!!
Click to expand...
Click to collapse
I don´t know if it was a "fault" but I unlocked with the firmware with which I got the phone and it was the firmware before the latest one
so at my first rooting try I did no update to the latest firmware, but at all further tries I flashed the newest firmware 52.0.A.8.131 for my country and provider (H8314 Mobilkom A1, it´s for Austria)
I did every step from this guide:
2. FASTBOOT
(Optional; If you modify the system or need the camerafix.zip)fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot boot twrp.img
3. TWRP
Advanced menu -> "Install recovery ramdisk" -> Choose twrp.img
4. Reboot into installed TWRP
5. TWRP
(Optional; Root Part 1/2) Flash Magisk 19.4 or newer
Click to expand...
Click to collapse
booting into twrp never was a problem and also every time I did the fastboot command with the ...vbmeta.img (don´t know if this is still necessary but I did)
6. Reboot into SYSTEM
Click to expand...
Click to collapse
and here is always the same and first problem: a boot loop, so I rebooted into recovery: fix boot loop
after this no problem to boot into system and everything is working fine but no root (Magisk and root checker)
7. (Optional; Root Part 2/2) Install the official Magisk App to gain root.
Click to expand...
Click to collapse
after I installed this it shows me:
1) Magisk is not installed (new version 19.3)
2) a newer version of the app is available (7.3.2)
sure I updated both the app and installed from twrp the 19.3 zip but still no success (again boot loop and fixed the loop from twrp)
I tried the complete procedure a lot of times, always with flashtool flashed the latest firmware, booted into system, than twrp a.s.o., I tried some solutions from this forum like patching the twrp directly with Magisk: https://forum.xda-developers.com/showpost.php?p=74368287&postcount=23 but no success
at least I tried to install SU but also no root
...I have no idea what I should try next so I hope you have some advices?
Same problem for me.. maybe it has to do with the drm?
Same problem for me.. maybe it has to do with the drm?
b00rn said:
Some days ago I got a brand new XZ2c (single sim) and from the past I know that this forum is the place to go for guides for rooting and for custom roms :good:
So I started a lot of reading articles and than tried this guide:
[RECOVERY][Android 8 / 9][Stock/Custom ROM][XZ2/c/p, XZ3] TWRP 3.3.1-0 [UNofficial] https://forum.xda-developers.com/xp...recovery-twrp-3-2-2-0-touch-recovery-t3821597 and for sure all tools I dl from the links from the guide
btw. my goal is the eXistenZ Pie rom and of course root
I don´t know if it was a "fault" but I unlocked with the firmware with which I got the phone and it was the firmware before the latest one
so at my first rooting try I did no update to the latest firmware, but at all further tries I flashed the newest firmware 52.0.A.8.131 for my country and provider (H8314 Mobilkom A1, it´s for Austria)
I did every step from this guide:
booting into twrp never was a problem and also every time I did the fastboot command with the ...vbmeta.img (don´t know if this is still necessary but I did)
and here is always the same and first problem: a boot loop, so I rebooted into recovery: fix boot loop
after this no problem to boot into system and everything is working fine but no root (Magisk and root checker)
after I installed this it shows me:
1) Magisk is not installed (new version 19.3)
2) a newer version of the app is available (7.3.2)
sure I updated both the app and installed from twrp the 19.3 zip but still no success (again boot loop and fixed the loop from twrp)
I tried the complete procedure a lot of times, always with flashtool flashed the latest firmware, booted into system, than twrp a.s.o., I tried some solutions from this forum like patching the twrp directly with Magisk: https://forum.xda-developers.com/showpost.php?p=74368287&postcount=23 but no success
at least I tried to install SU but also no root
...I have no idea what I should try next so I hope you have some advices?
Click to expand...
Click to collapse
Luspuz said:
Same problem for me.. maybe it has to do with the drm?
Click to expand...
Click to collapse
b00rn said:
Some days ago I got a brand new XZ2c (single sim) and from the past I know that this forum is the place to go for guides for rooting and for custom roms :good:
So I started a lot of reading articles and than tried this guide:
[RECOVERY][Android 8 / 9][Stock/Custom ROM][XZ2/c/p, XZ3] TWRP 3.3.1-0 [UNofficial] https://forum.xda-developers.com/xp...recovery-twrp-3-2-2-0-touch-recovery-t3821597 and for sure all tools I dl from the links from the guide
btw. my goal is the eXistenZ Pie rom and of course root
I don´t know if it was a "fault" but I unlocked with the firmware with which I got the phone and it was the firmware before the latest one
so at my first rooting try I did no update to the latest firmware, but at all further tries I flashed the newest firmware 52.0.A.8.131 for my country and provider (H8314 Mobilkom A1, it´s for Austria)
I did every step from this guide:
booting into twrp never was a problem and also every time I did the fastboot command with the ...vbmeta.img (don´t know if this is still necessary but I did)
and here is always the same and first problem: a boot loop, so I rebooted into recovery: fix boot loop
after this no problem to boot into system and everything is working fine but no root (Magisk and root checker)
after I installed this it shows me:
1) Magisk is not installed (new version 19.3)
2) a newer version of the app is available (7.3.2)
sure I updated both the app and installed from twrp the 19.3 zip but still no success (again boot loop and fixed the loop from twrp)
I tried the complete procedure a lot of times, always with flashtool flashed the latest firmware, booted into system, than twrp a.s.o., I tried some solutions from this forum like patching the twrp directly with Magisk: https://forum.xda-developers.com/showpost.php?p=74368287&postcount=23 but no success
at least I tried to install SU but also no root
...I have no idea what I should try next so I hope you have some advices?
Click to expand...
Click to collapse
Magisk 19.3 is the issue, use 18.1 stable, or 19.4 beta
Beetle84 said:
Magisk 19.3 is the issue, use 18.1 stable, or 19.4 beta
Click to expand...
Click to collapse
:good:
1st try with 19.3 beta and its done, also first magisk version without boot loop - so much time wasted and so easy solution (if you know it)
...I am so happy, you don´t believe!
only one question: why is at the twrp dl location in the "package" where all the files in (linked in the twrp thread) a magisk version which is not working on xz2c?
b00rn said:
:good:
1st try with 19.3 beta and its done, also first magisk version without boot loop - so much time wasted and so easy solution (if you know it)
...I am so happy, you don´t believe!
only one question: why is at the twrp dl location in the "package" where all the files in (linked in the twrp thread) a magisk version which is not working on xz2c?
Click to expand...
Click to collapse
I did bundle 18.1 which should work and linked now 19.4 beta, which should work too.
Which bundled version didn't worked exactly?
MartinX3 said:
Which bundled version didn't worked exactly?
Click to expand...
Click to collapse
it was 18.1 also I tried a 14.x which was an advise in another thread with similar problems (boot loop) and the "new" 19.3
...so at least I tried with 3 different Magisk versions and thought the "failure" has to be an other reason, but I was wrong - I am only wondering that it seems nobody else had problems with the 18.1, I was not only searching in this forum also tried to find solutions with G, found some threads with the boot loop problem but close to nothing with rooting problems
b00rn said:
it was 18.1 also I tried a 14.x which was an advise in another thread with similar problems (boot loop) and the "new" 19.3
...so at least I tried with 3 different Magisk versions and thought the "failure" has to be an other reason, but I was wrong - I am only wondering that it seems nobody else had problems with the 18.1, I was not only searching in this forum also tried to find solutions with G, found some threads with the boot loop problem but close to nothing with rooting problems
Click to expand...
Click to collapse
At least 19.4 works at your side [emoji14]
That's the best case of possibilities

Rooting Moto G6 with PPS29-118-15-11. What versions of noverity, twrp, magisk to use?

Hello forum, I have been trying to root my motorola G6..
After much struggle, getting stuck in a boot loop and other issues I finally have restored stock roms and now have build PPS29-118-15-11 installed. So at least the phone works again My bootloader is unlocked.
But I still want to root it.
I think I understand the procedure well enough, but I am unsure of the correct/best versions I need for the ROMS/boot, Magisk, and TWRP.
ROMS/boot:
I found a youtube with instructions for updating Android v9
But I haven't tried it as this recommends a boot img:
OPS27.104-15-10_no-verity_boot.img
OPS27.104-15-10_no-verity_boot.img | by dejello for Moto G6
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I am reluctant to use the above as it looks to be a downgrade from my current version 29-118-15-11.
Also, I thought that the filename prefix "O" indicated oreo instead of "P" for pie? So would this be a version 8 file?
TWRP:
Similarly, I am not sure if I am using the right, or best TWRP version. I currently have twrp-v3.2.3-ali.img
I flash this (with fastboot) and it works but shortly after I encounter the "no command" error (when booting to recovery) and I have to redo it. I am NOT overwriting it with a stock recovery.img.
I have also run into the "encryption password" problem, where I am unable to provide one to decrypt the data partition. So I can't backup the data with twrp (something I really would like to do).
Magisk
I have Magisk-23-0.zip
But I saw a post from brunogroa that recommends installing Magisk 19 and updating it to 23 later. Is this something that is required or can I just install v23?
So, I am looking for the correct versions for ROM, Magisk and TWRP to use, given that I have installed PPS29-118-15-11
Any assistance will be greatly appreciated.
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
pdpantages said:
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
Click to expand...
Click to collapse
I am stuck in a similar position.
SOLVED IT!!! Followed all of the steps that you posted except I installed Magisk with the patch method because I couldn't get the zip file to push onto the device. Kept getting a read only error, maybe because it wasn't rooted?
Anyway, I am rooted now!!!

Categories

Resources