Related
I'm sure several people will be wanting this information, so I figured I would post it here for everyone. This will allow you to backup your system and create custom Odin images for restore purposes. For anyone unfamiliar with the Samsung system, they use Odin to flash things to the device, much like HTC has RUU and Moto has SBF. Odin files are either .tar files, or .tar.md5 files.
The .tar.md5 files are .tar files with the md5 checksum added to the end of the file. If you attempt to flash a .tar.md5 file, Odin will automatically check that the contents are what they should be before flashing and proceed with the flash if the md5 is valid, otherwise it will stop.
In Odin, you should use the PDA button for all flashing. The PIT button may be used as well, if we can get a valid .pit file for the device, but for now, PIT won't be used either. Other than PDA, Start/Reset are the only other buttons you need to worry about.
Now, on to creating the backup files. First, you will need your device to be rooted (perm or temp root will work), and you also need to have access to terminal on the phone, either via an emulator or adb shell access. To create the backup files, you won't need a Linux/UNIX system, but you will if you want to create a flashable Odin package. The following will output the files on the root of the SDCard, adjust the "of=" path if you want them somewhere else. It will also create the files for the proper filename for Odin as well. So to create the files, here are the commands you will use from root shell (#):
System:
Code:
dd if=/dev/block/stl10 of=/sdcard/factoryfs.rfs bs=4096
Kernel:
Code:
dd if=/dev/block/bml8 of=/sdcard/zImage bs=4096
Recovery:
Code:
dd if=/dev/block/bml9 of=/sdcard/recovery.bin bs=4096
DO NOT INCLUDE THE FOLLOWING IN ANYTHING BUT A PERSONAL BACKUP
Cache:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/cache.rfs bs=4096
DBData:
Code:
dd if=/dev/block/stl11 of=/sdcard/dbdata.rfs bs=4096
Data:
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/movinand.bin bs=4096
The last three files (cache, dbdata, data) may contain personal information, so do not include these 3 files in anything but a personal backup/recovery package.
To create a flashable Odin package, you need to pull all of the files off of the phone/sdcard and onto your computer. From there, you use the following to create the package:
Code:
tar -H ustar -c factoryfs.rfs recovery.bin zImage > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
If you want to include cache/dbdata/data in the above for personal use, just add them after the "-c" and before the ">".
There are other files that may be in Odin packages, but they are protected by Samsung and cannot be dumped properly. The files are the bootloader, secondary bootloader, modems, and .lfs partitions. The files would be boot.bin, Sbl.bin, modem.bin (not sure what it would be for the CDMA/LTE dual modem here), and param.lfs. It however isn't that big of an issue that these can't be dumped as the can't really be altered by normal flashing of the device, and are usually only altered via OTA updates.
Thanks for this info imnuts! I unfortunately updated to the new update and would like to go back to rooted but cant until I downgrade.
Thanks!
Thanks for posting this. I'm going to attempt to make a personal backup and then I can factory reset the phone and make a stock version for people to use. I'm haven't installed the update yet either, so I'm hoping this will let people get back to ED1. I've also been playing around with theming using the fascinate community rom theme and ninjamorph to swap files. It'll take a while, but it's currently the only way I feel safe messing with framework-res.
wynalazca said:
Thanks for posting this. I'm going to attempt to make a personal backup and then I can factory reset the phone and make a stock version for people to use. I'm haven't installed the update yet either, so I'm hoping this will let people get back to ED1. I've also been playing around with theming using the fascinate community rom theme and ninjamorph to swap files. It'll take a while, but it's currently the only way I feel safe messing with framework-res.
Click to expand...
Click to collapse
I'm definitely looking forward to having a downgrade ROM image to get back to ED1!
So how do you add the last personal 3 i just got the droid charge and i am not very familiar with samsung files i had a droid x and a thunderbolt very shortly and am familiar with ruu and sbf but how do you add cache dbdata and the other one. I meab like the actual command not the instruction to put it after c
rami98 said:
So how do you add the last personal 3 i just got the droid charge and i am not very familiar with samsung files i had a droid x and a thunderbolt very shortly and am familiar with ruu and sbf but how do you add cache dbdata and the other one. I meab like the actual command not the instruction to put it after c
Click to expand...
Click to collapse
The only thing that would change would be the tar command. If you want to include the other files, it would be:
Code:
tar -H ustar -c cache.rfs dbdata.rfs factoryfs.rfs movinand.bin recovery.bin zImage > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
You just need to pull the files from your phone and have them in the same directory that you're in in terminal, and have them named appropriately. It also doesn't matter what order they are in (that I know of), I just have them in alphabetical order for ease of reading.
So im going to try and do the voodoo lagfix for the first time ever but I wanted to make a backup. Im on ED2 and NOT rooted so how would I go about making these backups?
imnuts said:
The only thing that would change would be the tar command. If you want to include the other files, it would be:
Code:
tar -H ustar -c cache.rfs dbdata.rfs factoryfs.rfs movinand.bin recovery.bin zImage > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
You just need to pull the files from your phone and have them in the same directory that you're in in terminal, and have them named appropriately. It also doesn't matter what order they are in (that I know of), I just have them in alphabetical order for ease of reading.
Click to expand...
Click to collapse
I tried the above and I keep getting this error message in the command prompt:
'tar' is not recognized as an internal or external command, operable program or batch file.
(I'm trying this on windows 7 professional)
Any help would be appreciated, thanks!
mypantsaretorn said:
I tried the above and I keep getting this error message in the command prompt:
'tar' is not recognized as an internal or external command, operable program or batch file.
(I'm trying this on windows 7 professional)
Any help would be appreciated, thanks!
Click to expand...
Click to collapse
You wouldn't by any chance be trying the "tar" command at a windows command prompt, would you?
imnuts said:
To create the backup files, you won't need a Linux/UNIX system, but you will if you want to create a flashable Odin package.
To create a flashable Odin package, you need to pull all of the files off of the phone/sdcard and onto your computer. From there, you use the following to create the package:
Code:
tar -H ustar -c factoryfs.rfs recovery.bin zImage > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
If you want to include cache/dbdata/data in the above for personal use, just add them after the "-c" and before the ">".
Click to expand...
Click to collapse
Course you might be running Linux in a vmware or Hyper-V environment....hint?
HTH
Damn! I didn't pay attention to the second part of that sentence! Lol
Thanks for the "hint"..
Sent from my SCH-I510 using XDA App
The other option would be using Cygwin, but I've never tried it, so it may or may not work.
imnuts said:
The other option would be using Cygwin, but I've never tried it, so it may or may not work.
Click to expand...
Click to collapse
cygwin works!
Edit: Here is how:
1. Search google for cygwin - download
2. Run - you will be prompted to get packages - I assumed "archive" was a good place to start - not sure if you need this or not...
3. When complete you will see a new icon on your desktop - double-click
4. Be patient as it loads
5. Copy the files output'ed from first post to same folder on PC
6. Back in cygwin:
a. cd x: (where x: is the drive letter of the drive that has the folder with the files)
b. tar -H ustar -c cache.rfs dbdata.rfs movinand.bin factoryfs.rfs recovery.bin zImage > package_name.tar
c: md5sum -t package_name.tar >> package_name.tar
d: mv package_name.tar package_name.tar.md5
Complete output of commands:
These files are for the users to personalise their cygwin experience.
They will never be overwritten nor automatically updated.
`./.bashrc' -> `/home/UWINKET//.bashrc'
`./.bash_profile' -> `/home/UWINKET//.bash_profile'
`./.inputrc' -> `/home/UWINKET//.inputrc'
`./.profile' -> `/home/UWINKET//.profile'
Your group is currently "mkgroup". This indicates that neither
your gid nor your pgsid (primary group associated with your SID)
is in /etc/group.
The /etc/group (and possibly /etc/passwd) files should be rebuilt.
See the man pages for mkpasswd and mkgroup then, for example, run
mkpasswd -l [-d] > /etc/passwd
mkgroup -l [-d] > /etc/group
Note that the -d switch is necessary for domain users.
[email protected] ~
$ cd h:
System Volume Information
[email protected] /cygdrive/h
$ cd downloads
[email protected] /cygdrive/h/downloads
$ cd charge
[email protected] /cygdrive/h/downloads/charge
$ cd tarbackup/
[email protected] /cygdrive/h/downloads/charge/tarbackup
$ tar -H ustar -c cache.rfs dbdata.rfs movinand.bin factoryfs.rfs recovery.bin
zImage > package_name.tar
[email protected] /cygdrive/h/downloads/charge/tarbackup
$ md5sum -t package_name.tar >> package_name.tar
[email protected] /cygdrive/h/downloads/charge/tarbackup
$ mv package_name.tar package_name.tar.md5
[email protected] /cygdrive/h/downloads/charge/tarbackup
$
Hmm flash did not work with my personal data in it - got an error. Created a new .tar file with just factoryfs.rfs recovery.bin and zImage and was able to flash that. TG for TiBu!
jism31 said:
Thanks for this info imnuts! I unfortunately updated to the new update and would like to go back to rooted but cant until I downgrade.
Click to expand...
Click to collapse
How do you start doing this. How do I get to root shell (#)... Thanks
AD
I plan to get rooted on ED1 so I can get a stock image backed up, and have a clean base to work from. Still getting my head around the odin stuff first.
RaptorMD said:
I plan to get rooted on ED1 so I can get a stock image backed up, and have a clean base to work from. Still getting my head around the odin stuff first.
Click to expand...
Click to collapse
you dont have to do that its already done
http://forum.xda-developers.com/showthread.php?t=1085190
Well, I successfully followed all the instructions and have created my first ODIN flashable file, I have not tried to flash it yet. I'm just curious, I pull all the different .rfs, .bin, and zImage on this file and noticed it's about 1.8gb file. Is this normal?
Also, before I try to flash this. Should I have dissable voodoo lagfix and converted back to rfs before I dumped the files?
Thanks for all the help!
JKChad said:
Well, I successfully followed all the instructions and have created my first ODIN flashable file, I have not tried to flash it yet. I'm just curious, I pull all the different .rfs, .bin, and zImage on this file and noticed it's about 1.8gb file. Is this normal?
Also, before I try to flash this. Should I have dissable voodoo lagfix and converted back to rfs before I dumped the files?
Thanks for all the help!
Click to expand...
Click to collapse
Yes, that's normal for it to be so large as dd will dump the partition, including empty space. If you were to compress it with zip or lzma, it'd drop down considerably.
Not sure about the voodoo part as I've never dumped files from an ext4 partition. I don't see any reason why it wouldn't work, but I'd flash with caution and have another working image ready just in case.
imnuts said:
Not sure about the voodoo part as I've never dumped files from an ext4 partition. I don't see any reason why it wouldn't work, but I'd flash with caution and have another working image ready just in case.
Click to expand...
Click to collapse
Shouldn't be an issue as long as he keeps the voodoo kernel.
Sent from my SCH-I510 using Tapatalk
Anybody try this with voodoo yet ?
So i just wanted to share this info as it has been very helpful to me in my development process. When making custom recoveries you often end up with a recovery.img and with Samsung devices there isn't really a good way to flash those. The best way to flash these is to run the following on a linux box:
$ tar -H ustar -c recovery.img > recovery.tar
$ md5sum -t recovery.tar >> recovery.tar
$ mv recovery.tar recovery.tar.md5
Now you can flash that recovery.tar.md5 through Odin in the PDA tab. Im guessing you can use the same process on any .img file (userdata.img, etc.) you create but i havent tested that. Ive only tested this on recovery.img and it works great.
Sorry if this is old information but i couldn't find any posts in the Skyrocket section and just wanted to share this.
Thanks
Easiest way I've found to flash a recovery img on skyrocket is to rename recovery file to recovery.img and place it on internal SD. (This won't work if your soft bricked and a tar file will be necessary )
Then type: dd if=/sdcard/recovery.img of=/dev/block/mmcblk022 in adb shell or terminal emulator.
That should work for any of our recovery images as long as you rename it to recovery.img and put it in your internal SD. I suppose you could replace /sdcard/ with /external_sd/ if you wanted to flash from external SD. Oh and don't be supprised if you catch a little heat for posting this in dev section.
Sent from my SAMSUNG-SGH-I727 using xda premium
Noob question.... Is there a way to do this on windows vs linux?
cdshepherd said:
Easiest way I've found to flash a recovery img on skyrocket is to rename recovery file to recovery.img and place it on internal SD. (This won't work if your soft bricked and a tar file will be necessary )
Then type: dd if=/sdcard/recovery.img of=/dev/block/mmcblk022 in adb shell or terminal emulator.
That should work for any of our recovery images as long as you rename it to recovery.img and put it in your internal SD. I suppose you could replace /sdcard/ with /external_sd/ if you wanted to flash from external SD. Oh and don't be supprised if you catch a little heat for posting this in dev section.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22 bs=4096
And not sure if there is a windows way. Try googling for Windows tar and md5sum. There most likely is a way.
Sent from my SAMSUNG-SGH-I727 using XDA App
Thank you
I used your method to flash the clockworkmod touch recovery. It worked flawlessly
Sk8er, I used your method today. Its flawless dude. Thanks
Sent from my SAMSUNG-SGH-I727 using xda premium
kamgrn said:
Noob question.... Is there a way to do this on windows vs linux?
Click to expand...
Click to collapse
funny... nobody bothered to answer this.
The way to do this in Windows as I know:
1. Ensure the fastboot drivers for your device is installed.
2. Acquire the fastboot binary (this is fastboot.exe).
3. Test if fastboot can see your device. Open DOS Command prompt, go to the fastboot binary folder and run "fastboot devices" command.
Example: C:\FASTBOOT\fastboot devices ---> The output should be some sort of serial number.
4. Flash the img file you have via command "fastboot flash boot <image_filename>"
Example: C:\FASTBOOT\fastboot flash boot boot.img
jtdc said:
funny... nobody bothered to answer this.
The way to do this in Windows as I know:
1. Ensure the fastboot drivers for your device is installed.
2. Acquire the fastboot binary (this is fastboot.exe).
3. Test if fastboot can see your device. Open DOS Command prompt, go to the fastboot binary folder and run "fastboot devices" command.
Example: C:\FASTBOOT\fastboot devices ---> The output should be some sort of serial number.
4. Flash the img file you have via command "fastboot flash boot <image_filename>"
Example: C:\FASTBOOT\fastboot flash boot boot.img
Click to expand...
Click to collapse
What if this is for the note, where there is no fastboot? I can get to odin mode, or to recovery mode, but no fastboot...unless i'm missing something..??
Thanks
Thank you for the post. I used your method but to flash TWRP as follows:
1. Downloaded recovery file (openrecovery-twrp-2.2.0-skyrocket.img) for Samsung Skyrocket from TWRP website on Linux.
2. Renamed file to recovery.img
3. Ran the following commands to covert IMG file to a TAR file:
tar -H ustar -c recovery.img > openrecovery-twrp-2.2.0-skyrocket.tar
md5sum -t openrecovery-twrp-2.2.0-skyrocket.tar >> openrecovery-twrp-2.2.0-skyrocket.tar
mv openrecovery-twrp-2.2.0-skyrocket.tar openrecovery-twrp-2.2.0-skyrocket.tar.md5
4. Flashed recovery using ODIN as customary.
It worked flawlessly with no issues. I highly recommend TWRP over CWM Touch Recovery. TWRP wipes things cleanly. You DO NOT have to wipe 3x which will reduce the wear and tear on your device.
ebaul said:
What if this is for the note, where there is no fastboot? I can get to odin mode, or to recovery mode, but no fastboot...unless i'm missing something..??
Thanks
Click to expand...
Click to collapse
use samsung tool kit v2.3. i had same issue as u and this page only sort of helped me and i guessed my way to tool kit. you only need to install it and place the recovery you need to transform in its input folder, where ever you installed it. then run it and just follow the instructions its pretty easy.
Thanks for the Pakistanian guy above me for reviving this vital topic ...
this method is great :
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22 bs=4096
BUT to be sure no leftovers are there :
dd if=/dev/zero of=/dev/block/mmcblk0p22
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22 bs=4096
Can be done inside Android if you're rooted , and a terminal emulator app is installed ...
nice commands to keep in mind.
mahanddeem said:
Thanks for the Pakistanian guy above me for reviving this vital topic ...
this method is great :
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22 bs=4096
BUT to be sure no leftovers are there :
dd if=/dev/zero of=/dev/block/mmcblk0p22
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22 bs=4096
Can be done inside Android if you're rooted , and a terminal emulator app is installed ...
Click to expand...
Click to collapse
Lol
its pakistani
btw great the other method worked for you
sk8erwitskil said:
So i just wanted to share this info as it has been very helpful to me in my development process. When making custom recoveries you often end up with a recovery.img and with Samsung devices there isn't really a good way to flash those. The best way to flash these is to run the following on a linux box:
$ tar -H ustar -c recovery.img > recovery.tar
$ md5sum -t recovery.tar >> recovery.tar
$ mv recovery.tar recovery.tar.md5
Now you can flash that recovery.tar.md5 through Odin in the PDA tab. Im guessing you can use the same process on any .img file (userdata.img, etc.) you create but i havent tested that. Ive only tested this on recovery.img and it works great.
Sorry if this is old information but i couldn't find any posts in the Skyrocket section and just wanted to share this.
Thanks
Click to expand...
Click to collapse
Would it be the same approach whilst with custom zImage? and load into PDA tab? or are they any other settings to flash custom kernel with odin... I tried flashing with heimdall v.1.3.1 and 1.3.2 both version results "fail to initialise protocol". could please provide any pointes on how to flash custom built kernel image on S2 lte.
I think I finally find it!!
thank you man +1
mrbeers said:
Anyone have a CWD backup for the Repp? I am both newb & noob to the rooting scene and deleted my backup when I factory reset my phone. Any help will be appreciated. I'm gonna spam this message until I get my 10 posts then I'll post a new thread. Sorry mods! My family is without a phone until I fix this!
Click to expand...
Click to collapse
I don't recommend that if you want help
Sent from my SGH-I727 using Tapatalk 2
Huge thanks !
sk8erwitskil said:
So i just wanted to share this info as it has been very helpful to me in my development process. When making custom recoveries you often end up with a recovery.img and with Samsung devices there isn't really a good way to flash those. The best way to flash these is to run the following on a linux box:
$ tar -H ustar -c recovery.img > recovery.tar
$ md5sum -t recovery.tar >> recovery.tar
$ mv recovery.tar recovery.tar.md5
Now you can flash that recovery.tar.md5 through Odin in the PDA tab. Im guessing you can use the same process on any .img file (userdata.img, etc.) you create but i havent tested that. Ive only tested this on recovery.img and it works great.
Sorry if this is old information but i couldn't find any posts in the Skyrocket section and just wanted to share this.
Thanks
Click to expand...
Click to collapse
Hi! First of all, thx a lot really was trying to find this out for a long time. One Question i have tough. I Only used the first command and left it as a simple tar file, flashed it with odin and all was well. So what do you actally do by adding md5sum and then renaming it? Is it better to add the md5sum or does it make no difference?
again huge thanks! I always used mskip toolkit, but i like to not depend on additional software
I believe ODIN will verify the md5 sum of the .img if the .md5 file is in the tar. Just in case your .img in the tar gets corrupted. If that happens ODIN will abort the flash and report something like md5 mismatch
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
---------- Post added at 12:21 PM ---------- Previous post was at 12:20 PM ----------
So its not necessary but a good practice.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
sk8erwitskil said:
So i just wanted to share this info as it has been very helpful to me in my development process. When making custom recoveries you often end up with a recovery.img and with Samsung devices there isn't really a good way to flash those. The best way to flash these is to run the following on a linux box:
$ tar -H ustar -c recovery.img > recovery.tar
$ md5sum -t recovery.tar >> recovery.tar
$ mv recovery.tar recovery.tar.md5
Now you can flash that recovery.tar.md5 through Odin in the PDA tab. Im guessing you can use the same process on any .img file (userdata.img, etc.) you create but i havent tested that. Ive only tested this on recovery.img and it works great.
Sorry if this is old information but i couldn't find any posts in the Skyrocket section and just wanted to share this.
Thanks
Click to expand...
Click to collapse
very helpful... thx mate
That's strange but command from first post don't work for me. Tablet says about incorrect file (.img, not .img.md5). So I've modified commands to make them work with Galaxy Tab 8.9 and Odin 1.8.5:
Code:
cp recovery.img recovery.img.md5
md5sum -t recovery.img.md5 >> recovery.img.md5
tar -H ustar -c recovery.img.md5 > recovery.tar
md5sum -t recovery.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
Well I am getting a message similar to the one in the title. I just got this galaxy tab p5113 model a couple days ago and decided to go ahead and get root access as well as flash cwm recovery. Everything went well.....gained root access...bbooting into cwm recovery with no problems..
I went and rebooted the phone after all operationswere complete and I found the boot logo to be missing, and in it's place is green text that says "espresso10.jpg draw failed" .....
Now I have searched and not found a comprehensive answer or very many threads containing much useful information.
In an attempt to fix the problem I subsequently downloaded the stock p5113 firmware and flashed via Odin.....still showing the error message on boot.
This one has really stumped me!
What files could possibly have been corrupted and why wouldn't the flashing of the stock firmware fix and repair the problem.....I would assume that it would have replaced the missing files....
ssCISengineer said:
Well I am getting a message similar to the one in the title. I just got this galaxy tab p5113 model a couple days ago and decided to go ahead and get root access as well as flash cwm recovery. Everything went well.....gained root access...bbooting into cwm recovery with no problems..
I went and rebooted the phone after all operationswere complete and I found the boot logo to be missing, and in it's place is green text that says "espresso10.jpg draw failed" .....
Now I have searched and not found a comprehensive answer or very many threads containing much useful information.
In an attempt to fix the problem I subsequently downloaded the stock p5113 firmware and flashed via Odin.....still showing the error message on boot.
This one has really stumped me!
What files could possibly have been corrupted and why wouldn't the flashing of the stock firmware fix and repair the problem.....I would assume that it would have replaced the missing files....
Click to expand...
Click to collapse
First, did you factory reset then flash the file through Odin? Does the tablet boot up?
p3113owner said:
First, did you factory reset then flash the file through Odin? Does the tablet boot up?
Click to expand...
Click to collapse
Yes sir the tablet boots, and I did reset and flash in Odin.
please remember to thank me for e-peen points!
Sent from a Galaxy Nexus between here and there.
ssCISengineer said:
Yes sir the tablet boots, and I did reset and flash in Odin.
please remember to thank me for e-peen points!
Sent from a Galaxy Nexus between here and there.
Click to expand...
Click to collapse
My suggestion is to reset and flash in Odin again. Try downloading the stock ROM file again as the one you have may be corrupted.
I'm having the same issues as the OP. Sorry to resurrect an old thread but I've been searching everywhere and I can't find a fix for this. I've attempted everything stated above and still no fix. I've heard that flashing the stock param.lfs would fix this issue however I can't find the stock param.lfs anywhere. If anyone happens to have it, I'd appreciate it if they could share it out.
Code:
# ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/ | grep PARAM
lrwxrwxrwx root root 2012-09-20 15:50 PARAM -> /dev/block/mmcblk0p4
# cat /dev/block/mmcblk0p4 > /sdcard/mmcblk0p4.raw
# strings /sdcard/mmcblk0p4.raw | grep espresso
logo_espresso7.jpg
logo_espresso7.jpg
logo_espresso10.jpg
logo_espresso10.jpg
logo_espresso10.jpg
ketut.kumajaya said:
Code:
# ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/ | grep PARAM
lrwxrwxrwx root root 2012-09-20 15:50 PARAM -> /dev/block/mmcblk0p4
# cat /dev/block/mmcblk0p4 > /sdcard/mmcblk0p4.raw
# strings /sdcard/mmcblk0p4.raw | grep espresso
logo_espresso7.jpg
logo_espresso7.jpg
logo_espresso10.jpg
logo_espresso10.jpg
logo_espresso10.jpg
Click to expand...
Click to collapse
I'm sorry man, I'm not great at this. What should I do with this? Actually, what I should say is what should I do with the mmcblk0p4.raw file? Is this my param.lfs?
detninrod said:
I'm sorry man, I'm not great at this. What should I do with this? Actually, what I should say is what should I do with the mmcblk0p4.raw file? Is this my param.lfs?
Click to expand...
Click to collapse
1. The first command to know which the PARAM block device
2. The second to dump the param block device to a file
3. The third, I show you I found the logo file inside /dev/block/mmcblk0p4, my device P3100
The "#" prefix mean I run a command as root.
Open Terminal Emulator or over "adb shell", and then type "su" (without quote). Issue all my above command, write the result here. Compress your param dump file and upload it here. Probably a recovery override your param partition.
ketut.kumajaya said:
1. The first command to know which the PARAM block device
2. The second to dump the param block device to a file
3. The third, I show you I found the logo file inside /dev/block/mmcblk0p4, my device P3100
The "#" prefix mean I run a command as root.
Open Terminal Emulator or over "adb shell", and then type "su" (without quote). Issue all my above command, write the result here. Compress your param dump file and upload it here. Probably a recovery override your param partition.
Click to expand...
Click to collapse
Code:
[email protected]:/ # ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/ | grep PARAM
lrwxrwxrwx root root 2012-09-20 12:12 PARAM -> /dev/block/mmcblk0p4
This is what I get after running the first command. I then dumped the param block device to file and then ran the check on it.
Code:
[email protected]:/ # strings /sdcard/mmcblk0p4.raw | grep espresso
# strings /sdcard/mmcblk0p4.raw | grep espresso
logo_espresso7.jpg
logo_espresso7.jpg
logo_espresso10.jpg
logo_espresso10.jpg
logo_espresso10.jpg
I'll attach the resulted file in just a moment. Thank you.
detninrod said:
Code:
[email protected]:/ # ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/ | grep PARAM
lrwxrwxrwx root root 2012-09-20 12:12 PARAM -> /dev/block/mmcblk0p4
This is what I get after running the first command. I then dumped the param block device to file and then ran the check on it.
Code:
[email protected]:/ # strings /sdcard/mmcblk0p4.raw | grep espresso
# strings /sdcard/mmcblk0p4.raw | grep espresso
logo_espresso7.jpg
logo_espresso7.jpg
logo_espresso10.jpg
logo_espresso10.jpg
logo_espresso10.jpg
I'll attach the resulted file in just a moment. Thank you.
Click to expand...
Click to collapse
Here is the resulted file. Thanks again.
I also misread OP's original post stating they have a P-3113. Mine is a P-5113 however I have done the exact same steps as he did.
detninrod said:
Here is the resulted file. Thanks again.
Click to expand...
Click to collapse
Are you sure zipped the correct dump file? What I have got is empty mmcblk0p4.raw prefixed by your command!
ketut.kumajaya said:
Are you sure zipped the correct dump file? What I have got is empty mmcblk0p4.raw prefixed by your command!
Click to expand...
Click to collapse
I did something dumb and I'm not going to admit to it.. but I did end up fixing the problem. I found a .tar.md5 that can be flashed with Odin for the P-3110. I put it on my ExtSDcard and flashed my param partition using it and it fixed my issue. I got the .tar.md5 from here. I just flashed my param partition, I didn't use it to flash anything else. I really wouldn't recommend it to anyone that doesn't have a P3110, but I just ended up getting lucky. Thanks for your help ketut.kumajaya, I do appreciate your assistance with this.
detninrod said:
I did something dumb and I'm not going to admit to it.. but I did end up fixing the problem. I found a .tar.md5 that can be flashed with Odin for the P-3110. I put it on my ExtSDcard and flashed my param partition using it and it fixed my issue. I got the .tar.md5 from here. I just flashed my param partition, I didn't use it to flash anything else. I really wouldn't recommend it to anyone that doesn't have a P3110, but I just ended up getting lucky. Thanks for your help ketut.kumajaya, I do appreciate your assistance with this.
Click to expand...
Click to collapse
The file name param.lfs? Mind to share here? 637MB is too big for 8MB data
ketut.kumajaya said:
The file name param.lfs? Mind to share here? 637MB is too big for 8MB data
Click to expand...
Click to collapse
lol it's not actually mine but I'm sure it should be fine (I found a tutorial somewhere out on the interwebs). It isn't just the param.lfs, it's the FULL flash for the P-3113. I used Mobile Odin, chose the param partition, chose this image, and flashed it. It will only pull the param.lfs from the image if you only choose the param partition.
I would have used the P-5113 image to reflash my param partition, but it doesn't included it for some reason
Here's the actual param.lfs. I guess it would be a bit easier to manage then copying the full image over to an SD card.
detninrod said:
Here's the actual param.lfs. I guess it would be a bit easier to manage then copying the full image over to an SD card.
Click to expand...
Click to collapse
Just flashed this on my 3110, fixed the logo, nice one, cheers
GiggedyGoo said:
Just flashed this on my 3110, fixed the logo, nice one, cheers
Click to expand...
Click to collapse
Nice! Glad to hear it!
detninrod said:
I'm having the same issues as the OP. Sorry to resurrect an old thread but I've been searching everywhere and I can't find a fix for this. I've attempted everything stated above and still no fix. I've heard that flashing the stock param.lfs would fix this issue however I can't find the stock param.lfs anywhere. If anyone happens to have it, I'd appreciate it if they could share it out.
Click to expand...
Click to collapse
The param.lfs word guided me to the right direction: http://forum.xda-developers.com/showthread.php?t=1898377
Thank you !!!
detninrod said:
Here's the actual param.lfs. I guess it would be a bit easier to manage then copying the full image over to an SD card.
Click to expand...
Click to collapse
Just flashed my GT-P5100 and everything got fixed
Device have now right bootlogo and right charge logos without any jpg drawing errors, also my P5100 now also boots right in android instead first boot going to cwm.
I used mobile odin and used that param.lfs and now everything is normal :good:
THANK YOU !
I have a USA Galaxy Note that has been updated to UEALI3 and was rooted with chainfire's enos exploit app. I would like to dump the stock recovery partiton but I can not get it to work. I have run this command in terminal...
su
cat proc/mtd
At this point I'm told file dose not exist. I also used...
su
dd if=recovery-partiton of=/sdcard/recovery.img
This says my path is invalid. Please help, it seems many people are looking for this stock recovery for future OTA updates. I would like to provide it so it can be packaged into a Odin flashable *.tar for them and for my future use incase I want a Nandroid backup with CWR.
74 views and still no one has a answer? The recovery partiton is said to be one of the easiest to dump... I only need the revised command to enter into terminal, come on guys!
Bumping
First the disclaimer:
I am not responsible for what you do to your phone. Following these directions could cause you to brick, locust plague, or end of times. You assume ALL responsibility for what you do with this information.
Now, on to the fun stuff. I take *NO* credit for this information at all. I am a student of people far more knowledgeable about these things. However, I've managed to take what I've learned and apply it in really fun ways. For example, I have a script that takes an OTA and builds a new full ODIN image from it...with all partitions fully signed except system. Many people have asked me to "repackage it" with various requests. This tutorial is going to show how to do that.
Requirements:
o) You will need to install Cygwin. A default installation should suffice for this exercise.
o) You will need one of the ODIN TAR Full Rooted Restore images. They are gzipped to make them smaller.
Process:
o) You need to unpack the files stored inside the gzip. 7 Zip is a handy program for doing that. We need the individual partition files extracted to a work directory that can be accessed from a Cygwin command prompt. I create a C:\Android\S4_GPE directory for my own image creation tasks.
o) Once the individual files are unpacked, we need to repack them. Open a Cygwin command prompt and navigate to the directory you extracted the files to. In my case, that would be cd c:/Android/S4_GPE
Follow the directions below to repack the files as needed. I give a few examples here to show you the basics of how it's done. Basically you run each command in your Cygwin command prompt. Or you can add them to an SH script and run it that way. Whatever you feel most comfortable with.
The output of these commands is an ODIN flashable file that will install what you choose.
BOOT
filename=boot
tar -H ustar -c boot.img > $filename.tar
md5sum -t $filename.tar >> $filename.tar
mv $filename.tar $filename.tar.md5
RECOVERY
filename=recovery
tar -H ustar -c recovery.img > $filename.tar
md5sum -t $filename.tar >> $filename.tar
mv $filename.tar $filename.tar.md5
MODEM
filename=modem
tar -H ustar -c NON-HLOS.bin modem.bin > $filename.tar
md5sum -t $filename.tar >> $filename.tar
mv $filename.tar $filename.tar.md5
FULL ODIN IMAGE
filename=I9505GUEUB_FULL_ROOTED
tar -H ustar -c boot.img recovery.img NON-HLOS.bin modem.bin system.img.ext4 > $filename.tar
md5sum -t $filename.tar >> $filename.tar
mv $filename.tar $filename.tar.md5
gzip $filename.tar.md5
Those are some of the common ones. What if I wanted a "semi-full rooted image"? For instance, without the modems? You just modify this line:
tar -H ustar -c boot.img recovery.img NON-HLOS.bin modem.bin system.img.ext4 > $filename.tar
so that it becomes:
tar -H ustar -c boot.img recovery.img system.img.ext4 > $filename.tar
Of if you don't want recovery, either, and just want boot and system:
tar -H ustar -c boot.img system.img.ext4 > $filename.tar
And the rest stays the same. I really hope this helps people. I will update this post to clarify anything that's confusing and will try to help people in this thread to create whatever they need. Again, you take responsibility for anything you create using these instructions and flash to your phone.
whats the command to create a system dump to an odin compatible system.img file? been a while. i forget
This is how I do it in my script:
adb shell "su -c 'cd /sdcard; dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img.ext4'"
adb pull /sdcard/system.img.ext4
adb shell rm /sdcard/system.img.ext4
SamuriHL said:
This is how I do it in my script:
adb shell "su -c 'cd /sdcard; dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img.ext4'"
adb pull /sdcard/system.img.ext4
adb shell rm /sdcard/system.img.ext4
Click to expand...
Click to collapse
I'm a relative noob and just learning as much as I can and this is alot of great info. I am able to pull system dump and pull recovery.img from my but when I create an odin flashable recovery image (for back-up purposes) it fails auth. Is there a way to pull a signed recovery image from system? Thanks.
No. When you dd extract a partition it adds padding to it which messes with the signature. I create a signed recovery img file by patching the boot img with the recovery-from-boot.p in the OTA update. That's a lot more involved than what's in this tutorial, however.
SamuriHL said:
No. When you dd extract a partition it adds padding to it which messes with the signature. I create a signed recovery img file by patching the boot img with the recovery-from-boot.p in the OTA update. That's a lot more involved than what's in this tutorial, however.
Click to expand...
Click to collapse
Got it, thank you. I found the thread on hexediting the partition file. I will see if that works.
muniz_ri said:
Got it, thank you. I found the thread on hexediting the partition file. I will see if that works.
Click to expand...
Click to collapse
My initial results weren't very conclusive on that. I tried it with the NON-HLOS.bin file just to see if I could make it consistent with the one I create by patching, and the results were not good. There's no way to know exactly how long to make the cut. It seems like all you do is remove the trailing 00's when hexediting, but, I can tell you that's not enough to make it match. I've got more research to do on this as it would be extremely useful to be able to edit the dd extracted files to make them match the signed files. So far, that doesn't seem possible.
SamuriHL said:
My initial results weren't very conclusive on that. I tried it with the NON-HLOS.bin file just to see if I could make it consistent with the one I create by patching, and the results were not good. There's no way to know exactly how long to make the cut. It seems like all you do is remove the trailing 00's when hexediting, but, I can tell you that's not enough to make it match. I've got more research to do on this as it would be extremely useful to be able to edit the dd extracted files to make them match the signed files. So far, that doesn't seem possible.
Click to expand...
Click to collapse
That's too bad, I was also hoping removing the trailing zeros would work. Can you point me to a tutorial, etc where i can learn how to patch using the OTA files? thanks again.
muniz_ri said:
That's too bad, I was also hoping removing the trailing zeros would work. Can you point me to a tutorial, etc where i can learn how to patch using the OTA files? thanks again.
Click to expand...
Click to collapse
It's not quite as simple as that. There isn't a tutorial on it. I learned what I know from Matt Groff. It started with a thread here:
http://forum.xda-developers.com/showthread.php?t=1702233
But that thread isn't going to teach nearly enough to learn how to do this. It involves parsing the update scripts from the OTA to find the command they use to patch the actual partition and then converting that to a command to patch the file. So if you look at this command from install-recovery.sh:
applypatch EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:8036608:1ad324cf48a6e19fd402603477cd0ed8472ed863 EMMC:/dev/block/platform/msm_sdcc.1/by-name/recovery f4579fa7099942ec2f214cff81014b8e8b1a550f 8632576 1ad324cf48a6e19fd402603477cd0ed8472ed863:/system/recovery-from-boot.p
What that's doing is taking 8036608 bytes from the boot partition, ensuring it has a sha1 hash of 1ad324cf48a6e19fd402603477cd0ed8472ed863, patching it with the contents of the recovery-from-boot.p file, and then writing it to the recovery partition.
Each time an OTA comes out for our phones, I create signed recovery, modem, and non-hlos files using this process. Then I use the process outlined in this tutorial to create the ODIN tar md5 files that I post.
SamuriHL said:
It's not quite as simple as that. There isn't a tutorial on it. I learned what I know from Matt Groff. It started with a thread here:
http://forum.xda-developers.com/showthread.php?t=1702233
But that thread isn't going to teach nearly enough to learn how to do this. It involves parsing the update scripts from the OTA to find the command they use to patch the actual partition and then converting that to a command to patch the file. So if you look at this command from install-recovery.sh:
applypatch EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:8036608:1ad324cf48a6e19fd402603477cd0ed8472ed863 EMMC:/dev/block/platform/msm_sdcc.1/by-name/recovery f4579fa7099942ec2f214cff81014b8e8b1a550f 8632576 1ad324cf48a6e19fd402603477cd0ed8472ed863:/system/recovery-from-boot.p
What that's doing is taking 8036608 bytes from the boot partition, ensuring it has a sha1 hash of 1ad324cf48a6e19fd402603477cd0ed8472ed863, patching it with the contents of the recovery-from-boot.p file, and then writing it to the recovery partition.
Each time an OTA comes out for our phones, I create signed recovery, modem, and non-hlos files using this process. Then I use the process outlined in this tutorial to create the ODIN tar md5 files that I post.
Click to expand...
Click to collapse
Success! Thanks so much, just created my first signed odin image!
Theres two more ways the get signed images. One is using dd if=of with the right bs and count. For example, I extracted the stock signed PIT file for the S4 using
Code:
su
dd if=/dev/block/mmcblk0 of=/sdcard/sch1545.pit bs=8 count=580 skip=2176
you can see the thread and md5 comparisonhere The other method is hexediting but it was easier on 4.2.2 but still very doable on 4.3. You have to know what signatures look like though. Hexediting can also be useful for manually extracting the zimage and ramdisk from a boot.img
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Theres two more ways the get signed images. One is using dd if=of with the right bs and count. For example, I extracted the stock signed PIT file for the S4 using
Code:
su
dd if=/dev/block/mmcblk0 of=/sdcard/sch1545.pit bs=8 count=580 skip=2176
you can see the thread and md5 comparisonhere The other method is hexediting but it was easier on 4.2.2 but still very doable on 4.3. You have to know what signatures look like though. Hexediting can also be useful for manually extracting the zimage and ramdisk from a boot.img
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm also going to play around more with hexediting, if it will work it seems much more straightforward. Thanks again for all of the good info!
SamuriHL said:
My initial results weren't very conclusive on that. I tried it with the NON-HLOS.bin file just to see if I could make it consistent with the one I create by patching, and the results were not good. There's no way to know exactly how long to make the cut. It seems like all you do is remove the trailing 00's when hexediting, but, I can tell you that's not enough to make it match. I've got more research to do on this as it would be extremely useful to be able to edit the dd extracted files to make them match the signed files. So far, that doesn't seem possible.
Click to expand...
Click to collapse
Sam, id be glad to try hexediting the NON-HLOS.bin file and then send you the md5.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Sam, id be glad to try hexediting the NON-HLOS.bin file and then send you the md5.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll pm one to you tomorrow. I definitely am curious if you're able to md5 hash it correctly.
Pm sent. Good luck.
Sent from my SM-P600 using Tapatalk 4
SamuriHL said:
Pm sent. Good luck.
Sent from my SM-P600 using Tapatalk 4
Click to expand...
Click to collapse
How do you limit the number of bytes extracted for the mdm.bin to match the updater script's parameters? Thank you.
muniz_ri said:
How do you limit the number of bytes extracted for the mdm.bin to match the updater script's parameters? Thank you.
Click to expand...
Click to collapse
I didn't. The first signed modem bin I made was done by looking at the size in the updater script and using cygwin to copy that many bytes to a new file. From then on I just patched the previous version's modem bin and NON-HLOS bin files.
Sent from my SM-P600 using Tapatalk 4
SamuriHL said:
I didn't. The first signed modem bin I made was done by looking at the size in the updater script and using cygwin to copy that many bytes to a new file. From then on I just patched the previous version's modem bin and NON-HLOS bin files.
Sent from my SM-P600 using Tapatalk 4
Click to expand...
Click to collapse
First time quickly hexediting it I got
md5: 9616e85b765e0365e8ccd57550a715b8
Surge1223 said:
First time quickly hexediting it I got
md5: 9616e85b765e0365e8ccd57550a715b8
Click to expand...
Click to collapse
Which doesn't match the digital signature. This is what I was afraid of and what I was running into.
Sent from my SM-P600 using Tapatalk 4
SamuriHL said:
Which doesn't match the digital signature. This is what I was afraid of and what I was running into.
Sent from my SM-P600 using Tapatalk 4
Click to expand...
Click to collapse
what are you comparing the sig to?
Sent from my SCH-I545 using XDA Premium 4 mobile app