Database Develop

Lenovo a7000 bricked

I have bricked my lenovo a7000 phone. It won't start at all. I had installed twrp . I tried booting into twrp recovery mode, but the screen remains blank. The last battery status I saw was 66 percent. Please help
Another query to the admin of XDA developers
I am using the following procedure to post
I go to this page
http://forum.xda-developers.com/t/lenovo-a7000
then I click, new thread. Then I start my post. I want to know the right procedure to post my queries regarding lenovo a7000

Does sptools detect the phone?

elixir. said:
Does sptools detect the phone?
Click to expand...
Click to collapse
yeah, it does. I did a full stock rom install. took me hours to get things back to normal. Thanks for answering.

archz2 said:
yeah, it does. I did a full stock rom install. took me hours to get things back to normal. Thanks for answering.
Click to expand...
Click to collapse
hi,
From where did you get the stock ROM? I had messed up on a custom ROM and have now ended up with no IMEI and other serial numbers. Unable to connect to any network (both wireless and mobile). Please help.

mohanvgopal said:
hi,
From where did you get the stock ROM? I had messed up on a custom ROM and have now ended up with no IMEI and other serial numbers. Unable to connect to any network (both wireless and mobile). Please help.
Click to expand...
Click to collapse
you can easily find IMEI numbers at the sides of box in which your phone came.
when u get those IMEI numbers.
open engineer mode in your phone. if you dont know how to access it, just download this app called MTK Engineering Mode from here https://play.google.com/store/apps/details?id=com.themonsterit.EngineerStarter&hl=en
open this app, tap on MTK Settings.
then goto CDS Information
then to set IMEI of 'Phone 1' tap on it, Here you can see a command line with “AT+”.
Now just add this command to it EGMR=1,7,”IMEI NO” And press “send at command” button. [ if you want to change the the phone 2 IMEI AT+EGMR=1,10,”NEW IMEI NO”]
restart your phone.
n u are all set.
you can check your IMEI by just dialing *#06#
HIT THANKS IF WORKED

mohanvgopal said:
hi,
From where did you get the stock ROM? I had messed up on a custom ROM and have now ended up with no IMEI and other serial numbers. Unable to connect to any network (both wireless and mobile). Please help.
Click to expand...
Click to collapse
You can find the stock rom in this post. Press thanks if found useful.
http://forum.xda-developers.com/showthread.php?p=60588846
To restore IMEI number, root your phone then use chamelephon app to restore your IMEI numbers.

archz2 said:
You can find the stock rom in this post. Press thanks if found useful.
http://forum.xda-developers.com/showthread.php?p=60588846
Click to expand...
Click to collapse
Hi,
I have downloaded the stock ROM, and when flashing that I had landed into the current problem.
my bad. i should have been little extra careful while flashing.
Also I have got an OTA for S149 now. has anyone else got it?
and I am still have not overcome the IMEI issue.
---------- Post added at 08:24 PM ---------- Previous post was at 08:08 PM ----------
archz2 said:
To restore IMEI number, root your phone then use chamelephon app to restore your IMEI numbers.
Click to expand...
Click to collapse
finally set the IMEI numbers using Chamelephon app. Not sure if it would get erased during next phone reset. Let me wait till I mess up again.

mohanvgopal said:
Hi,
I have downloaded the stock ROM, and when flashing that I had landed into the current problem.
my bad. i should have been little extra careful while flashing.
Also I have got an OTA for S149 now. has anyone else got it?
and I am still have not overcome the IMEI issue.
---------- Post added at 08:24 PM ---------- Previous post was at 08:08 PM ----------
finally set the IMEI numbers using Chamelephon app. Not sure if it would get erased during next phone reset. Let me wait till I mess up again.
Click to expand...
Click to collapse
Your next phone reset will be after months I guess? Why worry? Enjoy the moments of your phone working perfectly

touch issue
I've got a weird issue with my touch. Its on s149
I tried to draw straight horizontal lines but it comes as a curvy lines...... But when I draw vertical lines it doesn't come curvy ....
Can someone tell me if its a hardware issue or a software issue.
I don't know how to attach an image .... So if someone could tell me how to attach an image I'll attach the screenshot

Same problem i am facing , not even twrp recovery mode shows

Phones IMEI changed without even touching it

I have this problem - my G800F changed it's IMEI to 350695200123951. When that happened I had not touched it (no root, no nothing) at evening I still was able to make calls, but later that night it showed 'not registered on network'. I have tried factory reset, reinstalling the firmware using Kies, then I used odin, tried to make EFS backup and restore, but so far I haven't had any success. So I thought that some of you brilliant minds could help me, maybe there is a way to change the IMEI in efs backup file? The only strange thing that happened to my phone couple of days before this happened is that some random number from Ukraine called me, but for obvious reasons I did not answer it nor did I call it back. So now I'm stuck using my fathers old HTC Wildfire S, I really hope that you could help me, because I want my phone back.

