Database Info

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

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

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

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

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

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

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

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

international p6200

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

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

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

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

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

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

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

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

__________________

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

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

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

ROM Manager has killer my TF101!

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

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

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

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

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

[Q] Unfortunately Launcher has stopped and other issues

Hi guys,
I've been reading you for a while, but this is actually my first post.
Currently stuck with a "Unfortunately, Launcher has stopped" on my tablet, with no access to any menus except my Settings. The menu bar (back, home and multitasking) is now gone. I've got my keyboard to navigate, but something in the display is also quite wrong, image seems to be zoomed, or set at the wrong resolution. Tried to search on the forum, but all posts found were not about the same rom or the same issue. Sorry if I missed one.
Here's a little background story:
I've rooted my TF300T about a month ago and installed Hydro 4.1. It has been working very well since then, but in the last days, I thought that my tablet felt a little slower than usual, so I started searching if an update to 4.2 was available.
I'm not sure if this is what caused the issue or not, but I went into my "Power button" menu and went into "Recovery" mode (instead of Shutdown, reboot, etc.), which then restarted my unit into TWRP menu.
I then selected the "System" submenu and simply touched "Reboot". (terms might not be exact). At the first reboot, I got the problems that I described.
Can't do much, popup keeps appearing on my screen. I haven't tried yet to clear the cache of my Launcher, which I'm trying to avoid as I would prefer to avoid rearranging 5 pages of icons, but between that and reinstalling everything, obviously I prefer to simply lose my display preferences.
Can anyone help me about what caused my issue, and what can I do now?
Here are 2 screenshots that I took, showing that my bottom menu is missing and that the fonts aren't set right (clock and left icon). Also, my notifications menu now appears near the middle of my screen.
EDIT: I unfortunately cannot post links yet
I remember installing an app (with root access) that gave me a menu about my resolution. One thing that I'm wondering, could it be that the resolution got changed and I simply never rebooted since the change, which now caused my Launcher to crash? How can I launch an app without having access to the app menu?
Thanks in advance for your help.

irepressed said:
Hi guys,
I've been reading you for a while, but this is actually my first post.
Currently stuck with a "Unfortunately, Launcher has stopped" on my tablet, with no access to any menus except my Settings. The menu bar (back, home and multitasking) is now gone. I've got my keyboard to navigate, but something in the display is also quite wrong, image seems to be zoomed, or set at the wrong resolution. Tried to search on the forum, but all posts found were not about the same rom or the same issue. Sorry if I missed one.
Here's a little background story:
I've rooted my TF300T about a month ago and installed Hydro 4.1. It has been working very well since then, but in the last days, I thought that my tablet felt a little slower than usual, so I started searching if an update to 4.2 was available.
I'm not sure if this is what caused the issue or not, but I went into my "Power button" menu and went into "Recovery" mode (instead of Shutdown, reboot, etc.), which then restarted my unit into TWRP menu.
I then selected the "System" submenu and simply touched "Reboot". (terms might not be exact). At the first reboot, I got the problems that I described.
Can't do much, popup keeps appearing on my screen. I haven't tried yet to clear the cache of my Launcher, which I'm trying to avoid as I would prefer to avoid rearranging 5 pages of icons, but between that and reinstalling everything, obviously I prefer to simply lose my display preferences.
Can anyone help me about what caused my issue, and what can I do now?
Here are 2 screenshots that I took, showing that my bottom menu is missing and that the fonts aren't set right (clock and left icon). Also, my notifications menu now appears near the middle of my screen.
EDIT: I unfortunately cannot post links yet
I remember installing an app (with root access) that gave me a menu about my resolution. One thing that I'm wondering, could it be that the resolution got changed and I simply never rebooted since the change, which now caused my Launcher to crash? How can I launch an app without having access to the app menu?
Thanks in advance for your help.
Click to expand...
Click to collapse
What you describe is likely caused by changing the resolution. Are you still running hydro 4.1?
You can likely recover by replacing your build.prop or editing the one you now have. build.props are usualy rom specific so you need one from the rom you are using.

