-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Support for poco f3 plz. For me to install evolution x rom on it. #79
Comments
Hey @Bizz912, thanks a lot! :) You mean this device? https://wiki.lineageos.org/devices/alioth/ Would you be able to test the new release? |
As soon as I get that phone in place of galaxy a32 4g. |
I can test it also with my phone |
Do let us know man. |
Can account spoofer be added for unlocking bootloaders on poco phones? |
I don't know what an account spoofer exactly is so I don't know 😅 |
Basically tricking the software or device into using randomly generated account, something similar to how Aurora store uses a dummy account. |
@tsterbak Btw is oneplus 8 supported? Its not on the list. |
Thanks for the info about account spoofing :) I knew Aurora did it, but how would that be used to unlock the bootloader on Poco phones? Are there any resources available? At least when I unlocked a Xiaomi device, they basically want it all... SIM and phone number and you have to create an account...
Nope, if its not on the list, it's not supported. The issue is, it requires to flash a vbmeta and dtbo image and I'm not sure yet how to support it in a user friendly way... Also, I don't have a device that requires these steps available for testing. |
Its alright, I am also looking at op8 for usb 3.1, display port. I can't seem to figure the unlock bootloader part either on poco. Didn't know about phone number req though. 😔 |
Yeah that is a bummer... Got a Redmi Note 8 Pro and I don't want to give 'em my phone number and almost exact location... Just why is this a requirement?! |
Merged and officially still untested. |
The tool's awesome.
The text was updated successfully, but these errors were encountered: