yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Imoseyon:
Someone sent me a link to this thread and I didn't get a chance to look through it all. And I don't have a S3 (yet) so I may be off-base here, but here's probably a good workaround in case bootloader never gets unlocked:

1) Flash a combined custom kernel/recovery image to recovery partition.

2) Hi-jack boot init in ROM to boot into recovery when /sdcard/continue_init doesn't exist (and touch /sdcard/boot_kernel).

3) When it boots into recovery, check to see if /sdcard/boot_kernel exists. If so, boot into custom kernel (remove /sdcard/boot_kernel and touch /sdcard/continue_init). If not, boot into recovery.

Well, I'm sure invisiblek and other amazing devs are working on a better solution already, but if not I think the above should work. I think. :)
[Verizon Samsung Galaxy S III] ckochinsky125:
I didn't lose mine but Im sure verizon will figure something out to take it away even if you buy unsubsidized phones, just because thats how they are.

---------- Post added at 09:29 PM ---------- Previous post was at 09:27 PM ----------

I have a question for the great devs who found the current work around. I am new to exactly how to unlock bootloaders( i have used methods on previous phones) but what are the chances that they will be able to get the current method to stick or does it already? I was just a little confused reading through this and other threads. I had a nexus which never had to deal with this but all my other phones took a little while for bootloader(thunderbolt, fascinate, inc)
[Verizon Samsung Galaxy S III] SwervFusion:
Nah..

On GSM, as long as the phone is sim unlocked, and supports the bands that the carrier uses, you just put the sim in and go..

Only thing is, your stuck using edge speeds if the phone wasn't designed for that carrier (At least that's how it is between AT&T/TMO).
[Verizon Samsung Galaxy S III] tekhna:
Imoseyon in the house! Loved your kernels on the TBolt.
[Verizon Samsung Galaxy S III] neyenlives:
come on over to the freenode channel #verizons3 :) long time no see, welcome
[Verizon Samsung Galaxy S III] open1your1eyes0:
Imoseyon, you make some mean VZW Galaxy Nexus kernels (one of which I am personally using right now). ;) Glad to have you with us in here sir. Looking forward to much of your work on this device. :good:
[Verizon Samsung Galaxy S III] Loglud:
This is all very true and efuses/qfuses are very interesting beasts to mess around with. The problem is that alot of the time they lead to a single devices being unlocked. E-Fuses often times contain a unique id that is used in single write id. This is set by the manufacture and each device is different. Alot of time we can get around bootloaders by looking at the boot chain.

Usually,

xloader->uboot->boot.img->system.img->userdata.img

˅

recovery.img

˅

systemflash

The system flash usually have to have secure info in the kernel and the inframs, however there is no check usually in the header, meaning you can overload the header to allow secondary boot.

This is always an interesting idea, however kexec relies on a register being set in the kernel that has the location of the stack where the proc1 lies. If kexec is enabled in the kernel then we can use a precompiled kexec. However it most likley will not so i would look here on how to make it.

http://xdaforums.com/showthread.php?t=1427610
[Verizon Samsung Galaxy S III] Buddy Revell:
Hope to see your Lean Kernel on the Verizon GS3. It is freakin awesome on my Galaxy Nexus.
[Verizon Samsung Galaxy S III] aj8600:
Just tried to join.... Maybe it's me but is anyone in there?
[Verizon Samsung Galaxy S III] ZServ:
76 people are in there lol
[Verizon Samsung Galaxy S III] segv11:
Nexus phones direct from Google are changing that equation... at least for GSM devices. Not a moment too soon, either. The amount of control carriers have here (compared to, say, Europe) is disguising.

Sent from my BANNED Unified-Search-enabled Galaxy Nexus.
[Verizon Samsung Galaxy S III] aj8600:
Well **** me.....

I will admit I'm not very learned in the ways of irc.

I couldn't get it to work on my Andchat app. Any help? Not meaning to hijack the thread though.
[Verizon Samsung Galaxy S III] CrimsinX:
I got an email out to him this morning...waiting for reply.
[Verizon Samsung Galaxy S III] Cvballa3g0:
Are you in the freenode irc?
[Verizon Samsung Galaxy S III] aj8600:
I was... I didn't see anything but my name
[Verizon Samsung Galaxy S III] Sniper_5:
I SHOULD have this phone by the 12th, if I do, I'm available as a tester once I root the phone. I'll gladly help in any way I can.

Sent from my Droid X until I get my SGS3
[Verizon Samsung Galaxy S III] johnc810:
Just wanted to let everyone who is thinking about returning the phone know that you only have 14 days from when the phone shipped to return it. I just spoke to verizon about this. I read in this forum earlier that you had 30 days to activate it and then 14 days from activation which is not true.
[Verizon Samsung Galaxy S III] aj8600:
irc freenode.net/

Right?

Then #verizons3?
[Verizon Samsung Galaxy S III] viode:
Here's a trivially modified version of the bootloader (aboot). I simply modified some insignificant EXIF data ("Adobe Photoshop" to "VerizonSucksCock") from invisiblek's dumped aboot.img.

If flashing this doesn't brick the device it tells us that aboot is not signed/checked.

WARNING: I will not be responsible for bricks. It would be wise do binary diff this against your own aboot before attempting.

Download: http://www.mediafire.com/?dyhmkepoebbpj21
[Verizon Samsung Galaxy S III] aj8600:
+1 as will I :) we'll
[Verizon Samsung Galaxy S III] open1your1eyes0:
EDIT: If serious however, on that note. In case you do brick your device, just take it back to Verizon if you're still within your 14 day period and play dumb (always worked for me). "Woke up this morning and somehow got this screen, not sure what's happening." Trust me, they'll have no idea what that is either. They'll play around with it for a few minutes (to no avail of course) and end up replacing your phone. Just make sure to stick to your story.
[Verizon Samsung Galaxy S III] sneakysolidbake:
encouraging fraud.......lol :rolleyes:

someone who isn't me would do the same thing
[Verizon Samsung Galaxy S III] erronr:
Yes, that is serious.
[Verizon Samsung Galaxy S III] rothnic:
Do you know of any other phones that have implemented something like this? I think this type of solution is currently being considered as a worst case scenario if a full work around can't be found. Although, I think what you outlined is a good interim solution if not a more likely outcome.
[Verizon Samsung Galaxy S III] ikithme:
Just in case no one knows WHAT kexec is:

"In computing, kexec (kernel execution) is a mechanism of the Linux kernel that allows "live" booting of a new kernel "over" the currently running kernel. kexec skips the bootloader stage (hardware initialization phase by the firmware or BIOS) and directly loads the new kernel into memory, where it starts executing immediately. This avoids the long times associated with a full reboot[1], and can help systems to meet high-availability requirements by minimizing downtime.

While feasible, implementing a mechanism such as kexec raises two major challenges:

the new kernel will overwrite the memory of the currently running one, while it is still executing

the new kernel will usually expect all physical devices to be in a well-defined state (as they are after system reboot, when the BIOS (or firmware) resets them to a "sane" state). Bypassing a real reboot may leave devices in an unknown state, and the new kernel will have to recover from that."

From wikipedia

My question is how exactly does it boot, is it something like this:

Boatloader checks boot partition, passes because kernel is correct

Kernel starts booting then kexec runs and replaces stock kernel

ROM finishes booting?

Or is it something that happens after the rom is booted, which might cause problems of its own.
[Verizon Samsung Galaxy S III] bobloblaw1:
kexec

In computing, kexec (kernel execution) is a mechanism of the Linux kernel that allows "live" booting of a new kernel "over" the currently running kernel. kexec skips the bootloader stage (hardware initialization phase by the firmware or BIOS) and directly loads the new kernel into memory, where it starts executing immediately. This avoids the long times associated with a full reboot[1], and can help systems to meet high-availability requirements by minimizing downtime.

While feasible, implementing a mechanism such as kexec raises two major challenges:

the new kernel will overwrite the memory of the currently running one, while it is still executing

the new kernel will usually expect all physical devices to be in a well-defined state (as they are after system reboot, when the BIOS (or firmware) resets them to a "sane" state). Bypassing a real reboot may leave devices in an unknown state, and the new kernel will have to recover from that.

http://en.m.wikipedia.org/wiki/Kexec
[Verizon Samsung Galaxy S III] antp121:
Isn't that what they use on the razr? They have some gooooood aosp roms.
[Verizon Samsung Galaxy S III] youarealwaysthereMD:
My friend who writes android apps says it is possible and has been done with other devices.

He also said an unlock would be far better.

Here's to a solution :)
[Verizon Samsung Galaxy S III] aj8600:
Excited to see where this is going :D

Hoping for something great by the time Tuesday rolls around
[Verizon Samsung Galaxy S III] The Archangel:
Don't let it happen again.

I just spent 20 minutes on my phone cleaning out 3-4 pages of clutter, I'm watching this thread now. Next person I see get off topic, will get an infraction. If yall wanna talk bout how Verizon sucks, go to the general section.​
[Verizon Samsung Galaxy S III] biff6789:
Is it even possible to combine recovery and kernel on the same partition before kernel source is released?

