I have the Droid Turbo xt1254 and have been running CrDroid. Today I tried to flash SuperSU 2.76 so I could access the app but I'm getting stuck with a bootloop at the Motorola Disclaimer page. I tried to enter TWRP through recovery and it gives me the splash screen and then goes into a Motorola Disclaimer bootloop. I'm pretty stuck here, as I can't event get into TWRP to reformat my phone. Any help would be greatly appreciated.
mbguitarman said:
I have the Droid Turbo xt1254 and have been running CrDroid. Today I tried to flash SuperSU 2.76 so I could access the app but I'm getting stuck with a bootloop at the Motorola Disclaimer page. I tried to enter TWRP through recovery and it gives me the splash screen and then goes into a Motorola Disclaimer bootloop. I'm pretty stuck here, as I can't event get into TWRP to reformat my phone. Any help would be greatly appreciated.
Click to expand...
Click to collapse
You can get into TWRP through ADB fastboot commands.
When you do so, you would want to flash the NEWEST SuperSu that is compatible with Nougat ROMs. 2.76 is OLD. That incompatible older version of SuperSU is most likely the cause of your problem...
ChazzMatt said:
You can get into TWRP through ADB fastboot commands.
When you do so, you would want to flash the NEWEST SuperSu that is compatible with Nougat ROMs. 2.76 is OLD. That incompatible older version of SuperSU is most likely the cause of your problem...
Click to expand...
Click to collapse
Not quite correct, the newer versions, 2.79 or 2.79 SR1, cause the same issue too.
mangojain said:
Not quite correct, the newer versions, 2.79 or 2.79 SR1, cause the same issue too.
Click to expand...
Click to collapse
Those are old also. Nougat is now on 7.1.2.
When I wrote that and even today, SuperSU-v2.79-SR3 is the newest. But I didn't want to list a specific version because 2 or 3 months from now it also maybe outdated.
Flash the newest SuperSu. That's what I said.
Is that so hard?
Why do you keep trying to flash older ones? Are you trying each one up the steps or something? Just jump to the newest and stop complaining.
Right now this is the newest...
SR3-SuperSU-v2.79-SR3-20170114223742.zip
But 2 or 3 months from now don't complain if it doesn't work. Go find the NEWEST.
Thanks a lot @ChazzMatt this really helped me to recover my phone, just downloaded the latest SuperSU (2.82 at this moment) flashed it and load the full system again.
Cj Marquez said:
Thanks a lot @ChazzMatt this really helped me to recover my phone, just downloaded the latest SuperSU (2.82 at this moment) flashed it and load the full system again.
Click to expand...
Click to collapse
You're welcome!
Super SuperSu 2.82 SR5 I think is the latest. But of course that will change again.
Related
In January I installed SuperSU 2.6.2-3 in accordance with this forum. Interestingly, today I received notification from the Playstore to update SuperSU to 2.65 (dtd Feb 01, 2016). I don't know why I received this notification from the Playstore since I did not install from there and did not receive this notification much earlier. Also, I assume updating to 2.65 through the Playstore would not be a good idea.
Chainfire has recently decided that SuperSU 2.65 was Stable. Only Stable versions get pushed to the Play Store, so that's why you got an update. I believe it will be safe to install, but be sure to make a backup via TWRP first.
Funcionando en Moto g 2015 xt1543 México [MM]
Probé la actualización y todo bien ? OK
TVD1903 said:
Chainfire has recently decided that SuperSU 2.65 was Stable. Only Stable versions get pushed to the Play Store, so that's why you got an update. I believe it will be safe to install, but be sure to make a backup via TWRP first.
Click to expand...
Click to collapse
But my first SuperSU flash was 2.65. And like many others on this forum who did the same, this version soft bricked my phone (stuck on unlocked boot loader screen). Are you saying 2.65 is safe to install on top of 2.6.2-3 but not safe as an initial install?
MrTooPhone said:
But my first SuperSU flash was 2.65. And like many others on this forum who did the same, this version soft bricked my phone (stuck on unlocked boot loader screen). Are you saying 2.65 is safe to install on top of 2.6.2-3 but not safe as an initial install?
Click to expand...
Click to collapse
I think so yes, as the new version was designed as a version to be compatible with every version of Android an to be installed over older versions. Do make a backup though, and if you are afraid, just don't do it. It won't hurt to stay on an older version for a while. You can install the update to the app because that will not immediately install the actual SuperSU update. Do not accept the prompt when opening the app for updating the binary in that case though.
TVD1903 said:
I think so yes, as the new version was designed as a version to be compatible with every version of Android an to be installed over older versions. Do make a backup though, and if you are afraid, just don't do it. It won't hurt to stay on an older version for a while. You can install the update to the app because that will not immediately install the actual SuperSU update. Do not accept the prompt when opening the app for updating the binary in that case though.
Click to expand...
Click to collapse
So what version of SuperSU do you have installed? How did you install that version? On top of a previous version or a fresh TWRP flash?
MrTooPhone said:
So what version of SuperSU do you have installed? How did you install that version? On top of a previous version or a fresh TWRP flash?
Click to expand...
Click to collapse
I am using a Custom ROM with SuperSU built-in. I have however also used the Stock ROM with SuperSU v2.65, installed using TWRP.
Got the same notification, updated fine, updated also su binaries (asked by the app) and - everything works fine. Stock 6.0.
Well I was reluctant to try based on my first experience flashing 2.65. But I accepted the update via Playstore, SuperSU updated the binaries, rebooted, and all is still good.
I would assume all those rooting the G3 MM for the first time should use 2.62-3 then upgrade to 2.65.
MrTooPhone said:
I would assume all those rooting the G3 MM for the first time should use 2.62-3 then upgrade to 2.65.
Click to expand...
Click to collapse
This is how I did mine when following the thread :
[GUIDE] [OSPREY] [MM] Install TWRP, Root and Xposed successfully on 6.0
Installed 2.62-3, then just received the 2.65 from the app store. No problems here either. Not sure about the TWRP update from 2.8.7 r7 to the 3.x.x versions though, but I am getting the impression that due to extensive changes it is not a good idea.
pjc123 said:
This is how I did mine when following the thread :
[GUIDE] [OSPREY] [MM] Install TWRP, Root and Xposed successfully on 6.0
Installed 2.62-3, then just received the 2.65 from the app store. No problems here either. Not sure about the TWRP update from 2.8.7 r7 to the 3.x.x versions though, but I am getting the impression that due to extensive changes it is not a good idea.
Click to expand...
Click to collapse
I have had no issues backing up with twrp-osprey-3.0.0-r2.img. I have not tried restoring yet.
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
pjc123 said:
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
Click to expand...
Click to collapse
don'tn worry ... the update works perfectly ...
..::Matr!x::.. said:
don'tn worry ... the update works perfectly ...
Click to expand...
Click to collapse
Thanks.
pjc123 said:
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
Click to expand...
Click to collapse
I have received several updates since 2.62-3. All have installed from playstore just fine including 2.79. As an initial installation, I think 2.62-3 was the only one that installed as systemless without forcing a systemless installation. Once you have a successful installation, all updates should be as well.
Sorry I'm not able to help you but you can help me. I soft brick my Moto g xt2541 twice due to different super su and wrong recoveries . Can you please provide me links u used to root. My issue is listed here. http://forum.xda-developers.com/2015-moto-g/help/unable-to-root-moto-g-2015-1-gb-model-t3523471 your help is much appriciated
Sent from my MotoG3 using Tapatalk
mirpuri said:
Sorry I'm not able to help you but you can help me. I soft brick my Moto g xt2541 twice due to different super su and wrong recoveries . Can you please provide me links u used to root. My issue is listed here. http://forum.xda-developers.com/2015-moto-g/help/unable-to-root-moto-g-2015-1-gb-model-t3523471 your help is much appriciated
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I followed these directions eleven months ago for the initial unlock bootloader, TWRP recovery and root, using the versions of SuperSU and TWRP listed, however I did not install Xposed.
http://forum.xda-developers.com/201...twrp-root-xposed-t3294588:confused::confused:
I have since updated to:
SuperSU 2.79
TWRP 3.0.2-r1
Caveat: My phone is a XT1540.
Hello Friends,
I have tried to root my OPO running on cos 13 through TWRP. Unfortunately the rooting failed and the phone failed to start, It hangs in "cyanogen mod ready " boot animation screen. some how I have managed to flash the phone to stock OS and again updated it to COS 13.
Now I would like to root the phone , Please someone provide me the right SUPERSU link !
so that I can use it through TWRP.
P.S: The bootloader is already Unlocked.
Thanks in advance :good:
I'm dealing with the same problem, and I've had to flash the system partition back to 5.1.1 and then upgrade to 6.0.1 3 times. Each time I try installing different versions of SuperSU It hangs. Apparently you aren't supposed to install it, and enable root from the developer options, but I don't have any such option.
srink.007 said:
Hello Friends,
I have tried to root my OPO running on cos 13 through TWRP. Unfortunately the rooting failed and the phone failed to start, It hangs in "cyanogen mod ready " boot animation screen. some how I have managed to flash the phone to stock OS and again updated it to COS 13.
Now I would like to root the phone , Please someone provide me the right SUPERSU link !
so that I can use it through TWRP.
P.S: The bootloader is already Unlocked.
Thanks in advance :good:
Click to expand...
Click to collapse
squigley said:
I'm dealing with the same problem, and I've had to flash the system partition back to 5.1.1 and then upgrade to 6.0.1 3 times. Each time I try installing different versions of SuperSU It hangs. Apparently you aren't supposed to install it, and enable root from the developer options, but I don't have any such option.
Click to expand...
Click to collapse
You need to flash the beta sytemless SU, downloads are at the bottom of this post. Latest is BETA-SuperSU-v2.67-20160121175247.zip - http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Ok, so I found a Beta version of SuperSU 2.7.1, and it seems to have worked. It was a different install process, saying it detected a "systemless root" or something, and it needed to patch the boot image. After that I appear to have root access again..
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Edit: Whoops, guess I should have refreshed the page before posting.. What you said is correct Ken.
Thank you
kenboyles72 said:
You need to flash the beta sytemless SU, downloads are at the bottom of this post. Latest is BETA-SuperSU-v2.67-20160121175247.zip - http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
thanks a lot
DONE
http://imgur.com/hh3qkdxGuys Finally I have done it. Yes the phone is rooted now
1. Flash Stock COS 12
2.Update Stock COS 13 using stock recovery
3. Installed SUPERSU (chainfire) from Play Store
3. Install TWRP
4. Create NANDROID BACKUP (optional , I have created since I doubted the rooting process on cos 13)
5. Installed Latest STABLE SUPERSU ( V 2.65 as of now) {my last attempt with beta 2.71 failed }
6. Done
http://imgur.com/hh3qkdx
I used Wugfresh's Bacon Root Toolkit to root my phone. I unlocked my bootloader and rooted my phone correctly and even got a confirmation by the toolkit saying that my phone was successfully rooted. However, my phone has been stuck on the CYANOGEN MOD READY for the last 30 minutes. How do I fix this?!
yqazi27 said:
I used Wugfresh's Bacon Root Toolkit to root my phone. I unlocked my bootloader and rooted my phone correctly and even got a confirmation by the toolkit saying that my phone was successfully rooted. However, my phone has been stuck on the CYANOGEN MOD READY for the last 30 minutes. How do I fix this?!
Click to expand...
Click to collapse
You should never use toolkits for rooting!
Now you need to flash TWRP recovery and flash any stock/custom rom as you like.
Flashing recovery wouldn't be much of a issue as your bootloader is already unlocked.
Mr.Ak said:
You should never use toolkits for rooting!
Now you need to flash TWRP recovery and flash any stock/custom rom as you like.
Flashing recovery wouldn't be much of a issue as your bootloader is already unlocked.
Click to expand...
Click to collapse
Darn
I tried using fastboot to install TWRP and I used TWRP to flash SuperSU. After rebooting, I had the same problem.
My phone is running CyanogenOS 13.1
yqazi27 said:
Darn
I tried using fastboot to install TWRP and I used TWRP to flash SuperSU. After rebooting, I had the same problem.
My phone is running CyanogenOS 13.1
Click to expand...
Click to collapse
Fek all that;
Just use kingoroot or kingroot(google it).
Make sure you've a fast connection.
And if you want to change from kinguser to supersu,use this guide..
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965
Mr.Ak said:
Fek all that;
Just use kingoroot or kingroot(google it).
Make sure you've a fast connection.
And if you want to change from kinguser to supersu,use this guide..
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965
Click to expand...
Click to collapse
I tried installing it but KINGROOT says there is no adaptation(root) available for A0001 Oneplus One
yqazi27 said:
I tried installing it but KINGROOT says there is no adaptation(root) available for A0001 Oneplus One
Click to expand...
Click to collapse
Use kingoroot latest version.
I'm sure one of it will work.
Mr.Ak said:
Use kingoroot latest version.
I'm sure one of it will work.
Click to expand...
Click to collapse
KINGOROOT didn't work either
yqazi27 said:
KINGOROOT didn't work either
Click to expand...
Click to collapse
Ok so I flashed back to CyanogenOS 11 and installed root and it worked. Then I went into TWRP and installed the CyanogenOS 13 zip. My device booted but my root access was gone. How do I update from COS 11 to COS 13 and still retain root? Also, TWRP asked to install SuperSU to root. I clicked no since my device was already rooted. Should I try again and click yes?
yqazi27 said:
Ok so I flashed back to CyanogenOS 11 and installed root and it worked. Then I went into TWRP and installed the CyanogenOS 13 zip. My device booted but my root access was gone. How do I update from COS 11 to COS 13 and still retain root? Also, TWRP asked to install SuperSU to root. I clicked no since my device was already rooted. Should I try again and click yes?
Click to expand...
Click to collapse
No,the root will not survive a clean flash.
Why don't you root cos13.1.x with twrp?
Mr.Ak said:
No,the root will not survive a clean flash.
Why don't you root cos13.1.x with twrp?
Click to expand...
Click to collapse
First of all, I did a dirty flash. Second if I SuperSU zip from TWRP while running COS13.1.2, my device gets stuck in a bootloop.
yqazi27 said:
First of all, I did a dirty flash. Second if I SuperSU zip from TWRP while running COS13.1.2, my device gets stuck in a bootloop.
Click to expand...
Click to collapse
Dirty flash of what?
I'm not talking about SuperSu.zip,Twrp has inbuilt root script,use that.
Flashing SuperSU will cause bootloop in Cm13 buddy.
Kalyan nath said:
Flashing SuperSU will cause bootloop in Cm13 buddy.
Click to expand...
Click to collapse
Are you sure you used latest SuperSU?
giaur said:
Are you sure you used latest SuperSU?
Click to expand...
Click to collapse
Yeah.
are you getting a bootloop or stuck at OnePlus bootlogo? i had a similar problem with SuperSU 2.78 and 2.79 besides i use MultiROM. after flashing a new 7.X ROM and SuperSU i got stuck at OPOs bootlogo.
by the way: never use toolkits
Sent from my One
Here are the steps to root the Moto G4 (Plus) on Android 7.0 with SuperSU.
1. Unlock your bootloader with the Code you can receive from Motorola. Further instructions: unlocking bootloader. You have to create a Motorola account first.
2. Flash TWRP 3.0.2.0 through bootloader. Download and how-to-flash: twrp athene
3. Backup partitons in TWRP (especially the boot-partition)
4. Flash Kernel ElementalX through TWRP. Download and further information: ElementalX
5. Wipe Cache and ART-Cache through TWRP (don't know if necessary but doesn't harm)
6. Flash SuperSU v2.79 SR3 through TWRP. Download SR3-SuperSU-v2.79-SR3-20170114223742.zip: SuperSUv2.79SR3.
SuperSU v2.79 SR3 (or newer) will flash as systemless by default on Motorola devices running Android 6+. Older versions of SuperSU won't do that without creating a config file .supersu in /data containing the line
Code:
SYSTEMLESS=true
So the best is to make sure you don't use an older version of SuperSU than 2.79 SR3!
That's it and it works. SuperSU.apk is going to be installed in step 6.
Successfully tested with XT1642, XT1622 (eta82), XT1643 (Adarsh balu), XT1644 (WTF?), XT1641 (EkisDeMX).
It's the same old guide man. Please see before posting if similar threads exist. XDA is getting confusing for the common non-techie person anyways.
Works perfect on Moto g4 (XT1622) :good:
I've tried to install SuperSU before and it didn't work on my device XT1640. I've got a bootloop and had to flash stock ROM (now I'm using another supersu). Does it really work now? Cuz I don't want to get a bootloop again and lose all my data.
Dex5er said:
I've tried to install SuperSU before and it didn't work on my device XT1640. I've got a bootloop and had to flash stock ROM (now I'm using another supersu). Does it really work now? Cuz I don't want to get a bootloop again and lose all my data.
Click to expand...
Click to collapse
You have to use SuperSU v2.79 SR3. If you use any older version, it won't install systemless and causes bootloops.
Which version of SuperSU did you flash?
And you have to flash ElementalX kernel before installing SuperSU. Otherwise you will get bootloop too.
tywinlannister7 said:
It's the same old guide man. Please see before posting if similar threads exist. XDA is getting confusing for the common non-techie person anyways.
Click to expand...
Click to collapse
Didn't find any thread which describes the method rooting with SuperSU in the first post and as its topic.
In some threads (with other topics like how to root with phh's SuperUser) there is in the discussion mentioned this method with SuperSU but nobody will ever find these posts...
disguisedview said:
You have to use SuperSU v2.79 SR3. If you use any older version, it won't install systemless and causes bootloops.
Which version of SuperSU did you flash?
And you have to flash ElementalX kernel before installing SuperSU. Otherwise you will get bootloop too.
Click to expand...
Click to collapse
I've installed ElementalX Kernel first then I installed SuperSU and I've got a bootloop. I used SuperSU v2.62 and got a bootloop, then I tried with SuperSU v2.74 and also got a bootloop.
Dex5er said:
I've installed ElementalX Kernel first then I installed SuperSU and I've got a bootloop. I used SuperSU v2.62 and got a bootloop, then I tried with SuperSU v2.74 and also got a bootloop.
Click to expand...
Click to collapse
Ok, seems to be the reason. You have to use version 2.79 SR3 or newer if available.
Otherwise it won't work without further modification...
disguisedview said:
Ok, seems to be the reason. You have to use version 2.79 SR3 or newer if available.
Otherwise it won't work without further modification...
Click to expand...
Click to collapse
Alright, is there any problem if I unroot my device with this supersu and root again with the SuperSU that you said, will I get any problem? Do I have to reinstall ElementalX Kernel and twrp again?
Dex5er said:
Alright, is there any problem if I unroot my device with this supersu and root again with the SuperSU that you said, will I get any problem? Do I have to reinstall ElementalX Kernel and twrp again?
Click to expand...
Click to collapse
I don't know. If you have backup of your partitions then flash your original system and boot partition and start from beginning (ElementalX and then SuperSU 2.79 SR3).
If you don't have backups then download (here on xda or somewhere else) stock firmware and flash system und boot partition.
I am currently using the resurrection remix ROM on my moto g4 plus....and my turbo charging is not working...is there anything that I can do to fix this
Asish.pradhan said:
I am currently using the resurrection remix ROM on my moto g4 plus....and my turbo charging is not working...is there anything that I can do to fix this
Click to expand...
Click to collapse
Is it really not working? Or it just doesn't show the popup "TurboPower connected"?
does it work on XT1643 Indian variant ?
---------- Post added at 04:44 PM ---------- Previous post was at 04:40 PM ----------
Asish.pradhan said:
I am currently using the resurrection remix ROM on my moto g4 plus....and my turbo charging is not working...is there anything that I can do to fix this
Click to expand...
Click to collapse
Turbo Power worked fine in my device when using the Ressuruction Rom. Probably restarting the device would solve the issue.
I checked the power input using ampere..its working fine..thnks every1
disguisedview said:
Here are the steps to root the Moto G4 (Plus) on Android 7.0 with SuperSU.
1. Unlock your bootloader with the Code you can receive from Motorola. Further instructions: unlocking bootloader. You have to create a Motorola account first.
2. Flash TWRP 3.0.2.0 through bootloader. Download and how-to-flash: twrp athene
3. Backup partitons in TWRP (especially the boot-partition)
4. Flash Kernel ElementalX through TWRP. Download and further information: ElementalX
5. Wipe Cache and ART-Cache through TWRP (don't know if necessary but doesn't harm)
6. Flash SuperSU v2.79 SR3 through TWRP. Download SR3-SuperSU-v2.79-SR3-20170114223742.zip: SuperSUv2.79SR3.
SuperSU v2.79 SR3 (or newer) will flash as systemless by default on Motorola devices running Android 6+. Older versions of SuperSU won't do that without creating a config file .supersu in /data containing the line
Code:
SYSTEMLESS=true
So the best is to make sure you don't use an older version of SuperSU than 2.79 SR3!
That's it and it works. SuperSU.apk is going to be installed in step 6.
Successfully tested with XT1642, XT1622 (eta82).
Click to expand...
Click to collapse
Does it work with XT1643 Indian variant ? Please do let me know .
arpith.pr said:
Here are the steps to root the Moto G4 (Plus) on Android 7.0 with SuperSU.
1. Unlock your bootloader with the Code you can receive from Motorola. Further instructions: unlocking bootloader. You have to create a Motorola account first.
2. Flash TWRP 3.0.2.0 through bootloader. Download and how-to-flash: twrp athene
3. Backup partitons in TWRP (especially the boot-partition)
4. Flash Kernel ElementalX through TWRP. Download and further information: ElementalX
5. Wipe Cache and ART-Cache through TWRP (don't know if necessary but doesn't harm)
6. Flash SuperSU v2.79 SR3 through TWRP. Download SR3-SuperSU-v2.79-SR3-20170114223742.zip: SuperSUv2.79SR3.
SuperSU v2.79 SR3 (or newer) will flash as systemless by default on Motorola devices running Android 6+. Older versions of SuperSU won't do that without creating a config file .supersu in /data containing the line
Does it work with XT1643 Indian variant ? Please do let me know .
Click to expand...
Click to collapse
Nobody confirmed it yet in this thread.
I could it only test with 1642.
But normally i would say it should also work on 1643 variant.
arpith.pr said:
Does it work with XT1643 Indian variant ? Please do let me know .
Click to expand...
Click to collapse
Yes it does work. It is the only way to root stock N on any of the models.
tywinlannister7 said:
Yes it does work. It is the only way to root stock N on any of the models.
Click to expand...
Click to collapse
Thanks
Working on XT1643....
Im making a video on how to do this to make it easier .... For others like me to understand
I can just Reboot to custom recovery, root and then still use my stock recovery?
Could anyone please point out a way to root my phone(in title), as of this day. There are many methods. So I am confused. I recently read about magisk manager, used to root. Does it work? I just wanted to know the latest method, easier one of any. Also can TWRP manager be used to flash recovery in phone or should it be done flashing TWRP. Img, file.
Please forgive me if i posted in wrong section.
Thanks in advance.
enusri said:
Could anyone please point out a way to root my phone(in title), as of this day. There are many methods. So I am confused. I recently read about magisk manager, used to root. Does it work? I just wanted to know the latest method, easier one of any. Also can TWRP manager be used to flash recovery in phone or should it be done flashing TWRP. Img, file.
Please forgive me if i posted in wrong section.
Thanks in advance.
Click to expand...
Click to collapse
Use PC via ADB (fastboot)to flash TWRP. Flash Magisk in recovery, then dl Magisk manager from play store.
Magisk works very well.
This all is assuming your boot loader is unlocked.
Good luck.
melp57 said:
Use PC via ADB (fastboot)to flash TWRP. Flash Magisk in recovery, then dl Magisk manager from play store.
Magisk works very well.
This all is assuming your boot loader is unlocked.
Good luck.
Click to expand...
Click to collapse
So instead of supersu, we use magisk?
And I read somewhere also that using magisk we can still get updates to our phones. Is that right?
Also there is a TWRP manager in play Store can we use it to flash TWRP instead of ADB?
Thanks for the steps though.
enusri said:
So instead of supersu, we use magisk?
And I read somewhere also that using magisk we can still get updates to our phones. Is that right?
Also there is a TWRP manager in play Store can we use it to flash TWRP instead of ADB?
Thanks for the steps though.
Click to expand...
Click to collapse
My experience with TWRP manager has been it breaks my recovery. No idea why so I flashed via PC. Not sure you can still receive updates when your boot loader has been unlocked. Depends on a lot of factors. Someoneelse will have to answer that question.
melp57 said:
My experience with TWRP manager has been it breaks my recovery. No idea why so I flashed via PC. Not sure you can still receive updates when your boot loader has been unlocked. Depends on a lot of factors. Someoneelse will have to answer that question.
Click to expand...
Click to collapse
OK thanks.
An unlocked bootloader doesn't prevent you from receiving updates from Motorola. But I think rooting the ROM will prevent installation of further updates.
I don't think Motorola is going to push any further updates. So just do anything you want with your phone (personal opinion).
bin.sayantan said:
An unlocked bootloader doesn't prevent you from receiving updates from Motorola. But I think rooting the ROM will prevent installation of further updates.
I don't think Motorola is going to push any further updates. So just do anything you want with your phone (personal opinion).
Click to expand...
Click to collapse
I've never received a update notice.
I would have to agree... There is little chance of getting another update, and if we did it would just be a simple security update and not important.
And no, even with Magisk you cannot apply an OTA update, it will fail.
Unlock your bootloader, flash the twrp recovery using adb fastboot...then wipe the stock rom, flash custom rom along with SuperSU....enjoy! (Processes are same but you should use the latest versions of all these...)
https://forum.xda-developers.com/2015-moto-g/general/guide-osprey-moto-g3-begin-how-to-t3599251