tobdaryl said:
What you describe is likely caused by changing the resolution. Are you still running hydro 4.1?
You can likely recover by replacing your build.prop or editing the one you now have. build.props are usualy rom specific so you need one from the rom you are using.
Click to expand...
Click to collapse
Yes, still using Hydro 4.1. I do have a build.prop editor installed on my tablet, but since I can't launch app, I don't know how to do it.
I'll try to connect the tablet to my PC and see if I can get access to my file from there.
Thanks!

irepressed said:
Yes, still using Hydro 4.1. I do have a build.prop editor installed on my tablet, but since I can't launch app, I don't know how to do it.
I'll try to connect the tablet to my PC and see if I can get access to my file from there.
Thanks!
Click to expand...
Click to collapse
I'm presently downloading 4.1 hydro to retrieve the build.prop. If you unzip it the build.prop is /system/build.prop also located there on your tab. I have another fifteen minutes to download if you wish for me to supply the file!

tobdaryl said:
I'm presently downloading 4.1 hydro to retrieve the build.prop. If you unzip it the build.prop is /system/build.prop also located there on your tab. I have another fifteen minutes to download if you wish for me to supply the file!
Click to expand...
Click to collapse
If you could, I would appreciate it!
Only thing left, how can I send the file to my TF300T without access to my apps? I'm currently trying to cheat by opening my apps using the Share feature with screenshots taken, but so far, no success.

irepressed said:
If you could, I would appreciate it!
Only thing left, how can I send the file to my TF300T without access to my apps? I'm currently trying to cheat by opening my apps using the Share feature with screenshots taken, but so far, no success.
Click to expand...
Click to collapse
We should be able to push with adb, set permissions, and reboot.
---------- Post added at 04:58 PM ---------- Previous post was at 04:36 PM ----------
http://www.mediafire.com/?tk3cifzci0vw24e
place the build.prop from the zip file into the directory with fastboot.
Open terminal or cmd in the directory with fastboot.
Boot into twrp – twrp provides adb access by default.
Use twrp mount menu and check mount system.
Then type
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
in twrp reboot system
type
adb kill-server

tobdaryl said:
We should be able to push with adb, set permissions, and reboot.
---------- Post added at 04:58 PM ---------- Previous post was at 04:36 PM ----------
place the build.prop from the zip file into the directory with fastboot.
Open terminal or cmd in the directory with fastboot.
Boot into twrp – twrp provides adb access by default.
Use twrp mount menu and check mount system.
Then type
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
in twrp reboot system
type
adb kill-server
Click to expand...
Click to collapse
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?

irepressed said:
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
Click to expand...
Click to collapse
Ok, I just killed my adb.exe, tried the command again and that got rid of the out of date error.
But, still stuck with the "device not found".

irepressed said:
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
Click to expand...
Click to collapse
Slowdown, I'm getting behind. I'm willing to help but you are now worse off than before.
Sit tight for five minutes and I'll try to give you a twrp flashable zip for your build.prop and hope that is the extent of the damage.
If not we'll try to go from there.
http://www.mediafire.com/?ybplc1ws8uvskhf
This is a twrp flashable zip that only replaces your build.prop with the one from hydro 4.1.

tobdaryl said:
Slowdown, I'm getting behind. I'm willing to help but you are now worse off than before.
Sit tight for five minutes and I'll try to give you a twrp flashable zip for your build.prop and hope that is the extent of the damage.
If not we'll try to go from there.
This is a twrp flashable zip that only replaces your build.prop with the one from hydro 4.1.
Click to expand...
Click to collapse
Alright, I'll wait for your answer before trying anything else.
So now, I've got your latest .zip file.
Still can't see my TF300T from my PC, so, ADB is a no go for now.
In fact, I do see it in the Device Manager, but since my last reboot, it now shows an exclamation mark on it as if my drivers weren't good.
Since you mentioned the file is a flashable zip, I'm guessing that I can flash it using TWRP without going through my PC?
Can you give me precise info on that, since I do not want to mess with my system more than I already did.
Thanks

irepressed said:
Alright, I'll wait for your answer before trying anything else.
So now, I've got your latest .zip file.
Still can't see my TF300T from my PC, so, ADB is a no go for now.
In fact, I do see it in the Device Manager, but since my last reboot, it now shows an exclamation mark on it as if my drivers weren't good.
Since you mentioned the file is a flashable zip, I'm guessing that I can flash it using TWRP without going through my PC?
Can you give me precise info on that, since I do not want to mess with my system more than I already did.
Thanks
Click to expand...
Click to collapse
Look at the bottom of my previous post. You will find a new link there. Just flash with twrp and reboot. Don't worry about wiping or any of that, just flash and reboot.

tobdaryl said:
Look at the bottom of my previous post. You will find a new link there. Just flash with twrp and reboot. Don't worry about wiping or any of that, just flash and reboot.
Click to expand...
Click to collapse
Yep, that's the file I was talking about.
I now need to flash and reboot, your file is at the root of an SDcard in my TF300T, I go through the Install menu and then, can't seem to view the content of my sdcard. Tried to mount it first but can't select it either, it will simply stay on "Internal Storage".
EDIT: The RCK icon is the only one right now that boots me into something. If I try the USB icon, it just stays on that screen forever.

Trash the two zips you have downloaded. I'm providing a new one for when we get back to that point. And there will be no doubt about which zip you are using.
http://www.mediafire.com/?hagehu5qu5ky6sf
OK. First I'll explain your earlier comment about adb being old. Twrp expects a recent adb or refuses to allow adb access ( we'll not worry at the moment about that but it is something you need to address later (I hope).
If you have a cord between your tablet and pc remove it. The sdcard may be mounted as data on the pc and not allow twrp to mount it.
You have been using this sdcard prior to this exercise?
Do you have any backups or flashable zips or anything of that nature on your internal sdcard?
If so what?

tobdaryl said:
Trash the two zips you have downloaded. I'm providing a new one for when we get back to that point. And there will be no doubt about which zip you are using.
OK. First I'll explain your earlier comment about adb being old. Twrp expects a recent adb or refuses to allow adb access ( we'll not worry at the moment about that but it is something you need to address later (I hope).
If you have a cord between your tablet and pc remove it. The sdcard may be mounted as data on the pc and not allow twrp to mount it.
You have been using this sdcard prior to this exercise?
Do you have any backups or flashable zips or anything of that nature on your internal sdcard?
If so what?
Click to expand...
Click to collapse
Zips trashed, kept only the one provided in your latest answer.
No cord between PC and tablet. Still unable to click on "Using external SD" or "Mount SDCard". It simply won't let me check the box or switch the bullet.
As for using this SDcard before, yes in a PC, but no, first time in my Asus. Also tried with another one just in case and same result.
As for backups and flashable zips, I kept everything from when I did my root and rom install.
I do know that I have a backup in the Restore menu of TWRP, which seems about the time I installed it. I suppose I could simply do a restore and avoid additional headaches, but my question is, what exactly will it restore? At this point, I'm mentally prepared to go back to what I had after installing Hydro 4.1, as long as I can use the tablet ASAP.

Asap = restore your backup.
If I'm restoring a different rom I'll wipe Cache, Dalvik Cache, and Factory Reset. If the backup is from the same rom I'm flashing and I want to keep the apps I have Installed since the backup I won't Factory Reset.
Good Luck!

tobdaryl said:
Asap = restore your backup.
If I'm restoring a different rom I'll wipe Cache, Dalvik Cache, and Factory Reset. If the backup is from the same rom I'm flashing and I want to keep the apps I have Installed since the backup I won't Factory Reset.
Good Luck!
Click to expand...
Click to collapse
So, I did the restore, and I'm up and running, but, no more Hydro 4.1. I guess my backup was probably what got done right before the installed it.
The good thing is, my tablet is working again and my root is still active. The bad part is that I'm gonna have to dig my head again in all the tutorials and try to find the best one.
Hey, I wanted to say a huge thank you for all your help, if it wasn't for guys like you, newbies like me would be stuck with useless thin computers.

irepressed said:
So, I did the restore, and I'm up and running, but, no more Hydro 4.1. I guess my backup was probably what got done right before the installed it.
The good thing is, my tablet is working again and my root is still active. The bad part is that I'm gonna have to dig my head again in all the tutorials and try to find the best one.
Hey, I wanted to say a huge thank you for all your help, if it wasn't for guys like you, newbies like me would be stuck with useless thin computers.
Click to expand...
Click to collapse
Great I'm glad you are happy. I had hoped for the outcome you expressed but this works also.
You're welcome!

[Q] Total noob wants help reverting to factory rom

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:

[Q] TF700 Stuck on Loading Screen

My Asus Transformer TF700 got stuck last night, and I can't start it since - it is stuck on the loading screen, where there is a spinning wheel under the Asus logo.
I tried factory resetting according to the following steps I found:
1) Holding the power + volume down buttons.
2) Navigating to the Wipe Data option using the volume down button.
3) Selecting and approving using the volume up button.
Then it said "Erasing" for a short period of time and restarted - back to the same loading screen.
Is there anything else I can do?

amitb83 said:
My Asus Transformer TF700 got stuck last night, and I can't start it since - it is stuck on the loading screen, where there is a spinning wheel under the Asus logo.
I tried factory resetting according to the following steps I found:
1) Holding the power + volume down buttons.
2) Navigating to the Wipe Data option using the volume down button.
3) Selecting and approving using the volume up button.
Then it said "Erasing" for a short period of time and restarted - back to the same loading screen.
Is there anything else I can do?
Click to expand...
Click to collapse
Are you pure stock?
No root, custom ROM, recovery?

berndblb said:
Are you pure stock?
No root, custom ROM, recovery?
Click to expand...
Click to collapse
Yeah, pure stock. Bought it almost two years ago and haven't made any modifications.

amitb83 said:
Yeah, pure stock. Bought it almost two years ago and haven't made any modifications.
Click to expand...
Click to collapse
Ok in that case your only option is to reflash the Asus firmware - provided you can still boot into recovery. But since you an get to the Wipe Data option in the bootloader, there's a good chance recovery still works.
The following is from Preatoriano's All-in-one guide from the General section , updated for current instructions:
1) Download the desired Asus stock firmware for your SKU (region) which would be 10.6.1.14.10 from Asus/support/downloads
2) Extract the .zip file somewere on your desktop (the result will be another .zip file,use it for step 3)
3) Rename the extracted archive to "EP201_768_SDUPDATE.zip" (without the " " and make sure file extensions are showing in Windows Explorer. You don't want to name the file EP_201_768_SDUPDATE.zip.zip) and upload it to a fat32 formatted MicroSD card
4) Insert the MicroSD card in your tablet and boot up by pressing Volume Down and POWER to get in to the bootloader menu. RCK should be flashing, push Vol Up to enter recovery.
The recovery should detect the sdupdate.zip and start to flash it. It probably reboots when it's finished, if it doesn't long press Power
Good luck

Hi, thanks for the reply.
I'm afraid this didn't seem to work. Could there be something I got wrong here?
- I downloaded the zip file here:
support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1 (can't post the link properly as a new user),
then selected Android and then the first option under Firmware (Version V10.6.1.14.10, 493MB, 2013.08.28 update).
- Extracted the zip file and renamed to EP201_768_SDUPDATE.zip (no double zip extension).
- Copied the file to a Micro SD card from an old Galaxy S2 phone, after formatting it.
- Inserted the SD card to the tablet, and pressed the power and volume down buttons until a menu appeared.
- Selected RCK using volume down.
What appears next is a brief "Installing System Update" message, and then a dead Android with the message "Error!" - which is what happened without the SD card as well.
Maybe the file should have been named something else or located within some folder?
More information regarding that menu:
At the upper left corner, the following text appears:
Android card hu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.10-20130801" A03
Key driver not found.. Booting OS

amitb83 said:
Hi, thanks for the reply.
I'm afraid this didn't seem to work. Could there be something I got wrong here?
- I downloaded the zip file here:
support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1 (can't post the link properly as a new user),
then selected Android and then the first option under Firmware (Version V10.6.1.14.10, 493MB, 2013.08.28 update).
- Extracted the zip file and renamed to EP201_768_SDUPDATE.zip (no double zip extension).
- Copied the file to a Micro SD card from an old Galaxy S2 phone, after formatting it.
- Inserted the SD card to the tablet, and pressed the power and volume down buttons until a menu appeared.
- Selected RCK using volume down.
What appears next is a brief "Installing System Update" message, and then a dead Android with the message "Error!" - which is what happened without the SD card as well.
Maybe the file should have been named something else or located within some folder?
More information regarding that menu:
At the upper left corner, the following text appears:
Android card hu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.10-20130801" A03
Key driver not found.. Booting OS
Click to expand...
Click to collapse
You have to download the firmware for your SKU or region! If you took the first version, you got the JP version which is for Japan :laugh:
You have to dwnld the WW (worldwide) version which is the second on the download page.
These files are signed and stock recovery checks that signature to make sure you install the correct SKU.
Follow the same steps with the correct firmware and it'll work

berndblb said:
You have to download the firmware for your SKU or region! If you took the first version, you got the JP version which is for Japan :laugh:
You have to dwnld the WW (worldwide) version which is the second on the download page.
These files are signed and stock recovery checks that signature to make sure you install the correct SKU.
Follow the same steps with the correct firmware and it'll work
Click to expand...
Click to collapse
Same behavior (an error message a couple of seconds after the "Installing System Update" comes up) when using the WW version
Is there any way to check if the SD card and the file were even recognized? Is it possible that the card isn't the right type somehow?.. (it's from a Galaxy S2 and it fits but feels a bit loose)

amitb83 said:
Same behavior (an error message a couple of seconds after the "Installing System Update" comes up) when using the WW version
Is there any way to check if the SD card and the file were even recognized? Is it possible that the card isn't the right type somehow?.. (it's from a Galaxy S2 and it fits but feels a bit loose)
Click to expand...
Click to collapse
Loose? You have to use your finger nail to push it in. You should clearly feel the spring load mechanism engage?
Card has to be fat32 formatted and update file not in any folder, top level of the card.
Is all that true?

berndblb said:
Loose? You have to use your finger nail to push it in. You should clearly feel the spring load mechanism engage?
Card has to be fat32 formatted and update file not in any folder, top level of the card.
Is all that true?
Click to expand...
Click to collapse
OK, that's a really weird one - although it really seemed to be the right type of card, I couldn't get it to "click in" properly no matter what.
So I ended up pushing it and holding it in while performing the reboot process - and it worked! Sat there for about five minutes without moving my finger, worried this might screw up the installation
Bottom line - the tablet seems alive and well now, thanks a lot for the help!

amitb83 said:
OK, that's a really weird one - although it really seemed to be the right type of card, I couldn't get it to "click in" properly no matter what.
So I ended up pushing it and holding it in while performing the reboot process - and it worked! Sat there for about five minutes without moving my finger, worried this might screw up the installation
Bottom line - the tablet seems alive and well now, thanks a lot for the help!
Click to expand...
Click to collapse
Phew! Makes me sweat just reading that! If your finger had slipped, you could have perma-bricked your tablet!!!
Kids - don't try this at home! :laugh:
But I'm glad you got it working again. End's well all swell... :highfive: