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.
Related
Long time lurker, not much of a poster here in the S4 forums (former owner of S2 and Motorola Atrix, rooted and had lots of ROM fun with both until they crapped out).
In speaking with Samsung, AT&T, and Best Buy reps I may have found a potential way for all of you wanting to get back from 4.3, 4.4.2 NB1, or NC1 back to 4.2.2.
I expressed my phone's constant operational issues since moving from 4.2.2, and was essentially given the go ahead to visit an AT&T service center (not your standard AT&T store, but one of their direct service facilities that have many more technical resources and serviceable personnel) and they would reflash the phone from scratch with the original 4.2.2 software to attempt to "fix" my phone. If this is the case, the workaround the locked bootloader/Knox/Qcode might just be available wouldn't you all think?
I have an appointment with them tomorrow afternoon and will update as I am able to.
airforcerg said:
Long time lurker, not much of a poster here in the S4 forums (former owner of S2 and Motorola Atrix, rooted and had lots of ROM fun with both until they crapped out).
In speaking with Samsung, AT&T, and Best Buy reps I may have found a potential way for all of you wanting to get back from 4.3, 4.4.2 NB1, or NC1 back to 4.2.2.
I expressed my phone's constant operational issues since moving from 4.2.2, and was essentially given the go ahead to visit an AT&T service center (not your standard AT&T store, but one of their direct service facilities that have many more technical resources and serviceable personnel) and they would reflash the phone from scratch with the original 4.2.2 software to attempt to "fix" my phone. If this is the case, the workaround the locked bootloader/Knox/Qcode might just be available wouldn't you all think?
I have an appointment with them tomorrow afternoon and will update as I am able to.
Click to expand...
Click to collapse
Unless they exchange your phone, I doubt they'll get 4.2.2 on it. The reps are not very educated and probably just said that not knowing. So unless you get an exchange, this probably won't bring anything. Not to mention if all S4's suddenly come in for service that'll be suspicious.
Sent from my SGH-I337 running BlackBox 3.0
@Surge1223 maybe there's something he can possibly find out?
hope this isnt a dream thread. but which 4.2? though mf3 or mdl?
I don't know what you expect @Surge1223 to tell you. He wouldn't know anything about this. I can say though that from what I have read around here, it's impossible for AT&T to downgrade your device. Maybe OP will get lucky, but I bet they were just telling him something to get him to move on, because they couldn't solve his problem. Who knows though, I may be completely wrong. Wouldn't be the first time.
Maybe if they actually do work on his phone in person surge would have a question/s to possible ask whoever is working on his phone, of course unless they give him a refurbished device
Brooklynsour said:
Maybe if they actually do work on his phone in person surge would have a question/s to possible ask whoever is working on his phone, of course unless they give him a refurbished device
Click to expand...
Click to collapse
This. At best he will get a new/refurb device with MF3 on it.
There's no trick any tech can do to allow reversion to MDL, short of replacing the entire motherboard.
jeboo said:
This. At best he will get a new/refurb device with MF3 on it.
There's no trick any tech can do to allow reversion to MDL, short of replacing the entire motherboard.
Click to expand...
Click to collapse
Sadly this appears to be the case. The at&t rep I spoke with earlier this week was clearly incorrect. Within the past 3 months it appears that all device service centers have been recently outfitted with updates to their flashing system that ONLY includes the NB1 software. They tried to explain to me that no downgrade potential even exists, and that neither Samsung nor att (whether they may have the software existent in some form within their databases) "can", but obviously won't perform any downgrade of android software.
They've essentially created just another "failsafe" to prevent any further changes.
my apologies for getting anyone's hopes up.
You're good bro. We all figured that was the case.
Hi folks,
My Shield 32 GB just arrived and is charged up. I've signed on with a google account and done nothing else.
I will eventually root it but want to put it through its paces for a month or so first.
It arrived with KK 4.4.2 (wow! so old!) on it. It offers an OTA update from October 2014. Says it is OTA 1.21. I've seen LOTS of other OTA numbers much later around these forums. Do I have to take the 1.21 OTA before I can get to the more recent ones?
And, by taking the OTA, am I doing anything irreversible that I probably shouldn't do, since I'm eventually a rooting and maybe ROMing kind of guy?
Thanks. I've read up and it looks like I probably want to go all the way to the 5.1 release, once they sort out the speaker-killing bug. But for the moment I'd like to make sure I'm not missing anything before taking the OTA.
Thanks!
Marc
I decided to download the update after I successfully activated the device on AT&T's cellular network.
That was a bit of a hassle... couldn't do it from the device (the ATT app said something about incompatibility with the SIM card), the PC online web registration wouldn't accept it because NVidia Shield wasn't listed in the device types, and it took the efforts of 3 ATT folks to get me activated. First one passed me to the second one when he found out it was a device not purchased from ATT (but... dude... here's the SIM and IMEI number that's all you need...), the second one set me up and told me to call another number to accept terms and conditions. Did that, still no joy, found the default APN isn't set up right. Fixed that, still no joy, eventually talked to person 3 that found out they didn't attach a data plan to the device when they set it up... as part of my family shared data account. Duh.
Anyway, I applied the 1.21 and then it prompted me to download the 2.1 update to Android 5.01. It has downloaded. I think I want to copy it over to my PC before I let it apply.
Marc
Hmmm. Poked around and found the 1.21 update but not the 2.1 full LTE OTA. Perhaps I'd need root to get at the files. Oh well. I can always download it if I need it. Applying the 2.1 update now.
And I've made it all the way to the 2.2.1 hotfix. Seems stable enough for the moment.
I understand OTA 3.0 got pulled; so I guess I'll be staying on Lollipop 5.01 until they release the fix.
It's a bit surprising that I had to do all the updates sequentially and that there wasn't any direct-to-the-latest. But it didn't take long. I wonder if all these OTAs are clogging up my memory somewhere?
OK, on to exploration!
Marc
the update got pulled indeed, caused all kind of problems, including blown speakers
nvidia employee told us on nvidia forum they would release a new OTA 3.1, targeted end of june
lastest news: it's now targeted end of july....
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.
Bought a shield tablet from a guy on Craigslist. Turns out it's the older one with the bad battery and the recall for this serial number has already been claimed (big surprise)! Is there anything I can do to fix this tablet besides just buy another one and making sure it has the right battery? Hard lesson is learned.
The seller stated that this WAS the replacement tablet. I don't know if that's true, but it does have TWRP installed and is unlocked. After some searching, I saw that nvidia says the new battery model might not show up if the device is modified. I.e., not 100% convinced I got scammed. Only about 99%! . I'm scared to try to update with a ROM now because of it. The build is from August of 2015
apollyon0810 said:
The seller stated that this WAS the replacement tablet. I don't know if that's true, but it does have TWRP installed and is unlocked. After some searching, I saw that nvidia says the new battery model might not show up if the device is modified. I.e., not 100% convinced I got scammed. Only about 99%! . I'm scared to try to update with a ROM now because of it. The build is from August of 2015
Click to expand...
Click to collapse
If it boots to twrp thats awesome. Be positive .. Take your time search, ask and find out all possible scenarios. Kill- Swich is a good tobic to search about.
UPDATE: It's all about the bootloader.If it's Unlocked you are saved.
I got everything updated and am running the latest TWRP and Bliss ROM. Everything is working fine, I just don't know how concerned I should be about the battert.
As mentioned read the kill switch thread.
From what I could tell, if my bootloader is unlocked and I'm on a third party ROM, I should be golden. Am I mistaken?
Well first off find out if you have the bad battery or not. And second look at the threads regarding replacing that pack with others imho you could find a broken screen k1 model put the battery and Mobo in your pyro have the stylus and the new board...
did the killswitch activate or can you boot into fastboot?
****DISREGARD I GOT IT TO WORK SOMEHOW. NOT REALLY SURE WHAT THE TRICK WAS. THROW ENOUGH MUD AT THE WALL, SOME OF IT'LL STICK!!!***********
Hi, my kid fried his S7, so I bought an SM-G930V on ebay, naively thinking it would have the Verizon software. Well, it boots up as T-Mobile. And yes, the back of the unit is engraved "SM-G930V". so it was born as a Verizon device!!!
So after 4 frustrating hours, and one miraculous un-bricking of the device, I'm still stuck on T-Mobile. I'm reading lots of threads and at this point they're all running together in m head. One said something like "the bootloader is locked, don't even bother". But if that is the case, how did someone at some point convert this from Verizon to T-Mobile?
Odin keeps throwing the "Fail! Auth" when I try to download the 4 Verizon ROM files that I downloaded. I read many, many threads about that error. I tried about 20 different cables (yeah, I'm a pack rat!) to no avail.
So at this point, before I spend/waste more time on Odin troubleshooting:
1- Would a "locked" bootloader prevent me from loading the Verizon ROM on a physical SM-G930V that has been converted to an SM-G930T?
2- How can I tell if my bootloader is "locked"??
3- Am I barking up the wrong tree here? Should I just try to get the seller to take the phone back and replace it with one that already has the Verizon ROM?
Thanks!!
I guess I shouldn't discount the possibility that this is a Frankenphone, and someone salvaged the back of a verizon unit and attached it to a T-Mobile chassis...but I guess that would be a longshot....
Locked bootloader will prevent downgrades, so if the firmware you were trying to flash was slightly behind what your phone had it could have been the cause. Glad you got it sorted.
Aha, that may be it, thanks for shedding some light! The first VZ software I tried was from a static link as the SanFirm utility wasn't working (maybe the back-end was down, who knows) and had a datestamn of 06/25/2018; several hours later the SamFirm thing worked and gave me a set of files dated. 03/12/2019. I have no idea what the baseline T-Mobile software was, but I figure it HAD to be newer than the June 2018 date.
Thanks again!