Database Users

nv edit help

So I had issues with my phone not long after updating to 4.4.2 using the houseofmoto method (about a month or two) phone was randomly rebooting itself so I flashed 4.4.2 back onto my phone after unlocking the bootloader. Now I can't seem to get the NV edit to work to get gsm unlocked for use in the US. Any help would be appreciated. I've tried the cdma ws method and both of the radiocomm methods with no luck. pretty sure I'm doing something wrong.

TogaDuck said:
So I had issues with my phone not long after updating to 4.4.2 using the houseofmoto method (about a month or two) phone was randomly rebooting itself so I flashed 4.4.2 back onto my phone after unlocking the bootloader. Now I can't seem to get the NV edit to work to get gsm unlocked for use in the US. Any help would be appreciated. I've tried the cdma ws method and both of the radiocomm methods with no luck. pretty sure I'm doing something wrong.
Click to expand...
Click to collapse
Are you booting into Fastboot mode, and then from there rebooting into Factory mode, before attempting the edit? Also, are you letting the phone sit for about five minutes or so after the edit before rebooting?
Edit: you may get better luck with responses if you post directly in the GSM unlock threads, as there are already lots of people subscribed to those threads.

In the past I've just booted directly to BP Tools mode and both of the how to guides say to boot into bp tools mode but I shall give your boot options a try.

The CDMA Workshop method requires booting into BP Tools, but the RadioComm method requires booting into Factory mode.
I haven't tried the CDMA WS method, but the RadioComm method worked fine for me. In the introductory post, he mentions BP Tools, but only to say that it doesn't work with RadioComm, and that you need to boot into Factory mode instead.
http://forum.xda-developers.com/showthread.php?t=2166542

got it working using the cdma ws method. selected ap fastboot then rebooted to boot menu selected bp tools mode reapplied the edit and is now working.

If it helps, here's the bit I was referencing from the intro post in the RadioComm thread. I highlighted the relevant bits in red.
cellzealot said:
(snip)
That method requires booting into BP Tools mode from the boot menu and loading the Qualcomm diagnostic device interfaces.
The problem is that there are no signed 64bit drivers available and you must force load the drivers on Win7/8 64 bit for the diagnostic port in order to see the device properly and have NV read/write access.
This has been a stumbling block for many users and makes the NV editing unnecessarily difficult.
This method uses Factory boot mode and allows RadioComm to have full diagnostic mode access via the Motorola USB Networking driver that loads normally with the standard USB driver set. I will demonstrate 2 different ways to perform the edit, one manual and one using a preconfigured SEEM table file that writes the value in a single operation.
(snip)
Click to expand...
Click to collapse
Glad you got it working though!

[Q] Damaged EFS, no backup - how to repair S5 with NULL IMEI?

Hi,
I have a problem with my S5. After flashing a custom ROM I found out that my IMEI is null, and so the EFS is corrupted. I tried to restore it from backup only to find out that I have deleted the backup
What can I do now? I anything? Would restoring EFS from another S5 (with damaged mainboard) could be a solution?
Generally everything works except of phone modem, I have got IMEI written - is there maybe a method to set the IMEI without EFS or a method to create EFS? I already tried sam IMEI changers, but I found out that they only do this on the application level - apps will be able to read different IMEI for licensing, but phone still sees NULL IMEI.

You can't restore EFS from another S5 coz it'll brick your device.

Bruce666 said:
You can't restore EFS from another S5 coz it'll brick your device.
Click to expand...
Click to collapse
Thanks for answer
So what can I do?

