IMP NOTE : Use " python-2.7.xx" ,latest version otherwise extractor will led to undesired output like this one https://forum.xda-developers.com/showpost.php?p=72165633&postcount=295 and extractor supports android 7.1.2(updated on 18-May-2017)
Extractor of system.new.dat of Marshmallow and Lollipop ROM's
{
"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"
}
DOWNLOAD
OLD
Extractor 1.0
or
Mirror
Extractor 2.0
Extractor 3.0
UPDATED
Extractor 4.8 (Updated on 18-May)
SOURCE
$GIT-HUB Contribute!
Changelog -> https://github.com/matriex/System_Extractor-WIN/commit/4b94cde74f63f6f1ff21b8c745b306326b15cb5a
Alternative of repack, if the repack script doesn't works with your system folder then try this script SCRIPT / GUIDE
How to
Extract ext4-Image files
Download Imgextractor.exe binary from the link
https://github.com/matriex/System_Extractor-WIN/blob/master/bin/Imgextractor.exe
1. Create a folder named ext and copy the binary to ext folder
2. Copy your image file ,say "system_1.img" to ext folder
3. Select the ext folder , hold the shift (right) click RMB
4. Select "Open command window here"
5. Then type this command on CMD
Code:
Imgextractor.exe system_1.img -i
6. The files will be in "system_" named folder.
NOTE:You should rename IMG file to system_1.img before doing anything
Extract *.DAT files
Users, The extractor works with nought 7.0.0 and 7.1.1 perfectly (tested with CM14.1-2016-12-12 & aosp_7.0_2016-09-19), If you encounter errors then please install python and then try extracting again
Method I
Download and run the extractor .
METHOD II (command line)
Use python 2.7.xx
1. Download zip and extract sdat2img.py binary from the link
https://github.com/xpirt/sdat2img/archive/master.zip
2. Create a folder "ext"
3. copy "sdat2img.py", "system.transfer.list" and "system.new.dat" to ext folder
4. Open cmd on "ext", (by selecting and holding shift , you will find "Open command window here")
5.Type this on command window
Code:
python sdat2img.py system.transfer.list system.new.dat system.img
6. After that you'll find system.img on that folder, that image file is ext4 image file and can be extracted by this guide
http://forum.xda-developers.com/showthread.php?t=2285831
END OF SUPPORT I DON'T HAVE ANY METHODS LEFT AND PLESE ASK PROBLEMS RELEATED TO ANDROID 6.0 ONLY
Repack *.DAT
/*Repack will or will not work, Don't panic if it not worked, You can still use folder =) */
For flashing xyz_ROM.zip with dat files , you need to modify updater-script
Script, "of some roms" , b'coz some roms contains a link b/w updateR-script
and system.transfer.list. The link includes following : There is a line in
updateR-script script called
Code:
if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "36,0,32770,......,307199") == "0b20303394271424267e36a0ce7573f1b62ddc0d" then
if you found this in
updateR-script then from here follow the guide Repack_INFO.txt otherwise
directly copy system.new.dat and system.transfer.list to ROM folder and
repack/zip it and flash it.
Repack ,select from script, then choose manually (option 1)
Copy all your ROM files/subfolders(bin ,app ,build.prop etc) to system folder
Everything is expalined in extractor, read it carefully
If you found "range_sah1()" on your updateR-script then continue below, else only you have to replace system.new.dat and system.transfer.list of "xyz_ROM"
CONTINUE ONLY IF YOU FOUND RANGE RANGE_SHA1
After repack a SHA1_VALUE of system.new.dat is generated and file is created as "SHA1_VALUE.txt" with "system.new.dat" & "system.transfer.list"
And follow this guide Repack_INFO.txt (attached end of this POST)
OR GIT ATTACHEDhttps://github.com/matriex/System_Extractor/blob/master/Repack_INFO.md
That's all if you need help feel free to comment
Thanks for using this method I can't say it will work , but what's wrong in trying , I tried 10 to 20 times to make it work
A LITTLE ADVICE
1. If the script failed to work ,please take a look at this post again I'm sure I've posted enough resource which will help you out in extracting and repacking .DAT files .
2. Please keep this thread clean.
3. Please don't quote whole thread(use tags).
4. I take no responsibility of repacking system.img!
5. For Linux users :https://github.com/matriex/System_Extractor-Linux/blob/master/README.md
6. Use Python 2.7.x or otherwise extractor will not work Do not use python 3.0 or update sdat2img.py binary!
Thanks to @xpirt for sdt2img
Repack_INFO.txt (GIT-HUB, clear view)
Any possible way to put it back?
? if possible Or why don't you flash it directly by folder
matrixex said:
Wait comming soon if possible
Or why don't you flash it directly by making some changes in updater-script
Click to expand...
Click to collapse
I am in no dire need of it right away, I am just asking for any future need.
nicesoni_ash said:
I am in no dire need of it right away, I am just asking for any future need.
Click to expand...
Click to collapse
Hi
I have successfully created repack script for system to dat , download it and reply worked or not
Deleted
Deleted
Works well on new Nutella OTA images. Thx
tweakradje said:
Works well on new Nutella OTA images. Thx
Click to expand...
Click to collapse
Cool please give me the link to android N OTA
Sure. Here you go http://developer.android.com/preview/download-ota.html
Cheers
tools not working broo
Source
Tools not working bro
Thanks. Tested and it worked.
v3ndul said:
Tools not working bro
Click to expand...
Click to collapse
Impossible i have tried it with marshmallow and Lollipop system.new.dat files several times(truly 4-5 ROMS more than 10times) it worked without any issues please be sure that you have copied your files as stated and also match the names as stated in extractor.
Don't copy whole post just use HIDE
v3 doesnt work. when I open it (with admin rights) I see the copyright and warnings then it closes and opens a new windows. it does that again and again sort of like a loop
Abaddon said:
v3 doesnt work. when I open it (with admin rights) I see the copyright and warnings then it closes and opens a new windows. it does that again and again sort of like a loop
Click to expand...
Click to collapse
same here
edit: solved using this version
View attachment 3692066
kenzolo said:
same here
edit: solved using this version
View attachment 3692066
Click to expand...
Click to collapse
Abaddon said:
v3 doesnt work. when I open it (with admin rights) I see the copyright and warnings then it closes and opens a new windows. it does that again and again sort of like a loop
Click to expand...
Click to collapse
I am really sorry this is because i converted bat file to exe file
Just uploaded a new version of v3.0 just download it
And you will get two things
1 bin
2 system_extractor.bat
Just run system_Extractor and enjoy
v3ndul said:
Tools not working bro
Click to expand...
Click to collapse
Don't quote the op.
Hi,
I've managed to extract, but repacking is giving the following error:
Found System FOLDER
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
error: ext4_allocate_best_fit_partial: failed to allocate 584 blocks, out of space?
Click to expand...
Click to collapse
I double checked, and I haven't ran out of disk nor RAM.
Can you help me?
Thanks
pacacc said:
Hi,
I've managed to extract, but repacking is giving the following error:
I double checked, and I haven't ran out of disk nor RAM.
Can you help me?
Thanks
Click to expand...
Click to collapse
No bro you haven't ran out of disk or RAM :silly:
This problem persist due to size of your system folder i.e it must be greater than 2GB
Right?
Don't worry jusy edit my batch file code using notepad ++
Here which line you have to edit
Search this line
bin\make_ext4fs.exe -s -l 2048M system.img system
Now replace 2048M with 4096M
After that the line will look like
bin\make_ext4fs.exe -s -l 4096M system.img system
And after that save it.
Done
Reply it worked or not
EDIT ON 30/5/2016
Use new version 4.0 IT CAN CALCULATE SIZE AUTOMATICALLY NO NEED TO EDIT SCRIPT
thanks for sharing this
i'm done the following
1. unpack
2. editing system file content(replace & delete)
3. repack (without error)
4. copy 2 file (system.new.dat & sistem.transfer.list) through 7zip
is that the correct steps? i mean, after that i can flash it like other rom zip
Related
{
"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"
}
As all of you well know, Android is an open source operating system and as such the development and modding are the bread and butter for devices with this OS.
In this thread I'll explain how to extract the firmware partition containing the operating system and programs with a Windows PC.
The purpose of this thread is to share knowledge, so feel free to help me to dump device such as Acer, Samsung and Sony Ericsson, expecially I need someone that help me with Acer's .bin
1. Unpack the system partition from an HTC ROM
What you need:
UniExtract: http://legroom.net/software/uniextract (freeware)
ZipScan: http://www.zipscan.co.uk/ (shareware)
Cygwin: http://cygwin.org/setup.exe (freeware)
Unyaffs for Windows: http://goo.gl/z6yI
Download and install all the tools (Unyaffs it's a prompt executable, so it isn't installable)
Now you need an HTC ROM, download one at your pleasure from Conflipper's site: http://www.shipped-roms.com/shipped/
Once you have downloaded it, right click on the ROM executable and select Extract with UniExtract in the subfolder (v.fig1), select Isxunpack extraction and then clik on the OK button (v. fig2)
Now in the subfolder you have the various files which make up the executable, including data1.cab which is the file that we are more interested in (do not delete other files).
Open ZipScan, go to File -> Open Archive File... and browse until select the data1.cab. You should see something like this:
Extract from the cab only the ROM.zip and open this file with any archives extraction software (eg WinRAR or the same ZipScan). Inside you have various .img files which make up the ROM, but for the purposes of this guide, we need only the system.img.
Copy in a blank folder this file, unyaffs.exe and cygwin1.dll (you'll find it in C:\Cygwin\Bin).
Now open Cygwin from Start -> All Programs to ensure that its functions are integrated to the Windows Prompt and close it.
Open the Windows Prompt (Start -> All Programs -> Accessories) and position yourself in the folder containing the files using the cd command or alternatively install this .reg which allow you to open the Windows Prompt in the chosen folder by command in the context menu (Right click on the folder -> Command Prompt Here).
Now the last thing that you have to do is to give the extraction command: unyaffs system.img
Et voilà, now you have the folders containing the extracted system.
Enjoy
2. Unpack the system partition from a Motorola ROM
°°°Coming Soon°°°
°°°reserved°°°
°°°2nd reserved°°°
°°°3rd reserved°°°
Thank you! I had found a different way but this will save some steps.
mark
i will see
!!!!!!!!!!!!!!!!111
Someone once told me you can just run the .exe file, let it open, use windows to search for the rom.zip that would have been extracted into a temp folder, drag&drop to another location, then cancel the .exe again.
Haven't tried this myself though.
What else can you show us in windows?... Is it at all possible to extract ramdisc thingies from kernels so we can apply one custom kernel to other roms ourself?
... or should I bite the bullet and install/learn how to use ubuntu?
Nice initiative. Finish the guides and I'll see to it that it's stickied.
ddotpatel said:
Is it at all possible to extract ramdisc thingies from kernels so we can apply one custom kernel to other roms ourself?
... or should I bite the bullet and install/learn how to use ubuntu?
Click to expand...
Click to collapse
There are simple perl scripts kicking about to unpack/pack boot.img, so you can use them on Windows as long as you install perl first - say either via Cygwin or Active State.
I just used WinRAR to do everything that UniExtract and ZipScan can do.
...so basically you showed me that system.img can be unpacked using the linux command-line utility UnYaffs.exe, which can be run through CygWin. Thanks.
Why doesn't someone make a UnYaffs.exe for windows command line?
After I change things, how to I ReYaffs it to system.img? ...and when I re-zip it don't I have to sign it or something? If I modify an apk do I have to deODEX it first? Do I reODEX after?
I would love a quick tutorial on, say, how to change an icon for an app. Something that shows people who already know how to do this type of stuff a brief step-by-step guide to taking a [ROM], adding and deleting a few apks inside it, making a graphical change to an apk inside it (skinning), and then recooking those changes in to a new [ROM] to be shared with all.
rpmccormick said:
I just used WinRAR to do everything that UniExtract and ZipScan can do.
...so basically you showed me that system.img can be unpacked using the linux command-line utility UnYaffs.exe, which can be run through CygWin. Thanks.
Why doesn't someone make a UnYaffs.exe for windows command line?
After I change things, how to I ReYaffs it to system.img? ...and when I re-zip it don't I have to sign it or something? If I modify an apk do I have to deODEX it first? Do I reODEX after?
I would love a quick tutorial on, say, how to change an icon for an app. Something that shows people who already know how to do this type of stuff a brief step-by-step guide to taking a [ROM], adding and deleting a few apks inside it, making a graphical change to an apk inside it (skinning), and then recooking those changes in to a new [ROM] to be shared with all.
Click to expand...
Click to collapse
No ****... I was wondering why he's making it all so complicated with all these extra tools when I can click the file in Winrar (extract to...) and be done. All in ONE step for me.. LOL
For me it was more than one step because using WinRAR on system.img didn't get all the files out. Using unyaffs did. But now I have a system.img from a new Android tablet and I can't get anything out of it other then the META-INF directory using WinRAR, Unyaffs, or UniExtract. Anyone have any clue how to get in to those?
...and I still want an easy tutorial on how to re-assemble a flashable system.img / update.zip once I change some stuff in there.
I really hope one of those reserved spots is for the newer Samsung phones. What really cheeses me, though, is that I had that explained to me once, and I can't find it, and didn't write it down
I've compiled both unyaffs.exe, mkyaffsimage and mkyaffs2image for cygwin, with the DLL you can use them on Windows too. Sadly, I don't know too much about C and C++, so I can't make it work, but maybe I will try to compile them for Windows, and with some bugfixing, MAYBE it will run.
Samsung did not use the usual yaffs image (for Galaxy S at least), but their own format, what can be easily extracted. I will post some more about it as soon as I get back to windows, recompile the executables and upload them.
i wana extract boot.img , but i have some error
$ gunzip -c boot.img | cpio -i
bash: cpio: command not found
gzip: boot.img: not in gzip format
Click to expand...
Click to collapse
I had some problems with unyaffs. This version posted on 1st page is bugy, if you have same problem try...
hmmm i have i more problem: To prevent spam to the forums, new users are not permitted to post outside links in their messages.
so sry guys i can't help you right now
rpmccormick said:
i just used winrar to do everything that uniextract and zipscan can do.
...so basically you showed me that system.img can be unpacked using the linux command-line utility unyaffs.exe, which can be run through cygwin. Thanks.
Why doesn't someone make a unyaffs.exe for windows command line?
After i change things, how to i reyaffs it to system.img? ...and when i re-zip it don't i have to sign it or something? If i modify an apk do i have to deodex it first? Do i reodex after?
I would love a quick tutorial on, say, how to change an icon for an app. Something that shows people who already know how to do this type of stuff a brief step-by-step guide to taking a [rom], adding and deleting a few apks inside it, making a graphical change to an apk inside it (skinning), and then recooking those changes in to a new [rom] to be shared with all.
Click to expand...
Click to collapse
+1000
.
WinImage can extract the .img.
Unfortunately, I don't think it can repack them properly.
Hi friends of XDA,
this tutorial is for friends who want to develope a rom from ftf file but are not able to decrypt the system.sin file successfully or having
problems with creating a simple zip file of the rom to flash with clockworkmod. i know there are a hand full of tutorials for this but this is my version.
very complete and extremely noob friendly (i think).
I have attached this guide as text file at the end of this post(suitable for offline reading)(use it with notepad ++ for
proper format)
#include
/*
* I am not responsible for bricked devices, dead SD cards or
* thermonuclear war.
* do some research if you have any concerns.
* YOU are choosing to make these modifications.
* yes, i copied this disclaimer from FXP because it is cool and i am lazy!
*/
okay now lets get started,
This tutorial assumes that you have a copy of the ftf file of the phone for which you want to create a flashable
rom (.zip) file.
steps for extracting the system.sin and decrypting it,
1. open the appropriate ftf file with any archive extractor application (7zip recommended).
2. you will find about 11 .sin files (number of files may vary).
3. we only want the system.sin file so extract it.
4. after extracting the system.sin file (for me after extraction it was around 341 mb)(it may vary for your phone).
5. there are two ways to decrypt the system.sin file
5.1 using a simple command line program (aiup.exe)(this method is simple and one step process).
5.2 using flashtool and unyaffs tool (claimed that this always works).
5.1 using a simple command line program (aiup.exe):
5.1.1 note: many of them are reporting that this method is not working with ics system.sin files but personally it always
worked for me with both gb and ics system.sin files.
5.1.2 create a folder and put just the system.sin file inside it. it is easier to use a simple path, for eg., create a folder
"c:\system" and put system.sin in there. in my case the path for the system.sin will be "c:\system\system.sin"
5.1.3 download the attached aiup.exe program (extract it from the attached zip) and place it with the already
extracted system.sin file (in my case i extracted as "c:\system\aiup.exe")
5.1.4 open command prompt by windows+r and typing cmd and press enter.
5.1.5 type the path for the aiup.exe in the cmd window and press enter (in my case i will type as "c:\system\aiup.exe")
5.1.6 you will get the aiup window now type "system.sin 4096 c:\system\system\"
(remember the aiup.exe and system.sin should be in the same folder)
5.1.7 the above step explained:
system.sin - we are typing system.sin in the aiup command window because we want to decrypt the system.sin, for
this to work the system.sin file and aiup.exe has to be present in the same folder. if system.sin file is
present somewhere else then in aiup.exe command window instead of typing system.sin you have to
replace it with the path to system.sin file.
4096 - it defines the page size of the system.sin file where it can be anything from 2048, 4096 or 8192
(if you get a page file parameter wrong error then try with another page file size as described above).
c:\system\system\ - it defines where the files has to be extracted it can be anywhere according to your
convinience.
if it is working then you will be having a blinking cursor in the aiup command window.
wait for some time as the system.sin file is being extracted. after extraction it will say done.
now go to the extracted folder which you defined above (in my case it is "c:\system\system\") and check whether
system.sin file is extracted to a seperate "system" folder.
5.1.8 if you find nothing there or a empty folder the try the step 5.1.6 with another page file size. if all page
file sizes fail with empty folder or with page file parameter error then you will have to use the alternative
method to decrypt and extract system.sin file (see 5.2)
5.1.9 upon succesful extraction of system.sin file using aiup.exe jump to step 6.
5.2 (alternative method) creating a system dump using flashtool and extracting the dump using unyaffs tool:
note: if aiup.exe method fails then we have to use flashtool and unyaffs to decrypt and extract the system.sin
file which is supossed to be always succesful unlike the aiup.exe method.
5.2.1 download latest flashtool from here and download unyaffs from here (if the links are broken search the forum)
5.2.2 now follow steps from 1 to 4 and and 5.1.2 (extract system.sin from ftf file)
5.2.3 open flashtool and click advanced>SIN editor.
5.2.4 sin editor window gets opened, type the path to the extracted system.sin fie in appropriate box
(in my case "C:\system\system.sin")
5.2.5 now click "dump data" in the sin editor window.
5.2.6 wait for it to dump the system.sin file data.
5.2.7 After completion of the process (check the flashtool log window) you will get two files created in the folder
(in my case "C:\system\") one will be "system.partinfo" and other will be "system.yaffs2"
5.2.8 now unyaffs tool has to be used on the system.yaffs2 file. download unyaffs tool and extract the files where the
system.yaffs2 file is present (in my case "c:\system\")
5.2.9 after extracting the two files in the unyaffs archive, the folder ("c:\system\") should contain the below files
cygwin1.dll
system.yaffs2
system.partinfo (not actually requiered)
unyaffs.exe
5.2.10 open command prompt (step 5.1.4)
5.2.11 type the following command "path_to_unyaffs_program\unyaffs.exe system.yaffs2"
(in my case "c:\system\unyaffs.exe system.yaffs2") and press enter.
5.2.12 wait for some time untill the process gets completed then you will find the extracted system files
in the appropriate folder (in my case "c:\system\")
5.2.13 now create two folders, parent and child (folder inside folder) . name the main folder (parent folder) as whatever you want
(in my case "working_folder") and the folder inside it (child folder) SHOULD BE COMPULSORY NAMED as "system" (all lower case letters).
5.2.14 now select all the extracted folders and files which were extracted by the unyaffs tool
(in mycase they are present in "c:\system\") and exclude "cygwin1.dll" "system.yaffs2"
"system.partinfo" "unyaffs.exe" (exclude all the files and folders which were not exracted by the unyaffs tool)
and move all the files and folders extracted by the unyaffs tool to the "system" folder created in step 5.2.13
Now as the system folder has been created from the system.sin let us shift our focus to "META-INF" folder.
6. here you will need to use a custom rom specific for your device (i recommend using the rom claimed to be popular for your
device).
7. after downloading the custom rom (.zip file) open the rom (.zip file) and extract ONLY the "META-INF" folder from the rom.
8. move the extracted "META-INF" folder to the "working_folder" created in step 5.2.13
9. now the "working_folder" should contain only the following two folders in it
system (collection of files and folders extracted by unyaffs tool as explained before)
META-INF (extracted from custom rom (step 6 - 8))
Creating flashable zip:
note: I strongly recommend going through the updater-script (using a text editor) (notepad++ recommended) present in
"META-INF\com\google\android" before creating the flashable zip because it may contain missing file permissions and/or
unwanted junk code for files which are not present in your rom because it was not created for your rom it was created
for the custom rom (remember extracting the META-INF folder from the custom rom?). the updater-script and the
update- binary has to be from the same rom as different updater-script and update-binary may throw errors in clockworkmod.
10. now select both the "system" and "META-INF" folder inside the "working_folder" and use 7zip (recommended) or winrar
to create a .zip archive and set the compression mode to STORE (very important).
11. The above created .zip can be readily used with clockworkmod for flashing the rom or with android kitchen by dsixda for
rooting the rom and modding etc.,
HAPPY FLASHING!
CREDITS:
authors of flashtool
authors of aiup.exe
authors of unyaffs tool and adridu52 for uploading it
dsixda for his awesome noob friendly kitchen!
FXP for the disclaimer!
(please pm me if i have missed you out!)
please post your comments and questions below..........
PRESS THANKS IF I HAVE HELPED YOU!
Nice tut my friend... Tha second method works I can confirm dat!! When I use tha first method den, it didn't work so I search for another method & I got tha second method & it works fine!!!
To save stress of typing path, goto tha folder created where aIUP.exe is present, hold shift key & right on blank area, yhu will see command prompt, click on it to open command prompt having tha folder path already!!! Guys if dis method works for yhu dnt hesitate to press thanks for OP.....
whalesplaho said:
Nice tut my friend... Tha second method works I can confirm dat!! When I use tha first method den, it didn't work so I search for another method & I got tha second method & it works fine!!!
To save stress of typing path, goto tha folder created where aIUP.exe is present, hold shift key & right on blank area, yhu will see command prompt, click on it to open command prompt having tha folder path already!!! Guys if dis method works for yhu dnt hesitate to press thanks for OP.....
Click to expand...
Click to collapse
thanks whalesplaho!
and about the right click cmd thing, it doesn't work with win xp so i mentioned a universal method to open the command prompt
gouthamthemostwanted said:
thanks whalesplaho!
and about the right click cmd thing, it doesn't work with win xp so i mentioned a universal method to open the command prompt
Click to expand...
Click to collapse
My pleasure buddy... Oooooooopsssss, didn't know dat!
gouthamthemostwanted said:
thanks whalesplaho!
and about the right click cmd thing, it doesn't work with win xp so i mentioned a universal method to open the command prompt
Click to expand...
Click to collapse
very nice tut..
.
some screenshots will make it much more better.
sandy7 said:
very nice tut..
.
some screenshots will make it much more better.
Click to expand...
Click to collapse
Or maybe video tutorial will be good
Sent from my Nokia 3310 using Tapatalk 2
right now i'm not havin my pc once i get it to work, i'll update my post with screen shots!
chepoz said:
Or maybe video tutorial will be good
Sent from my Nokia 3310 using Tapatalk 2
Click to expand...
Click to collapse
u will get video tut in this thread..http://forum.xda-developers.com/showthread.php?t=1661770
gouthamthemostwanted said:
right now i'm not havin my pc once i get it to work, i'll update my post with screen shots!
Click to expand...
Click to collapse
better, that will make tha tut more noob-friendly!!!
Good work bro
Sent from my MANGO using Tapatalk 2
bandarigoda123 said:
Good work bro
Sent from my MANGO using Tapatalk 2
Click to expand...
Click to collapse
Thanks friend
hit thanks if I've helped!
sent from my smultron
Help
pitchblack5691 said:
Thanks friend
hit thanks if I've helped!
sent from my smultron
Click to expand...
Click to collapse
I made a rom using system folder and it is flashable..
The problem is when i boot my rom doesn't detects my sim card...
When i see closely in my ftf i see boot folder and boot_delivery.xml
i suspect the reason is somewhere behind this...
Do you have any idea..
Its a new ftf for sony xperia M C1905
Here is a screenshot:
{
"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"
}
Is my unlocked bootloader lose if i flash with this flashable zip?.
Sent from my Xperia Mini Pro using Tapatalk
Flashtool-No "Dump data" menu
Hello,
I'm using the latest Flashtool (0.9.18.5) and Sin Editor has no "Dump data" item.
The items are: "dump header", "Dump raw", "Extract data", "Advanced" (see attached picture)
I've tried all of them and was not able to generate any yaffs2 file.
Any idea ?
Thanks
We have 3 major works here... So I gonna to make it seperated
-1st post is HOW TO EXTRACT kernel.img (boot.img)
-2nd post is HOW TO CONVERT PICTURE FILE to BOOT.RLE
-3rd post is HOW TO REPACK THE KERNEL PAKAGE into boot.img
Requiredment
-Window machine
-installed cygwin
-the full boot.img/kernel (some kernel won't work because there is no full pakage/ i mean we can't)
-bootimg.zip (tool for UNPACK and REPACK kernel)
-boot_screen_logo_creation_package.rar
Thank and Credit
i- Credit to DooMLoRD Recognized Developer over most of XPERIA devices for his own tool and tutor that I learned before
ii- Credit to jimbo77 Senior Member for his tutorial that I used and learned and tool for unpack and repack
ii- Don't forget to give them a thanks meter
=============================================================================
Here we go
1-This section I will show u how to unpack and repack the boot.img
just see from original thread by jimbo77 from here and download the UNPACK and REPACK tool by him HERE
this is a fast guide from me:-
1-extract the bootimg-tools.zip into new folder (name it 'boot' folder)
2-move it into cygwin directory (cygwin/boot)
3- move your fav kernel into same directory
4-run cygwin.bat
cd /boot
Click to expand...
Click to collapse
{
"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"
}
5-Now, unpack your boot.img by running the following command:
./extractboot boot.img
Click to expand...
Click to collapse
If your output looks like this, then the extraction has worked correctly! Note that the Command Line string has also been read from the source file, this will be used later when you go to re-pack your file.
Your script folder should now look like this:
boot.img-kernel is the compiled kernel blob that was inside the source boot.img, if you want to replace the kernel with another compiled kernel image, you can replace this file with another one (but leave the file name the same)
boot.img-ramdisk.gz is the gzipped ramdisk image which has been split from the boot.img, you should leave this file alone.
The “out” folder contains the EXTRACTED ramdisk, and this is where you should make your changes to the ramdisk.
Important Note!
Remember, when editing files in the ramdisk through Windows, such as init.rc, Windows notepad will not format the files correctly, making them almost impossible to read, wheras Wordpad will LOOK like it is formatting the files correctly, if you save one of these files from the Wordpad application it will BREAK the file and it will no longer be able to be read correctly by Android. To edit these files you MUST use an editor such as Notepad++ which you can download for free.
AGAIN...
Special thanks/credit to jimbo77 for his excellent guide
So.. NEXT step to change a kernel logo is here
Requiredment
1-a picture what are u like to look into the 1st boot screen (kernel logo) (make sure it size/resolution same your device resolution)
2-boot_screen_logo_creation_package.rar
3-some infos and knowledges here
4-window machine like i explained on 1st post
My quick guide
-extract the tool.rar
-move extracted files into new folder (name it 'rle' folder without quote)
-move into cygwin folder (to make it easy to follow my simple guide)
-copy your own logo.png (a picture u want to use on a kernel) into same rle folder
(for 4 steps above it shold look like tis)
-now launch cygwin.bat
cd /rle
Click to expand...
Click to collapse
./convert_image_to_rle.bat logo.png
Click to expand...
Click to collapse
Ah...my mistake..don't forget to move/copy/replace new logo.rle into
C/cygwin/boot/out/ramdisk/here
if you done good...follow next step on next post (to repack your moded kernel)
Last step before you flash a new look kernel (boot.img) is
Repack your moded kernel
./packboot
Click to expand...
Click to collapse
One thing to note that people may mention in other guides, is that when packing boot.img files, you will usually have to declare a base address, and a command line to the packaging tool. This set of scripts reads the existing command line and base address from the boot.img file you originally provided at the time of repacking, so always make sure you leave your original source boot.img file in the folder and do not re-name it after extraction, your newly created boot.img file will be named boot_new.img and will NOT overwrite the original.
Done! If your screen looks like the image above, then you should now have a freshly created boot_new.img file, ready to be flashed to Android for testing, you can now go ahead and flash it through FASTBOOT one thing I'll recommend though is to first do
I need this for an extra (extra thanks maybe)
(may U?)
great work man
:laugh:
i got this eror what to do?
Theliakos said:
i got this eror what to do?
Click to expand...
Click to collapse
run as administrator
Thanks for this tutorial. But how about when the ramdisk is lzma? I tried changing commands from extractboot and packboot (from "gzip.... " to "lzma........." ) everything works well, the phone boots, but I don't have recovery mode anymore. In rest the kernel is perfect. But I need recovery mode, for installing things. I guess changing the command "gzip - or gunzip, whatever" to "lzma" is not all I have to modify. Any chance for a help?:crying:
LaShto34 said:
Thanks for this tutorial. But how about when the ramdisk is lzma? I tried changing commands from extractboot and packboot (from "gzip.... " to "lzma........." ) everything works well, the phone boots, but I don't have recovery mode anymore. In rest the kernel is perfect. But I need recovery mode, for installing things. I guess changing the command "gzip - or gunzip, whatever" to "lzma" is not all I have to modify. Any chance for a help?:crying:
Click to expand...
Click to collapse
same problem
Nice and awesome tutorial brother! :good::fingers-crossed::highfive:
Deleted
yamin8000 said:
same problem
Click to expand...
Click to collapse
Finally. I made it. For lzma ramdisks use this http://forum.xda-developers.com/showthread.php?t=1659584&highlight=lzma but I modified it to something like this (see attachment). All credits must go to the original developer, I only changed some "gzip -c" word to "lzma -dc". And I managed to modify any kernel with lzma compressed ramdisk. :good:
LaShto34 said:
Finally. I made it. For lzma ramdisks use this http://forum.xda-developers.com/showthread.php?t=1659584&highlight=lzma but I modified it to something like this (see attachment). All credits must go to the original developer, I only changed some "gzip -c" word to "lzma -dc". And I managed to modify any kernel with lzma compressed ramdisk. :good:
Click to expand...
Click to collapse
So all the step is the same with the one on the OP except we need to change gzip -c into lzma -dc?
Sent from my ST15i using xda premium
Singgih4050 said:
So all the step is the same with the one on the OP except we need to change gzip -c into lzma -dc?
Click to expand...
Click to collapse
Yes, but unfortunately it doesn't work with this tutorial (at least for me, because I lost recovery - In rest the kernel behaves normal, but we all need cwm recovery). It only fully works (again, for me) with that modified version of android kernel kitchen 0.3.1.
Will this method work with LOCKED bootloader?
mine can't be unlocked
No it will not working because this is tutorial about to change a kerenl bootlogo (Sony Ericsson) word on startup phone..
Your phone cant be unlocked and no chance to change/flash custom kernel with custom bootlogo.
GSUKeitarou said:
Will this method work with LOCKED bootloader?
mine can't be unlocked
Click to expand...
Click to collapse
---------- Post added at 03:46 AM ---------- Previous post was at 03:45 AM ----------
Good job mate :good:
works for me after i edit bootlogo for Xperia play kernel by doomlord and i managed to enter cwm
LaShto34 said:
Finally. I made it. For lzma ramdisks use this http://forum.xda-developers.com/showthread.php?t=1659584&highlight=lzma but I modified it to something like this (see attachment). All credits must go to the original developer, I only changed some "gzip -c" word to "lzma -dc". And I managed to modify any kernel with lzma compressed ramdisk. :good:
Click to expand...
Click to collapse
thanks for the guide:fingers-crossed:
Al ok but phone not booting after bootlogo changed!!!!
Code:
[email protected] /boot
$ ./extractboot boot.img
Page size: 2048 (0x00000800)
Kernel size: 5920144 (0x005a5590)
Ramdisk size: 4617107 (0x00467393)
Second size: 0 (0x00000000)
Board name:
Command line: androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-h
cd.park=3 vmalloc=400M androidboot.emmc=true
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
13874 blocks
[email protected] /boot
$ ./packboot
Using base address 0x80200000
Using command line 'androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F
ehci-hcd.park=3 vmalloc=400M androidboot.emmc=true'
[email protected] /boot
$
Whas is my erros?? My phone can't booting after flash boot.img (new), i don't change bootlogo, only unpack and repack .Thank for help
But now WORK when i change with android kitchen =))
I've been getting this error. I'm already run as administrator. What's the problem?
This tool extracts KDZ in various parts. How to use which part, for what purpose, its your wish. I use this tool mainly for extracting BASEBAND quickly in single command. I made this tool for myself and worked for me everytime with every KDZ including V20D Hongkong P765. If it works for some more people then I will sure be happy. Experienced people are requested to please stay away and use your own methods.
Based on LGExtract method by Spyrosk's AIO TOOL FOR P990 (Optimus2x) which is very huge and hard to digest at first attempt, I stripped down his utility for our convenience of dissecting KDZ. THANKS A LOT TO SPYROSK
This is simple BATCH FILE utility which should dissect any LG KDZ file and provide us FLS, BIN, CAB, WDB and DLL files all in one folder place.
1) First unzip and copy the folder in any Drive (preferably D Drive, but its your choice)
2) If you check in Windows Explorer you should find a folder named as follows >>> "D:\KDZTOOL" or "C:\KDZTOOL"
3) Now copy your V10H_00.kdz in the same folder as shown in screenshot below.
{
"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"
}
4) Now open DOS command prompt (with Run As Administrator option) and give following DOS commands.
D:
CD \KDZTOOL
PROCKDZ V10H_00 LGP760 V10H
Click to expand...
Click to collapse
Screenshot of above...
The syntaxt of above command is as follows.
PROCKDZ <KDZFILENAME> <DEVICE NAME> <SHORT VERSION NAME>
Click to expand...
Click to collapse
PROCKDZ Command Parameters:
<KDZFILENAME> = your original KDZ filename without KDZ file extension. Do not change filename on your own.
<DEVICE NAME> = your device variant, but enter as shown above starting with "LGP"
<SHORT VERSION NAME> = your own version but enter as shown above, only version
Type Space between each parameter
Example:
D:\KDZTOOL>PROCKDZ V20D_00 LGP765 V20D
Give command and just wait for LONG LONG time until the message appears as everything is "DONE!"
Now open a new "D:\KDZTOOL\BIN" folder created inside and find all your files there (including TEMP files LGP760 _AP
[*].bin, which you can delete, if you dont want.)
FLS = Fls file is baseband file of your device.
I have not hidden the results so you can see whats happening on screen and understand the simplicity of the batch file I have updated 7Zip to latest version so CAB file extraction is much faster than before.
Check mentioned folder, all your files should be there.
Tested OK on Windows 7 64bit, should work on XP, Vista, 2K and 32 bit too. Good Luck.
READ FAQ IN SECOND POST BELOW BEFORE ASKING QUESTIONS.
FREQUENTLY ASKED QUESTION
1) Is it possible extract bin file?
Answer: No. This tool does not extract BIN. But it extracts kdz into wab, fls, bin and wdb. And at end, you get BIN file split into several parts which is used by LG Update Tool, which is useful for Rooting with Lelus Method. Also this method is useful to extract FLS file, which is baseband of your model and location.
Nevermind, found a simpler method to do this
codearm2 said:
Nevermind, found a simpler method to do this
Click to expand...
Click to collapse
oic
Is it possible extract bin file?
denzel09 said:
Is it possible extract bin file?
Click to expand...
Click to collapse
No. This tool does not extract BIN. But it extracts kdz into wab, fls, bin and wdb.
And at end, you get BIN file split into several parts which is used by LG Update Tool, which is useful for Rooting with Lelus Method.
cmahendra said:
No. This tool does not extract BIN. But it extracts kdz into wab, fls, bin and wdb.
And at end, you get BIN file split into several parts which is used by LG Update Tool, which is useful for Rooting with Lelus Method.
Click to expand...
Click to collapse
and thanks, but this is already in op. For this i did that question, if there is also a method for extract bin..
@ OP, i followed the steps correctly, but i dont get any bin folder inside the kdz tool folder. i rather get a V20A_00 zip file. Inside this zip file i get dll and wdb files. I wanted fls file, so am i doing anythin wrong?
EDIT: nvm i found my way. I extracted the wdb file and got the BIN folder.
Gh0sT.RPG said:
@ OP, i followed the steps correctly, but i dont get any bin folder inside the kdz tool folder. i rather get a V20A_00 zip file. Inside this zip file i get dll and wdb files. I wanted fls file, so am i doing anythin wrong?
EDIT: nvm i found my way. I extracted the wdb file and got the BIN folder.
Click to expand...
Click to collapse
It always works on all kdz. Mostly ppl do mistakes in syntax.
Sent from my LG-P765 using xda app-developers app
useless tool!
KDZ flash tool has the feature
@all, I request all the contributors, keep doing your work. Dont worry about people who feel jealous or who just want to be famous by indulging into confrontations. Just look at their thanks meter and yours which tells whole story. Keep doing your work without expecting returns from it. It may help one person and that is enough. XDA is for everyone from noons to devs. Thanks "All".
I use this tool mainly for extracting BASEBAND quickly in single command. I made it for myself and worked for me everytime with every KDZ including V20D Hongkong P765. It extracts KDZ in various parts. How to use which part, for what purpose, its your wish.
Can't find BIN directory
cmahendra said:
This tool extracts KDZ in various parts.
Now open a new BIN folder created inside and find all your files there (including TEMP files LGP760 _AP
[*].bin, which you can delete, if you dont want.)
Click to expand...
Click to collapse
Jedi Master cmahendra: This does not work for me. I can't locate the BIN file. I am using 32 bit Windows 8.
dm146
dm146 said:
Jedi Master cmahendra: This does not work for me. I can't locate the BIN file. I am using 32 bit Windows 8.
dm146
Click to expand...
Click to collapse
And you should inform what error you got. Just by saying "does not work", you are not helping yourself. Send more information. What error you get? At what point? What is the file name of your kdz and what is the variant model you are trying?
If you have copied V20D_00.kdz file in folder and if it is LGP765 rom, then your dos command syntax will be something like this...
D:\KDZTOOL>PROCKDZ V20D_00 LGP765 V20D
Should work. Try again and inform. (I extracted folder in D Drive hence its showing command prompt as "D:\KDZTOOL>"
This can be run from any disk drive you choose.
======================
More info...
PROCKDZ Command Parameters:
<KDZFILENAME> = your original KDZ filename without KDZ file extension. Do not change filename on your own.
<DEVICE NAME> = your device variant, but enter as shown above starting with "LGP"
<SHORT VERSION NAME> = your own version but enter as shown above, only version
Type Space between each parameter
Hope this helps.
KDZTOOL
cmahendra said:
And you should inform what error you got. Try again and inform.
Click to expand...
Click to collapse
By the way, I should have said thanks for taking the time to reply.
These are the files I find when I extract the KDZTOOL zip file: 7z.dll; 7z.exe, LGExtract.exe, and PROCKDZ.bat
I put these in the KDZTOOL folder on my desktop, along with the V201A_00.kdz file
I run the following command:
C:\Users\user\Desktop\KDZTOOL\PROCKDZ V20A_00 LGP768 V20A
I get no errors.
This is the report at the end of the exercise: "Done! Open BIN file and find all your rom dissection files."
However, there is no BIN file in the C:\Users\user\Desktop\KDZTOOL directory, and I can't find a BIN on my computer that is related to the KDZTOOL.
I had tried it earlier on the C:\ directory, to similar effect.
I have looked at the contents of the batch file. I don't see where it creates a BIN directory.
@ECHO OFF
ECHO Please wait....Starting kdz dissection!
set kdzfile=%1
set device=%2
set version=%3
lgextract -kdz %kdzfile%.kdz
7z x %kdzfile%.cab
lgextract -wdb %version%.wdb %device%.dll
cd BIN
copy /B "%device%_AP[?].bin" + "%device%_AP[??].bin" "%device%_AP.bin"
cd ..
copy %version%*.* BIN
ERASE %version%*.*
copy %device%.dll BIN
ERASE %device%.dll
cls
Echo .
Echo .
Echo Done! Open BIN file and find all your rom dissection files.
I have tried creating a BIN sub-directory in the \KDZTOOL directory but this only results in the V20A.kdz being removed from \KDZTOOL to \KDZTOOL\BIN. There is nothing else there.
dm146
KDZTOOL working!!!!
cmahendra said:
And you should inform what error you got. Try again and inform.
Click to expand...
Click to collapse
I think that I have solved the problem. The 7-Zip tool in the package was not compatible with my operating system. I edited the batch file to use 7-Zip already installed on my computer. See:
@ECHO OFF
ECHO Please wait....Starting kdz dissection!
set kdzfile=%1
set device=%2
set version=%3
lgextract -kdz %kdzfile%.kdz
C:\"Program Files"\7-Zip\7z x %kdzfile%.cab
lgextract -wdb %version%.wdb %device%.dll
cd BIN
copy /B "%device%_AP[?].bin" + "%device%_AP[??].bin" "%device%_AP.bin" BIN
cd ..
copy %version%*.* BIN
ERASE %version%*.*
copy %device%.dll BIN
ERASE %device%.dll
cls
Echo .
Echo .
Echo Done! Open BIN file and find all your rom dissection files.
After the extraction the program still reports a syntax error, but I am not sure what that is. In any event, I have dissected the kdz file. Now onto editing it so that I can root.
Thanks again; as usual you are a great mentor!
dm146
KDZTOOL working perfectly (it seems)!!!
cmahendra said:
And you should inform what error you got. Try again and inform. (
Click to expand...
Click to collapse
I think I have located the cause of the syntax error. I had removed 7z.exe and 7z.dll from the folder. I thought they would not be necessary as I am using my own installation of 7-zip. I replaced them and now no more syntax error.
I now seem to be extracting the bin files OK.
dm146
dm146 said:
I think I have located the cause of the syntax error. I had removed 7z.exe and 7z.dll from the folder. I thought they would not be necessary as I am using my own installation of 7-zip. I replaced them and now no more syntax error.
I now seem to be extracting the bin files OK.
dm146
Click to expand...
Click to collapse
I am using same 7z.exe and 7z.dll on XP 32bit and Windows 7/8 64bit without any issue. I dont know why you say 7z is not compatible for your windows. 7zip should work all versions of windows without any changes.
Install 7ZIP for Windows found on their website and try again. May be some necessary old framework is missing from your pc. On FREEWARE website, there are only 2 files to download one for 32bit and another for 64bit. I am using 64bit 7ZIP right now or just try installing 32 bit for windows to recheck.
BTW click on the website link, It says "7-Zip works in Windows 7 / Vista / XP / 2008 / 2003 / 2000 / NT / ME / 98."
All is well that ends well. Using your guides I have been able to update the ROM and now I am able to disassemble the bin files. The next step is to edit the bin so as to root the phone.
Keep up the good work.
Sent from my LG-P768 using xda app-developers app
dm146 said:
All is well that ends well. Using your guides I have been able to update the ROM and now I am able to disassemble the bin files. The next step is to edit the bin so as to root the phone.
Keep up the good work.
Sent from my LG-P768 using xda app-developers app
Click to expand...
Click to collapse
To make it more suitable for all, I have copied 32bit version of 7z.exe and 7z.dll and repacked the folder, TESTED OK. Thanks for your query. Now should work on all win versions. It was 64bit version before with bit bigger filesize.
Why 7z did not work
cmahendra said:
To make it more suitable for all, I have copied 32bit version of 7z.exe and 7z.dll and repacked the folder, TESTED OK. Thanks for your query. Now should work on all win versions. It was 64bit version before with bit bigger filesize.
Click to expand...
Click to collapse
That explains why 7z.exe didn't work for me. I have a Window 32 bit operating system.
Keep up the good work.
Dm146
Hello, everyone!
This is intended for everyone who want to modify kernels they are using. Since I could not find tutorials on how to repack kernels for our Novathor devices, I decided to write my own tutorial. Maybe there are other ways, but this is how I do it and it is 100% failsafe. I took transcendence CM 1.1.6 kernel as an example in this tutorial. So, let's start!
Requirements:
- Flashtool
- Linux (Ubuntu preferable), you can also use builduntu if you don't want to install linux to your hard drive
- Files provided in attachment
- Not to close terminal in linux at any price
- Brains
STEP 1: Unpacking
First of all, you want to unpack the kernel. This is the easiest one.
Fire up Flashtool, select tools/extractors/elf
Easy, right? Now, click on those three dots and find kernel you wish to modify. Kernel MUST have .elf extension for this to work, so if you have "boot.img" at you disposal, please rename it to "kernel.elf" (without quotes). Once you loaded your kernel, just click unpack. Do not close Flashtool yet. In it you will see logs that kernel is unpacked. Please take a screenshot of that window as we will need that report later. Screenshot should look like this:
{
"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"
}
After you have saved screenshot somewhere, look in the folder where your kernel is, and you will find two or three files additional files, sometimes even four, depending on the kernel itself. They should be named this way:
kernel.elf.ramdisk.gz (very rarely, this file may be called kernel.elf.2)
kernel.elf.Image (sometimes this file may be called kernel.elf.1)
kernel.elf.3
kernel.elf.cmd
It depends on the kernel how much files you're going to have. Now, please rename them, so that you delete kernel.elf from names. Now they should be named like this:
ramdisk.gz
Image
3
cmd
Bolded files are needed for our modifications. Now to the next step!
STEP 2: Modifying
Now that we have needed files at our disposal, it's time to do the modifications.
Image file
This file is zImage of the kernel. This is the core of the kernel, where CPU frequencies, drivers, governors, etc. are stored. This file you cannot really modify but if you have built your own specific zImage, you can replace it. I don't recommend touching this file unless you know what you're doing (in other words, unless you're developer or programmer).
So, noobs: don't modify this file; pros: Go ahead
ramdisk.gz
You want to change that sweet boot image, that's why you want to unpack kernel in the first place? On how to create boot image, go here.
This file contains the rest of the tweaks developers apply to kernel. Here you will find CWM, bootsplash image, autoroot files, etc, all depending on kernel you are modifying. Now, hot to unpack this bloody file? some suggest to use 7zip, but this way you will break symlinks and your kernel will definitely not boot. Proper way of unpacking ramdisk.gz goes like this:
First of all, boot up linux (or load builduntu into virtual machine, your choice).
We want to set up working folders, right? Fire up terminal and enter following commands, one line at the time:
mkdir kernel-working
mkdir ramdisk-working
cd ramdisk-working
mkdir ramdisk-contents
cd ramdisk-contents
Click to expand...
Click to collapse
Don't close terminal, or I will break you fingers Now in your home folder you will find folders we've just created. Nice, isn't it? Remember those files we've unpacked earlier? copy them to these folders. ramdisk.gz goes to ramdisk-working folder, while the rest goes to kernel-working folder.
Download kernel_repack.zip from the attachment und unpack files which are in it to kernel-working folder.
Now we're all set up for modifying
Go back to the terminal. Copy and paste following command and run it:
gunzip -c ../ramdisk.gz | cpio -i
Click to expand...
Click to collapse
Again, don't close the terminal. This time I will break your legs if you do so Now ramdisk.gz is unpacked in ramdisk-contents folder (which is in ramdisk-working folder). There you will find bunch of files and folders. After you have done all your modifications, it's time to pack it up. To do so, run the following command in terminal:
find . | cpio -o -H newc | gzip > ../newramdisk.gz
Click to expand...
Click to collapse
In ramdisk-working folder you will find newramdisk.gz file, besides ramdisk.gz. Copy newramdisk.gz to kernel-working folder and rename it to ramdisk.gz.
Now all files for compiling new kernel are prepared. To the next and final step.
STEP 3: Packing kernel back
In terminal, run following commands (and yes, you run cd .. twice in a row):
cd ..
cd ..
cd kernel-working
Click to expand...
Click to collapse
Remember that screenshot we've took earlier? This is where we need it Told you so
And finally, here is the mother of all commands which neatly packs all of our files back into kernel, but don't use it just yet, I will explain why:
sudo python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk [email protected],cmdline
Click to expand...
Click to collapse
Take a look at the my screenshot and you will see that each of the files have its own adress. For example Image is at the adress 0x00008000 and ramdisk.gz is at the adress 0x01000000,ramdisk and 3 is at the adress 0x00000000,cmdline. By writing proper names and adresses, I'm telling computer where to pack files inside the kernel. You will have to change adresses in this command according to your screenshot, because not all kernel have the same adresses for same files. This is the most important step because if you do this wrong, kernel will not properly compile!
If you did all the work correctly, in kernel-working folder you will find new kernel.elf file. If it was named boot.img before editing, rename it back, if it was named kernel.elf then leave as it is. If you want, you can test if you packed kernel properly by trying to unpack it in Flashtool. If flashtool reports that you have some files to unpack, than all is OK, if it reports nothing, then something went wrong.
Ta-da! Your kernel is finally packed and is ready to be flashed to your phone. Hopefully, if you didn't messed up something when you did your modifications and alterations to ramdisk.gz, it should properly boot.
You can flash kernel in your preffered way.
Final words:
I tried to make this tutorial as user-friendly as possible. It is pretty straightforward once you get into it.
I hope that I clarified some thing, and more importantly, that I helped you.
Cheers everyone, and happy, repacking/flashing/modifying
Not a bad guide! Keep it up!
Sent my Carbonised Xperia P
Nice! :good:
Another good reference for kernel unpacking is this: http://forum.xda-developers.com/xperia-u/general/tutorial-explaining-stock-boot-image-t2126924
Enviado desde mi ST25i mediante Tapatalk
great guide
I just have windows , so am i doomed ?? I just wanted to change my kernel to Candy instead of Sony
Johnt880 said:
I just have windows , so am i doomed ?? I just wanted to change my kernel to Candy instead of Sony
Click to expand...
Click to collapse
Run builduntu in virtualbox.
If i got a sony kernel that sorted with the word sony out that will do my phone ?Just a standard kernel
I didn't quite understand you, can you clarify a little?
kernel 4.4.2
is there a way to modify the kernel aosp 4.4.2. This method does not work
kosmos-2011 said:
is there a way to modify the kernel aosp 4.4.2. This method does not work
Click to expand...
Click to collapse
Try that > http://forum.xda-developers.com/showthread.php?t=2073775