Database Users

[Q] Need help with semi/soft brick!

So my Vibrant has been turning off randomly. I think its because of the loose battery or maybe it's just over-heating. But a few days ago, after turning it on there is only a black screen and lit capacitive buttons at the bottom.
It boots up normal, with the vibrant name, t-mobile animation, and the Galaxy S boot animation, then black screen! This started to happen after a few reboots, and now it won't rebbot properly, just black screen. It seems like I have to restore my phone, but the problem is I cannot get the phone into recovery or download mode! Please advise.
Samsung Vibrant, Eugene Eclair v6 custom rom with lag fix

First of all, there's no such thing as semi brick, there's brick or not. Try installing your Rom again..

Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App

iwillkillyou said:
Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
dude, he cant back up if he cant access the homescreen. neither can he use rom manager..
cant use the hardware buttons to get into dl or recovery either... read op guys...
2010ngojo said:
[Q] Need help with semi/soft brick!
So my Vibrant has been turning off randomly. I think its because of the loose battery or maybe it's just over-heating. But a few days ago, after turning it on there is only a black screen and lit capacitive buttons at the bottom.
It boots up normal, with the vibrant name, t-mobile animation, and the Galaxy S boot animation, then black screen! This started to happen after a few reboots, and now it won't rebbot properly, just black screen. It seems like I have to restore my phone, but the problem is I cannot get the phone into recovery or download mode! Please advise.
Samsung Vibrant, Eugene Eclair v6 custom rom with lag fix
Click to expand...
Click to collapse
Do this bro... just tested it myself, works fine...
get adb installed on your computer, should already have it if your rooting but if not get it, youll find it in the stickied thread for informative links in the development section.
get a cmd prompt open on your computer and type in
>adb devices
let it start up deamon and it will tell you device not found, its ok.
now type and have ready...
>adb reboot recovery (do NOT press enter yet)
start your phone like normal. before its even finished with the boot up tmobile animation and the galaxy s (but after the plain vibrant text/picture) logo press enter. if it says error: device not found then wait all the way till galaxy s only you did it too early...
screen will go black and reboot into standard recovery... hope to goodness you had a working clockwork recovery installed and nandroid ready for this next part...
go down using your volume keys and select reinstall packages using the power key
now in clockwork recovery go down to nandroid
now go to restore
go to your earliest back up and restore it.
there you go.
I would start fresh get odin set up and reinstall the original rom at this point as something may still be corrupted, reroot, install latest clockworkmod, latest vibrant 9 rom (im using and see no bugs and runs better then the vibrant 6 rom i had) and DONT install the lag fix until the newest "TRUE" lag fix comes out with the new file system and kernel that JAC is working on and has almost ready.
good luck and pm me if any of these steps need further explanation.

Pypanys thanks for that post, I learn something new but he said its bootsup normally, but it goes to a black screen after the boot logo he can enter recovery mode, same thing happen to me. I was opening maps and it crashed, it frooze the phone, to I restarted the phone and enter recovery amd deleted user apps, and it did the fix,
Sent from my SGH-T959 using XDA App

iwillkillyou said:
Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
iwillkillyou said:
Pypanys thanks for that post, I learn something new but he said its bootsup normally, but it goes to a black screen after the boot logo he can enter recovery mode, same thing happen to me. I was opening maps and it crashed, it frooze the phone, to I restarted the phone and enter recovery amd deleted user apps, and it did the fix,
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
hes just stated man that he cant even get into recovery, my guess is hes locked out using the volume up/down keys like many new phones are (which btw is a known defect, spend 10min on the phone with tmobile doing thier trouble shooting to show them it doesnt work and they send you a replacement..) sooooo I gave him a way to get into recovery without the buttons and not having to wait till he gets to a black screen where possibly its frozen and he cant use adb commands.
I was just making mention to you also that he cant even back stuff up NOW (hopefully he already archived all his apps and data) and hes better off starting fresh since hes getting problems using his current rom/lagfix....

Thanks for the quick reply p()()pypants, but i will have to try your method later. It's late and I have class (college) tomorrow, but i will post my results soon. Thank you again.
Edit 1:
Btw, is there a way to back up my current rom? Like the way rom manager back up roms? I know my current rom works before so that's why I want to back it up.
Edit 2:
Actually i did not use adb to root my phone, just used the one click method. So can you please give me more detailed instructions on how to install/use adb?

Okay, I typed in "adb reboot recovery" and press enter as my phone booted up during the t-mobile animation and at the Galaxy S boot animation. Neither time work. Then I reentered it again after the black screen. That did not work either. CMD keeps on returning "error: device not found" and the phone stays on with the black screen.

2010ngojo said:
Okay, I typed in "adb reboot recovery" and press enter as my phone booted up during the t-mobile animation and at the Galaxy S boot animation. Neither time work. Then I reentered it again after the black screen. That did not work either. CMD keeps on returning "error: device not found" and the phone stays on with the black screen.
Click to expand...
Click to collapse
Do you have the right drivers installed? You can check here: http://forum.xda-developers.com/showthread.php?t=728929
Another very stupid question, just to cover all bases - your phone is plugged into the computer, correct? When you install the new drivers, try plugging the phone into a different USB port on the computer than you've been using, so it will hopefully pick up the new drivers without much extra effort.
If that doesn't help, just keep trying the command while the phone boots up. Maybe you'll get lucky and it will work. Sorry I don't have any real solution for you :\

I'm fairly sure I have the right drivers, otherwise I wouldn't be able to root in the first place. Yes, the phone is plugged in also. I'll try a different USB port and see what happens...
Update: Trying different USB ports does not help.

red triangle with exclamation point on recovery screen

figured it all out.. thanks!

Means you don't have a recovery. Need to most likely run the 2.1 ruu and reroot with eris one click. Something went wrong and it didn't flash Ra recovery

i hope your ok buddy,try it again but check if the root me.zip file is in your sd card first before you go into recovery,if its their it should of flashed the recovery.
Sent from my Vanilla Tazz using Tapatalk

thank you. i googled and found instructions for flashing amon ra recovery. but it fails in the first couple steps. when it tells me to run "su" from the shell command it tells me permission denied. the phone is not rooted yet, so i can not allow superuser from the phone as most of my googling has suggested.
what now?

the rootme.zip is on the sd card.

did u reboot after you pressed the button? and then did u turn it off and go to recovery?

mindnumbinglyfun said:
trying to root my friends phone (using the one-click root for eris) ive run into a problem i havent seen before, and cant find answers for on google or this site.
when i reboot the phone into recovery holding volume up with powering on, i get a picture of the eris, with a red triangle and exclamation point. and thats it. i cant do anything.
any idea what it is or how to get rid of it?
Click to expand...
Click to collapse
That is the splash screen of the stock recovery.
It means that flashing of Amon_RA never happened.
[ For goofs, you can prove it is a stock recovery by pressing Vol-up+End again when that image is on the screen. (If you were rooting a Cupcake Eris, the key sequence would be Home+End) ]
As others have pointed out, the primary reason that OneClick fails is that the person using it fails to perform a normal reboot in between use of the app and cold-booting into the recovery. Just reboot your phone once normally, shut it down, and then cold-boot to recovery.
- install app
- run app
- shut down phone normally
- reboot phone normally
- shut down normally
- cold boot into recovery
One more thing; you know that this is not a development topic, yes?
bftb0

No solution to this Boot Loop issue!!

No one is able to offer a solution to this issue
I have the EVO with CM7 and after flashing phone it enter a boot loop with
White back ground and HTC Logo.
Other post have same issue..and we are not able to get into recovery
please see post: http://forum.xda-developers.com/showthread.php?t=1340267
bootloop and the phone was using CM7. I was able to get to boot loader menu but can not get to recovery.
Tried to add recovery image no dice...now the phone will only charge and not boot

Just so you know, this belongs in the Q & A section...as it doesn't offer any 'development' of roms, kernels, ect.
Anyways, did you try flashing a boot.img via fastboot?
P.s....prepare to be flamed.

