yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] zachf714:
Question is, is that check part of the ramdisk(the pem file) or is it part of the security in the kernel, and I guess the best way to check is to look through the security section but I don't have a system currently to build on because I am in the process of a rebuild
[Verizon Samsung Galaxy S III] open1your1eyes0:
Wow I guess they figured out our workaround method. Touche Samsung.
[Verizon Samsung Galaxy S III] scrawnyb:
UPDATE: Answered my own question here regarding source code.

It's available @ http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SCH-I535 as SCH-I535_NA_KK_Opensource.zip

Anyways, it looks like we would need patches to 2 places here.

The source code that I believe needs patched should be in: drivers/usb/core/generic.c and drivers/hid/hid-picolcd.c

Maybe someone can write some in-memory patches to skip these checks?
[Verizon Samsung Galaxy S III] Surge1223:
It has been pointed out to me that our current approach isn't the best. We need boot logs to see where the kernel is actually failing before we can consider the possibility of patching the kernel. Ill grab these logs myself soon. I have a complicated situation with my s3 (a family member is currently using it) so I have to wait until I can borrow it to test. If anyone has any boot logs (whether it be last_kmsg, last recovery log, seclog etc) after attempting to boot with the 4.4.2 kernel then please upload them in the mean time (preferably via pm to not clutter this thread) Thanks!
[Verizon Samsung Galaxy S III] Surge1223:
Hi, I'll give an update on the situation, also I've been able to use my s3, and others have sent me logs (you guys have a great s3 community BTW) also i may have forgotten to say thanks to those sending me logs etc, sorry.

We know this zImage is an odd cookie...I've been looking at it and I have consulted other parties more skilled than I am in this field and its taking a bit of time to get a read on what's going on with the kernel failure. Sorry if it seems progress is slow, and unfortunately some of this is attributed to this not being the highest priority for a lot of us. That doesn't mean we're not trying, just progress has been slow. I will try to work on this today and see if I can give you guys a better update within the week.
[Verizon Samsung Galaxy S III] VECTUS:
I've cleaned up the thread a bit. ONCE AGAIN, if you are not a developer (donating a phone doesn't qualify. PM said developer that info thank you) this is not a thread you need to post in... Asking for ETA's (yes the how is this going questions) ALSO doesn't qualify as developer question's... Thank you for your cooperation in advance...:good:
[Verizon Samsung Galaxy S III] Surge1223:
Hi all, I realized today after having to find yet another method of decompressing the zImage (for another samsung variant) that Sammy has been upping their security and also making it a pain for us to examine the kernel (even if it is "open source") so while im busy with other things currently I figured id explain how to decompress the s3 kk zimage for other devs who would like to try to fix/patch the kernel.

First open the zImage with a hex editor, then find the lzo magic header and strip everything before it. Then there should be another lzo magic header later in the zimage, find it and strip everything everything after it. Save the modified zImage. Next using terminal in linux/cygwin cd to the dir with the zImage and enter

Also the above was just for reference, I will also attach the decompressed zImage here
[Verizon Samsung Galaxy S III] dexter35803:
Kernel

Ok so kernels are above my pay grade as well but i would like to try out a TW rom with 4.4.2, so i compiled this kernel as stock except one thing. i think i disabled the compression encryption on it please go over it and let me know. I have been up and down source trying to find a way around the security issues samsung decided to place upon there devices.

here are the following files my:

.config

compressed zimage

and the image file that looks to be uncompressed

