please help for anyone who knows baseband fix not in the know, I wear GT-I9300T Australia Vodafone and running Android JB.4.3 initially imei null and baseband not in the know then I tried to flash back the official firmware using odin, not beehasil then I tried repair using octoplus without box, Z3X without box, other flash modem using TWRP recovery, still fail but after I install Xposed - Imei changger - I can write my Imei into my device but my baseband still unknown can not connect to the network, is there any who can give me a hint? I was getting frustrated, for hours I spent time in front of the computer looking for a reference but have not encountered an unknown Baseband fix, but I do not want to give up so easily considering I have to save long enough to buy the Samsung GT I9300T first. Thank you and sorry if my English is bad this forum is amazing
Try flashing the mk6 firmware (or the very first version of 4.3 for your carrier).
Try flashing the above mentioned firmware again after a factory reset in recovery (flashing twice clears old firmware remnants).
Try flashing via kies in emergency recovery.
Related
Hi Guys,
My Galaxy S2 came with KE7 I bought it in the UK and it's not branded to any network, I flashed CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4 and then the stock kernel and all was good.
A while later I tried to flash the clockworkmod from http://forum.xda-developers.com/showthread.php?t=1118693 ... that flashed OK but I couldn't get into the CWM recovery so I flashed the CF-Root back.
The recovery menu now works, but I still have the warning triangle on boot (I have tried reflashing the stock kernel again). This in itself doesn't bother me too much - I did this a month or 2 ago.
I've been told by someone that there is an upgrade available via Kies, however when connecting the phone Kies on Windows just tries to connect for ages and then gives up. (I have disabled USB debugging). Not that it should be relevant but I have previously removed Kies.apk, KiesAir.apk and kieswifi.apk using g-script but I put these back before trying to do this.
My phone currently reports:
Android: 2.3.3
Baseband: I9100XXKE4
Kernel: 2.6.35.7-I9100XWKE7-CL215725 [email protected] #2
Build: GINGERBREAD.XWKE7
Looking at these values, is the mix of XX and XW correct? (It's possible that I might have downloaded the wrong CF-root version the second time)
All I would really like to do is get the official version Samsung version and then root the phone. I believe that the Kies upgrade would still keep all applications.
Any help would be much appreciated.
You can find official, stock roms in the development threads
Sent from my GT-I9100
Thanks.
I've seen the thread http://forum.xda-developers.com/showthread.php?t=1075278 but I'm not sure which is the correct stock firmware for me.
Given the other issues I've described above I'm a bit 'concerned' that I've already done something wrong :S
EDIT:Re-editting my post cos Im blind and cant read good
Sorry dude I got all screwed-up there I have ta apolagize.Anyway you can download the one i told you and all will be cool as its a UK+Europe generic as stated and its XWKF3 but you are indeed on KE7 and you will find it here
http://forum.xda-developers.com/showthread.php?t=1075278
its XWKE7 ,Build Date 18/05/2011 generic XEU
.TO root go to this link.
http://forum.xda-developers.com/showthread.php?t=1103399
its a kernel flash via odin that takes,from hitting the start button,about 10 seconds to complete.It roots and puts CWM on your phone.The kernel you want is one of the first ones (xx-xeu-ke7).You Cant go wrong its all explained.
EDIT: You can also check to see if it really is unbranded by checking your product code by typing this number and checking the last 3 letters of your code *2767*4387264636#
Thanks very much. The PCode I have is GT-I9100LKAXEU.
I'm going to try the latest KI3 and see how that goes, failing that I'll reflash the I9100XWKE7_I9100XXKE4_I9100XEUKD1 I've just got (I note that this lists KE4 and KE7 in the filename, which does match the version I currently have).
The important part about your code is the XEU which is your local CSC.this is recognized by kies when you connect.The first thing Kies does when you connect is rcognize this code to identify the phone and look for the appropriate firmware update.When you flash a new firmware if its not official obviously kies wont understand it cos it doesnt register.Your Product Code says your phone is a UK model (XEU) so for example if you flash an official firmware and by default the phone sets KOR then kies has 2 conflicting CSCs and thus might decide not to connect.If you want your phone to work properly on kies then when you flash an official FW make sure you have XEU selected as your CSC marking *#272*(IMEI)# this will then reboot your phone although its always good to do a factory rest too.Do this anyway although not on an official FW as it might not always set the CSC to your area so it pays to check.
This is what Kies looks at for an upgrade .
http://forum.xda-developers.com/showthread.php?t=1089874
Spoof FW Check Fus may be worth a search also.
jje
Hi, Thanks in advance for reading and helping me out with this issue.
Here are my phone information.
Model no: GT-I9100
Android Ver: 2.3.3
Baseband Ver: I9100CCKDH
Kernel Ver: [email protected]#2
Build no: GINGERBREAD.XWKDD
My phone is from Singapore so the original firmware should be the asian one (DXKI2). I wanted to root my phone so i followed instructions from this article.
Article url: androidadvices. com/ how-to-update-samsung-galaxy-s-ii-i9100-to-gingerbread-xwkdd-2-3-3-firmware
I followed everything it said, which was to first upgrade the firmware to XWKDD before rooting. I did not wipe any data before the upgrade. So at the end ODIN reflected a pass (green color) and i unplugged my phone. However it entered boot loop and i used the stock recovery mode to flash a stock kernel (DXKH2) to my phone. It seemed to have returned back to factory state but when i check my phone settings it reflected the different versions as mentioned in phone information above.
Please help as i have the conception that all version should be the same but mine is kinda all over the place. Am i wrong?
Secondly, KIES now does not recognise my phone's firmware when i plug it into the computer but i can still access my files through it. Why is that?
Thirdly, where should i go from here to root my phone? Please help provide me with answers and links so that i can eventually root my phone properly and install cyanogenmod onto my phone. I would really appreciate if someone could help answer my questions and give me step by step help for my problem. THANKS!!
Jephtath
Very old KDD firmware with looks like KH2 rooted kernel .
Secondly, KIES now does not recognise my phone's firmware when i plug it into the computer but i can still access my files through it. Why is that?
No codes match on Kies server .KDD and KH2 mix is not a known product .
One upgrade firmware to stock newer version Root phone if you need root to matching version as per instructions .
Stock Roms .and csc
http://forum.xda-developers.com/showthread.php?t=1075278
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
jje
I am unsure of what do you mean.
However, what i did was to use ODIN and flash the stock kernel for DXKI2 for my phone. I made a mistake in telling you that my original firmware was DXKH2.
Now the phone's build number is still GINGERBREAD.XWKDD.
When I connected my phone back to the computer, KIES cannot read the phone as it says that i have to use the KIES PC studio mode to connect. This error did not take place before hand as KIES would automatically connect to my phone.
What should i do now? I don't know whether my phone is using the latest XWKDD firmware so it may not be ready for rooting. What should be displayed on my phone in order for me to know that the firmwares are ready to be rooted?
Please help me ASAP as I am afraid I have screwed up my phone. I dont even know how to bring it back to original factory settings and everything.
Jephtath
Goooooooooooogle
Jephtath said:
I am unsure of what do you mean.
However, what i did was to use ODIN and flash the stock kernel for DXKI2 for my phone. I made a mistake in telling you that my original firmware was DXKH2.
Now the phone's build number is still GINGERBREAD.XWKDD.
When I connected my phone back to the computer, KIES cannot read the phone as it says that i have to use the KIES PC studio mode to connect. This error did not take place before hand as KIES would automatically connect to my phone.
What should i do now? I don't know whether my phone is using the latest XWKDD firmware so it may not be ready for rooting. What should be displayed on my phone in order for me to know that the firmwares are ready to be rooted?
Please help me ASAP as I am afraid I have screwed up my phone. I dont even know how to bring it back to original factory settings and everything.
Jephtath
Click to expand...
Click to collapse
Mr. Egan showed you the links where to get your answers. Click on them and read and you will find everything you need, XWKDD is a firmware version that is ancient and outdated. You should flash new software for your country/region
I currently have a samsung galaxy s3 (i9300). I recently made a downgrade from android from android 4.3 to android 4.0.4 using odin.
However, after flashing, the sim card is no longer working,it's detected, but there's no signal. (only a smalle circle in the top).
i didn't even make a EFS backup. When i searched in the net i found that this has an issue with flashing a modem file with recovery depending on AP,CP,and CSC. Those are mine
AP:I9300XXALE8
CP:I9300XXLE8
CSC;I9300OJVALE7
Is there a link to flash the modem file with my configuration ? How can i change the imei without using a z3x box ?
Hi!
Try this emergency modem from this post: http://forum.xda-developers.com/showpost.php?p=43946365&postcount=15
Try searching before you make this any worse. You cannot downgrade from 4.3 so flash again with 4.3 and pray you haven't corrupted the efs, if you have then pay for a repair.
I am trying to repair my nephews i9300 with imei showing the fake 0049. I have been using smartphones for a decade now and it usually takes about 4hrs to 2days to solve a problem.
The first few things i read were the *#4636#* code which was not working on 4.3, so i flashed 4.0.4 but after flashing i realized it was not for reparing imei so i did not go through with it.
now the problem here is that 1), there is a galore of methods for fixing this 2), i dont wanna do anything too risky and brick the mobile of my nephew.
If it was my own phone i would have been done trying about everything by now but i am still reading around to see the surest and relative fix to my dev/prob.
Btw unlike from what i have read, his Imei got corrupted while he was asleep not flashing any custom roms etc.
Atm i am downloading the XXUGMK6 and will go through with flashing it before i install XXUGMK6 Modem.zip
XXUGMK6 Kernel.zip.
(i could not find the firmware for my country btw currently downloading one with OXA at the end.)
I hope it works out but any clear advise would really be helpful here.
Thanks.
@the boy plunger: I guess, there's no efs-backup.
What modem is actually installed?
rp158 said:
@the boy plunger: I guess, there's no efs-backup.
What modem is actually installed?
Click to expand...
Click to collapse
No backup, im currently flashing xxugmk6, let me get back to you.
.
Baseband is now i9300XXUGMK6. (thats the modem?)
Tried this method
http://www.androidveterans.com/solve-registered-network-galaxy-s3-i9300-issue-restore-imei/
First time with only PDA option, after ODIN was done, it gave me null/null IMEI, after flashing the patched Kernel and modem it went back to 0049. I checked CSC with *1234# and it was UNKNOWN.
Tried again with ODIN with PDA,CSC and Modem this time. After Odin the IMEI was 0049 instead of Null. After patched files flashing nothing chanded. (though CSC shows in *1234# menu).
Used this for flashing in Recovery.
CF-SGS3-CWM-v5.5-v1.2.zip
@the boy plunger: settings…info…baseband views your modem.
MK6 isn't actual, neither build nor modem. So try to update via OTA or KIES. (If they deny, you've to reset counter & status by TriangleAway first.) There's a little chance, that you get your IMEI back during update. Otherwise, let it repair by Samsung-service. All these witchy IMEI-procedures are either outdated or didn't work generally.
rp158 said:
@the boy plunger: settings…info…baseband views your modem.
MK6 isn't actual, neither build nor modem. So try to update via OTA or KIES. (If they deny, you've to reset counter & status by TriangleAway first.) There's a little chance, that you get your IMEI back during update. Otherwise, let it repair by Samsung-service. All these witchy IMEI-procedures are either outdated or didn't work generally.
Click to expand...
Click to collapse
I am at 4.3 currently will it update any further from Kies?
Btw 1 thing, He said he woke up in the morning it was saying "NOT REGISTERED ON NETWORK". He dint do any flashing or anything.
I think phone was working with the fake IMEI (0049) for more than a year and just stopped working when casue conflict between Wifi and Network radios etc.
What if i goo back to 404 and try the *#4636#* or similer methods?
Going back to 4.0 is worthless. IF there ever was a valid IMEI/efs-package, you messed it up in the meantime.
Either update-procedure repairs or service-center or going on without telephone-functions.
What about these methods?
http://www.sammobile.com/forum/showthread.php?t=15196
@the boy plunger: these are the witchy things. I only read about and didn't try, so go your way.
Maybe, the patched modem helps.
Hey guys,
Sorry in advance for what is no doubt something that's came up a few times in the past (as is clearly evident by the posts). I've spent a long time trying to get around the issues with this thing so hopefully I can explain what I've done so far which might help.
So, basically -
My brother had an S3. The screen broke (glass only) and he asked me to repair it. This was a few months ago. Inbetween he moved to using a Windows phone and had the S3 sitting around until he eventually decided to hand me it to repair a couple of days ago.
Now, the phone was working flawlessly prior to him turning it off and switching over to the Windows phone. The S3 sat dormant for a few months, battery out.
When I went to turn it on to test the screen and buttons to ensure that's the only fault, it wouldn't get past the boot screen.
No huge deal there.
Upon checking in recovery it was unable to mount the EFS partition. I managed to get round that.
It still wouldn't boot, so I flashed a new ROM and it booted up fine however was in "Factory mode" with IMEI starting 0049.
I've done a fair amount of searching and came to a few conclusions but essentially :
How I don't know but his EFS folder was competely corrupt and essentially contained few files, none of which were IMEI related. I have no clue how this has happened but it has.
I've managed to get the phone working ALMOST flawlessly by restoring a stock EFS backup IMG using kTool, I HAVE the phone's IMEI and serial which are printed on the phone itself. Only issue now is that the phone can't connect to any networks - because the IMEI is a default.
So, I've dug around in the stock EFS backup IMG that I was able to find (which has got the phone working great, minus mobile networks) and found that the IMEI folder contained a file "mps_code.dat". Upon opening this file it's basically empty. I assume this is because it's a stock EFS I located.
Does anyone have any clue how I can input the IMEI into this file? I tried to decompile the IMG, type it into the file and save, then recompile the IMG however kTool doesn't recognise the newly created IMG file and crashes, then restores the phone. Is there a specific tool I should be using to make the IMG and can someone root into their "mpd_code.dat" and tell me the format that it needs to be in? (I don't need or want any IMEI numbers, just the format that the file is. Just open it in a text editor through Root Explorer (root\efs\imei) and star out the IMEI if you can).
Just to clarify before anyone jumps on it - I'm NOT looking for the file(s) OR the IMEI numbers on anyones phone with that request. Simply the format in which it should be in. I'm simply trying to put the IMEI for the phone ONTO the phone so it'll recognise networks and work as it should. Everything else is absolutely fine now.
So just to clarify the options I've boiled down to :
Recompile the efs.img with the correct IMEI within - if someone can tell me how that'd be great - then restore it on kTool.
OR
Edit the on-phone mps_code.dat with the correct IMEI but I need the format (if someone could peek at theirs that'd be great).
Thank you in advance all and sorry for the story! If I manage to get this to work I'll upload a tutorial with all the relevent files required which I know will help a lot of people.
Cheers
Mine mps_code.dat have 3 letters in it i-e 'TNL' which is csc i think. And imei is in efs1 and efs2 partition you can see in pit analysis thread google it if you don't know anout this thread.
Only thing which you can do is give phone to repair shop they have boxes and tools which can write imei. Or take backup of efs1 efs2 and efs of other phone and restore it in your phone.you do backup/restore using partition backup app in playstore by wanam.
Thanks for your reply. I will try to locate someone else I know with an S3 and pull their EFS - hopefully something will happen that's of benefit.
In the meantime, I'll focus on this as hard as I can to get it sorted. I've managed to go from having the IMEI reading as a random 0049 one, to "Null/Null" which means it HAS been written to (or does in my mind), just with nothing rather than the correct number.
If I get anywhere I'll update this thread, and if im successful in the repair I'll create a How-To based on what I did.
Cheers
I can repair your device. Had the same problem with my mothers phone.
The problem is that samsung changed the style of the efs format years ago and the S3 was falling in this time.
So if you need help, i can help.
konsolen said:
I can repair your device. Had the same problem with my mothers phone.
The problem is that samsung changed the style of the efs format years ago and the S3 was falling in this time.
So if you need help, i can help.
Click to expand...
Click to collapse
Hey mate,
Want me to PM you?
Thanks
I had the same problem days ago and I couldn't connect to sim network.
What I did was flash stock rom using odin and then a custom modem and a custom kernel I found in the internet. At the end it gave me a normal imei number (not the [email protected]%) but it wasn't my original imei... nevertheless it can connect now without any issues .
jairolas said:
I had the same problem days ago and I couldn't connect to sim network.
What I did was flash stock rom using odin and then a custom modem and a custom kernel I found in the internet. At the end it gave me a normal imei number (not the [email protected]%) but it wasn't my original imei... nevertheless it can connect now without any issues .
Click to expand...
Click to collapse
Hey bro,
Do you remember specifically what ROM, kernel and modem you flashed? Ive tried this with no luck so interested in trying your combination.
Cheers
Ok guys this is exactly what I did:
1- backup all your data.
2- download a stock 4.3 jellybean rom from sammobile (I used the Trinidad and Tobago version because I live in Mexico but that shouldn't matter), autoroot cf for i9300 4.3 from their website and twrp 2.8 recovery, again from their website.
3- download this especial kernel and this modem:
https://www.dropbox.com/s/4cawyqzg8zo1vot/Patched_XXUGMK6_kernel.zip.zip?dl=0
https://www.dropbox.com/s/tky93zds14kt1hz/Patched_XXUGMK6_modem.zip.zip?dl=0
4- Proceed to flash stock 4.3 rom using odin 3.07.
5- After stock rom is installed flash the root cf file and recovery tar using odin.
6- Now that you have a rooted stock rom with custom recovery proceed to flash both the especial kernel zip and the modem zip using twrp recovery.
7- You should now be able to connect network.
Good luck.
jairolas said:
Ok guys this is exactly what I did:
1- backup all your data.
2- download a stock 4.3 jellybean rom from sammobile (I used the Trinidad and Tobago version because I live in Mexico but that shouldn't matter), autoroot cf for i9300 4.3 from their website and twrp 2.8 recovery, again from their website.
3- download this especial kernel and this modem:
https://www.dropbox.com/s/4cawyqzg8zo1vot/Patched_XXUGMK6_kernel.zip.zip?dl=0
https://www.dropbox.com/s/tky93zds14kt1hz/Patched_XXUGMK6_modem.zip.zip?dl=0
4- Proceed to flash stock 4.3 rom using odin 3.07.
5- After stock rom is installed flash the root cf file and recovery tar using odin.
6- Now that you have a rooted stock rom with custom recovery proceed to flash both the especial kernel zip and the modem zip using twrp recovery.
7- You should now be able to connect network.
Good luck.
Click to expand...
Click to collapse
Thanks bro, will try that in the morning!
Hey mate,
I started the process of this today, using a stock samsung FW that I updated to using Kies.
Unfortunately the end result is the same, 0049 IMEI number.
What I'll do is I'll download the T&T 4.3 from Sammobile and see if that makes any difference.
Thanks again,
jairolas said:
Ok guys this is exactly what I did:
1- backup all your data.
2- download a stock 4.3 jellybean rom from sammobile (I used the Trinidad and Tobago version because I live in Mexico but that shouldn't matter), autoroot cf for i9300 4.3 from their website and twrp 2.8 recovery, again from their website.
3- download this especial kernel and this modem:
https://www.dropbox.com/s/4cawyqzg8zo1vot/Patched_XXUGMK6_kernel.zip.zip?dl=0
https://www.dropbox.com/s/tky93zds14kt1hz/Patched_XXUGMK6_modem.zip.zip?dl=0
4- Proceed to flash stock 4.3 rom using odin 3.07.
5- After stock rom is installed flash the root cf file and recovery tar using odin.
6- Now that you have a rooted stock rom with custom recovery proceed to flash both the especial kernel zip and the modem zip using twrp recovery.
7- You should now be able to connect network.
Good luck.
Click to expand...
Click to collapse
yetep said:
Hey mate,
I started the process of this today, using a stock samsung FW that I updated to using Kies.
Unfortunately the end result is the same, 0049 IMEI number.
What I'll do is I'll download the T&T 4.3 from Sammobile and see if that makes any difference.
Thanks again,
Click to expand...
Click to collapse
Hey hey,
Right unfortunately all of the above doesnt solve any issues im having with the IMEI.
What I'm ultimately trying to do is find out a way to fix this, without having to use third-party hardware or a samsung service station.
The real reason is that I don't think the average user should have to go that extent to fix this - it's ultimately Samsung's fault.
Android is designed to be customisable allowing users to go up/down versions as they please (provided it's compatible with the hardware of their phone).
Just a thought -
is there any possible way to "bake" the old style EFS into a newer rom?
yetep said:
Hey mate,
I started the process of this today, using a stock samsung FW that I updated to using Kies.
Unfortunately the end result is the same, 0049 IMEI number.
What I'll do is I'll download the T&T 4.3 from Sammobile and see if that makes any difference.
Thanks again,
Click to expand...
Click to collapse
Hey All (that are viewing this).
The above procedure didn't work. I have managed to get the IMEI to change from 0049 to NULL/NULL and back again at will using a blank EFS restore file that I've got, however can't figure out what and how to change the files WITHIN the EFS restore to the correct IMEI etc.
I'll continue my search and if I come across anything, I'll let you all know on here and create a How-To.
Cheers
Hey all - just a quick question on this.
Does anyone know how to modify the server to which a program points to check for user credits etc? There's clear reason I'm asking for this, however for obvious reasons I won't elaborate further right now.
Cheers
Hello there! Is the problem fixed? Couple of days ago i fixed someones i9300 whos having this kind of error. Pm me ill help
lyxtian said:
Hello there! Is the problem fixed? Couple of days ago i fixed someones i9300 whos having this kind of error. Pm me ill help
Click to expand...
Click to collapse
I have sent you a pm.
konsolen said:
I can repair your device. Had the same problem with my mothers phone.
The problem is that samsung changed the style of the efs format years ago and the S3 was falling in this time.
So if you need help, i can help.
Click to expand...
Click to collapse
I have a samsung galaxy s7 sm-G930F which is bricked. no imei anymore and no efs backup. can u help me fix it?