Related
I just spoke with the Android dept at AT&T who where I spoke to a gentleman named Jeremy Everson. After he informed me that I was the 6th caller he had had in the past 3 hours about the failing updates...he called Samsung on a 3-way conversation with me.
Here's what I found out. If you DO NOT HAVE GPS, EMAIL OR MMS PROBLEMS...THEN THE UPDATE MAY BRICK YOUR PHONE. THIS IS ATT AND SAMSUNGS RESPONSIBILITY AND THEY ARE GOING TO FIX IT.
AT&T IS WORKING DILIGENTLY WITH SAMSUNG AND MR. EVERSON INFORMED ME THAT THEY ARE FRUSTRATED AT THE BLURRY COMMUNICATION WITH SAMSUNG OVER THIS UPDATE.
All in all...there are no answers yet as to why this update isnt working...but we know that it is causing problems.
Basically, what that tells me is stop resetting, odin-ing, unrooting, and reflashing...it is a problem on Samsungs end...not your device.
fiendiish said:
I just spoke with the Android dept at AT&T who where I spoke to a gentleman named Jeremy Everson. After he informed me that I was the 6th caller he had had in the past 3 hours about the failing updates...he called Samsung on a 3-way conversation with me.
Here's what I found out. If you DO NOT HAVE GPS, EMAIL OR MMS PROBLEMS...THEN THE UPDATE MAY BRICK YOUR PHONE. THIS IS ATT AND SAMSUNGS RESPONSIBILITY AND THEY ARE GOING TO FIX IT.
AT&T IS WORKING DILIGENTLY WITH SAMSUNG AND MR. EVERSON INFORMED ME THAT THEY ARE FRUSTRATED AT THE BLURRY COMMUNICATION WITH SAMSUNG OVER THIS UPDATE.
All in all...there are no answers yet as to why this update isnt working...but we know that it is causing problems.
Basically, what that tells me is stop resetting, odin-ing, unrooting, and reflashing...it is a problem on Samsungs end...not your device.
Click to expand...
Click to collapse
That doesn't help those of us with completely bricked phones...
qwertyaas said:
That doesn't help those of us with completely bricked phones...
Click to expand...
Click to collapse
Contact Samsung 1800 726 7864. That's the number I was given by AT&T to call. Or, take your phone to an AT&T store. You did nothing to brick your device. This is their issue.
We have the choice to not do the update, right? I think I read that from another thread somewhere, but I just wanted to double check. I haven't received a notification from AT&T yet about the update, but when I do, I don't think I want to go through with it seeing how there are a lot of issues with the update.
"AT&T does not provide technical support for the Samsung Captivate update and makes no warranties, express, implied or statutory, as to the content within this solution; such content is provided "as is" and with all faults, and your use of the content is at your own risk. "
this is a mess
Oh mannnn...after reading your painful story with AT&T & Samsung...all I want to say to those people is "F*** YOU!!".
WTH have you guys been doing for 2 months???
You have spent 2 months to come up with the phone bricker not the problem fixer???
I really want to switch to Android world but it seems starting with Samsung is one hell bad idea of mine. Maybe I should wait for the phones from other makers.
well... at least they're aware that there is an issue
Well.. if you think about it, as soon as we rooted our units.. there goes AT&T's responsibility.
That's the thing I noticed the most about AT&T, they are pros are shifting to blame to anyone but themselves.
If you're under the 30 day return policy return it ASAP, No hesitation, talk to a manager if necessary.
For those over 30 days hope for the best, make AT&T and Samsung aware of your issue.
I just got off the phone with AT&T they are sending me a new phone. Spent about 45 minutes on the phone doing through all of test they do to try and get the update. The tech I talked to is actually overnighting me a new phone. I had to agree to the terms that there is no physical damage or liquid damage. There is none.
I claimed my GPS failes to aquire a viable signal. Network tower triangulation is not acceptable. I waited passed the 30 days for this update that was promised and I can no longer get.
I have used ODIN in the past and believe something with it is causing the problem. Before I ever used odin I had a backup made of my entire phone with just a root.
Tried to use ODIN and restore my previous ROM with no luck still failing at 50%. I have removed all traces of lagfix, root, roms and still can not get the update to take. I even swapped out the SIM card at the store. All of it failed so the tech had them rush me a new phone.
thehavock18 said:
I just got off the phone with AT&T they are sending me a new phone. Spent about 45 minutes on the phone doing through all of test they do to try and get the update. The tech I talked to is actually overnighting me a new phone. I had to agree to the terms that there is no physical damage or liquid damage. There is none.
I claimed my GPS failes to aquire a viable signal. Network tower triangulation is not acceptable. I waited passed the 30 days for this update that was promised and I can no longer get.
I have used ODIN in the past and believe something with it is causing the problem. Before I ever used odin I had a backup made of my entire phone with just a root.
Tried to use ODIN and restore my previous ROM with no luck still failing at 50%. I have removed all traces of lagfix, root, roms and still can not get the update to take. I even swapped out the SIM card at the store. All of it failed so the tech had them rush me a new phone.
Click to expand...
Click to collapse
Wow, so anyone getting this phone should really just wait for the phones that are pre-installed with this update already.
Sounds like Ill have to wait a few months then.
Thanks for the info.
fiendiish said:
Contact Samsung 1800 726 7864. That's the number I was given by AT&T to call. Or, take your phone to an AT&T store. You did nothing to brick your device. This is their issue.
Click to expand...
Click to collapse
I was within my 30 days so they gave me a new Captivate. Sadly, I haven't had a chance to back up my old phone so everything is gone from there.
For some reason, the AT&T employee said this uses my only 'exchange' in terms of warranty. I didn't even bother to argue as that makes no sense - how is replacing a bricked phone (that was bricked on an AT&T update) 'exchanging' the phone [as in being able to exchange to a different phone].
orlandoxpolice said:
"AT&T does not provide technical support for the Samsung Captivate update and makes no warranties, express, implied or statutory, as to the content within this solution; such content is provided "as is" and with all faults, and your use of the content is at your own risk. "
this is a mess
Click to expand...
Click to collapse
I would think that one could argue successfully to get a new phone regardless, because this update is being pushed to the phone and not voluntarily download (by some), I woke up to a message that the device had fail to connect to the server (thank god) for the update. but if they're updating your phone without your approval then they (whomever is pushing the update) can't absolve themselves of responsibility. unless my not reading the EULA leads to it saying something like, we can do what we want when we want and you can suck it!
fiendiish said:
Here's what I found out. If you DO NOT HAVE GPS, EMAIL OR MMS PROBLEMS...THEN THE UPDATE MAY BRICK YOUR PHONE. THIS IS ATT AND SAMSUNGS RESPONSIBILITY AND THEY ARE GOING TO FIX IT.
Click to expand...
Click to collapse
Not sure if that's true. I have GPS issues (Even outside on a clear night it took more than five minutes for me to get a lock). My phone is bricked.
A new one is on the way. Should be here tomorrow.
I recently picked up the phone but however had to send it to repair due to a constant rebooting issue (which much to my dismay i discovered a fix just a day after sending it). I believe it was sent to Future Tel and they re flashed my phone with a different version of ICS then my previous version. While I did not think much of this at the time it has recently become apparent that the current Jelly Bean roll out is only heading to phones with the system version 492002. However my phone is on 49003. Will my phone ever receive the ICS update and is Rogers/Fido aware of this? Is there any way be able to receive ICS without having to flash on new software and change system files. I have contacted Motorola support but they have not gotten back to me. I am very happy with the phone, however i would very much appreciate the new update. Any and all help is appreciated. Thanks.
genboxboy said:
I recently picked up the phone but however had to send it to repair due to a constant rebooting issue (which much to my dismay i discovered a fix just a day after sending it). I believe it was sent to Future Tel and they re flashed my phone with a different version of ICS then my previous version. While I did not think much of this at the time it has recently become apparent that the current Jelly Bean roll out is only heading to phones with the system version 492002. However my phone is on 49003. Will my phone ever receive the ICS update and is Rogers/Fido aware of this? Is there any way be able to receive ICS without having to flash on new software and change system files. I have contacted Motorola support but they have not gotten back to me. I am very happy with the phone, however i would very much appreciate the new update. Any and all help is appreciated. Thanks.
Click to expand...
Click to collapse
You're not the first person to report this issue... I believe the wrong firmware was loaded in the Motorola download program for a long time.
I just made a tutorial for this, maybe you want to try it out?
http://forum.xda-developers.com/showthread.php?p=38765124
Let me know how it works!
PS the firmware file you're looking for is here : http://sbf.droid-developers.org/van...12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml.zip
Rogers and Fido use the same firmware, but the phone is able to adapt based on which SIM is installed.
Thanks for the help. Quick question though, will flashing new software on make me loose my warranty and also does it require root access ? I have a feeling a gut feeling that i may brick my phone during this as this was the reason i had to send it to repair in the first place .
I recently wrote to Motorola about this and they responded with "Thanks for reaching out to Motorola. I have reviewed your e-mail, and I am ready to help. I apologize for the delay and any inconveniences you're experiencing. Please note that Motorola stands behind our products by offering one year warranty from the date of purchase. This warranty does not cover physical or liquid damage. Based on your email, we recommend sending the phone to Motorola to be reflash with the Jelly Bean software update. Please drop the phone along with a copy of the proof of purchase off at your local service carrier store, so that it can be shipped to Motorola centre for repair , and return within 5-7 business days from when we receive it. If the phone is determined to have suffered physical or liquid damage and deemed not repairable, it will be shipped back to you unrepaired." along with a bunch of other info on getting my phone to repair. I will probably just wait a bit to make my decision. Thanks anyways.
genboxboy said:
Thanks for the help. Quick question though, will flashing new software on make me loose my warranty and also does it require root access ? I have a feeling a gut feeling that i may brick my phone during this as this was the reason i had to send it to repair in the first place .
I recently wrote to Motorola about this and they responded with "Thanks for reaching out to Motorola. I have reviewed your e-mail, and I am ready to help. I apologize for the delay and any inconveniences you're experiencing. Please note that Motorola stands behind our products by offering one year warranty from the date of purchase. This warranty does not cover physical or liquid damage. Based on your email, we recommend sending the phone to Motorola to be reflash with the Jelly Bean software update. Please drop the phone along with a copy of the proof of purchase off at your local service carrier store, so that it can be shipped to Motorola centre for repair , and return within 5-7 business days from when we receive it. If the phone is determined to have suffered physical or liquid damage and deemed not repairable, it will be shipped back to you unrepaired." along with a bunch of other info on getting my phone to repair. I will probably just wait a bit to make my decision. Thanks anyways.
Click to expand...
Click to collapse
My tutorial doesn't require root, and will not void the warranty on your phone, in fact it is almost the same process that Motorola uses when repairing your phone. If you have any questions, please let me know.
Sent from my Nexus 7 using Tapatalk HD
I have a P6810 that was imported from Hong Kong by Expansys. My warranty is valid until August 25, 2013. The screen has a problem where it sometimes intermittently flashes dark lines on the screen. Full screen vertical lines. It's really just like those columns of pixels aren't being lite up to the same degree as the others, and not as brightly as they should be.
It doesn't do it all the time, but it has become more frequent, and it appears in all applications as far as I can tell. I have not yet reloaded the firmware because personally it seems like more of hardware problem. Either the LCD or the LCD driver is failing.
The only place that seems to be willing to work on it is Samsung Warranty Repair in Hong Kong, and they do not accept devices that have been shipped to them for repair. All warranty repair work there must be hand delivered. I'm in Hawaii and that is not an option. Expansys is of no use. They just said contact Samsung Hong Kong Warranty Repair.
Is there anybody that works on the P6810 state side? How much does it cost to replace the LCD or the motherboard? Does anybody know? It will cost me at least $60 just to ship the thing back to Hong Kong anyway, so I'm willing to investigate other options, but I don't know what they are for a specialty item like the P6810.
me too on p6800..
i have the same issue here but i am not sure if it is really hardware fail as i am using custom erobot rom v2.3
Thank you for the response
Salamonti said:
me too on p6800..
i have the same issue here but i am not sure if it is really hardware fail as i am using custom erobot rom v2.3
Click to expand...
Click to collapse
Thanks for the response. With only 2 of us responding so far it's hard to know if its just because a Super AMOLED of this size is a new technology, and there were still some bugs not worked out in the processing, or if it is as you say, and as I'm hoping, just a software issue.
My P6810 hasn't done it at all for about 2 weeks now. I'm hoping that when Ice Cream Sandwich is pushed out, that it will solve the problem once and for all.
My findings were that since mine is a p6810, it won't be fixed under warranty, and Samsung won't fix it even if I pay for it, unless I hand deliver it to Hong Kong. If I'm confident that the problem is the hardware (I'm not), then I have to buy a used p6800 on eBay and try to fix it myself. I'm not going to do that.
If yours is a p6800 couldn't it have been fixed under warranty in the U.S.? I wonder if your erobot rom 2.3 is using the same graphics driver code as Jelly Bean? In other words, was erobot rom v2.3 a custom ground up recode of everything, or did they cannibalize Jelly Bean for sections of code?
I love my p6810. I'm in Hawaii and don't have TV. I read on it every morning and watch movies on it almost every night. It's the perfect 7" tablet in my opinion, but that display issue drives me crazy.
I guess one of the morals of the store is to not trust Expansys if they tell you that they have a grey market item that is fully covered under the manufacturers warranty. They told me that, but it was not true.
i am not in US and my tb is not covered by warranty either (as i am in Egypt)
my custom rom is built on JB 4.1.2
but i know nothing about display driver so i cant figure it out
Thanks
Salamonti said:
i am not in US and my tb is not covered by warranty either (as i am in Egypt)
my custom rom is built on JB 4.1.2
but i know nothing about display driver so i cant figure it out
Click to expand...
Click to collapse
Thanks for your response. When Ice Cream Sandwich comes out, I will reply about whether or not it fixes the problem.
Arobase40 said:
Some clues you may investigate on...
On the technical aspects :
- You can try to do a factory reset and see if that solve your display issue.
- Try to flash any official ROM : HC or ICS even though this is a European version.
- If the display issue is still there, then you can consider this as a hardware failure. I don't know how Law works in your country, but you could try to find a non profit organization specialized in juridical procedures which could help you in forcing Expansys to support the warranty procedure... ^^
---------- Post added at 11:38 PM ---------- Previous post was at 11:33 PM ----------
Unless you are a good developer or a very good modder and you like to play dice, don't even try to use the eRobot rom with your P6810...
Click to expand...
Click to collapse
Thanks Arobase40.
I will probably wait until ICS comes out and then factory reset and install/upgrade to ICS immediately.
On Expansys, just as a matter of justice, I wish I could force them to do something, but my warranty expired on 8/22/13. They wouldn't answer their phone and only responded to one of several emails, saying "Contact Samsung". I think the most effective thing I can do is just let other members of xdadevelopers know what happened to me relative to Expansys.
Thanks for your input Arobase40, I appreciate your suggestions.
Arobase40 said:
I don't really understand your position about your GT 7.7 ???
As you were talking about P6810, I assumed you were talking about the International version, right ???
Then, as I said you could flash a European firmware with PC Odin as I don't think Samsung will deliver any further updates/upgrades... ^^
But whatever, and again you could simply do a factory reset to see if that solve your issue...
But if you already used a Cyanogen firmware, then just forget everything about what I said, and forget about your warranty as well... ^^
I don't understand what the members of xdadevelopers could do for you relative to Expansys, except suggesting you to contact your local non profit organization, if there is one (should be existing) ?!?!?!
Which Expansys is it ? A US one or any others ???
You have to write them an official letter as "Registered Letter with Acknowledgement of Delivery" to make things official so the warranty will be extended "indefinitely" until Expansys solve your problem...
But again, get informed yourself about your local rules or laws !!!
I got a similar problem with ASUS, as my TF101 returned 3 times in their repair center and the last time they "lost" it (it was stolen on the way to the Repair Center)... ^^
ASUS accepted to pay me back the price I paid for it but refused to compensate the prejudice as they awaited a very long time (about a month) before they just started to investigate on what happened to my device... ^^
I first wanted to go on trial with ASUS, but I tried first an official transaction with the help of a retired judge (as member of a non profit organization)...
So they finally accepted to compensate an additional 250 € of the initial 540 € price I paid (got a 60 € discount from official price)... So I got 790 € and didn't pay anything for a lawyer or for the Trial procedure...
On the other hand, if we were going to a Trial, ASUS knew they will loose and would have to pay MUCH MUCH more...
YOU are the only one to know if you want to take your chance...
Click to expand...
Click to collapse
Thanks Arobase40,
Yes I am talking about a Hong Kong version. It arrived default in Mandarin(?).
The only ICS 4.2.2 version I could find was P6810XXLPL_CSC_XEU with is the United Kingdom version. I’ve downloaded it. My preference is to use this one so that my P6810 defaults into English. I do plan to use Odin for this (probably this weekend).
My planned strategy is to do a factory reset to positively flush everything out, and then use Odin to update to ICS 4.2.2. My preference is to do everything at once, and only once, because even though I have Titanium Backup installed and running, my experience with my Nook was it still took several hours to get everything setup correctly after a factory reset.
I don’t have Cyanogen firmware installed, as my goal in getting at P6810 was to buy the best, and therefore not have to spend much time mod’ing it. I have rooted though so that I could install fonts with diacritical marks.
In terms of alerting xdadevelopers to Expansys policies, the best way to get Expansys to change their policies is enough people give them feedback during the purchasing process. If I had been able to read a post like this prior to my purchase of my P6810, I would have asked more questions and made a few phone calls, and I would have been better informed and wouldn’t have purchased from Expansys unless that had been able to give me some kind of further assurance that they would stand behind the product if it was required.
Yes it was the Expansys in the U.S. It’s the one you find on the internet when Googling within the U.S..
Thanks for the suggestion on the “Registered Letter with Acknowledgment of Delivery”.
Part of the problem is that for the past month, my P6810 hasn’t displayed the problem. I’m confident that it’s coming back sometime in the future, and probably worse, but intermittent problems are tricky to demand repairs on. If the “Registered Letter with Acknowledgment of Delivery” would get me an indefinitely extended warranty though, it could be worth it. It kind of boils down to a question of how much time would it take me versus other options. I’ll have to think about it. In any case, thanks for your suggestions.
I will try to go ahead and factory reset, then update to ICS 4.2.2 this weekend and see what happens. Actually, interestingly, my P6810 tells me that it has ICS 4.2.1 installed right now, as of early July. That surprised me when I saw it yesterday because I don’t remember that happening. I certainly didn’t do it. But maybe that’s why the screen problem went away?
Arobase40 said:
GOTCHA !!!
Sounds like there are many confusions with your explanations... ^^
1) ICS is Android 4.0.x !!!
2) 4.1.2 or 4.2.2 are Jelly Bean Android versions !!! NONE of them are available for P6810 yet and will probably never be... ^^ Yes I know, I'm very defeatist and somewhat negative in my position, but Sammy will maybe prove I was wrong...
3) If your device tells you have ICS 4.2.1, then there is something wrong somewhere !!! ^^
This is the first thing you'll have to investigate on...
4) NO ONE as P6800 or P6810 owners got a 4.2.2 Android versions, and we will most probably never get such versions... ^^
5) On Expansys policies and responsibilities concerns : have you fully been informed they would send you a H.K version when you bought this device ??? Check at this when you ordered it and what your delivery and invoice mentions/forms...
6) There may be a slight chance, but go on the Samsung US website to find out the Phone number or the mail address by which you can contact them and described your issue (after you're fully sure about the real Android version you have...) and ask them for help/support and/or a RMA to send your device for repair. They will tell you if they accept to take your device under warranty to a US repair center... ^^
In Europe, we are probably better protected against juridical aspects compared to the US, but we obtain less as damages when we win while in the US you can get MUCH MUCH more if you can afford a Trial...
7) But before going that far : backup up all your internal storage (including the Titanium Backup folder) onto your hard disk computer or an external USB HDD...
8) Optionally, use Kies to backup up all your data and apps.
9) Make sure your battery is fully charged.
10) Get into your Settings and in the Backup and Reinit tab option and select "Re establish default param" (I'm unsure about the real words, as I don't have a US/English firmware version, but you should find out...
It shouldn't be that long before it'll reboot and ask you to reconfigure your Tab.
11) Don't reinstall anything and take awhile and your time to check & assure that solve your display issues. Update your default apps with Google Play and see if that's still good...
12) Finally you'll have 2 options : restore everything with Kies or copy back the Titanium Backup folder from your backup place to the internal storage, download TB and restore everything.
If after the restore you encounter the same display issues again, then you'll know you must not do a full restore, but just your apps... ^^
13) Before you try to update/upgrade or flash anything, make sure which firmware version you're downloading and installing !!! LOL
Good luck !
EDIT : when you buy anything anywhere better is to read the terms and conditions of the Online retailers... ^^
http://www.expansys-usa.com/terms/
In the European or French Expansys website, they can't do what they want as European/French rules & laws better protect customers against such illegal restrictions !!! ^^
I guess you should have consumers organizations as the ones I was referring earlier at your place, when needed...
Click to expand...
Click to collapse
Thanks Arobase40,
1) You're right. I've just checked and its 4.0.4 installed. ICS was an update I made shortly after I purchased the unit. Since there will be no JB for the P6800/P6810, there's no point in my waiting for it.
5) There was no indication that an HK version would be sold/shipped. Also it does not indicate that anywhere on the receipt. I knew it would be a non-U.S. version, because Samsung only sells the P6800 within the U.S.
6) I tried asking Samsung's U.S. warranty repair center if they could repair it, but they go by model numbers, and the P6810 is not one that they will touch. Same thing with the U.K. Samsung Warranty Repair Center, they said that the serial # indicated that it wasn't made in the U.K., so they could not work on it. I couldn't even find anyone in the U.S. who sells parts (i.e. LCDs) for it, it's such a speciality item.
7 - 13) Thanks for the detailed steps. Since I realize now that I was completely confused about the version of my firmware, I realize that for sure, I'm going to have to do one or all of the steps you have outlined.
Thanks again!
My AT&T LG G4 got stuck in bootloop today 810, ser. number 505, H/W 1.0, on 10o, no root, all stock. Apparently this is a hardware problem that has been affecting more and more G4 owners:
http://forum.xda-developers.com/g4/help/lg-g4-stuck-bootloop-t3268734
Called up AT&T, and they're sending another G4, which is the only way to fix this. Warranty will continue through the end of the original G4.
UPDATE: Received the replacement G4 from AT&T. Unfortunately another 505 serial number, H/W 1.0, with 10o.
Yea that happened to me too... I bought it at launch weekend. Replaced under warranty
Sent from my LG-H810 using Tapatalk
Yep just happened to mine the other day. was look at a forum web site and the phone locked up then boot looped. called the att warranty center and they sent me a "like new" one. positive not about the new one it was manufactured 12/23/2015 according to https://imeidata.net/warranty/lg
Add another AT&T variant to the failure list. Mine froze and went into irrecoverable bootloop Saturday night. It's on the FedEx truck now to the LG Ft Worth Repair center. The more research I've done, the more I'm seeing it's a common hardware issue. I'll be posting mine for sale the second I get my replacement or "repaired" phone back. I'm back to using my first gen Moto X and I forgot how smooth it ran. I think I'll be getting the X Pure Edition to replace the G4.
is there a way to factory reset the phone. my phone just died this morning and i just spoke to ATT they will be sending a replacement. not sure if my phone rooted will void anything
Another AT&T fail. Mine died a week ago. Serial 505. Lasted 8 months. Replacement is also a serial 505.
SN 806
Ive seen some posts and I have had this happen to day halfway to a meeting and lost my gps and contacts. I have an 806 serial and anything to save it would be great. I dont know how to get to dload mode or I might try something more.
My friend's G4 AT&T fails to. She asks me to help her but there is no way to make it work. Really confused. The problem is she buy the AT&T version, and then buy the unlock code to make it the international one. Now she stays in Vietnam, not US, how can we get the warranty ?
that isn't good. so this just happens randomly? I'm on 10o all stock with 505.
Same here. Happened the morning of January 28 (1/28). Started bootlooping. It would sometimes get past the AT&T logo, but most of the time bootlooped at the LG logo. AT&T did an overnight replacement which was a much newer hardware version. So I'm suspect based on the HW version this was a new phone not a refurbished. Still 5.1 (no marshmellow). It has been flawless. Even taking my 128GB microSD which failed to work on the previous hardware - which would spontaneously software eject.
AT&T said it was probably related to the Android 6.0 marshmallow update. The store rep said that I was the 6th person to come into the store with the same issue. The tried factory reset themselves with no avail. Then had a phone overnighted to my home.
Sure sounds like a hardware issue with the H810.
Hey guys,
I have a confirmed fix that i applied to a friends phone.
It involved opening the phone up and applying pressure to one of the chips.
Will post video/more info for those who are interested.
Skedgy sky said:
Hey guys,
I have a confirmed fix that i applied to a friends phone.
It involved opening the phone up and applying pressure to one of the chips.
Will post video/more info for those who are interested.
Click to expand...
Click to collapse
Please post this video!
Skedgy sky said:
Hey guys,
I have a confirmed fix that i applied to a friends phone.
It involved opening the phone up and applying pressure to one of the chips.
Will post video/more info for those who are interested.
Click to expand...
Click to collapse
YES PLEASE POST THIS VIDEO!! And please in the mean time give us more info until you can post the vid!!!!
petermg said:
YES PLEASE POST THIS VIDEO!! And please in the mean time give us more info until you can post the vid!!!!
Click to expand...
Click to collapse
Some of the other G4 boards here on XDA show G4's that have been disassembled, and the motherboard is baked in the oven for several minutes. This apparently melts and the resin or adhesive that holds the chip that is causing problems. After heating up, the chip apparently re-seats itself, at least temporarily, allowing the phone to boot up. Apparently it's easy to get the G4 apart, but that probably would affect your warranty. At least you could get valuable info off the phone if that was absolutely necessary.
wified said:
Some of the other G4 boards here on XDA show G4's that have been disassembled, and the motherboard is baked in the oven for several minutes. This apparently melts and the resin or adhesive that holds the chip that is causing problems. After heating up, the chip apparently re-seats itself, at least temporarily, allowing the phone to boot up. Apparently it's easy to get the G4 apart, but that probably would affect your warranty. At least you could get valuable info off the phone if that was absolutely necessary.
Click to expand...
Click to collapse
Link? I've not run into any of these posts showing anyone baking a G4 board!
petermg said:
Link? I've not run into any of these posts showing anyone baking a G4 board!
Click to expand...
Click to collapse
http://forum.xda-developers.com/g4/help/diy-h815-usa-variant-hardware-boot-loop-t3311623
Bake away!
There are some other tips on the last couple of pages of this original thread on the bootloop problem, too:
http://forum.xda-developers.com/g4/help/lg-g4-stuck-bootloop-t3268734
Same here guys . LG G4 BOOTLOOP STUCK .. . Now I have a cheap phone ( Alcatel idol 3 ) wich works better than lg .and super fast unfortunately front can not good as lg ...bit is OK my lg is now at garbage RIP. LG G4
Mine's a 508... However it still affected me, when I called LG they said it's probably an update, however it never completed it. TurnOn > Freeze > BootLoop. Looking at the PR Distributor cause well.
Can you believe Claro PR (my carrier) didn't accept it cause it has a bruise on the top right edge (metal side, not even the screen), when I asked LG for repairs (phone call) they said they won't take it either (the first time I called), the 2nd time I called they said they wouldn't take it cause the LG-H810PR is apparently an International version, and so I needed to look up with My Carrier (Claro, yay...) ultimately, I read this >> http://www.androidauthority.com/lg-admits-g4-bootloop-problem-hardware-fault-669603/ << And it led me to PR's LG Distributor and hopefully they'll do a repair or give me a replacement. If they don't, well you'll see me doing a topic.
wified said:
My AT&T LG G4 got stuck in bootloop today 810, ser. number 505, H/W 1.0, on 10o, no root, all stock. Apparently this is a hardware problem that has been affecting more and more G4 owners:
http://forum.xda-developers.com/g4/help/lg-g4-stuck-bootloop-t3268734
Called up AT&T, and they're sending another G4, which is the only way to fix this. Warranty will continue through the end of the original G4.
UPDATE: Received the replacement G4 from AT&T. Unfortunately another 505 serial number, H/W 1.0, with 10o.
Click to expand...
Click to collapse
Where is the serial located ? I have my box.. tried to call local AT&T & they said they considered the IMEI to be the serial..
Would like to confirm if the one I got is a 505 or not..
Mines a 509 just shut off in the middle of chromecasting from plex, and just loops at the LG logo. I got it as a replacement in December for my G3 that randomly died. I going to fight ATT to send me something other than another G4.
Ok, so I happened upon an LG G4 H810 AT&T variant at a pawn shop a few weeks ago, they couldn't get it working because of the boot loop issue (person that pawned it probably did so knowing it was defective and had it working just long enough to demo it to get the cash). I took a look at it, great shape overall, no damage noted, plain old "ceramic" back cover, battery had a date of January 15 2016 on it so it's tough to say if the battery was just newer or the device itself since I couldn't get it to boot. Date code was 508 so obviously one of the well known defective models.
Long story short: got it for a pittance because they couldn't get anyone else to buy it, got it home, registered it at LG's website on my account, waited 2 days then chatted their support up and got them to accept it for RMA, shipped it out last week and it should be back tomorrow. I'm not sure if they repaired it or replaced it - the limited info I have says they "Swap Board (Main/RF)" so I'm guessing the entire motherboard was swapped for (hopefully) a newer one made this year that might not fail but probably will.
So, I had a question or two and I've done quite a bit of research the past few days and never found specific answers so at this point I'm just going to ask them and be done with it:
1) There's apparently no working root at all for the H810 that I've been able to find. I'm going to assume that the unit I'll be getting tomorrow or Tuesday will have been upgraded to Marshmallow unfortunately but that's just how it goes so there's no rolling back as I understand things. If there's a working root I'd be interested in knowing which one that happens to be. Also with no root there's probably no recovery either but I will keep researching to find out more as I'm able.
2) There's apparently no custom ROMs available because of the locked bootloader which will never get unlocked obviously as well. I've read that the PR (Puerto Rico) ROM could be installed on an H810 that was still running Lollipop with the v2 rollback but if this repaired board is Marshmallow that means it's been upgraded to v3 rollback and so that's dead in the water too.
3) I'm also going to assume that if the board has been replaced and hopefully is one made in 2016 (with a 6xx serial number) then it could last a while but there's no guarantee of it. I've seen people say the 6xx versions have not failed but then I find a post or two from someone that claims to know someone with a 6xx model and it failed at least once on them but I can't get any actual verification on it, that's just hearsay to me if there's no direct proof so all I can do is continue hoping it's a 6xx revision board and that it's not going to fail anytime soon.
This will be my second G4, had a Sprint variant last year and never had problems with it, sold it to a gent from Australia when he visited Las Vegas and as far as I know he's still using it, who knows.
If anyone can offer some info related to those questions I'd be grateful so thanks in advance if anyone can.
Have fun, always...
EDIT:
Seems that if I get very lucky and the replacement board comes with H81020n on it - the original Marshmallow build - there's a chance I can roll it back to H81010o using the TOT method from the other thread for it, that would at least get me root potential I suppose. Guess I'll find out tomorrow if the replacement arrives. Can't find any absolutely verified info about later builds, looks like the very latest patch build is H81022b from September and I'm going to assume if that happens to be on the board then all hope is lost, basically. Ugh...
br0adband said:
Ok, so I happened upon an LG G4 H810 AT&T variant at a pawn shop a few weeks ago, they couldn't get it working because of the boot loop issue (person that pawned it probably did so knowing it was defective and had it working just long enough to demo it to get the cash). I took a look at it, great shape overall, no damage noted, plain old "ceramic" back cover, battery had a date of January 15 2016 on it so it's tough to say if the battery was just newer or the device itself since I couldn't get it to boot. Date code was 508 so obviously one of the well known defective models.
Long story short: got it for a pittance because they couldn't get anyone else to buy it, got it home, registered it at LG's website on my account, waited 2 days then chatted their support up and got them to accept it for RMA, shipped it out last week and it should be back tomorrow. I'm not sure if they repaired it or replaced it - the limited info I have says they "Swap Board (Main/RF)" so I'm guessing the entire motherboard was swapped for (hopefully) a newer one made this year that might not fail but probably will.
So, I had a question or two and I've done quite a bit of research the past few days and never found specific answers so at this point I'm just going to ask them and be done with it:
1) There's apparently no working root at all for the H810 that I've been able to find. I'm going to assume that the unit I'll be getting tomorrow or Tuesday will have been upgraded to Marshmallow unfortunately but that's just how it goes so there's no rolling back as I understand things. If there's a working root I'd be interested in knowing which one that happens to be. Also with no root there's probably no recovery either but I will keep researching to find out more as I'm able.
2) There's apparently no custom ROMs available because of the locked bootloader which will never get unlocked obviously as well. I've read that the PR (Puerto Rico) ROM could be installed on an H810 that was still running Lollipop with the v2 rollback but if this repaired board is Marshmallow that means it's been upgraded to v3 rollback and so that's dead in the water too.
3) I'm also going to assume that if the board has been replaced and hopefully is one made in 2016 (with a 6xx serial number) then it could last a while but there's no guarantee of it. I've seen people say the 6xx versions have not failed but then I find a post or two from someone that claims to know someone with a 6xx model and it failed at least once on them but I can't get any actual verification on it, that's just hearsay to me if there's no direct proof so all I can do is continue hoping it's a 6xx revision board and that it's not going to fail anytime soon.
This will be my second G4, had a Sprint variant last year and never had problems with it, sold it to a gent from Australia when he visited Las Vegas and as far as I know he's still using it, who knows.
If anyone can offer some info related to those questions I'd be grateful so thanks in advance if anyone can.
Have fun, always...
EDIT:
Seems that if I get very lucky and the replacement board comes with H81020n on it - the original Marshmallow build - there's a chance I can roll it back to H81010o using the TOT method from the other thread for it, that would at least get me root potential I suppose. Guess I'll find out tomorrow if the replacement arrives. Can't find any absolutely verified info about later builds, looks like the very latest patch build is H81022b from September and I'm going to assume if that happens to be on the board then all hope is lost, basically. Ugh...
Click to expand...
Click to collapse
I haven't kept up with root, but I doubt anything MM latest or not you won't be able to root it. Also never flash wrong model firmware like the PR version. In the past that was a last resort firmware (before we got a back to stock for the actual AT&T model. You could get lucky but chances are you'll get a board with the latest or just the last previous firmware especially if it has a newer serial.
Pretty much the AT&T G4 is a device you want if you don't tinker with the device. I honestly love the G4, until certain apps even new apps ran worse on the G4 than they do on my G2.
Sent from my iPhone using Tapatalk
Just got the H810 back, checking on the board info here in a bit (if I can even detect anything) but it's running H81022b so I'm guessing that means I'm stuck with it as is but that was somewhat expected. I'm not going to even bother attempting a rollback at this point, will just wait for the yellow leather cover to arrive in the next few days then I'll put it up for sale on craigslist I suppose and go from there.
I have to wonder exactly what they did because the board info that I can detect using the LG Info tool from the Play Store still lists the same info for board date/etc (January 2016) so I don't know what the hell they actually did.
Kinda sucks but it's how things go sometimes.