Ok, so my brand new EVO was working fine. Power save came on, and turned the screen off. I hit the power button, and you could see the backlight light up, but nothing would come on the screen.
My soution was to remove the battery, then reinsert it.
Now it just gets stuck at the white EVO screen!
Does anyone have anything that can help me with this?
Try keeping the battery out for like 5-10 minutes then put it back in. If that doesn't fix it, might have to do a Hard Reset or bring it back to the store for a new one.
Tried to hard reset, but nothing happens. It stays stuck at that screen.
Hard Reset meaning a full wipe of the phone. I think it's Vol button and Power button at same time. And then choose hard reset or something of that nature. Yeah Vol Down and Power
http://www.knowyourcell.com/htc/htc.../463924/how_to_hard_reset_the_htc_evo_4g.html
Yep, that's the procedure I went through to hard reset.
Like I said though, that didn't fix it.
Bring it back to the store then man or keep the battery out for a few minutes (if you haven't tried that yet) or possibly take SD card out?
When I take the SD card out, it comes up with some new "artwork" on the boot screen that leads me to believe it either can't be booted without this card, or ****'s just broke.. IDK.
It's like a phone with a red X on it?
That's probably not the best description, but it's close.
Ok, so this time taking the SD card out worked. It booted.
I would suggest try to bring it back asap before they run out but maybe someone else has gone through this before and help you. Sorry bro, keep us updated though
EDIT: Nice! Thought that might be it. They were having SD card errors which is why the OTA is being sent out. Glad it worked out for you
Nothing to be sorry over.
My personal opinion at this point is that the SD card got knocked loose, and wasn't seated correctly.
That seems like a horrible design. How are you supposed to see if the pins are aligned correctly?
I mean it should just slide in, but maybe it doesn't fit the tolerance every time.. IDK.
Again, to recap what I did to fix it.
I removed the SD card, reset it to factory default, and it booted.
After that, I put the SD card back in, and all is still well.
Thanks for your help xda-dev forum!
Ok, nevermind. It's still broke.
Seems like when power save comes on something gets hosed.
I'm half afraid to do the OTA update, as I want to root this thing.
Ok, I'm about 90% sure the problem is with the SD card being seated correctly.
Every time I put the card in, the phone freezes within a few minutes.
If I have no card inserted, it runs without a problem.
This is the problem the OTA fixes, you can take it back to the store and see if they will swap it but I'd be willing to bet they tell you to apply the OTA.
I did the OTA, and am still having this problem.
Took it to the store tonight, they agreed to replace it, however their systems were down, because of a storm. So I will be waiting until tomorrow i guess.
plastek said:
I did the OTA, and am still having this problem.
Took it to the store tonight, they agreed to replace it, however their systems were down, because of a storm. So I will be waiting until tomorrow i guess.
Click to expand...
Click to collapse
Whenever I do the update and restart it get's stuck in a continuous loop. I already returned the phone and they replaced it but when I did it again it did the exact same thing. I just learned and didn't install the update again :/
I don't know what I'm going to do now seems like it's stuck. If I update I don't get the latest fixes but if I do it messes up my phone and it restarts over and over again uncontrollably... bleh
Just got my replacement phone.
It seems to function properly so far.
syypher said:
Whenever I do the update and restart it get's stuck in a continuous loop. I already returned the phone and they replaced it but when I did it again it did the exact same thing. I just learned and didn't install the update again :/
I don't know what I'm going to do now seems like it's stuck. If I update I don't get the latest fixes but if I do it messes up my phone and it restarts over and over again uncontrollably... bleh
Click to expand...
Click to collapse
It might be worth doing the update in the store or having them just perform the update so they can go through all the hassle and you just get the result. It's what they get paid to do.
This time they did the update in the store before even giving me the phone.
I think they were just super swamped yesterday, and the early people didn't get updated phones.
The store guy told me I was the sixth return, but they sold "over a lot" of units.
I rooted my phone, now I want to reset it to factory default
I hold down the vol and power on, I get the white screen When I want to go in to recovery, it reboots and hangs with a pic of phone and red w/ xclamation over it
it there any other way to hard reset???
Related
I have an extra Excalibur with the official T Mobile WM6 rom that isn't working. When I turn the phone on, I get a screen with a white background, red text, and blue soft key buttons that reads:
Device start up failed dueto s
udden loss of power. Please c
lick "yes" to continue.
Note:
Do not remove battery be
fore device has been comple
tely shutdown (OFF).
Yes | No
If I press yes the phone does a power cycle and hangs at either the T Mobile splash screen or the WM6 splash screen. I've had no luck with a hard reset. Anybody familiar with this issue? It isn't a huge deal. Currently I'm using a Cavalier and I also have a working Excalibur and a working Wizard, both with 6.1 roms. However, it's be nice to get this phone working.
Only time I ever seen that error is when I ws messing with editing a ROM and must of removed a file that screwed WM up. Now since you say it's the official T-Mo ROM maybe it got currupted somehow. How I fixed it was the Hard Reset the USB way. Hold down the camera button while plugging in the USB with the cell off. It'll load the boat loader and you need to reflash with an official ROM. Now I know you said you Hard Reset, but I've seen people explain a few differents methods all being explained as Hard resetting. This method worked for me during my testing.
I'm flashing the original rom and everything seems to be working alright.
I really appreciate your help man.
Okay, I wish I had better news but I'm still running into problems. After I finished installing the rom from T-MO's website, I powered the phone on. It showed the T-Mo screen, then the WM6 Screen, then played the T-Mo animation/sound. The screen stuck here, and the phone would not power off so I removed the battery and put it back in. I then got the original error message and pressed yes, and the phone lagged at the same point again.
how long did you wait for fist boot?
rickwyatt said:
how long did you wait for fist boot?
Click to expand...
Click to collapse
Like Ricky said, how long did you wait? The first boot could take a while, the flash is going to perform a "Cold Boot Config". It take a bit longer that first time to load.
I actually got it to prompt me for cold boot config once, but after finishing the phone rebooted and hung once again.
I don't know, maybe you got a hardware problem. I'd try reflashing it again and when it boots the first time don't touch it and see what happens. If it hangs for more then say 10 mins. I'd say you might be having a hardware problem.
Hmm. I guess I most definitely have a hardware problem. An error of that sort would most likely be from a faulty motherboard, correct? I have a dash that was taken into the lake not too long ago. Everything recovered okay, other than the screen. The phone no longer turns on for a completely different reason, but I think the guts are mostly good.
Is it possible to change out motherboards? If so, is it unwise to try the motherboard that went swimming with me over the summer?
Well considering neither work, what do you have to loose? lol I say try swapping aprts and see what comes of it. I have seen cells "go swimming before and servive as long as the battery is removed right away and it's allowed to dry thoroughly. They don't opperate on much voltage so short curcuits due to water is not as bad as say a 12 volt or higher device.
Also, I forgot to mention the status on the phone. Okay, I can flash an official ROM and it will boot up and run Cold Boot Config. After that the phone will power cycle. It hangs a little bit at the T-Mo splash screen, but does eventually start. At that point it basically works flawlessly, except I cannot detect it through ActiveSync via USB.
Once the phone powers off, it will not turn back on. I don't get the original error message, just nothing happens. Only way to get the phone turned on again is to hold the camera button down while plugging in the USB cord, and start all over flashing an official ROM.
Yeah, I would say hardware failure. It's a complete new flash so it shouldn't be suffering from a software problem. Maybe the ROM Chip is damaged causing errors to the WM installation. Same thing as a bad hard drive in a computer that will currupt files and end up crashing the system.
drkfngthdragnlrd said:
Yeah, I would say hardware failure. It's a complete new flash so it shouldn't be suffering from a software problem. Maybe the ROM Chip is damaged causing errors to the WM installation. Same thing as a bad hard drive in a computer that will currupt files and end up crashing the system.
Click to expand...
Click to collapse
That's exactly what i'm thinking too, sounds like a hardware error as a flash wont solve it.
So what piece of hardware is the most likely culprit?
I never took mine apart, but I would say it's the ROM Chip which should be soldered to the motherboard. If it is replace the whole motherboard...
t mobile dash
so when holding down the camera key and plug the usb do i try to also turn it on what am i looking for and how long do i hold the keys down
thank you
Hi!
First of all i got AOKP + Franco kernel for 2w without any problem and I didn't change any option since last week.
This morning i rebooted it, it switched off and it didn't start again.
I cannot switch one my nexus again since then. I have always a black screen, also if I try to enter in download mode or in the recovery.
I tried to connect to my computer and smt times my laptop see a omap4400 (i'm not sure about the name) but after few second it disappears.
Tomorrow I'm going to the service center... But I have a big doubt:
What the hell happened this morning?
Thanks
Remove the battery for 5 minutes and try again.
If that doesn't work,
Follow this guide:
1. Download the zip file from http://forum.gsmhosting.com/vbb/f634...eeeee-1465412/, created by Legija
2. Extract zip to whatever location you're comfortable with (I used Android directory)
3. Open up Device Manager (Hold down Windows Key, press R, the type in devmgmt.msc and press OK)
4. Go to actions menu, select Add Legacy Hardware
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process
9. Once completed, unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Click to expand...
Click to collapse
biscuitownz said:
Remove the battery for 5 minutes and try again.
If that doesn't work,
Follow this guide:
Click to expand...
Click to collapse
This, if OP can't reach fastboot.
Sent from my i9250
I'm having the exact same problem. I saw my phone at maybe 10% battery in the AM, said screw it and let it die, woke up this morning and plugged the phone in and nothing. No LED light, black screen, completely unresponsive. I've tried every trick in the book, and the only one that seemed to work marginally even was using a different battery, which got my phone to boot to the encryption screen, but then shut off again. It did that twice, and now both batteries are useless.
I used Legija's program to try and bring some life back to my gnex, even though it's not the international version, just in hopes of getting some of my data back (I have already started the replacement process with Verizon since the phone was insured), but I got no luck there either.
It's extremely disappointing and annoying to me that this phone survived all sorts of ROM installations (I was also using AOKP on 4.1 if someone wants to start making connections), reformatting, tweaking, almost every setting on that phone was modified by me.
Not only that but almost any software or hardware problem I did run into I could solve in maybe an hour, but I let my charge run out and the phone just up and bricks itself? Now, that's just bull****... I would be very curious as to an explanation as to WHY on earth this would happen. Very confusing.
Not to hijack the thread, but my interest here is not restoring the phone to working condition but just seeing if I can pull my data off of it. I wouldn't even be posting here had I been able to have an SD card with my gnex, which I figured was unnecessary at the time I bought it since I knew the space on their was enough for me already, and the added branding of "Nexus" brand which had me under the impression it was maybe stable enough by itself. Not a mistake I'll make again..
Is it at all possible to get the data off of my phone at this point? At least partially? I believe encryption makes it impossible but I'm rather stubborn. Any help would be greatly appreciated..
owlieowl said:
I'm having the exact same problem. I saw my phone at maybe 10% battery in the AM, said screw it and let it die, woke up this morning and plugged the phone in and nothing. No LED light, black screen, completely unresponsive. I've tried every trick in the book, and the only one that seemed to work marginally even was using a different battery, which got my phone to boot to the encryption screen, but then shut off again. It did that twice, and now both batteries are useless.
I used Legija's program to try and bring some life back to my gnex, even though it's not the international version, just in hopes of getting some of my data back (I have already started the replacement process with Verizon since the phone was insured), but I got no luck there either.
It's extremely disappointing and annoying to me that this phone survived all sorts of ROM installations (I was also using AOKP on 4.1 if someone wants to start making connections), reformatting, tweaking, almost every setting on that phone was modified by me.
Not only that but almost any software or hardware problem I did run into I could solve in maybe an hour, but I let my charge run out and the phone just up and bricks itself? Now, that's just bull****...
Not to hijack the thread, but my interest here is not restoring the phone to working condition but just seeing if I can pull my data off of it. I wouldn't even be posting here had I been able to have an SD card with my gnex, which I figured was unnecessary at the time I bought it since I knew the space on their was enough for me already, and the added branding of "Nexus" brand which had me under the impression it was maybe stable enough by itself. Not a mistake I'll make again..
Is it at all possible to get the data off of my phone at this point? At least partially? I believe encryption makes it impossible but I'm rather stubborn. Any help would be greatly appreciated..
Click to expand...
Click to collapse
So just to be clear... You've been able to get it to boot all the way up to the encryption screen, right? If so you should be able to get into fastboot (Holding down BOTH volume rockers and the power key.) From there you could relock/unlock the bootloader to do a full factory wipe which might solve your boot issue.
As far as the data loss from the wipe, you could then try this: http://forum.xda-developers.com/showthread.php?t=1994705
TomBall718 said:
So just to be clear... You've been able to get it to boot all the way up to the encryption screen, right? If so you should be able to get into fastboot (Holding down BOTH volume rockers and the power key.) From there you could relock/unlock the bootloader to do a full factory wipe which might solve your boot issue.
As far as the data loss from the wipe, you could then try this: http://forum.xda-developers.com/showthread.php?t=1994705
Click to expand...
Click to collapse
I was able to get it to the encryption screen with my old battery that had a little bit of charge left in it twice, but it shut itself down on me both times. So now both batteries are useless.. I took it to the Verizon store hoping they would maybe try one of their batteries, but they just called customer service and told me they're just going to replace it at this point.
I have a feeling the charging mechanism is somehow damaged, because when I did get it to the encryption screen I had it plugged into a wall outlet and it wasn't charging at all. So, I can't turn the phone on whatsoever anymore.. if I could turn it on I could solve this problem... but it simply refuses to boot. The closest I came to interfacing with it was the OMAP Flash script, which did work, but didn't fix the problem.
So maybe if I could get the phone working enough to use ADB with it I could get my data back, but not even that seems possible..
owlieowl said:
I was able to get it to the encryption screen with my old battery that had a little bit of charge left in it twice, but it shut itself down on me both times. So now both batteries are useless.. I took it to the Verizon store hoping they would maybe try one of their batteries, but they just called customer service and told me they're just going to replace it at this point.
I have a feeling the charging mechanism is somehow damaged, because when I did get it to the encryption screen I had it plugged into a wall outlet and it wasn't charging at all. So, I can't turn the phone on whatsoever anymore.. if I could turn it on I could solve this problem... but it simply refuses to boot. The closest I came to interfacing with it was the OMAP Flash script, which did work, but didn't fix the problem.
So maybe if I could get the phone working enough to use ADB with it I could get my data back, but not even that seems possible..
Click to expand...
Click to collapse
If the phone isn't charging then there's something wrong with the USB port. One way to test that would be to use a battery charger. Also, try a different cable. I've had issues with a few different cables that for whatever reason started to not fit properly in the phone.
If you're USB port has gone bad then you'll need to either A) Always use an external battery charger. B) Get a replacement. C) Fix it yourself (Good guide here: http://www.ifixit.com/Guide/Repairi...+LTE)+Micro+USB+Charge+Port+&+Main+Mic/9641/1 )
Hi there, this is my first post, i didnt want it to be like this but i have come to you in desperation.
I was excited about 4 hours ago to realise my phone was getting an update saying it was going to imporve battery life etc..
Well i let it do its thing while it was downloading, i went to check after an hour or so and it said the software had been corrupted or something along those lines, either way it had to start the download again.
It was about bed time when this happened so i chucked it on the charger, fell asleep, woke up and it was doing something on a kind of screen i had never seen before, black screen, obviously showing that it is processing the update(i was a little tired from waking up) i think i remember taking its time maybe longer than it should have been.
I went back to sleep woke up about an hour ago from now and checked my phone and the screen would not turn on, i think the charger cable had fallen out from the phone because it is loose and does that some times.
So i placed the cord back in and it didnt seem to respond with the red led coming up for a while then all of a sudden it worked for some reason, but was flashing. i suspected this was because the battery had been sucked dry. So after a while the led stopped flashing and i pressed the power button, sure enough it powers up straight away to the HTC - quietly brilliant screen. And thats that, end of story. It's stuck on that screen WTF?
I have been through forums like these interested in changing ROMs and so on but it all seems so complicated i never even bothered, so obviously i am a noob, but i dont think there is any reason for this to happen other than sh*t luck.
Can anyone help us out?
Your better off sending for repair unless you want to start unlocking the bootloader etc.
Reboot your phone in bootloader ( press PowerButton + Volume down at the same time) you will get to a screen with various lines, look factory reset, navigate that menu with your volume keys. Hit factory reset you should get . See if it fixes it.
masucu said:
Reboot your phone in bootloader ( press PowerButton + Volume down at the same time) you will get to a screen with various lines, look factory reset, navigate that menu with your volume keys. Hit factory reset you should get . See if it fixes it.
Click to expand...
Click to collapse
mercccccccccccccccccccccccccccccccci
zezo_ddd said:
mercccccccccccccccccccccccccccccccci
Click to expand...
Click to collapse
Well did it work? before you say that long thanks
Thanks for your help, unfortunately, the factory reset didnt work.
What happened when i first did it, the update screen came up like the first time but still ended up freezing on the quietly brilliant screen.
I'd be willing to unlock the bootloader, i really dont want to send the phone away for a third time. Why didnt i get the Galaxy S3!?!?!
I hate to ask, can u point me to the right thread to do that, there seems to be a few but they seem to have different purposes.
Thanks again.
helter_skelter87 said:
Thanks for your help, unfortunately, the factory reset didnt work.
What happened when i first did it, the update screen came up like the first time but still ended up freezing on the quietly brilliant screen.
I'd be willing to unlock the bootloader, i really dont want to send the phone away for a third time. Why didnt i get the Galaxy S3!?!?!
I hate to ask, can u point me to the right thread to do that, there seems to be a few but they seem to have different purposes.
Thanks again.
Click to expand...
Click to collapse
If you wait a day or so, the RUU will be released for your region now that the OTA has been released.
You'll be able to fully reload your phone - this is all HTC do when you send it for repairs and you can do it in a lot less time.
At the moment, HTC may even reload the 2.17 software so you may still have the problem again when trying to load the OTA.
Thanks all for your interest.
I spoke with customer support and they told me exactly what i already had done, factory reset through hboot.
After that was a no go, he told me i have to send it back to the point of sale, so they can flash the software?
Where can i find this ruu once it has been released?
I'm pretty sure the updates all say to not have the phone plugged in when updating.
Sent from my HTC One X using xda app-developers app
I'm not 100% sure it is the power button so I wanted to run the situation by the forum, but also because this was my son's first Christmas and I have all his videos/pictures on the internal memory ... my priority is really trying to get those. I could really care less if I had to buy a new phone.
So here's the situation ....
Phone was fully charged and I came into work. Had already been listening to a podcast, sent a few text message, etc. I looked over at one point and the screen wouldn't come on. Tried pressing the power button multiple times with no luck. If I removed the battery and put it back in, it would power on briefly and then shut off.
Device only briefly comes on when I first put the battery in. If I'm quick I can try putting the phone in download mode. It gets to the initial screen and then powers off. Sometimes it is there a few seconds longer than others.
I mistakenly tried this and didn't even have the power button in and it still went to the download mode, so THAT is why I'm thinking something is wrong with the power button. It's as though it is permanently pressed.
I read a few threads and watched a few youtube videos but I'm not really getting a clear answer. I've taken the phone apart and the button is NOT pushed in. I can press it and it seems fine (besides it not doing anything). I did try also hitting it a few times as some videos suggested and it didn't help?
Anyone have any thoughts on a next step?
Edit: in case this is important, it is rooted, running moar v6.x, zerolemon battery. i realize the case may have been the initial culprit so at the moment it is back to a stock battery and case.
lawlhai said:
I'm not 100% sure it is the power button so I wanted to run the situation by the forum, but also because this was my son's first Christmas and I have all his videos/pictures on the internal memory ... my priority is really trying to get those. I could really care less if I had to buy a new phone.
So here's the situation ....
Phone was fully charged and I came into work. Had already been listening to a podcast, sent a few text message, etc. I looked over at one point and the screen wouldn't come on. Tried pressing the power button multiple times with no luck. If I removed the battery and put it back in, it would power on briefly and then shut off.
Device only briefly comes on when I first put the battery in. If I'm quick I can try putting the phone in download mode. It gets to the initial screen and then powers off. Sometimes it is there a few seconds longer than others.
I mistakenly tried this and didn't even have the power button in and it still went to the download mode, so THAT is why I'm thinking something is wrong with the power button. It's as though it is permanently pressed.
I read a few threads and watched a few youtube videos but I'm not really getting a clear answer. I've taken the phone apart and the button is NOT pushed in. I can press it and it seems fine (besides it not doing anything). I did try also hitting it a few times as some videos suggested and it didn't help?
Anyone have any thoughts on a next step?
Edit: in case this is important, it is rooted, running moar v6.x, zerolemon battery. i realize the case may have been the initial culprit so at the moment it is back to a stock battery and case.
Click to expand...
Click to collapse
If it's the power button take it to sprint and and they should fix or replace...especially seeing as its a known issue.
http://i.imgur.com/qrByUGN.jpg
lawlhai said:
I'm not 100% sure it is the power button so I wanted to run the situation by the forum, but also because this was my son's first Christmas and I have all his videos/pictures on the internal memory ... my priority is really trying to get those. I could really care less if I had to buy a new phone.
So here's the situation ....
Phone was fully charged and I came into work. Had already been listening to a podcast, sent a few text message, etc. I looked over at one point and the screen wouldn't come on. Tried pressing the power button multiple times with no luck. If I removed the battery and put it back in, it would power on briefly and then shut off.
Device only briefly comes on when I first put the battery in. If I'm quick I can try putting the phone in download mode. It gets to the initial screen and then powers off. Sometimes it is there a few seconds longer than others.
I mistakenly tried this and didn't even have the power button in and it still went to the download mode, so THAT is why I'm thinking something is wrong with the power button. It's as though it is permanently pressed.
I read a few threads and watched a few youtube videos but I'm not really getting a clear answer. I've taken the phone apart and the button is NOT pushed in. I can press it and it seems fine (besides it not doing anything). I did try also hitting it a few times as some videos suggested and it didn't help?
Anyone have any thoughts on a next step?
Edit: in case this is important, it is rooted, running moar v6.x, zerolemon battery. i realize the case may have been the initial culprit so at the moment it is back to a stock battery and case.
Click to expand...
Click to collapse
maybe this will help you: http://forum.xda-developers.com/showthread.php?t=2369125. i had a verizon s3 which wouldn't even turn on until i tried this (steps were a little different since it was a verizon one and not sprint). here are the verizon steps: http://forum.xda-developers.com/showthread.php?t=2581166.
you may be able to use the win32diskimager in windows to create the sd card instead of linux. i have also heard the SD card needs to be the same size as the phone. 16GB phones means 16GB Class 10 SD Card. 32GB phone means 32GB Class 10 SD Card. I used a SanDisk card from best buy. probably the best $15 i ever spent lol. i used the sd card to boot the phone. then reinstalled stock recovery and bootloader. thsi didn't affect the actual ROM (didn't take away root on 4.3 jellybean). Good luck!
Try a dirty flash. Can you get into recovery? Flash moar again. Or try nandroid and to external SD and transfer to computer to see if u can collect the files you're trying to get back
Generally when I get refurb, I have pretty good luck, but perhaps the forces that be are saying I shouldn't have one. When I first ordered, I got one with a dead pixel. Couldn't fix it, so I sent it back. Just today I got my replacement. I was pretty excited since the tablet looks brand new (still has most of the plastic on it around the edges. I charge it for a bit, turn it on and....
It played the Samsung startup music, but the screen stayed black. Didn't show anything. Keys lit up like they should, everything sounded normal, but was just black. For a while nothing happened, then finally the screen came on. It seemed to act normal from there on. Thinking nothing of it, maybe it was just a glitch, I took a few OTA updates. Every time it reboots, the screen issue comes up. And while it was updating, it didn't show the android updating screen. Also, I can't get it to go into recovery. Perhaps I actually am, but the screen is off so I can't see. I've searched and can't find anyone with a similar issue. Since this is my second device, should I just send it back and ask for a refund or is there something I can do to try and fix it?
Racso14 said:
Generally when I get refurb, I have pretty good luck, but perhaps the forces that be are saying I shouldn't have one. When I first ordered, I got one with a dead pixel. Couldn't fix it, so I sent it back. Just today I got my replacement. I was pretty excited since the tablet looks brand new (still has most of the plastic on it around the edges. I charge it for a bit, turn it on and....
It played the Samsung startup music, but the screen stayed black. Didn't show anything. Keys lit up like they should, everything sounded normal, but was just black. For a while nothing happened, then finally the screen came on. It seemed to act normal from there on. Thinking nothing of it, maybe it was just a glitch, I took a few OTA updates. Every time it reboots, the screen issue comes up. And while it was updating, it didn't show the android updating screen. Also, I can't get it to go into recovery. Perhaps I actually am, but the screen is off so I can't see. I've searched and can't find anyone with a similar issue. Since this is my second device, should I just send it back and ask for a refund or is there something I can do to try and fix it?
Click to expand...
Click to collapse
Well to force reboot, hold and press power+home+volume up and down until it reboots. Have you tried to also factory reset in recovery?
DUHAsianSKILLZ said:
Well to force reboot, hold and press power+home+volume up and down until it reboots. Have you tried to also factory reset in recovery?
Click to expand...
Click to collapse
I was trying to say I can't get into recovery. I don't know if it actually is in recovery with the screen off, or if I just cant get to it at all.
Additionally I just tried a KIES update, and it did not take. When I plug into KIES it says the same update is available even after I just updated it. Just now doing a software factory reset. So far no change. Unless someone can provide me information on how to fix this, looks like I'll be sending it back.
You will know if you're in recovery if you type 'adb devices' into a command window with the usb cable attached.
If it returns a set of numbers you're in recovery.