yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] -SmithTech-:
100 pages of crap

can the moderators do something with this post?

100 pages of off topic discussions and complaints if ridiculous.

I try and check this thread daily just to see if there are any relevant updates but I simply don't have the time to wade through pages and pages of bs.
[Verizon Samsung Galaxy S III] mattydangerfox:
Most useful information is here: http://xdaforums.com/showthread.php?t=1769411
[Verizon Samsung Galaxy S III] inm8num2:
I don't understand what you mean by this statement. Could you elaborate? Are you saying that rooting the phone isn't as big a perk as going against Verizon's wishes? Or are you saying the Verizon GS3 has been rooted sufficiently such that it's not considered a perk?
[Verizon Samsung Galaxy S III] zombieplanalpha:
Do you work for Verizon? Nobody is doing this just because Verizon doesn't want them to. The point is that Verizon should have no say in the software on my phone especially when they are being openly hypocritical by allowing the developers edition access to the same network.

Sent from my Verizon S3 with locked bootloader but I would love to change my signature.
[Verizon Samsung Galaxy S III] inm8num2:
Of course I don't work for Verizon. There's no need to get defensive. Why do you think I'm asking about rooting? I don't agree with Verizon's actions, either, but I'm just trying to get a sense of the rooting potential for the Verizon GS3. I'm trying to decide whether to keep this phone or not.

Here's my originalpost:

I genuinely don't understand what the following statement means in terms of answering my question:

"At this point in time the biggest perk to unlocking the bootloader outside of having a standard boot sequence is to piss off Verizon."

I have no idea how to interpret that in the context of the prospect of rooting/custom ROMs for the Verizon GS3. That statement to me implies that rooting the phone isn't as big a perk as pissing off Verizon. I just want to know what the prospects are for the phone having Android updates like other rooted phones, among other things. Yes, I know people are angry at Verizon. I am as much as anyone.

But my question isn't about how much I can piss off Verizon, or what the biggest perk of rooting my phone is. My question is what is the long term outlook for the Verizon GS3 development and custom updates so we don't have to wait endlessly for OTA updates.
[Verizon Samsung Galaxy S III] Metfanant:
well thats just not true...
[Verizon Samsung Galaxy S III] PJnc284:
The device is already rooted and has been pretty much since it was out in public hands. Heck there's even custom roms and kernels but they essentially hijack the boot sequence resulting in a quick reboot and generally takes a bit longer which is where the standard boot sequence comes in.
[Verizon Samsung Galaxy S III] Schaweet:
Interesting because even stock rooted on my DX I couldn't get updates. I realize things could be different with this though.

Sent from my SGS3
[Verizon Samsung Galaxy S III] inm8num2:
I know it's rooted, but I'm wondering how it looks for the Verizon GS3 to have developer updates for Android like on other devices instead of waiting for OTA updates. Because of the workarounds for loading custom ROMs and kernels, my limited understanding prevents me from assessing whether the GS3 could get JellyBean at the same pace as another phone which doesn't have the bootloader encryption issues.
[Verizon Samsung Galaxy S III] ylexot:
I could get OTAs when stock rooted on my DX.
[Verizon Samsung Galaxy S III] HHF2:
I hope he/she keeps pissing you off. You have the best and funniest analogies that I have ever heard! Keep up the good work.....
[Verizon Samsung Galaxy S III] schmaltzy:
WOW, this thread has gotten way off topic......

Well, not sure if any of you have seen this. I know I skimmed over something this morning about CVPCS's work but not sure if anyone posted a link. To lazy to skim through posts of FCC and petition signing posts that have nothing to do with the threads original intent....

Anyway, sorry if this has been posted yet this morning, but here's some good news that could maybe be used to update the first page!

https://plus.google.com/105844328547178759011/posts/6dJg4RRqST9
[Verizon Samsung Galaxy S III] Div033:
A talented CM developer by the username cvpcs is working hard getting CM10 working fully on our device. He is an official CM dev who created an excellent AOSP rom called Ruby for the Droid Incredible. He worked on other devices as well. The CM team took notice of his talent and brought him on board.

We're in pretty good standing for receiving updates promptly.

