Database Develop

[Q] Unlock code

i couldnt find my code, so was wondering when at&t will hand the, out to customers?
thnks

anyone...?

Download the apps sgs Unlock on the market

unlocked code for froyo 2.2
Any one knows how to unlocked code for froyo, or after flashed back to 2.1. Because I tried all the method and unlocked code all the market but it's not working.

after u update it to jh7, i guess the nvdata.bin gets deleted or shows some buffer values.....i wrote down my unlock code just after i got my cappy in stock condition....after froyo( cognition2.2beta7 ) also im unable to find the unlock code....
but mines unlocked anwyays.....

neo_31591 said:
after u update it to jh7, i guess the nvdata.bin gets deleted or shows some buffer values.....i wrote down my unlock code just after i got my cappy in stock condition....after froyo( cognition2.2beta7 ) also im unable to find the unlock code....
Click to expand...
Click to collapse
i think my captivate got an automatic update.
How do i know the nvdata.bin file has been deleted?
is there anyway to unlock if the nvdata.bin has been deleted ?
FYI I ran the market app from " DaGentooBoy" which also not able to find the unlock code. am I screwed ?

Why do you want to unlock?
Are you planning on switching to another GSM carrier or going overseas?
Are you planning on selling the phone on eBay and buying a different phone?
Or do you only want to unlock for the sake of saying you have an unlocked phone?
If you answered no, no, and yes (in that order) to any of those questions then you don't NEED to unlock.
Also, it was documented that upgrading to JH7 or JI6 deleted the nvdata.bin file from your phone, thus eliminating the possibilty of unlocking after you upgraded. You should have done it straight from JF6 when you got the phone, and backed up that file for future use. It pays to read and research.

miztaken1312 said:
Why do you want to unlock?
Are you planning on switching to another GSM carrier or going overseas?
Are you planning on selling the phone on eBay and buying a different phone?
Or do you only want to unlock for the sake of saying you have an unlocked phone?
If you answered no, no, and yes (in that order) to any of those questions then you don't NEED to unlock.
Also, it was documented that upgrading to JH7 or JI6 deleted the nvdata.bin file from your phone, thus eliminating the possibilty of unlocking after you upgraded. You should have done it straight from JF6 when you got the phone, and backed up that file for future use. It pays to read and research.
Click to expand...
Click to collapse
this phone was giving to me by someone who left the country, and i'm on tmobile so i have no use for a att locked phone

boi.. i guess ur screwed then.. well there was a method to reset the unlock code to anything u want but u gotta search for it yourself in the forums here......dunno if that worked out for anyone....
also try searching the forums.....the nvdata.bin file i guess doesnt get deleted but the place where the unlock code is written gets filled with buffer values...
again, i guess i read somewhere there is a method to get past that but even that only worked out for some....
i could search the forums for ya, but im in office an cant do so now....
just keep on searching in the forums...ull surely find the solution....

also, this is what ive read only in some forums that people pay around $25 to get their cell phones unlocked by giving their IMEI number or sumthng of that sort......am not from the USA so really have no clue about it.....

Diamond_dawg said:
this phone was giving to me by someone who left the country, and i'm on tmobile so i have no use for a att locked phone
Click to expand...
Click to collapse
Follow the One-Click Unlock guide
http://forum.xda-developers.com/showthread.php?t=761751
One way the unlock code could have gone missing is if the owner of the Captivate flashed to the leaked Froyo build and back to stock. As it is a leaked build it couldn't have been automatic afaik.

mine is a JH7 phone and i got the unlock code =D. at first i couldnt find it by the PC method. it wouldnt work. it gave me an error sagint the nv_file.bin wasnt there. and i searched for it and it wasnt. i thought i was screwed so factory reset,then i rooted my phone, enable sideloading using unleash the beast. After all that, i went to android market and search for "froyo" and supprisingly i found a unlocker that worked. (looks like a padlock perhaps 5th in the list) i installed it and ran it, IT FOUND IT!!! was so happy since im not even in USA and i can use it on any provider =D

xonsniper4 said:
mine is a JH7 phone and i got the unlock code =D. at first i couldnt find it by the PC method. it wouldnt work. it gave me an error sagint the nv_file.bin wasnt there. and i searched for it and it wasnt. i thought i was screwed so factory reset,then i rooted my phone, enable sideloading using unleash the beast. After all that, i went to android market and search for "froyo" and supprisingly i found a unlocker that worked. (looks like a padlock perhaps 5th in the list) i installed it and ran it, IT FOUND IT!!! was so happy since im not even in USA and i can use it on any provider =D
Click to expand...
Click to collapse
hey do u mean the app 'Samsung galaxy s unlock' by DaGentooBoy?? its the 7th in the market when we type froyo...i insalled it...no codes found! ! !
i upgraded to jh7 then to cogv2.2beta7
( i do have the unlock codes, just trying if this app works....not workin for me)

Diamond_dawg said:
this phone was giving to me by someone who left the country, and i'm on tmobile so i have no use for a att locked phone
Click to expand...
Click to collapse
I don't think it will get a signal on Tmo's 3G system, so why would you want to use it on Tmo's edge anyways?

fldude99 said:
I don't think it will get a signal on Tmo's 3G system, so why would you want to use it on Tmo's edge anyways?
Click to expand...
Click to collapse
You are correct. T-Mo's 3G frequency is different from AT&T's. T-Mo uses the 1700/2100Mhz range for their 3G while AT&T uses the 850/1900Mhz range. The only frequency range the companies share is the 900Mhz band which is 2G

fldude99 said:
I don't think it will get a signal on Tmo's 3G system, so why would you want to use it on Tmo's edge anyways?
Click to expand...
Click to collapse
I dont get at&t 3g or Tmobile 3g where i live

[Q] SIM card Disaster!...

Alright, so I have lost track of the # of hours I have spent trying to solve this problem. I have a Samsung Captivate originally purchased from Rogers, and a Rogers Sim card. I flashed a custom rom onto my captivate, which was good but still gave me some problems. I somehow ended up when clearing something in the rom getting into a bootloop, so I could no longer access my phone.
I used Odin to go back to stock, but my phone gives me the "no sim card in phone" issue. I checked by putting another sim into my phone..same issue, and I put my sim in another phone...and it works fine..so it is not my sim card. I did *#7465625#
and Network Lock is on. I even flashed to Rogers froyo rom, since I am using a rogers sim card, but still get that problem. None of the market tools for unlocking the phone give me any codes...what should I do..?

The SGS Unlock tool from the market won't work on Froyo, as far as I know (I haven't bothered checking to see if it has been updated in the past few months, but it was a 2.1 only thing the last time I checked.)
There is a froyo unlock procedure in the development section. Have you tried using that after flashing your Rogers rom?
http://forum.xda-developers.com/showthread.php?t=831569
Edit: Oh yeah, make absolutely sure you back up /efs before you do anything, or you'll have your face ripped off if the procedure doesn't work for you.

Helroz has put out an app on the market to unlock 2.1 and 2.2 phones Havent tried it yet.... worth a shot...

kind of confused. I mean, I originally purchased my phone from Rogers, and my Sim is from Rogers. I am not sure if it was always locked to rogers, but it just says "no service" and doesn't recognize that I have a rogers sim card. even if network lock is on, shouldn't it still recognize my sim? The methods you have posted have not worked for me. Perhaps I should see if I can get an unlock code from Rogers themselves. If I could do that, would that solve the problem?
Also, if I somehow managed to get an unlock code for my phone, where would I enter it? Would I have to relock my phone to rogers? Could someone explain how I would do that?

Did you try a factory reset from the settings?

MikeyMike01 said:
Did you try a factory reset from the settings?
Click to expand...
Click to collapse
I have done a factory reset before, but i'll try doing it right now...see what happens.

ok I just did a factory reset...still telling me there is no sim inserted even though there is..any other ideas?

Alright so finally everything is showing as "OFF" including Network Lock but it still will not recognize my SIM. i did another factory reset but still no luck. Any other ideas??

What does it say in your APN Settings?

Can't access APN settings. infact, just going into "mobile networks" gives me "insert SIM card" even though it is already well-inserted

Sorry - I meant to say mobile networks - brain fart
[EDIT] The only thing i can think of would be to check the pins that contact the sim card... see if those somehow got damaged. Also check to ensure they are clean, blow out the sim card holder and if needed give the pins a wipe to clean them up and try again. If all else fails, try to get your hands on another sim from the same carrier and see if it works. If a different sim works, then yours is hosed most likely...

It's okay guys I managed to solve things in the end! thanks for all your help tho

rofl, it was backwards ey?

zeusx64 said:
rofl, it was backwards ey?
Click to expand...
Click to collapse
No way...

How did you end up resolving the problem? What ended up being the fix?

zeusx64 said:
rofl, it was backwards ey?
Click to expand...
Click to collapse
I wonder...I just couldn't bring myself to pose the question

for self-pride(not that I have any left after spending god knows how many hours searching in a hex editor for non existent damn unlock codes) I refuse to state how i resolved my issue -______________-; (cough). but THANK YOU ALL for your support anyways! I have definitely definitely learned from this horrible mistake.

bet it was inserted backwards

[Q] cannot use *#7465625# after CM9 mod

I just upgrade my Captivate to CM9 ICS from GB. When I enter *#7465625# to check the lock status. Nothing happens. I remember it worked fine when I did this prior to the upgrade. Is it nornal? or did I break anything?
Thanks.

bigboy0723 said:
I just upgrade my Captivate to CM9 ICS from GB. When I enter *#7465625# to check the lock status. Nothing happens. I remember it worked fine when I did this prior to the upgrade. Is it nornal? or did I break anything?
Thanks.
Click to expand...
Click to collapse
You didn't break anything . Pretty much all the special codes I've ever used stops working on ICS and JB. That being said I'm guessing you're wanting to check your GPS lock status. Download GPS Test from the play store and that should show you everything you'll ever want to know about your lock status.

I might not be very clear in my question, Sorry.
I actually want to vertify if my phone is locked or unlocked after the upgrade; like using *#06# to review the IMEI.

bigboy0723 said:
I might not be very clear in my question, Sorry.
I actually want to vertify if my phone is locked or unlocked after the upgrade; like using *#06# to review the IMEI.
Click to expand...
Click to collapse
I wasn't able to find a good solution for this either (did an unlock a couple weeks ago). I had to just try it with a SIM card from a phone on another network.

Once unlocked ---- Always unlocked.
And the reason those USSD Codes won't work...basically from what lil I know...is because they are either Samsung ussd codes or Carrier Specific Codes and therefore you need to be on a Stock Firmware for them to work (like m1batt1 was pointing out). --- Although some may by chance work.

There is a flashable zip that will restore the *#*#2263#*#* code on the Cappy which let's you change modem frequencies but I don't think it restores that code. Browse through the Slim threads. I'm on my phone and cannot link the zip.
Sent from my SGH-I897 using xda premium

Rooting Galaxy s3 mini....

Hi, I posted about this on another thread, but was then told that there is a forum for the S3. I would like to root my S3 mini GT-18190N, running 4.1.2. Its still under guarantee so it needs to be able to unroot.
Somebody mentioned CydiaImpactor, as it would be the easiest. So I installed to my mac, ticked both usb debugging and accept unknown sources, and ran the program. Within seconds I got an error, 'Error signature bugs unavailable'.......which I posted to the thread, and heard nothing from there and still havent about what that meant. I eventually found out that it means the bug has been fixed. But that is all I got.
I just wondered, what does that mean, does it affect any other ways of rooting? I found another rooting program on here, was given the the stock firmware for my phone but that needs to be unlocked. I did ask about whether the same problem would affect that firmware, but no answer. It seems the advice given on the first thread I started, about taking this to the correct forums needs to be done, which is why I am asking here. Sorry for multiple posting its not spam, its on advice from members on here.
I am a complete novice, never rooted before. So could anybody show me a root system that works for my phone.
Thank you

johnmwc2 said:
Hi, I posted about this on another thread, but was then told that there is a forum for the S3. I would like to root my S3 mini GT-18190N, running 4.1.2. Its still under guarantee so it needs to be able to unroot.
Somebody mentioned CydiaImpactor, as it would be the easiest. So I installed to my mac, ticked both usb debugging and accept unknown sources, and ran the program. Within seconds I got an error, 'Error signature bugs unavailable'.......which I posted to the thread, and heard nothing from there and still havent about what that meant. I eventually found out that it means the bug has been fixed. But that is all I got.
I just wondered, what does that mean, does it affect any other ways of rooting? I found another rooting program on here, was given the the stock firmware for my phone but that needs to be unlocked. I did ask about whether the same problem would affect that firmware, but no answer. It seems the advice given on the first thread I started, about taking this to the correct forums needs to be done, which is why I am asking here. Sorry for multiple posting its not spam, its on advice from members on here.
I am a complete novice, never rooted before. So could anybody show me a root system that works for my phone.
Thank you
Click to expand...
Click to collapse
hi bro, maybe i will buy this s3mini because i notice that it cost only 114.50 euro in my country, more than 50% less than the official price
so...
about root:
you can root the s3mini flashing the firmware with odin
else you can use cydia impactor(be sure to download the latest version from official websites)
i notice that samsung patched the masterkey bug exploited by cydiaimpactor in other galaxy phone but i dont know about s3mini 18190
however i rooted an s3mini of one of my friend s1 months ago, he has never made a firmware update and after he enabled debug usb and installed driver it work! and got root access on his phone, after root you CAN'T do ota update! you an use odin however maybe samsung upgrade to kitkat android 4.4
did you do some firmware update?

-Install TWRP (this video might be of help)
-enter recovery mode and reboot. TWRP will ask you whether you want to root or not

Hi, before I did anything I took a copy of the phone which I have stored on the laptop, windows 7. Then with CWM rooted the phone, and installed a ROM I found. The first time it didnt work, so I had to find another ROM, and install that. This ROM works but its not from my Carrier, which is EE/Orange. The Base version ends in AMJ2, which I dont seem to be able to find to get the correct ROM. The Build Number I have which is the ROM is DMod v6. It works, but its causing problems with Samsung. I have given hope of getting back to the original, but if I could get it to work with EE, it would be better. DModv6 is a US based ROM.
I hope I have explained it ok, its the first time I have done this, so not sure. Please ask for more details.
Sorry it took me so long to answer, have not been very well.
Thank you for your help

What do you mean by it not working with EE/Orange? What functionality do you not have?
Sent from my GT-I8190 using xda app-developers app

Mermaid Man said:
What do you mean by it not working with EE/Orange? What functionality do you not have?
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
As I have already mentioned, its a US based ROM, which only recognises T-Mobile UK. My phone keeps loosing the connection all the time. and I have to reconnect. T-Mobile UK is the US version of T-Mobile even though we have T-Mobile in the country, but without the UK at the end of it. And believe me it is not working properly. The phone itself does work, its faster, the battery life is much longer than when it was on EE. But I am also now having problems with Samsung, they have stopped me from using their software, because they say my phone is not using the correct software.
My first try, I did get Kit Kat running, but without the CAMERA, it wouldnt work. But there again, it was on a US based ROM, and had problems keeping the connection going. That was awesome but without the Camera, it was a bit useless. If I could get a ROM thet had either EE or Orange,

johnmwc2 said:
As I have already mentioned, its a US based ROM, which only recognises T-Mobile UK. My phone keeps loosing the connection all the time. and I have to reconnect. T-Mobile UK is the US version of T-Mobile even though we have T-Mobile in the country, but without the UK at the end of it. And believe me it is not working properly. The phone itself does work, its faster, the battery life is much longer than when it was on EE. But I am also now having problems with Samsung, they have stopped me from using their software, because they say my phone is not using the correct software.
My first try, I did get Kit Kat running, but without the CAMERA, it wouldnt work. But there again, it was on a US based ROM, and had problems keeping the connection going. That was awesome but without the Camera, it was a bit useless. If I could get a ROM thet had either EE or Orange,
Click to expand...
Click to collapse
Hey mate,
Try to use Maclaw's Recovery and KitKat ROM. They work perfectly! Flash Maclaw's recovery first (TWRP) and then wipe cache and dalvik and then flash the kitkat ROM (CM 11).
find them all here: maclaw.pl/downloads/ (stupid 10 post rule for new accounts doesn't let me post the link to HELP the user (johnmwc2)
---------- Post added at 06:32 PM ---------- Previous post was at 06:28 PM ----------
Also the reason that your phone has gone all crazy is because of the ROM you flashed (US version) probably only supports the US frequencies which is why you only get t-mobile network (in some places) as the frequencies change in each location as the phone masts give out different frequencies in different locations according to their surroundings (some frequencies penetrate walls much easier but may not go as far and vice versa).
Im 70% sure the ROM is the problem. the other 30% is me thinking maybe the ROM might not have anything to do with allowing the phone to receive phone signal ( in terms of SOFTWARE not hardware - before anyone tries flaming me). My other instinct tells me maybe its the baseband/modem version thats incompatible witht the US ROM?
just use Maclaws KitKat and TWRP!
They work a treat! :laugh:

pixel 4 xl mobile network problem

need some help here , my pixel 4 xl just updated to jan 2021 update
, post update im unable to connect to mobile network .
already tried hard reset not working
also flashed previous factory image still aint working
is any other thing i can try to solve the problem or im doomed?

capayam said:
need some help here , my pixel 4 xl just updated to jan 2021 update
, post update im unable to connect to mobile network .
already tried hard reset not working
also flashed previous factory image still aint working
is any other thing i can try to solve the problem or im doomed?
Click to expand...
Click to collapse
Who is your provider? Are you using SIM or eSIM? Are you rooted? Did you disable all the Magisk modules before the update? If you forgot that step, have you since disabled all Magisk modules and started over?
While you may be out of commission on the phone side (although, Google Voice would be a good band-aid), you may not be out of commission on the SMS side. Google's text app, Messaging, recently went live with RCS messaging and it can send texts via WiFi.
Incidentally, if it's Google Fi that's giving you fits, the same thing happens to me every time I do a clean install. Fi refuses to connect until I've rebooted two or three times and then the final confirmation comes several hours later.

im in malaysia bought secondhand 1 year ago on grey market , check my sim with another phone , working well on that phone. had been running my phone on regular stock since bought.

capayam said:
im in malaysia bought secondhand 1 year ago on grey market , check my sim with another phone , working well on that phone. had been running my phone on regular stock since bought.
Click to expand...
Click to collapse
Okay, you answered almost none of my questions but it's irrelevant at this point because it sounds like the phone was stolen. If the IMEI is reported as stolen, it's flagged in a database and alerted carriers will shut off the service.
If that's the case, at this point, I'd be more concerned about the police knocking on my door than lack of mobile service. I'd send you over to IMEI.info to verify but I'm guessing I haven't told you anything you didn't already know.

imei number legit not reported or blacklisted, but yeah i think this phone is doomed unless there some magic update resolved this

capayam said:
imei number legit not reported or blacklisted, but yeah i think this phone is doomed unless there some magic update resolved this
Click to expand...
Click to collapse
Why don't you try to reset using the last official 10 firmware (to reset all partitions), then activate through setup, then flash and test a custom rom. This is of course only possible if it's an unlocked bootloader (which you didn't mention) but that's where I'd start especially if it worked before the update. You say is legit and sounds like it worked BEFORE the last update so roll back and then use a custom rom.

GROOVYJOSHCLARK said:
Why don't you try to reset using the last official 10 firmware (to reset all partitions), then activate through setup, then flash and test a custom rom. This is of course only possible if it's an unlocked bootloader (which you didn't mention) but that's where I'd start especially if it worked before the update. You say is legit and sounds like it worked BEFORE the last update so roll back and then use a custom rom.
Click to expand...
Click to collapse
will try it later dude

capayam said:
will try it later dude
Click to expand...
Click to collapse
Unfortunately it's my best guess because I can't reproduce it myself but if it worked prior to the firmware upgrade, it should work by reverting the firmware to the previous firmware in my opinion. I'd take it the step furtherand go with a custom 10 ROM to remove Google firmware updates messing with it in the future (assuming we get it working again).
Interestingly enough, I searched other forums and found other users reporting the same issue. Again, assuming it worked on the previous firmware, I would roll bak to it. Ideally, I would rollback to 10 because I know 10 works (not sure how well it works for you in your local and provider), but thats where I would start. Backup everything you need, then use the last 10 firmware to -w the device and activate then start over.

Why is this posted in development?

shiftr182 said:
Why is this posted in development?
Click to expand...
Click to collapse
who knows