Hi,
I am pretty new when it comes to android development and linux kernels but nevertheless I managed to compile my first linux kernel.
And best of it, my phone even boots with the new kernel and works fine so far
However no baseband is detected (baseband version unknown in the settings), same goes for wifi.
Not even my simcard is detected.
Here is what I did sofar:
I flashed my phone with the following firmware: XT1524_SURNIA_RETDE_6.0_MPI24.65-39_cid7_subsidy-DEFAULT_CFC.xml
Everything works fine.
Then I flashed only the boot section and the sparsechunk files from the following firmware: XT1524_SURNIA_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml
I didnt flash the modem or other parts and everything still worked fine.
I got the official kernel source from motorola and changed the branch to lollipop-5.1.1-release-surnia
I used the msm8916_defconfig and the precompiled google toolchain arm-eabi-4.8 from google to compile the kernel.
It compiled fine without errors and got my zImage file as output.
Then I used Android kitchen to repack the boot.img from the RETEU 5.1.1 firmware with my new zImage and flashed it.
As I said in the beginning my phone boots but no baseband, wifi, simcard is detected.
I also tried to flash other modem versions, to no avail.
My guess is that there are some compiling options missing to use the correct baseband but unfortunetly I wasent able to come up with a solution nor did I find something on google.
So what am I missing?
Thank you in advance
Robert
Related
hi all!
Here s the story:
I went to flash VR 2.3 yesterday, which welcomed me with a blank screen at boot. Tried another rom, got same result.
A little scare and backup restore later, i was back on track and understood that those roms are KG3 based and a new kernel was not "recommanded" but NECESSARY
So, my question is this: if I update to KG3 Kernel, can I still run other stuff? If not, is it OK to flash an older kernel just for another older base rom?
Thanks!
EDIT:
[A]: Yes
Yes and no.
The actual kernel code itself has close to 0 changes from FW version to version.
(Though, there HAVE been some changes from 2.3.3 based ones to 2.3.4 ones).
Usually a 2.3.3 kernel works on most (if not all) 2.3.3 based FWs and same goes for 2.3.4.
However, there is more in the zImage than just the bare kernel code, there is the initial ram disk that takes care of booting up the OS.
Some ROMs depend on certain things to be or not to be in there (usually goes for custom kernels).
But there is really no problem just flashing a matching kernel for ROM/FW you're going to install.
Thanks a lot!
I just went ahead anyhow, and flashed KG3, then just let the phone reboot in VR 2.1 (which is KF2, I believe). it booted just fine, so I guess it might be, as you say, on a case by case basis.
I ll talk with VR dev so that he can edit the install instructions, which are a little misleading since he states this step is optional
Thanks for getting back to me!
flash this boot into your mini5
then you can use baseband 3xx in android 2.3.3 without button flashing
but it will bring another problem ：wifi couldn't turn on
I have tried it in DSC 0.6、1.1 ，it works well except wifi
it couldn't work in miui or cm7
New baseband without wifi....What is the benefit?...
Sent from my Dell Streak using Tapatalk 2
manics, would you pull and share config from this kernel?
adb pull /proc/config.gz
this boot was not builded by me
it is from a modified version of streakmi
i found it in BBS.ZHANGKU.COM
i am trying to ask the poster
but i guess maybe it is using kernel of streakmod recovery
_n0p_ said:
manics, would you pull and share config from this kernel?
adb pull /proc/config.gz
Click to expand...
Click to collapse
N0p. Want me to flash and pull?
I dont use wifi.
I try to do it tomorrow (will be near pc, so can unpack everything without flashing).
--
WiFi simply needs corresponding driver and I might blindly guess that dhd.ko from 407 should do.
the poster says ,this boot is from the earliest 2.3.3 roms of dj_steve, but he could not remember from which one.
Checked kernel config vs 407 kernel - nothing changed except resume speedup. I wonder what code in kernel could control blinking.
Hi,
I've got a German but unbranded phone and wanted to install a kernel with CWM.
The data from my original kernel showed XW LP7, so I installed the CF-Root-SGS2_XW_XEN_LP7-v5.4-CWM5.zip kernel from here.
Installation went fine, system booted and was usable afterwards. Root works, CWM too. But WiFi does not work. It always tries to get an IP, aborts, reconnects, but never connects successfully.
When I flash the original kernel again, Wifi works instantly. The original kernel can be downloaded here:
http://www.usp-forum.de/samsung-gal...samsung-galaxy-s2-i9100-original-kernels.html
It is the "XWLP7 Original Germany" one, no XEN, O2 or E+.
Attached are the version details of the working kernel.
How can I modify my working kernel to include CWM? I want to be able to flash different roms and make full backups without hassle.
Thanks.
How can I modify my working kernel to include CWM?
Will require you to learn how to build a kernel if you require to do it yourself how to is posted in development .
As per the post you flashed CWM and root from try another version or LP9 .
Other rooting methods are posted .
LP7 working for many users including myself .
jje
Hi guys,
I've ordered a new, unlocked i9300 from eBay, and I had some adventures with it:
I've unpacked it, inserted my SIM, powered it on, and found out that the phone always thinks that I'm roaming. Instead of trying to understand what's going on, I though: "I'll just install CyanogenMod and everything will be good".
I've installed CyanogenMod 10.2 (latest stable build), only to find out that my SIM is not being detected at all. It says that Baseband is unknown, IMEI and related are unknown as well.
After trying lots of stuff, I gave up and decided to return to stock ROM (4.3). While trying to do that, I bricked my phone, and the only thing I could do is enter Odin mode.
After reading dozens of tutorials and trying lots of stuff, I ended up flushing GT-I9300_mx_20120329.pit, and that unbricked my phone.
I successfully flashed Android 4.3. This version detected my SIM, displayed the Baseband/IMEI, but it didn't connect to the cellular network. I could scan for available networks, but when I chose my network manually, it said "Selected network not available ".
I tried to flush alternative modems, but all it did is making things worse. Usually it made the phone behave like with CyanogenMod, i.e. Baseband/IMEI are unknown.
Again, after trying lots of stuff, I tried to flush Android 4.1.2. That made no change until I've stumbled on this thread. Flushing Patched_Modem_I9300XXEMG4.zip made my networking work again, and restored it to behave exactly like it did initially. Again, the phone thinks that I'm roaming all the time, but at least it works.
So currently, I have two issues:
My phone always thinks I'm roaming. Is there a fix for it?
And more important: currently, I cannot install anything other than Android 4.1.2!
Could you please shed some light on the situation? What happens with my phone? Why does it think I'm roaming? Why does the SIM work only with Patched_Modem_I9300XXEMG4? How can I make other ROMs (e.g. CyanogenMod) work?
Thanks, any help is much appreciated!
9999 :) said:
Hi guys,
I've ordered a new, unlocked i9300 from eBay, and I had some adventures with it:
I've unpacked it, inserted my SIM, powered it on, and found out that the phone always thinks that I'm roaming. Instead of trying to understand what's going on, I though: "I'll just install CyanogenMod and everything will be good".
I've installed CyanogenMod 10.2 (latest stable build), only to find out that my SIM is not being detected at all. It says that Baseband is unknown, IMEI and related are unknown as well.
After trying lots of stuff, I gave up and decided to return to stock ROM (4.3). While trying to do that, I bricked my phone, and the only thing I could do is enter Odin mode.
After reading dozens of tutorials and trying lots of stuff, I ended up flushing GT-I9300_mx_20120329.pit, and that unbricked my phone.
I successfully flashed Android 4.3. This version detected my SIM, displayed the Baseband/IMEI, but it didn't connect to the cellular network. I could scan for available networks, but when I chose my network manually, it said "Selected network not available ".
I tried to flush alternative modems, but all it did is making things worse. Usually it made the phone behave like with CyanogenMod, i.e. Baseband/IMEI are unknown.
Again, after trying lots of stuff, I tried to flush Android 4.1.2. That made no change until I've stumbled on this thread. Flushing Patched_Modem_I9300XXEMG4.zip made my networking work again, and restored it to behave exactly like it did initially. Again, the phone thinks that I'm roaming all the time, but at least it works.
So currently, I have two issues:
My phone always thinks I'm roaming. Is there a fix for it?
And more important: currently, I cannot install anything other than Android 4.1.2!
Could you please shed some light on the situation? What happens with my phone? Why does it think I'm roaming? Why does the SIM work only with Patched_Modem_I9300XXEMG4? How can I make other ROMs (e.g. CyanogenMod) work?
Thanks, any help is much appreciated!
Click to expand...
Click to collapse
When the phone gets upgraded from 4.1 to 4.3 your efs changes from efs v1 to efs v2 sometimes this upgrade does not go smoothly (as in your case) so then you need to always use a patched modem from version mg4 onwards (not a normal one) if you flash a rom which changes the baseband to anything less than 4.3 then it will not work.You need to keep on mg4 or later to keep signal and because your efs is not fully upgraded properly you need to always use a patched modem and preferably kernel as well.
I am not sure about the roaming issue but if you try patched modem and patched kernel together that might help.Take a look here for some patched modems and kernels and remember you always need to use them >> https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list << You should also be able to use 4.3 roms as long as you use the patched files above ie baseband and kernel.
In general, It would be great if I could use CyanogenMod 10.2.
Should I proceed in the following order? Flush CM -> flush patched kernel -> flush patched modem.
Which of the patched versions should I choose?
Also, what do these versions change? What functionality was patched in these files? Can I read about it somewhere?
Thanks for the help.
9999 :) said:
In general, It would be great if I could use CyanogenMod 10.2.
Should I proceed in the following order? Flush CM -> flush patched kernel -> flush patched modem.
Which of the patched versions should I choose?
Also, what do these versions change? What functionality was patched in these files? Can I read about it somewhere?
Thanks for the help.
Click to expand...
Click to collapse
No the kernel will only work for 4.3 roms not CyanogenMod roms but the patched modems will work.You can try flashing CyanogenMod then the patched modem but CyanogenMod does not include a modem so whatever modem you where on when you flashed CyanogenMod you will keep.
tallman43 said:
No the kernel will only work for 4.3 roms not CyanogenMod roms but the patched modems will work.You can try flashing CyanogenMod then the patched modem but CyanogenMod does not include a modem so whatever modem you where on when you flashed CyanogenMod you will keep.
Click to expand...
Click to collapse
I tried installing CyanogenMod, then flushing some of the patched modems you've linked. Unfortunately, nothing changes - Baseband/IMEI are always unknown.
9999 :) said:
I tried installing CyanogenMod, then flushing some of the patched modems you've linked. Unfortunately, nothing changes - Baseband/IMEI are always unknown.
Click to expand...
Click to collapse
You mean flash not flush.
Also you should be careful to by things like this off ebay, There is a very high chance you brought the phone broken like this but did not notice straight away.
Don't hang around on 4.1.2 as you might get SDS.
Upgrade to 4.3 stock of higher using custom roms with a patched modem of mg4 or higher as stated by tallman43.
Read here for what you or the previous owner has done. Also on stock make sure your csc is correct.
http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289
If you cannot get it to work you need to take it in for repair. Make sure it works on 4.3 before paying.
Hi all,
I have been trying to port TWRP for my device (a somewhat dated tablet, the Toshiba AT100 Thrive) but am running into problems with the kernel. It seems that no matter what I try, I am unable to get a kernel that actually boots.
I have the full OmniROM 4.4 source (with the end intention of building OmniROM for the tablet) as well as the kernel source from Toshiba (it is their patched version of 2.6.39.4). I also have a known working recovery (built around CWM with a 2.6.39 kernel) and stock boot.img and ICS ROM for the tablet.
I have extracted the kernel config from the ICS ROM as well as the kernel command line parameters.
Additionally, I also have access to two other ports (CyanogenMod) with kernel sources for this tablet and have found the AOSP source for the 2.6.39 and 3.10 kernels.
I am using CentOS 6.7 64-bit as my build OS, as that is what I have running on my Linux machine. I have OpenJDK 1.6 installed as opposed to the Oracle version (this might affect building OmniROM, but certainly shouldn't affect the kernel build).
I can successfully compile the kernel from the Toshiba sources using the tablet's config, as well as the CM-based port kernel sources and the 3.10 kernel (2.6.39 has some bugs straight out of the Google repository, which I can only get around if I disable yaffs2 in that kernel config or replace the yaffs2 source for it with the equivalent from the Toshiba sources).
I have the Android emulator set up on my Windows machine with both a ICS and KitKat AVD. After being unable to get the Toshiba-based kernel to start on my tablet, I thought I'd try building a kernel from the sources to run in the emulator.
At this stage, not a single one of my kernels has successfully booted either the tablet or the emulator. I have tried using the kernel config from the ICS AVD to build both the Toshiba 2.6.39 and AOSP 3.10 sources. The compile completes with no errors and a zImage is produced. However, it fails to boot the emulator.
Out of desperation, I have tried downloading the toolchains for Gingerbread and ICS and using those to build the kernels instead of the toolchain provided with OmniROM 4.4. That hasn't made a difference, either.
On the tablet, I have tried extracting the known working recovery kernel from the CWM recovery and using it as a prebuilt kernel. TWRP fails to load and the tablet always reboots after a few seconds, regardless of whether I set the kernel commandline parameters or not.
I am puzzled by this. Clearly there is something wrong but I am at a loss as to how to debug it, especially as do not appear to be able to produce a working kernel either for the tablet or emulator, despite having the sources and the kernel configs.
If anyone has any suggestions, they would be much appreciated.
Still have the same problem.
I've now tried building an Ubuntu 12.04 VM and compiling the kernels within that, but still get the same results.
Does anyone have any ideas or has anyone else ever run into this problem?
Did it ever work? I am experiencing this with SM-G950F. Very keen.
Unfortunately I was not able to resolve the issue. After spending a fair bit of time on it, I gave up and moved onto other projects. I've still got everything I need to try again, so at some point I may do so (especially as a use case for my tablet is possible again in the near future).