Building AOSP - No baseband - Xperia Z5 Compact Q&A, Help & Troubleshooting

Hi guys,
I'm trying to get myself started in the process of building custom ROMS and whatnot, so I decided to mess a bit with my phone, backing up TA, unlocking bootloader, rooting, etc.
Now, I was trying to test out AOSP for a bit to get a sense for what a basic android feels like and what might be missing, so I followed Sony dev's tutorial on building AOSP, copying the binaries to the vendor folder and all and I flashed it into my phone.
However, I can't get the SIM card to work at all. It says baseband is unknown. Could you guys shed some light into what I may be missing?
My stock Z5C is on version 32.4.A.1.54 (Customized PT) if that matters, after I restored TA and stock firmware, everything works fine again, it also works on LineageOS roms
Thanks

Related

[Q] No network on custom ROMs

Hello everyone, after a lot of desperation I finally decided to create a topic discussing my problem.
Few weeks ago, I decided to change ROM in my i9100 to SlimBean, since that moment I have been experiencing variety of problems. First problem came directly after flashing SlimBean, my phone was suddenly SIM locked. After some time, I managed to unlock it (or atleast I think so). Also, I went back to stock ICS ROM. Everything was good, but you know.. Stock is stock. So I went throught the forums and checked for some ROMs. Since I found that CM is finally stable, I flashed recovery from their thread and continued in flashing ROM itself. Everything went smooth, after few moments I was booting into CM. When the booting finished, I found out that I have no network signal. I checked the IMEI, it was correct. After trying few things, I decided to try another ROM. Same problem, no network available. I went back to stock ROM, network is working. I have tried various versions of stock ROMs, from 2.3.6 all the way up to 4.1.2. All stock ROMs run without a problem, once I go with custom ROM, no network is available. Any hints?
I believe I have the same/similar problem. I have spent hours playing around with different things (changing modems/kernels/ROMs) and nothing seems to work. I modified my nv_bin file in the efs folder recently to unlock my phone (the unlock code no longer worked). I did this from within a stock 2.3.5. When that worked, I installed a back-up I had of 4.1.2 (Resurrection Remix v3.1.2) and everything was still fine. But when I tried to upgrade to CM 10.1 or Resurrection Remix v4.0.7 (or CM 10.2 nightly), I got no signal and couldn't locate any networks. When I went back to the Resurrection Remix (Android 4.1.2), everything was fine. I've installed various ROMs between my i9100 as well as my i9505 so it's not a matter of not installing them correctly. As far as I can tell, anything past 4.1.2 doesn't seem to like the edited nv_bin file. This was necessary as it's a carrier model from Chile and I wanted to be able to use it with other sims. Reverting back to an unedited nv_bin is not an option.
I ran EFS Professional and repaired my nv_bin file with 4.3 installed. With the carrier's sim, everything is roses. When I insert another sim, I get the network unlock prompt. Although I do have an unlock code, it doesn't work anymore (and hasn't for a long time). When I revert back to the edited nv_bin file that I had backed-up, I don't get the network unlock prompt anymore but I don't get any signal either, regardless of the sim card. I am able to see my IMEI and my phone finds the access point for whatever sim I install but it can't find any networks.
Anybody have any ideas?

Ordered i9300 from eBay - need help to understand what's going on

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.

Cm11 "cannot connect to camera", permanent fix?

Hi,
I'm currently running CM11 nightly (20141206) and haven't been running stock since at least a year and a half (read: I don't remember the last stock version I were running).
I have the common issue where Android cannot connect to the camera. The often posted "camera restart" does the trick, but I've read various places that flashing the latest stock rom and opening the camera once fixes this issue permanently, even after flashing custom roms again. Since my phone is laggy and I've been dirty flashing for a long time I figure it is time for a clean flash anyways. Is it correct that this would fix the issue?
If so, how should I go about doing it? I remember reading about an upgraded EFS partition in newer roms that aren't compatible with certain modems etc. My current baseband version is I9300XXEMB6. Is this something I need to take into account? (if I backup the current EFS and something goes wrong in upgrading to the newer version, will I be able to restore it afterwards?)
Also, does the latest stock roms contain Knox (or what it's called)? I suppose I don't want that?
I know there are bits and pieces spread around on the forum, but if someone could outline the process for me, or even better, point me towards some step by step guide covering the above, that would be much appreciated.
In advance, thanks a bunch!
-AndyGizzle
Trying a tiny little bump on this one

[Q] How to deodex .167 rom ?

just got this phone yesterday, and it was on 4.4.4 , so I went through the rooting process (downgrade/root/upgrade) and everything is working fine
I did build my pre-rooted .167 version based on my customization number (downloaded files through xpirifirm), and spent today restoring my backups with titanium, but I just noticed that now I'm using an odexed rom, which I totally hate since it isn't mod-friendly, so I decided to look into deodexing
The thread I found with google points to a deodex script by a dev here on xda, problem is it does not work with Z2, so my only current choice is to download a pre-rooted & deodexed rom and use that, I'd rather create one from my device's Customization FTF file, but I haven't gotten any luck, yet.
I used to have a Note2, and I created a couple of deodexed roms for personal use and for the sake of learning how to use android kitchen, any ideas if it works with the Z2 stock rom (kitchen thread doesn't mention anything)
would appreciate any help, still a Sony/xperia nub, so please take it easy on me
Kamome Tool is something you can use or you can download one already pre-made
yeah, I eventually used that on my phone, and it seems to work fine, although there are some odex files left (due to lack of companion jar files)
I didn't want to download a pre-made rom since it meant different customization number, and people were reporting NC (noise cancellation) not working when using such roms, plus I got to learn something new myself this way
ticktock666 said:
yeah, I eventually used that on my phone, and it seems to work fine, although there are some odex files left (due to lack of companion jar files)
I didn't want to download a pre-made rom since it meant different customization number, and people were reporting NC (noise cancellation) not working when using such roms, plus I got to learn something new myself this way
Click to expand...
Click to collapse
noise cancleing is a odd one.
if it works on your current rom, itll work if you flash anorher
but if you data wipe on the 2nd rom it stops working untill you go back to the one it was working on
so i had a tiwanese FTF flashed and NC was working. i flashed a custom rom and it was still working till i had to wipe my device

[Xperia P] Phone crashes shortly after successful boot - independent from ROM!?

Hi,
I have quite a serious problem with my phone.
I used stable CM11 as my ROM lately, worked nice, seemed to be ok. Now, if I want to boot my phone, it suddenly crashes as soon as I want to enter unlock code. "Funny" thing is, performing a full backup via TWRP didn't help.
So I decided to wipe everything (even sdcard) and do everything from scratch, including flashing boot.img. After flashing the ROM zip, it's still the same.
After that, I flashed boot.img from AOSP 5.1 Unstable, installed this new, different ROM (which I had successfully tested on my device before) and STILL THE SAME?!
What's going on here? It sounds a bit like defective hardware, but I never experienced a crash when I was in Recovery mode, so that's quite unplausible.
My last idea is to flash stock ftf. Perhaps this will help...

Categories

Resources