Is it necessary to install the TWRP 3.0.2-0 RC1 zip before rooting? The reason I'm asking is because all I wanted was to boot TWRP (not install it), but when I booted the TWRP RC1 img, then installed the SuperSU 2.79 zip, root didn't "take". I had to use the alpha2 version of TWRP and then the SuperSU zip installed just fine.
Perhaps this is an anomaly with TWRP 3.0.2-0 RC1 on NMF26U?
CatThief said:
Is it necessary to install the TWRP 3.0.2-0 RC1 zip before rooting? The reason I'm asking is because all I wanted was to boot TWRP (not install it), but when I booted the TWRP RC1 img, then installed the SuperSU 2.79 zip, root didn't "take". I had to use the alpha2 version of TWRP and then the SuperSU zip installed just fine.
Perhaps this is an anomaly with TWRP 3.0.2-0 RC1 on NMF26U?
Click to expand...
Click to collapse
You're using the outdated 2.79 version. You can use that version but you need to do one more step if you use RC1. However, rather than the long explanation, just download the new 2.79 SR2 and install it on TWRP RC1 (whether RC1 is permanently installed, or temporary like you're doing).
Why do you prefer root but leaving TWRP behind.
CatThief said:
Is it necessary to install the TWRP 3.0.2-0 RC1 zip before rooting? The reason I'm asking is because all I wanted was to boot TWRP (not install it), but when I booted the TWRP RC1 img, then installed the SuperSU 2.79 zip, root didn't "take". I had to use the alpha2 version of TWRP and then the SuperSU zip installed just fine.
Perhaps this is an anomaly with TWRP 3.0.2-0 RC1 on NMF26U?
Click to expand...
Click to collapse
I just want root for running a firewall and AdAway.
Can I have the name of the firewall app you used.
CatThief said:
I just want root for running a firewall and AdAway.
Click to expand...
Click to collapse
AFWall+
I forget to mention I also like root for Titanium Backup. It's a total must have.
I first booted TWRP RX1, then installed TWRP RC1 and then SU v2.79-SR2. This did work. I also tried v2.78-SR4 first (as it is linked in the Pixel Forum SU Thread) but that did not install.
Sorry that I can't help with the TWRP Boot only try.
Related
I have rooted my Pixel and installed TWRP before after an update. But after this update, I installed RC1 of TWRP and it is installed now. But when I install the ZIP of SU through TWRP, I do the install and reboot then go into the playstore and install SuperSU and it says I am not rooted.. What am I doing wrong?
exbtlegends said:
I have rooted my Pixel and installed TWRP before after an update. But after this update, I installed RC1 of TWRP and it is installed now. But when I install the ZIP of SU through TWRP, I do the install and reboot then go into the playstore and install SuperSU and it says I am not rooted.. What am I doing wrong?
Click to expand...
Click to collapse
Wrong version of SU? You need the beta, SU 2.79 SR3
Note the 9 in there, not an 8.
TonikJDK said:
Wrong version of SU? You need the beta, SU 2.79 SR3
Note the 9 in there, not an 8.
Click to expand...
Click to collapse
I have 2.79 SR3. That's what I don't understand. The only thing I've tried different is the RC1 build of TWRP. I did have alpha 2 before. May go back to alpha and see if it lets me root
If you are just booting TWRP to install a zip, I find that Alpha 2 is more reliable than RC 1. There are times on RC 1 the initial popup doesn't show up for me, so then it won't install the zip. The times I've used Alpha 2 it has worked without issue.
alluringreality said:
If you are just booting TWRP to install a zip, I find that Alpha 2 is more reliable than RC 1. There are times on RC 1 the initial popup doesn't show up for me, so then it won't install the zip. The times I've used Alpha 2 it has worked without issue.
Click to expand...
Click to collapse
Odd that the main release doesn't work but the alpha does. I tried multiple times in a row to get su to install. It says it is installing it and gives no errors. Reboot and no root
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?
I have a Honor 8 with Emui 5.0.1, Android 7 model FRDL09 , build FRD- L09C432B394.
I have unlocked the bootloader and installed 3.0.3-0 Twrp but when i try to install SuperSU from the recovery i can't (the phone start the operation but after 2 or 3 seconds on the screen there are some very fast message and the phone just reboot. I was able to read the message that is:
- System-less Mode, Boot Image Support required
- creating image
I tried with 2 different version of SuperSU (sr3-SuperSU-2.79-Sr3- 2017 0114223742.zip and SuperSU-v2.82-Sr5-Permissive.zip but i have the same problem
Anyone can help to figure out what i'm doing wrong?
Tia
Install twrp 3.1.1 from open kirin thread.
I use magisk for root, and any problem with this recovery.
I use EMUI 5 b402.
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
xuso77 said:
Install twrp 3.1.1 from open kirin thread.
I use magisk for root, and any problem with this recovery.
I use EMUI 5 b402.
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Click to expand...
Click to collapse
Yea i just did that reading better the forum and i figured out that i was using the wrong twrp version
I still used the official SuperSu 2.82, do you think it is better go for magisk?
Thank you for your reply
For me is better magisk.
When I want update my device, I uninstall magisk with the uninstalled twrp zip, and then, I update with the full update package and 0 problems.
xuso77 said:
For me is better magisk.
When I want update my device, I uninstall magisk with the uninstalled twrp zip, and then, I update with the full update package and 0 problems.
Click to expand...
Click to collapse
Sadly i can't find the original rom of my phone so i can't reflash it to remove the changes done by SuperSU so i need to stick with it even if i want to try magisk
Flash this Version from TWRP
SR1-SuperSU-v2.82-SR1-20170608224931.zip
I'm running stock ROM on unlocked bootloader with root through Magisk. I've been using TWRP, but changed over to Blu_spark TWRP recently.
Every time I update my OS Ota, I lose TWRP and Magisk. The Magisk app is installed, but the ROM is not rooted. If course, if I try to install patch the system so it's rooted through the Magisk app, it says that it can't unpack the file. If I reboot to recovery to install from there, I get the stock recovery, not TWRP.
I tried to re-install TWRP and Magisk once before, and borked my phone. I had to quote and start from scratch. I lost all data since I wasn't rooted and Titanium Backup would not run.
What is the proper way to get TWRP and Magisk back after an OTA update?
Flash them after you flash update zip. If you don't you will lose recovery and root every time. Gets overwritten by stock recovery. Normal behavior
Sent from my ONEPLUS A6003 using Tapatalk
So you're saying that instead of doing the OTA update, I should download the update from here, and manually update it ? Can I just install the update? I'm rooted, (well, I was) so the OTA will only download the full update. Is that required instead of the update?
I really have to do a full re-install for every update? That sucks. A lot.
Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.
MickyFoley said:
Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.
Click to expand...
Click to collapse
Ok. Cool. I tried that last time, but it failed. As a result, I'm a bit anxious about doing it again. Hopefully, I won't have any problems this time.
Thanks for the info.
I have had similar troubles as you, here's an overview of how to solve those problems.
OTA through OS:
Download and install OTA
Use Magisk Manager to download the TWRP A/B retention script and install it
Install Magisk to current and inactive slot
Reboot
Guys I am using latest blu_spark twrp. my bootloader is unlocked and I am running oxygenOS openbeta23. Following is my problem.
My flash order: (Note: already I have bue_spark twrp recovery running without issues)
1. Flash the full OTA(openbeta)
2. Flash the blu_spark twrp zip file on both active and non active slots.
3. Flash the latest magisk zip file. If step 3 is not successful means I will try to reboot in to recovery and again flash the magisk installer zip.
Until some time back all this worked fine. But for last 2-3 times although the flashing process of twrp zip on both slots ends with success message, when I reboot to recovery from twrp in order to flash magisk, the device boots in to stock recovery. I don't know how even after flashing twrp zip on both slots successfully why the devices bootbback to stock recovery. Then to have blu_spark twrp I have to connect my device to a computer in fastboot mode and then boot in to custom recovery using the blu_spark twrp image file and again flash the blu_spark twrp zip file which is inconvenient and also requires a computer.
Am I missing anything here?? If yes why this method was working perfectly before? Please somebody help.
Regards,
Sivabalan K
I flash in following order my stable updates
Flash full rom zip
Flash bluespark recovery
Restart into bluespark recovery
Flash magisk
Restart into Android
Everything works flawless. Magisk installed with all the modules running
Hi guys,
Don't you need to disable lock pattern/PIN or fingerprint/face ID? And don't need to uninstall magisk modules?
I never update my OP6 from my initial unlock/twrp/magisk and I'm a bit anxious to do it now...
Thanks
PS : I'm using original twrp (3.2.3-1), is this a problem?
Hello. I'm trying to flash a TWRP custom recovery on a SM-A305G (Galaxy A30). While reading the official A30's post on the TWRP website, in order to properly flash the custom recovery, they recommend me to first root my device with Magisk (which I understand how to) but THEN flashing a pre-rooted TWRP image for my device. How could this be done?
Related link: https://twrp.me/samsung/samsunggalaxya30.html
Thanks in advance to who could answer this question. Internet hero.
Rooting Android OS is adding an user with elevated rights ( comparable to adminstrator in Windows OS ) to it, nothing else.
TWRP recovery does not require a phone's Android is rooted.
lnrdx said:
Hello. I'm trying to flash a TWRP custom recovery on a SM-A305G (Galaxy A30). While reading the official A30's post on the TWRP website, in order to properly flash the custom recovery, they recommend me to first root my device with Magisk (which I understand how to) but THEN flashing a pre-rooted TWRP image for my device. How could this be done?
Related link: https://twrp.me/samsung/samsunggalaxya30.html
Thanks in advance to who could answer this question. Internet hero.
Click to expand...
Click to collapse
That just isn't how it is done, we don't root TWRP, we root the phone's OS. There isn't anything to "root" in or about TWRP because TWRP has the power to modify a device without needing root.
It isn't required, but, it is possible to root a device and then use an app such as Rashr, Flashify or TWRP Manager along with root permissions to flash a TWRP img or even use a Terminal Emulator app with root permissions to install TWRP via dd commands. It doesn't "have" to be done this way, it's just an alternative way to achieve root and flash TWRP on devices that are capable of doing it this way, in this order, not all devices can do it this way.
I want to have Magisk AND TWRP.
I rooted the phone with Magisk and had Magisk running.
Then installed TWRP app and flashed TWRP with root permission.
Now TWRP is installed but Magisk is gone again.
How can I have BOTH?
woheller69 said:
I want to have Magisk AND TWRP.
I rooted the phone with Magisk and had Magisk running.
Then installed TWRP app and flashed TWRP with root permission.
Now TWRP is installed but Magisk is gone again.
How can I have BOTH?
Click to expand...
Click to collapse
Flash the Magisk.zip via TWRP just to be sure binaries are installed, then wipe cache and dalvik cache in TWRP then boot into system and install the Magisk Manager app(if it dosen't get installed when you flash the Magisk.zip).
Unfortunately not working.
I installed Magisk via Odin wirh a Magisk-patched stock rom ( Galaxy A10). WORKED
Then installed TWRP via Odin and got TWRP and Magisk working by immediately booting into recovery after flashing.
But then I installed the CrDroid custom rom via TWRP and now Magisk is gone.
[ROM][ARM][OFFICIAL] crDroid 8.x for Galaxy A10 [Android 12]
*** Disclaimer I am not responsible for any damage you made to your device You have been warned crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features...
forum.xda-developers.com