October security patches released...
https://dl.google.com/dl/android/aosp/blueline-qp1a.191005.007-factory-c36610c6.zip
Worked exactly the same as the 10 and .C3 build for me. Flash-all (minus -w) and patched boot in Magisk. No issues.
4.3 MB from the C3 update.
After the C3 update I had an improvement in the battery's life but after few days was the same. I hope this will better this time.
Edit : multi-tasking freeze is here again...
sliding_billy said:
Worked exactly the same as the 10 and .C3 build for me. Flash-all (minus -w) and patched boot in Magisk. No issues.
Click to expand...
Click to collapse
It worked fine for 10 and .c3 build, but magisk_patched.img does not work for me. It installs fine and the phone boots up fine but magisk says it is not installed
Code:
~/Downloads/pixel3/blueline-qp1a.191005.007$ sha256sum magisk_patched.img
46432e0feae1b97f631165a10eb0049041c2e6fffce89a6a2733bf8aee9dc9ac magisk_patched.img
Do you have the same sha256sum? I used canary build of magisk to patch it.
---------- Post added at 09:49 PM ---------- Previous post was at 09:36 PM ----------
wildnux said:
It worked fine for 10 and .c3 build, but magisk_patched.img does not work for me. It installs fine and the phone boots up fine but magisk says it is not installed
Code:
~/Downloads/pixel3/blueline-qp1a.191005.007$ sha256sum magisk_patched.img
46432e0feae1b97f631165a10eb0049041c2e6fffce89a6a2733bf8aee9dc9ac magisk_patched.img
Do you have the same sha256sum? I used canary build of magisk to patch it.
Click to expand...
Click to collapse
Nevermind. I had to patch with beta version of magisk. Version: 19.4 (19400) and it worked.
wildnux said:
It worked fine for 10 and .c3 build, but magisk_patched.img does not work for me. It installs fine and the phone boots up fine but magisk says it is not installed
Code:
~/Downloads/pixel3/blueline-qp1a.191005.007$ sha256sum magisk_patched.img
46432e0feae1b97f631165a10eb0049041c2e6fffce89a6a2733bf8aee9dc9ac magisk_patched.img
Do you have the same sha256sum? I used canary build of magisk to patch it.
---------- Post added at 09:49 PM ---------- Previous post was at 09:36 PM ----------
Nevermind. I had to patch with beta version of magisk. Version: 19.4 (19400) and it worked.
Click to expand...
Click to collapse
Good deal. I just never leave Canary for my Pixel 3 and Pixel 3 XL despite having other devices on stable or Beta.
what Google Play System update patch level are you guys on? I'm back to August, 1 from September, 1 after installing the October OTA.... so what's going on here?
Installed yesterday. Now wireless provider signal only shows as 4G, no LTE.
Can I use the same magdisk patched image from C3? Or should I pull the boot image from this update?
gmmurphy said:
Can I use the same magdisk patched image from C3? Or should I pull the boot image from this update?
Click to expand...
Click to collapse
It might work, but I think it is asking for trouble. Try the installation method at https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
It is much simpler, and you don't need to patch boot images. I just did it an hour ago using the latest Magisk from the Canary channel. I saw a report in another thread the latest from the Beta channel also works. I don't think it works with Magisk from the stable channel, but have not tried it.
dcarvil said:
It might work, but I think it is asking for trouble. Try the installation method at https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
It is much simpler, and you don't need to patch boot images. I just did it an hour ago using the latest Magisk from the Canary channel. I saw a report in another thread the latest from the Beta channel also works. I don't think it works with Magisk from the stable channel, but have not tried it.
Click to expand...
Click to collapse
Did you uninstall all the modules before doing this?
georgs_town said:
Did you uninstall all the modules before doing this?
Click to expand...
Click to collapse
No, I did not uninstall the modules, I just followed the instructions in the tutorial.
I was able to flash the factory image by running the "flash.bat" script with "-W" removed. Security update is dated Oct 5, Google Play system is dated Sept 1. Just to be safe, I uninstalled Cerberus before running the script as Cerberus caused me issues transitioning from Android Pie to Android 10 last month.
Other than Cerberus, I only have magisk for rooting, no modules loaded, no edXposed. I re-routed using the latest Canary build for Magisk, patching the boot.img and then flashing the magisk_patched.img in fastboot mode.
So I'm having another major problem. When I updated to 10 from 9 running dirty unicorns, everything flashed fine except for the image update zip. I remember it had something to do with the active slot but I cant remember for the life of me what I did last time to get the image to flash. Currently when I run flash all bootloader and radio flash fine, but flashing the image zip my phone boots into the fastbootd recovery screen and fastboot command screen shows fastboot: error: command failed. Sending sparse product b FAILED.
Any help would be greatly appreciated. Right now I'm stuck in fastboot on my phone.
Edit: I just did a factory wipe and it's flashing fine now. I'm guessing it had something to do with the magisk patched boot img I was using. I really don't know what the problem was.
I am on Android 10 and can't install latest small security update. https://i.imgur.com/0TMV5i8.png
Before I've restored image according to Magisk doc https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Ipeacocks said:
I am on Android 10 and can't install latest small security update. https://i.imgur.com/0TMV5i8.png
Before I've restored image according to Magisk doc https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Just download the full factory image, edit the flash all file to remove the -w, and then flash that in fastboot mode. Make sure you save the flash all file and the -w is removed before you use it. Trying to take the ota on a rooted device doesn't work well.
@jd1639 w/o -w root will disappear but my personal data on phone persists?
Ipeacocks said:
@jd1639 w/o -w root will disappear but my personal data on phone persists?
Click to expand...
Click to collapse
Yes, you'll loose root but your data will all be there. You'll have to move a copy of the stock boot.img file to your device, let magisk patch it, then move the patched file to your pc and flash that with fastboot. Almost all of us do this process with each update.
@jd1639 Are you talking about this `-w`?
https://imgur.com/nlbZdht
Ipeacocks said:
@jd1639 Are you talking about this `-w`?
https://imgur.com/nlbZdht
Click to expand...
Click to collapse
No. Download the factory image to your pc and extract it, it's a zip file. In there you'll see a flash-all.bat file. Edit that. I use notepad ++. Then save it and just double click on the edited file (I'm assuming your using a windows pc). There is also another zip file you'll find after you've extracted the factory image. Extract that too and you'll find the boot.img file you'll need to patch with magisk for root.
Edit, sorry, I didn't look at the image you uploaded that closely. It is the -w I was referring to.
Related
Hi guys I was able to root my P10 using magisk and the new treble project on oreo very easily.
All credit goes to @topjohnwu as he's the creator of Magisk and this method all i'm doing is sharing his work and adding the boot image for the P10
Requirements:
Your PC
P10 ON OREO B360 (this only works on oreo if you try to do it on nougat you could easely brick your device)
Bootloader Unlocked (?)
ADB & Fastboot
I actually don't know if you need to have your bootloader unlocked as it's using the treble project to update the boot partition.
I had mine unlocked when i did this.
Step 1:
Get your boot image from update files (huawei update extractor > settings > uncheck the first 3 checkboxes) here i have the boot image from my VTR-L29C432B360
Install the latest Magisk Manager apk from here.
Step 2:
Open Magisk Manager, go to Settings > Update Channel > Custom Update channel with this link http://goo.gl/jefZKH
after that check if the latest magisk update is v15.4 (as the time of posting this guide)
if it says Invalid Update Channel you probably misspelled the link
Step 3:
Copy your boot image to your internal storage/sd card
Go on Magisk Manager > Install > Patch boot image file > Select the boot image on your internal storage/sd card
when it finishes go on your pc and pull the patched boot image to your desktop or desired folder. it will be stored on your internal memory/MagiskManager/patched-boot.img
Step 4:
Open cmd on the same folder as your patched boot image
Go to fastboot (Power-off then Vol+ and Power)
now on cmd type
Code:
fastboot devices
should come as response a serial number and fastboot
this means your device is connected to you pc and on fastboot
after that type
Code:
fastboot flash ramdisk patched_boot.img
it will flash the patched boot image
when it's done just reboot
and you're set!!
You'll have root with Magisk and pass safety net without a problem.
Friend, thanks for the information. Sorry you know how to install viper4android in B360
DarkPJV said:
Friend, thanks for the information. Sorry you know how to install viper4android in B360
Click to expand...
Click to collapse
i wish i knew... i'm also looking for how to install it. if i get it to work i'll post a guide too
D4XT3R said:
i wish i knew... i'm also looking for how to install it. if i get it to work i'll post a guide too
Click to expand...
Click to collapse
It would be fantastic.friend
Thank you very much for this guide, worked like a charm.
I even have full SafetyNet back, incl. CTS. What I didn't have before I flashed the patched bootimage.
I'm just wondering why you suggest to modify the update channel? I got an error message anyway (and I didn't misspell it), so I changed it back to 'Stable' and had not problems.
smashedup said:
Thank you very much for this guide, worked like a charm.
I even have full SafetyNet back, incl. CTS. What I didn't have before I flashed the patched bootimage.
I'm just wondering why you suggest to modify the update channel? I got an error message anyway (and I didn't misspell it), so I changed it back to 'Stable' and had not problems.
Click to expand...
Click to collapse
well the modified channel update is one that @topjohnwu modified for huawei's treble enabled phones like the P10 so that we wouldn't have any problem with safety net or flashing the boot partition but if it worked for you it might work for others too
Hello i just upgraded from nougat to oreo and bootloader is locked again i tried to flash the recovery img without success any solution to root that phone?
samy0x said:
Hello i just upgraded from nougat to oreo and bootloader is locked again i tried to flash the recovery img without success any solution to root that phone?
Click to expand...
Click to collapse
do you have oem unlocking enabled on your phone? if after enabling this option it still fails to flash the patched boot image unlock the boot loader, I know a pain in the ass, but you'll pass safety net without a problem
D4XT3R said:
do you have oem unlocking enabled on your phone? if after enabling this option it still fails to flash the patched boot image unlock the boot loader, I know a pain in the ass, but you'll pass safety net without a problem
Click to expand...
Click to collapse
Yes
Phone Locked
FRP Unlock
have you tried it again and worked? if not it only works with unlocked bootloader
D4XT3R said:
have you tried it again and worked? if not it only works with unlocked bootloader
Click to expand...
Click to collapse
Yes i tried again no solution i'll wait for sometime if no solution i'll unlock bootloader
I'm exploring that solution maybe : https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-root-preserve-user-data-t3716547
I can confirm that Magisk v16 works for me on VTR-L29C432B360. Installed with the Magisk Manager without flashing in TWRP.
Jannomag said:
I can confirm that Magisk v16 works for me on VTR-L29C432B360. Installed with the Magisk Manager without flashing in TWRP.
Click to expand...
Click to collapse
How did you do that
samy0x said:
How did you do that
Click to expand...
Click to collapse
I opened the Magisk Manager app and it prompted me that v16 is available for install. Then I pressed "Install", rebooted and that was it.
What about working Xposed and Magisk like on Nouget EMUI 5.1? I'm always stock in boot-look when i try to flash BETA3 Xposed v90 SDK 26 amr64
---------- Post added at 07:59 PM ---------- Previous post was at 07:58 PM ----------
Jannomag said:
I opened the Magisk Manager app and it prompted me that v16 is available for install. Then I pressed "Install", rebooted and that was it.
Click to expand...
Click to collapse
Yes me to, but first you need 15.4 magisk version and than you can update to v16 in MagiskManager app
urbanboymne said:
What about working Xposed and Magisk like on Nouget EMUI 5.1? I'm always stock in boot-look when i try to flash BETA3 Xposed v90 SDK 26 amr64
---------- Post added at 07:59 PM ---------- Previous post was at 07:58 PM ----------
Yes me to, but first you need 15.4 magisk version and than you can update to v16 in MagiskManager app
Click to expand...
Click to collapse
Oh, of course. Sorry, I meant with "not flashing with TWRP" that I didn't need to flash the zip for v16 manually, just install it within the app. But of course you need to install 15.4 first.
meh , cant extract ramdisk.img from update.zip...
About magisk...is the root gone away finally fixed ?
on my old nova plus,when rooted whit magisk,we had to flash that darn patched boot img every 1-2 weeks in order to re have root again
is that finally fixed ?
Jannomag said:
I can confirm that Magisk v16 works for me on VTR-L29C432B360. Installed with the Magisk Manager without flashing in TWRP.
Click to expand...
Click to collapse
Exactly the same for me... and passes safety net
---------- Post added at 02:04 PM ---------- Previous post was at 01:57 PM ----------
Can we flash TWRP 3.1.1 after rooting with Magisk ?
Big thankyou it worked like a charm
Here's how to root the Pixel 3 running on official and stock Android 10 release, step by step :
(not tested on Pixel 3 XL but it might work the same, just use the right firmware for your device)
What do you need :
> Pixel 3 phone with Android 10
> Unlocked bootloader on your Pixel device
> Latest ADB and FASTBOOT tools on your computer
1 ) Download the latest Android 10 factory image for your device ("Blueline" is the regular Pixel 3) :
Link > Android 10 factory image
2 ) Extract the "boot.img" file on your phone
3 ) Download latest Magisk Manager application on your phone and install it :
Link > https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched
5 ) Enable adb debugging on your Pixel phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
9 ) When i'ts done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings and rebooting your phone.
Note that this guide is actually for using adaway. I don't know if it will work for any other root related feature on your phone.
Great guide, thanks!
ibolito said:
11 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings.
Click to expand...
Click to collapse
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
bafforosso said:
Great guide, thanks!
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
Click to expand...
Click to collapse
Thanks its done!
I get a "This site can't be reached" message when I click the link for magisk manager in step 3. Not sure if anyone else sees it.
Thank you for making this guide!
Thanks, works perfectly!
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Oberbergler said:
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Click to expand...
Click to collapse
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
If I updated via ota adb side load to 10. But used the boot.img from the factory image, would this explain why it did boot, however not one app would start. The system ui would then crash. Just trying to figure out where I screwed up. Thank you.
ibolito said:
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
Click to expand...
Click to collapse
Thanks man Everything was right but I forgot to update adb and fastboot. Now I have root
ignore me -- im idiot.
i am not sure if my pixel 3 is really rooted. all the apps requiring root says they are granted root access, but, for example, i cannot modify system files with a root file manager at all unlike i could with android 9. how can i confirm it is surely rooted?
So I have a problem, maybe someone can help me with.
Back in March I made the following post:
"I was running on the original September Update since I got the phone, I used this guide when I first rooted https://www.xda-developers.com/googl...r-root-magisk/
Today I decided it was time to update so I used this guide https://www.xda-developers.com/flash...-google-pixel/
Then I wanted to reroot my phone. So I bootet the TWRP image and flashed the magisk 18.1 zip. But after that I softbricked my phone and it wouldn't boot anymore.
So in my panic I flashed the TWRP zip and my phone worked again, but now everytime I try to flash the magsik zip the same thing happens, bootloop and back to flashing twrp.zip. "
After that didn't work, I tried flashing the magisk uninstaller, through twrp, but it exited with "Error 1" everytime. (Running TWRP 3.3.0)
So i decided to give up, because I had some personal stuff to take care of, but after Android 10 came out yesterday, I decided to give this another go.
I flashed the factory image without "-w" and everything is working fine. So today I followed this guide, double checked everything but after I flash the patched boot image I get stuck with a bootloop again... I can flash back the original boot image and everything works so it's not a huge deal, but right now I can't use google pay, because it says I'm rooted.
Any idea what I could do? Can't run the uninstaller and can't reroot... ???
thanks!
Have you checked if your patched boot.img matches the firmware on your phone?
Well it's the same one I used to flash the firmware.
I flashed yesterday without an issue and today I loaded that boot.img onto my phone, used the canary magisk manager to patch it and then transfered it back to my PC to flash it.
Edit: I'm thinking this might have to do with the fact that I couldn't uninstall magisk before.
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
GohanBurner said:
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
Click to expand...
Click to collapse
I had it working before I bodged a magisk module install
No luck here. The steps SEEM to work perfectly. Flashed the modified boot image, booted up fine, but magisk says it's still not installed. No root.
- Latest magisk canary
- Used the same firmware
- No errors anywhere along the way
Hey Mac users, I had to use the command fastboot flash boot_b magisk_patched.img
To get the patched image over to my phone. It worked out great. I was able to reboot,
and see the root in Magisk Manager.
YMMV
Thanks, worked like a charm on Linux with latest platform-tools! I thought I'd have to wait a lot longer to get root back on my device.
I have also tried this multiple times. No errors, but I can't edit system files or add modules.
[GCAM] Buffer fix by Wyroczen
Hey, I've made buffer fix for LG V40 in a form of TWRP flashable zip and second option with file for replacement:
It will fix lagging viewfinder in GCAM both nightsight and normal mode.
Instructions:
Boot into TWRP, mount vendor, flash zip.
Requirements:
Stock android 9 work (may or may not work in others)
Downloads:
Celsoazevedo: https://www.celsoazevedo.com/files/android/p/lg-v40-buffer-fix/
Donation:
If you want, you can support my work by sending me donation
https://www.paypal.me/wyroczen
XDA: DevDB Information
LG V40 TWRP flashable lib fix.
xenius9 said:
patched lib for android 10. wyroczen helped me do it)
Click to expand...
Click to collapse
What's this?
View attachment fix-buffer-Magisk.zip
View attachment fix-buffer-TWRP.zip
Well gonna try it on Android 10 Pixel Experience and report back with Gcam 7
Ainz_Ooal_Gown said:
Well gonna try it on Android 10 Pixel Experience and report back with Gcam 7
Click to expand...
Click to collapse
lib from android 9, Android 10 may not work.
bsg19071979 said:
lib from android 9, Android 10 may not work.
Click to expand...
Click to collapse
Well the magisk module didn't show up at all
Ainz_Ooal_Gown said:
Well the magisk module didn't show up at all
Click to expand...
Click to collapse
View attachment fix-buffer-Magisk_Q.zip
working great on stock, just used latest GCam_7.3.018_Urnyx05-v1.5.apk
EDIT: it seems after using stock camera, the lag is back. Stock camera crashed for me but worked again after restart. For anyone who wants to revert the change I have attached original, untouched file from Pie firmware.
Scratch that, my phone reverts to default file after reboot, something is not right with Magisk, will have to check, sorry for confusion
If I'm unrooted, can I use this?
Does anyone know how to manually replace the lib file without using TWRP? I'm rooted and have tried several root file managers. Seems like the original file is still there after reboot.
This is for stock ROMs, I am currently using 20f:
you have to disable verity:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
you can dump vbmeta.img using qfil
You have to install Magisk also, so dump with qfil boot_a and boot_b, upload them to your phone and patch them with Magisk Manager, back to qfil and flash patched versions back. You will have working root.
Use any File Manager with root to replace com.qti.chi.override.so (SHA1: DE4248C89864CFD676522FE8BD19AA03D4A2BF3E) inside /vendor/lib/hw/
Use external SD card in this process, will save you a lot of headaches and don't use TWRP. For some reasons it doesn't work on stock.
Thanks. I learn something every day. Motorollas disable dm-verity automatically after unlocking the bootloader, so never had to do this seperatly before.
Will the fastboot commands wipe user data?
Does "adb disable-verity" work on those phones as well? Or must it be done in fastboot?
it doesn't wipe user data
well, this was working on 20e fw but it doesn't work anymore on 20f fw, I can't mount /vendor or /system as RW in TWRP
could be a TWRP issue. I'm on 20e currently. Is there a 20f for US retail?
banesi said:
you have to disable verity:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
you can dump vbmeta.img using qfil
Click to expand...
Click to collapse
Worked great to disable Verity! Thank you. Took me a moment to realize that I had to copy the vbmeta partitions first, using QFIL. Then rewrite the partitions using the fastboot commands from your post.
The post above should be sticky or prerequisite for the OP.
Unfortunately even with the lagfix file replacing the stock file, Im stll getting the same lag in GCam.
For some unkown reason even when you magisk/twrp buffer fix, file stays the same
---------- Post added at 12:16 ---------- Previous post was at 11:34 ----------
bsg19071979 said:
View attachment 4994459
View attachment 4994461
Click to expand...
Click to collapse
well, this is wrong, lib files inside those zips are just stock files, not modified files
I have updated my previous post.
That did the trick. Gcam working great now!
Had to get the file again, this time downloading it directly from celsoazevedo.com. This time the SHA1 matched what you had in your post above.
For reference, using GCam 7.3 from Urnyx05 v1.5 with the config file below. Not claiming it's the perfect, but so far so good....
https://f.celsoazevedo.com/file/cfiles/gcm1/GCam_7.3.018_Urnyx05-v1.5.apk
Config file
https://www.celsoazevedo.com/files/android/p/f/2020/02/7.2uryny2.1.xml
banesi said:
For some unkown reason even when you magisk/twrp buffer fix, file stays the same
---------- Post added at 12:16 ---------- Previous post was at 11:34 ----------
well, this is wrong, lib files inside those zips are just stock files, not modified files
I have updated my previous post.
Click to expand...
Click to collapse
when I use your override file on andriod 10( lg v40,v30b), some funtion has bug , cine video mode can't see any thing but full green screen. hope U can do something, THX!
Sadly this breaks HDR 10 and cine video on stock Q right now. Hope you'd be able to look at this issue! Good job with the buffer fix
skeeeee said:
Sadly this breaks HDR 10 and cine video on stock Q right now. Hope you'd be able to look at this issue! Good job with the buffer fix
Click to expand...
Click to collapse
Same here! But this doesn't break these features. It just gives green screen in viewfinder but records the video normally
Hi,
I just updated to 10.0.9.HD01BA on my OP7T Pro and after that I tried to root it with Magisk by patching the OTA update.
This didn't work and it was stuck at the boot animation, so I extracted the boot.img and patched it with Magisk.
But with the patched version I'm also always stuck at the boot animation.
If I flash the original boot.img again, everything is fine, except that there is no root of course.
I already rooted many OP7 and OP7T and never got this result.
Is Magisk currently not supporting 10.0.9, or am I doing something wrong?
I really don't know what else I could do.
Is someone else experiencing this issue?
Catter38 said:
Hi,
I just updated to 10.0.9.HD01BA on my OP7T Pro and after that I tried to root it with Magisk by patching the OTA update.
This didn't work and it was stuck at the boot animation, so I extracted the boot.img and patched it with Magisk.
But with the patched version I'm also always stuck at the boot animation.
If I flash the original boot.img again, everything is fine, except that there is no root of course.
I already rooted many OP7 and OP7T and never got this result.
Is Magisk currently not supporting 10.0.9, or am I doing something wrong?
I really don't know what else I could do.
Is someone else experiencing this issue?
Click to expand...
Click to collapse
Did you disable and delete all Magisk modules before updating to OOS 10.0.9? If not, do the following:
- Boot your phone and enable ADB debugging in dev settings.
- Flash the patched Magisk boot.img.
- During boot connect your device to a PC and enter:
"adb wait-for-device shell magisk --remove-modules"
- Your device should reboot without any modules and you can install them again.
Macusercom said:
Did you disable and delete all Magisk modules before updating to OOS 10.0.9? If not, do the following:
- Boot your phone and enable ADB debugging in dev settings.
- Flash the patched Magisk boot.img.
- During boot connect your device to a PC and enter:
"adb wait-for-device shell magisk --remove-modules"
- Your device should reboot without any modules and you can install them again.
Click to expand...
Click to collapse
Unfortunately, I forgot to uninstall the modules.
I tried the adb command and the device reboots, but it's still in the same bootloop.
I also tried to uninstall the modules with TWRP, but since there isn't a fully working version for the OP7T Pro, this also didn't work.
What's weird is, that the magisk patched version of the boot.img always results in a way smaller file than the original.
The original file is ~100mb, while the patched version is ~40mb.
I don't know if this is normal, but it seems odd.
I also tried it with the canary version of magisk, which results in the same small boot.img.
Looks like I have to stay unrooted until this is fixed.
Ok, finally I got it to work.
Since my girlfriend also has a OP7T Pro and still is on 10.0.8 with root, I simply took her boot image and booted it with fastboot. This also resulted in the same bootloop, but now the adb command worked and I was able to boot a rooted 10.0.8 boot.img. Now I was able to use the direct install of magisk and patched the 10.0.9 installation with it.
I think my problem was, that I did't remove the modules in the first place, which screwed up the whole update.
I still can't explain why I wasn't able to patch the boot.img with magisk. It didn't work on my phone with the canary build of magisk, neither did it work on the phone of my girlfriend with magisk 20.4.
Anyway. Now I have a working 10.0.9 boot.img and can safely upgrade my girlfriends phone too.
Thanks for the help!
https://app.box.com/s/9r77wcvk2dnbos87rpr1lfcnmnd091le
Here is.... HD10.0.9BA Patched and the original boot.img..... ?
kovacsabesz said:
https://app.box.com/s/9r77wcvk2dnbos87rpr1lfcnmnd091le
Here is.... Last build... Patched and the original img..... ?
Click to expand...
Click to collapse
Interesting, your patched image also is way smaller than the original.
Did you verify, that it's working?
https://app.box.com/s/at1mhbvpkspg4wfzp16cqppgdvvidese
I'm using it now.... Without problem
Catter38 said:
Interesting, your patched image also is way smaller than the original.
Did you verify, that it's working?
Click to expand...
Click to collapse
It seems to be normal. I'm not sure why but it might be due to compression. Anyway, glad you figured it out.
Catter38 said:
Interesting, your patched image also is way smaller than the original.
Did you verify, that it's working?
Click to expand...
Click to collapse
kovacsabesz said:
https://app.box.com/s/9r77wcvk2dnbos87rpr1lfcnmnd091le
Here is.... HD10.0.9BA Patched and the original boot.img.....
Click to expand...
Click to collapse
Would you mind uploading the files again if you can? I'm struggling with my device being in bootloop and I can't remove the module causing it bc I can't access adb with the bootloop. With the stock boot img I'm hoping to boot the device again and remove the bad module via adb
Macusercom said:
Did you disable and delete all Magisk modules before updating to OOS 10.0.9? If not, do the following:
- Boot your phone and enable ADB debugging in dev settings.
- Flash the patched Magisk boot.img.
- During boot connect your device to a PC and enter:
"adb wait-for-device shell magisk --remove-modules"
- Your device should reboot without any modules and you can install them again.
Click to expand...
Click to collapse
Im im a similar situation now, is there a way before removing the modules all i can backup them or atleast access a file or something with the modules names ?
kovacsabesz: can you please reupload the file? Thanks
I have a Samsung A52 5g and there is a new software update from android 11 to 12. Do I have to go through the first time setup for magisk or can i just patch it as an update like normal?
sygmstr said:
I have a Samsung A52 5g and there is a new software update from android 11 to 12. Do I have to go through the first time setup for magisk or can i just patch it as an update like normal?
Click to expand...
Click to collapse
If the previous method was patching the boot image, you can repeat the process with the new one that comes with the update.
SubwayChamp said:
If the previous method was patching the boot image, you can repeat the process with the new one that comes with the update.
Click to expand...
Click to collapse
well I just tried updating and I lost root so if you update to a newer version of android you have to do a clean install of magisk
sygmstr said:
well I just tried updating and I lost root so if you update to a newer version of android you have to do a clean install of magisk
Click to expand...
Click to collapse
Sure, you lost root as an update includes most likely a newer boot image that will replace the magisk-patched boot image, as I said you, you should patch the new boot image included in the update and install it normally, not a clean update, so you wouldn't need to uninstall it previously.
SubwayChamp said:
Sure, you lost root as an update includes most likely a newer boot image that will replace the magisk-patched boot image, as I said you, you should patch the new boot image included in the update and install it normally, not a clean update, so you wouldn't need to uninstall it previously.
Click to expand...
Click to collapse
I tried patching magisk to my samsung using the method in their instructions twice now and I havent been able to get it to work. Can you help me?
sygmstr said:
I tried patching magisk to my samsung using the method in their instructions twice now and I havent been able to get it to work. Can you help me?
Click to expand...
Click to collapse
And what was the method you used the first time? In some devices you need to patch the boot image, if this is the case you have to extract the boot image from the stock ROM (the same you're currently on), unpack it from the lz4 format, also depends on if your device has ramdisk, and most of them support patching the whole AP file and then converting it in tar format to flash it through Odin. You should follow this https://topjohnwu.github.io/Magisk/install.html
I just did this upgrade and successfully kept magisk, did you get this working?