Recently got a G1 off a friend as tempory fix until my replacement X10 arrives.
Phone is currently locked to T-Mobile and I don't have an active T-Mobile sim card.
I've been following the guides on rooting it but I've ground to a halt.
I've flashed the ROM back to the earlier T-Mobile ROM (i.e. before the exploit was patched) as per the guide, but now, because the sim card in the phone isn't active, I can't log in to my google account to get onto the actual handset.
Any possible work around for thid?
Before I flashed it, the ROM that was originally on it allowed me to skip this login step and connect via my Wi-Fi.
I hope you do know, unlocking and rooting are two different things.
Yes.. hence I listed flashing, rooting and sim unlocking as 3 seperate proceedures.
http://forum.xda-developers.com/showthread.php?t=452316 should help you
Although if you sim-unlock it (since you're not a T-mobile customer you would have to buy a code from numerous ebay/craigslist sellers) you could just use your simcard to go through activation (look in the big APN thread for your settings)
That thread is big help, thanks!
Still stuck though, I've got DroidExplorer and all the other software needed installed, however I need to get USB debugging enabled on the phone.
I cannot do this without gaining access to the phone itself.
Going round in circles here!
No one?
Related
Ok first off I apologize for posting this in two places, however not sure this issue is related to the unlocking method or "unbricking" method I used...
Anyway, here goes:
I just acquired a Droid 3. I went ahead and followed the directions from here and obtained an unlock code from moto4unlock.com - $6USD and was sent to me within 30 min.
The first time I followed this thread, every time I inserted my ATT sim (prior to unlocking) I would get the "Unlock Code Screen" where it forces you to input the unlock code. After obtaining the unlock code from above, I went ahead and unlocked. What was surprising, is it did not tell me "Unlock Fail" like this thread stated it would - it actually said unlock successful.
Anyway, moving forward - I went ahead and completed the rest of the steps. After updating the build.prop file, I was able to make calls, and data worked. Well, I had purchased this phone for my mother and wanted to remove my google account and use hers. I didn't realize I couldn't just "remove" the account, instead it was telling me I had to do a hard reset. I went ahead and reset the phone and noticed I couldn't obtain a network signal.
So, I followed these steps to go back to Stock Firmware - I noticed after the install completed, I got a roaming triangle with my att sim and vodafone/verizon sim. (Prior to doing it the first time, I never had a roaming signal so no idea why it has one now)
What I also noticed is when I inserted my ATT sim it did not prompt me to "unlock" the phone again like it did the first time.
So I continued with the rest of the steps. After flashing the new radio and updating the Build.Prop, I get a red circle with a line through it over the signal bars. I've selected GSM/UMTS and no luck...
Any ideas ?
Might be the same flash method, but I would try the fast/easy unbrick method from the development forum. I've used it many times and it has never failed me. Then try the radio flash and build.prop edit again and see if it works. Be sure to make other build.prop edits found in the original unlock thread, since some of those will help set the preferred network on boot to be gsm/umts instead of global.
Now, if the phone is unlocked successfully (by Verizon code, for example, which it seems to be), resetting will not undo this. It's permanent as far as I know. It needs to have a connection to a valid Verizon line while the code is inputted, just fyi. If this is the problem, maybe the code you paid for didn't permanently unlock the device? Many people have had issues unlocking through third party codes, so that's the only reason I bring it up.
I'm not using this tweak anymore since I'm back on Verizon now, but I don't remember ever having the icon you mentioned pop up in the status bar.
Good luck.
Sent from my DROID3 using Tapatalk
not trying to be lazy but just wanna make sure I try the method your suggesting.... can you link me to the one your referring to
Sent from my GT-I9100 using Tapatalk
Hi,
I have a Samsung Captivate that I am trying to unlock. Its out of contract with AT&T and so I called them to get the unlock code. They provided the unlock code. I have a non-AT&T sim card from an overseas trip few years back. I insert this sim card and restart the phone and it asks me to enter the unlock code but am unable to unlock with this code - keep getting "unlock request unsuccessful".
I also got the unlock code for my wife's Captivate from AT&T. Using the same non-AT&T sim card in her phone, when I entered the unlock code provided, I was able to unlock her phone successfully.
Additional info if it helps:
1. My phone is running the official Gingerbread from Samsung whereas my wife's phone is running the original Eclair (with the one OTA update that was initially provided by AT&T).
2. I had rooted both phones when both were running Eclair. However, I lost root access on my phone when upgraded to Gingerbread whereas her phone still has root access. I have not rooted my phone since upgrading to Gingerbread.
3. When I had rooted both phones on Eclair, I had come across a method to inspect the efs/nv_data.bin file manually on this forum to get the unlock code:
Code:
su
busybox grep -E "^[0-9]{8}$" /efs/nv_data.bin
The unlock codes retrieved with above method for both phones are the same as those provided by AT&T recently.
Question is why I am unable to unlock my phone whereas we didnt have any problems unlocking my wife's phone. Would upgrading to the official Gingerbread ROM (non-rooted) from Samsung have anything to do with it?
I had read somewhere that Samsung had encrypted something (bootloader?) with the Gingerbread update for the Captivate that prevented it from being rooted the same way that the Captivate could be rooted with Eclair. Could this be related to why I am unable to unlock my device?
Another thought is whether I would need a different unlock code that works with Gingerbread? I am thinking this is unlikely as my undertanding is that the unlock code is determined by the IMEI number and not the ROM?
Anyway, would appreciate any help/feedback on what I can do to unlock my phone.
Thanks,
-Topper
P.S. Since I tried multiple times to unlock the device unsuccessfully (by entering non-AT&T sim, trying with #7465625*638* code, etc), it shows that I only have one try left to try and unlock the phone.
There are many threads where they describe how to unlock Captivate using manual method i.e. hex editing nv_data.bin file in /efs folder of your phone.
You have to root your phone first if not done so already. Also back up your efs folder on your sdcard and/or your PC. This is a very important step. If you mess up your efs in future(for any reason like while flashing a rom or whatever), you can always restore this folder from your back up. Also back up another copy after you're successful with unlocking that way you can go back to original efs or the unlocked one.
You may use the instructions in this thread to unlock it even though it's for SGS III:
http://forum.xda-developers.com/showthread.php?t=1718665
uhm said:
There are many threads where they describe how to unlock Captivate using manual method i.e. hex editing nv_data.bin file in /efs folder of your phone.
You have to root your phone first if not done so already. Also back up your efs folder on your sdcard and/or your PC. This is a very important step. If you mess up your efs in future(for any reason like while flashing a rom or whatever), you can always restore this folder from your back up. Also back up another copy after you're successful with unlocking that way you can go back to original efs or the unlocked one.
You may use the instructions in this thread to unlock it even though it's for SGS III:
http://forum.xda-developers.com/showthread.php?t=1718665
Click to expand...
Click to collapse
Thanks! I had subscribed to the original thread here but had forgotten all about it. Rooted my phone (still gingerbread) per another thread, unlocked manually as per above thread & confirmed by putting T-Mobile Sim card that both phones work as expected. Glad to see the manual process above still works on sgs iii - so maybe it will work on the exhilarate too.
I have the SG S4 Active (i537) for AT&T, baseband I537UCUAMF3 and tried every method I could find for unlocking and acces to ServiceMode, but nothing really worked.
After reading several post on xda and other forums about this phone, I found this thread: http://forum.xda-developers.com/showthread.php?t=2514607 and done the steps described in these posts. I guess (tried with a T-Mobile not active Sim) I was able to unlock the phone; before doing this method I was getting the message "enter network lock key" when inserting the T-mobile SimCard, after that the phone just boot-up normally without asking for the network key again. I said that I "guess" the phone is unlock because I can't be 100% sure because the SIM card is not active (old one). I will try with an active SIM card and update the info.
In any case I am not responsible for any damages that this method could do to your phone, and I'm not affiliated in any way with the developer of the app.
Please read the posts provided about this thread before trying this method.
Samsung Galaxy S4 Active (I537) AT&T
Baseband: I537UCUAMF3
Android 4.2.2
Note: Before trying the unlock method I inserted a Straight Talk (AT&T compatible Sim card active) and worked like a charm, so if you're using Straight Talk (AT&T compatible Sim) you don't need to unlock the phone.
Update: I tested the unlock with an active T-Mobile SIM and worked perfect
If you can't access Service Mode try using SamIOTA app in playstore, worked for me! (tip: tap on the two options for several times and it will access the app!)
Hi All,
I've trawled through this forum for quite a while and haven't yet found any answers or similar cases to the issue I'm currently having. Here's a summary of where I am at the moment with my i9305 LTE:
- Got a i9305 locked to EE.
- When EE quoted £20+ and 10-20 days for unlock I started looking at altenatives.
- For one of the alternatives, I flashed to get root and I believe I lost my IMEI. I didn't have an efs backup and was unable to restore via stock flashing.
- Luckily, I had a screenshot of my settings so I re-wrote my IMEI using QPST.
- Decided to go for the legit unlock this time so called EE and paid for the unlock code.
- Pre-root, when I put in my unsupported SIM I would get a prompt for an unlock code, but that doesn't have anymore. While waiting for the EE code, I found that when I inserted the unsupported SIM, I would sometimes be able to connect in very specific locations (e.g. certain places outside the house). Wi-Fi works perfectly.
- When the unlock code came, I attempted to enter it by getting to the prompt using "#7465625*638*#". Although, when I enter the code here, it does not accept it (I have an unlock and an unfreeze code, neither work).
- I have trialed the SIM in various other phones and have had no problems with signal at all, the problems arise when I place the SIM in the i9305.
- I have tried changing the modem, so far no luck...
No idea how to go about fixing this... At the moment I can't use it as a phone.
Here is some more info:
Samsung GT-I9305
Nameless Rom 5.0.2
Baseband: I9305XXBLL3
Android Version: 5.0.2
- Should I keep trying different Modems?
- I've tried to verify whether phone is locked or unlocked, but *#7465625# doesn't work, do you know any other ways that I can diagnose sim lock status?
- Will different ROMs or kernels help?
Thanks for any help!
-- UPDATE --
Have flashed back to stock 4.1.1.
I attempted to sim unlock via the *#197328640# approach, but wasn't able to get it to work...
My current next hope is to try and restore my i9305 to the point where it asks for a code to unlock upon entering a new SIM again... Would really appreciate any help, Thanks!
I've still not been able to fix, but will update when I do in case it helps anyone else :good:
Ugh, I am having so many issues with this at the moment. One of those things being that I am using T-mobile as my carrier. I'm stuck on 4.4 at the moment, and need to update it. But, will that relock the phone? How do I re-unlock it if that happens? I've already read that I can't flash the phone to T-mobile ROM, but are there any custom ROMs that you would recommend [I do actually use the S-pen, not sure if any have been updated to where that can still be used.] Lastly, is there any way to get mobile hotspot and tethering to work now that I am using tmobile?
Spikemare said:
Ugh, I am having so many issues with this at the moment. One of those things being that I am using T-mobile as my carrier. I'm stuck on 4.4 at the moment, and need to update it. But, will that relock the phone? How do I re-unlock it if that happens? I've already read that I can't flash the phone to T-mobile ROM, but are there any custom ROMs that you would recommend [I do actually use the S-pen, not sure if any have been updated to where that can still be used.] Lastly, is there any way to get mobile hotspot and tethering to work now that I am using tmobile?
Click to expand...
Click to collapse
I never tried this Rom.
T-Mobile Alliance Lollipop Rom on ATT Note 3
http://forum.xda-developers.com/note-3-att/general/t-mobile-alliance-rom-att-note-3-t3065127 I don't think you would have to worry about any of this as you are using T-Mobile " After the phone came up, I went to settings..general..applications...running .... and found every Tmobile app and cleared cache and disabled them. The real important one here is the Visual Voicemail. Otherwise it will keep on trying to contact Tmobile and then you will get text messages saying there is an error. Thanks @sapps
Wifi Calling is throwing a sim card error (as you would expect). Only problem is it is shown in status bar and lockscreen. I'm sure there is a way to hide it or disable it. I just haven't had a chance to figure it out."
Rooted i747 said:
I never tried this Rom.
T-Mobile Alliance Lollipop Rom on ATT Note 3
http://forum.xda-developers.com/note-3-att/general/t-mobile-alliance-rom-att-note-3-t3065127 I don't think you would have to worry about any of this as you are using T-Mobile " After the phone came up, I went to settings..general..applications...running .... and found every Tmobile app and cleared cache and disabled them. The real important one here is the Visual Voicemail. Otherwise it will keep on trying to contact Tmobile and then you will get text messages saying there is an error. Thanks @sapps
Wifi Calling is throwing a sim card error (as you would expect). Only problem is it is shown in status bar and lockscreen. I'm sure there is a way to hide it or disable it. I just haven't had a chance to figure it out."
Click to expand...
Click to collapse
But it's the N900A, so it's the AT&T version. Won't that brick the phone if I put the tmobile ROM on it? That's what I've read in other threads on here anyway. [Honestly I shouldn't write when I'm tired, or I would have explained this better.]. Basically, I bought an unlocked AT&T phone. A Note 3 to be exact. It's stuck on 4.4 but can upgrade to lolipop. Nothing I try will let me upgrade the normal way. I'm not sure how to upgrade it without relocking the SIM card somehow. Or is the simcard already semi-locked and that's why it's giving me the error? I also can't even find a AT&T specific rooting guide for this phone. I saw every other carrier except AT&T, does that even make a difference? And are there any ROMs that can return S-pen programs after I install them, or should I just stop at rooting if I want that? If so, I just really want to upgrade to lollipop and root the phone. I would like my mobile hotspot and wifi calling to work, but I suppose I can make do with hangouts.
Spikemare said:
But it's the N900A, so it's the AT&T version. Won't that brick the phone if I put the tmobile ROM on it? That's what I've read in other threads on here anyway. [Honestly I shouldn't write when I'm tired, or I would have explained this better.]. Basically, I bought an unlocked AT&T phone. A Note 3 to be exact. It's stuck on 4.4 but can upgrade to lolipop. Nothing I try will let me upgrade the normal way. I'm not sure how to upgrade it without relocking the SIM card somehow. Or is the simcard already semi-locked and that's why it's giving me the error? I also can't even find a AT&T specific rooting guide for this phone. I saw every other carrier except AT&T, does that even make a difference? And are there any ROMs that can return S-pen programs after I install them, or should I just stop at rooting if I want that? If so, I just really want to upgrade to lollipop and root the phone. I would like my mobile hotspot and wifi calling to work, but I suppose I can make do with hangouts.
Click to expand...
Click to collapse
It won't brick you phone. It's a T-Mobile Rom that's been ported for AT&T Note 3. After you flash the Rom, you have to Odin the N900A_OC1_ALL_Other_Stock_Partitions.tar.md5 using Odin's PDA slot. As far as rooting what you have now, just use Towel root https://towelroot.com/ (install on phone like any other app) and click "make it rain". Install Supersu, busybox and Safestrap. OR use Kingo Root http://www.kingoapp.com/ (Kingo Root will install supersu for you). The reason it won't upgrade to Lollipop is you have a T-Mobile sim card in it. It needs a AT&T sim card (I have AT&T and can't upgrade mine unless the sim card is in the phone). If you just want a rooted Lollipop Rom, but it's AT&T http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2 You know since you're on T-Mobile you have to go into settings>more networks>mobile networks>access point names and change it to T-Mobile's APN. I would just root it and put the T-Mobile Alliance Lollipop Rom on ATT Note 3 on it. I gave it a try yesterday and it does have T-Mobile apps on it, just not for me. Just remember to change the APN to T-Mobile's ( just write down the one you using now).