Replace all with Quarx 0405 files
/system/etc/mot_ise_imager_cfg.bin
/system/lib/camera.so
Add in libkobecamera.so
I also replaced libbayercamera.so and libsoccamera.so with libkobecamera.so
Edit build .prop to 3m and remove flash strings like we did with CM7 Defy Ports.
Don't change build.prop to Kobe or remove Jordan/Defy strings, hw back lights quit working.
I've only tested with lgcamera free, but taking pictures works, no video yet.
Using camcorder will crash camera and require a reboot to take pictures.
Tested with Epsylon3 latest.
No USB tethering so I'm typing from phone.
EDIT: Back on CM7, so I can type better instructions. All commands for adb. I prefer adb over different root explorers when replacing system files.
Open Quarx Nightly and extract all to the same folder: /system/etc/mot_ise_imager_cfg.bin, /system/lib/libcamrea.so, /system/lib/libkobecamra.so
Open Epsylon3 CM9 Latest and extract /system/build.prop and place in the same folder with the CM7 system files
Open CM9 build.prop with any editor except Windows Notepad (NEVER use WINDOWS NOTEPAD for anything AT ALL EVER, use Notepad+.)
CHANGE
ro.media.capture.maxres=5m
ro.media.capture.flash=led
ro.media.capture.flashIntensity=41
ro.media.capture.torchIntensity=25
ro.media.capture.classification=classH
INTO
ro.media.capture.maxres=3m
ro.media.capture.classification=classA
Open a terminal in the folder with all the extracted files (or open terminal then -- cd /path/to/files)
adb remount
adb push ./mot_ise_imager_cfg.bin /system/etc/mot_ise_imager_cfg.bin
adb shell chmod 0644 /system/etc/mot_ise_imager_cfg.bin
adb push ./libkobecamera.so /system/lib/libkobecamera.so
adb shell chmod 0644 /system/lib/libkobecamera.so
adb push ./libkobecamera.so /system/lib/libbayercamera.so
adb shell chmod 0644 /system/lib/libbayercamera.so
adb push ./libkobecamera.so /system/lib/libsoccamera.so
adb shell chmod 0644 /system/lib/libsoccamera.so
adb push ./libcamera.so /system/lib/libcamera.so
adb shell chmod 0644 /system/lib/libcamera.so
adb push ./build.prop /system/build.prop
adb shell chmod 0644 /system/build.prop
adb reboot
Explanation of Commands used
./ means your current directory, user /path/to/file/ if your terminal is active at another location or
cd -- change your directory
chmod changes permissions (use google for more info)
adb remount--lets you write to root system directories
adb push--copy's files to phone, overwriting if the file already exists
adb shell--changes PC OS Terminal into Android Terminal, exit with "exit"
adb reboot--reboots phone
MIUI INFO
I stopped working on MIUI for the past couple of days to remake White Rabbit 1.4 with Quarx's Latest Nightly. I should be done in about 12-24 hours, earlier if I quit procrastinating.
I also changed my MIUI translation efforts over to compiling MIUI from patchrom source with Quarx's Nightly. I can compile fine up to SystemUI...the last part before it starts making the rom's zip. Hopefully I'll have something in the next week. I'd really like to have a Bravo MIUI instead of using Defy Ports.
thx
where libbayercamera.so and libsoccamera.so ??
rui3bo2 said:
where libbayercamera.so and libsoccamera.so ??
Click to expand...
Click to collapse
They're the libraries for the red lens and green lens Defy cameras, you don't need them and I renamed libkobecamera.so to just overwrite them so the kobe library was the only one being used. You don't need them, and I'm actually not sure if you even need to overwrite libbayercamera.so and libsoccamera.so, they were already overwritten when I found this copy\paste camera hack. Although with how the Kobe ICS github page is looking, this won't matter soon.
skeevy420 said:
They're the libraries for the red lens and green lens Defy cameras, you don't need them and I renamed libkobecamera.so to just overwrite them so the kobe library was the only one being used. You don't need them, and I'm actually not sure if you even need to overwrite libbayercamera.so and libsoccamera.so, they were already overwritten when I found this copy\paste camera hack. Although with how the Kobe ICS github page is looking, this won't matter soon.
Click to expand...
Click to collapse
My English is not good to see do not quite understand, ha ha.
skeevy420 said:
They're the libraries for the red lens and green lens Defy cameras, you don't need them and I renamed libkobecamera.so to just overwrite them so the kobe library was the only one being used. You don't need them, and I'm actually not sure if you even need to overwrite libbayercamera.so and libsoccamera.so, they were already overwritten when I found this copy\paste camera hack. Although with how the Kobe ICS github page is looking, this won't matter soon.
Click to expand...
Click to collapse
Wait how is the ICS github page looking? I've never that we even had a github page, who's behind it? Quarx?
BravoMotorola said:
Wait how is the ICS github page looking? I've never that we even had a github page, who's behind it? Quarx?
Click to expand...
Click to collapse
Yes, its Quarx's. Last updated 2 hrs ago.
Also new CM7 nightly up.
Related
Big ups to Drizzy for making such an awesome ROm.
Here are 3 modified apk's; framework-res, Rosie, and HtcClockWidget.
I didn't change all the pictures just the status bar, Rosie Bar and WeatherClock Background. If people like my work I might just start posting more visuals on the demand of what people would like changed. Font color is going to stay because I can't edit the xml files.
To Install:
adb remount
adb push framework-res.apk /system/framework/framework-res.apk
adb push Rosie.apk /data/app_s/Rosie.apk
adb push HtcClockWidget.apk /data/app_s/HtcClockWidget.apk
adb shell reboot
http://www.mediafire.com/download.php?jzrykjnv2oy
Now with BlUE accents/highlights! (I think, I'm color blind so blue and purple look the almost the same, either way I think it looks nice.)
Blue Blur http://www.mediafire.com/download.php?y4y4gzjcyvn
push com.htc.resources.apk to /system/framework/com.htc.resources.apk
looks good
ok when i unzip the file where do i put them so they cn be push to my phone
jacsonmoore3 said:
ok when i unzip the file where do i put them so they cn be push to my phone
Click to expand...
Click to collapse
on your computer put them in your working path so that you can do adb push whatever.apk /data/app_s/whatever.apk
or if you don't have adb do this with them on the root of your sdcard
Code:
mount /system
mount /data
mount /sdcard
cp /sdcard/framework-res.apk /system/framework-res.apk
cp /sdcard/Rosie.apk /data/app_s/Rosie.apk
cp /sdcard/HtcClockWidget.apk /data/app_s/HtcClockWidget.apk
(use the mv command it cp doesn't work)
reboot
david1171 said:
on your computer put them in your working path so that you can do adb push whatever.apk /data/app_s/whatever.apk
or if you don't have adb do this with them on the root of your sdcard
Code:
mount /system
mount /data
mount /sdcard
cp /sdcard/framework-res.apk /system/framework-res.apk
cp /sdcard/Rosie.apk /data/app_s/Rosie.apk
cp /sdcard/HtcClockWidget.apk /data/app_s/HtcClockWidget.apk
(use the mv command it cp doesn't work)
reboot
Click to expand...
Click to collapse
well i dont know what u mean by [working path] but i think i can do it from my phone..do i do it in recovery or can i use the terminal..i have adb but im not getting what u talking bout cuz im still learning
jacsonmoore3 said:
well i dont know what u mean by [working path] but i think i can do it from my phone..do i do it in recovery or can i use the terminal..i have adb but im not getting what u talking bout cuz im still learning
Click to expand...
Click to collapse
If you have adb then put the apks in you're sdk/tools folder or where ever you're adb is located
Use the commands David gave you in the terminal or recovery, doesn't matter.
AdrianK said:
Use the commands David gave you in the terminal or recovery, doesn't matter.
Click to expand...
Click to collapse
actually it would be the recovery console because i do not believe that you can type "mount data" or "mount system" in the terminal and have it work, it will tell you the device or resource is busy.
also i use windows and i have adb.exe and AdbWinApi.dll in my system32 folder so i can use adb from any directory on my computer.
the working path is what appears by default when you open up command prompt (which for me is C:\users\david\ i use for adb commands do adb push desktop/what.ever [dir on phone] or adb push downloads/what.ever [dir on phone])
but as stated before drop the files into your tools folder and cd to your tools folder then adb push from there.
Rosie for some reason isn't working for me... adb or console, going to try root explorer and see if it works, good work regardless
Will this work for other Hero roms?
bigchi2000 said:
Rosie for some reason isn't working for me... adb or console, going to try root explorer and see if it works, good work regardless
Click to expand...
Click to collapse
that was me, I had zipped the original Rosie.apk instead of the one I modified I updated the zip so everyone download and tell me what you think.
kabluey said:
that was me, I had zipped the original Rosie.apk instead of the one I modified I updated the zip so everyone download and tell me what you think.
Click to expand...
Click to collapse
cool loks great. do you think you can change the selection highlights from red to green or blue
w0rd said:
Will this work for other Hero roms?
Click to expand...
Click to collapse
i pushed this on to mligns hero and it worked fine. im in the process of flashing the new jachero so i will try it on that one and post my results.
great work i like this!! +5
learningmore said:
i pushed this on to mligns hero and it worked fine. im in the process of flashing the new jachero so i will try it on that one and post my results.
Click to expand...
Click to collapse
Thanks appreciate it!
cp: cannot create /data/app_s/Rosie.apk (or any other file) : Path does not exist.
i also made sure those files were there
have any idea on how to get Plurk onto blur?
full lockscreen? Thanks.
Now has blue selection highlights!
I think if you wanted plurk you would need to find a non-odex plurk apk and push it to you data/app_s/ folder. I don't know if drizzy put out a build with plurk so look at some of the other hero roms.
kabluey said:
Big ups to Drizzy for making such an awesome ROm.
Here are 3 modified apk's; framework-res, Rosie, and HtcClockWidget.
I didn't change all the pictures just the status bar, Rosie Bar and WeatherClock Background. If people like my work I might just start posting more visuals on the demand of what people would like changed. Font color is going to stay because I can't edit the xml files.
To Install:
adb remount
adb push framework-res.apk /system/framework/framework-res.apk
adb push Rosie.apk /data/app_s/Rosie.apk
adb push HtcClockWidget.apk /data/app_s/HtcClockWidget.apk
adb shell reboot
http://www.mediafire.com/download.php?jzrykjnv2oy
Now with BlUE accents/highlights! (I think, I'm color blind so blue and purple look the almost the same, either way I think it looks nice.)
Blue Blur http://www.mediafire.com/download.php?y4y4gzjcyvn
push com.htc.resources.apk to /system/framework/com.htc.resources.apk
Click to expand...
Click to collapse
Thanks for the blue it right on time. I'm running it on the new jac.
I have looked around quite a bit, and haven't really figured out the straight answer on this.
I have seen apks that can be downloaded of things like the clock or gallery app, and then I have seen custom roms that include things like the AOSP dialer, contact app, browser, etc. However in my small amount of trying, I couldn't install them on top of another ROM (or stock).
Is there an issue with signing them, or does it have to be done in recovery mode, or do I have to remove the existing stuff in something like Titanium backup and then install the other APKs, or would my only option be to learn the dark arts of rom cooking?
Edit: Answered thanks to mrchu001. Doing an "adb remount" and then issuing the install command from the shell worked.
I'm not sure if this works for ALL apks between roms, but when i flashed Fresh it didn't have the cooliris 3d gallery that DC has, so i opened the zip, and copied the APK from one rom to the other then flashed it. I'm sure there are some programs that just won't work even if you did it this way, but something to consider.
That works in most cases..
Just get the zip on your computer, open it extract the apk you want and adb install it to your connected device.
No luck with either method mentioned above. I'm sure I don't know what I'm doing... but I did an adb install <apk name> and got an error:
Code:
MacBook: tools laydros$ adb install CarDock.apk
1344 KB/s (238640 bytes in 0.173s)
pkg: /data/local/tmp/CarDock.apk
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
And I grabbed one of the base rooted roms, unzipped, added the CarDock and DeskClock apks to the system/app folder with everything else, and the ROM failed to load. I did the same clockwork rom manager install rom from SD card methods I have done before. I assume this means that the zip was not properly signed.
The apks I was testing were ones from bugless beast 0.4, any ideas?
laydros said:
No luck with either method mentioned above. I'm sure I don't know what I'm doing... but I did an adb install <apk name> and got an error:
Code:
MacBook: tools laydros$ adb install CarDock.apk
1344 KB/s (238640 bytes in 0.173s)
pkg: /data/local/tmp/CarDock.apk
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
Click to expand...
Click to collapse
it looks like you didnt direct your terminal correctly. i'm assuming you have the sdk on your computer btw. now try to upload the rom you want on your phone. plug it in. make sure usb debugging is set. make sure the apks you want to put on your phone are on your desktop. and try this:
Code:
cd ~/*where every your sdk is*/tools
./adb remount
./adb shell
./adb install ~/desktop/*apk name* /system/app
./adb shell reboot
maybe you already tried but just incase.. do you have the Unknown sources check box "Checked" under "Settings/application" menu? if not you need to to install apps not from the market..
mrchu001 said:
it looks like you didnt direct your terminal correctly. i'm assuming you have the sdk on your computer btw. now try to upload the rom you want on your phone. plug it in. make sure usb debugging is set. make sure the apks you want to put on your phone are on your desktop. and try this:
Code:
cd ~/*where every your sdk is*/tools
./adb remount
./adb shell
./adb install ~/desktop/*apk name* /system/app
./adb shell reboot
Click to expand...
Click to collapse
The remount part did it, and then doing the install from adb shell. Thanks so much.
For the sake of anyone else that finds this, once you type adb shell, you are working from the phones shell instead of the one on your computer, so you would skip that command. I ended up moving the files to the sdcard, and then doing
Code:
cd ~/*where every your sdk is*/tools
./adb remount
./adb shell
(at this point you are at the phone's prompt)
install /sdcard/*apk name* /system/app
exit
(now you are back at the computer's prompt)
./adb shell reboot
Now I need to figure out what to install to get the phone/contacts working. Calendar and Mms applications were easy, but after installing several apks for the phone and contacts I just have a mess.
FroydVillain 1.0.0 install *.apk files in /system/app
Hi has anyone tried installing another apk file in FroydVillain 1.0. I follow the steps in the thread described i am able to issue adb shell commands and i have placed the apk files in the SD card as described. but i am getting an error as below that the file or dir is not found. tried several paths:
# install /mnt/sdcard/*.apk /system/app
install /mnt/sdcard/*.apk /system/app
install: can't stat '/mnt/sdcard/*.apk': No such file or directory
# install /sdcard/*.apk /system/app
install /sdcard/*.apk /system/app
install: can't stat '/sdcard/*.apk': No such file or directory
I use /mnt/sdcard path cause on Froyo the SDCARD folder is under /mnt.
any help solving this. i am trying to install some of the HTC Sense UI app to sys app. Like Stock.apk for test. and HTCAlbum.apk and others same result every time.
I have tried also AndroidCommander 0.7.9.6 updated for froyo. installing with it's install option button, and also from the console i run the shell command for install, successfully adds the apk in sys app folder but the apk is not installed, and asks for installation.
Thanks.
Regards Alek
help
Hi,
Can you explain to begginers (like me) how do you installed the apk in system/app? please, I want to install contacs.apk form CM9 to other rom.
Thanks.
Hey guys, I wanted to modify the framework in cyanogenmod 7. What I did was se this command in terminal:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
rm /system/app/SystemUI.apk
so as you can see, i deleted the framework and after that i couldnt do anything in terminal. I turn off the phone and then i usb mounted the phone to adb push the moddified systemui.apk, i was able to push the apk, but when i restarted the phone, there was no framework.. any ideas as to why that is.. maybe the apk file is corrupted?
Its named signedsystemui.apk! Did you push it with the right name?
Sent from my......ummm...let me get back at'chya!
I don't usually delete things before pushing new file and I don't normally recommend signing system/apps.
This is what I would do. Keep in mind, your mod (whatever you may have done with it) could simply be a little goofed up.
Code:
adb remount
adb shell
stop
cp system/app/SystemUI.apk /system/app/SystemUI.bak
adb push <path to>/signedSystemUI.apk /system/app/SystemUi.apk
start
exit
In the above, <path to> refers to the location of your modified aoj. For me, it would normally be "Users/tommytomatoe/Mod/app.apk". What I do is drag and drop the apk into the terminal after typing "adb push".
If it boots up after issuing adb shell start, then you're golden! If not, then do this. Keep in mind, if you're in splash screen you will want to reboot into recovery first and mount system using the options in the menu. If you're in boot loop with bootanimation, go ahead and issue these commands:
Code:
adb remount
adb shell
stop
mv system/app/SystemUI.bak /system/app/SystemUI.apk
start
exit
Now, you will have original apk and it should boot up. Go back to ground zero and remodify your apk and make sure you've taken correct steps.
All i did was change some pngs. I did sign the apk... maybe thats why it didnt work..When changing pngs to the systemui.apk, do i also have to modify the framework-res.apk?
~CR7~ said:
All i did was change some pngs. I did sign the apk... maybe thats why it didnt work..When changing pngs to the systemui.apk, do i also have to modify the framework-res.apk?
Click to expand...
Click to collapse
It appears the newer gb stuff has elements in framework res as well as system ui. It wont hurt to change both if same files exist in both. Tjats what I think.
And also, don't sign system apk. All the system apk prefer to have same signature. Signing one would result in having to sign all in most cases...
Sent from my PC36100 using XDA Premium App
just saw this in a chinese forum
i m bad in english.. but i ve tried my best to translate it so that u guys can try it
i think it may help us to improve our display quality
download the attachment
extract zip
using root explorer
move be_photo and be_movie to /system/etc
edit the permission for both files to : r-w-e
r- -e
r- -e
"change owner" wner:0 - root
group:0 - root
(apply to both files)
open and edit the
/system/build.prop
add these on the end of it
#Bravia Engine Service
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
reboot ur device
*sry for my bad english
Does this work in tiamat rom?
i saw this for the Galaxy S2 just for stock rom
yup. I m using it with tiamat
could somebody just reiterate those instructions a little clearer, perhaps in code tags?
Any confirmation about this if it works on xoom
Sent from my MZ601 using xda premium
beepoo83 said:
Any confirmation about this if it works on xoom
Sent from my MZ601 using xda premium
Click to expand...
Click to collapse
Read above, already answered your question which is a yes it works on xoom if you read the instructions.
I'm not 100% sure exactly what it does but from the looks of the description (from what I can read from the broken English) it''s supposed to make the display better but who knows, I'll hold off until more about it and possibly see screen shots.
scsa20 said:
Read above, already answered your question which is a yes it works on xoom if you read the instructions.
I'm not 100% sure exactly what it does but from the looks of the description (from what I can read from the broken English) it''s supposed to make the display better but who knows, I'll hold off until more about it and possibly see screen shots.
Click to expand...
Click to collapse
Just one who confirmed that it work wish to see more people involve in
Sent from my MZ601 using xda premium
I can confirm that this works on my Xoom (Euro 3G running Tiamat Moray 2.2.2)
Basically the Bravia Engine boosts images and videos, read this review from GSMArena for more information: http://blog.gsmarena.com/heres-what-sony-ericsson-mobile-bravia-engine-really-does-review/
*Edited Moray
how much improvement are you noticing? Is it worth it?
I don't really see a difference. I compared it to my co-worker's tiamat xoom.
These stuffs really work. the screen has better contrast (just a little)
I took 2 picture, you can see black color become deeper
Is this hack only for images and video exclusively?
Or will it always run in the background
Sent from my ADR6350 using xda premium
beakeroo said:
could somebody just reiterate those instructions a little clearer, perhaps in code tags?
Click to expand...
Click to collapse
1) Download post#1 attached file
2) extract somewhere
3) connect XOOM via USB
4) in cmd.exe window navigate to path specified in 2)
5) execute in cmd code below
Code:
adb remount
adb push be_movie /system/etc/be_movie
adb push be_photo /system/etc/be_photo
adb shell chmod 0755 /system/etc/be_movie
adb shell chmod 0755 /system/etc/be_photo
adb shell echo -e \#Bravia Engine Service\\nro.service.swiqi.supported=true\\npersist.service.swiqi.enable=1\\n^>^>/system/build.prop
adb reboot
Thanks for that, I was a bit worried about OPs language barrier
_TB_TB_ said:
1) Download post#1 attached file
2) extract somewhere
3) connect XOOM via USB
4) in cmd.exe window navigate to path specified in 2)
5) execute in cmd code below
Code:
adb remount
adb push be_movie /system/etc/be_movie
adb push be_photo /system/etc/be_photo
adb shell chmod 0755 /system/etc/be_movie
adb shell chmod 0755 /system/etc/be_photo
adb shell echo -e \#Bravia Engine Service\\nro.service.swiqi.supported=true\\npersist.service.swiqi.enable=1\\n^>^>/system/build.prop
adb reboot
Click to expand...
Click to collapse
If we follow this method do we still need to do this part after -
open and edit the
/system/build.prop
There seemed to be extra editing steps in the OP's post and I wasn't sure if they were needed. I am also using the Tiamat ROm and the files pushed fine but I don't notice a difference really.
Isun said:
If we follow this method do we still need to do this part after -
open and edit the
/system/build.prop
There seemed to be extra editing steps in the OP's post and I wasn't sure if they were needed. I am also using the Tiamat ROm and the files pushed fine but I don't notice a difference really.
Click to expand...
Click to collapse
Nope. If you follow the adb method there's no need for opening and editing the build.prop file. The second to last command in the adb method will echo the necessary text to the build.prop file for you.
once again sry for my bad english.. i m just trying to share this with u guys so that we can make our xoom better
omnia1994 said:
once again sry for my bad english.. i m just trying to share this with u guys so that we can make our xoom better
Click to expand...
Click to collapse
Though I don't think I notice the change I do thank you for sharing the info.
Just for kix ill take a look at this. If its cool ill make a nice clean zip package
So is this going to become a zip?
This will have to be "flashed" through adb and your a100 needs to be on the newest update.
[STOCK ROM] Official Packages It's the first link on that post. We can thank vache for that.
All bloatware is still included, also acer's MusicA.odex did not deodex and is included.
Code:
$ adb shell
$ su
# stop
# mount -wo remount /system
# rm /system/app/*
# rm /system/framework/*
# cd /mnt/external_sd/path_to_tar
# busybox tar xvf A100_2.007.04_COM_GEN1_deodex.tar -C /
Permissions should be fine as it is in tar format otherwise:
Code:
# chmod 644 /system/app/*
# chmod 644 /system/framework/*
dalvik cache will be about 20MB larger and it should be wiped
Code:
# busybox rm /data/dalvik-cache/*
# exit
$ exit
$ adb reboot
It will take a bit longer on the first boot while the cache rebuilds
For anyone that doesn't know deodexing is only useful for creating a ROM/theme.
After any theming of the apps permissions will have to be set and keep the official stock ROM in hand in case of a bootloop.
Code:
# chmod 644 /system/app/apk_package
or
# chmod 644 /system/framework/jar_package
I've been running this for a few days and have had no issues at all.
Using this method we can start building some ROMS. I would suggest using tar and maybe include a small script to flash it.
Let me know if anyone wants a full ROM package as this is only the apps and framework.
A100_2.007.04_COM_GEN1_deodex.tar - 191.05 MB
[edit] As it turns out MusicA does not work at all, it doesn't even show up in the app drawer. Some guy named Jeff Lee compiled some of the framework wrong. com.acer.android.clearfilib_tablet.jar/C:/Users/Jeff_lee/Desktop/_acer/Jeff/clearfilib_tablet.java will not work. It should be a classes.dex file in the jar archive. Oh well it looks like its fixed in ICS.
02/22/12
Here's Deodex ICS, everything deodexed without issues. But without root this will be useless. [edit] We now have root so this will be very useful
A100_0.002.00_WW_GEN1_deodex.tar - 206.06 MB
Pending...
I was meaning to do this for a few days now and I am glad to see it works.
Did you do some more testing to see how it is, performance-wise?
Icewyng said:
I was meaning to do this for a few days now and I am glad to see it works.
Did you do some more testing to see how it is, performance-wise?
Click to expand...
Click to collapse
Nothing more than opening the stock apps and using it as I normally do. Just ran linpack, it got the same result as before deodexing. It really shouldn't run any better or worse. Though odex is supposed to be faster than using the dex format. It's also zipaligned so that can also speed things up a bit to compensate.
eww245 said:
This will have to be "flashed" through adb and your a100 needs to be on the newest update.
[STOCK ROM] Official Packages It's the first link on that post. We can thank vache for that.
All bloatware is still included, also acer's MusicA.odex did not deodex and is included.
Code:
$ adb shell
$ su
# stop
# mount -wo remount /system
# rm /system/app/*
# rm /system/framework/*
# cd /mnt/external_sd/path_to_tar
# busybox tar xvf A100_2.007.04_COM_GEN1_deodex.tar -C /
Permissions should be fine as it is in tar format otherwise:
Code:
# chmod 644 /system/app/*
# chmod 644 /system/framework/*
dalvik cache will be about 20MB larger and it should be wiped
Code:
# busybox rm /data/dalvik-cache/*
# exit
$ exit
$ adb reboot
It will take a bit longer on the first boot while the cache rebuilds
For anyone that doesn't know deodexing is only useful for creating a ROM/theme.
After any theming of the apps permissions will have to be set and keep the official stock ROM in hand in case of a bootloop.
Code:
# chmod 644 /system/app/apk_package
or
# chmod 644 /system/framework/jar_package
I've been running this for a few days and have had no issues at all.
Using this method we can start building some ROMS. I would suggest using tar and maybe include a small script to flash it.
Let me know if anyone wants a full ROM package as this is only the apps and framework.
A100_2.007.04_COM_GEN1_deodex.tar - 191.05 MB
Click to expand...
Click to collapse
Great work eww245! I am definately interested.....just noticed your thread today.
Is there a way to do this on the tablet itself?? Thanks for the work....
Sent from my ADR6400L using xda premium
BrothaJINC said:
Is there a way to do this on the tablet itself?? Thanks for the work....
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Probably but be prepared for a lot of force closings. I suggest you immediately end it with reboot ex: # busybox tar x.... ; reboot
and don't use stop, the screen will go black. Good Luck
So just put in the code above on a terminal then reboot. And have the file on the sdcard
Sent from my ADR6400L using xda premium
BrothaJINC said:
So just put in the code above on a terminal then reboot. And have the file on the sdcard
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Yep, not sure if your on ICS but I haven't tested it yet.
No I'm trying to get to ics... I'm on gen2.... Will post back how it went.... Thanks for the help...
Sent from my ADR6400L using xda premium
Using this method we can start building some ROMS. I would suggest using tar and maybe include a small script to flash it.
Let me know if anyone wants a full ROM package as this is only the apps and framework.
A100_2.007.04_COM_GEN1_deodex.tar - 191.05 MB
hello eww245, i am not familiar with this and at the risk of sounding like a total newb, how would one go about this....what i mean is could you just give the basics to get me started....how would we get past the acer signature and checksums? thanks so much for your hard work
oneovakindoldys2 said:
Using this method we can start building some ROMS. I would suggest using tar and maybe include a small script to flash it.
Let me know if anyone wants a full ROM package as this is only the apps and framework.
A100_2.007.04_COM_GEN1_deodex.tar - 191.05 MB
hello eww245, i am not familiar with this and at the risk of sounding like a total newb, how would one go about this....what i mean is could you just give the basics to get me started....how would we get past the acer signature and checksums? thanks so much for your hard work
Click to expand...
Click to collapse
As far as signatures, all the apks and jars are signed but unless you sign them with all the same keys, files will have to be added / replaced in the archive. They are just zip files.
One tool baksmalli code.google.com/p/smali/ allows the code to be extracted into smalli code, which is quite difficult to read. That's what I used to deodex the files, but something like adding a reboot menu to the long press power button is possible.
Another, ApkTool code.google.com/p/android-apktool/ Will decode all the xml files and extract the images. With that it's possible to change or add string values. Like new translation values or changing text that's already there.
The eaisest edit would be just replacing images. So using 7zip or if you use linux xarchiver works good. As I mentioned above if the apks/jars are unzipped and rezipped the signature changes. So the images will have to be replaced in the archive.
I haven't experiment much yet my self, I tried to change the autobacklight values without any effect, but I did manage to add a CRT power off effect to the framework-res.apk.
Good luck hopefully this helps.
eww245 said:
As far as signatures, all the apks and jars are signed but unless you sign them with all the same keys, files will have to be added / replaced in the archive. They are just zip files.
One tool baksmalli code.google.com/p/smali/ allows the code to be extracted into smalli code, which is quite difficult to read. That's what I used to deodex the files, but something like adding a reboot menu to the long press power button is possible.
Another, ApkTool code.google.com/p/android-apktool/ Will decode all the xml files and extract the images. With that it's possible to change or add string values. Like new translation values or changing text that's already there.
The eaisest edit would be just replacing images. So using 7zip or if you use linux xarchiver works good. As I mentioned above if the apks/jars are unzipped and rezipped the signature changes. So the images will have to be replaced in the archive.
I haven't experiment much yet my self, I tried to change the autobacklight values without any effect, but I did manage to add a CRT power off effect to the framework-res.apk.
Good luck hopefully this helps.
Click to expand...
Click to collapse
Thanks alot Eww, I will do some research on this and see what I can come up with. In the meantime, I have a question [mission actually...lol] for anyone that might have some knowledge. I have been working on cracking fastboot and nvflash on our a100 so we can flash custom roms. I have come to the conclusion that our fastboot/nvflash is locked/disabled in the default prop and init. I have been working on this in my spare time....anyway, this is the progress i have made so far ....i have extracted the leaked ics release, decompressed it, extracted the boot image, unpacked it and used split_boot to seperate the ramdisk from the kernel and made the changes that I thought were necessary. I then used mkboot and finally got it gzipped up without any errors. I now have an edited boot.img for the a100 that should enable fastboot operation, however I have no way to get it back on to the tablet.....tis is the dilemma! Any suggestions with merit will certainly be appreciated. thanks again
How do get cm7 to boot? i flashed it on safestrap 3.05 but all i get is black screen. also check y D3 rom Collection filled the best D3 roms https://www.mediafire.com/folder/b0gq735hrqxx6/Droid_3_ROMS