Ok so im a little frustrated and hope someone can put me in the right direction. My first mistake was flashing the wrong build. I was rooted on the nov build and flashed The decmber update but i flashed the US build and got a bootloop.(i have the Canadian variant). then i flashed a magisk patched boot image not realizing i had installed the wrong build and of course that wouldnt boot. Luckily i could still acess fastboot so i flashed the correct build without erasing data and boom it booted. yippee right? So then i patched the boot.img with the correct canary build of magisk and then adb reboot fastboot followed with fastboot flash boot and the patched img. but im back to a bootloop. So I flash the original boot.img and im back but no root. My brain is now mush!!! i need someone to hold my hand and tell me how to just clean slate everything and reoot.
wulfgarfang said:
Ok so im a little frustrated and hope someone can put me in the right direction. My first mistake was flashing the wrong build. I was rooted on the nov build and flashed The decmber update but i flashed the US build and got a bootloop.(i have the Canadian variant). then i flashed a magisk patched boot image not realizing i had installed the wrong build and of course that wouldnt boot. Luckily i could still acess fastboot so i flashed the correct build without erasing data and boom it booted. yippee right? So then i patched the boot.img with the correct canary build of magisk and then adb reboot fastboot followed with fastboot flash boot and the patched img. but im back to a bootloop. So I flash the original boot.img and im back but no root. My brain is now mush!!! i need someone to hold my hand and tell me how to just clean slate everything and reoot.
Click to expand...
Click to collapse
Deactivate your magisk modules. I had a bootloop because of a mod by tulsadiver
P6P said:
Deactivate your magisk modules. I had a bootloop because of a mod by tulsadiver
Click to expand...
Click to collapse
sorry im not in a bootloop. i reflashed the boot.img and im back but a patched boot img wont work i get a bootloop.
wulfgarfang said:
sorry im not in a bootloop. i reflashed the boot.img and im back but a patched boot img wont work i get a bootloop.
Click to expand...
Click to collapse
Yes i know. But when you flash a patched boot.img your modules will be activated automatically. On stock boot.img they're deactivated because of missing magisk.
That sounds awesome but how can i deactivate the modules if i cant access them?
wulfgarfang said:
That sounds awesome but how can i deactivate the modules if i cant access them?
Click to expand...
Click to collapse
Dunno if there is an easier way but I did:
1. Flash patched boot.img
2. Turn off device
3. "adb wait-for-device shell magisk --remove-modules"
4. Connect your phone to computer and turn it on.
5. Phone tries to boot and the command should be accepted
6. Wait until the command worked and the phone boots up without issues
P6P said:
Dunno if there is an easier way but I did:
1. Flash patched boot.img
2. Turn off device
3. "adb wait-for-device shell magisk --remove-modules"
4. Connect your phone to computer and turn it on.
5. Phone tries to boot and the command should be accepted
6. Wait until the command worked and the phone boots up without issues
Click to expand...
Click to collapse
P6P said:
Yes i know. But when you flash a patched boot.img your modules will be activated automatically. On stock boot.img they're deactivated because of missing magisk.
Click to expand...
Click to collapse
My god man! Thank you so much. I could not do it as outlined above but I did it through safe mode and it worked im rooted again. And i also had the tulsadiver mod. I never thought about a module causing the issue until you mentioned it. Thank you again.....I dont have to start over. Two days of thinking and annoying my wife is over.
wulfgarfang said:
My god man! Thank you so much. I could not do it as outlined above but I did it through safe mode and it worked im rooted again. And i also had the tulsadiver mod. I never thought about a module causing the issue until you mentioned it. Thank you again.....I dont have to start over. Two days of thinking and annoying my wife is over.
Click to expand...
Click to collapse
I'm glad to help.
Step 1: Long press the power key until the Google logo appears on your Pixel.
Step 2: When the Google logo disappear & the animation starts, press & hold the volume down button until your phone boot into safe mode.
Step 3: You can see safe mode at the bottom left corner.
This will disable all magisk modules and then reboot
Solved....thanks everyone! I did it through safe mode and it worked im rooted again. And i also had the tulsadiver mod. I never thought about a module causing the issue until you mentioned it. Thank you again.....I dont have to start over. Two days of thinking and annoying my wife is over.
Related
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
DarkPhoenix said:
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
Click to expand...
Click to collapse
From what I understand you can not do ADB in TWRP to install an update. What I did was download the factory images, remove -w from the flash all.bat. flashed the images and let the phone boot normally. Once I knew it was running I went to the bootloader and booted TWRP temporarily. Once that was up I flashed Magisk and then my kernel
I don't install TWRP anymore.
DarkPhoenix said:
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
Click to expand...
Click to collapse
Adding to what hatdrc said, you want the full image, not OTA, and install from your PC in fastboot mode. If you are concerned about saving your data, remove the -w switch from flash-all.bat first using a file editor like notepad. Have the twrp.zip, kernel.zip and magisk.zip files already staged. I personally don't boot to system first (but you can), I "catch" the reboot after flashing completes with the volume down button to reboot to fastboot mode. Then fastboot boot twrp.img, and then install twrp, kernel and magisk zips all in one go using the "add more zips" button in twrp. Every month when you update, you'll lose twrp, kernel and magisk, so those have to be reflashed each time. You'll soon get used to it and can do the whole thing in about 5 minutes consistently. Just make sure to pre-stage the 3 zip files on the phone before you start. Best of luck.
I tried that but couldn't get it to work. I downloaded the ADB tools again just in case there was an issue with that. I'm going to run the flash-all script again to see if I can get it to work.
DarkPhoenix said:
I tried that but couldn't get it to work. I downloaded the ADB tools again just in case there was an issue with that. I'm going to run the flash-all script again to see if I can get it to work.
Click to expand...
Click to collapse
if whats suggested above doesnt work, you can make the OTA work....download the ota to your PC, boot to Android Recovery (not TWRP), apply the ota via ADB from the menu. Whenever I have "odd" issues applying the Full image, this always works for me. Obviously you need to re-root after.
GL!
cmh714 said:
if whats suggested above doesnt work, you can make the OTA work....download the ota to your PC, boot to Android Recovery (not TWRP), apply the ota via ADB from the menu. Whenever I have "odd" issues applying the Full image, this always works for me. Obviously you need to re-root after.
GL!
Click to expand...
Click to collapse
Doesn't installing TWRP remove Android Recovery?
DarkPhoenix said:
Doesn't installing TWRP remove Android Recovery?
Click to expand...
Click to collapse
hmm, since I dont install TWRP anymore, you may be correct....still cant hurt to try
DarkPhoenix said:
Doesn't installing TWRP remove Android Recovery?
Click to expand...
Click to collapse
Yes it does. TWRP replaces the stock recovery.
Sent from my [device_name] using XDA-Developers Legacy app
v12xke said:
Adding to what hatdrc said, you want the full image, not OTA, and install from your PC in fastboot mode. If you are concerned about saving your data, remove the -w switch from flash-all.bat first using a file editor like notepad. Have the twrp.zip, kernel.zip and magisk.zip files already staged. I personally don't boot to system first (but you can), I "catch" the reboot after flashing completes with the volume down button to reboot to fastboot mode. Then fastboot boot twrp.img, and then install twrp, kernel and magisk zips all in one go using the "add more zips" button in twrp. Every month when you update, you'll lose twrp, kernel and magisk, so those have to be reflashed each time. You'll soon get used to it and can do the whole thing in about 5 minutes consistently. Just make sure to pre-stage the 3 zip files on the phone before you start. Best of luck.
Click to expand...
Click to collapse
Ok, I got the flash-all script to run. My brain shut down and I was running the wrong command.
DarkPhoenix said:
Ok, I got the flash-all script to run. My brain shut down and I was running the wrong command.
Click to expand...
Click to collapse
Well done. Now you can do it all over again in a week on Monday the 7th when the January build comes out.
v12xke said:
Well done. Now you can do it all over again in a week on Monday the 7th when the January build comes out.
Click to expand...
Click to collapse
I was updating so I could install Bootleggers rom so updating should be a lot easier lol.
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!
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
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
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