Need LG-Q710AL FIRMWARE for unbrick phone please cant found - Android Q&A, Help & Troubleshooting

Need LG-Q710AL FIRMWARE for unbrick phone please cant found

I need it as well a client brought in his stylo 4 will not boot it gets an error "images of verified boot not installed all slots are unbootable" I can only get into download mode. It tries to go to recovery but dies a few seconds beforehand. If I find it I will post a link here.

Please do, I'll do the same!

g0new0rk said:
I need it as well a client brought in his stylo 4 will not boot it gets an error "images of verified boot not installed all slots are unbootable" I can only get into download mode. It tries to go to recovery but dies a few seconds beforehand. If I find it I will post a link here.
Click to expand...
Click to collapse
Hello-Have you had any luck with this yet? I can't even find a boot image to flash with patched lgup, not that I know it would work...I am having the same message.

blodgettmike said:
Hello-Have you had any luck with this yet? I can't even find a boot image to flash with patched lgup, not that I know it would work...I am having the same message.
Click to expand...
Click to collapse
Not yet. I have not been able to dump it with patched LGUP and DLL I have tried DLL from "LMQ710MS" which is a Qualcomm chip, "LMQ710BAW" which is a south America QNote+ but seems to be the same phone on the inside. Also tried "LMQ710FA" a south America Q Stylus Plus seems to be same on the inside. both have the MT6750S
I have gotten it to pretend it dumps the phone. It goes through the motions but open any of the files in hxd and they are either full of 00 00 00 00 or have what looks like GPT repeated info in it. I have not been following LG much and this is just for fun for me. I tried to use the Lg download mode tools in python but cannot seem to get a connection I am guessing since they came out in 2016 LG has switched up their protocol. Seems they encrypted the DLL's as well.
I have tried LG Bridge, LG Mobile Support Tool. The logs show the IMEI check fails. I assume it means it is a sprint/boost phone as I know the IMEI is not blacklisted or stolen. But more of they realize it is a boost/sprint unit and block it. I tried every trick I could find I get as far as it says "downloading software" but it just hangs. I am going to try fresh installs after while just to rule it out. I would like to find out if anyone has used any LG tools to do a firmware update or firmware error recovery on a Sprint or Boost phone that is within 6 months old.
The story I heard is Sprint thinks their OTA updates should fix everything there is no reason to release firmware. I sure hope T-Mobile is buying Sprint. It seems is trying very hard to drive down there sell price... I talked to LG, of course, they cannot do anything until one of there techs puts hands on it. I am thinking of just trading it in it is only 4 months old. I just hate to give up or fail. But there is some type of issue with them I highly doubt the person above and myself are the only ones that have had this issue. I know there is at least 1 more person seen them on Lg forums.
If I make any headway or happen across a fix I will update within this thread.

g0new0rk said:
Not yet. I have not been able to dump it with patched LGUP and DLL I have tried DLL from "LMQ710MS" which is a Qualcomm chip, "LMQ710BAW" which is a south America QNote+ but seems to be the same phone on the inside. Also tried "LMQ710FA" a south America Q Stylus Plus seems to be same on the inside. both have the MT6750S
I have gotten it to pretend it dumps the phone. It goes through the motions but open any of the files in hxd and they are either full of 00 00 00 00 or have what looks like GPT repeated info in it. I have not been following LG much and this is just for fun for me. I tried to use the Lg download mode tools in python but cannot seem to get a connection I am guessing since they came out in 2016 LG has switched up their protocol. Seems they encrypted the DLL's as well.
I have tried LG Bridge, LG Mobile Support Tool. The logs show the IMEI check fails. I assume it means it is a sprint/boost phone as I know the IMEI is not blacklisted or stolen. But more of they realize it is a boost/sprint unit and block it. I tried every trick I could find I get as far as it says "downloading software" but it just hangs. I am going to try fresh installs after while just to rule it out. I would like to find out if anyone has used any LG tools to do a firmware update or firmware error recovery on a Sprint or Boost phone that is within 6 months old.
The story I heard is Sprint thinks their OTA updates should fix everything there is no reason to release firmware. I sure hope T-Mobile is buying Sprint. It seems is trying very hard to drive down there sell price... I talked to LG, of course, they cannot do anything until one of there techs puts hands on it. I am thinking of just trading it in it is only 4 months old. I just hate to give up or fail. But there is some type of issue with them I highly doubt the person above and myself are the only ones that have had this issue. I know there is at least 1 more person seen them on Lg forums.
If I make any headway or happen across a fix I will update within this thread.
Click to expand...
Click to collapse
Thanks for the update, very much appreciated!

blodgettmike said:
Thanks for the update, very much appreciated!
Click to expand...
Click to collapse
Check your "private messages" .

I had the same problem. I just bought a new one from Walmart and returned the busted phone in its stead. Not exactly on the up-and-up, but boost will eat that cost. Is there a way I can extract the KDZ from my phone now? It's the same phone, just with all the bootable slots!

g0new0rk said:
Not yet. I have not been able to dump it with patched LGUP and DLL I have tried DLL from "LMQ710MS" which is a Qualcomm chip, "LMQ710BAW" which is a south America QNote+ but seems to be the same phone on the inside. Also tried "LMQ710FA" a south America Q Stylus Plus seems to be same on the inside. both have the MT6750S
I have gotten it to pretend it dumps the phone. It goes through the motions but open any of the files in hxd and they are either full of 00 00 00 00 or have what looks like GPT repeated info in it. I have not been following LG much and this is just for fun for me. I tried to use the Lg download mode tools in python but cannot seem to get a connection I am guessing since they came out in 2016 LG has switched up their protocol. Seems they encrypted the DLL's as well.
I have tried LG Bridge, LG Mobile Support Tool. The logs show the IMEI check fails. I assume it means it is a sprint/boost phone as I know the IMEI is not blacklisted or stolen. But more of they realize it is a boost/sprint unit and block it. I tried every trick I could find I get as far as it says "downloading software" but it just hangs. I am going to try fresh installs after while just to rule it out. I would like to find out if anyone has used any LG tools to do a firmware update or firmware error recovery on a Sprint or Boost phone that is within 6 months old.
The story I heard is Sprint thinks their OTA updates should fix everything there is no reason to release firmware. I sure hope T-Mobile is buying Sprint. It seems is trying very hard to drive down there sell price... I talked to LG, of course, they cannot do anything until one of there techs puts hands on it. I am thinking of just trading it in it is only 4 months old. I just hate to give up or fail. But there is some type of issue with them I highly doubt the person above and myself are the only ones that have had this issue. I know there is at least 1 more person seen them on Lg forums.
If I make any headway or happen across a fix I will update within this thread.
Click to expand...
Click to collapse
thank a lot for the update.

Cross firmware
same problem

Cross firmware success
I croossed firmware with several q stylo Alpha , the problem id no baseband, wifi dont work, using lgup modded 1.14 option partición dll

djcal1985 said:
I croossed firmware with several q stylo Alpha , the problem id no baseband, wifi dont work, using lgup modded 1.14 option partición dll
Click to expand...
Click to collapse
Update
working 2G and H+ an data,
no working
3g,LTE
WIFI and bluetooth
need help for edit nvdata, dont know parameters for lte

the solution you have to get dump system from lgup DUMP option and edit like system.img and flash on la option -partition dl

djcal1985 said:
I Cross firmware with lgup modded but you Lost baseband , wifi and bluetooth nota working
Click to expand...
Click to collapse
I tried to , but it give me some kind of error like 0X.... succes cmd sign

the phone q710al q710pl got root, please upload backup from system please

bump
does any one fixed no data/4g/Lte issue ? i have phone with no data / apn issues.

djcal1985 said:
I croossed firmware with several q stylo Alpha , the problem id no baseband, wifi dont work, using lgup modded 1.14 option partición dll
Click to expand...
Click to collapse
i try to crossed firmware on my q710al with q710hs Q stylo Alpha ... but now my phone turn on/off .
no firmware for Q710al to fix this ... can anyone suggest me Q710Hs firmware which fix this issue ?

I can get y'all the dump file but I need a patched version of LGUP DEV to do it. All other versions give a timed out error.

Jackspsychosis said:
I can get y'all the dump file but I need a patched version of LGUP DEV to do it. All other versions give a timed out error.
Click to expand...
Click to collapse
hi! i found this on hovatek. pls do try it

waayo69 said:
hi! i found this on hovatek. pls do try it
Click to expand...
Click to collapse
Right on. I try here in a bit. Since my post I've been trying patch LGUP myself. The only is that lack knowledge or brain cells. Its difficult to say the least. The eggheads that know how to do it are not very forthcoming.

Related

Why did restore via TOT wipe my IMEI?

