Database Info

[Q] Some question about making a custom rom

Hi
I hope someone can help me.
I am trying to make my own custom rom. I used this way.
- flashed xxJPM
- de odexed all apps and framework
- added stock android lockscreen
- removed some useless system apps
- then changed theme
all this works great. but I had problems with adding some other apps to /system/apps
1. I copied the *.apk file to /system/app
2. I extract the lib files into /system/lib
But apps like quickpic or the gingerbread keyboard are not working. When I just install them android create a data folder. What do I have to do with those database files in this folder? Can someone show me the right way for installing own system apps?
Then I do a factory data reset in the settings. After this nothing was working. I had no lockscreen. Even all options by pressing the shutdown button except "shutdown" disappeared. Does anyone know why this happened?
I am new to this. So it would be great if you can help me.

cal.mar said:
Hi
I hope someone can help me.
I am trying to make my own custom rom. I used this way.
- flashed xxJPM
- de odexed all apps and framework
- added stock android lockscreen
- removed some useless system apps
- then changed theme
all this works great. but I had problems with adding some other apps to /system/apps
1. I copied the *.apk file to /system/app
2. I extract the lib files into /system/lib
But apps like quickpic or the gingerbread keyboard are not working. When I just install them android create a data folder. What do I have to do with those database files in this folder? Can someone show me the right way for installing own system apps?
Then I do a factory data reset in the settings. After this nothing was working. I had no lockscreen. Even all options by pressing the shutdown button except "shutdown" disappeared. Does anyone know why this happened?
I am new to this. So it would be great if you can help me.
Click to expand...
Click to collapse
QuickPic/Gingerbread: Nope. Open the .apk and copy the lib files to /system/lib
About the rest. i have no idea since I don't know your internal files.
THIS IS DEVELOPMENT. DO NOT CLOSE.
It helps people with force close problems.

The Dark Lestat said:
QuickPic/Gingerbread: Nope. Open the .apk and copy the lib files to /system/lib
About the rest. i have no idea since I don't know your internal files.
THIS IS DEVELOPMENT. DO NOT CLOSE.
It helps people with force close problems.
Click to expand...
Click to collapse
dude he already added the lib files..so this is an un-usual problem
"1. I copied the *.apk file to /system/app
2. I extract the lib files into /system/lib"

cal.mar said:
Hi
I hope someone can help me.
I am trying to make my own custom rom. I used this way.
- flashed xxJPM
- de odexed all apps and framework
- added stock android lockscreen
- removed some useless system apps
- then changed theme
all this works great. but I had problems with adding some other apps to /system/apps
1. I copied the *.apk file to /system/app
2. I extract the lib files into /system/lib
But apps like quickpic or the gingerbread keyboard are not working. When I just install them android create a data folder. What do I have to do with those database files in this folder? Can someone show me the right way for installing own system apps?
Then I do a factory data reset in the settings. After this nothing was working. I had no lockscreen. Even all options by pressing the shutdown button except "shutdown" disappeared. Does anyone know why this happened?
I am new to this. So it would be great if you can help me.
Click to expand...
Click to collapse
After making your own dump your not suppose to factory reset, only after flashing your own dump your ready to factory reset, but if you factory reset while making a dump/removing and adding files, you will soft brick and loose your work..
Did you change the framework and tw framework?
Adding back some framework files via adb might help..
Or you will have to start over again..

I forgot to add that you should check your permissions on the lib file
Sent from my Alpha 17 1.2 GHz ACID Lestatious 2.0 BUILD 1.8 Galaxy 3 FROYO

rudolf895 said:
dude he already added the lib files..so this is an un-usual problem
"1. I copied the *.apk file to /system/app
2. I extract the lib files into /system/lib"
Click to expand...
Click to collapse
After copying lib files give this command over adb..
chmod 777 /system/lib/filename.so
InDroid 4.0 (Build 6)

cal.mar said:
Hi
I hope someone can help me.
I am trying to make my own custom rom. I used this way.
- flashed xxJPM
- de odexed all apps and framework
- added stock android lockscreen
- removed some useless system apps
- then changed theme
all this works great. but I had problems with adding some other apps to /system/apps
1. I copied the *.apk file to /system/app
2. I extract the lib files into /system/lib
But apps like quickpic or the gingerbread keyboard are not working. When I just install them android create a data folder. What do I have to do with those database files in this folder? Can someone show me the right way for installing own system apps?
Then I do a factory data reset in the settings. After this nothing was working. I had no lockscreen. Even all options by pressing the shutdown button except "shutdown" disappeared. Does anyone know why this happened?
I am new to this. So it would be great if you can help me.
Click to expand...
Click to collapse
As for the lockscreen and power menu, i was having same problem few days back. Searched all over, no solution. In the end I had to start it all over again. I suggest u do the same.
InDroid 4.0 (Build 6)

arunmcops said:
As for the lockscreen and power menu, i was having same problem few days back. Searched all over, no solution. In the end I had to start it all over again. I suggest u do the same.
InDroid 4.0 (Build 6)
Click to expand...
Click to collapse
yeah I think you are right. Thank you all for your help. I'll try it again. And I hope that it will work.

HI ok. I've tryed it again.
But know when I want to flash my new factoryfs.rfs the Download crashed.
I don't know where the problem could be.​

Do I have to use this command?
dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
Click to expand...
Click to collapse
Can someone explain this command to me?

still third time flashing chrashes.
when Odin is flashing the factoryfs.rfs it stops at a specific level. odin get 99% of CPU and I have to interupped it. What is my fault? DId anyone have same problems? I try it to make like all the tutorials says.
Edit: Odin says before flashing "Big Partition size!" What do I have to do to make it smaller?
Edit: I get this:
# dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
435200+0 records in
435200+0 records out
222822400 bytes transferred in 115.950 secs (1921711 bytes/sec)
Click to expand...
Click to collapse

Found the problem why odin crashes. I copied the factoryfs.rfs file with 7zip into the .tar package but I had to use TotalCommander.
But still I have no lockscreen after flashing and the options in the power menu are not visible.

[ROM ORIGINAL & ROOTED EDITION] RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1 [UPDATE 12/16]

[ROM ORIGINAL & ROOTED EDITION] RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1 [UPDATE 12/16]
Searching the original RUU ROM?
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe
Take this & enjoy!
http://www.multiupload.com/74DIWTH88Y
Mirror:
http://www.multiupload.com/FKJ8B7Q0QM
>>>>> UPDATE <<<<<
OK, folks!
For some unknown reasons a lot of users asking for a REAL ORIGINAL ROOTED ROM. This is a PD98IMG.ZIP file which is flashable via the boot loader.
Now I'll present you this ROM at this download:
http://www.multiupload.com/AURLLESU5V
- EVERYTHING is still ORIGINAL
- NOTHING has changed or added or modified at this ROM
- Bussybox is installed
- Toolbox is installed
- Superuser 3.07 is installed
The ONLY exception is the RECOVERY partition. I still like to use the 4ext to do some backups and other things. That's the reason why I keep this partition within the ROM.
Finaly here are common questions and answers about this ROM:
Q: How to update?
A: Just download the PD98IMG.zip and store it on your SDCARD. Unplug the batterie, plug it back and press the VOL-DOWN key for enter the bootloader. That's it.
Q: Does it work on every device?
A: Don't know. But it's working on every device with S-OFF
Q: This ROM is a peace of crap! Why the hell the "lib" folder is not within the "system" partition?
A: This question you should ask HTC. If you need the "lib" folder within the "system" partition please use an other image than this because this is ORIGINAL!
Q: Where I can add some support question about this ROM?
A: Use the trash bin because I will not give any support or add features or anything else to this ROM.
Q: Do you plan to do other things with this ROM?
A: NO!!!!!!!
Q: I love this ROM. But I want to do some changes and release this to the community. Is this O.K.?
A: From my point of view this ROM is Public Domain. Don't ask. Enjoy it and do it!
Regards!

http://forum.xda-developers.com/showthread.php?t=1382235

denied1977 said:
http://forum.xda-developers.com/showthread.php?t=1382235
Click to expand...
Click to collapse
This one is rooted and it's not the EXE

MrT69 said:
This one is rooted and it's not the EXE
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1335027
?

Damn!!!
Sometimes I hate your postings @ Mike1986
Sorry m8 - wasn't aware that this ROM is already available...

MrT69 said:
Damn!!!
Sometimes I hate your postings @ Mike1986
Sorry m8 - wasn't aware that this ROM is already available...
Click to expand...
Click to collapse
multiupload is much better so its a plus =D

how can i root it, i unintentionally install it on my phone and i cant get rid of

