[Q] emergancy calls only - Galaxy S I9000 Q&A, Help & Troubleshooting

Hello, two days ago I had a flight, and during the flight time my phone was in Flight Mode, when we landed I turned off flight mode and my phone ha s no signal 'emergancy calls only'. Have tried few different sim cards which had worked one years ago in this Country (UK). Tried: wipe, rom reinstall (Cyanogenmod 10.1), installed stock 2.3.6 GB rom. Can anyone help?

try flashing stock jvu firmware using odin without simcard inside
Sent from my GT-I9000 using xda premium

Finished flashiink few minutes ago, has not solved my problem :/

try your sim in another phone and see if it's working !!!

I tried 3 different cards, which works on other phones. Maybe my phone locked?

does your sim have a pin code ? does the phone request for it after the boot ?

Sim's does not have pin codes

Have you tried to manually select the network..?

I tried, but I dont realy know that I do it right

Is there any network showing when you did the manual search.? If no, I'm afraid its a radio problem

yes, phone Finds 5 signals

Bingo..! So you still have hope. Let me check the soln. I'll get back to you if I found one..

If it helps, my sim is from Lebara carier

Is your home network showing in those 5 networks.!

Yes

What's the reply you getting when u trying to catch it manually..
Also check you can see the imei of your phone. Type *#06#

Registerting, then "Can't connect to this network at the moment, please try again later" imei is correct

Try this. I'm not sure it works or not. Give it a try if you want to.
1. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site too)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you on Galaxy S.
For this, you’ll need root. If you have a root-enabled kernel, like the Voodoo lagfix kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC (to XEU for Europe): enter *#272*imei# on the phone tab. Note: this will reset your phone to factory settings, so make sure you did a clockworkmod backup before this. Incorrect CSC setting may cause MMS not working also.
4. check if you inserted the SIM card correctly Try this . I'm not sure it works. Just give it a try on your responsibility.
---------- Post added at 03:39 AM ---------- Previous post was at 03:35 AM ----------
Check any of the first 3 methods works or not.

Try what @jabrif said if it's not working try this :
Flash your phone with GB firmware
check if your sim is working , if it's complete with this :
root your phone
flash cm9 ( ics 4.0.4 )
check if your sim is working , if it's complete with this :
flash the rom based on cm 10.1 or 10
check your network signal
good luck

When I flashed GB rom JVU, it hasn't solved my problem. Maybe something wrong with efs folder?

Related

[Q] soft-bricked SGS, undetected to kies/odin/heimdall