dirtysausage said:
No one is able to offer a solution to this issue
I have the EVO with CM7 and after flashing phone it enter a boot loop with
White back ground and HTC Logo.
Other post have same issue..and we are not able to get into recovery
please see post: http://forum.xda-developers.com/showthread.php?t=1340267
bootloop and the phone was using CM7. I was able to get to boot loader menu but can not get to recovery.
Tried to add recovery image no dice...now the phone will only charge and not boot
Click to expand...
Click to collapse
The things people do for CM7 =)

Is there a way to get to fast boot using adb? Im not able to get the phone to boot now
just shows connected under device manager as MY HTC **again black screen no boot**

teh roxxorz said:
Just so you know, this belongs in the Q & A section...as it doesn't offer any 'development' of roms, kernels, ect.
Anyways, did you try flashing a boot.img via fastboot?
P.s....prepare to be flamed.
Click to expand...
Click to collapse
Is there a way to get to fast boot using adb? Im not able to get the phone to boot now
just shows connected under device manager as MY HTC **again black screen no boot**

Was a problem a few months back with some users, no solution was ever found. The only thing they were able to do was flash a radio and pull the battery to cause an intentional brick and then have it swapped.

RileyGrant said:
Was a problem a few months back with some users, no solution was ever found. The only thing they were able to do was flash a radio and pull the battery to cause an intentional brick and then have it swapped.
Click to expand...
Click to collapse
wow thought someone would have answer for a fix!
Wonder why it shows up in device manager...but not able to accept any commands
I see adb > My HTC would be nice to access the phone some how this way but abd says no device

dirtysausage said:
wow thought someone would have answer for a fix!
Wonder why it shows up in device manager...but not able to accept any commands
I see adb > My HTC would be nice to access the phone some how this way but abd says no device
Click to expand...
Click to collapse
Well I had the same issue, but my adb skills are next to nill. I just upgraded from the kyocera zio. I was able to flash a new recovery image through the zio clockwork mod fastboot program. Now I wont promise it will work for you but it is worth a shot.

jlmancuso said:
Well I had the same issue, but my adb skills are next to nill. I just upgraded from the kyocera zio. I was able to flash a new recovery image through the zio clockwork mod fastboot program. Now I wont promise it will work for you but it is worth a shot.
Click to expand...
Click to collapse
Yeah I did try a recovery the RA recovery for the EVO...I was able to update and tried to enter recovery but was not able to. I tried with another recovery by adding it to the root of the card and attempted to load the file with adb..BUT after the power down the phone no longer boots to bootloader...black screen and it vibrates once. I can only see it register as adb device >My HTC under device manager. But please not that running adb shell and no device detected.
Can anyone help?

had the same problem alot of times .

What did you do?
Sent from my SCH-I500 using XDA App

[Q] help needed. Stuck in CWM bootloop after attempting OTA update

Hi All, as the title states, I'm currently stuck in a CWM bootloop after trying to applying the new OTA update on my rooted transformer.
I know it was kinda stupid of it.
I tried following the steps posted here, but i can't seem to get adb to push the file through.
I must admit that I'm not very good with using command prompts and i have no idea if I'm doing it right.
Steps I'm sure i'm doing right so far.
I opened up my cmd and cd C:\android-sdk\platform-tools
When typing adb devices, my transformer is successfully recognized as 0123456789ABCDEF OFFLINE
However, the next part got me slightly confused.
I had typed in C:\android-sdk\platform-tools>adb push C:\cwm_recovery-5027_rogue_rburrow-tf101-r1.zip /sdcard/download.
However, i kept encountering the error that the device is offline.
I had also set up a marco to press the up arrow+enter key with a 10ms pause in between followed by a 1 second pause before repeating.
However, the file was still unable to be pushed to the device despite countless tries.
I'm not sure if it's because the line i had entered was wrong or was it due to some other factor.
Would someone be kind enough to help me take a look and see if i had done something wrong?
Thank you very much for your help!

lunzi88 said:
Hi All, as the title states, I'm currently stuck in a CWM bootloop after trying to applying the new OTA update on my rooted transformer.
I know it was kinda stupid of it.
I tried following the steps posted here, but i can't seem to get adb to push the file through.
I must admit that I'm not very good with using command prompts and i have no idea if I'm doing it right.
Steps I'm sure i'm doing right so far.
I opened up my cmd and cd C:\android-sdk\platform-tools
When typing adb devices, my transformer is successfully recognized as 0123456789ABCDEF OFFLINE
However, the next part got me slightly confused.
I had typed in C:\android-sdk\platform-tools>adb push C:\cwm_recovery-5027_rogue_rburrow-tf101-r1.zip /sdcard/download.
However, i kept encountering the error that the device is offline.
I had also set up a marco to press the up arrow+enter key with a 10ms pause in between followed by a 1 second pause before repeating.
However, the file was still unable to be pushed to the device despite countless tries.
I'm not sure if it's because the line i had entered was wrong or was it due to some other factor.
Would someone be kind enough to help me take a look and see if i had done something wrong?
Thank you very much for your help!
Click to expand...
Click to collapse
Damn man sorry to hear that. Def should have flashed stock recovery before applying the OTA. Im sure one of these guys can help you out though good luck!
Sent from my Transformer TF101 using xda premium

pierrekid said:
Damn man sorry to hear that. Def should have flashed stock recovery before applying the OTA. Im sure one of these guys can help you out though good luck!
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
yeah dude, i realised that after i googled for a fix.
prior to this my experience with OTA updates on rooted+CWM phones had never encounter such problem.
The most that had happened previously was that the update failed to be installed.
I had no idea it could get stuck in a loop i couldnt get out of.

when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS

baseballfanz said:
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
Click to expand...
Click to collapse
thanks for the tip.
I can't try it right now as I left the tablet at home when I left for work today.
I'll update once I get back home to try it.

baseballfanz said:
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
Click to expand...
Click to collapse
The words are not even popping up for me, it just shows the asus logo and then goes straight into recovery. I go into adb devices and it shows OFFLINE aswell.
:S

baseballfanz said:
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
Click to expand...
Click to collapse
That's what I did when it happened to me. Worked like a charm.

I did the same thing and I'm stuck too.
Sent from my Kindle Fire using xda premium

Same problem here for the same reason...flash ota update on my root tablet....I'm always on cwm recovery when reboot. I'm able to cold boot it when holding.vol down and power but I do I get around this cwm ecovwry bootloop? Thanks
Envoyé depuis mon HTC Glacier avec Tapatalk

lamaqc said:
Same problem here for the same reason...flash ota update on my root tablet....I'm always on cwm recovery when reboot. I'm able to cold boot it when holding.vol down and power but I do I get around this cwm ecovwry bootloop? Thanks
Envoyé depuis mon HTC Glacier avec Tapatalk
Click to expand...
Click to collapse
Same here. The only way I can boot now is VolDown + Power. Another thread recommended flashing some stock-like ROM, but I'd rather not.

Has someone found out how to boot normally?
I have to cold boot everytime my device reboots or it shuts off, which is quite often.
The cold boot method is becoming really annoying.
Thanks!

Found a way!
Hi guys! This is my first post helping somebody
So I found a way to make it boot normally...
What you need to do is to cold boot your device.
Then download from the store Android Terminal Emulator.
Open it up and type in:
Code:
su
Allow SuperUser if prompted.
If you get # then you are good to go!
Now you need to type in:
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Once it's done, reboot your tablet and you should see a progress bar.
Let it load and once it's done, you have your tablet back!
Hope it works!

Hi guys I'm in trouble!! I have continuos bootloops in recovery. I tryed to flash a rom as usual but always bootlooping adn when I tryed to make a cold boot it remain in the same " colod booting linux ".. I can't restore my backup cause I move it on my memory card and cant restore it! Can I do something? I can't boot anymore... Any suggestions? I can only install the rom I have put in the internal memory..

My tf101 is bricked !! Please help!!

My tf101 cannot enter recovery anymore
when i try to enter recovery ,
there is a " ! " on the robot , then tf101 reboot automatically
then freeze on the ASUS logo page
I cannot boot up the machine in normal mode too !
my tf101 is B70 version, someone help..thanks

! with the Android guy is recovry, stock recovery.
instead of Vol up to get into revovery, wait till you get options to cold boot or wipe device.
try booting that way.
also what were uou doing when it gotvstuck at that screen?

baseballfanz said:
! with the Android guy is recovry, stock recovery.
instead of Vol up to get into revovery, wait till you get options to cold boot or wipe device.
try booting that way.
also what were uou doing when it gotvstuck at that screen?
Click to expand...
Click to collapse
i tried cold boot , but it said cold booting up linux .. but no response
i tried wipe device , but it still freeze on ASUA screen too
yesterday, i try to root and install CWM via Prime V4.5
then the device comes this .....
Thanks ...

Never heard of that root utility before. You may not have used the right rooting utility for your device which can cause a brick situation. Also, are u sure u dont have the tf 101 and not thr tf prime? The vipermod utility found in the tf prime forum will root ics for both the 101 and prime. My suggestion is that u make sure u have the right device and search the right forum for brick recovery, unroot, or return to stock threads. They are usually found in the development sections.
Sent from my SGH-I777 using XDA

viperMod PrimeTime 4.5 will only root the TF101 and shouldn't be used to install CWM. That's why it bricked.

cholywell said:
viperMod PrimeTime 4.5 will only root the TF101 and shouldn't be used to install CWM. That's why it bricked.
Click to expand...
Click to collapse
i had an issue that was caused by lack of sleep last night that i might be able to help this guy out.he never used it to flash CWM.. he rooted it and never flashed from within the CWM app. The stock recovery doesn't have options for choosing files ect..

victor1144 said:
My tf101 cannot enter recovery anymore
when i try to enter recovery ,
there is a " ! " on the robot , then tf101 reboot automatically
then freeze on the ASUS logo page
I cannot boot up the machine in normal mode too !
my tf101 is B70 version, someone help..thanks
Click to expand...
Click to collapse
I might be able to help you... I saw your post around 4am. I had the same problem kinda. Was asleep most the day (got done at 6am).
I rooted with viperMod PrimeTime and it worked !
BUT i forgot to FLASH CWM RECOVERY from inside the app and proceeded to install the new ROM after root was made USING the CWM app. What happened in my case , the CWM app restarted trying to flash the new ROM, WITHOUT CWM being my recovery instead rebooted to STOCK recovery and something glitched up. I had the same thing as you stuck on Eee pad never re-starting. Cold boot wouldn't work or full wipe..In my case something conflicted.
Below is the NVFlash of the 3.2 Build of 8.6.5.13 (Latest Build). You need to re-flash again using APX threw your USB connected to a PC (it self installs) :
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
the links are in Grey btw and says US version, ect ..read everything but its very straight forward... ill explain what i did toward the end of the post to simplify it since it took awhile to figure it out. Ill add side comments threw the process that explains better than the link.
Attention: These tools are designed to bring your device back to working condition. They are great for getting back to stock if you need to send your device in for repair or you need to downgrade to stock in order to root your device, etc.
Instructions for Windows users:
1. download the file from the original link i gave above. NVFlash of the 3.2 Build of 8.6.5.13 (Latest Build) USWindows
2. unpack zip to desktop.
3. Press Volume up and Power at the same time on your Transformer to enter APX mode, connect to pc (hold for about 7 seconds). Basically, Power off.. THAN, power and Volume up at the same time to enter APX mode. IMPORTANT!! the screen remains BLACK like its frozen ,with no writing or indication something is happening. that's normal and the original poster in the link never mentioned it. That is APX mode..
4. drivers for APX are in there if you need them..inside the windows downloaded file its called NVFLASH towards the bottom
On your PC go Device manager.. if APX is working correctly and the Transformer is in APX mode it will appear as an exclamation on the device manager named APX.. you cant miss it.. it stands out. On my Windows 7 PC it changed and said Asus USB (or something like that)
5. double click Run Download.bat file and let run! everything is prepackaged so no copying files, etc. In the same file you downloaded that you unzipped named Windows its the 4th file that says "download" with a gear looking icons.
Your Transformer (based on what happened with mine) will go threw a self install like its pushing files and flashing it..the black screen looks like its being pushed the files and reflashing without a recovery. Your going back to stock. if you dont see anything on your Transformer screen after running/double clicking the Download.bat file ....Right click on APX in the device manager , properties, Drivers, update Firmware, choose manual install and find the Downloaded.bat file and click it. That should do the trick..I did both and only noticed the Transformer lighting up after manually pushing it threw APX.
6. After the device reboots power it off. Then hold vol- and power until you get the option to erase your data.... Select the option to wipe data.
7. Download the latest update from the Asus website if applicable and follow the manual instructions. This step may not be necessary if your OTA update worked or my nvflash is the latest version. US update on there site is 9.2.1.17.Its the only one...
What i did was go back to stock since i didn't see any interesting ROMS..Point is THAT unbricked my device by flashing it in APX mode when it was connected to the PC.
I did use ViperMod again to Root, but used the Clockwork mod app in my Transformer to FLASH CWM RECOVERY to try a few ROMS out.
After trying a few of them out i choose to revert everything to stock, unrooted and reflashed STOCK recovery.
Hopefully that helps you out.. it did work for me...

Thank you so much it worked great

Lantek23 said:
Thank you so much it worked great
Click to expand...
Click to collapse
Glad i could help

Sorry to dig up slightly old threads, but I have a question for you. I have a TF101 that I was trying to update to ICS. It is currently running 3.2 courtesy of the unbricking tool listed in this thread. I had to unstore it as it was bricked from a bad install. That was many moons ago. It won't show an updaate listed, so I decided to go with the manual route. I downloaded the appropriate update (my device lists WW version) loaded it on an SD card had the install prompt come up and rebooted to install... For a split second it shows the android with the gears like it is installing the update and then shows the android with a triangle and exclamation mark. After that, nothing. I have to reboot to get it off that screen. Upon booting, I get a message saying system update failed (2) unknown error. Any ideas?

If Im not mistaken, the zip file you download (I guess from asus?) contains another zip.
Thats the zip you should place on your SD card, did you do that?

Also try renaming that zip to EP101_SDUPDATE.zip (the one extracted)

I already had the zip extracted, and renaming didn't do anything.

Killa357 said:
I already had the zip extracted, and renaming didn't do anything.
Click to expand...
Click to collapse
Are you rooted? Did you remove any system apps?
Another thing to try is on your micro sd card, make a folder name ASUS and inside that folder another folder call Update, inside the Update folder put the extracted zip file (don't rename). Turn off TF and turn it back on, see if it will detect the update file.
If that fail, you did mentioned you use the unbricking tool, use that NVFlash to flash a compatible ICS ROM

It isn't rooted anymore since I ran the unbricking tool, and no system files were modified. Placing it in Asus>Update folder didn't work. I may end up having to really do things manually...

Killa357 said:
It isn't rooted anymore since I ran the unbricking tool, and no system files were modified. Placing it in Asus>Update folder didn't work. I may end up having to really do things manually...
Click to expand...
Click to collapse
You don't need to be root to use NVFlash.

Just when with a slightly older version of the update and it worked. There may be something wrong with the file Asus has hosted.

Hi
I have a slightly different problem. I have rooted my B60 serial number, it has the ICS from ASUS on it and it boots fine, its rooted and it works. Now the problem is I thought lets try a clockwork mod and play with custom roms.
So I set my win 7 up to adb etc, and pressed power button volume button - and off to recovery I went...
but all I got was a little green android on its back chest open and an exclamtion mark. No adb fastboot devices command.
I seem not to have a recovery nor a way of forcing a custom recovery.
Should I NV flash or just be happy the tab works and leave well alone?
Any other answers since a lack of recovery may come back to haunt me sooner or later.
I also tried the power button vol uyp for 7 secs and nothing happens I can get to the cold boot erase data option on power down, don't want to do that yet since Im not sure what data gets erased and I may have a totally non working tab.

Use RecoveryInstaller to install cwm recovery

Use RecoveryInstaller to install cwm recovery
This is my problem I can't get recovery - nor can I get adb to see the device. It shows as a hard drive/storage device but not in adb.