- 05-14-2011, 10:36 AM #27
- 05-14-2011, 02:00 PM #28
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
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.
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?
- 05-15-2011, 09:14 PM #30
- 05-17-2011, 10:53 PM #31
- 05-25-2011, 01:32 PM #32
- 05-25-2011, 01:58 PM #33
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.
- 05-25-2011, 04:19 PM #34
- 2 Posts
- 0 Post(s)
- 0 Thread(s)
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
- 05-28-2011, 05:47 PM #35
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!!!!!
- 05-31-2011, 08:57 AM #36
- 06-14-2011, 06:05 AM #37
- 06-18-2011, 04:31 AM #38
- 06-20-2011, 08:26 PM #39
- 06-21-2011, 08:02 AM #40
- 06-22-2011, 08:14 AM #41
This can work with 3.1 however I wouldn't do it, I'll come up with a new guide and some new files for everyone. I've just been so busy at work and dealing with Motorola that I want to scream.
I don't want to let you guys down though So I'll stop slacking and get on it!
- 06-22-2011, 02:26 PM #43
- 06-22-2011, 08:28 PM #44
- 594 Posts
- 0 Post(s)
- 0 Thread(s)
In preparation, I'm trying to load the SDK, but am stuck in a loop saying I don't have JDK. I've installed it again and again. I've rebooted. I've tried everything I can think of. I've gone into Control panel - System - Advanced - Environment variables and changed the user path to C:\Program Files\Java\jdk1.6.0_26\bin in an attempt to force it.
Is just having the files from the .zip file provided going to be enough? I can live with that, although I'd be a bit disappointed because I was thinking about playing. I'm a microcontroller guy. I'm a fantastic assy guy, really good at C and "eh" at C++. Android is out of my box, but learning new stuff keeps the brain young.
- 06-22-2011, 11:37 PM #45
- 06-22-2011, 11:52 PM #46
- 06-28-2011, 04:46 PM #47
- 07-06-2011, 04:29 PM #48
- 07-08-2011, 07:43 PM #49
- 07-08-2011, 10:30 PM #50
Re: [GUIDE][VZW Version] Drivers, SDK, Unlocking, Rooting & Retur
Since it doesn't seem to be getting much of a response.
I Just gave up on rooting my Xoom, went back to 3.0.1 and went to update from there.
Can't do anything, though, on account of there being an inability to connect to WiFi. It says... error, right under Wi-Fi. And, considering this is a WiFi Xoom, it's fairly important.