yashsingh1/xdaforums huggingface dataset:
[Droid X Themes and Apps] zsg1313:
haha you are going through the same **** i did yesterday.

What I had to do way to reboot to koush recovery and choose to mount the system and also the sdcard. Then run your adw commands.

there is a thread on this somewhere with better instructions but im not sure where i saw it yesterday
[Droid X Themes and Apps] willy1234x1:
Link to Koush's recovery? The only one I can find on Google is 404'd
[Droid X Themes and Apps] zsg1313:
Droid X recovery bootstrap in the Market or the Devs page is clockworkmod.com
[Droid X Themes and Apps] Macaroni86:
I think an all pass means you have a mix of odex and deodexed files. Someone correct me if I'm wrong but I read on another site the results you want are:

-adb pull- **PASS**

-odex- **FAIL**

-7z- **PASS**

-busybox- **PASS**

-java- **PASS**

-temp- **PASS**

If you fail the odex test that means you don't have any odex files left. Took me a half dozen tries but I finally got it. You can always list your /system/framework/ and see if there are any odex files left to double check.
[Droid X Themes and Apps] jzmax22:
when i type in

11. cp /sdcard/done_frame/* /system/framework/

my phone resets and then i try to run adb shell w/ pc mode and i get

no device found, any ideas how to fix this, i also get a bunch of fc's , so i wind up doing a restore to get my phone back. what am i doing wrong?

i see others are having these same problems, but no resolves
[Droid X Themes and Apps] dr154:
Revised Command-Line

if ur doing the commands right, ur phone shouldn't restart after u input that command since you used the stop command, which makes the phone unusable until u reboot.

if it says no device found, restart adb services by typing "adb start-server".

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
[Droid X Themes and Apps] GoldenCyn:
Didn't work for me, tried all mothods. I just installed the ota, then rooted, then installed the 2.3.15 deodexed leak. Ding.
[Droid X Themes and Apps] ECS2010:
Im not an expert or anything but you can also deodex your phone manually using root explorer.

All I did was press r/w, multi-select, and move the odexed files from system/app and system/framework to my sd card. Then moved again to my computer.

Sorry if this has been mentioned before but I didn't see it mentioned anywhere else. I did this a few weeks ago and am successfully running the galaxy s theme 1.5.2 with no ill effects. Couldn't get Ultimate X to work :(
[Droid X Themes and Apps] imajinaxn:
I'm trying to DL the xultimate to deodex but i keep getting Trojan warnings. Anyone have a clean file?
[Droid X Themes and Apps] RCars2:
Thanks for the tip on that one. I was banging my head against a wall trying to get this to work.

If anyone else needs to do this method do the following:

-Launch koush's loader and select "Reboot Recovery"

-Once at the menu use the up and down volume keys to highlight "mounts and storage", press the camera key to select.

-Using the same keys highlight "mount /sdcard" and select it.

-Now you can run your adb commmands

-Once you get to reboot you will see the command come back returned.....this is fine

-Go to your phone and press the power key once to go back a screen

-Press the camera key to select "reboot system now"

At this point you should be good to go and the phone will reboot. Dont freak out if it takes forever to reboot. Mine did and took about 3-4 minutes longer than normal to boot and then once loaded it was a little slow for the first minute or so. After that all clean sailing.

Hope that helps anyone else out if they get stuck on this.
[Droid X Themes and Apps] DroidXBeast:
I didn't ready every post in this thread, so I apologize if it has been mentioned.

The instructions note to put the phone in mass storage mode. The phone needs to be switched back to PC mode before performing the copy commands in su, otherwise you'll get a No such file or directory error.
[Droid X Themes and Apps] HellRayzer:
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
[Droid X Themes and Apps] catmanzrt:
Not working?

I ran step 1 then step 2. press any key to continue but the menu doesn't return so I can select step 3. Did I do something wrong? How do I select step 3 without the menu? I have a blank screen with a flashing underscore.

EDIT: I exited out and reran test and got a Pass on all 8 items. Does this mean it's completed or do I have more steps to do. I ran version 2.2.2 of xU
[Droid X Themes and Apps] zsg1313:
if test passes then run main.

And best way to test is make a backup then install a theme!
[Droid X Themes and Apps] joebob296:
When I get to option 3 it just says An error occurred please fix it. When i ran the test I passed all of them. Anybody have any ideas on what i did wrong?
[Droid X Themes and Apps] ThatOneDude05:
When I enter in adb shell it is supposed to be a # or a $ sign.... I remember when I rooted it was supposed to be changed to a # sign....after i type in stop it says permission denied and then nothing else works.
[Droid X Themes and Apps] catalystsupreme2:
Can someone please answer this
[Droid X Themes and Apps] crashdau:
I see you indicated you used xUltimate 2.2.1. I suggest downloading the newest version 2.2.2.

i SBF'd from 2.2 Leaked to 2.1 last night, then updated to Official OTA 2.2. Then rooted using DOROOT.bat and manually deodexed with xUltimate 2.2.2 and everything went fine. Only issues I ran into were getting adb to see my device during the rooting process. Once I figured out the right settings for me I had no problems.
[Droid X Themes and Apps] mortodestructo:
I had no problems doing this on the OTA 2.2 update. Afterwards, though, when I replace the stock services.jar with teenfaces' services.jar (the one with the white text), the X freezes upon startup. I get all the way through the boot animation, but once the desktop shows, it shows no service and completely locks up. It worked on the leaked 2.2. Is anyone else having this problem?
[Droid X Themes and Apps] catmanzrt:
I finally got mine to work but I did it a little different. I did the first part in USB storage mode and ran the shell commands in PC mode and it solved my problems, don't ask me why but it worked for me.
[Droid X Themes and Apps] dr154:
when you run adb shell is suppose to be $ and then you run su for root access it changes to # .

ur suppose to do the shell command in pc mode... or else the it will say done_app and done_frame folders don't exist, because they are still mounted in storage mode.
[Droid X Themes and Apps] krze:
Can I delete the folders I dropped onto my SDcard or do they need to be there forever? (done_app, done_frame folders)

Thanks.
[Droid X Themes and Apps] catmanzrt:
I was following these instructions and step 7 had me put it in USB mass storagr., Maybe I misunderstood.

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:
[Droid X Themes and Apps] sheelanagig:
Social networking/Friend feed and news widget not working

After deodexing, has anybody else also experienced their moto social networking widget not working? It isn't pulling updates at all... just displays "get social updates touch here.". When I touch it, it takes me to the setup accounts screen which shows my facebook acct is already set up. have tried deleting the account and re-adding, but no luck. The news widget has the same prob even though I selected the news channels to subscribe to. Can deal without that one, but would like to get the blur social netwk widget back.

I can't just push the original FriendFeed.apk and FriendFeed.odex back to /system/app without the reverting everything else as well, right?

Thanks!

EDIT: Nevermind...I did a restore back to stock 2.2 and then used 928Droid's zip file to deodex. The blur widets still work. I must have made a mistake somewhere during my manual attempt.
[Droid X Themes and Apps] dr154:
Step 7 is so you can do step 8, before step 9, at the end of step 8 it should read, put phone back into pc mode. Then proceed to step 9.
[Droid X Themes and Apps] BoxyBox:
Every time I get to SyncML.odex in Step 3 (whatever the hell that is), I get a "the system cannot find the file specified" error and the whole process aborts. Should I restore to a recent backup with Koush's bootstrapper and try to remove the file beforehand, or is it necessary to flash a stock .sbf and restore to factory? I'd like to undo what I may have done to my phone for now, but I'd rather not start from scratch.

EDIT: Restored backup and moved the SyncML.apk and .odex to sdcard. Process didn't abort and every step ran smoothly. Looking in Root Explorer now, I can see that the files were copied to /system successfully due to their modified date. The only command that didn't work was mounting /system as RO due to a "busy device", but I'm pretty sure a reboot accomplishes this step anyway.

However, when I run the Test.exe file, I get "FAIL!" for odex, and it skips deodex and redex. Any ideas on what I did wrong? I was sure I had done everything correctly and I never got any errors along the way.

EDIT2: Nevermind; after reading a few more posts I see that you WANT to fail odex, since you shouldn't have any more .odex files (makes sense). In order to test further, I made another backup and installed a theme... and the clock is now white and readable! This is what I wanted to fix :)

In addition, those who say this doesn't work on a Droid 2 running 2.2 appear to be incorrect, as that's what I'm using.
[Droid X Themes and Apps] chris6551:
cant find files

Im sure Im blind but I cant find any of the files in the zip that we are supposed to move or delet in the instructions, can someone tell where I find these files. also I did step four without deleting the guava.odex file even though I cant find it. should I just start over. any help would be very grateful.

:confused:
[Droid X Themes and Apps] sheelanagig:
In the directory/folder that you unzipped xUltimate to and where the "Main.exe" executable is that you are running (most likely called xUltimate-v2.2.2), it should have created the following sub-directories:

(after successfully pulled the original system files by selecting option 1 & 2 of "main.exe")

origi_app

origi_frame

(after deodex was successfully run in option 3 & 4 of "main.exe")

done_app

done_frame
[Droid X Themes and Apps] krze:
bump

10char
[Droid X Themes and Apps] dr154:
yes, once you completed the deodex process, yes u can delete those two folders.
[Droid X Themes and Apps] Vasichko:
Ok so this deodox will pull my apk, and odex files and modify them. If i went thru and renamed all the bloatware so they are running this will cause an issue right?

I should probably run the deodex before I mess with anything in rom manager correct?
[Droid X Themes and Apps] mezdup:
worked great for me. before going through with it i put my bloatware apps back in their place and rebooted. re-removed them after deodexing and applyling a theme. thanks!
[Droid X Themes and Apps] lovalova24:
cmd prompt

:confused: i am stuck on the command prompt when i type in adb shell it says that adb is not a as an internal or external command blah blah blah i tried it with the phone in all three modes except for media sync mode please help :confused:
[Droid X Themes and Apps] mezdup:
you have to "cd" to the tools folder
[Droid X Themes and Apps] lovalova24:
do u kno the actually steps
[Droid X Themes and Apps] thepolishguy:
Tried it. Got stuck at #4. It got to 30 core.jar and then fatal error. bummer.
[Droid X Themes and Apps] aholeinthewor1d:
Run steps 1-3 and then switch the connection mode on ur phone to media sync before u start step 4
[Droid X Themes and Apps] thepolishguy:
Thanks- I will try next time. I just borrowed the two folders I needed from a friend on XDA who was running 2.2 ota and deodexed that way.
[Droid X Themes and Apps] Muchoburrito:
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. :)
[Droid X Themes and Apps] Muchoburrito:
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
[Droid X Themes and Apps] tripp7453:
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?
[Droid X Themes and Apps] hka148:
I got "cp: write error: No space left on device" at final steps. What can I do:(
[Droid X Themes and Apps] Sleuth255:
hmm.. not sure why your filesystem reverted to ro mode especially since the cp commands worked.
[Droid X Themes and Apps] ppazz1101:
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.
[Droid X Themes and Apps] ghostlypickel:
Either you don't have enough space on your device, or maybe you don't have /system mounted?
[Droid X Themes and Apps] Sleuth255:
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.
[Droid X Themes and Apps] mrm0rbid99:
I think you might be mistaken, this worked perfectly for me on D2
[Droid X Themes and Apps] Adilaaa:
if still unanswered, no, because the "stop" command freezes your phone so it does not crash while the files get replaced
[Droid X Themes and Apps] happenstance314:
I am getting an error that the .odex files are read-only.

How do I work around this?
[Droid X Themes and Apps] stevemoffler:
cant run adb commands what to do??
[Droid X Themes and Apps] lunchbox2:
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.
[Droid X Themes and Apps] BuzzFuzz:
Why Error:
[Droid X Themes and Apps] Ronbo85:
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
[Droid X Themes and Apps] Ronbo85:
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!
[Droid X Themes and Apps] yzak47:
do you mean that i can dismiss this step after reboot the device?

i got the same situation as him,

"DEVICES OR resource busy"

then i typed reboot, the phone could successfully rebooted.

is that ok?
[Droid X Themes and Apps] r6zer:
Can I use a terminal on the phone to copy all the deodexed files or do I have to do it through my pc?
[Droid X Themes and Apps] allfaccino:
First off all thx for help!!

Cant do step 3, error msg, balck screen, I am with 2.2 rooted with speedmod 13E GT9000B, I made test and java failed, do you think this is the problem?:cool:
[Droid X Themes and Apps] Wassimz:
Lack of experience

That's what I did in the second part :

F:\android\platform-tools>adb shell

$ su

su

# stop

stop

# 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/app/*.odex

rm /system/app/*.odex

rm /system/framework/*.odex

rm /system/framework/*.odex

# cp: write error: No space left on device

cp: write error: No space left on device

cp: write error: No space left on device

cp: write error: No space left on device

cp: write error: No space left on device

cp: write error: No space left on device

cp: write error: No space left on device

cp: write error: No space left on device

cp: write error: No space left on device

cp: write error: No space left on device

# # # mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system

mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system

# reboot

reboot

?
[Droid X Themes and Apps] kirpeace:
can the tutorial be used for motorola defy
[Droid X Themes and Apps] modizaki:
Is this method works with the Milestone 2?
[Droid X Themes and Apps] cynnar:
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

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

rm /system/app/*.odex
rm /system/framework/*.odex

before the

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.
[Droid X Themes and Apps] :
Thank you so much for this tut, I just deodexed my XXJVP 2.3.4 Semaphore on the fly :)

(note, I've deleted lots of apks+odexs before in /system/app - just the crap I do not need)

Went down from about 80Megs to about 40Megs, sweet :)

PS: had to change "ext3" with "ext4" :)