Database Info

[Q] If Wi-Fi Xoom is bricked, can (RSD) flashing the 3G SBF, then fastbooting work?

Damn, I can't fit the whole question in the subject.
Let's say someone hypothetically bricked their wifi Xoom. Can't connect with fastboot anymore. However, it does get picked up by RSD Lite.
If the Wi-Fi Xoom is bricked, can flashing the 3G SBF using RSD Lite be used JUST to enable fastboot? And if so, would just doing a "fastboot flash boot boot.img" and "fastboot flash system system.img" (with the right wi-fi files) be able to save it? And possibly the same with recovery.img?
I noticed that the boot.img and system.img files are the same size between the wifi version and the 3G/4G. Same with the recovery partition. That's why I ask.

If you can enable fastboot using RSD then I don't see why you wouldn't be able to unbrick it.
If I were you I would try it. I don't think you can brick anymore than what it already is
Sent from my Xoom using Tapatalk

Kas206 said:
If you can enable fastboot using RSD
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1037094
when i hold power and Volume up restart the xoom and hold power + volume down its show
failed to boot LNX 0x0004
Starting Fastboot protocol support
but the problem the computer not Recognize on the xoom . i installing drivers and still not Recognize
whats i do ?
i have Windows and Mac

try uninstalling your drivers and use this to reinstall
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.0.40_Driver_4.9.0.exe

A Question very important?
Xoom wifi is good or the xoom 3g? information about it,, I appreciate it

At this moment, I can only get the wifi version in Canada. I don't know if I would need it on 3G/4G.
Dinar, I assume you used to be able to connect? But not after the 0x0004 error? Can you get in RSD mode at all? When you are in Fastboot mode, does "fastboot devices" on your computer show a device?

What's wrong with that appears in the
Scourge1024 said:
Dinar, I assume you used to be able to connect? But not after the 0x0004 error? Can you get in RSD mode at all? When you are in Fastboot mode, does "fastboot devices" on your computer show a device?
Click to expand...
Click to collapse
no not show a device
when i connect a xoom in computer the computer never show the xoom
Scourge, what is the error message in your xoom?

It was something like LNX 0x0004 and the following message was about Fastboot or RSD mode 2. It changed depending on if I held the down button on reboot. I lost the ability to scroll through the boot options.
I couldn't get fastboot, adb or RSD Lite to see my Xoom in either mode.

Did you get RSDLite to flash the .sbf file? I tried that on my bricked device and I couldn't see anything happening on the screen of the xoom. I waited for about one or two minutes and stopped the process. What about the drivers? Are there different drivers for adb, fastboot and RSDLite? I have motohelper installed and it says all necessary drivers are installed. Can it be a driver issue? Thats something I haven't tried.

My Motohelper updated itself and I was still not connecting with my first Xoom. There are different drivers. Different ones become active depending on what mode you're in.
But I couldn't even see my Xoom so I declared it bricked as of April 14th at 3:47am. I seriously don't know the exact time.
When I use adb or fastboot from my Mac, I don't need drivers. It just works.

i have Mac and Windows same problem not show xoom
give me steps for the mac i want try

mine is just like yours says failed image LNX 0x0002
starting rsd mode 2
will cycle with the power and up button to the above. push the down button says it is in the fastboot protocol mode but computer doesn see it. cmd module says waiting on device. have current usb drivers. anybody out there can repair it. moto wants an arm and a leg for a repair because it was fastboot oem unlocked and voided warranty

Yeah, if nothing can see it... What exactly does Motorola want to charge to fix it? Can't you return it to where you bought and get an exchange? I'd only feel okay with that if you bought at a big store though and not a mom and pop sorta shop.

I dont know if this will help, but I noticed that in your first post your commands may not be complete:
fastboot flash boot boot.img
fastboot flash system system.img
Your are missing the words in red above. I may be wrong and you dont need them, but Im sure you do. At least all I got was a bunch of command options scroll in my command prompt without the entire command.
I thought I had a bricked xoom after messing around with the frameworks-res.apk through "root explorer" app. I flashed the boot.img like crazy, but it was my frameworks that I had messed with last before the locked boot sequence. I found an image on the boards for the 3g system.img and I was back in business.

cvela said:
I dont know if this will help, but I noticed that in your first post your commands may not be complete:
fastboot flash boot boot.img
fastboot flash system system.img
Your are missing the words in red above. I may be wrong and you dont need them, but Im sure you do. At least all I got was a bunch of command options scroll in my command prompt without the entire command.
I thought I had a bricked xoom after messing around with the frameworks-res.apk through "root explorer" app. I flashed the boot.img like crazy, but it was my frameworks that I had messed with last before the locked boot sequence. I found an image on the boards for the 3g system.img and I was back in business.
Click to expand...
Click to collapse
I did the same. Only thing is after I had WiFi showing "Error" under it and it wouldn't start. Had to insmod the bcm4329.ko and I was back in business.

