[Q] root problem - G 2014 Q&A, Help & Troubleshooting

my moto g 2014 titan_retaildsds in not compatible with chainfire auto root zip titan_retaildsds and its not rooting please can anyone help me????:crying:

syash01 said:
my moto g 2014 titan_retaildsds in not compatible with chainfire auto root zip titan_retaildsds and its not rooting please can anyone help me????:crying:
Click to expand...
Click to collapse
1. Follow Motorola's instructions to
unlock the bootlader.
2. Flash TWRP 2.8.5 with fastboot.
3. Flash latest SuperSU with TWRP.
4. Enjoy

syash01 said:
my moto g 2014 titan_retaildsds in not compatible with chainfire auto root zip titan_retaildsds and its not rooting please can anyone help me????:crying:
Click to expand...
Click to collapse
Well, flashing with TWRP only worked for me on KitKat, it stopped working for 5.02, but what I did was used auto root for Lollipop, I was told this is the only supported method for this device on Lollipop, are you still on 4.4.4 or did you receive the OTA 5.02?
And as you are trying Auto Root, are you sure you are choosing the correct one for your device, it took me an hour or so to ensure that it was the correct one, I analysed all the tags and compared them with my version, there was a few for my device so I had to make sure everything matched.
This is the one I used, it works but best check if it fits your device: download(dot)chainfire(dot)eu/603/CF-Root/CF-Auto-Root/CF-Auto-Root-titanumtsds-titanretaildsds-xt1068.zip
You need to add the http protocol and replace (dot) with .
It won't let me post links.

TchTlk said:
Well, flashing with TWRP only worked for me on KitKat, it stopped working for 5.02
Click to expand...
Click to collapse
How so?

doppelhelix said:
How so?
Click to expand...
Click to collapse
After the flash was successful with TWRP, I launched the SU app and it said something along the lines of 'SuperUser is not installed correctly' I used the exact same method as I did on KitKat, I then learned that this is no longer the way of rooting the device on Lollipop, I installed TWRP for nothing.

After rooting via TWRP 2.8.5.0 try to change the mode with SELinux Mode Changer: https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=de

TchTlk said:
I then learned that this is no longer the way of rooting the device on Lollipop, I installed TWRP for nothing.
Click to expand...
Click to collapse
?
There was and is only one correct way to install SuperSU regardless of lollipop or kitkat
· Flash TWRP 2.8.5 with fastboot.
· Flash latest SuperSU with TWRP.
Wolfcity said:
change the mode with SELinux Mode Changer:
Click to expand...
Click to collapse
Chainfire himself is strictly against changing SELinux. That's why he had to invest so much time and even bought a Moto G (2014) so he can fix any error resulting of enforced SELinux. SuperSU 2.45 was the result of his investigation into the XT106x.

doppelhelix said:
?
There was and is only one correct way to install SuperSU regardless of lollipop or kitkat
CR Auto Root is the only method that worked for me since the lollipop update, I tried the SU zip with TWRP, i t was successful, however the SU app just displayed an error message saying that if wasn't installed correctly.
I did exactly the same thing as before, the only thing that changed was the new update.
Click to expand...
Click to collapse

TchTlk said:
.
I did exactly the same thing as before, the only thing that changed was the new update.
Click to expand...
Click to collapse
Maybe your twrp version was outdated?

doppelhelix said:
?
There was and is only one correct way to install SuperSU regardless of lollipop or kitkat
· Flash TWRP 2.8.5 with fastboot.
· Flash latest SuperSU with TWRP.
Chainfire himself is strictly against changing SELinux. That's why he had to invest so much time and even bought a Moto G (2014) so he can fix any error resulting of enforced SELinux. SuperSU 2.45 was the result of his investigation into the XT106x.
Click to expand...
Click to collapse
Thx for that info. Didn´t heard that and if Chainfire said so it´s better to follow that.
And btt,flashing TWRP 2.8.4.0 or 2.8.5.0 with latest superSU (2.46 at the moment) should work with 5.0.2 without any other variations.

Related

update to lolipop my xz3c and keep the root, possible?

sorry for the bed english...
i have experia z3 compact rotted
4.4.4.
build 23.0.a.2.93
how can i update to lolipop and keep my root?
10x.
Yes you can indeed! You just have to flash a pre-rooted Lollipop firmware (linked). That link has a pre-made pre-rooted 5.0.2 Lollipop firmware that should work well! The only problem right now is the the XZDualRecovery does not really support Lollipop yet, but will very soon be updated!
You may also want to refer to this comprehensive guide.
Tuberomix said:
Yes you can indeed! You just have to flash a pre-rooted Lollipop firmware (linked). That link has a pre-made pre-rooted 5.0.2 Lollipop firmware that should work well! The only problem right now is the the XZDualRecovery does not really support Lollipop yet, but will very soon be updated!
You may also want to refer to this comprehensive guide.
Click to expand...
Click to collapse
And is that a problem if XZDualRecovery is not supported yet ?
I have a Z3c rooted on 4.4 and I still don't understand what is the purpose of dual recovery. What does it change for me on a daily basis if I flash a pre-booked 5.0.2 and if dual recovery doesn't work yet ?
Sorry for the dumb question, I prefer to make sure before trying to flash the pre-booked 5.02
hayatesan said:
And is that a problem if XZDualRecovery is not supported yet ?
I have a Z3c rooted on 4.4 and I still don't understand what is the purpose of dual recovery. What does it change for me on a daily basis if I flash a pre-booked 5.0.2 and if dual recovery doesn't work yet ?
Sorry for the dumb question, I prefer to make sure before trying to flash the pre-booked 5.02
Click to expand...
Click to collapse
Changes nothing for you.
An identical thread already exists.
Tapatalked
frason said:
Changes nothing for you.
An identical thread already exists.
Tapatalked
Click to expand...
Click to collapse
Is there additional useful information in that thread ?
You might have problems installing Xposed. In KitKat I could only install it from Recovery. If Lollipop is the same you might not be able to install it until there's a working Recovery.
Xposed is still alpha for lollipop, expect issues.
i just donwload this file and 1 more qustion...
is it support hebrew? if not where do i get file like this thet support hebrew?
and i simplly update via ota...my root will dissappere?
cpurick said:
You might have problems installing Xposed. In KitKat I could only install it from Recovery. If Lollipop is the same you might not be able to install it until there's a working Recovery.
Click to expand...
Click to collapse
Just tried to root my z3c this morning and install xposed, root is ok but still I can't update xposed to run module, where can I get the zip file to install xposed ? thank you in advance
b_boy_9x said:
Just tried to root my z3c this morning and install xposed, root is ok but still I can't update xposed to run module, where can I get the zip file to install xposed ? thank you in advance
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3034811
Xposed for LP
tribemac said:
http://forum.xda-developers.com/showthread.php?t=3034811
Xposed for LP
Click to expand...
Click to collapse
i'm using kk and already install this by recovery after reading that post
After reading a couple of posts :
- "real" root on lollipop is not yet available. You can't mount system as r/w without recovery.
- no recovery yet support lollipop.
- xposed is yet in beta for lollipop. However, everything works except modules made specifically for kk.
- xposed can only be installed via recovery on lp. It's because of security breach fixed.
So, I would advise to wait for a recovery before flashing lp.
Best chance are at nut's dual recovery.
Regards.
Mazzeru said:
After reading a couple of posts :
- "real" root on lollipop is not yet available. You can't mount system as r/w without recovery.
- no recovery yet support lollipop.
- xposed is yet in beta for lollipop. However, everything works except modules made specifically for kk.
- xposed can only be installed via recovery on lp. It's because of security breach fixed.
So, I would advise to wait for a recovery before flashing lp.
Best chance are at nut's dual recovery.
Regards.
Click to expand...
Click to collapse
Xposed doesn't work well at all on z3c people is stucked in bootloop after second restart. And some people have r/w on lollipop including my self.
I did the same process do I get root in version .77 for the lollipop, but not worked.
What can I have done wrong?

[SuperSU][System-Mode][2.82 SR5]

This is SuperSU that installs always in System-Mode.
Instructions
1 - Download zip
2 - Go in recovery & make a backup (optional, but recommended)
3 - Flash zip
Changelogs here & here
Special thanks to @aufarxda (the original creator of this thread) @Chainfire @CCMT
binaries failed to update
Just installed the lastest security update (6.01) from google on my nexus 6. Flashed v2.66 and binaries will not update. Any suggestions?
Thanks My Brother ?
Reflash the kernel.
Unroot.
Reroot.
Should work.
Hope that helps.
aufarxda said:
Reflash the kernel.
Unroot.
Reroot.
Should work.
Hope that helps.
Click to expand...
Click to collapse
I am on CM13 1/6/2016 nightly on angler, and this is causing a bootloop now. Before this newest nightly, I was able to install with no problem. Systemless also still works.
fpqc said:
I am on CM13 1/6/2016 nightly on angler, and this is causing a bootloop now. Before this newest nightly, I was able to install with no problem. Systemless also still works.
Click to expand...
Click to collapse
Nightly comes with problems.Look Angler's XDA thread and ask others which nightly is the most stable build.
Hope that helps.
aufarxda said:
Nightly comes with problems.Look Angler's XDA thread and ask others which nightly is the most stable build.
Hope that helps.
Click to expand...
Click to collapse
The reason I think is that this is the first update with the newest vendor.img. That's the only thing that seems out of the ordinary.
fpqc said:
The reason I think is that this is the first update with the newest vendor.img. That's the only thing that seems out of the ordinary.
Click to expand...
Click to collapse
Well, just reflash last update before this one.
Or, just wait another update with the fix.
I have the Verizon SCH-I545, MDK bootloader, and am running JDC Team's AOSP 6.0.
I am unable to install any version of SU above 2.52. TWRP 2.8.7.0 and 2.8.7.2 by Antaresone and the official 2.8.7.0 all fail with the same message.
Recovery.log
https://www.dropbox.com/s/kmc3bafuvlfq20v/recovery.log?dl=0
FernBch said:
I have the Verizon SCH-I545, MDK bootloader, and am running JDC Team's AOSP 6.0.
I am unable to install any version of SU above 2.52. TWRP 2.8.7.0 and 2.8.7.2 by Antaresone and the official 2.8.7.0 all fail with the same message.
Recovery.log
https://www.dropbox.com/s/kmc3bafuvlfq20v/recovery.log?dl=0
Click to expand...
Click to collapse
Solution 1(Tricky, and may not work) :
Try to mount data and system using mount option and remove mounting script on the updater-binary.
Then, use TWRP file manager to remove /supersu manually.
At last, install the zip again.
Solution 2 (not really a solution) :
If you really cant mount data or system, ask the rom dev or someone on your phone's forum for solution.
Solution 3 (1% chance of working) :
Dont bother about the bootloader.
Check your boot image instead.
Solution 4 :
Check if you have chcon on system/bin.
If not download this file and move it into system/bin.
Link :Drive
Hi,
Thanks! This version finally works for secondary roms in Multrirom!!!
Droidphilev said:
Hi,
Thanks! This version finally works for secondary roms in Multrirom!!!
Click to expand...
Click to collapse
Nice to know.
Can this be flashed over systemless root to convert to system root or will I have to flash my system.img backup then this. I'm running systemless root on Htc M9 Marshmallow dev edition
Sent from my HTC One M9 using Tapatalk
I installed 2.64 beta via TWRP. It installed successfully however upon reboot it shows i still have 2.52. Is that normal?
slick97477 said:
I installed 2.64 beta via TWRP. It installed successfully however upon reboot it shows i still have 2.52. Is that normal?
Click to expand...
Click to collapse
Don't know. Maybe install the app on the zip manually. Update the binary and if updating fails, full unroot and re-root with the new zip.
krazyace35 said:
Can this be flashed over systemless root to convert to system root or will I have to flash my system.img backup then this. I'm running systemless root on Htc M9 Marshmallow dev edition
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
No, full unroot first.
Then, remove /su
Replace the kernel with new custom one.
And then, flash the system mode zip.
aufarxda said:
No, full unroot first.
Then, remove /su
Replace the kernel with new custom one.
And then, flash the system mode zip.
Click to expand...
Click to collapse
Cool thanks for the info
Sent from my HTC One M9 using Tapatalk
---------- Post added at 06:00 PM ---------- Previous post was at 05:30 PM ----------
@aufarxda I'm guessing there are no custom kernels yet for Marshmallow? I can't find one I also noticed flar2 said the kernel source hasn't been released yet
Sent from my HTC One M9 using Tapatalk
krazyace35 said:
@aufarxda I'm guessing there are no custom kernels yet for Marshmallow? I can't find one I also noticed flar2 said the kernel source hasn't been released yet
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Maybe not avaiable for your phone.
But most Marshmallow phone devs already made custom kernels for their phones.
Thanks for this, @aufarxda. Can you tell us what you did and made it always install in System mode?
KreAch3R said:
Thanks for this, @aufarxda. Can you tell us what you did and made it always install in System mode?
Click to expand...
Click to collapse
I moved v2.52 script with little modifications (aside from the ui_print).

