Question about wipe encryption in Google Nexus 6p - LineageOS Questions & Answers

We all know that there are two types of file encryption, one is called "wipe" and the other is "inplace". I have a project and I have to test how to use wipe to encrypt.
So I had a test about the ‘wipe’ encryption in pure lineageOS14.1 but unfortunately it failed. Here are my steps:*
1. Change the parameter "forcefdeorfbe" to "encryptable" in file fstab.angler then recompile the lineage source code to disable the forced encryption in Google Nexus 6P*
2. Get the root of the Nexus 6P (su root)*
3. Type the command in adb:
vdc cryptfs enablecrypto wipe password qwer
to use ‘wipe’ to delete all the files and then encrypt the system with the password set to ‘qwer’.*
Then my cell phone restarted without the encryption that I had expected, here is my log of that error:
02-05 06:22:00.701 370 3185 I Cryptfs : Enabling support for allow_discards in dmcrypt.*
02-05 06:22:00.701 370 3185 I Cryptfs : target_type = crypt*
02-05 06:22:00.701 370 3185 I Cryptfs : real_blk_name = /dev/block/platform/soc.0/f9824900.sdhci/by-name/userdata, extra_params = 1 allow_discards*
02-05 06:22:05.740 370 3185 E Cryptfs : Cannot load dm-crypt mapping table.*
02-05 06:22:05.741 370 3185 I Cryptfs : Making empty filesystem with command /system/bin/make_ext4fs -a /data -l 58688269824 /dev/block/dm-0*
02-05 06:22:05.811 370 3185 I make_ext4fs: SELinux: Loaded file_contexts contexts from /file_contexts.bin.*
02-05 06:22:05.812 370 3185 I make_ext4fs: Creating filesystem with parameters:*
02-05 06:22:05.812 370 3185 I make_ext4fs: Size: 58688266240*
02-05 06:22:05.812 370 3185 I make_ext4fs: Block size: 4096*
02-05 06:22:05.812 370 3185 I make_ext4fs: Blocks per group: 32768*
02-05 06:22:05.812 370 3185 I make_ext4fs: Inodes per group: 8192*
02-05 06:22:05.812 370 3185 I make_ext4fs: Inode size: 256*
02-05 06:22:05.812 370 3185 I make_ext4fs: Journal blocks: 32768*
02-05 06:22:05.812 370 3185 I make_ext4fs: Label:*
02-05 06:22:05.812 370 3185 I make_ext4fs: Blocks: 14328190*
02-05 06:22:05.812 370 3185 I make_ext4fs: Block groups: 438*
02-05 06:22:05.812 370 3185 I make_ext4fs: Reserved block group size: 1024*
02-05 06:22:05.826 370 3185 I make_ext4fs: Created filesystem with 11/3588096 inodes and 271280/14328190 blocks*
02-05 06:22:05.826 370 3185 I make_ext4fs: error: file_write: write: No space left on device*
02-05 06:22:05.830 370 3185 D Cryptfs : Successfully created filesystem on /dev/block/dm-0*
I read the function called cryptfs_enable_internal in the file cryptfs.c and there is a variable called "no_ui", it seems that this variable separated the process of encryption into two parts: the preparation before reboot and the real encryption after reboot. Although I don't think this variable should be used in this command when I want to use the ‘wipe’ command to wipe the cell phone and encrypt the cell phone. However, I still tried this:*
vdc cryptfs enablecrypto wipe password qwer noui*
The cell phone warned me that the data was corrupted and must have a factory reset.*
So now I can only use "inplace" to encryt my cell phone, could you please give me some ideas about:*
Is there anything wrong with my steps that makes the ‘wipe’ encryption never successful on my phone?

Related

Memory addresses/Memory Map for RAM, OneNAND, etc.

I am too dumb to find correct region... adresses...
But 2 ways...
1.
JTAG
Not solved yet...
2.
Via Command... + WinComm...
http://forum.xda-developers.com/showpost.php?p=12798324&postcount=3
Code:
[B]Memcpy[/B] address length
Example:
Memcpy 0x00000000 0x100
On U700 I can dump RAM on 0... but not on S8500...
Any suggestions?
Thanx.
Best Regards
Edit.:
Found in ELFs:
SDRAM_START_ADDR 0x20000000
SDRAM_END_ADDR 0x6CFFFFFF
See Screenshots. If Debug Level is Mid or High... but I don't understand, what my handset say to me...
On U700 in Debug Level Low possible to read something... on S8500 no success yet.
But maybe my fault.
Have you find the secret upload mode?
If you go to Fota in internals menu and Type something in there than bada crashes and you have got the upload mode (light bluascreen than only restart with key). but how to communicate with the device, i had not found any tool on the GSPN from samsung.
Try to memcpy RAM from 0x20000000 and 0x40000000 in S8500/8530.
Under the first one address you should find 128MB (0x8000000) of oneDRAM and under the second one 256MB (0x10000000) of SDRAM.
Rebellos said:
Try to memcpy RAM from 0x20000000 and 0x40000000 in S8500/8530.
Under the first one address you should find 128MB (0x8000000) of oneDRAM and under the second one 256MB (0x10000000) of SDRAM.
Click to expand...
Click to collapse
A small doubt:
http://dev.odroid.com/wiki/odroid-t/pds/FrontPage/s_blockdiagram.jpg
Does LPDDR1 corresponds to SDRAM?
jake792 said:
A small doubt:
http://dev.odroid.com/wiki/odroid-t/pds/FrontPage/s_blockdiagram.jpg
Does LPDDR1 corresponds to SDRAM?
Click to expand...
Click to collapse
SDRAM is kind of RAM, widely used in computers nowadays
http://en.wikipedia.org/wiki/Synchronous_dynamic_random_access_memory
LPDDR is subtype of SDRAM designed for mobile phones, that is Low-Power Ram.
I'm not sure if thats LPDDR1 or LPDDR2 in Waves.
Thanx.Also since total amount of ram is 384mb.. lesser availibility of free ram would be there.
Bump...
I have not managed problem to dump memory...
Maybe in RAM it is possible to catch some uncompressed data...
Thanx in advance.
Best Regards
Blub...
Problem 1 unsolved to read from handset via Command in bada:
Code:
[B]Memcpy[/B] address length
Memory Map...Partition Table etc. would be interesting for me in 2013...
Maybe start with Partition Table...
I need more space for apps_compressed.bin in bada 2 XXLA1...
Other ideas decrease for instance OSP partition... for test...
I have now access to edit direct in Binary Bootloader... aka boot_loader.mbn.
My skills to understand source or ELF files are very very EXTREME limited.
Maybe S8500 and S8530 have easy "partition Block" like partition.bin from S8600...
Thanx for reading.
Best Regards
Edit 1.
In ELF it is easier to find...
Code:
FLASH_MODEM_START_ADDR 0x00400000
FLASH_MODEM_END_ADDR 0x01100000
FLASH_CODE_START_ADDR 0x01100000
FLASH_CODE_END_ADDR (0x03100000+FLASH_FOTA_HOLE_RESERVED_SIZE)
FLASH_CODE_COMPRESS_START_OFFSET 0x800
Hmm.
Code:
01100000
I could check Little Endian... in boot_loader.mbn
XPKG5 need other addresses for RC1 and RC2
Also MBUKI...
I need this to identify addresses in Boot...
Best Regards
http://forum.xda-developers.com/showpost.php?p=20188325&postcount=369
Code:
// firmware qmd ver start addr max length
{ S8500v12 | BADA_APPS, 0x03050000, 0x01100000, 0x03500000 },
{ S8500v12 | BADA_RSRC1, 0x04070000, 0x04800000, 0x06F00000 },
{ S8500v12 | BADA_RSRCS, 0x04070000, 0x0B700000, 0x00F00000 },
{ S8530v12 | BADA_APPS, 0x03050000, 0x01300000, 0x03500000 },
{ S8530v12 | BADA_RSRC1, 0x04070000, 0x04A00000, 0x05000000 },
{ S8530v12 | BADA_RSRCS, 0x04070000, 0x09A00000, 0x00F00000 },
{ S8500v20 | BADA_APPS, 0x04020000, 0x01100000, 0x02000000 },
{ S8500v20 | BADA_RSRC1, 0x05020000, 0x05D00000, 0x05A00000 },
{ S8500v20 | BADA_RSRCS, 0x05020000, 0x03A00000, 0x02300000 },
{ S8530v20 | BADA_APPS, 0x04020000, 0x01300000, 0x02000000 },
{ S8530v20 | BADA_RSRC1, 0x05020000, 0x03600000, 0x04100000 },
{ S8530v20 | BADA_RSRCS, 0x05020000, 0x07700000, 0x01E00000 },
{ S8600 | BADA_APPS, 0x04020000, 0x08000000, 0x02000000 },
{ S8600 | BADA_RSRC1, 0x05020000, 0x0A200000, 0x03200000 },
{ S8600 | BADA_RSRCS, 0x05020000, 0x0D400000, 0x02800000 },
{ S7250D | BADA_APPS, 0x04020000, 0x00E00000, 0x01F00000 },
{ S7250D | BADA_RSRC1, 0x05020000, 0x02F00000, 0x01E00000 },
{ S7250D | BADA_RSRCS, 0x05020000, 0x04D00000, 0x01C00000 },
Perfect overview, very helpfull.
Big thanx b.kubica :good:
Best Regards
Memo to me...
Code:
-----------------------------------------------------------
Samsung Secondary Bootloader (SBL) v3.0
Copyright (C) Samsung Electronics Co..
Build On: Jun 8 2011 21:44:47
-----------------------------------------------------------
Re_partition: magic code(0x0)
[PAM: ] ++FSR_PAM_Init
[PAM: ] OneNAND physical base address : 0xb0000000
[PAM: ] OneNAND virtual base address : 0xb0000000
[PAM: ] OneNAND nMID=0xec : nDID=0x50
[PAM: ] --FSR_PAM_Init
fsr_bml_load_partition: pi->[B]nNumOfPartEntry = 7[/B]
partitions loading success
board partition information update.. source: 0x0
.Done.
read 1 units.
==== PARTITION INFORMATION ====
ID : *unknown id* (0x9)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 0
NO_UNITS : 1
===============================
ID : *unknown id* (0x0)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1
NO_UNITS : 7
===============================
ID : *unknown id* (0x1)
ATTR : RW SLC (0x1001)
FIRST_UNIT : 8
NO_UNITS : 796
===============================
ID : *unknown id* (0x14)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 804
NO_UNITS : 716
===============================
ID : *unknown id* (0x15)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1520
NO_UNITS : 372
===============================
ID : *unknown id* (0x17)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1892
NO_UNITS : 56
===============================
ID : *unknown id* (0x18)
ATTR : RW SLC (0x1001)
FIRST_UNIT : 1948
NO_UNITS : 56
===============================
It is possible to "identify" partitons on OneNAND via SBL from I9000 etc...
pi->nNumOfPartEntry = 7
bada Bootloader shows something like this:
Code:
[BM : ] FSR_BML_GetFullPartI() is completed
[BM : ] stPartI.nNumOfPartEntry : 7
[BM : ] 1th PartEntrt(nAttr:0x1002)(nID:0x0)
[BM : ] [1th] pPEntry->n1stVun : 1
[BM : ] [1th] [B]pPEntry->nNumOfUnits : 7[/B]
[BM : ] [1th] pPEntry->nLoadAddr : 0x0
+-------------------------------+
| Bootloader Shadowing FINISHED |
+-------------------------------+
Launch Image at 0x42480000
Catched via UART cable... + JTAG...
Will play little bit with
I9000_s1_odin_20100512.pit
and
I9000_s1_odin_20100803.pit
Tasks for 2014...
Learning more about Partitions...
Best Regards
Edit 1.
Short modified I9000_s1_odin_20100512.pit...
Code:
fsr_bml_load_partition: pi->nNumOfPartEntry = 12
partitions loading success
board partition information update.. source: 0x0
.Done.
read 1 units.
==== PARTITION INFORMATION ====
ID : IBL+PBL (0x0)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 0
NO_UNITS : 1
===============================
ID : PIT (0x1)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1
NO_UNITS : 1
===============================
ID : EF[COLOR="Red"]1[/COLOR] (0x14)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 2
NO_UNITS : 40
===============================
ID : SB[COLOR="Red"]1[/COLOR] (0x3)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 42
NO_UNITS : 5
===============================
ID : SBL[COLOR="Red"]1[/COLOR] (0x4)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 47
NO_UNITS : 5
===============================
ID : PARA[COLOR="Red"]1[/COLOR] (0x15)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 52
NO_UNITS : 20
===============================
ID : KERNE[COLOR="Red"]1[/COLOR] (0x6)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 72
NO_UNITS : 30
===============================
ID : RECOVER[COLOR="Red"]1[/COLOR] (0x7)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 102
NO_UNITS : 30
===============================
ID : FACTORYF[COLOR="Red"]1[/COLOR] (0x16)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 132
NO_UNITS : 1146
===============================
ID : DBDATAF[COLOR="Red"]1[/COLOR] (0x17)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1278
NO_UNITS : 536
===============================
ID : CACH[COLOR="Red"]1[/COLOR] (0x18)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1814
NO_UNITS : 140
===============================
ID : MODE[COLOR="Red"]1[/COLOR] (0xb)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1954
NO_UNITS : 50
===============================
RO I think should mean read only
RW = read/write
SLC and STL
NO_UNITS = Number of ... maybe... not sure
STL = Section Translation Layer (Google for BML FSR and BML STL by Samsung)
unit = 256kB or so
No idea what's SLC, "Single Level Cell" doesn't make much sense here
Probably answer is in there - https://github.com/supercurio/samsung_fsr
About SLC, etc, I wrote something about this here:
http://forum.xda-developers.com/showpost.php?p=33359041&postcount=6
I think the relevant info is in the links...
http://forum.xda-developers.com/showthread.php?t=816449
Found this usefull thread about PIT...
2014 I will play little bit Partition file PIT.
Ideas.
1.
Modifying PIT to 1 partition over the whole size... in my case 512 MB...
To write maxbe Fulldumps...
If this is nonsense during few Security limitations...
2.
Increasing first Partition to write 4 MB boot.bin... to solve this Security thingie...
http://forum.xda-developers.com/showthread.php?t=1250270
So maybe then bada Boot restoreable with SBL...
Summary...
Units seems Blocks... seems 256 KB size...
So I need instead 1 Unit... 16 for Partition 1...
Later more, I will try to "convert" this info from here now:
Code:
==== PARTITION INFORMATION ====
ID : *unknown id* (0x9)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 0
NO_UNITS : 1
Taken from here:
http://forum.xda-developers.com/showpost.php?p=49033160&postcount=11
Best Regards
Edit 1.
So bada Partition table/info looks like this... S8500..
Little bit explained... later more
Code:
==========================
ID
ATTR
FIRST_UNIT 0
NO_UNITS 1
00000000-00040000
[B]256 KB[/B]
==========================
ID
ATTR
FIRST_UNIT 1
NO_UNITS 7
00040000-001C0000
1792 KB [B]2 MB[/B]
1835008 Byte
==========================
ID
ATTR
FIRST_UNIT 8
NO_UNITS 796
203776 KB [B]203 MB[/B]
208666624 Byte
==========================
ID
ATTR
FIRST_UNIT 804
NO_UNITS 716
183296 KB [B]183 MB[/B]
187695104 Byte
==========================
ID
ATTR
FIRST_UNIT 1520
NO_UNITS 372
95232 KB [B]95 MB[/B]
97517568 Byte
==========================
ID
ATTR
FIRST_UNIT 1892
NO_UNITS 56
14336 KB [B]14 MB[/B]
14680064 Byte
==========================
ID
ATTR
FIRST_UNIT 1948
NO_UNITS 56
14336 KB [B]14 MB[/B]
14680064 Byte
===========================
Code:
<6>Scanning device for bad blocks
<7>onenand_bbt_wait: ecc 0xaaaa ctrl 0x0400 intr 0x8080 addr1 0x92 addr8 0x0
<6>OneNAND eraseblock 146 is an initial bad block
<7>onenand_bbt_wait: ecc 0xaaaa ctrl 0x0400 intr 0x8080 addr1 0x5cc addr8 0x0
<6>OneNAND eraseblock 1484 is an initial bad block
<6>OneNAND eraseblock 2047 is an initial bad block
<5>Creating 11 MTD partitions on "(null)":
<5>0x00001f000000-0x00001f500000 : "nv_data"
<5>0x000000400000-0x000009800000 : "fw_block"
<5>0x000000400000-0x000000600000 : "dbl"
<5>0x000000600000-0x000001380000 : "amss"
<5>0x000001300000-0x000003600000 : "apps"
<5>0x000003600000-0x000007700000 : "rsrc1"
<5>0x000007700000-0x000009500000 : "csc"
<5>0x000009500000-0x000009800000 : "fota"
<5>0x000009800000-0x000018f00000 : "stl1"
<5>0x000018f00000-0x00001ec00000 : "stl2"
<5>0x00001ec00000-0x00001f000000 : "secdata"
S8530 UART Log... with latest Android from volk204...
Later I will compare S8500...
Best Regards
S8530 SD-Version ZenDroKat
/proc/mtd
Code:
dev: size erasesize name
mtd0: 00500000 00040000 "nv_data"
mtd1: 09400000 00040000 "fw_block"
mtd2: 00200000 00040000 "dbl"
mtd3: 00d80000 00040000 "amss"
mtd4: 02300000 00040000 "apps"
mtd5: 04100000 00040000 "rsrc1"
mtd6: 01e00000 00040000 "csc"
mtd7: 00300000 00040000 "fota"
mtd8: 0f700000 00040000 "stl1"
mtd9: 05d00000 00040000 "stl2"
mtd10: 00400000 00040000 "secdata"
/proc/partitions
Code:
major minor #blocks name
31 0 5120 mtdblock0
31 1 151552 mtdblock1
31 2 2048 mtdblock2
31 3 13824 mtdblock3
31 4 35840 mtdblock4
31 5 66560 mtdblock5
31 6 30720 mtdblock6
31 7 3072 mtdblock7
31 8 252928 mtdblock8
31 9 95232 mtdblock9
31 10 4096 mtdblock10
253 0 488284 zram0
179 0 1912832 mmcblk0
179 1 602112 mmcblk0p1
179 2 401408 mmcblk0p2
179 3 909311 mmcblk0p3
179 16 1024 mmcblk0boot1
179 8 1024 mmcblk0boot0
179 24 15632384 mmcblk1
179 25 11330560 mmcblk1p1
179 26 18432 mmcblk1p2
179 27 563200 mmcblk1p3
179 28 3719168 mmcblk1p4
http://download.tizen.org/releases/daily/1.0/sbs/
Oh, about PIT...
Check content of file:
lutil.tar.gz
Attached...
Best Regards
Edit 1.
Oh, maybe this helps me to unterstand more...
PIT/XML files
=============
You can convert a PIT file to XML format as follows:
./pit2xml pit/SLP_ALL_Ver04.pit SLP_ALL_Ver04.xml
and back again:
./xml2pit SLP_ALL_Ver04.xml SLP_ALL_Ver04.pit
The relevant data in the file should remain the same.
The XML for SLP_ALL_Ver04.pit looks like this:
Click to expand...
Click to collapse
Edit 2.
According to this example:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<root>
<partition Name="ipl+recovery" FileName="ipl-recovery.bin" DeltaName="" BlockSize="256" BlockLength="2"/>
<partition Name="pit" FileName="pit" DeltaName="" ID="1" BlockSize="256" BlockLength="2"/>
<partition Name="csa" FileName="csa" DeltaName="" ID="2" BlockSize="256" BlockLength="32"/>
<partition Name="u-boot" FileName="u-boot-whdr.bin" DeltaName="" ID="3" BlockSize="256" BlockLength="4"/>
<partition Name="u-boot_bak" FileName="u-boot-whdr.bin" DeltaName="" ID="4" BlockSize="256" BlockLength="4"/>
<partition Name="params" FileName="params" DeltaName="" ID="5" BlockSize="256" BlockLength="4"/>
<partition Name="config" FileName="config" DeltaName="" ID="6" BlockSize="256" BlockLength="8"/>
<partition Name="kernel" FileName="uImage" DeltaName="" ID="7" BlockSize="256" BlockLength="28"/>
<partition Name="kernel_bak" FileName="uImage" DeltaName="" ID="8" BlockSize="256" BlockLength="28"/>
<partition Name="log" FileName="log" DeltaName="" ID="9" BlockSize="256" BlockLength="5"/>
<partition Name="modem" FileName="modem.img" DeltaName="" BinType="1" ID="10" BlockSize="256" BlockLength="64"/>
<partition Name="qboot" FileName="qboot" DeltaName="" ID="11" BlockSize="256" BlockLength="240"/>
<partition Name="UBI" FileName="ubi.img" DeltaName="" ID="12" Attribute="1" BlockSize="256" BlockLength="1627"/>
<partition Name="movinand" FileName="movinand.bin" DeltaName="" DevType="2" Attribute="1"/>
<partition Name="csc" FileName="rfs_part4.csc" DeltaName="" DevType="2" ID="4" Attribute="1"/>
</root>
I will try to "convert":
Code:
I9000_s1_odin_20100512.pit
I9000_s1_odin_20100803.pit
First by hand and my low brain...
Code:
===============================
ID : CACHE (0x18)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1814
NO_UNITS : [B]130[/B]
===============================
ID : MODEM (0xb)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1944
NO_UNITS : [B]60[/B]
===============================
Aha...
increased reserved space for AMSS... in:
I9000_s1_odin_20100512.pit
Need this for stupid tests... to start with patched SBL...
Best Regards
didn't they already understood and documented every possible part of pit file format?
didn't they already understood
Click to expand...
Click to collapse
Thanx for Link, never seen before...
No idea yet, how easy it is to use... for me.
At the moment for me it is easier to use my little brain + WinHex + example from Samsung Tizen team... in XML Format.
And I am on the older Stuff like I9000 PIT... OneNAND... not eMMC/moviNAND...
No Encryption...
Best Regards
Edit 1.
Short tested this:
http://jenkins.casual-dev.com/job/Analyze PIT File/build
Used this PIT from I9000...
I9000_s1_odin_20100512.pit
Code:
-----BEGIN PIT ANALYSIS-----
PIT Name: TA
PIT Parameter: àú
PIT Parameter: ØC
Entry Count: 13
File Type: 
--- Entry #0 ---
ID: 0 Partition Name: IBL+PBL param: S param: e param: r param: v param: e param: r param: \ param: 9 param: 0 param: \ param: T param: o
Filename: boot.bin param: i param: n param: n param: ; param: C param: : param: \ param: P param: r param: o param: g
Block Size: 1 (512B)
Block range: 256 - 256 (hex 0x100 - 0x100)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:6684783 Size: 2097268 FOTA: param: a param: m param: param: F param: i param: l param: e param: s param: \ param: E param: S param: T param: s param: o param: f
The IBL+PBL param: S param: e param: r param: v param: e param: r param: \ param: 9 param: 0 param: \ param: T param: o partition, identified as partition number 0, is 512B in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as boot.bin param: i param: n param: n param: ; param: C param: : param: \ param: P param: r param: o param: g.The partition carries a filesize of 2097268 and an offset of 6684783.
--- Entry #1 ---
ID: 1 Partition Name: PIT
Filename: param: ries.pit
Block Size: 1 (512B)
Block range: 256 - 256 (hex 0x100 - 0x100)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The PIT partition, identified as partition number 1, is 512B in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as param: ries.pit.
--- Entry #2 ---
ID: 20 Partition Name: EFS
Filename: efs.rfs
Block Size: 40 (20.5kB)
Block range: 256 - 295 (hex 0x100 - 0x127)
FilesystemType: 0 PartType: 2 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The EFS partition, identified as partition number 20, is 20.5kB in size and carries a raw format. This partition resides on the Bootloader section of the AP undocumented. It identifies itself to Odin as efs.rfs.
--- Entry #3 ---
ID: 3 Partition Name: SBL
Filename: sbl.bin
Block Size: 5 (2.6kB)
Block range: 256 - 260 (hex 0x100 - 0x104)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The SBL partition, identified as partition number 3, is 2.6kB in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as sbl.bin.
--- Entry #4 ---
ID: 4 Partition Name: SBL2
Filename: sbl.bin
Block Size: 5 (2.6kB)
Block range: 256 - 260 (hex 0x100 - 0x104)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The SBL2 partition, identified as partition number 4, is 2.6kB in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as sbl.bin.
--- Entry #5 ---
ID: 21 Partition Name: PARAM
Filename: param.lfs
Block Size: 20 (10.2kB)
Block range: 256 - 275 (hex 0x100 - 0x113)
FilesystemType: 0 PartType: 2 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The PARAM partition, identified as partition number 21, is 10.2kB in size and carries a raw format. This partition resides on the Bootloader section of the AP undocumented. It identifies itself to Odin as param.lfs.
--- Entry #6 ---
ID: 6 Partition Name: KERNEL
Filename: zImage
Block Size: 30 (15.4kB)
Block range: 256 - 285 (hex 0x100 - 0x11d)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The KERNEL partition, identified as partition number 6, is 15.4kB in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as zImage.
--- Entry #7 ---
ID: 7 Partition Name: RECOVERY
Filename: zImage
Block Size: 30 (15.4kB)
Block range: 256 - 285 (hex 0x100 - 0x11d)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The RECOVERY partition, identified as partition number 7, is 15.4kB in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as zImage.
--- Entry #8 ---
ID: 22 Partition Name: FACTORYFS
Filename: factoryfs.rfs
Block Size: 1146 (586.8kB)
Block range: 256 - 1401 (hex 0x100 - 0x579)
FilesystemType: 0 PartType: 2 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The FACTORYFS partition, identified as partition number 22, is 586.8kB in size and carries a raw format. This partition resides on the Bootloader section of the AP undocumented. It identifies itself to Odin as factoryfs.rfs.
--- Entry #9 ---
ID: 23 Partition Name: DBDATAFS
Filename: dbdata.rfs
Block Size: 536 (274.4kB)
Block range: 256 - 791 (hex 0x100 - 0x317)
FilesystemType: 0 PartType: 2 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The DBDATAFS partition, identified as partition number 23, is 274.4kB in size and carries a raw format. This partition resides on the Bootloader section of the AP undocumented. It identifies itself to Odin as dbdata.rfs.
--- Entry #10 ---
ID: 24 Partition Name: CACHE
Filename: cache.rfs
Block Size: 140 (71.7kB)
Block range: 256 - 395 (hex 0x100 - 0x18b)
FilesystemType: 0 PartType: 2 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The CACHE partition, identified as partition number 24, is 71.7kB in size and carries a raw format. This partition resides on the Bootloader section of the AP undocumented. It identifies itself to Odin as cache.rfs.
--- Entry #11 ---
ID: 11 Partition Name: MODEM
Filename: modem.bin
Block Size: 50 (25.6kB)
Block range: 256 - 305 (hex 0x100 - 0x131)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The MODEM partition, identified as partition number 11, is 25.6kB in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as modem.bin.
--- Entry #12 ---
[B]ID: 11 Partition Name:
Filename:
Block Size: 0 (0B)
Block range: 0 - -1 (hex 0x0 - 0xffffffff)
FilesystemType: 0 PartType: 0 DevType: 1 BinType: 1
Offset:0 Size: 0 FOTA:
The partition, identified as partition number 11, is 0B in size and carries a raw format. This partition resides on the Raw section of the CP NAND.
[/B]
-----END PIT ANALYSIS-----
Helpfull to understand maybe last few Bytes of PIT...
Anyway... output not 100 % correct, because Blocksize is 256 KB, instead 512 Byte...
Its the difference between eMCC/moviNAND versus OneNAND...

please help in call audio

Is anyone having this problem whilst building and testing roms , Can someone review this cat log and suggest a fix its for in call volume this is the problem:
Code:
02-05 18:10:40.748 8670 8670 W System : ClassLoader referenced unknown path: /system/priv-app/Dialer/lib/arm
02-05 18:10:40.759 7021 7021 I InCall : CallList - onUpdate - [Call_2, ACTIVE, [Capabilities: CAPABILITY_HOLD CAPABILITY_SUPPORT_HOLD CAPABILITY_MUTE CAPABILITY_CANNOT_DOWNGRADE_VIDEO_TO_AUDIO], [Properties:], children:[], parent:null, conferenceable:[], videoState:Audio Only, mSessionModificationState:0, VideoSettingsCameraDir:-1), mIsActivSub:false]
02-05 18:10:40.759 7021 7021 I InCall : InCallPresenter - Phone switching state: INCALL -> INCALL
02-05 18:10:40.761 7021 7021 E QtiImsExtUtils: getImsPhoneId failed. Exception = org.codeaurora.ims.QtiImsException: ImsService is not running
02-05 18:10:40.761 7021 7021 E QtiImsExtUtils: getConfigForPhoneId phoneId is invalid
02-05 18:10:40.761 7021 7021 E QtiImsExtUtils: isCarrierConfigEnabled bundle is null
02-05 18:10:40.761 7021 7021 E QtiImsExtUtils: getImsPhoneId failed. Exception = org.codeaurora.ims.QtiImsException: ImsService is not running
02-05 18:10:40.761 7021 7021 E QtiImsExtUtils: getConfigForPhoneId phoneId is invalid
02-05 18:10:40.761 7021 7021 E QtiImsExtUtils: isCarrierConfigEnabled bundle is null
02-05 18:10:40.789 531 531 I hash_map_utils: key: 'volume_boost' value: ''
02-05 18:10:40.789 531 3072 I hash_map_utils: key: 'volume_boost' value: ''
02-05 18:10:40.792 7021 7021 E QtiImsExtUtils: getImsPhoneId failed. Exception = org.codeaurora.ims.QtiImsException: ImsService is not running
02-05 18:10:40.792 7021 7021 E QtiImsExtUtils: getConfigForPhoneId phoneId is invalid
02-05 18:10:40.792 7021 7021 E QtiImsExtUtils: isCarrierConfigEnabled bundle is null
02-05 18:10:40.792 7021 7021 E QtiImsExtUtils: getImsPhoneId failed. Exception = org.codeaurora.ims.QtiImsException: ImsService is not running
02-05 18:10:40.792 7021 7021 E QtiImsExtUtils: getConfigForPhoneId phoneId is invalid
02-05 18:10:40.792 7021 7021 E QtiImsExtUtils: isCarrierConfigEnabled bundle is null

ccache not working

I recently started with building LineageOS. However, I see that ccache isn't working for me for some reason. The ccache directory size is just 56MB. The build takes the same amount of time ~5hr(on my laptop). I've even set the cache size as 70GB. However, my out directory is 55.7GB. What am I doing wrong?
Probable relevant log:
Code:
[ 99% 40898/40912] Target cache fs ima...age/out/target/product/kenzo/cache.img
BuildImage: in_dir = /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache, out_file = /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache.img
fs type is not ext4
Running: mkuserimg.sh -s /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache.img ext4 cache 268435456 -D /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system -L cache /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin
make_ext4fs -s -T -1 -S /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin -L cache -l 268435456 -a cache /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache.img /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label: cache
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
Running ['mkuserimg.sh', '-s', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache.img', 'ext4', 'cache', '268435456', '-D', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system', '-L', 'cache', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin'] command, exit code = 0
/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache.img maxsize=273985536 blocksize=135168 total=6398184 reserve=2838528
[ 99% 40904/40912] Construct recovery from boot
failed to reconstruct target deflate chunk 1 [(null)]; treating as normal
chunk 0: type 0 start 0 len 9041930
chunk 1: type 2 start 9041930 len 4148992
chunk 2: type 0 start 10711741 len 1347
Construct patches for 3 chunks...
patch 0 is 205 bytes (of 9041930)
patch 1 is 5082118 bytes (of 1669811)
patch 2 is 152 bytes (of 1347)
chunk 0: normal ( 0, 9041930) 205
chunk 1: deflate ( 9041930, 7662273) 5082118 (null)
chunk 2: normal ( 16704203, 1333) 152
[ 99% 40904/40912] Target userdata fs .../out/target/product/kenzo/userdata.img
BuildImage: in_dir = /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/data, out_file = /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/userdata.img
fs type is not ext4
Running: mkuserimg.sh -s /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/data /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/userdata.img ext4 data 26838785024 -D /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system -L data /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin
make_ext4fs -s -T -1 -S /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin -L data -l 26838785024 -a data /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/userdata.img /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/data /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system
Creating filesystem with parameters:
Size: 26838781952
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label: data
Blocks: 6552437
Block groups: 200
Reserved block group size: 1024
Created filesystem with 38/1638400 inodes and 150074/6552437 blocks
Running ['mkuserimg.sh', '-s', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/data', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/userdata.img', 'ext4', 'data', '26838785024', '-D', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system', '-L', 'data', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin'] command, exit code = 0
/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/userdata.img maxsize=27400671936 blocksize=135168 total=155432808 reserve=276824064
[ 99% 40908/40912] Target system fs im...G/systemimage_intermediates/system.img
BuildImage: in_dir = /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system, out_file = /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/obj/PACKAGING/systemimage_intermediates/system.img
fs type is not ext4
Running: mkuserimg.sh -s /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/obj/PACKAGING/systemimage_intermediates/system.img ext4 system 2684354560 -D /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system -L system /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin
make_ext4fs -s -T -1 -S /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin -L system -l 2684354560 -a system /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/obj/PACKAGING/systemimage_intermediates/system.img /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system
Creating filesystem with parameters:
Size: 2684354560
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 10240
Label: system
Blocks: 655360
Block groups: 20
Reserved block group size: 159
Created filesystem with 3340/163840 inodes and 292571/655360 blocks
Running ['mkuserimg.sh', '-s', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/obj/PACKAGING/systemimage_intermediates/system.img', 'ext4', 'system', '2684354560', '-D', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system', '-L', 'system', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin'] command, exit code = 0
[ 99% 40909/40912] Install system fs i...ge/out/target/product/kenzo/system.img
/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system.img+/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p maxsize=2740531200 blocksize=135168 total=1160426351 reserve=27709440
[ 99% 40910/40912] Package target file...eage_kenzo-target_files-d4b338b746.zip
using prebuilt recovery.img from BOOTABLE_IMAGES...
using prebuilt boot.img from BOOTABLE_IMAGES...
putting script in bin/install-recovery.sh
running: unzip -o -q /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/obj/PACKAGING/target_files_intermediates/lineage_kenzo-target_files-d4b338b746.zip -d /tmp/targetfiles-cmkmqI
++++ boot ++++
using prebuilt boot.img from BOOTABLE_IMAGES...
++++ recovery ++++
using prebuilt recovery.img from BOOTABLE_IMAGES...
++++ recovery (two-step image) ++++
building image from target_files RECOVERY...
running: mkbootfs -f /tmp/targetfiles-cmkmqI/META/recovery_filesystem_config.txt /tmp/targetfiles-cmkmqI/RECOVERY/RAMDISK
running: minigzip
running: /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/bin/mkbootimg --kernel /tmp/targetfiles-cmkmqI/RECOVERY/kernel --cmdline androidboot.hardware=qcom ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 ramoops_memreserve=4M buildvariant=userdebug --base 0x80000000 --pagesize 2048 --ramdisk_offset 0x01000000 --tags_offset 0x00000100 --os_version 7.1.2 --os_patch_level 2017-08-05 --ramdisk /tmp/tmpFzhpAo --output /tmp/tmpBQOvrL
++++ system ++++
creating system.img...
BuildImage: in_dir = /tmp/targetfiles-cmkmqI/system, out_file = /tmp/system-d7Wo62.img
fs type is not ext4
Running: mkuserimg.sh -s /tmp/targetfiles-cmkmqI/system /tmp/system-d7Wo62.img ext4 system 2684354560 -T 1230748200 -C /tmp/targetfiles-cmkmqI/META/filesystem_config.txt -B /tmp/system-blocklist-OsEPwM.map -L system /tmp/targetfiles-cmkmqI/META/file_contexts.bin
make_ext4fs -s -T 1230748200 -S /tmp/targetfiles-cmkmqI/META/file_contexts.bin -C /tmp/targetfiles-cmkmqI/META/filesystem_config.txt -B /tmp/system-blocklist-OsEPwM.map -L system -l 2684354560 -a system /tmp/system-d7Wo62.img /tmp/targetfiles-cmkmqI/system
loaded 3332 fs_config entries
Creating filesystem with parameters:
Size: 2684354560
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 10240
Label: system
Blocks: 655360
Block groups: 20
Reserved block group size: 159
Created filesystem with 3342/163840 inodes and 292951/655360 blocks
Running ['mkuserimg.sh', '-s', '/tmp/targetfiles-cmkmqI/system', '/tmp/system-d7Wo62.img', 'ext4', 'system', '2684354560', '-T', '1230748200', '-C', '/tmp/targetfiles-cmkmqI/META/filesystem_config.txt', '-B', '/tmp/system-blocklist-OsEPwM.map', '-L', 'system', '/tmp/targetfiles-cmkmqI/META/file_contexts.bin'] command, exit code = 0
++++ userdata ++++
creating userdata.img...
BuildImage: in_dir = /tmp/tmpbdwQbq/data, out_file = /tmp/tmpucca6X
fs type is not ext4
Running: mkf2fsuserimg.sh /tmp/tmpucca6X 26838785024
in mkf2fsuserimg.sh PATH=/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/bin/:/usr/lib/jvm/java-8-openjdk/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/development/scripts:/run/media/vinayak/6FA49F144DC575A7/android/lineage/prebuilts/devtools/tools:/run/media/vinayak/6FA49F144DC575A7/android/lineage/external/selinux/prebuilts/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/prebuilts/android-emulator/linux-x86_64:/home/vinayak/venv/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
make_f2fs -l 26838785024 /tmp/tmpucca6X
Info: zone aligned segment0 blkaddr: 512
Info: Overprovision ratio = 1.250%
Info: Overprovision segments = 323 (GC reserved = 167)
Running ['mkf2fsuserimg.sh', '/tmp/tmpucca6X', '26838785024'] command, exit code = 0
userdata size (14) is 0.00% of limit (26838785024)
++++ extrauserdata ++++
++++ cache ++++
creating cache.img...
BuildImage: in_dir = /tmp/tmpQp6j5q/cache, out_file = /tmp/tmpPUYQ9G
fs type is not ext4
Running: mkf2fsuserimg.sh /tmp/tmpPUYQ9G 268435456
in mkf2fsuserimg.sh PATH=/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/bin/:/usr/lib/jvm/java-8-openjdk/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/development/scripts:/run/media/vinayak/6FA49F144DC575A7/android/lineage/prebuilts/devtools/tools:/run/media/vinayak/6FA49F144DC575A7/android/lineage/external/selinux/prebuilts/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/prebuilts/android-emulator/linux-x86_64:/home/vinayak/venv/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
make_f2fs -l 268435456 /tmp/tmpPUYQ9G
Info: zone aligned segment0 blkaddr: 512
Info: Overprovision ratio = 15.000%
Info: Overprovision segments = 35 (GC reserved = 21)
Running ['mkf2fsuserimg.sh', '/tmp/tmpPUYQ9G', '268435456'] command, exit code = 0
cache size (14) is 0.00% of limit (268435456)
done.
[ 99% 40911/40912] Package OTA: /run/m...kenzo/lineage_kenzo-ota-d4b338b746.zip
unzipping target target-files...
running: unzip -o -q /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/obj/PACKAGING/target_files_intermediates/lineage_kenzo-target_files-d4b338b746.zip -d /tmp/targetfiles-Rnr8Wy
--- target info ---
blockimgdiff_versions = (str) 1,2,3,4
blocksize = (int) 131072
boot_size = (int) 67108864
build.prop = (dict) {'persist.audio.dirac.speaker': 'true', 'ro.sys.sdcardfs': 'true', 'persist.audio.fluence.speaker': 'true', 'bluetooth.hfp.client': '1', 'audio.safx.pbe.enabled': 'true', 'dalvik.vm.isa.arm.variant': 'cortex-a53.a57', 'ro.product.cpu.abilist': 'arm64-v8a,armeabi-v7a,armeabi', 'debug.enable.sglscale': '1', 'ro.build.product': 'kenzo', 'persist.data.iwlan.enable': 'true', 'ro.build.id': 'NJH47F', 'ro.hwui.gradient_cache_size': '1', 'dalvik.vm.stack-trace-file': '/data/anr/traces.txt', 'ro.product.cpu.abilist32': 'armeabi-v7a,armeabi', 'ro.build.selinux': '1', 'ro.qc.sdk.audio.fluencetype': 'fluence', 'tunnel.audio.encode': 'false', 'ro.frp.pst': '/dev/block/bootdevice/by-name/config', 'af.fast_track_multiplier': '1', 'dalvik.vm.lockprof.threshold': '500', 'ro.build.fingerprint': 'Xiaomi/kenzo/kenzo:6.0.1/MMB29M/V8.2.1.0.MHOCNDL:user/release-keys', 'ro.product.manufacturer': 'Xiaomi', 'dalvik.vm.isa.arm64.features': 'default', 'audio.offload.pcm.24bit.enable': 'false', 'persist.radio.cs_srv_type': '1', 'ro.hwui.layer_cache_size': '48', 'ro.build.description': 'kenzo-user 6.0.1 MMB29M V8.2.1.0.MHOCNDL release-keys', 'ro.bootimage.build.fingerprint': 'Xiaomi/lineage_kenzo/kenzo:7.1.2/NJH47F/d4b338b746:userdebug/test-keys', 'ro.product.cpu.abi': 'arm64-v8a', 'ro.sys.fw.dex2oat_thread_count': '4', 'ro.product.brand': 'Xiaomi', 'wifi.interface': 'wlan0', 'ro.cm.build.version.plat.sdk': '7', 'ro.product.model': 'Redmi Note 3', 'persist.radio.redir_party_num': '0', 'media.camera.ts.monotonic': '1', 'ro.cmlegal.url': 'https://lineageos.org/legal', 'persist.audio.fluence.voicecall': 'true', 'persist.cne.feature': '1', 'media.msm8956hw': '1', 'audio.offload.multiple.enabled': 'false', 'persist.demo.hdmirotationlock': 'false', 'ro.build.host': 'skynet', 'ro.build.version.security_patch': '2017-08-05', 'telephony.lteOnCdmaDevice': '1', 'media.sf.extractor-plugin': 'libffmpeg_extractor.so', 'ro.product.locale': 'en-US', 'audio.offload.min.duration.secs': '30', 'ro.btconfig.vendor': 'qcom', 'persist.audio.fluence.voicerec': 'true', 'audio.offload.video': 'false', 'dalvik.vm.isa.arm64.variant': 'generic', 'mmp.enable.3g2': 'true', 'persist.radio.NO_STAPA': '1', 'persist.hwc.downscale_threshold': '1.15', 'persist.sys.dalvik.vm.lib.2': 'libart.so', 'persist.loc.nlp_name': 'com.qualcomm.location', 'ro.board.platform': 'msm8952', 'voice.playback.conc.disabled': 'true', 'persist.data.qmi.adb_logmask': '0', 'ro.product.cpu.abilist64': 'arm64-v8a', 'audio.playback.mch.downsample': 'true', 'net.tcp.2g_init_rwnd': '10', 'ro.vendor.extension_library': 'libqti-perfd-client.so', 'persist.radio.multisim.config': 'dsds', 'persist.rild.nitz_long_ons_3': '', 'persist.rild.nitz_long_ons_2': '', 'persist.rild.nitz_long_ons_1': '', 'persist.rild.nitz_long_ons_0': '', 'ro.build.flavor': 'lineage_kenzo-userdebug', 'dalvik.vm.isa.arm.features': 'default', 'audio.deep_buffer.media': 'true', 'rild.libargs': '-d /dev/smd0', 'ro.gps.agps_provider': '1', 'persist.rild.nitz_short_ons_0': '', 'ro.build.version.release': '7.1.2', 'ro.build.version.codename': 'REL', 'DEVICE_PROVISIONED': '1', 'audio.offload.disable': '1', 'net.bt.name': 'Android', 'persist.data.netmgrd.qos.enable': 'true', 'ro.hwui.text_large_cache_width': '2048', 'persist.audio.fluence.audiorec': 'false', 'persist.radio.VT_HYBRID_ENABLE': '1', 'ro.opengles.version': '196610', 'use.voice.path.for.pcm.voip': 'true', 'persist.rild.nitz_plmn': '', 'ro.hwui.text_small_cache_height': '1024', 'ro.build.display.id': 'lineage_kenzo-userdebug 7.1.2 NJH47F d4b338b746 test-keys', 'audio.offload.pcm.16bit.enable': 'false', 'persist.radio.hw_mbn_update': '0', 'ro.config.ringtone': 'Orion.ogg', 'persist.radio.force_on_dc': 'true', 'persist.gps.qc_nlp_in_use': '1', 'debug.egl.hw': '0', 'ro.storage_manager.enabled': 'true', 'ro.carrier': 'unknown', 'ro.product.board': 'msm8952', 'ro.build.version.preview_sdk': '0', 'ro.com.google.clientidbase': 'android-xiaomi', 'persist.radio.start_ota_daemon': '1', 'ro.cm.build.version.plat.rev': '0', 'persist.timed.enable': 'true', 'ro.build.date': 'Tue Aug 22 13:26:20 IST 2017', 'ro.use_data_netmgrd': 'true', 'persist.radio.sib16_support': '1', 'qcom.bluetooth.soc': 'smd', 'ro.build.date.utc': '1503388580', 'audio.offload.buffer.size.kb': '64', 'keyguard.no_require_sim': 'true', 'ro.qc.sdk.audio.ssr': 'false', 'voice.conc.fallbackpath': 'deep-buffer', 'persist.dpm.feature': '5', 'ro.cm.display.version': '14.1-20170822-UNOFFICIAL-kenzo', 'ro.build.version.all_codenames': 'REL', 'mm.enable.smoothstreaming': 'true', 'ro.btconfig.if': 'smd', 'persist.dbg.vt_avail_ovr': '1', 'dev.pm.dyn_samplingrate': '1', 'ro.build.type': 'userdebug', 'ro.hwui.text_small_cache_width': '1024', 'voice.record.conc.disabled': 'false', 'ro.cm.version': '14.1-20170822-UNOFFICIAL-kenzo', 'persist.radio.sw_mbn_update': '0', 'ro.product.name': 'lineage_kenzo', 'ro.hwui.drop_shadow_cache_size': '6', 'ro.build.version.base_os': '', 'ro.telephony.call_ring.multiple': 'false', 'voice.voip.conc.disabled': 'true', 'persist.data.mode': 'concurrent', 'media.sf.omx-plugin': 'libffmpeg_omx.so', 'ro.expect.recovery_id': '0x22ab51ee62435272df9ab420618c4be9c94727ed000000000000000000000000', 'ro.telephony.default_network': '22,20', 'ro.wifi.channels': '', 'ro.hwui.r_buffer_cache_size': '8', 'persist.camera.HAL3.enabled': '1', 'ro.modversion': '14.1-20170822-UNOFFICIAL-kenzo', 'ro.build.characteristics': 'default', 'debug.mdpcomp.logs': '0', 'audio.offload.gapless.enabled': 'true', 'ro.build.version.incremental': 'd4b338b746', 'ro.config.alarm_alert': 'Hassium.ogg', 'ro.hwui.text_large_cache_height': '1024', 'rild.libpath': '/vendor/lib64/libril-qc-qmi-1.so', 'ro.build.tags': 'test-keys', 'ro.sf.lcd_density': '480', 'ro.build.version.sdk': '25', 'ro.cm.releasetype': 'UNOFFICIAL', 'audio.dolby.ds2.enabled': 'true', 'persist.audio.fluence.spk.mono': 'true', 'ril.subscription.types': 'RUIM', 'persist.dpm.nsrm.bkg.evt': '3955', 'ro.build.user': 'vinayak', 'persist.dbg.volte_avail_ovr': '1', 'ro.hwui.path_cache_size': '32', 'ro.product.device': 'kenzo', 'debug.sf.hw': '0', 'persist.rild.nitz_short_ons_1': '', 'persist.rild.nitz_short_ons_2': '', 'persist.rild.nitz_short_ons_3': '', 'persist.radio.rat_on': 'combine', 'ro.btconfig.dev': '/dev/smd3', 'ro.hwui.texture_cache_flushrate': '0.4', 'ro.hwui.texture_cache_size': '72', 'ro.cm.device': 'kenzo', 'audio_hal.period_size': '192', 'ro.btconfig.chip': 'WCN3680', 'ro.telephony.default_cdma_sub': '0', 'persist.radio.apm_sim_not_pwdn': '1', 'persist.hwc.mdpcomp.enable': 'true', 'persist.radio.custom_ecc': '1', 'persist.sys.dun.override': '0', 'ro.config.notification_sound': 'Argon.ogg', 'audio.offload.track.enable': 'false', 'media.aac_51_output_enabled': 'true'}
cache_fs_type = (str) ext4
cache_size = (int) 268435456
default_system_dev_certificate = (str) build/target/product/security/testkey
device_type = (str) MMC
extfs_sparse_flag = (str) -s
extra_recovery_keys = (str) vendor/cm/build/target/product/security/lineage
fs_type = (str) ext4
fstab = (dict) {'/cache': <common.Partition object at 0x7f2d76e445d0>, '/boot': <common.Partition object at 0x7f2d76e44050>, '/system': <common.Partition object at 0x7f2d76e44950>, '/dsp': <common.Partition object at 0x7f2d76e44210>, '/frp': <common.Partition object at 0x7f2d76e44110>, '/persist': <common.Partition object at 0x7f2d76e44810>, '/recovery': <common.Partition object at 0x7f2d76e44750>, '/firmware': <common.Partition object at 0x7f2d76e44610>, '/data': <common.Partition object at 0x7f2d76e44550>, '/misc': <common.Partition object at 0x7f2d76e44790>}
fstab_version = (int) 2
mkbootimg_args = (str) --ramdisk_offset 0x01000000 --tags_offset 0x00000100
mkbootimg_version_args = (str) --os_version 7.1.2 --os_patch_level 2017-08-05
multistage_support = (str) 1
ota_override_device = (str) kate,kenzo
recovery_api_version = (int) 3
recovery_as_boot = (str)
recovery_mount_options = (str) ext4=max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc
recovery_size = (int) 67108864
selinux_fc = (str) /tmp/targetfiles-Rnr8Wy/META/file_contexts.bin
squashfs_sparse_flag = (str) -s
system_size = (int) 2684354560
tool_extensions = (str) device/xiaomi/kenzo/../common
update_rename_support = (str) 1
use_set_metadata = (str) 1
userdata_size = (int) 26838785024
unable to load device-specific module; assuming none
using prebuilt recovery.img from BOOTABLE_IMAGES...
using system.img from target-files
Total of 655360 4096-byte output blocks in 6263 input chunks.
Finding transfers...
Generating digraph...
Finding vertex sequence...
Reversing backward edges...
0/0 dependencies (0.00%) were violated; 0 source blocks stashed.
Improving vertex order...
Revising stash size...
Total 0 blocks (0 bytes) are packed as new blocks due to insufficient cache size.
Reticulating splines...
1156825088 1156825088 (100.00%) new __DATA
max stashed blocks: 0 (0 bytes), limit: 214748364 bytes (0.00%)
using prebuilt boot.img from BOOTABLE_IMAGES...
boot size (10713088) is 15.96% of limit (67108864)
running: openssl pkcs8 -in build/target/product/security/testkey.pk8 -inform DER -nocrypt
running: java -Xmx2048m -Djava.library.path=/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/lib64 -jar /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmpOsziEC /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/lineage_kenzo-ota-d4b338b746.zip
done.
[100% 40912/40912] build bacon
Package Complete: /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/lineage-14.1-20170822-UNOFFICIAL-kenzo.zip
make: Leaving directory '/run/media/vinayak/6FA49F144DC575A7/android/lineage'
#### make completed successfully (04:59:23 (hh:mm:ss)) ####
va6996 said:
I recently started with building LineageOS. However, I see that ccache isn't working for me for some reason. The ccache directory size is just 56MB. The build takes the same amount of time ~5hr(on my laptop). I've even set the cache size as 70GB. However, my out directory is 55.7GB. What am I doing wrong?...
Click to expand...
Click to collapse
Your better off posting your question on the following Official LineageOS thread for your device.
http://forum.xda-developers.com/showthread.php?t=3542491
Good Luck!
~~~~~~~~~~~~~~~
I Am The Egg Man,
They Are The Egg Men.
I Am The Walrus!
Coo Coo Cachoo!
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Finally discovered reason for Google Account Backup failing

Google account backup to drive is failing on the Chinese variant AL00 (mine):
Code:
02-05 20:05:53.385 3111 3125 I Backup : [BackupHttpRequestUtil] Http Response Code: 200
02-05 20:05:53.390 3111 3125 W Backup : [BackupTransportCS] Server returned error, invalidating auth token. This is retried once.
02-05 20:05:53.391 3111 3125 W Backup : [BackupTransportCS] Network error: proposed backoff of 42742233ms considered too large, not retrying. Exception that caused this: ljx: Server failed authorization.
02-05 20:05:53.391 3111 3125 W Backup : error auth code : AUTH_TOKEN_INVALID
02-05 20:05:53.392 3111 3125 W Backup : [BackupTransportCS] Setting moratorium: 1549440353392
02-05 20:05:53.393 3111 3125 E Backup : [GmsBackupTransport] Error sending final backup to server:
02-05 20:05:53.393 3111 3125 E Backup : ljx: Server failed authorization.
02-05 20:05:53.393 3111 3125 E Backup : error auth code : AUTH_TOKEN_INVALID
02-05 20:05:53.393 3111 3125 E Backup : at com.google.android.gms.backup.transport.BackupTransportChimeraService.a(:[email protected]@15.0.90 (100408-231259764):98)
02-05 20:05:53.393 3111 3125 E Backup : at mkh.k(:[email protected]@15.0.90 (100408-231259764):64)
02-05 20:05:53.393 3111 3125 E Backup : at mkh.a(:[email protected]@15.0.90 (100408-231259764):192)
02-05 20:05:53.393 3111 3125 E Backup : at mks.call(Unknown Source:2)
02-05 20:05:53.393 3111 3125 E Backup : at mkh.a(:[email protected]@15.0.90 (100408-231259764):124)
02-05 20:05:53.393 3111 3125 E Backup : at mkh.performBackup(:[email protected]@15.0.90 (100408-231259764):3)
02-05 20:05:53.393 3111 3125 E Backup : at android.app.backup.BackupTransport$TransportImpl.performBackup(BackupTransport.java:676)
02-05 20:05:53.393 3111 3125 E Backup : at com.android.internal.backup.IBackupTransport$Stub.onTransact(IBackupTransport.java:142)
02-05 20:05:53.393 3111 3125 E Backup : at android.os.Binder.transact(Binder.java:675)
02-05 20:05:53.393 3111 3125 E Backup : at duo.onTransact(:[email protected]@15.0.90 (100408-231259764):3)
02-05 20:05:53.393 3111 3125 E Backup : at android.os.Binder.execTransact(Binder.java:739)
02-05 20:05:53.393 3111 3125 E Backup : [GmsBackupTransport] Encrypted init failed, -1000
02-05 20:05:53.397 3111 3125 I Backup : [GmsBackupTransport] Next backup will happen in 43199995 millis.
02-05 20:05:53.404 1206 3469 I PerformBackupTask: K/V backup pass finished.
So the server is rejecting authentication. I hear this is a common problem and Google are rolling out fixes for client devices. my concern though, is given Google is banned in China (or certainly restricted), I doubt AL00 devices will ever get this fix.
Has any of the AL29 (Global ROM) users managed to get account backup working.
NOTE: This is NOT the Google Sync - this is a DEVICE level backup not to be confused with the sync app on the phone that displays sync of contacts, apps, games, calendar and so on.
Tweetytek said:
Google account backup to drive is failing on the Chinese variant AL00 (mine):
Code:
02-05 20:05:53.385 3111 3125 I Backup : [BackupHttpRequestUtil] Http Response Code: 200
02-05 20:05:53.390 3111 3125 W Backup : [BackupTransportCS] Server returned error, invalidating auth token. This is retried once.
02-05 20:05:53.391 3111 3125 W Backup : [BackupTransportCS] Network error: proposed backoff of 42742233ms considered too large, not retrying. Exception that caused this: ljx: Server failed authorization.
02-05 20:05:53.391 3111 3125 W Backup : error auth code : AUTH_TOKEN_INVALID
02-05 20:05:53.392 3111 3125 W Backup : [BackupTransportCS] Setting moratorium: 1549440353392
02-05 20:05:53.393 3111 3125 E Backup : [GmsBackupTransport] Error sending final backup to server:
02-05 20:05:53.393 3111 3125 E Backup : ljx: Server failed authorization.
02-05 20:05:53.393 3111 3125 E Backup : error auth code : AUTH_TOKEN_INVALID
02-05 20:05:53.393 3111 3125 E Backup : at com.google.android.gms.backup.transport.BackupTransportChimeraService.a(:[email protected]@15.0.90 (100408-231259764):98)
02-05 20:05:53.393 3111 3125 E Backup : at mkh.k(:[email protected]@15.0.90 (100408-231259764):64)
02-05 20:05:53.393 3111 3125 E Backup : at mkh.a(:[email protected]@15.0.90 (100408-231259764):192)
02-05 20:05:53.393 3111 3125 E Backup : at mks.call(Unknown Source:2)
02-05 20:05:53.393 3111 3125 E Backup : at mkh.a(:[email protected]@15.0.90 (100408-231259764):124)
02-05 20:05:53.393 3111 3125 E Backup : at mkh.performBackup(:[email protected]@15.0.90 (100408-231259764):3)
02-05 20:05:53.393 3111 3125 E Backup : at android.app.backup.BackupTransport$TransportImpl.performBackup(BackupTransport.java:676)
02-05 20:05:53.393 3111 3125 E Backup : at com.android.internal.backup.IBackupTransport$Stub.onTransact(IBackupTransport.java:142)
02-05 20:05:53.393 3111 3125 E Backup : at android.os.Binder.transact(Binder.java:675)
02-05 20:05:53.393 3111 3125 E Backup : at duo.onTransact(:[email protected]@15.0.90 (100408-231259764):3)
02-05 20:05:53.393 3111 3125 E Backup : at android.os.Binder.execTransact(Binder.java:739)
02-05 20:05:53.393 3111 3125 E Backup : [GmsBackupTransport] Encrypted init failed, -1000
02-05 20:05:53.397 3111 3125 I Backup : [GmsBackupTransport] Next backup will happen in 43199995 millis.
02-05 20:05:53.404 1206 3469 I PerformBackupTask: K/V backup pass finished.
So the server is rejecting authentication. I hear this is a common problem and Google are rolling out fixes for client devices. my concern though, is given Google is banned in China (or certainly restricted), I doubt AL00 devices will ever get this fix.
Has any of the AL29 (Global ROM) users managed to get account backup working.
NOTE: This is NOT the Google Sync - this is a DEVICE level backup not to be confused with the sync app on the phone that displays sync of contacts, apps, games, calendar and so on.
Click to expand...
Click to collapse
Basically Ppl outside of china never should buy chinese versions if they expecting google 100% support .. that's all
Works fine on my ROM
freeza said:
Works fine on my ROM
Click to expand...
Click to collapse
Yeah dat deodexed? But u have to do it over n over when new ota releases pain in ass..
PhoneTechShop said:
Yeah dat deodexed? But u have to do it over n over when new ota releases pain in ass..
Click to expand...
Click to collapse
What do you mean do it over?
Sent from my EVR-AL00 using Tapatalk
freeza said:
What do you mean do it over?
Sent from my EVR-AL00 using Tapatalk
Click to expand...
Click to collapse
debloating and deodexing .. or u have your own update support ?
PhoneTechShop said:
debloating and deodexing .. or u have your own update support ?
Click to expand...
Click to collapse
We have our own update strategy that's been working fine
freeza said:
We have our own update strategy that's been working fine
Click to expand...
Click to collapse
Can you tell us ?

[ROM][OFFICIAL] ArrowOS [Android 12.1][avicii]

{
"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"
}
ArrowOS​
Code:
/*
* 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 us for messing up your device, We will laugh at you.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/
ABOUT
ArrowOS is an Android Open Source Project based Android mobile operating system started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : check how to
DOWNLOADS
Click here to Download
Tip: Select OEM -> Device,choose Arrow version, choose build type: "GAPPS" or "VANILLA" to download.
Read our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
* Checking build integrity
GPL compliance:
ROM Source- https://github.com/ArrowOS
Kernel Source-https://github.com/PixelExperience-Devices/kernel_oneplus_sm7250
can you share the screenshots from your Nord ? what's different about this rom ?
thanks
Also those who want a support group on Telegram - https://t.me/+yfsMZKQUAP81NDI9
New OFFICIAL update is out.
Changelog -
Initial Release.
Added DeviceSettings
Overall bug fixes.
GRAB the build from here
**NOTE- Clean Flash is must for bugless experience**
does gpay warks with NFC? i was searching that feature but i see no rom working with what i tested
Apheff said:
does gpay warks with NFC? i was searching that feature but i see no rom working with what i tested
Click to expand...
Click to collapse
No idea with that test that once maybe
This is the first Android 12 room with working Gpay and nfc and payments. Battery life is great. FOD works great. Only my gCam crashes from time to time.
Can u please tell me how to flash this please, thanks for u r work
anandnani said:
Can u please tell me how to flash this please, thanks for u r work
Click to expand...
Click to collapse
1. Install any recovery using fastboot
2. Factory Reset
3. Then select adb sideload.
4. Then type adb sideload filename.zip in cmd (copy the name of the rom zip and should be in same folder as in adb or where cmd is opened)
5. Reboot
ANDROID 12.1 Test builds are out. Grab from here
Changelog -
* March Security Patch.
* Android 12.1.
* Included Screen OFF Gestures.
* Fixed NFC error in some scenarios.
Thank you for this ROM. I have been using ArrowOS (11) on another device for a long time, now trying it on Nord.
I ran into trouble with OTA updater. Most likely it is a problem with my phone. The latest OTA ArrowOS v12.1 - 20 Jun 2022 downloaded just fine. When I click Install in Updater, within a second I get an Install error.
The relevant part of the log:
Spoiler: Log
06-25 08:43:00.111 1401 1401 I update_engine: [INFO:delta_performer.cc(811)] Preparing partitions for new update. last hash = , new hash = MhNcrBB3JK+0w9uo+honKnFTFDXN0HgdpzFfb74YJPA=LgfliUHNbAtx+qQ9WvV0yX9x/47gsvPQCKCU29Ybmi4=
06-25 08:43:00.115 1401 1401 I update_engine: [INFO:delta_performer.cc(1394)] Resetting recorded hash for prepared partitions.
06-25 08:43:00.121 1401 1401 I update_engine: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
06-25 08:43:00.140 1401 1401 I update_engine: type=1400 audit(0.0:337): avc: denied { search } for name="/" dev="sde28" ino=1 scontext=u:r:update_engine:s0 tcontext=ubject_r:bt_firmware_file:s0 tclass=dir permissive=1
06-25 08:43:00.152 1401 1401 I update_engine: [INFO:dynamic_partition_control_android.cc(762)] Erasing AVB footer of system_other partition before update.
06-25 08:43:00.154 1401 1401 E update_engine: [libfs_mgr]ReadFstabFromFile(): cannot open file: '/system/etc/fstab.postinstall': No such file or directory
06-25 08:43:00.155 1401 1401 W update_engine: [WARNING:dynamic_partition_control_android.cc(636)] Cannot read fstab from /system/etc/fstab.postinstall: No such file or directory (2)
06-25 08:43:00.156 1401 1401 I update_engine: [INFO:dynamic_partition_control_android.cc(663)] AVB is not enabled on system_other. Skip erasing.
06-25 08:43:00.157 1401 1401 I update_engine: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
06-25 08:43:00.158 1401 1401 I update_engine: [INFO:dynamic_partition_control_android.cc(353)] Created metadata for new update from slot B in /dev/block/bootdevice/by-name/super
06-25 08:43:00.159 1401 1401 I update_engine: [INFO:dynamic_partition_utils.cc(33)] Removing group qti_dynamic_partitions_a
06-25 08:43:00.159 1401 1401 I update_engine: [INFO:dynamic_partition_control_android.cc(1008)] Added group oneplus_dynamic_partitions_a with size 7511998464
06-25 08:43:00.160 1401 1401 I update_engine: [liblp]Partition odm_a will resize from 0 bytes to 1417216 bytes
06-25 08:43:00.161 1401 1401 I update_engine: [INFO:dynamic_partition_control_android.cc(1042)] Added partition odm_a to group oneplus_dynamic_partitions_a with size 1417216
06-25 08:43:00.162 1401 1401 I update_engine: [liblp]Partition product_a will resize from 0 bytes to 1236574208 bytes
06-25 08:43:00.163 1401 1401 I update_engine: [INFO:dynamic_partition_control_android.cc(1042)] Added partition product_a to group oneplus_dynamic_partitions_a with size 1236574208
06-25 08:43:00.163 1401 1401 E update_engine: [liblp]Attempting to create duplication partition with name: system_a
06-25 08:43:00.164 1401 1401 E update_engine: [ERROR:dynamic_partition_control_android.cc(1027)] Cannot add partition system_a to group oneplus_dynamic_partitions_a
06-25 08:43:00.165 1401 1401 E update_engine: [ERROR:dynamic_partition_control_android.cc(828)] UpdatePartitionMetadata(builder.get(), target_slot, manifest) failed.
06-25 08:43:00.166 1401 1401 E update_engine: [ERROR:dynamic_partition_control_android.cc(528)] PrepareDynamicPartitionsForUpdate( source_slot, target_slot, manifest, delete_source) failed.
06-25 08:43:00.166 1401 1401 E update_engine: [ERROR:delta_performer.cc(822)] Unable to initialize partition metadata for slot A
06-25 08:43:00.167 1401 1401 E update_engine: [ERROR:download_action.cc(222)] Error ErrorCode::kInstallDeviceOpenError (7) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
06-25 08:43:00.169 1401 1401 I update_engine: [INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
06-25 08:43:00.170 1401 1401 I update_engine: [INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 200
06-25 08:43:00.171 1401 1401 I update_engine: [INFO:multi_range_http_fetcher.cc(131)] Terminating.
06-25 08:43:00.172 1401 1401 I update_engine: [INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kInstallDeviceOpenError
06-25 08:43:00.173 1401 1401 I update_engine: [INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
06-25 08:43:00.173 1401 1401 I update_engine: [INFO:update_attempter_android.cc(565)] Processing Done.
What could cause this error?
Edit: I am running Magisk V25.0 + UniversalSafetyNetFix to pass Safetynet.
dedaol said:
Thank you for this ROM. I have been using ArrowOS (11) on another device for a long time, now trying it on Nord.
I ran into trouble with OTA updater. Most likely it is a problem with my phone. The latest OTA ArrowOS v12.1 - 20 Jun 2022 downloaded just fine. When I click Install in Updater, within a second I get an Install error.
The relevant part of the log:
Spoiler: Log
06-25 08:43:00.111 1401 1401 I update_engine: [INFO:delta_performer.cc(811)] Preparing partitions for new update. last hash = , new hash = MhNcrBB3JK+0w9uo+honKnFTFDXN0HgdpzFfb74YJPA=LgfliUHNbAtx+qQ9WvV0yX9x/47gsvPQCKCU29Ybmi4=
06-25 08:43:00.115 1401 1401 I update_engine: [INFO:delta_performer.cc(1394)] Resetting recorded hash for prepared partitions.
06-25 08:43:00.121 1401 1401 I update_engine: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
06-25 08:43:00.140 1401 1401 I update_engine: type=1400 audit(0.0:337): avc: denied { search } for name="/" dev="sde28" ino=1 scontext=u:r:update_engine:s0 tcontext=ubject_r:bt_firmware_file:s0 tclass=dir permissive=1
06-25 08:43:00.152 1401 1401 I update_engine: [INFO:dynamic_partition_control_android.cc(762)] Erasing AVB footer of system_other partition before update.
06-25 08:43:00.154 1401 1401 E update_engine: [libfs_mgr]ReadFstabFromFile(): cannot open file: '/system/etc/fstab.postinstall': No such file or directory
06-25 08:43:00.155 1401 1401 W update_engine: [WARNING:dynamic_partition_control_android.cc(636)] Cannot read fstab from /system/etc/fstab.postinstall: No such file or directory (2)
06-25 08:43:00.156 1401 1401 I update_engine: [INFO:dynamic_partition_control_android.cc(663)] AVB is not enabled on system_other. Skip erasing.
06-25 08:43:00.157 1401 1401 I update_engine: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
06-25 08:43:00.158 1401 1401 I update_engine: [INFO:dynamic_partition_control_android.cc(353)] Created metadata for new update from slot B in /dev/block/bootdevice/by-name/super
06-25 08:43:00.159 1401 1401 I update_engine: [INFO:dynamic_partition_utils.cc(33)] Removing group qti_dynamic_partitions_a
06-25 08:43:00.159 1401 1401 I update_engine: [INFO:dynamic_partition_control_android.cc(1008)] Added group oneplus_dynamic_partitions_a with size 7511998464
06-25 08:43:00.160 1401 1401 I update_engine: [liblp]Partition odm_a will resize from 0 bytes to 1417216 bytes
06-25 08:43:00.161 1401 1401 I update_engine: [INFO:dynamic_partition_control_android.cc(1042)] Added partition odm_a to group oneplus_dynamic_partitions_a with size 1417216
06-25 08:43:00.162 1401 1401 I update_engine: [liblp]Partition product_a will resize from 0 bytes to 1236574208 bytes
06-25 08:43:00.163 1401 1401 I update_engine: [INFO:dynamic_partition_control_android.cc(1042)] Added partition product_a to group oneplus_dynamic_partitions_a with size 1236574208
06-25 08:43:00.163 1401 1401 E update_engine: [liblp]Attempting to create duplication partition with name: system_a
06-25 08:43:00.164 1401 1401 E update_engine: [ERROR:dynamic_partition_control_android.cc(1027)] Cannot add partition system_a to group oneplus_dynamic_partitions_a
06-25 08:43:00.165 1401 1401 E update_engine: [ERROR:dynamic_partition_control_android.cc(828)] UpdatePartitionMetadata(builder.get(), target_slot, manifest) failed.
06-25 08:43:00.166 1401 1401 E update_engine: [ERROR:dynamic_partition_control_android.cc(528)] PrepareDynamicPartitionsForUpdate( source_slot, target_slot, manifest, delete_source) failed.
06-25 08:43:00.166 1401 1401 E update_engine: [ERROR:delta_performer.cc(822)] Unable to initialize partition metadata for slot A
06-25 08:43:00.167 1401 1401 E update_engine: [ERROR:download_action.cc(222)] Error ErrorCode::kInstallDeviceOpenError (7) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
06-25 08:43:00.169 1401 1401 I update_engine: [INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
06-25 08:43:00.170 1401 1401 I update_engine: [INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 200
06-25 08:43:00.171 1401 1401 I update_engine: [INFO:multi_range_http_fetcher.cc(131)] Terminating.
06-25 08:43:00.172 1401 1401 I update_engine: [INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kInstallDeviceOpenError
06-25 08:43:00.173 1401 1401 I update_engine: [INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
06-25 08:43:00.173 1401 1401 I update_engine: [INFO:update_attempter_android.cc(565)] Processing Done.
What could cause this error?
Edit: I am running Magisk V25.0 + UniversalSafetyNetFix to pass Safetynet.
Click to expand...
Click to collapse
Well, to answer my own question:
This line in the log contains the clue: update_engine: [liblp]Attempting to create duplication partition with name: system_a
So, in fastbootd mode I've ran: fastboot delete-logical-partition system_a . The update installed successfully afterwards. Don't ask me why this was needed.
Hi All!
I installed this ROM yesterday, everything works fine, banking apps, google Pay etc.
My only questions is it possibile to lock app in memory? I like to have some apps always on like Spotify and browser. I cant see that option in recent apps screen.

Categories

Resources