All files are zipped in 7z so i could upload have fun let me know if this helps i can tell you what i changed in .config if needed but im pretty sure you guys can find it lol
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
Bump guess I am hopelessly in love with the idea of am unlocked 4.4 touchwiz rom
[Verizon Samsung Galaxy S III] Surge1223:
Is there still interest I this? I now have my s3 full time and since working on kexec lately I have a good understanding of how the kernel is decompressed and loaded, I think i have a pretty good idea where the issue is and it might very well be fixable.
[Verizon Samsung Galaxy S III] brickbeats:
I'm still interested, I've moved on to the Note 4 but my daughter could use some unlocked kit kat on her new/my old s3
[Verizon Samsung Galaxy S III] HamBone625:
I second that. I use my s3 still and have just been patiently waiting for 4.4tw
[Verizon Samsung Galaxy S III] fhem:
I'm still on the s3 and waiting. if ican help in any way let me know.
[Verizon Samsung Galaxy S III] n3wt:
oh hell yes!
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
+1

---------- Post added at 09:41 PM ---------- Previous post was at 09:41 PM ----------

+ 1
[Verizon Samsung Galaxy S III] kuronosan:
My wife would definitely appreciate this.
[Verizon Samsung Galaxy S III] open1your1eyes0:
If anyone can do it, Surge is definitely one of the guys. ;)
[Verizon Samsung Galaxy S III] mav3rick478:
Yes please.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Very interested.
[Verizon Samsung Galaxy S III] capt730:
Absolutely
[Verizon Samsung Galaxy S III] hokiealumnus:
+however many. Still on the stalwart S3 here too.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I think there would be a large following if this gets done. I have been using CM11, not bad, but I still miss lots of things I once had with Old & Slow's 4.3 stock rom, whether it was built in or a add-on. I think many of us want the phones to just work and not have to worry about extra glitches n gremlins you find with non-stock roms. Good luck, brave hearts...
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
And I tell u I would never get rid of my s3 and Verizon knows it and that's why they're locking it down like that. Good luck surge
[Verizon Samsung Galaxy S III] schwinn8:
I'm interested for our 2 phones... if you can get us to an unlock, I'm sure there will be many more options for us to try! Thanks for your efforts! Subbed!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I'm interested for the good of the S3 community. Good luck with this Surge.
[Verizon Samsung Galaxy S III] phillipmckinnish:
Thank you...Great News..:good::good::good::good::good::good:
[Verizon Samsung Galaxy S III] Macrodroid:
Definitely interested still. Cm and aosp are great, but still leave an empty feeling compared to tw.
[Verizon Samsung Galaxy S III] lepa71:
Yes,Yes,Yes. PLLEEEAAAASSSSEEEEE
[Verizon Samsung Galaxy S III] sjpritch25:
Honestly, i've been off tw for so long I don't miss it. But not saying I wouldn't flash it. He he he. Love that devs are still keeping this phone current.
[Verizon Samsung Galaxy S III] Surge1223:
K I'm on it
[Verizon Samsung Galaxy S III] 47th_Ronin:
Count me as one of the interested parties.
[Verizon Samsung Galaxy S III] cnlson:
Yes, please!

Stock, root, WiFi hotspot, xposed = perfect
[Verizon Samsung Galaxy S III] breaker911:
+1
[Verizon Samsung Galaxy S III] kidhudi:
+2

me and my bro
[Verizon Samsung Galaxy S III] YevOmega:
Have 3 S3s still serving as primary devices in the fam. Yes, please! Thanks Surge!
[Verizon Samsung Galaxy S III] shopman59:
Hope you can get it fixed I'm in

Thanks
[Verizon Samsung Galaxy S III] alquimista:
I've been watching this thread for ages, hoping, sending positive vibes, praying to whatever dogs will listen, and this is the post I have been yearning to see. In short, YES!!!

I'm not on the s3 anymore, and know nothing about kernel development. But I now have a spare s3 to test anything you can come up with.

Ta very much,

ALQI

mobile post, spelling doesn't count
[Verizon Samsung Galaxy S III] tedkord:
Count me in. I stopped checking this thread, figuring it was dead. Good to see someone still interested in getting this on our phones.

I just moved up to a Note 4, but I'm keeping the S3 as a backup, so I'd definitely load this on it.
[Verizon Samsung Galaxy S III] TheHobbyist:
I would be grateful for this as well!
[Verizon Samsung Galaxy S III] RGOLD:
Count me too. My S3 is alive and kicking will be nice to have 4.4
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
This would be a huge accomplishment we all commend you for your efforts surge
[Verizon Samsung Galaxy S III] dvaderx:
YES! I have 5 s3's would love to get it going.

Thanks!
[Verizon Samsung Galaxy S III] Surge1223:
OK so here's what's up... The ramdisk address change really doesn't matter for our purposes. But I'm trying two things

1. Build a kernel that can boot NE1, by figuring out exactly what requirements are missing and/or wrong

2. Boot a cm kernel then kexec into the Samsung kernel to boot the system

Status for both:

1. Still trying to find exactly what the problem is, so far logs have been giving me good info and I have been trying to patch/change things as I go.

2. I built the cm kernel with kexec ability (soft boot and hardboot built in) and re-enabled kernel modules to support the modules found in the NE1 kernel and to support kexec modules in general. This is based off the cm12 kernel for d2. I can successfully boot this kernel and kexec capability is working but I have yet to attempt to kexec into the NE1 kernel. I will upload sources for this to git if anyone wants to help try the second method (devs only though please)
[Verizon Samsung Galaxy S III] Surge1223:
I completely disabled selinux, so that's also not the reason behind NE1 not booting... Thought I'd post in case anyone was attempting to disable and check themselves.
[Verizon Samsung Galaxy S III] zachf714:
I have a feeling kexec won't work, based on cm using the iommu heap for display and camera where and verizon uses v4l2 as the heap for everything which is a very different heap which means the display driver is different
[Verizon Samsung Galaxy S III] Surge1223:
Well the issue right now is that NE1 doesn't allow the zimage to be decompressed because of an address change, that's just what I figured out recently though.

In theory, changing the location for decompression in head.S and packaging the zImage and ramdisk with offsett 0x01300000 (so base address @ 0x80200000 and ramdisk @ 0x81500000) should allow the NE1 boot.img to load.

Haven't tested yet.
[Verizon Samsung Galaxy S III] djskinnyb:
Count me as one more interested. Just prefer TW roms.
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
Hey [MENTION=4939386]Surge1223[/MENTION] considering the events of late does this mean the towel has been thrown on this venture so to speak

Either way thanks for being the last to help us out and we, I, for that matter really appreciate the thought and happy Thanksgiving to you brother.
[Verizon Samsung Galaxy S III] Scott:
Very cool. I will give it a shot in about 2 hours.

Also, I can upload you pretty much any stock RAM Disk, I have almost every tar except the 4.4.2 so let me know if you need anything and I know other people watching this thread can share files too if you want to see something.
[Verizon Samsung Galaxy S III] GMPOWER:
I had left the HLOS patch in when I modified the update script, so I am now running baseband i535OYODNE1, and had the same issue with booting.
[Verizon Samsung Galaxy S III] Scott:
So HLOS will more than likely have nothing to do with this then. It wa sjust a random thought I threw out.

One less step to try tonight

Good info!
[Verizon Samsung Galaxy S III] Scott:
Same results as with pure stock kernel.

I am going to try garwynn recomendation for giggles.

I'll post a binary comparison of the two ram disks as well
[Verizon Samsung Galaxy S III] Scott:
Wow they did change a lot!

Left file is NE3 RAM disk; Right file is ML1 RAM Disk
[Verizon Samsung Galaxy S III] zachf714:
alright. I know there is not a cert file in the 4.3 ramdisk, atleast not the ML1 ramdisk. Maybe we could try a zimage from a caf built kernel ? I could just extract my kernel from my phone and try booting it 3.4.92 or something, the problem would be that samsung is using major hacks with display and media repos as well as the kernel to use mheap instead of iommu which does not make much sense in a 3.4.x kernel
[Verizon Samsung Galaxy S III] Scott:
Whelp, I am at a stopping point for now.

