i am normally building my kernel standalone, but now i wanted to add inline-kernel-building support for it.
for this i have commited this:
https://github.com/DerTeufel/androi...mmit/70104d40af4355346590a84391882a70e53ccabc
and in my defconfig i am pointing to the initramfs to use:
CONFIG_INITRAMFS_SOURCE="source/ramdisks/t0lte-combo/"
it's the same as i use always, just added source/ in front.
link to ramdisks: https://github.com/DerTeufel/android_kernel_samsung_smdk4412/tree/dualboot/ramdisks
if i am flashing the resulting boot.img now, the device boots straight into dl mode, even without asking to confirm it with power up.
what am i mssing here?
Ramdisk is not correctly packed on your boot.img or is a problem with boot partition. If is jump straight to download mode the boot.img is corrupted or missing.
Trimis de pe al meu GT-N7100
goodoane said:
Ramdisk is not correctly packed on your boot.img or is a problem with boot partition. If is jump straight to download mode the boot.img is corrupted or missing.
Trimis de pe al meu GT-N7100
Click to expand...
Click to collapse
Is there something wrong with my commit to /build? I had seen, galaxy s1 is building in a similar way
Gesendet von meinem GT-N7105 mit Tapatalk 2
I have realised now, that on the s1 I just can take the zImage and rename it to boot.img to make everything work. This does not work for the note2. I guess this is the problem here.
My question is now, how can I modify the build system to create a proper boot.img, without adding the Ramdisk twice? By building the kernel standalone, I am only adding the modules to the Ramdisk. But for this I need to build the kernel and modules before building the Ramdisk. Anyone can tell me how to do this?
Gesendet von meinem SGH-I317 mit Tapatalk 2
http://technopyrate.blogspot.pt/2013/04/how-to-edit-android-bootimg-in-windows.html
For windows users:
bootimg-tools.zip:
http://www.mediafire.com/download/aswdwlj9sa91p51/bootimg-tools.zip
For linux users search adequate bootimg-tools.zip
Thx, but sadly this is not what I am needing. I want to modify build system to build the boot.img the way I need it, not afterwards, because I want building the kernel to be automated.
Gesendet von meinem GT-N7105 mit Tapatalk 2
carlitoschivas said:
Uzu0kz w a 6u1yV43 a waw s
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Exactly.
i got it fixed now, still very ugly, but working
https://github.com/DerTeufel/android_build/commit/c0abcbf9c713e539d5bf0aa2b6b565a9f138e794
Related
Hi.
I did my first kernel for note 2, everything is correct. I wanted to make my kernel compatible with Stweaks but didn't work out.
I did everything in the ramdisk but are missing some files. I guess that I have to modify some files .c or .h.
Thanks for the help.
Pafcholini said:
Hi.
I did my first kernel for note 2, everything is correct. I wanted to make my kernel compatible with Stweaks but didn't work out.
I did everything in the ramdisk but are missing some files. I guess that I have to modify some files .c or .h.
Thanks for the help.
Click to expand...
Click to collapse
You only need to modify the ramdisk. What did you change? And what error are you getting?
Gesendet von meinem GT-N7105 mit Tapatalk 2
DerTeufel1980 said:
You only need to modify the ramdisk. What did you change? And what error are you getting?
Gesendet von meinem GT-N7105 mit Tapatalk 2
Click to expand...
Click to collapse
Thank you. I checked my ramdisk and fixed the issues.
Enviado desde mi GT-N7100 usando Tapatalk 2
Hi,
I've enabled in the stock 4.3 kernel of N7100 fuse support.
The kernel compiles with fuse.ko module. When I try to load the kernel module I get:
insmod: init_module '/sdcard/fuse.ko' failed (Exec format error)
and in syslog:
<4>[21999.381035] c0 TIMA: lkmauth--wait_notify completed.
<6>[21999.381252] c0 mcdrvkmod mcd: 501|Err tima verify_module: Module Hash value does not match, addr:200000, len:ba780
<6>[21999.381386] c0 mcdrvkmod mcd: 501|Module Hash value not match
<6>[21999.381466] c0 mcdrvkmod mcd: 801|Trustlet tima_lkmauth::Returning 0
<3>[21999.382168] c0 TIMA: lkmauth--verification failed 64
<4>[21999.382243] c0 TIMA: MSG=lkm_modified; result (TIMA_RESULT=MSG=lkm_modified
<3>[21999.383274] c0 TIMA: lkmauth--unable to load kernel module; module len is 763776.
Apparently, the module is not signed. It was build from stock... I don't understand why it should be a problem...
Can I self sign it or something? Can I disable the signature checking in the stock kernel, flash it and then load the module?
I don't really need fuse... I want the rt73usb driver and fuse was just a test....an unsuccessful one..
I don't want to use custom roms with strange names....I like the stock one.
Any help appreciated
Are you using the new bootloader of sammy 4.3?
If not, disable TIMA in your kernel, then your modules pass the check. This is how I made wifi work on the leaked 4.3 roms
Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
DerTeufel1980 said:
Are you using the new bootloader of sammy 4.3?
If not, disable TIMA in your kernel, then your modules pass the check. This is how I made wifi work on the leaked 4.3 roms
Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
Click to expand...
Click to collapse
I have custom recovery so I guess that the bootloader is unlocked.
I want to understand the logic here, If I can't load a built from stock module, I shouldn't be able to load the freshly built kernel by the same logic, right?
Can you please link to disabling TIMA reading material? I get nothing from google.
Thank you
I am not talking about a unlocked bootloader. Samsung 4.3 comes with a new bootloader if you flash it by odin.
If you use a zip to install it, your bootloader is still the one from 4.1.2
As far as I know / think it is working, TIMA uses something within the bootloader to verify the module is valid.
If you have TIMA enabled, but old bootloader, the verification always fails.
You should grep for TIMA in your kernel source, and set the default to n in every Kconfig and just remove it from your defconfig (or set it to: not set) and also from your main kernel makefile
Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
DerTeufel1980 said:
I am not talking about a unlocked bootloader. Samsung 4.3 comes with a new bootloader if you flash it by odin.
If you use a zip to install it, your bootloader is still the one from 4.1.2
As far as I know / think it is working, TIMA uses something within the bootloader to verify the module is valid.
If you have TIMA enabled, but old bootloader, the verification always fails.
You should grep for TIMA in your kernel source, and set the default to n in every Kconfig and just remove it from your defconfig (or set it to: not set) and also from your main kernel makefile
Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
Click to expand...
Click to collapse
I've OTA updated to 4.3 . How do I check bootloader version?
I grep'ed the kernel source for TIMA before posting here. Nothing...
Maybe this one?
CONFIG_ARM_TRUSTZONE=y
vadimbrk said:
I've OTA updated to 4.3 . How do I check bootloader version?
I grep'ed the kernel source for TIMA before posting here. Nothing...
Click to expand...
Click to collapse
That's not possible. I've merged the source into my kernel, and there was TIMA in it. Which source did you download? What grep command did you use?
Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
DerTeufel1980 said:
That's not possible. I've merged the source into my kernel, and there was TIMA in it. Which source did you download? What grep command did you use?
Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
Click to expand...
Click to collapse
Downloaded from opensamsung n7100 update 2
grep -rn "TIMA" /path/to/kernel_source
That's not the 4.3 kernel source.
I am wondering the kernel even booted. It should give black screen because of wrong (old) mali driver.
Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
DerTeufel1980 said:
That's not the 4.3 kernel source.
I am wondering the kernel even booted. It should give black screen because of wrong (old) mali driver.
Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
Click to expand...
Click to collapse
Didn't try to boot it. What do you mean not the 4.3 kernel source? what is it?
Where do I get the stock 4.3 kernel source?
I think it is the n7100 swa update 1, which is 4.3 kernel source
Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
DerTeufel1980 said:
I think it is the n7100 swa update 1, which is 4.3 kernel source
Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
Click to expand...
Click to collapse
You're right. It was the wrong source.
Added "default no" in security/tima_uevent/Kconfig
and commeted TIMA in the make file.
I needed to copy dhd.ko to /lib/modules to make the wifi work again.
Thank you for the help
!!!!!! ONLY WORKS WITH CM11 !!!!!!
(and maybe other aosp roms)
!!!DOESN'T work with touchwiz rom!!!
UPDATE 24.6.2014!!!!
These are the most recent GPU drivers from qualcomm (24. June 2014).
These newer ones should provide better performance and some bug fixes.
Zip is modified to work on cm11 roms.
!!!!!!!!!!!!!!!!!Flash at your own risk!!!!!!!!!!!
I'm not responsible for any damage!!
If the phone doesn't boot after 3 minutes, restart recovery and flash latest cm11 zip again.
Link:
http://www13.zippyshare.com/v/32772090/file.html
I will update the OP every time new drivers are available.
Have fun
Status update:
I'm working on touchwiz 4.4.2 rom compatibility.. Stay tuned.
Will NEVER work on tw 4.3 roms.
Guess there'll be some beta tests.
Gesendet von meinem GT-I9505 mit Tapatalk
what are the improveness?
Yea, I'm also pretty curious! And could you tell where you got them from?
Me Gusta!
Which version would this be? I've got 53.0 atm.
Edit: ok, 66.
here it is the changelist
And does it make everything so much better?
Me Gusta!
Just download from the same link as change list, you need to make a account... I've flashed the zip, will report back with results.
Result: I can't notice any real improvement in general use or in bench.. Il test further.
David_cole said:
Just download from the same link as change list, you need to make a account... I've flashed the zip, will report back with results.
Result: I can't notice any real improvement in general use or in bench.. Il test further.
Click to expand...
Click to collapse
Which update pack did you flash? Hammerhead(N5) update?
_Sofos_ said:
Which update pack did you flash? Hammerhead(N5) update?
Click to expand...
Click to collapse
Tested both
David_cole said:
Just download from the same link as change list, you need to make a account... I've flashed the zip, will report back with results.
Result: I can't notice any real improvement in general use or in bench.. Il test further.
Click to expand...
Click to collapse
You should check if you flashed it correctly... Check Antutu benchmark (system info) should be driver v66 (old one is v54)
Edit: seems it's ok.
Gesendet von meinem GT-I9505 mit Tapatalk
iamnotkurtcobain said:
You should check if you flashed it correctly... Check Antutu benchmark (system info) should be driver v66 (old one is v54)
Edit: seems it's ok.
Gesendet von meinem GT-I9505 mit Tapatalk
Click to expand...
Click to collapse
Check screenshot mate, I found why it didn't work first time.... If you are on f2fs you have to manually mount system before flashing and it will work thanks mate.
Link added in OP. Have fun. Doesn't change benchmark scores BUT some games work better with it (less graphic glitches). UI seems better too.
Gesendet von meinem GT-I9505 mit Tapatalk
iamnotkurtcobain said:
You should check if you flashed it correctly... Check Antutu benchmark (system info) should be driver v66 (old one is v54)
Edit: seems it's ok.
Gesendet von meinem GT-I9505 mit Tapatalk
Click to expand...
Click to collapse
I installed the driver, it's OK for me ?
GT-I9505 - Tapatalk
krz_ayman said:
I installed the driver, it's OK for me ?
GT-I9505 - Tapatalk
Click to expand...
Click to collapse
It shows v53 so no.. you still have the old ones. It should say v66.
_Sofos_ said:
It shows v53 so no.. you still have the old ones. It should say v66.
Click to expand...
Click to collapse
Ok so I saw it too. how should I do to update? I have followed the instructions in post 1
GT-I9505 - Tapatalk
krz_ayman said:
Ok so I saw it too. how should I do to update? I have followed the instructions in post 1
GT-I9505 - Tapatalk
Click to expand...
Click to collapse
Manually mount system in recovery, then flash.
I manually reboot and flash, but still v53 ...: (help?
GT-I9505 - Tapatalk
krz_ayman said:
I installed the driver, it's OK for me ?
GT-I9505 - Tapatalk
Click to expand...
Click to collapse
It DOESN'T work with touchwiz roms. Just cm11 and other aosp roms. You have to try.
Gesendet von meinem GT-I9505 mit Tapatalk
More Info:
Removed Locked/Unlocked
Removed Warnings, replaced with Google Logo
Materialized Bootlader
Requirements:
Unlocked Bootloader
Recovery
Brain
How to install:
Reboot into recovery
Flash zip
Enjoy
Thanks:
@bitdomo for perfect tool
Download:
Indigo/Amber - Marshmallow LOGO - https://github.com/dzej1/dzej1.gith...d/Materialized_BL-Marshmallow_V2.zip?raw=true
Indigo/Amber - N LOGO - https://github.com/dzej1/dzej1.gith...id/bullhead/Materialized_BL-N_V2.zip?raw=true
Looks good. Thanks.
Sent from my Nexus 5X using Tapatalk
Looks good and working fine.
Great, got rid of the silly warning screen
Easy and done.
Great job aligning the warning screen Google logo. Can't even see when it switches to the regular boot logo.
Any chance you can post an undo, just in case?
mikel12323 said:
Easy and done.
Great job aligning the warning screen Google logo. Can't even see when it switches to the regular boot logo.
Any chance you can post an undo, just in case?
Click to expand...
Click to collapse
In original thread from developer of this tool is a stock.zip ?
http://forum.xda-developers.com/showthread.php?p=63634019
Gesendet von meinem Nexus 5X mit Tapatalk
Looks good. Finally I can pretend that my device is not unlocked
Looks great. I like it Removed warnings. Thank you my dude
This looks great. Thank you so much for fixing the unlocked Google logo!
Has this been tested with MMB29Q (February 2016 update) ?
mikel12323 said:
Has this been tested with MMB29Q (February 2016 update) ?
Click to expand...
Click to collapse
Bootloader is still same. So it works.
Gesendet von meinem Nexus 5X mit Tapatalk
mikel12323 said:
Has this been tested with MMB29Q (February 2016 update) ?
Click to expand...
Click to collapse
Works perfectly with MMB29P. Personally, I would hold off until more people have tested the new security update.
UPDATE: Is working fine for me with MMB29Q.
Looks great! Thank you!
Looks great and works perfect!
Hello,
First of all, thank you for this mod !
It's working fine on my 5X unlocked bootloader, pure nexus rom (18 feb 16) with ElementalX 1.06 kernel :good:
Cheers
this looks great!
just confirm then, to install this we flash the zip, and to uninstall (if bootloder changed or etc), we flash the stock.zip, right? No need to go into ADB fastboot w/ a PC?
2x4 said:
this looks great!
just confirm then, to install this we flash the zip, and to uninstall (if bootloder changed or etc), we flash the stock.zip, right? No need to go into ADB fastboot w/ a PC?
Click to expand...
Click to collapse
If you reflash or upgrade your bootloader it replace my themed imgdata with stock, which imho contain all bootloader images. So for this process in unnecessary to restore, but if you will YES you have to just flash that zip through recovery.
Gesendet von meinem Nexus 5X mit Tapatalk
domicq said:
If you reflash or upgrade your bootloader it replace my themed imgdata with stock, which imho contain all bootloader images. So for this process in unnecessary to restore, but if you will YES you have to just flash that zip through recovery.
Gesendet von meinem Nexus 5X mit Tapatalk
Click to expand...
Click to collapse
But the OTA will fail when trying to verify imgdata partition, in the case it tries to patch BL, right?
RusherDude said:
But the OTA will fail when trying to verify imgdata partition, in the case it tries to patch BL, right?
Click to expand...
Click to collapse
To be honest, I'm not sure if it'll fail, but I was writing about manual upgrading with fastboot, not OTA.
Gesendet von meinem Nexus 5X mit Tapatalk
Can we get this for the nexus 6p as well I'll gladly test
Sent from my Nexus 6P using Tapatalk
is this still compatible with the new MC vendor update, or will it need to be redone?
Hey guys so it looks like I got twrp into boot and recovery on my phone because when I try to start it up it just starts into recovery. I have access to the fastboot but don't have any oxygen roms on the phone to boot from. Any ideas how to fix this? Thanks!
Wrong section buddy!
pappschlumpf said:
Wrong section buddy!
Click to expand...
Click to collapse
Thanks, I realized this right after I posted. Already flagged for the mods, sorry bout that
Eilermoon said:
Thanks, I realized this right after I posted. Already flagged for the mods, sorry bout that
Click to expand...
Click to collapse
Flash a custom kernel, or Magisk. You're on stock kernel, right?
Gesendet von meinem ONEPLUS A6003 mit Tapatalk
pappschlumpf said:
Flash a custom kernel, or Magisk. You're on stock kernel, right?
Gesendet von meinem ONEPLUS A6003 mit Tapatalk
Click to expand...
Click to collapse
Yes but I can currently only access fastboot mode and adb devices doesn't show the phone connected so I can't adb push to it. If I try to fastboot boot the twrp recovery, that fails on me as well.