Develop Bugs

H815 TWN, differences from EU?

I am certain my G4 is TWN, from the box and the software version. But what are the actual differences to the European H815? Specifically, can I flash European KDZs or use the EU command for flashing a rooted /system image?
Code:
dd if=/data/media/0/system.rooted.H81510c-EU.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
Thanks

I have a the TWN version too damn it. - that's what happens when you buy from a global vendor over the internet .
Good news is that you can flash the EU rooted system image. I did and it worked fine.
Bad news is that you can't unlock the boot loader (yet), which means no TWRP or custom roms and flashing a stock Marshmallow leaves you without root and no way to downgrade.
Cheers
BTW I don't know of any differences between the EU and TWN devices other than the version coding - to me it just seems to be a way for LG to control their different markets.

Thank you for this. I do not want to unlock it just yet, since I bought it from a local vendor and I have a 2 year warranty with them. I see there is already a rooted image for v10d TWN, so I will flash that soon (are you sure the parameters for the dd command are the same?).
Sidenote, it would be nice if we could compile our own KDZs and make rooted ones.

metalboy94 said:
Thank you for this. I do not want to unlock it just yet, since I bought it from a local vendor and I have a 2 year warranty with them. I see there is already a rooted image for v10d TWN, so I will flash that soon (are you sure the parameters for the dd command are the same?).
Sidenote, it would be nice if we could compile our own KDZs and make rooted ones.
Click to expand...
Click to collapse
I can't really comment on the all the parameters in that command string except to say that it's one I used and it worked well. Whether those numbers would need to be modified for the 10D image or not I can't say - I would suggest you ask the author of that original rooting thread.
BTW you can't unlock the bootloader on the TWN version just now in any case. I tried the official method over the weekend and was told the TWN version was not supported. There's unofficial unlock method available for any G4 variant yet either but people are working on it.

wadken1 said:
I can't really comment on the all the parameters in that command string except to say that it's one I used and it worked well. Whether those numbers would need to be modified for the 10D image or not I can't say - I would suggest you ask the author of that original rooting thread.
BTW you can't unlock the bootloader on the TWN version just now in any case. I tried the official method over the weekend and was told the TWN version was not supported. There's unofficial unlock method available for any G4 variant yet either but people are working on it.
Click to expand...
Click to collapse
Probably the parameters aren't different between firmware images, because they depend on the partition table of the device.
Now waiting for a version of Xposed that is confirmed not to drain battery. Thanks again!

I'm running xposed now with about 10 modules. I don't see any great battery drain.

wadken1 said:
I have a the TWN version too damn it. - that's what happens when you buy from a global vendor over the internet .
Good news is that you can flash the EU rooted system image. I did and it worked fine.
Bad news is that you can't unlock the boot loader (yet), which means no TWRP or custom roms and flashing a stock Marshmallow leaves you without root and no way to downgrade.
Cheers
BTW I don't know of any differences between the EU and TWN devices other than the version coding - to me it just seems to be a way for LG to control their different markets.
Click to expand...
Click to collapse
Hang on, I can flash MM into my TWN? I missed that, how does that work? Is there a thread?

wadken1 said:
I have a the TWN version too damn it. - that's what happens when you buy from a global vendor over the internet .
Good news is that you can flash the EU rooted system image. I did and it worked fine.
Bad news is that you can't unlock the boot loader (yet), which means no TWRP or custom roms and flashing a stock Marshmallow leaves you without root and no way to downgrade.
Cheers
BTW I don't know of any differences between the EU and TWN devices other than the version coding - to me it just seems to be a way for LG to control their different markets.
Click to expand...
Click to collapse
I did the same thing, buying online and getting stuck with TWN. I came from a GS6 and was thinking "I'll wack an AOSP ROM on the G4 and I'll have the perfect phone". Now I'll probably never buy another LG even though I actually like the G4 but when we pay close to $1k for a phone we should be able to do what we like with it!

There is a thread for stock marshmallow which you can install with flash fire but there's no root available with that option just now.

wadken1 said:
There is a thread for stock marshmallow which you can install with flash fire but there's no root available with that option just now.
Click to expand...
Click to collapse
I've tried to find the correct thread but could you point me in the right direction?
Thanks

gz5ztg said:
I've tried to find the correct thread but could you point me in the right direction?
Thanks
Click to expand...
Click to collapse
Sorry. Missed this while I was away.
The thread I'm talking about is http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-rom-t3233049
BUT be warned you will lose root !!. So far as I know just now there is no way to get root on stock MM without an unlocked bootloader. This may have changed inthe last couple of days - you'll need to read around the forum.
ALSO there is no sure way back to L is you decide you can't live without root (I certainly couldn't so I'm waiting for further developments). I think I read that someone here more-or-less accidentally managed to recover back to L but I didn't really have time to take in all the details so futher reading needed if you want to take the risk.

wadken1 said:
Sorry. Missed this while I was away.
The thread I'm talking about is http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-rom-t3233049
BUT be warned you will lose root !!. So far as I know just now there is no way to get root on stock MM without an unlocked bootloader. This may have changed inthe last couple of days - you'll need to read around the forum.
ALSO there is no sure way back to L is you decide you can't live without root (I certainly couldn't so I'm waiting for further developments). I think I read that someone here more-or-less accidentally managed to recover back to L but I didn't really have time to take in all the details so futher reading needed if you want to take the risk.
Click to expand...
Click to collapse
Okay thanks, maybe I will wait. This is going to sound like a completely noob type question but what is it that you are doing that you couldn't live without that requires root?