Also, to those thinking they can buy a global model to run on Verizon's network, unless you have an ESN/MEID that Verizon approves and is on their whitelist (meaning you bought a Verizon-branded phone) they won't activate it on their network.

Best options at this point:

1) KEXEC (chainloading kernels, which has worked with considerable success on Motos)

2) Kernel/recovery combined partition, but could easily be broken with a future OTA

3) Meeting a Samsung employee out in the back alley who deals encryption keys
[Verizon Samsung Galaxy S III] rothnic:
Not sure, that is why i was asking if anyone had an example on how it would be implemented.
[Verizon Samsung Galaxy S III] jaben2:
In IRC I believe they said they got KEXEC working and was able to run a custom kernel. Supposed to be making a post here on XDA.
[Verizon Samsung Galaxy S III] SirKronan:
This would be sweet! I anxiously await the post ... :D
[Verizon Samsung Galaxy S III] biff6789:
Since this is a news thread...

It was reported in IRC within the past hour or so that supposedly BOTH kexec is likely working and noobnl (whom many of you may know from his work with AOSP ROMs) has stated that the RIL has been cracked :D

To those who don't know what that means, kexec chainloads kernels (in simplest terms, the custom kernel loads on top of the stock kernel AFTER the bootloader checks to make sure the stock kernel has been unmodified). This was necessary if one wanted to run a non-Touchwiz ROM (such as CM, AOKP, etc) or if they just wanted to run an overclocked, undervolted kernel.

The RIL is essentially the radio. It was also needed to run a non-Touchwiz ROM and now opens the door to Jelly Bean ROMs.

There is still working/testing to be done, and there are no ETAs, so don't bug the devs. They're actively working on it so let them do their thing.

What a roller coaster of a weekend :)
[Verizon Samsung Galaxy S III] NFSP G35:
^That's fantastic news. Thanks for the succinct update, and also a big thanks to the devs for doing what they do so well. :good:

Mine shipped out on the 8th, and I'm very happy that I'll be able to root it immediately, and hopefully have a custom ROM before too long.

...and if the devs manage to get a decent JB ROM working on here, I will be one happy camper :D
[Verizon Samsung Galaxy S III] densetsu86:
Just a question does the kexec allow the sgsiii to use both cores. I have heard that kexec on both the droid razr and droid 3 doesn't allow for dual core yet. Any such issues with sgsiii or is it too soon to tell?
[Verizon Samsung Galaxy S III] biff6789:
You'll want to ask that here:

http://xdaforums.com/showthread.php?t=1760678
[Verizon Samsung Galaxy S III] narsciso:
I never would have thought to be an issue. Wow man
[Verizon Samsung Galaxy S III] I Am Marino:
It's a huge issue over there and I don't believe it's been solved yet to my knowledge, could be wrong.
[Verizon Samsung Galaxy S III] TheClap:
According to Noobnl in the IRC channel, the dual core thing isnt an issue since its a hard reboot so it reloads the bootloader; "this is a more advanced form kexec."
[Verizon Samsung Galaxy S III] tpike:
Thanks for the updates

Sent from my DROID RAZR using Xparent ICS Tapatalk 2
[Verizon Samsung Galaxy S III] I Am Marino:
Well I hope for the best for you guys.
[Verizon Samsung Galaxy S III] 17akota:
So much has happened this weekend! First we get root (I'm fine with that since I've been locked down forever :/ ) and now we possibly have the answer for the bootloader! I am extremely excited to get my S3 today now. Huge thanks to everyone that is in this!
[Verizon Samsung Galaxy S III] CrimsinX:
Sent out an email yesterday to Josh over at mobiletechvideos.com. He thinks he can replace the bootloader with the Sprint version. Might be another good solution. This would mean truly unlocked! All is looking good so far, keep it up!
[Verizon Samsung Galaxy S III] JimmyHACK:
Source files for the Verizon version are now available from Samsung. Hopefully this may help a little in some way.
[Verizon Samsung Galaxy S III] AdamLange:
Link?
[Verizon Samsung Galaxy S III] antp121:
Go to opensource.Samsung.com and search for the sch-I535
[Verizon Samsung Galaxy S III] invisiblek:
This has already been tried. It will brick the phone.
[Verizon Samsung Galaxy S III] antp121:
Will open source files help?
[Verizon Samsung Galaxy S III] dreamsti:
http://opensource.samsung.com/index.jsp;jsessionid=67C9340B3AF815AF738FE6DFC9A8663A
[Verizon Samsung Galaxy S III] invisiblek:
they wouldnt give us source for aboot

