Database Develop

[Q] TELL HTC PRIVACY MESSAGE can not be turned off

Hello, After i s-offd my htc one the revone method which i am greatful for and thank that team for all the hard work in making us s-off i do have a problem i am baffled with.
Can any shead some help with this....... after s-off i loaded a RUU and a normal rom on my one device but noticed when setting the phone up after install i get this message in the Tell HTC and reporting.......
This is test device. Accordingly,to collect critical information about the device, Tell HTC is enabled and cannot be turned off regardless of device settings.
please can someone tell me why after installing a RUU i would get this message and how to solve it, sorry for being thick here but noobies need a little help.
Thankyou all.

i think you have to remove it with a custom hboot. but be careful and read because if you s-on with custom hboot=brick

It's solely because you're S-OFF. Your device has all security disabled, thus it acts like a test device. Once you go S-ON, the red text will immediately disappear. The Tell HTC option will remain because that text is on most devices (even my little brother's unmodified device which has never been tampered with) but it's toggleable.
I believe there is an app in the /system/app folder that displays this, as customs roms don't have this option (the ones that aren't 99% close to stock, that is)

Theshawty said:
It's solely because you're S-OFF. Your device has all security disabled, thus it acts like a test device. Once you go S-ON, the red text will immediately disappear. The Tell HTC option will remain because that text is on most devices (even my little brother's unmodified device which has never been tampered with) but it's toggleable.
I believe there is an app in the /system/app folder that displays this, as customs roms don't have this option (the ones that aren't 99% close to stock, that is)
Click to expand...
Click to collapse
Thank you for your reply, i dont think i will bother changing the hboot untill there is a much safer way of doing it than there is at present,Its best to leave well alone after the mind bobbling i had to s-off, just when you think you have masterd the last 3 htc,s ive owend there is always something new and differant and more complexed, thanks again sir.

hotpointdave said:
Thank you for your reply, i dont think i will bother changing the hboot untill there is a much safer way of doing it than there is at present,Its best to leave well alone after the mind bobbling i had to s-off, just when you think you have masterd the last 3 htc,s ive owend there is always something new and differant and more complexed, thanks again sir.
Click to expand...
Click to collapse
You're welcome. Are you sure you need S-OFF, though, or did you merely acquire S-OFF because you could? It is fairly easy to make your phone a shiny paperweight with the security off as you now have full write access to the hboot and radio sections.

Handsfree Activation Bootloop FIX

Hi Guys. First off I'm posting this for information in hopes to help anyone else having this problem. I'll go over the problem I was having. What caused the problem for me and the steps I took to resolve it.
Problem:
A Handsfree activation bootloop. More specifically, no matter which rom, RUU, OTA, recovery or firmware I flashed, my phone would go threw a HFA and PRL update, say that it was successful and reboot on it's own and start the process over again. If at some point by chance I could catch it and disable the vDM.apk would be the only way I could stop it and boot normally. I tried resetting my profile, factory resets, Sprint support (which was completely useless) and everything else mentioned above. I even threw the kitchen sink in for good measure. lol. I was able to make phone calls, receive text and mms. I even had LTE and 3G service. But my wifi calling and sprint zone didn't work. So I knew something wasn't activating properly.
Cause:
Well for me it started when I accidentally flashed a M7 rom. Yeah don't laugh, it happens. Anyway, in recovery it said it failed but not before it formatted "/dev/block/mmcblk0p37" which is the system partition on the M7. But on the M8, it's the /carrier partition. So it erased all my info and filled it with a bunch of s**t. To the point that the partition was full and activation couldn't write to it. It also injected a bunch of s**t in "/dev/block/mmcblk0p39" which is the /devlog partition on the M8. So just a big mess. This is just how I got to this point. I'm not saying this your cause but the fix might help you.
Fix:
1 Get your self to a point that you are booted up to a rom. If you can't, try flashing an international rom made for sprint like "insert coin" for example. Those don't HFA bootloop from my experience.
2 Download MSL reader from the market. And get your MSL you'll need it later.
3 With a good root explorer, go to /carrier folder, do a backup of it (just in case) open the folder and delete everything in the folder.
4 Go to /devlog folder, open it and delete everything in there. (You don't need this stuff, it will rewrite itself).
5 Download the zip at the bottom of the post, extract it and copy the contents to your /carrier folder. Don't worry about the /devlog folder. leave it empty.
6 Now your going to flash a RUU. Download the one you want. I used https://www.androidfilehost.com/?fid=95784891001604379 (Don't worry it won't get you S-on or lock your bootloader). It will probably do a HFA again and it should fail. If not, try disabling it. Because we need to get to the dialer.
7 In your dial pad enter ##786# and go to edit mode. Enter your MSL if it asks you. Go to the menu button at the upper right and hit reset. Go threw the promps, the phone should reboot and restore. Let it boot up. It will go threw HFA again. But now you'll notice it activated properly. At this point your all done. Flash a custom recovery again. Profit.
Special Thanks to @Captain_Throwback You rock.
Let me know if this helps. Please post any questions and I'll try guiding you threw.

Dude iv been having some serious issues with data. I'm going to try this and see what happens thanks.

sprkat85 said:
Dude iv been having some serious issues with data. I'm going to try this and see what happens thanks.
Click to expand...
Click to collapse
Hope it helps.

Macropoutsis said:
Hope it helps.
Click to expand...
Click to collapse
It definitely helped out. Thanks for posting this again.

sprint htc one m8 h/k edition
u have mentioned in point 3 download root explorer
but in my case I am facing hands free activation page with emergency button .. and cant go further
how can I get rid of it ..
please help me .. i shall be very thankful to you

sprkat85 said:
It definitely helped out. Thanks for posting this again.
Click to expand...
Click to collapse
hello guys ..
I am facing the bitter problem in m8
after installing custom rom ,,as u told in your method for hands free activation loop fix,, I am facing the hands free activation loop ...
is there anything I can do to avoid it.???
otherwise its an phone for incoming calls only..
help me out guys

I ended going completely stock running an ruu then took steps to flash the newest firmware after I rooted. The problem I had was I flashed the wrong firmware. I do not have the HTC one m8 anymore.

gag_dhiman said:
hello guys ..
I am facing the bitter problem in m8
after installing custom rom ,,as u told in your method for hands free activation loop fix,, I am facing the hands free activation loop ...
is there anything I can do to avoid it.???
otherwise its an phone for incoming calls only..
help me out guys
Click to expand...
Click to collapse
What ROM?
If it is stock based you can try this, either go through TWRP and select file manager or do this in the zip before flashing.
Go to system/app/HtcOMADM_SPCS and rename the apk by adding .bak after .apk.
After the phone boots and you pass setup you can always rename the file by removing the .bak
You might get better results by posting this question in that ROM thread, or make a thread in the Q&A and put the ROM name in the title of the thread.

gag_dhiman said:
hello guys ..
I am facing the bitter problem in m8
after installing custom rom ,,as u told in your method for hands free activation loop fix,, I am facing the hands free activation loop ...
is there anything I can do to avoid it.???
otherwise its an phone for incoming calls only..
help me out guys
Click to expand...
Click to collapse
Hey bud. Didn't get my notifications on this thread. Are you still having a problem?

Hello senior.
I am ising the stock rom in sprint m8 harman kardon edition.
I still facing the problem. Cant rename htc omadm. Spcs file.
Moreover . In notifications area one line is written ( device management is running)
Sorry senior. For late reply.. i was in roaming.
Do guide me

HFA loop !!!!!!!!!!!!!!!!!1 never ending
I installed twrp .. in bootloader under twrp recovery,then advanced and in file manager /.. I go through system folder but no app folder is there .. and I am still facing the hands free activation loop/... do something seniors.....
dopy25 said:
What ROM?
If it is stock based you can try this, either go through TWRP and select file manager or do this in the zip before flashing.
Go to system/app/HtcOMADM_SPCS and rename the apk by adding .bak after .apk.
After the phone boots and you pass setup you can always rename the file by removing the .bak
You might get better results by posting this question in that ROM thread, or make a thread in the Q&A and put the ROM name in the title of the thread.
Click to expand...
Click to collapse

gag_dhiman said:
I installed twrp .. in bootloader under twrp recovery,then advanced and in file manager /.. I go through system folder but no app folder is there .. and I am still facing the hands free activation loop/... do something seniors.....
Click to expand...
Click to collapse
You have to mount system first.

Yes ... Seniors ... Yes... Got the solution... Thanks a lotttt..

hi i have bought on aliexpress a htc one m8 looks is m8 sprint from imei .my phone show bootloader unlocked
m8 whl pvt ship s-off
cid-11111 hboot -3.16.0.000
radio -1.00.20.0.120
running on kitkat 4.4.4
can any one help i try this tutorial but not show gsm network

Does Sprint M9 work with this method?

Remove the Red Text From Firmware zip and Aboot - S-OFF Only!

**Warning! This is a potentially hazardous procedure! Do not proceed unless you are willing to deal with the consequences if you do something wrong.** I am not responsible if you brick, blow up, catch on fire, or do any other damage to your phone. Do this at your own RISK! Now that I have that out of the way.
If you feel that you have the necessary skills then proceed. You don't have to wait for someone to make a No Red Text firmware zip, or flashable aboot. It is so easy to create your own no red text aboot zip, or a no-red-text firmware zip. This will work on all M9's and other HTC devices. M8, M7, etc hboot's.
You will need 7zip, and a hex editor. Just open up the firmware zip with 7zip, and extract the signed-aboot. Now open the aboot with a hex editor. In search type the first couple of words of the red text "This Build", and hit enter. That will take you to the line you need to edit to remove that annoying Red Text. On the M9 I believe it will be line 00086F2E or 0008EF3A. Once you have found the lines that appear in red on your screen after you unlocked your bootloader, navigate to the numbers on the left that coincide with the letters. Don't remove any! Type in 20,and watch the letters disappear. Do this for the entire text, and only for that text. The 20 creates a blank space that won't show on the screen. Save it, and put it back in the zip. Flash in download with fastboot. Enjoy. To make a flashable aboot take your modified aboot and android_info.txt from your device, and zip them up together. Then flash in download with fastboot.
You can also do the fake locked mod the same way. Just type in unlocked, in search, and look for the place that has locked, unlocked, and relocked together. Then do the same thing you did for the development warning to the "un" in "unlocked".
Cheers
I Truly Enjoy XDA-Developers. Com with this Fabulous HTC One M9

thanx
thanx its working

thank you.

singhshb said:
thanx its working
Click to expand...
Click to collapse
You're welcome!
daydream3r said:
thank you.
Click to expand...
Click to collapse

batinica said:
This no doubt a noob question but when you say "Just open up the firmware zip with 7zip, and extract the signed-aboot" how do I go about get the zip from my device?
Click to expand...
Click to collapse
You don't get the zip from your device. What you need to do is search for a firmware zip here on XDA and use it. You will probably find someone who has already made a no red text firmware zip and use the ABOOT from it, but where's the fun in that. You could make your own firmware zip, but that's not the purpose of this thread. Search for a thread on XDA to teach you how to make a firmware zip if you are interested in doing that as well.
Using XDA to unleash the power of Android on my S6 Edge Plus & HTC One M9

help please
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one

bakh1 said:
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one
Click to expand...
Click to collapse
Sorry my friend but looks like hard brick if it won't power on. there's nothing you can do but jtag.
This is a dangerous thing to do and could destroy your device. You are hex editing the a boot, which is cannot be compromised in any way or you will end up with a paperweight. You see, your bootloader is no longer operational. That's why your phone won't power on. In this case, allowing somebody to do it, that had no clue what they were doing, was extremely risky and foolhardy and looks to have destroyed your device.

bakh1 said:
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one
Click to expand...
Click to collapse
I'm sorry to hear that your brother made a mistake editing the ABOOT. Like @Behold_this said you are now going to have to take your phone to a repair shop that has the professional tools to restore your phone to a working condition. If you are with T-Mobile and bought the phone through them you may be able to take it to them and get it replaced. Just don't mention that you modified the ABOOT. Also, if you are a US customer and you haven't used your Uh-Oh protection you can try that. I know that Mo Versi had said rooting your phone would not void the Uh Oh protection, but I don't know about modifying the ABOOT. They're all worth a try. I wish you the best with this. There's always a risk when you modify a device like we do here on XDA. The key is to always follow directions carefully, and if you're not a 100% sure of what you are doing don't do it.
Using XDA to unleash the power of Android on my S6 Edge Plus & HTC One M9

please help me
i am currently out of us and not going back soon so i gave to local repair shop here they said they cant help me because jtag can only be done on m8 not m9 something like that and my brother said give me one more try he said something about htc unbrick project what should i do please

bakh1 said:
i am currently out of us and not going back soon so i gave to local repair shop here they said they cant help me because jtag can only be done on m8 not m9 something like that and my brother said give me one more try he said something about htc unbrick project what should i do please
Click to expand...
Click to collapse
As far as I know that project was for the M7 and won't work on the M9. Besides that method required for the phone to boot to bootloader or fastboot I believe. Since your phone won't boot at all the only thing I can think to do is go through your carrier or HTC. HTC has repaired or replaced many bricked devices free, but I have heard of a few cases where they would charge. If you don't mind not telling them the complete truth about how it was bricked you could tell them it was in the process of updating when it happened. That has actually happened on the M7. This is the first time I have actually heard first hand of a M9 hard bricking. All of the other ones I have heard about were able to boot to download, htc ftm, or bootloader mode and could be recovered. You have tried to boot to htc ftm by holding the power and volume up buttons continuously?
Using XDA to unleash the power of Android in my S7 Edge, One M9, and S6 Edge Plus

jbfountain said:
**Warning! This is a potentially hazardous procedure! Do not proceed unless you are willing to deal with the consequences if you do something wrong.** I am not responsible if you brick, blow up, catch on fire, or do any other damage to your phone. Do this at your own RISK! Now that I have that out of the way.
If you feel that you have the necessary skills then proceed. You don't have to wait for someone to make a No Red Text firmware zip, or flashable aboot. It is so easy to create your own no red text aboot zip, or a no-red-text firmware zip. This will work on all M9's and other HTC devices. M8, M7, etc hboot's.
You will need 7zip, and a hex editor. Just open up the firmware zip with 7zip, and extract the signed-aboot. Now open the aboot with a hex editor. In search type the first couple of words of the red text "This Build", and hit enter. That will take you to the line you need to edit to remove that annoying Red Text. On the M9 I believe it will be line 00086F2E or 0008EF3A. Once you have found the lines that appear in red on your screen after you unlocked your bootloader, navigate to the numbers on the left that coincide with the letters. Don't remove any! Type in 20,and watch the letters disappear. Do this for the entire text, and only for that text. The 20 creates a blank space that won't show on the screen. Save it, and put it back in the zip. Flash in download with fastboot. Enjoy. To make a flashable aboot take your modified aboot and android_info.txt from your device, and zip them up together. Then flash in download with fastboot.
You can also do the fake locked mod the same way. Just type in unlocked, in search, and look for the place that has locked, unlocked, and relocked together. Then do the same thing you did for the development warning to the "un" in "unlocked".
Cheers
I Truly Enjoy XDA-Developers. Com with this Fabulous HTC One M9
Click to expand...
Click to collapse
I finally found your effort of writing this "recipe".
Thanky for sharing!

Is the "red text" referred to here the notice about the reporting software and that HTC will collect information about what your phone is doing, etc.? If so, will the procedure actually remove the software or stop it from running, or does it just get rid of the notice?
ETA: Is that reporting software an issue to worry about for battery use/privacy/whatever else reasons?

drfarmkid said:
Is the "red text" referred to here the notice about the reporting software and that HTC will collect information about what your phone is doing, etc.? If so, will the procedure actually remove the software or stop it from running, or does it just get rid of the notice?
ETA: Is that reporting software an issue to worry about for battery use/privacy/whatever else reasons?
Click to expand...
Click to collapse
The red text that appears on your phone after unlocking it doesn't have any functionallity. Some just do not want to see it. That's what this is all about. If you don't want to see it use this method. If it doesn't bother you don't do it.
Cheers
Sent from my HTC 10 using XDA Labs

WiFi NVRAM WARNING err 0x10 in wifi

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

[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!