Develop Bugs

[Q] Trouble Unlocking Bootloader

Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. I have been trying to unlock this phone for 2 days now!
Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well my code is 16 numbers long. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same.
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.

Tread3r said:
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. For purposes of convenience and time (I have been trying to unlock this phone for 2 days now!) I will post my IMEI code here ( 3529000059203526 ) and the unlock code given to me by sony through email (61CAA387DC11C4CF).
I hope this doesnt break any rules or anything.
I am doing this to see if anyone here can help me. Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well as you can see my code is 16 numbers long, so in effect I only entered up to number "5". I would like to know if anyone is willing to test my IMEI and see if they get the same code. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key, this is why I am posting. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same (as above).
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Click to expand...
Click to collapse
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.

abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Thanks for the advice, I will edit it ASAP.

abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Hey he removed the imei number from his original message but that's pointless unless u remove it from your quote
Sent from my Xperia S using xda app-developers app

I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967

Chriszo said:
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Click to expand...
Click to collapse
Glad to hear im not alone . No I still haven't found a way to unlock it. Sorry for asking but what does "PN" mean? Just so we are clear.

Ok thanks for your answer. No problem, but its just a mistake. Correctly it should be "PM" for personal message. I thought you would write on this way so I cant read any reasults

UPDATE:
I have tried other processes that all have the same steps, be it they were simplified programs with GUI's. I have come to the conclusion that my fastboot driver was installed incorrectly, because the first time I installed it on my phone I was able to see the S1 bootloader icon on device manager and I was able to click on it fast enough to enable it to install the driver. And correct me if im wrong but when we press UP on the volume rocker on our XS's and connect it to the USB we should see a blue right light? Well that is what happens when I do it so I assume I installed it correctly then.
Now after these first few failed attempts at unlocking I got frustrated and just factory reset my phone, completely ( I made back ups of course). This time however I used a program which is suppose to install all the drivers and simplify the whole unlocking process, I dont remember what program exactly, i'll check my files and get back to you guys on that.
Again it failed, showing the FAILED ("oem" error message) so I checked the steps from Doomlords guide and re checked my device manager. This time when I connect my phone it doesnt show the S1 bootloader icon on Dev manager, instead it shows "android phone ADB Interface". BUT I still get the blue LED when I connect my phone via USB, so does that mean I have fastboot on my phone again? ( I assume I do because the program I used says it did install it correctly and it even showed the "install anyway" window)
I am almost loosing all hope to unlock my XS , maybe I got a lemon phone or did something wrong again. I am willing to do another factory reset and restart the whole process again. This time I will follow every single step on the official website and see what happens.
But before I do that I want to ask, does anyone know of any news or whereabouts for an unofficial unlock bootloader process? I know its a long shot because we already have an official way but as from recent experience it doesnt work 100% of the time.

Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/

Chriszo said:
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Click to expand...
Click to collapse
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.

Tread3r said:
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Click to expand...
Click to collapse
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).

It was AOKP, the advanced project for this device.
I think your right, but in how far is the bootloader linked to the needed kernel? And why cant the bootloader be unlocked several times...?
Of course the kernel is a main part of the rom, but without an unlocked bootloader even the kernel would not be accepted by the bootloader. Thats the problem with other firmwares/ roms why you have to unlock it

I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?

razormc said:
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
Click to expand...
Click to collapse
I am using Windows 7 and I have used flashtool. I believe the drivers are correct because,as you said, the blue LED does show and stay while I fastboot my phone. Same goes for the green LED when I go to flashboot.

Chriszo said:
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
Click to expand...
Click to collapse
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve

Tread3r said:
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Click to expand...
Click to collapse
First, unlock your bl. Then root. I done that on my old Arc S and it works great.
Sent from my LT26i using xda developers-app

@ Tread3r:
Yes the drivers are installed correctly, because the phone starts into fastboot and flashboot with each the right light.
Thats the great problem with our devices. I did it nearly the same way and Ive got a similar problem, as the first answers describe in this post. Actual the original stock rom is installed on my Sony and all works correctly, but its just a short-term workaround
The bootloader unlockind process still end in an error message and that is my problem.
@ Vatih:
Nice try, but this is our problem... :/
---------- Post added at 11:41 AM ---------- Previous post was at 10:57 AM ----------
I cant believe it myself, but the alternative way works, althought I cant read anythink in the tool because of the language...
I've got the superuser app and root permissions and all works.
This link helped me: http://forum.xda-developers.com/showthread.php?p=39498268
It's the tool for the "new" firmware, .55, the latest from sony.
Hope, its also succesfully with your devices

I solved our problem. My bootloader is now open
I did it with the unlock, flashtool tool of this forum that helps you to open the bootloader and flash kernels and roms.
http://forum.xda-developers.com/showthread.php?t=2087337
Seems like just the code was wrong.
It worked with the first try
But be careful, although its just the bootloader, all data will be deleted. My phone is empty again :/ Of course I've got some backups...

[Q] Unlock code does not work