Nexus 6 Nougat Root with SuperSU

I can't seem to find the answer to this.
I've just flashed the Nougat Factory image for Nexus 6 and want root. Can anyone confirm is the latest SuperSU is compatible? I've flashed TWRP and downloaded the latest SuperSU but just a little hesitant to flash it in case of issues.
Thanks a lot.
Yep I rooted just fine. works ok.
Nucleotide said:
I can't seem to find the answer to this.
I've just flashed the Nougat Factory image for Nexus 6 and want root. Can anyone confirm is the latest SuperSU is compatible? I've flashed TWRP and downloaded the latest SuperSU but just a little hesitant to flash it in case of issues.
Thanks a lot.
Click to expand...
Click to collapse
I had no problems with the latest version, which I installed last night (downloaded factory image, extracted to PC and fastboot flashed through bootloader, rebooted to recovery and flashed SuperSU 2.78-SR1).
yudumcan said:
Yep I rooted just fine. works ok.
Click to expand...
Click to collapse
pkgnex said:
I had no problems with the latest version, which I installed last night (downloaded factory image, extracted to PC and fastboot flashed through bootloader, rebooted to recovery and flashed SuperSU 2.78-SR1).
Click to expand...
Click to collapse
Perfect. Flashed and working great. Thank you! :good:
If you enjoy having an unknown organization having absolute godlike control over your phone, then sure, use stupidsu.
But if you like to have auditable and sane control over your own device, I would very VERY much suggest that you instead use https://github.com/seSuperuser/AOSP-SU-PATCH
Nucleotide said:
I can't seem to find the answer to this.
I've just flashed the Nougat Factory image for Nexus 6 and want root. Can anyone confirm is the latest SuperSU is compatible? I've flashed TWRP and downloaded the latest SuperSU but just a little hesitant to flash it in case of issues.
Thanks a lot.
Click to expand...
Click to collapse
I flashed factory image today and went to Nexus Root Toolkit to root and flash recovery. It went well.
new to Nexus 6, just got Nougat OTA, whats the best way to root and have double tap to wake (will it drain battery big time?) and notification led? pls help, tia
btw I use Mac
Isn't the nexus 6 supposed to be 100% stock Android and with that being able to be rooted by any root method? I know I've read many times that if you want to get into root and hacking to pick up a nexus device as they were easily recoverable and weren't root blocked by any means
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
Isn't the nexus 6 supposed to be 100% stock Android and with that being able to be rooted by any root method? I know I've read many times that if you want to get into root and hacking to pick up a nexus device as they were easily recoverable and weren't root blocked by any means
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
Not sure what exactly you're asking but the Nexus 6 is easily rooted when using the proper methods. Unlock the bootloader, fastboot flash TWRP recovery and then flash SuperSU or Magisk in TWRP.

