• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [HOW-TO] Manually deodex your phone.

I did the OP's method and went through the whole thing. Had a few errors but searched my way around and got it to go with no errors, finally.

So now I THINK I am deodexed... How in the world can I tell if I am Deodexed?

There's gotta be a way - its too important. People need to know for sure before they start doing custom stuff!
 
chenry888 said:
So now I THINK I am deodexed... How in the world can I tell if I am Deodexed?

There's gotta be a way - its too important. People need to know for sure before they start doing custom stuff!
Click to expand...
check in "/system/app" look through the whole list, if you see one .odex file your only partially deodexed. Try the process again if that is the case
 
eraursls1984 said:
check in "/system/app" look through the whole list, if you see one .odex file your only partially deodexed. Try the process again if that is the case
Click to expand...

I just looked through the list and all I see are .apk files... no Odex.. so Nice!
Thanks for the tip!

(I PM'ed you because I now have an off-topic question... hope you dont mind :))
 
I am stuck on option 4, 30 out of 42. It says unexpected top level error, help me please?

Edit: Redid everything now on out of 43, maybe I did something wrong?

Edit: Still not working, it seems to be Core.odex thats not working
 
1324356565 said:
I am stuck on option 4, 30 out of 42. It says unexpected top level error, help me please?

Edit: Redid everything now on out of 43, maybe I did something wrong?

Edit: Still not working, it seems to be Core.odex thats not working
Click to expand...

You did delete the guava.odex file right?
 
The cmd prompt doesn't work for me... is that part needed? When I open a cmd prompt and type in adb shell on my computer, it gives me: 'adb' is not recognized as an internal or external command, operable program or batch file.

I'm stuck.

EDIT: I changed the directory, and now when I type adb shell, I get permission denied.
 
bump. Anyone? I don't even know if I can use my phone without completing that last step, so I haven't unplugged it =\ Please help! I can't get the final step, the cmd prompt working. Thanks...

EDIT: nevermind, rebooting now. I restarted computer/phone and somehow it worked. Now it's rebooting and taking forever on the red eye.... hope it boots...
 
I am stuck at the cmd part. Can someone help me out here? When I open it up I get the same thing as the last 2 posts above me but they didn't explain how they fixed it.
 
You have to find your android sdk tools folder and add it to your windows path. Then you never have to worry about adb shells again.

If your sdk is installed in C:\android-sdk-windows you need to add C:\android-sdk-windows\tools to your path. Your folder is probably in a different area so you'll have a different path.
 
So, this does work on the OTA .340 update? And when I get to the command prompt adb part, do I just copy and paste that code and run it all at once? Thanks!
 
cmathis said:
So, this does work on the OTA .340 update? And when I get to the command prompt adb part, do I just copy and paste that code and run it all at once? Thanks!
Click to expand...

No. You need to copy and paste each command separately.

Haven't done this on .340 yet. Let us know if it works for you.
 
Since I've been through this process twice and run across similar problems, some reworked instructions are in order.
Thanks to those who came up with these solutions.


What you'll need:
A Windows based machine
xUltimate v2.2
SDK
The lasest version of Java
Patience


1.Turn on USB Debugging on the phone
2. Unzip xUltimate v2.2, and launch "Main.exe"
3. If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
4. Run option 1. After option 1 is done, run option 2.
5. Now these well take a while. Run option 3.
6. 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.
7. Switch the phone to Windows media sync
8. Now run option 4, and wait.
9. Turn off USB Debugging
10. Exit xUltimate, and put the phone in USB mass storage.
11. Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
12. Turn USb debugging back on and Put the phone in PC mode
13. Open a command prompt to C:\android-sdk_r07-windows\android-sdk-windows\tools (or where your ADK tools folder is located), and enter the following:

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
Click to expand...
In all likelihood the phone will freeze and need a battery pull, however after that you should be good to go.
 
OK in order for me to complete this I had to have my phone in charge only mode otherwise it would not recognize the SD card was there. Just thought this might help...

Also, this seems to be taking a long time to boot for the first time after doing this so don't get scared if this happens to you...
 
You must log in or register to reply here.
Back
Top Bottom