Database Info

[Q] No OTA for me and some noob questions

Hello,
I need some help to get the new ICS update. I have a TF101 (no G), serial B80, with firmware HTK75.WW_epad-8.6.6.23.
Previously I was on 8.6.6.19 and used razorclaw to root it. Then I have done the wipe data, and installed 8.6.6.23.
When I boot with Power and Vol- then Vol+ to enter RCK mode I get the green android guy with exclamation mark.
When I boot with Power and Vol-, then Vol+ I get 2 options: Wipe data and android cold boot.
I used some apps to test if the device is root and they say no.
Sorry for my english, but it's not my main language.
Any idea to fix this?

The 8.6.6.23 is firmware for the 3G model. You will not see OTA since ICS is not released for G model yet.
You can try to manually install 8.5.6.21. You could also try rooting and installing cwm recovery and flash the ICS ROM

Thanks for the answer. I've searched around and it seems that I can't get back to 8.5.6.21.
When I try to install it I get the android guy with exclamation point.
I guess I have to wait for ICS on 3G model

mantorrix said:
Thanks for the answer. I've searched around and it seems that I can't get back to 8.5.6.21.
When I try to install it I get the android guy with exclamation point.
I guess I have to wait for ICS on 3G model
Click to expand...
Click to collapse
Easiest way is to root, install CWM recovery and flash an ICS ROM. Either the stock rooted ROM or one of the many custom ROMs

I was in a similar situation. The ASUS recovery did not work for me either and I couldn't figure out how to install CWM. There is not a lot of help for noobs with B80s and with all the methods out there it was a challenge to find the correct one. Here's what I did:
1. If you are not rooted, follow the instructions in http://forum.xda-developers.com/showthread.php?t=1427838 to get rooted. I had updated to the .21 firmware, and at that point, the nachoroot method is the only option. I had some trouble connecting ADB, but eventually I got it to work. This was the most difficult part of the process.
2. Install CWM. I was having trouble with this using the ASUS recovery, and I think it has to do with B80 models. I found the app in this thread http://forum.xda-developers.com/showthread.php?t=1346180 and it is amazing. If you are rooted, it installs CWM even on the B80 versions. The custom recovery will allow you to install any rom.
3. Download the option B ROM from http://forum.xda-developers.com/showthread.php?t=1514658. Place the zip on your SD card. This rom is the ASUS stock ICS firmware with root. Contrary to what some have said--I noticed a huge difference with ICS!
3. Backup all your user apps and data with Titanium Backup (optional). Do not back up system data, just user apps if you want to keep them.
4. Open your recovery. Shut the tablet off, and boot into recovery by holding down the power button and the volume down button until you are prompted to boot into recovery by pressing volume up. Pressing volume up should load CWM.
5. Wipe and then install! To wipe, select "wipe" on the recovery menu. Then wipe all data, cache, and dalvik-cache. To install, select install zip from SD card and find the zip file you downloaded in step 3.
Best of luck!

Hi,
may i hook in here, i've got a similar problem:
i TRY to get in adb mode, but it doesn't work as expected:
i used this thread initially (ASUS Transformer Root ToolKit V7.1 Universal (Windows) | 2011-09-22), i downloaded the toolkit, connected my turned off tab to the pc, booted via Power + vol up, it got connected to windows and i installed the drivers. so far so good. BUT: if i start adb server and use adb device, i dont get any devices listed... i cant do anything. And when i use this nvflash method with the download.bat file, i get an error and the usb connection vanishes... i dont have any further ideas what to do. but i can boot afterwards normaly to 3.2.1, though i dont get any updates
any hints? Thanks for reading anyways
thanks, DK
[edit] i have the version HTK75.DE_epad-8.6.5.21-20111216 installed [/edit]

DreadKing said:
Hi,
may i hook in here, i've got a similar problem:
i TRY to get in adb mode, but it doesn't work as expected:
i used this thread initially (ASUS Transformer Root ToolKit V7.1 Universal (Windows) | 2011-09-22), i downloaded the toolkit, connected my turned off tab to the pc, booted via Power + vol up, it got connected to windows and i installed the drivers. so far so good. BUT: if i start adb server and use adb device, i dont get any devices listed... i cant do anything. And when i use this nvflash method with the download.bat file, i get an error and the usb connection vanishes... i dont have any further ideas what to do. but i can boot afterwards normaly to 3.2.1, though i dont get any updates
any hints? Thanks for reading anyways
thanks, DK
[edit] i have the version HTK75.DE_epad-8.6.5.21-20111216 installed [/edit]
Click to expand...
Click to collapse
What you did was put your tablet into APX mode. That's only good if you're doing NVFLash not ADB.
To use ADB just have yourtablet on like normal with USB debugging turn on

Hi,
thanks for your fast reply, you are right. i got my adb device id when beeing in the os, so this works. but, trying to use nvflash/Brk's Asus TF RootKit over apx, i got the initial connection, but when i want to flash it looses the connection or dies or something... no idea what
you got any hints how i can come back to a clean version, which is upgradable?
thx & best regards,
dk
this is the program output btw:
Creating backup of current boot and recovery img
this should take some time... please wait
Loading Bootloader to pad... please wait!
Starting...
Error! Could not load bootloader.
Click to expand...
Click to collapse

alexlarson011 said:
I was in a similar situation. The ASUS recovery did not work for me either and I couldn't figure out how to install CWM. There is not a lot of help for noobs with B80s and with all the methods out there it was a challenge to find the correct one. Here's what I did:
1. If you are not rooted, follow the instructions in http://forum.xda-developers.com/showthread.php?t=1427838 to get rooted. I had updated to the .21 firmware, and at that point, the nachoroot method is the only option. I had some trouble connecting ADB, but eventually I got it to work. This was the most difficult part of the process.
2. Install CWM. I was having trouble with this using the ASUS recovery, and I think it has to do with B80 models. I found the app in this thread http://forum.xda-developers.com/showthread.php?t=1346180 and it is amazing. If you are rooted, it installs CWM even on the B80 versions. The custom recovery will allow you to install any rom.
3. Download the option B ROM from http://forum.xda-developers.com/showthread.php?t=1514658. Place the zip on your SD card. This rom is the ASUS stock ICS firmware with root. Contrary to what some have said--I noticed a huge difference with ICS!
3. Backup all your user apps and data with Titanium Backup (optional). Do not back up system data, just user apps if you want to keep them.
4. Open your recovery. Shut the tablet off, and boot into recovery by holding down the power button and the volume down button until you are prompted to boot into recovery by pressing volume up. Pressing volume up should load CWM.
5. Wipe and then install! To wipe, select "wipe" on the recovery menu. Then wipe all data, cache, and dalvik-cache. To install, select install zip from SD card and find the zip file you downloaded in step 3.
Best of luck!
Click to expand...
Click to collapse
Thanks! This worked for me. Thank you sir! Everything worked fine and I'm now on ICS!

followed exactly alexlarson011's instruction and voila - it works! thanks a lot!
best regards
-dk

Semi-Bricked my TF101

Just picked up a TF101 and it had the Cryo (whatever it is called) OS with ClockworkMod Recovery v5.8.3.4. The OS didn't pick up wifi on the apps but it is on and logged into the router so I did a reset. Once I reset the TF101, i am stuck at CWM. It won't boot into any OS or anything else. I tried almost everything I found googling (this site and others) but nothing works. I did, however, got the TF drivers for my laptop so I can connect to it but I can't get the USB debug option on (of course).
So what are my options? how do I "unbrick" this thing? is this what some people call it soft-brick as it does boot but there just isn't any OS in there? I tried to put the OS zip file from Asus on a MicroSD but when I went to install zip from sdcard, it i can't get to the microSD to install it. it doesn't find it at all.
what can I do? what are the steps in unbricking this thing? I got this for my dad for father's day (chinese father's day which is TODAY...) and would like to get it to him.
Thanks in advance!

Is it in a CWM boot loop? Meaning when you reboot the tablet it keep going back to CWM?
Try this to see if you can boot OS.
Turn off tablet
Push and hold Vol down plus Power button
Wait till you see a screen that give you two options
Wipe data or Cold boot Linux
Choose Cold boot to boot into OS.

baseballfanz said:
Is it in a CWM boot loop? Meaning when you reboot the tablet it keep going back to CWM?
Try this to see if you can boot OS.
Turn off tablet
Push and hold Vol down plus Power button
Wait till you see a screen that give you two options
Wipe data or Cold boot Linux
Choose Cold boot to boot into OS.
Click to expand...
Click to collapse
still stuck in CWM. I held it down and no options came up except to push vol +. tried both and regardless of what i do, it just goes right back into the CWM menu. it seems there's no OS to this tablet anymore?
Is there something I can do via USB cable to flash a ROM in there?

chivas228 said:
still stuck in CWM. I held it down and no options came up except to push vol +. tried both and regardless of what i do, it just goes right back into the CWM menu. it seems there's no OS to this tablet anymore?
Is there something I can do via USB cable to flash a ROM in there?
Click to expand...
Click to collapse
If you have ADB working, you can push a ROM file to internal memory and flash it.
Alternatively you can NVFlash a compatible ROM.

