-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lglaf doesn't work anymore on LG K10 2017 (M250N) since the last Oreo update. #56
Comments
extract-partitions.py doesn't have KILO (CENT / METR) challenge response authentication. All new versions of lafd require KILO to talk at all. You can use partitions.py --list to get a list, and --dump to dump the ones that you want. -- Brian |
Brian, thanks for responding; sadly, both commands ( |
You need to pass the --cr parameter so: ./partitions.py --cr --list or ./partitions.py --cr --dump -- Brian |
Hi Brian, thank you; I got a little bit further with this issue by doing a clean Linux install and then issuing the following in this order:
Now, when running
Apparently, LG disabled a lot of commands, as this seems to be the response when a command is not supported. When running lglaf with the
Everything else I tried did not seem to be supported. On the
|
Same exact issue on a G7. Have went through the same steps and cloned steadxfaster's lglaf. Dmesg shows activity and I can ctrl a reset, poweroff, etc. |
anyone able to provide the same command but with the "--debug" switch? |
@steadfasterX For what it's worth, I'm getting the same error 0x80000119 trying to dump any partition on LG V40. Using steadfasterX fork, branch develop. Ran with --debug, attaching log. steadfasterX branch develop.dump laf_a on LG V40.error 0x80000119.log "partitions.py --list" works for me, lists partitions on LUNs up to sdf. |
you can try my "ufs-test" branch (assuming that the v40 is an UFS device) but not guarantees. The problem is that in the middle of implementing the new UFS methods we both (@runningnak3d and I) stopped development. That means even though it might work for parts of the device the open commands are hard coded and so you can work only with one of the UFS disks at the same time. my mentioned UFS branch contains all known open cmds though and the only thing to do would be implementing a logic to use all of them automatically (for listing) and ofc a more intelligent logic when it comes to more like backing up etc (i.e. use only the required open cmd etc). My main issue was (and still is) that I do not own a LG UFS device and I am not willing to buy one. I don't know what happened to @runningnak3d but he might be your best chance (if he ever comes back here). |
@steadfasterX Danke schön, mann - yeah, I see the hardcoded open commands in laf_open_disk() in ufs-test branch, and I can backport other commits (laf_crypto, challenge-response, etc.) from develop branch to ufs-test branch. I see the Wireshark protocol dissector, enough for me to work on ... when I have time :-/ P.S.: Those hardcoded open commands - did you (or anyone else) verify them as working on UFS devices? |
Just to note that these instructions worked for me on my LG M257 Harmony (Cricket). So the fork, installing extra dependencies, and then running |
I'm afraid that LG did something with the last Oreo update to prevent us from using
lglaf
:I made sure to enable OEM unlocking in Developer Options. Dialing
*#*#759#*#*
does not give me a OEM unlock menu anymore (as it did before).The text was updated successfully, but these errors were encountered: