Wingray - Internal Storage has been wiped, and I'm out of my depth.
My friend gave me his bricked Xoom, which I accepted as a challenge, because I've been rooting and flashing my phones for years, but after 10+ hours of searching in the last couple weeks, I have been unable to locate coherent information on how to un-brick a Xoom that has had its internal storage wiped. My friend was trying to do a thorough wipe, and he succeeded in that, if nothing else.
My first obstacle was finding a driver, because Motorola Device Manager wants nothing to do with the Xoom, and whenever I finally found a link to a driver, it was at developer.motorola.com, and there apparently is no such domain, because every link takes me straight to motorola.com/us/home, where all that's waiting for me is the bloody Moto Device Manager.
The only post I found that seemed like it was aiming at where I want to get is at http://forum.xda-developers.com/show....php?t=2317986
, but I ran into problems that weren't foreseen by the author, and I haven't been able to find anything pertinent that doesn't direct me to developer.motorola.com again.
The Xoom has TWRP v.184.108.40.206(runandhide05 edition) for a recovery; and I'm aware that there is a 3.3 version, but I'm nervous about flashing a recovery update when there is no OS on the tablet. It was running EOS 4.2.2 I think, before the bricking.
According to the guide I found, I put TWRP into adb sideload and was able to get my PC to communicate by installing a universal adb driver from https://github.com/koush/UniversalAdbDriver
, so in my system Device Manager, the Xoom is listed as a GOOGLE GALAXY NEXUS ADB INTERFACE.
When TWRP is in adb sideload, I can interface with the Xoom via cmd.exe, but when I try to push a ROM, I keep getting an error on TWRP:
file_getprop:failed to stat "/system/build.prop" no such file or directory
...whatever that means. Another thing that kind of worries me is that when I type adb devices, it shows my device as 1234567890ABCDEF, which doesn't seem right.
I have yet to try fastboot, because I don't know what .img files I need to flash, and I don't think blind flashing is going to make things any better.
I think I have all the pieces, SDK and JDK are installed and updated, and I have the stock rom (HWI69.zip). I reckon if I can get the stock 3.x OS running, I'll have a jumping-off point, and be good to go; the process from there is well-documented.
Can anyone give me a nudge in the right direction, please?