Database Info

Root mate 9 oreo with magisk

Hello guys I just want an explanation on how to root mate 9 c185 (370) oreo from scratch explain it to a noob cause I just soft broke my phone trying to do it thank you
From 0 step please

Please anyone

Iloudsan said:
Please anyone
Click to expand...
Click to collapse
1. Unlock bootloader
2. Download magisk manager and install it
3. Extract ramdisk.img from fw
4. Run magisk manager and choose the ramdisk.img u copied on ur phone internal memory and create the patched_boot.img
5. Flash the patched_boot.img through fasboot flash ramdisk patched_boot.img
Done

Addymore said:
1. Unlock bootloader
2. Download magisk manager and install it
3. Extract ramdisk.img from fw
4. Run magisk manager and choose the ramdisk.img u copied on ur phone internal memory and create the patched_boot.img
5. Flash the patched_boot.img through fasboot flash ramdisk patched_boot.img
Done
Click to expand...
Click to collapse
Sorry if I sound noob but from where to extract the ram disk exactly do I extract it from the main update.zip?

Iloudsan said:
Sorry if I sound noob but from where to extract the ram disk exactly do I extract it from the main update.zip?
Click to expand...
Click to collapse
Yep.... Using Update Extractor Tool.... Remember to uncheck "Verify header checksum" in settings for oreo fw.... Otherwise it fails to extract

Addymore said:
Yep.... Using Update Extractor Tool.... Remember to uncheck "Verify header checksum" in settings for oreo fw.... Otherwise it fails to extract
Click to expand...
Click to collapse
and is there any way to Disable Encryption ? in oreo i only know how to do it in android 7

Addymore said:
Yep.... Using Update Extractor Tool.... Remember to uncheck "Verify header checksum" in settings for oreo fw.... Otherwise it fails to extract
Click to expand...
Click to collapse
rooted successfully but would love to have it encrypted cause i dont have SD card as i use 2 sim cards so i cant flash anything in twrp

Iloudsan said:
rooted successfully but would love to have it encrypted cause i dont have SD card as i use 2 sim cards so i cant flash anything in twrp
Click to expand...
Click to collapse
Actually twrp cannot decrypt the internal storage...! U have to use external sd.... No other choice for now....

Hello,
Based on instructions below I managed to install Magisk via patched_boot.img onto Mate9 Oreo 8.0.0.363(C432). I downloaded few modules like Xposed etc, after restarting I got a bootloop. When I back install ramdisk.img phoneboots but magisk is not installed. Any help is appreciated.

no need to extract ramdisk no more....the new one will install with twrp from sd card....starting 15v and also has to have bootloader unlock and be on stock oreo....

cross1989 said:
no need to extract ramdisk no more....the new one will install with twrp from sd card....starting 15v and also has to have bootloader unlock and be on stock oreo....
Click to expand...
Click to collapse
It cannot be installed any other way. Says no boot image.

Are you on stock android... I did root my mate 9...you need the special twrp for mate 9..its in the forum for magisk... Then just boot into twrp, do normal wipe, then install magisk, start with 15.4 version... Then it should update to 16..

Hi,
I've found an simpler method to root my Oreo Mate 9, which does not involve extracting the ramdisk.img of your rom.
This method comes for @ante0 in this post.
In my case (Mate9 with stock rom L29C432B366), this is what I did:
1) Start from an unrooted stock Oreo rom
2) Unlock bootloader
Note: Unlocking the bootloader will completely erase your phone, so backup before hand!
3) Download and flash (via fastboot) TWRP recovery TWRP-3.2.1-Oreo_FBE_Mate9.img
This recovery can be downloaded from the link in here
Note: to flash the recovery in Fastboot mode you have to type from the command line on the PC :
fastboot flash recovery_ramdisk TWRP-3.2.1-Oreo_FBE_Mate9.img
4) Reboot in recovery and mount the System and Vendor partitions
Note: if you skip this step, your phone will NOT reboot after step (5) :crying: (I know, I have tested this )
5) In recovery, flash the latest Magisk. I Have used the latest beta, Magisk 16.4 which can be downloaded from here.
6) Reboot system, and you're good to go, rooted and passing safetynet
What I like about this method is (1) no need to extract a ramdisk.img specific to the rom you are rooting , and (2) I'm still decrypted in recovery
Note: Not tested with other rom versions than L29C432B366

how magisk works in mate9 C432 B369 ??
i try 16.0 cust and my mate9 soft brick

I need help guys.
I tried installing xposed from magisk app. After reboot, am stuck on bootloop after several retries. Was forced to flash new firmware using HWOTA8.Now,i have tried getting magisk to work but result to boot loop after boot is patched and flashed via fastbokt.Have also tried flashing through twrp by mounting system, vendor but still stuck on Huawei logo and reboot . Have tried flashing supersu but that does get root to work.
Please help because most of the app I use need root access and don't want to perform fresh installation.
Thanks.

Oneplus 6 - twrp boot not working

Hello,
I have bricked and unbricked my op6 with msm download tool.
Now i tried to install lineage and followed the instructions.
I tried following:
- with twrp standard
- with blu
- with twrp in Boot_a and b
In all cases the reboot lead to a dark screen.
Any idea?
BR Martin

You will have to msm flash

anupsnair said:
You will have to msm flash
Click to expand...
Click to collapse
That is what i did - twice already... Still no Boot into twrp...

martinforum said:
Hello,
I have bricked and unbricked my op6 with msm download tool.
Now i tried to install lineage and followed the instructions.
I tried following:
- with twrp standard
- with blu
- with twrp in Boot_a and b
In all cases the reboot lead to a dark screen.
Any idea?
BR Martin
Click to expand...
Click to collapse
From what firmware are you from?

Hitman478™ said:
From what firmware are you from?
Click to expand...
Click to collapse
MSM included OOS 5.1.5
Update required to which version to make twrp bootable?

martinforum said:
MSM included OOS 5.1.5
Update required to which version to make twrp bootable?
Click to expand...
Click to collapse
Thank you. Yes this was the reason why! I can boot in twrp again.
There are different howto's out there. What is the right order to install following packages - do I have to reboot after each package?
Twrp
Lineage rom
Openapps Pico
Su