The only reason you don't see CM10 threads is because they're still working on the boot hijack sequence. The current kexec method is somewhat inconvenient. Plus, CM10 is still very early in development. Pressing the volume rockers freeze the device as of right now and there are semi frequent reboot issues. It will take some time to iron out these bugs and get the boot hijack working well so please be patient. We have a very talented dev working on this and we will have CM10 in due time. Once the boot hijack is completed, that will be done forever and will no longer be an extra hurdle meaning CM11, 12, 13, 27, 160 will come as fast for us as it does every other GS3 variant.

At that point unlocking the bootloader will not offer us faster development. As pointed out to me, an unlocked bootloader does offer more control in things like flashing custom splash screens and radios/modems, but as far as rom/kernel development goes it will offer little benefit after the boot hijack sequence is completed.
[Verizon Samsung Galaxy S III] sfetaz:
I dont know too much about locked bootloaders and I would like to learn something. What I have read is that that phone wants a signature before flashing onto the locked img areas. . That signature is encrypted using 256 bit encryption. Then the phone has a way to decrypt that signature to see if its legit. My question is where on the phone does it know what signature to check for, and how does it know what the right signature is? In someway the phone itself knows what key to look for. Where is this key stored on the phone and how is it setup so that this key cannot be found? Sorry if this is newbish but I dont understand how a package can be signed with an encryption key, how the phone knows what key to look for (meaning the key itself is on the phone) yet there is a way that verizon set it up so people can't simply find that key.

Also I read this thread everyday looking for legit research onto the locked bootloader, can we all please reduce the amount of speculation and ranting so that the developers can use this thread more for research on a workaround? I think it would be helpful to them.
[Verizon Samsung Galaxy S III] Coop9:
It's rooted.

We have custom ROMS.

RIL is cracked, AOSP ROMs are possible (and already are out there)

We can load custom kernels through KEXEC and make this pretty seamless by piggy-backing on the recovery partition.

In terms of development potential we're fine. You can install CM9 today. CM10 will be there soon, we will have it before any non-nexus phone has it officially.

Give it another couple weeks and things will look even better. It was just 2 weeks ago the first people started getting these in their hands. There was much gnashing of teeth, Droid X users thinking it was the same thing they had expereinced with that phone. Well, in that short time we're already further along than the X is two years later.
[Verizon Samsung Galaxy S III] newuser134:
What exactly is the point of a 4G smartphone without data? It's all nice and fun that we got CM9/10 working in concept and it runs great, but would you want to buy a phone if you knew it would never have data connection?

So, on the road to breaking the bootloader or finding a workaround, it's a very big step, however, I wouldn't say the locked bootloader really "isn't a huge issue", it IS a huge issue, otherwise there wouldn't be a whole forum full of people working on it like this. I'd have to say I've never seen any other forum's members come together and cooperate at this level in this kind of harmony to solve an issue. Hopefully it will get solved, and we will show Verizon they cannot keep us out of our own phones for long.
[Verizon Samsung Galaxy S III] Div033:
In the time you took to post this rant you could have read a couple pages back to see that data is now working on CM9. I agree that the issue of the locked bootloader should not be quelled but we need not be freaking out about not having custom roms because we do have them.
[Verizon Samsung Galaxy S III] AdamLange:
OP updated with latest news & links.
[Verizon Samsung Galaxy S III] Stam2000:
Nice except you're a Cowboys fan
[Verizon Samsung Galaxy S III] catalyst11:
Lol.

Sent from my SIII
[Verizon Samsung Galaxy S III] tjac357:
Everything is happening so fast you need to put the time next to the date on the thread title :good:
[Verizon Samsung Galaxy S III] morbidrealities:
Stinks

