- 6 Oct 2016
- 9,988
- 322
Are you serious? A list like that could take a year to make...Maybe a detailed list of system app and fonctions releated ?
Are you serious? A list like that could take a year to make...Maybe a detailed list of system app and fonctions releated ?
Ok, my bad.Are you serious? A list like that could take a year to make...
Don't know what the problem is exactly, I'm not a TWRP dev. If the problem is related to moving from Stable to Weekly, then a clean flash is not just a solution, it's a well-known requirement. Inconvenient, but that's how it is.If you have a better solution, just let me know. I'm just trying to find a workaround to my problem.
Hello,Hi
Any tips for moving to a new weekly?
I went from stable to 21.6.9 using your instructions but after installing the new version 21.6.16 it just boot-loops again.
Is there a specific sequence to follow or is it a once off deal?
Thanks for the patch regardless.
Hi
Any tips for moving to a new weekly?
I went from stable to 21.6.9 using your instructions but after installing the new version 21.6.16 it just boot-loops again.
Is there a specific sequence to follow or is it a once off deal?
Thanks for the patch regardless.
No, you don't have to mount anything.That is what I did, do i have to mount something?
It does mention in the script output that system, i think, must be mounted but also don't worry just below it.
Maybe I'll try again tonight, thanks.
No, you don't have to mount anything.
Please try this new version and feedback => TWRP_Stable_to_Weekly_BootFix_v1.1.zip
The addon.d script "999-bootfix.sh" is not used because Xiaomi.eu doesn't support addon.d scripts...Sorry, I don't need to use your boot fix, I'm just curious about (and maybe thinking about the similar solution with addon.d for automatically re-installing Magisk for the each weekly update)
I understand why you require that phone was shipped with Pie or below.
But I wonder can you really execute the 999-bootfix.sh once you already switch to the weekly with A11
Because, looking into the /vendor/etc/fstab.qcom (on my Mi 9T), /system (as root) becomes ro=read only once the Xiaomi.eu is installed, hence I'm wondering how your script can still modify then props on the /system
Ok, that's (addon.d not supported) why you have to flash it every time againThe addon.d script "999-bootfix.sh" is not used because Xiaomi.eu doesn't support addon.d scripts...
"/system" is Read-Only when system is booting, in recovery mode you can mount it as Read-Write without issue.
Hello all!
For users who are wanting to install the latest Weekly ROM version but currently having Stable ROM version, you will generally be faced to this following issue if you don't do a clean installation => Your device is only rebooting into TWRP and it can't boot to system anymore unless if you flash the previously installed Stable ROM version.
This patch will fix this boot issue so you will be able to use the Weekly ROM version without losing your data.
IMPORTANT: Your device must have been shipped with Android 9 or below! How to know this info? Search your device on this website then check the "Platform > OS" line => https://www.gsmarena.com/
Download link: TWRP_Stable_to_Weekly_BootFix_v1.1.zip (mirror link: here)
== Use it at your own risks (backup first) ==
Steps to follow:
1) Stable ROM version MUST be installed on your device
(If you already installed the Weekly ROM version over the Stable one, please reflash your last Stable ROM version first)
2) Install the BootFix patch in TWRP
3) Flash the Weekly ROM version (+ Wipe Dalvik & Cache)
4) Install the BootFix patch in TWRP
5) Reboot your device
IMPORTANT: I recommend to NOT delete the "bootfix" file found in the "/sdcard" folder because you will surely have to install my BootFix patch after installing a Weekly ROM update (to be able to boot to system). If you remove this file by mistake, you have to redo all steps above.
Feedbacks are welcome!
Didnt work for me, i am on 12.5.5.0 and flashed the fix, then flashed weekly (wiped cache), then when i try to flash the fix again it give me an error 7 after checking android version.Hello all!
For users who are wanting to install the latest Weekly ROM version but currently having Stable ROM version, you will generally be faced to this following issue if you don't do a clean installation => Your device is only rebooting into TWRP and it can't boot to system anymore unless if you flash the previously installed Stable ROM version.
This patch will fix this boot issue so you will be able to use the Weekly ROM version without losing your data.
IMPORTANT: Your device must have been shipped with Android 9 or below! How to know this info? Search your device on this website then check the "Platform > OS" line => https://www.gsmarena.com/
Download link: TWRP_Stable_to_Weekly_BootFix_v1.1.zip (mirror link: here)
== Use it at your own risks (backup first) ==
Steps to follow:
1) Stable ROM version MUST be installed on your device
(If you already installed the Weekly ROM version over the Stable one, please reflash your last Stable ROM version first)
2) Install the BootFix patch in TWRP
3) Flash the Weekly ROM version (+ Wipe Dalvik & Cache)
4) Install the BootFix patch in TWRP
5) Reboot your device
IMPORTANT: I recommend to NOT delete the "bootfix" file found in the "/sdcard" folder because you will surely have to install my BootFix patch after installing a Weekly ROM update (to be able to boot to system). If you remove this file by mistake, you have to redo all steps above.
Feedbacks are welcome!
Is there an error message? Error 7 means nothing (generic error code) in TWRP.give me an error 7 after checking android version.
Yes, after check the android version it shows some red letters and show this generic error code... Is there a way to extract a log from twrp and give you more information?Is there an error message? Error 7 means nothing (generic error code) in TWRP.
Please try this new version => TWRP_Stable_to_Weekly_BootFix_v1.2.zipYes, after check the android version it shows some red letters and show this generic error code... Is there a way to extract a log from twrp and give you more information?
The curious thing is that in the fix flash before flashing weekly there is no error
Same problem
Ok! i will made it later on and post, thanks so much for your help!@fridlack Then I need your recovery.log, use the "Copy Log" button in "Advanced" menu of TWRP. You will find the recovery.log file in root of phone's storage.
It's certainly an incompatibility with your actual TWRP version (maybe too old?).Ok! i will made it later on and post, thanks so much for your help!
HRe is the log file, I check the recovery nowIt's certainly an incompatibility with your actual TWRP version (maybe too old?).
Are you using the latest Official TWRP? => https://androidfilehost.com/?fid=2188818919693777991
In your log file:recovery
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.www.mediafire.com
HRe is the log file, I check the recovery now
/tmp/bootfix/script.sh: line 1: syntax error: unexpected redirection
I update recovery and now I don't have problems flashing but followings the steps it boots to recovery again... Please, I appreciate so much your support but don't spend more time with me, I feel bad about this... Maybe I am doing something wrongIn your log file:
/tmp/bootfix/script.sh: line 1: syntax error: unexpected redirection
I don't understand this "unexpected redirection" thing... Your TWRP is outdated, an update will certainly avoid this bug.
EDIT: Found a workaround, I will update my bootfix to v1.2.1. ^^
I saw in your recovery.log you installed "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip". I never used that thing and I don't recommend it.I update recovery and now I don't have problems flashing but followings the steps it boots to recovery again... Please, I appreciate so much your support but don't spend more time with me, I feel bad about this... Maybe I am doing something wrong
I tried with 1.1 and 1.2
Thanks for the zip file recommendation, I tried this to solve the problem from a telegram group, don't know what this zip file do.I saw in your recovery.log you installed "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip". I never used that thing and I don't recommend it.
EDIT: You should uninstall Magisk to check if it's not a Magisk issue.
EDIT 2: New version (better compatibility with old custom recovery versions): TWRP_Stable_to_Weekly_BootFix_v1.2.2.zip
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation