Develop Bugs

[Q] Updating an unlocked Captivate Glide I927 to ICS

Hi,
I did make this query earlier on another thread (I promise that thread will be deleted in the next 14-15hrs, but I need to keep it up till that time), but I have now been suggested to re-word and describe the situation properly, before attempting a knee-jerk update and getting my phone locked.
I bought my Captivate Glide I927 from an Indian website, which promised "unlocked for all GSM networks" handsets. The phone came in the original AT&T box, and works properly for voice and text on both Airtel and Tata Docomo networks. Google Play works as well, but internet browsing thru any browser isnt working. The phone came with GB 2.3.6 installed (I927UCKL1). However, I wasnt provided with any "unlock" code, as I have been reading about in this forum (required in case the phone gets locked after an update). The specific seller I bought from on the site is no help at all regarding either the unlock code or an ICS update.
I have downloaded the new firmware "I927UCLJ3_I927ATTLJ3_ATT.zip" from samfirmware, and also have Odin and CWMR on my PC (Basically everything to update my Captivate Glide to ICS). I have also asked around in the reliable-looking half-a-dozen mobile repair shops in my locality, but they cannot guarantee anything, much less a particular model-specific solution for the ICS update while keeping the handset unlocked.
So, my queries are:
1. What do I do to get the internet browsing working on the same setup (GB 2.3.6)
2. If I do flash the ICS update (I927UCLJ3_I927ATTLJ3_ATT.zip), will the handset get locked??
3. If it does get locked, what are the methods to get it unlocked again??
Any replies and solutions are appreciated.
Thank you.

Check out this post by Phoenix84188, it has a patched libsec-ril that allows the bit-flip method to work with the LJ3 ICS ROM.
Bit more involved, but you could also modify the CSC files and flash that modified image instead.
As for internet browsing, did you check your APN settings?

abalsy said:
Hi,
2. If I do flash the ICS update (I927UCLJ3_I927ATTLJ3_ATT.zip), will the handset get locked??
3. If it does get locked, what are the methods to get it unlocked again??
Any replies and solutions are appreciated.
Thank you.
Click to expand...
Click to collapse
Hard to tell if it will lock, better to be prepared.
When I flashed the I927UCLJ3_I927ATTLJ3_ATT over the existing Gingerbread on the Rogers version of the phone SGH-i927R, it got network locked.
Thus on first boot it was requesting the Network Code. The store I bought it originally unlocked from provided me the code.

After upgrading mine from GB -> ICS (back to) -> GB Official, I then "Unlocked" it with an Unlock code. Then flashed up to the latest official and LiteROM, CM10 preview, etc, and never had to unlock again.

Dont know whether it helps- I too bought from a Indian website. It came unlocked. I flashed to ICS when the ROM came up first (subsequently it was removed and the re-released). I used CWMR to fix the keyboard light and Titanium Backup to remove the bloatware. I dont have any issues with my handset so far other than the occassional deep sleep issue (it goes off from standby and has to be battery resetted)
Ameyam

Dont worry i boughy my glide unlocked from ebay...im from central america and i flashed the ICS update, then flashed LiteRom, CM10 and now Pacman and my phone is still unlocked!!

AT&T unlocks from ebay are the cheapest one's to buy. I would suggest to find out first if they have an unloack code to be on the safer side. Although 99.99% they'll have an unloack code. Flash the ICS update and if it asks you for a code then go buy it.
My handset got locked once when originally updating to ICS and i bought the code from http://cellunlocker.net

Official updates (through Odin or Kies) have a tendency to relock Samsung devices. To the best of our knowledge, all current custom ROMs require you to first flash the official ICS update, so this is a problem. Have your unlock code on hand.
NEVER buy an unlocked device where the seller won't give you the code for it. Weird things happen.

roothorick said:
NEVER buy an unlocked device where the seller won't give you the code for it. Weird things happen.
Click to expand...
Click to collapse
That's good advice. Thank you.

---

ameyam said:
Dont know whether it helps- I too bought from a Indian website. It came unlocked. I flashed to ICS when the ROM came up first (subsequently it was removed and the re-released). I used CWMR to fix the keyboard light and Titanium Backup to remove the bloatware. I dont have any issues with my handset so far other than the occassional deep sleep issue (it goes off from standby and has to be battery resetted)
Ameyam
Click to expand...
Click to collapse
I had the same issue. I surfed the web but didn't find any solution. Than I instaled litekernel and I don't remember why but I used interactive governor and it helped. Hope this will be the help for everybody, cause many are having the same problem

[Q] 2 years down, My play is jus a psp

Hi all, Its been almost 2 years since i did an OTA update on my play and bricked it. Using the first patch that came out to fix this problem of phone not booting, i "destroyed" the bootloader or something or RadioRom and my phone does not accept any sim. it was originally unlocked.
Has anyone come up with a way to revive the play to make calls or something. cos its really depressing having a phone jus lying there wasting away, only to be brought out when needed for navigation or games.
Someone please helppppppppppppppppppppppppppppppp

Assuming your radio/sim is in working condition, I don't particularly see how bricking your phone can cause the phone to act like that. Have you tried flashing the stock firmware on again after it was bricked? And have you tried reunlocking the phone and putting on a custom rom/kernel?

jayact~ said:
Assuming your radio/sim is in working condition, I don't particularly see how bricking your phone can cause the phone to act like that. Have you tried flashing the stock firmware on again after it was bricked? And have you tried reunlocking the phone and putting on a custom rom/kernel?
Click to expand...
Click to collapse
about 2 years back, shortly after this phone came out, a problem was noted with OTA updates on unlocked bootloader.
The phone was bought "sim-free" or factory unlocked depending on which nomenclature is correct.
With an unlocked bootloader, the OTA update caused the phone to go dead.
in a haste to get the phone working again, a patch was released which broke the radio rom but got your phone to boot again. i believe the initial patch was released by BLAGUS.
well that killed my radio and now, no sim inserted works.
I reinstalled the stock firmware on it. tried several variants from different regions in the hope that it might work. was getting help from Wazz, Blagus and Bin4ry but seems they've moved on to more important projects now.

2 years ago, I would've brought my phone to the carrier. While your warranty would have been voided, you still should've been able to tell them that it is THEIR fault that it's not working since it was their OTA update that broke the phone. At the very least, they should've been able to get you a discount on a replacement Xperia Play, or at least I think they would have if they wanted to keep a happy customer.

Waqas said:
about 2 years back, shortly after this phone came out, a problem was noted with OTA updates on unlocked bootloader.
The phone was bought "sim-free" or factory unlocked depending on which nomenclature is correct.
With an unlocked bootloader, the OTA update caused the phone to go dead.
in a haste to get the phone working again, a patch was released which broke the radio rom but got your phone to boot again. i believe the initial patch was released by BLAGUS.
well that killed my radio and now, no sim inserted works.
I reinstalled the stock firmware on it. tried several variants from different regions in the hope that it might work. was getting help from Wazz, Blagus and Bin4ry but seems they've moved on to more important projects now.
Click to expand...
Click to collapse
Alright, I understand now. I wish I knew more, so I could help you out.
Was this the patch you used? I believe I used this ftf to relock my bootloader when my phone was bricked after I accepted an OTA update, just as you did. My radio never had any issues, though.. That said, my phone was sim-locked, since I have the R800x, so maybe that has something to do with it..

[Q] Modem Help after 4.3 Flash with new board

My trusty N7100 had an allergic reaction to saltwater about 3 weeks ago. It only got the top of the phone but it shorted out and would freeze on the boot screen until the battery was pulled. I took it to a few shops here in the Philippines but wasn't much they could do. From the tear down vids, etc, I figured it needed a new board. I took it to Hong Kong for New Year's and a friend found a shop that was able to get it up and running for $100 but couldn't get any info on what work was done. The phone was still rooted/unlocked and worked on my prepaid HK data sim as well as my local carrier when I returned to the Philippines two days ago. But it was showing as "Modified" in device status and wouldn't do OTA updates. I decided to flash it from 4.1 to 4.3 with ODIN and now its "Not Registered on Network".
Looks like a common error for the 4.3 upgrade but after hours of research, I'm in the dark as to the best path forward. IMEI, s/n, etc., in device status have remained unchanged and show out of the box numbers (the one thing I did record. Based on the below I am trying to figure out if I should be flashing Globe Philippines rom's or HK rom's... or just need to change to a HK modem?
Before the dunking:
Philippines Globe phone. I bought it in Oct2012, rooted it to unlock but that's about it. Unfortunately it was my first Android phone and I didn't record the system specs anywhere. I have some Titanium BU's but no images (doh)
After resuscitation in Hong Kong, everything was all good (but I didn't make a recovery image of this either = doh x2):
Android 4.1.1
Baseband N7100XXALJ2
Kernel: 3.0.31-343940
Build: JR003C.N7100ZSALJ7
I flashed the ROM with what I thought was the recommended 4.3 stock rom for Philippines Globe. I have Wi-Fi but can't connect to mobile networks. I tried three different sims for two different carriers.
Android 4.3
Baseband: N7100XXUEMK1
Kernel: 3.0.31-2229877
Build: JSS15J.N7100XXUEML3
This one has got me stumped as I'm not sure what flavor my phone is after its organ transplant. Now that its mostly alive, I could take it back over to the boys at the mall but that would be too easy. Thanks for any help. I've been a lurker on here since I first looked at buying this phone and have learned a lot from this site.
I'm running ODIN via Virtualbox with a Kubuntu host and W7 guest.

Sorry for long winded question... really just need point in right direction. Try switching modems? If so which one? Or just reflash with HK stock ROM? Thanks!

I'm not so sure if this will work but try to reflash again but before that wipe data 1st then followed by wipe cache partition and wipe dalvik cache.

Thanks! Before I saw this reply, I tried flashing to latest HK version of 4.3 - N7100ZSUEML1 with no success but didn't wipe caches. Rooting failed this morning but I read up on here that doing the factory reset is supposed to flash the davlik. After reading this, I did the factory reset/wipe and then wiped the cache and reflashed ZSUE with ODIN3. After I got the language switched from Chinese to English, I was hopeful as I went through set up process of "new" phone but no dice. I was going to try to flash back to N7100ZSALJ7 but I didn't back it up and can't scare up that ROM on the net. I have found a HK 4.1.2 version (N7100ZSDMA4) that I may try but after three days of solid computer time, I'm getting tempted to just take it down to the guys at the mall and see what they can do. Being a Kubuntu user for several years, I'm used to solving my tech problems on the net but still low on the Android food chain and committed cardinal sin #1, always have a viable backup. There is a lot of great information on here and the net in general but with so many variants of phones, ROM's, regions, etc., it is hard to find the right needle in this haystack!
I'm down but not out so if anyone has anymore suggestions, I'm all ears. IMEI, etc., are still in tact. I'm wondering if I'm running into the regional issue. I was reading up on the Note 3 and thought I remember seeing something that said Sammy might roll regional coding backwards along with Knox. With an "official" 4.3 running on this Note 2, I've got Knox now. So turning a new ROM on in the Philippines for the first time with a HK board could possibly be the issue but I think that's a dark horse as its unlocked and my new Note 3 isn't having regional issues after I unlocked it (but I unlocked the Note 2 with root and unlocked the Note 3 the easy way - via $ and the IMEI for unlock code. I'm missing something easy. I've got good signal strength. I can see all the usual suspects here under Mobile Networks/Network Operators - Globe, Sun, Smart. It even says I'm registered on Globe when I click on it. But when I try for mobile data or to make a call, "Not Registered on Network".
Thanks for any and all help.

[Q] T-Mobile branded S3 somehow became AT&T.

When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.

GraphicsApathy said:
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
Click to expand...
Click to collapse
Can you go to your phone's settings => about device and check what the firmware settings are? Let's see what you have under firmware version, baseband version & build number. If possible, you may post a screen shot. Did you say you returned to stock by wiping your phone? Hardly seems likely and you would have probably needed to flash some firmware. Would you recall what you flashed?

Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.

GraphicsApathy said:
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
Click to expand...
Click to collapse
It's definitely on AT&T firmware. Apologies if I sound like I'm doubting you but are you certain it had T-Mobile firmware when you acquired it? I'd guess it was probably already an AT&T phone. If you bought it in the secondary market, there could have been some previous repairs involving parts swaps. Your safest bet may be to leave it as is and unlock for you use on T-Mobile. Trying to force on T-Mobile firmware now could result in a brick. As it is on 4.1.1, you can easily free unlock it by following the well tested method you'll find elsewhere in this forum.

No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.

GraphicsApathy said:
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
Click to expand...
Click to collapse
There could have been a previous JTag operation involving forced firmware installation on the MB. I've seen previous hybrid firmware involving one or other partition belonging to a different model - e.g. the modem, bootloader or something else but not the complete system.
Yes, that's the unlock method I was referring to. You won't get any confirmation that the process worked at the end. However, if you did it correctly, you would know it worked when you insert a non-compatible SIM card and it works. You should also be able to install T-Mobile apps especially the Wi-Fi calling app which is a really nice feature of T-Mobile.

I'm getting it microSIM'ed tomorrow. I'll see how that goes.
UPDATE: Successfully obtained and installed T-Mobile microSIM. Still wish to replace AT&T boot animation and bloatware with T-Mobile's, though.

GraphicsApathy said:
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
Click to expand...
Click to collapse
OK. I'd be interested in knowing the outcome but I'll be surprised if it isn't unlocked already. Did some further research and there have been some reports of people successfully 'flashing' AT&T firmware on T-Mobile phones, and vice versa. Not sure why this should happen and conventional logic suggests the result should be a hard brick which is indeed the most common outcome. I'll also suggest you boot into download mode and see the information under bootloader. If the device has a T-Mobile bootloader, it may be possible to remove the OS via custom recovery and re-flash T-Mobile firmware.

Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction

GraphicsApathy said:
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
Click to expand...
Click to collapse
If download mode info shows secure bootloader enabled, the phone is, to all intents and purposes, now an AT&T phone. Attempting to flash T-Mobile firmware may likely result in a brick which would require a JTag fix. I was hoping download mode would show it still had a T-Mobile bootloader which could have allowed for safe firmware installation but this does not appear to be the case. Likely the motherboard was previously replaced or it suffered a brick and AT&T firmware was JTagged on. Either way, it would be safer to leave it as is.

Bummer. I'll leave it as is then. Thank you for all the help.

Sim network unlock PIN (t0lte n7105)

My n7105 was running good on 4.4 latest. I run on lineage os nightly official first for few days but switched to unofficial with ril stock blob due to network issues. It ran good for around 15 days however one day it random ly started connect/disconnecting mobile network. I notice and restarted phone. Now phone is asking sim network unlock PIN. I reflashed last working back up with twrp. Same problem. I switched to official, same problem. I reflashed samsung firmware with odin but same problem. I tried all methods like galaxysimunlock, galaxy s unlock, woodoo but no success. Dr.fone not tried as not sure of results.
Anyone have idea what wrong could have happened. Please suggest solution. I purchased from a reseller 4 year back. Not knowing it was factory unlocked or not. But i upgraded it from 4.1 to 4.3 and then 4.4 without issue with samsung OTA.
Sent from my Lenovo A2010-a using Tapatalk

Hi! Ive a similar problem. I just installed the latest nightly on my i9305. Then at first boot i entered the sim pin and the phone constantly kept asking me for the pin, during phone setup. I disabled sim security from a different phone and inserted into the samsung again. Then lightlyOS booted and did setup fine, but now I wanted to make a call and noticed my sim is locked, theres an error when I search for a mobile network and I cannot set sim securty on again as the screen stays green, nomatter where I push it. looks like a major error to me. Google lists some of these errors for lineageOS within the last 7 days. Mabye theres a fix soon or a workaround?! anybody any idea about it? cheers!

Unlock resolved
Hello,
found solution.
Had same trouble with my Note 2 N7105 after using LOS 14.1 around 3 weeks.
Starting with random Mobile network misses and ending with requesting "SIM Network unlock pin".
Mobile was never locked and working since years with different roms, providers and networks.
Restoring old backups CWM and TWRP without succes.
Flashing stockrom still shows the lock.
Now flashed with odin oldest stockrom 4.1.1 of t-mobile I can found
https://www.usp-forum.de/downloads.php?do=file&id=1172
and doing the unlock according
https://forum.xda-developers.com/showthread.php?t=2014982&page=1
Can confirm, that using this removes the lock also after flashing newer roms afterwards.
Keep in mind to keep the waittimes 30 seconds and 1 minute minimum. Use your watch!!

retrocruiz said:
Hello,
found solution.
Had same trouble with my Note 2 N7105 after using LOS 14.1 around 3 weeks.
Starting with random Mobile network misses and ending with requesting "SIM Network unlock pin".
Mobile was never locked and working since years with different roms, providers and networks.
Restoring old backups CWM and TWRP without succes.
Flashing stockrom still shows the lock.
Now flashed with odin oldest stockrom 4.1.1 of t-mobile I can found
https://www.usp-forum.de/downloads.php?do=file&id=1172
and doing the unlock according
https://forum.xda-developers.com/showthread.php?t=2014982&page=1
Can confirm, that using this removes the lock also after flashing newer roms afterwards.
Keep in mind to keep the waittimes 30 seconds and 1 minute minimum. Use your watch!!
Click to expand...
Click to collapse
Followed procedure
Done
Now Enjoying 4.1.1 t mobile
Sent from my GT-N7105 using Tapatalk

Reflash custom after stock rom
dipeshxda6969 said:
Followed procedure
Done
Now Enjoying 4.1.1 t mobile
Click to expand...
Click to collapse
You have not to stay at 4.1.1, it is possible to reroot, install custom recovery an use old backup or flash of higher level custom Roms.
I am back on LOS 14.1 actual 20170804, hoping that accidentally locking did not reoccure after some weeks of usage.
Easiest way for me is using Android Unified Toolkit from Skipsoft:
https://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761
.

retrocruiz said:
You have not to stay at 4.1.1, it is possible to reroot, install custom recovery an use old backup or flash of higher level custom Roms.
I am back on LOS 14.1 actual 20170804, hoping that accidentally locking did not reoccure after some weeks of usage.
Easiest way for me is using Android Unified Toolkit from Skipsoft:
https://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761
.
Click to expand...
Click to collapse
Done
Now running on Los 14.1 official
Sent from my GT-N7105 using Tapatalk

LOS unofficial have specific problem of sim lock. I reflashed LOS Unofficial (earlier downloaded, now it has already taken down) after unlocking again after few days it again locked. Now returned on samsung rom 4.4 as it runs without any issue.
Sent from my GT-N7105 using Tapatalk

Intermediate relocks not at mine
Sad to hear, that relocks occure.
Knocking on wood, my N7105 is now running since nearly 3 weeks without relocking on LOS 14.1 Version 20170804.

Hello,
I have been experiencing this problem for a long time (Cyannogen).
Unfortunately for me, the network is unlock maximum 2 months, minimum one day, before locking.
I restore the official 4.4.2 ROM every month with TWRP to unlock the SIM network with my code, then I reinstall the latest version of LOS.

dipeshxda6969 said:
Followed procedure
Done
Now Enjoying 4.1.1 t mobile
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
can i used this method to unlock other phones as well? like huwei mate 9?

Pretty messed up bug. Lineage OS sim locked up a sim unlocked. (how is that even possible!?)
Even after getting the unlock code (for free), I was still unable to unlock the phone until I flashed a factory ROM. Even then it was a PIA cause ODIN was failing at the radio flash portion. I was lucky as hell the phone booted the factory ROM after I flashed TWRP back.
How is this not listed in big bold letters for the rom?