Thinking about unrooting Read this first!!!! ALL MODELS

[Kippui]

can you not do the "fastboot oem lock" for when u just want a clean system but still plan on starting over?

 

[dirtymindedx]

can you not do the "fastboot oem lock" for when u just want a clean system but still plan on starting over?

If your xoom is locked you will not be allowed to write files to it. The reason for fastboot oem unlock is to ensure that your device can be written to. Most times when people get RSD errors or its frozen at the Dual Core logo this is the initial step to make sure your device can be seen by fastboot and this will also tell you whether your device is recoverable in many situations.

 

[bwcorvus]

nice set of links definitely treasure in my book. Can you post a link on there to this thread since they still haven't stickied this yet?

Added to my post.

 

[dirtymindedx]

Thanks for the add. I help people root, debrick, and reroot their devices a lot lately this is definitely helpful when I don't have to go to different pages to look for stuff. saves a lot of time. Thanks again!

 

[bwcorvus]

Thanks for the add. I help people root, debrick, and reroot their devices a lot lately this is definitely helpful when I don't have to go to different pages to look for stuff. saves a lot of time. Thanks again!

Np, you may want to add the line below. Also we can always use more helpers in the irc channel


"Note: If no userdata.img file is present in your download, please issue the command:
fastboot erase userdata"

 

[dirtymindedx]

just made the change to the posting with the note. I havent been in an IRC chat in a loooong time. Whats the chat address I may check it out tomorrow night.

 

[bwcorvus]

just made the change to the posting with the note. I havent been in an IRC chat in a loooong time. Whats the chat address I may check it out tomorrow night.

Links in my sig, but its #xoom on irc.freenode.org.

 

[dirtymindedx]

i figured it out the minute i sent you the message lol

 

[popcity]

Thanks, worked like a charm!

 

[maxatma]

Ok my Xoom is stuck at "writing boot" for a freaking long time...
Here is my log:

C:\Android\android-sdk\platform-tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
FAILED (remote: (00120000))
finished. total time: 152.033s


When I force-rebooted it after a while, it booted normally. with my tiamat kernel but without any data.

I also found the Xoom stock sbf file, but upon trying to flash it via RSDLite it says "Unable to retrieve initialization values from INI file "

How on earth should I force my Xoom to go back to stock?

 

[macarmody]

thanks, have used twice without any issues. Unfortunately I keep rerooting when the Google upgrade dissapoints. . . like a read only SD card. Keeping the post handy I case 3.3 delivers.

 

[debijon999]

I rooted my xoom wifi/3g Verizion model HMJ37 build after 3.1 ud using the One Click Method and cannot find instructions to unroot. Using your instructions I hold the vol down and power on buttons and get "Starting fastboot protocal support" and it hangs there. I tried vol down and vol up but nothing happens. As you have guessed I am a noobie. I also cannot find the "Tools Folder:. Is it in the Xoom ? Also are you doing the cd\tools in the xoom or on the PC?

Thanks for your help. I have searched with no results.

 

[macadoo]

developer.android.com/sdk/installing.html

Sounds like you need to setup the dev environment on ur PC - follow the link to finds the steps

You'll need the jdk (not the jre) too

Once that's fixed, you'll find the /tools folder under where you put the adk

Open a CMD prompt from the /tools folder and fastboot will run from there

I had bootlooped my xoom and fastbooted Clockwork Recovery 3.2 to it again to get back in business

Thanks to all the devs for their great work making the Xoom fun

 

[debijon999]

Thanks Macadoo I followed your help and it worked fine. After downloading the jdk kit I could not find the fastboot command so I copied it from the one click tools and all worked fine. I restored to 3.0 and after a few minutes it updated to 3.1 and a few minutes it updated to 3.2. All is great and this was fun. Thanks again.

Bill

 

[woggly4]

Please add that this instruction (original post) is only appliable to US Xooms. Not EUs

uh, is that true? i thought this is applicable for "all models" (cf. title)?

 

[dirtymindedx]

uh, is that true? i thought this is applicable for "all models" (cf. title)?

The instructon states goto the link and download your firmware and follow the instructions. this has been tested on all models. i have helpwd many users. the people who dont get this to work are those who messed up and flashed the wrong files before reading this thread.

 

[woggly4]

Thanks a lot, your guide worked fine for me!

 

[voyager_s]

Thanks a lot for the guide...really helped a lot. Managed to flash back to stock and relock the boot and return the product.

Thanks again



Sent from my Nexus S using XDA App

 

[Simonetti2011]

Thanks for the info!

Last night I lost wifi & 3G after a semi-successful rooting, so I decided that wifi is more important than root, and had to flash back to stock FW. Your guide was quite helpful.

 

[IsmaelJones]

Help I have a Telstra Xoom with OTA 3.1. I rooted this then found another update to 3.2 had just arrived so I tried to follow this to take it to the stock Telstra img H.6.1-38-9_Telstra_Australia. All was working fine until the command:

fastboot flash system system.img

I got this:

sending 'system' (262144 KB)..
FAILED (remote: (00120003))
finished. total time: 202.745s

What can I do now?

On the xoom it says:

Failed to process command error(0x120003)

Where do I go now.

Please reply very urgent.

Thanks a million...