U need to install the recovery.img from mike1986 ROM 6.1x
How to do?
Make a PD98IMG.ZIP file which contains the android file and recovery.img
Flash this and then install the superuser 3.07
But fyi - the lib folder is outside the system.img
So if you want to install additional things to this ROM it might be that this will not work.
Sent from my Desire HD using XDA App

is it official htc rom

evanbigfan said:
multiupload is much better so its a plus =D
Click to expand...
Click to collapse
http://driphter.com/index.php?topic=3872.0
better than multiupload

""desire s"" ??

i tried to de-odex this rom with dsixda kitchen but unsuccessful due to 2 files not successfully de-odex in app folders....
anybody got any luck in de-odex the rom?

arzme said:
i tried to de-odex this rom with dsixda kitchen but unsuccessful due to 2 files not successfully de-odex in app folders....
anybody got any luck in de-odex the rom?
Click to expand...
Click to collapse
the two that dont get deodexed is maps and google voice if im not mistaken. just replace them with the apk's from market. This happens for most all htc ruu's.
The important files still get deodexed though, and thats what matters.

JSLEnterprises said:
the two that dont get deodexed is maps and google voice if im not mistaken. just replace them with the apk's from market. This happens for most all htc ruu's.
The important files still get deodexed though, and thats what matters.
Click to expand...
Click to collapse
u are spot on abt the 2 files that fail to de-odex.
need a clarify abt "just replace them with the apk's from market".... u mean, while de-odex, just remove the file and after flashing the rom, then install the 2 files from market...
or i need still to replace the file before zipping them back into roms?
anyway, thanks for sharing the knowledge.

arzme said:
u are spot on abt the 2 files that fail to de-odex.
need a clarify abt "just replace them with the apk's from market".... u mean, while de-odex, just remove the file and after flashing the rom, then install the 2 files from market...
or i need still to replace the file before zipping them back into roms?
anyway, thanks for sharing the knowledge.
Click to expand...
Click to collapse
Use whatever Rom you have on your device now, use a file explorer to get into /data/app and copy the Apk's specific to maps (com.google.maps) and voice (com.google.[somethingorother].voice) and copy em to your sd. Then plug in to pc, choose storage mode, and move em to your pc. Or if you're familiar with adb commands, you can go that route, but you need to know the exact filename of the Apk.
Sent by magic from my fingertips

JSLEnterprises said:
Use whatever Rom you have on your device now, use a file explorer to get into /data/app and copy the Apk's specific to maps (com.google.maps) and voice (com.google.[somethingorother].voice) and copy em to your sd. Then plug in to pc, choose storage mode, and move em to your pc. Or if you're familiar with adb commands, you can go that route, but you need to know the exact filename of the Apk.
Sent by magic from my fingertips
Click to expand...
Click to collapse
okay understood. thanks.

arzme said:
okay understood. thanks.
Click to expand...
Click to collapse
ok, so click thanks.

JSLEnterprises said:
ok, so click thanks.
Click to expand...
Click to collapse
it didn't work....
first method: before odex, i replaced the map.odex - de-odex didn't work
second method: delete both the map.odex & map.apk, then replaced with a map.apk - rom hangs on boot up
third method: delete map.odex & map.apk and continue to cook - rom hangs on boot up

arzme said:
it didn't work....
first method: before odex, i replaced the map.odex - de-odex didn't work
second method: delete both the map.odex & map.apk, then replaced with a map.apk - rom hangs on boot up
third method: delete map.odex & map.apk and continue to cook - rom hangs on boot up
Click to expand...
Click to collapse
Delete the apks that didn't de odex and then create a seprate folder with the data/app option put the 2 you want from market/phone in to that folder should be ok then
sent from my dhd

able to successfully de-odex and cook the rom.... my initial problem when the rom can't boot is due to the rom tht i use to cook... i have to do again, the extraction of the rom from the RUU. maybe my first time, the rom got corrupted.
thanks to all tht one way another, give their helps.

[HOW-TO] Re-Odex a ROM

I made a tutorial for other devices here http://forum.xda-developers.com/showthread.php?t=1500475
Why this tutorial?
I wanted a good odexed rom, but there isn't any here. So I tried to make my own odexed rom, but it wasn't so good. So I read something about re-odexing and tried it out. I modified it a little bit and I don't know all about re-odexing, so if someone know something better, pls post it here in the thread for everyone. Im working also on this thread, so I'll try to make few things like a flashable update.zip who executes the script. English is also not my mother language, but I hope you'll understand me
What is a odexed and a deodexed rom?
When you look at a stock rom in the folder /system/app, you will see files with the ending .odex and the apks doesn't contains classes.dex files. When you look at a deodexed rom, you'll see that there are no .odex files and the apks contains classes.dex files. Basically every apk contains a classes.dex files. Then the dalvik virtual machine generates a dalvik cache based of the classes.dex file. When you load a app, it will be loaded from the the dalvik cache, not from the apk. Samsung built the odexed rom using a tool called dexopt-wrapper. This tool generates .odex files based from the classes.dex, that means it does the same job like the dalvik vm. The .odex files were pushed in the /system. The files are the replacement for the dalvik cache. Like I wrote above, apps are loading from the dalvik cache, not from apk or classes.dex file, so classes.dex are not needed anymore, so they are deleted in odexed roms. Deodexing using xUltimate means regenerating a classes.dex based from the .odex file, merging it into the apk and deleting .odex.
What are the advantages and disadvantages from a deodexed rom?
Advantages:
-All needed things are in one apk, so modding/theming is (better) possible
-Needs less space on /system
Disavantages:
-Needs more space on /data, you have on some roms only 110/170 mb free(because a deodexed rom needs a dalvik cache for system apps and frameworks
-Is not so stable than a odexed rom(because some moves dalvik cache to a low end sdext)
-Slower on first boot(because a odexed rom has already execute ready .odex files, a deodexed rom needs to generate dalvik cache)
Why should I re-odex?
I wanted this, because I use ~100 apps and I have a slow sd card, so moving /data/app and /data/dalvik cache to sdext made my system unstables, which was needed to run ~100 apps on a deodexed rom. But when I tried it on a odexed rom, I had only to move /data/app to sdext. So I used long time Stock rooted JPU. But the system was not so fast than on any other custom rom and I hated the stock theme. So If you want more space on /data and you don't want to try out new themes, you should probably try re-odexing.
What do I need to re-odex?
-A full NANDroid Backup
-More than 30 mb free space on /system
-ADB drivers for Option 1
-Titanium Backup Pro for Option 2
How can I re-odex a Rom?
There are 2 Options to do it, but only the first does a full re-odex.
Before doing anything make sure that you have a full NANDroid Backup because you'll propably get into a bootloop.
Option 1 using dexopt-wrapper:
I used first the script from puppet13th, but I got into a bootloop. So I corrected the $BOOTCLASSPATH and corrected permissions, but I got also into a bootloop. I compared the re-odexed Kyrillos Rom v9.3 framework with the framework from JPU. The difference was that Kyrillos Rom v9.3 Framework files android.policy.jar and services.jar doesnt contained the Meta-Inf.
Step 1: Check jars
Pull all your framework .jars using this adb command to your computer
Code:
adb pull /system/framework
and open them in WinRar or sth and check that they contains the Meta-Inf folder. If some file doesnt contain a Meta-Inf folder, I attached all jars from Stock JPU, so you can add the Meta-Inf folder from them. When you are done with adding Meta-Inf Folder to one file, you can push it to the system using this adb command(services.jar is only for example, use your filename):
Code:
adb push services.jar /system/framework
Some users told me that you can re-odex the rom without being in CWM, so you can may skip Step 2, but you could get into a bootloop without Step 2, but you can try it out, there is no risk with a NANDroid backup
Step 2(optional): Reboot your phone into cwm recovery and get adb access there
I never got adb access in windows, but i got always access with linux. If you also don't get access on Linux, you should try to reboot your phone and to select then recovery in the extended power menu, this gaves me always adb access.
Step 3: run reodex script
I attached a script, which push a script and needed binaries over adb to the phone. Then it executes the pushed script, which creates odex files and removes classes.dex from apks or jars and rezipaligns apks and deletes the dalvik cache.
For windows users: double click on odex.cmd
For linux users: open a terminal and navigate to the folder which contains the unzipped attachment and run
Code:
chmod +x reodex.sh
./reodex.sh
After its finished, simply reboot and enjoy your fully re-odexed rom.
Step 4 (optional) convert /data:
I dont know if there is a better option, but after a re-odex with Option 1, my phone didnt showed the right free space on /data. So I converted /data to a other filesystem and back and then it showed the right free space.
Option 2 using Titanium Backup Pro:
You need to have Titanium Backup pro for re-odexing.
Step 1:
Select Menu -> More -> integrate sys dalvik into rom and wait until its finished. Then you should have more space on /data. I had when I tried it before 105 and after 135 mb free space on /data and 0kb free space after it on /system, so its not all.
You can also undo it. Its good when you want to try out a new theme, so you can undo and redo it using TB Pro.
Simply select Menu -> More -> Undo sys dalvik integration
and you're done.
Option 1 vs. Option 2
-Option 1 does a full re-odex, you have full free space on /data(Option 2 does only re-odex the apps, not the framework)
-Option 1 deletes classes.dex from apks and jars(against Option 2), so you have more space free on /system
-You can undo Option 2 fast, so theming/modding is also possible by undo, theme and redo it(against Option 1)
For other Phones:
If someone has a other phone, theres a chance for getting re-odex working, but I think that you should not hope that it works. You can try to put in the right $BOOTCLASSPATH. You can find the valid $BOOTCLASSPATH in /init.rc. Then replace the following characters with the $BOOTCLASSPATH in the script in the folder odex(beginning from Line 8):
Code:
BOOTCLASSPATH=replace_this_with_your_bootclasspath
cd /system/framework
for filename replace_this_with_your_bootclasspath
In the line
Code:
for filename replace_this_with_your_bootclasspath
you must replace the ":" character between framework files with a space.
For theme developers:
I dont know if it works that you use the re-odexed theme on a stock odexed theme. If it is so, you dont have to re-odex and deodex your phone, you can simply push the dexopt-wrapper binary to a folder, chmod 755 it and use it to make odex files from the needed apks and jars(all apks inside /system/framework has no odex files, so dont odex them) like this:
Code:
dexopt-wrapper /system/app/Phone.apk /mnt/sdcard/Phone.odex /system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar
You can change argument 1-2, but not argument 3(its the BOOTCLASSPATH)Then you could copy all needed main apks or jars to sdcard and remove classes.dex. Then only do Step 1 from Option 1 and you should have a theme for odexed rom.
Download Links
XDA gaves me only 500 Errors when uploading was done, so I uploaded it to min.us
Framework jars from JPU
Re-Odex Script for Windows
Re-Odex Script for Linux
Credits
puppet13th for making orginal script
If I helped you, dont be shy, just press the Thanks Button under this post.

www.kingsrom.com/f8-how-to-theme-guideslinkstutorials

Oh year I didnt see any tutorial before, but his is only for Froyo sense or Gingerbread aosp, so it wont work on galaxy 3 and I also wrote my tutorial so that noobs can understand it(I hope so).
I could also post a system.img of a re-odexed Kyrillos Rom v9.3 and other Roms, but I dont know if Im allowed to do that.

TearsDontFalls said:
Oh year I didnt see any tutorial before, but his is only for Froyo sense or Gingerbread aosp, so it wont work on galaxy 3 and I also wrote my tutorial so that noobs can understand it(I hope so).
I could also post a system.img of a re-odexed Kyrillos Rom v9.3 and other Roms, but I dont know if Im allowed to do that.
Click to expand...
Click to collapse
So the re-odexed kyrillos rom v9.3 is working faster than the original kyrillos rom v9.3??

Its not generally faster, but much faster for me because I have ~100 apps and when I run these apps on kyrillos v9.3 deodexed, i must move app and dalvik-cache to sdext which made my phone laggy. With a odexed kyrillos v9.3, i have much more space free on /data, so i only must move app to sdext which is much.
I wrote also the advantages and disadvantages from a deodexed and odexed rom in my tutorial.

TearsDontFalls said:
Its not generally faster, but much faster for me because I have ~100 apps and when I run these apps on kyrillos v9.3 deodexed, i must move app and dalvik-cache to sdext which made my phone laggy. With a odexed kyrillos v9.3, i have much more space free on /data, so i only must move app to sdext which is much.
I wrote also the advantages and disadvantages from a deodexed and odexed rom in my tutorial.
Click to expand...
Click to collapse
So, in a re-odexed rom the HD2SD is not working ?
You use again froyo data2SD ?

dante_100 said:
So, in a re-odexed rom the HD2SD is not working ?
You use again froyo data2SD ?
Click to expand...
Click to collapse
As far as I understand, it works but only for data/app.
correct me if I'm wrong

Sorry, my english is not the yellow from the egg(you must not understand this).
Im using on my re-odexed rom also Hybrid Data 2 SD, I can move also move /data/dalvik-cache and any other folder to sdext, its only not needed, because I had after the re-odexing much more free space on /data, so I did moved dalvik cache back to the NAND from the sdext, before re-odexing I moved dalvik cache to sdext, becaue it was needed for running ~100 apps.
short form:Only Theming is impossible with a re-odexed rom
Hope you'll understand this now.
Edit: Can someone help me for creating a update.zip for re-odexing. It must only copy the dir odex to /data/local/tmp/odex , chmod 755 them all and execute the shell script /data/local/tmp/odex/odex

Sooo
if i get ADB access using windows i can skip step 2 in option1 right?

chandradithya said:
Sooo
if i get ADB access using windows i can skip step 2 in option1 right?
Click to expand...
Click to collapse
No. You need to reboot in cwm and try to get adb access from there. Windows adb in recovery never worked for me, you need linux to get adb access from cwm mode
Sent from my i9003 powered by Poseidon's Rom + UC kernel

Right, I tried to make a update.zip which execute the script, but i had no success, it would be great if somebody can help me.

bscraze said:
No. You need to reboot in cwm and try to get adb access from there. Windows adb in recovery never worked for me, you need linux to get adb access from cwm mode
Sent from my i9003 powered by Poseidon's Rom + UC kernel
Click to expand...
Click to collapse
ADB actually works for me, just ran cmd.exe using admin privileges and i ran the odex script it worked, odexed ALL my system files, cleared my /data/dalvik-cache/
But like TearsDontFalls said it doesn't show the free memory correctly,
Im running g3mod and im yet to try the option4 that asks you to switch file systems
And the /g3mod.log says,
st17: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
While the other partitions are all clean,

How did you got adb access in windows? Sure you was in cwm recovery while re-odexing?

Finally, someone post a guide on this. And it works! Though titanium backup never worked for me. And is it necessary to run the script on cmw? Cause I didn't done it on cmw.
Sent from my GT-I5800 using XDA App

I didn't expect that it works on a running system, but it can be so, so I'll update the guide after Christmas.

TearsDontFalls said:
How did you got adb access in windows? Sure you was in cwm recovery while re-odexing?
Click to expand...
Click to collapse
It worked perfectly for me,
I tried going to the G3 kernels recovery, ADB just wouldnt connect,
so i turned it on, Ran the script when it was in standby mode , then it gave an error at first,
Which i rectified by making the /system read or write using root explorer,
I think i ran the script using admin privileges.
Dont remember..
And g3mod.log showed me this
Code:
Checking mmcblk0p2
/dev/block/mmcblk0p2: clean, 11/125488 files, 15840/500173 blocks
Checking stl6
/dev/block/stl6: clean, 1302/13600 files, 46914/54400 blocks
Checking stl7
/dev/block/stl7 contains a file system with errors, check forced.
/dev/block/stl7: Inodes that were part of a corrupted orphan linked list found.
/dev/block/stl7: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
Checking stl8
/dev/block/stl8: clean, 12/2176 files, 143/8704 blocks
Data2SD Disabled
Multi-OS Data Disabled
System detected: FROYO
System booted with Samsung Froyo kernel mode
Compcache disabled
No problems right now, But cant stop wondering why it says it is inconsistent.

I don't know why it is so, but it also doesn't show the right free space, so convert it to a other file system and then convert it back.

UNBELIEVABLE!
Finally, the first method worked for me.
Working great on HTC Amaze 4G
Thanks

heyjoe66 said:
UNBELIEVABLE!
Finally, the first method worked for me.
Working great on HTC Amaze 4G
Thanks
Click to expand...
Click to collapse
Thanks for your report. So it seems to be working on other devices, so I'll create a thread in android development.

Thanks works on sense 3.5, but I had to change Bootclasspath from the boot.img and add missing files below in odex script.
great guide
edit: now searching on how to re odex a single file.

[MOD][4.1.1 JRO03D] Deodexed Apps and Framework

Deodexed and zipaligned system/framework and system/apps from a JRO03D pull
Since I needed it for another project and it's still not posted, below are some links:
Non-flashable zip of the apks/jars:
http://www.mediafire.com/?npphsab2p1gu16z
CWM-flashable zip of the apks/jars:
note: note: note: note: note: the zip will recursively delete /system/app and /system/framework, so if you put other files in there do not use this zip
http://www.mediafire.com/?zcy0pa6k7y53a85
(tested in CWM 6.0.0.6 - should work in TWRP and CWM 6.0.0.4, I would appreciate if someone can confirm)
---------------
If something goes wrong, here is a flashable zip to return the odexed versions back:
http://www.mediafire.com/?v9rz5jy4wd6osmg

barrmulio said:
Deodexed and zipaligned system/framework and system/apps from a JRO03D pull
Since I needed it for another project and it's still not posted, below are some links:
Non-flashable zip of the apks/jars:
http://www.mediafire.com/?npphsab2p1gu16z
CWM-flashable zip of the apks/jars:
note: note: note: note: note: the zip will recursively delete /system/app and /system/framework, so if you put other files in there do not use this zip
http://www.mediafire.com/?zcy0pa6k7y53a85
(tested in CWM 6.0.0.6 - should work in TWRP and CWM 6.0.0.4, I would appreciate if someone can confirm)
---------------
If something goes wrong, here is a flashable zip to return the odexed versions back:
http://www.mediafire.com/?v9rz5jy4wd6osmg
Click to expand...
Click to collapse
isn't it possible to run a init script that would do this? This won't deodex or zip align any other apps that have been installed right? and should i do a full wipe before attempting this?

I'm not aware of any init scripts for deodexing
the flashable zip removes *all* files from system/app and system/framework (including any manually moved there) and flashes deodexed apps from stock 4.1.1 JRO0D. It doesnt touch any of your files in /data and doesnt need wipe. If you have other files in /system then adb remove/add the files manually using non flash version
Sent from my DROID BIONIC using xda app-developers app

barrmulio said:
I'm not aware of any init scripts for deodexing
the flashable zip removes *all* files from system/app and system/framework (including any manually moved there) and flashes deodexed apps from stock 4.1.1 JRO0D. It doesnt touch any of your files in /data and doesnt need wipe. If you have other files in /system then adb remove/add the files manually using non flash version
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
Cool.. worked great for me!

Worked great, thanks!
Sent from my Nexus 7 using xda app-developers app

Many thanks for this. Can you confirm whether SU binary included?
Thanks!
Sent from my Nexus 7 using Tapatalk 2

battletank said:
Many thanks for this. Can you confirm whether SU binary included?
Click to expand...
Click to collapse
it is not, this is just the stock system/app and system/framework, if there's a lot of interest i can merge them
i could add it in, but chainfire has a flashable zip at his site too

I just flashed this in CWM and I'm getting past my roms bootscreen but after that its just a black screen and the backlight is still on. I'm going to see if I can get back into CWM and do a restore of a nandroid.
I had just installed this rom (Glazed) http://forum.xda-developers.com/showthread.php?t=1796668

Modyfying existing ROM

Hi,
I decided to try to make a modification of an existing ROM which would suit me better right after flashing. Nothing large, only adding some apps and stuff. But Ive got a couple of questions:
1) Ive read some apps cant run from /system partition. Looks like that (at least) one of mine is one of them - it FCs when in /system/apps or /system/priv-apps. Is there any workaround to make this work? I dont want to lose it when doing factory reset (or to flash the ROM again after every factory reset).
2) I wanted to add langunages (http://forum.xda-developers.com/showthread.php?t=2602704) but according to forums those files are odexed. How could I deodex them to make them run on an deodexed ROM?
3) I want to include the faux kernel but Im not sure if simply copying those files into the ROM would do ... in the other cases it went ok but Im not sure about the kernel - Im afraid I could break something.
4) Can I also use the ROM file to store other files? I mean - if I put files into the ROM in /data/media/0/ would it simply appear in my home directory or could this break anything - by which I mean to destroy my existing files?
Thanks for any leads!

michalurban said:
Hi,
I decided to try to make a modification of an existing ROM which would suit me better right after flashing. Nothing large, only adding some apps and stuff. But Ive got a couple of questions:
1) Ive read some apps cant run from /system partition. Looks like that (at least) one of mine is one of them - it FCs when in /system/apps or /system/priv-apps. Is there any workaround to make this work? I dont want to lose it when doing factory reset (or to flash the ROM again after every factory reset).
2) I wanted to add langunages (http://forum.xda-developers.com/showthread.php?t=2602704) but according to forums those files are odexed. How could I deodex them to make them run on an deodexed ROM?
3) I want to include the faux kernel but Im not sure if simply copying those files into the ROM would do ... in the other cases it went ok but Im not sure about the kernel - Im afraid I could break something.
4) Can I also use the ROM file to store other files? I mean - if I put files into the ROM in /data/media/0/ would it simply appear in my home directory or could this break anything - by which I mean to destroy my existing files?
Thanks for any leads!
Click to expand...
Click to collapse
1) What is the app? on system/app they should work fine since kitkat update, i think
2) To deodex i used a kitchen i got out of foro nexus (cant get the link atm) that only worked on linux. If you want to translate things in your rom, i think it can be done without deodexing, im not sure.
3) Copy paste should work fine but if you take a look at faux's meta inf, see what's there, merge it with your rom's meta inf. But it should work with cp
4) You can use the meta inf to link files to storage like your sdcard, yes. However, if you try to put a wallpaper somewhere inside the rom it wont show up

anerik said:
1) What is the app? on system/app they should work fine since kitkat update, i think
2) To deodex i used a kitchen i got out of foro nexus (cant get the link atm) that only worked on linux. If you want to translate things in your rom, i think it can be done without deodexing, im not sure.
3) Copy paste should work fine but if you take a look at faux's meta inf, see what's there, merge it with your rom's meta inf. But it should work with cp
4) You can use the meta inf to link files to storage like your sdcard, yes. However, if you try to put a wallpaper somewhere inside the rom it wont show up
Click to expand...
Click to collapse
Thanks very much for your reply! Now:
1) The app is a game, Traffic Racer. When I flash a ROM where this app has been put in /data/app it runs fine. In /system/app or /system/priv-app it FCs. As you say it should work Ill try to do it again - but I tried it twice in /system/priv-app and once in /system/app already so I dont believe it would work. BTW I use APKs from update.zip created by TiBa if it could be relevant.
2) Linux is not a problem so Ill try to find the link here.
3) Ill try only to copy the files first before messing with meta files.
4) I only want to store some apps config backup files (for Apex launcher and Agenda widget mainly).

michalurban said:
Thanks very much for your reply! Now:
1) The app is a game, Traffic Racer. When I flash a ROM where this app has been put in /data/app it runs fine. In /system/app or /system/priv-app it FCs. As you say it should work Ill try to do it again - but I tried it twice in /system/priv-app and once in /system/app already so I dont believe it would work. BTW I use APKs from update.zip created by TiBa if it could be relevant.
2) Linux is not a problem so Ill try to find the link here.
3) Ill try only to copy the files first before messing with meta files.
4) I only want to store some apps config backup files (for Apex launcher and Agenda widget mainly).
Click to expand...
Click to collapse
Oh, games could cause issues, yes. Better leave it on data app. Messing with meta inf is totally easier than it sounds anyways and could help fixing any possible bugs, you gotta try it. Backup files i dont think they'll work on the rom but you can store them into storage/emulated/legacy which is the storage, though you could do this any other easier way

