Database Users

Factory values in BT AudioGateway

Hi..
I have been instalaling some BTroute and Jetaware aplications in my touch Dual- so now my \HKEY_LOCAL_MACHINE\software\microsoft\Bluetooth\audioGateway does not have the factory settins
Can someone send me the default settins?
Just check on the registry and write down here the Keys and Values
Thank you

Default setting from my Touch Dual 20keys
\HKEY_LOCAL_MACHINE\software\microsoft\Bluetooth\AudioGateway
BTAGExtModule = OEMAGW.dll
BTAGPBModule = \Windows\BthAGPhonebook.dll
Capability = 0x65(101)
ConnectHFOnCall = 0x0(0)
NoRoleSwitch = 0x1(1)
SupportCLI = 0x0(0)
Hope this can help you.

My was
BTAGextmodule=BthagPhoneBook.dll
BTAGPBModule=OEMAGW.DLL
Capability 0x65
ConnectHFOnCall 0x0
MicVolume 0x8
NoRoleSwitch 0x1
PowerSave 0x0
SpkVolume 0x8
SupportCli 0x0
I'm going to try yours
Thanks!

Strange DSP-Kernel problem

I have a strange problem with my defy. When I updated the Defy with the latest Pikachu Rom 2.x I noticed a strong performance gap. CPU was on 100% and did not get down. The process "bridge_recovery" (kernel) nearly got 95% CPU (beginning before even the lock screen is visible). On inspecting with adb I found the following problem related to the DSP:
dmesg output:
Code:
<6>[ 666.158386] bridge_load_firmware: loading bridge firmware from /system/lib/dsp/baseimage.dof
<6>[ 666.184692] ***** DSPMMU FAULT ***** IRQStatus 0x2
<6>[ 666.184783] ***** DSPMMU FAULT ***** faultAddr 0x205aace0
<6>[ 666.184967] WMD_DEH_Notify: ********** DEVICE EXCEPTION **********
<6>[ 666.185058] WMD_DEH_Notify: DSP_MMUFAULT,errInfo = 0x0
<6>[ 666.185241] WMD_DEH_Notify: DSP_MMUFAULT, High Address = 0x205a
<6>[ 666.185333] WMD_DEH_Notify: DSP_MMUFAULT, Low Address = 0xace0
<6>[ 666.185485] WMD_DEH_Notify: DSP_MMUFAULT, fault address = 0x205aace0
<6>[ 666.185607] dspbridge fatal error occured, attempting to recover
<6>[ 666.188781] WMD_DEH_Notify: ********** DEVICE EXCEPTION **********
<3>[ 666.188873] WMD_DEH_Notify: DSP_SYSERROR, errInfo = 0x102
<6>[ 666.296752] CM_FCLKEN_IVA2(0x48004000) = 0x1
<6>[ 666.296844] CM_CLKEN_PLL_IVA2(0x48004004) = 0x77
<6>[ 666.296997] CM_ICLKEN1_IVA2(0x48004010) = 0x0
<6>[ 666.297088] CM_IDLEST_IVA2(0x48004020) = 0x0
<6>[ 666.297180] CM_IDLEST_PLL_IVA2(0x48004024) = 0x1
<6>[ 666.297332] CM_AUTOIDLE_PLL_IVA2(0x48004034) = 0x1
<6>[ 666.297424] CM_CLKSEL1_PLL_IVA2(0x48004040) = 0x114a0c
<6>[ 666.297576] CM_CLKSTCTRL_IVA2(0x48004048) = 0x3
<6>[ 666.297668] CM_CLKSTST_IVA2(0x4800404c) = 0x1
<6>[ 666.297821] RM_RSTCTRL_IVA2(0x48306050) = 0x4
<6>[ 666.297912] RM_RSTST_IVA2(0x48306058) = 0x307
<6>[ 666.298004] PM_PWSTCTRL_IVA2(0x483060e0) = 0xff0f07
<6>[ 666.298156] PM_PWSTST_IVA2(0x483060e4) = 0xff7
<6>[ 666.298248] CM_ICLKEN1_CORE(0x48306a10) = 0x30060da
<6>[ 666.298400] PM_MPUGRPSEL_PER(0x483070a4) = 0x3e803
<6>[ 666.298492] PM_IVA2GRPSEL_PER(0x483070a8) = 0xc0
<6>[ 666.298583] PRM_IRQSTATUS_IVA2(0x483060f8) = 0x2
<6>[ 666.298736]
<6>[ 666.298736]
<6>[ 666.298736] ******* MBX DUMP *********************
<6>[ 666.299072] MAILBOX_SYSCONFIG(0x48094010) = 0x11
<6>[ 666.299163] MAILBOX_FIFOSTATUS_MPU(0x48094080) = 0x0
<6>[ 666.299224] MAILBOX_FIFOSTATUS_DSP(0x48094084) = 0x0
<6>[ 666.299407] MAILBOX_MSGSTATUS_MPU(0x480940c0) = 0x1
<6>[ 666.299468] MAILBOX_MSGSTATUS_DSP(0x480940c4) = 0x 0
<6>[ 666.299652] MAILBOX_IRQSTATUS_MPU(0x48094100) = 0xaab
<6>[ 666.299743] MAILBOX_IRQSTATUS_DSP(0x48094108) = 0xaaf
<6>[ 666.299896] MAILBOX_IRQENABLE_MPU(0x48094104) = 0x4
<6>[ 666.299987] MAILBOX_IRQENABLE_DSP(0x4809410c) = 0x0
<6>[ 666.300140] dspbridge: delivering sigkill to all bridge users
<6>[ 666.300231] dspbridge: waiting for bridge users to exit
<6>[ 666.300323] dspbridge: all bridge users exited
<6>[ 666.300476] reset mbox
I tried different ROMs like cm7.2 and motoice on cm9, but both would not boot (30min+ on boot animation). WhiteRabbit booted, but I had the same problem with the bridge_recovery process. So I got back to Pikachu 111216 (from what I updated). The problem is not gone, but the old mod is successful on loading the firmware after some tries. Until that point, I have 100% CPU, too. This rom is useable, but some newer version would be fine.
It seems, the milestone had some similar failure: see at code.google.com /p/cyanogenmod4milestone/issues/detail?id=672 (Sorry, I am not allowed to post links)
But I did not found some real solution.
I hope, someone has an idea what to do?

[Q&A] [GUIDE][K920] Unlock bootloader on Lenovo VIBE Z2 Pro

Q&A for [GUIDE][K920] Unlock bootloader on Lenovo VIBE Z2 Pro
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE][K920] Unlock bootloader on Lenovo VIBE Z2 Pro. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Great guide, Electry.
I just used the QFil to unbrick my phone.
My phone hung at the bootup logo after the latest update. I think it was because I didn't unroot before update.
Nice to see some development on this great phone.

Tried to unlock bootloader but its not success
Hi supporter!
I tried to unlock bootloader my K920 China mobile version (OTA to 5.0.2, vibeUI2.5)
but i can't dial *#*#8899#*#* because it not appear pop-up dialog
I was setup driver, but Device Manager is not have the "Modem" to show "Lenovo HS-USB modem phone", the "Port" is not show "Lenovo HS-USB Diagnostics" and "Lenovo HS-USB NMEA" too.
pls help!
Thanks!
ps. sorry about my English

buidinhhai said:
Hi supporter!
I tried to unlock bootloader my K920 China mobile version (OTA to 5.0.2, vibeUI2.5)
but i can't dial *#*#8899#*#* because it not appear pop-up dialog
I was setup driver, but Device Manager is not have the "Modem" to show "Lenovo HS-USB modem phone", the "Port" is not show "Lenovo HS-USB Diagnostics" and "Lenovo HS-USB NMEA" too.
pls help!
Thanks!
ps. sorry about my English
Click to expand...
Click to collapse
You could try skipping step 8. and 9. in "Preparation" section, as I'm not sure if enabling diagnostic mode is really needed. Simply continue with the guide and let me know how it worked

I don't know unlocked BL or not
Electry said:
You could try skipping step 8. and 9. in "Preparation" section, as I'm not sure if enabling diagnostic mode is really needed. Simply continue with the guide and let me know how it worked
Click to expand...
Click to collapse
I press volume- and plug in the cable, the Device Manager show all port such as the upon post. But when i tried to flash , the QFil show this :
Start Download
COM Port number:6
Switch To EDL
Download Fail:Switch To EDL FailSystem.Exception: Fail to find QDLoader port after switch
в QFIL.Tech.DownloadTech.GetPortAfterReset(String description, Int32 timeoutInSec)
в QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
Then i've tried to unlock
(press volume + and plug in the cable to see Qualcomm HS-USB QDloader 9008)
the QFil show this :
Process Index:0
Programmer Path:C:\VibeZ2Pro_UnLock_BootLoader_L\prog_emmc_firehose_8974.mbn
Image Search Path:C:\VibeZ2Pro_UnLock_BootLoader_L
Please select the XML file
Start Download
Program Path:C:\VibeZ2Pro_UnLock_BootLoader_L\prog_emmc_firehose_8974.mbn
COM Port number:3
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:3
Sending NOP
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
Request payload size 0xc000 is not the same as support payload size, change to 0x20000
Set TxBuffer 0x20000, RxBuffer 0x4000
Firehose configure packet sent successfully!
Total Bytes To Program 0xB1EA0
Download Image
PROGRAM: Partition 0, Sector: 0, Length: 33 Sectors, Sector Size: 512 Bytes
File: C:\VibeZ2Pro_UnLock_BootLoader_L\gpt_backup0.bin
PROGRAM: Written Bytes 0x4200 (64)
Program Size: 0.02 MB
PROGRAM: Partition 0, Sector: 0, Length: 34 Sectors, Sector Size: 512 Bytes
File: C:\VibeZ2Pro_UnLock_BootLoader_L\gpt_main0.bin
PROGRAM: Written Bytes 0x4400 (64)
Program Size: 0.02 MB
PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x54c
PROGRAM: Partition 0, Sector: 264232, Length: 1356 Sectors, Sector Size: 512 Bytes
File: C:\VibeZ2Pro_UnLock_BootLoader_L\emmc_appsboot.mbn
PROGRAM: Written Bytes 0xa9800 (64)
Program Size: 0.66 MB
Total Size: 0.69 MB
Total Size: 0 Seconds
PATCH: Partition 0, Sector: 7, Offset 168 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 168 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 32 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 24 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 72 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-33.
PATCH: Partition 0, Sector: 1, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(2,3072)
PATCH: Partition 0, Sector: 0, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-33.,3072)
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(1,92)
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-1.,92)
Total download file size: 0,6948242MB
Throughput: 0M/s
Reset Phone
Waiting for reset done...
Let me know was i unlocked bootloader ?
is there the code or other method to test the Lenovo-phone's status of the bootloader?

buidinhhai said:
Let me know was i unlocked bootloader ?
is there the code or other method to test the Lenovo-phone's status of the bootloader?
Click to expand...
Click to collapse
It looks like you did it
If you have Lollipop, you can check it by doing "One-Time boot" into TWRP recovery. It should boot without an error.
Guide here: http://forum.xda-developers.com/android/development/recovery-twrp-2-8-6-1-sevenmaxs-t3086999

thanks to Electry
Electry said:
It looks like you did it
If you have Lollipop, you can check it by doing "One-Time boot" into TWRP recovery. It should boot without an error.
Guide here: http://forum.xda-developers.com/android/development/recovery-twrp-2-8-6-1-sevenmaxs-t3086999
Click to expand...
Click to collapse
Finally, i unlocked bootloader and up rom 4.4.2. Now, my phone has google service and my language - Vietnamese.
Thanks for your help, @Electry.

I have the same message, but my problem is that, That I have problem with OS. They not loaded. Telephone booting until logo, vibration and rebooting.
Was lolipop 5.0.2 untill it. Errors the same
PATCH: Partition 0, Sector: 7, Offset 296 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 296 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 32 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 24 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 72 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-33.
PATCH: Partition 0, Sector: 1, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(2,3072)
PATCH: Partition 0, Sector: 0, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-33.,3072)
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(1,92)
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-1.,92)
Total download file size: 2051,244MB
Throughput: 15,

Great giude friend

Hello to everybody !!
Also my Lenovo S856 is bricked. This happened because the recovery did not allow to make mods (backup, restore ..) but only wipes, and I thought it depended on the locked bootloader. At that point, I used the app EzUnlock and yet the phone is bricked, it does not turn on, no recovery, no sign of life, and it is seen as Qualcomm HS-USB Dignostics 9006 (COM3).
My seller sent me a rom to make the flash with MiFlash but the process crashes after 4 seconds. I also tried the QFIL tools and even then the process crashes with the message "Download Fail: Switch To FailFireHose Fail.
Any suggestions ?
Thanks for help

Electry said:
You could try skipping step 8. and 9. in "Preparation" section, as I'm not sure if enabling diagnostic mode is really needed. Simply continue with the guide and let me know how it worked
Click to expand...
Click to collapse
Am stuck in an error
Reset Phone
Waiting for reset done...
Download Fail:FireHose Fail Fail to find QDLoader port after switch
Finish Download
then phone boots in normal mode. Please help.
Supersu needs binary update and i also cant update it. Plz Help

Hello,
Everytime I try this method I am getting the below error
Process Index:0
Programmer Path:C:\Users\user\Downloads\UnlockBootloader_LP_ROW\UnlockBootloader_LP_ROW\prog_emmc_firehose_8974.mbn
Image Search Path:C:\Users\user\Downloads\UnlockBootloader_LP_ROW\UnlockBootloader_LP_ROW
Please select the XML file
Start Download
COM Port number:7
Switch To EDL
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
at QC.QMSLPhone.Phone.QPHONEMS_SwitchToEDL()
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
Please let me know what can be done.
Note : I am on Lenovo Vibe z2 Pro Stock rom build S288[rooted]

Issue resolved.. Thank you

Any idea how to unlock bootloader of lenovo vibe P1 with mm6.0.1
Sent from my Lenovo P1a42 using XDA-Developers mobile app

