Could use some help with a potential brick

[madmaverickmatt]

Hey all. I have reached a defect in my research and I could use some help.

I have a Wifi Xoom that I fried the mother board on. Not sure how, just woke up one morn and it wouldn't turn on anymore.
So I replaced that MOBO with another that was listed as soft bricked (It was cheep so I figured why not try).

Anyway with the new board installed I can boot to the Motorola Logo, I can load fastboot, recovery and RSD. The device appears as it should on my pc and I can fastboot flash.

I replaced the system image, the recovery image, The userdata image and the boot image with the ones from the moto dev websight using fastboot. I also cleared cache, from fastboot and recovery as well as deleting all user data from recovery (Factory Reset).

I also re-installed the whole system using four different WIFI RSD Images which went successfully as well.

Now I know its actual flashing because I flashed a different recovery to test and that worked, but for some reason im stuck in a boot loop at the Motorola Logo. I can still access all features (fastboot, recovery and RSD) but it will not boot past the Moto Logo.

I have tried installing the 4.1.1 and 4.1.2 updates through recovery which both installed their updated boot loaders and for a moment I thought I had success when I saw the xoom boot image with the flashing squares, but then that froze and it rebooted never to be seen again.

So my question is, is this a hard brick and I should just stop trying or does anyone have any other suggestions?

Also I am using a Moto cable, it tells me that I am successfully flashing.

Everything I read thus far indicates that if you can access fastboot and recovery that its not hard bricked, but what exactly does a hard brick look like?

Thanks All any insight is appreciated.

p.s. I have relocked, unlocked, etc

[Ads]

[ggrant3876]

Hey all. I have reached a defect in my research and I could use some help.

I have a Wifi Xoom that I fried the mother board on. Not sure how, just woke up one morn and it wouldn't turn on anymore.
So I replaced that MOBO with another that was listed as soft bricked (It was cheep so I figured why not try).

Anyway with the new board installed I can boot to the Motorola Logo, I can load fastboot, recovery and RSD. The device appears as it should on my pc and I can fastboot flash.

I replaced the system image, the recovery image, The userdata image and the boot image with the ones from the moto dev websight using fastboot. I also cleared cache, from fastboot and recovery as well as deleting all user data from recovery (Factory Reset).

I also re-installed the whole system using four different WIFI RSD Images which went successfully as well.

Now I know its actual flashing because I flashed a different recovery to test and that worked, but for some reason im stuck in a boot loop at the Motorola Logo. I can still access all features (fastboot, recovery and RSD) but it will not boot past the Moto Logo.

I have tried installing the 4.1.1 and 4.1.2 updates through recovery which both installed their updated boot loaders and for a moment I thought I had success when I saw the xoom boot image with the flashing squares, but then that froze and it rebooted never to be seen again.

So my question is, is this a hard brick and I should just stop trying or does anyone have any other suggestions?

Also I am using a Moto cable, it tells me that I am successfully flashing.

Everything I read thus far indicates that if you can access fastboot and recovery that its not hard bricked, but what exactly does a hard brick look like?

Thanks All any insight is appreciated.

p.s. I have relocked, unlocked, etc

Welcome to the forum. Glad you decided to join us. You're doing everything I'd do. Are you sure there's not another problem on the inside?

[madmaverickmatt]

at this point I am sure of nothing and appreciate ALL suggestions.

Thanks

[sr20hardbody]

If it were me I'd try unlocking the boot loader flashing cwm then load a custom ROM and gapps package and if it works and you wanna stay stock then retry from that point.

I bet those stock .img are very finnicky with everything having to be 100% correct.

[madmaverickmatt]

I tried installing the timult cwm and open recovery, both of those installed successfully, then I installed EOS 3 and that installed, but still boot loops.

[ggrant3876]

I tried installing the timult cwm and open recovery, both of those installed successfully, then I installed EOS 3 and that installed, but still boot loops.

Did you do all of the required wipes?

[zigackly]

If you can get into recovery, mount and format all your partitions from TWRP (data, system, cache, dalvik, and internal storage), then try flashing a ROM. You can get the ROM onto the Xoom with adb push after formatting. Probably won't work, but it can't hurt to try. Also make sure you don't have any external SD cards in there when you boot.

[madmaverickmatt]

I did several wipes, but i will try and wipe all and reflash again via ADB, like you said it cant hurt ;-)

[madmaverickmatt]

ok, interesting progress, I booted into recovery, and wiped everything three times, following this I pushed cm10 and the gapps package to the emmc directory using adb and then installed, This got me past the moto logo to a cm10 logo which froze the first time. Then after a reboot just kept spinning the cm10 logo (10 plus minuits). So I rebooted into recovery and factory reset and wiped davlic cache, this hangs me at the moto logo again. Like I said, progress sort of lol.

[madmaverickmatt]

ok , I have a thought and it could be crazy feel free to tell me as much. ok so I can flash system, userdata, recovery and data, but what about the other directories, is it posbile that something else is missing from some sub folder in the etc directory for example. I just cant see another reason why it would start booting and then crap out so im thinking I have another xoom so maybe I can pull the files from the file tree of that one, one by one and push them to this one. any thoughts, am I just spinning my wheels?