Database Info

verizon update to unlock bootloader a lie???

i happened to find this while just looking online although it seems like there are arguments against it and for it accross the table... im neutral as id much rather have an unlocked bootloader i am simply just posting this so everyone can see it and maybe share something to prove or disprove
http://www.gottabemobile.com/2012/07/16/verizon-wont-unlock-galaxy-s-iii-bootloader/
this says they wont release an update to unlock the s3

beeholtz said:
this says they wont release an update to unlock the s3
Click to expand...
Click to collapse
Verizon never made any sort of promise that they would unlock the bootloader. The rumor got started a month ago from transcripts of chats with ill-informed customer service reps who didn't know a bootloader from a barnacle. They chose to lock it, and they will not willingly reverse that decision. When our bootloader gets unlocked, it will be through the fine efforts of communities like this one. Depending on the type of exploit, I might not be surprised if Verizon then pushes an update to relock the bootloader, as has happened with some HTC phones in the past.
In general, never take the word of a CSR without a fair bit of skepticism, especially if it conflicts with VZW's official statements.

lazarus2405 said:
Verizon never made any sort of promise that they would unlock the bootloader. The rumor got started a month ago from transcripts of chats with ill-informed customer service reps who didn't know a bootloader from a barnacle. They chose to lock it, and they will not willingly reverse that decision. When our bootloader gets unlocked, it will be through the fine efforts of communities like this one. Depending on the type of exploit, I might not be surprised if Verizon then pushes an update to relock the bootloader, as has happened with some HTC phones in the past.
In general, never take the word of a CSR without a fair bit of skepticism, especially if it conflicts with VZW's official statements.
Click to expand...
Click to collapse
Correct me if I'm wrong but once and if the bootloader is unlocked we can just stay on that bootloader (unlocked) even if verizon does try to re-lock it correct? In a sense similar to s-off
Sent from my SCH-I535 using Tapatalk 2

niv3d said:
Correct me if I'm wrong but once and if the bootloader is unlocked we can just stay on that bootloader (unlocked) even if verizon does try to re-lock it correct? In a sense similar to s-off
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
IMO - Its just safe practace not to take any OTA updates until after the Devs got them fixed. Verizon could patch their own bootloader if they needed to - via an OTA. So, yes, you could stay unlocked (once it is unlocked anyway), so long as you stay away from OTAs .

i have a thunderbolt and in 9 days when i have an upgrade available on my account will be getting the s3. on my thunderbolt after i rooted i never even had to block updates i just straight up never got ota updates. is there a setting in the s3 that ill need to check or uncheck a box to not receive them after i root?

why are so many folks concerned about ota updates? The day one roots his/her phone OTA should be forgotten. The devs here will have all the updates we can possibly achieve and in alot more timely fashion.

droidstyle said:
why are so many folks concerned about ota updates? The day one roots his/her phone OTA should be forgotten. The devs here will have all the updates we can possibly achieve and in alot more timely fashion.
Click to expand...
Click to collapse
**** yeah!
Sent from my SCH-I535 using Tapatalk 2

if you actually took the time to read my post you would have noticed that i asked if there is a way to NOT RECEIVE OTA UPDATES as opposed to asking about receiving them. i will post that question in q and a when i get the phone thanks anyways

beeholtz said:
if you actually took the time to read my post you would have noticed that i asked if there is a way to NOT RECEIVE OTA UPDATES as opposed to asking about receiving them. i will post that question in q and a when i get the phone thanks anyways
Click to expand...
Click to collapse
I did read your post...my apologies since that post was not 100% directed towards you...I kind of hijacked your thread posting that for others to read lol. There has been 100 threads on here about "will I lose ota if I root".

A big cellphone company lied to us? It can't be. Haha sorry for the sarcasm but the way this phone has been going I think an unlock will come through the developers over the big companies. That means we'll have to pay up on that bounty.
Sent from my SCH-I535 using xda premium

ya my bad too i didnt mean to be a **** about it. i had some ahole customer i dont like helping come up today. fixing their computers and network just makes about anything else sound like more fun. im just stoked to get the phone soon but i also am getting it knowing about having a locked bootloader and the possibility of all those little quirks and issues that some people have and some dont. On my thunderbolt i rooted it not long after i got it and have flashed roms and kernels and radios etc until i find one i really like at the time. I'm figuring once the dev. edition comes out people will get it and verizon will then do the same thing on the next big deal phone that comes out in however many months.

I swear at this point, they're just sitting back in their chairs and cackling madly. Biggest trolls ever.

I think the "ota" talk only references people who are stock and take ota, get said-bootloader "fixed" by vzw, then want to mod afterwards. Then a new/different method will have to be used, whether it be Odin/rollback/whatever is come up with.
People already unlocked and rooted will be fine.
Sent from my Galaxy S3 using Tapatalk 2

I can't say i'm terribly surprised, Verizon seems content to violate whatever they want for their benefit. Just need to put the pressure to them.

I am not even concerned about the boot loader anymore. You can flash kernels with kexec cwm(6010), Odin new modems and the roms that synergy, bean and Nos are producing are just fantastic. Developers will find a way and there are some great ones on the SG3.
Sent from my SCH-I535 using xda premium

Rather doubt it
Doubt verizon will unlock the bootloader
anytime soon. For now we are left to
root use custom stock roms with some
themes or leave Verizon.
Cheers,
INC > TB > S3

azbobs said:
For now we are left to
root use custom stock roms with some
themes or leave Verizon.
Cheers,
INC > TB > S3
Click to expand...
Click to collapse
This is simply not true...there is plenty of aosp dev going on! we have 4 cm10 roms, 1 aokp jb rom, 1 paranoidandroid rom...the bugs these roms do have are not related to the locked bootloader. Its the same issues across multiple devices. 5min of research would of yielded these results...

Verizon is NEVER going to unlock the bootloader. Ever. You can quote me on that.
Sent from my SCH-I535 using xda premium
---------- Post added at 12:23 PM ---------- Previous post was at 12:22 PM ----------
droidstyle said:
This is simply not true...there is plenty of aosp dev going on! we have 4 cm10 roms, 1 aokp jb rom, 1 paranoidandroid rom...the bugs these roms do have are not related to the locked bootloader. Its the same issues across multiple devices. 5min of research would of yielded these results...
Click to expand...
Click to collapse
Ya and they all break your phone and wipe out vital information like imei and/or permanently break data.
Sent from my SCH-I535 using xda premium

It's the Big Red SideShow starring Mr. Smoke & Mirror's Himself Lowell McAdams.

Verizon can burn in hell. I
Off topic, but is the volume really this quiet on this phone? I came from the OG like 2 weeks ago and it was literally double the decibels that this thing is putting out. I've heard about the volume+ app but is that the only way to increase volume? I'm still stock but plan on rooting n roming soon, perhaps one of them contains that dsp manager that cm7 base used to include?
Sent from my SCH-I535 using xda app-developers app

[Q] Verizon OTA Update - 5/30/13

I read on cnet last night that Verizon would be sending an update for all GS3 users and, sure enough, I was prompted for the update for an update morning. (5/30/2013)
I am running stock 4.1.2 rooted.
Does anyone know if this is safe for me to apply? Will I lose root?
Thanks!

yep
You will lose root and if you have a custom recovery (twrp for instance) it will be overwritten. You will also get a "update failed" message. However, the update actually will succeed. You can reroot the same way you did before (unlock bootloader, root, install custom recovery if desired). I was surprised that the OTA was even available for rooted/custom folks. There will be a couple new apps installed, one dealing with CallerID which will force your 4G and WiFi to both be on - freezing that new app will fix that issue too, search the forums for details.
Goddrick said:
I read on cnet last night that Verizon would be sending an update for all GS3 users and, sure enough, I was prompted for the update for an update morning. (5/30/2013)
I am running stock 4.1.2 rooted.
Does anyone know if this is safe for me to apply? Will I lose root?
Thanks!
Click to expand...
Click to collapse

gozirra said:
You will lose root and if you have a custom recovery (twrp for instance) it will be overwritten. You will also get a "update failed" message. However, the update actually will succeed. You can reroot the same way you did before (unlock bootloader, root, install custom recovery if desired). I was surprised that the OTA was even available for rooted/custom folks. There will be a couple new apps installed, one dealing with CallerID which will force your 4G and WiFi to both be on - freezing that new app will fix that issue too, search the forums for details.
Click to expand...
Click to collapse
How are you surprised about the OTA being available for rooted phones? You don't make any sense with that comment as the update is just that an update. Verizon doesn't know which customers have rooted their device just that you have a device that needed to be updated.

Because thats the way it always was back when I had my original Incredible? A lot of people were surprised that the update was available to them, I'm not a minority here. No reason to be rude.
jmxc23 said:
How are you surprised about the OTA being available for rooted phones? You don't make any sense with that comment as the update is just that an update. Verizon doesn't know which customers have rooted their device just that you have a device that needed to be updated.
Click to expand...
Click to collapse

gozirra said:
Because thats the way it always was back when I had my original Incredible? A lot of people were surprised that the update was available to them, I'm not a minority here. No reason to be rude.
Click to expand...
Click to collapse
I am not being rude just stating the fact that Verizon doesn't know your phone is rooted in fact all companies don't know what you did to your phones until something bad happens to it. I will also add that the update will be pushed regardless if you're rooted or not the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.

jmxc23 said:
I am not being rude just stating the fact that Verizon doesn't know your phone is rooted in fact all companies don't know what you did to your phones until something bad happens to it. I will also add that the update will be pushed regardless if you're rooted or not the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.
Click to expand...
Click to collapse
Funny I did not see him mention anywhere that Verizon knew anything. His experience with a previous phone was that for some reason after rooting etc. his phone did not receive OTA updates. Whatever the reason, instead of being rude, you could have simply helped him understand like you finally did : "... the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.".

