[X]Assistant

[gredmy]

FirmwareMotorola XOOM
Motorola XOOM, MZ600, MZ601, MZ604, MZ605, MZ606
Description | Discussion пїЅ | Purchase пїЅ | Firmware пїЅ | Accessories пїЅ | FAQ ClockworkMod recovery

Read first!

Dear Xoom owners!
I beg you to read the cap, and in particular the section with instructions and express your opinion about their correctness and relevance.

• пїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ download

  10 commandments novice, andHow to make the forum convenient and useful
  
• Before asking a question, use the search on the topic! And also look Android OS FAQ and further Glossary. Respect your and other people's time.
  
• If a forum member gave you good advice that helped you solve your problem Do not post a message with the text “Thank you! You are super!!!". On our forum, it is customary to express gratitude by raising the reputation of a particular participant.
  
  
  • The reputation of other participants can be influenced by any user who has collected 15 useful posts. If you do not have 15 helpful posts, ask the moderator to raise the reputation of the person who helped you through the "Complaint" button.
    

Drivers and Utilities

• Android SDK Tools
  
• A set of the most necessary executable files (adb fastboot) to run the command linetools.cmd - Xoom_tools.rar (364.83 KB)
  
  
• RSD Lite 5.0 , Update to version 5.3.1 , RSD Lite 5.6 , documentation
  
• Motorola_End_User_Driver_Installation_5.2.0_32bit.msi
  
• Motorola_End_User_Driver_Installation_5.2.0_64bit.msi
  

Official firmware

• !Currently JB 4.1.1 firmware is available only for XOOM USA WIFI ONLY. There is no Russian language.
  
• !Currently, ICS firmware is officially available only for Verizon USA. There is no Russian language. More for XOOM USA WIFI ONLY
  
• !At the moment, ICS firmware is officially for MZ601 Europe, France and Germany (T-Mobile), Germany MZ604 and Europe. Is there Russian language.
  
• ! At the moment, all firmware from 3.2 for Europe, as well as for Australia, have Russian.
  
• Original Motorola XOOM (SBF) service firmware forRSD Lite. Mirror Xoom 3G and Xoom wifi
  
• on xda forfastboot.
  
• on MOTODEV forfastboot.
  

Recovery

• CWM Rogue Touch Recovery v1.5.0 (RC3) (Backup and restore to USB Drive, Backup and restore to internal memory card internal storage)
  
• ClockworkMod 3.2.0.0 (R4c)
  
• EOS recovery (R6) CWM Based (does not restore backup from other versions of recovery), news from Alex469
  
• unofficial [RECOVERY] TWRP 2.2.0 with on-screen keyboard! from giving Uv. yamay
  

Modified and custom firmware

• Android Honeycomb 3.2.2 - Stock & Rooted ! Some users have a problem with WIFI, watch here and here
  
• Team Tiamat Xoom Rom 2.1 Hammerhead Complete localization support (Russian present).
  
• Team Tiamat Xoom Rom 2.2.2 - Moray Complete localization support (Russian present). Mirror1 , Mirror2
  
• Xoom Zone 2.2.2 - Family Pack Derivative of Tiamat Xoom Rom (Russian is present), This rom does not support 4G devices (does not support 4g devices).
  
• Team Eos ICS 1.0.0 Firmware based on AOSP from Team Eos (continuation of Teamat). Russian is not fully present. Included versions for all devices (Wifi (wingray / MZ604).:. US 4G (stingray / MZ602).:. EU 3G (umts_everest / MZ601).:. US 3G (stingray_cmda / MZ600))
  
• Team Eos ICS 2.0.0 The latest AOSP based firmware from Team Eos (continuation of Teamat). Russian is not fully present. Included versions for all devices (Wifi (wingray / MZ604).:. US 4G (stingray / MZ602).:. EU 3G (umts_everest / MZ601).:. US 3G (stingray_cmda / MZ600))
  
• Cyanogenmod
  
  Team EOS 3 "JELLYBEAN" Nightlies firmware

  • Wingray / MZ604 / WIFI ONLY
    
  • Umts_everest / MZ601 / EU 3G ONLY
    
  • (MOD) SMS_MMS_SIP enabled on (Umts_everest / MZ601 / EU 3G ONLY)
    
  • Stingray / MZ602 / US 4G ONLY
    
  
  

Kernels

• [AOSP] Tiamat from solarnz
  
• Launchpad
  
• Rogue 1.4.1 "Electra"
  
• Tiamat Xoom 2.2.0 "Odachi"
  
• Rogue 1.4.3 "Rana"
  

Instructions

• user's manual XOOM_manual.pdf (5.42 MB)
  
  

How to find out the version of your device and firmware

• To find the version of your device go toSettings>About tablet . It will be located at the very bottom> Build number . (In my case it was H.6.3-25-9 )
  
• Next go onreference and in the firmware located there find your own (In my case it is EVRSU_U5. H.6.3-25-9 _SIGNED_USAEVRSTUTMDE_P014_A005_M004_HWumts_evere st_1FF.sbf.gz)
  

adb, fastboot, recovery - scary words or manna from heaven? - reprint with permission of the author AntonCh original here

Perhaps, starting our bullying the device, you need to be sure that you can get everything back to a working state at any cost .. without even using a computer ... just imagine how you are perverted by deleting files from the system partition ... while you are on the bus ... knowing that right on the bus you will be able to bring the "corpse" back to life .. great? or flashing the experimental firmware, just to look at it with your eyes - and return to a stable build and live happily ever after?

What kind of beast is ADB?

Where many are mentioned adb, adb shell ..
ADB = Android Debug Bridge- is a program for both debugging and controlling your Android device from a computer (via usb cord).
In addition, there are applications to control the device via wifi and so on. We will not consider it for now ..
To work with ADB, you need to enable usb debugging on the device (settings ->applications ->development ->USB debugging)
Where to get adb.exe? in principle, it lives in android sdk (as well as fastboot by the way), but you can use the previously mentioned folderXoom_tools.rar(364.83 KB)
running tools.cmd

Quick Reference for adb Commands:

adb devices - connected devices
adb push<local><remote>- transfer file to device<local>- local file (the one on the computer)<remote>- file on device
adb pull<remote> [<local>] - download file from device
adb shell<command>- run the command on the device
adb shell - go to the command shell of the device
adb install program.apk - install the program on the device

adb usage examples:

adb push update.zip /sdcard/update.zip
- will copy update.zip from the current directory (on the computer) to the device (specifically, to the root of the SD card)
adb pull /sdcard/00001.vcf
- download the file 00001.vcf from the device (from the root folder of the SD card) to the current directory
adb pull /sdcard/00001.vcf C:
- download file 00001.vcf from the device (from the root folder of the SD card) to the root folder of the C drive:

!!! note the paths: paths to files / folders on the device are written with a "/" separator, for example /sdcard/somefolder/somefile.zip
!!! note the case: the names of the folders and files on the device are case-sensitive: i.e. for example, "file" and "File" are two different files. The same applies to commands and their parameters (-v and -V can have different values) all in / sdcard / is an exception, since The SD card uses the FAT file system - the case on the name does not matter.
the path of the local file can be omitted if it is located in the current directory (in the lg_gt540_tools folder if you use tools.cmd from there)

When we are told about the command that "you need to run on the device" or "run through the adb shell" it means that you must enter the adb shell
After entering, we will be met by an "invitation" - "$" you can enter commands ..
To go to the execution of commands from the superuser (root) - you must enter the command "su" if you do it for the first time - pay attention to the phone - a dialog will appear confirming the granting of superuser rights. (Naturally, this refers to rooted phones, I’ll probably finish getting the root later - for now the entire description here implies installing a custom firmware in which root is already built in)
When switching to the command execution mode from the superuser, the invitation will change from "$" to "#"
Exit from adb shell - exit (if previously there was a "su" command, then it will leave the superuser mode, to exit, type exit again)

What is fastboot and what is recovery?

fastboot
fastboot - mode for firmware / boot device. Allows you to flash individual sections of the flash memory device.
The fastboot itself is built into the low-level boot loader: i. through fastboot you can not break fastboot - this is the most important thing! Knowing how to use fastboot - you can always flash your device - even if you have not injected the wrong firmware into the system section before.
recovery
Recovery - a set of low-level utilities for saving / restoring a backup copy of all ROM partitions. By analogy with computer software - this is the "acronis true image on livecd". You can boot into the recovery and save the "current state of the system" - and then if you go back to it .. In addition, many system patches are made through it - so we will need recovery.

What can recovery?

1. firmware update.zip patches
2. hardcore
3. backup / restore (including you can flash new firmware method of "restore")
4. connect sd to computer (conveniently, you can get access to sd without leaving recovery)
5. formatting phone sections (system / data / boot / cache .....), clearing dalvik-cache.