If anyone has / can try anything then by all means feel free to contribute.
[Verizon Samsung Galaxy S III] BoilerDroid:
Possible Source

Not a Dev, but didn't know if this is:

1. helpful

2. possible source

http://samsung-updates.com/details/30088/Galaxy_S_3_Verizon/SCH-I535/VZW/I535VRUDNE1.html

Let me know if you want me to delete this post.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Nice find! :good:

EDIT: Here's a faster source: http://www.sammobile.com/firmwares/3/?download=31550
[Verizon Samsung Galaxy S III] esjames:
agree'd sammoble is way better:good:
[Verizon Samsung Galaxy S III] Scott:
Edit NVM. This is just Odin TAR.

I was thinking this was source.

Good to have for sure but... I we need kernel source.

If anyone downloaded this already and can drop box it to me please do because neither of these sites are remotely usable for me.

You can drop box a link in PM.
[Verizon Samsung Galaxy S III] eeraider:
So do you want the ODIN TAR in a dropbox? If so, yes I've downloaded the tar file and can put it is a dropbox for you.
[Verizon Samsung Galaxy S III] YevOmega:
Yeah, I think that's what he wants. Put it on your DB and PM him a link please. Thanks.
[Verizon Samsung Galaxy S III] Scott:
Yes please do. Then PM me a link and I can mirror it all over hell for everyone on very fast servers.

Plus I want to inspect some of the HLOS and the other img files because I couldnt do the full conversion (obvious).

Thanks!
[Verizon Samsung Galaxy S III] eeraider:
I am getting the following message when I try to PM you.
[Verizon Samsung Galaxy S III] open1your1eyes0:
[MENTION=426561]scrosler[/MENTION]

http://xdaforums.com/showthread.php?t=2795659
[Verizon Samsung Galaxy S III] Scott:
Strange! I will check my settings but open has us covered!

Thank you sir!
[Verizon Samsung Galaxy S III] LLStarks:
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=i535

Still nothing...

Samsung please!

Judging by their track record over the past few OTAs, I expect it to be there tomorrow.
[Verizon Samsung Galaxy S III] Scott:
Yes, but even then you have to understand that they changed the game so much that it may be more than just a recompile of the kernel.

Yes that fixed it on ML1 but we dont know whats going to happen on ND3. And honestly, I am a bit concerned.

I wish we could get more Sr Developer input on this. IM not a firmware guy at all. I just work with everything at the OS level.
[Verizon Samsung Galaxy S III] thenugdestrroyer:
Cnex the wizard
[Verizon Samsung Galaxy S III] Scott:
I dont know him but if you do then ask him if he has any ideas
[Verizon Samsung Galaxy S III] thenugdestrroyer:
I do believe it's been brought to his attention. Don't think he has seen it yet. He's crazy who knows what toggles or kernels or ROMs he's making right now lol
[Verizon Samsung Galaxy S III] kuronosan:
Is it not possible to use the aboot from an unlocked variant?
[Verizon Samsung Galaxy S III] prdog1:
Nope. They are device/varient specific. Dev device has embedded unlock code for only that device. If don't keep a copy of your individual aboot and accidently lock bootloader have to send to Samsung to have unlocked again. :cool:
[Verizon Samsung Galaxy S III] GMPOWER:
I was able to pull it from /proc/config.gz in recovery.
[Verizon Samsung Galaxy S III] zachf714:
I will compile it from Sprint source with this now and post it up

---------- Post added at 07:49 PM ---------- Previous post was at 07:45 PM ----------

Was this on stock 4.4.2 or a custom rom ? because that config says 3.4.77 but the kernel compiles as a 3.4.0 kernel

edit ---- That is a cyanogenmod kernel....... I need from stock rooted
[Verizon Samsung Galaxy S III] afaneh92:
No config.gz and searched and take a look to many file. Samsung hide it.
[Verizon Samsung Galaxy S III] Scott:
No, I said its a change in AOSP since 4.3. I posted a link a ways back on how you might get it.

