Related
Can anyone upload a Magisk patched boot image for 10.0.1GM57AA? The model that I have is GM1900. When I try to patch it myself on Magisk, I get an error saying "process error"
Anyone able to help?
Heelixx said:
Anyone able to help?
Click to expand...
Click to collapse
Hi.
magisk-patched 4.14.117-perf+ with twrp: https://ufile.io/3ieksyfx
flash with fastboot flash boot 4.14.117-perf+.img
meltbanana said:
Hi.
magisk-patched 4.14.117-perf+ with twrp: https://ufile.io/3ieksyfx
flash with fastboot flash boot 4.14.117-perf+.img
Click to expand...
Click to collapse
Thanks a lot for uploading this! I managed to flash it and root my device but now the wifi isn't working. I cleared the cache with TWRP but that didn't resolve the issue. Flashing back the original boot image made the wifi work again.
Heelixx said:
Thanks a lot for uploading this! I managed to flash it and root my device but now the wifi isn't working. I cleared the cache with TWRP but that didn't resolve the issue. Flashing back the original boot image made the wifi work again.
Click to expand...
Click to collapse
ok, perhaps it depends on BA (EU) or AA (global) ROM version? however you can boot the rooted one, install a downloaded version of magisk20 via magisk manager to patch your own kernel directly.
meltbanana said:
ok, perhaps it depends on BA (EU) or AA (global) ROM version? however you can boot the rooted one, install a downloaded version of magisk20 via magisk manager to patch your own kernel directly.
Click to expand...
Click to collapse
I flashed the 4.14.117-perf+.img that you uploaded and then I booted in TWRP and flashed my original stock boot image. While still in TWRP, I flashed the zip of Magisk and then I rebooted. That got it working. So I'm rooted now. Thanks for sending me the image. I appreciate it!
@Heelixx
Can you explain to me how important a magisk boot patched is? Did you leave Pie for 10? What's the procedure?
lvints said:
@Heelixx
Can you explain to me how important a magisk boot patched is? Did you leave Pie for 10? What's the procedure?
Click to expand...
Click to collapse
I was rooted on 10.0 and then I upgraded to 10.0.1
There is a procedure for upgrading to 10.0.1 and still keeping root. I wasn't aware of this and after I got the update, I restarted my device and ended up without root access.
A Magisk patched boot image is important for getting your device rooted.
If you're asking for the procedure to root your device, then you can follow this link which explains it, https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
In case it helps anyone out, here is a link to the stock boot.img from March QQ2A.200305.003, and one I patched with Magisk 20.3 (20300).
Stock file: https://drive.google.com/open?id=1I9cnV8rH4GVCgEDJa1j4ps5VwVj3zfD-
Patched file: https://drive.google.com/open?id=1DA7vt1AtFmtc4XYX5_UCTjbkEa0fweuc
These files are to install Magisk. Please only flash it if you are already on March update. This is not March OTA!
Link courtesy of @i5lee8bit; March OTA patched with Magisk 20.4 https://www.androidfilehost.com/?w=files&flid=306923
Dear Mushtafa, great thanks to you! I've been looking for this all day. Thank you!
mushtafa said:
In case it helps anyone out, here is a link to the stock boot.img from March QQ2A.200305.003, and one I patched with Magisk 20.3 (20300).
Stock file: https://drive.google.com/open?id=1I9cnV8rH4GVCgEDJa1j4ps5VwVj3zfD-
Patched file: https://drive.google.com/open?id=1DA7vt1AtFmtc4XYX5_UCTjbkEa0fweuc
Click to expand...
Click to collapse
Doesn't work for me when I flash the magisk and reboot, I can no longer swipe or tap anything on my screen. Only physical side buttons are functioning.
onlyguynamedniles said:
Doesn't work for me when I flash the magisk and reboot, I can no longer swipe or tap anything on my screen. Only physical side buttons are functioning.
Click to expand...
Click to collapse
You've already updated to March and booting OK?
Have Magisk Manager installed?
You could flash the stock file and modify itself with your install of Magisk and see if that makes any difference.
I'm not sure how many people have flashed this? Not sure if anyone else has had issues with it?
mushtafa said:
You've already updated to March and booting OK?
Have Magisk Manager installed?
You could flash the stock file and modify itself with your install of Magisk and see if that makes any difference.
I'm not sure how many people have flashed this? Not sure if anyone else has had issues with it?
Click to expand...
Click to collapse
No I'm still on January, I never got the Feb OTA and didn't bother to try manually since it didn't seem significant enough but I wanted this March update because of the new Pixel drop feature set.
You can't flash the March boot image if you're still on January! That's why you're having issues.
You need to flash the boot mode mage from January, or update to Match firmware
mushtafa said:
You can't flash the March boot image if you're still on January! That's why you're having issues.
You need to flash the boot mode mage from January, or update to Match firmware
Click to expand...
Click to collapse
I tried to do this with the March update downloading it from Google and the result was the same as onlyguynamedniles, my touchscreen not working, I am in February update.
Last month there were several downloads for February, this time for March only one file available.
otrobruno said:
I tried to do this with the March update downloading it from Google and the result was the same as onlyguynamedniles, my touchscreen not working, I am in February update.
Last month there were several downloads for February, this time for March only one file available.
Click to expand...
Click to collapse
You flashed the March boot.img on your February firmware? Why?
mushtafa said:
You flashed the March boot.img on your February firmware? Why?
Click to expand...
Click to collapse
sorry but this was my first time trying this, before all I had to do was:
when OTA was available, went to Magisk Manager/Uninstall/Restore Images (Not Reboot)
applied OTA as everyone ormally would Settings/System/System Update (Not Reboot)
then, go to Magisk Manager/Install/Install to Inactive Slot
finally, after installation done, reboot
but this march update is not appearing so steps I've tried this time:
1. Got the latest boot image
2. Patched boot image in magisk manager
3. Flashed magisk-patched boot image
please your help what's missing?
otrobruno said:
sorry but this was my first time trying this, before all I had to do was:
when OTA was available, went to Magisk Manager/Uninstall/Restore Images (Not Reboot)
applied OTA as everyone ormally would Settings/System/System Update (Not Reboot)
then, go to Magisk Manager/Install/Install to Inactive Slot
finally, after installation done, reboot
but this march update is not appearing so steps I've tried this time:
1. Got the latest boot image
2. Patched boot image in magisk manager
3. Flashed magisk-patched boot image
please your help what's missing?
Click to expand...
Click to collapse
If you're not getting the March OTA, you need to download it from Google and sideload it. https://developers.google.com/android/ota
There is a thread here somewhere which shows how to do this.
The boot.img I shared above is for people who need it for Magisk and saves them downloading the ~2GB factory file.
Hi.
Is "10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)" ok for the pixel 4 xl unlocked ?
wonderlander17 said:
Hi.
Is "10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)" ok for the pixel 4 xl unlocked ?
Click to expand...
Click to collapse
Affirmative :good:
dang is it that hard to understand . if youre build number does not look exactly like this QQ2A.200305.003 then do not use these boot.img's
its that simple this is not to upgrade you to the march sec patch with root this is for people already on the march sec patch to use to gain root
FIXED IT!! After taking the March update I flashed this patched img the phone boots up to a black screen. If you use the power button it brings up a White menu with "power off" "restart". So then I turn the phone off and load fastboot and flash the stock boot img and everything works again. Any ideas? Figured it out.... Magisk modules that were running.
Can you flash any of them without the use of a computer?
mydjtl said:
Can you flash any of them without the use of a computer?
Click to expand...
Click to collapse
Nope. TWRP or any other recovery is not yet compatible.
mydjtl said:
Can you flash any of them without the use of a computer?
Click to expand...
Click to collapse
Yes with ex kernel manager it's possible
Here's an updated patched March 2020 QQ2A.200305.003 boot image with Magisk 20.4.
I've been using it for the last 2 days and haven't noticed any problems as of yet. Couldn't direct install in Magisk Manager, so feel free to use this if it makes things any easier. OP, please feel free to add this link to your post if you want.
https://www.androidfilehost.com/?w=files&flid=306923
i5lee8bit said:
Here's an updated patched March 2020 QQ2A.200305.003 boot image with Magisk 20.4.
I've been using it for the last 2 days and haven't noticed any problems as of yet. Couldn't direct install in Magisk Manager, so feel free to use this if it makes things any easier. OP, please feel free to add this link to your post if you want.
https://www.androidfilehost.com/?w=files&flid=306923
Click to expand...
Click to collapse
Added to OP, cheers
So i accidentally updated my pixel firmware via official OTA update (security patch 5. january 2021). First i was scared of a bootloop but it all went fine and booted.
Of course my root is gone now, but i want to root it again. Bootloader is still unlocked. Does anyone know, if i can just flash the magist boot.img again and it will boot fine? Or is there a risk that maybe THIS will cause a bootloop?
Thanks!
ViruuZ said:
So i accidentally updated my pixel firmware via official OTA update (security patch 5. january 2021). First i was scared of a bootloop but it all went fine and booted.
Of course my root is gone now, but i want to root it again. Bootloader is still unlocked. Does anyone know, if i can just flash the magist boot.img again and it will boot fine? Or is there a risk that maybe THIS will cause a bootloop?
Thanks!
Click to expand...
Click to collapse
You need to patch the new boot.img.
sd_shadow said:
You need to patch the new boot.img.
Click to expand...
Click to collapse
Thanks for reply! So i extract my current boot.img, but how to patch it?
ViruuZ said:
Thanks for reply! So i extract my current boot.img, but how to patch it?
Click to expand...
Click to collapse
Open Magisk manager app
Select install magisk
Select and Patch a File
Copy new patched boot.img to pc
Flash
well, was a bit hasty here. I knew i could patch it via magisk, but last time there already was a patched image given. How can i extract my boot.img without root now? Or is there maybe a given for the last update?
ViruuZ said:
well, was a bit hasty here. I knew i could patch it via magisk, but last time there already was a patched image given. How can i extract my boot.img without root now? Or is there maybe a given for the last update?
Click to expand...
Click to collapse
Found my current firmware, will extract it there. Thanks anyway!
ViruuZ said:
well, was a bit hasty here. I knew i could patch it via magisk, but last time there already was a patched image given. How can i extract my boot.img without root now? Or is there maybe a given for the last update?
Click to expand...
Click to collapse
Normally you have to go to google firmware page and download it.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Are you guys having the SafetyNet passed?
sd_shadow said:
You need to patch the new boot.img.
Click to expand...
Click to collapse
No you don't. You only have to repatch the new boot image when a new major Android revision comes out. For example going from Android 11 to 12. I've updated my Pixel 5 every month a new update comes out. And I've always used the same boot.image file. No need to keep wasting your time patching that file. When you look through the OTA files you'll notice that none of those files in the zip file are a boot.image file. Meaning it doesn't touch it when it's doing the OTA.
xT29c said:
You only have to repatch the new boot image when a new major Android revision comes out.
Click to expand...
Click to collapse
That is kind of useful, thank you for sharing. Can someone confirm this?
@hanni2301 Have you succeeded in getting root back ? I got the same problem today....
Why do you ask me?
I always patch the actual boot.img out of the monthly factory image with magisk (beta or Canary) first and flash then the factory image, reboot, flash boot boot.img and afterwards the custom kernel.
@xT29c said that you can reuse ure patched boot.img from last month, as it changes only between different mayor Versions.
So you can save some time, but the process is still the same.
IMO, yes, you should always patch the new boot.img from each months new factory image in Magisk when re-rooting.
Do you need to? i suppose that's up to you. However I think you should want to.
Essentially, you're missing out on any code changes/fixes, etc that Google may have added to the new months kernel.
~ Maybe an idea for a new thread to upload the Pixel 5 stock boot.img from each months new OTA, along with a Magisk patched boot.img. ~
Same issue losing root. But when I try to open Magisk manager app, it says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing the same thing.
leveleyed said:
Same issue losing root. But when I try to open Magisk manager app, it says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing the same thing.
Click to expand...
Click to collapse
I am not sure, but this may be because Magisk Manager is no longer..
get v22
New v22.0 update merges Magisk and Magisk Manager app
Samsung's Galaxy S21 series is now supported too
www.androidpolice.com
Hello, I have a OnePlus 9 running android 12 c.40 and I'm trying to update to c.47. When I try and update it says installation problem half way through. I've tried clearing the storage to most system and Google apps along with hiding them from magisk with no luck. I'm unsure if there's a way to update manually with Android 12 because I could not find a way. I was only able to update through TWRP before in which it is incompatible with Android 12. Would appreciate any help with this!
SeeTurtle said:
Hello, I have a OnePlus 9 running android 12 c.40 and I'm trying to update to c.47. When I try and update it says installation problem half way through. I've tried clearing the storage to most system and Google apps along with hiding them from magisk with no luck. I'm unsure if there's a way to update manually with Android 12 because I could not find a way. I was only able to update through TWRP before in which it is incompatible with Android 12. Would appreciate any help with this!
Click to expand...
Click to collapse
Google-ota detects altered partitions and ota fails... Your boot img is altered to root. Restore stock boot img for build your on currently. Google your method.
Google-ota detects altered partitions and ota fails... Your boot img is altered to root. Restore stock boot img for build your on currently. Google your method.
Click to expand...
Click to collapse
So I just completely uninstalled magisk and used the flash toolbox to retire stock images. I also flashed the stock boot.img myself but still with no luck
SeeTurtle said:
So I just completely uninstalled magisk and used the flash toolbox to retire stock images. I also flashed the stock boot.img myself but still with no luck
Click to expand...
Click to collapse
Did you also flash a custom kernel?
mattie_49 said:
Did you also flash a custom kernel?
Click to expand...
Click to collapse
Yes but I reflashed the stock kernel
SeeTurtle said:
Yes but I reflashed the stock kernel
Click to expand...
Click to collapse
Here is your other issue. Dtbo,vendor_boot stock untouched need flashed back.
SeeTurtle said:
Yes but I reflashed the stock kernel
Click to expand...
Click to collapse
This doesn't matter
mattie_49 said:
Here is your other issue. Dtbo,vendor_boot stock untouched need flashed back.
Click to expand...
Click to collapse
Unfortunately still getting the same error
I am in the same situation. I only had my OP 9 for a couple of weeks and I came from a OP 5 where rooting and flashing was much easier. It would be good to know what you did to get OOS updated.
So when you download the package, you can use Oxygen Updater to install it. Choose the root package and it will install with Magisk, you will lose Twrp recovery. But you can just flash that back afterwards. Worked like a charm for me
I don't have TWRP cause it's not compatible with Android 12. I've had to factory reset the last 3 updates because of this same issue. When I had TWRP I could update with oxygen update and keep root. Being android 12 I also don't have the option to manually update via the phones update system. I don't mind factory resetting again because I have swift backup. I'd just like to know how to avoid it. Like if I could just flash it with fastboot or something
I downloaded the Oxygen Updater app and downloaded the full OTA however not able to use the auto update method simply because TWRP does not work on A12. There is a manual process where you need to download the OP Local Update APK and use this to flash the update. I have not tried this myself but I would assume you would lose root doing this method and need to root your phone again.
Z-Blade said:
I downloaded the Oxygen Updater app and downloaded the full OTA however not able to use the auto update method simply because TWRP does not work on A12. There is a manual process where you need to download the OP Local Update APK and use this to flash the update. I have not tried this myself but I would assume you would lose root doing this method and need to root your phone again.
Click to expand...
Click to collapse
This worked! I uninstalled root in the first place so losing it didn't matter. This is the Apk. You have to remove the .zip in order to turn it into an APK. Thanks for the tip!
SeeTurtle said:
This worked! I uninstalled root in the first place so losing it didn't matter. This is the Apk. You have to remove the .zip in order to turn it into an APK. Thanks for the tip!
Click to expand...
Click to collapse
Sweet! I have downloaded the full OTA and extracted the boot.img so I can use Magisk to patch it to get root again. I still haven't gone through the process yet but thanks for letting us know this method works. Also thanks to @illusiveairforce for leading us to the Oxygen Updater app.
mattie_49 said:
Here is your other issue. Dtbo,vendor_boot stock untouched need flashed back.
Click to expand...
Click to collapse
Hi,
What else should I reflash to make sure all root traces are removed ?
abl.img
aop.img
bluetooth.img
boot.img
boot.on mobile.img
cpucp.img
devcfg.img
dsp.img
dtbo.img
engineering_cdt.img
featenabler.img
hyp.img
imagefv.img
keymaster.img
modem.img
multiimgoem.img
my_bigball.img
my_carrier.img
my_company.img
my_engineering.img
my_heytap.img
my_manifest.img
my_preload.img
my_product.img
my_region.img
my_stock.img
odm.img
oplusstanvbk.img
oplus_sec.img
product.img
qupfw.img
qweslicstore.img
shrm.img
splash.img
system.img
system_ext.img
tz.img
uefisecapp.img
vbmeta.img
vbmeta_system.img
vbmeta_vendor.img
vendor.img
vendor_boot.img
vm-bootsys.img
xbl.img
xbl_config.img
After successfully rooting my Nord 2T by backing up and then patching the stock boot.img I proceeded to patch the inactive slot within Magisk (it was unecessary of me..) and after rebooting entered a loop. Anyone know where I can get the factory ROM? I was on the May patch. Thanks in advance!
I am also looking for the factory OTA image.
How did you get the boot.img exactly?
jolaviska said:
I am also looking for the factory OTA image.
How did you get the boot.img exactly?
Click to expand...
Click to collapse
Good ol SP Flash but I think the backed up images are corrupted hence the need of factory firmware to use it to restore my device.
Apologies I did not realise you still needed the firmware. I have mirrored it here if you still need it May Patch Full ROM
garylawwd said:
Apologies I did not realise you still needed the firmware. I have mirrored it here if you still need it May Patch Full ROM
Click to expand...
Click to collapse
So extracting boot. img from your file won't be enough to do Root right?
Riski3Run said:
So extracting boot. img from your file won't be enough to do Root right?
Click to expand...
Click to collapse
You can't extract from the firmware. You must use spflash tool to pull the boot.img from the device (mediatek devices are a bit different to Snapdragon devices)
I'm going to do it today but I had to bring my daughter to the hospital after a fall she had which required stitches.
Once I have it extracted I might write a guide on how to do it with links to all firmware needed and have a thread where we will have both the stock and magisk patched boot.img's available.
Been like 6 weeks and no root on my device, this is the longest I have went without rooting in almost 7 years
garylawwd said:
You can't extract from the firmware. You must use spflash tool to pull the boot.img from the device (mediatek devices are a bit different to Snapdragon devices)
I'm going to do it today but I had to bring my daughter to the hospital after a fall she had which required stitches.
Once I have it extracted I might write a guide on how to do it with links to all firmware needed and have a thread where we will have both the stock and magisk patched boot.img's available.
Been like 6 weeks and no root on my device, this is the longest I have went without rooting in almost 7 years
Click to expand...
Click to collapse
Thanks. I rooted mine within a day but went too far with patching the inactive slot via Magisk and now phone is soft bricked. If you are still interested in extracting the boot image for patching then use this tool. I tried to use it to flash the payload.bin but phone still not booting. I even flashed all the extracted images manually in fastbootd. I guess the OTA file doesn't contain all the files needed to restore the device back to its factory state.
Anyone with the full firmware containing the SP Flash Scatter file please share it. You'll be saving everyone else. I bought my phone on a trip and there are no OnePlus repair centers over here so won't be using my phone until I can restore it myself
garylawwd said:
Apologies I did not realise you still needed the firmware. I have mirrored it here if you still need it May Patch Full ROM
Click to expand...
Click to collapse
Hello
Can't you upload this zip file somewhere else?
Each time download is not finished.
Riski3Run said:
Hello
Can't you upload this zip file somewhere else?
Each time download is not finished.
Click to expand...
Click to collapse
Saw you were able to fully extract the payload.bin so could you mirror the files as well..
Issue is now resolved Thanks @Riski3Run and @garylawwd
Alternatively extracting and flashing the payload.bin ALSO works. No need to extract the images just use this beautiful tool
garylawwd said:
Apologies I did not realise you still needed the firmware. I have mirrored it here if you still need it May Patch Full ROM
Click to expand...
Click to collapse
Hi Garylawwd, when I click on the link it displays an empty folder. Can you perhaps reupload the firmware? My device is bricked and I'm unable to find the stock rom and scatter file for CPH2399 :/
woodiewood3 said:
Hi Garylawwd, when I click on the link it displays an empty folder. Can you perhaps reupload the firmware? My device is bricked and I'm unable to find the stock rom and scatter file for CPH2399 :/
Click to expand...
Click to collapse
Were you on the latest June security patch?
garylawwd said:
Were you on the latest June security patch?
Click to expand...
Click to collapse
Yes I was on the June patch, but I completely messed up my Phone.. can't boot into recovery or fastboot, screen stays black.
When I plug in the phone my computer recognizes it as Mediatek usb port.
When I try to use mtk_gui it is able to connect but it freezes after DA extension and thus I'm unable to read or write anything from or to the device via mtk_gui.
I hope that I can flash the stock firmware via SP flash tool, otherwise I will probably need to send it to OP repairs centre.
But to flash via SP flash tool I do need the firmware + scatter file. ATM I'm unable to find them.
I am unable to create the scatter file via MTKDroid it says --- Unknown ROM structure, backup NOT possible!