Does anyone know where i can find the newest security December 1, 2019 update for the g7 play? i've searched online and cannot find it anywhere. My phone keeps reminding me of a failed update so i went looking for the new one. Do i re-flash the phone to stock and update it that way before re-rooting it or wait until someone post the newest update in the mirrors repository? What do you guys suggest?
dominoeflux said:
Does anyone know where i can find the newest security December 1, 2019 update for the g7 play? i've searched online and cannot find it anywhere. My phone keeps reminding me of a failed update so i went looking for the new one. Do i re-flash the phone to stock and update it that way before re-rooting it or wait until someone post the newest update in the mirrors repository? What do you guys suggest?
Click to expand...
Click to collapse
https://support.motorola.com/us/en/Solution/MS147329
Oct 2019 seems to be the latest:
https://www.theandroidsoul.com/spri...lay-moto-g6-play-with-october-security-patch/
Normally you go back to stock, patch and then re-root.
What model do you have?
I cannot get root on my XT1952-4.
mtmtumbo said:
https://support.motorola.com/us/en/Solution/MS147329
Normally you go back to stock, patch and then re-root.
What model do you have?
I cannot get root on my XT1952-4.
Click to expand...
Click to collapse
I have the same model with boost mobile...do you need help rooting it? I just followed the instructions for the boot.img magisk patch but when you patch it make sure you select beta in magisk and in advanced settings make sure all are checked especially recovery mode before you patch and lastly when you reboot, reboot to recovery every time or the root will not stick...that's something no one mentioned when i was trying to root mine. I had to research the problem of why the root wasn't sticking. When you reboot to recovery it will stay on a blank screen and then vibrate, that's normal. It does that before it boots up. Once it's booted, check to make sure you have root by opening the magisk app, you should see both green check marks and thanks for you help with how to update.
dominoeflux said:
I have the same model with boost mobile...do you need help rooting it? I just followed the instructions for the boot.img magisk patch but when you patch it make sure you select beta in magisk and in advanced settings make sure all are checked especially recovery mode before you patch and lastly when you reboot, reboot to recovery every time or the root will not stick...that's something no one mentioned when i was trying to root mine. I had to research the problem of why the root wasn't sticking. When you reboot to recovery it will stay on a blank screen and then vibrate, that's normal. It does that before it boots up. Once it's booted, check to make sure you have root by opening the magisk app, you should see both green check marks and thanks for you help with how to update.
Click to expand...
Click to collapse
thanks, I followed the instructions as well to patch boot.img and use fastboot with magisk_patched.img, but when I rebooted, I only got the xxxxxx-xxxxxx-xxxxxxx-xxxxxxx-xxxxxx code and then no vibration and nothing else - seems stuck and just looping at this point
what do you mean select beta in magisk?
what version of apk did you create the patched img from? 7.4.0?
and yes, i made sure i checked all the advanced options (including recovery) before creating the patched img file
mtmtumbo said:
thanks, I followed the instructions as well to patch boot.img and use fastboot with magisk_patched.img, but when I rebooted, I only got the xxxxxx-xxxxxx-xxxxxxx-xxxxxxx-xxxxxx code and then no vibration and nothing else - seems stuck and just looping at this point
what do you mean select beta in magisk?
what version of apk did you create the patched img from? 7.4.0?
and yes, i made sure i checked all the advanced options (including recovery) before creating the patched img file
Click to expand...
Click to collapse
when you go in the magisk manager, select the three lines at the top left and go to settings/update channel and select beta....if you don't you will loop. i used the latest magisk version which is 7.4.0 so yes you're using the correct one. your suppose to see those codes it's normal, if the phone does not vibrate, then that means that it didn't work.
dominoeflux said:
when you go in the magisk manager, select the three lines at the top left and go to settings/update channel and select beta....if you don't you will loop. i used the latest magisk version which is 7.4.0 so yes you're using the correct one. your suppose to see those codes it's normal, if the phone does not vibrate, then that means that it didn't work.
Click to expand...
Click to collapse
Thanks, I enabled beta in magisk and tried it again and it still did not vibrate after showing the codes - just rebooting in a loop as before.
What size is your magisk_patched.img and boot.img files?
Here are mine:
33,554,432 boot.img
18,103,592 magisk_patched.img
You can see after the patching that the size of the boot image drops almost in half - is that normal?
I transfer these files using adb push and pull as I heard MTP transfers could corrupt the files.
Anyhow, since we're on the same build, can you post up your boot and patched img somewhere so I can try them?
mtmtumbo said:
Thanks, I enabled beta in magisk and tried it again and it still did not vibrate after showing the codes - just rebooting in a loop as before.
What size is your magisk_patched.img and boot.img files?
Here are mine:
33,554,432 boot.img
18,103,592 magisk_patched.img
You can see after the patching that the size of the boot image drops almost in half - is that normal?
I transfer these files using adb push and pull as I heard MTP transfers could corrupt the files.
Anyhow, since we're on the same build, can you post up your boot and patched img somewhere so I can try them?
Click to expand...
Click to collapse
Did you repatch the stock boot.img before flashing again? The magisk patch is different if not on beta and the magisk recovery is not selected, that's why it's probably still not working.
also make sure that you're patching the correct boot.img from your stock firmware that you're on, it creates problems if you're not. I can't upload my .imgs for some reason and you're correct it didn't vibrate the first time i was successful, but after i have to reboot the phone i would reboot to recovery so when the phone boots the root sticks, that's when it will vibrate.
@mtmtumbo I apologize I haven't been on here in a couple of days, any update on rooting your g7 play?
dominoeflux said:
Did you repatch the stock boot.img before flashing again? The magisk patch is different if not on beta and the magisk recovery is not selected, that's why it's probably still not working.
also make sure that you're patching the correct boot.img from your stock firmware that you're on, it creates problems if you're not. I can't upload my .imgs for some reason and you're correct it didn't vibrate the first time i was successful, but after i have to reboot the phone i would reboot to recovery so when the phone boots the root sticks, that's when it will vibrate.
Click to expand...
Click to collapse
happy new year all
yes i re-patched the stock boot.img before flashing, magisk was on beta and yes the third option in advanced for recovery was selected before i patched the boot.img
after i saw the codes and it was looping, i rebooted the phone to recovery but no difference
i'm also having a problem flashing twrp without just using fastboot boot twrp.img - flashing it with fastboot flash doesn't work (using dtbo.img first to avoid the black screen)
btw you can use mega.nz to upload your img's - give it a shot and post the URL here
if it matters, this is the ROM I'm using:
XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
mtmtumbo said:
happy new year all
yes i re-patched the stock boot.img before flashing, magisk was on beta and yes the third option in advanced for recovery was selected before i patched the boot.img
after i saw the codes and it was looping, i rebooted the phone to recovery but no difference
i'm also having a problem flashing twrp without just using fastboot boot twrp.img - flashing it with fastboot flash doesn't work (using dtbo.img first to avoid the black screen)
btw you can use mega.nz to upload your img's - give it a shot and post the URL here
if it matters, this is the ROM I'm using:
XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
Happy New Year man.....i believe i figured out why you're still boot looping, did you reboot back into the bootloader after you flashed the patched.img?
edit: when your doing twrp, you have to boot into it before installing it to the ramdisk. there's a how to in this forum here: https://forum.xda-developers.com/g7-play/how-to/how-to-successfully-install-twrp-g7-play-t3979701
the GSI's don't work for me so i'm waiting for a legit custom build before installing twrp again
Update 134-7
XT1952-2
ATTMX
https://mirrors.lolinet.com/firmwar...USMXLA_regulatory-XT1952-2-MEXICO_CFC.xml.zip
OpenMX
https://mirrors.lolinet.com/firmwar...EFAULT_regulatory-XT1952-2-MEXICO_CFC.xml.zip
RETAR
https://mirrors.lolinet.com/firmwar...ULT_regulatory-XT1952-2-ARGENTINA_CFC.xml.zip
Related
So i was running Android 10 Nov update rooted WITHOUT TWRP
And i wanted to update to Dec update
So i DLed DEC update factory image took out the -w booted my phone into the bootloader flash-all
It does its thing phone boots up obvi now i dont have root.
I put the bootloader.img onto my phone go into Magisk manager and modify the bootloader then bring it back to the computer.
Boot the phone into bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
phone gets stuck in the G logo with the loading bar
any hints????
after doing some researched i tried it again but this time flashing the patched boot.img to both a and b slots. Still same result
krolla03 said:
So i was running Android 10 Nov update rooted WITHOUT TWRP
And i wanted to update to Dec update
So i DLed DEC update factory image took out the -w booted my phone into the bootloader flash-all
It does its thing phone boots up obvi now i dont have root.
I put the bootloader.img onto my phone go into Magisk manager and modify the bootloader then bring it back to the computer.
Boot the phone into bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
phone gets stuck in the G logo with the loading bar
any hints????
Click to expand...
Click to collapse
krolla03 said:
after doing some researched i tried it again but this time flashing the patched boot.img to both a and b slots. Still same result
Click to expand...
Click to collapse
You stated that you patched the bootloader.img, is that correct?? You need to patch the boot.img, or, was that just a typo on your part?
Did you disable all your magisk modules before you fastbooted the factory image?? If not, then it's very likely that one, or maybe more modules, isn't compatible with the December update. I'll wait for your reply before trying to help solve the problem.
I previously dealt with similar symptoms. You can read about it here -- https://forum.xda-developers.com/showpost.php?p=81102855&postcount=33
Badger50 said:
You stated that you patched the bootloader.img, is that correct?? You need to patch the boot.img, or, was that just a typo on your part?
Did you disable all your magisk modules before you fastbooted the factory image?? If not, then it's very likely that one, or maybe more modules, isn't compatible with the December update. I'll wait for your reply before trying to help solve the problem.
Click to expand...
Click to collapse
OK so stupid me yes i was patching and flashing the bootloader.img not the boot.img.
I just tried flashing the indeed patched boot.img and now im getting the same issue as rustnails. Where it gets stuck at the G logo for a few secs and reboots.
I did not uninstall or disable any of the magisk modulus
how do i do that now that i dont have root?
krolla03 said:
OK so stupid me yes i was patching and flashing the bootloader.img not the boot.img.
I just tried flashing the indeed patched boot.img and now im getting the same issue as rustnails. Where it gets stuck at the G logo for a few secs and reboots.
I did not uninstall or disable any of the magisk modulus
how do i do that now that i dont have root?
Click to expand...
Click to collapse
Fastboot into twrp. Go to advanced, select file manager, go to /data/adb/modules then delete each one of them. Reboot, then go back and fastboot your patched boot.img to regain root :good:
Badger50 said:
Fastboot into twrp. Go to advanced, select file manager, go to /data/adb/modules then delete each one of them. Reboot, then go back and fastboot your patched boot.img to regain root :good:
Click to expand...
Click to collapse
Ok. Before i try that let me just ask this.
Can i just temp boot TWRP to do that
I dont want to install TWRP permanently because ive had mostly trouble with TWRP in the last few android versions.
krolla03 said:
Ok. Before i try that let me just ask this.
Can i just temp boot TWRP to do that
I dont want to install TWRP permanently because ive had mostly trouble with TWRP in the last few android versions.
Click to expand...
Click to collapse
Yep. It'll just be temporary :good:
Badger50 said:
Yep. It'll just be temporary :good:
Click to expand...
Click to collapse
Thanks man. I got it all working again!!!
Hi badger, @Badger50 (Mod Edit: added mention tag)
i have an issue with rooting my device
when I write fastboot flash boot magisk_patched.img I get a message says < waiting for device >
can you please help me to find a solution to my problem?
dark_heroo said:
Hi badger, @Badger50 (Mod Edit: added mention tag)
i have an issue with rooting my device
when I write fastboot flash boot magisk_patched.img I get a message says < waiting for device >
can you please help me to find a solution to my problem?
Click to expand...
Click to collapse
Not sure what your starting point is but:
After installing you fastboot factory image
you can either temporarily or permanently install TWRP (temp TWRP= fastboot twrp.img, install magisk, reboot OR perm TWRP = fastboot twrp.img, install TWRP.zip from witin TWRP)
then you just flash/install magisk in TWRP
In my sig is a link to a detailed step by step guide for all this.
Good luck!
Hey guys like the title says this months update is ready. I'm wondering if I can do the restore stock boot img thru magisk even tho I'm using MVK kernel?? Will it send me into boot loop??
** No bootloop everything worked out just fine **
Just a note tho, if you've rooted by patching the boot img you won't have a backup in magisk. You'll have to take the stock boot img from your current build and compress it with this file name stock_boot_0.img in a .gz compression then copy that to the /data folder in root storage. Then go into /sbin folder and go into .magisk folder, tap on config and change the SHA value to 0 and save it.
After that's done you can restore your stock boot thru magisk, take the OTA update, don't reboot yet, install magisk to the inactive slot, once done you can reboot and your good to go and still rooted
Perfect
Grabbed the full factory image. Removed the -w in flash-all. Flashed, patched boot.img. Works great!
Anyone having trouble with root on Jan update getting lost after a rebooot?
Tried 3 times now and same result each time.
Load magisk patched boot image for January via fastboot
Root fully operational
Install a magisk module
Required reboot after installing above module
Phone is no longer rooted
Can anyone confirm or deny if they get the same.
adm1jtg said:
Anyone having trouble with root on Jan update getting lost after a rebooot?
Tried 3 times now and same result each time.
Load magisk patched boot image for January via fastboot
Root fully operational
Install a magisk module
Required reboot after installing above module
Phone is no longer rooted
Can anyone confirm or deny if they get the same.
Click to expand...
Click to collapse
No..root still working here after reboot.
adm1jtg said:
Anyone having trouble with root on Jan update getting lost after a rebooot?
Tried 3 times now and same result each time.
Load magisk patched boot image for January via fastboot
Root fully operational
Install a magisk module
Required reboot after installing above module
Phone is no longer rooted
Can anyone confirm or deny if they get the same.
Click to expand...
Click to collapse
Working just fine here
adm1jtg said:
Anyone having trouble with root on Jan update getting lost after a rebooot?
Tried 3 times now and same result each time.
Load magisk patched boot image for January via fastboot
Root fully operational
Install a magisk module
Required reboot after installing above module
Phone is no longer rooted
Can anyone confirm or deny if they get the same.
Click to expand...
Click to collapse
UPDATE: thanks to the feedback i got it working... Turns out was a bad magisk module, updated and all is well. Thanks
thatsupnow said:
Hey guys like the title says this months update is ready. I'm wondering if I can do the restore stock boot img thru magisk even tho I'm using MVK kernel?? Will it send me into boot loop??
** No bootloop everything worked out just fine **
Just a note tho, if you've rooted by patching the boot img you won't have a backup in magisk. You'll have to take the stock boot img from your current build and compress it with this file name stock_boot_0.img in a .gz compression then copy that to the /data folder in root storage. Then go into /sbin folder and go into .magisk folder, tap on config and change the SHA value to 0 and save it.
After that's done you can restore your stock boot thru magisk, take the OTA update, don't reboot yet, install magisk to the inactive slot, once done you can reboot and your good to go and still rooted
Click to expand...
Click to collapse
I've done all steps up until the OTA part. It keeps giving me "Couldn't update, Installation problem" after numerous tries. Both here and the Magisk guide say DO NOT reboot. Am I screwed if I reboot or just have to repeat the process?
Thanks
Basically I was on November update with magisk and a custom kernel installed I couldn't take otas so how I fixed it was @mbk17 I had to flash the matching boot IMG in fastboot from the update I was on to get installation problem error to go away so I could take an ota.
Download matching factory image from goggles website
Then unzip the file
Then also unzip the image bonito zip
The boot IMG is inside second zip
Flash boot IMG in fastboot issue fixed :victory:
thatsupnow said:
Just a note tho, if you've rooted by patching the boot img you won't have a backup in magisk. You'll have to take the stock boot img from your current build and compress it with this file name stock_boot_0.img in a .gz compression then copy that to the /data folder in root storage. Then go into /sbin folder and go into .magisk folder, tap on config and change the SHA value to 0 and save it.
After that's done you can restore your stock boot thru magisk, take the OTA update, don't reboot yet, install magisk to the inactive slot, once done you can reboot and your good to go and still rooted
Click to expand...
Click to collapse
Actually, there is an easier way. Get the stock boot.img for the current build, put it on your phone, and patch that boot.img through Magisk. It will backup that original boot.img before it patches it. Don't need to do anything with the patched boot.img, but when you restore images, it will take the backup you just created.
---------- Post added at 10:03 PM ---------- Previous post was at 09:59 PM ----------
mbk17 said:
I've done all steps up until the OTA part. It keeps giving me "Couldn't update, Installation problem" after numerous tries. Both here and the Magisk guide say DO NOT reboot. Am I screwed if I reboot or just have to repeat the process?
Thanks
Click to expand...
Click to collapse
I know it's too late but in the future if you get this, you're still rooted until you reboot, so just reinstall magisk through direct install. Now when you reboot, you're still rooted.
That said, if you can't update through the ota, you're going to have to update through ADB, and you'll lose root anyway.
Bramton1 said:
Actually, there is an easier way. Get the stock boot.img for the current build, put it on your phone, and patch that boot.img through Magisk. It will backup that original boot.img before it patches it. Don't need to do anything with the patched boot.img, but when you restore images, it will take the backup you just created.
Tried that and didn't work. Kept saying backup didn't exist, hence why I posted this steps
Click to expand...
Click to collapse
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://file5.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
My computer is down so:
THANKS A MILLION!!!!!!!!!!!!!
YOU'RE SO AWESOME!!!!!!!!!!!!
Orion9k0 said:
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
Click to expand...
Click to collapse
If you are not using TWRP, follow this guide: https://forum.xda-developers.com/t/guide-how-to-root-oneplus-7t-without-twrp.3979307/
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
posiblyLopsided said:
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
Click to expand...
Click to collapse
Did you switch back the default OTA active slot after flashing both?
nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
i did not flash i only booted. i have tried flashing in the past with android 11 and had the same result of eternal loading. but that was a while ago and it is possible i did smth wrong.
nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
Did you remove or at the very least disable all Magisk modules before OTA updating?
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
kurskoo40 said:
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
Click to expand...
Click to collapse
the issue is that when i do fastboot boot magisk.img it gets stuck on the boot animation. i have to hold the power button and volume up to force it to power off then i can boot it back to the normal version
posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
thexile said:
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
Click to expand...
Click to collapse
how would i do that? can i use my phone file manager or do i need to use adb?
posiblyLopsided said:
how would i do that? can i use my phone file manager or do i need to use adb?
Click to expand...
Click to collapse
Since you have no root access currently, you have to do so via adb in recovery mode with adb enabled.
thexile said:
Since you no root access currently, you have to do so via adb in recovery mode with adb enabled.
Click to expand...
Click to collapse
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
posiblyLopsided said:
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
Click to expand...
Click to collapse
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
yeah looks like i learned the hard way too. also i didnt realise they released twrp for oneplus 7t. id heard that it just didnt work with android 11 but maybe im wrong. ill try it out anyways. if the twrp works that would be amazing. also thanks for all the help.
thexile said:
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://srv-store6.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Click to expand...
Click to collapse
Thanks. This worked fine. I just used local install from update, backed out without rebooting, installed magisk app and did the first reboot into bootloader, then wrote magisk modded boot image to boot a/b. It was a dirty update over the prior version.
thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
i have successfully rooted after useing twrp to remove those magisk modules.
Hi, I really need EU version of boot.img, could you please help me?
I've even looked for the full 11.0.2.1.HD65BA but with no luck.
So basically can't find anywhere both the boot.img and the full stock rom, any advice?
Thank you
Hello all,
yesterday I've updated to latest OOS LE2123_11.C.44_1440_202201182111 (Android 12). I was previously on root, so I've updated the phone via full 4GB OTA through the system updater.
Everything was fine until I've tried to root by following these steps:
ATTENTION: if you're a Googler and willing to root the OPO 9 Pro, don't use the steps below, because they lead to a soft-bricked phone! (at least, for me)
Download the full OTA via Oxygen Updater
Extract the boot.img (192MB) via Payload Dumper (and I was confused, because the previous Android 11 boot.img was exactly the half in size)
Let the phone update itself
Throw the boot.img inside Magisk and create a patched boot.img
Flash the pathed boot image via fastboot with "fastboot flash boot Magisk_patched_blabla.img"
The phone was refusing to boot, as it was automatically booting in Fastboot mode.
So I've reflashed the patched IMG file, and the phone switched to Qualcomm Crashdump mode
Then, don't ask me how, I've managed to get it back to fastboot mode. Searched XDA for a clean and tested boot.img, understood that the boot contains 2 slots A/B, set the active boot slot to A, flashed the boot.img downloaded before, and the phone turned back to life.
So...what am I doing wrong? Maybe everything?
What are the correct steps to root the phone?
Thank you in advance
you don't have to flash the magisk_patched.img but instead boot it with : "fastboot boot magisk_patched.img"
Then you can install magisk by it's manager and reboot the phone.
Here is everything explained: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-0-0-0.4252373/
OS Update with install to inactive slot in magisk works too.
nicoilboss said:
you don't have to flash the magisk_patched.img but instead boot it with : "fastboot boot magisk_patched.img"
Then you can install magisk by it's manager and reboot the phone.
Here is everything explained: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-0-0-0.4252373/
Click to expand...
Click to collapse
I follow those steps I can get the boot and install alpha apk after it's install completed to reboot, phone gets bricked and stuck in fastboot.
Wait for the new Magisk, it's going to support Android 12.
https://twitter.com/topjohnwu/with_replies
djsubterrain said:
Wait for the new Magisk, it's going to support Android 12.
https://twitter.com/topjohnwu/with_replies
Click to expand...
Click to collapse
Missed this one...
How come some people is actually running on the rooted OOS C.44 EU? Are they using a particular version of a patched boot.img that's floating underground?
l_mike said:
OS Update with install to inactive slot in magisk works too.
Click to expand...
Click to collapse
I've clickbaited like a moron on the UPDATE/REBOOT button after OTA, and I've missed the opportunity to do it *before* rebooting the phone... then followed the steps I've posted and knocked out of the door...
xmff00 said:
Missed this one...
How come some people is actually running on the rooted OOS C.44 EU? Are they using a particular version of a patched boot.img that's floating underground?
Click to expand...
Click to collapse
Your post doesn't specify which version of magisk you're using, unless I overlooked it. If you're not using alpha already, use alpha. And make sure you also patch the boot.img with alpha and not a different version than you're trying to install. A couple of people have said canary works now (at least for C40), but I can't confirm whether it still works on C44. Stable doesn't work (yet).
terlynn4 said:
Your post doesn't specify which version of magisk you're using, unless I overlooked it. If you're not using alpha already, use alpha. And make sure you also patch the boot.img with alpha and not a different version than you're trying to install. A couple of people have said canary works now (at least for C40), but I can't confirm whether it still works on C44. Stable doesn't work (yet).
Click to expand...
Click to collapse
New stable V24 is released. Works great
nicoilboss said:
you don't have to flash the magisk_patched.img but instead boot it with : "fastboot boot magisk_patched.img"
Then you can install magisk by it's manager and reboot the phone.
Here is everything explained: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-0-0-0.4252373/
Click to expand...
Click to collapse
I've tried to use this method but when I try to flash using the 'fastboot boot magisk_boot.img' I get the error "failed - command boot not recognized"
ADB shows the 'sending' command but then nothing happens other than error mentioned above. I've tried to use both the patched and unpatched images but same error. No idea how to proceed from here
I recently got my hands on a T-Mobile 9 Pro. Fresh out of the box a couple weeks ago.
It updated to A12 a few days ago (Software Version says LE2127_11_C.16).
What are my options to root this thing? I'm relatively aware of the steps, but I don't see any temp boot images for the T-Mobile variant.
As I've seen other people mention, OEM unlocking is no longer grayed out, so that appears to be one hurdle out of the way. Right now, after reading about users having data connection issues, I'm not interested in flashing the global/EU images and I'm more than happy sticking with the T-Mobile image.
i have been trying this all day so far and all i get is either bootloop to fastboot or black screen of nothing...
i have also been trying to find the tmo a12 update on my phone where they place it before it installs. but can seem to find it even with a rooted 11.2.9.9. does ne1 know where this file is located. i want to pull it and try and get the boot.img out and try it that way..
ok we are making progress on this, i was apparently doing it the wrong way.
galaxyuser88 said:
i have been trying this all day so far and all i get is either bootloop to fastboot or black screen of nothing...
i have also been trying to find the tmo a12 update on my phone where they place it before it installs. but can seem to find it even with a rooted 11.2.9.9. does ne1 know where this file is located. i want to pull it and try and get the boot.img out and try it that way..
ok we are making progress on this, i was apparently doing it the wrong way.
Click to expand...
Click to collapse
How did you manage to get the root? I have been looking into it for a long time now and haven't been able to obtain it or should I say I'm more afraid to obtain the wrong method and ruin the phone.
NotSoSweet6626 said:
How did you manage to get the root? I have been looking into it for a long time now and haven't been able to obtain it or should I say I'm more afraid to obtain the wrong method and ruin the phone.
Click to expand...
Click to collapse
Well when I fastbooted I would flash boot instead of just boot boot.img.
Also make sure you use the correct boot.img with the same security patch version other wise you might or will have issues..
I am hoping that you have all the adb, fastboot, device drivers all set on your computer. If you do not you can search the internet to see how to setup your computer for this. You will need this to properly root your phone.
Make sure you download and have msm just in case you need it..
1. Download magisk and the magisk app to your phone and install it.
2. You have two choices here you can either pull your own stock boot.img and use magisk app on your phone to patch the img or download the correct version magisk patched boot.img from these forums.
3. Put your phone into fastboot mode
4. Open cmd prompt and Use fastboot " fastboot boot (magisk_patched_boot.img) < this is your patched boot.img".
5. Hit enter. Your computer should send the patched boot img to your phone and then your phone should reboot.
6. Once your phone boots ups, open the magisk app and then click on install. On this part you have to click direct install and then click let's go. Magisk will then root your stock boot img and will reboot.
7. After your phone reboots and you have done everything correctly you should have a rooted phone.
8. Enjoy root.
Sorry I do not have the n10 so I can not help you there.
galaxyuser88 said:
Well when I fastbooted I would flash boot instead of just boot boot.img.
Also make sure you use the correct boot.img with the same security patch version other wise you might or will have issues..
I am hoping that you have all the adb, fastboot, device drivers all set on your computer. If you do not you can search the internet to see how to setup your computer for this. You will need this to properly root your phone.
Make sure you download and have msm just in case you need it..
1. Download magisk and the magisk app to your phone and install it.
2. You have two choices here you can either pull your own stock boot.img and use magisk app on your phone to patch the img or download the correct version magisk patched boot.img from these forums.
3. Put your phone into fastboot mode
4. Open cmd prompt and Use fastboot " fastboot boot (magisk_patched_boot.img) < this is your patched boot.img".
5. Hit enter. Your computer should send the patched boot img to your phone and then your phone should reboot.
6. Once your phone boots ups, open the magisk app and then click on install. On this part you have to click direct install and then click let's go. Magisk will then root your stock boot img and will reboot.
7. After your phone reboots and you have done everything correctly you should have a rooted phone.
8. Enjoy roo
Click to expand...
Click to collapse
NishiMoon said:
Would you happen to have a copy of the Oneplus 9 (not pro) TMobile LE2117_11_C.18 Stock Boot.img?? It would be greatly and I mean greatly appreciated
Click to expand...
Click to collapse
galaxyuser88 said:
Well when I fastbooted I would flash boot instead of just boot boot.img.
Also make sure you use the correct boot.img with the same security patch version other wise you might or will have issues..
I am hoping that you have all the adb, fastboot, device drivers all set on your computer. If you do not you can search the internet to see how to setup your computer for this. You will need this to properly root your phone.
Make sure you download and have msm just in case you need it..
1. Download magisk and the magisk app to your phone and install it.
2. You have two choices here you can either pull your own stock boot.img and use magisk app on your phone to patch the img or download the correct version magisk patched boot.img from these forums.
3. Put your phone into fastboot mode
4. Open cmd prompt and Use fastboot " fastboot boot (magisk_patched_boot.img) < this is your patched boot.img".
5. Hit enter. Your computer should send the patched boot img to your phone and then your phone should reboot.
6. Once your phone boots ups, open the magisk app and then click on install. On this part you have to click direct install and then click let's go. Magisk will then root your stock boot img and will reboot.
7. After your phone reboots and you have done everything correctly you should have a rooted phone.
8. Enjoy root.
Sorry I do not have the n10 so I can not help you there.
Click to expand...
Click to collapse
Would you happen to have a copy of the Oneplus 9 (not pro) TMobile LE2117_11_C.18 Stock Boot.img?? It would be greatly and I mean greatly appreciated
NishiMoon said:
Would you happen to have a copy of the Oneplus 9 (not pro) TMobile LE2117_11_C.18 Stock Boot.img?? It would be greatly and I mean greatly appreciated
Click to expand...
Click to collapse
I will check when I get home. If I do it will prolly be the 9pro 5g one I have..
I would imagine the boot.img would be the same if not very close. I can't seem to get oppo_decrypt to extract the firmware ops file for the boot.img. I just wanna root my phone already
Rooted Stock TMO LE2127_11_C.18
After the last update that screwed up my oneplus 9 pro, I decided it was time to look at unlocking the bootloader and rooting my phone so that I could get control over these damn updates. I just want to be able to root my stock OOS so that I can...
forum.xda-developers.com
Take a look here for the c18 boot img for tmo..
galaxyuser88 said:
Rooted Stock TMO LE2127_11_C.18
After the last update that screwed up my oneplus 9 pro, I decided it was time to look at unlocking the bootloader and rooting my phone so that I could get control over these damn updates. I just want to be able to root my stock OOS so that I can...
forum.xda-developers.com
Take a look here for the c18 boot img for tmo..
Click to expand...
Click to collapse
Thank you but I ended up pulling my own boot.img for the OnePlus 9 instead of trying the OP9 Pro. I was able to pull my own boot.img then patch it, boot it, flash it. Now I'm happily rooted
LE2117.11.c18