Database Develop

Phone does not connect to Network (started after being stuck at samsung logo)

Hi everyone,
I rooted my note and was using Jon ROM V3 for the last 3 months. Never had any malicious apps and my phone was working as usual.
Yesterday I took my phone and see that it is stuck at Samsung logo (an hour ago it was working fine). Tried reset and re-flashed ROM but no luck.
Later through download mode i flashed Official Indian Firmware(I live in India). Now I by passed the logo screen and the phone shows full signal bars but not able to connect to carrier network.
(tried all basic work out like removing battery/sim and re-inserting to phone and boot up)
I pressed power key and it did not show the power menu , it directly switched off mobile.
I rooted again with Philz kernel and flashed JON ROM. Still i see that my phone is not able to connect to any network. Also I observe that even here on this ROM when i press power key it directly turns off.
This is weird. I thought my IMEI was wiped off but im lucky to see that its still there.
I need your help. Im without my phone for the last 2 days now.
-
Jonathan

Note - I find that my IMEI number has been changed (to some generic IMEI 004999010640000) after i flashed the official firmware !!!! that's why it is not connecting to any network.
Someone please help me.

How did you flash the official firmware?
was it a tar file or a zip? I mean did you use odin?

chickoo.t90 said:
How did you flash the official firmware?
was it a tar file or a zip? I mean did you use odin?
Click to expand...
Click to collapse
It was a tar file The official Indian firmware I got from sammobile

either a glitch or you selected by accident clear efs.
anyways without efs backup hard to recover emei.
Do you get the simcard enter pinscreen on boot? If you dont then its not imei, if you do then you need someone like cvxcvx, search to fix it. That or Samsung

chickoo.t90 said:
How did you flash the official firmware?
was it a tar file or a zip? I mean did you use odin?
Click to expand...
Click to collapse
baz77 said:
either a glitch or you selected by accident clear efs.
anyways without efs backup hard to recover emei.
Do you get the simcard enter pinscreen on boot? If you dont then its not imei, if you do then you need someone like cvxcvx, search to fix it. That or Samsung
Click to expand...
Click to collapse
No I do not enter pin for simcard. I see my imei has been changed to 004999010640000. I tired fixing one problem and got onto another.
I guess there is no way other than sending my device to Samsung !
Anyways I appreciate your help. Thanks

jonastro said:
No I do not enter pin for simcard. I see my imei has been changed to 004999010640000. I tired fixing one problem and got onto another.
I guess there is no way other than sending my device to Samsung !
Anyways I appreciate your help. Thanks
Click to expand...
Click to collapse
You have a so called "developer IMEI". If you didn't safe your EFS then there is no real chance to restore it yourself.
There is a member (cxlcxl) who has hardware and can restore the original IMEI remotely.
But you still can use your device. Try to change the Sim Pin in the settings: you can use the same Pin for old and new (this is easier for me because sometimes I forget the new number).
After this the network connection should come back.
My workaround in my Pristine Custom Rom: one different jar-file that doesn't have the checks on startup from my old XXLSC dump. With this it works completely normal: Sim and Pin are always recognized from startup. I'm using this for many months now.

ThaiDai said:
You have a so called "developer IMEI". If you didn't safe your EFS then there is no real chance to restore it yourself.
There is a member (cxlcxl) who has hardware and can restore the original IMEI remotely.
But you still can use your device. Try to change the Sim Pin in the settings: you can use the same Pin for old and new (this is easier for me because sometimes I forget the new number).
After this the network connection should come back.
My workaround in my Pristine Custom Rom: one different jar-file that doesn't have the checks on startup from my old XXLSC dump. With this it works completely normal: Sim and Pin are always recognized from startup. I'm using this for many months now.
Click to expand...
Click to collapse
Thanks. BTW I jus gave my phone now to Samsung service center. They said its easy for them to restore my original IMEI and they charged me 150Rupess (3 Dollars) :good:

Really? Just $3

jonastro said:
Thanks. BTW I jus gave my phone now to Samsung service center. They said its easy for them to restore my original IMEI and they charged me 150Rupess (3 Dollars) :good:
Click to expand...
Click to collapse
sweet!

nokiamodeln91 said:
Really? Just $3
Click to expand...
Click to collapse
Aha , yes not joking.

Moto X mobile data not working.. i messed up

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!

Nexus 6 No LTE with IMEI correct, Bad "0" IMEi I have LTE?!?!?!? Heeeeelp!

Ok, Ladies and Gentleman I need some deep thought processing here for some help with a Motorola Nexus 6. In brief here is what the problem is, a while back when flashing Pure Nexus rom, I experienced a loss of my IMEI. I can restore my IMEI but if and when I do, I lose any 4g and LTE connectivity. The phone functions in 3g with data and phone etc... just slow as molasses but if I restore my IMEI to the one that doesn't show up my IMEI correctly I get back LTE/4g and all works fine also. I've tried going all the way back to the original firmware which was saved to computer and restoring it. Same thing, I have IMEI but no LTE/4g. restore bad efs and get LTE/4g back. I've tried going through all the factory firmware's and flashing by ADB and or TWRP and nothing firmware wise will allow me to restore the IMEI and have LTE/4g signal. If I restore the bad efs and get OOOOOOOO for IMEI when using the *#06# on any firmware version, I regain LTE/4g functioning! I am using Pure Nexus 7.1 now and can still see the 00000000 as a IMEI, if I restore my efs and get IMEI back showing correctly, no LTE/4g signal! My phone can only function as it should as long as the IMEI doesn't show correctly! I have tried just flashing base bands and other segments of any rom and still the problem persist! I have even tried restoring an EFS from another nexus 6 and still no help. It's not the sims because I've tried AT&T sims and Verizon sims from other phones and it does the same thing! I've tried flashing with a sims in the phone and without. Any ideas??? It's like somehow a correlating segment of a file is not being recognized when the correct IMEI is present, like some thing some where in the efs, IMEI, and radio are not taking to each other so to speak, unless it shows the zero's! Brain waves come on and help me out here!!

Have you tried doing a fresh install of a complete factory nexus image? (i.e. entirely wiping the device)

jbaumert said:
Have you tried doing a fresh install of a complete factory nexus image? (i.e. entirely wiping the device)
Click to expand...
Click to collapse
Thanks, and Yes, about 30 different times, using Google developer site original factory firmware, using ADB and or TWRP all the way back to original image, which I have saved as I said in the original post! I don't have a problem restoring IMEI it's just if I do, the phone will not connect to LTE/4g no way no how. I have to have a "0" IMEI for the phone to function as it should actually function and the LTE/4g radio to work, something strange is a miss!

TheWacoKid said:
Thanks, and Yes, about 30 different times, using Google developer site original factory firmware, using ADB and or TWRP all the way back to original image, which I have saved as I said in the original post! I don't have a problem restoring IMEI it's just if I do, the phone will not connect to LTE/4g no way no how. I have to have a "0" IMEI for the phone to function as it should actually function and the LTE/4g radio to work, something strange is a miss!
Click to expand...
Click to collapse
Alrighty, no need to yell.... The factory image is flashed with "fastboot" NOT adb or TWRP. Just wanted to clarify how you were returning the phone to stock.

jbaumert said:
Alrighty, no need to yell.... The factory image is flashed with "fastboot" NOT adb or TWRP. Just wanted to clarify how you were returning the phone to stock.
Click to expand...
Click to collapse
Yes I said thanks because I was yelling! Jezz, get a grip THIS IS YELLING! ADB/Fastboot both tools are used to flash, extract etc.. with your computer, so obviously one cannot flash/restore etc... without using the proper tools via computer!

Try this:
1) Install "Change APN" app from Google store
2) Open ChangeAPN and click the "option" ( the 3 vertical dots) in the upper right-hand corners.
3) click "reset to default"
4) exit the app
5) perform carrier reset ##3282#
6)If needed: after the phone reboots, perform PRL/Device config update. That's it and you should have LTE data.

Dixon Butz said:
Try this:
1) Install "Change APN" app from Google store
2) Open ChangeAPN and click the "option" ( the 3 vertical dots) in the upper right-hand corners.
3) click "reset to default"
4) exit the app
5) perform carrier reset ##3282#
6)If needed: after the phone reboots, perform PRL/Device config update. That's it and you should have LTE data.
Click to expand...
Click to collapse
Thanks! Ok, Itried that, restored my IMEI, "reset APN to default" Tried Carrier reset ##3282# and it says "NO Cellular Network" even though I am showing my network and 3G. So, I rebooted and same thing, went to PRL and tried to update and it says "update error" but it will refresh!

TheWacoKid said:
Yes I said thanks because I was yelling! Jezz, get a grip THIS IS YELLING! ADB/Fastboot both tools are used to flash, extract etc.. with your computer, so obviously one cannot flash/restore etc... without using the proper tools via computer!
Click to expand...
Click to collapse
You clearly don't know the difference between a recovery, the bootloader and the operating system.
ADB is used when the phone is on and is not how you flash a factory image. Fastboot is used in the bootloader and is the proper method of restoring to factory.

admiralspeedy said:
You clearly don't know the difference between a recovery, the bootloader and the operating system.
ADB is used when the phone is on and is not how you flash a factory image. Fastboot is used in the bootloader and is the proper method of restoring to factory.
Click to expand...
Click to collapse
No, I guess not, that's how I've been flashing, restoring and unbricking cells for years, I just don't understand anything!

TheWacoKid said:
No, I guess not, that's how I've been flashing, restoring and unbricking cells for years, I just don't understand anything!
Click to expand...
Click to collapse
You know some magic we don't? There is no way you've flashed a ROM with ADB...

