Trying to patch boot.img with Magisk on March update. I check "select and patch..", select boot.img and it says "lets go". When I click on that Magisk closes and nothing happens. No magisk_patched.img is created. Anyone else have this problem?
Daisymae said:
Trying to patch boot.img with Magisk on March update. I check "select and patch..", select boot.img and it says "lets go". When I click on that Magisk closes and nothing happens. No magisk_patched.img is created. Anyone else have this problem?
Click to expand...
Click to collapse
What do you mean when you say you "checked
select and patch'? Do you mean you opened Magisk Manager tapped install (next to Magisk),tapped install, tapped select a boot image to patch. Selected it and tapped the check mark? If yes, try again.
Homeboy76 said:
What do you mean when you say you "checked
select and patch'? Do you mean you opened Magisk Manager tapped install (next to Magisk),tapped install, tapped select a boot image to patch. Selected it and tapped the check mark? If yes, try again.
Click to expand...
Click to collapse
Tried it several times with same result. When I get to "method" I tap "select and patch". It immediately takes me to the download directory where the boot.img is. I tap that and it takes me back to the screen with the methods. I tap next and then "lets go" appears.. I tap that and it closes. Nothing happens.
Update: found the problem. It was a canary magisk manager. DL the stable one and patched image was created.
Daisymae said:
Trying to patch boot.img with Magisk on March update. I check "select and patch..", select boot.img and it says "lets go". When I click on that Magisk closes and nothing happens. No magisk_patched.img is created. Anyone else have this problem?
Click to expand...
Click to collapse
Had exactly the same thing today. I cleared cache and data on Magisk Manager, uninstalled it and then reinstalled. Worked fine after that. Might be able to skip the uninstall step, I just do things that 2ay to be complete. Make sure you get the APK from a legit source, there are fakes out there.
Ahhh, just saw the post above. Yep I was on Canary and when I reinstalled I went back to stable.
Yes, it is a bug in the latest canary magisk manager. It should be fixed in next canary release.
Stable version roots fine so that's an option until canary builds are fixed.
rspkt said:
Stable version roots fine so that's an option until canary builds are fixed.
Click to expand...
Click to collapse
Beta works without issue as well.
Where is DL for APK...
imaverik said:
Where is DL for APK...
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/
thx!
imaverik said:
thx!
Click to expand...
Click to collapse
You're welcome!
When I patch the March boot.img with Magisk Manager 7.5.1 stable and Magisk 20.3 I get a boot loop at the "G" screen after the progress bars cycle for a few seconds. I actually got the same result when I did the Magisk method of accepting the March OTA which is why I'm trying this method. I've tried reflashing both slots with factory March and then flashing patched image to both slots, so far no love. If I flash the stock boot.img back to the active slot it boots right up without root. Any ideas? TIA!
ktdt00 said:
When I patch the March boot.img with Magisk Manager 7.5.1 stable and Magisk 20.3 I get a boot loop at the "G" screen after the progress bars cycle for a few seconds. I actually got the same result when I did the Magisk method of accepting the March OTA which is why I'm trying this method. I've tried reflashing both slots with factory March and then flashing patched image to both slots, so far no love. If I flash the stock boot.img back to the active slot it boots right up without root. Any ideas? TIA!
Click to expand...
Click to collapse
It could be a bad (outdated) module that is causing the boot loop.
Try this:
- Download: image-newpixel3xlRemove
-
Code:
fastboot flash boot magisk_patched.img --slot all
-
Code:
fastfoot boot image-newpixel3xl.img
- Use a root file manager to open data/adb/modules folder
- Remove/Delete all the modules in the folder
- Remove/Delete the hidden file: .disable_magisk in the cache folder
- Reboot
- Thank the OP!
Homeboy76 said:
It could be a bad (outdated) module that is causing the boot loop.
Try this:
- Download: image-newpixel4xlRemove
-
Code:
fastboot flash boot magisk_patched.img --slot all
-
Code:
fastfoot boot image-newpixel4xlRemove.img
- Use a root file manager to open data/adb/modules folder
- Remove/Delete all the modules in the folder
- Remove/Delete the hidden file: .disable_magisk in the cache folder
- Reboot
- Thank the OP!
Click to expand...
Click to collapse
That worked! I actually had to use the image-newpixelxx vs image-newpixelxxRemove as the latter also boot looped for me. Who knows what state I'd gotten myself into to cause that. I also had to manually take Magisk out of core only mode afterwards in the app settings in order to get systemless hosts working again. Anyway - it definitely was a bad module and you put me directly on the right track! Thanks so much!
ktdt00 said:
It could be a bad (outdated) module that is causing the boot loop.
Try this:
- Download: image-newpixel4xlRemove
-
-
That worked! I actually had to use the image-newpixelxx vs image-newpixelxxRemove as the latter also boot looped for me. Who knows what state I'd gotten myself into to cause that. I also had to manually take Magisk out of core only mode afterwards in the app settings in order to get systemless hosts working again. Anyway - it definitely was a bad module and you put me directly on the right track! Thanks so much!
Click to expand...
Click to collapse
Glad you got it working.
Hey all, anyone having the issue of the Play Store not being certified after updating to the March update? I'm rooted after using the patched image with Magisk but I can't get certified. Thanks in advance.
My phone boots fine after root but the touch screen is not working. After flashing the stock boot.img again then everything works fine. Any suggestions? Thanks in advance.
JayYip said:
My phone boots fine after root but the touch screen is not working. After flashing the stock boot.img again then everything works fine. Any suggestions? Thanks in advance.
Click to expand...
Click to collapse
If I may ask, what version Magisk are you using? Stable or Canary?
rsnyc said:
If I may ask, what version Magisk are you using? Stable or Canary?
Click to expand...
Click to collapse
Stable.
JayYip said:
Stable.
Click to expand...
Click to collapse
I can't figure it out on my Pixel 3 XL. Hopefully someone will update us.
Related
Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.
Works fine for me.
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Working fine for me as well.
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.
RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.
Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018
I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse
Hello,
I have seen few requests about providing pre-rooted boot image file for OP7T Global (not Indian or European) version for firmware 10.0.6 so here you go.
Steps :
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
Also attaching the stock boot file in case anything goes wrong.
P.S : I don't own Global OP7T.
Link : https://androidfilehost.com/?w=files&flid=302500
has anyone tried this one yet?
xrelic7 said:
has anyone tried this one yet?
Click to expand...
Click to collapse
I would if I could update to the Global rom. Local update fails on rooted Indian 10.0.6. Anyone can advise me on this?
damn i want to do it but i am afraid some of my apps will stop working cause idk if magiskhide will work at current time
xrelic7 said:
has anyone tried this one yet?
Click to expand...
Click to collapse
Yes, I tried on my 7t and it booted successfully!Thanks OP's work!!! By the way , I also flash Blu kernel via fk app and it also worked fine. But I don't test any magisk mondule.
23333 said:
Yes, I tried on my 7t and it booted successfully!Thanks OP's work!!! By the way , I also flash Blu kernel via fk app and it also worked fine. But I don't test any magisk mondule.
Click to expand...
Click to collapse
ty for the reply i might grow a few and give it a shot hopefully magiskhide is working so certain apps cant detect that i am rooted
I tried the method above it booted the first time without problems however when i installed magisk canary and tried it did not have the option to direct install idk if i did something wrong not sure
xrelic7 said:
I tried the method above it booted the first time without problems however when i installed magisk canary and tried it did not have the option to direct install idk if i did something wrong not sure
Click to expand...
Click to collapse
Are you using Global or Indian HD65AA ? Not getting an option to directly install means somehow the patched image did not boot and the original imaged booted.
imakul8 said:
I would if I could update to the Global rom. Local update fails on rooted Indian 10.0.6. Anyone can advise me on this?
Click to expand...
Click to collapse
You need to download the global 10.0.6 OTA not fastboot image in order to do the local update.
zeusofyork said:
You need to download the global 10.0.6 OTA not fastboot image in order to do the local update.
Click to expand...
Click to collapse
Yes, that's what I have.
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
I've followed the above steps exactly but when I reboot the device it and open MAgisk Manager it shows that MAgisk is not installed. Any ideas?
Edit: I'm on Hd1900 Chinese variant running 10.0.6 global ROM
---------- Post added at 02:02 AM ---------- Previous post was at 01:18 AM ----------
ricksrod said:
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
I've followed the above steps exactly but when I reboot the device it and open MAgisk Manager it shows that MAgisk is not installed. Any ideas?
Edit: I'm on Hd1900 Chinese variant running 10.0.6 global ROM
Click to expand...
Click to collapse
When you run step 2, it boots the phone. Step 3 says to reboot. Not sure if that is correct? Rebooting would just boot to the stock boot image again?
ricksrod said:
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
I've followed the above steps exactly but when I reboot the device it and open MAgisk Manager it shows that MAgisk is not installed. Any ideas?
Edit: I'm on Hd1900 Chinese variant running 10.0.6 global ROM
---------- Post added at 02:02 AM ---------- Previous post was at 01:18 AM ----------
When you run step 2, it boots the phone. Step 3 says to reboot. Not sure if that is correct? Rebooting would just boot to the stock boot image again?
Click to expand...
Click to collapse
You're right. Just skip that step 3.
imakul8 said:
You're right. Just skip that step 3.
Click to expand...
Click to collapse
I did assume that so that's the step I followed.
Just to confirm, when I boot the patched image and install Magisk Manager and launch it, it should show that it is already installed? So I press "install" next to Magisk and direct install, this looks like it works. Then I reboot and I am not rooted, if I open Magisk Manager it shows that Magisk is not installed.
ricksrod said:
I did assume that so that's the step I followed.
Just to confirm, when I boot the patched image and install Magisk Manager and launch it, it should show that it is already installed? So I press "install" next to Magisk and direct install, this looks like it works. Then I reboot and I am not rooted, if I open Magisk Manager it shows that Magisk is not installed.
Click to expand...
Click to collapse
Right. Magisk said it was installed. I direct installed again, rebooted and Magisk was still installed. No idea to help you. ?
imakul8 said:
Right. Magisk said it was installed. I direct installed again, rebooted and Magisk was still installed. No idea to help you.
Click to expand...
Click to collapse
I've tried extracting the boot_img from my device and then patching that directly in Magisk and that does not work also, even though it reports a success, it doesn't appear to work.
When you install Magisk, what do you have ticked in the Advanced Settings out of:
Preserve Force Encryption
Preserve AVB 2.0/dm-verify
Recovery Mode
?
ricksrod said:
I've tried extracting the boot_img from my device and then patching that directly in Magisk and that does not work also, even though it reports a success, it doesn't appear to work.
When you install Magisk, what do you have ticked in the Advanced Settings out of:
Preserve Force Encryption
Preserve AVB 2.0/dm-verify
Recovery Mode
?
Click to expand...
Click to collapse
Just the first two. Not recovery mode.
imakul8 said:
Just the first two. Not recovery mode.
Click to expand...
Click to collapse
I've got it working now by using the Canary version of Magisk. I thought the stable version was now working?
ricksrod said:
I've got it working now by using the Canary version of Magisk. I thought the stable version was now working?
Click to expand...
Click to collapse
Stable is working for me, but good that you got it working. ?
Can someone check if magisk hide is working properly? Thanks
Jeens99 said:
Can someone check if magisk hide is working properly? Thanks
Click to expand...
Click to collapse
It works. Snapchat and my banking app don't like root. They're working fine.
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
I'm currently on Magisk 20.4
Is it safe to update to 21.4?
I heard some updates didn't go well on our phone.
Thanks
kenbo111 said:
I'm currently on Magisk 20.4
Is it safe to update to 21.4?
I heard some updates didn't go well on our phone.
Thanks
Click to expand...
Click to collapse
Yup, did both updates this morning. Working fine on 21.4
Quick question - I was going to do this myself to provide another datapoint, but I'm wondering about the "Preserve AVB 2.0/dm-verity" option. It's unchecked, which I think is correct... but what does this mean, and how should we have this set (ie, if we think for ourselves, what's this about?)
For some reason, the "Direct Install" (or whatever it's called) option in Magisk Manager didn't work. It just said "download complete" and didn't actually install it. Maybe that's why you heard that the update didn't go well. I had to do the "Download zip only" option, instead, reboot into recovery and install it there. It seems to be working fine. It's just the update option in Magisk Manager that didn't.
Osprey00 said:
For some reason, the "Direct Install" (or whatever it's called) option in Magisk Manager didn't work. It just said "download complete" and didn't actually install it. Maybe that's why you heard that the update didn't go well. I had to do the "Download zip only" option, instead, reboot into recovery and install it there. It seems to be working fine. It's just the update option in Magisk Manager that didn't.
Click to expand...
Click to collapse
Weird, direct install has always worked for me. Other devices not so much, but always on the V30.
schwinn8 said:
Quick question - I was going to do this myself to provide another datapoint, but I'm wondering about the "Preserve AVB 2.0/dm-verity" option. It's unchecked, which I think is correct... but what does this mean, and how should we have this set (ie, if we think for ourselves, what's this about?)
Click to expand...
Click to collapse
Sorry to repost, but for you guys who did the Magisk install, can you please answer this question? Do we leave this preserve option unchecked (that's how it's coming up on my phone).
schwinn8 said:
Sorry to repost, but for you guys who did the Magisk install, can you please answer this question? Do we leave this preserve option unchecked (that's how it's coming up on my phone).
Click to expand...
Click to collapse
Anyone would know better than me, but I've done it checked and unchecked without issue. I lean toward checking it when updating, not really sure why.
ldeveraux said:
Weird, direct install has always worked for me. Other devices not so much, but always on the V30.
Click to expand...
Click to collapse
Yeah, it's always worked for me, as well. This was the first time that it didn't, which is why I mentioned that it could be an issue with this particular version.
schwinn8 said:
Sorry to repost, but for you guys who did the Magisk install, can you please answer this question? Do we leave this preserve option unchecked (that's how it's coming up on my phone).
Click to expand...
Click to collapse
I didn't get a "preserve" option (or any options). Maybe that's only if you're coming from certain versions, like 20.x versions, since I believe that I updated from 21.0.
Osprey00 said:
Yeah, it's always worked for me, as well. This was the first time that it didn't, which is why I mentioned that it could be an issue with this particular version.
I didn't get a "preserve" option (or any options). Maybe that's only if you're coming from certain versions, like 20.x versions, since I believe that I updated from 21.0.
Click to expand...
Click to collapse
Nope, it's there on mine when I upgraded from 21.X to 21.X. It's right there when you expand Option when you start the Install process.
ldeveraux said:
Nope, it's there on mine when I upgraded from 21.X to 21.X. It's right there when you expand Option when you start the Install process.
Click to expand...
Click to collapse
I get no such option when I install it from recovery. Maybe it's only if you install it through Magisk Manager.
Well, I went ahead and installed it with the option unchecked. It applied and booted with no issues. Looks like it worked.
I figured leaving it unchecked makes sense, since I believe we disable dm-verity during the WTF process anyway, so we shouldn't need to touch it. I wanted to be sure before I did it myself, but it seems I didn't have to worry. Unchecked worked for me.
Osprey00 said:
I get no such option when I install it from recovery. Maybe it's only if you install it through Magisk Manager.
Click to expand...
Click to collapse
Well yeah, I thought that would have been clear. I said I was able to flash direct install, not through twrp
ldeveraux said:
Well yeah, I thought that would have been clear. I said I was able to flash direct install, not through twrp
Click to expand...
Click to collapse
I know, and I did the opposite. I was just speaking it out loud for the sake of discussion.
Speaking of things that should've been clear earlier, it's occurred to me that that "Preserve AVB 2.0/dm-verity" probably does exactly what it says. Remember that, until about a year ago, it was recommended to flash a "dm-verity" zip in recovery when installing a ROM. I don't remember the order, but it could've been that we were supposed to flash Magisk first and then dm-verity because Magisk erased the latter. That "preserve" option, therefore, likely allows you to flash Magisk without erasing dm-verity and having to go into recovery after to re-flash it. Now, we haven't needed to flash dm-verity for a year, so the option may not matter if you're using a ROM version that's less than a year old, though there's probably no harm in being safe and checking it. Anyways, that's my guess.
My attempt of update Magisk from 21.4 to 22.0 brought me completely forgotten fastboot screen. Phone no longer boots. Just fastboot screen.
Magisk's direct install seemed to do nothing for unknown reason. Later I needed to reboot and was surprised to see fastboot screen.
Which partition should I flash using fastboot to fix this (especially preserving data, root, twrp etc.) ?
boot or boot + system? I do have a TWRP backups of these, but they are in WIN format. Can Ijust flash them with fastboot?
There's more to this -
fastboot devices
list no devices.
Reinstallation of the LG drivers didn't help.
you
przemhb said:
My attempt of update Magisk from 21.4 to 22.0 brought me completely forgotten fastboot screen. Phone no longer boots. Just fastboot screen.
Magisk's direct install seemed to do nothing for unknown reason. Later I needed to reboot and was surprised to see fastboot screen.
Which partition should I flash using fastboot to fix this (especially preserving data, root, twrp etc.) ?
boot or boot + system? I do have a TWRP backups of these, but they are in WIN format. Can Ijust flash them with fastboot?
Click to expand...
Click to collapse
You need to flash the original boot image from your stock or custom ROM via the flash boot using the command "flashboot flash boot <boot_file>
Then reflash TWRP and re-install magisk. Maybe the v21.4. The latest one broke my boot too. Good luck!
You need to flash the original boot image from your stock
Click to expand...
Click to collapse
I've got TWRP flashable TWRP-H93030b_00_OPEN_EU_0704.zip with two files: boot.img, and boot-original.img.
If I recall correctly boot.img is pre-patched? Which of these should I use?
I finally managed to connect over fastboot.
przemhb said:
I've got TWRP flashable TWRP-H93030b_00_OPEN_EU_0704.zip with two files: boot.img, and boot-original.img.
If I recall correctly boot.img is pre-patched? Which of these should I use?
I finally managed to connect over fastboot.
Click to expand...
Click to collapse
boot.img should be good. You can always flash the other boot image if it does not boot up.
Managed to flash "boot.img", TWRP and boot to TWRP, but... got "Mount Decrypt Data Enter Password".
I haven't encrypted purposely any partition.
Furthermore TWRP locked and doesn't unlock when I try to "swipe to unlock"...
Forced reboot. Android started. Phone works, but Magisk isn't installed. Rebooted once again into TWRP and installed Magisk ignoring data decrypt message. TWRP said it failed, but after reboot Magisk Manager sees Magisk installed and so TitaniumBackup
Seems it solved the prolem.
My phone updated to le2125_11_c.61 and I can't find a suitable boot.img to flash magisk. The OTA update has a partial boot image so that fails. Does anyone have a copy of the boot.img for this version, or is there another method I should use?
rustyshakelford2 said:
My phone updated to le2125_11_c.61 and I can't find a suitable boot.img to flash magisk. The OTA update has a partial boot image so that fails. Does anyone have a copy of the boot.img for this version, or is there another method I should use?
Click to expand...
Click to collapse
Just use the C.48 patched image, boot (don't flash), and then direct install Magisk. Should work. If it doesn't, no harm done since you didn't flash it.
EtherealRemnant said:
Just use the C.48 patched image, boot (don't flash), and then direct install Magisk. Should work. If it doesn't, no harm done since you didn't flash it.
Click to expand...
Click to collapse
That was a nice thought, but unfortunately it didn't work. The phone hangs when booting both the magisk'd and regular C.48 image.
I did fastboot boot boot.img. Is that correct? I'm a bit out of practice.
rustyshakelford2 said:
That was a nice thought, but unfortunately it didn't work. The phone hangs when booting both the magisk'd and regular C.48 image.
I did fastboot boot boot.img. Is that correct? I'm a bit out of practice.
Click to expand...
Click to collapse
Yeah that's correct. Bummer that it didn't work. Give me a few to download and patch it.
rustyshakelford2 said:
That was a nice thought, but unfortunately it didn't work. The phone hangs when booting both the magisk'd and regular C.48 image.
I did fastboot boot boot.img. Is that correct? I'm a bit out of practice.
Click to expand...
Click to collapse
Well unfortunately I have downloaded two different python scripts trying to patch the full OTA with the incremental OTA and they are both failing so I guess we will have to wait for someone else to do it because I don't have the expertise to fix this.
As long as your bootloader is unlocked, You could try booting (again not flashing) into TWRP and then try sideloading Magisk (after renaming .apk to .zip) ?
djsubterrain said:
As long as your bootloader is unlocked, You could try booting (again not flashing) into TWRP and then try sideloading Magisk (after renaming .apk to .zip) ?
Click to expand...
Click to collapse
You can't boot into TWRP because it doesn't work on OOS12. It crash dumps.
Someone who is rooted needs to install the OTA and pull the image unless there is a tool I haven't come across that works better for incremental OTA extraction.
The incremental C.61 OTA (downloaded thru Oxygen Updater) ins't getting installed.
The oxygen updater app isn't listing the file and the About device Local Install is throwing Verification failed.
Any idea to fix this ?
LE2121
Thanks
observingi said:
The incremental C.61 OTA (downloaded thru Oxygen Updater) ins't getting installed.
The oxygen updater app isn't listing the file and the About device Local Install is throwing Verification failed.
Any idea to fix this ?
LE2121
Thanks
Click to expand...
Click to collapse
I am also facing the same problem..
rustyshakelford2 said:
My phone updated to le2125_11_c.61 and I can't find a suitable boot.img to flash magisk. The OTA update has a partial boot image so that fails. Does anyone have a copy of the boot.img for this version, or is there another method I should use?
Click to expand...
Click to collapse
Try using the MSM tool for your device, press F8, then select boot_a or boot_b depending on what slot you're in. To check your slot, reboot to fastboot and issue the command fastboot getvar current-slot.
You should be able to then patch the boot.img and flash it normally.
razercortex said:
Try using the MSM tool for your device, press F8, then select boot_a or boot_b depending on what slot you're in. To check your slot, reboot to fastboot and issue the command fastboot getvar current-slot.
You should be able to then patch the boot.img and flash it normally.
Click to expand...
Click to collapse
Getting this phone to actually boot into MSM mode is a nightmare. I either end up in fastboot or it boots up normally. I got it to show up exactly once, but it timed out and booted up before I got the readback going.
rustyshakelford2 said:
Getting this phone to actually boot into MSM mode is a nightmare. I either end up in fastboot or it boots up normally. I got it to show up exactly once, but it timed out and booted up before I got the readback going.
Click to expand...
Click to collapse
Enable USB debugging in settings, then type adb reboot edl.
razercortex said:
Enable USB debugging in settings, then type adb reboot edl.
Click to expand...
Click to collapse
I got it! I managed to readback boot_b using the password "oneplus". I can't seem to find where it saved the file though.
It's in C:\ aka your root drive
razercortex said:
Try using the MSM tool for your device, press F8, then select boot_a or boot_b depending on what slot you're in. To check your slot, reboot to fastboot and issue the command fastboot getvar current-slot.
You should be able to then patch the boot.img and flash it normally.
Click to expand...
Click to collapse
That's a cool trick. I didn't know about that one.
Successfully rooted! Huge thanks to razercortex and others in this thread who helped.
Here is a download of both the unmodified and magisk patched boot.img for e2125_11_c.61 global.
https://www.dropbox.com/s/bpoe31lt022rigj/e2125_11_c.61%20global%20boot.img.zip?dl=1
I booted the patched image via fastboot and then did a magisk direct install. After updating the safetynet fix module and running props I am passing safeteynet. I had to restore props to defaults and then apply the android 11 fingerprint for this phone, otherwise it would fail CTS.
rustyshakelford2 said:
Successfully rooted! Huge thanks to razercortex and others in this thread who helped.
Here is a download of both the unmodified and magisk patched boot.img for e2125_11_c.61 global.
https://www.dropbox.com/s/bpoe31lt022rigj/e2125_11_c.61%20global%20boot.img.zip?dl=1
I booted the patched image via fastboot and then did a magisk direct install. After updating the safetynet fix module and running props I am passing safeteynet. I had to restore props to defaults and then apply the android 11 fingerprint for this phone, otherwise it would fail CTS.
Click to expand...
Click to collapse
Can you please share the steps to get the boot.img
I have to get it from LE2121
gulshanstrider said:
Can you please share the steps to get the boot.img
I have to get it from LE2121
Click to expand...
Click to collapse
You should be able to just boot (don't flash) the 2125 rooted image they posted and then use Magisk to direct install.
EtherealRemnant said:
You should be able to just boot (don't flash) the 2125 rooted image they posted and then use Magisk to direct install.
Click to expand...
Click to collapse
I have an LE2125 on 11_C.61 and when I fastboot the posted patched boot.img file I get Magisk Installed: N/A in Magisk Manager. I even patched the posted boot.img myself in Magisk and get Magisk Installed: N/A when fastbooting that patched boot.img. Any ideas?
TornSack said:
I have an LE2125 on 11_C.61 and when I fastboot the posted patched boot.img file I get Magisk Installed: N/A in Magisk Manager. I even patched the posted boot.img myself in Magisk and get Magisk Installed: N/A when fastbooting that patched boot.img. Any ideas?
Click to expand...
Click to collapse
Did you go to try to direct install? I haven't actually tried C.61 yet, I've got stuff to do this weekend and can't have my phone in an experimental state when I'm trying to call and Uber to get around, so I can't test it myself.