Develop Bugs

How to update OTA with Magisk (can I just sideload without risk of bootloops)?

So I can't remove Magisk ("stock boot.img backup does not exist") so I was wondering if it was safe to sideload the November OTA (the whole 1GB file, not sure how to do just the 60MB delta update) and I assume that removes Magisk but keeps userdata, but does that cause any issues e.g bricks or bootloops?
I'm on 8.0 October Security Patch. My main aim isn't to remove Magisk, but I guess I have to to update to the Nov patch, and then reinstall it

brpqzme said:
So I can't remove Magisk ("stock boot.img backup does not exist") so I was wondering if it was safe to sideload the November OTA (the whole 1GB file, not sure how to do just the 60MB delta update) and I assume that removes Magisk but keeps userdata, but does that cause any issues e.g bricks or bootloops?
Click to expand...
Click to collapse
First, try the
[2017.10.15] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu - Magisk-uninstaller-20171123.zip
If that doesn't work download the appropriate Factory Image for your phone.
Go to Android 8/Oreo and do #5 to save data.

I'll give this a shot now!
Do I need to disable any Modules before flashing the ZIP? Couldn't find a definite answer searching online
Homeboy76 said:
First, try the
[2017.10.15] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu - Magisk-uninstaller-20171123.zip
If that doesn't work down the appropriate Factory Image for your phone.
Go to Android 8/Oreo and do #5 to save data.
Click to expand...
Click to collapse

brpqzme said:
I'll give this a shot now!
Do I need to disable any Modules before flashing the ZIP? Couldn't find a definite answer searching online
Click to expand...
Click to collapse
I don't know, but I don't think it would hurt to disable the modules.
Just don't lock the bootloader.

So in case anyone else reads this -
For some reason, flashing the MAGISK UNINSTALLER ZIP caused a soft brick (device would boot only into fastboot and then "NO COMMAND", not boot into OS).
I'd already downloading the factory images from your links, so I flashed BOOT.IMG onto both slots, A and B.
Device then booted back into the OS, no data lost etc. But Magisk w
Still wouldn't accept OTA.
Flashed OTA as per the link you gave with flashall, worked fine. Will flash Magisk through TWRP next.
Thanks

brpqzme said:
So in case anyone else reads this -
For some reason, flashing the MAGISK UNINSTALLER ZIP caused a soft brick (device would boot only into fastboot and then "NO COMMAND", not boot into OS).
I'd already downloading the factory images from your links, so I flashed BOOT.IMG onto both slots, A and B.
Device then booted back into the OS, no data lost etc. But Magisk w
Still wouldn't accept OTA.
Flashed OTA as per the link you gave with flashall, worked fine. Will flash Magisk through TWRP next.
Thanks
Click to expand...
Click to collapse
Please go to the link below and post the information about the problem Magisk-uninstaller-20171123.zip caused:
[2017.11.23] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu
Why? So, topjohnwu can fix it or tell you why it didn't work. The link above is where I got the 'Latest Uninstaller (Support v1+)' from.
Also it would help if you add the make and model of your phone, Magisk- version you were trying to uninstall.
Flashed OTA as per the link you gave with flashall

Posting here instead of creating a new thread.
Same issue as OP except i have TWRP installed as well, so SYS.img is altered as well so i can't take OTAs. Does the factory image also contain system flash?
On the OTA page, it says make sure your device is up to date, but im on October's image and cannot move to November's. Should i flash October and let it OTA to current or safe to flash November. Thinking of just going to 8.1 beta but one step at a time.

AlPoo said:
Posting here instead of creating a new thread.
Same issue as OP except i have TWRP installed as well, so SYS.img is altered as well so i can't take OTAs. Does the factory image also contain system flash?
On the OTA page, it says make sure your device is up to date, but im on October's image and cannot move to November's. Should i flash October and let it OTA to current or safe to flash November. Thinking of just going to 8.1 beta but one step at a time.
Click to expand...
Click to collapse
When you go to settings System Updates can you update?
If not Download the appropriate (October 2017) Factory Image for your phone.
Go to Android 8/Oreo and do #5 to SAVE data or #4 to WIPE data.
This will remove root and you should get the OTA.

