Droid 2 Root for DX OTA 2.2...

[shadowx582]

ok so I've rooted the 2.2 update, got bootstrap loaded and running... but I can't get the phone deodoxed... I get all the way to step 4 but then I get this error when it's deodox'n(sp?) core.odex
UNEXPECTED TOP-LEVEL ERROR:
java.lang.OutOfMemoryError: Java heap space


kinda sucks too cus I'm processing 30/40 in step 4 before it stops. I've tried restarting the whole process several times. Even when I rooted the leaked 2.2 I had the same problem at the exact same process. SDF'd back to 2.1, let the ota update work then rooted and tried to deoxed again... anyone have any idea what could be doing this?

 

[ironman77]

Alright Soupy,

First off let me say thanks bro for laying these steps out for me it makes it so much easier!! Now on to where I think I'm stuck. I have done everything from step 1 - Step 14 however there are some problems for me between step 10 - 14.

Step 10 - I located the system32 folder and placed adb exe. and AdbWinApi.dll ( then I went into cmd prompt after C\users\Name> adb devices " pop up error comes up and says program can't start because ADbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem.
- So I attempted to reinstall the AdbWinApi.dll in system32 folder ( Same error keeps coming up.

Step 11: - checked off no problem ( quick question should it be in pc mode or usb on DX)
Step 12: after getting into Device Manager I only saw Android ADB Interface listed at top of Device manager tab under Android Phone > I don't see ADB Interface drop or 'Mot Composite ADB Interface
Step 13: not opening properly still " pop up reads same as listed in Step 10

So I feel like I'm really close but I've got to get these errors figured out and see the proper drivers listed in Device Manager. Please advise what to do...

Thanks,

 

[ironman77]

Alright Ironman, lets get you set up on ADB step by step.

1. Go to Android Developers website, and download the SDK setup from the link HERE.
2. Unzip the SDK files into the root of your C:\. (So C:\android-sdk-windows is mine)
3. Run SDK Manager, to do this you MUST have Java installed (if you don't Google it).
4. It'll pop up a cmd prompt window, then pop up another window asking you which packages to install. Press 'Accept All' on the right under the list of available installs and let it install.
5. After it is all installed, open up your Start Menu, and right click on Computer. Choose properties.
6. On the left, click Advanced system settings. On the bottom right, click Environmental Variables.
7. Under System variables, click new. Variable name is adb, Variable value is C:\android-sdk-windows\tools
8. Click Ok to exit out of that, and Ok again. And Ok again.
9. Now, go over to your android-sdk-windows folder. Open up tools.
10. Copy adb.exe (first thing listed) and AdbWinApi.dll to your C:\Windows\System32 folder. Now you can run adb from any directory (it's the easy way so when you open cmd prompt you can just press adb devices).
11. Plug in your DX, make sure USB debugging is enabled (this is toggled by going to Settings>Applications>Development).
12. Now lets make sure you have the right ADB drivers installed on your system. Go to Control Panel, click on Device Manager, and you should see an ADB Interface drop down at the top of the devices. If it reads 'Mot Composite ADB Interface' that is the right driver.
13. Lets confirm all this worked! Open Start menu, type 'cmd' in the 'Search programs and files'. Should read C:\Users\(your name or whatever).
14. Type in adb devices (it'll start up daemon), and it should show a list of devices.

Bam! At this point, follow the directions for root, and you can root through ADB. I'm a firm believer of hands on methods for doing stuff...so I prefer doing ADB instead of one-click. Hope this helps!

Ok NEW INFO!

I think I may have figured out most of getting Step 12 checked off my list. Not sure if it should matter but it matters what will show in Device manager for what mode I put my DX in.


DX mode changes in Device Manager
- PC Mode - < Device Manager > Android USB Devices { Mot Composite ADB Interface}
- Windows Media Sync < Same as PC Mode > ( Likley not used in development)
- USB Mass Storage < Device Manager > Android Phone { Android ADB Interface }

Again I'm not sure which mode I should use but it looks like drivers are installed correctly ??

Still trouble shooting to figure out Step 10 and Step 13/14




Alright Soupy,

First off let me say thanks bro for laying these steps out for me it makes it so much easier!! Now on to where I think I'm stuck. I have done everything from step 1 - Step 14 however there are some problems for me between step 10 - 14.

Step 10 - I located the system32 folder and placed adb exe. and AdbWinApi.dll ( then I went into cmd prompt after C\users\Name> adb devices " pop up error comes up and says program can't start because ADbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem.
- So I attempted to reinstall the AdbWinApi.dll in system32 folder ( Same error keeps coming up.

Step 11: - checked off no problem ( quick question should it be in pc mode or usb on DX)
Step 12: after getting into Device Manager I only saw Android ADB Interface listed at top of Device manager tab under Android Phone > I don't see ADB Interface drop or 'Mot Composite ADB Interface
Step 13: not opening properly still " pop up reads same as listed in Step 10

So I feel like I'm really close but I've got to get these errors figured out and see the proper drivers listed in Device Manager. Please advise what to do...

Thanks,

 

[Soupy McD]

Alright so challer figured this out one out...the difference was between 64-bit and 32-bit (I was running 32-bit previously, just installed 64). You need to copy the .dll into the SysWoW64 folder, not system32. Once that happens, you should be able to run from any directory.

 

[Soupy McD]

ok so I've rooted the 2.2 update, got bootstrap loaded and running... but I can't get the phone deodoxed... I get all the way to step 4 but then I get this error when it's deodox'n(sp?) core.odex
UNEXPECTED TOP-LEVEL ERROR:
java.lang.OutOfMemoryError: Java heap space


kinda sucks too cus I'm processing 30/40 in step 4 before it stops. I've tried restarting the whole process several times. Even when I rooted the leaked 2.2 I had the same problem at the exact same process. SDF'd back to 2.1, let the ota update work then rooted and tried to deoxed again... anyone have any idea what could be doing this?

I found out that it's actually an issue within java's programming, the OutOfMemoryError is thrown out by Java when the program is creating too many objects that its set heap space (transfer memory I believe) can handle (which I guess is 64mb stock?). I saw you solved it on the xUltimate thread so hell yeah!

 

[ironman77]

Alright so challer figured this out one out...the difference was between 64-bit and 32-bit (I was running 32-bit previously, just installed 64). You need to copy the .dll into the SysWoW64 folder, not system32. Once that happens, you should be able to run from any directory.

That worked!!

So what mode should I have the DX as well as checked usb debugging

- PC Mode or USB Mass Storage

 

[Soupy McD]

Pc mode for rooting!

 

[mjsplicer78]

I have sdk on cpu. adb recognizes my DX i have the debugging notification, but whenever I try to push superuser i get permission denied. Where did i go wrong

 

[Lifeiskilingme79]

I have sdk on cpu. adb recognizes my DX i have the debugging notification, but whenever I try to push superuser i get permission denied. Where did i go wrong

I had the same thing happen to me. I fixed it by switching out of PC Mode and using Charge Only. If that doesn't work, then do a battery pull and try again. Based on what I could tell, that error happens when your SD card is mounted and in use.

 

[mjsplicer78]

Worked thx

 

[mjsplicer78]

Out of curiosity how long is the wait to get past #12 when it gets you back to C:\droid2root.
Last line I have says adb connection will be reset. restart adb server on desktop and re-login, so am I supposed to do anything here?

 

[Lifeiskilingme79]

Out of curiosity how long is the wait to get past #12 when it gets you back to C:\droid2root.
Last line I have says adb connection will be reset. restart adb server on desktop and re-login, so am I supposed to do anything here?

Mine took about 30 seconds but it could be shorter/longer based on several things. Shouldn't be too long though.

 

[mjsplicer78]

Out of curiosity how long is the wait to get past #12 when it gets you back to C:\droid2root.
Last line I have says adb connection will be reset. restart adb server on desktop and re-login, so am I supposed to do anything here?

Mine took about 30 seconds but it could be shorter/longer based on several things. Shouldn't be too long though.

I've been waiting 15 minutes, should i cancel and do a battery pull and start over?

 

[Lifeiskilingme79]

Out of curiosity how long is the wait to get past #12 when it gets you back to C:\droid2root.
Last line I have says adb connection will be reset. restart adb server on desktop and re-login, so am I supposed to do anything here?

Mine took about 30 seconds but it could be shorter/longer based on several things. Shouldn't be too long though.

I've been waiting 15 minutes, should i cancel and do a battery pull and start over?

Yea, 15 minutes is excessive. I had problems here (not the same one as you) and I did a pull and my phone was slow and near unresponsive until it was completely loaded up. If you do a restart, don't panic like I did. Remember when you restart the root process, you don't have to do it all over again. Restart with the adb shell and you should be good to go forward. Worked for me at that point at least.

 

[mjsplicer78]

Mine took about 30 seconds but it could be shorter/longer based on several things. Shouldn't be too long though.

I've been waiting 15 minutes, should i cancel and do a battery pull and start over?

Yea, 15 minutes is excessive. I had problems here (not the same one as you) and I did a pull and my phone was slow and near unresponsive until it was completely loaded up. If you do a restart, don't panic like I did. Remember when you restart the root process, you don't have to do it all over again. Restart with the adb shell and you should be good to go forward. Worked for me at that point at least.

Alright, appreciate it, have to pick this up later i guess