ghostboa said:
Funny I did not see him mention anywhere that Verizon knew anything. His experience with a previous phone was that for some reason after rooting etc. his phone did not receive OTA updates. Whatever the reason, instead of being rude, you could have simply helped him understand like you finally did : "... the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.".
Click to expand...
Click to collapse
Okay I have corrected myself like you have so eloquently posted I don't see the need to defend him if I already like you stated told him finally the reason. I already know that I should have done it sooner and like I normally do correctly fall back and respond in a normal tone. I unlike others am self aware of what I do and make an effort to correct any wrongs that I have caused. I don't filter myself when I post my thoughts so they can come across
as rude depending on your sensitivity level the difference is that I don't insult people nor belittle them in any way. I can only imagine how you or anyone will react if I was a total jackass.

ok then
Thanks for the explanation. follow-up question - if Verizon doesn't "know" then what is with the "unauthorized software discovered, call Verizon" popup that so many people have reported? Or the infamous yellow triangle? I assumed (yeah I know the cliche) that Verizon in fact DID "know" otherwise that wouldn't have happened. Simple mistake based on past experience, sorry.

As a side note.. If you have Titanium you can freeze SDM 1.0 and you won't get those updates

gozirra said:
Thanks for the explanation. follow-up question - if Verizon doesn't "know" then what is with the "unauthorized software discovered, call Verizon" popup that so many people have reported? Or the infamous yellow triangle? I assumed (yeah I know the cliche) that Verizon in fact DID "know" otherwise that wouldn't have happened. Simple mistake based on past experience, sorry.
Click to expand...
Click to collapse
This is completely unrelated to OTAs though. That warning is solely because of the secure bootloader on the Verizon GSIII. That warning is built into the system to pop up whenever you try installing software to the phone without having the prerelease bootloader in place. Verizon and Samsung intentionally made this model GSIII more difficult to install custom software onto or to make it a more secure device, depending on how you look at it. It's a business decision at the end of the day.
Sent from my SCH-I535 using Tapatalk 4 Beta

Probably business related as they don't want to be the first company to have an worldwide malware problem on their devices.

ghostboa said:
...you could have simply helped him understand like you finally did : "... the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.".
Click to expand...
Click to collapse
That's the key (at least in my experience with HTC phones). I can't remember the name of the file, but it was one file that you could rename and the phone would not check or ignore OTA updates that were pushed by the carrier.

i downloaded the update the other day by mistake as it bricked my phone. im rooted only and stock. i know its going to keep forcing the update thru, is there anyway i can get the update to go thru successfully without bricking my phone again?

You didn't brick your phone at least not a hardware brick.

TouchWiz 4.3 update - WHY

Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"

galets said:
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
Click to expand...
Click to collapse
Because you can't. Once you take the 4.3 OTA, you're stuck with it.

McDastardly said:
Because you can't. Once you take the 4.3 OTA, you're stuck with it.
Click to expand...
Click to collapse
I have to say, it was incredibly disappointing that Samsung decided to sneak device lock-down disguised as a software update. Very lame. I was under impression that Samsung does value community building mods for its overpriced phones, understands the value of such community. Apparently, they don't. I agree with someone who said it will be the last Samsung device he purchased, I think it's time for me to join the boycott.
But coming back to the issue at hand: lets imagine I was lucky enough not to trust Samsung to deliver me an update and instead took a hacked one. Is there any reason whatsoever to stay on 4.3? And by that I mean:
- does 4.3 solve some problem in original firmware, that anyone should care about?
- does 4.3 implement some new feature, which was not in original 4.1 firmware that I should be excited about?

galets said:
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
Click to expand...
Click to collapse
What features were taken out? Anything that can be replaced with better apps on the market shouldnt count. In my opinion the new stock task manager makes it worth it.
---------- Post added at 01:17 PM ---------- Previous post was at 01:11 PM ----------
Well if I could go back in time I would have just waited for a custom 4.3 tw rom. But at least I don't feel the need to flash a new rom every day now.

ThePagel said:
What features were taken out?
Click to expand...
Click to collapse
At this time, my biggest issue is that codes do not work, and i cannot get into hidden menu, so no QPST. I'm on PagePlus, so updating PRL is a manual process, and without putting phone into modem mode I cannot do that.
There are a few other annoying things, such as: can't turn off warning against increasing volume on headphones (i think there's some add-ons which let you do it though)

galets said:
At this time, my biggest issue is that codes do not work, and i cannot get into hidden menu, so no QPST. I'm on PagePlus, so updating PRL is a manual process, and without putting phone into modem mode I cannot do that.
There are a few other annoying things, such as: can't turn off warning against increasing volume on headphones (i think there's some add-ons which let you do it though)
Click to expand...
Click to collapse
I can understand your annoyance with the hidden menu being gone. But that wasn't a "feature" it was a "hidden menu" after all and with root there are ways to get rid of the volume warning. That bugs the crap out of me as well but not to the point to change it yet.... YET!

galets said:
I have to say, it was incredibly disappointing that Samsung decided to sneak device lock-down disguised as a software update. Very lame. I was under impression that Samsung does value community building mods for its overpriced phones, understands the value of such community. Apparently, they don't. I agree with someone who said it will be the last Samsung device he purchased, I think it's time for me to join the boycott.
Click to expand...
Click to collapse
Nah, Samsung hasn't been overwhelmingly developer friendly for awhile. There's a bit of dislike for them due to Exynos processors.

