Related
Hi.
How to obtain Image files from zImage or boot.img?
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.
Can anyone help me here, my phone security patch showing June 5th, how to update it?
Download latest ww ota from Asus website. Download payload dumper and extract payload.bin from that downloaded ota.
After payload.bin extracted put phone in fastboot plug typec into side plug of phone and to your PC.
CMD prompt
Fastboot flash boot boot.img
Fastboot xxx xxx.img (xxx change to all img names example above)
Flash all 21 files
DanXbix said:
Download latest ww ota from Asus website. Download payload dumper and extract payload.bin from that downloaded ota.
After payload.bin extracted put phone in fastboot plug typec into side plug of phone and to your PC.
CMD prompt
Fastboot flash boot boot.img
Fastboot xxx xxx.img (xxx change to all img names example above)
Flash all 21 files
Click to expand...
Click to collapse
thx for the step by step, and will this wipe all my data?
edit:i found some guide mention that i need unlock the bootloader, do i need do this first?
Yes you also need to unlock first and will wipe data
DanXbix said:
Download latest ww ota from Asus website. Download payload dumper and extract payload.bin from that downloaded ota.
After payload.bin extracted put phone in fastboot plug typec into side plug of phone and to your PC.
CMD prompt
Fastboot flash boot boot.img
Fastboot xxx xxx.img (xxx change to all img names example above)
Flash all 21 files
Click to expand...
Click to collapse
It worked but during the process, while flashing system and vendor file I got Invalid sparse file format at header magic
Is it normal? The phone is working fine but checking whether it's normal or anything else needs to be done?
It would be very helpful. Thanks
iamgulshan said:
It worked but during the process, while flashing system and vendor file I got Invalid sparse file format at header magic
Is it normal? The phone is working fine but checking whether it's normal or anything else needs to be done?
It would be very helpful. Thanks
Click to expand...
Click to collapse
yes got same issue but there is a raw of this update now in other guide cn to ww thread flash raw you don't need to unlock
hashcheck said:
yes got same issue but there is a raw of this update now in other guide cn to ww thread flash raw you don't need to unlock
Click to expand...
Click to collapse
That one I had with security patch of June 5th and after flashing now I have July 5th security patch.
I followed the official instructions you can find here.
My device has a boot ramdisk so I grabbed the boot.img as requested by the instructions. I also checked if it has a separate vbmeta partition and it does.
I followed all steps in section "Patching Images", but when I get to the line saying
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
Bash:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Click to expand...
Click to collapse
I don't know from where I was supposed to get vbmeta.img. The instructions never mentioned getting vbmeta.img. Maybe it doesn't matter because the step is optional, and it says "you can patch the vbmeta partition", not "you should" or "you must".
When extracting boot.img from my phone's firmware I also got vbmeta.img, but I don't know if I should flash it as it is, or if I should have Magisk patch it first. Anyway I skipped that optional step and Magisk works, but it would be nice if the instructions were more clear.
I also don't know if the fact that Magisk works despite me skipping that step has anything to do with the fact that before installing Magisk I had dirty flashed LineageOS 19 over LineageOS 18.1, where I had already installed Magisk some months ago by flashing the apk from recovery. The reason I had to reinstall Magisk is that after the upgrade to LOS 19 apps with root permissions would complain about not having root permissions, and the Magisk app would say Magisk was not installed.
Ludoboii said:
Code:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Click to expand...
Click to collapse
The vbmeta.img that they are talking about is the original vbmeta that you copied.
Of course, you need to be rooted or using a ROM bootloader to copy that.
That's a bit of a Catch 22.
That command just alters byte 0x7b from 0x00 to 0x03.
That's the flags.
The minimal vbmeta.img is 256 bytes with the correct header and 0x03 at 0x7b
I just tried this:
Code:
C:\>fastboot erase vbmeta
C:\>fastboot flash vbmeta vbmeta_empty.img
C:\>fastboot reboot
This worked fine for me. No guarantees for you. You don't need to erase, I just wanted to make sure.
I believe that the vbmeta is normally verified in the init process in the boot image.
Since Magisk has a custom init it probably just ignores vbmeta.
If you went to flash a modified boot image that had a stock init this would make a difference.
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.