baseballfanz said:
If you have ADB working, you can push a ROM file to internal memory and flash it.
Alternatively you can NVFlash a compatible ROM.
Click to expand...
Click to collapse
Sorry to sound ignorant but what's ad and what command (extra code after the .exe) do I add afterwards?

I'd try to flash a ROM via NVFLASH.
You may download it from here, but you must know if your TF101 is WW version, US version or any other. You must also know if your device is SBK1 or SBK2. That depends on the serial number. For example, mine starts by B50 and it's SBK1. If yours is SBK2 then you'll have to take a look at wheelie. If not, take a look here.
http://forum.xda-developers.com/showthread.php?t=1620758
However, I'm not responsible for any damage your device might suffer.
Take a look at that and tell me

here's the endall- easyflash version 0.8.3b whitekidneys just updated it and saved my brick. it'll save yours too. just install it on your computer, along with naked drivers 0.7, put the tf in apx, and flash. literally that easy.

Follow the link to easy flash / nvflash and follow the steps...
http://forum.xda-developers.com/showthread.php?p=26893961
Sent from my Transformer TF101 using xda app-developers app

i'm getting the CWM bootloop too, but i can do what was mentioned and get into the OS although it still boots into CWM on the next reboot. what can i do to fix the bootloop? not really fancying reinstalling yet again. but if i have to...

thefunkygibbon said:
i'm getting the CWM bootloop too, but i can do what was mentioned and get into the OS although it still boots into CWM on the next reboot. what can i do to fix the bootloop? not really fancying reinstalling yet again. but if i have to...
Click to expand...
Click to collapse
Try Install different recovery... download and flash the new recovery through CWM..
Sent from my Transformer TF101 using xda app-developers app

[Q] asus transformer sort semi brick need help asap please...

ok so ive had my tf101 rooted since i got the thing over a year and a half ago, i was running the megatron rom which was cm9 based and everything was good. today i tried to flash Eos4 and i got F%$ked out the a$$. so i did my standard procedure which was put the rom and gapps package on my device and then i wiped everything (after making a nandroid) and flash the rom along with its gapps. then i went to reboot it then i got shot back into recovery...so i was like wtf. i then found a way where if i hold the power and volume down for about 10 seconds i could cold boot android and once booted fix this problem with my recovery. unfortunately when i go to boot into android my device just bootloops on the boot animation ( ive left for about ten mins just to make sure) then i was like oh well ill just restore my nandroid, but for some reason clockwork mod touch wont let me use my microsd card, and its also not letting me restore from the backup i made earlier, it says files not found. i tried to connect it to my pc so i could just factory reflash it but unfortunately it will not be picked up by my pc through adb or apx.
so here is my main issue,
i just need to boot into android one time successfully so i can change the location of some ROM files and fix this stupid recovery bull****.
or if i could some how factory reset the tablet completely then that would be fine too
or or i could flash a different recovery that actually worked (currently on CWM 5.8.3.4 installed from rom manager which i realize now to be a huge mistake)
and i've tried ever tool on this forum as well and nothing works because it cannot pick up my device.
*** one other side note i am running windows 8 pro 32bit through Vmware (if this can be problematic)
thanks for any help in advance

To fix this, you will need to get your tablet recognized by your computer via ADB (in recovery) or APX mode.
You could have a bad cable, or it could be the VM causing the detection issues.
Is there a way you can connect it to a computer running Windows natively?
Does your computer make the new hardware sound when connecting?
Once you get it detected via one method or the other, here are my suggestions:
APX - Use the Naked Driver 0.72 and replace whatever driver is being used. Then use EasyFlasher to install TWRP 2.2.1.4 (it blows CWM away, and can read internal AND external memory)
ADB - use the Naked Driver 0.72 and replace whatever driver is being used. Then download the TWRP 2.3.2.3 blob from the TWRP project: http://techerrata.com/browse/twrp2/tf101
Call the downloaded file TWRP.blob.
Then run the following from your computer via ADB:
Code:
adb push TWRP.blob /sdcard/
adb shell
su
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
reboot
Make sure it is a normal reboot to complete the recovery. Then reboot to recovery and you should be able to see the external card (so long as it is formatted for FAT32).

Thanks for the quick response and it probably is because I am using vmware... Unfortunately I don't have access to a windows machine right now. But I will definitely try to find one
Sent from my SAMSUNG-SGH-I747 using xda premium

Ok so now it looks like this... All i did was flash some random ass jb rom I found in my cwm folder... It has been like this for about 15 mins
Sent from my SAMSUNG-SGH-I747 using xda premium
** edit I'm assuming it got stuck boot the apps because now a my directories seem F&#cked up too... It now goes sdcard/0/0/0/(everthing else)