Issues on top of issues rooting Pixel 2 XL! Help? :(

First, I followed a tutorial precisely and ended up with a bootloop. It was just stuck at the white screen with a G. This was only after flashing the patched_boot.img file that Magisk gave me. I searched for hours online for an answer for that, and my device isn't listed when I type "adb devices." It's just blank. I uninstalled and reinstalled the drivers, I used different usb ports, different cables, I'm using the latest Google usb drivers, as well as the latest adb/fastboot files.
I wanted to push twrp to my phone via ADB, so I can flash magisk that way and fix this issue. I've read that it fixed my problem for other people, but sadly I'm unable to so far. When I try using the command "adb push twrp.zip /sdcard/" I get the following error:
"adb: error: failed to get feature set: no devices/emulators found"
In case anyone was wondering this is the tutorial I initially followed: https://youtu.be/M-0NIUUvYI4
I really don't know where to go from here. I've been looking around for 6 hours straight. All help is most appreciated.

Fastboot boot the twrp img file, then once you're in twrp, adb push the twrp zip file, and the stock boot image (extract it from whatever security update you're on). Then, adb push the magisk zip file (instead of a patched boot image) and download and adb push a custom kernel as well.
Flash the stock boot img, then twrp zip, then a custom kernel to retain touch functionality within twrp (I recommend flash kernel) and finally flash the magisk zip file and once you reboot, you should be good to go.

rickysidhu_ said:
Fastboot boot the twrp img file, then once you're in twrp, adb push the twrp zip file, and the stock boot image (extract it from whatever security update you're on). Then, adb push the magisk zip file (instead of a patched boot image) and download and adb push a custom kernel as well.
Flash the stock boot img, then twrp zip, then a custom kernel to retain touch functionality within twrp (I recommend flash kernel) and finally flash the magisk zip file and once you reboot, you should be good to go.
Click to expand...
Click to collapse
Thanks for the response, Ricky. I tried using the ADB sideload feature in TWRP but it just stuck at "Starting ADB sideload feature..." and eventually fails. Then I used a flash drive and connected it to the phone via the adapter, and that worked. Unfortunately, after flashing those files it was still stuck at the same bootloop screen. I went back to TWRP and now the usb flash drive isn't being recognized. What should I do?
Edit: I was able to FINALLY get it out of the bootloop! I tried this script earlier and it didn't work, but it was because I didn't have the critical partitions unlocked (https://forum.xda-developers.com/pixel-2/development/tool-deuces-bootloop-recovery-flashing-t3725778). Unlocked them, ran the script, works perfectly now. However, now I'm going to root it via TWRP and use the files you mentioned. Will do that tomorrow after sleep!

rickysidhu_ said:
Fastboot boot the twrp img file, then once you're in twrp, adb push the twrp zip file, and the stock boot image (extract it from whatever security update you're on). Then, adb push the magisk zip file (instead of a patched boot image) and download and adb push a custom kernel as well.
Flash the stock boot img, then twrp zip, then a custom kernel to retain touch functionality within twrp (I recommend flash kernel) and finally flash the magisk zip file and once you reboot, you should be good to go.
Click to expand...
Click to collapse
Hey I just wanted to inform you that I did get it working after continuing where I left off last. Thanks for your help, Ricky. It's much appreciated. Now I'm just gonna investigate on how to update OTA with magisk.

Mr December said:
Hey I just wanted to inform you that I did get it working after continuing where I left off last. Thanks for your help, Ricky. It's much appreciated. Now I'm just gonna investigate on how to update OTA with magisk.
Click to expand...
Click to collapse
If your going the OTA route, which, personally, I wouldn't if your bootloader is "fully" unlocked, you'll need to completely unroot, and return back to stock recovery. Not trying to deter you, I just think that fastbooting the monthly factory images is much easier, with fewer chances for errors. Not to mention, if you know the proper technique, you won't lose any data :good:

