Database Users

OUTDATED[Guide] Setting up/using adb/fastboot-unlock, flash custom recovery & root

OUTDATED[Guide] Setting up/using adb/fastboot-unlock, flash custom recovery & root
Below is a great guide to rooting, from several sources, (mostly taken from pingvinen's "An Idiot's Guide to Flashing the Xoom" and a guide by publicanimal. and I hope it helps. You can find the links to all of the files referenced below in the Xoom Heaven thread (thanks StrifeSoldierVII!)[/I]
(New thread in General Section by Jack207407 will have all the updated links for flashing
http://forum.xda-developers.com/showthread.php?t=1443110
One Stop For ROM's, MOD's, and Root Wifi-Only and 3G/4G Models)
"What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and don't try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned.
HERE'S THE USUAL DISCLAIMER--I AM NOT RESPONSIBLE FOR ANY HARM THAT MAY COME TO YOUR DEVICE IF YOU FOLLOW ANY PART OF THIS GUIDE--ANY RISK IS ON THE USER!
I strongly recommend you to read the entire guide before trying. In fact, read it twice to ensure that you have understood everything. If there is weird stuff that you don't understand, don't hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but no one (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
Just a note before we begin: the different Xoom. Models that are able to use this guide are the following:
MZ600 - stingray_cdma - Motorola US 3g Xoom (technically this device is stingray as well, but I will be using stingray_cdma as the two devices have incompatible software)
MZ601 - utms_everest - Motorola EU 3g Xoom
MZ602 - stingray - Motorola US 4g Xoom
MZ604 - wingray - Motorola Wifi Xoom
(thanks solarnz!)
___________
Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity) 2. Install Java SDK and Android SDK tools (for adb and fastboot commands) 3. Unlock the device for flashing (allowing replacement of recovery and boot images) 4. Install a modified recovery image (ClockWorkMod recovery for Android) 5. Root the device (Allow r/w access to the device filesystem) 6. Flash a kernel that supports overclocking etc.
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows PC. Windows 7, Mac and Linux users will probably have to do some steps differently.
1.0 Install the latest Motorola USB drivers
The installation file can be found at: http://developer.motorola.com/docstools/USB_Drivers/
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2.0 Installation of development software
Android SDK and Java SDK need to be installed. You can find the installation kits here.
http://developer.android.com/sdk/index.html In case you can't find fastboot.exe, look for it here (thanks to jerrycycle): http://forum.xda-developers.com/showpost.php?p=19546334&postcount=5
Update: you could also just install the adb fastboot pack here:http://www.android.net/forum/downloads.php?do=file&id=67
http://www.oracle.com/technetwork/java/javase/downloads/index.html
2.1 Install them as any other software, making an Android SDK folder on C/.
2.2 Make sure that all the files you need are in the Platform Tools folder (fastboot, recovery image file and so on). Copy any files in the Tools folder to the Platform Tools folder if necessary. Note: If the Android SDK complains that the Java Dev Kit can't be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
(Warning: Never put any zip files in your Platform Tools folder. Flashing zip files through fastboot will cause very serious problems. Zip files must be flashed from the external micro SD card through CWM recovery on the Xoom...we'll get to that later.)
2.3 Test that ADB and FASTBOOT works. You should open a command window by right clicking in your Platform Tools folder where all of your files are, plug in your Xoom to your computer with your Motorola cable (it may not work with a generic cable) and write 'adb devices'. Your Xoom should now be listed. Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom.
Optional: Those that want to be able to access adb from any where on their computer, here's a tip from scsa20: "For windows, if you go into System Properties and choose Advanced, then Environment Variables..., you'll be able to edit the Path variable under System variables, just add the path to where adb and fastboot is located (separated with a semi-colon ().
Here's what my Path variable looks like:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%Sy stemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\ System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\android-sdk-windows\tools;C:\android-sdk-windows\platform-tools;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\
It's long but do you see the android stuff there at the end?"
Update: xda poster Mandelbrot Benoit suggests an alternate adb setup, here: http://forum.xda-developers.com/showpost.php?p=18072572&postcount=50
If your windows computer doesn't see your Xoom, consider this (Originally Posted by AngryBulleteyeTruth):
When the xoom does not show up on PC it may be the problem of.... windows media player!
Xoom uses drivers of WMP to communicate with PC. If someone does not have the newest WMP drivers it will not show up and you can see xoom device in the devices tab on PC having an exclamation mark.
So the solution is to download and install Windows Media Player 11. It has worked for me.
--------
OK. Now that you are set up, it's Showtime! Take a deep breath...
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to secure important data before you start. (It will also void your warranty, so you still have time to go back.)
3.1 Power up and start the Xoom.
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode.
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal. Don't bother to do any setup at this time, just make sure that USB debbuging is checked in settings, and now go on to step 4
4. Install recovery image (CWM) UPDATED 4/19/12
If you haven't done it already, download the recovery image file and save it to your computer in the Platform Tools folder.
(Download the recovery image from this link: http://forum.xda-developers.com/showthread.php?t=1604014 only the img file flashed through fastboot Remember, never try to flash a zip file through fastboot!)
Important: At this time, make sure you have a good (known to be working) microsd card in your sdcard slot in your Xoom. Reboot the Xoom with the sdcard in the slot to make sure it's mounted.
4.1 Boot into flash mode with 'adb reboot bootloader.'
4.2 Install your downloaded recovery image: 'fastboot flash recovery eos-recovery-r6.img' or whatever is the exact name of the recovery img file you are flashing.
4.3 Enter CWM recovery with the procedure below.
4.4 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work (if you see Starting Fastboot Protocol), experiment with the timing (see below).
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for getting this far!
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. Just repeat steps 4.1 through 4.6 if that happens.
UPDATE(12/28/11) Since putting this guide together, Motorola has issued a number of Over-the-Air (OTA) updates that have complicated the process of flashing the Clockawork Mod recovery, so if you have accepted any OTA updates, please read the following, which describes each step (http://forum.xda-developers.com/showthread.php?p=26009191#post26008083) (Thanks to Landorin.)
(If you have root and want to remove these files, remove or rename /system/etc/install-recovery.sh with something like root explorer. You can then flash your custom recovery through fastboot again.)
For those of you that get stuck with some error like 'device not recognized' poster Madjinj gives the following advice:
1) Be sure that you have your adb folder in the root of C drive directly and be sure that you are in adb folder in command prompt program (CMD in Windows machines) i.e by typing "cd c:\XXX" where XXX is the name of adb folder in your machine.
2) Be sure that you type "adb reboot bootloader" in comand prompt to activate adb program. if the problem persists, try typing "fastboot reboot" then after reboot type "adb reboot bootloader" in command prompt program.
3) Use the USB cable that came with your Xoom (some cables are not good in flashing for unknown reason..!!
4) make sure that you activate USB debugging mode.
5.0. Rooting the Xoom
The Universal Xoom Root zip file from solarnz is located here: http://forum.xda-developers.com/showthread.php?t=1242241
5.1 You need to transfer the Universal Xoom Root zip file to a working external micro SD card. You can do this on a computer or cell phone, but the Universal Xoom Root zip file must be located in the root directory of the micro SD card.
5.2 Insert the now prepared SD card in the Xoom.
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option.
5.4 Select 'Install ZIP from sd card.'
5.5 Select 'Choose ZIP.'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install any app requiring root and start it. If the rooting was successful, then the app should request superuser permission and you should be able to grant it without any problems.
6. Flashing a new rom or kernel...(e.g. Tiamat Moray Rom and/or Odachi Kernel). Look in the Xoom Heaven thread or in the Development section of this form for all of these files.
6.1 This step is identical to 5, but swap out the ROOT zip for the ROM or KERNEL zip. For simplicity, you may want to prepare the micro SD card with both zip files at the same time in step 5.1..."
------------------------
This is still one of the best explanations of how to use adb and fastboot to unlock and root the Xoom and install a custom recovery, etc, and doesn't deserve to buries on back pages of this forum. Hopefully, the step-by-step nature of this guide will help those of you that have limited experience with this kind of tinkering.
Oh, and please feel free to correct any errors or omissions. As I said, it came from several sources and needed to somewhat updated.

Thank you, just bought my xoom yesterday and was confused on the steps to take!
This has made it as clear as possible for me and will follow your instructions to the letter tonight.
Sent from my MZ604 using xda premium

fastyan said:
Thank you, just bought my xoom yesterday and was confused on the steps to take!
This has made it as clear as possible for me and will follow your instructions to the letter tonight.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
Good luck! Let us know how you make out and if anything needs to be clarified.

think im doing something wrong as unlocked fine but when i go to install the recovery file it keeps coming up cannot load? any ideas where im going wrong?
been at it 3 hours now lol and losing the will to live im sure its gona be something simples

fastyan said:
think im doing something wrong as unlocked fine but when i go to install the recovery file it keeps coming up cannot load? any ideas where im going wrong?
been at it 3 hours now lol and losing the will to live im sure its gona be something simples
Click to expand...
Click to collapse
Check to make sure that your file download is good, and that you are typing it's name correctly. Better yet, you could rename the file "recovery.img" and that will make it very easy to get it right.

On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium

fastyan said:
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
When you're in the bootloader, you won't be able to access the SD Card or anything of that sort and adb won't work, in stead, when you're in the bootloader, you're switching over to fastboot. I'm sure if you type in fastboot devices you'll see your xoom listed.

Thank you for the reply and that's one thing sorted but any idea why its telling me "cannot load recovery"? I have tried renaming it and downloaded the recovery file 4 times incase that was wrong but still no joy :-(
I have done this all before on my phone and never had a problem so I must be missing something but f$*@ed if I know what?
Thanks again for your help though.
Sent from my Desire HD using xda premium

Just had a thought. Could it be that the XOOM hasn't actually unlocked, would that cause it to not load? Is there any way to check if its unlocked successfully? Although I did try it twice before?
Sent from my MZ604 using xda premium

Once you got it in the bootloader, you gotta make sure you do fastboot oem unlock, press volume down then up, press volume down again then up again, and let it format and reboot.
If it's already unlocked, you'd get a message telling you so (generally).
Then when you go to flash the recovery, make sure that the recovery image is in the folder where fastboot is and type in fastboot flash recovery recovery.img (if I remember the syntax that is, I'm at work and don't feel like scrolling up or going into the root guide to confirm xD ).

fastyan said:
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium[/QUOTE
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
Click to expand...
Click to collapse

okantomi said:
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote.Oof course the cwm recovery img.. goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
Click to expand...
Click to collapse
With the way I have my system setup, I can run adb and fastboot wherever I am

No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
No progress yet as im at work but when I get home I will start the process from scratch again and see how I get on and will keep you posted.

scsa20 said:
With the way I have my system setup, I can run adb and fastboot wherever I am
Click to expand...
Click to collapse
Care to share???
That would be helpful to many, I'm sure. We could add it to the guide, along with anything else you can think of.

fastyan said:
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
No progress yet as im at work but when I get home I will start the process from scratch again and see how I get on and will keep you posted.
Click to expand...
Click to collapse
If, as you follow this guide, you find any explanations that are not clear or if you think of a step to take or something else that might improve the guide, please post it and we can add it in. It's been almost 6 months since I've unlocked and at least a couple of months since I've had to use adb, so I'm sure I've forgotten some things. Those of you whose experience is fresh can give really good advice. That's how this guide was originally written, by pingvinen, right after he had gone through a grueling rooting process.

okantomi said:
Care to share???
That would be helpful to many, I'm sure. We could add it to the guide, along with anything else you can think of.
Click to expand...
Click to collapse
For windows, if you go into System Properties and choose Advanced, then Environment Variables..., you'll be able to edit the Path variable under System variables, just add the path to where adb and fastboot is located (separated with a semi-colon (;)).
Here's what my Path variable looks like:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\android-sdk-windows\tools;C:\android-sdk-windows\platform-tools;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\
Click to expand...
Click to collapse
It's long but hey, see where the android stuff is near the end?

@Okantomi:
We all have learned some things from trial & error (eg.the sk cannot detect java dev kit)
i could only flash recovery after renaming it to recovery(do not forget to add.img in cmd while flashing).also the official motorola name recovery as same.
after downloading sdk and updating to platform tools i have kept a zip in safe location so that i do not need to download again platform tools if i install sdk fresh
initially knowledge was scattered now it is at one place.
right now testing steady hawkin's kernel and new recovery
btw good signature pic.

Ok so another night has gone and still can't get recovery on!! Tried re unlocking the XOOM and every time it comes up with "cannot load recovery.img" I tried installing everything on my laptop and went right from the start and getting exactly the same thing!
Starting to think im never gonna get this sorted now :-( just feels like the XOOM isn't unlocking? Every time I go through the unlocking process it never states that its already unlocked? Is there any way I can check that it is unlocked?
Please help im losing the will to live now lol
Sent from my MZ604 using xda premium

I would say to send it to me and I can take a wack at it but I don't think you want to wait that long to simply root it.
Let me ask you, are you getting any sort of error messages when you do fastboot flash recovery recovery.img? If so, what's that error message?

scsa20 said:
I would say to send it to me and I can take a wack at it but I don't think you want to wait that long to simply root it.
Let me ask you, are you getting any sort of error messages when you do fastboot flash recovery recovery.img? If so, what's that error message?
Click to expand...
Click to collapse
Not getting any error message it just says "cannot load recovery.img"
I have tried with and without the .img and always the same?
Tried going through the whole process again on my laptop incase I had missed something but exactly the same.
When I unlock it I follow the onscreen instructions and at the end it says its complete before it reboots. Then I turn on usb debugging again and reboot bootloader all ok but won't let me load the new recovery?
Normally I would just say it wasn't meant to be and leave as it is but I wont be beaten on this so I'm purposely not installing anything on it till its done. Any ideas apart from bringing it round yours lol ;-)
Sent from my Desire HD using xda premium

[HOWTO] Backup and Restore the System Software

The recently posted rooting method for the KFHD has been great for owners to get started on modifying the device to suit their own tastes. However, I've been a little concerned about everybody jumping in without a safety net in place. There are numerous ways that this device can get bricked. Not to put all of you into a panic, but just getting an eventual OTA update from Amazon might put some of these rooted KFHDs in jeopardy. With no custom recovery on the horizon, I think it's important to have some backup/restore plan to get these devices booting again.
Overview
This backup plan involves making raw data clones of all critical storage partitions required to boot the device. These backup archives can then be stored somewhere off the device. In case of some critical failure that prevents the device from booting normally, these archives can be used to get the device booting normally again. The restore procedure requires the use of fastboot to write the backup archives back to their proper partitions. The use of fastboot requires a working bootloader, so the device will need to boot to the bootloader's bootlogo at a minimum. If the device has a broken bootloader, this guide will not be helpful. There's currently no working procedure for repairing a broken bootloader on the 2nd generation Kindle Fire devices.
To be clear, this guide is not a backup/restore plan for your data. This is strictly for backing up the system software while in a bootable state and recovering it if some modification bricks the device. This procedure has been tested on a KFHD with system software version 7.1.1. Although I have not tested it, I'm nearly certain it will work just fine on version 7.1.5. If the KF2 has the same partition layout as the KFHD, there's no reason why it shouldn't work for that device as well. Check the post on KFHD partitions for details.
Warning: Everything below is inherently dangerous and can potentially brick your device if they are not executed properly. I have tested various aspects to the best of my ability, but you assume all responsibility for performing any of these steps.
Backup
Attached is a small shell script written to do the following…
Make a "kindlebackups" directory in /sdcard (if necessary) and make it user read/writeable.
Create gzipped backup archives of partitions 1 through 11. This includes all partitions except /cache and /data.
Make all archive files user read/writeable.
The entire backup (stock) takes up approximately 550 MB, so be sure to have at least that much available in /sdcard. Root privileges are required for the script to run properly. The best time to use this script is after step two of the published rooting procedure. That's after the second reboot of the process when the device boots up in emulation mode and allows root access for the first time. At this point, the system partition is completely stock and has not been exposed to any modifications. Even if you are past this point, the backups will still be useful for any bootable state that allows root privileges.
Download the script, unzip and place it into your current working directory where you still have access to adb, then run the following adb commands to copy the script to the Kindle Fire and prepare it to be executed...
Code:
adb push backup.sh /data/local/backup.sh
adb shell chmod 777 /data/local/backup.sh
If the device is in the process of being rooted and it has just finished rebooting for the second time...
Code:
adb shell /data/local/backup.sh
If the device has already been rooted and the su binary is available on the system...
Code:
adb shell su -c "/data/local/backup.sh"
The entire process should take approximately 5 minutes. Once the script has completed the backup, access the Kindle Fire's storage area from your computer, then copy the contents of the "kindlebackups" folder to it. The "kindlebackups" folder may be deleted after transferring to your computer.
Restore
To begin the restore procedure, the device must be put into fastboot mode. My factory cable did the job for me, so I have not explored the possibility of changing bootmodes. I developed this guide on a borrowed KFHD and I do not intend to risk the device more than necessary. Unless someone comes forward with a procedure to change bootmodes into and out of fastboot mode, I'm going to say that a factory cable is required for the time being. Besides, based on my experience with the original Kindle Fire, a broken system almost always means there is no way to change the bootmode through it. Since this procedure will very likely be used on a device that cannot boot completely or otherwise has a bad system, a factory cable will probably be the only way into fastboot mode. If you plan to root or modify your system software, invest in a factory cable.
Use the factory cable (with the device turned off, plug into the device, then the computer) to get to fastboot mode. If successful, a "fastboot" logo will take the place of the original "kindle fire" logo.
Decompress the gzipped archive to be flashed… Linux users have gunzip, Mac OS X users also have gunzip and a built-in GUI utility, and Windows users can use 7-zip. The archive must be decompressed before flashing. Skipping this step will brick your device.
Flash the image file(s) back to the device. In most cases, the device will just have to get a working system partition flashed back to it, but the others are available if they are needed. To flash the system partition...
Code:
fastboot -i 0x1949 flash system system.img
- Optionally erase the cache and/or userdata partitions if the contents of either interfere with the operation of the system software. The system will rebuild them on reboot…
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
Once the process is complete, long-press the power button (~20 seconds) until it powers down, unplug the factory cable, and power the device back up.
Good luck.

Thanks kinfauns. I appreciate everything you did for the original kindle fire. This should help a lot of people.
Sent from my Kindle Fire

My kindles /system directory is already screwed. Do you have a system.img file I can use?
Sent from my Galaxy Nexus using xda app-developers app

When i boot my kindle fire hd to fastboot (by factory cable) and connect it to pc, pc can't recognize kindle, it don't have driver for it.

Could anybody post his clean backup here? Screwed my kindle, want go back to stock. Backup is only way.

Copying kindlebackup folder
Thanks for the script - the backup procedure was smooth -
I couldnt find the kindlebackups folder while browsing through my PC and for others like me who wonder how to take these out of your KFHD, here is a simple way - I used a program called Wondershare MObilego (Manage SDcard option under more tools) Backing up was a cakewalk.
I have no affiliation to this tool maker - Just sharing a way that helped a n00b like me. (First rooting experience)

Thanks for the efforts!
BTW, will a backup from a clean device work for other devices instead of the same one which the backup was created from? Just wondering if people who have already fiddled around their root devices can get a fresh start.

vuhai6 said:
When i boot my kindle fire hd to fastboot (by factory cable) and connect it to pc, pc can't recognize kindle, it don't have driver for it.
Click to expand...
Click to collapse
I don't know if anybody has packaged the device drivers set up for this device. If nothing else, you can get the device driver installer in the "Kindle Fire Utility" for the original KF and use that. You just have to change the PID from 0006 to 0007 before installing it and should work. Refer to this post if you still have problems...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
for device driver information. Again, written for the original KF, but the process for installing device drivers is the same. Only the PID is slightly different and that should get edited in the INF before installation.
ceebu said:
Thanks for the script - the backup procedure was smooth -
I couldnt find the kindlebackups folder while browsing through my PC and for others like me who wonder how to take these out of your KFHD, here is a simple way - I used a program called Wondershare MObilego (Manage SDcard option under more tools) Backing up was a cakewalk.
I have no affiliation to this tool maker - Just sharing a way that helped a n00b like me. (First rooting experience)
Click to expand...
Click to collapse
Glad to hear it worked out for you. I am not familiar with that program, but the KFHD should connect automatically to a Windows device as external storage... does it not?
dreamcryer said:
Thanks for the efforts!
BTW, will a backup from a clean device work for other devices instead of the same one which the backup was created from? Just wondering if people who have already fiddled around their root devices can get a fresh start.
Click to expand...
Click to collapse
I have not tested this and don't have a way to do so. I have some concerns about it, but I'm sure someone desperate enough will jump in and try it out. I know it's too late for some, but my suggestion is for everybody to make a backup if you can and not rely on someone else to give you archives after the fact. It's better to have your own backups.

Not recognized
My kindle is also not recognized when plugged in

kinfauns said:
I don't know if anybody has packaged the device drivers set up for this device. If nothing else, you can get the device driver installer in the "Kindle Fire Utility" for the original KF and use that. You just have to change the PID from 0006 to 0007 before installing it and should work. Refer to this post if you still have problems...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
But pc don't recognize as Kindle, it as Tate-PVT-08 (sorry, i use mac cho screenshot, but windows too)

vuhai6 said:
But pc don't recognize as Kindle, it as Tate-PVT-08 (sorry, i use mac cho screenshot, but windows too)
Click to expand...
Click to collapse
I know that the vendor id is correct.
Sent from my Kindle Fire

kinfauns said:
Glad to hear it worked out for you. I am not familiar with that program, but the KFHD should connect automatically to a Windows device as external storage... does it not?
Click to expand...
Click to collapse
I was only able to see the contents of /sdcard using windows...
Sent from my GT-I9100 using xda app-developers app

cesdev89 said:
My kindle is also not recognized when plugged in
Click to expand...
Click to collapse
Then you're first going to have problems getting root privileges. You need to get adb working before you attempt any part of rooting or backing up with this procedure.
vuhai6 said:
But pc don't recognize as Kindle, it as Tate-PVT-08 (sorry, i use mac cho screenshot, but windows too)
Click to expand...
Click to collapse
This is the correct "product" reported by the KFHD. This and the product ID (0007) are the only differences between the KFHD and the original when it comes to installing the device drivers on Windows.
ceebu said:
I was only able to see the contents of /sdcard using windows...
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
/data/media and /sdcard are essentially the same thing (see the second post in this thread for an explanation of why this is the case). You should have seen kindlebackups in that directory.

kinfauns said:
You should have seen kindlebackups in that directory.
Click to expand...
Click to collapse
For some reason I didn't see it there, on hindsight I guess I panicked a bit (n00b) and fell back to the solution I already had.. (been using mobilego to manage my sgs2)..
Sent from my GT-I9100 using xda premium

kinfauns said:
I don't know if anybody has packaged the device drivers set up for this device. If nothing else, you can get the device driver installer in the "Kindle Fire Utility" for the original KF and use that. You just have to change the PID from 0006 to 0007 before installing it and should work. Refer to this post if you still have problems...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
for device driver information. Again, written for the original KF, but the process for installing device drivers is the same. Only the PID is slightly different and that should get edited in the INF before installation.
Glad to hear it worked out for you. I am not familiar with that program, but the KFHD should connect automatically to a Windows device as external storage... does it not?
I have not tested this and don't have a way to do so. I have some concerns about it, but I'm sure someone desperate enough will jump in and try it out. I know it's too late for some, but my suggestion is for everybody to make a backup if you can and not rely on someone else to give you archives after the fact. It's better to have your own backups.
Click to expand...
Click to collapse
I'm ready to try

Didn't show at first
Kindlebackups showed up in root browser right away, but didn't show on PC until I rebooted KF2. So now should
I decompress and put in folder containing ADB?

Yuretz said:
Could anybody post his clean backup here? Screwed my kindle, want go back to stock. Backup is only way.
Click to expand...
Click to collapse
I got the same situation, could anyone kindly help to provide a backup?

Same here ... just need the system image ... Please

I'd appreciate it if everybody would refrain from making this a "beg for a system image" thread.
strat6 said:
Kindlebackups showed up in root browser right away, but didn't show on PC until I rebooted KF2. So now should
I decompress and put in folder containing ADB?
Click to expand...
Click to collapse
You can put the the images wherever you want, but you'll need to specify the path to the file. For example, if you are using Windows and put the kindlebackups directory on C:, you just need to modify the command to...
Code:
fastboot -i 0x1949 flash system C:\kindlebackups\system.img

Thank you for posting how to do this. It opens a lot of doors with at least a little security.
I made a backup earlier without a problem, then went ahead and made myself a factory cable(easy to do and worked great- old asus usb cable, 1k resistor, soldering iron, shrink tape and voila!). I feel much better about doing any mods to this device now knowing I can just flash my backup.

[Q] Desperate need some help, failure updating 4.4

my nexus 4 was rooted with 4.3 but then i decide to upgrade to 4.4
this is the video i am trying to follow, basically just wipe & install which i did most the time.
youtube title "NEXUS 4: HOW TO MANUALLY UPDATE TO ANDROID 4.4 KITKAT"
it has two files one is mako and one is gapp.
after i did all the wiping in cwm and try to install the mako file, it shows "no file context" or sth similar, and installation is abort (i think there is problem when i transfer the file), but then i continue to install the gapp file (what the hell was i thinking?)
so now i am stuck in the google start up loop, i can only access cwm recovery mode and don't have a valid rom to install in my sdcard.
i tried to adb push another rom to the sdcard with no success (my storage was already very low, any way to remove files in the storage at this point?)
the "mount & storage" also doesn't seem to let me mount the sdcard (but system shows up "unmount").
so now i don't know what to do.
if anything has any idea or suggestion please let us know.
i am quite desperate now with a dead phone and will try anything.
thanks for reading such a long thread.

Dude that vid is old and it installs pa or some other port just flash factory images from google
Sent from my F1 using xda app-developers app

try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.

Frickelpit said:
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Click to expand...
Click to collapse
any step by step guide to do this?
i am still new to this thing even i install a few roms before.
i will google it now, but any additional info is much appreciate.
thanks

Frickelpit said:
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Click to expand...
Click to collapse
frustrated..
i can't seem to get my windows to recogize the device (when i type adb devices, it shows an empty list)
already try trouble shooting this for a long time with no result.
any idea?

telly0050 said:
frustrated..
i can't seem to get my windows to recogize the device (when i type adb devices, it shows an empty list)
already try trouble shooting this for a long time with no result.
any idea?
Click to expand...
Click to collapse
after tons of troubleshooting finally got it back to work.
it ends up the reason is i didn't update to the latest cwm at the very beginning.
and sideloading 4.4 didn't work because of that too, i have to install an old 4.2 to have it working.

[me176c/x] [K013] Collection of ROMs and Updates

[me176c/x] [K013] How to Root and update from .182 to Lollipop release
Stock ROMs up to v.182, all languages
ASUS' Download Center for the MeMo Pad 7 Link is now inaccessible as ASUS has redesigned their site. Even the support page for this tablet no longer has any links to download ROMs/updates. Sad panda. However, the ones below (ASUS' direct links included) still work! I am also in the process of reuploading/rehosting all of these as well, so stay tuned! So far everything is rehosted on Google Drive, and I plan to add more mirrors in the next couple of days. Pleasse bear with my snarkiness, I have been up late and it's now 4am. I must crash now.
Anyway........ Enjoy!!
WW 182 Full ROM
ASUS
Google Drive
WW OTA 191
ASUS
Google Drive
Google Drive (alt)
WW OTA 198
Google Drive
WW OTA 199
Mediafire
Google Drive
WW OTA 201
Google Drive
Zippyshare (ew)
WW Lollipop release
Mediafire
Google Drive
If you have other links to share, especially direct links from ASUS or non-GDrive hosts, please feel free to post them and I will credit you!
(Manually) Flashing Updates
Sometimes (read: often) an update will fail to install and reboot, and then the tablet will claim you're up to date when you check for updates (and we know it's full of crap). So you'll have to manually update yourself, and often, if only works if you start from .182 (or above), and flash each file in consecutive order. So here's how it works. Be sure to read over this before starting, to get an idea of what's in store for you. And to be safe, read it again. And to be doubly-sure, read it AGAIN (I cannot stress this enough).
Obligatory warnings:
Your warranty (expired by now, for sure) is now null and void. Regardless of whether you do this, it's no longer valid either way! :laugh:
I am not liable for any damages to your device (or your brain) that this process may cause. What you do to your device is on you, but if you play it safe and read this all carefully (and read it again! And AGAIN!), you shouldn't have any trouble.
Instructions:
First things first, install your drivers if you haven't already, and set up the Android Platform Tools (adb and fastboot exes and such, also attached to this OP). I highly suggest trying the Latest ADB Fastboot and USB Driver installer tool for Windows by @fawazahmed0 (or the various attached drivers below, if you still somehow have trouble with getting your PC to recognize this dinosaur of a device).
Next, before we continue, make sure USB debugging is enabled on your tablet. Go to Settings > About tablet, and tap on Build Number 7 times, and you'll see a toast, "You are now a developer!" Back out once and scroll down a bit, you'll now see Developer Options. Enter, and near the top you'll see an option for USB debugging, so check that box. Plug in your tablet to the PC, then open a command line interface (Hit Windows Key + R, then type in "cmd" and press enter). Type in "adb devices" (without quotes) and look at your tablet's screen for a prompt. Check the box and tap OK. Now. back in the command prompt, press up and enter on your keyboard (which will repeat that last command), and you'll see your tablet's serial number (a string of letters/numbers) and the word "device" if you did it correctly. Now you're ready for the next part.
1. Install the "RootZenFone-1.4.6.8r.apk" (attached to this OP, below) and run it. Beware, it may have some Chinese text/Engrish. It's fairly simple to figure out though, thankfully.
2. Turn on USB debugging if you haven't already (didn't you read this first? You're already slacking!).
3. Download the zip file(s) you need and rename it update.zip and transfer it to your tablet. Or copy all files to the tablet and rename them (with a file manager of your choice, see next step) as you go.
4. Download a file manager that has root access (such as MiXplorer or Root Browser).
5. Go to / (root) and manually copy your update.zip to the /data folder.
6. Download this command file (also attached below, in a zip) and copy it to the /cache/recovery folder. This must be present each time you install an update via this method, so leave a copy on your device.
7. Back to Windows Command Prompt, run the command, "adb shell" (without quotes, as before), wait a moment for it to reload the server, then type, "su" (again, without quotes). When you type in the "su" command for the first time, it will prompt for SuperSU access on your tablet, similar to how it requested the RSA perms with adb debugging. You must allow this root permission, or the following won't work!Now, type line by line (or better yet, copy and paste into the command prompt (a right click automatically pastes copied text into it, btw):
Code:
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
In brief, what this means is that you just ordered the "command" file to boot as a "recovery" in order to flash the update package you copied and renamed previously. Thus, the tablet will reboot and commence flashing. At least, I think that's what's happening here. Sorry, I'm no rocket surgeon. All I know, is that it works. However, if you are getting an error during the update process, as mentioned above, you will likely have to flash the next incremental update (the one just above your current version) instead and go from there, flashing each OTA in order using the coded commands above every time. Be sure to rename EACH ZIP to "update.zip" as you do this or the command cannot find the file! Yes, this sounds like a pain, and it is! But this has worked when the direct approach had failed.
Archive folder of everything needed, on Google Drive
ROOT ZenFone FAQ has a translated guide on how to fix ptotential issues with the root process.
Credits:
@plopingo and @jerbear294 for some of the links.
@lethardicus for finding most of the OTA zips again when one weirdly went missing @fawazahmed0 for the driver installer tool
@slayeralive for providing the basis for these instructions

Nice work sub

No need for adb just copy zip ti /data and command file to /cache/recovery and reboot to recovery

@GuyInDogSuit
Update
mirrored OTA 191, 198, 199, 201 & RootZenFone-1.4.6.8r apk => https://drive.google.com/folderview?id=0B5G23fyE72tnLS0yaXlUamVmcXc&usp=sharing#list

@GuyInDogSuit @slayeralive
I've try to update manually but it failed
how to flash .182 if I'm already in .191 ?

slayeralive said:
No need for adb just copy zip ti /data and command file to /cache/recovery and reboot to recovery
Click to expand...
Click to collapse
You don't have to do all the typing anymore?

GuyInDogSuit said:
You don't have to do all the typing anymore?
Click to expand...
Click to collapse
I've try, the tablet show android logo with no command on the screen after reboot without entering command

you did something wrong. command file is just txt file , and echo command in terminal is used for writing text in txt files.try to copy command file and reboot to recovery from terminal emulator with reboot recovery command. I created this method mainly for unbricking read post
http://forum.xda-developers.com/memo-pad-7/general/unbrick-asus-memopad-7-me176c-cx-t2970049

GuyInDogSuit said:
Thanks to @plopingo and @jerbear294 for some of the links.
Click to expand...
Click to collapse
OMG, I can't believe I JUST found this thread.
I have two of these tablets that I use as wall-mounted controllers for HA. One of them accepted the OTA updates and I was able to get it to .201 and keep it rooted. The other one, no matter what I tried, would not pull down anything above the .182 it was running.
This post has EVERYTHING you need to go from whatever all the way to .201 quickly and very easily. I installed 15 Second ADB, the ASUS ADB drivers, and ran through all of the updates. This, my friends, is awesomesauce.
HUGE THANK YOU to @GuyInDogSuit, @plopingo, and @jerbear294!

No luck
im on .182. When I move the files to the directories and reboot to recovery it fails. i get an error. Could this be becuase i had modified the build prop with xblast

peldo123 said:
im on .182. When I move the files to the directories and reboot to recovery it fails. i get an error. Could this be becuase i had modified the build prop with xblast
Click to expand...
Click to collapse
It could. I have made that last year and end up with a bricked tablet...
I had to make a complete reset.
I made a few tries until I get it right and found out that using certain terminal apps don't allow spaces between commands whilst others do... Try commands without breaks if you're using a terminal app. Or try temp cwm to update all the updates at once.

Can't get it to work
Every time i try this procedure this happens:
The tablet restarts after executing the adb shell step.
The tablet starts to update the firmware, but then suddenly throws an error. This happens with both the rom and the update files.
Anyone has any idea how to fix this?
Thx in advance!

kdlannoy said:
Every time i try this procedure this happens:
The tablet restarts after executing the adb shell step.
The tablet starts to update the firmware, but then suddenly throws an error. This happens with both the rom and the update files.
Anyone has any idea how to fix this?
Thx in advance!
Click to expand...
Click to collapse
Did you unzipped the file? You see, there's a zip inside another zip. Unzip the 1st time into root/data folder and rename it to update.zip!

This fixed it! That was a stupid mistake

kdlannoy said:
This fixed it! That was a stupid mistake
Click to expand...
Click to collapse
I'm glad it worked. I once made the same mistake.

I an on 191
there is no /cache/recovery folder
ls /cache
aplogs
backup
lost+found
modemcrash
Should i create /cache/recovery ?

mrseverin said:
I an on 191
there is no /cache/recovery folder
ls /cache
aplogs
backup
lost+found
modemcrash
Should i create /cache/recovery ?
Click to expand...
Click to collapse
Should be safe. I had a recovery folder, but nonetheless I don't see why it would harm anything.

I've had several Android devices. That was the easiest root I've ever done.

bravesoul said:
Did you unzipped the file? You see, there's a zip inside another zip. Unzip the 1st time into root/data folder and rename it to update.zip!
Click to expand...
Click to collapse
Could you give me a little more detail? I can't seem to make it work. Also, I don't have a "data" folder in /root? Can I create one? Thanks. Nevermind, I got it to work.

regele said:
Could you give me a little more detail? I can't seem to make it work. Also, I don't have a "data" folder in /root? Can I create one? Thanks. Nevermind, I got it to work.
Click to expand...
Click to collapse
"/root" isn't a folder. It's the source. For example. When you copy something to a hard drive you are copying to the root of that hard drive. The same goes with the root of the android. So. Copy the unzipped .zip file to root and to inside data folder. Rename it into update.zip and run the commands.
I realise you got it to work, but since this is a community I have explained to others.

trying to bring my brothers A500 to life in 2019

Hey together,
I really hope someone out there is still using a A500 Tablet and may be able to help me fix a weird issue i encounter on every ROM i tried so far.
I installed the ROMs mentioned in this Thread: https://forum.xda-developers.com/iconia-a500/general/2018-a500-upgrade-threaddownloads-to-t3832293
And all of them come with the Same Problem for me.
If i try to open the Google PlayStore or something else that wants me to login into a Google Account it just says: "There was a problem communicating with Google Servers" "Try again later"
anyone knows of this issue ? All the fixes several Google searches gave me did not help to fix that issue for me on any of the ROMs.
help would be highly appreciated
kind regards
Finn

Hi,
have you read the tips? It says:
"- Google play will not work right if you do not format your data partition to f2fs. (You can do this in recovery)"
Have you tried it?

Matra-PB said:
Hi,
have you read the tips? It says:
"- Google play will not work right if you do not format your data partition to f2fs. (You can do this in recovery)"
Have you tried it?
Click to expand...
Click to collapse
That may not be the problem I've hear a lot of people are having this problem. But it's a good place to start if he hasn't tried it yet.

Success story upgrading A500 in 2019 July
finneus_ said:
Hey together,
I really hope someone out there is still using a A500 Tablet and may be able to help me fix a weird issue i encounter on every ROM i tried so far.
I installed the ROMs mentioned in this Thread: https://forum.xda-developers.com/iconia-a500/general/2018-a500-upgrade-threaddownloads-to-t3832293
And all of them come with the Same Problem for me.
If i try to open the Google PlayStore or something else that wants me to login into a Google Account it just says: "There was a problem communicating with Google Servers" "Try again later"
anyone knows of this issue ? All the fixes several Google searches gave me did not help to fix that issue for me on any of the ROMs.
help would be highly appreciated
kind regards
Finn
Click to expand...
Click to collapse
First my thanks to the forum key members for providing answers to queries and to all the key contributors of SW/ROMS in this forum. I followed the procedures from this forum to Flash / upgrade my Acer Iconia A500 on 4.0.3 ICS that was sitting in a trunk for the last few years. Summary of steps I tried out.
STEP 1: Install the Acer device drivers listed in the links in this forum on your Laptop/Computer even if by default your Windows 10 OS (assuming you are on Win10 like me) is able to recognize the A500 connected to the USB port.
USB_Acer_1.00.0524_A30HA31HA32H_A.ZIP
STEP 2: ROOTING the Acer A500.
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch ON. If you do not see this menu, then click 7 times of the Android Build No. listed under settings and come back to the menu above to enable USB Debugging.
3. Connect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
4. Since most of the discussions regarding flashing A500 were from 2011, the earlier Gingerbreak method for rooting did not work.
I downloaded the following file from this forum to root my tablet.
ICS_rooting_A10x_A5xx.zip
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
Note: The McAfee Antivirus software started tagging a file 'mempodroid' within this ZIP file Tools folder as a virus or malicious file. This rooting method uses the 'mempodroid' exploit which is detected as a VIRUS by McAfee and Qurantined. So restore from Qurantine and check list of files are still present in the folder. If not verify 8+8 files in folders again.
As per inputs in this forum, I restored the files quarantined and then suppressed McAfee SW for the duration of my upgrade activities on my laptop and was able to successfully extract all the files in the ZIP file to a local folder on the laptop. This ZIP file has adb and fastboot - two key programs useful for rooting your A500 apart from SU or superuser base file used in step 2. The file to run is the BAT file runit-win.bat if you are on windows. At the end of this step your tablet should be rooted. You may check by installing the RootCheck app from Google Playstore.
Step1a: Install a File Manager app from the Google playstore. This will help you extract the CPU ID and convert it with the SBK tool to get the SBK number/string. important steps SBK tool was available in file - SBCalc_v1.1.ZIP available in this forum.
STEP 2b: SUPERUSER and SUPERSU installation
1. Install SuperUser.apk first.. (IMP - Its available in this forum. Its like a base version for superSU to install over. If you do not install SuperUser.apk, then each time you try installing SuperSU, you would get an error message about a SU file being incompatible.)
2. Then install an older version of SuperSU downloaded from the website - filename -> eu.chainfire.supersu_v2.65-265.ZIP . Newer versions will not work. U got to install an older version as new version seems to be a paid SW.
3. Next Open SuperSU app on your tablet and let it update itself a couple of times each time opening and closing the app after the upgrade.
4. Remove SuperUser.apk file as now its no longer needed.
5. Now that you have ROOT access and SuperUSer access
6. Install Titanium Backup. File name in this forum- update-recovery-TWRP-rev2.0-beta4.ZIP . This will help you to flash/upgrade ROM software on your tablet.
Twrp 2.8:
http://www.mediafire.com/file/e7wpny5f39vw3pc/update-recovery-TWRP-rev2.0-beta4.zip/file
Compressed Archive (.ZIP)
File size: 4.91MB
Uploaded: 2018-08-14 21:40:26
https://www.mediafire.com/download/e7wpny5f39vw3pc
STEP 3: Install an Unlocked Bootloader i.e. unlocked bootloader Skrillax v9 - file name in this forum BabSector.rar or A500-Bootloader-Nvflash.ZIP
Once you have reached this step, you now have the basic tools needed for the final ROM upgrade of the tablet.
I did get error message after the reboots that happened after Unlocking the Bootloader. Someting about a LNX partition not being okay or some such msg. Each time I just WIPED the Cache and selected similar options to wipe System, Data, User, Dhelvic cache (spelling incorrect) etc. Since you have not installed the final OS or ROM for your tablet yet, no harm in deleting these partition data. Actually its recommended to wipe, format in f2f formats etc. all of which is possible using the TWRP Recovery software you installed in step 2. Choose Recovery menu option each time the tablet boots or gives errors.... using the volume rocket and power buttons. More info -> Go through this thread and install unlocked bootloader.
https://forum.xda-developers.com/showthread.php?t=1622425
Flashing Bootloader Steps
-------------------------
1. generate your SBK from cpuid
2. put tab in APX by holding reset (small pinhole bottom right side)
and pushing power for 3-4 sec. - then release reset approx 1 sec. later
the screen should be blank and power button should be lit - plug in USB to PC.
2. Run A501 A.bat - when finished reboot tab to recovery (win 7 and under
right click on A501 A.bat and select Run as Administrator)
3. run Recovery(power and volume-) ->WIPE -> "Advanced wipe ->System (only)and swipe to wipe.
4. unplug USB and reboot tab to APX
5. plug in USB afer it is in APX mode -> Run A501 B.bat (win 7 and under
right click on A501 B.bat and select Run as Administrator)
Bootloader unlock tutorial
--------------------------
Step 1: Get your cpuid - https://forum.xda-developers.com/showthread.php?t=1624645
Step 2: Convert it into an SBK - https://forum.xda-developers.com/showthread.php?t=1810618
Step 3: Download the A500 drivers
- http://www.mediafire.com/file/pde8rojv1t8gnif/USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501.zip/file
Step 4: Download the files to install the bootloader
- http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
Step 5: Follow the instructions in "how to.txt"
Step 6: Download a rom and flash in twrp
This tutorial is based of
https://forum.xda-developers.com/showthread.php?t=2450119 thread so big thanks to KaijiKun .
Bootloader unlock files:
http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
STEP 4. Downloaded file omni-4.4.4-20150210-a500-IconiaHD.ZIP as I was not sure version omni 5.1.1 was as stable as Omni4.4.4 reading all the threads in this forum.
First rename the downloaded OMNIROM file as update.zip .
OmniRom 4.4.4
http://www.mediafire.com/file/ghd72j3g618kk9g/OMNIROM-5.1.1-Tegraowners_ROM_v13t2.zip/file
File size: 244.66MB
Uploaded: 2015-04-05 17:40:14
STEP 5: Install another tool adb_fast.ZIP. This tool is also available in this forum.
Note:You need to copy the update.zip file to your computers folder where this tool adb_fast is installed. In mine it was C:\Program files (x86)\Minimal ADB and Fastboot folder. This adb_fast file creates an application shortcut on your computer desktop. Clicking on the short cut launches adb and fast boot programs I mentioned at the beginning.
STEP 6: Copy the file to the SD card (16GB) of your tablet.
Run the adb_fast tool from your desktop shortcut. This will open a Command Prompt type black screen window where you can enter the code as given below. Note you may need to see how your SD card is listed in a file manager in your computer
Code:
adb push update.zip /mnt/sdcard/update.zip --- NOTE: this creates mnt folder on internal storage and I had to then move the file using TWRP recovery tool installed in step 2, to the SD card.
adb push < ------- is the push command.
rom.zip < ------- is the name of the Rom zip file.
/sdcard < ------- is the location your pushing the Rom to.
E.) Reboot tablet with Power+Down Arrow i.e. This will start the Upgrade process for the tablet to OMNIROM 4.4.4
-- Power Button + UP VOLUME pressed... then release Power button after LED lights.
-- System will boot to commmand prompt
STEP 7: Install GAPPS using pico gapps short version and Wipe Data/Factory reset ----------------?>and wipe cache partition?
Reboot after 1st reboot
G.) https://opengapps.org/ to install a minimal version of Google Apps on the tablet.
File name -> pa_gapps-modular-mini-4.4.4-20150410-signed.ZIP
Root tablet again and install SuperSU if you need it
other info.
You can use TWRP to flash the OmniROM on the tablet or you can use the following in worst case senario to do the same.
Code:
fastboot devices
fastboot flash update.zip -- check if syntax is ok from threads in this forum
fastboot reboot-bootloader
copied below from other threads ---->
I find that a large amount of complaints in developer threads are due to people not properly wiping before a flash.
Of course there is times when a 'dirty' flash is fine, but if you're ever not sure, wipe as cleanly as possible.
fastboot allows for about the cleanest of wipes by the way. And each partition can be done separately too.
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
can all be done individually, but to do these all in one command
Code:
fastboot erase system -w
If possible I recommend to do these steps before flashing a ROM, and now that you know you can do this all within fastboot mode i suggest to try it out, its quick and painless!
Don't forget to wipe your kernel too! (fastboot erase boot)
~Important~ If your device uses an emulated SD card (as in no removable micro SD but an SD partition on phone)
Then be careful wiping data/userdata as this will erase all contents of internal SD - you are forewarned!
ADB= Android Debugging Bridge (ADB)
[TOOL]Minimal ADB and Fastboot [2-9-18]
https://forum.xda-developers.com/showthread.php?t=2317790&page=12
First a short explanation:
Fastboot, like ADB, is a tool to communicate from PC to Android phone. There are times when it is a must to use, and times when it is just helpful.
ADB is used within your recovery or within your OS, but when you are in bootloader mode and need to communicate with your phone then you need fastboot.
And you may ask why would i ever need this?
Well many reasons. Main one is knowledge, learning the ins and outs of fastboot, like learning ADB, can get you out of many jams.
And if you want to unlock your bootloader this is done through fastboot. Granted HTC's unlock is... well crap, but for a Nexus this is how its done.
One other reason I have to stress is learning for safety reasons, This is about the safest way possible to flash firmware to your phone (ie Radio, Hboot, Recovery)
Lastly you may want to know the limitations,
There are many of course, this isnt JTAG, it will not resurrect a hard brick, but it often save peoples phones from 'soft bricks' and lots of time when know how and when to use it.
Think of fastboot as the program that takes over when ADB cant be used, it works with firmware more than software.
https://forum.xda-developers.com/showthread.php?t=1624645&page=3
GUIDES
---------------
Civs Guide to flashing the bootloader http://forum.xda-developers.com/showthread.php?t=1622425
Walkthrough using APXFLASH tool at Step 6 http://forum.xda-developers.com/showthread.php?t=1624645&page=2
From Civato's OP of The Guide: nvFlashToolPackages
Skrilax_CZ bootloader thread http://forum.xda-developers.com/showthread.php?t=1619913 and should be "required reading" for anyone mucking about in their tabs internals!!!!
Rollback to HC
jazzyjames guide http://forum.xda-developers.com/showthread.php?t=1516012
Iconia Root http://forum.xda-developers.com/showthread.php?t=1138228 /gingerbreak: For returning to Honeycomb
----------------
To get my CPUID, I have followed the steps below:
Open yr file explorer, esfile explorer is a great one....navigate to:
/sys/firmware/fuse/acer_cpuid - add a zero to the front!
To get CPUID get a Root browser of some sort and go to sys/firmware/fuse/acer_cpu_id
convert my CPUID into SBK?
--------------------------
https://forum.xda-developers.com/showthread.php?t=1055354&page=6
What Does Root Give Me?
1. Full control over your system
2. Ability to alter system files. You can replace many parts of the "Android Core" with this including:
o Themes
o Core apps (maps, calendar, clock etc)
o Recovery image
o Bootloader
o Toolbox (linux binary that lets you execute simple linux commands like "ls") can be replaced with Busybox (slightly better option)
o Boot images
o Add linux binaries
3. Run special apps that need more control over the system
o SuperUser (lets you approve or deny the use of root access to any program)
o Task Manager For Root (Lets you kill apps that you otherwise could not kill)
Tether apps (like the one found at [android-wifi-tether.googlecode.com])
4. Backup your system
o You can make a folder on your SDCARD and backup all of your .APK files to your SDCARD (helps if an author decides to "upgrade" you to a version that requires you to pay to use the version you just had)
5. Relocate your (browser/maps/market) cache to your /sdcard
6. Relocate your installed applications to your /sdcard
7. Reboot your phone from the terminal app easily (su <enter> reboot <enter>)
Turn the rotation lock off.
-------------------------------------------------------
SUMMARY - Regardless of version, rooting is the same... next
** Unlock the bootloader.
** Fastboot flash a Custom Recovery (TWRP).
** Download to the Tablet, Chainfire's SuperSU root updater .zip
** Boot into the previously fastboot flashed Custom Recovery, and flash the SuperSU updater .zip.
** Reboot - you're rooted.
-------------------------------------------------------
PS. I tried to maintain a log in Notepad during my upgrade. Unfortunately did not write detailed instructions and link to required files. Above is a summary of what worked for me.

Can not root
sukasis said:
First my thanks to the forum key members for providing answers to queries and to all the key contributors of SW/ROMS in this forum. I followed the procedures from this forum to Flash / upgrade my Acer Iconia A500 on 4.0.3 ICS that was sitting in a trunk for the last few years. Summary of steps I tried out.
STEP 1: Install the Acer device drivers listed in the links in this forum on your Laptop/Computer even if by default your Windows 10 OS (assuming you are on Win10 like me) is able to recognize the A500 connected to the USB port.
USB_Acer_1.00.0524_A30HA31HA32H_A.ZIP
STEP 2: ROOTING the Acer A500.
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch ON. If you do not see this menu, then click 7 times of the Android Build No. listed under settings and come back to the menu above to enable USB Debugging.
3. Connect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
4. Since most of the discussions regarding flashing A500 were from 2011, the earlier Gingerbreak method for rooting did not work.
I downloaded the following file from this forum to root my tablet.
ICS_rooting_A10x_A5xx.zip
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
Note: The McAfee Antivirus software started tagging a file 'mempodroid' within this ZIP file Tools folder as a virus or malicious file. This rooting method uses the 'mempodroid' exploit which is detected as a VIRUS by McAfee and Qurantined. So restore from Qurantine and check list of files are still present in the folder. If not verify 8+8 files in folders again.
As per inputs in this forum, I restored the files quarantined and then suppressed McAfee SW for the duration of my upgrade activities on my laptop and was able to successfully extract all the files in the ZIP file to a local folder on the laptop. This ZIP file has adb and fastboot - two key programs useful for rooting your A500 apart from SU or superuser base file used in step 2. The file to run is the BAT file runit-win.bat if you are on windows. At the end of this step your tablet should be rooted. You may check by installing the RootCheck app from Google Playstore.
......
Click to expand...
Click to collapse
Hi sukasis, i was unable to root the tablet. I download all and run the runit.win.bat (trying normal, as admin, and open a cmd as admin and then navigate to the bat to execute).
- It say device connected
- Then push 7 files correctly
- Executing of the main script. (it freeze here a lot of time)
Then error: protocol fault (no status)
The file "su" isn't created
Not getting root!
I try in USB 3.0 and 2.0 same error.
I have windows 10.
I uncheck the Debugging mode and it's bring another error, so i believe the connection is good because in debug mode can push files.
I don't know whate else i can do.