Database Users

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

HELP! cooking flashable zip into rom!!!

I am trying to take a keyboard that somebody made into a flashable .zip file, and implement it into a rom that I am working on. What I did was flash the .zip through cwm, then found the apk, backed it up, and then placed it in the /system/app folder on the new rom. The problem is as soon as the rom boots, I get a force close error. So I took a look at the .zip file, there are two folders meta-inf and system. inside system there is an app folder and lib folder. My question is can I just take the apk and lib file out and place them directly into /system/app and system/lib on the new rom? and if so do i need to do anything with the META-INF folder? any ideas would be GREATLY appreciated!!!
thanks

the META-INF folder may have some script that does some other manipulation of the filesystem or runs helper apps during installation. See what's in META-INF/com/google/android/update-script.

Creating a Flashable zip problem

Hi I created a bootanimation and want to make it flashable. I followed tutorials from the net and xda. I got two files META-INF and system.
I put my bootanimation.zip in system/media. That's all. I didn't touch META-INF .
After flashing the zip in cwm, it says Installation aborted . Need Help please...

thats because the flashable zip wasnt for your phone
status 0 - wrong update binary
status 6 - wrong update script
here is my template for you
simply download it
open it in winrar (or if using phone just unzip everything)
open the system foler
you will notice a framework folder that is currently empty
you can leave this folder as it is
just create folders to where you want to flash the file to
for example your bootanimation.zip create the following
in the system folder create a folder called media
in the media folder place your bootanimation.zip
the same is true for any other files you want to flash
if you want to flash a file to system/framework just put a file in that folder
if you want to flash a file to system/app just create a folder called app in the system folder and put what you want to flash there
if on winrar you just have to open the zip and right click and create a folder - no need to unzip everything
if on phone and you have unzipped everything just zip everything back up when done
flashable zip template can be download from here
if you are using stock rom you need to enable custom boot animations first using the custom boot enabler zip
(if you already have a custom boot animation and bootanimation.zip working in a custom rom then you dont need to do this)

Ovafloa_X said:
Hi I created a bootanimation and want to make it flashable. I followed tutorials from the net and xda. I got two files META-INF and system.
I put my bootanimation.zip in system/media. That's all. I didn't touch META-INF .
After flashing the zip in cwm, it says Installation aborted . Need Help please...
Click to expand...
Click to collapse
If just a bootanimanion, push using root browser only
Or using a another flashable bootanimation file and the replace the bootanimation.zip with yours
I attch it . Credits to its maker

works perfectly! thanks

How to create boot.img

I have some original C code, which I have compiled successfully, and like to put on my phone, SM-N900P. I downloaded a copy of stock firmware and used unmkbootimg to unpack the boot.img. What do I do from here on? I have searched online and this site. I believe I have to put my files in the ramdisk directory. What I do not know is what files go in there? Can I put .img files in there? Is there a specific order in which directory to use within the ramdisk? I read someone's post instructing me to put the .ko files in ramdisk/lib/modules directory. But the ramdisk directory I have does not have a /lib directory. Should I create one? I only ask because each phone seems to have a different setup. I basically have a zImage, dt.img, and a couple of other img files.
Even if you can not help, I appreciate if you point me to relevant useful information.
Thanks

sansari123 said:
I have some original C code, which I have compiled successfully, and like to put on my phone, SM-N900P. I downloaded a copy of stock firmware and used unmkbootimg to unpack the boot.img. What do I do from here on? I have searched online and this site. I believe I have to put my files in the ramdisk directory. What I do not know is what files go in there? Can I put .img files in there? Is there a specific order in which directory to use within the ramdisk? I read someone's post instructing me to put the .ko files in ramdisk/lib/modules directory. But the ramdisk directory I have does not have a /lib directory. Should I create one? I only ask because each phone seems to have a different setup. I basically have a zImage, dt.img, and a couple of other img files.
Even if you can not help, I appreciate if you point me to relevant useful information.
Thanks
Click to expand...
Click to collapse
boot.img contain: ramdisk, zImage (kernel compressed with modules), dtb (device tree binary) and some time have name dt.img.
When you compile kernel from source, you will get zImage and dt.img (if you use dtbTool to merge all device tree rev). Use xiaolu's unmkbootimg to extract stock kernel to get ramdisk and modify it, replace zImage and dt.img then repack it to become boot.img and ready to flash it.
You should create thread in Q&A box

hiepgia said:
boot.img contain: ramdisk, zImage (kernel compressed with modules), dtb (device tree binary) and some time have name dt.img.
When you compile kernel from source, you will get zImage and dt.img (if you use dtbTool to merge all device tree rev). Use xiaolu's unmkbootimg to extract stock kernel to get ramdisk and modify it, replace zImage and dt.img then repack it to become boot.img and ready to flash it.
You should create thread in Q&A box
Click to expand...
Click to collapse
Thanks. I'll move to Q&A

Question about creating TWRP flashable file

Hey all, I've looked all over an can't find the answer to this... I have a NAND backup I made using TWRP, however, I had the problem many have had with getting errors when trying to restore it. So I thought I'd try a different way by creating a TWRP flashable file from the NAND files. I have taken the files from the backup and extracted them using CYGWIN. I read a thread here:
https://forum.xda-developers.com/showthread.php?t=2746044
But I'm stuck on a couple of things... First, the part about using the META-INF folder from another ROM... I've checked the files in in the META-INF folder and notice that the updater-script is what loads the files and directories. But none of the META-INF files I have found matches my backup files.
The files I want to flash are the complete system folder, complete data folder and the boot.img file. Is it possibly to flash these with TWRP without the META-INF folder/files? If I have to use the META-INF how do I make sure all the files and folders are flashed?
Would it be better to create an ODIN flashable file and just use Odin to do the flash? If so should I put the system and data folders into one file and then use the boot.img (or would I put the boot.img finle into a tar) in the Bootloader spot in Odin?
Thanks in advance.