Hello all, I apologize in advance if this is a no brainer answer but I'm new to the idea of rooting my phone and am curious on something.
Can I just root my device to gain some of the functional advantages and not have to flash a ROM? I may consider something down the road but I'm curious about just rooting it so I can do some tings that I can't do otherwise.
Thank you in advance to anyone willing to answer!
Yup...
betterwithfetter said:
Hello all, I apologize in advance if this is a no brainer answer but I'm new to the idea of rooting my phone and am curious on something.
Can I just root my device to gain some of the functional advantages and not have to flash a ROM? I may consider something down the road but I'm curious about just rooting it so I can do some tings that I can't do otherwise.
Thank you in advance to anyone willing to answer!
Click to expand...
Click to collapse
Yes, you can just root it. Once completed, you'll be stock, rooted.
Sent from my SM-N920P using Tapatalk
LMMT said:
Yes, you can just root it. Once completed, you'll be stock, rooted.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you for the response. Whats the best root method out there for this phone?
betterwithfetter said:
Thank you for the response. Whats the best root method out there for this phone?
Click to expand...
Click to collapse
My personal preference:
Download TWRP 3.0, SuperSU 2.52, and freeza's BeastMode kernel. Place BeastMode and SuperSU 2.52 on your phones SD card.
Using Odin on a PC, place the TWRP.img file in the PDA slot. Unchecked auto reboot, boot phone into download mode, and plug it into the PC. Select "start." Once TWRP has successfully flashed (should only take a few seconds, but give it 30 seconds, to be sure the process is complete). Once you're certain that the flash is complete, unplug the phone from the computer, and pull the phones' battery. Reinsert the battery, press and hold the home button, and the volume up button. While continuing to hold them, press the power button. The phone should boot into TWRP, and you can release the buttons. From within TWRP, flash the BeastMode kernel, and SuperSu 2.52, that you previously downloaded. Reboot your phone. You are now stock odexed rooted.
Sent from my SM-N920P using Tapatalk
LMMT said:
My personal preference:
Download TWRP 3.0, SuperSU 2.52, and freeza's BeastMode kernel. Place BeastMode and SuperSU 2.52 on your phones SD card.
Using Odin on a PC, place the TWRP.img file in the PDA slot. Unchecked auto reboot, boot phone into download mode, and plug it into the PC. Select "start." Once TWRP has successfully flashed (should only take a few seconds, but give it 30 seconds, to be sure the process is complete). Once you're certain that the flash is complete, unplug the phone from the computer, and pull the phones' battery. Reinsert the battery, press and hold the home button, and the volume up button. While continuing to hold them, press the power button. The phone should boot into TWRP, and you can release the buttons. From within TWRP, flash the BeastMode kernel, and SuperSu 2.52, that you previously downloaded. Reboot your phone. You are now stock odexed rooted.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Wow that sounds interesting. I will be checking that out for sure. Thank you very much!
betterwithfetter said:
Wow that sounds interesting. I will be checking that out for sure. Thank you very much!
Click to expand...
Click to collapse
It's not nearly as complicated as it sounds.
Sent from my SM-T700 using Tapatalk
It has to be SuperSU 2.52 correct?
Sent from my SM-N910P using Tapatalk
gimmezell said:
It has to be SuperSU 2.52 correct?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
No it doesn't have to be that version but the official SuperSU thread will be the place to learn which version you should flash. And you MUST flash the kernel BEFORE you flash SuperSU. Do not flash superSU before flashing the root permissive kernel. That's the only thing that wasn't specifically pointed out in the instructions above.
Related
Hi all, I'm new here (great place, very informative) and pretty new to the Android scene in general.
As the title said, My AT&T S4 won't boot to recovery after I flashed 4.3 JWR663. Worked fine before and 4.3 is working great, but I can't get to TWRP. When I hold "power + volume up" I get the blue text dialog indicating its going to boot to recovery and the phone just shuts off. I can boot to download mode, but haven't done anything out of fear. I'm not rooted (which is what I'd like to do once this is fixed).
Should I try and re-flash TWRP? Any other suggestions? Feel free to break it down like you're talking to a child. Thanks in advance.
Try flashing it. Get goomanager from the play store. Open it and hit the menu button. Hit install openrecoveryscript.
Sent from my SGH-I337 using xda premium
graydiggy said:
Try flashing it. Get goomanager from the play store. Open it and hit the menu button. Hit install openrecoveryscript.
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
Will that work without root?
Vikingod said:
Will that work without root?
Click to expand...
Click to collapse
You'll need root to flash a recovery with GooManager.
How did you install 4.3? I assume that it's a custom 4.3 as I don't think it has been officially released yet. If it's custom, I'd assume that the ROM had been rooted as well...
theSpam said:
You'll need root to flash a recovery with GooManager.
How did you install 4.3? I assume that it's a custom 4.3 as I don't think it has been officially released yet. If it's custom, I'd assume that the ROM had been rooted as well...
Click to expand...
Click to collapse
I was rooted, but the ROM had it removed and I need to flash Chainfire to get it back. But I can't get into recovery to do so. I think the ROM was done by Jah0n
Is it safe to flash TWRP with Odin now? If so, could you point me to the directions to help me do so. Thanks again for the help.
Found a fix!
My recovery is fine. All I did was power down, try to boot into recovery with "power + volume up + home" and just when the phone vibrated to boot into recovery, I let go of the power button but continued holding the other buttons. It booted into TWRP just fine.
Vikingod said:
Found a fix!
My recovery is fine. All I did was power down, try to boot into recovery with "power + volume up + home" and just when the phone vibrated to boot into recovery, I let go of the power button but continued holding the other buttons. It booted into TWRP just fine.
Click to expand...
Click to collapse
Yep, that's the way you're supposed to get into recovery.
I an able to get in with only power+vol up. Both work for me.
Sent from my SGH-I337 using xda premium
Vikingod said:
Hi all, I'm new here (great place, very informative) and pretty new to the Android scene in general.
As the title said, My AT&T S4 won't boot to recovery after I flashed 4.3 JWR663. Worked fine before and 4.3 is working great, but I can't get to TWRP. When I hold "power + volume up" I get the blue text dialog indicating its going to boot to recovery and the phone just shuts off. I can boot to download mode, but haven't done anything out of fear. I'm not rooted (which is what I'd like to do once this is fixed).
Should I try and re-flash TWRP? Any other suggestions? Feel free to break it down like you're talking to a child. Thanks in advance.
Click to expand...
Click to collapse
Did you try manually booting into recovery with the power and volume button?
quattros said:
Did you try manually booting into recovery with the power and volume button?
Click to expand...
Click to collapse
He fixed his problem a few posts ago...
Sent from my SGH-I337 using xda premium
I have an older phone and after flashing the twrp recovery it won't let me boot into recovery mode at all can someone please give some advice on how I should fix this?
Which phone do you have?
An Alcatel One touch POP D3 4037A
Try using the Alcatel mobile tool to flash back to stock.
TWRP doesn't work
My LG G3 running lineage os 14.1 won't boot into TWRP.
graydiggy said:
He fixed his problem a few posts ago...
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
The blue and black screen start up screen comes up. But it stays like this. This happened since I flashed the lineage ROM. What should I do?
my phone agua rio 4.4.2 kitkat .
After flashing twrp recovery img .
After rebooting it .twrp not installed and it only reboot normal i didnt get to twrp recovery
Need solution pls pls
This thread is about the Samsung Galaxy s4.
Hi there. I'm new of this forum and even of the Android customization scenario. I have a Samsung Galaxy s4 i-9505 with 5.0.1 firmware and build LRX22C.I9505XXUHPK2. I've tried to install TWRP with Odin3 (so without root my phone) and all the procedure goes well. After reboot, I have turned-off my phone and I've tried to enter in the TWRP's recovery mode (using the combo buttons: VolumeUP + Home button + Power button) but the "TEAMWIN" logo didn't appear and the normal "Android Recovery Menu" were visualized.
I need some help to undestand if I did some mistakes during the flashing process. I've used the last versione of TWRP (3.1.1-0 for jfltexx). Any help will be appreciated. Thanks for your attention to this matter.
If you want to root with TWRP, try this for the gt-i9505:
open Odin 3.07 and uncheck everything except r reset time;
download the tar version of twrp for the gt-i9505: https://dl.twrp.me/jfltexx/
download the latest version of supersu.zip and copy it to an sd card or the phone's internal storage: http://www.supersu.com/download;
place the sd card in the phone if twrp has been saved to the sd card from the step above;
connect the phone in download mode and flash twrp in Odin's PDA slot;
when you see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery, install supersu.zip, reboot.
If you just want to install a custom ROM, copy the ROM to the internal or external sd card, install twrp, and install the ROM. Root is not required to install a custom ROM, only a custom recovery.
Warning: whenever you flash anything to a phone, it is always possible for something to go wrong and you must be prepared to deal with any consequences. I have used this method for several note 2, note 3, s3, and s4 phones without any issues. With this being said, I can't guarantee that the above steps will work for your phone or your phone won't be bricked.
Hi!
I'm totally new to Nexus 4. I'm on 4.3 and yesterday unlocked bootloader and rooted. Everything works.
Today I booted in fastboot just to see CWM. On exiting it warned me about possible root lost. I answered YES.
So now I lost root. I still have SuperSU but when I run it I get message that no binaries installed and SU can't install them and I need to reroot phone...
I tried to download chainfire 1.65 zip and flash it CWM - same result...
Any hints would be appreciated!
Sent from my Nexus 4 using xda app-developers app
Goldenmeadow said:
Hi!
I'm totally new to Nexus 4. I'm on 4.3 and yesterday unlocked bootloader and rooted. Everything works.
Today I booted in fastboot just to see CWM. On exiting it warned me about possible root lost. I answered YES.
So now I lost root. I still have SuperSU but when I run it I get message that no binaries installed and SU can't install them and I need to reroot phone...
I tried to download chainfire 1.65 zip and flash it CWM - same result...
Any hints would be appreciated!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Try flashing TWRP.
Pipusz said:
Try flashing TWRP.
Click to expand...
Click to collapse
Ok, I'll try.
But am I accessing CWM properly? Do I have to go through fastboot?
My last phone had button combination to boot straight into recovery. I don't see such option in Nexus 4.
Thanks again!
Sent from my Nexus 4 using xda app-developers app
Goldenmeadow said:
Ok, I'll try.
But am I accessing CWM properly? Do I have to go through fastboot?
My last phone had button combination to boot straight into recovery. I don't see such option in Nexus 4.
Thanks again!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Is there an option in your current ROM to reboot into recovery? If not, power off the device, then hold down the volume up-down and the power buttons. I tend to forget these button combinations, but I think this is the one that will lead you to fastboot. From there, navigate with the volume buttons and OK something with the power button.
Pipusz said:
Is there an option in your current ROM to reboot into recovery? If not, power off the device, then hold down the volume up-down and the power buttons. I tend to forget these button combinations, but I think this is the one that will lead you to fastboot. From there, navigate with the volume buttons and OK something with the power button.
Click to expand...
Click to collapse
Thanks for reply!
Sorry I forgot to give tech details: I run stock ROM + kernel, just rooted and unlocked fastboot.
So yes, this is the way I use to access recovery: through fastboot.
Last time while exiting CWM I selected NO to last question about trying to fix root and my root is still here
Thanks for help again!
Sent from my Nexus 4 using xda app-developers app
Goldenmeadow said:
Thanks for reply!
Sorry I forgot to give tech details: I run stock ROM + kernel, just rooted and unlocked fastboot.
So yes, this is the way I use to access recovery: through fastboot.
Last time while exiting CWM I selected NO to last question about trying to fix root and my root is still here
Thanks for help again!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Glad to hear that. If it's OK, leave it that way, it won't cause any harm.
If you want to try TWRP, go to the Play Store and download the GooManager application. Grant it superuser permission, then hit the menu button at the upper-right side of the screen, right under the clock. From there, select "Install OpenRecoveryScript" and it will download and flash the latest TWRP on your device. After that, reboot to recovery to check if it's working.
I just went throught the same thing
I just unlocked my phone and flashed the latest CWM recovery and then the latest SuperSU zip; and all was fine. But whenever I was exiting from CWM recovery, it said "Possible root access loss" and if it can "fix it". Whenever I say "Yes" I lose root access; and when I select "No" the root privileges stayed. I could have lived with that but I thought screw this **** and flashed the TWRP recovery. This one doesn't say anything about losing access; all's cool.
But I still want to know what CWM was trying to do. It was trying to "fix" /system/bin/su and losing root access. Anybody?
crossjaw said:
I just unlocked my phone and flashed the latest CWM recovery and then the latest SuperSU zip; and all was fine. But whenever I was exiting from CWM recovery, it said "Possible root access loss" and if it can "fix it". Whenever I say "Yes" I lose root access; and when I select "No" the root privileges stayed. I could have lived with that but I thought screw this **** and flashed the TWRP recovery. This one doesn't say anything about losing access; all's cool.
But I still want to know what CWM was trying to do. It was trying to "fix" /system/bin/su and losing root access. Anybody?
Click to expand...
Click to collapse
cwm is most likely installing a su that isnt up to date
simms22 said:
cwm is most likely installing a su that isnt up to date
Click to expand...
Click to collapse
Oh... I've never had problems with CWM before( this wasn't actually a problem anyway). Thanks
I pulled this from my phone and posted it in the other thread, and someone suggested I make a thread for it. Here it is!
http://j2cool.com/mirror/files/Blur_Version.139.15.1.ghost_verizon.Verizon.en.US.zip
To install, you will need to be on the latest OTA (camera update).
Fastboot flash the original system.img and recovery,img
You can then use the volume down key to select "Recovery"
Once in recovery, press the power button and volume buttons together to bring up the menu,and select "Install from SDcard"
You can then select the OTA, and install it. Your phone will reboot, and you will have to do this again from the new recovery. You should then be able to reboot system and have your new 4.4 Kitkat Moto X!
Sent from my XT1060 using Tapatalk
Whoops. Replied while trying to edit. Mobile forum use is a pain.
Sent from my XT1060 using Tapatalk
Chrome says this file is dangerous
km8j said:
Chrome says this file is dangerous
Click to expand...
Click to collapse
Chrome is smart, Chrome knows a Verizon update image is too good to be true :laugh:
What's the install method for VZW Dev Ed?
Flash system.img but not boot.img?
Mercutio5 said:
What's the install method for VZW Dev Ed?
Flash system.img but not boot.img?
Click to expand...
Click to collapse
You don't need boot.img in either. Now, I don't know how the dev ed works, maybe it's just the exact same with an unlocked bootloader, so let me know how installing goes.
km8j said:
Chrome says this file is dangerous
Click to expand...
Click to collapse
Because it's a large zip file from somewhere no one has downloaded before. I promise you, it's safe and clean though.
Mercutio5 said:
What's the install method for VZW Dev Ed?
Flash system.img but not boot.img?
Click to expand...
Click to collapse
Dev edition you can install like any other device. The benefit is that you can flash custom files without recovery flipping its ****.
Sent from my XT1080MDEV.
Will this work on GSM dev edition?
tesselator said:
Will this work on GSM dev edition?
Click to expand...
Click to collapse
Only if you want to break your phone.
This is for Verizon.
Whats the procedure for flashing this on a rooted verizon dev edition
Gs0230 said:
Whats the procedure for flashing this on a rooted verizon dev edition
Click to expand...
Click to collapse
Put the zip in internal storage. Go into stock recovery, install zip, choose this update zip. Because one of the first things it does it flash a new recovery, you have to go into recovery again and install zip again (the second time around it knows it doesn't have to flash the recovery).
Of course, since this way uses stock recovery, you have to be running stock.
I'm on stock just rooted with unlocked bootloader twrp 2.6.3 installed will I lose root
Sent from my XT1060 using XDA Premium 4 mobile app
Gs0230 said:
I'm on stock just rooted with unlocked bootloader twrp 2.6.3 installed will I lose root
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You need to use stock recovery. After the update u can install twrp and root again
Can I keep root and how do i revert to stock recovery
Gs0230 said:
I'm on stock just rooted with unlocked bootloader twrp 2.6.3 installed will I lose root
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, you're going to lose root (the update will wipe out System). If you have an unlocked bootloader then it isn't a big deal -- just re-root after the update.
BUT don't try to flash this update with twrp installed. 1) I'm pretty sure it won't work anyway b/c it needs to verify that your System is stock and, at the very least, installing twrp changes the install-recovery script which is in System 2) this .zip file is made to be flashed from a stock recovery, so I'm not sure it would work 3) as I said before, part of this update is a new recovery - I'm not sure how well the process would go if you started from twrp
And how would I root after its done
Gs0230 said:
And how would I root after its done
Click to expand...
Click to collapse
The same way you rooted before?
I'm sorry, I've been assuming you have a Dev edition b/c you said you had twrp -- is that not the case? If you do NOT have a dev edition and you rooted via pwn- or rock- or whatever its called myMoto then NO, you will NOT be able to root after the update until someone releases another hack
piccit said:
Put the zip in internal storage. Go into stock recovery, install zip, choose this update zip. Because one of the first things it does it flash a new recovery, you have to go into recovery again and install zip again (the second time around it knows it doesn't have to flash the recovery).
Of course, since this way uses stock recovery, you have to be running stock.
Click to expand...
Click to collapse
I got this the second time (with the new recovery):
"Install aborted"
:|
Maybe the battery level is too low, so i'm gonna charge it a little and see what happens
PS: the "normal" OTA is downloading SO slow D: that's why i'm trying the one in this thread
------EDIT----
For some reason the download speed just increased, so i'm staying with it
I cannot flash this in TWRP right?
NOTE: NOW CONFIRMED TESTED AND WORKING FOR THE T817T/W AND T817P MODELS.
Looking for testers with the T817 model (no ATT or Verizon models) to test a new hack to get root on Samsung stock SElinux Enforcing kernels running Android 5.11 or Android 6.0.
This means the kernel will be stock, so LTE will be unaffected.
Basically what this is about:
Chainfire has released new beta's of Supersu, the latest is 2.52. This new release can root Samsung 5.1.1 roms and Android 6.0 Marshmallow roms.
However to accomplish this a patch needs to be applied to the kernel Ramdisk to allow root with stock kernels.
What does this mean? This means if you have a T817 running Lollipop 5.1.1 then you can gain root and retain LTE connectivity as it uses the stock kernel instead of having to flash a permissive T810 wifi only kernel.
I need someone willing to test the patched Ramdisk and kernel on their device which has 5.1.1 installed.
The procedure is fairly simple all that is required is to flash the new boot.img, then root with Supersu v2.52.
Here is the patched boot.img for anyone that wants to test it.
*It goes without saying make a back up with TWRP first! *
FOR SM-T817T/T817W
Extract the boot.img from the zip then Install with TWRP:
Tab_S2_t817_boot.zip
FOR SM-T817P
Extract the boot.img from the zip then Install with TWRP:
Tab_S2_T817P_boot.zip
Then root with BETA-SuperSU-v2.52 using TWRP
I have a t817p I would be happy to test, how do I install twrp without root though?
Sent from my SM-T817P using Tapatalk
saramon said:
I have a t817p I would be happy to test, how do I install twrp without root though?
Sent from my SM-T817P using Tapatalk
Click to expand...
Click to collapse
If you have an SM-T817P I will upload a specific boot.img for you.
You dont need root to install TWRP, just install with ODIN.
Install with TWRP: Tab_S2_T817P_boot.zip
Stock Recovery if required: T817PVPU1AOH6_recovery
Flashed it, and I'm getting LTE
saramon said:
And I eagerly await the upload, I got TWRP installed
Click to expand...
Click to collapse
Important: make a full back up with TWRP first!
saramon said:
Flashed it, and I'm getting LTE
Click to expand...
Click to collapse
Do you have root?
Yup, sure do, got xposed installed too
Sent from my SM-T817P using Tapatalk
saramon said:
Yup, sure do, got xposed installed too
Sent from my SM-T817P using Tapatalk
Click to expand...
Click to collapse
So we can say we have success?
You are the first one to have root and LTE on a 5.1.1 S2 tablet!
Just to be sure, this does work with the Tmobile T817T, correct?
Edit: found answer.
graysooner said:
Just to be sure, this does work with the Tmobile T817T, correct?
Edit: found answer.
Click to expand...
Click to collapse
No idea. Nobody has tested it yet and come back with the answer.
Still waiting...
ashyx said:
So we can say we have success?
You are the first one to have root and LTE on a 5.1.1 S2 tablet!
Click to expand...
Click to collapse
I'd say so, great job!
Willing to try, but a question. If I flash with Odin, is TWRP installed also?
graysooner said:
Willing to try, but a question. If I flash with Odin, is TWRP installed also?
Click to expand...
Click to collapse
You have to flash twrp first. You will find my builds of TWRP in the development section.
Flash the 5.1.1 t810 version.
can't get into twrp
ashyx said:
If you have an SM-T817P I will upload a specific boot.img for you.
You dont need root to install TWRP, just install with ODIN.
[/URL]
Click to expand...
Click to collapse
i flashed the boot patched file odin is successful it says but kernel is not seandroid enforcing and will not boot into twrp, boots into stock recovery still
Aikavaras2015 said:
i flashed the boot patched file odin is successful it says but kernel is not seandroid enforcing and will not boot into twrp, boots into stock recovery still
Click to expand...
Click to collapse
That message is normal.
What you have to do is after flashing twrp you need to directly boot into twrp to prevent the stock recovery overwriting it.
Flash twrp again but disable auto reboot in Odin.
After flashing reboot by holding POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
i did that, still booted into system not twrp
ashyx said:
That message is normal.
What you have to do is after flashing twrp you need to directly boot into twrp to prevent the stock recovery overwriting it.
Flash twrp again but disable auto reboot in Odin.
After flashing reboot by holding POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
Click to expand...
Click to collapse
still no twrp. just goes to stock. I have tried both times with autoreboot off, once with f reset checked and another with f reset unchecked.
Aikavaras2015 said:
still no twrp. just goes to stock. I have tried both times with autoreboot off, once with f reset checked and another with f reset unchecked.
Click to expand...
Click to collapse
Don't mess with f.reset
Honestly this is purely about timing. Plenty have already done it with the same device as you.
As long as you are flashing the correct twrp file then you should be good after following the advice above.
Can you flash twrp then post me a screenshot of odin?
How did you get xposed working?
[/U]
saramon said:
Yup, sure do, got xposed installed too
Sent from my SM-T817P using Tapatalk
Click to expand...
Click to collapse
I have the T715 but can't get xposed to work
LeeLongLang said:
[/U]
I have the T715 but can't get xposed to work
Click to expand...
Click to collapse
Please, this thread is only for testing the above kernels.
Hey guys. Im running stock MM with unlocked bootloader. I was able to flash twrp on but when I try to install superuser 2.46 through twrp I am stuck at the logo screen when I reboot. Is there something else that needs to be done to root this phone?
I also noticed that every time I boot into twrp it prompts me with the "keep system read only?" dialog. I "allow modifications" every time.
I used a systemless root on M. BETA-SuperSU-v2.62-20151210170034 for sure works.
jason2678 said:
I used a systemless root on M. BETA-SuperSU-v2.62-20151210170034 for sure works.
Click to expand...
Click to collapse
Amazing, thank you! This worked for me too. Any idea why the newer versions don't work?
madkapitolist said:
Amazing, thank you! This worked for me too. Any idea why the newer versions don't work?
Click to expand...
Click to collapse
Not really. I think the automation is changing in the newer versions. 2.65 tries to decide between systemless and traditional root somehow. 2.62 definitely works on the mxpe. I've heard 2.64+ do not.
How were you able to flash twrp on MM? I have tried the guides and have not been able to boot into recovery. Any advise?
veuro said:
How were you able to flash twrp on MM? I have tried the guides and have not been able to boot into recovery. Any advise?
Click to expand...
Click to collapse
The only real trick I'm aware of is that you have to boot straight into TWRP from the bootloader. Don't reboot into your rom after fastboot flashing the custom recovery. Use the volume buttons to select start recovery and power button to start it. If you reboot into your stock rom your recovery will get replaced.
Flash SuperSU once you get into recovery, and that should make TWRP "stick".
Some people have said to reboot to recovery from recovery once the first time you boot into TWRP before rebooting to system. I'm not entirely sure that is required, but I did do it and TWRP stayed working for me.
One other thing, every time I've flashed SuperSU 2.62 my phone seems to bootloop once after the moto logo on the first boot. Don't panic. This seems to be normal, just let it go. The second time it will boot normally.
I tried both and it would simply not boot into twrp
Sent from my XT1575 using Tapatalk
veuro said:
I tries both and it would simply not boot into twrp
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Veuro: Are you flashing TWP 2.8.7.1? as soon as you flash and it says ok, open Recovery.
I am flashing just like the guides say.. I'm on MM original rom
Sent from my XT1575 using Tapatalk
Has anyone been successful rooting mm?
Sent from my XT1575 using Tapatalk
Are you unlocked?
Yes I'm unlocked. I finally figured it out using the systemless root guide, but it was a little confusing at first
Sent from my XT1575 using Tapatalk
Would you mind explaining what you did? All of the instructions I've found for systemless root use files associated with variants besides the US version which is what I'm trying to root.
Edit: Never mind figured it out! For those of you that are confused, the only version of SuperSU that works for a stock systemless root is 2.62-3. Simply fastboot TWRP then install that version of SuperSU through TWRP and you're good to go.