• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Wanted - KK1 (or similar 2.3.6) stock kernel

Slug

Check six!
Anyone got the tarball of this bad boy laying around? I cleared my own collection out a week or two ago, unfortunately. :(

Intratech hasn't managed to move his downloads from Multiupload yet and another member needs the stock kernel package as a 'safety net' prior to rooting. Any help will be greatly appreciated.
 
If they download some kk1 firmware from check fuss they should be able to extract the kernel from the firmware zip.
 
Yeah, but that still requires CWM or Mobile Odin to flash the zImage. I was looking for the .tar or .tar.md5 that could be flashed from the PC with Odin, just in case a firmware flash didn't complete the reversion. Probably over-cautious, but when it's someone else's handset....
 
I've extracted a modem from a samfirmware package before and flashed it with Odin. I thought it would be the same for the kernel.
 
It looks like to get a stock kernel tar from samfirmware you need to open up the firmware and then delete everything except the zimage. I would do it and post it up but I'm away from a PC until I finish work.
 
Just popping in here.....I'm looking for the KK1 kernel, but I would like to find it for my current 2.3.5 firmware.

Slug, if you made this thread for me.....I appreciate it.......if it wasn't......I still appreciate it as to it gave me a place to ask!!!!


Samsung Galaxy SII i9100 T-Mobile Germany BOKK1 2.3.5
 
Just download your firmware from sammobile.com/firmware
Once downloaded use 7zip to open the file and extract the zImage. Once the zImage has been extracted right click on it, then select 7zip> add to archive...
Where it says archive format select tar from the drop down menu then click OK and you are done.
 
When I use 7Zip to extract to get the zImage is it normal to see this in the dialogue box:

"0 There is no correct record at the end of archive"

This have me a bit worried at to whether it worked correctly. Everything went fine as I extracted the .rar file.......I got the message above immediately as I extracted the MD5 file to get to the zImage.

A little help please!!!

Thanks in advance
lotsip81
 
I appreciate all of your guys responses and help, you have my "thanks". This really is a great forum, glad I joined!!
 
Just download your firmware from sammobile.com/firmware
Once downloaded use 7zip to open the file and extract the zImage. Once the zImage has been extracted right click on it, then select 7zip> add to archive...
Where it says archive format select tar from the drop down menu then click OK and you are done.

I did as described here, and thought that I would try to flash back to a stock kernel. I mainly just wanted to do it for a learning experience.

But I ran into problems. I was trying to flash the stock kernel through Odin. So I cleared the cache partition and the Dalvik cache as well. Powered down, and rebooted into download mode. Connected to the computer and Odin recognized the device immediately, so I selected the zImage that was in .tar format and clicked start.

It sat in "downloading do not turn off target" for about 30 minutes before I disconnected it. Luckily I had made a nanoid backup so I was able to restore the phone to how it was 2 days ago.

My question is "What did I do wrong?"

Thanks for the help
lotsip81

edit: FYI my phone was at about 85% battery if it matters.
 
One more note, and possibly important. I had apps frozen with Titanium Pro, mostly the bloatware. Don't know if this is important info, but I just thought I'd put out all the details. :confused:
 
Sounds like it was simply a faulty file.

If you're rooted with CF-Root and have the CWM app, you can use its "Flash kernel" option to revert. Copy the stock zImage to your internal SD volume, then open CWM, selection Flash kernel and select the zImage. I can't remember if the handset reboots automatically afterwards; if it doesn't then restart manually.

nb you'll still see CWM installed but it won't work now that the CWM Recovery has been removed along with the custom kernel. Superuser and su will also still be installed so technically you'll still have root access. To properly unroot you really need to remove them too.
 
Sounds like it was simply a faulty file.

If you're rooted with CF-Root and have the CWM app, you can use its "Flash kernel" option to revert. Copy the stock zImage to your internal SD volume, then open CWM, selection Flash kernel and select the zImage. I can't remember if the handset reboots automatically afterwards; if it doesn't then restart manually.

I thought that the process above was done just to remove the "!" at booting screen.....:confused:

What I was trying to do was flash stock kernel to try to unroot. I just wanted to see if it'd work. Or do i have to flash full firmware to unroot?

Am I right though about flashing a kernel with Odin? Extract till I get zImage the change image to .tar and flash that?
 
Well the first time I tried it with the download from SamMobile, I tried it again with the firmware I downloaded with CheckFUS. Both of them acted the same way.

Here's how it went:

Downloaded firmware BOKK1 2.3.5 carrier specific, extracted the .rar so I had access to the MD5 file. Extracted the MD5 file to get to the zImage. Took the zImage, added it to archive as a .tar format. Went into CWM, cleared the partition cache then the Dalvik cache. Powered off and went itno download mode. I then opened Odin and selected the zImage in .tar format to flash to my phone.

But neither one of them worked. I can hardly believe that both of the downloads are bad. So I must assume that either I did something wrong with the file, or this is an improper way to do this.

Slug, If I do it the way you are suggesting, do I remove the stock zImage from the internal sd after reboot?

Thanks for the help,
lotsip81
 
I thought that the process above was done just to remove the "!" at booting screen.....:confused:

That's a side-effect of flashing a stock Samsung kernel.

do i have to flash full firmware to unroot?

It's the easiest way, due to the above-mentioned files being left even when the kernel is replaced. The kernel itself only facilitates the root by allowing the su binary etc to be installed to /system, and providing the enhanced recovery.

If I do it the way you are suggesting, do I remove the stock zImage from the internal sd after reboot?

There's no need to keep it, so yes.
 
It might be worth, instead of extracting the zimage from the tar and then turning it back into a tar, deleting everything from the firmware tar except the zimage and try flashing that.
 
It might be worth, instead of extracting the zimage from the tar and then turning it back into a tar, deleting everything from the firmware tar except the zimage and try flashing that.

I tried leaving the zImage as it was when it was first extracted, but Odin didn't even see it there at all.

Two more simple (for you guys) questions. If I do flash the MD5 firmware file, do I lose all my apps? I do have them backed up with Titanium, just wondering what to expect.

And what did I do wrong in the way I described earlier that it didn't work?
 
BTW,

Thanks for the quick response guys. I sure hope they pay you well for putting in all this hard work around here!!
 
What I meant was don't extract the zimage from the firmware tar/md5. Open up the firmware and delete all the files inside except the zimage. That will turn the firmware tar into a flashable kernel.

You shouldn't lose your apps when you flash the md5.
 
Back
Top Bottom