How to use recovery?

Log in recovery - VOLUMEDOWN + POWER.
Navigate the VOLUMEUP / VOLUMEDOWN menu, select the POWER item.
reboot system now - restart the phone
apply sdcard: update.zip - install patch update.zip from sd card root
wipe data / factory reset - clear user data section (hardware)
wipe cache partition - clear cache partition
install zip from sdcard - install patch .zip from sd card (select zip ->choose zip from sdcard)
backup and restore - backup and restore phone partitions.
mounts and storage submenu:
- mount / unmount / xxxxx connect / disconnect partition / xxxxx
- format xxxxx format section xxxxx
- mount usb storage, you can connect the sd card to the computer via usb cord.

Data backup

Having entered the recovery we can create a backup of the entire system through the backup and restore - option>backup
Backup takes place on the sd card in the folder clockworkmod / backup name - the date and time of the backup copy byGMT
To restore, select the restore item, then select from which folder to restore.
advanced restore allows you to restore partitions one by one to choose from. First select the folder, then the restored partition.
I recommend then renaming folders with backups in order to make it easier to understand later.
For example, the folder 2010-11-30.08.57.43 - says only about the backup time, and if you rename it to 2010-11-30.08.57.43_quarx21, you will immediately see that this is a copy of the system with 2.1 firmware installed from Quarx. It is more reasonable to add explanations to the end of the folder name - then when sorting by name they will go in chronological order. I called the so-called "installation" backup copies of the firmware with a different approach: so that they do not interfere among your copies.
There is a suspicion that by renaming the backup folder you cannot use spaces and Russian letters. use _ instead of spaces Perhaps this is exactly what leads to the appearance of the “MD5 mismatch” MD5 creation algorithm based only on the contents of the files, neither the file names nor the folders have any influence on this checksum. Also, if you make manipulations with backup folders via mount usb in recovery, be sure to restart recovery (reboot system now, log in). Do not forget to unmount usb on your computer before unmount on your phone!

Simple instructions for unlocking the bootloader. Based oninstructionsfrom dearfreemsk1

• Download the latest driver http://developer.motorola.com/docstools/USB_Drivers/
  
• DownloadXoom_tools.rar(364.83 KB)
  unpack to any place.
  
• We connect the device to the computer, - do not forget about the tick - Applications - Development - Debugging via USB.
  
• Run tools.cmd in the Xoom_tol folder
  
• adb reboot bootloader
  
  
• XOOM will reboot into bootloader mode (the screen will show “Starting Fastboot Protocol Support.”)
  
• fastboot oem unlock
  
  
• We read the warning on the screen.
  
• Press the volume-down button to select "Accept."
  
• 1 Press the volume up to click on “Accept.”
  
• After that XOOM will be unlocked and formatted.
  

Installrecovery

1. downloadrecovery-Tiamat-R4c-100611-1150-cwm.img
2. rename the downloaded image to recovery.img (for simplicity)
3. DownloadXoom_tools.rar(364.83 KB)
unpack to any place.
4. Connect the device to the computer, - do not forget about the tick - Applications - Development - Debugging via USB.
5. If your device already has a bootloader unlocked, then we skip this step. If not, then we lookhere, or higher:Simple instructions for unlocking the bootloader
6. recovery.img put in the folder Xoom_tools and run tools.cmd
7. Now we flash the Recovery itself. (Recovery-Tiamat-R4c-100611-1150-cwm.img renamed to recovery.img is in the Xoom_tools folder)
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
8. Now it is important to immediately get into our stitched recovery with buttons when you first boot, otherwise xoom will register a regular recovery and you will need to sew it again! We do this - when you boot, the Moto logo appeared, after 3 seconds you press the down button - then Android Recovery appears - you press the up button.
Important!
If you just want to install CWM, then at the beginning you need to get a ROOT and delete the script/system/etc/install-recovery.sh which rewrites the standard recoveries.

Install Tiamat Xoom Rom throughCWM Recowery

Before installing the firmware, you must install Recovery. Instructions look above - Install recovery

1. Download Tiamat Xoom Rom 2.2.2 "Moray" (or Mirror1 , Mirror2 ) and copy it to the root of the microSD card.
2. Insert a microSD card with a Tiamat Xoom Rom 2.2.2 "Moray" recorded on it into the device
3. Restart the device in Recovery
4. Select nandroid backup in Recovery and put the resulting stored somewhere
5. Select Wipe data / factory reset (If you do not, then after the firmware will get a constant animation of water)
6. Select Install zip from sdcard in Recovery
7. Choose in Recovery choose sip from sdcard
8. Reload and ... Welcome to the party.
! Possible solution to the problem with the non-normal operation of the firmware, look here thanks say So_kill

Stitch throughfastbootor how to restore the device after unsuccessful firmware

1. Download the original, or the desired firmwarehere.
2. Download hereXoom_tools.rar(364.83 KB)
and unpack somewhere, should get the folder Xoom_tools.
3. Unpack the downloaded firmware archive and the contents (boot.img, system.img, recovery.img and userdata.img) are copied to the Xoom_tools folder.
4. Press the volume up and power buttons until the reboot starts, and then, when the device starts to load, the volume button is down and do not release until “Starting Fastboot Protocol Support” appears on the screen. Now we connect the device to the computer.
5. Run the tools.cmd file in the Xoom_tools folder
6. We make the firmware of the device by entering the following commands:

• fastboot flash boot boot.img
  
• fastboot flash system system.img
  
• fastboot flash recovery recovery.img
  
• fastboot flash userdata userdata.img
  
• fastboot erase cache
  

7. If there is no userdata.img in the downloaded archive with firmware, then you should use the command:

• fastboot erase userdata
  

8. Last command:

• fastboot reboot
  

And we are happy with the received firmware.

Firmware manual throughRSD Lite

You probably noticed how long Motorola makes updates for XOOM, especially to get root by the user? In addition to this, everyone can just make mistakes when getting root on the device, and you could get a brick from the device, with which there is nothing to do. Fortunately, we have these .SBF files. Many of you have probably heard about them before, but while the device is working for you, why use it? You probably do not really understand what it is.
. The SBF file is used to flash all of the internal memory and will return the device to the factory settings.
(Attention!) Everything that is described below is done at your own risk! No claims to the author or forum are not accepted! Before flashing the device through RSD Lite read the warningsAddrian hereandhere. We strongly recommend using this method only as a last resort, when fastboot does not help.
This is a great opportunity for anyone who has managed to get a brick and you need to go back to the drain to make it work again. It does not delete your data, including your applications, contacts, messages, etc. To get a fully stocked machine, you will need to do another WIPE (complete cleaning of the machine).

What is needed for that

You will need a couple of things:

• .Sbf file compatible with your version of appavrata
  
• To find the version of your device go toSettings>About tablet. It will be located at the very bottom>Build number. (In my case it wasH.6.3-25-9)
  
• Next go onreferenceand in the firmware located there find your own (In my case it is EVRSU_U5.H.6.3-25-9_SIGNED_USAEVRSTUTMDE_P014_A005_M004_HWumts_evere st_1FF.sbf.gz)
  
• RSD Lite
  
• Drivers must be installed and updated.
  

How to install.

Instructions:

• Install RSD Lite
  
• Unzip the RSDLite.zip file and double-click the file. Msi file Follow the instructions.
  
• If necessary, back up something to an SD card that you think is important.
  
• Connect the device to a computer, and then select a USB Mass Storage device.
  
• There must be removable media in "My Computer"
  
• Copy everything to your computer (most likely, your photos, DCIM)
  
• Turn off the phone
  
• Press and hold the volume up button, then turn on the device, a black screen should appear with the Motorola logo and the caption Starting RSD Protocol Support 0
  
• Now connect it to the computer.
  
• In Windows should install new drivers.
  
• Now run RSD Lite
  
• Your device should appear in the list at the bottom (A955, port 1, connected, etc.)
  
• If this does not happen, you may need to run RSD Lite on behalf of the Administrator (right click Program Files / Motorola / RSD Lite / on SDL.exe and select "Run as Administrator")
  
• Click on the "..." button located at the top of the RSD Lite
  
• Using the window that popped up, find the downloaded .SBF file and select it, then click "Open"
  
• Click the "Start" button at the beginning of the program.
  
• This process takes about 5-10 minutes. Your phone will reboot several times. The process ends when the progress field in the RSD Lite table is completely filled.
  
• Now you need to reset the settings (Optional, optional)
  
• Go to Settings>Privacy>then select>Factory Reset.
  
• Follow the instructions.
  
• The device will reboot and .... You will receive a completely new device.
  

Just a small FAK on RSD Litehere

• Instructions for restoring bootloader + Report on the operation from dear Alex469
  
• Universal Xoom Root - ANY XOOM ANY UPDATE (Universal Root for all devices and updates)
  
• About methods of getting root and possible problems with installing official updates from dear Alex469
  
• Installation instructions for US Xoom Wifi only (possibly for others) Canadian firmware 3.1 with root. - from the author Sammie
  
• Guideline for connecting to the 3G Internet from the operator Intertelecom Ukraine. from dear cccvvv
  
• Disassembly (in pictures)
  
• Disassembly (video)
  
• Solving the problem of time zones from dear hamer-gaa
  
• (Instructions) Restoring Xoom RSD Mode 2 LNX 0x0004
  
• Instruction on custom firmware, ICS 4.0.4 EoS Nightly from dear yamay and the second more complete instruction.
  
• Program prohibiting automatic update for custom firmware, from dear alex_boy and myself fast .
  
• Installing CWM for MZ606 only from dear Worldoggoo
  
• Step-by-step instructions for beginners how to flash the device from dear alex_boy
  
  
• Russification MOTOROLA XOOM. Final version! (12/24/2013)

Voting results: "Who is sitting on what"

The material presented on the page is unofficial (with the exception of official firmware), in the event of unsuccessful firmware or destruction of the device, the author of the software and the Administration do not bear responsibility for the resource! All actions are performed at your own risk!

Theme needs a curator! Those interested can leave a request in the topic.I want to be curator.
Pay attention to the requirements for candidates in the topic header!

Post has been editedVlad J.S. - 06.02.17, 11:03

Reason for editing: Russification MOTOROLA XOOM. Final version! (12/24/2013)

[freemsk1]

Instructions for unlocking the bootloader:
* Warning 1 * - These actions lead to a loss of warranty.
* Warning 2 * - A full hardware reset of your device (wipe) will be performed.

1. Download the latest driverhttp://developer.motorola.com/docstools/USB_Drivers/
   
2. Download the latest Android SDK and install them.http://developer.android.com/sdk/index.html
   Google has changed the location of some files. Go to the Platform Tools folder and copy everything into the Tools folder.
   
3. Open the command line in the folder with the installed Android SDK Tools.
   
4. adb reboot bootloader
   
   
5. XOOM will reboot into bootloader mode (the screen will show “Starting Fastboot Protocol Support.”)
   
6. fastboot oem unlock
   
   
7. We read the warning on the screen.
   
8. Press the volume-down button to select "Accept."
   
9. Press volume up to click on “Accept.”
   
10. After that, XOOM will be unlocked and formatted.
    

Post has been editedfreemsk1 - 28.02.11, 16:01

[freemsk1]

