OK, so I haven't used my TF for a couple of weeks...it was in a sleeve and I assume the battery died. I went to boot it tonight, and it wouldn't (no real surprise)...so I plugged it in and let it charge for some time...still, nothing.
The screen does turn on, but it remains black - but you can tell the screen still works. Occasionally, when I hold the power button it the whole screen flashes blue and it quickly displays a bit of the Android Alien...never, ever, seen a blue screen with the Android logo on the tablet.
Anyway, I can't get it to boot. I've tried holding the power button, tried booting while holding the Vol+ and Vol- button...still, nothing.
Any ideas? Searching yields nothing like this...it's similar to the deep sleep, but clearly the screen still wakes (but remains black), and then I get a little flash of blue, too.
Thanks fellas.
polkadots said:
OK, so I haven't used my TF for a couple of weeks...it was in a sleeve and I assume the battery died. I went to boot it tonight, and it wouldn't (no real surprise)...so I plugged it in and let it charge for some time...still, nothing.
The screen does turn on, but it remains black - but you can tell the screen still works. Occasionally, when I hold the power button it the whole screen flashes blue and it quickly displays a bit of the Android Alien...never, ever, seen a blue screen with the Android logo on the tablet.
Anyway, I can't get it to boot. I've tried holding the power button, tried booting while holding the Vol+ and Vol- button...still, nothing.
Any ideas? Searching yields nothing like this...it's similar to the deep sleep, but clearly the screen still wakes (but remains black), and then I get a little flash of blue, too.
Thanks fellas.
Click to expand...
Click to collapse
I've Googled again and again...nothing...all it does when I try and boot is flash to an old school Windows style blue screen...It flickers so I can't make out what it all says, it's doing some kind of memory check (?)...and something else, I think...but that's it. I tried this too: http://www.addictivetips.com/mobile/how-to-unbrick-asus-eee-pad-transformer-honeycomb-tablet/
Is this thing FUBAR???
Nobody has any clues about what to do hear? Seriously?
I can't even get it to boot...the screen turns on, but remains black, unless it flashes that blue screen...what do?
nvflash a flashable rom...
http://forum.xda-developers.com/showthread.php?t=1123429
"bricked" is such an overused phrase on xda.
EDIT: sorry, didn't click the link on the second post
what does 'it doesn't work' mean in the context of nvflash? does it refuse to connect? does it successfully flash it but not start? more info would be appreciated
Yea, it connects. My computer recognizes it, I can get in ADX (?) mode, it flashes. From my computer side of things it works, but the entire time the NVFlash process is going I don't see anything on my screen. So it appears to work on the computer side of things, but not on the tablet side. I still have the booting problems and the blue screen.
Thanks so much
Sent from my PC36100 using Tapatalk
Probably something hardware on the inside then.
^Agree with the above post
although while you are flashing something, you aren't supposed to have screen activity on it. I hope you didn't pull the plug because of that.
I hope that you can find a solution to your problem, but it might actually be a ram problem or something
Damn...I was afraid it would be hardware related. So, I was (am?) rooted and was running a custom ROM...can I still send this to Asus? Will they replace it, or am I just effed? Thanks guys, I appreciate the insights.
Sent from my PC36100 using Tapatalk
They will replace it, but they might charge you for it. Most of the time you can get away with "custom rom? what does that mean? I just used the installer thingy with the cord in the computer and tablet" Just ask them for an RMA #, they're pretty good at that kind of stuff.
Unless, of course, you overclocked it to something insane and fried the circut board, you should be good to go.
Dyskmaster said:
They will replace it, but they might charge you for it. Most of the time you can get away with "custom rom? what does that mean? I just used the installer thingy with the cord in the computer and tablet" Just ask them for an RMA #, they're pretty good at that kind of stuff.
Unless, of course, you overclocked it to something insane and fried the circut board, you should be good to go.
Click to expand...
Click to collapse
I was running Revolver. Then I followed the unbricking instructions on that link...no change.he in how my TF acted before or after. I filed for an RMA online, and will go that route. No crazy overclocking. Thanks.
Sent from my PC36100 using Tapatalk
Asus told me the screen on mine is dead. i have to send it to them
mine boot but after 2 sec the screen goes black. even when i press the power button it only turns on for 2 sec. good thing i went back to stock before all that madness went down
kinda sucks i wanted to try all the new roms now i gotta wait at least a week still the RMA send it back
same problem black screen flashes blue
same problem as polkadots
screen lights up (i.e. not backlight problem) stay lit and then flashes blue. You have to press power to shut off the black screen (i.e. not backlight problem). I have not tried to do any roms it was a refurbished product that worked fine for a month and then had this problem. have tried hard and soft resets and the black screen comes on and acts like it is working. then it flashes blue upon the touch and goes back to black screen. any ideas? anyone with same problem? do i have to send back to Asus?
how do all.... nexus s I9023
i have just purchased a some what lovely google nexus s I9023
working fine for an hour or so...
i had a little pop up asking me to update...
i thought OK... sure why not...
having done so phone worked fine for an additional 20 mins...
then phone froze... i took the battery out and started it up again...
it froze on GOOGLE screen...
iv trawled every forum possible since this has happened...
now the PHONE WILL NOT EVEN TURN ON...
the phone is completely stock no mods or addon's to it!
im at the end of my tether.. SOME ONE PLEASE HELP!!!!!!!!
Hold volume up + power after reinserting the battery and putting it on charge. Do you enter bootloader mode? And what happens if you click recovery?
done the hold volume up and press power...
still no joy unresponsive!!
when it does work after 50 attempts of taking the battery out and putting it back in and doing volume and power
it turns on.. scroll to recovery.. it turns off google screen pops on...
then a Green android lying on his back appears with its stomach open showing white blocks and a explanation mark above it!
IM PUZZLED!!!!!
it then resets it self going back to being unresponsive!!
HELP!!!!
Give this a shot.
Also, could it be a power button issue? And that android screen is the splash for stock recovery. You have to press vol. up + power again to get past it, beyond this you can do a factory reset and similar magic. However you likely don't want this, and on the screen where you chose to enter recovery, you'll likely want to use fastboot to unlock the phone (which will wipe all personal data) and then flash a stock ROM again. At this point i would advise lots and lots of reading.
If it's less than a year old, i would be calling samsung though. If it is a new phone i would definitely do this first. Do not unlock unless you have no chance of going through warranty. Will need to know the exact status of the phone for best advice here.
My One S had been dead for quite some time and I have two batterys which probably both are dead.
When I put my phone charging, first the led will go orange, then the led will get green over time, but the only thing that gets the warmer is the motherboard and when I try do switch it on it does the usual battery-empty-better-flash-the-bottom-row sequence. Any ideas?
This all hapended after a screen change so not sure if the screen is ****ed or the phone.
Is it possible that I might have a boot loop where there is no screen action?
When I connect my One S to my computer it says properly villec2.
When I try to boot it, it just stays black and vibrates after some time like its rebooting.
Any ideas how to fix this? I can't boot into bootloader or recovery.
After some messing around all my PC says that its a Android 1.0 device. Which might mean it's in fastboot mode?
All help is appreciated. 2 beers for the guy who solves the mystery. :good:
Has anyone ever gotten stuck on the OP logo bootscreen after replacing the screen?
After replacing the OPO screen with the Vifocal screen+display assembly, I am stuck on the OnePlus logo, the Cyanogenmod doesn't ever appear, and the top of the phone (logic board) gets very hot. The same thing happens when the phone is powered off and then is plugged in to charge (doesn't show the battery recharging animation, it's just stuck at the OP logo). Can boot into fastboot (vol up + power). Cannot boot into recovery (vol down + power).
No custom ROMs, not rooted. Using most recent over the air OS version, although prior to the screen breaking I remember a notification asking me to update, but I don't recall ever accepting it. Since then the phone has been off (approx 2 weeks) while I was waiting for my replacement screen.
Thoughts? Thanks everyone!
I've replaced my screen a couple of times without issue. I'd tear it apart again and make sure a all the connections are solid and be certain you didn't forget or miss any.
Hi, While on holidays I dropped my phone on the beach and a wave hit it, it was covered in sand etc and it was wet. The phone, however, was still turned on and the screen still worked. I locked the phone, and removed the sand from the charging port and between the buttons. But when I turn it on, it goes to the "1+ Powered By Android" screen, and it doesn't go past that. I also can't reach the recovery screen, but I can get to fastboot mode
I left it in rice for a few days, to no luck and I put it in the hot press overnight which didn't work either.
I also tried flashing the stock rom from fastboot mode, and flash a recovery rom too, but it didn't help at all.
Does anyone have any suggestions on what I should do to try and fix it?
Cheers, Adam.