Found sth like this:
Never tried coz never lost IMEI
In the dialer, type- *#197328640# or *#*#197328640#*#*
>You will be prompted into the Command mode, provided On the screen, Select on Common, normally option 6
> Now Select (FTM) Option 1
>FTM is for debugging and testing., (Field Test Mode)
>If (FTM) is on, you will have to turn this OFF
>As soon as you turned this off your NULL or altered IMEI number will be restored
>(Important) Without leaving the Command screen, press the Menu key, the button that’s found left of the Home button.
> Select Key input and enter option 2. In this case, you want to turn it off
>Wait for a minute. This will turn your FTM OFF
> Remove your battery and SIM card for two minutes
>Place your battery in your phone, (important) do not place your SIM card in.
> When the phone is booted, enter the command mode again dial – *#197328640#
>Select the Debug Screen, normally option 1
>After that, choice phone control, option eight
>Click on nas control, option 3
>Afterwards, click “RRC (HSDPA), option 5
>To Fix not registered on network or Null IMEI #, click RRC revision, option 2.
>Choose the released of your phone, here we will choose option 5 (HSDPA only)
>Final step to fix Null IMEI not registered on a network for Samsung Galaxy is to turn off your phone and insert your Sim card
or
>Insert your Sim card, afterwards reboot your phone

Thanks - are you sure about this bricking device?
I already tried this numbers but it always says "No Network", The only instruction that I found was to use *#0011# and it goes into the Service Menu, but it doesn't look like that described. There is something called NVM restore, but it doesn't do anything with IMEI
I am gonnna post screenshots at evening.
Bruce666 said:
Found sth like this:
Never tried coz never lost IMEI
In the dialer, type- *#197328640# or *#*#197328640#*#*
>You will be prompted into the Command mode, provided On the screen, Select on Common, normally option 6
> Now Select (FTM) Option 1
>FTM is for debugging and testing., (Field Test Mode)
>If (FTM) is on, you will have to turn this OFF
>As soon as you turned this off your NULL or altered IMEI number will be restored
>(Important) Without leaving the Command screen, press the Menu key, the button that’s found left of the Home button.
> Select Key input and enter option 2. In this case, you want to turn it off
>Wait for a minute. This will turn your FTM OFF
> Remove your battery and SIM card for two minutes
>Place your battery in your phone, (important) do not place your SIM card in.
> When the phone is booted, enter the command mode again dial – *#197328640#
>Select the Debug Screen, normally option 1
>After that, choice phone control, option eight
>Click on nas control, option 3
>Afterwards, click “RRC (HSDPA), option 5
>To Fix not registered on network or Null IMEI #, click RRC revision, option 2.
>Choose the released of your phone, here we will choose option 5 (HSDPA only)
>Final step to fix Null IMEI not registered on a network for Samsung Galaxy is to turn off your phone and insert your Sim card
or
>Insert your Sim card, afterwards reboot your phone
Click to expand...
Click to collapse

evilsnailofdestruction said:
Thanks - are you sure about this bricking device?
I already tried this numbers but it always says "No Network", The only instruction that I found was to use *#0011# and it goes into the Service Menu, but it doesn't look like that described. There is something called NVM restore, but it doesn't do anything with IMEI
I am gonnna post screenshots at evening.
Click to expand...
Click to collapse
Yes I'm sure about bricking. EFS partition on your phone is made for ONLY YOUR PHONE. This is sth like restoring TA Partition on xperia devices. When you flash ta from another xperia, you brick device
Tapatalked from SM-G900F

I read someone saying they had successfully restored a backed up EFS partition from an identical model S5 to another, and it worked
The problem I can see, is if the original gets blocked by the carrier, chances are so will the clone
Not sure about network issues having two identical devices on the same network at the same time, both making calls, might end up like an IP conflict

Pretty sure that transferring IMEI from one device to another is against the law too......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F

Yes, I also know that is it against the law, but I have a complete phone with broker mainboard (so even the IMEI is written on the back), and I would like to use this opportunity to copy the IMEI from old (broken) mainboard to the new one. It even looks better than the situation when I have got and old case with written IMEI that doesn't correspond to the IMEI on the new mainboard.
The mainboard is broken that way, that there is short-circuit somewhere and the CPU is constantly using power and it get's really hot, so it use useless.
I am trying to flash EFS, let's see what is gonna to happen
keithross39 said:
Pretty sure that transferring IMEI from one device to another is against the law too......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse

1. Tried flashing EFS = nothing happened
2. Tried flashing EFS + Modem + ModemST1 + ModemST2 = nothing happened
3. Restored android to STOCK
I can't get into the service menu.
The only Service menu that I can get into is this one, but there isn't any fixing IMEI/NVRAM option
Code:
*#0011#
Menu > Back
Menu > keyInput "Q"
Menu > keyInput "0000"
Wait for few seconds
evilsnailofdestruction said:
Yes, I also know that is it against the law, but I have a complete phone with broker mainboard (so even the IMEI is written on the back), and I would like to use this opportunity to copy the IMEI from old (broken) mainboard to the new one. It even looks better than the situation when I have got and old case with written IMEI that doesn't correspond to the IMEI on the new mainboard.
The mainboard is broken that way, that there is short-circuit somewhere and the CPU is constantly using power and it get's really hot, so it use useless.
I am trying to flash EFS, let's see what is gonna to happen
Click to expand...
Click to collapse

Hi,
you have 2 options
1. Use Samsung Kies which will repair you efs
2. Flash with Odin the official rom 5.0
If you install another efs, the data installed may be not work, even if it is same model. In S5, nothing to do with the IMEI
You can also root the phone and with adb commands, erase all the efs
you can also use Z3X tools

Hi,
Thanks - some new ideas
So if I understand you correctly, I have 3 options:
1. Use Samsung Kies which will repair you efs - how to repair EFS with Samsung Kies?
2. Flash with Odin the official rom 5.0 -> I tried flashing oryginal 4.4 and it didn't helped. Should flashing 5.0 help?
3. You can also root the phone and with adb commands, erase all the efs - What will erasing EFS will give me? Shouldn't I have EFS partition with some data?
you can also use Z3X tools -> ok... I am gonna figure this out, 'cause I don't know it yet
FrenchSnake said:
Hi,
you have 2 options
1. Use Samsung Kies which will repair you efs
2. Flash with Odin the official rom 5.0
If you install another efs, the data installed may be not work, even if it is same model. In S5, nothing to do with the IMEI
You can also root the phone and with adb commands, erase all the efs
you can also use Z3X tools
Click to expand...
Click to collapse

I have the same issue. Anybody may help me ? (galaxy S5 SM-G900H made in Vietinam)
thanks in advance

Bruce666 said:
Found sth like this:
In the dialer, type- *#197328640# or *#*#197328640#*#*
>Insert your Sim card, afterwards reboot your phone
Click to expand...
Click to collapse
This does nothing on Galaxy A5!
attached 0011 code screen

Has anybody found the solution? Efs professional gives me error " device connection lost" while using Qualcomm nv tools on s5.

Redmi note 3 Pro / Snapdragon 650 edition - Hard brick resurrect

