I flash my OB with v20o (smartflash - root), its ok, root,
Now i can flash with v20C.kdz , original p970H.
I used tool to extrat files ap and cp.
Root is a big problem.
Flash smartflash or kdz, bam my root bye.
How i can make file .zip to flash for CWM.
FLash it with R&D testtool + workaround, use cwm injection method (search for it).
Thats how you ll get your phone with the correct software + root
I found use cwm injection method, but is not clear to me.
When i flash with V20o - rooted, i used smartflash, after process reboot in cwm and install from zip superuser. Thats it i do.
After flash using smartflash phone reboot in cwm, send superuser and ok.
the question is how inject cwm. I read topic about this but is not clear for me.
Can you help me?
I can only guide you here again: http://forum.xda-developers.com/showthread.php?t=1512203
I think it doesnt work with smartflash. But if you use an already rooted version, there also is no need to inject
If you are in CWM, simply make a full wipe and you can install any custom ROM you want already.
Then there is no need to really root and boot it
in this topic
http://forum.xda-developers.com/showpost.php?p=23788913&postcount=170
File cp ap, flash smartflash, auto reboot in cwm mode, install SU.
how make cwm inject in file to flash? is the question.
Phone simple reboot in cwm after flash witch SF.
And don't send SU to phone in first boot, bye bye root, need flash again and send zip SU.
I want make this in other V20XX, its cool.
When you are in CWM, you need to flash superuser.zip, then you can restart.
And dont forget to wipe
How inject cwm in my files, i have files and i need how inject cwm. that it
N00BY0815 said:
When you are in CWM, you need to flash superuser.zip, then you can restart.
And dont forget to wipe
Click to expand...
Click to collapse
All this ok for me.
Simple i do, in my files, i want inject cwm. Only this so
I think is that
Op afraid that lg might know this and patch it. I call that's a bull. I don't think lg engineer didn't know how to use dd. As long as we have unecrypted bin file we can patch it. Btw, how can one conceal a patching method using simple dd when you have unpatch file and patched file to compare? Even I managed to figure it out. Op true intention known only to himself.
So, to patch your bin file: (this is done on ubuntu, i don't know if windows got dd)
1. Download cwm at http://download.clockworkmod.com/rec...8.1.3-p970.img to the folder where you keep your bin file.
2. Open terminal and cd to the same folder as above
3. What we need to find is the location where we're suppose to copy cwm into the bin file. dd is bit-stream reader and it will show us the location in term of bytes. We need to search for ANDROID! string. So type:
dd if=LGP970AT-00-V20b-SEA-XXX-JAN-02-2012+0_AP.bin| strings -n 8 -t d| grep ANDROID!
result:
1436661 ANDROID!
1703936 ANDROID!
6422528 ANDROID!
bla..bla..bla...
4. Look of the last entry which contain the ANDROID! string and take note of its byte location (6422528 in this case)
5. Now it's time to copy cwm into the bin file. Type:
dd if=<cwm.img> bs=1 seek=<byte location> conv=notrunc of=<rom.bin>
So in this case:
dd if=recovery-clockwork-touch-5.8.1.3-p970.img bs=1 seek=6422528 conv=notrunc of=LGP970AT-00-V20b-SEA-XXX-JAN-02-2012+0_AP.bin
6. That's it. Your rom is ready to be flash using smartflash tool. You can run the same command in step 3 to verify that cwm is succesfully copied into the bin file. If at the same byte location the ANDROID! string change to [email protected] then you're good to go.
Don't waste your bandwidth to download the op's file if you can do this yourself and beside there's nothing to test, not that op modified the rom in any way. You would be better off testing huexxx zues rom imho.
Savvy?
Edit: Forgot to add. Credit goes to people who found this rooting method. I didn't found it only take a look at it.
Sent from my LG-P970 using XDA App
Hello everyone,
Have you ever faced the nullnull keyboard error after flashing new stock ROM!!
Here I would like to share with you some information on how to fix this annoying problem..
<<Please follow these tips in order (only go to next option if the first one fails)>>Option #1 (try this one first):
- The easiest and shortest way is to try flashing the ROM again by PC Odin.. flash any custom safe kernel you like (PhilZ-cwm6, HydraCore, SpeedMod), then wipe data/cache..
- Alternatively, you can downgrade to Gingerbread, go to phone and dial *#272*IMEI# (where IMEI is your IMEI number that you can find in Settings --> about phone --> Status). This will open CSC installer window, install your convenient CSC code according to your area (this will delete all your DATA, so please backup first)...
If this doesn't help go to next option!!
Option #2 (I wanna be clean ):
- On stock ICS, install any custom safe kernel you like (PhilZ-cwm6, HydraCore, SpeedMod).
- Download Abyss Kernel and jBroid cleaner and put them in your external SD card.
- Reboot to CWMR (volume up+home+power).
- Install Abyss Kernel.
- Go to advanced menu and reboot recovery.
- You are now on Abyss Kernel, wipe Data/Dalvik/Cache from wipe menu.
- Go to storage menu and choose format /system.
- Install jBroid cleaner.
- Reboot to download mode (volume down+home+power).
- Install the ROM by PC Odin.
- Wait the phone for full boot.
- Reboot to download mode again (volume down+home+power).
- Install the ROM again by PC Odin ((very important!!!)).
If this doesn't help also go to next option!!
Option #3:
- Put the ROM file on your SD card.
- Open mobile odin, select cache tab and point to full ROM file you have on SD card and flash.. if also doesn't help go to the next method!!
PS: this might delete your DATA, so make backup first.
The long method:
- Go to stock ROM and take out the .md5 extension (ROM.tar.md5 --> ROM.tar).
- Open it by WinRAR or any unpacking program and extract cache.img file.
- Now in linux terminal, or cygwin (support Windows and Mac OS users) you need to make flashable tar file out of cache.img file. [If you are using cygwin, put cache.img in \cygwin\home\"user" folder]. Open linix terminal or cygwin and type the following command:
Code:
tar -H ustar -c cache.img > cache.tar
The following commands are not necessary since the tar file you just created is flashable; but for perfection matter!!
Code:
md5sum –t cache.tar >> cache.tar
mv cache.tar cache.tar.md5
- Open PC Odin, select CSC tab and open the cache.tar or cache.tar.md5 that you have just created and flash it.
PS: this might delete your DATA, so make backup first.
-------------------
If you find these tips beneficial, please press THANKS button...
.
majdinj said:
Hello everyone,
Have you ever faced the nullnull keyboard error after flashing new stock ROM!!
Here I would like to share with you some information on how to fix this annoying problem..
<<Please follow these tips in order (only go to next option if the first one fails)>>Option #1 (try this one first):
- The easiest and shortest way is to try flashing the ROM again by PC Odin.. flash any custom safe kernel you like (PhilZ-cwm6, HydraCore, SpeedMod), then wipe data/cache..
- Alternatively, you can downgrade to Gingerbread, go to phone and dial *#272*IMEI# (where IMEI is your IMEI number that you can find in Settings --> about phone --> Status). This will open CSC installer window, install your convenient CSC code according to your area (this will delete all your DATA, so please backup first)...
If this doesn't help go to next option!!
Option #2 (I wanna be clean ):
- On stock ICS, install any custom safe kernel you like (PhilZ-cwm6, HydraCore, SpeedMod).
- Download Abyss Kernel and jBroid cleaner and put them in your external SD card.
- Reboot to CWMR (volume up+home+power).
- Install Abyss Kernel.
- Go to advanced menu and reboot recovery.
- You are now on Abyss Kernel, wipe Data/Dalvik/Cache from wipe menu.
- Go to storage menu and choose format /system.
- Install jBroid cleaner.
- Reboot to download mode (volume down+home+power).
- Install the ROM by PC Odin.
- Wait the phone for full boot.
- Reboot to download mode again (volume down+home+power).
- Install the ROM again by PC Odin ((very important!!!)).
If this doesn't help also go to next option!!
Option #3:
- Put the ROM file on your SD card.
- Open mobile odin, select cache tab and point to full ROM file you have on SD card and flash.. if also doesn't help go to the next method!!
PS: this might delete your DATA, so make backup first.
The long method:
- Go to stock ROM and take out the .md5 extension (ROM.tar.md5 --> ROM.tar).
- Open it by WinRAR or any unpacking program and extract cache.img file.
- Now in linux terminal, or cygwin (support Windows and Mac OS users) you need to make flashable tar file out of cache.img file. [If you are using cygwin, put cache.img in \cygwin\home\"user" folder]. Open linix terminal or cygwin and type the following command:
Code:
tar -H ustar -c cache.img > cache.tar
The following commands are not necessary since the tar file you just created is flashable; but for perfection matter!!
Code:
md5sum –t cache.tar >> cache.tar
mv cache.tar cache.tar.md5
- Open PC Odin, select CSC tab and open the cache.tar or cache.tar.md5 that you have just created and flash it.
PS: this might delete your DATA, so make backup first.
-------------------
If you find these tips beneficial, please press THANKS button...
.
Click to expand...
Click to collapse
Nice info...:good:
Hi, I rooted my s10 with magisk but cannot flash twrp parched with odin because the file is .img and odin accepts file tar.
What do I Havel to do?
Guide to Extract Boot image file and flash via Odin Tool
First, download the preferred Samsung Stock ROM for your device model.
Extract the firmware zip file on your computer within a folder.
Now, the boot image file named as AP_xxx (similar kind of) file.
Recently, Samsung firmware files use a new compression type called .lz4 extension. You may see something like boot.img.lz4 file name.
Extract the boot.img.lz4 file via 7Zip to .tar extension and now you will see the boot.img.tar file. Download 7Zip - github (dot) com (slash) mcmilk (slash) 7-Zip-zstd (slash) releases
Now, open the Odin tool and connect your device to the PC via a USB cable.
Click on the ‘AP’ button and select the boot.img.tar file from your computer.
Click on the ‘Start’ button.
That’s it. Wait for flashing to complete and reboot your handset.
Hope this guide will be helpful to you. If you’re facing any issue, you can ask your queries in the comments below.
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.