Database Develop

Anyone figured out how to root ALI_RETAIL_9.0_PPSS29.118-15-11-2?

I've tried everything and I just get a bootloop. If anyone has the steps that worked for them I'd love to have my root back. Thanks community!

What exactly have you tried? We can't give you a solution for problems we don't know...

Had the same problem on 118-15-11-2, so I flashed 55-37-7 instead and it rooted fine on Magisk 20.1.

Will 55-37-7 work with Tmobile Moto G6? Haven't tried flashing that one yet.

fireman644 said:
Will 55-37-7 work with Tmobile Moto G6? Haven't tried flashing that one yet.
Click to expand...
Click to collapse
I have a Moto G6 (Ali) xt1925-6 and yes currently on retail ppss29.55-37-7 which has October patch. I've not had any problems flashing the 118 or the 55 retail builds as long as they have same or newer security patches.

Skippy12359 said:
Had the same problem on 118-15-11-2, so I flashed 55-37-7 instead and it rooted fine on Magisk 20.1.
Click to expand...
Click to collapse
Did you install Magisk by patching the recovery.img (recovery mode)? Normal installation through boot.img causes a bootloop, afaik.
https://forum.xda-developers.com/moto-g6/how-to/magisk-twrp-moto-g6-t4006983

WoKoschekk said:
Did you install Magisk by patching the recovery.img (recovery mode)? Normal installation through boot.img causes a bootloop, afaik.
https://forum.xda-developers.com/moto-g6/how-to/magisk-twrp-moto-g6-t4006983
Click to expand...
Click to collapse
After flashing and setting up 55-37-7 stock pie, I booted to twrp and flashed magisk 20.1. It boot fine and then installed magisk manager apk and had root.

Skippy12359 said:
After flashing and setting up 55-37-7 stock pie, I booted to twrp and flashed magisk 20.1. It boot fine and then installed magisk manager apk and had root.
Click to expand...
Click to collapse
Alternate route - I flashed to ALI_RETAIL_9.0_PPS29.118-11-1 (back to July Pie) and used magisk 19.3, DM Verity Disabler from August.
Seems to work fine, but wants to keep updating the system with latest version of Pie from December.
I did try to flash ALI_RETAIL_9.0_PPS29.55-24, but that killed my T-Mobile connection (wouldn't turn on the radio and/or recognize the SIM.)
Can anyone tell us what the difference between 55 and 118 variants are?
PS. My phone is the U.S. G6.

oldguy51 said:
Alternate route - I flashed to ALI_RETAIL_9.0_PPS29.118-11-1 (back to July Pie) and used magisk 19.3, DM Verity Disabler from August.
Seems to work fine, but wants to keep updating the system with latest version of Pie from December.
I did try to flash ALI_RETAIL_9.0_PPS29.55-24, but that killed my T-Mobile connection (wouldn't turn on the radio and/or recognize the SIM.)
Can anyone tell us what the difference between 55 and 118 variants are?
PS. My phone is the U.S. G6.
Click to expand...
Click to collapse
The big question is which variant of the Moto G6 do you have? For example I have XT1925-6 which is the US Unlocked variant. You need to flash the correct firmware for your variant.
https://mirrors.lolinet.com/firmware/moto/ali/official/
Go here once you know your variant to get the exact right firmware. Who is your provider?

I have the XT-1925-6 Tmobile US unlocked bootloader. I had root with PPS29-118-11-1. Now that I have updated to -2 I have lost root and get a bootloop everytime I try and flash Magisk or DM-verity. Could you help? Thanks.

fireman644 said:
I have the XT-1925-6 Tmobile US unlocked bootloader. I had root with PPS29-118-11-1. Now that I have updated to -2 I have lost root and get a bootloop everytime I try and flash Magisk or DM-verity. Could you help? Thanks.
Click to expand...
Click to collapse
Maybe you should try try "retail" firmware. If you havr the xt-1925-6 variant, it will work. US unlocked will accept it. The version is ALI_RETAIL_9.0_PPS29.55-37-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
It worked for many of us. You can use RSDLite, as long as you are connected by a USB 2 port. Do a backup first, because your internal storage will be deleted.
If you truly have an xt-1925-6, it will work

Yeah I tried flashing the firmware but it wouldn't take. Gave me errors at the beginning and wouldn't flash. I'll try again with a USB 2 port and RSDlite. I was using manual commands.

theseeker2654 said:
The big question is which variant of the Moto G6 do you have? For example I have XT1925-6 which is the US Unlocked variant. You need to flash the correct firmware for your variant.
Go here once you know your variant to get the exact right firmware. Who is your provider?
Click to expand...
Click to collapse
I'm connecting to T-Mobile, but I can't remember if the phone is used or a New in Box from Amazon at some point. It is a GSM version.
Here's a pair of questions that might help us noobs:
1. How do you tell which version of the moto g6 phone you have? (if there's a link to another discussion that gives this info, awesome.)
2. Is there a map of the hardware types to appropriate retail images? When I looked in the RETAIL directory for the link above, there appears to be two versions for 9.0 - 29.55 and 29.118 - with my phone functioning in the .118 stream through trial and error.
Thanks!
-og

OK I have used the ALI_RETAIL_9.0_PPS29.55-37-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and the device will boot stock. Wiped it and followed the usual steps to root it. Once I apply Magisk or dm_verity disabler there is a bootloop. Could anyone please provide the steps needed to root and prevent the bootloop. I have tried everything that I can think of. Using Magisk 20.2 and dm_verity 12/27/19. Should I try another version? Thank you.

fireman644 said:
OK I have used the ALI_RETAIL_9.0_PPS29.55-37-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and the device will boot stock. Wiped it and followed the usual steps to root it. Once I apply Magisk or dm_verity disabler there is a bootloop. Could anyone please provide the steps needed to root and prevent the bootloop. I have tried everything that I can think of. Using Magisk 20.2 and dm_verity 12/27/19. Should I try another version? Thank you.
Click to expand...
Click to collapse
According to posts in this thread, one says don't use dm_verity zip and another says edit fstab.qcom. I haven't tired either yet as I'm still on Aug patch with updates "disabled".

Here is how I eventually rooted PPSS29.118-15-11-2:
https://forum.xda-developers.com/showpost.php?p=81229155&postcount=381
I was never able to boot after trying to flash TWRP, so I just didn't bother flashing TWRP. Booting it manually was enough.
I only flashed Magisk-19.4 from TWRP, nothing else. I have no idea if directly flashing a newer Magisk might have worked.
I'm now updated to Magisk-20.3 and everything works.

fireman644 said:
OK I have used the ALI_RETAIL_9.0_PPS29.55-37-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and the device will boot stock. Wiped it and followed the usual steps to root it. Once I apply Magisk or dm_verity disabler there is a bootloop. Could anyone please provide the steps needed to root and prevent the bootloop. I have tried everything that I can think of. Using Magisk 20.2 and dm_verity 12/27/19. Should I try another version? Thank you.
Click to expand...
Click to collapse
For the installation of Magisk I used the .zip v19.3 because the latest (v20.3) caused a bootloop.
Here are the steps that worked for me:
1.) Boot into TWRP and copy the fstab.qcom from /vendor/etc
2.) Edit fstab.qcom like this:
line 9: forceencrypt=/dev/block/bootdevice/by-name/metadata => encryptable=/dev/block/bootdevice/by-name/metadata
This will remove forceencryption and will only work if you format /data!! But you should do this anyway before flashing the magisk.zip
3.) Replace the fstab.qcom in/vendor/etc with the edited one. Be sure the permissions are 0644 (rw-r--r--). To change it open the terminal command and type
Code:
chmod 0644 /vendor/etc/fstab.qcom
4.) Flash the magisk.zip to install Magisk
During the installation process Magisk will remove dm-verity
5.) Reboot and update Magisk Manager + Magisk to v20.3

OOS 10.3.1 GM21AA Global Full Zip!

I'm not responsible for anything you do to your device. This is the full zip from Oxygen Updater. Enjoy.
OOS 10.3.1 Global GM21AA
MEGA (a bit slow)
https://mega.nz/#!8R8hnTJB!iT15i_HFJSFGtGf1-nc56lOFhStIPjm7kP6D2zacoYs
Google Drive
https://drive.google.com/file/d/1LoElSYQ9MtNUHeC5TSLGfvZsSD8bSDBd/view?usp=drivesdk
AFH
https://www.androidfilehost.com/?w=files&flid=305551

JDROIDS said:
I'm not responsible for anything you do to your device. This is the full zip from Oxygen Updater. Enjoy.
OOS 10.3.1 Global GM21AA
https://mega.nz/#!8R8hnTJB!iT15i_HFJSFGtGf1-nc56lOFhStIPjm7kP6D2zacoYs
Click to expand...
Click to collapse
Anyone who wants to download and add to their thread feel free.

JDROIDS said:
Anyone who wants to download and add to their thread feel free.
Click to expand...
Click to collapse
I know there is some confusion from OnePlus as to which oos version is for which device but 10.3.1 is indeed for 21AA global.

avid_droid said:
10.0.4 also works as it is for EU but it's basically the same thing without all the India features
---------- Post added at 08:03 PM ---------- Previous post was at 07:56 PM ----------
@JDROIDS have you been experiencing odd battery drain in this release? I've been on it for over a day now and it's horrible battery is killing me
Click to expand...
Click to collapse
I have only been on 10.3.1 for a few hours so I can't accurately comment on the battery yet.

If IAM on beta 9 rooted and twrp. can I flash this with twrp ?

JDROIDS said:
I'm not responsible for anything you do to your device. This is the full zip from Oxygen Updater. Enjoy.
OOS 10.3.1 Global GM21AA
https://mega.nz/#!8R8hnTJB!iT15i_HFJSFGtGf1-nc56lOFhStIPjm7kP6D2zacoYs
Click to expand...
Click to collapse
do you have the rom on another server? the mega is bad .. I can't download it by the mega

Mega sucks...!!!
Can you upload it to another file server???

I have been running this version for several days, battery lasts about 1-2 days.

Do you use the stock or custom kernel ?

I have had a slight improvement with the radio performance after updating to 10.3.1 GM21AA. In my bathroom, the device used to drop to WiFi Calling but now can stay on cellular. The call quality in my bathroom on cellular now is decent. It shows 3 bars where it once was 1, but that one bar was garbled when on cellular on 10.3.0.

spinoza23 said:
Mega sucks...!!!
Can you upload it to another file server???
Click to expand...
Click to collapse
Try the second link from Google drive I added. See if that works.

parydia said:
Do you use the stock or custom kernel ?
Click to expand...
Click to collapse
All original, without root or other modification.

I also added an AFH link so the download should be quick there for those of you having issues with Oxygen Updater.

Many thanks for this. Might you have the boot image for this 10.3.1 ?
I rushed myself and rebooted without first reinstalling Magisk 20.3. My phone boots with the new 10.3.1 and works, but I lost root. Magisk Manager 7.5.1 still works, but won't let me install the 20.3.
Many thanks in advance.
I'm OnePlus 7 pro, GM 1917, and now 10.3.1, without TWRP... Oh, and feeling stupid! I absolutely knew to not reboot at that point, and lost track of where I was in the process.

I can't believe how I was Over-thinking this!
I'm good to go. It worked so easily. Thanks for the hand-up.

Thanks

Beta 9 , magisk, and twrp.flashed 10.3.1 ,reboot recovery,flashed twrp installer,reboot to recovery , twrp doesn't see internal storage.reboot system .play store would keep closing , uninstalled magisk app.reboot all is good except twrp....I know I did this wrong.now what to do to get twrp corrected to see storage.? Any help much appreciated thanks....... figured it out thanks anyway

so you guys have flashed to 10.3.1 and then reinstalled twrp and magisk 20.3 without issues? mine keeps getting stuck on the boot logo after i flash magisk. Not sure what i might be doing wrong. flash the 10.3.1 zip, reboot, fastboot twrp, then boot into twrp and install magisk. I've been able to install EX kernel as well and it'll boot as long as I don't try and install magisk. But really need root back! Help!

pvtjoker42 said:
so you guys have flashed to 10.3.1 and then reinstalled twrp and magisk 20.3 without issues? mine keeps getting stuck on the boot logo after i flash magisk. Not sure what i might be doing wrong. flash the 10.3.1 zip, reboot, fastboot twrp, then boot into twrp and install magisk. I've been able to install EX kernel as well and it'll boot as long as I don't try and install magisk. But really need root back! Help!
Click to expand...
Click to collapse
Everyone should flash new system updates via Magisk. This works flawlessly. If this is new to you, search xda. It's written over and over daily because people are still flashing updates via TWRP and having issues. Use Magisk!

JDROIDS said:
Everyone should flash new system updates via Magisk. This works flawlessly. If this is new to you, search xda. It's written over and over daily because people are still flashing updates via TWRP and having issues. Use Magisk!
Click to expand...
Click to collapse
How do you flash updates via magisk? Just download the update locally then patch it? Doesn't that erase all data on the phone?
Sent from my GM1917 using Tapatalk

Rooting redmi 9 eea version with magisk without twrp

I've been trying to root my redmi9 for a couple of days now, with no luck. Downloaded the relevant firmware for my version to my pc, extracted it and copied the boot img over to my phone and copied over magisk manager APK too. On my phone I opened and installed magisk manager and proceeded to the install process then selected patch file and clicked install. Unfortunately each time that I do this I get the same outcome the message reads-
-Device platform: arm64-v8a
-Copying images to cache
! Process error
! Installation failed
I've uninstalled magisk and reinstalled, with the same outcome. Then I've downloaded my phone's firmware directly to my phone and tried to patch the boot IMG like that, but exactly the same outcome. Re-checked that I have the correct firmware for my version and it is, so I can't really understand what is going wrong and why I can't select a patch to send back to pc? Points of note, I haven't got my sim inserted and wondered if this could be a problem as I can't select the other two debugging settings on my phone without my sim inserted ( install via USB and usb debugging (security settings) options) but USB debugging is selected to on. My miui version is Miui global 11.0.7 stable 11.0.7.0(QJCEUXM)
If any body has an already patched IMG file that I can use, or can help me achieve this myself it would be very much appreciated.

Philtyj said:
I've been trying to root my redmi9 for a couple of days now, with no luck. Downloaded the relevant firmware for my version to my pc, extracted it and copied the boot img over to my phone and copied over magisk manager APK too. On my phone I opened and installed magisk manager and proceeded to the install process then selected patch file and clicked install. Unfortunately each time that I do this I get the same outcome the message reads-
-Device platform: arm64-v8a
-Copying images to cache
! Process error
! Installation failed
I've uninstalled magisk and reinstalled, with the same outcome. Then I've downloaded my phone's firmware directly to my phone and tried to patch the boot IMG like that, but exactly the same outcome. Re-checked that I have the correct firmware for my version and it is, so I can't really understand what is going wrong and why I can't select a patch to send back to pc? Points of note, I haven't got my sim inserted and wondered if this could be a problem as I can't select the other two debugging settings on my phone without my sim inserted ( install via USB and usb debugging (security settings) options) but USB debugging is selected to on. My miui version is Miui global 11.0.7 stable 11.0.7.0(QJCEUXM)
If any body has an already patched IMG file that I can use, or can help me achieve this myself it would be very much appreciated.
Click to expand...
Click to collapse
New version of magisk has this error.if you have another phone then you use it to patch your boot.img..it will work...I am also doing this...for a unknown error magisk manager cannot patch boot.img in redmi 9....then I try to patch my boot.img on another phone and it can patch....follow the link.....
https://forum.xda-developers.com/showpost.php?p=83419803&postcount=1

Hi, thanks for the reply. I'm not fully understanding what you're saying. How do I do this using another phone? Do I download magisk onto my other phone, then copy the boot IMG to the phone and patch the image? Then send the patch back to my pc to then flash the patch onto my redmi 9 via fastboot?
In your link, are these steps to follow to flash my redmi9 after creating the patch on my other phone?
Sorry for all of the questions, I'm new to this, it's my first attempt to root a phone and it seems that I've picked the hardest one to unlock and root!!

Philtyj said:
Hi, thanks for the reply. I'm not fully understanding what you're saying. How do I do this using another phone? Do I download magisk onto my other phone, then copy the boot IMG to the phone and patch the image? Then send the patch back to my pc to then flash the patch onto my redmi 9 via fastboot?
In your link, are these steps to follow to flash my redmi9 after creating the patch on my other phone?
Sorry for all of the questions, I'm new to this, it's my first attempt to root a phone and it seems that I've picked the hardest one to unlock and root!!
Click to expand...
Click to collapse
Yes...you can use any device to patch your boot.img file...there is no problem to do so....you can patch any boot.img in any device.....this new version of magisk manager has some issue with our redmi 9 ..so use another device and patch it..then flash patched boot.img via fastboot and follow the tutorial which I give you....

Shas45558 said:
Yes...you can use any device to patch your boot.img file...there is no problem to do so....you can patch any boot.img in any device.....this new version of magisk manager has some issue with our redmi 9 ..so use another device and patch it..then flash patched boot.img via fastboot and follow the tutorial which I give you....
Click to expand...
Click to collapse
Hi there, thanks for the help, I've finally rooted my redmi9! One more thing that I wanted to ask. It's about the ROM. I've tried to find information on Google, but nothing comes up that replies to my question. After rooting with magisk, do I need to install a ROM or is my original Xiaomi ROM still ok and working? I'm not interested in installing a custom ROM, root was simply to gain access for installing a program/app. So I'm hoping my original rom is in tact and I'm good to go.

Philtyj said:
Hi there, thanks for the help, I've finally rooted my redmi9! One more thing that I wanted to ask. It's about the ROM. I've tried to find information on Google, but nothing comes up that replies to my question. After rooting with magisk, do I need to install a ROM or is my original Xiaomi ROM still ok and working? I'm not interested in installing a custom ROM, root was simply to gain access for installing a program/app. So I'm hoping my original rom is in tact and I'm good to go.
Click to expand...
Click to collapse
You do not need to install any custom ROM your stock ROM is ok. But you can try the gsi ROM...
Follow the link you can install GSI without any problem...
https://forum.xda-developers.com/showpost.php?p=83533901&postcount=1

EEA version have call recorder or not? i try global version not have call recorder

adiyanto said:
EEA version have call recorder or not? i try global version not have call recorder
Click to expand...
Click to collapse
Hi Adiyanto,
Hope You're Doing Great..
Yes, You Are Right,
I Have Global Version It Doesn't Have Call Recorder And I Have Also Tried And Flashed EEA Version ROM And It Also Doesn't Have Call Recorder. So I Flashed The Redmi 9 Prime ROM Since It Has Call Recorder And Working Perfectly.
Note That, You Need To Unlock The Bootloader For This Activity. Or You Can Unlock Your Device Bootloader Then Root The Device Then Install Any Call Recorder In Any ROM That Works Perfectly.
Hope This Will Help You ...
Thanks,
MUHAMMAD Asif Qasim

aasiaasi said:
Hi Adiyanto,
Hope You're Doing Great..
Yes, You Are Right,
I Have Global Version It Doesn't Have Call Recorder And I Have Also Tried And Flashed EEA Version ROM And It Also Doesn't Have Call Recorder. So I Flashed The Redmi 9 Prime ROM Since It Has Call Recorder And Working Perfectly.
Note That, You Need To Unlock The Bootloader For This Activity. Or You Can Unlock Your Device Bootloader Then Root The Device Then Install Any Call Recorder In Any ROM That Works Perfectly.
Hope This Will Help You ...
Thanks,
MUHAMMAD Asif Qasim
Click to expand...
Click to collapse
maybe u can try Indonesia version. this version have call recorder. but i need for recorder my whatsapp phone.... ill try Any Call Recorder

aasiaasi said:
Hi Adiyanto,
Hope You're Doing Great..
Yes, You Are Right,
I Have Global Version It Doesn't Have Call Recorder And I Have Also Tried And Flashed EEA Version ROM And It Also Doesn't Have Call Recorder. So I Flashed The Redmi 9 Prime ROM Since It Has Call Recorder And Working Perfectly.
Note That, You Need To Unlock The Bootloader For This Activity. Or You Can Unlock Your Device Bootloader Then Root The Device Then Install Any Call Recorder In Any ROM That Works Perfectly.
Hope This Will Help You ...
Thanks,
MUHAMMAD Asif Qasim
Click to expand...
Click to collapse
Hi Qasim,
Would you please share the complete process of rooting and new img file restoration as I am new to this redmi9 am using this device in pakistan. Looking forward for your kind response
Regards nauman

Philtyj said:
Hi there, thanks for the help, I've finally rooted my redmi9! One more thing that I wanted to ask. It's about the ROM. I've tried to find information on Google, but nothing comes up that replies to my question. After rooting with magisk, do I need to install a ROM or is my original Xiaomi ROM still ok and working? I'm not interested in installing a custom ROM, root was simply to gain access for installing a program/app. So I'm hoping my original rom is in tact and I'm good to go.
Click to expand...
Click to collapse
Can you share your magisk_patched.img ? Cause I tried to patch the image on another device, but the created image boot-loops only
Tried patching the image on the redmi directly, but the resulting patched image is only 10MB and obviously boot-loops.
Thanks.

