Bootloader Partially Locked?

---

I noticed that the community has not successfully made a Kernel thats works without doing a boot-loop. Could it be possible that there is E-Fusish type security measure, like the Droid 2 and X, that prevents users from loading custom kernels that Verizon implemented? Thats the only explanation I can think of why we are having issues with our Galaxy versus other carrier's versions.

Sent from my SCH-I500 using XDA App

Samsung gave us a BUNK defconfig

the bootloader's not locked, kernel isn't signed

I've got a working kernel that boots, but the accelerometer is screwed up

Originally Posted by jt1134

Samsung gave us a BUNK defconfig

the bootloader's not locked, kernel isn't signed

I've got a working kernel that boots, but the accelerometer is screwed up

Sorry for my next noobish question but has anybody sent an email to Samsung about getting a fixed source code or is it pointless until 2.2 drops?



Sent from my SCH-I500 using XDA App

pointless? I guess that depends on who you ask. But yes, Samsung has received much electronic mail from smartphone enthusiasts over the past few weeks.

Originally Posted by jt1134

pointless? I guess that depends on who you ask. But yes, Samsung has received much electronic mail from smartphone enthusiasts over the past few weeks.

I will talk to my Samsung rep to see if there is anybody I could escalate this to in their North America branch to get this fixed but highly unlikely thou.

Sent from my SCH-I500 using XDA App

@Jt
I will be back on irc tommorow, but I have the accelerometer fixed on my kernel just no wifi, bluetooth or sound still. Have you found a fix for any of these, or are you still using my config?

AFAICT everything works now. I started with your config as a base

Originally Posted by jt1134

AFAICT everything works now. I started with your config as a base

This is good news, no?

Very nice gang.. I will block off some time for sure to stop in and see what's shakin' this evening..

Dirrk.. what initramfs are you using? I was able to compile with yamaha_b5 and your ramdisk, then I got the no sound/orientation/etc.. However it seems when JT compiles, he uses koush's ramdisk, and gets sound (orientation still off).

If I compile with b5_yamah + koush ramdisk (from his git), Odin fails to flash every time. If I switch back to your ramdisk, odin flashes, kernel boots, etc..

Sounds like you guys are making some good progress. Thanks for your hard work. Can't wait to be able to overclock this sucker.