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

Root One-Click Root for DX2 2.3.3

I appreciate that. As I mentioned in my post, I do see the usb messages at the top of the phone (notification messages), but I can't interact with them, they seem to be just status messages.

As for the other icons that appear at the top (bluetooth, wifi, usb etc), I have tried many times to touch the screen there but all I can select is whatever appears below that. If my memory serves me right it acknowledges the touch while my finger is on the screen but whatever appears goes away after I remove my finger.

Being a total noob with smartphones perhaps its a simple case of operator error. Some things are rather difficult to select. Is there another place with a menu or setting that this can be changed from? I looked but couldn't find one.

Also, it might be a good idea to mod the instructions to make it clear that if you aren't prompted you must select that icon and change the setting to "Charge only" mode. I didn't have any issues with the usb debug setting. In my post above I describe what that appears to do, on or off.

On the lefthand image you posted, I see icons for usb, a triangle warning and several others I don't recognize appearing above the word Development. Are you saying you can poke the usb icon to the far left and the menu image on the right shows up?

I don't have the phone with me right now so I can't try it.

But thanks once again for hanging in there with me on this.
 
droidmanx2 said:
I appreciate that. As I mentioned in my post, I do see the usb messages at the top of the phone (notification messages), but I can't interact with them, they seem to be just status messages.

As for the other icons that appear at the top (bluetooth, wifi, usb etc), I have tried many times to touch the screen there but all I can select is whatever appears below that. If my memory serves me right it acknowledges the touch while my finger is on the screen but whatever appears goes away after I remove my finger.

Being a total noob with smartphones perhaps its a simple case of operator error. Some things are rather difficult to select. Is there another place with a menu or setting that this can be changed from? I looked but couldn't find one.

Also, it might be a good idea to mod the instructions to make it clear that if you aren't prompted you must select that icon and change the setting to "Charge only" mode. I didn't have any issues with the usb debug setting. In my post above I describe what that appears to do, on or off.

On the lefthand image you posted, I see icons for usb, a triangle warning and several others I don't recognize appearing above the word Development. Are you saying you can poke the usb icon to the far left and the menu image on the right shows up?

I don't have the phone with me right now so I can't try it.

But thanks once again for hanging in there with me on this.
Click to expand...

Your'e welcome. As soon as you plug your phone in you should see the USB symbol and then the words "USB connection" should appear briefly then go away. At that point you should be able to touch the icon and swipe down to bring up the options pictured above. The Wi-Fi, signal strength, battery indicators on the right you can't mess with, those are accessed by going into settings.
 
We can chalk this up to my just being a newbie. It has to do with knowing how to operate a darn thing. No I got the phone in my hands I can see that you need to swipe on the top not just touch it expect the pop up. I haven't tried it just yet but I suspect the charge mode is all I need to change to get the root capability now. I'll post after I try it.

Thank yet again coolpoete for your patience with this noob!
 
We can chalk this up to my just being a newbie. It has to do with knowing how to operate a darn thing. No I got the phone in my hands I can see that you need to swipe on the top not just touch it expect the pop up. I haven't tried it just yet but I suspect the charge mode is all I need to change to get the root capability now. I'll post after I try it.

Thank yet again coolpoete for your patience with this noob!
 
Well, it isnt the charge mode. I now know how to swipe the usb icon to change the connection mode, but that didnt do it. I have s log of that the runme.bat file here on my droid. Ive spent the last 15 minuites trying to copy it to the clipboard but cant get the thing to select ALL of the text. Im going to try to paste in the hole file now instead. No, I can't seem to figure out how to do that either. Bumer. All I will say is that there is a lot of permissions issues. It says can't seem to copy the files because of permissions. It mounts the drive it determines the gingerbread is running, ask if you're running as root, but fails to copy do that the permissions problems. That's the essence of what I see in the file but I know looking at the file would show alot more.
 
Ok, I'm glad you figured out how to change the charge mode. That's a step further. However, you are not telling me what specifically is happening when you try to run the Root program after you plug your phone in. Please watch the YouTube video here:
http://www.youtube.com/watch?v=sKiHoBixicw
It shows exactly what is supposed to happen and how your phone will behave during the process. I have also included the ZegRush root method steps as shown on XDA-Developers. I suggest you read through that thread to make sure you have a good understanding of the entire process, but it works just like the One-Click method. Please respond with where specifically in those steps of the rooting process you get stuck.

1. First download the correct Motorola driver for your Windows system:
a. Windows universal 32-bit Motorola drivers version 5.2.0
 b. Windows universal 64-bit Motorola drivers version 5.2.0
 2. Next download DooMLoRD's ROOT-zergRush: DooMLoRD_v4_ROOT-zergRush-busybox-su.zip (Older version: DooMLoRD_v3_ROOT-zergRush-busybox-su.zip).
3. Install the correct driver and reboot.
4. Once the computer comes back up, extract DooMLoRD_v4_ROOT-zergRush-busybox-su.zip.
5. Make sure USB Debugging is enabled on your device. This can be accessed by hitting the Menu key and navigating to: Settings -> Applications -> Development and making sure there is a check mark in the box next to USB Debugging.
6. Plug the USB cable into your phone and computer.
7. Make sure your phone is in “Charge Only” mode:
a. Drag the Pull Down Menu down
b. Tap “USB Connection”
c. Select “Charge Only” mode
d. Click OK
8. From the new folder you created, launch runme.bat.
9. A command prompt window will open, make sure the phone is plugged into computer via the USB cable and press any key.
10. zergRUSH will reboot your phone once it is done. Watch for errors. If there are none, you will be rooted. If there are errors, try re-running zergRUSH again.
11. Once your phone is rooted, open the market and upgrade Superuser
Click to expand...
 
It never gets stuck, and goes all the way thru, rebooting along the way. On step 2 (modifying local.prop) there are errors trying to write the files: its a read only file system. This happens with each file attempted. BTW, I used zergRush to try this on my Win 7 box. I was thinking the wrong charge mode was allowing the ext. SD card to be mapped to the PC, and that was causing incorrect permissions on the internal files that need to be altered or added to for rooting. Apparently the charge mode wasn't the culprit. It would be great if I could post the console dump from the zergRush script, but it is proving to be too difficult for me on the droid, which is my only way on the internet until monday. Ive got it on the phone, just can't figure out how to send or post it. I did watch the video (thanks!), but in my case on step 2 there are lots of messages, so thats where i departed from the video in terms of what i saw.
 
I see. Well, there's not much else I can tell you. The only other thing I can suggest is to backup what you need and factory reset your phone then try the root method again. There could be something in the system files preventing the phone from being rooted. I've rooted a whole bunch of times experimenting with roms but each time was after a sbf or factory reset.
 
I had a service call and stopped at the library to check my email. Don't have the droid with or the log file however :( Perhaps tomorrow I'll post it here.

You latest advice sounds apropos. I'll check with my friend and see if she cares if it get reset to factory after I pull her photos off. That was easy, but don't know about her contacts.

Have no idea why the exploit didn't have the correct permissions, but it probably has something to do with some change done on her phone since factory, at least that my hope.

I'm also concerned that after resetting to factory it may update to v2.3.5. If it does I'll need to get it back down to v2.3.4, but from what I understand almost every procedure (nandroid backup for sure) seems to require getting root as a starting point. Perhaps I read that wrong for restoring an earlier version.

Well that my update for now. Appreciate your assistance.

PS: FOUND THIS on XDA DEV: http://forum.xda-developers.com/showthread.php?t=1654368
This is almost exactly what my log shows, using the same zergRush tool. Will finish reading page 2 of forum. A bit scared seeing that some say SBF may brick the phone...

That thread gives me great pause. I too have this v2.3.4....621 firmware. I definitely don't want to brick the phone!
 
droidmanx2 said:
Your latest advice sounds apropos. I'll check with my friend and see if she cares if it get reset to factory after I pull her photos off. That was easy, but don't know about her contacts.
Click to expand...
if she has a google account then she could back up her contacts easily there. After the reset the contacts can be restored. It's part of the Google ecosystem. Other than that there are other backup and restore methods in the app market.

I'm also concerned that after resetting to factory it may update to v2.3.5. If it does I'll need to get it back down to v2.3.4, but from what I understand almost every procedure (nandroid backup for sure) seems to require getting root as a starting point. Perhaps I read that wrong for restoring an earlier version.
Click to expand...
After factory resetting the phone if you root within a relatively quick amount of time it won't pick up the update. Plus, it will tell you that it's downloading it and will ask you if you want to install it now so you will have an option to decline.

PS: FOUND THIS on XDA DEV: Droid 2 on 621 refuses to root - xda-developers
This is almost exactly what my log shows, using the same zergRush tool. Will finish reading page 2 of forum. A bit scared seeing that some say SBF may brick the phone...

That thread gives me great pause. I too have this v2.3.4....621 firmware. I definitely don't want to brick the phone!
Click to expand...
Not true at all on the Droid X2. I have performed the SBF quite often and have not run into any problems. Again, you have to follow that process carefully as well. In my experience if you are trying to install ROM's and other things that are not meant for the phone you have you can brick the phone. If you follow the processes you will be just fine.
 
Not true at all on the Droid X2. I have performed the SBF quite often and have not run into any problems. Again, you have to follow that process carefully as well. In my experience if you are trying to install ROM's and other things that are not meant for the phone you have you can brick the phone. If you follow the processes you will be just fine.
Click to expand...
Are you sure? That thread sounded alot like the trouble I'm having, and the poster has clearly rooted phones many times.

But I'm finally online with my Mac with the logfile, so I'm attaching to this post. Take a look and see if you still believe it can be done.

if she has a google account then she could back up her contacts easily there.
Click to expand...
She does, and I looked around to find how to grab / sync / backup the contacts, but couldn't figure it out. Could you possibly offer some clues on that?

I got the backups done now, just not with google.

Thanks again coolpoete!!!
 

Attachments

If you don't believe me read around for yourself, many have done it with much success. Youtube it. It's the best way to put your phone in a out-of-the-box-factory state for wanting to flash a new ROM or return it to the store for insurance rebate. By the way, the thread you posted was on a Droid 2 not a Droid X2, albeit the processes should be similar.

As far as Gmail is concerned, just go on your phone to start-settings-accounts & sync and log in using the gmail account. You can then set the options there to synchronize your contacts to Gmail. That way if you do a reset or SBF, you just log back in to Gmail and your contacts come back. http://support.google.com/mail/bin/topic.py?hl=en&topic=2517643&parent=2451697&ctx=topic

I'm not versed on the log file so I couldn't tell you what's wrong from what's not wrong other than what you already know. I would follow my previous advice on hard resetting the phone.
 
I didn't think there was a distinction. Thanks for clarifying that for me.

According to wikipedia, the droid x2 is the 2nd generation of droid. So is a "droid 2" a newer device than an x2?

I believe advice you gave is sound and I'll follow it once I get her OK to reset the phone.

You're probably right as to there being some app or system change interfering with the root process. Best to just start from a factory fress stateand try to root from that.
 
Hey there coolpoete.

I had to wait for my friends account to expire on June 26th before I wiped the Droid X2 she gave me. I went into the settings menu and selected the "reset to factory settings" option. Now I have a brand spanking, newly initialized Droid X2 bought in Feb 2011.

However when I try to flash it with SBF 2.3.4 using the 32 bit Moto drivers 5.1.0 AND 5.2.0 (using RSD Lite 5.3.1 AND 5.4.4) all I get in every attempt is: "Failed flashing process. Phone[0000]: Phone is not compatible with multi-interface super file. (0x703B)"

I searched for this error and found quite a few hits, but all of them for the Droid X not the Droid X2 which I have. There's no doubt about it I have a Droid X2. But I'm wondering if perhaps I have an earlier model that has firmware from the "X" line.

The instructions I found for SBF on the droidxforums.com ([GUIDE] How to SBF an X2) said that when you press and hold the up volume while turning on the X2 with the power switch you will see a message "Starting RSD protocol support", but I don't. All I see is the Moto logo and it never goes away after waiting up to 5 minutes.

I decided to try to connect the X2 to the computer and attempt a flash anyway. When I connected the phone to the computer RSD recognized the phone and allowed me to start an download. It took a few minutes to do it, but the progress proceeded slowly and reached 100%. Just after it hits 100% I get the failure message above.

Clearly something is different about this Droid X2 than what others are reporting.

This is with version 2.3.4 initialized to factory fresh condition. I can get past the activation screen by following some instructions I found online, so it does behave like some of the X2s out there at least.
 
The instructions I found for SBF on the droidxforums.com ([GUIDE] How to SBF an X2) said that when you press and hold the up volume while turning on the X2 with the power switch you will see a message "Starting RSD protocol support", but I don't. All I see is the Moto logo and it never goes away after waiting up to 5 minutes.
Click to expand...

when booting it you have to press and hold the vol down button untill those words come up. Pull the battery out, put it back in, then hold down the vol down button while powering on. when you see the words come up release the vol down button then continue with the flashing instructions.
 
Glad to see you're still tuned in to this thread Poete.

