yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Hipcatjack:
What you are saying does make sense. At least as far as cdma to cdma and gsm to gsm. But (and someone correct me if I am wrong) Sammy hardware is just a whole different beast than the Quietly Brilliant phone maker. I had an og HTC Droid Incredible up until I got this phone a few weeks ago. My Dinc with s-off had Evo Rom/kernels ported to it. Hell coming from the Dinc with CM9 running on it,I was actually unimpressed with The GS3 when I first got it.

I'm starting to come around to loving this phone but it still got a long way to go to be as awesometastic as the original Incredible.

sent from an UNlocked I535!!!
[Verizon Samsung Galaxy S III] ooofest:
My Incredible still has jermaine151's In-Sensitive Minimalist ROM with GO EX Launcher and it can give an iPhone 4s a run for its money (actually, it has on several occasions with my relatives' phones), but a stock Galaxy S III generally runs circles around the Incredible (and, by extension, the iPhone 4s) without breaking a sweat.

I still adore the Incredible, but it had a h/w issue where reboots occur during web browsing or video recording at odd times and this turned out to be a not uncommon issue with that line. It fit perfectly in the palm of my hand and was perfect for stashing anywhere, even though I generally kept it in a holster. Mine is an early AMOLED version, which is of course terrific - my spouse's Incredible 2 was great all-around, but my smaller display beat it for clarity and richness quite markedly.

Nevertheless, my hand has adapted to the much larger Galaxy S III footprint in the past month and the larger display real estate has been a (previously unperceived) much-needed relief for these older eyes. Its everyday speed still amazes me - there's no way an Incredible could download 15 updates from Google Play in the background and not experience significant lag in foreground apps, but this Galaxy S III just whistles along.

I would defend the Incredible's historical strengths to extremes, but feel it's more than a stretch to say it remains competitive with my new Samsung - especially since a bootloader unlock method has been released.

- ooofest
[Verizon Samsung Galaxy S III] salas2324:
Someone tell me if I'm right or wrong. To relock using the EZ method I have to Odin to stock first? Or how would I go about this?

Sent from my Verizon Samsung Galaxy S3 4G LTE
[Verizon Samsung Galaxy S III] jlokos:
The recommendation is stock, but the developer of EZ lock said any stock rom should work (I asked him the same question). Obviously no guaranties!
[Verizon Samsung Galaxy S III] Hipcatjack:
Agreed on everything you just said...

I can not wait to see quadrant scores on an aosp or cm10 with a stream lined kernel!
[Verizon Samsung Galaxy S III] Jaytronics:
Thank you for that download. I am always looking to better my speaking and writing skills.

Or

I always look to better my skills in speaking and writing. Thank you for that download.

I am laughing out loud!

Or

LOL!
[Verizon Samsung Galaxy S III] MichaelVash7886:
Not running stock keyboard, swiftkey. Predictive text was kinda broken already with some of the predictions imo.
[Verizon Samsung Galaxy S III] slickdaddy96:
I ran a Touch Pro 2 with dual boot with gingerbread on the sdcard and it ran as good or better in some aspects as WM6.5 did that was nand. Took the developers forever to reverse engineer everything to get it working, but it worked pretty well once it was stable. So it is definitely a possibility for your devices.
[Verizon Samsung Galaxy S III] OneStepAhead:
Not as far as I know

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

I was ROM crazy on all my HTC devices, but I never ran a single rom on my Galaxy Nexus or Galaxy S II because they didn't seem to need it. I'm feeling the same way about my GS III as well. I went from a ROM a day habit to now cold turkey, lol. Give me root and I'm happy.
[Verizon Samsung Galaxy S III] hotelmrrsn:
broke mine too, downloaded swype beta installer and it's working flawlessly (and better than the stock keyboard imo)
[Verizon Samsung Galaxy S III] ooofest:
Yeah, my Incredible needed some help about a year into its life when Stock updates slowed to a crawl and so did the device; ROMming helped make it fresh and wonderful all over again and it still feels great. Except for the periodic reboots during web browsing or taking videos. So, it's time to upgrade the device.

However, our Incredible 2 has the latest Gingerbread and runs quite smoothly with it - I only needed to root it recently in order to change the DPI for my spouse. It's actually still a joy to use and we both think that Sense is nice for what it is - she isn't missing a thing by not ROMming.

I bought the Galaxy S III for what it can do now and for hopefully running Jelly Bean and gaining Google's voice search capability at some point (even if wrapped by S-Voice) - I'm OK with TouchWiz for now.

