After some time I got a second Axon 10 and I spend some time figuring out what was possible with this phone in terms of root, custom ROM etc.
My results are as follows.
What is working:
Android 9 + Magisk and TWRP
Android 9 + TWRP + Custom ROMs (LineageOS 16 and patched GSI)
Android 10 + Magisk and TWRP
Android 10 + Magisk and MicroG flashed via Magisk (= stock ROM without Google Services)
Android 11 + Magisk
What is not working:
Android 11 + Magisk + TWRP (TWRP logo flashes randomly but TWRP does not load).
Android 11 + Magisk + MicroG (the nanolx patching script does not work with Android 11 as of yet)
Encryption in Custom ROMs
Method to flash files via EDL
Unzip / unrar my files into the backup\full folder of the EDL tool and choose restore + full in the tool.
Unlock Bootloader:
Before you try any of the files, you MUST unlock your bootloader!
BACKUP of your data as it will be lost!
Download the EDL tool from this Thread
If your phone is not on android 9, you must go back to Android 9 first. e.g. by using my Android 9 1.9 backup.
After you restored it, restart while holding the volume + key and do a factory reset / format data.
Boot into EDL again and unlock the bootloader.
Now you are on android 9 with unlocked bootloader.
From here you can follow the other guides in the form and install TWRP or lineageos. Or flash one of my files below.
Flashing EDL files:
Unzip / unrar my files into the backup\full folder of the EDL tool and choose restore + full in the tool.
I put all my files into this MEGA account: MEGA
Android 10 version 2.9 Magisk + TWRP
Android 11 version 3.5 stock
Android 11 version 3.5 Magisk
Android 10 version 2.10 stock
Android 10 version 2.10 Magisk (TWRP can be flashed with Magisk)
Install MicroG:
Only works on Android 9 and 10.
Before you install MicroG you must patch the stock ROM to allow for signature spoofing.
The patcher script I used is on https://downloads.nanolx.org/NanoDroid/Stable/ When I write these lines the up-to-date-version is NanoDroid-patcher-23.1.2.20210117.zip
Reboot.
Install MicroG from the Magisk repository.
After a restart there will be error messages that google apps keep crashing. With each warning, disable the apps one by one.
When you reboot again, no errors should appear and MicroG should report that it is fully working.
You can add the Bromite Framework and give F-droid system rights. Both are available from the Magisk repo.
Updates will likely install the Google apps again and uninstall Magisk...
Revive phone:
Not really related, but I bricked my phone several times.
If your phones does not boot anymore or hangs in a bootloop, try accessing the EDL mode.
The easy way:
Boot while holding volume -
The hard way:
Old Volume +, volume - and power until you end up in EDL. The screen will be black, so it helps if you have the Phone connected to Windows and can hear the system sound when the USB sees a connection.
In anyway you can then use the EDL tool to restore / flash an EDL image.
On custom ROM support:
Well there is LineageOS 16 by Unjustified Dev. https://forum.xda-developers.com/t/rom-unofficial-zte-axon-10-pro-9-lineageos-16-0.3992127/ It works well. But has a patch level that is outdated by now.
On top of it you can install the GSI ROMs created by Rafyvitto. The latest one is Resurrection Remix https://forum.xda-developers.com/t/...nofficial-resurrection-remix-q-8-6-7.4172527/
with a security patch level of mid 2021. Which is recent enough to use. The stock roms are not much better.
With both Custom ROMs, encryption is not working which poses a privacy/security risk when your phone is stolen. Do not forget that your phone does not only contain your photos and data but also your passwords to your accounts.
Added Android 10 2.10 files.
Its nice to see anything new for this phone. I wish I can use these roms but I have the American version.
Hi and thanks for your work and your files.
I'm stuck on "Loading the programmer: prog_ufs_firehose_sdm855.elf >>>", if I try to recover your edl files with EDL Tool, v 3.25.
I have to choose option 2: "Restore Full EDL from backup", right?
Is there a way to check if the bootlaoder is really unlocked?
Thanks in advance
OK, I was able to solve the problem with the "programmer" and try the backups. The next step was almost clear. The device is stuck in bootloop. I've already tried all the backups I could find on Mega. After the EDL Tool has done its work and the device has restarted, the mobile phone goes into the boot loop. And now? So the starting position was: Android 9 with an open bootloader. Maybe someone has an idea?
After I couldn't get the device out of the bootloop, I flashed the A2020G_PRO_V1.6_FULL_EDL via MiFlash and then did an OTA update to 1.8.
Then I tried unlocking the bootloader again, which unfortunately didn't work. The flash is carried out without errors, but the device then apparently does not start in the desired Fastboot mode.
Thanks for your guide. However am I missing something with the Android 11+Magisk installation? I restored all the correct files and everything flashed correctly, however upon reboot there is no Magisk installed anywhere. Did a factory reset after the flash and still not there. Tried installing Magisk via his github and tried patching the boot.img again and it says success but after rebooting it says Magisk is not installed.
brian117 said:
Thanks for your guide. However am I missing something with the Android 11+Magisk installation? I restored all the correct files and everything flashed correctly, however upon reboot there is no Magisk installed anywhere. Did a factory reset after the flash and still not there. Tried installing Magisk via his github and tried patching the boot.img again and it says success but after rebooting it says Magisk is not installed.
Click to expand...
Click to collapse
Maybe you need to switch the slot in TWRP. It sounds as if you install it to the other slot (like A) an then boot B. Or vice versa.
Related
First- I am NOT Responsible if you brick your Device! You do everything at your own Risk!
As I cannot find successfull thread here guiding to root this tablet I am posting the success with rooting with Magisk, all is seen on Russian forum 4pda,but the firmware I am on is not here ,it was little hard to find it(paid) but at the end it works, I have full root:
1 .You must have UNLOCKED BOOTLOADER!!! You can do it here are 2 threads guiding to it,mine was with DC_unlocker-4USD;
2. You must download Magisk from its original thread :Link
3.You must Look at which firmware you are,download the patched ones :С170B003
С170B253
C100B270
Or you can download you full Rom, extract it using Huawei Firmware Extractor extract the BOOT.img from UPDATE.APP file transfer it to your tablet and using Magisk--> install choose boot.img and patch it, then copy the patched_boot.img from folder "Downloads" in the internal memory back to PC,rename to boot.img.
4.You must have installed ADB and fastboot.
5.Using fastboot command on PC install the patched boot.img to tablet:
-First on your tablet enable Developer Options, thick Enable OEM Unlock,thick USB Debugging on,when connected to PC must ask for Fingerprint Security Rsa key,thick Always Trust to this PC"
-Second Tunoff Tablet, then hold volume Down button and connect to PC with USB Cable,Fastboot menu must appear: With green at bottom must be written that it is not FRP locked! If so -dont do proceed disable remove Huawei Account if you have one!
-Third-copy patched boot.img to folder where is located ADB and fastboot, then hold shift and right click mouse button and click Open Command Prompt here.
Now on fastboot menu enter following:
fastboot.exe flash boot boot.img
At the end everything must be OK!
Reboot with power button and check in Magisk !
Regards
I just wanted to confirm that this method works for my tablet. My Huawei Mediapad M3 10.1" BAH-L09 had bootloader unlocked. Emui5.1.2 and OS 7.0. Following these instructions, I extracted the BOOT.img from the stock ROM, then used Magisk Manager app (6.0.1) to create the patched-boot.img. Flashing this patched-boot.img using fastboot mode with command:
fastboot flash boot patched_boot.img
My tablet now is ROOTED without any problems (camera works normally). In short, just follow exactly these instructions and your tablet will be ROOTED
This works for me on BAH-L09 with Build Number BAH-L09C100B270. My Tab ist now rooted with Magisk 17.1 installed. Next i do flash special version of TWRP from the TWRP Builder site. I took the version for the BAH-W09 (WIFI version of the tab) on my own risk. I KNOW thats not the correct version, so please dont criticize.
Installation via fastboot worked. I can boot into Huawei recovery (Power+Vol-up) and TWRP (Power + Vol-Up and Vol-down same time). System boots without problem too. Also i can flash back the original huawei rcovery.img in fastboot mode.
But there is an issue in this TWRP recovery version 3.2.1-0. It does not decrypt data. I tried to format data and flash "no-verity-opt-encrypt". But there is still an Huawei secure mechanism, that wants me to format data in Huawei recovery again. Without format data my tab do not boot into system.
Next step i tried to get TWRP for my device on TWRP-builder app. but no succes because the build queue ist full. So i have to wait...
Sorry but how did you unlock the bootloader?
DragonautMk said:
Sorry but how did you unlock the bootloader?
Click to expand...
Click to collapse
I used dc-unlocker (you can google for). Its easy but it costs ca. 4 €.
Does this method still works on latest ota ?
The4anoni said:
Does this method still works on latest ota ?
Click to expand...
Click to collapse
My M3 10 lite was on latest frmware C100B270 as i used dc-unlocker. Unlock worked well for me.
Does rooting enable you to install Google Services on the tablet? Is so, how?
Is there an international ROM that can be used (with Google tools)
Thanks! Worked for my Mediapad M3 lite 10 (BAH-L09), but now... How can I update Magisk? The Magisk manager doesn't support the version installed.
Can't install twrp either
---------- Post added at 08:40 PM ---------- Previous post was at 07:51 PM ----------
ossizwei said:
This works for me on BAH-L09 with Build Number BAH-L09C100B270. My Tab ist now rooted with Magisk 17.1 installed. Next i do flash special version of TWRP from the TWRP Builder site. I took the version for the BAH-W09 (WIFI version of the tab) on my own risk. I KNOW thats not the correct version, so please dont criticize.
Installation via fastboot worked. I can boot into Huawei recovery (Power+Vol-up) and TWRP (Power + Vol-Up and Vol-down same time). System boots without problem too. Also i can flash back the original huawei rcovery.img in fastboot mode.
But there is an issue in this TWRP recovery version 3.2.1-0. It does not decrypt data. I tried to format data and flash "no-verity-opt-encrypt". But there is still an Huawei secure mechanism, that wants me to format data in Huawei recovery again. Without format data my tab do not boot into system.
Next step i tried to get TWRP for my device on TWRP-builder app. but no succes because the build queue ist full. So i have to wait...
Click to expand...
Click to collapse
The same for me. Have you got the appropiatte twrp recovery?
wanlus said:
Thanks! Worked for my Mediapad M3 lite 10 (BAH-L09), but now... How can I update Magisk? The Magisk manager doesn't support the version installed.
Can't install twrp either
The same for me. Have you got the appropiatte twrp recovery?
Click to expand...
Click to collapse
This is an old post. Development has going forward. Look here:
For a LineageOS rom
https://forum.xda-developers.com/mediapad-m3/development/rom-t3945684
For TWRP
https://forum.xda-developers.com/mediapad-m3/development/twrp-t3914531
For the first step use the 3.2.0 version of TWRP if you are in Huawei's stock Rom.
For me its the best for this moment. Only issue is, that camera dont work in this early lineage rom. But developer is working on it.
ossizwei said:
This is an old post. Development has going forward. Look here:
For a LineageOS rom
https://forum.xda-developers.com/mediapad-m3/development/rom-t3945684
For TWRP
https://forum.xda-developers.com/mediapad-m3/development/twrp-t3914531
For the first step use the 3.2.0 version of TWRP if you are in Huawei's stock Rom.
For me its the best for this moment. Only issue is, that camera dont work in this early lineage rom. But developer is working on it.
Click to expand...
Click to collapse
Ok, thank you so much. I've got installed Twrp properly, and it boots ok... but no more. Now it stays on the recovery home screen. I'll try again
There is confusion over which recoveries to install for Redmi 6 (cereus).
Failure to install the correct TWRP will result in a hard brick with no chance of restoring the device without an authorised account or going to a Mi Service Centre.
If you are currently on the MIUI Oreo ROM:
You may ONLY use TWRP 3.3.0 OR 3.2.3-0 OR 3.2.3-1
The recovery by either TWRP or LR.Team is both ok.
If you are on the PIE rom:
You MUST use TWRP 3.3.1 or OrangeFox Recovery. R10.0-2 nocrypt Pie is confirmed to be working by me.
To root MIUI pie, follow the instructions in this post from 4PDA. This is because you will be unable to decrypt data.
You need to create an account to download the patched boot.img. You can either create one yourself or ask me or someone else to PM you with the boot.img. I will not attach it to this thread because it is not my work. The files have now been attached. See post below.
All credits go towards the respective recovery authors and 4pda
OK here are the boot files from 4pda
You MUST follow the instructions from this guide: http://4pda.ru/forum/index.php?showtopic=907017&st=5020#entry87853533
All files obtained from 4pda.ru - from a post by MCMXCII
Full credits go towards the authors of the respective .imgs
I did something wrong just don't know what
I tried with OrangeFox and when rebooted in recovery the phone would not turn on and just vibrates.
I was lucky because I just needed to open and remove the battery to get the phone back up.
So just to get it right (please correct me if i'm wrong):
Starting from unlocked MIUI stock with android 8.1 base:
0) Download patched boot image from OP
1)Download TWRP 3.3.0 OR 3.2.3-0 OR 3.2.3-1
2)Download Magisk 19.3 Stable (would the latest stable also work https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445?)
3)Download official Pie Rom: http://bigota.d.miui.com/V10.4.4.0.PCGMIXM/miui_HM6Global_V10.4.4.0.PCGMIXM_99304098f7_9.0.zip
4)Enter Fastboot -> Flash TWRP
5)Enter TWRP -> Flash the Pie Rom -> Flash patched boot.img -> flash Magisk
6)Boot into system -> Leave the device alone for 2-3 minutes and install Magisk Manager
7)Download -> TWRP 3.3.1 or OrangeFox Recovery. R10.0-2
8)Enter Fastboot -> Flash TWRP/OrangeFox
would this be the correct procedure?
cheers
snoerme said:
So just to get it right (please correct me if i'm wrong):
Starting from unlocked MIUI stock with android 8.1 base:
1)Download TWRP 3.3.0 OR 3.2.3-0 OR 3.2.3-1
2)Download Magisk 19.3 Stable (would the latest stable also work https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445?)
3)Download official Pie Rom: http://bigota.d.miui.com/V10.4.4.0.PCGMIXM/miui_HM6Global_V10.4.4.0.PCGMIXM_99304098f7_9.0.zip
4)Enter Fastboot -> Flash TWRP
5)Enter TWRP -> Flash the Pie Rom -> flash Magisk
6)Boot into system -> Leave the device alone for 2-3 minutes and install Magisk Manager
7)Download -> TWRP 3.3.1 or OrangeFox Recovery. R10.0-2
8)Enter Fastboot -> Flash TWRP/OrangeFox
cheers
Click to expand...
Click to collapse
?????????????????????
Why don't you skip steps 1-3 and just use XiaoMi Flash to install 10.4.4.0 via Fastboot by 'saving user data', then follow the instructions here? XiaoMiFlash will overwrite your recovery with the default so there is no risk of a brick. Then Flash TWRP Pie, flash boot img, flash magisk.
As I have said, you will brick your device. If you have TWRP Oreo, and then you install MIUI Pie, you will brick your device. You are doing EXACTLY what I told you not to do!
It didn't come out as clearly as you think. maybe it's my own deficiency.
btw whenever i flashed any update via TWRP the recovery got replaced by stock recovery as well.
(I don't tell this to call into question that your suggested way of doing was the most safe way.)
Is XiaoMi Flash available for linux as well?
edit: do you know if the latest magisk stable 20.0 would also work?
snoerme said:
It didn't come out as clearly as you think. maybe it's my own deficiency.
btw whenever i flashed any update via TWRP the recovery got replaced by stock recovery as well.
(I don't tell this to call into question that your suggested way of doing was the most safe way.)
Is XiaoMi Flash available for linux as well?
Click to expand...
Click to collapse
I'm not sure - I have never flashed any MIUI ROM in TWRP. It seems normal though - the updaterscript probably tells TWRP to overwrite itself.
https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847 It's a bit complicated
This work for me :
1 - Install Pie Rom https://bigota.d.miui.com/V10.4.4.0.PCGMIXM/miui_HM6Global_V10.4.4.0.PCGMIXM_99304098f7_9.0.zip with TWRP 3.3.1 https://mifirm.net/downloadtwrp/62 or with another method.
2 - Shut down the phone , go to fastboot (Vol - and power), plug to computer.
3 - From the computer fastboot flash boot boot_10.4.4.0_R6_mgsk_193.img (see the second post of this thread).
4 - fastboot flash recovery recovery-TWRP-3.3.1-0602-REDMI6-CN-wzsx150.img
5 - Recovery (Vol+ and power)
6 - Install Magisk 19.3
Reboot and enjoy
Hi, currently I'm on stable China mui v10.4.3.0. Do you have boot.img on that v10.4.3.0. Currently link only provide boot.img for v10.4.2.0 for the china version. If no how do I get those, can I just backup them from twrp, Then create patched boot img with those backup boot? Thanks
Che0063 said:
OK here are the boot files from 4pda
You MUST follow the instructions from this guide: http://4pda.ru/forum/index.php?showtopic=907017&st=5020#entry87853533
All files obtained from 4pda.ru - from a post by MCMXCII
Full credits go towards the authors of the respective .imgs
Click to expand...
Click to collapse
Thanx for boot_10.4.4.0_R6_mgsk_193.img :good:
ribou said:
This work for me :
1 - Install Pie Rom https://bigota.d.miui.com/V10.4.4.0.PCGMIXM/miui_HM6Global_V10.4.4.0.PCGMIXM_99304098f7_9.0.zip with TWRP 3.3.1 https://mifirm.net/downloadtwrp/62 or with another method.
2 - Shut down the phone , go to fastboot (Vol - and power), plug to computer.
3 - From the computer fastboot flash boot boot_10.4.4.0_R6_mgsk_193.img (see the second post of this thread).
4 - fastboot flash recovery recovery-TWRP-3.3.1-0602-REDMI6-CN-wzsx150.img
5 - Recovery (Vol+ and power)
6 - Install Magisk 19.3
Reboot an denjoy
Click to expand...
Click to collapse
ThanX ! ! !
This work for me :good:
EDIT:
The flashlight and the camera does not work after flash the boot boot_10.4.4.0_R6_mgsk_193.img [emoji848]
Does anyone else have a similar problem?
View attachment 4862683
I have the camera and flashlight problem too. Any fix?
Unfortunately, I didn't find any solution.
Currently, my phone does not start, has a black screen and vibrates all the time. I can't run it in any way
EDIT:
Hi.
I was able to bring the phone to life. Get instructions on how to get to the battery https://www.youtube.com/watch?v=L9FH88b16bc https://www.youtube.com/watch?v=fAflA4UKLLY. In orangeFox recovery I checked the flashlight, it works.
That makes us two. My phone is unusable at the moment. I thought the root was responsible for the camera bugs, I uninstalled magisk, the bug was still there. I tried to reinstall MIUI 10.4.4 ang got an error. I've wiped everything including vendor and system.
I clean dalvik and cache and for now the phone is working even, after flash the patch boot.img
ribou said:
This work for me :
1 - Install Pie Rom https://bigota.d.miui.com/V10.4.4.0.PCGMIXM/miui_HM6Global_V10.4.4.0.PCGMIXM_99304098f7_9.0.zip with TWRP 3.3.1 https://mifirm.net/downloadtwrp/62 or with another method.
2 - Shut down the phone , go to fastboot (Vol - and power), plug to computer.
3 - From the computer fastboot flash boot boot_10.4.4.0_R6_mgsk_193.img (see the second post of this thread).
4 - fastboot flash recovery recovery-TWRP-3.3.1-0602-REDMI6-CN-wzsx150.img
5 - Recovery (Vol+ and power)
6 - Install Magisk 19.3
Reboot an denjoy
Click to expand...
Click to collapse
Hello this is the steps i did but when rebooting to recovery i end up on blackcreen or mai i say powered off screen with the device unable to boot to recovery,any ideas what i did wrongly?
It seems there is something wrong with that boot patch. I followed a procedure on youtube and my phone is succesfully rooted without any bug
@ambyy
what guide did you use on YouTube?
Wysłane z mojego Redmi 6 przy użyciu Tapatalka
https://www.youtube.com/watch?v=I_4Zmco9R78&t=25s
Hard brick caused by flashing wrong TWRP is indeed able to get solved with unplugging the battery.
Miui v11 boot.img please
Hopefully someone can help me out here:
I'm on Mi 9T (davinici) with xiaomi.eu-cROM 12.1.2 (Stable) and OrangeFox Beta R11.0 Recovery. Bootloader is obviously unlocked.
I followed the guide for Magisk v22.0 and installed the apk first, opened it and it says
"Ramdisk No"
Alright, so I have to patch the recovery.img.
In Orangefox Recovery I open the Terminal and extract recovery.img with
Code:
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery.img
Reboot to system and I chose "Install" in Magisk, "Recovery Mode" is already selected, click "Next" and I select the newly created file "recovery.img". Magisk does it's thing and I have "magisk_patched_cOdEy.img" in my Download folder which I pull with adb.
I reboot to fastboot mode and
Code:
fastboot flash recovery magisk_patched_cOdEy.img
which works w/o problems and reboot again.
But when I open Magisk it still says it's not installed.
So, I check the guide under Magisk in Recovery, where it gets really confusing, but from what I got is that I need to start the phone with recovery button combo (Power+VolUp for Mi 9T) pushed and release at splash screen so Magisk is activated. I try this multiple times since it's really hard with the timing (milliseconds too long it kicks me into fastboot mode. idk why).
Can someone figure out what went wrong/what I did wrong? Never had problems with earlier Magisk versions.
Follow up question: There's some warning about going back to stock recovery will brick your phone in installation. Does that include installing OrangeFox again? I'm 95% sure it doesn't, but would be nice to know before I do it.
Some Xiaomi devices have their bootloaders set up so that it will accept an initramfs that was manually added to the boot image. Therefore, on these devices you'll need to patch the boot image even though there's no ramdisk. Try that.
Didgeridoohan said:
Some Xiaomi devices have their bootloaders set up so that it will accept an initramfs that was manually added to the boot image. Therefore, on these devices you'll need to patch the boot image even though there's no ramdisk. Try that.
Click to expand...
Click to collapse
Can I reinstall OrangeFox or TWRP recovery then?
I'll report back, when I tried it.
edit: So this actually works and I was able to enter TWRP recovery again after flashing.
edit 2: Now WiFi is not working anymore. fml.
edit 3: For anyone stumbling over this thread. Nothing worked, I had to do a compelte wipe and then flash Magisk "the old way", by renaming the .apk into a .zip and flashing it in recovery. That did the trick without any probems and I'm rooted now after quite a hassle.
yeah, I stumbled upon it. And I'm having the same/a very similar issue. I was very happy with Magisk up to v22 when the problems began.
I'm still at DerpFest based on Android 9.0 (from 2019 ) and TWRP-3.4.0.0.I had Magisk running since it was 19.4, upgraded it multiple times already. So didn't think much about updating to 22. Then, it said the same: no ramdisk. Pitty. OK, so I went ahead and let Magisk patch the TWRP.img I still got on my phone and flashed the patched TWRP onto recovery. Upon booting, Magisk is there, but no wifi, no sound, no light sensor, ... LTE works, though .
Anyways, I just want to get my old setup back, so I thought, I just flash the original TWRP again. According to the Magisk documentation, if I don't press any button, it should boot to Android without Magisk. Well, it always boots into Android+Magisk disregarding that. If I flash the original TWRP.img back, I always end up in TWRP. So, the order is: boot.img -> magisk-modified-recovery.img -> (boot.img?) -> system. How can I get the behaviour Magisk advertises?
And yes, I tried uninstalling Magisk (via uninstall.zip meythod), which said it would uninstall, but actually didn't. I also flashed different boot images (a backup I had in TWRP, the original boot.img I've found in the DerpFest zip...) to no avail.
So, Immortal68, which of the many wipes one can do did result in the old behaviour? And: now that you have Magisk22, does it say "Ramdisk: yes" again?
I decided to upgrade to the G9+ after finding a LineageOS ROM for the phone. Root via TWRP & Magisk worked without a hitch. Then I installed the LineageOS 18.1 ROM from here: https://www.getdroidtips.com/lineage-os-18-1-moto-g9-plus/
Next I went to install GApps via the Aroma setup, but found that TWRP was gone. There was some limited recovery from the ROM installation which didn't seem to be of any use, so I reflashed TWRP & then Magisk, but I didn't get root back.
The phone now has a working version of LineageOS, but I can't even get the Google crap I need.
When I try to flash something via TWRP I get an error saying there was a "Zip signature verification failure", so I can't even get back to stock ROM to try again. (I guess this error is related to not having root.)
(I installed TWRP & Magisk on another G9+ with stock ROM and everything seems as expected. The phone is rooted. I just want to get rid off all the Google software I can.)
Anyone got an idea how I can get root back?
------
And any reason why "ADB devices" doesn't list the attached phone? "Fastboot devices" works fine.
Have u tested lineage, is
everything working fine?
UsmanQ said:
Have u tested lineage, is
everything working fine?
Click to expand...
Click to collapse
Everything seems to be there, seems normal. Except root.
doktorspin said:
Everything seems to be there, seems normal. Except root.
Click to expand...
Click to collapse
doktorspin said:
Everything seems to be there, seems normal. Except root.
Click to expand...
Click to collapse
Have u tried superoot or something else instead of magisk?
Sapper Morton said:
The ROM that you're using is not meant to be daily driven, Erfan compiled that for experimental purposes, but that aside, there's a few things that you should take in consideration when using Lineage; It's not meant to be used with TWRP, that's why they ship their own recovery (Lineage Recovery). It's still possible to flash custom files with it (That doesn't match their original signature), you just need to skip a warning.
For Magisk, download the latest stable build from here: Download
(The .apk has the flashing script built-in, so just rename that to .zip).
One major difference from TWRP, is that Lineage Recovery doesn't support decrypting userdata, so the files must be flashed using ADB or USB OTG.
Use ADB Sideload as follows:adb sideload magisk.zip
As for me, I didn't unlocked my device yet, so if you could confirm me something: I need to know if I will lose my DRM certification, used for Netflix, Disney+, Prime Video and such.
Download Castro from Play Store, go to the DRM tab, and check the Widevine status, tell me if it remains L1, or if it downgraded to L3. That's what's holding me back from testing, or even compiling for this device.
Click to expand...
Click to collapse
Thanks for the response.
1. I'm using the Github Magisk 23.
2. Lineage Recovery is gone. I reflashed TWRP.
3. Attempting to use "ADB sideload Magisk-v23.0.zip" ADB responds "cannot read 'Magisk-v23.0.zip'"
4. I haven't got Play Store on the phone as I can't flash the aroma package (1.7GB) via TWRP.
UsmanQ said:
Have u tried superoot or something else instead of magisk?
Click to expand...
Click to collapse
I don't know anything about the other methods for getting root. I've always used Magisk.
(I'm working under the idea that as TWRP + Magisk works fine on one phone, they aren't the problem.)
Sapper Morton said:
The idea is to rollback to Lineage Recovery, you can even flash only the boot.img that it's inside the ROM flashable file, instead of reflashing the whole thing again. It's probably in payload.bin format, so you'll need a payload firmware extractor (Easily found on GitHub), in case you choose the first option.
• Aroma is not supported on Lineage Recovery, so I would recommend something smaller, like OpenGapps nano or stock.
Click to expand...
Click to collapse
<rant>
What sort of idiots build in a crap recovery when one has obviously already installed a functional recovery, needed in the process of gaining root and installing LineasgeOS? This unnecessary included recovery wasn't in previous versions of LOS I've used.
Yes, this is an unpleasant surprise and I'm ticked off. I'm an end user who wants a relatively de-Googled phone, but now to maybe get a functional recovery I have to extract stuff from a payload file, but to do that I have to install more crud so that I can run the tool that does the extracting.
And I need Aroma to be able to select what I must have from Google. My partner needs their voice tech. I could dump almost everything else and use Pico. </rant> Sorry.
Is there no way to wipe the slate clean, get rid of this Lineage, and start again?
(I don't understand how installing their recovery could ruin the functionality of another recovery.)
Sapper Morton said:
Download Castro from Play Store, go to the DRM tab, and check the Widevine status, tell me if it remains L1, or if it downgraded to L3. That's what's holding me back from testing, or even compiling for this device.
Click to expand...
Click to collapse
On the second G9+ which I rooted but left the stock ROM, I installed Castro and it indicates L3.
doktorspin said:
I decided to upgrade to the G9+ after finding a LineageOS ROM for the phone. Root via TWRP & Magisk worked without a hitch. Then I installed the LineageOS 18.1 ROM from here: https://www.getdroidtips.com/lineage-os-18-1-moto-g9-plus/
Next I went to install GApps via the Aroma setup, but found that TWRP was gone. There was some limited recovery from the ROM installation which didn't seem to be of any use, so I reflashed TWRP & then Magisk, but I didn't get root back.
The phone now has a working version of LineageOS, but I can't even get the Google crap I need.
When I try to flash something via TWRP I get an error saying there was a "Zip signature verification failure", so I can't even get back to stock ROM to try again. (I guess this error is related to not having root.)
(I installed TWRP & Magisk on another G9+ with stock ROM and everything seems as expected. The phone is rooted. I just want to get rid off all the Google software I can.)
Anyone got an idea how I can get root back?
------
And any reason why "ADB devices" doesn't list the attached phone? "Fastboot devices" works fine.
Click to expand...
Click to collapse
take a look at this group of telegram, here they can help you to return
Lolinet [English Only]
Our website: MIRRORS.LOLINET.COM Our channel: https://t.me/lolinetnews Please speak in English
t.me
Lineage is working fine, some details that will be fixed when releasing the new kernel
There is a method to root with magisk by patching the ramdisk its a way better rooting method then with twrp in fact magisk dev recommends this way of rooting if you have not tried this here is a magisk official link https://topjohnwu.github.io/Magisk/install.html
Hope This helped you bro
The ROM in the O.P. works.
Folks, I actually made a number of mistakes in this process.
The major one was to muff the fastboot command for flashing TWRP. I had followed instructions which said to boot TWRP, which didn't install TWRP, just loaded it into phone memory. But...
The ROM cited in the O.P. doesn't seem to have any problems that I have noticed in my usage, which is basically as a hand computer, not as a phone.
LineageOS now overwrites recovery with its own recovery, which is pretty moronic, because the user has already had to install a recovery to root the device.
But fortunately, if you have your ADB/fastboot apps handy with TWRP in the same folder it's an easy fix.
You should already have this stuff, but use the following software:
sebastian3367HD has provided TWRP for G9+ users onsight here. I'll assume it's called "twrp.img".
Magisk-v23 here -- put it somewhere easy on your phone.
Also get GApps 11. I used core NikGapps here, select latest date, then the version of GApps you want. (The core version 82MB just gives you Play Store & support software.) Put it the same place on the phone you put Magisk.
Assuming you've flashed the O.P. LineageOS ROM, which overwrites trusty TWRP, put your phone in fastboot mode, either using
1. power button + volume down
until you get the droid image on its back, or get there with your phone on, sending
2. adb reboot bootloader
via the windows command shell.
You're now in fastboot mode. You can now flash TWRP back onto the phone. Note that the phone has two slots of memory, so that the phone can hold two operating systems. If you send
fastboot flash recovery twrp.img
it will be flashed to the current slot, either A or B. To be safe you should flash both:
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
That gives you the safety of having TWRP in both slots. (Incidentally, TWRP allows you to changes slots.) (Also remember if you reflash LineageOS you'll have to put TWRP back on if you want a decent recovery program.)
Use TRWP to Reboot to Recovery.
Now install Magisk using TWRP:
Spoiler: (You know this)
a) choose Install
b) if the bottom right button says Install Zip press it and it will change to Install Image
c) if you put Magisk on your external SD card Select Storage to choose the SD
d) find and select Magisk-v23.0.apk, then
e) swipe to flash.
Then install GApps, basically the same as for Magisk.
Reboot to System. You should be rooted now and should have Play Store (and whatever else you opted for).
M.Akram said:
There is a method to root with magisk by patching the ramdisk its a way better rooting method then with twrp in fact magisk dev recommends this way of rooting if you have not tried this here is a magisk official link https://topjohnwu.github.io/Magisk/install.html
Hope This helped you bro
Click to expand...
Click to collapse
Thanks for the info. My problem was simple to fix, using the right commands!
I haven't installed that rom because afaik the source tree isn't available anywhere which seems kind of fishy, if anyone knows where they are please let us know
I use a Redmi Note 7 (lavender) with LineageOS 18.1 with the LineageOS recovery. My device does not have ramdisk.
I decided to install Magisk. I followed the tutorial and flashed the Magisk recovery image to recovery using fastboot. When I boot with the recovery combination (Power + volume up) it does not boot into recovery, but if I long press volume up, it does. But the Magisk app says Magisk is not installed. Flashed again and it still didn't work. So I decided to uninstall it. Since the app did not detect Magisk, I renamed the APK into "uninstall.zip" and sideloaded it usng adb from the LineageOS recovery. That installed Magisk. Today,I decided to boot without Magisk, powering on my phone the usual way (long press Power), but Magisk still works. What is going on?
That's probably just a problem with the Installation Guide.
I just realized that if you flash the apk as a zip it installs Magisk onto boot and it worked, because I do have ramdisk, even ough Magisk tought me I don't.
You've likely got a type of device that doesn't have ramdisk in boot, but still accepts an added initramfs.
It's practically impossible to determine if this is the case, but generally Xiaomi devices are this way, so many Xiaomi users have to install to boot even though they have a "Type III" device (as described here: https://topjohnwu.github.io/Magisk/boot.html#piecing-things-together).