Hi,
This is for a Canadian T889V (note 2) from Wind Mobile.
A few weeks ago I tried to use the online form to get an unlock code from Wind (they let you have the code after 6 months for $10), and the code didn't work, I called their customer support multiple times, and all I got was, try the same code again (tried it rooted/unrooted/completely stock, etc, etc...), and I'm down to the last unlock attempt.
They also suggested I call Samsung, which I did, but the Samsung rep just told me to call Wind again.
So, in the end, my situation is that I have 1 unlock attempt left, I have a pure stock phone (running 4.1.1, Baseband T889VVLALJ4 (I used Odin to flash image from SamMobile)) that has the flash counter tripped to 4, but at the Odin screen, it says:
Product name: SGH-T889V_NA_VTR (I thought Wind was supposed to be GLW)
Custom Binary Download: yes (4 counts)
Current Binary: Samsung Official
System Status: Official
Click to expand...
Click to collapse
I have tried what was suggested in this thread: http://forum.xda-developers.com/showthread.php?t=2014982 at least 10 times, I got the PERSO_NV_INIT is SUCCESSFUL message at the end at least 7 times, and in all attempts, when I put in the rogers SIM card from my iPad (only other micro SIM I have), it asks for an unlock code.
So now, I think my only option left is to try a third party unlocking service, and hope that it works... does anyone have any suggestions for such service?
Also, is it possible to reset the unlock counter at all/if this fails horribly, am I stuck with Wind for good?
Thanks,

StackUnderflow said:
Hi,
This is for a Canadian T889V (note 2) from Wind Mobile.
A few weeks ago I tried to use the online form to get an unlock code from Wind (they let you have the code after 6 months for $10), and the code didn't work, I called their customer support multiple times, and all I got was, try the same code again (tried it rooted/unrooted/completely stock, etc, etc...), and I'm down to the last unlock attempt.
They also suggested I call Samsung, which I did, but the Samsung rep just told me to call Wind again.
So, in the end, my situation is that I have 1 unlock attempt left, I have a pure stock phone (running 4.1.1, Baseband T889VVLALJ4 (I used Odin to flash image from SamMobile)) that has the flash counter tripped to 4, but at the Odin screen, it says:
I have tried what was suggested in this thread: http://forum.xda-developers.com/showthread.php?t=2014982 at least 10 times, I got the PERSO_NV_INIT is SUCCESSFUL message at the end at least 7 times, and in all attempts, when I put in the rogers SIM card from my iPad (only other micro SIM I have), it asks for an unlock code.
So now, I think my only option left is to try a third party unlocking service, and hope that it works... does anyone have any suggestions for such service?
Also, is it possible to reset the unlock counter at all/if this fails horribly, am I stuck with Wind for good?
Thanks,
Click to expand...
Click to collapse
Hi
I am also with wind and recently obtained the code same way you did. I am rooted running jedix 16 at the time with twrp as my custom recovery. So i am on 4.1.2 and the code worked right away. I dont think you should be on 4.1.1 to do it.
Sent from SGH-T889v Canadian Wind Mobile

vseslija said:
Hi
I am also with wind and recently obtained the code same way you did. I am rooted running jedix 16 at the time with twrp as my custom recovery. So i am on 4.1.2 and the code worked right away. I dont think you should be on 4.1.1 to do it.
Sent from SGH-T889v Canadian Wind Mobile
Click to expand...
Click to collapse
The first time I tried it I used the code on Jedi Master 10 (which is based on 4.1.2 if I'm not mistaken), I also tried the code on 4.1.2 stock (**MA3 base band), and 4.1.1 (**LJ4 baseband).
Right now I think my main priority should be figuring out if its possible to reset the unlock attempts counter (and/or finding other unlocking procedures to bypass the code/counter completely).

I think I just screwed myself even more, I took it to a shady place to see if its possible to get it unlocked, they did some weird voodoo crap which I think bricked by modem. (any attempts to get it into service mode shows a blank screen)
I tried reflashing everything and restoring an old EFS from long ago, but the baseband version in settings->about phone says Unknown, and it kept saying no SIM card even if I use my original SIM....
Did anyone encounter this before? how to fix this? do I need to get the hardware fixed? is Samsung likely to help?
Edit: I'm fairly sure they used and NsPro

You could probably just flash a new baseband and all will be well... Also the RIL needs to match the baseband as well for it to work and come up in about phone, so try downloading get RIL from the play store and see if it detects a non matching RIL (it needs to match the baseband) also it requires root
Sent from my Nexus 4

stewi21 said:
You could probably just flash a new baseband and all will be well... Also the RIL needs to match the baseband as well for it to work and come up in about phone, so try downloading get RIL from the play store and see if it detects a non matching RIL (it needs to match the baseband) also it requires root
Sent from my Nexus 4
Click to expand...
Click to collapse
Hi, thanks for the response,
I downloaded getRIL and gave it superuser permission, and it said my device is unsupported.
Also, what do you mean flash a new baseband? I restored an nandroid backup all the way back from Janurary and that didn't store phone functionality.
Thanks,

Dang... That's a shame, It is probably because the nandroid doesn't backup the modem/baseband, by the fact that you made a nandroid I'm assuming you have a custom recovery?
Sent from my Nexus 4

stewi21 said:
Dang... That's a shame, It is probably because the nandroid doesn't backup the modem/baseband, by the fact that you made a nandroid I'm assuming you have a custom recovery?
Sent from my Nexus 4
Click to expand...
Click to collapse
I have TWRP, I've tried using Odin to flash the stock .tar.md5 file from sammobile, and that didn't work. So I've re-rooted after that and recovered an old backup.
Strangely, I have modem.emmc.win and modem.emmc.win.md5 in the backup directory, but no modem option in TWRP when trying to restore that backup...

well that makes everything a lot easier, dont worry about ODIN, its a pain in the a$$
grab a modem from here http://forum.xda-developers.com/showthread.php?t=2061031 (see if you can find one that matches your ROM, otherwise just try any)
flash it in recovery, clear cache and dalvik and reboot and you should be sweet

stewi21 said:
well that makes everything a lot easier, dont worry about ODIN, its a pain in the a$$
grab a modem from here http://forum.xda-developers.com/showthread.php?t=2061031 (see if you can find one that matches your ROM, otherwise just try any)
flash it in recovery, clear cache and dalvik and reboot and you should be sweet
Click to expand...
Click to collapse
I tried both modems (4.1.1 and 4.1.2) from Wind (GLW) to no avail, it still says Baseband unknown and it still wont recognize any SIM cards...
If I go to a store with an NsPro, will they be able to fix it?

What's an nspro? Also if you don't mind losing your data, flashing a whole stock rom package through Odin should get you going if all else fails
Sent from my Nexus 4
---------- Post added at 09:57 AM ---------- Previous post was at 09:54 AM ----------
You should be able to grab a complete Odin package over on samfirmware
Sent from my Nexus 4

stewi21 said:
What's an nspro? Also if you don't mind losing your data, flashing a whole stock rom package through Odin should get you going if all else fails
Sent from my Nexus 4
---------- Post added at 09:57 AM ---------- Previous post was at 09:54 AM ----------
You should be able to grab a complete Odin package over on samfirmware
Sent from my Nexus 4
Click to expand...
Click to collapse
It's a thing that came up in research that repairs IMEI damage (I think but I'm not sure), in any case I already tried flashing an entire stock ROM (multiple times, 4.1.2 and 4.1.1) through Odin, and it didn't work.

Have you tried different packages, from memory some don't include the baseband and bootloader and stuff like that (It's been a while since my Samsung captivate)
Sent from my Nexus 4

stewi21 said:
Have you tried different packages, from memory some don't include the baseband and bootloader and stuff like that (It's been a while since my Samsung captivate)
Sent from my Nexus 4
Click to expand...
Click to collapse
Yes, I've tried the stock from this post:
http://forum.xda-developers.com/showthread.php?t=2061031
And a rooted version from this post:
http://forum.xda-developers.com/showthread.php?t=1975560

StackUnderflow said:
Yes, I've tried the stock from this post:
http://forum.xda-developers.com/showthread.php?t=2061031
And a rooted version from this post:
http://forum.xda-developers.com/showthread.php?t=1975560
Click to expand...
Click to collapse
At this point if I bring it back to Wind (and by extension, Samsung) I think it's fairly obvious I voided my warranty, but if I pay (not sure how much though), would they be able to fix it?

I'm not sure sorry, because I bought my captivate off XDA and the time I bricked it I had to mail it to adam outler and get it made unbrickable
try downloading an ODIN package from samfirmware and flashing it, because the .zip packages you linked wouldnt flash the modem and RIL. Also GLW is Wind on samfirmware, so just search T889V and choose the newest GLW package, youll need to make an account to download it

