It was hard enough to get him to agree to me offering to change boot logo for people on his rom. He was eventually kind enough to agree to me doing it. I have a lot on for the next 4 weeks. I will see if I can sort it out once everything has settled down for me.Have you reached out to Malaysk to see what it could be?
But your picture remains, can change 1st boot image from yours but on second boot yours comes back!?In kernel.img chinese programmers have set protection. I change the picture once - the second time does not work!
Understood. A bit of a shame though :crying:In kernel.img chinese programmers have set protection. I change the picture once - the second time does not work!
Could you do the same for this BMW Logo (Boot & Recovery) for 800x480 RK3188 April 23, 2016 ("update_4_4_4_FUSE_800X480_RK3188_15_MAL_23_04_2016.rar"), please??
Unfortunately due to the way the kernel is compiled now it is impossible to change the logo more than once so because Malaysk has already changed the logo any change after that won't work.Could you do the same for this BMW Logo (Boot & Recovery) for 800x480 RK3188 April 23, 2016 ("update_4_4_4_FUSE_800X480_RK3188_15_MAL_23_04_2016.rar"), please??
![]()
Thanks for your quick answer. Would be possible with any BMW logo?Unfortunately due to the way the kernel is compiled now it is impossible to change the logo more than once so because Malaysk has already changed the logo any change after that won't work.
It wouldn't matter what the logo was it is impossible to change now. It only works with older roms.Thanks for your quick answer. Would be possible with any BMW logo?
It can't be done anymore, read the previous posts:good:Can you add this MG please to update_4_4_4_FUSE_800X480_RK3188_15_MAL?
Many Thanks.
Unfortunately the last one to work was February or March.Great job with these!
Which was the last RK3188 1024x600 Malaysk version that allowed changing the 1st boot logo? update_4_4_4_FUSE_1024X600_RK3188_17_MAL_23_04_2016?
Would it be possible to insert this Jeep diagram png as 1st boot logo on the newest ROM release that still allowed these changes?
I saw from the first post there was a ford and vw 23/04, did those not work in the end, reverted to Malaysk logo on 2nd boot?Unfortunately the last one to work was February or March.
I read back in the thread and saw the latest Malaysk 23/04 and booroondook 30/03 ROMs can't be modded because of some kernel protection.ford_1024X600_RK3188_17_MAL_23_04_2016.rar (with Ford boot animation (bootanimation_dancing_droids.zip))
I'm not sure on both counts. The best thing to do would be to download some from various build dates and test them to see if the boot logo actually stays with the modded one. It's the best I can suggest really. Then when you find the latest one that still works let me know and I'll apply the logo you want.I saw from the first post there was a ford and vw 23/04, did those not work in the end, reverted to Malaysk logo on 2nd boot?
I read back in the thread and saw the latest Malaysk 23/04 and booroondook 30/03 ROMs can't be modded because of some kernel protection.
Can the second to latest booroondook 12/03 be modded?
DIY_KLD_FUSE_AllCPU_KK444_AllRes_160226_root_mod_boo_2016-03-12_v1.0.0.zip
https://mega.nz/#!WUBG3LhT!n37W2w0kD_onrZGi_BGEBYHCDEYMd31JZS8JIm1_Qo0
http://4pda.ru/forum/index.php?showtopic=704299&st=0#entry43482386
Which was the latest Malaysk that is still modable? Was it 17/03?
update_4_4_4_FUSE_1024X600_RK3188_16_MAL_17_03_2016.zip
Thanks. It seems the booroondook 12/03 can be modded. According to his release notes the 12/03 is based on KLD-20160226. So his Mar 3rd release has a Feb 26th kernel which should be older than the new kernel protection causing the problems.I'm not sure on both counts. The best thing to do would be to download some from various build dates and test them to see if the boot logo actually stays with the modded one. It's the best I can suggest really. Then when you find the latest one that still works let me know and I'll apply the logo you want.
Will doThanks. It seems the booroondook 12/03 can be modded. According to his release notes the 12/03 is based on KLD-20160226. So his Mar 3rd release has a Feb 26th kernel which should be older than the new kernel protection causing the problems.
You previously modded this boo 12/03 ROM with a bmw logo which seemed to get a good report:
http://forum.xda-developers.com/showpost.php?p=65943724&postcount=102
Can you please mod the boo 12/03 ROM with this jeep diag 1024 image in the attached zip? I can flash and report back.
https://mega.nz/#!WUBG3LhT!n37W2w0kD...31JZS8JIm1_Qo0 (DIY_KLD_FUSE_AllCPU_KK444_AllRes_160226_root_mod_b oo_2016-03-12_v1.0.0.zip)
Here's the link jeep_boo_2016-03-12_v1.0.0.rarThanks. It seems the booroondook 12/03 can be modded. According to his release notes the 12/03 is based on KLD-20160226. So his Mar 3rd release has a Feb 26th kernel which should be older than the new kernel protection causing the problems.
You previously modded this boo 12/03 ROM with a bmw logo which seemed to get a good report:
http://forum.xda-developers.com/showpost.php?p=65943724&postcount=102
Can you please mod the boo 12/03 ROM with this jeep diag 1024 image in the attached zip? I can flash and report back.
https://mega.nz/#!WUBG3LhT!n37W2w0kD...31JZS8JIm1_Qo0 (DIY_KLD_FUSE_AllCPU_KK444_AllRes_160226_root_mod_b oo_2016-03-12_v1.0.0.zip)
Thanks! That flashed fine and retains the custom logo after 2nd reboot. It seems the custom 1024x600 picture doesn't fill the full screen though, there is a black border around it, is that normal?Here's the link jeep_boo_2016-03-12_v1.0.0.rar