{18/07/14} [KK 4.4.4] neXusCM 11 for XSP, Build # 5 [LBL UBL] - Xperia SP Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
neXusCM​
CHANGE-LOG:​
Build # 5
-CM latest source
-Linaro 4.8
-All audio video patches and updated binaries,libs from my PA tree
-Rear mic fixes also included
RECOMMENDED KERNEL: STOCK 205
Build # 4
- CM updated source and new apps.
- New files from 205 firmware
- Removed old build props and updated with new ones.
- Glove mode patch removed for touch stability
Build # 3
- CM source update
- fixed and updated ramdisk
- Sepolicies restored to original
- Userdebug build instead of eng
Build # 2
fixed ramdisk
Build # 1
-Initial Build
Click to expand...
Click to collapse
Click to expand...
Click to collapse
DOWNLOAD​:
Build # 5:
http://d-h.st/K8H
NOTE: Flash this for Audio Echo Fixes and Volumes
https://mega.co.nz/#!vQp1BCha!kvuw31Bx5r03qf_b3U8vMZ64qU9doBQc4f6vsK6nH48
Build # 4:
https://mega.co.nz/#!HYxziQZK!ERbol6pVsKuiMPnxw4vhO-JYZGRPmTPjl-jvdlMtR8I
Build # 3:
http://d-h.st/EUK
Build # 2:
https://mega.co.nz/#!WApk0QaL!oIsNBseh-7bhbrEp9fMXFUtSGGw6TNpPdSvtZEq1ICc
Build # 1:
http://d-h.st/QdX
Click to expand...
Click to collapse
Click to expand...
Click to collapse
GAPPS:
http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Locked BLs FTF Files:
Kernel 205 FTF:
https://mega.co.nz/#!zJohFDzb!bgo6C1MjtiBdVQZXkjl-r-n9wQAkTAsRzo0K5ynERWk
Kernel 201 FTF:
http://d-h.st/DgV
Click to expand...
Click to collapse
Click to expand...
Click to collapse
WORKING:
Everything apart from below
Click to expand...
Click to collapse
NOT WORKING:
Rear MIC, although i havent confirmed myself
Use SPIRITFM for Radio
Click to expand...
Click to collapse
Click to expand...
Click to collapse
INSTRUCTIONS:
1. I suppose you have a custom recovery. (Philz, TWRP, CWM are all good to go)
(Use latest LBL recovery. If you can't find it, go die !!!)
2. I hope you can download the zip from link below in Download category.
3. Place it on SD Card and boot to recovery and flash it.
4. Wipe factory reset (dont argue why full reset, and why wipe AFTER installing zip)
5. Use flashtool (for locked) to flash 205 kernel ftf.
Use fastboot (for unlocked) to flash anything u want which is cm11 compatible.
6. Reboot. (AND SUFFER if you forgot to flash GAPPS, you deserve this)
7. Reboot again to recovery to flash GAPPS and accept your insolence.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
SOURCE:
https://github.com/neXusPRIME/android_device_sony_huashan
https://github.com/neXusPRIME/android_vendor_sony
https://github.com/neXusPRIME/android_kernel_sony_msm8960t
Click to expand...
Click to collapse
Click to expand...
Click to collapse
CREDITS:
-bagyusz
- MrSteve555
-dh.harald
-KeiranFTW
-cray_Doze
-adfad666
-davidmarco
-dssmex
-DooMLoRD
-Cyanogenmod team
Click to expand...
Click to collapse
Click to expand...
Click to collapse
​

---

So If coming from 4.3 ( .201 FW )...Wipe data/cache/dalvik then flash ROM? then reboot after first boot?
thanks

---

Revontheus said:
So If coming from 4.3 ( .201 FW )...Wipe data/cache/dalvik then flash ROM? then reboot after first boot?
thanks
Click to expand...
Click to collapse
Yes, u can keep 201 kernel stock or optionally 205 via flashtool.
Although i only flashed via PHILZ.

---

What does "GSM/MOBILE BASEBAND: NOPE" mean?
Tia!
Sent from my C5303 using XDA Free mobile app

---

air001 said:
What does "GSM/MOBILE BASEBAND: NOPE" mean?
Tia!
Sent from my C5303 using XDA Free mobile app
Click to expand...
Click to collapse
don't work.

---

"What does "GSM/MOBILE BASEBAND: NOPE" mean? "
This mean phone calls don't work? And 3G doesn't work?

---

Precisely !

---

So then what does this rom good for?

---

It's useless right now but I hope the bugs will be fixed in the next version.

---

@neXus PRIME
I just want to report that flashing via TWRP doesn't fix baseband issue. Small step forward, but now it's clear that the issue is somewhere in source.
I'd suggest you to start from strach and use unmodified bagyusz sources. After that there will be time to add some updates. If that won't work, it means that 4.4.3 brings new RIL management or something similiar. Even one commit could break it.

---

Raz9 said:
It's useless right now but I hope the bugs will be fixed in the next version.
Click to expand...
Click to collapse
I also hope your useless feedback is also fixed in future versions.
I am filling in VOLUNTARILY for bagyusz until he is back, not my duty ... and people askedme to port 4.4.3.
Stay away from this development threads if u are allergic to bugs.

---

MrSteve555 said:
@neXus PRIME
I just want to report that flashing via TWRP doesn't fix baseband issue. Small step forward, but now it's clear that the issue is somewhere in source.
I'd suggest you to start from strach and use unmodified bagyusz sources. After that there will be time to add some updates. If that won't work, it means that 4.4.3 brings new RIL management or something similiar. Even one commit could break it.
Click to expand...
Click to collapse
Thanks, The sources are UNMODIFIED. Its something to do with releasetools maybe
The only change i do is delete the line:
TARGET_RELEASETOOLS_etcetc..... Could it be the reason?

---

Thanks given for @neXus PRIME and @MrSteve555, appreciate the efforts.
Would love an update on LBL Slimkat if possible
Sent from my C5303 using Tapatalk

---

@neXus PRIME
If you didn't touch the dev trees, CM sources, and you only modified releasetools, I'd suspect the root of the problem there.

---

MrSteve555 said:
@neXus PRIME
If you didn't touch the dev trees, CM sources, and you only modified releasetools, I'd suspect the root of the problem there.
Click to expand...
Click to collapse
But it has nothing related to baseband... i searched and lot of threads tagged cm11 unknown baseband many xperia phones too. There is a fix floating around. Please help me search it.
One such post is:
http://forum.xda-developers.com/showpost.php?p=52006785&postcount=6
in here:
http://forum.xda-developers.com/showthread.php?t=2720512

---

Flashing LBL Cm11 via Twrp and Philz gave me no baseband only via Cwm did it work.
But I had no WiFi Hotspot on any.
Sent from my C5303 using Tapatalk

---

Treboeth said:
Flashing LBL Cm11 via Twrp and Philz gave me no baseband only via Cwm did it work.
But I had no WiFi Hotspot on any.
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Which CWM made it work??? I can fix hotspot but need to know the CWM version.

---

Same baseband issue here too:
https://code.google.com/p/freexperia/issues/detail?id=2419

---

neXus PRIME said:
Which CWM made it work??? I can fix hotspot but need to know the CWM version.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2649923
This is the one I used but may have caused confusion I meant this rom http://forum.xda-developers.com/showthread.php?t=2735975

---

I found that:
There is a fix in the first post, maybe it will be helpful.
http://forum.xda-developers.com/showthread.php?t=2762703
Also, we should have in mind that the ramdisk changes when the Android build changes, and running new build on kernel/ramdisk can lead to weird issues. Maybe not in our case but worth checking.
I know the releasetools aren't connected to baseband but it's the only thing that was changed by you.
Also, flashing basebands after flashing the ROM doesn't do anything, it still stays unknown. So the issue really goes deeper than the baseband.
One thing to note: When FXP320 was released, the ramdisk was broken and baseband wasn't working, but flashing kernel from FXP319 fixed the issue. But when someone combined FXP320 kernel and FXP319 ramdisk, everything also worked fine