Develop Bugs

How to re-odex a rom

odex again is not so easy...for system/app i use this:
http://forum.xda-developers.com/showthread.php?t=734236
but if you want also framework odexed...?! that is tricky...(coolexe helped me and maked a odex script for me..was written for desire..changed it to work on one x...) because you must look at the boothclass order (find in the kernel init.rc....if the order is a other then in the script you get a not booting rom....
if you want booth apps and framework odexed...you must make framework first odexed ""important"" or you will get a not booting rom...
here´s the new scxript for framework
for jb version of the script..take the one attached..and remove the txt...not the sourceforge version which is for ics
https://sourceforge.net/projects/alexvhtcroms/files/odex.sh/download
steps for framework:
adb push odex.sh /data
adb push dexopt-wrapper /system/bin +xbin (can be found in system app odex link)
adb shell chmod 755 /data/odex.sh
adb shell chmod 755 /system/bin+xbin/dexopt-wrapper
adb shell /data/odex.sh
adb pull /system/framework reodex-framework-onex
now you must manual cut the classes.dex file from the jar files...(be sure you have a meta-inf in each file)
after that make a new-half odexed rom..flash and do the rest with system app...
with kind regards...Alex

how about this one?
http://forum.xda-developers.com/showthread.php?t=1514576

zerozoneice said:
how about this one?
http://forum.xda-developers.com/showthread.php?t=1514576
Click to expand...
Click to collapse
never seen...not bad.. but it seems that is only for system app..system app can also be re-odexed using titanium backup pro...main part is the framwork
with kind regards

I think this way should be the easiest. I've been using it for a few months now and it worked every time without any issues. Just need to remember that every *.jar file in framework folder needs to have it's classes.dex inside (you can drag'n'drop the one from any other .jar that has it into ones that don't using 7zip). The script itself reads your boothclasspath and removes dalvik afterwards so you ultimately boot into a fully odexed rom. As always, it's recommended to make a nandroid before attemting to do this.

PlayPetepp said:
I think this way should be the easiest. I've been using it for a few months now and it worked every time without any issues. Just need to remember that every *.jar file in framework folder needs to have it's classes.dex inside (you can drag'n'drop the one from any other .jar that has it into ones that don't using 7zip). The script itself reads your boothclasspath and removes dalvik afterwards so you ultimately boot into a fully odexed rom. As always, it's recommended to make a nandroid before attemting to do this.
Click to expand...
Click to collapse
can you look again to the link...get the site is not availeble...sounds interesting
with kind regards

big thanks to playpetepp for the site
http://themikmik.com/showthread.php?12988-Tool-App-Dexo-the-Universal-Odex-Utility
i tryed lots of scripts and other things but nothing work as good as this one (the One from the link above)
first try all is re-odex viperx 1.0.1 (take me only 10min.) to do
when it is done it wont reboot stuck with black screen (freeze)
hold the power button till the phone goes off and then bootup again
and your done
so big thanks for this

sebastiaan15 said:
big thanks to playpetepp for the site
http://themikmik.com/showthread.php?12988-Tool-App-Dexo-the-Universal-Odex-Utility
i tryed lots of scripts and other things but nothing work as good as this one
first try all is re-odex viperx 1.0.1 (take me only 10min.) to do
on when it is done it wont reboot stuck with black screen (freeze)
hold the power button till the phone goes off and then bootup again
and your done
so big thanks for this
Click to expand...
Click to collapse
Seems like very nice script..
But i can't find the files needed (dexo) on that page...

swemoza said:
Seems like very nice script..
But i can't find the files needed (dexo) on that page...
Click to expand...
Click to collapse
At the bottom of that post there's a highlighted "did you read everything". Click on it.
Btw, those scripts are the work of tommytomatoe. My part was negligible.
-. typewrited .-

PlayPetepp said:
At the bottom of that post there's a highlighted "did you read everything". Click on it.
Btw, those scripts are the work of tommytomatoe. My part was negligible.
-. typewrited .-
Click to expand...
Click to collapse
so big thanks to tommytomatoe
and also big thanks to you for posting it here

PlayPetepp said:
At the bottom of that post there's a highlighted "did you read everything". Click on it.
Btw, those scripts are the work of tommytomatoe. My part was negligible.
-. typewrited .-
Click to expand...
Click to collapse
Aha.. Thank you mate...

Tried your method in the 1st post , and it worked ! 100% .

The Mikmik method works great.Thx for the link. ARHD is a dream in odex
Sent from my HTC One X using xda premium

PlayPetepp said:
At the bottom of that post there's a highlighted "did you read everything". Click on it.
Btw, those scripts are the work of tommytomatoe. My part was negligible.
-. typewrited .-
Click to expand...
Click to collapse
Ah ha... your favorite subject mate

ckpv5 said:
Ah ha... your favorite subject mate
Click to expand...
Click to collapse
Ah ... you caught me. :highfive:

PlayPetepp said:
I think this way should be the easiest. I've been using it for a few months now and it worked every time without any issues. Just need to remember that every *.jar file in framework folder needs to have it's classes.dex inside (you can drag'n'drop the one from any other .jar that has it into ones that don't using 7zip). The script itself reads your boothclasspath and removes dalvik afterwards so you ultimately boot into a fully odexed rom. As always, it's recommended to make a nandroid before attemting to do this.
Click to expand...
Click to collapse
I used this one and I'm very happy with it. So easy to launch and the HOX is a little more reactive now.

Probs
I tried your script with bootclasspath adjusted to SGS3.
Just did bootclasspath jars.
Still no luck - bootloop.
dexo Tool worked from the get go. But - SystemUI doesn't work. No notification bar whatsover. At least I can boot. Retrying...
Alex-V said:
here´s the new scxript for framework
https://sourceforge.net/projects/alexvhtcroms/files/odex.sh/download
Click to expand...
Click to collapse

C:\fastboot>adb shell
[email protected]/# chmod 755 /system/bin/dexo /system/bin/dexopt-wrapper /system/xbin
/zip /system/xbin/zipalign /system/xbin/busybox
/system/xbin/zipalign /system/xbin/busybox <
/system/bin/sh: chmod: cannot execute - Permission denied
getting this error message when in adb shell, any ideas guys? commands were copied from site

Do "adb remount" before "adb shell".
-. typewrited .-

PlayPetepp said:
Do "adb remount" before "adb shell".
-. typewrited .-
Click to expand...
Click to collapse
thanks man, so thats use adb remount again after using the adb push commands? i have pushed the neccesary files
still getting the permission denied message : (
---------- Post added at 10:25 PM ---------- Previous post was at 10:21 PM ----------
C:\fastboot>adb remount
remount succeeded
C:\fastboot>adb shell
[email protected]/# chmod 755 /system/bin/dexo /system/bin/dexopt-wrapper /system/xbin
/zip /system/xbin/zipalign /system/xbin/busybox
/system/xbin/zipalign /system/xbin/busybox <
/system/bin/sh: chmod: cannot execute - Permission denied
126|[email protected]/#

Try "mount -o rw,remount /system" after entering "adb shell"
If you have root explorer app installed you could change permissions for folders from phone.
-. typewrited .-

[GUIDE] DEODEX Xperia S Stock Rom (6.1.A.2.45 ~ 6.2.B.1.96) - 27/8

Warning: This is very advanced, if you do not know what it is, dont play play.
I'm not responsible if your device bricked during deodexing process.
This method has been commonly used, I just improved it and included important cautions and precautions.
Requirements:
- Rooted firmware (Search XDA)
- Busybox installed (included when root with Root Many Droid)
- ADB correctly set up on computer *(sdk + environment variables setup)* ? - if u dont know what it is, as long as sdk installed is ok *(only sdk installed)*
- Xperia S with coresponding firmware version.
- In phone, usb debugging enabled, unknown sources enabled
- Downloaded app and framework zips
Downloads:
LT26i - 6.2.B.1.96 deodexed **not tested** by zhuhang
http://www.androidfilehost.com/?fid=23060877490002553​LT26i - 6.2.B.0.200 deodexed **not tested** by @davidbar93
https://www.dropbox.com/s/saog0fip6m8gsyf/done_app.rar
https://www.dropbox.com/s/d8s6rll8esatzny/done_frame.rar​LT26i - 6.1.A.2.55 deodexed **working** by zhuhang
http://www.androidfilehost.com/?fid=9390244042945593433
http://www.androidfilehost.com/?fid=9390244042945593434​LT26i - 6.1.A.2.50 deodexed **working** by zhuhang
http://www.androidfilehost.com/?fid=9390244042945593431
http://www.androidfilehost.com/?fid=9390244042945593432​LT26i - 6.1.A.2.45 deodexed **working** by zhuhang
http://www.androidfilehost.com/?fid=9390244042945593350
http://www.androidfilehost.com/?fid=9390244042945593351​
Instructions:
1. Extract downloaded zips
2. Copy done_app and done_frame to /sdcard/ (via MTP acceptable)
3. Make sure debugging mode connected
4. (i) Open Command Prompt on PC (Ctrl + R > cmd) *(sdk + environment variables setup)*
4. (ii) Go to /android-sdk/platform-tools/ folder, hold Shift button and right click mouse, 'Open Command window here' (Win 7) *(only sdk installed)*
5. Enter lines ony by one:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
busybox cp /sdcard/done_app/* /system/app/
busybox rm /system/app/*.odex
busybox cp /sdcard/done_frame/* /system/framework/
busybox rm /system/framework/*.odex
chmod 644 /system/app/*
chmod 644 /system/framework/*
busybox mount -o ro,remount /system/ /system/
reboot
6. Close Command Prompt
7. Wait for phone to reboot, you'll see "Android Upgrading, Optimizing aplications..."
8. If optimizing aplications succeed, congratulations, ur stock rom is deodexed! Done.
Note: Every time u put apks into /system/app/ and restart, Android Upgrading will appear for once.
Donations:
Its also recommended to make donation using Paypal balance. (lower transaction fee)
My Paypal Account is ready! Malaysian please PM me for local bank account.
I would appreciate if you can donate to me so I can maintain this OP. I'm also making IRS for you guys.
Credits:
Deodexed using dsixda's kitchen
Compressed using Winrar

Is it as simple as that?

eScapeeXc said:
Is it as simple as that?
Click to expand...
Click to collapse
Definitely yes if u know the commands and steps.
Try it yourself then, i've done hundred times on acroS and XS
Link to acroS in my sig.

zhuhang said:
Warning: This is very advanced, if you do not know what it is, dont play play.
I'm not responsible if your device bricked during deodexing process.
This method has been commonly used, I just improved it and included important cautions and precautions.
Requirements:
- Clean Rom (best with data wiped, orelse FCs)
- Rooted firmware (Root with Root Many Droid : here)
- Busybox installed (included when root with Root Many Droid)
- ADB correctly set up on computer *(sdk + environment variables setup)* ? - if u dont know what it is, as long as sdk installed is ok *(only sdk installed)*
- Xperia S with: usb debugging enabled, unknown sources enabled
- Downloaded app and framework zips
Downloads:
LT26i .45 deodexed
http://www.androidfilehost.com/?fid=9390244042945593350
http://www.androidfilehost.com/?fid=9390244042945593351​
Instructions:
1. Extract downloaded done_app and done_frame zips
2. Copy done_app and done_frame to /sdcard/ (via MTP acceptable)
3. Make sure debugging mode connected
4. (i) Open Command Prompt on PC (Ctrl + R > cmd) *(sdk + environment variables setup)*
4. (ii) Go to /android-sdk/platform-tools/ folder, hold Shift button and right click mouse, 'Open Command window here' (Win 7) *(only sdk installed)*
5. Enter lines ony by one:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
busybox cp /sdcard/done_app/* /system/app/
busybox rm /system/app/*.odex
busybox cp /sdcard/done_frame/* /system/framework/
busybox rm /system/framework/*.odex
busybox mount -o ro,remount /system/ /system/
reboot
Note: Do not change permissions of files to 644 or folders to 755! We'll do it later.
6. Leave Command Prompt open
7. Wait for phone to reboot, if optimizing aplications succeed, congratulations, ur stock rom is deodexed!
8. Now let's manually fix some permissions
9. Return to Command Prompt
10. Enter lines ony by one:
Code:
adb shell
su
mount -o rw,remount /system/ /system/
chmod 644 /system/app/*
chmod 644 /system/framework/*
busybox mount -o ro,remount /system/ /system/
reboot
11. After phone reboot, there should be no more "Android Upgrading, Optimizing aplications..."
12. Viola, Done!!
Note: Every time u put apks into /system/app/ and restart, Android Upgrading will appear for once.
Credits:
Deodexed using dsixda's kitchen
Packed using Winrar
Click to expand...
Click to collapse
Is this what u used for AC!D V6? is the internal speaker volume low?

darkace007 said:
Is this what u used for AC!D V6? is the internal speaker volume low?
Click to expand...
Click to collapse
This is deodexing stock ICS rom, nothing to do with any mod or acid v6
Do u know what's deodexing?

I dont exactly know but its about theming possibilties right but I saw one of ur posts that AC!D works for stock .45.
Sent from my LT26i using xda app-developers app

darkace007 said:
I dont exactly know but its about theming possibilties right but I saw one of ur posts that AC!D works for stock .45.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
Deodex is not for theming. U can understand it somewhere else
I will add advantages of deodexing to 1st post.
Acid v6 not working yet, I haven't really tested. V5 works.
It doesn't matter whether ur Rom is odexed or deodexed, the advantage is no android upgrade loop on deodexed Rom.
Sent from my LT26i using xda app-developers app

You can actually a package, which used here man. Sdk, busybox, etc. It would be better. And one more question. Is it exactly at .55?

eScapeeXc said:
You can actually a package, which used here man. Sdk, busybox, etc. It would be better. And one more question. Is it exactly at .55?
Click to expand...
Click to collapse
Sdk has to be installed (few hundred Mbs) + Java
Root+busybox link given.
I can't make a package for that. Maybe links. I will consider.
Its .45, I'll do .50 and .55, can anyone provide me the app and framework?

There was another Deodexed .45 thread here.... if it was .55 would been better...

s-X-s said:
There was another Deodexed .45 thread here.... if it was .55 would been better...
Click to expand...
Click to collapse
Very soon...
Sent from my LT26i using xda app-developers app

zhuhang said:
Sdk has to be installed (few hundred Mbs) + Java
Root+busybox link given.
I can't make a package for that. Maybe links. I will consider.
Its .45, I'll do .50 and .55, can anyone provide me the app and framework?
Click to expand...
Click to collapse
s-X-s said:
There was another Deodexed .45 thread here.... if it was .55 would been better...
Click to expand...
Click to collapse
Just a thought why don't take .55 deodex both app and framework from the ROM I post long ago. It is in zip format so you could easily extract app and framework then follow instruction in first post to inject to your ROM.

tosa.th said:
Just a thought why don't take .55 deodex both app and framework from the ROM I post long ago. It is in zip format so you could easily extract app and framework then follow instruction in first post to inject to your ROM.
Click to expand...
Click to collapse
Where did u posted it?

zhuhang said:
Where did u posted it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2005595

tosa.th said:
http://forum.xda-developers.com/showthread.php?t=2005595
Click to expand...
Click to collapse
U modified a little things.

zhuhang said:
U modified a little things.
Click to expand...
Click to collapse
Yes, I delete few app that recognize as bloat ware (this is recommended by rom kitchen) I see that you also use rom kitchen I believe you should see that as well.
The other change is not relate to app and framework.

tosa.th said:
Yes, I delete few app that recognize as bloat ware (this is recommended by rom kitchen) I see that you also use rom kitchen I believe you should see that as well.
The other change is not relate to app and framework.
Click to expand...
Click to collapse
Nope, i didnt saw which is recognized bloatware.
Which one?

zhuhang said:
Nope, i didnt saw which is recognized bloatware.
Which one?
Click to expand...
Click to collapse
Didn't write it down so can not tell you exactly which one.
It said some thing like do you want to remove bloatware ? I just say yes.
May be you could try to deodex .55 ROM then see if it detect any bloatware.

tosa.th said:
Didn't write it down so can not tell you exactly which one.
It said some thing like do you want to remove bloatware ? I just say yes.
May be you could try to deodex .55 ROM then see if it detect any bloatware.
Click to expand...
Click to collapse
I never encounter bloatware detected, anyway i will remove any apps.

Updated 27/12/12
Added:
LT26i - 6.1.A.2.50
LT26i - 6.1.A.2.55
Both not tested, let me know the result.
EDIT: Should be LT26i

Deodexed Help!

I want to have a Deodexed ROM without going and installing a different ROM. Is it possible to Deodex the 4.1.2 stock rom? Im sure it is. Im SGH-1317m on 4.1.2.
Thanks :fingers-crossed::good:

Pirlo#21 said:
I want to have a Deodexed ROM without going and installing a different ROM. Is it possible to Deodex the 4.1.2 stock rom? Im sure it is. Im SGH-1317m on 4.1.2.
Thanks :fingers-crossed::good:
Click to expand...
Click to collapse
u can use any of the deodex tools and kitchens, or just smali/baksmali like I do.
if u have link for this rom, I can do it for you.

Pirlo#21 said:
I want to have a Deodexed ROM without going and installing a different ROM. Is it possible to Deodex the 4.1.2 stock rom? Im sure it is. Im SGH-1317m on 4.1.2.
Thanks :fingers-crossed::good:
Click to expand...
Click to collapse
In titanium back up you can odex o4 deodex in settings
Sent from my GT-N7105 using xda premium

Android The Greek said:
In titanium back up you can odex o4 deodex in settings
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
How do i do that?

Sent from my GT-N7105 using xda premium

Android The Greek said:
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Oh yeah. I tried that. It didn't work on the stock rom

djodjoni said:
u can use any of the deodex tools and kitchens, or just smali/baksmali like I do.
if u have link for this rom, I can do it for you.
Click to expand...
Click to collapse
How do i use the smali or baksmali? i have android kitchen. I just cant run any of the .Jar files. If thats even what your supposed to do. sorry. im usually not this lost

Pirlo#21 said:
How do i use the smali or baksmali? i have android kitchen. I just cant run any of the .Jar files. If thats even what your supposed to do. sorry. im usually not this lost
Click to expand...
Click to collapse
I havent used any kitchen actually, just do things manually with some small dirty scripts
So smali/baksmali:
1) to run a jar you can just exe "java -jar baksmali.jar" for example
for that of course you need to have java installed and it needs to be in your path
the (bak)smali jars normally come with a script wrapper so you dont need to bother for the java thing. I ll explain later
2) to deodex you need to baksmali, then smali then pack the classes.dex back into the apk/jar, then zipalign (optional but recommended)
3) to backsmali: baksmali -a {API} -x {APP.odex} -d {Dependencies ex: framework} -o {OUT_DIR}
4) to smali: smali -a {API} -o {output.dex} {smali DIR-got from baksmali}
5) to pack: aapt a -v {the package to put it in apk/jar} {the.dex file got from smali}
note u may use any archiving tool i just reuse the tools i get from AOSP
6) to zipalign: zipalign -f 4 r {the package apk/jar} {the out zipaligned package apk/jar}
ur done.
You normally also need to deodex framework and then app folder.
So if this is a bit complicated to do it urself if you have linux environment you can:
1) download:
smali
baksmali
baksmali.jar
smali.jar
aapt
zipalign
deodex.sh
from: http://web.djodjo.org/?a=download:android:tools:x86_linux:alltools
2) put those in your ~/bin and chmod them to 777
3) get your system dir(or just system/app and system/framework) to some place
4) execute deodex.sh {fullpath to the system dir} {API for you it is 16}
and wait ...
In case you've got the ext4 sparsed image i.e. system.img
you can download deodexsystem.sh from the same link and execute:
sudo deodexsystem.sh system.img 16
this one will even pack it back to an ext4 sparsed image file so you can tar it and flash it with odin
enjoy

djodjoni said:
I havent used any kitchen actually, just do things manually with some small dirty scripts
So smali/baksmali:
1) to run a jar you can just exe "java -jar baksmali.jar" for example
for that of course you need to have java installed and it needs to be in your path
the (bak)smali jars normally come with a script wrapper so you dont need to bother for the java thing. I ll explain later
2) to deodex you need to baksmali, then smali then pack the classes.dex back into the apk/jar, then zipalign (optional but recommended)
3) to backsmali: baksmali -a {API} -x {APP.odex} -d {Dependencies ex: framework} -o {OUT_DIR}
4) to smali: smali -a {API} -o {output.dex} {smali DIR-got from baksmali}
5) to pack: aapt a -v {the package to put it in apk/jar} {the.dex file got from smali}
note u may use any archiving tool i just reuse the tools i get from AOSP
6) to zipalign: zipalign -f 4 r {the package apk/jar} {the out zipaligned package apk/jar}
ur done.
You normally also need to deodex framework and then app folder.
So if this is a bit complicated to do it urself if you have linux environment you can:
1) download:
smali
baksmali
baksmali.jar
smali.jar
aapt
zipalign
deodex.sh
from: http://web.djodjo.org/?a=download:android:tools:x86_linux:alltools
2) put those in your ~/bin and chmod them to 777
3) get your system dir(or just system/app and system/framework) to some place
4) execute deodex.sh {fullpath to the system dir} {API for you it is 16}
and wait ...
In case you've got the ext4 sparsed image i.e. system.img
you can download deodexsystem.sh from the same link and execute:
sudo deodexsystem.sh system.img 16
this one will even pack it back to an ext4 sparsed image file so you can tar it and flash it with odin
enjoy
Click to expand...
Click to collapse
thanks but none of the downloads work for me and i tried to do it with Cygwin but i cant keep a terminal open for more than 3 seconds before it crashes sorry. ive been busy. why it took me so long to get back. and i also tried doing the android kitchen in Ubuntu. but every time i try. that terminal also force closes. i don't know what going on!

Pirlo#21 said:
thanks but none of the downloads work for me and i tried to do it with Cygwin but i cant keep a terminal open for more than 3 seconds before it crashes sorry. ive been busy. why it took me so long to get back. and i also tried doing the android kitchen in Ubuntu. but every time i try. that terminal also force closes. i don't know what going on!
Click to expand...
Click to collapse
what do you mean "none of the downloads work for me".
You use those in ubuntu not in cygwin.
What exactly do you do when it crashes? do you see any messages?

djodjoni said:
what do you mean "none of the downloads work for me".
You use those in ubuntu not in cygwin.
What exactly do you do when it crashes? do you see any messages?
Click to expand...
Click to collapse
okay. Well. I cant seem to run the ./menu on ubuntu. ive tried several commands.

Success!
djodjoni said:
what do you mean "none of the downloads work for me".
You use those in ubuntu not in cygwin.
What exactly do you do when it crashes? do you see any messages?
Click to expand...
Click to collapse
Okay! im sorry for the really long wait reply. But i got everything to open well. I extracted the system.img, boot.img, cache.img and modem.bin from a stock rom .tar... I gave it root, gave it busybox. did all that stuff. but before i build it. whats the API level i need to deodex? is it 16?

[Q] How to make stock ROM support INIT.D

hi guys, a friend of mine is asking me if there's something i can do to make her cp a bit faster/ smoother running stock rom (gb 2.3.6) since he don't want to use any custom rom. her cp
searching the thread, i was able to read some info that some was able to flash mod/ tweaks on stock roms to at least improve its performance. so i'm planning to install andrenaline engine or crossbreader on it but, as far as i know, flashing them requires ur rom, aside from of course being rooted, have cwm, etc., to support init.d which stock roms don't have. (corect me if i'm wrong)
i'm a bit in doubt doing this in the fist place, so any guide/ help or suggestions to make this init.d thing work is really really much appreciated. thnx in advance!
info i got (xda forum) about making stock rom support init.d Enable Init.d for Any Phones w/o Need of Custom Kernels

here, this link provide init.d support;
http://forum.xda-developers.com/showpost.php?p=32716432&postcount=3
flash zip_init.zip.
copy zip_init.zip to sd-card,
boot to cwm, mount /system, mount /data then flash zip_init.zip
check for test.log in /data if it is there or not, no test.log not working.
it work on my stock rom.
also flash adrenoboost v0.7 will boost perfromance from stock 5000 to 7000 (antutu benchmark).
adrenoboost link;
http://forum.xda-developers.com/showthread.php?t=2167228

saintsoh said:
here, this link provide init.d support;
http://forum.xda-developers.com/showpost.php?p=32716432&postcount=3
flash zip_init.zip.
copy zip_init.zip to sd-card,
boot to cwm, mount /system then flash zip_init.zip
check for test.log in /data if it is there or not, no test.log not working.
it work on my stock rom.
also flash adrenoboost v0.7 will boost perfromance from stock 5000 to 7000 (antutu benchmark).
adrenoboost link;
http://forum.xda-developers.com/showthread.php?t=2167228
Click to expand...
Click to collapse
thnx for the reply bro. about the adrenoboost, i think its main purpose is to boost the performance of Adreno 205 GPU or similar gpu but my friends device doesn't have gpu.

i didnt know tat.
anyway i think after mount /system, u should also mount /data (just in case).
it work on my sgw without mount /data but then i saw check /data for test.log which makes it necessary or not?
i'm not sure, just be on the safe side mount /data.

saintsoh said:
i didnt know tat.
anyway i think after mount /system, u should also mount /data (just in case).
it work on my sgw without mount /data but then i saw check /data for test.log which makes it necessary or not?
i'm not sure, just be on the safe side mount /data.
Click to expand...
Click to collapse
okay, i'll try that and hope it'll work
EDIT: sad, it didn't work

just learn something new when i reverted back to stock and re-install zip-init for init.d support.
when flash zip_init.zip and reboot, cwm will ask to "disable recovery flash" - select "NO".
(note: if select "yes", it will give a false positive, 'install-recovery.sh' will not have execute permissions and init.d support will not work).
after troubleshoot found out the install-recovery.sh is not in execute permission (rwxr--r-- instead of rwxr-xr-x).
by correcting the 'install-recovery.sh' permission, init.d support will work again.
ps;
must install busybox app (do a normal install).

saintsoh said:
just learn something new when i reverted back to stock and re-install zip-init for init.d support.
when flash zip_init.zip and reboot, cwm will ask to "disable recovery flash" - select "NO".
(note: if select "yes", it will give a false positive, 'install-recovery.sh' will not have execute permissions and init.d support will not work).
after troubleshoot found out the install-recovery.sh is not in execute permission (rwxr--r-- instead of rwxr-xr-x).
by correcting the 'install-recovery.sh' permission, init.d support will work again.
ps;
must install busybox app (do a normal install).
Click to expand...
Click to collapse
i got busybox installed, but i'm having status 0 error in CWM. in troubleshooting guide, it says replace the update-binary in zip-init.zip with a working update-binary of your phone and i don't how to do it

dec0der said:
i got busybox installed, but i'm having status 0 error in CWM. in troubleshooting guide, it says replace the update-binary in zip-init.zip with a working update-binary of your phone and i don't how to do it
Click to expand...
Click to collapse
update-binary is in the zip file, just download the latest which is the v2 and re-flash again.
if still doesn't work, try get help from init.d support thread.
i didn't get it working on the first time twice but somehow get it work again again.

saintsoh said:
update-binary is in the zip file, just download the latest which is the v2 and re-flash again.
if still doesn't work, try get help from init.d support thread.
i didn't get it working on the first time twice but somehow get it work again again.
Click to expand...
Click to collapse
it was v2 of zip_init that i use and i think i re flashed it 5x already and still getting that error anyways, thnx 4 ur help bro, godbless!

dec0der said:
it was v2 of zip_init that i use and i think i re flashed it 5x already and still getting that error anyways, thnx 4 ur help bro, godbless!
Click to expand...
Click to collapse
superusers app needed for terminal emulator, fx explorer(root access), busybox and script manager apps installed for root access.
use script manager, look for install-recovery.sh in /etc or system/etc (both r the same directory).
touch su n boot icon, su will turn green n boot will turn blue. reboot.
or
use fx explorer to set file permissions if u do not know linux commands.
google play search for fx explorer app and fx root addon (enable root access).
use root folder, look for install-recovery.sh in system/etc.
touch tool menu below and mount read-write then u can change file permission.
or
if u r familiar with linux commands, u can use terminal emulator to change file permission.
check install-recovery.sh permission is rwxr-xr-x, not other like rwxr--r--.
how2check in emulator, type n press enter:
ls -l etc/inst* ↵
how2change file permission, type n press enter:
su ↵
cd etc ↵
mount -o remount rw /system ↵
chmod 755 install-recovery.sh ↵
exit ↵
exit ↵
done, there shouldnt be any error, reboot.
if not re-flash zip_init.zip, reboot, select "NO" to disable flash recovery.

saintsoh said:
superusers app needed for terminal emulator, fx explorer(root access), busybox and script manager apps installed for root access.
use script manager, look for install-recovery.sh in /etc or system/etc (both r the same directory).
touch su n boot icon, su will turn green n boot will turn blue. reboot.
or
use fx explorer to set file permissions if u do not know linux commands.
google play search for fx explorer app and fx root addon (enable root access).
use root folder, look for install-recovery.sh in system/etc.
touch tool menu below and mount read-write then u can change file permission.
or
if u r familiar with linux commands, u can use terminal emulator to change file permission.
check install-recovery.sh permission is rwxr-xr-x, not other like rwxr--r--.
how2check in emulator, type n press enter:
ls -l etc/inst*
how2change file permission, type n press enter:
su
cd etc
mount -o remount rw /system
chmod 755 install-recovery.sh
exit
exit
done, there shouldnt be any error, reboot.
if not re-flash zip_init.zip, reboot, select "NO" to disable flash recovery.
Click to expand...
Click to collapse
busybox was installed correctly as i can see the folder bin/ xbin. it's rooted already so superuser was in there and i used root explorer file manager. i can't find install-recovery.sh in /etc or system/etc which maybe means that it was not working

dec0der said:
busybox was installed correctly as i can see the folder bin/ xbin. it's rooted already so superuser was in there and i used root explorer file manager. i can't find install-recovery.sh in /etc or system/etc which maybe means that it was not working
Click to expand...
Click to collapse
1) phone is rooted,
2) superuser app installed,
3) busybox app installed,
4) root explorer file manager app installed,
5) no install-recovery.sh in /etc or system/etc?
6) no test.log in /data?
7) re-flash zip_init.zip, reboot, select 'NO' to disable flash recovery?
8) no init.d directory in /etc?
9) in etc/init.d directory, there should have two files 00test n 08setperm. in /etc should have install-recovery.sh file.
10) u dont have these three files?
flashing cant write on system directory, means manufacturer locked the system.
unless u can find way to break the lock.

saintsoh said:
1) phone is rooted,
2) superuser app installed,
3) busybox app installed,
4) root explorer file manager app installed,
5) no install-recovery.sh in /etc or system/etc?
6) no test.log in /data?
7) re-flash zip_init.zip, reboot, select 'NO' to disable flash recovery?
8) no init.d directory in /etc?
9) in etc/init.d directory, there should have two files 00test n 08setperm. in /etc should have install-recovery.sh file.
10) u dont have these three files?
flashing cant write on system directory, means manufacturer locked the system.
unless u can find way to break the lock.
Click to expand...
Click to collapse
1-4 yes, all done
5-10 don't have those files coz i got status 0 error flashing zip_init.zip v2 in CWM
if thats the case, maybe i'll try to flash different stock firmware 1st

dec0der said:
1-4 yes, all done
5-10 don't have those files coz i got status 0 error flashing zip_init.zip v2 in CWM
if thats the case, maybe i'll try to flash different stock firmware 1st
Click to expand...
Click to collapse
try manually put in those files in their respectively directories.
unzip n try putting those files in their respective order.
create a init.d directory in /etc then put those two files 00test n 08setperm into it.
put the install-recovery.sh in /etc, set all permissions to rwxrwxrwx.
(upload manager doesnt allow .sh file, rename install-recovery.sh.txt to install-recovery.sh)
done, reboot n see it works or not.

saintsoh said:
try manually put in those files in their respectively directories.
unzip n try putting those files in their respective order.
create a init.d directory in /etc then put those two files 00test n 08setperm into it.
put the install-recovery.sh in /etc, set all permissions to rwxrwxrwx.
(upload manager doesnt allow .sh file, rename install-recovery.sh.txt to install-recovery.sh)
done, reboot n see it works or not.
Click to expand...
Click to collapse
okay, i'll try that. thnx

「HELP」Deodexing Acro S

Guys I need some help.
I am trying to deodex my friend's Acro S using this tool here: http://forum.xda-developers.com/showthread.php?t=2176241
I can make the sytem dump but can't deodex it. I followed the instruction on how to get the bootclasspath and I am sure of the bootclasspath I am inputing but gives me an error saying "The system cannot find the specified path." After pasting the bootclasspath and pressing enter, the tool just returns to the start asking what I want to do. Anyway can someone post their bootclasspath here for verification.
Did anyone here tried using this tool?
My friend's Acro S in on stock .96 rom, rooted, and unlocked bootloader.
Any help will be greatly appreciated.

ronin1728 said:
Guys I need some help.
I am trying to deodex my friend's Acro S using this tool here: http://forum.xda-developers.com/showthread.php?t=2176241
I can make the sytem dump but can't deodex it. I followed the instruction on how to get the bootclasspath and I am sure of the bootclasspath I am inputing but gives me an error saying "The system cannot find the specified path." After pasting the bootclasspath and pressing enter, the tool just returns to the start asking what I want to do. Anyway can someone post their bootclasspath here for verification.
Did anyone here tried using this tool?
My friend's Acro S in on stock .96 rom, rooted, and unlocked bootloader.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
The bootclasspath files generally are the files in /system/framework. So you need the files present in /system/framework.
Or you can use my tool over here - http://forum.xda-developers.com/showthread.php?t=2213235
I am sure that it will work for Acro S.

abcdjdj said:
The bootclasspath files generally are the files in /system/framework. So you need the files present in /system/framework.
Or you can use my tool over here - http://forum.xda-developers.com/showthread.php?t=2213235
I am sure that it will work for Acro S.
Click to expand...
Click to collapse
Oh thank goodness you are here. Yes I saw your tool too. And I have some questions about what to do (^^)d
1st: The apks that need deodexing are inside the /system/app, everything inside???
2nd: What about the jar files, where are they located? I am unsure where I can find these.
3rd: After I successfully deodex the apk & jar files, do I need to manually zipaligned them?
4th: And can I just copy/paste the deodexed files in /system?
Thank you in advance. (^-^)v

ronin1728 said:
Oh thank goodness you are here. Yes I saw your tool too. And I have some questions about what to do (^^)d
1st: The apks that need deodexing are inside the /system/app, everything inside???
2nd: What about the jar files, where are they located? I am unsure where I can find these.
3rd: After I successfully deodex the apk & jar files, do I need to manually zipaligned them?
4th: And can I just copy/paste the deodexed files in /system?
Thank you in advance. (^-^)v
Click to expand...
Click to collapse
1. Yes, the apks in /system/app need to be deodexed, but some of them are already deodexed. Simply pull all the apks from your phone and place them in the "apks" folder of my tool. The already deodexed apks will be automatically deleted
2. Jar files are located in /system/framework. You can use the pull from framework option in my tool. It will pull all the framework files.
3. Yes, you will have to manually zipalign all the apks. Sorry
4. It is better if you make a flashable zip, or try this - first keep the deodexed apks in /sdcard/done_app and the deodexed framework files in /sdcard/done_frame. I would still recommend you to make a flashable zip as it is the safest.
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
Regards,
abcdjdj