Related
Hi there,
Something very strange has appears to my Nexus S.
It's been more than one year that my phone works perfectly with ICS 4.04 flashed by recovery and ROM stock, I've never reflashed my phone since this day.
Then two days ago, no more GSM network, can't pass any call or text, but data in WCDMA works perfectly.
I've tried :
- Factory reset
- Cyanogen Mod last ROM
- Tried my SIM card on the Nexus S of a friend --> works perfectly
- Tried my friend SIM card on my phone --> same issues, no GSM but data works in WCDMA
I've search a lot on google and XDA, and I've discovered what was IMEI and /efs.
But it's too late for me, my IMEI is the cursed generic IMEI, not the one written behind my battery.
I've tried to flash with stock ROM Stock Android 2.3.6 (GRK39F) with Odin because I've read that it could retrieve my original IMEI. There was no .md5 file inside so I can't flash it with Odin, else I've flash it with ADB / Fastboot.
Phone start and GSM mobile works !
But I got generic IMEI yet, and data is stuck on edge, no WCDMA.
I was thinking it was caused by the old ROM radio flashed with ROM Stock Android 2.3.6 (GRK39F).
So I've flash using recovery the latest Cyanogen and ROM radio KB3 (which was working great in WCDMA for me before all this mess).
No change, GSM works, but data network is stuck in Edge, even if I force WCDMA in *#*#4636#*#* menu, it keep staying in edge.
I don't understand all of this, but I think this is again link to this generic IMEI.
My /efs folder is not empty, I have nv_data.bin but file is dated from yesterday and I can't find any backup like ".nv_data.bin" or "nv_data.bin.bak".
This story seems to be classic in XDA forum, but it's really difficult for me to find a solution, especially for a Nexus S.
This phone is pretty old, you guys are experienced with it and I really need your help, I like this phone and I don't want to change it =(
Is there any way to regenerate my original IMEI ?
Maybe I'll try a flash with Odin and 2.3.4 GRJ22, I never tried Odin, but it seems sometimes to solve the problem. Do you think it could work ?
I really need your help guys, I'm so sad : /
Thanks for reading this, and thanks again if your reply.
hey man,
sorry to hear that...
have you tried to use your sim on another phone? the phone is 2 years old and possibly the problem is from the simcard\network.
another option is to check weather your APN's are as supposed to be.
you can check online or via customer service.
sheeen said:
Hi there,
Something very strange has appears to my Nexus S.
It's been more than one year that my phone works perfectly with ICS 4.04 flashed by recovery and ROM stock, I've never reflashed my phone since this day.
Then two days ago, no more GSM network, can't pass any call or text, but data in WCDMA works perfectly.
I've tried :
- Factory reset
- Cyanogen Mod last ROM
- Tried my SIM card on the Nexus S of a friend --> works perfectly
- Tried my friend SIM card on my phone --> same issues, no GSM but data works in WCDMA
I've search a lot on google and XDA, and I've discovered what was IMEI and /efs.
But it's too late for me, my IMEI is the cursed generic IMEI, not the one written behind my battery.
I've tried to flash with stock ROM Stock Android 2.3.6 (GRK39F) with Odin because I've read that it could retrieve my original IMEI. There was no .md5 file inside so I can't flash it with Odin, else I've flash it with ADB / Fastboot.
Phone start and GSM mobile works !
But I got generic IMEI yet, and data is stuck on edge, no WCDMA.
I was thinking it was caused by the old ROM radio flashed with ROM Stock Android 2.3.6 (GRK39F).
So I've flash using recovery the latest Cyanogen and ROM radio KB3 (which was working great in WCDMA for me before all this mess).
No change, GSM works, but data network is stuck in Edge, even if I force WCDMA in *#*#4636#*#* menu, it keep staying in edge.
I don't understand all of this, but I think this is again link to this generic IMEI.
My /efs folder is not empty, I have nv_data.bin but file is dated from yesterday and I can't find any backup like ".nv_data.bin" or "nv_data.bin.bak".
This story seems to be classic in XDA forum, but it's really difficult for me to find a solution, especially for a Nexus S.
This phone is pretty old, you guys are experienced with it and I really need your help, I like this phone and I don't want to change it =(
Is there any way to regenerate my original IMEI ?
Maybe I'll try a flash with Odin and 2.3.4 GRJ22, I never tried Odin, but it seems sometimes to solve the problem. Do you think it could work ?
I really need your help guys, I'm so sad : /
Thanks for reading this, and thanks again if your reply.
Click to expand...
Click to collapse
Still nothing,.. Sorry you haven't got this resolved yet.. Hopefully some fresh eyes here can make short work of it..
Thanks for your reply guys.
I've tried the sim in another phone and it works great, the real problem is generic IMEI I guess.
Thanks for your help and your link in PM Setting Out, I think I'll try the second one.... the first can't work with me because my /esf and /data/radio does not have an old backup of nv_data.bin.
I have two questions please :
- How the holy s*** this thing can happen randomly after ONE YEAR of fully founctional phone ? (not a single flash since one year)
- How can it be so ramdom ? I mean, before rom stock flash, GSM does not work but I was having Data (WCDMA). Now, After rom stock flash, GSM is working but Data is stuck in Edge. I can't understand how IMEI can impact such randomly issues.
Well, as you know the IMEI is sent to your operator as long as you have signal.
if the operator doesn't get a valid one problems may occur.
In order to find out if this really is a EFS problem go into /data/radio/log and cat the nv.log, find a line like this:
MD5 fail. orignal md5 '84373eddf2a1617f795b1c1af650f8a784373eddf2a1617f795b1c1af650f8a7' computed md5
'3eddf2a1617f795b1c1af650f8a7' (rild)
put the phone in airplane mode then use a unix text editor and manualy edit nv_data.bin.m5d and make sure the string of numbers is equal to the string after "computed md5" (in this case 3eddf2a1617f795b1c1af650f8a7) save the file take the phone out of airplane mode then reboot check the IMEI with the *#06#
Thanks a lot for your reply.
I have /data/radio/log/nv.log file.
But I have no checksum in this file, only text like "/data/radio/nv_data.bin does not exist."
This is strange because /data/radio/nv_data.bin file exist.
But in /efs folder, I have a nv.log file too, and in this file I have some checksum.
Any way to do something with this one ?
EDIT : I've tried the manipulation with /efs folder, it does not change my generic IMEI =(
Sure, I verified permissions and owner of file.
sheeen said:
Thanks a lot for your reply.
I have /data/radio/log/nv.log file.
But I have no checksum in this file, only text like "/data/radio/nv_data.bin does not exist."
This is strange because /data/radio/nv_data.bin file exist.
But in /efs folder, I have a nv.log file too, and in this file I have some checksum.
Any way to do something with this one ?
EDIT : I've tried the manipulation with /efs folder, it does not change my generic IMEI =(
Sure, I verified permissions and owner of file.
Click to expand...
Click to collapse
Here are some detailed steps
Ensure you have one good copy of nv_data.bin somewhere on the phone. it could be located in either /efs or /data/radio
Ensure you have a nv.log with at least one line that looks somewhat like this:
MD5 fail. orignal md5 'XXXXXXXXXXXXXXXXXXXXXX' computed md5 'XXXXXXXXXXXXXXXXXXXXXXXXX' (rild)
where the X's are a bunch of number and letters.
Copy the good nv_data.bin, nv_data.bin.md5 and nv.log to both the sdcard and then via usb put them on your hard drive in a folder called efsbackup
(use either rootexpoler or adb shell to copy the files to the sdcard first)
Open the nv.log and look for the second sting of lines. after the words computed md5 (the first string is the md5 the phone found and the second string is the md5 it was expecting for. if the md5 it was expecting can't be found, it uses the default IMEI 004999010640000
Open nv_data.bin.m5d with a proper unix text editor (I suggest Notepad++ or jedit) and remove the sting of numbers and letters and replace it with the string from the nv.log (the second string after computed md5) and save the file
Go back to the phone and put the phone into Airplane Mode (this turns off the radio)
Copy the files nv_data.bin and nv_data.bin.m5d back to the sdcard overwirting them
Using either rootexplorer or adb shell copy the nv_data.bin and nv_data.bin.md5 back to the original folder (either /efs or /data/radio (for me it was /data/radio that did the trick))
Using either rootexplorer or adb shell ensure both files have the following attributes Owner:radio Group:radio Owner:RWX Group:R Other:R
Using adb shell type ps (this lists all the running processes) find the one that end with rild and remember the pid
Using adb shell type kill pid# where pid# is the rild process (this restarts the radio)
Go back to the phone and take the phone out of Airplane mode
Reboot the phone
Open up the dialer and dial *#06# (the universal way to get your IMEI it SHOULD be equal to the one written under the battery)
Thanks for the reply, but it can't work.
Ensure you have one good copy of nv_data.bin somewhere on the phone. it could be located in either /efs or /data/radio
Click to expand...
Click to collapse
I have no good copy of nv_data.bin, date shows that all have been generated last week.
So, I'd like to flash the phone with Odin rom stock 2.3.4 AND re-partition with the .pit file.
I've already flash it without the .pit, but my IMEI is still generic, I need the .pit file.
But the .pit file is nowhere, even on samfirmware : /
If somebody got this file, plz send it to me.
sheeen said:
Thanks for the reply, but it can't work.
I have no good copy of nv_data.bin, date shows that all have been generated last week.
So, I'd like to flash the phone with Odin rom stock 2.3.4 AND re-partition with the .pit file.
I've already flash it without the .pit, but my IMEI is still generic, I need the .pit file.
But the .pit file is nowhere, even on samfirmware : /
If somebody got this file, plz send it to me.
Click to expand...
Click to collapse
-I too have looked high and low for the Odin file since the Nexus S can be put in download mode holding the volume button while pluging in the micro USB. I did find some odin files but any one who tired them ened up perm bricking their phone.
-If you have a good backup it should restore the EFS partition as well as the RADIO.
-The only other way that I know of, I am afraid is to get the phone JTAGed by Samsung.
Good Luck
After two weeks of trying everything, I gave up and used a Z3X.
Now my IMEI is restored, and backup on my PC, my laptop, my sdcard and on cloud...
Thanks all for trying to help me.
Long story short, I bricked my lg g2 d801 after flashing twrp recovery and trying to flash custom rom. The phone would restart randomly. I had no connection and the signal bars crosses out in red. In settings most of my info like baseband, imei etc were missing. I was looking up and many people bricked their phones with no EFS backup to restore the IMEI. This is how I fixed my phone. This should also help people who have zeroed out IMEI after bad flash or whatever reason. But you should at least have IMEI number ready (from your box/ receipt or call t-mobile)
1. Flashed the phone to factory firmware using LG support tool. I used the following guide:
http://androidcure.com/unbrick-lg-g2-stock-firmware/
used the firmware: T-Mobile KitKat D80120A_00.kdz
there's also similar guides in xda, follow whichever you prefer. Goal is to revert the phone back to stock.
After flashing the phone, the phone was woking; however imei was null. In phone settings my IMEI was 0. To fix the null/bad imei follow this guide (Not all the steps are my work; this guide helped me http://forum.xda-developers.com/showthread.php?t=1942417 , also watched some you tube videos):
2. You need the following drivers and software:
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1
QPST_2.7_378
imei converter: http://www.sendspace.com/file/a3spfh
3. After installing the driver; turn on USB debugging and connect the phone to computer
4. Install QPST, run QPST configuration from from start menu
5. Click on Ports tab. Click Add new port. Your phone should be COM4/5. It will say USB after the port. Select the port and click OK.
6. The port should come up on active phones. Select the phone and and click on "Software Download" from start clients menu
7. Click on Backup tab. Your port should appear. Backup by clicking on start
8. Now go to Program Files/qualcomm/qpst/bin folder
9. Run RF_NV_Manager program
10. Click File read from phone. Your IMEI should appear on number 550; NV_UE_IMEI_I
11. In my case; there was no item 550 as my IMEI was missing. Don't worry.
12. Click on file> Read supported RF NV items
13. Now click on item 550. It should show 9 blank fields.
14. Start IMEI converter. Type in your IMEI in enter IMEI click on convert IMEI
15. There will be 18 digits in groups of 9
18. In RF_NV_Manager program; click on Hex by Write NV button
19. IN the 9 boxes; type in the numbers from IMEI converter starting from left. Type in first group of two numbers in the first field, then go to the next field and type in second 2 digits
20. After you fill in; click on write NV
21. Now click on File> Read from phone. NV item number 550 should appear now.
22. Unplug, Restart your phone and your IMEI number should be there and phone should connect to network.
Above process fixed my phone with full 4G LTE data. Now depending on the how bad your EFS was damaged; you might not get 4G lte data. But at least now; you will be able to send the phone back to LG for repair or return to t-mobile as IMEI number will be in your phone.
You can do this with EFS Professional. It does all the conversion for you and you dont need QPST. Just simply type in IMEI and write to device.
Sent from my LG-D802 using Tapatalk
I've tried the this guide and it didn't work for me. I get an error when I try to write NV. The good news is that I don't have an immediate need to change/fix IMEI but I was wondering if it ever gets zeroed out I have a way to restore it. I will give your tool a try.
lyriquidperfection said:
You can do this with EFS Professional. It does all the conversion for you and you dont need QPST. Just simply type in IMEI and write to device.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
So the EFS Professional is compatible with phones other than Samsung? Once I've unzipped the file I see a bunch of binaries for Samsung phones, but nothing for LG G2. When I try to run it generates an error the app is for Samsung devices only... Where can I get a compatible binary for LG G2 or EFS professional that works with LG G2?
I've tried Qualcomm NV Tools instead of EFS Professional and I cannot create a backup. When backup is being created it errors out saying the device has been disconnected... Also if I write the IMEI it says it was accepted but it doesn't change.
PS: I should probably start screweing around with these apps since I may introduce the problem. My IMEI is fine.
tpaxadpom said:
So the EFS Professional is compatible with phones other than Samsung? Once I've unzipped the file I see a bunch of binaries for Samsung phones, but nothing for LG G2. When I try to run it generates an error the app is for Samsung devices only... Where can I get a compatible binary for LG G2 or EFS professional that works with LG G2?
I've tried Qualcomm NV Tools instead of EFS Professional and I cannot create a backup. When backup is being created it errors out saying the device has been disconnected... Also if I write the IMEI it says it was accepted but it doesn't change.
PS: I should probably start screweing around with these apps since I may introduce the problem. My IMEI is fine.
Click to expand...
Click to collapse
Imei will only write if zeroed out. You are correct, EFS Professional is for samsung devices but the Qualcomm NV Tools is universal. I am currently in the middle of updating it so more features can be used on other devices.
Sent from my LG-D802 using Tapatalk
lyriquidperfection said:
Imei will only write if zeroed out. You are correct, EFS Professional is for samsung devices but the Qualcomm NV Tools is universal. I am currently in the middle of updating it so more features can be used on other devices.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
got it. Thank you.
Ey guys , im new in this foro. Sorry but my english.....i have a LG D802 , the imei said unkown ....I tried the method in this post but always obtain error when i use RF_NV_Manager , when i trie to read files from phone give me an error...the phone bricked when install a new custom rom.
Help please.....
the driver is correctly and the program detect the phone in port 26...
the error is this....
kamaleonico said:
the error is this....
Click to expand...
Click to collapse
did you try restoring the the phone with flash tool first?..
thank you so much, just did it and it worked perfectly fine !
kingroach said:
Long story short, I bricked my lg g2 d801 after flashing twrp recovery and trying to flash custom rom. The phone would restart randomly. I had no connection and the signal bars crosses out in red. In settings most of my info like baseband, imei etc were missing. I was looking up and many people bricked their phones with no EFS backup to restore the IMEI. This is how I fixed my phone. This should also help people who have zeroed out IMEI after bad flash or whatever reason. But you should at least have IMEI number ready (from your box/ receipt or call t-mobile)
1. Flashed the phone to factory firmware using LG support tool. I used the following guide:
http://androidcure.com/unbrick-lg-g2-stock-firmware/
used the firmware: T-Mobile KitKat D80120A_00.kdz
there's also similar guides in xda, follow whichever you prefer. Goal is to revert the phone back to stock.
After flashing the phone, the phone was woking; however imei was null. In phone settings my IMEI was 0. To fix the null/bad imei follow this guide (Not all the steps are my work; this guide helped me http://forum.xda-developers.com/showthread.php?t=1942417 , also watched some you tube videos):
2. You need the following drivers and software:
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1
QPST_2.7_378
imei converter: http://www.sendspace.com/file/a3spfh
3. After installing the driver; turn on USB debugging and connect the phone to computer
4. Install QPST, run QPST configuration from from start menu
5. Click on Ports tab. Click Add new port. Your phone should be COM4/5. It will say USB after the port. Select the port and click OK.
6. The port should come up on active phones. Select the phone and and click on "Software Download" from start clients menu
7. Click on Backup tab. Your port should appear. Backup by clicking on start
8. Now go to Program Files/qualcomm/qpst/bin folder
9. Run RF_NV_Manager program
10. Click File read from phone. Your IMEI should appear on number 550; NV_UE_IMEI_I
11. In my case; there was no item 550 as my IMEI was missing. Don't worry.
12. Click on file> Read supported RF NV items
13. Now click on item 550. It should show 9 blank fields.
14. Start IMEI converter. Type in your IMEI in enter IMEI click on convert IMEI
15. There will be 18 digits in groups of 9
18. In RF_NV_Manager program; click on Hex by Write NV button
19. IN the 9 boxes; type in the numbers from IMEI converter starting from left. Type in first group of two numbers in the first field, then go to the next field and type in second 2 digits
20. After you fill in; click on write NV
21. Now click on File> Read from phone. NV item number 550 should appear now.
22. Unplug, Restart your phone and your IMEI number should be there and phone should connect to network.
Above process fixed my phone with full 4G LTE data. Now depending on the how bad your EFS was damaged; you might not get 4G lte data. But at least now; you will be able to send the phone back to LG for repair or return to t-mobile as IMEI number will be in your phone.
Click to expand...
Click to collapse
Hey kingroach, amazing guide, wonderful!
I followed everything step by step. Right now I have some generic IMEI which does not work, I'm trying to write my original one back, but at step 20, when I click "Write NV", the numbers change, the Hex unchecks and the popup comes out. When I close it, Hex goes back to being checked and numbers return to what I made them. and I get this popup:
Here's a video.
lyriquidperfection said:
You can do this with EFS Professional. It does all the conversion for you and you dont need QPST. Just simply type in IMEI and write to device.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Hi, thank you for your help too in these threads. I tried EFS Pro, everything checks out, it says IMEI written, but when phone is restarted, nothing has changed. Do you know if EFS Pro need some other setting enabled to actually change the IMEI?
Try deleting 550 nv item which contains the imei and save. Restart the phone and add it.
kingroach said:
Try deleting 550 nv item which contains the imei and save. Restart the phone and add it.
Click to expand...
Click to collapse
nope, it dont work
im genuinly surprised the procedure works for lg g2 and not for nexus 5
how did you delete item 550?
asterix005 said:
how did you delete item 550?
Click to expand...
Click to collapse
I couldn't - you try with the custom list, under tools I think. You move item 550 from the right column, and it dissappears, but when I read NV phone items, its there. It's untouchable I tell you!:silly:
kingroach said:
Long story short, I bricked my lg g2 d801 after flashing twrp recovery and trying to flash custom rom. The phone would restart randomly. I had no connection and the signal bars crosses out in red. In settings most of my info like baseband, imei etc were missing. I was looking up and many people bricked their phones with no EFS backup to restore the IMEI. This is how I fixed my phone. This should also help people who have zeroed out IMEI after bad flash or whatever reason. But you should at least have IMEI number ready (from your box/ receipt or call t-mobile)
1. Flashed the phone to factory firmware using LG support tool. I used the following guide:
http://androidcure.com/unbrick-lg-g2-stock-firmware/
used the firmware: T-Mobile KitKat D80120A_00.kdz
there's also similar guides in xda, follow whichever you prefer. Goal is to revert the phone back to stock.
After flashing the phone, the phone was woking; however imei was null. In phone settings my IMEI was 0. To fix the null/bad imei follow this guide (Not all the steps are my work; this guide helped me http://forum.xda-developers.com/showthread.php?t=1942417 , also watched some you tube videos):
2. You need the following drivers and software:
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1
QPST_2.7_378
imei converter: http://www.sendspace.com/file/a3spfh
3. After installing the driver; turn on USB debugging and connect the phone to computer
4. Install QPST, run QPST configuration from from start menu
5. Click on Ports tab. Click Add new port. Your phone should be COM4/5. It will say USB after the port. Select the port and click OK.
6. The port should come up on active phones. Select the phone and and click on "Software Download" from start clients menu
7. Click on Backup tab. Your port should appear. Backup by clicking on start
8. Now go to Program Files/qualcomm/qpst/bin folder
9. Run RF_NV_Manager program
10. Click File read from phone. Your IMEI should appear on number 550; NV_UE_IMEI_I
11. In my case; there was no item 550 as my IMEI was missing. Don't worry.
12. Click on file> Read supported RF NV items
13. Now click on item 550. It should show 9 blank fields.
14. Start IMEI converter. Type in your IMEI in enter IMEI click on convert IMEI
15. There will be 18 digits in groups of 9
18. In RF_NV_Manager program; click on Hex by Write NV button
19. IN the 9 boxes; type in the numbers from IMEI converter starting from left. Type in first group of two numbers in the first field, then go to the next field and type in second 2 digits
20. After you fill in; click on write NV
21. Now click on File> Read from phone. NV item number 550 should appear now.
22. Unplug, Restart your phone and your IMEI number should be there and phone should connect to network.
Above process fixed my phone with full 4G LTE data. Now depending on the how bad your EFS was damaged; you might not get 4G lte data. But at least now; you will be able to send the phone back to LG for repair or return to t-mobile as IMEI number will be in your phone.
Click to expand...
Click to collapse
i tried. but at step 5, my my PC said "No Phone". can you help me ????
I keep getting
Exception Thrown!!
NvManager::getNvItemsFromPhone( const string comport )-
QpstServer::sendSyncImpl - Bad response from phone (DM packet
commands 19-24)
Any ideas? Please tag me in this.
Did you first reflash the stock rom? Someone was getting similar error and flashing stock rom fixed it.
Use EFS Professional to write your Original IMEI ....
I got this phone (Lenovo A606) about a month ago with the following problems:
1) Modem (the one with the SIM card) doesn't work, status in the about section shows "invalid IMEI" and "unknown baseband". SIM card settings are greyed out in the settings.
2) Wi-fi works fine, but i always have an additional SSID in wifi menu that says 0x010 something error
According to previous owner, it went bad after bad flash or update, but he might have been lying and modem is physically dead due to some reason.
3) Serial number is also a blank
So far i've tried:
1) Flashing different stock firmwares with full flash format and DA DL flags checked/unchecked in SP Flash tool
2) Fixing nvram/trying to restore IMEI and SN through numerous tools of different versions: Maui Meta 3g, SN Writer tool, SN Station Writer tool, infinity box CM2MTK, etc - every one of tools that i've tried (i've also tried different versions of the same tools) show me different errors, best solutions online for which are "check your drivers, change usb cable or change computer" all of which i've obviously tried with the exact same result
3) Fixing nvram by deleting nvram folder in /dev/nvram
4) Replacing MP0B_001 in the nvram folder (rather putting it in, the target folder is empty after stock flashing)
5) Using nvram fixes through both custom and stock recovery menus prepared by the poor bastards like me, but with more knowledge about this stuff
6) Flashing nvram from a donor working phone through SP Flash tool
And since i'm making this post nothing of the above has worked.
So far i've came up with two possibilities:
1) The modem is physically dead and i lost in total 72 hours of my life on a goose chase. If this case is true, how can I make sure of it? Is there a low-level recovery menu or a factory mode that can confirm/deny it?
2) I'm doing something wrong and there is a simple fix for it. In this case, I ask for help guide me in the right direction, if possible with exact instructions.
fdxcd said:
I got this phone (Lenovo A606) about a month ago with the following problems:
1) Modem (the one with the SIM card) doesn't work, status in the about section shows "invalid IMEI" and "unknown baseband". SIM card settings are greyed out in the settings.
2) Wi-fi works fine, but i always have an additional SSID in wifi menu that says 0x010 something error
According to previous owner, it went bad after bad flash or update, but he might have been lying and modem is physically dead due to some reason.
3) Serial number is also a blank
So far i've tried:
1) Flashing different stock firmwares with full flash format and DA DL flags checked/unchecked in SP Flash tool
2) Fixing nvram/trying to restore IMEI and SN through numerous tools of different versions: Maui Meta 3g, SN Writer tool, SN Station Writer tool, infinity box CM2MTK, etc - every one of tools that i've tried (i've also tried different versions of the same tools) show me different errors, best solutions online for which are "check your drivers, change usb cable or change computer" all of which i've obviously tried with the exact same result
3) Fixing nvram by deleting nvram folder in /dev/nvram
4) Replacing MP0B_001 in the nvram folder (rather putting it in, the target folder is empty after stock flashing)
5) Using nvram fixes through both custom and stock recovery menus prepared by the poor bastards like me, but with more knowledge about this stuff
6) Flashing nvram from a donor working phone through SP Flash tool
And since i'm making this post nothing of the above has worked.
So far i've came up with two possibilities:
1) The modem is physically dead and i lost in total 72 hours of my life on a goose chase. If this case is true, how can I make sure of it? Is there a low-level recovery menu or a factory mode that can confirm/deny it?
2) I'm doing something wrong and there is a simple fix for it. In this case, I ask for help guide me in the right direction, if possible with exact instructions.
Click to expand...
Click to collapse
Greetings and welcome to assist. Changing IMEI numbers is illegal and can not be discussed on xda so we have to be careful. If you have the original IMEI number it may be possible to restore it with an octoplus box or something similar but we are limited to what can be discussed on xda
Regards
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. Changing IMEI numbers is illegal and can not be discussed on xda so we have to be careful. If you have the original IMEI number it may be possible to restore it with an octoplus box or something similar but we are limited to what can be discussed on xda
Regards
Sawdoctor
Click to expand...
Click to collapse
Never tried to change it, since there wasn't any imei in the firmware to begin with. I only fruitlessly trying to return sim functionality
Lost IMEI and Baseband on your U Pro.
lets search for a solution.
forword:
if we flash the 2080227 stock rom we will lose the IMEI and Baseband information in Settings.
the IMEI and Baseband is still there its just that it dont show in settings anymore.
Why:
stock rom 20180227 contains all images of the official Stock Rom as dump.
also modemst1.img and modemst2.img. in that images are the imei information stored.
baseband information is stored in fsg.img
but why it dont restore also the imei info in settings ? maybe its region related. we dont know that yet.
lets Discuss and find a Solution/fix for that
reserved
here i will post the possible solution ..............
1.
This will restore the IMEI numbers into settings for slot 1.
Slot1 and slot2 will be similar then.
1. Install xposed manager APK. You have to have root for that.
https://xposed-installer.de.uptodown.com/android
2. Download in the app framework v90.beta3 and install it ( all in the app)
3. Download this app from playstore (IMEI changer)
https://play.google.com/store/apps/details?id=com.vivek.imeichanger
4. Your imei is written on your u pro box back cover.
Enter the IMEI in the app. Save it and reboot.
Done!
can you maybe transfer from eragon rom thread to here the posts concerning imei?
thank you
jimibxl said:
can you maybe transfer from eragon rom thread to here the posts concerning imei?
thank you
Click to expand...
Click to collapse
Don't need to. .
In 10min .
Look into post #2
First solution will be there
I have already tested several apps from different vendors, unfortunately without success.
xdaONLINEuser said:
..
Click to expand...
Click to collapse
First solution is online
Found another solution just now.
Will check that that in a few hours.
If that works we can restore all
xdaONLINEuser said:
I have already tested several apps from different vendors, unfortunately without success.
Click to expand...
Click to collapse
The first solution was also tested by me. It worked. Try it
unfortunetly if xposed is uninstall imei is lost again
jimibxl said:
unfortunetly if xposed is uninstall imei is lost again
Click to expand...
Click to collapse
LOL . I did not tested that.just uninstalled framework and xposed app and the IMEI is gone. You are right. WTF
In ~2hours I will know if the other fix I found will work
Maybe helpful information:
For me without any changings the IMEI isn't gone. With *#06# I see two IMEI
I'm on eragon 4 but I've had to make a factory reset after update from 3 to 4 (there were some problems like system settings not working)
Laptapper said:
Maybe helpful information:
For me without any changings the IMEI isn't gone. With *#06# I see two IMEI
I'm on eragon 4 but I've had to make a factory reset after update from 3 to 4 (there were some problems like system settings not working)
Click to expand...
Click to collapse
I guess the problem of losing the IMEI was caused if someone flashed the stock rom 0227. It was overwriting modemst 1 and 2 where the IMEIs are stored. Eragon doesn't do that.
I have found appropriate tools (also via xda), which perfectly fulfill the task...
QUALCOMM smartphone write IMEI tool 1.01
QMSL IMEI and SN writer 1.4
But apparently the tools do not support the chipset, or I have not yet found a way to use the tools accordingly.
If someone has experience with these tools…
Thanks in Advance
xdaONLINEuser said:
I have found appropriate tools (also via xda), which perfectly fulfill the task...
QUALCOMM smartphone write IMEI tool 1.01
QMSL IMEI and SN writer 1.4
But apparently the tools do not support the chipset, or I have not yet found a way to use the tools accordingly.
If someone has experience with these tools…
Thanks in Advance
Click to expand...
Click to collapse
Already tested them a few days ago. They don't work.
Feedback of my progress so far:
I use NV ram tool to try to restore IMEI.
I was able to build IMEI but it did not flashed it because of a driver (diagnostic mode) problem.
I just have to find the right driver. Lol.
Sound funny , but I have around 100 different diagnostic drivers for Qualcomm devices.. one is the right one I hope ....
Gesendet von meinem U_Pro mit Tapatalk
skeleton1911 said:
Already tested them a few days ago. They don't work.
Feedback of my progress so far:
I use NV ram tool to try to restore IMEI.
I was able to build IMEI but it did not flashed it because of a driver (diagnostic mode) problem.
I just have to find the right driver. Lol.
Sound funny , but I have around 100 different diagnostic drivers for Qualcomm devices.. one is the right one I hope ....
Gesendet von meinem U_Pro mit Tapatalk
Click to expand...
Click to collapse
all the best man to succeed, we are with you
Been looking through XDA threads hoping to get some ideas on missing IMEI thing. I'm also trying to run a NV Backup using the QFIL program and up to now I wasn't able to do that, the blue 'start' button was always disabled(diagonal gray stripes) with the COM port and diag driver ON. I think, the problem is related to the lack of IMEI/ESN etc.., because today I hooked up my spare Moto G4 Play and got the NV bckp from it. Then, after that, I actually had a little success with Upro, I used the same diag driver which poped-up with Moto, HS-USB 9091 (instead of 900D), it's also a Qualcomm driver, found it on my desktop(uncheck: show compatible drivers to see it) Not a total success but, at least I could start the bckp. It failed, still, I've never gotten this far. Can you try and see if you're able to get the NV backup w/o IMEI#?
Is there a way to somehow convert to text the .qcn files? How about editing it, if that's possible then the imei could be written into saved files and fed back into the phone using 'restore'. Just saying, am clueless on that.
Ok, here is that link from another XDA thread and you'll find two screenshots below:
https://forum.xda-developers.com/moto-g4-plus/help/diag-mode-g4-qpsd-t3591683/page2
https://drive.google.com/file/d/1pCyf1xcrtsESGYCTbpJLiSoF102Kik5q/view?usp=sharing
https://drive.google.com/file/d/1xawPNNMCD39nzQJaoBfwwnf0zVFCwQTA/view?usp=sharing
I am ready to try the IMEI edit on my Upro. I was dry practicing today on .qcn files extracted from Moto 4g Play, navigating the .qcn with this editor http://mh-nexus.de/en/hxd/ , finding the proper columns and rows, playing with hex./dec. conversions guided by this: (watch?v=zn_D6TEFABQ)
But I'm still missing the most important element: the actual Qfil generated .qcn backup files from my Upro, can't get it. You guys have any suggestions?
How can i unlock lte band i do have my imei showing when i do *#06# but qpst/qxdm doesn't read my device in qpst it says no phone no esn in the com port used by my phone
jimlap30 said:
How can i unlock lte band i do have my imei showing when i do *#06# but qpst/qxdm doesn't read my device in qpst it says no phone no esn in the com port used by my phone
Click to expand...
Click to collapse
Are you in diagnostics mode? Which driver # do you see.
skeleton1911 said:
reserved
3. Download this app from playstore (IMEI changer)
https://play.google.com/store/apps/details?id=com.vivek.imeichanger
4. Your imei is written on your u pro box back cover.
Enter the IMEI in the app. Save it and reboot.
Done!
Click to expand...
Click to collapse
Its a placebo fix or better only a solution for fake/anonymize the IMEI for apps only!
If the provider needs the IMEI to connect to his network it is not working!
With a app on phone you can not bring back the IMEI, its stored in the NVRAM.
You have absolut no write access to this "partiton" on a running system.
for real restoring you must flash it!
I've got the ZTE Blade V Smart (2050) that uses the MT6771 processors. It had been rooted on Android 9 which caused me to lose my IMEI, but I removed root, and then updated the phone to Android 10. After updating I received the NVRAM ERROR in my wifi settings. What did I do? I did a data factory reset thinking it would update properly the next time. Wrong! I tried over 20 times at least. I have searched high and low online for a backup of the firmware to download so I can achieve root again and fix the wifi error. No success unless I wanna pay. Then, I attempted to do a ROM dump using Wwr and SPFT. No success there either. After that I began downloading the crack box programs to see if I could possibly get one to root me or do anything. In doing so, I discovered that the MT6771_scatter.txt for Android 10 is not the same as on Android 9. So my question is, how can I dump my ROM if the scatter files from Android 9 & 10 are different? I would really like to have root again also so I can fix the NVRAM wifi issue, as well as use some of the perks of having Magisk and it's modules on my phone. Thank you in advance for any assistance.
finnroth69 said:
I've got the ZTE Blade V Smart (2050) that uses the MT6771 processors. It had been rooted on Android 9 which caused me to lose my IMEI, but I removed root, and then updated the phone to Android 10. After updating I received the NVRAM ERROR in my wifi settings. What did I do? I did a data factory reset thinking it would update properly the next time. Wrong! I tried over 20 times at least. I have searched high and low online for a backup of the firmware to download so I can achieve root again and fix the wifi error. No success unless I wanna pay. Then, I attempted to do a ROM dump using Wwr and SPFT. No success there either. After that I began downloading the crack box programs to see if I could possibly get one to root me or do anything. In doing so, I discovered that the MT6771_scatter.txt for Android 10 is not the same as on Android 9. So my question is, how can I dump my ROM if the scatter files from Android 9 & 10 are different? I would really like to have root again also so I can fix the NVRAM wifi issue, as well as use some of the perks of having Magisk and it's modules on my phone. Thank you in advance for any assistance.
Click to expand...
Click to collapse
Use Mtkclient to Backup/flash any Partition wanted. You won't need a scatter.txt for this. You can make your own by using Mtkclient to read/pull the GPT table only (partition info) using:
Code:
python mtk printgpt
then manually creating a scatter file on your own by editing the old Android 9 scatter (and changing differences). Hope I helped
Slim K said:
Use Mtkclient to Backup/flash any Partition wanted. You won't need a scatter.txt for this. You can make your own by using Mtkclient to read/pull the GPT table only (partition info) using:
Code:
python mtk printgpt
then manually creating a scatter file on your own by editing the old Android 9 scatter (and changing differences). Hope I helped
Click to expand...
Click to collapse
I ended up being able to pull the scatter using mtk deauthorization tool. Still having trouble with Wwr, SPFT, Meta, and MTK Tool all reading my phone though. They ask get to a certain point in the process and just stop. Then the apps usually crash. I checked and rechecked my drivers, I've uninstalled and reinstalled everything several times. It only happens with those apps. This is the same as it was doing before when I was running Android 9 also. I can get any other apps to read my phone, but the ones I need to actually read... No so much.
finnroth69 said:
I've got the ZTE Blade V Smart (2050) that uses the MT6771 processors. It had been rooted on Android 9 which caused me to lose my IMEI, but I removed root, and then updated the phone to Android 10. After updating I received the NVRAM ERROR in my wifi settings. What did I do? I did a data factory reset thinking it would update properly the next time. Wrong! I tried over 20 times at least. I have searched high and low online for a backup of the firmware to download so I can achieve root again and fix the wifi error. No success unless I wanna pay. Then, I attempted to do a ROM dump using Wwr and SPFT. No success there either. After that I began downloading the crack box programs to see if I could possibly get one to root me or do anything. In doing so, I discovered that the MT6771_scatter.txt for Android 10 is not the same as on Android 9. So my question is, how can I dump my ROM if the scatter files from Android 9 & 10 are different? I would really like to have root again also so I can fix the NVRAM wifi issue, as well as use some of the perks of having Magisk and it's modules on my phone. Thank you in advance for any assistance.
Click to expand...
Click to collapse
And where did you get it 10 Android ?