Related
I installed Magisk Manager 5.3.0 and opened it and clicked on Install to download Magisk 14 and to patch the boot.img file that I got from the Samsung Firmware file.
I patched the file and that completed fine with no errors.
I then copied the patched boot.img file to my computer so I could run ODIN on to flash it. Its in the proper format, "magisk.img.tar" is that I called it.
I opened ODIN 3.12 and selected the file under BL and plugged my phone in while in Download Mode.
ODIN detected my phone with the Added! msg in the log window.
ODIN is still running as I type this and all that is in the log is the following:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
Theres no change on the phone screen either.
OEM Unlock is enabled as on the phone screen it says FRP Lock: Off
Phone is a Samsung Galaxy J3 Emerge (J327P) with Boost Mobile
Samsung firmware file from SAMMOBILE is J327PVPU1AQF4_J327PSPT1AQF4_BST
John877 said:
I installed Magisk Manager 5.3.0 and opened it and clicked on Install to download Magisk 14 and to patch the boot.img file that I got from the Samsung Firmware file.
I patched the file and that completed fine with no errors.
I then copied the patched boot.img file to my computer so I could run ODIN on to flash it. Its in the proper format, "magisk.img.tar" is that I called it.
I opened ODIN 3.12 and selected the file under BL and plugged my phone in while in Download Mode.
ODIN detected my phone with the Added! msg in the log window.
ODIN is still running as I type this and all that is in the log is the following:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
Theres no change on the phone screen either.
OEM Unlock is enabled as on the phone screen it says FRP Lock: Off
Phone is a Samsung Galaxy J3 Emerge (J327P) with Boost Mobile
Samsung firmware file from SAMMOBILE is J327PVPU1AQF4_J327PSPT1AQF4_BST
Click to expand...
Click to collapse
It has to be added in AP not BL.
I did the same and I tried to flash it in odin in AP but odin crushes!!
My phone is Galaxy S7 edge
Hani88 said:
I did the same and I tried to flash it in odin in AP but odin crushes!!
My phone is Galaxy S7 edge
Click to expand...
Click to collapse
Can you by any chance send me the boot-image, stock, patched, tared ?
Or do you have the possibility to untar the image (or create just the boot.img) and use a "real" gnu-tar (preferred on linux).
Or give me the exact firmware, so I can try to create the image and tar it with the tar on my Fedora system ?
When doing the (internal) beta-tests I had the same issue, because of incorrect tar-headers (gnu-tar does not care about it). That should be fixed in MagiskManager, but Odin seems to be extremely nitpicking about the tar-header.
It might also be a problem with signed (or better not signed) bot-image, but I guess this would lead to another error.
jenslody said:
Can you by any chance send me the boot-image, stock, patched, tared ?
Or do you have the possibility to untar the image (or create just the boot.img) and use a "real" gnu-tar (preferred on linux).
Or give me the exact firmware, so I can try to create the image and tar it with the tar on my Fedora system ?
When doing the (internal) beta-tests I had the same issue, because of incorrect tar-headers (gnu-tar does not care about it). That should be fixed in MagiskManager, but Odin seems to be extremely nitpicking about the tar-header.
It might also be a problem with signed (or better not signed) bot-image, but I guess this would lead to another error.
Click to expand...
Click to collapse
Well for me I only know how to extract the boot.img file from the AP file using winrar and patching it using magisk then renaming to .img.tar
I don't know anything about gnu-tar linux
Hani88 said:
Well for me I only know how to extract the boot.img file from the AP file using winrar and patching it using magisk then renaming to .img.tar
I don't know anything about gnu-tar linux
Click to expand...
Click to collapse
Can you give me the exact version of your rom, so I can download it and send you a patched image for testing ? Or send me the boot.img either patched, stock or patched and tared ?
Hani88 said:
Well for me I only know how to extract the boot.img file from the AP file using winrar and patching it using magisk then renaming to .img.tar
I don't know anything about gnu-tar linux
Click to expand...
Click to collapse
Well, if that's what you did, no wonder why it's failing and Odin is stuck on analyzing the image—it's not in the proper format, you shouldn't rename it, you need to tar the boot.img file.
jenslody said:
Can you give me the exact version of your rom, so I can download it and send you a patched image for testing ? Or send me the boot.img either patched, stock or patched and tared ?
Click to expand...
Click to collapse
It is
GF935FXXS1DQHM
I downloaded it from samfirm
I can send you the boot.img tomorrow because my laptop is not with me
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
白い熊 said:
Well, if that's what you did, no wonder why it's failing and Odin is stuck on analyzing the image—it's not in the proper format, you shouldn't rename it, you need to tar the boot.img file.
Click to expand...
Click to collapse
Now I understand because inside it also there is not "meta inf " folder. How to tar it ?
Hani88 said:
It is
GF935FXXS1DQHM
I downloaded it from samfirm
I can send you the boot.img tomorrow because my laptop is not with me
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
Now I understand because inside it also there is not "meta inf " folder. How to tar it ?
Click to expand...
Click to collapse
In MagiskManager's settings chose the .img.tar output format. The patched image should be named "patched_boot.img.tar", if it's just "patched_boot.img" you can not directly flash it!
jenslody said:
In MagiskManager's settings chose the .img.tar output format. The patched image should be named "patched_boot.img.tar", if it's just "patched_boot.img" you can not directly flash it!
Click to expand...
Click to collapse
But in odin in AP I am not able to import img file
Hani88 said:
But in odin in AP I am not able to import img file
Click to expand...
Click to collapse
That's why you have to chose the correct patch-format in MagiskManager's settings before patching the stock boot.img .
In the settings click/touch "Patch Boot Output Format" and chose ".img.tar", then in the main menu click/touch "Install", then again "Install", then "Patch Boot Image File", chose the stock-image and wait until it is patched.
This should create a file named "patched_boot.img.tar" in the MagiskManager-folder of your internal storage.
This should be flashable.
Changing just the ending of any file does not change the format and can not work therefore.
jenslody said:
That's why you have to chose the correct patch-format in MagiskManager's settings before patching the stock boot.img .
In the settings click/touch "Patch Boot Output Format" and chose ".img.tar", then in the main menu click/touch "Install", then again "Install", then "Patch Boot Image File", chose the stock-image and wait until it is patched.
This should create a file named "patched_boot.img.tar" in the MagiskManager-folder of your internal storage.
This should be flashable.
Changing just the ending of any file does not change the format and can not work therefore.
Click to expand...
Click to collapse
Thanks for the explanation.. I will do it tomorrow
Flashing a patched boot image will trip the knox counter right ? Of course mine is tripped but I want to know that
@jenslody I have just tried flashing the patched boot.img file in ODIN under the AP/PDA field and depending on ODIN version it either crashes or is stuck at file analysis. I have named the file "magisk" to keep the filename short. Therefore the full filename is magisk.img.tar. It was created using the patcher in magisk manager with the output setting of img.tar. I prefer to flash it in ODIN as I would like to keep the stock recovery for the sake of future updates.
How I obtained the boot.img file is from opening the stock firmware image from SAMMOBILE and extracting the AP file and grabbing the boot.img. I also grabbed the recovery.img this way just to have it. I dont have access to any other way of extracting the files as I dont have or use linux personally so its my windows 10 computer only.
As you offered the other guy above I am including my stock extracted boot.img file as well as my exact firmware version on SAMMOBILE.
The exact firmware filename is: J327PVPU1AQF4_J327PSPT1AQF4_BST
Its the Samsung Galaxy J3 Emerge (2017) from Boost Mobile (J327P) with Baseband version ending in QF4. Its on Android 6.0.1.
I was unable to attach the boot.img file here cause its too big (11.7mb) and the upload failed when I tried to ZIP it instead cause the limit there is 20mb. So here it is on DropBox instead.
https://dl.dropboxusercontent.com/s/azyeqrx7rtvjvik/boot.img
Once again the is extracted directly from the firmware file with winrar with no magisk patching.
John877 said:
@jenslody I have just tried flashing the patched boot.img file in ODIN under the AP/PDA field and depending on ODIN version it either crashes or is stuck at file analysis. I have named the file "magisk" to keep the filename short. Therefore the full filename is magisk.img.tar. It was created using the patcher in magisk manager with the output setting of img.tar. I prefer to flash it in ODIN as I would like to keep the stock recovery for the sake of future updates.
How I obtained the boot.img file is from opening the stock firmware image from SAMMOBILE and extracting the AP file and grabbing the boot.img. I also grabbed the recovery.img this way just to have it. I dont have access to any other way of extracting the files as I dont have or use linux personally so its my windows 10 computer only.
As you offered the other guy above I am including my stock extracted boot.img file as well as my exact firmware version on SAMMOBILE.
The exact firmware filename is: J327PVPU1AQF4_J327PSPT1AQF4_BST
Its the Samsung Galaxy J3 Emerge (2017) from Boost Mobile (J327P) with Baseband version ending in QF4. Its on Android 6.0.1.
I was unable to attach the boot.img file here cause its too big (11.7mb) and the upload failed when I tried to ZIP it instead cause the limit there is 20mb. So here it is on DropBox instead.
https://dl.dropboxusercontent.com/s/azyeqrx7rtvjvik/boot.img
Once again the is extracted directly from the firmware file with winrar with no magisk patching.
Click to expand...
Click to collapse
This should work, unless your ODIN-version stumbles about other things than mine.
Nevertheless, I uploaded a patched version of your boot.img to my server: https://rpm.jenslody.de/magisk/J327PVPU1AQF4_patched_boot.img.tar .
It's tared with the tar from my Fedora-system, but the (tar-header related) fixes @topjohnwu made to the java-tar he uses in MagiskManager made the created image flashable on my J5 (latest stock).
I also added a tared image with md5-checksum for you to test: https://rpm.jenslody.de/magisk/J327PVPU1AQF4_patched_boot.img.tar.md5
jenslody said:
This should work, unless your ODIN-version stumbles about other things than mine.
Nevertheless, I uploaded a patched version of your boot.img to my server: https://rpm.jenslody.de/magisk/J327PVPU1AQF4_patched_boot.img.tar .
It's tared with the tar from my Fedora-system, but the (tar-header related) fixes @topjohnwu made to the java-tar he uses in MagiskManager made the created image flashable on my J5 (latest stock).
I also added a tared image with md5-checksum for you to test: https://rpm.jenslody.de/magisk/J327PVPU1AQF4_patched_boot.img.tar.md5
Click to expand...
Click to collapse
@jenslody, just for me to understand—you get the patched version via Magisk Manager, then untar it, then tar it again with a custom built tar?
Where are the patches you mention?
I think I realized my mistake. I extracted the boot.img file from the AP file of the firmware then not realizing it has to be inside a tar archive file I just renamed the boot.img file boot.img.tar instead. I feel like kind of an idiot right now.
Would it be sufficient to just use 7zip to create a tar archive with the boot.img file inside it?
Also would this be how to flash the recovery.img file too if I flash TWRP and want to go back to the stock recovery?
白い熊 said:
@jenslody, just for me to understand—you get the patched version via Magisk Manager, then untar it, then tar it again with a custom built tar?
Where are the patches you mention?
Click to expand...
Click to collapse
I used the stock boot for J3, patched it through MagiskManager (one as *.img, one as *.img.tar), renamed the patched_boot.img to boot.img (taht's what Odin expects inside the tar, used Fedora's tar (I'm on Fedora 26) to create a tar archive from it and just for testing added a md5-checksum to one version of it.
MagiskManager is the 5.30 released with/for Magisk 14.4, bot patched. The fixes I mention were made by @topjohnwu in the (internal) beta-testing for 14.4.
To be clear:
the released Magisk with MagiskManager create img.tar-files that work for my J5 with the Odin-version I use (Odin3 v3.10.7) without any tweaking.
My self-tared versions are for testing purposes, to see if other Odin versions are more nitpicking than mine (about tar-headers). The included boot.img is exactly (binary) the same.
John877 said:
I think I realized my mistake. I extracted the boot.img file from the AP file of the firmware then not realizing it has to be inside a tar archive file I just renamed the boot.img file boot.img.tar instead. I feel like kind of an idiot right now.
Would it be sufficient to just use 7zip to create a tar archive with the boot.img file inside it?
Also would this be how to flash the recovery.img file too if I flash TWRP and want to go back to the stock recovery?
Click to expand...
Click to collapse
Same question here.. and you are not the only one who's feeling like an idiot now
---------- Post added at 09:23 AM ---------- Previous post was at 09:02 AM ----------
jenslody said:
Can you by any chance send me the boot-image, stock, patched, tared ?
Click to expand...
Click to collapse
here is it thanks for helping
https://drive.google.com/file/d/0B9_cANW46As_Y2Jwa0xsR1p2UkE
John877 said:
I think I realized my mistake. I extracted the boot.img file from the AP file of the firmware then not realizing it has to be inside a tar archive file I just renamed the boot.img file boot.img.tar instead. I feel like kind of an idiot right now. [emoji14]
Would it be sufficient to just use 7zip to create a tar archive with the boot.img file inside it?
Click to expand...
Click to collapse
It's unnecessary, you should just select .img.tar as the output format in Magisk Manager's settings. Then you can use the .img file you've extracted from the stock firmware. Magisk Manager will patch the .img file and create a patched .img.tar
This you should be able to flash with Odin.
白い熊 said:
It's unnecessary, you should just select .img.tar as the output format in Magisk Manager's settings. Then you can use the .img file you've extracted from the stock firmware. Magisk Manager will patch the .img file and create a patched .img.tar
This you should be able to flash with Odin.
Click to expand...
Click to collapse
When I extracted the boot.img file from the firmware it was boot.img. When I patched it from magisk manager, it was boot.img still even though I chose output format img.tar.
Anyone noticed that can't root with magisk the p20 pro or it just me?
Yes! There is a way to extract the boot image, use Magisk to patch it, then flash that boot image via fastboot. I'm actually waiting for someone with experience to advise on these items:
1. Can I extract the boot image from my phone directly? If so, can someone point me in the direction of the software to do so?
2. If I can't extract directly, do I need to use the update file from Firmware Finder that matches my current firmware exactly? I'm running B155, but there seems to be slight variations in the naming for some of the available firmware.
3. After I get all of this completed successfully, how do I verify that the image is good to use to avoid bricking the phone?
Thanks in advance to anyone that could help!
sarichter said:
Yes! There is a way to extract the boot image, use Magisk to patch it, then flash that boot image via fastboot. I'm actually waiting for someone with experience to advise on these items:
1. Can I extract the boot image from my phone directly? If so, can someone point me in the direction of the software to do so?
2. If I can't extract directly, do I need to use the update file from Firmware Finder that matches my current firmware exactly? I'm running B155, but there seems to be slight variations in the naming for some of the available firmware.
3. After I get all of this completed successfully, how do I verify that the image is good to use to avoid bricking the phone?
Thanks in advance to anyone that could help!
Click to expand...
Click to collapse
This guide has everything you should need. https://topjohnwu.github.io/Magisk/install.html
1. No, unless rooted
2. Find either the same FW you are on, or extract from a OTA.
3. Not sure on that one, it's always worked for me.
purple patch said:
This guide has everything you should need. https://topjohnwu.github.io/Magisk/install.html
1. No, unless rooted
2. Find either the same FW you are on, or extract from a OTA.
3. Not sure on that one, it's always worked for me.
Click to expand...
Click to collapse
Thank you so much! Do you have any idea where I can get the OTA or at least figure out in specificity which OTA on Firmware Finder is correct? It sounds like it needs to be 100% exact to avoid issues / bricking.
---------- Post added at 03:12 PM ---------- Previous post was at 02:18 PM ----------
purple patch said:
This guide has everything you should need. https://topjohnwu.github.io/Magisk/install.html
1. No, unless rooted
2. Find either the same FW you are on, or extract from a OTA.
3. Not sure on that one, it's always worked for me.
Click to expand...
Click to collapse
OK... so I was able to extract the RAMDISK.IMG file but I can't patch it because Magisk Manager hangs after I install it. Is there a way to patch the RAMDISK.IMG file manually or via PC?
OK... so if anyone who is having trouble rooting... this is what I did to get root.
1. Be sure to download the firmware you are CURRENTLY on to avoid any possible issues.
2. Extract the RAMDISK.img file from the post above: https://topjohnwu.github.io/Magisk/install.html
3. Obtain a previously patched RAMDISK file to get an initial Magisk install on your phone first. There is one on XDA floating around named CLT-29-MAGISK.img.
4. Boot into FASTBOOT and then get to a CMD window with your ADB tools and use the command "fastboot flash ramdisk CLT-29-MAGSIK.img"
5. Reboot the phone and download Magisk Manager 5.5.5.
6. After installing Magisk Manager 5.5.5, install the next two upgraded versions while INSIDE Magisk Manager until you get to 7.1.x.x.
7. Click INSTALL on the Magisk option and let Magisk Manager patch your freshly extracted RAMDISK.img file from Step 2.
8. Copy that RAMDISK.img file to your PC.
9. Boot into FASTBOOT and then get to a CMD window with your ADB tools and use the command "fastboot flash ramdisk patched_boot.img"
10. Reboot and you'll have root!
sarichter said:
OK... so if anyone who is having trouble rooting... this is what I did to get root.
1. Be sure to download the firmware you are CURRENTLY on to avoid any possible issues.
2. Extract the RAMDISK.img file from the post above: https://topjohnwu.github.io/Magisk/install.html
3. Obtain a previously patched RAMDISK file to get an initial Magisk install on your phone first. There is one on XDA floating around named CLT-29-MAGISK.img.
4. Boot into FASTBOOT and then get to a CMD window with your ADB tools and use the command "fastboot flash ramdisk CLT-29-MAGSIK.img"
5. Reboot the phone and download Magisk Manager 5.5.5.
6. After installing Magisk Manager 5.5.5, install the next two upgraded versions while INSIDE Magisk Manager until you get to 7.1.x.x.
7. Click INSTALL on the Magisk option and let Magisk Manager patch your freshly extracted RAMDISK.img file from Step 2.
8. Copy that RAMDISK.img file to your PC.
9. Boot into FASTBOOT and then get to a CMD window with your ADB tools and use the command "fastboot flash ramdisk patched_boot.img"
10. Reboot and you'll have root!
Click to expand...
Click to collapse
Not sure why people struggle with this. The guy who started this thread has a copypasta guide he posted and could have followed. You should post your post in guide section for others I guess.
purple patch said:
Not sure why people struggle with this. The guy who started this thread has a copypasta guide he posted and could have followed. You should post your post in guide section for others I guess.
Click to expand...
Click to collapse
People struggle because the firmware is from 100 different regions, all with different release dates, there is no official TWRP that works 100% correctly with encryption, and Magisk changed the standard install method. I'm not surprised that people are having a tough time figuring out what to do so they don't brick their phone. This thing isn't cheap!
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.
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
Hello guys. I failed several times rooting this device and finally managed to root.
You need to extract AP tar and then replace the boot.img with a magisk patched one.
You then need to re tar the file using 7zip and flash as normal.
AP CSC HOME CSC and BL
If there's enough demand I'll write a proper guide. Also if soft bricked you need to press both volume buttons and plug in usb at right point on restart.
jameswalker457 said:
Hello guys. I failed several times rooting this device and finally managed to root.
You need to extract AP tar and then replace the boot.img with a magisk patched one.
You then need to re tar the file using 7zip and flash as normal.
AP CSC HOME CSC and BL
Click to expand...
Click to collapse
Thanks @jameswalker457
Which one did you use CSC_HOME or CSC?
When I run with CSC, I get a 'fail' in ODIN However, it does run with CSC_HOME, BL and the patched AP - but it doesn't actually root the device.
Greatful for your help.
Thanks
Used BL AP (with patched boot.img) CSC and HOME_CSC in the userdata
kevinsims said:
Thanks @jameswalker457
Which one did you use CSC_HOME or CSC?
When I run with CSC, I get a 'fail' in ODIN However, it does run with CSC_HOME, BL and the patched AP - but it doesn't actually root the device.
Greatful for your help.
Thanks
Click to expand...
Click to collapse
See above. Missed the quotation
I'm not sure why we need a third thread for this:
SM-X200 root failed...
It's now a bricked tablet after a boot loop, I think should wait to magisk get an update. It won't power on or charge I think. I have two days trying to power on in several times and many key conbinations. No Samsung logo or something. Can I do...
forum.xda-developers.com
The best way to root samsung tab a8 2021 pls
Android 11 I got fast as f boot loop solution below btw An 4 gamers I got fps/ping boost solution below to
forum.xda-developers.com
I still do not have root. What I did:
1. unlocked bootloader
2. install magisk manager 24.3
3. Download X200XXU1AVC1 from Samfw
4. unzip the firmware
5. Untar the AP tar file
6. Extract boot.img, send to device, and patch with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
7. Replace boot.img with the newly patched one (renamed to boot.img)
8. Create a tar file from the AP folder using
" tar -C AP_folder -cvf AP_patched.tar ."
9. "adb reboot bootloader" to download mode
10. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar
9. Flash via Odin, exit download mode, enter stock recovery, factory reset
For some reason I can't get from download mode to recovery w/o first booting the fresh android.
No boot loop, but no root either.
These are the file names I got from Samfw:
AP_X200XXU1AVC1_CL23784803_QB49828201_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
BL_X200XXU1AVC1_CL23784803_QB49828201_REV00_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_OMC_XAR_X200XAR1AVC1_CL23784803_QB49838021_REV00_user_low_ship_MULTI_CERT.tar.md5
The md5sum of the files:
AP stock: fa97e5cee1deaf26175b27d26df94266
AP patched: 006b12f713fc3caa127bc5cba01ae4b9
BL: 2172ca468462a46917d78e94157aed54
HOME_CSC: 5ede57b9ffe8059f3166dd5de6ef8721
The tar file worried me. It had file names like ./boot.img instead of boot.img. So I created a new file, with the patched boot.img, this way:
cd AP_folder
tar -cvf ../AP_patched.tar *
Then flashed that. Took longer than the previous tar.
On reboot, it asks me to press PWR to accept boot loader unlocked. Then a splash screen saying: unapproved software, then a few boot loops.
I got to recovery, factory reset, the tablet does the LONG boot, does the initial setup thing.
Install Magisk Manager, and root! Google Play still works.
Whoopee! I can now wait for a working TWRP.
jameswalker457 said:
Hello guys. I failed several times rooting this device and finally managed to root.
You need to extract AP tar and then replace the boot.img with a magisk patched one.
You then need to re tar the file using 7zip and flash as normal.
AP CSC HOME CSC and BL
Click to expand...
Click to collapse
Hello, I have a problem/doubt. I have the files AP, BP... etc I use 7zip to extract the boot.img ..... if I unzip all the AP XXX.tar.md5 the 7zip warns me that there is data after the file, it warns me of an error and at the end it stops in the fota . ...when I replace the boot.img in the AP folder by the one corresponding to the patched with Magisk and use the 7zip again to create the .tar the file does not work with ODIN...I do not know what step or mistake I make. Regards
PS: I'm extracting the files instead of unzipping the .tar.md5 to see if that's the problem ....
PS: Root! Thanks Jameswalker457 Cheers! ....
Translated with www.DeepL.com/Translator (free version)
IkeGolden said:
Hello, I have a problem/doubt. I have the files AP, BP... etc I use 7zip to extract the boot.img ..... if I unzip all the AP XXX.tar.md5 the 7zip warns me that there is data after the file, it warns me of an error and at the end it stops in the fota . ...when I replace the boot.img in the AP folder by the one corresponding to the patched with Magisk and use the 7zip again to create the .tar the file does not work with ODIN...I do not know what step or mistake I make. Regards
PS: I'm extracting the files instead of unzipping the .tar.md5 to see if that's the problem ....
PS: Root! Thanks Jameswalker457 Cheers! ....
Translated with www.DeepL.com/Translator (free version)
Click to expand...
Click to collapse
> if I unzip all the AP XXX.tar.md5
That is because a .tar.md5 is a tar file with an md5 concatenated to it.
> use the 7zip again to create the .tar the file does not
The proper tool to create .tar files is "tar".
>PS: I'm extracting the files instead of unzipping the .tar.md5 to see if that's the problem ....
Care to be more specific on how you did that?
>PS: Root! Thanks Jameswalker457 Cheers! ....
Good news.
Have root my SM-X205 (LTE) for 1 Feb Patch level but no go with latest May update.
Getting constant boot loop (exactly same process, magisk boot.bin etc) so rolled back to Feb for now.
lufee84 said:
Have root my SM-X205 (LTE) for 1 Feb Patch level but no go with latest May update.
Getting constant boot loop (exactly same process, magisk boot.bin etc) so rolled back to Feb for now.
Click to expand...
Click to collapse
What firmware version worked, and which failed?
X200XXU1AVC1 worked for me.
Yes, X205XXU1AVC1 works.
No luck with latest X205XXS1AVE1 (May Patch).
garyemiller said:
I'm not sure why we need a third thread for this:
SM-X200 root failed...
It's now a bricked tablet after a boot loop, I think should wait to magisk get an update. It won't power on or charge I think. I have two days trying to power on in several times and many key conbinations. No Samsung logo or something. Can I do...
forum.xda-developers.com
The best way to root samsung tab a8 2021 pls
Android 11 I got fast as f boot loop solution below btw An 4 gamers I got fps/ping boost solution below to
forum.xda-developers.com
I still do not have root. What I did:
1. unlocked bootloader
2. install magisk manager 24.3
3. Download X200XXU1AVC1 from Samfw
4. unzip the firmware
5. Untar the AP tar file
6. Extract boot.img, send to device, and patch with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
7. Replace boot.img with the newly patched one (renamed to boot.img)
8. Create a tar file from the AP folder using
" tar -C AP_folder -cvf AP_patched.tar ."
9. "adb reboot bootloader" to download mode
10. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar
9. Flash via Odin, exit download mode, enter stock recovery, factory reset
For some reason I can't get from download mode to recovery w/o first booting the fresh android.
No boot loop, but no root either.
Click to expand...
Click to collapse
Not sure if this helps but i read an article that says you should patch the whole AP tar file rather than extract just the boot.img. Maybe because it patches the recovery and super etc img files too? I havet tried this yet as I cant even get my bootloader unlocked
dan.langridge88 said:
Not sure if this helps but i read an article that says you should patch the whole AP tar file rather than extract just the boot.img. Maybe because it patches the recovery and super etc img files too? I havet tried this yet as I cant even get my bootloader unlocked
Click to expand...
Click to collapse
Dunno where you read that, don't care. This works (as above):
1. unlocked bootloader
2. install magisk manager 24.3
3. Download X200XXU1AVC1 from Samfw
4. unzip the firmware
5. Untar the AP tar file
6. Extract boot.img, send to device, and patch with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
7. Replace boot.img with the newly patched one (renamed to boot.img)
8. Create a tar file from the AP folder using
" cd AP_folder"
" tar -cvf AP_patched.tar ."
9. "adb reboot bootloader" to download mode
10. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar
9. Flash via Odin, exit download mode, enter stock recovery, factory reset
Note the fixed "tar" command. Do not use "tar -C".
garyemiller said:
Dunno where you read that, don't care. This works (as above):
1. unlocked bootloader
2. install magisk manager 24.3
3. Download X200XXU1AVC1 from Samfw
4. unzip the firmware
5. Untar the AP tar file
6. Extract boot.img, send to device, and patch with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
7. Replace boot.img with the newly patched one (renamed to boot.img)
8. Create a tar file from the AP folder using
" cd AP_folder"
" tar -cvf AP_patched.tar ."
9. "adb reboot bootloader" to download mode
10. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar
9. Flash via Odin, exit download mode, enter stock recovery, factory reset
Note the fixed "tar" command. Do not use "tar -C".
Click to expand...
Click to collapse
OK, I've un-tarred the AP tar.md5 and patched the old boot-img file on the device, renamed it and replaced the original boot.img in the AP "folder".
Steps 8 & 9 are a little confusing for me, if you could expand on those. Can I use 7zip to re-tar? Those look like DOS commands in step 8.
Ar-Pharazon said:
OK, I've un-tarred the AP tar.md5 and patched the old boot-img file on the device, renamed it and replaced the original boot.img in the AP "folder".
Steps 8 & 9 are a little confusing for me, if you could expand on those. Can I use 7zip to re-tar? Those look like DOS commands in step 8.
Click to expand...
Click to collapse
Slightly expanded:
1. unlocked bootloader
2. install magisk manager 24.3 on the tablet
3. Download X200XXU1AVC1 firmware from Samfw onto PC
4. unzip the X200XXU1AVC1 firmware zip file
5. Make a directory for the AP tar contents
"mkdir AP"
6. Untar the AP tar file into directory AP, all on one line:
"tar -xvf AP_X200XXU1AVC1_CL23784803_QB49828201_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar.md5 -C AP"
7. Change the current directoy to the AP directory:
"cd AP"
8. Using adb send boot.img, to the tablet,.
9. Patch boot.img with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
10. Using adb copy magisk_patched-24300-9Iez2.img from the tablet and into the AP directory.
11. Rename magisk_patched-24300-9Iez2.img to boot.img:
"mv magisk_patched-24300-9Iez2.img boot.img"
12 Create a tar file from the AP directory Note the space and period(".") after ".tar":
" tar -cvf AP_patched.tar ."
13. Use adb on PC to enter download mode on tablet:
"adb reboot bootloader"
14. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar as files to be flashed.
15. Flash via Odin, exit download mode, enter stock recovery, factory reset
How about that?
garyemiller said:
Slightly expanded:
1. unlocked bootloader
2. install magisk manager 24.3 on the tablet
3. Download X200XXU1AVC1 firmware from Samfw onto PC
4. unzip the X200XXU1AVC1 firmware zip file
5. Make a directory for the AP tar contents
"mkdir AP"
6. Untar the AP tar file into directory AP, all on one line:
"tar -xvf AP_X200XXU1AVC1_CL23784803_QB49828201_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar.md5 -C AP"
7. Change the current directoy to the AP directory:
"cd AP"
8. Using adb send boot.img, to the tablet,.
9. Patch boot.img with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
10. Using adb copy magisk_patched-24300-9Iez2.img from the tablet and into the AP directory.
11. Rename magisk_patched-24300-9Iez2.img to boot.img:
"mv magisk_patched-24300-9Iez2.img boot.img"
12 Create a tar file from the AP directory Note the space and period(".") after ".tar":
" tar -cvf AP_patched.tar ."
13. Use adb on PC to enter download mode on tablet:
"adb reboot bootloader"
14. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar as files to be flashed.
15. Flash via Odin, exit download mode, enter stock recovery, factory reset
How about that?
Click to expand...
Click to collapse
I'm guessing those are Linux commands?
In any event, I made 7zip re-tar the AP folder with the patched boot.img, but it ends in .tar.tar
Is this an issue, or should/can it be renamed .tar.md5 like the original?
Ar-Pharazon said:
I'm guessing those are Linux commands?
In any event, I made 7zip re-tar the AP folder with the patched boot.img, but it ends in .tar.tar
Is this an issue, or should/can it be renamed .tar.md5 like the original?
Click to expand...
Click to collapse
I do them on Linux, but they can also work on WinBlows. Since I do not use M$ products, I can only say I've seen those commands work on WinBlows, but can't say how to set that up.
I also can't help you with 7zip, it can run on Linux, but never use it myself.
People have problems when they don't use "real" tar, so don't. Save yourself the pain.
You do not need to convert the .tar to a .tar.md5. Odin will use either file type. A .tar.md5 file is a .tar file with its md5 hash appended. Odin can use the file to verify the .tar integrity, but that is optional.