Ok here goes…….I have a problem with my wifi xoom……basically it wont boot. All that happens is a continuous honeycomb type animation that never goes.
This problem started in about February time this year when I was attempting to unlock, root and flash a custom ROM on the device. Since then I have been continually reading the forums and trying various method to resolve the issue.
I cant say exactly what I did at the outset as it was some time ago but I suspect that I may have used an outdated guide or flash the wrong image to my device. I do remember that following that the device booted up fine and then the following morning I was greeted with this problem that I have been unable to resolve.
From ADB dumpstate…. I can see the following entry……(I guess this is the kernel i flashed?)
[ 207.730229] Restarting Linux version 2.6.36.3Tiamat_Xoom-v1.3.0-gc02ada7 (big
[email protected]) (gcc version 4.4.0 (GCC) ) #1
SMP PREEMPT Wed Apr 13 04:27:14 PDT 2011
I have become intimately acquainted with ADB and Fastboot and have tried many times the routine of Unlocking the bootloader, Using fastboot to flash the Motorola Stock image files to flash back to stock and start again. All of this appears to work but when I reboot I get the same bootloop.
Unlike many other posts, I don't have a problem with ADB mounting the Xoom so I know my drivers are correct. I am able to communicate with the xoom via ADB and Fastboot and also use ADB shell to navigate the filesystem.
What happens persistently is that when flashing any image, the xoom reports it has flashed successfully, however when rebooting nothing has changed.
This is particularly evident when trying to flash a recovery image ('recovery-Tiamat-R4c-100611-1150-cwm-1.img' ) to gain access to clockworkmod recovery. When I reboot, all I get is the Android Recovery menu. I have tried this many times paying particular attention to the ….power +vol up……….Moto logo (wait 3 secs)……vol Down………vol up and still get the same result.
I can also make changes to the file system while in ADB shell such as changing the boot animation which actually changes on the screen of the xoom……and also uploading SU and Superuser.apk ………..but when I reboot…all of the changes have been undone and the same problem remains.
I understand that in the later models any custom recovery will be overwritten on reboot? Is this correct?
I took a look at this guide;
http://forum.xda-developers.com/showthread.php?t=1477024
5.) Now you have to rename the 2 notorious files, that reinstall your Stock Recovery over CWM, into a format that is unreadable by the bootloader. In the already opened Command Prompt, type the following commands:
Quote:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
My problem here is that i cant get the recovery image to stick, and while ever i'm in Fastboot I can't gain shell access to rename the recovery files. If I reboot the device the recovery image gets overwritten and these files are not present.
I have also considered flashing an update.zip via host cable (Android Recovery from USB) to negate the need for clockwork mod but that didn't work either.
I feel like I am so close, there must be something I can rename change to avoid this overwriting cycle. I have a full recursive file listing (ls -alR) for anyone to view in order to help. I don't understand the contents of the OS enough to know what should and shouldn't be there.
Anyone help please ??
This problem started in about February time this year when I was attempting to unlock, root and flash a custom ROM on the device. Since then I have been continually reading the forums and trying various method to resolve the issue.
I cant say exactly what I did at the outset as it was some time ago but I suspect that I may have used an outdated guide or flash the wrong image to my device. I do remember that following that the device booted up fine and then the following morning I was greeted with this problem that I have been unable to resolve.
From ADB dumpstate…. I can see the following entry……(I guess this is the kernel i flashed?)
[ 207.730229] Restarting Linux version 2.6.36.3Tiamat_Xoom-v1.3.0-gc02ada7 (big
[email protected]) (gcc version 4.4.0 (GCC) ) #1
SMP PREEMPT Wed Apr 13 04:27:14 PDT 2011
I have become intimately acquainted with ADB and Fastboot and have tried many times the routine of Unlocking the bootloader, Using fastboot to flash the Motorola Stock image files to flash back to stock and start again. All of this appears to work but when I reboot I get the same bootloop.
Unlike many other posts, I don't have a problem with ADB mounting the Xoom so I know my drivers are correct. I am able to communicate with the xoom via ADB and Fastboot and also use ADB shell to navigate the filesystem.
What happens persistently is that when flashing any image, the xoom reports it has flashed successfully, however when rebooting nothing has changed.
This is particularly evident when trying to flash a recovery image ('recovery-Tiamat-R4c-100611-1150-cwm-1.img' ) to gain access to clockworkmod recovery. When I reboot, all I get is the Android Recovery menu. I have tried this many times paying particular attention to the ….power +vol up……….Moto logo (wait 3 secs)……vol Down………vol up and still get the same result.
I can also make changes to the file system while in ADB shell such as changing the boot animation which actually changes on the screen of the xoom……and also uploading SU and Superuser.apk ………..but when I reboot…all of the changes have been undone and the same problem remains.
I understand that in the later models any custom recovery will be overwritten on reboot? Is this correct?
I took a look at this guide;
http://forum.xda-developers.com/showthread.php?t=1477024
5.) Now you have to rename the 2 notorious files, that reinstall your Stock Recovery over CWM, into a format that is unreadable by the bootloader. In the already opened Command Prompt, type the following commands:
Quote:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
My problem here is that i cant get the recovery image to stick, and while ever i'm in Fastboot I can't gain shell access to rename the recovery files. If I reboot the device the recovery image gets overwritten and these files are not present.
I have also considered flashing an update.zip via host cable (Android Recovery from USB) to negate the need for clockwork mod but that didn't work either.
I feel like I am so close, there must be something I can rename change to avoid this overwriting cycle. I have a full recursive file listing (ls -alR) for anyone to view in order to help. I don't understand the contents of the OS enough to know what should and shouldn't be there.
Anyone help please ??