gz5ztg said:
Okay thanks, maybe I will wait. This is going to sound like a completely noob type question but what is it that you are doing that you couldn't live without that requires root?
Click to expand...
Click to collapse
Here's a few of the things I use which need root:
TI Backup
LMT Launcher
Bubble UpnP
FX Explorer (with root)
Gravity Box (xposed) to give expanded desktop
Llama + Secure settings (allows for automated control of airplane mode, gps and others which have been denied by google for default seetings)
Buidprop editor - allows altering a number of settings but especially DPI
Greenify advanced functions
Amplify
Better Battery Stats
Flashfire
Busybox
Viper4Android
SE Linux Mode Changer (needed to allow Viper to work)

Will my H812 have less problems on lollipop?

This phone was given to me with marshmellow and im having the issue of not being able to update google play service among other things. the other issues im having might be the effect of the google play service. i just wanted to know if its worth attempting the downgrade on lollipop

shatheone said:
This phone was given to me with marshmellow and im having the issue of not being able to update google play service among other things. the other issues im having might be the effect of the google play service. i just wanted to know if its worth attempting the downgrade on lollipop
Click to expand...
Click to collapse
Depending on the underlying issue, you may still encounter the Play Services issue on Lollipop as you have on Marshmallow.
First, see if you can work the issue out on your current system.
- Delete cache and Data on Play Services.
- reset app preferences and reset default apps in the menu in the Apps folder in Settings.
- delete your Google account and re-install it.
- use LGUP-NEW to reinstall your Marshmallow rom (H81220). Check out this site for some H812 stock roms:
https://lg-firmwares.com/lg-h812-firmwares/
scroll down to the firmwares list and install the correct stock kdz - carrier and version
You can downgrade to Lollipop (H81210) using LGUP-NEW - frankly I haven't noticed a lot of difference between them but does have the current advantage of being rootable. Some members report better battery life but you will lose some security updates.

sdembiske said:
Depending on the underlying issue, you may still encounter the Play Services issue on Lollipop as you have on Marshmallow.
First, see if you can work the issue out on your current system.
- Delete cache and Data on Play Services.
- reset app preferences and reset default apps in the menu in the Apps folder in Settings.
- delete your Google account and re-install it.
- use LGUP-NEW to reinstall your Marshmallow rom (H81220). Check out this site for some H812 stock roms:
https://lg-firmwares.com/lg-h812-firmwares/
scroll down to the firmwares list and install the correct stock kdz - carrier and version
You can downgrade to Lollipop (H81210) using LGUP-NEW - frankly I haven't noticed a lot of difference between them but does have the current advantage of being rootable. Some members report better battery life but you will lose some security updates.
Click to expand...
Click to collapse
thanks for the reply, i actually did all of those things, including a factory reset. i will try to reinstall using lg up, maybe something in the stock image got corrupted? i learned that even if my phone boot loops, it wont be repaired as the serial number is out of range. so i might hold on to it until theres a good custom available

shatheone said:
thanks for the reply, i actually did all of those things, including a factory reset. i will try to reinstall using lg up, maybe something in the stock image got corrupted? i learned that even if my phone boot loops, it wont be repaired as the serial number is out of range. so i might hold on to it until theres a good custom available
Click to expand...
Click to collapse
Yes, very possible that something got corrupted. Definitely try a re-install of your stock kdz with LGUP-NEW.
If you haven't checked out steadfasterX's bootloader unlock thread, you will have to in order to install any custom rom with some assurance of success:
https://forum.xda-developers.com/g4/general/bl-unlock-unlock-bootloader-proof-t3648288
You might as well get started now as it won't be long before he publishes. You will have to install his SALT program and create a backup before proceeding to unlock your bootloader preparatory to installing any custom rom:
https://forum.xda-developers.com/g4/general/tool-salt-lg-revolution-t3717864

sdembiske said:
Yes, very possible that something got corrupted. Definitely try a re-install of your stock kdz with LGUP-NEW.
If you haven't checked out steadfasterX's bootloader unlock thread, you will have to in order to install any custom rom with some assurance of success:
https://forum.xda-developers.com/g4/general/bl-unlock-unlock-bootloader-proof-t3648288
You might as well get started now as it won't be long before he publishes. You will have to install his SALT program and create a backup before proceeding to unlock your bootloader preparatory to installing any custom rom:
https://forum.xda-developers.com/g4/general/tool-salt-lg-revolution-t3717864
Click to expand...
Click to collapse
i couldnt get LG up to recognize my phone even after taking out the battery, so ill have to find another usb cable and try that. i see two different kdzs for my software version so ill have to research the correct one. and im not planning one unlocking the bootloader until theres a better way. id sell it before risking a brick

shatheone said:
i couldnt get LG up to recognize my phone even after taking out the battery, so ill have to find another usb cable and try that. i see two different kdzs for my software version so ill have to research the correct one. and im not planning one unlocking the bootloader until theres a better way. id sell it before risking a brick
Click to expand...
Click to collapse
IF, you'd actually read steadfasterX's thread and in particular his latest update (last page on the thread, currently) ... you would realize there had already been a proof of a successful unlock of an H812. I suspect your phone has been screwed up by somebody who didn't know what they were doing in the first place. No one has done more work in this area and had more successes than steadfasterX - good luck for waiting for a better way or getting much trying to sell it - check ebay and see the prices - LOL.

sdembiske said:
IF, you'd actually read steadfasterX's thread and in particular his latest update (last page on the thread, currently) ... you would realize there had already been a proof of a successful unlock of an H812. I suspect your phone has been screwed up by somebody who didn't know what they were doing in the first place. No one has done more work in this area and had more successes than steadfasterX - good luck for waiting for a better way or getting much trying to sell it - check ebay and see the prices - LOL.
Click to expand...
Click to collapse
i didnt mean any disrespect, but the process is still in alpha state. this is my only phone currently so i dont want to risk bricking it. i have no reason for unlocking bootloader when there isnt enough rom support to justify doing so

shatheone said:
i didnt mean any disrespect, but the process is still in alpha state. this is my only phone currently so i dont want to risk bricking it. i have no reason for unlocking bootloader when there isnt enough rom support to justify doing so
Click to expand...
Click to collapse
The risk of bricking your phone has been minimized with steadfasterX's process - he has had a couple of successful unlocks of an H812 now and when he publishes it for the public, the risk will be minimized as much as it can be in any unlock case.
With respect to your phone not being recognized by LGUP-NEW. Make sure you have installed the LGMobileDriver_WHQL_Ver_4.2.0 available for download from the US LG site - the Windows driver will give you problems.

sdembiske said:
The risk of bricking your phone has been minimized with steadfasterX's process - he has had a couple of successful unlocks of an H812 now and when he publishes it for the public, the risk will be minimized as much as it can be in any unlock case.
With respect to your phone not being recognized by LGUP-NEW. Make sure you have installed the LGMobileDriver_WHQL_Ver_4.2.0 available for download from the US LG site - the Windows driver will give you problems.
Click to expand...
Click to collapse
well i wouldnt care doing it if there was more rom support, i dont see a point in unlocking at this point. if im missing a benefit of unlocking right now, enlighten me. and thats the driver i already have installed

shatheone said:
well i wouldnt care doing it if there was more rom support, i dont see a point in unlocking at this point. if im missing a benefit of unlocking right now, enlighten me. and thats the driver i already have installed
Click to expand...
Click to collapse
One benefit might be fixing your screwed up phone. Still didn't read the OP I guess as you were advised to in steadfasterX's bootloader unlock thread. Here's an idea ... before making summary judgements with little or no knowledge, perhaps you should check with the member that is sited in the "proof" for the H812 and post your questions there for the Roms he has tried. My understanding was that he was on Lineage for Nougat - the most popular downloaded custom rom for .... are you ready ... the H815/H811 - here's an idea ... why don't you check out ALL the roms that are for the H815/H811 in the Android Development section ... hmm ... really?

sdembiske said:
One benefit might be fixing your screwed up phone. Still didn't read the OP I guess as you were advised to in steadfasterX's bootloader unlock thread. Here's an idea ... before making summary judgements with little or no knowledge, perhaps you should check with the member that is sited in the "proof" for the H812 and post your questions there for the Roms he has tried. My understanding was that he was on Lineage for Nougat - the most popular downloaded custom rom for .... are you ready ... the H815/H811 - here's an idea ... why don't you check out ALL the roms that are for the H815/H811 in the Android Development section ... hmm ... really?
Click to expand...
Click to collapse
if you took 10 seconds, you would see i actually posed in that thread. and all they did was direct me to the OP which says nothing about lineageos working for h812, or that the h815/ or h811 roms work for this variant. all it says is that i can flash nougat based roms. so the thread isnt too helpful, im not sure why you think it is.

shatheone said:
i didnt mean any disrespect, but the process is still in alpha state. this is my only phone currently so i dont want to risk bricking it. i have no reason for unlocking bootloader when there isnt enough rom support to justify doing so
Click to expand...
Click to collapse
Hey man, i'm agreeing with you for most of this...
I'm also not going to risk anything until 10 H812 users have successfully unlocked bootloader and flashed a custom rom (one thats intended for h815 or h811) with steadfasterx's method. Maybe you can flash H815 custom roms once the bootloader is unlocked... but just to be safe, let's flash other stock carrier firmwares in the meantime...... in the end no matter what anyone says, its your phone at risk...
Member TheLatios381 and I were asking same question here:https://forum.xda-developers.com/g4...10-q2-2017-t3567402/post75742903#post75742903 because no answer to our question on steadfasterx's thread...

How to proceed with "Frankenstein" LG G4 phone?

