Database Info

3 doubts about flashing CWM and EOS ROM

Hi all.
I have an Spanish wifi-only Xoom (MZ604) and I'm tired of waiting for motorola's updates (still in Honeycomb 3.2!!!).
I want to test either EOS3 (Android 4.1.1) or EOS2 (Android 4.0.4) custom roms. I've read almost all tutoriales but I still have some doubts about the procedures... could anybody check this message and warn me if I'm going to do something wrong?
DOUBT 1.- Key shortcuts in Xoom
Can anybody tell me the existing key combinations in Xoom? I only know about POWER+VOL_UP key to enter bootloader mode.
DOUBT 2.- How to install CWM.
If I understand it correctly, both EOS2 and EOS3 should be installed from CWM recovery...
Is the following procedure OK?
- Some tutorials say that you have to be root first to install CWM ... is it really needed? Can't be done directly with ADB?
- Install Android SDK in the PC.
- Download eos-recovery-r6.img or eos-recovery-r6-softkeys.img
- Connect XOOM to PC with the original USB cable.
- Reboot XOOM in bootloader mode (Power + VolUp)
- Exec adb and then:
fastboot oem unlock <---- is this a requirement?
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
DOUBT 3.- How to install or upgrade EOS 2 or 3 ROM?
Is the following procedure OK?
- Download ROM and gapps zip files.
- Start XOOM in recovery mode (CWM) -> How to do this?
- Do a nandroid backup.
- Wipe everything (data, cache, dalvik, etc)
- Install ROM zip.
- Install gapps zip.
- No need to do anything to root it, the rom is already rooted <-- is that right?
- Reboot
Is everything OK? Did I miss anything? Do I need to root my 3.2 install before any other step? Do I have to do the "oen unlock"?
Thanks.

All you need to do is unlock your boot loader and get into flashing eos3. Will give you details how to soon
Sent from my MZ601 using Tapatalk 2

wesamothman said:
All you need to do is unlock your boot loader and get into flashing eos3. Will give you details how to soon
Click to expand...
Click to collapse
Thanks for answering. If I'm understanding you correctly, you say that I don't need CWM and I can just flash the EOS ROM directly to my xoom without "applying" it as a zip in CWM...
I would really like to install CWM, I appreciate a lot the possibility to do "nandroid" backups to be able to go back before installing kernels, updates or so ...

NoP_Compiler said:
Thanks for answering. If I'm understanding you correctly, you say that I don't need CWM and I can just flash the EOS ROM directly to my xoom without "applying" it as a zip in CWM...
I would really like to install CWM, I appreciate a lot the possibility to do "nandroid" backups to be able to go back before installing kernels, updates or so ...
Click to expand...
Click to collapse
Since you are going to install EOS Jellybean, I don't advise you with CWM. A different recovery made by EOS team is better through which you can do nandroid backup and other stuff...
Here is what you need to do step by step...
Note: please read this procedure carefully more than once until you are fully aware of it. If you have any doubts or concerns, just ask to avoid confusion before you apply. This should be followed step by step.
To summarize:
First, download the above ROM and GAPPs and put them onto your xoom internal and external SD card. Put them under /mnt/sdcard for internal sd or somewhere accessible, and under the root of your external sd card.
To download:
• Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
• Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
• Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
• GAPPS: http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120726-eos-signed.zip
• ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ ; get the latest one...
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder. This is the sdk you downloaded above.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to: Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
adb reboot recovery
Now, you have your device unlocked and recovery installed.
Reboot your xoom by selecting the option "reboot system now" from recovery. you can navigate up and down using the volume buttons. Once an option is highlighted, press the power button to select, you will still have your old ROM.
To flash the other ROM downloaded above,
1. Boot into recovery by:
i. As soon as you hit the reboot command above, you should see a Motorola logo appear. Wait 3 seconds and tap the Volume down button and the words Android Recovery should appear on the screen. When you see that, tap the Volume up button and you’ll boot into recovery.
2. From within Recovery, perform wipe data, wipe cache, and go to advanced, wipe dalvik cache and battery stats. Don't worry, if the ROM and GAPPs are deleted, which should not be the case, you will have them on your external sd card
Note: wipe data will delete your stuff on the xoom. It would be great if you backup your files that you need to your external sd card before you start any of this procedure.
3. In recovery, navigate to install zip from sdcard > choose zip from sd card and select the EOS ROM you copied to the root of the SD card. Once the files are flashed, DO NOT reboot afterwards. Hold on.
4. Again, from Recovery, choose install zip from sdcard > choose zip from sd card and select the GAPPs you copied to the root of the SD card.
Then hit reboot system now. It will take 2 - 3 minutes for the first reboot. Setup your google account. and you are good to go.
Later reboots will be much faster (around 30 - 45 seconds). The more apps you install, the slower it boots...
That is pretty much it. Enjoy, I hope this helps you

Of course it helps! In fact, a lot.
When I was talking about CRW I really meant EOS recovery (which is based in CRW itself IIRC).
The only that I can't understand is why some tutorials ask me to root the tablet before doing all this process...
Anyway, I think I'm finally going with EOS3 + EOS recovery if nobody here advices me to flash EOS 2 instead...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.

So, before flashing:
- Do you think EOS3 (JB in Xoom) is mature enough to use it, or I should go with EOS2 final (ICS)?
- Do you know of anything not working in a wifi xoom with EOS3 rel.127?
- I've downloaded eos6-recovery.img ... do you think I should flash the "soft-keys" or the rogue-recovery instead?
- I don't have Microsoft Windows in my laptop: I work under Linux, so I haven't downloaded Motorola's USB drivers... I imagine that they are not needed under Linux, and It will work just with SDK's "adb" and "fastboot", right?
- Can the device be bricked with this procedure, or there is always a "Power+VolKey" way to flash a stock image? (like galaxys2 that its almost unbrickable).
PS: Thanks for informing me in the other thread that the EOS rom comes already rooted

I will be away for couple of hours, will answer your questions all as soon as I get back...
Sent from my MZ601 using Tapatalk 2

NoP_Compiler said:
So, before flashing:
- Do you think EOS3 (JB in Xoom) is mature enough to use it, or I should go with EOS2 final (ICS)?
- Do you know of anything not working in a wifi xoom with EOS3 rel.127?
- I've downloaded eos6-recovery.img ... do you think I should flash the "soft-keys" or the rogue-recovery instead?
- I don't have Microsoft Windows in my laptop: I work under Linux, so I haven't downloaded Motorola's USB drivers... I imagine that they are not needed under Linux, and It will work just with SDK's "adb" and "fastboot", right?
- Can the device be bricked with this procedure, or there is always a "Power+VolKey" way to flash a stock image? (like galaxys2 that its almost unbrickable).
PS: Thanks for informing me in the other thread that the EOS rom comes already rooted
Click to expand...
Click to collapse
Alright, eos jelly bean is fully stable, ,such faster and smoother than ICS. You want feel the difference until you try it... however, eos ICS is stable too and has more features and addons by eos because it has been there under dev for longer time, jellybean is new, one month old only... I recommend you to go for jellybean, and try and see for yourself. At anytime you can flash ICS since your Xoom booloader is already unlooked and recovery installed, you can do that by just wiping data and flash ICS zip. That is as simple as that...
For Motorola drivers on Linux, I think it is not needed, adb is built in with Linux, but I am not sure as I haven't tried that yet.
For eos recovery, don't use the soft key version, use the normal one...
with this recovery, you will be safe, because at all times, your external SD is accessible in emergencies...
Hope that helps...
Sent from my MZ601 using Tapatalk 2

You have it down perfectly. Just to recap.
1. Set up android sdk. Download recovery image and store in sdk folder. Download rom/gapps and store on tablet.
2. Boot into fastboot (power + volume up).
3. fastboot oem unlock (required). This will wipe all data.
4. fastboot flash recovery recovery.img (whatever recovery you decide to go with, I recommend eos soft key).
5. boot into recovery, make nandroid backup, flash rom of your choice + gapps if necessary.
People tie rooting to flashing custom roms because many people have become so reliant on apps like rom manager that flash the recovery for you, an app that requires root access. I never rooted my galaxy nexus or xoom. I simply flashed recoveries in fastboot and proceeded to flash roms in recovery.
It actually bothers me how some have become so reliant on root access to flash roms. It has gotten to a point where many people genuinely don't know the difference and that, to me, says they don't really understand what it is they're doing, which will lead to issues should they ever need to troubleshoot.
You seem to have it down well though. Good luck.

Thanks a lot to both.
I'm still waiting for JDK to download for Android SDK to work (I'm on hollydays in a small house in the middle of the forest and Im connecting with GPRS via tethering...).
I'll inform about the results...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.

Good luck...
Sent from my MZ601 using Tapatalk 2

Ok. EOS6-RECOVERY installed correctly. There are a couple of mistakes and some missing info in the "tutorial", so I'm going to change it to help future users:
I finally did it under Windows because almost all tutorials in Internet explain all the possible problems that you can find in Windows, and it's a "too risky" task for me to "experiment" by myself.
PART 1 .- HOW TO INSTALL EOS6 RECOVERY:
Originally quoted from wesamothman:
First, download the above ROM and GAPPs and put them onto your xoom external SD card. Put them in a folder called /sources/ of your external sd card.
- Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
- Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
- GAPPS: http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120726-eos-signed.zip
- ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ ; get the latest one...
And the most important:
- Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
Check that the md5sum of this file is correct and matches with the one provided in the download page. This is the most important file because it will allow to install the CWM recovery system and it's CRITICAL that the file is not corrupted.
Steps:
a.- Install in your PC the lastest JavaSE JDK from Oracle's website.
b.- Install in yout PC Android SDK, open Windows' cmd, enter the android-sdk folder and run:
Code:
tools\android.bat update sdk
Now select "Android SDK Tools", "Android SDK platform-tools", and Extras/"Google USB Driver". Click on "Install packages".
c.- Enable USB debugging in the XOOM (in settings, development).
d.- Install the Motorola USB drivers for your laptop (32 or 64 bits, check it in the Windows system properties).
e.- Plug the Xoom to your laptop.
f.- Execute cmd and enter the android-sdk/platform-tools folder.
Run "adb devices", if you get an empty "List of devices attached", then you must enter the control-panel -> devices and "Fix problem with device" over the MZ60x device. After a While, Windows will fix it and "adb devices" will show a message like:
Code:
List of devices attached
037887sda897xz device
(the digits string will vary according to your device)
NO NEED TO DO THIS:
NO -> 1. Power off your XOOM device.
NO -> 2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
Because the first command show after this lines: (adb reboot bootloader) won't work while in fastboot. Only "fastboot" commands work in fastboot mode. If you try that command in fastboot mode, it will say "Error: device not found".
So just, with your xoom working under the Android OS, do:
Code:
adb reboot bootloader
With the above, you'll enter fastboot mode without needing to press any key in the startup.
Now your Xoom will show the Motorola logo and the words "Fastboot protocol...". If you need to stop now for any reason, you can abandon this mode safely and reboot the tablet with "Power+VolUP+VolDown" for a few seconds.
But let's continue.... If you now do:
Code:
fastboot devices
You should get a string like
Code:
List of devices attached
037887sda897xz fastboot
If you don't see that string (and you see and error about device not found), you have to "fix/repair" the usb drivers again in the Windows ControlPanel / Devices. Now you'll see a "FASTBOOT" device instead of the MZ60x you repaired before (that's why we have to repair/fix again the device, because WIndows see it as a different device while in fastboot mode).
After repairing it, unplug and plug the USB cable (still in fastboot mode) and repeat the command:
Code:
fastboot devices
Now it will work and you'll see the device recognized by "fastboot"
Issue the following command to unlock the Xoom (you'll void the warranty):
Code:
fastboot oem unlock
Follow the Xoom's onscreen instructions to unlock the bootloader. You have to use VolDown to move through options and VolUP to accept an option.
The xoom will reboot and your old android OS will show, but now with a factory reset. Select language, time, etc and enable again USB debugging and execute in the PC:
Code:
adb reboot bootloader
(to start again the tablet in fastboot mode)
Now copy the file eos-recovery-r6.img to the android-sdk/platform-tools/ folder and execute:
Code:
fastboot flash recovery eos-recovery-r6.img
You will see something like:
Code:
C:\Users\sromero\Desktop\android-sdk-windows\platform-tools>
fastboot flash recovery eos-recovery-r6.img
sending 'recovery' (4114 KB)...
OKAY [ 0.499s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 1.529s
Check in the xoom's screen that the file was correctly written and execute:
Code:
fastboot reboot
You xoom will start again in Android OS mode. Execute:
Code:
adb reboot recovery
And you'll start the nice EOS Recovery (based on Clockworld Mod) recovery system.
You can also do it manually by powering on the Xoom and when the motorola logo appears, wait 3 seconds and press VolUp.
Now, you have your device unlocked and recovery installed. Now, you are SAFE because you can do nandroid backups and restores and can put any ROM in your system and go back with a backup or flash another different rom.
PART 2 .- HOW TO USE CWM / EOS RECOVERY
Code:
Up -> VolumeUp button
Down -> VolumeDown button
Select -> POWER button
PART 3 .- HOW TO INSTALL EOS3 ROM:
Under recovery mode (abd reboot recovery), do:
- Backup/restore -> backup to external SD.
- Wipe data/factory reset
- Wipe cache
- Advanced -> Wipe Dalvik Cache
- Advanced -> Wipe Battery Stats
- Install ZIP from SDCARD -> /sources/ -> the eos3 rom .zip file.
- Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
- Reboot
- Enjoy your new rom!

Very well detailed... great...thx.
Sent from my MZ601 using Tapatalk 2

wesamothman said:
Very well detailed... great...thx.
Click to expand...
Click to collapse
No... thank you for the initial info
After restarting, I have a notification about a ROM update (128). The ROM-management app allows me to download it or apply a incremental update...
Do you know if that second option (incremental update) is safe?
Anyway, I can just always do a Nandroid and test it ... having CWM I can't loose never anything, right?

Of course it is safe, I use it a lot. Just boot into recovery now by long press on power menu, select reboot, recovery,
First download build128. It will be under /storage/sdcard0/goo manager.
From recovery, wipe cache, dalvik, flash build 128, and reboot,
FYI, this latest build has theme engine now
Sent from my MZ601 using Tapatalk 2

wesamothman said:
First download build128. It will be under /storage/sdcard0/goo manager.
From recovery, wipe cache, dalvik, flash build 128, and reboot,
FYI, this latest build has theme engine now
Click to expand...
Click to collapse
So, the incremental update has to be flashed from recovery too?
I'll try it after a few days, when people confirms that it has not any major bug...
Thanks.

NoP_Compiler said:
Thanks a lot to both.
I'm still waiting for JDK to download for Android SDK to work (I'm on hollydays in a small house in the middle of the forest and Im connecting with GPRS via tethering...).
I'll inform about the results...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
Click to expand...
Click to collapse
Worth noting that to use fastboot and stuff, you only really need to install the Android SDK Platform-tools, maybe the regular SDK tools as well, I can't remember.
You don't need to install all the other stuff.
---------- Post added at 08:02 AM ---------- Previous post was at 08:01 AM ----------
NoP_Compiler said:
So, the incremental update has to be flashed from recovery too?
I'll try it after a few days, when people confirms that it has not any major bug...
Thanks.
Click to expand...
Click to collapse
Yes, any updates/mods/gapps updates need to be flashed in recovery.
Unless specified that its necessary by devs though, you don't need to wipe anything. I've been on JB nightlies from day 1 and I haven't wiped cache or anything since the initial wipe.

Is it possible to...
a.- change the system font (too 'light' in my xoom).
b.- disable jellybean UI animations...
?

I don't know about question a, though I'm sure its possible.
As for question b, try a different launcher. Apex launcher and nova launcher are both popular Android 4.0+ launchers (check play store for them).

Eos ROM,m settings, developer options, disable animations and transitions
Sent from my MZ601 using Tapatalk 2

[HOW TO] Beginner's Guide to Flashing & Fun on the A700 (Root, ROMs, Etc.)

Installing ROMS & Such on the A700/701
For Extreme A700/Android Neophytes
Read It All BEFORE Beginning!​
Important Links:
http://forum.xda-developers.com/showthread.php?t=1710755 ← Unlock Bootloader
http://forum.xda-developers.com/showthread.php?t=1791165 ← CWM
http://forum.xda-developers.com/showthread.php?t=1806980 ← CM10 Official Thread
http://forum.xda-developers.com/showthread.php?t=2056964 ← CM10.1 Official Thread
http://forum.xda-developers.com/showthread.php?t=2489708 ← CM10.2 Official Thread
-----http://get.cm/?device=a700 ← CM10 Download
-----http://goo.im/gapps ← Google Apps 4.1.2
http://forum.xda-developers.com/showthread.php?t=1995981 ← AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=1952124 ← iconiaN
http://forum.xda-developers.com/showthread.php?t=1953917 ← Vorbeth’s EasyRoot ← Do This to Root!
http://forum.xda-developers.com/showthread.php?t=2004441 ← Vorbeth’s OC GPU Kernel
http://forum.xda-developers.com/showthread.php?t=1994294 ← CoolOne700
http://forum.xda-developers.com/showthread.php?t=2196266 ← IcOdiv for A701 & A700 based on CyanogenMod 10.1
http://forum.xda-developers.com/showthread.php?t=2219575 ← Evil Alex Purgatory A701
http://forum.xda-developers.com/showthread.php?t=2232411 ← 7comp based on RootBox
http://forum.xda-developers.com/showthread.php?t=2510004 ← Official PAC-man 4.3
Software You Will Use/Need (depending on your root method):
http://support.acer.com/us/en/product/default.aspx?tab=1&modelId=4318 ← Acer USB Drivers
http://developer.android.com/sdk/index.html ← Android SDK
General Information:
First off, this was never made adequately clear for new users (without going through a hundred different posts with hundreds of replies): You will be using the Android SDK and the Windows Command Prompt. When installing the Android SDK, change the directory to something easy like C:\SDK because you will be typing it a lot. The directory in that folder you will be using exclusively for this process is the “platform-tools” directory. This is where adb and fastboot are found.
In addition, you will need to activate ADB Debugging on your tablet. This is found by going to Settings -> Developer Options -> USB Debugging. If this isn’t done, you will get nothing accomplished. Yes, you will need to have your tablet connected through USB to your PC for this to work. I know there are other ways, but I’m writing this with brand new users in mind.
After you’ve got that set, you should go ahead and install the Acer USB Drivers. None of my computers could properly identify the tablet without the drivers. Speaking of quirks, 64GB microsd cards are not generally very friendly with CM10 or CWM even when formatted as Fat32. There are lots of issues I can’t find a workaround to. Consider using a 32GB until the kinks are worked out.
I’m also assuming you are currently running the JB OTA that was pushed worldwide in October 2012. If you are not, then there are a few extra steps when installing IconiaN. Although I compiled the instructions you’re reading, I had nothing to do with anything else. In fact, I didn’t write the codes used to install things through the command prompt….I just compiled all the information into one easy-ish to follow paper.
As usual, if anything in this causes a brick to your tablet, it was your decision. I’m just providing the information that has worked for me (repeatedly). Also, as I’m not a developer, nor am I very handy with editing files or trouble shooting things without actually handling them…….Ask your specific questions directly to those people in charge of the files (pawitp, Vorbeth, Moscow Desire, meier2009, odiv81 and alx5962). They’re the gurus at this..I am a plebe in their shadow.
TL;DR:
Install Android SDK to an easy directory.
Install Acer USB Drivers.
Unlock Your Bootloader: (codes from alx5962)
1. Open a command prompt in windows and navigate to the directory where adb is stored. For the sake of conversation, I’m going to call it “C:\SDK\platform-tools”
2. Plug your tablet into your computer through USB. It should automatically mount because you’ve installed the Acer USB Drivers and didn’t skip that step above. J
3. At the command prompt, enter the following:
Code:
adb reboot-bootloader
-- Allow the device to reboot.
4. Type Code:
Code:
fastboot oem unlock
5. Press the + Volume button to select Unlock then - Volume button to confirm.
6. Restart :
Code:
fastboot reboot-bootloader
----- I had issues on step 6. I tried that, and it rebooted to the bootloader screen. To be on the safe side without hard rebooting (not knowing what was going on), I used the command from Step 3. to reboot. This works for ICS and for JB bootloaders, I confirm I used the above steps on both.-----​7. Confirmation of your unlocked status will be seen in the upper left hand corner of the screen.
Install Clockwork Mod Recovery: (all work & codes from pawitp)
Somehow I wasn’t able to install this properly (permanently) until last night (11/09/12). I’m still not entirely sure what I did differently, but I’ll try to document it here. The safest version of CWM is 6.0.1.5. Don’t attempt anything without that version or better. I’ve heard that at this time the touch version isn’t working properly, so be sure to download the original style CWM.
To navigate CWM, the following bit of information will come in handy (especially if you’ve never used it before.) Use the ‘Vol-‘ and ‘Vol+’ buttons to navigate up and down and the ‘Power’ button to select your choice. When you have made a choice it will sometimes give a screen with a ton of “NO” options with only one “YES” option (usually near the bottom). Like any good video game, if you scroll upwards, you can get to the bottom of the screen faster.
1. Place the CWM file you downloaded into your “platform-tools” directory. For the sake of being easy to install, I changed the file name to ‘recovery.img.’
2. Open a command prompt in windows and navigate to the directory where adb is stored. For the sake of conversation, I’m going to call it “C:\SDK\platform-tools”
3. Plug your tablet into your computer through USB.
4. At the command prompt, enter the following:
Code:
fastboot flash recovery recovery.img
5. At this point, you have flashed CWM to the system, BUT you will now need to boot into CWM using :
Code:
fastboot boot recovery.img
The caveat here is that you will need to install either a custom ROM or unencumbered boot.img (kernel) NOW. If you do not install one, flashing CWM was pointless because stock recovery will overwrite it at next reboot. When prompted at reboot (leaving CWM after flashing a ROM) you should choose to keep CWM. This was sort of a miscommunication between the devs and myself, but meier2009 and Moscow Desire cleared it up.
-----Step 5. does NOT install recovery, but forces your system to boot into CWM by pushing the file to your A700 from your ‘platform-tools’ directory.-----​
For Future Reference: Enter recovery…(JB):
a. With system powered off, press and hold ‘Power’ and ‘Vol -‘
b. When the system vibrates, release the ‘Power’ button.
c. When the system vibrates a second time, slide your finger from ‘Vol-‘ to ‘Vol+.”
d. When the system vibrates a third time, release that button.
Install pawitp’s CM10.1 OR IcOdiv (A701): (all work & codes from pawitp)
Download the CM10 nightly from the official Cyanogen page and grab the Google Apps file (optional, but you won’t have market without it) listed in the links section. Despite what people say, I have always been unable to install from my external SD card. Instead, I save the zip files to the root/main directory of the internal SD. Save BOTH FILES to internal SD at this time. This has always worked for me, but your mileage may vary. You do this at your own risk, blah, blah, blah.
1. Boot your A700 into CWM using the steps outlined in Step 5. (or 6) from “Install Clockwork Recovery Mod.”
2. Backup your system by navigating to “backup and restore” by using the ‘Vol-‘ and ‘Vol+’ buttons to navigate up and down and the ‘Power’ button to select your choice.
3. At this point, there are two options for you. “backup” and “backup to external_sdcard”…. I have never been able to mount my 64GB Fat32 external_sd in CWM. Try a smaller card if you have one available (I don’t). If you can backup to external, that is probably necessary when coming from stock. I would only backup to internal if you are just updating from an older nightly or previous rom.
4. On the main screen, assuming you’re coming from stock JB or ICS, you will need to do a couple of wipes. I’m positive the first is necessary, and have read in other parts of threads and other forums that the other two wipes are needed, but as they’re both called “cache,” I went ahead and did both (with no ill effects).
Select “wipe data/factory reset”
Select “wipe cache partition”
Select “advanced” and navigate to “wipe dalvik cache”
Go back to the main menu.
5. From the main menu, select “install zip from sdcard”.
6. Select “choose zip from sdcard” and scroll down to the CM10 zip file. Press the ‘Power’ button to select and confirm.
After this has successfully installed, you can choose to install Google Apps or not. I’m assuming you will want to install them because…well…who doesn’t?
7. To install Google Apps, follow Steps 3 and 4 from above, but this time you will choose the gapps zip file instead of the CM10 zip.
8. Reboot Device & Enjoy well sorted Jelly Beans.
Install iconiaN: (all work & codes from Vorbeth)
At the moment this is my favorite. It is one version number (4.1.1) behind CM10 (4.1.2), BUT it is compatible with my SD card, and is similar to the stock experience …. only faster and without the bloatware. The only reason it is second in this guide is because of the alphabet (C before I & P before V).
The latest updates to the ROM bring the latest GAPPS and firmware. meier2009’s 4Way Reboot Mod is also included (and rocks).
1. Boot your A700 into CWM.
2. Follow Steps 2-6 from above if coming from stock JB (or CM10, or CoolOne700) with the exception that you’re installing the iconiaN zip (not CM10, duh). Also, iconiaN comes with v4.2 Google Apps pre-installed, so no need for Step 7.
-----2.a. If coming from stock ICS, you will need to install the Jelly Bean Firmware (Found in the Aroma Setup of the ROM)
3. If coming from an older version of iconiaN, you shouldn’t need to do the wipes, but go ahead and do the backup just to be safe.
4. Reboot Device & Enjoy well sorted Jelly Beans.
-----On a side note, I went ahead and installed BusyBox (https://play.google.com/store/apps/details?id=stericson.busybox) not sure if this was necessary, but I am suffering no ill effects from having it running on my tablet. -----​
Install Vorbeth's OC GPU Kernel: (all work & codes from Vorbeth)
This is a custom kernel (as of this writing available only for the A700) that overclocks the Tegra 3 from 1.3Ghz to 1.5Ghz. There has been a noted improvement in gaming performance using this kernel.
1. Boot your A700 into CWM.
2. From the main menu, select “install zip from sdcard”.
3. Select “choose zip from sdcard” and scroll down to the iconiaN Kernel zip file. Press the ‘Power’ button to select and confirm.
4. Reboot Device PLAY SOME GAMES! WEE!
Install Vorbeth’s EasyRoot: (all work & codes from Vorbeth)
If for some reason you’re happy with stock and just want a very simple way to ROOT, then this is for you. Using this kernel will cause OTA to stop working (or you will have to edit the updater-script) and remove all the file checks. The latest update has made all previous instructions null, and it is now exceedingly easy to install ROOT on your A700. Awesome! Still, this does require an unlocked bootloader.
1. Download and extract the EasyRoot ZIP on your computer.
2. Locate and double click the file 'easyroot.bat'.
3. Follow all onscreen instructions.
4. Profit.
CoolOne700: (all work & codes from meier2009)
This is the new kid on the block. meier2009 has included three different install options in this ROM including Full (rooted stock), Small (all the Acer bloatware removed), and Custom (Choose what you want.) It’s definitely one to keep an eye on. Custom install is very handy. He’s also got his 4Way Reboot Mod which adds all our favorite reboot/recovery features. Sweet! Also, BusyBox and SuperSU are included on install, so you don’t need to worry about that.
1. Boot your A700 into CWM.
2. Follow Steps 2-6 from CM10 Install if coming from stock JB (or CM10, or iconiaN) with the exception that you’re installing the CoolOne700 zip (not CM10, duh). Also, CoolOne700 comes with Google Apps pre-installed, so no need for Step 7.
-----2. a. If coming from stock ICS, you will need to install the Jelly Bean Firmware (Found in the Aroma Setup of the ROM)
3. If updating from an older version of CoolOne700, you won’t need to do any of the wipes, but it is always a great idea to do the backup.
4. Reboot Device & Enjoy well sorted Jelly Beans.

Code:
6. If upon reboot, you hit the old system recovery, you will need to reflash the recovery.img OR just work around it by doing:
Code:
fastboot boot recovery.img
-----Step 6. does NOT install recovery, but forces your system to boot into CWM by pushing the file to your A700 from your ‘platform-tools’ directory. I had to use this method to install CM10 because I was never able to get CWM to install. Your luck may be different.-----
THAT´s the Trick my Friend !
Install recovery with
Code:
fastboot flash recovery recovery.img
AND THEN
Code:
fastboot boot recovery.img
Install any ROM and if you´re rebooting and asked to FIX Recovery, answer YES, then it will be leaved there !!!
With this way your also able to start CWM Recovery temporary
only use
Code:
fastboot boot recovery.img
then CWM will start, you can flash anything and after that CWM is gone, because the Stock Recovery is always inside the Recovery Partition

Makes sense then how I finally ended up with CWM actually installed on my tablet. Were the original instructions from pawitp mistaken, or just incomplete?

ExtremeRyno said:
Makes sense then how I finally ended up with CWM actually installed on my tablet. Were the original instructions from pawitp mistaken, or just incomplete?
Click to expand...
Click to collapse
Lost in translation...

ROFLMAO

Added more info last night and have now included the AOSP 4.2 to the links. Keepin' this bumped & updated.

Thanks for posting this excellent How To! I used it to install CM10.
I can confirm the backup to external backup functionality does work with a 8 GB MicroSDHC card. One thing you could do to bypass the external vs internal SD card discussion is to use sideloading. I used it to both install CM10 and the Google Apps and it works nicely. Just select Update through sideload in CWM and then enter 'adb sideload <filename>' on the command line and everything works nicely.
Also for the real beginner you could may be suggest backing up all user applications using Titanium Backup in order to easily restore them after flashing a mod.

Bumping thread back near the top. Lots of people got an A700 for the holiday and it seems many of them are bricking or at least screwing things up using outdated methods or strange new forms of CWM from other forums.
Also, thanks for the info, SanjuroE. Appreciated, and I can honestly say I never knew how to do the sideloading thing. I didn't actually realize that was what it was as on my old tablet (three years ago) sideloading was always in reference to installing from the external SD.

This guide was awesome. Many thanks for this.

I flashed CWM 6.0.3.1 via fastboot.
After that I tried fastboot boot recovery.img but it doesn't work.
On the display:
Booting downloaded image.
But nothing happens ??
Can anyone help me ??

schlex2010 said:
I flashed CWM 6.0.3.1 via fastboot.
After that I tried fastboot boot recovery.img but it doesn't work.
On the display:
Booting downloaded image.
But nothing happens ??
Can anyone help me ??
Click to expand...
Click to collapse
Loot at
http://forum.xda-developers.com/showthread.php?t=1791165
Post #166 to end of thread.

cfgh said:
Loot at
http://forum.xda-developers.com/showthread.php?t=1791165
Post #166 to end of thread.
Click to expand...
Click to collapse
Thanks mate!
I tried another recovery.img and than everything went fine!! :good:

USB driver link is not working.

papars said:
USB driver link is not working.
Click to expand...
Click to collapse
Check this : http://forum.xda-developers.com/showpost.php?p=58172023
Many files available, including Drivers

I can't connect my iconia a700 to PC (Windows 10) is say: device not found. Any help?
I install USB Driver, but in Device managers shows Acer Iconia Tab a700 with yellow worming sign.

Driver Issues WIN10
goralpm said:
I can't connect my iconia a700 to PC (Windows 10) is say: device not found. Any help?
I install USB Driver, but in Device managers shows Acer Iconia Tab a700 with yellow worming sign.
Click to expand...
Click to collapse
Hi,
I have the same issue and it took me hours to even find a driver from ACER. But even after the installation I cannot get the tablet to work stable. I installed general MTP drivers which gave me access to the "adb reboot-bootloader" command but during the reboot the tablet gets stuck on the Acer logo screen and does not boot into the bootloader. I have to unplug the tablet and only then I get the white text in the top left corner of the screen saying "starting Fastboot USB download protocol". But that is it. I assume that fastboot would use the Acer drivers to access the tablet but I don't have any for windows 10.
My question: Could somebody post drivers for Windows 10 for the A700/A701?
Thanks
realshadow

realShadow said:
Hi,
... ...
My question: Could somebody post drivers for Windows 10 for the A700/A701?
Thanks
realshadow
Click to expand...
Click to collapse
I had exactly the same problem. The solution was give here: https://forum.xda-developers.com/showthread.php?p=48915118
You don not need Acer driver.
- Wayne

[GUIDE] Root ASUS MemoPad FHD 10 Model ME302C US version 5.0.16

This post (#377 on page 38) was originally written under thread "Root Now Available For ASUS MemoPad FHD 10 Model ME302C" (http://forum.xda-developers.com/showthread.php?p=51699593) however OP has not been able to update the original post and this has caused much confusion. Its difficult to read through 40+ pages of posts with new modifications to the originally posted root procedure. I am posting the latest instructions in a new thread.
Thanks to @perpe on the German Android Hilfe forum
[Anleitung]Root, Unroot, Up-/Downgrade, Unbrick ASUS MeMO Pad FHD 10 (ab Android 4.3)
http://www.android-hilfe.de/root-custom-roms-modding-fuer-asus-memo-pad-fhd-10/528918-anleitung-root-unroot-up-downgrade-unbrick-asus-memo-pad-fhd-10-ab-android-4-3-a.html
There is also a Russian Forum 4PDA for this tablet
Прошивка Asus MeMO Pad FHD 10 (Только WW регион)
http://4pda.ru/forum/index.php?showtopic=500286
This is a thread for apps that can be frozen or removed:
[Sammelthread] Apps die man deinstallieren oder einfrieren kann
http://www.android-hilfe.de/asus-memo-pad-fhd-10-me302c-forum/482780-sammelthread-apps-die-man-deinstallieren-oder-einfrieren-kann.html
+++++++++++++++++++++++++++
This guide and below links are for USA build only (Goto Settings -> About Phone -> Build Number). WW build needs WW 5016 update and WW 5017 root update files but, indeed, uses the same procedures. DO NOT interchange USA for WW files otherwise you will BRICK. Links for WW 5017 root can be found on previous forum posts. ASUS hosts the WW 5016 update on its support page http://www.service.asus.com/#!downloads/c1wax
AS ALWAYS, BACKUP YOUR DATA! Titanium backup is a good option. Make sure backup files are copied to your PC or external storage
MAKE SURE THE BATTERY IS FULLY CHARGED!
Tools Needed:
USA Asus 5016 update - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME302C/US_ME302C-V5_0_16-0-ota-user.zip
USA 5017 root update - https://docs.google.com/file/d/0B-6nm7Jks0W5eWxSM0JoZ2FPVGc
For those of you who are already root and would like to update to 5016 it is recommended to download the latest 5016 update (~700mb) directly from Asus website. Please do not do an OTA update as this may fail since you are already root. Make sure that SuperSU survival mode is OFF. Place US_ME302C-V5.0.16-0-ota-user.zip in the internal Storage via Windows Explorer. Make sure it has the exact file name US_ME302C-V5.0.16-0-ota-user.zip. Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet. Then copy 5017 root update US_ME302C-V5.0.17-0-ota-user.zip in the internal Storage via Windows Explorer. Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet. You will then be root. Make sure you install SuperSU by Chainfire from Play Store. For BusyBox use BusyBox X by Robert Nediyakalaparambil as it is x86 compatible.
For those of you who are not rooted the easiest method is to accept the OTA update to 5016. (Alternatively, place US_ME302C-V5.0.16-0-ota-user.zip in the internal Storage via Windows Explorer. Make sure it has the exact file name US_ME302C-V5.0.16-0-ota-user.zip. Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet). Then copy 5017 root update US_ME302C-V5.0.17-0-ota-user.zip in the internal Storage via Windows Explorer. Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet. You will then be root. Make sure you install SuperSU by Chainfire from Play Store. For BusyBox use BusyBox X by Robert Nediyakalaparambil as it is x86 compatible.
Optional:
1) Install AdsFree from http://adfree.bigtincan.com
2) Review the German forum (link at top) for apps that can be safely frozen or uninstalled via Titanium Backup
Please note avoid OTA updates after root is obtained otherwise you will loose root or maybe worse. Keep up to date with developments on this thread for rooting methods when and if Asus release new updates. @perpe recommends all future updates be installed via the internal storage method. You can also check the German FHD 10 forum for updates at the above link
+++++++++++++++++++++++++++
Step by Step Guide for root via Fastboot Method for US version 4.7.3 or below: (read above instructions first as it is much easier to update and root using alternative methods)
Please note that tablet with versions higher than 4.7.3 no longer have the ability to use the fastboot method as this has been disabled by Asus in the latest versions. Some members have suggested downgrading fastboot to 4.7.3 if you have a later version. However this is not recommended and could result in problems. Fastboot downgrade should only be a last resort and limited to advanced users:
fastboot flash fastboot fastboot.img
(fastboot.img can be found inside the 4.7.3 release on the ASUS website. You can extract fastboot.img from the ~700mb update using 7 zip. Or download USA build here: http://support.mediafire.com/download/dk487lcxqfsgau6/fastboot473.zip )
Tools Needed:
Intel Drivers - http://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Asus Drivers - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME173X/ASUS_Android_USB_drivers_for_Windows.zip (download these in case Intel drivers don't work)
ADB and Fastboot tools - http://forum.xda-developers.com/showthread.php?t=2588979 (say no to drivers, just install adb)
Linux Fastboot for Intel SoC - http://www.android-hilfe.de/7373742-post8.html
USA Asus 5016 update - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME302C/US_ME302C-V5_0_16-0-ota-user.zip
USA 5017 root update - https://docs.google.com/file/d/0B-6nm7Jks0W5eWxSM0JoZ2FPVGc
Enable USB Debugging:
The “Developer Options” menu item on 4.2.* is hidden.
1. Goto Settings -> About Phone.
2. Goto “Build Number” at the end of the Scroll list.
3. Tap on “Build Number” repeatedly (7 times). On your third tap you should see message indicating that you only have 4 more taps to go to ‘become a developer’.
4. Continue: 4 more taps.
5. Hooray, you are now a ‘Developer’, go back to the Setting page.
6. You should see Developer Option menu item in your setting list now.
7. Open Developer Options and check USB debugging > OK
Install ADB and Fastboot from above (say no to drivers, just install adb)
Install Intel drivers
Plug in USB cable (at this point your PC will auto install several devices)
adb devices
(if you don't see a device you have a driver issue. Try the Asus drivers - Goto Device Manager. Right click on "Android" and choose "Update Driver" and do a "Manual install" and select the extracted Asus drivers. Also the tablet could be listed under "Other devices". Make sure to reboot your PC when done.)
adb reboot bootloader
Wait for tablet to reboot into bootloader. You'll see an Android with a hard hat
fastboot devices
( if you don't see a device you have a driver issue. Try the Asus drivers - Goto Device Manager. Right click on "Android" and choose "Update Driver" and do a "Manual install" and select the extracted Asus drivers. Also the tablet could be listed under "Other devices". Make sure to reboot your PC when done.)
fastboot erase cache
(Please note do not use command "fastboot erase system" - it has caused many people issues and is useless)
(Please note "fastboot erase userdata" is optional. the command is a "factory reset" and removes all user data. Sometimes after an update the tablet may be sluggish or have issues then you could try this command)
fastboot flash update US_ME302C-V5.0.16-0-ota-user.zip
If it is working your CMD window will show:
sending 'update' (******* KB)...
OKAY [49.549s]
writing 'update'...
OKAY [3.220s]
finished. total time: 52.772s
Tablet will take time to apply update.
After successful reboot place US_ME302C-V5.0.17-0-ota-user.zip in the internal Storage via Windows Explorer
(Alternatively, reboot into bootloader and apply 5017 root update using command "fastboot flash update US_ME302C-V5.0.17-0-ota-user.zip")
Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet
You are now root. Install SuperSU by Chainfire from Play Store. For BusyBox use BusyBox X by Robert Nediyakalaparambil.
Optional:
1) Install AdsFree from http://adfree.bigtincan.com
2) Review the German forum (link at top) for apps that can be safely frozen or uninstalled via Titanium Backup
+++++++++++++++++++++++++++++++++++++++++++++++++++
Step by Step Guide for Factory Reset via Fastboot Method for US version >4.7.3:
Please note that tablet with versions higher than 4.7.3 no longer have the ability to use the fastboot method as this has been disabled by Asus in the latest versions. You’ll need to downgrade fastboot to 4.7.3 before restoring your tablet. Extract Fastboot.img from US_ME302C_V4_7_3.rar using 7 zip (~700MB download, link below) or download just Fastboot.img (~10mb, Mediafire link below) into same directory as ADB and Fastboot
Tools Needed:
Intel Drivers - http://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Asus Drivers - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME173X/ASUS_Android_USB_drivers_for_Windows.zip (download these in case Intel drivers don't work)
ADB and Fastboot tools - http://forum.xda-developers.com/showthread.php?t=2588979 (say no to drivers, just install adb)
Linux Fastboot for Intel SoC - http://www.android-hilfe.de/7373742-post8.html
USA Fastboot 473 IMG - http://support.mediafire.com/download/dk487lcxqfsgau6/fastboot473.zip
USA Asus 473 update – http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME302C/US_ME302C_V4_7_3.rar
USA Asus 5016 update - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME302C/US_ME302C-V5_0_16-0-ota-user.zip
USA 5017 root update - https://docs.google.com/file/d/0B-6nm7Jks0W5eWxSM0JoZ2FPVGc
Enable USB Debugging:
The “Developer Options” menu item on 4.2.* is hidden.
1. Goto Settings -> About Phone.
2. Goto “Build Number” at the end of the Scroll list.
3. Tap on “Build Number” repeatedly (7 times). On your third tap you should see message indicating that you only have 4 more taps to go to ‘become a developer’.
4. Continue: 4 more taps.
5. Hooray, you are now a ‘Developer’, go back to the Setting page.
6. You should see Developer Option menu item in your setting list now.
7. Open Developer Options and check USB debugging > OK
Install ADB and Fastboot from above (say no to drivers, just install adb)
Install Intel drivers
Plug in USB cable (at this point your PC will auto install several devices)
adb devices
(if you don't see a device you have a driver issue. Try the Asus drivers - Goto Device Manager. Right click on "Android" and choose "Update Driver" and do a "Manual install" and select the extracted Asus drivers. Also the tablet could be listed under "Other devices". Make sure to reboot your PC when done.)
adb reboot bootloader
Wait for tablet to reboot into bootloader. You'll see an Android with a hard hat
fastboot devices
( if you don't see a device you have a driver issue. Try the Asus drivers - Goto Device Manager. Right click on "Android" and choose "Update Driver" and do a "Manual install" and select the extracted Asus drivers. Also the tablet could be listed under "Other devices". Make sure to reboot your PC when done.)
fastboot erase cache
fastboot flash fastboot fastboot.img
be patient while update completes then reboot back to bootloader
adb reboot bootloader
fastboot devices
fastboot erase cache
fastboot erase userdata
fastboot flash update US_ME302C-V5.0.16-0-ota-user.zip
tablet will take time to apply update.
After successful reboot place US_ME302C-V5.0.17-0-ota-user.zip in the internal Storage via Windows Explorer
(Alternatively, reboot into bootloader and apply 5017 root update using command "fastboot flash update US_ME302C-V5.0.17-0-ota-user.zip")
Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet
You are now root. Install SuperSU by Chainfire from Play Store. For BusyBox use BusyBox X by Robert Nediyakalaparambil.
Optional:
1) Install AdsFree from http://adfree.bigtincan.com
2) Review the German forum (link at top) for apps that can be safely frozen or uninstalled via Titanium Backup

One little note:
fastboot flash update <name-of-the.zip> only works with the 4.2.2 fastboot. On 4.3 it only works with small zips, like the fake update.zip for root.
The easiest way to update is to place the update zip on to the internal storage and select the triangle from the notification bar to start the update process. (it's the same way like with the root zip)

cantdownload
Cant download 2nd link

Beware
Hey Guys, after I applied these "updates" and checked root (positive) I installed the Xposedframework , when I rebooted my Memo , it does not get much further then the ASUS logo and never-ending busy circle. I will attempt a factory reset, and let you all know.
Just posting this message to make sure you have your backup done as mentioned in the first post. It could be painful otherwise!

Hi
can u help me root asus zenfone 5 ?
or tell me how to make a update ota zip flashable to flashed on stock recovery..
thx for reply me...

Hi all. Thanks for the great post. This forum helps a lot who would other wise be lost.
I am a bit confused about the methods posted in the opening post. The first method explains DL the files and install from internal storage which seems simple enough. But then I scrolled down to see the second method via fastboot.
I would prefer to use the first method as it appears simple as I have said. But unsure which I should use.
Also how can I backup without root access?
Thanks for your help
Mode l# ME302C
Firmware version: 51.31
Android Version: 4.2.2
Build # US_EPAD-4.6.2-20130815
Edit: I jumped in and used the procedure described in "For those of you who are not rooted "(or the second method of the first 2). It worked. My memopad is now rooted and appears to be operating fine. Thank you to the author of this post.

help needed
Why can't I get the magic yellow triangle? Somebody please help me.
Here are my screen shots from my google+, please remove the blank space at the beginning of the address:
ht tps://plus.google.com/106139843999975472357/posts/818h3Tbagkm
ht tps://plus.google.com/106139843999975472357/posts/Z6J5iTEPswP

Asus302c said:
Why can't I get the magic yellow triangle? Somebody please help me.
Click to expand...
Click to collapse
Try plugging it into a computer or rebooting.

Would installing the latest version of the firmware get rid of the root access? V5.0.19 is the latest, from the end of May. http://usterki.hobby-elektronika.eu/biazet.html

Polarbert said:
Would installing the latest version of the firmware get rid of the root access? V5.0.19 is the latest, from the end of May.
Click to expand...
Click to collapse
Yes and you risk to get big trouble if SuperSU survival mode is active. For save updating you have to remove root first.
Gesendet von meinem ME302C mit Tapatalk

I just wanted to say:
I got the Memo Pad FHD 10: It lagged in slowness a bit in a few well known apps. Also when browsing the internet. Also the kicker for knowing I had to 'Root' was certain apps use the 'System font' for Chinese-Pinyin display. Asus-Memo Factory-font does not display accented characters well. But the standard setting do not allow adjustment to the System-font.
Your Easy instructions under: 'For those who are not rooted'... Were simple. I downloaded the two files... 5.0.16 (Although: Note I needed to rename, the 5.016, to exactly match what you said. The filename was slightly different.)
I was a little scared, even though I had already upgraded the firmware of my Tablet to 51.31, but another poster had that number as well, so I decided to boldly press-on.
Then I put the 5.017 and boom... and installed the SuperSU file as instructed... and a way I went! Thanx! Thankx! :good: I put on HiFonts and found a font that was suitable for the system. The pad is also now so much snappier!!! I hope that doesn't mean the battery is now going to drain at an alarming rate. I haven't tested that yet. :

GPS Working 5017
intrepid24 said:
This post (#377 on page 38) was origina
Click to expand...
Click to collapse
Is anyone else having an issue with the GPS on the device on 5016 rooted with the 5017 using the 'intrepid' link above. A favorite app we use: 'Copilot', does not get past "determining position". I'm speaking of when the device does not have an internet connection.
The app I speak about is designed to work without only the GPS available. But since I'm on an odd build, instead of checking with the problems on those ends. I figured, I worry first about the build itself.

I know this may be quite an old thread, but I've stupidly updated my fathers tablet to 5.0.21, and in the process lost root. Is there any trouble with following this method to get back to 5.0.17 and rooting the tablet? After updating I saw no difference, and thus no need to lose root access.
http://www.gory.pun.pl/viewforum.php?id=5
Is there an alternative to getting root? I've tried towel root and framaroot but neither of these worked.

To this day this tablet has treated me well...Is there any kitkat roms floating around the web for this tablet?

asus memo pad me302c stuck on boot screen
Hi guys! I`m new on the forum so i don`t know if this is the right place to ask... I have this Tablet stuck on boot screen and i tried every solution i found on internet but nothing seems to make it work... Can someone give me a clue about what can i do? Thank you!

I have the same problem. I have this in DroidBoot:
IFWI Version: 51.33
Serial_num: 11111111111111
Product: WW_EPAD
I've tried to flash many files, flashed earlier fastboot versions, but I'm totally stuck here

_MsG_ said:
I have the same problem. I have this in DroidBoot:
IFWI Version: 51.33
Serial_num: 11111111111111
Product: WW_EPAD
I've tried to flash many files, flashed earlier fastboot versions, but I'm totally stuck here
Click to expand...
Click to collapse
What works depends on what you were doing before this issue appeared.
If you can read German, you can check:
http://www.android-hilfe.de/thema/a...k-asus-memo-pad-fhd-10-ab-android-4-3.528918/
I'd recommend trying the RAW update.

Ok now I have the same problem with everyone having this tablet. Many of the apps have been upgraded in the world, but no longer support Android 4.3 anymore. We need at least 5.0 to work. And I can find no custom-roms. At first search I thought one was available, but then found it was not for the ME302C. The 'C' version is the intel chip. We need a wizard to create a rom.

robertkjr3d said:
Ok now I have the same problem with everyone having this tablet. Many of the apps have been upgraded in the world, but no longer support Android 4.3 anymore. We need at least 5.0 to work. And I can find no custom-roms. At first search I thought one was available, but then found it was not for the ME302C. The 'C' version is the intel chip. We need a wizard to create a rom.
Click to expand...
Click to collapse
How did you get the bootloader unlocked to be able to install a custom recovery and then a ROM to begin with? I chatted with Asus support just now and they said that for the ME302C they never made an unlock tool which I don't believe. I have an ME301T and they made the tool for it and I was able to unlock the bootloader, root and custom ROM. I was going to root my friend's ME302C but without being able to unlock the bootloader to install a custom ROM I don't see the point. Thanks in advance!

Asus ME302KL will this be the same process?

[GUIDE]RCA Maven Pro (RCT6213W87DK), Bootloader, Custom Recoveries, Firmware and Root

SPECIAL KNO'DIS: This Guide has been changed to refelct proper installation for both types of Maven Pro tablets, be Sure to follow the appropriate guide.
For the purpose of this guide, I'll assume you already have working ADB and Fastboot on your PC, if not, you'll need to set that up first. This guide doesn't cover installation of ether of those. If you're looking for the guide to the Viking Pro (RCT6303W87DK), go here.
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR TABLET!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!!​ (Or ask for help, there's a lot of friendly people around here)​
So, without further ado, lets get started. First, you'll need to know which version of firmware your device is running, this can be found in 2 different ways. From a running device go to: Settings/About tablet and look at the Build number. Or you can boot into stock recovery and the firmware version will be at the top left of the screen.
You should see something like the following, and note the 2nd number after the 2nd "V":
Code:
RCT6213W87DK-ANDROID5.0-V37-V1.9.30 <-- This is x.9.x version of firmware
or
RCT6213W87DK-ANDROID5.0-V68-V1.12.30-B <-- This is x.12.x version of firmware
Now that you know which firmware you have, follow the approriate guide below. I've broken this post into 2 different sections, as each tablet is just a little bit different.
About the Bootloader​
This applies to both versions of firmware and tablet users. Turns out, the booloader doesn't have to be unlocked in order to install a custom recovery or root the device. So there's really no reason to unlock it, and I have removed that portion of this guide.
Installing MTK Preloader Signed Drivers​
Drivers located Here
x.9.x Versions
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the micro USB on the tablet, the other to the USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
3- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
4- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
5- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug the usb cable from the pc (I find it easier to just keep the micro in the tablet).
x.12.x Versions (Requires Full size Male-to-Male USB Cable)
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the full size USB cable to both the tablet and the PC.
3- Plug the micro USB into the tablet, the other to another USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
4- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
5- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
6- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug both USB cables from the PC (I find it easier to just keep them in the tablet).
Installing TWRP​
Firmware/TWRP Downloads
Maven x.9.x (Currently Contains: V37-1.9.30 and TWRP)
Maven x.12.x (Currently Contains: V63-V1.12.0-20150802 and V66-1.12.20-B-20150831 Firmware and TWRP)
Special Thanks to: @ShadowCX11 for testing for me.
Be sure you are using the appropriate TWRP for your version of firmware, and do the following:
1- Extract the firmware and the SP Flash Tool to your desktop.
2- Start the SP Flash Tool, and where it says "scatter file loading" click and navigate to the folder where you have the firmware and load the scatter file (depending on device, it could be in the "Images" folder).
3- Once that is done, uncheck everything, and select "recovery" only, from the list, navigate to the TWRP image file and click "Open", then click on the download button.
4- Plug the USB cable(s)* back into your PC. At this point the flash tool will load the recovery to the tablet. DO NOT UNPLUG ANYTHING UNTIL THE FLASH TOOL SHOWS YOU A GREEN CHECK MARK TO INDICATE THAT IT IS DONE, OR YOUR TABLET COULD BE HARD BRICKED AND IRREPARABLE.
5- After you get your check mark, unplug and boot into recovery, hold the Volume + and Power button. When splash screen comes up (the 2 dogs) release the power button.
6- Welcome to TWRP
*Remember, x.12.x requires 2 USB cables to work
ROOT​
You can get root by flashing the latest SuperSu zip file located here, be sure to download the flashable zip.
Otherwise, for root, you can use the KingRoot app located here, (get the apk, or "Download for Android") and if you don't want a Chinesse Super User app, you can replace it with the ChainFire SuperSu by going here.
NOTE: This method of replacing KingRoot with SuperSu no longer works properly, and results in a bricked device.
Device Tree
GitHub
CREDITS
@vampirefo (for the CWM Recovery and teaching me about TWRP, there would be no recoveries if it wasn't for him!)
@Bogram (for the lk.bin patch trick)
@smartmanvartan (for the flashing guide)

Reserved

Reserved #2

Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)

equinox13 said:
Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)
Click to expand...
Click to collapse
Ooh, a v12, sorry friend, lol. Make sure the tablet is off, and be ready with "Device Manager" open, the preloader only shows up for a bit, then it disappears. The patch tool should still work for you, but the TWRP recovery may not. If it doesn't, the CWM recovery will after I modify it, because it's non-touch.
If neither recovery works for you, you can give me a copy of your "boot.img" file, and I can convert TWRP or CWM to work on your tablet. Also, I've changed the guide up top to include other root methods.
If you have any trouble, by all mean, post, and I'll try to help you through it
Regards,
Nepo
EDIT:
A friend found some V12 firmware, and I'll be uploading it soon. I can get a boot.img file from it to make a recovery.

My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down

GartimusPrime said:
My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down
Click to expand...
Click to collapse
You can reflash firmware while it is in a bootloop, I've done this many times. If you have everything set up, drivers, SP Flash Tool, firmware, etc..
Do the following:
1) Startup the Flash Tool and Load your firmware, as described in the OP (be sure to "uncheck" the Preloader)
2) Plug in your micro USB cable to both the PC and the tablet
3) Press and hold the "Reset" button located on the back
4) Click the Download button, then let go of the reset button, it should start flashing the firmware.
If it doesn't the first time, retry steps 3 and 4. I've had it fail the first time before, but work on the second.
Good Luck and let me know how it goes. Also, if the battery is completely drained by the time you read this, just flash firmware normally (again, uncheck the preloader). The tablet has to be powered off to flash it anyway.
Regards
Nepo

So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?

ShadowCX11 said:
So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?
Click to expand...
Click to collapse
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)