@admiralspeedy
I was very gratified when I noticed that I'd overnight become a Senior Member - until I realised that it had nothing to do with the wisdom I'd imparted in my posts, but only that I'd posted 100. So seniority doesn't imply knowledge, which I think you're beginning to demonstrate in this thread as well as in another where I've seen this same strange unnecessarily belligerent attitude.
TheWacoKid is asking for help, which I'd be happy to offer if I had any ideas. I feel absolutely no desire to tell him that he has no idea what he's doing. And nor should you.
Stop trolling and become a properly-active member of the community.

dahawthorne said:
@admiralspeedy
I was very gratified when I noticed that I'd overnight become a Senior Member - until I realised that it had nothing to do with the wisdom I'd imparted in my posts, but only that I'd posted 100. So seniority doesn't imply knowledge, which I think you're beginning to demonstrate in this thread as well as in another where I've seen this same strange unnecessarily belligerent attitude.
TheWacoKid is asking for help, which I'd be happy to offer if I had any ideas. I feel absolutely no desire to tell him that he has no idea what he's doing. And nor should you.
Stop trolling and become a properly-active member of the community.
Click to expand...
Click to collapse
Actually, I wouldn't have jumped on him like that if he hadn't come out swinging with snarky comments when people tried to help him.

admiralspeedy said:
You know some magic we don't? There is no way you've flashed a ROM with ADB...
Click to expand...
Click to collapse
Look, I came on here to discuss a situation and or problem, which is what I thought this web site was known for, which I havent run into before, in that way not only do I get some help and or suggestions which might help me but help others at the same time who might have the same problem and or will have in the future and find possible solutions! If you don't have anything positive to add to the conversation/situation/problem at hand you are wasting my time, others time and most of all just making a fool out of yourself being childish and immature. Most on here come for solutions not looking to nitpick and try and belittle others like they know everything, which you don't, otherwise you would have given a solution! So you can continue to act like a troll or just leave the situation be and by the way, you ever hear of ADB Sideload??

Use method 2 , you will get everything definitely
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

TheWacoKid said:
Look, I came on here to discuss a situation and or problem, which is what I thought this web site was known for, which I havent run into before, in that way not only do I get some help and or suggestions which might help me but help others at the same time who might have the same problem and or will have in the future and find possible solutions! If you don't have anything positive to add to the conversation/situation/problem at hand you are wasting my time, others time and most of all just making a fool out of yourself being childish and immature. Most on here come for solutions not looking to nitpick and try and belittle others like they know everything, which you don't, otherwise you would have given a solution! So you can continue to act like a troll or just leave the situation be and by the way, you ever hear of ADB Sideload??
Click to expand...
Click to collapse
I'm "belittling" you because your first two replies to someone who tried to help you were snarky and rude. In your own words, get a grip.

admiralspeedy said:
Actually, I wouldn't have jumped on him like that if he hadn't come out swinging with snarky comments when people tried to help him.
Click to expand...
Click to collapse
Time for you to go back and read some more...
You can flash a ROM with adb... Now unless you can help him... Shaddyup

rignfool said:
Time for you to go back and read some more...
You can flash a ROM with adb... Now unless you can help him... Shaddyup
Click to expand...
Click to collapse
No, you can use ADB sideload to flash a ROM which requires you to be in the recovery. Standard ADB cannot be used to flash a ROM.

admiralspeedy said:
I'm "belittling" you because your first two replies to someone who tried to help you were snarky and rude. In your own words, get a grip.
Click to expand...
Click to collapse
Amazing to any one with half a brain how you a Troll can think from typed response that someone is yelling, swinging, snarky and rude but your the one with an attitude that is all the above because like I said your a childish troll! I can't believe this site would even allow someone like you to be a member paid or otherwise! Your attitude is all your own and based on your own weak assumptions! Now go back to playing with your legos!

drmuruga said:
Use method 2 , you will get everything definitely
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Thanks, I've used both of those methods, I have even tried just flashing individual parts all by themselves to see if just one part would give an error of some kind while flashing, no errors on any flash of any kind, the only difference being that if I read them correctly that on those methods it said to wipe data factory reset in recovery, before reboot, the Flashall bat file reboots automatically into image just flashed, I usually reboot as last command, if that makes any difference, I've even tried wiping then just flashing the new bootloader after a wipe, because it basically acts like a security checkpoint and partition manager, then rebooting and flashing the rest of one of the google firmware versions for the nexus 6.

TheWacoKid said:
Thanks, I've used both of those methods, I have even tried just flashing individual parts all by themselves to see if just one part would give an error of some kind while flashing, no errors on any flash of any kind, the only difference being that if I read them correctly that on those methods it said to wipe data factory reset in recovery, before reboot, the Flashall bat file reboots automatically into image just flashed, I usually reboot as last command, if that makes any difference, I've even tried wiping then just flashing the new bootloader after a wipe, because it basically acts like a security checkpoint and partition manager, then rebooting and flashing the rest of one of the google firmware versions for the nexus 6.
Click to expand...
Click to collapse
So was there a solution? The thread just ended. I also have this problem but I'm no where as technical as thewacokid.
But I do know how to follow steps

[Crossflash] - AT&T V405UA10 to Korean V409NUA

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!

Current Version is not available for user. Error on startup.

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 :/