That's because your recovery is not compatible with 4.2.1. TWRP recovery 2.3.2.3 or 2.3.3.x should be fine as federuco said, to fix the sdcard/0/0/... issue.
For the stuck at apps thing, usually it's because you didn't wipe everything when changing rom. Make sure to do a full reset, wipe cache dalvik and system.

Lethe6 said:
That's because your recovery is not compatible with 4.2.1. TWRP recovery 2.3.2.3 or 2.3.3.x should be fine as federuco said, to fix the sdcard/0/0/... issue.
For the stuck at apps thing, usually it's because you didn't wipe everything when changing rom. Make sure to do a full reset, wipe cache dalvik and system.
Click to expand...
Click to collapse
But my problem is I can't flash another recovery... I can't access the memory on my micro sd card... So like idk what to do
Sent from my SAMSUNG-SGH-I747 using xda premium

What happens if you reboot it after it is at the starting apps screen?
If you can get into the OS, install GooManager and install TWRP.

frederuco said:
What happens if you reboot it after it is at the starting apps screen?
If you can get into the OS, install GooManager and install TWRP.
Click to expand...
Click to collapse
I can't get into the os that's the problem... I just clean installed Windows via boot camp on my mac... Gunna try a few tools now... Hopefully I can get it back to stock... I'll update in a little bit
Sent from my SAMSUNG-SGH-I747 using xda premium

Ok so my computer can sort of detect it... I installed the drivers via brks root kit but when I plug it in in apx mode it says unknown device... Tried all my programs and they all failed...
Sent from my SAMSUNG-SGH-I747 using xda premium

Ok so I've tried to to reinstall the drivers... Tried to flash everything in apx and adb but it's not being properly detected By the PC... So I have no idea what to do at this point... If I could somehow either boot into android or flash TWRP
Sent from my SAMSUNG-SGH-I747 using xda premium

Use the Naked Drivers.
Let me find the link to the thread....
Here you go: http://forum.xda-developers.com/showthread.php?t=1514942
Grab the driver pack in the first thread, update the device using the APX driver when in APX mode.
Then you should be good to go. I have used EasyFlasher via APX with great success.

frederuco said:
Use the Naked Drivers.
Let me find the link to the thread....
Here you go: http://forum.xda-developers.com/showthread.php?t=1514942
Grab the driver pack in the first thread, update the device using the APX driver when in APX mode.
Then you should be good to go. I have used EasyFlasher via APX with great success.
Click to expand...
Click to collapse
Not to sound like a complete noob at this point but idk how to install these naked drivers
Sent from my SAMSUNG-SGH-I747 using xda premium

I think I installed the drivers right but idk can someone please like teamviwer or Google + hangout with me
Sent from my SAMSUNG-SGH-I747 using xda premium

Put your device in APX mode. To do so, make sure it's completely powered off (hold the power button 10 seconds), then hold down volume up + power for about 5 seconds. Do that while it's connected through USB. The screen will remain black so you won't see anything on the device, but you will hear a new device found in windows. Go in your device manager and look for either "unkown device" or "NVIDIA boot-recovery driver for mobile devices". If you see the nvidia one, right click and delete it; it should be come unknown. Right click the unknown device, install driver... navigate to where you extracted the naked drivers, and install.
Then use easyflasher.

Lethe6 said:
Put your device in APX mode. To do so, make sure it's completely powered off (hold the power button 10 seconds), then hold down volume up + power for about 5 seconds. Do that while it's connected through USB. The screen will remain black so you won't see anything on the device, but you will hear a new device found in windows. Go in your device manager and look for either "unkown device" or "NVIDIA boot-recovery driver for mobile devices". If you see the nvidia one, right click and delete it; it should be come unknown. Right click the unknown device, install driver... navigate to where you extracted the naked drivers, and install.
Then use easyflasher.
Click to expand...
Click to collapse
Not working... :/ I swear it's not me
Sent from my SAMSUNG-SGH-I747 using xda premium

[Q] Cannot install TWRP

I managed to root my TF101 using this thread:
http://forum.xda-developers.com/showthread.php?t=1689193
The problem is I TWRP is not installed.
When I press Volume Down + Power buttons and then The Volume Up, my device goes to a screen with 2 icons, "Wipe Data" and "Android" and after 10 seconds it boots to Android. I assume this is the stock recovery.
I Tried:
1) Both EasyFlashers (http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html)
2) Goo Manager
3) Terminal Mathod (http://teamw.in/project/twrp2/109)
All of them failed.
Is there anything else for me to try?

What were your steps when you tried using Easyflasher ?

I confirmed the device was in APX mode, through the device manager.
Run EasyFlasher.exe and chose the SBK1 (my TF101 is B60)
Chose "TWRP 2.2.1" and pressed Flash.
Everything seems to be working, since both in the command prompt and the device I get that the process was successful, but booting to recovery does not run TWRP, instead if goes to the screen I mentioned earlier.

lefterhs said:
I confirmed the device was in APX mode, through the device manager.
Run EasyFlasher.exe and chose the SBK1 (my TF101 is B60)
Chose "TWRP 2.2.1" and pressed Flash.
Everything seems to be working, since both in the command prompt and the device I get that the process was successful, but booting to recovery does not run TWRP, instead if goes to the screen I mentioned earlier.
Click to expand...
Click to collapse
Not sure it matters, but did you run Easyflasher as Admin ?
Ensure the correct APX drivers were installed ?
Reboot the TF once before trying to enter recovery ?
Held the Vol Down & Power from a powered off state until the white text appeared at the top of the screen, then hit volume up to enter RCK ?

*Detection* said:
Not sure it matters, but did you run Easyflasher as Admin ?
Ensure the correct APX drivers were installed ?
Reboot the TF once before trying to enter recovery ?
Held the Vol Down & Power from a powered off state until the white text appeared at the top of the screen, then hit volume up to enter RCK ?
Click to expand...
Click to collapse
1. Yes, I am administrator.
2. I used Universal Naked Drivers 0.72 from here:http://forum.xda-developers.com/showthread.php?t=1514942
3. Yes, after using any of the methods mentioned, I allowed it to reboot once normally.
4. Yes, I get the screen I mentioned with the Wipe Data/Android, when I press Vol Up after the Vol Down+Power combination.

When I say Run as Admin, I mean Right click the exe and choose Run as Administrator
I'd try using the drivers included in the Easyflasher bundle here (EDIT - Dev recommends the drivers you used anyway)
http://forum.xda-developers.com/showthread.php?t=1688012
As it uses APX this shouldn't matter, but make sure USB Debugging is enabled in Developer Options too and let it install the drivers while powered on and connected to the PC
I'd try another USB port too to rule that out
Which SBK/Serial is your TF?
EDIT -Another thought, are you running a stock ROM atm? Which one ?
You could try using Peri to flash TWRP
http://forum.xda-developers.com/showthread.php?t=1681155

I tried the Peri.
Continue? (Y/N) Y
Starting... This will take awhile...
9444+1 records in
9444+1 records out
4835404 bytes transferred in 2.385 secs (2027423 bytes/sec)
Done! You should see some reported #s above.
Now we reboot the TF again, you'll see a blue bar.
It will take awhile to fill, then you have recovery!
Click to expand...
Click to collapse
Unfortunately, I don't see any blue bar. The device just reboots to Android.
The serial is: B60KAS103665
Yes, I use the stock ROM, I never tried to install a custom ROM, until now.
IML74K.WW_epad-9.2.1.27-20120615
Actually, my goal is to install the KatKiss ROM using these instructions:
3w.transformerforums.com/forum/asus-transformer-tf101-development/33773-official-faq-katkiss-rom-formerly-teameos-4-android-4-2-x-tf101.html
Is there any other method, not using TWRP, to install KatKiss?
Update:
I also tried to install CM recovery, using the 3rd option of 1-Click Transformer Root. Again, I don't see anything to get installed (a blue bar is not showing) and it just reboots to Android.
Lately, I have a problem.
I get a "DMClient has stopped" error twice each time I turn the TF101 on. I think this is the ASUS update process. Can this be relevant?

lefterhs said:
I tried the Peri.
Unfortunately, I don't see any blue bar. The device just reboots to Android.
The serial is: B60KAS103665
Yes, I use the stock ROM, I never tried to install a custom ROM, until now.
IML74K.WW_epad-9.2.1.27-20120615
Actually, my goal is to install the KatKiss ROM using these instructions:
3w.transformerforums.com/forum/asus-transformer-tf101-development/33773-official-faq-katkiss-rom-formerly-teameos-4-android-4-2-x-tf101.html
Is there any other method, not using TWRP, to install KatKiss?
Click to expand...
Click to collapse
Your TF is SBK1, so should have no problem getting a custom recovery flashed to it, the only thing I'm wondering is if the stock ROM is causing problems, I seem to remember someone else with stock having problems getting a modern custom recovery flashed too
Unfortunately the only way to flash KatKiss is from custom recovery TWRP as the ROMs are released in flashable .zip format
Do you have another PC you could use to try and flash TWRP via Easyflasher ?
What OS are you running on your PC ?
At least one of the methods you have tried should have definitely worked, so long as the TF is in APX mode, the drivers are installed, and the PC can see the TF, Easyflasher should have done the job
I never recommend flashing CWM as it screws with JB ROMs, but it might be worth trying to flash that recovery first, then a custom ICS ROM, after that if you get that far, try installing TWRP again before trying to flash a JB ROM
Just make sure you don't flash a JB ROM with CWM recovery installed
---------- Post added at 12:42 PM ---------- Previous post was at 12:41 PM ----------
lefterhs said:
Lately, I have a problem.
I get a "DMClient has stopped" error twice each time I turn the TF101 on. I think this is the ASUS update process. Can this be relevant?
Click to expand...
Click to collapse
Hmm, you could try clearing the data / cache from DMClient in Settings > Apps > All
Code:
1. Settings
2. Applications
3. Running services
4. All
5. DMClient
6. Clear data
7. Force stop
8. Shut down and restart the tablet
Maybe there is an old update file stuck in cache causing problems
Have you tried factory resetting it 100% ?

I did a few things, at the same time.
1. Changed USB port.
2. Used the original EasyFlasher.
3. Cleared and force stopped the DMClient, which I believe did the trick.
Now, TWRP got installed, although It also did a hard reset to my device. When it opened, I had to setup the device like it was the first time I turn it on.
Anyway, I think I will continue to Kat Kiss installation now.
Thanks for your help.

lefterhs said:
I did a few things, at the same time.
1. Changed USB port.
2. Used the original EasyFlasher.
3. Cleared and force stopped the DMClient, which I believe did the trick.
Now, TWRP got installed, although It also did a hard reset to my device. When it opened, I had to setup the device like it was the first time I turn it on.
Anyway, I think I will continue to Kat Kiss installation now.
Thanks for your help.
Click to expand...
Click to collapse
Ah good news, yea it does sound as if the DMClient was stopping the install, Im not sure exactly how it works, but possibly if the TF thinks there is a pending update, it won't allow the flash until its cleared
Good thing you mentioned it, I was almost at a loss as to what was causing the problem
And yep, now you have it installed, make sure you are up to date 2.3.2.3 (Use GooManager to install the latest version), and then you can install any custom ROM you like from TWRP

lefterhs said:
I managed to root my TF101 using this thread:
http://forum.xda-developers.com/showthread.php?t=1689193
The problem is I TWRP is not installed.
When I press Volume Down + Power buttons and then The Volume Up, my device goes to a screen with 2 icons, "Wipe Data" and "Android" and after 10 seconds it boots to Android. I assume this is the stock recovery.
I Tried:
1) Both EasyFlashers (http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html)
2) Goo Manager
3) Terminal Mathod (http://teamw.in/project/twrp2/109)
All of them failed.
Is there anything else for me to try?
Click to expand...
Click to collapse
this has a beta twrp zip that is flashable, maybe help? http://forum.xda-developers.com/showthread.php?t=2308565

Hello,
I'm trying to install the MarshMallow 6.0.1 Release on my TF101 (SBK2 -BBxxxxx) with stock rom IMLK74K.WW_epad-9.2.1.27-20120615 and easyflasher (universal naked drivers installed correctly on windows 10). I can flash it correctly but I have the same problem as lefterhs.
I have also tried different version of twrp, latest easyflasher, different USB ports, with USB debugging on the device, still same problem, only choice is android and wipe data.
I have also tried with CWM but I had the error can't mount SD card. Rooted with 1-click transformer root. I begin to believe I will not be able to change the ROM. Any idea?
Thanks,
EDIT: Problem solved, managed to flash Roach CWM 5.5.0.4 from EasyFlasher and flash TWRP 2.8.1.1 from zip inside Roach CWM 5.5.0.4 recovery. Then followed the procedure in https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496. Katkiss is running on my tf101.
*Detection* said:
Ah good news, yea it does sound as if the DMClient was stopping the install, Im not sure exactly how it works, but possibly if the TF thinks there is a pending update, it won't allow the flash until its cleared
Good thing you mentioned it, I was almost at a loss as to what was causing the problem
And yep, now you have it installed, make sure you are up to date 2.3.2.3 (Use GooManager to install the latest version), and then you can install any custom ROM you like from TWRP
Click to expand...
Click to collapse

[Q] tablet not working properly

when i factory reset the tab and installed a rom. it started normally. i did everything normally and it showed google account manager has stopped.
so i tried going into CWM recovery mode but got me into stock recovery so factory reset the tablet and then tried wipe cache participation but shows error. I think that the problem is the cache and the dalvich. but i cant use usb debugging so i cant delete the cache and the dalvich.
:crying::crying::crying::crying::crying:
so does any body know how to fix this
thanks in advance :laugh:

Help cache partication error
yolo squad dodo said:
when i factory reset the tab and installed a rom. it started normally. i did everything normally and it showed google account manager has stopped.
so i tried going into CWM recovery mode but got me into stock recovery so factory reset the tablet and then tried wipe cache participation but shows error. I think that the problem is the cache and the dalvich. but i cant use usb debugging so i cant delete the cache and the dalvich.
:crying::crying::crying::crying::crying:
so does any body know how to fix this
thanks in advance :laugh:
Click to expand...
Click to collapse
Can anyone help me please!!!!!!!

yolo squad dodo said:
so i tried going into CWM recovery mode but got me into stock recovery
Click to expand...
Click to collapse
You are not reading what you are typing.
Obvious answer: If you end up in the STOCK RECOVERY you simply do not have a custom recovery installed (Clockworkmod as you wrote). Get yourself a copy of a recent recovery from AndroidAndi's download repository (TWRP, Clockworkmod Swipe, PhilZ Touch), and flash the .tar.md5 of the recovery with ODIN in download mode.
Obvious question: How did you flash a ROM, other than some OTA Stock Samsung update on the device itself, in the first place when you don't have a custom recovery installed in order to do so?
EDIT: What exactly do you mean by "factory reset"? Did you re-flash your tablet with a Stock ROM? If that's the case, then any custom recovery you had installed was wiped and replaced with the stock recovery. Hence why you now don't have a custom recovery anymore.

BoneWithABeagle said:
You are not reading what you are typing.
Obvious answer: If you end up in the STOCK RECOVERY you simply do not have a custom recovery installed (Clockworkmod as you wrote). Get yourself a copy of a recent recovery from AndroidAndi's download repository (TWRP, Clockworkmod Swipe, PhilZ Touch), and flash the .tar.md5 of the recovery with ODIN in download mode.
Obvious question: How did you flash a ROM, other than some OTA Stock Samsung update on the device itself, in the first place when you don't have a custom recovery installed in order to do so?
EDIT: What exactly do you mean by "factory reset"? Did you re-flash your tablet with a Stock ROM? If that's the case, then any custom recovery you had installed was wiped and replaced with the stock recovery. Hence why you now don't have a custom recovery anymore.
Click to expand...
Click to collapse
Odin won't recognise my tablet in Odin mode neither does my computer is there another to install a CWM recovery. By the the I do have back up on the phone if that helps.
By the way I am a noob

yolo squad dodo said:
Odin won't recognise my tablet in Odin mode neither does my computer is there another to install a CWM recovery. By the the I do have back up on the phone if that helps.
By the way I am a noob
Click to expand...
Click to collapse
Just to recap on the steps you should have done...
1. You downloaded the .tar.md5 of the recovery you want to install, from Android Andi's filehost, on your PC
2. You installed the Samsung USB drivers on your computer
3. You installed ODIN on your computer
4. You unplugged the tablet from the charger and powered it off
5. You took your tablet and HELD VOL-UP while you powered it back on (to get into bootloader mode)
6. You plugged the tablet in to the computer and waited for a moment while Windows was installing the driver
--- Here the story ends, according to what you wrote as you say ODIN does not find the tablet.
Well, are you sure you did the steps so far in that order? Can't be that ODIN doesn't detect the tablet when it's operational (read: no a total dead brick) and it's in download mode.
The ONLY problem possible: You installed Samsung KIES, and not just the USB drivers, on your computer. KIES interferes with ODIN. You need to exit ODIN, bring up the Task Manager (press CTRL+ALT+DELETE and select "Task Manager"), find "kies" and end the running process(es) - ignore any warning message.
If that's too complicated: Uninstall KIES and then find the "Samsung Mobile USB drivers" installation package ... with a bit of searching (just to assign some homework to you) you will the links right here in this forum section more than just once.
Once KIES is terminated, or uninstalled and just the USB drivers installed, start ODIN again ... now it should detect the tablet.
Once ODIN confirms that the tablet is detected...
7. Select the .tar.md5 of the recovery as the "PDA"
8. Flash the recovery. Once complete the tablet rebooted into the newly installed recovery.
As for on-device flashing. That's possible...
- Your installed ROM must be ROOTED (no root, no fun)
- You need Chainfire's "MobileODIN" (the free version from the Play Store would suffice), and you need to let MobileODIN install the "p311x flashkernel package" (I think with the free version you need to download it manually from Chainfire's thread and install it manually) - jump into Chainfire's thread and read on
Once you have Mobile ODIN installed it is just a matter of:
- Download the .tar.md5 of the recovery on your tablet once more (or transfer it over from your PC)
- Start Mobile ODIN
- Select the .tar.md5 of the recovery (should automatically be set as a "PDA")
- Flash and reboot into the recovery
However, as a fair warning ... as with every flashing of your device ... keep in mind something could go wrong (just to straighten it out that there's always room for user mistakes or murphy's law getting into the way ("Everything that can go wrong will go wrong"))

