Made the Most stupid mistake ever in my life! [FIXED]using modded cable, Thanks.

xdaman85

Senior Member
Apr 14, 2007
581
87
0
London
And now you have the cable for the next time you brick it ;)

What did you do to get past your second blocker (mode 2)?
Yes, please let us know what you did. I had a scare myself today...resulting from incompatible busybox update. Managed to make it back to android recovery and reflashed my nandroid backup but I saw that RSD Mode 3 and started freaking when my PC couldn't see the Xoom. I just kept pressing up,down/power til something worked. I think I will order that developer's cable now. It's just not worth this stress.
The reason I got the second blocker (RSD mode 2) is because I flashed the wrong Build, I flashed the "Build H.6.2-24 for Retail Europe" as I couldn't find a build for the UK on here:
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard

Now if you look at this link:
https://supportforums.motorola.com/thread/50967?start=0&tstart=0
You'll notice Matt mentions the "Build H.6.2-24 for Retail Other International" includes the UK, so after reading that I decided to flash that build and all went well.

I just made a Factory Cable, just-in-case. Figured it would be a lot easier if I wasn't under the stress of a bricked Xoom.

I also second okantomi's request. Most of us have never used RSD lite, nor had to try to "wake " a bricked device. Anything you can share with us, XDAman85 will be much appreciated.

Sent from my Xoom using XDA Premium App
Yes, that is a great idea mate, it's better to make one before you need it.

Any ways just to share how I did this.

My Xoom would start up on Dual Core Moto screen with a "Starting RSD mode 3" on the top left and that was it, it wouldn't do anything else.

Holding Volume + and power would reboot it and then it would automatically restart again and go back into the Dual Core Moto screen with a "Starting RSD mode 3" again. Plugging it into the PC didn't do anything, the PC wouldn't even detect it.

I then restarted the device by holding Volume up and power and before it started up, I pressed the Volume down button. This took it into the Dual Core Moto screen again, but this time the "Starting RSD mode 3" wasn't on the top left, it was in fastboot mode, but the problem was the PC wasn't detecting the Xoom. When I plugged the Xoom onto the PC using the Factory cable instead, it made the ding ding sound or what ever you want to call it and installed 2 different drivers:
Motorola Flash Interface driver and Mot Single ADB Interface driver.

I placed all four of my files, Boot.img, system.img, recovery.img and userdata.img into the platform-tools folder in the Android SDK folder and then typed the following commands into cmd:

fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock

after doing the "fastboot oem lock", it restarted the Xoom, and all was working as normal.
 

Kippui

Senior Member
Jan 1, 2011
595
37
0
Oops, you're right! The breakout board needs to be at the micro-B end, not the USB-A end.

Redo. Get these two:


http://www.sparkfun.com/products/10031 (USB Micro-B Plug Breakout Board) USD$4


http://www.sparkfun.com/products/9966 (USB Mini-B Plug Breakout Board) USD$2

Have along a regular USB-A male to mini-B male cable, some jumper wire, and a soldering iron (sorry! but it's really easy!). You know the deal, pin 1 (mini) to 1 & 4 (micro), 2/3/5 are straight-through.

Final cost: still $6! (plus shipping)
Can you make a few and sell for $25? You might be comfortable soldering things but I'm not.
 

e.mote

Senior Member
Feb 16, 2011
2,165
892
0
Make a Motorola factory cable for Xoom w/ no soldering

@Kippui

The breakout method is versatile in that it can be reconfigured for any pinout, and thus can be (re)used for any custom USB connection. You can also use it as a USB analyzer. But for a specific connection, eg this "factory" cable, try the no-solder method below:

http://talk.maemo.org/showthread.php?t=14092

The how-to is for an OTG cable, but as TX2000 said, it's basically same as the Moto factory cable. The hard part is to find a cable that has all 5 wires connected and correctly color-coded, which is in the how-to,


http://www.amazon.com/gp/product/B000Y032X8 (mini-B female to micro-B male adapter) USD$3

Ignore the instructions in the how-to, as we only need the link to the cable. Use a utility knife and remove a 1" section of the cable sheath to expose the 5 wires. Per the article, they should be correctly color-coded. Use a tap splice connector (probably 22-26 AWG, available in any hardware store or online) to connect the red (#1, or VCC) wire and brown (#4, or ID) wire together. Electrical tape the exposed section. No soldering.

Note that if the cable doesn't have the correct color code (red/green/white/brown/black), you'd have to cut the connector to trace each wire to the pin, which is a PITA, but still doable. Hence I'm linking to this article, which is linked to a specific part with (hopefully) correct color codes.
 
Last edited:
  • Like
Reactions: okantomi

gabs139

New member
Dec 6, 2012
1
1
0
Help me with my factory cable

The reason I got the second blocker (RSD mode 2) is because I flashed the wrong Build, I flashed the "Build H.6.2-24 for Retail Europe"


Yes, that is a great idea mate, it's better to make one before you need it.

Any ways just to share how I did this.

My Xoom would start up on Dual Core Moto screen with a "Starting RSD mode 3" on the top left and that was it, it wouldn't do anything else.

Holding Volume + and power would reboot it and then it would automatically restart again and go back into the Dual Core Moto screen with a "Starting RSD mode 3" again. Plugging it into the PC didn't do anything, the PC wouldn't even detect it.

I then restarted the device by holding Volume up and power and before it started up, I pressed the Volume down button. This took it into the Dual Core Moto screen again, but this time the "Starting RSD mode 3" wasn't on the top left, it was in fastboot mode, but the problem was the PC wasn't detecting the Xoom. When I plugged the Xoom onto the PC using the Factory cable instead, it made the ding ding sound or what ever you want to call it and installed 2 different drivers:
Motorola Flash Interface driver and Mot Single ADB Interface driver.

I placed all four of my files, Boot.img, system.img, recovery.img and userdata.img into the platform-tools folder in the Android SDK folder and then typed the following commands into cmd:

fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock

after doing the "fastboot oem lock", it restarted the Xoom, and all was working as normal.

Hi I followed these steps to the bar ive got a factory cable my xoom is bricked and stuck in RSD Mode 3, when i plug it in it makes the ding dong noise and it installs the drivers you mentioned. I go to flash the boot.img in cmd platform tools folder that I placed there and the cmd just sits there saying <waiting for device> and nothing happens? Please please help I feel I am so close now that my pc actually recognises the Xoom as a usb device I just cant flash it out of this RSD mode 3 any suggestion please help!


07453654934

---------- Post added at 04:33 PM ---------- Previous post was at 04:26 PM ----------

Hi I followed these steps to the bar ive got a factory cable my xoom is bricked and stuck in RSD Mode 3, when i plug it in it makes the ding dong noise and it installs the drivers you mentioned. I go to flash the boot.img in cmd platform tools folder that I placed there and the cmd just sits there saying <waiting for device> and nothing happens? Please please help I feel I am so close now that my pc actually recognises the Xoom as a usb device I just cant flash it out of this RSD mode 3 any suggestion please help!


07453654934
Scratch that I missed the getting rid of the RSD Mode 3 part cheers your a lad!
 
  • Like
Reactions: Kovaelin