Related
"Hi all,
OxygenOS 4.1.5 was withdrawn, we are pushing out the incremental roll-out of OxygenOS 4.1.6 (7.1.1) OTA for OnePlus 3 and 3T instead.
Here are some highlights
New additions:
• Added system push notifications for important information from OnePlus
Updates:
• Updated network settings for select carriers
• Updated OnePlus Community app to v1.8
• Updated Android Security Patch level to 1st May 2017
• Modified WiFi no internet indication icon
Bug fixes:
• Fixed storage issue present on 3rd party filemanagers
• Fixed VoLTE issue on certain Jio SIM cards
• Fixed connection issue on Android Auto
Optimizations:
• Battery
• Proximity sensor
• Camera low light focus
• Expanded screenshot
Other changes:
• Enhanced system stability
For those who were on previous versions for OnePlus 3 and 3T, we appreciate your active feedback and attempts to reach out to us. With your help, we have been able to better optimize and improve several key areas. Thank you for your patience and as always, we look forward to hearing your continued feedback in the bug reporting forum here: https://forums.oneplus.net/feedback/.
As always, this OTA will be incremental. The OTA will reach a small percentage of users today, and we'll begin a broader rollout in a few days.
Your feedback is appreciated. We may not always be able to respond to every comment in the forums, but please be assured that we take your comments and feedback seriously. Hope you enjoy!
Please make sure to fill out our user survey here: https://goo.gl/forms/Pvr6KisTvbFoqZkl1
Never Settle.
****Special thanks to @ Stephan Mävers for helping out with rom validation."
https://forums.oneplus.net/threads/oxygenos-4-1-6-7-1-1-ota-for-oneplus-3-and-3t.547283/
Full ROM: https://drive.google.com/open?id=0B8wU-_ssGUuoSGJqUVYzYWlEUlk
MD5: 3db32c320ebce696e9b058a31e77e9a8
So quick, just now got someone OTA adn informed at OP forum and uploaded in xda. Great effort @piats
[email protected] said:
So quick, just now got someone OTA adn informed at OP forum and uploaded in xda. Great effort @piats
Click to expand...
Click to collapse
Hehe, time to give something back for this community :good::highfive:
Edit: remember to backup everything before flashing. I dirty flashed this ROM over stock OOS 4.1.5 via bluespark recovery v35 and it didn't boot back to system. So I booted back to recovery and somehow twrp asked password to decrypt data partition. I was decrypted before. So I installed stock recovery. Wiped everything and flashed this ROM via stock recovery. Everyhthing works now.
Can I flash this zip using TWRP?
DouglasDuZZ said:
Can I flash this zip using TWRP?
Click to expand...
Click to collapse
Well you can try but remeber to backup everything before flashing. See my previous post.
I would recommend stock recovery for now.
I would really like to know the reasons behind these withdrawns, but thats just me. Thanks for the mirror.
batt002 said:
I would really like to know the reasons behind these withdrawns, but thats just me. Thanks for the mirror.
Click to expand...
Click to collapse
Because there was an issue they missed through QC. OTAs are always incremental/staged just in case something like this happens. This way only small number of devices are affected
bhake said:
Because there was an issue they missed through QC. OTAs are always incremental/staged just in case something like this happens. This way only small number of devices are affected
Click to expand...
Click to collapse
Yes I'm interested in that issue that was missed, but we'll never know
I instaled new Twrp blu spark 3.1.1.37 by eng stk.
Full wipe, clean flash the rom, full zip. Recovery ok. No need to reflash recovery..
All apps work for me. Root, everything.
piats said:
Hehe, time to give something back for this community :good::highfive:
Edit: remember to backup everything before flashing. I dirty flashed this ROM over stock OOS 4.1.5 via bluespark recovery v35 and it didn't boot back to system. So I booted back to recovery and somehow twrp asked password to decrypt data partition. I was decrypted before. So I installed stock recovery. Wiped everything and flashed this ROM via stock recovery. Everyhthing works now.
Click to expand...
Click to collapse
I dirty flashed full zip from encrypted 4.1.5 with TWRP 3.0.4-1 and everything went fine.
I am on OOS 4.1.5 . rooted with magisk and twrp recovery. I thought magisk would help hide root and update using OTAs. I did hide the oneplus update process in magisk hide and updates prompted a 45 mb download.(with root it would say go download the full zip). I downloaded the OTA . but as expected flashing it via twrp failed. is there any way to just do OTA update with root and twrp ? I did see some threads where people went to stock recovery and installed it. is that a simple procedure ?
I just updated to oxygen os 4.1.6 and I am unable to root my device, i was able to root on previous versions using the same supersu file but now it does not work, if anyone has a solution please help me out.
Olal said:
I just updated to oxygen os 4.1.6 and I am unable to root my device, i was able to root on previous versions using the same supersu file but now it does not work, if anyone has a solution please help me out.
Click to expand...
Click to collapse
Hi, try latest supersu 2.82 or magisk
Sent from my OnePlus3 using XDA Labs
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 Pie, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Known issues: (as of May 19, 2020)
- FM Radio app doesn't work; It actually works, just once every two attempts: If it crashes the first time, select close app, clear apps from background and try again; I'll find a definite fix soon;
- Wi-Fi signal strength doesn't show on status bar, only in the wireless screen;
- Fingerprint reader doesn't work;
- SELinux is currently set to permissive;
Instructions:
- This is a FULL ROM build, meaning your BOOT, DTBO, SYSTEM and VENDOR partitions will be overwritten. Backup first!
- You need firmware version 11.x.y (preferably 11.3.169 - recovery encryption only tested with that version), any will do. 10.5 will not work
- Download TWRP from the files section, fastboot flash it (if you don't have custom recovery yet)
- Download patched vbmeta.img
- Download the latest build
- (Optional) Download Gapps (arm64 9.0, any flavor) and Magisk
- Boot to recovery (whichever you have), flash the new recovery
- Reboot to recovery, now your data is decrypted, flash vbmeta, latest build, magisk and gapps
- Format DATA completely to start from scratch since encryption is different
- Reboot
Downloads:
Builds: https://sourceforge.net/projects/lineageos-lenovo-z5s/files/
Source code:
LineageOS: https://github.com/LineageOS
Kernel and Device Tree: https://github.com/jacoghi
Reporting Bugs:
DO NOT Report bugs if you're not following the instructions!
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Changelog:
May 19, 2020:
- Initital release, everything working except for FM and fingerprint reader;
- Kernel is completely overhauled and updated to LA.UM.7.8.r1-08500-SDM710.0;
- Audio drivers are stock 11.3.169 (we don't have the sources);
- Wifi is open-source, with MAC randomization currently being tested;
- Call recording already works;
- BT Audio works for calls and everything else, HD codecs being optimized;
- Wifi Display works perfectly on my cheap chinese Android TV Box. Please test with a Chromecast / Google Cast / SmartTVs, since I don't have any of those;
- Camera2API is active, RAW pictures are also enabled;
- Build will automatically encrypt your device, I had to fool Lenovo's BS keymaster to make it work, so it has to be enabled;
- As of now, I don't care if your apps work or not, that's not my problem, just let me know about hardware issues;
jacoghi said:
Please test with a Chromecast / Google Cast / SmartTVs, since I don't have any of those;
Click to expand...
Click to collapse
I can confirm that this works.
It's great to have a ROM that works and doesn't have audio problems or auto brightness issues compared to GSIs. I've been using this for two days without any problems aside from the bugs already mentioned. I am holding off on using Magisk like I normally do so as not to introduce complications.
Overall, a great first effort. Thank you very much!
carlshark said:
I can confirm that this works.
It's great to have a ROM that works and doesn't have audio problems or auto brightness issues compared to GSIs. I've been using this for two days without any problems aside from the bugs already mentioned. I am holding off on using Magisk like I normally do so as not to introduce complications.
Overall, a great first effort. Thank you very much!
Click to expand...
Click to collapse
Thanks for confirming that to me, great to know. Would you happen to have any of those fancy hi Def Bluetooth headphones so we can test aptx and aptxhd? And you can use magisk without any issues, I'm using it here right now, no problems.
jacoghi said:
Would you happen to have any of those fancy hi Def Bluetooth headphones so we can test aptx and aptxhd?
Click to expand...
Click to collapse
No, sorry. If that changes, I will let you know
I can imagine most of the users that are here are currently using a GSI. The stock 11.3.169 from here can actually be installed via TWRP. Flashing it would revert to stock recovery so users need to reinstall the TWRP recovery image during the same session. That's how I ensured that I was running an 11.x firmware after using all those GSIs from 4PDA. Hopefully this helps others to revert to stock so they can use your LOS build.
Some more good news, we now have a TWRP that decrypts data even from this updated Lineage 16 build. It actually should work for any ROM flashed atop firmware 11.3.169. That's the one I'm using and probably the majority of people who wanna stick to "the latest and greatest" speech, so here we go, now we can enable OTAs without any issues and flash anything. This recovery can decrypt any data regardless of password type, so you can use PATTERN, PIN, or whatever, it will work, I tested them all.
https://sourceforge.net/projects/lineageos-lenovo-z5s/files/twrp-3310-jd2019-recovery.img/download
And what is apparently massive news for us, our phone will get an Android 10 official update, meaning we'll be able to boot lineage 17.1 with the updated audio drivers (in theory). Anybody in China or who knows how to trick their system and able to get ahold of these files?
https://club.lenovo.com.cn/thread-5849244-1-1.html
jacoghi said:
Some more good news, we now have a TWRP that decrypts data even from this updated Lineage 16 build. It actually should work for any ROM flashed atop firmware 11.3.169. That's the one I'm using and probably the majority of people who wanna stick to "the latest and greatest" speech, so here we go, now we can enable OTAs without any issues and flash anything. This recovery can decrypt any data regardless of password type, so you can use PATTERN, PIN, or whatever, it will work, I tested them all.
https://sourceforge.net/projects/lineageos-lenovo-z5s/files/twrp-3310-jd2019-recovery.img/download
Click to expand...
Click to collapse
Hi, I used your recovery to try and create a full backup of your ROM before I go back to stock. I encounter an error when it tries to backup the system partition - the backup fails. When I tried to install the Full OTA ROM from Lenovo, it also fails. I flashed the other TWRP and both the backup and install worked.
I'm going back to stock to get the 11.5 update available only if the phone has a locked bootloader.
carlshark said:
Hi, I used your recovery to try and create a full backup of your ROM before I go back to stock. I encounter an error when it tries to backup the system partition - the backup fails. When I tried to install the Full OTA ROM from Lenovo, it also fails. I flashed the other TWRP and both the backup and install worked.
I'm going back to stock to get the 11.5 update available only if the phone has a locked bootloader.
Click to expand...
Click to collapse
Hey man, thanks for the report. I just rebooted to recovery and backed up the system partition without a hitch, so no clue what happened with you. Regarding the Lenovo Ota it probably doesn't work since they use different manifests from the ones I'm using with lineage. Nevertheless I'll make it universal now that I know about it. Let me know if you can get 11.5 and we can make a dump of all partitions. Thanks man
jacoghi said:
Hey man, thanks for the report. I just rebooted to recovery and backed up the system partition without a hitch, so no clue what happened with you. Regarding the Lenovo Ota it probably doesn't work since they use different manifests from the ones I'm using with lineage. Nevertheless I'll make it universal now that I know about it. Let me know if you can get 11.5 and we can make a dump of all partitions. Thanks man
Click to expand...
Click to collapse
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.
carlshark said:
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.
Click to expand...
Click to collapse
hey man could you please help out, was trying to revert to the stock rom but getting a blank screen after i'm done and it shows lenovo
carlshark said:
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.
Click to expand...
Click to collapse
That's why it failed, system partition is 5.1 GB, your sdcard is probably formatted in FAT32 which DOESN'T ALLOW files over 4GB, that's a filesystem limitation.
I'll wait for somebody getting us 11.5 firmware files and release a new twrp for Android 10, (partitions won't change and AFAIK, wsx's twrp doesn't decrypt and is full of extra non open source stuff) and Lineage 17.1, until then makes little sense to me update this knowing it won't last long anyways.
jacoghi said:
That's why it failed, system partition is 5.1 GB, your sdcard is probably formatted in FAT32 which DOESN'T ALLOW files over 4GB, that's a filesystem limitation.
Click to expand...
Click to collapse
Oh, right, I totally forgot all about that. Should have tried enabling compression or saving to internal storage.
I'll wait for somebody getting us 11.5 firmware files and release a new twrp for Android 10, (partitions won't change and AFAIK, wsx's twrp doesn't decrypt and is full of extra non open source stuff) and Lineage 17.1, until then makes little sense to me update this knowing it won't last long anyways.
Click to expand...
Click to collapse
I've found a 4PDA post regarding updating to 11.5 and reposted the good stuff here. Hope it helps. Thanks for your good work!
---------- Post added at 06:38 AM ---------- Previous post was at 06:35 AM ----------
seisa said:
hey man could you please help out, was trying to revert to the stock rom but getting a blank screen after i'm done and it shows lenovo
Click to expand...
Click to collapse
I know this is the wrong thread to answer this, but we can't really help you out without some more details. Were you trying to install through recovery? Through QFIL?
From the looks of it, sounds like you have a bootloop. Try doing QFIL again and unlocking bootloader, or the other way around - sometimes it works for me that way.
I have Z5s 6GB/128GB model, sold as Global Version & Global ROM.
It does have EU LTE bands, so it probably is somewhat "global".
The downside: I am at 10.5 version with no updates available. Seller also told that there are no updates.
Two questions:
1. Is it absolutely necessary to have 11.3+ to install this LineageOS ROM? What is blocking installation if I have 10.5? Can I brick it?
-- EDIT: I will answer myself: Yes it is needed. LineageOS did not flash over 10.5 and gave an error. That was validation error before flashing, so no harm done.
2. Is it safe to install Chinese ROM on this device? Is it possible to loose something in the process? Like LTE bands or something else important?
-- EDIT: Seems to be ok.
I really want to install LineageOS or some other google free AOSP ROM. But I do not want to loose important features or brick it in the process.
Thanks.
EDIT: I installed Arrow OS GSI at the moment over 10.5 and it seems to work. But still looking forward to get pure LineageOS installed.
I have one problem that is hardware related:
Microphone level is quite low compared to my previous phone and people are complaining about low volume when I call.
Is there any way to add more gain? I tried to search but did not find easy and straightforward answer. Most solutions refer to methods/files that do not exist on this ROM.
What I found was complaint that there is still no way to easily manage audio stuff in android...
Mic Test (lauresprojects.com.mictest) app confirms that recording levels are considerably lower in both direct sound and communication mode when comparing to my other phone.
Otherwise seems to working quite nicely. Thanks for your good work.
I can't use face unlock with this ROM.
Is there still some active development at this project?
Is there some active development at this project?
{
"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"
}
About Us:
Dirty Unicorns is an AOSP based project built to enhance the stock Android experience.
Our focus has been and is always to contribute back to the community. That is ultimately why we do what we do.
We DO NOT accept, nor ask, for donations. We do not believe in that. Everything that is necessary to keep this project going comes out of our own pocket. This includes, but is not limited to; Devices, Gerrit, our websites and services, etc.. The only thing that we ask in return is that you have patience, search the thread for answers prior to posting, read diligently, and try to enjoy the process with us!
Kernel Source:
https://github.com/DirtyUnicorns/android_kernel_google_bluecross
Flashing Instructions:
If you have a device that uses TWRP
Verify that you're using the latest version of TWRP
Perform a FULL WIPE: (A full wipe is when you wipe system/data/cache/dalvik)
Flash the latest version of this ROM
Reboot and ENJOY!
If you have a device that does not use TWRP
Download boot.img and ROM zip from DU server
Reboot into bootloader and flash the boot.img
Code:
fastboot flash --slot all boot boot.img
Reboot to recovery
Go to recovery select factory reset
Select Apply update from ADB to flash the zip
Code:
adb sideload nameofbuild.zip
Reboot and ENJOY!
If you're just updating DU on a device without TWRP
Download ROM zip from DU server
Reboot into recovery and select Apply update from ADB to flash the zip
Reboot system now and ENJOY!
**All bugs and feature requests must be reported to JIRA**
**If you use Xposed, please don't bother reporting any bugs**
**If you use another kernel, please don't bother reporting any bugs**
**If you fail to follow these instructions, please don't bother reporting any bugs**
Download Links:
Build(s) - Bonito
Other Links:
ROM Source - https://github.com/DirtyUnicorns
Gerrit - http://gerrit.dirtyunicorns.com
Crowdin (translations) - https://crowdin.net/project/dirtyunicorns
JIRA (Bug Reporting / Feature Requests) - http://jira.dirtyunicorns.com/
Telegram - https://t.me/dirtyunicorns / https://t.me/DirtyUnicornsSupport
XDA:DevDB Information
Dirty Unicorns, ROM for the Google Pixel 3a XL
Contributors
NYCHitman1, jbats
Source Code: https://github.com/DirtyUnicorns
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 14.7
Stable Release Date: 2020-09-13
Created 2020-08-08
Last Updated 2020-09-13
Thank you so much!
I've used nothing but DU since March and I'd like to thank you for your continued work on our device. Hopefully now more people will find and appreciate your efforts!
Sweet a new rom to try out
@jbats good to see you round these parts. Just installed DU for the 1st time on bonito; runs good, looks good, and I like the new boot logo and recovery. Any plans to build an in rom updater like lineage or aosip? I've become a fan of seamless updates. Anyways, nice work as usual and thanks for the rom.
41rw4lk said:
@jbats good to see you round these parts. Just installed DU for the 1st time on bonito; runs good, looks good, and I like the new boot logo and recovery. Any plans to build an in rom updater like lineage or aosip? I've become a fan of seamless updates. Anyways, nice work as usual and thanks for the rom.
Click to expand...
Click to collapse
Currently, no. However, we are planning to do this in the future.
Just flashed & loving it so far. Great to see the team still working. I'm trying to remember the first phone I flashed dirty on. Maybe htc m8. It was so long I don't recall
I've installed Bliss and Dirty Unicorns,
Dirty Unicorns is better IMO because of the minimal apps and quickness of multi-tasking.
Only complaint I would have is the lack of customization when it comes to status bar and colors.
Love the ROM and still using it, ty DU team. Please make variations of your boot animation
godpowerrr said:
I've installed Bliss and Dirty Unicorns,
Dirty Unicorns is better IMO because of the minimal apps and quickness of multi-tasking.
Only complaint I would have is the lack of customization when it comes to status bar and colors.
Love the ROM and still using it, ty DU team. Please make variations of your boot animation
Click to expand...
Click to collapse
We're not making anymore variations of the boot animation. We have a light version and a dark version. That's good enough for us.
As for the lack of customization, we include what we find useful. We're never going to be one of these cookie cutter kitchen sink ROM's you see littered across XDA. If you would like to make a particular feature request, check the OP for instructions on how to do so.
FYI
Tried flashing boot .img and rom.zip from perminent TWRP (stock Pie), and does not work. I'll update to Q and follow the directions now.
Ok? I have no adb device detected from DU recovery. I guess I'll truy TWRP. Nevermind, temporary TWRP doesn't work with June release of Q.
Back to initial Pie factory image, and now will not boot into DU recovery. Temporary TWRP will not flash du_bonito-v14.6-20200808-1220-OFFICIAL and gives an error.
Flashed bootloader-bonito-b4s4-0.2-6355063.img, radio-bonito-g670-00042-200421-b-6414611.img, and 20200808-OFFICIAL-boot.img from fastboot and DU recovery has adb and sideload is working, but get an error at 47%
Code:
C:\Users\Russell\Downloads\Android\ADB and Fastboot>adb sideload du_bonito-v14.6-20200808-1220-OFFICIAL.zip
serving: 'du_bonito-v14.6-20200808-1220-OFFICIAL.zip' (~47%) adb: failed to read command: No error
In recovery
Code:
Step 1/3
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
E:Error in /sideload/package.zip (status 1)
Maybe a bad download, but I'll probably try v14.5 if I'm going to go through the trouble downloading again.
Honestly, I already pulled the trigger on an LG V20, and just playing with this a bit more before it goes on Swappa. No SD slot, no decent recovery partition, and USB 2.0? No thanks.
ssurell said:
Tried flashing boot .img and rom.zip from perminent TWRP (stock Pie), and does not work. I'll update to Q and follow the directions now.
Ok? I have no adb device detected from DU recovery. I guess I'll truy TWRP. Nevermind, temporary TWRP doesn't work with June release of Q.
Back to initial Pie factory image, and now will not boot into DU recovery. Temporary TWRP will not flash du_bonito-v14.6-20200808-1220-OFFICIAL and gives an error.
Flashed bootloader-bonito-b4s4-0.2-6355063.img, radio-bonito-g670-00042-200421-b-6414611.img, and 20200808-OFFICIAL-boot.img from fastboot and DU recovery has adb and sideload is working, but get an error at 47%
In recovery
Maybe a bad download, but I'll probably try v14.5 if I'm going to go through the trouble downloading again.
Honestly, I already pulled the trigger on an LG V20, and just playing with this a bit more before it goes on Swappa. No SD slot, no decent recovery partition, and USB 2.0? No thanks.
Click to expand...
Click to collapse
If you're coming from Pie, you need to flash stock to both slots to get your firmware up to date.
TWRP does not work on Q for Pixel 3 and 4.
Please do some research before messing with the device further.
NYCHitman1 said:
If you're coming from Pie, you need to flash stock to both slots to get your firmware up to date.
TWRP does not work on Q for Pixel 3 and 4.
Please do some research before messing with the device further.
Click to expand...
Click to collapse
I like to try every possible combination of flashing, maybe resize or dd some partitions at sleep deprived 4am, whatever. But I've been using the factory flash-all images, so I assume both slots, else what good are they. Some of the problem may have been with the myriad of adb versions I have littering my system. A photographic memory would be more effective than research redundancy (I forgot thinking temp. TWRP still worked).
Come to think of it, I think I flashed the June OTA going to Q. So that's likely why I didn't have ADB with DU Recovery
ssurell said:
I like to try every possible combination of flashing, maybe resize or dd some partitions at sleep deprived 4am, whatever. But I've been using the factory flash-all images, so I assume both slots, else what good are they. Some of the problem may have been with the myriad of adb versions I have littering my system. A photographic memory would be more effective than research redundancy (I forgot thinking temp. TWRP still worked).
Come to think of it, I think I flashed the June OTA going to Q. So that's likely why I didn't have ADB with DU Recovery
Click to expand...
Click to collapse
Unfortunately, it doesn't. The flash-all script only flashes to the active slot on the device, so you would have to manually change slots and run said flash-all script again to be completely up to date. As for the platform-tools versions, I believe 30.0.4 is the latest revision available at this time. Might be a good idea to download that and delete everything else you have.
Outside of this, our flashing instructions are very clearly labeled and should get you through the process of flashing DU as long as you follow the instructions that are applicable to you.
ROM is running great. Do we have to do a full wipe or can we just clear cache between uodates
sjpritch25 said:
ROM is running great. Do we have to do a full wipe or can we just clear cache between uodates
Click to expand...
Click to collapse
You don't have to wipe at all between updates. It's written in the OP. Please read the instructions.
Great ROM, only issue I have is that whenever I try to change the volume while using my Pixel Buds, the system UI crashes and restarts every time. I've also found that this isn't device specific and happened on other phones I've had with Bliss. Aside from that, great work!
champ784 said:
Great ROM, only issue I have is that whenever I try to change the volume while using my Pixel Buds, the system UI crashes and restarts every time. I've also found that this isn't device specific and happened on other phones I've had with Bliss. Aside from that, great work!
Click to expand...
Click to collapse
Could be a larger platform issue. You could provide logs to Google, but seeing as R is literally right around the corner -- they'll likely ignore it until the revision is out to the masses.
Download from DU site fails
I can't download any file greater than 1GB in size from https://download.dirtyunicorns.com/
It always stops at exactly 1 GB.
Unfortunately the latest DU release for bonito is 1.07 GB in size.
Can you confirm that? Maybe it's my Internet connection. I've tried different browsers and even wget.
Are there any mirrors?
NYCHitman1 said:
Could be a larger platform issue. You could provide logs to Google, but seeing as R is literally right around the corner -- they'll likely ignore it until the revision is out to the masses.
Click to expand...
Click to collapse
Yeah that's what I figured. The second Android R releases, I don't see anyone caring ??
socksi said:
I can't download any file greater than 1GB in size from https://download.dirtyunicorns.com/
It always stops at exactly 1 GB.
Unfortunately the latest DU release for bonito is 1.07 GB in size.
Can you confirm that? Maybe it's my Internet connection. I've tried different browsers and even wget.
Are there any mirrors?
Click to expand...
Click to collapse
Hi @socksi. I have downloaded the file in 12 secs from our server without issue. Unfortunately, we do not use mirrors.
I will reach out to our webmaster and have him look into it. Stay tuned.
NYCHitman1 said:
Hi @socksi. I have downloaded the file in 12 secs from our server without issue. Unfortunately, we do not use mirrors.
I will reach out to our webmaster and have him look into it. Stay tuned.
Click to expand...
Click to collapse
It fails even when using a VPN tunnel. Most probably it's not my Internet connection.
Maybe some kind of GEO blocking? I'm from Germany.
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* 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.
*/
Another weebified custom ROM aiming to be a home for weebs - Based on Project Materium, an optimized LineageOS-based Android aftermarket firmware with extra features, developed by people all over the world.
Quoting the LineageOS description:
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Click to expand...
Click to collapse
We offer vanilla, GApps and AuroraOSS variants. If you install a vanilla variant, the only supported GApps package is MindTheGapps (GApps/AuroraOSS builds are not available for a few devices due to space issues).
Download & instructions:
Install MIUI 12.5 if you have updated to anything Android 12.
Fully install custom recovery of your choice.
Flash the ROM. You can also sideload it with ADB if you want to.
!!! If you'll flash Magisk, you'll need to enable "Reflash (recovery) after installing a ROM" after choosing the ZIP as well !!!
After flashing, reboot to recovery.
Format data.
Flash Magisk if you want to.
Reboot to system and enjoy!
Download (Taken down due to discontinuation)
IMPORTANT: If you are coming from another ROM, you need to format data (TWRP > Wipe > Format Data > *type "yes"*).
IMPORTANT: If you want to keep Magisk after each OTA, you need to make it flash to inactive slot **right before rebooting** (Magisk > Install (In "Magisk" card) > Install to inactive slot)
About:
Features:
Latest security patches merged from LineageOS
SafetyNet passing unconditionally without Magisk/with kdrag0n's SafetyNet fix
Many optimizations coming from Stellar OS/Project Materium/droid-ng
New wallpapers & bootanimation
QS customization (tint, rows customizer, data usage)
Status bar customization (4G/LTE toggle, new NFC & VoLTE icons)
Kill app from notification
Notification pulse
KitKat-style notification ticker
Screenshot sound toggle
Per-app volume
WiFi & Bluetooth timeout
Smart Charging & Cutoff
Sensor, Wakelock and Alarm blocker
Battery info on lockscreen
Improved microG support (signature spoofing, location support)
...and more! (We accept suggestions!)
What's working:
Almost everything
Bugs:
Microphone doesn't work when speaker is enabled during calls.
You tell me.
Sources are available at https://github.com/ProjectKasumi and https://github.com/Kasumi-Devices
Full list of device sources used;
Device tree
Linux kernel tree used
Vendor tree for proprietary blobs
ROM Founded By: Yuki (AITEx64)
ROM Developed By: Beru Hinode
ROM Designed By: Ayuko, Qirkl and UsiF.
ROM OS Version: 1.3 "PoPiPa" R2
ROM Kernel: Customized Linux 4.14.186 from MiCode
ROM Firmware Required: MIUI 12.5.16.0.RKLMIXM (Global)
Based On: Project Materium 1.0 (LineageOS 18.1)
Version Information
Status: Discontinued
Last Stable Version: 1.4 "PoPiPa"
SELinux Status: Permissive
Initial Release Date: July 20, 2022
poggers! atleast some buildbot didn't post it this time
J6idot said:
poggers! atleast some buildbot didn't post it this time
Click to expand...
Click to collapse
It wasn't even their build, they just took my build and posted it away! XD
Let's goo. Very awesome work here
Amazing work!! Im a little disapointed with the note 10s
Hope to get the most out of it with a costum rom!
Miui on the 10s is a complete disaster... What the hell happened...
solidamage said:
Amazing work!! Im a little disapointed with the note 10s
Hope to get the most out of it with a costum rom!
Miui on the 10s is a complete disaster... What the hell happened...
Click to expand...
Click to collapse
I could never get used to MIUI myself so I feel you. For custom ROMs, there are quite a lot built (buildbotted) with practically the same bugs as well; you can check them out in respective Telegram groups/channels!
Hey there,
First of all, thx for bringing this
what about fast charging in these?
Would it work as expected?
Or as in every other GSI custom build i tested it doesn't work, and was kinda disappointing :/
Will the fix module be merged in the rom, making possible the avoid of magisk installing? Actually don't Care bout su and want m'y banking app to work
Hope to get your opinion soon
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
It happens to me too ... Any advice?
Is this available on Android 12?
nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
Are you coming from 12.5.16 GLOBAL?
Do you format data before restarting?
Oxydeme said:
Are you coming from 12.5.16 GLOBAL?
Do you format data before restarting?
Click to expand...
Click to collapse
yup did all the steps in the thread
nintendobuster420 said:
yup did all the steps in the thread
Click to expand...
Click to collapse
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked
Oxydeme said:
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked
Click to expand...
Click to collapse
first I installed MIUI 12.5.16 global and completely erased the phone it had MIUI 13 before
then I installed orangefox by woomy
then I switched to slot B and installed the rom (gapps variant) also enabled reflash orangefox after installing rom
after installing I formatted data and installed magisk
then i rebooted and it bootlooped
i have a rosemary 10s with nfc
nintendobuster420 said:
first I installed MIUI 12.5.16 global and completely erased the phone it had MIUI 13 before
then I installed orangefox by woomy
then I switched to slot B and installed the rom (gapps variant) also enabled reflash orangefox after installing rom
after installing I formatted data and installed magisk
then i rebooted and it bootlooped
i have a rosemary 10s with nfc
Click to expand...
Click to collapse
Did you installed Magisk into the right slot?
@windowz414 is there any kind of vbmeta file to flash in order to be sure it would boot? An alternative boot IMG maybe? Or even a check disabler?
@nintendobuster420 finally gonna try flash tomorrow,
Did smtg else this evening, worked on a project, that isn't related at all to Android flashing x)
I also got a RN10S with NFC, maybe something related to variants?
Edit1: gonna try flashing Kasumi 1.3 PoPiPa Auroraoos 20220721; will update the post soon
Edit2: Kasumi auroraoos bootloop actually, reflashed auroraoos boot.img still bootlooping;
Gonna try with Kasumi classic, latest build to see
Edit3: Kasumi official 20220721 boolooping as well
Edit4: Will do a last attempt with Kasumi 20220716
Last attempt worked, I successfully booted up Kasumi, but with several differences
1- Backed up Pics and other important things for me;
2- Unlocked BL - Mi Unlock BL Tool latest version;
3- Switched Rom from 12.5.18EU to 12.5.16G with Mi Flash version 2018.5.28.0 (select fastboot rom, refresh, clean all, flash);
4- Booted once to get system settled
5- Installed TWRP from Womymy, booted on it
6- Switched Slot to B, Reflashed current recovery and rebooted from inside TWRP
NO I didn't, I switched to Slot B, reflashed recovery, got plenty errors, didn't rebooted in the end.
7- MTP mounted Storage and passed the zip rom
8- Flashed Kasumi, flashed again TWRP with the toggler while flashing rom, then directly formated format data,
9- Booted rom successfully!
still no fast charge, will keep it tough
@windowz414
Well done porting LOS dude!
Completely debloated
But still 13Go system
Little problem on CPU info
Battery seems good, phone is responsive, all the things that can be tweaked my god , bushido! Notification makes me smile
One word, net!
@HistoriaXV @nintendobuster420 hope you could success flash in the next days
Oxydeme said:
Hey there,
First of all, thx for bringing this
what about fast charging in these?
Would it work as expected?
Or as in every other GSI custom build i tested it doesn't work, and was kinda disappointing :/
Will the fix module be merged in the rom, making possible the avoid of magisk installing? Actually don't Care bout su and want m'y banking app to work
Hope to get your opinion soon
Click to expand...
Click to collapse
System reports "Charging slowly" but my battery fully charges from ~10% in just 1.5~2 hours.
nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
I have recently pushed a boot fix about this, you can flash it and format data to get it fixed.
Oxydeme said:
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked
Click to expand...
Click to collapse
I use the OFOX from Woomy and it works with it too, so it's not recovery fault.
You mentioned firmware requirement there, good shot! Glad to see someone that's not from the development team finally noticing it!
Oxydeme said:
Did you installed Magisk into the right slot?
@windowz414 is there any kind of vbmeta file to flash in order to be sure it would boot? An alternative boot IMG maybe? Or even a check disabler?
Click to expand...
Click to collapse
The vbmeta required is shipped along with the ZIP itself, so whether if you disable it or not, you can always keep verity enabled AS LONG AS YOU DON'T MODIFY ANYTHING INCLUDING INSTALLATION OF TWRP. The boot problem was due to some missing permissions required with Lawnchair 12.0, which was platform-specific issue. I have mitigated it as the lead developer of Kasumi and now just waiting for LineageOS to merge August '22 ASB on their Lineage 18.1 branches to ship newer builds. Until then, I have placed a little flashable that you can slap in on the recovery. It's global (means will work on all devices with latest Kasumi build installed). In fact, all it does is just putting the new permission XML file.
Oxydeme said:
@nintendobuster420 finally gonna try flash tomorrow,
Did smtg else this evening, worked on a project, that isn't related at all to Android flashing x)
I also got a RN10S with NFC, maybe something related to variants?
Click to expand...
Click to collapse
Not at all. Even though I have Secret, everything should be around the same across all variants, given that Woomy also tested it only for NFC during initial bringup before.
Oxydeme said:
Edit1: gonna try flashing Kasumi 1.3 PoPiPa Auroraoos 20220721; will update the post soon
Edit2: Kasumi auroraoos bootloop actually, reflashed auroraoos boot.img still bootlooping;
Gonna try with Kasumi classic, latest build to see
Edit3: Kasumi official 20220721 boolooping as well
Edit4: Will do a last attempt with Kasumi 20220716
Last attempt worked, I successfully booted up Kasumi, but with several differences
1- Backed up Pics and other important things for me;
2- Unlocked BL - Mi Unlock BL Tool latest version;
3- Switched Rom from 12.5.18EU to 12.5.16G with Mi Flash version 2018.5.28.0 (select fastboot rom, refresh, clean all, flash);
4- Booted once to get system settled
5- Installed TWRP from Womymy, booted on it
6- Switched Slot to B, Reflashed current recovery and rebooted from inside TWRP
NO I didn't, I switched to Slot B, reflashed recovery, got plenty errors, didn't rebooted in the end.
7- MTP mounted Storage and passed the zip rom
8- Flashed Kasumi, flashed again TWRP with the toggler while flashing rom, then directly formated format data,
9- Booted rom successfully!
Click to expand...
Click to collapse
The dedication and the hassle... My God, it's just pure inspiration to me. XD
Oxydeme said:
still no fast charge, will keep it tough
Click to expand...
Click to collapse
As I said previously, it's what system reports presumably due to some SEL denials. I tried to get as many as possible sorted out, still no luck. But just as a fact, it actually is fast charging.
Oxydeme said:
@windowz414
Well done porting LOS dude!
Completely debloated
But still 13Go system
Little problem on CPU info
Battery seems good, phone is responsive, all the things that can be tweaked my god , bushido! Notification makes me smile
One word, net!
Click to expand...
Click to collapse
Well, thank you I guess. ^^;
Before I begin with replies to these, just referring to "dude", I'm a girl so I would prefer you calling me with "dudess" or "dudette" instead. Again, all up to you. No forces here.
The debloat is rather Lineage talent, I really just based on Materium and added things on top.
That 13 GB system partition is something that's coming from partition values from source, so whatever you do unless you flash GSI, it will always be 13 GB. See GitHub:Kasumi-Devices/[email protected]/BoardConfig.mk (Partitions section, BOARD_SYSTEMIMAGE_PARTITION_SIZE flag) for more info.
Eh, I still can't find a way to get CPU info properly, I guess it's related to kernel? Unsure though.
And some more tweaks will come as well, just stay tight! I'm working hard on another update! ;3
Sambit0789 said:
Is this available on Android 12?
Click to expand...
Click to collapse
Unfortunately no. Kasumi 1.x.x are all Android 11. Android 12 Kasumi will be possible only once our internal tests will be done and I finally finish working on Kasumi v2. Hundreds hyped, gradually widening audience, looking into the release of it. xD
My phone has arrived and in few days, I ll attempt to switch to the EU ROM
(I ve bought a CN unit, which arrived nice and sealed in its box)
So, I ll attempt to follow this guide to the letter: https://xiaomi.eu/community/threads/howto-install-fastboot-image.64508/
Heading over to sourceforge, I can see that the latest stable releases for my phone are one from AUG and one from MAY i.e.
xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip
2022-08-05
xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.12.0.SKACNXM_v13-12-fastboot.zip
2022-05-13
But according to that guide, it says "download latest fastboot" image. And thats the older one released in MAY (V13.0.12.0...)
So I presume I cannot use the latest V13.0.13.0 (released in AUG) for this method!?
Is there a fastboot (V13.0.13.0) in the making, so perhaps I could wait a little longer for that?
Or do I just use the one released 6 months ago?
jstoner said:
My phone has arrived and in few days, I ll attempt to switch to the EU ROM
(I ve bought a CN unit, which arrived nice and sealed in its box)
So, I ll attempt to follow this guide to the letter: https://xiaomi.eu/community/threads/howto-install-fastboot-image.64508/
Heading over to sourceforge, I can see that the latest stable releases for my phone are one from AUG and one from MAY i.e.
xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip
2022-08-05
xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.12.0.SKACNXM_v13-12-fastboot.zip
2022-05-13
But according to that guide, it says "download latest fastboot" image. And thats the older one released in MAY (V13.0.12.0...)
So I presume I cannot use the latest V13.0.13.0 (released in AUG) for this method!?
Is there a fastboot (V13.0.13.0) in the making, so perhaps I could wait a little longer for that?
Or do I just use the one released 6 months ago?
Click to expand...
Click to collapse
Without functional TWRP in A12, Xiaomi Eu rom provided roms in Fastboot .zip.
Now that there is a TWRP, the roms are in Zip.
Either you use a Fastboot .zip and update via Ota or you install the Twrp and flash the rom.
For updates you must go through the Ota and not flash directly with the TWRP.
NOSS8 said:
Without functional TWRP in A12, Xiaomi Eu rom provided roms in Fastboot .zip.
Now that there is a TWRP, the roms are in Zip.
Either you use a Fastboot .zip and update via Ota or you install the Twrp and flash the rom.
For updates you must go through the Ota and not flash directly with the TWRP.
Click to expand...
Click to collapse
Regarding TWRP, do I get the latest version (skkk) or the one from TeamWin? (because both are intended for 11 Ultra I think - codenamed "star")
My guess is skkk, which also says "A12"
Then I can use "xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip", which seems to be latest
I plan to use this guide - I hope it is accurate (it says "unofficial"!)
jstoner said:
Regarding TWRP, do I get the latest version (skkk) or the one from TeamWin? (because both are intended for 11 Ultra I think - codenamed "star")
My guess is skkk, which also says "A12"
Then I can use "xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip", which seems to be latest
I plan to use this guide - I hope it is accurate (it says "unofficial"!)
Click to expand...
Click to collapse
Official here:
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/star/
NOSS8 said:
Official here:
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/star/
Click to expand...
Click to collapse
Just done the same thing yesterday. Use 3.70_12-v6.5_A12-star-skk.img. I had problems with fastboot V13.0.12.0.SKACNXM_v13-12-fastboot had failed status read failed (too many links) errors. But think that's just my adb setup in Windows 11. So just used fastboot to boot twrp. Then in twrp flashed twrp to ramdisk reboot to recovery and flashed xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip formatted data reboot to systsem. Working V13.0.13.0. I ended up just copying V13.0.13.0.zip and twrp to a flash drive mounted OTG in twrp and installed. Only because of issues with laptop.
NOSS8 said:
Official here:
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/star/
Click to expand...
Click to collapse
no, by "unofficial" I meant the Guide ;-)
(if it would work if I followed that guide to the letter - as I m not too tech savvyy)
jstoner said:
no, by "unofficial" I meant the Guide ;-)
(if it would work if I followed that guide to the letter - as I m not too tech savvyy)
Click to expand...
Click to collapse
The installation remains the same
https://forum.xda-developers.com/t/twrp-mi-11-pro-ultra-mars-star.4280313/
If you install a xiaomi Eu rom (twrp included) check the version of Twrp and update it if necessary.
NOSS8 said:
The installation remains the same
https://forum.xda-developers.com/t/twrp-mi-11-pro-ultra-mars-star.4280313/
If you install a xiaomi Eu rom (twrp included) check the version of Twrp and update it if necessary.
Click to expand...
Click to collapse
Now, I ve backed up everything and was about to flash the phone to latest stable MIUI
But just realised v14 was released in the meantime, in December
But for the 11 Ultra, there is only weekly ROM available (no stable)
Looks like I ll have to extend my wait
As for v13, I can still see that the latest is xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip
I wonder - will there be another v13 release for this phone?
Should I go with this latest v13 or wait for the first stable v14 (star) release?
Sometimes, having been presented with choices, makes it so hard to decide! But for sure, I need a stable build for this phone..
jstoner said:
Now, I ve backed up everything and was about to flash the phone to latest stable MIUI
But just realised v14 was released in the meantime, in December
But for the 11 Ultra, there is only weekly ROM available (no stable)
Looks like I ll have to extend my wait
As for v13, I can still see that the latest is xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip
I wonder - will there be another v13 release for this phone?
Should I go with this latest v13 or wait for the first stable v14 (star) release?
Sometimes, having been presented with choices, makes it so hard to decide! But for sure, I need a stable build for this phone..
Click to expand...
Click to collapse
Whether Weekly or stable, both are based on the Chinese rom.
For the stable you will have to wait while Xiaomi releases the rom.
I use the Weekly when available and they are really "stable".
Note that if you install a Weekly and move to the stable you will have to format the data.
Also going from A12 to A13, formatting the data is not mandatory but I recommend it.
NOSS8 said:
Whether Weekly or stable, both are based on the Chinese rom.
For the stable you will have to wait while Xiaomi releases the rom.
I use the Weekly when available and they are really "stable".
Note that if you install a Weekly and move to the stable you will have to format the data.
Also going from A12 to A13, formatting the data is not mandatory but I recommend it.
Click to expand...
Click to collapse
Ah, OK - so there's no 'stable' MIUI v14 for the 11 Ultra yet? I get it..
As for the format consideration, I m a huge fan of clean installs too. I guess I ll go with v13 for the time being, as I don't have much of a time luxury to wait for the official stable v14..
Seems like it v14 (stable) has just been released for the 11 Ultra!
xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13.zip
But is this ROM meant to be installed via fastboot or twrp?
In my mind, it is still not clear what the difference is between fastboot and twrp
I can only presume that twrp is essentially a GUI (vs just typing commands in fastboot!?) But I m not really sure anymore
I ve been an Galaxy S series user over the last years. Back then, I used to flash a new ROM via "Odin". Was that using the twrp method or fastboot? I m sorry, but I m totally confused now
Since twrp is an extra software that needs to be installed on the phone - isn't that come with any drawbacks? What is the more 'clean' approach to installing an MIUI on the 11 Ultra?
jstoner said:
Seems like it v14 (stable) has just been released for the 11 Ultra!
xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13.zip
But is this ROM meant to be installed via fastboot or twrp?
In my mind, it is still not clear what the difference is between fastboot and twrp
I can only presume that twrp is essentially a GUI (vs just typing commands in fastboot!?) But I m not really sure anymore
I ve been an Galaxy S series user over the last years. Back then, I used to flash a new ROM via "Odin". Was that using the twrp method or fastboot? I m sorry, but I m totally confused now
Since twrp is an extra software that needs to be installed on the phone - isn't that come with any drawbacks? What is the more 'clean' approach to installing an MIUI on the 11 Ultra?
Click to expand...
Click to collapse
Yep, TWRP avoids typing command lines.https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/star/
Two version of roms:
Rom.Fastboot.zip to install with a pc with the Bat file included in the rom folder.
Provided this way if no working TWRP.
Rom.Zip to install via OTA.
If this is a first installation you will have to install the TWRP first then TWRP / wipe format data type Yes (this will erase all your data) and reboot to the TWRp and flash the rom, then the updates will be done via OTA/TWRP.
NOSS8 said:
Provided this way if no working TWRP.
Click to expand...
Click to collapse
So basically you imply that recovery (TWRP) is the preferred path
If I understood correctly, the biggest (?) advantage of chosing a recovery ROM (instead of a fastboot one) is the benefit of having OTA afterwards, right? (and maybe simplicity of having the GUI - that is TWRP)
Now, to put this the other way - what's the disadvantage of chosing the recovery ROM over a fastboot one? Is there any? (other than the need to have to install an 'extra layer' - that is TWRP)
So that ROM that was just released (xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13.zip) is a recovery ROM. right? If so, the latest twrp (v3.7.0 from https://eu.dl.twrp.me/star/) will work for this brand new MIUI 14?
jstoner said:
So basically you imply that recovery (TWRP) is the preferred path
If I understood correctly, the biggest (?) advantage of chosing a recovery ROM (instead of a fastboot one) is the benefit of having OTA afterwards, right? (and maybe simplicity of having the GUI - that is TWRP)
Now, to put this the other way - what's the disadvantage of chosing the recovery ROM over a fastboot one? Is there any? (other than the need to have to install an 'extra layer' - that is TWRP)
So that ROM that was just released (xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13.zip) is a recovery ROM. right? If so, the latest twrp (v3.7.0 from https://eu.dl.twrp.me/star/) will work for this brand new MIUI 14?
Click to expand...
Click to collapse
For Xiaomi EU roms regardless of whether they are in ZIP or Fastboot.zip only the way of installing them is different.
For Stock roms, those in Recovery are used for updating or troubleshooting, they only contain the essentials, unlike those in Fastboot containing all the Imgs of the phone.
For the TWRP, you must take into account the version of Android A12 or A13, not Miui13 or 14.
The link https://eu.dl.twrp.me/star/ is obsolete, the one I posted is the official one developed by SKKK.
xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13.zip
use
twrp-3.7.0_12-v6.9_A13-star-skkk.img
The first boot of the rom takes 5/8 minutes.
NOSS8 said:
For Xiaomi EU roms regardless of whether they are in ZIP or Fastboot.zip only the way of installing them is different.
For Stock roms, those in Recovery are used for updating or troubleshooting, they only contain the essentials, unlike those in Fastboot containing all the Imgs of the phone.
For the TWRP, you must take into account the version of Android A12 or A13, not Miui13 or 14.
The link https://eu.dl.twrp.me/star/ is obsolete, the one I posted is the official one developed by SKKK.
xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13.zip
use
twrp-3.7.0_12-v6.9_A13-star-skkk.img
The first boot of the rom takes 5/8 minutes.
Click to expand...
Click to collapse
I ll prob do it in the weekend
From what I read, I also have to unlock the bootloader and from a security PoV, I m not really happy about that, but no way around it. Just can't live with the stock CN ROM
Not sure if unlocking the bootloader takes time or if it is instateneous (via the MI website)
As for my concerns over the method (twrp vs fastboot), it would seem that the fastboot is probably more 'clean'
No disrespect towards the developers who made the twrp possible - thus making it so much easier for people to fiddle with ROMS on their mobile and at no cost, but regardless of that, it is still an extra piece of software that resides on the phone. Just the way I understand it. Again, not looking down at twrp
What do you mean by "fastboot containing all the imgs..."?
Isn't it one single image per phone model?
Or did you mean to say 'features' or 'apps'?
Personally, I d be more interested in less/apps/fancy features (except for security of course)
jstoner said:
I ll prob do it in the weekend
From what I read, I also have to unlock the bootloader and from a security PoV, I m not really happy about that, but no way around it. Just can't live with the stock CN ROM
Not sure if unlocking the bootloader takes time or if it is instateneous (via the MI website)
As for my concerns over the method (twrp vs fastboot), it would seem that the fastboot is probably more 'clean'
No disrespect towards the developers who made the twrp possible - thus making it so much easier for people to fiddle with ROMS on their mobile and at no cost, but regardless of that, it is still an extra piece of software that resides on the phone. Just the way I understand it. Again, not looking down at twrp
What do you mean by "fastboot containing all the imgs..."?
Isn't it one single image per phone model?
Or did you mean to say 'features' or 'apps'?
Personally, I d be more interested in less/apps/fancy features (except for security of course)
Click to expand...
Click to collapse
As said above, this only concerns stock roms(recovery/fastboot), not xiaomi Eu roms, whether in Zip or Fastboot, it's the same, only the installation method differs.
Unlocking the bootloader takes at least 168 hours before finalization (time to study a bit).
The latest Stable or Weekly versions are in Zip, so with TWRP.
Unlock
https://new.c.mi.com/global/post/101245
https://en.miui.com/unlock/index.html
Unfortunately, the more I read, the more I m getting kind of disappointed with things 'Xiaomi'
In order to get the unlock process started (1 week..really??), I need to download the MI drivers. OK
So I m trying to search "official" MI drivers and they are nowhere to be found!
All I get is this https://xiaomidriver.com/ which claims to host the official drivers (!)
How can this be for the image of a reputable brand?
How can Xiaomi not hosting themselves all these useful tools like all other major vendors do (in their own domain!)?
How me, as an end user, is supposed to verify authenticity of a driver found on a xyz domain claiming to be the official one?
What's more, at the bottom of this page it says "xiaomidriver.com is not endorsed or affiliated to Xiaomi..."
I mean seriously???
I purchased this phone for its hardware capabilities but is there nothing more than that?
I mean, I get Xiaomi not wanting to encourage people mess with the ROMS. After all, some will end up bricking their phone and then they ll chase up Xiaomi for this
But Xiaomi not hosting something as so very basic as a USB driver??? This can't be right
Even that official page kindly provided by NOSS8 earlier, states "ensure your PC has necessary Mi USB drivers and platform tools" Well...where am I supposed to get these from? The first random site I google up?
........
After bashing my head around this, I eventually found an official link (from miui.com), for obtaining the flash tool from which I can do a workaround to extract the drivers....c'mon!!
jstoner said:
Unfortunately, the more I read, the more I m getting kind of disappointed with things 'Xiaomi'
In order to get the unlock process started (1 week..really??), I need to download the MI drivers. OK
Click to expand...
Click to collapse
It is very simple.
The installation of the drivers is done with Mi Unlock (gear at the top right) then check:
{
"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"
}
Also download platform tools which would be useful for installing TWRP or performing certain Fastboot operations.
@NOSS8 I tried installing xiaomi.eu Rom MIUI14 on the Mi 11 pro. It booted and everything but whatsapp and camera was not working. Whatsapp not syncing, camera asks for SD card?
So I decided to downgrade to MIUI 13 from Aug 2022 the version in this post above. This is what I did:
1. Fastboot TWRP latest skkk for A12.
2. Flash from TWRP last stable MIUI 13 Rom
3. Phone restarts fine but goes in to loop after connecting to wifi. Please note I have done format data before and after flash
4. I rebooted the ROM to recovery it asks for pin, then says wrong password, failed mount.
Please advise. What should I do? I am happy to toll back to MIUI13 as I am not sure what is going on with MIUI 14. How do solve this problem? Many thanks
It's better to use fastboot when doing downgrade/rollback android or Miui version .