Related
Hi,
I bought a second hand samsung s4(a few days old) from my friend...after inserting my sim in it, it isn't showing any network signals...when i looke in settings for network operators and selected automatically choose preferred networks, it shows "Can't connect to this network right now please try again later"...have removed and reinserted my sim in it but still no benifit...Have searched about my problem and found a related problem with another devices (s3) and it told them to place an EFS folder in root if you have backup but it was for a rooted phone and mine is not...So, Please help me
Hi.
I come from another post looking for a solution to my dilemma (http://forum.xda-developers.com/galaxy-s5/help/switch-stock-rom-t2866861#post55236673), thanks to fffft member found that I can open the band 4 of my cell S5 using the QPST program, however I can not find a modified .qcn file that corresponds to my model (G900F).
What I have done is make a backup of my original .qcn (which understand not share because there goes my IMEI) and I need advice from someone who knows that is the parameter that should change to open the AWS band 4.
Much appreciate your help.
I see that nobody has answered, if it was not for lack of cooperation, or because no one has had this problem.
Continue researching and achieve get qcn file G900M, which is super, but not left so installed as well, the QPST program generates an error and does not let install, so proceeded to compare them to see how different they are, and actually they are very different in their hexadecimal setting.
The issue now is, I need someone to tell me what are the parameter I have to modify my original qcn (my G900F) to enable AWS band 4.
Thank you for your help.
..
Hello again fffft.
I will try to explain everything in the best way. I can not send the file qcn G900M, because I have understood that within the IMEI can be identified, and the first thing I asked the person I give it to me was that change could not deliver it to anyone.
Now step by step to do was the following (taken from this forum http://forum.xda-developers.com/showthread.php?t=2291589 ):
Install phoneutil.apk in my phone.
Install QPST 2.7 build 323.
Choose the usb connection “RNDIS + DM + MODEM” from the menu that comes by typing *#0808#.
On the Ports tab of the program QSPT set the COM port corresponding to the cell (seeing that port recognizes the cell through Device Manager).
Choose “Start Clients” and choose “SOFTWARE DOWNLOAD”.
Hit the “Restore” tab, set port to COM number, choose the QCN file, and start.
Attached two images, one in which it is seen that the process is running smoothly, and a second in which shows the error.
With regard to your question about the RMNET protocol, for I must say I have no idea regards, because as I said I am still a newbie.
Finally and with respect to qcn file G900T me would be very very difficult to get the file G900M was relatively easy (not as easy lol) but because here in my country is the model that is sold, but the model does not get G900T no way.
I remain attentive to your suggestions, and thanks again for the help.
..
I thought S5 supports AWS band as well as other bands? I bought S5 from Rogers and use it with Wind mobile (Canada).
..
Hi.
Well, with my answer are attached to the two qcn files, not if it's okay to post them because I do not know which is the information that I'm giving, but I'll trust you fffft.
Review the entries with IMEI and clear, making this process and I thought this would be a very good explanation of why not to overwrite the original file leaves the cell, because the second IMEI not for the phone, but even if this were true, no understand how in the above forum they spread a qcn file for S4 that everyone could use.
Anyway, I hope that with this we can advance the issue to see if I can get out of this mess.
Thanks again.
..
Ok fffft, I found the parameter you say, but now my question is, as I edit the file qcn? I need some special program?
Loperaco said:
Ok fffft, I found the parameter you say, but now my question is, as I edit the file qcn? I need some special program?
Click to expand...
Click to collapse
Well, download the program XVI32 to edit the hexadecimal, apparently was successful but eventually the program generated the same mistake I had already seen, indicating "Could not reset the phone. COmmunication Errors Occurred".
Will you help me?
..
Hi there.
I have an interesting fact to share, because I could not properly complete the process to overwrite the qcn file then started to review the QPST program and its functions, among these I found the display content on qcn files through this for any entries who had been unable to write and determine that it was possible to write the file so qcn "hot" (ie directly on the phone) Oh and surprise! when I saw that the code / parameter that indicated fffft if I had changed even though the restore process had not been successful.
Anyway achieved modify the parameter in question and probe the cell after this, but still not achieve even connect AWS band 4, so despite the success the result was a failure.
Knowing this now accept suggestions from all of you experts.
..
Got a little further, but the bands did not get enabled...
fffft said:
Docx? Shouldn't those be .qcn files?
Anyway, you should try encouraging someone to post a NV dump from their 900T for comparison. You can check the existing AWS threads to confirm, but as I recall to enable AWS on earlier Galaxy models, required editing NV_RF_BC_CONFIG_l from 80 03 e8 04 to 80 03 e8 06
So ostensibly you will want to make the same change on your 900F. Comparing your NV to a 900T would lend confidence to that presumption.
.
Click to expand...
Click to collapse
fffft, Laperaco,
I am pursuing the same Band change as described here and have an update of the things that I was able to discover:
1) I was able to use QPST and pull NV backup from my phone - see my JJ_ATT_S5_Bands_Tester_No_IMEI (IMEI removed in Line 550)
**Note that I was not able to restore any QCN back to my phone in either USB mode (and I think this is what Loperaco was talking about), but...
2) I was able to program my phone directly using RF NV Item Manager, but did not get desired results (see below):
- a) I changed 1877 NV_RF_BC_CONFIG_l from 80 03 e8 04 to 80 03 e8 06 and nothing changed - i.e. radio still worked and I was still getting EDGE (no HSPA+)
- b) I tried changing the next line 1878 NV_RF_HW_CONFIG_I from f6 to 2c, because I saw that in another QCN file I found online. That actually "killed" my radio altogether, at least until I changed it back to f6
- c) Upon further inspection of the SM-N900T file I found online (too big to upload here), I saw that there are quite a few differences, which leads me to believe that additional configurations must be made to take advantage of the HSPA+ bands.
!! Please !! If someone with T-Mobile SGS5 looking at this, could you pull your QCN, mask IMEI if you'd like and post it here for comparison.
Otherwise, fffft, do you have any other thoughts regarding the changes needed...?
Last note that files are posted as .qcn.txt, becuase forum does not allow posting of qcn file extensions. Just remove .txt and you will have original qcn.
Thanks,
JJ
fffft said:
Your reluctance to document what you have done in detail is unfortunate because it prevents us from confirming that you did as you summarized or possibly discern any errors along the way. Nor did you tell us how you concluded that the phone did not connect to AWS, whether the changes were persistent after a reboot or what the service mode showed for activity after using the diagnostic menu to lock the handset to AWS, et cetera.
Of particular value would be a before and after NV dump from your phone, alongside a 900T NV dump. Which would illustrate both the required changes and any progress made with the attempted write.
To reply to your question, two obvious possibilities are apparent
1. That you changed the parameter as you summarized and that was insufficient to effect the desired change. Which would mean that the required parameter is different for the S5 than preceding Galaxy models for some reason e.g. that a different parameter needs editing or that radio changes are needed as well, even though that was not the case for the S3 & S4.
2. That you made some inadvertent error in your procedure that you didn't discern. No one can look for possible errors in the absence of you providing a detailed, step by step description of what you did though.
.
Click to expand...
Click to collapse
Ok ok, let me see how I can solve this.
First of all is not reluctance, I tried to be clear in how I do things, but I'll try again:
1. I bought a model of cell G900F that has disabled the AWS band 4.
2. I tried using the QPST program to replace the qcn file with one that corresponded to a G900M model, since in this model if the band 4 is enabled, but the process to make it in the program generated the error "Could not reset the phone. Communication Errors Occurred ".
3. I do not know how or if the QPST program writes an error log, so I do not know where to look it can be sent. I explain how to install and run the program each button is a bit wasteful, but I followed the steps in this forum http://forum.xda-developers.com/showthread.php?t=2291589
4. After this, and having received suggestions from fffft, I tried modifying the original qcn file from my phone, because I thought that perhaps the problem was because they were different models and finally the phone would not allow me to put a qcn file of another model. The modifications I did was change the parameter NV_RF_BC_CONFIG_l from 80 03 e8 04 to 80 03 e8 06. This is done by the program XVI32 modifying the hexadecimal.
5. I tried again using the option to restore the qcn file in QPST program, but got the same error "Could not reset the phone. Communication Errors Occurred".
6. I assumed I had to think of something else so it was when using the RF NV Manager (included in the installation program QSPT) for locate the actual file contents qcn on my phone, and I realized that despite the error obtained in restoring the file using the QPST program the parameter indicated in paragraph 4 of this list if it had changed.
7. I proceeded to check the signal and actually still had no access to the 4G network, the most that is connected to the HSDPA + network.
8. I read the comments from fffft and now I'm writing this.
I hope I was clear in my problem and have made a good step by step.
Now the issue is that:
A. I do not know how to access the diagnostic menu that enables or disables the AWS band, so I do not understand fffft what you're talking about.
B. I agree that modify only the parameter in question is not sufficient, otherwise the matter would be solved.
C. It is possible that I made a mistake as you point out, I finally am new to this, but still I explained my process so I am attentive to suggestions.
Thanks for the help.
JJ_Boja said:
fffft, Laperaco,
I am pursuing the same Band change as described here and have an update of the things that I was able to discover:
1) I was able to use QPST and pull NV backup from my phone - see my JJ_ATT_S5_Bands_Tester_No_IMEI (IMEI removed in Line 550)
**Note that I was not able to restore any QCN back to my phone in either USB mode (and I think this is what Loperaco was talking about), but...
2) I was able to program my phone directly using RF NV Item Manager, but did not get desired results (see below):
- a) I changed 1877 NV_RF_BC_CONFIG_l from 80 03 e8 04 to 80 03 e8 06 and nothing changed - i.e. radio still worked and I was still getting EDGE (no HSPA+)
- b) I tried changing the next line 1878 NV_RF_HW_CONFIG_I from f6 to 2c, because I saw that in another QCN file I found online. That actually "killed" my radio altogether, at least until I changed it back to f6
- c) Upon further inspection of the SM-N900T file I found online (too big to upload here), I saw that there are quite a few differences, which leads me to believe that additional configurations must be made to take advantage of the HSPA+ bands.
!! Please !! If someone with T-Mobile SGS5 looking at this, could you pull your QCN, mask IMEI if you'd like and post it here for comparison.
Otherwise, fffft, do you have any other thoughts regarding the changes needed...?
Last note that files are posted as .qcn.txt, becuase forum does not allow posting of qcn file extensions. Just remove .txt and you will have original qcn.
Thanks,
JJ
Click to expand...
Click to collapse
Hi JJ.
We are indeed talking about the same issue, however I see a difference and that is that despite not having the band 4 AWS enabled on your phone, this only gives you the edge band, however my phone without enabling the band 4 gives me HSDPA+, so my question, just out of curiosity, is what is the frequency at which your operator transmits the EDGE network?
Loperaco said:
5. I tried again using the option to restore the qcn file in QPST program, but got the same error "Could not reset the phone. Communication Errors Occurred".
6. I assumed I had to think of something else so it was when using the RF NV Manager (included in the installation program QSPT) for locate the actual file contents qcn on my phone, and I realized that despite the error obtained in restoring the file using the QPST program the parameter indicated in paragraph 4 of this list if it had changed.
Click to expand...
Click to collapse
Laperaco,
1) I was also unable to load qcn file from backup even without modifications, so...
2) I made modifications directly to the phone using RF NV Item Manager*
*Note from my post that changing line 1877 made no difference in connectivity for me.
3) This specific connection is below (although it naturally fluctuates):
Network Type: EDGE:2
GSM RSSI: -89db (63%) 12 asu
GSM Signal Strength: 13db (42%)
Preferred Network Type is LTE/GSM autio (PRL)*
*Non-GSM selections (WCDMA, LTE-only, etc) simply do not connect, so no HSPA+ for me
JJ
JJ_Boja said:
Laperaco,
1) I was also unable to load qcn file from backup even without modifications, so...
2) I made modifications directly to the phone using RF NV Item Manager*
*Note from my post that changing line 1877 made no difference in connectivity for me.
3) This specific connection is below (although it naturally fluctuates):
Network Type: EDGE:2
GSM RSSI: -89db (63%) 12 asu
GSM Signal Strength: 13db (42%)
Preferred Network Type is LTE/GSM autio (PRL)*
*Non-GSM selections (WCDMA, LTE-only, etc) simply do not connect, so no HSPA+ for me
JJ
Click to expand...
Click to collapse
Ok JJ, we are going through the same steps, we must wait for more help, I'll keep researching but I see that not many people have our problem.
I have a question is that with that code or through option that could see data that you send me.
Any information or change that has put it in the post.
..
Hi all, i've purchased an SM-G900F but there is a problem, it has rooted.
I've noticed those :
- I can see IMEI number (if i do #*06#) but my EFS folder is empty
- When turn on WiFi , the device will reboot automatically and appear " Factory Mode is On"
- i can make first call with sim , after i'm unable to call , but the 3G network works
- Whit ES File Explorer i've see that my efs folder is empty (But i can see my IMEI with secret code)
- In Device Info i see one time "Official Status" and another time "Personalized Status"
I'm tinking that old owner is a very st......d guy. Howewer these are all information :
Model : SM-G900F
Version : 4.4.2
BASEBAND : NE2
BUILD : NE2
What do you think? How i can solve the problems?
EDIT 1 : i've formatted from recovery , now it ask me to insert the samsung account of old owner...
- Use Phone INFO ★Samsung★ app to obtain more detailed information about your device, including Model, Baseband, Bootloader, CSC, IMEI, S/N, etc...
- May be the Reactivation lock has been enabled. You should ask the ex-owner for the account.
qwertyup88 said:
Hi all, i've purchased an SM-G900F but there is a problem, it has rooted.
I've noticed those :
- I can see IMEI number (if i do #*06#) but my EFS folder is empty
- When turn on WiFi , the device will reboot automatically and appear " Factory Mode is On"
- i can make first call with sim , after i'm unable to call , but the 3G network works
- Whit ES File Explorer i've see that my efs folder is empty (But i can see my IMEI with secret code)
- In Device Info i see one time "Official Status" and another time "Personalized Status"
I'm tinking that old owner is a very st......d guy. Howewer these are all information :
Model : SM-G900F
Version : 4.4.2
BASEBAND : NE2
BUILD : NE2
What do you think? How i can solve the problems?
EDIT 1 : i've formatted from recovery , now it ask me to insert the samsung account of old owner...
Click to expand...
Click to collapse
reactivation lock is on. you will need to contact old owner. There is also a way to "fix" that but not sure if it is appropriate for XDA.
kabloomz said:
reactivation lock is on. you will need to contact old owner. There is also a way to "fix" that but not sure if it is appropriate for XDA.
Click to expand...
Click to collapse
Can you send me an email ? i really need hepl
vndnguyen said:
- Use Phone INFO ★Samsung★ app to obtain more detailed information about your device, including Model, Baseband, Bootloader, CSC, IMEI, S/N, etc...
- May be the Reactivation lock has been enabled. You should ask the ex-owner for the account.
Click to expand...
Click to collapse
The guy was not traceable now. He's vanished ....
You are kinda between a rock and a hard place if reactivation lock is enabled and you don't have the login to toggle that. In most cases that means that the phone is stolen and this is an explicit anti theft feature. You need that login from the original owner. Or if you have the original receipt, you might be able to convince a Samsung repair center to disable the reactivation lock for you.
In any event, as to your original question the most likely cause of the problem is a corrupt configuration file, namely a text file named "factorymode". You can try this repair from the command line or a root aware text editor.
Code:
echo -n ON > /efs/FactoryApp/factorymode
.
fffft said:
You are kinda between a rock and a hard place if reactivation lock is enabled and you don't have the login to toggle that. In most cases that means that the phone is stolen and this is an explicit anti theft feature. You need that login from the original owner. Or if you have the original receipt, you might be able to convince a Samsung repair center to disable the reactivation lock for you.
In any event, as to your original question the most likely cause of the problem is a corrupt configuration file, namely a text file named "factorymode". You can try this repair from the command line or a root aware text editor.
Code:
echo -n ON > /efs/FactoryApp/factorymode
.
Click to expand...
Click to collapse
Just now the guy told me account and password . Now i'm able to use my phone !!!!! But now i see that the efs folder is empty...
qwertyup88 said:
Just now the guy told me account and password . Now i'm able to use my phone
Click to expand...
Click to collapse
Great. But you neglected to tell us if you tried (or even noticed) the suggestion to check your factory mode configuration file. The contents should show "ON" (yes, "ON") and the permissions 0644. Your efs folder may appear empty to you when it really isn't. It depends on whether you have your file browser (or command line options) set to display hidden and system files or not.
.
fffft said:
Great. But you neglected to tell us if you tried (or even noticed) the suggestion to check your factory mode configuration file. The contents should show "ON" (yes, "ON") and the permissions 0644. Your efs folder may appear empty to you when it really isn't. It depends on whether you have your file browser (or command line options) set to display hidden and system files or not.
.
Click to expand...
Click to collapse
y factory mode is on , because i can't acces my wifi, and it appear that factory mode is on. I've set to see hidden files , but now i haven't root on my device
Edit: terminal emulator say : no such file or directory
Edit 2 : Solved with terminal emulator and busy box Thanks to @leoaudio13 for his dump
These are the command for mount efs :
su
mke2fs /dev/block/mmcblk0p12
mount -w -t ext4 /dev/block/mmcblk0p12
reboot
After then , with text editor i've disabled FactoryApp in efs folder tanks to all
.
For the benefit of anyone else reading this thread, do not repeat the steps in the post above until
you understand what they do. A typo in those steps could easily cause you endless grief.
Glad you go it working.
If those steps fixed your issue, then you mislead us with erroneous information earlier. You said that you had an empty efs folder earlier. But those steps would not have been necessary or effective if that was accurate. You must have had a missing efs partition. There is a considerable difference between an empty and nonexistent item and that datum would have led us to a solution.
On a normal phone, there would be an extant efs folder and it would be automatically mounted at boot. A missing folder strongly suggests that the wrong firmware or a flash error took place. Presumably by the previous owner.
Anyone using the make filesystem command mke2fs /dev/block/mmcblk0p12 should be very careful with typos as an incorrect address could cause major corruption that would be difficult to recover from.
.
Originally Posted by qwertyup88 View Post
Hi all, i've purchased an SM-G900F but there is a problem, it has rooted.
I've noticed those :
- I can see IMEI number (if i do #*06#) but my EFS folder is empty
- When turn on WiFi , the device will reboot automatically and appear " Factory Mode is On"
- i can make first call with sim , after i'm unable to call , but the 3G network works
- Whit ES File Explorer i've see that my efs folder is empty (But i can see my IMEI with secret code)
- In Device Info i see one time "Official Status" and another time "Personalized Status"
I'm tinking that old owner is a very st......d guy. Howewer these are all information :
Model : SM-G900F
Version : 4.4.2
BASEBAND : NE2
BUILD : NE2
What do you think? How i can solve the problems?
EDIT 1 : i've formatted from recovery , now it ask me to insert the samsung account of old owner...
Click to expand...
Click to collapse
Ive got almost the same problem, i bought my s5 to a friend who visited Philippines from Korea, He acquired the Phone in a Pawnshop in korea, i restore the phone and now it asked me for a password which i dont know, send it to the Technician, Force to delete the account (dont know how) but the problem is that, Phone has NO SIGNAL from then on, it has a NO signal above instead of a bar signal, EFS folder is empty, IMEI was null 000000000000000.
Anybody has the same experience? how can i fix this? please help.
Not perfectly solved .... After first call it don't connect to the network. Only after reboot it connect.
Any suggestions ?
qwertyup88 said:
Not perfectly solved .... After first call it don't connect to the network. Only after reboot it connect.
Any suggestions ?
Click to expand...
Click to collapse
could be a block imei by the operator? if it is POSSIBLE to solve? or it could be due however to the efs folder, or the firmware, modem?
edreab86 said:
Ive got almost the same problem, i bought my s5 to a friend who visited Philippines from Korea, He acquired the Phone in a Pawnshop in korea, i restore the phone and now it asked me for a password which i dont know, send it to the Technician, Force to delete the account (dont know how) but the problem is that, Phone has NO SIGNAL from then on, it has a NO signal above instead of a bar signal, EFS folder is empty, IMEI was null 000000000000000.
Anybody has the same experience? how can i fix this? please help.
Click to expand...
Click to collapse
it's a different problem , you have a null imei , in your case it's more difficult to resolve.
Originally Posted by qwertyup88
it's a different problem , you have a null imei , in your case it's more difficult to resolve.
Click to expand...
Click to collapse
As you can read i said, Ive got almost the same problem, i don't say we have the same problem. in a sense that previous owner account or the reactivation lock is present. sorry if i made a statement that bothers you, just looking for a solution.
hello guys, always about the efs folder I was reading this post: http://forum.xda-developers.com/showthread.php?t=2705524.
according to you through this tool is possiblile restore the backup I had done with samsung tool? I would like to try this because the efs folder on my sm-g900f is 23kb, but the backup I had done with samsung tool is 14mb !! what do you think?
People, i'm going crazy with this...
In these last days i've been trying to make my Gionee work but with no results...
All works GPS, WIFI, FM Radio and even NFC... all but what is most important in a phone, the ability to make and receive calls/sms etc... No signal...
At this time i believe its the modemst1 that is damage some how... the modemst2 is ok and it has the IMEI...
Both of this files are at /dev/block/platform/msm_sdcc.1/by-name/, and by what i can tell their both 1.5Mb...
It seems that modemst1 might contain other relevant information for the process of registering on the network...
What i ask now doesn't requires an expert knowledge of Android.
I believe that any Android user should know this operations, for his own safe guard!
During the process THE SIM CARD MUST BE OFF THE PHONE
Changing IMEIs
This process can be skiped if you trust me and believe when i say that i dont wont your IMEI.
Just want my new phone to work again... As soon has i got your backup and restore it, i'll change the IMEI to my own...
Requirements:
EFS_Professional_2.1.80_BETA - Download HERE
This tool can be used to change the IMEI. Change it 00000(...) before start the backup and after completed change it back to your IMEI.
During the process THE SIM CARD MUST BE OFF THE PHONE
1 - Open application and choose "Qualcomm NV Tools" press ok to confirm
2 - Select the Diagnostics Port and press connect
3 - Go to "Secure Ops" and press SEND the Diag password
4 - Check the IMEI (Dec) box and change the IMEI
5 - Below the IMEI (Flipped) area make sure its selected Phone and press Write
6 - Disconnect and reboot the phone. Confirm if your IMEI has changed before starting the backup process
Process 1 - Backup to IMG files
Requirements:
- ADB available on your PC or Terminal Emulator app installed in your phone
- Phone rooted and BusyBox installed [get BusyBox from PlayStore its free]
Using the Terminal Emulator or ADB in command line, type these commands:
Code:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/storage/sdcard0/efs1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/storage/sdcard0/efs2.img
Process 2 - Backup with TWRP Recovery
Requirements:
- TWRP Recovery installed - Download version 2.8.6.0 HERE
1 - Reboot into Recovery Mode
2 - Press Backup
3 - Select only the EFS partition
4 - Rename the backup (optional) and press Backup
In both processes you can choose just to share with me only the modemst1 backup.
I believe that the IMEI information is on the modemst2.
The backup procedures dont have any risk to your phone.
Changing the IMEI carrys some risks... If you're not sure of this, just DON'T DO IT.
Or simply trust in me, and backup without changing your IMEI
Again, people i just can't put in words the suffering that i've been in this last 2 weeks...
Please anyone, just end my personal hell...
Thanks you all
please someone share you efs backup from e7 32GB indian version..
Hi friends We often suffer hard brick in our devices .
Even after flashing stock recovery . IMEI is not recovered
its easy to recover imei in MTK based devices but when it comes to qualcomm based devices
it is a big mess
This is my First Tutorial
how to recover lost IMEI in yureka yunqiue & other some qualcomm devices
im not responsible if anything wrong happen to your device
Tools you need
QXDM professional
usb hs-diagnostic 9006 driver
adb tool & driver
terminal app
now lets begin
1) Root your bricked phone & install terminal app (Note :- assuming you flashed stock rom or custom rom & you are facing imei lost issue )
now grant terminal app su permission by typing
SU in the app
in terminal type this code
Code:
setprop sys.usb.config diag,adb
now connect you phone to the usb
if you have installed the drivers correctly your phone will be detected by you system in diagnostics mode
now here is the trick
IMEI information is located inside the NV_ITEMS ==550
open qxdm professional
goto communication
browse to NV_ITEMS
now search for 550 in Item number
select the option dual sim (sim 0 stands for SIM1 and 1 stands for SIM2)
Code:
IMEI example "123456-78-9012340"
sort it out 1 ,23 ,45 ,67 ,89 01 ,23 ,40
{ 0x08, 0x1A, 0x32, 0x54, 0x76, 0x98, 0x10, 0x32, 0x04 }
As you can see i have sorted it out & swaped the values
0x08 is the length keep it as it
0x1A = first digit of IMEI with A
0x32 = swaped 23 to 32
.
.
after you are done putting value of your IMEI in sim 1 press the write button & wait few sec
now repeatg the step for sim2
Reboot Your Phone & voila
Hit Thanks if you think i have helped you
I just debricked my yureka plus and tried many tutorials to recover my imei numbers but didn't worked now i will try this and let you know what happens next!
It Works
Ty for this tutorial it worked for me
I recovered my IMEI using this TY again :victory:
Thanks a million for your help dude. Yours is the only method which worked on my Yu Yureka with cm12.1
I spent endless hours and wasted almost 3 gb of useless downloads. God bless you and may all your projects shine brightly in all your future ventures. Wish I could hit that thanks button a few hundred times........
Warmest regards
this tutorial it worked for me
I recovered my IMEI using this step but network not show and not show sim card
QXDM returns "read only" error. When i edit the contents with the correct ones and press write, the error is seen below as nv contents read only mode
sohail0098 said:
QXDM returns "read only" error. When i edit the contents with the correct ones and press write, the error is seen below as nv contents read only mode
Click to expand...
Click to collapse
same thing happened to me also.
i am using oneplus 2 and lost imei of one sim
what device you are using?
did you got any fix for that?
---------- Post added at 03:57 AM ---------- Previous post was at 03:54 AM ----------
botnet.py said:
Hi friends We often suffer hard brick in our devices .
Even after flashing stock recovery .
Click to expand...
Click to collapse
i followed the exact steps but encountered one problem.
using oneplus 2 and trying to recover one lost imei
when i select slot 1 for second sim it says it is not active and even when i try to edit and write it says its write protected.
any help in that case?
ashu01 said:
same thing happened to me also.
i am using oneplus 2 and lost imei of one sim
what device you are using?
did you got any fix for that?
---------- Post added at 03:57 AM ---------- Previous post was at 03:54 AM ----------
i followed the exact steps but encountered one problem.
using oneplus 2 and trying to recover one lost imei
when i select slot 1 for second sim it says it is not active and even when i try to edit and write it says its write protected.
any help in that case?
Click to expand...
Click to collapse
share screenshot .....& did u selected dual sim ?& double check if ur phone is rooted properly
ashu01 said:
same thing happened to me also.
i am using oneplus 2 and lost imei of one sim
what device you are using?
did you got any fix for that?
---------- Post added at 03:57 AM ---------- Previous post was at 03:54 AM ----------
i followed the exact steps but encountered one problem.
using oneplus 2 and trying to recover one lost imei
when i select slot 1 for second sim it says it is not active and even when i try to edit and write it says its write protected.
any help in that case?
Click to expand...
Click to collapse
Just reinstall your rom by wiping internal storage also. Then let the phone boot. Don't install gapps for quicker bootup. Then after restoring imei flash the rom of your choice. Try cm nightly first for recovering imei.
sohail0098 said:
Just reinstall your rom by wiping internal storage also. Then let the phone boot. Don't install gapps for quicker bootup. Then after restoring imei flash the rom of your choice. Try cm nightly first for recovering imei.
Click to expand...
Click to collapse
you got your IMEI back??
i have tried many things..
could you please list the steps you have done.
and how you got rid of that write protected issue?
ashu01 said:
you got your IMEI back??
i have tried many things..
could you please list the steps you have done.
and how you got rid of that write protected issue?
Click to expand...
Click to collapse
I was on cm13 unofficial build. I tried qxdm professional but there was this write protected error. I connected my device in fastboot mode and erased system. Then hotbooted TWRP (latest) and flashed the same rom again after wiping data and internal storage using rm rf. Then i let the rom boot up. (Without Gapps). Then i again tried the same steps as mentioned above. And after i got imei back, i rolled to my favourite rom. Hope you get back your imei soon.
lost yureka imei number and baseband unknown
botnet.py said:
Hi friends We often suffer hard brick in our devices .
Even after flashing stock recovery . IMEI is not recovered
its easy to recover imei in MTK based devices but when it comes to qualcomm based devices
it is a big mess
This is my First Tutorial
how to recover lost IMEI in yureka yunqiue & other some qualcomm devices
im not responsible if anything wrong happen to your device
Tools you need
QXDM professional
usb hs-diagnostic 9006 driver
adb tool & driver
terminal app
now lets begin
1) Root your bricked phone & install terminal app (Note :- assuming you flashed stock rom or custom rom & you are facing imei lost issue )
now grant terminal app su permission by typing
SU in the app
in terminal type this code
Code:
setprop sys.usb.config diag,adb
now connect you phone to the usb
if you have installed the drivers correctly your phone will be detected by you system in diagnostics mode
now here is the trick
IMEI information is located inside the NV_ITEMS ==550
open qxdm professional
goto communication
browse to NV_ITEMS
now search for 550 in Item number
select the option dual sim (sim 0 stands for SIM1 and 1 stands for SIM2)
Code:
IMEI example "123456-78-9012340"
sort it out 1 ,23 ,45 ,67 ,89 01 ,23 ,40
{ 0x08, 0x1A, 0x32, 0x54, 0x76, 0x98, 0x10, 0x32, 0x04 }
As you can see i have sorted it out & swaped the values
0x08 is the length keep it as it
0x1A = first digit of IMEI with A
0x32 = swaped 23 to 32
.
.
after you are done putting value of your IMEI in sim 1 press the write button & wait few sec
now repeatg the step for sim2
Reboot Your Phone & voila
Hit Thanks if you think i have helped you
Click to expand...
Click to collapse
i have lost yureka imei number how to recover imei number? can i recover it by flashing stock rom? currently i am using cm12.1 in my phone. sim is not detected network is not recognize what should i do. should i follow this guide or flash stock rom? plz help me
Please provide links for qxdm professional
Recoverd imei bt no signals on lte H.E.L.P............
sohail0098 said:
I was on cm13 unofficial build. I tried qxdm professional but there was this write protected error. I connected my device in fastboot mode and erased system. Then hotbooted TWRP (latest) and flashed the same rom again after wiping data and internal storage using rm rf. Then i let the rom boot up. (Without Gapps). Then i again tried the same steps as mentioned above. And after i got imei back, i rolled to my favourite rom. Hope you get back your imei soon.
Click to expand...
Click to collapse
Hello Sohail,
Greetings from Karnataka,
Bro, Im in dire need of IMEI fix, WRT Yu Yureka.
Is it possible to help me?
Ive also created a thread, with relevant info :
https://forum.xda-developers.com/yureka/orig-development/yu-imei-issue-t3605198
Thanks
ashu01 said:
you got your IMEI back??
i have tried many things..
could you please list the steps you have done.
and how you got rid of that write protected issue?
Click to expand...
Click to collapse
Have you installed stock ROM v1?
If the above post doesn't work then you can follow this ..My Name Suman Das..I myself have done this.
Believe Me you will be successfull..
Step 1:Search Google for ".qcn" file for yunique / yureka whatever you have...
Step 2: Download qpst configuration tool. and istall it on your computer..
Step 3: Root Your Phone..Kingroot or SuperSu .zip can be used..
Step 4: Download And Install Terminal Emulator apk from any where..
Step 5:Connect your phone to PC With USB Debugging mode enabled..
Step 6: Open terminal Emulator...and Type this commands to Enable Diag mode of oyur mobile into PC..
adb shell(then enter)
su(then enter)
setprop sys.usb.config diag,adb(then enter)
After this your phone will be connected to PC In Diag Mode..then you are ready to Restore the Downloaded .qcn file ..
Step 7: Go To PC Open QPST Configuration & Check Ports for Qualcomm Port DIAG In Device Manager..
Step 8: Now you will see your Phone in QPST Configuration .Now click on Start Clients In the Menu Bar Of QPST and go to Software Download..
Step 8: Click on Port Browse option and select your phone.Then Go to Restore.And browse for your ".qcn" file and click on restore...
and then You have successfully Restored your phone back .then Simply restart your phone and it's ready..
---------- Post added at 12:41 PM ---------- Previous post was at 12:19 PM ----------
sourabhlangoo said:
Recoverd imei bt no signals on lte H.E.L.P............
Click to expand...
Click to collapse
If the above post doesn't work then you can follow this ..My Name Suman Das..I myself have done this.
Believe Me you will be successfull..
Step 1:Search Google for ".qcn" file for yunique / yureka whatever you have...
Step 2: Download qpst configuration tool. and istall it on your computer..
Step 3: Root Your Phone..Kingroot or SuperSu .zip can be used..
Step 4: Download And Install Terminal Emulator apk from any where..
Step 5:Connect your phone to PC With USB Debugging mode enabled..
Step 6: Open terminal Emulator...and Type this commands to Enable Diag mode of oyur mobile into PC..
adb shell(then enter)
su(then enter)
setprop sys.usb.config diag,adb(then enter)
After this your phone will be connected to PC In Diag Mode..then you are ready to Restore the Downloaded .qcn file ..
Step 7: Go To PC Open QPST Configuration & Check Ports for Qualcomm Port DIAG In Device Manager..
Step 8: Now you will see your Phone in QPST Configuration .Now click on Start Clients In the Menu Bar Of QPST and go to Software Download..
Step 8: Click on Port Browse option and select your phone.Then Go to Restore.And browse for your ".qcn" file and click on restore...
and then You have successfully Restored your phone back .then Simply restart your phone and it's ready..
Download Link For Softwares---https://drive.google.com/folderview?id=0B-0bWbXeDJt4dGMyVkF2TnBSVWs
Got the solution
I was struggling for many days and it was so simple though I got my IMEIs back by just flashing Volte modem file. A huge thanks to that person who somewhere in some thread mentioned this step.You are great bro.
codeddanny said:
I was struggling for many days and it was so simple though I got my IMEIs back by just flashing Volte modem file. A huge thanks to that person who somewhere in some thread mentioned this step.You are great bro.
Click to expand...
Click to collapse
You mean if i reflash the volte modem, i can get back my imei?
Sent from my YU5510 using Tapatalk