Related
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
Hello, I have been having some odd problems with my data connection lately and Verizon wants me to get a new SIM card from them. My data connection constantly drops for no reason and it is starting to bother me quite a bit.
The only problem is that I have rooted and unlocked the bootloader. I checked around but there does not seem to be a re-lock guide for the Verizon GN.
Do I need to re-lock it for them to give me my new SIM card or can I just keep it like it is when I take my phone in for the new card? I am sure that my phone is not having the problem as my brother's data connection keeps dropping constantly as well, but I am going to go through the steps that Verizon wants me to.
There's an app called bootunlocker that will lock/unlock boot loader easily to remove the unlocked locked pad on the Google boot screen.
When taking your phone in it depends on the rep looking at your phone if you need to be stock or not. Some care some don't.
I'd go stock to ensure less hassle from the rep. Some users have gone as far as deleting files that may show evidence they have unlocked and rooted their device from the sdcard.
Use this to go completely back to stock 4.0.4 but keep in mind everything will be gone from your sd card its like starting from scratch, i like to use this every once in a while just to clean up everything I download.
http://forum.xda-developers.com/showthread.php?t=1743939
No. No you don't need to unroot or relock or anything like that. Just take out the old SIM and put in the new.
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..
Hi All,
I'm looking for some guidance. I have a VS986 on Vz 10B rooted. Overall, the phone works OK with good battery usage but I still suffer from the occasional missed touches, even though I've done the tweaking, and sometimes when downloading lots of files on WiFi I have to toggle the WiFi as DNS appears to stop.
My question is, should I stay on 10B and wait for the Boot unlock, or upgrade to 13B?
Your help is greatly appreciated.
-Kev
ktraub said:
Hi All,
I'm looking for some guidance. I have a VS986 on Vz 10B rooted. Overall, the phone works OK with good battery usage but I still suffer from the occasional missed touches, even though I've done the tweaking, and sometimes when downloading lots of files on WiFi I have to toggle the WiFi as DNS appears to stop.
My question is, should I stay on 10B and wait for the Boot unlock, or upgrade to 13B?
Your help is greatly appreciated.
-Kev
Click to expand...
Click to collapse
I'm kind of in the same boat - rooted 10B and avoided OTA's hoping for bootloader unlock which, from past reports, won't work on anything but 10B.
I don't have any touchscreen issues and use DNSSet to avoid slow WiFi speeds at home, so I'm in no rush to upgrade. If your touchscreen and WiFi issues are frustrating you, and as there's no way to tell if/when Verizon bootloader unlock will happen, I'd say update. If you can live with those issues, I'd wait because it seems like having an unlocked bootloader means as much to you as it does for me..
I just know with my luck, I'll update from 10B and then immediately the VZ bootloader unlock will drop and it'll only work on 10B and I'll be kicking myself for updating. Let me know if you update so I can come back in a couple days to learn how to unlock the bootloader on 10B
Icculus760 said:
I'm kind of in the same boat - rooted 10B and avoided OTA's hoping for bootloader unlock which, from past reports, won't work on anything but 10B.
I don't have any touchscreen issues and use DNSSet to avoid slow WiFi speeds at home, so I'm in no rush to upgrade. If your touchscreen and WiFi issues are frustrating you, and as there's no way to tell if/when Verizon bootloader unlock will happen, I'd say update. If you can live with those issues, I'd wait because it seems like having an unlocked bootloader means as much to you as it does for me..
I just know with my luck, I'll update from 10B and then immediately the VZ bootloader unlock will drop and it'll only work on 10B and I'll be kicking myself for updating. Let me know if you update so I can come back in a couple days to learn how to unlock the bootloader on 10B
Click to expand...
Click to collapse
Icculus760, you echo my feelings exactly. I have the same luck as you with timing.
I guess I'll just try to wait it out until I get too frustrated with the issues.
I was also wondering about the security fixes, if there are any, in 13B. Do you know if there are any?
ktraub said:
Also wondering about the security fixes, if there are any, in 13B. Do you know if there are any?
Click to expand...
Click to collapse
Verizon's site says "The following improvement has been made: Android security patches" but doesn't give any more information, so the short answer is no.....I have no idea what actual security fixes they may have implemented
ktraub said:
Icculus760, you echo my feelings exactly. I have the same luck as you with timing.
I guess I'll just try to wait it out until I get too frustrated with the issues.
I was also wondering about the security fixes, if there are any, in 13B. Do you know if there are any?
Click to expand...
Click to collapse
Which method you guys used to root 10b, I am on 10b but yet to root as we don't have a kdz of 10b to restore if I make anything wrong during the root process
I haven't noticed any security changes but 13b has definitely improved system stability. I had so many issues with lag and missed taps on 11a, so if you have those issues you won't regret updating to 13b!
I finally took the courage to go to 13B because holding out with 10B for custom ROM support is vaporware. So basically, I had a 10B rooted. Needed to get to 13B with root. So what I did was follow the two guides below to get me to 11A (doesn't matter if rooted or not rooted on 10B, it will make the LG G4 updated to 11A non-rooted):
http://www.verizonwireless.com/support/knowledge-base-105457/
http://www.verizonwireless.com/support/knowledge-base-164676/
Then onto 13B:
http://forum.xda-developers.com/verizon-g4/help/how-to-upgrade-to-13b-via-kdz-t3274036
Then get rooted 13B image by either:
http://forum.xda-developers.com/verizon-g4/general/vs98613b-saved-image-rooted-t3258794 (for stock and rooted 13B)
http://forum.xda-developers.com/verizon-g4/general/vs986-rooteddebloated-t3256814 (for debloated and rooted 13B)
Flashing the rooted 13B by:
http://forum.xda-developers.com/g4/...-tmo-vzw-intl-variants-soon-root-lg-t3164765/
with the following command here (but note to modify the image's file name for flashing): http://forum.xda-developers.com/showpost.php?p=62028523&postcount=2
I've been reading around and mostly want to know everything for this for that time when CM becomes stable.
Anyways:
Do you lose Verizon network functionality? By this I really mean, calls, SMS, SMS, voice mail, and 4G LTE.
When converted...just act like it's the US unlocked model when flashing ROMs? Do I need to flash the Verizon radio?
I'm confused...and the final question..
To convert it requires a SuperCID and then RUU flash, right? I've seen Sprint owners do it and one Verizon owner, but the instructions were all very unclear to me.
Thanks!
Answers are on post #4, tested it out after being sure of how to do this. If you're lazy, click here...
I've converted my VZW branded 10 to U.S Unlocked. I am NOT using the phone on Verizon network, so I can only answer part of your questions.
To convert, I changed my cid to SuperCID (22222222) and flashed the latest stock RUU.exe from HTC.com for U.S Unlocked. Pretty simple.
I can't tell you if the phone would work on Verizon network, but I would assume it would with a radio flash to get the basic things you mentioned working, as outlined in:
http://forum.xda-developers.com/verizon-htc-10/how-to/vzw-how-to-unlocked-model-vzw-t3376743
Haven't yet flashed any non-stock roms, but I can't imagine why this would be a problem. Also the CM thread has some people who flashed the Unlocked firmware on a VZW phone and got CM working.
I haven't and probably will never try, but I see advanced feature breaking after you do this like wifi calling and the like. but ive also heard all that's different is the radio. but theres different settings unlocked and hidden between the two that may give issues also.
so just give it a shot if you really want. the worst that would happen is you would need to switch back to Verizon firmware.
Tested it out...
Tarima said:
I've converted my VZW branded 10 to U.S Unlocked. I am NOT using the phone on Verizon network, so I can only answer part of your questions.
To convert, I changed my cid to SuperCID (22222222) and flashed the latest stock RUU.exe from HTC.com for U.S Unlocked. Pretty simple.
I can't tell you if the phone would work on Verizon network, but I would assume it would with a radio flash to get the basic things you mentioned working, as outlined in:
http://forum.xda-developers.com/verizon-htc-10/how-to/vzw-how-to-unlocked-model-vzw-t3376743
Haven't yet flashed any non-stock roms, but I can't imagine why this would be a problem. Also the CM thread has some people who flashed the Unlocked firmware on a VZW phone and got CM working.
Click to expand...
Click to collapse
afuller42 said:
I haven't and probably will never try, but I see advanced feature breaking after you do this like wifi calling and the like. but ive also heard all that's different is the radio. but theres different settings unlocked and hidden between the two that may give issues also.
so just give it a shot if you really want. the worst that would happen is you would need to switch back to Verizon firmware.
Click to expand...
Click to collapse
Changed my CID to SuperCID (22222222).
Got the latest Unlocked U.S. FW from the HTC Dev site (RUU EXE) and flashed it.
Flashed a Verizon radio in fastboot. (The same one used to make the actual U.S. Unlocked variant work on Verizon)
Flashed TWRP in fastboot.
Formatted my data.
It booted without issue.
Followed this guide (though, on initial boot it showed 4GLTE active BUT no bars (line through them).
After following the guide, I rebooted.
Testing functions:
Calls: Functional and no delays.
SMS: Functional and fast.
MMS: Functional and fast.
Data connection: Functional.
Behavior after reboot: Starts again with the bars crossed off, eventually comes up and working though. Works after that, calls too. Takes about 45 seconds to connect.
Thing to note: It seems as if my signal strength is lessened. Though, this could easily be placebo, weather, etc. It's 1:31AM and I've never paid attention to it before.
Network comes up as 3107 instead of Verizon Wireless.
HTC software updates seem to be broken, it gives a corrupted error. I'm locked/S-OFF, so dunno.
Final deduction: It seems to functional and all, without hiccup most likely. It takes longer to connect than the stock VZW FW does of course, but after the boot it seems fine.
I'm done testing this for now, but if anyone is wondering yeah go for a it. It seems to be fine besides a slower initial connection. Excited for CM to become stable, then I'll play with this some more.
Ariac Konrel said:
Changed my CID to SuperCID (22222222).
Got the latest Unlocked U.S. FW from the HTC Dev site (RUU EXE) and flashed it.
Flashed a Verizon radio in fastboot. (The same one used to make the actual U.S. Unlocked variant work on Verizon)
Flashed TWRP in fastboot.
Formatted my data.
It booted without issue.
Followed this guide (though, on initial boot it showed 4GLTE active BUT no bars (line through them).
After following the guide, I rebooted.
Testing functions:
Calls: Functional and no delays.
SMS: Functional and fast.
MMS: Functional and fast.
Data connection: Functional.
Behavior after reboot: Starts again with the bars crossed off, eventually comes up and working though. Works after that, calls too. Takes about 45 seconds to connect.
Thing to note: It seems as if my signal strength is lessened. Though, this could easily be placebo, weather, etc. It's 1:31AM and I've never paid attention to it before.
Network comes up as 3107 instead of Verizon Wireless.
HTC software updates seem to be broken, it gives a corrupted error. I'm locked/S-OFF, so dunno.
Final deduction: It seems to functional and all, without hiccup most likely. It takes longer to connect than the stock VZW FW does of course, but after the boot it seems fine.
I'm done testing this for now, but if anyone is wondering yeah go for a it. It seems to be fine besides a slower initial connection. Excited for CM to become stable, then I'll play with this some more.
Click to expand...
Click to collapse
I was the guinea pig for this in regards to Sprint, but you've seem to partially answer a question I had.
I know that the Verizon and US Unlocked use the same model ID, but the Sprint and internal do not. Leaves me wondering if I could just run the RUU for my Sprint phone.
Ariac Konrel said:
Changed my CID to SuperCID (22222222).
Got the latest Unlocked U.S. FW from the HTC Dev site (RUU EXE) and flashed it.
Flashed a Verizon radio in fastboot. (The same one used to make the actual U.S. Unlocked variant work on Verizon)
Flashed TWRP in fastboot.
Formatted my data.
It booted without issue.
Followed this guide (though, on initial boot it showed 4GLTE active BUT no bars (line through them).
After following the guide, I rebooted.
Testing functions:
Calls: Functional and no delays.
SMS: Functional and fast.
MMS: Functional and fast.
Data connection: Functional.
Behavior after reboot: Starts again with the bars crossed off, eventually comes up and working though. Works after that, calls too. Takes about 45 seconds to connect.
Thing to note: It seems as if my signal strength is lessened. Though, this could easily be placebo, weather, etc. It's 1:31AM and I've never paid attention to it before.
Network comes up as 3107 instead of Verizon Wireless.
HTC software updates seem to be broken, it gives a corrupted error. I'm locked/S-OFF, so dunno.
Final deduction: It seems to functional and all, without hiccup most likely. It takes longer to connect than the stock VZW FW does of course, but after the boot it seems fine.
I'm done testing this for now, but if anyone is wondering yeah go for a it. It seems to be fine besides a slower initial connection. Excited for CM to become stable, then I'll play with this some more.
Click to expand...
Click to collapse
Does your volte work ? Something you can try is flash Viper10 and select as a verizon model instead of the unlocked version, this will add get you on global mode and I think will fix your signal issues. You list your on Viper10 just dirty flash it again selecting verizon version and give it a try. If it does not help you can always just dirty flash again and go back selecting the unlocked version. Just do a back up before doing this and you will covered if you just want to restore the back up. From my experience this might help just do not try running a custom kernel for the verizon version if you converted to the unlocked as your camera may not work and keep forcing close but you can run a custom kernel for the unlocked if you converted to unlocked. My recommendation would be to run the Elite kernel as I have had really good luck with the Elite kernel on the Htc 10 and I think theirs is what I run well on my Motorola nexus 6 also.
Ariac, regarding OTA software updates on the phone, I think you get that "corrupt" message because you flashed a different radio and twrp. Might be worth flashing the original Unlocked radio/recovery back and see if it at least detects the latest update. If it does, you'll also need to remove superCID to be able to take the update.
I reflashed the RUU yesterday, removed superCID and I was able to take the OTA.