Self-made TWRP 3.2.3-0 recovery for MIX 2S
It's official now!
Please go to https://twrp.me/xiaomi/xiaomimimix2s.html to download.
Updates:
v15 (2019-01-09):
Built against latest omni-9.0 tree and lineage-16.0 polaris kernel
This should fix the decryption issue on android 9.0 roms with 2019-01 security patches. If v14 works for you, then no need to flash this.
v14 (2018-12-09):
Built against latest omni-9.0 tree
This should fix the decryption issue on latest android 9.0 roms. If v13 works for you, then no need to flash this.
v13 (2018-11-21):
Fixed wiping issue
v12 (2018-11-16):
Built against latest omni-9.0 tree
This should fix the decryption issue on latest android 9.0 roms. If v11 works for you, then no need to flash this.
v11 (2018-10-12):
Built against latest omni-9.0 tree
This should fix the decryption issue on latest android 9.0 roms
v10 (2018-09-25):
Fixed wiping issue
v9 (2018-09-24):
Built against omni-9.0 tree, updated blobs from MIUI 10 Pie
Fixed android 9.0 decryption
NOTE: If you are on android 8.0/8.1, please use v8, I don't know if v9 would work with oreo
v8 (2018-08-03):
Synced with latest twrp code, version number now 3.2.3-0
v7 (2018-07-20):
Updated kernel and blobs to MIUI 10 8.7.19, fixed the non-booting issue after 8.7.16. Thanks for @simonsmh for fixing!
Synced with latest twrp code, version number now 3.2.2-0
Re-enabled MTP mode. If you have problems like crashing, please detach your device from usb.
v6 (2018-06-09):
Fixed wrong color in screenshots (thanks @wzsx150 for reporting)
Disabled USB MTP mode.
Note: This version has disabled USB MTP mode to take a try to fix the non-responsive problem as @TimesLeader suggested. If you need MTP feature, please stick to v5 and wait for TWRP fixing it.
v5 (2018-06-06):
Synced with latest omni and TWRP code (git-25b850d to git-ff9d097).
touch vibration now works.
removed the TW_BLANK_SCREEN_ON_BOOT option.
note: If you encountered the non-responsive problem, please try to get me some logs (adb logcat, dmesg, etc). Reboot will recover from it.
v4 (2018-06-03):
Synced with latest TWRP code (git-72638b6 to git-bf4f24f, reverted 34ad728).
Thanks @simonsmh for various fixes and cleanups!
v3 (2018-05-26):
No longer laggy UI! Thanks TWRP for their fix!
Also thanks @joemossjr for a stuck-in-blank-screen problem.
v2 (2018-05-21):
Fixed the keystore problem. Now you can safely decrypt the /data partition.
Disclaimer:
Use this at your own risk!
Works:
ADB
Decryption of /data
Screen brightness settings
Smooth UI
Touch vibration
Usage:
Reboot to fastboot mode (unplug, poweroff, vol-dn+power until fastboot appears), then execute:
fastboot boot recovery.img
If your phone got stuck in "Downloading boot.img...", just reboot phone (long press power button) and try again.
Flash to recovery partition (thanks for @sytayeth for testing):
fastboot flash recovery recovery.img
Source code and compile guide:
https://github.com/notsyncing/android_device_xiaomi_polaris
v15 Download: https://drive.google.com/open?id=10jqnlc0sVv0oWH2hYkxUglO5QhJwmnQd
sha256: 508695c7b82933c413cf6521a3deb1b012fe34e155ebf21d2a6f2e69338e9ce4
md5: baf3fa355339e0574b95897ec6a961a7
v14 Download: https://drive.google.com/open?id=1Mhe0BF613HGWwt1gc_95vuXB-ETci6sb
sha256: 16a977900abf77dedf75195239f122e0368d512ba9feb7fe0803823a3585c607
md5: bbb2b7054cd52b72326bf2c39188ebe2
v13 Download: https://drive.google.com/open?id=1nzqC1gKeI-XogjcUX4ZURz0OUT9Rshcg
sha256: dc4c37fdeeaa2a12de9c54c292f0275de02497b0ec0866dca254b625fbc494a7
md5: 404b9d4f22fa22d862c7b60db9d933bc
v8 Download: https://drive.google.com/open?id=1Ge3WuWjjKoHWPIe9jvCtK2kGihHDE8Pm
v8 recovery.img:
sha256: 12b864620650ce55efa9971be89c14eb497cc9ca65cea2e5cee3d5e7b623bb9e
md5: 6c55b55b6408111e9b8bbc50b4364317
Thanks:
@Travismills82 for his TWRP tree used as skeleton: https://github.com/travismills82/twrp_android_device_samsung_star2qltechn
@teamwin for sagit TWRP tree used for partial decryption works: https://github.com/TeamWin/android_device_xiaomi_sagit
@TimesLeader for dipper TWRP tree used for adb works:android_device_xiaomi_dipper
@wuxianlin for enchilada TWRP tree used for init.rc works:android_device_oneplus_enchilada
Do you think this recovery can be flashed from the other one that we have???
Sorry, I just read now that it's not tested.
Cool thx!
why does it so lag?lol
sytayeth said:
Do you think this recovery can be flashed from the other one that we have???
Sorry, I just read now that it's not tested.
Click to expand...
Click to collapse
it should work, but I didn't try it, because on reboot it will be replaced by MIUI recovery
ghost_nup said:
why does it so lag?lol
Click to expand...
Click to collapse
Yes, it lags, but at this moment, I don't know why and have no clue to resolve it
notsyncing said:
Yes, it lags, but at this moment, I don't know why and have no clue to resolve it
Click to expand...
Click to collapse
The one posted in xiaomi.eu thread lags too, there it has not been resolved until now too
Cool!
Sorry but this is exactly the same posted with almost the release of the phone. You stating you made it yourself?
Puksom said:
Sorry but this is exactly the same posted with almost the release of the phone. You stating you made it yourself?
Click to expand...
Click to collapse
The other release doesn't support /data decryption
notsyncing said:
it should work, but I didn't try it, because on reboot it will be replaced by MIUI recovery
Click to expand...
Click to collapse
Yes, It works.
martepato said:
The other release doesn't support /data decryption
Click to expand...
Click to collapse
Thank you, after my test, you can indeed confidential data partition.
im trying to build it from your source but it just stays at a black screen
joemossjr said:
im trying to build it from your source but it just stays at a black screen
Click to expand...
Click to collapse
You could try adb logcat to see if adb started.
Is there any screen flashing? or just black screen?
Also, check the TARGET_RECOVERY_PIXEL_FORMAT workaround on README, or you could experience black screen with flashing.
Can you hit me up on Hangouts? I have made 20 builds today all with the same problem lol my email is [email protected]
---------- Post added at 04:28 AM ---------- Previous post was at 04:27 AM ----------
It's just a black screen adb does start tho
joemossjr said:
Can you hit me up on Hangouts? I have made 20 builds today all with the same problem lol my email is [email protected]
---------- Post added at 04:28 AM ---------- Previous post was at 04:27 AM ----------
It's just a black screen adb does start tho
Click to expand...
Click to collapse
sent you a message on hangout, please check it
New twrp in the op
joemossjr said:
New twrp in the op
Click to expand...
Click to collapse
Thank you so much. Really appreciate your work.
joemossjr said:
New twrp in the op
Click to expand...
Click to collapse
Thanks for your work, this is really helpful.
It's noty work it's the ops work. I just helped with the black screen issue and laggy twrp
Related
RECOVERY
TWRP & CM-Recovery
Z00A/Z008 ( LP Bootloader)
Just as the title says these are unofficial recovery builds for Asus Zenfone 2 Z00A and Z008 models
These have been tested and confirmed functional. These are built from current CM devices trees, CM kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 2.8.7.3 (LP based)
TWRP 2.8.7.7 (M based)
CM-Recovery 9-28-15 (LP based)
CM-Recovery 12-22-15 (M based)
{ Cm-Recovery doesn't use "version" tags so using build date as a version # }
SOURCES
Recovery built in a CM-12.1/13.0 environment respectively using device trees/kernel
from our CM device trees/kernel CM-zenfone2 github
Z00A LP Tree HERE
Z008 LP Tree HERE
Z00A M Tree HERE
Z008 M Tree HERE
Kernel Source
CM-Recovery source from CM-recovery
TWRP source tyipically from Omnirom
HOWEVER 2.8.7.6 beta uses modified TWRP source from omnirom (and patched from thier gerrit) from
HERE
Code:
Changelog:
1-22-16:
TWRP 2.8.7.7
- fixed OTG & external SDCARD mount
- from TWRP: language support, code cleanup and minor fixes(see twrp github for full list)
- this is pre-release testing main ly for soon to be released TWRP 3.0
12-22-15:
* updated builds
* should fix backups in TWRP
* should fix issues flashing newer ROMS after 12-17-15
12-7-15
* 2.8.7.5 TWRP builds
* fixed opengapps flashing
12-6-15
* split into new thread
* Marshmallow based recoveries now live
* TWRP is WIP prior to next major official tag, new theme included for testing
Z00A/Z008 ( MM Bootloader)
Just as the title says these are unofficial recovery builds for Asus Zenfone 2 Z00A and Z008 models
These have been tested and confirmed functional. These are built from current CM devices trees, CM kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 3.0.2-M1 (MM based)
SOURCES
Recovery built in a Omnirom-6.0 environment respectively using device trees/kernel below
Z00A/Z008 MM Tree HERE
Kernel Source HERE
TWRP source tyipically from Omnirom
Code:
Changelog:
Initial source built MM bootloader friendly based recovery release
Z00D
Just as the title says these are unnoficial recovery builds for the Asus Zenfone 2 Z00D (ze500cl) model
These have been tested and confirmed functional. These are built from experimental devices trees, modified Stock kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 3.0.2-0
SOURCES
Recovery built in a omnirom environment respectively using device trees/kernel
from our my github
Device Tree
Kernel Source
Code:
Changelog:
5-3-16: Initial TWRP build
XDA:DevDB Information
Zenfone2 Recovery, Tool/Utility for the Asus ZenFone 2
Contributors
jrior001, crpalmer
Source Code: https://github.com/CM-zenfone2
Version Information
Status: Beta
Beta Release Date: 2015-12-06
Created 2015-12-07
Last Updated 2016-08-03
Niceeeeeeeeeeeeeeeee
Well this was unexpected, thank you so much for this!
Edit: Well I tried the MM version, and I must say I love the new look! It's kinda laggy, but that's very expected and I got a recovery log.
Aceofzeroz said:
It's kinda laggy, but that's very expected and I got a recovery log.
Click to expand...
Click to collapse
TWRP still uses some really old code for pixelflinger. We have been using a JB era patch from Intel to add x86 optimized acceleration, which Dees_Troy(TWRP dev) and the zenfone5/6 devs ported to KK & LP. I updated it for M, but this is about as good as it gets until TWRP overhauls that section of their code. Without this patch is basically unusable.
And yes the new theme is sexy It's months in the making from TWRP contributer @z31s1g and it's quite lovely.
jrior001 said:
TWRP still uses some really old code for pixelflinger. We have been using a JB era patch from Intel to add x86 optimized acceleration, which Dees_Troy(TWRP dev) and the zenfone5/6 devs ported to KK & LP. I updated it for M, but this is about as good as it gets until TWRP overhauls that section of their code. Without this patch is basically unusable.
And yes the new theme is sexy It's months in the making from TWRP contributer @z31s1g and it's quite lovely.
Click to expand...
Click to collapse
Ah, I understand the situation now and glad that the patch worked out for the time being. Definitely better than not having the latest TWRP to play with, so my highest gratitude for the amazing work bringing up Marshmallow in time for the holidays! :thumbup:
Sent from the Ace's MB865 using Tapatalk
This is a bit wonky with device encryption. It'll boot the recovery without a theme loaded and ask for my pattern (as expected). I'll put that in and it'll decrypt and mount storage, then the "put in your pattern" prompt comes up again (this time, with my twrp theme loaded). I can cancel that prompt just fine and it'll sit on the main screen and I can proceed from there, so it's not a showstopper at least.
This didn't happen on 2.8.7.3.
edit: on flashing opengapps 6.0 micro, I'm warned that the recovery is missing the xz binary and can't flash the zip (and told me to update to the latest recovery for my device, lol). I'll upload the generated log shortly.
edit edit:
Code:
# Begin Open GApps Install Log
-----------------------------------------------------------------------------
ROM Android Version | 6.0
-----------------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: The installer detected that your recovery does not support
XZ decompression. Please update your recovery or switch to another one like TWRP.
# Begin User's gapps-config
# End User's gapps-config
Fortunately, flashing my L-gapps seems to have worked fine (...seeeeeems to. I'll see if it works. The setup app did at least update itself, so there's that.)
Is there an easy way to update my TWRP? Any apps that can do this for me?
roach9 said:
Is there an easy way to update my TWRP? Any apps that can do this for me?
Click to expand...
Click to collapse
I know Flashify can do that in many devices, I am not sure about ours, I think best way would be to flash it using fastboot.
Marshmallow recovery can be used to flash lollipop Rom...??..and vice versa...??
Any difference for 2.8.7.4 vs .3 other than the look? Googled it and found nothing.
Sayan44 said:
I know Flashify can do that in many devices, I am not sure about ours, I think best way would be to flash it using fastboot.
Click to expand...
Click to collapse
Why not via TWRP itself? TWRP has a feature to flash an .img directly to boot or recovery.
Sent from my ASUS_Z00AD
I am on 2.8.7.3. I am thinking to flash cm13. Is it necessary to update twrp? Or I can flash cm13 using my old one?
Sent from my ASUS_Z00A using Tapatalk
rex_perfect said:
Marshmallow recovery can be used to flash lollipop Rom...??..and vice versa...??
Click to expand...
Click to collapse
Pretty much, LP version is stable and works for flashing M ROMs.
Sent from my ASUS_Z00A using Tapatalk
espeon said:
This is a bit wonky with device encryption. It'll boot the recovery without a theme loaded and ask for my pattern (as expected). I'll put that in and it'll decrypt and mount storage, then the "put in your pattern" prompt comes up again (this time, with my twrp theme loaded). I can cancel that prompt just fine and it'll sit on the main screen and I can proceed from there, so it's not a showstopper at least.
This didn't happen on 2.8.7.3.
edit: on flashing opengapps 6.0 micro, I'm warned that the recovery is missing the xz binary and can't flash the zip (and told me to update to the latest recovery for my device, lol). I'll upload the generated log shortly.
edit edit:
Code:
# Begin Open GApps Install Log
-----------------------------------------------------------------------------
ROM Android Version | 6.0
-----------------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: The installer detected that your recovery does not support
XZ decompression. Please update your recovery or switch to another one like TWRP.
# Begin User's gapps-config
# End User's gapps-config
Fortunately, flashing my L-gapps seems to have worked fine (...seeeeeems to. I'll see if it works. The setup app did at least update itself, so there's that.)
Click to expand...
Click to collapse
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
So what's the difference of this TWRP and TheSSJ TWRP?
jrior001 said:
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
The 2nd one happened after I decrypted; I forgot to mention that. I don't think it actually happened when I was encrypted using the L-based recovery (I upgraded my recovery, then decrypted, then tried flashing the rom + gapps)
Thread moved to proper forum
jrior001 said:
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Having the same issue actually, not encrypted, worked on .3 no pin or lock on screen either. Happened trying to install the latest Gapps package.
Heavybullets said:
Having the same issue actually, not encrypted, worked on .3 no pin or lock on screen either. Happened trying to install the latest Gapps package.
Click to expand...
Click to collapse
ended up fastboot installing the recovory, didnt work, factory reset, then try it, didn't work, fixing permissions, all that, nothing has worked for me, the latest .4 twrp still comes up with that "The installer detected that your recovery does not support
XZ decompression." Error.
Heavybullets said:
ended up fastboot installing the recovory, didnt work, factory reset, then try it, didn't work, fixing permissions, all that, nothing has worked for me, the latest .4 twrp still comes up with that "The installer detected that your recovery does not support
XZ decompression." Error.
Click to expand...
Click to collapse
well yeah when you have a missing binary reflashing it probably isn't going to do anything, assuming it didn't get corrupted
TWRP 3.0.2-0 is out now for all currently supported devices.
What’s new in 3.0.2-0:
Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
Add Greek translation to some builds.
TWRP 3.0.2.0 for sprout4 (Tested on Karbonn Sparkle V)
Download link: https://drive.google.com/file/d/0By0nqyW_a9Bsbm1lWGwzcHk0Tk0/view?usp=sharing
Mirror link: https://mega.nz/#!BZVz0RRA!zL96iTDs1mrNAx5epoi9xNt1HIOU2b1PbVRHKPsQpn8
hello, will this work with sprout 8 too?
johngare said:
hello, will this work with sprout 8 too?
Click to expand...
Click to collapse
I tested on only on sprout4 (Karbonn Sparkle V). If they work on same kernel, it should boot up, otherwise it won't.
Marius (TMT) said:
I tested on only on sprout4 (Karbonn Sparkle V). If they work on same kernel, it should boot up, otherwise it won't.
Click to expand...
Click to collapse
I am looking for a tester for my builds of the recovery (TWRP says they need a new maintainer for sprout). Anyone on board?
MSF Jarvis said:
I am looking for a tester for my builds of the recovery (TWRP says they need a new maintainer for sprout). Anyone on board?
Click to expand...
Click to collapse
Count me in.
KcLKcL said:
Count me in.
Click to expand...
Click to collapse
Counted. Stay tuned.
Thanks for update. Working great on my canvas A1.
rajputmiles said:
Thanks for update. Working great on my canvas A1.
Click to expand...
Click to collapse
KcLKcL said:
Count me in.
Click to expand...
Click to collapse
Here is the source-built TWRP 3.0.2-0 recovery for sprout(4|8) devices. Test everything out and then we can make it official.
Cheers,
Jarvis
MSF Jarvis said:
Here is the source-built TWRP 3.0.2-0 recovery for sprout(4|8) devices. Test everything out and then we can make it official.
Cheers,
Jarvis
Click to expand...
Click to collapse
Downloading... Will report tomorrow.
Edit: sorry didn't know you have to submit reports today.
rajputmiles said:
Downloading... Will report tomorrow.
Click to expand...
Click to collapse
TOMORROW!! Oh, Come on, I've got to submit the device tree to @Dees_Troy tonight to get it official.
MSF Jarvis said:
TOMORROW!! Oh, Come on, I've got to submit the device tree to @Dees_Troy tonight to get it official.
Click to expand...
Click to collapse
Okay report within 3 hours
rajputmiles said:
Okay 3 hours.
Click to expand...
Click to collapse
It's just a recovery! Make a backup, restore it, Flash a ROM and then say it works. Actually, if it boots up, I can assume it will work completely. At least help me with that. It's for YOUR benefit. I don't even have the device!
MSF Jarvis said:
It's just a recovery! Make a backup, restore it, Flash a ROM and then say it works. Actually, if it boots up, I can assume it will work completely. At least help me with that. It's for YOUR benefit. I don't even have the device!
Click to expand...
Click to collapse
Okay first of all thanks for your work for this device tree. It's just I was busy in something. And I know what it is to test a recovery.
Report :
Recovery img doesn't get boot up(tried via fastboot & flashify too). I tried rebooting to recovery like 3 times & Black screen comes for like 2 seconds and then it automatic reboots the system -->> starts the rom.
MSF Jarvis said:
Here is the source-built TWRP 3.0.2-0 recovery for sprout(4|8) devices. Test everything out and then we can make it official.
Cheers,
Jarvis
Click to expand...
Click to collapse
Unfortunately , I am sorry to tell source-built twrp 3.0.2-0 did not boot up.... (flased via fastboot...but it won't get into recovery.....just reboots system...). I am back on my ported twrp 3.0.2-0.
rajputmiles said:
Okay first of all thanks for your work for this device tree. It's just I was busy in something. And I know what it is to test a recovery.
Report :
Recovery img doesn't get boot up(tried via fastboot & flashify too). I tried rebooting to recovery like 3 times & Black screen comes for like 2 seconds and then it automatic reboots the system -->> starts the rom.
Click to expand...
Click to collapse
Marius (TMT) said:
Unfortunately , I am sorry to tell source-built twrp 3.0.2-0 did not boot up.... (flased via fastboot...but it won't get into recovery.....just reboots system...). I am back on my ported twrp 3.0.2-0.
Click to expand...
Click to collapse
So apparently @varun.chitre15's ThunderZap kernel doesn't like being used for TWRP. I'll try with AOSP source.
---------- Post added at 11:16 PM ---------- Previous post was at 10:35 PM ----------
rajputmiles said:
Okay first of all thanks for your work for this device tree. It's just I was busy in something. And I know what it is to test a recovery.
Report :
Recovery img doesn't get boot up(tried via fastboot & flashify too). I tried rebooting to recovery like 3 times & Black screen comes for like 2 seconds and then it automatic reboots the system -->> starts the rom.
Click to expand...
Click to collapse
Marius (TMT) said:
Unfortunately , I am sorry to tell source-built twrp 3.0.2-0 did not boot up.... (flased via fastboot...but it won't get into recovery.....just reboots system...). I am back on my ported twrp 3.0.2-0.
Click to expand...
Click to collapse
Another test build.
:fingers-crossed:
MSF Jarvis said:
So apparently @varun.chitre15's ThunderZap kernel doesn't like being used for TWRP. I'll try with AOSP source.
---------- Post added at 11:16 PM ---------- Previous post was at 10:35 PM ----------
Another test build.
:fingers-crossed:
Click to expand...
Click to collapse
Still no luck. Same problem. Not booting up.
rajputmiles said:
Still no luck. Same problem. Not booting up.
Click to expand...
Click to collapse
****in' final test build. If this doesn't boot, I'll go off TWRP compiling for two weeks
MSF Jarvis said:
****in' final test build. If this doesn't boot, I'll go off TWRP compiling for two weeks
Click to expand...
Click to collapse
Nope. It does not seems to boot up. Only black screen, then it reboots in android os.
MSF Jarvis said:
****in' final test build. If this doesn't boot, I'll go off TWRP compiling for two weeks
Click to expand...
Click to collapse
Still same. Recovery not booting up.
Black screen for 2 second-->> reboots into rom.
One more thing what is meant by "ThunderZap kernel doesn't like being used for TWRP". Cause cyanogen mod kernel is coming with cm snapshot release 1.
rajputmiles said:
Still same. Recovery not booting up.
Black screen for 2 second-->> reboots into rom.
One more thing what is meant by "ThunderZap kernel doesn't like being used for TWRP". Cause cyanogen mod kernel is coming with cm snapshot release 1.
Click to expand...
Click to collapse
Recovery is just a ramdisk put together with a kernel zImage. I used TZ5.2 zImage first time.
Your recovery boots, right? I'll try with your zImage, though would you mind telling me which zImage are you using ?
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DOWNLOAD: Fixed....
Things that are different from official build:
fixed wrong theme color in screenshots on OP6.
Add support for QCOM haptics vibrator. (fixed vibration)
BUGS:
mtp (causes kernel panics) (can add a test build if needed)
flashing aroma packages
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDAevDB Information
[RECOVERY][enchilada] TWRP 3.2.3-0 Touch Recovery [UNOFFICIAL]
Contributors
Joemossjr
Dees_Troy
wuxianlin
@notsyncing on github for the fixes
Source Code: Github
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Created 2018-07-07
Last Updated 2018-08-01
Donation Link: Buy this man a beer
Thanks for this. Add the version that supports MTP. Will test and let you know!
It's definitely bugged lol but I'll add it tomorrow
Thank you very much!
joemossjr said:
It's definitely bugged lol but I'll add it tomorrow
Click to expand...
Click to collapse
I'm working with your 3.2.1 version since the beginning and except aroma absolut everything is working. Never had any issue with MTP. Always worked stable so far. I did countless restores and all worked flawless even with swipe code in place.
So thanks very much to provide us with the very first working TWRP for the OP6.
Regarding aroma support, would you agree to my feeling that this is not an issue to be solved in the twrp framework but probably being a bootloader or firmware issue?
Simple temporary fix to avoid kernel panic on mtp:
Do not connect usb cable
Toogle unmount mtp, wait few second and enable mtp again in mount menu in recovery. Connect usb.
xXx said:
I'm working with your 3.2.1 version since the beginning and except aroma absolut everything is working. Never had any issue with MTP. Always worked stable so far. I did countless restores and all worked flawless even with swipe code in place.
So thanks very much to provide us with the very first working TWRP for the OP6.
Regarding aroma support, would you agree to my feeling that this is not an issue to be solved in the twrp framework but probably being a bootloader or firmware issue?
Click to expand...
Click to collapse
I'll be getting logs tonight while flashing an aroma package to see what's needed lol I feel like it's something simple but we will see. Thanks for the support everyone I do this on my free time lol I'll post the mtp enabled here shortly
mtp has been added to the downloads folder and is specified in the name!
https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned
joemossjr said:
https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned
Click to expand...
Click to collapse
thanks, very much appreciated :highfive:
joemossjr said:
mtp has been added to the downloads folder and is specified in the name!
Click to expand...
Click to collapse
Yes I have tested it and can confirm it's working. Just make sure you unmount mtp and remount it before attaching the USB cable (thanks to @DocRambone for the tip)
DocRambone said:
Simple temporary fix to avoid kernel panic on mtp:
Do not connect usb cable
Toogle unmount mtp, wait few second and enable mtp again in mount menu in recovery. Connect usb.
Click to expand...
Click to collapse
This works, thanks!
It's not working for me both new versions. Boot looped.
Sent from my ONEPLUS A6003 using XDA-Developers Legacy app
mbr007 said:
It's not working for me both new versions. Boot looped.
Click to expand...
Click to collapse
Did you remember to flash magisk after reboot into twrp?
lollyjay said:
Did you remember to flash magisk after reboot into twrp?
Click to expand...
Click to collapse
Yeah you have to flash magisk if you already had it flashed before hand
joemossjr said:
mtp has been added to the downloads folder and is specified in the name!
Click to expand...
Click to collapse
I just flashed your new mtp enabled zip version and screen brightness went down considerably even it's on 100% already. Does anybody know a workaround to get it brighter again?
Can you add another mirror like androidfilehost please? Unable to access google drive...
xXx said:
I just flashed your new mtp enabled zip version and screen brightness went down considerably even it's on 100% already. Does anybody know a workaround to get it brighter again?
Click to expand...
Click to collapse
Seems to be a general problem. I've the same, but not only with this version of TWRP, also with the original version.
It starts by me sometimes flashing 3.2.1.0 if i remember right and I never found a solution to get the screen brightness full back again ?
adiher said:
Seems to be a general problem. I've the same, but not only with this version of TWRP, also with the original version.
It starts by me sometimes flashing 3.2.1.0 if i remember right and I never found a solution to get the screen brightness full back again ?
Click to expand...
Click to collapse
I can make a new build that's higher
joemossjr said:
https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned
Click to expand...
Click to collapse
Could this have anything to do with why aroma isn't working?
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page5
From the magisk 16.6 change log.
Note to ROM Developers
If you are embedding Magisk Zip into your ROM, and your ROM uses Aroma Installer, please be aware that on some devices (most likely Samsung devices), it is possible that the installation process of Magisk could break Aroma. Please test flashing your ROM zip before releasing to your users. If you found out you are the few unfortunate devices, unzip the Magisk zip, and do the following changes and re-zip the installer:
Code:
# Remove or comment out these 2 lines in META-INF/com/google/android/updater-script eval $BOOTSIGNER -verify < $BOOTIMAGE && BOOTSIGNED=true $BOOTSIGNED && ui_print "- Boot image is signed with AVB 1.0"
The reason why Aroma Installer breaks is unknown. Maybe consider letting the project that's abandoned for nearly 5 years go?
Hi
Did anyone tried GSI roms on the MI9?
Please share your experience if you did
Phh is working on treble support. As always with GSI's you'll probably have the best experiences with vanilla.
See his progress thus far here (he's making progress on indisplay fp): https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Mi-9
CrazyBeaver2377 said:
Phh is working on treble support. As always with GSI's you'll probably have the best experiences with vanilla.
See his progress thus far here (he's making progress on indisplay fp): https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Mi-9
Click to expand...
Click to collapse
Best experience with vanilla? What do you mean with vanilla? AOSP or something else?
Another question: so it would be possible to flash the GSI according to the method Phh is explaining in your link? Only the fingerprint sensor wouldnt work, right?
Finally I unlocked and flashed my FlokoROM, it's almost good for daily driver for me!
I need to fix BT in-call (by magisk patch) and rom's bug related to AOD, though.
https://treble.andro.plus/
If you need GApps on GSI, you should Repair/resize system partition in TWRP -> Wipe -> Advanced wipe and reboot recovery, mount system then flash latest OpenGApps.
I added fix for system-as-root device on OpenGApps yesterday, so you have to use 22 March or later build.
AndroPlus said:
Finally I unlocked and flashed my FlokoROM, it's almost good for daily driver for me!
I need to fix BT in-call (by magisk patch) and rom's bug related to AOD, though.
https://treble.andro.plus/
If you need GApps on GSI, you should Repair/resize system partition in TWRP -> Wipe -> Advanced wipe and reboot recovery, mount system then flash latest OpenGApps.
I added fix for system-as-root device on OpenGApps yesterday, so you have to use 22 March or later build.
Click to expand...
Click to collapse
Great. Phh is also making good progress.
Honestly i'm probably not going to daily GSI myself. I'll await device tree bringup by someone and start building some roms then.
I sent you a PM a few days ago btw
AndroPlus said:
Finally I unlocked and flashed my FlokoROM, it's almost good for daily driver for me!
I need to fix BT in-call (by magisk patch) and rom's bug related to AOD, though.
https://treble.andro.plus/
If you need GApps on GSI, you should Repair/resize system partition in TWRP -> Wipe -> Advanced wipe and reboot recovery, mount system then flash latest OpenGApps.
I added fix for system-as-root device on OpenGApps yesterday, so you have to use 22 March or later build.
Click to expand...
Click to collapse
Very nice, I wasn't expecting ROMs that soon.
Btw, is the fingerprint scanner working already? I know that phh fixed it but sources are not released yet?
AndroPlus said:
Finally I unlocked and flashed my FlokoROM, it's almost good for daily driver for me!
I need to fix BT in-call (by magisk patch) and rom's bug related to AOD, though.
https://treble.andro.plus/
If you need GApps on GSI, you should Repair/resize system partition in TWRP -> Wipe -> Advanced wipe and reboot recovery, mount system then flash latest OpenGApps.
I added fix for system-as-root device on OpenGApps yesterday, so you have to use 22 March or later build.
Click to expand...
Click to collapse
Great! Do you intend on opening up an xda thread? Also will this rom be relatively stock, or will you aim to start adding features in?
Many thanks!
AndroPlus said:
Finally I unlocked and flashed my FlokoROM, it's almost good for daily driver for me!
I need to fix BT in-call (by magisk patch) and rom's bug related to AOD, though.
https://treble.andro.plus/
If you need GApps on GSI, you should Repair/resize system partition in TWRP -> Wipe -> Advanced wipe and reboot recovery, mount system then flash latest OpenGApps.
I added fix for system-as-root device on OpenGApps yesterday, so you have to use 22 March or later build.
Click to expand...
Click to collapse
I'm so glad to see you here! I have tried the ROM. It works like a shot, the problem I see is that the fingerprint reader doesn't work and the quality of the camera is terrible. I installed the Gcam but it gives me FC. I will follow your work very closely.
Thank you! and lots of encouragement!
CrazyBeaver2377 said:
Great. Phh is also making good progress.
Honestly i'm probably not going to daily GSI myself. I'll await device tree bringup by someone and start building some roms then.
I sent you a PM a few days ago btw
Click to expand...
Click to collapse
Sorry, was busy... I won't build non-GSI as GSI is good enough for me and somehow there were too many bugs happens only on non-GSI.
cd993 said:
Great! Do you intend on opening up an xda thread? Also will this rom be relatively stock, or will you aim to start adding features in?
Many thanks!
Click to expand...
Click to collapse
No, I won't open a thread. The rom is based on crDroid (based on LOS) so there are already plenty of features.
BoRoU said:
I'm so glad to see you here! I have tried the ROM. It works like a shot, the problem I see is that the fingerprint reader doesn't work and the quality of the camera is terrible. I installed the Gcam but it gives me FC. I will follow your work very closely.
Thank you! and lots of encouragement!
Click to expand...
Click to collapse
You can use xtreme v8 version.
https://forum.xda-developers.com/Mi-9/themes/xiaomi-mi9-googlecam-port-t3910034
AndroPlus said:
Sorry, was busy... I won't build non-GSI as GSI is good enough for me and somehow there were too many bugs happens only on non-GSI.
No, I won't open a thread. The rom is based on crDroid (based on LOS) so there are already plenty of features.
You can use xtreme v8 version.
https://forum.xda-developers.com/Mi-9/themes/xiaomi-mi9-googlecam-port-t3910034
Click to expand...
Click to collapse
Thanks!
AndroPlus said:
Sorry, was busy... I won't build non-GSI as GSI is good enough for me and somehow there were too many bugs happens only on non-GSI.
Click to expand...
Click to collapse
Hmm okay that's a shame to hear. Imo device specific roms would be better with the current state of GSI's/treble. They were never really intended for daily use and/or work perfectly on a single device. I'm hoping for someone else to step up soon and start working on device tree bringup.
AndroPlus said:
You can use xtreme v8 version.
https://forum.xda-developers.com/Mi-9/themes/xiaomi-mi9-googlecam-port-t3910034
Click to expand...
Click to collapse
Well, I just installed the latest version. With the xtreme it works well! I just miss the fingerprint. However, I'm going to try it for a few hours to see how it behaves!
Thanks for the job!
AndroPlus said:
Finally I unlocked and flashed my FlokoROM, it's almost good for daily driver for me!
I need to fix BT in-call (by magisk patch) and rom's bug related to AOD, though.
https://treble.andro.plus/
If you need GApps on GSI, you should Repair/resize system partition in TWRP -> Wipe -> Advanced wipe and reboot recovery, mount system then flash latest OpenGApps.
I added fix for system-as-root device on OpenGApps yesterday, so you have to use 22 March or later build.
Click to expand...
Click to collapse
Hi. Thanks for your work. I flashed it yesterday on my Sharp Aquos S2 and it boot and works well with the fix for selinux.
AndroPlus said:
Finally I unlocked and flashed my FlokoROM, it's almost good for daily driver for me!
I need to fix BT in-call (by magisk patch) and rom's bug related to AOD, though.
https://treble.andro.plus/
If you need GApps on GSI, you should Repair/resize system partition in TWRP -> Wipe -> Advanced wipe and reboot recovery, mount system then flash latest OpenGApps.
I added fix for system-as-root device on OpenGApps yesterday, so you have to use 22 March or later build.
Click to expand...
Click to collapse
work with mi9? how about camera
@AndroPlus whats differents between 21 march and 23 march builds?
Here is magisk path for BT in-call audio and tap to wake (force enabled):
https://drive.google.com/file/d/1JVQ-Qsw-Lzj4b7IiNlZEAocHvU5EYZTr/view?usp=sharing
This module also works on other GSIs. [EDIT] only on CAF based GSI such as LOS
Vihru said:
work with mi9? how about camera
Click to expand...
Click to collapse
Default camera (Snap) is not good, so you have to install Google Camera:
https://forum.xda-developers.com/Mi-9/themes/xiaomi-mi9-googlecam-port-t3910034
It works fine and I got clearer photo compared to Redmi Note 7 (GM1).
Lovetz said:
@AndroPlus whats differents between 21 march and 23 march builds?
Click to expand...
Click to collapse
General system stability improvements to enhance the user's experience™
...if you want to check what was changed, go to GitHub and read recent commits.
https://github.com/FlokoROM
https://github.com/crdroidandroid
@AndroPlus is it possible to dirtfy flash march 23 version over march 21? What steps I must made for this? I use gapps and magisk.
is it essy to get back to xiaomi.eu? if i try this.
AndroPlus said:
Finally I unlocked and flashed my FlokoROM, it's almost good for daily driver for me!
I need to fix BT in-call (by magisk patch) and rom's bug related to AOD, though.
https://treble.andro.plus/
If you need GApps on GSI, you should Repair/resize system partition in TWRP -> Wipe -> Advanced wipe and reboot recovery, mount system then flash latest OpenGApps.
I added fix for system-as-root device on OpenGApps yesterday, so you have to use 22 March or later build.
Click to expand...
Click to collapse
i think you should make own thread for that FlokoRom? would be nice to get news about it.. screenshots etc..
Lovetz said:
@AndroPlus is it possible to dirtfy flash march 23 version over march 21? What steps I must made for this? I use gapps and magisk.
Click to expand...
Click to collapse
Yes. You should flash system img, then flash gapps zip.
Kernel source:
https://github.com/omnirom/android_kernel_nubia_nx609j
Device tree:
https://github.com/omnirom/android_device_nubia_nx609j
Download:
omni-9-20190902-nx609j-HOMEMADE.zip
TWRP: twrp-3.3.1-0_CPTB-20190901-01-SAR-NX609J.img
How to flash:
Make sure you're on latest Pie firmware
Boot to TWRP
Wipe data
Flash ROM
Optional: flash gapps
Reboot
Known issues:
-You tell me
XDA:DevDB Information
OmniROM 9.0, ROM for the ZTE nubia Red Magic
Contributors
vache
Source Code: https://github.com/omnirom
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2019-08-28
Created 2019-08-28
Last Updated 2019-09-03
It is working fine with Chinese oreo also. If anyone needs help then i can help them
Here are some screen shots
Nice, I will try it ASAP...
ABM30 said:
Nice, I will try it ASAP...
Click to expand...
Click to collapse
I had issues with Chinese firmware of pie. Twrp was not booting but for developer it was botting fine. That a why I had to flash Chinese firmware first 2.26 and then after flashing you need again flash those files in fastboot after unlocking it.
methuselah said:
I had issues with Chinese firmware of pie. Twrp was not booting but for developer it was botting fine. That a why I had to flash Chinese firmware first 2.26 and then after flashing you need again flash those files in fastboot after unlocking it.
Click to expand...
Click to collapse
How much time needs to boot up? It is already 7 min and still on omni booting animation
I think I need to start over (even i have wiped with original recovery but...)
P.S You have used 2.26 CN or 2.36CN ROM?
EDIT:
Which version of TWRP are you using? I am on 3.3.1.
EDIT 2
OK, I am in OMNI! ...with Bluespark TWRP!
@ABM30 are you on telegram?
methuselah said:
@ABM30 are you on telegram?
Click to expand...
Click to collapse
The firmware of the connection is invalid？
Where can I download omnirom9.0？
New build up !
omni-9-20190902-nx609j-HOMEMADE.zip
Install process has change, Pie firmware is new mandatory. Also make sure to use the TWRP linked in OP.
Changelog:
Switch to P kernel sources
Fixed encryption
Fixed WFD (Wifi display)
...
vache said:
omni-9-20190902-nx609j-HOMEMADE.zip
Install process has change, Pie firmware is new mandatory. Also make sure to use the TWRP linked in OP.
Changelog:
Switch to P kernel sources
Fixed encryption
Fixed WFD (Wifi display)
...
Click to expand...
Click to collapse
So it begun
navik said:
The firmware of the connection is invalid？
Where can I download omnirom9.0？
Click to expand...
Click to collapse
Download the 3.19 Chinese firmware and flash that first.
Thank you so much, i will try it in this week, and spread this on red magic pages comments, everyone already seems hopeless... Thanks @vache, thanks @methuselah too ?
Thank you so much, i will try it in this week, and spread this on red magic pages comments, everyone already seems hopeless... Thanks @vache, thanks @methuselah too ?
ianseer said:
Thank you so much, i will try it in this week, and spread this on red magic pages comments, everyone already seems hopeless... Thanks @vache, thanks @methuselah too ?
Click to expand...
Click to collapse
Thanks @vache only. Not me. He is the only one because of which we got omni pie.
Btw... The RGB light features, is it gone? Or we need to port it from the cn rom to get such features?
methuselah said:
So it begun
Download the 3.19 Chinese firmware and flash that first.
Click to expand...
Click to collapse
i need to install chinese first then in twrp wipe system and data then flash the omnirom 9.0 right?
i need to wipe system or leave it?
alrfa3y-1 said:
i need to install chinese first then in twrp wipe system and data then flash the omnirom 9.0 right?
i need to wipe system or leave it?
Click to expand...
Click to collapse
Yes first install chinese, then unlock Boot loader and flash given twrp in this thread. And then wipe everything except internal storage. Flash omni and gapps.
ianseer said:
Btw... The RGB light features, is it gone? Or we need to port it from the cn rom to get such features?
Click to expand...
Click to collapse
I guess it won't be coming. Its not part of aosp code so. The effects are not gonna be tweaked I guess. Back led perfectly fine.
methuselah said:
Yes first install chinese, then unlock Boot loader and flash given twrp in this thread. And then wipe everything except internal storage. Flash omni and gapps.
I guess it won't be coming. Its not part of aosp code so. The effects are not gonna be tweaked I guess. Back led perfectly fine.
Click to expand...
Click to collapse
thank you very much man ?
methuselah said:
Yes first install chinese, then unlock Boot loader and flash given twrp in this thread. And then wipe everything except internal storage. Flash omni and gapps.
I guess it won't be coming. Its not part of aosp code so. The effects are not gonna be tweaked I guess. Back led perfectly fine.
Click to expand...
Click to collapse
hi please can you confirm the rom is stable ?
if ok i will try ?
alrfa3y-1 said:
hi please can you confirm the rom is stable ?
if ok i will try ?
Click to expand...
Click to collapse
It's better than official in everyway. Latest security patch. What do you need
i flash the rom without gapps its work fine but wiht nano gapps stock in bootloob
i dont know why
---------- Post added at 02:10 PM ---------- Previous post was at 02:09 PM ----------
methuselah said:
It's better than official in everyway. Latest security patch. What do you need
Click to expand...
Click to collapse
now its work with mind the gapps thank you all
i flash the rom without gapps its work fine but wiht nano gapps stock in bootloob
i dont know why
now its work with mind the gapps thank you all
i flash the rom without gapps its work fine but wiht nano gapps stock in bootloob
i dont know why
Click to expand...
Click to collapse
Well I guess you should have grabbed a recovery log right after flashing Omni and gapps before booting to the ROM. (just flash ROM and gapps), go to advanced and I then "advance menu of twrp".
There is this option there to grab recovery log and dmesg". Grab that and post it here. @vache could have looked into it.