buidinhhai said:
I press volume- and plug in the cable, the Device Manager show all port such as the upon post. But when i tried to flash , the QFil show this :
Start Download
COM Port number:6
Switch To EDL
Download Fail:Switch To EDL FailSystem.Exception: Fail to find QDLoader port after switch
в QFIL.Tech.DownloadTech.GetPortAfterReset(String description, Int32 timeoutInSec)
в QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
Then i've tried to unlock
(press volume + and plug in the cable to see Qualcomm HS-USB QDloader 9008)
the QFil show this :
Process Index:0
Programmer Path:C:\VibeZ2Pro_UnLock_BootLoader_L\prog_emmc_firehose_8974.mbn
Image Search Path:C:\VibeZ2Pro_UnLock_BootLoader_L
Please select the XML file
Start Download
Program Path:C:\VibeZ2Pro_UnLock_BootLoader_L\prog_emmc_firehose_8974.mbn
COM Port number:3
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:3
Sending NOP
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
Request payload size 0xc000 is not the same as support payload size, change to 0x20000
Set TxBuffer 0x20000, RxBuffer 0x4000
Firehose configure packet sent successfully!
Total Bytes To Program 0xB1EA0
Download Image
PROGRAM: Partition 0, Sector: 0, Length: 33 Sectors, Sector Size: 512 Bytes
File: C:\VibeZ2Pro_UnLock_BootLoader_L\gpt_backup0.bin
PROGRAM: Written Bytes 0x4200 (64)
Program Size: 0.02 MB
PROGRAM: Partition 0, Sector: 0, Length: 34 Sectors, Sector Size: 512 Bytes
File: C:\VibeZ2Pro_UnLock_BootLoader_L\gpt_main0.bin
PROGRAM: Written Bytes 0x4400 (64)
Program Size: 0.02 MB
PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x54c
PROGRAM: Partition 0, Sector: 264232, Length: 1356 Sectors, Sector Size: 512 Bytes
File: C:\VibeZ2Pro_UnLock_BootLoader_L\emmc_appsboot.mbn
PROGRAM: Written Bytes 0xa9800 (64)
Program Size: 0.66 MB
Total Size: 0.69 MB
Total Size: 0 Seconds
PATCH: Partition 0, Sector: 7, Offset 168 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 168 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 32 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 24 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 72 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-33.
PATCH: Partition 0, Sector: 1, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(2,3072)
PATCH: Partition 0, Sector: 0, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-33.,3072)
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(1,92)
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-1.,92)
Total download file size: 0,6948242MB
Throughput: 0M/s
Reset Phone
Waiting for reset done...
Let me know was i unlocked bootloader ?
is there the code or other method to test the Lenovo-phone's status of the bootloader?
Click to expand...
Click to collapse
Dear after that remove the cable & also remove the battery of phone . put any ota zip "Hungary2Default.ota" OR better "HongKong2Default.ota" in Sd Card & apply update from sd card option
this worked for me

adithebratt said:
Issue resolved.. Thank you
Click to expand...
Click to collapse
able to share how you resolved that?
i sort of unlocked bootloader (based on the comment from the earlier posts) but I failed to flash TWRP to the phone, always "waiting for device"

Issued resolved with another USB cable (my 3rd USB cable that I hardly use)

[GUIDE] Build AOSP for zerofltexx by Astrubale

DELETED

but there is some aosp build usable ( incall micro working on fine ) for galaxy s 6?
thanks for the guide Master

supera3 said:
but there is some aosp build usable ( incall micro working on fine ) for galaxy s 6?
thanks for the guide Master
Click to expand...
Click to collapse
Depend on what source zero-common, zerofltexx and kernel are based.

Very cool guide, I'll have to give this a shot later just for fun! Sorry for doubting you before.

If there are new commits, before ". build/envsetup.sh" tipe "repo sync" for upgrade.

Hi @Astrubale,
I tried to build cm-13.0 with your tutorial, but build fails non-stop on:
Code:
target SharedLib: libexpat (/home/sebek/android/system/out/target/product/zerofltexx/obj/SHARED_LIBRARIES/libexpat_intermediates/LINKED/libexpat.so)
/home/sebek/android/system/out/target/product/zerofltexx/obj/SHARED_LIBRARIES/libexpat_intermediates/lib/xmlparse.o: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
build/core/shared_library_internal.mk:80: recipe for target '/home/sebek/android/system/out/target/product/zerofltexx/obj/SHARED_LIBRARIES/libexpat_intermediates/LINKED/libexpat.so' failed
make: *** [/home/sebek/android/system/out/target/product/zerofltexx/obj/SHARED_LIBRARIES/libexpat_intermediates/LINKED/libexpat.so] Error 1
make: *** Waiting for unfinished jobs....
make[3]: Nothing to be done for 'dtbs'.
or
Code:
/home/sebek/android/system/out/target/product/zerofltexx/obj/SHARED_LIBRARIES/libcrypto_intermediates/android_compat_hacks.o: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
build/core/shared_library_internal.mk:80: recipe for target '/home/sebek/android/system/out/target/product/zerofltexx/obj/SHARED_LIBRARIES/libcrypto_intermediates/LINKED/libcrypto.so' failed
make: *** [/home/sebek/android/system/out/target/product/zerofltexx/obj/SHARED_LIBRARIES/libcrypto_intermediates/LINKED/libcrypto.so] Error 1
make: *** Waiting for unfinished jobs....
make: Leaving directory '/home/sebek/android/system'
The solution is to remove xmlparse.o or android_compat_hacks.o and I guess it continues the build. Almost at the end of compilation (I presume) it throws out that very error and after a while I get:
Code:
/home/sebek/android/system/kernel/samsung/exynos7420/scripts/Makefile.fwinst:45: target '/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule
/home/sebek/android/system/kernel/samsung/exynos7420/scripts/Makefile.fwinst:45: target '/lib/firmware/abov/abov_valley.fw' given more than once in the same rule
make[1]: Leaving directory '/home/sebek/android/system/kernel/samsung/exynos7420'
make[1]: Entering directory '/home/sebek/android/system/kernel/samsung/exynos7420'
INSTALL net/ipv4/tcp_htcp.ko
INSTALL net/ipv4/tcp_westwood.ko
/home/sebek/android/system/kernel/samsung/exynos7420/scripts/Makefile.fwinst:45: target '../../system/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule
/home/sebek/android/system/kernel/samsung/exynos7420/scripts/Makefile.fwinst:45: target '../../system/lib/firmware/abov/abov_valley.fw' given more than once in the same rule
DEPMOD 3.10.61
make[1]: Leaving directory '/home/sebek/android/system/kernel/samsung/exynos7420'
make: Leaving directory '/home/sebek/android/system'
#### make failed to build some targets (26:29 (mm:ss)) ####
Maybe you'd be willing to give me some advice on how I could finish this build ? I am building on Ubuntu 16.04, dl'd the newest kernel from Brandon's git repo.
My best