Scourge1024 said:
Yeah, if nothing can see it... What exactly does Motorola want to charge to fix it? Can't you return it to where you bought and get an exchange? I'd only feel okay with that if you bought at a big store though and not a mom and pop sorta shop.
Click to expand...
Click to collapse
i sent it back to moto

cvela said:
I dont know if this will help, but I noticed that in your first post your commands may not be complete:
fastboot flash boot boot.img
fastboot flash system system.img
Your are missing the words in red above. I may be wrong and you dont need them, but Im sure you do. At least all I got was a bunch of command options scroll in my command prompt without the entire command.
I thought I had a bricked xoom after messing around with the frameworks-res.apk through "root explorer" app. I flashed the boot.img like crazy, but it was my frameworks that I had messed with last before the locked boot sequence. I found an image on the boards for the 3g system.img and I was back in business.
Click to expand...
Click to collapse
You are correct. I'll fix my first post!

I'm getting all the same side effects here from attempting to re-lock the wi/fi xoom. Im debating on what to do here.

Oohh... Relocking is not good... If the images aren't exact factory ones, that's a sure brick. No point in relocating the Wi-Fi version. At least not right now.
If RSD Lite and Fastboot can't see it, look for your receipt...

haa yeah. Thats too bad that I'm just a fewww days over my 14 day store warranty and didnt buy the insurance. I sent in a repair order online where i ship it back to them.....dont know if illl ever get anything back though ha

[Q] Bricked in RSD Mode 2 and PC cannot detect XOOM - help

My XOOM is bricked and show RSD Mode 2 when power on, I can go into the fastboot mode by press VOL UP + Power button, and plan to do fastboot process to restore the system.
However, my problem is the Computer cannot detect XOOM, when I input "fastboot oem unlock", then the command stopped at a "Waiting for device" reply, so I cannot go to next step.
I have installed all of the needed software I see in this forum. Moto USB driver, Android SDK, Java, fastboot.
I have tried the RSDlite 5.0 but with the same reason, the RSDlite cannot detect device so it cannot work out.
anyone with the same problem and how to solve it? Do I need to send back it to Motorola for restore?
Thanks a lot for your help, It is too bad to stay with a bricked XOOM.

Xoom stuck in RSD mode 2
I'm having the same issue. I'm at the boot screen with the Moto symbol and I have an error in the top right that says "Failed image SOS 0x0002" and below that "Starting RSD mode 2". My computer does not see my xoom. I've tried other links to this problem but they are not the same. They all mention RSD mode 3. Damn my stupidity . Someone please help

Unbrick RSD Mode 2
I don't know what version xoom you are using, or under what circumstances you bricked your xoom under, but I managed to get mine (3g, USA) out of RSD 2 this way after it wouldn't boot coming out of a botched automated unroot/relock procedure. You may want to try this to get back to stock and working again, and then redo all the rooting and tweaks. I am going to go on the notion that you use windows (I use windows 7 64bit, but the steps should be the same or similar for other versions), have android sdk installed, and know what fastboot is.
... but first a few disclaimers!
1) If everything is fine now, disregard this reply!
2) I am in no way an expert in unbricking xooms, this is just how I figured it out for my situation.
3) Again, this is how I unbricked MY xoom, it may or may not work for you. If something here doesn't work for you, I really can't help.
4) I am not as big of a douche bag as I sound like in the last couple of disclaimers. If you are stuck and there is something I forgot to mention, I'll try to help.
4) You are probably having the same problem as someone else. As much as I hate to say it... GOOGLE IT! Just make sure you have all the error codes and include how you bricked your device. Horrible example: " R2D2 mode after I tried to turn my xoom into an autonomous killing machine by feeding my device crepes error code xx42" Bad example, yet it's very (odd) specific.
5) Don't be offended if I go into details that seem way below you. Someone else may need to read this, and may not understand everything you or I do. I try to break everything down as much as I can. Also, if I didn't go far enough into detail, let me know.
6) I inserted two 4's to see if you are really taking the time to read the entire post so the first 4 may not be true!
7) Once you get fastboot working, and the bootloader unlocked, the brick may be undone. I have you get the stock images just in case. Following the last part of the post will wipe your data.
Now back to our regularly scheduled programming...
1) Download the correct stock system software (wifi/3g) from motodev.
motorola.com/products/software/?utm_campaign=xoomsoftware&utm_medium=motorolacom&utm_source=supportforums&utm_term=unlockboard&pubid=987654
You have to register on the site. I would attach the files, but I agreed to a nice end user agreement saying I will not redistribute them. Also, I can't post links yet since I am still new so the beginning of the url is missing. There are posts in the xoom development forum that link to the file.
2) Unzip the contents to the folder where fastboot is located. Usually located in C:/program files/android/android-sdk/tools, or C:/program files (x86)/android/android-sdk/tools if you use a 64bit version of windows.
3) Power on the xoom and get into fastboot by holding the volume down button as soon the moto logo shows. I noticed it took a little while longer than usual for fastboot to show up. I noticed in the original post that the user said Volume up + Power. That is how you hard reboot... or do a dragon punch...I forget.
4) Once the device shows fastboot is running, Open a command prompt ( start, all programs, accessories, command prompt, or type cmd in the search bar ). Next type/copy these commands minus any comments marked by "<---". Note that every new line is a new command:
ON THE PC:
cd c:/program files/android/android-sdk/tools <---May be different depending upon what version of windows you are using. Replace 'programs files' with 'program files (x64)' if using 64 bit windows. If all else fails, type cd then copy one of the paths from step 2.
fastboot oem unlock <---This MAY solve your problem right here
should say check your device for instruction. On the xoom, hit volume down, then volume up, voulme down again, and volume up again to confirm the unlock.
When I did that my xoom rebooted, and I was back in business; however, if the unlock worked and you are still not able to boot, let's get back to stock. Get the xoom back into fastboot again by holding the volume down button while it starts.
ON THE PC:
You should still be in the same command prompt from earlier.
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot oem lock
This will wipe your xoom completely, but your nice shiny paperweight should be less paperweight like. I do the relock for good measure just because I think I left it unlocked, then I received an OTA update, and got good RSD Mode 2 again for some reason. If you want, try it without the fastboot oem lock command in case you want to get right back into rooting, flashing recoveries, etc... Well, hope all this helped. Again if clarification is needed, let me know and I will try to help. Hope this works. Take it easy!

zanzebar said:
I'm having the same issue. I'm at the boot screen with the Moto symbol and I have an error in the top right that says "Failed image SOS 0x0002" and below that "Starting RSD mode 2". My computer does not see my xoom. I've tried other links to this problem but they are not the same. They all mention RSD mode 3. Damn my stupidity . Someone please help
Click to expand...
Click to collapse
I have the same issue. Looks like I now own a brick!

zanzebar said:
I'm having the same issue. I'm at the boot screen with the Moto symbol and I have an error in the top right that says "Failed image SOS 0x0002" and below that "Starting RSD mode 2". My computer does not see my xoom. I've tried other links to this problem but they are not the same. They all mention RSD mode 3. Damn my stupidity . Someone please help
Click to expand...
Click to collapse
1) Turn the xoom on and leave it plugged into USB.
2) When it says Starting RSD Mode 2, type the following in your command prompt in windows "fastboot oem unlock"
*Make sure you are typing these commands within the directory where your fastboot and .img's are located. ( I dropped mine in C:\Android-sdk\platform-tools\
*The Xoom will not respond initially and your command prompt will say "waiting for device".
3) Hold the power button and volume up to reset the xoom. The fastboot command should intercept the xoom booting and take you to the unlock prompt again. Follow the on screen instruction.
*This will wipe the device again, which I'm assuming you did when you locked
it with a custom kernel (boot.img)
After it is completed, type "fastboot reboot" in windows command prompt or just reboot however you can.

This doesn't work!
i have two motorola xoom, one of them have the failed image sos 0x0002 starting rs mode 2.
When i plug in the bricked motorola xoom nothing respons in the computer. i have the fastboot on with the waiting for device activated with fastboot oem unlock and RSD Lite v4.9 or 5.0 doesn't detect it too..
What can we do? i'm from spain and i bought the tablet in new york. Can i send it to the garanty?

The only way to do this is as follows:
Download rsdlite 4.9 or earlier only and install it on your computer.
Downlaod the latest moto drivers and install them.
Search for and download the stock SBF file for your Xoom wifi or 3g.
Get your Xoom to the rsd mode 2 screen and plug it in your computer
Use rsdlite to push the SBF file to the Xoom.
It will probably say it failed after a long wait. Its OK. Just restart your Xoom and your back to factory.
Good luck

csseale said:
The only way to do this is as follows:
Download rsdlite 4.9 or earlier only and install it on your computer.
Downlaod the latest moto drivers and install them.
Search for and download the stock SBF file for your Xoom wifi or 3g.
Get your Xoom to the rsd mode 2 screen and plug it in your computer
Use rsdlite to push the SBF file to the Xoom.
It will probably say it failed after a long wait. Its OK. Just restart your Xoom and your back to factory.
Good luck
Click to expand...
Click to collapse
i believe there is no SBF file for wifi xoom right now.