Additionally, it wasn't that sneaky. The phone was intended to have a locked bootloader from the beginning. It was expected that the update would patch the loophole we found from the leaked aboot step. That's why it was mentioned multiple times to not accept the 4.3 update in case it locked the bootloader.
Samsung hasn't been developer friendly for a long time. Anytime you take an OTA update you can expect it to prevent the use of custom firmware unless a trusted source says it doesn't.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Additionally, it wasn't that sneaky. The phone was intended to have a locked bootloader from the beginning. It was expected that the update would patch the loophole we found from the leaked aboot step.
Click to expand...
Click to collapse
I still maintain it's been sneaky. The boot loader was not patched for a long time, you even get an icon which indicates custom firmware. Many folks understood it as if Samsung quietly endorses modding. The S3 has had a reputation of phone friendly for modders. Many purchased this very model specifically because they intended to mod it. Also don't forget, people look up to tinkerers, so a lot of sales were made because "this guy who knows the phones has samsung"

galets said:
I still maintain it's been sneaky. The boot loader was not patched for a long time, you even get an icon which indicates custom firmware. Many folks understood it as if Samsung quietly endorses modding. The S3 has had a reputation of phone friendly for modders. Many purchased this very model specifically because they intended to mod it. Also don't forget, people look up to tinkerers, so a lot of sales were made because "this guy who knows the phones has samsung"
Click to expand...
Click to collapse
Samsung isn't as nice as you think. HTC will often allow you to unlock the phone by signing an agreement that you are voiding the warranty. Verizon has had a history of locking bootloaders that other carriers wouldn't.
This bootloader lock is mostly Verizon's implementation anyway. They're the ones who changed the bootloader and patched our loophole. Other devices on the 4.3 OTA update (sprint and T-Mobile) still have unlocked bootloaders.
The custom icon was only stating we had a custom recovery installed. Didn't have anything to do with firmware checking.
Sent from my SCH-I535 using Tapatalk 2

It's hard to call it sneaky if you look back at the thread that was all about waiting for the update it was repeated daily, if not a couple of times a day that if the OTA hits your phone not to take it because it would lock your bootloader. Taking my early upgrade from the Bionic this didn't really surprise me lol. It just clinched it that, I'll maintain my unlocked bootloader and rom away until its time for my next phone, which will be a nexus or amazingly enough a moto if i can let go of my bionic anger lol....

If you purchase a phone to be modded, after you mod it, why would you ever take a manufacturer OTA?
Sent from my SCH-I535 using xda app-developers app

galets said:
I have to say, it was incredibly disappointing that Samsung decided to sneak device lock-down disguised as a software update. Very lame. I was under impression that Samsung does value community building mods for its overpriced phones, understands the value of such community. Apparently, they don't. I agree with someone who said it will be the last Samsung device he purchased, I think it's time for me to join the boycott.
But coming back to the issue at hand: lets imagine I was lucky enough not to trust Samsung to deliver me an update and instead took a hacked one. Is there any reason whatsoever to stay on 4.3? And by that I mean:
- does 4.3 solve some problem in original firmware, that anyone should care about?
- does 4.3 implement some new feature, which was not in original 4.1 firmware that I should be excited about?
Click to expand...
Click to collapse
Samsung probably does value it, however we need to keep in mind it doesn't HAVE to be their fault.
Android is released from Google, then Samsung gets a hold of it, adds their own skin/features/framework, then hands it off to Verizon, where Verizon locks everything down and adds crap things to it. Verizon is EXTREMELY against community mods and such.
We need to figure out if other carriers are having issues with the 4.3 rollout (if it exists) then we might be able to decide who dropped the ball
SGS3 running Android 4.4 KitKang

XdrummerXboy said:
Samsung probably does value it, however we need to keep in mind it doesn't HAVE to be their fault.
Android is released from Google, then Samsung gets a hold of it, adds their own skin/features/framework, then hands it off to Verizon, where Verizon locks everything down and adds crap things to it. Verizon is EXTREMELY against community mods and such.
We need to figure out if other carriers are having issues with the 4.3 rollout (if it exists) then we might be able to decide who dropped the ball
SGS3 running Android 4.4 KitKang
Click to expand...
Click to collapse
Its samsung. Every version of the s3 is locked on 4.3 the only difference is nobody is complaining about it on the other forums. samsung wants to be able to have there phones used in government agencies and the like so they locked the phone down. I accidentally upgraded and haven't complained once because its not that big of a deal. I am just not buying from samsung from now on (unless they make the tablet that folds into a phone). Someone can correct me if I am wrong but everything I have read says every s3 on 4.3 has been locked down. If you do say I am wrong please give me a link so I can educate myself.

XdrummerXboy said:
Samsung probably does value it, however we need to keep in mind it doesn't HAVE to be their fault.
Android is released from Google, then Samsung gets a hold of it, adds their own skin/features/framework, then hands it off to Verizon, where Verizon locks everything down and adds crap things to it. Verizon is EXTREMELY against community mods and such.
We need to figure out if other carriers are having issues with the 4.3 rollout (if it exists) then we might be able to decide who dropped the ball
SGS3 running Android 4.4 KitKang
Click to expand...
Click to collapse
Ahhh I forgot about the Knox or whatever they call it. I thought you were able to switch between using it and not though.
But I guess maybe they have to make sure EVERYTHING is secure, then build the "non" secure stuff on top of that framework.
SGS3 running Android 4.4 KitKang

