[Q] Stuck in boot loop after factory reset - CWM works - need help

[sasquatchgeoff]

Here are the particulars.
rooted
Display JZO54K
Fingerprint = motorola/tervigon/wingray:4.1.2/JZO54K/.....

Loaded elementalx - xoom- v1.3 three months ago ran fine. Stupidly, I did not flash a backup. Now after deleting cache, factory reset, stuck in "loading apps" after splash, the boot loops back to motorola screen where I can launch CWM v4.0.0.4 - I want to get a ROM on there and continue using this mission-critical dinosaur. Can someone help?

I guess the real question is can a rom be copied onto the ext-sd card via windows out of the xoom? If so will CWM see it and will it work?

Have not tried connecting and using ADB. Not feeling confident enough at this point. ext SD still has data but when in CWM device does not show up in Windows.

TIA for any help

Geoff

 

[sasquatchgeoff]

Here are the particulars.
rooted
Display JZO54K
Fingerprint = motorola/tervigon/wingray:4.1.2/JZO54K/.....

Loaded elementalx - xoom- v1.3 three months ago ran fine. Stupidly, I did not flash a backup. Now after deleting cache, factory reset, stuck in "loading apps" after splash, the boot loops back to motorola screen where I can launch CWM v4.0.0.4 - I want to get a ROM on there and continue using this mission-critical dinosaur. Can someone help?

I guess the real question is can a rom be copied onto the ext-sd card via windows out of the xoom? If so will CWM see it and will it work?

Have not tried connecting and using ADB. Not feeling confident enough at this point. ext SD still has data but when in CWM device does not show up in Windows.

TIA for any help

Geoff

I pushed a stock rooted rom via ADB (I found the internal sdcard is accessible via the ADB shell) . The stock rom showed up in the CWM select zip file list. Installed the rom and the xoom animation freezes then continues the boot loop - regardless of rom installed. Cleaned system cache and davik cache as well after factory wipe. I am beginning to think hardware issues. No amount of cajoling will get this thing to boot into its OS. Either memory or processor - when it worked, I did have it running incredicontrol and 1.4 ghz and the max memory limitation upped to 64MB in order to run a lecture player for school.