I just wanted to say that I hope you guys figure this out. It sucks that Verizon did this to you and didn't at least advertise or warn that they were the only carrier to encrypt the bootloader. Wish I could help in some way other than hoping it all works out in the end for you guys. Sucks to expect it will be the same as all the other US versions then find out it's been gimped.:(
[Verizon Samsung Galaxy S III] Immolate:
Agreed this is not worth a freak-out over, but I also think its a mistake to discount people's concerns as minor. I've been on enough Moto phones and enough others to know the difference an encrypted bootloader makes in the amount of flashing fun you can have, and the difference is significant. I think Verizon was wrong-headed and dishonest to not let the development community know this was coming. I read several blogs every day along with this site, and nobody seriously predicted this was going to happen.

But on the other hand, if you have unlimited data and needed to preserve it pre 6/28, then you had to put your money down on something, and the S3 was the best pick if you didn't want the GNex. If you did, you can probably sell your S3 and pick up a non-subsidized GNex and at least break even on the deal, so no harm there other than time and trouble.

I believe in pushing back on the businesses we patronize when they become unresponsive to our needs, but I also believe in rolling with the punches and having the proper perspective on the events in our lives. Make your peace with the circumstances life presents you and and then work to improve them. Life isn't a series of goals met. It's a series of journeys made.

I suggest that if you feel passionately about what Verizon has done here, find others that feel as you do and organize an effective response. There are plenty of us who aren't the activist type, but wouldn't hesitate to pitch in if we believe in what you're doing and sense your commitment and competence to get it done. I don't know what an effective response to this is, but I know it isn't an irrational hissy fit. Verizon has been inspiring individual dissatisfaction since day one, and those types of complaints don't phase them much.

Any effective response will involve either making them believe you're hurting their revenue, or making them believe you're about to hurt their revenue. There are countless ways to do this from boycott to brand damage to lawfare. Like any major concern, they work hard to prevent any of these things from happening, so you'll have to find a hole in their defenses to exploit. Just remember that our community is a small one, and that we need the help of the muggles to inflict any real pain.
[Verizon Samsung Galaxy S III] Elite49:
I second the update op title with time as well.
[Verizon Samsung Galaxy S III] Stryker1297:
you must be new so ill be nice. it is perfectly legal to do this and the fact that verizon did this makes them the real criminals when other carriers just needed to flash with odin
[Verizon Samsung Galaxy S III] ooofest:
Samsung allows changing font sizes through their standard UI for this phone, if that helps.

Not the same as changing DPI (i.e., relative sizes of all UI elements), I realize . . .

- ooofest
[Verizon Samsung Galaxy S III] NightxFall:
I really appreciate the work you guys are doing but I have one question. Based on your progress so far, does it look like we'll ever be able to have both custom kernels and a recovery.img? A custom kernel just isn't worth not having a recovery for me. If anything ever goes wrong then I'm basically completely screwed lol.
[Verizon Samsung Galaxy S III] droidstyle:
no your not thats what odin is for!
[Verizon Samsung Galaxy S III] ckochinsky125:
Great work guys. Love the developer community and what you guys have already done in such a short time with this phone.
[Verizon Samsung Galaxy S III] neyenlives:
Exactly. Do you know how many times I have flashed a recovery image that I made on my own phone? Never. I have made lots of them. They either didnt work or a couple days later they were so far outdated i just deleted them. Use Odin for everything.
[Verizon Samsung Galaxy S III] open1your1eyes0:
That's correct. ODIN is the equivalent of Fastboot. If you know what Fastboot is, then you know how powerful this tool can be.

Slighty OT: In regards to the craziness last night, I knew one of you guys would eventually get root. :) Also I knew the "dd" command was the only way to get custom recovery and custom kernel on there. The only missing piece I was missing was the exact block on the device that held the recovery and kernel partitions. After that is the easy part. The only thing I'm extremely surprised about is that the custom system tar doesn't trip the flash counter (which is a good thing of course). Glad you guys got that settled and now I am even more excited to get my device on Monday. :)
[Verizon Samsung Galaxy S III] NightxFall:
So what exactly is the difference between Odin and recovery? Let's say I brick my device, my recovery.img no longer exists in its proper form so I can't just flash a different ROM or use a nand backup in CWM. Do I have to hook up my phone to my PC and run Odin to flash a backup/different ROM? Also that would mean I can't just flash kernels/roms/backs straight on my phone anymore right? I'm sort of new to this, I'm rooted and running a custom ROM on my Ally, buts its extremely simple on this phone. Being able to flash files when not near a PC is important to me
[Verizon Samsung Galaxy S III] XDAholic:
Hopefully vzw gs3 will be supported by mobile Odin.....
[Verizon Samsung Galaxy S III] ckochinsky125:
You can glad everything through Odin it is such an easy process
[Verizon Samsung Galaxy S III] skennelly:
I can't completely agree with this. I am coming from the Droid x, and was certain that this phone would be unlocked. I figured that it would have amazing development that lasted several years like the og Droid. My goal in getting this phone was to have a device that was the most future proof with the best hardware. If this thing doesn't get unlocked, 18 months from now it will be stuck on whatever version of android we are on with no hope for a software update. I planned on keeping this device for more than two years in order to keep my unlimited data. Yes I think most people can handle stock if they had to, but I think the concern is the future of this phone and what version of android we'll get stuck on.
[Verizon Samsung Galaxy S III] aatrek:
At least it's not Gingerbread, right? :eek:
[Verizon Samsung Galaxy S III] Robster180:
Probably chocolate chip or toaster strudel or some other candy/snack

