Help ! Corrupted IMEI - Galaxy Note II Q&A, Help & Troubleshooting

Hi everyone,
6 days ago, I left my previous carrier (Bouygues Telecom) for a new one (SFR).
As I'm not used to buy my phones from a carrier, I did not think of simlockage... but I should have !
Because, last monday, when I installed my new SIM, I found out that the phone was locked.
I cannot join my previous carrier (access requires an eligible phone number, which I no longer have since I left them) and my new carrier cannot help me.
So, today, I tried to downgrade to an official 4.1.1, for trying the unlock via dial caller *#197328640# code method. But this failed. I installed GalaxSimlock app, and I found out that my IMEI wasn't the same: yesterday evening, it was like 354666... and now, it has become 004999...
I tried to restore my efs with TWRP recovery, but the IMEI remains the same... but I'm sure that IMEI was "good" when I backed it up (10 days ago). As long as I don't have any more solution, I would like to know those of you who faced the problem and, the solutions the found to fix the issue.
Thanx in advance.

If your imei is based on new rom, won't work old rom. At least you need newer baseband. Look my signature for multitool, that have option to update modem. (mg1)
Sent from my GT-N7100 using xda premium

Thank you for the quick reply.
Right now, I'm downloading the MutiTool_AromaV11 - Basic version.
I'll edit when further info.

Thank you very much ! That restored my IMEI !!!
Have a beer ?
Edit : cannot make a gift to you : Paypal says you're not allowed to receive gift...

Me too
Yan le Flan said:
Hi everyone,
6 days ago, I left my previous carrier (Bouygues Telecom) for a new one (SFR).
As I'm not used to buy my phones from a carrier, I did not think of simlockage... but I should have !
Because, last monday, when I installed my new SIM, I found out that the phone was locked.
I cannot join my previous carrier (access requires an eligible phone number, which I no longer have since I left them) and my new carrier cannot help me.
So, today, I tried to downgrade to an official 4.1.1, for trying the unlock via dial caller *#197328640# code method. But this failed. I installed GalaxSimlock app, and I found out that my IMEI wasn't the same: yesterday evening, it was like 354666... and now, it has become 004999...
I tried to restore my efs with TWRP recovery, but the IMEI remains the same... but I'm sure that IMEI was "good" when I backed it up (10 days ago). As long as I don't have any more solution, I would like to know those of you who faced the problem and, the solutions the found to fix the issue.
Thanx in advance.
Click to expand...
Click to collapse
My IMEI has changed too after a NAND restore. I had an efs backup to restore, but this made no difference. Now I can't register on any network.
I need help as well.
I used DrKetan's tool (which is excellent) but my phone now says I have no SIM card. I can't get the card out to clean it, etc, (It's a cut-down to mini-SIM original SIM card, usin a cutting tool from Amazon)
Now I've used the advanced multitool version. My IMEI is now restored and all is well in the world.
Steven

Good! Can we use multitool to r flash MG1 modem while on an old ROM? I wanna test this ROM with my original IMEI.
Envoyé depuis mon GT-N7100 avec Tapatalk 4

Yeah it's only way to restore imei on old rom. You can flash mg1 on old rom too and purpose to add it on multitool is only this.
Sent from my GT-N7100 using xda premium

@dr.ketan
Since this thread is about the same thing and since the OP has resolved his issue Ill mini-hijack it .. thanks
I have somehow killed my phone signal today while trying new roms.
I did a TWRP backup first of course including EFS.
At some point I could no longer get signal so I tried to restore my nandroid. The EFS fails to restore in TWRP.
I tried your tool to restore modem and while it completes it fails to restore my signal.
I wonder if you might have some other idea for me.
Thanks.

Give detail which rom you have flashed before nandroid
What rom you have right now (dial *#1234# and post result) after nandroid.
Sent from my GT-N7100 using xda premium

dr.ketan said:
Give detail which rom you have flashed before nandroid
What rom you have right now (dial *#1234# and post result) after nandroid.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
thankyou,
started with hellybean http://forum.xda-developers.com/showthread.php?t=2134990 then tried a couple of TW roms and finally this
http://forum.xda-developers.com/showthread.php?t=2119003
Now back to the hellybean nandroid which works fine apart from the efs restore which fails.
I completely wiped inbetween the TW and CM roms. I thought it was a good idea but I guess maybe not.
There is hardly anything in /efs just the imei folder which is empty and nv_data.bin and its .md5 as well as nv.log.
...
The twrp backup has the efs.ext4.win file at 5mb.
(i posted in the twrp thread too by the way, I hope thats ok)

Related

No Service after flashing latest Jedi X

I have a t889 and a original sim card which was cut to microsim form. I had no trouble getting service. I rooted successfully and still had service. At this point I performed nandroid backup and efs backup and attempted to flash jedi x following all steps provided in the thread (wipe data, cache, format system, wipe dalvik, fix permissions). As soon as I did this I lost service...it has bars but no voice calls and no 4g. My IMEI still shows however. I ve tried everything from stock factory restore through ODIN to restoring efs, flashing stock radios/kernels restoring nandroid still cant get service, defintely need some step by step advice on how to get back my service. I feel like I followed all the appropriate steps to flash the room.
Sent from my SGH-T889 using xda app-developers app
What recovery
Sent from my SGH-T889
I flashed CWM through ODIN cwm6-recovery-n7100-121014.tar
Any help would be appreciated is it because jedi has a built in modem? Just trying to figure it out
amullins said:
Any help would be appreciated is it because jedi has a built in modem? Just trying to figure it out
Click to expand...
Click to collapse
Have try your backups see if it works? Check imei if its 0 then your f$#%@. Samething happpen to me excepty imei is still there. Novchoice you have try to unrooted and flash ota stock see if it works.
Sent from my SGH-T889 using xda app-developers app
what?
culua said:
Have try your backups see if it works? Check imei if its 0 then your f$#%@. Samething happpen to me excepty imei is still there. Novchoice you have try to unrooted and flash ota stock see if it works.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
How does the imei dissappear and how the heck do we avoid that?! Thanks so much.
I was in same bout as you. I used my insurances claim and got a new note 2.
Sent from my SGH-T889 using xda app-developers app
So did all of you flashed this rom and this happened to you?? Im confused.
I've been flashing phones since
<------
2007 and this note 2 I am terrified of flashing. every other day is a new thread just like this. Nobody knows why, nobody has a defacto solution. The only remotely close info I've read that works is to unroot and flash to stock. Even that is a gamble. If that does not work, consider it a loss. Sell it on eBay as a bad IMEI phone
Hey guys just fyi to let you know what I found with this issue. Just giving my input.
Well it looks like my imei is populating but my note 2 no longer gets service. Im probably going to warranty it so I can get service again I spent all of my weekend trying to fix. I think this issue may be related to something within the modem or radio being flash incorrectly and somehow corrupting the efs files. I searched forums about efs corruption and I think maybe it has something to do with a nv_data file missing? Not sure if that applies for sgn2 but I couldnt find or maybe I dont know WHERE to find it in root explorer. Maybe if we compare a working sgn2's efs file with a NON WORKING sgn2's efs file maybe that would help? I followed the steps in the t889 root guide step by step... and then as soon as I flashed Jedi 9 through cwm recovery BAAM...service was gone.
I tried reflashing, I tried reflashing stock modem\kernel and reverting back to stock via odin but no go.I did notice it was able to connect to tmobile for one to two sec because it would actually sync the time and date after turning on for the first time. But never again after that. My Imei and bars are showing ..but when I make a call it says "not registered on network" and no 4g either. I think this may be because the rom had included a different radio not sure which one defintely wasnt the canada ver. Flashing this rom somehow made my phone stop receiving service...Does restoring efs backup a guaranteed fix the lost imei/ service issues? Can flashing using earlier version of odin cause an issue? I used 1.84. Everything passed successfully however. Just throwing ideas to help. I definitely want to try to avoid the issue when get my note 2 back from repair.
I know that efs and modems are fixable but I believe there is additional steps needed to fix the imei... not sure if there has been a solution on that but im looking everywhere... found that you can pull your batter, write down your imei, us nv tool to create a nv file and flash it to the phone but not sure how it works with GNII... I personally havent had any issues so am not going to test with my device but for those with no service you could atleast try and report back for others... go to galaxynote2root website and find the videos on flashing tmo to att and vice versa, youll find the programs needed, drivers, etc and basic instructions to what im suggesting
Sent from my SGH-T889 using xda app-developers app
I had this issue with a GS3. Had to do a warranty exchange. Ever since then I don't flash radios because that is when this can happen.
Sent from my SGH-T889 using xda premium
amullins said:
I have a t889 and a original sim card which was cut to microsim form. I had no trouble getting service. I rooted successfully and still had service. At this point I performed nandroid backup and efs backup and attempted to flash jedi x following all steps provided in the thread (wipe data, cache, format system, wipe dalvik, fix permissions). As soon as I did this I lost service...it has bars but no voice calls and no 4g. My IMEI still shows however. I ve tried everything from stock factory restore through ODIN to restoring efs, flashing stock radios/kernels restoring nandroid still cant get service, defintely need some step by step advice on how to get back my service. I feel like I followed all the appropriate steps to flash the room.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Does the phone even register to the network? Have you perhaps tried a different sim? I know you will be limited as to the carrier but try a friends sim just to be sure. I'm sure you could even take the phone to the dealer and they will test a different sim in the phone.
Has your IMEI possibly changed somehow, maybe it is acting like conflicting IP addresses on a network.
In Kies there is an emergency firmware recovery, perhaps that could help. I know I am probably not much help but 1 cent worth of help is better then no cents.
la1z24 said:
I've been flashing phones since
<------
2007 and this note 2 I am terrified of flashing. every other day is a new thread just like this. Nobody knows why, nobody has a defacto solution. The only remotely close info I've read that works is to unroot and flash to stock. Even that is a gamble. If that does not work, consider it a loss. Sell it on eBay as a bad IMEI phone
Click to expand...
Click to collapse
+1. As a newbie I was able to flash anything on my moto defy / ME525 without worrying a bit of bricking it, but I could only eagerly wait OTA update on my T889V.
I've actually been experience serverely degraded service since I flashed MyRom Revolution v2 last month, and not matter what I flash since service is questionable. I'm on the latest Jedi -XX from the 6th, and my 4g/3g service is 90% not there anymore, and i will flip to edge sometime for roaming on AT&T even or jsut be without service altogether... I've flashed the lastest modem from the Jan 26th, no help. New rom, ... no help. I'm ready to have my phone exchanged as well. Any ideas ?
Some people were having issues with the January 26th update flash back to ll4 and see if that doesnt improce things... also seen a thread refering to band 2 issues with one response refering to ATT towers... did you by chance ever download a ported ATT rom with a modem part of the install by chance?
Sent from my SGH-T889 using xda app-developers app

Nailed it!!!!!!!!! My 4g is back again

Last week, I did the most stupid thing on my note 2 (SGH-t889). I saw a rom that i liked for the n7100 and flashed on my 889v. Of course, rom works fine but no DATA OR VOICE :crying:crying:
So I flashed my phone with my previous rom and I had data again. All of a sudden, after installing all my apps, I lost the connection. My phone went completely crazy
i saw unknown baseband on settings / phone status; phone rebooted itself. I tried to flash a stock rom, or even flash the 889v modem on any rom and no luck; i was on a constant boot loop
I had to flash another modem from T-Mobile to get out of boot looping (MODEM: T889UVALL4_Modem-Jan_16_13-teshxx) but i couldn't get on any network even if I my phone could detect them (I'm on Videotron).
I've searched xda and other sitEs for solution on how to fix an almost empty esf folder. On a tmo modem my emei was 0 0 and on videotron modem it was null.
SOLUTION
My efs folder was almost empty; no nv_data.bin and those other files.
I went across this site
http://galaxynote2root.com/galaxy-note-2-tutorials/how-to-enable-t-mobile-3g4g-aws-bands-on-att-galaxy-note-2-sgh-i317/
It's a tutorial on how to enable aws on the AT&T note 2. It had just what i needed: a qcn file. Ive follwed the directions on the site; flashed the qcn file with the QPST software and rebooted the phone. My emei was a bunch of 0. No signal still but the battle wasn't loss.
On this thread
http://forum.xda-developers.com/showthread.php?t=1804117
I've used the EMEI NVitem generator to create en encrypted file of my EMEI
Put it on the the NV reader / writer, reboted the phone
And VOILA!!!!!!!!!!!!!
i got my signal back but with a tmo modem (MODEM: T889UVALL4_Modem-Jan_16_13-teshxx)
my 4g is back and my gps is working flawwless
Now, just to let you know, I'm not a developer and i take no credit for this. Even if this thread get approved or deleted, I just wanted to help other members like me who are stuck on the same situation (especially 889v owners). At the end.... MY PHONE IS BACK !!!!!!!!!!!!!!!!!!!!!!!
ohhhh! i allmost forgot....
I AM NOT RESPONSIBLE FOR YOUR PHONE
demension21 said:
Last week, I did the most stupid thing on my note 2 (SGH-t889). I saw a rom that i liked for the n7100 and flashed on my 889v. Of course, rom works fine but no DATA OR VOICE :crying:crying:
So I flashed my phone with my previous rom and I had data again. All of a sudden, after installing all my apps, I lost the connection. My phone went completely crazy
i saw unknown baseband on settings / phone status; phone rebooted itself. I tried to flash a stock rom, or even flash the 889v modem on any rom and no luck; i was on a constant boot loop
I had to flash another modem from T-Mobile to get out of boot looping (MODEM: T889UVALL4_Modem-Jan_16_13-teshxx) but i couldn't get on any network even if I my phone could detect them (I'm on Videotron).
I've searched xda and other sitEs for solution on how to fix an almost empty esf folder. On a tmo modem my emei was 0 0 and on videotron modem it was null.
SOLUTION
My esf folder was almost empty; no nv_data.bin and those other files.
I went across this site
http://galaxynote2root.com/galaxy-n...3g4g-aws-bands-on-att-galaxy-note-2-sgh-i317/
It's a tutorial on how to enable aws on the AT&T note 2. It had just what i needed: a qcn file. Ive follwed the directions on the site; flashed the qcn file with the QPST software and rebooted the phone. My emei was a bunch of 0. No signal still but the battle wasn't loss.
On this thread
http://forum.xda-developers.com/showthread.php?t=1804117
I've used the EMEI NVitem generator to create en encrypted file of my EMEI
Put it on the the NV reader / writer, reboted the phone
And VOILA!!!!!!!!!!!!!
i got my signal back but with a tmo modem (MODEM: T889UVALL4_Modem-Jan_16_13-teshxx)
my 4g is back and my gps is working flawwless
Now, just to let you know, I'm not a developer and i take no credit for this. Even if this thread get approved or deleted, I just wanted to help other members like me who are stuck on the same situation (especially 889v owners). At the end.... MY PHONE IS BACK !!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
MIKE BROWN FTW!!!!!!
Sent from my SGH-T889 using XDA Premium HD app
I can not download Download ATT_I317_AWSMOD_dumimei.qcn. I just get a blank screen in Chrome, IE and Safari. Can you post it or send me a dropbox link or something. Thanks
edit:
Never mind, never saw that kind of Captchaw before. I thought it was just an ad.
I keep getting a size difference error when I go to write the my imei
Did you generate a txt file with the emei generator?
Sent from my SGH-T889 using xda premium
demension21 said:
Did you generate a txt file with the emei generator?
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Problem was I used serveral tools to try to fix this and they did not not requirer the check digit at the end of the imei. The CDWS imei converter requires it. I'm back up and running !!!
gedster314 said:
Problem was I used serveral tools to try to fix this and they did not not requirer the check digit at the end of the imei. The CDWS imei converter requires it. I'm back up and running !!!
Click to expand...
Click to collapse
so you got data back...if so on what baseband?
demension21 said:
Did you generate a txt file with the emei generator?
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Id really love to talk about your process, as I have used QPST(UPST), CDMA Workshop, etc through varios Android, Blackberry, Palm, etc devices and am trying to confirm (repair steps) for posting... please PM me so I can test
Sent from my SGH-T889 using xda app-developers app
I say (repair steps), I mean restoring from backup... have all the various backups and until my GNII and N4 are picked up im not fixing what isnt broke
Sent from my SGH-T889 using xda app-developers app
demension21 said:
so you got data back...if so on what baseband?
Click to expand...
Click to collapse
Here you go.
Wow. I followed your steps to the letter and it worked, thank you so much!!
Have you flashed back to a VTR modem or would that mess everything up? Thanks again for your help.
From past experience flashing the videotron modem would bring me back to boot loop, wouldnt lose imei or signal but would start then after 30secs reboot.. Im stuck with tmo modem. Works fine but signal seems a little weaker.
i have canadian note2 t889v that i got from craigs the other day. everything seemed fine, didnt have sim to try for mobilicity that im on (aws band), he said he used it with rogers fine
I put the sim card, went to search networks but my provider was not listed there. So I rooted the phone , loaded twrp, flashed prerooted factory rom for t889v ( from mrrobins) , no network, than i flashed original factory rom, still no luck, than i flashed t889v modem and still the same.
My imei is present, and matches one on back of the phone. My efs folder is there and is populated (dont know if anything is missing from there)
I dont have backup of efs or imei. What are the chances it is corrupted ? Does anyone have any suggestion, and should i try this method to try to fix it ?
You may have to put your apn settings manually for your carrier. I would try that to start.
Sent from my ASUS Transformer Pad TF700T using xda premium
Already tryed
Sent from my HTC DESIRE HD using xda app-developers app
Also my emei number is correct in abaut.
What are the files I need to have in efs how can I know if my efs is corrupt ?
Sent from my SGH-T889V using xda app-developers app
Have you check the *#2263# menu to make sure it is on the correct band, also in network setting you can switch to gsm, wcdma, so on. As for imei as far as I know if it were corrupt your imei would be bad. Is it possible the phone has been blacklisted?
That code dont work in stock dialer. And mobilicity dont block imei #
Sent from my SGH-T889V using xda app-developers app
pearse said:
Wow. I followed your steps to the letter and it worked, thank you so much!!
Have you flashed back to a VTR modem or would that mess everything up? Thanks again for your help.
Click to expand...
Click to collapse
yes I've tried flashing the 889v modem and I was back in a bootloop again
man i wiish that I could have an original 889v nv data files; i could find a way to midify the emei and flash it on my phone
knnrsk said:
i have canadian note2 t889v that i got from craigs the other day. everything seemed fine, didnt have sim to try for mobilicity that im on (aws band), he said he used it with rogers fine
I put the sim card, went to search networks but my provider was not listed there. So I rooted the phone , loaded twrp, flashed prerooted factory rom for t889v ( from mrrobins) , no network, than i flashed original factory rom, still no luck, than i flashed t889v modem and still the same.
My imei is present, and matches one on back of the phone. My efs folder is there and is populated (dont know if anything is missing from there)
I dont have backup of efs or imei. What are the chances it is corrupted ? Does anyone have any suggestion, and should i try this method to try to fix it ?
Click to expand...
Click to collapse
you mentioned that the phone was working on rogers before you had it?
did you try any othe sim card... form rogers or mobile city?
try frash custom rom and 889v modem with it?
if that doesnt work try the method in the op

[Q] IMEI and Baseband Missing - GT-N7100

Hi,
I'm sure this has been covered many times but I'm finding little information that relates to the GT-N7100 or anything that I can actually get to work...
So, I'm new to flashing Android phones. This is my first Android device. I've messed around with ROMs on old Windows Mobile 6.1 and 6.5 devices before but not Android.
The problem I'm basically having is that my GT-N7100 no longer recognises quite a few system details, mainly the baseband version and the IMEI.
I'm not 100% sure where the problem first occured. What I did last night was:
Installed ODIN for Windows and flashed a root/recovery ROM to the device to root it.
Checked SuperSU was there, check. All good.
Tried to boot into CWM Recovery to flash a MIUI ROM. I got the Samsung Galaxy Note II GT-N7100 screen appear, followed by flickering like an out of tune TV.
After some Googling, found that I'd somehow got the wrong ROM for the GT-N7100, followed by a link to the correct one... so I downloaded that, flashed it, all good. I can now bootinto CWM Recovery.
Did a backup through CWM. Flashed the ROM, set it all up, then noticed I only had "Emergency Calls Only". Checked a few settings and everything looked OK. I did a bit of Googling and it pointed to checking the IMEI number.
Checked my IMEI and it came up as 004999010640000 which didn't look right to me. Tried pressing a few random buttons, nothing. Checked my box and that was definitely not right as my IMEI is 356000053********.
In a bit of confusion, went back into CWM Recovery and did a restore. This seemed to put the stock but rooted ROM back onto the device, clearing MIUI. Now I just have a circle with a line through it where the signal strength would normally be.
About Device says IMEI is "Unknown". Dialling *#06# brings up "null / null".
Now, I'm not sure where the problem occured, but I do remember seeing the circle with a line through it on the stock ROM before I flashed MIUI... so I've got a feeling it was the root/recovery that killed it.
I thought it did, but it turns out that CWM Recovery's backup does not backup the /efs folder, and even if it did, I've got a feeling it was fudged before I even got to that stage...
I have tried taking a copy of the existing /efs folder and pasting it onto my external SD card. I have then deleted the /efs folder, rebooted the device so that it regenerated the folder, deleted the nv_data.bin and nv_data.bin.md5, copied the .nv_data.bak and .nv_data.bak.md5 from the backed up copy and renamed them to nv_data.bin and nv_data.bin.md5 to no avail.
One guide suggested there may be a failed checksum error in the nv.log file, but there isn't a line that says anything about an md5 checkum error.
I tried one this morning that talked about using a hex editor to restore the information. I've done this again to no avail. I could see in the file that model number was correct when editing it, but no sign of an IMEI... but it was a large file...
I've tried a few other random bits and pieces that I can't remember, as to be honest, it was getting late and I was getting tired.
This is the information that my About Device screen shows:
Model Number: GT-N7100
Android Version: 4.1.2
Baseband Version: Unknown
Kernel Version: 3.0.31 -1071214 [email protected] #1 SMP PREEMPT Fri May 31 11:14:19 KST 2013
Build Number: JZO54K.N710XXDME6
Network: Unknown
Signal strength: 0dBm 99 asu
Mobile network type: Unknown
Service state: Out of service
Roaming: Not roaming
Mobile network state: Disconnected
My phone number: Unknown
IMEI: Unknown
IMEI SV: Unknown
The only thing I haven't really tried so far is just flashing a stock ROM to it. Not sure where to get this from to be honest either.
Any ideas what I can do? I have noticed while typing this that it doesn't seem to be registered a SIM card being inserted? It was last night... I did try booting with no SIM card and reinstalling the SIM, but it doesn't seem to pick it up now?
Any help would be great.
Cheers,
Mike.
Little bit of an update. I have some progress.
I flashed back to the stock ROM and I now have a baseband version of N7100XXALIH, which is great. We're getting somewhere... but I still have no IMEI. This is the current report from my About Device screen:
Model number: GT-N7100
Android version: 4.1.1
Baseband version: N7100XXALIH
Kernel version: 3.0.31 -259982 [email protected] #1 SMP PREEMPT Tue Oct 2 02:04:58 KST 2012
Build number: JRO03C.N7100XXALJ1
Network: O2 - UK
Signal strength: -95 dBm 9asu
Mobile network type: GPRS
Service state: Out of service
Roaming: Not roaming
Mobile network state: Disconnected
My phone number: Unknown
ERI Version: Not available
IMEI: 004999010640000
IMEI SV: 01
Serial Number: 00000000000000
Device status: Normal
Your imei is generic, if you have efs backup restore it
Otherwise flash stock rom +wipe if it doesn't solve then better send to service station.
Sent from my GT-N7100 using xda premium
Shame, I thought that might be the case.
I've just done a stock ROM flash and wipe which resolved the baseband issue... but it hasn't restored the IMEI. Unfortunately the backup I took didn't include the EFS when I thought it did so I have no backup to restore.
I'm just fiddling with a few things but not holding my hopes up. I might try a few things and if it doesn't work by the weekend, then I'll just unroot, try to clear the flash history and take it into CPW and say it's broken and I don't know why... see how it goes...
Not got much further with this to be honest. I've asked a friend who has the same device if he can send me a copy of his EFS folder that I could have a dig around with to see if I can find anything, but waiting on that at the moment... He sent me his nv_data.bin and nv_data.bin.md5, but when I put these in the EFS folder and rebooted (with no SIM for safety), it still pulls out the dummy IMEI number...
Someone has suggested to me to search around on here for the standard PIT file, to flash that and then flash a stock pre-rooted ROM which should sort it all out. I've not heard of this before, but from a quick search I've found that PIT is Partition Information Table... which suggests this is going to completely re-build the partition table and then flash a new device. Is this advisable, and do you think it could resolve my issue?
I've managed to install TriangleAway and reset the custom flash count to 0, so it no longer reports as custom firmware... I may just take it to CPW tomorrow and see what they say before I even think about messing with this PIT stuff anymore.
Unfortunately, EFS is a little more complicated than a folder with a few files, it's a dedicated partition which generally can't be restored without a backup.
Using somebody else's folder won't work, and actually using another imei is probably illegal since every phone is supposed to have one unique imei.
I've read that people some times miraculously get back their imei after flashing stock rom, but since you've tried it, I don't think there's realistically much to do besides sending to service.
Sent from my GT-N7100 using Tapatalk 2
nimraynn said:
I've managed to install TriangleAway and reset the custom flash count to 0, so it no longer reports as custom firmware... I may just take it to CPW tomorrow and see what they say before I even think about messing with this PIT stuff anymore.
Click to expand...
Click to collapse
I had faced the same issue and was able to get the IMEI back. Even I did not have the backup of the EFS folder. Go through the thread.
http://forum.xda-developers.com/showthread.php?t=2331833
Try to find a stock rom which has all three - CSC, Modem and PDA available. Install it with PIT from ODIN. (I installed 4.1.1) Once installation is complete, you should be able to see you IMEI number correctly. Root the device and take the back up of the EFS Folder and install any rom that you need. Hope this helps.
This is illogical
Flashing 3 files have no more role than flashing stock rom +wipe
On The contrary flashing 4.1.1 may brick your device.
Sent from my GT-N7100 using xda premium
what about Kies emergency recovery ? did u tried it ?
adytum said:
Unfortunately, EFS is a little more complicated than a folder with a few files, it's a dedicated partition which generally can't be restored without a backup.
Using somebody else's folder won't work, and actually using another imei is probably illegal since every phone is supposed to have one unique imei.
I've read that people some times miraculously get back their imei after flashing stock rom, but since you've tried it, I don't think there's realistically much to do besides sending to service.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
I wasn't planning on actually using someone else's folder, but more using it to test if that was firstly 100% definitely my issue, and secondly to see if I could dig around to try and work out what might actually be wrong with the /efs directory. I have absolutely no intention of using someone else's IMEI, which is the reason why I took the SIM card out before booting it up with the new nv_data.bin.
kailashnj said:
I had faced the same issue and was able to get the IMEI back. Even I did not have the backup of the EFS folder. Go through the thread.
http://forum.xda-developers.com/showthread.php?t=2331833
Try to find a stock rom which has all three - CSC, Modem and PDA available. Install it with PIT from ODIN. (I installed 4.1.1) Once installation is complete, you should be able to see you IMEI number correctly. Root the device and take the back up of the EFS Folder and install any rom that you need. Hope this helps.
Click to expand...
Click to collapse
I'll take a look and see, but I've tried a stock ROM already and it's not worked.
dr.ketan said:
This is illogical
Flashing 3 files have no more role than flashing stock rom +wipe
On The contrary flashing 4.1.1 may brick your device.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Why would flashing 4.1.1 brick the device? I used a stock ROM to flash back to and according to About Device, I'm currently running 4.1.1?
yahyoh said:
what about Kies emergency recovery ? did u tried it ?
Click to expand...
Click to collapse
I haven't, I'll take a look and see.
nimraynn said:
Why would flashing 4.1.1 brick the device? I used a stock ROM to flash back to and according to About Device, I'm currently running 4.1.1?
Click to expand...
Click to collapse
Just search xda 'sds' or sudden death, you will find answer.
Sent from my GT-N7100 using xda premium
yahyoh said:
what about Kies emergency recovery ? did u tried it ?
Click to expand...
Click to collapse
Thank you so much for this suggestion! I tried it, but unfortunately Emergency Recovery wouldn't detect that my device needed it. I guess it technically didn't as the OS was working, just didn't have a working IMEI...
However, it did keep popping up telling me there was an update for the device, and everything had a different version number. PDA, PHONE and CSC all had completely different versions to what was flashed... so I thought, what harm can it do? Hit update, let it do it's thing and hey presto! I have a working device again! :good:
I'm doing my happy dance. Saved me a trip to CPW tomorrow! :fingers-crossed:
dr.ketan said:
Just search xda 'sds' or sudden death, you will find answer.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Sounds nasty!
nimraynn said:
Thank you so much for this suggestion! I tried it, but unfortunately Emergency Recovery wouldn't detect that my device needed it. I guess it technically didn't as the OS was working, just didn't have a working IMEI...
However, it did keep popping up telling me there was an update for the device, and everything had a different version number. PDA, PHONE and CSC all had completely different versions to what was flashed... so I thought, what harm can it do? Hit update, let it do it's thing and hey presto! I have a working device again! :good:
I'm doing my happy dance. Saved me a trip to CPW tomorrow! :fingers-crossed:
Sounds nasty!
Click to expand...
Click to collapse
u can try firmware upgrade and initialisation
dr.ketan said:
Your imei is generic, if you have efs backup restore it
Otherwise flash stock rom +wipe if it doesn't solve then better send to service station.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
is it possible if you backup your efs folder and send it over to us to have a correct one to restore?
No.
It's different for each device. To flash others is illegal and all the devices have same imei will gets banned.
So never try to share same imei.
Sent from my GT-N7100 using xda premium
Hey,
I also had same problem with my mobile.. while changing the firmware i lost my IMEI and got no Baseband version.. How can i fix it?
nimraynn said:
Hi,
I'm sure this has been covered many times but I'm finding little information that relates to the GT-N7100 or anything that I can actually get to work...
So, I'm new to flashing Android phones. This is my first Android device. I've messed around with ROMs on old Windows Mobile 6.1 and 6.5 devices before but not Android.
The problem I'm basically having is that my GT-N7100 no longer recognises quite a few system details, mainly the baseband version and the IMEI.
I'm not 100% sure where the problem first occured. What I did last night was:
Installed ODIN for Windows and flashed a root/recovery ROM to the device to root it.
Checked SuperSU was there, check. All good.
Tried to boot into CWM Recovery to flash a MIUI ROM. I got the Samsung Galaxy Note II GT-N7100 screen appear, followed by flickering like an out of tune TV.
After some Googling, found that I'd somehow got the wrong ROM for the GT-N7100, followed by a link to the correct one... so I downloaded that, flashed it, all good. I can now bootinto CWM Recovery.
Did a backup through CWM. Flashed the ROM, set it all up, then noticed I only had "Emergency Calls Only". Checked a few settings and everything looked OK. I did a bit of Googling and it pointed to checking the IMEI number.
Checked my IMEI and it came up as 004999010640000 which didn't look right to me. Tried pressing a few random buttons, nothing. Checked my box and that was definitely not right as my IMEI is 356000053********.
In a bit of confusion, went back into CWM Recovery and did a restore. This seemed to put the stock but rooted ROM back onto the device, clearing MIUI. Now I just have a circle with a line through it where the signal strength would normally be.
About Device says IMEI is "Unknown". Dialling *#06# brings up "null / null".
Now, I'm not sure where the problem occured, but I do remember seeing the circle with a line through it on the stock ROM before I flashed MIUI... so I've got a feeling it was the root/recovery that killed it.
I thought it did, but it turns out that CWM Recovery's backup does not backup the /efs folder, and even if it did, I've got a feeling it was fudged before I even got to that stage...
I have tried taking a copy of the existing /efs folder and pasting it onto my external SD card. I have then deleted the /efs folder, rebooted the device so that it regenerated the folder, deleted the nv_data.bin and nv_data.bin.md5, copied the .nv_data.bak and .nv_data.bak.md5 from the backed up copy and renamed them to nv_data.bin and nv_data.bin.md5 to no avail.
One guide suggested there may be a failed checksum error in the nv.log file, but there isn't a line that says anything about an md5 checkum error.
I tried one this morning that talked about using a hex editor to restore the information. I've done this again to no avail. I could see in the file that model number was correct when editing it, but no sign of an IMEI... but it was a large file...
I've tried a few other random bits and pieces that I can't remember, as to be honest, it was getting late and I was getting tired.
This is the information that my About Device screen shows:
Model Number: GT-N7100
Android Version: 4.1.2
Baseband Version: Unknown
Kernel Version: 3.0.31 -1071214 [email protected] #1 SMP PREEMPT Fri May 31 11:14:19 KST 2013
Build Number: JZO54K.N710XXDME6
Network: Unknown
Signal strength: 0dBm 99 asu
Mobile network type: Unknown
Service state: Out of service
Roaming: Not roaming
Mobile network state: Disconnected
My phone number: Unknown
IMEI: Unknown
IMEI SV: Unknown
The only thing I haven't really tried so far is just flashing a stock ROM to it. Not sure where to get this from to be honest either.
Any ideas what I can do? I have noticed while typing this that it doesn't seem to be registered a SIM card being inserted? It was last night... I did try booting with no SIM card and reinstalling the SIM, but it doesn't seem to pick it up now?
Any help would be great.
Cheers,
Mike.
Click to expand...
Click to collapse
anupjoshi said:
Hey,
I also had same problem with my mobile.. while changing the firmware i lost my IMEI and got no Baseband version.. How can i fix it?
Click to expand...
Click to collapse
dr ketan There are solution with Last firmware with new efs2?
with 4.1.2 all work but if upgrade To 4.3 leaked, i have imei ok but Not network registered.. prese help me. thanks
Inviato dal mio GT-N7100 con Tapatalk
vingar said:
dr ketan There are solution with Last firmware with new efs2?
with 4.1.2 all work but if upgrade To 4.3 leaked, i have imei ok but Not network registered.. prese help me. thanks
Inviato dal mio GT-N7100 con Tapatalk
Click to expand...
Click to collapse
mine after upgrade to 4.3 same happened as DMG1 custom rom, imei getting 00499xxxx and cannot connect to network..
i'm really really frustated... does it seems that the modem chip is too old and cannot accept any new released modem ?
downgrade modem in 4.3 impossible, getting imei null.. flash kernel in 4.3 brings me boot loop and vibrate.. and no one cannot give me better solution..
i googling everywhere and found some method on how to repair imei using uart usb cable.. is it possible ?
Mobile network not available
Hi Dr.Ketan and everyone else on here.
I've been following/installing Roms and posts on XDA since the original HTC desire days before moving onto an S2 and then the Note 2, strangely enough is my first post. I have been following the progress of this rom since early October and finally decided to give it a try with the more matured version 3.
The Rom worked well and I can see this pretty much being ready as new daily Rom (ProBam is my current daily). There is one problem though that I have spent half the day trying to figure it out, I thought someone here might be able to give me advice. I did a backup in Philz then and full wipe before installing the Rom.
After the Rom loaded everything that I tried seemed to work quite well, apps in general were fluid and from what I could see things were as they should be. When trying to text or make calls I ran into “Mobile network not available” problems. When installing the rom I did select the MI6 modem. So far I have tried.
1. Checking the sim card (testing it in another phone)
2. Contacting my cellular provider (Cell C in South Africa) to make sure they didn’t block me for any reason (which they didn’t).
3. I went into network settings to manually select my network (it wont register to Cell C).
4. I tried restoring Probam again which works but now get “Mobile network not available" problems on that Rom, the same issue on todays nightly Cyanogen 10.2 which does indicate that this is a problem with other Roms now.
I did some hunting on Google and see that others have had similar problems with Samsing phones where their EFS folder gets corrupted and IMEI number becomes 0000. In my case it looks like my IMEI number is still there and when I checked my Philz backup I learnt today that a standard Philz backup doesn’t by default backup the EFS folder (just my luck). Short of downloading a 1 gig stock rom using crappy South Africa internet and flashing it with Odin might there maybe be a quicker way that I have overlooked?
Beyond this thanks for a really great Rom, I am curious what would cause this problem with the V3 Rom so that no one else is affected with this, I have flashed other Roms over the years and not had this one yet :>
Thanks!!
Emergency Calls Only
dr.ketan said:
Your imei is generic, if you have efs backup restore it
Otherwise flash stock rom +wipe if it doesn't solve then better send to service station.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Model number: GT-N7100
Android version: 4.1.1
Baseband version: N7100XXALIH
Kernel version: 3.0.31 -199846 [email protected] #1 SMP PREEMPT Thu Sep 20 03:30:33 KST 2012
Build number: JRO03C.N7100XXALJ1
Network: O2 - UK
Signal strength: -95 dBm 9asu
Mobile network type: GPRS
Service state: Out of service
Roaming: Not roaming
Mobile network state: Disconnected
My phone number: Unknown
ERI Version: Not available
IMEI: 3546.... GOOD
IMEI SV: 01
Serial Number: R31... GOOD
Device status: Normal
After restoring EFS my Imei back but I am still stuck on emergency calls only
Please help me Ketan Sir

[Q] Trouble with network connectivity probably caused by EFS???

Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.
What comes to my mind at first that something wrong with your sim card but if you insist that everything is ok with your card so I don't know what to suggest to you. Is it not related with your Omega ROM?
Sent from my GT-N7100 using xda premium
artorelis said:
What comes to my mind at first that something wrong with your sim card but if you insist that everything is ok with your card so I don't know what to suggest to you. Is it not related with your Omega ROM?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Ya, I was asking this question on the Omega forum and I am waiting for the right response.
Sent from my GT-N7100 using xda premium
It does seem to be Efs related. Did u downgrade from the latest firmware ? Check these links-
http://forum.xda-developers.com/showthread.php?t=2332913
http://forum.xda-developers.com/showthread.php?t=2331833
Sent from my GT-N7100 using xda app-developers app
joshphilips said:
It does seem to be Efs related. Did u downgrade from the latest firmware ? Check these links-
http://forum.xda-developers.com/showthread.php?t=2332913
http://forum.xda-developers.com/showthread.php?t=2331833
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Yes, I did downgrade from v17 back to 16 since something went wrong with Poweramp but I forgot that if I selected for the efs backup or not since I (stupidly) didn't think that efs is important...:banghead:
Sent from my GT-N7100 using xda premium
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
If the answer to this is yes: Then you should contact your carrier as it sounds like your IMEI might have been blacklisted (often if a phone is reported stolen)
If the answer is no: Then you need to fix your IMEI so it matches as it should. This would usually be done by restoring your EFS backup. I suggest restoring a totally stock Firmware if they don't match and you don't have an EFS backup. But you should have one somewhere, surely? Every tutorial out there tells you to back it up...
Good luck.
muppetmania said:
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
If the answer to this is yes: Then you should contact your carrier as it sounds like your IMEI might have been blacklisted (often if a phone is reported stolen)
If the answer is no: Then you need to fix your IMEI so it matches as it should. This would usually be done by restoring your EFS backup. I suggest restoring a totally stock Firmware if they don't match and you don't have an EFS backup. But you should have one somewhere, surely? Every tutorial out there tells you to back it up...
Good luck.
Click to expand...
Click to collapse
Thanks for replying, I should have a backup, but it probably be the wrong one. Anyway I will go for a full stock restore since I have the firmware with me now.
Sent from my GT-N7100 using xda premium
muppetmania said:
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
Good luck.
Click to expand...
Click to collapse
Do you mean the one in the About Device ==> Status? In fact, the IMEI from the dialing does match the one in About Device ==> Status. However, I don't get your instruction since if in the case where IMEI from the setting matches the one on the dialer means that my phone is reported to be stolen, then why I have to make the IMEI in the setting and the one shown in the dialer the same?
Dan Law 001 said:
Do you mean the one in the About Device ==> Status? In fact, the IMEI from the dialing does match the one in About Device ==> Status. However, I don't get your instruction since if in the case where IMEI from the setting matches the one on the dialer means that my phone is reported to be stolen, then why I have to make the IMEI in the setting and the one shown in the dialer the same?
Click to expand...
Click to collapse
No, when I say "The one on the sticker" I, strangely enough, mean the one on the sticker.
Take off your battery and the phone will have a sticker/label with the IMEI on it. Verify that number matches.
muppetmania said:
No, when I say "The one on the sticker" I, strangely enough, mean the one on the sticker.
Take off your battery and the phone will have a sticker/label with the IMEI on it. Verify that number matches.
Click to expand...
Click to collapse
Thanks for your clearification No, it wasn't.:good: Then, I need to flash a stock firmware via Odin, right? In addition, when they say stock firmware, they mean the one that is on sammobile.com, right? In other words, if I have a Hong Kong version of GT-N7100, the file from this link (http://www.sammobile.com/firmwares/3/?download=15126) would be the correct one, isn't?
Dan Law 001 said:
Thanks for your clearification No, it wasn't.:good: Then, I need to flash a stock firmware via Odin, right? In addition, when they say stock firmware, they mean the one that is on sammobile.com, right? In other words, if I have a Hong Kong version of GT-N7100, the file from this link (http://www.sammobile.com/firmwares/3/?download=15126) would be the correct one, isn't?
Click to expand...
Click to collapse
That's correct, yes. It doesn't actually matter which N7100 image you flash, but if you have a Hong Kong version you might as well flash that image. Just make sure you don't have a N7105 (the LTE/Dual Carrier version) - flashing A N7105 to an N7100 (or the other way around) is a recipe for major disaster.
Flashing the image should fix the problem, but it also depends. If the EFS is really totally corrupt, it won't help, you need to have that EFS backup or take the phone to someone who can repair it for you. There are specialist tools to repair EFS, but they cost quite a bit of money. Most reliable phone unlocking places should have something that can help you.
Anyway, hopefully restoring to stock will fix the problem.
Good luck.
muppetmania said:
That's correct, yes. It doesn't actually matter which N7100 image you flash, but if you have a Hong Kong version you might as well flash that image. Just make sure you don't have a N7105 (the LTE/Dual Carrier version) - flashing A N7105 to an N7100 (or the other way around) is a recipe for major disaster.
Flashing the image should fix the problem, but it also depends. If the EFS is really totally corrupt, it won't help, you need to have that EFS backup or take the phone to someone who can repair it for you. There are specialist tools to repair EFS, but they cost quite a bit of money. Most reliable phone unlocking places should have something that can help you.
Anyway, hopefully restoring to stock will fix the problem.
Good luck.
Click to expand...
Click to collapse
Thanks for information, but how do I know that if the EFS is "totally" corrupt, "partially" corrupt, or not corrupt at all? In fact, I never touch the EFS in the root. Also, as I am not quite sure that if I have any previous EFS(S) backup or not, so, if possible, where does the backup(s) most likely to be found?
If you haven't taken an EFS backup yourself, then you won't have any.
I don't know the difference between corruption levels either, all I know is I've read a number of forum posts where someone has reflashed stock and their EFS data (i.e. the right IMEI number) is back. So I'd consider that to be a partial corruption. Others have flashed back to stock and it's still a bogus IMEI
Basically, flash back to stock. If it doesn't work, you'll have to take it in for repair.
UPDATE: Please read on - this information is incorrect - it is possible to recover with the correct modem flashed.
Before doing the flash with Odin, do I have to perform a factory reset? Since all the app data and homescreen layout remains the same after the reboot and the IMEI is also the same as before. And is it normal that my device got unrooted after flashing the stock firmware?
NOTE: The information from me in this post below is wrong
Dan Law 001 said:
Before doing the flash with Odin, do I have to perform a factory reset? Since all the app data and homescreen layout remains the same after the reboot and the IMEI is also the same as before. And is it normal that my device got unrooted after flashing the stock firmware?
Click to expand...
Click to collapse
It's normal your device got unrooted, yes. If your IMEI is still the same after ODIN and stock flash, then you have major issues (sorry!)
Doing a factory reset etc won't help. Your /efs partition is either gone or corrupt.
What IMEI does *#06# show?
muppetmania said:
it's normal your device got unrooted, yes. If your imei is still the same after odin and stock flash, then you have major issues (sorry!)
doing a factory reset etc won't help. Your /efs partition is either gone or corrupt.
What imei does *#06# show?
Click to expand...
Click to collapse
004999010640000 / 01
Dan Law 001 said:
004999010640000 / 01
Click to expand...
Click to collapse
Type 004999010640000 into Google...
Sorry man. Good luck getting it fixed.
just flash ME4 modem everything will be alright
bhasg1007 said:
just flash ME4 modem everything will be alright
Click to expand...
Click to collapse
Interesting to know - why does that work? (I don't doubt you, I just like to know why things work)
Just go through this thread http://forum.xda-developers.com/showthread.php?t=2333216
Even i had the same problem no network no imei nothing after downgrading so i just changed the modem and now everything is fine as it should be

N7105 factory mode

Hi guys, i seriously need help here. Please refer to attached screenshot.
I came here after flashing sokp 4.2.2 rom, and it prompted me an error saying encryption was unsuccessful. After which, i wasnt able to use my phone since then.
I tried to flash stock rom, and I end up with this. Please dont tell me to search the forums because Ive been to them countless times. I suppose this is a efs issue, because baseband and imei are unknown and I do not have a backup for it. Tried with the writing tool for imei, doesnt work as well.
Pls ask me for any info u might need/i missed out to help with this issue.
I think it's in the efs folder, you have to use a root browser and edit factory mode to off instead of on. It's been a long time since I saw factory mode so I'm not 100%
Sent from my GT-N7105 using Tapatalk
sawdoctor said:
I think it's in the efs folder, you have to use a root browser and edit factory mode to off instead of on. It's been a long time since I saw factory mode so I'm not 100%
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply. But even if I off factory mode, will the baseband and imei be unknown?
I'm not sure but if it doesn't the 2 things that might be worth trying are, emergency firmware recovery with kies or mskips toolkit has a rescue package but I think you have to go to skipsoft.net now as the thread was closed
Sent from my GT-N7105 using Tapatalk
It's current value is "OFF"...u have to write "ON"...i know it sounds weird but that is the value. Amd if u don't have any previous back up of EFS then there's nothing u can do at home to bring it back. Same thing happened to mine and i got it repaired from a local shop for cheap...they used z3x box...the problem is my IMEI is correct and network works fine...but everytime i flash a ROM i have to take it to the shop and get the modem patched or else it doesn't connect to network. So go to Samsung service centre and get it fixed by them...they'll charge u more but their fix is permanent.
Sent from my GT-N7100 using XDA Free mobile app
Alright, it seems like i have a backup of the efs, bt the nv_data.bin file is not included, and i read on other threads that this file is responsible for the imei and all? This backup is dated in aug2013, but it doesnt help in restoring my phone because the efs pro software doesnt see this as a backup file. Im actually looking for one of the thread that actually taught how to edit the nv_data.bin file, but no luck till date.
This thread might help
http://forum.xda-developers.com/showthread.php?t=1946915
[WARNING! + GUIDE] Backup and Restore IMEI / NV Data Procedure for GT-I9305. There is another post in this thread where they flashed the param.bin file
Check out the last post in this thread
http://forum.xda-developers.com/showthread.php?t=2724169
[Q]Null Imei, Baseband Unknown N7105
Sent from my GT-N7105 using Tapatalk
is it safe to flash the file that is intended for i9300? i dare not do that in case it doesnt work coz is different models.
ok my phone's all fixed up now. If anyone is interested to know, samsung kies original firmware helped.

Categories

Resources