Stuck at Motorola Dual-Core? [Wifi-Only]

[TheRedDroid]

Hiya,

After dealing with a half-bricked Xoom, I did some research on this problem and found a solution.

If in any case, you happen to get stuck on the "Motorola Dual-Core Technology"


Solution to this (For the MZ604, One-Click rooted):

MZ604 Stock .imgs Download: http://developer.motorola.com/products/software/

*Make sure you have fastboot in the same directory as your adb for easy access*

1. Plug in your USB cord

2. Turn off your Xoom (Vol-Up + Power)

3. Boot into fastboot (Vol-Down + Power)

4. On your computer, open up a command prompt, and type the following:

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

-or-

fastboot flash boot <path to boot.img>
fastboot flash system <path to system.img>
fastboot flash recovery <path torecovery.img>
fastboot flash userdata <path userdata.img>
fastboot erase cache
fastboot oem lock

5. Reboot the Xoom

fastboot reboot

6. There you go, back to stock!

 

[kcrudup]

On the real though, if you can get to Fastboot (or even the Moto "Android Recovery" state), you're not THAT bricked you've got to relock and go back to out-of-box; just keep a known-good boot.img around somewhere.

 

[Waza_Be]

You just saved my life!

 

[lrs421]

Thanks for sharing OP.

I take it this method is the same for 3.1?

 

[Lcsglvr]

I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.

I just posted this in a new thread.

I tried reverting back to stock using the "one click" root/unroot tool that was the first to come out for the Xoom.

Anyway, I tried the unroot process and everything was going fine, until something occurred. Now, it tries to boot up and says at the Moto Dual Core Technology screen, "Failed to boot LNX 0x0004 // Starting RSD mode 2".

Can someone help

Can anyone help!

 

[HooliganBG]

I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.

I just posted this in a new thread.






Can anyone help!

same here, anyone help ((

 

[rebill]

I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.

I just posted this in a new thread.






Can anyone help!

You can still enter fastboot if you xoom won't shut off. Just hold the appropria oncete buttons as it reboot. Happened to me last night upgrading to 3.1. It. Wouldn't shut down at all. Once I got into fastboot my computer saw it and I was able to fix

 

[finesse801]

Honestly, I almost went through all of this last night when my WIFI Xoom got stuck in a boot loop.

However, I noticed that when my recovery went to flash the new 3.1 file, I felt like it didn't take as long as it should have. The file was the right size and all and it even said that everything installed successfully, but it just kept boot looping regardless of trying over and over. So I went ahead and re-downloaded the 3.1 file and repeated the steps to flash it and everything worked.

So, before you spend a whole lot of time restoring your Xoom, simply re-download the files and try it one more time. It worked for me.

 

[Lcsglvr]

You can still enter fastboot if you xoom won't shut off. Just hold the appropria oncete buttons as it reboot. Happened to me last night upgrading to 3.1. It. Wouldn't shut down at all. Once I got into fastboot my computer saw it and I was able to fix

Thanks! Finally have some hope to recovering. I'll post steps I took later once I get this damn thing fixed.

 

[Lcsglvr]

hmmm... I'm in fastboot supposedly and tried to flash boot.img but it seems to be stuck at <waiting for device>

This happen to anyone else?


After search seems like a driver issue, but I have installed the drivers... I was previous rooted, so I know I have the drivers. Just to be sure, I ran the MotoHelper again. I don't understand. It's just seeing my device on the "Starting Fastboot protocol support."

help?

 

[zerin]

hmmm... I'm in fastboot supposedly and tried to flash boot.img but it seems to be stuck at <waiting for device>

This happen to anyone else?


After search seems like a driver issue, but I have installed the drivers... I was previous rooted, so I know I have the drivers. Just to be sure, I ran the MotoHelper again. I don't understand. It's just seeing my device on the "Starting Fastboot protocol support."

help?

Yes. How did I fix it? I returned the xoom and had a new one two days later.

If the screen says something like "Entering RSD 2" then you're boned. The xoom won't be recognized in either the current state or in fastboot state by the computer, so no amount of commands will help. Even having the stock images doesn't help with that. Even RSDLite can't see the xoom in that state.

There have been several reports of people just being honest to Motorola and them fixing the device under the warranty.

 

[Lcsglvr]

Hmm honesty. I'll give it a shot.

Sent from my ADR6300 using XDA App

 

[kelvie]

Is the final OEM lock necessary? It's quite a pain as your userdata gets wiped if you unlock it...

 

[drahyrt]

I was stuck on bootloop, with unrecognised device, through adb was able to get back into clockwork recovery somehow at first boot, think twice down volume? Could be wrong.
I was able tto rreflash zip 3.1 over thet top again.
sry if this is different and unhelpful, bu imagine things are pretty desperate if you are considering returning the device

 

[jbartcaps]

Yes. How did I fix it? I returned the xoom and had a new one two days later.

If the screen says something like "Entering RSD 2" then you're boned. The xoom won't be recognized in either the current state or in fastboot state by the computer, so no amount of commands will help. Even having the stock images doesn't help with that. Even RSDLite can't see the xoom in that state.

There have been several reports of people just being honest to Motorola and them fixing the device under the warranty.

You're not boned at all. I had that happen to me so I just got back into fastboot, downloaded the files in the OP put ADB, Fastboot and the adb extensions into the file I downloaded then ran the commands and got me XOOM back up and running fine.

 

[zerin]

You're not boned at all. I had that happen to me so I just got back into fastboot, downloaded the files in the OP put ADB, Fastboot and the adb extensions into the file I downloaded then ran the commands and got me XOOM back up and running fine.

You were likely in RSD 3, which is recognized by the computer. RSD 2 means adb and fastboot cannot see the device at all, so no flashing images is possible.

There's several states that all look very similar. Because some success was had with one doesn't mean it works for all. Motorola recognizes and is telling users that, in this state, the device needs to be sent back to them.

 

[JAdderly]

Can someone help us wifi xoom. Im stuck on the motorola screen and have a lil experience. I can fast boot reboot/fastboot device and it work but cant get the files from the hwi69 to fastboot on to it. I think im entering the commands wrong. Any advice would be appreciated

 

[okantomi]

Hiya,

After dealing with a half-bricked Xoom, I did some research on this problem and found a solution.

If in any case, you happen to get stuck on the "Motorola Dual-Core Technology"


Solution to this (For the MZ604, One-Click rooted):

MZ604 Stock .imgs Download: http://developer.motorola.com/products/software/

*Make sure you have fastboot in the same directory as your adb for easy access*

1. Plug in your USB cord

2. Turn off your Xoom (Vol-Up + Power)

3. Boot into fastboot (Vol-Down + Power)

4. On your computer, open up a command prompt, and type the following:

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

-or-

fastboot flash boot <path to boot.img>
fastboot flash system <path to system.img>
fastboot flash recovery <path torecovery.img>
fastboot flash userdata <path userdata.img>
fastboot erase cache
fastboot oem lock

5. Reboot the Xoom

fastboot reboot

6. There you go, back to stock!

Very good info to get into fastboot protocol:

 

[mrmota]

Much thanks for the info. Worked like a champ. On an updated 3.2.1 XOOM I did an unlock, re-locked the wrong way, soft bricked, unbricked back to locked state. Finally followed your steps applied stock files and XOOM is re-locked and stock rocking back at 3.01. I needed to do all this to make sure I could get it back to stock in case it goes back to BB in 2 weeks. I was lucky enough to find one at a BB just not sure if I'll keep it. I plan on trying out some roms plus I heard Motorola is planning on doing an ICS push to the XOOM. ICS is very nice. It runs great on my unlocked Verizon G-Nex.. Again Thanks..

 

[KaoticEvil]

This post not only saved my half-bricked non-rooted Xoom, but also let me flash it from the Singapore firmware (bought if from Amazon, don't ask lol) to the regular USA firmware so that I can properly root it!

Thank you so very much!!