Database Info

No Recovery, garbled screen, can I recover?

I rooted my TF101 model B80 using RazorClaw (nvflash is a no-go for this model). Installed CWM, all was well. I tried to install Prime ROM from CWM, and was unimpressed; tried to restore my Nandroid backup of original rooted OS. Now, Transformer will not boot into any recovery (neither CWM or original green android), and screen comes up garbled. Is there any way I can restore my original stock by merely putting a particular image on my external sd card?
Any other suggestions welcome, I just can't get to a screen (recovery or otherwise) where there is any readable text I can respond to. Nor can I turn the device off. It will continue to reboot in this fashion. When I get home today I'll be able to start from a dead battery.
Thanks

Did you wipe before restore?

davebugyi said:
Did you wipe before restore?
Click to expand...
Click to collapse
Yes, I did a full wipe including dalvik cache before all restores. At this point, though, my primary concern is just finding a path back to usability!

DIncLover said:
I rooted my TF101 model B80 using RazorClaw (nvflash is a no-go for this model). Installed CWM, all was well. I tried to install Prime ROM from CWM, and was unimpressed; tried to restore my Nandroid backup of original rooted OS. Now, Transformer will not boot into any recovery (neither CWM or original green android), and screen comes up garbled. Is there any way I can restore my original stock by merely putting a particular image on my external sd card?
Any other suggestions welcome, I just can't get to a screen (recovery or otherwise) where there is any readable text I can respond to. Nor can I turn the device off. It will continue to reboot in this fashion. When I get home today I'll be able to start from a dead battery.
Thanks
Click to expand...
Click to collapse
I had the same situation..I used the unbrick method:
http://forum.xda-developers.com/showthread.php?t=1123429
then you could try restore a backup ..
To turn off the device press the power button for 10-15 seconds..

bruuuno said:
I had the same situation..I used the unbrick method:
http://forum.xda-developers.com/showthread.php?t=1123429
then you could try restore a backup ..
To turn off the device press the power button for 10-15 seconds..
Click to expand...
Click to collapse
I can try this when I get home today.... I'm just concerned because the method involves nvflash .... which I thought didn't work from the newer TF models (I have a model B80). I needed to wait for the RazorClaw exploit because previous attempts at using nvflash failed....

Then NVFlash will fail still...

davebugyi said:
Then NVFlash will fail still...
Click to expand...
Click to collapse
So am I hopelessly hosed?

Sounds like this problem
http://forum.xda-developers.com/showthread.php?t=1321207&highlight=green+screen
Being you can't get back into CWM not sure how you'll flash the stock kernel.
HAve you tried Holding Vol Down button plus Power button till you get prompt to enter recovery at which time immediately push Vol up button withion 5 sec.

baseballfanz said:
Sounds like this problem
http://forum.xda-developers.com/showthread.php?t=1321207&highlight=green+screen
Being you can't get back into CWM not sure how you'll flash the stock kernel.
HAve you tried Holding Vol Down button plus Power button till you get prompt to enter recovery at which time immediately push Vol up button withion 5 sec.
Click to expand...
Click to collapse
OK .... my bad.... I guess I wasn't pressing the buttons in the right sequence/duration. I CAN get to CWM!
So, once again, I try to restore the Nandroid backup and after rebooting, end up with the screen situation as in the reference you provided.
So, I am assuming my Nandroid backup is not restoring the kernel that it needs. I was running a recent OTA update; I believe the version was 8.6.5.19.
Where can I get the appropriate kernel to install from CWM? Does it matter in what order I install the kernel and the Nandroid backup?

DIncLover said:
Where can I get the appropriate kernel to install from CWM? Does it matter in what order I install the kernel and the Nandroid backup?
Click to expand...
Click to collapse
Look here
http://www.gnufabio.com/revolver/dls/

