yashsingh1/xdaforums huggingface dataset:
[Xoom Q&A, Help & Troubleshooting] aussois:
That's the thing - moto provides all the tools to relock for US ONLY! There is no official way for canadians, which makes no sense. So us canadians can unlock no problem, but cannot relock, yet US units can? Strange to me...
[Xoom Q&A, Help & Troubleshooting] csseale:
Try rsdlite 4.9 or earlier it should see it then.
[Xoom Q&A, Help & Troubleshooting] footboydog:
I tried RSD 4.9 and no luck. I think it just doesn't work with Wi-Fi only zooms.
[Xoom Q&A, Help & Troubleshooting] crushsuitandtie:
Anyone who locked the zoom back and now can't boot, try my instructions from another thread...

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.
[Xoom Q&A, Help & Troubleshooting] footboydog:
I have just tried this and still no luck. Fastboot just sits there with the "waiting for device" message and the Xoom just boots with the "Starting RSD mode 2" message. I also tried your suggestion with rebooting into fastboot mode by holding the vol down button and that doesn't work either.

BTW I don't have a custom boot.img. I am on a stock ROM but I just had the bootloader unlocked.

Incidentally I have tried RSD lite 4.8, 4.9 and 5.0 now and none work.
[Xoom Q&A, Help & Troubleshooting] eurodj:
IM on the same boat!!!!Stupid me tried to unroot i don't know what i was thinking!!!!!!!!!!!! Anyone know if there is anything we can try i live outside the U.S and purchased it on amazon while in the U.S and dont have the box anymore so i can find out my serial nor mac address!!!
[Xoom Q&A, Help & Troubleshooting] crushsuitandtie:
The only reason you should be getting this is because you re-locked it with a custom kernel or root capable boot.img. The lock will take hold but the boot can't go through with a custom kernel. Your focus should be just re-unlocking it first.

I accidently did the same thing. All i had to do was type fastboot oem unlock, and while it says "waiting for device", reset the xoom while plugged in. It intercepted mine before the error and sent me back to the unlock screen on the xoom. Sorry this did not help you, as it did me.
[Xoom Q&A, Help & Troubleshooting] footboydog:
I flashed back to the stock Canadian ROM before all this so I don't see how it's got itself into this state. Unless it's because I have a UK Xoom and it doesn't like the Canadian ROM (stock UK ROM is not available or at least wasn't at the time).

Do you have a 3G Xoom or Wi-fi only?

BTW Motorola UK support have replied and said a repair would be out of warranty as I unlocked. I asked them how much it would cost.
[Xoom Q&A, Help & Troubleshooting] eurodj:
How much did they say it was?
[Xoom Q&A, Help & Troubleshooting] footboydog:
I asked but their reply was "We would like to inform you that we will escalate your case to another department" so I'm still waiting to find out.
[Xoom Q&A, Help & Troubleshooting] pocharlies:
i'm in the same situation.

Motorola spain doesn't repair my xoom. with motorola eu, i need to send it, it cost more than 200$... no way.

i have the rsd mode 2 active all the time and i try to install rsdlite 5.0 4.9 4.8, formating windows, i try with 10 diferent computer in the work, ubuntu x64, 86_64, windows 7, vista, xp 32/64 bits, without nothing.

I'm trying to rebooting while fastboot iw <waiting for device> but computer never detects the motorola xoom.

the most strange is that i instal stock boot.img, and system.img but in didn't flash recovery.img stock and i lock the tablet "i don't know why i'm like retard locking it".

My only way is pay around 200$ and wait 1 month or more to use it...

it doesn't have any sense. i'm really disapointed with motorola. no sdcard support, no international support, no update support, no "panic mode" support.

we can do a post to list the possible fixes about this problem and the diferent cases.

i have another motorola xoom "my father's xoom" and rsdlite detects it inmediately when i turn on in rsd mode.

anyone can explain exactly how fastboot detects his computer?

when i plug it in ubuntu, and i try lsusb to find if motorola's plugin some usb conection, it doesn't send nothing...

if someone can help me, i'll pay with paypal. please help me! :P
[Xoom Q&A, Help & Troubleshooting] sirtoast:
damnit, i'm in the same boat. Bought a Xoom Wifi in the Florida while on vacation, and brought it back to Canada. Like almost everyone else, I'm hung at <waiting for device>.

I feel so goddamn stupid for not being willing to wait a couple days for 3.1
[Xoom Q&A, Help & Troubleshooting] ydaraishy:
What Canadian ROM? There's no Canadian images released by Motorola (see http://moto.ly/xoomsoftware).

Sounds like that's your problem.
[Xoom Q&A, Help & Troubleshooting] sirtoast:
Just called Motorola, and am sending the xoom in for service. wish me luck:)
[Xoom Q&A, Help & Troubleshooting] dirtymindedx:
I can fix your xoom no cost using teamviewer. already fixed 5 of these on xoomforums takes maybe 15 minutes to restore to factory setting. I am talking about the xoom USA 3g or wifi.
[Xoom Q&A, Help & Troubleshooting] dirtymindedx:
ok try this