It appears a lot of people have had this issue where the imei is wiped after flashing back via the TOT method. Not sure about KDZ method, but I wanted to use the TOT method since it's apparently a valid release, so it can take any of the OTAs as they come.
How come this is never identified in the instructions? I would think that would be a very important piece of information. Just curious.
I never backed it up. I do have the original IMEI number from the box, the receipt plus on the barcode sticker in the battery compartment.
I guess I'll have to see how to do it manually, but I'm just curious, why isn't this a warning that something like this could happen? Or, is it because I did something wrong? I know on the first try, in the LG Flash Tool, the instructions in the Verizon forums didn't state to switch from Upgrade DL to Board DL. If I do Upgrade DL, I get the big red 2 instead of the big red 3, so I searched and saw instructions saying to go to BOARD DL instead. That seemed to fix it, but now my IMEI is all messed up with zeroes.
Any ideas as to what else I might have done that could have done this? I've flashed back to 10b twice now.
Thanks!
iBolski said:
It appears a lot of people have had this issue where the imei is wiped after flashing back via the TOT method. Not sure about KDZ method, but I wanted to use the TOT method since it's apparently a valid release, so it can take any of the OTAs as they come.
How come this is never identified in the instructions? I would think that would be a very important piece of information. Just curious.
I never backed it up. I do have the original IMEI number from the box, the receipt plus on the barcode sticker in the battery compartment.
I guess I'll have to see how to do it manually, but I'm just curious, why isn't this a warning that something like this could happen? Or, is it because I did something wrong? I know on the first try, in the LG Flash Tool, the instructions in the Verizon forums didn't state to switch from Upgrade DL to Board DL. If I do Upgrade DL, I get the big red 2 instead of the big red 3, so I searched and saw instructions saying to go to BOARD DL instead. That seemed to fix it, but now my IMEI is all messed up with zeroes.
Any ideas as to what else I might have done that could have done this? I've flashed back to 10b twice now.
Thanks!
Click to expand...
Click to collapse
I don't know why it happened during your restore, but there is a G2 IMEI restore method if you'd be willing to try it on your G3: http://www.droidviews.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
It looks like a QPST tool and an IMEI converter zip file, but nothing says "LG G2" anywhere so it may work for the G3. But I've never used it though, so if you're up for a gamble...good luck
I don't envy your situation I hope you get it fixed up and if you do please fill us in how you did it. I doubt you'll be the only one this happens to.
startswithPendswithOOH said:
I don't know why it happened during your restore, but there is a G2 IMEI restore method if you'd be willing to try it on your G3: http://www.droidviews.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
It looks like a QPST tool and an IMEI converter zip file, but nothing says "LG G2" anywhere so it may work for the G3. But I've never used it though, so if you're up for a gamble...good luck
I don't envy your situation I hope you get it fixed up and if you do please fill us in how you did it. I doubt you'll be the only one this happens to.
Click to expand...
Click to collapse
UPDATE:
First off, if you EVER lose your IMEI number, then you MUST flash back to 10B. Reason being is, anything later than 10B no longer gives you access to Modem mode which is the only way I've been able to make this work.
Recently, I was TOT flashing 10b to my phone to downgrade it from MM so I could flash a custom ROM. Once again, the IMEI got lost. But I found that QPST wasn't working anymore! I even KDZ flashed back to 48A and still, QPST wouldn't work. I tried 35B, nothing. I then went back to 10B. I don't know HOW many times I did this yesterday, but my phone was out of commission all day.
Finally, this afternoon, I found this article that I wrote up and read, and re-read what I posted below and it was step 2 that stood out to me. I noticed I couldn't find Modem mode anywhere as it was listed. But, because I saw that I flashed to 10B, I decided to try it once more. So, I TOT flashed back to 10b. I still couldn't find modem mode. Then it dawned on me. I selected "Internet Connect" and viola! There it was! Once I had that, QPST worked again and I was able reprogram my IMEI.
So, if you happen to flash anything, whether it's 10b or later, and you find that your IMEI is gone, you must flash back to 10b. QPST will not work on anything later (at least, 47/48A for sure). I've also tried 35B and it won't work. You MUST have 10b so that you can select modem mode. I was unable to get it to work on any other version.
I was able to find my IMEI on my receipt which is stored in my MyVerizon documents section of my account. But, it's also located on the label in the battery compartment, so if you no longer have your box or receipt, open up the G3 and remove the battery and you'll see the IMEI number on the sticker there.
I skipped the entire portion of the Backup and Restore EFS on LG G2 section. No reason for that since I wiped the IMEI for some reason during the restore.
Next, I followed the steps in the Restore Lost IMEI on LG G2 section as follows:
Here are the files to download:
LG USB drivers
IMEI-Converter.zip [mirror link]
QPST_2.7_378.zip
After downloading all the files (IMEI-Converter and QPST_2.7_378.zip. Didn't install drivers as I already had them) and installing the QPST tools, I followed the directions. I didn't attempt to backup the IMEI since it's gone.
First, I put my phone into debugging mode and switched it to modem mode (on 10b). To do this, you need to ensure your phone is connected. Go to the notifications area and select "USB Connected". From there, select "Internet connect" and then select "Modem". You must do this or QPST will not work.
Connected device to PC and ran QPST configuration and added the new port. Mine was already on port 41 due to the TOT restore, so Ieft it at that.
Skipped all the steps on backing up. I would do this AFTER I restored the IMEI.
Ran the C:\Program Files (x86)\qualcomm\qst\bin\RF_NV_Manager.exe program.
Went to Setting->Comport and set it to 41.
Clicked on File->Read from phone and navigated down to the 550 line which showed the IMEI was blank, which we already know is true.
Clicked on File->Read supported RF NV items.
Ran the IMEI Converter.exe (after extracting it) and typed in my IMEI number for my phone. This converts it into 9 groups of hexadecimal numbers.
In the RV_NV_Manager program, selected the 550 line and put a check mark in the hex check box.
Taking each hex value from the converter program, I entered the numbers into the 9 text boxes. The left-most set went in the first text box, and so on.
Clicked the "Write NV" button to write the values back to the phone.
Clicked File->Read from phone and verified that item number 550 contained my correct IMEI number.
Disconnected the phone from the USB cabled, rebooted and all was golden. Verified on my MyVerizon page that my phone was no longer an unsupported device anymore.
iBolski said:
Thanks for the link. That was actually what I found and used. LOL!
In any case, it DOES work. I was able to fix it. Basically...
Cool. Good info to know. And congrats
Click to expand...
Click to collapse
I have the same problem of vanished imei. I was trying to write the IMEI using RF NV Manager but when I click write I get error NvManager :write to phone- unable to write NV_UE_IMEI_I to phone(parameter is write protected and thus read only).
Somebody please help to bring my phone alive.
---------- Post added at 10:47 PM ---------- Previous post was at 10:16 PM ----------
Well setting the phone USB connection mode to ethernet solved the problem .
Settings>storage>usb pc connection>internet connection>ethernet. Need to be in the 10B version to be able to do this.
iBolski said:
Thanks for the link. That was actually what I found and used. LOL!
In any case, it DOES work. I was able to fix it. Basically, I was able to find my IMEI on my receipt which is stored in my MyVerizon documents section of my account. But, it's also located on the label in the battery compartment, so if you no longer have your box or receipt, open up the G3 and remove the battery and you'll see the IMEI number on the sticker there.
Basically, I skipped the entire portion of the Backup and Restore EFS on LG G2 section. No reason for that since I wiped the IMEI for some reason during the restore.
Next, I followed the steps in the Restore Lost IMEI on LG G2 section as follows:
After downloading all the files (IMEI-Converter and QPST_2.7_378.zip. Didn't install drivers as I already had them) and installing the QPST tools, I followed the directions. I didn't attempt to backup the IMEI since it's gone.
First, I put my phone into debugging mode and switched it to modem mode (on 10b)
Connected device to PC and ran QPST configuration and added the new port. Mine was already on port 41 due to the TOT restore, so Ieft it at that.
Skipped all the steps on backing up. I would do this AFTER I restored the IMEI.
Ran the C:\Program Files (x86)\qualcomm\qst\bin\RF_NV_Manager.exe program.
Went to Setting->Comport and set it to 41.
Clicked on File->Read from phone and navigated down to the 550 line which showed the IMEI was blank, which we already know is true.
Clicked on File->Read supported RF NV items.
Ran the IMEI Converter.exe (after extracting it) and typed in my IMEI number for my phone. This converts it into 9 groups of hexadecimal numbers.
In the RV_NV_Manager program, selected the 550 line and put a check mark in the hex check box.
Taking each hex value from the converter program, I entered the numbers into the 9 text boxes. The left-most set went in the first text box, and so on.
Clicked the "Write NV" button to write the values back to the phone.
Clicked File->Read from phone and verified that item number 550 contained my correct IMEI number.
Disconnected the phone from the USB cabled, rebooted and all was golden. Verified on my MyVerizon page that my phone was no longer an unsupported device anymore.
Click to expand...
Click to collapse
Thnks so much i mean so much, my imei is erased after using the LGFlashtool and imagined the worst, even i think sell it in parts, but I followed your instructions and my IMEI is back in my cell. Now my question is, did he do that was erased, now I'm in stock room 10b and want to put Lollipop, but after this experience and it scares me. at all, especially if I'm in another country and I can not take it to be repaired so easily with Verizon.
Anyway, thnks again works for me into Verizon Wirless Vs985 from México
My English was sponsored by Google translator
Siylar said:
Thnks so much i mean so much, my imei is erased after using the LGFlashtool and imagined the worst, even i think sell it in parts, but I followed your instructions and my IMEI is back in my cell. Now my question is, did he do that was erased, now I'm in stock room 10b and want to put Lollipop, but after this experience and it scares me. at all, especially if I'm in another country and I can not take it to be repaired so easily with Verizon.
Anyway, thnks again works for me into Verizon Wirless Vs985 from México
My English was sponsored by Google translator
Click to expand...
Click to collapse
If you are not rooted yet, then you can take the OTAs all the way to LP. If you do root, you can only get to 12b. You won't be able to go to LP, so you would have to flash back to 10b again. There is a 12b KDZ somewhere that will also allow you to upgrade to LP if you want to go that route. The only thing that has me a little worried about it (and it's probably nothing) is that when you flash back to 12b stock via KDZ, it states the software is modified, but it still will take the LP OTA, so go figure! LOL!
As for the IMEI being wiped again, that shouldn't happen if you are taking the official OTAs. For me, when I did the TOT flash back to 10b, that was the first time I did it and who knows what I did. I probably did something wrong because the second time I flashed back to 10b (so I could upgrade to the official LP OTA), my IMEI wasn't wipe, so I have to think I did something wrong the first time.
In any case, taking the official OTAs should not wipe your IMEI so you should be good to go.
Worse comes to worse, if it does get wiped, just do the steps outlined above and you'll be back in business.
So I had a replacement phone sent to me and this phones ieme is wiped due to a similar experience to yours. My question is, do I HAVE to use the ieme that came with my phone? Or can I use the one that is on my replacement phone right now?
swimmerhair said:
So I had a replacement phone sent to me and this phones ieme is wiped due to a similar experience to yours. My question is, do I HAVE to use the ieme that came with my phone? Or can I use the one that is on my replacement phone right now?
Click to expand...
Click to collapse
You could use either imei as long as they are both for the same model of phone. I have 2 LG G2s. The imei on one got swapped to an imei for some other model. It sort of worked but I kept getting mobile network disconnections (on straight talk). I couldn't update software because the imei wasn't an LG G2. I didn't have a record of my imei for that phone, so I used the imei of my other Lg g2 which was inop with a cracked screen. Once I put a valid lg g2 imei on it everything worked correctly again and I could update software. Still on straight talk with no more network problems.
Awesome! I have been dealing with Big Red for a week now because their Fraud Prevention is meddling in my business. This will make things a little easier in the meantime. Thanks again! I will post and let everyone know how it goes.
Sorry for reviving an old thread but if I tot back to 10b from the xdabbeb version of 35B, will that be the way to go about it? Am I at a risk of hard brick?
nagi_007pk said:
Sorry for reviving an old thread but if I tot back to 10b from the xdabbeb version of 35B, will that be the way to go about it? Am I at a risk of hard brick?
Click to expand...
Click to collapse
Yes to the first question, and every time we do something with our phone that LG and Verizon don't intend for us to do with our phone we risk either soft or hard bricking.
iBolski said:
Thanks for the link. That was actually what I found and used. LOL!
In any case, it DOES work. I was able to fix it. Basically, I was able to find my IMEI on my receipt which is stored in my MyVerizon documents section of my account. But, it's also located on the label in the battery compartment, so if you no longer have your box or receipt, open up the G3 and remove the battery and you'll see the IMEI number on the sticker there.
Basically, I skipped the entire portion of the Backup and Restore EFS on LG G2 section. No reason for that since I wiped the IMEI for some reason during the restore.
Next, I followed the steps in the Restore Lost IMEI on LG G2 section as follows:
Here are the files to download:
After downloading all the files (IMEI-Converter and QPST_2.7_378.zip. Didn't install drivers as I already had them) and installing the QPST tools, I followed the directions. I didn't attempt to backup the IMEI since it's gone.
First, I put my phone into debugging mode and switched it to modem mode (on 10b)
Connected device to PC and ran QPST configuration and added the new port. Mine was already on port 41 due to the TOT restore, so Ieft it at that.
Skipped all the steps on backing up. I would do this AFTER I restored the IMEI.
Ran the C:\Program Files (x86)\qualcomm\qst\bin\RF_NV_Manager.exe program.
Went to Setting->Comport and set it to 41.
Clicked on File->Read from phone and navigated down to the 550 line which showed the IMEI was blank, which we already know is true.
Clicked on File->Read supported RF NV items.
Ran the IMEI Converter.exe (after extracting it) and typed in my IMEI number for my phone. This converts it into 9 groups of hexadecimal numbers.
In the RV_NV_Manager program, selected the 550 line and put a check mark in the hex check box.
Taking each hex value from the converter program, I entered the numbers into the 9 text boxes. The left-most set went in the first text box, and so on.
Clicked the "Write NV" button to write the values back to the phone.
Clicked File->Read from phone and verified that item number 550 contained my correct IMEI number.
Disconnected the phone from the USB cabled, rebooted and all was golden. Verified on my MyVerizon page that my phone was no longer an unsupported device anymore.
Click to expand...
Click to collapse
So I tried the steps inside of here. There was issues with it reading my phone. I am in the process of getting back to 10b so that I can try from there but I am not sure that will help. PM me for screen shots cause I can't attach yet. hxxp://tinypic.com/r/2j5o20o/9 hxxp://tinypic.com/r/2ivz7up/9 hxxp://tinypic.com/r/29ngqoy/9
Darkblaze1 said:
So I tried the steps inside of here. There was issues with it reading my phone. I am in the process of getting back to 10b so that I can try from there but I am not sure that will help. PM me for screen shots cause I can't attach yet. hxxp://tinypic.com/r/2j5o20o/9 hxxp://tinypic.com/r/2ivz7up/9 hxxp://tinypic.com/r/29ngqoy/9
Click to expand...
Click to collapse
So I solved my own issue. Didn't mean to revive an old thread. I am doing kdz to 5.1 then the upgrade to 35b for stock. (Needing to keep stock for work reasons and for Airwatch Agent (unless anyone knows how to make it work on AOSP))
thank u ................................................)(
Darkblaze1 said:
So I solved my own issue. Didn't mean to revive an old thread. I am doing kdz to 5.1 then the upgrade to 35b for stock. (Needing to keep stock for work reasons and for Airwatch Agent (unless anyone knows how to make it work on AOSP))
Click to expand...
Click to collapse
While you're on 10b, root, install twrp, and backup your efs. This will make it painless to restore your imei should you lose it again. I wish I did this the first time.
I realize that this is an old thread but I am hoping that someone can help. I went back to 10b and, in doing so, I lost my imei. I have tried to follow the steps in this guide but I keep getting an error in step 7 when I try to read from the phone in RF NV Manager.
NvManager::getNvItemsFromPHone (const String comPort) - QpstServer::sendSyncImpl - Bad response from phone (DM Packet commants 19 - 24)
If I skip step 7, I can do all the steps until 12. When I try to write to the phone, I get the following error message.
NvManager:::writeToPhone( const string comPort) - QpstServer:::initialize - Unable to attach to the QPST server.
Any help would be greatly appreciated.
hamillp said:
I realize that this is an old thread but I am hoping that someone can help. I went back to 10b and, in doing so, I lost my imei. I have tried to follow the steps in this guide but I keep getting an error in step 7 when I try to read from the phone in RF NV Manager.
NvManager::getNvItemsFromPHone (const String comPort) - QpstServer::sendSyncImpl - Bad response from phone (DM Packet commants 19 - 24)
If I skip step 7, I can do all the steps until 12. When I try to write to the phone, I get the following error message.
NvManager:::writeToPhone( const string comPort) - QpstServer:::initialize - Unable to attach to the QPST server.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Make sure you are back to 10b. You cannot use the tool to fix your IMEI after 10b. It won't find the phone. I wiped my IMEI a few months ago and followed my own directions (since I'm the one that posted this lol) and completely forgot that you had to do it in 10b. I wiped my IMEI, flashed back to 47A and attempted to fix my IMEI that way. Nope. Won't work. The tool requires you to be on 10b in order to be found.
If you are on 10b, make sure you select the correct port. It SHOULD be 41 since that's what was last used when you flashed the 10B tot. Remember, you must also be booted into your phone, not in download mode. Once you hook the phone up, be sure you've selected the correct mode. My G3 has died since then so I can't remember it off the top of my head, but it SHOULD be in here explaining how to get to that mode. I think it's Modem mode.
Then hook up the phone and the software should find it and allow you to fix your IMEI number.
iBolski said:
Make sure you are back to 10b. You cannot use the tool to fix your IMEI after 10b. It won't find the phone. I wiped my IMEI a few months ago and followed my own directions (since I'm the one that posted this lol) and completely forgot that you had to do it in 10b. I wiped my IMEI, flashed back to 47A and attempted to fix my IMEI that way. Nope. Won't work. The tool requires you to be on 10b in order to be found.
If you are on 10b, make sure you select the correct port. It SHOULD be 41 since that's what was last used when you flashed the 10B tot. Remember, you must also be booted into your phone, not in download mode. Once you hook the phone up, be sure you've selected the correct mode. My G3 has died since then so I can't remember it off the top of my head, but it SHOULD be in here explaining how to get to that mode. I think it's Modem mode.
Then hook up the phone and the software should find it and allow you to fix your IMEI number.
Click to expand...
Click to collapse
Thanks for the reply. Yes, I am on 10b. I did use port 41. I was in modem mode. I even tried to do it in ethernet mode as well but that didn't work. It shows an unknown phone connected in the QPST configuration tool. It shows com 41 and that it is enabled. Everytime I get to a step where it has to interact with the phone, however, I get an error.
Anyone know what this error means:
NvManager::getNvItemsFromPHone (const String comPort) - QpstServer::sendSyncImpl - Bad response from phone (DM Packet commants 19 - 24)
More importantly, anyone know how to fix it?

