Post Reply

di11i kernel beta .01 (unsecure boot.img- root shell, adb remount) ext4 tweaks/init.d

OP di11igaf

2nd March 2012, 05:52 AM   |  #1  
di11igaf's Avatar
OP Recognized Developer
Flag East Coast
Thanks Meter: 666
 
1,760 posts
Join Date:Joined: Sep 2010
Donate to Me
More
This basically (for right now) the stock kernel image with some tweaks to init.
-unsecure boot.img-(perma- rooted adb shell)
-adb remount(mount /system r/w)
-init.d support added in for init scripts(survive after reboot)
-ext4 filesystem mount tweaks-/system/data/cache(faster I/O)
(Actually have a full ext2 version for,****s and giggles, but it boots into the encryption error screen, so cant release that. May have a fix though)
-mem and cache tweaks coming soon

still working on the actual kernel, will release that next, still have lots of work to do

boot.img MD5- fca41dba8f4699b67fd461a1632b65cf

MAKE BACKUP FIRST

You will not have issues if you wipe data, chances are youll be fine if you dont, but if anything starts acting up just wipe data, then install boot.img
This is the actual boot.img and for now has to be flashed with adb with these EXACT commands--
Code:
adb push boot.img /sdcard/
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0 seek=3968 bs=4096 count=2048
reboot


#Thanks Diamondback and friends for offsets



This is not the ideal way to flash this, but i can not get the blob file to staging partition to actually write the image. Im pretty sure its an issue with the signature of the blob file, so if someone wants to pack this into a blob id be glad test it and then update the OP.
My primes been using this boot.img for a few days, along with one other. Flash at your own risk.
NOT COMPATIBLE WITH CM-9
Attached Files
File Type: img boot.img - [Click for QR Code] (4.13 MB, 92 views)
Last edited by di11igaf; 3rd March 2012 at 02:39 AM.
The Following 7 Users Say Thank You to di11igaf For This Useful Post: [ View ]
2nd March 2012, 09:34 AM   |  #2  
MasterZen88's Avatar
Senior Member
Thanks Meter: 813
 
467 posts
Join Date:Joined: Feb 2012
Donate to Me
Quote:
Originally Posted by di11igaf

This basically (for right now) the stock kernel image with some tweaks to init.
-unsecure boot.img-(perma- rooted adb shell)
-adb remount(mount /system r/w)
-init.d support added in for init scripts(survive after reboot)
-ext4 filesystem mount tweaks-/system/data/cache(faster I/O)
(Actually have a full ext2 version for,****s and giggles, but it boots into the encryption error screen, so cant release that. May have a fix though)
-mem and cache tweaks coming soon

still working on the actual kernel, will release that next, still have lots of work to do

boot.img MD5- fca41dba8f4699b67fd461a1632b65cf

MAKE BACKUP FIRST

You will not have issues if you wipe data, chances are youll be fine if you dont, but if anything starts acting up just wipe data, then install boot.img
This is the actual boot.img and for now has to be flashed with adb with these EXACT commands--

Code:
adb push boot.img /sdcard/
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0 seek=3968 bs=4096 count=2048
reboot


#Thanks Diamondback and friends for offsets



This is not the ideal way to flash this, but i can not get the blob file to staging partition to actually write the image. Im pretty sure its an issue with the signature of the blob file, so if someone wants to pack this into a blob id be glad test it and then update the OP.
My primes been using this boot.img for a few days, along with one other. Flash at your own risk.

Great! I'm not the only one who as this problem. For what ever reason I too cannot get the blob to write.


I've tried running the blobpack -s to sign the blob but after trying to write it to the staging partition its a no go.....

EDIT: how are you working on the kernel if it has not been released yet?? JW, not trying to say your not but it would be cool if someone found a way to edit a compiled kernel.
2nd March 2012, 09:40 AM   |  #3  
Doktaphex's Avatar
Senior Member
Flag London
Thanks Meter: 426
 
1,430 posts
Join Date:Joined: Oct 2010
More
Quote:
Originally Posted by MasterZen88

Great! I'm not the only one who as this problem. For what ever reason I too cannot get the blob to write.


I've tried running the blobpack -s to sign the blob but after trying to write it to the staging partition its a no go.....

EDIT: how are you working on the kernel if it has not been released yet?? JW, not trying to say your not but it would be cool if someone found a way to edit a compiled kernel.

ICS kernel source is on the global download site.
2nd March 2012, 09:48 AM   |  #4  
MasterZen88's Avatar
Senior Member
Thanks Meter: 813
 
467 posts
Join Date:Joined: Feb 2012
Donate to Me
Quote:
Originally Posted by Doktaphex

ICS kernel source is on the global download site.

Correct but thats an older source code V9.4.2.7 right?
2nd March 2012, 10:24 AM   |  #5  
Doktaphex's Avatar
Senior Member
Flag London
Thanks Meter: 426
 
1,430 posts
Join Date:Joined: Oct 2010
More
Quote:
Originally Posted by MasterZen88

Correct but thats an older source code V9.4.2.7 right?

True, I don't know how much they have changed since then. Surely they need to be releasing new source pretty quickly to be in compliance with the license. I don't know enough about that side of things though.
2nd March 2012, 10:36 AM   |  #6  
Dexter_nlb's Avatar
Senior Member
Thanks Meter: 4,490
 
5,336 posts
Join Date:Joined: Feb 2009
Donate to Me
More
prime has a BLOBSIGN signature in the first 28 bytes of the blob files for prime.
you just need to copy those 28bytes from an existing blob file that works.

this is of course only working on a unlocked prime. then the BLOBSIGN signature is not checked, so anything can be pasted in front of it.

Rayman will update the packblob to include the signature later on.
2nd March 2012, 12:07 PM   |  #7  
jermaine151's Avatar
Senior Member
Flag Columbus, Ohio
Thanks Meter: 3,311
 
3,993 posts
Join Date:Joined: Jun 2010
Donate to Me
More
Quote:
Originally Posted by MasterZen88

Great! I'm not the only one who as this problem. For what ever reason I too cannot get the blob to write.


I've tried running the blobpack -s to sign the blob but after trying to write it to the staging partition its a no go.....

EDIT: how are you working on the kernel if it has not been released yet?? JW, not trying to say your not but it would be cool if someone found a way to edit a compiled kernel.

I'm confused. I thought after our PMs you had it flashing just fine?


Sent from my Galaxy Nexus using Tapatalk
2nd March 2012, 02:01 PM   |  #8  
MasterZen88's Avatar
Senior Member
Thanks Meter: 813
 
467 posts
Join Date:Joined: Feb 2012
Donate to Me
Quote:
Originally Posted by jermaine151

I'm confused. I thought after our PMs you had it flashing just fine?


Sent from my Galaxy Nexus using Tapatalk

Yes it flashed but later I realize non of my settings/changes took effect.

When I stated it work, I had took the stock kernel/initramfs from asus blob, extracted, made no changes at all, recompile like we talked about in our PM's then flashed it. It work but then after I made changes, recompiled. Non of my changes took effect.


Again Jermaine you have been a BIG help. and can only hope one day I can return the favor!!!
2nd March 2012, 02:07 PM   |  #9  
Diamondback's Avatar
Developer Committee / Senior Moderator / Recognized Developer
Thanks Meter: 6,394
 
4,418 posts
Join Date:Joined: Jan 2010
More
Quote:
Originally Posted by jermaine151

I'm confused. I thought after our PMs you had it flashing just fine?


Sent from my Galaxy Nexus using Tapatalk

Quote:
Originally Posted by MasterZen88

Yes it flashed but later I realize non of my settings/changes took effect.

When I stated it work, I had took the stock kernel/initramfs from asus blob, extracted, made no changes at all, recompile like we talked about in our PM's then flashed it. It work but then after I made changes, recompiled. Non of my changes took effect.


Again Jermaine you have been a BIG help. and can only hope one day I can return the favor!!!

Flashing blobs does NOT always work. No idea why yet. Directly dd'ing the boot.img to the right place works BETTER than flashing a blob in some cases...

Asus really screwed up with this Unlocker thing....
2nd March 2012, 02:28 PM   |  #10  
jermaine151's Avatar
Senior Member
Flag Columbus, Ohio
Thanks Meter: 3,311
 
3,993 posts
Join Date:Joined: Jun 2010
Donate to Me
More
Quote:
Originally Posted by MasterZen88

Yes it flashed but later I realize non of my settings/changes took effect.

When I stated it work, I had took the stock kernel/initramfs from asus blob, extracted, made no changes at all, recompile like we talked about in our PM's then flashed it. It work but then after I made changes, recompiled. Non of my changes took effect.


Again Jermaine you have been a BIG help. and can only hope one day I can return the favor!!!

No problem. I'm surprised it didn't work for you after you made changes.

Quote:
Originally Posted by Diamondback

Flashing blobs does NOT always work. No idea why yet. Directly dd'ing the boot.img to the right place works BETTER than flashing a blob in some cases...

Asus really screwed up with this Unlocker thing....

Flashing them to staging seems to work perfectly for me. That's how I made my insecure boot.blob and flashed it. It doesn't matter whether you're on unofficial CWM or Official since if you start your updater-script with unmounting staging, it doesn't hurt anything if staging wasn't mounted. Then you can either dd the blob to mmcblk0p4 or you can directly flash it via:
Code:
package_extract_file("boot.blob", "/dev/block/mmcblk0p4");
I have not found an occasion where this didn't work. You need to make sure that you don't add any --cmdline parameters when you mkbootimg or you will get a bootloop. Staging is definitely the safest way to flash to any partitions on the Prime.

Quote:
Originally Posted by MasterZen88

Correct but thats an older source code V9.4.2.7 right?

The kernel versions seem to be the same with the latest .15 build as the previous one. I wonder if they just recompiled the same source and that's why the host name changed to Mercury.

EDIT: I'm going to pack this kernel into a flashable blob and attach it here.
Last edited by jermaine151; 2nd March 2012 at 02:38 PM.

The Following User Says Thank You to jermaine151 For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes