Database Info

[Q] XOOM - Update Issues with 3.x moved to ICS

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.

[Q] Need some help on reverting back to full stock

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.

[Q] Rooted Xoom Stuck on Bootloader

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.

[HELP!] Asus Fonepad 7 fe170cg stuck at lollipop

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 ..

Stuck at "Launching flashstock.bat"

So I had an old Nexus 5 running a custom KK rom. I tried getting it back to stock using Wugs Toolkit. I've been playing with it for hours trying to get it to work. I ended up making it worse and it gets stuck on Google Logo now. I tried using the revert to stock option on the toolkit. It looks like everything is working.. Here is the log..
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
fastboot getvar product
product: hammerhead
finished. total time: 0.001s
Launching flashstock.bat
and then it just stops.. I tried downloaded two seperate .tgz images from Google. They both do the same thing. It doesn't go out of the bootloader screen or anything. It writes the radios and that's about it.

This is a *very* high-level suggestion - there are many tutorials that take you through drivers/ADB, etc. I just want to give you the script I followed for the manual procedure, which turned out to be extremely quick and simple.
After suggesting Wugfresh's NRT to several people in these forums (I'm a very big fan) I decided to refresh my Nexus 6 with the latest image and make it unencrypted - a problem that doesn't exist on the N5. I wasn't sure that NRT would do this for me, since the script automatically restarts the device and I wanted to be sure that it didn't start before I had flashed a modified no-encrypt boot image, since it would just encrypt itself again. So I downloaded the factory image, a no-encrypt boot image (thanks, doitright ) and TWRP - naturally being very careful to get the right ones. I unzipped the TGZ and the image files down to their final *.img components. To make things simple I renamed the various images to one-word names (e.g. radio.img). I put all of them in the same directory as ADB & fastboot.
Since all Nexus devices are updated the same, this should also work for you. Since you've used NRT I'm guessing that you have the PC drivers already installed. You'll also need ADB/Fastboot. Switch on USB debugging, connect the N5 to your PC, and in a CMD window type these commands:
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery twrp.img
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot -w flash system system.img
fastboot flash cache cache.img
fastboot reboot
Some of these may be overkill (I believe the -w wipe command erases userdata anyway), but it worked for me.
I would say take a TWRP image first as well so that you can recover, but it sounds as if you have nothing to recover anyway.
If the more expert member want to suggest amendments to the script, I won't be insulted...

dahawthorne said:
Switch on USB debugging, connect the N5 to your PC, and in a CMD window type these commands:
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery twrp.img
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot -w flash system system.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
USB debugging means nothing if you're trying to use fastboot.
http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
gregs1213, stop using a toolkit, since you don't know what you're doing. read the above link and the following one as well:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

Just trying to help, beekay...
Thanks for the link - I'll read it carefully.

dahawthorne said:
Just trying to help, beekay...
Thanks for the link - I'll read it carefully.
Click to expand...
Click to collapse
Hey, sure, I didn't mean to "attack" you. I noticed that you wanted to help. Really. Thanked you for that.

No worries, beekay. Posts don't allways mean what they look like, which is why we have smilies.
And I did read the articles. I tried with my N6 to attach it in bootloader mode with no USB debugging, and you're absolutely right. I suppose I just read "Remember to switch on USB debugging" so often that I assumed it was needed for any sort of work. Thanks for the tip. It's things like this that encourage all of us to try new things - like flashing a ROM manually instead of with NRT...

This problem occurred to me when I updated Wugfresh NRT to 2.0.6.
So I return back to 2.0.5 and this problem solved.
Try using NRT 2.0.5 to see if the problem solved or not

mraramesh said:
This problem occurred to me when I updated Wugfresh NRT to 2.0.6.
So I return back to 2.0.5 and this problem solved.
Try using NRT 2.0.5 to see if the problem solved or not
Click to expand...
Click to collapse
Toolkits don't teach people stuff, they just hide it from them

mraramesh said:
The problem is Wugfresh NRT
Click to expand...
Click to collapse
I edited your post to show you the error of your ways
Sent from my Xperia z5 using Tapatalk

While replying to another thread asking for help in installing a ROM, I linked to this, and I notice that the OP never did tell us if he managed to get his device working. Feedback is not only helpful to the forum, it's also polite.
So bump for gregs1213's attention...