BoneWithABeagle said:
Just to recap on the steps you should have done...
1. You downloaded the .tar.md5 of the recovery you want to install, from Android Andi's filehost, on your PC
2. You installed the Samsung USB drivers on your computer
3. You installed ODIN on your computer
4. You unplugged the tablet from the charger and powered it off
5. You took your tablet and HELD VOL-UP while you powered it back on (to get into bootloader mode)
6. You plugged the tablet in to the computer and waited for a moment while Windows was installing the driver
--- Here the story ends, according to what you wrote as you say ODIN does not find the tablet.
Well, are you sure you did the steps so far in that order? Can't be that ODIN doesn't detect the tablet when it's operational (read: no a total dead brick) and it's in download mode.
The ONLY problem possible: You installed Samsung KIES, and not just the USB drivers, on your computer. KIES interferes with ODIN. You need to exit ODIN, bring up the Task Manager (press CTRL+ALT+DELETE and select "Task Manager"), find "kies" and end the running process(es) - ignore any warning message.
If that's too complicated: Uninstall KIES and then find the "Samsung Mobile USB drivers" installation package ... with a bit of searching (just to assign some homework to you) you will the links right here in this forum section more than just once.
Once KIES is terminated, or uninstalled and just the USB drivers installed, start ODIN again ... now it should detect the tablet.
Once ODIN confirms that the tablet is detected...
7. Select the .tar.md5 of the recovery as the "PDA"
8. Flash the recovery. Once complete the tablet rebooted into the newly installed recovery.
As for on-device flashing. That's possible...
- Your installed ROM must be ROOTED (no root, no fun)
- You need Chainfire's "MobileODIN" (the free version from the Play Store would suffice), and you need to let MobileODIN install the "p311x flashkernel package" (I think with the free version you need to download it manually from Chainfire's thread and install it manually) - jump into Chainfire's thread and read on
Once you have Mobile ODIN installed it is just a matter of:
- Download the .tar.md5 of the recovery on your tablet once more (or transfer it over from your PC)
- Start Mobile ODIN
- Select the .tar.md5 of the recovery (should automatically be set as a "PDA")
- Flash and reboot into the recovery
However, as a fair warning ... as with every flashing of your device ... keep in mind something could go wrong (just to straighten it out that there's always room for user mistakes or murphy's law getting into the way ("Everything that can go wrong will go wrong"))
Click to expand...
Click to collapse
odin recognize tablet and it got flash or what ever its called. it restarted but it didn't go into recovery but just restart as normal

I got it working by installing custom rom.
Thanks a lot by the way for the tips

yolo squad dodo said:
odin recognize tablet and it got flash or what ever its called. it restarted but it didn't go into recovery but just restart as normal
Click to expand...
Click to collapse
For future reference: keeping VOL DOWN UP held while powering on/rebooting the tablet takes you into the recovery in case you borked the system and selecting "Reboot" -> "Recovery" from within the _custom_ ROM's power menu is not an option (the Stock Samsung ROM does not have that option by default). Though keep in mind that this only works when the tablet is _NOT_ connected to the charger/computer ... when the USB cable is plugged in it seems to ignore the hardware keys.
yolo squad dodo said:
I got it working by installing custom rom.
Thanks a lot by the way for the tips
Click to expand...
Click to collapse
Great you got your recovery and custom ROM installed. Have fun.

BoneWithABeagle said:
For future reference: keeping VOL DOWN held while powering on/rebooting the tablet takes you into the recovery in case you borked the system and selecting "Reboot" -> "Recovery" from within the _custom_ ROM's power menu is not an option (the Stock Samsung ROM does not have that option by default). Though keep in mind that this only works when the tablet is _NOT_ connected to the charger/computer ... when the USB cable is plugged in it seems to ignore the hardware keys.
Great you got your recovery and custom ROM installed. Have fun.
Click to expand...
Click to collapse
Umm isn't recovery power and volume UP? At least that's how it is on my 7'' tablet and the 10'' I rooted and installed a ROM on.
jrc2
Sent from my T-Mobile S2 using Tapatalk

jrc2 said:
Umm isn't recovery power and volume UP? At least that's how it is on my 7'' tablet and the 10'' I rooted and installed a ROM on.
Click to expand...
Click to collapse
Now that you mention it... yes, you're right jrc... "VOL DOWN" == Download Mode / "VOL UP" == Recovery (I failed to recall the "UP as in update.zip" association).