[App] Option.xml generator - Windows Mobile Development and Hacking General

Here is one small file that creates Option.xml files in Sys, OEM and Packages folders.
Valid comands are:
OE.exe /Sys - for parsing folders in Sys directory
OE.exe /Oem - for parsing folders in OEM directory
OE.exe /Packages - for parsing folders in Packages directory
OE.exe /All - for parsing folders in Sys, OEM and Packages directories
OE.exe /C your_dir - for parsing custom directory
OE.exe /C your_dir /R - for parsing custom directory and all subdirectories
Copy OE.exe to yourKitchen\tools directory and edit yourKitchen.CMD file so that contains o option for running the program. In zip you can find example for XperiaKitchen.CMD and copy changes from it.
When you extract rom on the main menu you will find shortcut O that creates Option.xml files with /All parameter
You need to have .net framework 3.5 installed on your pc for this to work, although it is needed for whole kitchen to work I think.
Change log:
V 1.1
- bugfix for creating one Option.xml file for main package and it subpackages instead of creating one Option.xml file for every folder
- added custom directory with or without recursive scan
V 1.0
- initial release
- basic file creation through Sys, Oem and packages directories

Great app, haven't tried it out yet, but will the next time I build a rom, can you modify it to take a directory instead of hardcoded to SYS/OEM/Packages and then have an option to either recursively do all sub directories or just the single directory you passed it?
Thanks,
Geoff

Hi,
you app create this option.xml for a example Adobe PDF:
PACKAGE_BlackStone_AdobePDF
Code:
<?xml version="1.0" encoding="UTF-16" standalone="yes" ?>
<Items>
<Item name="PACKAGE_BlackStone_AdobePDF" group="OEM" checked="true">
<Tip>"PACKAGE_BlackStone_AdobePDF"</Tip>
<Guid type="p">459c6490-3483-43e2-a3b0-47c3a8e51657</Guid>
</Item>
</Items>
PACKAGE_BlackStone_AdobePDF_0409
Code:
<?xml version="1.0" encoding="UTF-16" standalone="yes" ?>
<Items>
<Item name="PACKAGE_BlackStone_AdobePDF_0409" group="OEM" checked="true">
<Tip>"PACKAGE_BlackStone_AdobePDF_0409"</Tip>
<Guid type="p">d2a41d55-c07d-4b40-940c-62822da9f23f</Guid>
</Item>
</Items>
this is the correct option.xml for Adobe PDF package:
Code:
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<Items>
<Item name="Adobe PDF 2.5.1.0.360303.00" group="Office" checked="true">
<Tip></Tip>
<Guid type="p">459c6490-3483-43e2-a3b0-47c3a8e51657</Guid>
<Guid type="i">20280efc-ad2f-495e-9562-af84c9b0c24f</Guid>
</Item>
</Items>
the differences:
two dsm numbers in one option.xml
first dsm number for PACKAGE_BlackStone_AdobePDF
second for PACKAGE_BlackStone_AdobePDF_0409
Two folder, one package and one option.xml in first folder.
There are packages with three or four folders,
then contains the Option.xml three or four dsm numbers.
example:
Entertainment Package (SYS folder) folder list:
Entertainment
Entertainment_DPI_192
Entertainment_Lang_0409
Entertainment_Lang_0409_DPI_192
Option.xml for Entertainment Package:
Code:
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<Items>
<Item name="Solitare and Bubble Breaker" group="Games" checked="true">
<Tip></Tip>
<Guid type="p">0cfc3dc0-5fbc-4153-9ce9-72df4d8c2922</Guid>
<Guid type="i">1f037daf-1ebb-49ff-b6b8-9e3bda1bcbb7</Guid>
<Guid type="i">65e649ac-6009-434b-965b-f1a90bee5d5f</Guid>
<Guid type="i">a8fa2e24-3062-41f9-8d78-321382db9528</Guid>
</Item>
</Items>
wfg
starbase64