first of all - great job steadfasterX and cWks! with unlocking LG G4
probably I bought (in China) "Frankenstein" LG G4 phone, because it should be H810, but on mainboard is written VS986. I have unlocked it by SALT and instaled TWRP, but I have not find any ROM which would work
based on the information from the vendor it should have V10o ATT firmawe, but in the LG software it shows that is model H815 with firmware V29a.
subsequently I brick it and unbrick it a try to fash .tot files using LG software, but unsuccessful. Because the LGUp shows, that it is model LS991 finally I flash the LS991ZVD.tot file. during booting, the android will stop, when "configuring your phone", probably LS991 files have wrong modem...
now works the download mode and recovery mode only for this phone (no fastboot) and in SALT shows that is ARB4 which is not possible to unlock
Is there any possibility to:
1. to flash correct modem (possibly for VS986?) - 1.a) how is possible to modify the modem in tot file?
2. erase eMMC or go back to ARB2?
I have the backup prepared in TWRP with ARB2, but how us it to recover the phone?
Many, many, many thanks for help!
Or it is easier to buy in Chine the new motherboard? and which?
Thank you very much for answers!!!

Dedulo said:
first of all - great job steadfasterX and cWks! with unlocking LG G4
probably I bought (in China) "Frankenstein" LG G4 phone, because it should be H810, but on mainboard is written VS986. I have unlocked it by SALT and instaled TWRP, but I have not find any ROM which would work
based on the information from the vendor it should have V10o ATT firmawe, but in the LG software it shows that is model H815 with firmware V29a.
subsequently I brick it and unbrick it a try to fash .tot files using LG software, but unsuccessful. Because the LGUp shows, that it is model LS991 finally I flash the LS991ZVD.tot file. during booting, the android will stop, when "configuring your phone", probably LS991 files have wrong modem...
now works the download mode and recovery mode only for this phone (no fastboot) and in SALT shows that is ARB4 which is not possible to unlock
Is there any possibility to:
1. to flash correct modem (possibly for VS986?) - 1.a) how is possible to modify the modem in tot file?
2. erase eMMC or go back to ARB2?
I have the backup prepared in TWRP with ARB2, but how us it to recover the phone?
Many, many, many thanks for help!
Or it is easier to buy in Chine the new motherboard? and which?
Thank you very much for answers!!!
Click to expand...
Click to collapse
Ok well first of all read my signature about the anti roll back details. It is absolutely impossible to flash lower ARB . That's for what it is made for obviously .
Next is that you have flashed stupid files and besides they're with an arb higher than 2 so you cannot unlock it anymore.
we all know that Frankenstein devices are special in many terms .
one example is nobody knows what they do or flash in the primary boot loader which we cannot read out. That means we don't know which RAM is compatible and we do not know if they make any modifications in the signed boot loader stack which ensure they can load Frankenstein devices.
So even if you flash for example h810 files with an arb of 4 it may not load or working properly the same goes for vs 986 of course .
yeah and I have to repeat myself but flashing that arb of 4 was bad in another way,too. Having that arb you have no way to use qfil anymore as that works only up to arb 3. So you have no way to use it to flash for example other models image files or even more important to unbrick your device if it ever hard bricks.
You can of course use a text editor to modify any kdz file and flash whatever you like .. The other option is to use the SD card unbrick method linked in my signature but it requires to hard brick your device first. I can tell you how but in your situation it is very risky if you can't get the SD card unbrick working . so I would recommend to go the Hex editor way just search XDA for how to use it and flash vs986 files with an ARB of 4
Sent from my OnePlus 6T using XDA Labs

steadfasterX said:
Ok well first of all read my signature about the anti roll back details. It is absolutely impossible to flash lower ARB . That's for what it is made for obviously .
Next is that you have flashed stupid files and besides they're with an arb higher than 2 so you cannot unlock it anymore.
we all know that Frankenstein devices are special in many terms .
one example is nobody knows what they do or flash in the primary boot loader which we cannot read out. That means we don't know which RAM is compatible and we do not know if they make any modifications in the signed boot loader stack which ensure they can load Frankenstein devices.
So even if you flash for example h810 files with an arb of 4 it may not load or working properly the same goes for vs 986 of course .
yeah and I have to repeat myself but flashing that arb of 4 was bad in another way,too. Having that arb you have no way to use qfil anymore as that works only up to arb 3. So you have no way to use it to flash for example other models image files or even more important to unbrick your device if it ever hard bricks.
You can of course use a text editor to modify any kdz file and flash whatever you like .. The other option is to use the SD card unbrick method linked in my signature but it requires to hard brick your device first. I can tell you how but in your situation it is very risky if you can't get the SD card unbrick working . so I would recommend to go the Hex editor way just search XDA for how to use it and flash vs986 files with an ARB of 4
Sent from my OnePlus 6T using XDA Labs
Click to expand...
Click to collapse
You are right. I have done some stupid steps, because the method for unlocking my "Frankenstein" phone did not work. I read about the anti roll back, but I hoped that something had changed (also the unlocking process has gradually developed )
I had to take apart the phone first and find out what was written on the motherboard This was a big mistake!
Today I have bricked (hard?) my phone by flashing LS991 ZVB ARB3 tot file, because I don't know, how to work with Hex editor.
Which KDZ file I need to download for SD card unbrick? I suppose that VS986 with ARB4, right?
Thanks for a help and reply!

Dedulo said:
You are right. I have done some stupid steps, because the method for unlocking my "Frankenstein" phone did not work. I read about the anti roll back, but I hoped that something had changed (also the unlocking process has gradually developed )
I had to take apart the phone first and find out what was written on the motherboard This was a big mistake!
Today I have bricked (hard?) my phone by flashing LS991 ZVB ARB3 tot file, because I don't know, how to work with Hex editor.
Which KDZ file I need to download for SD card unbrick? I suppose that VS986 with ARB4, right?
Thanks for a help and reply!
Click to expand...
Click to collapse
well I see. the ARB is (as written in the linked guide) a (extreme likely) physical blown fuse, so a process which can not be reverted..
yes you hard-bricked the phone by flashing a lower ARB then the current one. once you flashed ARB 4 you can't flash ARB lower then 4.
the good is as you have hard-bricked it you may be able to use the sdcard unbrick but that requires the 9008 qdl mode:
connect the device to your PC and view the device manager. does it add something like QHUSB BULK? If yes use the vs986 files + UsU files as written the sdcard thread.
You can also use FWUL from booting on USB and just type: lsusb in a terminal after connecting the phone. paste the output here then. It should show something like "QDL 9008" or "QualComm...". If thats the case use the vs986 files + UsU files as written in the sdcard thread.
If both of the above does not show up the QDL 9008 mode.. well try it without battery in again. If it still failing it is likely gone. sorry. The QFIL files available do not work with ARB >3 so.
You can still read on in the sdcard unbrick thread in the second post to find out how to force the sdcard unbrick mode (that differs from the the QDL mode and so need to disassembling the whole mainboard and doing tricky stuff without a guarantee of that it work at the end.)
.-

steadfasterX said:
well I see. the ARB is (as written in the linked guide) a (extreme likely) physical blown fuse, so a process which can not be reverted..
yes you hard-bricked the phone by flashing a lower ARB then the current one. once you flashed ARB 4 you can't flash ARB lower then 4.
the good is as you have hard-bricked it you may be able to use the sdcard unbrick but that requires the 9008 qdl mode:
connect the device to your PC and view the device manager. does it add something like QHUSB BULK? If yes use the vs986 files + UsU files as written the sdcard thread.
You can also use FWUL from booting on USB and just type: lsusb in a terminal after connecting the phone. paste the output here then. It should show something like "QDL 9008" or "QualComm...". If thats the case use the vs986 files + UsU files as written in the sdcard thread.
If both of the above does not show up the QDL 9008 mode.. well try it without battery in again. If it still failing it is likely gone. sorry. The QFIL files available do not work with ARB >3 so.
You can still read on in the sdcard unbrick thread in the second post to find out how to force the sdcard unbrick mode (that differs from the the QDL mode and so need to disassembling the whole mainboard and doing tricky stuff without a guarantee of that it work at the end.)
.-
Click to expand...
Click to collapse
Yes, Q HS-USB QDLoader 9008 is in the Ports (in DevMan), but now I need to prepare SD card, because the old files (which I have used for unbricking last time) do not work .

Dedulo said:
Yes, Q HS-USB QDLoader 9008 is in the Ports (in DevMan), but now I need to prepare SD card, because the old files (which I have used for unbricking last time) do not work .
Click to expand...
Click to collapse
sure. you need ARB 4 files.
.-