Same issue, no recovery though
Hi,
I have the same issue as the original poster, B80 serial, RazorClaw root. However, when I boot to recovery I get the green android with yellow triangle and exclamation mark.
I need to restore a recovery on my device as I may need to unroot to send to Asus. I have an even deeper problem of having to have the device connected to power for it to turn on after shut down.
However my main question is for that serial number and root method, what is the best way to flash a recovery on my device (stock or CWM) if I can not get into recovery to begin with?
P.S. RecoveryInstaller will not work, after installing the apk, I click the flash recovery button, the system holds for a bit, then nothing happens.
I will continue to search the forms for some answers, any insights or direction will be appreciated.
I can get into apx mode.
Thank you community!

I think you can flash the recovery via the staging partition. Search around the TF section, it's in here somewhere. Although, I wonder why the 1 click recovery didn't work?

gee one said:
I think you can flash the recovery via the staging partition. Search around the TF section, it's in here somewhere. Although, I wonder why the 1 click recovery didn't work?
Click to expand...
Click to collapse
Everything I see in the forms requires one of several conditions which my TF doesn't currently meet.
1. Recovery. I can not go into any recovery, thus I can not perform any flashing of any other rom or recovery.
2. B70 or later. Because of the security in the boot for these new serials, I can not use the NVFlash tools to un-brick / flash.
I am already rooted, however I do not know the reason for lack of recovery on this device. I unfortunately bought it yesterday from Craigslist, so not sure what this guy did before I got it.
I searched for flashing recovery staging partition and did not find anything immediately relevant. Please advice is there is a different wording I should use in my search as I am now getting an immense download on all of this trying to figure out what to do. I am also fairly new to Android devices having 1 other phone that is rooted.
Thank you for all the support and quick response! wonderful community here.

Try searching for posts with /dev/block/mmcblk0p4
This is particularly dangerous because you don't have access to nvflash. If you get bootloops, it is bricked. You have to be sure that whatever you flash will be 100% compatible with what you have now.
Also, when you try to boot into recovery, what does the text at the top say? There should be a version number in there somewhere.
sent from my cyanogen(mod) vision

gee one said:
Try searching for posts with /dev/block/mmcblk0p4
This is particularly dangerous because you don't have access to nvflash. If you get bootloops, it is bricked. You have to be sure that whatever you flash will be 100% compatible with what you have now.
Also, when you try to boot into recovery, what does the text at the top say? There should be a version number in there somewhere.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Thank you gee one. I have since been able to install clockworkmod. My issue with the power not turning on if not plugged in still persists, I have started a separate thread.
I found your post on the staging partition here:
http://forum.xda-developers.com/showthread.php?t=1309949&highlight=power
Do you recommend this for the issue still persisting?
If so, considering I am on 8.6.5.19 will I have to use the blob from that? It is not on Asus website as I got it from the firmware update option in the settings before loading up my new ROM.
Do you recommend this step as the only resolution or is there another way?

Ok let me get this straight:
You have clockworkmod installed. Can you boot into it and do the buttons work?
Are you getting a garbled screen when you boot into the rom? Or are you just trying to unroot?
The tricky part is to avoid the bootloops of death.
sent from my cyanogen(mod) vision

Honestly what i would do if i were you, assuming i understood correctly that you can get into clockworkmod, just reflash the prime rom you didnt like(after wiping everything, including cache and dalvik), and if it boots and everythings okay, at least you know nothings really wrong with ur tablet. As for the plug in situation, make sure your battery isnt simply dead. As far as i know, it wont charge from recovery, so if uve been stuck without a booting rom for a while, it being dead could definitely be possible. Once you are in a working rom and you sorted out the charging issue, then you should worry about getting back to stock.

Thank you camaros,
I am able to load stock ROM successfully.
Battery is not dead as it is fully charged, and will run un tethered after powerup. I will test resetting it although I doubt that is causing it.
What i would like to determine is, is this related to a hardware or software issue?
Also, is there a way to restore stock recovery from CWM?

[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] [solved] Won't boot - No ADB, no CWM/, no "wipe data", no nvflash (c20 serial)

[Q] [solved] Won't boot - No ADB, no CWM/, no "wipe data", no nvflash (c20 serial)
Thanks for reading.
I recently bought a refurbished Transformer with a serial starting with c20. I rooted with vipermod, installed recoveryinstaller and AOKP. After being unable to install CWM (I now know why) my device became unable to boot into recovery. Recoveryinstaller would not install either. When I attempted to normal boot, the device would just hang. My only option was to cold boot into linux, which worked.
I then attempted to "full wipe" in order to re-install recoveryinstaller for access to recovery. After doing so, my Transformer no longer boots. It sits at the "Android" splash screen, which I believe is AOKP still attempting to load. Recovery doesn't boot, full wipe only beings me back to the "Android" splash, and cold booting into linux also returns me to the "Android" splash.
After lots of searching and reading, I found a few help threads that offered suggestions for those unable to boot, but they all require adb. My understanding based on the adb tutorial is that it requries configuration within the Android OS, and for the device to be running, which mine does not. And from what I've read, the c20 serial number isn't compatible with nvflash.
Can someone point me in the right direction? I feel like I'm at a dead end here. Thanks a bunch.
-Chris
edit: to clarify, I never setup ADB, which makes me think that solutions like this won't work: http://forum.xda-developers.com/showthread.php?p=25636698#post25636698

Hello cfbauer,
Did you try this driver pack? after 1st remove all you transformer drivers?
http://forum.xda-developers.com/showthread.php?t=1514942
If you install this, then you can check with adb if there is communication possible with your transformer. if you connect it, is there any life on your pc when you start your TF?
or volume + and power to put tablet in apx mode and see if then the apx driver installs. If it does then try the brks rootkit v7.1 to see if you can install cwm with this tool....maybe your refurbished TF is an old B40 to 70).
unless this is what you already did......
dont forget to disable spashtop and asys sync on your pc.......

Well I managed to get ADB setup, I think. I'm new to this, but when I attempt to boot into recovery, and do "adb devices" I get "0123456789ABCDEF offline".
I'm a little hesitant to try nlheiz's suggestion of brks rootkit v7.1 as it says it's for a serial number that's older than my device is. nlheiz, can you confirm this is safe? Or can someone else suggest an alternate method of getting my 2 week old Transformer to a useful state? I definitely appreciate the help.
-Chris
edit: I just read this
The only thing that differs between SBK1 tablets and SBK2 tablets is the use of NVFlash. SBK2 cannot use NVFlash, so if you end up botching both your recovery and your ROM, and cannot boot into either, then you are SCREWED, so I would suggest reading everything before attempting to mod your device if you are an SBK2 owner.
Click to expand...
Click to collapse
There is no emoticon to convey how sad I am right now
edit2: I'm looking at trying this guide: http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html since it appears to be able to fix the issue I'm having.
edit3:attempting the guide posted in edit2 is giving me a "error:device offline" on step 6 when I try the adb push command
edit4: I can't seem to download brk Universal Rootkit 7.1 as neither download link is working

Does anyone have a suggestion? I'd appreciate it. Or is my device totally dead and I'm just screwed?

Try NvFlash anyway, It can't hurt. Does ADB work at all?

Thing O Doom said:
Try NvFlash anyway, It can't hurt. Does ADB work at all?
Click to expand...
Click to collapse
Thanks for your response. I get "0123456789ABCDEF offline" when I type adb devices when I boot into recovery mode, which isn't actually recovery mode since the system it hangs when I try to boot into recovery mode.

cfbauer said:
Thanks for reading.
I recently bought a refurbished Transformer with a serial starting with c20. I rooted with vipermod, installed recoveryinstaller and AOKP. After being unable to install CWM (I now know why) my device became unable to boot into recovery. Recoveryinstaller would not install either. When I attempted to normal boot, the device would just hang. My only option was to cold boot into linux, which worked.
I then attempted to "full wipe" in order to re-install recoveryinstaller for access to recovery. After doing so, my Transformer no longer boots. It sits at the "Android" splash screen, which I believe is AOKP still attempting to load. Recovery doesn't boot, full wipe only beings me back to the "Android" splash, and cold booting into linux also returns me to the "Android" splash.
Can someone point me in the right direction? I feel like I'm at a dead end here. Thanks a bunch.
-Chris
Click to expand...
Click to collapse
How did you get AOKP ROM on the TF if you couldn't get CM to install?
Are you still on stock recovery? I know yo usay recoery doesn't boot but what does it do when trying to boot into recovery?
Doe sit hang or you get any message?
FOR ADB offline message, have you try a different USB port?

baseballfanz said:
How did you get AOKP ROM on the TF if you couldn't get CM to install?
Are you still on stock recovery? I know yo usay recoery doesn't boot but what does it do when trying to boot into recovery?
Doe sit hang or you get any message?
FOR ADB offline message, have you try a different USB port?
Click to expand...
Click to collapse
OMG it worked! I'm back baby! So exited. Thanks for your help! I suppose this means my Transformer is an SBK1. Nice.
To answer your questions if you're curious, I used RecoveryInstaller. It was CWM, but an older version, my mistake. I ran into the random reboots issue, but the version of CWM recoveryInstaller used wasn't compatible with Aroma, which was required to install a custom kernel.
I don't remember the exact text on screen when I try to load into recovery, but I believe it was something like "booting into recovery mode."
And yes, I did try a different usb port for adb, it didn't work. Thanks for the suggestion though!

Thing O Doom said:
Try NvFlash anyway, It can't hurt. Does ADB work at all?
Click to expand...
Click to collapse
Worked! Thanks for the heads up!

By the way, you don't need Aroma to install a custom kernel with AOKP. Since I utterly refuse to flash touch recovery (no ext-sd support) I can't use aroma. The classic way is to go grab the .zip of the kernel (I recommend Testymehics or Guevor's test kernels) out of development. Clear cache, then flash as if you were flashing a rom, no aroma required.

Bricked

My TF300 is unlocked. I installed the new JB and then I was trying to install CWM. I used fastboot to push it to the device. When I rebooted, holding down the volume button, It came up to the menu with RCK, USB, etc. I selected wipe data by accident. It sat there for a while saying it was going to wipe and go into the boot loader. After a while I shut it off thinking it was hung. Now when I power on the device I get only the ASUS startup screen. Volume up or down don't affect the mode. It just says "The Device is Unlocked" at the top, and the static ASUS logo in the middle. When I plug in the USB to my Windows 7 computer I get nothing in the device listing. I can't even fully turn the device off. Holding power for a few seconds, it goes off, and then it comes right back on by itself.
I think I'm totally bricked, right? I CAN get into APX mode.

Yes, wiping the data will brick your device if you don't have a working recovery.

sparky28000 said:
Yes, wiping the data will brick your device if you don't have a working recovery.
Click to expand...
Click to collapse
Actually, I just discovered that I do have access to APX. Is there a way to push a working recovery through APX?

jrfaulkin said:
Actually, I just discovered that I do have access to APX. Is there a way to push a working recovery through APX?
Click to expand...
Click to collapse
I did exactly the same thing.
I have exact same problem.
Tried it via APX mode via NVflash but no luck so far.:crying:
need the correct SBK version.
SBKv1 and SBKv2 doesn't work for the TF300t.
I send my tf300t for repair.
Lets hope that they can fix my TF300t.

jeroen.wit said:
I did exactly the same thing.
I have exact same problem.
Tried it via APX mode via NVflash but no luck so far.:crying:
need the correct SBK version.
SBKv1 and SBKv2 doesn't work for the TF300t.
I send my tf300t for repair.
Lets hope that they can fix my TF300t.
Click to expand...
Click to collapse
Unfortunately, APX and nvflash is not available for the TF300T currently. As I understand it, you're required to record some information and your Secure Boot Keys (SBK) prior to bricking to be able to access APX. Otherwise, your only recourse is to contact Asus and start the RMA process.
I'm recording my developments over in this thread : http://forum.xda-developers.com/showthread.php?t=1825265&page=2 (my post is at the bottom)

I think I'm going to hold out until someone figures out the NvFlash process as described here:
http://androidroot.mobi/technical/tf-secure-boot-key/

I had the same issue. wiped my data after the JB update as my device froze halfway through the update, so I forced a reboot and it hang at the Asus screen, so not thinking I wiped data to go do a fresh update... I wiped the update and all my data/system/recovery.
I found that in the boot loader screen (Wipe Data, Fastboot, ETC....) I was able to navigate to fastboot select it and then it would hang from there. - my computer wouldnt recognize it either however, i tried flashing a copy of TWRP anyway while in my hanging fastboot just to see what happened.
It didnt work first few times but it did eventually flash. so I had a recovery to work with. via a MicroSD put a fresh copy of the JB update on it and re-flash through the recovery via External SD Card.
It did remove my root access, TWRP and all the data on my device after flashing the JB update but it "un-bricked" me and got me booted again.
Don't know if I was just lucky or if it will work for you.

gypsyshaw said:
I had the same issue. wiped my data after the JB update as my device froze halfway through the update, so I forced a reboot and it hang at the Asus screen, so not thinking I wiped data to go do a fresh update... I wiped the update and all my data/system/recovery.
I found that in the boot loader screen (Wipe Data, Fastboot, ETC....) I was able to navigate to fastboot select it and then it would hang from there. - my computer wouldnt recognize it either however, i tried flashing a copy of TWRP anyway while in my hanging fastboot just to see what happened.
It didnt work first few times but it did eventually flash. so I had a recovery to work with. via a MicroSD put a fresh copy of the JB update on it and re-flash through the recovery via External SD Card.
It did remove my root access, TWRP and all the data on my device after flashing the JB update but it "un-bricked" me and got me booted again.
Don't know if I was just lucky or if it will work for you.
Click to expand...
Click to collapse
The difference in your situation is that you were able to access the boot loader. My boot loader is wiped. I don't get the option to select Wipe Data/Fastboot, etc. I'm stuck in a mode where I think the only option is to low-level flash the bootloader after re-initializing all of the partitions.

Happened to me too. I'm hoping that ASUS will fix it for a reasonable price. Otherwise I'm just going to get a Nexus 7.

[Q] Need help with SL101 (didn't see a fourm for it)

SL101 with CWM 1 click root v.1 which i understand is basically the same as the TF101
Tried rooting and seemed to be a success but bricked when trying to install cy mod.
Tried factory reset in recovery mode and still bricked.
Won't mount to SD card.
Can't seem to find any guides to reset firmware back to stock...
Any ideas? links to a guide i haven't found? (I have looked) or am I bushwacked?
Thanks.

TWRP recovery is advised instead of CWM, flash TWRP recovery and then try your ROM again

Did you use ROM Manager to install CWM?
That does not play nice with the Asus tablets.
You can try using PERI to push a new recovery via ADB when in recovery.
I would use ADB to push the TWRP 2.3.2.3 blob myself.

*Detection* said:
TWRP recovery is advised instead of CWM, flash TWRP recovery and then try your ROM again
Click to expand...
Click to collapse
I am not able to open any files through the tablet to access this app. The only screen i can get to is the CWM recovery when you hold power + vol. down.

chchas said:
I am not able to open any files through the tablet to access this app. The only screen i can get to is the CWM recovery when you hold power + vol. down.
Click to expand...
Click to collapse
Follow freds instructions above

*Detection* said:
TWRP recovery is advised instead of CWM, flash TWRP recovery and then try your ROM again
Click to expand...
Click to collapse
used PERI to "unbrick" and it went through the whole spiel with no change.
any instruction on how to use the TWRP?

chchas said:
used PERI to "unbrick" and it went through the whole spiel with no change.
any instruction on how to use the TWRP?
Click to expand...
Click to collapse
ALSO. Might note that I do not have access to my tablets home screen AT ALL. Not through cold boot or anything (unless it takes more than 30 minutes to cold boot)

chchas said:
used PERI to "unbrick" and it went through the whole spiel with no change.
any instruction on how to use the TWRP?
Click to expand...
Click to collapse
If you have TWRP installed as your recovery now, just boot into that, press WIPE, then wipe SYSTEM, CACHE and DALVIK CACHE, then press the Home button in TWRP to go back to the main screen and press INSTALL, choose your ROM, flash that, then clear CACHE and DALVIK again, then flash GAPPS and wipe both CACHES again, then reboot
You can also flash a kernel of your choice, KatKernel is the popular one to go with TeamEOS4 ROM

*Detection* said:
If you have TWRP installed as your recovery now, just boot into that, press WIPE, then wipe SYSTEM, CACHE and DALVIK CACHE, then press the Home button in TWRP to go back to the main screen and press INSTALL, choose your ROM, flash that, then clear CACHE and DALVIK again, then flash GAPPS and wipe both CACHES again, then reboot
You can also flash a kernel of your choice, KatKernel is the popular one to go with TeamEOS4 ROM
Click to expand...
Click to collapse
I only have CWM installed. I can't figure out how to load TWRP onto the tablet without being able to pull up the screen.
Still stuck, I'm finding a bunch of different ways to do it but I can't find a step by step specific to my particular problem.

chchas said:
I only have CWM installed. I can't figure out how to load TWRP onto the tablet without being able to pull up the screen.
Still stuck, I'm finding a bunch of different ways to do it but I can't find a step by step specific to my particular problem.
Click to expand...
Click to collapse
From a quick look at the PERI files I would assume this method:
Boot the tablet into CWM and connect it to the PC > USB
Download and extract the PERI files, right click and run EasyRecoveryV0.4.bat as Admin
Once its done you should have TWRP installed, instructions say it should reboot itself, but doing it from recovery I'm not sure, just make sure it says its done PC side then manually reboot if necessary
If all goes well, flash a new ROM from TWRP

*Detection* said:
From a quick look at the PERI files I would assume this method:
Boot the tablet into CWM and connect it to the PC > USB
Download and extract the PERI files, right click and run EasyRecoveryV0.4.bat as Admin
Once its done you should have TWRP installed, instructions say it should reboot itself, but doing it from recovery I'm not sure, just make sure it says its done PC side then manually reboot if necessary
If all goes well, flash a new ROM from TWRP
Click to expand...
Click to collapse
I really appreciate the help man!
PERI isn't working through recovery mode I guess. The tablet will show up as a device ONLY in device manager and I cannot access any of the storage and it isn't recognizing my SD card that I literally bought new a couple days ago. Please let me reiterate. I only have access to the "stuck" screen of EEE slider and can only get as far as the CWM recovery and using the volume and power buttons to navigate. i CANNOT get past this god forsaken screen.
Those of you guys who have the patience to help people in need FOR FREE are amazing and truly deserve a kings ransom! thanks again for the help so far! I hope we can get through this!

chchas said:
I really appreciate the help man!
PERI isn't working through recovery mode I guess. The tablet will show up as a device ONLY in device manager and I cannot access any of the storage and it isn't recognizing my SD card that I literally bought new a couple days ago. Please let me reiterate. I only have access to the "stuck" screen of EEE slider and can only get as far as the CWM recovery and using the volume and power buttons to navigate. i CANNOT get past this god forsaken screen.
Those of you guys who have the patience to help people in need FOR FREE are amazing and truly deserve a kings ransom! thanks again for the help so far! I hope we can get through this!
Click to expand...
Click to collapse
Been there done that. I had to use adb commands to push a new recovery blob. What version of cwm are you using again?

I have always had to use this one. After having this exact same issue.
D

DatDude123 said:
I have always had to use this one. After having this exact same issue.
D
Click to expand...
Click to collapse
v6.0.1.3
Do you have instruction on how you fixed yours? or a link ?

http://forum.xda-developers.com/showthread.php?p=16557195
This is what saved me. Alk I flash now is arhd and revolver. I do not attempt jellybean any longer......it was me, a laptop, and the tablet connected via usb and using adb commands. You are about to learn a lot.
D

So are there any handy links to a step by step of this? i found one for a Prime but i don't think it's the same thing....

So I followed this guide for adb http://forum.xda-developers.com/showthread.php?t=1071584 and got all the way to the end'. Now i'm stuck, where do I go from here? I don't want to screw anything up so any pointers will help!
Also, i can do this adb stuff while in recovery mode right?
Thanks!