Xoom won't do.... Anything

Discussion in 'Motorola Xoom' started by ldeezy80, Jun 27, 2013.

  1. ldeezy80

    ldeezy80 New Member

    Joined:
    May 22, 2013
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Could this be because I never had a chance to enable USB debugging? Wouldn't have a clue how to fix that now

    Sent from my Inspire™ 4G With Beats Audio using Xparent BlueTapatalk 2
     
  2. tcrews

    tcrews Premium Member
    Premium Member Developer

    Joined:
    Jan 27, 2010
    Messages:
    1,353
    Likes Received:
    22
    Trophy Points:
    53
    Location:
    Lexington, SC
    Ratings:
    +22
    Nope, that only has to do with the tablet actually booted and running the OS.

    Try updating your USB drivers with the latest from Motorola. If you can't talk to it in fastboot mode...that is most likely your problem.

    You really need to be looking at fastboot as what is going to save you....

    Sent from my Nexus 10 using Tapatalk 2
     
  3. ldeezy80

    ldeezy80 New Member

    Joined:
    May 22, 2013
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    So you seem confident there's a fix, no? I read somewhere xoom's were terribly hard to brick, but I thought I did it. I will try the drivers. Does it make sense that the drivers work for rsd and install when I plug in USB in rsd while in my computer, though? Obv I'm no expert, I just kinda assumed if the driver was working it was working. Ok...heeere we go

    Sent from my Inspire™ 4G With Beats Audio using Xparent BlueTapatalk 2
     
  4. ldeezy80

    ldeezy80 New Member

    Joined:
    May 22, 2013
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Damn. Strike 15. Updated to latest USB drivers (which I think I already had bc it only gave repair and remove options) I repaired and no dice. Fastboot won't work. Agggg

    Worth uninstalling then reinstalling? Motorola device mgr 2.3.9

    Also, when I check devices the xoom is only recognized as an "s flash" in rsd mode. Doesn't recognize any drives or files

    Sent from my Inspire™ 4G With Beats Audio using Xparent BlueTapatalk 2
     
    #16 ldeezy80, Jun 28, 2013
    Last edited: Jun 28, 2013
  5. tcrews

    tcrews Premium Member
    Premium Member Developer

    Joined:
    Jan 27, 2010
    Messages:
    1,353
    Likes Received:
    22
    Trophy Points:
    53
    Location:
    Lexington, SC
    Ratings:
    +22
    Are you booting to fastboot protocol mode and letting windows detect the device in that mode before trying to fastboot? What fastboot files are you using?

    If booting to fastboot and windows has detected...what kind of errors are you getting? Try fast boot OEM unlock and let me know the results.....

    If it boots to the logo, it is repairable.

    Sent from my Nexus 10 using Tapatalk 2
     
  6. ldeezy80

    ldeezy80 New Member

    Joined:
    May 22, 2013
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Absolutely booting to fastboot before attempting any cmds. When you say what fastboot files ya kinda list me...the SDK bundle?

    No errors. Just no response. I will try OEM unlock again right now .

    Nothing.

    [​IMG]

    What's next? Lol. Thank you very much again

    Sent from my Inspire™ 4G With Beats Audio using Xparent BlueTapatalk 2
     
    #18 ldeezy80, Jun 28, 2013
    Last edited: Jun 28, 2013
  7. ldeezy80

    ldeezy80 New Member

    Joined:
    May 22, 2013
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Only screens I can access

    [​IMG]

    [​IMG]

    [​IMG]

    Sent from my Inspire™ 4G With Beats Audio using Xparent BlueTapatalk 2
     
  8. tcrews

    tcrews Premium Member
    Premium Member Developer

    Joined:
    Jan 27, 2010
    Messages:
    1,353
    Likes Received:
    22
    Trophy Points:
    53
    Location:
    Lexington, SC
    Ratings:
    +22
    Fastboot files would be the files to flash to the device. You would have to download them from Motorola. Should be a system.img, a boot.img, a recovery.img and a user.img.

    Put them in the same location fastboot is located to make it easier. If you don't have them....you'll need to find them and/or ask around for them. Unfortunately when I sold my Xoom I deleted the ones I had downloaded. I looked earlier on Motorola's site and couldn't find them...as well, links I had to them no longer work.

    That's one reason I suggested trying to flash the recovery.img file I linked in earlier an posting, it would allow you to install CM10.1 or EOS, etc...Roms if you can't find the stock one.

    Try the fastboot OEM unlock and then the fastboot the recovery as stated above.

    Sent from my Nexus 10 using Tapatalk 2
     
  9. ldeezy80

    ldeezy80 New Member

    Joined:
    May 22, 2013
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Ok. Btw...when stuck in waitingfor device what's the best way to cancel out?
    Sent from my Inspire™ 4G With Beats Audio using Xparent BlueTapatalk 2
     
  10. ldeezy80

    ldeezy80 New Member

    Joined:
    May 22, 2013
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
  11. tcrews

    tcrews Premium Member
    Premium Member Developer

    Joined:
    Jan 27, 2010
    Messages:
    1,353
    Likes Received:
    22
    Trophy Points:
    53
    Location:
    Lexington, SC
    Ratings:
    +22
    Very weird...

    When you do the fastboot oem unlock, what are you getting on the Xoom's display? Since you are getting the "waiting on device", either your computer is not talking to the Xoom or the Xoom hasn't properly initialized the Fastboot protocol boot sequence.

    I downloaded the file you linked....once I was approved....and opened the zip up....it's the correct files for the original OS (OS 3.0 and then it'll update all the way to 4.1.2, one update at a time...). You should be extracting those to the same location fastboot.exe sits so you have fastboot.exe, system.img, boot.img, recovery.img and userdata.img all in the same folder and run the commands from a DOS prompt at that directory...

    You could try RSDlite again with this file, http://sbfdownload.droid-developers.org/everest/VZW_MZ604_signed_JZO54K.combo.sbf.gz
     
  12. ldeezy80

    ldeezy80 New Member

    Joined:
    May 22, 2013
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Sorry for taking so long to respond. Xoom is still useless, as far as I can tell. TC I tried to rsd with that file in your last post, same old crap. Gets stuck on either "switching to bp/lte pass through", or one other message like "Jump to RDL" or something. First rsd will create an image file and once that's at 100% it says "device renumeration" and reboots. When rebooting I tried to hold the button to get back to rsd protocol as well as just let it run. Fail every time and every file. Recovery will not boot and fast boot commands are ignored . I did ALOT of reading for potential solutions and some said holding down for 20 seconf s when rebooting will get fast boot to be recognized.... Not for me. All fast boot commands stick on waiting for device.

    Any other options? TC I remember you saying if I get to red M its likely salvageable, what would you do next?

    Thanks again.

    Sent from my Desire HD using Xparent Green Tapatalk 2
     
Search tags for this page
cannot do recovery on xoom
,
fix a xoom that wont power on
,
motorola xoom wont do anything
,
motorolla xoom wont turnon or off stuck protocal
,
resetting xoom says bp failed
,

wingray 4.3

,
xoom 2 wont power down
,

xoom boot options

,
xoomwon't boot
,

xoom wont turn on