Related
Yesterday i had my TP2 on the bed.. anyway i tried to call someone and noticed that again my touchscreen went dead (it happened 2 times before) and both times it recovered without me doing much.
during the night the battery died and when i plugged it in today it started up but it wont go back from landscape... touchscreen still is not working.. and when i call someone the mic is dead... i cannot hear them.
When i try to make it go to sleep it wakes up again
The phone works with hardware keys, but i`m utterly dissapointed by HTC
RIght now i`m waiting it to charge up and reflash the latest ROM from Energy... any other hints would be appreciated
thanks
wow, that is very strange.
is your device exposed to anything out of the ordinary?
dont know why you would get hardware failures like that. But maybe its software issue? try hard-reseting or flashing back to stock rom and see if that does anything.
wiping the device...
I think it's time for a change in OS (nexus one)
phone functions returned except the screen
qiuness said:
phone functions returned except the screen
Click to expand...
Click to collapse
Is the screen completely dead, or is the touchscreen just not responding? My touchscreen just topped responding a few days ago. I tried a soft reset, hard reset, and re-loading the stock ROM, but the screen still wouldn't respond, so AT&T swapped the phone out for me.
exactly... the screen works just not the touch. I bought the phone of a HTC reseller unlocked with no contract a year ago
Background: Very familiar with the Eris, rooted it, flash ROMs frequently, never had an issue.
So I bought the phone on eBay, only issue was the phone was a bit beat up and the screen had been replaced. No big deal. Turned it on everything was fine, worked for about a day, then I decided to flash another ROM. Flashed the ROM and the phone would reboot every time I got to the lock screen UNLESS I had signal, then it would work. This issue happens to EVERY ROM I flash. I wiped cache,dvlik-orwhatever, full wipe, everything each time I would flash a ROM, and none of them have been stable. After flashing the first ROM I also ran into the turn off and vibrate 5 times with a flashing green light problem. I have gotten out of this twice with the USB pull method. I have researched these issues, I have tried flashing quite a few ROMs, and nothing seems to work flawlessly. Is the DI just a terrible phone or do I just have a bad unit? The main issue seems to be with signal, such as if I go from airplane mode on to off it will reboot and then get stuck in a boot cycle and the issue with flashing the phone and having to have signal before I can unlock the phone.
I am currently about to flash the PB31IMG to see if it will resolve the issues and then attempt to re-root. Any advice would be greatly appreciated as nothing has seemed to work so far. I would key you into what I have tried but I don't remember. Basically all the things to fix the 5 vibrate issue and general flashing woes.
Update:
Still no good. Flashed the PB31IMG via vol. down and power and it still did a reboot. Unlocked, got to the white HTC screen, and restarted. Booted the second time, got to the lockscreen, and rebooted before I could even slide down the unlock. Third reboot, got to activation this time, then it rebooted. Fourth reboot, go to activation, then rebooted. Fifth reboot, got to lockscreen, then rebooted before I could slide down.
So yeah. basically you can see what I am dealing with. And it is not fun. I have tried SD card in, SD card out. Just did its 6th reboot, didnt even get to the unlock screen before rebooting.
UPDATE 5/3:
Link to the video of whats happening. Nothing special and I recorded it with my Eris, but you'll at least see the timing of the reboots and what not. And ignore the breathing. lol. Just turn off the sound. Right after the video ended it did a 5 vibe. Pulled the battery and now it's just doing bootloops.
I have never had the random reboots before, at least not at the rate and consistency you have been. To me it sounds like something went wrong in the rooting process and I would recommend unrooting and rerooting.
As for the flashing green light and 5 vibrates, I have so insight on this. It can happen if you press power and Vol+. I think it puts it in a safety mode and the only way to get out of it is a battery pull. So if you ever get stuck in a situation like this wait 10 minutes and try to turn it back on normally. If this doesn't work try booting into hboot (power + vol down) if this doesn't work power + vol up has worked for some people too.
There are cases however, where battery pulls don't help either. And no matter what the person tries the phone won't turn back on. This is a hardware problem and the only way to fix this is getting a new phone.
Dhessler5 said:
I have never had the random reboots before, at least not at the rate and consistency you have been. To me it sounds like something went wrong in the rooting process and I would recommend unrooting and rerooting.
snipped.
Click to expand...
Click to collapse
Would flashing the PB13IMG in Hboot unroot it or would I need to follow the guide? Just curious as I have never unrooted before, but I do know there is a guide for it.
The 5 vibrate thing is under control, it just has happened so I wanted to make it known.
And thanks for the info.
I would follow the guide for it, it would be the easiest and safest way and if you run into any problems they would be able to help you out and know exactly what to tell you. I have yet to unroot too so I don't want to tell you something without being 100% sure so I recommend the guide.
Alright, so it turns out flashing the image I flashed via Hboot is a way to unroot. :/ And that is when I got all the reboots in the beginning (the ones specifically posted, its not the first time). I am going to flash again once more to see if I can get a flawless start.
Still no good, flashed it again via Hboot and it restarted again. This timeat the white HTC screen after unlocking but before activation. :? Hm. Better than nothing, after the first reboot it fully loaded and everything is fine so far. Lets just home it doesn't slowly begin to degrade like last time.
A while ago while running the peanut stock ROM, every time my phone would reboot some apps would loose information (such as log in) and I was eventually unable to access the EPST settings.
If you rerooted your phone you could try to go into hboot and then recovery and "fix permissions." I am not sure if this will do any good but it couldn't hurt.
Also if it is unrooted you could try to bring it in to Verizon and see if they will give you a new phone or a restored one.
Make sure you have the stock Rom if you bring it back to Verizon also
sent from my dinc
sorry to hear this happened on an ebay phone... I've had it happen to 3 of mine... warranty took care of it since I'm still within my date. but after one year what do I do? luckily I bought my bros early upgrade meaning the Inc2 will suffice until april 2012
ohh yea my point sorry: I had an Eris before the Inc. //////had many problems after 5 they gave me the Inc if I agreed to drop my current one year contract and get a new two year paying the two year price PLUS got credited $199 for the Eris, and got to keep it, so I thought I made out until I realized this phone isn't gunna last two years. ANYWAY. I bought the Eris off Ebay, they gave me warranty after warranty no problem, best of luck
I have had my Inc for a year and have not had any issues. I would say you bought a bad model from someone on eBay. The 5vibration green light is indicative of a hardware failure and I have not seen anyone have a fix for it.
Sorry to say but I have seen no one, NO ONE recovery from the 5 vibs of death. From what I have gathered it is some sort of qualcomm download mode and I know of no way out. I have a feeling it is caused by pressing the vol + and vol - and power while trying to get into hboot.
This is just an uneducated guess. If your willing to part with the device I would love to get my hands on a 5 vibs phone.
Since it happens when the phone loses the signal, I'm wondering if it might be a radio issue. Which radio version is installed? It could be incompatible for your area/ROM/whatever.
Another thought: you said the screen was changed out. It is very possible that the kernal installed won't work for an lcd screen.
Anyway, more things to check and to test. Good luck!
mine always happened when i accidently pushed the vol + instead of vol -
twice it happened
ACD168 said:
mine always happened when i accidently pushed the vol + instead of vol -
twice it happened
Click to expand...
Click to collapse
That should be 3 vibs, not the 5.
they both won't work after wards thought as far as my testing.. had to get warranty replacements
I remember reading Chingy fixed 5 vib. It's not the end. I've seen other people fix it with ruu.
I couldnt fix mine when I got the 5 vibrations and I tried everything. My theory is that it has something to do with a messed up kernel flash since the baseband and kernel are apparently linked and I saw somewhere that flashing the same baseband 2x will cause this. It happened to me when I tried to flash a kernel twice (the first time it failed), some people could be getting this when flashing roms since they install new kernels also.
You can flash radios and kernals twice. There was one leaked radio in the past that caused problems from being flashed twice, but it isn't typical
Edit: I think chingy said something about trying a hundred different things, but eventually he got it to work by connecting to PC with battery removed. I could be wrong though because I read that post months ago. I know he got it working again by wiping system and starting fresh
I had the 5 vibs on mine a few weeks ago. It was an unfortunate event. I had the phone for almost a year, bought it new too. I had probably flashed at least a hundred times (thank you nighties for feeding my ROM flashing addiction) but I digress.
I was at work when it happened. If I remember right I believe I was re-installing a pandora apk when my phone did the vibs and led. As an fyi it is the same apk I am using now and it works fine. I initially thought oh well I'll fix it when I get home, surely someone has the answer...sadly not. I spent quite a while searching threads and google to no avail.
I was able to get it unrooted through hboot tho. I was also able to get it to boot when usb was connected to my PC, but as soon as I unplugged it would do the vibs again.
I don't like to admit defeat, but I had clearly lost. I called and got a replacement device sent (and an extended battery because the guy thought it could have been a battery issue, lucky me)
All I can do now is hope it doesn't happen again, but if it does hello warranty man. If someone does find a fix I would love to know about it for future reference.
Sent from my ADR6300 using XDA Premium App
Trifurcated said:
I had the 5 vibs on mine a few weeks ago. It was an unfortunate event. I had the phone for almost a year, bought it new too. I had probably flashed at least a hundred times (thank you nighties for feeding my ROM flashing addiction) but I digress.
I was at work when it happened. If I remember right I believe I was re-installing a pandora apk when my phone did the vibs and led. As an fyi it is the same apk I am using now and it works fine. I initially thought oh well I'll fix it when I get home, surely someone has the answer...sadly not. I spent quite a while searching threads and google to no avail.
I was able to get it unrooted through hboot tho. I was also able to get it to boot when usb was connected to my PC, but as soon as I unplugged it would do the vibs again.
I don't like to admit defeat, but I had clearly lost. I called and got a replacement device sent (and an extended battery because the guy thought it could have been a battery issue, lucky me)
All I can do now is hope it doesn't happen again, but if it does hello warranty man. If someone does find a fix I would love to know about it for future reference.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
I think the 3, vibrate and 5 vibrate are connected because both times I had the 3 vib I had the same problems, would turn on when connected to usb then 3 vib and green flashing light... weird.
I was using the phone today and the screen suddenly locked up on me. It wouldn't respond to any button presses so I just did a battery pull to reset it. However, the phone won't turn back on now. It doesn't do anything, even when plugged into the charger, the phone doesn't even indicate that it's charging or anything at all. It's like it has been completely bricked.
It was completely stock, never unlocked it or rooted and never installed any custom rom or anything of that nature. I've only had the phone for a couple of months and I'm completely baffled as to what could have happened. It certainly wasn't anything that I did.
Any ideas? Or does anyone have any experience with this type of thing happening to their phone?
So I've left the battery out for over 30 minutes and it still won't turn on. I have an extended battery and the regulary battery that came with the phone and it won't turn on with either battery.
I have also tried the volume down and power button method and that doesn't do anything at all either.
Plugging the phone into the computer with the USB cable also does nothing.
How long have you had the phone. Did you buy it from a store?
.....Clones & Drones.....
Mine did the exact same thing! It was realy weird, however all i did was keep the power button pressed and it rebooted fine.
Sent from my Galaxy Nexus using xda premium
ptmr3 said:
How long have you had the phone. Did you buy it from a store?
.....Clones & Drones.....
Click to expand...
Click to collapse
I got the phone when it was released and I ordered it online right from Verizon's website.
I hope that you have the warranty from the carrier!
gulmat said:
Mine did the exact same thing! It was realy weird, however all i did was keep the power button pressed and it rebooted fine.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I wish it was that simple for me.. I held the power button down for over a minute and still, nothing happened. This is really frustrating.
!!!!!!!+111111
evolishesh said:
I hope that you have the warranty from the carrier!
Click to expand...
Click to collapse
.....Clones & Drones.....
ptmr3 said:
!!!!!!!+111111
.....Clones & Drones.....
Click to expand...
Click to collapse
I'm not sure about that one. I know I don't have insurance thru verizon but isn't there a manufacturer warranty? Like I could get a refurb from verizon instead of a brand new one?
I've never had a smartphone just stop working for no reason at all and I was never really into modding them so I thought I was safe. I guess I was wrong.
Really disappointed in Samsung right now. This is my first nexus device, not sure if I'll get another.. That's totally lame to have a crap product that just stops working for no reason. This is an unmodded phone, completely stock, never been dropped or anything of that sort. The only thing that I did was swap the regular battery out for the extended version.
russ4h said:
I'm not sure about that one. I know I don't have insurance thru verizon but isn't there a manufacturer warranty? Like I could get a refurb from verizon instead of a brand new one?
I've never had a smartphone just stop working for no reason at all and I was never really into modding them so I thought I was safe. I guess I was wrong.
Really disappointed in Samsung right now. This is my first nexus device, not sure if I'll get another.. That's totally lame to have a crap product that just stops working for no reason. This is an unmodded phone, completely stock, never been dropped or anything of that sort. The only thing that I did was swap the regular battery out for the extended version.
Click to expand...
Click to collapse
I'd definitely go to Verizon with this. Most definitely manufacturer defect.
Hold down volume up and volume down and the power button. Does it boot into fast boot? Id say if it doesn't do anything then go ahead and call your carrier because its a faulty unit. You can also try plugging it in without a battery and then Inserting the battery. That also saw sends a power up signal to the device. Though I don't know if this trick works on a nexus three. This was an old trick to "jump start" a nexus one that had a faulty power button. But aside from all this, it sounds to me like you've got a faulty unit whether you get it running or not. Probably just need to swap it , sounds like something went pop.
Sent from my Galaxy Nexus using Tapatalk
You should be able to get a refurbished phone.its probably just a manufacturer defect.
Sent from my Galaxy Nexus using Tapatalk
android01 said:
Hold down volume up and volume down and the power button. Does it boot into fast boot? Id say if it doesn't do anything then go ahead and call your carrier because its a faulty unit. You can also try plugging it in without a battery and then Inserting the battery. That also saw sends a power up signal to the device. Though I don't know if this trick works on a nexus three. This was an old trick to "jump start" a nexus one that had a faulty power button. But aside from all this, it sounds to me like you've got a faulty unit whether you get it running or not. Probably just need to swap it , sounds like something went pop.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Thanks for the tips, I tried the volume up, volume down, and power button method just now and it doesn't do anything. I Also just tried plugging it in and then putting the battery in and nothing as well.
The thing is, I don't have insurance thru Verizon (i.e. the $5 a month thing). Would going to them even benefit me at all? Do you know if they would offer a refurb or something?
The phone has a 1 year warranty on it. You shouldn't have to pay anything but you might just get a refurbished replacement.
I think I had the same thing happen to me a few days ago. However, I have the GSM version that I bought from amazon (thru a third party seller), so no warranty. Yeah, I know. Smart. Also, in my case, I unlocked the bootloader so I could flash the official yakju so I would get updates faster from google. Despite some lagginess with 4.0.2, it had been working great for a month+.
When mine crashed, all I did was press the back button and the screen went crazy and froze up, then started glitching and made a buzzing sound. I pulled the battery and tried a reboot. The Google logo would glitch and "ghost" and then the animation would start, but it was slower and choppy. After a few seconds, it froze and the screen was all low-rez looking and I could see what I can only describe as strange pixelation or scan lines (with a few of them moving from the top of the screen down to the bottom in a continuous loop). The only way to get it to stop was another battery pull.
I tried to use fastboot to get back in and reflash to the original firmware, but I kept getting a usb error (didn't have that when I first unlocked the bootloader using a mac, so not sure what the problem was). Now, the phone won't get passed the Google logo and just sits there for 30+ minutes without making any progress (that I can see). I keep trying to get back into the bootloader using fastboot, but now it won't even do that.
I've contacted Samsung/UK (as that's where mine originated), but don't think I will be getting any help based on their initial response. And, since my bootloader is unlocked, that probably voided the warranty anyway. I have no idea what happened, but it seems like some sort of combination of hardware/software problem. So, basically I'm screwed and out $700.
russ4h said:
Thanks for the tips, I tried the volume up, volume down, and power button method just now and it doesn't do anything. I Also just tried plugging it in and then putting the battery in and nothing as well.
The thing is, I don't have insurance thru Verizon (i.e. the $5 a month thing). Would going to them even benefit me at all? Do you know if they would offer a refurb or something?
Click to expand...
Click to collapse
I'd say go contact Verizon and see what they say. If they can't help you out then you gotta contact Samsung and I believe (if my memory serves me right) all their products have a one year warrenty from the day the phone was used. So you should see what they have to say.
Similar thing happened to me, it rebooted itself, as it has been doing quite a bit of lately, and then wouldnt turn on no matter what I did.
Eventually just help the POWER and VOL DOWN button together to reboot, and it worked fine again. I'm completely stock wtf.
tandp74 said:
I think I had the same thing happen to me a few days ago. However, I have the GSM version that I bought from amazon (thru a third party seller), so no warranty. Yeah, I know. Smart. Also, in my case, I unlocked the bootloader so I could flash the official yakju so I would get updates faster from google. Despite some lagginess with 4.0.2, it had been working great for a month+.
When mine crashed, all I did was press the back button and the screen went crazy and froze up, then started glitching and made a buzzing sound. I pulled the battery and tried a reboot. The Google logo would glitch and "ghost" and then the animation would start, but it was slower and choppy. After a few seconds, it froze and the screen was all low-rez looking and I could see what I can only describe as strange pixelation or scan lines (with a few of them moving from the top of the screen down to the bottom in a continuous loop). The only way to get it to stop was another battery pull.
I tried to use fastboot to get back in and reflash to the original firmware, but I kept getting a usb error (didn't have that when I first unlocked the bootloader using a mac, so not sure what the problem was). Now, the phone won't get passed the Google logo and just sits there for 30+ minutes without making any progress (that I can see). I keep trying to get back into the bootloader using fastboot, but now it won't even do that.
I've contacted Samsung/UK (as that's where mine originated), but don't think I will be getting any help based on their initial response. And, since my bootloader is unlocked, that probably voided the warranty anyway. I have no idea what happened, but it seems like some sort of combination of hardware/software problem. So, basically I'm screwed and out $700.
Click to expand...
Click to collapse
That's awful man. I've been reading more and more about random reboots happening with this phone and what not.. I just don't know what to think right now, I thought this was supposed to this beast of a phone and now after only a couple of months, it has completely stopped working for no apparent reason at all. Pretty lame, and this has definitely never happened to me before as I always take care of my phones. I just figured that if something were to happen to this phone, it would be from my own doing, just as it has been with every other phone that I've ever owned (ie from modding, from a drop, etc.). Samsung gets a thumbs down from me, I paid a lot of money to get this phone and now I'm going to be stuck with a refurb because they have put out a crap product.
As for you, I wouldn't even tell Samsung that you unlocked it. They probably won't be able to tell if you did or not since the phone won't boot properly. They should offer you a refurb, so you'll be in the same boat as me. I went into Verizon today and that's the best that they could do. I have to wait til Monday for it to come in the mail. I'm stuck without a phone til Monday.
volsey said:
Similar thing happened to me, it rebooted itself, as it has been doing quite a bit of lately, and then wouldnt turn on no matter what I did.
Eventually just help the POWER and VOL DOWN button together to reboot, and it worked fine again. I'm completely stock wtf.
Click to expand...
Click to collapse
Yeah, it's looking like this phone has been giving many people similar problems. Samsung must have let a bad batch slip out or something. I was completely stock as well, no unlock, no root, no custom rom, just a plain old basic user here and mine took a dump on me.
Mine does this about every other day and I have to pull the battery and restart, sorry to hear yours won't reboot. Ouch
It looks like I've got serious sleep of death issues. Here's what's happened so far.
I got the phone on Thursday afternoon. As soon as I started it up, it performed an update to 4.0.4. After entering my account info, a bunch of my old apps were restored and I installed a few more. Thursday night, the phone froze in sleep mode and I couldn't wake it up. Pulled the battery and everything was fine, didn't think too much about it.
Friday I got two similar lock ups, one in the afternoon and one at night. Had to pull the battery both times. I uninstalled any apps that I was no longer using or did not use too much.
Saturday three lock ups! Once while connected to the wall charger. At this point I uninstalled every downloaded app and powered the phone off overnight.
Sunday morning (today) I got a lock up in the morning and finally did a factory reset and did not allow any old apps to be imported. The only thing I have installed now, besides the stock apps, is Google Voice. And my phone just locked up again...
Is there anything else I can do at this point or should I just send this back to Google for a replacement?
Try to do a clean install ... or wipe your cache and Dalvik cache
and your bone stock I would DEFINately bring it back ive installed countless roms and kernels and never pulled battery yet you didnt need to spend your money on a defective phone
irizwan said:
I believe theres a rouge app responsible .. try a clean install then don't install any apps then check
Click to expand...
Click to collapse
He just said he did this.
Anyways, try flashing a kernel and raising the minimum value slightly, saw this fix every SoD on the G2x forums. You'll need CPU Master or something similar.
I'm using CPU Master Pro, in case you were wondering.
Sent from my Galaxy Nexus using Tapatalk 2
Unroot and reroot. Problem should be solved.
Sarumiso said:
It looks like I've got serious sleep of death issues. Here's what's happened so far.
I got the phone on Thursday afternoon. As soon as I started it up, it performed an update to 4.0.4. After entering my account info, a bunch of my old apps were restored and I installed a few more. Thursday night, the phone froze in sleep mode and I couldn't wake it up. Pulled the battery and everything was fine, didn't think too much about it.
Friday I got two similar lock ups, one in the afternoon and one at night. Had to pull the battery both times. I uninstalled any apps that I was no longer using or did not use too much.
Saturday three lock ups! Once while connected to the wall charger. At this point I uninstalled every downloaded app and powered the phone off overnight.
Sunday morning (today) I got a lock up in the morning and finally did a factory reset and did not allow any old apps to be imported. The only thing I have installed now, besides the stock apps, is Google Voice. And my phone just locked up again...
Is there anything else I can do at this point or should I just send this back to Google for a replacement?
Click to expand...
Click to collapse
Install a custom kernel and change your minimum CPU to 700mhz. Fixed my sods. Honestly though I'd go for an exchange.
Sent from my Galaxy Nexus using xda premium
Please update as i am planning on getting a gnex from the play store soon and would like to know what happens
Sent from my SAMSUNG-SGH-I897 using XDA
Toad858 said:
Please update as i am planning on getting a gnex from the play store soon and would like to know what happens
Sent from my SAMSUNG-SGH-I897 using XDA
Click to expand...
Click to collapse
Just get the Gnex, geesh. There's lemons with every product, not just phones.
Sent from my Galaxy Nexus using Tapatalk 2
Might be a bad Sim card
Thanks for the advice everyone. I ended up contacting Google who transferred me to Samsung for an RMA. During the course of the call, they had me try to reset the phone from recovery mode and I found that my phone can't go into recovery mode. Holding VolUp + Power resulted in a regular system boot. If I go to fastboot and try to enter recovery, I just get a little droid lying down with a red triangle and exclamation point.
At this point I'm thinking that first upgrade to 4.0.4 must have been corrupted somehow. I'm looking at trying to reflash it via Odin since I'm not looking forward to a week or more without a smartphone and the fact that the Samsung rep made me a little nervous by the number of times she said "might", "maybe" and "possibly" when talking about not charging me for a second phone during the RMA process.
Sarumiso said:
Thanks for the advice everyone. I ended up contacting Google who transferred me to Samsung for an RMA. During the course of the call, they had me try to reset the phone from recovery mode and I found that my phone can't go into recovery mode. Holding VolUp + Power resulted in a regular system boot. If I go to fastboot and try to enter recovery, I just get a little droid lying down with a red triangle and exclamation point.
At this point I'm thinking that first upgrade to 4.0.4 must have been corrupted somehow. I'm looking at trying to reflash it via Odin since I'm not looking forward to a week or more without a smartphone and the fact that the Samsung rep made me a little nervous by the number of times she said "might", "maybe" and "possibly" when talking about not charging me for a second phone during the RMA process.
Click to expand...
Click to collapse
To go to Bootloader mode requires VolUP+VoldDOWN+Power button
suggest returning defective phone
You phone seems defective.
I realize you don't want to send it back, but getting stuck with a bad phone can drive you crazy.
When I bought my Evo 3D phone a year ago, after the update, it started to reboot at random times. After talking to their support, with no solution, I insisted on a new unit.
Once I got the new phone, I had no problems ever again.
Now I have the Galaxy Nexus, and I used it a lot the first few days to make sure it wasn't defective.
I hope you can find a solution, but if you don't, consider getting a new unit. It's not worth the hassle of keeping a questionable unit.
Have u tried to unroot yet??? It fixes all the problems u could possibly have.
Use Wug's toolkit to fix this issue.
This morning I woke up and went to switch on my Acer A100 to no avail. The power button will light up blue and the home button will light up, but the screen is black.
I first tried the paperclip reset, and worked all the way up to a hard reset, but the problem persists.
Thinking I could possibly just reflash the ROM (I'm running the ICS Gen1 ROM I downloaded from XDA (which worked for the last several months)), I went to plug my Acer into my computer running Windows 7, and heard a strange noise. My tablet is showing up in APX mode, which from what I have read may be helpful for me to start fixing this thing.
However, I'm having trouble finding the drivers I'd need to start doing further troubleshooting.
Any help that could be provided would be greatly appreciated.
Hopefully this isn't a lost cause, because I've certainly voided my warranty by flashing ROMS in the past, correct? I've had the tablet for less than a year, and have been generally dissatisfied with it (it gets sluggish, doesn't always charge correctly, and generally acts strange).
The same thing recently happened to me, no screen but the blue light was on. I had to send it in to Acer. I also had a custom ROM on my tablet but they fixed it for free ad sent it back, so its worth a try. If it doesn't show the boot screen I don't think they can tell.
nsmith4 said:
The same thing recently happened to me, no screen but the blue light was on. I had to send it in to Acer. I also had a custom ROM on my tablet but they fixed it for free ad sent it back, so its worth a try. If it doesn't show the boot screen I don't think they can tell.
Click to expand...
Click to collapse
Good to know. Thanks.
MarkBell said:
Good to know. Thanks.
Click to expand...
Click to collapse
Exact thing happened to me. Sent it to acer. Fixed under warrenty. Still had to pay shipping one way though.
MarkBell said:
This morning I woke up and went to switch on my Acer A100 to no avail. The power button will light up blue and the home button will light up, but the screen is black.
I first tried the paperclip reset, and worked all the way up to a hard reset, but the problem persists.
Thinking I could possibly just reflash the ROM (I'm running the ICS Gen1 ROM I downloaded from XDA (which worked for the last several months)), I went to plug my Acer into my computer running Windows 7, and heard a strange noise. My tablet is showing up in APX mode, which from what I have read may be helpful for me to start fixing this thing.
However, I'm having trouble finding the drivers I'd need to start doing further troubleshooting.
Any help that could be provided would be greatly appreciated.
Hopefully this isn't a lost cause, because I've certainly voided my warranty by flashing ROMS in the past, correct? I've had the tablet for less than a year, and have been generally dissatisfied with it (it gets sluggish, doesn't always charge correctly, and generally acts strange).
Click to expand...
Click to collapse
Sounds like a dead emmc. Since it is not bootable, acer will not know if you were flashing roms, send it back... :good:
They have to be getting a ton of these dead tabs back, so I doubt they even waste time looking anymore.
Same thing happened to me. Just sent it into Acer Repair yesterday.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Romman0 said:
Sounds like a dead emmc. Since it is not bootable, acer will not know if you were flashing roms, send it back... :good:
They have to be getting a ton of these dead tabs back, so I doubt they even waste time looking anymore.
Click to expand...
Click to collapse
Wow this really seems to be happening often with the Acer A100. Happened to me just yesterday, Tab was working great there were no signs of problems or at least none that I could tell then out of the blue the Tab just froze up forcing me to Power down by holding the power button for xx number of seconds and never booted up again. Only thing that comes on the screen the the Acer logo screen.So what does dead emmc mean, does it just mean the system died or is there any detailed info on what it really is?
BlueIce said:
Wow this really seems to be happening often with the Acer A100. Happened to me just yesterday, Tab was working great there were no signs of problems or at least none that I could tell then out of the blue the Tab just froze up forcing me to Power down by holding the power button for xx number of seconds and never booted up again. Only thing that comes on the screen the the Acer logo screen.So what does dead emmc mean, does it just mean the system died or is there any detailed info on what it really is?
Click to expand...
Click to collapse
Its been explained a few times, notably in the bricked thread. Its partial erasing of the emmc which corrupts the gpt. What causes it is unknown, and Acer won't admit to it or help us with it or even talk about it.
Sent from my Galaxy Nexus using Tapatalk 2