For those who are not familiar with Seamless System Update. If you have ever used Linux, you will find that it can update itself while you are using it. Unlike windows that Pops Green screen and you need to wait for update to complete. In the same way, this feature introduces A/B partition so you can update your phone while using it and next time you reboot it will be running new update.
Read this for more information https://m.androidcentral.com/what-are-seamless-updates-and-how-will-they-work
I tested my Redmi note 5 pro (Indian Varient) and found that this feature is not available in the device.
I would like to know if this is ROM specific or Manufacturer firmware specific. (Can a Rom add this feature)?
Why would MIUI not come with this when their system updates are big and time consuming?
coder3101 said:
For those who are not familiar with Seamless System Update. If you have ever used Linux, you will find that it can update itself while you are using it. Unlike windows that Pops Green screen and you need to wait for update to complete. In the same way, this feature introduces A/B partition so you can update your phone while using it and next time you reboot it will be running new update.
Read this for more information https://m.androidcentral.com/what-are-seamless-updates-and-how-will-they-work
I tested my Redmi note 5 pro (Indian Varient) and found that this feature is not available in the device.
I would like to know if this is ROM specific or Manufacturer firmware specific. (Can a Rom add this feature)?
Why would MIUI not come with this when their system updates are big and time consuming?
Click to expand...
Click to collapse
As i understand whyred only have partition A. Which wont have seamless update.
This is not rom related, manufacture need to repartition the device to work with seamless updates
Related
As the title says, here's a list of some GSI's i have tested so far... but first for some story.
Bought the phone in summer, it's quite nice but has its own issues like no kernel source BUT since we can unlock the device and actually play around, oh boy it has been fun.
On the course of few hours and many downloads later I have a small list of GSI's that worked!
Every GSI I have mentioned REQUIRE device specific patch(es)!!!
For that you have to root.
----------------------WORKING GSI's-------------------------
BlissROM - It boots and functions quite fast
Cons: no included Gapps
Flashing any system editing patch results in "Phone is booting" homescreen.
https://sourceforge.net/projects/treblerom/files/BLESS/2020.09.21/
3.5 jack, VoLTE, Bluetooth, ComboFix patches are required, flash with Magisk manager
DO NOT USE FixLagSmooth
HavocOS 3.7 and 3.6 - Work and can be daily driven
3.6 requires FixLagSmooth patch
MUST root and apply all linked patches (don't use FixLagSmooth on 3.7, you can but no need)
https://forum.xda-developers.com/mi...rom-how-to-install-android-10-gsi-mi-t4126223
AOSP Android 10 based - Also does work and requires patching
https://forum.xda-developers.com/mi...rom-how-to-install-android-10-gsi-mi-t4126223
HydrogenOS Android 10 - Works
Has few bugs
No Google services
https://mirrors.lolinet.com/firmware/gsi/HydrogenOS/
----------------------COMMUNITY REPORTED GSI's-------------------------
Android 11 GSI - Reported to be functional by HumptyPotato47, thanks mate!
No Gapps as of now NikGapps exist for Android 11, search XDA for it!
Requires more testing...
https://github.com/phhusson/treble_experimentations/releases/tag/v300.f
----------------------MAYBE WORKING GSI's-------------------------
OxygenOS 10 GSI - Seems to work.. sorta
First boot after exiting fastboot causes the phone to reboot
Second boot will loop
https://mirrors.lolinet.com/firmware/gsi/OxygenOS/
----------------------NON FUNCTIONAL GSI's-------------------------
You tell me
...I did find a very nice list of GSI ROMs to try out more, here's the link:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
----------------------FLASHING GSI-------------------------
If you test one then don't hesitate with replying which one, about the experience, bugs and how you installed it.
My method of installing was this:
1. Make sure to have the new adb commandline that supports fastbootd mode
2. Drop the GSI .img file in /adb directory for ease
3. Make sure you're running MIUI with unlocked bootloader and USB debugging enabled
3.5 MAKE SURE you get a GSI ROM with Gapps as existing TWRP isn't fully functional
4. GSI you should have must be AB partition!!!
Once all set then follow the next commands
>adb reboot bootloader
>fastboot -w
>fastboot reboot fastboot
>fastboot erase system
>fastboot flash system "GSI-ROM-name-without-quotes".img
>fastboot reboot bootloader
>fastboot reboot
----------------------SETTING UP GSI-------------------------
Once all that is complete it should boot, if not then that specific GSI does not work.
Also a thing worth mentioning! Whenever I boot this phone to fastbootd Windows keeps forgetting what driver it was which requires
few extra clicks in device manager to set it up for fastbootd use. Including an image with simple to follow instructions if you have the same issue.
>fastboot boot twrp.img
Once in TWRP you should be able to access internal storage with your computer, drag Magisk.zip over and flash. Don't forget to wipe cache!
If it boots normally then root was successful, now apply the linked patch and reboot once again. Since we are playing with GSI:
Head to Settings
Find Phh Treble Settings
Misc features
Check Disable audio effect. -- DISABLE IT AFTER PATCHING!!!
IMPORTANT!!! I only tested Havoc and Bliss for a long period, IF one of my mentioned GSI's or others require more patches then I have linked headphone jack and Bluetooth audio patches too.
Combo fix should do the trick thought so your mileage may vary.
----------------------HELP US-------------------------
IF you find more working GSI's then tell us and I will make sure to add them to the main post so it won't get clogged under other comments!
Update on 05.10.2020 GMT+3
Bliss ROM GSI
As only a day or two have passed I already encountered few issues.
> You cannot remove screenshot sounds, even when fully muted
> Data drain is something interesting I've noticed, consumption compared to MIUI is higher.
> When using the gesture navigation it is a bit buggy when using quick side swipe for multitasking.
Positive notes!
> It is stupid fast
> Battery life is good
> GCam is amazing
> 99% of the customization options work perfectly
> Fast charging modes and such work perfectly
Neutral stuff...
> No FOD, thanks for closed source
> whenever you take a picture or a screenshot and have Blutetooth audio connected, it pauses and plays out loud via speaker. No music leaks out
this phone is born dead, no developer cares about it.
alsartawi said:
this phone is born dead, no developer cares about it.
Click to expand...
Click to collapse
Sad truth but won't stop others from working on it. Eventually we might get a kernel source
Kevin Soosaar said:
Sad truth but won't stop others from working on it. Eventually we might get a kernel source
Click to expand...
Click to collapse
i would pay to see a stable custom rom for this phone, i really loved it.
alsartawi said:
i would pay to see a stable custom rom for this phone, I really loved it.
Click to expand...
Click to collapse
Havoc OS and Bliss ROM are both quite stable, albeit with Bliss you don't get Gapps which is a huge bummer to most users.
Personally I just installed MicroG services and use Aurora store with anonymous "account".
When I tried to flash Gapps with TWRP I ended up soft bricking ROM so it was required to restore stock and try again. Of course there's no need if you can still use fastbootd.
Kevin Soosaar said:
Havoc OS and Bliss ROM are both quite stable, albeit with Bliss you don't get Gapps which is a huge bummer to most users.
Personally I just installed MicroG services and use Aurora store with anonymous "account".
When I tried to flash Gapps with TWRP I ended up soft bricking ROM so it was required to restore stock and try again. Of course there's no need if you can still use fastbootd.
Click to expand...
Click to collapse
does FOD works on Havoc OS?
edit: sorry i just read that it's not working.
alsartawi said:
does FOD works on Havoc OS?
Click to expand...
Click to collapse
FOD is not working as the driver sources are not public, reverse engineering is not possible too afaik. Everything else works.
Should i send this phone back to Amazon?
Seriously, last night i bought it, thinking about to install some custom rom, but if there are no developers caring of it, i might returb the phone to the seller...
IMO MIUI EU is better then GSI roms. Everything works. Got rid of most chinese crap. You can use Magisk.
Have nice features (MIUI in general). The only thing i dont like -mine turns on WIFI byitself dotn know how it happens... but it happens when i sleep. china collecting logs?
https://www.scmp.com/abacus/tech/ar...earch-and-browsing-data-china-researcher-says
afigienas said:
IMO MIUI EU is better then GSI roms. Everything works. Got rid of most chinese crap. You can use Magisk.
Have nice features (MIUI in general). The only thing i dont like -mine turns on WIFI byitself dotn know how it happens... but it happens when i sleep. china collecting logs?
https://www.scmp.com/abacus/tech/ar...earch-and-browsing-data-china-researcher-says
Click to expand...
Click to collapse
Literally the main reason I made this post is to help others who are interested to use GSI ROM's on their devices. I do agree that MIUI has some decent features and I did use Xiaomu.eu before but it was so buggy. In the end I love customizing the device however I like it so MIUI is just not for me. Either way I might try to negotiate with Amazon to get a refund as touch and Bluetooth problems still persist. Fun fact, on Bliss the edge detection is pretty good and not as aggressive or straight out bad.
Simon_19 said:
Seriously, last night i bought it, thinking about to install some custom rom, but if there are no developers caring of it, i might returb the phone to the seller...
Click to expand...
Click to collapse
Actually there are plenty of people ready to build ROMs for Toco (Mi Note 10 Lite) and Tucana (Mi Note 10) but there just isn't any kernel source available. Making things worse is the cancelled release of Toco in India and we know that they are one of the biggest Android ROM builders next to Russians. No one there is gonna import a device like this because better phones for money exist. If you don't like it then yeah I recommend returning otherwise give GSI a try for now and see what happens.
You won't lose warranty as there is no E-fuse like on Samsung phones so locking bootloader and flashing back to stock is enough.
Is anyone try oos gsi ?
HumptyPotato47 said:
Android 11 GSI of phh is working fine. It is very smooth. But i switched back to miui because i can't find any android 11 gapps.
Click to expand...
Click to collapse
can you give the link of the rom?
HumptyPotato47 said:
Android 11 GSI of phh is working fine. It is very smooth. But i switched back to miui because i can't find any android 11 gapps.
Click to expand...
Click to collapse
Hi, there are gapps for Android 11, look for NikGapps here in XDA
Kevin Soosaar said:
Actually there are plenty of people ready to build ROMs for Toco (Mi Note 10 Lite) and Tucana (Mi Note 10) but there just isn't any kernel source available. Making things worse is the cancelled release of Toco in India and we know that they are one of the biggest Android ROM builders next to Russians. No one there is gonna import a device like this because better phones for money exist. If you don't like it then yeah I recommend returning otherwise give GSI a try for now and see what happens.
You won't lose warranty as there is no E-fuse like on Samsung phones so locking bootloader and flashing back to stock is enough.
Click to expand...
Click to collapse
who said its cancelled?
Dr. DoubtReaper said:
who said its cancelled?
Click to expand...
Click to collapse
The mentioned Mi Note 10 Lite for India was supposed to be called Mi 10i or something like that. It quickly disappeared and is not happening.
Of course I might be wrong by this date but looking for now there is no 10i, only speculation videos and threads.
Mi Note 10 Lite for India would've been code named "tocoin", same hardware and everything else so just a rebadge in old Xiaomi fashion... :laugh:
anyone tried new version of blissROM? feedback?
GaryFisher88 said:
anyone tried new version of blissROM? feedback?
Click to expand...
Click to collapse
Not sure if the one I linked is up do date, give it a try yourself as my device went in for warranty repairs.
Hello, I am currently using Xiaomi.eu based on MIUI 12 and I would like to know how to flash HAVOC OS GSI. Should I flash back to Global Rom then flash the GSI as indicated? Answer is greatly appreciated.
Not sure if this really should be going to the noob friendly thread, but since it is a couple of questions covering various Android related issues, I figured that I will make it a separate thread after all.
1. Sometime updating an Android version would also end up updating the bootloader, at time rendering it impossible to downgrade again. Can this also happen in custom ROM (e.g. Lineage). I am asking this because I am thinking of custom ROM with newer Android version on my Galaxy S7, but may want to revert to a relatively old Android 7.0 after I am done testing.
2. Do file systems (the way application, application data are stored in the system and other information) etc. tend to stay the same as stock for a given Android version? For example between stock Android 7.1 and Lineage 14.1.
3. Same question as question 2., but between major Android versions (e.g. stock 7.1 and stock 8.0).
4. On rooted devices, can you usually update major version update without losing any data, and is it usually trouble free?
Feel free to skip reading this part, but for some background information, the reason I am asking all those questions is because one of the app I tried to restore via Titanium Backup and Swift Backup both failed. The application itself launches properly, but as soon as I restore the data, it would instantly crash and close. My guess is that this is probably caused by attempt to go from Android 6.0 to 11.0. Maybe it is the backup software or maybe something changed in the way files are stored, but whatever the reason, it just won't work.
So I am thinking that my best option is to try it to restore it on an Android 7.0 phone that I have (also on the way to be retired, and if it works, update to Android 8.0. Since Android 8.0 was the last officially released major version for that phone, and I was thinking that if it does work, perhaps I could alternatively go for an early Lineage ROM, then make gradual updates up to Android 11.0 and see if it helps the app remain unbroken. And then if it does work, perhaps I could then make a backup then restore it on the other new Android 11.0 phone that I have.
All in all, it is a silly amount of work to do just for one app.. but it is important to me, so I will exhaust every option that I can think of to find a solution.
Thanks!
As soon as I've updated my phone to Android 12, is there any way to roll back to Android 11? I'm talking about stock UI 4.0. Unfortunately, if you are on Android 12 - there's no easy way to re-install a copy of Android 11 stock ROM. Flashing via Odin doesn't go through. Some people say that you need to go to a Samsung Service Center. I can't believe it! I'm sure there must be a fix for that. Of course, it's possible to play around with really high possibility to permanently brick the phone. I'm talking about reformatting partitions and flashing a pit file...
If the bottled version is higher on Android 12, it probably is, then you can't downgrade. In the build number, I believe it's the 5th number from the right might want to check that it with Google. If the new firmware has a higher number there NO going back...
robotov said:
As soon as I've updated my phone to Android 12, is there any way to roll back to Android 11? I'm talking about stock UI 4.0. Unfortunately, if you are on Android 12 - there's no easy way to re-install a copy of Android 11 stock ROM. Flashing via Odin doesn't go through. Some people say that you need to go to a Samsung Service Center. I can't believe it! I'm sure there must be a fix for that. Of course, it's possible to play around with really high possibility to permanently brick the phone. I'm talking about reformatting partitions and flashing a pit file...
Click to expand...
Click to collapse
Yes, it's possible, and I've done it.
robotov said:
As soon as I've updated my phone to Android 12, is there any way to roll back to Android 11? I'm talking about stock UI 4.0. Unfortunately, if you are on Android 12 - there's no easy way to re-install a copy of Android 11 stock ROM. Flashing via Odin doesn't go through. Some people say that you need to go to a Samsung Service Center. I can't believe it! I'm sure there must be a fix for that. Of course, it's possible to play around with really high possibility to permanently brick the phone. I'm talking about reformatting partitions and flashing a pit file...
Click to expand...
Click to collapse
I confirm that I also downgraded from Android 12 / One UI 4.0 (January 1 patch) to Android 11 / One UI 3.1 (November 1 patch) without problems. There were several aspects of the new version that were bothering me a lot, now I'm happy both versions are binary 3, but it will cease to be in the following versions for sure...
Hi can you help me with guidelines to upgrade to android 12? I'm using Note 20 ultra n985f/ds. It was previously a Live demo unit but is now fully functional on android 10. My csc is OXM WWD... looking forward to your help
Also I'd like to know which is better, should I just change my csc so I can receive the push for update via OTA or just follow a guideline for flashing with Odin, thanks in advance
Hi everyone,
just now the Global Version of MIUI 13 with Android 12 have been released, there's also the version from Xiaomi.eu available.
I have been following the development a bit and i have a few questions being a rooted user.
- Obviously getting root again shouldn't be a problem with the latest releases of magisk which is flashed via fastboot (boot.img)
- TWRP is not yet able to access encrypted partition on android 12, thus the rom has to be installed via fastboot. Where else could this lead be a shortcoming? Are there alternatives?
I just don't want it to feel like a mistake to upgrade early. So i am looking for some experiences from other users.
Root will be no problem.
About encryption use adb sideload, fastboot, sd card, usb otg. Whatever you like.
Or wipe data and foash dfe zip. Restart to rom, restart recovery and data will be decrypted. Then flash rom you like from internal. But there is again problem where to put dfe.
just buy some chippest sd card for this just for flashing roms and your problem will be solved forever
do you have link?
Don't even bother flashing it or updating to it, it's infested with bugs and there are no performance or battery life improvements since it's just the initial release.
It is basically same with 12.5. It does not even have android 12 features that come stock with it. I tried it, only noteworthy change was the font change MiSans, other than that there was nothing lol.
SnowDenix said:
It is basically same with 12.5. It does not even have android 12 features that come stock with it. I tried it, only noteworthy change was the font change MiSans, other than that there was nothing lol.
Click to expand...
Click to collapse
Lol.
Any screenshots around?
Haldi4803 said:
Lol.
Any screenshots around?
Click to expand...
Click to collapse
No I already went back to crdroid lol.
So downgraded from Beta 2 of A14 to A13 and now cant get past the stage of the setup to transfer datat from an old device. It either says setting has stopped working or if i click on dont copy, it will then go to the checking info page then back again to transfer data. Have tried different A13 builds and different roms, all with the same build. Thanks.
Spell out the adb tools used.. version #
Steps used to "downgrade" your mentioning many different roms, especially confusing because you must flash (all ?) partitions to downgrade especially bootloader and such.
If you used factory web flasher or not. Or another all in one tool. Even just adb tools and double click flash-all.
I thinking you need to use factory flasher, wipe all, flash all partitions. Keep bootloader UNLOCKED.
The statement of trying to transfer data makes no sense since you likely can't get past system installation to get to transfer data.
So post steps please of your methods to get to your post question.
Maybe a better spot to post question, lots of great people in this thread!
June 7, 2023 - Beta 3 UPB3.230519.008 Global - Android 14 "Upside Down Cake" - Pixel 7 Pro [Cheetah]
Android 14 Beta program for the Pixel 7 Pro [Cheetah] Download links in the middle of the OP. Welcome to the Android 14 Developer Preview! This first release is for developers only, to help with early development, testing, and feedback...
forum.xda-developers.com
SAMVREMIX said:
So downgraded from Beta 2 of A14 to A13 and now cant get past the stage of the setup to transfer datat from an old device. It either says setting has stopped working or if i click on dont copy, it will then go to the checking info page then back again to transfer data. Have tried different A13 builds and different roms, all with the same build. Thanks.
Click to expand...
Click to collapse
Yeah...even after you downgraded successfully enough to get to the setup page/stage, maybe it was not downgraded successfully 100%.
I suggest using Google's official Android Flash Tool to reflash the full factory image to all partitions to try and get everything properly set up.
A couple of things to be sure of: best to use platform-tools r33.0.3 (in case flashing in fastbootd is necessary), make sure to check "force flash all partitions" and make sure not to check "skip secondary".
If for some reason you think flashing to both slots would be best, it hasn't been confirmed that the Android Flash Tool does this, so then you should try badabing2003's PixelFlasher to flash to both slots....
Hope this helps...
simplepinoi177 said:
Yeah...even after you downgraded successfully enough to get to the setup page/stage, maybe it was not downgraded successfully 100%.
I suggest using Google's official Android Flash Tool to reflash the full factory image to all partitions to try and get everything properly set up.
A couple of things to be sure of: best to use platform-tools r33.0.3 (in case flashing in fastbootd is necessary), make sure to check "force flash all partitions" and make sure not to check "skip secondary".
If for some reason you think flashing to both slots would be best, it hasn't been confirmed that the Android Flash Tool does this, so then you should try badabing2003's PixelFlasher to flash to both slots....
Hope this helps...
Click to expand...
Click to collapse
Have got it all sorted now. Went back to 05 May beta and that's working fine. Was using the official flashing tool and flashing all partitions and wiping butbthar was where I was getting the issue.. But now if I just wipe it works all ok.
SAMVREMIX said:
So downgraded from Beta 2 of A14 to A13 and now cant get past the stage of the setup to transfer datat from an old device. It either says setting has stopped working or if i click on dont copy, it will then go to the checking info page then back again to transfer data. Have tried different A13 builds and different roms, all with the same build. Thanks.
Click to expand...
Click to collapse
Same issue with me as well but the problem is I can't use android flash tool because oem unlocking and usb devugging was not enabled tried sideloading the OTA zip of android 13 may patch but still the same error stucked on initial screen setup please provide any leads Thanks
shivdubey said:
Same issue with me as well but the problem is I can't use android flash tool because oem unlocking and usb devugging was not enabled tried sideloading the OTA zip of android 13 may patch but still the same error stucked on initial screen setup please provide any leads Thanks
Click to expand...
Click to collapse
i have the same problem, any help?
Had the same issue, I sideloaded latest Android 14 beta 2 OTA image for my pixel 5 and that fixed the problem.
OTA images for Google Pixel | Android Developers
Instructions for downloading and appying preview OTA images for Pixel devices.
developer.android.com
A14 Beta 2.1 was just released and includes the following fix aimed at addressing this issue:
Fixed an issue that prevented users from completing device setup after opting a device running an Android 14 beta build out of the beta program. However, this fix is not backward compatible, so users that want to opt out of the beta program should take the following steps beforeopting out:
Update the device to Android 14 Beta 2.1, either through the over-the-air (OTA) update prompt, or by downloading an OTA image and then applying the update manually.
Reset the pin, pattern, or password that's used on the device by navigating to Settings > Security & privacy > Screen lock. You can use the same pin, pattern, or password that was used previously, but you need to go through the setup flow.
Opt out of the beta program by following the instructions listed for the "How can I opt out and return to a public Android release" question in the FAQ section of the Android Beta Program page.