What I read was the vol UP button (see step 10). But I also tried the vol Down button AND the photo button. I never saw those words ever, no matter what buttons I tried. I waited 5 minutes more than once waiting for those words but never ever saw them.

Also, once any button is pressed and held while powering up the only way to "exit" to try again is to remove the battery. The device doesn't respond to any buttons, power or otherwise.

Have you tried this new "Motofail" exploit yet?
 
droidmanx2 said:
But I also tried the vol Down button AND the photo button.
Click to expand...
The fact that there is a photo button indicates that this is a Droid X1, not X2. Make sure to follow instructions as pertaining to the droid X1 as they are different. If you try to flash a phone using the wrong software you could end up bricking the device! I hope it has not come to that yet though..

Here are some links to some instructional videos on how to perform an SBF to the DX1. Again, any ROMs or other files you may have downloaded from the DX2 forums CAN NOT be used on the DX1.

I don't know about a motofail exploit, I've never heard of it on the DX2.
 
Sounds like Verizon was scamming my friend, as all of the manuals, magazines, even account info told her (& me) this was an X2 device.

I read some reviews on the X2 and puzzled over the "missing" photo button statements, since the phone had one. There wasn't a single piece of info I came across that said anything except that it was an X2.

But given the trouble I've had and the subtleties in the info Verizon provides topped off by me being a newbie in all this I'll bet you're absolutely right about it being a Droid 1.

I found a post on a forum that said to press the down volume and photo buttons while powering up the phone, and after 3 seconds release the buttons and you will be in the bootloader. That is exactly what happens on my phone.

So now that I know it's a Droid 1 (dang they have so many similar names!) perhaps I'll have more luck in rooting it.

None of the rooting methods I've been working with (for the X2) are applicable. Plus, now that I have restored the phone to factory state, it isn't activated nor is there any options for USB debugging etc that come with gingerbread. I suspect (tho not certain) there isn't even an OS on the phone now, it's only a small applet with enough smarts to get activated, after which the OS gets downloaded and installed.

Anyway, I've got much research to do to find appropriate info for the Droid 1.

The motofail exploit is pretty new. Doug Rosenthal says it should work with *any* moto phone. If you google motofail you'll find the info. The exploit was first published in Feb 2012 but just now seems to be getting attention in some of the forums.
 
Ok, first thing is to ensure you get the name correct, it's the Droid x1. I'm not being a smartass but if you have plan to fix it you need to make sure you are referencing the correct info.
Hopefully you can sbf the dx1 back to stock. Take it immediately back to vzw and tell them that it's not the right phone.

Did a bit of reading on the motofail project and it seems like it's a root tool. It's set to work on the Droid 3, 4, Droid Razr, Droid Bionic. Seeing as though we already have our own tested and proven root method for the Droid X2 I don't see this as being beneficial. I would be hesitant to try something that has not been proven to work on the DX2.
 
Woah there Coolpoete,

First, thanks for hanging in there with me, I know newbies can be frustrating.

Second, as you said, I don't have the X2 but rather the X1 (as evidenced by the red camera button). I got this as a freebie from a friend. I don't think vzw will do much for me, and there's no contract / service on the phone anymore.

Third, I appreciate you clearing up the nomenclature. I see lots of different posts and am not sure what the correct name is. I don't think you're being a smart ass. Droid 1, Droid X, Droid X1, dx1 ??? These all refer to the same model correct? And that is the first gen of the Droid right?

You're right the motofail is a (redundant) root method. There's certainly plenty to choose from. It caught my eye because many posts said it should root ANY moto android phone. Perhaps it was just a big ego talking, who knows.

Should we move this conversation to another thread, since this thread is for X2 and I'm dealing with an dx1 problem? I'll post here for now, but thought I'd ask to be polite.

After determining my device is a dx1 I attempted to sbf it to the "605" version of gingerbread, specifically VRZ_MB810_4.5.605_1FF_01.sbf. I also tried this version, which was referenced in the same thread: VRZ_MB810_2.3.34_1FF_01. I stayed away from the "621" release as there were many warning that once that's installed you can't go back down to an earlier version.

I used several methods, starting with RDSLite 5.4.4 on Windows 7 with the 5.2 64 bit drivers off moto's website. It talks to the phone without any problems.

I also used "sbf_flash" on Mac OSX. Also no issues with talking to the phone as you can see below. This is the output from sbf_flash. Perhaps the phone was already at the "621" version and that's why I can't get the Android + exclamation point to show up after flashing & reboot. On every attempt I made (RSDLite or sbf_flash, either 605 or 234 sbf files) the download and checksum verification steps all succeeded and there were no errors reported.

The problem comes after the phone is rebooted. All the instructions I can find for the dx1 say to hold the home button while powering up the phone (after the reboot & pulling the bat). That should result in the Android guy with an exclamation point, but it doesn't in my case.

I had a log file I created with the exact text from the bootloader but I left it on the Windows 7 box so I can't post it now. Here's the best I can do from memory:

Bootloader
30.??
Err: 25,70,70,70,??...

New_??? ...
Service Req'd
Bat OK
USB Connected
-------------------------------------------
The 2 sbf images I tried seemed to load OK, according to the phone and the host tool I used. Now sure what the problem is now.

BTW, I don't think any of the attempts I made thinking it was a Droid X2 caused this, since they seemed to be rejected and the phone was normal and appeared unaffected afterwards. But the first time I tried to use the dx1 methods I ran into this. Now the phone only runs the bootloader.

Here is the output for sbf_flash for the "605" gingerbread sbf:

----------------
sh-3.2# chmod +x sbf_flash
sh-3.2# ./sbf_flash 605.sbf
SBF FLASH 1.24 (mbm)
OPTICALDELUSION

=== 605.sbf ===
00: RDL03 0x82000000-0x8204CFFF B942 AP
01: RDL01 0x00150000-0x001FFFFF DEFA BP
02: CG03 0x00000000-0x008FCB67 D93E BP
03: CG31 0xB0280000-0xB02847FF B9A8 AP
04: CG33 0xB1900000-0xB24C07FF 48DA AP
05: CG34 0xB0700000-0xB07047FF 75F3 AP
06: CG35 0xB1000000-0xB13FFFFF E2B9 AP
07: CG39 0xB2A00000-0xC41C07FF 3536 AP
08: CG42 0xB0800000-0xB083FFFF AC60 AP
09: CG47 0xB1400000-0xB18FFFFF 1062 AP
10: CG61 0xB0B00000-0xB0B7FFFF 7BF4 AP
11: CG64 0xB0000000-0xB00047FF 1768 AP
12: CG65 0xB0180000-0xB01847FF 7167 AP
13: CG66 0xD0000000-0xDFFFFFFF 9D92 AP

>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> uploading CG31: 100.0%
-- OK
>> uploading CG33: 100.0%
-- OK
>> uploading CG34: 100.0%
-- OK
>> uploading CG35: 100.0%
-- OK
>> uploading CG39: 100.0%
-- OK
>> uploading CG42: 100.0%
-- OK
>> uploading CG47: 100.0%
-- OK
>> uploading CG61: 100.0%
-- OK
>> uploading CG64: 100.0%
-- OK
>> uploading CG65: 100.0%
-- OK
>> uploading CG66: 100.0%
-- OK
>> verifying CG31
-- OK
>> verifying CG33
-- OK
>> verifying CG34
-- OK
>> verifying CG35
-- OK
>> verifying CG39
-- OK
>> verifying CG42
-- OK
>> verifying CG47
-- OK
>> verifying CG61
-- OK
>> verifying CG64
-- OK
>> verifying CG65
-- OK
>> verifying CG66
-- OK
>> rebooting
sh-3.2#
 
As far as the name convention goes, "Droid X", "X1", "DX1" yes, should refer to the same model phone that you have. The "Droid 1" or just "Motorola Droid" is a different model, it's the first in the Motorola "Droid" series that preceded the Droid X or X2. The root methods used Zegrush and Pete's One-Click are compatible across some models but as far as SBF files and ROMs that's where you need to be specific. I think you got the right files to work with now but I'm not sure why your phone isn't booting. Hopefully again, you haven't bricked the phone in the process.

To avoid future confusion, yes I would advise you to seek further counsel in other forums. I have no experience on the DX1 and I really hope you get the phone working again. I would still try to contact Verizon once you get it restored. If you have any serial numbers attached to your original invoice you can still prove they sold you the wrong phone. You never know what they might say.

Droid X1 forum links:
Main Forum
All Things Root
RootzWiki Forum (another great resource that has alot of support)
 
Many many thanks for all your help Coolpoete.

I'll keep after it. Hopefully I'll find another thread with dx1 specific info and someone as helpful as you were.

Take care, and I'll see ya around :D
 
You must log in or register to reply here.
Back
Top Bottom