Related
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.
WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are NOT risking voiding your warranty!
I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Hello!
Some people asked me how to root Xiaomi Pocophone F1 with magisk and to keep stock recovery on it, to recive OTA updates etc. so this is the complete guide
Sorry for all language misstakes, my english is not perfect, so please, if you have found anything, inform me via private message, so I can edit the post and correct it.
1. Unlock Bootloader Unlocking Bootloader Explanation and Troubleshooting for NEWBIES | thanks to @madsponge26
2. TWRP boot (not flashing, you will keep your stock recovery)
3. Pull stock boot.img from your phone (method II)
4. Boot.img patching (Patching stock boot.img with magisk manager app) (method II)
5. Patched magisk boot.img flashing (method II)
Tools and Information we need
USB Driver
Minimal ADB Fastboot
TWRP 3.2.3-x Unofficial with working DECRYPTION 12/10/2018
Magisk Manager App
How to Unlock Bootloader
Back up Files (Internal Storage)
1. Go to Settings > About phone
2. Find the MIUI Version and press 6-8 times
3. Go to Additional Settings > Developers Options
4. Press and check USB Debugging and OEM Unlocking
5. Go to Settings > Developers Options > Mi Unlock Status > Add Account & Device and log in with your MI account.
6. Go to MIUI Unlock website
7. Login to your MI account
8. You should be able to download Mi Unlock and unlock bootloader without filling any forms or applying for permissions (I was able to do that this way)
- if not, then apply and wait.
*Install Xiaomi USB Drivers from link above or by Mi Unlock app settings option.*
In MI Unlock app:
1. Shut down your phone manually, and hold Volume down key and Power button to enter Fastboot mode.
2. Connect your phone to PC using USB cable and click "Unlock".
***Mi account should verified.
Booting into TWRP, getting ADB SuperUser access, pulling stock boot.img
1. Open Minimal ADB Fastboot terminal AS ADMINISTRATOR!
2. Shut down your phone
NOW FOCUS
3. Connect your phone to your PC and hold Power and Volume Down buttons until Fastboot screen will be visible.
4. Follow the steps:
Put that command in your Minimal ADB Fastboot terminal:
Code:
fastboot devices
Your phone should be visible.
example: ,,7e00a8e3 fastboot"
Code:
fastboot boot <path to your TWRP .img recovery file>
Your phone should be booted into TWRP recovery.
If ask's for password: CLICK CANCEL
If ask's for keeping /system read only: swipe (allow modifications)
UPDATE:
NOW YOU CAN JUST FLASH MAGISK.ZIP AND REBOOT
There was no TWRP with working decryption before.
Method II:
Code:
adb devices
Your phone should be visible.
example: ,,7e00a8e3 recovery"
Code:
adb shell
Here we go! We got access to Super User shell via ADB ^^
and now the magic:
- In TWRP recovery, go to Advanced > File Manager
- Go to "/dev/block/platform/" folder (go into ,,soc" folder, if you have one there)
- Here you will see some files and folders, we need to open folders and search for the folder called "by-name" inside one of them. || For me it was /dev/block/platform/soc/1d84000.ufshc and ,,by-name" inside of it.
- At the end, we need name of the folder contains ,,by-name" inside for this string: /dev/block/platform/soc/FOLDER NAME/by-name
- Now go to your ADB Shell terminal and put that command:
soc = you should have this folder too, if not; ignore (please confirm that in comments)
FOLDER NAME = your folder with ,,by-name" inside
Code:
ls -al /dev/block/platform/[COLOR="DarkOrange"][B]soc[/B][/COLOR]/[COLOR="Red"][B]FOLDER NAME[/B][/COLOR]/by-name
Now you should see partitions of your phone.
You need to find your boot partition, for me it was:
Code:
lrwxrwxrwx 1 root root 16 Feb 15 1970 [B][COLOR="Red"]boot[/COLOR][/B] -> [B][COLOR="Red"]/dev/block/sde45[/COLOR][/B]
--
Pulling our stock boot.img!
Go to your ADB Shell terminal and put that commands:
Replace sde45 with your partition from step above*
Code:
dd if=/dev/block/[B][COLOR="Red"]sde45[/COLOR][/B] of=/sdcard/boot.img
Code:
exit
Code:
adb pull /sdcard/boot.img
Our stock boot.img should be downloaded into our Minimal ADB Fastboot directory!
Code:
adb reboot
Stock boot.img patching and flashing (For Method II only)
1. Save your stock boot.img into phone's internal storage/sdcard
2. Download latest Magisk Manager from MAGISK GITHUB REPO
3. Install Magisk Manager on your phone.
4. Open Magisk Manager, check Keep Force Encryption
5. Click Install > Install > Boot Image Patching > Select your stock boot.img and patch it.
6. Save your patched boot.img to your computer
7. Shut down your phone
8. Open Minimal ADB Fastboot terminal on your PC
9. Connect your phone to your PC and hold Power and Volume Down buttons until Fastboot screen will be visible.
4. Follow the steps:
Enter commands:
Code:
fastboot devices
Your phone should be visible.
example: ,,7e00a8e3 fastboot"
Code:
fastboot flash boot <path to your patched_boot.img>
Code:
fastboot reboot
5. Open Magisk Manager, your phone should be rooted.
6. Download Root Checker from Play Store and check if your device is rooted.
FOR OTA UPDATES:
- Uninstall magisk with Magisk Manager App (Restore Image option)
- Apply OTA update
then:
Method I:
- Boot into twrp (version with working decryption)
- Flash Magisk ZIP again
Method II:
- Pull boot.img and patch it again
- Flash new patched boot.img
If you have any questions or problems, type those in the comment below, I will try to help you
Stock Mi Recovery 3.0 for Pocophone F1: GOOGLE DRIVE
Before flashing OTA update, you need to uninstall magisk and install it again after update.
Thanks for a great tutorial, this is what I needed, just a few queries.
1. After ota will I retain root or again the whole process will have to be repeated.
2. In this process if I start with an unlocked bootloader with 8.10.9 beta rom any chance or need to wipe data or internal storage.
3. What if after flashing twrp, I just flash magisk and reboot without flashing force encryption disabler, stock recovery will automatically overwrite twrp, will I lose any data or root.
sanjay0501 said:
Thanks for a great tutorial, this is what I needed, just a few queries.
1. After ota will I retain root or again the whole process will have to be repeated.
2. In this process if I start with an unlocked bootloader with 8.10.9 beta rom any chance or need to wipe data or internal storage.
3. What if after flashing twrp, I just flash magisk and reboot without flashing force encryption disabler, stock recovery will automatically overwrite twrp, will I lose any data or root.
Click to expand...
Click to collapse
1. For now you need to uninstall magisk root before any OTA update, and install it again after it. I don't figured it out yet, how to update OTA and keep magisk.
2. Mi Unlock App will tell you if your internal storage needs to be wiped or not after connecting your phone in fastboot mode.
For me there was a red text that my internal storage will be wiped, for you it will be propably similar.
3. In this tutorial you are not flashing TWRP, you are just booting your phone into TWRP without flashing it to get acess to Super User via ADB and to pull stock boot.img to patch it later with magisk.
Target of this tutorial is to keep stock recovery, so it wont be overwrited because you will be already using it. It shouldn't affect magisk root, but
it would be an good idea to check ,,Keep Force Encryption" in Magisk Manager app before patching boot.img if you are not going to flash Disable Force Encryption zip etc.
exepowered said:
1. It depends propably on OTA update type. Can't answer for sure now, but OTA is comming on Friday with new version of MIUI 10 Beta so I will check that.
2. Mi Unlock App will tell you if your internal storage needs to be wiped or not after connecting your phone in fastboot mode.
For me there was a red text that my internal storage will be wiped, for you it will be propably similar.
3. In this tutorial you are not flashing TWRP, you are just booting your phone into TWRP without flashing it to get acess to Super User via ADB and to pull stock boot.img to patch it later with magisk.
Target of this tutorial is to keep stock recovery, so it wont be overwrited because you will be already using it. It shouldn't affect magisk root, but
it would be an good idea to check ,,Keep Force Encryption" in Magisk Manager app before patching boot.img if you are not going to flash Disable Force Encryption zip etc.
Click to expand...
Click to collapse
Thanks for ur help.
Hi, thanks for the tutorial but I have a problem when unlocking my bootloader, when I am on the Mi unlock application and I connect my phone in fastboot mode mi unlock do not recognize my phone and therefore impossible to click unlock.
My computer recognizes the phone well but not the application do you have solutions?
Open it as administrator
Wysłane z mojego POCOPHONE F1 przy użyciu Tapatalka
uremytoy said:
Open it as administrator
Wysłane z mojego POCOPHONE F1 przy użyciu Tapatalka
Click to expand...
Click to collapse
I opened it in administrator mode, it does not work
Inside unlock tool there are drivers. Try to install them. I've had the same and it worked for me
Wysłane z mojego POCOPHONE F1 przy użyciu Tapatalka
hey dudes, can someone please upload the stock recovery for me?
everytime the phone wants to install an ota it just boots into twrp and i have to manually reboot it from there.
so if i just flash the stock poco recovery the phone would updtate the ota normally and root still would be there?
Before flashing OTA update, you need to uninstall magisk and install it after update.
WasIstDenn said:
hey dudes, can someone please upload the stock recovery for me?
everytime the phone wants to install an ota it just boots into twrp and i have to manually reboot it from there.
so if i just flash the stock poco recovery the phone would updtate the ota normally and root still would be there?
Click to expand...
Click to collapse
Stock Mi Recovery 3.0 for Pocophone F1: GOOGLE DRIVE
Before OTA update, uninstall magisk via Magisk Manager App, then after update install it again using my guide, otherwise you will get bootloop.
I don't figured it out yet, how to keep magisk live when updating.
exepowered said:
Stock Mi Recovery 3.0 for Pocophone F1: GOOGLE DRIVE
Before OTA update, uninstall magisk via Magisk Manager App, then after update install it again using my guide, otherwise you will get bootloop.
I don't figured it out yet, how to keep magisk live when updating.
Click to expand...
Click to collapse
So after uninstalling magisk and applying OTA, we need to do whole process again? pull out boot - patch it and flash it?
at this point it makes more trouble than just installing twrp.
For now there is twrp with decryption working so you can flash magisk ZIP, with booted twrp (not flashed).
I used the same boot I had before OTA and there was no problems too.
exepowered said:
For now there is twrp with decryption working so you can flash magisk ZIP, with booted twrp (not flashed).
I used the same boot I had before OTA and there was no problems too.
Click to expand...
Click to collapse
You extracted the boot image, patched it using magisk, and flashed it using fastboot.
Instead, can't we just install Magisk.zip using twrp? This way it saves us from running all those commands.
For OTA, we can uninstall magisk and flash original stock recovery, then apply ota, then flash twrp and magisk.zip.
Correct me if I am wrong.
Thanks
anirudh281998 said:
You extracted the boot image, patched it using magisk, and flashed it using fastboot.
Instead, can't we just install Magisk.zip using twrp? This way it saves us from running all those commands.
For OTA, we can uninstall magisk and flash original stock recovery, then apply ota, then flash twrp and magisk.zip.
Correct me if I am wrong.
Thanks
Click to expand...
Click to collapse
I know what I have done.
But if the same patched boot.img is not working after uninstalling and OTA update, you can skip other steps and just boot into twrp [version with working decryption] (everything is in my post) and flash ZIP. ZIP does the same thing, it patches boot.img so it's just faster for now. When I was doing this tutorial, there was no twrp with working decryption for poco...
You can try to flash same patched boot.img you had before OTA. Last time it worked for me.
You don't need to flash twrp too...
Just uninstall magisk
Do OTA update
BOOT into twrp (version with working decryption)
Flash magisk.zip
reboot
exepowered said:
I know what I have done.
But if the same patched boot.img is not working after uninstalling and OTA update, you can skip other steps and just boot into twrp [version with working decryption] (everything is in my post) and flash ZIP. ZIP does the same thing, it patches boot.img so it's just faster for now. When I was doing this tutorial, there was no twrp with working decryption for poco...
You can try to flash same patched boot.img you had before OTA. Last time it worked for me.
You don't need to flash twrp too...
Just uninstall magisk
Do OTA update
BOOT into twrp (version with working decryption)
Flash magisk.zip
reboot
Click to expand...
Click to collapse
I flash the decryption TWRP and install magisk but the phone bootloops back to recovery no matter what I try. I have to uninstall magisk using the official installer, only then the phone lets me boot into system but obviously I lose root. Any guesses what I should do to get root with formatting storage ?
Hey dude! Is there any way to unlock my poco f1 bootloader without wiping the data?
SusanooX said:
Hey dude! Is there any way to unlock my poco f1 bootloader without wiping the data?
Click to expand...
Click to collapse
Nope
Is it equal, on wich (original) ROM/Software-Verisom i´am for unlocking, flashing twrp and rooting ?
Or is it the best, to NOT update the original Rom OTA and after that unlocking, flashing twrp and rooting ?
After installing new stock OTA, before rebooting I used to flash magisk via manager. Now with magisk app v22 this doesn't work anymore?
Procedure from the xda guide: Magisk Root without TWRP for OnePlus 6 Oxygen OS
After installing a stock ota magisk root is lost, but above guide showed a very simple procedure to reinstall:
1. install ota but don't reboot
2. open magisk manager and install magisk (there was an option to install after ota)
reboot and done
Now that magisk manager has been replaced with magisk app above option isn't available anymore and after tapping "install" I am asked for a file.
If that's the way things are now, that's fine. For the first time in my life I'll have no root and I'll live with it - to keep things simple
icaros1530 said:
After installing new stock OTA, before rebooting I used to flash magisk via manager. Now with magisk app v22 this doesn't work anymore?
Procedure from the xda guide: Magisk Root without TWRP for OnePlus 6 Oxygen OS
After installing a stock ota magisk root is lost, but above guide showed a very simple procedure to reinstall:
1. install ota but don't reboot
2. open magisk manager and install magisk (there was an option to install after ota)
reboot and done
Now that magisk manager has been replaced with magisk app above option isn't available anymore and after tapping "install" I am asked for a file.
If that's the way things are now, that's fine. For the first time in my life I'll have no root and I'll live with it - to keep things simple
Click to expand...
Click to collapse
The file it's looking for is your boot.img from the firmware you are on. Magisk will "patch" it for root. You then place the magisk_patched.img on you pc. Boot to fastboot and flash it to reboot with root.
fastboot flash boot magisk_patched***.img
That's how it's done on my phone st least.
Tulsadiver said:
The file it's looking for is your boot.img from the firmware you are on. Magisk will "patch" it for root. You then place the magisk_patched.img on you pc. Boot to fastboot and flash it to reboot with root.
fastboot flash boot magisk_patched***.img
That's how it's done on my phone st least.
Click to expand...
Click to collapse
That's it! Sometimes I use my other phone that's rooted with magisk as well and tks to the adb/fastboot magisk module by Osm0sis and Surge I fastboot flash the patched boot.img from mg other phone connected to mine using a OTG cable. I just toss the patched boot.img in termux apps prper directory which is: data/data/com.termux/files/home/magisk-patchedboot.img , and flash it: fastboot flash boot magisk-patchedboot.img --slot all then reboot system and done.
Adb+fastboot installer magisk module: https://forum.xda-developers.com/attachments/update-adb-installer-v1-0-41-signed-zip.5293523/
Hello everyone hope you are all keeping well.
Here is a little guide on how to Unlock/Lock the Bootloader and Root/Unroot our Nord2T.
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
Unlock The Bootloader;
If you haven't done it already...beware that this will erase all of your user data. To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
Code:
adb devices
(just to make sure that your phone is, in fact, recognized by your PC and that you're able to run adb commands)
Code:
adb reboot bootloader
(so your phone will reboot into fastboot mode)
Code:
fastboot flashing unlock
(device should now unlock)
Code:
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
Rooting Guide;
Unlocking the Bootloader is necessary before continuing
1 - Download Nord2T stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Spoiler: Global Build boot.img's
Stock boot CPH2399_11_A.07 (did not extract it and can't find the firmware file to be able to download and extract, if someone could please upload a link to it on this thread I would sincerely appreciate it)
Stock Boot CPH2399_11_A.09
Stock Boot CPH2399_11_A.11
Stock Boot CPH2399_11_A.14
Stock Boot CPH2399_11_A.15
Stock Boot CPH2399_11_A.16
Stock Boot CPH2399_11_A.17
Stock Boot CPH2399_11_A.19
Stock Boot CPH2399_11_C.24
Stock Boot CPH2399_11_C.26
Stock Boot CPH2399_11_C.27
Spoiler: IND Build boot.img's
Stock Boot CPH2401_11_A.11
Stock Boot CPH2401_11_A.13
Stock Boot CPH2401_11_A.14
Stock Boot CPH2401_11_A.15
Stock Boot CPH2401_11_A.16
Stock Boot CPH2401_11_A.17
Stock Boot CPH2401_11_A.18
Stock Boot CPH2401_11_A.19 (I didn't capture the download for this, if anyone has it please send me a link to the official OTA)
Stock Boot CPH2401_11_C.23
Stock Boot CPH2401_11_C.24
Stock Boot CPH2401_11_C.26
Stock Boot CPH2401_11_C.27
2 - Download latest Magisk Manager from HERE and install it on your phone
3 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
4 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
5 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
6 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
7 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
System Updates;
For system updates. Just apply the OTA update as normal.
Once updated you will have no root and you must follow steps above again with the new boot.img that corresponds to the firmware version you are on.
Unroot;
To unroot simply flash the stock boot.img.
Relock Bootloader;
If you have TWRP installed flash the stock boot.img (same as your firmware version from earlier in this post)
This is so as you can access fastboot properly.
1 - To relock Bootloader first download Oxygen Updater app from the Playstore.
2 - Download the firmware which corresponds to the firmware which you have currently installed.
3 - Move/copy this firmware.zip to your PC and extract it. (inside you will see a folder and a couple files. The only file we need is payload.bin)
4 - Download/install Fastboot Enhance on your PC
5 - Reboot phone to bootloader mode so it gets detected by Fastboot Enhance, from there boot to fatsbootd.
6 - Flash payload.bin in Fastboot Enhance
7 - Wipe data in fastbootd from your Nord 2T, reboot and finish phone setup.
8 - Enable developer options, enable USB debugging from developer options.
9 - Reboot to bootloader and run the command;
Code:
fastboot flashing lock
The device will be now successfully locked.
Hope this helps out
Thank you so much
Thanks so much. Going to try this weekend with my daughter phone.
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
jolaviska said:
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
Click to expand...
Click to collapse
No I still haven't received the ota. Did you get updated to this version already?
I received the update but refusing to apply it
jolaviska said:
I received the update but refusing to apply it
Click to expand...
Click to collapse
It will show up again.
Don't worry.
Rooted my Nord 2T successfully. Thanks once again
Download Nord2T stock boot.img
Click to expand...
Click to collapse
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
luke! said:
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
Click to expand...
Click to collapse
By using THIS software. I will always update this thread with the latest boot.img files in the future but this is the software I used
Thank you.
And what is the procedure to OTA update, once we have magisk_patched_boot.img installed.
OTA won't install, so need to revert somehow install new update and root again?
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Stock Global boot CPH2399_11_A.11 added to OP. Sorry for the delay, only received the update today
nielsync said:
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Click to expand...
Click to collapse
Ya I didnt do it this way at all because my device updated while i was asleep and i was unrooted, so I had to patch the new boot using the method in the OP.
I would definitely advise restoring the stock boot.img before proceeding with an update, then install the update normally and just patch the new image with magisk and then flash.
For a while the 'install to inactive slot' option only works on certain devices, the Nord 2T obviously is'nt one of those devices.
I'm sure the magisk documentation recommends restoring stock images before an update.
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
cioce said:
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
Click to expand...
Click to collapse
I didn't want to share any of the magisk images because there is a new version of magisk every other week and people may like to be on the beta branch or canary branch of magisk or whatever.
It's very easy to patch the image though. Just download magisk.apk and use it to patch the boot.img's I've provided above. Then move the patched.img to your pc and flash.
But anyways here is the magisk patched.img for CPH2399_11_A.11 using magisk 25.2 stable
Stock Boot for Indian variant CPH2401_11_A.13 added to OP
can u post the latest update boot.img for indian unit CPH2401_11_A.14
Stock boot for Indian CPH2401_11_A.14 added to OP
Stock boot for Global CPH2399_11_A.14 added to OP
Hi guys,
I've crashed my OP9 due flash an older boot.img.
Today I updated to C61, flashed a patched C46 boot image for root.
Now the phone holds on at the OnePlus Start logo.
Has anyone an untouched boot.img from C61 Firmware?
I've installed the global Firmware, but I believe, it doesn't matter.
Thanks and regards!
[email protected] said:
Hi guys,
I've crashed my OP9 due flash an older boot.img.
Today I updated to C61, flashed a patched C46 boot image for root.
Now the phone holds on at the OnePlus Start logo.
Has anyone an untouched boot.img from C61 Firmware?
I've installed the global Firmware, but I believe, it doesn't matter.
Thanks and regards!
Click to expand...
Click to collapse
Search online I find it there 2
I'm searching for boot.img of EU version. Could you please share where you found yours?
Method confirmed to work for OnePlus 9 EU (LE2113) and OnePlus 9 Global (LE2115) - Enjoy!
Update rooted C.47 to C.61:
Open magisk, click 'Uninstall magisk'
Reboot
Updated via standard system update to C.61 . (At first it failed at 99% for me, but on second try it completed successfully). Alternatively: try the Oxygen updater to download the C.61 OTA incremental update.
Reboot
Easy way to root C.61:
Download the patched boot.img:
EU (LE2113 - Europe) from Mega
or Global (LE2115) from GDrive or Mega
Place the downloaded boot file in the same folder as your adb.
Open a terminal or command prompt in that folder and execute: "adb reboot bootloader"
Execute "fastboot boot .\C.61_boot_magisk_patched-25100_Bvj5U.img" to temporarily boot the patched boot file.
Download & install Magisk 25.1.
Open Magisk. If it indicates 'Installed Magisk: n/a', you're device was not correctly rooted. If it says 25.1, you can patch your boot to make the root stay:
Select 'Direct Install' and reboot.
Congrats!
DIY way:
All files here on a Mega folder if it helps you guys save time
Download C.61 OTA incremental update from the cellphone (both in-built system update and Oneplus Updater give the same download).
Use Payload dumper to extract the stock boot.img and copy it to your phone.
Download and install Magisk 25.1 on your phone, use 'Select and Patch a File' to patch the stock boot.img which creates magisk_patched-25100_4vi6c.img
Copy this file to your desktop and run the following commands to boot the patch:
boot in fastboot: "adb reboot bootloader" in terminal
temporarily boot the patched boot file: "fastboot boot .\magisk_patched-25100_4vi6c.img"
After reboot, open Magisk. If it indicates 'Installed Magisk: n/a', you're device was not correctly rooted. If it says 25.1, you can patch your boot to make the root stay:
Select 'Direct Install' and reboot.
Congrats!
(Optional) Way to extract your current boot file from a rooted phone:
Ensure you're rooted
Execute "adb reboot bootloader" on your pc
To check the current active boot partition execute "fastboot getvar all" on your pc and look for "(bootloader) current-slot:a" meaning you'll be using boot_a.img later on or "(bootloader) current-slot:b" for boot_b.img
Execute the following commands on your pc:
adb shell
su
dd if=/dev/block/bootdevice/by-name/boot_a of=/sdcard/Download/boot_a.img
dd if=/dev/block/bootdevice/by-name/boot_b of=/sdcard/Download/boot_b.img
exit
adb pull /sdcard/Download/boot_a.img boot_a.img
adb pull /sdcard/Download/boot_b.img boot_b.img
Whichever boot partition was active in step 3 is the one you want
xHalt said:
Same here. I can find boot.img for the OnePlus 9 Pro (EU) but not for the OnePlus 9 (EU).
I tried the payload dumper on the incremental update (instructions do tell you it doesn't work on incremental .zip, only on full .zip). I got the boot.img out of it and was able to patch with Magisk 25.1, but when booting it's not rooted yet.
All files here on a Mega folder if it helps you guys save time :
My phone: OnePlus 9 EU - LE2113
Issue I had: Couldn't update to C.61
I was on C.47, rooted with Magisk 25.1. Tried to update through the system pop-up as well as through the Oxygen Update to update to C.61. It kept failing at 21%.
Steps I took to update:
Uninstalled magisk
Updated via standard system update failed at 99%.
I retried with the Oxygen updater and now it succeeded to 100%
Rebooted
Issue: now I'm no longer rooted.
Steps I took to root again:
Downloaded C.61 OTA incremental update from the cellphone (both in-built system update and Oneplus Updater gave the same download).
Used Payload dumper to extract the stock boot.img and copied it to my phone.
Installed Magisk 25.1 on my phone, used 'Select and Patch a File' to patch the stock boot.img which created magisk_patched-25100_4vi6c.img
Copied this file to my desktop and ran the following commands to try and boot the patch:
boot in fastboot: "adb reboot bootloader" in terminal
termporarily boot the patched boot file: "fastboot boot .\magisk_patched-25100_4vi6c.img"
It takes a LONG time to boot, but eventually it does boot correctly.
Issue: however, Magisk is NOT installed and I'm not rooted yet.
I also tried to install TWRP recovery but keep getting the Qualcomm Crashdump Mode.
boot in fastboot: "adb reboot bootloader" in terminal
temporarily boot the TWRP recovery: "fastboot boot .\twrp-3.6.2_11-0-lemonadep.img" in terminal
Issue: Qualcomm Crashdump Mode pops up and is stuck there
Anyone able to figure the last step out?
Appreciated!
Click to expand...
Click to collapse
i am in a similar situation. my OP 9 (EU) is (still) on the c47 build with the latest magisk. I never updated to c48 but have now decided to give c61 a try. But iam not able to install the OTA, inbuild system is crashing @ 35%, even with the local install method and the loaded update from the oxygen updater, its still crashing. Today i uninstall magisk, flash the c47 stock boot.img and vendor_boot.img but it still crashing. After some research I tried to reset the phone. Device is now fully wiped, only the bootloader is unlocked. But i still got this crashes What did you do to install the update ? my next try is to use the MSN tool from this forum, but i'm afraid to brick my device.
I have extracted the original boot.img and vendor_boot.img from LE2115_11_C.61 using MsmDownloadTool (F8 > select the desired partitions > ReadBack) and uploaded to GoogleDrive.
My OP 9 EU version is on build C.48 (rooted with Magisk) and I also have the issue where the update crashes at 21%.
Did anyone already find a solution on how to upgrade to C.61 without data loss?
MrMagic said:
My OP 9 EU version is on build C.48 (rooted with Magisk) and I also have the issue where the update crashes at 21%.
Did anyone already find a solution on how to upgrade to C.61 without data loss?
Click to expand...
Click to collapse
I spent a few hours trying to solve the problem. no chance. I ended up using the msm tool. after that it was possible to update from C37 to C48 and finally to C61.
I just found this in the OP9 Root topic:
Root OnePlus 9
This is for Europe (11.2.2.2.LE25DA). If you are on Global, EU version works, but up to you. It appears for last year, unless you are from India, OnePlus doesn't care. It might be a while before a Full OTA update for Global is released, you'll...
forum.xda-developers.com
Apparently you can use the boot.img from the C.61 OP9 Pro build on the regular OP9.
I was finally able to go from c47 rooted to c61.
Now I have no root.
Any way to get it?
aldoc01 said:
I was finally able to go from c47 rooted to c61.
Now I have no root.
Any way to get it?
Click to expand...
Click to collapse
Try the updated instructions above. Can confirm it works now.
@xHalt Did you do anything else besides uninstalling Magisk to get the C.61 OTA update to install?
I am on C.48 and uninstalled Magisk, but I still cannot install the C.61 OTA. Tried both the standard system updater and Oxygen Updater.
Not sure why it's failing because it doesn't give any meaningful error message.
Is there a stock boot image I can flash to get past this error?
Daeril said:
I have extracted the original boot.img and vendor_boot.img from LE2115_11_C.61 using MsmDownloadTool (F8 > select the desired partitions > ReadBack) and uploaded to GoogleDrive.
Click to expand...
Click to collapse
Amazing, @Daeril ! Thank you. It works.
Updated the instructions for everyone.
MrMagic said:
@xHalt Did you do anything else besides uninstalling Magisk to get the C.61 OTA update to install?
I am on C.48 and uninstalled Magisk, but I still cannot install the C.61 OTA. Tried both the standard system updater and Oxygen Updater.
Not sure why it's failing because it doesn't give any meaningful error message.
Is there a stock boot image I can flash to get past this error?
Click to expand...
Click to collapse
I updated from C.47 and only had to reboot.
Try with the stock boot indeed: I included the stock boot for C.47 in the Mega folder or direct link here.
Alternatively: revert to C.47 first? Files also in the Mega folder.
aldoc01 said:
I was finally able to go from c47 rooted to c61.
Now I have no root.
Any way to get it?
Click to expand...
Click to collapse
Please see the updated instructions above and let me know if it works for you.
xHalt said:
Try with the stock boot indeed: I included the stock boot for C.47 in the Mega folder or direct link here.
Alternatively: revert to C.47 first? Files also in the Mega folder.
Click to expand...
Click to collapse
I tried with the stock boot already. Flashed it with fastboot, but didn't make any difference.
Do you know how I would go about reverting to C.47 without data loss? I have the ZIP file on my phone, but the updater says I cannot install it because the version is older than what I'm already running.
MrMagic said:
I tried with the stock boot already. Flashed it with fastboot, but didn't make any difference.
Do you know how I would go about reverting to C.47 without data loss? I have the ZIP file on my phone, but the updater says I cannot install it because the version is older than what I'm already running.
Click to expand...
Click to collapse
Only way is sadly with data loss/reset afaik.
xHalt said:
Please see the updated instructions above and let me know if it works for you.
Click to expand...
Click to collapse
working!!
thanks mate