XdrummerXboy said:
Ahhh I forgot about the Knox or whatever they call it. I thought you were able to switch between using it and not though.
But I guess maybe they have to make sure EVERYTHING is secure, then build the "non" secure stuff on top of that framework.
SGS3 running Android 4.4 KitKang
Click to expand...
Click to collapse
You can still root the OTA by using saferoot. Once rooted, superSU will ask if you want to disable knox. You can then load safestrap which will allow you to load other 4.3 roms and multi-boot your phone etc. Read ALL the threads on saferoot and safestrap before you install them.
Sent from my SCH-I535 using xda app-developers app

galets said:
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
Click to expand...
Click to collapse
App access to notifications. That is my killer app for 4.3

Help with Rooting 4.4.2

So I had 4.1.2 on my phone and rooted with no problems, but now that I updated to 4.4.2 and lost my root... I cannot for the life of me figure out how to get root back again. Anyone help me please?

Well I got impatient and found something called towelroot and root checker now says I am rooted, but I cannot get CWM installed. Using both Odin 307 and 309 I boot into downloading mode and odin fails and I see red error saying "secure check fail: recovery"
Any help?

MortTheBeast said:
Well I got impatient and found something called towelroot and root checker now says I am rooted, but I cannot get CWM installed. Using both Odin 307 and 309 I boot into downloading mode and odin fails and I see red error saying "secure check fail: recovery"
Any help?
Click to expand...
Click to collapse
If you go to settings > about phone build and based band ending in ML1 NC1 NE1 have looked bootloader a meaning you can't install custom rims .. You will have to root / install safestrap and boot custom tw Roms since you are on 4.4.2 you have to wait for a 4.4.2 tw rom I don't think any are out yet
Sent from my iPod touch using Tapatalk

MortTheBeast said:
Well I got impatient and found something called towelroot and root checker now says I am rooted, but I cannot get CWM installed. Using both Odin 307 and 309 I boot into downloading mode and odin fails and I see red error saying "secure check fail: recovery"
Any help?
Click to expand...
Click to collapse
Since we can't install custom roms, I found this xposed module called Wanam Xposed. I'm not even rooted yet but I was going to with towelroot. Anyway, it lets you customize certain looks of the stock rom without modifying anything. You need the Xposed Framework first and then you can get Wanam Xposed.

Mon431 said:
Since we can't install custom roms, I found this xposed module called Wanam Xposed. I'm not even rooted yet but I was going to with towelroot. Anyway, it lets you customize certain looks of the stock rom without modifying anything. You need the Xposed Framework first and then you can get Wanam Xposed.
Click to expand...
Click to collapse
Yea I am just going to be as patient as possible till I can unlock the bootloader. How long does it usually take for the tech geniuses to figure this kind of stuff out? I'm wishing I hadn't updated 4.4.2 now... (slaps forehead)

MortTheBeast said:
Yea I am just going to be as patient as possible till I can unlock the bootloader. How long does it usually take for the tech geniuses to figure this kind of stuff out? I'm wishing I hadn't updated 4.4.2 now... (slaps forehead)
Click to expand...
Click to collapse
Unless if the file leaks from Samsung like it did on 4.1.2, it won't ever get unlocked

Mon431 said:
Unless if the file leaks from Samsung like it did on 4.1.2, it won't ever get unlocked
Click to expand...
Click to collapse
EEEEeeeeek! Don't say things like that! LOL
Anyway... I guess if worse comes to worse, shouldn't a Factory Reset take me back to 4.1.2? And then I would be able to try out one of the 4.4.3 CM Nightly builds

MortTheBeast said:
EEEEeeeeek! Don't say things like that! LOL
Anyway... I guess if worse comes to worse, shouldn't a Factory Reset take me back to 4.1.2? And then I would be able to try out one of the 4.4.3 CM Nightly builds
Click to expand...
Click to collapse
A factory reset will reset your phone like it's new but it'll stay on the same version. For example, if you updated to 4.3 and then did a factory reset, you be on 4.3 but your phone would be reset.

Son of a biscuit lol.... maybe if I dunk in the toilet it will revert back to 4.1.2? LMAO! Man... being impatient really put the screws to myself.

MortTheBeast said:
Son of a biscuit lol.... maybe if I dunk in the toilet it will revert back to 4.1.2? LMAO! Man... being impatient really put the screws to myself.
Click to expand...
Click to collapse
1st rule of rooting...NEVER OTA! Bricks, locked bootloaders, and facepalms will be imminent.
Sent from my SCH-I535 using XDA Premium 4 mobile app

MortTheBeast said:
Son of a biscuit lol.... maybe if I dunk in the toilet it will revert back to 4.1.2? LMAO! Man... being impatient really put the screws to myself.
Click to expand...
Click to collapse
Yeah, once you update to 4.4.2 you're stuck. You will NEVER be able to go back and you'll never be able to flash a custom recovery. It's Touchwiz from here on out for you.
I feel for you, but it's pretty universally known that you don't take OTA's from Verizon OR Samsung because they usually close up loop holes.

sbenson1226 said:
Yeah, once you update to 4.4.2 you're stuck. You will NEVER be able to go back and you'll never be able to flash a custom recovery. It's Touchwiz from here on out for you.
I feel for you, but it's pretty universally known that you don't take OTA's from Verizon OR Samsung because they usually close up loop holes.
Click to expand...
Click to collapse
That seems to be a little presumptuous saying "never". Software is software... which to me means "if there is a will, there is a way", in regards to hacking/cracking it. And if I get that hard pressed to want the ability to tinker with roms I can always just sell the phone and buy one thats not been updated to 4.4.2. All I can say right now being a newb to all this stuff is "lesson learned and stored in memory for future use". :good:

MortTheBeast said:
That seems to be a little presumptuous saying "never". Software is software... which to me means "if there is a will, there is a way", in regards to hacking/cracking it. And if I get that hard pressed to want the ability to tinker with roms I can always just sell the phone and buy one thats not been updated to 4.4.2. All I can say right now being a newb to all this stuff is "lesson learned and stored in memory for future use". :good:
Click to expand...
Click to collapse
It's not really presumptuous, it's the truth. Samsung and Verizon are hell bent on keeping their bootloaders locked down. The S5 hasn't been cracked. The S4 cannot be cracked, after MDK. The S3 cannot be cracked after 4.2.1. The S3 was pure luck because somebody inside of Samsung leaked what we needed. The only way it will ever be cracked is if Samsung themselves hand us the code. Never going to happen again. Sorry, it's the hard truth. If you want to tinker, don't buy a Verizon phone and don't buy a Samsung.

What exactly is even the reasoning behind locking the bootloader? I mean, I know they don't want people messing with their software.. but WHY? Are they not already making their profits by selling the phone? Just can't wrap my head around companies that want to limit a consumers options. That would be like buy a computer with for example Windows 8 on it and being told there is no way to remove it and install Windows 7. If I can have whatever OS I want on my computer... then how is that any different then a phone which nowadays is pretty much a handheld computer.

sbenson1226 said:
It's not really presumptuous, it's the truth. Samsung and Verizon are hell bent on keeping their bootloaders locked down. The S5 hasn't been cracked. The S4 cannot be cracked, after MDK. The S3 cannot be cracked after 4.2.1. The S3 was pure luck because somebody inside of Samsung leaked what we needed. The only way it will ever be cracked is if Samsung themselves hand us the code. Never going to happen again. Sorry, it's the hard truth. If you want to tinker, don't buy a Verizon phone and don't buy a Samsung.
Click to expand...
Click to collapse
Maybe you (or someone else) can explain to me what options if any I have for unlocked bootloader capability for S3 and S4? Like whats the final software version number that still allows unlocking the bootloader, what if any carrier specific options have it unlocked or able to be. Like you mentioned the S5 not being cracked but I read through a thread on here dating back to just this past May and confirming unlocked bootloader for S5 T-Mobile. S5 is out of my price range, but the S3 and S4 I can pick up at a reasonable price... just need the proper information so I can be sure Im not getting something thats going to stick me with a locked boot. Thanks

MortTheBeast said:
What exactly is even the reasoning behind locking the bootloader? I mean, I know they don't want people messing with their software.. but WHY? Are they not already making their profits by selling the phone? Just can't wrap my head around companies that want to limit a consumers options. That would be like buy a computer with for example Windows 8 on it and being told there is no way to remove it and install Windows 7. If I can have whatever OS I want on my computer... then how is that any different then a phone which nowadays is pretty much a handheld computer.
Click to expand...
Click to collapse
Locking the bootloader means added profit on verizons end. You have less access to features that get baked into a custom rom that we bypass, such as free tethering and simply making a device better than stock. Verizon wants this.
The less debloating and access to modified firmware available means they make more money on services people have to pay for.
Verizon will tell you it's better for consumers because it adds to your customer service experience. If you have a problem, and need help, then they are more likely to be able to help you knowing you are not running modified firmware that could give you a less than par experience. They will also add that using unapproved software could negatively impact their network (ie: tethering) and cause problems for other consumers.
There may be some truth in that, but without the ability to flash a new rom you essentially limit your software abilities and limit the life of the phone. It forces people to buy their services and extend their plan more often.
---------- Post added at 01:19 AM ---------- Previous post was at 01:13 AM ----------
The t-mobile variant for both the s3 and s4 have unlocked bootloaders on every device. None of them will work on verizons network. Every Verizon Samsung phone is completely locked down.
The last available firmware that can be unlocked on the S3 is mf1. The s4's is MDK or something but that's way harder to find. There is no unlock method for the s5.
MortTheBeast said:
Maybe you (or someone else) can explain to me what options if any I have for unlocked bootloader capability for S3 and S4? Like whats the final software version number that still allows unlocking the bootloader, what if any carrier specific options have it unlocked or able to be. Like you mentioned the S5 not being cracked but I read through a thread on here dating back to just this past May and confirming unlocked bootloader for S5 T-Mobile. S5 is out of my price range, but the S3 and S4 I can pick up at a reasonable price... just need the proper information so I can be sure Im not getting something thats going to stick me with a locked boot. Thanks
Click to expand...
Click to collapse