ok, that's something that I didn't know and I will fix that during the day
tnx starbase64 for explanation

gzub said:
Great app, haven't tried it out yet, but will the next time I build a rom, can you modify it to take a directory instead of hardcoded to SYS/OEM/Packages and then have an option to either recursively do all sub directories or just the single directory you passed it?
Thanks,
Geoff
Click to expand...
Click to collapse
good idea
I will implement that too in next version

kulla said:
good idea
I will implement that too in next version
Click to expand...
Click to collapse
so new version is up, please test and give me some feedback

Love it
Looks great for a newb chef like me, I'll run it tonight

Hi,
now it works.
wfg
starbase64

joshkoss said:
Looks great for a newb chef like me, I'll run it tonight
Click to expand...
Click to collapse
I'm newbie too in this so I'm trying to simplify everything as much as I can
@starbase64 I'm glad it works for you

Hi,
Found a bug. When the oc.exe is placed in outter folder (e.g. ..\tools\oc.exe /all) or current folder (e.g. oc.exe /all) it won't work.

ahlok_hk said:
Hi,
Found a bug. When the oc.exe is placed in outter folder (e.g. ..\tools\oc.exe /all) or current folder (e.g. oc.exe /all) it won't work.
Click to expand...
Click to collapse
well it's not a bug acctualy because it is ment to be placed in tools folder, for parsing folders with oc.exe outside tools directory use /C dir_where_your_files are and optionaly /R if there are subdirectories in it and you want to parse them too

Related

Registry workshop question?

Hi,
I would appriciate if somebody could help me with the following.
Currently I'm trying to build my own wm6 rom and conversion off roms is no problem for me anymore.
Next step is changing and comparing registry hives but I'm stuck a little!
The registry hives I'm talking about are:
-default.hv
-user.hv
I downloaded RGUCOMP and also have the Registry workshop.
What I'm trying to figure out is how can I convert *.hv files to files to working registry string so that I can edit and compare them with the Registry workshop.
I do know this but don't understand:
dump default.hv:
1. SET _FLATRELEASEDIR=.
2. RGUCOMP -o default.hv -nologo > default.txt
3. Add 'REGEDIT4' (first line)
4. Last line MUST be empty
5. Save as UNICODE
... edit the txt file ...
build default.hv:
1. rename default.txt to boot.rgu (same folder as RGUCOMP.exe)
2. SET _FLATRELEASEDIR=.
3. RGUCOMP -b
4. rename boot.hv to default.hv
Enter this: "RGUCOMP -o default.hv -nologo > default.txt
", 'you should not see the reg entries, because "> default.txt" redirects the output to default.txt '.
Is there no solution to convert a *.hv file to a working registry string *.reg?
Or maybe there is a solution to export the registry from my device and convert it to a *.hv
I'm new to this and any help would be higly appriciated!
Greetings, Leo
after :
RGUCOMP -o default.hv -nologo > default.txt
you'll see default.txt contain all the regkey.
since default.txt doesn't contain the first line 'REGEDIT4',
so you need to add it.
it's same in user.hv
Won't get it
Hi Leies,
Thank you for your reply,
still don't understand, do I have to name the file REGEDIT4 .txt after created, or the first line in the opend textfile must be REGEDIT4, and what about the empty line, do I tab twice [ENTER] to have that and save the textfile in unicode? Sorry I'm stupid, but I just don't get it, it stays blank, weird? Can you send me a sample so I can see please?
Greetings Leo
Leies said:
after :
RGUCOMP -o default.hv -nologo > default.txt
you'll see default.txt contain all the regkey.
since default.txt doesn't contain the first line 'REGEDIT4',
so you need to add it.
it's same in user.hv
Click to expand...
Click to collapse
one more question
Can I create a subdirectory for this c:\hv files\.. and place the boot.hv and user.hv together with rgucomp files in here, or should it be in c:\..
Thanks,
Leo
not name the file, it's add at the first line..
did you got the dump folder already ?
default.hv and user.hv are in dump folder after you have extracted imgfs_raw_data.bin by viewimgfs.exe . (maybe different when you use other tool)
rgucomp -o dump\default.hv -nologo > default.rgu (or default.txt as you like)
then, default.rgu will stored in rgucomp.exe same folder, not at dump folder.
It may help, just try for dumping default.hv:
1. SET _FLATRELEASEDIR=.
1b. echo REGEDIT4 > default.txt
2. RGUCOMP -o default.hv -nologo >> default.txt
Click to expand...
Click to collapse
No need the 3rd original step and you should be able to open default.txt with notepad
Hi,
Thanks for your answer.
Still don't work, this is the error:
wmain: (RGUComp) !ERROR release directory ".echo REGEDIT4 " does not exist
What am I doing wrong?
Please, please, help.
Leo
naboleo said:
It may help, just try for dumping default.hv:
No need the 3rd original step and you should be able to open default.txt with notepad
Click to expand...
Click to collapse
*.hv
Hi thanks again
Will try tomorrow, today I'm having my birthday party
Greetings, Leo
Leies said:
not name the file, it's add at the first line..
did you got the dump folder already ?
default.hv and user.hv are in dump folder after you have extracted imgfs_raw_data.bin by viewimgfs.exe . (maybe different when you use other tool)
rgucomp -o dump\default.hv -nologo > default.rgu (or default.txt as you like)
then, default.rgu will stored in rgucomp.exe same folder, not at dump folder.
Click to expand...
Click to collapse
Did a bat command sample file. Just rename it *.bat instead os *.bat.txt and run it. It should create both user and defaut registry and open them directly in notepad.
Btw : happy birthday !
Found it
Hi,
Thank you Naboleo and Leies
1. set _flatreleasedir=c:\dump
2. RGUCOMP -o default.hv -nologo > default.txt
3. RGUCOMP -o user.hv -nologo > user.txt
Both added first line REGEDIT4, last line empty and saved as unicode!
Done
I'm sooooo happy
Greetings Leo
Again another question
Hi,
I'm making you grazy I know but this is realy important for me, Im almost there building the rom.
Currently I'm busy with RGUCOMP, I converted user.hv to a user.txt file and edited the strings (just some ringtones to delete), now I'm trying to convert back but it doesn't work, it gives some errors.
build user.hv
1. rename user.txt to boot.rgu
2. SET _Flatreleasedir=c:\dumphv (this is my dir)
3. RGUCOMP -b
4. rename boot.hv to user.hv
The errors:
Buildboothive: <RGUCOMP> !ERROR unable to find required source file "Boot.rgu"
ERROR C:\MacB\private\winceos\COREOS\filesys\reg\reghive \.hive c line 877: FS: Registry Exception Handler
wmain: <RGUCOMP> !ERROR failed building BOOT hive
It makes me grazy haha...
Any ideas
Thanks again,
Leo
Laurentius26 said:
Hi,
build user.hv
1. rename user.txt to boot.rgu
2. SET _Flatreleasedir=c:\dumphv (this is my dir)
3. RGUCOMP -b
4. rename boot.hv to user.hv
The errors:
Buildboothive: <RGUCOMP> !ERROR unable to find required source file "Boot.rgu"
ERROR C:\MacB\private\winceos\COREOS\filesys\reg\reghive \.hive c line 877: FS: Registry Exception Handler
wmain: <RGUCOMP> !ERROR failed building BOOT hive
It makes me grazy haha...
Any ideas
Thanks again,
Leo
Click to expand...
Click to collapse
did your rgucomp.exe and boot.rgu in c:\dumphv ?
if yes , just type :
set _FLATRELEASEDIR=.
rgucomp -b
it could be done .
since i'm lazy than u, so i have wrote a *.bat tfile to do extract and repack process .
* remember boot.rgu , you need to rename it to default.hv and copy to "dump" fiolder .
* if you can't directly copy in ( show error ), you may try this command :
attrib -s -r -h dump\default.hv
and then del it .
PS : Happy Birthday Man !
Converting back
@Leies
Thank you for your quick reply's
I love a vampire like you
It doesn't work yet
Two files I've I copied from the dump directory to compile:
-default.hv
-user.hv
Converted them to:
-default.txt
-user.txt
They are in c:\dumphv together with the tools:
-boot.rgu
-cereg400.dll
-make_boot_hv.bat
-rgucomp.exe
How to do this?
default.txt => default.hv
user.txt => user.hv
After that I can copy them back to the dump and start build_imgfs, would be great
I'm enjoying my birthday
Cheers, Leo
Hihi, i seen your post in universal , so i guess that you're cooking a uni rom and using helmi_c method , since i had cooked many for my uni , but not using helmi_c 's method , so maybe something differents ...
ok , let's go ,
when you use "rgucom -b" , the file name of default.hv should rename to boot.rgu , after rgucom success , it'll create a file "boot.hv" and copy it to dump\ and rename to default.hv ,
same as user.hv , should rename to boot.rgu when "rgucom -b" , after rgucom, it'll create a file "boot.hv" and copy it to dump\ and rename to user.hv ,
maybe you can use this to create a bat file and it will auto finish for you .
you can add "pause" if you like to see some information when batch runs.
cd\
cd temp
copy default.rgu boot.rgu
set _FLATRELEASEDIR=.
rgucomp -b
PAUSE
attrib -s -r -h dump\default.hv
del dump\default.hv
copy boot.hv dump\default.hv
del boot.hv
del boot.rgu
copy user.hv boot.rgu
set _FLATRELEASEDIR=.
rgucomp -b
attrib -s -r -h dump\user.hv
del dump\user.hv
copy boot.hv dump\user.hv
del boot.hv
del boot.rgu
PAUSE
BuildImgfs
PAUSE
make_imgfs nk.fat -nosplit
Your so helpful
I'm starting to love you.
That's dangerous isn't?
Anyway, thank you, thank you, thank you
Will let you know how rom is progressing if you like?
Leo
Leies said:
Hihi, i seen your post in universal , so i guess that you're cooking a uni rom and using helmi_c method , since i had cooked many for my uni , but not using helmi_c 's method , so maybe something differents ...
ok , let's go ,
when you use "rgucom -b" , the file name of default.hv should rename to boot.rgu , after rgucom success , it'll create a file "boot.hv" and copy it to dump\ and rename to default.hv ,
same as user.hv , should rename to boot.rgu when "rgucom -b" , after rgucom, it'll create a file "boot.hv" and copy it to dump\ and rename to user.hv ,
maybe you can use this to create a bat file and it will auto finish for you .
you can add "pause" if you like to see some information when batch runs.
cd\
cd temp
copy default.rgu boot.rgu
set _FLATRELEASEDIR=.
rgucomp -b
PAUSE
attrib -s -r -h dump\default.hv
del dump\default.hv
copy boot.hv dump\default.hv
del boot.hv
del boot.rgu
copy user.hv boot.rgu
set _FLATRELEASEDIR=.
rgucomp -b
attrib -s -r -h dump\user.hv
del dump\user.hv
copy boot.hv dump\user.hv
del boot.hv
del boot.rgu
PAUSE
BuildImgfs
PAUSE
make_imgfs nk.fat -nosplit
Click to expand...
Click to collapse
Last one
Hi Leies,
Must be something else!
Here's my story if you want to read.
My device: Universal
The rom I'm trying to build is WM6
I'm using a nk.nba ('Rom' folder) out of Helmi_C's kitchen.
The only thing I want to do is to take some ringtones out there!
So here it is:
cd\
cd\dump
prepare_imgfs nk.nba -nosplit
viewimgfs imgfs_raw_data.bin
dump directory created.
Take the ringtones out.
Maybe here I'm going wrong, I need to edit User.hv and default.hv to take the registry values out, wright ?
It works ok if I leave User and default.hv beside but when i look in my phone under ringtone settings the values are there but when I select them as ringtone the ringtones don't exist's, so that's uckly.
Yes, and I also edited the initflashfiles.dat in the responsable OEM
Next I copy to the dump directory:
boot.rgu
cereg400.dll
make_boot_hv.bat
rgucomp.exe
cd dump
set _flatreleasedir=c:\dump
RGUCOMP -o user.hv -nologo > user.txt
I edit the text and save it as unicode textfile.
Still in dump directory.
RGUCOMP -b
So know user.txt is in boot.rgu
I change the name to user.hv
Same for default.hv
batchfile's are coming later, I'm not so fast as you
Both I copy back to my dumped 'rom' (from here I took them in the first way, so I overwrite them with the new ones)
build_imgfs imgfs_raw_data.bin
make_imgfs nk.nba
Done, ready to use for kitchen. (but not when I edit the *.hv?)
Cheers, Leo
b.t.w. You builded some Roms before for the Universal isn't?
I need to no this please, because I've got the feeling that I'm close to rombuilding, this is the last key that has to suite.

<selector> button states

I am trying to figure out how to use the <selector> resource to change custom button images depending on the state of the button. I have created button_up.9.png, button_down.9.png, button_disabled.9.png and put them in the drawable folder.
I then created this button.xml file in the drawable folder:
Code:
<?xml version="1.0" encoding="utf-8"?>
<selector xmlns:android="http://schemas.android.com/apk/res/android">
 <item
android:state_enabled="false"
android:drawable="@drawable/button_disabled" />
<item
android:state_pressed="true"
android:state_enabled="true"
android:drawable="@drawable/button_down" />
<item
android:state_focused="true"
android:state_enabled="true"
android:drawable="@drawable/button_up" />
<item
android:state_enabled="true"
android:drawable="@drawable/button_up" />
</selector>
Eclipse does not like this xml file and spits out:
Code:
error: Found tag selector where item is expected
This seems to be how all the examples I have found define their selector xml file, what am I doing wrong?
Edit:
Eclipse is no longer giving me the error above but is giving me this error on the closing </selector>:
Code:
Multiple annotations found at this line:
- error: Error parsing XML: not well-formed (invalid
token)
- Content is not allowed in trailing section.
Ok, this is really strange. I just took the xml code I had pasted above and copied it over the same code in button.xml. This time it didn't give me any errors and I can now use the selector in my layout without a problem. Does anyone know why Eclipse would have been showing these incorrect xml errors?

[GUIDE] Sense Language and Locale settings

Someone asked about how to change and edit the language settings for sense based roms, so I thought I'd write a small guide.
This seems to only work for Sense 2 roms
The language and locale settings for sense based roms have to do with the cid, which tells where the phone is from.
First off, we need to know your backup-cid, which can be found by putting:
Code:
dd if=/dev/block/mmcblk0p17 bs=1 count=8 2>/dev/null; echo
in either adb shell, or terminal emulator.
This will spit out an 8 character string, which will be something like "HTC__001"
Next, the cid files are stored in /system/customize/CID/ on the phone in xml format. They are not too hard to modify with a text editor, and you should be able to work out what values you want where.
Code:
<?xml version="1.0" encoding="utf-8"?>
<customization_form>
<category name="system">
<module name="locale">
<function>
<set name="single">
<item name="total_list">[COLOR="Red"]en_NZ;en_AU;en_GB;en_US;fr_FR;[/COLOR]</item>
<item type="boolean" name="[COLOR="Red"]en_NZ[/COLOR]">yes</item>
<item type="boolean" name="[COLOR="Red"]en_AU[/COLOR]">yes</item>
<item type="boolean" name="[COLOR="Red"]en_GB[/COLOR]">yes</item>
<item type="boolean" name="[COLOR="Red"]en_US[/COLOR]">yes</item>
<item type="boolean" name="[COLOR="Red"]fr_FR[/COLOR]">yes</item>
</set>
</function>
</module>
That is part of my modified cid.xml, the parts you want to change are in red.
Now, I don't know if we can just swap out the new cid.xml file, and re-run the setup after a reboot to get our language options.
What I did was create a flashable zip to replace the cid.xml file after installing a sense rom.
I have attached a zip, so you just open it up, and swap out the file in zip/system/customize/CID/ with a modified cid.xml, and then flash the zip after flashing a sense rom.
-Nipqer
Nipqer said:
Someone asked about how to change and edit the language settings for sense based roms, so I thought I'd write a small guide.
This seems to only work for Sense 2 roms
The language and locale settings for sense based roms have to do with the cid, which tells where the phone is from.
First off, we need to know your backup-cid, which can be found by putting:
Code:
dd if=/dev/block/mmcblk0p17 bs=1 count=8 2>/dev/null; echo
in either adb shell, or terminal emulator.
This will spit out an 8 character string, which will be something like "HTC__001"
Next, the cid files are stored in /system/customize/CID/ on the phone in xml format. They are not too hard to modify with a text editor, and you should be able to work out what values you want where.
Code:
<?xml version="1.0" encoding="utf-8"?>
<customization_form>
<category name="system">
<module name="locale">
<function>
<set name="single">
<item name="total_list">[COLOR="Red"]en_NZ;en_AU;en_GB;en_US;fr_FR;[/COLOR]</item>
<item type="boolean" name="[COLOR="Red"]en_NZ[/COLOR]">yes</item>
<item type="boolean" name="[COLOR="Red"]en_AU[/COLOR]">yes</item>
<item type="boolean" name="[COLOR="Red"]en_GB[/COLOR]">yes</item>
<item type="boolean" name="[COLOR="Red"]en_US[/COLOR]">yes</item>
<item type="boolean" name="[COLOR="Red"]fr_FR[/COLOR]">yes</item>
</set>
</function>
</module>
That is part of my modified cid.xml, the parts you want to change are in red.
Now, I don't know if we can just swap out the new cid.xml file, and re-run the setup after a reboot to get our language options.
What I did was create a flashable zip to replace the cid.xml file after installing a sense rom.
I have attached a zip, so you just open it up, and swap out the file in zip/system/customize/CID/ with a modified cid.xml, and then flash the zip after flashing a sense rom.
-Nipqer
Click to expand...
Click to collapse
ooohhh yeeees, it works great
thx
---------- Post added at 10:13 PM ---------- Previous post was at 10:06 PM ----------
Do you know how I can change the hardware keyboard language? Can I disable the spelling or set it to german?
I'm not sure exactly, but look under Language & Keyboard settings, and I think it's under the dafault soft keyboard settings that the Hardware keyboard settings are kept.
I'm running cyanogen at the moment, so this is only from memory for sense.
-Nipqer
Nipqer said:
I'm not sure exactly, but look under Language & Keyboard settings, and I think it's under the dafault soft keyboard settings that the Hardware keyboard settings are kept.
I'm running cyanogen at the moment, so this is only from memory for sense.
-Nipqer
Click to expand...
Click to collapse
thats not possible, I can only select englisch ...
should I delete some files with the rootexplorer , under system/usr .. ?

[Q] Any way to remove the 512 character limit on Nook Touch notes?

In the interface for reading books, you can highlight a word or set of words, then attach a note to that.
The notes are limited to 512 characters, but you can have an unlimited number of notes for a book. I currently work around the limit by highlighting a word, writing the note, then highlighting the next word and continuing the note.
Is there a way to remove the limit of 512 characters, or increase it to a very large number? My nook is fully rooted, so I imagine it is a simple config file or sqlite entry somewhere, but I don't know where to look.
I determined that the 512 character limit is hard coded into the Reader.apk app. I modified the app to increase the limit to 8192 characters (16 times as much) and have posted the details below.
Attached is the apk for the updated app. To install it, you must first uninstall the old reader.apk as this one is signed using a different key.
For those who wish to make the changes themselves, the following are the steps needed.
Pre-requisites
Nook must be rooted (obviously)
Android SDK must be installed. Link to sdk download page
APKTool must be installed. Link to APKTool download page
Install the Nook framework file. This is needed to properly recompile the apk later.
Code:
adb pull /system/framework/framework-res.apk
Code:
apktool if framework-res.apk
Copy the original Reader.apk file into the current directory.
Code:
adb pull /system/app/Reader.apk
Decompile the apk file using apktool
Code:
apktool d Reader.apk
Make the changes needed
Modify the AndroidManifest.xml file. Remove the "sharedUserId" flag.
Change this
HTML:
<manifest android:sharedUserId="android.media" android:versionCode="1" android:versionName="1.0" package="com.bn.nook.reader.activities"
xmlns:android="http://schemas.android.com/apk/res/android">
to this
HTML:
<manifest android:versionCode="1" android:versionName="1.0" package="com.bn.nook.reader.activities"
xmlns:android="http://schemas.android.com/apk/res/android">
Modify the following files. Search for "0x200" and replace it with "0x2000" (ie add a zero; this will multiply max size by 16):
Reader/smali/com/bn/nook/reader/ui/AddNoteView$1.smali
Reader/smali/com/bn/nook/reader/commonui/ReaderCommonUIConstants.smali
Modify the following file. Search for "512" and replace it with "8192" (the decimal equivalent of hex 0x2000)
Reader/res/layout/add_note_layout.xml
Recompile the source code into a new apk.
Code:
apktool b Reader ReaderUnsigned.apk
Create a signing key; Skip this step if you have created one already. Note: keytool is located in the Android SDK->Tools folder.
Code:
keytool -genkey -v keystore myAndroidKey.keystore -alias myAndroidKeyAlias -keyalg RSA -validity 10000
Sign your new apk.
Code:
jarsigner -verbose -keystore myAndroidKey.keystore ./ReaderUnsigned.apk myAndroidKeyAlias
Use zipalign (also in sdk->tools) to align your apk.
Code:
zipalign -v 4 ReaderUnsigned.apk ReaderSigned.apk
Rename the system reader.apk file to uninstall/backup the apk.
Code:
adb shell mv /system/app/Reader.apk /system/app/Reader.apk.bak
Remove any entries of the previous Reader.apk signing key from the "/data/system/packages.xml" file.
Pull the packages.xml file.
Code:
adb pull /data/system/packages.xml
Edit the packages.xml file. Search for "com.bn.nook.reader". Remove this entire tag:
HTML:
<package name="com.bn.nook.reader" ...>...</package>
Push the packages.xml file back.
Code:
adb push packages.xml /data/system/packages.xml
Install your new app and enjoy the larger note sizes!
Code:
adb install ReaderSigned.apk

Where is "feature.xml" ?

Hi,
On Lollipop 5.0.1, i look for the file "feature.xml" should be in "system / csc /" but I can not find it
Anyone know where it is?
I would like to modify it to change the variable "CscFeature_Camera_ShutterSoundMenu> false."
Put "true" instead of "false".
Thanks
resolved
Actually I solved my problem by adding the line "<CscFeature_Camera_ShutterSoundMenu> TRUE </ CscFeature_Camera_ShutterSoundMenu>" in OTHERS.XML
This line adds the no-sound menu in the camera app.
Others.xml therefore contains:
Code:
<?xml version="1.0" encoding="UTF-8" ?>
<SamsungMobileFeauture>
<FeatureSet>
<CscFeature_Web_bool_EnablePriorityUserBookmark>false</CscFeature_Web_bool_EnablePriorityUserBookmark>
<CscFeature_Camera_ShutterSoundMenu>TRUE</CscFeature_Camera_ShutterSoundMenu>
</FeatureSet>
</SamsungMobileFeauture>

Categories

Resources