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

Root Deodex for 2.2 ota?

I just used this method earlier to deodex my DX while on the 2.3.15 OTA update. [HOW-TO] Manually deodex your phone.

I then used this to do the black notification bar modification. Froyo 2.2 Dark Gray StatusBar - xda-developers

Everything went great for me. It took a little bit of patience and careful treading, but everything appears to be in order. I think it takes just a bit of tinkering to make sure that all the text and icons are white, that were previously black. Most of it changes right off the bat though.

EDIT: For example, the, "spinning arrows," icon in my notification bar and dropdown for, "Connection Detected," appears to still be black. I think I still have to do some manual editing to change something here or there. I also read, in the thread linked above, that when downloading something like an .apk via the web browser, the text for the name/description of the item is supposedly still black and needs to be changed in an .xml or .apk file. If I figure out anything new or whatever, I'll try to remember to post about it here.
 
Upvote 0
I followed the link to get xultimate v2.2.2, but avg is going nuts saying the executables all have trojans in them.

Is there a link for a clean version anywhere?
There is such a thing as a false detection. If countless others are using the exact same files from the same location, I wouldn't worry much about what your AV is spitting out.
 
Upvote 0
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. 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

When entering the code do I enter each line then press enter, or all of it at once?
 
Upvote 0
When entering the code do I enter each line then press enter, or all of it at once?
The quote somehow messes up the formatting. Those commands are supposed to be on separate lines.

It should look like this.
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
Enter each command one at a time.
 
  • Like
Reactions: eraursls1984
Upvote 0
Plug the device into your computer and make sure that your USB mode is set to, "PC Mode." Bring up the command prompt and make sure you're current path is where your Android SDK's, "tools," folder is located. It should be something like, "C:\android\tools\" Now type, "adb devices" (without quotes). It should show your device as being connected. If not, you may need to reinstall drivers. If it does list your device, then go ahead and continue trying to access the shell.
 
Upvote 0
Plug the device into your computer and make sure that your USB mode is set to, "PC Mode." Bring up the command prompt and make sure you're current path is where your Android SDK's, "tools," folder is located. It should be something like, "C:\android\tools\" Now type, "adb devices" (without quotes). It should show your device as being connected. If not, you may need to reinstall drivers. If it does list your device, then go ahead and continue trying to access the shell.

I tried that in pc mode and charge only mode. when i type stop i get permission denied. I thought after you type adb shell it changes the $ to # and it never does that.
 
Upvote 0
The command, "adb shell," is a command that throws you into what it suggests, the shell prompt. It's essentially the terminal for the android operating system on your phone. The prompt marker will only change to a pound sign if you're rooted. If you do not have root access, then it will stay a dollar sign. If you see a dollar sign, try issuing the command, "su" (without punctuation). If it gives you the message, "Permission denied," then you do not have root.

Read what I said again please. You make it seem as though you're skipping the process of making sure that you're command prompt's current directory is set correctly. You need to be in the SDK's tools folder before trying to access the shell or issue any of the above commands.

EDIT: Look.
Code:
C:\Documents and Settings\Owner>adb devices
'adb' is not recognized as an internal or external command,
operable program or batch file.

C:\Documents and Settings\Owner>cd desktop/android/tools

C:\Documents and Settings\Owner\Desktop\android\tools>adb devices
List of devices attached
015D778F17014015        device


C:\Documents and Settings\Owner\Desktop\android\tools>adb shell
# exit
exit

C:\Documents and Settings\Owner\Desktop\android\tools>
 
Upvote 0
Does anyone know how I can make sure this worked? I put in step
rm /system/framework/*.odex
and it spit back the # symbol when it seemed to be done but when I then put in
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
it spit the cmd back and told me something about the system or device being busy. was the same way for over 10 minutes and the phone was unresponsive to any touch or button push. I exited out and unplugged then had to pull the battery, everything rebooted fine (took a while on the eye though) and I just want to make sure everything worked right before i try to apply a theme and screw everything up.
 
Upvote 0
Does anyone know how I can make sure this worked? I put in step and it spit back the # symbol when it seemed to be done but when I then put in it spit the cmd back and told me something about the system or device being busy. was the same way for over 10 minutes and the phone was unresponsive to any touch or button push. I exited out and unplugged then had to pull the battery, everything rebooted fine (took a while on the eye though) and I just want to make sure everything worked right before i try to apply a theme and screw everything up.


Mine did the same thing, couldn't remount as RO.
I sent the reboot command and everything has been fine since.
I did notice that things seem to be much snappier.

I have since installed Tranquility 2.3.5rc and a black swype keyboard and I'm much happier than with the stock 2.2OTA.
Just need to find a status bar I like and I'll be done messing with the gui.

Edit:
Now running a 2.1 themed swype.
 
Upvote 0
Does anyone know how I can make sure this worked? I put in step and it spit back the # symbol when it seemed to be done but when I then put in it spit the cmd back and told me something about the system or device being busy. was the same way for over 10 minutes and the phone was unresponsive to any touch or button push. I exited out and unplugged then had to pull the battery, everything rebooted fine (took a while on the eye though) and I just want to make sure everything worked right before i try to apply a theme and screw everything up.
I had all of this happen to me the first go around as well.

When you issue the, "stop," command up above, it literally stops your phone. Your phone freezes. It's normal and it's what the command does. When you saw your phone frozen, it was supposed to be that way.

When you get the message about the resource/system being busy, just go ahead and reboot as though nothing happened. I ended up going back, after my phone booted back up, and reissued all of the shell commands. It can't hurt to do so, and it successfully remounted the second time around. The second time I did the commands, I was essentially confirming that I successfully deodexed the first time. When I typed the rm commands, the prompt told me that it couldn't find any files. That's good. That means that the first time I issued the commands, they were correctly removed. At this point, the second mounting command went through without a hitch and I rebooted with a fully deodexed phone.
 
  • Like
Reactions: eraursls1984
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones