I have a problem with install the APX Driver. I use Windows 8 Pro and Windows 7 SP1 in VirtualBox and in both i can not install the APX Driver.
[How-To] All-In-One Guide For Asus Infinity (TF700) [25/03/2013]
- Thread starter Pretoriano80
- Start date
Experienced something like it with W7 64Bit
Connected tab to pc in apx mode, had an unknown usb device, used windoof device manager to manually search for driver, took the inf file from nvflash site and installed... still no good, but it worked after windoof reboot.
Very finicky stuff, fetching files then worked only when i put wheelie and nv# commands in a batch file and kept holding power and volume up keys through all of the process, was glad when i was through...
Sent on my behalf by my nuclear driven XPhone using CommonSense 3.14
---------- Post added at 08:24 PM ---------- Previous post was at 08:18 PM ----------
And as a precaution you might want to kill any services related to android first, if you have some suites installed. I.e. asus agents, samsung kies agents and the like...
Sent on my behalf by my nuclear driven XPhone using CommonSense 3.14
If you don't have root and now you're on JB, you can not root while you're running JB, you have to downgrade back to .30, do the root then upgrade back to JB. Second question: NO root will not void your warranty since you could remove root before return back for an exchange.
Hmmm, I had my tablet rooted on 9.4.5.30, but when I installed the JB update, I lost root. Will this happen every time, or do I need to root on ICS, temp unroot, install the JB update, and finally re-root (via SuperUser)?
Same thing happened to me. I am going to downgrade to .30 to get root back then like you say temp unroot and reinstall jb. I am hoping that works this time. I hate to not have root.
Downgrade (JB->ICS) firmware update not loading
I let my (new to me, but never rooted/unlocked by previous owner) TF700T take the Jelly Bean OTA before realizing I needed to be on ICS to get root access. I followed the Softbrick/Downgrade instructions but when the tablet gets into recovery mode, the mascot goes almost immediately from the loading animation to flat on its back with a red triangle on its chest.
I'm sure I have the correct firmware for my SKU, US .30, and I've uncompressed it and renamed the resulting .zip file correctly. It's on a FAT32 SD card and when I enter recovery mode, I get a "signature match" message. What am I missing?
I let my (new to me, but never rooted/unlocked by previous owner) TF700T take the Jelly Bean OTA before realizing I needed to be on ICS to get root access. I followed the Softbrick/Downgrade instructions but when the tablet gets into recovery mode, the mascot goes almost immediately from the loading animation to flat on its back with a red triangle on its chest.
I'm sure I have the correct firmware for my SKU, US .30, and I've uncompressed it and renamed the resulting .zip file correctly. It's on a FAT32 SD card and when I enter recovery mode, I get a "signature match" message. What am I missing?
I gave it a fresh re-format before starting, so this shouldn't be the issue. Every time I check the card's contents in File Manager I see only the ICS firmware .zip file, and LOST.DIR -- which I assume is being added every time the update fails and the tablet hard-reboots without ejecting the card properly (based on info from Droid Forums, which I can't link to because noob, but easily googlable). The directory is empty, so I've just been deleting it before each attempt.
Did mine this morning and worked like a charm. I am now back on JB and rooted, yea! Any luck for you?
I may have missed the right posts to be following - I am a little confused.
I did root the recommended method and also stayed locked as recommended before the OTA JB.
I took the OTA. Now I'm waiting for the JB unlock method and I see talk of downgrading to ICS without JB and unlocking?
I have tools from my HTC evo ROM rooting &flashing but this being a whole different animal these do not necessarily work with transformer tf700.
Don't I still have root?
I open Titanium and it says I don't have root. But is it compatible with tf700 anyway?
I open Busybox and it says I have root. But is it compatible with tf700 ? I am reluctant to install it until I see a roadmap for the tf700.
I open Rom Manager and it says I must install CM. But I read that there is no CM for tf700 yet?
I am under the impression that the ICS stuff wont work on the JB and we must wait for the dev's to cook up the JB recipes.
Or am I adrift in the bay . . .
I did root the recommended method and also stayed locked as recommended before the OTA JB.
I took the OTA. Now I'm waiting for the JB unlock method and I see talk of downgrading to ICS without JB and unlocking?
I have tools from my HTC evo ROM rooting &flashing but this being a whole different animal these do not necessarily work with transformer tf700.
Don't I still have root?
I open Titanium and it says I don't have root. But is it compatible with tf700 anyway?
I open Busybox and it says I have root. But is it compatible with tf700 ? I am reluctant to install it until I see a roadmap for the tf700.
I open Rom Manager and it says I must install CM. But I read that there is no CM for tf700 yet?
I am under the impression that the ICS stuff wont work on the JB and we must wait for the dev's to cook up the JB recipes.
Or am I adrift in the bay . . .
I did finally get the downgrade to ICS to work, after finding a post by xcal321 in the thread "WW .30 OTA failed...manual update?" (page 5) on this forum. (Sorry I can't link, too noob). xcal's advice: "There is no need to rename [the .zip file containing the update]. You also do not have to use an external SD card. Placing the file in the root of the internal SD card (/sdcard aka /mnt/sdcard) will work."
I downloaded a fresh version of the US .30 firmware, unzipped, moved the resulting zip file to the /sdcard directory of my internal storage, and entered recovery mode. Got the red triangle again. BUT! When it rebooted, the system recognized a firmware update was available and gave me a popup asking if I wanted to install it. Went through perfectly! So now I'm back on ICS, ready to try rooting through debugfs.
Don't have any idea why this worked, whether it would work reliably for others, or why the external sdcard + renaming method didn't work for me. But OP may want to add a note to the guide. What worked for me was way simpler than the method described there.
You are 100% correct. No rename needed after you download and extract from the zip. If you put on root of Ext SD card, you need to enter stock recovery mode to flash, if you put it in root of internal SD card, you just reboot and it will find and prompt you to upgrade..Simple as that!
FYI - Someone has confirmed in another thread that they *were* able to run the bootloader unlock tool under Jelly Bean - so it seems that there is no need to return to ICS in order to unlock the bootloader...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
I too can confirm that the UnLock tool on the ASUS website works on JB.
Now that I'm unlocked I have to find a way to ROOT. I have access to Fastboot and it works but I can't get the root tools to work. Has anyone been able to root, for the first time, after the JB update?
This is encouraging... I've rooted and unlocked my Galaxy Nexus and flashed it many dozens of times - so I'm comfortable with that. But it's clear that this device has different challenges, especially for those of us who didn't pay enough attention at the start and get NVFlash working before allowing the .30 update (like me). We're seeing 2 reports here that unlock tool seems to work with JB installed... without having use of NVFlash to fall back on, I think I'll probably wait for a bit more corroboration before I take a chance at unlocking my TF700T. I'm guessing that if rooting isn't cookbook yet, it will be soon (I know - I must do more reading in this subforum). So if this is all consistent, it sounds like we should be able to unlock and root, even with all updates applied up to date including JB. Only thing that would be missing is NVFlash if I understand correctly, meaning that we take a chance at bricking without necessarily having a working rescue tool at hand.
Curious: is this device more prone to bricking than, say, a Galaxy Nexus? I've flashed radio files, kernels, boot loaders and a few dozen ROMs to the GNex, and the most extreme "fix" ever needed was to boot into recovery, wipe data, cache and Dalvik cache, and flash a new kernel or ROM. Is that not the case with this device? As great as it would be to have a total recovery tool like NVFlash, is something like this more necessary on the TF700T than on the GNex?
Curious: is this device more prone to bricking than, say, a Galaxy Nexus? I've flashed radio files, kernels, boot loaders and a few dozen ROMs to the GNex, and the most extreme "fix" ever needed was to boot into recovery, wipe data, cache and Dalvik cache, and flash a new kernel or ROM. Is that not the case with this device? As great as it would be to have a total recovery tool like NVFlash, is something like this more necessary on the TF700T than on the GNex?
If your device is unlocked, it pretty simple to root while you're on JB.
http://forum.xda-developers.com/showpost.php?p=32293050&postcount=1
I downgraded to 9.4.5.30, rooted, backed up error via OTA root keeper, took the upgrade again, and restored root. Now rooted on JB.
Sent from my rooted BIONIC running ICS 6.7.247 (!) via Tapatalk 2
Sent from my rooted BIONIC running ICS 6.7.247 (!) via Tapatalk 2
Rootkeeper failure when SuperSU is installed
Root keeper failed to restore root for me twice after the latest firmware upgrade
The third time, I rolled back to 9.4.5.30, removed SuperSu and kept only Superuser, used the "temp unroot" option in Root keeper before upgrading back to 10.4.4.16 and this time Root keeper worked flawlessly
Root keeper failed to restore root for me twice after the latest firmware upgrade
The third time, I rolled back to 9.4.5.30, removed SuperSu and kept only Superuser, used the "temp unroot" option in Root keeper before upgrading back to 10.4.4.16 and this time Root keeper worked flawlessly
Last edited:
Ditto, had to temp unroot and use Superuser. SuperSu was a flop for me too. Removed.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone