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

[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 only boots in recovery mode P3110

I have a Galaxy Tab 2 7'' Wifi (P3110) with CM 10.1.3.
Thing is, I wanted to install the latest nightly, so I booted in Recovery mode, tried to install the zip file and I had a Status 7 error. So after that I decided to stay with my CM version, but when I try to boot the tablet it goes to recovery mode and doesn't boot! I tried to wipe everything and still. I can't flash anything else (not even the CM version I already have) because I keep getting the Status 7 error.
I am desperate, I don't know what to do!

Well, you attempted to flash CM11/Omni with the wrong recovery, that's why you got the "Error 7"
Anyway, the problem should be easy to rectify.
1. Install ODIN3 on your computer (don't forget to also install the Samsung USB drivers as well).
EDIT In case you are about to install the drivers by installing "Kies" ... make SURE that NONE of the Kies components are running in the background (on Windows) once you try to flash with ODIN3 - or it won't work. If you Google around for a bit, there are several Downloads for JUST the USB drivers - I can upload you the USB drivers installer I used for my P3110 (flashed back to Stock to sell it off)) /EDIT
2. Download the correct .tar.md5 recovery file for the ROM you're going to use from Android Andi's file repository.
For CyanogenMod 11 you want to grab either PhilZ Touch or CWM Swipe Edition, for OMNI you want to grab TWRP.
3. Start ODIN3 and select the <recovery>.tar.md5 as a PDA file (make sure that nasty checkmark at "Repartition" is NOT checked"!)
4. Power on the tablet and make sure you get it into Download Mode
If it boots into Download Mode itself, that fine. If not just press... was it Power + VOL Down?... until you see the screen telling you to pres VOL up to proceed into Download Mode.
5. Connect the tablet to the computer (wait a second in case Windows decides to install the driver)
6. Flash the recovery
7. Disconnect after flash, jump into the recovery, flash CM11 or OMNI
Of course you can also flash back to Stock ROM (given you have the ODIN flashable tar.md5 at hand), verify that it boots after flashing, get into download mode, flash the custom recovery, flash the custom ROM.

BoneWithABeagle said:
Well, you attempted to flash CM11/Omni with the wrong recovery, that's why you got the "Error 7"
Anyway, the problem should be easy to rectify.
1. Install ODIN3 on your computer (don't forget to also install the Samsung USB drivers as well).
EDIT In case you are about to install the drivers by installing "Kies" ... make SURE that NONE of the Kies components are running in the background (on Windows) once you try to flash with ODIN3 - or it won't work. If you Google around for a bit, there are several Downloads for JUST the USB drivers - I can upload you the USB drivers installer I used for my P3110 (flashed back to Stock to sell it off)) /EDIT
2. Download the correct .tar.md5 recovery file for the ROM you're going to use from Android Andi's file repository.
For CyanogenMod 11 you want to grab either PhilZ Touch or CWM Swipe Edition, for OMNI you want to grab TWRP.
3. Start ODIN3 and select the <recovery>.tar.md5 as a PDA file (make sure that nasty checkmark at "Repartition" is NOT checked"!)
4. Power on the tablet and make sure you get it into Download Mode
If it boots into Download Mode itself, that fine. If not just press... was it Power + VOL Down?... until you see the screen telling you to pres VOL up to proceed into Download Mode.
5. Connect the tablet to the computer (wait a second in case Windows decides to install the driver)
6. Flash the recovery
7. Disconnect after flash, jump into the recovery, flash CM11 or OMNI
Of course you can also flash back to Stock ROM (given you have the ODIN flashable tar.md5 at hand), verify that it boots after flashing, get into download mode, flash the custom recovery, flash the custom ROM.
Click to expand...
Click to collapse
Thanks! I didn't know that was a recovery problem!
Somehow I couldn't reboot into Download mode with the key combo so I used ADB for that, and flashed the new recovery with Heimdall (in the CMW official website the versions are old, maybe that was the problem...).
Then I installed CM.
Thanks again!

ultrachilled said:
Somehow I couldn't reboot into Download mode with the key combo so I used ADB for that
Click to expand...
Click to collapse
I am aware you managed to flash the ROM, but just as a hint about "this is a trap for young players":
IF your tablet is connected to the wall wart (power supply) or to the USB port of computer while trying to trigger the key-combo to hop into download mode or recovery it won't work! Your tablet needs to be _disconnected_!

Update Recovery!
hey you can try update your custom recovery to latest version by downlading the zip file here http://forum.xda-developers.com/showthread.php?t=2548257
and than try re-flash your current rom or any kitkat room for your device

Not able to install - always standard recovery menu

Hello guys.
Im struggeling to install a custom ROM at the stage of installing a CWM recovery. My S2 plus 9105p runs Android 4.2.2 and everytime I try to upload a recovery img via Odin everything works fine as expected but when I try to start (volume up, home, power) the recovery mode - it gets always into the standard Android one - not CWM recovery!!! It looks like Samsung has integrated some kind of security mechanism which keeps us from running custom ROMs...
I have realy tried maybe 5 different recovery images, but non of those worked for me.
Can you please help?
THX

try flashing the files used in this guide

karamancho said:
try flashing the files used in this guide
Click to expand...
Click to collapse
I tried exactly also this particular site and steps described on it, but didn't help... The same problem. Everything was OK, but recovery was not CWM but standard Android one.

When u have flashed ur recorvery, take ur battery out and then plug battery again. And now go to recorvery.

Now it is WORKING !
Hi guys.
I followed the step-by-step guide on this page:
http://forum.xda-developers.com/showthread.php?t=2560928
- used the CWM 6.0.4.5 and Odin3 0.7
- after successfull flash of the PDA with this recovery (manualy unset the auto-reboot option) I have pulled the battery out for a couple of seconds
- the battery came back in again and with home-volUP-Power I got directly to the new CWM recovery.
So thanx all for your support and you can lock this thread as everything is working now.
DETAILED STEPS FOR INSTALLING CWM RECOVERY IF THE PHONE AUTOMATICALLY RE_FLASHES IT:
Installation
WITH ODIN
1. Be sure, that your device is on 4.2.2 stock firmware and shut down the phone
2. Be sure that Samsung drivers are installed on your pc. Just install Kies or google for them
3. Download Odin 3.07(google it) and the CWM-Recovery image (in this case CWM 6.0.4.5 )
4. Open Odin as administrator
5. Start-up the phone by pressing Vol_DOWN + Home + Power so you get into the flash-menu.
6. After reading the disclaimer and warning stuff - simply press Vol_UP and plug the USB cable to the PC and Phone
7. In ODIN click on PDA and select the downloaded CWM-recovery (*filename*.tar.md5) . Check - "F. Reset Time" and UNCHECK!! -> "Auto Reboot"
8. Click start and wait until the blue progress bar in your device is graphicaly 100% (I also suggest to wait another minute to make things sure..)
9. Pull out the battery
10. Pull out the uSB cable from PC and phone
11. Wait abou 10-15 seconds and power up your phone to get into the recovery menu by pressing: Vol_UP + Home + Power
12. DONE

[Solved]GT P3110 stuck in recovery mode, Not detected in ODIN, No APK recovery

I was trying a new ROM after installing mobile odin (pro) and superSu. However after failed installation the tab is restarting in recovery mode only ( screen shot attached). It is neither detected by odin nor can I install any apk as it is not booting further. I have wiped all data and caches and also have the recovery image (cwm and one supplied by mobile odin) but both are showing signature verification failed due to stock <3e>. So if somehow I can bypass the signature verification , I can load the backup. In short--
1. Tab not detected in PC ( via ODIN) , which was perfectly detected earlier. So no method via PC possible.
2. Tab not going beyond recovery mode, so no APK installation is possible.
3. It can read from SD card in recovery mode , but every image ( I know they are good, as used them earlier) is showing " Signature verification failed" and aborting.
4. I have a working CWM image but cannot install it due to reason 3 ( probably <3e> is the culprit).
I have searched the forum as far as I could but found all solutions are either PC based or APK based.

When you are in recovery, is the tab detected via adb from pc?

bukaida said:
I was trying a new ROM after installing mobile odin (pro) and superSu. However after failed installation the tab is restarting in recovery mode only ( screen shot attached). It is neither detected by odin nor can I install any apk as it is not booting further. I have wiped all data and caches and also have the recovery image (cwm and one supplied by mobile odin) but both are showing signature verification failed due to stock <3e>. So if somehow I can bypass the signature verification , I can load the backup. In short--
1. Tab not detected in PC ( via ODIN) , which was perfectly detected earlier. So no method via PC possible.
2. Tab not going beyond recovery mode, so no APK installation is possible.
3. It can read from SD card in recovery mode , but every image ( I know they are good, as used them earlier) is showing " Signature verification failed" and aborting.
4. I have a working CWM image but cannot install it due to reason 3 ( probably <3e> is the culprit).
I have searched the forum as far as I could but found all solutions are either PC based or APK based.
Click to expand...
Click to collapse
Signature verification fails because you are on stock recovery. Also have you tried booting in to download mode then plugging the USB cable to your tablet, then pressing volume up to start the download mode, then plugging the other end to your PC while odin is running? It should get detected

Power+ Vol up and Power + Vol down both are going to recovery mode. Plus getting an error 'logo_espresso7.jpg' draw failed at initial screen. Is there any <3e> compatable recovery without signature verification failed that can be run from sd card directly?
Ps: This happened when I tried to install "crdroid-5.1.1-20151103-p3110" via mobile ODIN pro.
The Tab is not detected in ADB server either.

bukaida said:
Ps: This happened when I tried to install "crdroid-5.1.1-20151103-p3110" via mobile ODIN pro.
Click to expand...
Click to collapse
The rom was meant to be installed with twrp or other custom recovery and not via mobile odin.

john99ap said:
The rom was meant to be installed with twrp or other custom recovery and not via mobile odin.
Click to expand...
Click to collapse
Yeah, the fault is mine, lack of knowledge. But what now? Can I recover my Tab ?
please help.

[Solved Problem]
The problem is solved. I finally could figure out that the culprit was the external volume down key ( not letting me go to download mode). So I opened the back cover as the last option and press the soft points corresponding to volume down and power together with two tooth-peaks. And voila , it issued the warning screen, and pressed up and it went to download mode. Connected with odin, flashed and load cwm recovery . Now that <3e> kernel is also gone.
Ps. It was weird about the Vol key behavior as it was working fine in both side in recovery mode during selection.

bukaida said:
The problem is solved. I finally could figure out that the culprit was the external volume down key ( not letting me go to download mode). So I opened the back cover as the last option and press the soft points corresponding to volume down and power together with two tooth-peaks. And voila , it issued the warning screen, and pressed up and it went to download mode. Connected with odin, flashed and load cwm recovery . Now that <3e> kernel is also gone.
Ps. It was weird about the Vol key behavior as it was working fine in both side in recovery mode during selection.
Click to expand...
Click to collapse
if you want to install the latest roms, you should update to the latest common twrp from android-andi http://andi34.github.io/recoveries_tab2.html
cwm recovery is outdated and causing issues with the latest roms

Is twrp safe to run from mobile odin? Will it automatically overwrite installed cwm?

bukaida said:
Is twrp safe to run from mobile odin? Will it automatically overwrite installed cwm?
Click to expand...
Click to collapse
install twrp as zip with your current cwm. its the easiest way. twrp will replace cwm, yes.