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:
Related
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?
So it seems my phone has become a shiny paperweight. The thing is, I don't really understand why it happened. I've been reading how other people arrived at the same situation and although some symptoms are similar, I didn't do any of those things. I wasn't flashing anything, I didn't drop the phone etc
This is what happened: about 24 hours ago, I was using my phone as a GPS (google maps and waze) when it froze. No biggie, it had happened a few times before so I pulled out the battery, waited a few minutes, put the battery back and pressed the power button. The phone started as usual, it got past the HTC splash screen, the boot animation started. A few seconds (maybe 5) into the boot animation, out of reflex, I pressed the power button to turn off the screen. Don't ask why, dunno. As I've said, reflex. So the screen went black. And it stayed that way.
Since then I've been trying to bring it back to life. No luck yet. Here's the status of the phone:
Battery is not empty - when my phone froze yesterday it was about 80% full. I tried a different battery, no change
When I plug in the USB cable to charge it, the orange/green LED that usually lights up, well... doesn't
When I press the power button, the screen backlight turns on for 2 - 3 seconds, then turns off. Pressing VolDown+PWR does the same thing. I know it seems like a battery issue, but I'm pretty sure it isn't
The computer does not see the phone anymore when connected through an USB cable. 'adb devices' doesn't return anything and I don't see anything in the Device Manager (I was hoping for a QHSUSB_DLOAD but no such luck...)
The phone is a HTC Sensation 4G, HBOOT 1.17 (I think), S-OFF, rooted, was running InsertCoin 3.4.6/Android 2.3.5. As I've mentioned, I wasn't doing any of the things that usually lead to a bricked phone like trying to S-OFF/S-ON, flash a ROM etc. I'm currently reading the internets in an attempt to figure out what went wrong and how to fix it. These are the questions I'm trying to get an answer for:
When the phone boots, is it not in read only mode? At least when it gets to the boot animation part.... And if so, even if the power button is pressed... shouldn't the phone just turn off and that's it?
Since the phone seems to be as responsive as a... well, brick... If I send the phone to HTC to repair it, will they be able to tell it was S-OFF and all that?
Does this sound like something that JTAG could fix?
Thanks in advance for any help or info.
stealth.kid said:
So it seems my phone has become a shiny paperweight. The thing is, I don't really understand why it happened. I've been reading how other people arrived at the same situation and although some symptoms are similar, I didn't do any of those things. I wasn't flashing anything, I didn't drop the phone etc
This is what happened: about 24 hours ago, I was using my phone as a GPS (google maps and waze) when it froze. No biggie, it had happened a few times before so I pulled out the battery, waited a few minutes, put the battery back and pressed the power button. The phone started as usual, it got past the HTC splash screen, the boot animation started. A few seconds (maybe 5) into the boot animation, out of reflex, I pressed the power button to turn off the screen. Don't ask why, dunno. As I've said, reflex. So the screen went black. And it stayed that way.
Since then I've been trying to bring it back to life. No luck yet. Here's the status of the phone:
Battery is not empty - when my phone froze yesterday it was about 80% full. I tried a different battery, no change
When I plug in the USB cable to charge it, the orange/green LED that usually lights up, well... doesn't
When I press the power button, the screen backlight turns on for 2 - 3 seconds, then turns off. Pressing VolDown+PWR does the same thing. I know it seems like a battery issue, but I'm pretty sure it isn't
The computer does not see the phone anymore when connected through an USB cable. 'adb devices' doesn't return anything and I don't see anything in the Device Manager (I was hoping for a QHSUSB_DLOAD but no such luck...)
The phone is a HTC Sensation 4G, HBOOT 1.17 (I think), S-OFF, rooted, was running InsertCoin 3.4.6/Android 2.3.5. As I've mentioned, I wasn't doing any of the things that usually lead to a bricked phone like trying to S-OFF/S-ON, flash a ROM etc. I'm currently reading the internets in an attempt to figure out what went wrong and how to fix it. These are the questions I'm trying to get an answer for:
When the phone boots, is it not in read only mode? At least when it gets to the boot animation part.... And if so, even if the power button is pressed... shouldn't the phone just turn off and that's it?
Since the phone seems to be as responsive as a... well, brick... If I send the phone to HTC to repair it, will they be able to tell it was S-OFF and all that?
Does this sound like something that JTAG could fix?
Thanks in advance for any help or info.
Click to expand...
Click to collapse
It reminds me Desire S problem - fried emmc chip... If your phone has no valid warranty, I'm suggesting to see phone's internals and inspect emmc chip.
The phone still has warranty, I will try to have it repaired/replaced. The only thing I'm concerned about is the fact that it was S-OFF and running a custom ROM... And I don't have the knowledge or equipment to try to take it apart and fix it myself
If you have warranty just use it they won't be able to ckeck if phone was unlocked or not since it can't boot up.
Hey I have a sensation 4g. All has been well until today. I was at work and got an email. Went to check it but the screen wouldnt turn on. This has happend several times since using Viper rom, which is why I switched to energy. I pulled the battery and went to turn it back on.
Since than all I get out of it is a brief lighting of the screen followed by a boot vibration. After that the screen stays off and it "boot vibrates" at regular intervals never displaying anything. Attempts to get into the boot loader for recovery are met with the same.
If I plug a charger into it the charge indicater lights for about 15 seconds than turns off. Occasionally I can see a red light in the upper left hand corner.
I have used a htc g2 battery held against the pins as a known good battery so I have eliminated my battery as bad.
It is rooted, was running ICS Energy rom.
adb does not detect the device nor does linux or windows, but thats not too unusual since it technically doesnt turn on.
I am assuming that the thing is totally dead for whatever reason, but on the off chance someone has any ideas Im all ears, I love this phone.
azethoth said:
Hey I have a sensation 4g. All has been well until today. I was at work and got an email. Went to check it but the screen wouldnt turn on. This has happend several times since using Viper rom, which is why I switched to energy. I pulled the battery and went to turn it back on.
Since than all I get out of it is a brief lighting of the screen followed by a boot vibration. After that the screen stays off and it "boot vibrates" at regular intervals never displaying anything. Attempts to get into the boot loader for recovery are met with the same.
If I plug a charger into it the charge indicater lights for about 15 seconds than turns off. Occasionally I can see a red light in the upper left hand corner.
I have used a htc g2 battery held against the pins as a known good battery so I have eliminated my battery as bad.
It is rooted, was running ICS Energy rom.
adb does not detect the device nor does linux or windows, but thats not too unusual since it technically doesnt turn on.
I am assuming that the thing is totally dead for whatever reason, but on the off chance someone has any ideas Im all ears, I love this phone.
Click to expand...
Click to collapse
Maybe it was a hardware failure. how many times does it vibrate? there is something called qualcomm diagnostic mode that htc phones sometimes get happens when the hboot gets corrputed/damaged. depending how many vibrations you get some people have had luck attempting to blind boot a pc58img.zip to the bootloader to flash a ruu. but since your phone isnt being recognised by the pc as anything i wouldnt hold out to much hope how many vibes do you get?
You might be in diag mode, as heavy_metal_man said.
Does QHSUSB_DLOAD come up in Device Manager?
neither windows nor linux recognize the device at all.
as far as the vibration. I call it a boot vibration, as it is the same intensity and duration of the normal boot vibrate you get on power up.
Its a single vibration of about one second. After that every about 30 seconds it vibrates again.
I did try to shove a P58IMG.zip onto the sd card but I figured that was a long shot anyway and of course nothing happened.
Just out of curiosity have you tired another battery? I know you did check it but one time I was charging my device with a perfectly good battery, it wasn't low, and my device made a weird noise like a high pitch noise then went black. I had no charging light, no life what so ever. I thought I was completely screwed thinking something fried my device. Out of desperation I put another fully charged battery in. Then my device sprang back to life and I haven't had any trouble since. I never figured out what happened. But I was so Glad it worked. So just for curiosity do try another battery. It can't hurt to try it. In my weird case it worked. Like I said earlier the weird part was my battery was good! Not dead! So it won't hurt to just try. You have nothing to lose. I do hope it helps. Good luck and best wishes!
Sent from my HTC Sensation using xda premium
sadly I have no other battery, I have a g2 battery that I can hold in as a substitute but still the same result. I will try to throw that img back on the sd card and see if I can blind install it.
Appreciate the help guys.
hello guys
i have 8x and right now my phone is going on continues boot loop it goes until i see htc logo but not quietly brilliant thing
and then it just reboot i can't turn it off unless its out power so i searched for a fix and everyone is talking about hard reset so how come you
switch it off with out draining it of power
farooq88 said:
hello guys
i have 8x and right now my phone is going on continues boot loop it goes until i see htc logo but not quietly brilliant thing
and then it just reboot i can't turn it off unless its out power so i searched for a fix and everyone is talking about hard reset so how come you
switch it off with out draining it of power
Click to expand...
Click to collapse
Almost the same problem here after I installed an update (don't know which one). I get the HTC Quietly Brilliant and then it reboots until it runs out of power. Hooking it up to a computer, wall charger (tried two different ones) shows the red LED charging light for a while, and then it reboots. It seems like my battery just wont charge, so I can't reset or flash back original ROM. It just shuts off after a couple of seconds. I can go into recovery if plugged to a computer for as long as I like, but as soon as I try to flash, it turns off and goes into reboot loop.
H3223 XaA2 Ultra, got a black screen even flashing stock firmware with new flasher. It'll boot but has a black screen, anyone know how to fix this? i can access flash mode and fastboot mode. but when starting its just a black screen, no unlocked bootloader screen, no sony screen, but the phone seems like its booting because the led will change and then stay green because its fully charged and plugged into my computer.
okay so further development, the phone now boots (still black screen) but i can take screen shots holding power and volume down) and it makes the ting noise when booting.anyone know how to solve this?
can anyone provie a clean stock boot.img?
any advice at all... ive literally been browsing the internet all day trying to figure this out.
thread can be closed... bootloader was mssed up :/ gonna have to get replacement from seller.