anerik said:
Oh, games could cause issues, yes. Better leave it on data app. Messing with meta inf is totally easier than it sounds anyways and could help fixing any possible bugs, you gotta try it. Backup files i dont think they'll work on the rom but you can store them into storage/emulated/legacy which is the storage, though you could do this any other easier way
Click to expand...
Click to collapse
Thanks again! Ive got one more question about including the faux kernel. The updater-script is supposed to run this command during the installation in CWM:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
... which I dont know how to implement. If I would only copy all files it would overwrite the original boot.img (Kitkat+ 1.1 original anyway) - which im not sure is the same. So Im not sure if it wont screw something up ...
Or is this extraction the same as copying it? Does the "/dev/block/platform/msm_sdcc.1/by-name/boot" just mean - "its a block device on first SD, partition name boot"?

michalurban said:
Thanks again! Ive got one more question about including the faux kernel. The updater-script is supposed to run this command during the installation in CWM:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
... which I dont know how to implement. If I would only copy all files it would overwrite the original boot.img (Kitkat+ 1.1 original anyway) - which im not sure is the same. So Im not sure if it wont screw something up ...
Or is this extraction the same as copying it? Does the "/dev/block/platform/msm_sdcc.1/by-name/boot" just mean - "its a block device on first SD, partition name boot"?
Click to expand...
Click to collapse
Put faux's boot.img on the rom first, then on updater script go to the line that refers to extracting boot.img (should be like the last one) and replace that with the command on faux's updater script. That means it will extract it in that directory, nothing else. Be sure to copy modules aswell and set the perms

Q&A threads should be created in the Q&A forum... not the Development forum.
Thread moved.

One more question - is there a special way how to pack the ZIP file? Cause I unpacked a ROM, added some apks, packed it but it didnt work (no error, just ended at "opening rom" or what the CWM message is) ... but when I modified existing ZIP it went fine ...