Can anyone help me? I installed a program called gallery refresh and it didn't seem to do anything. Then my A100 started running very slow, so I rebooted it. Now it won't come on! It goes to the ANDROID screen, and it's animated, but it just stays there forever. One time it started up after about 15 minutes but it went really slow then just froze. Now it won't boot up at all. Just the Android logo. Is my A100 bricked? I still had important information on there. Is there anything that can be done or can I save my data off the internal sd card??
Thank you.
rrand said:
Can anyone help me? I installed a program called gallery refresh and it didn't seem to do anything. Then my A100 started running very slow, so I rebooted it. Now it won't come on! It goes to the ANDROID screen, and it's animated, but it just stays there forever. One time it started up after about 15 minutes but it went really slow then just froze. Now it won't boot up at all. Just the Android logo. Is my A100 bricked? I still had important information on there. Is there anything that can be done or can I save my data off the internal sd card??
Thank you.
Click to expand...
Click to collapse
Now it's stuck at the green "acer acer acer acer" screen. It doesn't seem to be doing anything at all.
It's worse now...
I read some instructions on another site to clear the Dalvik cache and I tried it. Now all I get when I turn on the A100 is a black screen. I think it's really bricked now.
The acer logo is back now. I accidently forgot to put the external sd card back in it. It now boots up to the Acer logos, but that's it.
Need more info, what rom, recovery, etc?
pio_masaki said:
Need more info, what rom, recovery, etc?
Click to expand...
Click to collapse
Stock ICS, rooted, CWM recovery.
I went into the CWM settings and told it to do a Backup and on the next blank screen, the android came up with a spherical thing in his tummy that's rolling about. I'm not sure what that means. There is no indication of how long the backup will take, or even where it's putting it, or whether it works at all. I don't know how long it lasts.
Does Android have a safe mode you can somehow get to?
rrand said:
Does Android have a safe mode you can somehow get to?
Click to expand...
Click to collapse
Goto a100 general sticky section, there is a dedicated brick thread with some things to try.
Sounds like the good old emmc failure to me though, and if it is, everything is lost, data, motherboard, TOTAL LOSS.
Sent via my Sosei "III" Bakedbean Iconia A100.
---------- Post added at 02:22 AM ---------- Previous post was at 02:18 AM ----------
Also, there is a difference between emmc failure or just bricking by say a bad flash.
Suggest reading the wealth of guides here.
Sent via my Sosei "III" Bakedbean Iconia A100.
Last thing you can try is booting back into recovery and try to adb pull off your internal SD. Not likely to work, but worth a shot. Stop rebooting and wiping it, you'll just kill it faster, wait until after you get what you can off of it.
Then do a factory reset. It'll likely just not finish or reboot or go to Andy on his back again, never know.
Sent from my HTC DNA
Now it won't work at all. I didn't do anything to it, just went to sleep and when I woke up it wouldn't turn on. Been on the phone with Acer. They won't allow me to send it in for repairs because I'm three months out of warranty.
rrand said:
Now it won't work at all. I didn't do anything to it, just went to sleep and when I woke up it wouldn't turn on. Been on the phone with Acer. They won't allow me to send it in for repairs because I'm three months out of warranty.
Click to expand...
Click to collapse
That sucks, Acer probably put only a year of warranty on because of their stupid eMMC chip. Thank god we are moving towards eSata now. I'm hopefully buying a Surface Pro.
Sent from my A100 using xda app-developers app
plznote said:
That sucks, Acer probably put only a year of warranty on because of their stupid eMMC chip. Thank god we are moving towards eSata now. I'm hopefully buying a Surface Pro.
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
I think a year is the standard time for devices, though IMO once this defect became known they should have recalled or extended the period, instead they just replace it with the same buggy board and kick it back out to die later for good.
Sent from my HTC DNA
Yes, I was very peeved. Acer wouldn't even fix it for money. They said I could not send it in. Thankfully, my note program was synced to Google. I thought for sure I lost it! I was feeling sick about it all night. Today I bought a Nexus and it synced right back up. I was so relieved. It was by far the most important data on the device. So I'm done with Acer now. Hope my Nexus will be better. Thanks for your concern, guys.
Same here. But I got on with acer chat and got bumped up to level 2.and they are fixing for free and paying for shipping. Out of warranty since March.
Sent from my SCH-I535 using Tapatalk 4 Beta
ontiuoW 368
Cporcelli said:
Same here. But I got on with acer chat and got bumped up to level 2.and they are fixing for free and paying for shipping. Out of warranty since March.
Click to expand...
Click to collapse
Thank you so much for posting your experience with Acer! If I had not seen this, I would not have even tried to get service since my warranty expired Nov 2012! But I guess because my problem was the dead emmc issue, I got bumped to Level 2 support and they authorized my return/repair immediately, including sending a FedEx shipping label to send my tablet to them! (Still waiting on the email with the shipping label, but I expect it shortly.)
So if you have a dead emmc, contact Acer chat service anyway, regardless of warranty! Their Level 2 support hours are 8:00 AM - 4:45 PM CST, Mon-Fri. Just go through support chat and they will transfer you through!
Related
Hi,
About 1,5 months ago I received my first Android phone, a Galaxy Nexus.
I have unlocked the bootloader, rooted it en eventually installed Clockwork Mod Recovery following guides on this excellent forum! Everything went perfectly and it ran very smoothly in that state for about half a month up until yesterday.
I didn't have any custom roms installed, so I received the notification for the Android 4.0.2 update, it failed because of Clockwork Mod which I later found out. So I set about to manually install it, I downloaded the image from the google site and placed it in my home directory on my Phone, when I then wanted to restart to start in recovery mode it didn't do anything.
I tried getting the battery out and in, sim card out and in, recharging it,...
It does nothing, not even a small vibration signaling the phone is trying to start.
Anyone has any ideas to fix it, or might it be possible to send it back to the shop ( even though it is rooted etc. ?)
Thanks in advance,
Exatto
You need to get the stock images and flash using Odin or the ADB/Fastboot method. After which the phone will return to stock. Then you can root and do what you like. Lots of guieds on here on how to do it. Good luck.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
By the way if you send back a rooted phone they will tell you to take a jump. Rooting voids the warranty.
No response at all? A real brick?
Sent from my Galaxy Nexus using xda premium
Can you get into download mode? If you can you can use any of the methods above to sort it.
I don't think there is a real brick. There are restore images. Extremely hard to brick a nexus...borderline impossible.
Yeah I have never heard of a "real" bricked Nexus.
jd1001 said:
Can you get into download mode? If you can you can use any of the methods above to sort it.
Click to expand...
Click to collapse
No, that's the point. I can't get in any modes. It does't react at all. I think it might be a hardware fault, a friend suggested it might be due to a short circuit battery.
I just followed this guide (http://forum.xda-developers.com/showthread.php?t=1419170) to update, using method 1, having clockwork mod installed. And when I shut it down to restart in recovery mode it suddenly stopped reacting. I have had this before, but then taking the battery in and out fixed everything. Now it doesn't anymore.
Cool, well if removing the battery for a few minutes doesnt sort it then you should be able to return it because the carrier won't be able to tell if it is rooted if they can't turn it on.
When you charge it do you get the charging battery icon when you press the power button?
stkiswr said:
I don't think there is a real brick. There are restore images. Extremely hard to brick a nexus...borderline impossible.
Click to expand...
Click to collapse
But I can't do anything with a restore image when I can't even get it started, let alone be recognized by my computer?
P.S.: Sorry for the late reply, but apparently I still have to wait 5 minutes in between posts.
Can you see the charging battery icon when the phone is off and plugged into the wall?
jd1001 said:
Cool, well if removing the battery for a few minutes doesnt sort it then you should be able to return it because the carrier won't be able to tell if it is rooted if they can't turn it on.
When you charge it do you get the charging battery icon when you press the power button?
Click to expand...
Click to collapse
No, not a charging sign. I hope I can return it, but what if the battery is faulty and they just pop a new one in and then see that it is rooted?
Thanks for the help.
Could well be a dead battery dude, if you have a mate with a Nexus you could try yourself first. I know what you mean about the guy in the shop seeing the unlocked bootloader if he tried a different battery but you may be lucky in that he might not know what it is or you could just grab the phone and leg it ha ha
I hope it gets sorted and be sure to post here what happens. Take it easy.
jd1001 said:
Could well be a dead battery dude, if you have a mate with a Nexus you could try yourself first. I know what you mean about the guy in the shop seeing the unlocked bootloader if he tried a different battery but you may be lucky in that he might not know what it is or you could just grab the phone and leg it ha ha
I hope it gets sorted and be sure to post here what happens. Take it easy.
Click to expand...
Click to collapse
Thanks, hope it get's sorted out. Have to send the phone back, because it was imported, so no chance of legging it
Will post the outcome.
As promised the followup:
Luckily they didn't notice my GN was rooted etc. as today I received a brand new one after I sent the broken one in to an official Samsung repair center
I did test some things before I sent it in though, a friend just bought a new one and we tested if my battery worked in his phone (it didn't) and we tested his working battery in my phone (it didn't work either), so something was definitely very screwed up.
Haven't got any idea of what went wrong eventually as the repair service didn't offer any details, although I am off course glad I got a brand new one.
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
(NOTE THAT I AM ONLY EXPLAINING IN *DETAIL SO THAT SOMEONE MAY BE ABLE TO CORRECTLY ANALYZE THE PROBLEM)
Okay, so I got my new AT&T Samsung Galaxy S III less than a month ago.
My friend helped me in the past few days to root and install cyanogenmod 10. Everything was still fine, until I did something in some kind of pixel density changing app. When rebooting, it only showed the Samsung and Samsung Galaxy S III screens when booting up, but went no further. I wiped everything and restored the last backup I made (advanced restore). Everything ran fine again, with all the original factory stuff. I decided to try and see if I could reinstall cm10 (wiped everything, installed zip, rebooted), and it was successful. Then I decided I wanted to wipe that and try out Energy HD 2.0. Once trying to install the zip, it returned an error message and aborted. I then decided to scrap that idea and just go back to the original factory rom and everything. So I once again wiped and restored my last backup. Upon hitting Reboot, it just went black and didn't turn on again. Now I am completely unable to turn it on, charge it, go into cwm recovery, or download mode. Plugging into the computer just pops a driver install message for QHSUSB_LOAD. Never has anything, even the LED, so much as blinked.
Can somebody please help me? I just would like to know if there is a way to get it working. I'd be very grateful, thanks!
*detail, meaning just what I was doing, as I do not remember exact error codes and such.
Try reflashing. What stock image are you using?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
kinghorsey said:
Try reflashing. What stock image are you using?
Click to expand...
Click to collapse
Is it even possible to re-flash a recovery image (from Odin3) when the device cannot enter download mode?
I think it may have been CWM Recovery v5.0.4.2 or something that I originally installed/flashed (can't check right now though, because I was kicked off my computer). Then it had upgraded to v6.something later on my phone.
((Sent from my stupid old iPhone 3Gs))
Look into jtag service
sent from outside ur window
twanskys204 said:
Look into jtag service
sent from outside ur window
Click to expand...
Click to collapse
Haha, okay. I just don't want to spend $60 at this very moment.
Sent from omygoshwhatthehellareyoudoingoutthere
stupid iPhone
Ascyndaeon said:
Haha, okay. I just don't want to spend $60 at this very moment.
Click to expand...
Click to collapse
Yeah I would say your bootloader is messed up and the only way to breath life back into your phone is jtag repairs. I had a problem identicle to yours and I searched the net for a week solid trying to figure out how to fix it without having to fork over the money.. but alas had to send it. Luckily the guy who provides the repairs is amazing at what he does. Phone will be back in your hands within a few days if you're from the states.
fallenkirmit said:
Yeah I would say your bootloader is messed up and the only way to breath life back into your phone is jtag repairs. I had a problem identicle to yours and I searched the net for a week solid trying to figure out how to fix it without having to fork over the money.. but alas had to send it. Luckily the guy who provides the repairs is amazing at what he does. Phone will be back in your hands within a few days if you're from the states.
Click to expand...
Click to collapse
Hmm, okay. I wonder then why only JTAG Repairs knows how to fix this stuff, and the information isn't widely available.
And so if I do send it to jtag, then I guess I'll be getting it back within a few days, 'cause I live in the US.
Thanks for your input.
Ascyndaeon said:
Hmm, okay. I wonder then why only JTAG Repairs knows how to fix this stuff, and the information isn't widely available.
And so if I do send it to jtag, then I guess I'll be getting it back within a few days, 'cause I live in the US.
Thanks for your input.
Click to expand...
Click to collapse
Well there is a way for you to do the jtag repairs yourself... but i wouldn't touch the process with a 10 foot pole lol... I would rather let a pro do things like that... just youtube jtag repair and take a look at some of the process.... way beyond my comprehension atleast..
fallenkirmit said:
Well there is a way for you to do the jtag repairs yourself... but i wouldn't touch the process with a 10 foot pole lol... I would rather let a pro do things like that... just youtube jtag repair and take a look at some of the process.... way beyond my comprehension atleast..
Click to expand...
Click to collapse
Ah, I suppose you're right. Not to mention expensive. That equipment probably costs more than having them fix it. Though it would probably be worth it of you bricked it on a regular basis.
First off my device is unlocked and rooted but that is it and I did that weeks and weeks ago when the latest android patch came out.
It has been working fine but I had a sleep over with the kids last weekend and they like to play with it as usual. After they left, hours later I noticed the device showing the google start screen like it was stuck there. I tried to get it into the boot loader or recovery and nothing. Now it appears dead, no lights, etc.
I tried charging and tried using the volume and power thing, etc to no avail. When connected to the pc I am gettng the dreaded QHSUSB_Dload thing.
#First question is there a fix for this? I have searched every where and have yet to find anything substancial other than the volume thing which is not working.
# second question is can I rma this or will it not be accepted due to it being rooted? There is no way I can bring it back to stock without accessing the bootloader.
#last question - If I cannot rms it can I take it apart and do something to repair it or is there anything I can do?
Thanks guys. This really sucks. i have never had an issue up until now and this thing is totally stock besides being rooted and unlocked.
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2381582
That will not work with a hard brick. I cannot get into bootloader or adb.
Sent from my Nexus 4 using xda app-developers app
Bump
Do you guys think I can do an RMA?
Sent from my Nexus 4 using xda app-developers app
Thanks for the outpouring of support here. :banghead:
I think it is clear I'm screwed.
Pretty unbelievable as I'm all stock except for recovery.
Sent from my Nexus 4 using xda app-developers app
Richieboy67 said:
Bump
Do you guys think I can do an RMA?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'd try to send it back for repair. What do you have to lose?
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Richieboy67 said:
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I understand that, but right now you have a $200 paper weight. So why not gamble on the s/h for the rma?
I think you are misunderstanding what I am saying.
Google basically makes you pay for a replacement. Upon inspection they refund the money. If they do not refund the money then I am out the full cost.
I could find that reasonable if I was playing around or something but I have kept my devices all stock ever since the latest version came out except for unlocking and rooting.
I guess the other option would be to find someone to do a jtag repair and I could only find one guy and I don't think he touches Nexus 7s. Not sure though but waiting for him to reply. This sucks! My device was perfect and I loved it.Great battery, no touch screen issues. Not a single issue and then all of a sudden this. i really cannot understand what caused it.
Thanks for the reply. I really figured there would be others this happened too but everyone gets Hard Brick mixed up with soft brick and every hard brick post I read is not a hard brick. Hard Brick = F#cked :crying:
I gotcha. I thought you paid to send it back & then you had the option to pay to fix it if it wasn't covered by warranty.
That could be through Asus directly but not sure.
I think though if they go to repair it they will see the unlocked boot loader. That voids the warranty
Sent from my Nexus 4 using xda app-developers app
If it was mine I would take the back cover off and unplug the battery and let it sit for ~5 min. If there is a physical reset plug then push that in a couple times.
dkryder said:
If it was mine I would take the back cover off and unplug the battery and let it sit for ~5 min. If there is a physical reset plug then push that in a couple times.
Click to expand...
Click to collapse
Yeah, if you know an RMA is a very very very poor shot / don't want to try it. I guess a tear down is your second best bet.
You should check out Adam Outler's tear down videos if you feel you might be able to take this on. I'll link Outler's videos below. They MAY help you in deciding if you want to go through with it (and what you may expect to see).
http://www.youtube.com/watch?v=RMzi4K_PwPs (Transplant Nexus 7 Boards)
http://www.youtube.com/watch?v=QOFpY1nXFew (Nexus 7 Unboxed the XDA way)
Thanks guys.
I finally got an email back from those guys that do Jtag repairs and he said it was a hardware issue but I am not sure if he understood my issue.
I do not think taking it apart and unplugging the battery will work here if the bootloader is corrupt. I am going to try to let the battery go completely dead though and then try to do the volume/power key thing to see if there is any chance.
I do not know much about this but what I read is that if the bootloader is stopped somehow while loading it can become corrupt in some cases and you cannot do anything without it and there is a device specific key involved. That is why only someone with some specific software can fix it. I thought this key as called Jtag but again, I do not know much about this. The Jtag guy said it was hardware.
Man, I have an Hp touchpad that I got years ago. I installed Android on it years ago and have it overclocked it to over 1700mhz and that thing is still going strong. The kids even dropped it and it has a crack in the screen and it still will not die. Here I have a Nexus only a few months old fully stock except for root and unlock and it is dead. Kills me especially after the way I always stand up for the Nexus line. Still loving my Nexus 4 though and it is well over a year old. Oh well, if that one goes like this one I am jumping off a high bridge. :laugh:
Richieboy67 said:
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am confused as to why you are so sure what is wrong with it, how do you know the bootloader is corrupt if you claim no wrong doing. Also technically speaking you did do something to begin with, you knew full well that you would be voiding the warranty by rooting and installing a custom recovery. More than likely if kids messing with it actually did end up with it how it is now they probably accepted an OTA and it corrupted the boot, on the LG G2 they have figured out how to delete the FOTA information that it continuously tries to boot from and return normal boot sequence.
But I reiterate you cannot blame this on anyone but yourself right now, being angry with ASUS or the kids will do you no good. You knowingly voided your warranty now it is time to put your nose down and see if you can fix it, there are a lot of resources here to do such.
whoamanwtf said:
I am confused as to why you are so sure what is wrong with it, how do you know the bootloader is corrupt if you claim no wrong doing. Also technically speaking you did do something to begin with, you knew full well that you would be voiding the warranty by rooting and installing a custom recovery. More than likely if kids messing with it actually did end up with it how it is now they probably accepted an OTA and it corrupted the boot, on the LG G2 they have figured out how to delete the FOTA information that it continuously tries to boot from and return normal boot sequence.
But I reiterate you cannot blame this on anyone but yourself right now, being angry with ASUS or the kids will do you no good. You knowingly voided your warranty now it is time to put your nose down and see if you can fix it, there are a lot of resources here to do such.
Click to expand...
Click to collapse
First off, I am not sure what is wrong with it which is why I am posting here. I stated numerous times that I do not know much about this.
And yes, I know this that rooting and unlocking voids the warranty. I also know that it is my fault for doing it but I have been doing it for around 3 years now and have used various roms and kernals in the paqs and have never had an issue. Perhaps it is a hardware issue. I just do not think this issue was caused by me.
In terms of the kids playing with the device. They play games, things like that. The desktop is locked and they have no access to settings or anything. When I said messing with it I just meant playing games though sometimes they open new games and leave the old ones running. I do not know how that would cause this.
There was no ota or update.
I am not sure what you are saying about LG.
And again, I am not angry with Google or Asus. My point was that this issue was most likely not caused due to rooting or unlocking and an ota would not cause a dhsusb issue even if it did go bad.Lets try to remember that nearly everyone here roots, unlockes and installs roms, etc. I have done so as well but not on this device. This one I wanted to keep pretty much vanilla but I wanted to be able to use Titanium back up, etc. And also, I rooted and unlocked months ago when I first got the device and had to root again when the latest version came out which was awhile ago.
In terms of fixing I have not found a solution for this. I do not know if it is a hardware issue or a software issue. That is why I am posting here. I am looking for some information from people who know this stuff. I know nothing but what I have read and so far I have read many different things. I am here to learn.
OK so here is what I meant with the G2..
I had a stock/rooted/TWRP G2 and half asleep accepted an OTA Update, when it does this it downloads the update into a partition that the device checks before booting. Because I had the custom recovery obviously the update failed but it left that code in the boot partition that would now allow me to even get into download mode. See this post here for how it was fixed http://forum.xda-developers.com/showthread.php?t=2582142
I am not sure if this would be the same problem or how to go about fixing it because of the device difference, but maybe it could help? I didn't mean to come off as a ****, just far too many people like to get into their devices and void the warranty then blame everyone else.
It is really not difficult to pull the back cover off and unplug the battery, I suggest doing this it could very well help just be careful not to crack the back while pulling it off, a credit card/ID and a butter knife should do the trick without leaving marks.
No worries. I appreciate the help.
I agree with you totally.
Sent from my Nexus 4 using xda app-developers app
In not an expert at unlocking phones or anything but I think my phone has the bootloader issue. At times it freeze and then either stays frozen for a bit 5 - 10 min or so it then reboots itself, it I'll rest the phone to get it unfrozen. It is doing it multiple times a day and becoming more and more frequent.
Does this mean that I'm getting closer and closer to complete failure, and I need to back up everything in the phone and get replacement.
The warranty from Google is over. Bought October 2015. I may have extended warranty through my credit card. What would all of the experts on this suggest?
I would love any and all help and suggestions.
Sent from my Nexus 5X using Tapatalk
Well Surprise surprise. Google said they would replace. I'll send it back and set of the phone they send didn't have the same problem. Can I get a wahoo! Happy dance.
Sent from my Nexus 5X using Tapatalk
If you send it for repair, will your personal data get wiped or do they send it back all intact?
KTroopA said:
If you send it for repair, will your personal data get wiped or do they send it back all intact?
Click to expand...
Click to collapse
They will probably replace motherboard, so internal storage will not be the same.
gingus7 said:
In not an expert at unlocking phones or anything but I think my phone has the bootloader issue. At times it freeze and then either stays frozen for a bit 5 - 10 min or so it then reboots itself, it I'll rest the phone to get it unfrozen. It is doing it multiple times a day and becoming more and more frequent.
Does this mean that I'm getting closer and closer to complete failure, and I need to back up everything in the phone and get replacement.
The warranty from Google is over. Bought October 2015. I may have extended warranty through my credit card. What would all of the experts on this suggest?
I would love any and all help and suggestions.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I had the same issue, though my phone is dead. I had actually gotten it to where I could ADB the firmware, and it eventually got pretty far into the 4 colored circles until it started bootlooping. Now, it is completely dead.
I had just backed up my photos, but I did lose other app data that I had not backed up recently. Not a whole lot since most apps now backup online these days. But if I get a replacement LG phone, I will always backup on a schedule.
There was an XDA article where LG has a class action against it for the G4 for using solder that doesn't hold up to the heat or heating/cooling cycles. The 5X was added to that lawsuit as well as other phones in April.
This is the first phone that has actually died on me since I dropped a Nokia 8320 into water. I even have my Motorola V600, Razr, BB 8320, and more recent phones that all still work. It amazes me that LG hasn't figured out how to fix this problem since it seems to affect a lot of their models.