[HOW-TO] Manually deodex your phone.

Search This thread

aholeinthewor1d

Senior Member
Aug 19, 2010
1,145
259
Run steps 1-3 and then switch the connection mode on ur phone to media sync before u start step 4

Sent from my DROIDX using Tapatalk
 

Muchoburrito

New member
Oct 2, 2010
4
0
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system

When I type in this mount command, I get the following message:

mount: Device or resource busy

I assume it doesn't matter much, as dr 154's post for revised command lines doesnt even include this mount command...just exits.

I am hoping this is the answer because I am sticking with it. lol If this is a bad idea, please tell reply. :)



so try these, which worked for me...

adb shell
su
stop
mount -o remount,rw /dev/block/system /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
exit
exit
adb reboot
 

Muchoburrito

New member
Oct 2, 2010
4
0
Everything went through cleanly. This is what you are supposed to get as the results. Odex failed because you are "de"odexing. :)

Test log:

( 1:47:07.15 Tue 10/19/2010)
****
C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Intel\DMIX;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\Common Files\Roxio Shared\10.0\DLLShared\;C:\Program Files\Common Files\DivX Shared\;C:\Program Files\QuickTime\QTSystem\
****
C:\Windows\system32\java.exe
****
Main ADB
Android Debug Bridge version 1.0.26
****
PATH ADB
****
[ro.build.id]: [VZW]

[ro.build.display.id]: [VZW]

[ro.build.version.incremental]: [2.3.15]

[ro.build.version.sdk]: [8]

[ro.build.version.codename]: [REL]

[ro.build.version.release]: [2.2]

[ro.build.date]: [Wed Sep 1 21:13:50 CDT 2010]

[ro.build.date.utc]: [1283393630]

[ro.build.type]: [user]

[ro.build.user]: [w30471]

[ro.build.host]: [il93lnxdroid08]

[ro.build.tags]: [test-keys]

[ro.build.product]: [shadow_vzw]

[ro.build.description]: [cdma_shadow-user 2.2 VZW 2.3.15 ota-rel-keys,release-keys]

[ro.build.fingerprint]: [verizon/shadow_vzw/cdma_shadow/shadow:2.2/VZW/23.15:user/ota-rel-keys,release-keys]

[ro.build.version.full]: [Blur_Version.2.3.15.MB810.Verizon.en.US]

[ro.build.config.version]: [GAS_NA_GCXSHAD00VZW_P022]

[ro.build.config.date]: [Wed_Sep_01_21:13:04_-0500_2010]

****
****
-Windows x86-
-adb pull- **PASS**
-odex- **FAIL**
-7z- **PASS**
-busybox- **PASS**
-java- **PASS**
-temp- **PASS**




******************************
For those that are stuck at the command line, this is what you need to do:

1. Download android sdk packages (look up on google) and extract them to
c:\AndroidSDK and then run the SDK Manager to install the packages.
2. With your phone connected and in pc mode, open up a cmd prompt on your computer.... i.e. click start, type cmd, click enter and a dos prompt should open up.
3. type cd\
4. type cd\AndroidSDK\tools\
5. Now type the commands
 
Last edited:

tripp7453

New member
Oct 30, 2010
1
0
can't remove directories

I'm a newbie to Droid X and Linux, so be gentle ...
I did the following in the command window:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/

When I tried rm /system/app/*.odex I received an error message saying "rm failed for /system/app/AccountAndSyncSettings.odex, Read-only file sytem".

Does that matter or can I continue?
 

Sleuth255

Retired Senior Moderator
Mar 3, 2006
3,551
38
Milwaukee
blog.kwilcox.org
I'm a newbie to Droid X and Linux, so be gentle ...
I did the following in the command window:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/

When I tried rm /system/app/*.odex I received an error message saying "rm failed for /system/app/AccountAndSyncSettings.odex, Read-only file sytem".

Does that matter or can I continue?

hmm.. not sure why your filesystem reverted to ro mode especially since the cp commands worked.
 
Last edited:

ppazz1101

Member
Feb 27, 2009
34
1
Pittsburgh, PA
Everything works until i try to copy the files. It starts working, then i get "cp: write error: no space left on device". Any ideas? I've tried multiple times and every time it freezes. I have to restore after that.
 

ghostlypickel

Senior Member
Jan 6, 2010
58
25
Everything works until i try to copy the files. It starts working, then i get "cp: write error: no space left on device". Any ideas? I've tried multiple times and every time it freezes. I have to restore after that.

Either you don't have enough space on your device, or maybe you don't have /system mounted?
 

Sleuth255

Retired Senior Moderator
Mar 3, 2006
3,551
38
Milwaukee
blog.kwilcox.org
for "not enough space" issues, try removing apps that you downloaded (you can re-install them later) or use a program like Titanium Backup to remove bloatware. The DX wiki has a link to a list of bloatware apps that can be safely removed.
 
Last edited:

lunchbox2

Member
Dec 11, 2010
10
0
Something went wrong during this process

hey guys, I was in the middle of doing this, and got to the final steps where you have to mount stuff. This is what I did:

C:\Program Files\Android\android-sdk-windows\platform-tools>adb shell
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# cp /sdcard/done_app/* /system/app/
cp /sdcard/done_app/* /system/app/
# cp /sdcard/done_frame/* /system/framework/
cp /sdcard/done_frame/* /system/framework/
# rm /system/framework/*.odex
rm /system/framework/*.odex
# rm /system/app
C:\Program Files\Android\android-sdk-windows\platform-tools>adb shell

As I was typing in the rm /system/app command, the phone disconnected from the computer for some reason, and i got booted back to the prompt:
C:\Program Files\Android\android-sdk-windows\platform-tools>

I tried to run shell again but I just got the error: device not found message.

Now when I try to turn on my phone, I get a bunch of weird messages on a black background saying

"The application Voice Commands (process com.nuance.android.bsuite.vsuiteapp) has stopped unexpectedly. Please try again." It says force close, but if I do that, the message just pops up again.

What do I do! I can't use my phone at all!

Update: Now the message has gone away, but the phone is black. I see the top menu bar, where it tells me the time (which is wrong), shows the battery bar, and shows that I am not connected to a network. It also shows me the advanced task killer little green icon. I can pull down the notifications menu bar, but it won't let me launch task killer. The power button works, as does the back button to get out of the power menu, but that is all that is working right now. Is there a way to just reinstall everything? I did a rom backup, but its stored on the phone I think. I used the rom manager to make the backup.

EDIT: Found SBF info, flashed. Phone is working again.
 
Last edited:

BuzzFuzz

Account currently disabled
Feb 16, 2010
690
172
46
GB
meettomy.site
Why Error:

1.jpg
 

Ronbo85

Senior Member
Dec 5, 2010
127
10
Ft Lauderdale
I too have run into problems, i have DX OTA 2.2 rooted, Trying to deodex using ultimate v.2.2.1 , i get through steps 1-3 fine, but when i start 4 it makes it to 30 out of 43 and hangs on core.odex then says:

Starting core.odex
*****************************************
* Deodexing... *


UNEXPECTED TOP-LEVEL ERROR:
java.lang.OutOfMemoryError: Java heap space
at java.util.TreeSet.<init>(Unknown Source)
at org.jf.dexlib.Code.Analysis.AnalyzedInstruction.<i nit>(AnalyzedInstru
ction.java:53)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.buildIn structionList(Metho
dAnalyzer.java:462)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.<init>( MethodAnalyzer.java
:113)
at org.jf.baksmali.Adaptors.MethodDefinition.addAnaly zedInstructionMetho
dItems(MethodDefinition.java:351)
at org.jf.baksmali.Adaptors.MethodDefinition.getMetho dItems(MethodDefini
tion.java:290)
at org.jf.baksmali.Adaptors.MethodDefinition.writeTo( MethodDefinition.ja
va:130)
at org.jf.baksmali.Adaptors.ClassDefinition.writeMeth ods(ClassDefinition
.java:322)
at org.jf.baksmali.Adaptors.ClassDefinition.writeVirt ualMethods(ClassDef
inition.java:307)
at org.jf.baksmali.Adaptors.ClassDefinition.writeTo(C lassDefinition.java
:136)
at org.jf.baksmali.baksmali.disassembleDexFile(baksma li.java:189)
at org.jf.baksmali.main.main(main.java:278)
Press any key to continue . . .

then:

*****************************************
MAJOR ERROR!! WITH DEODEXING! core.odex
*****************************************
********DELETING INCORRECT FILES*********
please exit out of window "***Deodexing ADB Window, DO NOT EXIT!***"

Press any key to continue . . .


then :

*****************************************
ERROR! Something Happened??? FIX IT!
*****************************************

Press any key to continue . . .

then:


-xUltimate Script v2.2.1-
ROM: VZW
*****************************************
Choices: (Do not use anything here!! Press "7")
*****************************************

(1) Pull /system/app/ from phone (origi_app)
(2) Pull /system/framework/ from phone (origi_frame)
(3) Deodex /system/app/ (Output="done_app")
(4) Deodex /system/framework/ (Output="done_frame")
(5) Pull and Deodex all
(6) Backup original files
(7) Exit
(8) Help
(10) Deodex from /sdcard/odex/ (system and app)
(15) ADVANCED

Type Choice number:

I have the same exact problem. I have tried so many different suggestions & been reading and searching many forums for hours and seen this posted quite a few times but never really answered. I did see this mentioned in the help section for the application...

"ADVANCED MENU- Option "2" will apply the core.odex patch (REQUIRED) if your phone is originally has .odex files and you deodex. v1.0
*NOTE: The core.odex patch is only required if you phone is NOT deodexed (Do not use if your phone has no .odex files OR you have a mixed ROM!)*"

but in my version of xultimate (2.2.2 & 2.2) ADVANCED MENU Option 2 says TBA and is not available.

My D X is rooted with Froyo 2.2
 
Last edited:

Ronbo85

Senior Member
Dec 5, 2010
127
10
Ft Lauderdale
In case anyone stumbles on this problem too I found a thread somewhere that addresses the problem. What you have to do is update your java on your PC. Thats what some other posters did to resolve the issue and it worked for me as well. I simply went to the sun micro site d-load section and grabbed an update.... problem solved!
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    I AM NOT RESPONSIBLE FOR WHATEVER HAPPENS TO YOUR PHONE!

    You must be rooted!


    This is a guide on manually deodexing, you phone. (Duh!)

    The reason I am making this tutorial is because I could not get my theme to work with Teenfaces deodexed nandroid. You may want to follows this if you have the same problem as me, or if you just want to take a shot at doing it.

    What you'll need:
    A Windows based machine
    xUltimate v2.2
    Patience

    Process:

    1. Unzip xUltimate v2.2, and launch "Main.exe"
    2. If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
    3. Run option 1. After option 1 is done, run option 2.
    4. Now these well take a while. Run option 3.
    5. IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
    6. Now run option 4, and wait.
    7. Exit xUltimate, and put the phone in USB mass storage.
    8. Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
    9. Put the phone in PC mode
    10. Open a command prompt, and do the following:

    Code:
    adb shell
    su
    stop
    mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
    cp /sdcard/done_app/* /system/app/
    cp /sdcard/done_frame/* /system/framework/
    rm /system/app/*.odex
    rm /system/framework/*.odex
    mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
    reboot

    Your phone should now be deodexed!

    You may notice an increase in speed, and you now have the ability to edit certain files with greater effects. (i.e. services.jar)

    Credits:
    Rainabba and Mike919: For initially working with me to get a white clock, and later deodex.
    toxman: For testing, and being a huge risk taker.
    teenfaces: For letting me use his services.jar
    And especially Xeudoxus: For letting me a guinea pig, for xUltimate, and answering my questions. And also for the making the xUltimate tool. It defiantly makes thing easier.
    1
    So when you run the test and everything passes except odex, does that mean the deodex worked? it seems like nothing would be left odexed because you deodexed it. does that sound right. I know this was mentioned through the thread but was never fully answered.

    How do you know for sure if it worked or not?

    Thanks, Hell
    1
    ghostlypickel; said:
    1. Unzip xUltimate v2.2, and launch "Main.exe"
    2. If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
    3. Run option 1. After option 1 is done, run option 2.
    4. Now these well take a while. Run option 3.
    5. IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
    6. Now run option 4, and wait.
    7. Exit xUltimate, and put the phone in USB mass storage.
    8. Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
    9. Put the phone in PC mode
    10. Open a command prompt, and do the following:

    Code:
    adb shell
    su
    stop
    mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
    cp /sdcard/done_app/* /system/app/
    cp /sdcard/done_frame/* /system/framework/
    rm /system/app/*.odex
    rm /system/framework/*.odex
    mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
    reboot

    Your phone should now be deodexed!

    You may notice an increase in speed, and you now have the ability to edit certain files with greater effects. (i.e. services.jar)

    Many thanks to all involved to make this possible.http://media.xda-developers.com/images/smilies/smile.gif

    I wanted to say I used this on the fascinate gingerbread leak.
    Here is what I had to change to get it to work properly.

    step 5 does not apply to (or at least not on the leak).

    In adb shell I had to change
    Code:
    mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
    to
    mount -t rfs -o remount,rw /dev/block/stl9 /system

    Also I had a problem of
    cp: write error: No space left on device

    to solve this problem I simply ran the
    Code:
    rm /system/app/*.odex
    rm /system/framework/*.odex
    before the
    Code:
    cp /sdcard/done_app/* /system/app/
    cp /sdcard/done_frame/* /system/framework/
    and that solved all my problems.

    My first attempt at this and it went great.
    I hope this information will help others.
    1
    NOOB QUESTION : Will deleting all the .odex files from system/app counted as deodexing ?? :angel:

    simple answer. no