Hi all
Just want to say I've been using XDA for a very long time, back to the OG Droid days, and wanted to say thanks right off the bat to those who are more skilled than I and for the help posted.
I recently aquired a sch-I545. The phone is in excellent condition, the only issue was that it was missing the IMEI, it's on the phone sticker, just not software. The baseband is also unknown. I knew this when buying it, that's how I got it so cheap. I figured that the guy had tried to flash it, and just didn't want to own up to it.
However, I have hit a wall. I've tried flash a stock rom on it so that I could root it and gain access to the EFS folder and see if I could modify anything. When I did, even though there was an EFS folder there was nothing to modify. I then heard about flashing a modem.bin to see about correcting the baseband and possibly the IMEI. Though I was rooted I didn't have a custom recovery, as of yet. I went to install TWRP via Odin and it starts the NAND write and then Fails.
So at my wits end I took it to a local shop, hoping that they might have better experience with this and I got the phone back today, with the Software Update Failed screen. I asked what was up, and was told that since someone tried to flash it, they erased the IMEI and they couldn't correct it. Asked why they gave me the phone back with the screen and was told that they too tried to flash with ODIN and it failed.
Luckily I didn't have to pay anything, but I think they just borked things up to and didn't want to own up to it lol.
SO....here's my question.
Can I flash a stock, or rooted ROM to this puppy that already has an IMEI and Baseband, and then Modify the IMEI to the correct one that is stickered on the phone? If I can, what search parameters should I look for? And is there a particular version of ODIN I need to use?
If I can't flash a ROM that already has a baseband and IMEI, how can I go about correcting this issue if ODIN doesn't want to write a custom recovery?
Thanks
You'll need Odin software and the correct factory image for the phone. There are a couple different builds so make sure to get the right one. If it's an MDK device and has never taken an OTA you're in luck. It can get TWRP on it after following the process. If it's later than MDK no TWRP. Search here and you'll find a thread explaining how to do it all.
Is there any way to tell if it's MDK after I flash the correct factory image? I have no clue if the person before updated via OTA.
Related
Error: “Not Registered on Network”
SGS III have JB 4.1.1 (I9300XXDLI8) ROM/baseband, rooted with CF-Root/TWRP.
I was running the above ROM with some sort of (probably) Soft unlocking done by a local mobile repair shop. Anyway, recently I decided to try out one of the custom ROM i.e. Omega 32.1 (JB 4.1.1) and before proceeding any further I made a full backup on SD card with TWRP.
I downloaded and flashed Omega 32.1, thinking that I can always go back if something doesn’t work out. Anyway, long and the short of it, when I restored my S3 through TWRP restore, I found out that it isn’t connecting with my mobile network i.e. Warid Tel with the error “Not Registered on Network”.
By the way I also happen to have the factory unlock code for this SGS3, but unfortunately all the USSD codes I've tried to enter it, doesn't work.
Although, I guess I can take it back and get it re-unlocked again, but that isn’t going to allow me to install custom roms.
Can anyone guide me how to fix this situation, any tips, help, will be highly appreciated.
Regards
Babur
Megneto said:
Error: “Not Registered on Network”
SGS III have JB 4.1.1 (I9300XXDLI8) ROM/baseband, rooted with CF-Root/TWRP.
I was running the above ROM with some sort of (probably) Soft unlocking done by a local mobile repair shop. Anyway, recently I decided to try out one of the custom ROM i.e. Omega 32.1 (JB 4.1.1) and before proceeding any further I made a full backup on SD card with TWRP.
I downloaded and flashed Omega 32.1, thinking that I can always go back if something doesn’t work out. Anyway, long and the short of it, when I restored my S3 through TWRP restore, I found out that it isn’t connecting with my mobile network i.e. Warid Tel with the error “Not Registered on Network”.
By the way I also happen to have the factory unlock code for this SGS3, but unfortunately all the USSD codes I've tried to enter it, doesn't work.
Although, I guess I can take it back and get it re-unlocked again, but that isn’t going to allow me to install custom roms.
Can anyone guide me how to fix this situation, any tips, help, will be highly appreciated.
Regards
Babur
Click to expand...
Click to collapse
Check your IMEI number.
Has it changed?
eggman89 said:
Check your IMEI number.
Has it changed?
Click to expand...
Click to collapse
No it hasn't changed.
The problem was the original "soft unlock"
Megneto said:
...
I was running the above ROM with some sort of (probably) Soft unlocking done by a local mobile repair shop. Anyway, recently I decided to try out one of the custom ROM i.e. Omega 32.1 (JB 4.1.1) and before proceeding any further I made a full backup on SD card with TWRP.
...
Click to expand...
Click to collapse
The problem was the original "soft unlock" - some of those (I believe even some early that were made by NSPro) are rather poor and are based on flashing a special modem binary. You will be able to fix it if you search around for the fix posted by Ariza (even if I believe something happened to the original post).
I am trying to find the fix by Ariza, but so far nothing has turned up. Also, if I search for the user "Ariza" it doesn't help either. Do you remember exact member alias?
Also, does that fix result in permanent resolution of the issue?
Or, is it better to get rid of this SGS3, and get factor unlocked version?
Thanks for your help and patience.
Edit:
I forgot to mention in OP that it correctly identifies the network when I check Status of the device.
Edit 2:
I was able to get hold of the guy who actually did the 'soft' unlocking in the first place, and he confirmed that it was done using NSPro (through Dongle) and is willing to do it again.
But the issue is, it will restrict me to JB 4.1.1 and I can't install any custom ROM.
Hmm ...
Megneto said:
I am trying to find the fix by Ariza, but so far nothing has turned up. Also, if I search for the user "Ariza" it doesn't help either. Do you remember exact member alias?
Also, does that fix result in permanent resolution of the issue?
Or, is it better to get rid of this SGS3, and get factor unlocked version?
Thanks for your help and patience.
Edit:
I forgot to mention in OP that it correctly identifies the network when I check Status of the device.
Edit 2:
I was able to get hold of the guy who actually did the 'soft' unlocking in the first place, and he confirmed that it was done using NSPro (through Dongle) and is willing to do it again.
But the issue is, it will restrict me to JB 4.1.1 and I can't install any custom ROM.
Click to expand...
Click to collapse
The thread was this:
http://forum.xda-developers.com/showthread.php?t=1918601
(in a post towards end I have some of the stuff from the forum where you had to register in order to get the files, and you might still recover some of those links - apparently those are patched versions of the corresponding stock modems which no longer check some of the information from nv_data.bin; you will need to add that modem after each major ROM change).
If you only plan to use 4.1.1 and not upgrade then NsPro should be OK, otherwise you either need a "subscription" to the services of that guy
Thank you for the help. I will go through that thread soon.
I've have also looked at this thread http://forum.xda-developers.com/showthread.php?t=1705650 by UpInTheAir. I have installed android SDK for Winx64 and successfully extracted modem.bin (as a test). I think I'll get the phone back to that guy, so he can patch the modem with NSPro again, once that is done, I'll extract the modem, repackage it so I can install it with CWM and test whether that can eventually help me in experimenting with other ROMs.
I will keep you posted on my progress.
Again thank you for your valued help.
Kind regards.
Babur
Having tried the method mentioned in my previous post, I finally gave up and took the phone for repair.
What transpired from thereon is interesting and confusing. As according to Mr. Repair 'serial number and IMEI' were repaired, nothing more. In fact I extracted the modem and compared it with the one I have, they are exactly same no patch applied.
However, both IMEI and serial number were showing correctly prior to the repair, and even after repair they are same (I double checked those with the original invoice/phone box etc.). So I am not sure how they were damaged when they were showing correctly.
Update:
I've sold the unit question, as I felt not to take any more risks with it, and bought an factory unlocked SGS3. Hopefully I will not face any problems with playing around with custom ROMs from hereon in.
Thank you and kind regards to all.
Babur
Below is the situation i'm in. Please dont reply with a generic "flash xyz in Odin" post as ive tried if you read.
I got a used Note 2. It has a clean ESN. Works fine. I wanted too root/unlock it to load a custom recovery and then a custom ROM.
It has VRALI3 as both baseband and Build.
I tried to use multiple version of Casual with no luck. I then tried to use different odin files with no luck..i keep getting an error and fails during the nand flash portion. At one point I soft bricked it (only boot logo..no recovery...no boot).
Only way i restored it was via sch-i605-16gb.pit in the pit area, I605VRLI3- verizon.tar for PDA and uncheck re-partition.
So back to where I was.
I tried to then use the pit file with CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar
No luck..fails with nand flash write error.
Tried instructions at http://forum.xda-developers.com/showthread.php?p=34891181
No luck.
Then I tried to load root66_VZW_stock_system.tar and it worked. It only has a system.img file in it.
With this..I have a baseband of VRALI3 but with a build of VRALJB with ROOT.
So I was supper happy and then tried to repeat everything above with no luck still..nand flash error.
I tried goo manager since i had root and loaded custom recovery..got the yellow triangle.
Back to pit + vrali3..then pit + root66 back to root.
And thats where i sit.
I think VRALI3 was a prelease build???? But i dont know what i need to do to get out of it and unlock the bootloader. I have no idea what version bootloader was/is loaded already....
What can I do??
Thank you for reading...and any help would be appretiated.
guardianali said:
Below is the situation i'm in. Please dont reply with a generic "flash xyz in Odin" post as ive tried if you read.
I got a used Note 2. It has a clean ESN. Works fine. I wanted too root/unlock it to load a custom recovery and then a custom ROM.
It has VRALI3 as both baseband and Build.
Click to expand...
Click to collapse
Vrali3 is the pre release which has a different bootloader than the other 3 versions. As far as I know, you are up a creak without a paddle. There is no way to unlock bootloader and root, or change to a different version when you are on that. Probably why the person was selling it. I'm guessing the person was selling it for cheaper than other ones and that's why you bought it. That pre release is known to be attached to that damn toolkit that people think is awesome. Sell it and buy a different one.
Sent From My Sticky Note, Too?
I'm trying to fix an S4 for my friends 14 yr old son. All I know is that he says he used towel root to root it. There's some stuff on screen. Stable root, stable boot initiating, build number etc; can't remember exactly and don't have the phone on me now. Anyway, it boots just fine but systemui is constantly crashing, making it impossible to do anything. I tried a factory reset with no luck. Still same problems. I downloaded stock firmware and tried to odin back to stock also with no luck. Getting a "fail(auth)" message. My question is, before I attempt to try odin again is there a way I can push a new systemui.apk to the phone to try and fix it? Or a way to remove the root files through adb? Any help is much appreciated. For the record, I've successfully unbricked many galaxy devices in my time. Don't know why this one is giving me such a hard time.
Odin failed? Probably a bad download. Also was it a no wipe or emergency repair file? Best bet may be to follow the links in this thread http://forum.xda-developers.com/showthread.php?t=2776189 for the appropriate build number and use the emergency repair if everything still isn't working.
I would recommend the no wipe Odin image from surge, Nc5, should take care of your issue. If that fails, you should try the Full wipe of NC5, bc that is rootable without downgrading or following some directions that you may not understand. Dont know your comfort level with the phone, but if you know adb, then you might be smarter than me.
Your Odin might have failed bc of a bad download. Try redownloading the file, use stock samsung data cable, try a different usb port on pc etc.
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?