try updating Java on ur comp..... I had the same error... & after I updated my Java software it worked... Step 4 on #30 will take a bit longer than others... n #34 too... (I'm referring to Run 4 (1-42)).... u won't need to run 1-3 again.. but make sure when running 4 again u type 'Y' b/c u will need to delete files so they can reinstall again........ I'm no pro at this.. but this is what I did.. & it worked....
09-27-2010 07:05 PM
Droid X Forums
Try using the latest xUltimate too. I believe it's 2.2.2. I tried manually deodexing a while back and had nothing but problems. Tried again about a week ago with the new software and not one single issue.
oh yeah... that would prob work... b/c that's the one i used... go here
[Release] xUltimate - Droid Forum - Verizon Droid & the Motorola Droid Forum
then go down to Main xUltimate 2.2.2... that should do it...
I was using xUltimate 2.2.2. I updated Java, and that appears to have been the issue. Made it through all the xUltimate steps. Doing the commands now...
Sweet! Worked like a charm. I'm now deodexed.
When I start step 4 and adb shell I get... What should I do?
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
* daemon not running. starting it now on port 5037 *
CreateProcess failure, error 2
* failed to start daemon *
error: cannot connect to daemon
wll after just running the xultimate steps it passes the test and i am able to download any mod from rom manager
Great to hear!!!! I figured that was probably it...
Originally Posted by SoundZombie
Are you in Charge Only mode? what mode are you in?
Originally Posted by challer2000
You also need to make sure that you are running the command prompt in the correct location.... where the adb files are located... do you have the android-sdk_r07-windows installed on your computer?
Originally Posted by jbreezy