{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ubuntu Touch for Xiaomi Mi Mix 3
With Support for OTA Updates
DISCLAIMER:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
REQUIRED:
- Unlocked bootloader
- Enable USB Debugging
INSTALLATION:
Download official installer from ubuntu-touch.io and follow on-screen instructions.
KNOWN BUGS:
Automatic brightness
Proximity sensors
GPS
Others: Please test and report
BUGS STATUS:
See here.
CHANGELOGS:
01 July 2021:
- Added ubports installer support (one-click installer)
- Fixed call audio
- Added Anbox 10 early support
22 June 2021:
- Added OTA support
- Fixed audio
- Fixed fingerprint
- Fixed MTP and ADB
- Fixed charging icon
27 May 2021:
- Switched from GSI to manual build using UBPorts CI
- Battery icon doesn't show as charge during charging, but it is charging fine
- Anbox is now working
Build info:
Build author: xperseus
Repo: https://gitlab.com/ubports/community-ports/android9/xiaomi-mi-mix-3
References:
Ubports' CI Guide: https://github.com/ubports/porting-notes/wiki/GitLab-CI-builds-for-devices-based-on-halium_arm64-(Halium-9)
Ubports' Documentation: https://docs.ubports.com/en/latest/
Halium Documentation: https://docs.halium.org/en/latest/index.html
Common tree: https://github.com/LineageOS/android_device_xiaomi_sdm845-common/tree/lineage-16.0
Device tree: https://github.com/LineageOS/android_device_xiaomi_perseus/tree/lineage-16.0
Kernel source: https://github.com/LineageOS/android_kernel_xiaomi_sdm845/tree/lineage-16.0
Credit to UBPorts & Halium team for support and guides. Specially thanks to NotKit.
Created 20 May 2021
Last Updated 01 July 2021
Screenshots
thanks!!
can i dualboot with android ?
Sorry english not my main language
Tungpham99 said:
can i dualboot with android ?
Sorry english not my main language
Click to expand...
Click to collapse
No you cannot.
Hi,
No matter how hard I try I cannot get past the MI logo.
I tried several twrp img (not every, and on most recent ones I get a treble zip compatibility error btw, seems normal tho)
I wonder if I missing something obvious...
Finally the possibility of Linux on this phone I waited for this day so long thank you so much for your work. Sadly Im unable to boot. On what TWRP Version are you? The current one wouldnt work with any Miui Android 9 version i tried. Tried flashing via TWRP / ADB both end in stuck Mi Logo.
xN&5NP said:
Finally the possibility of Linux on this phone I waited for this day so long thank you so much for your work. Sadly Im unable to boot. On what TWRP Version are you? The current one wouldnt work with any Miui 10 / Android 9 version i tried. Tried flashing via TWRP / ADB both end in stuck Mi Logo.
Click to expand...
Click to collapse
What Rom did you have previously installed? And did you do a full wipe / format before installing Miui 9?
luigi024 said:
Hi,
No matter how hard I try I cannot get past the MI logo.
I tried several twrp img (not every, and on most recent ones I get a treble zip compatibility error btw, seems normal tho)
I wonder if I missing something obvious...
Click to expand...
Click to collapse
Pls try this version of twrp as i used this one: https://dl.twrp.me/perseus/twrp-3.2.3-0-perseus.img.html
xN&5NP said:
Finally the possibility of Linux on this phone I waited for this day so long thank you so much for your work. Sadly Im unable to boot. On what TWRP Version are you? The current one wouldnt work with any Miui Android 9 version i tried. Tried flashing via TWRP / ADB both end in stuck Mi Logo.
Click to expand...
Click to collapse
Please use 3.2.3: https://dl.twrp.me/perseus/twrp-3.2.3-0-perseus.img.html
xN&5NP said:
What Rom did you have previously installed? And did you do a full wipe / format before installing Miui 9?
Click to expand...
Click to collapse
Please follow this steps:
1. Install Android 9 MIUI as base (I used CN 9.2.15) < Mi Flash fastboot as I was on android 11
2. Install and boot to TWRP < use TWRP 3.2.3, don't use the latest version
3. Download and flash Ubuntu Touch GSI v10 from here in TWRP < flash ubports GSI
4. Flash halium-boot.img attached in this post via fastboot/TWRP. < flash my halium-boot.img
5. Download and flash Halium-boot_no_console_patch from here in TWRP. < THIS IS A MUST, otherwise bootloop
6. Wipe data and reboot.
Note: u will lose all data in step 1, pls backup
luigi024 said:
Hi,
No matter how hard I try I cannot get past the MI logo.
I tried several twrp img (not every, and on most recent ones I get a treble zip compatibility error btw, seems normal tho)
I wonder if I missing something obvious...
Click to expand...
Click to collapse
Did you download and flash Halium-boot_no_console_patch as mentioned in op, this is very important to get out of bootloop.
Yes I flashed Halium-boot_no_console_patch each time I tried to boot, but it wasn't even booting, only MI logo...
I use the recovery package to reflash android 9, it may have caused the issue... Gonna wait a few more hours to download the fastboot package ! And while waiting I'll try just with this TWRP version if it works !
luigi024 said:
Yes I flashed Halium-boot_no_console_patch each time I tried to boot, but it wasn't even booting, only MI logo...
I use the recovery package to reflash android 9, it may have caused the issue... Gonna wait a few more hours to download the fastboot package ! And while waiting I'll try just with this TWRP version if it works !
Click to expand...
Click to collapse
Yes pls do that, and let me know.. i did it a few time, always working from my side. I think u might need to fastboot flash CN9.2.15 like me.
@luigi024, @xN&5NP hi both, I just tried to simulate my steps and realized that I failed to mentioned one important step, you need to flash LineageOS 16 on top of CN9.5.12. I have updated the op, if you cannot download LineageOS please pm me.
xperseus said:
@luigi024, @xN&5NP hi both, I just tried to simulate my steps and realized that I failed to mentioned one important step, you need to flash LineageOS 16 on top of CN9.5.12. I have updated the op, if you cannot download LineageOS please pm me.
Click to expand...
Click to collapse
Followed your steps and got Ubuntu Touch up and running. Great work!
xperseus said:
Please follow this steps:
1. Install Android 9 MIUI as base (I used CN 9.2.15) < Mi Flash fastboot as I was on android 11
2. Install and boot to TWRP < use TWRP 3.2.3, don't use the latest version
3. Download and flash Ubuntu Touch GSI v10 from here in TWRP < flash ubports GSI
4. Flash halium-boot.img attached in this post via fastboot/TWRP. < flash my halium-boot.img
5. Download and flash Halium-boot_no_console_patch from here in TWRP. < THIS IS A MUST, otherwise bootloop
6. Wipe data and reboot.
Note: u will lose all data in step 1, pls backup
Click to expand...
Click to collapse
Where do I find halium-boot.img as described in 4.? I'm obviously blind. Thanks in advance.
chromanju said:
Where do I find halium-boot.img as described in 4.? I'm obviously blind. Thanks in advance.
Click to expand...
Click to collapse
Please read the OP, the installation now is supported by Ubuntu Touch installer (UBPorts Installer), just download it from https://ubuntu-touch.io/get-ubuntu-touch and follow on screen instructions. Let me know if u still have questions.
Related
TWRP Recovery 3.2.1-0 For Cubot X18 Plus
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Welcome all Cubot X18 Plus users, This is Lastest TWRP Recovery For your device By TWRPBuilder Team
CHANGELOG for 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
DownloadsCubot X18 Plus Recovery img
Sources:
Code:
[CENTER][URL="https://github.com/TwrpBuilder/android_device_cubot_cubot_x18"][COLOR="bule"]Device tree[/COLOR][/URL]
[URL="https://github.com/TeamWin/Team-Win-Recovery-Project"][COLOR="bule"]TeamWin Github
[/COLOR][/URL][/CENTER]
How to install:
you must have fastboot installed on your pc and then:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
Don't Forget to Hit Thanks :good:
Thank you kindly for the work to get TWRP working on the X18 Plus! Are new versions of TWRP automatically built now along with all the other versions supported. How has the feedback been on the release?
James.Harking said:
Thank you kindly for the work to get TWRP working on the X18 Plus! Are new versions of TWRP automatically built now along with all the other versions supported. How has the feedback been on the release?
Click to expand...
Click to collapse
Yes, a new release is auto-built every month.
Tested by @iNFeRNuSDaRK and confirmed it's working. Except for encryption support.
Encryprion
yshalsager said:
Yes, a new release is auto-built every month.
Tested by @iNFeRNuSDaRK and confirmed it's working. Except for encryption support.
Click to expand...
Click to collapse
My phone is encyipted. How to get it off ??? Thanks
Hi all,
I just wanted to post an interesting message from the X18 plus 'forum' regarding the functionality of the TWRP.
Cheers guys!
Quote:
Originally Posted by HûnSt°rJonnyt
yes, got it successfully running with SP Flash Tool, i couldn't flash it with fastboot.
twrp runs and i could install magisk.
Badly it seems there are some x18 Plus modifications missing in the recovery img
when i want to update the system i get things like
E3004: This package is for CUBOT_X18_Plus devices this is a cubot_x18.
even if try to modify the updater-script to ignore these checks, i fail at least at updating the system partitions, maybe some problems with encryption or file system layouts modifications for x18 plus are missing
ok i tried to recompile the recovery and tried to find the right parameters but this gets much more confusing, when i try to update to the latest official rom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HûnSt°rJonnyt said:
ok i tried to recompile the recovery and tried to find the right parameters but this gets much more confusing, when i try to update to the latest official rom
Click to expand...
Click to collapse
Test the new build (will be uploaded here with today's date in some minutes) and check
[Build Progress]
yshalsager said:
Test the new build (will be uploaded here with today's date in some minutes) and check
[Build Progress]
Click to expand...
Click to collapse
same as with the old build
E3004: This package is for CUBOT_X18_Plus devices this is a cubot_x18.
Edit: ok i see, i think the build wasn't successfull so there where no changes in the .img
---------- Post added at 04:47 PM ---------- Previous post was at 03:51 PM ----------
so i tried more stuff, when reverting back to original recovery i get
E3005: "EMMC:/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot:10138528:fcf3cc2d6ac345fa071fb12e409df7234de130cb:10156960:84a65157b0daa69dd9559f7d7b109ad2909e225b" has unexpected contents.
so i think maybe it's an issue with original update and unlocked bootloader, not sure how to understand this. Maybe TWRP is fine and this issue don't come when using custom rom
HûnSt°rJonnyt said:
same as with the old build
E3004: This package is for CUBOT_X18_Plus devices this is a cubot_x18.
Edit: ok i see, i think the build wasn't successfull so there where no changes in the .img
---------- Post added at 04:47 PM ---------- Previous post was at 03:51 PM ----------
so i tried more stuff, when reverting back to original recovery i get
E3005: "EMMC:/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot:10138528:fcf3cc2d6ac345fa071fb12e409df7234de130cb:10156960:84a65157b0daa69dd9559f7d7b109ad2909e225b" has unexpected contents.
so i think maybe it's an issue with original update and unlocked bootloader, not sure how to understand this. Maybe TWRP is fine and this issue don't come when using custom rom
Click to expand...
Click to collapse
Well, build errored that's why it's the same.
This error you posted means you have modified boot partition, are you trying to flash an OTA?
New build is out!
https://github.com/TwrpBuilder/andr...a9fb23dad3e/TWRP-3.2.1-cubot_x18-20180629.img
Good morning everybody, I tried the new build but i have again the same error "Failed to mount '/data' (Invalid argument).
Any new?
yshalsager said:
Well, build errored that's why it's the same.
This error you posted means you have modified boot partition, are you trying to flash an OTA?
Click to expand...
Click to collapse
yes it's ota.
i will try new release soon
HûnSt°rJonnyt said:
yes it's ota.
i will try new release soon
Click to expand...
Click to collapse
You can't flash ota if you made modifications to boot/system
So first flash full rom, flash ota, backup boot, flash magisk or whatever
when you get another ota, restore boot then flash, and so
I ported Philz recovery to x18 plus, got it working, everything works fine except it can't mount /data
So just asking asking between TWRP and now Philz recovery being ported is the X18 plus are we in a position where there is a working recovery that can install a GSI so we could use the Project Trebble ROMS? If not then what is the impediment stopping this? I am happy to try and contact Cubot directly if it helps out?
@yshalsager : I saw that you wrote in the other thread that you need the /vendor/etc/fstab.* files. Do you still need these? If I can get some instructions on how to provide these to you I happily will do.
Thanks all for continued work on this phone.
James.Harking said:
So just asking asking between TWRP and now Philz recovery being ported is the X18 plus are we in a position where there is a working recovery that can install a GSI so we could use the Project Trebble ROMS? If not then what is the impediment stopping this? I am happy to try and contact Cubot directly if it helps out?
@yshalsager : I saw that you wrote in the other thread that you need the /vendor/etc/fstab.* files. Do you still need these? If I can get some instructions on how to provide these to you I happily will do.
Thanks all for continued work on this phone.
Click to expand...
Click to collapse
The recoveries are working alright, its just an issue with Oreo's force encryption of the data partition (the system automatically encrypts the data partition on 1st boot) if you do a full wipe of /data the encryption is cleared, you'll see TWRP can access it but after first boot its back to encrypted.
As for GSI I guess you can install (haven't had time to test thought), you may need to do a full wipe of /data before you boot the new system.
I just tested out the official RR GSI from https://forum.xda-developers.com/pr...pment/gsi-resurrection-remix-o-6-1-0-t3811299 on x18_plus everything working okay except MTP, you have to disable adb. And network when using dual SIM is not very stable
James.Harking said:
So just asking asking between TWRP and now Philz recovery being ported is the X18 plus are we in a position where there is a working recovery that can install a GSI so we could use the Project Trebble ROMS? If not then what is the impediment stopping this? I am happy to try and contact Cubot directly if it helps out?
@yshalsager : I saw that you wrote in the other thread that you need the /vendor/etc/fstab.* files. Do you still need these? If I can get some instructions on how to provide these to you I happily will do.
Thanks all for continued work on this phone.
Click to expand...
Click to collapse
Give this a try and check if force encryption disabled
https://forum.xda-developers.com/showpost.php?p=77091359&postcount=1
Hi @kamwash @yshalsager,
Great work guys, could I request for the lurkers on this forum that you might point people to a guide for installing your recoveries? Or conversely write a few lines here if you have a few spare minutes. I think it would help out as other tutorials are not really specific for the X18 plus and people are scarred of bricking their working phones.
Many thanks gents!
James.Harking said:
Hi @kamwash @yshalsager,
Great work guys, could I request for the lurkers on this forum that you might point people to a guide for installing your recoveries? Or conversely write a few lines here if you have a few spare minutes. I think it would help out as other tutorials are not really specific for the X18 plus and people are scarred of bricking their working phones.
Many thanks gents!
Click to expand...
Click to collapse
Install using fastboot
As I already wrote in the first post
How to install:
you must have fastboot installed on your pc and then:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
https://drive.google.com/open?id=10i5ddHcV0lt8JJ7nV1bJjqc1XXjLCp8n
Note this is just a hobby, but feel free to report bugs.
Kernel source: Prebuilt stock kernel
Boot to fastboot ( volume down and power )
in fastboot type:
Link comes later when stable
fasboot reboot and hold power up and volume
Click to expand...
Click to collapse
Note: this twrp is working with the orginal system, when ota happens just flash twrp again.
BUGS:
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Contributors
@bassbounce ( Compiled )
@Manish4586 ( Device tree )
Device tree: https://github.com/Manish4586/android_device_xiaomi_jasmine-twrp
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information:
Status: testing
Created 17-9-2018
Last Updated 17-9-2018
Nice! So this is supposed to work without A/B conflicts - unlike the other TWRP project?
Edit: Awesome! This works great so far. I now have permanent TWRP on my device. It updates partition details perfectly and I was able to flash Magisk without an issue.
Thanks a lot for your work!
thedisturbedone said:
Nice! So this is supposed to work without A/B conflicts - unlike the other TWRP project?
Click to expand...
Click to collapse
U are right, this twrp just boots the stock android, the other did not do that.
bassbounce said:
U are right, this twrp just boots the stock android, the other did not do that.
Click to expand...
Click to collapse
Thank you. Edited my initial post with results. This would open our device to a lot of possibilities.
I have September update, can i install this?
ki69 said:
I have September update, can i install this?
Click to expand...
Click to collapse
I dont know, i didnt test it on the september .
bassbounce said:
Yes, it should be no problem.
Click to expand...
Click to collapse
Thanks man, can you build it for mi a2 lite (daisy) ?
Touch screen don't work
After flash twrp touch screen don't work
My device rooted and install magisk
s.arthit1993 said:
After flash twrp touch screen don't work
My device rooted and install magisk
Click to expand...
Click to collapse
Try flashing stock boot img
This is work for my Mi A2 Rooted Whit Magisk V17.1 ?
Unfortunately, I'm not a developer.
Can someone compile the code and make an available download for this image, please?
Many Thanks!
MMN said:
Unfortunately, I'm not a developer.
Can someone compile the code and make an available download for this image, please?
Many Thanks!
Click to expand...
Click to collapse
same problem here, I don't know how to download or install it, I would like to try it
Adairo said:
same problem here, I don't know how to download or install it, I would like to try it
Click to expand...
Click to collapse
Fastboot flash boot file.img
Restart phone and boot in to recovery volume up and power key.
If it works please report here,
I don't know if twrp works with the September update which is pulled back.
Also I need a 6gb 128 a2 to test this.
DOWNLOAD:
Some ppl reported touch problems we look in to that
Dont download yet
nvm
wi-fi does not work
bassbounce said:
Fastboot flash boot file.img
Restart phone and boot in to recovery volume up and power key.
If it works please report here,
I don't know if twrp works with the September update which is pulled back.
Also I need a 6gb 128 a2 to test this.
Click to expand...
Click to collapse
You have changed the file. The difference is enormous. Which one is correct?
-> twrp-jasmine-0.1.img (27.276kb) -> Link removed in the cited post
-> boot.img (37.252kb) -> Link in post #1
Mi A2 6/128GB is here.
dimaxxxxx said:
wi-fi does not work
Click to expand...
Click to collapse
And yes: wifi does not work on both images
WiFi not working, help please.
Testing without wifi:
* Magisk v17.1 (via TWRP/zip) -> works
* SuperSU (via Magisk) -> works
* SELinux-Manager (via TWRP/zip) and go to permissive mode -> works
* xposed (xposed-v90.2-sdk27-beta3, via TWRP) -> bootloop - I'll try direct installation through Magisk when wifi works.
What's about error message when deleting the cache in TWRP:
unable to find partition for path '/cache'?
To all restore the stock boot.img. To fix it
We need to find a solution. Don't flash the twrp.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
******************************************
Hi there,
This is the official build (beta) based on TWRP sources and xiaomi blobs ... fully working !
(Mi 9 Lite / Mi CC9)
!!! IT'S NOT MY PROBLEM, IF YOU DON'T READ AND FOLLOW MY INSTRUCTION CAREFULLY, IF YOU DON'T HAVE TIME FOR THIS, OR IF YOU FLASH SOMETHING OR DO A MANIPULATION I DIDN'T MENTION HERE !!!
THIS RECOVERY DOESN'T SUPPORT ANY ZIP MOD/ROM THAT DOESN'T USE SYSTEM_ROOT MOUNT. CHECK OFFICIAL TWRP HOMEPAGE FOR MORE INFORMATION ABOUT NEW A/B DEVICES FROM 2019
Installation Procedure (first time) :
- Unlock your bootloader D)
- Enable ADB from your Official MIUI Developer option
- Plug your USB cable to your Windows PC and type :
adb reboot bootloader
- type then :
fastboot flash recovery twrp-3.3.1-0-pyxis-final (auto-decrypt).img (rename your image just by twrp.img)
fastboot flash vbmeta vbmeta.img
fastboot reboot (keep Vol+ pressed until you see TWRP splash)
- Wait for decrypting ... (if already you set a lockscreen pattern or a fingerprint)
- Format Data (button on the right) + Type "yes" on the keyboard popup
- Reboot
- To boot TWRP from MIUI : reboot menu + keep Volume UP pressed.
- To boot from phone off : power button + Volume UP
TWRP can now auto-decrypt your crypted /data partition so you can make backup with no issue.
This is a big fix that prevent to loose your fingerprint and pattern ...
For MIUI users, you must flash the fstab.zip fix after flashing your MIUI rom !!!
Enjoy ! :good:
Update : 2019-11-05
-version : 3.3.1-0
-busybox update
-terminal fixed
-stable and optimized : setting lockscreen pattern and fingerprint on the first boot is no longer needed !
BE SURE WHEN YOU WIPE YOUR DATA, YOU KEEP THE "4 FOLDERS BELOW + .layout_version". THESE ARE YOU ENCRYPTION DATA. IF YOU DELETE THEM, YOU WILL NOT BE ABLE TO RESTORE YOUR DATA BACKUP UNTIL YOU FORMAT YOUR DATA AGAIN.
TRICK TO SAVE YOUR LIFE : ALWAYS KEEP YOUR BACKUPS ON THE EXTERNAL STORAGE !!!
Download
link
XDA : DevDB Information
TWRP, Tool/Utility for the Mi 9 Lite / Mi CC9 (pyxis)
Contributors
gringo80
Source Code 1 : https://github.com/TeamWin
Source Code 2 : Prebuilt Recovery Kernel from MIUI
Version Information
Status : Stable
Release Date : 2019-11-05
Any screenshot?
Thank you for the contribution, is it required to flash the zip to prevent encryption after each rom flash ??
j0an said:
Thank you for the contribution, is it required to flash the zip to prevent encryption after each rom flash ??
Click to expand...
Click to collapse
To prevent encryption, go to twrp homescreen and choose "format data" and type "yes"... but before that, make your data backup on the external-sd ! (the first thing i do on all my devices)
Please use the official beta build !
:good:
gringo80 said:
Please use the official beta build !
:good:
Click to expand...
Click to collapse
Where's the download link? Maybe I'm blind....
oieNao said:
Where's the download link? Maybe I'm blind....
Click to expand...
Click to collapse
Update : vbmeta Fix is available (the patch is no longer needed)
Please download the latest build from 2019-10-27 (11:25:55) . This is the final build.
Read the OP !
Awesome.
Will you bring more goodness to our device, like custom roms?
Sent from my MI 9 Lite using Tapatalk
tiagorodrigueez said:
Awesome.
Will you bring more goodness to our device, like custom roms?
Sent from my MI 9 Lite using Tapatalk
Click to expand...
Click to collapse
I'm working on a GSI patch. The builds (AOSP-PixelExperience-LineageOS) boot but stuck on bootanimation.
For information, our device is treble ready : so the builds to use are arm64-ab (yes ab not aonly) !
Also suitable for the Mi 9 Lite?
gringo80 said:
Update : vbmeta Fix is available (the patch is no longer needed)
Please download the latest build from 2019-10-27 (11:25:55) . This is the final build.
Read the OP !
Click to expand...
Click to collapse
what is the vbmeta.img file? never encountered something like this in other phones
mikdo said:
Also suitable for the Mi 9 Lite?
Click to expand...
Click to collapse
yes, i have the mi 9 lite !
sorry for noob question, but what happen if I don't format data after flashed twrp?
gringo80 said:
I'm working on a GSI patch. The builds (AOSP-PixelExperience-LineageOS) boot but stuck on bootanimation.
For information, our device is treble ready : so the builds to use are arm64-ab (yes ab not aonly) !
Click to expand...
Click to collapse
It's a surprise to be ABdevice. Some people on our telegram group already tested havoc builds and booted but had some bugs on 4g and offline charging.
Sent from my MI 9 Lite using Tapatalk
holymoz said:
what is the vbmeta.img file? never encountered something like this in other phones
Click to expand...
Click to collapse
vbmeta means verified boot signature. the vbmeta.img provided here bypass this verification !
tiagorodrigueez said:
It's a surprise to be ABdevice. Some people on our telegram group already tested havoc builds and booted but had some bugs on 4g and offline charging.
Sent from my MI 9 Lite using Tapatalk
Click to expand...
Click to collapse
It depends on the kernel used. You can modify the kernel as you want to make it aonly or A/B. Here, the stock kernel provided by xiaomi is for A/B buils. That's it ! I want to make a patch so to keep the stock kernel untouched ! (Modded kernels are never perfect)
When i flash the recovery, i am stuck at the twrp boot image. What to do?
jbsabado28 said:
When i flash the recovery, i am stuck at the twrp boot image. What to do?
Click to expand...
Click to collapse
download the last build and flash vbmeta
(OP)
holymoz said:
sorry for noob question, but what happen if I don't format data after flashed twrp?
Click to expand...
Click to collapse
you can't access to the internal storage content. better to decrypt by formatting data !
tiagorodrigueez said:
It's a surprise to be ABdevice. Some people on our telegram group already tested havoc builds and booted but had some bugs on 4g and offline charging.
Click to expand...
Click to collapse
please send the link on pm
---------- Post added at 11:33 PM ---------- Previous post was at 11:30 PM ----------
gringo80 said:
I'm working on a GSI patch. The builds (AOSP-PixelExperience-LineageOS) boot but stuck on bootanimation.
For information, our device is treble ready : so the builds to use are arm64-ab (yes ab not aonly) !
Click to expand...
Click to collapse
Its sad that they didnt boot... Cant wait to see some rom's working treble or not
[GSI][arm64][A/AB] Ubuntu Touch (ubports)
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included...
forum.xda-developers.com
In order to flash Halium on a Guacamole device, you need the stock Android 9 firmware. For Global: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7 Pro/9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip/download For EU: https://sourceforge.net/projects/fa...16_all_1908281716_b2bb5-FASTBOOT.zip/download Next make sure your firmware actually boots.
Next enable developer options and enable usb debugging.
Reboot to twrp and format data.
Next you need to install Lineage 16 which can obtained from http://dlr.ovh:8080/guacamole/lineage-16.0-20200325-nightly-guacamole-signed.zip
let it boot, reboot to twrp and format data
Now Download artifacts ( https://gitlab.com/RyanAM/oneplus-guacamole-halium9/-/jobs/1757465059/artifacts/browse)
and extract .zip. Inside the zip you extracted you will find a boot.img and a system.img. flash boot.img with twrp by selecting install image then selecting boot.
reboot to fasboot and run
fastboot flash system system.img and reboot. Enjoy!
TWRP image: https://sourceforge.net/projects/ma...uacamole-unified-Pie-mauronofrio.img/download(edited)
Downgrade 11 to 10: https://oxygenos.oneplus.net/OnePlu...all_2010191035_downgrade_22b70083812944e2.zip
Downgrade 10 to 9: https://oxygenos.oneplus.net/fulldowngrade_wipe_MSM_18857_190505_1527_user.zip
Artifacts · devel-flashable (#1757465059) · Jobs · RyanAM / Oneplus Guacamole-halium9
GitLab.com
gitlab.com
Sources: https://github.com/RyanAM
I'm kind of a lazy poster..
most things are working
mms doesn't seem to work
screen brightness settings don't work to well
screen flashes a little now and again
not sure if nfc works
some other things you tell me
I started this just to see if it would work and for fun. here we are just thought i should share
Screenshot please
muphetz said:
Screenshot please
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oh look at that I found my old name on xda! I hope you guys enjoy this! If a mod can maybe change this thread to my real xda account?
Don't forget to join our Discord server! You will get latest updates and be able to talk with us about what problems you might have. https://discord.gg/nNaA5jfY93
This is currently the port status (I might not update it here, join the Discord for latest information)
Working
-Camera
-Data
-SMS
-Screen + Touch
-Bluetooth
-Torch
-Battery
-WiFi
-Some more that I likely missed
Broken
-Sometimes auto rotation
-MMS?
-Sensors as in Gyroscope, Accelerometer, etc. (Unsupported on Halium 9)
-Fingerprint Reader (UBPorts doesn't support under screen fingerprint readers yet)
-Front camera (depending on what vendor.img you choose to use)
On the Discord, we also put a guide on how to install Anbox. Have fun!
How add google account on ubuntu,,the browser didnt support it when i try,,and is ubuntu support recovery?,can we run android apk on ubuntu?
muphetz said:
How add google account on ubuntu,,the browser didnt support it when i try,,and is ubuntu support recovery?,can we run android apk on ubuntu?
Click to expand...
Click to collapse
You can go to discord link and attempt to install anbox. Techwizz I believe had some success. I'm not sure about google account in browser. I have connected to my Gmail from there but account in setting I don't think works for google accounts. I believe google doesn't allow it. But if you go to www.google.com you should be able to sign in on top right.
muphetz said:
How add google account on ubuntu,,the browser didnt support it when i try,,and is ubuntu support recovery?,can we run android apk on ubuntu?
Click to expand...
Click to collapse
Also if you guys want to change the screen size for now us the ut tweak tool in the appstore. Sometimes wifi scanning networks don't show up so use the same tool to restart unity 8. Neat little tool for things
muphetz said:
How add google account on ubuntu,,the browser didnt support it when i try,,and is ubuntu support recovery?,can we run android apk on ubuntu?
Click to expand...
Click to collapse
We haven't got the Ubuntu Touch recovery working quite yet, but that's on our to-do list! Also following up on Anbox, it doesn't seem to work in the latest version of UBPorts but I believe the devs plan on adding better support back in.
ram9200 said:
[GSI][arm64][A/AB] Ubuntu Touch (ubports)
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included...
forum.xda-developers.com
In order to flash Halium on a Guacamole device, you need the stock Android 9 firmware. For Global: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7 Pro/9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip/download For EU: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7 Pro/9.5.11-GM21BA-OnePlus7ProOxygen_21.E.15_OTA_015_all_1907281610_ce0f1a6b7c8-FASTBOOT.zip/download Next make sure your firmware actually boots.
Next enable developer options and enable usb debugging.
Reboot to twrp and format data.
Next you need to install Lineage 16 which can obtained from http://dlr.ovh:8080/guacamole/lineage-16.0-20200325-nightly-guacamole-signed.zip
let it boot, reboot to twrp and format data
Now you can flash halium-boot.img, in twrp install.img/boot.img which the current version can be obtained below.
Then obtain your GSI image. For UBPorts, the latest can be found below
Flash your GSI image.
TWRP image: https://sourceforge.net/projects/ma...uacamole-unified-Pie-mauronofrio.img/download(edited)
Downgrade 11 to 10: https://oxygenos.oneplus.net/OnePlu...all_2010191035_downgrade_22b70083812944e2.zip
Downgrade 10 to 9: https://oxygenos.oneplus.net/fulldowngrade_wipe_MSM_18857_190505_1527_user.zip
Halium Boot: https://drive.google.com/file/d/1PWmTUbDbysXLDBiIfZXd4OKcJAcw4KT-/view?usp=sharing
Ubports GSI: https://drive.google.com/file/d/1ZxaQ3FshR8q4mphFJVSOa9d8pCoz57L9/view?usp=sharing
Sources: https://github.com/RyanAM
Click to expand...
Click to collapse
thanks for this OP
can i ask , does this work with dual boot ?
ram9200 said:
[GSI][arm64][A/AB] Ubuntu Touch (ubports)
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included...
forum.xda-developers.com
In order to flash Halium on a Guacamole device, you need the stock Android 9 firmware. For Global: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7 Pro/9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip/download For EU: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7 Pro/9.5.11-GM21BA-OnePlus7ProOxygen_21.E.15_OTA_015_all_1907281610_ce0f1a6b7c8-FASTBOOT.zip/download Next make sure your firmware actually boots.
Next enable developer options and enable usb debugging.
Reboot to twrp and format data.
Next you need to install Lineage 16 which can obtained from http://dlr.ovh:8080/guacamole/lineage-16.0-20200325-nightly-guacamole-signed.zip
let it boot, reboot to twrp and format data
Now you can flash halium-boot.img, in twrp install.img/boot.img which the current version can be obtained below.
Then obtain your GSI image. For UBPorts, the latest can be found below
Flash your GSI image.
TWRP image: https://sourceforge.net/projects/ma...uacamole-unified-Pie-mauronofrio.img/download(edited)
Downgrade 11 to 10: https://oxygenos.oneplus.net/OnePlu...all_2010191035_downgrade_22b70083812944e2.zip
Downgrade 10 to 9: https://oxygenos.oneplus.net/fulldowngrade_wipe_MSM_18857_190505_1527_user.zip
Halium Boot: https://drive.google.com/file/d/1PWmTUbDbysXLDBiIfZXd4OKcJAcw4KT-/view?usp=sharing
Ubports GSI: https://drive.google.com/file/d/1ZxaQ3FshR8q4mphFJVSOa9d8pCoz57L9/view?usp=sharing
Sources: https://github.com/RyanAM
Click to expand...
Click to collapse
Hey you guy. I just wanna say ty so much. I have been trying to get this for what maybe a year and half maybe a year i really dont know. I cant tell you how may hours i wasted just to brick my phone. But this is great ty.
dtgo said:
thanks for this OP
can i ask , does this work with dual boot ?
Click to expand...
Click to collapse
In theory yes but you might need to compile Lineage removing the force encrypt stuff, I'm assuming modifying the fstab is enough.
amaroney55 said:
Hey you guy. I just wanna say ty so much. I have been trying to get this for what maybe a year and half maybe a year i really dont know. I cant tell you how may hours i wasted just to brick my phone. But this is great ty.
Click to expand...
Click to collapse
No problem bud, enjoy!
Maybe if you inst
dtgo said:
thanks for this OP
can i ask , does this work with dual boot ?
Click to expand...
Click to collapse
You could try installing to say system_b. I haven't tried this however. You would still have to fastboot boot twrp.img everytime however. As I said again though I haven't tried this!
ram9200 said:
Maybe if you inst
You could try installing to say system_b. I haven't tried this however. You would still have to fastboot boot twrp.img everytime however. As I said again though I haven't tried this!
Click to expand...
Click to collapse
But halium-boot.img will only boot ubports...
ram9200 said:
Maybe if you inst
You could try installing to say system_b. I haven't tried this however. You would still have to fastboot boot twrp.img everytime however. As I said again though I haven't tried this!
Click to expand...
Click to collapse
The problem here is force encrypt makes it so you can't use your /data partition until you decrypt your phone, so you need to compile LOS without force encrypt or disable it some other way.
Techwizz01 said:
The problem here is force encrypt makes it so you can't use your /data partition until you decrypt your phone, so you need to compile LOS without force encrypt or disable it some other way.
Click to expand...
Click to collapse
Oh and there's this app for switching slots btw (has an Android version too) https://open-store.io/app/switch-my-slot.shouko
I do kn
Techwizz01 said:
Oh and there's this app for switching slots btw (has an Android version too) https://open-store.io/app/switch-my-slot.shouko
Click to expand...
Click to collapse
I do know the oneplus6 can do this but haven't investigated. You may research some there. I haven't run nothing but ubuntu touch on my phone since I got it working.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Motorola G 5G Plus/ Motorola One G 5G
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction:
This is the Official Lineage OS 20 thread for the Motorola G 5G Plus/Motorola One 5G, codename Nairo.Join our Motorola G 5G Plus / Motorola One 5G Development Telegram Group!
LINKS:
ROM/Recovery: LineageOS-20 - Latest Official BuildsMind The Gapps: DownloadMagisk: MagiskFactory Firmware: Stock Firmware MirrorCopy Partitions: copypartitions.zip
How to Install:
LineageOS Wiki
Contributors[/B]
erfanoabdi, SyberHexen, Jleeblanch
Source Code: https://github.com/LineageOS/
ROM OS Version: Android 13
ROM Kernel: Linux 4.19
Based On: LineageOS
Version Information
Status: Stable
reserved 1
reserved 2
Thanks alot.
What is not working?
I can't wait for a lineage os 19 I saw the source code for it and I know there is a pixel experience with Android 12 available
Hmmm... nairo-twrp-3.6.0_11.0_RC-1.0.img linked above boots, but no touchscreen (from V- + Power or CLI fastboot reboot bootloader). I have a twrp-3.5.0-1-nairo.img from a previous Arrow OS load that does... is that safe to use to load the Lineage OS?
Note to self: no, no you can't. Corrupt OS message from recovery after trying to reboot. Also storage appears encrypted still from "install Magisk" step, guess that should have been a warning. Sigh.
Flash back to stock again, sigh. At least that seems to recover everything.
we do really need a hero who can create a nairo twrp, this version boots with android 12 on nairo but touch doesnt work :c
Tommy0000 said:
we do really need a hero who can create a nairo twrp, this version boots with android 12 on nairo but touch doesnt work :c
Click to expand...
Click to collapse
wait a min or 2 for touch screen
1. is there any screen shots ?
2. what the step 04 does ?
Emerald_N8 said:
1. is there any screen shots ?
2. what the step 04 does ?
Click to expand...
Click to collapse
Step 4 will prevent you from bricking as it's common slot_b tends to be empty or not correctly setup on Motorola phones.
Esentially it copies the bootloader partitions from a -> b
Emerald_N8 said:
1. is there any screen shots ?
2. what the step 04 does ?
Click to expand...
Click to collapse
Step 4 will prevent you from bricking as it's common slot_b tends to be empty or not correctly setup on Motorola phones.
Esentially it copies the bootloader partitions from a -> b
wesleyvanneck12345678 said:
wait a min or 2 for touch screen
Click to expand...
Click to collapse
Hey wesley,
i'm currently trying to flash my motorola.
the touchscreen will not respond. i have waited for a coulple of minutes, but no avail.
are there any tricks to make it work?
best regards
EDIT :
My first try was TWRP-3.6.0_11.0_RC-1.0.img. This did not work
I've Downloaded "twrp 3.5.0", and i had to wait one or two minutes for the touchscreen to start work
TWRP 3.6.0 did not work for me.
EDIT2:
i was not able to flash the newest zip (03.24) on my "vanilla" phone but the first one worked well.
The 27.1.2022
Also Install the Pico gapps. i could not flash the nano package
best regards
bendedheadtube said:
Hey wesley,
i'm currently trying to flash my motorola.
the touchscreen will not respond. i have waited for a coulple of minutes, but no avail.
Click to expand...
Click to collapse
As a workaround I used a keyboard / trackpad combo via a 2.4 GHz dongle (china mini keyboard) and was able to use above linked TWRP 3.6.0_11.0_RC-1.0
bendedheadtube said:
Hey wesley,
i'm currently trying to flash my motorola.
the touchscreen will not respond. i have waited for a coulple of minutes, but no avail.
are there any tricks to make it work?
best regards
EDIT :
My first try was TWRP-3.6.0_11.0_RC-1.0.img. This did not work
I've Downloaded "twrp 3.5.0", and i had to wait one or two minutes for the touchscreen to start work
TWRP 3.6.0 did not work for me.
EDIT2:
i was not able to flash the newest zip (03.24) on my "vanilla" phone but the first one worked well.
The 27.1.2022
Also Install the Pico gapps. i could not flash the nano package
best regards
Click to expand...
Click to collapse
touch works for me after phew seconds on 3.6.0
The flash was succsessful to a lineage version. so the twrp is no longer a problem
I think my problem with (03.24) was a misunderstanding with slot A and slot B.
i can't change them within the lineageos bootloader.
i was able to get 3.24 running after a couple of tries (and factory resets)
one of the tries showed no mobile data available.
i was able to fix it with "factory resets" and reflashing until it worked again.
But then the gps was not working. a couple of satellites in view, but no in use.
until i found a note in my old google keep from 2016:
" fastboot erase modemst1 "
" fastboot erase modemst2 "
facepalm. so one of the factory resets was unnecessary.
so a small hint for all people :
1) wireless mouse is a good hint, for twrp 3.6.0
2) fastboot to erase the gps data, then it will work again.
3) pico gapps
can someone check if there is a wireless display option in cast setting on this custom rom ?
or can this custom rom mirror screen to a tv or mirror screen to a laptop (or a pc with a wifi dongle ) via project settings in windows 10 ?
Emerald_N8 said:
can someone check if there is a wireless display option in cast setting on this custom rom ?
or can this custom rom mirror screen to a tv or mirror screen to a laptop (or a pc with a wifi dongle ) via project settings in windows 10 ?
Click to expand...
Click to collapse
Sorry, i don't have devices to test your request.
Is this Rom still in development, or is the development in "freeze" because there is now an official lineageos rom
LineageOS Downloads
download.lineageos.org
bendedheadtube said:
Sorry, i don't have devices to test your request.
Is this Rom still in development, or is the development in "freeze" because there is now an official lineageos rom
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
just compare the maintainers ;-)
justtogetit said:
just compare the maintainers ;-)
Click to expand...
Click to collapse
where too look for the maintainers name ?