TWRP 3.0.2 recovery port for X5+ and LEM5

Here is a bit from a SuperSU crash log

SPOILER: Click to show
SPOILER: Click to show
D/PowerManagerNotifier( 753): onUserActivity: event=2, uid=1000 V/SettingsInterface( 753): from settings cache , name = screen_on_by_sensor , value = 0 I/BufferQueueProducer( 199): [Application Error: eu.chainfire.supersu](this:0xb 75a8980,id:73,api:2,p:753,c:199) queueBuffer: fps=3.01 dur=5319.61 max=5069.95 m in=14.39 D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400) V/SettingsInterface( 753): from settings cache , name = screen_on_by_sensor , value = 0 I/BufferQueueProducer( 199): [FrameBufferSurface_0](this:0xb75306a8,id:0,api:1, p:199,c:199) queueBuffer: fps=3.01 dur=5321.30 max=5068.93 min=16.50 I/SurfaceFlinger( 199): [Built-in Screen (type:0)] fps:3.059640,dur:5556.21,max :5069.02,min:16.50 D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400) V/SettingsInterface( 753): from settings cache , name = screen_on_by_sensor , value = 0 D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400) V/SettingsInterface( 753): from settings cache , name = screen_on_by_sensor , value = 0 D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400) D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400) V/SettingsInterface( 753): from settings cache , name = screen_on_by_sensor , value = 0 D/InputReader( 753): AP_PROF:AppLaunch_dispatchPtr:Up:2030172, ID:0, Index:-119 2059856 I/PerfService( 753): PerfServiceNative_boostDisableAsync:5 I/libPerfService( 753): 5: set: 1 I/libPerfService( 753): 5: set freq: 0 V/SettingsInterface( 753): from settings cache , name = screen_on_by_sensor , value = 0 V/SettingsProvider( 753): call(system:sound_effects_enabled) for 0 D/SettingsProvider( 753): lookupValue table system cache contains Key sound_eff ects_enabled , value = Bundle[{value=0}] D/FeatureProxyBase( 753): FeatureProxyBase class constructor D/FeatureProxyBase( 753): getService(), serviceName = multiwindow_service_v1 V/WindowManager( 753): Changing focus from Window{3e9b7499 u0 Application Error : eu.chainfire.supersu EXITING} to Window{296fcd06 u0 com.android.launcher/com.a ndroid.launcher2.Launcher} Callers=com.android.server.wm.WindowManagerService.re moveWindowLocked:3056 com.android.server.wm.WindowManagerService.removeWindow:29 92 com.android.server.wm.Session.remove:193 android.view.ViewRootImpl.dispatchDe tachedFromWindow:3449 D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400) D/PhoneStatusBar( 880): setSystemUiVisibility vis=400 mask=ffffffff oldVal=0 ne wVal=400 diff=400 D/PhoneStatusBar( 880): hiding the MENU button D/FeatureProxyBase( 753): FeatureProxyBase class constructor D/FeatureProxyBase( 753): getService(), serviceName = multiwindow_service_v1 I/WindowManager( 753): Gaining focus: Window{296fcd06 u0 com.android.launcher/c om.android.launcher2.Launcher} D/Dialog ( 753): dismissDialog I/WindowManager( 753): Losing focus: Window{3e9b7499 u0 Application Error: eu.c hainfire.supersu EXITING} D/Dialog ( 753): handleMessage:{ when=0 what=67 obj=com.android.server.am.AppE rrorDialog$2@2221686c target=android.app.Dialog$ListenersHandler obj=com.android .server.am.AppErrorDialog$2@2221686c } I/Process ( 2750): Sending signal. PID: 2750 SIG: 9 D/AbsListView( 1312): onWindowFocusChanged: hasWindowFocus=true, this=com.androi d.launcher2.listapplist.MzListView{160dd33 VFED.VC. ........ 0,0-400,400 #7f0e00 77 app:id/main_menu_list} V/InputMethodManager( 1312): onWindowFocus: null softInputMode=288 first=false f lags=#1910500 V/InputMethodManagerService( 753): windowGainedFocus: android.os.BinderProxy@33 7dc69e controlFlags=#0 softInputMode=#120 windowFlags=#1910500 W/InputMethodManagerService( 753): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@25928e35 attribute=n ull, token = android.os.BinderProxy@341e0be1 D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400) D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400) D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400) D/GuiExt ( 255): [GuiExtS] binder of dump tunnel(RB-0xb8e7d7f0) died D/PowerManagerService( 753): handleWakeLockDeath: lock=462793959 [SuperSU Recei ver Wakelock] D/PowerManagerNotifier( 753): onWakeLockReleased: flags=805306378, tag="SuperSU Receiver Wakelock", packageName=eu.chainfire.supersu, ownerUid=10071, ownerPid= 2750, workSource=null D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400) D/DisplayManagerService( 753): Display listener for pid 2750 died. I/SurfaceFlinger( 199): EventThread Client Pid (2750) disconnected by (199) D/PowerManagerService( 753): userActivityNoUpdateLocked: eventTime=2030282, eve nt=0, flags=0x1, uid=10071 I/SurfaceFlinger( 199): EventThread Client Pid (2750) disconnected by (199) D/PowerManagerNotifier( 753): onUserActivity: event=0, uid=10071 I/SurfaceFlinger( 199): [SF client] DEL(0xb75a12f0) for (753:system_server) D/PowerManagerService( 753): updateWakeLockSummaryLocked: mWakefulness=Awake, m WakeLockSummary=0x0 D/PowerManagerService( 753): updateUserActivitySummaryLocked: mWakefulness=Awak e, mUserActivitySummary=0x9, nextTimeout=2033965 (in 3683 ms) D/PowerManagerService( 753): mDisplayPowerRequest.policy = 3 D/PowerManagerService( 753): isWfdEnabled() mWfdStatus=WifiDisplayStatus{featur eState=0, scanState=0, activeDisplayState=0, activeDisplay=null, displays=[], se ssionInfo=WifiDisplaySessionInfo: C/O:Client,GId:,Pp:,SId:0,IP:}, return false D/DisplayPowerController( 753): requestPowerState: policy=BRIGHT, useProximityS ensor=false, screenBrightness=102, screenAutoBrightnessAdjustment=0.0, useAutoBr ightness=false, blockScreenOn=false, lowPowerMode=false, boostScreenBrightness=f alse, dozeScreenBrightness=-1, dozeScreenState=UNKNOWN, waitForNegativeProximity =false I/PowerManagerService( 753): setBrightness mButtonLight, screenBrightness=102 D/PowerManagerService( 753): updateDisplayPowerStateLocked: mDisplayReady=true, policy=3, mWakefulness=1, mWakeLockSummary=0x0, mUserActivitySummary=0x9, mBoot Completed=true, mScreenBrightnessBoostInProgress=false D/PowerManagerService( 753): Releasing suspend blocker "PowerManagerService.Wak eLocks". I/ActivityManager( 753): Process eu.chainfire.supersu (pid 2750) has died D/ActivityManager( 753): SVC-handleAppDiedLocked: app = ProcessRecord{cfc7ca6 2 750:eu.chainfire.supersu/u0a71}, app.pid = 2750 D/ActivityManager( 753): SVC-mBroadcastQueues: com.android.server.am.BroadcastQ ueue@71f6cd8 D/ActivityManager( 753): SVC-mBroadcastQueues: com.android.server.am.BroadcastQ ueue@229b5831 D/FeatureProxyBase( 753): FeatureProxyBase class constructor D/FeatureProxyBase( 753): getService(), serviceName = multiwindow_service_v1 D/FeatureProxyBase( 753): FeatureProxyBase class constructor D/FeatureProxyBase( 753): getService(), serviceName = multiwindow_service_v1 D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400) I/Finsky ( 2471): [1] com.google.android.finsky.utils.by.onTrimMemory(2): Memor y trim requested to level 40 D/Surface ( 753): Surface::disconnect(this=0xb90e1ec0,api=2) D/GraphicBuffer( 753): unregister, handle(0xb90e0950) (w:400 h:400 s:400 f:0x1 u:0x000933) D/GraphicBuffer( 753): unregister, handle(0xb9039c68) (w:400 h:400 s:400 f:0x1 u:0x000933) I/BufferQueueProducer( 199): [Application Error: eu.chainfire.supersu](this:0xb 75a8980,id:73,api:2,p:-1,c:199) disconnect(P): api 2 I/BufferQueueConsumer( 199): [Application Error: eu.chainfire.supersu](this:0xb 75a8980,id:73,api:2,p:-1,c:199) getReleasedBuffers: returning mask 0xfffffffffff fffff D/GraphicBuffer( 199): free, handle(0xb759f150) (w:400 h:400 s:400 f:0x1 u:0x00 0933) D/GraphicBuffer( 199): free, handle(0xb758ec68) (w:400 h:400 s:400 f:0x1 u:0x00 0933) D/GraphicBuffer( 753): unregister, handle(0xb90e0530) (w:400 h:400 s:400 f:0x1 u:0x000933) D/Launcher( 1312): Launcher, onTrimMemory: level = 5 D/MALI

( 1312): _egl_make_current:857: [MALI] make current with display 0x1,
context 0x40000001, state 0xb8eee8e0
D/MALI

( 1312): _egl_make_current:872: [MALI] Map __dpy 0x1 to dpy 0xb8e26730

D/MALI

( 1312): _egl_make_current:906: [MALI] Map __ctx 0x40000001 to ctx 0xb
8eec850
D/FeatureProxyBase( 753): FeatureProxyBase class constructor
D/FeatureProxyBase( 753): getService(), serviceName = multiwindow_service_v1
D/FeatureProxyBase( 753): FeatureProxyBase class constructor
D/FeatureProxyBase( 753): getService(), serviceName = multiwindow_service_v1
I/BufferQueueConsumer( 199): [Application Error: eu.chainfire.supersu](this:0xb
75a8980,id:73,api:2,p:-1,c:-1) disconnect©
D/GraphicBuffer( 199): free, handle(0xb753e130) (w:400 h:400 s:400 f:0x1 u:0x00
0933)
I/BufferQueue( 199): [Application Error: eu.chainfire.supersu](this:0xb75a8980,
id:73,api:2,p:-1,c:-1) ~BufferQueueCore
D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400)
D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400)
D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400)
D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400)
D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400)
D/Surface ( 199): Surface::setBuffersDimensions(this=0xb7534b88,w=400,h=400)
D/FeatureProxyBase( 753): FeatureProxyBase class constructor
D/FeatureProxyBase( 753): getService(), serviceName = multiwindow_service_v1
^C

Added a new log, filtered to only SuperSu events, attached to this message.
Log created/filtered/exported with mLogcat  11 mai 2017 SU Filtered logcat.log (339.02 KB)

May 11, 2017 1:33:25 GMT 1 m47r1x said:
May 10, 2017 7:52:19 GMT 1 savi said:
Hello,

I confirm same behavior on a W618 with latest SU V2.79. Installation through TWRP.



The supplied scatter file in this thread is for MT6572 soc, but the W618 in the X5+ has an MT6580.

The files are mainly different in partitions and blocks.

I am wondering if that causes the problems with root and trying to find out.

Any info from you is highly appreciated.


The scatter file included in my release is the original file from stock firmware, just modified to load the custom named boot and recovery img. Here there are the lines from 6 to 10 of this scatter file:

- general: MTK_PLATFORM_CFG

info:

  • config_version: V1.1.2

platform: MT6580

project: w616_wgl
Please, next time check before telling your stories.
Thank you

May 10, 2017 14:45:00 GMT 1 insedere said:
Hello, possible to flash only twrp with flashify? On D5+ ? Best Regards

To use flashify you need to have root access, but are you able to gain root access before flashing the TWRP?

Even more, if you only flash the new recovery, it will be overwritten at first reboot, so I’m sorry, you need to follow the “standard” procedure.

May 11, 2017 9:34:03 GMT 1 Ciro Danise said:
May 10, 2017 14:45:00 GMT 1 insedere said:
Hello, possible to flash only twrp with flashify? On D5+ ? Best Regards

To use flashify you need to have root access, but are you able to gain root access before flashing the TWRP?

Even more, if you only flash the new recovery, it will be overwritten at first reboot, so I’m sorry, you need to follow the “standard” procedure.


hi ciro - thanks for answer,
i did the proper way to root - and it has root - only the old TWRP does not mount DATA. (override recovery deleted and flashed org boot.img)
so i will override TWRP with the newer one.
Is this possible with flashify.

Last i have a D5 - good working battery life - but join does not run every time (dont know why).

The D5+ is very stable with join - but at beginning - about 7hrs - not really an option.

10calls a 2minutes - about 30 notifications a day. - i think normal use

i have spend a lot of time to get the d5+ up to 20hrs battery life with Mobile Data always on an full function with all notifications over join.  (so it is a real backup to forget phone at home)

Now i wish to do a full img backup - but is it with the old TWRP not possible.

hope you understand my bad english.
Best Regards
eike

May 11, 2017 8:52:31 GMT 1 savi said:
I think not, because everything appears to work well except the SU UI. The only modification to the boot.img is the kernel rewrite protection to be disabled. And to my understanding this scatter file is for X5+, meaning it has the MTK6580 Boot.img If what you are saying is correct it means i now use a MTK6580 device with a MTK6572 boot.img? I understand that the only ported thing is the TWRP recovery, and if that is the cause (not flashing correctly SU binaries) a re-installation of superSU using a different SU app (like SuperUser) should fix the problem?

A bit of off-topic : I got the wakelock detector you was mentioning in the other post and is terrible on the device, but you can get the PC version that works through ADB but you have to replace the files in the ADB folder with the ones provided in the MTKdroid folder (the timeout of the authorization is to small in the original ADB)


On my device the wackelock detector is perfectly working. otherwise I would not have recommended it. I told you the little issue with the black letters (in one setting) on the black background.
Have you tried it in square mode?
Regarding the scatter file, i might have messed up my downloads - and I am sorry for that - i pulled another one from xda to compare.
@ciro thanks for your kind words, dont worry I am not here to tell stories to anybody.
I am just a member of this tiny community who is trying to support this board and its users as well as find help for a non properly working device.

May 11, 2017 13:01:51 GMT 1 insedere said:
May 11, 2017 9:34:03 GMT 1 Ciro Danise said:
To use flashify you need to have root access, but are you able to gain root access before flashing the TWRP?

Even more, if you only flash the new recovery, it will be overwritten at first reboot, so I’m sorry, you need to follow the “standard” procedure.


hi ciro - thanks for answer,
i did the proper way to root - and it has root - only the old TWRP does not mount DATA. (override recovery deleted and flashed org boot.img)
so i will override TWRP with the newer one.
Is this possible with flashify.

Last i have a D5 - good working battery life - but join does not run every time (dont know why).

The D5+ is very stable with join - but at beginning - about 7hrs - not really an option.

10calls a 2minutes - about 30 notifications a day. - i think normal use

i have spend a lot of time to get the d5+ up to 20hrs battery life with Mobile Data always on an full function with all notifications over join.  (so it is a real backup to forget phone at home)

Now i wish to do a full img backup - but is it with the old TWRP not possible.

hope you understand my bad english.
Best Regards
eike


Sorry, I didn't notice that you were talking about D5+. This recovery doesn't work on D5+; if you have an issue on my D5+ recovery please report it in the correct thread: /thread/85/twrp-3-2-x3-w612

Hello,
just flash twrp3.0.2 in d5+.
Also not able to Mount DATA partition.
Is there a way to make it?
BR
Eike

May 11, 2017 13:25:11 GMT 1 m47r1x said:
SPOILER: Click to show
On my device the wackelock detector is perfectly working. otherwise I would not have recommended it. I told you the little issue with the black letters (in one setting) on the black background. Have you tried it in square mode?

I actually do not have a black background, i have a transparent background witch sits on top of the app icon. It is extremely hard to see anything. And i have used the square screen and dark theme (it makes the letters white). P.S. do not install as system, the square screen will no longer apply to it and menu buttons will no longer be accesible (it took me a hour to uninstall it and reinstall it as user).

But you can use the PC version of this app to get same data over ADB (this is actually what i was bringing new to the conversation).

To all moderators : Sorry for off-topic, it will not happen again.

Recovery works good, except one bug: if the screen times out,i cant turn it back on, buttons dont work, only restart by holding power for 10sec. Disabled the screen timeout to avoid it in future use.

Thank you for the report, I’ll check that issue.

I rooted my X5+ with the rooting guide. Root works.

Can I factory reset the watch? (still rooted after)
If yes, do I have to do it in the settings or in TWRP?

Wiping Data partition in TWRP is enough and it will not remove your root.

Thank you

well i installed TWRP but don’t know how to boot to it (recovery).device not rooted yet.

found answer  in another forum and posted here link

I usually write the instrcution to enter recovery at the end of the post. I omitted it, but now I’ve added again.
Thank you

Hello,

I have Finow X5 AIR with firmware version176206 (the latest OTA upgrade)

Is this TWRP recovery compatible with this version of firware.

Kindly help me how to root Finow X5 AIR with this version

Thanking You

drsaidalavi

LEM5 root work with TWRP and magisk, instal magisk zip and install magisk apk, enjoy. 0 problems

works with the last update

unsuccessful twrp to my x5+… i mean i flash it but how to start twrp i don’t have any idea because adb start doesn’t work at all!!!

Jan 1, 2018 4:39:56 GMT 1 carni0 said:
LEM5 root work with TWRP and magisk, instal magisk zip and install magisk apk, enjoy. 0 problems

works with the last update


One question plz,

i need to know how is the battery life after flashing that custom recovery on Lemfo Lem 5 as we all know before the battery life was very bad and consuming very fast, and actually i don’t know if there is a relation between recovery and the battery!!!

Thank you,

Hi,
i got stuck in the process of flashing the TWRP recovery port to my LEM5 with w618-170926 - then i messed something up and bricked it.

Here is what i did:
I downloaded the recovery-twrp-302-lem5-20170429 to the watch with SpFlashTool v5.1636.
After rebooting the watch touch was not working anymore, so i couldn’t allow USB debugging for adb. Even so in testing mode (by booting watch with pressed “down” button) there was no touch input.

In order to set it back, i then tried to flash the firmware w616-170111, that was said to be required in first post.

After that, the watch would not boot anymore - the display stays black and there is a faint beebing sound while pressing up or down button.

I disconnected the battery cable to be shure it is powered off and tried flashing w618-170306, w618-170327 and w618-170911, which yielded error message S_FT_ENABLE_DRAM_FAIL.

Is it possible, that the watch still can be flashed with FW 170927, when it becomes available for download, or is the problem likely to be somwhere else?

Any thoughts or hints would greatly be appreciated.