Related
Hey there hope this is the right place for this ... Just want to report something that has happened. I am currently unable to use the G tablet stock vanilla TnT... any clue as to why this would happen? I dont really use it anyway however should this be resolved? and would it affect the tablet in the long run if not addressed? I use Launcher pro and the tablet forces itself to that when "home" force closes. I would like to try the TnT lite however am not confident about it.
Do i need to root the device before i hold the power button and vol +? to flash the new rom ( it bugs me that this is all i have to do to put in a custom rom. it seems to easy, unless it is that easy)
Will i lose all the files, PDF's, and documents that i have on it once i flash the new rom ?
As you can see im a noob to Android. Thanks for advice and guidance in advanced and patients.
Follow the instructions in the alternate gtab firmware post. It worked great for me. I would suggest installing cwm so you can back up your existing firmware.
My update would force close during download on the stock firmware. I finally got it to work by minimizing the pop up that displayed the progress. For some reason the screen would crash the download.
Your files should be there but you will lose all user settings and installed apps when you do the factory reset.
This is a common issue with stock, and TnT Lite. The user data seems to be very unstable once you upgrade to different firmware.
The "easiest" thing to do is just wipe the user data. However, if there is certain data you need to keep, I would recommend the excellent Titanium Backup. The only caveat is that the device has to be rooted, to use it.
roebeet said:
The only caveat is that the device has to be rooted, to use it.
Click to expand...
Click to collapse
And Z4root does this easily. Just install and click "root".
RyuFDAC01 said:
Hey there hope this is the right place for this ... Just want to report something that has happened. I am currently unable to use the G tablet stock vanilla TnT... any clue as to why this would happen? I dont really use it anyway however should this be resolved? and would it affect the tablet in the long run if not addressed? I use Launcher pro and the tablet forces itself to that when "home" force closes. I would like to try the TnT lite however am not confident about it.
Do i need to root the device before i hold the power button and vol +? to flash the new rom ( it bugs me that this is all i have to do to put in a custom rom. it seems to easy, unless it is that easy)
Will i lose all the files, PDF's, and documents that i have on it once i flash the new rom ?
As you can see im a noob to Android. Thanks for advice and guidance in advanced and patients.
Click to expand...
Click to collapse
Tntlite is that easy I was surprised. Too since rooting my HTC hero a year and a half ago was so much more hands on
Hey guys.... first off thanks for the advice it worked great it was easy to do... flashed TnT lite and was excited.... i attempted to pull an app from freewareloversDOTcom and was stuck in downloading status for some time even with a good wifi signal... This is where all hell broke loose ....the file i wanted never downloaded.... then the pic gallery forced closed then the launcher forced closed and had to shut down now now its in bootloop....I attempted to power and vol + but nothing happened in fact got a triangle !.... what is needed now.....
LOL at the entire situation this was my fear..... please if someone with extreme patients can list or point to a noob friendly thread on what i need to do
i have a microSD card can that be used read somewhere that i may need that.....
I thank you guys VERY VERY MUCH appreciate this
Hey guys.... first off thanks for the advice it worked great it was easy to do... flashed TnT lite and was excited.... i attempted to pull an app from freewareloversDOTcom and was stuck in downloading status for some time even with a good wifi signal... This is where all hell broke loose ....the file i wanted never downloaded.... then the pic gallery forced closed then the launcher forced closed and had to shut down now now its in bootloop....I attempted to power and vol + but nothing happened in fact got a triangle !.... what is needed now.....
LOL at the entire situation this was my fear..... please if someone with extreme patients can list or point to a noob friendly thread on what i need to do
i have a microSD card can that be used read somewhere that i may need that.....
Click to expand...
Click to collapse
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recovery\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recovery/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
dcom222 said:
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recover\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recover/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
Click to expand...
Click to collapse
Dude thank you so much for your effort in this !!!!! gonna try this as soon as i put my baby to sleep.... will let you know if this worked for me
dcom222 said:
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recover\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recover/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
Click to expand...
Click to collapse
You mind if I steal these directions? It's more detailed than the one I wrote up on my TnT Lite post. I'd like to post it there (specifically the command file, as some people have issues understanding the "SDCARD2" change).
And thanks for posting your experiences to help the other users here!
roebeet said:
You mind if I steal these directions? It's more detailed than the one I wrote up on my TnT Lite post. I'd like to post it there (specifically the command file, as some people have issues understanding the "SDCARD2" change).
And thanks for posting your experiences to help the other users here!
Click to expand...
Click to collapse
Please do if they look to be correct. Hopefully we'll see confirmation that these instructions work.
I appreciate all your work on the gTablet!
dcom222 said:
Please do if they look to be correct. Hopefully we'll see confirmation that these instructions work.
I appreciate all your work on the gTablet!
Click to expand...
Click to collapse
Same here Roebeet thanks for your work...dcomm222 thanks again... So I tried to only install the TnTlite 2.0 from the microsd card, it read it, looked to have loaded it, and it went right into the bootloop again.... I really want TnT lite ......
so now i am going to try your method... fingers crossed
RyuFDAC01 said:
Same here Roebeet thanks for your work...dcomm222 thanks again... So I tried to only install the TnTlite 2.0 from the microsd card, it read it, looked to have loaded it, and it went right into the bootloop again.... I really want TnT lite ......
so now i am going to try your method... fingers crossed
Click to expand...
Click to collapse
I had no luck trying to re-flash to 2.0X once I got in the boot loop - I couldn't get past it no matter what until I went back to stock. Once I was back at stock I could re-flash to 2.0X from the internal SD. I'm still trying to figure out what's getting me in the boot loop - everything seems to work great for a while.
Good luck!
dcom222 said:
I had no luck trying to re-flash to 2.0X once I got in the boot loop - I couldn't get past it no matter what until I went back to stock. Once I was back at stock I could re-flash to 2.0X from the internal SD. I'm still trying to figure out what's getting me in the boot loop - everything seems to work great for a while.
Good luck!
Click to expand...
Click to collapse
GOT IT BACK!!!! geez man I was full on panic mode
have you flashed back to TnT lite back yet and how long does it last? Damn i am so tempted to go back im thinking it has something to do with what we attempted to load on the tablet ... i dont know just looking for a reason to Flash ....can this constant recovery flash do any damage to the tablet? I would like to try other Roms but dont want to mess my tablet up..
BTW i got this EUL when it rebooted especially sections 4.1 and 4.2 wtf!!! sorry about that but that is how i felt
Thanks again guys!!!!
RyuFDAC01 said:
GOT IT BACK!!!! geez man I was full on panic mode
have you flashed back to TnT lite back yet and how long does it last? Damn i am so tempted to go back im thinking it has something to do with what we attempted to load on the tablet ... i dont know just looking for a reason to Flash ....can this constant recovery flash do any damage to the tablet? I would like to try other Roms but dont want to mess my tablet up..
BTW i got this EUL when it rebooted especially sections 4.1 and 4.2 wtf!!! sorry about that but that is how i felt
Thanks again guys!!!!
Click to expand...
Click to collapse
If I remember correctly, the stock firmware with the OTA update will prompt you to accept a license and prompt to set the time, etc....
I just flashed the TnT 2.02 again. So far it seems OK, however it did the first 2 times I did it as well. I followed all of the instructions at "forum.androidcentral.com/showthread.php?p=442691#post442691" except I substituted using roeboot's TnT. Once I did it I had everything working (flash, market, etc...). Both times the boot loop happened when I tried to install or uninstall something, and both times were after a few hours of use. I tried a third time and almost instantly got into a boot loop, but I think I got ahead of myself in that try and did some things out of order. The good thing is that I was able to recover each time.
Out of curiosity, did your tablet come with a gray or green cloth to clean the screen? The reason I ask is that I thought I had seen somewhere that this might be an indication of a difference in gTablets.
The EULA shows up with a new stock firmware - and yeah 4.1 / 4.2 kinda bugged me too. I never selected "I Agree" - fark that.
As for the boot loops, it seems that we still can't pin it down - maybe it's just random, I don't know.
Hi,
I was stuck after bootlooping using Cyanmod, then flashing NVflash still didnt fix the issue, this fix did it for me. Thanks for getting me back up & running. I will give another shot at using cyanmod now that I have all the files needed to get me back.
BTW< I have a green cloth. What does that mean?
Thanks,
Rich
dcom222 said:
If I remember correctly, the stock firmware with the OTA update will prompt you to accept a license and prompt to set the time, etc....
Out of curiosity, did your tablet come with a gray or green cloth to clean the screen? The reason I ask is that I thought I had seen somewhere that this might be an indication of a difference in gTablets.
Click to expand...
Click to collapse
My tab came with a grey cloth... funny thing though I got mine on the second wave of shipments to sears... I NEVER had any issues with the time i just set it and it kept the time... I remembered that when these first came out that was a problem... i thought mine was diff because i never had any issues with time reseting itself... anyway Thanks again dude for your help hope i could play this forward to someone more noobier than me
Roebeet looking forward to your TnT lites...
dcom222 said:
After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Click to expand...
Click to collapse
I now have clockwork recovery installed... How do i copy the update.zip from external microsd to internal microsd... mounting sd-ext gives an error..
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Error mounting SDEXT:!
Frustration levels are high with this device!!
Thanks!
a "me too" reboot problem
I was able to install TNT Lite 2.0, then 2.11. I got Clockwork Recovery installed as well.
The market would start, but if I did a search for obvious things like "Kindle", the market would give an error that it didn't exist in the market. Thinking it was the error situation described here:
http://forum.xda-developers.com/showthread.php?t=845175
I applied those instructions, and rebooted.
Upon reboot, it ended up in a continual reboot loop.
Trying to do the start with volume+power, it brings up Clockwork Recovery, and when told to wipe data/factory reset, it stays in the reboot loop. When told to apply sdcard's update.zip, it looks only at the one on the internal sdcard, which is for CWR, and goes back into the loop.
At that point I setup a microSD with the information from this post:
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
including changing the line from sdcard to sdcard2. Again it doesn't recognize that the internal sdcard2 is plugged in, and attempts to mount it with CWR (mount /sd-ext) yields the error:
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Error mounting SDEXT:!
So, unfortunately I'm at an impasse, like the previous poster. I just bought the tablet a couple of days ago, so I'm far from expert at tweaking it into working.
Any suggestions on what to do, are greatly appreciated.
PS - Bought the gtablet from Office Depot, and received a green cloth.
Boot into clockwork recovery and go to advanced and format SD, use the 2gb and 512mb I believe, then flash TNT or another rom. That fixed my boot loop.
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 ;-)
I've seen posts in other forums about where to find files and how to do this with other devices but nothing specific to the TF700. After installing the latest system update (4.2.1) I found a lot of apps, including system apps. were crashing and the whole thing was running incredibly slow. I went into the settings and did a factory reset, reinstalled the apps and set everything up again but the same thing is still happening.
I read somewhere that flashing the system rom (which I'm guessing reinstalls the system files) might be a way to get things working again. I've never done this before, and I know things can go badly if you do it wrong, so I'm hoping someone can walk me through it, including letting me know which files I should be using.
Thanks in advance for the help.
slap_shot_12 said:
I've seen posts in other forums about where to find files and how to do this with other devices but nothing specific to the TF700. After installing the latest system update (4.2.1) I found a lot of apps, including system apps. were crashing and the whole thing was running incredibly slow. I went into the settings and did a factory reset, reinstalled the apps and set everything up again but the same thing is still happening.
I read somewhere that flashing the system rom (which I'm guessing reinstalls the system files) might be a way to get things working again. I've never done this before, and I know things can go badly if you do it wrong, so I'm hoping someone can walk me through it, including letting me know which files I should be using.
Thanks in advance for the help.
Click to expand...
Click to collapse
Download the full Asus firmware from Asus site, unzip the file then copy the unzipped file to the root of your micro sdcard, you should see a notification to upgrade, do the upgrade.
Firmware unavailable
buhohitr said:
Download the full Asus firmware from Asus site, unzip the file then copy the unzipped file to the root of your micro sdcard, you should see a notification to upgrade, do the upgrade.
Click to expand...
Click to collapse
I have tried to do that but the Build Number that I have isn't on the Asus site. After upgrading my build number is JOP40D.ww_epad-10.6.1.14.4-20130329
All the ones on the Asus site have 2012 as the year, and I even tried the one that matched everything else and just get an error message after it starts installing.
Any ideas?
slap_shot_12 said:
I have tried to do that but the Build Number that I have isn't on the Asus site. After upgrading my build number is JOP40D.ww_epad-10.6.1.14.4-20130329
All the ones on the Asus site have 2012 as the year, and I even tried the one that matched everything else and just get an error message after it starts installing.
Any ideas?
Click to expand...
Click to collapse
Go to this page, select "Android" and find your build number - it's there: Version V10.6.1.14.4(WW)
http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1
slap_shot_12 said:
I have tried to do that but the Build Number that I have isn't on the Asus site. After upgrading my build number is JOP40D.ww_epad-10.6.1.14.4-20130329
All the ones on the Asus site have 2012 as the year, and I even tried the one that matched everything else and just get an error message after it starts installing.
Any ideas?
Click to expand...
Click to collapse
Try this method:
Download this from Asus " Version V10.6.1.14.4(WW) "
You have to decompress the ZIP File. Then you have the actual update ZIP file, then rename the File to "EP201_768_SDUPDATE.zip" (without quote).
Reformat your micro sdcard to fat32 (make sure you do this) and copy the File to the root of a FAT32 formated microSD Card and insert into your Tab.
Now, reboot into recovery (hold volume down and power button and release when see white text on the screen) and the update install will begin without any verification of Software Version.
eenyae about
buhohitr said:
Try this method:
Download this from Asus " Version V10.6.1.14.4(WW) "
You have to decompress the ZIP File. Then you have the actual update ZIP file, then rename the File to "EP201_768_SDUPDATE.zip" (without quote).
Reformat your micro sdcard to fat32 (make sure you do this) and copy the File to the root of a FAT32 formated microSD Card and insert into your Tab.
Now, reboot into recovery (hold volume down and power button and release when see white text on the screen) and the update install will begin without any verification of Software Version.
Click to expand...
Click to collapse
This did it --- Thanks very much. Renaming the file allowed the update to complete and now it seems to be working normally again. I sure appreciate the help everyone!! :good:
So I've had a bit of bad luck mixed with poor timing. Here's the run down.
I have an Asus Transformer TF101 which was running the stock rom.
I rooted my Tablet a few weeks back without any problem. Things were great. Then, I tried to upgrade to Jelly Bean from ICS using Team EOS (I followed these 2 threads mainly, http://www.transformerforums.com/fo...ficial-faq-teameos-4-android-4-2-x-tf101.html & http://forum.xda-developers.com/showthread.php?t=2063406)
I put the ROM and all the files needed onto my micro SD card.
I booted into TWRP and followed the instructions. Things seemed to have gone great. When I rebooted, I saw the new splash Logo upon bootup and awaited it to do it's thing. It never did. I let it run for an hour and it never made it into the OS.
I rebooted, went back into TWRP with plans to redo the procedure, only now the microSD card slot is not being picked up. I tried multiple micro SDs of different sizes (1GB-32GB), I've tried inserting before boot up, inserting after bootup, inserting after bootup and then rebooting the device. No luck.
I bought a USB adapter that plugs in where the power plug goes, hoping I could run the files off a USB flash drive. or a micro SD card within a USB flash drive. No luck.
I am running Teamwin's TWRP 2.3.2.3
My backup from nandroid happens to be on my microSD card too. So I can't use it to recover the old OS either.
TL;DR: Micro-SD card stopped working after a failed attempt to flash an OS. OS and backups are on the microSD card. PC recognizes the device but won't let my access the hard drive.
Does anyone have any suggestions on what to try?
Thanks!
Well, the USB is not set up to be mounted in recovery. Keep in mind, the microSD is mounted at /sdc/ in TWRP.
You can always use ADB and push a file to the internal (/sdcard/) so you can flash if your microSD slot is dead.
Let me find a post on how to do this.
EDIT: Here is what to do if you need to use ADB:
Plug tablet to PC via USB
It should install new hardware and show 1 devices, an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: http://db.tt/b9dQ6xzp
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite ROM. If applicable, save any other files needed (GAPPs or kernel)
Save this at c:\adb\ROM.zip. Other files save accordingly like Kernel.zip and GAPPs.zip.
Next, run the following commands
Code:
adb push ROM.zip /sdcard/
Once this competes, you will need to repeat for any other files to flash like GAPPs or Kernel.
After these files have been transfered, you can install a file from the internal (/sdcard/) directory.
frederuco said:
Well, the USB is not set up to be mounted in recovery. Keep in mind, the microSD is mounted at /sdc/ in TWRP.
You can always use ADB and push a file to the internal (/sdcard/) so you can flash if your microSD slot is dead.
Let me find a post on how to do this.
EDIT: Here is what to do if you need to use ADB:
Plug tablet to PC via USB
It should install new hardware and show 1 devices, an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: http://db.tt/b9dQ6xzp
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite ROM. If applicable, save any other files needed (GAPPs or kernel)
Save this at c:\adb\ROM.zip. Other files save accordingly like Kernel.zip and GAPPs.zip.
Next, run the following commands
Code:
adb push ROM.blob /sdcard/
Once this competes, you will need to repeat for any other files to flash like GAPPs or Kernel.
After these files have been transfered, you can install a file from the internal (/sdcard/) directory.
Click to expand...
Click to collapse
Thanks so much frederuco! I will be trying this later today and will update this post as soon as I do.
I just wanted to say good luck, and we are all counting on you.
Almost there!
frederuco said:
I just wanted to say good luck, and we are all counting on you.
Click to expand...
Click to collapse
The update! I followed your instructions, while on the cmd prompt, I got no confirmation that the files were moved, but they appear to be on the device now. When I go to reinstall through TWRP, the flashing fails. I am going to do some digging around the forum to see what solutions there may be, but if you (or anyone reading) has an idea, do tell.
I will be sure to update this thread if I fix it, including the solution I found.
Try downloading the ROMs again.
Also, note that I edited my reply as I had said ROM.blob and it should be ROM.zip.
frederuco said:
Try downloading the ROMs again.
Also, note that I edited my reply as I had said ROM.blob and it should be ROM.zip.
Click to expand...
Click to collapse
I think I'm in good shape. I tried to edit my post from earlier, but I had to wait a few minutes before it would let me.
I realized the file didn't finish transferring to the tablet. Moments after my last post, I got a confirmation from cmd prompt that the first file finished. The second one just finished, and the third is still transferring I suspect. That would totally explain the failure.
db1984 said:
I think I'm in good shape. I tried to edit my post from earlier, but I had to wait a few minutes before it would let me.
I realized the file didn't finish transferring to the tablet. Moments after my last post, I got a confirmation from cmd prompt that the first file finished. The second one just finished, and the third is still transferring I suspect. That would totally explain the failure.
Click to expand...
Click to collapse
Yes, that would do it!
frederuco said:
Yes, that would do it!
Click to expand...
Click to collapse
Alright, so I got past the logo, Android upgraded all the Apps and is now "Starting apps" .. it's been here for about 10 minutes. I think I can take it from here.
The ADB push was the solution.
Waited another 15 minutes. Nothing happened (stayed at Starting apps)
Restarted device. Booted up as it should and I am now all set. Thanks again!
Now that you're using EOS can you use the microSD slot? I know moving from stock to EOS fixed my card slot issues not to mention that I'm loving the Jellybean goodness
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
bsoplinger said:
Now that you're using EOS can you use the microSD slot? I know moving from stock to EOS fixed my card slot issues not to mention that I'm loving the Jellybean goodness
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
I'm fairly certain the slot itself is broken. Haven't been able to get it to read things yet.
I'm still having some minor issues with the setup, but I know I've seen fixes to these problems when browsing this forum. Google Search/Google Now crashes 3-4 seconds after opening it. The system also reboots "randomly" (really, just when it's idle for more than 10 minutes), I also had to go into TWRP last night to get the system to power down. Long pressing power and selecting Power Off simply rebooted it.
But compared to where I was 24 hours ago (and had been stuck there for 1+ week, I really didn't want to burden people with my problem since I'm a lurker here), I really can't complain and have full confidence that I'll be able to get the kinks worked out.
At least I have an adapter for the power port, so I can plug USB sticks (or USB-microSD adapters) into the tablet still.
db1984 said:
I'm fairly certain the slot itself is broken. Haven't been able to get it to read things yet.
I'm still having some minor issues with the setup, but I know I've seen fixes to these problems when browsing this forum. Google Search/Google Now crashes 3-4 seconds after opening it. The system also reboots "randomly" (really, just when it's idle for more than 10 minutes), I also had to go into TWRP last night to get the system to power down. Long pressing power and selecting Power Off simply rebooted it.
But compared to where I was 24 hours ago (and had been stuck there for 1+ week, I really didn't want to burden people with my problem since I'm a lurker here), I really can't complain and have full confidence that I'll be able to get the kinks worked out.
At least I have an adapter for the power port, so I can plug USB sticks (or USB-microSD adapters) into the tablet still.
Click to expand...
Click to collapse
The workaround for Google Now crashing is to disable Hotword Detection in Settings - Language & Input - Voice Search (or something like that). Search the EOS thread for "Hotword" and you will find the location.
Do you have a SD in the dock? This can cause SOD and RR's.
Hmm, I guess I have never tried powering down on EOS, but I am pretty sure it works. I just put my tablet to sleep and never turn it off. I find my tablet (even undocked) will lose more power when it is off than when it is sleeping.
frederuco said:
The workaround for Google Now crashing is to disable Hotword Detection in Settings - Language & Input - Voice Search (or something like that). Search the EOS thread for "Hotword" and you will find the location.
Do you have a SD in the dock? This can cause SOD and RR's.
Hmm, I guess I have never tried powering down on EOS, but I am pretty sure it works. I just put my tablet to sleep and never turn it off. I find my tablet (even undocked) will lose more power when it is off than when it is sleeping.
Click to expand...
Click to collapse
Nope, nothing was in the dock. I actually didn't have the keyboard dock plugged in during the "crisis"- I did try getting TWRP to read a card from it once, that was about it.
I read somewhere else, that once you let the battery die on it's own, and recharge, the "never powers off" issue goes away for many people (haven't seen one specifically relating to EOS on TF101, but the other symptoms were spot on)
I'll be checking out the Google Now tweak in a bit.
I'd been running a custom kernel on my Transformer since about a week or two after I bought it at a Black Friday sale simply because it would keep running on the stock ICS ROM. Changed to KAT kernel when I moved to EOS. You might want to consider a custom kernel if you have a Transformer that suffers from the reboot issue like mine did.
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
db1984 said:
-snip-
Click to expand...
Click to collapse
You may want to try doing a full format in TWRP, and using the superwipe full scripe from the ARHD thread, then formatting again, wipe cache and dalvik, push the latest EOS, KATkernel and Gapps to the device, wipe dalvik cache and cache, flash EOS, wipe dalvik cache and cache, boot into the ROM, boot back into twrp, wipe cache and dalvik, flash Gapps, wipe cache and dalvik, boot into the ROM, boot back into TWRP, wipe cache and dalvik, flash KATkernel, wipe cache and dalvik, cold-boot into the ROM.
That should set you up with the most stable your tf is going to get, it seems erroneous and like a ton of work, but I strongly believe in doing this whenever I flash a new rom setup, I've gotten to doing it in about 10 minutes now.
Just an update.
EOS's random reboots were getting pretty bad. Happened a few times while I was working on a few docs (thankfully Evernote had autosaved)
I also noticed when the screen would go off, it would eventually turn back on and attempt to reboot, getting stuck at the Asus loading splash (pre EOS logo). I ended up re-flashing with my newly gained leet adb skills (thanks frederuco ) and went with Cyanogenmod 10. I've only had 1 random reboot since and Google Now seems to work 90% of the time.
I'm sure there are some more things I can do to fine-tune it, still getting a hang of everything.
Thanks again for everyone who's helped.
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!