[DEV] LineageOS bring-up thread for Lenovo P2 [P2a42]

ilmervanhattem · Jan 19, 2017 at 4:39 PM

wzedlare said:
What about this one?

https://mega.nz/#!fkUTlIpI!Ql1hS26vVYbXVMu8xPiYmz6YKiE1SKYTRVxoJ9BL-XY

Code:

C:\P2a42-Root>fastboot boot recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [  0.568s]
booting...
OKAY [  0.516s]
finished. total time: 1.086s

NOT BOOTING ANYTHING

ForgottenDude · Jan 21, 2017 at 7:36 AM

Hello, @wzedlare, how is CM coming along for this P2?

I am NOT asking for an ETA. I am going to buy a new phone, and currently looking at the Lenovo P2 and the Redmi Note 4 snapdragon version. Considering I am on XDA, my huge priority is custom rom support (although Lenovo is close to stock android as compared to RN4). I am leaning towards the P2 due to the S-AMOLED screen, bigger battery, almost stock android feel, easier bootloader unlock procedure, etc.

So, how is it coming along? I don't mind if it takes a month or something, lol, but if there is a possibility that we will have CM for this device, I'll go ahead and buy this. Because, let's face it, I don't think Lenovo will provide much updates.

wzedlare · Jan 21, 2017 at 7:47 AM

ForgottenDude said:
Hello, @wzedlare, how is CM coming along for this P2?

I am NOT asking for an ETA. I am going to buy a new phone, and currently looking at the Lenovo P2 and the Redmi Note 4 snapdragon version. Considering I am on XDA, my huge priority is custom rom support (although Lenovo is close to stock android as compared to RN4). I am leaning towards the P2 due to the S-AMOLED screen, bigger battery, almost stock android feel, easier bootloader unlock procedure, etc.

So, how is it coming along? I don't mind if it takes a month or something, lol, but if there is a possibility that we will have CM for this device, I'll go ahead and buy this. Because, let's face it, I don't think Lenovo will provide much updates.

CM is waiting for my oem unlock, I am waiting for lenovo's meaningless 14 days to unlock it.

ForgottenDude · Jan 21, 2017 at 10:06 AM

wzedlare said:
CM is waiting for my oem unlock, I am waiting for lenovo's meaningless 14 days to unlock it.

Ooh, that's right. Yours will be unlocked tomorrow, I think (going from the 1st post in previous page).

Yes, the 14 days wait is weird, especially considering Moto doesn't do that. It's still better than Xiaomi's, lol.

ilmervanhattem · Jan 22, 2017

ilmervanhattem · Jan 22, 2017 at 9:40 AM

Restored system and data from two different twrp-backups, but now device says wrong pin (also tried 0000 and 1234). Anybody know why this happens and how to fix it?

wzedlare · Jan 22, 2017 at 9:43 AM

ilmervanhattem said:
Restored system and data from two different twrp-backups, but now device says wrong pin (also tried 0000 and 1234). Anybody know why this happens and how to fix it?

Try to restore cache, dalvik-cache and dalvik/art parts from your data backup

ilmervanhattem · Jan 22, 2017

wzedlare said:
Try to restore cache, dalvik-cache and dalvik/art parts from your data backup

There is no dalvik-cache or dalvik/art part in my TWRP (?) Or do I have to do it manually? How? :good:

I only backed up DATA

wzedlare · Jan 22, 2017 at 9:57 AM

ilmervanhattem said:
There is no dalvik-cache or dalvik/art part in my TWRP (?) Or do I have to do it manually? How? :good:

There must be

or I remember their names wrongly, I will tell you after 2 hours(I will flash twrp and check)

ilmervanhattem · Jan 22, 2017

wzedlare said:
There must be or I remember their names wrongly, I will tell you after 2 hours(I will flash twrp and check)

Now extracting the Apps from TWRP-backup using Titanium Backup...
Did not work!

None of my twrp-backups are working, while before they did (exactly the same)

Reinstalled everything, no solution

wzedlare · Jan 22, 2017 at 7:57 PM

For those who are curious; Cm13 reboots itself when starting apps at optimization screen.I will try to fix this issue tomorrow, I'm busy right now

maxysoft · Jan 22, 2017

Sorry but I have not received any notification even though I was subscribed to the thread :/ I am also available for testing and I can confirm that the phone reboots at the optimization screen

ilmervanhattem said:
Restored system and data from two different twrp-backups, but now device says wrong pin (also tried 0000 and 1234). Anybody know why this happens and how to fix it?

Go into /data/system and delete locksetting.db

edit. none of the recovery you provided boots @wzedlare

wzedlare · Jan 22, 2017 at 8:35 PM

maxysoft said:
Sorry but I have not received any notification even though I was subscribed to the thread :/ I am also available for testing and I can confirm that the phone reboots at the optimization screen

Go into /data/system and delete locksetting.db

edit. none of the recovery you provided boots @wzedlare

Thanks for your efforts, my oem is unlocked now.I will inform everyone in this thread whenever I take a successful step.

Kicroy · Sep 8, 2015 56 3 0

To the guys who work on customs for the P2 or who have some knowledge, can we expect few custom officially supported, or this would be too complex/not interesting enough?

maxysoft · Jan 22, 2017 at 8:53 PM

Kicroy said:
To the guys who work on customs for the P2 or who have some knowledge, can we expect few custom officially supported, or this would be too complex/not interesting enough?

The problem is that this phone is very little known so developers are not interested in the development. The P2 have good performance and overall good hw but only few people know that it exists, so the "main" developers should not fiddle with it

wzedlare · Jan 24, 2017

I uploaded new build.Lineage reboots itself because I couldn't configure modem files well.Frankly, I couldn't figure out the exact source of the fatal error of modem.

