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.
Related
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
My Xoom has had an odd problem. When I got it new, I unlocked the bootloader and rooted.
However, any pushed updates from Moto such as HLK55 caused my Xoom to boot and show the unhappy !Android icon. I had to shut down cold, and reboot. In other words, it never updated properly.
Now that ICS is out, I have Kang 1/15 running but have some non-crash issues. I'd like to flash to try to update to the factory ICS push file but fear that my XOOM won't complete as well.
Any ideas?
So long as you flash back to complete stock using the Motorola files you should be able to upgrade your way up to ICS (via 3.1 and 3.2).
Get the files from http://developer.motorola.com/products/software/
And as on that page, get ADB running and make sure it detects your device then run these commands.
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
Make sure you get the right version for your device.
Hey guys,
I got this Motorola Xoom from a friend that he wanted updated. He got the Xoom from a contact in Motorola. The thing is nothing shows up in software updates, then I checked the version number
trygon-userdebug 3.1 HMJ37 124251 test-keys
I figured test-keys release won't get the ota notification. I want to update it to Jellybean, so what options do I have? Official JB is preferable but if there's no way out of this then I can root.
I'd like to add, I have no clue which Xoom this is. It is 32gb, has some sort of slot on top(not sure simcard or what). And I can't find the model number anywhere on the body or in settings.
I connected to PC and saw MZ604. I'm checking out the images section now.
Ok I assume I can download a stock image and then put them files in the fastboot folder and flash via these commands
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
death__machine said:
Ok I assume I can download a stock image and then put them files in the fastboot folder and flash via these commands
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
That'll do it.
Do I have to unlock before doing any of the above? I got these steps from http://forum.xda-developers.com/showthread.php?t=1081519
Please post all questions in the Q & A section. Thanks! Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2
My bad! Apologies.
I used a European Image and flashed it successfully. It was a Honeycomb image, I updated it a lot of times till it reached 4.0.4. Hmm, so there's no jellybean yet for people running European Firmware I read. Another issue was play store kept saying server error.
I googled the Server Error and sorted it is. Thanks guys!
I can understand this is very old post. But I see you said you sorted this by using European Image and flashed it successfully. can you tell me which European image you used ?
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
3 days ago I got a lollipop ota update to my fe170cg. Everything is cool except rooting. I want to root this device like a used to do at kitkat.
But I couldn't find any solution to root this device. I also tried VampireFo's tethered CWM recovery but no luck with that it is not even flashing CWM because of the tigth locked asus lollipop bootloader. I also tried to downgrade to kitkat because of the lollipop recovery But I couldn't downgrade. Now I have no more chance to root this device. And no chance to downgrade to kitkat as well. So I decided to ask professionals like you. I really need help!!. Any help would be appreciated. Thanks from now for any response.
FreeAgentNBS said:
3 days ago I got a lollipop ota update to my fe170cg. Everything is cool except rooting. I want to root this device like a used to do at kitkat.
But I couldn't find any solution to root this device. I also tried VampireFo's tethered CWM recovery but no luck with that it is not even flashing CWM because of the tigth locked asus lollipop bootloader. I also tried to downgrade to kitkat because of the lollipop recovery But I couldn't downgrade. Now I have no more chance to root this device. And no chance to downgrade to kitkat as well. So I decided to ask professionals like you. I really need help!!. Any help would be appreciated. Thanks from now for any response.
Click to expand...
Click to collapse
Hey there!
Not sure this will help you or not..for me it just doing good. Try use fastboot
fastboot erase cache
fastboot erase system
fastboot erase userdata
Then you need you flash the a stock firmware. UL-K012-WW-11.2.3.33-user
Download the appropriate firmware from Asus website. There are three .img files in the firmware zip file (fastboot.img, boot.img, splashscreen.img).
Copy all these three files to the extracted folder. Now type the following command in the command window one by one:
fastboot flash fastboot fastboot.img
fastboot flash boot boot.img
fastboot flash splashscreen splashscreen.img
fastboot reboot-bootloader
then you get your droidboot back.
user Temp CWM IntelAndroid-FBRL-05-16-2015-PTR to flash UL-K012-WW-11.2.3.33-user
so that you can downgrade to kitkat
BigBadWolf90 said:
Hey there!
Not sure this will help you or not..for me it just doing good. Try use fastboot
fastboot erase cache
fastboot erase system
fastboot erase userdata
Then you need you flash the a stock firmware. UL-K012-WW-11.2.3.33-user
Download the appropriate firmware from Asus website. There are three .img files in the firmware zip file (fastboot.img, boot.img, splashscreen.img).
Copy all these three files to the extracted folder. Now type the following command in the command window one by one:
fastboot flash fastboot fastboot.img
fastboot flash boot boot.img
fastboot flash splashscreen splashscreen.img
fastboot reboot-bootloader
then you get your droidboot back.
user Temp CWM IntelAndroid-FBRL-05-16-2015-PTR to flash UL-K012-WW-11.2.3.33-user
so that you can downgrade to kitkat
Click to expand...
Click to collapse
Thanks a lot It worked :good:
thanx a lot it worked
It worked at-last ....
BigBadWolf90 said:
Hey there!
Not sure this will help you or not..for me it just doing good. Try use fastboot
fastboot erase cache
fastboot erase system
fastboot erase userdata
Then you need you flash the a stock firmware. UL-K012-WW-11.2.3.33-user
Download the appropriate firmware from Asus website. There are three .img files in the firmware zip file (fastboot.img, boot.img, splashscreen.img).
Copy all these three files to the extracted folder. Now type the following command in the command window one by one:
fastboot flash fastboot fastboot.img
fastboot flash boot boot.img
fastboot flash splashscreen splashscreen.img
fastboot reboot-bootloader
then you get your droidboot back.
user Temp CWM IntelAndroid-FBRL-05-16-2015-PTR to flash UL-K012-WW-11.2.3.33-user
so that you can downgrade to kitkat
Click to expand...
Click to collapse
:good::good::good: Thank you so much dude..:highfive: :victory: Now it is working ..