I am trying to learn how to make an odin flashable Stock Rom Tar file for the SCH-i815 for backup purposes.
After running this command through terminal emulator:
ls -al /dev/block/platform/dw_mmc/by-name
Terminal emulator spits these out:
lrwxrwxrwx root root 2012-09-08 13:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-09-08 13:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-09-08 13:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-09-08 13:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-09-08 13:24 HIDDEN -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-09-08 13:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-09-08 13:24 LTE -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-09-08 13:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-09-08 13:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-09-08 13:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-09-08 13:24 SBL2 -> /dev/block/mmcblk0p3
Those are the partitions for my device. After reading around, it seems I can dump them to my sdcard using this command through terminal emulator on my device:
dd if=/dev/block/"mmc_partition_here" of=/SdCard/backup/"mmc_partition_name_here" bs=4096
Is this correct? and If so, is it recommended that I dump and repackage all partitions in a tar file? or would Recovery, Kernel, Factoryfs, and LTE be enough? Every google result i read seems to imply Kernel, Recovery and Factoryfs are all that is needed, with modem being optional.
I would be dumping this from 100% stock rom with SU.
Once all is dumped, I woul be packaging the files in a tar file using this command:
tar -H ustar -c recovery.img system.img modem.bin zImage> package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
Can anyone with experience chime in? I wanna make sure this is correct before i attempt this, I don't want to bork my tab.
Hey!
Never used odin, only heimdall in rare cases, to restore my backups I use terminal emu..
you are correct.
ex. to backup stock rfs system_fs
dd if=/dev/block/mmcblk0p9 of=/sdcard/system.rfs bs=4096
to restore
dd if=/sdcard/system.rfs of=/dev/block/mmcblk0p9
You can flash recovery ,kernel ,data ,modem while system is even running with terminal emulator,
maybe also system while system is running, but I have not tested this..
biopsin said:
Hey!
Never used odin, only heimdall in rare cases, to restore my backups I use terminal emu..
you are correct.
ex. to backup stock rfs system_fs
dd if=/dev/block/mmcblk0p9 of=/sdcard/system.rfs bs=4096
to restore
dd if=/sdcard/system.rfs of=/dev/block/mmcblk0p9
You can flash recovery ,kernel ,data ,modem while system is even running with terminal emulator,
maybe also system while system is running, but I have not tested this..
Click to expand...
Click to collapse
I have pulled System, Kernel and Recovery successfully.
I am able to successfully create and flash Kernel and Recovery tar files separately, but when I try to make a single tar with System, Kernel and Recovery Odin fails and spits this out:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> i185Stock.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> factoryfs.img
<ID:0/013> NAND Write Start!!
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I used the following command line entries to create the single tar and md5:
tar -H ustar -c factoryfs.img recovery.img zImage > i185Stock.tar
md5sum -t i185Stock.tar >> i185Stock.tar
mv i185Stock.tar i185Stock.tar.md5
Any ideas? Would changing the order of the dumps when creating a tar file make a difference?
EDIT: Changing the order when creating the tar file soft bricks it as it fails when it gets to factoryfs Kernel and Recovery I have no problem creating a tar and flashing, but system will fail in Odin during flash. I don't know why system won't flash.
Seems a dumped factoryfs won't flash without some more work done on a linux box: http://forum.xda-developers.com/showpost.php?p=20654525&postcount=15
jivy26 said:
Code:
dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.img bs=4096
That wont flash in odin you still need to make it 512M so quick run down in linux
Download this http://dl.dropbox.com/u/53644280/ext4_utils.zip
So you can view contents of .img
Code:
mkdir tempdir; mount -o loop factoryfs.img tempdir
To repack img w/ 512M
Code:
./mkuserimg.sh -s /some/directory/ ./factoryfs_custom.img ext4 ./temp 512M
Then making a TAR ball.
Click to expand...
Click to collapse
I need someone with a linux box to repack the factoryfs to 852
Thank you for this!!! I, too, am interested in creating an ODIN tar file for my SCH-I815 tablet. I saw this one here for the Verizon Galaxy S III, and perhaps it'll give a clue on how to do it on our tablet.
http://forum.xda-developers.com/showthread.php?t=1777579
AlpineMan said:
Thank you for this!!! I, too, am interested in creating an ODIN tar file for my SCH-I815 tablet. I saw this one here for the Verizon Galaxy S III, and perhaps it'll give a clue on how to do it on our tablet.
http://forum.xda-developers.com/showthread.php?t=1777579
Click to expand...
Click to collapse
I used this, among others, as a guide ;p I have been researching this for a while.
I am able to dump System, Kernel and Recovery. I can even make Odin flashable tar files of Kernel and Recovery. I can't get System/Factoryfs to flash successfully tho, It always fails. I've never used linux before, but I'm thinking i might as well give it a go since I've been unsuccessful thus far.
Gilbot said:
I used this, among others, as a guide ;p I have been researching this for a while.
I am able to dump System, Kernel and Recovery. I can even make Odin flashable tar files of Kernel and Recovery. I can't get System/Factoryfs to flash successfully tho, It always fails. I've never used linux before, but I'm thinking i might as well give it a go since I've been unsuccessful thus far.
Click to expand...
Click to collapse
I'll ask the author of that GS3 ODIN thread to see if he can chime in here.
Any progress on this?
Sent from my SPH-L710 using Xparent SkyBlue Tapatalk 2
No, I put it on the backburner until I can get Linux installed and learn how to use it.
Sent from my SCH-I815 using xda premium
Hello,
I'm not able to build (repackage) correctly system.img for SM-G361F, output is always rejected by both Odin (10.3.7) and Heimdall
I'm trying to repackage (pre-root) system.img taken from "G361FXXU1APA2_G361FOXX1APA1_G361FXXU1APA2_HOME.tar.md5" (taken from ETL factory image named ETL-G361FXXU1APA2-20160202095551.zip )
Step-by-step:
1) tar xvf G361FXXU1APA2_G361FOXX1APA1_G361FXXU1APA2_HOME.tar.md5 system.img
2) simg2img system.img system.img.raw
3) mount system.img.raw /mnt
4) made changes
5a) make_ext4fs -s -g 32768 -b 4096 -T -1 -S file_contexts -f -l 1843M system.repack.img /mnt/
5b) mkuserimg.sh -s /mnt system.repack.img ext4 system 1843M file_contexts
6) tar --owner 0 --group 0 --numeric-owner -H ustar -c system.img > G361F_SYSTEM.tar
7a) Load either system.img through Heimdall (PIT file downloaded through Heimdall is here: http://forum.xda-developers.com/showpost.php?p=65779994&postcount=146 )
7b) Load G361F_SYSTEM.tar in Odin v3.10.7 in AP tab and flash it
On ODIN/Download screen I can see that
1) FRP LOCK: OFF
2) KNOX: 0x0
3) System status: official
4) RP SWREV: S1, L1, M1
Notes
1) I have checked the box "OEM Unlock" in Developers settings to enabled
2) "file_contexts" is taken from booted up device through ADB (adb pull /file_contexts)
3) I've tried repackage the image without making any changes
4) When I compare original and repackaged images ("ls -lsaR" outputs), it seems like owner:group permissions are not persisted
5) I've tried both simg2img/make_ext4fs/mkuserimg.sh from CM12.1 repository (up to date today) and from https://github.com/ASdev/android_img_repack_tools (branch android-5.1.1)
6) I'm not sure about size 1843M, however flashing fails in the same manner when I go with 1536M and 2048M and anything between those two
7) Heimdall fails at about 6% of flashing single (sparse system.img) file with error "Failed to unpack received packet"
OSS Kernel for SM-G361F is here: https://github.com/smarek/G361F-Kernel
OSS Platform for SM-G361F is here: https://github.com/smarek/G361F-Platform
Questions are:
1) Is there anything special to be aware of when building for Samsung devices?
2) Did I miss or misunderstood any step in system.img repackaging process?
well recently i tried to root my phone and it went perfectly later than i tried to flash the rom and it failed.somehow my device stuck at the Samsung Galaxy A5 logo with these information that I cannot quite understand:
ODIN MODE
PRODUCT NAME:SM-A500F
CURRENT BINARY:CUSTOM
SYSTEM STATUS;CUSTOM
REACTIVATION LOCK(KK)FF
KNOX WARRANTY VOID:0x1(4)
QUALCOMM SECUREBOOET:ENABLED (CSB)
RP SWREV: S1,T1,H1,R1,A1,P1
SECURE DOWNLOAD:ENABLE
anyone please help me: crying:
sharifulaiman said:
well recently i tried to root my phone and it went perfectly later than i tried to flash the rom and it failed.somehow my device stuck at the Samsung Galaxy A5 logo with these information that I cannot quite understand:
ODIN MODE
PRODUCT NAME:SM-A500F
CURRENT BINARY:CUSTOM
SYSTEM STATUS;CUSTOM
REACTIVATION LOCK(KK)FF
KNOX WARRANTY VOID:0x1(4)
QUALCOMM SECUREBOOET:ENABLED (CSB)
RP SWREV: S1,T1,H1,R1,A1,P1
SECURE DOWNLOAD:ENABLE
anyone please help me: crying:
Click to expand...
Click to collapse
I had the same problem, when I flashed my testing recovery.
What u need is flash stock recovery and boot (you can find them by extracting official firmware; you can find it here) After extracted them you have boot.img and recovery.img, but odin flashes only tar files, so, to create boot.tar and recovery.tar, open terminal (if u use linux or cygwin if u use windows) and type:
Code:
tar -H ustar -c recovery.img > recovery.tar
and then
md5sum -t recovery.tar >> recovery.tar
for recovery.img and for boot.img type:
Code:
tar -H ustar -c boot.img > boot.tar
and then
md5sum -t boot.tar >> recovery.tar
If it doesn't work flash official firmware, but first try first metod, because by flashing official firmware your data will be wiped
I'm looking for the few previous and this CP version:
CP fw version : G920FXXU6ERF8
CP fw date : Jun 25 2018 14:28:09
MODEL : SM-G920F
VER : G920FXXU6ERF5/G920FFTM6ERF1/G920FXXU6ERF8/G920FXXU6ERF5
I'd like to unlock a phone with a blocked network.
Can I install CP alone without losing data?
can anyone help with creating files for unbrick using MultiDownloader
1 BL1
2 Bl2.bin;
3 dram_el3mon.bin
4 dram_train.bin
5 epbl.bin
6 s-boot.bin
I uploaded sboot from firmware that was in the device
I also found boot1 and boot2 on YouTube for model a750f, should be the same since its a exynos 7885
eldon301 said:
can anyone help with creating files for unbrick using MultiDownloader
1 BL1
2 Bl2.bin;
3 dram_el3mon.bin
4 dram_train.bin
5 epbl.bin
6 s-boot.bin
I uploaded sboot from firmware that was in the device
I also found boot1 and boot2 on YouTube for model a750f, should be the same since its a exynos 7885
Click to expand...
Click to collapse
why you don't use heimdall and samloder for download original firmware tested on my SM-A750FN and I was angry theta this two programs saved my phone evrytime (one rule never flash **** on boot partitions use original fw. then you will be never Brik a phone.
use samloader like instructions
then flash in order one after another files in download mode on phone using himedall (download mode press both volume buttons and put cable in connected to pc) then use command to veryfite if device in developer mode is connected "add devices" then you use "adb reboot bootloader" then you downloads the pit file from phone to veryfite all partitions name on phone and files on computer for flash width heimadall, then flash original firmware
like me to extract original firmware on Mac OS (maybe on linux you must use other arguments for commands)
firmware to download on galaxyfirmware
for download mode press both volume buttons and put cable connected to pc
after download firmware you get it reddy for flash release firmware.zip width path of your zip
unzip -x *.zip ; rm -rf HOME_CSC* *.txt ; for f in *.md5; do tar xf $f; done && rm -rf *.md5 && unlz4 -dm *.lz4 && rm -rf *.lz4
Click to expand...
Click to collapse
then you flash it width heimdall
14 partitions in line order for flash
heimdall flash --BOOTLOADER sboot.bin --CM cm.bin --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img --VENDOR vendor.img --CACHE cache.img --ODM odm.img --OMR omr.img --HIDDEN hidden.img --RADIO modem.bin --PARAM param.bin --CP_DEBUG modem_debug.bin --USERDATA userdata.img
Click to expand...
Click to collapse