if starting fastboot is on your xoom screen open up a command prompt:

1. with the command prompt open type: cd "replace with tools directory location"

2. disconnect your xoom from your computer and shut off the xoom

3. at the prompt type: fastboot oem unlock

4. it will say waiting for device

5. now plug it into your computer and reboot into fastboot

6. follow the on screen instructions and agree to everything

7. your device will reboot you will get the motorola dual core window

8. force restart device and go back to fastboot

9. you can now goto: MOTODEV > Products > Device Software

10. signup and download the files you need

11. extract all the img's into the tools folder

12. then copy each line one by one into the command window. This will allow you to go back to factory settings like you bought it from the store

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

no more $600 brick!

If this works hit the thank you button my meter looks lonely.
[Xoom Q&A, Help & Troubleshooting] sirtoast:
can't get to step 6. I've unplugged the xoom, restarted and tried to connect it with different type of timing. xoom stays at "Starting Fastboot Protocol support." and the command prompt on the pc stays at waiting for device :(
[Xoom Q&A, Help & Troubleshooting] dirtymindedx:
once you reboot after oem unlock you dont have to unplug the xoom just reboot in fastboot
[Xoom Q&A, Help & Troubleshooting] sirtoast:
Just tried that, no change. tried it on 3 different usb ports.

just for reference, fastboot/adb was working 3 hours ago, up to the point where I bricked the device
[Xoom Q&A, Help & Troubleshooting] eurodj:
Same here can't do fastboot if i could i would've fixed it using one of the threads on here!!!It just stay in the starting fastboot protocol line
[Xoom Q&A, Help & Troubleshooting] dirtymindedx:
install teamviewer and send me a PM with the ID and password I will be on this till 10pm so if anyone wants me to fix it let me know.
[Xoom Q&A, Help & Troubleshooting] sirtoast:
pm sent, hope this works:)
[Xoom Q&A, Help & Troubleshooting] Hexbug:
When I got stuck at <waiting for device> I just turned it off via the power button, and then back on again. It booted into fastboot and went on its merry way... doing what it was supposed to. So maybe you could give that a try.. ?
[Xoom Q&A, Help & Troubleshooting] sirtoast:
i'm not able to shut the xoom off at all, can only reboot to the Dual Core logo
[Xoom Q&A, Help & Troubleshooting] eurodj:
let me know if it works!!!!!I got dibs on next!!
[Xoom Q&A, Help & Troubleshooting] sirtoast:
I haven't heard from him, not sure if my PMs are getting through to him. Hope I wasn' too late to get him for teamviewer
[Xoom Q&A, Help & Troubleshooting] eurodj:
BTW i cant turn mine off either
[Xoom Q&A, Help & Troubleshooting] eurodj:
I sent him my info too!! Of course we dont know what time zone he is on either!
[Xoom Q&A, Help & Troubleshooting] sirtoast:
My kudos go to Dirtymindedx. He wasn't able to get my device working, but went through a lot of work, and tested it on 2 of my PCs to cover all bases. At least now, when I send it in to Motorola tomorrow morning for repair/replace, I'll know that I did everything that I could.

My warning to everyone is, if you're on a Wifi Xoom, beware the one click root.

Will let you know what happens with motorola as I find out more.
[Xoom Q&A, Help & Troubleshooting] eurodj:
Same here let me know cause ill be sending mine in also!!
[Xoom Q&A, Help & Troubleshooting] dirtymindedx:
they should ban the one click unroot portion of the program it seems to be botching up the fastboot options. Please just take the time to learn how these things work the quick way doesnt always mean its better.
[Xoom Q&A, Help & Troubleshooting] chaz03:
Hey everyone, I started the thread here. From my knowledge this "condition" or "state" of the device is a true BRICK. As far as this moment, there is no known fix procedure that we as xoom owners are able to do. RSD has no recognition of the device. No adb commands. Fastboot is junked. The device would most likely need some sort of hardware replacememt or a new RSD that would somehow pick the device up in thie state that its in. And yes you can not turn the device fully off. There are no other options to select other than rsd mode and Fastboot protocol. and well....dead. I've never actually had the privledge to hold a true Bricked device until this happened. so I did the usual and hit up motorola support. I filed a repair order online. Then called up a rep to clarify some thing and the situation. I was honest with him and told him I understand the voiding in warranty when i unlocked the bootloader. Trust me i did not want to tell this guy any of this. But idid any i think my honesty paid off. I dont know if this is the typical situation for many where motorola states they will cover the device repair under warranty, buyt they did for me. Freakin awesome delivery time. Ask you to write a brief explanation of what happened to the device. It took 2 days for everything to get me back to ground zero with a fresh new xoom. Best of luck to you guys. I was in a mad anger fit after this all happened. But anyway i posted on motorola support forums as well an you can pick some info up there as well. Hope someone could find a fix for this!
[Xoom Q&A, Help & Troubleshooting] dirtymindedx:
honestly there are ways to fix these issues but it depends on what is affected in the actions taken by the user. This week I have repaired plenty of xooms in xoomforums with similar issues. Sounds like files were inproperly written to the xoom in every instance when trying to unroot the device. Everyone is trying to get their hands on the 3.1 update but if you wait for the community they will come through almost 100% of the time and within 2 days from the release the hack came out using clockwork. dont take shortcuts quick root is great when the device has been out a year but this is a new device and people are still learning from their mistakes please dont take shortcuts with your 600 dollar devices. take time and learn what things do and how they function.
[Xoom Q&A, Help & Troubleshooting] bwcorvus:
Just had this happen 2 times. All I did to recover was boot while holding power and volume down. Do not let then go until it says fastboot on the xoom, then fastboot oem unlock.

Sent From My Evo
[Xoom Q&A, Help & Troubleshooting] footboydog:
I got them from this thread. I realise now that it says "I wouldn't try OEM locking with these". :(.

@chaz03, interesting they will fix yours under warranty. I will raise this with Motorola UK when they tell me how much it will cost to repair out of warranty.

BTW I don't think I mentioned that mine says 0x0004 instead of 0x0002 in the error message. It also shows the error above the "Starting fastboot protocol support" message when booting into fastboot. Maybe this is why I can't get my PC to see the Xoom then.
[Xoom Q&A, Help & Troubleshooting] DinarQ8:
i have same problem i don't now whats i do :(

my PC can't see th xoom

i from kuwait i can't back the xoom to usa :(
[Xoom Q&A, Help & Troubleshooting] dirtymindedx:
ok hold down volume and power on your xoom

if you see starting fastboot then you may be fine

now open up a command line and change the directory to your tools directory

type: fastboot oem unlock

if it says waiting for device

force your device to reboot and

hold down volume and power on your xoom

if your command prompt still says waiting for device then its possible you have

super bricked your device and need to get it to motorola
[Xoom Q&A, Help & Troubleshooting] ghiggo:
I have the same problem on a Xoom wifi USA from Italy :-(
[Xoom Q&A, Help & Troubleshooting] csseale:
You need RSDLITE 4.9 or lower.

You need the newsest moto drivers from their site

You the the SBF file for your Xoom..wifi or 3g

Install rsdlite onto your puter.

Plug your Xoom into your puter.

Get it to the rsd mode 2 screen

Point rsd lite to the sbf file

Let it oush the file to your Xoom

It may say fail after a long time. Its OK just reboot and your running again.

The newest rsdlite 5 will not work has to be older to recognize the Xoom rsd mode 2

SBF is the only way. Sorry but yes it works many have tried and succeeded every time with this exact problem.

Edit.

Seems wifi doesn't have an SBF file floating around. Hmm..sorry. without the sbf this is a no...go...
[Xoom Q&A, Help & Troubleshooting] dirtymindedx:
i got a message from a user stating that they clicked on the 1 click root method and force reboot the xoom and it seemed to fix it. Its weird but hey anything is possible at this point.
[Xoom Q&A, Help & Troubleshooting] bwcorvus:
Actually it may work...flash the 3g sbf. It will softbrick you, but you will have fastboot back.

Sent From My Evo
[Xoom Q&A, Help & Troubleshooting] csseale:
Problem is even after that...THERE IS ABSOLUETLY NO WAY to relock the xoom. Even after you SBF or managed to get the moto files pushed if you try to OEM lock you get lxn mode 2 error...like to say watch Google movies...you can't. So for all of us who has received that error...we are Google movie screwed.
[Xoom Q&A, Help & Troubleshooting] bwcorvus:
I have relocked mine after receiving the error. I have relocked 5 times now, testing different things. I had 2 softbricks where i had the "failed image LNX 0x0002 / RSD mode 2" and recovered both times and have locked since then. Again to fix the error, all i did was hold both power and volume down for about 60 seconds while booting, i just didn't let go until it got to fastboot. I have locked 3.0.1 3 different times, and 3.1 bootloader with 3.0.1 images 2 times. I still trying to figure out how to get full 3.1 locked, but i have some ideas.
[Xoom Q&A, Help & Troubleshooting] csseale:
Mmmm I have tried multiple diffent ways when recovering and none has givin me back the ability to relock...

Edit.

Yea I am on 3.1
[Xoom Q&A, Help & Troubleshooting] bwcorvus:
Yea thats the key, if you flash back the stock 3.0.1 wifi images, you will be ok. It works fine with the 3.1 bootloader, but you have to follow the directions 100%. Anything that isn't right, will stop the boot.
[Xoom Q&A, Help & Troubleshooting] pocharlies:
i have the same problem and i can't send it to motorola, i'm from spain.

i'm starting in fastboot protocol support. and computer doesn't detect it never

just rebooting it, waiting 60 sec in fastboot protocol but is imposible

anyone can explainm exactly what can i do?

i'll be very gratefully or i'll lose my xoom forever..

pm me or say something plz!!
[Xoom Q&A, Help & Troubleshooting] footboydog:
Still no word from moto on cost of repair. I asked them for an update today and this was their reply:

"We would like to inform you that we will pass your case to our repair service department who will contact you backto give you an estimation of the quotes for this repair."

Not impressed :(
[Xoom Q&A, Help & Troubleshooting] sirtoast:
I'd prefer to NOT pay, but depending on how much it is, I'll likely take it on the chin. I just got notification that the Xoom had been delivered today, to the repair shop. We'll see what comes of it.
[Xoom Q&A, Help & Troubleshooting] footboydog:
It's been over a week since I asked Motorola how much the repair would be and still no answer. I asked them again yesterday and no response has come back at all.

This is really annoying. Users of my apps are asking for Honeycomb features and I can't test them without a tablet. The Android emulator is so slow its not worth bothering with.

Gonna try this tomorrow.
[Xoom Q&A, Help & Troubleshooting] footboydog:
Fixed!

Mwahahahahah! I followed the guide here to make a Motorola factory cable out of the micro USB cable that came with my Nexus S. After some delicate soldering I plugged it into my PC. Without pressing any buttons it booted straight away. My PC picked it up as a "Motorola Flash device" which meant that RSD lite could now detect it. I rebooted into fastboot mode and that was picked up also. I ran fastboot oem unlock and now it boots! Woot!
[Xoom Q&A, Help & Troubleshooting] eurodj:
Wish i wouldve read this again before i sent it in!!!!wouldve done the cable!!!!!Anywhows according to the service site my Xoom was repaired today so ill let you guys know when i get it back!!
[Xoom Q&A, Help & Troubleshooting] sirtoast:
I just got my xoom back this week, and they were able to re image it. I marked the microSD blank that comes in the slot, so I know I got the same device back (or they replaced the device but were cunning enough to also move the blank to the new unit.

Came back with 3.0.1, though, so I'm still waiting for the 3.1 update, which was behind this whole mess to begin with. Oh well:-)
[Xoom Q&A, Help & Troubleshooting] CompCrash:
When you sent yours in how long did it take to get it back?
[Xoom Q&A, Help & Troubleshooting] sirtoast:
I seem to recall it being just over a week, maybe 10 days at the most (that includes a holiday here in Canada). if I remember correctly, I expressed it to them on a Friday, so they rec'd it on Monday or Tuesday. I called on following Friday to see what the story was, and they said that it had just been given to Canada Post, and that I received it either Monday or Tuesday.

My memory is a little fuzzy about the timeframes, but I do know that it was surprisingly fast.
[Xoom Q&A, Help & Troubleshooting] CompCrash:
I just sent mine out today for the same problem. Since you had weekends in yours it shouldn't take as long. Thank you.
[Xoom Q&A, Help & Troubleshooting] sirtoast:
good luck, hope works out well for you.
[Xoom Q&A, Help & Troubleshooting] CompCrash:
So sent out the phone yesterday, and I will get it back tomorrow. That has to be the fastest turn around I have ever seen.
[Xoom Q&A, Help & Troubleshooting] digitalnerd:
a little help would be FANTASTIC!
[Xoom Q&A, Help & Troubleshooting] cruiseyunfat:
I'm having the same problem on my Xoom.

People here are confused with two different error:

The error of the subject is " Failed image LNX 0x0002/RSD mode 2"

This error the device does not pick up, cannot re-install drivers and flash.

The error everyone is suggesting fix is for " SOS 0x0002 failed image"

SOS failed image I have had before and can be fixed with the recommended tutorials that is found on the web.

LNX failed image is a bricked tablet. I have been trying to fix for sometime now and no one out there knows a fix. Better take it in.

Any help from anyone?
[Xperia Play General] Rixter757:
Hey all,

I can't post in the Development forum because I have too few posts, but I thought some may benefit from my experience based on questions I read in Bin4ry's Root your Play thread.

And before I begin - Thanks very much Bin4ry & lollylost100 :D

Before running Step 2 from Bin4ry's tutorial, you must run Step 8 from lollylost100's tutorial on bootloader unlocking, quote here:

8. Connect your phone in fastboot mode (turn phone off, hold "search" button and plug in USB Cable)

Once you run Step 2 from bin4ry's tutorial, the process can take a good 10 minutes - the DOS prompt just sits at the "sending system 236189kb" and it's tempting to cancel it thinking nothing is happening (I nearly did). Just wait. My speed was 300kb/s while I see others were much faster.

I also read comments from others in Bin4ry's thread that you need to download the Android Dev kit. This wasn't my experience. I was downloading these tools while my DOS prompt was stuck on "sending system..." and if they had have finished downloading first I would have probably guessed they were needed & cancelled the process to install the dev tools before re-running the patch.

I hope no-one thinks I'm nit picking what is a brilliant guide, more experienced peops won't need this but others might ;)

Rixter
[Xperia Play General] svenk919:
Could that speed be because you're on usb 1(.1)?

Also, it's never bad to help people ;)
[Xperia Play General] Rixter757:
Thanks svenk919,

No it's USB 2 ok, it just bottlenecks for no apparent reason sometimes. It's a laptop that only 9 mths old & I have it overclocked so it's pretty snappy ;)

Someone should sticky XQ55's post on the Dev forum that has all of our .apk's available for download - saved me a little hassle just now.

Rixter
[Captivate Q&A, Help & Troubleshooting] mwiz123:
So last night my phone bricked

Heres What I did

1. Flash Stock

2. Flashed http://xdaforums.com/showthread.php?t=952588

3. Got Tired of it...

4.Then Flashed http://xdaforums.com/showthread.php?t=1045734

5. Got Tired of this...

6. So insted of waisting time i went into recovery and flashedhttp://xdaforums.com/showthread.php?t=964583

7. After it finished I Flashed some GPS Fixes and deleted the battery stats

8. Then in recovery and rebooted my phone and it never came back on since

dose anyone know where i went on?

Ive tried http://www.addictivetips.com/mobile/how-to-unbrick-samsung-captivate/ and

http://xdaforums.com/showthread.php?t=775911

and even went to AT&T for help.

they said all it is is the battery but is it more then that?

I have read around and it said it corrupted my files is this perminante?
[Captivate Q&A, Help & Troubleshooting] TRusselo:
if it wont turn on. it is a hard brick. j-tag fix only.

congratulations! your phone is under 1 year old!

you have a warranty! Use it!.

Just say " It just stopped working "

if it cant turn on, they cant prove you wrong!

or get ahold of " mobiletech videos " he just got set up with jtag un-bricking. and the first people to test it out get it done for free!! shipping included!!
[Captivate Q&A, Help & Troubleshooting] BWolf56:
Just to add to your post;

If you get any sign of life (light, vibration or any kind of image) then it's not bricked all you'll need is a JIG (you can build one for very cheap).

If that's not the case.. Well back to Trusselo's post :rolleyes:
[Captivate Q&A, Help & Troubleshooting] mengbo:
my suggestion is to try this first:

http://cgi.ebay.com/ws/eBayISAPI.dl...21187&ssPageName=STRK:MESELX:IT#ht_651wt_1139
[Captivate Q&A, Help & Troubleshooting] mwiz123:
nope no signs of life none what so ever
[Captivate Q&A, Help & Troubleshooting] mwiz123:
how do i get hold and what is a J-Tag?