Tf700t Adb Tool V2
As of this post, it would appear that the S-OFF tool, Revolutionary, may not successfully flash clockworkmod recovery for everyone. And once it S-OFFs your HBOOT, it won't run again, so there's no way to get it to retry the recovery flashing.
The following is a guide on how to manually flash a recovery. May come in handy some day. Or you may want to wait for Revolutionary to address the issue. But if you're one of the people who has run Revolutionary and is without a recovery image, this is for you.For now, TeamWin has created a brand new recovery called TWRP, and it works great. You can download the image here:Or you can go with ClockworkMod recovery, which is what you would end up with if the recovery portion of Revolutionary succeeds:Choose which recovery you want to try, and save that image to your computer.There are two popular methods to flash a recovery.
The easiest way is known as the update.zip method. The other way, fastboot, is more technical and requires that your PC is set up with drivers and the and fastboot tool.Both methods require that you boot your phone into HBOOT.
If you are unsure how to do this, see this post:UPDATE.ZIP METHOD:This method can be used to flash to any partition, not just recovery. Essentially you place a file at the top (root) level directory of your SD card and HBOOT will automatically find the file and flash its contents. The filename needs to be named PG86IMG.ZIP for the Evo 3D, and it needs to contain the.img files named the same as the partition name.Most of the time, you don't need to worry about all this; the file you download will already be in the correct format. You just have to rename it to PG86IMG.ZIP. The link to TWRP recovery above is distributed in this update.zip format.
All you need to do is rename it and put it in the root of your SD card. Then boot into HBOOT. HBOOT will automatically scan for the file, and if it was named correctly, it will ask you if you want to flash what's in the file.
Say yes, and it will do it's thing. That's it.If you only have the.img file, you can make your own update.zip file. For example, if you have a recovery image file, it needs to be named recovery.img. Then, put it in a ZIP file without compression. Name the file PG86IMG.ZIP, and you're all set.FASTBOOT METHOD:This method requires a little more setup and is a bit more manual than the above update.zip method, but in my experience, having a computer set up to run fastboot and adb can come in handy, especially once you've graduated to an advanced power root user.
If you ever want to help in the effort to crack bootloaders, having fastboot working is a mustfastboot is a little executable tool that comes with the Android SDK. It is right alongside adb. If you have adb working, then fastboot is ready to go. Both adb and fastboot require that you have the HBOOT drivers installed for your phone.
You can get the drivers here:(go to the part, 'are any drivers required?' )Once the drivers are installed, you should get the Android SDK here:Just get the.zip file and extract it anywhere on your computer. Look for the /tools folder. In there, you'll see the fastboot executable.Ok, these instructions are for Windows users, but the equivalent steps should work for mac and linux:Open up a cmd window and go to your SDK tools folder. Fastbootand press enter. You should see a list of fastboot commands available.
If you don't get that, you're probably not in the right folder. Check your path and where you installed the SDK and make sure you are in the /tools folder.Once you've verified you can run fastboot, it's time to move the recovery image to the /tools folder (easier not to have to specify a path to the recovery file). I would also rename the recovery file to something short like recovery.img.Once the recovery image is in the same /tools folder as fastboot, you'll need to put your phone in fastboot USB mode. To do this:1) make sure the Fast Boot option is disabled. Note, this 'Fast Boot' has nothing to do with the fastboot executable I've been talking about.
This is a setting in Sense to allow the phone to boot up faster. To disable this setting, go to Settings Power Fast boot (uncheck the box).2) Hold down the power button and select Power Off from the menu. Wait 1 minute for the phone to completely power off.3) Boot into HBOOT.
See this post for detailed instructions on how to boot into HBOOT:4) Once you're in HBOOT, you'll see it scan for a few files. This is normal. When it is done, you can make selections in the menu. Vol-UP and Vol-DOWN allows you to move up and down the menu list.
POWER button acts as ENTER and selects whatever you're highlighted over.By default, FASTBOOT is selected. So just press power.5) now you should be in the FASTBOOT section of HBOOT. Plug the phone in via the USB cable to the computer where you installed the Android SDK. You should see the red FASTBOOT banner turn into FASTBOOT USB. If that doesn't happen, it means that your HBOOT drivers aren't working.Your phone is now ready to accept commands from the fastboot executable that came with the Android SDK. Go back to that cmd window where we tested the fastboot command earlier.
From there, issue the following command. Fastboot flash recovery recovery.imgHere's a quick explanation of the above command:fastboot: that's the executable toolflash: that's the function we want the fastboot tool to performrecovery: this is the name of the partition we want to flash into.
Since we are flashing a recovery image, it needs to go to the recovery partition.recovery.img: this is the name of the actual file to flash. Your filename may be different. Just make sure it matches the actual filename.Fastboot will flash the image and give you a success/failure notification. If successful, you're all set. To check out the new recovery image, verify that BOOTLOADER is selected in the HBOOT menu (should be highlighted in blue). Press POWER button to select it.
Now you should be back at the main HBOOT menu.Use VOL-DOWN to highlight RECOVERY and press POWER button. The phone will now attempt to boot into the new recovery image. You'll see the htc splash screen briefly and then the recovery image.
That's it!A note about ROM Manager:Some people have mentioned here and there that the easiest way to flash a recovery image is with the ROM Manager app, which is free on the Market. While this is true, I discourage people from using this app to flash their recovery IF they don't know how to use the two methods detailed above. Because there may come a day when you have a bad flash, or you did something that prevents your phone from booting into Android, and you can't run ROM Manager. If, in this situation, you needed to reflash your recovery, you'll need to do it the manual way.If you are proficient in the manual flash, then by all means, use ROM Manager to change out your recovery image. Just be sure that the image it recommends is the proper one for the Evo 3D. It seems possible to use an old version of ROM Manager and flash a recovery not intended for the Evo 3D, so be careful.
Tf700t Adb Tool V20
As always great post Novox77! I really would like to say thanks for all the nice work you put in around here. But, I'm writing this right now because Revolutionary failed to load clockworkmod recovery on my phone. I know its happening to a lot of people but I think tha it's kind of crappy that it works for some people and not for others. And it seems like my luck (i.e.
Bad luck) that it didn't work for me, as I am a noob! Anyways, after reading a few things I decided to try to use the Fastboot Method. I was unsuccessful with loading the fastboot drivers (followed complex instructions off XDA Dev. Because at the time I hadn't found your thread yet). Anyways after an unsuccessful attempt I moved onto trying the Update.zip Method of manually flashing a recovery image.
Unfortunately, at first it didn't work for me. I followed your instructions to perfection!When I load into my phones bootloader the recovery option is in green, however when I click on it, the phone shows a red triangle with an exclamation point.Supposedly this means that I don't have a recovery image successfully installed on the phone.Forgive me if this sounds like a stupid problem to have but I'm a noob, and believe me this is my first time rooting so I expect a little trial by fire.Atleast I have been reading and reading about rooting for the last 2 days! In regard to my last post, I have figured out the issue I was having and fixed it.I now have root access!Here is how I went about fixing the issue I was having:I read the original post above and then sought out a Youtube Video called 'TeamWin Recovery Installation Guide for HTC EVO 3D' and watched the video. Here is the link:In the video and in this orginal post it says to rename the TeamWin recovery file 'PG86IMG.zip' however, this did not work for me. Instead I had to rename it 'PG86IMG' (without the.zip extension). Then I dragged the file onto my SD Card and loaded up the bootloader.
Once on the bootloader menu it will ask if you want to update the TeamWin Recovery file, I clicked 'Yes' as stated in the video and then proceeded to reboot the phone. Once the phone was back on the home screen I erased the 'PG86IMG' from my SD Card and dragged the Superuser.zip file onto the SD card directory. Once finished I loaded into bootloader and clicked on Recovery and presto! I went in the recovery menu and able to load the.zip file that granted me root access!(Hope this helps someone, but just about 99% of this information was covered in this original post and in the Youtube video I linked. All of the credit goes to Novox77 and Youtube's willwhitworth.). For those of us using CWM!Last night I spent an hour trying to figure out why my phone wouldn't charge while powered off.ceabbott2 found and informed me that this is a bug in CWM 4.0.1.4 - checking the CWM website, I found they had a 4.0.1.5 image available there.Tired of dealing with this, I just grabbed the free version of Rom Manager from the Market.I went to the first option, install CWM - and then rebooted into recovery to see for myself what's up.4.0.1.5 was installed nicely and now when power is off, my phone recharges. Help.After installing revolutionary.exe, the recovery image was not loaded automatically.
I tried loading the image manually and that did not work. After rebooting I was getting error 16 when making a call. I restored to factory default and error 16 did not go away. Sprint was able to resolve the problem. I have attempted to load the recovery image using the zip file and copying on the root of the SD card and also tried using fastboot and flashing it from my PC and neither method works. Any ideas!!!!
Help.After installing revolutionary.exe, the recovery image was not loaded automatically. I tried loading the image manually and that did not work. After rebooting I was getting error 16 when making a call. I restored to factory default and error 16 did not go away. Sprint was able to resolve the problem.
I have attempted to load the recovery image using the zip file and copying on the root of the SD card and also tried using fastboot and flashing it from my PC and neither method works. Any ideas!!!! Click to expand.Here's what I did. I went to my sdk folder.
The fastboot option was located in android-sdk-windowstools folder. Then I opened up another folder window and went to android-sdk-windowsplatform-tools and copied the files AdbWinApi.dll and AdbWinUsbApi.dll. I then pasted those files in android-sdk-windowstools. You will also need to copy the clockwork.img file into this same folder(for simplicty). Now within that folder(android-sdk-windowstools hold down the shift button and right click. Select the option 'open command window.in the command window type - fastboot devices and hit enteryour device should be recognizednow type -flashboot flash recovery clockwork.img(this is whatever your file name is)you should get a response of OKAYIf you don't have sdk you can find it here.
Help.After installing revolutionary.exe, the recovery image was not loaded automatically. I tried loading the image manually and that did not work. After rebooting I was getting error 16 when making a call. I restored to factory default and error 16 did not go away.
Sprint was able to resolve the problem. I have attempted to load the recovery image using the zip file and copying on the root of the SD card and also tried using fastboot and flashing it from my PC and neither method works. Any ideas!!!! So I noticed that the TWRP NANDroid images have.win extension. I expected.img.
Does anyone know if they are using a proprietary format? Or if I can just rename it to.img?I suppose I'll be brave and rename it and try to flash it via fastboot and see what happensAnd regarding Windows hiding file extensions, they've been making that the default setting since Windows 95. So I have to assume that it's the best decision for most users of windows.Personally, I think it's rediculous to hide the extension. It's one of the first things I change in a fresh install of Windows, followed by showing all hidden files. So I am curious I am not a seasoned vet on roms and recoveries and how to do everything but I saw all the posts on how to put clockwork mod as a recovery on manually and wondered why it is not being written on doing it through ROM manager. All I had to do was select flash clockwork mod and it flashed and installed in about 10 seconds. Like I said I'm nowhere near as advanced as everyone on here so it may have been written already and I missed it or what I flashed is not an updated version or something.
Just thought maybe it was worth writing about.
The ASUS Transformer Infinity Pad TF700T is a great tablet. Well, at least until ASUS released the Android 4.2.1 update. That basically turned a great tablet into a piece of garbage. Well, not really garbage, but close enough. The biggest problem, at least for me, with the Infinity tablet ended up being lag. I basically abandoned the tablet because I couldn’t stand to use it. Performance was atrocious, and despite the Infinity’s superior specs, I actually preferred my Nexus 7 for most tasks.
Taking matters into my own handsFor my first few months, I actually believed that would satisfactorily resolve my issue. Unfortunately, factory reset didn’t work too well. Sure, I’d get by for a short time, usually 1-2 weeks, but I’d be back struggling with lag shortly thereafter. I got frustrated. So, I decided to set about to correcting the issue — since ASUS doesn’t care — and reclaiming my tablet.
I decided that I’d unlock my tablet and install a custom rom. In particular, I opted for the Crombi-KK ROM.Getting startedThe first thing you need to remember is that you’re voiding your warranty by even starting this process. That’s because your first step involves unlocking your tablet’s bootloader. I was okay with this solution for two reasons. First, my tablet is 2 years old, so repairs aren’t covered by the warranty. And second, I know ASUS isn’t going to fix the issue. Please read this entire post before trudging off on the installation.Once you’re okay with voiding your warranty, the first step is to unlock your bootloader.
ASUS provides a bootloader unlock tool that you can download directly to your tablet.Follow this link and select Android from the drop-down menu. Then expand Utilities, scroll down to find Version V8For Andorid 4.2. I selected the. It’s packaged as a.rar file, so use any of the (I used ) to get the file into an Android OS.apk file. You’ll install the new app onto your tablet.
Note, you should have the box next to Uknown sources checked (look under Menu Security) to allow installation. Open and run the sunlock tool once it’s installed. This should take a minute or two, so be patient. You’ll know it’s done, so just wait. Installing TWRPWith the tablet unlocked, you’re ready to install the custom ROM. I followed, though they’re a little confusing at times. Note that you don’t need to root your tablet to finish this project.If you haven’t installed a custom rom, do a quick search for custom rom installation, just to get a feel for what’s going on.From this point forward, you’ll use your desktop computer for the installation.The first step in the process is to download (in this case TWRP — Team Win Recovery Package) and — do this while you’re unlocking the tablet, it’ll save you some time.
Doing some TWRPingFor me, the most difficult part of this custom ROM installation was the TWRP step. Don’t get frustrated, because here’s what you need to know.Use this (Windows) program to quickly get ADB on your desktop. ADB is part of the Android software development package, but you only need this small portion. Save yourself some time, hassle, and frustration with ADB Setup. Be sure to install the file directly to your C: drive. If you’ve done this right, you should have a folder structure that looks like this:This will enable easy access in the very near future.Download (if you haven’t already) the TWRP file. It’s packaged as a.zip folder, so use Windows (or your desktop’s).zip unpacking program to extract the files to your desktop.
Open the folder and look for the boot.blob file.Rename this to twrp.blob (right click rename twrp). Note that you can leave this as boot.blob, just remember the name for later.Copy this file over to your ADB folder, which should now look like this:Now, you’re ready to run some fastboot magic and install the TWRP recovery. This is extremely easy, though the instructions don’t tell you how (they assume you already know how to get fastboot). FastbootingPlug in your tablet via USB and make sure your computer recognizes and installs the device drivers. If your computer doesn’t, this is a pain and you’ll need to go back to the.If you’re fortunate, Windows (or your system) will recognize your ASUS tablet, install the proper drivers, and you can reboot into fastboot mode to use ADB to flash your TWRP recovery program.Get started by opening the terminal on your desktop.
In Windows, use the Windows Key + R to open the run dialog. Type cmd in the box and click Enter.
Pinch hitter 2 passwords. This is an exciting baseball game where you have to complete various tasks to become a major league player.
You should see the command terminal (old DOS for you pre-Windows folks with a memory).Change directories to your ADB folder — this is why it’s nice to sit ADB in the C: drive.Now, shut down and restart your tablet while holding Power + Vol- (volume down). You should see a “funky” screen with 3 icons: RCK, an Android, and “WIPE DATA.” If you’re restarting, you didn’t hold down the proper buttons, so try again. This is the fastboot screen.Type the following fastboot commands on the line (no pictures because I already performed the step):fastboot -i 0x0B05 flash recovery twrp.blobWait about 10-15 seconds for the recovery to finish. The command prompt says something like “successful”.Reboot your tablet. Installing the custom ROMWith the tablet rebooted, it’s time to move your downloaded custom ROM file over. You can do this ahead of time and save the hassle of rebooting. It’s up to you.I like to use Windows Explorer to move the file.
Simply copy (or cut) and paste the cm-11.0-20140719-crombi-kk-tf700tsigned.zip file from your desktop to your tablet’s root drive (at least somewhere you’ll easily find it). Wait a few minutes for the transfer, then reboot your tablet back into fastboot (Power + Vol-).With fastboot loaded back, select the RCK icon — it should be flashing — and press Vol+ to select the option.You should load directly to the TWRP recovery module and see a series of 8 icons, beginning with “Install”.I prefer to wipe my devices before installing a custom ROM, so click Wipe Advanced Wipe and select the partitions (generally the first four for me). Wait for the wipe to complete and return to the home screen.Click Install and navigate to the location of the folder where you saved your Crombi file.
Advanced tip: If you see a “signed” in the zip file name ( bestromeversigned.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.You’re ready to install the custom ROM by answering the questions and following the steps. Crombi includes the Google apps files, so you don’t have to worry about installing those from a separate file. Complete the installation, restart your tablet, and you have a whole new device. A whole new worldCrombi is really helping me to establish a whole new relationship with my ASUS Transformer tablet. You won’t see vast improvement for about 15-30 minutes as the device “settles down.” Be patient.One of my biggest issues was the lag of the tablet.
That’s almost disappeared from the system.Admittedly, the ROM isn’t perfect, for instance, there are some quirks when I connect my keyboard, but overall, I’m loving the fact that I’ve reclaimed my tablet, and it’s usable.If you’re struggling to love your ASUS Transformer Infinity Pad, perhaps Crombi-kk can help you love again. Thanks for an excellent post. I encountered an issue with twrp – it could not see my rom zip file from the install button. Solution was updating to the latest release (2.8) instead of the 2.6 I had installed. This also resolved an issue with my windows drivers I wasn’t even aware of yet. Moral: always check to be sure you have the latest release. Here’s the link:.Also note the following from the TeamWin website that saved my bacon when trying to move my ROM file over:“Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows.
You can change the.zip to something else like.txt and then copy it to the root and rename the file back to.zip once it’s copied to the device. You can also copy the zip into any subfolder.”Thanks again. Jeff, a couple other things – The fastboot command should have the letter “i” not the number “1” as in the following:fastboot -i 0x0B05 flash recovery twrp.blogAlso, the XDA post at has another wonderful tutorial on this same topic with a couple of additional helpful tips and links. He also reminds the reader to create a backup/restore image in case things go south, which is good advice.Thanks again for a great article.
Tf700t Adb Tool V2 2
I’ve been looking for a solution to the terrible lag problem that plagued this otherwise fine tablet. One of the advantages of the Android/open source option is the abilitiy to take matters into your own hands when your manufacturer (that’s YOU, Asus!) lets you down. Hiya Jeff!Thanks for your posting above! This is awesome! Now my Asus Infinity TF700t is with its soul renewed!
🙂I had the serious lagging for ages until just recently I have decided to give it a factory reset. It begins with just Google-ing for ways to download or backup all Asus’s default apps like SuperNote, MyCould, MyNet, etc, even the Asus Task Manager and your website spotted my attention.You have made process/procedures or as you called it, ‘project’, so details and simple at the same time. Thank you again!