Related
HI, How are you all ..
i am new here, last monday i bought xperia x1.
Now the Problem is I am unable to send Text Message (sms) I write message and send but after some time message appear " your message cannot be sent " I Check my Sim Card and try to another mobile and work fine,.. Only Problem in Xperia X1..
Only SMS Problem..
other function work fine,,,
Please solve my problem give me idea or suggestion or any trick
dukhi said:
HI, How are you all ..
i am new here, last monday i bought xperia x1.
Now the Problem is I am unable to send Text Message (sms) I write message and send but after some time message appear " your message cannot be sent " I Check my Sim Card and try to another mobile and work fine,.. Only Problem in Xperia X1..
Only SMS Problem..
other function work fine,,,
Please solve my problem give me idea or suggestion or any trick
Click to expand...
Click to collapse
1st: welcome to xda
I understand you are still on stock rom, did you install other apps? always helpful to add as many details as possible
did you update to latest version via SEUS?
read here and compare your settings
then i read somewhere a hard reset would help (will restore default settings), consider it
cheers
reply`
Thank you sir for reply
Actuelly i am using Windows Mobile first time i dont know about Rom. and i never upgrade mobile..
Last night i reset everything from
Setting --> System --> Clear Storage and enter password 1234 then mobile restart and everything come to default..
So please help me step by step because am new to window mobile.
am very thank full to you.
s
Nobody reply me
100 people view this page but only 1 answer .. no anyone here for help me. bye
don't get impatient and discouraged so fast, the response time is always variable
maybe you get an answer within minutes, maybe you don't get one for various reasons, help here is still optional and not mandatory, that's as it is
some here even have a real life
are you able to connect to internet in general, browse, read, whatever and only SMS don't work or is there a general connection setup problem? I would check that first (if not already done)
do you have a new X1? any idea about installed firmware (aka stock rom, when from SE)?
second thing you should consider is SEUS - the SE Update Service, you dl part of the connect software to your pc (go to SE home, support, select X1, ->update service, dl application) which then enables you to connect to SEUS
try to update to the latest firmware and retry sensing an sms
then drop some feedback
cheers
DrakenKorin said:
don't get impatient and discouraged so fast, the response time is always variable
maybe you get an answer within minutes, maybe you don't get one for various reasons, help here is still optional and not mandatory, that's as it is
some here even have a real life
are you able to connect to internet in general, browse, read, whatever and only SMS don't work or is there a general connection setup problem? I would check that first (if not already done)
do you have a new X1? any idea about installed firmware (aka stock rom, when from SE)?
second thing you should consider is SEUS - the SE Update Service, you dl part of the connect software to your pc (go to SE home, support, select X1, ->update service, dl application) which then enables you to connect to SEUS
try to update to the latest firmware and retry sensing an sms
then drop some feedback
cheers
Click to expand...
Click to collapse
Dear when i update the phone the following error appear !
Code:
The Phone contain manipulated software and is not supported by this application
i am not understand,,,
dukhi said:
Dear when i update the phone the following error appear !
Code:
The Phone contain manipulated software and is not supported by this application
i am not understand,,,
Click to expand...
Click to collapse
I should have asked earlier: is it a used X1? somehow doesn't sound like new...
search for software information, e.g under start - settings - system - about device (location depends on firmware version) and tell me what you find
get the device into bootloader and tell me what's displayed there, sounds like you are not on stock rom anymore
cheers
One simple thing. Did you check the sms service number? Its easy to forget this because nowadays it is common for smartphones (and dumb phones too) to get this number automatically from the sim card. Nonetheless I would check it to make sure you dont fall victim to such a basic detail. You can check it here: Phone\Settings\Services\Mailbox and SMS\
You can look for the correct number on your carrier's website (or you call them).
hello dear friends....I had some strange issue 2 days ago...my apps settings restore to time that I just installed them....
i would to hard reset my phone and it was a good time to doing it...so I did hard reset but after it another problem,call and SMS didn't work....some strange problems,so I Task 29 my phone but it hang on SE logo....
No way,I tried to SEUS my phone and this error appeared....
The Phone contain manipulated software and is not supported by this application
what I suppose to do???
First of all: Don't mess around with things like task 29 if you don't know what they actually do. Task 29 completely erases the rom section of your phone so it's no suprise your phone is no longer able to boot. Now you have to flash another rom in order to use your phone again.
Another remark, the fact that you use tools like task 29 and afterwards you try to use SEUS only confirms that you have no clue what you're actually doing. SEUS only works with original software, as soon as you change to a custom rom or even if you only install hard spl SEUS won't work anymore. So you need to read the corresponding tutorials (hard spl, back to spl, custom roms, task 29) and either get it done the right way or reverse to stock spl and rom. Good luck.
tnx dear friend for ur compelete answer,U are right,my mistake and I appriciate for ur guidence....
I have installed another ROM from SDcard and my problem is solved now,tnx again.....
Hi,
I installed the French ftf from the other thread and now I get the Storefront App (That I am not able to uninstall) starting a Screen-Demonstration Video everytime the screen is turned off or locks. I can temporarily disable the Service, but it just starts up again. Would one of you be so kind to use the Sony Update Service to get his/her flash files (I know, that this will wipe the device, but maybe some of you already backed up their files and just haven't posted them yet or just want to reset their device anyway.) like this.
Thank you, your help is much appreciated.
lowtraxx
lowtraxx said:
Hi,
I installed the French ftf from the other thread and now I get the Storefront App (That I am not able to uninstall) starting a Screen-Demonstration Video everytime the screen is turned off or locks. I can temporarily disable the Service, but it just starts up again. Would one of you be so kind to use the Sony Update Service to get his/her flash files (I know, that this will wipe the device, but maybe some of you already backed up their files and just haven't posted them yet or just want to reset their device anyway.) like this.
Thank you, your help is much appreciated.
lowtraxx
Click to expand...
Click to collapse
this used to be fixed by dialing *#*#73556673#*#*
Yep, dial *#*#SELLMORE#*#* and it'll go away.
Sent from my C6603 using xda premium
Thank you very much, that worked. Nonetheless would it be nice to have a Generic unbranded UK/DE non-Storefront Firmware so I let the post open for now.
lowtraxx said:
Thank you very much, that worked. Nonetheless would it be nice to have a Generic unbranded UK/DE non-Storefront Firmware so I let the post open for now.
Click to expand...
Click to collapse
Just so you know, all Xperia firmwares contain the retail demo software, they always have There is only one "special" firmware this time around (from the demo units) and it can't be recovered through EMMA, PCC or Update Service yet so we can't create an FTF - and even that special firmware doesn't actually have anything different.
It's really funny to do to friends though, while they're not looking go *#*#SELLMORE#*#* and watch them freak out
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!
I have read through many posts here in the forum, where I got some tips that I have tried, but nothing that totally applied to my problem, only parts of it. I have upgraded my phone with every firmware of the Open_EU since January 2020 without any problem using LGUP. Last time I upgraded to Android 10 in August, it was also successful but then check nt-code: 222201: ff started to appear everytime I turned on the phone. It's annoying, but not a big problem since the phone works perfect. However I tried to upgrade to Android 10 v405ebw30c recently, and now LGUP can't make the upgrade, it says can't cross-DL, with a strange message judypn_lao_eea ->judypn_lao_com. Could the NT-code be the cause of this? I also tried to enter the hidden menu, *#546368#*405# and I can see the nt code, but I can't change it. Nothing happens. Will I have to root my phone to make this work? or are there other options?
Some history, this phone doesn't officially exist in Sweden, where I live. However, it's possible to buy it anyway. It was sold as brand new and unlocked. The first week I discovered that I couldn't make the officially update . Then I found out it's originally italian (TIM), and probably someone that unlocked afterwards. But maybe not properly made since it was problem to make upgrades with LG Bridge. And when I succefully managed to make the upgrade with LGUP I decided to keep the phone anyway, because I liked it too much. But since this NT code started to appear after the Android 10 upgrade, I wondered if maybe there's some "leftovers" from TIM italy. So is rooting the only option for me? Except for the upgrade problems it works perfect every day.
suain81 said:
I have read through many posts here in the forum, where I got some tips that I have tried, but nothing that totally applied to my problem, only parts of it. I have upgraded my phone with every firmware of the Open_EU since January 2020 without any problem using LGUP. Last time I upgraded to Android 10 in August, it was also successful but then check nt-code: 222201: ff started to appear everytime I turned on the phone. It's annoying, but not a big problem since the phone works perfect. However I tried to upgrade to Android 10 v405ebw30c recently, and now LGUP can't make the upgrade, it says can't cross-DL, with a strange message judypn_lao_eea ->judypn_lao_com. Could the NT-code be the cause of this? I also tried to enter the hidden menu, *#546368#*405# and I can see the nt code, but I can't change it. Nothing happens. Will I have to root my phone to make this work? or are there other options?
Some history, this phone doesn't officially exist in Sweden, where I live. However, it's possible to buy it anyway. It was sold as brand new and unlocked. The first week I discovered that I couldn't make the officially update . Then I found out it's originally italian (TIM), and probably someone that unlocked afterwards. But maybe not properly made since it was problem to make upgrades with LG Bridge. And when I succefully managed to make the upgrade with LGUP I decided to keep the phone anyway, because I liked it too much. But since this NT code started to appear after the Android 10 upgrade, I wondered if maybe there's some "leftovers" from TIM italy. So is rooting the only option for me? Except for the upgrade problems it works perfect every day.
Click to expand...
Click to collapse
I'm not sure, but worth a try,I warn the site is Russian, here's how to edit NT code https://4pda.ru/forum/index.php?showtopic=951883&view=findpost&p=100635159 here is a list of NT codes:View attachment NT_code.txtunfortunately needed root!working with QFIL do backup ftm.bin!
lexih said:
I'm not sure, but worth a try,I warn the site is Russian, here's how to edit NT code here is a list of NT codes:View attachment 5134107unfortunately needed root!
Click to expand...
Click to collapse
Thank you for your reply. Yes, I have read many instructions even on this page how to edit, cust_path_mapping.cfg, and that it's surely easy once the phone is rooted. But that's why I first wanted to see the possibilities to do this without that I have to root the phone.
suain81 said:
I have read through many posts here in the forum, where I got some tips that I have tried, but nothing that totally applied to my problem, only parts of it. I have upgraded my phone with every firmware of the Open_EU since January 2020 without any problem using LGUP. Last time I upgraded to Android 10 in August, it was also successful but then check nt-code: 222201: ff started to appear everytime I turned on the phone. It's annoying, but not a big problem since the phone works perfect. However I tried to upgrade to Android 10 v405ebw30c recently, and now LGUP can't make the upgrade, it says can't cross-DL, with a strange message judypn_lao_eea ->judypn_lao_com. Could the NT-code be the cause of this? I also tried to enter the hidden menu, *#546368#*405# and I can see the nt code, but I can't change it. Nothing happens. Will I have to root my phone to make this work? or are there other options?
Some history, this phone doesn't officially exist in Sweden, where I live. However, it's possible to buy it anyway. It was sold as brand new and unlocked. The first week I discovered that I couldn't make the officially update . Then I found out it's originally italian (TIM), and probably someone that unlocked afterwards. But maybe not properly made since it was problem to make upgrades with LG Bridge. And when I succefully managed to make the upgrade with LGUP I decided to keep the phone anyway, because I liked it too much. But since this NT code started to appear after the Android 10 upgrade, I wondered if maybe there's some "leftovers" from TIM italy. So is rooting the only option for me? Except for the upgrade problems it works perfect every day.
Click to expand...
Click to collapse
So, u have 2 problems right? u want to upgrade to v405ebw30c, but can't, and you also have the nt-code error right?
First, no, they aren't related. I think that's highly unlikely. That's not something lgup checks for. I'd bet you're using the 1.14 version dll and should be using the 1.16 dll and should be doing a refurbish.
As far as the nt-code error. It's a pain, lots and lots of info about fixing it, most of them need root. But here's what worked for me, no root needed: I switched from att pie to Korean open Q (first time had the nt-error and no editing anything would fix it), so went back to att and then did the korean 409N again, first with partition DL. Let that finish, it has to reboot the phone completely to finish. Then, don't change the phone in anyway, just shut it off. Back to LGUP and do a Refurbish with the same kdz.
No more nt-error code. It *seems* that nt-error code info gets propagated to various partitions as a part of refurbish. I verified that the ftm partition, where that information lives, was completely spaces (blank) after the refurbish... it's odd, I know. But for whatever reason, I no longer have the nt-error code problem.
cheers
AsItLies said:
So, u have 2 problems right? u want to upgrade to v405ebw30c, but can't, and you also have the nt-code error right?
First, no, they aren't related. I think that's highly unlikely. That's not something lgup checks for. I'd bet you're using the 1.14 version dll and should be using the 1.16 dll and should be doing a refurbish.
As far as the nt-code error. It's a pain, lots and lots of info about fixing it, most of them need root. But here's what worked for me, no root needed: I switched from att pie to Korean open Q (first time had the nt-error and no editing anything would fix it), so went back to att and then did the korean 409N again, first with partition DL. Let that finish, it has to reboot the phone completely to finish. Then, don't change the phone in anyway, just shut it off. Back to LGUP and do a Refurbish with the same kdz.
No more nt-error code. It *seems* that nt-error code info gets propagated to various partitions as a part of refurbish. I verified that the ftm partition, where that information lives, was completely spaces (blank) after the refurbish... it's odd, I know. But for whatever reason, I no longer have the nt-error code problem.
cheers
Click to expand...
Click to collapse
Thank you for your reply. No I don't know if they're related either, it was just a guess since the problems started at the same time. Well, I always had a kind of "problem" since I never have been able to upgrade from LG Bridge. And that I guess is from the NT-code. But the sign in the start appeared after the Android 10 upgrade. However, I'm using LGUP 1.16.0.3 and I have used it everytime, with DLL version 1.9.39.7.
And actually it wouldn't bother me too much having this sign in the start anyway, I only restart the phone like once per week. But of course it bothers me that I can't make the upgrade like before. And I can also mention that I have never tried to refurbish with LGUP, only upgrades, because I have some bank apps etc. that are a bit complicated to reinstall. Of course it's possible, but I have to be mentally prepared for it. So I'll only do that when I know there's no other option. And the phone work good today, so I'm not in a rush, but in a couple of months I should be doing an upgrade of course.
And thanks for telling me the other option too, I will surely try it one day but since it also requires refurbish I will try after I fail to make the normal refurbish.
I don't have any experience of rooting, if I root my phone, will I keep all the data or is it comparable to refurbish? Are the any other risks rooting the phone? I'll lose the warranty, but I don't really have the warranty anyway since it's not an official product in my country.
suain81 said:
I don't have any experience of rooting, if I root my phone, will I keep all the data or is it comparable to refurbish? Are the any other risks rooting the phone? I'll lose the warranty, but I don't really have the warranty anyway since it's not an official product in my country.
Click to expand...
Click to collapse
No, to root, you loose all data and have to start again. Part of rooting is to flash dm-verity which turns off encryption. But, that allows you to do a backup of the data partition once you've reinstalled everything. The positive side there is that in the future, you could back up that partition (data), make any other changes, then flash data back, and your apps would be back as they were.
Other risks? Well, maybe, if the phone was stolen I guess, it would be easier for someone to steal your data. Your situation, with serious banking apps, it **may be** you don't want that risk...
Maybe for just trying a refurb to lose nt-code, look at LG's 'restore' from previous device ability, use it to save off the apps somewhere, then restore after refurb? no root needed.
cheers
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 :/