Hi everyone!
I have been reading all the posts I can to see if there was anything similar to what has happened to me. So this is the issue. The phone model is Samsung Galaxy S I9000GT
Last night I flashed my phone to install CyanogenMod and did the following steps:
Got it into Download mode with the three buttons
installed the Samsung USB composite device driver
Ran zadig.exe of the Heimdall Suite
Launched Heimdall frontend
unzipped Hardcore SpeedMOD kernel
ran the zImage of the Hardcore SpeedMOD kernel on Heimdall frontend (it was supposed to show a blue bar transfer but it was the normal green one on win7) it went to 100% and rebooted. It was showing the normal boot loop screen and then I tried to get it onto recovery mode and it went nuts.
After this, the phone went soft-bricked with the pc (problem icon) cellphone icons, I am able to get it onto Download Mode but unable to put it on Recovery Mode, I would like to put it on CM7 if possible, the only thing the phone does now is to get on the soft-bricked screen and on Download Mode, I have tried pluging it onto different machines running ODIN, a win7 and win XP, both 32 bit and none of them is able to recognize it, it is recognized as Gadget Device on the win XP machine, on the win7 with kies it just loops on the connecting icon, on Heimdall it doesn't recognize it at all... any ideas of what to do?
Make sure Kies is off and dead (check task manager processes for all kies related). Then try Odin.
Try cleaning the USB ports (phone/computer cable) as sometimes when the device is almost recognized that helps.
Did you try to get into recovery before it had fully flashed (ie rebooted and then gotten all the way to the homescreen)? If you tried to go into recovery during the first boot sequence then I could see having issue.
That being said, if you can get into download mode you likely only have an issue with 1) Driver (I would remove and reinstall) 2)Ports/cables (Clean and then Clean again - really I helped someone this morning that cleaned once but still had issues and then cleaned again and got it done) 3)Kies is active when it shouldn't be (like most of the time IMHO).
Also try to remove the battery, go into recovery and then immediately connect to odin. Once in odin, I'd flash a complete rom with pit file (and make sure it has all the files or you'll get a mounting error). But the key is getting Odin or Heimdall to see the phone.
G
thank you very much! it is now recognizable on Odin!!!!
So I have the 512.pit file but I don't have the PDA, Modem, Bootloader, CSC files, do you know where can I get them? I have already downloaded the CM7 zip file
ospina said:
thank you very much! it is now recognizable on Odin!!!!
So I have the 512.pit file but I don't have the PDA, Modem, Bootloader, CSC files, do you know where can I get them? I have already downloaded the CM7 zip file
Click to expand...
Click to collapse
Samfirmware.com will have a stockfirmware that should have them (but make sure all the files that create the partitions are there if you re-pit - my stock firmware does not have db_data on samfirmware but its needed for flashing with a pit file) though they are usually all packed in one file for the PDA spot.
But stock is likely not what you want. Just flash darky anything and which will get you CWM recovery which is what you want for CM7 (which I had problem trying - write down you Imei and back up you efs folder...).
G
Hello!
So I have already installed about 3 firmwares succesfully to my phone, the problem is that none of them recognizes the SIM Card, therefore rendering it useless again, I have installed 2 9000T (latinamerica version) and the 9000B and 9000M just to check, currently on Eclair on the 9000T with no option for upgrading it through kies. I just want to go back to the old firmware but I can't get to the one that is the one for my region apparently correct. Does having the SIM card in while flashing it and such has any effect on it being unable to recognize it?
No sim shouldn't matter. Have you tried changing the csc so it's your region?
Sent from my GT-I9000M using XDA Premium App
As you may see, I am total noob on this, how can I get the CSC file for my region or how can I change it?
Thank you very much

[Q] galaxy ace s5830D in BOOT LOOP, no access to 'RECOVERY'

Hi gals and guys, I bought a new galaxy ace s5830D (gingerbread) from Telus and decided to unlock it the following way:
1. root using Universal_GB_ROOT_v10.zip
2. installed SuperOneClickv2.1.1-ShortFuse.zip on PC
3. installed Root Explorer (File Manager) v2.19.apk
4. used ADB shell on PC to read ST5L for unlock code
here is where the problem begins:
-- upon reboot phone goes in a bootloop (screen lights for a sec without Samsung logo)
-- I CANNOT put phone in recovery via home + power
--I CAN put phone in 'download' via power + home + vol dwn; or to RamDump with vol Up; or to Emergency Dload Mode by holding both up and dwn
I have tried the following:
-- flash stock telus rom S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar using ODIN. The flash goes successful but upon reboot goes back to bootloop? And still cannot enter 'recovery'
-- tried to flash cwm-recovery-ace.tar.md5 using ODIN. The flash is successful but on reboot goes to bootloop. Still no acess to 'recovery'
-- tried QtADB but cannot connect to phone
-- tried OneClickUnbrick but it will not recognize connection to phone either
-- tried AndroidSDK however cannot get to recognize device
So any ideas considering the main thing is I cannot get to 'recovery' and flashing with ODIN still results in bootloop.
Thanks for any advice
tedxdadevelopers said:
Hi gals and guys, I bought a new galaxy ace s5830D (gingerbread) from Telus and decided to unlock it the following way:
1. root using Universal_GB_ROOT_v10.zip
2. installed SuperOneClickv2.1.1-ShortFuse.zip on PC
3. installed Root Explorer (File Manager) v2.19.apk
4. used ADB shell on PC to read ST5L for unlock code
here is where the problem begins:
-- upon reboot phone goes in a bootloop (screen lights for a sec without Samsung logo)
-- I CANNOT put phone in recovery via home + power
--I CAN put phone in 'download' via power + home + vol dwn; or to RamDump with vol Up; or to Emergency Dload Mode by holding both up and dwn
I have tried the following:
-- flash stock telus rom S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar using ODIN. The flash goes successful but upon reboot goes back to bootloop? And still cannot enter 'recovery'
-- tried to flash cwm-recovery-ace.tar.md5 using ODIN. The flash is successful but on reboot goes to bootloop. Still no acess to 'recovery'
-- tried QtADB but cannot connect to phone
-- tried OneClickUnbrick but it will not recognize connection to phone either
-- tried AndroidSDK however cannot get to recognize device
So any ideas considering the main thing is I cannot get to 'recovery' and flashing with ODIN still results in bootloop.
Thanks for any advice
Click to expand...
Click to collapse
What ROM are you trying to flash with ODIN, because I couldn't find any on SamFirmware. Also in order to use ADB, you need the drivers, make sure you have them installed (they automatically install when you install Kies).
tedxdadevelopers said:
Hi gals and guys, I bought a new galaxy ace s5830D (gingerbread) from Telus and decided to unlock it the following way:
1. root using Universal_GB_ROOT_v10.zip
2. installed SuperOneClickv2.1.1-ShortFuse.zip on PC
3. installed Root Explorer (File Manager) v2.19.apk
4. used ADB shell on PC to read ST5L for unlock code
here is where the problem begins:
Click to expand...
Click to collapse
The stl5 method might damage the efs partition. It's a coinflip, with 3 outcomes:
-all goes well and you get an unlocked ace.
-your imei becomes 00000000000000 in which case you get aa working ace, but many carriers deny service to that imei, so no calls, no sms, no movile data.
-completely f****d up efs partition. You loose your imei. That's it, you're toast. No amount of flashing fixes this, it's not a hardbrick, but no rom will boot appropriately.
Try and flash a full package with odin. Make sure you use the correct odin version for your model and have the correct firmware. Then go into recovery and wipe everything, see if it boots. If it boots, open up your call app and dial *#06#* to see your imei (to make sure its still there).
If you have successfully flashed with odin before, and still won't boot or go into recovery, then maybe your efs partition got messed up.
Return the phone to telus, just don't tell them what you did.
thanks for the suggestions.. few more questions
-- any suggestions as to what to tell telus that is believable that happened? (phone is 3 days old and i bought it outright)
-- also re Efs partition damage, is there any way to repartition the phone and rewrite imei (isn't it on the stickers behind the battery)?
with ODIN i flashed (several times - all successfully) the stock rom made for the TELUS D version on the Ace. Its someone that build it from a stock Ace. Its available if u google it and many ppl have returned their Telus phones to stock telus\koodoo status via that rom with proprtietary carrier startup screen and all. The Model D of the Ace is not at all available on the SamFirmware site.
I also flashed only the CWM Recovery - sucessfully and still no access to 'recovery' menu.
ODIN i am using is the right version according to all i have read (4.42); and the .ops file is made, as I understand it, for partitions of the D version of the Ace. (odin + ops + rom was all one package that many ppl from telus have said to have used sucesfully to return their phones to stock.)
-- should i try to flash with odin a cyannogen mode 7.2.0; could that make a difference vs stock rom, or does the cyannogen just go on top of the stock rom; ie will not function without a proper stock rom? (i guess what i am asking is cyannogen a complete self contained os?)
--If the efs partition is damaged does it make sense then, that the ADB, oneclick unblock etc.., will not recognize the phone? Am i supposed to be able to even connect to ADB when phone is in 'download mode'? or its made to work only when phone is already booted up?
thanks guys again.. T
tedxdadevelopers said:
thanks for the suggestions.. few more questions
-- any suggestions as to what to tell telus that is believable that happened? (phone is 3 days old and i bought it outright)
-- also re Efs partition damage, is there any way to repartition the phone and rewrite imei (isn't it on the stickers behind the battery)?
with ODIN i flashed (several times - all successfully) the stock rom made for the TELUS D version on the Ace. Its someone that build it from a stock Ace. Its available if u google it and many ppl have returned their Telus phones to stock telus\koodoo status via that rom with proprtietary carrier startup screen and all. The Model D of the Ace is not at all available on the SamFirmware site.
I also flashed only the CWM Recovery - sucessfully and still no access to 'recovery' menu.
ODIN i am using is the right version according to all i have read (4.42); and the .ops file is made, as I understand it, for partitions of the D version of the Ace. (odin + ops + rom was all one package that many ppl from telus have said to have used sucesfully to return their phones to stock.)
-- should i try to flash with odin a cyannogen mode 7.2.0; could that make a difference vs stock rom, or does the cyannogen just go on top of the stock rom; ie will not function without a proper stock rom? (i guess what i am asking is cyannogen a complete self contained os?)
--If the efs partition is damaged does it make sense then, that the ADB, oneclick unblock etc.., will not recognize the phone? Am i supposed to be able to even connect to ADB when phone is in 'download mode'? or its made to work only when phone is already booted up?
thanks guys again.. T
Click to expand...
Click to collapse
Hey again, changing IMEI is illegal in some countries:
Here is a link on how to change it though.
when I go to repair my phone, they normally don't ask why does this happen, they just ask what's the problem. ALso, you have to pretend you are really angry, because the phone broke just 3 days after buying it. That's all. Just be sure that the boot animation is from the stock ROM, as well as the currently installed ROM.
Good deal, had phone exchanged for a new one. That should serve as a lesson to those trying to screw with their efs/ that sometimes it may actually NOT work!!
Thanks guys Cheers!

[Error] Gnote dont recognize simcard after factory reset.

Hello!
I did an update for ICS 4.0.4.
Everything was ok.
But after 3 weeks using this rom, I did a factory reset (*2767*3855#) and now my Gnote (GT-N7000) dont recognize any sim card.
I think this is not a problem related with IMEI. The IMEI number on the stiker in the back is the same when I put *#06# or access via menu.
Now in the notification bar appear "No SIM - Insert SIM Card"
-----------
What I've done:
Check if simcard is not inverted (no, it is not)
Try my simcard in another phone (yes, this works)
Try another simcard in my phone (not work)
Do the factory reset again (not work)
Put the 4.0.4 rom again via ODIN (not work)
Upgrade to 4.1.2 via ODIN (not work)
Downgrade to 2.3.6 (not work)
Upgrade to 4.0.4 via Kies (not work)
Please, I need help to solve this problem!
Sorry about my english.
Thanks in advance,
Yuri
sushi745 said:
Hello!
I did an update for ICS 4.0.4.
Everything was ok.
But after 3 weeks using this rom, I did a factory reset (*2767*3855#) and now my Gnote (GT-N7000) dont recognize any sim card.
I think this is not a problem related with IMEI. The IMEI number on the stiker in the back is the same when I put *#06# or access via menu.
Now in the notification bar appear "No SIM - Insert SIM Card"
-----------
What I've done:
Check if simcard is not inverted (no, it is not)
Try my simcard in another phone (yes, this works)
Try another simcard in my phone (not work)
Do the factory reset again (not work)
Put the 4.0.4 rom again via ODIN (not work)
Upgrade to 4.1.2 via ODIN (not work)
Downgrade to 2.3.6 (not work)
Upgrade to 4.0.4 via Kies (not work)
Please, I need help to solve this problem!
Sorry about my english.
Thanks in advance,
Yuri
Click to expand...
Click to collapse
Have you checked that your IMEI (*#06#) matches the one below the battery?? Were you running stock 4.0.4 kernel when you wiped?
What happens in Odin PC when you try to flash firmware again? What is the error?
glevitan said:
Have you checked that your IMEI (*#06#) matches the one below the battery?? Were you running stock 4.0.4 kernel when you wiped?
What happens in Odin PC when you try to flash firmware again? What is the error?
Click to expand...
Click to collapse
Yes! They match!
No errors. Odin PC recognize my phone. I can flash a firmware and the process finish without errors.
I heard that do this kind of reset in a rom above to 4.0.x can brick the device. Is this right? (I hope not)
regards,
YM
sushi745 said:
Yes! They match!
No errors. Odin PC recognize my phone. I can flash a firmware and the process finish without errors.
I heard that do this kind of reset in a rom above to 4.0.x can brick the device. Is this right? (I hope not)
regards,
YM
Click to expand...
Click to collapse
Yes it is...anyway, if it is finishing fine, that doesn't seem to be your problem. I would suggest that you flash a safe kernel and continue from there just in case.
Check this out: http://forum.xda-developers.com/showthread.php?t=1901191
Try formatting it again. (To fat32).
If possible use your pc to do so.
Then try again...
Sent from my GT-N7000 using xda app-developers app
as per the stickies have you ever backed up your efs.. if you have it then restore it otherwise try the following method
Download "Terminal Emulator" app from market
- open it
- type into the command:
su
echo -n ON > /efs/imei/keystr
sync
Go to home, force close your terminal app, shut your screen off, and when your turn it back and now reboot your phone
Obviously you must be rooted so don't ask for it. Hope this works for you
Sent from my GT-N7000 using Tapatalk 2

Need Help Urgent Please

I Flashed a Stock Rom with a Stock PIT
After Flashed Successfully When My Phone Restarted it is Asking
enter password to use encrypted device storage
I am Shocked Because I didnot Put Any Password.
But I remember That i already have My Nandroid Backup Of My Phone.
So when I restore My Phone I get back to its Normal State BUT . . .
MY PROBLEM IS" IF I PUT A ENCRYPTION PASSWORD" AND WHEN I FLASHED A ROM WITH A 4GB OR 6 GB PIT FILE.
IT WILL AGAIN ASK FOR A PASSWORD OR NOT ??
IF IT ASK FOR A PASSWORD THEN CAN I PUT THE PASSWORD THAT I DONE RIGHT NOW ?
I am asking this Because i ddidnot put any Encryption password In my Phone . Then also when i Flashed a Stock Rom with Stock Pit. It ask Me For Password Help me please . .
1.costum rom
2.flash stock rom
3.done
bhomank said:
1.costum rom
2.flash stock rom
3.done
Click to expand...
Click to collapse
Not very helpful. I also have this EXACT same problem. Never set any passwords. Have tried PIT and ROM flash via Odin, both stock and custom ROMS
Same message.
Strange thing is it appears to have booted fine and that this password is being requested by the OS.
This is evidenced by the fact that there is an 'Emergency Call' button giving access to the emergency dialler, and that i can adjust handset volume settings via side buttons.
Indeed if i press the volume button the slider appears with the settings cog which if pressed shows the sliders for Ringtone, Media, Notifications and System volumes.
I have heard of a phone lock that can happen if you overstep the flash counter that some mobiles have installed at some level. i.e. if you flash ROMS too many times. Could it be this?
But if so how come it still persists after flashing? What level is it then stored at and how to get rid of it?
thx in advance
P.S. i note that if i go into download mode there is small text at the top left of my screen saying:
ODIN MODE
PRODUCT NAME: GT-N7000
CUSTOM BINARY DOWNLOAD: YES (4 COUNTS)
CURRENT BINARY: CUSTOM
what is putting this there? and why is it counting the no. installs i do?
ALSO NOTE THAT when in CWM6 and do a Factory Reset itsays this halfway thru the wiping process:
>Formatting /emmc/.android.secure
>Error mounting /emmc/.android.secure
same problem, can't make it go away
got same problem ? going to have a play see if i can get it gone , was hoping i would find an answer on here but may be time to bury it lol
---------- Post added at 02:12 PM ---------- Previous post was at 02:06 PM ----------
xaragen
24th May 2013, 03:57 PM |#11
Junior Member25 posts Thanks: 6
SOLVED.
Ok guys just a quick update. I haven't had time and forgot about this thread but here's what I did and I am posting here so that somebody in same situation could benefit. I created a note to self in past and found it.
"In case I ever get that annoying Encryption message.
Do the following:
1) For this method to work you must have access to SDcard or internal memory.
2) If you dont have access, make sure you have Superuser file on any type of Memory (internal or external).
(On the sidenote I will always keep that in internal as well as external card from now on.)
3) Fire up Odin - Install Clockwork Recovery in PDA - Do Not Check reset time.
4) START....
5) Install zip from sdcard... superuser
a) it will fail first time with error code 0.
b) do it again (dont worry about that).
6) Fire up odin again.
7) Rename the MD5 i717 file to TAR. (see NOTE)
8) PDA that ****.
9) START and wait....
10) PASS you're done. Thank PAST ME...!!!! "
NOTE : Now I think this will work for other devices than just I717. You must get a stock rom TAR for your device. Dont get the latest but the one before latest.
After booting is complete and the device no longer asks for passcode. Go into security settings of the device. Then Setup a password lock for your device. Make sure its password lock and is at-least 8 characters. NOTE DOWN THAT PASSWORD
REBOOT.
Device will ask for password to unclock, Enter it and then go to security settings again and disable password unlock it or simply set it to slide.
Make sure you have NOT enabled any device Administrators in security settings. Most commonly people with exchange accounts on phone have that.
After this you can flash the any ROM you intend to flash (On stock rom it will still appear.) and if that encryption screen comes up use the password you setup previously.
Again I cant guarantee this will work for individual devices but yeah It worked for me and my friends device (both i717). Its now a goto method to get rid of it.

Lose IMEI

I updated my phone to 6.0 is successful but I lose MY IMEI ,Now what can i do ?
. . .
Who can help me ?
tkp206093 said:
I updated my phone to 6.0 is successful but I lose MY IMEI ,Now what can i do ?
Click to expand...
Click to collapse
How did you lose it? Because updating to 6.0.1 is not how this happened.
Please share some details - how did you buy the phone, who is your sim card operator, where are you located, and what did you do before you started seeing this error? Also did you contact ATT or Samsung?
This error message is usually caused by a sim card problem. Visit your dealer and get it replaced.
lirex said:
How did you lose it? Because updating to 6.0.1 is not how this happened.
Please share some details - how did you buy the phone, who is your sim card operator, where are you located, and what did you do before you started seeing this error? Also did you contact ATT or Samsung?
This error message is usually caused by a sim card problem. Visit your dealer and get it replaced.
Click to expand...
Click to collapse
I bought this phone from the second hand website. When I first tried the phone for a week, it was normal without any error.
Then, I saw this website: https://mega.nz/#F!lJQj3JyR!Jky5Fhv0HySHIizJK-K1CA
This website can root my mobile which is for 5.1.1
I have followed these steps but then my phone was in reactivation lock.
I have tried so many methods to unlock it.
I paid for someone to control my computer to unlock it. It was successful.
After unlocked the phone, it was under the situation of losing IMEI.
I had not checked it after unlocked and updated it to 6.0 immediately.
Someone said that he could help me to rewrite it but he could only help me if I go to his place.
However, I am living in Hong Kong that I could not leave to find him.
This phone cannot be rooted.
I had called internet service centre to help me, but they said that it had been out of their service area.
Although they told me to go to their shop to ask for help, my phone is second hand.
I am afriad that they would not help me.
Do you have any other methods to help me?
tkp206093 said:
I bought this phone from the second hand website. When I first tried the phone for a week, it was normal without any error.
Then, I saw this website: https://mega.nz/#F!lJQj3JyR!Jky5Fhv0HySHIizJK-K1CA
This website can root my mobile which is for 5.1.1
I have followed these steps but then my phone was in reactivation lock.
I have tried so many methods to unlock it.
I paid for someone to control my computer to unlock it. It was successful.
After unlocked the phone, it was under the situation of losing IMEI.
I had not checked it after unlocked and updated it to 6.0 immediately.
Someone said that he could help me to rewrite it but he could only help me if I go to his place.
However, I am living in Hong Kong that I could not leave to find him.
This phone cannot be rooted.
I had called internet service centre to help me, but they said that it had been out of their service area.
Although they told me to go to their shop to ask for help, my phone is second hand.
I am afriad that they would not help me.
Do you have any other methods to help me?
Click to expand...
Click to collapse
This problem is very common when updating/flashing roms using recovery. It happend a couple of times on my old galaxy s3. Becouse we dont have CWM or TWRP yet to backup EFS partitions (that is where IMEI is stored) before flashing/updating,there is only one solution to this problem. And it has only 50% chance to work. You must flash original stock firmware using Odin(old one,before you updated to 6.0,for you that is 5.1.1).This will wipe your phone and every data you have on it, so backup your data.
Here you can download firmware.First one is very slow, dont know for second.
https://samsung-firmware.org/model/SM-G890A/region/ATT/
or
http://samsung-updates.com/device/?id=SM-G890A
Step 1) Turn OFF your mobile and go to Download Mode by pressing and holding the Volume Down + Home Buttosn together for few seconds followed by Power button then proceed with volume up.
Step 2) Now open ODIN on your PC and connect your Galaxy to your computer.
Step 3) Once your phone is successfully connected to your PC, the ID:COM box on ODIN will turn yellow and will show the COM port number.
Step 4) unzip the downloaded firmware, u will get a tar file.
Step 5) click on AP in Odin and choose the file ".tar"
Step 6) check "Auto Reboot" and "F. Reset Time" options and make sure that "Re-Partition" is unchecked
!!!!DO NOT CHECK "Nand Erase All" IN ANY WAY!!!!
Step 7) Click on Start button in ODIN window to start the flashing process. The process will take few minutes to complete.
DO NOT UNPLUG USB CABLE WHILE EXECUTING THE PROCESS, YOU MAY BRICK YOUR PHONE!
Step 8) When the installation is completed, you read a "Reset " then a "Pass". your phone will restart (first boot will take a longer time so don't panic)
It is recommended to make hard reset after flashing to have a fresh official firmware
I hope this solves your problem, if it doesnt,im very sory, but i belive there is nothing you can do.(for now)
pavijan123 said:
This problem is very common when updating/flashing roms using recovery. It happend a couple of times on my old galaxy s3. Becouse we dont have CWM or TWRP yet to backup EFS partitions (that is where IMEI is stored) before flashing/updating,there is only one solution to this problem. And it has only 50% chance to work. You must flash original stock firmware using Odin(old one,before you updated to 6.0,for you that is 5.1.1).This will wipe your phone and every data you have on it, so backup your data.
Here you can download firmware.First one is very slow, dont know for second.
https://samsung-firmware.org/model/SM-G890A/region/ATT/
or
http://samsung-updates.com/device/?id=SM-G890A
Step 1) Turn OFF your mobile and go to Download Mode by pressing and holding the Volume Down + Home Buttosn together for few seconds followed by Power button then proceed with volume up.
Step 2) Now open ODIN on your PC and connect your Galaxy to your computer.
Step 3) Once your phone is successfully connected to your PC, the ID:COM box on ODIN will turn yellow and will show the COM port number.
Step 4) unzip the downloaded firmware, u will get a tar file.
Step 5) click on AP in Odin and choose the file ".tar"
Step 6) check "Auto Reboot" and "F. Reset Time" options and make sure that "Re-Partition" is unchecked
!!!!DO NOT CHECK "Nand Erase All" IN ANY WAY!!!!
Step 7) Click on Start button in ODIN window to start the flashing process. The process will take few minutes to complete.
DO NOT UNPLUG USB CABLE WHILE EXECUTING THE PROCESS, YOU MAY BRICK YOUR PHONE!
Step 8) When the installation is completed, you read a "Reset " then a "Pass". your phone will restart (first boot will take a longer time so don't panic)
It is recommended to make hard reset after flashing to have a fresh official firmware
I hope this solves your problem, if it doesnt,im very sory, but i belive there is nothing you can do.(for now)
Click to expand...
Click to collapse
You said this is high risk, Can I try this ? I was not should download this 5.1.1 G890AUCU3BOJE?
pavijan123 said:
This problem is very common when updating/flashing roms using recovery. It happend a couple of times on my old galaxy s3. Becouse we dont have CWM or TWRP yet to backup EFS partitions (that is where IMEI is stored) before flashing/updating,there is only one solution to this problem. And it has only 50% chance to work. You must flash original stock firmware using Odin(old one,before you updated to 6.0,for you that is 5.1.1).This will wipe your phone and every data you have on it, so backup your data.
Here you can download firmware.First one is very slow, dont know for second.
https://samsung-firmware.org/model/SM-G890A/region/ATT/
or
http://samsung-updates.com/device/?id=SM-G890A
Step 1) Turn OFF your mobile and go to Download Mode by pressing and holding the Volume Down + Home Buttosn together for few seconds followed by Power button then proceed with volume up.
Step 2) Now open ODIN on your PC and connect your Galaxy to your computer.
Step 3) Once your phone is successfully connected to your PC, the ID:COM box on ODIN will turn yellow and will show the COM port number.
Step 4) unzip the downloaded firmware, u will get a tar file.
Step 5) click on AP in Odin and choose the file ".tar"
Step 6) check "Auto Reboot" and "F. Reset Time" options and make sure that "Re-Partition" is unchecked
!!!!DO NOT CHECK "Nand Erase All" IN ANY WAY!!!!
Step 7) Click on Start button in ODIN window to start the flashing process. The process will take few minutes to complete.
DO NOT UNPLUG USB CABLE WHILE EXECUTING THE PROCESS, YOU MAY BRICK YOUR PHONE!
Step 8) When the installation is completed, you read a "Reset " then a "Pass". your phone will restart (first boot will take a longer time so don't panic)
It is recommended to make hard reset after flashing to have a fresh official firmware
I hope this solves your problem, if it doesnt,im very sory, but i belive there is nothing you can do.(for now)
Click to expand...
Click to collapse
Thanks for your help, I tried but this method is not successful
pavijan123 said:
This problem is very common when updating/flashing roms using recovery. It happend a couple of times on my old galaxy s3. Becouse we dont have CWM or TWRP yet to backup EFS partitions (that is where IMEI is stored) before flashing/updating,there is only one solution to this problem. And it has only 50% chance to work. You must flash original stock firmware using Odin(old one,before you updated to 6.0,for you that is 5.1.1).This will wipe your phone and every data you have on it, so backup your data.
Here you can download firmware.First one is very slow, dont know for second.
https://samsung-firmware.org/model/SM-G890A/region/ATT/
or
http://samsung-updates.com/device/?id=SM-G890A
Step 1) Turn OFF your mobile and go to Download Mode by pressing and holding the Volume Down + Home Buttosn together for few seconds followed by Power button then proceed with volume up.
Step 2) Now open ODIN on your PC and connect your Galaxy to your computer.
Step 3) Once your phone is successfully connected to your PC, the ID:COM box on ODIN will turn yellow and will show the COM port number.
Step 4) unzip the downloaded firmware, u will get a tar file.
Step 5) click on AP in Odin and choose the file ".tar"
Step 6) check "Auto Reboot" and "F. Reset Time" options and make sure that "Re-Partition" is unchecked
!!!!DO NOT CHECK "Nand Erase All" IN ANY WAY!!!!
Step 7) Click on Start button in ODIN window to start the flashing process. The process will take few minutes to complete.
DO NOT UNPLUG USB CABLE WHILE EXECUTING THE PROCESS, YOU MAY BRICK YOUR PHONE!
Step 8) When the installation is completed, you read a "Reset " then a "Pass". your phone will restart (first boot will take a longer time so don't panic)
It is recommended to make hard reset after flashing to have a fresh official firmware
I hope this solves your problem, if it doesnt,im very sory, but i belive there is nothing you can do.(for now)
Click to expand...
Click to collapse
I repair my IMEI by SamsungToolPRO
tkp206093 said:
I repair my IMEI by SamsungToolPRO
Click to expand...
Click to collapse
I'm having the same problem with IMEI 350000000006. Idk what was the cause, I just switch the sim card then when I switch it back the IMEI gone.
I had SamsungToolPRO 24.3 here but it requires root to fix.
Can you or anyone else help me?
if you lose imei in update your phone you can get orignal imei number instant..!
Write Cert File To Fix Network.!
If you need Root I Can Help with both Of Version Root 5.0 Or 5.1 Or 6.0
Sent from my SM-G935T using Tapatalk
---------- Post added 03-03-2017 at 12:04 AM ---------- Previous post was 02-03-2017 at 11:41 PM ----------
here is image that show it wad rooted 6.0.1 i test in unlock network and repair imei..!
http://cloud.tapatalk.com/s/58b8b24c3c2a7/FB_IMG_1488497560081.jpg?
Sent from my SM-G935T using Tapatalk

Categories

Resources