But I'm also coming from the X and these devs have gotten further in 2 says than almost 2 years between the X and X2, high hopes for this thing cracking soon
[Verizon Samsung Galaxy S III] bobcaruso:
Funny, I'm running CM9 with a KEXEC kernel, with working data, right now:silly:
[Verizon Samsung Galaxy S III] inm8num2:
Thanks, guys. Appreciate the responses - that's what I was looking for!

And I have the utmost faith in the developers. What they've done in such a short time has been amazing. It's helpful to hear you guys talk about the big picture - what's been done so far, what's around the corner, etc.
[Verizon Samsung Galaxy S III] bobcaruso:
With KEXEC and boot hijack, the locked bootloader is a non-issue
[Verizon Samsung Galaxy S III] Div033:
Yes, I agree. Correct me if I'm wrong but we still can't flash radios/modems or custom splash screens with a locked bootloader. These are relatively minor things but do limit our freedom with the device. I would still pay the amount I pledged to see the bootloader unlocked, regardless of our ability to flash custom kernels/roms.
[Verizon Samsung Galaxy S III] Srambo217:
#

#

#

#

****I made this thread for bootloader discussion, we need to keep this thread uncluttered for R&D - http://xdaforums.com/showthread.php?t=1784088

****

#

#

#

#
[Verizon Samsung Galaxy S III] tpike:
Check pm :D

Sent from my SCH-I535 using Xparent ICS Tapatalk 2
[Verizon Samsung Galaxy S III] Schaweet:
I flashed radios and splash screens and boot animations on my DX and that bootloader was uber locked down.

Sent from my SGS3
[Verizon Samsung Galaxy S III] Div033:
Thanks for the clarification. An earlier poster seemed confident that we couldn't. Indeed the locked bootloader is starting to seem moot outside of principal.
[Verizon Samsung Galaxy S III] AlexDeGruven:
It's really dependent on the individual device configuration. Moto is going to lock things down differently than Samsung, who is going to lock things down differently from HTC, who is going to lock things down differently than (lol) LG.
[Verizon Samsung Galaxy S III] tpike:
Exactly, it's all assumptions until someone does it and makes it doable for others.

Sent from my SCH-I535 using Xparent ICS Tapatalk 2
[Verizon Samsung Galaxy S III] Coop9:
Data issues have nothing to do with the bootloader. AOSP is still a work in progress, give it time.

At this point the locked bootloader is not a huge issue. It would be nice to have it unlocked, but it's not holding any development back. Just because a lot of people are still complaining and worrying doesn't make it a big issue in terms of development... Hell, most people don't even really understand what it means.
[Verizon Samsung Galaxy S III] techdeskjocky:
I'm on the newest CM9 as of 1am PDT today. Everything works so far except MMS. Haven't lost data once. Actually getting better speeds with CM9
[Verizon Samsung Galaxy S III] Cvballa3g0:
Guys, I need help. http://xdaforums.com/showthread.php?p=29064037#post29064037
[Verizon Samsung Galaxy S III] Schaweet:
Did you try this.....

Okay so this worked for me in the end:

You can force a SIM reprovision dialing this:

*2767*3855#

Shouldn't have to press call. It'll reset your phone + wipe data. Only tested in touchwiz, but it fixed everything.

Sent from my SGS3
[Verizon Samsung Galaxy S III] neyenlives:
Last I heard this only works on stock, but that was before the SIM Toolkit was added to the build and data wasn't working at that time either, so maybe this will work on CM9 now?
[Verizon Samsung Galaxy S III] NegativeOne:
What does a sim reprovision mean?
[Verizon Samsung Galaxy S III] neyenlives:
It basically reactivates your sim on the network, or that's the end result.
[Verizon Samsung Galaxy S III] Schaweet:
Well yes but he mentioned he returned to stock or at least I thought he did. This kexec method for CM9 really isn't tested (well it is now lol) and CVPCS stated the RIL wasn't quite right and he was still debugging it.

Like I said before you early adopters are brave as you never know what this can end up doing to the phone.

