Related
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
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
I'm trying to root my Rogers One X running 4.1.1 using these instructions, howtorootandroid.org/2013/05/28/how-to-root-htc-one-x-step-by-step-tutorial/ (as a new user I'm restricted from posting actual links).
I've got everything completed to the point where it says to disconnect the USB cable and select Recovery from the HBoot menu. When I select that, the phone reboots to the home lock screen. The next step says to go to Backup and backup the system partition. Problem is, I don't know where they mean when they say go to Backup. The only Backup function I know of is in Settings and that just backs up the Google user account data. How does one backup the system partition? Is the phone supposed to reboot to the lock screen from the Recovery prompt? Or is something going awry in that step?
After that it says go to install and install the SuperSU.zip file. Using a file manager I can locate the apk for the Superuser app and it installs but when I open it I get a message saying "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" That last part seems obvious.
Thoughts appreciated on how to resolve.
Thanks.
Stop what you're doing, you're using a root process for the wrong device. That's for the quad core One X, if your phone is a Rogers phone then it is the dual core version. To be sure, go into your bootloader and tell us what it says there, only the top four or five lines. To get into the bootloader, simply power the phone on by holding the power button and the volume down button at the same time, keep holding until it boots into a white screen, that's your bootloader.
Sent from my Evita
Thanks. Don't need to go into bootloader, just checked the device hardware information and you're right, it's a dual core. Using the volume + power buttons won't go into bootloader. I can get there with the Hanson2000 utility. The items in the Fastboot USB menu are Bootloader, Reboot, Reboot Bootloader and Power Down.
Through the process I used last night, the bootloader is unlocked and I haven't bricked the phone.
What's the process to root a dual core version, then?
Another question. Since the bootloader is now unlocked, do I need to continue to finish rooting the phone? With the bootloader unlocked, I can install custom ROMs, right? That's, ultimately, the goal. I'm trying to be able to update to 4.2 or 4.3 which, I've been led to believe, will also enable full USB host functionality on the phone.
Thanks.
Essentially you've done the hard part now. All that is left to do is install a custom recovery, and then you'll be able to flash custom ROMs from within that recovery. The AIO kit only has the ability to install TWRP 2.5 I believe, and that version is riddled with faults. So below I'll outline how to install a stable version.
Download TWRP 2.6 from here. You'll need to flash it manually using fastboot. So once you've downloaded it, put it in the same directory that adb and fastboot reside in on your pc and connect your phone. Now you need to open a command prompt from within that directory (shift + right click opens the menu, then select open command prompt here). Enter the following command:
fastboot devices
This will make sure you're connected properly, hopefully it will return your device serial number. Now you want to enter the following commands:
fastboot flash recovery "filename.img"
(the exact recovery filename, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you'll have a custom recovery which you can enter by pressing the recovery option on your screen. Now it's time to select the ROM you want to try and download to your pc. Once you've done that, select mount from the recovery menu, then select mount usb storage. Your phone memory will now show up as a removable drive on your pc and your can copy a ROM across.
Before you flash a ROM, make a backup of your current setup, you can do this by entering the backup option from the main recovery menu. It's essential to backup the system partition in case something goes wrong in the future, you can easily restore it.
In terms of ROMs, only EVER download ROMs you find in our forum. Never download from a different device forum or from another site, that's a surefire way to brick your phone. Your two options are Android Development, where you'll find Sense based ROMs, and Original Android Development, which is where you'll find aosp ROMs.
Once you've copied a ROM to your phone, simply perform a full wipe in recovery (cache/dalvik cache/factory reset/system), do this by going to the wipe option, then advanced wipe. Just don't wipe sd card. Then you can select the install menu, and find the ROM on your sd card, and install it.
Your phone is s-on, so you'll need to perform one extra step. When you download the ROM, within the root folder of the zip file there is a file called "boot.img", you need to extract this and copy/paste into your adb/fastboot directory. After the install process has finished in recovery, go back to the main menu and select reboot, then select bootloader. When the phone reaches bootloader, make sure it's connected again and issue the following command:
fastboot flash boot boot.img
Now you can reboot your phone and enjoy the ROM. Please note, you will need to flash the boot.img from each ROM you want to install. Unless you decide to get s-off, which removes that need.
Sent from my Evita
Actually, AIO allows you to use the TWRP, ClockWorldMod or your own file. I downloaded the file you linked and WinZip says it's an invalid archive. Can I use CWM instead?
It is suggested that you use TWRP, other recoveries are known to have bugs. Don't worry about what WinZip says, just check the md5 and as long as it matches the md5 listed on the download page it's fine.
I'd also suggest doing it the manual way as you actually learn something during the process. The time will come when one day you need to do something manually, and it's better to have a little experience than have to learn at zero hour.
Sent from my Evita
---------- Post added at 11:55 PM ---------- Previous post was at 11:52 PM ----------
Don't get me wrong, AIO kits are convenient, but they're also a big part of the reason why people have absolutely no idea about what they're doing to their phones, or how to recover if something goes wrong.
Sent from my Evita
Problem is that WinZip shows no file when it opens the archive. Can't do anything with it.
I understand your point about doing it manually. I'm a photographer and an end user, not a programmer and don't do code well. I can likely manage getting the recovery installed but took a look at a couple of the custom ROM threads and have no idea what the people posting the threads are talking about insofar as some of the instructions. I just want to get the phone able to operate as a USB host.
It's not a zip file, that's why. You're not meant to be able to do anything with it on your pc. Check the md5 like I said and you'll know the file integrity is good. Then you just need to flash it as per previous instructions.
Sent from my Evita
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
What do you mean by usb host? In what kind of application?
Sent from my Evita
Sounds like he wants a rom with OTG support
Yeah that's what I was thinking.
Sent from my Evita
Yes, I do want a ROM with full OTG support. It's getting there that's the thing. Stock, it has USB storage capability and some devices (mouse/keyboard) but not broader for things like cameras.
I'm sorry for the problems. Remember I'm not a coder or a deep 'inside baseball' guy. When a file shows up on my computer as a zip file, I think I need to unzip it. I don't have the first flying flipping clue what md5 is, other than some sort of hash function, and have no idea how to check it.
It seems there are utilities to check it. Based on what the WinMD5 utility I downloaded tells me, it seems that the file is fine. I'll try to load it and see what happens.
EDIT: OK, I think I need to just do a factory reset and forget about it.
I downloaded ADB and fastboot, put it on my desktop. There are two nested folders inside the main folder. I put the recovery file into the Android folder which has the fastboot application. Opened a cmd window from within that folder and typed 'fastboot devices'. Nothing happened. It just came back to the same command prompt. The serial # wasn't returned. Nada.
EDIT II: I booted into bootloader manually and tried 'fastboot devices' again from the command prompt. It worked this time, returning the serial #. Next I tried to flash the recovery file and got the following message - "error: cannot load 'openrecovery-twrp-2.6.0.0-evita' : Unknown error. I decided to try the AIO kit and see what happened. Selected Your Own Recovery and started the process. The window opened to select the .img file and no file was showing that had that file extension. I think the problem is that the downloaded file is being seen by my computer as a zip file. Can I simply change the file extension to .img?
RFPhotog said:
Yes, I do want a ROM with full OTG support. It's getting there that's the thing. Stock, it has USB storage capability and some devices (mouse/keyboard) but not broader for things like cameras.
I'm sorry for the problems. Remember I'm not a coder or a deep 'inside baseball' guy. When a file shows up on my computer as a zip file, I think I need to unzip it. I don't have the first flying flipping clue what md5 is, other than some sort of hash function, and have no idea how to check it.
It seems there are utilities to check it. Based on what the WinMD5 utility I downloaded tells me, it seems that the file is fine. I'll try to load it and see what happens.
EDIT: OK, I think I need to just do a factory reset and forget about it.
I downloaded ADB and fastboot, put it on my desktop. There are two nested folders inside the main folder. I put the recovery file into the Android folder which has the fastboot application. Opened a cmd window from within that folder and typed 'fastboot devices'. Nothing happened. It just came back to the same command prompt. The serial # wasn't returned. Nada.
EDIT II: I booted into bootloader manually and tried 'fastboot devices' again from the command prompt. It worked this time, returning the serial #. Next I tried to flash the recovery file and got the following message - "error: cannot load 'openrecovery-twrp-2.6.0.0-evita' : Unknown error. I decided to try the AIO kit and see what happened. Selected Your Own Recovery and started the process. The window opened to select the .img file and no file was showing that had that file extension. I think the problem is that the downloaded file is being seen by my computer as a zip file. Can I simply change the file extension to .img?
Click to expand...
Click to collapse
That's a bit odd, it shouldn't download as a zip, it should be a file with the ".img" extension. Did you download it from the link I posted? Are you able to check the extension type in file properties?
Also I noticed you had a command return saying 'openrecovery-twrp-2.6.0.0-evita', did you make sure you put the ".img" extension on the end of your fastboot command?
Sent from my Evita
I did include the .img extension. Tried it again now and it worked. I must have made a type when I tried the first time.
So, I have a custom recovery process installed. Now, what ROM would you suggest?
By the way, I do appreciate the help.
I can't really suggest a ROM, as best/favorite ROM threads and questions aren't allowed on XDA. In this case I can probably point you in the right direction though.
The OTG side of things lies within the kernel though, not the ROM itself. The only kernel I can think of that has this support is the Rohan b6 Kernel, which you'll find here.
This means you'll only be able to use 4.1 based ROMs from this section though. The reason for this is because aosp kernels can only be used with aosp ROMs. If you try to use this kernel in conjunction with a sense based ROM, or an aosp ROM from a different android version (4.0, 4.2, 4.3) it won't work.
Keeping all that in mind, there are some great 4.1 aosp ROMs in that section. Development has moved into 4.2 and above but you'll still find the 4.1 ROMs there. Just make sure to look at the android version in the title and features of the ROM.
Flashing a custom kernel is an extra step in the install process too. Do the wipe in recovery like I described earlier, then install the ROM, then install the kernel. Instead of extracting the boot.img from the ROM zip, extract it from the kernel zip and use the same method I outlined before to flash it in fastboot.
Sent from my Evita
---------- Post added at 02:22 AM ---------- Previous post was at 02:22 AM ----------
Oh, and it's no problem at all, always willing to lend a hand.
Sent from my Evita
Well, we're getting there, I think.
I've got the file loaded onto the phone. The filename is rom.zip. I've done the wipe and then from the Install menu I selected the rom.zip file and swiped to start. Got an error message saying 'unable to open zip file'.
Tried a different ROM and it worked.
Which ROM did you end up going for?
Sent from my Evita
Started with Evervolv. That's the one that didn't work. Then went to Cyanogen. It's still booting for the first time so still hoping it all worked.
Did you flash the boot.img via fastboot afterwards?
Sent from my Evita
Yep. The one from the new kernel.
Did a wipe, advanced wipe, installed the ROM, installed GAAPS, installed the kernel, flashed the boot.img from the kernel zip file.
It's at the Cyanogen spinning wheel. My understanding is that it can take a while on the first boot?
If it sits here for much longer, I'll do it again, wipe and reinstall.
It can take a while, not normally longer than five minutes though.
Sent from my Evita
Last edit: Jan 2, 2018
The information here can be found in many places on the web and several forums. But when I started flashing custom ROMs about two years ago, I got frustrated many times because I found that information to be scattered, fragmented and in many cases outdated.
I hope this guide will make it a little easier for those users who wish to unleash the potential of this tablet but have no idea where to start. This is meant to be for inexperienced users who may be flashing for the first time.
If you find information I provide here to be incorrect or outdated, please do chime in!
And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames.
YOU DO THIS AT YOUR OWN RISK
First things first:
Backup everything on your tablet you care about to an external microSD or your PC. Don't worry about your apps. You can always install them from the Play Store.
This is just common sense. It is not inherently risky to flash custom ROMs. But something can wrong at any time and you have to be careful. If you are, this is a safe procedure.
Basically the process of flashing a custom ROM on the TF700 involves three steps:1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using said custom recoveryRooting is optional
To install a custom ROM it is not necessary to root the tablet. You do have to unlock the bootloader and install a custom recovery no matter what, but in my opinion rooting is an unnecessary step since any custom ROM you flash will be rooted anyway.
But if you want to root the TF700 on stock firmware there are three ways to go about it:
Up to firmware version 10.6.1.14.8 you could use a tool called Motochopper to root the TF700. Asus plugged the hole Motochopper exploited in the last firmware update.
For firmware version 10.6.1.14.10 there is Kingo Android Root (only works on Windows AFAIK).
And then there is Towelroot, a one-click-root exploit. It's an apk, so no PC necessary. Only Towelroot v1 works for the TF700 and it's hard to find. My dog ate the copy I had..
Unlocking the bootloader
Your tablet should be fully charged at this point!
Make sure "USB debugging" is checked in Settings > Developer Options (if you don't see it, go to About Tablet and tap 7 times on Build Number)
Download the Asus Unlock Tool v7 from here: https://www.androidfilehost.com/?fid=817550096634776735
On your tablet, in Settings > Security check "Unknown Sources"
Copy the .apk to your tablet.
Find the apk in your tablet's file browser, tap it and let it install
Open the app and follow the instructions. You will loose your warranty as soon as you click "I agree".
Update 2/15: Google added another wrinkle: It now checks even sideloaded apps and refuses to install them if they are considered not secure. The Unlock tool seems to fail their test. v8 does not install at all anymore. v7 will install if you allow "less secure apps" in your Google account settings. On the web - not your Google account on the tablet
July 2015: And another wrinkel... It seems to be pretty consistent now that the Unlock Tool hangs on the Google account password step. I suspect something changed on the Google side. It probably doesn't allow the tool to check/compare the password anymore. There have been quite a few security changes lately and the unlock tool never gets updated so I suspect that Google now is blocking access by the tool to it's servers.
The work-around is easy enough: Delete the Google account from the tablet (Settings > Accounts), then run the tool again. If that doesn't do it, do a factory reset from Settings, reboot and during the initial setup establish a WiFi connection but skip the google account setup, then run the tool
Click to expand...
Click to collapse
If you get an unspecified "network error" you could be in for some major headaches. Many tablet's serial number and/or the mac address of the mainboard seem to be registered incorrectly in Asus database. This problem is widely discussed on several forums, just google: "cannot unlock TF700" or similar and read the threads. Too many variables to discuss this here...
To check if you are unlocked, boot the tablet and read the tiny script. It should say:
The device is unlocked.
Installing a custom recovery on your tablet
To determine if you need to update your bootloader read post #3
I highly recommend you choose TWRP as your custom recovery. If you want CWM, you are on your own.
To push TWRP to your tablet you need to set up "Fastboot" between your tablet and your PC. Fastboot is a protocol that enables you low level access to your tablet.
Practice/Background
Power down your tablet and disconnect it from the dock
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in fastboot mode and you will see three icons (I assume again you are on a JB 4.2 bootloader. In older bootloaders you had 4 icons and had to select the USB icon to get into fastboot mode):
RCK - (which should be flashing) is your recovery (the stock recovery at this point, but once TWRP is installed this is one way to get into it)
Android - is your system, selecting it boots you back to into your ROM.
Wipe Data - stay away! Especially with custom software installed never, ever use this option!
To toggle between the three icons use Volume Down, to select one use Volume Up. Try it but do not push Volume Up when the 'Wipe data' icon is flashing!
Installing ADB and fastboot plus the necessary drivers
For a working ADB/fastboot connection from PC to tablet you need:
a) Asus device drivers – if you connect the tablet to your PC and it's recognized as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it to get the drivers, then uninstall the program from your PC if you don't want it. The drivers will stay.
b) Fastboot and ADB drivers which will be installed if you run the tool below.
Windows Vista, 7, 8, 10:
Download and run this cool little tool [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
The tool installs the adb and fastboot.exe to a folder on your C:\ drive (look for adb) and the corresponding drivers. Takes about 15 seconds.
On Windows 8.+ you need to turn off the driver verification feature. Here's a great video on how to do it:
https://www.youtube.com/watch?v=afrvSGiMAtk
Win XP (and all other Win versions if the above does not work for some reason)
I recommend the "ADB Install Tool" mentioned above or the 'Minimal ADB Fastboot Tool': [TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers
Either works fine.
If you need the drivers, get them here and install manually in Device Manager:[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync) - xda-developers
Win7 and Win8 users seem to have the best luck wth the drivers sbdags provided here: http://forum.xda-developers.com/showthread.php?t=2646279
It's fine if you want to use his Recovery Install Tool from that thread. But I highly recommend you familiarize yourself with basic fastboot commands! There are lots of tuturials all over the web.
Linux:Check out this site https://code.google.com/p/adb-fastboot-install/
iOS:[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) - xda-developers or:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
TROUBLE WITH ADB FASTBOOT DRIVERS? SALVATION IS NEAR!! (May 2017 edit)
And it is called FWUL (F-orget(?) Windows Use Linux) a great Arch Linux distro that you can boot off a USB stick or CD with simple adb fastboot all setup for you. Follow the instructions, set your boot sequence to boot from USB or SD drive first and disable Secure Boot in your BIOS Security settings. I have fought with Windows driver problems as long as I have been using Android devices and some stuff I never got to work. With this baby I was able to connect to 4 different Android devices with no problems at all. A beauty! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
The fun begins
Fastboot does not play well with USB 3.0, so use a USB 2.0 port for this. And no hubs and such....
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8/10: Inside that folder Shift + right click and select "Open command window here".
For Win XP click here
select 'Run' from the Start menu, type
Code:
cmd
and hit Enter. In the resulting command prompt type
Code:
cd C:\adb\ [I](or whatever the path to your fastboot folder is..)[/I]
If all of the above fails follow these instructions: https://www.michaelcrump.net/power-tip-for-windows-users-open-command-prompt-here/
In the command window on your PC type:
Code:
fastboot devices
If that command returns a string of numbers and letters, you are good as gold.
View attachment 3070087
If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot.
Getting the correct drivers working can be the hardest part of this exercise. If your computer does not "see" the tablet in fastboot, try to uninstall the existing driver (if any) in Device Manager and manually install the Google Universal Naked Drivers. And if Windows does not cooperate at all, PM me and I can hook you up with a Puppy Linux live CD with fastboot/adb set up already.
Let's assume everything is good:
On your computer go here: https://twrp.me/devices/asustransformerinfinityTF700T.html
Download the latest version of TWRP. Version 2.8.0 or later is ready for KitKat and Lollipop custom roms as well as backward compatible with JB ROMs.
FYI ONLY: If you for whatever reason want to format your data partition:
Formatting /data starting with TWRP 2.7.x and later takes a lot longer than in previous versions (up to 90 minutes). LET IT FINISH. DO NOT INTERRUPT THE FORMATTING.
Formatting data is only necessary in cases of data corruption.
Place the TWRP file into the same directory as your fastboot.exe.
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery <name-of-file>
This will flash the recovery to the recovery partition
Example:
If the file is named TWRP_2.8.6.2_TF700_recovery.img, the fastboot command is:
Code:
fastboot -i 0x0B05 flash recovery TWRP_2.8.6.2_TF700_recovery.img
You can rename the file to something easier to type, but file name and fastboot command have to match.
So if you renamed the file to twrp.img:
Code:
fastboot -i 0x0B05 flash recovery twrp.img
If your recovery comes as a blob:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
If it is successful type:
Code:
fastboot reboot
and let the tablet boot up normally.
Booting back into the (not rooted) stock rom you may get a dialog from TWRP asking you if you want to root.
You can accept or cancel it - doesn't matter. I assume you are going to install a custom rom and they are rooted anyway.
Create a nandroid
Your almost there! You are now on the stock ROM with a custom recovery installed.
Power the tablet down and boot into the bootloader menu with Volume Down and Power buttons.
With RCK flashing, push Volume Up and you should boot into TWRP. Familiarize yourself with the many options of the touch based interface without executing anything yet. TWRP is very user friendly. You basically cannot do anything of consequence "by accident", so don't be shy.
Touch "Backup", leave the default selection as they are and swipe the button to create a nandroid (a backup) of your current system.
This is a very healthy habit to develop: You always want to have a nandroid of your last working system squared away so that you can do a simple restore if you flash something that does not work, or something goes wrong during a flash. With a working recovery and a good nandroid you are minutes away from a working system if you soft brick your tablet.
Hint:
It's a good idea to have at least one good nandroid on external media. Sooner or later you will format your data partition and if you're like me, you may forget to backup your nandroids in the heat of the moment..
Installing a custom ROM
From here on out it's as easy as downloading the installation file of your custom ROM, booting into TWRP, choosing "Install" and navigating to the zip of the ROM you want to flash.
If you see a "signed" in the zip file name (best_rom_ever_signed.zip), make sure you check "verify zip signature" under the "Install" menu. Some devs sign their ROM zips - a better way to ensure file integrity than md5 sum.
Whatever you decide to flash: READ THE OP of the corresponding thread and make sure you have the correct bootloader and the required recovery installed! I can't stress this enough! If you are not sure, DO NOT FLASH!
Look for the ROMs in the Development section of the XDA forum for this tablet: Transformer TF700 Android Development - xda-developers or check out post #2. There's a description of the most popular roms for this tablet.
It is mandatory to do a Factory Wipe in TWRP before installing a custom ROM or going from one ROM base to another (a so called clean install).
If you choose 'Wipe' in TWRP, all you have to do is swipe the button - 'Factory Wipe' is the default selection under the 'Wipe' menu. You will loose your apps, but it will not wipe your /data/media/ folder where your files, pictures, etc live.
If you do this right before flashing the custom ROM, make sure you have the zip file of your custom ROM on your microSD - not on your internal SD where it may get wiped....
Once you installed a custom recovery NEVER EVER UNDER ANY CIRCUMSTANCES - AND I REPEAT: NEVER! - use the 'Wipe Data' option from the bootloader menu or the "Factory Reset" option in Settings > Backup&Restore.
In your custom recovery you have the option to wipe, backup and restore every partition on your tablet selectively or collectively. Any wiping, any backup and any restore of the system, data, recovery or boot partitions MUST be done in your recovery (or in fastboot)!
You can safely use Titanium Backup or Asus Backup for apps and settings, but that's it. For everything else use your recovery.
Hit the 'Thanks' button and rate the thread 5 stars if this helped you
ROMs for the TF700
Update June 2017:
Time moves on and this tablet is till alive....
Most of the roms below are ancient by now. One dev, the legendary timduru, is still working for this tablet and currently supporting Nougatella, Android 7.1.2 for this tablet.
Skip to here if you are thinking about a current rom: https://forum.xda-developers.com/showpost.php?p=72540013&postcount=346
Click to expand...
Click to collapse
KatKiss-KatshMallow by timduru (MM on the TF700 - who would have thought?) is still under intermittent but active development and it is a beauty. Multi-window support anyone?
http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
CROMi-X is based on the latest Asus firmware (JB 4.2.1) for this tablet with many, many tweaks and improvements, but since there have been no further Asus updates, development on this rom has stopped. This rom would give you the most Asus-like experience on this tablet.
http://forum.xda-developers.com/showthread.php?t=2425383
And here is the recent incarnation of this rom: CROMi-X Resurrected: http://forum.xda-developers.com/tra...pment/cromi-x-5-4-resurrected-tweaks-t3273515
@LetMeKnow still releases a new teak here and there, so keep following the thread.
Development on all of the following roms has stopped. The devs have moved on to other devices
CROMBi-KK is based on CM11 and tweaked for this tablet but a little buggy. The later LP based roms from the same team are definitely better.
http://forum.xda-developers.com/showthread.php?t=2672751
CyanogenMod is build from the ground up, CM10.x emulating JB 4.3, CM11 emulating KitKat (JB 4.4). CM was not build with a transformer (keyboard) in mind, but the dev has ironed out most of those bugs.
http://forum.xda-developers.com/showthread.php?t=1957660
ZOMBi-X: From the same team that developed CROMi-X and CROMBi-KK. Based on OMNI rom with multi-window support.
http://forum.xda-developers.com/transformer-tf700/development/rom-t2857931
ZOMBi-POP The (almost last) project from the CROMI/CROMBi/ZOMBi team. It's Omni based Lollipop for the TF700
http://forum.xda-developers.com/transformer-tf700/development/rom-t3006593
A note: This rom will run with data formatted to ext4, which is the OEM default. But it benefits from /data on F2FS, the new file system developed by Samsung, more than any other rom before it. Changing the file system for /data to F2FS has become very easy since the TWRP team build support for it into their recovery. I wrote a guide for converting your data partition to F2FS here:
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
That same team took one final stab at a 6.0 rom for this tablet: http://forum.xda-developers.com/showpost.php?p=65968239&postcount=3719
But I would call this definitely an unfinished product with a doubtful future.
CM12 I don't run CM roms - try it for yourself
http://forum.xda-developers.com/transformer-tf700/development/rom-cyanogenmod-12-0-t3006624
OmniROM by lj50036 who's on the ZOMBi team
http://forum.xda-developers.com/transformer-tf700/development/rom-omnirom-tf700t-t3056438
There are quite a few more variants, check them out in the XDA Development forum and don't forget to make a nandroid before flashing anything new
AND IF YOU LIKE YOUR NEW ROM, SHOW YOUR APPRECIATION AND DONATE TO THE DEVELOPER!
Alternative methods to install TWRP
Edit February 2015
In this section I originally explained how to flash TWRP to your device using apps like GooManager (currently not supported anyway), TWRP Manager or Flashify from the Play Store which do it right from your tablet. These apps "save you the trouble" of getting ADB and fastboot set up and working on your PC. These methods still exist and they do work sometimes (and if you have root), but I will not recommend or promote them any longer.
Why?
Because I'v read too many stories about these apps failing, even flashing to the wrong partition - you name it.
If you are not willing to invest the time to learn the basics about ADB and fastboot (google "adb fastboot xda tutorial") and install the necessary drivers on your PC, you should not be flashing anything to your tablet!
GET ADB AND FASTBOOT WORKING!
I have spent quite a few hours helping users who got themselves into a situation where the only thing they could access on their tablet was recovery, but they did not know anything about adb/fastboot and did not set it up when the tablet was still working. To get it to work with a soft bricked tablet is much, much harder!!
Sooner or later you will do something stupid (I have done it and so will you) and ADB/fastboot may save your bacon IF you had it working when you didn't really need it.
HOW TO UPDATE YOUR BOOTLOADER
The last official Asus firmware update to JB 4.2.1 brought us to the 10.6.1.14.10 bootloader - and it will be the last one we ever get since there will not be any Asus firmware updates anymore.
If you are on an older bootloader and want to run a KK or Lollipop ROM, you should update your bootloader to this version.
Determining which bootloader you currently have
From an "Off" state, boot the tablet with Volume Down and Power into the bootloader menu. Read the small script in the upper left. You'll see
US_epad-10.6.1.14.10-20130801" or similar.
US or WW, JP, CN is your SKU or region
10.6.1.14.10 is your bootloader version
20130801 is the build date (and immaterial in most cases).
Updating your bootloader
Still on stock with stock recovery:
Just OTA update to the last Asus firmware or flash it manually.
Custom ROM with custom recovery
Either:
1. Flash Asus stock firmware in your custom recovery
Download the official Asus firmware, unzip it once, flash that second zip in TWRP or CWM.
The distinct disadvantage of this method is that you will loose your custom ROM and your custom recovery and you will have to reflash them, but it works to get you onto the latest bootloader - or the latest stock rom if you desire to return to stockOr:
2. Flash only the bootloader in recovery
This is what I would recommend you do.
Go here for a collection of flashable bootloader/recovery packages: http://forum.xda-developers.com/transformer-tf700/general/firmware-10-6-14-10-twrp-t2867157
If all you need is the latest US bootloader, go to post #3.
The packages (bootloader + recovery) will replace not only your bootloader, but also your current recovery with whatever the TWRP version in the package is.To flash a KK or Lollipop ROM afterwards you need TWRP 2.8.+.
If you choose a bootloader package with an older recovery, you need to flash the latest TWRP version after you flashed the above bootloader package. In between you have to reboot (do not skip this step!)
sbdags said:
@moderator could we sticky this please.
Brilliant post Bernd
Click to expand...
Click to collapse
Damn -you beat me to post 3! LOL
But thanks - almost everything I know about Android I learned following your lead.
berndblb said:
Damn -you beat me to post 3! LOL
But thanks - almost everything I know about Android I learned following your lead.
Click to expand...
Click to collapse
Yes after I posted I wondered if I was jumping the gun.... Maybe a mod can sort it for you? Sorry!
Mod edit: I deleted your previous post to give the third post to OP. I will copy paste it here.
@stamatis could we sticky this please.
Brilliant post Bernd :good:
sbdags said:
Yes after I posted I wondered if I was jumping the gun.... Maybe a mod can sort it for you? Sorry!
Click to expand...
Click to collapse
No problem. You "jumping the gun" is an honor to me.
Thanks
Well written and very informative post. Thread stuck.
please help
Yes i am a total noob goober.:cyclops:.I want to unlock root and flash my tf700 ..I have watched plenty of youtube vids and read how to do it, enough to where i think i am comfortable. Well I downloaded the file from asus website to unlock the M8 and it wont open on the tablet. It says file not supported. So i tried to download it on my computer and transfer it over, well my computer cant install the drivers for my tablet..urgghh.. So I saw an older article saying it would work if we downloaded the M7 file, Well that downloaded and worked I was able to open and go through the prompts, I signed away and clicked ok.. Yet another error...Which I read might happen, but I tried 20 or so times and still nothing. Am i way over my head in this, It sounds so simple to do...Any help or am i a lost cause?
Thanks
blackc3 said:
Yes i am a total noob goober.:cyclops:.I want to unlock root and flash my tf700 ..I have watched plenty of youtube vids and read how to do it, enough to where i think i am comfortable. Well I downloaded the file from asus website to unlock the M8 and it wont open on the tablet. It says file not supported.
Click to expand...
Click to collapse
I think you mean v8, v7 for the Asus Unlock tool?
You have to extract it. On the tablet you can use the app ES File Explorer from the Play Store. It downloads as a .rar file, the result has to be an apk
So i tried to download it on my computer and transfer it over, well my computer cant install the drivers for my tablet..urgghh..
Click to expand...
Click to collapse
You have to get the drivers working - no excuses
Without working drivers you cannot push a recovery to your tablet. What Windows version do you have?
Try installing the Asus PC Sync Utility, try the Google Naked Drivers, try the ones attached to this post (note: I have not tested these myself) - you will have to find the correct combination for your PC yourself.
Here are a few links that may be helpful.
http://www.addictivetips.com/window...-or-device-drivers-manually-in-windows-vista/
http://forum.xda-developers.com/showthread.php?t=2670645&page=3
So I saw an older article saying it would work if we downloaded the M7 file, Well that downloaded and worked I was able to open and go through the prompts, I signed away and clicked ok.. Yet another error...Which I read might happen, but I tried 20 or so times and still nothing. Am i way over my head in this, It sounds so simple to do...Any help or am i a lost cause?
Thanks
Click to expand...
Click to collapse
No. You just got started!
Here are a couple of different approaches if you cannot unlock:
http://www.transformerforums.com/fo...discussion/42587-my-unlocking-experience.html
http://forum.xda-developers.com/showpost.php?p=51210808&postcount=6
Thanks for the guide,
everything went smooth until this step:
fastboot -i 0x05B0 flash recovery twrp.blob
Now my cmd just hangs there (been like 10 mins), not sure if i should restart tablet or cmd? Tablet still in fastboot screen. Thanks.
What do you get with this command:
fastboot devices
Sent from my K00C using Tapatalk
berndblb said:
What do you get with this command:
fastboot devices
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
It recognizing it correctly (atleast from what I understood from the guide). If it matters, I installed twrp 2.7 instead since it indicated 2.6.3.2+
I get:
015d2bbce9141e18 fastboot
Can I safely reboot/close cmd and try again?
Yes. Ctrl C will cancel the command, you should get the command prompt back.
Strange... twrp.blob is in the same folder as your fastboot.exe, right?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Wait! There's a typo in my post!!! LOL!
And you are the first one to notice it!
Try
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
OP updated
Sent from my ASUS Transformer Pad TF700T using Tapatalk
berndblb said:
Wait! There's a typo in my post!!! LOL!
And you are the first one to notice it!
Try
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
I tried that too initially seeing it in the cromi kk rom. However it didn't do anything either when I cancelled the first one that hanged.
But funny, I rebooted and tried again using your guide 0x05b0 and it worked. So I'm not sure what happened there. I used a lower case "b" this second time.. lol
Just downloading cromi kk now, thanks!
droijo said:
I tried that too initially seeing it in the cromi kk rom. However it didn't do anything either when I cancelled the first one that hanged.
But funny, I rebooted and tried again using your guide 0x05b0 and it worked. So I'm not sure what happened there. I used a lower case "b" this second time.. lol
Just downloading cromi kk now, thanks!
Click to expand...
Click to collapse
He, he, he - always wondered about that "-i 0x0B05" bit. I had this guide (including the typo) up on a different forum for months and quite a few people followed it successfully. I suspect
Code:
fastboot flash recovery twrp.blob
would work just as well.
Off to test it....
Edit: Yep - the above command just flashed TWRP 2.7 to my tablet without a hitch. So fastboot seems to totally ignore the -i 0x0B05 part (which is the Asus vendor ID).
Anybody know why every reputable website out there (e.g. TWRP, Androidroot) has it as part of the fastboot commands?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
berndblb said:
He, he, he - always wondered about that "-i 0x0B05" bit. I had this guide (including the typo) up on a different forum for months and quite a few people followed it successfully. I suspect
Code:
fastboot flash recovery twrp.blob
would work just as well.
Off to test it....
Edit: Yep - the above command just flashed TWRP 2.7 to my tablet without a hitch. So fastboot seems to totally ignore the -i 0x0B05 part (which is the Asus vendor ID).
Anybody know why every reputable website out there (e.g. TWRP, Androidroot) has it as part of the fastboot commands?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
A question for @_that as I always thought you needed the ID. Maybe not?
sbdags said:
A question for @_that as I always thought you needed the ID. Maybe not?
Click to expand...
Click to collapse
Apparently there was an older fastboot version that needed it. I've not used the ID for a long time.
It doesn't matter if you use 0x0B05 or 0xb05, it's the same number.
Great tut.
Thanks for posting. Good info, very concise.
berndblb said:
I hope this guide will make it a little easier for those users who wish to unleash the potential of this tablet but have no idea where to start. This is meant to be for inexperienced users who may be flashing for the first time.
If you find information I provide here to be incorrect or outdated, please do chime in!
And the standard disclaimer: I am not responsible if you misunderstand instructions I give here or if my instructions are dead wrong. I may be a fiend who's going for the world record in tablets bricked. Do your own research, read thrice, ask twice, flash once.
YOU DO THIS AT YOUR OWN RISK
First things first:
Backup everything on your tablet you care about to an external microSD or your PC. Don't worry about your apps. You can always install them from the Play Store.
Basically the process of flashing a custom ROM on the TF700 involves three steps:
1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using the custom recovery
Rooting is optional
To install a custom ROM it is not necessary to root the tablet. You do have to unlock the bootloader and install a custom recovery no matter what, but in my opinion rooting is an unnecessary step. However - as of today, Feb 27, 2014, another path to installing a custom recovery opened up (again) and that method (using GooManager to install TWRP - see below) requires you to be rooted.
So if you want to root the TF700 on stock firmware there are two ways to go about it:
Up to firmware version 10.6.1.14.8 you could use a tool called Motochopper to root the TF700. Asus plugged the hole Motochopper exploited in the last firmware update.
For firmware version 10.6.1.14.10 there is Kingo Android Root (only works on Windows AFAIK). There was some controversy around Kingo. Late last year their threads on XDA got closed because they used the vroot method which had a sniffer component that collected information and sent it to servers in China. The developers of Kingo removed vroot and worked it out with XDA. Their threads got re-opened in December. So I believe Kingo is safe to use - but you be the judge of that....
Unlocking the bootloader
Your tablet should be fully charged at this point!
Make sure "USB debugging" is checked in Settings > Developer Options (if you don't see it, go to About Tablet and tap 7 times on Build Number)
Go to Asus website: ASUSTeK Computer Inc. -Support-
Select your device, choose "Android" for OS and look for the "Utilities" on the resulting page.
Download the Asus Unlock Tool v8 (I assume you are on JB 4.2 firmware)
The tool downloads as a .rar file which is an archive you have to decompress. 7zip is a free and very good Windows tool that will do it for you or use ES File Explorer on the tablet
On your tablet, in Settings > Security check "Unknown Sources"
Copy the .apk you extracted from the .rar archive to your tablet.
Find the apk in your tablet's file browser, tap it and let it install
Open the app and follow the instructions. You will loose your warranty as soon as you click "I agree".
This can be a 5 Minute operation that goes without a hitch or a very frustrating experience with lots of error messages. There is no definite rhyme or reason for this. For some people it works like a charm, for others it works after 15, 25 or 55 attempts, for some never.... This problem is widely discussed on several forums. For now I assume it goes ok.
To check if you are unlocked, boot the tablet and read the tiny script. It should say: This device is unlocked.
Installing a custom recovery on your tablet
I highly recommend you choose TWRP as your custom recovery. If you want CWM, you are on your own.
To push TWRP to your tablet you need to set up "Fastboot" between your tablet and your PC. Fastboot is a protocol that enables you low level access to your tablet.
Practice/Background
Power down your tablet and disconnect it from the dock
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in fastboot mode and you will see three icons (I assume again you are on a JB 4.2 bootloader. In older bootloaders you had 4 icons and had to select the USB icon to get into fastboot mode):
RCK - (which should be flashing) is your recovery (the stock recovery at this point, but once TWRP is installed this is one way to get into it)
Android - is your system, selecting it boots you back to into your ROM.
Wipe Data - stay away! Especially with custom software installed never, ever use this option!
To toggle between the three icons use Volume Down, to select one use Volume Up.
Installing ADB and fastboot plus the necessary drivers
For a working ADB/fastboot connection from PC to tablet you need:
a) Asus device drivers – if you connect the tablet to your PC and it's recognized as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it
b) Fastboot and ADB drivers which will be installed if you run the tool below.
Windows 7/8:
Download and run this cool little tool [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
This is not confirmed to work on Win 8.1, but that may be due to the driver signature verification in Win8. Google how to turn it off.
The tool installs the adb and fastboot.exe to a folder on your C:\ drive (look for the adb folder) and the corresponding drivers. Takes about 15 seconds
Win XP (and all other Win versions if the above does not work for some reason)
I recommend the "ADB Install Tool" mentioned above or the 'Minimal ADB Fastboot Tool': [TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers
Either works fine.
If you need the drivers, get them here and install manually in Device Manager:[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync) - xda-developers
Linux and iOS: Check out this site https://code.google.com/p/adb-fastboot-install/ or this [GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) - xda-developers
The fun begins
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8: Shift + right click and select "Open command window here".
In Win XP select 'Run' from the Start menu, type
Code:
cmd
and hit Enter. In the resulting command prompt type
Code:
cd C:\adb\ [I](or whatever the path to your fastboot folder is..)[/I]
All Windows versions: In the command window on your PC type:
Code:
fastboot devices
If that command returns a string of numbers and letters, you are good as gold.
If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot.
Getting the correct drivers working can be the hardest part of this exercise. If your computer does not "see" the tablet in fastboot, try to uninstall the existing driver (if any) in Device Manager and manually install the Google Universal Naked Drivers.
Let's assume everything is good:
On your computer go here: Techerrata Downloads - Browsing tf700t
Download the correct TWRP version for the ROM you intend to flash (see list below)
Rename the file to twrp.blob and place it into the same directory as your fastboot.exe.
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
This will flash the recovery to the recovery partition
If it is successful type:
Code:
fastboot reboot
and let the tablet boot up normally.
Booting back into the (not rooted) stock ROM you may get a dialog from TWRP asking you if you want to root.
You can accept or cancel it - doesn't matter. I assume you are going to install a custom ROM and they are rooted anyway.
Alternative methods to installing TWRP
A) The app GooManager, free in the Play Store, downloads and installs TWRP (currently version 2.6.3.1) on the TF700. But GooManager requires root AND the bootloader to be unlocked. For users who are rooted already or those who cannot get ADB and fastboot to work on their PC, rooting with Motochopper or Kingo and then using GooManger to install TWRP may be a good alternative.
B) sbdags, the developer of CROMi-X (probably the most popular ROM for this tablet) provided a tool that automates the fastboot commands necessary to install a recovery..
I personally believe it is essential to have a working fastboot connection from PC to tablet and becoming familiar with basic fastboot commands when you develop a flashing habit, but if you want to take a shortcut his tool is here: http://forum.xda-developers.com/showthread.php?t=2646279
ROM – Recovery combinations
I assume you are on the 10.6.1.14.10 bootloader
CROMi-X – TWRP 2.6.1 or later http://forum.xda-developers.com/showthread.php?t=2425383
CROMBi-KK – TWRP 2.7.0 http://forum.xda-developers.com/showthread.php?t=2672751
NOTE: Formatting data in TWRP 2.7 takes a lot longer than in previous versions (up to 90 minutes). DO NOT INTERRUPT THE PROCESS if you format /data (usually only necessary with data corruption)
CM11 – CWM 6.0.4.6+ http://forum.xda-developers.com/showthread.php?t=1926286
Create a nandroid
Your almost there! You are now on the stock ROM with a custom recovery installed.
Power the tablet down and boot into the bootloader menu with Volume Down and Power buttons.
With RCK flashing, push Volume Up and you should boot into TWRP. Familiarize yourself with the many options of the touch based interface without executing anything yet.
Touch "Backup", leave the default selection as they are and swipe the button to create a nandroid (a backup) of your current system.
This is a very healthy habit to develop: You always want to have a nandroid of your last working system squared away so that you can do a simple restore if you flash something that does not work, or something goes wrong during a flash. With a working recovery and a good nandroid you are minutes away from a working system if you soft brick your tablet.
Installing a custom ROM
The most popular custom ROMs for the TF700 are CROMi-X, CROMBi-KK and CyanogenMod (CM).
CROMi-X is based on the latest Asus firmware (JB 4.2.1) for this tablet with many, many tweaks and improvements.
CROMBi-KK is a mix of CM11 and CROMi-X and at this point still in beta.
CM11 is build from the ground up, emulating KitKat (JB 4.4).
There are quite a few more variants, check them out in the XDA Development forum and don't forget to make a nandroid before flashing anything new
Note: Whatever you decide to flash: READ THE OP of the corresponding thread and make sure you have the correct bootloader and the required recovery installed! I can't stress this enough! If you are not sure, DO NOT FLASH!
Look for the ROMs in the Development section of the XDA forum for this tablet: Transformer TF700 Android Development - xda-developers
Note: It is recommended (mandatory if you go for CM) to do a Factory Wipe in TWRP before installing a custom ROM.
If you choose 'Wipe' in TWRP, all you have to do is swipe the button - 'Factory Wipe' is the default selection under the 'Wipe' menu. You will loose your apps, but it will not wipe your /data/media/ folder where your files, pictures, etc live.
If you do this right before flashing the custom ROM, make sure you have the zip file of your custom ROM on your microSD - not on your internal SD where it may get wiped....
From here on out it's as easy as downloading the installation file of your custom ROM, booting into recovery, choosing "Install" and navigating to the zip of the ROM you want to flash.
If you go for CROMi-X and TWRP as your recovery, make sure you check "verify zip signature" under the Install menu. sbdags signs his ROM zips - a better way to ensure file integrity than md5 sum.
For a general overview and comparison of ROMs check out Gtanner00's thread, post 2 + 3. Note that he describes roms for the TF300, but since the framework for the TF300 and TF700 is very similar there is usually an equivalent rom for the TF700 at the XDA Developers forum.
http://www.transformerforums.com/forum/showthread.php?t=41508
Do not follow or download from any of the links he provides! I only link to his thread for general information!
Any questions - please ask.
AND IF YOU LIKE THE ROM, SHOW YOUR APPRECIATION AND DONATE TO THE DEVELOPER!
Once you installed a custom recovery NEVER EVER UNDER ANY CIRCUMSTANCES use the 'Wipe Data' option from the bootloader menu or the "Factory Reset" option in Settings > Backup&Restore.
In your custom recovery you have the option to wipe, backup and restore every partition on your tablet selectively or collectively. Any wiping, any backup and any restore of the system, data, recovery or boot partitions MUST be done in your recovery (or in fastboot)!
You can safely use Titanium Backup or Asus Backup for apps and settings, but that's it. For everything else use your recovery.
Click to expand...
Click to collapse
droijo said:
I tried that too initially seeing it in the cromi kk rom. However it didn't do anything either when I cancelled the first one that hanged.
But funny, I rebooted and tried again using your guide 0x05b0 and it worked. So I'm not sure what happened there. I used a lower case "b" this second time.. lol
Just downloading cromi kk now, thanks!
Click to expand...
Click to collapse
Same thing happened to me. Fastboot recovery command did not return after over 10 minutes. I did Ctrl-C. Ran the command again and got the invalid argument error. Tried a couple times with same result. Unplugged and replugged USB cable (to same USB port). Ran the command again and it worked. When it worked, it took 11 seconds to flash recovery.
Also probably worth noting in the guide is that the Asus boot unlocker requires Google sign-in. If you have 2-step verification setup on your Google account, you need to use a one-time app password to sign-in.
Code:
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
^C
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
sending 'recovery' (6930 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
sending 'recovery' (6930 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
sending 'recovery' (6930 KB)...
OKAY [ 2.704s]
writing 'recovery'...
OKAY [ 8.026s]
finished. total time: 10.731s
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: