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.
Related
Hello everyone !
So i bought this G3 online (second hand), on th back it sais it's D855 variant 32/3 and it had kitkat.. and wanted to upgrade so i looked it up and found MM update 30B.kdz so i backed up my EFS and flashed it then i got stuck in a bootloop so i flashed another rom LP 21A.kdz and it worked but no network neither WiFi or BT.. USB debugging works but no MTP or PTP connexion and Model name became D855V.. i looked this problem online and someone mentionned it may be caused because it's a different variant, checked my device info on some IMEI check websites and they said it's L990.. i opened it up to confirme and it says it's indeed a LS990 on the motherboard.. so i tried to flash a LS990 rom back but al i could find is a .TOT extension roms which demands a .dll file and check etc.. i tried flashing them using LGUP and LG Flash Tool and they both gave me an erreur message that it's a different device modele.. tried different .dll files LS990....dll , D855....dll and LGUP8974.dll wich is supposed to ignore some checks but still nothing worked.. i think .kdz roms doesn't do that check wich brought me to this problem in the 1st place.. but i couldn't find a .kdz rom for LS990 anywhere.. found US990...kdz but don't think it's the same !
guys please help !.. i'm a civil engineering student whom is drowning in debts and spent the last money i got on this phone because i needed it and can't afford to lose it like that.. you could letteraly save my life ;D
sorry for bad English.
Download LS990 .tot and D855's .dll. Use a hexeditor to change the headers of the ls990 .tot to the name found on the D855's .tot. Flash the generated LS990(now disguised as a D855) .tot unto phone using the D855's .dll
So i installed a hex editor(HxD) and opened the LS990 .tot and searched for every "LS990" header and changed them all to what replaces "D855" in D855 .tot.. stop me if i'm in the wrong way, then saved the work so the LS990 .tot should be disguised as a D855 .tot right ? and i got the D855 .dll already. is that ready to be flashed now ? wouldn't it cause a hardbrick or sth ?.. it's not like i have many options but i just don't want to make things worse..
Ps: while i was in Maths class i was trying o think of sth.. and thought
that i may be able to root it and install TWRP then flash a LS990 rom since i have USB debugging working.. but i have to root it first and the way to root it while on LP is LG One Click Root but i'm having a hard time doing that although i tried everything but i think that's because of the wrong rom.. just wanted to mention it !
Thank you Sir !.. i'm waiting for your comments before i flash the modified Rom !
So i installed a hex editor(HxD) and opened the LS990 .tot and searched for every "LS990" header and changed them all to what replaces "D855" in D855 .tot.. stop me if i'm in the wrong way, then saved the work so the LS990 .tot should be disguised as a D855 .tot right ? and i got the D855 .dll already. is that ready to be flashed now ? wouldn't it cause a hardbrick or sth ?.. it's not like i have many options but i just don't want to make things worse..
Ps: while i was in Maths class i was trying o think of sth.. and thought
that i may be able to root it and install TWRP then flash a LS990 rom since i have USB debugging working.. but i have to root it first and the way to root it while on LP is LG One Click Root but i'm having a hard time doing that although i tried everything but i think that's because of the wrong rom.. just wanted to mention it !
Thank you Sir !.. i'm waiting for your comments before i flash the modified Rom !
flashed D855 rom to LS990 and only .tot roms available "device modele diff".. HELP!
Hello everyone !
So i bought this G3 online (second hand), on th back it sais it's D855 variant 32/3 and it had kitkat.. and wanted to upgrade so i looked it up and found MM update 30B.kdz so i backed up my EFS and flashed it then i got stuck in a bootloop so i flashed another rom LP 21A.kdz and it worked but no network neither WiFi or BT.. USB debugging works but no MTP or PTP connexion and Model name became D855V.. i looked this problem online and someone mentionned it may be caused because it's a different variant, checked my device info on some IMEI check websites and they said it's L990.. i opened it up to confirme and it says it's indeed a LS990 on the motherboard.. so i tried to flash a LS990 rom back but all i could find is a .TOT extension roms which demands a .dll file and check etc.. and no .kdz since Sprint didn't realease any as far i found out, i tried flashing them using LGUP and LG Flash Tool and they both gave me an erreur message that it's a different device modele.. tried different .dll files LS990....dll , D855....dll and LGUP8974.dll wich is supposed to ignore some checks but still nothing worked.. i think .kdz roms doesn't do that check wich brought me to this problem in the 1st place.. but i couldn't find a .kdz rom for LS990 anywhere.. found US990...kdz but don't think it's the same !
So somone told me to try sth so i installed a hex editor(HxD) and opened the LS990 .tot and searched for every "LS990" header and changed them all to what replaces "D855" in D855 .tot.. stop me if i'm in the wrong way, then saved the work so the LS990 .tot should be disguised as a D855 .tot right ? and i got the D855 .dll already. i was worried that it would cause a hardbrick or sth .. it's not like i have many options but i just didn't want to make things worse.. then i tried to flash it anyway but both lg flash tool and lgup pop up an errour message after check and stops before it even starts
Ps: while i was in Maths class i was trying o think of sth.. and thought
that i may be able to root it and install TWRP then flash a LS990 rom since i have USB debugging working.. but i have to root it first and the way to root it while on LP is LG One Click Root but i'm having a hard time doing that although i tried everything but i think that's because of the wrong rom.. just wanted to mention it !
guys please help !.. i'm a civil engineering student whom is drowning in debts and spent the last money i got on this phone because i needed it and can't afford to lose it like that.. you could letteraly save my life ;D
sorry for bad English.
Hello, Since the Board Giag Tool Doesnt work for the D851 and the only way to unbrick the D851 is by sending it to LG Repair or Some Other Repair or Flashing it with either Medusa Box or Octoplus Box. It wasnt long when @Kathik figured out that the LG G3 F460 S/K/L which is also not supported by the Board Diag Tool can be unbricked by creating a debrick image. You can find his thread here.
This debrick image that @Kathik used is just a dump of the bootloaders from a working LG G3 F460. And all we need to do is to find a way to create the debrick image from a working D851 running the firmware version the bricked D851 was on before it got bricked.
Fortunately for all of us, i got my hands on the zip file which creates the dump or debrick image (Thanks to @Anik49) We have the file.
So all we need is volunteers to flash this zip file in TWRP and once done, you should see a file name debrick.img.zip on your Sdcard.
If this work, we wont need to send our devices for repairs or dissasemble them when they get bricked.
Please feel free to ask any questions about the process.
I flashed the zip and it said it created the debrick.img.zip but I am unable to locate it anywhere. I'm assuming this is because I am on Stock LG Marshmallow with the slight research I did with the thread you linked.
Sorry bud, I tried. It was the only G3 I had hands on. I hope someone else will volunteer in our community.
Maybe u need to downgrade to 5.0
I wrote in the other thread, the day that I put to work to upgrade to Marhsmallow, i will make the debrick files in some versions as 10c, 10f and other higher ... Right now I have a lot of work and I can not do today. Greetings
Any updates on this?
I would also like to hear from a kind soul as now I have a bricked D851 too
UP , anyone ? im suffring with my D851
Jyed said:
UP , anyone ? im suffring with my D851
Click to expand...
Click to collapse
I tried creating the unbrick SD this week but failed to do. Seems like the phone was not actually reading from the SD files.
But I have successfuly created the files to unbrick the phone now as long as the phone is in 9008 mode.
http://forum.xda-developers.com/tmo...hard-brick-t2921642/post67988741#post67988741
makiavelo said:
I wrote in the other thread, the day that I put to work to upgrade to Marhsmallow, i will make the debrick files in some versions as 10c, 10f and other higher ... Right now I have a lot of work and I can not do today. Greetings
Click to expand...
Click to collapse
Hi again, this is my debrick file from D851 running Cloudy 1.2 over a fresh V10c instalation. If it's necesary another version or V10c without Cloudy 1.2, tellme... i will upgrade to marshmallow in next weeks.
http://www.mediafire.com/download/fvyz5bgd8xwb13n/debrick.zip
Hi Guys i have LG G3 D851 ..i am currently on MM i want to downgrade to lollipop so i downloaded the kdz file V20e but the problem is that LGUP cannot detect my G3 shows the device as unknown model but correctly shows the comports i even tried using LGFlash tool used seems that i cannot downgrade shows error and stops so i wanna know is there any way to fix this unknown model in LGUP ...
Guess no one wants to help here ?? To anyone else who has this issue u may need to change the buildprop file and ur phone must be rooted it still doesnt shows as unknown in LGUP but since i have rooted my phone n bought a new battery and installed xposed and im having a good battery life i still want to know why it aint showing up in LGUP
jinderation said:
Guess no one wants to help here ?? To anyone else who has this issue u may need to change the buildprop file and ur phone must be rooted it still doesnt shows as unknown in LGUP but since i have rooted my phone n bought a new battery and installed xposed and im having a good battery life i still want to know why it aint showing up in LGUP
Click to expand...
Click to collapse
Did you ever resolve this problem? The same thing is happening to me.
dant3ch said:
Did you ever resolve this problem? The same thing is happening to me.
Click to expand...
Click to collapse
i think D851 doesnt support LGUPdirect mthod thats what i figure but u can go back via tot method to lollipop or kitkat...im still using MM with custom rom
jinderation said:
i think D851 doesnt support LGUPdirect mthod thats what i figure but u can go back via tot method to lollipop or kitkat...im still using MM with custom rom
Click to expand...
Click to collapse
Try this dll it works..
https://drive.google.com/file/d/0B0VrTZddvLF7b3Q1b1BlQ2w0clE/view
Salik Iqbal said:
Try this dll it works..
https://drive.google.com/file/d/0B0VrTZddvLF7b3Q1b1BlQ2w0clE/view
Click to expand...
Click to collapse
is there somehow can u install this dll ? i dont somehow know it ?
jinderation said:
is there somehow can u install this dll ? i dont somehow know it ?
Click to expand...
Click to collapse
Dont install it.. use it with flashtool as dll and tot for ur model.. old flashtool way
Salik Iqbal said:
Dont install it.. use it with flashtool as dll and tot for ur model.. old flashtool way
Click to expand...
Click to collapse
i cant seem to flash via lgflashtool 2014 cuz it needs kdz n in TWRP u need .zip file...what other flashing method is available?
jinderation said:
i cant seem to flash via lgflashtool 2014 cuz it needs kdz n in TWRP u need .zip file...what other flashing method is available?
Click to expand...
Click to collapse
The only flashing method that has ever worked for me when my phone was bricked along with Corrupted recovery is the .TOT method. And that I'm afraid is the one from where you have to start all over from Out of the box experience with 4.4 Kitkat. If the LGFlashTool2014 does not work for you, I recommend the LGFlashtoolv1.8.1 + the crack. It will not ask you for the KDZ and should allow you to downgrade without any hassle.
There are 2 things you will need:
LGD851AT-01-V10c.zip & LGFLASHv160.dll
This will point you in the right direction. Just scroll down to the text where it says "2014 TOT Method (Old/Outdated)"
http://forum.xda-developers.com/showthread.php?t=2785089
Good luck
jinderation said:
Guess no one wants to help here ?? To anyone else who has this issue u may need to change the buildprop file and ur phone must be rooted it still doesnt shows as unknown in LGUP but since i have rooted my phone n bought a new battery and installed xposed and im having a good battery life i still want to know why it aint showing up in LGUP
Click to expand...
Click to collapse
its dll you must download this one LGUP_8974.dll " LGUP_8974_8084_DLL_Ver_0_3_17_6.msi "
Hi guys,I'm a Chinese ,I found this dll in Chinese forum ,but it's difficult to download,thank you !! and I'll take this
Solution to LGUP LG G3 unknown
While an old thread, it'll be found in searches. For anybody who gets "UNKNOWN" device with LGUP for the LG G3, I found that LGUP for the G3 is often distributed with the wrong DLL file. See the details here, post #11.
HTH
LGUP worked with my LG G3 D851 when I used it as in this tutorial:
LG G3 LineageOS Tutorial - Linus Tech Tips
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?