Does Anyone know any method to root and install magisk in android pie ?
Lilesh Jadav said:
Does Anyone know any method to root and install magisk in android pie ?
Click to expand...
Click to collapse
Remove screenlocks 1st to make things easy.
Download twrp 3.3.1.0 img and zip
Download magisk 19.3
Copy twrp zip and magisk zip to sdcard
Open a cmd prompt and enter the following
PHP:
adb reboot bootloader
fastboot boot (drag n drop twrp img here)
Once twrp is booted install magisk and reboot to system you should be rooted. *If you want twrp installed as your recovery, install the twrp zip 1st then install magisk
https://forum.xda-developers.com/z2-force/how-to/oreo-nougat-how-to-root-z2-t3756669 works for pie as well. Be sure to use the latest TWRP.
Hi
I can't install Magisk
I tried to install using this thread https://forum.xda-developers.com/t/install-magisk-on-android-11-r-100-functional.4162761/
Tried to install Magisk on OctaviOS 1.3
If i do this
Code:
1-Reboot in twrp and flash MagiskR.zip
2-Reboot system and install MagiskR.APK
3-Open magisk and update MagiskR.APK
And go to Magisk I have only 3 options Magism home page, Magisk Logs, Magisk settings and nothing else. No plugins and ways to give root to applications.
Also it types.
Magisk
Latest: N/A
Installed: N/A
Status:N/A
A/B: Yes
SAR: Yes
Ramdisk: Yes
When I try to do all 5 steps
Code:
Twrp installation:
1-Reboot in twrp and flash MagiskR.zip
2-Reboot system and install MagiskR.APK
3-Open magisk and update MagiskR.APK
4-Reboot in twrp and Flash Magisk-e66b0bf3(20425).zip
5-Reboot system and ready
I get always in fastboot
Then I tried to install Magisk on Syberia Project and after flashing zip I don't have Magisk Manager installed on my phone. I installed apk from this thread and tried lastest apk from Github. Both didn't work
I also tried to update Magisk apk to Beta version and nothing changed.
Is your bootloader unlocked?
Im wondering if a custom GSI installation is possible
Checking the app "Treble info" says the phone supports the modern version of project treble
And im wondering if anything else has to be done for a GSI to work (for example flashing another file before the GSI)
or just simply flash it via twrp or ADB?
and if its possible, The installation of an android 12 GSI would be possible?
Generic system images | Android Open Source Project
source.android.com
Well you need to flash a vbmeta.img, with a special command. Details are in the link above.
Vbmeta.img is usually available in the stock ROM, but if it fails or does not exist, use the Google official vbmeta. https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
DISCLAIMER: whatever you're doing with your device is your responsibility and only yours! Not mine or anyone else. So be careful and don't brick your device, but if you do and are looking for someone to blame: use a mirror and nothing else.
This is just a small collection of possible tweaks for the following device. It is meant for advanced/experienced users.
Goals reached:
1) root
2) install twrp, doing nandroidbackup, unlock data with my pin, flashing zips etc.
3) debloated sytem with system-rw
NEW:
Flashed successfully a GSI ROM (LineageOS 18.1) and it booted and worked. Haven't tested much. Instructions can be found below.
NOTE: For the GSI i made an overlay (with phhuson template and attached it to this post. Haven't found the time to upload it to phhuson*s repo and it might take a while, but you can manually install this one if desired.
My phone:
manufacturer: Lerovo
brand: Motorola
model: E7 plus
internal name: guam (XT2081-2)
ROM: QPZS30.30_Q3_38_69_3
channel: retaileu
REQUIREMENTS:
1) your phone connect to a computer with an usb cableUsing linux myself since a year or so, but it will work wirth windows too.
Some tools are windows only (like Rescue and Smart Assistant), so you might need to dual-boot.
2) Android SDK Platform Tools (ABD/FASTBOOT)Download the package for your os, unzip the file and open a terminal in it's directory (or added the path to your PATH environment variable).
https://developer.android.com/studio/releases/platform-tools
Don't forget to enable ADB under developer options.
3) unlocked bootloaderWell, yes if you want to flash something, you really need this. Everything you need to know:
https://motorola-global-en-uk.custhelp.com/app/standalone/bootloader/unlock-your-device-a
4) optional but strongly recommended: Lenovo Rescue and Smart Assistant (WIndows only)With this tool you can download the latest image for your device and flash it directly to the phone.
You can use these file later for flashing magisk etc.
Further it helped me once when my phone wasn't detectable via fastboot anymore. But there is no guarantee.
Download:
https://support.lenovo.com/de/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
Files will be under C:\ProgramData\LMSA\Download\RomFiles/ (Windows 10, 64.bit)
Spoiler: Verified Boot / AVB / VBMETA
From Android 8 onward google implemented a security system called Android verifiy boot. Read more about it here: Android Verified Boot AVB
AVB 2.0
To flash any other software (magisk, twrp, gsi rom etc.) you need to flash a vbmeta.img first:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot bootloader
Spoiler: Magisk
Download: https://github.com/topjohnwu/Magisk
You will find the latest on the right under "Releases".
Instructions:
1) Install "Magisk*.apk in your current rom
2) Copy boot.img from "Lenovo Smart and Rescue" to the internal memory of the phone
3) Flash the boot image within the magisk app (see magisk wiki)
4) reboot bootloader aka adb reboot fastboot
5) fastboot flash boot magisk_patched.img
6) reboot device, open magisk again, done.
Spoiler: SYSTEM-RW
Requirement: root
You can use an existing tool for that: systemRW from lebigmac
Download: https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
Follow his instructions and start script from within booted rom. Use his path to copy the script.
Workarounds:
1) ERROR 73: https://forum.xda-developers.com/t/...-read-write-r-w.4247311/page-23#post-84901531 You need to resume from within a linux device.
2) if you encounter any other error it might be related to extra protection. I flashed two files before starting the proccess but they might not be needed:
a) flash an modified/empty vbmeta.img. (see above)
b) Disable verity/encryption (see above)
Spoiler: TWRP
adrianuexen's twrp (see other thread) does not work for me. So i looked around and noticed that the Lenovo K12 (not pro or anything) is a rebranded E7 plus.
Search for "Lenovo K12 twrp" and you will find some sites with unofficial twrp 3.4.2 for that device.
BE CAREFUL: sources for this are at best unofficial, at worst malicious. So choose wisely if you want to go this way.
What is working for me:
everything seems ok: touch screen, decrypt data, adb sideload, flash images, adb shell, mounting etc.
Go ahead if you decided to give it a try.
You can simply try if it works:
1) reboot bootloader
2) fastboot boot recovery.img
If you want to install it:
1) reboot bootloader
2) fastboot flash recovery recovery.img
If twrp starts with prompt for password, change language with the second button.
The K12 was developed for the chinese market, so the recovery starts in chinese language too. You can change language to english like this:
1) right side: 3 button
2) last button on top (world symbol)
3) english and confirm at bottom
Spoiler: Disable DM-Verity - FORCEENCRPYT
You can use this with a working twrp recovery.
I prefer to use adb sideload for these tasks.
Download: Disable DM-Verity - ForceEncrpyt
Spoiler: GSI-ROM flashing
If it is working for you stick with "the usual way", but i can't flash an img-file no matter what i tried. Always get an empty error (error ' ')
Spoiler: The usual way
0. Get an up-to-date fastboot on your computer (fastboot —version should give version >= 29)
1. Get vbmeta.img from https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
2. Get A/B GSI (I'm guessing you need ARM64), don't forget to uncompress it
3. From running Android, do adb reboot bootloader
4. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5. fastboot reboot bootloader
6. fastboot flash system system-xxxx.img
6bis. If fastboot tells you there isn't enough place, do fastboot delete-logical-partition product, fastboot delete-logical-partition product_a, fastboot delete-logical-partition product_b
and run the fastboot flash command again
7. On your phone, the screen should have a button "go back to recovery", select it, then select "factory reset / wipe data"
8. Reboot and enjoy
Spoiler: the workaround
The idea is: building a super image with the system.img from your choosen GSI.
A)
You can do this directly via lpmake and set your config, an example here: https://forum.xda-developers.com/t/gsis-on-a51-5g.4114349/
B) The tool SuperRW (lebigmac see above) can be used to do the same (and in fact is doing the same). You just need to modify "myargs.txt" copy the system.img to the img folder and are good to go with systemrw.
Today I used AndyYan's GSI LineageOS 18.1
(arm64, A/B) LineageOS 18.1 arm64 A/B
to test it and after setting parameters in myargs.txt the new image was flashable and lineageos booted without any hassle (afaik in that short time .
Instructions:
Requirements: root, vbmeta.img applied correctly, if using: SystemRW
Start with the instructions from lebigmac (see above).
Once you get error 73 you need to stop and continue with steps below before you start sysrw_repair_v1.32.
You need to edit your "myargs.txt" on your device. You will remove/resize the product partition and make some space for the larger systen image of your GSI
1) adb shell
2) su
3) cd /data/local/tmp/systemrw_1.32/log
4) edit myargs.txt (can do it on PC or however you like it most):
a) change product_a partition (100MB and an empty image)
OLD:
--partition product t_a:none:2853670912:mot_dp_group_a --image product_a=/data/local/tmp/systemrw_1.32/img/product_a.img
NEW:
--partition product t_a:none:104857600:mot_dp_group_a --image product_a=/data/local/tmp/systemrw_1.32/img/empty.img
b) change system_a partition (at least the size of your downloadad GSI_system.img)
LineageOS image has 1818747328 byte, so i set the size of the partition to 2 GB)
OLD:
--partition system_a:none:941010944:mot_dp_group_a --image system_a=/data/local/tmp/systemrw_1.32/img/system_a.img
NEW:
--partition system_a:none:2147483648:mot_dp_group_a --image system_a=/data/local/tmp/systemrw_1.32/img/los_18.1.img
5) We will create "empty.img" (when in adb shell
touch /data/local/tmp/systemrw_1.32/img/empty.img
6) leave adb and push your GSI file to the phone
adb push lineage-18.1-20211010-UNOFFICIAL-treble_arm64_bvS.img /data/local/tmp/systemrw_1.32/img/los_18.1.img
7) Now start sysrw_repair.sh from linux machine and let it do all the hard work .
After that you should get a rom which will be flashed automatically or manual if you remove the phone before the flash starts
This is work in progress and feedback very welcome.
changelog:
2021-10-14:
- ROM: QPZS30.30_Q3_38_69_2 to ROM: QPZS30.30_Q3_38_69_3
- vbmeta.img: added information about vbmeta.img / verified boot
- GSI-flashing: LOS 18.1 working
Really nice work
Ty,added a solution to flash GSI ROMs, even if you are not able to flash the system images directly via fastboot
hola esto es un rom de android 11?
Will try later and report back
Thanks very much for this detailed writeup. I think you can safely say that the "workaround" is the way to go, the "usual way" just flops. I suspect it's because the stock partition sizes are insufficient for LineageOS. I was able to flash the same rom as you using lebigmac's scripts, then lineage-18.1-20220217-UNOFFICIAL-treble_arm64_bvS.img.
I have a problem getting root after flashing LOS. I tried to install the latest Magisk version (24.3) but it complains about a leftover 'su'. Removing Magisk causes the system to bootloop, even after reflashing the stock boot.img. How did you manage to get root in LOS?
Edit: after 2 days evaluation the error reported by Magisk doesn't seem to be serious. It just performs as it normally does
Reporting back after a few more days of testing.
Found that bluetooth refuses to work correctly. Tested with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bvS.img and lineage-18.1-20220217-UNOFFICIAL-treble_arm64_bvS.img.
Also found the camera software to be inferior in lineage compared to the one found in A10 stock.
I wasn't able to get call recording working neither. Because of all these reasons i decided to move back to stock
Hello,
I flashed the latest Lineage recovery and LineageOS20 on my Google Pixel 5, and I'd like to disable encryption on the data partition. Is there an ADB command I can run, or file I can flash to achieve this? I also have Magisk 26.1 flashed.
I use this phone for a development project and encryption is getting in the way.
Thanks!
I'm surprised no one knows.
I wanted to go the TWRP route of formatting the data partition, but I can't get TWRP to boot when running Android 13. I need to be on Android 12 to boot TWRP successfully, but being on Android 12 means I can't flash LineageOS20 (requires Android 13), a real catch 22.
Otherwise, does anyone have a link to the latest LineageOS19.1 for Redfin? The link is broken on the LineageOS website and I can't locate that zip file on any other website.