So I haven't had a chance to try anything you all have said since I've been at work all night. I have to agree with the last post though. I have looked everywhere and cannot find the.sbf I hope it leaks soon though so I dont have to deal with the shame of sending it to moto.

I still can't get the xoom to receive commands. I need that .sbf. I'll definitely be checking every minute for the wifi version leak.

The above means does not work.
I end up with a RSD re-enumaration failed error.

I'm on wifi xoom and can make it into "Starting Fastboot protocol support" but when i attempt to flash any of the images posted above or do a fastboot oem unlock I simply get <waiting for device> and nothing responds. Help?

Your Xoom is completely Bricked
At this point there is nothing you can do. You can A. wait patiently for .SBF for wifi only xoom or B. explain to motorola what happened and if it is under warranty they will replace or repair your xoom in 1 week.

Mayday
I am having the same problem, will someone be kind enough to find get the sbf out... aint android open source?

BlueEditionE6 said:
I am having the same problem, will someone be kind enough to find get the sbf out... aint android open source?
Click to expand...
Click to collapse
Android is open source but google is not releasing the source code for honeycomb yet.not exactly the same thing. You might be ****ed...

rockhumper said:
Android is open source but google is not releasing the source code for honeycomb yet.not exactly the same thing. You might be ****ed...
Click to expand...
Click to collapse
As long as you didn't reformat your internal sdcard you're probably not really bricked. It's not impossible but is really hard to brick the Xoom. I would suggest you go to the IRC #[email protected] freenode and see if any of those guys can help you. If anyone can, they can.
Good luck!

Trying to root my g-slate

So I got bored with waiting around for someone else to do it, and decided to take a shot at rooting my G-Slate. I figure it's basically the same as the Xoom, so the same sort of process should work....
My initial game plan was this:
Get into Fastboot
Flash a recovery image
Boot the recovery image
Now "adb shell" is a root shell
Copy a "su" binary into /system/bin
Declare victory
That started out pretty well. Powering on and holding down volume-up gets into fastboot. The fastboot binary on my laptop sees the device. Typing "fastboot oem unlock" claims to work. Flashing the Xoom recovery image [1] claims to work.
But... I can't seem to boot to recovery. Running "adb reboot recovery" just reboots normally. Doing "fastboot boot recovery.img" freezes the device. Booting with down-volume gets me to some sort of LG updater state that might as well be freezing the device. Booting with both volume buttons down either 1.) doesn't boot or 2.) brings me to fastboot. That's all the button combinations.
So I guess my question is this: does anyone have any suggestions for how to proceed?
I really don't want to just blind-flash the Xoom boot.img from the unlock thread, because if that doesn't work my device is bricked until someone either makes a working kernel or somehow extracts the current one.
On the up side, my g-slate is *claiming* to have working fastboot that can flash images. It could be totally lying though.
[1] http://forum.xda-developers.com/showthread.php?t=1038870

Tried the same method. No dice. Right now there has been no luck on anyone's part that i know when it comes to rooting. Shoot we havent even been able to get one of the xda mods to create us our own forum for that matter...i had to go out and create my own. I have tried other methods that worked on my nexus one when none other would but alas still no luck.
I imagine since the g-slate is brand new that its not a question of if it can be rooted, but how and when. I'm going to try one more method i know of that worked on the lg optimus tonight. I'll post here if it works.

Soure code seems to be available too
It also appears the source code is available from LG here .lg.com/global/support/opensource/opensource-detail.jsp
I just did a search under mobile phones for the model number 909
Don't know if that will help anyone here.
I have been hunting all over for root access. fastboot says I unlocked the bootloader but nothing seems to want to take.
XDA Mods, please create a G-Slate Section
HA. member since 2006 and my first post just add a www in front of that link