I believe the guy asking said he returned to stock via Odin and could not get voice working. I asked if he tried reprovisioning his sim at stock.

Sent from my SGS3
[Verizon Samsung Galaxy S III] tonu42:
Been running cm9 fine no wonky issues for me.
[Verizon Samsung Galaxy S III] Neverendingxsin:
Just a quick question I have my phone now and I'm debating on activating it but I'm curious the ONLY thing affected by the locked bootloader is the kernel correct? We can still flash roms and radios correct?
[Verizon Samsung Galaxy S III] Div033:
Roms yes, kernels yes via kexec, radios we don't know yet.
[Verizon Samsung Galaxy S III] alexcolodner:
Correct. And there are workarounds in place for flashing custom kernels which have been working fine. Unlocking bootloader would just make things easier. Not sure about radios.
[Verizon Samsung Galaxy S III] Neverendingxsin:
Thanks for the quick replies. Radios are my biggest concern especially since I'm coming from a thunderbolt
[Verizon Samsung Galaxy S III] tpike:
don't let that keep you from activating. This is a great device!

Sent from my SCH-I535 using Xparent ICS Tapatalk 2
[Verizon Samsung Galaxy S III] Neverendingxsin:
believe me i want to activate it, but i also paid full price so getting the developer one is no big deal i just don't want to wait. Im just worried it'll end up like my thunderbolt and have ril issues which stop development down the road
[Verizon Samsung Galaxy S III] tpike:
Well that makes sense

Sent from my SCH-I535 using Xparent ICS Tapatalk 2
[Verizon Samsung Galaxy S III] Neverendingxsin:
Yup, but since i have no idea when the developer phone will come out id rather just use this one, but for development and long term sake i dont want anymore radio problems, thats the biggest thing i had about the thunderbolt. Im fine with using kexec for kernels and all that.
[Verizon Samsung Galaxy S III] nosympathy:
I think we can. I could be wrong but I thought some of the guys with the newer phones with the updated stickers were flashing our current release stock image and it was downgrading their baseband. Not 100% though, as it was posted in General section. Maybe someone with an "updated" phone can answer this for us?
[Verizon Samsung Galaxy S III] crazydad:
ok so i just bought the s3 at VZW and it has the updated sticker. i wat to root it and install a recovery. where can i find how to root and if i can even root it < cause it has been updated for me me>. any help would be cool. i have looked AT The root post but it says dont use this if you have the update. thanks for the help
[Verizon Samsung Galaxy S III] Sniper_5:
Does your info look like this? If so, your fine to Root. I flashed Root_66 via Odin with no issues what-so-ever.

Sent from my VZW SGS3
[Verizon Samsung Galaxy S III] techdeskjocky:
Been on cm9 for close to 24 hours. One camera force close that was fixed with a reboot. Totally happy with it.
[Verizon Samsung Galaxy S III] crazydad:
Yes it does . it has the same as yours. Now if you can point me to the right way to root my s3......lol
[Verizon Samsung Galaxy S III] bbolton_98:
Question my sIII info is different, than what's posted in screenshot above. Is this what most of us have or will it be of any use to helping with bootloader work?

I'm stock unrooted, no updates that I know of haven't touched root or anything yet.

Thanks to all the dev's.

bbolton_98
[Verizon Samsung Galaxy S III] TheClap:
Just out of curiosity, why is your baseband verison I535VRLG1 while mine is I535VRLF2?

My Kernel Version is also different:

You have 3.0.8-743127

I have 3.0.8-618049
[Verizon Samsung Galaxy S III] NegativeOne:
I have 618 too- pre ordered. New phones have a dubious mini update
[Verizon Samsung Galaxy S III] squiggie:
Holy god has this turned into a junk thread...
[Verizon Samsung Galaxy S III] Poloasis:
Where do you suggest we go if you have another?

Thanks mate.
[Verizon Samsung Galaxy S III] suzook:
Not in the BOOTLOADER THREAD! This thread is useless now. Are there any mods around? Wtf?
[Verizon Samsung Galaxy S III] kzoak82:
I agree aren't there another threads about "random thoughts" or the specific topics being posted here? I check this for relevant updates and for the last couple of days all I read about is how Johnny can't find the camera or Daisy doesn't like the white s3 and would rather have a pink one.......
[Verizon Samsung Galaxy S III] ali87va:
Stay on topic, Jesus Christ