Develop Bugs

Programme A exit after "Getting data from Device"

I tried load a rom image using the OSImage tools. When execting the Programme A it goes to the step of "Getting data from device and just quit - no error .. nothing"
Any advice?

asuming that you mean for xda1 because that program does NOT work with xda2's
then this guide have never failed me
Ok here you go, its a little outdated but its what I still use:
Qman's how to use XDArit to write nk.nb1 or nk.nbf to your SD card aka the Bootloader Method!
1. Place XDArit and the nk.nb1 or nk.nbf file in the same folder and start XDArit.
2. Select your SD card (disk drive) from the drop down menu.
3. Select Write to SD
Notice that the Windows CE box is already checked so just click the browse button at the end of that window.
4. Select your (nk.nb1 or nk.nbf) image and then Open
Notice by default XDArit will open looking for a *.nb1 file but if you're going to use a .nbf file you'll have to manually change the "Files of Type" to *.nbf
Notice that nk.nbo / nk.nbo was automatically added as your boot-loader and its check box is unchecked so leave it that way and click OK. XDArit should start writing to the card.
When XDArit has finished writing the image put the SD-card into the XDA and hold the power button and soft reset. You'll be taken to the below screen:
SD DOWNLOAD
Card Type:
CE OS & BOOT
Press action to Download
Or
Press REC to Exit
Press action to download and it will start the download/restore from the SD card.
Follow the on screen instructions once its "Completed" which will consist of a "Soft Boot/Reset".
Click to expand...
Click to collapse

Can't write to the SD
Thanks for your reply, however I can't write the SD memory - when trying, I got: Error in opening device...
I tried using the OSIMAGETOOL to write to the memory directly and I get an error : Access denied. see attached image...
Any clue??
Thanks
Rudegar said:
asuming that you mean for xda1 because that program does NOT work with xda2's
then this guide have never failed me
Ok here you go, its a little outdated but its what I still use:
Qman's how to use XDArit to write nk.nb1 or nk.nbf to your SD card aka the Bootloader Method!
1. Place XDArit and the nk.nb1 or nk.nbf file in the same folder and start XDArit.
2. Select your SD card (disk drive) from the drop down menu.
3. Select Write to SD
Notice that the Windows CE box is already checked so just click the browse button at the end of that window.
4. Select your (nk.nb1 or nk.nbf) image and then Open
Notice by default XDArit will open looking for a *.nb1 file but if you're going to use a .nbf file you'll have to manually change the "Files of Type" to *.nbf
Notice that nk.nbo / nk.nbo was automatically added as your boot-loader and its check box is unchecked so leave it that way and click OK. XDArit should start writing to the card.
When XDArit has finished writing the image put the SD-card into the XDA and hold the power button and soft reset. You'll be taken to the below screen:
SD DOWNLOAD
Card Type:
CE OS & BOOT
Press action to Download
Or
Press REC to Exit
Press action to download and it will start the download/restore from the SD card.
Follow the on screen instructions once its "Completed" which will consist of a "Soft Boot/Reset".
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Saving files in nano editor

I wanted to edit my build.prop file but have a problem saving it.
I press Ctrl+O (Ctrl being the Vol-Down button) to open the write file dialog. Then I specify a filename but what to do next? Pressing the enter button doesn't do anything. I can change the file name but still enter does nothing.
Is there a specific command needed to write to the file? It's probably not file access settings, because the same happens when I choose a file from the sdcard.

TOLTESPR / SM-N910P hard brick trials and solution (mmc_read failed)

Greets all,
Apologies in advance for the longer post.
TLDR: Writing the debrick-n910p.img image to SDcard using Windows (10 x86_64) for me caused my hard bricked SM-N910P / Sprint Samsung Galaxy Note 4 to endlessly boot-loop (displaying BOOT RECOVERY MODE / CHECK BOOT PARTITIONS.. / COPY FROM T-FLASH.. / BOOT RECOVERY / WRITE 188416 sectors / REBOOT). I found my solution for this issue to be that as long as I wrote the debrick-n910p.img image in Windows (10 x86_64), then booted into Linux and wiped the GPT data structures on the SDcard only to convert the SDcard to basic MBR (+DOS compatible flag), then created & formatted a single 32GB partition as FAT32, then and only then, write the debrick-n910p.img image file to the SDcard in this way, I was able to save my hard-bricked phone flawlessly!
I ran into the "mmc_read failed" issue that many posters to this site have experienced. I wanted to add the solution that worked for me along with the issues I ran into, as a reference for myself if I ever need it again in the future, and to pass on the information in the event others may find it helpful.
In all my trials and research I never found a point-by-point / exact instructions for the SM-N910P / Sprint Samsung Galaxy Note 4, nor anyone running into the same issue(s) that I did. that's what this post is => links to others solutions, my experience, and my solution for a hard-bricked SM-N910P / Sprint Samsung Galaxy Note 4.
SCENARIO: After ~6months of owning my phone I bought from craigslist it started experiencing random lagging, then random reboots, and ultimately the phone failed to boot into the OS one day. So I booted up TWRP, did a full-wipe and fresh OS load. after the OS flash (like I've done a million times, nothing different/strange) the device was set to reboot, then the screen went dark, and never came back on. just poof. it would flat-out not boot again; no LED during charging, nothing would happen when attempting to power on the phone, or any attempt to try booting recovery (Home+Vol-Up+Power) or to Odin/Kies download-mode (Home+Vol-Down+Power). To me the phone was dead, I considered it the "true brick". Yet, I wondered at the most curious thing that would happen when I connected the phone to my computer via the microUSB cable without the battery; I would hear the "new device attached" Windows chime, and Device Manager would list a new "Qualcomm HS-USB QDLoader 9008" device. otherwise, the phone remained dark, and completely void of any life.
At this point I started researching to purchase a replacement cellphone when a website caught my eye with the title "Qualcomm Snapdragon Unbrick Guide, Snapdragon’s are UNBRICKABLE".
I skimmed over the text, and began thinking it possible to revive my (broken?) phone - I just desired a straight-forward HOWTO describing the procedure how I could resurrect my phone, and I figured I would be on my way.
In the end, I found some promising posts, and the very SM-N910P debrick image itself (see below for links), but never found a step-by-step for my exact model of phone.
N910P Debrick Image + Useful Links
Mega Link to the N910P debrick image (128MB)
Samsung N910P Galaxy Note 4 Sprint USA Repair Firmware (N910PVPU4COG5_SPT4COG5_Sprint_USA_v5.1.1_Repair_Firmware.zip)
Win32DiskImager (Project Homepage) (v0.9 binary)
dd for windows
Galaxy Note 4 Unbrick/Debrick.img for N910G/F/T/W8 [unbrick] [unbrick image]
[*]- Inside, a reference For N910P refer this thread​
Galaxy Note 4 N910T FIXED HARD BRICKED
SM-N910P (US-Sprint) debrick.img
All instructions seemed to state I needed a 16GB or larger SDcard, so I went out and purchased a brand new 128GB MicroSDXC card, specifically Samsung MicroSDXC EVO Memory Card w/ Adapter 128GB (2017 Model) - Model: MB-MP128G / Model Code: MB-MP128GA/AM
The gist of all the reports on how to fix my issue was to write the N910P debrick image to a micro SDcard and magically the phone would come back to life. And so, I did just that. In my case using Windows 10 x86_64 - using the suggested applications to write the image to the SDcard: Win32DiskImager and/or dd for windows, then popping the SDcard into the "dead" phone, attaching the battery to the phone and pushing power - or one of the 3 finger salutes (recovery/download-mode) - then the magic would happen, the screen would show the following text:
Code:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
BOOT RECOVERY
WRITE 188416 sectors
REBOOT
But, unfortunately for me, that is all it would do, I would keep seeing that text over and over... If I let the "COPY FROM T-FLASH.." appear then press one of the 3 finger salutes (recovery -or- download-mode), the phone would just reboot before it displayed the rest, and continue back in it's loop:
Code:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
BOOT RECOVERY
WRITE 188416 sectors
REBOOT
This just kept occurring over, and over with infinite reboots. Yet, ALL the documentation said it would ultimately boot into download-mode, I just had to "put it in the freezer to let the phone cool" (never mind that the phone wasn't hot AT ALL) for an hour or something similar?? All my searching found nobody else with this issue (at least no one reporting it). So I am reporting it and also reporting how I fixed my sorry state of affairs.
As I noted above, I was using Windows 10 x86_64 as the OS and Win32DiskImager, as well as dd for windows, to write the debrick image to the SDcard up to this point. This was my process:
:: Windows 10 ::
place SDCARD in drive
format the SDCARD (drive d:/f:, whichever) through Windows Explorer (explorer.exe) via RIGHT-CLICK on drive -> Format ...
capacity 119GB / Filesystem: exFAT / Allocation Size: drop-down = Default Allocatio-- n Size
CHECK Quick Format
click Start button
click OK
click OK when finished
click Close button
in Windows Explorer (explorer.exe), RIGHT-CLICK on SDCARD drive -> Eject
eject SDCARD from computer
- EITHER Win32DiskImager OR dd for windows, only do 1.
:: Win32DiskImager ::
run Win32DiskImager as Administrator
DEVICE = drive of the SDCARD (D:/F:, whichever)
IMAGE FILE = click FOLDER icon, select "debrick-n910p.img"
click WRITE button
click OK
at Write Successful = click OK
more then likely (win10) a ****-ton of Explorer screens pop up, with errors like "You need to format the disk in Drive ? before you can use it" pops up
IGNORE ALL THIS, ALT-F4 to close ALL the pop-ups and errors
OR just REBOOT, as at this point we are done
Shutdown Windows (10) -> REBOOT
:: dd for windows ::
open "cmd" as Administrator
dd --list
dd if=debrick-n910p.img of=\\.\Volume{3fde94fa-d22d-11e7-b791-806e6f6e6963} bs=1M
Once the debrick-n910p.img file is finished being written to the SDcard, 27 partitions (what appears to be mostly duplicate) will show up and all drive letters will get filled, being displayed as mostly unreadable, that is just the nature of what the debrick image is.
My Solution to this situation was as follows:
:: LINUX ::
boot linux from USB -or- CD (I booted a handy USB stick with Qubes OS v4-rc3, choose Troubleshooting -> Rescue a Qubes System)
upon boot, choose "3" to be dropped to shell
mount windows folder that holds the debrick N910P image = mount /dev/sda2 /mnt/sysimage
place SDCARD in drive
fdisk -l << make sure your SDcard shows up (/dev/mmcblk0) is there
cgdisk /dev/mmcblk0
delete ALL paritions (using "d" on each highlighted partition)
"New"
Fist sector = hit ENTER (choose default = 2048 for me)
Size in sectors = 32G
Hex code = 0700 (Microsoft basic data)
Partition name = hit ENTER
"Write"
type "yes"
"Quit"
gdisk /dev/mmcblk0
should display = "Found valid GPT with protective MBR; using GPT"
"x" (extra functionality (experts only))
"z" (zap (destroy) GPT data structures and exit)
"Y" (Yes to continue)
"N" (blank out MBR)
fdisk /dev/mmcblk0
"p" (print parition table)
"c" (toggle dos compatibility flag)
should show DOS COMPATABILITY FLAG SET (DEPRICATED)
"d" (delete partition)
MAKE SURE NO PARTITIONS EXIST!
"n" (new partition)
"p" (primary)
hit ENTER (default = "1")
hit ENTER (first sector, my default was 63)
"+32G" (last sector, this creates 32GB partition)
"a" (toggle bootable flag, should show "the bootable flag on partition 1 is enabled now")
"t" (partition type)
"c" (W95 FAT32 (LBA))
"w" (write table to disk and exit)
Format the new partition, FAT32
mkfs.fat -F 32 /dev/mmcblk0p1
Goto the folder containing the debrick N910P image
cd /mnt/sysimage/Users/$USER/Downloads/SM-N910P-trltespr
dd if=debrick-n910p.img of=/dev/mmcblk0 bs=1M
sync
Eject sdcard and place in your Note 4 phone
This time, when I put the battery in the phone, I got the same text as before:
Code:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
BOOT RECOVERY
WRITE 188416 sectors
REBOOT
And then, it did a REAL reboot, and went directly to download-mode!
I tested this multiple times - as long as I wrote the debrick image in Win10, and then erased the SDcard and formatted it as Fat32 without using GPT just a basic MBR, and wrote the debrick image that way in linux it worked flawlessly!
let it boot, then do it's reboot
should be able to go into RECOVERY = Home+Vol-Down+Power !!!
:: Boot Windows ::
unzip "N910PVPU4COG5_SPT4COG5_Sprint_USA_v5.1.1_Repair_Firmware.zip"
run Odin3 3.09
click PIT button -> select "TRLTE_USA_SPR.pit" -> click OPEN
click AP button -> select "ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB5691107_REV00_user_low_ship_MULTI_CERT.tar.md5" -> click OPEN
phone should be in DOWNLOAD mode (home+vol-down+power -> UP to continue) and connected via microUSB, Odin3 should be detecting it with a BLUE ID:COM lit up on top-left
click START button in Odin3
when finished it will reboot, and all should be well
- One last note, about the "mmc read fail" error, I took this gentleman's advice:
As a side note....
IF YOU HAVE THE MMC READ FAIL MESSAGE!!!
Which consists of Random Reboots, Heating Issues when theirs hardly no apps on, or even Lag or Glitchyness.
The Temp FiX that I've been using everyday and haven't had these issues since was downloading this app
WakeLock Manager and setting to PARTIAL LOCK! on Level 4.
Click to expand...
Click to collapse
And am currently running Wake Lock - PowerManager from Google Play as suggested, just to be safe - and so far, I have not YET had to deal with that horrid business again (so far, fingers crossed).
And there ye have it, that is my story, my tribulations, and my fix. Thank you to all who came before me, and for everyone's good advice = Good luck to all, and have a great rest of 2017.

XORr0 said:
[*]mount windows folder that holds the debrick N910P image = mount /dev/sda2 /mnt/sysimage
Click to expand...
Click to collapse
Hi man, thank you for the post, but can´t mount the sysimage
Help me please!!!

Mega Link a la imagen de debrick N910P ( 128MB )
the files are not there if it is not too much trouble to provide me with the: confusing files: confusing

[MTK][woods][Moto E4] Increase Recovery partition

Hello guys!!! I'm back with super cool guide about increasing recovery partition.
Recovery: This partitions hold the files that allow one to enter ‘recovery mode’, which is essentially a second boot partition that allows one to apply OTAs, make/restore backups, and install ROMs or root binaries. This partition will either hold the stock recovery, or a custom recovery. Custom recoveries can be flashed and allow the user to back up, restore, install to and wipe other partitions, among other features. This partition can be safely modified but ensure to always have a stock recovery flashed when applying stock OTAs.
You may ask why I need to increase recovery partition?
The Answer is: Some recoveries like Orange Fox, PitchBlack need around 24-27 Mb size but OEM packed with 16Mb recovery.
So that's why I need to increase partition size.
Code:
/*
* First Take a Full Backup.
* Im not responsible for anything that may happen to your phone by doing this experiment.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
*/
Ok as I mention earlier first take a full backup of your system. In this process we need to delete all the partitions.
Let's start the process​
Step
Now use this Script to back up nvram nvdata frp ... etc partitions. (Usage is given in README)
Step
download this scatter file
Step
Put The scatter file into existing Stock rom folder
Step
Now Open the Spflash tool
Step
Select the new scatter file in spflash tool
Step
Now Select Format all + Download option (by default its select Download only option) & start the flashing process.
Now if you switch on your phone than your imei and baseband will not work.
Follow Guide A if you got backup from that script.
Follow Guide B if you not got backup from that script.
While in spflash tool, Press Ctrl+Alt+V to open advanced mode
Go to window->write memory and another tab with name Write Memory will appear next to Memory test.
If you don't know how to do the above step only watch this video for enabling Write Memory Tab click this link
Guide A
Go to Write memory :
In file path->select efuse.img
Begin address (HEX) : 0xAB80000
Regin: EMMC_USER
Then press button Write memory
Plug USB cable
Now Proceed with other files in same way
In file path->select hw.img
Begin address (HEX) : 0xED80000
Regin: EMMC_USER
Then press button Write memory
Plug USB cable
In file path->select oem.img
Begin address (HEX) : 0xF580000
Regin: EMMC_USER
Then press button Write memory
Plug USB cable
In file path->select persist.img
Begin address (HEX) : 0x7B80000
Regin: EMMC_USER
Then press button Write memory
Plug USB cable
In file path->select utags.img
Begin address (HEX) : 0xAC00000
Regin: EMMC_USER
Then press button Write memory
Plug USB cable
In file path->select nvram.img
Begin address (HEX) : 0x380000
Regin: EMMC_USER
Then press button Write memory
Plug USB cable
In file path->select secro.img
Begin address (HEX) : 0x6380000
Regin: EMMC_USER
Then press button Write memory
Plug USB cable
In file path->select frp.img
Begin address (HEX) : 0xAC80000
Regin: EMMC_USER
Then press button Write memory
Plug USB cable
In file path->select nvdata.img
Begin address (HEX) : 0xAD80000
Regin: EMMC_USER
Then press button Write memory
Plug USB cable
Now you have imei and baseband!
Enjoy!
Guide B
Download this file click this link & unpack it.
Go to Write memory :
In file path->select efuse.img
Begin address (HEX) : 0xAB80000
Regin: EMMC_USER
Then press button Write memory
Plug USB cable
Now Proceed with other files in same way
In file path->select hw.img
Begin address (HEX) : 0xED80000
Regin: EMMC_USER
Then press button Write memory
Plug USB cable
In file path->select persist.img
Begin address (HEX) : 0x7B80000
Regin: EMMC_USER
Then press button Write memory
Plug USB cable
In file path->select utags.img
Begin address (HEX) : 0xAC00000
Regin: EMMC_USER
Then press button Write memory
Plug USB cable
Now Also there are two ways either you can follow one.
Method 1
Now install custom recovery and flash magisk.
Now install custom recovery and flash magisk.
After got baseband number use toolhero app.
Make sure you have data connection.
Click on IMEI wait for few seconds it will ask root access, grant access and set whatever IMEI number you want after that click modify. It will open share tab click any sharing media just for facking give message and back to toolhero now click on modify again.
This time it will ask to reboot. Reboot and see the IMEI number.
If the above method not worked follow the second method.
Method 2
Download this Nvram Database file click here
Now download the SNWritter tool & use the above file. (follow any snwritter guide on youtube.)
Credits : @vishalk17
www.lenovoroot.com
@Zumairmhd
Please hit a like if it is all success :good::good::good:​

Getting access to recovery combination(FTM mod)

* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
Click to expand...
Click to collapse
This is instruction is for carrier devices that have disabled button combo's.
Prerequisites:
1) Knowledge
2) Unlocked bootloader
3) Write down your IMEI and SN somewhere
4) QPST
How to check NT Code:
1) In dialer call *#546368#*model#. Put your model number instead 'model'. Example *#546368#*500# for V500N
2) Go SVC Menu -> Version info.
3) Write down your NT Code
Booting into EDL mode:
1) Plug in your turned on phone to PC
2) Press and hold Power+Volume Down
3) As soon as your screen is blank, rapidly start pressing Volume Up.
4) If you've successfully booted into EDL, your screen will be completely blank and the device manager will show (Under COM Ports): Qualcomm HS-USB QDLoader 9008
Backing up stock FTM:
1) Open QFIL
2) Select build type - Flat build
3) Storage type - UFS (Right corner at the bottom)
4) Programmer path - choose firehose that you downloaded from attachments
5) Go Tools->Partition Manager->OK
6) Press right mouse button at FTM -> Manage Partition Date -> Read Data
7) Look for backup folder in log and copy your ReadData*.bin file into another folder. Rename it to make it easier
Modifying FTM:
1) Download and install HxD from attachments
2) Download and open ftm_v50_mod.bin
3) At the offset 0000D000 put your IMEI. You won't miss it, you'll see IMEIIMEIIMEIIME at decoded side)
4) At the offset 00012000 put your SN. You won't miss it, you'll see SNSNSNSNSNSNSN at decoded side)
5) At the offset 00014000 put your NT code's last number instead of both 'xx' at decoded side
6) Flash it back. Repeat steps of backing up part, but this time choose Load Data instead of Read Data then pick your modified file.
Congrats! You get back recovery button combo
People who helped me with that:
vl48
@SGCMarkus
@Awesomeslayerg

yulbax said:
This is instruction is for carrier devices that have disabled button combo's.
Prerequisites:
1) Knowledge
2) Unlocked bootloader
3) Write down your IMEI and SN somewhere
4) QPST
How to check NT Code:
1) In dialer call *#546368#*model#. Put your model number instead 'model'. Example *#546368#*500# for V500N
2) Go SVC Menu -> Version info.
3) Write down your NT Code
Booting into EDL mode:
1) Plug in your turned on phone to PC
2) Press and hold Power+Volume Down
3) As soon as your screen is blank, rapidly start pressing Volume Up.
4) If you've successfully booted into EDL, your screen will be completely blank and the device manager will show (Under COM Ports): Qualcomm HS-USB QDLoader 9008
Backing up stock FTM:
1) Open QFIL
2) Select build type - Flat build
3) Storage type - UFS (Right corner at the bottom)
4) Programmer path - choose firehose that you downloaded from attachments
5) Go Tools->Partition Manager->OK
6) Press right mouse button at FTM -> Manage Partition Date -> Read Data
7) Look for backup folder in log and copy your ReadData*.bin file into another folder. Rename it to make it easier
Modifying FTM:
1) Download and install HxD from attachments
2) Download and open ftm_v50_mod.bin
3) At the offset 0000D000 put your IMEI. You won't miss it, you'll see IMEIIMEIIMEIIME at decoded side)
4) At the offset 00012000 put your SN. You won't miss it, you'll see SNSNSNSNSNSNSN at decoded side)
5) At the offset 00014000 put your NT code's last number instead of both 'xx' at decoded side
6) Flash it back. Repeat steps of backing up part, but this time choose Load Data instead of Read Data then pick your modified file.
Congrats! You get back recovery button combo
People who helped me with that:
vl48
@SGCMarkus
@Awesomeslayerg
Click to expand...
Click to collapse
For correct work in my LMV500EM need repeat NT code's last number in offset 00014020 - where was "xx"

It can't use for imei recording, please don't try imei recording, imei won't work

I can enter fastboot after flash different Android version kernel

Mr.PvT said:
It can't use for imei recording, please don't try imei recording, imei won't work
Click to expand...
Click to collapse
This guide was not for changing IMEI, read article. If you won't write down your imei you'll lose your reception

can fix imei 0??

yulbax said:
How to check NT Code:
1) In dialer call *#546368#*model#. Put your model number instead 'model'. Example *#546368#*500# for V500N
2) Go SVC Menu -> Version info.
3) Write down your NT Code
Click to expand...
Click to collapse
This does not make NT code available in Verizon LM-V450VM.
I can get a Hidden Menu using **228378 but it does not have "Version info"
Any ideas?

can you help me fix CSN v500n =((

i'm try but not working

Hello. I have a lg v60 att mobile, I crossflahed it with android 12 v30c, everything worked fine, only there was no nt code. I decided to flash pdm with lg up and it stuck on blue screen. Then I put it into Qualcomm 9008 mode and accidentally deleted all the files. Then they restored it with medusa pro direct v30c eu and now I have no baseband imei and serial number. Can anyone help ?

can you please explain what last part xx of NT Code means? My version Info keeps crashing but shows should be implemented. I took a screen of startup nt mismatch. I read somewhere this info can be used. Should or could I copy and paste from a different ftm file that doesn't have error? I see 15 listed in the ftm that gives no error and "15" listed in one that gives error. I did notice that the bands are available in the error one and not in the no code throwing nt code ftm file.
No Error Code has :
"15","310,410,FFFFFFFF,FFFFFFFF,FF","310,150,FFFFFFFF,FFFFFFFF,FF","310,170,FFFFFFFF,FFFFFFFF,FF","311,180,FFFFFFFF,FFFFFFFF,FF","310,560,FFFFFFFF,FFFFFFFF,FF","310,030,FFFFFFFF,FFFFFFFF,FF","310,280,FFFFFFFF,FFFFFFFF,FF","310,950,FFFFFFFF,FFFFFFFF,FF","313,100,FFFFFFFF,FFFFFFFF,FF","312,670,FFFFFFFF,FFFFFFFF,FF","313,110,FFFFFFFF,FFFFFFFF,FF","313,120,FFFFFFFF,FFFFFFFF,FF","313,130,FFFFFFFF,FFFFFFFF,FF","313,140,FFFFFFFF,FFFFFFFF,FF","901,44F,FFFFFFFF,FFFFFFFF,FF"
FTM With Error Code has:
"15","310,260,FFFFFFFF,FFFFFFFF,FF","310,310,FFFFFFFF,FFFFFFFF,FF","310,490,FFFFFFFF,FFFFFFFF,FF","310,660,FFFFFFFF,FFFFFFFF,FF","310,800,FFFFFFFF,FFFFFFFF,FF","310,200,FFFFFFFF,FFFFFFFF,FF","310,210,FFFFFFFF,FFFFFFFF,FF","310,220,FFFFFFFF,FFFFFFFF,FF","310,230,FFFFFFFF,FFFFFFFF,FF","310,240,FFFFFFFF,FFFFFFFF,FF","310,250,FFFFFFFF,FFFFFFFF,FF","310,160,FFFFFFFF,FFFFFFFF,FF","310,270,FFFFFFFF,FFFFFFFF,FF","310,120,FFFFFFFF,FFFFFFFF,FF","312,530,FFFFFFFF,FFFFFFFF,FF"
Thanks in advance

rikita said:
This does not make NT code available in Verizon LM-V450VM.
I can get a Hidden Menu using **228378 but it does not have "Version info"
Any ideas?
Click to expand...
Click to collapse
none of the secret codes work on my device. How to check NT Code ?

o i fix nt but have imei 0

chauduc1113 said:
может исправить imei 0??
Click to expand...
Click to collapse
chauduc1113 said:
can fix imei 0??
Click to expand...
Click to collapse
did you manage to fix imei?

Model LM-V500EM. After upgrading from V500EM20q_00_OPEN_EU_OP_0318 to V500EM30b_00_OPEN_EEA_OP_1025 disappeared Serial No. and NT code. I had backup ftm from V500EM20q. According instruction "Modifying FTM" below copied Serial No. and NT code from ftm V500EM20q to ftm V500EM30b. For me copied NT code was "1","FFF,FFF,FFFFFFFF,FFFFFFFF,19" Now it's all right.