So, i rooted my original galaxy tab p1000 with odin3-v1.8, but when im in clockwork mod, and i want to install roms or WHATEVER thing i choose, i get an error similar to E: can't mount. Whether i try to clear cache or reset, it says this and i have no choice. It seems like a brick....ANYONE Help me, Much will be appreciated.
It seems like it was not rooted correctly. Did you run titanium backup after rooted?
Can u tell us what was the latest working firmware u had? FROYO,,GB? 2.2, 2.3.3, 2.3.6?
Anyways, Follow these steps carefully to fix almost all kind of softbrick:
1a. Download Fus Check Downloader 2.1 on your computer from url]http://fus.nanzen.se/[/url] , start it up and and downloaded a Firmware for your region. It will automatically decode the .enc2 file to.zip file
1b. Download this pitfile from following link:
http://forum.xda-developers.com/attachment.php?attachmentid=631856&d=1308653969
1c. Download this dbdata from the following link:
http://forum.xda-developers.com/attachment.php?attachmentid=631856&d=1308653969
2. Extract the .zip file generated from decoding file to a folder and I got tar.md 5 file.
3. Start Odin - put the .md5 to PDA
Put the pitfile from step 1b to the PIT
Check repartition. Leave everything else as is.
4. Go to download mode on the G-tab, connect to ur computer
and click start on Odin. It takes about 6 to 7 minutes to do the flashing.Once done flashing it will reboot but mostlikely you still have problems with your tab.
5. on your Odin, put the dbdata file from step 1c to PDA, leave everything else as is.
Reboot your tab to download mode, connect to computer, and click start on Odin.
6. Once done, reboot to recovery mode, do a factory reset wipe, and data cache wipe.
Reboot again, wait for about 5 minutes for the tab to boot, you should be all set.
Thx
yappoe said:
It seems like it was not rooted correctly. Did you run titanium backup after rooted?
Can u tell us what was the latest working firmware u had? FROYO,,GB? 2.2, 2.3.3, 2.3.6?
Anyways, Follow these steps carefully to fix almost all kind of softbrick:
1a. Download Fus Check Downloader 2.1 on your computer from url]http://fus.nanzen.se/[/url] , start it up and and downloaded a Firmware for your region. It will automatically decode the .enc2 file to.zip file
1b. Download this pitfile from following link:
http://forum.xda-developers.com/attachment.php?attachmentid=631856&d=1308653969
1c. Download this dbdata from the following link:
http://forum.xda-developers.com/attachment.php?attachmentid=631856&d=1308653969
2. Extract the .zip file generated from decoding file to a folder and I got tar.md 5 file.
3. Start Odin - put the .md5 to PDA
Put the pitfile from step 1b to the PIT
Check repartition. Leave everything else as is.
4. Go to download mode on the G-tab, connect to ur computer
and click start on Odin. It takes about 6 to 7 minutes to do the flashing.Once done flashing it will reboot but mostlikely you still have problems with your tab.
5. on your Odin, put the dbdata file from step 1c to PDA, leave everything else as is.
Reboot your tab to download mode, connect to computer, and click start on Odin.
6. Once done, reboot to recovery mode, do a factory reset wipe, and data cache wipe.
Reboot again, wait for about 5 minutes for the tab to boot, you should be all set.
Click to expand...
Click to collapse
Seems like the problem for me was resolved by following these instructions:
http://www.thegalaxytabforum.com/in...gingerbread-p1000xxjq1-p1000xxjq1-p1000xxjpz/
Thank you for your help too,
My CWM recovery is corrupted.
I would like to
- go back to a GB based ROM (from an ICS one- Liquidsmooth)
- and go back by using ODIN by flashing a kernel (TAR FILE)
Can anyone
1- Point me to a link for franco kernel or abyskernel tar files (to be used in ODIN)
2 - let me know how we concvert a zimage file (inisde kernel files) to tar for use in ODIN
TY
Download any kernel zip you like, extract zimage, and tar it with 7-Zip.
extract zimage?
I need to zip the zimage as tar using 7zip yes?
I believe zimage file cannot be opeend using 7zip?
i toiok the zimage file from abysnote and zipped it in tar using 7zip.
After connecting phone in download mode to ODIN, and starting flash
ODIN gets stuck at <ID:004>zimage
Any help?
Question
- can i flash a whole ROM using ODIN? will this have a jernel accompanying it? or i have to flash both seperately? ( i want to flash criskelo's ICS rom - i am on liquidsmooth ICS now)
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.
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.