Develop Bugs

help with file permissions, converting .IMG files to update.zip ROMs.

I've successfully scripted the automated creation of a file structure into which the contents of BOOT.IMG, SYSTEM.IMG, DATA.IMG, CACHE.IMG and SD-EXT.IMG are extracted. The script also creates a valid update-script file under ./META-DATA/....
The only issue I have is that I'm using windows so the .IMG files extracted as a yaffs file system, looses the original file permissions. I need someway to recreate the permissions in the update.zip.
Thats all.
Having a way of converting a nandroid backup to an update.zip means you can very easily cook custom roms from a nandroid backup, and port ROMs across phones using a portable .ZIP format.

[Q] HELP!!! Black Custom Boot Screen

This is my first time trying to create a custom boot animation... I think its going to be great if someone would gladly help me out... I can't figure out what has gone wrong with it and why when I restart its just a black screen.. I appreciate everyone who can help me. Thank you... And Thank You XDA... I would upload it directly to xda but the file is too big... so here is the link to whoever wants to help me...
megaupload[dot]com/?d=7NK0BRHR
i noticed and changed alot with it also with the numbering system and still nothing just a black screen...

is it going to the right place some goto (system\customize\resource) some goto (system\media)
whats that ds.store file have never seen that in a evo bootanimation before
both folders are number the same that may make a differance
thing is hugh may want to cut it down maybe split the bigger one in two and remove the smaller and use later as different anime(even after running it through pngoptmizer still over 24.6 mb

hope this helps some
"quoted from pseudoremora"
After creating your bootanimation -- You need to make sure that a couple things have been done correctly for the bootanimation to 1) Work and 2) Be able to be flashed via recovery.
1) To make the bootanimation work
a. Make sure that after creating the animation itself that the .zip you create has NO compression -- (e.g You use "store" mode, instead of "normal" -- both 7zip/Winrar have this feature)
b. Make sure the desc.txt file is properly formatted and has the correct folder names inside the file. Also make sure you have a carriage return (press enter) at the VERY last line of your desc.txt file
c) Make sure the .png filenames are somewhat sequential and organized. (e.g. BootUp001, BootUp002, BootUp003, etc)
2a) To make a flashable package
a. First create a folder to house the bootanimation and you'll also need to explicitly define the folder names that you want the animation to be pushed to. (e.g -- Inside lets say the "MyBootanimation" folder -- you should have three folders; they're names respectively are:: system/customize/resource or system\media
Inside the resource folder is where your newly created bootanimation.zip will go.
2b) To make the package flashable and work in recovery; you'll need a update-script file which should be in a folder called:: META-INF (ALL CAPS); inside that folder should reside, three more folders:: com/google/android/. The update-script file will go INSIDE the android folder.
So, to get this to work, you'll open the "MyBootanimation folder and inside it should reside to folders (system (and it's subfolders); which houses the bootanimation and META-INF (and it's subfolders); which houses the update-script). You need to select both files and zip them up in NORMAL mode, not "store" mode. This will create your new package, which you then need to sign via whatever method you use. I use command line and I'd like not to explain that if I don't have to.

try this(sense base can get asop if thats need)
http://dl.dropbox.com/u/9628638/racecar.zip

dased14 said:
is it going to the right place some goto (system\customize\resource) some goto (system\media)
whats that ds.store file have never seen that in a evo bootanimation before
both folders are number the same that may make a differance
thing is hugh may want to cut it down maybe split the bigger one in two and remove the smaller and use later as different anime(even after running it through pngoptmizer still over 24.6 mb
Click to expand...
Click to collapse
You can also change from png to jpeg. I redid one recently that was 61 mb with pngs, ended up at just over 4 mb with jpegs. Just a thought. And that ds.store, delete it.
Sent from my ADR6300 using XDA App

create flashable zip question

I have 4 computers that I use and 2 of them have adb drivers installed, the other 2(work computers that i am not really allowed to install much on) does not. To be able to push files to my htc desire on the computers that i do not have adb drivers installed I need a flashable zip. I only want to push files such as ringtones, /system apps, bootanimation.zip files and such, i have no intention of changing the framework or the theme and so on. So could anyone point me in the direction of where could i find a ready empty zip file like this or a tutorial in how to make one?
P.S. one of the uses for this is when i am out on a business trip i do not have my personal computer with me, so if brut-maps gets updated i want to be able to push it to the phone without adb.

Hello.
I only have basic knowledge on the subject, so i'm just gonna explain what i do when i need to flash something via flashable .zip.
1) Get a simple flashable .zip used to flash files anywhere on the /system partition.
2) Open it with WinRAR or 7zip or whatever. Navigate to META-INF/com/google/android/. There you will find two files: update-binary and updater-script. You need not touch the binary, because it's the same for all flashable .zips. What you need to do is extract then edit the updater-script, as that tells the recovery what to do with the flashable .zip's contents.
3) Editing the updater-script: let's say we need to create a .zip to flash a new Mail.apk to /system/app. The updater-script's content would need to be:
Code:
show_progress(0.1, 0);
mount("MTD", "system", "/system");
delete("/system/app/Mail.apk");
package_extract_dir("system", "/system");
show_progress(0.1, 10);
unmount("/system");
The "show_progress" lines are self-explanatory. The "mount" command tells the system to mount the /system partition. We then delete the old Mail.apk and tell the recovery where we want to extract the contents of the .zip. After everything's done, we unmount /system.
Add the edited updater-script to the archive, overwriting the original one. Be sure to set your archiver to "Normal" compression level.
4) Creating the proper directory structure: again, let's say we need to flash Mail.apk to /system/app and that we have properly configured the updater-script for this task. We now need to create a folder named "system" (anywhere on the PC), place a subfolder named "app" inside it, then place the new Mail.apk inside the "app" subfolder. We then add the whole structure to the flashable .zip (making sure that there are no other folders in it than "META-INF") and that's that! Again, make sure you use "Normal" compression.
5) Copy the .zip to your SD card, reboot into Recovery and flash the .zip.
6) Enjoy!

thank you very much, that was exactly the kind of information i was looking for.

You're welcome.
Here's a simple flashable .zip i used to replace media_profiles.xml in the /system/etc folder when i didn't have a PC handy and my phone wouldn't boot. You can edit it and use it for your own purpose.

Vendor Folder Access denied on stock kernel

Question: Is it true that on stock kernel for Arc, any modification make to Vendor folder will be denied? I try to install some apps with cwm, only the apps that has modification to vendor folder wont work. info: i used file manager to access that folder, it can be open, but the files within cant be edited, not even paste a new file or replace any files.

xange said:
Question: Is it true that on stock kernel for Arc, any modification make to Vendor folder will be denied? I try to install some apps with cwm, only the apps that has modification to vendor folder wont work. info: i used file manager to access that folder, it can be open, but the files within cant be edited, not even paste a new file or replace any files.
Click to expand...
Click to collapse
As far as I know, indeed. At least not through CWM, you might be able to edit via ES File Explorer(used myself), make sure to make /system writeable.

Someguyfromhell said:
As far as I know, indeed. At least not through CWM, you might be able to edit via ES File Explorer(used myself), make sure to make /system writeable.
Click to expand...
Click to collapse
You should flash arc S ftf to arc. It might help you

TOOLS TO WORK ON ROM

Hi!
I let you here some tools to work on ROM.
First One is Brottli (files ROM format) to Ext4, like it say change from brottli format to ext4 format as example system.new.dat.br and system.transfer.list to system.ext4
Brottli_Dat_to_EXT4.zip
Second on ( the one i use more to extract files from ext4 format images) 7z_Ext4_Imgextractor, for this tool you need to extract, enter in work folder, right click on 7z.exe, compatibility and select execute as administrator or it will not work properly.
7z_Ext4_Imgextractor.zip
Third, is the same as 7z_Ext4_Imgextractor.zip but i only use if 7z_Ext4_Imgextractor.zip doesn´t work. Some times extract with a few errors...
Ext4_Imgextractor.zip
And the last one, is a Update.zip, inside you will find system and vendor folders, inside that folder you can paste a directory/file as you find inside the extract image, example if the file is in vendor/etc, you need to create/paste etc directory inside vendor...
Important Only works with directory with 755 permission and files with 644 permission!!!!! You need to know what you are doing...
update.zip
I hope this tools helps you.