Hello,
I'm planing to test Magisk for a temporary Root on device.
Can I test a patched_boot.img with "fastboot boot patched_boot.img" CMD.
Will the result be the same as if I directly flash with "fastboot flash boot /path/to/patched_boot.img" CMD until I restart my device ?
As I hope, Is there less risk with this method ?
No. You can't boot a boot image the same way you can with a recovery image.
The nature of Magisk makes it very safe though. The only modification to your device is the boot image, so if anything goes wrong you can simply flash the stock boot image (a compressed copy is saved in /data) or dirty flash your ROM.
Actually, In 5.1 I was able to gain temporary root or test my magisk patched boot.img. upon reboot magisk manager did not detect magisk install. I now pan to test disabling dm-verity in this same manner. I hope this helped.
Prerequisites :
Running Stock OOS
Unlocked Bootloader
Fastboot
Disclaimer : I am not responsible for any damage to your device.
Click to expand...
Click to collapse
Download : [ALL VARIANTS]
OOS Patched Boot Images (Credits : @Bradl79 for maintaining the folder)
9.5.4 Boot Images :
OOS 9.5.4 Patched [EU Version/1913]
OOS 9.5.4 Patched [Global | Indian Version /1917 | 1911]
Want To Maintain Root On New OTAs?:
#171
Patched Boot Image Not Available For Your Model Yet? :
#6
Instructions :
Download the patched boot image
Install the latest version of Magisk Manager
Reboot the phone in fastboot mode
Use the following command via command prompt :
Code:
fastboot flash boot boot_patched.img
fastboot reboot
The phone will reboot into system, this may take some time be patient
Open Magisk & Install it again[Direct Install]
You've got a rooted OnePlus 7 Pro.
Credits :
gururoop (Stock Firmware)
b1czu (Instructions)
Regards,
acervenky
Included the stock as well as patched image.
Link to repository : Github
Regards,
acervenky
Reserved 2
Am Trying To Port OnePlus 6T TWRP Recovery. Just Got My Hands On The Stock Recovery. Will Update If It Works
acervenky said:
It seems that the size difference is vast, so I would request one of you to download the stock boot.img from the repository, patch it and rechceck the file size.
You can try the patched boot.img and inform whether it works, for any issues/help PM me.
Link to repository : Github
Regards,
acervenky
Click to expand...
Click to collapse
I am upgrading the firmware to 9.5.3 right now. As soon as it finishes, I would try and report back
EDIT : The patched boot image on my phone is 56.32 MB so yes there is substantial size difference. Let me try booting from it
You can also patch the boot.img yourself.
Here is how:
.) Download latest Stock OOS
.) Extract boot.img using payload.bin dumper (needs python)
.) Install Magisk Manager on your device
.) Copy boot.img to your device
.) Patch boot.img using Magisk Manager
.) Copy patched boot.img to your pc, reboot your phone to fastmode and use 'fastboot boot patched_boot.img' to boot from patches bootimage.
.) Run Magisk Manager, choose direct install
-> Voila, you have a rooted OP7pro.
Kingmohdarif said:
Am Trying To Port OnePlus 6T TWRP Recovery. Just Got My Hands On The Stock Recovery. Will Update If It Works
Click to expand...
Click to collapse
zanderzone said:
I am upgrading the firmware to 9.5.3 right now. As soon as it finishes, I would try and report back
EDIT : The patched boot image on my phone is 56.32 MB so yes there is substantial size difference. Let me try booting from it
Click to expand...
Click to collapse
Please post the screenshots if you guys have successfully rooted, will update the OP accordingly
GoodSoul said:
You can also patch the boot.img yourself.
Here is how:
.) Download latest Stock OOS
.) Extract boot.img using payload.bin extractor (needs python)
.) Install Magisk Manager on your device
.) Copy boot.img to your device
.) Patch boot.img using Magisk Manager
.) Copy patched boot.img to your pc, reboot your phone to fastmode and use 'fastboot boot patched_boot.img' to boot from patches bootimage.
.) Run Magisk Manager, choose direct install
-> Voila, you have a rooted OP7pro.
Click to expand...
Click to collapse
Yes if you're on another version of OOS, this method works
Regards,
acervenky
acervenky said:
Download: OOS 9.5.3 Patched
Click to expand...
Click to collapse
Your patched boot.img is about 56mb in size while my extracted boot.img is 100mb in size. There might be something wrong with your boot.img ...
zanderzone said:
EDIT : The patched boot image on my phone is 56.32 MB so yes there is substantial size difference. Let me try booting from it
Click to expand...
Click to collapse
Did it work?
GoodSoul said:
Your patched boot.img is about 56mb in size while my extracted boot.img is 100mb in size. There might be something wrong with your boot.img ...
Did it work?
Click to expand...
Click to collapse
That extra 44mb is most likely empty space, which patching with Magisk removes like on other devices.
bmg1001 said:
That extra 44mb is most likely empty space, which patching with Magisk removes like on other devices.
Click to expand...
Click to collapse
You might be right since after 56% of the file everything is just blank.
GoodSoul said:
You might be right since after 56% of the file everything is just blank.
Click to expand...
Click to collapse
Same thing happens on the Essential Phone. Extracting the image with dd gives you a ~60mb boot image but Magisk brings it down to 23mb.
bmg1001 said:
Same thing happens on the Essential Phone. Extracting the image with dd gives you a ~60mb boot image but Magisk brings it down to 23mb.
Click to expand...
Click to collapse
Well then the patched image should work without any problems, and others who want to root with TWRP there's an unofficial version out as well
Regards,
acervenky
Thanks for the patched boot.img but this command did not work for me
Code:
fastboot boot patched_boot.img
For me this has worked
1. Install Magisk Manager
2.. Reboot device to bootloader
3.. open cmd at the location of the extracted patched_boot.img
4.. In cmd type
Code:
fastboot flash boot_a patched_boot.img
5.. In cmd type
Code:
fastboot flash boot_b patched_boot.img
6.. In cmd type
Code:
fastboot reboot
7.. Open Magisk Manager, it will prompt you with additional files are needed to complete Magisk install, go ahead and download the files.
8. After a few seconds, install will be complete and you will be rooted!
b0uNz said:
Thanks for the patched boot.img but this command did not work for me
Code:
fastboot boot patched_boot.img
For me this has worked
1. Install Magisk Manager
2.. Reboot device to bootloader
3.. open cmd at the location of the extracted patched_boot.img
4.. In cmd type
Code:
fastboot flash boot_a patched_boot.img
5.. In cmd type
Code:
fastboot flash boot_b patched_boot.img
6.. In cmd type
Code:
fastboot reboot
7.. Open Magisk Manager, it will prompt you with additional files are needed to complete Magisk install, go ahead and download the files.
8. After a few seconds, install will be complete and you will be rooted!
Click to expand...
Click to collapse
Hey man
Thanks for this, your commands worked but unfortunately I messed up my phone. Kinda new to rooting. Just realized I was on 9.5.4 on a GM1913. The patched boot image on here for 9.5.3 broke my wifi and the settings app completely unstable, it crashes constantly.
Not sure if the problem was that I used the boot image for 9.5.3 on 9.5.4 or because the patched boot image on here was intendend for other versions of the OP7P and not the European GM1913.
Does anyone have a flashable zip for the GM1913? Alternatively a stock or patched boot image intended for 9.5.4 GM1913? Any help would be much appreciated, still no OP7 here https://www.oneplus.com/support/softwareupgrade so I am stuck with a non working phone
b0uNz said:
Thanks for the patched boot.img but this command did not work for me
Code:
fastboot boot patched_boot.img
Click to expand...
Click to collapse
What error did you got when you tried that command? Did you oem unlock first and enabled usb debugging?
@acervenky @b0uNz @GoodSoul
Unlike older OnePlus phones, the current bootloader of the OnePlus 7 Pro doesn't allow 'fastboot boot' (also known as tethered booting) command. The situation is same as Essential PH-1 as well some other phones.
You will get something like the following:
Code:
downloading 'boot.img'...
OKAY [ 1.215s]
booting...
FAILED (remote: unknown command)
Titokhan said:
@acervenky @b0uNz @GoodSoul
Unlike older OnePlus phones, the current bootloader of the OnePlus 7 Pro doesn't allow 'fastboot boot' (also known as tethered booting) command. The situation is same as Essential PH-1 as well some other phones.
You will get something like the following:
Code:
downloading 'boot.img'...
OKAY [ 1.215s]
booting...
FAILED (remote: unknown command)
Click to expand...
Click to collapse
Yep, that's the same error I got initially. Do you have any idea as to what went wrong with my phone?
I am wondering if I messed up because I flashed the patched boot.img for 9.5.3 while being on 9.5.4, or if it's because it was for the wrong version, I have a GM1913.
Are boot images unique for each model, like GM1913, GM1917 etc?
Titokhan said:
@acervenky @b0uNz @GoodSoul
Unlike older OnePlus phones, the current bootloader of the OnePlus 7 Pro doesn't allow 'fastboot boot' (also known as tethered booting) command. The situation is same as Essential PH-1 as well some other phones.
You will get something like the following:
Code:
downloading 'boot.img'...
OKAY [ 1.215s]
booting...
FAILED (remote: unknown command)
Click to expand...
Click to collapse
Thanks for reporting, I'll update the OP accordingly.
Regards,
acervenky
Hey guys, for anyone that has OOS 9.5.4. Here is a patched boot image for it! https://www.androidfilehost.com/?fid=1395089523397968832
mingo_mgx said:
Hey guys, for anyone that has OOS 9.5.4. Here is a patched boot image for it! https://www.androidfilehost.com/?fid=1395089523397968832
Click to expand...
Click to collapse
Hey man, thank you! :good::good: You might have just saved my day. Quick question before I flash it though, is this for the GM1913 or GM1917?
---------- Post added at 10:12 PM ---------- Previous post was at 10:03 PM ----------
mingo_mgx said:
Hey guys, for anyone that has OOS 9.5.4. Here is a patched boot image for it! https://www.androidfilehost.com/?fid=1395089523397968832
Click to expand...
Click to collapse
Never mind, I couldn't wait so I tried it and my phone is fixed! I am rooted and wifi and the settings are working again. Thank you so much.
@acervenky, could you add the 9.5.4 boot image to the OP? Just to avoid any other noobs like myself messing up their brand new phone like I did with the wrong boot image..
Also does anyone know if boot images are specific to different models? Are they different on GM1913, 1915, 1917 etc? Would be good to mention that in the OP too if so.
Hello everyone,
So this is the first time i had issue with magisk after the update.
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager then installing that zip - also from Magisk Manager, but it would say this:
Code:
- Device platform: arm64-v8a
- Existing zip found
- Copying image to cache
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
So now i don't know what do to.
I did notice however, that after the Magisk update, it seem to have installed newest OTA update (with security patches from May), which usually it fails to install, i guess due to unlocked bootloader.
Any help would be greatly appreciated!
EDIT:
Managed to figure it out, it's been a long time since I've done this so i forgot that method I've tried is used to patch boot image, not to install zip file, my bad.
I booted into TWRP and extracted my current boot.img.
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Booted back into the system and *BAM*, got my root back!
Magisk is still the best! Thank you!
maretodoric said:
Hello everyone,
So this is the first time i had issue with magisk after the update.
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager then installing that zip - also from Magisk Manager, but it would say this:
So now i don't know what do to.
I did notice however, that after the Magisk update, it seem to have installed newest OTA update (with security patches from May), which usually it fails to install, i guess due to unlocked bootloader.
Any help would be greatly appreciated!
EDIT:
Managed to figure it out, it's been a long time since I've done this so i forgot that method I've tried is used to patch boot image, not to install zip file, my bad.
I booted into TWRP and extracted my current boot.img.
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Booted back into the system and *BAM*, got my root back!
Magisk is still the best! Thank you!
Click to expand...
Click to collapse
I'm also getting same error how did you managed to find the solution...
maretodoric said:
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager.
[...]
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Click to expand...
Click to collapse
Similar problem here, but with Magisk 19.3.
Could you pass a link to patched boot image,you used? Can´t find it...
Thanks
I didn't download boot.img, it's best that you extract it yourself by using ADB.
Download adb software, there should be some tutorial here on forums how to find and get it (possibly https://forum.xda-developers.com/mi-a1/how-to/computer-setup-rooting-gcam-setup-t3731526) , but Windows 10 SHOULD natively have it (at least i did, i didn't have to install anything, already had ADB).
Now here comes the tricky part. I didn't remember this and i didn't write it down. When this happens again to me, i will be in huge .......
I'm sorry i can't help you, but try to google for info on how to extract boot.img from current installation using fastboot or adb.. not sure which, possibly fastboot.
Then you will have clean untouched boot.img from official repo. No need to wait for it to appear on xiaomi site.
If i find a tutorial, i will post it here. Please do the same if you find it before me.
GOT IT!!!
- Follow the previous tutorial if you do not have adb and fastboot, so you can install them. There should be plenty of tutorials how to install both of them
- After you installed it, download this version of TWRP https://dl.twrp.me/tissot/twrp-3.3.0-2-tissot.img.html to your desktop
- Connect your phone to your PC via USB cable
- Open command prompt (in Windows, hit CTRL+R then type in cmd)
- Change directory to desktop, for example type cd C:\Users\<username>\Desktop - replace "<username>" with your username ofcourse.
- Type adb reboot bootloader - it will boot to fastboot mode
- Once the phone is in fastboot mode, type fastboot boot twrp-3.3.0-2-tissot.img (keep cmd prompt open)
- It will boot into recovery, click on "Backup"
- Select "Boot"
- Click on Select Storage and there choose Internal Storage, click on OK
- Then on the bottom part of the screen, just swipe to right to extract boot.img (It should literally say "Swipe to Backup"). Pay attention to messages, it will display the directory where it will place the boot.img, but it will not be strictly named boot.img
- In my case, it's in Internal Storage/TWRP/BACKUPS/00bf23cc0904/2019-06-20-14-25-3_PKQ1/boot.emmc.win
You can either rename it to boot.img or just leave that name. But either way, open new magisk manager, select "Install" next to Magisk (not magisk manager), click on "Select and Patch a file", point to your new boot.img or boot.emmc.win.
Magisk will patch that image and show you the new location. Just download that file to your PC, on desktop, cmd again "adb reboot bootloader", and when it gets to fastboot mode, type "fastboot flash boot magisk_patched.img".
You should be good to go!
Hi, I have unlock the boot loader and root my pixel 4a 5g in february update.
I don't understand how update it when new update comes ?
I can update it with Ota when comes in settings/System/Update ?
Or I do flash system image with fastboot and then flash the boot.img with Magisk to flash it in Fastboot mode ?
But I see : Flashing a new system image deletes all user data !!?
Before on Oneplus and later Xiaomi is more easy with Twrp. But now it's very complicated to update my freshly updated Pixel 4a 5g and Root
Please that it is the easiest procedure to update every month with Magisk installed. Previously I stopped all the Mods installed so as not to have a similar bootloop for Substartum .. Thank you
Thanks
Here's what I do:
- Download full factory image
- Unzip the archive
- There will be flash-all.bat (for Windows) and flash-all.sh (Linux) files created. You will need to edit the appropriate file to remove the -w flag on the "fastboot -w update image-bramble-rq1c.210205.006.zip" command near the bottom of the script.
- Within the archive you just unzipped, a directory will be created i.e. bramble-rq1c.210205.006 and within that there will be another zip file i.e. image-bramble-rq1c.210205.006. This zip file also needs to be uncompressed to extract the individual .img files including boot.img.
- Copy boot.img to your phone (Download directory is a good place)
- Flash the update using the edited flash-all script
- Once flashing is complete and the phone has rebooted, go into Magisk Manager and Install Magisk using the "select and patch a file" method. Navigate to the Downloads directory and select boot.img. Once complete, there will be a patched boot image named something like magisk_patched_bEKaK.img created in the Download directory. Copy that file back to your PC and then use fastboot to flash it to your phone i.e. "fastboot flash boot magisk_patched_bEKaK.img".
- Reboot phone and profit!
weissbierdood said:
Here's what I do:
- Download full factory image
- Unzip the archive
- There will be flash-all.bat (for Windows) and flash-all.sh (Linux) files created. You will need to edit the appropriate file to remove the -w flag on the "fastboot -w update image-bramble-rq1c.210205.006.zip" command near the bottom of the script.
- Within the archive you just unzipped, a directory will be created i.e. bramble-rq1c.210205.006 and within that there will be another zip file i.e. image-bramble-rq1c.210205.006. This zip file also needs to be uncompressed to extract the individual .img files including boot.img.
- Copy boot.img to your phone (Download directory is a good place)
- Flash the update using the edited flash-all script
- Once flashing is complete and the phone has rebooted, go into Magisk Manager and Install Magisk using the "select and patch a file" method. Navigate to the Downloads directory and select boot.img. Once complete, there will be a patched boot image named something like magisk_patched_bEKaK.img created in the Download directory. Copy that file back to your PC and then use fastboot to flash it to your phone i.e. "fastboot flash boot magisk_patched_bEKaK.img".
- Reboot phone and profit!
Click to expand...
Click to collapse
Thank you very much.
Have a good day..
I have now the good procedure to update it. Thanks