Hi there,
after flashing an ebw version (since there seems to be no androind 10 ua version) on my v405ua i get this error/warning message everytime i boot up the phone, which says "current Version is not available for user. Can't find matched carrier. Check NT-Code ....."
How do i fix this Warning ? Since basically everything seems to work as usual, my lte wifi 5 etc. all work just fine. Except for when im in the NL i cant get an internet connection through the mobile network, is says something is wrong with my apn settings.
Help is much appreciated, and thanks in advance.
Gurkenbeat said:
Hi there,
after flashing an ebw version (since there seems to be no androind 10 ua version) on my v405ua i get this error/warning message everytime i boot up the phone, which says "current Version is not available for user. Can't find matched carrier. Check NT-Code ....."
How do i fix this Warning ? Since basically everything seems to work as usual, my lte wifi 5 etc. all work just fine. Except for when im in the NL i cant get an internet connection through the mobile network, is says something is wrong with my apn settings.
Help is much appreciated, and thanks in advance.
Click to expand...
Click to collapse
The NT-Error code thing has been discussed quite a bit, as it's very common to anyone that has cross-flashed. There are various things people have done and some have worked for some, but not others.
First, it's not a problem, it's just something that shows up when u boot up, after that it's inconsequential. *But*, I found that if I did a Lgup partition DL of the rom (that I wanted to cross flash to), let it boot up, then shut it off. Then do a 'Refurbish' with the exact same rom. Then I'd no longer have the NT-Error code show up.
As far as the mobile data goes, just verify what the apn settings should be, it may be as simple as that.
cheers
Would a "reflash" to an ua version solve the problem ?
for example there seems to be a verizon version of the 405ua available, would that solve the nt warning ?
Gurkenbeat said:
Would a "reflash" to an ua version solve the problem ?
for example there seems to be a verizon version of the 405ua available, would that solve the nt warning ?
Click to expand...
Click to collapse
No
AsItLies said:
The NT-Error code thing has been discussed quite a bit, as it's very common to anyone that has cross-flashed. There are various things people have done and some have worked for some, but not others.
First, it's not a problem, it's just something that shows up when u boot up, after that it's inconsequential. *But*, I found that if I did a Lgup partition DL of the rom (that I wanted to cross flash to), let it boot up, then shut it off. Then do a 'Refurbish' with the exact same rom. Then I'd no longer have the NT-Error code show up.
As far as the mobile data goes, just verify what the apn settings should be, it may be as simple as that.
cheers
Click to expand...
Click to collapse
Unfortunatley, this didn't work for me but I'm planning on LOS where the error goes away. I just wonder if this causes my SafetyNet to fail?
FreeSoftwareServers said:
Unfortunatley, this didn't work for me but I'm planning on LOS where the error goes away. I just wonder if this causes my SafetyNet to fail?
Click to expand...
Click to collapse
No, it doesn't cause safetynet to fail, they are completely different things.
AsItLies said:
The NT-Error code thing has been discussed quite a bit, as it's very common to anyone that has cross-flashed. There are various things people have done and some have worked for some, but not others.
First, it's not a problem, it's just something that shows up when u boot up, after that it's inconsequential. *But*, I found that if I did a Lgup partition DL of the rom (that I wanted to cross flash to), let it boot up, then shut it off. Then do a 'Refurbish' with the exact same rom. Then I'd no longer have the NT-Error code show up.
As far as the mobile data goes, just verify what the apn settings should be, it may be as simple as that.
cheers
Click to expand...
Click to collapse
What partitions do I select?
blowtorchhonor said:
What partitions do I select?
Click to expand...
Click to collapse
If you're doing a part D/L select all but ftm. After it reboots, go to Lgup mode again and do a 'refurbish' with the same kdz.
Most of the time that gets rid of the nt code thing.
cheers
AsItLies said:
If you're doing a part D/L select all but ftm. After it reboots, go to Lgup mode again and do a 'refurbish' with the same kdz.
Most of the time that gets rid of the nt code thing.
cheers
Click to expand...
Click to collapse
Thank you so much for the quick reply! I flashed to the latest OPEN_EU ROM and now I can't flash back to anything else, hopefully I don't have to if the NT message can be removed.
blowtorchhonor said:
Thank you so much for the quick reply! I flashed to the latest OPEN_EU ROM and now I can't flash back to anything else, hopefully I don't have to if the NT message can be removed.
Click to expand...
Click to collapse
I was unable to do a refurbish after the DL. It said unable to cross flash V405UA to V405. Message is still present.
blowtorchhonor said:
I was unable to do a refurbish after the DL. It said unable to cross flash V405UA to V405. Message is still present.
Click to expand...
Click to collapse
When u get that crossflash issue u have to use a different version of lgup. If you look in the 'guides' forum, there will be links to (I believe it's) ver 1.16, a newer version that will work with newer versions of the roms.
cheers
AsItLies said:
When u get that crossflash issue u have to use a different version of lgup. If you look in the 'guides' forum, there will be links to (I believe it's) ver 1.16, a newer version that will work with newer versions of the roms.
cheers
Click to expand...
Click to collapse
I was using an outdated common DLL, thanks for helping me! Let's see if this works!
blowtorchhonor said:
I was using an outdated common DLL, thanks for helping me! Let's see if this works!
Click to expand...
Click to collapse
Nope
I have this message that pops up on my V450VM. I assume it was related to Navigation Gestures that I used, and loved, on my V405QA7. When activating and setting it up, my V50 downloaded Nav Gestures from backup and when the phone updated to A11 I found the app was incompatible. I deleted the app and key. Ever since, rebooting has brought up the notification and I assume something didn't delete from the app. Guess I may have been wrong. I'm living with it and it doesn't seem to cause any issues but my OCD flares everytime :/
Related
So i have seen many guys charging a good amount of money for this, DFS is charging like 50$ per phone. Many guys are struggling to get thr phone working since they are unable to flash Akey/SPC which is needed for some carriers like Reliance, TATA in India atleast.
I'm not going to put usual diag setup stuff right now, or may not able to update it at all.
The below commands should be sent step by step as mentioned through DFS or CDMA workshop or any other tools which you prefer to use. Also you need to first send the 16 digit password for your phone model. I believe for L720 it is "2012112120131219"
----To change SPC to 000000 or any anything
00
4B13030000000000
4B130F006E766D2F6E756D2F383500
4B1308006E766D2F6E756D2F383500
4B13020041020000B60100006E766D2F6E756D2F383500
4B1305000000000000000000303030303030
4B13030000000000
Click to expand...
Click to collapse
In the second last line i.e. "4B1305000000000000000000303030303030", the last 12 digits are your SPC hex value, if you want to change it to anything else like 123456, you need to edit the last 12 digits and make it look like "4B1305000000000000000000313233343536"
----To change the A-Key to anything, in the below case, akey decimal to be flashed is 11111111133333333785 (the akey hex will be: 9A3298B4E238A719)
00
4B13030000000000
4B130F006E766D2F6E756D2F323500
4B1308006E766D2F6E756D2F323500
4B13020041020000B60100006E766D2F6E756D2F323500
4B130500000000000000000019A738E2B498329A
4B13030000000000
Click to expand...
Click to collapse
In the above cmds, if you take a close look at the last 16 characters in the 2nd last line and the mentioned akey hex, you maybe observe that the akey hex in the cmd is in a reverse manner. You can change generate your akey online or via regular tools like DFS and arrange it in the similar manner to flash. You might need to downgrade your modem in order to get this working, please post here if it works without downgrading the modem.
This has been tested on 2xGalaxy Victory and one Sprint L720, so please test and report if this works for you.
funkym0nk3y said:
Mods
if this has been posted in wrong section, then please pardon my ignorance and kindly move it to appropriate section.
Click to expand...
Click to collapse
Good write up. I flash phones and make tutorials. Some people on here claim they can do this and do that but, haven't written a clear guide yet on how to do it. Lol But, my guides are free and to the public.
Also this should be in the general section. Development is only for roms, etc.
as for resetting the SPC, you will need to downgrade the modem from MF9 to MDL or MDC... i have tried it with MF9 and didn't work...
thanks for sharing
PapaDocta said:
as for resetting the SPC, you will need to downgrade the modem from MF9 to MDL or MDC... i have tried it with MF9 and didn't work...
thanks for sharing
Click to expand...
Click to collapse
If you dont mind someone asking, how do you downgrade the modem? I tried to downgrade the complete os from samsung-udpates but nothing has worked for me.... any other suggestions??? thx in advance
to downgrade the modem just download the old modem's tar file and flash it via odin.. it should work without any problems
PapaDocta said:
to downgrade the modem just download the old modem's tar file and flash it via odin.. it should work without any problems
Click to expand...
Click to collapse
I actually tried that and still nothing! Maybe i just have a phone that wont take....? I have tried several os downgrades and last resort was the modem downgrade and still the same result: UNABLE TO USE THE 16 DIGIT PASSWORD TO ACCEPT ON WORKSHOP.....
I appreciate your input and help brother thx again.
If you're serious about flashing phones you should invest the proper amount of money, in the proper tools.
slawson said:
If you're serious about flashing phones you should invest the proper amount of money, in the proper tools.
Click to expand...
Click to collapse
TKS BRO
Thank you this is the only thing i have seen that has actually had some success, at least i did not get any errors but how do i know if the akey is in if i press read i just get a lot of cps errors. DOes the trial version of dfs not let you do anything in the cave ?
anyway thanks again hopefully this works.
Many parameters on a number of phones are write only, so you won't be able to read them.
flashing rom fear
So I got my phone working on my cdma carrier in Indonesia. But now I am concerned about flashing New roms esp using Odin and factory resetting. Will I lose my settings with a factory reset?
How do I flash roms and still keep my network settings?
Thanks
jarcher12 said:
So I got my phone working on my cdma carrier in Indonesia. But now I am concerned about flashing New roms esp using Odin and factory resetting. Will I lose my settings with a factory reset?
How do I flash roms and still keep my network settings?
Thanks
Click to expand...
Click to collapse
To answer my own question since nobody else did
Dont worry i just installed the one click mf9 rom and am now free of nags for reboot and the annoying register phone on sprint. very happy with the phone and its performance, blows my old epic out the water.
Hi,
did anyone try to change the akey for Sprint Note 3... ? N900P
thanks in advance...
Add to my Framily!!!!
A00275186Ak
Thank You!
jarcher12 said:
So I got my phone working on my cdma carrier in Indonesia. But now I am concerned about flashing New roms esp using Odin and factory resetting. Will I lose my settings with a factory reset?
How do I flash roms and still keep my network settings?
Thanks
Click to expand...
Click to collapse
Using cwm to flash another rom
Sent from my SPH-L720 using XDA Premium 4 mobile app
I have a Sprint SPH-L720. I tired to use the command 4B1305000000000000000000303030303030 it accepts it but responds back with a differnt command and the SPC doesn't change.
I did downgrade the baseband to both MDC and MDL with it still not working.
Any ideas how to change the SPC to 000000?
Been awhile but I thought I posted an update. Downgraded to the MDC modem and tired again and it solved my problem.
Thank you for the awesome post.
Using the command
please how will i make use of this command.
i am currently using Sprint SPH-L720T
any other methods of changing spc?
Okijaamaka said:
please how will i make use of this command.
i am currently using Sprint SPH-L720T
any other methods of changing spc?
Click to expand...
Click to collapse
You need a PC software such as DFS to send these command to your phone. You also have to enable diag mode in your phone before connecting it to the PC's USB.
rizapn said:
You need a PC software such as DFS to send these command to your phone. You also have to enable diag mode in your phone before connecting it to the PC's USB.
Click to expand...
Click to collapse
i have DFS but do you have step by step on how to connect it?
please. want to change my spc to 000000
Hi. I am in the UK and have the first gen moto x. i was dicking around with roms etc and i ended up accidentally erasing internal storage. I managed to the get the phone back to how it was apart from the fact that it cannot make calls, text, get 3g signal. it is essentially a small tablet. when i use the dialler code to show the imei number it is 0. i tried reinstalling modems etc and none have worked. i have tried differnet roms and even flashing lollipop. I am wondering if the modems files i am using are not working because they are US files and I need some kind of EU file? Idk.
I had my imei written down so i was going to try and change it to that on the phone but engineer tools does not open or even seem to exist on the phone. i cant try using the stock rom etc because it is on a site (something like sbf developers ) that says it is forbidden. i literally have tried everything. can anyone help? :crying:
azerouz said:
Hi. I am in the UK and have the first gen moto x. i was dicking around with roms etc and i ended up accidentally erasing internal storage. I managed to the get the phone back to how it was apart from the fact that it cannot make calls, text, get 3g signal. it is essentially a small tablet. when i use the dialler code to show the imei number it is 0. i tried reinstalling modems etc and none have worked. i have tried differnet roms and even flashing lollipop. I am wondering if the modems files i am using are not working because they are US files and I need some kind of EU file? Idk.
I had my imei written down so i was going to try and change it to that on the phone but engineer tools does not open or even seem to exist on the phone. i cant try using the stock rom etc because it is on a site (something like sbf developers ) that says it is forbidden. i literally have tried everything. can anyone help? :crying:
Click to expand...
Click to collapse
Hey! If you've installed a US ROM, you are using the wrong baseband files to access your service provider network ( XT1053- US ; XT1052- UK)
Try installing an XT1052 based rom and report back . Also, be careful while flashing your new chosen ROM. Ensure that it does not downgrade / modify your current bootloader as you may end up bricking your phone (since you've upgraded to LP)
Best of luck mate .
Bhargav4591 said:
Hey! If you've installed a US ROM, you are using the wrong baseband files to access your service provider network ( XT1053- US ; XT1052- UK)
Try installing an XT1052 based rom and report back . Also, be careful while flashing your new chosen ROM. Ensure that it does not downgrade / modify your current bootloader as you may end up bricking your phone (since you've upgraded to LP)
Best of luck mate .
Click to expand...
Click to collapse
Ty for the reply. I just tried flashing a rom for the 52 instead of the 53 and twrp gives an error message of "This package is for the device: xt1052 ghost, xt1052 ghost etc.. this device is ." the etc is just a couple more models but the device doesnt seem to know what it is? its saying becuase it is for the 52 it cannot install even though the device is the 52.
azerouz said:
Ty for the reply. I just tried flashing a rom for the 52 instead of the 53 and twrp gives an error message of "This package is for the device: xt1052 ghost, xt1052 ghost etc.. this device is ." the etc is just a couple more models but the device doesnt seem to know what it is? its saying becuase it is for the 52 it cannot install even though the device is the 52.
Click to expand...
Click to collapse
Strange . Do elaborate as to what rom you are flashing and which rom you are currently using (The one that has a problem).
Also, are you wiping the system before flashing ?
Bhargav4591 said:
Strange . Do elaborate as to what rom you are flashing and which rom you are currently using (The one that has a problem).
Also, are you wiping the system before flashing ?
Click to expand...
Click to collapse
Hi again. i googled xt1052 rom and found a few. the one i tried was cyanhacker(obviously based on cm). after i got that error i tried editing the updater script to skip over the process in which it checks what device it is on. after that it appeared to flash successfully but when i tried to boot it showed the bootloader unlocked screen, vibrated then restarted and just kept doing that bootloop.
azerouz said:
Hi again. i googled xt1052 rom and found a few. the one i tried was cyanhacker(obviously based on cm). after i got that error i tried editing the updater script to skip over the process in which it checks what device it is on. after that it appeared to flash successfully but when i tried to boot it showed the bootloader unlocked screen, vibrated then restarted and just kept doing that bootloop.
Click to expand...
Click to collapse
1. Please download the correct ROM for your device from here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
2. Head over here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 and follow the Instructions. CAUTION: If you decide yourself for manual flashing DO NOT PASTE THIS CODE:
Code:
fastboot oem config carrier vzw
Or you'll end up, like me: http://forum.xda-developers.com/moto-x/moto-x-qa/carrier-retail-devices-t3174988
In case I could help you with some guidance, I would be happy, if you could help me, in my thread.
//EDIT: Your battery should be on 70% or more, before you try to do anything! Keep this in mind, else flashing could be interrupted!
Kind regards
Xanthales said:
1. Please download the correct ROM for your device from here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
2. Head over here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 and follow the Instructions. CAUTION: If you decide yourself for manual flashing DO NOT PASTE THIS CODE:
Code:
fastboot oem config carrier vzw
Or you'll end up, like me: http://forum.xda-developers.com/moto-x/moto-x-qa/carrier-retail-devices-t3174988
In case I could help you with some guidance, I would be happy, if you could help me, in my thread.
//EDIT: Your battery should be on 70% or more, before you try to do anything! Keep this in mind, else flashing could be interrupted!
Kind regards
Click to expand...
Click to collapse
Thankyou so much. did what you said. tinkered in twrp. flashed a lollipop rom and made a call. My man right here <3
azerouz said:
Thankyou so much. did what you said. tinkered in twrp. flashed a lollipop rom and made a call. My man right here <3
Click to expand...
Click to collapse
No problem, im glad to hear, that I could help you!
Maybe you can help me here?: http://forum.xda-developers.com/moto-x/moto-x-qa/carrier-retail-devices-t3174988
This would be awesome, if you got a retail device!
Hello everyone,
Im new at Rooting, but I'm good at following instruction from videos, forums, and whatever I get my hands on. I have an LG G4, that I recently rooted. There are some issue with Root, and some applications I cant run (like snapchat- I had tried with Rootswitcher and Magisk but failed).
I followed instructions from several videos and forums here at Xda-Devs. But nothing seems to work. I have download multiple firmwares but everytime i get an error. the lgflashtool14 goes up to 9 % and there is some logs in my phone, but everything stops.
Also I want to mentioned that this are the steps that i rooted
Please any help will be appreciated, I want to go back to stock. :fingers-crossed:
Edit : I have tried all variants of the firmware, some they not even get stuck they say " contact administrator "
An3ru said:
Hello everyone,
Im new at Rooting, but I'm good at following instruction from videos, forums, and whatever I get my hands on. I have an LG G4, that I recently rooted. There are some issue with Root, and some applications I cant run (like snapchat- I had tried with Rootswitcher and Magisk but failed).
I followed instructions from several videos and forums here at Xda-Devs. But nothing seems to work. I have download multiple firmwares but everytime i get an error. the lgflashtool14 goes up to 9 % and there is some logs in my phone, but everything stops.
Also I want to mentioned that this are the steps that i rooted
Please any help will be appreciated, I want to go back to stock. :fingers-crossed:
Edit : I have tried all variants of the firmware, some they not even get stuck they say " contact administrator "
Click to expand...
Click to collapse
why flash other variants? what phone you have,?? why use flashtools and not LGUP try LGUP.
raptorddd said:
why flash other variants? what phone you have,?? why use flashtools and not LGUP try LGUP.
Click to expand...
Click to collapse
Hey Raptorddd,
I have a LG G4 h811. And i been trying using LGUp but when i plug my phone under model it says "unlnown". I been trying to fix with but with no solution. Well other t mobile variants i meant there are like 4 out there and i have different errors.
An3ru said:
Hey Raptorddd,
I have a LG G4 h811. And i been trying using LGUp but when i plug my phone under model it says "unlnown". I been trying to fix with but with no solution. Well other t mobile variants i meant there are like 4 out there and i have different errors.
Click to expand...
Click to collapse
then i think its not a h811. open up phone and take motherborad out see what it says on the actual motherboard in your hand, what ever it says flash that, maybe is not a h811
raptorddd said:
then i think its not a h811. open up phone and take motherborad out see what it says on the actual motherboard in your hand, what ever it says flash that, maybe is not a h811
Click to expand...
Click to collapse
Hey man, I followed your instructions, and in one side of the motherboard says, EAX #####501_h810_main_1.0. Would that be the firmware im looking for.??
*edit : its weird since I look up the H810 is a ATT, but I got this Phone in Tmobile
*edit 2: by dialing *#*#244773825625#*#* it gives me this - HW version Rev1.0 - Factory Version LGH811AT-01-V20r-310-260-jan-11-2017-arb03-SW ORIGINAL VERSION *same as the factory version*- Anti rollback version 3-
An3ru said:
Hey man, I followed your instructions, and in one side of the motherboard says, EAX #####501_h810_main_1.0. Would that be the firmware im looking for.??
*edit : its weird since I look up the H810 is a ATT, but I got this Phone in Tmobile
*edit 2: by dialing *#*#244773825625#*#* it gives me this - HW version Rev1.0 - Factory Version LGH811AT-01-V20r-310-260-jan-11-2017-arb03-SW ORIGINAL VERSION *same as the factory version*- Anti rollback version 3-
Click to expand...
Click to collapse
go by what the motherboard says.. if you got it from tmobile return it.
yes seems yours its a att 810
motherboard is what determines your variant other things can be edited but not that number and printing on mitherboard
yes weird they might be refurbishing phone using other motherboards
raptorddd said:
then i think its not a h811. open up phone and take motherborad out see what it says on the actual motherboard in your hand, what ever it says flash that, maybe is not a h811
Click to expand...
Click to collapse
Well I got it more than a year, unfortunately. Also I tried LGup and it gets the port and what software Im using, But model says unknown. I want to select the phone, but first i have to select the model, is there any fix in this situation?!
raptorddd said:
go by what the motherboard says.. if you got it from tmobile return it.
yes seems yours its a att 810
motherboard is what determines your variant other things can be edited but not that number and printing on mitherboard
yes weird they might be refurbishing phone using other motherboards
Click to expand...
Click to collapse
Ok, but i might not be able to return it since its past the year. And with LGup I open the software and states that MODEL "unknown" and gets the COM port and the software im runing in a small window. Is there any fix for it, that you know of?.
An3ru said:
Well I got it more than a year, unfortunately. Also I tried LGup and it gets the port and what software Im using, But model says unknown. I want to select the phone, but first i have to select the model, is there any fix in this situation?!
Click to expand...
Click to collapse
do you have the h810 KDZ .? not sure i can help much more.. maybe try in the KDZ go back to stock thread or do search..
or try updating this files
https://forum.xda-developers.com/showpost.php?p=73631178&postcount=931
raptorddd said:
do you have the h810 KDZ .? not sure i can help much more.. maybe try in the KDZ go back to stock thread or do search..
or try updating this files
https://forum.xda-developers.com/showpost.php?p=73631178&postcount=931
Click to expand...
Click to collapse
I have it, but I attempt to flash it with lgflashtools and still stuck at 9%. Also tried LGup, and still im unable to do anything with that program
Hi, I don't remember exactly when this started, but its been a few months. Pretty much when I go to my wifi settings one of the available wifi networks is named "WiFi NVRAM WARNING err 0x10". By now its obvious its something about the phone and not an actual network, but what is causing this and is there a way to fix this? Thanks!
lil chickenz said:
Hi, I don't remember exactly when this started, but its been a few months. Pretty much when I go to my wifi settings one of the available wifi networks is named "WiFi NVRAM WARNING err 0x10". By now its obvious its something about the phone and not an actual network, but what is causing this and is there a way to fix this? Thanks!
Click to expand...
Click to collapse
This is from a lost or corrupted nvram data.
Is you phone imei correct?
How do I check if it's correct?
I used some online thing and it looked normal except it said it was for r1 hd 2018 and I bought mine in 2017. Does that matter?
lil chickenz said:
How do I check if it's correct?
Click to expand...
Click to collapse
the numbers are on the box the phone came in , And on stick that covers the battery.
I did just mean that it had numbers and not all 000
Are you on one of the stock roms, or some custom one?
Yeah it was a bunch of numbers so normal, and im not using the rom that came with the phone but I'm using a stock one another user posted
The original 6.1 from here https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
mrmazak said:
the numbers are on the box the phone came in , And on stick that covers the battery.
I did just mean that it had numbers and not all 000
Are you on one of the stock roms, or some custom one?
Click to expand...
Click to collapse
I also ran the debloat script but I don't think it should matter
lil chickenz said:
I also ran the debloat script but I don't think it should matter
Click to expand...
Click to collapse
I had only seen this issue after "format all" was done in spft. or when testing some Lineage ports. And on the posts it only happened with a phone that used my bootloader roll-back script.
Did you do the bootloader roll-back?
If so , will need to search back in the forum to see when this was posted and what fix i used.
this was post i was refering to. Not sure if it is gonna be same or similar to your current issue, but read it and perhaps give it a try. But remember any thing you modify can break your device further or fix it, There are no guarantees here .
https://forum.xda-developers.com/showpost.php?p=73231462&postcount=99
Hello all, been a little while with LG V40 as my second device, and loved it so much but tried to follow the crossflash procedures as mentioned here:
https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and I succeeded with it, only few notes wanted to share as experience/question about them:
- wifi, 3G and 4G are working as it should and no other problem found.
1. after flashing, phone booted successfully to Android 10, giving strange error message :
"WARNING!
Current version is not available for user. Can't find matched carrier. Check NT-Code: 310410310150 310170,311180,310560,310030,3 10280,310950,313100,312670: FF,FF,FF,FF,FF,FF,FF,FF,FF,FF
2. there's no SN for the phone in the settings!
- attached some screenshots for errors, looking forward to seeing some feedback or help if possible with how to fix those problems.
thanks in advance for all for such great efforts done here.
Hi, possible remove simlock after crossflash? Thanks.
P.S.
To remove message "WARNING!
Current version is not available for user. Can't find matched carrier......"
You must have root and edit file cust_path_mapping.cfg
77an said:
Hi, possible remove simlock after crossflash? Thanks.
P.S.
To remove message "WARNING!
Current version is not available for user. Can't find matched carrier......"
You must have root and edit file cust_path_mapping.cfg
Click to expand...
Click to collapse
thank you so much, i overcome it by crossflashing the latest EU Android 10.
and, about sim lock, it can't be done with cross flashing.
abokamel said:
thank you so much, i overcome it by crossflashing the latest EU Android 10.
and, about sim lock, it can't be done with cross flashing.
Click to expand...
Click to collapse
Can you share the rom that you use?
Also, were you root?
oscarillo said:
Can you share the rom that you use?
Also, were you root?
Click to expand...
Click to collapse
no, it's stock, not rooted.
the current rom i use now is here
abokamel said:
no, it's stock, not rooted.
the current rom i use now is here
Click to expand...
Click to collapse
Thanks a lot for your reply.
One more question.
Did you do a Refurbish or Upgrade option?
oscarillo said:
Thanks a lot for your reply.
One more question.
Did you do a Refurbish or Upgrade option?
Click to expand...
Click to collapse
used the command line, i think it's making refurbish
This is a bit of an older thread, but just recently did the same crossflash from pie on att device to korean open Q.
Decided on the KR instead of EBW because KR, I thought, had more of the t-mo LTE bands I needed. Unfortunately, the different sites with firmware specs aren't always accurate (which LTE bands supported). One site has EBW supporting every LTE band of every LG phone! Def inaccurate.
So I tested both EBW and KR Q versions. Use LTE Discovery (from playstore) to view LTE bands in your current location. One thing to note about that, the LTE bands it shows u are going to be the nearest towers it's using. Which means that another tower, a little farther away, won't show up.
So to verify a particular band, that you think the phone might be capable of, but you aren't sure, you have to go into the svc menu and select 'field test' and enable only that LTE band you're searching for. Then use LTE Discovery and see if it's connected with that band. If it isn't connected with it (usually it will default to a 3G band if that one u selected isn't available), that means 2 things; 1) either that band isn't used in your area 2) Your device doesn't support that band (or both 1 and 2).
But in my case, I know band 71 works in my area (from previous testing), but I have to select enable for only that band for it to show up, because other nearby towers with band 66 will 'drown it out'.
Thus, the point here, the KR firmware Band 71 **DOES WORK**. And, btw, no site indicates it included in supported bands. The following screenshot shows it connected to 71 and the KR 409 at the bottom.
Cheers
abokamel said:
Hello all, been a little while with LG V40 as my second device, and loved it so much but tried to follow the crossflash procedures as mentioned here:
https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and I succeeded with it, only few notes wanted to share as experience/question about them:
- wifi, 3G and 4G are working as it should and no other problem found.
1. after flashing, phone booted successfully to Android 10, giving strange error message :
"WARNING!
Current version is not available for user. Can't find matched carrier. Check NT-Code: 310410310150 310170,311180,310560,310030,3 10280,310950,313100,312670: FF,FF,FF,FF,FF,FF,FF,FF,FF,FF
2. there's no SN for the phone in the settings!
- attached some screenshots for errors, looking forward to seeing some feedback or help if possible with how to fix those problems.
thanks in advance for all for such great efforts done here.
Click to expand...
Click to collapse
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
You need to have root access to so you can open your /oem/OP/cust_path_mapping.cfg and a hex editor. I use HxD.
Write down the number you have in the beginning, in my case "FFFFFF,60"
Reboot into 9008, open QFil and backup your FTM by choosing "READ" option
File will be stored at C:\Users\User\AppData\Roaming\Qualcomm\QFIL\COMPORT_9
Rename file to FTM_original.bin and open in HxD
Press ctrl + G to go to offset 14000
and replace first section with number you wrote down from cust_path_mapping earlier while deleting everything after
Also, if you're missing a serial number you can add that in as well, located at offset 12000 in the FTM file
Replace the red FFFFFFFFFFFFFF with your serial #
Once done, hit "SAVE AS" so you have a backup of the original if things go wrong and rename to FTM_fixed.bin
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
advancedtekniqs said:
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
<snip brevity>
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
Click to expand...
Click to collapse
Wow thanks for that. First I've seen this idea to fix that issue. Other methods didn't work. Will try soon.
There are some other values you can change in cust.prop that can help also. Get's rid of most of the KR language in unexpected places. Will jot them down and add them here shortly.
cheers
AsItLies said:
Wow thanks for that. First I've seen this idea to fix that issue. Other methods didn't work. Will try soon.
There are some other values you can change in cust.prop that can help also. Get's rid of most of the KR language in unexpected places. Will jot them down and add them here shortly.
cheers
Click to expand...
Click to collapse
I've only been using this rom for about 6 hours. I haven't really noticed any KR except on the phone dialer. Doesn't really bother me, but if you have a way to set that to ENG, I'd like to know as well.
advancedtekniqs said:
I've only been using this rom for about 6 hours. I haven't really noticed any KR except on the phone dialer. Doesn't really bother me, but if you have a way to set that to ENG, I'd like to know as well.
Click to expand...
Click to collapse
Yes u need to change the cust.prop in OP. Change the target region country to US (from KR) and same for target country. Change language prop to en_US.
Additionally, change featureset prop to OPENUS from OPENKR.
these changes disable most KR elements in firmware, most noticeably dual clock and call recording in dialer. They **may** also enable volte if supported by carrier.
This is from nice guy Neo on tele group who's played with this much more than I have
Cheers
Oh yeah, lol, just remembered, the main reason I was asking for the info above was to get the 'field test' selection (so you can select LTE bands) in the SVC Menu from dialer. By default, it doesn't show up, but above changes fixes that also.
advancedtekniqs said:
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
You need to have root access to so you can open your /oem/OP/cust_path_mapping.cfg and a hex editor. I use HxD.
Write down the number you have in the beginning, in my case "FFFFFF,60"
Reboot into 9008, open QFil and backup your FTM by choosing "READ" option
File will be stored at C:\Users\User\AppData\Roaming\Qualcomm\QFIL\COMPORT_9
Rename file to FTM_original.bin and open in HxD
Press ctrl + G to go to offset 14000
and replace first section with number you wrote down from cust_path_mapping earlier while deleting everything after
Also, if you're missing a serial number you can add that in as well, located at offset 12000 in the FTM file
Replace the red FFFFFFFFFFFFFF with your serial #
Once done, hit "SAVE AS" so you have a backup of the original if things go wrong and rename to FTM_fixed.bin
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
Click to expand...
Click to collapse
thank you so much for sharing such detailed fix for that strange problem., as a work around, I managed to flash OPEN US kdz, then reflashed the open KR, then it's gone now, but i can't find mt phone's serial number when showing it on settings.
thanks again for such amazing tutorial. keep up
AsItLies said:
Yes u need to change the cust.prop in OP. Change the target region country to US (from KR) and same for target country. Change language prop to en_US.
Additionally, change featureset prop to OPENUS from OPENKR.
these changes disable most KR elements in firmware, most noticeably dual clock and call recording in dialer. They **may** also enable volte if supported by carrier.
This is from nice guy Neo on tele group who's played with this much more than I have
Cheers
Oh yeah, lol, just remembered, the main reason I was asking for the info above was to get the 'field test' selection (so you can select LTE bands) in the SVC Menu from dialer. By default, it doesn't show up, but above changes fixes that also.
Click to expand...
Click to collapse
that's terrific and brilliant to be honest! thank you so much for information you shared.
So, just found something additional that works on open 409N. The 'buffer fix' can be a bit of a pain. Tried a magisk module supposedly for v40 Q but that didn't work. So did what I've done before and just copy the .so fix to the appropriate directory, but that didn't work, even the oem camera stopped working after that.
So, even though this says it's for 'custom roms' tried it, and boom, works in magisk and does what's needed to fix buffer.
cheers
abokamel said:
thank you so much for sharing such detailed fix for that strange problem., as a work around, I managed to flash OPEN US kdz, then reflashed the open KR, then it's gone now, but i can't find mt phone's serial number when showing it on settings.
thanks again for such amazing tutorial. keep up
Click to expand...
Click to collapse
Try this website to find your seriel# by IMEI
So, interesting updates, for anyone using this Rom.
I went back to my AT&T rom, android 9. Then, just a few hours later... decided to go back to KR Open Don't ask, it's too confusing
But, the point, this time, when flashing the KR rom, I did part DL, and then after booting did Refurbish. Had read on tele that doing that fixes some of the issues crossflashing causes. Sure enough, my NT-code issue went away (couldn't fix that even with hexedit of ftm)!
So, that was cool. But now, my S/N disappeared! IMEI was still okay though. So tried the hexedit ftm and added S/N, boom, now it's fine also. But the funny thing was, with the refurbish and no NT-code problem, I looked at what was in the newer ftm at that address, and it had nothing, no info at that address at all.
One thing to be aware of, attesting to why this is difficult to deal with, these values (IMEI, S/N - and others) get propagated from one partition to another, I don't know the chain of events or criteria involved, but it adds to the difficulty of trying to fix issues. Which specific place it looks for something is confusing also, and if it's doing compares of 2 or more places is a mystery.
But anyway, do a Part DL to crossflash, then do a Refurb and it appears to fix some of the issues.
cheers
Awesome work, fellas!
What program and files do you all have success with during the flashing? Perhaps share a link to it?
Also, is a serial number necessary? For using the phone and having service? Seems you guys are taking the blank serial number very seriously. Thanks!
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
AsItLies said:
But anyway, do a Part DL to crossflash, then do a Refurb and it appears to fix some of the issues.
cheers
Click to expand...
Click to collapse
So for an old sprint v40 running oreo, Just crossflash to the korean Q rom via partition DL, then again, with Refurb option? Or swap between different roms? Haven't done any crossflashing yet..hoping to avoid errors. Serial number loss won't stop the phone from working, right?
fireblade20 said:
Awesome work, fellas!
What program and files do you all have success with during the flashing? Perhaps share a link to it?
Also, is a serial number necessary? For using the phone and having service? Seems you guys are taking the blank serial number very seriously. Thanks!
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
So for an old sprint v40 running oreo, Just crossflash to the korean Q rom via partition DL, then again, with Refurb option? Or swap between different roms? Haven't done any crossflashing yet..hoping to avoid errors. Serial number loss won't stop the phone from working, right?
Click to expand...
Click to collapse
Mine is an AT&T, but afaik, Sprint should be the same. Yes, do the part DL, let it reboot as normal, then shut off and do refurb. Is S/N a big deal? no, everything works, and the S/N is still in the phone, just not displaying properly. It's an individual thing how much effort you put into fixing that. Some people have lost either / or IMEI or dual IMEI (some roms have that), when cross flashing. That's a problem because they get no cell signal, but that's on a different rom.
Look in this thread for how to LGUP / crossflash.
cheers
Thanks man!