Instructions for getting root (thankshttp://twitter.com/koush):

1. Before getting root rights, you need to unlock the bootloader.Motorola XOOM - Firmware (OS 3.0) (Post # 6699907)
   
2. Download the file on the PC:xoomroot.zip(2.95 MB)
   
   
3. Unzip the contents to the folder with the installed Android SDK Tools.
   
4. Open the command line in the folder with the installed Android SDK Tools.
   
5. adb reboot bootloader
   
   
6. fastboot flash boot rootboot.img
   
   
7. fastboot reboot
   
   
8. We are waiting for the device to reboot
   
9. adb remount
   
   
10. adb push su / system / bin
    
    
11. adb shell ln –s / system / bin / su / system / xbin / su
    
    
12. adb shell chmod 4755 / system / bin / su
    
    
13. At this stage there are two options to choose from.
    Option A:
    adb push Superuser.apk / system / app
    
    Option B: Exit adb and download Superuser from the market.
    
14. Everything. Root rights obtained
    

K

This instruction is out of date. More recent information in the header section of the instructions.

Post has been editedgredmy - 06.08.12, 18:59

[vovkab]

freemsk1 @ 02.26.2011, 12:36

Instructions for unlocking the bootloader (thankshttp://twitter.com/koush):

mdja ... :)
Is this the official unlock in general where does koush come in?
Already even the article was onofficial blog, about the fact that there is nothing blocked, and unlocking occurs by standard means entering the android sdk. Namely, fastboot oem unlock, as well as on the Nexus S

[ilygor]

I wonder if it will be possible to install Android 2.3 with Flyer on it?

Post has been editedilygor - 28.02.11, 15:39

[freemsk1]

Instructions for overclocking the processor:

1. Preunlock the bootloaderandget root
   
2. Download and unzipxoom_ocboot.zip(2.94 MB)
   (The file contains boot.img with an overclocked kernel and the corresponding module for Wi-Fi)
   
3. Reboot to bootloader mode
   
   adb reboot bootloader
   
   
4. Flash the modified boot.img and reboot
   
   fastboot flash boot xoom_ocboot.img
   fastboot reboot
   
   
5. We transfer the module for Wi-Fi to the device and reboot
   
   adb remount
   adb push bcm4329.ko /system/lib/modules/bcm4329.ko
   adb reboot
   
   
6. Is done
   
7. Download SetCPU (version: 2.1.1 and above) we can change the processor frequency (Values: 1GHz, 1.2GHz, 1.4GHz, 1.504GHz)
   

Original article on XDAhttp://forum.xda-developers.com/showthread.php?p=11695470

Post has been editedfreemsk1 - 28.02.11, 19:23

[ilygor]

Freemsk1 @ 02.28.2011, 16:00

Instructions for overclocking the processor:

Overclocking for each core?

[Reactivator]

Can the cores work at different frequencies?

[freemsk1]

ilygor
Reactivator
According to the information from XDA - yes, overclocking for two cores and at the same frequency

PS: In the root guide, this step
adb shell ln –s / system / bin / su / system / xbin / su
I gave an error ...
It turns out that such a symbolic link is not necessary to create, it works without it.

[Incubus]

Freemsk1 @ 02.26.2011, 12:42

Open the command line in the folder with the installed Android SDK Tools.
Code
adb reboot bootloader

my adb writes: error device not found

in "my computer" xoom is visible.

Where I nakosyachil?

P.S. so unlock did, it was necessary to turn off xoom, then volume down + power, only after that fastboot saw xoom (adb still does not see)
fastboot oem unlock - and bootloader unlocked

I will fight with adb

Post has been editedIncubus - 10.03.11, 21:30

[freemsk1]

Incubus,
Applications ->Development ->USB debugging.
Ticked?

PS: most likely not

Post has been editedfreemsk1 - 13.03.11, 20:20

[Incubus]

Well, I did not doubt that I missed something. Jackdaw naturally did not stand.

Post has been editedIncubus - 11.03.11, 12:58

[apelsin12]

And who made 3g work at xoom?

[Remzy]

+1
You can install a fee
http://www.wired.com/gadgetlab/2011/02/tea...-xoom/?pid=1487
but a question of drivers

[lovlan]

Dear forum users please help. After attempting to reset fastboot oem unlock and unlocking the ROOT XOOM stopped loading. Only fastboot works. Is it possible to revive this device with something or has it turned into a pile of iron.

[PuhovI]

Friends, I ordered an American xoom, will it be difficult to Russify the OS?

[padrecc]

PuhovI @ 04/01/2011, 15:24

Friends, I ordered an American xoom, will it be difficult to Russify the OS?

But does it matter if you already ordered? :)

But seriously, MoreLocale (Morelocale) to help you.
Russification is not complete but very close to that.

And for this branch it is offtopic and you here>>Motorola XOOM - Discussion

Posted on 04/03/2011, 02:13:

Lovlan @ 03/30/2011, 09:58

Dear forum users please help. After attempting to reset fastboot oem unlock and unlocking the ROOT XOOM stopped loading. Only fastboot works. Is it possible to revive this device with something or has it turned into a pile of iron.

Judging by the description, you tried to get the root using the firmware method of the loader, which is for 3G only.
This is not fatal.
You as an option herehttp://forum.xda-developers.com/showthread.php?t=1010568

[lovlan]

I tried to use the instructions on the link provided by the respected padrecc, but "DUAL CORE" burns and burns, and then does not boot, adb does not work accordingly, before that I tried to fill in some version of the OS, now he writes ANDROID RECOVERY, and after a few seconds Entering Android recovery Mode, a then Reading ODM Fuse: 1 After rebooting, nothing happens again - M DUAL CORE freezes on the screen. What are the considerations?

[Zzoro]

XOOM Wi-Fi Got root by using a program with XDA. Wai file periodically "falls asleep", you have to switch. Is it from the root or is it all so?

[Alex469]

What kind of program is it for root? Link to the studio

[Zzoro]

Alex469 @ 04/04/2011, 23:33

then for the program for root? Link to the studio

http://forum.xda-developers.com/showthread.php?t=1011196