most likely this is just kernel source
[Verizon Samsung Galaxy S III] connexion2005:
My method would be different versus trying just one of the bootloaders. My method would overwrite the pit/sbl1/sbl2/sbl3/tz and rpm image locations with an unlocked CDMA SGS III set of images. Lets not rule it out just yet just because someone flashed a Sprint bootloader via ODIN.
[Verizon Samsung Galaxy S III] neyenlives:
The source wont include any of the Samsung proprietary code which is developed under the Apache license. Only thing in the source is the Linux kernel that must be published under the GPL. Typically the things the devs have to work on the most is not in the source.

They might get a few lulz from Samsung sloppy code garbage.....
[Verizon Samsung Galaxy S III] invisiblek:
it wasn't flashed via odin, dd

good luck with this, i hope it works
[Verizon Samsung Galaxy S III] connexion2005:
Which all partitions were flashed? If it was just one or two of the vital zones this may be an invalid method of testing.
[Verizon Samsung Galaxy S III] invisiblek:
Just aboot
[Verizon Samsung Galaxy S III] OldManJames:
since you are using Jtag you could also restore it to working order if it doesnt work right?
[Verizon Samsung Galaxy S III] connexion2005:
Yes absolutely. My testing will be harmless as all original data will be saved for restoration if needed.
[Verizon Samsung Galaxy S III] juntistik:
Well if your method works there is a $725 dollar bounty for you...and counting. I'm interested to see how the RIL from sprint will handle the LTE bands here on VzW, last night on IRC it seemed to be a nonissue to everyone but I would assume there is still some labor intensive work to do.

I'll have my sgs3 tonight and would have no problem looking at lines and lines of code for a good cause..I do it at school and work, at least this will be for a valuable cause :laugh:
[Verizon Samsung Galaxy S III] OldManJames:
do you have access to a phone to test on?
[Verizon Samsung Galaxy S III] connexion2005:
Not yet. I have two BETA testers but they are not sending in their devices until they receive them (3 more days).

---------- Post added at 09:49 AM ---------- Previous post was at 09:48 AM ----------

I have all prerequisites though. Just need a VZW model...
[Verizon Samsung Galaxy S III] squiggie:
This is EXACTLY the reason why Verizon is locking bootloaders. This is NOT ok, and Verizon does know. The rep you bring it to may not know at the time, but Verizon knows once they go for refurb.
[Verizon Samsung Galaxy S III] Flowah:
But anyone playing around with this stuff, could easily recover if they opened the phone up more, couldn't they? I remember the Droid1 being very open. I can't remember any permanent bricks. I sure didn't get any. If I ever had problems, I just SBFed the phone and got right back into it. I was flashing kernels and ROM's at least once a week for a while.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Key note to remember, the only reason we would do something like that is because of the locked bootloader being an issue to begin with. ;)
[Verizon Samsung Galaxy S III] connexion2005:
I can recover any hard brick just so you are aware. The initial statement was correct, committing fraud to carriers is what causes devices to be locked in the first place. It's hard to blame them with 1,000,000's of dollars per year being lost to fraud.

Now let's stay on topic... ;)
[Verizon Samsung Galaxy S III] neh4pres:
How do you recover from any hard brick? Is there a link so I can read up on this?
[Verizon Samsung Galaxy S III] ScottIsMyName:
If you can recover hard bricks, I'm pretty sure Verizon can also. They are not losing millions of dollars per year because of things like that.
[Verizon Samsung Galaxy S III] neyenlives:
You have probably never had to staff and orchestrate a major size refurb service from beginning to end. Which is okay, but it means we cant possibly know the actual cost associated with the scale of the operations required to satisfy the entire Verizon customer base. Have a great day!
[Verizon Samsung Galaxy S III] neyenlives:
He has JTAG equipment. Only thing JTAG cant fix is if you physically brick a component like fry it.
[Verizon Samsung Galaxy S III] juntistik:
Has anyone seen any data discussing the correlation between a locked/encrypted bootloader and returns of defective devices? I can understand the logic that Verizon is applying, but I feel like its flawed. Wouldn't more bricks occur from trying to circumvent the encrypted bootloader? People tampering with their technology and then returning it when it breaks is common in the world of technology and it happens with consoles, computers, etc. Companies plan and budget for it, i'm not sure if there is really any correlation between encrypting the bootloader and reductions in returns.