MortTheBeast said:
Maybe you (or someone else) can explain to me what options if any I have for unlocked bootloader capability for S3 and S4? Like whats the final software version number that still allows unlocking the bootloader, what if any carrier specific options have it unlocked or able to be. Like you mentioned the S5 not being cracked but I read through a thread on here dating back to just this past May and confirming unlocked bootloader for S5 T-Mobile. S5 is out of my price range, but the S3 and S4 I can pick up at a reasonable price... just need the proper information so I can be sure Im not getting something thats going to stick me with a locked boot. Thanks
Click to expand...
Click to collapse
If you're looking to stay with Verizon, I would keep an eye out for a GS4 with the MDK firmware. I see them pop up from time to time on Swappa, but never in the condition I'm looking for (looking to upgrade my wife). Other than that, your best bet is to leave Verizon and buy unlocked phones because at least they don't have additional carrier restrictions.

BadUsername said:
Locking the bootloader means added profit on verizons end. You have less access to features that get baked into a custom rom that we bypass, such as free tethering and simply making a device better than stock. Verizon wants this.
The less debloating and access to modified firmware available means they make more money on services people have to pay for.
Verizon will tell you it's better for consumers because it adds to your customer service experience. If you have a problem, and need help, then they are more likely to be able to help you knowing you are not running modified firmware that could give you a less than par experience. They will also add that using unapproved software could negatively impact their network (ie: tethering) and cause problems for other consumers.
There may be some truth in that, but without the ability to flash a new rom you essentially limit your software abilities and limit the life of the phone. It forces people to buy their services and extend their plan more often.
---------- Post added at 01:19 AM ---------- Previous post was at 01:13 AM ----------
The t-mobile variant for both the s3 and s4 have unlocked bootloaders on every device. None of them will work on verizons network. Every Verizon Samsung phone is completely locked down.
The last available firmware that can be unlocked on the S3 is mf1. The s4's is MDK or something but that's way harder to find. There is no unlock method for the s5.
Click to expand...
Click to collapse
Appreciate the response... but now you also mention the S5 having "no unlock"... what about this thread... http://forum.xda-developers.com/showthread.php?t=2711730

sbenson1226 said:
If you're looking to stay with Verizon, I would keep an eye out for a GS4 with the MDK firmware. I see them pop up from time to time on Swappa, but never in the condition I'm looking for (looking to upgrade my wife). Other than that, your best bet is to leave Verizon and buy unlocked phones because at least they don't have additional carrier restrictions.
Click to expand...
Click to collapse
What exactly id MDK? 4.2.2? And yea I really don't care what carrier I am with, I just want a phone I can tinker with and I been getting "tinker withdrawal" since upgrading to 4.4.2
Out of curiosity, what other phones are worth looking into that are comparable to the S3 and S4? It sucks when I am a diehard Samsung lover.

MortTheBeast said:
Appreciate the response... but now you also mention the S5 having "no unlock"... what about this thread... http://forum.xda-developers.com/showthread.php?t=2711730
Click to expand...
Click to collapse
That's T-Mobile. The Verizon version is locked down.
Sent from the Shark Tank using XDA Premium 4 mobile app

Unlocked S7 (SM-G930U) on T-Mo, How To Stop OTA Update Nag Notifications?

Hi. I purchased a new unlocked Galaxy S7 in July (SM-G930-U) not from T-mobile, but my carrier is T-Mobile. A few days ago, I got a notification to do a software update and almost tapped ok, but stopped the download and did some quick research to see if it was a T-Mobile update, or a Samsung update.
It turns out is a T-Mobile update, of course. I DO NOT WANT THEIR SYSTEM SOFTWARE on my unbranded, bloatware-free, and feature unrestricted phone.
But, there is no option for "No Thanks" to refuse the update, just "Later." And the icon never leaves my notification bar, and the phrase calling to update is always on the notification panel, and lock screen as well.
From initial setup, I selected the option to download updates manually, and have never done any updates on this phone (still factory). Is there any way I can stop this from occurring at all? Or does T-Mobile have me on perpetual rage inducing roller coaster? I do not want have to see this every day, and hopefully ever after if there is a way to stop this, as I do not plan to ever do updates via T-Mobile.
Thanks to anyone who has any suggestions or solutions!

athenalong said:
Hi. I purchased a new unlocked Galaxy S7 in July (SM-G930-U) not from T-mobile, but my carrier is T-Mobile. A few days ago, I got a notification to do a software update and almost tapped ok, but stopped the download and did some quick research to see if it was a T-Mobile update, or a Samsung update.
It turns out is a T-Mobile update, of course. I DO NOT WANT THEIR SYSTEM SOFTWARE on my unbranded, bloatware-free, and feature unrestricted phone.
But, there is no option for "No Thanks" to refuse the update, just "Later." And the icon never leaves my notification bar, and the phrase calling to update is always on the notification panel, and lock screen as well.
From initial setup, I selected the option to download updates manually, and have never done any updates on this phone (still factory). Is there any way I can stop this from occurring at all? Or does T-Mobile have me on perpetual rage inducing roller coaster? I do not want have to see this every day, and hopefully ever after if there is a way to stop this, as I do not plan to ever do updates via T-Mobile.
Thanks to anyone who has any suggestions or solutions!
Click to expand...
Click to collapse
Im assuming your not rooted. You can try downloading an app from the playstore like Package Disabler and freeze the software update apks. I beleive that specific app is discontinued but there are others specifically designed for Samsung. You can Google which ones to freeze but if you scroll through the app list it should be self explanatory according to the package name.

sshafranko said:
Im assuming your not rooted. You can try downloading an app from the playstore like Package Disabler and freeze the software update apks. I beleive that specific app is discontinued but there are others specifically designed for Samsung. You can Google which ones to freeze but if you scroll through the app list it should be self explanatory according to the package name.
Click to expand...
Click to collapse
First, thank you =]
Yes, you are correct, I have not rooted this one (only rooted my first Galaxy S a lonnnng time ago). I just got it (and paid full price for it =/ ) and I am not versed well enough in rooting to delve into that arena after only having it for 7 weeks =].
When I rooted the S, I used a one-click rooting program that I can't even remember. I also imagine that rooting now take more care and precision, correct?
Once again, I appreciate your response! Thanks!

athenalong said:
First, thank you =]
Yes, you are correct, I have not rooted this one (only rooted my first Galaxy S a lonnnng time ago). I just got it (and paid full price for it =/ ) and I am not versed well enough in rooting to delve into that arena after only having it for 7 weeks =].
When I rooted the S, I used a one-click rooting program that I can't even remember. I also imagine that rooting now take more care and precision, correct?
Once again, I appreciate your response! Thanks!
Click to expand...
Click to collapse
Yea rooting absolutely got a bit more complicated over the years especially with Samsung phones. Depending on your model Snapdragon or exynos it probably isnt worth the trouble at this moment anyway. Hope you achieve your goal with the update notification. If u need any more help let me know.

athenalong said:
Hi. I purchased a new unlocked Galaxy S7 in July (SM-G930-U) not from T-mobile, but my carrier is T-Mobile. A few days ago, I got a notification to do a software update and almost tapped ok, but stopped the download and did some quick research to see if it was a T-Mobile update, or a Samsung update.
It turns out is a T-Mobile update, of course. I DO NOT WANT THEIR SYSTEM SOFTWARE on my unbranded, bloatware-free, and feature unrestricted phone.
But, there is no option for "No Thanks" to refuse the update, just "Later." And the icon never leaves my notification bar, and the phrase calling to update is always on the notification panel, and lock screen as well.
From initial setup, I selected the option to download updates manually, and have never done any updates on this phone (still factory). Is there any way I can stop this from occurring at all? Or does T-Mobile have me on perpetual rage inducing roller coaster? I do not want have to see this every day, and hopefully ever after if there is a way to stop this, as I do not plan to ever do updates via T-Mobile.
Thanks to anyone who has any suggestions or solutions!
Click to expand...
Click to collapse
Hello,
I'm new to Samsung, but have had android for some time. With most phones the update is not only carrier specific but also model specific. Are you sure the update that you are being alerted to is a T-Mobile update. If I was to get an AT&T S7, unlock it and put in a T-Mobile sim to use on T-Mobile's network. Any updates that come to the phone will still be for the AT&T model since the CID and maybe the MID are different then a T-Mobile S7. I would assume that the unlocked G-930U would also have a different CID and MID. Again this is my first Samsung, but I hope this info helps.
Rsotbiemrptson
Sent from my SM-G930T using XDA-Developers mobile app

sshafranko said:
Yea rooting absolutely got a bit more complicated over the years especially with Samsung phones. Depending on your model Snapdragon or exynos it probably isnt worth the trouble at this moment anyway. Hope you achieve your goal with the update notification. If u need any more help let me know.
Click to expand...
Click to collapse
I really do appreciate your responding to me. I will do as you suggested and look in the Play Store for some apps.
Once again, THANK YOU for all of your help, and have a great day =]

Rsotbiemrptson said:
Hello,
I'm new to Samsung, but have had android for some time. With most phones the update is not only carrier specific but also model specific. Are you sure the update that you are being alerted to is a T-Mobile update. If I was to get an AT&T S7, unlock it and put in a T-Mobile sim to use on T-Mobile's network. Any updates that come to the phone will still be for the AT&T model since the CID and maybe the MID are different then a T-Mobile S7. I would assume that the unlocked G-930U would also have a different CID and MID. Again this is my first Samsung, but I hope this info helps.
Rsotbiemrptson
Click to expand...
Click to collapse
Hello! Thanks for your response.
It most definitely is a T-Mobile update... Though I will not permit their update to install, I will try to do some research based on what you mentioned and see what I can find out.
Thank you, and have a great day =]

athenalong, did you download the T-Mo update, or find a way to block it? I also have an S7 SM-G930U and want to switch to T-Mobile from AT&T today.