I have yet to get a confirmation on this from any US carrier. Can the boot loader be unlocked? I know this is verizon and while other carriers may have an S3 who's boot loader can be unlocked, well, we all know how Big Red is about this.
Is there any confirmation about the status of the S3s boot loader any US carrier? Is it locked down as tight as a motorola droid phone? Or will we be able to unlock the boot loader?
Device(s): LTE Galaxy Nexus (AOKP b37); Dinc (CM 7.1) [retired]
Carrier: Not Provided
Thanks: 957
Thanked 1,308 Times in 763 Posts
Quote:
Originally Posted by ajdroidx
I have yet to get a confirmation on this from any US carrier. Can the boot loader be unlocked? I know this is verizon and while other carriers may have an S3 who's boot loader can be unlocked, well, we all know how Big Red is about this.
Is there any confirmation about the status of the S3s boot loader any US carrier? Is it locked down as tight as a motorola droid phone? Or will we be able to unlock the boot loader?
Hoping to find out as well. If the bootloader is unlocked, I'm probably going to get one (hopefully with some sort of credit to my line or something from VZW due to the mid-call muting issues) with the hopes that the audio quality during calls and the radio itself is better.
I have yet to get a confirmation on this from any US carrier. Can the boot loader be unlocked? I know this is verizon and while other carriers may have an S3 who's boot loader can be unlocked, well, we all know how Big Red is about this.
Is there any confirmation about the status of the S3s boot loader any US carrier? Is it locked down as tight as a motorola droid phone? Or will we be able to unlock the boot loader?
when HTC started their unlocked policy Verizon did not interfere with it. so I would suspect the same will be said about Samsung phones.
Who knows what is really going on yet. Galaxy nexus was locked. You had to unlock it. Being locked is a good thing for most people. Being locked and encrypted is when you should worryB-)
Device(s): LTE Galaxy Nexus (AOKP b37); Dinc (CM 7.1) [retired]
Carrier: Not Provided
Thanks: 957
Thanked 1,308 Times in 763 Posts
Quote:
Originally Posted by fbm111
Who knows what is really going on yet. Galaxy nexus was locked. You had to unlock it. Being locked is a good thing for most people. Being locked and encrypted is when you should worryB-)
No it wasn't. It was a matter of doing a fastboot oem unlock and a few seconds.later you're good to go. This is a big deal for people who want the flexibility to root/rom. A locked bootloader is just typical Verizon trying to exert draconian control over everything. T-Mobile is looking better and better.
Device(s): LTE Galaxy Nexus (AOKP b37); Dinc (CM 7.1) [retired]
Carrier: Not Provided
Thanks: 957
Thanked 1,308 Times in 763 Posts
Quote:
Originally Posted by artman540
The Galaxy Nexus was 100% locked, hence the reason you had to unlock it. It took all of... one minute.
Obviously we're talking about whether or not it can be unlocked. The Nexus was unlockable BY DEFINITION and design. The sgs3 bootloader is purposely locked to prevent flashing parts of the OS. this is totally different from the nexus being "locked".
Im going to play with the phone for 14 days and then return it/cut ties with Verizon. I love my unlimited data but im not handing over my hard earned money to a company that is pretty much telling me how i can or cannot use my phone.
I just got shipping notice tonight and my GS3 will be arriving Monday. However, I'm very tempted to return it unopened and just keep my Galaxy Nexus until the lines on my family plan are off contract.
Getting very tired of Verizon's arrogant handling of everything from voice/data plans to encrypted bootloaders:
- Forcing Share Everything down our throats (sure we can keep our current plan for now, but we'll all have to be on SE sooner or later)
- Raising and adding fees
- Screwing up the Galaxy Nexus launch and software udpates
- Locking and encrypting the GS3 bootloader (even as the other carriers left it unencrypted)
- Forcing that stupid Wifi toggle notification in the main notification area instead of with the toggles like on the other carrier versions (really Verizon, are we stupid enough that you have to constantly remind us to switch to WIFI????)
- Always late with updates, so I'm sure we'll be the last ones to receive GS3 updates
All of this just leaves a bad taste in my mouth and I am done with them!
The droid x had a locked boot-loader and still had awesome rom development. So I'm sure devs will come up with lots of great roms for us to play with.
The problem is that the rest of the planet will get JellyBean on their GS3 probably within a month from now, the Verizon version won't until the official release (which will probably be over a month behind every other carrier's official release), or will be using an older kernel that will likely cause problems. The DroidX never ran ICS properly... you should know that.
I can confirm, through the Samsung Galaxy Support Team (Level 2), that the request for the ENCRYPTED bootloader (not just locked) was made by Verizon themselves, and Verizon was the ONLY carrier to want this...
The bootloader status is also part of the OEM/Carrier agreement between Samsung and VZW, and because of said agreement, VZW is the only party with the ability to unlock the device...
i got the vibe from the tech that i spoke to, that VZW requested this and that they would have refused the carry the device without Samsung agreeing to the the modification
Edit: I've also read from someone who has spoken with a Level 3 Samsung Tech...that the phones left Samsung and Verizon THEMSELVES performed the software modifications...this person got the vibe from his tech that Samsung was resistant to the modification, but that VZW went ahead with it anyway
__________________
- Samsung Galaxy SIII (Blue32) - SynergyROM JellyBean - Nova Launcher -
- Droid X - Liberty3 - Overclocked @ 1.15ghz - LauncherPro Plus -
Questions about rooting/modding your VZW Samsung Galaxy S3? Go Here
Last edited by Metfanant; July 7th, 2012 at 02:21 AM.
Anyone else leaving Verizon over this locked bootloader BS?
I've decided to leave for AT&T. Faster data speeds, an extra GB data for the same price, rollover minutes all had me strongly considering, but this pushed me over the edge.
If I don't see it being fixed then yes. At&t or tmobile, anybody have insight on which is better as far as speeds (I'm in Connecticut and also frequent Boston alot)
If I don't see it being fixed then yes. At&t or tmobile, anybody have insight on which is better as far as speeds (I'm in Connecticut and also frequent Boston alot)
Really depends on the area. Tmobile is just awful in general. But they do have good coverage in certain area's. AT&T will have better overall coverage. Same goes for LTE/HSPA.
The Following User Says Thank You to darkestred For This Useful Post:
Verizons speeds and stability is better (depends on the area though) but I switched to AT&T though because I wanted 3gb of data instead of the 1gb Verizon was offering at the same price. I could care less about unlimited talk time.
Trust me brother AT&T is evil. The grass is no greener over there. I just left them with no intentions of ever returning.
yeah, I had them when I was still in my family plan and they weren't the best company to deal with. I might not have a choice though, only thing they aren't carrying the 32gb version like tmobile is
Pre-paid here I come!! VZ just made it a no-brainer for me. An encrypted boot loader is a huge no-no for me, especially if this is my last upgrade ever.
It will be a long wait til next May with my Thunderbolt, but it'll be worth it!!
Device(s): LTE Galaxy Nexus (AOKP b37); Dinc (CM 7.1) [retired]
Carrier: Not Provided
Thanks: 957
Thanked 1,308 Times in 763 Posts
Quote:
Originally Posted by fbm111
This is ridiculous at this point. Let the phone get into the hands of the powers to be before you all think strictly doom and gloom.
For me it's the principle of the thing and the fact that this sets a precedence. The sgs3 may be rooted, but the bootloader is still encrypted which means no custom kernels.
For me it's the principle of the thing and the fact that this sets a precedence. The sgs3 may be rooted, but the bootloader is still encrypted which means no custom kernels.
Dont give up hope yet, the devs may find a way to crack it. Theres already a ton of dev's, some who dont even have the device yet, working on the bootloader. When the actual phone launches, we'll have a ton more.
Device(s): LTE Galaxy Nexus (AOKP b37); Dinc (CM 7.1) [retired]
Carrier: Not Provided
Thanks: 957
Thanked 1,308 Times in 763 Posts
Quote:
Originally Posted by NightxFall
Dont give up hope yet, the devs may find a way to crack it. Theres already a ton of dev's, some who dont even have the device yet, working on the bootloader. When the actual phone launches, we'll have a ton more.
I'm sure people will try but cracking encrypted bootloaders is more daunting than rooting. I'm a bit worried the bootloader being locked will scare devs away. I'm not very hopeful for AOKP
This is ridiculous at this point. Let the phone get into the hands of the powers to be before you all think strictly doom and gloom.
like the Droid X?
Quote:
Originally Posted by NightxFall
Dont give up hope yet, the devs may find a way to crack it. Theres already a ton of dev's, some who dont even have the device yet, working on the bootloader. When the actual phone launches, we'll have a ton more.
like the Droid X?
The Following 2 Users Say Thank You to Metfanant For This Useful Post:
Device(s): LTE Galaxy Nexus (AOKP b37); Dinc (CM 7.1) [retired]
Carrier: Not Provided
Thanks: 957
Thanked 1,308 Times in 763 Posts
Quote:
Originally Posted by fbm111
Seriously?
Phone is not out yet and you keep saying like the DROID X?
I happen to follow quit a few Devs on twitter and I bet this will be taken care of before Tuesday.
Try having a little patience.
We shouldn't have to be even having this discussion. Verizon is the ONLY carrier in the entire world carrying the sgs3 that decided to lock the bootloader. And I think you're way overly optimistic about the bootloader being unlocked by Tuesday when it doesn't even launch until Tuesday. Time will tell, but I'm sure the locked bootloader is pissing plenty of devs off (@supercurio for one). True it's not a Motorola bootloader encryption, but it's still not anywhere close to a gimme.
Phone is not out yet and you keep saying like the DROID X?
I happen to follow quit a few Devs on twitter and I bet this will be taken care of before Tuesday.
Try having a little patience.
i exercised 2 years of patience as a DX owner
1. People not familiar with Moto devices and the consequences of the bootloader being encrypted don't fully understand how much effort was put into cracking the DX
2. i have plenty of patience, however im not interested in locking myself into a phone and a contract (without unlimited data) for the next two years with no idea whether it will be unlocked or not...so for the time being, it is MY OPINION that sticking with my already locked down DX which is running very nicely on Liberty3 Gingerbread and keeping my unlimited data plan is the right move...
i pre-ordered the SGS3 under the assumption it would be unlocked, if this is achieved then i will re-order
Was the Thunderbolt bootloader locked in a similar way? And since this is the only S3 version that is locked, would it be possible to downgrade somehow back to Samsung's original software somehow?
JackpotClavin and Invisiblek have successfully loaded a custom kernel using a modified recovery ramdisk. It's still very early but this is excellent news for us. As it stands, this method wipes ClockworkMod and requires the recovery key combination on every boot, but those issues can probably both be overcome with custom scripts.
Stay tuned guys...and mash those two guys' Thanks buttons!
Good news...still a hack, though. I'd much prefer an unlocked bootloader. I wonder if this will require running something in recovery each time you boot in order to have the custom kernel take effect?
Good news...still a hack, though. I'd much prefer an unlocked bootloader. I wonder if this will require running something in recovery each time you boot in order to have the custom kernel take effect?
Hacks are ok, as long as we can do custom kernels there is hope. I have lots of hope mainly because this is a Samsung and NOT a Motorola.
Device(s): LTE Galaxy Nexus (AOKP b37); Dinc (CM 7.1) [retired]
Carrier: Not Provided
Thanks: 957
Thanked 1,308 Times in 763 Posts
Quote:
Originally Posted by SirKronan
Hacks are ok, as long as we can do custom kernels there is hope. I have lots of hope mainly because this is a Samsung and NOT a Motorola.
Well hopefully they gain access to the boot partition and are able to boot from it. Having to boot to recovery to boot a custom kernel every time you reboot is kind of a PITA. They say they're working on it, though.
Well hopefully they gain access to the boot partition and are able to boot from it. Having to boot to recovery to boot a custom kernel every time you reboot is kind of a PITA. They say they're working on it, though.
Especially for those of us utilizing multiple batteries. I like never having to plug my phone into a charger.
Verizon sucks... Really, Verizon? The only US carrier to lock down the SGIII bootloader.
What a crappy distinction for Verizon.
Just got off the phone with a Verizon CS rep. She had absolutely no idea what I was talking about when I told her the reason why I wanted to cancel my preorder for the 2 SGIII phones I preordered for two lines on our family plan, "what's a bootloader?"
The phones are in the process of being sent out today, so I can't cancel the order. Will have to ship the phones back unopened, or return the phones unopened to a Verizon corporate store for credit back to my account.
I'm going to wait for all the contracts on all lines on our family plan to expire, then I'll seriously think about switching to another carrier. Been with Verizon for ages now.
Stop knocking the droid x, it had a locked and encrypted boot loader. It still had many great roms that were loved by its users. We're even running ICS roms. Does it suck that the s3 boot loader is locked, yeah. But all this doom and gloom is still rather amusing. Especially so soon after its release.
Stop knocking the droid x, it had a locked and encrypted boot loader. It still had many great roms that were loved by its users. We're even running ICS roms. Does it suck that the s3 boot loader is locked, yeah. But all this doom and gloom is still rather amusing. Especially so soon after its release.
Mostly because it was popular AND being one of the first with a locked bootloader it was a challenge. Dev community is just sick of locked bootloaders.
I can confirm, through the Samsung Galaxy Support Team (Level 2), that the request for the ENCRYPTED bootloader (not just locked) was made by Verizon themselves, and Verizon was the ONLY carrier to want this...
Edit: I've also read from someone who has spoken with a Level 3 Samsung Tech...that the phones left Samsung and Verizon THEMSELVES performed the software modifications...this person got the vibe from his tech that Samsung was resistant to the modification, but that VZW went ahead with it anyway
I agree with the first part, but there is no way that second part is true. Verizon did not receive them from Samsung, open each one up, hook it up and lock the bootloader.
7Likes
The boot loader (US VERSION)
)
I hope you're right though.
