deodex'd.... or am I????


Last Updated:

  1. MoFunk

    MoFunk Member This Topic's Starter

    Joined:
    May 12, 2010
    Messages:
    11
    Likes Received:
    0
    I am a noob to android so I hope this all comes out right, but I have a weird question..... how do I tell if I am deodex'd for sure.

    So I am on the Froyo OTA and I rooted my phone (can't find the thread I used for that). I then started with titanium backup, got that bootstrapper and did a full backup and then tried to deodex my phone from this link (xUltimate). I kept getting errors on one of the steps and ran their little utility called Test.exe and it said my phone was already deodexed. So I thought maybe that happened when I rooted the phone. I then went to try install a theme that I liked, but I got an error so I had to recover. So I tried another one that was supposed to just make the top bar dark, had to recover. I then installed this one and it worked thought the text on the bar is not white and in the thread someone else had the same issue and was told that their phone is not deodex'd. So I guess my basic question is how can I tell if I am or not?

    Thanks.
     

    Advertisement
  2. Macaroni86

    Macaroni86 New Member

    Joined:
    Sep 14, 2010
    Messages:
    1
    Likes Received:
    2
    Does xUltimate's test results say "Odex: Pass" and "Deodex: Pass"?

    If you pass both of those then you have a mix of odex files still and are not completely deodexed. I had that happen to me also, I just ran xUltimate again and it worked correctly. Until you get "Odex: Failed" you are not completely deodexed.
     
    luca992 and MoFunk like this.
  3. MoFunk

    MoFunk Member This Topic's Starter

    Joined:
    May 12, 2010
    Messages:
    11
    Likes Received:
    0
    Looks like I do have both. Thank you. I am going to try this again.
     
  4. xliderider

    xliderider Well-Known Member

    Joined:
    Jan 28, 2010
    Messages:
    1,232
    Likes Received:
    192
    What version of xUltimate did you use? I used 2.2 and the process went well with no errors the first time through. I started with OTA 2.2 as well.
     
  5. MoFunk

    MoFunk Member This Topic's Starter

    Joined:
    May 12, 2010
    Messages:
    11
    Likes Received:
    0
    So I used a different machine last night and repeated all the steps and I am fully deodexed!

    I am using version 2.2....

    Thanks all!
     
  6. ECFfighter7232

    ECFfighter7232 Well-Known Member

    Joined:
    Jul 21, 2010
    Messages:
    1,493
    Likes Received:
    336
    use root explorer and look in system/app folder if you see files ending in .odex then your still odexed, if all you see is .apk files, then you have been deodexed and can apply themes
     
  7. Patmos

    Patmos Active Member

    Joined:
    Nov 23, 2009
    Messages:
    36
    Likes Received:
    0
    I am trying to Deodex my X and this is what I get on the test. I have the new OTA update to the new .340 version. After I press enter at the end of this I get deodex = failed and redex = skip. I have done this about 5 times with the same result. What could be wrong? One thing, I never get the guava.odex file it says to delete. I have looked everywhere and it isn't there. Also I have CW recovery installed as well. The process also goes through without a single error. Which is weird maybe?
    -Windows x86-
    *************************
    * adb = PASS! *
    * *
    * odex = PASS! *
    * *
    * zip = PASS! *
    * *
    * busybox = PASS! *
    * *
    * java = PASS! *
    * *
    * temp = PASS! *
    * *
    * deodex = *
    * *
    * redex = *
    *************************


    Error occured while loading boot class path files. Aborting.
    org.jf.dexlib.Util.ExceptionWithContext: Cannot locate boot class path file core
    .odex
    at org.jf.dexlib.Code.Analysis.ClassPath.loadBootClassPath(ClassPath.jav
    a:237)
    at org.jf.dexlib.Code.Analysis.ClassPath.initClassPath(ClassPath.java:14
    5)
    at org.jf.dexlib.Code.Analysis.ClassPath.InitializeClassPathFromOdex(Cla
    ssPath.java:110)
    at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:96)
    at org.jf.baksmali.main.main(main.java:278)

    Press any key to continue . . .
     

Share This Page

Loading...