naumanakram said:
Hi Qasim,
Would you please share the complete process of rooting and new img file restoration as I am new to this redmi9 am using this device in pakistan. Looking forward for your kind response
Regards nauman
Click to expand...
Click to collapse
Dear Nauman,
Greetings !!!
For Rooting Your Device Please Refer To This LINK. Or If You Just Want Call Recording Feature Then Flash Redmi 9 Prime ROM To Your Mobile.
Thanks,
MUHAMMAD Asif Qasim

Cannot install Magisk

Hello,
I have a One Plus 5 with a Custom AOSP Rom 11.0 and TWRP 3.4.0.1 and I'm trying to install Magisk like it's explained here.
But whatever I try - it does not work.
When I flash it via TWRP it says everything went well, but in the end my Magisk Manager does not have the "green ticks" and my apps say I have no root access.
I also tried this with my current ROM but there is an error. I'll attach all logs and files in case it's helpful.
Thank you very much.
Edit:
I was now able to create a flashed boot.img file, but when I flash that it always boots into the bootloader and cannot boot my phone anymore normally anymore.

Quite simple... Magisk v20.4 isn't compatible with Android 11. Currently you need to switch to the beta update channel if you want root on A11.

Didgeridoohan said:
Quite simple... Magisk v20.4 isn't compatible with Android 11. Currently you need to switch to the beta update channel if you want root on A11.
Click to expand...
Click to collapse
Awesome thank you... A little bit embarissing since I spend so much time before but thank you very much

General [IMG] Boot + magisk patched boot images

Hi, I have decided to gather boot images and magisk patched images to one thread for now. I will try to edit this thread to be up-to-date. You can let me know what could you want next or if anything is wrong etc.
Stock boot.img files (direct links): ​
EU NE2213_11_A.12​
Stock boot.img - link
EU NE2213_11_A.10​
Stock boot.img - link
​Magisk patched boot.img are here a file that can be downloaded (I am using magisk canary usually, but in Magisk, you can change the channel from the canary to stable etc.) - names as the versions come. ​
Below this there are those magisk patched files which you just flash (or boot and then flash directly from the Magisk app) via fastboot ​

Reserved

Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?

HessNL said:
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
Click to expand...
Click to collapse
Apparently not. I have patched that stock boot via magisk, then via fastboot boot <patchedimage.img> booted (and also tested if it actually boots) and when it booted, via magisk app I did "Direct install (recommended)", rebooted and done.

Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it

Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.

HessNL said:
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Click to expand...
Click to collapse
Yes, because this is probably and currently the most secure option to root it as we haven't got twrp available yet.
BuBbLeFIZzY said:
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
Click to expand...
Click to collapse
That's not that you have it early. The phone itself is early in spite of rooting and doing things like rooting, custom recoveries, ROMs etc. I currently can't find boot img for your model, but once I do, I will post it here for you with patched one.

Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future

fozzy056 said:
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
Click to expand...
Click to collapse
You're really welcome, I wanted to unite those currently quite hard rooting stuff!
And yes, I can't wait to see twrp too!

Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.

GeekMcLeod said:
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
Click to expand...
Click to collapse
Not yet unfortunately. Or I don't know about it yet. :/

kouzelnik3 said:
Not yet unfortunately. Or I don't know about it yet. :/
Click to expand...
Click to collapse
Yeah.. I googled a lot last night once I got my phone trying to find it to root it. I need me that extra bit of customization.
Is there a way I can get it from my phone?

what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this

Johnstan725 said:
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Click to expand...
Click to collapse
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone

Johnstan725 said:
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Click to expand...
Click to collapse
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.

g96818 said:
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
Click to expand...
Click to collapse
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?

Johnstan725 said:
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Click to expand...
Click to collapse
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.

g96818 said:
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
Click to expand...
Click to collapse
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?

Johnstan725 said:
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Click to expand...
Click to collapse
Hmmm. Well you should be fine if you patched the boot and let magisk do the install. I only suggested wiping since you said you flashed the img from the bootloader.
You might run into the same problem I have with the 9RT. I too upgraded from color to oos and couldn’t update at all, even though I rooted from the magisk app. I had to wait for someone to make a fastboot rom. I had no problems updating color following my method, but not oos after switching. Hopefully that’s not the case for you.