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] Is there a way to root using a different carrier's stock image?

I have the Samsung Galaxy S3 (T-Mobile) and it includes all the unneccesary carrier bloatware. Since I'm not a T-Mobile customer, I would prefer not to have all the extra T-Mobile applications, so I was wondering when rooting with Odin 3, instead of using T-Mobiles stock image, can I possibly use a different carriers, like WIND Mobile.
The instructions I got were from:
http://forum.xda-developers.com/show....php?t=1771687
When I tried using the WIND image on my T-Mobile device, rooting fails!
Any suggestions?

new2s3 said:
I have the Samsung Galaxy S3 (T-Mobile) and it includes all the unneccesary carrier bloatware. Since I'm not a T-Mobile customer, I would prefer not to have all the extra T-Mobile applications, so I was wondering when rooting with Odin 3, instead of using T-Mobiles stock image, can I possibly use a different carriers, like WIND Mobile.
The instructions I got were from:
http://forum.xda-developers.com/show....php?t=1771687
When I tried using the WIND image on my T-Mobile device, rooting fails!
Any suggestions?
Click to expand...
Click to collapse
Never use another carrier's ROM unless it specifically states it will work with another carrier. What you need to do is root with the official T-Mobile image that has root/super user injected into it.
Once you are done with that, get Titanium Backup free version from the market and uninstall what you don't want.
Use this thread which is in the Android Development forum for T-Mo: http://forum.xda-developers.com/showthread.php?t=1949687
That is the thread I started with when I rooted my T-Mo S3.

Technically what you're trying to do can be done. As said above, you shouldnt flash another carriers rom as the bootloaders and modem would most likely brick if the flash was successful(although i think odin checks this and the flash would fail anyway).
That said the system+kernel alone would be ok to flash. I actually have a package made just for this purpose posted here. See if that does what you want. Only thing is it was made for someone on moblicity although from what i remember the system was the same for both wind and moblicity(no branding or carrier specific apps). I can do this with WIND if need be just shoot a PM.

Carrier switching

Hi, my girlfriend has a note 2 that was originally from rogers, she has gone over to bell and i was wondering would it be possible to flash the stock bell firmware on her rogers phone or would this end up with some type of damaging effect. any help would be great. her phone is the sgh-i317m

Really, the only difference between the roms is the carrier's apps. Changing roms doesn't improve connections.
What app is she missing? Or what does she hope for by changing? I always go out of my way to remove any carrier branded apps!

There's no advantage to running the bell firmware over the Rogers. Unless you need the bell apps, but those are on the play store anyway.
1] ROGERS • T0LTE-CAN • SLIM 4.3
2] ••waiting for my N3••

I find the rogers modem better than bell one
Sent from my SGH-I317M using xda app-developers app

The firmware is the same, and so is the modem. What differs between the two is the CSC, carrier specific content. You'd have to check if Fast Dormancy and HD Voice still work, but those are about the only two tweaks that changing CSC might affect.
I don't know for sure about fast dormancy, but HD Voice required a factory reset to activate in some circumstances.
There is a code to change the CSC from another already available on the phone, but I don't remember it off the top of my head (it's been posted on here a few times already). Caution, it does wipe the phone without warning.

ckavvouras said:
Hi, my girlfriend has a note 2 that was originally from rogers, she has gone over to bell and i was wondering would it be possible to flash the stock bell firmware on her rogers phone or would this end up with some type of damaging effect. any help would be great. her phone is the sgh-i317m
Click to expand...
Click to collapse
If the phone already rooted you don't need to flash firmware again to get Bell's rom. Just go to playstore and install the app from link below. All ypu need to do is change CSC thats all.
https://play.google.com/store/apps/details?id=com.manniakk.cscselector

Cool thanks I appreciate everyone's help, The main thing i was worried about was flashing different radios and messing that up but since i can just install the bell apps from the play store i see no reason to really mess around with it. thanks

Right. All North American carriers use the latest modem.

Bell to rogers and back again

I recently had to downgrade my rom so I could use of of the unlocking methods I found here on xda. I went over to sammobile and downloaded the appropriate rom ( android 4.1) for my carrier and phone, I flashed it using mobile odin, turns out it was a rom for a rogers phone even thought the description and even the file ended with BMC and not RWC which indicated it was for bell, any case I unlocked the phone all went back an restored the system image from cwm all was fine till about 24 hours ago when my phone started acting up very glitchy and i decided it was time to to a full clean up and resort the stock rom. I again mobile odin to flash stock but for what ever reason the apps being loded on to the phone are for rogers carrier. I am using I317MVLBMA3_I317MOYABMA3_BMC which by all indication tells me its for bell, so what the hell is going on ? I have downloaded this and flashed it both from mobile odin and from my pc and ever time its a rogers rom. any help would be great.

They're the same roms. All Canadian versions are the same except the system carrier apps included. Your glitches probably happened from something else. Is there any app that you've installed in the last 24 hours or have you done something unusual on your phone in the last 24 hours?

koreancanuck said:
They're the same roms. All Canadian versions are the same except the system carrier apps included. Your glitches probably happened from something else. Is there any app that you've installed in the last 24 hours or have you done something unusual on your phone in the last 24 hours?
Click to expand...
Click to collapse
they are for the most part the same roms with minor differences for instance the rogers rom displays a 4g icon where as the bell displays a HSDPA icon or something lol, and also the carrier bloatware is not the same bell has its own bloat, even the browser launches to rogers website. I even removed the bloat with titanium and when i flashed the new rom it came right back so i have no idea why this ghost apk files are coming from.

update, I downloaded the telus firmware and tried to flash that with odin, flashed fine but rogers apps are still there. can not return to bell stock firmware, any help would be great.

Download csc changer from play and set it for bmc whats funny is mine is rogers but when I flash it I get all bell stuff
Sent from my SGH-I317M using Tapatalk

32dave said:
Download csc changer from play and set it for bmc whats funny is mine is rogers but when I flash it I get all bell stuff
Sent from my SGH-I317M using Tapatalk
Click to expand...
Click to collapse
worked out great thanks a lot man, I was racking my brain why this was not working.

[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.