Related
Hey all, just wanted to give a quick rundown. I shared this on Slickdeals earlier and someone recommended I throw it over here so that it might help anyone. My Coworker got his gTablet yesterday (from the Woot deal in March) and I had the chance to play with it/flash a custom ROM.
First about the stock ROM. His had angry birds and flash preinstalled, there were some funny directories setup on the internal storage which included a few apps (angry birds and flash amoungst them). I suspect they did some funny business at the factory with our units, but it did not in ~ANY~ way appear to be used/returned etc. The directories I remember were "Master", which I believe had apps and ... Oh hell it's too long now, something else. Anyways it didn't appear to be anything other than new is my point.
Next, the screen. It was definitely a TN panel and did have some odd viewing angles, and while not ideal it was certainly not anything that was preventing one person from enjoying it, vertical or horizontal. It was difficult for others to gather around and see videos well, so if that is a large concern for you then be concerned I suppose.
The stock ROM. It came with 1.1-3381 (or whatever the 33 was). It really does suck. They disable the menu button in most locations with the stock ROM, and it was slow/sluggish just like everyone has been saying.
Now I hope this crash course is of some help to anyone with their new toy. First to check your ROM version, you can go tab the Gears icon at the side of the screen, then choose About in the left menu. In here you'll find the rom version (should be something like 1.1-3389, 1.1-3588 or 1.2-something). Here's what I did to get his updated. Get familiar with XDA, it'll be a great friend and resource.
1.) I loaded the 1.1-3588 stock recovery, an upgrade from the 1.1-3389 recovery. It was possible to do this by going to this page (don't forget to thank Roebeet for putting all of this together), downloading the "3588 Recovery Pack v1.0".
2.) Unzip the 3588 Recovery Pack v1.0 then connect your tablet to your PC and enable USB mode (when you plug it in, you'll need to click the Yellow/Orange circle in the upper-right, then choose to enable USB tethering). Copy the "recovery" folder, and the update.zip to the root (what opens when you double-click the tablet drive) of the tablet internal memory (Probably D: or F: ).
3.) After the files copy to the tablet, turn off USB tethering, then turn off the tablet. You'll be restarting it in Recovery, which will automatically load the new recovery.
4.) To start the tablet in recovery, have the tablet turned off, then press and hold the power button and volume + button. You'll see a small message in the upper-left to indicate that it is starting in recovery. You can release the buttons now.
5.) After the update finishes installing the tablet will automatically reboot to Android once again, with the ugly Tap And Tap interface. This is OK, you're two steps from fixing it.
6.) Turn on USB tethering again, then open the tablet folder and delete the recovery folder and update.zip.
7.) Go back to this page, and once again thank Roebeet, and download "clockworkmod .8 bekit". Once downloaded, unzip it, then copy the recovery and update.zip to the root of the internal memory again. Turn off the tablet.
8.) Start the tablet in Recovery again by holding power button and Volume + at the same time. Once again you'll see a message in the upper-left and you can release. It'll do its thing and reboot to Android when it completes.
9.) After you get into Android again, start USB Tethering then delete the recovery folder and update.zip.
10.) At this point you can load what ROM you want (within limits, BE SURE TO READ THE ROM THREADS FIRST). I installed Vanilla AOSP Gingerbread ROM. Go download the file from that thread, then place it into the root of your tablet internal memory. Be sure to thank kornyone for their work. Also be sure to download the "gapps" available on this page as well, for you will have to install it to have the Android Market, GMail, etc.
11.) To install it, turn off the tablet, reboot into Recovery (Power button & Volume + at the same time..). You'll now be in Clockworkmod, a custom recovery. You can navigate the custom recovery by using the volume rocker to go up and down, the power button to go back a menu, and the Home soft key to press enter.
To properly install a ROM you should always first clear the data/system/cache. It's been a while since I've used clockworkmod, but I believe the option you are looking for is Factory Data Reset, choose Yes on the next screen. Then delete cache just to be sure.
Now you can go to "Install ZIP from sdcard", then "Choose zip" or something akin to it. Navigate to the file you copied, and tell it to install. Wait a short while and you should see that it successfully installed. Now just press the power key a few times to get back to the main menu and then choose to Reboot (whatever the top option is).
Enjoy your Gingerbread Android.
A few app recommendations: I use LauncherPro. It's available in the Android market and it's a "Home" replacement. Try it out, it's smooth and it has a bunch of extra widget if you purchase the program (1.99). Also check out Dolphin Browser HD. The last word of advice I can give is to get familiar with Long Press, it's basically right-click in Android. To do a long press just hold down on an icon or a blank area and see what happens.
A round of thanks go out to Roebeet and kornyone for putting the files used together, and a special thanks for the excellent documentation Roebeet. If I've left anyone out or placed this post in the wrong section please let me know and I'll get it fixed.
newbie question
I load the clockworkmod recovery and nothing changes. How do I get the clockwork mod to work? I already have my gTablet rooted. Now just trying to get to where I can load a custom ROM.
Thanks
apboswell said:
I load the clockworkmod recovery and nothing changes. How do I get the clockwork mod to work? I already have my gTablet rooted. Now just trying to get to where I can load a custom ROM.
Thanks
Click to expand...
Click to collapse
If you have flashed clockwork properly then to power on your device hold the volume up key as press the power button. This will load the recovery kernel and the clockworkmod, from which you can backup your device and install custom roms.
Just wanted to posted a quick update -- Two of the tablets that people at my workplace ordered suffered an odd corruption of the internal memory. The symptoms were random app's force closing, then upon trying to reboot the device it simply boot loops (the OS screen displays, then flips back to Viewsonic -> Load screen, repeat endlessly). Got them booted into recovery and tried to load data to which it reported the data partition could not be loaded due to the block being inaccessible. After a quick search the solution to this problem if you encounter it is:
1.) Boot into clockworkmod .08 by holding the power button and volume + button until you see the Recovery key press detected in upper-left.
2.) Go to advanced using the volume buttons, then press the home key to enter the advanced menu.
3.) In here go to Partition SD Card and select 2048, then 0. Wait a few minutes and the data partition will be ready to go again.
At this point I went ahead and did formatted the following partition through the mount menu: boot, system, data, cache. Afterwards I loaded the ROM again and everything appears to be working well.
Hope this helps anyone else who gets this random error.
Good post! Thanks!
The SD repartitioning is a very common fix here, in XDA. Usually it's what we try if you have weird FC's or file corruption and a re-flash or data wipe doesn't fix things. I've had to do that at least twice on my own device, over the last 3 months or so.
Also, keep in mind that the 3588 Recovery Pack is designed with a rooted ROM in mind (it lets you flip back and forth between clockworkmod and standard recovery via a script that can run off the GTablet or via adb)
**** 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
Updated 14-Dec-2011: I'm posting an updated recovery, "20111213" (I compiled it yesterday) below. I'm not going to bother cleaning up this entire post with updated information, as I'm just too tired right now. Please read the post, then read the "Changes" section towards the bottom... then download the update (if you want.) Probably this weekend some time, I'm going to be consolidating the posts for all 3 models of this device into a single post with three download links. (I'm trying to get them all in sync with each other.)
**** 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 T869 (tmobile galaxy tab 7 plus) tablet.
WHAT THIS DOES:
Installed from recovery, this .zip will first ensure that it's running on the Samsung/TMobile SGH-T869. If you have a different model, don't waste your time downloading it. It won't work. I do NOT have this tablet to test with, and a special thanks to shadejinx for doing the testing. That being said, he tells me that the backup and restore both work okay. However, there is an issue with rebooting back into recovery (see Post Installation notes and Issues.) If you want to try this, 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.
So, once it knows that it's working on the proper type of tablet, this package will make a backup copy of your existing recovery image, and place it in your internal storage with the name starting with "recovery_backup" and ending with the version of the recovery package you installed. For example, recovery_backup_20111206.img.
Next, a new version of the clockwork mod recovery is installed.
Then, the script will look for and delete any existing clockworkMod recovery backups that you have sitting around. Why? Because I'm re-using the script I wrote for the GT-P6210 tab... read that thread if it matters. Once my CWM-based recovery is installed, overwriting it with the same or newer versions won't delete the backups anymore.
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.
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 "t869_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.)
3. Select the file you placed on your storage card (starts with "t869_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
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/showpost.php?p=20074586&postcount=14
Update: According to shadejinx, this doesn't work for the SGH-T869. However, there's an alternative way, but you must have adb installed: Connect your tablet to the PC you have adb installed on, and power down the tablet. (A full power off - not just standby.) You'll notice that your tablet really isn't fully powered down, as there's a battery icon smack in the middle of the screen. It's in a "low power mode", and "adb" can still talk to it. Use adb to send the following command: "adb reboot recovery". You'll end up in recovery.
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 "t689_factory_recovery.img"
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 20111213:
* 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...
* Issues with getting into recovery are resolved. (after this update, you shouldn't need to use adb while the tablet is powered down.)
Here's the link for the recovery/root .zip (for the tmobile SGH-689)
version 20111213: http://www.mediafire.com/download.php?oro674o2881kw54
old versions:
version 20111206: http://www.mediafire.com/download.php?07ucaimq8qs6q05
Take care
Gary
uploaded and available. (message is to mark the thread as unread and as a place-holder for future notes.)
Your donation note is cool, man.
Just flashed update. It works fine I have root everything works the same installed superuser from market. Great work now all we need is a nice ICS ROM and voodoo
Sent from my SGH-T869 using XDA App
I wonder if tmobile would let me borrow one of these for a couple days so I can test some updates to the recovery.
"Hello, welcome to T-Mobile. Can I help you?"
"Yes, I'd like to quietly sit over there and attach my notebook computer to one of your demo tablets for about an hour to test voiding the warranty by flashing in low-level tools that, among other things, will allow anyone to bypass all the silly locks you people put on these devices. Oh, and I'm not a tmobile customer (and probably never will be.) Okay?"
heh
CSR: sure, go right ahead. Could you root it and install a custom ROM while your at it.. we've been getting tired of looking at this same old spoon fed sammy touchwiz and samsung apps nobody uses. Overclock the snot out of it.
just kidding, back on topic..
@garyd9 I'll get the updated recovery stuff tested tonight.
Updated and a new link posted in the OP.
Thanks to shadejinx for testing.
Changes for 20111213:
* 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...
* Issues with getting into recovery are resolved. (after this update, you shouldn't need to use adb while the tablet is powered down.)
garyd9 did this work blind and it worked perfectly the first time... I am very impressed. Anyone who reads this needs hit the thanks button on the OP.
garyd9 said:
* 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.
Click to expand...
Click to collapse
Where have you seen this?
rxxt said:
Where have you seen this?
Click to expand...
Click to collapse
I used the magic "search" function in XDA. It's a really cool feature of the site that lets you press a button, type a few letters, and find things.
Even if you aren't capable of using that function (and quite a few people are search-impaired for some reason), or if you might be searching for the incorrect term (I've done that myself a few times) you can always search manually. That involves opening threads and reading through them (not just the first post!)
I know that if I were looking for a firmware image, the DEV subforum thread marked with "Official FIRMWARES" would catch my attention, and I'm sure I'd find something useful if I spent a minute scanning through the thread that's less than 30 posts long. (That's a hint, by the way. I absolutely refuse to provide a direct link.)
Good hunting!
Gary
Sry, it was exactly the search function there do that I found this thread, but now I can see that it is too 'Galaxy Tab Plus', it was only 'Galaxy Tab' that Iam looking for, therefore the misplaced question..
(first the original reply)
rxxt said:
Wow, is it really true .. You have really savedmy day, damn well you tell me about the search option, otherwise I never havefound it, I can not thank you enough, what would we do without people likeyou..
Click to expand...
Click to collapse
Alas, 'tis true that some folk could never get along without those of us who point out the obvious.
(and now the current edited version)
rxxt said:
Sry, it was exactly the search function there do that I found this thread, but now I can see that it is too 'Galaxy Tab Plus', it was only 'Galaxy Tab' that Iam looking for, therefore the misplaced question..
Click to expand...
Click to collapse
Thank you for making my point.
edit: Please don't take my sarcasm personally. It's how I keep sane.
Take care
Gary
With the release of ICS, and seeing that others have taken over carrying the torch for updated and more modern versions of CWM Recovery, I'm no longer going to be supporting this release.
I'll leave the thread intact, but request that it be locked.
Oh, and I am still around, but I'm giving my Galaxy Tab 7.0 Plus to my wife. The stock firmware is actually very good for her, and she doesn't demand the amount of control over a tablet that I want.
Take care
Gary
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!