Database Users

[Q] Is it spossible to chnge the system.ext2 file?

Hi,
I really like all the Android builds that use the Desire ROM as I really like the HTC Sense. However, my language isn't really supported there (The fonts exist but the formatting is bad).
I have some files that should fix the formatting, but they are meant for the original HTC Desire and are installed by going to the ROM Manager/Recovery Mode and then choosing an option called: "Install Zip from SD Card".
Since I can't go to this ROM Manager nor get into Recovery mode with the HD2 Builds I am looking for an alternate way to change the system files on the Android build I am using.
The thing is that I am having difficulties doing so.
At first I tried using EStrongs File Explorer to get root access and copy over the new files I want to change but it gave me an error that it failed.
After I couldn't make it work I started looking for ways to open and edit the system.ext2 file in Windows.
I couldn't find any program or driver that would let me change the files, but only view them so I decided to install Linux and do it from there.
I used VMware workstation to install Ubuntu on my system.
On Ubuntu I mounted the system.ext2 following the mentioned instructions here: http://forum.xda-developers.com/showpost.php?p=8001443&postcount=8
It mounted okay but it said there was 0 bytes free when I tried to overwrite the files I wanted to change.
In addition it gave me permission errors, the error was that I did not have permission to copy the files.
I am not that familiar with Linux and I tired googling for answers but couldn't find anything useful.
I would appreciate if anyone can explain how to do it, or direct me to somewhere with more details as I'm kinda stuck at the moment.
The files I wanna change are:
/framework/framework.jar
/app/.DS_Store
/app/Gallery3D.apk
/app/Mms.apk
And a few font files to /fonts
Thanks a lot!

It is best to mount the ext2 file as you suggest but instead of trying to modify the file, copy the contents into a new folder and use the genext2fs command to recreate the system.ext2 file!

Hey man, it worked perfectly.
Thanks a lot!!
By the way, is there a recommended file size for the system.ext2? Or should I just keep the original size?
Is it worth setting it bigger? Will it benefit somehow?

[GUIDE] Extract files from Nandroid backups

I have seen this asked a few times recently so I figured I would try to put together a quick and easy guide to extracting files from Nandroid backups. This guide only covers Windows, I assume if you are running Linux you can download unyaffs and compile/run it without my assistance. If you are adventurous you can install cygwin and compile unyaffs on your own (or download it at any number of sites across the internet), however I have included all the files needed to extract the files from the img files.
1. Download unyaffs along with the cygwin1.dll
2. Extract the files to a new folder.
3. Copy the system.img file from the ROM or your Nandroid backup to the folder you extracted unyaffs.exe and cygwin1.dll to.
4. Open a command prompt and cd to the folder containing the three files. If you are on Windows 7 you can just navigate there with Windows Explorer and in the URL bar type cmd to open a comman prompt in that location.
5. Type unyaffs system.img
You have now extracted all the files from the system partition of your Nandroid backup. The APKs are in the /app folder and some apps require library files that can be found in the /lib folder. For example: Swype.apk requires that libSwypeCore.so be in the lib folder for it to work properly.

I get an "end of image" message and no folder is created with the extracted files.
I am trying to recover some photos from my Gallery, which I presume is in data.img - but no matter what I try to extract, I get "end of image"
any ideas?

Is the system.img the only thing you can open with this or can you open the data.img or the wimax.img also?

Lock-N-Load said:
I get an "end of image" message and no folder is created with the extracted files.
I am trying to recover some photos from my Gallery, which I presume is in data.img - but no matter what I try to extract, I get "end of image"
any ideas?
Click to expand...
Click to collapse
Your photos should be on your MicroSD card, not on one of the system partitions. Look in SDCARD:\DCIM\100ANDRO, your photos should be there.

cruise350 said:
Is the system.img the only thing you can open with this or can you open the data.img or the wimax.img also?
Click to expand...
Click to collapse
I want to know this also

