MobileRead Forums - View Single Post

DanyDanman · 06-30-2024, 06:47 PM

Evening, I found this post:

https://xdaforums.com/t/question-fas...#post-87923023

As it is:

Code:

C:\Users\User>adb shell
Go103:/ $ getprop sys.get_unlock_ability

Go103:/ $ getprop ro.oem_unlock_supported

Go103:/ $ getprop ro.oem_unlock_allowed

3 times blank.

This make me wonder can you patch in support for this action like in that tool
Maybe than I can try it out. (this https://github.com/bkerler/edl#for-generic-unlocking) Nvm, read the situation wrong. His is locked.

I have tried different pc (non ryzen) usb 2.0 port and no luck getting resolved the unknow command. Found that as possible solution. I truly hope that they did no remove those commands, I have read accounts from people that they can.

06-30-2024, 06:47 PM	#26
DanyDanman Connoisseur Posts: 51 Karma: 10 Join Date: Jun 2024 Device: Boox Go 10.3	Evening, I found this post: https://xdaforums.com/t/question-fas...#post-87923023 As it is: Code: C:\Users\User>adb shell Go103:/ $ getprop sys.get_unlock_ability Go103:/ $ getprop ro.oem_unlock_supported Go103:/ $ getprop ro.oem_unlock_allowed 3 times blank. This make me wonder can you patch in support for this action like in that tool Maybe than I can try it out. (this https://github.com/bkerler/edl#for-generic-unlocking) Nvm, read the situation wrong. His is locked. I have tried different pc (non ryzen) usb 2.0 port and no luck getting resolved the unknow command. Found that as possible solution. I truly hope that they did no remove those commands, I have read accounts from people that they can. Last edited by DanyDanman; 06-30-2024 at 06:49 PM.