[Q] How to Unbrick A XOOM? Hellllppppp!!!

[GulMiguel]

J decided yesterday to run the update and all was working spectacularly. I had everything I needed and all my apps came back. However, I was feeling good about myself and decided that I wanted to do the overclocking as well. So I flashed that part of the update, the XOOM rebooted (partially) - it never left the big red M screen. I have tried to SBF (which isn't working - the process fails before it even starts). I can get to fastboot, but once there, there isn't anything that I can do to bring the XOOM back to life. It looks like I'll be paying Verizon a visit unless some supergenius dev has a 're-animation' method that I have not yet considered. I'm currently going through very painful withdrawal symptoms and would really appeciate the help of anyone else who has been through this.

Many many thanks in advance.

 

[myersn024]

If all you did was flash a new kernel, then you should be able to flash the stock kernel from fastboot and that should get you fixed. If you're still on 3.0, then you can get the stock images from Motorola (I don't have the link handy). If you're on 3.1 then I'm sure someone can get you a copy of the stock boot image.

 

[GulMiguel]

If all you did was flash a new kernel, then you should be able to flash the stock kernel from fastboot and that should get you fixed. If you're still on 3.0, then you can get the stock images from Motorola (I don't have the link handy). If you're on 3.1 then I'm sure someone can get you a copy of the stock boot image.

At the time this all happened, I had just successfully upgraded to 3.1. However, when I tried to use RSD Lite 4.9 and the HR139 image to perform the normal SBF procedure, it kept failing out with a message referring to the fact that it cannot find some type of initialization in the INI file. I'm totally lost and feeling somewhat depressed and stupid.

 

[Mandelbrot.Benoit]

If you can get to Red M you should be able to get into get into bootloader by powering on by holding power and volume down. Then as long as adb recognizes device follow this.

http://www.xoomforums.com/forum/mot...s/2788-how-restore-3g-4g-system-boot-img.html

It just pushes stock images with adb and not rsd

Edit; in your case hold power + volume up to reboot device, then immediately hold volume down until Rsd protocol words come up then hook xoom to computer. Don't follow first step in guide because you are already in bootloader.

 

[myersn024]

At the time this all happened, I had just successfully upgraded to 3.1. However, when I tried to use RSD Lite 4.9 and the HR139 image to perform the normal SBF procedure, it kept failing out with a message referring to the fact that it cannot find some type of initialization in the INI file. I'm totally lost and feeling somewhat depressed and stupid.

As far as I know, there are no overclock kernels that work with 3.1, which is why you had the trouble you had. You'll either have to flash back to completely stock 3.0 or you'll need the boot img out of the 3.1 update.

 

[deanthemean]

Help

I tried overclocking my xoom with this link h t t p://w w w.dkszone.net/overclock-motorola-xoom-1.5ghz-detailed-guide[/url]. I did step 3 and it got stuck in "starting RSD mode 3". adb wont recognize my device. Please help.