XperiaSP Locked Bootloader (LBL) Cyanogenmod 12.0

Search This thread

TechGerbil

Member
Sep 7, 2014
8
0
OK I tried your work but now i want to go my stock rom and os and how to do that ????
I am new in android

If you want to go back to the original Sony rom, either repair your phone through PC Companion or down the ftf and flash with Flashtool. Repairing with PC Companion would mean it'll install the latest available version (4.3). If you want to install older versions, you would have to flash it yourself with Flashtool.

Stock Sony ftf: http://xdaforums.com/showthread.php?t=2311964

Flashtool and guide: http://xdaforums.com/showthread.php?t=2658952
 
Nov 4, 2013
13
1
35
New Delhi
If you want to go back to the original Sony rom, either repair your phone through PC Companion or down the ftf and flash with Flashtool. Repairing with PC Companion would mean it'll install the latest available version (4.3). If you want to install older versions, you would have to flash it yourself with Flashtool.

Stock Sony ftf: http://xdaforums.com/showthread.php?t=2311964

Flashtool and guide: http://xdaforums.com/showthread.php?t=2658952

the steps provided didn't helped me any other solution pls.
 

pcgardner

Member
Dec 24, 2012
49
11
Leeds
Was going to try that but I can't get back to the recovery. I'm pressing the camera button but it just continues to boot. Rebooting to recovery through the power menu doesn't work either.