They work hard as they can to keep us locked down.
[Verizon Samsung Galaxy S III] zachf714:
I just looked at the sprint source, samsung disabled it. But at this point it does not make a difference. Are you on 4.3 or 4.4.2 ?

---------- Post added at 10:24 PM ---------- Previous post was at 10:22 PM ----------

The way its enabled in aosp is not there either, just grepped the configs for the sprint source

edit - I am wondering what would happen if we took a cm ramdisk and just threw in the .sh files from the 4.4.2 ramdisk that came from the NE1 ota
[Verizon Samsung Galaxy S III] afaneh92:
Give the link plz, BTW today I was playing with safestrap, early was trying to get kitkat run on 4.3 kernel by replace ramdisk from sprint kernel that stuck on black screen.

What happend today is while trying to boot 4.3 on safestrap while Iam on kitkat. And Boom the blue light was shining. Black screen but usb working and I cant see what is going on.

Tomorrow will give it another try maybe this will help you.
[Verizon Samsung Galaxy S III] zachf714:
being on a locked bootloader is no help, you cant flash a different kernel from safestrap because your bootloader is locked IE why you black screened

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

@scrosler do you have the sprint ramdisk ? I want to take a look at it and compare to the vzw NE1 ramdisk
[Verizon Samsung Galaxy S III] afaneh92:
I cant flash kernel but I can delete ramdisk and load different ramdisk at boot, by modify safestrap boot scripts.

Sprint ramdisk is slightly different, our 3.4 kernel can boot stock kitkat sprint rom.
[Verizon Samsung Galaxy S III] zachf714:
You may have come across something else by loading other ramdisks, may have found a way to load aosp. I am going to try to get a look at the sprint ramdisk but I dont feel like downloading a full sprint rom or tar right now
[Verizon Samsung Galaxy S III] Scott:
I can download one tonight. I have a quick connection if I can find a fast link. If so I will post it up.
[Verizon Samsung Galaxy S III] afaneh92:
Iam focus on booting 4.3 if it work aosp will be easy.

Sorry cant upload ramdisk now from device. I will tomorrow.
[Verizon Samsung Galaxy S III] old&slow:
Here you go sprint ramdisk
[Verizon Samsung Galaxy S III] zachf714:
That is not true, the aosp ramdisk is way different and 4.3 wont boot it was compiled with display repos meant for a 3.0.x kernel

---------- Post added at 01:25 AM ---------- Previous post was at 01:10 AM ----------

Thanks, im looking through a git diff of the 2 ramdisks right now, verizon has a lot of nasty empty spaces

the diff http://pastebin.com/LtmGCr0p
[Verizon Samsung Galaxy S III] Scott:
Agreed but OandS got you what we were looking for. :good:

What next? VZW kernel on sprint ram disk? IM running out of ideas, lol
[Verizon Samsung Galaxy S III] old&slow:
I've got us cellular too if you want it but when trying to port them I realized they all apparently have the boot check.
[Verizon Samsung Galaxy S III] Scott:
Post it.

I compiled the source from that yesterday (or maybe the day before) and inseterd into VZW ram disk. No go. All black.

I hate you Samsung!
[Verizon Samsung Galaxy S III] zachf714:
Have you tried to remove the cert.pem ? maybe with that gone it will bypass
[Verizon Samsung Galaxy S III] Scott:
No, I was thinking that there is a check in init that looks for it so we would need to bypass it in the init binary.

So we tried with different init binaries and still no go.

However, not tried without it all together.

EDIT: Wait you are the one that made that suggestion: http://xdaforums.com/showpost.php?p=53679617&postcount=18
[Verizon Samsung Galaxy S III] old&slow:
uscc ramdisk
[Verizon Samsung Galaxy S III] zachf714:
It looks like mostly what is changed between the 3 is the SEPolicy