Also, as far as helping dev's get their hands on vzw sgs3's, would said phones need service? If not, I would love to see this community come together and see what we can provide. I have seen dev's doing amazing work over the past few days without even having a vzw sgs3 on hand.
[Verizon Samsung Galaxy S III] Elite49:
Wuhoh looks like Verizons blaming Samsung while Samsung is blaming Verizon. Now that the blame game has started and we KNOW its Verizon who requested it hopefully now we can get a response from them. Why must Verizon be so stupid.
[Verizon Samsung Galaxy S III] ooofest:
I must have missed that - Verizon is blaming Samsung . . . for locking it uniquely to Verizon's request?

- ooofest
[Verizon Samsung Galaxy S III] neyenlives:
Which way did the mud sling? Give us links! Would be good to see them duke it out!
[Verizon Samsung Galaxy S III] tehh4ck3r:
All we have is stuff from Samsung support reps saying VZW requested it locked and VZW support twitter saying it was samsung's fault
[Verizon Samsung Galaxy S III] tysdad08:
There is a tweet on droidlife.com from Verizon saying it was Samsung.
[Verizon Samsung Galaxy S III] ScottIsMyName:
Technically that IS true, but it was at Verizon's request....nice try Verizon.
[Verizon Samsung Galaxy S III] skennelly:
Absolutely! Do they expect us to believe that bs. Are we to believe that Sammy had it out for VZW customers when every other mobile provider has an unlocked device! :mad:
[Verizon Samsung Galaxy S III] Schaweet:
Here's to hoping it was all a misunderstanding and we get it officially unlocked. Hahahhaha...... So not gonna happen. Wishful thinking though.
[Verizon Samsung Galaxy S III] CrimsinX:
So VZW wont mind Samsung giving us the encryption/unlock code, right?
[Verizon Samsung Galaxy S III] magnafides:
If they do unlock it, it will be as a result of customer backlash. This is Verizon's M.O.

All I know is, after this contract is up and unlimited data is gone I will be looking for a new provider barring radical changes to the landscape. $350 GNex + Straight Talk looks very appealing right now.
[Verizon Samsung Galaxy S III] AdamLange:
OP updated with latest info. If something need to be added let me know by PM.
[Verizon Samsung Galaxy S III] Hilbe:
Update on The Verge:

http://www.theverge.com/2012/7/9/3147043/verizon-confirms-locked-bootloader-samsung-galaxy-s-iii
[Verizon Samsung Galaxy S III] c4v3man:
My thoughts exactly... if it's Samsung's doing, then they can release the unlock tool without any worries...
[Verizon Samsung Galaxy S III] engelba:
Sorry to be asking a noob question but...

What does it mean technically for the bootloader to be "locked"? e.g. it is encrypted/signed etc...?

Answer or pointers to documentation would be much appreciated... (google search didn't help much :-) )

I've been a Java developer over 10 years now; kind of getting fired up about this and wondering how I can help "resolve" this....
[Verizon Samsung Galaxy S III] rothnic:
http://androidforums.com/evo-3d-all-things-root/342046-encrypted-bootloader-properly-defined.html

Nearly all are locked, many are signed (just allows for an integrity check), and some like the GSIII's are secure. Encrypted is a misnomer, since if it was encrypted, then the bootloader would not be able to be used. It does check file integrity via decrypting the hash of the partition in question.

http://upload.wikimedia.org/wikipedia/commons/2/2b/Digital_Signature_diagram.svg
[Verizon Samsung Galaxy S III] aj8600:
guys if we unlock our bootloaders our connection to the network could fail!?!!? quick stick you heads as deep in the sand as you can an hope the mean bootloader stays locked up
[Verizon Samsung Galaxy S III] rothnic:
I think they are just using the network integrity excuse to deny unlocking the bootloader. I don't think they are threatening what you are talking about.
[Verizon Samsung Galaxy S III] aj8600:
yeah that was my attempt at sarcasm lol
[Verizon Samsung Galaxy S III] engelba:
Gonna guess that have a pretty strong key, salted.....

..was just entertaining the notion what it would take to crack the key with a "SETI at home" approach....i.e. 1000's of home PC's running trying to break the key (screen saver et al). But I'm sure that has already been explored by someone :-)
[Verizon Samsung Galaxy S III] skennelly:
Ridiculous! The only thing Verizon support is good for is telling you to factory reset your phone! Anyone that unlocks their bootloader gets there support from these forums, not some moron vzw employee! :mad:

Vzw is a bunch of good for nothing, no nothing, lying idiots... Rant over.