5
[ROM][Sv2][UNOFFICIAL][RETROFIT] LineageOS 19.1 for Redmi K20 Pro / Mi 9T Pro [r...
source link: https://forum.xda-developers.com/t/rom-sv2-unofficial-retrofit-lineageos-19-1-for-redmi-k20-pro-mi-9t-pro-raphael.4464937/page-6#post-87409791
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
[ROM][Sv2][UNOFFICIAL][RETROFIT] LineageOS 19.1 for Redmi K20 Pro / Mi 9T Pro [raphael]
Thread starter
Start date
Krullendhaar
Senior Member
Oct 30, 2014
So I have the following issue:
My windows 10 laptops seems to recognize my Xiaomi, because when I plug it in with USB cable it shows up as "Mi 9T Pro" in windows. I downloaded the latest ADB from google and ADB works fine. However, when I boot into fastboot mode it seems my Mi 9T pro is no longer recognized by my laptop. Under device manager I can see the general "Android" device, indicating it was not recognized.
So ADB devices returns my device and fastboot devices returns nothing. Of course I run the command fastboot devices in fastboot mode (by typing adb reboot bootloader to get into fastboot mode).
Someone here suggested installing the latest google usb drivers. I downloaded them, but I am not sure how to install them. I tried installing it as follows: boot into fastboot mode, go to device manager, manually select the latest google usb drivers. If I try this, however, I get the message "no drivers found".
UPDATE: UNPAUSE WINDOWS UPDATES. This fixed it for me. If windows updates are paused the driver won't install. If they are not paused, they will install automatically.
My windows 10 laptops seems to recognize my Xiaomi, because when I plug it in with USB cable it shows up as "Mi 9T Pro" in windows. I downloaded the latest ADB from google and ADB works fine. However, when I boot into fastboot mode it seems my Mi 9T pro is no longer recognized by my laptop. Under device manager I can see the general "Android" device, indicating it was not recognized.
So ADB devices returns my device and fastboot devices returns nothing. Of course I run the command fastboot devices in fastboot mode (by typing adb reboot bootloader to get into fastboot mode).
Someone here suggested installing the latest google usb drivers. I downloaded them, but I am not sure how to install them. I tried installing it as follows: boot into fastboot mode, go to device manager, manually select the latest google usb drivers. If I try this, however, I get the message "no drivers found".
UPDATE: UNPAUSE WINDOWS UPDATES. This fixed it for me. If windows updates are paused the driver won't install. If they are not paused, they will install automatically.
Last edited: Yesterday at 2:20 PM
Krullendhaar
Senior Member
Oct 30, 2014
install latest google usb driver https://developer.android.com/studio/run/win-usb
For reference: in order to install this go to fastboot mode. Open device manager, click on the unknown device and manually select driver. Then select this driver.
Last edited: Yesterday at 2:28 PM
Krullendhaar
Senior Member
Oct 30, 2014
The first few times I reboot the device kinda lags and hangs for a few seconds.It does go away after a few reboots.
Last edited: Today at 10:56 AM
Redsandro
Senior Member
Jul 17, 2012
www.Redsandro.com
The developer is AFK so I'm trying to build this myself using the linked sources in order to get my keyboard problem fixed.
Here's my local manifest raphael.xml, It may be helpful for others. Not sure I'm allowed to link to vendor bits so I redacted that.
Here's my local manifest raphael.xml, It may be helpful for others. Not sure I'm allowed to link to vendor bits so I redacted that.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="gitlab" fetch="https://gitlab.com" />
<project path="device/xiaomi/raphael" name="xiaomi-sm8150-devs/android_device_xiaomi_raphael" remote="github" revision="lineage-19.1" />
<project path="device/xiaomi/sm8150-common" name="xiaomi-sm8150-devs/android_device_xiaomi_sm8150-common" remote="github" revision="lineage-19.1" />
<project path="kernel/xiaomi/sm8150-legacy" name="xiaomi-sm8150-devs/android_kernel_xiaomi_sm8150-legacy" remote="github" revision="lineage-19.1" />
<project path="vendor/xiaomi" name="[redacted]/proprietary_vendor_xiaomi" remote="gitlab" revision="lineage-19.1" />
<project path="hardware/xiaomi" name="LineageOS/android_hardware_xiaomi" remote="github" revision="lineage-19.1" />
</manifest>
Last edited: Yesterday at 5:14 PM
Reactions: dj_mcm2001, z1022 and Ullebe1
Krullendhaar
Senior Member
Oct 30, 2014
Installation tips on windows:
1. Download latest ADB drivers from google
2. Connect phone to windows 10 pc and make sure software updates are not paused. Windows will automatically install the correct drivers for Xiaomi Mi 9T Pro (or go to additional updates in settings and select the optional driver update)
3. Open command prompt in the adb folder by simply typing "cmd" in the path and pressing enter. I personally never managed to use cd (change directory) or 'open command here' in windows to get adb working.
4. Check adb: Type adb. If you get an error, then adb is not setup correctly.
5. Check adb connection: type adb devices. If you get an error, then you might need to update the driver for your device as described in step 2.
6. Go into fastboot mode and check fastboot connection: type fastboot devices. If you encounter an error, then it might be the case you need to manually install another driver. This time it is the google usb driver. You need to go to device manager in windows while connected in fastboot mode, select the unknown device (it just says "Android"), click on manually install drivers and then select the google usb driver. I repeat, do this while connected in fastboot mode. This driver won't be automatically downloaded by windows. Download the latest driver from google.
1. Download latest ADB drivers from google
2. Connect phone to windows 10 pc and make sure software updates are not paused. Windows will automatically install the correct drivers for Xiaomi Mi 9T Pro (or go to additional updates in settings and select the optional driver update)
3. Open command prompt in the adb folder by simply typing "cmd" in the path and pressing enter. I personally never managed to use cd (change directory) or 'open command here' in windows to get adb working.
4. Check adb: Type adb. If you get an error, then adb is not setup correctly.
5. Check adb connection: type adb devices. If you get an error, then you might need to update the driver for your device as described in step 2.
6. Go into fastboot mode and check fastboot connection: type fastboot devices. If you encounter an error, then it might be the case you need to manually install another driver. This time it is the google usb driver. You need to go to device manager in windows while connected in fastboot mode, select the unknown device (it just says "Android"), click on manually install drivers and then select the google usb driver. I repeat, do this while connected in fastboot mode. This driver won't be automatically downloaded by windows. Download the latest driver from google.
Last edited: Today at 8:54 AM
Redsandro
Senior Member
Jul 17, 2012
www.Redsandro.com
If anyone else wants to use AOSP Keyboard swiping with a language that used to work in LOS18 but is not able to compile this, I've built a version with the bugfix and the august security patches.The developer is AFK so I'm trying to build this myself using the linked sources in order to get my keyboard problem fixed.
Use at your own risk. No warranty. Better build it yourself.Download: lineage-19.1-20220908-UNOFFICIAL-raphael.zip
Security patch level:
2022-08-05Sha256sum:
9884c95c6ff7ab8b53e7b425dd849c7d1bdcf2d6fd6508161691fd930fe36684Expiry: The link will expire when there is a new security patch level later this month.
You need to have the original from @SebaUbuntu installed first. Then you can dirty flash this one using the same recovery provided in this thread.
I am not an Android developer and I have no intentions of taking over Seba's fantastic work. It's just that he's unresponsive/AFK and this bug has been bugging me for too long.
Settings > Apps > Android Keyboard (AOSP) > Storage > Clear storage
Restart system
Now you have 28 dictionaries in stead of just 8.
Last edited: Today at 4:12 PM
Reactions: coleckion
Krullendhaar
Senior Member
Oct 30, 2014
After 2 days of no issues, my fingerprint scanner stopped recognizing my finger and it won't let me add a new finger
UPDATE: When "extra dim" is active, the fingerprint does not work reliably. Similar for night light. This is because the sensor is optical.
UPDATE: When "extra dim" is active, the fingerprint does not work reliably. Similar for night light. This is because the sensor is optical.
Last edited: 40 minutes ago
Krullendhaar
Senior Member
Oct 30, 2014
If anyone else wants to use AOSP Keyboard swiping with a language that used to work in LOS18 but is not able to compile this, I've built a version with the bugfix and the august security patches.Use at your own risk. No warranty. Better build it yourself.
Download: lineage-19.1-20220908-UNOFFICIAL-raphael.zip
Security patch level:2022-08-05
Sha256sum:9884c95c6ff7ab8b53e7b425dd849c7d1bdcf2d6fd6508161691fd930fe36684
Expiry: The link will expire when there is a new security patch level later this month.
You need to have the original from @SebaUbuntu installed first. Then you can dirty flash this one using the same recovery provided in this thread.
I am not an Android developer and I have no intentions of taking over Seba's fantastic work. It's just that he's unresponsive/AFK and this bug has been bugging me for too long.
Settings > Apps > Android Keyboard (AOSP) > Storage > Clear storage
Restart system
Now you have 28 dictionaries in stead of just 8.
You might want to also try florisboard.
Top Liked Posts
-
No. Development has stalled about a month ago. Latest release is the 2022-07-07 one. Not sure if priorities have changed or insurmountable problems surfaced. Perhaps @SebaUbuntu can comment on that.Is this rom official yet?The developer is AFK so I'm trying to build this myself using the linked sources in order to get my keyboard problem fixed.
Here's my local manifest raphael.xml, It may be helpful for others. Not sure I'm allowed to link to vendor bits so I redacted that.Code:<?xml version="1.0" encoding="UTF-8"?> <manifest> <remote name="gitlab" fetch="https://gitlab.com" /> <project path="device/xiaomi/raphael" name="xiaomi-sm8150-devs/android_device_xiaomi_raphael" remote="github" revision="lineage-19.1" /> <project path="device/xiaomi/sm8150-common" name="xiaomi-sm8150-devs/android_device_xiaomi_sm8150-common" remote="github" revision="lineage-19.1" /> <project path="kernel/xiaomi/sm8150-legacy" name="xiaomi-sm8150-devs/android_kernel_xiaomi_sm8150-legacy" remote="github" revision="lineage-19.1" /> <project path="vendor/xiaomi" name="[redacted]/proprietary_vendor_xiaomi" remote="gitlab" revision="lineage-19.1" /> <project path="hardware/xiaomi" name="LineageOS/android_hardware_xiaomi" remote="github" revision="lineage-19.1" /> </manifest>I plan to go official in a few days, let me know if there's any bug leftThanks for the great work on this rom and It is a great news to make it official.
If anyone else wants to use AOSP Keyboard swiping with a language that used to work in LOS18 but is not able to compile this, I've built a version with the bugfix and the august security patches.The developer is AFK so I'm trying to build this myself using the linked sources in order to get my keyboard problem fixed.Use at your own risk. No warranty. Better build it yourself.
Download: lineage-19.1-20220908-UNOFFICIAL-raphael.zip
Security patch level:2022-08-05
Sha256sum:9884c95c6ff7ab8b53e7b425dd849c7d1bdcf2d6fd6508161691fd930fe36684
Expiry: The link will expire when there is a new security patch level later this month.
You need to have the original from @SebaUbuntu installed first. Then you can dirty flash this one using the same recovery provided in this thread.
I am not an Android developer and I have no intentions of taking over Seba's fantastic work. It's just that he's unresponsive/AFK and this bug has been bugging me for too long.
Settings > Apps > Android Keyboard (AOSP) > Storage > Clear storage
Restart system
Now you have 28 dictionaries in stead of just 8.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK