Develop Bugs

How to make custom Odin images

Hey folks,
XDA is down, so I can't tell how much has been done, development wise, but its looking bleak. I'd like to help out, even though I do not have the device.
First, we need to get some Odin images going. This is BEST done with somebody who has a stock, but rooted, Samsung Continuum.
This has been adapted from here:
Creating Custom ROMs/Backups for Odin - Android Forums
First, you need to root, via either one of the one click methods, or z4root.
Then, you must setup adb, if you haven't already. Alternatively, you could be a masochist and use the terminal on the device, downloaded from the market.
As root (#)
To backup kernel parition:
Code:
dd if=/dev/block/bml7 of=/sdcard/kernel bs=4096
To backup recovery partition (probably the same as the kernel):
Code:
dd if=/dev/block/bml8 of=/sdcard/kernel bs=4096
To backup system:
Code:
dd if=/dev/block/stl9 of=/sdcard/system bs=4096
Backup the kernel, system, and recovery images from your sdcard to your computer. Make backups!
Rename kernel to: zImage
Rename recovery to recovery.bin
Rename system to factoryfs.rfs
The next part requires linux, OS X, or cygwin.
Cygwin
If you are using heimdall, the above images are ready for flashing.
If using Odin, we must still package them.
Code:
$ tar -H ustar -c image_1 [image_2 ...] > your_odin_package.tar
If you want an all in one package, put each image name in. if not, make one image per tar file.
Example: tar -H ustar -c zImage > zImage.tar
This would give us a zImage.tar file. Now we will turn it into a tar.md5 file, so that Odin can make sure its not corrupt before flashing.
Code:
$ md5sum -t your_odin_package.tar >> your_odin_package.tar
$ mv your_odin_package.tar your_odin_package.tar.md5
using the above example, your final file would be zImage.tar.md5.
This gets used with Odin3 v.1.30, in the PDA section. You need to install Samsung usb drivers prior to, of course, and the phone must be in download mode.
ALWAYS USE THE PDA SECTION IN ODIN.
Odin can be found here:
http://adrynalyne.us/files/odin/Odin3v1.3.exe
Download mode (on the Fascinate anyway), can be achieved by powering off device, holding DOWN volume, and plugging in the usb cable, or hitting power.
I plan on posting some other stuff here, so PLEASE, someone make these images for everyone! Its essential to have a fall back. I do not own the device, so I cannot.

I have the images and they have been restored onyo 3 devices without flaw. Ill release them tomorrow.
Sent from my SCH-I400 using XDA App

It's not my intention to resurrect such an old thread, but here's a little more info about this method.
If you're using Mac OS, the commands are a bit different.
Instead of:
tar -H ustar -c image_1 [image_2 ...] > your_odin_package.tar
tar --format ustar -c image_1 [image_2 ...] > your_odin_package.tar
Instead of:
md5sum -t your_odin_package.tar >> your_odin_package.tar
md5 -r your_odin_package.tar >> your_odin_package.tar

Pastor! thanks for the info, how do i convert the rom cwm zip i have to a flashable tar?

joshkoss said:
Pastor! thanks for the info, how do i convert the rom cwm zip i have to a flashable tar?
Click to expand...
Click to collapse
put boot.img in that tar. it is said to flash like a charm.
If you want to create flashhable kernel tar file, then download the attached tar template, and using Total Commander, copy your kernel into it. This file is OK with Odin Attached Files
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kernel_base.tar

mai77 said:
put boot.img in that tar. it is said to flash like a charm.
Click to expand...
Click to collapse
Put boot.img into the odin, and it will almost certainly fail. And way to bump a dead thread

Lol, ^
Well since this thread is bumped anyways, I guess it's as good as place as any to ask; Imnuts, do you think there is a possibility you could work your kernel magic and maybe make us one now that we have source? thanks in advance, lol
Sent from my SCH-I400 using xda premium

Peanut butter jelly time!
Sent from my ADR6425LVW using Tapatalk

trailblazer101 said:
Lol, ^
Well since this thread is bumped anyways, I guess it's as good as place as any to ask; Imnuts, do you think there is a possibility you could work your kernel magic and maybe make us one now that we have source? thanks in advance, lol
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
now i only downloaded sources and took a look at txt files. kernel sources state "HOW TO BUILD KERNEL 2.6.35 FOR SCH-I400" now i looked at imnuts kernel building guide and seen that we would need the correct initramfs for it to boot correctly? and isnt 2.6.35 a GB kernel so maybe we can do something. I will be working on BRICKYOURPHONE.tars when i get my pc back in the same town as i. I might just rent a laptop if it doesnt happen soon lol
pretty sure imnuts knows something about this... (what we would need for custom kernel and GB ASOP?)
update on me:
PC still packed, finals over, and should be grabbing my pc in a week or so before spring quarter starts ive been missing thememing and posting more relevant things lol.

[APP] aZuZu Stock zImage Splitter 4 Windows Final

Anyway this is final version of command line samsung stock zImage Splitter
THIS TOOL CAN SPLIT STOCK IMAGES ONLY!
aZuZu Samsung Mobile Stock zImage Splitter, v1.02.3f. Final. (c) aZuZu. 2011.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If this is not usefull please report to mod..

great job!
awesome!

Wow, it's nice to see some x10 xda'ers in the galaxy forums

ok. folks! new version is up.. still in alpha but now supports all three formats
stock, tegrak, and chainfire are now supported.
WARNING: i have issuses with cygwin so there is special exe file run_cpio.exe in application folder which you can run manualy to unpack chainfire ramdisk.
enjoy!

A small guide on how-to use it would be highly appreciated...

pramathesh said:
A small guide on how-to use it would be highly appreciated...
Click to expand...
Click to collapse
today i have upload new version. which can handle all three formats..
for now it is using additional argument..
so to unpack stock zImage command goes
asmzis zImage stock
so to unpack chainfire zImage command goes
asmzis zImage chainfire
so to unpack tegrak zImage command goes
asmzis zImage tegrak
old version could unpack only stock.
p.s next version will be back to old asmzip zimage becouse i will add detection for types..
plus fix for zimages w/o ramdisk.

ok. reuploaded stock zimage splitter.
fixed:
a) it doesn't use 7z no more.
b) detection of stock / custom zimage / image wo ramdisk.. so it gives nice message

Will test
Enviado desde mi GT-I9000 usando Tapatalk

Tried to unpack stock JVQ zImage but without luck:
asmzis.exe zImage
aZuZu Samsung Mobile Stock zImage Splitter, v1.02.3f. Final. (c) aZuZu. 2011.
zImage File Size : 5595 kB.
zImage Header Size : 32 kB.
zImage Type : Custom zImage or zImage w/o ramdisk.
Click to expand...
Click to collapse
Here's the link to zImage: zImage-JVQ.tar (5.47 MB)
Also tried to unpack CF-Root 3.7 for JVQ zImage but had the same error.

Bo$s said:
Tried to unpack stock JVQ zImage but without luck:
Here's the link to zImage: zImage-JVQ.tar (5.47 MB)
Also tried to unpack CF-Root 3.7 for JVQ zImage but had the same error.
Click to expand...
Click to collapse
thanks on feed back... sorry my mistake. i added to hard rule about using signature so that cf-root can't be extracted i have upload hot fix now all "stock" packed zImages should be supported. Once again sorry!

Thanks for this great tool! Is it also possible to make a repacker?

sorry..but what is this? please, explain?

aZuZu said:
thanks on feed back... sorry my mistake. i added to hard rule about using signature so that cf-root can't be extracted i have upload hot fix now all "stock" packed zImages should be supported. Once again sorry!
Click to expand...
Click to collapse
Now it works, Thanks
syamsoul said:
sorry..but what is this? please, explain?
Click to expand...
Click to collapse
Tool to unpack initramfs from kernel image. It may be helpful to diff images from different ROM releases.

bub181 said:
Thanks for this great tool! Is it also possible to make a repacker?
Click to expand...
Click to collapse
well i don't have samsung so i need read some more text lines but i will soon..

Bo$s said:
Now it works, Thanks
Tool to unpack initramfs from kernel image. It may be helpful to diff images from different ROM releases.
Click to expand...
Click to collapse
thanks...!

I'd really love to learn how to build a kernel if someone is willing to teach. I'm a quick learner.
Sent from my GT-I9000 using XDA Premium App

pramathesh said:
I'd really love to learn how to build a kernel if someone is willing to teach. I'm a quick learner.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Tutorials:
how to build android kernel
Sources (2.3.3):
[REF] Source code: Unified git repo for GT-I9000 Gingerbread kernel source - xda-developers
https://opensource.samsung.com/ => search i9000
VM's with tools for building from sources:
http://forum.xda-developers.com/showthread.php?t=1022407
http://forum.xda-developers.com/showthread.php?t=881845
If you haven't sources (Sammy 2.3.4) you can modify initramfs:
http://forum.xda-developers.com/showthread.php?t=1152740

[APP] aZuZu Stock zImage Splitter 4 Windows Final

Anyway this is final version of command line samsung stock zImage Splitter
THIS TOOL CAN SPLIT STOCK IMAGES ONLY!
aZuZu Samsung Mobile Stock zImage Splitter, v1.02.3f. Final. (c) aZuZu. 2011.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If this is not usefull please report to mod..

it is useful!!! thanks for ur work!

Thanks! Will test it later today!!

dupe post.....

i have problems with upload on server but new version can handle tegrak / chainfire..

Hi, thanks for your job
for my information, what is the purpose of a zImage splitter ?
Sent from my GT-I9100 using XDA Premium App

ok what is this thing?

Very helpful for DEVs in breaking ROMs down, kinda like "unzipping".

Thanks,
working on stock zImage KF2. (just to try it )
Is it possible to do the reverse process (on windows ) ?
I believe it's a bit more complicated (or impossible ?)
Noob question : Why decompiling a kernel when sources are free ?

i tried it but after extracting using the tool i only get empty folders ... am i doing it wrongly?

cruzzmz said:
i tried it but after extracting using the tool i only get empty folders ... am i doing it wrongly?
Click to expand...
Click to collapse
For the moment, it's working on stock zImage only

ok. folks! new version is up.. still in alpha but now supports all three formats
stock, tegrak, and chainfire are now supported.
WARNING: i have issuses with cygwin so there is special exe file run_cpio.exe in application folder which you can run manualy to unpack chainfire ramdisk.
enjoy!

sicopat said:
For the moment, it's working on stock zImage only
Click to expand...
Click to collapse
i am trying to extract the stock XXKF2 kernel
this is what i did
1. extract the .tar file
2. extract ur tool
3. copy the zImage to to ur tool folder
4. use cmd and use
Code:
asmzis zImage
all the zImage is extracted but inside all the folders are empty

cruzzmz said:
i am trying to extract the stock XXKF2 kernel
this is what i did
1. extract the .tar file
2. extract ur tool
3. copy the zImage to to ur tool folder
4. use cmd and use
Code:
asmzis zImage
all the zImage is extracted but inside all the folders are empty
Click to expand...
Click to collapse
by agrument is see you are using old version...
today i have upload new version. which can handle all three formats..
for now it is using additional argument..
so to unpack stock zImage command goes
asmzis zImage stock
so to unpack chainfire zImage command goes
asmzis zImage chainfire
so to unpack tegrak zImage command goes
asmzis zImage tegrak
old version could unpack only stock.
p.s next version will be back to old asmzip zimage becouse i will add detection for types..
plus fix for zimages w/o ramdisk.

Not to complain, but what could possibly be the use of dumping my kernels, aside from ripping my hard work off ? I mean, they are just the stock kernels + my modifications.

got error when extracting the ram disk ... 7z exe come out with error
i extract only stock zImage

cruzzmz said:
got error when extracting the ram disk ... 7z exe come out with error
i extract only stock zImage
Click to expand...
Click to collapse
i downloaded stock XXKF2 kernel what ever from here.. http://forum.xda-developers.com/showthread.php?t=1101671
also fixed error in 7z call procedure and reupload all now should be ok ...

Chainfire said:
Not to complain, but what could possibly be the use of dumping my kernels, aside from ripping my hard work off ? I mean, they are just the stock kernels + my modifications.
Click to expand...
Click to collapse
Well if they are stock kernels and somebody wanted to test cf-root with for example tegrak kernel? Shouldn't that be allowed to him / her? If not say a word and i will remove application from server. Sorry if i offended you in any way. I just thought that this appliction could be usefull.

damn server.. now patched version should be uploaded...

Thanks, will wait for the recompiling solution

[DEV] Compiling *working* a kernel from source

Has anyone done it?
I did a few runs with the m2_att_defconfig and the defconfig I pulled from the stock boot.img but I've had no luck with either. I'm fairly certain I'm repacking my boot.img back correctly, but that could be an issue as well.
I've uploaded the kernel source to github as well as the defconfig I pulled from my phone in case someone wants to save some time.
I wonder if the ominous "QUALCOMM SECUREBOOT: ENABLE" has anything to do with it too.
Anyone have any thoughts? Ideas?
Please stay on topic here
======================================================
Edit
mdeejay is a genius. It works with the following:
Code:
./mkbootimg --cmdline "console=null androidboot.hardware=qcom user_debug=31" --kernel zImage --ramdisk ramdisk.gz --base 0x80200000 --ramdiskaddr 0x81500000 -o ./boot.img

I have been getting nothing but errors, can't figure it out. I'm trying for just stock right now.
Sent from my SGH-T999 using Tapatalk 2

Romanbb
try it

Have been working on this 'problem' now for nearly a week with testers (I have the International gsm model) and no luck at all. Tried unpacking/repacking with/without the command line using manaul methods and automatic but always hit a bootloop.
I NEED to be able to work with these boot image for AT&T/VERIZON/SPRINT and also TMOBILE for my US S3 ToolKit so if anyone has any insight what is needed to successfuly repack the boot image please share. I have been working with boot images from NAND backups as that was the only image available to me until yesterday when Adam Lange published the Odin Stock Roms for all the carriers so I will have another go today with those.
@ mdeejay is that a repacked boot image for Tmobile? If so and its worked for you please could you share how you managed it?
Mark.

mskip said:
@ mdeejay is that a repacked boot image for Tmobile? If so and its worked for you please could you share how you managed it?
Mark.
Click to expand...
Click to collapse
yes. its for tmobile
i cant test. i dont have device
you can try same way http://forum.xda-developers.com/showthread.php?t=1584919 create boot img with correct offsets for sgs3
i think its useful for all msm8960 devices

mdeejay said:
yes. its for tmobile
i cant test. i dont have device
you can try same way http://forum.xda-developers.com/showthread.php?t=1584919 create boot img with correct offsets for sgs3
i think its useful for all msm8960 devices
Click to expand...
Click to collapse
Ok thanks for the info I will check it out
Mark.

mdeejay is a genius!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Romanbb said:
mdeejay is a genius!
Click to expand...
Click to collapse
Hey Romanbb I havent had a chance to look at this yet do you mind sharing the params you had to use packing the boot image.
Thanks, Mark.

mskip said:
Hey Romanbb I havent had a chance to look at this yet do you mind sharing the params you had to use packing the boot image.
Thanks, Mark.
Click to expand...
Click to collapse
already edited the OP with what I used to repack the ramdisk

Romanbb said:
already edited the OP with what I used to repack the ramdisk
Click to expand...
Click to collapse
Thanks I will give it a try when I get home
Mark.

Could you please post how you got a working build environment or the guide you used to make one? I think my Ubuntu is giving me problems.
Sent from my SGH-T999 using Tapatalk 2

brfield said:
could you please post how you got a working build environment or the guide you used to make one? I think my ubuntu is giving me problems.
Sent from my sgh-t999 using tapatalk 2
Click to expand...
Click to collapse
you are giving ubuntu problems. Linux is infallible.

The Pope of Dope said:
you are giving ubuntu problems. Linux is infallible.
Click to expand...
Click to collapse
Lol, that is great!
But seriously, I cannot get a Kernel to build. It does everything but output the damn thing lol.

brfield said:
Lol, that is great!
But seriously, I cannot get a Kernel to build. It does everything but output the damn thing lol.
Click to expand...
Click to collapse
sudo apt-get install build-essential
???

The Pope of Dope said:
sudo apt-get install build-essential
???
Click to expand...
Click to collapse
Will try this if my current adventure doesn't work

roman, can u please drop one for at&t?? I don't have computer so can't build one. So requesting you to just make one oc for att version! Thnx

Haven't got my phone yet, but been doing some reading for when I do and according to this: https://developer.qualcomm.com/sites/default/files/snapdragon-specs.pdf and your latest source edits, it doesn't look like these processors necessarily support all these frequencies (they seem pretty limited compared to the Exynos). do they hold up very well?

I compiled mkbootimg from source, and for some reason it wont let me use the --ramdiskaddr option.
If I take that out then it compiles a boot.img but it isn't bootable.

brfield said:
I compiled mkbootimg from source, and for some reason it wont let me use the --ramdiskaddr option.
If I take that out then it compiles a boot.img but it isn't bootable.
Click to expand...
Click to collapse
https://www.dropbox.com/s/rz9ymlbur0zh7ll/mkbootimg

[tutorial] Step by step method to extract ftf file and get system file from ics [ics]

Complete method to extract system files from ftf files of xperia devices for ics​​​
(For gb u can use nero young method which is simple, but for ics u will get system files from ftf by this method (for windows)u will not get extracted folder by nero young method )​
whom is this tutorial for?​​​
For those who need exact system files from ftf of SONY XPERIA smart phone ​
Click to expand...
Click to collapse
TOOLS NEEDED
Flash tool for xperia devices (get it from here( use only flash tool version 0.9.0.0):http://androxyde.github.com/)
unyaffs tool (get it from here : http://www.mediafire.com/?h631v46n8v6efe3 )
Click to expand...
Click to collapse
METHOD :
step 1:
Open the ftf file using winrar
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
step 2:
Extract which ever file u need (in this case i need system folder so i extracted system.sin )
step 3:
Open flash tool and click advanced option and then click sin editor
step 4:
Go to system.sin file from where u had extracted and open file
step 5:
Click dump data option
Wait for it to finish the process
step 6:
After finishing the process u will get two files in the folder where u r having original system.sin (one will be system.partinfo and other will be system.yaffs2 ) so tht u get yaffs2 file continue with the next step
Click to expand...
Click to collapse
step 7:
Download unyaffs tool from the link provided first and extract unyaffs.exe and cygin1.dll to c drive of ur system by making a folder named "unyaffs"
Click to expand...
Click to collapse
step 8:
Go to the folder where u get system.yaffs2 ( the file we get though the flash tool process) and copy the file
step 9:
Paste it to the unyaffs folder in "c"
step 10:
While u are in unyaffs folder press shift + right mouse button then only u will get "open command window here option", click that.... Other wise u can go to this folder using usual command method
step 11:
U will get command window inside unyaffs folder
step 12:
U should type inside the command window "unyaffs.exe system.yaffs2" (app name)(space)(name of the file u need to extract, if u need to extract kernel use tht file name here) and then press enter
step 13:
Wait for some time " until u see end of image " and u can see the extracted folders appearing in the unyaffs folder
through this method u can get any .sin file inside ur ftf
thankyou for reading my tutorial
Dont forget to press thanks ​
:d
Click to expand...
Click to collapse

Nice! thank you very much :good:

oh good job:victory:, tks so much:good:

I offer extract (step 5) only ext4.
How to save into iaffs2 ?
I Flastool v0.9.5.0

LeClair said:
I offer extract (step 5) only ext4.
How to save into iaffs2 ?
I Flastool v0.9.5.0
Click to expand...
Click to collapse
I think there is no way. You can mount the ext4 file by
mount -t ext4 -o loop yourfile.ext4 mountpoint

LeClair said:
I offer extract (step 5) only ext4.
How to save into iaffs2 ?
I Flastool v0.9.5.0
Click to expand...
Click to collapse
sorry to give the information tht use only flash tool version 0.9.0.0 .. latest version might not help u to extract .sin files and u il get an error

Instead of steps 10 - 13 you should just be able to drag the system.yaffs2 file onto the unyaffs.exe and it should automatically run it with the file as a parameter.

roninnbaby said:
sorry to give the information tht use only flash tool version 0.9.0.0 .. latest version might not help u to extract .sin files and u il get an error
Click to expand...
Click to collapse
I introduced a bug in 0.9.1 when I reworked sin extraction to extract ext4 images correctly. It broke yaffs2 extraction.
0.9.6 corrects this bug. Now you can extract any system.sin (yaffs2 or ext4 images)
FT does not convert from a filesystem type to another
for yaffs2 images, use unyaffs
for ext4 images, use mount -o loop /path/to/image.ext4 /path/to/mountpoint
Under windows, you can use Diskinternals Linux reader or Yaffey which are both freeware

Nice TUT.. But doesnt work with large files i guess i have a 900MB system.sin file which is not getting selected in SIN Editor option...
Anyway you can help me?