I cannot boot into fastboot (or recovery)

Hello, I have a LG G5 RS988. I've been fiddling with custom ROMs a bit trying to get the signal to be stable on AT&T. I had finally given up and was going to just try it stock rooted. I don't remember what order i took these actions, but the end result is that i cannot boot into fastboot mode or recovery mode (TWRP was installed but is now gone).
I believe my first attempt was to wipe -> flash [LG-RS98811d-Flashable.COMPLETE-ARB01]
I think this is where i encountered the bootloops and quit messing with it for a day or so. When i came back to it, i've tried literally everything i can find to do to get it back to stock.
I have used LGUP with the uppercut 1.0.0.0 file to 'upgrade' it back to RS98811c_00_ARB01.kdz or any other .kdz i could find. While i had it in fastboot i had attempted to flash some things, but it eventually wouldn't boot so i set it into download mode. Now i can boot into android 6.XX but i have no access to the fastboot screen. It just shows the battery charging percentage...
Please help.
I've already mentioned this in another thread, but you will have to send this in for repair. Flashing lower KDZ versions even with the same ARB version can hard brick your device. It can be repaired through the 'firehose' method that needs non-free proprietary firehose file, partition xml, and stock mbm/bin images. Or through the JTAG box method which is what I do. This model RS988 is the hardest to repair because it is uncommon unlike the other variants. You won't be able to fix it another way otherwise. Also AT&T blocks LTE access to non AT&T devices especially generic unlocked versions from Huawei, OnePlus, Google, and Xiaomi. Even if you do connect, you'll fall back to 3G/HSPA/HSDPA/HSPA+ when calling or temporary LTE loss, but can reset the radio by toggling airplane mode. If you check your IMEI through them it will show up as generic and you won't get LTE access through their whitelist. You could try to call them and explain this issue, and do insist, you should end up with a higherup tech support person that can add your phone to their list. I haven't tried this since I'm on TracFone an MVNO, so I doubt this will work, but it has for others. This LTE issue also happens for Verizon users, as they only like white-listed phones to use their network.
patato21 said:
I've already mentioned this in another thread, but you will have to send this in for repair. Flashing lower KDZ versions even with the same ARB version can hard brick your device. It can be repaired through the 'firehose' method that needs non-free proprietary firehose file, partition xml, and stock mbm/bin images. Or through the JTAG box method which is what I do. This model RS988 is the hardest to repair because it is uncommon unlike the other variants. You won't be able to fix it another way otherwise. Also AT&T blocks LTE access to non AT&T devices especially generic unlocked versions from Huawei, OnePlus, Google, and Xiaomi. Even if you do connect, you'll fall back to 3G/HSPA/HSDPA/HSPA+ when calling or temporary LTE loss, but can reset the radio by toggling airplane mode. If you check your IMEI through them it will show up as generic and you won't get LTE access through their whitelist. You could try to call them and explain this issue, and do insist, you should end up with a higherup tech support person that can add your phone to their list. I haven't tried this since I'm on TracFone an MVNO, so I doubt this will work, but it has for others. This LTE issue also happens for Verizon users, as they only like white-listed phones to use their network.
Click to expand...
Click to collapse
Send it in to whom? Do you know what the cost to expect?
Random_Khaos said:
Send it in to whom? Do you know what the cost to expect?
Click to expand...
Click to collapse
You could expect to pay around $50-70, but do read my dm. Don't purchase remote PC repair methods. They could install malware on your computer, and the USB client redirector may not work for a hard bricked phone.