I did not fully understand the problem but i can see one thing: oos 5.1.5 as a base firmware for lineage is not correct because oreo firmware is not supported, so in order
if you want only TWRP
Update to the latest firmware (oos 10)
follow this guide: https://forum.xda-developers.com/oneplus-6/how-to/guide-installing-bluspark-twrp-magisk-t3997765
If you want lineage 16/17
Update to the latest open beta pie (28)
reboot to fastboot
download TWRP img and zip (9.101)
open windows prompt and type "fastboot boot twrp.img" (make sure to insert the correct name file instead of twrp.img and check if is .img and not the .zip)
device will automatic reboots in TWRP
now from here flash the TWRP .zip file and reboot to recovery to make sure it's there
now you can update recovery to 9.107 if you want (and it's highly reccomended) by flashing the proper 9.107 .zip
don't forget to use blue_spark TWRP
Now everytime you flash a rom you need to flash TWRP after that otherwise it will not stay there
hope it's all clear and that i've not forgot anything

Hitman478™ said:
I did not fully understand the problem but i can see one thing: oos 5.1.5 as a base firmware for lineage is not correct because oreo firmware is not supported, so in order
if you want only TWRP
Update to the latest firmware (oos 10)
follow this guide: https://forum.xda-developers.com/oneplus-6/how-to/guide-installing-bluspark-twrp-magisk-t3997765
If you want lineage 16/17
Update to the latest open beta pie (28)
reboot to fastboot
download TWRP img and zip (9.101)
open windows prompt and type "fastboot boot twrp.img" (make sure to insert the correct name file instead of twrp.img and check if is .img and not the .zip)
device will automatic reboots in TWRP
now from here flash the TWRP .zip file and reboot to recovery to make sure it's there
now you can update recovery to 9.107 if you want (and it's highly reccomended) by flashing the proper 9.107 .zip
don't forget to use blue_spark TWRP
Now everytime you flash a rom you need to flash TWRP after that otherwise it will not stay there
hope it's all clear and that i've not forgot anything
Click to expand...
Click to collapse
Thank you. Blue_spark twrp is working.
Now i have installed lineage and without reboot oppengapps pico but I do get an error message.
To ensure twrp, i reinstalled as you said bstwrp. But the reboot brings me back to a black screen.
Any tips for the right order to install and reboot?

General [SHARED] [UNOFFICAL][Stock Oxygen OS][Fastboot ROM][Firmware]OOS11.2.10.10 and OOS 12(C47)

What's this?This is a stock oxygen os fastboot Rom for OnePlus9 adapted from https://forum.xda-developers.com/t/...xygenos-a-04-a-07-for-mt2110-devices.4404719/ .I really appreciate @Valdem for his flashing script for OnePlus 9RT.And I modified his script according to OnePlus 9 partitions and changed some flashing order in script.
Note that this is only for the device which is unlocked bootloader.And internal storge may be cleaned if you downgrade from higher oxygen rom or come from other rom like custom rom.
The ROM's image is extracted from oos11.2.10.10BA and oos12(LE2113_C47) ota package.Note that the ROM is only for ONEPLUS9(LEMONADE).
For full package oxygen os:
Flashing instructions:
- On your PC, install bootloader drivers for OP9 and check if device is recognized in Bootloader and Fastbootd modes.
- On your PC, download the Fastboot ROM zip from the download link below.
- On your PC, unzip downloaded file
- On your PC, navigate to its now-uncompressed folder
- Reboot your OnePlus 9 to bootloader mode.
- Connect the OP9 to your PC
- On your PC open command line window in the uncompressed folder,
- double click flash-all.bat
- wait till PC shows "pause" on terminal.
-Whether to format data is depend on which rom you stayed before. If upgrade from older oxygen os or on the same version oxygen os,no need to format data.Otherwise format data and reboot phone.
For firmware package:
Firmware package is used for whom wants to install custom ROM.And flashing firmware package by using this instead of MSM can streamline the procedure.After the PC shows "pause"on termianl,firmware package has been installed completely.Then following the custom rom install procedure-flash boot boot.img.If not boot into recovery,replace phone into bootloader mode,flashing dtbo and vendor_boot partitions will work.
The using procedure is same as full package.
NOTE:Before using this fastboot ROM and Firmware,you must have a compatible boot.img which can flashing images in fastbootd mode.Oherwise,install the "boot.img","dtbo.img"and"vendor_boot.img"by using "fastboot flash boot boot.img","fastboot flash dtbo dtbo.img"and"fastboot flash vendor_boot vendor_boot.img"in phone's bootloader mode.If phone don't boot into recovery or fastbootd mode,flashing firmware(If target is OOS11,then flashing oos11.2.10.10 firmware;If target is OOS12,then flashing firmware OOS12C47).After this,reflashing boot,dtbo and vendor_boot.
Download link:
Oxygen os 11.2.10.10:OOS11.2.10.10(FULL PACKAGE)
Oxygen os 12(LE2113_C47):OOS12(LE2113_C47)(FULL PACKAGE)
Firmware package:
Oxygen os 11.2.10.10 firmware:OOS11.2.10.10firmware package
Oxygen os 12(LE2113_C47) firmware:OOS12(LE2113_C47)firmware package

in A12, which recovery do you use.
bec. twrp does not survive an Android 12 upgrade.
TWRP no compatible with A12

jmadiaga said:
in A12, which recovery do you use.
bec. twrp does not survive an Android 12 upgrade.
TWRP no compatible with A12
Click to expand...
Click to collapse
This script uses fastboot, not recovery. Custom ROMs typically post the recovery image to use for flashing them in the thread if you're asking about that.

Any one success in flashing OOS11.2.10.10 or OOS12(C47) by using this script?

cbrown666 said:
Any one success in flashing OOS11.2.10.10 or OOS12(C47) by using this script?
Click to expand...
Click to collapse
Fastboot scripts are the quickest path to bricking and having to use MSM in my experience so I'm not trying it. If you do, make sure you switch to slot A first because for some reason, slot B really doesn't like to cooperate on this device.

Has anyone been able to root on Android 12?

Patching AP.tar with magisk doesn't seem to work...

What do you mean it's not work? What error message do you get? Got a screenshot? Thanks

When I flash patched AP.tar, I get "error verifying vbmeta: HASH MISMATCH" error. I followed the official instructions for installing magisk.
I also tried flashing patched boot.img, but I get another error saying that only official firmware is allowed to be installed.
I never installed magisk this way, so I don't know if this procedure worked on previous Android versions (or if I'm even doing it right considering it's Samsung...).

umh..I made the mistake of connecting my M21 2021 Edition to internet and it updated something in the blink of an eye and then when I checked Developer Options the OEM Unlock button disappeared. I cant flash TWRP-ODIN-patch-file anymore , it shows Secure Download error in Download Mode also Custom Binary Blocked error. Without TWRP I cant flash anything. I'm dead!

I am also getting same error, I downloaded my firmware from samfw.com (SM-M215F / Android 12 / Binary 3), then I extracted it to my PC. Then copied AP file from PC to my phone, Patched it using Magisk v25.2 (From Github). Copied patched file from phone to PC. Flashed it using Odin v3.14.4 (BL, AP, CP, CSC). Getting error that VBMETA ERROR HASH_MISMATCH (3).
Has anyone found solution for it?

xyncronix said:
I am also getting same error, I downloaded my firmware from samfw.com (SM-M215F / Android 12 / Binary 3), then I extracted it to my PC. Then copied AP file from PC to my phone, Patched it using Magisk v25.2 (From Github). Copied patched file from phone to PC. Flashed it using Odin v3.14.4 (BL, AP, CP, CSC). Getting error that VBMETA ERROR HASH_MISMATCH (3).
Has anyone found solution for it?
Click to expand...
Click to collapse
You dont want to use Custom Recovery?

xyncronix said:
I am also getting same error, I downloaded my firmware from samfw.com (SM-M215F / Android 12 / Binary 3), then I extracted it to my PC. Then copied AP file from PC to my phone, Patched it using Magisk v25.2 (From Github). Copied patched file from phone to PC. Flashed it using Odin v3.14.4 (BL, AP, CP, CSC). Getting error that VBMETA ERROR HASH_MISMATCH (3).
Has anyone found solution for it?
Click to expand...
Click to collapse
I have successfully rooted my m21 with Android 12 . Watch the
Follow the process described here . Root will be successful.

OldNoobOne said:
You dont want to use Custom Recovery?
Click to expand...
Click to collapse
Custom recovery is good but to flash we can use Odin by samsung. Official samsung software.

Flashing the whole AP feels pretty big. All you actually need is the boot image. Extracting it from the stock rom can be pretty annoying though. If patching ap isn't working for you there's two ways to go. Either flash the magisk apk from recovery (this still works for m21) or patch just the boot image and flash it using Odin or recovery.
You can get the boot image of your respective stock rom from here inside the AP folder.
1. Patch the boot image using the magisk app and rename the patched boot image to "boot.img"
2. Add boot.img it to a tar archive
3. Flash the tar file to AP in Odin
Something you need to note is that magisk no longer patches some stuff from v25.0, so there's a small chance it might bootloop. So ideally, patch using magisk 24.x and then you can update later on using the magisk app.

.

[Updated September 2022] How to root A7 2018

Disclaimer​
Do this at your own risk as I will not be responsible for your bricking the phone or rendering it unusable. Proceed with caution!
Click to expand...
Click to collapse
If you want to root stock and for some reason want to have the latest security update, you have a problem and I'll help you do it.
What I did below is tested on an A7 SM-A750GN/DS but any A750x should work as well.
Prerequisites​
Latest magisk zip
Latest firmware from anywhere you like (my personal favourite is a toll-free website samfw.com)
Latest firmware from 2020
Latest Odin
Working custom recovery: tested on OrangeFox
DM-Verity disabler zip file
Time, a lot!
Unlocking bootloader​Steps:
Go to developer option > Software information > Tap on the build number 7 times to unlock developer option
Go to developer option and enable OEM unlock
Proceed as prompted and it will reset the phone
Set up as normal and move on to the next section
Rooting the phone​Steps:
Turn off the phone
Plug in the cable to the computer (Leave it plugged in for the remaining of the process)
Hold all 3 keys (up down volume, and power) at once and when the turquoise-ish screen pops up, press volume up key
Extract and get files from downloaded firmwareS [AP, BL (Take the BL file from the 2020 firmware, the latest BL will not allow any current custom recovery to function properly), CP, CSC]
Add the corresponding files to its boxes (AP_A750xxx to the AP slot; BL_A750xxx to the BL slot and so on)
Flash it
When the screen goes black, quickly hold all buttons again to re-enter Download mode
Uncheck all BL, CSC, CP, leaving AP
Add the recovery.tar file to the AP slot and press start
Boot to recovery
Flash magisk zip and then the DM-Verity disabler zip file
Go to wipe > Format data > Type "yes"
Reboot, et Voilà your phone is now rooted on the latest security update
If your phone is showing [Installed: N/A; Ramdisk: No] then reboot, there might be some error with the magisk app.

Reserved !

Reserved !

So I need to flash a stock firmware from 2020?

LadyAmy said:
So I need to flash a stock firmware from 2020?
Click to expand...
Click to collapse
No, just the bootloader because the latest custom recoveries of our devices support BL up to 2020 only.

Edit: Never mind, just realized, that there is a November 2020 Binary 5 Firmware.

Ronan Hansel said:
Disclaimer​
If you want to root stock and for some reason want to have the latest security update, you have a problem and I'll help you do it.
What I did below is tested on an A7 SM-A750GN/DS but any A750x should work as well.
Prerequisites​
Latest magisk zip
Latest firmware from anywhere you like (my personal favourite is a toll-free website samfw.com)
Latest firmware from 2020
Latest Odin
Working custom recovery: tested on OrangeFox
DM-Verity disabler zip file
Time, a lot!
Unlocking bootloader​Steps:
Go to developer option > Software information > Tap on the build number 7 times to unlock developer option
Go to developer option and enable OEM unlock
Proceed as prompted and it will reset the phone
Set up as normal and move on to the next section
Rooting the phone​Steps:
Turn off the phone
Plug in the cable to the computer (Leave it plugged in for the remaining of the process)
Hold all 3 keys (up down volume, and power) at once and when the turquoise-ish screen pops up, press volume up key
Extract and get files from downloaded firmwareS [AP, BL (Take the BL file from the 2020 firmware, the latest BL will not allow any current custom recovery to function properly), CP, CSC]
Add the corresponding files to its boxes (AP_A750xxx to the AP slot; BL_A750xxx to the BL slot and so on)
Flash it
When the screen goes black, quickly hold all buttons again to re-enter Download mode
Uncheck all BL, CSC, CP, leaving AP
Add the recovery.tar file to the AP slot and press start
Boot to recovery
Flash magisk zip and then the DM-Verity disabler zip file
Go to wipe > Format data > Type "yes"
Reboot, et Voilà your phone is now rooted on the latest security update
If your phone is showing [Installed: N/A; Ramdisk: No] then reboot, there might be some error with the magisk app.
Click to expand...
Click to collapse
where's the link for the needed files?

welp I can root my phone properly, but if I put a lock screen it gives me this loop when booting up, that's why I have to do a factory reset and right now I don't have a lock screen on my phone
https://imgur.com/a/VSYYQKB

SafetyNet doesn't pass (Response payload validation failed)
Tried version 25.2
EDIT: this helped:
[GUIDE] Passing Safetynet
This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders or custom verified boot keys. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on January 12, 2021...
forum.xda-developers.com

Thank you for this guide! It worked perfectly on my SM-A750FN variant. I've used the latest Android 10 ROM for the AP, CP & CSC files and the BL file from the last 2020 Android 10 ROM, OrangeFox recovery as well, but flashed Magisk v23.0, since any newer version uses Zygisk and it doesn't really work with my device (Tried v25.2 but can't use modules and the app displays: Installed: None, Ramdisk: No etc.).
If anyone wants to download the files I used here they are:
Download the roms for your device from here (NOTE: You need registration to download).
OrangeFox recovery from here (NOTE: PBRP should work as well, but do NOT use TWRP).
If you want you can download only the ".tar" files for the recoveries from here: OrangeFox or PitchBlack.
Magisk v23.0 from here (Optionally you can set your update channel to custom and paste this channel URL: https://raw.githubusercontent.com/topjohnwu/magisk-files/afe2c304e59f631280cc26ccc6d40a7cf04f7f37/stable.json in the Magisk app settings to prevent you from updating the it accidentally ).

Pozdrav evo provadim 5 dana na rutovanju telefona samsung A750G ul.2 i nemoze . Ako ima neko da je to odradio nek se javi i objasni.

Hey do I have to flash the complete firmware or just the BL. I'm currently running the July 2022 patch and I downloaded the firmware from 2020, so do I flash the entire firmware or just the BL from 2020
Please help, I have awful battery life and I'm trying to get as much improvement by rooting

Holding Volume up, down and power boots the phone normally, not in recovery mode.

This is what worked for me :