yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] juryben:
Is there a technical explanation of the booting processes and a site documenting the information? I'm tempted to host a wiki dedicated for this like free360.
[Verizon Samsung Galaxy S III] p-slim:
This thread is only for bootloader development process. If you have questions about bootloader take it to the q&a forum. Where are the mods when you need them
[Verizon Samsung Galaxy S III] myredfast:
Read the title "Research and News". It not "No questions and all post have to be approved by _________(insert name here)"
[Verizon Samsung Galaxy S III] kman79:
How is talking about issues with the Current CM9 Build, or Rooting, or Loosing Data relevant to "Locked Bootloader Research and News"?

There are other threads specific to CM9 Builds, Rooting, and Data Loss due to flashing of CM9 builds. This thread was the premier resourceful thread with active development on unlocking the bootloader, now it's gone to Jibber-jabber

Like the others have said, the last couple of pages have had nothing to do with R&D of unlocking or news regarding bootloaders. I haven't read a single post from the Devs working on the Bootloader in days. I'm hoping they haven't given up on it.
[Verizon Samsung Galaxy S III] AlexDeGruven:
The real work is going on under the "Original Android Development" section. So far, that hasn't been pooped all over yet.
[Verizon Samsung Galaxy S III] ali87va:
That's meant only for the devs who are actively involved in unlocking, this thread basically is for people who have ideas or news about BOOTLOADERS.
[Verizon Samsung Galaxy S III] LLStarks:
What ideas?

All I see is garbage speculation.
[Verizon Samsung Galaxy S III] Rob_Storm:
Can we get a mod to clean this thread please? Including this post of mine.

Maybe just create a random discussion thread and move all irreverent posts there so folks don't get upset their post was deleted.
[Verizon Samsung Galaxy S III] Srambo217:
If you guys would have looked at few pages back, you would have seen my post:
[Verizon Samsung Galaxy S III] ali87va:
That's what I'm sayin
[Verizon Samsung Galaxy S III] myredfast:
Somehow I knew there were going to be at least 5 more useless posts after mine, including mine. That made me LOL. Mods please delete!
[Verizon Samsung Galaxy S III] Deevious88:
http://xdaforums.com/showthread.php?t=1769411

That's the real R&D thread in my eyes. This thread is for news/discussion... Or am I the only one who seems to think that?
[Verizon Samsung Galaxy S III] Div033:
Having gone to forum police academy for five years, I know a thing or two about what's on topic and what's not. In boot camp, we learned about tangential subjects. While discussing CM9 and installing it is not directly related to the thread subject, it is still along the same lines because it deals with circumventing the bootloader, thus providing news on how it works. Starting a discussion about how the thread is not on topic, such as this, does more harm than it does good. These are empty posts and contribute nothing. At least before people were discussing something.

I'd like to flash my badge and show everyone to the R&D thread AdamOutlier started in the Original Android Development forum. That is an uncluttered thread with only devs posting and will be your best source for news. It would be pointless to post the "news" here when it's readily available in a neighboring thread. Because of this, this thread has become more of a bootloader general discussion and all things related, such as how kexec works to circumvent the bootloader and CM9. Maybe such a thread doesn't belong in Android Development, but it's remained here still.

At least that's how I saw it until the big stink was made. Now it's empty discussion.

The forum police bit was sarcasm for those less perceptive.
[Verizon Samsung Galaxy S III] NegativeOne:
I kind of think this thread should be locked. If people want to discuss different stuff they should make specific threads.
[Verizon Samsung Galaxy S III] NFSP G35:
....so 3 pages of griping about the thread being off topic is better than the so-called 'off-topic' posts themselves? This concept confuses me.

Personally, I'm perfectly happy to hear about CM9 running on the S3. I mean workarounds are every bit as viable part of "news" about locked bootloader as unlocking it is. Especially considering that my ultimate goal for this phone would be to have 100% working CM10, whether that's accomplished via hacking an unlocked bootloader or coming up with a work-around, I could care less.

And pressure on / responses from Verizon wireless directly relate as well.

So why doesn't everyone taking their own post to complain about the OT step back and ask if you're being part of the solution, or part of the problem.
[Verizon Samsung Galaxy S III] NegativeOne:
Everything is valid for being discussed. Why do you have to discuss it here? It would be more productive if you discussed it in an appropriate thread. You don't go to a dentist about a foot ache.
[Verizon Samsung Galaxy S III] Noxious Ninja:
No, but you might not go to a general practitioner to discuss your footache, either, unless there's no podiatrist around. The Verizon Galaxy S III is different than the rest, it needs its own discussion forum.
[Verizon Samsung Galaxy S III] NegativeOne:
Whatever. I'm done with this thread. All of the people who actually have anything important to say have given up on this thread. The rest of you clearly don't know what a bootloader is, or can't read. Thanks for making these boards a little worse for everyone else.
[Verizon Samsung Galaxy S III] Div033:
Now now, there's no need to get nasty. We're all adults here and I'm sure many people understand what the bootloader is.

This is simply the thread where discussions have taken place as a result of the new forum structure. All this thread needs is to be renamed and all would be well. The research and news is being very strictly moderated in the Original Android Development forum and its purity is surprisingly high. As a result, this thread took on a different purpose to be the discussion of all things related to flashing roms and bypassing the bootloader.

Back on topic, I'd like to talk a little bit about kexec and what people should expect.

Earlier tonight I took the plunge and flashed CM10 and boy are we in for a treat once all the kinks get worked out. Cvpcs has created a boot hijack for kexec based roms that is almost completely automated. All you need is an auto-kexec compatible recovery (CWM 6.0.1.0) and you're all set. Just flash the kexec enabled rom and boot as normal. Now what actually happens after you reboot from recovery is 3 automated reboots. One to "boot" into recovery, another to execute the kernel and a final one to boot into the rom of choice using said kernel. Furthermore, I tried doing a cold boot and it went straight to recovery, where I had to physically select the reboot option to start the aforementioned sequence.

This results in a significantly longer boot time, but understand it's all we have right now. I still look forward to a bootloader unlock but am definitely willing to live with this compromise should it not be doable. It's also important to note that if you restore/flash a touchwiz based rom then the kexec sequence no longer executes, resulting in a standard boot time. It definitely is working well and can only improve over time.

As far as CM10, yum. Things are definitely smoothed out in some areas like scrolling through lists and Widgets. Google now is amazing too. Our device flies on it. Unfortunately there are still several issues that I personally experienced relating to MMS and camera that brought me back to stock, but hey that's alpha software for you.
[Verizon Samsung Galaxy S III] Poloasis:
Great news mate. Btw where can I follow a thread on CM10?

Thx.
[Verizon Samsung Galaxy S III] aj8600:
I would be very cautious about flashing anything but touchwiz based roms atm. Huge RIL problems have been found. Many people are seeing a complete loss in data (sometimes irreversible)

Proceed with caution people. At least until a proper fix has been found
[Verizon Samsung Galaxy S III] NegativeOne:
Please post a link to what you are talking about. This is the first I hear of permanent data loss
[Verizon Samsung Galaxy S III] aj8600:
http://xdaforums.com/showthread.php?t=1785286

but most of what i have heard has come from irc. they have take down the links to the cm9 cm10 and aokp 4.0 for saftey
[Verizon Samsung Galaxy S III] Div033:
Yes I highly recommend against flashing aosp roms right now til the IMEI issues are resolved.
[Verizon Samsung Galaxy S III] jmotyka:
i believe this was just a cm9 problem, i could be wrong, i havnt heard any cm10 people have this problem, im talking people who never flashed aokp or cm9, im saying people who came from stock/root to cm10 have not had the data woes everyone else is. I have flashed two different cm10 builds in three days and not once did i loose data or my IMEI. I think the problem is happening when people are going out of their service area then roaming and then coming back into their service area to be honest. Again i could be wrong. But for me cm10 is flawless, SMS and MMS work for me, the only issues i suffer from is backlights for the keys are not functioning, haptic feedback is on crack, and stock camera app is not working. I downloaded cameraFX and taking pictures with no issues, im positive within the next week all these issues will be ironed out. As far as the rest of this thread is concerned i truly believe the major issue is there are to many people in the android community who dont know what they are doing. They are uneducated as to why the android development community is here and how it functions, they also dont know what to do when their phones get borked because the developers make it easy for us to flash. Those kind of people do it for the thrill of it(which is fine) but you should also be educating yourself and learning the inner workings of a rom, start learning java/android/kernel development and help out, we are not here to entertain you so you can entertain your friend!
[Verizon Samsung Galaxy S III] Div033:
There have been first hand accounts of the issue occurring on CM10 in irc. Flash at your own risk.
[Verizon Samsung Galaxy S III] jmotyka:
But did those ppl have cm9 or aokp or heavily modified TW installed? A couple of our TW roms are actually international roms made to work on the vzw rom and they could have left something in the rom that was doing damage behind the scene.

IDK what the problem is but i do know that someone is doing something wrong!
[Verizon Samsung Galaxy S III] Cvballa3g0:
I flashed the cm9 Rom right in my bedroom. I have never roamed before in my house or anywhere in the city.

As for experiance, this also happened to invisiblek, but he was able to get back to normal.
[Verizon Samsung Galaxy S III] neyenlives:
How? You can't jump in here saying so and so got hit by this but was able to recover without sharing details!
[Verizon Samsung Galaxy S III] NegativeOne:
IDK about you but I will take a bricked phone over getting hit by a bus
[Verizon Samsung Galaxy S III] Cvballa3g0:
All in my thread. http://xdaforums.com/showthread.php?t=1785286
[Verizon Samsung Galaxy S III] codyvance:
:::Crickets chirping:::

Sent from my Verizon Galaxy S3

Running the kick ass Synergy 1.6 with lean kernel .1, aosp apps, and locked bootloader.. F u verizon
[Verizon Samsung Galaxy S III] niv3d:
Or you could follow here but you can't post unless its beneficial to the goals

http://xdaforums.com/showthread.php?t=1769411
[Verizon Samsung Galaxy S III] codyvance:
Ya i follow that thread too .. Those guys are crazy smart, it's interesting to read their posts.

Sent from my Verizon Galaxy S3

Running the kick ass Synergy 1.6 with lean kernel .1, aosp apps, and locked bootloader.. F u verizon
[Verizon Samsung Galaxy S III] meishkov:
Exactly what I was just thinking of posting. Those guys know more stuff about our devices and their inner workings than Samsung does. Insane how much info is getting exchanged in there, it sucks for me cuz I'm helpless when it comes to editing any kinda complex software like that, shoot I don't think it's even as simple as software its like built-in commands in the hardware and what not. Extremely interesting following that thread, I can only hope to eventually get a new pc that's capable of dev'ing so I can just start learning some of the basics. Thank goodness we're all drawn to this stuff naturally, otherwise I'd hate to have to cover the bill for those guy's intelligence at an hourly rate!! :)
[Verizon Samsung Galaxy S III] faehsemc:
I think we need all that thread reproduced in a dumbed down version.. I have no idea what half of that means
[Verizon Samsung Galaxy S III] mike86325:
lol agreed. I try keeping up on it, but I can't tell if we are winning or losing the battle from anything I read
[Verizon Samsung Galaxy S III] xerxax:
Same. I'm not sure if we are making progress or not. It sounds positive as we get more information from manuals and junk but no one there is like, "ya, I think with this information we can unlock the bootloader and then create an auto-packager which will circumvent the bootloader and allow custom ROMS." All the information is techno-gabber and beyond me, they need a simple 10 number scale that shows how close they are the closer they get to 10. I don't know how it works but a got a "Grant" in my pocket for whoever figures it out and then explains it to me in a way that I can use it, lol. Gosh, I'm so noob. At least I got the moniez.
[Verizon Samsung Galaxy S III] NegativeOne:
It sounds like they have been talking more about ways to unbrick than making actual progress.
[Verizon Samsung Galaxy S III] meishkov:
Their knowledge and expertise would make NASA scientists jealous
[Verizon Samsung Galaxy S III] NFSP G35:
Maybe you should see here: http://xdaforums.com/showthread.php?t=1760568
[Verizon Samsung Galaxy S III] AdamOutler:
If you take a look at the first post in the R&D thread, you'll see thats part of the plan.