Dedulo said:
Yes, Q HS-USB QDLoader 9008 is in the Ports (in DevMan), but now I need to prepare SD card, because the old files (which I have used for unbricking last time) do not work .
Click to expand...
Click to collapse
I don´t find the right kdz for VS986 with ARB4. Can I use yours? (these two with ARB2: http://leech.binbash.it:8008/stock/LG/vs986/2BA/)

Dedulo said:
I don´t find the right kdz for VS986 with ARB4. Can I use yours? (these two with ARB2: http://leech.binbash.it:8008/stock/LG/vs986/2BA/)
Click to expand...
Click to collapse
well you still do not read my linked guide or understand what ARB is, right? Its IMPOSSIBLE to use an ARB lower then 4 in your case. so NO you can NOT use these.
Well I assumed there would be firmware with ARB 4 for the vs986 but it seems the highest is ARB 2..
keep in mind: everything you do now is extremely risky with maybe no point of return! If it bricks and is not switching to the 9008 mode.. you are lost!
After looking around a bit including in my ARB thread (which I mentioned) the LS991 seems to be the only one with ARB higher then 3 (so 4).
you are stuck with LS991 now. that means even when you may be able to unbrick with the sdcard unbrick it means you may never get cell service.
so try a LS991 kdz with ARB 4 (ZVD as you flashed that one should be fine) for the unbrick files to bring it at least back to life.
.-

steadfasterX said:
well you still do not read my linked guide or understand what ARB is, right? Its IMPOSSIBLE to use an ARB lower then 4 in your case. so NO you can NOT use these.
Well I assumed there would be firmware with ARB 4 for the vs986 but it seems the highest is ARB 2..
keep in mind: everything you do now is extremely risky with maybe no point of return! If it bricks and is not switching to the 9008 mode.. you are lost!
After looking around a bit including in my ARB thread (which I mentioned) the LS991 seems to be the only one with ARB higher then 3 (so 4).
you are stuck with LS991 now. that means even when you may be able to unbrick with the sdcard unbrick it means you may never get cell service.
so try a LS991 kdz with ARB 4 (ZVD as you flashed that one should be fine) for the unbrick files to bring it at least back to life.
.-
Click to expand...
Click to collapse
OK, so we understood each other. Because I flashed wrong file LS991 ZVD, I can't go back - only to the same firmware (because of ARB etc.). There is no way to change it (to VS986) or flash anything else
and, if I will be lucky, then the phone comes back to point during booting, when it stops in "configuring your phone". Never use him anymore for call services? How to go through this (configuration)?
There is only one way - to buy in Chine the new motherboard, but which (H815)?

Dedulo said:
OK, so we understood each other. Because I flashed wrong file LS991 ZVD, I can't go back - only to the same firmware (because of ARB etc.). There is no way to change it (to VS986) or flash anything else
and, if I will be lucky, then the phone comes back to point during booting, when it stops in "configuring your phone". Never use him anymore for call services? How to go through this (configuration)?
There is only one way - to buy in Chine the new motherboard, but which (H815)?
Click to expand...
Click to collapse
buy a h811 one as you can unlock h811 within just fastboot.
if you can't get one: the h815 international (so no h815p, h815tr etc) as it can be unlocked officially by the LG website.
if you can't get one: any h815 model should be fine as you can unlock by UsU and I haven't heard any big issues here.
good luck
.-

steadfasterX said:
buy a h811 one as you can unlock h811 within just fastboot.
if you can't get one: the h815 international (so no h815p, h815tr etc) as it can be unlocked officially by the LG website.
if you can't get one: any h815 model should be fine as you can unlock by UsU and I haven't heard any big issues here.
good luck
.-
Click to expand...
Click to collapse
I will try to unbrict it first and we will see... maybee I will wait for motherboard. this will be ok?
https://www.aliexpress.com/item/For...pm=a2g0s.13010208.99999999.259.88b93c00XlwucM
or is there any issue?
thank you very much for your time and help!

Dedulo said:
I will try to unbrict it first and we will see... maybee I will wait for motherboard. this will be ok?
https://www.aliexpress.com/item/For...pm=a2g0s.13010208.99999999.259.88b93c00XlwucM
or is there any issue?
thank you very much for your time and help!
Click to expand...
Click to collapse
I cannot guide you in where to buy or if that one is valid sorry.
.-

steadfasterX said:
I cannot guide you in where to buy or if that one is valid sorry.
.-
Click to expand...
Click to collapse
OK, I understand.
Could you be so kind and send me a link for kdz file? I don't find it. I have only LS991 ZVD tot file. It is possible to convert it to kdz?
Thank you!

I have prepared the SD card from tot file (not bin but img files) except PrimaryGPT.gpt (I don't fin it in tot file, only the PrimaryGPT_0.bin from another KDZ).
The proper KDZ for LS991 ZVD I could not download from LG support site, because my FR phone has IMEI VS986.
Until now the SD card unbricking method doesn't work for me.
I will try LS991 ZVB, which I used for bricking the phone.
Any idea what to do?

LG G8 sprint "Download mode"

Good afternoon friends. I still have a problem on my phone "your device has failed a routine safety ..." after I locked the bootloader. I gave it unofficial for repair, they could not do anything there. But now, for some reason, my phone does not load in edl9008 mode, but there is dowmload mode as on other lg devices (in theory, it should not be). So the question is, how to flash the phone via download mode to any other firmware? The main thing for me is that it starts and I can return twrp to restore my native firmware. Yesterday I tried it through uppercut, lgup didn't work. Does anyone have any knowledge of how to download kdz to this phone?

i wish someone would leak at least one sprint KDZ firmware

blaze2051 said:
i wish someone would leak at least one sprint KDZ firmware
Click to expand...
Click to collapse
Don't think you'll ever see, in your lifetime, a sprint kdz. Nor will you see an at&t one.
It's very important to do some research, initially, before messing with your phone. It's common knowledge that these kdz don't exist, and, that is why we always want to do a full backup of our device, especially when the kdz isn't (nor will ever be) available.
So where are u now? what's the situation? I ask because there are sprint backups around (from individual personal devices), that, if done carefully, can be used to fix a device without messing up the imei and s/n.

AsItLies said:
Don't think you'll ever see, in your lifetime, a sprint kdz. Nor will you see an at&t one.
It's very important to do some research, initially, before messing with your phone. It's common knowledge that these kdz don't exist, and, that is why we always want to do a full backup of our device, especially when the kdz isn't (nor will ever be) available.
So where are u now? what's the situation? I ask because there are sprint backups around (from individual personal devices), that, if done carefully, can be used to fix a device without messing up the imei and s/n.
Click to expand...
Click to collapse
phone is good i made more than one backup just it would be nice just to throw LGup and flash instead of using Qfil or other means of backup

LG G8 LMG820UM AT&T STOCK FIRMWARE/KERNEL

Hello, could someone PLEASE provide me with a stock or source for stock firmware for the AT&T LG G8 Thinq (LMG820UM). I've looked everywhere and can only find the U.S. Cellular, Verizon, Sprint, and T-mobile versions (everything except what I exactly need )!!!! The carrier's already unlocked. I wanna unlock the bootloader, flash custom ROMs like LineageOS (and TWRP) and root it and be able to revert back and LOCK the bootloader safely. I have LGup and other tools (though I don't know exactly what everything's for, such as firehose and other bootthings). I don't think cross flashing works and I don't want to do it anyway. Thanx!

PHANX0M said:
Hello, could someone PLEASE provide me with a stock or source for stock firmware for the AT&T LG G8 Thinq (LMG820UM). I've looked everywhere and can only find the U.S. Cellular, Verizon, Sprint, and T-mobile versions (everything except what I exactly need )!!!! The carrier's already unlocked. I wanna unlock the bootloader, flash custom ROMs like LineageOS (and TWRP) and root it and be able to revert back and LOCK the bootloader safely. I have LGup and other tools (though I don't know exactly what everything's for, such as firehose and other bootthings). I don't think cross flashing works and I don't want to do it anyway. Thanx!
Click to expand...
Click to collapse
Haven't seen anyone post their qfil backup of ATT rom, but it may be around. Yeah you won't find a kdz file of att rom because att doesn't allow that publicly.
Do you have att now? I'm guessing from what you say that you do, but you would like a kdz so you can go back if needed?
If you do have att, use qfil to back up ea partition individually, or use (I prefer) the bkerler edl utilities (search google), they take some effort to get up and running, but do a great job once done.
If u don't have att now... why would u want it? U may want to use them as a carrier but I'm pretty sure they still check the device imei, and if it's not one sold by them, some things *may* be restricted. I don't use them, only what I've read from others.
maybe you could explain better exactly what you want to do.

Yeah I have the AT&T phone now, and I want the kdz but don't know how to extract that ) :
And what do you mean they don't have it publicly? What if I extract it and post it?
Do you know anywhere where I could find them? I have and android 10 one with a broken screen (which I use Vysor for) and a working android 11 one.

PHANX0M said:
Yeah I have the AT&T phone now, and I want the kdz but don't know how to extract that ) :
Click to expand...
Click to collapse
you can't extract the kdz, that's not possible. You'll never find an ATT or Sprint kdz, they are simply not available, never will be, never have been.
The only thing you can do is back up what you currently have. Using qfil (look in guides section and you'll find how to set that up and use it) is probably the simplest option. You'll have to back up ea partition, and be sure to name them appropriately, as the back up doesn't do that.
Once you've done that, assuming the sim is unlocked, you can do other things you mention you want. But if the sim is not unlocked, you have to do that first, because flashing a different rom does not unlock it.
good luck

AsItLies said:
you can't extract the kdz, that's not possible. You'll never find an ATT or Sprint kdz, they are simply not available, never will be, never have been.
The only thing you can do is back up what you currently have. Using qfil (look in guides section and you'll find how to set that up and use it) is probably the simplest option. You'll have to back up ea partition, and be sure to name them appropriately, as the back up doesn't do that.
Once you've done that, assuming the sim is unlocked, you can do other things you mention you want. But if the sim is not unlocked, you have to do that first, because flashing a different rom does not unlock it.
good luck
Click to expand...
Click to collapse
So if I flash something custom, and then flash the backed up EA partition, it'll have the AT&T ROM/firmware again? I assume the bootloader has to be unlocked for this?

PHANX0M said:
So if I flash something custom, and then flash the backed up EA partition, it'll have the AT&T ROM/firmware again? I assume the bootloader has to be unlocked for this?
Click to expand...
Click to collapse
You'll have to flash back all the att partitions, not just some part of them. The device won't boot otherwise. And no, the boot loader does not have to be unlocked. Look in the guides section for the 'cross flashing' guide, it will explain what you need to do to make that happen, and you'll need a kdz you want to crossflash to. If you decide to x flash to a stock rom.
If all you wan to do is a custom rom, make sure the version of whatever rom you have, including if it's the att one, matches with the custom rom you want to use.
One note though re custom roms on LG devices; you will never be able to have Volte. That's an issue for US people especially, and other countries are getting there also.
LG, in it's infinite wisdom, has their ims stack (needed for volte to work) all over the rom, people have tried to port it, but it's a proprietary implementation, and has not, and probably never will be, ported. So, if you need volte, then your only option is a stock LG rom.

There's only ONE firehose for LG G8 Thinq all models, right? (If I even need to use that thing)
What are the EXACT things I have to back up to be able to revert back to AT&T ROM/Firmware?
So I know the T-Mobile version doesn't work with VoLTE (I've tried it myself and customer service told me I had to have them disable 3G blocker). But will the factory unlocked ROM work with it on an AT&T phone?
Even if I can't do this, is there ANY other way to go back to AT&T stock ROM/Firmware if I flash something else?

AsItLies said:
You'll have to flash back all the att partitions, not just some part of them. The device won't boot otherwise. And no, the boot loader does not have to be unlocked. Look in the guides section for the 'cross flashing' guide, it will explain what you need to do to make that happen, and you'll need a kdz you want to crossflash to. If you decide to x flash to a stock rom.
If all you wan to do is a custom rom, make sure the version of whatever rom you have, including if it's the att one, matches with the custom rom you want to use.
One note though re custom roms on LG devices; you will never be able to have Volte. That's an issue for US people especially, and other countries are getting there also.
LG, in it's infinite wisdom, has their ims stack (needed for volte to work) all over the rom, people have tried to port it, but it's a proprietary implementation, and has not, and probably never will be, ported. So, if you need volte, then your only option is a stock LG rom.
Click to expand...
Click to collapse
There's only ONE firehose for LG G8 Thinq all models, right? (If I even need to use that thing)
What are the EXACT things I have to back up to be able to revert back to AT&T ROM/Firmware?
So I know the T-Mobile version doesn't work with VoLTE (I've tried it myself and customer service told me I had to have them disable 3G blocker). But will the factory unlocked ROM work with it on an AT&T phone?
Even if I can't do this, is there ANY other way to go back to AT&T stock ROM/Firmware if I flash something else?

PHANX0M said:
There's only ONE firehose for LG G8 Thinq all models, right? (If I even need to use that thing)
What are the EXACT things I have to back up to be able to revert back to AT&T ROM/Firmware?
So I know the T-Mobile version doesn't work with VoLTE (I've tried it myself and customer service told me I had to have them disable 3G blocker). But will the factory unlocked ROM work with it on an AT&T phone?
Even if I can't do this, is there ANY other way to go back to AT&T stock ROM/Firmware if I flash something else?
Click to expand...
Click to collapse
Yes there's only one firehose file, and it does need to be used to when using Qfil. And you need to use Qfil to back up ALL PARTITIONS (not just some, all).
I can't help with specific carrier requirements, I only have used Mint. You'll have to ask the carrier what will and won't work.
No, there is no way to go back to att stock firmware. Period. No Other Way than whats already been indicated, from a back up.

AsItLies said:
Yes there's only one firehose file, and it does need to be used to when using Qfil. And you need to use Qfil to back up ALL PARTITIONS (not just some, all).
I can't help with specific carrier requirements, I only have used Mint. You'll have to ask the carrier what will and won't work.
No, there is no way to go back to att stock firmware. Period. No Other Way than whats already been indicated, from a back up.
Click to expand...
Click to collapse
Thank you for all the information thus far. If I restore the backup it can be completely as it was before and functional, including all data and everything? Do I have to unlock bootloader for this? And can I restore a backup from another phone (of the same model)?
Also, if I use the OPEN_CA ROM it'll let me use VoLTE?
Sorry, I'm only used to working with Xperia . Flashtool with Xperifirm was so much easier

PHANX0M said:
Thank you for all the information thus far. If I restore the backup it can be completely as it was before and functional, including all data and everything? Do I have to unlock bootloader for this? And can I restore a backup from another phone (of the same model)?
Also, if I use the OPEN_CA ROM it'll let me use VoLTE?
Sorry, I'm only used to working with Xperia . Flashtool with Xperifirm was so much easier
Click to expand...
Click to collapse
If you restore the backup the phone should then be back to 'stock'. The data partition backup would be probably in excess of 40 gig, no one backs those up.
No, the bootloader only needs to be unlocked if you want root access, this doesn't require root.
Volte depends on numerous things, 1 obviously being that the phone is capable of it, then the carrier has to have that capability, and it has to allow your specific device to use it on their network. I haven't used the open_ca rom so can't say, but have used the us_open in the States, and with Mint mobile it has definitely worked, as has vowifi.
good luck

AsItLies said:
If you restore the backup the phone should then be back to 'stock'. The data partition backup would be probably in excess of 40 gig, no one backs those up.
No, the bootloader only needs to be unlocked if you want root access, this doesn't require root.
Volte depends on numerous things, 1 obviously being that the phone is capable of it, then the carrier has to have that capability, and it has to allow your specific device to use it on their network. I haven't used the open_ca rom so can't say, but have used the us_open in the States, and with Mint mobile it has definitely worked, as has vowifi.
good luck
Click to expand...
Click to collapse
Thank you very much, I've not found such accurate and digestible information elsewhere!
But just to be sure.... I DON'T need to backup the userdata partition? And if I do.... Can I restore it from my old Broken G8 Thinq (which's android 10) to my new one (which's android 11) if I like the apps and stuff better (Both're AT&T). Would I have to unlock the carrier of the old one first (the new one is already unlocked)?
What if it were the same android version? What if it were different preinstalled carrier?
Also does that mean someone can get all my data with use of simple EDL?

PHANX0M said:
Thank you very much, I've not found such accurate and digestible information elsewhere!
But just to be sure.... I DON'T need to backup the userdata partition? And if I do.... Can I restore it from my old Broken G8 Thinq (which's android 10) to my new one (which's android 11) if I like the apps and stuff better (Both're AT&T). Would I have to unlock the carrier of the old one first (the new one is already unlocked)?
What if it were the same android version? What if it were different preinstalled carrier?
Also does that mean someone can get all my data with use of simple EDL?
Click to expand...
Click to collapse
Sorry, I can't be of much help with something like this. I've never tried to back up user data because it's just too much data and I would just prefer to reinstall the apps. Yes, someone could put the device in edl mode and pull off the user data, but if it's a stock device, it will be encrypted.

AsItLies said:
Sorry, I can't be of much help with something like this. I've never tried to back up user data because it's just too much data and I would just prefer to reinstall the apps. Yes, someone could put the device in edl mode and pull off the user data, but if it's a stock device, it will be encrypted.
Click to expand...
Click to collapse
So you're saying if the ROM (whether stock or not) supports encryption, the data pulled will be useless? And could I restore other partitions backed up from ANOTHER of the same device (whether different android version or not)?
And it's only encrypted if there's a lock code/pattern?
And if the bootloader was unlocked someone could just flash a custom recovery and bypass the lockscreen right?
Also luckily Mint doesn't read the IMEI like greedy AT&T