Jump to content

Kernel Unpacking


Guest utternoob

Recommended Posts

Guest utternoob

Yeah, but I think the problem was punctuation in the UI_print section, as there were spaces between speechmarks and what I wanted to say

Edit: The script was checking for things in the build.prop that didn't exist. Thanks guys :)

Still getting error, a bit stuck now :(

Edited by utternoob
Link to comment
Share on other sites

You don't need to. Yesterday we saw that the bootclasspath is OK. So no need to change anything else.

Just use existing boot.img of your source rom.

Link to comment
Share on other sites

Guest utternoob

Tried that, all it does is sit on android man. Heard of roms taking ages to boot, but mine seemed ridiculous. Could it be that the rom I'm porting is odexed? Think it maybe as it was based on stock rom

Link to comment
Share on other sites

Makes no difference if odexed/deodexed. No logcat at all? Run it via adb on boot.

It will tell you where it loops.

Edited by C3C0
Link to comment
Share on other sites

Guest razzmataz1478

Another problem. All the graphics will be mashed up because I believe the Ace is 480x360 resolution. So framework will need resizing

Link to comment
Share on other sites

Guest Mtman1
Another problem. All the graphics will be mashed up because I believe the Ace is 480x360 resolution. So framework will need resizing
Yep it is. Frameworks definitely needs resizing
Link to comment
Share on other sites

Guest utternoob

Mostly works, just need to scale framework and system ui for it to work fully, as doesn't get past skatie screen, despite sitting for around 5 minutes

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.