Having a way to unbrick a without JTAG is a bigger deal than anything... even the final goal. Developers suddenly grow e-balls and are able to test anything without fear. That's the reason locked bootloaders are so volitile to work with. If you screw something up, you're dealing with recovering locked hardware. That's much worse than trying to recover unlocked hardware.

However, I'm only going to be playing with this for another day or so before I resurrect my device.
[Verizon Samsung Galaxy S III] Hypnosis4U2NV:
Keep doing what you do Adam.. Along with E:V:A and Ralekdev, you guys are making some good progress and if anything, some interesting reading in that thread..

Sent from my Commodore 64..

READY.

load"*", 8,1
[Verizon Samsung Galaxy S III] xXJay_RXx:
My brain hurts just by reading that thread
[Verizon Samsung Galaxy S III] codyvance:
Lol same..

Sent from my Verizon Galaxy S3

Running the kick ass Synergy 1.7 with lean kernel .1, and locked bootloader.. F u verizon
[Verizon Samsung Galaxy S III] Schaweet:
I read it like I'm following it and then when I'm done I'm like WTF did I just read? Oh well, I bet they can't design airports like I can lol.

Sent from my Synergy GS3
[Verizon Samsung Galaxy S III] sasquatch080:
Wait wtf. You can design airports? Now I'm left with wtf? All I can do is tattoo. Lol. That thread is mind boggling.
[Verizon Samsung Galaxy S III] DROID3R:
Designing airports?? Thats easy. Umm long runway.... some gates..... some terminals a big parking lot.... done .

VERIZON GALAXY S 3
[Verizon Samsung Galaxy S III] con247:
You forgot the area where we get felt up by the TSA.
[Verizon Samsung Galaxy S III] Hipcatjack:
What adam said is correct, being able to recover from a brick without jtag/uart capabilities is crucial for development.(For those that don't know what that means, it's basically opening up your device and accessing the actual hardware through special wires to "read/write "to the device.) We are just lucky he COULD get unbricked via that option. As far as "progress" that in of itself was a learning experiance. I know he got slack for even taking that risk. But what the hell is hacking good for if you aren't willing to take some risks right?

I'm not going to pretend I can follow all of what's going on in that thread, (Pharmacy background and all) but the leaked hardware manuals was huge and so too was was a lot of the data dumps.

As far as a number scale it would seem like we are a solid 8 or 9 out of ten. But with a caveat... the scale could be linear or it could be exponential... where the closer to 10(our goal) we get, it gets harder and harder to make progress. I.e. approaching the speed of light. Only time can tell.(pun intended)

sent from a locked down bootloader
[Verizon Samsung Galaxy S III] jdhas:
I see what you did there....
[Verizon Samsung Galaxy S III] jdhas:
This seems important:

http://xdaforums.com/showthread.php?p=30274025
[Verizon Samsung Galaxy S III] slvfox:
The SIII bootloader has been unlocked. See this post from Adam. http://xdaforums.com/showpost.php?p=30274025&postcount=317
[Verizon Samsung Galaxy S III] xsteven77x:
Holy hell they did it.
[Verizon Samsung Galaxy S III] irtehun:
Now how do we tell if it applies without a kernel to test on?
[Verizon Samsung Galaxy S III] jdhas:
Patience, grasshopper.
[Verizon Samsung Galaxy S III] NegativeOne:
What do you mean? We have plenty of kernels. Can't we then just flash a kernel from one of the other GS III roms ?

Actually, re-reading Adam's post, I'm a little bit confused. What's the story here? If it's unlocked, why didn't Adam just flash a kernel from CM10 or AOSP or something? Why use a Sprint BL ?

He talks about handing it off to some dev for completion, but what's left???
[Verizon Samsung Galaxy S III] morpheousrx:
Well im stoked...and no paperclips involved...(rezound users chuckling)
[Verizon Samsung Galaxy S III] xsteven77x:
Shouldn't it no longer say secure boot or unsecured or something in odin mode now? Getting ready to flash so i'm gonna find out.
[Verizon Samsung Galaxy S III] irtehun:
Hah I remember having to do that!
[Verizon Samsung Galaxy S III] Hilbe:
Made a post in the CM10 thread in the Original Development forum for those of you who are already on a custom ROM. Will help you get unlocked aboot.img flashed manually. Should work for anyone with ADB, not require Mac/Linux.

http://xdaforums.com/showpost.php?p=30276359&postcount=492
[Verizon Samsung Galaxy S III] codyvance:
Getting really excited after Adams post.. It will be so awesome to give Verizon the middle finger

Sent from my Verizon Galaxy S3

Running the kick ass Synergy 1.7 with lean kernel .1, and locked bootloader.. F u verizon
[Verizon Samsung Galaxy S III] wera750:
Just flashed with terminal

sent from locked bootloadrer SGS3 running a custom kernel :)
[Verizon Samsung Galaxy S III] bucsfann20:
http://www.androidcentral.com/veriz...longer-issue?utm_source=ac&utm_medium=twitter

Not sure I'm allowed to post here, but saw this and thought it deserved the attention of the devs here.

Edit** Disregard. Just read above. Great job.
[Verizon Samsung Galaxy S III] Kreeker:
I literally screamed when I looked at my tapatalk and saw someone mention the bootloader was unlocked in another thread.
[Verizon Samsung Galaxy S III] Hilbe:
Here's how to do it manually without CASUAL. All credits to Adam.

From a computer with adb on a rooted device:

adb push aboot.img /sdcard/aboot.img

adb shell

su

dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5

Also can be done via downloading the attachment, putting at root of /sdcard/ and doing these commands in terminal on a rooted device:

su

dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5

MD5 (aboot.img) = 0ba9ad45fc15cf3d62af7dd363686b3f
[Verizon Samsung Galaxy S III] salas2324:
Ditto

Sent from my Verizon Samsung Galaxy S3 4G LTE
[Verizon Samsung Galaxy S III] NegativeOne:
So can we flash kernels without kexec now?
[Verizon Samsung Galaxy S III] Schaweet:
SO I did this and rebooted and all went fine (booted faster btw). Now how do I check to see if it worked, lol? Does this mean fastboot is now enabled instead of secureboot?

Edit: Just booted into odin mode and still says secure boot enabled. Must just be the hackery.
[Verizon Samsung Galaxy S III] codyvance:
Lol really?

Sent from my Verizon Galaxy S3

Running the kick ass Synergy 1.7 with lean kernel .1, and unlocked bootloader.. F u verizon
[Verizon Samsung Galaxy S III] faehsemc:
let's get some mutha f'n MIUI now!!!!

Thanks to all who cracked it
[Verizon Samsung Galaxy S III] Jihoonie:
Ditto. Want some MIUI on this bad boy
[Verizon Samsung Galaxy S III] MrJobs:
Flashed the aboot now the custom icon is gone and phone boots faster.
[Verizon Samsung Galaxy S III] bc760:
Is this real lol can't wait to get home tonight.
[Verizon Samsung Galaxy S III] Schaweet:
Yeah I noticed the faster boot but yeah my custom icon is gone too. Can't wait to get some custom stuff on here. I guess custom kernels already exist and could be flashed via CWM. I wonder if TWRP wrks too. Hmmmm......maybe I'll test. Kind of scared though lol.

