Database Info

Another Bricked Xoom in Dual Core Screen Please advice

hi guys, so I stomped my dads xoom while cleaning and I remembered I was not able to unbrick it, and out of nostalgia wanted to try again. I have read a lot of similar posts and guides still I have not been hable to unbrick this one.
Specs: Motorola Xoom Wifi Only Mz604 sd card missing (Ill buy one tomorrow)
Bootloader Version (According to RSD Lite) :0vx001045
Background: The tablet got bricked while the process of changing "stuff" (its been some years dont quite remember) I remember we got the gpu overclocked and was running a CFW stingray I believe.
Present Situation:
The tablet turns on and goes to "starting RSD Mode 3" at the dual core logo. and just stays there. Funny enough the computer does the dong but its unable to recognize the tablet in device manager. My computer does have Motorola device manager and Motorola Mobile Drivers v6.4.0_64bit.
IF I reset the tablet with "Power & Vol+" resets, but goes back to rsd mode 3
IF I reset the tablet with "Power & Vol+" and do "Vol-" after wards , it stays at Dual Core Logo, but no RSD mode or fastboot or abd. Just plain logo.
IF I reset the tablet with "Power & Vol+" and do "Vol-" While trying "fastboot flash boot boot.img" It gives me waiting for device prompt
At this point I downloaded RSD lite 5.6.4 but it didnt detect my tablet. So I kept digging until I found a thread about a factory Micro usb cable created by bridgeing pin 1 & 4 and BINGO. RSD lite detected my tablet.
Now I have downladed 3 Sbf hoping one will work:
"HUBWF_W5.H.6.4-20_SIGNED_UCAHUBU01SPLAWIFI_P010_A007_M006_HWwifi_hubble_AP1FF.sbf"
"HUBWF_W5.H.6.4-20_SIGNED_UCAHUBU01SPLAWIFI_P010_A007_M006_HWwifi_hubble_Service1FF.sbf"
"HUBWF_W5.H.6.6-27_SIGNED_UCAHUBU01SPLAWIFI_P011_A009_M007_HWwifi_hubble_Service1FF.sbf"
Here is the catch, rsd unzips , re-enumerates and makes the tablet Reboot executes around 3% , then generates an error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is as far as I've gotten the sbr files have been hard to get (most links broken). I feel Im at brink of getting it done. I believe the error has to do with the tablet not rebooting in rsd mode, it reboots to the plan back screen with dual core logo .
Any ideas? thanks in advance

any advice? anyone??
here is the log of the rsd lite flashing.
02/21/16 22:51:24 00002244 Phone.cpp 514 0 ERROR Generic failure when sending command.
02/21/16 22:51:24 00002244 Phone.cpp 1655 0 ERROR GetPhoneID failed: ERROR.
02/21/16 22:51:24 00002244 Phone.cpp 514 0 ERROR Generic failure when sending command.
02/21/16 22:51:24 00002244 Phone.cpp 1655 0 ERROR GetPhoneID failed: ERROR.
02/21/16 22:51:24 00002244 Phone.cpp 514 0 ERROR Generic failure when sending command.
02/21/16 22:51:24 00002244 Phone.cpp 1750 0 ERROR GetTechnology failed: ERROR.
02/21/16 22:51:24 00002244 Phone.cpp 514 0 ERROR Generic failure when sending command.
02/21/16 22:51:24 00002244 Phone.cpp 1819 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
02/21/16 22:51:24 00002244 Phone.cpp 514 0 ERROR Generic failure when sending command.
02/21/16 22:51:24 00002244 Phone.cpp 1977 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
02/21/16 22:51:24 00002244 Phone.cpp 514 0 ERROR Generic failure when sending command.
02/21/16 22:51:24 00002244 Phone.cpp 1866 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
02/21/16 22:51:40 The FlashLog key is turned off.
02/21/16 22:51:40 Multi upgrade started for 1 phones
02/21/16 22:51:40 [Device ID: 0] Flashing phone.
02/21/16 22:51:49 ERROR: Interface AP-OS: Error flashing subscriber unit. Device API Error: 0xE0020085 Address: 0x1F870 Command: ADDR - on device ID 0.
02/21/16 22:51:49 ERROR: Flash failure: Interface AP-OS: Error flashing subscriber unit. Device API Error: 0xE0020085 Address: 0x1F870 Command: ADDR (Error Code: e0020085),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=3 - on device ID 0.
02/21/16 22:51:49 [Device ID: 0] Interface AP-OS: Error flashing subscriber unit. Device API Error: 0xE0020085 Address: 0x1F870 Command: ADDR
02/21/16 22:51:49 ERROR: Failed flashing process. - on device ID 0.
02/21/16 22:51:50 Multi upgrade finished.

This MZ604 is from what region?
The 3 sbf files you download are for brazil and south america

Sad android...maybe paranoid

INITIAL COMMUNIQUE:
...
"Samsung GALAXY CORE Prime"
("POWERED by android")
"metroPCS" ("t-mobile network")
"bong bong bong laa laa"
"buzz-buzz-buzz buzzzzzz"
(via usb cable to slackware--porteus variant: "Unable to open MTP device '[usb:001,013]'")
"buzz-buzz-buzz buzzzzzz"
("Unable to open MTP device '[usb:001,014]'")
"buzz-buzz-buzz buzzzzzz"
("Unable to open MTP device '[usb:001,015]'")
"buzz-buzz-buzz buzzzzzz"
("Unable to open MTP device '[usb:001,016]'")
"buzz-buzz-buzz" ...
...
System Recovery <3rd edition?> (up vol+pwr+home) appears normal for an os 5.1.1 Android.
(note: subject does not appreciate being called a "lollipop")
TRANSLATORS NOTES:
Android SM-G360T1, lmy47x.g360t1uvu1aofa, (unique s/n classified) not responding to Heimdall protocol...
Dreams of Replicant status wanning...
Suspect it (she?) is showing early stages of depression...
Z768G not so jealous now...suspect foul play ... >.> ... <.< ...
---
Heimdall output:
Code:
[email protected]:/mnt/sda3/.../prime# heimdall flash --RECOVERY /mnt/sda3/.../prime/TWRP/recovery.img --verbose
it's 3.0.2.0 i think
Code:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
www glassechidna com au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
www glassechidna com au/donate
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
[email protected]:/mnt/sda3/.../prime#
...
worth noting:
Code:
Manufacturer: "Sasmsung"
S/N: 0
Code:
ERROR: libusb...
Code:
MTP device '[usb:...
Code:
gingerbread man in spotlight...again...
...
any helpful tips for a more fruitful communication with this 'droid?

SM-G900W8 Heimdall Print-Pit error

when i follow the steps to load lineage from the lineage wiki and I get to the heimdall part where I type heimdall print-pit i get the following error:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
what can i do with this to fix it? Do i need to unlock the phone first? Has anyone had any success with this phone and loading lineage on it?

Samsung Tab E cannot download stock rom

After I attempt to flash a stock ROM through download mode on Samsung Tab E, Heimdall outputs this error when its 4% done:
Code:
Uploading SYSTEM
4%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: SYSTEM upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
Is this a problem with the storage?

Try using odin

ERROR: Phone[0000]: Phone did not re-enumerate after RAM-downloader was sent.

How do i fix this in RSD lite thanks!!
ERROR: Phone[0000]: Phone did not re-enumerate after RAM-downloader was sent.
i have no clue i'm flashing stock firmware on motorola device