Flashed Build HWI69 for US Retail on a Canadian wifi MZ604 xoom..tired of
waiting for 3.1 update.
adb reboot bootloader
fastboot oem unlock
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
fastboot reboot
It is stuck on Starting RSD mode 2.
I can not get it to fastboot protocol...device does not turn off.
Any solutions?
Fastboot OEM lock is where you went wrong. Anyway see this thread.
OK I did this procedure yesterday but did not relock (I know it says to on the moto site but the guide I read said not to).
Anyway, pressing power and vol up will force a reboot. Unsure what will happen when it boots back up though...!
You should be fine. Only trying to relock will cause this error.
To get back to fastboot after a bad lock do this.
Power button and volume up, this will reboot the device.
As soon as the screen turns back on holds down power and volume down. In about 60 seconds your device should go to fastboot. Do not let go until it gets there.
Sent From My Evo
Thanks for the reply . It now says Failed to boot LNX 0X0004
Starting Fastboot protocol support
However it will not connect to xoom.
<wait for device> when issue fastboot command.
What the hell is going on?
you need to read this thread
http://forum.xda-developers.com/showthread.php?t=1108518
The exact thread I linked to...(-__-)'
I followed instruction from motorla dev support site.
"h**p://developer.motorola.com/products/software/?pubid=987654"
It uses command "fastboot oem lock"! So why did locking brick the device?
here it is:
Device Software Images
Select the appropriate device software image to download and re-lock your device. If you need to find your build number on your Motorola device go to Settings and About Phone or About Tablet.
The commands to flash and re-lock your device are as follows:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Note: If no userdata.img file is present in your download, please issue the command:
fastboot erase userdata
The Moto instructions are for locking the device back to it's own image. You are not using your device's own image. Every guide I've seen on here tells you not to relock, regardless of what Moto say. Believe the devs.
Thanxs
I now believe the devs......
Thanks for the reply. Sent the beast out to moto Canada today.
tfx1 said:
I now believe the devs......
Thanks for the reply. Sent the beast out to moto Canada today.
Click to expand...
Click to collapse
Try making or obtaining a factory cable which its different from an OTG cable. Start with the two links below. This might save the day.
http://forum.xda-developers.com/showthread.php?t=1077414
http://forum.xda-developers.com/showthread.php?t=1108518
Related
I tried to root my Motorolo Xoom 3G however after appliying fastboot reboot commend the device stays at the screen where Motorola logo and Dual core technology are.
The device is not responding any commend that I applied via PC.
I am able to enter fastboot protocol.
Here are the commends that I applied.
1 - adb reboot bootloader
2 - fastboot oem unlock
3 - fastboot flash boot boot.img
4 - fastboot reboot
After I applied all these commends , in MsDOS screen there were fihished text.
What should I do to start the device system again?
ssan said:
I tried to root my Motorolo Xoom 3G however after appliying fastboot reboot commend the device stays at the screen where Motorola logo and Dual core technology are.
The device is not responding any commend that I applied via PC.
I am able to enter fastboot protocol.
Here are the commends that I applied.
1 - adb reboot bootloader
2 - fastboot oem unlock
3 - fastboot flash boot boot.img
4 - fastboot reboot
After I applied all these commends , in MsDOS screen there were fihished text.
What should I do to start the device system again?
Click to expand...
Click to collapse
You can manually reboot by pressing volume up a power and holding until it reboots, then when you see the red dual core screen tap volume down and then volume up. You should be back in 'starting fastboot protocol' again. Make sure you have actually unlocked. Try fastboot oem unlock again and if it gives you instructions on the Xoom screen, follow them all. It should reboot into the os...skip all set-up steps except go into settings /applications/development and make sure debugging is checked. Then reboot back into fastboot and continue with what you are doing.
I unlocked it again however still it stucks at the Dual core screen. Is there any other operation to start the system.
By the way, I am using a Turkish version of Motorola Xoom 3g. I guess it is an important detail.
I have resolved the problem.
I downloaded MZ601_H.6.1-38-11_Retail_Turkey file from motorolo developer web site.
Fastboot flash boot bot.img
Fastboot flash system system.img
Fastboot flash recovery recovery.img
Fastboot flash userdata userdata.img
Fastboot erase cache
applied the above commends.
ssan said:
I have resolved the problem.
I downloaded MZ601_H.6.1-38-11_Retail_Turkey file from motorolo developer web site.
Fastboot flash boot bot.img
Fastboot flash system system.img
Fastboot flash recovery recovery.img
Fastboot flash userdata userdata.img
Fastboot erase cache
applied the above commends.
Click to expand...
Click to collapse
Great news! It's so good when you can resolve your own problems!
I feel really sorry that I have to part with this device when I've only owned it for a couple of days. But I have to do it!
OK, I'll get straight to it:
1. I was on ICS 4.0.4 Stock,un-rooted and boot loader remained locked.
2. Then I decided to Unlock the Bootloader and flash the Twrp recovery and then I flashed the EOS Jelly Bean stable for MZ604 WiFi UK version.
3. I need to get it back to stock. As in, stock ICS, un-rooted and bootloader relocked (If that's possible).
4. Now I'm not that kind of guy that will ask a question before doing loads of research on a thing. So this is what I found out but just need some confirmation from some experienced Xoom users who have done this procedure before. First of all I've read through this Official Xoom website: http://developer.motorola.com/products/software/ And then I figured that I have to download this version:
Build H.6.2-24 for Retail Europe
MD5 Sum: cae470d91a6f6e1473f981bc06f452fd
Spain, Italy, Austria, Switzerland, UK, Sweden, Norway, Denmark, Netherlands 118 MB Jun. 2, 2011 MZ604 Product Specs Download
Since I do live in the UK. And then after that I would have to follow these instructions given by Motorola themselves:
INSTRUCTIONS TO FLASH & RE-LOCK YOUR MOTOROLA XOOM:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
And by this I'm guessing they mean, first download the Zip and then extract all of the files to the place where the file ADB and Fastboot reside. And then put your motorola xoom in fastboot mode by connecting it to the computer via the motorola usb cable that was provided in the box. And have usb debugging enabled. Then open command prompt and type in adb reboot bootloader. Which would then reboot to fastboot mode and then you'd have to type in these commands.
Also would I have to type these commands seperately right?
So first: Typing in command prompt: fastboot flash boot boot.img
Then after that has finished I do the next and the next and the next until it comes down to the "fastboot oem lock" which I guess should be the relocking part and the other parts were flashing the stock img and removing the recovery in order to put everything back the way it was before.
So now after following all those instructions, I'm guessing that everything should be back as it was before. As in, I could easily go and hand this in the store that I bought it from and they wouldn't notice a single thing. Right? And of course the tablet would be running stock ICS 4.0.4, unrooted and bootloader locked, right?
I would really appreciate anyone reading through these instructions and maybe confirming if they are right or if they are wrong, could you please show me the right way?
Thank you very much
With regards,
Beston94
This is all you should do,.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache..
an unlock bootloader still update..i never lock back mine..
tumpy said:
This is all you should do,.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache..
an unlock bootloader still update..i never lock back mine..
Click to expand...
Click to collapse
Perhaps you misunderstood me because I don't need to update but I need to return it as it was.
Hey everyone, I rooted my Xoom MZ601 a while back using this method. I installed the Team EOS XOOM ROM and is updated to the latest nightly build. I want to return to stock following these instructions from thr MOTO Dev Site. The only thing is I can't even get into the Bootloader. I've tried doing it manually on the Xoom itself and also through ADB. It restarts and shows the "Dual Core" screen, then I get the "Starting Fastboot protocol support." message and that's as far as it goes. I have to do a hard-restart to get it back operational. Any ideas how I can fix this please?
Thanks
ADB is the wrong method for flashing back your image files.
You have to use fastboot. LOL it even says on it the website http://developer.motorola.com/products/software/
Instructions to Flash & Re-Lock Your Motorola XOOM:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Please post all questions in the Q & A section. Thanks! Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2
Chaosgod27 said:
ADB is the wrong method for flashing back your image files.
You have to use fastboot. LOL it even says on it the website
Instructions to Flash & Re-Lock Your Motorola XOOM:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Click to expand...
Click to collapse
Ok thanks, I issued the commands within the folder that I extracted the files into, now it just says <waiting for device >. The Xoom isn't doing anything. It is set to USB Debugging mode and is connected directly to the motherboard USB's. Any ideas? Thanks
efrant said:
Please post all questions in the Q & A section. Thanks! Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Sorry and thanks
No worries, I've done it thanks
You have to be in the bootloader. Since you're using TeamEOS rom hold down the power button, click on restart and goto bootloader. Then try them again.
Hello
I have a Motorola Xoom from Verizon, and this is the issue.
When I turn on, the tablet it's stuck in M logo screen, I already read almost any information about this issue, but still I can't use my xoom.
I already done this: the bootloader is already unlock
a) Files From MZ600 HRI39
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
b) used RSD method
c) used recovery method too
I had used every method on this forum to recover my Xoom, and nothing seems to work, at this time I don't know what else do.
adb commands doesn't work for me, only with fastboot and RSD is visible my device.
At this time I accept any sugestions, Since apply a factory reset, or install a new Android version
Long story short I bricked my phone when trying to flash recovery using toolkit. Now my phone won't turn on and recovery is gone as well. Somehow my PC can recognize the phone in fastboot mode although there's nothing showing on the screen.
So I tried the method in this thread:
http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696
It shows I flashed everything and it shows green color in the tool but when I checked the partitions, boot.img, recovery.img, userdata.img, system.img, etc are still broken. At that time the bootloader was still unlocked.
Since my computer can still see the phone in fastboot so I tried to flash the original image in fastboot. Again everything went through with no error but the phone still wouldn't turn on and the partitions are still same broken/corrupted. However the bootloader became locked after this. So now I end up with no more solutions. Since bootloader says locked(although boot.img is actually corrupted) I can't flash or do anything in fastboot command.
So I guess I'm really SOL right now... My only hope right now is maybe there will be USB JTAG or Nand flasher but I don't know if anyone can repair that right now.
Any suggestions?
fastboot oem unlock
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
Now use twrp or cwm or whatever
fastboot boot recovery nameofrecovery.img
If your phone boots to recovery you may consider running e2fsck against data and cache partitions through adb shell
Best of luck