Question how to root lineage 18.1 on US Retail Moto E - Moto E (2020)

i managed to unlock the bootloader, install twrp 3.5.0 and install a fixed lineage os rom, but is it still possible to get root access? i'm not sure if any other info about the device is needed that i can find.

frozencoffee said:
i managed to unlock the bootloader, install twrp 3.5.0 and install a fixed lineage os rom, but is it still possible to get root access? i'm not sure if any other info about the device is needed that i can find.
Click to expand...
Click to collapse
Download the Magisk APK.
Rename the .APK file extension to .ZIP (e.g. Magisk-v23.0.APK → Magisk-v23.0.ZIP).
Flash the ZIP file just like any other ordinary flashable ZIP.
Or
In case you’re using a custom ROM like LineageOS, then the flashable ZIP file contains the boot image.
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and more
Rooting your phone is still possible — and fun — these days. Here's how to do it on your Android device.
www.xda-developers.com

Related

Official Android Nougat, phh Superuser, Magisk Mod

Hello all,
Yesterday I did what many did and upgraded to Nougat as soon as it dropped, using the "sign up for Android beta" method. I came from a bootloader unlocked, rooted Nexus 5x running the latest version of 6.0.1 with a few basic mods - AdAway, Viper4Android, ElementalX Kernel w/ profile manager, Cf.Lumen and Greenify.
In upgrading to Android 7.0, I first flashed the system, vendor, boot and recovery image from the most recent version of 6.0.1 to revert completely to unrooted stock before taking the OTA.
After reading about this new method of systemless root that also seems to allow Android Pay to work, I'm trying to wrap my head around it before trying, and wanted some of the wise minds of XDA to confirm my procedure.
Current Status-
Device: Nexus 5x
Build: Android 7.0 NRD90M
Unlock Status: Bootloader Unlocked
Root Status: Unrooted
Boot.img and Recovery.img: Stock
Procedure:
1. Download latest TWRP, boot device into fastboot mode, and "fastboot flash recovery [TWRP file]"
2. Navigate to TWRP Recovery, locate phh root .zip (already downloaded to device), Magisk mod and ElementalX kernel, flash these.
3. Once booted, follow directions in the Magisk thread to mount the desired mods (AdAway, Viper4Android, etc.) while still passing SafetyNet check, and Android Pay will continue to work.
Also, if I understand correctly, future system updates will be possible using FlashFire and the OTA .zip while maintaining root status and the modifications, since \system is not modified using this method.
Any confirmation/feedback is welcome!
Thanks,
Moonboots
Moonboots said:
Hello all,
Yesterday I did what many did and upgraded to Nougat as soon as it dropped, using the "sign up for Android beta" method. I came from a bootloader unlocked, rooted Nexus 5x running the latest version of 6.0.1 with a few basic mods - AdAway, Viper4Android, ElementalX Kernel w/ profile manager, Cf.Lumen and Greenify.
In upgrading to Android 7.0, I first flashed the system, vendor, boot and recovery image from the most recent version of 6.0.1 to revert completely to unrooted stock before taking the OTA.
After reading about this new method of systemless root that also seems to allow Android Pay to work, I'm trying to wrap my head around it before trying, and wanted some of the wise minds of XDA to confirm my procedure.
Current Status-
Device: Nexus 5x
Build: Android 7.0 NRD90M
Unlock Status: Bootloader Unlocked
Root Status: Unrooted
Boot.img and Recovery.img: Stock
Procedure:
1. Download latest TWRP, boot device into fastboot mode, and "fastboot flash recovery [TWRP file]"
2. Navigate to TWRP Recovery, locate phh root .zip (already downloaded to device), Magisk mod and ElementalX kernel, flash these.
3. Once booted, follow directions in the Magisk thread to mount the desired mods (AdAway, Viper4Android, etc.) while still passing SafetyNet check, and Android Pay will continue to work.
Also, if I understand correctly, future system updates will be possible using FlashFire and the OTA .zip while maintaining root status and the modifications, since \system is not modified using this method.
Any confirmation/feedback is welcome!
Thanks,
Moonboots
Click to expand...
Click to collapse
Howdy sir! I'm still learning myself so I can't give you a great answer, but it's been a few weeks so I thought maybe you already gave this a shot? I'm looking to follow about the same process soon. I'm currently bootloader unlocked with TWRP loaded on Nougat (NRD90S on 5X).
How'd this go for ya?
Thanks!

Root S9 with latest firmware update One UI 2.5 (G960FXXSCFTK2/G960FOXMCFTJ2/G960FXXUCFTJ1)

How to root first time phone with latest update with magisk method?
I'm find this simple way without TWRP
Is this way good?
No need to install TWRP in this way and no need some other .zip files like "no verify opt encrypt"
or something like that is not necessary. Is that a good idea? What are these additional .zip files for?
I have some experience with root on older samsung phones that have been routed by installing TWRP and flashing .zip magisk pach.
Nothing more was needed.
In short,
This way from joutube goes like this:
First the OEM is unlocked, magiskmanager.apk is downloaded and installed apk. After that the AP file that we downloaded before of firmware is patched with magisk app and inserted into the downloads folder.
After that, we flash the patched AP file over the odin and that's it. Will this work for me on the latest firmware?
I found this way that involves installing TWRP and some zip file.
xxsen said:
How to root first time phone with latest update with magisk method?
I'm find this simple way without TWRP
Is this way good?
No need to install TWRP in this way and no need some other .zip files like "no verify opt encrypt"
or something like that is not necessary. Is that a good idea? What are these additional .zip files for?
I have some experience with root on older samsung phones that have been routed by installing TWRP and flashing .zip magisk pach.
Nothing more was needed.
In short,
This way from joutube goes like this:
First the OEM is unlocked, magiskmanager.apk is downloaded and installed apk. After that the AP file that we downloaded before of firmware is patched with magisk app and inserted into the downloads folder.
After that, we flash the patched AP file over the odin and that's it. Will this work for me on the latest firmware?
I found this way that involves installing TWRP and some zip file.
Click to expand...
Click to collapse
I have used the method on a Samsung Galaxy Xcover 4s with new firmware.
However I don't know if it will work with Samsung Galaxy S9 due to the need for "dm-verity and force encryption disabler".
Have you rooted?

Help with magisk patched boot image

So I have op7t, with stock oos 10.0.16HD65BA, unlocked bootloader, stock kernel and recovery. Where can I find magisk patched boot image for this deivce and do I need twrp installed? And does it matter if the patched boot image is for global and I have Europe?
I haven't touched these things since op3t and things have changed a lot, and I'm really confused, so feel free to link me about anything related to rooting/installing roms/twrp on this device.
TuomasRizt said:
So I have op7t, with stock oos 10.0.16HD65BA, unlocked bootloader, stock kernel and recovery. Where can I find magisk patched boot image for this deivce and do I need twrp installed? And does it matter if the patched boot image is for global and I have Europe?
I haven't touched these things since op3t and things have changed a lot, and I'm really confused, so feel free to link me about anything related to rooting/installing roms/twrp on this device.
Click to expand...
Click to collapse
Don't need that. Just install twrp and then flash magisk zip (rename magisk apk)
HueyT said:
Don't need that. Just install twrp and then flash magisk zip (rename magisk apk)
Click to expand...
Click to collapse
So I can just download magisk zip from their forum and flash that in twrp?
TuomasRizt said:
So I can just download magisk zip from their forum and flash that in twrp?
Click to expand...
Click to collapse
Yep
HueyT said:
Yep
Click to expand...
Click to collapse
So I installed unofficial twrp from oneplus 7t xda forums, and tried to install magisk.apk (renamed to zip) but apparently twrp seems not seeing anything in my internal storage? Is it bcs I have oxygenOs and twrp can't read the data partition? And how should I flash it now? from pc manually with fastboot or..?
TuomasRizt said:
So I installed unofficial twrp from oneplus 7t xda forums, and tried to install magisk.apk (renamed to zip) but apparently twrp seems not seeing anything in my internal storage? Is it bcs I have oxygenOs and twrp can't read the data partition? And how should I flash it now? from pc manually with fastboot or..?
Click to expand...
Click to collapse
adb push .zip /tmp
And you need an update to date version of twrp to flash apk.
Seriously, just use patched image method.
Lossyx said:
adb push .zip /tmp
And you need an update to date version of twrp to flash apk.
Seriously, just use patched image method.
Click to expand...
Click to collapse
I was going to use that, but as I asked in the first post, do I need europe version 10.0.16 HD65BA version magisk patched image, and if yes, where can I find it? And I have the latest twrp uploaded on there -> https://forum.xda-developers.com/t/...ry-for-oneplus-7t-unified-tes.3976961/page-46
TuomasRizt said:
I was going to use that, but as I asked in the first post, do I need europe version 10.0.16 HD65BA version magisk patched image, and if yes, where can I find it? And I have the latest twrp uploaded on there -> https://forum.xda-developers.com/t/...ry-for-oneplus-7t-unified-tes.3976961/page-46
Click to expand...
Click to collapse
Actually ignore what I said. I am not sure if that TWRP is capable of flashing apks, but it doesn't matter. Flash the previous version which was a zip file, then just update within magisk manager.
Release Magisk v21.4 · topjohnwu/Magisk
Update: v21.4 adds more regression hot fixes. Happy 2021! v21.3 adds a workaround for devices with buggy F2FS Linux kernel drivers. This F2FS bug may cause bootloops on many devices. Checkout the f...
github.com
fastboot boot twrp.img
adb push magisk.zip /tmp
Navigate and flash magisk zip from tmp folder
I am due to receive my OP7T in a couple of days and already started reading. I assume oos 10.0.16HD65BA is the latest A10 for 7T.
My goal is to get latest stable Android 10 build for my 1903 EU variant OP7T - Unlock Bootloader, Root with Magisk and then Install No Limits xXx Magisk ROM.
Will appreciate some feedback how to proceed please.
From the post above - it seems that the steps are - Unlock Bootloader, Boot (not flash) TWRP.img , adb push Magisk zip , flash Magisk zip in the loaded twrp and then boot to system.
My doubts -
I have been using adb and drivers for my OP5 - will that old adb and drivers work with OP7T?
Which TWRP.img is recommended
Which version of Magisk.zip can I flash (would v22 be OK?)
Can Magisk be updated via Magisk manager at a later stage?
I assume the system will revert to stock recovery (as TWRP was only loaded, not flashed) - will this cause loss of root?
Have I missed out any crucial points / steps?
Thanks
TuomasRizt said:
So I have op7t, with stock oos 10.0.16HD65BA, unlocked bootloader, stock kernel and recovery. Where can I find magisk patched boot image for this deivce and do I need twrp installed? And does it matter if the patched boot image is for global and I have Europe?
I haven't touched these things since op3t and things have changed a lot, and I'm really confused, so feel free to link me about anything related to rooting/installing roms/twrp on this device.
Click to expand...
Click to collapse
How did you eventually do it? Please share your process.

[HELP] How do I root my XT1952-1 (Android 9)

Hi everyone ,
I wandered for months in this forum but I didn't really find how to root my device. There are some tutorial for the "1952-4" but it's not my device. I really don't want to do risky things flashing wrong files. At this point I don't even know if my model can be rooted.
Here are useful infos :
Device : Moto G7 Play XT1952-1
Firmware : Android 9 (security patch december, 1st 2018)
Build : PPY29.68-28
Bootloader unlocked : YES
At this point, what am I supposed to do ? Is there a TWRP image that would work for sure ?
Thank you.
I managed to root my xt1952-4 but I couldn't use the methods on here as I would have TWRP and Magisk root but would lose wifi. So I decided to install magisk, extract the Boot.img file from the rom and patch it with magisk. I flashed it back using "fastboot flash boot boot.img" and now I have root and working wifi but no recovery.
MikeRWK said:
I managed to root my xt1952-4 but I couldn't use the methods on here as I would have TWRP and Magisk root but would lose wifi. So I decided to install magisk, extract the Boot.img file from the rom and patch it with magisk. I flashed it back using "fastboot flash boot boot.img" and now I have root and working wifi but no recovery.
Click to expand...
Click to collapse
Interesting, thanks.
I don't know if I can risk doing that on my XT1952-1 though, you never know how it'd behave.
If somebody successfully rooted XT1952-1, please let me know

Question Updating to Android 13 while keeping bootloader unlock/TWRP/root

I have been digging through these forums, but can't find an straight step-by-step guide explaining how you go about manually updating the firmware on this device when you have the bootloader unlocked, TWRP installed, and rooted with Magisk.
I know that having the bootloader unlocked means that the device can no longer get updates automatically and that the updates have to be manually downloaded installed from the ASUS website. But what I don't understand is how to install the firmware from the ASUS website and still keep TWRP recovery and Magisk root.
This is my first time updating the device after I first set it up in January, so I would very much appreciate it if some one knowledgeable could explain this process to me
(In case you need to know, I'm currently on WW-32.2810.2212.241 firmware, with TWRP 3.70_12-0 and Magisk 25.2 installed.)
jmaeshawn said:
I have been digging through these forums, but can't find an straight step-by-step guide explaining how you go about manually updating the firmware on this device when you have the bootloader unlocked, TWRP installed, and rooted with Magisk.
I know that having the bootloader unlocked means that the device can no longer get updates automatically and that the updates have to be manually downloaded installed from the ASUS website. But what I don't understand is how to install the firmware from the ASUS website and still keep TWRP recovery and Magisk root.
This is my first time updating the device after I first set it up in January, so I would very much appreciate it if some one knowledgeable could explain this process to me
(In case you need to know, I'm currently on WW-32.2810.2212.241 firmware, with TWRP 3.70_12-0 and Magisk 25.2 installed.)
Click to expand...
Click to collapse
Hi Bro.
Your ROG Phone was CN and did you flash the RAW WW firmware?.
Regards!.
jmaeshawn said:
I have been digging through these forums, but can't find an straight step-by-step guide explaining how you go about manually updating the firmware on this device when you have the bootloader unlocked, TWRP installed, and rooted with Magisk.
I know that having the bootloader unlocked means that the device can no longer get updates automatically and that the updates have to be manually downloaded installed from the ASUS website. But what I don't understand is how to install the firmware from the ASUS website and still keep TWRP recovery and Magisk root.
This is my first time updating the device after I first set it up in January, so I would very much appreciate it if some one knowledgeable could explain this process to me
(In case you need to know, I'm currently on WW-32.2810.2212.241 firmware, with TWRP 3.70_12-0 and Magisk 25.2 installed.)
Click to expand...
Click to collapse
I think twrp will not work properly with android 13 because twrp is made for android 12
Dumper UL full upgrade and you will get Boot.img and recovery.img (keep both files at safe place).
Use magisk manager to patch the boot file.
Keep recovery.img (original A13) and TWRP.img safe in ADB root folder (dont mix them up).
1. Update FOTA to Android 13 by copy UL full upgrade into root folder of your phone. If copy from PC/laptop with cable then unplug the cable, your phone will recognize the package, (if you already change COUNTRY CODE and currently use WW 241 rom that will be success update). Otherwise, reboot your device and pop up will appear. Wait the phone is fully reboot and set up everything.
2. Reboot your phone into download mode/fastboot mode (it's better that you should enable USB debug/Developer mode before doing anything). Using CMD command to flash patched boot from Magisk Manager. And reboot, now your phone could gain back root.
3. Check again if the recovery is gone or not. If it's gone, then use termux or any terminal emulator for the "dd command".
You will gain back the TWRP, if any failed, flash back original recovery.img that you have lately in ADB folder on your PC.
PS: backup everything, since going back from Android 13 to Android 12 need to full factory reset.
Br,
ChrisFeiveel84 said:
I think twrp will not work properly with android 13 because twrp is made for android 12
Click to expand...
Click to collapse
I'm on WW-33.0610.2810.81, and TWRP seems to be working OK so far

Categories

Resources