That said, one day down the road I'll probably want to go with a raw OS release - here's hoping our Development Wizards can deal with the current bootloader issue for then, and before that time for everyone else here who likes to ROM it up.

- ooofest
[Verizon Samsung Galaxy S III] morrowa2:
Read somewhere the "k" version would be "key lime pie"
[Verizon Samsung Galaxy S III] ikithme:
Heres a question:

Can we still jump in to recovery if the kernel is changed?

If so can we install a new kernel have a custom recovery running, boot that recovery first then have the recovery boot the kernel? Just a thought.
[Verizon Samsung Galaxy S III] rmtobler:
Yea exactly. Development was absolutely essential for my Samsung Fascinate. Without the devs, I would have probably smashed it by now. I am hoping the SG3 doesn't need a rom to fix issues. I would love to run a stable rooted stock rom with my own launcher running over it and be happy.

I'm just worried about getting stuck with jellybean for the rest of the phone's life. Sometimes new software is just as fun as new hardware... :(
[Verizon Samsung Galaxy S III] pwned3:
So do we know if it is encrypted yet? Locked is one thing but encrypted is an entirely different thing. If it is only locked then it's possible that it will be broken into. Encrypted means mine will be sold and I'll buy something with a unlocked bootloadwr
[Verizon Samsung Galaxy S III] mustbepbs:
Stuck with Jelly Bean? How could you possibly think JB is something negative? Will this device get the K iteration? Who knows? JB is seriously boss though. Certainly isn't something to be upset about.
[Verizon Samsung Galaxy S III] droidstyle:
being that a "detected unsupported

software" notification pops up after a custom kernel

flash tells me its encrypted...i may be wrong tho
[Verizon Samsung Galaxy S III] twilight2ner:
+1 While I could most certainly live with root and Nova launcher for a few months, if CM10/AOKP will never be a true possibility, I might just sell this while it's new and pick up a Nexus.

Thanks to all that are looking into this. If you need any testers/data gathered, please feel free to PM me!
[Verizon Samsung Galaxy S III] rmtobler:
Uhm... stuck implies a future situation in which JB = old. If this device never receives JB then we would be "stuck" with ICS......ICS isn't negative but its not JB and JB isn't negative but it isn't (insert newer android version here), being tied to samsung and verizon updates and not being able to stay up to date through dev support = negative......
[Verizon Samsung Galaxy S III] neyenlives:
there are already reports that the GSIII will see JB in 3rd or 4th quarter this year....
[Verizon Samsung Galaxy S III] tehh4ck3r:
If we had an unlocked BL we would probably see it less than a week after source code is released
[Verizon Samsung Galaxy S III] neyenlives:
true, but im ok with waiting if need be
[Verizon Samsung Galaxy S III] 17akota:
But some of us want Google Now, now. lol
[Verizon Samsung Galaxy S III] rmtobler:
That's why my post says "stuck with jb." I expect we get an official JB and that's it. That is what scares me about keeping the phone. The samsung fascinate community had to wait a long time for an official froyo before the devs could get an ASOP working on the phone. it sucks waiting for an official version to drop. plus samsung/verizon support for the fascinate stopped at gingerbread. if the fascinate was stuck on gingerbread I would never have waited this long to upgrade. ICS and the devs gave the phone new life. If we get stuck on JB whose to say the version after JB wouldn't provide the same longetivity.

Anyway this is all conjecture. I still don't have my phone until monday, and after that I have 3 days before leaving on a trip to make a decision based on actual experience and the assumption that I will be stuck with waiting for samsung/verizon.
[Verizon Samsung Galaxy S III] jarnow94:
You can literally get it now lol, I'm pretty sure there an APK you can download.
[Verizon Samsung Galaxy S III] 17akota:
Yea, but voice doesn't work on ICS.... :/
[Verizon Samsung Galaxy S III] ckochinsky125:
since they already have a custom kernel I think that means its not encrypted. I know with moto encrypted it was no where near this easy and still have not been cracked. I think samsung or verizon is going to come out and say something about it. I just cant see samsung all the sudden going from being such developer friendly to all the sudden locking down the devices real hard.
[Verizon Samsung Galaxy S III] jarnow94:
It is encrypted. I didn't read how they got the kernel to work but it was already confirmed that the bootloader was signed and encrypted.
[Verizon Samsung Galaxy S III] amt897:
This was almost certainly Verizon's doing, as they've done in the past, as they will probably continue to do. I mean, they've been doing it for a while. They think it harms the network, so they do what they can to protect their product. Us developers are a small portion of their network-- probably less than a percentage, honestly. Maybe 5% knows what a bootloader is. They wouldn't care if we left. We probably use more data, anyways, and pay the same amount. The issue is that by pissing off developers they also lose app support, but considering Google Play is across all carriers... won't do much.

But I digress.

They haven't gotten a custom kernel on it. From an earlier post it appears that system.img and cache.img are not encrypted, but boot.img and recovery.img are. So we have root and CWM. I'm not entirely sure how recovery.img is encrypted if we have CWM running, but boot.img definitely presents problems.

That means every time you boot up your phone, it makes sure boot.img has the same encrypted signature from Samsung. The encryption means we cannot fool it (easily). That is very, very difficult to break. Workarounds have been found, but they usually require a leak. Considering Samsung is probably not liking this (they probably get flak from devs for having to lock a bootloader), we can hope for someone disguntled enough to leak something. Otherwise, it may never be able to have full custom kernel, ROM, and radio support.

That is the state of affairs. But have faith in your developers, these guys are awesome.
[Verizon Samsung Galaxy S III] tonu42:
Dude, recovery isnt touched by anything. Obviously if we have CWM than its not.
[Verizon Samsung Galaxy S III] amt897:
Yeah, I was going off the OP's thing, but then I sort of stopped mid-typing to think about that. Clearly it's just boot.img that's encrypted.
[Verizon Samsung Galaxy S III] ddggttff3:
Heres whats going down. when you flash with ODIN it checks boot.img and recovery.img to make sure they are VZW/Samsung approved. If not, flash will fail. the good news is system.img is NOT checked when flashed, and this is how you get root. When you get root, you are able to manually flash images using ADB and the dd command. Now, from there you can FLASH ANY IMAGE... but with a catch. The bootloader checks boot.img on startup to make sure its not modified, but nothing else. This means we are able to flash our recovery, and boot it without any problems. This also means we are not able to just flash a new kernel though until we find out what is checking the boot.img file on boot.
[Verizon Samsung Galaxy S III] amt897:
Thanks for the clarification. I'm new to Samsung development and have only used adb, not Odin.
[Verizon Samsung Galaxy S III] NAU420:
Like the Rezound, before we got o-off by the use of a piece of wire. We could flash any rom and Kennel, but only by ADB commands. If thats the case I could live with the S3. Is this right??
[Verizon Samsung Galaxy S III] ddggttff3:
as I said, you CAN FLASH a custom kernel, but the phone WONT boot with it. it will boot into odin saying unapproved software. At this point you will have to flash back the stock boot.img to get your phone to turn back on.
[Verizon Samsung Galaxy S III] ExodusC:
If this is accurate, that means that ROM development really shouldn't be hindered at all, correct?

We should be able to do every single thing an unlocked bootloader SGS3 could do with the exception of modifying the bootloader itself, right?

For that matter, modifying the bootloader is pretty much never bothered with, is it?
[Verizon Samsung Galaxy S III] tekhna:
It will be greatly hindered because, as of now, we can't flash kernels. No AOSP kernel=no AOSP/AOKP. It probably won't affect Touchwiz ROMs much at all, but could put a damper on everything else.
[Verizon Samsung Galaxy S III] ExodusC:
Ah, right, I had read that as "can flash a kernel" rather than cannot.

I'm hoping there can be a workaround.

Doesn't the Droid RAZR's kexec hack allow the booting of an unsigned kernel?

I guess there's the possibility of something like that.
[Verizon Samsung Galaxy S III] Flowah:
The Droid2/X have AOSP/AOKP roms though, and they can't change kernels.
[Verizon Samsung Galaxy S III] ooofest:
I'm still learning here, but is the issue that the phone is locked AND the bootloader has a signature . . . a signature that is encrypted?

Something is checking that signature at boot and we don't know the private encryption key (or even method?) shared, I thought. This means we can't realistically offer up an encrypted signature of our own unless Samsung gives us a hand - therefore, need to figure out how to bypass the boot-time signature check entirely if we want to use non-stock ROMs.

Am I getting close?

- ooofest
[Verizon Samsung Galaxy S III] stiltzkin:
Yes, you're getting close. We thought the verification might be as simple as a CRC32 check of boot.img, so we tried loading both invisiblek's unsecure kernel and the bootloader dump from Sprint's version hacked to generate the same CRC as the stock bootloader. Neither image will flash via ODIN, and if written directly with dd the phone just doesn't boot. So at this point I believe all we know is that it's not a simple CRC check - that would have been too easy.

And just to reiterate, invisiblek has got a custom kernel up and running on the phone - it just can't be written to boot.img, it has to be written raw over the recovery partition to trick the phone into launching from it. It remains to be seen how useful this will actually be in getting a fully custom system loaded.

There's also word that a kexec method for chainloading an insecure kernel is being actively worked on - I'm staying tuned for this as well.

Hang in there guys.
[Verizon Samsung Galaxy S III] NAU420:
Thanks for the updates and I have hope. I was with the rezound guys and 6 months later we got s-off. I was just hoping for the same with the others "unlocked bootloader".
[Verizon Samsung Galaxy S III] Copyright5:
I'm pretty sure that that's because of a 2nd init recovery. It works kind of like a separate kernel but it's not.
[Verizon Samsung Galaxy S III] skennelly:
I don't think that anyone believes there is something wrong with JB. However, There are many phones stuck on GB. I think the point is, eventually there will be a newer/better update that this phone will not receive. If you want this update you'll need to purchase newer hardware. Those of us that preordered this phone likely did it to keep unlimited data. A new phone means either paying full retail, or loosing unlimited data.
[Verizon Samsung Galaxy S III] walloftvs:
Flash any image? So what is stopping us from flashing a different bootloader via ADB?
[Verizon Samsung Galaxy S III] Coop9:
That's my thought, with so many other phones with very similar hardware, it seems like it might be easier than if you only had a single device around.
[Verizon Samsung Galaxy S III] NegativeOne:
I'm not sure I understand your question. It seems like the previous post answers it. There are still checks.
[Verizon Samsung Galaxy S III] ikithme:
Boot.img is checked EVERY boot.
[Verizon Samsung Galaxy S III] AdamLange:
not exactly boot.img but boot parition containting kernel :) even when u do dd directly to partition it will not pass.
[Verizon Samsung Galaxy S III] invisiblek:
If you flash a bootloader that is not signed, you will get this: http://tinyw.in/RAk9

Someone tried this yesterday but flashing a sprint bootloader. Then ended up with <see above link>
[Verizon Samsung Galaxy S III] Stephen.k.spear:
You know with the fascinate/mesmerized the bootloaders were identical. I wonder if ucss plans on screwing their customers as well. Also have you guys though about packaging a recovery in the custom boot.img. Sorry I didn't read through the last few pages, just tossing ideas up.
[Verizon Samsung Galaxy S III] piiman:
You have to wonder why they go to all this for s such a small group of people. On top of that they end up taking returns for bricked phones because they won't supply the tool for us to his them. I'm surprised Samsung agreed to do it. they're big enough to tell vz to bug off and tell them "fine you don't want it we'll just let all your competitors sell it" oh well i had a dx and had plenty of stuff to flash.
[Verizon Samsung Galaxy S III] tonu42:
They're getting their dont worry. I also said the exact same thing in IRC where USC and VZW have same bootloader.
[Verizon Samsung Galaxy S III] skennelly:
Absolutely! There would have been plenty of people leave VZW over this phone. VZW would keep the people they want as customers and the rest of us would have moved to a provider that gave us some freedom.
[Verizon Samsung Galaxy S III] neh4pres:
Ok. Don't know what I did. But I now have the unlocked symbol splash screen and it says custom under it. All I did I think, was root and freeze bloat with tb
[Verizon Samsung Galaxy S III] walloftvs:
Bummer.
[Verizon Samsung Galaxy S III] NegativeOne:
There is at least one other person who has reported this. It seems like the usual case: There were a few unlocked models shipped accidentally. Are you sure it wasn't this way from the beginning for you? Try flashing an AOSP rom.:)
[Verizon Samsung Galaxy S III] piiman:
Damn! You cracked it by removing vz bloat! Good job! Lol
[Verizon Samsung Galaxy S III] AdamLange:
It's too easy to become true. checks are in bootloader so removing VZN bloat will for sure not unlock it :)
[Verizon Samsung Galaxy S III] RXWatcher:
Could we use jtag to 1) read the boot partition from a locked unit(verizon) and compare it to a non-locked unit(sprint) 2) watch the boot sequence to see where the check is?