Two G5s, one has OTA updated to Oreo, the other hasn't

I'm puzzled ...
I have two G5s (the wife uses one), both are UK, carrier-free, and seem to be identical. One has OTA updated to Oreo, the other hasn't and shows no inclination to do so. There is one difference though, they run/ran slightly different versions of Nougat:
The one that updated was previously running v20v-EUR-XX. The one that won't runs v20r-234-10. I don't know what that build is. It has previously received incremental updates to Nougat with no problem. Is it somehow an invalid region to receive an Oreo update?
Both phones were bought used, so I don't know their exact history.
If it's not going to update OTA then I will try flashing the update. TBH there's almost too much information here about flashing ROMs - I'd like to know the simplest way to flash a stock ROM, I don't want a rooted phone (been there, done that, fun, but banking apps etc. I depend on won't run). My desktop & laptop run Linux, so Windows-based tools won't help (unless they'll run under Wine ).
TIA to anyone who can help me out here.
LG H850 Oreo Update
ONLY LG H850(GBR) and H850 (VDF) received the Oreo Update.
Thanks, so what region is 234-10? Doesn't seem to correspond to any listed ROMs.
Any pointers to the best simple no-frills flash guide?
Looks like yours have branding, check which operator folder you got in "cust" folder.
Thanks for the hint.
The cust folder contains stuff on all UK operators. I don't entirely understand how this info works, but in op_list.cfg is the line 23410,O2=/OP/TLF_COM, which I guess means it was originally O2 branded. There's no trace of anything O2 on it now, but it would have originally shipped with AOS 6, and had already received 7 when I got it. That upgrade probably dropped anything specific to O2.
Is there any way to hack this so it appears to be running generic EUR software, or do I have to manually flash it to get 8?
Thks
There is GB euro open version but when I tried on my EE g5 it install french orange "jeus" app plus crap from Vodafone Romania, on the top of that you will get pop up error every time you restart your mobile about wrong customisation or something like that , other than that I loved oreo. Because of above I revert back to original ee software and just checking for update. G5 is not my primary phone so I don't have pressure about. EE was always slow on updates so this is normal in that case,not sure about other UK operators.
The EUR-XX build runs OK on my other G5, it updated OTA. This phone with O2 region code is not on O2 any more - I don't think it was ever carrier locked, but must have been bought from O2 originally. So even if O2 builds do update OTA, presumably it will only happen if they've got O2 SIMs in - I don't really follow how all this stuff works!
How did you install the ROM you tried out? I'm still trying to understand what the various tools being touted actually do.
I have the same problem.
I have an H850 with an unlocked bootloader and rooted.
There is no OTA update.
When I check on https://imei.guru/ I get:
Model: LGABCD
Region: ABC
When I check on https://proimei.info/en/checker/lg I get:
SUFFIX AO2UTN
BUYER O2U
BUYERNAME O2
I can try LG Bridge but I don't want to cause any issues since I'm rooted and the bootloader is unlocked.
Do I ned to use LG UP instead? And will I lose my data?
Any suggestions very welcome.
Thanks
As you're already unlocked and rooted, it should be a simple matter to flash a new system ROM. AFAIK you won't have to lose data. It's when you unlock the boot loader that it wipes all data.
In my case I don't have root, and I don't want a rooted phone after an upgrade. I'd prefer not to have to wipe and restore if possible too, but I can't work out how to do that.
I downloaded kdz and flashed with lg up, you can try if you really want oreo before O2 release. In worse case you can wait, and it doesn't matter what sim is in the mobile, when update is ready you will receive notification, I got different sim in my old g5 and previous updates was downloaded and installed without any problems.
Ah, thanks for that, maybe I'll just wait for O2 to get their act together! I can't use LGUP as I don't run any Windows machines, I'm all Linux. The closest I can get is XP running in a VM, but even though I can map a USB port into the VM it still doesn't recognize either of my devices. Uppercut doesn't help either .
konio25 said:
I downloaded kdz and flashed with lg up, you can try if you really want oreo before O2 release. In worse case you can wait, and it doesn't matter what sim is in the mobile, when update is ready you will receive notification, I got different sim in my old g5 and previous updates was downloaded and installed without any problems.
Click to expand...
Click to collapse
Which LG UP did you use?
Because this thread recommends not using LG UP and using UPPERCUT instead.
However, VirusTotal shows lots of issues:
https://www.virustotal.com/#/file/d...366b6643a5922cd3b09a3b1a9296b8c0a8f/detection
and so I would prefer to use LG UP instead, if it's compatible with H850.
Thanks
I can't remember exactly which LGUP I used, I tried a couple. A bit worrying about the virus reports in uppercut, one advantage of running in a VM, I can always just trash the image and go back to the previous state.
As I understand uppercut, it doesn't replace LGUP, just tries to fix some device detection issues then launches LGUP to do the actual update. But that still didn't work
No Expert said:
Which LG UP did you use?
Because this thread recommends not using LG UP and using UPPERCUT instead.
However, VirusTotal shows lots of issues:
https://www.virustotal.com/#/file/d...366b6643a5922cd3b09a3b1a9296b8c0a8f/detection
and so I would prefer to use LG UP instead, if it's compatible with H850.
Thanks
Click to expand...
Click to collapse
Hi,
I used version 1.14.3 (apparently this is the latest).
I flashed my g5 H850 several times as I wasn't sure if this bloatware from VDF Romania and french operator Jeux wasn't a issue of incorrect files. After all exercises i back to original EE soft.
All that with LG UP. I tried to use uppercut but my antivirus report as well on this so I don't bother and just use LG up.
konio25 said:
Hi,
I used version 1.14.3 (apparently this is the latest).
I flashed my g5 H850 several times as I wasn't sure if this bloatware from VDF Romania and french operator Jeux wasn't a issue of incorrect files. After all exercises i back to original EE soft.
All that with LG UP. I tried to use uppercut but my antivirus report as well on this so I don't bother and just use LG up.
Click to expand...
Click to collapse
Thank you.
Did you use the LG UP from here: https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
Because I that's the version I used but unfortunately on my PC it cannot detect my phone.
I'm not sure from where I downloaded, when I was looking for latest version I just search through google. Are you sure you have all drivers installed? Did you plug in your phone in download mode?
konio25 said:
Did you plug in your phone in download mode?
Click to expand...
Click to collapse
Ah - helpful tip! Because of the other messing around I'd been doing, it was in debug mode, D'oh I've got further, but still baulking.
From other threads re. XP and VMs, I found I needed to install an XP USB 3 driver, and switch to a USB virtual port in the VM. With all that, launching LGUP 1.14 via Uppercut the phone is detected and I can start an upgrade process.
It reboots the phone, which then displays the Firmware Update screen, but stays resolutely on 0%. LGUP shows "Build : U" as the step with progress at 4%. After 11 minutes it times out with a popup saying "Error: 0x2000 [ERROR] RX Timeout : 3.0". The barely readable little console window on the phone starts off with some info about the phone, then changes to simply "633E 1B00" after a couple of minutes.
I've tried using both physical USB 2 & USB 3 ports on the PC.
Any ideas?
Thks
Try to use lg up without uppercut, maybe your pc is a bit slow on vm. Once i startet flashing with lg up the whole process take about 5 min. Do you have hdd or ssd on your pc? Also check if there is no restriction for vm regarding size, make sure drive space is big enough. Also try to assign at least 2gb of ram for vm and if you have multi core cpu try to assign at least two cores. I believe if you will tweak settings on your vm it should be good to go. Check for vm tools update if needed update to latest.
LGUP without Uppercut doesn't work, it won't recognise the device. That's the only reason I downloaded Uppercut to start with.
I'm pretty convinced it's a USB connectivity problem. When the phone reboots there's no USB, then the USB interface comes up again, and LGUP has to continue talking to it in firmware-update mode. There are issues with the way the USB device is being captured by the VM. For some reason the MTP interface is still exposed to the host even though VBox says it's captured by the guest. In VBox terms this shouldn't happen, an interface is either accessible to the host, or is mapped to the guest and invisible to the host.
MTP is a bit of a weird beast though, and I think there's some black magic going on with the way this Linux (Ubuntu 18.04) is grabbing MTP devices. I've been trying to turn off every rule relating to Vendor 1004, Device 633e, as well as defaults, but it still has some magic default that means it spots an MTP device. I'm sure this is blocking proper communication through to the XP guest OS.
I shall keep tinkering ...
Well, I got it to work! I could not stop the host from seeing the USB interface, no mater how much of MTP I disabled, but the solution was to disconnect and re-connect the USB device to the VM, after the phone rebooted into flashing mode and LGUP was waiting to re-connect. I did it a couple of times, second time the connection to LGUP succeeded, and flashing completed in 3 - 4 mins.
Well that's it done on my spare slightly-broken test phone - I collect these things! - (took it from AOS 6 to 8), now to take a deep breath and do it on my real device I depend on. Time to back everything up again

LG V10 H90121j bricked after update through LGUP. Never reboot after 100% update!

LG V10 H90121j bricked after update which was successfully completed but phone does not turned on after that. I manage to unbrick through H90020w qfil and get access to update firmware screen. Now again every H901 kdz updated 100% but phone again bricks and not turning on. Please help me to restore my phone. I think I should unbrick with H901 qfil instead of H90020w. Please support.
Shan1122 said:
LG V10 H90121j bricked after update which was successfully completed but phone does not turned on after that. I manage to unbrick through H90020w qfil and get access to update firmware screen. Now again every H901 kdz updated 100% but phone again bricks and not turning on. Please help me to restore my phone. I think I should unbrick with H901 qfil instead of H90020w. Please support.
Click to expand...
Click to collapse
Dear shan, sould have read these forums before updating, I had the same misfortune when i updated my v10 through LG bridge, chances are you have a refurbished phone like me, where the motherboard is of a different version/country/carrier than the software, I have a korean f600l which i came to know after bricking my phone, the only ,method to revive it is to use the h90020w method but it will convert your tmobile to AT&t with fingerprint , vpn issues, unable to uninstall apps and in extreme cases like mine no radio, but atleast it works that fine for me, but if you want to make calls then dont go for it, first identify your board then ask for help from other senior members ,or others who have the same model . andn please do update if you are successful so that others may benefit from your method.
last gspian said:
Dear shan, sould have read these forums before updating, I had the same misfortune when i updated my v10 through LG bridge, chances are you have a refurbished phone like me, where the motherboard is of a different version/country/carrier than the software, I have a korean f600l which i came to know after bricking my phone, the only ,method to revive it is to use the h90020w method but it will convert your tmobile to AT&t with fingerprint , vpn issues, unable to uninstall apps and in extreme cases like mine no radio, but atleast it works that fine for me, but if you want to make calls then dont go for it, first identify your board then ask for help from other senior members ,or others who have the same model . andn please do update if you are successful so that others may benefit from your method.
Click to expand...
Click to collapse
hey, sorry for late reply. Thank you for your answer. I got solution but as you said, with no Radio, I cannot make calls. my imei shows only 0-17. I think my imei totally erased. my methode was to debrick with file H90021w and then flash with H90021w.dz file. I convert kdz file to dz file by using LG_Firmware_Extract_v1.2.6.1. these files are available on internet. I got my phone back to life but without network. Phone is booting with AT&T logo and working fine other then network issue.
can anyone help me with network issue now?

Enabling Carrier Aggregation LG V60

Hi,
Can someone post the carrier policy files of the LG V60 LMV600EA version ?
I need this files to enable carrier aggregation on my canadian V60.
Thanks
leptdre said:
Hi,
Can someone post the carrier policy files of the LG V60 LMV600EA version ?
I need this files to enable carrier aggregation on my canadian V60.
Thanks
Click to expand...
Click to collapse
I would like to help you but i have no idea where to find that file. i have the european v60.
[email protected] said:
I would like to help you but i have no idea where to find that file. i have the european v60.
Click to expand...
Click to collapse
Thank you so much for offering your help.
Actually, it is not a difficult process to extract that file.
First thing needed is to install QPST and enable the phone serial port.
After that, you need to open a program called EFS Explorer and then extract the files.
You can find a video that explains the process here
LG-V60 - Google Drive
drive.google.com
leptdre said:
Thank you so much for offering your help.
Actually, it is not a difficult process to extract that file.
First thing needed is to install QPST and enable the phone serial port.
After that, you need to open a program called EFS Explorer and then extract the files.
You can find a video that explains the process here
LG-V60 - Google Drive
drive.google.com
Click to expand...
Click to collapse
Done! hopefully it helps in your process!!
what was this for?
Hi, can you please chare your rfnv files as it is shown in this video ? https://drive.google.com/drive/folders/1YeDpBC-mxATynh7ue3nxKuC3uf6hFMKx
Thank you
[email protected] said:
Done! hopefully it helps in your process!!
Click to expand...
Click to collapse
Hi there would you be able to upload the files somewhere please? Or send them to me if possibe?
@leptdre , were you able to use the files to enable carrier aggregation? Would you be able to upload them somewhere?
Thanks
leptdre said:
Thank you so much for offering your help.
Actually, it is not a difficult process to extract that file.
First thing needed is to install QPST and enable the phone serial port.
After that, you need to open a program called EFS Explorer and then extract the files.
You can find a video that explains the process here
LG-V60 - Google Drive
drive.google.com
Click to expand...
Click to collapse
How are you enabling the V60 serial port. I'm having issues getting it to show up as diag
ebowen 747 said:
How are you enabling the V60 serial port. I'm having issues getting it to show up as diag
Click to expand...
Click to collapse
After installing the Qualcomm drivers, you will see LG Diagnostic Port, and LG Serial Port in device manager. Manually update/replace the serial port driver with Qualcomm HS-USB Diagnostics 9025. Then in the phone hidden menu you have to turn off the diag port under SVC, Port Check Test as shown in the video above. Then it should show up in QPST and EFS explorer
cheesyzombie said:
After installing the Qualcomm drivers, you will see LG Diagnostic Port, and LG Serial Port in device manager. Manually update/replace the serial port driver with Qualcomm HS-USB Diagnostics 9025. Then in the phone hidden menu you have to turn off the diag port under SVC, Port Check Test as shown in the video above. Then it should show up in QPST and EFS explorer
Click to expand...
Click to collapse
Is this with the device in regular boot or edl?
ebowen 747 said:
Is this with the device in regular boot or edl?
Click to expand...
Click to collapse
Regular
cheesyzombie said:
Regular
Click to expand...
Click to collapse
Thank you for your help
leptdre said:
Hi,
Can someone post the carrier policy files of the LG V60 LMV600EA version ?
I need this files to enable carrier aggregation on my canadian V60.
Thanks
Click to expand...
Click to collapse
I have all the carrier_policy.xml files, TM VM EA. But I have some questions first. In which country and what is the name of the Carrier? The only reason I'm asking is: As far as I know, nobody in the US has crossflashed (most have been crossflashing the lmv600am) and really been able to get a 5G signal. Yes, I know it may have the 5G moniker on the taskbar but using Netmonster tells a different story, as do other tools. It's 4g masquerading as 5g. For example, on the v50/v60 on tmob network, using b66 shows it's 5g when it really isn't. When you crossflash with a KDZ the efs partition is not overwritten nor should it be because it contains imei info. Any file (carrier_policy.xml as an example) in the efs to be change has to be DL from the efs partition using Qspt, edit, and then reloaded. Show are you really getting a 5g band on your phone??????
hooutoo said:
I have all the carrier_policy.xml files, TM VM EA. But I have some questions first. In which country and what is the name of the Carrier? The only reason I'm asking is: As far as I know, nobody in the US has crossflashed (most have been crossflashing the lmv600am) and really been able to get a 5G signal. Yes, I know it may have the 5G moniker on the taskbar but using Netmonster tells a different story, as do other tools. It's 4g masquerading as 5g. For example, on the v50/v60 on tmob network, using b66 shows it's 5g when it really isn't. When you crossflash with a KDZ the efs partition is not overwritten nor should it be because it contains imei info. Any file (carrier_policy.xml as an example) in the efs to be change has to be DL from the efs partition using Qspt, edit, and then reloaded. Show are you really getting a 5g band on your phone??????
Click to expand...
Click to collapse
I've been trying forever to get this to work with my ATT with stock FW and when crossflashed to EA, and you're right, I think it just doesn't, regardless of fw version installed. I've pulled the EA EFS policy files as well as the ATT ones, modified them, reuploaded and 5G just will not turn on. I've persisted so long because this method worked fine on my V50, however that one is a V500N (korean variant) whereas this is a V600AM (US/ATT variant), so I think that may have something to do with it. Have tried adding MCC-MNC, editing the rf_band lists, all sorts of combinations. I have a feeling that when the sim is inserted the phone doesn't even look at the modified xml files in the EFS partition and just generates it's own with the american models, but this is just speculation.
The other thing I noticed is that when I edit my ftm file to regain my serial number and remove the NT code error, the outer screen on the dual screen attachment works again, but then I lose 4G altogether and revert to 3G without data.
On my V50 all I had to do was add '5G' to some band lists and it worked, however, that unit is not crossflashed and still has stock korean firmware.
I'm in UK on Hutchison 3 network
cheesyzombie said:
I've been trying forever to get this to work with my ATT with stock FW and when crossflashed to EA, and you're right, I think it just doesn't, regardless of fw version installed. I've pulled the EA EFS policy files as well as the ATT ones, modified them, reuploaded and 5G just will not turn on. I've persisted so long because this method worked fine on my V50, however that one is a V500N (korean variant) whereas this is a V600AM (US/ATT variant), so I think that may have something to do with it. Have tried adding MCC-MNC, editing the rf_band lists, all sorts of combinations. I have a feeling that when the sim is inserted the phone doesn't even look at the modified xml files in the EFS partition and just generates it's own with the american models, but this is just speculation.
The other thing I noticed is that when I edit my ftm file to regain my serial number and remove the NT code error, the outer screen on the dual screen attachment works again, but then I lose 4G altogether and revert to 3G without data.
On my V50 all I had to do was add '5G' to some band lists and it worked, however, that unit is not crossflashed and still has stock korean firmware.
I'm in UK on Hutchison 3 network
Click to expand...
Click to collapse
Well I can tell you that there's a running discussion on a lot of the points you just made not the least of which is whether or not the modem is being provisioned at activation and if so what exactly and how much.
I have 2 lmv600am which I got off Ebay. Both had been crossed to EA fw when I got them. Since I'm on Google Fi, I went to the AT&T unlocking site and Sim unlocked. I then put my G-Fi sim into 1 of my v60 and sure enough I get a 5G moniker on my taskbar. Now during this time period Tmob is changing their policies on LG phones, mainly since LG is no longer in business. For example, lmv450 no longer actives on Tmob nor any of it's mvno's and I believe the same is happening for all Sprint phones plus all LG non-tmob phones. They're checking by imei.
So it didn't take long and bam, I wasn't even getting a 5g moniker. I call G-Fi and asked, WTF. I was told that G-Fi is now only allowing Google and Samsung phones to activate with 5G services, only 4g for V600am. Once again imei strikes. BTW you can page thru modem protocols here; *#546368#*600#>field test>modem settings>engineering mode to see if you even have the 5g protocol loaded. I use to but now I only have 2g, 3g, hspa and lte.
The only reason I'm bringing all this up is because Carrier Policies are changing with LG phones so It's worth a tech support call/chat with your carrier to see what's what on their side.
The next step would be to use a serious network app to verify what really going on. I think in your area the G-Mon app is being used a lot. I use Netmonster in the US. I saw a screen shot from a guy in Poland, I believe, that thought he was getting 5g only to find out that it was really lte+ 3xCA. He was getting 727.3 Mbps on the DL which is absolutely screaming. That’s faster than 99.9 % of the phones in the US.
hooutoo said:
Well I can tell you that there's a running discussion on a lot of the points you just made not the least of which is whether or not the modem is being provisioned at activation and if so what exactly and how much.
I have 2 lmv600am which I got off Ebay. Both had been crossed to EA fw when I got them. Since I'm on Google Fi, I went to the AT&T unlocking site and Sim unlocked. I then put my G-Fi sim into 1 of my v60 and sure enough I get a 5G moniker on my taskbar. Now during this time period Tmob is changing their policies on LG phones, mainly since LG is no longer in business. For example, lmv450 no longer actives on Tmob nor any of it's mvno's and I believe the same is happening for all Sprint phones plus all LG non-tmob phones. They're checking by imei.
So it didn't take long and bam, I wasn't even getting a 5g moniker. I call G-Fi and asked, WTF. I was told that G-Fi is now only allowing Google and Samsung phones to activate with 5G services, only 4g for V600am. Once again imei strikes. BTW you can page thru modem protocols here; *#546368#*600#>field test>modem settings>engineering mode to see if you even have the 5g protocol loaded. I use to but now I only have 2g, 3g, hspa and lte.
The only reason I'm bringing all this up is because Carrier Policies are changing with LG phones so It's worth a tech support call/chat with your carrier to see what's what on their side.
The next step would be to use a serious network app to verify what really going on. I think in your area the G-Mon app is being used a lot. I use Netmonster in the US. I saw a screen shot from a guy in Poland, I believe, that thought he was getting 5g only to find out that it was really lte+ 3xCA. He was getting 727.3 Mbps on the DL which is absolutely screaming. That’s faster than 99.9 % of the phones in the US.
Click to expand...
Click to collapse
Forgot to mention that I noticed that after a fresh flash, the xml files present in the EFS are different before and after inserting my sim.
Interesting but also disappointing to hear about the IMEI checking :/
I've been through hidden menu settings, and depending on which firmware I have installed I can see different bands and modem protocols available/activated, but can still never turn 5G on with my american V60's.
I had so much hope for this handset since firehose was made available!
Which reminds me, I even bootloader unlocked and rooted my crossflashed at&t unit. Successfully install Magisk etc, but couldn't enable r/w on system partition, even after generating and flashing a modified super partition. Something else going on here.
YOU need to check out the v60 group over on Discord.
cheesyzombie said:
Forgot to mention that I noticed that after a fresh flash, the xml files present in the EFS are different before and after inserting my sim.
Interesting but also disappointing to hear about the IMEI checking :/
I've been through hidden menu settings, and depending on which firmware I have installed I can see different bands and modem protocols available/activated, but can still never turn 5G on with my american V60's.
I had so much hope for this handset since firehose was made available!
Which reminds me, I even bootloader unlocked and rooted my crossflashed at&t unit. Successfully install Magisk etc, but couldn't enable r/w on system partition, even after generating and flashing a modified super partition. Something else going on here.
Click to expand...
Click to collapse
Increase the partition expansion to 300 or 400
hooutoo said:
YOU need to check out the v60 group over on Discord.
Click to expand...
Click to collapse
Hah I'm in the group, noticed a couple of your messages after the last post. I'm zobocop
ebowen 747 said:
Increase the partition expansion to 300 or 400
Click to expand...
Click to collapse
How do you change partition sizes?

Categories

Resources