[Crossflash] - AT&T V405UA10 to Korean V409NUA - LG V40 Guides, News, & Discussion

[Crossflash] - AT&T V405UA10 to Korean V409NUA - LG V40 Guides, News, & Discussion

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!

Related

[Q] new D3 user

Hi,
i recently bought a new droid 3 from verizon i already sim unlocked it because i live in Europe.
but i'm totally new to the android system but i do know some things about it but is there a guide to help me started rooting and flashing?
or could someone tell me the basics in a nutshell?
my previous phone was a WinMo based phone and all you needed was sspl and you could flash custom roms.
how is it done for android? and what does it mean with fastboot, root? (i asume it is something like linux to be root user?) safeboot? bootstrap? and what is CM7 or CM9
P.S. i study electronics-informatics so you don't need to tell me what linux or windows is
thnx in advance

Can you tell me how you unlocked your phone???
To root
http://forum.xda-developers.com/showthread.php?t=1240130
To flash ROMs install Safestrap from here
http://hash-of-codes.blogspot.com/p/android-downloads.html
Go to the android development section to find ROMs.
Liberty, ICS/CM9, MavRom, and SteelDroid are the most popular. Im using mavrom with ICS currently.

I definitely recommend looking into CM9. I just did a bunch of Googling on it today for my D3.
Now I'm running Ice Cream Sandwich and loving it. It's early yet and it has it's quirks, but overall I think it was worth it.

Dri94 said:
Can you tell me how you unlocked your phone???
Click to expand...
Click to collapse
euhm i sim unlocked my phone using this website unlock4moto.com/order_code/Motorola/Droid_3/any_Motorola/
(put http in before the link) xda wont let me post hyperlinks yet
you only need to give the IMEI number you can find here:
At the Home screen, press Menu
Tap Settings
Scroll down and tap "About phone"
Tap Status
Scroll down the screen and the IMEI # will be listed there
it worked for me and i got the sim unlock code emailed to me within 30 mins (look in you spam folder too)
P.S. thnx for the info

Downtown Dan said:
I definitely recommend looking into CM9. I just did a bunch of Googling on it today for my D3.
Now I'm running Ice Cream Sandwich and loving it. It's early yet and it has it's quirks, but overall I think it was worth it.
Click to expand...
Click to collapse
ooh but is there a way to brick the phone? cause it would be darn stupid to brick my 3 day old phone and send it back to america for repairs.
so just root the phone and install safestrap? no worries of bricking the phone? and are there other methods besides safestrap?
if yes what are the differences?
it all looks SO easy to flash roms for android ( in WinMo it was always wait and see) but then again it was Microsoft...

There is always a chance of bricking your phone but fortunately perma-bricking your phone while trying to flash new roms or using safestrap is almost impossible since you can still enter fastboot (m+powerup) from where you can install the stock sbf/rom
You can also flash using the 'old' bootstrap which basically removes your stock rom and flahes the new one.
Safestrap backs-up your old rom so you can try out another rom in another system/partition. Almost dualboot like except you can't reflash the original rom (yet)
Sry no links i'm on my droid3

"Almost dualboot like except you can't reflash the original rom" hey double, what do you mean by this. If you toggle safe system you can use your original ROM again. although i think im understanding wrong lol

Dri94 said:
"Almost dualboot like except you can't reflash the original rom" hey double, what do you mean by this. If you toggle safe system you can use your original ROM again. although i think im understanding wrong lol
Click to expand...
Click to collapse
You're right but you can't reflash your original rom (non-safe). E.g. i have mavrom as nonsafe/original and ics has safe..now if an update comes for mavrom i can't update it without uninstalling safestrap and going back to bootstrap

Oh I understand you now. And we got the same setup aha.
Sent from ICS Droid3 using xda premium

snakebomber said:
euhm i sim unlocked my phone using this website unlock4moto.com/order_code/Motorola/Droid_3/any_Motorola/
(put http in before the link) xda wont let me post hyperlinks yet
you only need to give the IMEI number you can find here:
At the Home screen, press Menu
Tap Settings
Scroll down and tap "About phone"
Tap Status
Scroll down the screen and the IMEI # will be listed there
it worked for me and i got the sim unlock code emailed to me within 30 mins (look in you spam folder too)
P.S. thnx for the info
Click to expand...
Click to collapse
Hello, Today I tried to unlock my droid 3 on the website that you share with us no luck for me.
I received an Email from them:
Hello
For IMEI number of the order, unfortunately, there is no code in database.
xxxxxxxxxxxxxxx
Please verifity given IMEI number.
If the IMEI is correct, we will propose an alternative solution.
Yours
unlock4moto
but when I dial *#06# it display MEID HEX
A00000xxxxxxxx i think this is the ESN
DEC
273045896523648364 is this the IMEI Number??
I tried to send the 18 numbers but on the website will not let me put more than 15.

Ed27 said:
Hello, Today I tried to unlock my droid 3 on the website that you share with us no luck for me.
I received an Email from them:
Hello
For IMEI number of the order, unfortunately, there is no code in database.
xxxxxxxxxxxxxxx
Please verifity given IMEI number.
If the IMEI is correct, we will propose an alternative solution.
Yours
unlock4moto
but when I dial *#06# it display MEID HEX
A00000xxxxxxxx i think this is the ESN
DEC
273045896523648364 is this the IMEI Number??
I tried to send the 18 numbers but on the website will not let me put more than 15.
Click to expand...
Click to collapse
of what i read is that the MEID is a kind of IMEI number but because there are so many phones with an IMEI number that they needed something new but the unlock is (according what i found on google) always done with the IMEI number.
to what carrier is your phone locked to? and what is the exact type of your phone XT860 XT862? (you can find this in the "about" menu under settings.
maybe it is because my phone was brand new and never used.So it was never activated on the verizon network.
and i don't know if this has anything to do with it but on the box it says that the phone is "global ready".(I personally think it has nothing to do with that because if the phone is quadband it is ALWAYS global ready, if ofcourse the phone is not locked to verizon or some other carrier)
i have an alternative website but it is more expensive i thought it was 23 dollars or so. it first checks if they have an unlock code (never used the site but it looks promising)
sim-unlock.net/sim-lock/75/Unlock_for_any_New_Motorola_Defy_Flipout_Milestone/ (again put the http in front of it)
i hope this helps

Lost imei number and device number

My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?

BlackStorm94 said:
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
Click to expand...
Click to collapse
Same thing happened to me after I unbricked my device using the exact same tutorial. However, even with IMEI 0 I can still make and receive calls and text messages. But I'm not sure if I should leave my device like this. If someone has any solution to provide I would be very grateful! I hope it doesn't involve flashing any ROM again cause I'm really afraid that I may brick my phone again ...

Hey guys, I had exactly the same problem. I tried different things including flashing various Roms and Bootstack, but nothing seemed to work. Since I’ve been searching for a solution quite a while, I now have the honor to help you out and everyone with an L90, who stumbles upon the same issue.
First of all, I made a backup of my EFS, so that I could restore the state my phone was in (IMEI=0, but working baseband). You can do that easily with TWRP (thx to shoxxy . By the way, this is something which we all should have done beforehand. It would have been much easier to restore our IMEIs.
But don’t worry, if you follow the instructions in this video (https://www.youtube.com/watch?v=nwzgs1Cmr9k) you should be able to get your IMEI working again. For those, who feel more comfortable following written instructions I copied the following procedure using this thread (http://forum.xda-developers.com/showthread.php?t=1960918) as a model and edited them a little to the way it just worked for me.
Do this on your own responsibility! And better double-check with the video our other threads.
Before you start:
Download this package (http://www.mediafire.com/download/figdbxb75j5kyry/package.rar), it belongs to the user who made the video on youtube (PremiumRepair).
Make sure your phone is rooted and USB-Debugging is enabled (http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Procedure :
Install Drivers. Either you use LG Support Tool or download them directly. For me the LGUnitedMobileDriver+3.14.1_ML_WHQL.exe worked just fine. Don’t forget to uninstall old drivers or you could run into problems.
Install QPST v2.7.378. Microsoft Visual C++ 2005 Redistributable is a prerequisite, just confirm it.
Plug your device into your PC (USB port)
Run QPST Configuration from your Windows Start menu. Switch to the second tab ("Ports") and choose "Add new port" (bottom left button). You should see a COM port associated with "USB/QD Diagnostic". Select it, then press Ok. You can close the QPST Configuration window now.
Open Windows Explorer and browse to "C:\Program Files\Qualcomm\QPST\bin" (or wherever you installed QPST) and launch RF_NV_Manager.exe. In RF NV Manager, Go to "Settings / Comport". You should see your COM port in the dropdown box. Select it, then press OK.
Go to "File" and choose "Read from phone". RF NV Manager will read all NV items from the phone. Now if you see item #550, you will be able to alter it (see below). If you can’t find it, go to “File” and choose “Read supported RF NV Items”. If you still can't find it, there is a way to create it. Take a look at the thread I linked to.
Now comes the critical step of altering the IMEI. Select item #550 and you'll see 9 boxes on the right, a "Write NV" button and an "Hex" checkbox. Check the "Hex" checkbox.
Now, you'll have to enter the IMEI in the 9 boxes in a very specific way. The easiest way is to use the IMEI converter (for other method see linked thread). Put your IMEI in, convert it and put the digits in the boxes (two number per box).
Now you can then press "Write NV" to write the IMEI value to your phone.
Once done, unplug the device, and reboot it. Now you IMEI should be changed. If it’s not your number, take a look at the step seven again and check the video.
Please give a feedback, if it worked for you (incl. Details about your device, ROM, etc.) so that other users can profit from it. Thanks
Edit: @ BlackStorm94 - Don't worry about the warning. It will vanish if you install a different ROM.

I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick

Lazgeor said:
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Click to expand...
Click to collapse
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951

mhikel said:
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Click to expand...
Click to collapse
So, I rooted the phone successfully, but the phone is still not recognized by QPST Configuration or RF NV Manager. My pc recognizes the phone and I can do everything properly, but these programs say that there is No Phone ... I don't know what to do ...

mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work

mhikel said:
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
Click to expand...
Click to collapse
I'm going to try on a new computer tomorrow afternoon and I'll let you know how it went. I uninstalled all drivers associated with my phone on my computer and after reinstalling them I still got no results. I guess I may have confused it So that's why I'll try on a new one. Thanks for your help

Hello, sorry for the late reply. I just wanted you to know that even though I tried with another computer, my phone was still not recognizable. It doesn't really matter tho, cause even with the IMEI 0 I still have service and it works normaly for about a month now. If you have any solution then I would like to try it, but if not then it's okay. Thanks for your time

No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)

[/COLOR]
mhikel said:
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Click to expand...
Click to collapse
Yeah yeah, I had USB Debugging enabled every time I plugged my phone into both of my PCs. But I don't think that's the reason this tutorial isn't working on my phone. When I unbricked the device, I had to use the L90 D405 loader.img in order to reflash the bootloader and recovery. But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n. I hope you understood this cause I know it's a bit weird I see options to activate NFC but I never use it so I can't tell you if it works. However I can activate it properly. Anyway, about the IMEI, as I told you, it basically works without problems even with 0 because I think that my service provider doesn't block anybody except someone reports the device as stolen. If you have any further solutions then let me know but if not the don't worry, I'm okay!

Lazgeor said:
But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n.
Click to expand...
Click to collapse
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!

mhikel said:
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
Click to expand...
Click to collapse
It's okay I don't want to bother you any further. I'll buy a new phone soon anyways and since I'll give this one to my small brother, I don't think he'll really worry if his IMEI is 0 If at some point this device gets blocked by a service provider then I'll start searching for ways to fix it again. That bootstack page you mentioned seems useful. I'll try that if I do have any problems. Thank you very much for your help

That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.

mhikel said:
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
Click to expand...
Click to collapse
Update: I actually fixed it I know I told you that I would leave it as it is for now, but today I had nothing to do, so I decided to try my best and fix it. What I did was, as the post you told me said, I had to install the Kit Kat bootstack and the easiest way to do that is by flashing the Kit Kat rom. So I downgraded to android 4.4.2 using the stock rom I found on another post, and then I used your tutorial on the Kit Kat version. This time I was able to pass step 6 because my phone was getting recognized properly. I also didn't needed root access after all, since the new rom was just installed and it worked. After finishing the tutorial and restarting the phone, my IMEI was back! Then I upgrated my phone to the lollipop version, and when the upgrade finished, my IMEI was still there. So now I'm in lollipop with a working IMEI. I'm so thankful to you now, thank you very much for helping me and providing me these useful tutorials. I really appreciate it

Wow, that's just great!=) congratulations, you can be proud! Happy for you, that was quite an issue. You are welcome=) Well, someone from this forum helped me out, when I seeked for help and I am happy to give something back. Thank you for sharing your solution! That should be helpful for the next one stumbling over this problem. Enjoy your completely restored phone!=)

Korea region V40, can I flash to European firmware?

Hello,
I have a LM-V409N here. It has some Korean bloatware but worse than that, even though the phone is set to English, a lot of things are still in Korean. For example an available software update description is in Korean. Buttons in the phone app show Korean text, etc.
Can I flash a European firmware on to this model? Will that 'just work'?
I hope someone can help me with this.
Thank you,

Rooted? you won't get far otherwise. Had the same problem on my korean G5.
On a rooted device though, you can edit the build.prop locale to your native region to turn off the korean elements of the UI and obviously remove the bloat.
some of the bloat can be disabled even if uninstall isn't allowed. Carrier specific ones can't unfortunately.
Flashing wise, iirc that's a no go as it will break radio. No signal afterwards. At least that was the problem on the V35.

Thank you so much for your reply. This makes me worry a bit less
No I don't have it rooted (yet). I will go figure out how to do that for this phone model and then if I can't find out how to do the build.prop changes I will come back here to ask for help
Do you have any idea why WiFi HotSpot is not working properly? Laptops and other phones just don't see the SSID and when trying to setup a 5GHz hotspot, the slider hangs when you turn it on (turns gray and freezes) and you have to reboot the phone to get it enabled again. But it will only turn on when on 2.4GHz.
If I can get all the Korean stuff to disappear, flashing won't be necessary anymore So let me get to finding that out!
Let's first see if flashing fixes anything.
Thank you so much once again!
Edit: Come to think of it, when I turn on the phone it shows an SK Telecom animation and sound (some Korean carrier I guess) and I would like that removed as well..
I guess the only way to get that removed is to flash another firmware? Would you know a firmware version for this LM-V409N which is just 'LG original' without any carrier/provider customization?
Thank you!
Edit2: OK, I found out how I can flash a stock firmware using the LGUP tool. However, this fails at the beginning of the process because of an 'Initialize' error.
I suspect I need the device to be rooted before flashing..? I could find how to flash pretty easily, but how to root..?
Can anyone point me to a guide for rooting the V40?
Thanks!

No, you don't need root. Just search here on xda for crossflash word. In the g7 forum I have made an tutorial. You will need lg drivers, com port, lg up and common. DLL for v40. For g7 it works like a charm. Be sure to check and compare GSM bands from Korea to EU. For g7 they was the same.

Inerent said:
No, you don't need root. Just search here on xda for crossflash word. In the g7 forum I have made an tutorial. You will need lg drivers, com port, lg up and common. DLL for v40. For g7 it works like a charm. Be sure to check and compare GSM bands from Korea to EU. For g7 they was the same.
Click to expand...
Click to collapse
OK, did all that. LGUP starts up, detects my LM-V409N correctly.
I select the KDZ file, set it to UPGRADE and click START.
Now it gives me the error 'LGUP Framework must be 1.16'. I have 1.14 apparently and I can't find 1.16 anywhere.
I read something about "If you do have some knowledge to bypass the LGUP Version Check on this DLL, then You can sideload kdz firmware onto your LG V40 ThinQ with LGUP 1.14." on this site: https://www.mylgphones.com/lgup-dll-for-lg-v40-thinq-version1-9-39-7.html
But again, I can't find anything about how to bypass that version check.
I tried with LGUP_common.dll versions 1.9.39.7 and 1.0.39.10. Both same result (need 1.16).
Also tried with 0.0.3.23 but that one gives the "Initialize" error after clicking START.
Any other tips or tricks you can suggest?
Thank you,

AzzKickah said:
OK, did all that. LGUP starts up, detects my LM-V409N correctly.
I select the KDZ file, set it to UPGRADE and click START.
Now it gives me the error 'LGUP Framework must be 1.16'. I have 1.14 apparently and I can't find 1.16 anywhere.
I read something about "If you do have some knowledge to bypass the LGUP Version Check on this DLL, then You can sideload kdz firmware onto your LG V40 ThinQ with LGUP 1.14." on this site: https://www.mylgphones.com/lgup-dll-for-lg-v40-thinq-version1-9-39-7.html
But again, I can't find anything about how to bypass that version check.
I tried with LGUP_common.dll versions 1.9.39.7 and 1.0.39.10. Both same result (need 1.16).
Also tried with 0.0.3.23 but that one gives the "Initialize" error after clicking START.
Any other tips or tricks you can suggest?
Thank you,
Click to expand...
Click to collapse
Hello.
I told you to look in g7 forum for crossflash. You will need lg up 1.15 and follow the exact steps. Beware it may brick your device, so I'm not responsible.
Link here https://forum.xda-developers.com/lg...ash-oreo-pie-firmwares-lg-g7-g7-t3915303/amp/
Warning!!! Pay attention not to download the common. DLL from there as it is for lg g7. You must download for your v40. Also for your firmware. Also you will loose your data, so backup first if you have important files, sms, etc.

Inerent said:
Hello.
I told you to look in g7 forum for crossflash. You will need lg up 1.15 and follow the exact steps. Beware it may brick your device, so I'm not responsible.
Link here https://forum.xda-developers.com/lg...ash-oreo-pie-firmwares-lg-g7-g7-t3915303/amp/
Warning!!! Pay attention not to download the common. DLL from there as it is for lg g7. You must download for your v40. Also for your firmware. Also you will loose your data, so backup first if you have important files, sms, etc.
Click to expand...
Click to collapse
OK so for my clarification, this method is how to bypass the version check? (If yes, I will go try this).
Or is this a separate method? (If it is separate, I'm afraid to brick it and I will not try it).
Thank you so much for your help. It really is very much appreciated.

AzzKickah said:
OK so for my clarification, this method is how to bypass the version check? (If yes, I will go try this).
Or is this a separate method? (If it is separate, I'm afraid to brick it and I will not try it).
Thank you so much for your help. It really is very much appreciated.
Click to expand...
Click to collapse
Yes, this is for bypassing the obsolete lg up 1.14.
But 1.15 will not work if you open it, it will ask you for developer user and password. But there is a hack with using cmd line. Follow my steps.
I repeat again, if there is a working DLL for lg v40 and if 40 supports crossflashing (highly it does) then you're good to go. Don't forget to check what is your com port when your v40 is connected in download mode.
---------- Post added at 11:39 AM ---------- Previous post was at 11:33 AM ----------
If you're connected to a USB 3.0 port and have quality USB c cable, it should install it in less than 1 minute
---------- Post added at 11:47 AM ---------- Previous post was at 11:39 AM ----------
Here is a little tutorial for V40
Easy commands for this new LGUP v1.15.06
If using powershell from win10:
1. Install USB drivers and put V40 in download mode - connect it to USB cable then go and check your COM port in windows device manger
2. Open powershell from C:\Program Files (x86)\LG Electronics\LGUP (shift + right mouse) and type cmd and hit enter.
3. Type this command: lgup_cmd.exe comX "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "(path to your kdz firmware)"
Example: (if your phone is under com5 and your kdz is located in D:\ and has this name XXX.kdz)
lgup_cmd.exe com5 "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "D:\XXX.kdz"
Links:
LGUP new version - https://drive.google.com/file/d/1dJZ...jumm5mtKp/view
LGUP common.dll for V40 - you must download it.
Firmwares: https://lg-firmwares.com/
European firmwares for V40 - https://lg-firmwares.com/lg-lmv405ebw-firmwares/#tab=firmwares

[/COLOR]Here is a little tutorial for V40
Easy commands for this new LGUP v1.15.06
If using powershell from win10:
1. Install USB drivers and put V40 in download mode - connect it to USB cable then go and check your COM port in windows device manger
2. Open powershell from C:\Program Files (x86)\LG Electronics\LGUP (shift + right mouse) and type cmd and hit enter.
3. Type this command: lgup_cmd.exe comX "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "(path to your kdz firmware)"
Example: (if your phone is under com5 and your kdz is located in D:\ and has this name XXX.kdz)
lgup_cmd.exe com5 "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "D:\XXX.kdz"
Links:
LGUP new version - https://drive.google.com/file/d/1dJZ...jumm5mtKp/view
LGUP common.dll for V40 - you must download it.
Firmwares: https://lg-firmwares.com/
European firmwares for V40 - https://lg-firmwares.com/lg-lmv405ebw-firmwares/#tab=firmwares
Click to expand...
Click to collapse
It worked!! :laugh:
You are the best. THANK YOU for your help!
Damn that was scary to watch that percentage creep up towards 100%

AzzKickah said:
It worked!! :laugh:
You are the best. THANK YOU for your help!
Damn that was scary to watch that percentage creep up towards 100%
Click to expand...
Click to collapse
What dll did you used? and from where did you find the information that the dll is correct? please links. :angel:

Inerent said:
What dll did you used? and from where did you find the information that the dll is correct? please links. :angel:
Click to expand...
Click to collapse
DLL: https://drive.google.com/file/d/1qKRlOFVZMIanphD-jp6dxenCqkaZP2Zc/view?usp=sharing
Information/details: https://www.mylgphones.com/lgup-dll-for-lg-v40-thinq-version1-9-39-7.html
Firmware: https://lg-firmwares.com/lg-lmv409n-firmwares/#tab=firmwares

AzzKickah said:
DLL: https://drive.google.com/file/d/1qKRlOFVZMIanphD-jp6dxenCqkaZP2Zc/view?usp=sharing
Information/details: https://www.mylgphones.com/lgup-dll-for-lg-v40-thinq-version1-9-39-7.html
Firmware: https://lg-firmwares.com/lg-lmv409n-firmwares/#tab=firmwares
Click to expand...
Click to collapse
So you didn't flashed the European firmware?

Inerent said:
So you didn't flashed the European firmware?
Click to expand...
Click to collapse
No I didn't. Neocyke told me that radio wouldn't work that way so that would have been useless then. This is the post: https://forum.xda-developers.com/showpost.php?p=80177222&postcount=2
Or did he mean FM Radio......? Because I could live without FM Radio.
The one I did flash is still Korean, but it has no carrier customization. No cellular provider specific apps, no Korean company logo's at startup.
Only thing I noticed is that there still are Korean characters showing right below the numbers in the phone dialer app. But it also shows ABC, DEF, etc.
Oh, and a second clock showing Korean time on the lock screen :silly: which I can't find out how to turn off

AzzKickah said:
No I didn't. Neocyke told me that radio wouldn't work that way so that would have been useless then. This is the post: https://forum.xda-developers.com/showpost.php?p=80177222&postcount=2
Or did he mean FM Radio......? Because I could live without FM Radio.
The one I did flash is still Korean, but it has no carrier customization. No cellular provider specific apps, no Korean company logo's at startup.
Only thing I noticed is that there still are Korean characters showing right below the numbers in the phone dialer app. But it also shows ABC, DEF, etc.
Oh, and a second clock showing Korean time on the lock screen :silly: which I can't find out how to turn off
Click to expand...
Click to collapse
I also have that clock on my V50.
For me it worked with my g7+ Hong Kong international to European and also got volte amd vowifi.
Yes, he was referring to the GSM radio. So this will be risky.
Maybe you should not try. You can check if someone did it with G7....
I also have remembered that I cross flashed my G7 from HK to European, to Korean, back and fourth between them and all was fine.
---------- Post added at 06:16 PM ---------- Previous post was at 05:58 PM ----------
Maybe the V line from LG is risky about radios. Or maybe that was on V35. My point is that this is very risky an you should assume responsibility if flashing. Maybe it's better do not try it.

Inerent said:
I also have that clock on my V50.
For me it worked with my g7+ Hong Kong international to European and also got volte amd vowifi.
Yes, he was referring to the GSM radio. So this will be risky.
Maybe you should not try. You can check if someone did it with G7....
I also have remembered that I cross flashed my G7 from HK to European, to Korean, back and fourth between them and all was fine.
---------- Post added at 06:16 PM ---------- Previous post was at 05:58 PM ----------
Maybe the V line from LG is risky about radios. Or maybe that was on V35. My point is that this is very risky an you should assume responsibility if flashing. Maybe it's better do not try it.
Click to expand...
Click to collapse
You seem to contradict yourself, or do I misunderstand?
You can check if someone did it with G7....
I also have remembered that I cross flashed my G7 from HK to European, to Korean
Click to expand...
Click to collapse
Why check if someone did it if you already did?
I will see how it goes with this firmware for a week or two. If it is all fine, I'll leave it like this.
I don't suspect it will brick the phone though if I flash a European firmware.. As long as you can get into Download-mode, there is not much to worry about I think

AzzKickah said:
You seem to contradict yourself, or do I misunderstand?
Yes, I am also confused.
Why check if someone did it if you already did?
I didn't do it from Korean to European.
I will see how it goes with this firmware for a week or two. If it is all fine, I'll leave it like this.
I don't suspect it will brick the phone though if I flash a European firmware.. As long as you can get into Download-mode, there is not much to worry about I think
For this I was confused. I do believe 50% that it can be done without problems.
Click to expand...
Click to collapse
Anyway, the benefits for European are many. Volte, vowifi, less bloatware, faster speed.
Half of me is screaming to DO IT, while the other half is paranoic!

Inerent said:
Anyway, the benefits for European are many. Volte, vowifi, less bloatware, faster speed.
Click to expand...
Click to collapse
Faster speed..? Please elaborate.
It shows LTE in the status bar though. But I don't know if that is VoLTE.
Now you're making me doubt if I should try a European firmware....
Half of me is screaming to DO IT, while the other half is paranoic!
Click to expand...
Click to collapse
I'm feeling exactly the same right now :laugh:

AzzKickah said:
Faster speed..? Please elaborate.
It shows LTE in the status bar though. But I don't know if that is VoLTE.
Now you're making me doubt if I should try a European firmware....
Click to expand...
Click to collapse
Yes, for my G7 it was faster speeds. Better battery life also.

Inerent said:
Yes, for my G7 it was faster speeds. Better battery life also.
Click to expand...
Click to collapse
What do you think, would this be a good one to try?
V405EBW20a_00_OPEN_EU_DS_0524.kdz
LM-V405EBW...? On my LM-V409N, would that go..?

AzzKickah said:
What do you think, would this be a good one to try?
V405EBW20a_00_OPEN_EU_DS_0524.kdz
LM-V405EBW...? On my LM-V409N, would that go..?
Click to expand...
Click to collapse
I'll search what country has better laws regarding government spying on people. And that firmware I'll choose. Maybe it's the UK, I know that it has forbidden StingRays. Also Deutschland seems OK.

Help! I tried to cross flash my T-Mobile V40 and ended up bricking it.

I ignored the warnings... I know, idiot.
But I went ahead and it completed.
But now the phone has a black screen and nothing else.
When plugged in, my computer recognises it as Qualcomm 9800 port 30.
Still nothing on screen though.
Anyway to get it back? Or get it to stock rom? Really don't want tmobile bloat all over it if possible.

Your only hope would be to get someone who has a T-Mobile v40 to dump all partitions from their phone, and make those partitions available to you.
You would then use 9008 mode to upload partition after partition to your phone. And I'm not even sure that would work.
Enjoy your paperweight / doorstop / skipping stone / table leveler / shim.
[NG]Owner

Double post.

What is it about the T-Mobile version that makes it so different to the others.

NGOwner said:
Your only hope would be to get someone who has a T-Mobile v40 to dump all partitions from their phone, and make those partitions available to you.
You would then use 9008 mode to upload partition after partition to your phone. And I'm not even sure that would work.
Enjoy your paperweight / doorstop / skipping stone / table leveler / shim.
[NG]Owner
Click to expand...
Click to collapse
From what I have seen on some other posts is that can cause the IMEI to return as 0. It may only be if you overwrite the modem partition though, so don't do that. You may only need the T-Mobile bootloader.

shawnmos said:
From what I have seen on some other posts is that can cause the IMEI to return as 0. It may only be if you overwrite the modem partition though, so don't do that. You may only need the T-Mobile bootloader.
Click to expand...
Click to collapse
It's not the modem partition, it's the ftm (and maybe some others too)

I was in a similar situation two days ago; I tried crossflashing my V405UA to T-Mobile and got stuck with no signs of life other than 9008 mode. After a few hours of panicking I was able to figure out how to use QFIL and got things back up and running. I did accidentally wipe my serial number and MAC address in the process from the looks of it, but my IMEI is still intact.
So, I know the V405TA is different from the V405UA and other variants, but I think you can probably get it back through 9008 mode. Feel free to send a PM if you'd like to talk more about it, just keep in mind that I'm far from an expert on any of this. The steps I took were basically:
- Get QFIL and the programmer from here: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
- Backup the necessary partitions (I didn't do this and now I don't have a S/N or MAC address although my IMEI is fine; I'm not sure which partitions you need to save but definitely look into that).
- Grab a copy of https://github.com/ANEP-ET/kdztools, it's a fork of kdztools that can generate rawprogram*.xml files.
- Get a KDZ from somewhere and use the tools to extract it and generate rawprogram*.xml files.
- You might need to edit rawprogram1.xml through rawprogram6.xml; IIRC I had to add "B." to the start of all of the filenames in rawprogram1.xml, "C." to the start of all of the files in rawprogram2.xml, and so on. I didn't have to change rawprogram0.xml.
- Add all of the rawprogram*.xml files in QFIL, I don't think you need a patch.xml (I clicked "Cancel" when asked for a patch file and everything still worked).
- Flash and you should hopefully be good to go.
Keep in mind that I don't really know what I'm doing so be careful and use common sense, this is just what worked for me. Feel free to PM if you want to discuss or have questions and good luck!

aw2a said:
I was in a similar situation two days ago; I tried crossflashing my V405UA to T-Mobile and got stuck with no signs of life other than 9008 mode. After a few hours of panicking I was able to figure out how to use QFIL and got things back up and running. I did accidentally wipe my serial number and MAC address in the process from the looks of it, but my IMEI is still intact.
So, I know the V405TA is different from the V405UA and other variants, but I think you can probably get it back through 9008 mode. Feel free to send a PM if you'd like to talk more about it, just keep in mind that I'm far from an expert on any of this. The steps I took were basically:
- Get QFIL and the programmer from here: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
- Backup the necessary partitions (I didn't do this and now I don't have a S/N or MAC address although my IMEI is fine; I'm not sure which partitions you need to save but definitely look into that).
- Grab a copy of https://github.com/ANEP-ET/kdztools, it's a fork of kdztools that can generate rawprogram*.xml files.
- Get a KDZ from somewhere and use the tools to extract it and generate rawprogram*.xml files.
- You might need to edit rawprogram1.xml through rawprogram6.xml; IIRC I had to add "B." to the start of all of the filenames in rawprogram1.xml, "C." to the start of all of the files in rawprogram2.xml, and so on. I didn't have to change rawprogram0.xml.
- Add all of the rawprogram*.xml files in QFIL, I don't think you need a patch.xml (I clicked "Cancel" when asked for a patch file and everything still worked).
- Flash and you should hopefully be good to go.
Keep in mind that I don't really know what I'm doing so be careful and use common sense, this is just what worked for me. Feel free to PM if you want to discuss or have questions and good luck!
Click to expand...
Click to collapse
Why would you want to flash a T-Mobile stock ROM?

Ainz_Ooal_Gown said:
Why would you want to flash a T-Mobile stock ROM?
Click to expand...
Click to collapse
I'd really like to get Android 10 on my V40, but I don't seem to get OTA updates since AFAICT I have an ATT variant that has been crossflashed to US Cellular (I got it on eBay). Unfortunately the only (stock) Android 10 ROM I can find is for the T-Mobile variant, so I figure I'd give it a go; I know that the T-Mobile variant is a bit different from the others but I thought I'd try anyway since I was curious. In the end, aside from some panic (and a missing S/N and MAC address) no harm was done and I learned a lot, so that's nice. And, hopefully, I can use what I learned to help other people in a similar situation now (even though I'm far from an expert).

aw2a said:
I'd really like to get Android 10 on my V40, but I don't seem to get OTA updates since AFAICT I have an ATT variant that has been crossflashed to US Cellular (I got it on eBay). Unfortunately the only (stock) Android 10 ROM I can find is for the T-Mobile variant, so I figure I'd give it a go; I know that the T-Mobile variant is a bit different from the others but I thought I'd try anyway since I was curious. In the end, aside from some panic (and a missing S/N and MAC address) no harm was done and I learned a lot, so that's nice. And, hopefully, I can use what I learned to help other people in a similar situation now (even though I'm far from an expert).
Click to expand...
Click to collapse
Ahh I see well we do have Android 10 in the flavors of LOS 17.1 and Havoc OS 3.5..

No firehose loader for the T-Mobile one so you can't fix in 9008 mode. It is a paperweight. You need to replace the motherboard.

Bump? Any way to revive it?

slebeau1988 said:
Bump? Any way to revive it?
Click to expand...
Click to collapse
You could try asking tmobile for help and see how much they'll charge you. You may get lucky if the phone is still in warranty

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

Database Develop

welcome