When the fastboot says Ok it is not telling you that you have unlocked the device. It says ok no matter what you put in. Try unlock and it will say ok as well. If it unlocked the device then it would prompt you on your device with a popup that tells you that you are voiding your warranty and have you hit ok. The device is not unlockable using the 'fastboot oem unlock' command. I have rooted a lot of devices, but never have done anything on an LG device and it is awkward. Vol+ and power gets some form of fastboot. Vol- and power gets download mode, which I am used to from Samsung devices (if we can get an interface like Odin then this becomes a lifesaver and makes the device "virtually" unbrickable). I cannot find any form of recovery. 'Adb reboot recovery' just restarts the device. One interesting this is that pushing both Vol+ and Vol- and power puts the device into what would seem like a bricked device (just use reset button). This same button combination worked on some Samsung devices so something is happening there, but I have not tried enough combos yet to figure it out.
So far as root, well, I have tried z4 (works with nearly all Sammy devices and LG seems to be using a lot of Sammy ideas or at least it looks that way), but to no avail. Gingerbreak apk might work or even the Xoom Root, but the rootboot.img might be different and I have not opened any of that up yet. I did get SU loaded once and in the system, but I could not reproduce it.
I will be working on this some more this weekend (returning the device at some point as it reboots on its own about 5 times a day), and looking into the recovery issue. If anyone has any ideas then please post.
Also, it looks like LG hacked the crap out of the thing to get the SD card to mount and it is weird, so please be aware of that. The SD card mounts every time you plug the device in and there is no way to turn that off. The reason this is important is that some root methods require that the SD card not be mounted, so you will have to unmount the SD card via ADB and with the card being internal I am not too sure it is a good idea, but . . .
I will mark this thread as a favorite and update if I get any where. I know that Cyanogen and Kmobs got G-Slate's recently, so hopefully they can give us a little insight once the device gets to them. I have also contacted LG and @TheLGGirl and asked them to confirm that the bootloader is locked, but have not heard anything back.

Also, the the Acer HC tablet was rooted yesterday using the Gingerbreak root method, and so that is helpful, but it has an SD card (see above).
Sent from my LG-V909 using Tapatalk

I tried the Acer method (GingerBreak) and it does not work. Will look at the logcat in a bit.
Sent from my LG-V909 using Tapatalk

Thanks hourst
I am used to odin (also have a vibrant). Something like that would be a life saver.
Makes sense about the fastboot commands seeming to take.
I was also having reboot issues with mine. I had a handful of reboots each day (about 3 or 4) for the first two days but they have stopped completely now. I have had it for about a week now and have not noticed a reboot since day 2.
I will keep poking around to see if i can come up with anything as well.

Could this help?
Under the impression the G2x root method maybe helpful since they are both LG devices with somewhat similar hardware.
Does anyone know or tried this http://forum.xda-developers.com/showthread.php?t=1056847 to see if it works?
Not sure if I am brave enough yet. But it could be possible the vol up+vol down+power button combo that seems to lock the device is putting it into the mode needed to run the nvflash application.
This really is mostly speculation but could be something to try.

Success
So i got brave.
vol up+vol down+power Device seems to freeze. Plugged in the usb and got a new hardware pop in windows. Listed it as APX device using the drivers in the file listed in my previous link installed successful and the device was found.
That is a far as I went.

im doing the NVFLASH right now... wish me luck and see how far I can go

Any Luck?
Suzannemscott
How did it go? any results or do you have a large brick?

ok i tried. and no luck , i did manage to brick it tho, but i was able to unbrick it phew, back to square one

Did it seem like anything happened? Also what did you do to unbrick it?

To unbrick it i just press the reset button, in the back, quickly hold down Vol+ and Vol- then it goes to a the Gslate screen with the square and then i hold down the reset again and it reboots, maybe i am doin to much but hey it get my Tab back it works!

Gah! Why does it claim to have fastboot when *any* fastboot command except "fastboot devices" just makes it freeze?
I went ahead and built the kernel that LG released and packed it into the clockwork recovery image for the Xoom. Fastboot boot... freeze.
Computer always says this, but I think it's just making fun of me:
downloading 'boot.img'... OKAY
booting... OKAY
I also tried to build and boot a custom kernel with a fb console enabled just to get some feedback, but all it wants to do in response to "fastboot boot" is freeze.
I'm starting to get discouraged here. My 14 day return period ends on Tuesday and I don't really want to get stuck with an unrootable device.

Chandon, would you be able to send me the kernel you built?

I'm sure someone with more expertise and knowledge will be able to root this thing eventually...but right now it seems to be a lot trickier to root than I initially thought. It's not unrootable...just complicated. Over my head by a lot. I don't think I'm going to return it...but I've now resigned to the fact that I may not ever be able to find a working method to root the damn thing myself.

SmellyTunic -
I've uploaded the two kernels I built [1].
They're both built from the v909 kernel source posted by LG[2], following the instructions posted by adrynalyne[3] for building custom android kernels, but I don't have any way to test them aside from the fact that "fastboot boot" doesn't work either straight, with a ramdisk, or with a rebuilt recovery image using the tools in [4].
[1] http://pandion.ferrus.net/gslate/kernels
[2] http://opensource.lge.com
[3] http://forum.xda-developers.com/showthread.php?t=1039854
[4] http://forum.xda-developers.com/showthread.php?t=915808

hourst2 said:
When the fastboot says Ok it is not telling you that you have unlocked the device. It says ok no matter what you put in. Try unlock and it will say ok as well. If it unlocked the device then it would prompt you on your device with a popup that tells you that you are voiding your warranty and have you hit ok. The device is not unlockable using the 'fastboot oem unlock' command.
Click to expand...
Click to collapse
Not entirely true. You said that if you try simply typing in "fastboot unlock", it tells you "OK" as well, right?
Not for me. That only ended up displaying the whole list of fastboot commands.
I agree with you that "fastboot oem unlock" is not unlocking the device though. But what are the alternatives? Everything I've ever rooted has used "oem unlock". I've never even heard of a different command that can be used to unlock a bootloader. I tried a google search and came up with nada.
Hmm...

wich you the best make happen

[Q] Can't unbrick. Tried nigh everything.

Greetings! First of all, I would like to thank anyone who takes the time to help me diagnose and resolve this issues, let alone anyone who takes the time to read this thread.
I've been having issues with my Xoom (ICS 4.0.0) for about 3 weeks now.
A brief history of the issue's occurrence:
-I unrooted the device and returned it to stock.
-Everything was fine and dandy until one day it spontaneously said something along the lines of 'Android is upgrading..', and then performed a reset.
-Since resetting, it bootloops.
The device only turns on when plugged into a charger and hard reset.
The device only turns off when allowed to boot loop for minutes and then hard reset (it simply does not reset, and just turns off).
I'm not the most technically-savvy person with android devices but here are some things I've done/noted.
When trying to use adb commands, it does not recognize the device or properly issue commands.
I've tried wiping data/clearing cache to no avail.
EDIT: I've tried fastbooting, but the bootloader will not unlock. When trying to unlock, it simply resets and then acts as though it was never unlocked.
I have no idea how to return it to a stock image. All I know is that I have a micro-SD and some spare time.
Could anyone help me understand what exactly is going on with my Xoom?
If I can provide you with any more information, please let me know.
Thanks again. (=

If it was stock and spontaneously upgraded it sounds like a bad OTA upgrade. I've been rooted from the start so never have taken an OTA upgrade...don't you need to accept it or can it just upgrade on it's own?
Anyway, can you get it into fastboot mode?
Volume up and power, then at dual core screen, press volume down...if you see something like "entering fastboot mode" you're not bricked. You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
If you haven't done so, just google 'recovering Xoom using fastboot' and you should get some good information.
Good luck!

Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools -
http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
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
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
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
As Always If This Was Helpful Hit the Thanks!

Yeah, what Mjamocha said...

okantomi said:
Yeah, what Mjamocha said...
Click to expand...
Click to collapse
LOL Thanks.

okantomi said:
Anyway, can you get it into fastboot mode?
Click to expand...
Click to collapse
Yes, I can. But so far nothing has been successful in terms of fastboot commands.
okantomi said:
You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
Click to expand...
Click to collapse
When I try to execute fastboot commands such as 'fastboot flash boot boot.img'.. it says the following:
Device still locked. Device must be unlocked first. Failed to process command error(0x8)
Whenever I try to unlock the bootloader, it appears to be successful at first and then the device reboots. But it just reboots to a bootloop, and the bootloader still says its locked. Perhaps I made a mistake in communication. The bootloader is currently locked and will not unlock, as just described.
When I try to unlock it and it reboots, even if I access the fastboot menu right away, it still says the device is still locked.
Thoughts?

Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.

slacka-vt said:
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
Click to expand...
Click to collapse
Yes, I can get into android recovery. However, within a second of switching into recovery mode, the robot falls down and there appears to be a red triangle caution sign containing an exclamation point.
When trying to do a factory reset, it says all data is wiped (as normal). Upon rebooting, it continues to bootloop. So essentially the factory reset and cache clear options in the Android Recovery menu do not produce the expected results.
Pretty odd. I didn't mess with the Xoom at all prior to this issue.

Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.

slacka-vt said:
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
Click to expand...
Click to collapse
Yeah, just tried it to no avail. Thanks so much for your help anyway. (=
I'm not sure what to do now.

I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.

slacka-vt said:
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
Click to expand...
Click to collapse
I hear ya. I've tried 2 different cords and 3 different computers. I'm using a Mac (10.6.8) right now, but have used 2 PCs (Vista + 7).

Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?

slacka-vt said:
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
Click to expand...
Click to collapse
I got the 'device still locked' error. Weird, huh?

How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.

slacka-vt said:
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
Click to expand...
Click to collapse
Yeah I tried that. Won't lock or unlock successfully. Locking produces no difference, and unlocking produces the same 'device still locked' error. This is getting out of hand! Thanks so much for your advice. You think I should open it up?

I hate to be so persistently annoying about this, but could anyone possibly suggest a method of working around the locked bootloader?
Is there anything I can do with an SD card to remedy the device's stubborn foolery?

I think you should give it a try, I have bricked my xoom a few times and have always been able to flash the stock imagine to recover. You really have nothing to lose by pulling the battery pin just be careful.
Sent from my Xoom using xda premium

I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?

cherlamperter said:
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
Click to expand...
Click to collapse
I have looking for a utube how to guide but no luck, I just might make one for you so you will know what to expect. Give me a few and I will get back to ya.
Sent from my Xoom using xda premium

Problem after unlocking bootloader - Bricked?

Hey guys, how are you?
Well, I wished to root my Moto G, so I (tryed?) to unlock the bootloader. Alright, done it, but then I ran into some trouble...
After the booting up, everything started forceclosing and since then, when I try to boot it, I get a black screen after the Motorola logo.
Now, I am really really worried about my phone. I got it a month ago. I'm so afraid I really f****d up my phone right now that my hands are shaking.
I'm new to Android, so sorry if the solution is pretty obvious. And if it's not, could explain it very carefully to me? I don't know what to do.
My best wishes to you, guys.

I'm assuming you used superboot if so that would happen.
The logo sort of blured out right just press volume down and power and it would work
Or did this happen when you were just trying to unlock bootloader?

TomGlass1 said:
I'm assuming you used superboot if so that would happen.
The logo sort of blured out right just press volume down and power and it would work
Or did this happen when you were just trying to unlock bootloader?
Click to expand...
Click to collapse
Yeah, that happenned when I was trying to unlcok bootloader.
And well, my computer now doesn't even recognizes my phone.
EDIT: It appears as "Fastboot falcon S" in the Device Manager. Tried installing some drivers I found in the Internet, but it didn't work.

Explain exactly what happened please. Was the unlock successful and did you just bootup normally after or did u do anything else in fastboot mode? Why are you trying to install fastboot drivers again, as you already wouldve had them to unlock the bootloader. Did you try installing recovery or some root img from fastboot? You said its forceclosing, but it isnt starting at all now?
Some things you can do right now (if your bootloader is unlocked) is to flash a recovery (twrp,cwm) through fastboot and if you think most system files (or settings) are beyond repair, flash your firmware version though fastboot. Will point you to the guides for them, but post more info if you want help.

hemanthmahesh said:
Explain exactly what happened please. Was the unlock successful and did you just bootup normally after or did u do anything else in fastboot mode? Why are you trying to install fastboot drivers again, as you already wouldve had them to unlock the bootloader. Did you try installing recovery or some root img from fastboot? You said its forceclosing, but it isnt starting at all now?
Some things you can do right now (if your bootloader is unlocked) is to flash a recovery (twrp,cwm) through fastboot and if you think most system files (or settings) are beyond repair, flash your firmware version though fastboot. Will point you to the guides for them, but post more info if you want help.
Click to expand...
Click to collapse
Alright, just after I unlocked, when I was booting, I got a message saying that "xxxx has stopped working/failed to initialize/something like that". And then, when I rebooted, I got the usual message of the "bootlocker has been unlocked". After that, the Motorola logo started animating, but then I just got a black screen. I can't turn it off and the battery just got depleted (I'm charging right now).
When I try to connect it in my computer, the PC recognizes it as "MTP Device" or "Fastboot falcon S" when fastbooted. I can't install any drivers and the Motorola Device Manager doesn't recognizes it either.
Well, if there is some missing information, just ask me. I tried to describe my problem the best I could. Anyway, sorry for my bad English and thanks in advance for any effort trying to discover what's wrong.

Motorola Device Manager isn't helpful in this state as it doesn't handle things in fastboot. You already have all the required drivers (fastboot falcon S is the right driver afaik, falcon being motog codename) for flashing your stock firmware.
1. First, you can try the "Factory" option in bootloader (the third one, use volume down to move selector, volume up to select), though this might not really work for major issues.
2. When in fastboot mode, use "fastboot getvar all" to get the firmware details if you already didn't know about it.
3. Otherwise if yours is a standard gsm (non dualsim/non cdma), just download Blur_Version.174.44.9.falcon_umts.Retail.en.GB (UK stock for gsm, 4.4.2)
Download the mfastboot files to use rather than fastboot for flashing. You might need to modify your commands a bit for various firmwares.
http://forum.xda-developers.com/showthread.php?p=47820707 (refer this thread for flashing your stock firmware)
All the firmwares are in either of the links below (all around 400mb):
http://sbf.droid-developers.org/phone.php?device=14
(or)
http://www.filefactory.com/folder/c6cdedc45a775d27
I still don't get why many ppl are getting these errors after unlocking, very bad unlock method of moto if so ( I didnt get any such issues though).

When I use the "fastboot getvar all" command, it says "waiting for device". The phone is already connected, but the Moto G doesn't recognizes it's connected either.
I'm getting more and more afraid I really hardbricked it.

http://www.mymotocast.com/download/MDM?platform=windows
Tried installing these drivers? Your fastboot doesn't seem to be setup properly. How did you unlock without a working fastboot driver? You are trying that command in bootloader mode right?

Already installed it from the start. The message I got is always this:
"There aren't any updates for your device at the moment
Current Version: N/A"
My fastboot: Doesn't matter the operation I do, I always get this <waiting for device> and the phone is already connected into the computer. And the phone doesn't recognizes it is connected too.
And greeeeat news: my phone now doesn't charges either. I get stuck on a screen with a battery logo and 0%, when connected to the charger. Still, I still can access the fastboot mode. Well, am I lucky or not?

I'm pretty confused with this. How exactly did you unlock without a working fastboot (no waiting for device issue)? Did you change your pc drivers after unlock or trying this from a different pc? When you say "phone doesn't recognizes it is connected" you mean it says "Connect USB data cable" below "Device is UNLOCKED"? If so, maybe try another usb port cause it should normally say "Transfer Mode: USB Connected" regardless of proper drivers.
Your phone will chrarge no matter what though, no worry about that. It needs to say "Battery OK (Charging)" when connected to PC
No, as long as you have working your device isn't technically bricked in any sense. Don't worry, get that fastboot working again and anything can be fixed.
Also you didnt say whether or not you tried that "Factory" option in bootloader!

hemanthmahesh said:
I'm pretty confused with this. How exactly did you unlock without a working fastboot (no waiting for device issue)? Did you change your pc drivers after unlock or trying this from a different pc? When you say "phone doesn't recognizes it is connected" you mean it says "Connect USB data cable" below "Device is UNLOCKED"? If so, maybe try another usb port cause it should normally say "Transfer Mode: USB Connected" regardless of proper drivers.
Your phone will chrarge no matter what though, no worry about that. It needs to say "Battery OK (Charging)" when connected to PC
No, as long as you have working your device isn't technically bricked in any sense. Don't worry, get that fastboot working again and anything can be fixed.
Also you didnt say whether or not you tried that "Factory" option in bootloader!
Click to expand...
Click to collapse
OMG. I tried that "Factory" option before but it didn't work. Now I tried a second time and it worked. Thanks a lot! Really :laugh:
Anyway, now my phone is back again and rooted. Thanks for the help, guys!

Thaiane said:
Already installed it from the start. The message I got is always this:
"There aren't any updates for your device at the moment
Current Version: N/A"
My fastboot: Doesn't matter the operation I do, I always get this <waiting for device> and the phone is already connected into the computer. And the phone doesn't recognizes it is connected too.
And greeeeat news: my phone now doesn't charges either. I get stuck on a screen with a battery logo and 0%, when connected to the charger. Still, I still can access the fastboot mode. Well, am I lucky or not?
Click to expand...
Click to collapse
Guys the problem occurs due to corruption of /data folder. Even I had the same issue.
What you can do is
1. Connect your phone to PC in fastboot mode.
2. In fastboot, enter the command "adb erase userdata" and "adb erase cache" without quotes and reboot you phone. It will work for most of the devices, if it doesn't I have some other workaround too.

help
forgotter said:
Guys the problem occurs due to corruption of /data folder. Even I had the same issue.
What you can do is
1. Connect your phone to PC in fastboot mode.
2. In fastboot, enter the command "adb erase userdata" and "adb erase cache" without quotes and reboot you phone. It will work for most of the devices, if it doesn't I have some other workaround too.
Click to expand...
Click to collapse
I have the same problem. my phone stuck in blank screen after Unlock Bootloader. and then I try to do "adb erase userdata" and "adb erase cache". but my phone has no chenge, still stuck in.
I attach log when enter command adb above.
I'm sorry before. I can't spech English well

jidurrr said:
I have the same problem. my phone stuck in blank screen after Unlock Bootloader. and then I try to do "adb erase userdata" and "adb erase cache". but my phone has no chenge, still stuck in.
I attach log when enter command adb above.
I'm sorry before. I can't spech English well
Click to expand...
Click to collapse
The log you have posted contains only the help commands of adb and not the actual commands you gave.
Give a try to factory reset from fastboot mode on your phone. And do you a custom recovery installed in your phone?

forgotter said:
The log you have posted contains only the help commands of adb and not the actual commands you gave.
Give a try to factory reset from fastboot mode on your phone. And do you a custom recovery installed in your phone?
Click to expand...
Click to collapse
I've tried factory reset for several times, but no change as well.
yes, I get a CWM in my phone. and then, what have I do?

jidurrr said:
I've tried factory reset for several times, but no change as well.
yes, I get a CWM in my phone. and then, what have I do?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2704207
Go to the above forum.
Sorry for late reply was busy with studies.

I had flash stock firmware
through PC