First of all, i have read some similar threads about this, and all advise diffrent solution besides the hardware mod, I have tried for 2 days all methods in Miui forums and none have worked for me except the hardware method.
My Device: Xiaomi Redmi Note 3 Pro / SD version.
State:
-would only show "Mi" logo when powered on.
-Would enter only Fastboot.
- No EDL mode
- No recovery
-bootloader locked
-In this state, you can't flash absolutely nothing with any software. (from fastboot).
Requirements:
- windows 7/ windows 10 x64 edition.
- ONLY LATEST version of miflash, from 2016 onward, so it has the required drivers and methods to work with the phone. (I have tried with older versions and it did not work, i thought there was no hope for my phone).
- one hard bricked Redmi Note 3 Pro
- any fersion of Stable FASTBOOT OFFICIAL rom. (.tgz extension) - I personally used kenzo_global_images_V7.2.3.0.LHOMIDA_20160129.0000.14_5.1_global_c85ba6c524.tgz
- medium disassembly skills,
- a lot of patience,
- minimum set of tools (one small cross screwdriver, 1-2 strong finger nails, good eyesight).
- one microusb cable
HOW TO:
1. uninstall all drivers and software related to the Xiaomi phone. (I ended up reinstalling windows 7 just to be sure all was gone - that is how desperate I became). To be sure this is done correctly, with the phone turned off, connect it to the computer.
Go into device manager, search in com ports, or wherever any drivers are installed for the phone, and uninstall all of them, ticking remove driver files also.
after doing this, hit refresh, and see if any drivers get installed again.
Repeat until there are no drivers installed, and the device will be without a driver.
2. Disconnect the phone and RESTART WINDOWS
3. Disable driver signature verification/enforcement:
a. in windows 7, this is easy: restart windows, hit f8 until a menu pops up where you can choose disable driver signature verification/enforcement.
b. in windows 10, it is a little bit longer, but: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/ - Be careful, when choosing the option in the last menu, use F... keys, not number keys.
4. while in windows, in the bottom right corner, there should be a message saying "test mode"
5. install ONLY the LATEST VERSION of Miflash! you may get some messages about driver installation (2 times), allow installation!
6. RESTART WINDOWS
7. Prepare the phone!: I followed the video here, even I did not understand the language: http://choimobile.vn/threads/video-...o-snapdragon-650-fix-download-mode-edl.65098/
- First, I used my nail to open the phone up, just like in the video. It is great that the screen is not glued to the body, there are only some clips holding it in place!
- after opening the cover please be careful - there is a cable connecting the case to the mainboard - the fingerprint sensor.
- after this, unscrew the 7 or 8 screws as in the video.
- unlock the cables as in the video - please be sure not to disconnect all the cables.
- now, first get the antenna plastic cover outside of the way.
- after disconnecting the camera module, I would personally advise you to get the camera out of the way first, as there is a piece of foil glued between the mainboard and the underneath of the camera module (on the display)
- with great care, rise the Mainboard from the display.
- to have better access to the testpoint pins, I turned the Mainboard over the battery.
- now, connect the microusb cable to the phone.
8. connect the phone to the computer.
9. go into device manager and check if there are any devices installed, there should be under ports.... a device called Qualcomm HS-USB Diagnostics 900E.
10. Now comes the tricky part, switching the phone to EDL mode (emercency download)
look on the back of the motherboard of the phone to connect the 2 testpoint pins as in the video. You can use anything to do this. a metal wire, a small scissors, an untied paperclip... You will have to do this while device manager is opened, as you must check it when the driver changes to "qualcomm hs-usb qdloader 9008".
Please be careful when trying to connect the 2 pins not to touch any metal housing, ans this will restart the device each time.
Now, try and try and try until the driver changes to "qualcomm hs-usb qdloader 9008".
11. unzip the rom using 7 zip to a destination of your choosing. I advise as short destination as possible and no spaces used in the folder naming. I unpacked it in C:\rom\
12. Open Miflash
13. As per other many many instructions:
a. click browse - select the folder where you unpacked the rom (for me, c:\rom\)
b. click the arrow next to brows button and select advanced.
c. in the first field, navigate to the folder where the rom was unpacked and select flashall.bat
d. in the third field select prog_emmc_firehose_8976_ddr.mbn from the "images"folder in the folder whre he rom was extracted
e. field 7: rawprogram0.xml and field8: patch0.xml
f. Hit the Refresh button, the device should appear as a com port in the white field of Miflash.
g. just to be sure, tick also "flash all" in the bottom of miflash.
14. Hit the Flash button on Miflash and this should be the last step before powering up your revived Xiaomi Redmi Note 3.
This is what I learned in the past 2-3 days.
Different errors I got during the learning process and what i did to avoid them:
- different problems with drivers not installing correctly or showing different device names - just use the method i pointed out in the beginning to uninstall any driver previously installed on the computer, with the refresh in device manager and than uninstalling all.
- "end of package" error at second 2 while flashing in Miflash - you are using an older or an unsupported version of miflash, just use the latest one.
- not being able to flash anything while in fastboot - if you have a locked bootloader, on redmi note 3 snapdragon version, you simply won't be able to flash anything. end of story. this is the whole purpose of having a locked bootloader.
- trying to go into EDL mode using fastboot comand "fastboot oem eld" - this will not work for a really bricked device as was mine. the only solution is to go through the tespoint pin connection.

i wonder if there's a way not to make trwp locked in the recovery partition, so if someone flashes a factory rom without precaution, twrp will simply get overwritten by factory recovery. Wouldn't that prevent these hard bricks?
btw, nice guide

Please move the thread into guides/tutorial section.

Well, mine was bricked too 2 days ago... even I already unlock the bootloader using the official way.
It happened because I'm on AOSP and I flash Xiaomi.EU ROM from TWRP.
'MI' Logo flashed twice then the phone turns off itself.
It can't boot, can't enter EDL mode. I just can go into fastboot mode. But nothing can be done there because it always says 'device is locked'.
'fastboot oem device-info' also says the phone is on locked state.
Dunno why this happen, I think its because I play with the unlock bootloader toggle on previous MIUI and AOSP ROM.
After countless of times trying to get into EDL, I give up.
Device manager always show "QCom HS-USB Diagnostic 900E" instead of "QCom HS-USB QLoader 9008"
Finally I try the official Mi Unlock software, re-unlock success and BAM... Phone boots again into system. lol...
This makes me think the bricked problem can prevented/solved to by:
- At least bind a Xiaomi Account to your phone once when using official ROM (recommended China Dev ROM)
- Use that account to apply for the unlock, and when you got the phone bricked/relocked, you can re-unlock it using official way to revive the phone

Now is possible unbrick without disassembly:
http://en.miui.com/thread-267263-1-1.html
http://www.htcmania.com/showthread.php?t=1174700

jujusito said:
Now is possible unbrick without disassembly:
http://en.miui.com/thread-267263-1-1.html
http://www.htcmania.com/showthread.php?t=1174700
Click to expand...
Click to collapse
please read through all the thread, don't just throw in a link. the method mentioned by you will not work on some bricked devices, including mine. this did not work for me, so I ended up disassembling the phone.

aabenroi said:
Well, mine was bricked too 2 days ago... even I already unlock the bootloader using the official way.
It happened because I'm on AOSP and I flash Xiaomi.EU ROM from TWRP.
'MI' Logo flashed twice then the phone turns off itself.
It can't boot, can't enter EDL mode. I just can go into fastboot mode. But nothing can be done there because it always says 'device is locked'.
'fastboot oem device-info' also says the phone is on locked state.
Dunno why this happen, I think its because I play with the unlock bootloader toggle on previous MIUI and AOSP ROM.
After countless of times trying to get into EDL, I give up.
Device manager always show "QCom HS-USB Diagnostic 900E" instead of "QCom HS-USB QLoader 9008"
Finally I try the official Mi Unlock software, re-unlock success and BAM... Phone boots again into system. lol...
This makes me think the bricked problem can prevented/solved to by:
- At least bind a Xiaomi Account to your phone once when using official ROM (recommended China Dev ROM)
- Use that account to apply for the unlock, and when you got the phone bricked/relocked, you can re-unlock it using official way to revive the phone
Click to expand...
Click to collapse
I also applied for an unlock code, but this takes up to 15 days, and I have the phone for only 3 days . I could not wait for the code, I had to do something to revive it.

meangreenie said:
i wonder if there's a way not to make trwp locked in the recovery partition, so if someone flashes a factory rom without precaution, twrp will simply get overwritten by factory recovery. Wouldn't that prevent these hard bricks?
btw, nice guide
Click to expand...
Click to collapse
I made a modified TWRP which will not cause hard bricks

Rajdip said:
I made a modified TWRP which will not cause hard bricks
Click to expand...
Click to collapse
great work! your modded twrp will no doubt save me when i forget i have to delete the emmc file in the future.

Dear, thank you for your contribution, this deserves to be a section more important, really saved my phone from the hard brick. Again very grateful

how do i know what a test point looks like on any phone? like the new redmi 3s? i cant get into edl because im stuck in Qualcomm HS-USB Diagnostics 900E

xdarkmario said:
how do i know what a test point looks like on any phone? like the new redmi 3s? i cant get into edl because im stuck in Qualcomm HS-USB Diagnostics 900E
Click to expand...
Click to collapse
maybe look for something like this?
http://choimobile.vn/Temp/Testpoint_Redmi_Note3_PRO_3.jpg
I doubt they will have much variance from xiaomi phone to phone to make it easy for factory / repair centers to fix many models... (I could be wrong though), other brands are probably different.

