Ok, I'll now make four attempts to identify what's buggy.
Attempt 1 (just extract and repack, to see if the Page can boot a repacked recovery, even without changes): ==>
Success, boots fine
Code:
C:\>imgutil stock_recovery.img /x /v prop.default
C:\>imgutil stock_recovery.img /r /v prop.default
Attempt 2: ==>
Failure, white screen
Code:
C:\>imgutil stock_recovery.img /x /v prop.default
- Edit default.prop with Notepad++ ==> ro.secure=0
C:\>imgutil stock_recovery.img /r /v prop.default
Attempt 3:
Skipped
Code:
C:\>imgutil stock_recovery.img /x /v prop.default
- Edit default.prop with Notepad++ ==> ro.secure=0 | ro.debuggable=1
C:\>imgutil stock_recovery.img /r /v prop.default
Attempt 4:
Skipped
Code:
C:\>imgutil stock_recovery.img /x /v prop.default
- Edit default.prop with Notepad++ ==> ro.secure=0 | ro.debuggable=1 | ro.adb.secure=0
C:\>imgutil stock_recovery.img /r /v prop.default
Attempt 4:
Skipped
Code:
C:\>imgutil stock_recovery.img /x /v prop.default
- Edit default.prop with Notepad++ ==> ro.secure=0 | ro.debuggable=1 | ro.adb.secure=0
C:\>imgutil stock_recovery.img /r /v prop.default
Attempt 5:
Skipped
Code:
C:\>imgutil stock_recovery.img /x /v prop.default
- Edit default.prop with Notepad++ ==> To Be confirmed
C:\>imgutil stock_recovery.img /r /v prop.default
Attempt 6: ==>
Success, boots fine and adb under recovery enabled and can take commands
Code:
C:\>imgutil stock_recovery.img /x /v prop.default
- Edit default.prop with Notepad++ ==> ro.adb.secure=0
C:\>imgutil stock_recovery.img /r /v prop.default
Attempt 7: ==>
Failure, boots fine and adb under recovery enabled, but can't take commands due to SELINUX context issue
Code:
C:\>imgutil stock_recovery.img /x /v prop.default
- Edit default.prop with Notepad++ ==> ro.debuggable=1 | ro.adb.secure=0
C:\>imgutil stock_recovery.img /r /v prop.default