stewi21 said:
I'm not sure sorry, because I bought my captivate off XDA and the time I bricked it I had to mail it to adam outler and get it made unbrickable
try downloading an ODIN package from samfirmware and flashing it, because the .zip packages you linked wouldnt flash the modem and RIL. Also GLW is Wind on samfirmware, so just search T889V and choose the newest GLW package, youll need to make an account to download it
Click to expand...
Click to collapse
I already tried that (if you mean http://www.sammobile.com/firmwares/), and I think it's the exact same one as the teshxx download (factory image, exact same size and file name inside the zip, I haven't done an md5sum due to being on Windows),
I reflashed rooted injected stock ROM, did triangle away, and unrooted, and I'll bring it to Wind and see if they will fix it for me tomorrow.
Thanks for your help!

I think I'm actually having the same problems as this guy:
http://forum.xda-developers.com/showthread.php?t=2195869
I also tried QPST, and got the same exception as him...
And by page 4 the 2nd post down, http://forum.xda-developers.com/showthread.php?t=2195869&page=4 he took it to Samsung, and they did some software voodoo to bring it back to life... Fortunately there's a Samsung repair center in my city, and hopefully I'll have the same luck as he did (they aren't open tomorrow though).

One last thing before you do that (lucky you've got a repair centre!) this post says the efs is backed up when you install Cyanogenmod http://forum.xda-developers.com/showthread.php?p=30716302
So you might be able to recover it
Sent from my Nexus 4

stewi21 said:
One last thing before you do that (lucky you've got a repair centre!) this post says the efs is backed up when you install Cyanogenmod http://forum.xda-developers.com/showthread.php?p=30716302
So you might be able to recover it
Sent from my Nexus 4
Click to expand...
Click to collapse
When I restored the old backup (didn't work), I had the efs check box checked in TWRP, and I assume that efs should be in the stock ROM (that's how the OP of that thread did it)

[Q] AT&T S3 stuck on Edge (not LTE)

My problem:
My galaxy s3 takes a LONG time to connect to AT&T when it boots up (over 5 minutes), and then only has Edge:2 network service.
How I got here:
Had 4.1.2 installed from AT&T
I rooted my phone with the "no countering tripping method" as described here: http://forum.xda-developers.com/showthread.php?t=1739426 to 4.1.1 this downgrade apparently made something not work, I kept getting errors, something about acore process failures.
I re-installed the stock 4.1.2 from AT&T
Still getting process failures
Read that clearing the contacts sometimes works, it didn't
Read that factory reset helps, it did
I still wanted a rooted phone, so this time I used this method: http://forum.xda-developers.com/showthread.php?t=1746665
Again processes started crashing
Again had to reset to factory
Now I noticed my phone wasn't working at all
Found that my IMEI was set to 0
Fixed that by following these instructions: http://forum.xda-developers.com/showthread.php?t=1804117
Note: the link to the sgs3.nv.gen.zip was bad, I found another here: http://forum.xda-developers.com/showthread.php?t=2335951 but my virus checker freaked out on it. I ran it on my kids pc, and it worked, don't know if I infected them or not, but I got my IMEI data back
Decided all this was too much hassle, so I reset my flash count to zero with this: http://forum.xda-developers.com/showthread.php?t=1494114
Reverted to stock 4.1.2 from AT&T and reset to factory
Still stuck on Edge:2
Found this thread: http://forum.xda-developers.com/showthread.php?t=2036891 my phone won't let me change my band preference, also under *#197328640#>SIM>CHECK NV it say "Band perf: Unexpected value"
Question:
Where do I go from here?
Thanks!

thabin said:
My problem:
My galaxy s3 takes a LONG time to connect to AT&T when it boots up (over 5 minutes), and then only has Edge:2 network service.
How I got here:
Had 4.1.2 installed from AT&T
I rooted my phone with the "no countering tripping method" as described here: http://forum.xda-developers.com/showthread.php?t=1739426 to 4.1.1 this downgrade apparently made something not work, I kept getting errors, something about acore process failures.
I re-installed the stock 4.1.2 from AT&T
Still getting process failures
Read that clearing the contacts sometimes works, it didn't
Read that factory reset helps, it did
I still wanted a rooted phone, so this time I used this method: http://forum.xda-developers.com/showthread.php?t=1746665
Again processes started crashing
Again had to reset to factory
Now I noticed my phone wasn't working at all
Found that my IMEI was set to 0
Fixed that by following these instructions: http://forum.xda-developers.com/showthread.php?t=1804117
Note: the link to the sgs3.nv.gen.zip was bad, I found another here: http://forum.xda-developers.com/showthread.php?t=2335951 but my virus checker freaked out on it. I ran it on my kids pc, and it worked, don't know if I infected them or not, but I got my IMEI data back
Decided all this was too much hassle, so I reset my flash count to zero with this: http://forum.xda-developers.com/showthread.php?t=1494114
Reverted to stock 4.1.2 from AT&T and reset to factory
Still stuck on Edge:2
Found this thread: http://forum.xda-developers.com/showthread.php?t=2036891 my phone won't let me change my band preference, also under *#197328640#>SIM>CHECK NV it say "Band perf: Unexpected value"
Question:
Where do I go from here?
Thanks!
Click to expand...
Click to collapse
This just happened to me too. I backed up my IMEI but lost it and had to get a new phone. I used QPST tool to restore my IMEI , which is located behind your battery. I did not work. There is another tool called NV Generate or something like that and still it did not work. I did not like spending the money for a warranty replacement, of course, so looked and tried hard for a fix. Since nothing worked I am also thinking that its possible I had a hardware problem, but I can say that an IMEI issue can be as bad as hardbricking, so proceed with caution and follow to a T. Good luck bro. I hope you can fix it. Let me know if you have a chance.
Edit: I missed the part about you using NV tool. I spoke with a bunch of Att help and a Samsung guy as well. Nobody knew about it. Mine was 5 freaking days past warranty. Still sick from that. If you are under warranty. Take it back.

I'm also having these issues..
Anyone have a true fix? I would go back to Full Stock, but have already tried that and still had the data issues. Something is hosed that needs to be fixed..

Fixed!!
I bought a new phone from AT&T, copied the nv config using the instructions here:
http://forum.xda-developers.com/showthread.php?t=1804117
Changed the IMEI to my phone's IMEI, and EUREKA! It works!
I'm attaching the file I used (with the IMEI blanked out, so be sure to fill in our own IMEI or this won't work for you, it is section 550, see http://forum.xda-developers.com/showthread.php?t=1804117 for more details).
I hope this helps others, and they don't have to pay the $35 restocking fee.

thabin said:
I bought a new phone from AT&T, copied the nv config using the instructions here:
http://forum.xda-developers.com/showthread.php?t=1804117
Changed the IMEI to my phone's IMEI, and EUREKA! It works!
I'm attaching the file I used (with the IMEI blanked out, so be sure to fill in our own IMEI or this won't work for you, it is section 550, see http://forum.xda-developers.com/showthread.php?t=1804117 for more details).
I hope this helps others, and they don't have to pay the $35 restocking fee.
Click to expand...
Click to collapse
This is exactly what I need! Thank you! My usb is corroded so I cannot connect usb and will have to load this manually. Could you please tell me the exact process you used to add your EMEI # to the file? I have opened the text file and went to section 550, but I do not know if i'm properly changing the number.

bweyadn said:
This is exactly what I need! Thank you! My usb is corroded so I cannot connect usb and will have to load this manually. Could you please tell me the exact process you used to add your EMEI # to the file? I have opened the text file and went to section 550, but I do not know if i'm properly changing the number.
Click to expand...
Click to collapse
I fixed the IMEI using the following instructions:
http://forum.xda-developers.com/showthread.php?t=1804117
The link on that page for the utility to generate a new IMEI didn't work, but I found another copy here:
http://forum.xda-developers.com/showthread.php?t=2335951
*WARNING* my virus checker freaked out about this file. I ran in on my kids machine (not mine) and it seemed to work fine, but I want you to be warned about the royal freakout my virus checker gave me.

thabin said:
I fixed the IMEI using the following instructions:
http://forum.xda-developers.com/showthread.php?t=1804117
The link on that page for the utility to generate a new IMEI didn't work, but I found another copy here:
http://forum.xda-developers.com/showthread.php?t=2335951
*WARNING* my virus checker freaked out about this file. I ran in on my kids machine (not mine) and it seemed to work fine, but I want you to be warned about the royal freakout my virus checker gave me.
Click to expand...
Click to collapse
I got almost just the identical problem... However, I checked my phone and my IMEI number is still intact... yet im stuck on EDGE
story was that I brought my rooted S3 from ATT (but not unlocked) to China 2 weeks ago hoping to use the phone on China Mobile's network (though knowing that China Mobile doesnt support the same band for 3g/4g as the US).
It wasn't til after inserting the sim that I realized I havent unlocked the phone yet... and since ATT won't give me the unlock code, I ended up trying to use the *#197328640# method, which was unsuccessful because I was still on ICS and this method requires Jellybean.
So in a hurry I used odin to upgrade to a jellybean version that apparently wasn't compatible with my I747.
After taking to a local shop, the dude repairing my phone was able to get the OS running again but it was weird in that even with an ATT sim card the phone would ask for an unlock code.
So finally after doing the re-flash of the official ATT I747 Jellybean rom, I was able to get into the *#197328640# menu and unlock my phone using
the second method mentioned in here: http://www.wikihow.com/Unlock-Samsung-Galaxy-Siii-(S3)
I was happy to get it to work with China Mobile's sim even though I can only use EDGE over there, but I also realize the dreafully long wait time for the phone to get a signal from power on.
After coming back to the States today and inserting my original ATT sim card, I noticed that it still takes a long time for the phone to get a signal after power on and after it acquires the signal from ATT, Im only getting signal (feels almost like the phone is stuck in the international setting...)
I have tried to reflash to z999 rom with cwm, tried to reflash the modem firmware, nothing is working.
My IMEI is still showing up in the "status" under about this phone, and its the same number as it appears in the back of the phone...
but for some reason I feel like this might have something to do with the fiddling of the secret code menu during my unlock oversea... since I had to go into the UMTS menu (which I believe is for EDGE)...
Since my IMEI isnt lost... anyone have any ideas what could have been the problem? This is getting beyond frustrating... would really appreciate the help!

T-mobile S4 Stock Android 4.3, Cannot Unlock, IMEI unknown after attempt by localshop

Hi All,
I had purchased T-Mobile Samsung Galaxy S4 (SGH-M919) with Stock android 4.3 while I was in usa, and want to use it in my home country now as I have left usa. I couldn't found any unlock solution on internet for stock android 4.3, and T-Mobile would not give me the unlock code. I tried third party services to provide unlock code and it did not work either. So I went to a local shop, and he screwed everything up. When I went back to the local shop to receive my phone (hoping it might have been definitely unlocked by them), he told me that he tried to downgrade it to 4.2.2 but it did not work (only after reading through all the forums I realize there is no way to go back to stock 4.2.2 if you are on stock 4.3 because of knox / bootloader issues on 4.3, leads me to think the shopowner did not really do his research before touching my phone, and no, he did not do any EFS backup). In an attempt to unlock my phone, he also flashed Metro PCS stock ROM on my phone, not to mention, my IMEI number is also 'Unknown' now. I managed to get back on T-Mobile stock 4.3 ROM now but still IMEI is unknown. I also tried to go to nearest Samsung center and they said they would not touch international phone models. At this point I have no idea what to do. Any suggestions how to get back my IMEI and or at the least to get the phone working to my country's network?
Thanks.

Try flashing the mk2 modem using odin. That may work but not sure.
Sent from my SGH-M919 using Tapatalk

Shop just need to pay you for new phone.
☞ Sent from here☜???

I won't provide a link but there are ways to restore your imei and as for unlocking I have used fast gsm dot com and it has worked every time. I hope u get ur issues fixed. Good luck
Sent from my SGH-M919 using Tapatalk

sd_N said:
I won't provide a link but there are ways to restore your imei and as for unlocking I have used fast gsm dot com and it has worked every time. I hope u get ur issues fixed. Good luck
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Hi sd_N, is it possible for you to provide me the link in private so I can just restore my original imei. I will then try fastgsm.com to unlock as you suggested. Thanks.

Anyone?

galaxysiv said:
Anyone?
Click to expand...
Click to collapse
Did you ever make any nandroid backups through recovery or save your /efs?

xdapowerapps said:
Did you ever make any nandroid backups through recovery or save your /efs?
Click to expand...
Click to collapse
Hi xdapowerapps, no I did not, I didnt knew the local shop would try to downgrade or flash METRO PCS rom on it :crying:

galaxysiv said:
Hi xdapowerapps, no I did not, I didnt knew the local shop would try to downgrade or flash METRO PCS rom on it :crying:
Click to expand...
Click to collapse
The local shop broke it. Tell them to pay for it.
Also, the only reason T Mobile won't give you an unlock code is if the phone isn't paid for in full. If the phone is paid for in full, they HAVE to give you the unlock code.
Are you sure you didn't buy the phone in the US, then leave the country without paying the bill so you could use the phone internationally without paying full price? If not, there is no reason T Mobile wouldn't give you the unlock code. So there's some missing information in this story.
Also, we do not discuss how to change IMEI's on XDA. The only thing permissable on XDA about flashing IMEI's is restoring YOUR OWN IMEI from a backup. That is done by restoring the EFS partition. But you didn't have a back up so you can't do that. That means anyway to fix your IMEI involves what is an illegal hack and that discussion is expressly not permitted on XDA. That information is used for illegal purposes and XDA is not going to be the place where it's shared for legal reasons.

Skipjacks said:
The local shop broke it. Tell them to pay for it.
Also, the only reason T Mobile won't give you an unlock code is if the phone isn't paid for in full. If the phone is paid for in full, they HAVE to give you the unlock code.
Are you sure you didn't buy the phone in the US, then leave the country without paying the bill so you could use the phone internationally without paying full price? If not, there is no reason T Mobile wouldn't give you the unlock code. So there's some missing information in this story.
Also, we do not discuss how to change IMEI's on XDA. The only thing permissable on XDA about flashing IMEI's is restoring YOUR OWN IMEI from a backup. That is done by restoring the EFS partition. But you didn't have a back up so you can't do that. That means anyway to fix your IMEI involves what is an illegal hack and that discussion is expressly not permitted on XDA. That information is used for illegal purposes and XDA is not going to be the place where it's shared for I also still see the imei folder inside EFS with a file mps_code.bat, but no nv files. (The imei folder was not regenerated on deletion either) Am I missing something? also still see the imei folder inside EFS with a file mps_code.bat, but no nv files. (The imei folder was not regenerated on deletion either) Am I missing something? egal reasons.
Click to expand...
Click to collapse
Hi skipjacks, thanks for responding. Nothing is pending with t-mobile, I was on prepaid account. I bought the phone like 10 days before leaving usa (due to emergency). T-mobile says my number on this new device should have being working for at least 45 days or so with refill balance. My cycle ended after 15 days of purchase and I really didnt see any reason to refill it as I was no more in usa. And no, I dont want to CHANGE my IMEI, only want to restore my own IMEI only. I am not sure if my EFS partition is corrupted, because I rooted my phone tried to backup EFS folder now (I know its too late but still), deleted it and rebooted (as a few threads suggested it would regenerate nv data files), but neither did I see any nv files when I did a back up now, nor after I rebooted. When I rebooted, the EFS folder did regenerate but there were no nv files in there. Also, after deleting EFS and regeneration the serial number was corrupted, but when I restored my backup, the serial number showed up correctly again. Also my current backup contains the imei folder with mps.code_bat file. I noticed that even imei folder was not regenerated on deletion of EFS and reboot. I somehow have the feeling that this is still indicating that my original EFS folder is still present (though I may be wrong, because I dont know). But my concern is the nv data files, which I dont see anywhere. I did come across several threads about imei corruption and restoration, but the only one I didnt come across was T-mobile SGH-M919 with stock android 4.3. I am wondering if this has some different file storage structure for imei (which again I dont know). At this point I am concerned about getting back my imei, I can get the unlock code from some reputed paid service again. I understand that open discussion about imei involving anything CHANGING IMEI is not allowed here. If anyone could just help me out restoring my original imei, even by pm, I would really appreciate it. I just dont want to throw away the phone and lose my money because of the error done by repair shop.

galaxysiv said:
Hi skipjacks, thanks for responding. Nothing is pending with t-mobile, I was on prepaid account. I bought the phone like 10 days before leaving usa (due to emergency). T-mobile says my number on this new device should have being working for at least 45 days or so with refill balance. My cycle ended after 15 days of purchase and I really didnt see any reason to refill it as I was no more in usa. And no, I dont want to CHANGE my IMEI, only want to restore my own IMEI only. I am not sure if my EFS partition is corrupted, because I rooted my phone tried to backup EFS folder now (I know its too late but still), deleted it and rebooted (as a few threads suggested it would regenerate nv data files), but neither did I see any nv files when I did a back up now, nor after I rebooted. When I rebooted, the EFS folder did regenerate but there were no nv files in there. Also, after deleting EFS and regeneration the serial number was corrupted, but when I restored my backup, the serial number showed up correctly again. Also my current backup contains the imei folder with mps.code_bat file. I noticed that even imei folder was not regenerated on deletion of EFS and reboot. I somehow have the feeling that this is still indicating that my original EFS folder is still present (though I may be wrong, because I dont know). But my concern is the nv data files, which I dont see anywhere. I did come across several threads about imei corruption and restoration, but the only one I didnt come across was T-mobile SGH-M919 with stock android 4.3. I am wondering if this has some different file storage structure for imei (which again I dont know). At this point I am concerned about getting back my imei, I can get the unlock code from some reputed paid service again. I understand that open discussion about imei involving anything CHANGING IMEI is not allowed here. If anyone could just help me out restoring my original imei, even by pm, I would really appreciate it. I just dont want to throw away the phone and lose my money because of the error done by repair shop.
Click to expand...
Click to collapse
First off....the enter key is your friend. Hit it every so often when typing giant blocks of text like that. :laugh:
Second, since your IMEI has been deleted, you now have to change it, even if you just want to change it back to what it was before. The process to fix it now is what can't be discussed here.
IF you had backed up your EFS partition, then it would be as simple as restoring it in recovery. That's all well and good. But your IMEI is now 0, so you have to change it to what it was.
But all that aside, you went to a store and they broke it. Take it back there and raise holy hell until they fix it for you or buy you a new one. I know consumer protections are stronger in some countries than others, but wherever you are, yelling and screaming is a universal language.

Skipjacks said:
First off....the enter key is your friend. Hit it every so often when typing giant blocks of text like that. :laugh:
yelling and screaming is a universal language.
Click to expand...
Click to collapse
You
learn
new
things
every
day. :silly:

Can someone at least tell me what file in T-Mobile Galaxy S4 SGH-M919 Stock Android 4.3 contains imei number, so at least I know if I even have that file or not or whether it is missing? Thanks.

galaxysiv said:
Can someone at least tell me what file in T-Mobile Galaxy S4 SGH-M919 Stock Android 4.3 contains imei number, so at least I know if I even have that file or not or whether it is missing? Thanks.
Click to expand...
Click to collapse
Whether your file is missing, modified, or corrupted, you need your /efs folder to restore it. You do not have have a nandroid backup or the /efs folder. I am sorry but the simplest we can put it without sounding harsh, you're screwed. You need to request the local shop give you a replacement phone or credit to get a new one.

Update: I went back to the shop and told them "You broke it, you fix it, I don't know how and I don't care, you gotta fix it". They managed to fix the imei number somehow. Regarding unlock, the shop ended buying the unlock code themselves. They mentioned that no one is able to unlock T-Mobile S4 with Stock 4.3 as of now without unlock code, unless they have some device like Z3x box. The phone is finally unlocked and working fine on my network. (YES, A HUGE HUGE RELIEF).
Everything is fine, except for 2 issues.
1. I want to backup my EFS folder so that I don't enter into trouble with IMEI again. I tried EFS Pro, but its not working. All I see is "'Initializing ADB server..." (the phone is rooted, usb debugging mode enabled, and supersu permission granted when prompted). I also tried to backup using Andromizer, but it says "Notification: File not found in /storage/emulated/0/Amdromizer/efs/efs.img". What is my best option as of now to backup and store my imei safely somewhere?
2. I am having issues with Wi-Fi. Before the shop flashed my phone, it was all good, but now it doesn't auto-connect to my home Wi-Fi anymore. Everytime I reboot or get out of range, I have to manually select my home network everytime and also enter the password everytime. Nothing has changed on my router. The other Samsung device that I have still auto-connects to my home Wi-Fi as usual. How can I fix this?
Thanks.

galaxysiv said:
Update: I went back to the shop and told them "You broke it, you fix it, I don't know how and I don't care, you gotta fix it". They managed to fix the imei number somehow. Regarding unlock, the shop ended buying the unlock code themselves. They mentioned that no one is able to unlock T-Mobile S4 with Stock 4.3 as of now without unlock code, unless they have some device like Z3x box. The phone is finally unlocked and working fine on my network. (YES, A HUGE HUGE RELIEF).
Everything is fine, except for 2 issues.
1. I want to backup my EFS folder so that I don't enter into trouble with IMEI again. I tried EFS Pro, but its not working. All I see is "'Initializing ADB server..." (the phone is rooted, usb debugging mode enabled, and supersu permission granted when prompted). I also tried to backup using Andromizer, but it says "Notification: File not found in /storage/emulated/0/Amdromizer/efs/efs.img". What is my best option as of now to backup and store my imei safely somewhere?
2. I am having issues with Wi-Fi. Before the shop flashed my phone, it was all good, but now it doesn't auto-connect to my home Wi-Fi anymore. Everytime I reboot or get out of range, I have to manually select my home network everytime and also enter the password everytime. Nothing has changed on my router. The other Samsung device that I have still auto-connects to my home Wi-Fi as usual. How can I fix this?
Thanks.
Click to expand...
Click to collapse
For the efs you can back it up using recovery. Just boot to recovery and its one of the options in the backup menu. The resulting file will be like a few KB. Its supposed to be small. Dont worry
Sent from your phone. You should be more careful where you leave that thing.

Tmobile gave me an unlock code and my phone isn't paid for but I used the region lock away app before I got the unlock code and it worked but u got to be rooted
Sent from my SGH-M919 using xda app-developers app

Bell S3 Unlocking Issues

Hey guys,
I've been trying to unlock my phone for a few days now. Long story short, I moved from Canada to Japan and now I want to unlock my S3 to use a Japanese SIM.
I bought an unlock code from eBay. I was previous running cyanogenmod but then I was told that rooting will cause issues, so I unrooted my phone after an unsuccessful SIM unlock attempt. (wiped the phone, installed stock TW)
Even after unrooting I still had issues, and was given directions for the Service mode. That did not work either. I have tried many different methods and troubleshooting tips and nothing seems to have worked.
Here are some screenshots of the debug mode, my phone details, and a simple root checker app I installed.
puu.sh/dPN0p.png
Here are some specs: SGH-i747m Samsung Galaxy S3 on Bell running official firmware 4.4.2
Thanks for reading, and I really hope someone can help ;_;

Does your phone display the correct imei as the one you provided to the unlocker? The imei using the dial pad is the same as the imei on label attached to the phone?

audit13 said:
Does your phone display the correct imei as the one you provided to the unlocker? The imei using the dial pad is the same as the imei on label attached to the phone?
Click to expand...
Click to collapse
Yes it displays the same IMEI on the label of the phone, and when using *#06# on the dial pad.
Despite my flashing back to stock, multiple sellers I have been through on eBay believe my phone is still rooted. One of my friends believed the people on eBay are at fault.
I then bought a code from a somewhat reputable looking website (cellunlocker.net) and received the exact same code. They had provided some additional troubleshooting methods but they did not work.

So it just won't accept the code or the prompt to enter the code doesn't appear on the screen?

audit13 said:
So it just won't accept the code or the prompt to enter the code doesn't appear on the screen?
Click to expand...
Click to collapse
The prompt appears on screen no problem. It won't accept the code. Please refer to the screenshots I posted in the OP (the puu,sh link)
Is there some extra step I can do to get my phone back to normal? I thought just flashing stock and wiping data/cache would do it but I'm still having problems and I can't figure them out.
I'm aware downgrading firmware is out of the question, but I really have no options left.
I haven't technically activated the Japanese SIM card yet. Could that be an issue?

Did you restore stock using Odin and firmware from sammobile.com?
Don't attempt to downgrade if you have a 4.4.2 bootloader as that could brick your phone.

audit13 said:
Did you restore stock using Odin and firmware from sammobile.com?
Don't attempt to downgrade if you have a 4.4.2 bootloader as that could brick your phone.
Click to expand...
Click to collapse
Yes I grabbed firmware from sammobile and flashed with Odin. I made sure to match the last four digits in the baseband of my phone which is FNH2 so I downloaded this one from sammobile
sammobile /firmwares/download/34795/I747MVLUFNH2_I747MOYCFNH2_BMC.zip/

On the Odin "Downloading..." screen, my warranty bit is 1. Could that be causing the issue?
If so how do I fix that

The warranty bit will not prevent your from unlocking the phone. When a phone is shipped, the warranty bit is set at 0. If a person flashes any non-Samsung approved software, it will change the warranty bit from 0 to 1. It cannot be reset to 0.
When flashing with Odin, I prefer 3.07. So you are just unzipping the file and flashing the tar.md5 file in PDA section? Try again but only check F reset time. Once you see reset in the status window, remove the usb cable, remove the battery, boot into recovery, do a factory wipe, and reboot.

audit13 said:
The warranty bit will not prevent your from unlocking the phone. When a phone is shipped, the warranty bit is set at 0. If a person flashes any non-Samsung approved software, it will change the warranty bit from 0 to 1. It cannot be reset to 0.
When flashing with Odin, I prefer 3.07. So you are just unzipping the file and flashing the tar.md5 file in PDA section? Try again but only check F reset time. Once you see reset in the status window, remove the usb cable, remove the battery, boot into recovery, do a factory wipe, and reboot.
Click to expand...
Click to collapse
Still no luck unfortunately ;_;
Blah. Might just sell this phone and buy a Japanese one.

The only other thing I can think of is a corrupt EFS folder.
Did you try re-injecting the imei?

audit13 said:
The only other thing I can think of is a corrupt EFS folder.
Did you try re-injecting the imei?
Click to expand...
Click to collapse
First time I've ever heard of that. Backup/restore?
I just did a quick google search and couldn't find a solid guide. Did you have a certain process in mind?
I appreciate all of your help.

http://forum.xda-developers.com/showthread.php?t=1804117

audit13 said:
http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
Thank you for providing the guide. Unfortunately it's still not working. I uploaded a video just in case that might help, I also have to get a refund from an unlock website, lol.
https://www.youtube.com/watch?v=anrfCgMvBrw&feature=youtu.be

This is really weird as it looks like you are doing everything right.

audit13 said:
This is really weird as it looks like you are doing everything right.
Click to expand...
Click to collapse
Then you can understand why I am incredibly frustrated, hahaha.
It's cool. I just ended up buying a Japanese phone.
Thank you for all your help, hopefully no one else runs into thee issues in the future