At least we have multiple wireless providers for this phone. Its not like verizon is the only cdma provider.
[Verizon Samsung Galaxy S III] tonu42:
That would I'm pretty sure 100% work. But two things.

1. Who would take there phone apart? I know. Adamoutler, but he doesnt have it I dont think.

2. Even if we find out where and what, what if it is indeed encrypted?
[Verizon Samsung Galaxy S III] ddggttff3:
what im wondering is if the VZW and att/sprint model share the same sbl1, sbl2, and sbl3 images. I mean, if we had dumps from all 3 phones, compared them, and att/sprint have the same, we could say that these may possibly hold the bootloader check code. I mean, p2 (sp1) is right after the modem, and if I remember correctly, doesnt the phone boot in partition order? 0, 1, 2 etc?
[Verizon Samsung Galaxy S III] NegativeOne:
Cool idea, but I bet they are all different :-(. Still worth a shot
[Verizon Samsung Galaxy S III] Imatoasta:
I bet somebody out there with a broken screen would be down for it since they have to take the phone apart anyways.
[Verizon Samsung Galaxy S III] neh4pres:
So other people are not getting the unlock splash after root? I wonder what I did lol
[Verizon Samsung Galaxy S III] ddggttff3:
thats a good question lol. I removed all vzw bloat and put a different bootanimation.zip on mine, and I still dont have the custom boot thing.
[T-Mobile LG G2x] droid_genius:
Hello so I tried to put genesis ics rom on g2x and followed instructions, now its stuck on his rom lg logo(meaning it shows lg logo, then shows custom logo) and I cant get into CWM either, any direction would help
[T-Mobile LG G2x] djvoleur:
What steps did you take because if the you followed the steps, it would boot.

Also, when you say you can't get into cwm, what does it say/do?
[T-Mobile LG G2x] zoppp:
Does it show some grip reaper?

Sent From My Handheld Portal Device
[T-Mobile LG G2x] droid_genius:
So after hours of being up all night, I fixed it.....I was sooooo happy I was able to get CMW Recovery loaded on there through CMD prompt but at 1st it was gone cause I didt know that ROM manager put a fake recovery on there, so did it manually and put a new rom on sd card and now it works back to 2.3.4 stock rooted, but thanks for responses all
[Galaxy Ace S5830 General] InverseSandwich:
Check this out - It's the cooper changelog for CyanogenMod... 9!

http://changelog.bbqdroid.org/#cooper/cm9/next

Seems strange though, as it has fixes for SII.
[Galaxy Ace S5830 General] madman:
bbqdroid do not speak truth and no device with memory less than 512mb and especially msm7k is going to get official cm9 until some older device gets official ics which will not happen
[Galaxy Ace S5830 General] InverseSandwich:
Kinda seems too good to be true.

It seems to be a mish-mash of other devices, for example, it uses SII RIL and has Tegra 3 drivers. Strange.
[Galaxy Ace S5830 General] K.A.:
You will get the same changelog for any device you select...thats not specifically for the Ace..
[Galaxy Ace S5830 General] tomsons26:
This was already discussed once ITS A AUTOMATED SCRIPT! :mad:

http://xdaforums.com/showthread.php?t=1729769&page=3

http://changelog.bbqdroid.org/#OMG_CM9_FOR_COOPER__NOT/cm9/next lol
[Galaxy Ace S5830 General] InverseSandwich:
Just realized that.

Shame though.:(
[Android Q&A, Help & Troubleshooting] sirlancelot166:
Been searching for answers and ways to implement H/W acceleration for video decoding(eg. H.264) in my own app for a long time, but got no clue.

I want to call H/W decoding based on NAL or frame level over raw bitstream, rather than setting up a media player for files.

Anyone can share this information? Many thanks!
[Desire Q&A, Help & Troubleshooting] grandmaster_b:
Hi guys I partitioned my card with minitool partition wizard and have since found out it is not recommended because it doesn't align partitions so if I use EXT4 Touch recovery to create and format the align/partitions is that ok or are there known problems too ? and if I do a NANDROID backup of existing unaligned partitions when I restore onto the newly partitioned aligned card will it put the partitions out of alignment or is the restore just smoke and mirrors copy paste ?
[Desire Q&A, Help & Troubleshooting] handy5876:
Best to do partitioning only with gparted. Gparted comes also in a small bootable live Linux cd. Download the ISO, burn it to cd, boot from it on pc. Before you boot connect desire with sdcard connectivity.

Sent from my HTC Desire
[Desire Q&A, Help & Troubleshooting] grandmaster_b:
Just thought I would let anyone else know that is interested:-

I used EXT4 Touch Recovery to create partitions,align format etc and then restored a NANDROID backup which I took on the card while it was not aligned so I can confirm the following so far:-

1) EXT4 Touch Recovery is the quickest easiest way to partition, format align your SD card.

2) The NANDROID backup is smoke and mirrors copy paste because it left the new slightly larger partition as is and fully aligned !