Hello I'm currently on CrDroid 9.1 unofficial GSI and the 9.2 update released but every time I update a GSI my phone bootloops and I'm forced to reinstall OneUI and flash the latest version of my GSI and lose all my stuff. Any idea on how to update CrDroid without losing my data ?
Thanks !
xXLoulouXx said:
Hello I'm currently on CrDroid 9.1 unofficial GSI and the 9.2 update released but every time I update a GSI my phone bootloops and I'm forced to reinstall OneUI and flash the latest version of my GSI and lose all my stuff. Any idea on how to update CrDroid without losing my data ?
Thanks !
Click to expand...
Click to collapse
When there is a GSI update try downloading the update then wipe the system partition then flash the update.
Related
Yesterday XIAOMI Mi5 has get a new update.
About TWRP aborts the update, because firmware MIUI 8.8.30 is required as a minimum requirement.
However, I find these not to download - does anyone have a link?
Regards & Thanks
Same here, does anyone can provide the download link ? Thank you
same here and the last update that worked has some bugs.
Apps crashing, battery drains etc.
Was hoping the new update would have fixed these issues but alas
I cannot get TWRP to flash giving the same error about MIUI 8.8.30
cabs77 said:
Yesterday XIAOMI Mi5 has get a new update.
About TWRP aborts the update, because firmware MIUI 8.8.30 is required as a minimum requirement.
However, I find these not to download - does anyone have a link?
Regards & Thanks
Click to expand...
Click to collapse
beerchow said:
Same here, does anyone can provide the download link ? Thank you
Click to expand...
Click to collapse
Blaster3K said:
same here and the last update that worked has some bugs.
Apps crashing, battery drains etc.
Was hoping the new update would have fixed these issues but alas
I cannot get TWRP to flash giving the same error about MIUI 8.8.30
Click to expand...
Click to collapse
This is to all of you, you can't apply stock OTA updates on rooted devices or devices that have TWRP installed. Stock OTA updates require an unmodified system partition(meaning no root, no Xposed, no root mods of any kind).
OTA updates also require stock recovery, not TWRP.
You can all try flashing any stock firmware for your device then wait for the update notification then try the update process.
To those of you that have TWRP installed, this is a good example of why it is so important to create a nandroid backup of your stock ROM before you modify anything on the device. If you had that nandroid backup, you could restore the backup, then flash a copy of your stock recovery, then unroot the device, then wait for the update notification, then you'd be able to apply the current update. Then after applying the update, root the device again and flash TWRP again, then create a new nandroid backup of the updated stock ROM and delete the older backup from before the update.
Sent from my LGL84VL using Tapatalk
I am running Lineage OS 15.1 when it applies the nightly update I get this error.
So what you are saying is they updated to MIUI 10 which as what I can see updates to MIUI 8.8.30 which includes new code
that TWRP and Lineage cannot install over. Also there is this Xiaomi's anti rollback that is installed as well so I am guessing
either live with the last Lineage OS update or install stock MIUI and call it day.
Blaster3K said:
I am running Lineage OS 15.1 when it applies the nightly update I get this error.
So what you are saying is they updated to MIUI 10 which as what I can see updates to MIUI 8.8.30 which includes new code
that TWRP and Lineage cannot install over. Also there is this Xiaomi's anti rollback that is installed as well so I am guessing
either live with the last Lineage OS update or install stock MIUI and call it day.
Click to expand...
Click to collapse
Oh, you mean a nightly update of LOS?
Maybe the MIUI update contained a bootloader update and the new builds of LOS were built to work with the new bootloader?
Sent from my LGL84VL using Tapatalk
Interesting I encountered the same problem. Lineage Cannont update because 8.8.30 stock ROM Miui is required.
Simply download latest available miui firmware. Via TWRP install it and then immediately install latest LineageOS.
Here is the link to the new MIUI
http://en.miui.com/thread-3709942-1-1.html
Sent from my LGL84VL using Tapatalk
Here all firmware files, select gemini for Mi5 https://sourceforge.net/projects/xiaomi-firmware-updater/files/Developer/
guys,i am currently using lineage os 15.1 official..if i have to flash another custom rom , which twrp i have to use..whether the offical twrp or lineage based twrp
dharun005 said:
guys,i am currently using lineage os 15.1 official..if i have to flash another custom rom , which twrp i have to use..whether the offical twrp or lineage based twrp
Click to expand...
Click to collapse
Lineage based is fine, I was on 15.1 official , then switched to Aex with same twrp with no problem whatsoever.
thnks fr ur reply.i installed lineage without changing it to ext4.so my doubt is if i have to change it frm f2f to ext4,can i use lineage based twrp to format data or i have to switch back to original twrp to do the process.
dharun005 said:
thnks fr ur reply.i installed lineage without changing it to ext4.so my doubt is if i have to change it frm f2f to ext4,can i use lineage based twrp to format data or i have to switch back to original twrp to do the process.
Click to expand...
Click to collapse
Lineage based causes issue with formatting data many a times. But in my case if u first change data to ext4 ,then wipe data then all is fine.
But users have also reported bootloops and decryption issues with formatting data with LOS twrp. So for safety, formatting data with official twrp is best but in my case former worked for me.
Hi
I'm currently on crdroid . can i flash los or aex with dirty flash?
mysteres said:
Hi
I'm currently on crdroid . can i flash los or aex with dirty flash?
Click to expand...
Click to collapse
Man, dont dirty flash one rom over other. The pain of clean flash is way less than dirty flash with problems.
dharun005 said:
guys,i am currently using lineage os 15.1 official..if i have to flash another custom rom , which twrp i have to use..whether the offical twrp or lineage based twrp
Click to expand...
Click to collapse
I couldn't get the Lineage OS TWRP to work as it couldn't mount the data partition even though it re-formated it to ext4.
Official TWRP worked first time.
Hope this helps.
Good luck!
They made a wiki on Beryllium (https://wiki.lineageos.org/devices/beryllium) and some other links to the official build (https://download.lineageos.org/beryllium) but they removed it.
I don't know what was the reason.
They rolling out the Lineage 16 PIE on couple devices like Oneplus 5/5T, Huawei P20 Pro, Xiaomi Mi Note 3, etc. (https://www.androidpolice.com/2019/...1-oneplus-phones-galaxy-s5-and-other-devices/)
wasn't released it failed but it is expected to succeed soon.
bower1994 said:
wasn't released it failed but it is expected to succeed soon.
Click to expand...
Click to collapse
Thank you for the response, out of curiosity, what was failed in the latest official build?
https://gitlab.com/LineageOS/builder/android/pipelines/49950700/builds
Yesterday all builds failed on that user/server
#### build completed successfully (01:34:25 (hh:mm:ss)) #### Guess we can expect a build in a few hours?
The nightly is available now
The inital nightly build seems to be broken, at least for me. Can't boot into system.
Same here, installed via adb sideload. system displays the boot animation for a while, then I end up in recovery every time.
tiantnait said:
Same here, installed via adb sideload. system displays the boot animation for a while, then I end up in recovery every time.
Click to expand...
Click to collapse
I tried again, this time flashing the 9.2.25 vendor firmware instead of 9.3.1, LOS flash also via sideload. It's working now!
no problems here.. clean flash, flashed firmware 9.2.25, los official nightly, pico gapps and magisk 18.2, wipe cache/dalvik and reboot. it runs awesome
Strel0ka said:
I tried again, this time flashing the 9.2.25 vendor firmware instead of 9.3.1, LOS flash also via sideload. It's working now!
Click to expand...
Click to collapse
No luck here. I also tried flashing 9.2.25 first (had 9.2.21 before). Still same boot loop. Must be something else.
(magisk, no google services, encrypted fs, not a clean install [update from UNOFFICAL 20190220])
going back to UNOFFICAL build works fine for now...
tiantnait said:
No luck here. I also tried flashing 9.2.25 first (had 9.2.21 before). Still same boot loop. Must be something else.
(magisk, no google services, encrypted fs, not a clean install [update from UNOFFICAL 20190220])
going back to UNOFFICAL build works fine for now...
Click to expand...
Click to collapse
So you performed a dirty flash of official LOS over unofficial LOS? That's like dirty flashing NOS over LOS. If you want to switch over to the official branch, I highly recommend starting from scratch.
My current setup is official LOS with microg + magisk and Encryption, no issues so far.
Yep.. Official build is on!
I am using S9+ Lineage 17.1 and I have TWRP theme. I lose it every time I update my system to the latest lineage nightly.
Is there a way to prevent this from happening?
Thank you in advance!
I am using my poco x3 pro with mi eu as my daily driver; however, duplicate apps still reign supreme and the default mi music app doesn't get recognized in Android Auto.
I have dabbled in custom roms before, a couple times but most of them have stopped me from completely using the phone normally, namely broken camera support with drive doesn't recognizing the camera (even with gcam, don't @ me), slow document viewer and so on. As such, I generally refrained from using them, until I saw Crdroid 8 with MIUI cam, which seems like the best of both world for me.
The guides on the thread are too vague? And Im not sure about updating (the rom required a custom recovery image, however, my recovery is too old and i don't want to risk my phone getting bricked)
Can someone help? Thanks a lot!
bump
Boot to twrp
Format data
Wipe data, dalvik, cache
Install latest firmware - https://xiaomifirmwareupdater.com/firmware/vayu/
Install ROM
Flash Gapps
Format data
AmmarHaseeb said:
Boot to twrp
Format data
Wipe data, dalvik, cache
Install latest firmware - https://xiaomifirmwareupdater.com/firmware/vayu/
Install ROM
Flash Gapps
Format data
Click to expand...
Click to collapse
Does this erase the internal storage? I don't have an SD card and a usb otg
BreadGyarados said:
Does this erase the internal storage? I don't have an SD card and a usb otg
Click to expand...
Click to collapse
I already got that figured out
BreadGyarados said:
I already got that fig
Click to expand...
Click to collapse
BreadGyarados said:
I already got that figured out
Click to expand...
Click to collapse
Flash latest twrp, or orangefox recovery. On A11 android you can put rom zip to internal storage and flash from there, on a12 you need sideload rom, because recovery still not support encrypting storage.
irmas5 said:
Flash latest twrp, or orangefox recovery. On A11 android you can put rom zip to internal storage and flash from there, on a12 you need sideload rom, because recovery still not support encrypting storage.
Click to expand...
Click to collapse
I see!
does twrp support cross android versions? Like can I dirty flash one of the update (a12)? The crdroid og thread mentioned sth about a12 custom recovery
BreadGyarados said:
does twrp support cross android versions? Like can I dirty flash one of the update (a12)? The crdroid og thread mentioned sth about a12 custom recovery
Click to expand...
Click to collapse
All custom recoveries cannot decrypt Android 12 yet.
So you cannot see internal storage in any Android 12 ROM if your phone is encrypted. This will cause difficulties in dirty flash Android 12 systems.
What do you mean cross Android versions? MIUI to CrDroid 12 ? CrDroid 11 to CrDroid 12? CrDroid 12 to CrDroid 12?
It is better to do clean flash than to only dirty flash when you are crossing different OS and different Android version to prevent bugs.
pl1992aw said:
All custom recoveries cannot decrypt Android 12 yet.
So you cannot see internal storage in any Android 12 ROM if your phone is encrypted. This will cause difficulties in dirty flash Android 12 systems.
What do you mean cross Android versions? MIUI to CrDroid 12 ? CrDroid 11 to CrDroid 12? CrDroid 12 to CrDroid 12?
It is better to do clean flash than to only dirty flash when you are crossing different OS and different Android version to prevent bugs.
Click to expand...
Click to collapse
What I meant cross android versions is that miui eu running android 11 to crdroid running android 12, as the device has no official android 12 support.
I know that I need to clean flash the roms as a first time installation, but current twrp supports android 11 (check it on mifirm).
BreadGyarados said:
What I meant cross android versions is that miui eu running android 11 to crdroid running android 12, as the device has no official android 12 support.
I know that I need to clean flash the roms as a first time installation, but current twrp supports android 11 (check it on mifirm).
Click to expand...
Click to collapse
The deciding matter is the Android system currently installed in the phone.
Your example is MIUI.eu with Android 11, in custom recoveries should be able to see internal storage.
[Phone is now Android 11]
After you install CrDroid Android 12 and boot, then custom recoveries cannot see internal storage if it's encrypted.
[Phone is now Android 12]
If you revert from CrDroid Android 12 to MIUI.eu Android 11 and boot, then custom recoveries should be able to see internal storage again.
[Phone is now Android 11]
If your phone is now Android 12, when you want to install something or flash/update a ROM in custom recoveries, it will be a bit complicated as mentioned earlier. You have to sideload with commands.
If you have microSD cards in the phone or USB OTG, then custom recoveries should be able to read them even under when phone is Android 12.
Whether ROMs can dirty flash or not, you have to read the ROM thread and replies (or Telegram if there is no XDA thread), especially replies by the developer.
Some version cannot be dirty flashed, even if it's by the same developer.