I have exactly the same problem, and posted here a few days ago (copy below) asking for help, but nobody replied :( Does flashing CM12 disable the CWM recovery? How do we reinstall the recovery?

---------- Post added at 10:38 AM ---------- Previous post was at 10:25 AM ----------

Recovery not working after installing CM12

I have just installed CM12 on my Xperia SP C5303 (locked bootloader) using the method in this thread. Everything seemed to go well, no errors, and the phone boots into CM12 without problems.

However, I can no longer boot into recovery, despite trying all the tips here, plus adb reboot recovery - it always boots into CM12. I tried repeating the recovery installation, but now it fails with the error "Version : Unknown --> (ERROR: NOT COMPATIBLE) " I see that step1.sh checks for CM11 but not for CM12 - is that because it's really incompatible with CM12 or just because step1.sh hasn't been updated?

Would it be safe to remove the version checks (or to add one for CM12) and then re-run install.bat? I don't want to risk bricking my phone!
 

trioset

Senior Member
Nov 23, 2014
151
122
London
Was going to try that but I can't get back to the recovery. I'm pressing the camera button but it just continues to boot. Rebooting to recovery through the power menu doesn't work either.

Please press VOLUME UP (after the nightrider LED effect + vibrate)

You can also press volume down but i find the touch sensitivity in twrp makes it unusable.

The power menu boot to recovery doesn't work
 
  • Like
Reactions: TechGerbil

aftreck

New member
Apr 26, 2015
1
0
Mumbai
Gave it a 3rd try nd have to say its working like charm now....
I have no issues with mobile data nor with brightness...its really smooth now...very happy !!!:eek:
 

kkh97

New member
Apr 25, 2015
1
0
used the rom for about a day then afterwards the device rebooted itself suddenly and its just stuck at the "sony" logo and nothing is happening. please help
 

bushladen

Senior Member
Apr 20, 2014
189
36
Paris
Please try V3 fixes.

Or V4 fixes...
and edit /system/etc/init.d/00fixes for more options if multitasking is still no good

I tried to give a look inthere but can't understand anything... :confused:
I will try the RR build to see if i got the same freezy lagguy issues...
If it works well, do you think that you could port the ram managment of RR on CM12?
Fix V4 allready flashed but still la...gg...y free....z....y...

Sent from my Xperia SP using XDA Free mobile app
 

trioset

Senior Member
Nov 23, 2014
151
122
London
Ok i have the minifree values but what line I have to change ? (Minifree or Minifree-2 )
How i can enable zram ? to have 128 Mb

From V4 default edit /system/etc/init.d/00fixes find this line

Code:
# uncomment this line to disable zram
fix-zram-off &

and change to like this

Code:
# uncomment this line to disable zram
[COLOR="Purple"]#[/COLOR] fix-zram-off &

And to change zram edit: LMK values edit /system/bin/fix-minfree-2

Delete this line

Code:
    $D "Setting low memory killer minfree parameter 2000,4000,8000,16000,21000,32000"

And change this line to your values

Code:
    echo "[COLOR="purple"]2000[/COLOR],[COLOR="purple"]4000[/COLOR],[COLOR="purple"]8000[/COLOR],[COLOR="purple"]16000[/COLOR],[COLOR="purple"]21000[/COLOR],[COLOR="purple"]32000[/COLOR]">$MINFREE

Where the 6 comma separated numbers are values in pages of 4kb

---------- Post added at 11:57 AM ---------- Previous post was at 11:54 AM ----------

Is this ROM even maintained? Bagyusz hasn't been active since February. :confused:
Could it be the show is over?
 
Last edited:

reinipic

Senior Member
Apr 30, 2014
257
169
Vienna
www.img-media.org
I have the same problem. Could you please give me an answer?

Hi guyys, I think you are not allone. I was on CM11 Rom (LBL) for over a year - two month ago I flashed CM12 for the first time. Now the troubles begin:
Because CM12 especially 5.0 over all is still a problem (wifi, calls etc.) even for their own Nexus series.
Anyway, I had a perfect backup of CM11 and I had perfect backup of the currently running CM12 Rom.

Because I need a stable running Rom for my bisiness, I switched always again back to my CM11 Rom.
But some day last week I flashed back to CM11 and was in a full bootloop. No chance to go back to Recovery or anything else.
Reason: I don´t know why, but there is something in the scripts of Kitkat or Lollipop, that damages SD cards, when you often switsch between the two systems. The sd card was dead, only readable, but not writeable again!!!

So in the latest backup I made to the sd card, not all data have been written on it (not a complete backup) and when i tried to restore the system, with CWM, only parts of the recovery were readable. Hehe, bootloop. **** happens
I personally think, that is a problem since Kitkat. Google allowed only verified apps to write on SD-card. I assume, that there is a problem in the scripts.

My tip: Save your time with experiments - install your phone from beginning with .ftf file. I did it too
Greets, reinipic
 

Georakos

New member
May 6, 2014
3
0
Hi guyys, I think you are not allone. I was on CM11 Rom (LBL) for over a year - two month ago I flashed CM12 for the first time. Now the troubles begin:
Because CM12 especially 5.0 over all is still a problem (wifi, calls etc.) even for their own Nexus series.
Anyway, I had a perfect backup of CM11 and I had perfect backup of the currently running CM12 Rom.

Because I need a stable running Rom for my bisiness, I switched always again back to my CM11 Rom.
But some day last week I flashed back to CM11 and was in a full bootloop. No chance to go back to Recovery or anything else.
Reason: I don´t know why, but there is something in the scripts of Kitkat or Lollipop, that damages SD cards, when you often switsch between the two systems. The sd card was dead, only readable, but not writeable again!!!

So in the latest backup I made to the sd card, not all data have been written on it (not a complete backup) and when i tried to restore the system, with CWM, only parts of the recovery were readable. Hehe, bootloop. **** happens
I personally think, that is a problem since Kitkat. Google allowed only verified apps to write on SD-card. I assume, that there is a problem in the scripts.

My tip: Save your time with experiments - install your phone from beginning with .ftf file. I did it too
Greets, reinipic[/QUOROM and let me know how I do it?

Thank you very much for your answer. I really appreciate that you care about us. Can you prob link the file that is for the stock ROM? Greeting's
 

Top Liked Posts

  • There are no posts matching your filters.
  • 251
    217989_cm.jpg

    translated by Kizsde :highfive:

    I would like to ask everbody not to send me PMs with questions about the installation, that is what the forum is here for. Also everbody should do this at their OWN RISK!

    If you already have recovery installed, go to step (3) and continue from there.

    217989_su.png

    (1): As a first step, we should "root" our stock 4.3, so later on we can install a recovery tool:

    - a: Download the towelroot apk and click on the Lambda icon
    - b: On the phone, navigate to Settings > Security and check the Unknown Resources checkbox
    - c: Copy the tr.apk to your phone's SD card and install it
    - d: Estabilish an active internet connection on your phone
    - e: Run the towelroot app and once it loaded, tap on the "make it ra1n" button. This should "root" your phone.

    **The reason why the word "root" is between quotation marks, is because the towelroot app doesn't actually root your phone, but allows a superuser application to be installed on it. We don't actually need an SU app, but "root" is needed for the installation of the recovery.

    217989_cwm_2.png

    (2): Installing the Recoveries (source: [link])

    -a: On the phone, navigate to "Settings > Developer Options" and check the "USB Debugging" checkbox. If you don't have it listed, just tap the "Build Number" within "Settings > About Phone" 4-5 times.

    -b: Connect your phone to the PC

    -c: Download the recovery pack created by dssmex

    -d: Extract the CWM_SP_4.4.1.zip file to your computer and depending on your operating system run the appropriate install***** file (install_mac.sh= MAC OSx; install_linux.sh= Linux; install.bat= Windows) **(On Windows a menu will appear, where you need to choose option "1" and the rest will be done automatically)

    -e: If the installation is successful and you see no errors, you can reboot your phone. Otherwise repeat the installation until it is completely error-free

    -f: After reboot, the phone indicates with some blinking lights and a slight vibration that you are now able to select from the recoveries (volume rocker down=TWRP recovery; volume rocker up=Philz recovery; camera button=CWM recovery). It is up to you which one you select, as all of them should be able to do the job just fine. Personally I recommend CWM and the guide will follow this method. IMPORTANT: During the recovery selection, the idle time is 2 seconds and if no button is pressed, the phone will boot normally.

    217989_cm_11_2.jpg

    (3): Installation of the CM12 rom:

    -a: Download the newest rom from here: [link]

    -b: Copy the cm-12-201*****-UNOFFICIAL-lbhuashan.zip to your phone, preferrably to the external SD card. (This can be performed during recovery too, but copying to the SD card is significantly slower this way, so before you do that please read section (4))

    -c: During recovery selection, choose CWM

    (Quick CWM navigation guide: With physical buttons: Volume down=move down; Volume up=move up; On/off button=Enter/select menu option; || With swipe gestures: Swipe down: move down; Swipe up=move up; Swipe right=Enter/select menu option; Swipe left=back)

    -d: Make a backup of your current system, by going to "backup and restore" and selecting the "backup to /storage/sdcard1" option. This will create a "clockworkmod" folder on your SD card and the dated backups will be stored here.

    -e: Now go to "Wipe data/factory reset" and select the "Yes-Wipe All user data" option. This will erase the /Data /Cache partitions and delete the ".android_secure" folder on the SD card. IMPORTANT: This may take several minutes to complete.

    It is advised to do the following when performing a clean install:

    It may happen that the installer is unable to format the system, so it needs to be perfomed manually by going to "mount and storage" and selecting the "format /system" option.

    -f: Navigate to "install zip->choose zip from /storage/sdcard1" then browse to and select the previously copied CM11 rom

    -g: The CM12 rom should now be installed. If you don't prefer to install the Gapps pack, then reboot your phone with the "reboot system now" option, otherwise go to step (4)

    217989_gapps.jpg

    (4): Installation of the google apps (Gapps):

    -a: Download the newest CM12 gapps from this list

    -b: Copy it to the external SD card

    -c: Go to CWM recovery again (camera button)

    -d: Navigate to "install zip->choose zip from /storage/sdcard1" and select the Gapps pack you just copied to the SD card


    (5): Installation of the SuperSU app:

    -a: Download the newest UPDATE-SuperSU-v2.**.zip

    -b: Copy it to the external SD card

    -c: Go to CWM recovery again (camera button)

    -d: Navigate to "install zip->choose zip from /storage/sdcard1" and select the UPDATE-SuperSU-v2.**.zip you just copied to the SD card

    -e: Once installation is done, reboot the phone

    217989_letoltes_2.jpg

    What works:

    USB Charging : Ok
    USB ADB : Ok
    USB MTP : Ok
    Video : Ok
    Audio : Ok
    Sensors : Ok
    Screen rotation : Ok
    WLAN : Ok
    WLAN Hotspot : Not tested
    GPS : Ok
    GSM : Ok
    GSM Data : Not tested
    GSM Voice : Not tested
    GSM SMS : Not tested
    Bluetooth : Ok
    NFC : Ok
    Camera : Ok
    FM Radio : Ok
    Keyboard : Ok
    MHL : Not tested
    OTG : Not tested

    What doesn't work:
    ???

    ----------------------------------------------------------------------------------------------------------------------​

    Frequently Asked Questions + Useful info:

    - The first boot will always be slow. This is because once you enter your google account details it starts updating the google apps and your personal details, while downloading your own applications as well

    - The rom does not include Sony's own services and user interface

    - The rom is rooted by default

    - You cannot apply any custom kernels as the bootloader is locked

    - After first boot, turn off NFC (or at least try to remove the check from the checkbox, it will not be possible due to a bug), then reboot the phone. After this you will be able to turn it on/off as per usual.

    - The rom contains CWM and Philz recovery too (camera button=CWM; volume up=Philz)

    - Glove mode is turned on by default, but if you would like to turn it off, go to "Settings->Language & Input" and remove the check from the "High Touch Sensitivity" checkbox

    - To enable "Developer Tools" & "Performance" menu options, navigate to "Settings->About Phone" and tap "Build number" 4-5 times

    - Hijack is a script that enables useres to boot not only stock roms on a locked bootloader, but custom ones too like Cyanogenmod, aopk, pa, pac, slimkat, omni etc...

    - It is not possible to update a rom OTA, only from recovery. The method of updating the rom is the same as installing it from step (3), the only difference is that the "-d: wipe data/factory reset" part needs to be skipped

    - If you want to play games, it is a good idea to change the "Profile" to "Performance" under the "Performance" menu option for the duration of play

    - You can make the Google search bar disappear from the home screen by opening the settings menu of the Trebuchet launcher via long press. Then expand the advanced settings by swiping up the grey bar of Wallpapers Modules Themes. Here look for the Search bar and switch it off.

    217989_log.jpg

    ROM: cm-12-20160130-UNOFFICIAL-lbhuashan

    GAPPS: gapps-502-base-********-1-signed.zip

    SuperSU: You need to install SuperSU !!!!

    Changes:

    cm-12-20160130-UNOFFICIAL-lbhuashan:
    -CyanogenMod update-source (nighty)
    -RIL source code update
    -Selinux disabled
    -Wifi mac loader fix
    -Audio fix
    -Audio vendor blobs update
    -glove mod settings fix
    -Adreno driver update
    -Add some tweaks

    cm-12-20150120-UNOFFICIAL-lbhuashan:
    -GSM fix
    -WIFI fix
    -BT fix
    -GPS fix
    -Camera fixed (1080p video recording OK)
    -FM radio fix
    -NFC fix
    -Hot reboot fixed

    ----------------------------------------------------------------------------------------------------------------------​

    Source codes:

    CyanogenMod

    Device tree:

    android_device_sony_lbhuashan

    android_device_sony_lbqcom-common

    android_device_sony_lbcommon

    android_vendor_lbsony

    hijack-ramdisk-huashan

    Kernel Source:

    android_kernel_sony_lbmsm8960t

    Screenshots:



    Credits:

    -MrSteve555
    -neXusPRIME
    -dh.harald
    -KeiranFTW
    -cray_Doze
    -davidmarco
    -dssmex
    -DooMLoRD
    -Cyanogenmod

    XDA:DevDB Information
    XperiaSP Locked Bootloader (LBL) Cyanogenmod 12.0, ROM for the Sony Xperia SP

    Contributors
    bagyusz
    ROM OS Version: 5.0.x Lollipop
    ROM Kernel: Linux 3.4.x
    Based On: CyanogenMod

    Version Information
    Status: Nightly

    Created 2014-11-20
    Last Updated 2016-01-30
    37
    New build incoming: :)
    https://mega.co.nz/#!bEBzASgJ!fzkGUsJOslojUzvdV-VR-vFbXq5DKxz0F2hP2gTMOJ0
    Let's have a look at the changelog(compared to bagyusz build)
    - used dlmalloc instead of malloc
    - fixed camera
    - set selinux to permissive at boot(fixes Wi-Fi and cellular connectivity)
    - CM source updates
    - some small cosmetic changes to the whole build here and there ;)
    32

    Yes, I'm going to pretend that I haven't even looked at the ETAs and trolling here, I'll let the mods sort it out if it's necessary :angel:

    Hmm, just gone browsing through all the fusion3 github repos and found this:
    Code:
    ro.use_data_netmgrd=true
    It could fix data connectivity(without using the script), although I'm not really sure about that(yep, it's a build.prop line)
    Anyway, I saw a first commit for sepolicy on gerrit and now it's finally booting again with qcom common sepolicy set but yay no bugs are fixed. I'll look at the logs when I get some actual free time (and school doesn't help with gaining free time [emoji14]).
    Anyway, to sum everything up and calm everyone down:
    Yes, someone is working on it. Slowly, but it's going forward.;)
    31
    Ok as of now what's working and what's not?
    Video and audio: working, although probably needs additional stuff like qcmediaplayer in framework to get the streams to wrok properly(YT, Netflix and all that stuff)
    Camera: working, needs framework changes that are on its way on gerrit
    WiFi: working, needs sepolicy changes to work with selinux enforcing
    RIL: nearly fully working, harware_qcom_ril repo needs some changes for RILs that support SEEK(our does), I got outgoing calls working on my private builds with header changes, but it has to be done officialy by some CM team members, more - it needs sepolicy changes to work with enforcing, but probably the latest commits in the common qcom sepolicy repo are fixing that with the bridgemgr policy inclusion
    Touch: obviously working
    NFC: reported working, didn't test myself
    Sensors: working
    ADB, MTP, genral USB functions: working
    Bluetooth: working
    WLAN hotspot: doesn't work and for now I have no idea how to fix it
    GPS: not tested
    FM Radio: it will take some time :p we don't have all the CM features yet, so I think the best choice is to wait until everything is buildable and correctly updated
    27
    All links are here
    Only data is not working
    But hey its Lollipop
    Thanks to MrSteve.

    Download rom..
    1. Rom (build 24/11): https://mega.co.nz/#!bEBzASgJ!fzkGUsJOslojUzvdV-VR-vFbXq5DKxz0F2hP2gTMOJ0

    Move this file to System/Bin
    2. Ramdisk (after downloading rom, open zip and move ramdisk.zip to system/bin): https://mega.co.nz/#!OcZAgShK!6OT9JiwMoieghZao8Zx_8OrlX9ITPZWytIPqeS5Phic

    3. Flash the rom

    Flash root
    4. SU (root): http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip

    Flash Gapps
    5. Gapps (Lollipop): https://www.androidfilehost.com/?fid=95784891001612867

    Flash this zip
    6. Outgoing call fix: http://xdaforums.com/attachment.php?attachmentid=3041707&d=1417382501

    Note: to avoid reboots
    go to settings> display> turn off the adaptive brightness.