Database Users

Question on .tar

Perhaps a dumb question, but my brain is hurting from all the learning here:
I have modified my phone as I want it, including rooted deodexed stock eb01, swapping .apks, running all the mods through cwm, removing apps,etc. (I guess I themed it the hard way).
Question: Can I create a .tar file from the device while it is running, basically a 'snapshot' of the system exactly as it is ? That way I can odin to current setup if I dork up my phone.
my apologies if this is a stupid question
Sent from my SCH-I500 using XDA App

THAT IS TOTALLY NOT A STUPID QUESTION...I actually believe its a great idea right now.

Well, the long answer is, you shell into the phone and make images of the various sectors of the phone, name them properly, and heimdall them. If you use odin, take an extra step to tar it together.
Here its a guide for doing that on a continuum:
http://androidforums.com/continuum-all-things-root/263953-how-make-custom-odin-images.html
Note it glosses over dividing out the kernel binaries and RAMdisk, mentioned in the more comprehensive guide for the Behold:
http://androidforums.com/behold-2-all-things-root/54424-creating-custom-roms- odin.html
I haven't seen anyone post a cute little listing of the actual partitions and cutoffs specific to the fascinate, but I haven't looked very hard either.
UPDATE #2: (it is L: bml7, not bm17 & not bmI7)
So theoretically it's really simple (from an adb shell):
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096​(copy zImage and factoryfs.rfs to your local computer)
tar -H ustar -c zImage factoryfs.rfs dbdata.rfs cache.rfs > odinTAR.tar​These two commands append an md5 checksum to your package, and then rename the file. This finishes the process.
md5sum -t odinTAR.tar >> odinTAR.tar
mv odinTAR.tar odin_package.tar.md5​NOTE: I did not include the modem, but you can flash that separately. This tar includes your personal data, so consider this before distributing any file you make this way. I haven't tested these instructions myself in any way.
Short answer:
Backup (everything but kernel) with nandroid and use that to restore. So long as you have a happy recovery setup, that is the path of least effort.
Swyped w/ XDA App. A clean tie attracts the soup of the day.

thanks for the response; certainly more involved than just a " create .tar" option somewhere. (Though that would be cool to develop for CWM or something)
Looks like some more learning for me. Always appreciate the info.

The next time there is a worthwhile update from VZW, I'd like to put together a not-stock, stripped-down-as-possible (small file) odin tar that is just enough to be a launchpad for flashing ROMs on whatever the next official modem is. So I'm doing my reading ahead of time.
Actually this looks like a great "What is where" link:
http://forum.xda-developers.com/showthread.php?t=850359
To paraphrase the link I posted above:
These are found in /dev/block. BML stands for Block Management Layer. STL is Sector Translation Layer. RFS is Samsung's Robust File System.
bml7 zImage (kernel)
stl9 factoryfs.rfs (system)
modem:
bml12 modem.bin
personal data:
stl10 dbdata.rfs
stl11 cache.rfs
other:
stl6 param.lfs
bml2 pit.pit
bml3 efs.rfs
NEVER:
bml1 boot.bin
bml4 Sbl.bin
unknown:
bml8 recovery.bin
You may use dd (and apparertly cat) to copy these partitions to your SD card:
adb shell su -c "dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096"
adb shell cat /dev/block/stl9 > /sdcard/factoryfs.rfs
You may reflash them individually with heimdall, or tar to flash as a group in Odin.

Help with the GT-P1000L

Hi there!
I am not an expert and I tried to install the Overcome Room + Overcome Kernell, to try to fix the issue showing "Internal MMC checksum verify failed".
I followed the guide step by step, choosing the room, the modem, the kernell etc etc...
flashing with Odin.
However, now looks like my Tab come to the point where the Internal Sdcard is damaged.
I am trying to follow this guide here:
http://forum.xda-developers.com/showthread.php?t=1463756
However, How in the hell do I insert this codes, I mean, where I type then?
adb shell "dmesg | grep mmc0"
or
heimdall flash --repartition --pit gt-p1000_mr.pit --primary-boot boot.bin \
--cache cache.rfs \
--factoryfs factoryfs.rfs --modem modem.bin \
--param param.lfs \
--secondary-boot Sbl.bin \
--kernel zImage --recovery zImage
or
# internal sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = disable
discard = disable
format_option = -r 1558
}
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.2/mmc_host/mmc1
# externel sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = enable
}
dev_mount sdcard /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2 /devices/platform/s3c-sdhci.2/mmc_host/mmc1
I have no clue to how put that!!!
And, besides, my tab only get stucked on the brick screen when I am charging it...If I try to turn it on on download mode, it will turn off...and no sign of life coming from it...
What is the deal? Did kill my device?
Update: Now It is being recognized by odin. Let me try the steps on the Heimdall.

Actually you have the L device.
You can't use overcome kernel.
You can install but the touchscreen won't work.
You will have to replace the kernel with humberos kernel.
Or just move on to Ice Cream Sandwich.
Sent from my GT-I9300 using xda app-developers app

Heimdall and MacOSX: Update Stock.

ALL CREDITS go TO: Benjamin Dobell, http://www.glassechidna.com.au THANK YOU!!
I AM NOT RESPONSIBLE, IF YOU TOAST YOUR DEVICE IN THE PROCESS!! Any damage done is YOUR fault, not mine and I am not responsible!
What is this guide for? It has all been said before, but I like comprehensive guides that cover the essentials and can somehow be understood by newbies! AND be found by the title.
First: Why do I use heimdall or why should you use it? Odin is available for Windows, but not for MacOSx or Linux and I didn't use Windows the last 8 years, if I could avoid it and I often don't install it at all, because I normally don't need it. Heimdall is opensource and theoretically easy to use and straight forward. In the process, you even learn what you are doing and are a bit more AWARE of the whole process. Nice side effect.
Start: Download version 1.3.1 (1.3.2 has sometimes problems with the CACHE upload) or compile the latest version via command line. A README is included. Reading is power, remember it and have a look, BEFORE actually flashing a new firmware or ROM.
https://github.com/Benjamin-Dobell/Heimdall/downloads
heimdall-suite-1.3.1-mac.dmg
1) You did install Kies, if not do it.
2) Some of the kext files, kernel extensions, do prevent heimdall from working correctly. Unload them inside the Terminal. Open Terminal and type:
THE
$
SIGN SHOULD NOT BE INCLUDED!!, but shows YOU that you should type the commands inside the command line (Terminal). Open a Terminal Window and Type:
$ sudo kextunload -b com.devguru.driver.SamsungComposite
$ sudo kextunload -b com.devguru.driver.SamsungACMData
$ sudo kextunload -b com.devguru.driver.SamsungACMControl
Type your account password.
4) Now: There is a frontend, but it's easier to use the command line actually!! The documentation is better and the verbose output shows the progress.
5) Have a look at heimdall's command line syntax and manual. Type
$ heimdall
6) Did you download a firmware image from sammobile or XDA? Unzip or untar it inside FINDER. Afterwards, you have got a folder and inside a few files looking like:
Sbl.bin
cache.img
factoryfs.img
hidden.img
modem.bin
zImage
7) The extensions can also be ".rfs" instead of ".img" . It doesn't matter.
8) Terminal: change directory to the firmware folder by dropping it to the terminal window after Typing "cd ":
$ cd /Users/YOURNAME/DOWNLOADS/FOLDER
Where are we now?? Type
$ pwd
/Users/YOURNAME/DOWNLOADS/FOLDER
which files are inside?? Type
$ ls
Sbl.bin
cache.img
factoryfs.img
hidden.img
modem.bin
zImage
9) Go to Download mode, i.e. with Volume down+Menu THAN +Power on, enter Download mode with Volume button
10) Is your cellphone recognized by heimdall?? Type
§ heimdall detect
Device detected
IF not: go back to 2) and unload kextfiles!!
10) My problem was that I didn't find the right syntax for the command line. It's documented in the README file and easy but ypu want to know what you do and not to brick the device. Reading is power, but I forgot about reading ALL of the README.
11) You can use a PIT file and should download it BEFORE flashing for the first time! It's a partition map of your cellphone. Type
§ heimdall download-pit --output PIT.pit
You saved it to the Firmware / Rom folder that you "cded" into before.
12) Start Flashing: YOU CAN BRICK YOUR DEVICE!! REMEMBER THAT and it's not my fault, if you toast it or if you made an expensive PAPERWEIGHT!!
13) You have got a few different files. Something like: Type
$ ls |more
PIT.pit
Sbl.bin
cache.img
factoryfs.img
hidden.img
modem.bin
zImage
14) OPen a text editor and fill in your files. There are more options. You could root your device, but I don't cover how to do it. Use the search button.
--pit PIT.pit --factoryfs factoryfs.img --cache cache.img --hidden hidden.img --secondary-boot Sbl.bin --kernel zImage --modem modem.bin
15) Flash the whole thing by typing and copying:
§ sudo heimdall flash --pit PIT.pit --factoryfs factoryfs.img --cache cache.img --hidden hidden.img --secondary-boot Sbl.bin --kernel zImage --modem modem.bin
Wait. Don't wet your panties. It should look like:
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
100%
KERNEL upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Uploading HIDDEN
100%
HIDDEN upload successful
Ending session...
Rebooting device...
15) Your done. Congrats! If your phone booted to the recovery, choose reboot with volume buttons and use the Power button to confirm it.
Did I forget sth. important? Write me a PM.
All credit goes to the developer! THANK you very much.

Thanks for the guide, although I fear issues... I am sticking with Odin through Parallels for the time being, but will give this a go soon...
Sent from my GT-N7000 using Tapatalk 2

the parameters have to be written in capital letters like --CACHE cache.img or you will get an error

Doesnt work
heimdall flash --recovery openrecovery-twrp-2.6.3.0-jgedlte.img
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!
---------- Post added at 01:04 PM ---------- Previous post was at 01:03 PM ----------
Doesnt work
heimdall flash --recovery openrecovery-twrp-2.6.3.0-jgedlte.img
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!

Hi, I know this is an old one and wrong phone, but i need to flash my S6 using my MAC. I brought the files in following order:
--pit PIT.pit --cache cache.img --hidden hidden.img --secondary-boot sboot.bin --modem modem.bin
but i don't know the commands for the following files:
recovery.img, system.img, boot.img, cm.bin
Thanks for helping me out.

L0rdR4gn4r said:
Hi, I know this is an old one and wrong phone, but i need to flash my S6 using my MAC. I brought the files in following order:
--pit PIT.pit --cache cache.img --hidden hidden.img --secondary-boot sboot.bin --modem modem.bin
but i don't know the commands for the following files:
recovery.img, system.img, boot.img, cm.bin
Thanks for helping me out.
Click to expand...
Click to collapse
Use parallels and Odin,or a pc

[Q] Galaxy S4 Odin Package Invalid MD5 Hash

Hi XDA!
I managed to bebloat and odex some extra system apps on my Stock Touchwiz ROM, and wanted to make a backup in case something goes wrong again. I tried to follow this guide: http://forum.xda-developers.com/showthread.php?t=2277127, however, Odin always throws an error 'MD5 hash value is invalid'. I suspect there is something wrong with my image, as the developer that started that thread said his packages worked perfectly. I used the make_ext4fs binary from this link: http://web.djodjo.org/dwn.php?ff=211260&a=download/android/tools/x86_linux/ext4tools:make_ext4fs, and copied it to my device. Is the binary supposed to be for Android? Somehow when I used other images(boot.img, for example) using the same method to package into an Odin flashable, Odin do not give the error. I have managed to create a working package of the system.img.ext4 before, but could not remember how I did it. Can someone point out what I did wrong?
This is what I did to dump the system.img.ext4(it's only 2400M because I have debloated the ROM, is this the problem?):
Code:
su
make_ext4fs -s -l 2400M -a system /storage/extSdCard/system.img.ext4 /system
This is what I did to create the Odin package:
Code:
tar -H ustar -c boot.img recovery.img system.img.ext4 > test.tar
md5sum -t test.tar >> test.tar
mv test.tar test.tar.md5
I also tried this when creating Odin package:
Code:
tar -c boot.img recovery.img system.img.ext4 > test.tar
md5sum -t test.tar >> test.tar
mv test.tar test.tar.md5
But both doesn't work. I realized when I only include boot.img or recovery.img or both(without system.img.ext4) and package these files the package passes Odin's MD5 check. Does anyone know what is the issue? Thank you very much!

Backup S5 stockRom before TWRP & root? Possible? Which tool? How?

How to backup stockRom S5 before starting to follow any instructions to root + flash + LineageOS ...
What I want:
* backup my brand new stock ROM Galaxy S5 SM-G900F
* before I even start with TWRP, root, etc.
* with an apk, via USB on a PC ... any way that would work
* or if total backup does not exist, then at least the EFS partitions?
because:
* I might want to sell it later
* I might have to send it back
* flashing TWRP & LineageOS might fail
* I have lost mobileInternet on an LG-V20 already because something went strange when flashing
* I am careful
Is there any way to backup a Samsung S5 before I even start with following any instructions here?
Am I asking for something impossible?
Was I on the right way already (see below), but have done something wrong?
Is it perhaps only possible after rooting? If so, then which tool do you recommend then?
Thanks a lot!
What I have tried:
* xda developer galaxy-s5/general every thread title until page 5 https://forum.xda-developers.com/galaxy-s5/general/page5
* xda developer search for "S5 backup", "S5 EFS", and a few other searches. Sorry for being dumb, please help me search, thanks.
* Heimdall PIT, but "ERROR: Failed to send request to end PIT file transfer!"
* Odin PIT, but "Can't open the specified file. (Line: 1892)"
* Samsung Tool 5.0 com.sec.ricky310711.samsungtool.apk https://forum.xda-developers.com/showthread.php?t=2696153 but the app-->Backup-EFS hangs at "Please Wait..." <-- probably because I could not install busybox because no root yet.
* manual EFS backup with dd https://forum.xda-developers.com/showthread.php?t=2737448 but I get a "su: not found", obviously, because unrooted
Code:
Heimdall v1.4.0
...
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 0 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Can't open the specified file. (Line: 1892)
<OSM> All threads completed. (succeed 0 / failed 1)

Anyone?

ankade said:
Anyone?
Click to expand...
Click to collapse
Though, I don't have your specific variant, the typical "just in case" files (that I personally always begin with) to obtain are the following:
1) Stock Firmware File (I just go with the latest and sometimes the 1 previously released).
2) Latest Odin PC Software.
3) Latest Samsung USB Drivers for the PC.
4) PIT file (PIT = Partition Information Table).
Those are usually the bare essentials that I begin with.
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.

Great, thanks a lot. That is a helpful list.
Ibuprophen said:
2) Latest Odin PC Software.
Click to expand...
Click to collapse
Which is the latest you are using? The version "Odin3-v3.13.1" does NOT work, see above.
How exactly do I extract the current state of my (still unrooted) SM-G900F ?
Thanks.

I have now tried again manually:
Code:
heimdall download-pit --output s5.pit
Is that the right command?
It only worked after overwriting the MSM8960 driver with zadig.exe
Then it looks like this:
Code:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
then after a while:
Code:
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...

heimdall 1.4.2
Hooray, big progress. It was a version problem, older versions of heimdall seem faulty. And grrrmpf: the "heimdall" website which comes up at the top on search engines ... provides an outdated 1.4.0 version. Which seems broken. But hooray, the 1.4.2 version of heimdall works:
this looks good, no?
Code:
cd heimdall_1.4.2_win64
heimdall print-pit --no-reboot
Code:
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is encouraged.
If you appreciate this software and you would like to support future development please consider donating: http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Code:
Entry Count: 30
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21325
Unknown 4: 14413
Unknown 5: 14137
Unknown 6: 52
Unknown 7: 0
Unknown 8: 0
now there are 30 such entries:
Code:
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 30720
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: APNHLOS
Flash Filename: NON-HLOS.bin
FOTA Filename:
I got the new heimdall 1.4.2 version from here:
https://github.com/Benjamin-Dobell/Heimdall/issues/295#issuecomment-364729538
and because he only provides the source, the binary from here
https://github.com/tothphu/heimdall_build/

this worked too:
Code:
heimdall download-pit --no-reboot --output S5-download-pit.pit
It resulted in a non-human-readable binary file of 8192 bytes.
But:
How to backup partitions?
with
Code:
heimdall --help
I can see that there I can flash ONTO the device with e.g.
Code:
heimdall flash --RECOVERY twrp-x.x.x-x-klte.img --no-reboot
but there does not seem to be a
Code:
heimdall read --RECOVERY --file recovery.img --no-reboot
?
how to READ a partition FROM the device?
?

Now I have tried it via USB debugging, with "minimal_adb_fastboot_1.4.3_portable.zip"
but
Code:
adb shell
ls -al /dev/block/platform/msm_sdcc.1/by-name/efs
lrwxrwxrwx root root 2014-05-24 16:36 efs -> /dev/block/mmcblk0p12
dd if=/dev/block/mmcblk0p12 of=/storage/3164-3234/S5/efs.img
results in
Code:
dd: /dev/block/mmcblk0p12: Permission denied
and
Code:
su -
/system/bin/sh: su: not found
so it looks as if my first hope has to be declared dead ...
No system backup without root, right?
?
But what I don't understand ... How did people extract these here then: https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/ ???
I have found instructions how to get back to stock rom, but I would like to use my own original stockROM for that. But I don't know how to back it up. Please help. Thanks.

how to root?
The phone is this one:
Samsung S5
SM-G900F
Android version 6.0.1
Android security patch level: 1 January 2017
I have tried these root tools:
Kingroot (NewKingrootV5.3.7_C197_B451_xda_release_2018_06_19_20180620193529_242043.apk) --> "Generating adaptation strategy, please come back later"
Towelroot v1.0 (tr.apk) --> "This phone isn't currently supported"
I did not want to try CF-Auto-Root because it says "If you have a Samsung-KNOX-enabled device, this package will trip the KNOX warranty flag. This flag cannot be reset, and will prevent some applications from working."
Is there really no way to get root without first installing TWRP ?
?