[GUIDE][VZW Version] Un Root & Re-lock the Xoom [3/05/2011]

[2CupsWithString]

This method is now depreciated, to restore your Xoom please go here: http://forum.androidcentral.com/xoo...cking-rooting-returning-stock.html#post716856

 

[Mudvayne622]

Can we haz App for this?

 

[doctorlove316]

Thank you, this will come in handy if need be.

 

[wg#AC]

I have a question I know that if you root your Xoom that it voides your warenty but will it also invalidate you for the free 4g uprade?

 

[plakius]

Help! .. I did this and now I'm stuck in boot and says "failed to boot LNX 0x0004"
"Starting RSD mode 2"

what now?

 

[2CupsWithString]

Help! .. I did this and now I'm stuck in boot and says "failed to boot LNX 0x0004"
"Starting RSD mode 2"

what now?

Try to flash the stock boot image again.

Were you rooted?

 

[Devwest]

I tried to re-lock the xoom and received this error "failed to boot LNX 0x0004"
"Starting RSD mode 2"
...I was rooted before flashing the stockboot...

Any ideas?

 

[robrowald]

Hold down the the down volume key and the power button, it will reboot into fastboot mode

from your command prompt type fastboot oem unlock (yes re-unlock it)
it will reformat the UDA and boot again.
Then try to re lock lock it

 

[Devwest]

Same error as before

 

[robrowald]

did you remove the superuser program

if not you need to do that.

get back to fastboot
re-flash the rootboot.img file
reboot the device
then adb remount
then adbshell rm -r /system/bin/su
then adbshell rm -r /system/xbin/su
then adbshell rm -r /system/app/superuser.apk
then reboot to the boot loader
reflash the stockboot.img file
then try to relock it

I haven't tried this myself, just theorizing

 

[2CupsWithString]

You might want to try re downloading the stock boot. It looks like its not finding the kernel to boot. Does it work when you are un locked?

 

[mistamista2000]

I un-rooted my XOOM, ensured that SU is no longer on it and verified its no longer rooted using a terminal program. Although I placed the stockboot.img back on (a few times) and it took, for some reason I still cannot re-lock it. When I do I get the Failed to boot LNX 0x0004 / Starting RSD Mode 2 message. Any help would be greatly appreciated.

 

[2CupsWithString]

I think you'll need to restore the stock software from developer.motorola.com - I'm not sure if it's even published yet.

 

[2CupsWithString]

Help! .. I did this and now I'm stuck in boot and says "failed to boot LNX 0x0004"
"Starting RSD mode 2"

what now?

I tried to re-lock the xoom and received this error "failed to boot LNX 0x0004"
"Starting RSD mode 2"
...I was rooted before flashing the stockboot...

Any ideas?

Are you guys still here or were you able to get back to unlock and re-flash a new boot image?

 

[Devwest]

I wasn't able to relock even after removing the su and super user. It still shows the same error. It does boot if I unlock it though.

 

[2CupsWithString]

I wasn't able to relock even after removing the su and super user. It still shows the same error. It does boot if I unlock it though.

Yeah it looks like a stock image will have to be restored so the bootloader can verify it's OK to lock the device.

Hopefully moto releases the stock images soon!

 

[mistamista2000]

Yeah it looks like a stock image will have to be restored so the bootloader can verify it's OK to lock the device.

Hopefully moto releases the stock images soon!

I thought stockboot.img was the stock image we needed...Guess the Motorola one is different in some way.

 

[2CupsWithString]

I thought stockboot.img was the stock image we needed...Guess the Motorola one is different in some way.

There is either a signature or md5 that the stock boot loader is looking to verify before it will re-lock.

either way flashing the root kernel or altering the /system partition is breaking it.

I can't imagine it being a very long time, the warning itself on the Xoom's screen says it needs to be restored by Moto software prior to re-locking the boot loader. So how can they release the Xoom and not have this ready to go on their end?

 

[kurttrail]

There is either a signature or md5 that the stock boot loader is looking to verify before it will re-lock.

either way flashing the root kernel or altering the /system partition is breaking it.

I can't imagine it being a very long time, the warning itself on the Xoom's screen says it needs to be restored by Moto software prior to re-locking the boot loader. So how can they release the Xoom and not have this ready to go on their end?

LOL! How could Motorola not had boot image ready to go? Really?

How about the SD reader, flash, 4g, a high profile h.264 codec...

Seriously, the Xoom is a work-in-progress, and it's gonna take a while before Motorola gets every thing working.

 

[2CupsWithString]

LOL! How could Motorola not had boot image ready to go? Really?

How about the SD reader, flash, 4g, a high profile h.264 codec...

Seriously, the Xoom is a work-in-progress, and it's gonna take a while before Motorola gets every thing working.

Yeah I agree, but they at least know what the stock software is already