Related lines from logs:

Code:

[   13.111098] sysmon-qmi: sysmon_clnt_svc_arrive: Connection established between QMI handle and modem's SSCTL service

[   13.137368] Fatal error on the modem.

[   13.137389] modem subsystem failure reason: fs_device_efs_rmts.c:175:Invalid shared ram address from Apps.

[   13.137395] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = RELATED.

[   13.138615] IPA received MPSS BEFORE_SHUTDOWN

[   13.138634] ipa ipa_uc_state_check:301 uC is not loaded

[   13.138637] ipa ipa_uc_state_check:301 uC is not loaded

[   13.141444] rmnet_ipa started deinitialization

[   13.141448] ipa ipa2_teardown_sys_pipe:1416 bad parm.

[   13.141452] ipa-wan ipa_wwan_remove:2111 Failed to teardown IPA->APPS pipe

[   13.141604] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rmnet_ipa0

[   13.200148] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rmnet_ipa0

[   13.200188] ipa-wan ipa_del_dflt_wan_rt_tables:377 Deleting Route hdl:(0x9) with ip type: 0

[   13.200675] ipa-wan ipa_del_dflt_wan_rt_tables:386 Deleting Route hdl:(0xb) with ip type: 1

[   13.200862] rmnet_ipa completed deinitialization

[   13.200949] IPA BEFORE_SHUTDOWN handling is complete

[   13.200957] subsys-restart: subsystem_shutdown(): [ffffffc0aa00b000]: Shutting down modem

[   13.300987] pil-q6v5-mss 4080000.qcom,mss: Port ffffff8001d72000 halt timeout

[   13.401059] pil-q6v5-mss 4080000.qcom,mss: Port ffffff8001d74000 halt timeout

[   13.402534] IPA received MPSS AFTER_SHUTDOWN

[   13.402558] ipa ipa_q6_post_shutdown_cleanup:2025 uC is not loaded, won't reset Q6 pipes

[   13.402563] IPA AFTER_SHUTDOWN handling is complete

[   13.404125] M-Notify: General: 4

[   13.404572] IPA received MPSS BEFORE_POWERUP

[   13.405183] IPA BEFORE_POWERUP handling is complete

[   13.405190] subsys-restart: subsystem_powerup(): [ffffffc0aa00b000]: Powering up modem

[   13.405321] pil-q6v5-mss 4080000.qcom,mss: modem: loading from 0x0000000086c00000 to 0x000000008c200000

[   13.408068] M-Notify: General: 6

[   13.409202] pil-q6v5-mss 4080000.qcom,mss: Debug policy not present - msadp. Continue.

[   13.409749] pil-q6v5-mss 4080000.qcom,mss: Loading MBA and DP (if present) from 0x00000000f3c00000 to 0x00000000f3d00000

[   13.484357] pil-q6v5-mss 4080000.qcom,mss: MBA boot done

[   13.542627] device-mapper: table: 253:0: crypt: IV mechanism required

[   13.542635] device-mapper: ioctl: error adding target to table

[   13.907974] pil-q6v5-mss 4080000.qcom,mss: modem: Brought out of reset

[   13.991242] pil-q6v5-mss 4080000.qcom,mss: Subsystem error monitoring/handling services are up

[   13.991247] pil-q6v5-mss 4080000.qcom,mss: modem: Power/Clock ready interrupt received

[   13.991915] IPA received MPSS AFTER_POWERUP

[   13.992295] M-Notify: General: 7

[   13.992485] rmnet_ipa started initialization

[   13.992489] IPA SSR support = True

[   13.992491] IPA ipa-loaduC = True

[   13.992494] IPA SG support = True

[   13.994621] rmnet_ipa completed initialization

[   13.995072] IPA AFTER_POWERUP handling is complete

[   13.995079] subsys-restart: subsystem_restart_wq_func(): [ffffffc0aa00b000]: Restart sequence for modem completed.

Modem resets itself because if this failure.If you know how to fix, please tell me.You can try to fix it, I linked new build in thread.I am also trying to fix it.I attached logcat and dmesg.

maxysoft · Jan 23, 2017 at 6:26 PM

wzedlare said:
I uploaded new build.Lineage reboots itself because I couldn't configure modem files well.Frankly, I couldn't figure out the exact source of the fatal error of modem.

Related line from logs:

Code:

modem subsystem failure reason: fs_device_efs_rmts.c:175:Invalid shared ram address from Apps.

Modem resets itself because if this failure.If you know how to fix, please tell me.You can try to fix it, I linked new build in thread.I am also trying to fix it.I attached logcat and dmesg.

Hi I've downloaded the new zip but the logcat at boot isn't working

wzedlare · Jan 24, 2017 at 8:54 AM

maxysoft said:
Hi I've downloaded the new zip but the logcat at boot isn't working

You need to open boot.img with Android Image Kitchen and edit related ramdisk/default.prop lines.Then it will start to take logs.

Code:

ro.adb.secure=0
ro.secure=0
persist.sys.usb.config=adb

The Mero · Jan 24, 2017 at 2:45 PM

Lenovo Logger

don't know if this is any use guys , built into phone . from dial pad enter ####3333# .. lenovo logger

maxysoft · Jan 24, 2017

wzedlare said:
You need to open boot.img with Android Image Kitchen and edit related ramdisk/default.prop lines.Then it will start to take logs.

Code:

ro.adb.secure=0 ro.secure=0 persist.sys.usb.config=adb

After changing some files I have a different error:

http://pastiebin.com/embed/58877fa0a0ec8

edit. ok no same error.. I looked the dmesg

[DEV] LineageOS bring-up thread for Lenovo P2 [P2a42]

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Senior Member