Hi I am from Turkey and I have a Motorola Xoom MZ601 EU version. I counld't find the lastest stock rom(4.0.4). Can anyone help me about this?
Last edited:
[INFO]Stock Images & Other Links
- Thread starter bwcorvus
- Start date
I need help please. Im trying to install sdk on my macbook with parallels running win 8. It will not install. What should I try to fix it?
Hi,
I have the US Verzion Wifi version. Is it M601 or what version it should be???
Thanks.
I have the US Verzion Wifi version. Is it M601 or what version it should be???
Thanks.
I'm not sure why but Chrome says the windows drivers file is malicious, anyone else get that?
Hi guys
Which one do I use if I want to reset my MZ601 HK version (to avoid that dreaded 4GB partition issue)?
Which one do I use if I want to reset my MZ601 HK version (to avoid that dreaded 4GB partition issue)?
xoom mz601 other intern. rental
I have flash my xoom with stock imej.. working fine but cant get official update for 3.2 or 4.0.4.. any help.. thanks..
I have flash my xoom with stock imej.. working fine but cant get official update for 3.2 or 4.0.4.. any help.. thanks..
Hi,
Is anyone able to re-upload the below image... it has been deleted.
Build H.6.2-24 for Retail Other International f0b99865cc9dfa48dce95f81e8219919
I have searched the hell out of google with no success. Any help would be greatly appreciated.
Cheers.
Is anyone able to re-upload the below image... it has been deleted.
Build H.6.2-24 for Retail Other International f0b99865cc9dfa48dce95f81e8219919
I have searched the hell out of google with no success. Any help would be greatly appreciated.
Cheers.
Very useful, thank you very much
I was planning to return my Motorola Xoom ROM's to the stock version.
I was planning to return my Motorola Xoom ROM's to the stock version.
I have some files here, including some OTAs.
https://www.mediafire.com/folder/9cb3cc6g918qb/xoom
Build H.6.2-21 for Brazi
MZ604_HWI69.zip
e379f0b9bcd0.signed-tervigon-HMJ37-from-HWI69.e379f0b9.zip
db223b6ed7c4.signed-tervigon-HTJ85B-from-HMJ37.db223b6e.zip
736173006aa3.signed-tervigon-HTK55D-from-HTJ85B.73617300.zip
01cd4f05157a.signed-tervigon-HTK75D-from-HTK55D.01cd4f05.zip
71a21bfe7c81.signed-tervigon-IML77-from-HTK75D.71a21bfe.zip
0d062b3bcbc7.signed-tervigon-IMM76-from-IML77.0d062b3b.zip
f85d815e2b75.signed-tervigon-JRO03H-from-IMM76.f85d815e.zip
75baa1719d30.signed-tervigon-JZO54K-from-JRO03H.75baa171.zip
Build HWI69 for US Retail
MZ604_H.6.2-21_Brazil.zip
Blur_Version.6.2.21.MZ604.Brasil.en.BR.zip
Blur_Version.64.0.20.MZ604.Brasil.en.BR.zip
https://www.mediafire.com/folder/9cb3cc6g918qb/xoom
Build H.6.2-21 for Brazi
MZ604_HWI69.zip
e379f0b9bcd0.signed-tervigon-HMJ37-from-HWI69.e379f0b9.zip
db223b6ed7c4.signed-tervigon-HTJ85B-from-HMJ37.db223b6e.zip
736173006aa3.signed-tervigon-HTK55D-from-HTJ85B.73617300.zip
01cd4f05157a.signed-tervigon-HTK75D-from-HTK55D.01cd4f05.zip
71a21bfe7c81.signed-tervigon-IML77-from-HTK75D.71a21bfe.zip
0d062b3bcbc7.signed-tervigon-IMM76-from-IML77.0d062b3b.zip
f85d815e2b75.signed-tervigon-JRO03H-from-IMM76.f85d815e.zip
75baa1719d30.signed-tervigon-JZO54K-from-JRO03H.75baa171.zip
Build HWI69 for US Retail
MZ604_H.6.2-21_Brazil.zip
Blur_Version.6.2.21.MZ604.Brasil.en.BR.zip
Blur_Version.64.0.20.MZ604.Brasil.en.BR.zip
Hi Guys
I am looking for the same file (I hope that it will include additional languages like Polish language)
Update: nevermind. the standard one has Polish language included. don't need the "other" one.
Sorry for such a panic
Last edited:
Need stock MZ602 sbf...
I've chased just about every thread I can find. My MZ602 Xoom (Verizon, WiFi + 4G LTE) locked up and now just boots to the "M" "Dual Core" screen. I had never unlocked or rooted the device. I was just able to unlock the bootloader, and was hoping to just flash the stock image back on it to see if I can get it working again. Sorry for being so late to the party...
I've chased just about every thread I can find. My MZ602 Xoom (Verizon, WiFi + 4G LTE) locked up and now just boots to the "M" "Dual Core" screen. I had never unlocked or rooted the device. I was just able to unlock the bootloader, and was hoping to just flash the stock image back on it to see if I can get it working again. Sorry for being so late to the party...
I've got a copy of a stock image for the MZ604 (Honeycomb version). Pretty sure (from what I remember anyway) it will work on the 602 also. You'd only have wifi though. No Verizon service. Also, my guess is you'd have to have your Xoom unlocked to flash it (from your post, it looks like you already did that). I doubt it would flash if you're not unlocked since it's the wrong software for your version of Xoom. I could be wrong about that though. I don't know. Anyway, if you can't find the right file for your device and wanted to play with it a bit, I could upload it somewhere for you. Up to you.
Hi, does anyone have a stock rom 3.2 or 3.2.2 for MZ616, Brazilian version? I am stuck in the infinite loop at booting.
Thank you!!!
Thank you!!!
Thank you
WAO! Thank you so much i tught i bricked my xoom and forcing the fastboot commands with the restart i could restore to factory! thank you again sir.
WAO! Thank you so much i tught i bricked my xoom and forcing the fastboot commands with the restart i could restore to factory! thank you again sir.
hello, my device Xoom MZ600 - where i may take ROM for fastboot Android 4.....+ ?
Failed image LNX 0x0002
Hi folks, I'm wondering if someone here has the know-how to help me out with a possibly bricked Xoom MZ601 after I tried to flash it back to stock firmware.
I'm now getting the following message in the top-left corner when I turn on the device:
Failed image LNX 0x0002
Starting RSD mode 2
If I restart it by holding the Vol Down button, I get this instead:
Failed image LNX 0x0002
Starting Fastboot protocol support
At this point the device should be recognised by my PC when I connect it via USB cable, and I should be able to run ADB or Fastboot commands from my PC, but in fact it is not recognised at all and ADB/Fastboot commands don't work (I get "waiting for any device" when I run them from the Command Prompt).
And yes, I do have the Motorola v6.4.0 USB drivers installed on my PC. I was able to successfully use ADB and Fastboot commands previously.
Here's what I did to get to this point:
Originally the Xoom had some custom ROM on it - not sure which, but it was definitely not stock. I wanted to return it to stock, so I downloaded one of the stock firmwares from the first post in this thread (which also matched the MD5 checksum of one of the stock firmwares from https://motorola-global-portal.custhelp.com/app/standalone/rom-images so I know the firmware was good).
I installed the Motorola USB drivers on my PC, connected a USB cable to the Xoom, and ran "adb reboot bootloader". The Xoom rebooted into Fastboot mode.
Then I unlocked it by running "fastboot oem unlock" and confirming the prompts. This worked, and the Xoom rebooted itself.
I then rebooted it back into Fastboot mode and ran the following commands in succession:
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
Each command was successful. A "succesful" message was displayed both on the Xoom itself and also in the Command Prompt window on my PC for each command.
But after running the final comand: "fastboot oem lock" - and confirming the prompt it gave me - the device tried to reboot, but then started to display the error message I mentioned above, and won't go any further than that. It's also not possible to turn it off anymore. If I push Power + Vol Up, it will turn itself off, but then it automatically turns back on after a few seconds. The only way I'll be able to turn it off will be to let the battery drain out.
I've read elsewhere that this scenario can happen if you "oem lock" the device after flashing a custom ROM. But I haven't done that - I've locked the device after flashing an official stock ROM, following the instructions on Motorola's own page. So I don't understand why this has happened.
Anyway it seems to be bricked, but the question is how to unbrick it. As I mentioned, it is no longer detected by my PC anymore, even when I put it into Fastboot mode. I've tried this on two different PCs. So there's no chance to run any ADB or Fastboot command on it currently.
Any ideas?
Hi folks, I'm wondering if someone here has the know-how to help me out with a possibly bricked Xoom MZ601 after I tried to flash it back to stock firmware.
I'm now getting the following message in the top-left corner when I turn on the device:
Failed image LNX 0x0002
Starting RSD mode 2
If I restart it by holding the Vol Down button, I get this instead:
Failed image LNX 0x0002
Starting Fastboot protocol support
At this point the device should be recognised by my PC when I connect it via USB cable, and I should be able to run ADB or Fastboot commands from my PC, but in fact it is not recognised at all and ADB/Fastboot commands don't work (I get "waiting for any device" when I run them from the Command Prompt).
And yes, I do have the Motorola v6.4.0 USB drivers installed on my PC. I was able to successfully use ADB and Fastboot commands previously.
Here's what I did to get to this point:
Originally the Xoom had some custom ROM on it - not sure which, but it was definitely not stock. I wanted to return it to stock, so I downloaded one of the stock firmwares from the first post in this thread (which also matched the MD5 checksum of one of the stock firmwares from https://motorola-global-portal.custhelp.com/app/standalone/rom-images so I know the firmware was good).
I installed the Motorola USB drivers on my PC, connected a USB cable to the Xoom, and ran "adb reboot bootloader". The Xoom rebooted into Fastboot mode.
Then I unlocked it by running "fastboot oem unlock" and confirming the prompts. This worked, and the Xoom rebooted itself.
I then rebooted it back into Fastboot mode and ran the following commands in succession:
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
Each command was successful. A "succesful" message was displayed both on the Xoom itself and also in the Command Prompt window on my PC for each command.
But after running the final comand: "fastboot oem lock" - and confirming the prompt it gave me - the device tried to reboot, but then started to display the error message I mentioned above, and won't go any further than that. It's also not possible to turn it off anymore. If I push Power + Vol Up, it will turn itself off, but then it automatically turns back on after a few seconds. The only way I'll be able to turn it off will be to let the battery drain out.
I've read elsewhere that this scenario can happen if you "oem lock" the device after flashing a custom ROM. But I haven't done that - I've locked the device after flashing an official stock ROM, following the instructions on Motorola's own page. So I don't understand why this has happened.
Anyway it seems to be bricked, but the question is how to unbrick it. As I mentioned, it is no longer detected by my PC anymore, even when I put it into Fastboot mode. I've tried this on two different PCs. So there's no chance to run any ADB or Fastboot command on it currently.
Any ideas?
Thanks for the links. The Build H.6.2-24 for Retail Other International f0b99865cc9dfa48dce95f81e8219919 isn't available at the download location.
New posts
-
[OFFICIAL] [NIGHTLIES] LineageOS 17.1
- Latest: sir_overthrow
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone