I was researching this and came across this: Xoom Wifi "Failed image LNX 0x0002 / RSD mode 2" - xda-developers someone seems to be saying you have to keep trying to get the drivers re-installed and it worked for him, others are saying it didn't work for them. Either way check it out.
[GUIDE][VZW Version] Drivers, SDK, Unlocking, Rooting & Returning to Stock
- Thread starter 2CupsWithString
- Start date
1. Download the source Motorola files here: http://developer.motorola.com/produc...rm=unlockboard (a free membership may be required)
2. Extract the zip file so you have: boot.img, system.img, recovery.img, userdata.img and place these files in to the same folder as fastboot (either in the SDK or from the zip attached to the first post).
3. Reboot your Xoom in to the bootloader.
Power off your Xoom, once it's off, power it on by simultaneously pressing the volume down and power button, keep your fingers pressed until the Xoom says it's starting fastboot protocol support.
4. Open a command prompt in the folder with fastboot and the Motorola image files.
5. Enter these commands
Quote:
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
Your Xoom has now been restored to factory software and the bootloader has been locked.
__________________
Fred
Ouch! After following each step I'm stuck with "failed to boot LNX 0X0004" in red with "starting fastboot protocol support" below it.
After updating Moto tools on both laptop and PC, neither of them recognize the Xoom Wifi and command prompt message "waiting for device".
Do I need to start a Motorola repair ticket?
Chris
2. Extract the zip file so you have: boot.img, system.img, recovery.img, userdata.img and place these files in to the same folder as fastboot (either in the SDK or from the zip attached to the first post).
3. Reboot your Xoom in to the bootloader.
Power off your Xoom, once it's off, power it on by simultaneously pressing the volume down and power button, keep your fingers pressed until the Xoom says it's starting fastboot protocol support.
4. Open a command prompt in the folder with fastboot and the Motorola image files.
5. Enter these commands
Quote:
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
Your Xoom has now been restored to factory software and the bootloader has been locked.
__________________
Fred
Ouch! After following each step I'm stuck with "failed to boot LNX 0X0004" in red with "starting fastboot protocol support" below it.
After updating Moto tools on both laptop and PC, neither of them recognize the Xoom Wifi and command prompt message "waiting for device".
Do I need to start a Motorola repair ticket?
Chris
Last edited:
Thank you.
Crap, I think my xoom is bricked, I didnt realize the rooting process wouldnt work for 3.1 Is there anything I can do to fix this? Its stuck at the Boot screen that says Dual Core Technology with a red Motorola sign. I would greatly appreciate any help.
Crap, I think my xoom is bricked, I didnt realize the rooting process wouldnt work for 3.1 Is there anything I can do to fix this? Its stuck at the Boot screen that says Dual Core Technology with a red Motorola sign. I would greatly appreciate any help.
Last edited:
You shoudl still be able to use fastboot or adb to reboot back into fastboot to fix your mistakes (aka reflash to stock)
This DOES work, I did it last night after making the same mistake and thought that I bricked my Xoom. You might need to enter in the command more than once, first try always gave me a device not found type error and they trying it again 1-2 more times always seemed to kick it back to fastboot and I reflashed everything to stock
This DOES work, I did it last night after making the same mistake and thought that I bricked my Xoom. You might need to enter in the command more than once, first try always gave me a device not found type error and they trying it again 1-2 more times always seemed to kick it back to fastboot and I reflashed everything to stock
My screen is stuck on the Dual Core Technology screen as well and everytime I reboot using the volume up / power key it goes to "Starting fastboot protocol support"
I have also used the volume up/power key to reboot and pressed the volume down key when rebooting to go into the Android recovery to reset to factory settings.
It goes throught he factory reset but when it reboots it freezes in the Dual Core Technology screen.
Please help me!!!!!
I have also used the volume up/power key to reboot and pressed the volume down key when rebooting to go into the Android recovery to reset to factory settings.
It goes throught he factory reset but when it reboots it freezes in the Dual Core Technology screen.
Please help me!!!!!
i didn't read that this wouldn't work on 3.1 and went ahead and did it .. i got past the first step but then couldn't find the files to root my xoom but my xoom is working
Thanks for this. I hunted on the Moto site for ages before I gave up!
Also helped having the zip you provide, ad the jdk I downloaded didn't include the fastboot.exe.
Also helped having the zip you provide, ad the jdk I downloaded didn't include the fastboot.exe.
Similar threads
Latest posts
-
-
-
-
Some application sends a vocal notification. Not shown in notification history.
- Latest: android_questions
-
Trending Posts
-
Repeated failure to update Google Play system update- Started by jtfwTX
- Replies: 1
-
Android has missing shortcuts and automation
- Started by kolilco1
- Replies: 1
-
Some application sends a vocal notification. Not shown in notification history.
- Started by android_questions
- Replies: 2
-
Question note8 wiped clean but can't get into phone to set it up
- Started by annamagnani
- Replies: 5
-
Facebook
Twitter
Instagram