i have been following instructions from http://androiding.how/root-moto-x-pure/
i have everything correct once in flash the latest supersu my device freezes at the boot image of moto.
If you're running MM make sure to use a systemless root.
I can vouch for the 2.62 version working on this phone. It is the only version I've tried.
Versions above 2.62 did not work, although I've seen some discussion in the forum that 2.67 is ok.
I'm on stock MM and am running the traditional root version of SuperSU 2.67.
No issues here.
That looks like a really old tutorial, and some of those links may be way out of date.
The bootloader unlock process hasn't changed (since we're pretty much just using Moto's official method), but you'll probably want to grab current versions of TWRP (3.0.0-1) and SuperSU (either 2.65 Stable or 2.67 Beta), IIRC.
Might also be simpler to use a tutorial here on XDA.
Edit: Don't quote me on this, but some older versions of TWRP may not work properly on the MM bootloader. So it could be that the minimum recommended version of TWPR (for 6.0) is newer than whatever is linked to from that old tutorial, which could explain your issue. If that's the case, updating to a newer TWRP via Recovery or Fastboot might just fix your problem.
Mejilan said:
I'm on stock MM and am running the traditional root version of SuperSU 2.67.
No issues here.
Click to expand...
Click to collapse
So you simply flashed SuperSU 2.67 via TWRP and you have fully functional phone and root?
Interesting, as it does not appear to work for everyone...
Yup. I'm not interested in engaging with the systemless root since it's still so experimental and early. I prefer going with a more stable experience.
Titanium Backup and Xposed are part of my bread and butter software environment. If root were broken, I would damn well know, right? Heh.
Gotta have my GravityBox and Enable Ambient Display...
A few weeks ago, I ditched TruPure and followed a Fastboot-heavy guide in order to restore my phone to stock 6.0. Was a pain, but I powered through.
Then I unlocked my bootloader again (with the same code Motorola provided to me months ago), and flashed TWRP 3.0.0 via Fastboot (later updated to 3.0.0-1 via TWRP itself).
Finally I booted into recovery and flashed SuperSU 2.67 beta and Xposed v80. Installed SuperSU Pro from the Play Store, and have been good to go since.
I'm pretty sure that I've been using SuperSU 2.67 for quite some time now, both on TruPure (up to 2.5 before I ditched it) and on stock MM.
I've been updating SuperSU more or less as quickly as Chainfire has been releasing Beta updates, as I'm pretty sure he's been focusing on MM compatibility fixes in recent months.
I didn't realize there were any issues with flashing (though I think TruPure has SuperSU baked in).
i have latest twrp, i didnt bother with the supersu step, but im currently having issues getting turbo charge to work on any rom i tried...
I flashed 2.66 after running commands in terminal to make root systemless & my phone booted normally.
Sent from my Moto X Pure Edition using Tapatalk
Related
Good evening ladys and gentlemen,
hoping you can help me with my root-not staying-problem.
I have the A2017G B09 version. I already managed to unlock my device and I had root with xposed installed.
Sounds good so far, right?
Well my problem is that after the restart that is needed to activate my xposed modules, my root went away and I couldn't get it back. After that I tried to do it again but root wouln't stick no matter what.
And yes, I did use the "reboot disemmcwp" command.
I tried to root by flashing the newest chainfire supersu 2.79, since I have newest twrp 3.0.3-1.
It would be great if you would be able to help me on my journey and maybe explain to me the difference between systemless and normal, and what magisk is since I saw that op up a few times.
Oh and please tell me from where I should start if I want to work on everything android related (roms, kernel, apps) since my semsester is nearing its end.
Thanks in advance.
Systemless root means that the /system partition is not modified, however the boot image is altered. There is much hype on this, however there still are many mods out there requiring modifications of /system. I personally do not see any advantage of it, probably because I have been using custom ROMs for years, and custom ROMs has many alterations to the /system compared to stock or pure CM or AOSP roms. However it is clear that the future goes that way and eventually most of the mods will be systemless. The advantage is that you will supposedly be able to flash OTA upgrades, however if the OTA is also modifying the boot partition, then it doesn't matter, you will not be able to flash the OTA upgrade. So the benefits of systemless mods are arguable.
Magisk is an open root. it is systemless from the beginning and any module under Magisk framework will be systemless. So far no official Magisk release (latest at this time is v10.2) is compatible with the Axon stock ROM. However, the latest v10.3-beta2 seems to fix the root injection problem. It is included in the Bad Boyz custom ROM.
There are some apps not working on root devices. They use a SafetyNet procedure to check for that, such as Android Pay or Pokemon Go. However there are ways to overcome this security check and you can enjoy root and SafetyNet compatibility either using SuperSU or Magisk, system or systemless root. the issue becomes a little tricky when adding Xposed mod framework to the mix, since the procedures to have all 3 (root, SafetyNet and Xposed) working is not that straightforward. However this is possible in the Axon 7. You can find one of my guides in the links in my signature.
Enjoy!!!!
Thanks for the info. I actually used your guide but nothing came out of it. I got stuck on the Axon screen. Tried it multiple times. Guess I'll try again either after the N update or when I get impatient.
Try reflashing supersu don't reboot, then use terminal in TWRP to do reboot disemmcwp and see if it works. I usually use root Explorer to see if I can change /system to r/w. If it did not work go back to terminal in TWRP and try again. I have had to do it a few times to get it to work. Using adb terminal seems to work first time, terminal apps have not worked for me.
Yuujinz said:
Thanks for the info. I actually used your guide but nothing came out of it. I got stuck on the Axon screen. Tried it multiple times. Guess I'll try again either after the N update or when I get impatient.
Click to expand...
Click to collapse
If you tried my guide, then you must use ROM B29 or any other ROM based on B29. I am afraid that the patch is only compatible with B27 or B29 based kernels.
Oki said:
If you tried my guide, then you must use ROM B29 or any other ROM based on B29. I am afraid that the patch is only compatible with B27 or B29 based kernels.
Click to expand...
Click to collapse
Wouldn't it brick my european device?
Yuujinz said:
Wouldn't it brick my european device?
Click to expand...
Click to collapse
You can flash directly the BootStack for your version of Axon 7 and the B29 ROM (or any other custom ROM) using TWRP. You can get those files from https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Oki said:
You can flash directly the BootStack for your version of Axon 7 and the B29 ROM (or any other custom ROM) using TWRP. You can get those files from https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Click to expand...
Click to collapse
Ok thanks I'll do it this evening
Or maybe not, to risky.
So I just updated to the latest xt1644 Nougat JP25.93.14-4 and am having an issue installing TWRP and getting it to stick. I installed it and even did a backup, but once I boot to System and then back to bootloader, and finally to recovery, it goes back to stock recovery. Also I am unsure of how to root this device now with Nougat. I've seen on a few sites differing methods. One site had a download for what they called a root package and it was a SuperSU 2.76 version. Another site said to use Phh SU and just install TWRP and then flash Phh. I don't want to mess anything up, can someone point me in the right direction since it seems everything in this forum is for a device other than the XT1644. Lastly, is it possible to revert back to Marshmellow using fastboot, or is that now not possible? I have unlocked my bootloader, obviously. Thanks.
After flashing TWRP you have to manually boot to TWRP without booting to system first. For rooting you have to flash ElementalX or Vegito Kernel and then flash SuperSU v2.79 SR3 or Magisk v12
.
tywinlannister7 said:
After flashing TWRP you have to manually boot to TWRP without booting to system first. For rooting you have to flash ElementalX or Vegito Kernel and then flash SuperSU v2.79 SR3 or Magisk v12
.
Click to expand...
Click to collapse
I did manually boot it. I went back to bootloader, then choose recovery again and it goes back to TWRP. After I boot to system is when the issue occurs. If I go back to bootloader after booting to system, that is when I have the problem. Once I try to go into recovery again it goes to stack recovery. I am trying to install TWRP 3.0.2.0 Athene.
robn30 said:
I did manually boot it. I went back to bootloader, then choose recovery again and it goes back to TWRP. After I boot to system is when the issue occurs. If I go back to bootloader after booting to system, that is when I have the problem. Once I try to go into recovery again it goes to stack recovery. I am trying to install TWRP 3.0.2.0 Athene.
Click to expand...
Click to collapse
try latest twrp 3.1.0
I got it working. I had originally set it to read only and I think that was the issue. Reinstalled it and mounted system and then choose to allow modifications. It then worked. Now onto root, we will see how that goes.
Sent from my XT1575 using Tapatalk
tywinlannister7 said:
try latest twrp 3.1.0
Click to expand...
Click to collapse
When rooting do you still do the little systemless trick or is that already accounted for. Does the elemental X kernel play well and is it nice and stable? Thanks for the info.
Sent from my XT1575 using Tapatalk
robn30 said:
When rooting do you still do the little systemless trick or is that already accounted for. Does the elemental X kernel play well and is it nice and stable? Thanks for the info.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
If you're using SuperSU v2.79 SR3 beta ( https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133), this already is configured for systemless, and if you're going for SuperSU, that's the version I recommend. Any versions below 2.79 SR3 appear to have created boot issues on Nougat (or required the echo systemless command to work).
ElementalX (1.0.4 stock is what you want) is stable and is essential for rooting. Don't try to root your device without flashing a custom kernel like ElementalX or vegito, else if you try to root the stock Nougat kernel, you'll likely trip anti-root kit/anti-rooting security (dm-verity, I recall?) and will prevent your device from booting. By flashing ElementalX or vegito, you'll bypass that security.
A useful checklist to follow is in this guide here: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 Having a newer version of TWRP shouldn't matter (and in fact may present less issues). With step 6, you may choose to flash either magisk or SuperSU as mentioned by tywinlannister7 (I've not had experience with phh superuser, so cannot comment). If, at some point in the future, you wish to swap rooting methods, I'd suggest following the recommended unrooting procedure for your existing root manager (e.g. unrooting from the SuperSU app settings, or flashing the magisk uninstaller, check their respective pages on XDA) before changing root managers. I've used the aforementioned checklist to root a XT1642 on Nougat without issue.
As for downgrading your system to Marshmallow if you so choose, that is possible. Verify the MM firmware you need (a selection for XT1644, retus channel devices, is here https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/) and use that firmware with a guide like this: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961 If you're using fastboot rather than mfastboot, replace mfastboot in the provided script with fastboot.
EDIT - no worries @pastorbob62 - good to have another member verifying information
robn30 said:
When rooting do you still do the little systemless trick or is that already accounted for. Does the elemental X kernel play well and is it nice and stable? Thanks for the info.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
NO! NO! NO! Do not use the systemless root method. That is for Marshmallow ONLY!. You will not be able to boot into the system after trying that and you may have to go all of the way back to flashing stock from fastboot to fix it.
ElementX-G4 kernel plays well with Nougat stock. I ran it with stock Nougat for a couple of weeks on my XT1625 without any major issues. So flash it from TWRP. Be sure you have the correct version. Then boot to system to check it out. Next reboot to TWRP and flash SuperSU 2.79. Boot back to the system. It will probably boot a couple of times before the system comes up. Don't panic. You should be good to go.
Edit: Sorry echo92. I was typing my reply at the same time you were. :good:
echo92 said:
If you're using SuperSU v2.79 SR3 beta ( https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133), this already is configured for systemless, and if you're going for SuperSU, that's the version I recommend. Any versions below 2.79 SR3 appear to have created boot issues on Nougat (or required the echo systemless command to work).
ElementalX (1.0.4 stock is what you want) is stable and is essential for rooting. Don't try to root your device without flashing a custom kernel like ElementalX or vegito, else if you try to root the stock Nougat kernel, you'll likely trip anti-root kit/anti-rooting security (dm-verity, I recall?) and will prevent your device from booting. By flashing ElementalX or vegito, you'll bypass that security.
A useful checklist to follow is in this guide here: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 Having a newer version of TWRP shouldn't matter (and in fact may present less issues). With step 6, you may choose to flash either magisk or SuperSU as mentioned by tywinlannister7 (I've not had experience with phh superuser, so cannot comment). If, at some point in the future, you wish to swap rooting methods, I'd suggest following the recommended unrooting procedure for your existing root manager (e.g. unrooting from the SuperSU app settings, or flashing the magisk uninstaller, check their respective pages on XDA) before changing root managers. I've used the aforementioned checklist to root a XT1642 on Nougat without issue.
As for downgrading your system to Marshmallow if you so choose, that is possible. Verify the MM firmware you need (a selection for XT1644, retus channel devices, is here https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/) and use that firmware with a guide like this: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961 If you're using fastboot rather than mfastboot, replace mfastboot in the provided script with fastboot.
EDIT - no worries @pastorbob62 - good to have another member verifying information
Click to expand...
Click to collapse
Thanks for all the information, it is very much appreciated. Thanks to pastorbob62 as well. This information will be very useful.
Sent from my XT1575 using Tapatalk
pastorbob62 said:
NO! NO! NO! Do not use the systemless root method. That is for Marshmallow ONLY!. You will not be able to boot into the system after trying that and you may have to go all of the way back to flashing stock from fastboot to fix it.
ElementX-G4 kernel plays well with Nougat stock. I ran it with stock Nougat for a couple of weeks on my XT1625 without any major issues. So flash it from TWRP. Be sure you have the correct version. Then boot to system to check it out. Next reboot to TWRP and flash SuperSU 2.79. Boot back to the system. It will probably boot a couple of times before the system comes up. Don't panic. You should be good to go.
Edit: Sorry echo92. I was typing my reply at the same time you were. :good:
Click to expand...
Click to collapse
One other thing, can I back up the stock kernel? Or at least find it somewhere for download. Is this something I can backup using TWRP? Thanks again.
Sent from my XT1575 using Tapatalk
robn30 said:
One other thing, can I back up the stock kernel? Or at least find it somewhere for download. Is this something I can backup using TWRP? Thanks again.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Got it figured out. Backing up my boot.img via TWRP ensures my stock kernel is safe. Already installed elemental X and SuperSU and all went perfectly smooth. Thanks again for the links.
Sent from my XT1575 using Tapatalk
robn30 said:
Got it figured out. Backing up my boot.img via TWRP ensures my stock kernel is safe. Already installed elemental X and SuperSU and all went perfectly smooth. Thanks again for the links.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
You are very welcome. Glad you got it figured out and all is working well. :good:
Hey guys... I know I am late to the thread but if you see this, can you inform me how can I receive updates afterwards? I currently have twrp with elementx kernel and Magisk. And there is a security patch out for the phone. How can I install that?
1emrys1 said:
Hey guys... I know I am late to the thread but if you see this, can you inform me how can I receive updates afterwards? I currently have twrp with elementx kernel and Magisk. And there is a security patch out for the phone. How can I install that?
Click to expand...
Click to collapse
Generally you'd have to revert back to a clean stock ROM, no TWRP, no ElementalX, no magisk. The stock ROM also needs to be in a read only state (no modifications allowed in TWRP) and cannot be debloated (OEM partition needs to be untouched).
You could revert back to a TWRP backup made before you flashed ElementalX, provided you did not let TWRP make modifications. You'd also have to find a stock recovery (if you flashed TWRP), and restore a stock logo.bin as well if you flashed a custom logo.bin to hide the bootloader warning. Then, you should be able to apply OTA/security updates. Attempts to apply OTA updates with TWRP on your device will likely fail and leave you in a soft bootloop unless you boot via the bootloader. You could try this to break the bootloop: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The easiest and safest method I've found is to re-flash the stock ROM you have. Ensure this is the same firmware as you currently have and the latest firmware that you've flashed onto your device (don't downgrade your firmware if possible). You can re-flash without erasing your data by omitting the fastboot erase userdata command. However, I would recommend you back up your device anyway (e.g. in TWRP) and any important files, as although this procedure should not affect your data with that command omitted, any firmware flash has the possibility of affecting your device stability. That may require a factory reset/device wipe to fix. Backing up your data should be standard policy when it comes to flashing anything affecting your device's system/underlying firmware.
After re-flashing the stock ROM, you should be able to apply the OTA update.
Thanks a lot for the detailed answer. I really appreciate people like you. [emoji3]
Sent from my Redmi Note 3 using Tapatalk
I just got my Moto G4 Plus and want to root it. Does somebody have a good guide for rooting it?
I found this guide on youtube, can I just follow this?: https://www.youtube.com/watch?v=g3bhXe3msxU&t=3s
What stock OS are you running on your device, Marshmallow or Nougat?
echo92 said:
What stock OS are you running on your device, Marshmallow or Nougat?
Click to expand...
Click to collapse
I just updated to Android 6.0.1 Marshmallow
If you're on Marshmallow (6.0.1), then the guide you linked should work, you may wish to keep the stock kernel (and not flash ElementalX). Also, instead of phh superuser, you could choose to flash SuperSU or magisk.
Here's a guide for rooting on Marshmallow 6.0.1 as well https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 You may wish to use a newer build of SuperSU than mentioned in the guide - the latest build currently is 2.82 SR1.
echo92 said:
If you're on Marshmallow (6.0.1), then the guide you linked should work, you may wish to keep the stock kernel (and not flash ElementalX). Also, instead of phh superuser, you could choose to flash SuperSU or magisk.
Here's a guide for rooting on Marshmallow 6.0.1 as well https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 You may wish to use a newer build of SuperSU than mentioned in the guide - the latest build currently is 2.82 SR1.
Click to expand...
Click to collapse
I found a video that showed how to unlock bootloader, and uses SuperSU when rooting. Can I use this guide insted, or is it to old you think?: https://www.youtube.com/watch?v=dK2uacpjGwc&t=119s
Thank you so much for all the help btw
skismas said:
I found a video that showed how to unlock bootloader, and uses SuperSU when rooting. Can I use this guide insted, or is it to old you think?: https://www.youtube.com/watch?v=dK2uacpjGwc&t=119s
Thank you so much for all the help btw
Click to expand...
Click to collapse
Looking through that video, I think it should work for 6.0.1 - as an aside for anyone reading this, the root procedure for Nougat is different. Though the resources linked in the video may work (I have not tested them), you may, as I mentioned above, wish to flash newer versions of TWRP and SuperSU than that linked in the video:
TWRP - (official): https://dl.twrp.me/athene/
I personally use shreps' TWRP: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
SuperSU v2.82: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703 Ideally, you'll want to use v2.79 SR3 or newer as they're systemless root.
EDIT: this guide linked to in the video has a nice description of some of the steps you'll need: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
One thing I'd add to those guides is before you flash SuperSU, make a backup of all of the partitions in TWRP (on the TWRP main menu, you'll see 'Backup'). If SuperSU fails to root or causes instabilty, you'll have a backup to fall back to.
Additionally, when flashing TWRP, you'll see the 'Image not signed or corrupted' warning, that's normal. As long as [OKAY] comes up in fastboot after flashing and you reboot to recovery afterwards (so TWRP is set as your recovery), then TWRP should stick.
You may also receive OTA messages - do not accept these whilst rooted and with TWRP. if you wish to turn them off, have a look here: https://forum.xda-developers.com/showpost.php?p=72373828&postcount=12
Don't FLASH TWRP, just BOOT it up, do whatever you need to do and... keep your stock bootloader. The TWRP is useful mostly for CM/Lineage ROM's, for stock it's just a headache waiting to happen.
echo92 said:
Looking through that video, I think it should work for 6.0.1 - as an aside for anyone reading this, the root procedure for Nougat is different. Though the resources linked in the video may work (I have not tested them), you may, as I mentioned above, wish to flash newer versions of TWRP and SuperSU than that linked in the video:
TWRP - (official): https://dl.twrp.me/athene/
I personally use shreps' TWRP: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
SuperSU v2.82: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703 Ideally, you'll want to use v2.79 SR3 or newer as they're systemless root.
EDIT: this guide linked to in the video has a nice description of some of the steps you'll need: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
One thing I'd add to those guides is before you flash SuperSU, make a backup of all of the partitions in TWRP (on the TWRP main menu, you'll see 'Backup'). If SuperSU fails to root or causes instabilty, you'll have a backup to fall back to.
Additionally, when flashing TWRP, you'll see the 'Image not signed or corrupted' warning, that's normal. As long as [OKAY] comes up in fastboot after flashing and you reboot to recovery afterwards (so TWRP is set as your recovery), then TWRP should stick.
You may also receive OTA messages - do not accept these whilst rooted and with TWRP. if you wish to turn them off, have a look here: https://forum.xda-developers.com/showpost.php?p=72373828&postcount=12
Click to expand...
Click to collapse
I managed to root my phone without bricking it! I think......
SuperSU was not on the phone when I rebooted the phone like in the video. I had to download it through play store. But since it says its rooted on root checker, and I could grant it permission, im pretty sure I done it right.
Thanks for the help I really appreciate it
Followed this youtube guide --> How to Root Moto G4 Plus, Unlock Bootloader and Install Recovery!
(his youtube is gizmoddict, xda is restricting the link)
On last step I had to install the zip, and it would reboot into the phone, except it didn't.
xt1625 moto g4 is now stuck in a twrp bootloop and I have no idea what to do, help is appreciated.
If this is the guide in question: https://www.youtube.com/watch?v=dK2uacpjGwc then are you running stock Nougat 7.0 on your device?
If so, that guide is too old to be useful - the stock Nougat kernel appears to be much stricter with being rooted on and so you must use a custom kernel (e.g. ElementalX or vegito) to root successfully on stock Nougat. If you were running Marshmallow as in the guide, then it should have worked (though depending on the version of SuperSU you flashed).
I would try to copy a custom kernel to your device and attempt to flash that via TWRP, see if you can get your device to boot.
echo92 said:
If this is the guide in question: then are you running stock Nougat 7.0 on your device?
If so, that guide is too old to be useful - the stock Nougat kernel appears to be much stricter with being rooted on and so you must use a custom kernel (e.g. ElementalX or vegito) to root successfully on stock Nougat. If you were running Marshmallow as in the guide, then it should have worked (though depending on the version of SuperSU you flashed).
I would try to copy a custom kernel to your device and attempt to flash that via TWRP, see if you can get your device to boot.
Click to expand...
Click to collapse
Yes that would be the link to the video, and I believe it came stock as 7.0 nougat? (not 100% on that)
Currently searching XDA for the custom kernel you mentioned, sounds like it should be easy to get working thank you.
echo92 said:
If this is the guide in question: then are you running stock Nougat 7.0 on your device?
If so, that guide is too old to be useful - the stock Nougat kernel appears to be much stricter with being rooted on and so you must use a custom kernel (e.g. ElementalX or vegito) to root successfully on stock Nougat. If you were running Marshmallow as in the guide, then it should have worked (though depending on the version of SuperSU you flashed).
I would try to copy a custom kernel to your device and attempt to flash that via TWRP, see if you can get your device to boot.
Click to expand...
Click to collapse
In twrp and checked on pc to see that there is only twrp on internal storage, attempting to install ElementalX-G4-2.00.zip right now.
It worked thank you (atleast I think it is), currently selecting the MHz for the cpu frequency (obvious choice of stock). Appreciate the help.
NVM not working, now it won't boot into twrp. Not sure what in the world is going on anymore with this phone :/
NVM to that as well, 3rd time is the charm in twrp is back again.
Figured it out I think, it says "No OS Installed! Are you sure you wish to reboot?" after installing that zip file. Why does it say that?
Ok lineage OS is installed, super happy about it, thanks for suggesting that kernel thing otherwise I'd not have found this. Super easy to get rolling.
Hey! haven't seen anyone in this section for a while....
Why I am making this thread
So lately, I was looking through my old phones only only to find my old dusty Samsung Galaxy Note 2 lying around. It had already been rooted with kingroot... Needless to say, it's a spyware and my phone was drastically slow probably because of it.
Long story short, kingroot messed up all the files. Trying to install a working version of SuperSU gave me a headache. Finally, Magisk(v22.1) was supposed to work on the phone as it stated that it's the last version to support v4.4.2 but it doesn't actually work. It keeps on showing N/A whenever I launch it and a million different permutations that I had done in the process of rooting it using Magisk never worked.
This took me days, just jumping from one rabbit hole into another, finding old dead links which really made me so frustrated that at some point I wanted to throw the whole phone away.
That's why I'm creating this thread, so that I save the hassle for myself in the future and hopefully anyone who comes across this.
Updated rooting guide
This guide worked for my GT N7100 android version 4.4.2. It'd also probably work on other devices on other old phones which have an android version less than 5
Just make sure to backup everything before trying it.
Step 1. Flashing TWRP
Download the files from the following link
[TWRP]N7100 TWRP v3.3.1-0 ODIN FLASHABLE [23/05/2019]
Ok there we go this recovery is the latest 3.2.3-2 for t03g only don't flash this on t0lte(N7105). UPDATE: 12/04/2019: official support: https://dl.twrp.me/t03g TWRP 3.2.3-2 for N7100. Bugs: Format as F2FS doesn't work because the option isn't...
forum.xda-developers.com
Download ODIN
https://samfw.com/Odin/Odin3_v3.13.3.zip
Boot the phone into download mode(VOLUME DOWN + POWER KEY + HOME KEY)
Open ODIN and in BL choose the file that you've downloaded whose extension is or is similar to ".tar"
Click start
Step 2. Downloading and flashing Magisk
In here, you need to download a very specific version of Magisk, because anything above this version won't work.
NOTE: If you have installed any later versions of Magisk then make sure to uninstall them first, you can find out how to uninstall it from here(https://topjohnwu.github.io/Magisk/install.html#uninstallation)
Download THESE VERY SPECIFIC VERSIONS of Magisk and Magisk Manager from here
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Get into TWRP recovery mode and then flash Magisk-v21.4.zip
Reboot back into the device and install MagiskManager-v8.0.7.apk
That's the end of it, your device is rooted now
HOWEVER, once MagiskManager has been installed, it would say that there's an update available(a newer version) available that you could upgrade to.
NEVER EVER UPDATE!! Updating your Magisk version to ANYTHING above v21.4 will cause it not to detect root. This is a bug with Magisk and it would probably never get fixed because support for android <5 had been discontinued a long time ago.
In case you ever do accidentally update Magisk, you will have to uninstall the Magisk app and then install MagiskManager-v8.0.7.apk again.
To uninstall and unroot your device, download this file and flash it with TWRP
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip
Where I got the links above from
https://github.com/topjohnwu/Magisk/releases/download/v21.4/
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/
Magisk v22.1
This release is focused on fixing regressions and bugs. Check the v22.0 release notes if coming from older releases.
Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 will only support Android 5.0 and higher.
ze7zez said:
Magisk v22.1
This release is focused on fixing regressions and bugs. Check the v22.0 release notes if coming from older releases.
Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 will only support Android 5.0 and higher.
Click to expand...
Click to collapse
Nope doesn't work as it wont be able to detect root at all, this is what had initially caused my headache to begin with
The last version of magisk that actually works on GT N7100 and probably any other old phone is the one that I linked in the thread
EDllT said:
(...)
Get into TWRP recovery mode and flash Magisk-v21.4.zip
Reboot back into the device and install MagiskManager-v8.0.7.apk
(...)
Click to expand...
Click to collapse
Thank you for the information.
I checked on Samsung Galaxy S4 Mini LTE i9195 (stock KK 4.4.2) and it works indeed at most version 21.4.
It is not possible to install MagiskManager-v8.0.7.apk because it is installed together with Magisk-v21.4.zip.