Removed Root on Costum FIrmware

As Mantioned in the title I accidentally removed my Root permission on my Amazon Fire . I'd tried to reeinstall busybox and after a reboot root permissions where gone :/
I also tried to use King Root again but with no luck. Flashed it with FireFlash
Model:KFFOWI
ROM:Cyanogenmod 12.1-20161122-UNOFFICIAL-ford
Unversed said:
As Mantioned in the title I accidentally removed my Root permission on my Amazon Fire . I'd tried to reeinstall busybox and after a reboot root permissions where gone :/
I also tried to use King Root again but with no luck. Flashed it with FireFlash
Model:KFFOWI
ROM:Cyanogenmod 12.1-20161122-UNOFFICIAL-ford
Click to expand...
Click to collapse
,
Assume you have tried re-enabling root under developer options to no avail (don't forget to reboot between attempts).
You will need to reinstall/sideload FireOS (same version that was on your device before installing CM 12.1) from stock recovery and start again. Be sure to keep device off WiFi except when running KingRoot; otherwise Amazon will push an OTA update that will block root and any hope of running a custom ROM.
Davey126 said:
,
Assume you have tried re-enabling root under developer options to no avail (don't forget to reboot between attempts).
You will need to reinstall/sideload FireOS (same version that was on your device before installing CM 12.1) from stock recovery and start again. Be sure to keep device off WiFi except when running KingRoot; otherwise Amazon will push an OTA update that will block root and any hope of running a custom ROM.
Click to expand...
Click to collapse
Is there a way to see what version of fireOS I had ? I installed CM12 a long Time ago.
Do I really need to install the same version ?
Unversed said:
Is there a way to see what version of fireOS I had ? I installed CM12 a long Time ago.
Do I really need to install the same version ?
Click to expand...
Click to collapse
If you go too low your device will brick. If uncertain sideload FireOS 5.3.1 which is the highest rootable build at present. You can find links in the index thread.
Do you recall using TWRP or FlashFire to install CM?
Davey126 said:
If you go too low your device will brick. If uncertain sideload FireOS 5.3.1 which is the highest rootable build at present. You can find links in the index thread.
Do you recall using TWRP or FlashFire to install CM?
Click to expand...
Click to collapse
I used flashfire. I have the stock recovery so no twrp
I guess this means installing stock firmware version 5.3.1.0 via sideload will work
I will try it
Unversed said:
I used flashfire. I have the stock recovery so no twrp
I guess this means installing stock firmware version 5.3.1.0 via sideload will work
I will try it
Click to expand...
Click to collapse
doesn't work. this is what I get:
loading: 'update-kindle-global-37.5.5.2_user_552153420.bin'
error: insufficient permissions for device.
See [http://developer.android.com/tools/device.html] for more information.
Unversed said:
doesn't work. this is what I get:
loading: 'update-kindle-global-37.5.5.2_user_552153420.bin'
error: insufficient permissions for device.
See [http://developer.android.com/tools/device.html] for more information.
Click to expand...
Click to collapse
Reboot both devices then follow instructions in this thread. Be sure to use the 5.3.1 bin, not the older one referenced in the video.
Davey126 said:
Reboot both devices then follow instructions in this thread. Be sure to use the 5.3.1 bin, not the older one referenced in the video.
Click to expand...
Click to collapse
ok my problem solved after sidloading with my windows partition
thanks for the huge help

Anyone figured out how to root ALI_RETAIL_9.0_PPSS29.118-15-11-2?

I've tried everything and I just get a bootloop. If anyone has the steps that worked for them I'd love to have my root back. Thanks community!
What exactly have you tried? We can't give you a solution for problems we don't know...
Had the same problem on 118-15-11-2, so I flashed 55-37-7 instead and it rooted fine on Magisk 20.1.
Will 55-37-7 work with Tmobile Moto G6? Haven't tried flashing that one yet.
fireman644 said:
Will 55-37-7 work with Tmobile Moto G6? Haven't tried flashing that one yet.
Click to expand...
Click to collapse
I have a Moto G6 (Ali) xt1925-6 and yes currently on retail ppss29.55-37-7 which has October patch. I've not had any problems flashing the 118 or the 55 retail builds as long as they have same or newer security patches.
Skippy12359 said:
Had the same problem on 118-15-11-2, so I flashed 55-37-7 instead and it rooted fine on Magisk 20.1.
Click to expand...
Click to collapse
Did you install Magisk by patching the recovery.img (recovery mode)? Normal installation through boot.img causes a bootloop, afaik.
https://forum.xda-developers.com/moto-g6/how-to/magisk-twrp-moto-g6-t4006983
WoKoschekk said:
Did you install Magisk by patching the recovery.img (recovery mode)? Normal installation through boot.img causes a bootloop, afaik.
https://forum.xda-developers.com/moto-g6/how-to/magisk-twrp-moto-g6-t4006983
Click to expand...
Click to collapse
After flashing and setting up 55-37-7 stock pie, I booted to twrp and flashed magisk 20.1. It boot fine and then installed magisk manager apk and had root.
Skippy12359 said:
After flashing and setting up 55-37-7 stock pie, I booted to twrp and flashed magisk 20.1. It boot fine and then installed magisk manager apk and had root.
Click to expand...
Click to collapse
Alternate route - I flashed to ALI_RETAIL_9.0_PPS29.118-11-1 (back to July Pie) and used magisk 19.3, DM Verity Disabler from August.
Seems to work fine, but wants to keep updating the system with latest version of Pie from December.
I did try to flash ALI_RETAIL_9.0_PPS29.55-24, but that killed my T-Mobile connection (wouldn't turn on the radio and/or recognize the SIM.)
Can anyone tell us what the difference between 55 and 118 variants are?
PS. My phone is the U.S. G6.
oldguy51 said:
Alternate route - I flashed to ALI_RETAIL_9.0_PPS29.118-11-1 (back to July Pie) and used magisk 19.3, DM Verity Disabler from August.
Seems to work fine, but wants to keep updating the system with latest version of Pie from December.
I did try to flash ALI_RETAIL_9.0_PPS29.55-24, but that killed my T-Mobile connection (wouldn't turn on the radio and/or recognize the SIM.)
Can anyone tell us what the difference between 55 and 118 variants are?
PS. My phone is the U.S. G6.
Click to expand...
Click to collapse
The big question is which variant of the Moto G6 do you have? For example I have XT1925-6 which is the US Unlocked variant. You need to flash the correct firmware for your variant.
https://mirrors.lolinet.com/firmware/moto/ali/official/
Go here once you know your variant to get the exact right firmware. Who is your provider?
I have the XT-1925-6 Tmobile US unlocked bootloader. I had root with PPS29-118-11-1. Now that I have updated to -2 I have lost root and get a bootloop everytime I try and flash Magisk or DM-verity. Could you help? Thanks.
fireman644 said:
I have the XT-1925-6 Tmobile US unlocked bootloader. I had root with PPS29-118-11-1. Now that I have updated to -2 I have lost root and get a bootloop everytime I try and flash Magisk or DM-verity. Could you help? Thanks.
Click to expand...
Click to collapse
Maybe you should try try "retail" firmware. If you havr the xt-1925-6 variant, it will work. US unlocked will accept it. The version is ALI_RETAIL_9.0_PPS29.55-37-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
It worked for many of us. You can use RSDLite, as long as you are connected by a USB 2 port. Do a backup first, because your internal storage will be deleted.
If you truly have an xt-1925-6, it will work
Yeah I tried flashing the firmware but it wouldn't take. Gave me errors at the beginning and wouldn't flash. I'll try again with a USB 2 port and RSDlite. I was using manual commands.
theseeker2654 said:
The big question is which variant of the Moto G6 do you have? For example I have XT1925-6 which is the US Unlocked variant. You need to flash the correct firmware for your variant.
Go here once you know your variant to get the exact right firmware. Who is your provider?
Click to expand...
Click to collapse
I'm connecting to T-Mobile, but I can't remember if the phone is used or a New in Box from Amazon at some point. It is a GSM version.
Here's a pair of questions that might help us noobs:
1. How do you tell which version of the moto g6 phone you have? (if there's a link to another discussion that gives this info, awesome.)
2. Is there a map of the hardware types to appropriate retail images? When I looked in the RETAIL directory for the link above, there appears to be two versions for 9.0 - 29.55 and 29.118 - with my phone functioning in the .118 stream through trial and error.
Thanks!
-og
OK I have used the ALI_RETAIL_9.0_PPS29.55-37-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and the device will boot stock. Wiped it and followed the usual steps to root it. Once I apply Magisk or dm_verity disabler there is a bootloop. Could anyone please provide the steps needed to root and prevent the bootloop. I have tried everything that I can think of. Using Magisk 20.2 and dm_verity 12/27/19. Should I try another version? Thank you.
fireman644 said:
OK I have used the ALI_RETAIL_9.0_PPS29.55-37-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and the device will boot stock. Wiped it and followed the usual steps to root it. Once I apply Magisk or dm_verity disabler there is a bootloop. Could anyone please provide the steps needed to root and prevent the bootloop. I have tried everything that I can think of. Using Magisk 20.2 and dm_verity 12/27/19. Should I try another version? Thank you.
Click to expand...
Click to collapse
According to posts in this thread, one says don't use dm_verity zip and another says edit fstab.qcom. I haven't tired either yet as I'm still on Aug patch with updates "disabled".
Here is how I eventually rooted PPSS29.118-15-11-2:
https://forum.xda-developers.com/showpost.php?p=81229155&postcount=381
I was never able to boot after trying to flash TWRP, so I just didn't bother flashing TWRP. Booting it manually was enough.
I only flashed Magisk-19.4 from TWRP, nothing else. I have no idea if directly flashing a newer Magisk might have worked.
I'm now updated to Magisk-20.3 and everything works.
fireman644 said:
OK I have used the ALI_RETAIL_9.0_PPS29.55-37-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and the device will boot stock. Wiped it and followed the usual steps to root it. Once I apply Magisk or dm_verity disabler there is a bootloop. Could anyone please provide the steps needed to root and prevent the bootloop. I have tried everything that I can think of. Using Magisk 20.2 and dm_verity 12/27/19. Should I try another version? Thank you.
Click to expand...
Click to collapse
For the installation of Magisk I used the .zip v19.3 because the latest (v20.3) caused a bootloop.
Here are the steps that worked for me:
1.) Boot into TWRP and copy the fstab.qcom from /vendor/etc
2.) Edit fstab.qcom like this:
line 9: forceencrypt=/dev/block/bootdevice/by-name/metadata => encryptable=/dev/block/bootdevice/by-name/metadata
This will remove forceencryption and will only work if you format /data!! But you should do this anyway before flashing the magisk.zip
3.) Replace the fstab.qcom in/vendor/etc with the edited one. Be sure the permissions are 0644 (rw-r--r--). To change it open the terminal command and type
Code:
chmod 0644 /vendor/etc/fstab.qcom
4.) Flash the magisk.zip to install Magisk
During the installation process Magisk will remove dm-verity
5.) Reboot and update Magisk Manager + Magisk to v20.3

Categories

Resources