Hey guys.
I know there are a lot of threads out there on this, but there is also a fair amount of conflicting information. Also, one thread I found seems to suggest the Captivate may work differently than other phones. That particular thread (listed below) seems to suggest the IMEI is directly tied to the model #, and editing the NV_DATA.BIN will fix the IMEI, even though it doesn't generally work on other devices)
My IMEI has turned into a generic one (quite some time ago, and I have no idea exactly when). I do not have a backup of the EFS folder. My phone works just fine, and I know for a fact I'm never returning it under warranty.
Is there any reason for me to care about this? Can my phone suddenly stop working one day because of this?
If I SHOULD be concerned, some threads suggest it's lost forever... some say flashing back to stock fixes it, and others have more complicated methods.
One promising method I've found involves a few simple edits to the NV_DATA.BIN file, but the thread is specific to the ATT version. I have the Rogers I896. This is the thread:
http://forum.xda-developers.com/showthread.php?t=881162&highlight=rogers
Again, if I should be concerned, are there any fellow Rogers users that would be willing to share the following Hex lines from the NV_DATA.BIN so I can try the method in that thread?
The lines are:
00188000
00188008
00188010
00188018
00188020
Thanks for any insight.
Holmes108 said:
Hey guys.
I know there are a lot of threads out there on this, but there is also a fair amount of conflicting information. Also, one thread I found seems to suggest the Captivate may work differently than other phones. That particular thread (listed below) seems to suggest the IMEI is directly tied to the model #, and editing the NV_DATA.BIN will fix the IMEI, even though it doesn't generally work on other devices)
My IMEI has turned into a generic one (quite some time ago, and I have no idea exactly when). I do not have a backup of the EFS folder. My phone works just fine, and I know for a fact I'm never returning it under warranty.
Is there any reason for me to care about this? Can my phone suddenly stop working one day because of this?
If I SHOULD be concerned, some threads suggest it's lost forever... some say flashing back to stock fixes it, and others have more complicated methods.
One promising method I've found involves a few simple edits to the NV_DATA.BIN file, but the thread is specific to the ATT version. I have the Rogers I896. This is the thread:
http://forum.xda-developers.com/showthread.php?t=881162&highlight=rogers
Again, if I should be concerned, are there any fellow Rogers users that would be willing to share the following Hex lines from the NV_DATA.BIN so I can try the method in that thread?
The lines are:
00188000
00188008
00188010
00188018
00188020
Thanks for any insight.
Click to expand...
Click to collapse
Yeah sure, I'll take a look at those
address lines.
Sent from my SGH-I896 using Tapatalk
---------- Post added at 09:03 PM ---------- Previous post was at 08:37 PM ----------
Here are what I got from mine. And I'm running Stock Gingerbread 2.3.3 (Official Rogers Update).
00188000 : ....REV0
00188008 : .1....GR
00188010 : WC....SG
00188018 : H-I896ZK
00188020 : ARWC....
Nick0703 said:
Yeah sure, I'll take a look at those
address lines.
Sent from my SGH-I896 using Tapatalk
---------- Post added at 09:03 PM ---------- Previous post was at 08:37 PM ----------
Here are what I got from mine. And I'm running Stock Gingerbread 2.3.3 (Official Rogers Update).
00188000 : ....REV0
00188008 : .1....GR
00188010 : WC....SG
00188018 : H-I896ZK
00188020 : ARWC....
Click to expand...
Click to collapse
Perfect, thanks. I managed to scrape together the model number, but I tried RWC instead of GRWC, and I had the wrong Rev #. I'll give this a try.
Thanks again.
Holmes108 said:
Perfect, thanks. I managed to scrape together the model number, but I tried RWC instead of GRWC, and I had the wrong Rev #. I'll give this a try.
Thanks again.
Click to expand...
Click to collapse
I also checked out my nv_data.bin (Froyo) and found out that its RWC, I guess that the GRWC is for gingerbread.
Sent from my SGH-I896 using Tapatalk
Imei captivate changed
HAHA! Earlier today I was reminded of your exact situ and how a dev a tool had wiped my original imei and replaced it (and numerous other users) with a "anonymous" IMEI... I remember that I originally freaked out a bit..oh my what if this and that..otr I want the phone unlocked et all.
Then the nerdy fixit kicked in and I recovered the original IMEI.
Today I was looking at the new captivate GO-PHONE and reading about the RIDICULOUS ABSOLUTELY INSANE WTH OVER THE TOP data plan they INSIST a smartphone MUST have.. off contract the data plans are NUTZ... and BOOP!
I was thinking 'if i could just jumble my imei around a bit.. then they would think i was using a DUMBPHONE and i could have all the precious UNLIMITED DATA... that i certainly deserve!! ahahah!! ...and have over paid for the past 9 years!!'
The day that I called in to have my phone totally unlocked the CSR asked me to punch a few buttons on my screen and read her the string.. She told me that the code i read to her was NOT from an AT&t phone and she didnt know how to unlock it.
FORTUNATELLY... Skyrocket just went on sale for a penny. So I will be signing another 2 year agreement instead of going off the grid with SIP VOIP DATA ANON shenanigans.. but figured you..or anyone else for that matter had not yet seen the light that shined down on me today so I wanted to have ya thinking 'on the bright side'
Y!S
Holmes108 said:
Hey guys.
I know there are a lot of threads out there on this, but there is also a fair amount of conflicting information. Also, one thread I found seems to suggest the Captivate may work differently than other phones. That particular thread (listed below) seems to suggest the IMEI is directly tied to the model #, and editing the NV_DATA.BIN will fix the IMEI, even though it doesn't generally work on other devices)
My IMEI has turned into a generic one (quite some time ago, and I have no idea exactly when). I do not have a backup of the EFS folder. My phone works just fine, and I know for a fact I'm never returning it under warranty.
Is there any reason for me to care about this? Can my phone suddenly stop working one day because of this?
If I SHOULD be concerned, some threads suggest it's lost forever... some say flashing back to stock fixes it, and others have more complicated methods.
One promising method I've found involves a few simple edits to the NV_DATA.BIN file, but the thread is specific to the ATT version. I have the Rogers I896. This is the thread:
http://forum.xda-developers.com/showthread.php?t=881162&highlight=rogers
Again, if I should be concerned, are there any fellow Rogers users that would be willing to share the following Hex lines from the NV_DATA.BIN so I can try the method in that thread?
The lines are:
00188000
00188008
00188010
00188018
00188020
Thanks for any insight.
Click to expand...
Click to collapse
hey guyz i need to know the same process regarding restoring imei number for my galaxy s2 i777
i would be gratefull if any one could help out in this
i.e the lines requored to be edited in .nv_data file
thanku
I lost the imei of my cappy a couple months ago, flashin the kk4 super one click without bootloaders fixed the problem
You can find it on andorid development section on the sticky posts
Related
Long story short, my imei is not the current one under the battery and i want to get it back. Before i thought my phone wasnt unlocked and that was the problem but its not. The phone is unlocked and i even have the codes, i just want to use my own IMEI. I currently can not connect to any networks with the captivate.
So far i have tried using the .bak file in /efs with no success (different imei).
I have tried several posts on xda but all seem to unlock and not give you your proper imei back.
Any advice or information would be greatly appreciated.
Buuummmppp
b0uncyfr0 said:
Long story short, my imei is not the current one under the battery and i want to get it back. Before i thought my phone wasnt unlocked and that was the problem but its not. The phone is unlocked and i even have the codes, i just want to use my own IMEI. I currently can not connect to any networks with the captivate.
So far i have tried using the .bak file in /efs with no success (different imei).
I have tried several posts on xda but all seem to unlock and not give you your proper imei back.
Any advice or information would be greatly appreciated.
Click to expand...
Click to collapse
How did u manage to mess it up, may I ask. This way atleast u could warn the rest of the community not to mess ours up.
Its quite simple really, dont back up your /efs folder and keep messing around with roms.
I don't think anyone has solved this. Everything around the nv_data.bin file relates to unlocking and it says you must have a good IMEI number to start with. There was some 3rd party software that can fix IMEI numbers - but it required a separate breakout box. I forget the name, but many downloaded the software only to discover they needed to buy the box to get it to work.
One of mine managed to wind up with the generic imei but I have yet to see any ill effects from it.
I am sorry to hear about this, and even sorrier to have to say this, but xda does not allow posting of instruction on how one can change the imei.
Sent from my SAMSUNG-SGH-I897 using XDA App
Ok if we cant talk about this thats fine. Right now i cant connect to any networks. If someone would be willing to upload their /efs for me so i can try it out. Would that work?
Im in Australia so anything apart from that should work right??
did you ever got to restore your original imei?
Check here for a how to restore your IMEI.
Have any of you restored a Captivate's EFS folder with another phones file to fix network/IMEI problems? if so did it work?
I don't have a backup of the EFS folder (didn't know it even existed), did a factory reset (after a couple of months of having the stock 2.3.5 flashed) and suddenly I can't connect to my network provider (no phone calls/txt/3g).
I read different forums stating that I need to restore the nv_data.bin file to get the product code back (it's mostly ceros product code on 0188008 Not Active) and my IMEI is also screwed up.
I changed the product code and it apparently stayed changed, but the entirety of the file seems corrupt comparing to the videos of how to modify it and IMEI is still the fake one.
I would appreciate if I could get a backup of the EFS folder to modify to my phone if at all possible (I'm NOT on ATT nor in the US for that matter) sending it back for repairs is sadly not an option.
Trying to modify an existing file seems like my last shot to fixing my phone =( please help =D
U are out of luck, nvdata from other phones will not repair it there are only 2 option's
1. If u can find someone who can repair the NV_DATA.BIN
2. You can find a repair guy with the Z3X box.
Edit- OP if u want a fresh NV_DATA file just PM me ur email address i can mail u a copy.
I'm assuming you've tried the steps in this post?
Even if you don't have a functional EFS folder, just follow the steps as if you did. It might be worth a shot.
@jmtheiss I have question regarding the above procedure..
I tried the above with a corrupted nv file but the step mentioned in the thread aren't they are just for the product code ?
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
If I'm reading the thread correctly, rebuilding the nv_data.bin file with the proper values should repopulate the /efs folder with the correct and necessary files.
It's possible this may run into a hiccup because you're not connecting to AT&T, but in theory, it should fix your problem.
Also, it appears that other people had good results by flashing to stock first, then trying this. It looks like the stock flash reset the IMEI, and then doing this fixed the product code issue.
Thanks for replying,
I treid every thing that i was able to find to repair the NV_DATA but apart from some links to XDA there is not enough knowledge how to repair it.
I tried every possible method to repair the imei, i have more the 25 backups of different NV_DATA files with me and over the time i had looked it to every possible file and treid to compare them with each other and they all look the same to me if we look into them with the help of a HEX editor.
I tried to change the files with 2 different phones and changing them with will give u imei code >004999010640000 but u cannot not repair it with anything.
I treid this with the phone with 2.1 update 1, 2.2 and 2.3.3 but what ever they will not work.
But after some research i found that the most of the guys who repairs the imei they use the Z3X/SPT for it and that is how i did it and its was recently some 6 days back.
I am still trying to find out how (if) you can manually repair the corrupted NV ?
You can contact connexion2005 in my sig. He does IMEI repairs for a fee. But it is worth it. he is a good person and doesn't cheat people out of money!
EDIT- Don't ask people for their EFS folders.... That is sorta really stupid.
b-eock said:
You can contact connexion2005 in my sig. He does IMEI repairs for a fee. But it is worth it. he is a good person and doesn't cheat people out of money!
EDIT- Don't ask people for their EFS folders.... That is sorta really stupid.
Click to expand...
Click to collapse
I'm a recent customer and I was very pleased with his service. 1 week total and everything is back to normal. I have backed up this new EFS to MULTIPLE places.
sorry for the no reply, I contacted conexion, waiting for his reply.
I know asking for the efs folder is not bright, but it was my only and last shot. I triead all other threads and was able to change it to what they mention, add product code and everything magically gets fixed... but it saved the product code and the file and imei stayed pretty much the same, so I'm guessing that doesn't work =(
thanks for your replies all! appreciate the support
Same problem here can't locate a line 00188008 in nv_data.bin
rkkaranrk said:
U are out of luck, nvdata from other phones will not repair it there are only 2 option's
1. If u can find someone who can repair the NV_DATA.BIN
2. You can find a repair guy with the Z3X box.
Edit- OP if u want a fresh NV_DATA file just PM me ur email address i can mail u a copy.
Click to expand...
Click to collapse
I have no backup of efs folder but there are some files in efs folder but not .nv_data file . When i opened the nv_data.bin from hex editor i can locate the line 00188010 and 00188020 but not 00188008 and 00188018.
Samsung I9003
Imei Null (nothing is displayed even not 000000)
Baseband Version Unknown
I am in stock rom and tried all the possible solutions that i found and also my service mode is empty and personalizationb tab neither show network lock on nor off
Hoping for your fast response sir
Current Location Nepal
^
Use Odin or Heimdall to flash to Stock KK4 Gingerbread. That has proven to restore imei #'s for some.
edited...
Sent from my SAMSUNG-SGH-I747 using Tapatalk
depace143 said:
I have no backup of efs folder but there are some files in efs folder but not .nv_data file . When i opened the nv_data.bin from hex editor i can locate the line 00188010 and 00188020 but not 00188008 and 00188018.
Samsung I9003
Imei Null (nothing is displayed even not 000000)
Baseband Version Unknown
I am in stock rom and tried all the possible solutions that i found and also my service mode is empty and personalizationb tab neither show network lock on nor off
Hoping for your fast response sir
Current Location Nepal
Click to expand...
Click to collapse
I believe you're in the wrong section, this is for the samsung captivate (I897).
^
Oops, my eyes didn't catch the i9003 earlier.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Hello,
I managed to give some hard times to me, after flashing an i9305 that I bought from eBay. The phone was rooted, in full working order, and when I flashed it to revert to stock, I managed to check EFS CLEAR, without taking any EFS backup beforehand. My odyssey is well knows to many of you; imei null/null, baseband null, to cut a long story short, I have a Samsung Galaxy S3 lte player. It does all but recognizing sim cards and provisioning networks (fair enough as I don't have a valid imei!!!).
I have gon ethrough the whole SGS2 forum, all topics, all solutions; I even unscrewed my phone to see if I can JTAG it, and that's only because QPST and EFS Pro cannot connect to my phone. Octopus and Samsung Tool CAN connect, but I cannot write imei. I cannot upload nvm files (I have a second, stock, and a friend of mine has one rooted from where we extracted the nvm in order to flash it on mine and rewrite imei), so as I read on the i9300 relevant thread, the phone can be jtaged in order to start receiving Rx and Tx commands and be able to upload the nvms and rewrite the imei.
The thing is that nobody tried to jtag this phone, and if someone did, nobody posted the resistance that has to be short circuit. As I saw here: http://forum.xda-developers.com/showpost.php?p=28073021&postcount=5 it is possible for i9300. Is there some schematic for i9305 then, or someone knows which resistance I have to short?
Any help will be appreciated...
you can still connect through Odin or adb, connecting is not the issue. there's nothing to write, imei is not stored in plain text, it's encrypted, so you won't be able to restore it if you don't have a backup. send it to service
I have the same problem bat I have imei back up sent it to repair center and after 2 month have it back
told me replace motherboard pay 250 euro bikose the binary counter 6.
You fixed Patrida?
trifos said:
I have the same problem bat I have imei back up sent it to repair center and after 2 month have it back
told me replace motherboard pay 250 euro bikose the binary counter 6.
You fixed Patrida?
Click to expand...
Click to collapse
Kalimera filaraki!
Unfortunately I was unable to fix it. Sotmax (member on both xda and myphone) offered to fix it. He could do it for a small cost but I would have to ship it from Thessaloniki to Kefalonia, and it was during the days that the ship workers were on strike. So it would delay a bit more, and I preferred to sell it. A guy over here (who then became friend and we exchange from time to time), bought it and fixed it in 10 minutes!!!!
He has schemas and JTAGs for most of the commercial phones, and I think that he had to open it and de/solder some pcb. It's not something difficult for him, but for you and me it's an issue!! The thing is that someone is now happy with the phone, and I am happy with my new gray 9305!
So if you need to fix it and you cannot find a workaround, you can always try talking to one of these 2 guys to have your work done! I know how much Sotmax is charging for the repair, and he says his job is guaranteed. you just have to be patient for 2 days to ship and 2 days to return (the fix takes no more than 30 minutes as he said). The other guy (his nickname is demernick at insomnia) didn't tell me how much he takes to fix, but it's much quicker as he only needs 1 day to ship from Florina to Thess, and another 1 day to return, so it's half time
There is also another one guy who writes in here. He says that he can do the job over the internet via teamviewer (you just have to follow his instructions and post the original IMEI from the box and phone under the battery), and he works with Octopus box ans Samsung Tool. If he manage to fix it, he charges you 10 euros via Paypal! He spent 2 days for me, so I donated that 10 euros to him for his work, even though he couldn't fix it... his website is cvxcvx.pl and I think his name in here has something to do with the website.
All 3 of them are trusted users. 2 of them are respected in here, and demernick is well established on insomnia!
If you need some extra help, feel free to contact me!
latousakis said:
Hello,
I managed to give some hard times to me, after flashing an i9305 that I bought from eBay. The phone was rooted, in full working order, and when I flashed it to revert to stock, I managed to check EFS CLEAR, without taking any EFS backup beforehand. My odyssey is well knows to many of you; imei null/null, baseband null, to cut a long story short, I have a Samsung Galaxy S3 lte player. It does all but recognizing sim cards and provisioning networks (fair enough as I don't have a valid imei!!!).
I have gon ethrough the whole SGS2 forum, all topics, all solutions; I even unscrewed my phone to see if I can JTAG it, and that's only because QPST and EFS Pro cannot connect to my phone. Octopus and Samsung Tool CAN connect, but I cannot write imei. I cannot upload nvm files (I have a second, stock, and a friend of mine has one rooted from where we extracted the nvm in order to flash it on mine and rewrite imei), so as I read on the i9300 relevant thread, the phone can be jtaged in order to start receiving Rx and Tx commands and be able to upload the nvms and rewrite the imei.
The thing is that nobody tried to jtag this phone, and if someone did, nobody posted the resistance that has to be short circuit. As I saw here: http://forum.xda-developers.com/showpost.php?p=28073021&postcount=5 it is possible for i9300. Is there some schematic for i9305 then, or someone knows which resistance I have to short?
Any help will be appreciated...
Click to expand...
Click to collapse
Are you sure you ticked EFS clear? Could it be that you had Perseus kernel prior to installing stock? I had some similar problem and as a result my phone only works with Perseus kernel installed.
I would try installing Perseus kernel to see if the phone magically springs back to life.
Rekoil said:
Are you sure you ticked EFS clear? Could it be that you had Perseus kernel prior to installing stock? I had some similar problem and as a result my phone only works with Perseus kernel installed.
I would try installing Perseus kernel to see if the phone magically springs back to life.
Click to expand...
Click to collapse
I was aware of Perseus, but that wasn't the issue. I DID tick the EFS Clear. After booting back to normal, the imei wasn null/null and the /efs folder was wiped out. it was en empty folder with just 1-2 files in it...
latousakis said:
I was aware of Perseus, but that wasn't the issue. I DID tick the EFS Clear. After booting back to normal, the imei wasn null/null and the /efs folder was wiped out. it was en empty folder with just 1-2 files in it...
Click to expand...
Click to collapse
Thing is, the I9305 doesn't store IMEI in the EFS. Which is why I find this a little strange.
Rekoil said:
Thing is, the I9305 doesn't store IMEI in the EFS. Which is why I find this a little strange.
Click to expand...
Click to collapse
Yes, but the other strange thing is that instead of having a bunch of files, there were only 2 files in the /efs folder!
latousakis said:
Yes, but the other strange thing is that instead of having a bunch of files, there were only 2 files in the /efs folder!
Click to expand...
Click to collapse
So get yourself a donor EFS and substitute the MAC addresses for your own data, it's on the box isn't it?
Rekoil said:
So get yourself a donor EFS and substitute the MAC addresses for your own data, it's on the box isn't it?
Click to expand...
Click to collapse
I think that that'w what he's done!
Hello XDAs,
After reading that Forum with much enthusiasm for a few...well...years, i got my first question.
I hope you can help me with a big problem on my g800f: I can´t register in network.
When I search for network it pops up a few results, but if choose one to register, it says "Can´t register. Try again later."
I did a few hours of research and found out it might have something to do with my IMEI (Note: till that day i did nothing to my phone, except cf-autoroot. But never faced any problems!).
So I checked my IMEI and it wasnt the original, it was changed to 350695200123951. So I googled a bit and realised it might have something to do with the efs-partition. Googled for solutions.
Found out it might help to flash a Stock-Rom, one with three parts, via odin so i did it. Everything worked fine, but my IMEI still was the different one.
I was a bit irritated so i searched for that IMEI. And there are a few threads (some in russian and arabian), also owners of a g800f, which also reported this problem: They did nothing, but sudddenly the IMEI changed to this number. One author tells he received a myserious call from the ukraine after this happened. He didnt answer it. I am quite sure i also received that call- I didnt answer it either.
So i googled even mre: "How to restore a damaged efs-partition, without backup?" I came to one very outdated guide which wanted me to delete the efs (after saving it on externalSD) and do a few mysetrious actions...
Well, i just realised i cant fully delete the efs, its not possible and i also cant apply my backup from external sd. Anyone knowing a solution for this?
But, the most important, how can i bring my g800f back into mobile network?
Or just: How can i get away from that cursed IMEI?
Any Ideas?
P.S. If you got any questions regarding technical details of my phone(CSC, AP, Kernel, Modems), just ask. I´ll answer.
P.P.S I´m excusing for that horrible english. I googled the entire night and i´m german.
LukiRe said:
Hello XDAs,
After reading that Forum with much enthusiasm for a few...well...years, i got my first question.
I hope you can help me with a big problem on my g800f: I can´t register in network.
When I search for network it pops up a few results, but if choose one to register, it says "Can´t register. Try again later."
I did a few hours of research and found out it might have something to do with my IMEI (Note: till that day i did nothing to my phone, except cf-autoroot. But never faced any problems!).
So I checked my IMEI and it wasnt the original, it was changed to 350695200123951. So I googled a bit and realised it might have something to do with the efs-partition. Googled for solutions.
Found out it might help to flash a Stock-Rom, one with three parts, via odin so i did it. Everything worked fine, but my IMEI still was the different one.
I was a bit irritated so i searched for that IMEI. And there are a few threads (some in russian and arabian), also owners of a g800f, which also reported this problem: They did nothing, but sudddenly the IMEI changed to this number. One author tells he received a myserious call from the ukraine after this happened. He didnt answer it. I am quite sure i also received that call- I didnt answer it either.
So i googled even mre: "How to restore a damaged efs-partition, without backup?" I came to one very outdated guide which wanted me to delete the efs (after saving it on externalSD) and do a few mysetrious actions...
Well, i just realised i cant fully delete the efs, its not possible and i also cant apply my backup from external sd. Anyone knowing a solution for this?
But, the most important, how can i bring my g800f back into mobile network?
Or just: How can i get away from that cursed IMEI?
Any Ideas?
P.S. If you got any questions regarding technical details of my phone(CSC, AP, Kernel, Modems), just ask. I´ll answer.
P.P.S I´m excusing for that horrible english. I googled the entire night and i´m german.
Click to expand...
Click to collapse
I´ve just seen this problem being reported i a different thread. Guess the problem will be discussed there?
Hi All,
Did any one actually get a fix for this issue as I have exactly the same problem, my SM-G800F IMEI now also shows as - IMEI 350695200123951-01 which is for a blacklisted NOKIA 6310. If anyone can supply an absolute beginners guide for me as to how I can get my original Imei back that would be fantastic.
I am just a user of an android phone and have zilch experience of tinkering with them.
I have seen reference to things like Odin and flashing firmware and am quite happy to give it a go myself and learn
I will post this on a few other threads that list the same issue as I am desperate to get this fixed now as is a waste of a perfectly good phone !!
Cheers.
SM-G800F, can't register in network
Hello,
I have exactly the same problem. Since some month I got the message "can´t register in network". After checking all, I found that my SM-G800F IMEI has changed to a NOKIA 6300 IMEI.
If anyone knows a fix for this issue (set back to the orignal IMEI) , it would be great. All apps which I could find didn't work (XPOSED IMEI Changer Pro , Mobile Uncle Tools App, MTK Technikmodus... ), are not supporting S5mini.
I don't have a backup of the original system EFS file.
Would be great when one could help.
Regards
Chris
@S5miniChris somewhere in XDA I read that restoring the original stock (multiple part) firmware might or did help.
Gotta do it in Odin (recommended to use an older version like 3.09).
bmwdroid said:
@S5miniChris somewhere in XDA I read that restoring the original stock (multiple part) firmware might or did help.
Gotta do it in Odin (recommended to use an older version like 3.09).
Click to expand...
Click to collapse
Thanks for your reply.
I have installed the original stock firmware. But it did not change the IMEI. Available for my model is only the single file " G800FXXU1CRG3_G800FDBT1CRE1_G800FXXU1CRG3_HOME.tar.md5"
Multible file firmware I couldn't find.
A manual modification of the IMEI should be possible with " Best smart Tolls " e.g. : BSTPRO 4.03 . But for the software a dongle is requiered. To purchase this is for one time use too expensive for me
Regards
Chris
S5miniChris said:
Thanks for your reply.
I have installed the original stock firmware. But it did not change the IMEI. Available for my model is only the single file " G800FXXU1CRG3_G800FDBT1CRE1_G800FXXU1CRG3_HOME.tar.md5"
Multible file firmware I couldn't find.
A manual modification of the IMEI should be possible with " Best smart Tolls " e.g. : BSTPRO 4.03 . But for the software a dongle is requiered. To purchase this is for one time use too expensive for me
Regards
Chris
Click to expand...
Click to collapse
Where from did you get the stock?
Samfirm_reborn tool already tried?
https://github.com/ivanmeler/SamFirm_Reborn/releases
Checking "binary nature" or "factory mode" downloads a multiple part rom.
Edit:
Checked tool and it's working.
bmwdroid said:
Where from did you get the stock?
Samfirm_reborn tool already tried?
Checking "binary nature" or "factory mode" downloads a multiple part rom.
Edit:
Checked tool and it's working.
Click to expand...
Click to collapse
I flashed now also with " binary nature " firmware downloaded with SamFim. The IMEI is still the same, it hasn't changed to the orginal IMEI.
I really can't believe that a firmware update will flash the E2PROM where the IMEI is stored. Therfor the orginal IMEI must be stocked some where
in the phone and by flashing transfered to the E2PROM.
Regards
Symptoms
-No IMEI and no Baseband
Both say unknown.
-No signal bars
-No sim detected (with or without sim card)
-Top right gets very hot hot at times
-Battery drains pretty fast
What I've tried
-Downgrade to 4.4
- Different play-store apps
- Different modems and radios
- IMEI writers etc
-Custom roms
-Same as above with no avail
-Stock roms
-4.4 stock
-5.0 stock
-Youtube
-All types of things in videos except octoplus or whatever its called.
Please help
You have an n900a? If yes, where did you get the 4.4 and 5.0 stock ROMs? They were never released by AT&T.
audit13 said:
You have an n900a? If yes, where did you get the 4.4 and 5.0 stock ROMs? They were never released by AT&T.
Click to expand...
Click to collapse
I used custom roms off XDA hoping it would somehow recover missing IMEI
Is the phone an n900a?
Yes SM-n900a
Made in China
If the stock roms don't restore imei and baseband, the efs folder may be damaged. A completely stock flash may be done via JTAG.
audit13 said:
If the stock roms don't restore imei and baseband, the efs folder may be damaged. A completely stock flash may be done via JTAG.
Click to expand...
Click to collapse
JTAG
Long time since I've heard that.
Wish there was something I could do on my own. I was hoping maybe just a modem flash.
I'll standby for a few more days then if nothing I'll start looking into what they could do.
Where did you get the stock 4.4 and 5.0 ROMs?
Here on XDA
audit13 said:
Where did you get the stock 4.4 and 5.0 ROMs?
Click to expand...
Click to collapse
I believe they were both from the unified threads.
you can find 4.4.2 stock on here
then 4.4.4 and 5.0 were based on official release.
Update
Still have no clue whats wrong
Either something is really wrong on the software side of the phone beyond Odin (maybe JTAG)
OR
The Sim card slot on the phone is damaged.
The phone was given to me because the old owner was never ever to get it working and gave up.
I have the IMEI on a sticker located on the back.
(Yes I know discussion about changing IMEI etc is banned that's not what I'm here for)
My main question is what can be done if I don't have an EFS back up? Is the phone just a softbrick/parts
If so plan forward is just to use as a car dock lol.
I am in the same boat man. I do not know what to do, to get my imei back and baseband. i posted a thread as well similar to yours hopefully one of us gets a success story!!!!!!
jjta said:
Still have no clue whats wrong
Either something is really wrong on the software side of the phone beyond Odin (maybe JTAG)
OR
The Sim card slot on the phone is damaged.
The phone was given to me because the old owner was never ever to get it working and gave up.
I have the IMEI on a sticker located on the back.
(Yes I know discussion about changing IMEI etc is banned that's not what I'm here for)
My main question is what can be done if I don't have an EFS back up? Is the phone just a softbrick/parts
If so plan forward is just to use as a car dock lol.
Click to expand...
Click to collapse
Willcruz82 said:
I am in the same boat man. I do not know what to do, to get my imei back and baseband. i posted a thread as well similar to yours hopefully one of us gets a success story!!!!!!
Click to expand...
Click to collapse
The first step would be to try to find the proper basebands. Dont know where any of the firms are located. Im trying to dig them all up. And reupload them but may take some days. I am hoping to temperarelly revive this device as i have gotton one myself.
Best of luck
TheMadScientist said:
The first step would be to try to find the proper basebands. Dont know where any of the firms are located. Im trying to dig them all up. And reupload them but may take some days. I am hoping to temperarelly revive this device as i have gotton one myself.
Click to expand...
Click to collapse
My goal as of now is to find a t mobile 1 with a broken screen and switch boards. Done with the boot loader being locked.
I was instructed to do 1 of 2 things... 1st like you said buy a busted up phone with a good logic board and swap. OR 2- buy that same junk Note3 and copy the efs files and install them into your phone and switch the imei to yours. etc... I gave up on trying to revive mine so I no longer can tell you if it works or not but it seems to be the best 2 options friend... good luck let me know if you get it with one of the options....