Seems to work ok for me for data.img and system.img, but not wimax.img or boot.img.

Yep, I tried that too...worked.

Is there a command to repack the system or data image after you have unpacked and played around with them???
I am pretty sure that my issue is within the data file...I removed what I think caused the problem but how do I repack it all to put it on the sd card and try it out?
thanks

Does anyone know a command to repack the files???

Worked for me.
Pretty much my whole family has Evo's. theyre all rooted too thanks to me but in my experimenting, i lost the 4G keys to mines. so i troubleshooted. i put Amen Ra's recovery on my brothers phone, and nandroid'ed only the wimax. put the entire folder for that backup on my sdcard on the spot where u would find ur backups, ran Amen Ra on my Evo. and bam. working 4G. u just cant use them at the sametime cuz it interfears.

Oh ok cool.
Is there anyway to pack the files on windows
I want to see if my phone will boot now that I got rid of some programs I believe to be causing it to bootloop

Stupid question. Don't mind me.

Awesome this works Thanks allot

how can I extract /data/system to then package back as either
* SBF
or
* update.zip
to write to another identical phone?
re
http://forum.xda-developers.com/showthread.php?p=17217163#post17217163
ubuntu fyi

I've extracted *.smg files from a SBF Rom File. I'm willing to extract Stock Apk's from it.
Now, my Unyaffs is in the same folder of the SMG files such as cygwin1.dll, however when i try to execute "unyaffs cg39.smg" I receive the following:
8 [main] unyaffs 5960 handle_exceptions: Exception: STATUS_ACCESS_VIOLATIO
N
2790 [main] unyaffs 5960 open_stackdumpfile: Dumping stack trace to unyaffs.e
xe.stackdump
the log says:
Exception: STATUS_ACCESS_VIOLATION at eip=004010B0
eax=444E1A20 ebx=0000001A ecx=FFFFFFE4 edx=00801322 esi=0040130E edi=610E21A0
ebp=0022EE88 esp=0022EE50 program=C:\Motorola\unaffys\teste-extracted\unyaffs.exe, pid 4708, thread main
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame Function Args
0022EE88 004010B0 (0022EEE9, 00000000, 00000000, 00401333)
0022EEB8 004013AF (00000002, 00800180, 00800090, 610A5E22)
0022EFA8 61004DD2 (0022EFC0, FFFFFFFF, 77A651CE, 00000000)
0022FF58 6100594F (00000000, 00000000, 00000000, 00000000)
End of stack trace
I've tried to regsrv32 the DLL and also receveid error as a invalid Dll. Does anyone have an idea?
I'm looking for stock Phone, Contacts and the keyboard apk, by the way, anyone knows the keyboard apk file?
thanks

Thanks
Sent from my PC36100 using Tapatalk 2

hi guys,exist a new link for this tool or another tool for open .img files?
thanks in advance

Help !!! Problem with mkfs.yaffs2 and large image size?

I have a problem when make img file.
unyaffs img file create all folder and files from system.img. This stuff work without any issue.
Size of this folders and files is 317.4 MB.
When start to create new img file with mkfs.yaffs2, size of new img file is 2GB.
How to resolve this problem and create image file with properly filesize?

FileFixer said:
I have a problem when make img file.
unyaffs img file create all folder and files from system.img. This stuff work without any issue.
Size of this folders and files is 317.4 MB.
When start to create new img file with mkfs.yaffs2, size of new img file is 2GB.
How to resolve this problem and create image file with properly filesize?
Click to expand...
Click to collapse
You're doing something wrong. Make sure the image you are trying to unyaffs is in its own empty folder. After unyaffs remove the .img from that folder. Then create new image file by running the mkfs.yaffs2 as follows: mkfs.yaffs2 /home/killahurtz/Desktop/location of extracted system.img/ system.img

~/Desktop/newrom$ mkfs.yaffs2 /home/filefixer/Desktop/newrom/ system.img
mkfs.yaffs2: Android YAFFS2 Tool,Build by PowerGUI
at http://www.openhandsetalliance.org.cn
Building...
Build Ok.
Into newrom folder no system.img file when go to create image. Just unpacked files and folders without system.img.
After that, system.img is corectly created but have 2GB.

FileFixer said:
~/Desktop/newrom$ mkfs.yaffs2 /home/filefixer/Desktop/newrom/ system.img
mkfs.yaffs2: Android YAFFS2 Tool,Build by PowerGUI
at http://www.openhandsetalliance.org.cn
Building...
Build Ok.
Into newrom folder no system.img file when go to create image. Just unpacked files and folders without system.img.
After that, system.img is corectly created but have 2GB.
Click to expand...
Click to collapse
Please attatch a screencap before and after you run the mkfs.yaffs2 command. Please be sure that the target directy is clearly visible.

There is the problem...
First picture is when unyaffs and second is when create image file after mkfs.yaffs2.

FileFixer said:
There is the problem...
First picture is when unyaffs and second is when create image file after mkfs.yaffs2.
Click to expand...
Click to collapse
I don't think your output path should be in the same folder you're trying to make an image from. That's the problem
Fix that and i'm positive it will work. Hope that helps.

I tried this method and system.img is created in new folder but this sistem.img no contains folders and files from /newrom folder. It contain a files from my Ubuntu system folder?!
I am confused...

ok have system.img in newrom folder in Desktop.
1.open terminal
2.cd Desktop/newrom
3.unyaffs system.img
4.now go remove the system.img file from your newrom directory
5.if you didn't close terminal type "cd.." to change path back to Desktop
6.mkfsyaffs newrom/ system.img
Sent from my HTC HD2 using XDA App

Thanks... Now it works perfect.
Now i go to write Begginerr guide for yaffs and unyaffs. It is very simple...
Best regards.
FileFixer

a beginner

there is a file called data.img . I was wondering where it is

kekelovewi said:
there is a file called data.img . I was wondering where it is
Click to expand...
Click to collapse
Its on d internet...try searching beginning with d thread which contains d build u wish 2 run on ur device. .

Maybe your are wondering why you don't see this file when you download and extract a given build ?
Thats because some builds will automatically create this data.img file during the first boot, and this is one reason the first boot takes a very long time usually.
However, some other builds will provide a pre-initialized data.img as a separate file to download (usually a zip file), and you have to manually place it (after unzip) in the appropriate location, and this has to be done before the first boot.
Thus, finally, this data.img file should be directly under the Android folder of your SD card, the very same directory where you have the clrcad.exe and haret.exe.
At least this applies for SD builds, for NAND builds I don't know if this has changed.

[Q] How do you change Kernel on SD ROM?

in http://forum.xda-developers.com/showthread.php?t=1058809
It says: "Download, unzip to your rom folder, restart twice.."
Is this just for that ROM or will it work for all?
What exactly do I do?
After unzipping, there are several levels of folders. which level goes where and does "rom folder" mean "Android" folder?

Download, unzip, copy "root" & "update" & "zImage" to your Android folder, reboot twice, have fun !
ROM folder = "Android" (or whatever your ROM's folder is called)
Just copy the folders and the file to the top level of your folder .
And a Kernel (technically) should work with all ROMs.
Your sd card should look like this:
G:/SDCARD/Android/root/
G:/SDCARD/Android/update/
G:/SDCARD/Android/zImage

Well it depends on your build, what build are you using?
because some builds have different path than Android, and others don't support putting new files in the folder build as far as I can remember.
so some require you to put these files manually using ADB push commands, or root explorer and apps of the like.
Not all builds support different kernels, so make sure you check if the kernel you want is compatible with the build you have.
and make a backup before you do anything or you might regret it.
manual kernel installation means:
copying the zImage to the build folder to replace the original, run android then push/copy-paste kernel files each to it's respective folder on the device. it's not that hard to be done.