Badger50 said:
If your going the OTA route, which, personally, I wouldn't if your bootloader is "fully" unlocked, you'll need to completely unroot, and return back to stock recovery. Not trying to deter you, I just think that fastbooting the monthly factory images is much easier, with fewer chances for errors. Not to mention, if you know the proper technique, you won't lose any data :good:
Click to expand...
Click to collapse
That sounds sick to me. :laugh: Would you mind pointing me in the right direction to a tutorial that has the proper technique to get it done without losing any data?

Mr December said:
That sounds sick to me. :laugh: Would you mind pointing me in the right direction to a tutorial that has the proper technique to get it done without losing any data?
Click to expand...
Click to collapse
This is how I do my monthly updates

Badger50 said:
This is how I do my monthly updates
Click to expand...
Click to collapse
Thanks bro I'll give it a shot today :laugh:

Badger50 said:
This is how I do my monthly updates
Click to expand...
Click to collapse
Hey I'm not exactly sure which factory image I should choose. When I was rooting the phone the tutorial said to use the image with the same build number. My current build number is "OPM1.171019.018, Feb 2018", and I'm assuming what I should do is use this one "OPM2.171019.029, Apr 2018"?
https://developers.google.com/android/images#taimen

Mr December said:
Hey I'm not exactly sure which factory image I should choose. When I was rooting the phone the tutorial said to use the image with the same build number. My current build number is "OPM1.171019.018, Feb 2018", and I'm assuming what I should do is use this one "OPM2.171019.029, Apr 2018"?
https://developers.google.com/android/images#taimen
Click to expand...
Click to collapse
You are correct :good:

Updating Pixel 3 XL and keeping root without wiping data

Hi, I have a Pixel 3 XL it has the February update and it's rooted and has TWRP installed. My question is can I update it via a flashable zip file so I can flash through TWRP? I don't want to lose any of my data because it's a pain setting everything back up. Back in the day I had Cynogen and usually kept up with the nightly updates as often as I could and it was a very simple process. I"m sure it's been asked but after doing some quick google searches all I found was to download the factory image and flash it with a custom flag but I really don't want to have to re-root it and all that again.

Well when you update just edit the flash-all.bat file and delete the -w within that and you won't delete your data. You will loose root and loose the installed twrp but you can easily reinstall and obtain root after the update is completed. Check the guides section of the boards as it has an excellent guide for rooting and updating with Google released updates.

GrandMstrBud said:
Hi, I have a Pixel 3 XL it has the February update and it's rooted and has TWRP installed. My question is can I update it via a flashable zip file so I can flash through TWRP? I don't want to lose any of my data because it's a pain setting everything back up. Back in the day I had Cynogen and usually kept up with the nightly updates as often as I could and it was a very simple process. I"m sure it's been asked but after doing some quick google searches all I found was to download the factory image and flash it with a custom flag but I really don't want to have to re-root it and all that again.
Click to expand...
Click to collapse
Flashing the Google image every month and editing the flash-all script is just what you have to do for A/B phones. The whole process takes less than 10 minutes once a month, and after some practice, probably 5 minutes. Pre-stage the latest TWRP and Magisk on your phone if it is not already there. Once you finish flashing the image, fastboot boot TWRP from your PC and then from your phone use TWRP to queue up both the TWRP and Magisk zipfiles and let her rip. If you use a custom kernel as well, you can do a 3-fer and queue up all three files in TWRP and it will flash all 3 in succession. Just make sure you are using the lastest version of the fastboot/adb binaries before you start. That is all.

Thanks guys, I had to refresh my memory on the process but all together maybe 20 minutes. Next time I'm guessing the process will take 10 minutes since I made some instructions for myself.

I only use temporary TWRP, so when it's time to update I just flash the OTA using stock recovery. No wipe or editing involved.

spotmark said:
I only use temporary TWRP, so when it's time to update I just flash the OTA using stock recovery. No wipe or editing involved.
Click to expand...
Click to collapse
Interesting.
You install Magisk, and at what step do you do that?
Thanks in advance.

Below works, but not always. Be near a computer when you do it and be prepared to use the flash-all without the -w.
1.Magisk Manager → Uninstall → Restore Images). Do not reboot or you will have Magisk uninstalled.
2. Now Update the system and let it install completely. Do not press the reboot button.
3. Go to (Magisk Manager → Install → Install to Inactive Slot) and install Magisk.
4.Once Magisk installation is done, press the reboot button in Magisk Manager.
Your phone may get into bootloop once, if that happens just restart the phone again.

statustray said:
Interesting.
You install Magisk, and at what step do you do that?
Thanks in advance.
Click to expand...
Click to collapse
After I flash the update, I boot the phone, and then into temporary TWRP and flash Magisk.

[GUIDE] How to Root OnePlus 7T without TWRP

So today with some testers i managed to make root on OnePlus 7T, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator). For now you should use only Magisk Canary files
I will explain 2 different guides:
First Root Guide:
This guide is for a specific rom version, so you will need to use a specific patched boot.img
- Download the patched_boot.img
- Reboot your device in bootloader-fastboot mode
- Flash the patched_boot.img in the boot partition:
Code:
fastboot flash boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
Second Root Guide:
This guide is more generic than the first one, you should use this one if you are unable to find a specific patched boot.img
- Download a patched_boot.img (you should try with the latest one)
- Reboot your device in bootloader-fastboot mode
- Boot the patched_boot.img:
Code:
fastboot boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
- Click on Install, then direct install and wait the end of the process
- Reboot the device
Third Root Guide:
Guide by @gpz1100
TIPS:
Actually you should use only Magisk canary files Magisk 20.3
You can get the stock boot images from the fastboot rom: https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
Actually i'm using magisk manager canary and magisk canary debug to patch the boot.img, I don't recommend updating magisk, if you don't want to see the updates install the normal magisk manager
Magisk 20.3 fully support OnePlus 7T and 7T Pro
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use Canary Magisk Manager and Canary Magisk (debug)
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Download:
Patched/Stock Boot Images: https://www.androidfilehost.com/?w=files&flid=300177
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
@RohanAJoshi

Flashed and working flawless.
Really thanks for this.
Awesome work bro.

Can you please upload the patched boot.img please? I dont see it in the above folder at all.

nick_22 said:
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
Click to expand...
Click to collapse
Done, i uploaded them using ftp and i forgot to move the files in the right folder

Working, thanks a lot @mauronofrio

I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.

jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
See OP, its clearly mentioned there. You have to flash this via fastboot and not any custom recovery. Firstly setup adb on your PC and then check the commands. Its very easy. Do some googling and still if its difficult for you, come back and ask.

jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
Welcome to the android scene, reminds me of the old psx scene

I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.

@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?

nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
Get your stock boot.img from 1st post.
Reboot to bootloader.
And do this command
fastboot flash boot boot.img
fastboot reboot
Device will boot unrooted.
---------- Post added at 05:58 AM ---------- Previous post was at 05:55 AM ----------
jesrani;80464121 [user=4712355 said:
@mauronofrio[/user], thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.

RohanAJoshi said:
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
Click to expand...
Click to collapse
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?

jesrani said:
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
In older devices like OP5T it happens like this, not in newer devices. OP7T has seamless updates, its installs while device is turned on in second partition.

nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
jesrani said:
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)

mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?

jesrani said:
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
Canary debug, don't update it

Help please. I have returned to Android after 5years with OnePlus 7t and trying to root it. I am trying this method but not being able to successfully root it. Steps I have tried
Went to fastboot mode by restarting the phone but I don't get an option to install the patched image file. And even boatloader is locked. Do I need to unlock the bootloader. And I unlock will I loose my data. Sorry for silly question I have completely forgot about Android.

Thanks, rooted successfully

?
To be honest need video tutorial asap?

mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Ok. Got it. So, I have already booted back to unrooted mode now. And I cant wipe my data again. Thanks for your response.

December firmware update!

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