Database Info

From leaked 3.1 US to 3.0 WW?? Possible?

Hi guys. Well lol.. noobs just shouldnt play. =)
I was on WW 8.2.3.13 and updated to US 3.1. Now im having some problems with it. Been freezing and stuff.
So.. is it possible in anyway to go back to ww version so i can get th OTA version when it comes?
Found a link with the WW firmware. Tried to use it and boot with volume down but it wont work.
http://forum.xda-developers.com/showthread.php?t=1090291

what i had to do was download the 8239 update from asus put it in microsd/asus/update then i hade to rename the file to ww_epad-user-8.4.4.5.zip. you should see update avaliable in the bottom right hand corner of the taskbar then select update. Then ur tf should do the rest itself.

Worked great! thanx =)

I tried this, it isnt offering me an update, no exclamation mark either

wilx said:
I tried this, it isnt offering me an update, no exclamation mark either
Click to expand...
Click to collapse
Did you put the file in microsd/asus/update (the removable sd card not internal)

baseballfanz said:
Did you put the file in microsd/asus/update (the removable sd card not internal)
Click to expand...
Click to collapse
yes I have put it there. Wont it need to be called us to fool it I can put it over the top? I need to return to WW stock rom. Will this unroot it and remove CWM too?

I am on PRIMORDIAL v3.1 btw

Hi guys!
Ok, place the zip file on microsd card. Then turn the transformer off.
Hold power and volume down until it boots up and you see the small text.
Now hurry and press volume upp right away. That seem to force it to start the firmware. I used the ww epad 8.2.3.13.
I dont know if its ok when your rooted tho..

wilx said:
yes I have put it there. Wont it need to be called us to fool it I can put it over the top? I need to return to WW stock rom. Will this unroot it and remove CWM too?
Click to expand...
Click to collapse
Look here for unroot infos
http://forum.xda-developers.com/showthread.php?t=1093403&highlight=unroot

baseballfanz said:
Look here for unroot infos
http://forum.xda-developers.com/showthread.php?t=1093403&highlight=unroot
Click to expand...
Click to collapse
Does anyone have the blob from the leaked 3.1, as the file has been pulled off the forums
thanks

Hello,
It doesn't work for me, is there any other thing to do ?
What i've done :
1) Make a folder called ASUS/Update from the root of your microSD card
2) Drop the .zip in there, rename to 'US_epad-user-8.4.4.5.zip'
3) If you're doing this on the Transformer itself, eject and remount the SD card. If on your PC, just plug the card in.
4) Click the update notification, it'll start the updater on it's own.
Got the notification, started it but got the warning when reboot itself in recovery, no update.

Discusbass said:
Hi guys!
Ok, place the zip file on microsd card. Then turn the transformer off.
Hold power and volume down until it boots up and you see the small text.
Now hurry and press volume upp right away. That seem to force it to start the firmware. I used the ww epad 8.2.3.13.
I dont know if its ok when your rooted tho..
Click to expand...
Click to collapse
To quote meself. Try the above. I used 8.2.3.13 tho.

Do I have to rename it or anything else ?

Hi, i didnt do that. Just booted with power and volume down. Then as soon as the small text appear on left side i pressed volume up. That way it flashes it right away.

Ok, someone on a french forum find the solution that worked for me !
Download the last WW update on the Asus Website
Open the .zip file, in the ASUS/Update folder there will be another .zip file
Rename it EP101_SDUPDATE.zip and put it to the root of your external microSDcard
Boot in recovery (volume down and power) and then press volume up when it's asked in the upper left corner.
Let the update apply.
Once it boot, power off your tab, boot again in recovery, wait to have the wipe menu, confirme to wipe your device, let it wipe and reboot and that's ok !

gniouki said:
Ok, someone on a french forum find the solution that worked for me !
Download the last WW update on the Asus Website
Open the .zip file, in the ASUS/Update folder there will be another .zip file
Rename it EP101_SDUPDATE.zip and put it to the root of your external microSDcard
Boot in recovery (volume down and power) and then press volume up when it's asked in the upper left corner.
Let the update apply.
Once it boot, power off your tab, boot again in recovery, wait to have the wipe menu, confirme to wipe your device, let it wipe and reboot and that's ok !
Click to expand...
Click to collapse
Sounds like you were using the wrong .zip file to begin with. There were a few going around. One was a zip with a zip in it, which you need to do what you did, another simply was that inner zip file. If you named the inner zip to US_epad-user-8.4.4.5.zip and followed the directions as posted previously it probably would've worked as well. Just looks like you had one copy of the zip and the instructions for the other

Was on TW_epad_user_8239 and updated to the leak 3.1 with US firmware.
managed to downgrade (all the way back to TW_epad_user_82313) and TF auto prompt me upgrade to TW_epad_user_8239 (with numerous reset)
However, there are many android.process* crashes...
*acore
*media
*gmail...
Still no OTA for 3.1 update

You have to wipe

gniouki said:
You have to wipe
Click to expand...
Click to collapse
??factory reset ??

silly me..just do the vol down again...thanks

[GT-P6210][CWMRecovery][ROOT] ClockworkMod Recovery and Root (07-Jan-2012)

**** USE AT YOUR OWN RISK ****
The following is posted so that I may share what I've done. It was done by me and for me. If you use it for you, then you take responsibility for whatever happens. This could, potentially, cause problems. It certainly will void your warranty (though it's pretty easy to undo this with no obvious signs.)
Install ClockworkMod Recovery and roots your P6210 tablet.
DO NOT ATTEMPT TO RESTORE ANY CWM BACKUP MADE WITH ANY OTHER VERSION/REVISION. IT WILL BREAK THINGS. THIS VERSION IS NOT BACKWARDS COMPATIBLE. JUST START WITH FRESH BACKUPS AND BE HAPPY.
WHAT THIS DOES:
Installed from recovery, this .zip will first ensure that it's running on the Samsung GT-P6210. If you have a different model, don't waste your time downloading it. It won't work. I have a P6210 to test with. I don't have any other 7 plus tab, so I can't test any other 7 plus tab, and therefore won't even act like it might work. If you want to try it anyway, you should have the knowledge to repair whatever you break - in which case you'll also have the knowledge to unpack this zip file and do things the manual way.
(starting with 20111210, a backup of the recovery is no longer made. I feel this is no longer needed as there is a confirmed working ODIN package people can use to restore their tablets with.)
Next, a new version of the clockwork mod recovery is installed.
(starting with 20111210, old backups are no longer purged. If you are upgrading from my original CWM recovery (previous to Dec 9th), please manually delete old clockwork recovery backups, as they are NOT VALID and will destroy your normal boot operation if you attempt to restore with a proper/current version of this recovery.)
Finally, the tab will be rooted. This only involves copying a tiny file (called 'su') to the system. In order for most android apps to make use of that, however, another application must be first installed. (See "Finishing SuperUser installation" below.) I considered putting that "SuperUser" application as part of this package, but it's really very easy to get it from the market.
INSTRUCTIONS:
Put the installation zip file on your tablet's external SD card. If you don't have an external SD card, you won't be able to install this. MicroSD cards are cheap. If you have a tablet that costs 399 USD, you can afford to spend a few extra dollars/euros/pesos/whatever on a microSD card. Just get one. Not only is it required for installing this from the factory recovery, but it makes a great place to back things up to. A nice 16GB card is suggested. 32GB is better. You'll need AT LEAST 1GB for this recovery. If you have a previous version of CWM already in-place, you won't need the storage card.
You can download the .zip file directly to your tablet and then possibly use the built in "My files" applet to move it to extStorages/SdCard, or you could download it to your computer and use "adb" to push the file to /mnt/sdcard/extStorages/SdCard, or you should be able to get it there with "Kies." If you have the proper adapter, you could also attach the microSD card directly to your computer and just copy it there. It doesn't matter HOW you get it on the card, as long as it's on the card.
After the zip file is on your microSD card, and the microSD card is inside (and recognized by) your tablet, then you need to...
Boot into recovery mode.
If the recovery version banner is "CWM-based Recovery v5.x.x.x", then you already have a version of CWM installed and should skip ahead to the proper section. If the banner is "Android system recovery (3e)", then you have the factory recovery and should continue with...
Installing from factory (3e) recovery:
Use the volume up/down buttons to move the highlight up and down, and the power button to select the highlighted option.
1. Select "apply update from external storage"
2. Select the file you placed on your storage card (starts with "p6210_CWMR".)
3. Sit back and watch it run. Read the information that is being sent to the screen. If there's an error, it'll display some message. If it works, it'll display a message starting with the word "Done!"
4. Select "reboot system now."
You now have a CWM-based recovery installed, and your tablet is rooted.
Please skip ahead to "Finishing SuperUser installation"
---------------------------------------------
Installing from CWM-based Recovery
Use the volume up/down buttons to move the highlight up and down, and the power button to select the highlighted option.
1. Select "Install zip from sdcard"
2. Select "choose zip from internal sdcard" (which will actually point to the external card.) (If you are upgrading and chose not to put the .zip on the external microSD card, you might need to select "choose zip from sdcard" instead.)
3. Select the file you placed on your storage card (starts with "p6210_CWMR".)
4. Select "Yes - Install (whatever filename you selected)"
5. Sit back and watch it run. Read the information that is being sent to the screen. If there's an error, it'll display some message. If it works, it'll display a message starting with the word "Done!"
6. Select "+++++ Go Back +++++"
7. Select "reboot system now."
---------------------------------------------
Finishing SuperUser installation
Install the SuperUser application directly from the android market:
https://market.android.com/details?id=com.noshufou.android.su
....
Post-installation Notes and Issues
It's a known issue with the version of CWM used in this recovery that the "internal sdcard" actually references the built in storage on the tablet. So, if you want to back up to your microSD card, choose "backup to internal sdcard". I'm retaining this issue to stay "compatible" with other CWM recoveries of the same version number. (won't fix)
The .zip package displays an incorrect version identifier/date when version 20111209 is being installed. (It's shows a banner with the date of 06-Dec) (cosmetic)
This recovery is NOT compatible with firmware updates via Kies (and perhaps not via other samsung official methods.) In order to perform a firmware update, I suggest the following procedure: First, perform a CWM Recovery backup, then use the ODIN package found elsewhere to restore this tablet to a factory state. Let Kies upgrade the tablet to whatever version it wants (give it a few tries in case multiple upgrades are needed.) Then re-install this recovery, and perform an "advanced restore" (or "advanced restore from internal sdcard if you made the backup using the similar option.) From there, restore "data." That will leave the entire firmware update in place. (boot is the normal boot kernel; system is what people like to call a ROM here, but is the samsung pre-installed apps; and data contains the applications you install and all your data.) Then "go back", wipe the cache partition, advanced, and wipe the dalvik partition. HOWEVER, please note that I have no way to know if any given samsung firmware update is "compatible" with this restore unless I've tried it myself. It's compatible with everything released up to the date of this note (10-Dec-2011), but I can't predict the future.
Donation?
I don't take donations. If you have spare money (I don't), please donate it to the Salvation Army, Red Cross, or just find a homeless person on the street and give them something. My favorite charity is the Shriner's Hospital for Children. (yes, I am.) If you'd like to thank me, there's a button at the bottom of this post dedicated to that. If you don't want to thank me, that's okay too.
Changes for 20120107:
Brought the recovery kernel up to date with the normal boot kernel. The only impact should be that if you keep crashing any time you boot normally (and before you are able to perform any action), you can now boot into recovery to _hopefully_ be able to retrieve the /proc/last_kmsg as a diagnostic tool.
Reduced the size of the .zip quite a bit.
Changes for 20111210:
* A backup of the existing recovery image is no longer being made. I feel this is no longer needed, as an ODIN package is now confirmed to be working that people can use to restore their tablets to a factory state.
* Old clockworkmod recovery backups are no longer being deleted when installing this. If you are installing this or newer from my CWM recovery previous to Dec 9th, 2011, please manually delete all those old backups. If you attempt to restore them, please be prepared to download ODIN and a factory ODIN image, as you'll need it in order to get your tablet working again. You've been warned...
* The issue that was causing backups to the tablet's built-in storage to fail has been corrected.
Changes for 20111209:
* Issues with getting into recovery are resolved.
* a backup of the recovery is only made if there is no sign of a previous version of this same recovery in place
Credits
Most obviously, Koush for his wonderful clockworkmod recovery. It's the basis of this entire project. Entropy512 for pointing me in the proper direction on a couple of things, pershoot mods to CWM for the Galaxy Tab 10.1 that I ported over to this one (due to the different partition structure of honeycomb devices.)
Links are below...
Take care
Gary

thanks gary, how might we be able to tell if this will be kosher with 3g version? do we need to --dump all pit via heimdall to ensure all partitions match up,etc? Thank you for your speedy work.

chrisrotolo said:
thanks gary, how might we be able to tell if this will be kosher with 3g version? do we need to --dump all pit via heimdall to ensure all partitions match up,etc? Thank you for your speedy work.
Click to expand...
Click to collapse
It's not kosher at all. I didn't wash my hands before compiling it, and had bacon bits on my salad for lunch. Sorry.

Thanks Gary. I have been watching your progress for about a week and you are like a put-bull. Amazing. u da man!!!

Pit bulls would be shamed as wussies. Many great devs possibly have a touch of Asperger's syndrome (with MUCH better socialization skills!) which, with tasks like this, is a benefit! At the very least just plain tenacious! lol
Thanks Gary. I've learned a lot just following along reading the discourse between you and others like Entropy. Appreciate it.

garyd9 said:
It's not kosher at all. I didn't wash my hands before compiling it, and had bacon bits on my salad for lunch. Sorry.
Click to expand...
Click to collapse
ahhh , close enough. anyways what could we do to find out without actually flashing this to possible incorrect partition??

chrisrotolo said:
ahhh , close enough. anyways what could we do to find out without actually flashing this to possible incorrect partition??
Click to expand...
Click to collapse
Which "3g" model do you have? The tmobile one or the international one?
I'm trying to narrow down which is the GT-P6200 and which is the SGH-T869!
I'm working with someone via PM and email to get the information needed for the SGH-T869, and I think it'll be pretty easy to get a recovery together for it, but other people will have to test and validate. I think this is the tmobile version...

international p6200

Soft Brick(kinda Sorta - well not really). Using defult 3e recovery. Tab would boot up, but would not go into recovery at all. Nada Nada. Thought it might have been some leftovers from other stuff I have been trying, so I odin3'd the factory image, did a wipe all and tried it again. Same difference. The only thing I could really think of was maybe I had a corrupted download.
funny thing is that it would boot up into the OS. Just not into recovery. will keep trying as I really want a way to make nandroid backups.

otamctech said:
Tab would boot up, but would not go into recovery at all.
Click to expand...
Click to collapse
No need to ODIN... that's why the package creates that backup recovery image. However, you said it's booting normally, correct? If so, it's not broken or bricked (and I experience the exact same thing.)
For some odd reason (that I haven't been able to figure out), after I flash a non-stock recovery, its very difficult to get the tab into recovery mode. Some times I get it instantly, and some times I have to try several times in a row. Are you using adb? If so, it might be easier. Power off the tab, plug it into your computer, and eventually the tab goes into a "low power mode" where you see the battery gauge but nothing else. From there (again, assuming you have adb installed/working), you can just run "adb reboot recovery" That usually gets me into recovery. 90% of the time.
If not, just try again. If you see the samsung animation starting, press/hold the power button to turn it off again, then press/hold volume up again... etc. It's a PITA, and a major annoyance of mine.
Two things about it make it REALLY annoying for me. First, I'm using samsung's own kernel for this... but I'm just repacking the initramfs portion of it. Second, if you put the factory recovery back, it's easy to get into recovery again.

chrisrotolo said:
international p6200
Click to expand...
Click to collapse
I'll get to that one eventually. I'm commited to do the tmobile one next, and I REALLY need to concentrate on my full-time job (the one that pays me a salary) which only leaves me a couple hours each day.
take care
Gary

absoultely, take your time. Is there a certain battery percentage requirement to get into either stock or CWM recovery say 50% or 60% minimum? we had this issue on dell streak 7. Let me know if I can help with partition layout or anything for p6200. thanks.

chrisrotolo said:
absoultely, take your time. Is there a certain battery percentage requirement to get into either stock or CWM recovery say 50% or 60% minimum? we had this issue on dell streak 7. Let me know if I can help with partition layout or anything for p6200. thanks.
Click to expand...
Click to collapse
No hard requirement I'm sure - but flashing at below 50% is just a stupid reckless risk, plain and simple as that.

If you are having issues getting into recovery after flashing this...
Here's a procedure I've come up with that has allowed me to get into this recovery 9 out of 10 attempts (and it doesn't require any special connections to a computer.) Please read all the steps before starting so you're prepared for what comes next. It'd really be annoying to have recovery finally pop up, but you weren't paying attention so the tablet turned off.
power off the tablet
Throughout this entire process the volume UP switch should be held and not released. This is the side of the volume switch closest to the power button. Once you see your recovery screen, you can release the volume switch (and any other button you might be holding at that time.)
Press/hold Volume Up (constant)
Press the power button, hold it down for 2-3 seconds, and release it.
You'll see the Samsung logo screen for a few seconds...
Instead of the expected recovery screen, you might see the samsung boot animation with music. If so, immediately (without releasing volume up), press and hold (and keep holding) the power button. Don't let it go this time.
The tablet will appear to power off after holding the power button for a few seconds, and then will power back on a second or two later.
(you're still holding that power button, right? how about volume up? Good.) Again, you'll see the samsung logo screen for a few seconds...
Instead of the boot animation, recovery should pop up this time. Release the power button as soon as it does or you'll just turn the tab back off again. You should also release the volume UP at this point.
(If you've flashed my recovery, please try this. If it doesn't work, please take the effort to reply to this post so I can know what people other than myself are experiencing.)
Take care
Gary

updated OP with:
Post-installation Notes and Issues
I'm aware that after flashing this, it is difficult to get back into recovery. I'm not sure WHY, but it's fairly consistantly a pain in the rear. However, I have found that following the steps in the following post seems to work (at least for me) 9 out of 10 times. (I was distracted on the 10th try, so not sure if it worked or not): http://forum.xda-developers.com/show...6&postcount=14
Remember above I mentioned that when this package installs, it creates a backup of the old recovery? Well, it does that no matter what recovery was in place. So, if you install this package with a factory recovery, that backup will be of the factory recovery (which is probably what you want.) If you install this package a second time when you already have the CWM Recovery installed, you'll overwrite that factory recovery backup with a backup of the CWM recovery (which makes no sense.) I'd strongly suggest that after you FIRST install this package, you make a copy of that backup recovery image file (and full filename is displayed when it's created), and stick that copy someplace safe. Perhaps just rename it and copy it to your SDcard or computer. A good name might be "p6210_factory_recovery.img"

The Tab 10.1 could be difficult to get into recovery too.
Usually, the following works for me:
Press and hold VolUp
Press and hold Power until the screen turns on (this is slightly different from your instructions)
Release Power but keep holding VolUp until Recovery shows

__________________

somebody9 said:
I was wondering if anyone knows what needs to be deleted in order to get rid of that pesky pop up menu you get by pressing on the Chevron/Arrow in the middle of the bar.
Click to expand...
Click to collapse
Please start a new thread for a new topic. Try to keep this one isolated to the CWM recovery.

garyd9 said:
Please start a new thread for a new topic. Try to keep this one isolated to the CWM recovery.
Click to expand...
Click to collapse
Sorry about that. Post removed.

Garys method of booting into recovery works fine. I'm just going to post it in linear format.
1. Press the power button and select Power Off
2. Press the volume up button (closest to power button) and do not release until the recovery screen is displayed
3. Press (do not hold) the power button
4. The static Galaxy 7.0 Tab Plus screen will display (possibly twice)
5. When the animated Samsung screen displays, press and hold the power button
6. The static Galaxy 7.0 Tab Plus screen will display
7. Release all buttons when the recovery screen displays.
This works every time for me

Updating firmware without touchable screen

Hello!
I've bought Transformer and after about 3 weeks touch screen stopped to work. I've tried discharging device, resetting and hard resetting but nothing. So I've written to ASUS service and a nice guy told me to update a firmware from ASUS website. OK. I've downloaded, as he told me so, WW firmware and now how can I put it into device without loosing my guarantee?
Btw. I have B90, so nvflash doesn't work.
Any ideas?

I'm a brand new owner of the TF101, but as I understand it, you should be able to update by doing the following (It has not worked for me, but I was able to install 8.6.5.13 the normal way, which requires a working screen, and I belive the updates I'm trying to install are broken.)
Take the zip file you downloaded from the support site. Inside it will be an "ASUS" folder, inside which there will be a folder named update "update", inside of which there will be a zip file.
Take that zip file, and rename it "EP101_SDUPDATE.zip", and place it in the root folder of your micro-sd card (not the sdcard folder).
With the micro-sd card in the system, power it completely off. Then hold down and power until you see a message on the screen, at which point you must press the up button withing 5 seconds.
In theory that should start the update. In the worst case it will stop after a few seconds and show a caution sign, indicating that it failed.
Hope that works for you.

Thanks a lot! I did the update, but unfortunately screen still doesn't respond :-\
I hope I can still give it to ASUS service with guarantee ;-)

ROM Manager has killer my TF101!

Righto. Before we go any further, jsut to say I am a relatively experienced rooter of Android handsets. Not tabs, granted, but handsets. Last night I rooted my TF and flashed Megatron and recommended kernel, no problem. I've had no problem taking nandroid backups or restoring as I've done that several times today, all with expected results.
Then I opened ROM Manager and allowed the app to update, I guess updating CWM too.
I then fiddled with SetCPU overclocking the CPU. This caused the tab to stutter a bit. Then freeze. Anyway, I hard rebooted and went into recovery to try and flash the backup I took about an hour ago. Now, CWM looks different (I guess this is where ROM Manager updated). I flashed the backup which seemed to go ok, but then when the TF rebooted I got an Android message saying that encryption hadn't worked properly, and that I would need to do a full (factory) reset. I hit ok and let it do it's think. The TF rebooted, but went direct into Recovery.
I tried wiping everything using Factory Reset, and wiping Dalvik, etc, but every time I tried I got a message saying "E: Can't mount /sdcard/" and then it reverted back to the main menu structure. Even when I choose "Install zip from sdcard" > "choose zip from sdcard" I just get a message up saying "E: Can't mount /sdcard/" and that's all she wrote. I think a) ROM Manager may have caused this and b) it's royally wrecked.
I did find teh following in a TF guide regarding cold booting:
-Quote-
11. Now do a Cold Boot (aka Hard Reset). This cleans system caches, but does not delete any user data.
Unplug the power cord and shut the unit off. Press and hold the VOL DOWN and then POWER button at the same time for at least 10-12 seconds until after the start-up screen appears and is joined by some small print at the top of the screen, then let them both go. If the TF booted the way it always does, you have not accomplished the task, try again until you have seen the 2 icons in the screen.
After a few seconds you should see a couple of icons in the middle of the screen called "Wipe Data" and "Android". The right "Android" will have a green highlight fading in and out. Wait a few more seconds until the term "Cold Booting Linux" appears in the list near the top of the screens and let it reboot. If you own a keyboard dock be sure you do this with the dock connected.
This process applies to all TF models, however, if your Prime or tf300 is locked up, there is a reset available using the hole just below the microSD slot, this is NOT the same as a hard reset.
12. Finally, restore your photos, docs etc & reinstall your apps from the backups, one group at a time & cold boot between each group that you restore. (Unless you are resetting because of system instability. In which case, read the next section, first.)
-Unquote-
I tried doing this but the TF froze at the point where the unit says "Cold-booting Linux". I left it for a good 30 minutes but no joy...
The other issue I have is that even when I attach my TF to my PC the PC doesn't recignise the unit. It knows I'm trying to attach something but it doesn't know what. Therefore I don't think I can flash anything like a new CWM version or kernel if the PC doesn't know where or what to flash to...?
I'd love to hear anyone's thoughts on this one...
Thanks in advance!

"Then I opened ROM Manager and allowed the app to update, I guess updating CWM too." - Never use ROM manager on the TF, it causes extensive problems. There is a warning thread about this in General.
You'll want to try running Roach2010's fix, either via my PERI tool (in my sig) or by manually typing the commands.

Lifesaver! One problem - when I plug my TF into my PC using the USB cable it doesn't recognise it. Won't this be a problem?
Sent from my GT-I9100 using xda app-developers app

(Also, I've replied a bit more to your post on Transformer Forum - Thanks mate!)

Alright you're going to want to download this while you read -- http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.24
Quick guide:
1. Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
2. Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip.
3. Run download.bat.
In the link below a driver package is also included, you need to either...
Code:
Open the Start Menu, type 'cmd' and hit enter, then type:
pnputil -a C:\path\to\driver folder\NvidiaUsb.inf file
exit
Then plug in the TF in APX mode and windows will find drivers automatically
Or you right click computer and hit 'Manage' and then hit 'Device Manager', find the ? entry that says APX and right click and hit 'update driver', then navigate to the folder.
Download the unbrick .zip from here: http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.24
(Before each file are 2 letters, (US, WW, CN, TW...) pick the one that is your Region. I'm assuming you need WW, which stands for World Wide, but if you reside in Taiwan take TW, China take CN and America take US.
Also download Wheelie NvFlash from here: http://androidroot.mobi/2012/05/31/wheelie-for-windows-beta/
Extract it, and copy the Contents of the folder into the Unbrick .zip folder's contents main folder, Overwrite any files that conflict.
Then you should be able to run Reflash_Sbkv#.bat to unbrick your TF in APX mode that is connected, try Sbkv2 first, then if you get access denied try Sbkv1.
Hope you're sorted out!

[Q] Apps will not update, device won't shutdown

Starting about two weeks ago, Google Maps app would begin launching itself periodically after opening any new apps. Then I started getting a notice when Hangouts was trying to update that "The package file is invalid" or something like that. That eventually became apps never finishing updates. This is especially noticeable with Google apps (Hangouts, Newsstand, Play, etc); they get to some percentage of completion and then just stop. (The percentage ranges between 37% [Newsstand] and 91% [Chrome]).
Cleared the Play Store cache and data and attempted to reboot, but the device would not shutdown. It cycled through the various shutdown prompts, then the shutdown spinning icon appeared.... and it stayed like that until the battery drained. Re-started after charging, nothing was fixed. Tried shutting down again, same problem. The only way it becomes responsive again is to hit the little hard reset button.
Did a full hard reset to factory spec, none of the apps will download updates at all. And when the device is fully booted I get a barrage of error messages saying that various Google apps/services have stopped working. (i.e. "Unfortunately, Google Maps has stopped working." or "Unfortunately, Google Play Services has stopped working.")
Device is a stock 32gb TF700T running I think 4.2.1 JB, with a 32gb SD card to which nothing has been written.

What do you mean by you did a "full hard reset"?
First, copy all data you don't want to loose off the tablet.
Then you can try to clear cache and data on everything Google. Go to Settings > Apps, swipe until you see All, then go to town: Maps, Hangouts, Services framework, Chrome, Play Store - the works.
Then go to Settings > Accounts and remove your Google account.
Reboot.
If it still hangs, try holding Power and Volume Down button together until the tablet boots into the bootloader menu.
You'll see 3 icons. Push Volume Down until "Wipe Data" is highlighted. Then press Volume Up.
It should reboot once it's done. If it returns you to the bootloader menu, use Volume Down to cycle to the Android, then hit Volume Up to boot the system.
If all that does not do it, you can manually reflash the Asus firmware or - even better - unlock the bootloader and flash a custom rom.

First, thank you for taking the time to reply. I appreciate the help.
And for what it's worth, the problem as evolved since I posted this; now, as soon as I power or wake up the device and enter my PIN, I start getting error massages that a variety of Google services have stopped working. Always Maps first.
berndblb said:
If it still hangs, try holding Power and Volume Down button together until the tablet boots into the bootloader menu.
You'll see 3 icons. Push Volume Down until "Wipe Data" is highlighted. Then press Volume Up.
It should reboot once it's done. If it returns you to the bootloader menu, use Volume Down to cycle to the Android, then hit Volume Up to boot the system.
Click to expand...
Click to collapse
This is what I meant by 'full hard reset'. Apologies for using confusing or incorrect verbiage.
berndblb said:
First, copy all data you don't want to loose off the tablet.
Then you can try to clear cache and data on everything Google. Go to Settings > Apps, swipe until you see All, then go to town: Maps, Hangouts, Services framework, Chrome, Play Store - the works.
Then go to Settings > Accounts and remove your Google account.
Reboot.
Click to expand...
Click to collapse
Okay, gave this a try. Still would not shut down on its own, and I had to hit the little reset button on the side. Got back in, added one Google account, attempted to update apps, and I get an error saying: "Update for [app name] could not be downloaded due to an error. (Error retrieving information from server. [RPC.S-7:AEC-7])" So I deleted that account and added another one. This time the Play Store wouldn't even show me the installed apps. White screen, spinning circle of sadness.
I don't know if this makes a difference, but I did not indicate in my original post that I have three different Google accounts on this device. But only one of them is the one used for downloading apps to this device.

If removing anything Google doesn't help, I would start fresh: Reflash the firmware following the steps under Alternative Install Method here: http://forum.xda-developers.com/showthread.php?t=1755576
Then set it up again with just one Google account. That should do it.

berndblb said:
If removing anything Google doesn't help, I would start fresh: Reflash the firmware following the steps under Alternative Install Method here: http://forum.xda-developers.com/showthread.php?t=1755576
Then set it up again with just one Google account. That should do it.
Click to expand...
Click to collapse
I attempted to reflash using the steps outlined at that URL, but to no avail. The update isn't recognized (perhaps because I'm already on that build number?), and the rar file does not launch.
At this point, I have two options: Install a custom ROM (can't really hurt, right?), or just get a new device. Considering ASUS is not updating the firmware anymore, meaning 4.2.1 is the highest OS version I'll ever run on it, I'm sort of leaning towards a new device. But I'll try flashing a custom ROM and see what that gets me.

tifosi77 said:
I attempted to reflash using the steps outlined at that URL, but to no avail. The update isn't recognized (perhaps because I'm already on that build number?), and the rar file does not launch.
At this point, I have two options: Install a custom ROM (can't really hurt, right?), or just get a new device. Considering ASUS is not updating the firmware anymore, meaning 4.2.1 is the highest OS version I'll ever run on it, I'm sort of leaning towards a new device. But I'll try flashing a custom ROM and see what that gets me.
Click to expand...
Click to collapse
You will need to unlock the bootloader. This can only be done with the app from asus. Then you must install a recovery. I recomend twrp 2.7.1.1 or philz touch recovery. If you want to stay stock flash sbdags's asus stock rooted rom. If you want stock, but with better performance, then flash CROMi-x. If you want the latest version of android and the new zen ui apps, flash CROMBi-kk, then my asus apps 2.0. If you want asus apps, you will have to wait till monday, the current releace has some issues.

tifosi77 said:
I attempted to reflash using the steps outlined at that URL, but to no avail. The update isn't recognized (perhaps because I'm already on that build number?), and the rar file does not launch.
At this point, I have two options: Install a custom ROM (can't really hurt, right?), or just get a new device. Considering ASUS is not updating the firmware anymore, meaning 4.2.1 is the highest OS version I'll ever run on it, I'm sort of leaning towards a new device. But I'll try flashing a custom ROM and see what that gets me.
Click to expand...
Click to collapse
.rar file??? Where did you get that from? The Asus firmware downloads as a zip (which contains the zip to be renamed). The ecovery will not flash a rar file...
You need to outline the exact steps you are taking. Somewhere you are making a mistake...

berndblb said:
.rar file??? Where did you get that from? The Asus firmware downloads as a zip (which contains the zip to be renamed). The ecovery will not flash a rar file...
You need to outline the exact steps you are taking. Somewhere you are making a mistake...
Click to expand...
Click to collapse
Pardon, I misspoke. I downloaded this zip file: www . asus . com /Tablets_Mobile/ASUS_Transformer_Pad_Infinity_TF700T/HelpDesk_Download/ V10.6.1.14.10 Only for US SKU (Android 4.2.1)
Unzipped the zip within the zip and copied that to the microSD card. Inserted the card into the tablet and nothing happened. Restarted the tablet, nothing happened. Same problems persist.

tifosi77 said:
Pardon, I misspoke. I downloaded this zip file: www . asus . com /Tablets_Mobile/ASUS_Transformer_Pad_Infinity_TF700T/HelpDesk_Download/ V10.6.1.14.10 Only for US SKU (Android 4.2.1)
Unzipped the zip within the zip and copied that to the microSD card. Inserted the card into the tablet and nothing happened. Restarted the tablet, nothing happened. Same problems persist.
Click to expand...
Click to collapse
If you use a microSD you have to rename the zip and boot into recovery.
Rename the ...user_ xxxx.zip to
EP201_768_SDUPDATE.zip
Copy it to the microSD, then boot to recovery with Power and Volume Down buttons and press Volume Up on the flashing RCK icon. That should do it.

berndblb said:
If you use a microSD you have to rename the zip and boot into recovery.
Rename the ...user_ xxxx.zip to
EP201_768_SDUPDATE.zip
Copy it to the microSD, then boot to recovery with Power and Volume Down buttons and press Volume Up on the flashing RCK icon. That should do it.
Click to expand...
Click to collapse
Okay, the instructions did not say to rename the file or to boot into recover.
I don't have the tablet with me today, so I will try this when I get home. Thank very much you for your help.

Followed instructions. Got notice that the update was starting, then instantly I get a prostrate android with his chest panel opened, a red triangle with an exclamation point and the word 'Error!' underneath. The device is now completely unresponsive in this condition, reacting only to holding the power button down until the device restarts.

Ok, halfway there.
The recovery sees the zip file but fails to open it. Either because it became corrupted during download/unzip or because it's named incorrectly.
You can just reboot by long pressing power from the dead Android screen btw - no harm done.
Recheck your steps.
You download the Asus firmware (file name contains "UPDATELAUNCHER")
You unzip that file ONCE, resulting in a file name that has "user+firmware version" in it.
You rename that "user" file to EP_201_768_SDUPDATE.zip (caps do matter).
Make sure Windows is showing the file extensions! In Windows Explorer - does it show the file's extension?
Do you have "Document" or "Document.doc", "Picture" or "Picture.jpg"?
If Windows adds file extensions automatically you may have named the file ....SDUPDATE.zip.zip

Okay, windows is not automatically adding the extension (I get the deleted file extension warning if I omit it and try to save with the suggested file name). The file name in the last two posts are different (one with an underscore between the EP and 201 and one without), and I've tried it both ways and I'm getting the same result regardless. And I've downloaded the rom update file fresh from the ASUS website, and I'm still ending up in the same place. Broken Android.
Just to clarify, when I download the original "UPDATELAUNCHER" file, my steps are to unzip that file, extract the zip file within, and rename that to EP_201_768_SDUPDATE.zip. Put that on the microSD card root, insert that into the TF700T, start in recovery (PWR+Vol down), select 'RECK' (I think that's what it reads) and hit Vol up, and it should take care of itself after that. Yes?

tifosi77 said:
Just to clarify, when I download the original "UPDATELAUNCHER" file, my steps are to unzip that file, extract the zip file within, and rename that to EP_201_768_SDUPDATE.zip. Put that on the microSD card root, insert that into the TF700T, start in recovery (PWR+Vol down), select 'RECK' (I think that's what it reads) and hit Vol up, and it should take care of itself after that. Yes?
Click to expand...
Click to collapse
Your card is FAT32 formatted?

Okay, I managed to miss the instruction to use the alternate method and so had not formatted the microSD to FAT32.
Formatted to FAT32, re-ran the steps and apparently the update took..... in part. I am no longer getting the same bevvy of 'Unfortunately [Google process] has stopped.' messages as I was before. But when I launch Google Play Store app, the 'Unfortunately...' message appears immediately. None of the other Google apps present this problem, but of course many of the 'problem' apps from a few weeks ago are not on the device by default. And with Play Store constantly crashing, there's no way for them to get on the device.
So the device works.... but no apps can be downloaded or updated.

Okay, I just did another factory reset. Can launch Play Store.... but no apps will update. I get an error saying "Update for [app] could not be downloaded due to an error. (Error retrieving information from server. [RPC:S-7:AEC-7])" A trip to the Google Box indicates that this might be a problem on Google's end, and is account related. Si?

Okay, sorry to be shotgunning the thread..... the error message appears to be account-specific. I've signed in using a different Google account, and everything appears to be fine and dandy when using that account as the primary for the device. I've added the 'problem' account, and it seems to be going smoothly. Just updated something like 40-odd apps without incident.
Thanks for the help!