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?
Related
Bought a refurbished G4 from Ebay. My question is can I flash custom rom on this device?
In general the device model shows it is H815 version.But when I do IMEI check it shows F500S.What is the actual variant?
Thanks..
yours best option is ... to dissasemble the phone and remove the motherboard .. search for video on you tube for tear down. take motherboard out and see what is imprinted on motherboard what variant it says then fo from there. software and cases ar easy to edit. but not the imprinted model number on board.
Mine is a f500l but its a refurbished h811 however you cant flash any f500 rom on it because lgup thinks the phone is h815 to do so you first have to gain root then edit build.prop and replace any h815 u see to f500s and also replace the software version to version of the official kdz u downloaded after that u would be able to flash stock rom and gain your original phone's identity
But do not do this before disassembling and getting sure that its a f500s or you would probably brick your phone
@shamescool Even if I use LGUP tool,not ToT method do I need to edit build prop?
If yes then all editing need to be done within build prop only or more than that?
Sorry if I am being noob.
As raptor said disasembly is the only way if its working id leave it be the risk of hard brick is to great.
I am noob with this phone too its near a month its in my hand
no actually build prop way is the safest way another way which is extremely hard for noobs is to use hex editor and edit f500's kdz file and replace f500 with h815 and software version too
just like the build prop method
but the only problem with this is i dont know how to do so with hex editor
i myself tried the root method and it actually worked but kdz file editing is a hard approach if you cant gain root
ask other users and see what you can learn with hex editor and then tell me
Thanks @shamescool & everyone helped here.Certainly I saw on my motherboard it is F500L.So I just flashed the F500L ToT in dowload mode with respective DLL & it worked like a charm.My device now have a relevant rom.Later flashed Nougat too..
Glad to hear it
I recently found a way to trick LGUP with WinHex:
Just open the tot file in it and search for xVLG
then replace every f500 to your rom varient
Then i flashed f500l file on my phone which was successful and my phone bricked
Although everything except sd card works with ls991 qfil files but iam thinking if f500l's tot bricked my phone why the hell f500l is written on the main board
So im gonna try a ls991 tot file and see what happens...sd card is not really a big deal but why the hell the phone bricks??
@shamescool
Thanks & noted..
My phone firstly also got bricked when I used LGUP..Better use LG flash tool 1.8(ToT)flasher with proper DLL for F500L & flash it in download mode..As it had worked for me I hope yours will work to..
LGUP has so many bugs.There is a modified & fixed 8994.DLL which you can try with.Remind me if you need it.
It would be very good if you could provide me some links
@shamescool Use this tool in download mode
https://www.androidfilehost.com/?fid=24499762636004654 & this DLL https://mega.nz/#!pfZw3aAB!z1akOrEahn4iKBv9-R3hKN2O3vetzYfg2agcG_BrO-w.....
If you are using LGUP & getting error follow this method
https://www.lgdestek.net/lg-up-da-takili-kaliyor-hatasi-cozumu-31595/
@asingha94 can you please update the links and provide a link for tot file you used. It will be very helpful.
Thanks in advance
@ jatinder_anttal Sorry for late reply.I sold my G4 long ago.Now I am using G6.I don't have any link right now but you can get it from Google easily.
Sorry for late reply.I sold my G4 long ago.Now I am using G6.I don't have any link right now but you can get it from Google easily.
Hi guys;
So i bought a second hand unlocked D851 ( TMOBILE) with kitkat (cloudy rom) wanted to upgrade it to lolipop but i hard bricked it then used board diag program to bring it back to life but i extracted a d850 rom TOT since the d851 didnt work so now my lg g3 is at&t and permenantly locked ,been trying for a week now to unlocked it for nothing then I read somewhere in this forum that its easy to unlock the d851 using the tmobile app. so is there any way to change it back to D851.
Anyone has any idea?!!
how u use the board diag cuz im stock in qualcomm hs-usb qdloader 9008 and the threadt is closed now
ipus89 said:
how u use the board diag cuz im stock in qualcomm hs-usb qdloader 9008 and the threadt is closed now
Click to expand...
Click to collapse
Try this thread... it is still open & active: https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
startswithPendswithOOH said:
Try this thread... it is still open & active: https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Click to expand...
Click to collapse
how about my problem??!!!
nice8man said:
how about my problem??!!!
Click to expand...
Click to collapse
1)What do you mean permanently locked...carrier/sim, mcafee security, something else? If it's carrier you can order a sim unlock code off of ebay for @$4.00 us, or use any other sim unlock services out there.
2)If you changed a d851 to a d850 using board diag and manually loading the partitions - then why not extract a d851 tot and do the same thing?
startswithPendswithOOH said:
1)What do you mean permanently locked...carrier/sim, mcafee security, something else? If it's carrier you can order a sim unlock code off of ebay for @$4.00 us, or use any other sim unlock services out there.
2)If you changed a d851 to a d850 using board diag and manually loading the partitions - then why not extract a d851 tot and do the same thing?
Click to expand...
Click to collapse
thank you for the reply.
1- its carrier unlock + i have no online wallet and i cant get one
2- thats what im looking for is there a way to manually load d851 partitions i mean when i loaded d850 partitions my phone was in dload mode ( hard bricked) do i have to hard unbrick now again?
by the way i can search for other carriers and i find mine under rat:GSM but i m unable to connect to it .
nice8man said:
thank you for the reply.
1- its carrier unlock + i have no online wallet and i cant get one
2- thats what im looking for is there a way to manually load d851 partitions i mean when i loaded d850 partitions my phone was in dload mode ( hard bricked) do i have to hard unbrick now again?
by the way i can search for other carriers and i find mine under rat:GSM but i m unable to connect to it .
Click to expand...
Click to collapse
1) I don't know of a free way to get an unlock code, so if you can't order one you're probably stuck. Pay a friend who can order one for you?
2) If we're on the same page here and you previously used the board diag tool then that should work again. Hard brick usually shows up in your device manager as qualcomm 9008 instead of an lg device, so to get back to that condition you would have to open the phone up and short a pin -
follow the guide in the link I posted before and you should be good to go. I don't have links for any d851 tot files though...sorry, not my variant.
startswithPendswithOOH said:
1) I don't know of a free way to get an unlock code, so if you can't order one you're probably stuck. Pay a friend who can order one for you?
2) If we're on the same page here and you previously used the board diag tool then that should work again. Hard brick usually shows up in your device manager as qualcomm 9008 instead of an lg device, so to get back to that condition you would have to open the phone up and short a pin -
follow the guide in the link I posted before and you should be good to go. I don't have links for any d851 tot files though...sorry, not my variant.
Click to expand...
Click to collapse
so i need to hard brick my phone again?
nice8man said:
so i need to hard brick my phone again?
Click to expand...
Click to collapse
Unfortunately...I think so. If you were to try and use the lg flash tool and try and tot a d851 file into a d850 it'll probably throw some errors - model check, for ex - and won't flash. You can try and see for yourself if you'd like...here's a link for a couple tools; the 1st is kdz method, second is tot: https://forum.xda-developers.com/showthread.php?t=2785089
To brick it again follow guide I linked( https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359), short that 2nd jtag pin in the pic for @5 seconds, plug in the usb, and it should go to qualcomm 9008. You already know how to do the rest as far as loading partitions and such, and if you don't the guide will tell you what to do.
Good luck :good:
startswithPendswithOOH said:
Unfortunately...I think so. If you were to try and use the lg flash tool and try and tot a d851 file into a d850 it'll probably throw some errors - model check, for ex - and won't flash. You can try and see for yourself if you'd like...here's a link for a couple tools; the 1st is kdz method, second is tot: https://forum.xda-developers.com/showthread.php?t=2785089
To brick it again follow guide I linked( https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359), short that 2nd jtag pin in the pic for @5 seconds, plug in the usb, and it should go to qualcomm 9008. You already know how to do the rest as far as loading partitions and such, and if you don't the guide will tell you what to do.
Good luck :good:
Click to expand...
Click to collapse
the link you attached is for mobiles that are already hard bricked mine is not
nice8man said:
the link you attached is for mobiles that are already hard bricked mine is not
Click to expand...
Click to collapse
Yeah....and?
Re-read your previous post where you asked if you'll have to brick it again.
I said yes, and gave you a link on how to do it. Did you read the link? My guess would be no, since the 1st 4 steps tell you how to brick it and enter qualcomm9008 mode.
You're on your own now. Good luck. And you're welcome for the time I spent trying to help you.
startswithPendswithOOH said:
Yeah....and?
Re-read your previous post where you asked if you'll have to brick it again.
I said yes, and gave you a link on how to do it. Did you read the link? My guess would be no, since the 1st 4 steps tell you how to brick it and enter qualcomm9008 mode.
You're on your own now. Good luck. And you're welcome for the time I spent trying to help you.
Click to expand...
Click to collapse
Thank you for your replies man i really appriciate it...i have read that topic like 5 times; maybe i dont understand english very well but when i read the title LG G3 Hard Brick Recovery+ Required Materials:Bricked LG G3 i thought he meant that this topic is for people that has thier phone bricked and need to recover them.
nice8man said:
Thank you for your replies man i really appriciate it...i have read that topic like 5 times; maybe i dont understand english very well but when i read the title LG G3 Hard Brick Recovery+ Required Materials:Bricked LG G3 i thought he meant that this topic is for people that has thier phone bricked and need to recover them.
Click to expand...
Click to collapse
It's cool. Yes the guide is for already bricked phones, but what I was trying to say is since you have a functional phone rt now you're gonna have to brick it, and by brick it I mean qualcomm9008 mode, and that's what the 1st part of the guide shows you how to do by shorting out the pin. Once you get to Qualcomm mode you can then use the board diag tool and load your partitions that you extracted from the tot and hopefully get back to your original d851 phone and get back up and running. Does that make more sense?
Again...good luck
startswithPendswithOOH said:
It's cool. Yes the guide is for already bricked phones, but what I was trying to say is since you have a functional phone rt now you're gonna have to brick it, and by brick it I mean qualcomm9008 mode, and that's what the 1st part of the guide shows you how to do by shorting out the pin. Once you get to Qualcomm mode you can then use the board diag tool and load your partitions that you extracted from the tot and hopefully get back to your original d851 phone and get back up and running. Does that make more sense?
Again...good luck
Click to expand...
Click to collapse
I did not know that you can hard brick the phone by shorting the pins; thank you.
startswithPendswithOOH said:
It's cool. Yes the guide is for already bricked phones, but what I was trying to say is since you have a functional phone rt now you're gonna have to brick it, and by brick it I mean qualcomm9008 mode, and that's what the 1st part of the guide shows you how to do by shorting out the pin. Once you get to Qualcomm mode you can then use the board diag tool and load your partitions that you extracted from the tot and hopefully get back to your original d851 phone and get back up and running. Does that make more sense?
Again...good luck
Click to expand...
Click to collapse
I hard bricked it again and then extracted another D851 tot and then loaded all the necessary partitions but the phone still on qload mode i copied the sbl1.mbm of the D850 and tried them with D851 partitions the phone revived but not in download mode.
I managed tp recover all partitions and the phone is on dowloading mode but still detected as d850 so i have the dll cross error everytime i try to flash a rom even with using the custon dll file.
Dear all, my quick story overwiev:
I have G4 H815 10H
Heat sink upgrade due to bootloop was done week ago and was ok
Wanted make software update to Nougat from 5.1 Lolipop and then some problems comes out
For this puprose wanted gain Root access, so
went through out https://forum.xda-developers.com/g4...t-tmo-vzw-intl-variants-soon-root-lg-t3164765 , but with 1 mistake, I've download T-Mobile H811 10H Version instead of H815 version and run
dd if=/data/media/0/system.rooted.H81110h.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
After this got Security error #11
So went to Stock Frimware flashing KDZ procedure https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
I've decided to flash Europe General H81510B_00.kdz file
but..... now this phone doesn't boot. I can see only Qualcomm hs-usb qdloader 9008 in my device manager.
I know that some of you guys (@TheMadScientist @steadfasterX) are able to unbrick this, really please help.
krzakx said:
Dear all, my quick story overwiev:
I have G4 H815 10H
Heat sink upgrade due to bootloop was done week ago and was ok
went through out https://forum.xda-developers.com/g4...t-tmo-vzw-intl-variants-soon-root-lg-t3164765 , but with 1 mistake, I've download T-Mobile H811 10H Version instead of H815 version and run
dd if=/data/media/0/system.rooted.H81110h.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
So went to Stock Frimware flashing KDZ procedure https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
I've decided to flash Europe General H81510B_00.kdz file
but..... now this phone doesn't boot. I can see only Qualcomm hs-usb qdloader 9008 in my device manager.
I know that some of you guys (@TheMadScientist @steadfasterX) are able to unbrick this, really please help.
Click to expand...
Click to collapse
Well.. You have corrupted the partition table as you used the wrong seek value. The procedure there is EXTREMELY risky and that's one reason why.
You need qfil in that mode. Download this file:
http://droid.binbash.it:8008/unbricking/qfil/h815/G4-h815_fullunbrick_working_7a3ae5809224d.zip
Install qpst and the drivers file from the software folder and after that start qfil. Select the prog_emmc_firehose file from the flashing folder in qfil and select the rawprogramm0 and patch0 file before clicking download.
After succeeded try download mode again and flash any h815 kdz again.
If that doesn't work you either have to wait until I'm back from vacation or find someone else with a box (e.g. infinity) to fix the gpt.
Sent from my LG-H815 using XDA Labs
steadfasterX thanks for your effort! Going to try it morning.
By the meantime maybe @TheMadScientist can say something from his experience?
How about SD card unbricking method https://forum.xda-developers.com/g4/help/unbrick-lg-g4-h811-9008-qualcomm-t3456417
I've tried once but it dosen't work.
Thanks in advance.
krzakx said:
steadfasterX thanks for your effort! Going to try it morning.
By the meantime maybe @TheMadScientist can say something from his experience?
How about SD card unbricking method https://forum.xda-developers.com/g4/help/unbrick-lg-g4-h811-9008-qualcomm-t3456417
I've tried once but it dosen't work.
Thanks in advance.
Click to expand...
Click to collapse
Guys I just studied it I ever actually had to unbrick mine. I studied in help for others so I don't know how much help I would exactly be
krzakx said:
steadfasterX thanks for your effort! Going to try it morning.
By the meantime maybe @TheMadScientist can say something from his experience?
How about SD card unbricking method https://forum.xda-developers.com/g4/help/unbrick-lg-g4-h811-9008-qualcomm-t3456417
I've tried once but it dosen't work.
Thanks in advance.
Click to expand...
Click to collapse
Yes that way is possible too. The only way it worked for me is by using dd to flash the gpt to the external sdcard and then flashing the bootloader stack plus laf. Quite easy if you have some Linux experience. But if not... you need a proper guide..
maybe there is a working h815 image out there as well but the one you're referring to is for the h811.... OMG you haven't used that one did you??? H811 has ARB!!! If you don't know what that means read https://bit.do/antirollg4 and ASK before using files not related to your model.
I'm very interested what SALT would tell us about your ARB once the device is working again....
Sent from my LG-H815 using XDA Labs
I have some base linux experience, (Debian) so no "handle follow guide" would be needed.
Yes, I have used H811 file, that was my mistake . I've exactly used this file http://downloads.codefi.re/thecubed/lg_g4/lef/h81110h.tar.gz from this topic https://forum.xda-developers.com/g4...t-tmo-vzw-intl-variants-soon-root-lg-t3164765 ,
Dear steadfasterX , please take one more time overlook for my situation and think about wright steps. Waiting for yours advices.
Best regards.
krzakx said:
I have some base linux experience, (Debian) so no "handle follow guide" would be needed.
Yes, I have used H811 file, that was my mistake . I've exactly used this file http://downloads.codefi.re/thecubed/lg_g4/lef/h81110h.tar.gz from this topic https://forum.xda-developers.com/g4...t-tmo-vzw-intl-variants-soon-root-lg-t3164765 ,
Dear steadfasterX , please take one more time overlook for my situation and think about wright steps. Waiting for yours advices.
Best regards.
Click to expand...
Click to collapse
No I was talking about the sdcard files. Flashing the h811 system file will not increase ARB (as said you corrupted the gpt though) but when you flash the h811(which you linked in your second post!) files to write the sdcard and then trying to boot from the sdcard it very likely will increase the ARB.
Ok so you haven't used the sdcard method yet?
Then try that one:
https://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853
Again try to boot to download mode with that and flash a h815 kdz. You MAY have luck but it depends. Give it a try.
Sent from my LG-H815 using XDA Labs
krzakx said:
Dear all, my quick story overwiev:
Click to expand...
Click to collapse
In the photo of your phone in download mode, it identifies as an LG-H810 running H81010o.
If I may ask, where did you get this phone from?
terence.tan said:
In the photo of your phone in download mode, it identifies as an LG-H810 running H81010o.
If I may ask, where did you get this phone from?
Click to expand...
Click to collapse
Dear @terence.tan you've asked good question.
So phone is from China seller, additionally I've made some photos of motherboard and got confused as you can see there VS986_MAIN_1.0 oh no... is all so mixed up.
Unfortunately do not have system.img back up eh.... stupid me.
SD Card method doesn't work.
Now I am think if I should go this method
https://forum.xda-developers.com/g4/help/lg-g4-vs986-super-hard-brick-unbrick-fw-t3666784
it's only idea because my motherboard seems to be VS968 labeled, but let me ask you guys as specialists.
Waiting for answer. Thanks.
One more question regarding SD Card method guys,
I've just prepared SD card fallowing this topic https://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853 , but it doesn't work.
Just for confirmation here you can se parted print, can you check please If I've burned SD Card image properly?
https://hastebin.com/inimikipux.sql
Thanks
Hi there! So you have a phone with a VS986 main board, which identifies as an H810, which was sold to you as an H815. (Which you have flashed with H811 software.)
The seller of your phone in China has done something strange to make this all work, we don't know what.
I'm sure you will understand, it will be very difficult for anyone to tell you exactly what to do.
The sdcard unbrick you tried didn't work because it has the boot stack files for H815, which require a phone with ARB version 0. I suspect you will need to copy either the VS986 or H810 boot stack files to your sdcard for it to work. (I don't know which, only the seller knows...)
However trying alternate boot stacks has a chance to increment your ARB; you should consider the consequences and not use anything with a high ARB before trying lower ones...
steadfasterX said:
Well.. You have corrupted the partition table as you used the wrong seek value. The procedure there is EXTREMELY risky and that's one reason why.
You need qfil in that mode. Download this file:
http://droid.binbash.it:8008/unbricking/qfil/h815/G4-h815_fullunbrick_working_7a3ae5809224d.zip
Install qpst and the drivers file from the software folder and after that start qfil. Select the prog_emmc_firehose file from the flashing folder in qfil and select the rawprogramm0 and patch0 file before clicking download.
After succeeded try download mode again and flash any h815 kdz again.
If that doesn't work you either have to wait until I'm back from vacation or find someone else with a box (e.g. infinity) to fix the gpt.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I'm literally praying to the Android Gods that this works. If it doesn't then I am truly truly lost...
Wish me luck!
Ugh!
I get this...
Sending NOP
ReadFile last error: 0
Response is NULL
NOP: Fail Code: 14
Unable to send FireHose NOP. Device is not in FireHose mode!
Download Fail:FireHose Fail FireHose Fail: Failed to send FireHose NOP to the phone.
Finish Download
Man, This LG is kicking my ass!
Any suggestions?
donniegalaxy2 said:
Ugh!
I get this...
Sending NOP
ReadFile last error: 0
Response is NULL
NOP: Fail Code: 14
Unable to send FireHose NOP. Device is not in FireHose mode!
Download Fail:FireHose Fail FireHose Fail: Failed to send FireHose NOP to the phone.
Finish Download
Man, This LG is kicking my ass!
Any suggestions?
Click to expand...
Click to collapse
Having just these problems on qfil with my h815 did you found a solution?
sr.arenisca said:
Having just these problems on qfil with my h815 did you found a solution?
Click to expand...
Click to collapse
No solution found by me!!! I gave up and sold the phone to ecoATM!
Is there any way to flash a kdz from my G4 ?
LG G4 with locked bootloader, Twrpinfish installed
jason_l367 said:
Is there any way to flash a kdz from my G4 ?
LG G4 with locked bootloader, Twrpinfish installed
Click to expand...
Click to collapse
It would help if you were more specific about what you are trying to do.
With that said, are you talking a stock kdz or a rooted system image? If a rooted system image you can do it with TWRP-in-FiSH, provided you can obtain the one you want from a member who provides his own TWRP-in-FiSH system image backup but you can't do a stock KDZ. Cross-flashing any different model firmwares, at this stage (until steadfasterX completes and publishes his boot loader unlock process), runs a high risk of a hard brick.
sdembiske said:
It would help if you were more specific about what you are trying to do.
With that said, are you talking a stock kdz or a rooted system image? If a rooted system image you can do it with TWRP-in-FiSH, provided you can obtain the one you want from a member who provides his own TWRP-in-FiSH system image backup but you can't do a stock KDZ. Cross-flashing any different model firmwares, at this stage (until steadfasterX completes and publishes his boot loader unlock process), runs a high risk of a hard brick.
Click to expand...
Click to collapse
Hi Sdembiske, I read about the unnofficial bootloader unlock: https://forum.xda-developers.com/g4/general/bl-unlock-unlock-bootloader-proof-t3648288 and it seems H812 is not fully tested yet (see Proofs section). I'm not brave enough to try it on my phone until it has been fully tested. I know if everyone thought like me, there would be no progress.. :laugh:. Thank god theres some brave people out there....
sdembiske said:
It would help if you were more specific about what you are trying to do.
With that said, are you talking a stock kdz or a rooted system image? If a rooted system image you can do it with TWRP-in-FiSH, provided you can obtain the one you want from a member who provides his own TWRP-in-FiSH system image backup but you can't do a stock KDZ. Cross-flashing any different model firmwares, at this stage (until steadfasterX completes and publishes his boot loader unlock process), runs a high risk of a hard brick.
Click to expand...
Click to collapse
Thx. I was provided a tot of genysys with Twrpinfish injected. Just thought there might be a way. Also, itd be neat to flash my kdz or tot from the device
Thx to @the_naxhoo for this tot
Also there seems to be easy ways to edit a kdz with hex editors apps than winhex for example, which requires a hefty priced pro add-on. BTW I've flashed different region kdz with LGUP without issues.
jason_l367 said:
Thx to @the_naxhoo for this tot
Also there seems to be easy ways to edit a kdz with hex editors apps than winhex for example, which requires a hefty priced pro add-on. BTW I've flashed different region kdz with LGUP without issues.
Click to expand...
Click to collapse
Being able to flash different region kdz's is very Model specific - e.g. H815 International/Europe version plus a very limited number of other models and only one or two with locked bootloaders (most of which have issues from what I can tell). Some models, like the H812 are locked up tighter, running a very high risk of hard bricks screwing around with other model/region firmware flashing- So again, you have to be specific.
Apologies. I own a H815T and have flashed H815 kdz's , so my question is- if there is any way to zip a kdz for flashing, extract correct partitions for the zip , edit the kdz for flashing from the device etc, i think it would be a pretty handy tool
Just a thought.
jason_l367 said:
Apologies. I own a H815T and have flashed H815 kdz's , so my question is- if there is any way to zip a kdz for flashing, extract correct partitions for the zip , edit the kdz for flashing from the device etc, i think it would be a pretty handy tool
Just a thought.
Click to expand...
Click to collapse
Once steadfasterx releases his unofficial bootloader unlock you can flash any g4 variants firnware and even better, custom roms. Just hang in there man...its coming soon
jason_l367 said:
Apologies. I own a H815T and have flashed H815 kdz's , so my question is- if there is any way to zip a kdz for flashing, extract correct partitions for the zip , edit the kdz for flashing from the device etc, i think it would be a pretty handy tool
Just a thought.
Click to expand...
Click to collapse
Check out steadfasterX's SALT: https://forum.xda-developers.com/g4/general/tool-salt-lg-revolution-t3717864
Has some of what you're looking for now and will eventually, when completed, be able to flash what you need.
Thanks mates
sdembiske said:
Check out steadfasterX's SALT: https://forum.xda-developers.com/g4/general/tool-salt-lg-revolution-t3717864
Has some of what you're looking for now and will eventually, when completed, be able to flash what you need.
Click to expand...
Click to collapse
Sorry if I'm asking in the wrong place but I followed your guide to bullet proof method to get started with SALT - FWUL 2.5 persistent.
I get to the welcome screen but when I press enter on 'FWUL 2.5 persistent' it says no such directory.
I have chosen -linux ,arch linux32bit (64bit wasn't available on my laptop) after following steps to create the .vdi drive in VirtualBox directory
Nevermind ,I had to use x64 arch Linux.
jason_l367 said:
Sorry if I'm asking in the wrong place but I followed your guide to bullet proof method to get started with SALT - FWUL 2.5 persistent.
I get to the welcome screen but when I press enter on 'FWUL 2.5 persistent' it says no such directory.
I have chosen -linux ,arch linux32bit (64bit wasn't available on my laptop) after following steps to create the .vdi drive in VirtualBox directory
Click to expand...
Click to collapse
We should move this over to the FWUL thread.
First, confirm you have downloaded only from this location in the FWUL OP for the persistent versions (my concern here is that you have downloaded a forgetful version):
https://androidfilehost.com/?w=files&flid=214529
Make sure you are running the latest version of (Windows) VirtualBox and that you have installed the Extension Pack as well.
Even if your Windows PC/laptop is 32bit, the VirtualBox drop-down menu should allow you, in the 'New' setup menu, to select Linux and under that entry, the 64bit Arch Linux OS (it should be right above or below the 32bit version in the drop-down menu) - that is what FWUL is based on ... i.e., it doesn't matter that your PC/laptop is 32bit.
Ensure you are matching your .img file name in the conversion command exactly to the persistent .img file name you downloaded, extracted and moved over to the VirtualBox original install folder to run the conversion command. Copying and pasting the conversion command from my post, is the most error free way to do it, provided the file name matches exactly to the .img file you downloaded.
Important: Insure you have enough available hard drive space on you PC/laptop to install the size of FWUL .vdi disk you created, in addition to the .img file you downloaded.
Check the following two locations on your PC/Laptop hard drive for the .vdi file you created from the conversion command.
C:\Users\Your_User_Name\VirtualBoxVMS
C:\Users\Your_User_Name\AppData\Local\VirtualStore\Program Files\Oracle\VirtualBox\
If you need to try again, remove the FWUL install and delete all FWUL related files - double check the two file locations above to make sure there are no FWUL related files there whatsoever.
Any further questions, please post to the FWUL thread.
Thanks dude. It worked :good:
jason_l367 said:
Thanks dude. It worked :good:
Click to expand...
Click to collapse
No problem. I can probably use the troubleshooting guide I prepared for you again on the FWUL thread.
Glad it worked - had me concerned there for a bit as I thought I laid everything out pretty succinctly in my original post, to avoid errors.
Enjoy - particularly when steadfasterX completes the full-meal-deal.
SALT v4.0 will come with flashing support for kdz and restoring image files (e.g from a previous backup)
Sent from my LG-H815 using XDA Labs
steadfasterX said:
SALT v4.0 will come with flashing support for kdz and restoring image files (e.g from a previous backup)
Click to expand...
Click to collapse
Yeah I'm backing up now
One question. How may hours does it take to do a full backup in salt?
I don't mean to be rude, but its been like 3 hours..
Sorry , took a basic backup but it failed verification. I'll have to do some reading
epescially when trying out the usu unlock feature!!!!
jason_l367 said:
Yeah I'm backing up now
One question. How may hours does it take to do a full backup in salt?
I don't mean to be rude, but its been like 3 hours..
Click to expand...
Click to collapse
My full backup (29GB) took up to approx. 6 hours to complete. Partial completes very quickly ...
Yeah I downloaded 30GB FWUL.
Hello all,
-I bought a 'refurbished' LG G4 online (claimed to be H815), but when I got it & checked the motherboard inside, it's VS986 instead.
Currently it's on H815 v10h (Lollipop), with ARB v2, and Baseband is MPSS.BO.2.5.c3-00070-M8992FAAAANAZM-1.19025.1
-What's is the best option I have (which ROM to flash)? I'm from Malaysia & I need GSM for 2G/3G capability (AFAIK Verizon's VS986 uses CDMA)*.
Please advise, thank you.
*EDIT: I entered Service Menu & found that several GSM & WCDMA modes are supported, but none of LTE modes is available.
Musafir_86 said:
Hello all,
-I bought a 'refurbished' LG G4 online (claimed to be H815), but when I got it & checked the motherboard inside, it's VS986 instead.
Currently it's on H815 v10h (Lollipop), with ARB v2, and Baseband is MPSS.BO.2.5.c3-00070-M8992FAAAANAZM-1.19025.1
-What's is the best option I have (which ROM to flash)? I'm from Malaysia & I need GSM for 2G/3G capability (AFAIK Verizon's VS986 uses CDMA)*.
Please advise, thank you.
*EDIT: I entered Service Menu & found that several GSM & WCDMA modes are supported, but none of LTE modes is available.
Click to expand...
Click to collapse
The problem with Frankensteins like this is nobody knows what EXACTLY they did to make it look like a h815.
First thing to try is checking the ARB (Antirollback, see my sig) and if you are one of the 1% of lucky users then you may see "nonfusing device" instead of an ARB level.
Assuming that you did that already (as u mentioned ARB2) u are screwed.
There is no valid way to get to a good result here.
Your main issue is that the modem partition must be a vs986 one - or at least a vs986 compatible one as the ARB also takes place in that partition.
Second, if you cannot change the modem partition u might not be able to get 2G/3G as you already found out.
unlocking the device won't help either as the main issue you have relies on the the modem (partition) and even when flashing a vs986 ROM or any other it might never work.
Last - but not least - whatever you do or plan to do: kee my first sentence in mind. Each step you do can easily hard brick your device.
Ofc you can use QFIL to likely bring it back to life (the G4's are really hard to brick until an unusable state) but for this you need the extra tools, knowledge and time to learn.
sorry but there is nothing much you can do other then request your money back as you were tricked.
if you can't I may would try getting another modem partition to work with but doing that requires also a lot of time to learn how to use SALT to extract KDZs, identify the ARB of the modem partition properly (so you do not increase the ARB level by flashing a wrong modem partition) and so on..
gl
.-
steadfasterX said:
The problem with Frankensteins like this is nobody knows what EXACTLY they did to make it look like a h815.
First thing to try is checking the ARB (Antirollback, see my sig) and if you are one of the 1% of lucky users then you may see "nonfusing device" instead of an ARB level.
Assuming that you did that already (as u mentioned ARB2) u are screwed.
There is no valid way to get to a good result here.
Your main issue is that the modem partition must be a vs986 one - or at least a vs986 compatible one as the ARB also takes place in that partition.
Second, if you cannot change the modem partition u might not be able to get 2G/3G as you already found out.
unlocking the device won't help either as the main issue you have relies on the the modem (partition) and even when flashing a vs986 ROM or any other it might never work.
Last - but not least - whatever you do or plan to do: kee my first sentence in mind. Each step you do can easily hard brick your device.
Ofc you can use QFIL to likely bring it back to life (the G4's are really hard to brick until an unusable state) but for this you need the extra tools, knowledge and time to learn.
sorry but there is nothing much you can do other then request your money back as you were tricked.
if you can't I may would try getting another modem partition to work with but doing that requires also a lot of time to learn how to use SALT to extract KDZs, identify the ARB of the modem partition properly (so you do not increase the ARB level by flashing a wrong modem partition) and so on..
gl
.-
Click to expand...
Click to collapse
-Thanks for your reply.
-About returning & requesting a refund, I think it'll be hard as I already damaged the warranty sticker over one of the screws while trying to check the board.
-If we ignore the modem issue for now (maybe use it as WiFi-only device), then what's the best ROM I could flash? I hope at least Marshmallow so it'll last longer as more & more apps are targetting higher Android API levels.
-BTW, I just tried flashing VS9862BA_00_0525_ARB02.kdz but LG UP says "KDZ file is invalid". On another note, while in download mode, I just noticed it says:
Code:
USER S0.0 AS0.0 B91 UHS
S U LG-H810 05.1 Hrev_10
H81010o
-So, now it also has AT&T's H810 pieces inside too?
-BTW, sorry for PM'ing you earlier; I didn't notice your signature (even though you put it in big, red fonts!).
Musafir_86 said:
-Thanks for your reply.
-About returning & requesting a refund, I think it'll be hard as I already damaged the warranty sticker over one of the screws while trying to check the board.
-If we ignore the modem issue for now (maybe use it as WiFi-only device), then what's the best ROM I could flash? I hope at least Marshmallow so it'll last longer as more & more apps are targetting higher Android API levels.
-BTW, I just tried flashing VS9862BA_00_0525_ARB02.kdz but LG UP says "KDZ file is invalid". On another note, while in download mode, I just noticed it says:
Code:
USER S0.0 AS0.0 B91 UHS
S U LG-H810 05.1 Hrev_10
H81010o
-So, now it also has AT&T's H810 pieces inside too?
-BTW, sorry for PM'ing you earlier; I didn't notice your signature (even though you put it in big, red fonts!).
Click to expand...
Click to collapse
-Okay, now I have successfully flashed VS9862BA_00_0525_ARB02.kdz by extracting the DZ file & flashing it directly! :good:
However, it seems Android FRP (Firmware Reset Protection) has been triggered; need to figure on how to bypass this while on 2BA firmware.....
Musafir_86 said:
-Thanks for your reply.
-About returning & requesting a refund, I think it'll be hard as I already damaged the warranty sticker over one of the screws while trying to check the board.
-If we ignore the modem issue for now (maybe use it as WiFi-only device), then what's the best ROM I could flash? I hope at least Marshmallow so it'll last longer as more & more apps are targetting higher Android API levels.
-BTW, I just tried flashing VS9862BA_00_0525_ARB02.kdz but LG UP says "KDZ file is invalid". On another note, while in download mode, I just noticed it says:
-Okay, now I have successfully flashed VS9862BA_00_0525_ARB02.kdz by extracting the DZ file & flashing it directly! :good:
However, it seems Android FRP (Firmware Reset Protection) has been triggered; need to figure on how to bypass this while on 2BA firmware.....
Click to expand...
Click to collapse
Warranty or not i would return it as its not what you had paid for. But up to you and ofc as you flashed a kdz on it you would need to get it back to the state jt was before..
You could unlock and flash nougat, oreo, pie but as with flashing the vs986 kdz/dz nothing comes without a risk ofc. Especially on Frankensteins!
The good is that you likely can revert UsU if you ever want to as you have a fusing device.
Sent from my OnePlus 7T Pro using XDA Labs