Sent from my SGS3 on Synergy Nightlies
[Verizon Samsung Galaxy S III] bryantwc1:
Same here. This is awesome. The method of doing it in terminal emulator on the phone is very simple
[Verizon Samsung Galaxy S III] TheBiles:
Just worked perfectly from AOKP! No more boot delay!

Sent from my Nexus 7
[Verizon Samsung Galaxy S III] s197:
You mind posting the MD5 please?
[Verizon Samsung Galaxy S III] Schaweet:
This is what I got

0ba9ad45fc15cf3d62af7dd363686b3f

Sent from my SGS3 on Synergy Nightlies
[Verizon Samsung Galaxy S III] dchurch85:
How can we tell if it worked?
[Verizon Samsung Galaxy S III] salas2324:
When phone turns on you shouldn't see an unlocked padlock under "SAMSUNG"

Sent from my Verizon Samsung Galaxy S3 4G LTE
[Verizon Samsung Galaxy S III] je2345:
Love this method! Worked while running Synergy Nightly. When you reboot you will see the padlock no longer shows up and you boot up in like 10sec
[Verizon Samsung Galaxy S III] s197:
Thank you.
[Verizon Samsung Galaxy S III] Hilbe:
md5 aboot.img

MD5 (aboot.img) = 0ba9ad45fc15cf3d62af7dd363686b3f

Will add to the post.
[Verizon Samsung Galaxy S III] bc760:
I've been rooted since day one and NEVER had the pad lock?
[Verizon Samsung Galaxy S III] xsteven77x:
Ya I was gonna say, is their any other signs for those of us who never had the custom pad lock?
[Verizon Samsung Galaxy S III] Hilbe:
Boot time is insanely quick.
[Verizon Samsung Galaxy S III] KennyCap:
Not for nothing but I've only flashed Synergy with invs kernel and have yet to see the unlocked screen. My device did say modified though.

I got the bytes in out in .045 sec I'm assuming it worked. Could we adb reboot bootloader?

I used terminal.
[Verizon Samsung Galaxy S III] Schaweet:
You could try flashing a custom kernel in CWM that doesn't do kexec and report back to everyone. Come on..... Take one for the team lol. Do it!

Just don't blame me if it doesn't work.

Sent from my SGS3 on Synergy Nightlies
[Verizon Samsung Galaxy S III] PJnc284:
I didn't get it until flashing CWM 6.0.1.0 with EZ Recovery but can confirm that the Custom boot screen is indeed gone. I kind of miss it though. :laugh:
[Verizon Samsung Galaxy S III] bc760:
Lol you do it
[Verizon Samsung Galaxy S III] inline6power:
Everything works great. Kexec is a thing of the past now

sent from my galaxy s3
[Verizon Samsung Galaxy S III] Schaweet:
I'm skerd. I'll let someone else do it and let me know how it goes.

Sent from my SGS3 on Synergy Nightlies
[Verizon Samsung Galaxy S III] 1ManWolfePack:
Wow.

I never thought I'd see the day. I can't believe how fast this puppy boots :)

I'm going to go into download mode and read what it says in there. Might be a good place to see if it "worked" for some...
[Verizon Samsung Galaxy S III] KennyCap:
Funny four of us in a row no padlock
[Verizon Samsung Galaxy S III] Schaweet:
Still says secure boot enabled for me. Not sure what else would change.

Sent from my SGS3 on Synergy Nightlies
[Verizon Samsung Galaxy S III] TechBSwift:
make that 5
[Verizon Samsung Galaxy S III] PJnc284:
No difference in the download mode info. Only difference I've noticed is that my custom boot screen is now gone and no longer bootloops.