SOS
Sorry no answer from me but exactly the same thing with my S5 mini g800F last week (end Sept), with exactly the same false IMEI, and I think I have now tried everything. No luck. Not the Ukraine phone call though!
Cannot get into "engineermode" which may have been a way to fix this. I loaded a new firmware, still nothing. ANY help will be appreciated but please nothing that asks me to add a "secret code" as the phone does not respond to those. I'm not an expert but got desperate enough to try my hand at a terminal emulator, it did not work. Stopped short of using SDK as the download is huge. Firmware now loaded is android 4.4.2 build number KOT49H.G800FXXU1AOG2. Heeeeelp anybody! The vendor is of no use either, just mumbling "this is a very strange thing, where did you get the phone....." (bought from the guy asking!!)

Warranty service restored the original IMEI
KVE123 said:
Sorry no answer from me but exactly the same thing with my S5 mini g800F last week (end Sept), with exactly the same false IMEI, and I think I have now tried everything. No luck. Not the Ukraine phone call though!
Cannot get into "engineermode" which may have been a way to fix this. I loaded a new firmware, still nothing. ANY help will be appreciated but please nothing that asks me to add a "secret code" as the phone does not respond to those. I'm not an expert but got desperate enough to try my hand at a terminal emulator, it did not work. Stopped short of using SDK as the download is huge. Firmware now loaded is android 4.4.2 build number KOT49H.G800FXXU1AOG2. Heeeeelp anybody! The vendor is of no use either, just mumbling "this is a very strange thing, where did you get the phone....." (bought from the guy asking!!)
Click to expand...
Click to collapse
Just couple of days ago got my phone back from warranty and they fixed it (thought they wouldn't since it was rooted), so I would suggest doing the same thing. At the warranty center I had to explain my problem for about 30 minutes, because they believed that phone couldn't change its IMEI. Also you could try other service centers, because some of them said that they could fix this problem for about 30-50 EUR. I believe the only thing that could help otherwise is something like the z3x box, but it would be more expensive as it costs 100+ USD.

If you download the original stock firmware you can flash the IMEI number back to the phone

:S
No solution has been under warranty , the pochaine time to think about backup your EMEI

Yes yes
there is a backup somewhere between all my external hard drives, memory sticks, cloud servers... And i can't find it, too long ago and too many passwords!! But, no use telling me now to make a "pochaine" backup. I will try the reflash to older version suggestion, and see whether that gives me access to the required features. If not, it is the mountain to climb, of getting to the samsung "support" to tinker with the phone. Glad you you are sorted sunciks. A person from xda did contact me, so lets see if that bears fruit.

KVE123 said:
there is a backup somewhere between all my external hard drives, memory sticks, cloud servers... And i can't find it, too long ago and too many passwords!! But, no use telling me now to make a "pochaine" backup. I will try the reflash to older version suggestion, and see whether that gives me access to the required features. If not, it is the mountain to climb, of getting to the samsung "support" to tinker with the phone. Glad you you are sorted sunciks. A person from xda did contact me, so lets see if that bears fruit.
Click to expand...
Click to collapse
A back up of your phone? I would suggest just making a new back up because it's less time consuming.

BUP
irontaco1 said:
A back up of your phone? I would suggest just making a new back up because it's less time consuming.
Click to expand...
Click to collapse
You are going to have to be patient with an old person here. Making a backup of the current situation? Will it not just copy the existing false IMEI and replace on restore? Please be specific, step by step, as you would for a kid. Regards

KVE123 said:
You are going to have to be patient with an old person here. Making a backup of the current situation? Will it not just copy the existing false IMEI and replace on restore? Please be specific, step by step, as you would for a kid. Regards
Click to expand...
Click to collapse
Nope it shouldn't. The IMEI number is installed with the firmware. So if you back it up and factory reset, it should fix it.
---------- Post added at 01:43 PM ---------- Previous post was at 01:39 PM ----------
KVE123 said:
You are going to have to be patient with an old person here. Making a backup of the current situation? Will it not just copy the existing false IMEI and replace on restore? Please be specific, step by step, as you would for a kid. Regards
Click to expand...
Click to collapse
If factory reseting doesn't work, then I suggest flashing the firmware manually.

BUP
OK I have tried this before, but just tried again. Does not work or I'm not doing it correctly.

What's the model number?

Reflash
KVE123 said:
OK I have tried this before, but just tried again. Does not work or I'm not doing it correctly.
Click to expand...
Click to collapse
Meaning tried to backup and factory reset. Now in process of manual flashing (via Kies). Previously found that Kies would download for an hour and then say "unexpected error...." so have not used it in more than two years. Anyway here we go again.
Model is SD-G800F [samsung galaxy s5 mini]
---------- Post added at 04:20 PM ---------- Previous post was at 04:09 PM ----------
KVE123 said:
Meaning tried to backup and factory reset. Now in process of manual flashing (via Kies). Previously found that Kies would download for an hour and then say "unexpected error...." so have not used it in more than two years. Anyway here we go again.
Model is SD-G800F [samsung galaxy s5 mini]
Click to expand...
Click to collapse
Correction = SM-G800F

KVE123 said:
Meaning tried to backup and factory reset. Now in process of manual flashing (via Kies). Previously found that Kies would download for an hour and then say "unexpected error...." so have not used it in more than two years. Anyway here we go again.
Model is SD-G800F [samsung galaxy s5 mini]
---------- Post added at 04:20 PM ---------- Previous post was at 04:09 PM ----------
Correction = SM-G800F
Click to expand...
Click to collapse
So you get an error when backing it up?

kies
irontaco1 said:
So you get an error when backing it up?
Click to expand...
Click to collapse
No, I mean downloading the firmware upgrade. It will download the new files but not install. This was long ago. Right now I get to tools to upgrade and initialise and get the message "does not support initializing" I give up!

No don't give up, just download the firmware and flash it with ODIN. If you need my to explain that, leave me an email and I'll send you the instructions.

irontaco1 said:
No don't give up, just download the firmware and flash it with ODIN. If you need my to explain that, leave me an email and I'll send you the instructions.
Click to expand...
Click to collapse
What you propose was the second thing I did. The first was doing a factory reset with the older version of the firmware (what the phone came out with). Neither steps worked. The firmware I flashed was (Build number) KOT49H.G800FXXU1AOG2. Which btw Kies indicates as the latest version.

Don't use kies
---------- Post added at 05:09 PM ---------- Previous post was at 04:50 PM ----------
The only reason I need an email from you is because XDA won't let me post links. The instructions I'm providing contain links so you can fix your problem.

email
[/COLOR]The only reason I need an email from you is because XDA won't let me post links. The instructions I'm providing contain links so you can fix your problem.[/QUOTE]
Kies does not work anyway
Can do (email) but not on this open forum. Use the private messages
Added edit in wrong place but, given the phone to samsung tech. Will post the outcome somewhere next week

irontaco1 said:
Don't use kies
---------- Post added at 05:09 PM ---------- Previous post was at 04:50 PM ----------
The only reason I need an email from you is because XDA won't let me post links. The instructions I'm providing contain links so you can fix your problem.
Click to expand...
Click to collapse
Can you help me please, i have the same probleme one week ago, without solutions, i pm you, please help me!

same problem here

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!=)

Can't access ProjectMenu

Hey there! So I have a problem. I was trying to go back to stock with a guide in this post: https://forum.xda-developers.com/p9/development/rom-huawei-p9-magic-rainbow-t3601064 . When I flashed update.zip, I was stupid enough to reboot my phone. Everything was looking fine. Untill I tried to access the projectmenu to se the USB mode to Manufacture mode. I entered this code into my dialer: *#*#2846579#*#* . The dialer just went back to the recent calls menu. So I tried to update, but the update failed. The last thing I tried was to flash the stock rom again with dload, but the problems kept occuring. I hope someone can help me, because I'm clueless.

Were you able to solve this? Im currently having issues with magiskhide which could be because of logging not being turned on so I tried to access the project menu and just like you said, it goes right back to the call log without the project menu popping up

what build number? if build number are different from original , then project menu can work, and can not

Arnys said:
what build number? if build number are different from original , then project menu can work, and can not
Click to expand...
Click to collapse
What do you mean different from original?
I'm on FRD-L09C432B407
That's an Honor 8 but if you have a fix it might still work

JimZiii said:
What do you mean different from original?
I'm on FRD-L09C432B407
That's an Honor 8 but if you have a fix it might still work
Click to expand...
Click to collapse
did you tried reset? https://www.youtube.com/watch?v=MNhwQQDrolY
(all files will be deleted, backup them)

Arnys said:
did you tried reset? https://www.youtube.com/watch?v=MNhwQQDrolY
(all files will be deleted, backup them)
Click to expand...
Click to collapse
Yes, didn't help

Did you find a solution for this? I’m having exactly the same problem. Already tried a factory-reset but without success.

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