Well you can enter edl mode from fastboot via this simple tool
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
And then you can flash any miui .tgz based rom and resurrect.
I hard bricked my Device last night and resurrected
PS : you must have the MiPcSuit installed

ilvmyname said:
Well you can enter edl mode from fastboot via this simple tool
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
And then you can flash any miui .tgz based rom and resurrect.
I hard bricked my Device last night and resurrected
PS : you must have the MiPcSuit installed
Click to expand...
Click to collapse
links dead

Quick addition: if you're using Virtual Box, like me (on a mac), you need to enable USB 2.0 on the virtual machine. On Virtual Box, this means you have to add an extension pack. This might save you 48hrs, like it cost me

i9502 (S4 duos) enable CP logging / enable diag mode

Hello,
I barely post anything as there is a huge amount of documentation on this forum, but I am really stuck at this and have no clue how to solve it.
I have two i9502 phones:
- one with good IMEIs and thus, working GSM, but the sensors are not working (hardware failure - sensorhub test fail + all sensors from the *#0*# menu are dead)
- one with good sensors, but one of the IMEI is null, thus GSM is not working
I am tying to clone the one with good IMEIs over the one with bad IMEIs. I have previously done this with success, but for the S4 Active model (i9525).
To do this, I need to use QPST or EFS Professional (awesome software btw) with the phone running in diag mode.
When I enable "DM+Modem+ADB" from the *#0808# menu I get "USB device not recognized" on my PC, a problem usually resolved by "Enable CP logging" from the original recovery.
The problem with this model is that "Enable CP logging" option is missing from the recovery.
Also, codes like ##DMMODE# or ##DIAG# have no effect and there is no relevant option in the service menu (*#0011#) or diag config menu (*#9090#).
Things I've tried so far:
- directly backup/restore EFS partitions using TWRP or EFS Professional
result: fail, I had both IMEIs null.
reason: Encrypted File System partitions are encrypted using the phone's certificate/key. This means the EFS backup only makes sense for the original phone.
- downgrade to android 4.4.2
result: fail, recovery menus and secret menu codes behave exactly the same.
- flash a recovery from i9500 to get the "enable CP logging"
result: fail: when I enable the option, the phone restarts and PC still not recognizes the device. This was the closest I ever got to solve this.
- downgrade to android 4.3
result: fail, cannot flash, odin gives error and the phone says something like "firmware revision 2, phone revision 3" (incompatible hardware revisions?)
Does anyone know how to enable diag mode for this model?
Important to mention that I do not have any kind of service box.
Things I am thinking of trying:
- flash MIUI and see from there. I doubt a ported rom could do anything about this.
- cook android 4.3 using dsixda's Android Kitchen, and flash using a custom recovery. I doubt this will work also. Expecting a brick
Thanks.

You ever figure out how to do this?

IMEI Problem

So I got a lg k8 2017 m200 .Used for a while but yesterday i did a reset and now imei is gone. I have tried the following:
1)Unable to root it.
2)Found no custom rom or custom recovery.
3)EFS Pro said successfully IMEI written but upon restart its still null.
4)Tried qpst but mobile is unknown and keeps disconnecting.(I enabled port check test and usb debugging)
5)Flashed stock rom 3 Times.
6)Reset it 8 Times.
9)Also wasn't able to use diag port command due to lack of superuser in adb.
None of all worked so can anyone help please. Reset of functionality is good. So i also turned off my lg and press vol up and vol down along with power button and it displayed imei there.

"So i also turned off my lg and press vol up and vol down along with power button and it displayed imei there."
Wait, it displays the correct IMEI there?
You said your IMEI is gone. but is it blank or its written "unknown" there? Or the IMEI is just wrong?
I had a problem with IMEI some years ago on a LG E610f and I fixed it by using LG tools back then. I still have the version 9.5 here and I doesnt support your phone, but Maybe the latest version supports your phone.