Related
All I want to do is flash back to stock, I feel like I am gonna lose my my mind or go buy a new phone. I have mostly spent a solid 10 hours of time trying to get it to work.
I have been endlessly looking, searching, trying all these different methods to get my ls980 to connect to my pc. So basically everytime I have hooked it up it comes up as unreconized or unknown device doesn't connect.
List of things: Latest LG mobile drivers I have installed them through there exe and tried to install them manually when the ! comes up on the device. I have tried my laptop and my desktop every usb in all of them. I have tried the stock cable, and about 8 other different cables. I have tried it in debugging mode with mtp and without debugging. I tried the support tool as well. Tried composite usb setting.
I guess I am at a loss at this point to what even to try besides sending it to be repaired. Which I don't feel like it's a phone problem and I am just missing something I can't find, I say this because the phone charges perfectly fine and no damage to the usb port at all. If anyone has good information or just a direction I can go will be greatly appericated.
Dirty Grimace said:
All I want to do is flash back to stock, I feel like I am gonna lose my my mind or go buy a new phone. I have mostly spent a solid 10 hours of time trying to get it to work.
I have been endlessly looking, searching, trying all these different methods to get my ls980 to connect to my pc. So basically everytime I have hooked it up it comes up as unreconized or unknown device doesn't connect.
List of things: Latest LG mobile drivers I have installed them through there exe and tried to install them manually when the ! comes up on the device. I have tried my laptop and my desktop every usb in all of them. I have tried the stock cable, and about 8 other different cables. I have tried it in debugging mode with mtp and without debugging. I tried the support tool as well. Tried composite usb setting.
I guess I am at a loss at this point to what even to try besides sending it to be repaired. Which I don't feel like it's a phone problem and I am just missing something I can't find, I say this because the phone charges perfectly fine and no damage to the usb port at all. If anyone has good information or just a direction I can go will be greatly appericated.
Click to expand...
Click to collapse
Is your device functioning normally, besides from this? Also, did you use the T-mobile drivers?
tabp0le said:
Is your device functioning normally, besides from this? Also, did you use the T-mobile drivers?
Click to expand...
Click to collapse
It works just fine, only notable thing that I never figured out was why OTA updates don't ever take, it's still on ZVC. I tried the T-mobile d802 drivers as it was suggested by another post I saw on here.
And you've removed all drivers to android and lg for it.
secret.animal said:
And you've removed all drivers to android and lg for it.
Click to expand...
Click to collapse
Correct, I uninstalled them, tried new ones a couple different ways from other posts, and removed them and tried again. Right now I just have them all uninstalled. Trying to figure out if it's something that's stopping it. In error I did forget that a couple times it reconized it but would :fail to start code 10.
Which version of windows are you running? On both desktop and laptop???
secret.animal said:
Which version of windows are you running? On both desktop and laptop???
Click to expand...
Click to collapse
Windows 7 64-bit home premium on both.
Dirty Grimace said:
Windows 7 64-bit home premium on both.
Click to expand...
Click to collapse
OK, that shouldn't be the problem. Zvc yet updates do not take.
Is it rooted?
And it is running on sprint network?
secret.animal said:
OK, that shouldn't be the problem. Zvc yet updates do not take.
Is it rooted?
And it is running on sprint network?
Click to expand...
Click to collapse
Long story short, it's on ZVC, even with other updates that came up it would never update past it. I took it into sprint several times they didn't know why, I did root it as one guy said that was an option, I used stump root, but then I unrooted as I felt I was getting into something too complicated. It is on the sprint network, about 90% of the time and all the times I tried to update previous to the root/unroot. But I am not trying to update it since the root, mostly trying to restore to stock and start overish.
I'm thinking maybe a virtual machine with Linux might find it. If it can then there is something. And maybe we can redo the partitions and such.
secret.animal said:
I'm thinking maybe a virtual machine with Linux might find it. If it can then there is something. And maybe we can redo the partitions and such.
Click to expand...
Click to collapse
I will check with a couple guys see if I can find someone with a machine with Linux this weekend. Thanks a lot for you on going help.
I have this phone at least for another year. So at least someone out here is still willing to help.
secret.animal said:
I have this phone at least for another year. So at least someone out here is still willing to help.
Click to expand...
Click to collapse
I was unable to find anyone outside local computer store that I know. Kind of problem finding that in rural midwest. I also tried installing drivers in vista compatability as that was suggested no luck..
Dirty Grimace said:
I was unable to find anyone outside local computer store that I know. Kind of problem finding that in rural midwest. I also tried installing drivers in vista compatability as that was suggested no luck..
Click to expand...
Click to collapse
As for driver removal, one thing I remember with the nexus devices. There is wugfresh nrt, nexus root toolkit. Let me see which application or program they loaded for removal before reinstall of drivers. I know they have 2 places you check into.
Dang, I'll have to try to load them via a windows emulator. I'm running Linux right now.
secret.animal said:
As for driver removal, one thing I remember with the nexus devices. There is wugfresh nrt, nexus root toolkit. Let me see which application or program they loaded for removal before reinstall of drivers. I know they have 2 places you check into.
Dang, I'll have to try to load them via a windows emulator. I'm running Linux right now.
Click to expand...
Click to collapse
Let me know.. I am kinda at the point where I might try to find someone to flash it back to stock, and just activated my old phone til it gets back.. like I am past the point of frustration and no legit just don't get why, since all my other devices have zero issues connecting.
Ok, so lets start with hello you wonderful smart people
I did something very stupid and I'm really hoping there is a solution to my foolishness.
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.
xSandmanx59 said:
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.
Click to expand...
Click to collapse
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.
epidenimus said:
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.
Click to expand...
Click to collapse
Thank you for the response. It's a surprisingly easy error indeed. Since I posted this, I figured out the key press you mentioned and have been trying ROM after ROM intended for my phone specifically, yet all of them will end one of 3 ways.
I get a black screen with itty bitty little text saying fastboot mode and restart.
I get everything ready and I boot up, it loads until about the wifi set up and then it will either freeze for a couple seconds and go to a black screen which requires a battery pull.
Or, I get a bsod with the options of volume up = dload and volume down = reboot.
So far I've tried candy5, CM 12.1/11, blisspop, paranoid android, cloudy, and dirty unicorn.
Not sure what I'm doing wrong with these. I use TWRP to wipe everything except external sd, install from there, reboot, and repeat.
I fixed it!! thanks to http://forum.xda-developers.com/sprint-lg-g3/development/rom-stock-zv6-base-odex-deodex-t2949087
this ROM is the only one I could find that worked. I'd still love to be able to upgrade to L but it seems like all of the 5.x roms crash during setup. Not sure what this is due to, but I have a working phone, so I'm not too upset by it.
If anyone has any info on why all the lollipop ROMs are having trouble on here I would appreciate it much.
Well it WAS fixed.... All was fine and well until there was a software update, I clicked install, it tried to reboot, and now I'm stuck in a custom recovery boot loop. I still can't connect to either of my PCs by USB and using my SD card to flash ROMs isn't doing anything now, just boots straight into TWRP every time, after full wiping and re-flashing several times now I'm really not sure how to fix this one.
Update:
Got past the bootloop from another thread on here which had a flashable fix. Now that I did that I'm actually able to use 5.x ROMs it seems. Currently working on Blisspop 3.5, once I get GAPPS to flash correctly, I think I aughta have a working Lollipop phone
Make sure you are using the correct TWRP for your device, having Bumped, as needed. Also, make sure you use the correct version of Gapps; it matters based on the version of Android your ROM is based upon.
Good luck and enjoy!
Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.
xSandmanx59 said:
Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Click to expand...
Click to collapse
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
xSandmanx59 said:
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.
Click to expand...
Click to collapse
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?
epidenimus said:
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?
Click to expand...
Click to collapse
Thank you for the response. I have noticed that a few small things are not so frequently updated in the copy/paste updates of the ROM threads. But that's to be expected =P Anyways, to answer your questions:
What are the driver's requirements? These are more variables associated with Windows...
I'm not entirely sure about this one. I know I found the drivers on the LG website for my LS990 model and I also installed a few others including older/latest/various models to test if any of them would work. I'm running windows 8.1 currently and the ls990 seems to have a little less support as the PC suite for LG doesn't include this model in their driver list.
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
Yes, it's been a long running issue on stock, stock rooted, and blisspop all with debugging on. I was able to connect to both of my computers for a long while until one day it just stopped. It was much worse than it is now. For a few days, then it decided to charge up to about 4% when I plugged it in with no battery and then put the battery back and waited for about 3-4 hours. Then I could turn it on long enough to selectively power down and it would then charge while powered off. Over the past couple days I've been able to plug it in and reboot to get it charging again... So bothersome. As for USB debugging, not sure when it stopped exactly but I assume it was around the same time (2 months ago)
What version of the Android SDK/Studio are you running?
I have the latest version of android studio from their website.
Have you added the platform-tools to the SDK, as required?
Yes, I believe so. I'm not 100% on the SDK stuff.
Can you get ADB to recognize the device when you connected and are in TWRP?
No. There is no response from my computer at all during any of the stages of driver and twrp and studio installations. Nothing is listed in my device menu either.
Beyond this, today my phone ran out of battery while I was out and about and then has refused to charge by any method. Then I finally got it to turn on to power down etc so it would charge about 3 hours later. Once I was able to boot back up I went out to smoke and came back to my phone somehow automatically flashing a different version of blisspop that had something about user_modified in the file name which then unloaded all of my saved layouts and whatnot. After about 20 minutes of reorganizing it went black, and has since been locked in a bootloop which has survived full wipes and re-installations of the previous version of blisspop I had been using. I just downloaded the latest version for ls990 once more, and I'll report back with whether or not that fixed the issue at hand.
Hi all. I'm posting here because after countless (2) hours of searching online I haven't been able to find a proper solution for a problem. I'm hoping that you all can help me with this one.
I've been using the LG g3 for the past year and everything has been great. But since my screen got smashed I've had to replace it with a newer one. I got this last Thursday.
I've been sticking with stock because I'm quite fond of the stock marshmallow. But since I'm a tinkerer I can't help myself. So after I updated (yesterday) I was going to attempt to root and flash a shiny new rom. Unfortunately, I haven't been able to get that far, as my phone can no longer be recognized by my computer.
I will put it in, and it will pop up with "USB Device not recognized". Under device managers it merely shows up as "unknown usb device". So I uninstalled my LG drivers (which are normally installed once you plug in the phone, but I digress. It did all of this before the 6.0 update) and it will attempt to install usb drivers but fail almost immediately and say it experienced an "unknown error", very helpfully reminding me to try and unplug/plug the device or factory reset.
Factory reset is very difficult for me right now as I have just finally gotten the phone tweaked to my liking. I really don't want to have to re-download everything. I have tried almost every workarounds I could find on the Internet but I keep running in circles. I've downloaded several different drivers for my phone and none of them work. I'm really at a loss.
I'm assuming that it must be the marshmallow update, as I haven't rooted or installed cfw as of yet. And I can plug someone else's phone in and it will install the drivers in a heartbeat. I can charge my phone but it won't give me options for MTP/PTP/Charge mode at all.
Anyways that's about all I can ask at the moment. I just hope someone here has experienced this and knows what to do.
Okay, I have now tried factory resetting my phone and it still won't work. It's the 6.0 update that's causing this. I'm at a loss, either I have to wait for google to hopefully patch this or I have to take back my new phone and exchange it for a new one.
You should be aware that the correct model number for a Canadian G3 from Koodo is D852, not D820 as you mentioned.
Before taking back your phone, try to see if your phone is recognized with a different USB cable (OEM one preferred), plugged in a different USB port of your computer, or, if possible on a friend's Windows 10 or Windows 8 computer, just in case different drivers might recognize your phone.
Your suspicion (that the OTA update to MM caused this) is not well supported by the reality: the OTA update was quite uneventful for thousands of other Canadian G3 phones; we should have heard more complaints if the OTA update were botched by Koodo or Telus.
Literally every time I try to get root via software like king root, root genius, ect on Windows 10. Right in the middle of the process Windows 10 will get the blue screen of death ultimately stopping you from rooting your device. This started happening right around the time not to long ago Verizon forced pushed out a ota update with no description and made it force install into devices.
FlameHammer said:
Literally every time I try to get root via software like king root, root genius, ect on Windows 10. Right in the middle of the process Windows 10 will get the blue screen of death ultimately stopping you from rooting your device. This started happening right around the time not to long ago Verizon forced pushed out a ota update with no description and made it force install into devices.
Click to expand...
Click to collapse
I'm more confused by the use of a hack type root method on a pixel than the bsod...
CyberpodS2 said:
I'm more confused by the use of a hack type root method on a pixel than the bsod...
Click to expand...
Click to collapse
Yes, this ^^ . But, also, what you might want to try @FlameHammer -- since this seems to be a bsod due to hardware conflict -- is to first make sure you have all your motherboard updates installed, then after go to the Device Manager, uninstall the USB hub/port that you are using to connect to your phone (beware! this may reset other devices and/or configurations) -- be sure to NOT check "delete the driver software for this device -- and then the "Scan for new hardware" button and have the USB port reinstalled.
But, like Cyberpod said, trying to figure out why you are using those very questionable "hack type root" methods as well as why it's happening without you providing your computer specs (most specifically your motherboard as that has most to do with your USB connections) is more of a critical/significant question...
Greetings,
General
I've been all over the Internet trying to gain access to more information about how to repair my LG G4. Well... Let's start from the beginning.
Story
I have an LG G4, it's old and I've had it for over 4-5 years now... I can't exactly remember how long I had it for. It still works, just needs a new battery and cable (cats chewed the cable and batteries don't last when you forget to disconnect them from the device, leave it plugged in for weeks and let it completely die for longer then a week).
I recently saw a video about the Pine phone and the fact that it was able to run a linux mobile distribution and when I looked into installing a custom OS into LG G4, it was possible... If I manually ported it myself.
I actually got fairly far using my Xubuntu system with configuring and compiling, the trouble I ran into was that I couldn't root or fastboot my device.
So, now here's where the problem began, I have a LG G4 factory reset and when I load up the Recovery mode, it brings up the android guy with their chest open and an exclamation mark in a yellow triangle, no message. After attempting to boot into recovery mode, I wait a little while and the phone automatically resets back to normal. When I use ADB to force the phone into fast boot, it skips it and starts the phone normally.
Now I'm on a mission to find a way to either fix the boot or flash the firmware (in hopes that it fixes the boot/recovery).
I have already tried:
Installing LGFlashTool
Versions, 2.0.1.6, 2.0.1.9, Year: 2014 and 2.0.2.5. Other than year 2014, the other ones were installed from LGFlashTool.com
Since Xubuntu can't run these files properly, I just ran them on my wife's Windows computer
I installed the LG Mobile Drivers and LGFlashTool had registered that it was the correct DLL but, it didn't seem to find the phone
Year 2014 LGFlashTool had found the phone but, I may have had the incorrect kdz file.
The Flash starts and the phone goes to firmware update, but the phone stops at zero and sits there while the program crashes saying that there was an error (in which no means to read, understand or locate the description of this error) and to try again by unplugging and removing the battery.
This version was downloaded from xda-developers.com
Conclusion
Once I can get into fastboot, I'll be able to root my phone and attempt to install the mobile OS I have ready.
Otherwise, I think I might be able to install a microSD card with the OS but, I don't think that will work if I can't get into the option to boot from a separate location (I believe that's called fastboot). But, then again... I think the phone needs to be rooted first... Then that brings me to the previous issue.
Details and Information
The phone details (as far as I see) are:
When I remove the battery I can see:
FCC ID: ZMFH810
IC ID: 2703C-H812
Model Number: LG-H812
I'm not exactly sure what KDZ file I got but the name is: PR H810PR10a_02.kdz, I also have the _04.kdz
I'm using H815 as my compile for the mobile OS, I may switch to H810 when I get back to that point.
Useless information: I still have the original leather backing... Removed from the phone because I didn't like it. If I find it, I can ship it to someone.
That's about it... I am very terrible about research and using Google properly (I have no idea why, I think it's a terrible flaw to have but, I have it). So, if you find the solution by typing words I didn't use or finding a similar post, I am very sorry. Hope I have everything posted here to help solve the issue, linking to posts that can resolve the issue or posting questions on what I might be missing will help.
Thanks in advance for the support of this community,
Lilrock
Lilrock said:
Greetings,
General
I've been all over the Internet trying to gain access to more information about how to repair my LG G4. Well... Let's start from the beginning.
Story
I have an LG G4, it's old and I've had it for over 4-5 years now... I can't exactly remember how long I had it for. It still works, just needs a new battery and cable (cats chewed the cable and batteries don't last when you forget to disconnect them from the device, leave it plugged in for weeks and let it completely die for longer then a week).
I recently saw a video about the Pine phone and the fact that it was able to run a linux mobile distribution and when I looked into installing a custom OS into LG G4, it was possible... If I manually ported it myself.
I actually got fairly far using my Xubuntu system with configuring and compiling, the trouble I ran into was that I couldn't root or fastboot my device.
So, now here's where the problem began, I have a LG G4 factory reset and when I load up the Recovery mode, it brings up the android guy with their chest open and an exclamation mark in a yellow triangle, no message. After attempting to boot into recovery mode, I wait a little while and the phone automatically resets back to normal. When I use ADB to force the phone into fast boot, it skips it and starts the phone normally.
Now I'm on a mission to find a way to either fix the boot or flash the firmware (in hopes that it fixes the boot/recovery).
I have already tried:
Installing LGFlashTool
Versions, 2.0.1.6, 2.0.1.9, Year: 2014 and 2.0.2.5. Other than year 2014, the other ones were installed from LGFlashTool.com
Since Xubuntu can't run these files properly, I just ran them on my wife's Windows computer
I installed the LG Mobile Drivers and LGFlashTool had registered that it was the correct DLL but, it didn't seem to find the phone
Year 2014 LGFlashTool had found the phone but, I may have had the incorrect kdz file.
The Flash starts and the phone goes to firmware update, but the phone stops at zero and sits there while the program crashes saying that there was an error (in which no means to read, understand or locate the description of this error) and to try again by unplugging and removing the battery.
This version was downloaded from xda-developers.com
Conclusion
Once I can get into fastboot, I'll be able to root my phone and attempt to install the mobile OS I have ready.
Otherwise, I think I might be able to install a microSD card with the OS but, I don't think that will work if I can't get into the option to boot from a separate location (I believe that's called fastboot). But, then again... I think the phone needs to be rooted first... Then that brings me to the previous issue.
Details and Information
The phone details (as far as I see) are:
When I remove the battery I can see:
FCC ID: ZMFH810
IC ID: 2703C-H812
Model Number: LG-H812
I'm not exactly sure what KDZ file I got but the name is: PR H810PR10a_02.kdz, I also have the _04.kdz
I'm using H815 as my compile for the mobile OS, I may switch to H810 when I get back to that point.
Useless information: I still have the original leather backing... Removed from the phone because I didn't like it. If I find it, I can ship it to someone.
That's about it... I am very terrible about research and using Google properly (I have no idea why, I think it's a terrible flaw to have but, I have it). So, if you find the solution by typing words I didn't use or finding a similar post, I am very sorry. Hope I have everything posted here to help solve the issue, linking to posts that can resolve the issue or posting questions on what I might be missing will help.
Thanks in advance for the support of this community,
Lilrock
Click to expand...
Click to collapse
Well first of all you need to unlock your phone. H812 can't be unlocked officially though. Check my sig for the only unofficial one. Once unlocked you can flash custom ROMs but first of all you should read about ARB (antirollback) also in my sig and ensure you understand the risks all this brings. Gl.
steadfasterX said:
Well first of all you need to unlock your phone. H812 can't be unlocked officially though. Check my sig for the only unofficial one. Once unlocked you can flash custom ROMs but first of all you should read about ARB (antirollback) also in my sig and ensure you understand the risks all this brings. Gl.
Click to expand...
Click to collapse
Thanks for the positive feedback, I will attempt to fix my phone with your solution. This phone is technically almost garbage and when I fully update the phone, it runs like trash. So, if I can install a custom ROM, it may run a little better or have the tools I would personally like in a phone.
I'll let you know the details of my attempt,
Lilrock
You might be able to use:
GitHub - Lekensteyn/lglaf: LG Download Mode utility and documentation
LG Download Mode utility and documentation. Contribute to Lekensteyn/lglaf development by creating an account on GitHub.
github.com
It is more reliable then the factory tools when it works.
SkewedZeppelin said:
You might be able to use:
GitHub - Lekensteyn/lglaf: LG Download Mode utility and documentation
LG Download Mode utility and documentation. Contribute to Lekensteyn/lglaf development by creating an account on GitHub.
github.com
It is more reliable then the factory tools when it works.
Click to expand...
Click to collapse
Which is included in mAid (https://maid.binbash.rocks).. ... Even with a UI...
Thank you very much with your support. I was able to unlock, bootloader and install the image installer.
I'm on the verge of compiling and installing Ubuntu Touch on my LG G4 H812.
Hope you guys proceed with everything you're doing right!