I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Guille05 said:
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Click to expand...
Click to collapse
What original firmware was on it?Most definitely,always make a full back up first thing.
Surgemanxx said:
What original firmware was on it?Most definitely,always make a full back up first thing.
Click to expand...
Click to collapse
It was originally on version 20p of the sprint software. And yeah, I definitely hadn't quite read up on all of the important things I needed to backup beforehand.
Guille05 said:
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Click to expand...
Click to collapse
The same thing happened to me, I came from a10 sprint and installed a11 from Canada, I was left without a network and without a fingerprint sensor, but the other sensors work without problem, to fix network and ntcode I think it is only possible by box, I don't know if of the fingerprint sensor is caused by the lack of serial and imei.
if you come up with a solution let me know bro
mclarenf195 said:
The same thing happened to me, I came from a10 sprint and installed a11 from Canada, I was left without a network and without a fingerprint sensor, but the other sensors work without problem, to fix network and ntcode I think it is only possible by box, I don't know if of the fingerprint sensor is caused by the lack of serial and imei.
if you come up with a solution let me know bro
Click to expand...
Click to collapse
Did you restore your 7 bin files after flashing the A11 software?
Guille05 said:
Did you restore your 7 bin files after flashing the A11 software?
Click to expand...
Click to collapse
They don't have a backup,that's the reason I ask what version software it was.
Guille05 said:
It was originally on version 20p of the sprint software. And yeah, I definitely hadn't quite read up on all of the important things I needed to backup beforehand.
Click to expand...
Click to collapse
Use this firmware.It will correct your issues.
Download LG Firmware for LG G8X ThinQ LMG850QM _Unknown kdz stock USA Rom
Download _Unknown KDZ stock firmware for download with direct link
lg-roms.com
Guille05 said:
Did you restore your 7 bin files after flashing the A11 software?
Click to expand...
Click to collapse
I have the backup of the 7 partitions but they are useless if all the original partitions have been deleted, that is what I understand, I restored the partitions of a KDZ a10 and then flashed it to a11
Surgemanxx said:
Use this firmware.It will correct your issues.
Download LG Firmware for LG G8X ThinQ LMG850QM _Unknown kdz stock USA Rom
Download _Unknown KDZ stock firmware for download with direct link
lg-roms.com
Click to expand...
Click to collapse
I've got version 30c of that firmware installed, you think going back one update would fix it?
mclarenf195 said:
I have the backup of the 7 partitions but they are useless if all the original partitions have been deleted, that is what I understand, I restored the partitions of a KDZ a10 and then flashed it to a11
Click to expand...
Click to collapse
When you flashed the A10 kdz, you followed netmsm's guide right? Did you get any errors when flashing the partitions with fhloader? When I extracted the kdz a few files were missing from the ones used by that code but every kdz I've extracted doesn't have them either.
Guille05 said:
I've got version 30c of that firmware installed, you think going back one update would fix it?
Click to expand...
Click to collapse
Yes,go to 30b it will all work.I tried 30c on my sprint model,and had issues with network connectivity as well.
Surgemanxx said:
Yes,go to 30b it will all work.I tried 30c on my sprint model,and had issues with network connectivity as well.
Click to expand...
Click to collapse
I have the 30a, it would be to try
Guille05 said:
When you flashed the A10 kdz, you followed netmsm's guide right? Did you get any errors when flashing the partitions with fhloader? When I extracted the kdz a few files were missing from the ones used by that code but every kdz I've extracted doesn't have them either.
Click to expand...
Click to collapse
yes, the netmsm's guide, fhloader only use it to restore the luns, restore the kdz partitions one by one with qfil, just try what Surgemanxx suggested first and tell me how it goes.
mclarenf195 said:
yes, the netmsm's guide, fhloader only use it to restore the luns, restore the kdz partitions one by one with qfil, just try what Surgemanxx suggested first and tell me how it goes.
Click to expand...
Click to collapse
It works very well.I tried 30c,and noticed it was slow and laggy and rolled back to 30b and it worked flawless.Fingerprint scanning and all worked with a T-Mobile sim with no issues.They should be good with 30b,all but the IMEI issue they have.
All right I completely erased the flash again and reinstalled following the steps very carefully. I'm now on 30b and can confirm that the sensors work once again. Although the major issues I think were deeper than just the update, because I updated before doing a full erase and it still wasn't working. Now I just have to keep trying to fix the IMEI and FP sensor.
Also I think I may have found my IMEI number thanks to having the ftm partition backed up and therefore still having the serial number. The first 8 digits are always 35886110 for the LG G8x sprint model (and maybe others in the US), the next 6 are the last 6 digits of the serial and the last one is a check digit that you can look up online. I've checked the number on multiple sites and it seems legit so I hope it's actually my number. Now I'll try to write it to the phone somehow, but at least having the IMEI back is a very big step forward.
IMEI is fixed, or at least it appears as such in the phone. I went through with the tutty method of installing the IMEI, and after much trouble (and tutty saying error to my command to write the IMEI) I was able to restore the IMEI to the phone. I confirmed this first using EFS Pro and going into qualcomm NV tools. The IMEI was still as 0 in my phone but after putting in a sim it appeared in the OS and has stayed there. However it still appears as permanently locked when a sim is inserted and the nt-code error does still happen, so the network doesn't work yet.
Guille05 said:
IMEI is fixed, or at least it appears as such in the phone. I went through with the tutty method of installing the IMEI, and after much trouble (and tutty saying error to my command to write the IMEI) I was able to restore the IMEI to the phone. I confirmed this first using EFS Pro and going into qualcomm NV tools. The IMEI was still as 0 in my phone but after putting in a sim it appeared in the OS and has stayed there. However it still appears as permanently locked when a sim is inserted and the nt-code error does still happen, so the network doesn't work yet.
Click to expand...
Click to collapse
That LUNS backup is for the Sprint U.S. model G850UM9.The IMEI is stored in modemst1 and 2 which is LUNS5 that I didn't include for that reason.The NT Code error shouldn't be there if it's the same model/region.Keep me posted.
Surgemanxx said:
That LUNS backup is for the Sprint U.S. model G850UM9.The IMEI is stored in modemst1 and 2 which is LUNS5 that I didn't include for that reason.The NT Code error shouldn't be there if it's the same model/region.Keep me posted.
Click to expand...
Click to collapse
I've flashed your backups and the NT Code error indeed disappeared. However I've still got the perm locked error (so my doesn't work), and the fp sensor still refuses record fingerprints. Was your phone network unlocked when you made that backup? Idk if that maybe interferes with the sim or something
Guille05 said:
I've flashed your backups and the NT Code error indeed disappeared. However I've still got the perm locked error (so my doesn't work), and the fp sensor still refuses record fingerprints. Was your phone network unlocked when you made that backup? Idk if that maybe interferes with the sim or something
Click to expand...
Click to collapse
Yes,it was network unlocked for sure.You're not the only one that has faced this after trying to repair the IMEI.It's perma blocked because it's embedded in the chipset itself,and so far I haven't seen any fix for it as of yet.
Related
Hi there.
I wanted to unlock my bootloader, root and flash a custom rom. So I first flashed the global fastboot rom 7.2.5, later flashed the s-twrp recovery and flashed the lineageOs 7.1. I realised that my sim cards weren't working so therefore switched to resurrection remix. Even then, I couldn't get the network even though wifi was working. So I flashed the global fastboot rom again. I still couldn't get the network. Then I realised that my IMEI number might've been erased while flashing even though I followed every step correctly. I dialed *#*#4636#*#* and found out that my IMEI numbers were now unknown. I got to know that my IMEI numbers were definitely wiped. I tried flashing recoveries, boot images, modem files, etc and now I can't even use WiFi. I tried using the WriteDualIMEI application but unfortunately it isn't finding the COM10/20/9/11 port. I have no clue what to do as of now. Can somebody help me with necessary links and details?
Thanks in advance.
Had this problem yesterday. You may refer to my thread on MIUI forum and see if it can help you. Assuming you have Kenzo variant like I do, refer to this and this first to recover IMEI number as well as EFS, then read the rest of my thread to get signal once you recover the IMEI.
slaveration said:
Had this problem yesterday. You may refer to my thread on MIUI forum and see if it can help you. Assuming you have Kenzo variant like I do, refer to this and this first to recover IMEI number as well as EFS, then read the rest of my thread to get signal once you recover the IMEI.
Click to expand...
Click to collapse
Hey there! Thanks for the quick response! It really means a lot.
The EFS thing makes sense now since all my details such as MAC Address, Baseband, IMEI number, etc are all unavailable or unknown. I tried flashing the modem files but are still unknown. Any tips?
keshavkd said:
Hey there! Thanks for the quick response! It really means a lot.
The EFS thing makes sense now since all my details such as MAC Address, Baseband, IMEI number, etc are all unavailable or unknown. I tried flashing the modem files but are still unknown. Any tips?
Click to expand...
Click to collapse
Did you try this guide to restore baseband/IMEI/MAC etc first? You may also use this QCN in case the XQCN in the guide didn't work. Follow carefully the guide. Then after you get everything, you may change the IMEI using tool found here . After that, follow my thread to flash everything possible to get all the connection back.
slaveration said:
Did you try this guide to restore baseband/IMEI/MAC etc first? You may also use this QCN in case the XQCN in the guide didn't work. Follow carefully the guide. Then after you get everything, you may change the IMEI using tool found here . After that, follow my thread to flash everything possible to get all the connection back.
Click to expand...
Click to collapse
That QCN file was vital! Thank you so much! Now all there's left to do is fix the signal! I've successfully got my IMEI numbers back and the baseband!
keshavkd said:
That QCN file was vital! Thank you so much! Now all there's left to do is fix the signal! I've successfully got my IMEI numbers back and the baseband!
Click to expand...
Click to collapse
Yes that's great! Follow my thread and flash some needed files. Next time please make a full nandroid backup before doing anything okay
Hi everyone, I've followed the WTF thread to unlock the bootloader on a V30 H933 (the Canadian version), but even after unlocking there's no fastboot support on the phone, only the US998 version seems to have it. Trouble is that Rogers, my local operator, only supports VoLTE and VoWiFi on their recognized devices - I tried having US998 running on my phone, calling their support and possibly getting some actual configuration I could put on the phone, but their response was "your phone is defective and needs to be replaced".
All that said, my goal here is to somehow install TWRP on this phone and root under the original ROM, so I can have the features I need from the network. So far, I've been pretty unsuccessful in this, so my plead would be: could anyone chime in to help me either
flash the minimal necessary over US998 to get H933 functionality/network information back as to reenable VoLTE and VoWiFi on my operator
come up with an update.zip or some other file I could use to flash a Magisk-patched boot.img
pack a full flashable ZIP image of the Canadian ROM (my last attempt at this left the phone in bootloop)
an alternative idea I haven't thought about that could help?
Ideally, at the end of the process, I'd like to have TWRP and Magisk installed on the phone, but I could settle for simply Magisk.
Once again, any help or pointers are more than welcome and appreciated.
I think you can extract a h933 kdz and flash individual partitions that do not have to do with recovery or the bootloader. You can probably use the dd command for it. I think the partitions you dont flash are anything with boot in it, abl and recovery. There may be a few more however.
The Elite said:
I think you can extract a h933 kdz and flash individual partitions that do not have to do with recovery or the bootloader. You can probably use the dd command for it. I think the partitions you dont flash are anything with boot in it, abl and recovery. There may be a few more however.
Click to expand...
Click to collapse
I tried something similar, extracted a KDZ and put the necessary BIN files on a flashable ZIP I found around. All I achieved was bootlooping the device...
I have an H933 on Freedom Mobile, and running the stock FM firmware. The loss of VOWIFI (and VoLTE) are exactly what i thought would happen if I proceed with flashing to US998.
I think #1 is right; that you may be able to restore access to network specific functionality but it would depend on being able to isolate the specific required "patch".
With this in mind, take a look at this post from the WTF! Thread:
https://forum.xda-developers.com/showthread.php?p=76613814
That user flashed some files (modem binaries from the original device firmware I think) and was able to restore VOWIFI and VoLTE functionality on the Verizon network.
Sent from my LG-H933 using Tapatalk
My h933 converted to us998 says that my volte is enabled
cre4per said:
My h933 converted to us998 says that my volte is enabled
Click to expand...
Click to collapse
What menu is that from @cre4per? Have you had the opportunity to confirm staying on LTE while receiving a call?
That would be good news to hear VoLTE working on a Canadian network using a generic phone model (instead of proprietary stuff).
Sent from my LG-US998 using Tapatalk
Mad Medik said:
What menu is that from @cre4per? Have you had the opportunity to confirm staying on LTE while receiving a call?
That would be good news to hear VoLTE working on a Canadian network using a generic phone model (instead of proprietary stuff).
Sent from my LG-US998 using Tapatalk
Click to expand...
Click to collapse
*#*#4636#*#*,
and to be honest i never really noticed, will do some checks today to see if i stay on lte, will let you know
cre4per said:
*#*#4636#*#*,
and to be honest i never really noticed, will do some checks today to see if i stay on lte, will let you know
Click to expand...
Click to collapse
Looking at this this morning. I don't think that is an indication that you are connected to a VoLTE service; just that your device is ready to accept it if the right service becomes available. I have that switch turned on and the service menu even says the voice network is LTE too (see image below) but Freedom Mobile doesn't even offer VoLTE service so it isn't possible that I actually have VoLTE operational.
I would interpret the LTE provision switch as turning on or off the functionality in your device, not a connection authorization from the network. Sort of like turning on the HD calling option on your device; it allows the possibility but won't do anything unless the service provider has the capability and authorizes it on your connection.
If someone has VoLTE working, could you check the menu cited by @cre4per, then hit the options (3 dots) and in there, select IMS service status? It lools like this is where you *should* see if the network has connected you to their VoLTE service (see image below).
I don't know how to interpret the, "Voice Network: LTE" on the main menu screen.
Just check and switches to 3g on calls also when going into that ims menu says unavailable
GryphonBR said:
I tried something similar, extracted a KDZ and put the necessary BIN files on a flashable ZIP I found around. All I achieved was bootlooping the device...
Click to expand...
Click to collapse
Out of all the partitions which ones did you flash and which ones did you not flash? Also was the h933 kdz also for oreo?
-deleted-
cre4per said:
My h933 converted to us998 says that my volte is enabled
Click to expand...
Click to collapse
As @Mad Medik mentioned, so far I don't know of any Canadian operators enabling VoLTE (or VoWiFi for that matter) to generic phones. I have a Rogers P10 Plus that's registered under my account as my main phone and which I reflashed to have these features available, but it just won't work. I've had extended arguments with Rogers representatives about it, and the 1+3T I'm presently using even have the same config your phone is showing: VoLTE Provisioned, but IMS shows as Not Registered so nothing else works. I'm waiting on an LS998 I bought to arrive, I'll try flashing H933 on it to see if it actually allows me to register on IMS.
The Elite said:
Out of all the partitions which ones did you flash and which ones did you not flash? Also was the h933 kdz also for oreo?
Click to expand...
Click to collapse
KDZ was for Oreo, indeed. It was the one I used to bring the phone to the latest (at the moment) update available.
As for which partitions I flashed, I was gonna give you a list, but to make it short the only partition not flashed was recovery.
GryphonBR said:
As @Mad Medik
KDZ was for Oreo, indeed. It was the one I used to bring the phone to the latest (at the moment) update available.
As for which partitions I flashed, I was gonna give you a list, but to make it short the only partition not flashed was recovery.
Click to expand...
Click to collapse
As far as I know there are some boot partitions that should not be flashed, which may have caused the soft brick. I know autoprime used to make these zips for the G3 and runningnak3d made one for the V10, you might want to cross reference the partitions they used and what they didnt. Probably the V10 first because the G3 is relatively ancient. I think in essence you should just be able to flash boot, system and modem and rpm though, but you would need 2 combine the split up system images after the extract.
The Elite said:
As far as I know there are some boot partitions that should not be flashed, which may have caused the soft brick. I know autoprime used to make these zips for the G3 and runningnak3d made one for the V10, you might want to cross reference the partitions they used and what they didnt. Probably the V10 first because the G3 is relatively ancient. I think in essence you should just be able to flash boot, system and modem and rpm though, but you would need 2 combine the split up system images after the extract.
Click to expand...
Click to collapse
The reason why I was flashing everything is because I used this thread to recover from a previous soft brick I stumbled upon. Upon speaking to the thread creator, he mentioned I should be able to follow a similar process to achieve an H933 flashable file. Did that and, well, managed to soft brick the phone... I might try your idea, though.
So, from my knowledge of attempting to get VoLTE working on an HTC 10, I suspect you won't get VoLTE working on anything other than Rogers H933 firmware. For whatever reason, the programming required for VoLTE isn't on the USIM card in your phone, but rather programmed into the phone by the provider. This means, unless your phone model is sold and supported for VoLTE on the provider you wish to use it on, you're screwed like I was, trying to get VoLTE working on my HTC 10 on Rogers.
This being said, the good news is we are back to CDMA tech here, where the only thing preventing you from using your third party phone with your provider is knowing what code to enter, and what parameters to program in. Since my H933 is on Telus, my programming won't do you much good.
What you're looking for is the IMS settings or IP Multimedia Subsystem settings, as this is what carries the VoIP packets that consist of VoLTE. If someone were to post the settings from their Rogers H933, you may be able to get VoLTE working on US998 firmware.
Why not just flash system and boot? After unlocked and rooted of course.. Lg up partition DL will let you flash individual partitions. I would have done it that way for my carrier but there is no kdz available..
JWnSC said:
Why not just flash system and boot? After unlocked and rooted of course.. Lg up partition DL will let you flash individual partitions. I would have done it that way for my carrier but there is no kdz available..
Click to expand...
Click to collapse
I tried that last night just bootloops
cre4per said:
I tried that last night just bootloops
Click to expand...
Click to collapse
Did you wipe data?
JWnSC said:
Did you wipe data?
Click to expand...
Click to collapse
Yea. Then went to restore and the restore wouldn't even work anymore. Was saying there was no partitions backed up but I had use that restore numerous of times trying to get los to boot very strange had to start back from scratch
Anyone with H933 from freedom mobile convert to US988? I'm just wondering how the service is after the change. I'm reading mixed reports but once modems extracted and compared there was a difference.
So I managed to downgrade to successfully unlock my bootloader however I am now stuck on 8.0.0.046(092Y) and am unable to OTA update. I have installed magisk and TWRP and they are both currently working however I am curious as to why I cannot update to a newer 8.0 OTA firmware. Any suggestions? The device is an ANE-LX3 single sim.
Because you used wrong firmware.
(092y) or similar numbers are here because wrong firmware..
At least that was case for me, when I installed single SIM firmware over dual SIM phone, and of course, that build number not exist in update servers, so no updates here, till you fix your firmware
Arnys said:
Because you used wrong firmware.
(092y) or similar numbers are here because wrong firmware..
At least that was case for me, when I installed single SIM firmware over dual SIM phone, and of course, that build number not exist in update servers, so no updates here, till you fix your firmware
Click to expand...
Click to collapse
This is what I feared, thanks for confirming. I am hoping flashing this will solve my issues. Any advice before doing so?
metalfangs said:
This is what I feared, thanks for confirming. I am hoping flashing this will solve my issues. Any advice before doing so?
Click to expand...
Click to collapse
HM.. in link you gave here, is writed about ane-lx1, you mentioned your phone are ane-lx3 single sim, so, I'm not sure it can fix your problem..
And I'm not used that files, and can't say anything about that.
And more important, what was full build number for your phone, aka ane-lx3c779, something like that, can you find it? Then I maybe be able to help.
And ,wulda be great if you type down all you did with phone, what used, etc.
Arnys said:
HM.. in link you gave here, is writed about ane-lx1, you mentioned your phone are ane-lx3 single sim, so, I'm not sure it can fix your problem..
And I'm not used that files, and can't say anything about that..
Click to expand...
Click to collapse
I noticed the file name is LX1 however in the description it says its for all models which is confusing. Any idea where I could find an official firmware download for LX3? Even a functional custom rom compatible with my device would be fine if I could find one.
I used hisuite to first downgrade and then used the firmware from this post to dload downgrade again in order to unlock the bootloader. I then factory reset after successfully unlocking the bootloader which left me at build 046.
To be honest I cannot remember what the original build number was although c779 does sound very familiar.
metalfangs said:
I noticed the file name is LX1 however in the description it says its for all models which is confusing. Any idea where I could find an official firmware download for LX3? Even a functional custom rom compatible with my device would be fine if I could find one.
I used hisuite to first downgrade and then used the firmware from this post to dload downgrade again in order to unlock the bootloader. I then factory reset after successfully unlocking the bootloader which left me at build 046.
To be honest I cannot remember what the original build number was although c779 does sound very familiar.
Click to expand...
Click to collapse
Hm, did you tried erecovery method ? Maybe that can fix your problem
metalfangs said:
So I managed to downgrade to successfully unlock my bootloader however I am now stuck on 8.0.0.046(092Y) and am unable to OTA update. I have installed magisk and TWRP and they are both currently working however I am curious as to why I cannot update to a newer 8.0 OTA firmware. Any suggestions? The device is an ANE-LX3 single sim.
Click to expand...
Click to collapse
Hello there brother. May I humbly ask how did you get your bootloader unlocked after downgrading? Can you share some steps please if you don't mind. Thank you
Omg, I've been messing with this thing for 2 months trying to fix it, all because I didn't take a backup of my /persist as soon as I got the phone, but there is a way to fix it!!! The only pre-requisites are that:
A) you still have your own /persist (that came with your specific phone, didn't overwrite it with one from the forums and didn't save your original somewhere) AND
B) all sensors still work (only the fingerprint scanner is broken) AND
C) that you have NEVER ran the hidden fingerprint calibration tools accessible from *#808# (unless you have a backup of /persist from before you did that)
Follow these simple instructions and enjoy:
https://forum.xda-developers.com/oneplus-8/how-to/guide-fix-persist-img-loss-finger-print-t4126455
You can ignore the entire part about having to run the MSM tool to roll back to a previous version of OOS (Step 2). Therefore, no data is lost, no factory reset is required, etc.
Also in very first part of Step 4, you need to dial *#808#, not *#801#
It took me less than 15 minutes and now it's good as new!!! Please give the OP thanks! He spent almost 200 hours figuring this out (and I don't doubt it; I must have spent easily over 20 hours myself and didn't get anywhere...). All I did was find his genius instructions and post them here.
Edit: And to add one last step to the guide, after you finish and get the fp scanner working again, please be sure to take a backup of your now fixed persist partition and store it in at least two different locations. Because if you are reading this, you are most likely modding your phone with at least Magisk (why else unlock the bootloader? and almost anything can cause persist to be corrupted. For me, it was simply installing a bad build of magisk canary back in May that did it. It's not just important for those installing aftermarket ROMs. It's vital for anyone who even thinks about unlocking the bootloader on this device. Because even the act of relocking the bootloader has caused persist to be corrupted for some...
Edit2: If you run the MSM tool after fixing persist, or manually relock the bootloader, you'll wind up with your FP being broken again. I'm assuming because the checksum of the "fixed" persist doesn't match that of the original, unmodified persist, so it gets marked as corrupt again. So you'll need to unlock the bootloader and restore/flash your backed up, fixed persist (you did back it up this time, right? Impossible to run msm tool to get back to stock AND have FP working. Bootloader must be unlocked after using msm tool and fixed persist restored.
please help HD9010 indian firmware currently..before i had global
i messed up my persist too while reverting back from open beta to stable via fastboot
now fingerprint enrollment error
i tried the guide but its not the same with 7tpro
there wasnt 'gf_persist.so' in data folder of my extracted persist.img
and calibrating was confusing for me but i did it upro my limit but i didnt have those many reds as the original OP had in his guide video while calibrating the fp
so please can you be kind enough to share your whole process that you used to manage the fingerprint error issue?
like what roms you used before and after or during fix?
and lastly, since the backedup persist didnt work i deleted and again backedup the persist in next attempt so it means my fingerprint is gone permanently? maybe?
please help me..ive spent my whole night and day searching and trying workarounds flashing roms back and forth
the hellboy said:
i messed up my persist too while reverting back from open beta to stable via fastboot
now fingerprint enrollment error
i tried the guide but its not the same with 7tpro
there wasnt 'gf_persist.so' in data folder of my extracted persist.img
and calibrating was confusing for me but i did it upro my limit but i didnt have those many reds as the original OP had in his guide video while calibrating the fp
so please can you be kind enough to share your whole process that you used to manage the fingerprint error issue?
like what roms you used before and after or during fix?
and lastly, since the backedup persist didnt work i deleted and again backedup the persist in next attempt so it means my fingerprint is gone permanently? maybe?
please help me..ive spent my whole night and day searching and trying workarounds flashing roms back and forth
Click to expand...
Click to collapse
I used his exact instructions on my 7T Pro 5G McLaren edition from T-Mobile. With a few helpful tips I added. You must have the global version of the 7T Pro McLaren since you are talking about open beta and stable releases. Unfortunately I can't help you there. It seems that the TMobile 7T Pro 5G McLaren is much more similar to the OP8 in some ways than the global 7T Pro, especially when it comes to OOS, partitioning, extra security crap, etc.
Edit:. You are in the wrong forum. You don't even have the global 7T Pro McLaren. You have the HD1910 Global (originally Chinese version) 7T Pro. Wrong forum. The 7T Pros didn't even have this issue (or if they did, it was no where near as widespread, I've never even seen it mentioned a single time). To the best of my knowledge, it began with the 7T Pro 5G McLaren from T-Mobile which was the newest phone released by 1+ until the OP8.
And if you deleted your backup of your original persist after trying to fix it unsuccessfully, it's now broken forever regardless. You need to RMA.
Late response, but this worked 100% for me after switching back to stock from AOSiP.
Thank you!
derget1212 said:
Late response, but this worked 100% for me after switching back to stock from AOSiP.
Thank you!
Click to expand...
Click to collapse
Glad to hear it worked!
One important thing to add:
If you run the MSM tool after fixing persist, or manually relock the bootloader, you'll wind up with your FP being broken again. I'm assuming because the checksum of the "fixed" persist doesn't match that of the original, unmodified persist, so it gets marked as corrupt again. So you'll need to unlock the bootloader and restore/flash your backed up, fixed persist (you did back it up, right? . Impossible to run msm tool to get back to stock AND have FP working. Bootloader must be unlocked after using msm tool and fixed persist restored.
starcms said:
Glad to hear it worked!
One important thing to add:
If you run the MSM tool after fixing persist, or manually relock the bootloader, you'll wind up with your FP being broken again. I'm assuming because the checksum of the "fixed" persist doesn't match that of the original, unmodified persist, so it gets marked as corrupt again. So you'll need to unlock the bootloader and restore/flash your backed up, fixed persist (you did back it up, right? . Impossible to run msm tool to get back to stock AND have FP working. Bootloader must be unlocked after using msm tool and fixed persist restored.
Click to expand...
Click to collapse
in the guide it tells you to get your phone into factory mode but does not tell you to take it out of factory mode. of you turn factory mode off and use the msm tool will fingerprint still work afterwords
cgrimm9 said:
in the guide it tells you to get your phone into factory mode but does not tell you to take it out of factory mode. of you turn factory mode off and use the msm tool will fingerprint still work afterwords
Click to expand...
Click to collapse
Apparently you need to reread the instructions
I did step three says.
3. Next step is to unlock the built in 'Factory Mode' I have a guide on how to do this below.
https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlock-factory-mode-root-t4118527
No where on this instructions says to relock the factory mode. I am just asking if you where to do that will fingerprint scanner work after doing msm tool.
I did the process 2 times now. Have no interest in doing it again unless I need to update. I just putting some thought in why I don't know if it's relavent or not just asking. sometimes a difficult problem can have a easy solution just got to figure it out
cgrimm9 said:
I did step three says.
3. Next step is to unlock the built in 'Factory Mode' I have a guide on how to do this below.
https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlock-factory-mode-root-t4118527
No where on this instructions says to relock the factory mode. I am just asking if you where to do that will fingerprint scanner work after doing msm tool.
I did the process 2 times now. Have no interest in doing it again unless I need to update. I just putting some thought in why I don't know if it's relavent or not just asking. sometimes a difficult problem can have a easy solution just got to figure it out
Click to expand...
Click to collapse
Yes, you can relock factory mode when done. Just re-edit those 2 lines. And once you have your FP working again, please be sure to make a backup of your fixed persist.img. Then you'll never have to do all the steps again. Simply restore your fixed persist.img if FP ever breaks again.
starcms said:
Omg, I've been messing with this thing for 2 months trying to fix it, all because I didn't take a backup of my /persist as soon as I got the phone, but there is a way to fix it!!! The only pre-requisites are that:
A) you still have your own /persist (that came with your specific phone, didn't overwrite it with one from the forums and didn't save your original somewhere) AND
B) all sensors still work (only the fingerprint scanner is broken) AND
C) that you have NEVER ran the hidden fingerprint calibration tools accessible from *#808# (unless you have a backup of /persist from before you did that)
Follow these simple instructions and enjoy:
https://forum.xda-developers.com/oneplus-8/how-to/guide-fix-persist-img-loss-finger-print-t4126455
You can ignore the entire part about having to run the MSM tool to roll back to a previous version of OOS (Step 2). Therefore, no data is lost, no factory reset is required, etc.
Also in very first part of Step 4, you need to dial *#808#, not *#801#
It took me less than 15 minutes and now it's good as new!!! Please give the OP thanks! He spent almost 200 hours figuring this out (and I don't doubt it; I must have spent easily over 20 hours myself and didn't get anywhere...). All I did was find his genius instructions and post them here.
Edit: And to add one last step to the guide, after you finish and get the fp scanner working again, please be sure to take a backup of your now fixed persist partition and store it in at least two different locations. Because if you are reading this, you are most likely modding your phone with at least Magisk (why else unlock the bootloader? and almost anything can cause persist to be corrupted. For me, it was simply installing a bad build of magisk canary back in May that did it. It's not just important for those installing aftermarket ROMs. It's vital for anyone who even thinks about unlocking the bootloader on this device. Because even the act of relocking the bootloader has caused persist to be corrupted for some...
Edit2: If you run the MSM tool after fixing persist, or manually relock the bootloader, you'll wind up with your FP being broken again. I'm assuming because the checksum of the "fixed" persist doesn't match that of the original, unmodified persist, so it gets marked as corrupt again. So you'll need to unlock the bootloader and restore/flash your backed up, fixed persist (you did back it up this time, right? Impossible to run msm tool to get back to stock AND have FP working. Bootloader must be unlocked after using msm tool and fixed persist restored.
Click to expand...
Click to collapse
yep. same here spent so much time on it. Then me and that dev crossed paths. i told him what i found and he told me what he found and together it birthed that hack
fp also works in custom roms now
So this fixed my issue with registering my fingerprints, but even after registering 5 prints, when I go to unlock my phone or anything that uses my prints scanning fails like 90% of the time. I have to press really hard or just put in my pin to get my phone to unlock. I removed my screen protector and cleaned my screen. Is there a way to recalibrate the scanner?
Trevaryn said:
So this fixed my issue with registering my fingerprints, but even after registering 5 prints, when I go to unlock my phone or anything that uses my prints scanning fails like 90% of the time. I have to press really hard or just put in my pin to get my phone to unlock. I removed my screen protector and cleaned my screen. Is there a way to recalibrate the scanner?
Click to expand...
Click to collapse
Program each finger twice. Also, it'll get much, much, much better with time as it autocalibrates/learns over a week or so.
I don't quite follow step 5 in the guide:
5. We need to extract the the old broken persist.img. The way I did this is by opening it extracting it via 7-ZIP on my PC
Click to expand...
Click to collapse
Also, do you run the steps after flashing a custom ROM?
pgg285 said:
I don't quite follow step 5 in the guide:
Also, do you run the steps after flashing a custom ROM?
Click to expand...
Click to collapse
For step 5, just extract it as if it was a zip file on your PC.
After fixing persist and getting FP working, make sure you make a backup of the fixed persist.img and save it in at least 2 or 3 different places to be safe. Occasionally for custom ROMs, to get the FP working after flashing ROM, take your fixed persist, go to fastboot, and do "fastboot flash persist your_backed_up_fixed_persist.img"
i just wanted to say that for some weird or maybe lucky reason, i did not have to reflash my backed up persist after using the msm to get back to stock from the aosip custom rom. I used the bootloader unlock trick through modded msm to install the rom and i went back using msm and fingerprint worked on the get go. I did not have to unlock bootloader and reflash persist.img .. not sure why i didnt have to its weird ( i never flashed my persist at all, even after installing the custom rom)
i think i lost my fingerprint forever because i have never done any backup and i flashed custom rom so RIP my fingerprint.
Would it make a difference if i dont lock factory mode or leave it unlocked?
AssyrianHero said:
i think i lost my fingerprint forever because i have never done any backup and i flashed custom rom so RIP my fingerprint.
Click to expand...
Click to collapse
That's exactly what these instructions are meant to fix...
the hellboy said:
please help HD9010 indian firmware currently..before i had global
i messed up my persist too while reverting back from open beta to stable via fastboot
now fingerprint enrollment error
i tried the guide but its not the same with 7tpro
there wasnt 'gf_persist.so' in data folder of my extracted persist.img
and calibrating was confusing for me but i did it upro my limit but i didnt have those many reds as the original OP had in his guide video while calibrating the fp
so please can you be kind enough to share your whole process that you used to manage the fingerprint error issue?
like what roms you used before and after or during fix?
and lastly, since the backedup persist didnt work i deleted and again backedup the persist in next attempt so it means my fingerprint is gone permanently? maybe?
please help me..ive spent my whole night and day searching and trying workarounds flashing roms back and forth
Click to expand...
Click to collapse
Brother i am suffering the same problem with same device OP 7T PRO, Did you managed to solve the problem? It will be a great help if you tell me
My mail id - [email protected]
the hellboy said:
please help HD9010 indian firmware currently..before i had global
i messed up my persist too while reverting back from open beta to stable via fastboot
now fingerprint enrollment error
i tried the guide but its not the same with 7tpro
there wasnt 'gf_persist.so' in data folder of my extracted persist.img
and calibrating was confusing for me but i did it upro my limit but i didnt have those many reds as the original OP had in his guide video while calibrating the fp
so please can you be kind enough to share your whole process that you used to manage the fingerprint error issue?
like what roms you used before and after or during fix?
and lastly, since the backedup persist didnt work i deleted and again backedup the persist in next attempt so it means my fingerprint is gone permanently? maybe?
please help me..ive spent my whole night and day searching and trying workarounds flashing roms back and forth
Click to expand...
Click to collapse
The instructions only work for the T-Mobile 7T Pro 5G Mclaren edition, all OP8, all OP8 pro, no idea about OP8T. That's because this was the first device that OnePlus used a different format for persist. That's confirmed by you not having gf_persist.so.
You would need to look at the forums for the OnePlus 7T Pro for a possible answer: https://forum.xda-developers.com/c/oneplus-7t-pro.9327/ The forums you are in now are ONLY for the HD1925, the T-Mobile branded 7T Pro 5G Mclaren variant.
And lastly, if you deleted your original persist.img (the one with broken fp), which it sounds like you did, and then wiped persist again afterwards, then there is absolutely no hope of fixing it besides sending it to OnePlus. Because you've lost your entire original persist if that is the case, unless you still have a backup of original persist.img with broken fp from before you tried fixing it.
Honestly found it on XDA of all places after looking for it all night
What does 1.16 give us that 1.14 doesn't? Everything honestly. Could not get my Wing recognized to flash with 1.14. No 1.15 Patched exists either
We can downgrade with ChipErase (and restore IMEI), we can modify PDM, we can dump the entire phone (will do tomorrow), can upgrade.
See link here for link: https://forum.xda-developers.com/t/...er-w-fastboot-drivers-and-common_dll.4304181/
This was the only working LGUp_Tool that worked outside of LGUP CMD
I wanted this to try other countries firmware files to see if we get other weird results. This should also allow custom KDZ files? from my understanding
ADDED INFO Nov 8, 2021
How to use LGUp Tool From this Download
1.) Download the LGUp 1.16.03 Patched from the XDA Link above
2.) Run the EXE as admin so it can install Drivers and the software properly
3.) Go to the install directory and run the 2 Bat files that are in the folder as admin
Code:
Default: C:\Program Files(x86)\LG Electronics\LGUp
-- Running LGUP_UI-fixer.bat -- run as admin, follow instructions, run the software when it says to, then close it
-- Run LGUP_UI-Fixer-addon.bat -- run as admin, follow steps, then run LGUp.exe when patch complete
You now have a working LGUP Tool 1.16 Patched for the LG Wing
Explaining the functions of LGUP Tool
Code:
REFURBISH： You will lose all user data（KDZ or TOT）
UPGRADE: Keep data and update your phone（KDZ or TOT) - Select Upgrade to flash kdz firmware to unbrick/restore your phone back to stock.
Chip Erase: Dangerous, This will erase IMEI/efs, do not try this if you do not have a NV backup. - Chip Erase can also remove the Google FRP on many LG devices with Android 5.0, 6.0.
PARTITION DL：Flash the single Partition or selected partitions onto your phone. - This feature can solve “unknown model” issues. This feature can be used to bypass Google FRP by flashing specific tot firmware.
DUMP：Dump all partitions of your phone as backup. - Dump the stock firmware from a working phone as back up and use Partition DL to restore phones.
FOTA Upgrade: This can be used to flash OTA Update file that comes with dot up file extension.
PDM: Change imei, wifi address, bluetooth, mac address
video for how to use LGUP Tool to flash the Wing
Awesome! I just DL'ed.. don't know when I'll have time to mess around with it. Or if I have the skill set to help. But I would definitely try to help out if I can and be excited for rootable firmware.
kaluna00 said:
Awesome! I just DL'ed.. don't know when I'll have time to mess around with it. Or if I have the skill set to help. But I would definitely try to help out if I can and be excited for rootable firmware.
Click to expand...
Click to collapse
I plan on making a video I'll put on the post explaining the tool
KaptinBoxxi said:
I plan on making a video I'll put on the post explaining the tool
Click to expand...
Click to collapse
Holy cow I can’t believe it. You actually found the exact tool that we needed! I went ahead and did a chip erase on my demo model, which had previously been flashed with the Korean firmware from the previous tutorial, and flashed the T-Mobile Firmware. IT WORKED! To get rid of the error at that shows up every time you reboot it, I accessed the hidden menu and changed the TN number to the one associated with TMO_US, as shown in this post.
Thank you!
twocans said:
Holy cow I can’t believe it. You actually found the exact tool that we needed! I went ahead and did a chip erase on my demo model, which had previously been flashed with the Korean firmware from the previous tutorial, and flashed the T-Mobile Firmware. IT WORKED! To get rid of the error at that shows up every time you reboot it, I accessed the hidden menu and changed the TN number to the one associated with TMO_US, as shown in this post.
Thank you!
Click to expand...
Click to collapse
I still can't get mine to accept a sim card and get data but I can make calls/text and use wifi, which is nice.
I wish Partition DL worked, we'd have the boot.img
I flashed Verizon Firmware and put the Verizon NT Code using PDM Mode, still didn't work. Going to try others later
KaptinBoxxi said:
I still can't get mine to accept a sim card and get data but I can make calls/text and use wifi, which is nice.
I wish Partition DL worked, we'd have the boot.img
I flashed Verizon Firmware and put the Verizon NT Code using PDM Mode, still didn't work. Going to try others later
Click to expand...
Click to collapse
Where did you get the Verizon firmware?
kaluna00 said:
Where did you get the Verizon firmware?
Click to expand...
Click to collapse
I found a site that had a "KDZ Downloader" and used that to download it. I can upload it here for those who need it once i redownload it here at work
or you can yourself from this post. Just need the LG URL to the firmware
[LG TOOLS] LG-KDZ-dll-Tool/LGUP_UI-fixer/LG-Kdz-downloader
Please, do not share elsewhere as I want to be able to update if necessary ! LG-KDZ-dll-Tool/KDZ dll extractor (=old version) : this message actually, scroll down a bit... LGUP_UI-fixer LG-Kdz-downloader Share this thread or my blog instead...
forum.xda-developers.com
KaptinBoxxi said:
I still can't get mine to accept a sim card and get data but I can make calls/text and use wifi, which is nice.
I wish Partition DL worked, we'd have the boot.img
I flashed Verizon Firmware and put the Verizon NT Code using PDM Mode, still didn't work. Going to try others later
Click to expand...
Click to collapse
I bought a mint mobile trial sim from amazon and I’m getting calls, text, and 5G data.
twocans said:
I bought a mint mobile trial sim from amazon and I’m getting calls, text, and 5G data.
Click to expand...
Click to collapse
I get calls and text, no cell service at all. I had to manually program in an IMEI. My IMEI comes back as 0 if I just flash it without PDM. IMEI doesn't apply via the service menu either
KaptinBoxxi said:
I get calls and text, no cell service at all. I had to manually program in an IMEI. My IMEI comes back as 0 if I just flash it without PDM. IMEI doesn't apply via the service menu either
Click to expand...
Click to collapse
Interesting. I was able to generate an IMEI in the hidden menu after the chip erase and it worked fine. I did also have to re-add my CSN, because that was also removed, and then my phone did an unprompted factory reset and rebooted.
By the way, when you flashed it, did you use Refurbish? Because with my demo unit, it refused to let me do that and would only allow chip erase. I was reluctant, but it turned out fine. And, the only important thing I was unable to reprogram afterwords was the S/N, but it doesn’t really matter to me. (Too bad the fingerprint scanner still doesn’t work though. That’s the only thing left that still isn’t working after all of this.)
twocans said:
Interesting. I was able to generate an IMEI in the hidden menu after the chip erase and it worked fine. I did also have to re-add my CSN, because that was also removed, and then my phone did an unprompted factory reset and rebooted.
By the way, when you flashed it, did you use Refurbish? Because with my demo unit, it refused to let me do that and would only allow chip erase. I was reluctant, but it turned out fine. And, the only important thing I was unable to reprogram afterwords was the S/N, but it doesn’t really matter to me. (Too bad the fingerprint scanner still doesn’t work though. That’s the only thing left that still isn’t working after all of this.)
Click to expand...
Click to collapse
I plan on testing every function to document what happens, so far I've done Refurbish, Partition DL, Dump, PDM and ChipErase. only Dump didn't work
Nice work fellas!!! Exciting to see some movement towards being able to root/development.
kaluna00 said:
Nice work fellas!!! Exciting to see some movement towards being able to root/development.
Click to expand...
Click to collapse
@KaptinBoxxi
BTW... How do you get to the hidden menu on the Verizon Varient?
kaluna00 said:
@KaptinBoxxi
BTW... How do you get to the hidden menu on the Verizon Varient?
Click to expand...
Click to collapse
I think its the same dial code. I don't have the device in front of me at the moment to say
I tried this earlier...
Post in thread 'LG Wing 5G Network option activation' https://forum.xda-developers.com/t/lg-wing-5g-network-option-activation.4285275/post-85116977
Am I using the wrong dial code for Verizon?
kaluna00 said:
I tried this earlier...
Post in thread 'LG Wing 5G Network option activation' https://forum.xda-developers.com/t/lg-wing-5g-network-option-activation.4285275/post-85116977
Am I using the wrong dial code for Verizon?
Click to expand...
Click to collapse
I have yet to have network work on my demo device regardless of what firmware is on it because my Serial Number and IMEI always come back at 0 and even if I manually enter new ones, it doesn't acivate, although i was able to get to the menu just fine with the standard code in that post.
Interesting, I wonder if there's something different in your firmware or kdz...
looking at the software version. mine is on
F100VM10i
maybe they (Verizon) patched out the hidden menu. your KDZ is labeled
F100VM10d
???
kaluna00 said:
looking at the software version. mine is on
F100VM10i
maybe they (Verizon) patched out the hidden menu. your KDZ is labeled
F100VM10d
???
Click to expand...
Click to collapse
I'm not sure what the final letter signifies, but F100V is verizon, yeah
KaptinBoxxi said:
I'm not sure what the final letter signifies, but F100V is verizon, yeah
Click to expand...
Click to collapse
think that represents the SW iteration identifier between updates... bit of a guess, but i believe that character has changed with updates.