NepoRood said:
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)
Click to expand...
Click to collapse
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.

ShadowCX11 said:
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.
Click to expand...
Click to collapse
Yes, to pull a copy from a running tablet you use dd, and the path is: /dev/recovery
So, I'd do it this way, using adb:
Code:
adb push NAME_OF_RECOVERY.img /data/local/tmp
# Wait for it, then type:
adb shell
#Followed by:
dd if=/data/local/tmp/NAME_OF_RECOVERY.img of=/dev/recovery
#After it finishes:
reboot recovery

Okay, I got CWM installed! Now to see if I can find a way to build TWRP...

ShadowCX11 said:
Okay, I got CWM installed! Now to see if I can find a way to build TWRP...
Click to expand...
Click to collapse
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.

NepoRood said:
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.
Click to expand...
Click to collapse
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.

ShadowCX11 said:
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.
Click to expand...
Click to collapse
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo

NepoRood said:
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo
Click to expand...
Click to collapse
Yeah, I can't figure out how to extract the kernel, because I don't usually have access to a PC. However, I'll take some testing builds if you can make them.
Also, back to the USB issue, a reflash of everything except preloader didn't fix it. However, checking the firmware update now tells me that this is the latest version (which is definitely wrong, since I had v68). It must be an incompatibility between the USA and Canadian variants. If you find a Canadian firm dump, can you send me a link?
---
Hmm, okay.
So I just took a look at the model number on my box, and it's RCT5213W87DKF. That extra letter is what changes this a bit. I'll try seeing what I can dig up in terms of OTA updates, and I'll keep posting about what I find.
---
Okay, so after a few packet captures, I found the tablet makes a GET request to http://tablet12.gyrodock.com:2300/OtaUpdater/android?device=RCT6213W87DK with the User-Agent rk29sdk/4.0, but the server returns a 404 page. When I do this in the browser, however, I get something quite peculiar happen, which interests me. Most of the other places on the site return a Tomcat 404 that has the path in the parenthesis. However, for the OTA URL, it just has empty parenthesis. POST requests to that URL return a 200 OK with no return data, which is also interesting. I'll keep hunting around.

Some people might not have a PC to run flash_tool on, so here's how you can flash recovery/uboot/mbr/ebr2/logo/sec_ro from within Android
I'll use recovery as an example. I'm using a V12 tablet, so steps might be different if you have a V9. I tried to make this guide as revision-agnostic as possible, so correct me if I mess something up.
Root your device. The method I use is KingRoot, because it doesn't require any weird things. You can uninstall KingRoot and flash SuperSU later.
Download a recovery image. Make sure if you have a V12 tablet, you download a recovery image for V12, and a V9 recovery for a V9 tablet, or you'll brick your recovery. I personally prefer TWRP, because it has more features and a nicer UI, but CWM works too.
Get shell access. You can use a terminal emulator.
Type in su, and give the terminal superuser access on your device.
Type in dd if=/sdcard/Download/mavenVY_XXX.img of=/dev/recovery, where Y is 9 or 12, and XXX is CWM or twrp3.0.2. This will flash the recovery image.
Finally, type in reboot recovery. This should reboot into your custom recovery! It might also enable Power + Vol Up access to recovery, however, this hasn't been confirmed.
All the other partitions are similar, just replace the references to recovery images with the respective file names for the raw partition, and /dev/recovery with /dev/[PARTITION]. You can NOT flash the android or usrdata partition while in Android or you'll most likely soft-brick your tablet, however, you can boot into TWRP and go to the terminal and do the flash. You must copy your disk images to /tmp when doing so however, or you'll probably lose the disk image during the flash, effectively causing a brick.
Hope this helps people out!

ShadowCX11 said:
I've found out that it seems the v12 tablets strictly enforce the checksums of partition images, so flashing a custom recovery or uboot does not work with flashtool.
Click to expand...
Click to collapse
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...

NepoRood said:
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...
Click to expand...
Click to collapse
Oh... makes sense...

ShadowCX11 said:
Oh... makes sense...
Click to expand...
Click to collapse
I'm glad you posted that info, it'll be super handy for folks that may not have access to a PC, or would rather use their device instead of a PC :good:

Nextbook Ares 8A with Android 6.0.1 root solutions

UPDATE: Please read the updated information at the bottom of this post, on my new recommendation to use the easier method, SuperSU systemless, to patch your original boot.img. This is in my quick start guide at the end of it, also. You still need to read my info on getting setup, also.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have started this thread as a place to post a working root solution for this tablet.
https://www.walmart.com/ip/Nextbook...-System/122137749?variantFieldId=actual_color
This is a great Android tablet for the price. It features an updated Intel Cherry Trail quad core 1.92 GHz processor, 1gb RAM, 16gb internal storage. and Android 6.0.1 Marshmallow.
UPDATE: There is a newer version of the tablet with a manufacturing sticker date of September, 2017. Despite retaining the 8A model number, it has a slower, ARM processor and Android Nougat 7.1.1. Although it is quite snappy, It shows much slower benchmarks in AnTuTu and has a much smaller battery, about half the size. Also the boxes are about 2/3 the thickness of the older, 6.0.1 tablets.
The chances of rooting it are very slim. My solution will not work for it. Fastboot mode appears to be disabled on this and one other Nougat tablet that I own. I am returning the one I tested.
UPDATE: I now have root, a custom TWRP recovery and modified boot images for the Android 6.0.1 version of this device.
I would like to thank @vampirefo for his TWRP and original boot images, for without his work, this would not be possible.
PLEASE DO NOT CONTACT HIM ABOUT THIS HE WILL NOT PROVIDE ANY SUPPORT FOR IT, THAT WILL BE PROVIDED BY ME AND OTHER GENEROUS FORUM MEMBERS.
I strongly recommend, though that you donate to him, in his signature, for all of his hard work on this, even if it is a small amount. I asked him twice about this and he never responded, so please donate to him.
His original boot.imgs are modified to remove encryption and make the kernel permissive.
I unpacked them and removed dm_verity to remove the failed verification message, on boot then repacked them.
FILES ARE UP ON ANDROID FILE HOST
https://www.androidfilehost.com/?w=files&flid=197521
Choose the version of the tablet that you own. Go to settings, about tablet and scroll to the bottom and look at the first few numbers of the build number. For example: V1.2.0.
Do not use this on the 1.0.8 version of the tablet or you will loose sound, wifi and maybe bluetooth. If you have this version of the tablet and can provide me a twrp, backed up, original boot.img, I can modify it to work with your tablet. You can temp boot twrp, to do this (see below). As of yet no one has provided one to me for the 1.0.8 tablet version.
UPDATE 10/24/2017: I now have a I now have a 1.0.8 modified boot.img up on android file host:
https://www.androidfilehost.com/?fid=962021903579487577
Here is a twrp backup of the 1.2.0 rom, with userdata deleted to start fresh. It will boot to the Android setup screen. If you have any major, unexplained problems, I recommend starting fresh with this. It works great on either tablet version: 1.1.1 and 1.2.0.
https://www.androidfilehost.com/?fid=673368273298970542
UPDATE 12/15/2017: I have uploaded a pre-rooted TWRP backup of my original V1.1.1 tablet
https://www.androidfilehost.com/?w=files&flid=235141
TO PREPARE YOUR DEVICE:
UPDATED 12/3/2017: I now have found a Version 2.1.5 of the tablet and have uploaded an unrooted, TWRP backed up version of it. It also contains the original recovery so do not check that box when flashing it in TWRP unless you intend to replace TWRP with the stock recovery
https://www.androidfilehost.com/?fid=673791459329065002
This will be long and thorough, because I see so many people who have trouble with this because they don't have their computer setup properly from the get go.
This will help you get ready to be successful in applying this.
First and foremost, unlocking your bootloader will delete all userdata on the tablet so you need a good backup of important files. If you backup to an external sd card, I strongly recommend also copying the files to an external source such as your computer. You can do that through mtp or remove the card and place it in an sd card adapter and insert it into an sd card reader. I did not do this, even though I knew better and my sd card was corrupted in the process, so I lost the original twrp backup of the virgin, untouched system partition.
Secondly, if you are on windows you need the proper drivers for adb and fastboot installed on your system. Proper drivers are the number one issue I see with windows users. For this Intel device get them here:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Here are the steps to install adb and Intel drivers, in the proper order:
The best way to to set up adb and fastboot in windows is to install it system wide. Here is an installer to do this that works well:
https://forum.xda-developers.com/showthread.php?t=2588979
Install process for 15 sec adb:
1. Run it (Require administrator privileges)
2. Press Y/Yes to install ADB and Fastboot
3. Press Y/Yes to install ADB system-wide
4. Press N/No to skip installing Drivers
5. 15 seconds passed - finished!
6. Now install the Intel drivers listed above and here, again:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Third, enable developer options by going to settings, about tablet, and tap on the build number seven times to enable it.
Then go to developer options and make sure usb debugging is enabled. watch on the tablet screen for a popup dialog the approve usb debugging. check the box to always allow for this computer and hit ok.
Now, with the proper drivers installed, adb and fastboot properly installed, You need to test that it is functioning properly. This is done with the tablet booted into Android. If you used the adb I recommended, go to my computer, C drive and open the newly created adb folder. Left click in an open area of the folder to select it. then shift right click to open a contextual menu, then select: open a command prompt here. Once the command window is open, type:
Code:
adb devices
and hit enter:
you should see the device serial number listed. I am now doing this from linux, so it may differ,slightly:
adb devices
List of devices attached
YFGV1216059870 device
Sometimes you get starting daemon on port... and you have to type it again to see the device listed. If you don't see this, then your drivers or adb/fastboot aren't properly installed.
If you see your device, then type:
Code:
adb reboot bootloader
and hit enter. your device should now reboot to bootloader mode. once in bootloader mode, type:
Code:
fastboot devices
enter and you device should once again be listed.
the next step, is to unlock your bootloader. Warning: ALL OF YOUR USERDATA WILL BE DELETED, HENCE THE BACKUP CREATED EARLIER. YOU HAVE BEEN WARNED!
It has come to my attention that this is not clear: after unlocking the bootloader, all userdata will be deleted, like doing a factory reset.
Go into developer options and select OEM unlocking. This does not unlock your bootloader, it only enables the ability to do it from a fastboot prompt.
Now jump to the Quick Start guide for updated instructions:
Older, system mode method hidden, please use the instructions in the Quick Start Guide
Now, while still booted into bootloader mode, type:
Code:
fastboot flashing unlock
and hit enter to unlock your bootloader. All data will be deleted and the tablet will be re-encrypted upon boot, without encryption option removed from the bootloader. Now type
Code:
fastboot reboot
t, to reboot the tablet and you should reboot to the android setup screen, You can set it up again if you want, but you will be deleting userdata later when you flash the modified boot.img, so keep this in mind.
So you may want to wait to unlock until I release twrp and the boot.img, so you can continue using the tablet.
UPDATE: The files are now live.
To summarize, the above steps are to prepare you for the next exciting adventure to come and to realize the full potential that a rooted device offers..................
To be continued.
THE FILES ARE NOW ON ANDROID FILE HOST. DOWNLOAD HERE:
https://www.androidfilehost.com/?w=files&flid=197521
Boot or flash TWRP Recovery and flash boot.img
These instructions are for Windows, for Linux you must type sudo before fastboot commands
Instructions: first make sure you read the instructions above to be sure you have the proper drivers and adb and fastboot are installed and tested before proceeding. Unlock your bootloader per above instructions. WARNING! DANGER WILL ROBINSON! THIS PROCEDURE WILL DELETE ALL USERDATA ON YOUR TABLET SO BE SURE YOU HAVE A BACKUP OF ANY IMPORTANT DATA.
First, unzip the files to a directory. I usually do it in C:\adb, and leave the SR2-SuperSU-v2.82-SYSTEMMODE.zip, zipped.
Now, left click in that folder in an empty spot, or where ever you unzipped it and select it. Now right click and choose open a command prompt here from the contextual menu. once the command window is open type
Code:
adb devices
, hit enter, to confirm your device is listed. Now type
Code:
adb reboot bootloader
and it should reboot to bootloader mode.
I recommend booting into twrp temp first so you can backup your original boot, recovery and system.
now:
Code:
fastboot boot Ares8A_recovery_twrp.img
enter and it should reboot to twrp temp. Don't choose read only after it boots. Once in twrp choose backup and hit select storage and choose micro sdcard. now swipe to backup. You can later install twrp permanently if you want to. To flash permanently:
From bootloader mode:
Code:
fastboot flash recovery Ares8A_recovery_twrp.img
UPDATE: See the the end of my updated quick start guide for updated info on a simpler method to patch your original boot.img with either systemless SuperSU or Magisk. I no longer recommend flashing my patched boot.imgs, but instructions are still provided here for historical reference and for the few who still want SuperSu in the unofficial, system mode.
I have hidden the older method here, but is still here for those who still want system mode SuperSU:
Now
Code:
fastboot flash boot Ares8A_111_boot.img
enter, for the 1.1.1 version, or
Code:
fastboot flash boot Ares8A_120_boot.img
enter, for the 1.2.0 version, to flash the appropriate boot.img
For the newer 2.1.5 version of the table:
Code:
fastboot flash boot unsigned-new.img
hit the enter key, to flash.
Next, again in bootloader mode issue:
Code:
fastboot format userdata
enter, and wait for a successful message in the command window and on the tablet. it will take a little while.
Next
Code:
fastboot format cache
enter, wait. Now
Code:
fastboot reboot
hit enter, and the tablet should reboot to the android setup screen where you can set it up. It will take some extra time to reboot, so be patient. You may see the boot animation for awhile. This will be booted unencrypted now without root. I recommend doing a backup again in twrp before rooting.
There has been some misunderstanding about the above. Your data is encrypted and will not be accessible it twrp, hence, the backup before you do anything with this tablet.
You must wipe the userdata, so a new, clean data partition can be created that is unencrypted. A factory reset is not enough. You will have problems if you don't format userdata in the above step to created a decrypted data partition.
Flashing SuperSu for root
For the v1.1.1 and v1.2.0 tablets:
Make sure you have the SR1-SuperSU-v2.82-SYSTEMMODE.zip on your ext sd card.
For the newer 2.1.5 you need a systemless version of SuperSU:
SuperSU-v2.82-201705271822.zip Get it at:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip Copy it to your external SD card.
When flashed, this systemless version will also patch your boot image for sytemless mode.
Furthermore, to install SR1-SuperSU-v2.82-SYSTEMMODE.zip, or SuperSU-v2.82-201705271822.zip, either boot twrp temp again, from bootloader mode issue:
Code:
fastboot boot Ares8A_recovery_twrp.img
, or if you already have it installed permanently and you are booted normally, issue
Code:
adb reboot recovery
enter to boot to it.
Next hit the install button in twrp and choose SR1-SuperSU-v2.82-SYSTEMMODE.zip or SuperSU-v2.82-201705271822.zip and swipe to confirm flash. after it is complete, go back to the main menu and choose reboot system. I choose not to install the twrp app before reboot.
Once rebooted, open the supersu app, making sure the following are selected in settings enable superuser, default access prompt or grant, enable su during boot, trust system user and enable pro, then go back and enable full content in logging. Next download a root check app to confirm root.
congratulations you should now be rooted! Now download a desired app that requires root and test to confirm you have no problems with root.
If you want an app that makes it easy to reboot in the various modes, I recommend Simple Reboot by Francisco Franco. It works great with this device and android version.
I was using Easy Reboot [ROOT] by Simone Luconi with my older, ares 8 with 5.1.1 and it had worked well.
Apparently it is not compatible with this device or rom. when I rebooted to recovery with it, I was not able to mount my external sd card and the card was corrupted on reboot. That is why I don't have a virgin, unrooted, copy of my system image now.
Good luck!
Here is a quick start guide for the already initiated:
https://forum.xda-developers.com/showpost.php?p=72970060&postcount=82
Here is a link to my post for some apps I personally find useful:
https://forum.xda-developers.com/showpost.php?p=72995672&postcount=112
Please report successes and problems on this thread, not to @vampirefo.
Thanks

@vampirefo has a solution, but has not released it. I'm not sure if it needs more work or testing before release? He has been quiet in this regard. It is my hope that he will reply with more relevant information about this.
I and maybe others, would be willing to give a donation, if that would help.
Thanks

Bootloader unlocking
WARNING! UNLOCKING THE BOOTLOADER WILL DELETE ALL OF YOUR DATA!
DON'T DO THE UNLOCKING UNTIL WE CAN REMOVE ENCRYPTION AND HAVE TWRP FOR BACKUP. YOU HAVE BEEN WARNED!
You can enable the ability for the bootloader to be unlocked with a setting in the developer options. Like I stated, it enables the ability to unlock it, but does not unlock it. On must use the command in adb, through a computer. make sure usb debugging is enabled in the developer options. In a command prompt issue adb devices to make sure your device is showing up. There will be a prompt on your tablet to allow this. Confirm this.
Now with the tablet off, boot into fastboot by hold the volume key down button and the power button at the same time. Also, you can type: adb reboot bootloader then hit enter to get into bootloader or fastboot mode.
Once in fastboot mode, open a command prompt in windows and type fastboot devices to confirm your device is still showing up. If my memory serves me correctly there will also be a security confirmation on the tablet, to approve.
To unlock the bootloader type: fastboot flashing unlock. All data will be deleted and (I believe,) the tablet will be re-encrypted upon boot, without encryption option removed from the bootloader.
I HAVE NOT TESTED THIS, AS I DON'T WANT TO DELETE DATA, UNTIL WE HAVE TWRP TO BACKUP AND ROOT.
6/7/2017 UPDATE: I HAVE UPDATED THE UNLOCK COMMAND. I HAVE UNLOCKED MY BOOTLOADER. AS I THOUGHT, ALL USER DATA IS DELETED (FACTORY RESET). I USED THE FIRST:
"fastboot flashing unlock" Unlocks the device. Allows flashing any
partition except bootloader-related
partitions
"flashing unlock_critical" Enables flashing bootloader-relate partitions.
all fastboot commands are listed by just typing fastboot, while booted into bootloader mode. My tablet is still running great with my bootloader unlocked. One more tiny step toward gaining root, however, there is still a long way to go.
Please post any additional info if I have something wrong, or left out any important steps.
Thanks

Geenify: How to grant permissions required by some features on non-root device?
I am currently using Greenify on my non-rooted device and it is working very well.
By using adb, one can grant it additional permission so it performs almost as well on an unrooted device. Here is a link for this:
https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
I copied and pasted each command, one at a time, in the command prompt then hit enter, to enable each one.
In Greenify settings, I also have aggressive doze enabled, Automated hibernation enabled, Wakeup Tracker enabled and Quick action Notification enabled.

How to boot into stock recovery mode
To boot to the stock recovery through adb:
adb reboot recovery
You will see "no command" on the tablet.
Hold the power button and volume up for about 4sec then release the volume up, where you should go to the stock recovery screen.
You can also get to it without a computer. With the tablet shut down, hold the volume down power button until it boots to bootloader or fastboot mode.
Use the volume up or down button to toggle through the options: normal boot, restart bootloader, recovery mode, reboot, power off and ftm mode. Choose recovery and use the volume up and power button as before.
In addition you can get to the efi bootmanager by holding the volume up, power button when the device has been shutdown first.

adb security confirmation
Unlike my Nextbook Ares 8 with 5.1.1, with this newer tablet which has 6.0.1, I have to reaffirm the security prompt on the device each time, despite checking the box: "Always allow from this computer".
Maybe this is because of the tightened security in Android Marshmallow? I'm not sure.
If there is a way around this each time, please let me know
Thanks
UPDATE: After I unlocked the bootloader and the tablet was factory reset, I no longer have to re-approve each time after checking the box: "Always allow from this computer"

Would love to see some break throughs with this device aswell. Cheers to any one working in it.

Is this relevant? It would seem they are the same device. twitter.com/srsroot/status/846663673645010944?lang=en

Giftlift said:
Is this relevant? It would seem they are the same device. twitter.com/srsroot/status/846663673645010944?lang=en
Click to expand...
Click to collapse
Don't try any of these one click root solutions. none work to my knowledge on android 6.01, (at least on this device) , and may install malware or pups on your host computer.

martyfender said:
Don't try any of these one click root solutions. none work to my knowledge on android 6.01, (at least on this device) , and may install malware or pups on your host computer.
Click to expand...
Click to collapse
:good::good:

This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk

vampirefo said:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
@vampirefo Thanks for taking the time to post this.
To familiarize myself with Linux, I created a persistent linux Mint 17.2 Mate 64 bit on a 32 gb usb thumb drive before I decide to commit my windows machine for a linux install.
I installed oracle jdk and android studio thinking this was the build environment needed to do this. the twrp compile forum makes no mention of what to do in this case. I must have been wrong? I don't think I need this to download and build android kernel sources and twrp source?
I'm now very doubtful about even tempting to do this. Yes, a lot of work just learning the basics of linux, let alone following the steps you give in your basic outline. I don't want to give up so easily, but the learning curve is steep.
So one just uses terminal commands to setup and download aosp and twrp git repositories and to make them? Also, is there any way to backup my device system, boot and recovery without root in linux or windows? I have used the adb pull command to backup the system directories to my windows computer, but don't know how to do it for other partitions, if possible.
I found this kernel building guide for arm and mediatek devices. would this be similar for Intel using the right repositories?
https://forum.xda-developers.com/android/software/guide-easy-kernel-building-tutorial-t3581057
Thanks
Click to expand...
Click to collapse

martyfender said:
vampirefo said:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
@vampirefo Thanks for taking the time to post this.
To familiarize myself with Linux, I created a persistent linux Mint 17.2 Mate 64 bit on a 32 gb usb thumb drive before I decide to commit my windows machine for a linux install.
I installed oracle jdk and android studio thinking this was the build environment needed to do this. the twrp compile forum makes no mention of what to do in this case. I must have been wrong? I don't think I need this to download and build android kernel sources and twrp source?
I'm now very doubtful about even tempting to do this. Yes, a lot of work just learning the basics of linux, let alone following the steps you give in your basic outline. I don't want to give up so easily, but the learning curve is steep.
So one just uses terminal commands to setup and download aosp and twrp git repositories and to make them? Also, is there any way to backup my device system, boot and recovery without root in linux or windows? I have used the adb pull command to backup the system directories to my windows computer, but don't know how to do it for other partitions, if possible.
Thanks
Click to expand...
Click to collapse
All work is done in terminal, root is required to make backups.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse

vampirefo said:
martyfender said:
All work is done in terminal, root is required to make backups.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
So I could uninstall android studio. Should I also revert back to openjdk? I see it mentioned in google docs on setting up a build environment.
UPDATE: I think I have now setup properly. Reverted to openjdk 8
I downloaded this: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8
I found this: https://github.com/CM-CHT/android_device_intel_cherrytrail-common Would this be useful?
Thanks
Click to expand...
Click to collapse

martyfender said:
vampirefo said:
So I could uninstall android studio. Should I also revert back to openjdk? I see it mentioned in google docs on setting up a build environment.
UPDATE: I think I have now setup properly. Reverted to openjdk 8
I downloaded this: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8
I found this: https://github.com/CM-CHT/android_device_intel_cherrytrail-common Would this be useful?
Thanks
Click to expand...
Click to collapse
No ideal, try it and see.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse

What would it take to interest @vampirefo in rooting this tablet and providing a nice clean ROM for the Ares 8A???

cjhudson101 said:
What would it take to interest @vampirefo in rooting this tablet and providing a nice clean ROM for the Ares 8A???
Click to expand...
Click to collapse
For me to root and provide TWRP recovery, I would need the tablet.
Sent from my Life Max using Tapatalk

vampirefo said:
For me to root and provide TWRP recovery, I would need the tablet.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
My bad, I guess I misunderstood one of your posts where you said you successfully rooted the tablet, but were withholding the method...
What if I sent you one?

cjhudson101 said:
My bad, I guess I misunderstood one of your posts where you said you successfully rooted the tablet, but were withholding the method...
What if I sent you one?
Click to expand...
Click to collapse
You didn't misread, I rooted my son's, he doesn't live near me, he is in college. He is using my laptop that I used, so all my source files are with him.
I need tablet to start over, I already know what to do but without tablet, I can't do it.
Sent from my Life Max using Tapatalk

Check your zip in the link, lets get vamp an 8a!
I just got one of these for $35, but now the closest walmart with it in stock is an hour away. Ill totaly send you one if I drive that way for any reason. Check your zip on brickseek ..... anyone?
slickdeals.net/f/10189248-nextbook-ares-8a-16gb-tablet-android-6-ymmv-35-bm?src=SiteSearchV2_SearchBarV2Algo1
it came with 6.0.1 on it