edit - the usc and vzw ramdisks are the exact same

edit - never mind, git was not working

edit - vzw vs usc http://pastebin.com/bwER8JRd
[Verizon Samsung Galaxy S III] zachf714:
someone try this, I cant remember if I have posted this before but it has the .pem file removed
[Verizon Samsung Galaxy S III] old&slow:
Actually just did it myself and was going to tell yall it didn't work.

Edit: Will try your's anyway.

Edit2: Same.
[Verizon Samsung Galaxy S III] CNexus:
Ok, many things to give input on here

First things first, on all other device we could not get it to boot without updating the firmware. Not to say it can't be done, but I didn't give it that much thought seeing how we can flash whatever we want through Odin since our bootloader is unlocked. Unfortunately you guys don't have that luxury so I'll try to help as much as I can.

Second, I'd disable selinux to start off. It's just annoying and caused issues with internal storage for us. You can diff against my files here: http://xdaforums.com/showthread.php?t=2747586

Third: how to possibly get this booting...

A) Swap zImage into one of the other 4.4 S3 ramdisks

B) check the parameters used to pack the boot.img on 4.3 versus 4.4. For us they changed the ramdisk address, so this could likely be the reason why I could not get it to boot. This would also explain why updating the firmware worked because the new bootloader "knows" it needs to load the kernel ramdisk from a different address versus earlier builds where it was looking in one place

My script here (https://www.dropbox.com/s/i00ebbs3pkgphxq/boot_info Linux only) will tell you all you could ever need to know about the kernel. First thing I would try is to grab your 4.1.2, 4.3, and 4.4 boot.imgs and repack the 4.4 boot.img with the different ramdisk addresses (I expect that there will be the 4.4 address and then one other)

To do the above you can use VTS, or my boot.img scripts here: http://xdaforums.com/showthread.php?t=2319018 (Linux only)

And that's all I've got at the moment

Oh and lastly, delete these files from /system/etc, they've caused stock roms not to boot in the past for me

recovery-resource.dat

selinux_restore (or something along those lines)

boot_fixup
[Verizon Samsung Galaxy S III] old&slow:
4.3 - RAMDISK ADDRESS: 0x81500000

4.4.2 - RAMDISK ADDRESS: 0x82200000
[Verizon Samsung Galaxy S III] CNexus:
Oh hey, would you look at that :D

Well hopefully that helps you guys. Crossing my fingers

Also [MENTION=426561]scrosler[/MENTION] I would use archi kitchen to build the rom if you are not already. I had major issues with dsixdas trying to get a 4.4 stock rom zip whipped up, booting, and fully working. I added support for all d2 variants back when I used it so it's just set up and go for you
[Verizon Samsung Galaxy S III] old&slow:
Lol, I'm gonna change it right quick and see what happens.
[Verizon Samsung Galaxy S III] zachf714:
when I looked at 4.3 the baseaddress and ramdiskaddress were the same

I just disabled selinux so I can change the address tho real quick too if you want
[Verizon Samsung Galaxy S III] Scott:
Yeah, I only use kitchens to zip final product and de / recompile boot.img. I build everything else by hand. But I will tell you I like the Archi kitchen because it does all the B/S work of finding the Sym links! :highfive: Saves Sooo much time!

Also, I haven't built ROM for testing but the odin is up so if you can get to it before me then by all means go for it. I have only done on device ota update to test that way I know I had a pure image... But now that Odin is up...

Otherwise I will spin it up tomorrow.

I have to work on "Android L" tonight for the Nexus 7 series. They are begging me for the Lolipop ROM.
[Verizon Samsung Galaxy S III] old&slow:
Just tried at 0x81500000 like 4.3 and still a no go.
[Verizon Samsung Galaxy S III] zachf714:
try with selinux disabled ?

send me your boot.img ?
[Verizon Samsung Galaxy S III] old&slow:
Did not disable selinux.