[ROM][6.0][AOSP][{Un,}Official] LineageOS 13.0 (Marshmallow)

Search This thread

KlovesXT910BR

Member
Nov 21, 2014
12
2
31
Guaçuí
Friend, even after installing the patch for Official Lineage, to install Ln13 04/09 or 04/01, the same of the fault, both in the slot and slot 1, being slot stock losing the Safestrap.

Please inform more detailed tutorial

Thank you

Xt910 GSM

sorry for English
 
Apr 20, 2017
5
0
i was trying to flash lineageOS 13.0 on driod razr xt912 using safestrap 3.75 right after that flash open gapp but couldn't due to low storage error of system partition so i decided to increase system memory . After googling found two way of doing , 1st parted , 2nd fdisk. After getting in error in parted so i switch to fdisk . Below are the steps i did please correct me


1) connected phone in safetrap 3.75 recovery to pc. CONNECTION WAS SUCCESSFUL . took backup of /system and /data from safetrap 3.75.

adb root

adb shell

# cat /etc/fstab

/dev/block/mmcblk1p25 /sdcard vfat rw
/sdcard-ext vfat rw
/dev/block/mmcblk1p24-orig /data ext3 rw
/dev/block/mmcblk1p21-orig /cache ext3 rw
/dev/block/mmcblk1p20-orig /system ext3 rw
/dev/block/mmcblk1p23 /osh ext3 rw
/dev/block/mmcblk1p20-orig /systemorig ext3 rw
/dev/block/mmcblk1p25 /ss vfat rw

# cat /proc/partitions

179 0 15564800 mmcblk1
179 1 128 mmcblk1p1
179 2 512 mmcblk1p2
179 3 512 mmcblk1p3
179 4 1 mmcblk1p4
179 5 512 mmcblk1p5
179 6 128 mmcblk1p6
179 7 4096 mmcblk1p7 pds
179 8 512 mmcblk1p8 utags
179 9 1024 mmcblk1p9
179 10 2048 mmcblk1p10
179 11 512 mmcblk1p11
179 12 512 mmcblk1p12
179 13 4096 mmcblk1p13
179 14 8192 mmcblk1p14 boot
179 15 9216 mmcblk1p15 recovery
179 16 217088 mmcblk1p16 cdrom
179 17 512 mmcblk1p17 misc
179 18 512 mmcblk1p18 cid
179 19 4096 mmcblk1p19 kpanic
179 20 655360 mmcblk1p20 system
179 21 1048576 mmcblk1p21 cache
179 22 622592 mmcblk1p22 preinstall
179 23 1364992 mmcblk1p23 webtop
179 24 3203072 mmcblk1p24 userdata
179 25 8401792 mmcblk1p25 emstorage
179 26 128 mmcblk1p26
179 64 2048 mmcblk1boot1
179 32 2048 mmcblk1boot0

# /sbin/fdisk /dev/block/mmcblk1

Disk /dev/block/mmcblk1: 15.9 GB, 15938355200 bytes
16 heads, 16 sectors/track, 121600 cylinders, total 31129600 sectors
Units = sectors of 1 * 512 = 512 bytes

u (unit to sector )

p

Device Boot Start End Blocks Id System
block/mmcblk1p1 * 256 511 128 83 Linux
block/mmcblk1p2 1024 2047 512 83 Linux
block/mmcblk1p3 2048 3071 512 83 Linux
block/mmcblk1p4 3072 31105023 15550976 5 Extended
block/mmcblk1p5 4096 5119 512 83 Linux
block/mmcblk1p6 5120 5375 128 83 Linux
block/mmcblk1p7 6144 14335 4096 83 Linux
block/mmcblk1p8 14336 15359 512 83 Linux
block/mmcblk1p9 16384 18431 1024 83 Linux
block/mmcblk1p10 18432 22527 2048 83 Linux
block/mmcblk1p11 22528 23551 512 83 Linux
block/mmcblk1p12 23552 24575 512 83 Linux
block/mmcblk1p13 24576 32767 4096 83 Linux
block/mmcblk1p14 32768 49151 8192 83 Linux
block/mmcblk1p15 49152 67583 9216 83 Linux
block/mmcblk1p16 67584 501759 217088 83 Linux
block/mmcblk1p17 501760 502783 512 83 Linux
block/mmcblk1p18 502784 503807 512 83 Linux
block/mmcblk1p19 503808 511999 4096 83 Linux
block/mmcblk1p20 512000 1822719 655360 83 Linux
block/mmcblk1p21 1822720 3919871 1048576 83 Linux
block/mmcblk1p22 3919872 5165055 622592 83 Linux
block/mmcblk1p23 5165056 7895039 1364992 83 Linux
block/mmcblk1p24 7895040 14301183 3203072 83 Linux
block/mmcblk1p25 14301184 31104767 8401792 83 Linux
block/mmcblk1p26 31104768 31105023 128 83 Linux

2) i decide to make changes in (20-25)'s partition ( system to +3072M, cache to +1024M, preinstall to +1S, webtop to +1S, userdata to +3072M, emstorage to +8102M). But in order to make changes in (20-25)'s i had to delete 26's partitions but after creating new table starting and ending sector of 26's partitions remains the same . Also after i knew that safetrap 3.75 does not use preinstall, webtop for stock slot so i change them to +1S SECTORE.


d 26
d 25
d 24
d 23
d 22
d 21
d 20

3) after creating the new partitions. Table as follows

P

Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 * 256 511 128 83 Linux
/dev/block/mmcblk1p2 1024 2047 512 83 Linux
/dev/block/mmcblk1p3 2048 3071 512 83 Linux
/dev/block/mmcblk1p4 3072 31105023 15550976 5 Extended
/dev/block/mmcblk1p5 4096 5119 512 83 Linux
/dev/block/mmcblk1p6 5120 5375 128 83 Linux
/dev/block/mmcblk1p7 6144 14335 4096 83 Linux
/dev/block/mmcblk1p8 14336 15359 512 83 Linux
/dev/block/mmcblk1p9 16384 18431 1024 83 Linux
/dev/block/mmcblk1p10 18432 22527 2048 83 Linux
/dev/block/mmcblk1p11 22528 23551 512 83 Linux
/dev/block/mmcblk1p12 23552 24575 512 83 Linux
/dev/block/mmcblk1p13 24576 32767 4096 83 Linux
/dev/block/mmcblk1p14 32768 49151 8192 83 Linux
/dev/block/mmcblk1p15 49152 67583 9216 83 Linux
/dev/block/mmcblk1p16 67584 501759 217088 83 Linux
/dev/block/mmcblk1p17 501760 502783 512 83 Linux
/dev/block/mmcblk1p18 502784 503807 512 83 Linux
/dev/block/mmcblk1p19 503808 511999 4096 83 Linux
/dev/block/mmcblk1p20 512016 6512016 3000000+ 83 Linux
/dev/block/mmcblk1p21 6512033 8512033 1000000+ 83 Linux
/dev/block/mmcblk1p22 8512050 8512052 1+ 83 Linux
/dev/block/mmcblk1p23 8512069 8512071 1+ 83 Linux
/dev/block/mmcblk1p24 8512088 14512088 3000000+ 83 Linux
/dev/block/mmcblk1p25 14512105 31104751 8296323+ 83 Linux
/dev/block/mmcblk1p26 31104768 31105023 128 83 Linux

w (writing)

recreating table successful

q (quit)

# mke2fs -t ext3 /dev/block/mmcblk1p20

# mke2fs -t ext3 /dev/block/mmcblk1p21

# mke2fs -t ext3 /dev/block/mmcblk1p22

# mke2fs -t ext3 /dev/block/mmcblk1p23

# mke2fs -t ext3 /dev/block/mmcblk1p24

# mkdosfs /dev/block/mmcblk1p25

#mount /dev/block/mmcblk1p20 /system/

#mount /dev/block/mmcblk1p21 /cache/

#mount /dev/block/mmcblk1p24 /data/

#mount /dev/block/mmcblk1p25 /sdcard/

# mount /dev/block/mmcblk1p25 /ss/

# mount /dev/block/mmcblk1p25 /and-sec/

4) after that wiped cache, data , andriod secure, data, webtop, system.
5) restored backup of /system and /data /
6) reboot the system
7) after Motorola logo "M" got error



ap fastboot flash mode [boot failure]
0A.77
eMMC Info: Size 16g
to return to normal mode - first press power key to power down
device is LOCKED, Status Code:0

battery ok
ok to program
Connect USB
Data cable

Invalid CG OTV [CG: system]: Invalid SP Data
Invalid CG HAB [CG: system, status: 0X004E]
Invalid CG OTV [CG: system]

8) i had to use RSD LITE to flash VRZ_XT912_9.8.2O-72_VZW-16-5_1FF.xml to boot normally. :(

9) after booting i check for changes i made , f**k system returns back to default partition table.




QUESTIONS

1) where do i go wrong

2) does i have to also make change in "ebr" or "mbr" after changing partitions size

4) does it relate to preinstall and webtop which i left to +1S SECTOR

5)does lineageOS 13.0 need /osh (webtop partitions) because i was flashing saw it searching for /osh for mount

6)does to safe to left the preinstall and webtop to +1S SECTOR
 

rootdefyxt320

Senior Member
Oct 4, 2012
488
440
Sydney, NSW
Quarx managed to to repartition the Defy successfully despite the locked bootloader. Basically, the partition table was hard coded into the 2ndboot kernel and would load during the 2ndboot process. Maybe Quarx can help with repartitioning our RAZRs.
 
N

notamemberanymore

Guest
i was trying to flash lineageOS 13.0 on driod razr xt912 using safestrap 3.75 right after that flash open gapp but couldn't due to low storage error of system partition so i decided to increase system memory . After googling found two way of doing , 1st parted , 2nd fdisk. After getting in error in parted so i switch to fdisk . Below are the steps i did please correct me


1) connected phone in safetrap 3.75 recovery to pc. CONNECTION WAS SUCCESSFUL . took backup of /system and /data from safetrap 3.75.

adb root

adb shell

# cat /etc/fstab

/dev/block/mmcblk1p25 /sdcard vfat rw
/sdcard-ext vfat rw
/dev/block/mmcblk1p24-orig /data ext3 rw
/dev/block/mmcblk1p21-orig /cache ext3 rw
/dev/block/mmcblk1p20-orig /system ext3 rw
/dev/block/mmcblk1p23 /osh ext3 rw
/dev/block/mmcblk1p20-orig /systemorig ext3 rw
/dev/block/mmcblk1p25 /ss vfat rw

# cat /proc/partitions

179 0 15564800 mmcblk1
179 1 128 mmcblk1p1
179 2 512 mmcblk1p2
179 3 512 mmcblk1p3
179 4 1 mmcblk1p4
179 5 512 mmcblk1p5
179 6 128 mmcblk1p6
179 7 4096 mmcblk1p7 pds
179 8 512 mmcblk1p8 utags
179 9 1024 mmcblk1p9
179 10 2048 mmcblk1p10
179 11 512 mmcblk1p11
179 12 512 mmcblk1p12
179 13 4096 mmcblk1p13
179 14 8192 mmcblk1p14 boot
179 15 9216 mmcblk1p15 recovery
179 16 217088 mmcblk1p16 cdrom
179 17 512 mmcblk1p17 misc
179 18 512 mmcblk1p18 cid
179 19 4096 mmcblk1p19 kpanic
179 20 655360 mmcblk1p20 system
179 21 1048576 mmcblk1p21 cache
179 22 622592 mmcblk1p22 preinstall
179 23 1364992 mmcblk1p23 webtop
179 24 3203072 mmcblk1p24 userdata
179 25 8401792 mmcblk1p25 emstorage
179 26 128 mmcblk1p26
179 64 2048 mmcblk1boot1
179 32 2048 mmcblk1boot0

# /sbin/fdisk /dev/block/mmcblk1

Disk /dev/block/mmcblk1: 15.9 GB, 15938355200 bytes
16 heads, 16 sectors/track, 121600 cylinders, total 31129600 sectors
Units = sectors of 1 * 512 = 512 bytes

u (unit to sector )

p

Device Boot Start End Blocks Id System
block/mmcblk1p1 * 256 511 128 83 Linux
block/mmcblk1p2 1024 2047 512 83 Linux
block/mmcblk1p3 2048 3071 512 83 Linux
block/mmcblk1p4 3072 31105023 15550976 5 Extended
block/mmcblk1p5 4096 5119 512 83 Linux
block/mmcblk1p6 5120 5375 128 83 Linux
block/mmcblk1p7 6144 14335 4096 83 Linux
block/mmcblk1p8 14336 15359 512 83 Linux
block/mmcblk1p9 16384 18431 1024 83 Linux
block/mmcblk1p10 18432 22527 2048 83 Linux
block/mmcblk1p11 22528 23551 512 83 Linux
block/mmcblk1p12 23552 24575 512 83 Linux
block/mmcblk1p13 24576 32767 4096 83 Linux
block/mmcblk1p14 32768 49151 8192 83 Linux
block/mmcblk1p15 49152 67583 9216 83 Linux
block/mmcblk1p16 67584 501759 217088 83 Linux
block/mmcblk1p17 501760 502783 512 83 Linux
block/mmcblk1p18 502784 503807 512 83 Linux
block/mmcblk1p19 503808 511999 4096 83 Linux
block/mmcblk1p20 512000 1822719 655360 83 Linux
block/mmcblk1p21 1822720 3919871 1048576 83 Linux
block/mmcblk1p22 3919872 5165055 622592 83 Linux
block/mmcblk1p23 5165056 7895039 1364992 83 Linux
block/mmcblk1p24 7895040 14301183 3203072 83 Linux
block/mmcblk1p25 14301184 31104767 8401792 83 Linux
block/mmcblk1p26 31104768 31105023 128 83 Linux

2) i decide to make changes in (20-25)'s partition ( system to +3072M, cache to +1024M, preinstall to +1S, webtop to +1S, userdata to +3072M, emstorage to +8102M). But in order to make changes in (20-25)'s i had to delete 26's partitions but after creating new table starting and ending sector of 26's partitions remains the same . Also after i knew that safetrap 3.75 does not use preinstall, webtop for stock slot so i change them to +1S SECTORE.


d 26
d 25
d 24
d 23
d 22
d 21
d 20

3) after creating the new partitions. Table as follows

P

Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 * 256 511 128 83 Linux
/dev/block/mmcblk1p2 1024 2047 512 83 Linux
/dev/block/mmcblk1p3 2048 3071 512 83 Linux
/dev/block/mmcblk1p4 3072 31105023 15550976 5 Extended
/dev/block/mmcblk1p5 4096 5119 512 83 Linux
/dev/block/mmcblk1p6 5120 5375 128 83 Linux
/dev/block/mmcblk1p7 6144 14335 4096 83 Linux
/dev/block/mmcblk1p8 14336 15359 512 83 Linux
/dev/block/mmcblk1p9 16384 18431 1024 83 Linux
/dev/block/mmcblk1p10 18432 22527 2048 83 Linux
/dev/block/mmcblk1p11 22528 23551 512 83 Linux
/dev/block/mmcblk1p12 23552 24575 512 83 Linux
/dev/block/mmcblk1p13 24576 32767 4096 83 Linux
/dev/block/mmcblk1p14 32768 49151 8192 83 Linux
/dev/block/mmcblk1p15 49152 67583 9216 83 Linux
/dev/block/mmcblk1p16 67584 501759 217088 83 Linux
/dev/block/mmcblk1p17 501760 502783 512 83 Linux
/dev/block/mmcblk1p18 502784 503807 512 83 Linux
/dev/block/mmcblk1p19 503808 511999 4096 83 Linux
/dev/block/mmcblk1p20 512016 6512016 3000000+ 83 Linux
/dev/block/mmcblk1p21 6512033 8512033 1000000+ 83 Linux
/dev/block/mmcblk1p22 8512050 8512052 1+ 83 Linux
/dev/block/mmcblk1p23 8512069 8512071 1+ 83 Linux
/dev/block/mmcblk1p24 8512088 14512088 3000000+ 83 Linux
/dev/block/mmcblk1p25 14512105 31104751 8296323+ 83 Linux
/dev/block/mmcblk1p26 31104768 31105023 128 83 Linux

w (writing)

recreating table successful

q (quit)

# mke2fs -t ext3 /dev/block/mmcblk1p20

# mke2fs -t ext3 /dev/block/mmcblk1p21

# mke2fs -t ext3 /dev/block/mmcblk1p22

# mke2fs -t ext3 /dev/block/mmcblk1p23

# mke2fs -t ext3 /dev/block/mmcblk1p24

# mkdosfs /dev/block/mmcblk1p25

#mount /dev/block/mmcblk1p20 /system/

#mount /dev/block/mmcblk1p21 /cache/

#mount /dev/block/mmcblk1p24 /data/

#mount /dev/block/mmcblk1p25 /sdcard/

# mount /dev/block/mmcblk1p25 /ss/

# mount /dev/block/mmcblk1p25 /and-sec/

4) after that wiped cache, data , andriod secure, data, webtop, system.
5) restored backup of /system and /data /
6) reboot the system
7) after Motorola logo "M" got error



ap fastboot flash mode [boot failure]
0A.77
eMMC Info: Size 16g
to return to normal mode - first press power key to power down
device is LOCKED, Status Code:0

battery ok
ok to program
Connect USB
Data cable

Invalid CG OTV [CG: system]: Invalid SP Data
Invalid CG HAB [CG: system, status: 0X004E]
Invalid CG OTV [CG: system]

8) i had to use RSD LITE to flash VRZ_XT912_9.8.2O-72_VZW-16-5_1FF.xml to boot normally. :(

9) after booting i check for changes i made , f**k system returns back to default partition table.




QUESTIONS

1) where do i go wrong

2) does i have to also make change in "ebr" or "mbr" after changing partitions size

4) does it relate to preinstall and webtop which i left to +1S SECTOR

5)does lineageOS 13.0 need /osh (webtop partitions) because i was flashing saw it searching for /osh for mount

6)does to safe to left the preinstall and webtop to +1S SECTOR


I am not so good in redo partition table but what I done with standart tool RSD
Mine 912 Spyder
xt912 ebr - preinstall 600mb, userdata 3.0gb, system 600mb, emstorage 8gb, webtop 1.5gb
without CID flashed 910 Britan got
xt910 ebr - preinstall 9mb, userdata 3.8gb, system 775mb, emstorage 8gb, webtop 1.5gb
then replased EBR from CHINA(ASIA)
xt910 ebr china - preinstall 9mb, userdata 3.8gb, system 775mb, emstorage 9.2gb, webtop 128kb
+/- sizes
If you can see, yes partitions cannot be deleted in case of locked bootloader
but they can be 128kb in fact
can you try do EBR for me with next
preinstall 9mb, userdata 1.5gb, system 775mb, emstorage 11.5gb, webtop 128kb
Thanks in Advance
PS edition SS for unused partitions for 912 spyder where use webtop and preinstal
 
Last edited:
Apr 20, 2017
5
0
Hi,



You can't change the partition table. It's cryptographically signed and checked by the bootloader. After you have changed it, the verification failed and the system no longer boots. Flashing with RSD restores the stock (signed) partition table.

Best regards,
Michael

how about i mount unused partitions like preinstall & webtop and mount it to /system/app and other places inside /system where most space occupy and make changes in /etc/fstab, mtab, recovery.fstab, recovery.fstab.bak

will it make /system big, coz i did it and " df -h" commmand shows the same size of /system whereas webtop was mounted to /system/app.


Is there is another way to use used partition for /system , i really wants to flash gapp stock versison which is around 700mb

---------- Post added at 01:55 PM ---------- Previous post was at 01:37 PM ----------

Quarx managed to to repartition the Defy successfully despite the locked bootloader. Basically, the partition table was hard coded into the 2ndboot kernel and would load during the 2ndboot process. Maybe Quarx can help with repartitioning our RAZRs.


can u guide me how to use or post a link on how to use it, coz i have never used it before
 

rootdefyxt320

Senior Member
Oct 4, 2012
488
440
Sydney, NSW
@Aavi Hanif Balani

It requires changes to the kexec kernel and the ROM itself. Also it will require research on what partitions have signatures checked by mbm. There's no tutorial available on how to do this. It requires advanced programming knowledge to be able to do it. Also you can risk hard bricking your device if you accidentally touch the bootloader partitions.
 
Apr 20, 2017
5
0
@Aavi Hanif Balani

It requires changes to the kexec kernel and the ROM itself. Also it will require research on what partitions have signatures checked by mbm. There's no tutorial available on how to do this. It requires advanced programming knowledge to be able to do it. Also you can risk hard bricking your device if you accidentally touch the bootloader partitions.


is there is a way to increase /system size coz i really wants to flash gapp stock version which is around 700mb or any other way in lineageos 13.0 to putt gapp stock in it
 

KlovesXT910BR

Member
Nov 21, 2014
12
2
31
Guaçuí
Hi

Thanks for the focused people to give continuity to a 6-year-old smartphone
How many versions have already been used and how many roms have already been made.

Group, I have not yet succeeded in installing the official version on my xt910,
Even after the patch installation, fails.

Please put a more detailed tutorial on the installation via slot stock.

sorry for my English
 
N

notamemberanymore

Guest
lineage-13.0-20170603-nightly-spyder-signed
seems same problem Browser do not play some online video, should to install another one
BT before not connected to all devices, now dont on at all, I press turn on, it grey, but never tutrned on
 

eremitein

Senior Member
May 16, 2017
1,026
1,285
As I posted early
sadly... last build have perfect battery and RAM optimization, good speed. have a problems too, like artefacts around some online videos, short GUI animation freezes and not working bluetooth. may be someone fix major bugs? :fingers-crossed:
I'm started to work above lonely 13th LOS with my ability))

Thus, i backported kernel and modules from lineage-14.1-2017-06-10 to 13.0-2017-06-10. And?.. All working fine!!


P.S. Which reasons what developers not to fix BT in latest 13th release? Is this a good take down 6.0 project and reverse to "dirty" 7.1.2?
I thank all developers kindly, but that...
 

eremitein

Senior Member
May 16, 2017
1,026
1,285
hmmm... in 13th steel stayed one strange bug, wneh screen sometimes start jumping to right.

It's a dilemma:
13.0 (pros) + more stable, more free RAM, longest battery life
13.0 (cons) - some UI freezes (to 2-3 sec), periodically screen start jumping to right (quick fixed after lockscreen), not worked BT in last releases
14.1 (pros) + very fast UI, good support
14.1 (cons) - code is "raw", huge RAM and battery eating (with picoGapps using is a pain), video thumbnails with artefacts, images distorted while zooming
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 44
    LineageOS 13.0 (Marshmallow) {un,}official builds for the Droid Razr

    LineageOS is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.

    Code:
    #include <std_disclaimer.h>
    /*
     * Your warranty is now void.
     *
     * We are not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at any of us for messing up your device, we will laugh at you.
     * Collectively, and at the same time.
     */

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.

    Use these builds on your own risk!

    Builds:
    Current official builds:
    https://download.lineageos.org/spyder (Droid Razr)
    https://download.lineageos.org/umts_spyder (Razr)
    (When migrating from CM (official and unofficial) or Lineage unofficial, flash this first (manually mount /data in TWRP before flashing and unmount it afterwards) and then directly flash the new image without rebooting)

    Su addon for official builds: http://droid.cs.fau.de/lineage-13.0/addonsu/ (The official addon doesn't currently install on Omap4)

    Current unofficial manual builds:
    https://droid.cs.fau.de/lineage-13.0/

    Old official CM nightly builds and snapshots:
    https://droid.cs.fau.de/Official_CM_Builds/spyder/ (Droid Razr)
    https://droid.cs.fau.de/Official_CM_Builds/umts_spyder/ (Razr)

    Old manual builds:
    https://droid.cs.fau.de/cm-13.0/test/

    Changes (only device/family specific, CM base is always synced before build and contains more changes):
    • 2017-03-25:
      • Sync with LineageOS (March security level)
    • 2017-03-02:
      • Sync with LineageOS
    • 2017-02-19:
      • Fix 10 kernel security bugs
      • Add SGX Omap4-changes
      • Sync with LineageOS
    • 2017-02-10:
      • Sync with LineageOS (January security patchlevel)
    • 2017-02-01:
      • Sync with LineageOS
    • 2017-01-11:
      • Sync with LineageOS
      • Rebrand to lineage
    • 2016-01-21:
    • 2016-01-16:
      • Added SELinux rules to allow fsck on stock-partitions and fixboot to unmount safestrap-partition
      • Graphics glitches fixed
      • zRAM uses 2 compression streams now
    • 2016-01-14:
      • Implemented LiveDisplay/Color Calibration
    • 2016-01-13:
      • More fixes for switching CDMA devices to GSM
      • T-Mobile CZ APN corrected
    • 2016-01-11:
      • Preferred network type is now set earlier
      • Audio-routing through dock-audio (desk/car) added
      • Mouse-pointer (USB/Lapdock) fixed
    • 2016-01-08:
      • Camera no longer crops pictures in portrait mode
      • USB storage integration added
      • Initial root-mode setting fixed
      • Migrated from busybox to toybox, busybox is gone
      • Fixed duration of boostpulse in power HAL
    • 2016-01-06:
      • VZW data fixed
      • Reboot to recovery fixed
      • Wifi configuration updated
      • Widevine blobs updated (from sprout)
    • 2016-01-04:
      • Adoptable storage fixed
      • Many kernel patches to filesystem-, block- and mmc-layers
    • 2015-12-25:
      • Fixed internal storage for real. You need to manually remove /data/system/storage.xml and reboot when upgrading from previous builds. After that the internal storage will be the primary sd.
    • 2015-12-24:
      • Fixed crashes of com.android.phone on GSM/UMTS (XT894/XT912)
      • Configure internal storage like expected in M (can't be adopted, would kill safestrap)
      • Fixed GPS initialization failing most of the time
      • Run wifi calibration at an earlier stage
      • Workaround for VZW data: toggle airplane mode after boot once
      • Something which needed ffmpeg and imagemagick
    • 2015-12-18:
      • Switching of preferred network fixed
      • SELinux rules updated
      • SELinux is now enforcing
    • 2015-12-14:
      • Audio-routing fixed
    • 2015-12-11:
      • Capacitive buttons on {umts_,}spyder are no longer recognized as an external stylus, but as buttons
      • SELinux policies updated
      • Update widevine from mako
      • Added (very slow) emulation of idiv-operations not supported by Omap4 but required by newer blobs (gapps swype, widevine)
    • 2015-12-07:
      • First build for most devices

    What's working:
    • Phone (tested on Verizon and on GSM/UMTS in Europe)
    • Mobile data
    • WiFi
    • GPS
    • Camera
    • HDMI
    • Playback of DRM-protected content (using Widevine from sprout)
    • Reboot to recovery

    What's not working:
    Probably most everything else, including, but not limited to:
    • Data encryption (due to safestrap)

    Gapps:
    OpenGApps
    If you install Gapps after the ROM has been booted for the first time you either need to wipe data or manually delete /data/system/users/0/runtime-permissions.xml and reboot. Without this Gapps will crash constantly. This is due to the new permissions-system in M.

    Installation:

    GSM users with XT912:
    These versions (both unofficial and official) automatically switch to GSM/UMTS without installing additional patches.

    Source / Repositories:

    XDA:DevDB Information
    LineageOS 13.0 on Motorola Droid Razr, ROM for the Motorola Droid RAZR

    Contributors
    stargo, Hashcode, Dhacker29
    Source Code: https://github.com/LineageOS

    ROM OS Version: 6.0.x Marshmallow
    ROM Kernel: Linux 3.0.x
    Based On: LineageOS

    Version Information
    Status: Nightly
    Beta Release Date: 2017-03-25

    Created 2015-12-14
    Last Updated 2017-06-12
    21
    Hi,

    just a short status update: I'm currently waiting for a Droid Bionic I ordered to arrive, so I can see if CM 13 works there, too and fix the problems on that device, if there are any.
    As soon as that has happened, I'll flip the switch on the official CM13 nightlies for maserati, spyder, targa and umts_spyder. I will not leave one of them behind.

    Cheers,
    Michael
    16
    Hi,

    Starting tomorrow, the official nightlies will be CM13: http://review.cyanogenmod.org/#/c/129192/

    Cheers,
    Michael
    10
    Hi,

    After 2016-05-07 nightlies don't update automatically, only manually. When i press apply update it restarts and the android with a red triangle screen appears.

    Similar issue here. reboot to recovery is not rebooting to safestrap. its rebooting to fastboot or something like that.

    It's rebooting to stock recovery, my hack to get to safestrap was broken by recent changes to the reboot-code, this should hopefully be fixed by http://review.cyanogenmod.org/#/c/144796/ (still need to build and test that).

    Cheers,
    Michael
    10
    Hi,

    Just reporting the official nightly does not boot, keep black screen, I try it in safestrap by luck ;)
    I'm not a dev, but never, since lollipop, have system.dat in the zip, maybe that is the issue, and the zip tryies to format partitions as ext4.

    lineage-13.0-20170224-nightly-umts_spyder-signed.zip
    Bad rom for sure! Take it down! Just wasted several hours flashing back to a stock ROM, re-rooting, reinstalling safestrap and installing a different cyanogenmod ROM.

    Thanks for the reports.
    For some reason the LineageOS build-system is building block-based OTAs which do not work on the devices because of the locked BL and safestrap. I've requested to remove the build for now and have asked, why the official build-system produces different OTAs as to what happens if I build the images.

    EDIT: The LineageOS build-system does not support the hacks needed for our devices with locked bootloader and safestrap (due to their use of signed-builds which require block-based OTAs). I've removed the devices from the build-schedule: https://review.lineageos.org/#/c/163953/

    Cheers,
    Michael
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone