Compile a CM 10.1 kernel, baseband and kernel unknown.
I'm a beginner. Learning to using CM source compiler kernel, and ROM.
The help of many good-hearted people, such as: AndreiLux and simone201
I can use CM10.1 source to compiled kernel for n7108 now.
However, while normal boot the system. The phone has no signal.
In the settings. Baseband and kernel is unknown.
Who can help me. Or tell me how to solve this problem.
Thank you.
In the annex, I have attached the the adb log when up and running.
wctliu said:
Compile a CM 10.1 kernel, baseband and kernel unknown.
I'm a beginner. Learning to using CM source compiler kernel, and ROM.
The help of many good-hearted people, such as: AndreiLux and simone201
I can use CM10.1 source to compiled kernel for n7108 now.
However, while normal boot the system. The phone has no signal.
In the settings. Baseband and kernel is unknown.
Who can help me. Or tell me how to solve this problem.
Thank you.
In the annex, I have attached the the adb log when up and running.
Click to expand...
Click to collapse
I haven't looked at the logs but my guess is you used n7100 proprietaries instead of the ones from n7108.
Extract the files (filenames here ) from a stock n7108 firmware (you've probably overwritten them on your device already) and recompile.
Make sure you have a modem for n7108 loaded (flash stock firmware with odin to be sure).
victorator said:
I haven't looked at the logs but my guess is you used n7100 proprietaries instead of the ones from n7108.
Extract the files (filenames here ) from a stock n7108 firmware (you've probably overwritten them on your device already) and recompile.
Make sure you have a modem for n7108 loaded (flash stock firmware with odin to be sure).
Click to expand...
Click to collapse
Thank you very much for your reply.
You are a good-hearted people.
I am afraid that is not the problem.
First of all, I use a script to crawl 7108 proprietaries, from my 7108.
Second, because the comparison of 7100 and 7108 the official firmware, only one file difference.
That is, "libsec-ril.so", this file I have also replaced the 7108 version.
Related
I recently rooted my galaxy sl using amit bagaria's universal cf root. After rebooting, the wifi wasn't switching on (it gave me an error message). So I googled it an found a solution. I flashed the bam kernel v14 (google it) and the wifi is working properly. Now, apparently the bam kernel v14 is not compatible with cm and i cannot flash any cm rom. Is that how it is supposed to be? How can i fix this? Thanks for all the help
rohit_6 said:
I recently rooted my galaxy sl using amit bagaria's universal cf root. After rebooting, the wifi wasn't switching on (it gave me an error message). So I googled it an found a solution. I flashed the bam kernel v14 (google it) and the wifi is working properly. Now, apparently the bam kernel v14 is not compatible with cm and i cannot flash any cm rom. Is that how it is supposed to be? How can i fix this? Thanks for all the help
Click to expand...
Click to collapse
The wifi problem is because you were on a value pack for 2.3.6, and if you root the device you can't use wifi unles you use bam kernel.
About CM, every ROM includes it's own kernel, so if you flash Dhiru's CM10 for example, this will come with it's own kernel and will install it automatically when you install the ROM. There are kernels for each Rom, so beware when you install a kernel on your Rom, first check if it's compatible. I think that's what you read about bam kernel, that is only compatible with Gingerbread.
PS: Please be more specific on the title next time
salaesp said:
The wifi problem is because you were on a value pack for 2.3.6, and if you root the device you can't use wifi unles you use bam kernel.
About CM, every ROM includes it's own kernel, so if you flash Dhiru's CM10 for example, this will come with it's own kernel and will install it automatically when you install the ROM. There are kernels for each Rom, so beware when you install a kernel on your Rom, first check if it's compatible. I think that's what you read about bam kernel, that is only compatible with Gingerbread.
PS: Please be more specific on the title next time
Click to expand...
Click to collapse
Alright.....now for example I want to flash Dhiru's CM10, how do I go about doing it? The normal way....with Odin? Just flash it PDA??
rohit_6 said:
Alright.....now for example I want to flash Dhiru's CM10, how do I go about doing it? The normal way....with Odin? Just flash it PDA??
Click to expand...
Click to collapse
No, you have to flash it using CWM. Please follow the installation instructions given in CM10 from dhiru:
http://forum.xda-developers.com/showthread.php?t=1868074
You are on stock rom, so follow the stock rom steps. You can skip the root step if you already rooted it.
As an advice, I suggest you make a /efs folder backup. This folder from your phone keeps a lot of information about it. I had some problems with 3g and stuff, and recovering it helped me. Before doing anything please read some threads about flashing this device.
Good luck!
I'm wondering if I have to flash a specific Kernel before flashing custom roms ( CM specifically ). My device is P3110 running stock 4.1.2 . Any help will be much appreciated, thanks guys.
Edit: Does flashing the CM Rom zip file flash the newest CM kernel or should I flash it manually?
kareemgonna said:
I'm wondering if I have to flash a specific Kernel before flashing custom roms ( CM specifically ). My device is P3110 running stock 4.1.2 . Any help will be much appreciated, thanks guys.
Edit: Does flashing the CM Rom zip file flash the newest CM kernel or should I flash it manually?
Click to expand...
Click to collapse
Next blackhawx 1.8.3 developed ketut.kumayaja
kareemgonna said:
I'm wondering if I have to flash a specific Kernel before flashing custom roms ( CM specifically ). My device is P3110 running stock 4.1.2 . Any help will be much appreciated, thanks guys.
Edit: Does flashing the CM Rom zip file flash the newest CM kernel or should I flash it manually?
Click to expand...
Click to collapse
You never want to flash a kernel before flashing a rom because the rom will over write the kernel when it installs its own. If you want a custom kernel flash it right after flashing the rom.
All roms come with their own kernel.
Sent from your phone. You should be careful where you leave that thing.
Thanks
Skipjacks said:
You never want to flash a kernel before flashing a rom because the rom will over write the kernel when it installs its own. If you want a custom kernel flash it right after flashing the rom.
All roms come with their own kernel.
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
That's exactly what I needed to know, I have another android device ( Xperia mini pro ) and every time I need to install a custom rom, I have to flash its kernel first. Here it seems like flashing the rom via recovery also flashes the kernel. Thanks for the help appreciated.
kareemgonna said:
I'm wondering if I have to flash a specific Kernel before flashing custom roms ( CM specifically ). My device is P3110 running stock 4.1.2 . Any help will be much appreciated, thanks guys.
Edit: Does flashing the CM Rom zip file flash the newest CM kernel or should I flash it manually?
Click to expand...
Click to collapse
The CM zip file has everything it needs. You just need to have a recovery ROM to be able to install CM from recovery. Additionally, you might want to reset various things from recovery before installing CM. Notice that if you reset the internal sdcard you will lose all your data (which might or might not be what you want).
Hello everyone
I've got p5110 with new 4.2.2 rom (xeo). I have installed also root and cwm. That wasn't problem. But the main problem was looking for kernel cos i want to overclock cpu on gpu on stock rom So i found this one http://forum.xda-developers.com/showthread.php?t=2302663 but there are few questions...
Which files I install? I know that zip file in cwm but there is the second one called proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) . I dont understand which file i should install first... :/ I want single boot on stock rom.
Thanks for all !
Qosmio46 said:
Which files I install? I know that zip file in cwm but there is the second one called proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) . I dont understand which file i should install first... :/ I want single boot on stock rom.
Click to expand...
Click to collapse
Just read the OP carefully, it has the instructions, and they are very simple:
1. Boot into the recovery.
2. Flash the kernel (blackhawk-next-kernel-x.y.z-p51xx.zip) -- replace "x.y.z" with the version you need.
3. Immediately after that (do NOT reboot!) flash the proprietary Samsung binaries (proprietary-vendor-samsung.zip).
4. Reboot.
You don't need to worry about all the dual-boot stuff.
I think I understand now there is a main file with kernel and with this zip comes some binary files in catalogue (that's what i saw) i need to install this in cwm after this install this second zip with no re booting. In this second zip are files which are managed these from first zip with kernel? Thats way i need to install these both one by one. Seems legit thank you very much i hope that will work
Qosmio46 said:
i hope that will work
Click to expand...
Click to collapse
It will, don't worry. I have been using this kernel for quite a while on my P3113, went through many version upgrades. The best kernel for this tablet, hands down!
Confirmed! Best Kernel
Today morning, i have installed this kernel as you said first kernel then these files It is great and working perfectly Thanks for help !
Hey peeps, I'm running slapnuts v1.4 rom on a d2vzw gs3 vrucml1 baseband. The rom is supposed to be running with Lean Kernel v4.0 but for some reason I am stuck with the stock kernel. I have also tried flashing Lean Kernel by itself but with no success, actually whenever I flash it I just end up losing wifi and having to flash the ml1 modules back. I could use some help here, thanks!
Another thing that I could use some clarification on, Safestrap directs users to install the kernel modules after flashing a rom (otherwise we would be without working wifi). The problem I'm seeing here though is whenever a kernel is flashed, wifi is no longer working, in other words, the module is gone and has to be re-flashed which I am assuming (only because I've been unable to get a kernel up and running) would remove the kernel all over again and visa versa.
Am I just doing something wrong or does it seem that something is broken here?
Yeorgaki said:
Hey peeps, I'm running slapnuts v1.4 rom on a d2vzw gs3 vrucml1 baseband. The rom is supposed to be running with Lean Kernel v4.0 but for some reason I am stuck with the stock kernel. I have also tried flashing Lean Kernel by itself but with no success, actually whenever I flash it I just end up losing wifi and having to flash the ml1 modules back. I could use some help here, thanks!
Another thing that I could use some clarification on, Safestrap directs users to install the kernel modules after flashing a rom (otherwise we would be without working wifi). The problem I'm seeing here though is whenever a kernel is flashed, wifi is no longer working, in other words, the module is gone and has to be re-flashed which I am assuming (only because I've been unable to get a kernel up and running) would remove the kernel all over again and visa versa.
Am I just doing something wrong or does it seem that something is broken here?
Click to expand...
Click to collapse
You cannot flash a custom kernel on TouchWiz 4.3+. You must use the stock kernel. That's the way that Safestrap works on the S3 given the limitations created by Samsung.
Sent from my SCH-I535 using Tapatalk
For those of you who don't know, MultiROM is a mod that lets you boot an arbitrary number of ROMs at once. It contains three parts: a modded version of the TWRP recovery, the MultiROM bootloader, and a kernel installed on the primary ROM that has support for kexec-hardboot. As far as I know, the only kernel for Moto X with kexec-hardboot support is tdhite's TDHK Kernel. If you have a ROM that is based on AOSP 4.4.4-5.0.x, please install this kernel then try using this build of MultiROM. The recovery image is tested and seems to be working; however, I do not have an AOSP ROM right now, so you are flashing at your own risk. Don't hold me responsible for bricking, breaking, or face-eating spaghetti monsters that arise from using this mod.
Installing
Connect your device to your computer via USB and run
Code:
adb reboot bootloader
in a terminal/cmd. Wait for the device to reboot to the bootloader, then run (as root/administrator)
Code:
fastboot flash recovery recovery.img
in the folder that you downloaded recovery.img to.
To install the MultiROM bootloader (after installing a kexec-hardboot kernel to your primary ROM!) upload multirom.zip to your device via adb push, mounting the device onto your computer, downloading the file directly, etc. then reboot to recovery and flash.
You can uninstall by flashing multirom_uninstaller.zip in TWRP (you will still have the modded recovery, just flash your choice of recovery to uninstall it).
Submitting bugs
If you experience bugs, make a post reply with this format:
Primary ROM: (provide name & link if possible)
Primary Kernel: (provide name & link if possible)
Secondary ROMs: (list all of them, provide links if possible)
Pastebin link to /sdcard/multirom/error.txt : (It might not exist, check anyway)
Pastebin link to /proc/last_kmsg : (this file lasts 1 reboot, access it from recovery immediately after the bug)
Other notes:
Download
https://www.dropbox.com/sh/rixkydvznnwjtd7/AAA5C6NLyW_RTNqg7_CWjQcva?dl=0
Credits
MultiROM team
TWRP team
kladd for his GitHub source (I made modifications to support MultiROM)
Makalak and Elimin8er on the #multirom irc channel for helping me build MultiROM
Linus Torvalds
Many other people that did work behind the scenes that I probably don't even know of
And of course, Praise DuARTe
Reserved
Reserved II
Reserved III
Last one, I promise!
OK so I tried this out. I do have multirom experience with my Nexus 4. I was in CM12.1. With tdhite's 1-11-15 kernel which according to his changelog has kexec support. Installation of multirom recovery went fine. Rebooted recovery. Installed multirom.zip went fine. I installed another cm12.1 ROM as a secondary ROM to test and it installed fine. Rebooted. In the multirom boot I chose the secondary ROM, it failed to boot saying primary ROM kernel did not have kexec support. So I'm assuming either the kernel doesn't have full kexec support for multirom or something else is borked. I'll ask about kexec support in his kernel thread. Any other thoughts?
@tdhite can help in patching kexec for his kernel to get the multi rom fully working
I have fixed kexec on the kernel
U applied wrong patch on it
Brawn_Sg said:
I have fixed kexec on the kernel
U applied wrong patch on it
Click to expand...
Click to collapse
Link to fixed kernel?
perfoliate said:
Link to fixed kernel?
Click to expand...
Click to collapse
Multirom is not far
I have made the kernel and I will make my separate multirom and twrp
So wait for today
Everything of mine will be separate
If anybody'd like to help out on the kernel/patch, as I might not get much time to work on it for the next few weeks, I can put everything on github and post it here.
seems to be running awesomely amazing on my phone good work yall
JCroffut said:
seems to be running awesomely amazing on my phone good work yall
Click to expand...
Click to collapse
Which kernel did you use?
Tdhk-24-05?
Yea the newest tdhk. It seems he fixed kexec
@JCroffut - Are you using "stock" as the main ROM with the recent "LP" kernel?
JCroffut said:
Yea the newest tdhk. It seems he fixed kexec
Click to expand...
Click to collapse
Thanks for the heads up. I'm going to try out this kernel tomorrow and if it works fine I'm going to talk with tdhk to see if he can help me out with making a general patch to try and merge into the cm kernel. Sorry I haven't done much here lately, finals are soon and I'm juggling 3 big projects. Again thanks for the heads up.
Sent from my Moto X using XDA Forums
Right now im only using 1 rom, but last night i had Carbon as my primary, with tdhk, and I had Paranoid as a secondary, again with tdhk. Everything ran fine.
JCroffut said:
Right now im only using 1 rom, but last night i had Carbon as my primary, with tdhk, and I had Paranoid as a secondary, again with tdhk. Everything ran fine.
Click to expand...
Click to collapse
Thanks for the info - I was hoping to keep stock as my Primary.
JCroffut said:
Right now im only using 1 rom, but last night i had Carbon as my primary, with tdhk, and I had Paranoid as a secondary, again with tdhk. Everything ran fine.
Click to expand...
Click to collapse
can you list out all the steps you went through? i tried this setup but multirom keeps saying that the kernel doesn't support kexec-hardboot (can confirm carbon rom is running tdhk 05-24).
thejrcrafter2 said:
can you list out all the steps you went through? i tried this setup but multirom keeps saying that the kernel doesn't support kexec-hardboot (can confirm carbon rom is running tdhk 05-24).
Click to expand...
Click to collapse
Same results here. Getting same error.
Pk I return to this project
Someone who knows how to compile kernel
Actually I don't have build machine
Or someone who has ubuntu
I will provide him with my new kexec kernel source
Tell me anybody ?