djseban2 said:
Hi @Astrubale,
I tried to build cm-13.0 with your tutorial, but build fails non-stop on:
Code:
target SharedLib: libexpat (/home/sebek/android/system/out/target/product/zerofltexx/obj/SHARED_LIBRARIES/libexpat_intermediates/LINKED/libexpat.so)
/home/sebek/android/system/out/target/product/zerofltexx/obj/SHARED_LIBRARIES/libexpat_intermediates/lib/xmlparse.o: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
build/core/shared_library_internal.mk:80: recipe for target '/home/sebek/android/system/out/target/product/zerofltexx/obj/SHARED_LIBRARIES/libexpat_intermediates/LINKED/libexpat.so' failed
make: *** [/home/sebek/android/system/out/target/product/zerofltexx/obj/SHARED_LIBRARIES/libexpat_intermediates/LINKED/libexpat.so] Error 1
make: *** Waiting for unfinished jobs....
make[3]: Nothing to be done for 'dtbs'.
or
Code:
/home/sebek/android/system/out/target/product/zerofltexx/obj/SHARED_LIBRARIES/libcrypto_intermediates/android_compat_hacks.o: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
build/core/shared_library_internal.mk:80: recipe for target '/home/sebek/android/system/out/target/product/zerofltexx/obj/SHARED_LIBRARIES/libcrypto_intermediates/LINKED/libcrypto.so' failed
make: *** [/home/sebek/android/system/out/target/product/zerofltexx/obj/SHARED_LIBRARIES/libcrypto_intermediates/LINKED/libcrypto.so] Error 1
make: *** Waiting for unfinished jobs....
make: Leaving directory '/home/sebek/android/system'
The solution is to remove xmlparse.o or android_compat_hacks.o and I guess it continues the build. Almost at the end of compilation (I presume) it throws out that very error and after a while I get:
Code:
/home/sebek/android/system/kernel/samsung/exynos7420/scripts/Makefile.fwinst:45: target '/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule
/home/sebek/android/system/kernel/samsung/exynos7420/scripts/Makefile.fwinst:45: target '/lib/firmware/abov/abov_valley.fw' given more than once in the same rule
make[1]: Leaving directory '/home/sebek/android/system/kernel/samsung/exynos7420'
make[1]: Entering directory '/home/sebek/android/system/kernel/samsung/exynos7420'
INSTALL net/ipv4/tcp_htcp.ko
INSTALL net/ipv4/tcp_westwood.ko
/home/sebek/android/system/kernel/samsung/exynos7420/scripts/Makefile.fwinst:45: target '../../system/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule
/home/sebek/android/system/kernel/samsung/exynos7420/scripts/Makefile.fwinst:45: target '../../system/lib/firmware/abov/abov_valley.fw' given more than once in the same rule
DEPMOD 3.10.61
make[1]: Leaving directory '/home/sebek/android/system/kernel/samsung/exynos7420'
make: Leaving directory '/home/sebek/android/system'
#### make failed to build some targets (26:29 (mm:ss)) ####
Maybe you'd be willing to give me some advice on how I could finish this build ? I am building on Ubuntu 16.04, dl'd the newest kernel from Brandon's git repo.
My best
Click to expand...
Click to collapse
Can you send me a screen of /android/system/kernel/samsung/exynos7420/ ?

Astrubale said:
Can you send me a screen of /android/system/kernel/samsung/exynos7420/ ?
Click to expand...
Click to collapse
Sure, it looks like this:
hxxp://imgur.com/M5sAjIo
@edit: I deleted exynos7420 dir and unzipped it (dl'd zip from github) once again, this time through Terminal. Turned out it was something wrong with that, therefore I succeded with building the ROM, but my S6 hangs on "Kernel is not seandroid enforcing", after flashing the ROM (tough luck, I guess). What's more I tried flahyboy's ROM, to see if it's maybe something wrong with my S6 - well, you can say flahyboy's ROM starts instantly, but in-call mic is not working. I'd be grateful for any hints on what might be wrong. One and only thing I noticed is flahyboy's ROM is slightly greater in size (~40MB) that mine.. maybe the build solution did not add something to my zip.. Anyway - great tutorial, thanks for that. Installing AOSP just made me even more anxious to wait for making this system stable :good:

djseban2 said:
Sure, it looks like this:
hxxp://imgur.com/M5sAjIo
@edit: I deleted exynos7420 dir and unzipped it (dl'd zip from github) once again, this time through Terminal. Turned out it was something wrong with that, therefore I succeded with building the ROM, but my S6 hangs on "Kernel is not seandroid enforcing", after flashing the ROM (tough luck, I guess). What's more I tried flahyboy's ROM, to see if it's maybe something wrong with my S6 - well, you can say flahyboy's ROM starts instantly, but in-call mic is not working. I'd be grateful for any hints on what might be wrong. One and only thing I noticed is flahyboy's ROM is slightly greater in size (~40MB) that mine.. maybe the build solution did not add something to my zip.. Anyway - great tutorial, thanks for that. Installing AOSP just made me even more anxious to wait for making this system stable :good:
Click to expand...
Click to collapse
Thank, but can you compile now?

Astrubale said:
Thank, but can you compile now?
Click to expand...
Click to collapse
Yeah, I compiled it at last, but if i flash the zip from out folder, then the phone hangs on first bootsplash ("Galaxy S6") with "Kernel is not seandroid enforcing"

djseban2 said:
Yeah, I compiled it at last, but if i flash the zip from out folder, then the phone hangs on first bootsplash ("Galaxy S6") with "Kernel is not seandroid enforcing"
Click to expand...
Click to collapse
Search for errors inside /proc/last_kmsg

Wow cool clean and easy Guide. Thanks for this.
Weil try myself on that.

Astrubale said:
Search for errors inside /proc/last_kmsg
Click to expand...
Click to collapse
Code:
Samsung S-Boot 4.0 for SM-G920F (Apr 22 2016 - 16:59:51)
EXYNOS7420 EVT 1.3 (Base on ARM CortexA53)
3048MB / 0MB / Rev 11 / G920FXXU3DPDP / (PKG_ID 0x0) / LOT_ID N3N1P / RST_STAT (0x10000)
__if_pmic_rev_init - MUIC API is not ready!
MON: 0x8(1)
MON[0] = (1)[0x1c, 0x7a]
MON[1] = (2)[0x1a, 0x56]
MON[2] = (3)[0x1a, 0x3d]
MON[3] = (4)[0x1c, 0x4e]
MON[4] = (5)[0x1a, 0x39]
MON[5] = (6)[0x1a, 0x30]
MON[6] = (7)[0x15, 0x44]
MON[7] = (0)[0x0c, 0x07]
pmic_asv_init
(ASV_TBL_BASE+0x00)[11:0] bigcpu_asv_group = 2184
(ASV_TBL_BASE+0x00)[15:12] bigcpu_ssa0 = 0
(ASV_TBL_BASE+0x00)[27:16] littlecpu_asv_group = 2457
(ASV_TBL_BASE+0x00)[31:28] littlecpu_ssa0 = 0
(ASV_TBL_BASE+0x04)[11:0] g3d_asv_group = 2184
(ASV_TBL_BASE+0x04)[15:12] g3d_ssa0 = 0
(ASV_TBL_BASE+0x04)[27:16] mif_asv_group = 2184
(ASV_TBL_BASE+0x04)[31:28] mif_ssa0 = 0
(ASV_TBL_BASE+0x08)[11:0] int_asv_group = 3276
(ASV_TBL_BASE+0x08)[15:12] int_ssa0 = 6
(ASV_TBL_BASE+0x08)[27:16] cam_disp_asv_group = 2184
(ASV_TBL_BASE+0x08)[31:28] cam_disp_ssa0 = 0
(ASV_TBL_BASE+0x0C)[3:0] dvfs_asv_table_version = 15
(ASV_TBL_BASE+0x0C)[4] asv_group_type = 0
(ASV_TBL_BASE+0x0C)[7:5] reserved01 = 0
(ASV_TBL_BASE+0x0C)[8] shift_type = 0
(ASV_TBL_BASE+0x0C)[9] ssa1_enable = 0
(ASV_TBL_BASE+0x0C)[10] ssa0_enable = 1
(ASV_TBL_BASE+0x0C)[15:11] reserved02 = 0
(ASV_TBL_BASE+0x0C)[16] asv_method = 1
(ASV_TBL_BASE+0x0C)[31:17] reserved03 = 0
(ASV_TBL_BASE+0x10)[3:0] main_asv_group = 0
(ASV_TBL_BASE+0x10)[7:4] main_asv_ssa = 0
(ASV_TBL_BASE+0x10)[11:8] bigcpu_ssa1 = 0
(ASV_TBL_BASE+0x10)[15:12] littlecpu_ssa1 = 0
(ASV_TBL_BASE+0x10)[19:16] g3d_ssa1 = 0
(ASV_TBL_BASE+0x10)[23:20] mif_ssa1 = 0
(ASV_TBL_BASE+0x10)[27:24] int_ssa1 = 0
(ASV_TBL_BASE+0x10)[31:28] cam_disp_ssa1 = 0
(ASV_TBL_BASE+0x14)[8:0] bigcpu_ssa_ema = 0
(ASV_TBL_BASE+0x14)[17:9] littlecpu_ssa_ema = 0
(ASV_TBL_BASE+0x14)[26:18] g3d_ssa_ema = 0
(ASV_TBL_BASE+0x14)[31:27] reserved04 = 0
chip_status = f, bin2_efuse = 0
muic_register_max77843_apis
muic_is_max77843 chip_id:0x43 muic_id:0xb5 -> matched.
MUIC rev = MAX77843(181)
init_multi_microusb_ic Active MUIC 0xb5
max77843_init_microusb_ic: MUIC: CDETCTRL:0x2d
max77843_init_microusb_ic: MUIC: CONTROL1:0x00
max77843_init_microusb_ic: MUIC: CONTROL2:0x3b
max77843_muic_get_adc_value: STATUS1:0x1f
max77843_muic_get_adc_value: ADC:0x1f
max77843_muic_get_adc_value: STATUS1:0x1f
max77843_muic_get_adc_value: ADC:0x1f
max77843_muic_get_chg_typ: STATUS2:0x00
max77843_muic_get_chg_typ: CHGTYP:0x00
max77843_muic_get_adc_value: STATUS1:0x1f
max77843_muic_get_adc_value: ADC:0x1f
max77843_muic_get_chg_typ: STATUS2:0x00
max77843_muic_get_chg_typ: CHGTYP:0x00
load Secure Payload done.
Chip ID : 060f4d16dd28 / 0x00007700
EL3 monitor information => Built : 16:48:28, Jan 18 2016
bConfigDescrLock: 1
sw_lock success
sw_lock success
sw_lock success
SCSI CMD : 55 11 00 00 00 00 00 00 14 00
SCSI Response(01) : Target Failure
SCSI Status(02) : max77843_set_muic_uart_early: MUIC: CONTROL1: 0x00
max77843_muic_get_adc_value: STATUS1:0x1f
max77843_muic_get_adc_value: ADC:0x1f
[Debug Info.]
S-BOOT : VERSION_-+F0
SecureOS : 20 (MB)
- read_bl1
blk_bread_bootsector: LUN 1, from 0x0, size 0x10, buffer 0x45708000
Verify_Binary_Signature 0x45720120 [email protected], [email protected]
pit_check_signature (PIT) valid.
PARAM ENV VERSION: v1.0..
blk_bread_bootsector: LUN 1, from 0xffe, size 0x1, buffer 0x441204c0
initialize_ddi_data: usable! (3:0xf), warranty reason : (0x0303)
MAGIC_RAM_BASE: 4000000, MAGIC_RAM_BASE2: 100001, ompin: 2000a
[ldfw] Pass LDFW partition!
[ldfw] read whole CM partition from the storage
ldfw: 0th ldfw's version 0x20151027 name : CryptoManagerV20
ldfw: 1th ldfw's version 0x20151203 name : fmp_fw
ldfw: init ldfw(s). whole ldfws size 0x204110
[ldfw] try to init 2 ldfw(s). except 0 ldfw 2 ldfw(s) have been inited done.
[mobi_drv] add: 0x43e71940, size: 11401
MobiCore IDLE flag = 0
MobiCore Driver loaded and RTM IDLE!
[OTP] 27 bit read: 0x5
[OTP] 22 bit read: 0x0
[OTP] 21 bit read: 0x0
[OTP] 23 bit read: 0x1
[OTP] 26 bit read: 0x1
[OTP] NANTIRBK0 bit reading: start
[OTP] NANTIRBK0: 3 bit
[OTP] 28 bit read: 0x1
[OTP] 29 bit read: 0x0
[OTP] 30 bit read: 0x1
[OTP] 25 bit read: 0x1
[OTP] ETC value: 0
[EFUSE] SMC Read the 0x0 ...
[EFUSE] SMC Read Count value: 3
[EFUSE] SMC Read the 0x1 ...
[EFUSE] SMC Read Count value: 1
[EFUSE] SMC Read the 0x2 ...
[EFUSE] SMC Read Count value: 0
[EFUSE] SMC Read the 0x3 ...
[EFUSE] SMC Read Count value: 1
(1,5) vs (1,5)
[EFUSE] This is commercial device.
set_tzpc_secureport: successfully protected 0
eSE Protection!!
Authenticated data read request (Swapped)
Authenticated data read response (Swapped)
RPMB: get hmac value: success
HMAC compare success !!
update_rpmb_version skip.
initialize_secdata_rpmb: usable! (0x52504d42)
DDR SIZE: 3G (0xc0000000)
LPDDR4 manufacturer : Micron
bin2_efuse = 0
[TMU] 52, 53, 51, 51
UFS vendor: SAMSUNG
FW rev : 0200
product : KLUBG4G1BD-E0B1
UFS size (GB) : 32
UFS ID : XXXXXXXXXXXXXXXX
lun:196 Query Response : 0xfc
lun:196 Query Response : 0xfc
lun:196 Query Response : 0xfc
lun:196 Query Response : 0xfc
dNumAllocUnits error at LU7 0 0
PROVISION : FAIL
PROVISION : FAIL
max77843_muic_api_print_init_regs: INTMASK[1:0x00, 2:0x00, 3:0x00]
max77843_muic_api_print_init_regs: MUIC: CDETCTRL:0x2d
max77843_muic_api_print_init_regs: MUIC: CONTROL1:0x00
max77843_muic_api_print_init_regs: MUIC: CONTROL2:0x3b
max77843_muic_api_print_init_regs: MUIC: CONTROL3:0x00
max77843_muic_api_print_init_regs: MUIC: CONTROL4[0x16]:0xb2
init_ific : MAX77843(0)
init_ific : MAX77843(0)
set_float_voltage: max77843 battery cv voltage 0x9c
set_charger_state: buck(1), chg(1), reg(0x05)
max77843_get_charger_status: Invalid charger
set_auto_current: get_charger_status(0)
max77843_muic_get_adc_value: STATUS1:0x1f
max77843_muic_get_adc_value: ADC:0x1f
max77843_muic_get_chg_typ: STATUS2:0x00
max77843_muic_get_chg_typ: CHGTYP:0x00
max77843_muic_get_adc_value: STATUS1:0x1f
max77843_muic_get_adc_value: ADC:0x1f
max77843_muic_get_chg_typ: STATUS2:0x00
max77843_muic_get_chg_typ: CHGTYP:0x00
get_wireless_charger_detect: wireless check 0
get_wireless_charger_detect : CHG_DTLS(0x00)
set_auto_current: unknown_state, curr(475)
max77843_get_charger_status: Invalid charger
get_wireless_charger_detect: wireless check 0
get_wireless_charger_detect : CHG_DTLS(0x00)
set_charger_current: chg curr(137), in curr(0)
max77843_get_charger_status: Invalid charger
get_wireless_charger_detect: wireless check 0
get_wireless_charger_detect : CHG_DTLS(0x00)
fuelguage : wpc_status(0)
set_charger_state: buck(1), chg(0), reg(0x04)
init_fuel_gauge: Start!!
init_fuel_gauge : MAX77843(0)
max77843_muic_get_adc_value: STATUS1:0x1f
max77843_muic_get_adc_value: ADC:0x1f
adc_read_temp temp_adc = 1852
init_fuel_gauge temp = 25
init_fuel_gauge : MAX77843(0)
init_fuel_gauge: Battery type : SDI, capacity: 5177, status: 128
init_fuel_gauge: Already initialized (0x1439, SDI type)
check_validation_with_tablesoc: Start!!
fuel_gauge_read_soc: SOC(32), data(0x209a)
fuel_gauge_read_ocv: VFOCV(3774), data(0xbcba)
calculate_table_soc : low(0) high(6) mid(7) table_soc(0)
calculate_table_soc : low(4) high(6) mid(3) table_soc(0)
calculate_table_soc : low(6) high(6) mid(5) table_soc(0)
calculate_table_soc : low(7) high(6) mid(6) table_soc(0)
calculate_table_soc: vcell [3774] table_soc [31]
differ(1), table_soc(31), RepSOC(32)
max77843_muic_get_adc_value: STATUS1:0x1f
max77843_muic_get_adc_value: ADC:0x1f
max77843_muic_get_chg_typ: STATUS2:0x00
max77843_muic_get_chg_typ: CHGTYP:0x00
fuel_gauge_read_vcell: VCELL(3716), data(0xb9d8)
vcell(3716),soc_diff_limit(50), low_temp_reset(0)
fuel_gauge_read_ocv: VFOCV(3774), data(0xbcba)
fuel_gauge_read_vcell: VCELL(3716), data(0xb9d8)
fuel_gauge_read_soc: SOC(32), data(0x209a)
fuel_gauge_read_vfsoc: VFSOC(30), data(0x1ef3)
init_fuel_gauge : OCV(3774), VCELL(3716), SOC(32), VFSOC(30)
AP_PMIC_SDA = 1
PMIC_ID = 0x12
OTP:0x78 PWR_SEQ:1 G3D_OCP:1 PSoff:1 INT_Volt:1
PMIC_STATUS1 = 0x2f PWRON JIGONB ACOKB MR2B PWRON1S
PMIC_STATUS2 = 0x11 RTC60SE RTC1SE
PMIC_PWRONSRC = 0x08 MRST
PMIC_OFFSRC = 0x00
PMIC_INT1 = 0xc3 PWRONF PWRONR PWRON1S MRB
PMIC_INT2 = 0x11 RTC60S RTC1S
PMIC_INT3 = 0x80 RSVD
PMIC_RTC_CTRL = 0x02
PMIC_RTC_SMPL = 0x83
RTC TIME: 2016-08-13 07:27:29(0x40)AM
s5p_check_keypad: 0x10110000
s5p_check_keypad: recovery mode
set_oneshot_recovery: recovery mode set! sys_bootm=0x80000
s5p_check_reboot_mode: INFORM3 = 0 ... skip
ATLAS_PLL = 1200MHz APOLLO_PLL = 1200MHz MIF_PLL = 3104MHz
MFC_PLL = 468MHz CCI_PLL = 532MHz
BUS0_PLL = 1600MHz BUS1_PLL = 668MHz
board_uart_rustproof ifc_sense: 0
-user build & not FAC
-rustproof mode Enabled
s5p_check_upload: MAGIC(0x4000000), RST_STAT(0x10000)
max77843_muic_get_adc_value: STATUS1:0x1f
max77843_muic_get_adc_value: ADC:0x1f
s5p_check_upload: debug level is LO! (mask: 0x220)
max77843_ific_set_mrstb: TOPSYS: MAINCTRL1[0x02]: [0x07]+[0x07]->[0x07]
s5p_check_upload: disable dump_gpr
max77843_muic_get_adc_value: STATUS1:0x1f
max77843_muic_get_adc_value: ADC:0x1f
s5p_check_download: 0
max77843_muic_get_adc_value: STATUS1:0x1f
max77843_muic_get_adc_value: ADC:0x1f
max77843_get_charger_status: Invalid charger
get_wireless_charger_detect: wireless check 0
get_wireless_charger_detect : CHG_DTLS(0x00)
check_pm_status: charger is not detected
fuel_gauge_read_vcell: VCELL(3718), data(0xb9ea)
check_pm_status: voltage(3718) is ok
check_pm_status: 7 sec reset, continue.
scr_draw_image: draw 'logo.jpg'...
read 'logo.jpg'(112504) completed.
board_set_dev_pm: s2mpb02 enable for display
42, 0, 13, 0x420013
DETECTED LCD TYPE : S6E3HA2
mipi-dsi driver(CMD mode) has been probed.
decon-int: ver0, max win7, command mode, hw trigger
single dsi mode
decon0 registered successfully
afw flag is Unknown [afw flag : 00 00 00 00]
secure info base: 45720000 and SMC Num = 0x83000013
secure smc success!!! [ret = 0]
Set debug level to low(4f4c)
DMV: Successfully informed TZ of boot mode: Recovery
load_kernel: loading boot image from 139264..
kernel size = 0x114f000, ramdisk size = 0x5fc000
dt_size:1454080, dt_actual:1454080
Verify_Binary_Signature 0x45720120 [email protected], [email protected]
Kernel Image
Verify_Binary_Signature: failed.(-18022398)
pit_check_signature (RECOVERY) invalid.
[TIMA trusted boot]: SEANDROID ENFORCING
Set invalid sign flag
No need to update kernel type.
[EFUSE] warranty bit is already set.
ace_hash_sha_digest: passed.(0)
tboot ctx base: 45720248
SMC Num = 0x83000001
mobismc success!!! [ret = 0]
SMC Num = 0x83000007
mobismc for tima info success!!! [ret = 0]
Pass. DTBH size is smaller than a page.
<dtbh_header Info>
magic:0x48425444, version:0x00000002, num_entries:0x00000008
<device info>
chip_id: 0x00001cfc
platform_id: 0x000050a6
subtype_id: 0x217584da
hw_rev: 0x0000000b
dt_entry[06]
chip_id: 0x00001cfc
platform_id: 0x000050a6
subtype_id: 0x217584da
hw_rev: 0x0000000a
hw_rev_end: 0x0000000b
offset: 0x0010a000
dtb size: 0x0002c800
Selected entry hw_ver : 11
dt_entry of hw_rev 10 is loaded at 0x4a000000.(182272 Bytes)
[EFUSE] RB count: device(0x3), binary(0x3)
[OTP] SW LOCK Success
DDI value :0x0000000f
sw_lock success
sw_lock success
Forced Enable KAP
Warranty Bit Set - Blowing KAP_VIOLATION_FUSE
KAP status = 5afe0003
ATAG_CORE: 5 54410001 0 0 0
ATAG_MEM: 4 54410002 20000000 40000000
ATAG_MEM: 4 54410002 20000000 60000000
ATAG_MEM: 4 54410002 20000000 80000000
ATAG_MEM: 4 54410002 20000000 A0000000
ATAG_MEM: 4 54410002 20000000 C0000000
ATAG_MEM: 4 54410002 1E800000 E0000000
ATAG_SERIAL: 4 54410006 XXXXXXXX XXXXXXXX
ATAG_INITRD2: 4 54420005 43000000 5fbd8f
ATAG_REVISION: 3 54410007 b
check_rustproof [0,0] On
ucs flag is Unknown
ucs flag : 00 00 00 00
ATAG_CMDLINE: f0 54410009 'console=ram loglevel=4 bootmode=2 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.hardware=samsungexynos7420 androidboot.debug_level=0x4f4c ess_setup=0x46000000 [email protected] [email protected] charging_mode=0x3000 s3cfb.bootloaderfb=0xe2a00000 sysscope=0x6b090719 lcdtype=4325395 consoleblank=0 lpj=239616 sec_debug.reset_reason=5 ehci_hcd.park=3 oops=panic pmic_info=35 cordon=c34c0eba5576148dc662cf43a6352c3b connie=SM-G920F_OPEN_EUR_c3811d70601ea690b7b0b2afca80be2c fg_reset=0 androidboot.emmc_checksum=3 androidboot.boot_salescode= androidboot.odin_download=1 androidboot.bootloader=G920FXXU3DPDP androidboot.selinux=enforcing androidboot.security_mode=1526595585 androidboot.ucs_mode=0 androidboot.hw_rev=11 androidboot.warranty_bit=1 androidboot.hmac_mismatch=0 androidboot.sec_atd.tty=/dev/ttySAC1 androidboot.serialno=XXXXXXXXXXXXXXXX snd_soc_core.pmdown_time=1000 zero_sdchg_ic=0 androidboot.fmp_config=0'
ATAG_NONE: 0 0
pack_atags: ramdisk size start 0x43000000, size 0x5fbd8f
Updating device tree @0x4a000000: done
Starting kernel at 0x40205000...
SWITCH_SEL(3)
BOOTING TIME : 2895
Here it is, mate. I can't seem to find anything suspicious besides
Code:
dNumAllocUnits error at LU7 0 0
PROVISION : FAIL
PROVISION : FAIL
but I can only guess

Hi I am having problems compiling due to the kernel. Which kernel source should I use? How should I configure it? Help pleaase

Added "extract files" guide.

Whenever I try to download the CyanogenMod repo, I get this error:
error: Exited sync due to fetch errors
I've tried using: repo sync -f and: repo sync --force-sync
I'm trying to download the CM13 repo.
I've also followed the steps exactly as they were written.

I'm trying to build cm-14.0. Fails at
HTML:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/julian/android/system/out/target/product/zerofltexx/obj_arm/SHARED_LIBRARIES/libsecril-client_intermediates/export_includes', needed by '/home/julian/android/system/out/target/product/zerofltexx/obj_arm/SHARED_LIBRARIES/audio.primary.universal7420_intermediates/import_includes', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/julian/android/system'
.
Any ideas what could be wrong?
/android/system/kernel/samsung/exynos7420 contains github.com/CyanogenMod/android_kernel_samsung_exynos7420 cm-14.0.
Thanks for the great guide anyway

[Guide] Mate 9 Flash and DDR Info

Steps:
A. Unlock bootloader and install TWRP 3.0.3-1.
B. Run TWRP and connect usb cable.
C. Download HWDev_2017042201.zip
D. Run "hwdev.bat" and it will use keyword search kernel log for Flash and DDR info

I got my mate 9 info
Flash: TOSHIBA THGBF7T0L8LBATAC
DDR: lpddr4

What kind of DDR info do you expect from the kernel ?
The most obvious one:
Code:
HWMHA:/data/data # cat /proc/ddr_rod
lpddr3
HWMHA:/data/data # cat /proc/ddr_info
ddr_info:
0x401
And your method will report
Code:
ddr: current logic version is lpddr4 verison !!!
The lowlevel flash specs (SAMSUNG KLUCG4J1EB-B0B1):
Code:
HWMHA:/data/data # cat /sys/kernel/debug/ufs/dump_device_desc
Device Descriptor[Byte offset 0x0]: bLength = 0x40
Device Descriptor[Byte offset 0x1]: bDescriptorType = 0x0
Device Descriptor[Byte offset 0x2]: bDevice = 0x0
Device Descriptor[Byte offset 0x3]: bDeviceClass = 0x0
Device Descriptor[Byte offset 0x4]: bDeviceSubClass = 0x0
Device Descriptor[Byte offset 0x5]: bProtocol = 0x0
Device Descriptor[Byte offset 0x6]: bNumberLU = 0x4
Device Descriptor[Byte offset 0x7]: bNumberWLU = 0x4
Device Descriptor[Byte offset 0x8]: bBootEnable = 0x1
Device Descriptor[Byte offset 0x9]: bDescrAccessEn = 0x0
Device Descriptor[Byte offset 0xa]: bInitPowerMode = 0x1
Device Descriptor[Byte offset 0xb]: bHighPriorityLUN = 0x7f
Device Descriptor[Byte offset 0xc]: bSecureRemovalType = 0x0
Device Descriptor[Byte offset 0xd]: bSecurityLU = 0x1
Device Descriptor[Byte offset 0xe]: Reserved = 0x4
Device Descriptor[Byte offset 0xf]: bInitActiveICCLevel = 0x0
Device Descriptor[Byte offset 0x10]: wSpecVersion = 0x2
Device Descriptor[Byte offset 0x12]: wManufactureDate = 0x1610
Device Descriptor[Byte offset 0x14]: iManufactureName = 0x0
Device Descriptor[Byte offset 0x15]: iProductName = 0x1
Device Descriptor[Byte offset 0x16]: iSerialNumber = 0x2
Device Descriptor[Byte offset 0x17]: iOemID = 0x3
Device Descriptor[Byte offset 0x18]: wManufactureID = 0xce01
Device Descriptor[Byte offset 0x1a]: bUD0BaseOffset = 0x10
Device Descriptor[Byte offset 0x1b]: bUDConfigPLength = 0x10
Device Descriptor[Byte offset 0x1c]: bDeviceRTTCap = 0x2
Device Descriptor[Byte offset 0x1d]: wPeriodicRTCUpdate = 0x0

user4774 said:
What kind of DDR info do you expect from the kernel ?
The most obvious one:
Code:
HWMHA:/data/data # cat /proc/ddr_rod
lpddr3
Click to expand...
Click to collapse
No, it's incorrect.
Someone post source code, if it don't specify ddr type and it return default value "lpddr3".
DDR source code

mankindtw said:
No, it's incorrect.
Someone post source code, if it don't specify ddr type and it return default value "lpddr3".
Click to expand...
Click to collapse
OK. So this 'lpddr3' is printed based on the /proc/ddr_info value (DDR_TYPE_ADDR&0x00000FFF)
which is the "real" one. Do you have the same 0x401 value ? Our flash chips are obviously from different manufacturers.
Code:
current_bootloader_log: ddr info 0x00000401
While we are at the possible hardware variations: there are 5 LCD panels supported by the kernel:
Code:
JDI_R63452_6P0
JDI_NT35695_CUT3_1
LG_TD4322_6P0
LG_ER69006A
SHARP_TD4322_6P0
I have LG_TD4322_6P0.
This info is also visible on the kernel commandline
Code:
boardid=0x00001585 productid=0x3a001414 ufs_product_name=KLUCG4J1EB-B0B1 LCD_ID=0

user4774 said:
OK. So this 'lpddr3' is printed based on the /proc/ddr_info value (DDR_TYPE_ADDR&0x00000FFF)
which is the "real" one. Do you have the same 0x401 value ? Our flash chips are obviously from different manufacturers.
Click to expand...
Click to collapse
I have same lpddr3 from /proc/ddr_rod, but couple of kernel log message show lpddr4.

1. Can you post command to get info about ROM type? Ufs and version or eMMC and version. I want stop hysteria about memory types and don't trust benchmarks.
2. It would be great if somebody will post command to get info about display. 5 different displays is interesting fact

5[Strogino] said:
1. Can you post command to get info about ROM type? Ufs and version or eMMC and version.
Click to expand...
Click to collapse
The lsscsi command is not included in busybox, so you need to peek yourself in /sys/bus/scsi
Code:
HWMHA:/data/data # cat /sys/bus/scsi/devices/0:0:0:0/vendor
SAMSUNG
HWMHA:/data/data # cat /sys/bus/scsi/devices/0:0:0:0/model
KLUCG4J1EB-B0B1
HWMHA:/data/data # cat /proc/ddr_info
ddr_info:
0x401
2. It would be great if somebody will post command to get info about display. 5 different displays is interesting fact
Click to expand...
Click to collapse
This is more tricky. The grep panel_probe /splash2/kmsg_log provides such output:
Code:
display: [display]mipi_lg_panel_probe_TD4322: hisilicon,mipi_lg_TD4322_6P0
display: [display]mipi_lg_panel_probe_TD4322: lcd_bl_type=4!
display: [display]mipi_lg_panel_probe_TD4322: pxl_clk_rate=146 M
display: [display]mipi_lg_panel_probe_TD4322: lcd_bl_ic_name=LM36923YFFR!
display: [display]mipi_lg_panel_probe_TD4322: v_back_porch=28
display: [display]mipi_lg_panel_probe_TD4322: v_pulse_width=8
display: [display]mipi_lg_panel_probe_TD4322: lcd-vddio-type=1
display: [display]mipi_lg_panel_probe_TD4322: gpio_lcd_vddio = 67
display: [display]mipi_lg_panel_probe_TD4322: lcd_support_dynamic_gamma = 1
display: [display]mipi_lg_panel_probe_TD4322: hisifb_write_gm_to_reserved_mem has some problem!
The framebuffer driver is buggy too, and needs some patching :crying: RGB565 and geometry are ok.
Code:
HWMHA:/data/data # fbset -fb /dev/graphics/fb0
mode "1080x1920-0"
# D: 0.007 MHz, H: 0.006 kHz, V: 0.003 Hz
geometry 1080 1920 1080 5760 16
timings 146000000 23 50 28 14 20 8
accel false
rgba 5/11,6/5,5/0,0/0
endmode

user4774 said:
The lsscsi command is not included in busybox, so you need to peek yourself in /sys/bus/scsi
This is more tricky. The grep panel_probe /splash2/kmsg_log provides such output:
Click to expand...
Click to collapse
Thanks. I have same chip Samsung KLUCG4J1EB-B0B1
But display is different:
Code:
[display]mipi_jdi_panel_probe_R63452: hisilicon,mipi_jdi_R63452_6P0
[display]mipi_jdi_panel_probe_R63452: lcd_bl_type=4!
[display]mipi_jdi_panel_probe_R63452: lcd_bl_ic_name=LM36923YFFR!
[display]mipi_jdi_panel_probe_R63452: pxl_clk_rate=146 M
[display]mipi_jdi_panel_probe_R63452: v_back_porch=28
[display]mipi_jdi_panel_probe_R63452: v_pulse_width=8
[display]mipi_jdi_panel_probe_R63452: lcd-vddio-type=1
[display]mipi_jdi_panel_probe_R63452: gpio_lcd_vddio = 67
[display]mipi_jdi_panel_probe_R63452: lcd_support_dynamic_gamma = 1

Flash: SAMSUNG KLUCG4J1EB-B0B1
DDR: lpddr4

sashimiyarou said:
Flash: SAMSUNG KLUCG4J1EB-B0B1
DDR: lpddr4
Click to expand...
Click to collapse
What's about display?

mankindtw said:
I got my mate 9 info
Flash: TOSHIBA THGBF7T0L8LBATAC
DDR: lpddr4
Click to expand...
Click to collapse
I have a Toshiba also different model THGBF7G9L4LBATRC but can't find any information on it. How do we know if it's UFS 2.1 or 2.0?
EDIT: There a chart here https://www.gizmochina.com/2017/04/...-ufs-2-1-description-official-mate-9-website/
The Samgsung model at least has an info page on it. It's UFS 2.0.
http://www.samsung.com/semiconductor/products/flash-storage/ufs/KLUDG8J1CB-B0B1?ia=2413

So, is it already evidence that we were cheated and that Mate 9 exists with UFS 2.0? That's why they erased that specification from their website.
Enviado desde mi MHA-L09 mediante Tapatalk

XoanCarlos said:
So, is it already evidence that we were cheated and that Mate 9 exists with UFS 2.0? That's why they erased that specification from their website.
Enviado desde mi MHA-L09 mediante Tapatalk
Click to expand...
Click to collapse
Yes. My Mate 9 has UFS 2.0 Toshiba flash.

Tikerz said:
Yes. My Mate 9 has UFS 2.0 Toshiba flash.
Click to expand...
Click to collapse
One word: deception. Now I understand erasing this specification of your website, at least here, in Spain.
Enviado desde mi MHA-L09 mediante Tapatalk

Tikerz said:
I have a Toshiba also different model THGBF7G9L4LBATRC but can't find any information on it. How do we know if it's UFS 2.1 or 2.0?
EDIT: There a chart here https://www.gizmochina.com/2017/04/...-ufs-2-1-description-official-mate-9-website/
The Samgsung model at least has an info page on it. It's UFS 2.0.
http://www.samsung.com/semiconductor/products/flash-storage/ufs/KLUDG8J1CB-B0B1?ia=2413
Click to expand...
Click to collapse
Maybe you didn't realize, but the Samsung model the other user posted is: KLUCG4J1EB-B0B1, and the one in your link is KLUDG8J1CB-B0B1. I tried to google the model number and google just automatically redirected to this different number.

mankindtw said:
Steps:
A. Unlock bootloader and install TWRP 3.0.3-1.
B. Run TWRP and connect usb cable.
C. Download HWDev_2017042201.zip
D. Run "hwdev.bat" and it will use keyword search kernel log for Flash and DDR info
Click to expand...
Click to collapse
toshiba UFS2.0
THGBF7....
KLU?G......
H28U.......

5[Strogino said:
;72030020]What's about display?
Click to expand...
Click to collapse
panel_lcd_lg_TD4322_6P0

They fit different ufs on our mate-thats a fact i have ifs 2.0 but i understand that other hardware like lcd is also different on some phones my lcd is JDI_R63452_6P0_LCD
I searched over other forums that many peoples have various touch screen isues regarding to model, so is that ufs big deal if we couldnt compare all phones with all hardware combinations? Better ufs, but worse lcd, worse lcd but better ufs or all things best/worst ;p

sashimiyarou said:
panel_lcd_lg_TD4322_6P0
Click to expand...
Click to collapse
Is it enough to run?
Code:
find /sys/devices/platform -type d -name "panel_lcd*"