Related
Hello
I have a Wileyfox Swift 1 (crackling) which has been updated to 7.1.1
It has been wiped because of plenty of bugs (random reboots, random crashes, it became randomly very slow...)
I want to remove lots of bloatware (Particularly this crapy phone app !), and mostly, I don't want to have to re-enable my custom keyboards after each reboot (which now occurs when I receive a SMS while listening to music) !
Can I :
- Downgrade to CM-13 ?
- Root this 7.1.1 ?
- Install Lineage OS 14 ?
I already have tried this without success :'(
Similar problem
I would love to know how to downgrade back to Cyanogen OS. I loved the phone prior to the Nougat update and now I hate it.
Could anyone provide instructions how to do this, it would be muchos appreciated.
mioux said:
Hello
I have a Wileyfox Swift 1 (crackling) which has been updated to 7.1.1
It has been wiped because of plenty of bugs (random reboots, random crashes, it became randomly very slow...)
I want to remove lots of bloatware (Particularly this crapy phone app !), and mostly, I don't want to have to re-enable my custom keyboards after each reboot (which now occurs when I receive a SMS while listening to music) !
Can I :
- Downgrade to CM-13 ?
- Root this 7.1.1 ?
- Install Lineage OS 14 ?
I already have tried this without success :'(
Click to expand...
Click to collapse
I have tried by myself, even if I have read multiple times that this downgade regularly leads to a brick :
WARNING : All data will be lost during process
Prequisite :
- fastboot and adb installed on your system
- find fastboot files of cm-13.1
6b2b09c40f1a2b85ee5335823640536d cm-13.1.2-ZNH2KAS3LG-crackling-signed-fastboot-84f0d5200b.zip
Click to expand...
Click to collapse
- if you want LineagoOS
-> lineageos file (/!\ don't take last version ! when I have installed this one, my touchscreen was not working /!\ take the image with this date 2017-06-26 10:44:39)
-> twrp file
-> unlocked bootloader
-> lineageos image on external sd card (recommended) or in internal memory AFTER you have restored CM13
Unzip the file, go in the directory and launch these commands
#!/bin/bash
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot reboot
Click to expand...
Click to collapse
To install lineageos
- you MUST have started CM13 at last one time... I had a bootloop without booting first CM13
- reboot in fastboot mode
- flash twrp :
fastboot flash recovery twrp-<version>.img
fastboot boot twrp-<version>.img
Click to expand...
Click to collapse
- in twrp go to wipe -> advanced wipe and wipe all but internal storage and external storage
- install lineageos from twrp
You can update to last version, it does not breack your touchpad
I'll correct the scripts and add shasums and filename of CM-13.1 tonight
Did you succeed in downgrading? Any news on this?
Where do you experience trouble by following this:
mioux said:
[...]
I already have tried this without success :'(
Click to expand...
Click to collapse
Lurkos said:
Did you succeed in downgrading? Any news on this?
Click to expand...
Click to collapse
Yes, just look at the previous post
kabu83 said:
Where do you experience trouble by following this:
Click to expand...
Click to collapse
I have flashed the aboot, abootbak and boot, then tried to install lineageos from twrp, even after formating all partitions. Each time, it has rebooted to 7.1.1 with 7.1.1 recovery (twrp was not persistent).
I really had to fully reinstall CM13, and booting it, before updating to lineageos.
Hi all,
I've managed to successfully move from stock 7.1.2 (TOS212D) to LineageOS 14 (2017-09-11) without an intermediate downgrade to an old CM13 build
To do so, I rebooted the phone from stock 7.1.2 into the bootloader (adb reboot-bootloader)
I then booted into TWRP 3.1.1.0 (fastboot boot twrp-3.1.1-0-crackling.img)
I said no to the prompt for mounting /system read-write
I went to Wipe -> Advanced Wipe -> Ticked System and chose Repair or Change Filesystem.
I changed /system to EXT4
At this point, I then wiped all partitions except for my MicroSD card
Next, I flashed the latest LineageOS nightly (lineage-14.1-20170911-nightly-crackling-signed.zip), followed by OpenGApps (I chose 7.1, ARM64, pico)
At this point, if you reboot, it will loop back to the bootloader
As my final steps, I flashed Foxy Kernel 2.6 and Magisk 14, and rebooted
I believe the "magic" here is Magisk's patching of the boot loader to allow it to work, I believe that patches out some of the checks that are causing the phone to go back into the bootloader after installing LineageOS via TWRP over stock 7.1.X
anticoralian said:
Hi all,
I've managed to successfully move from stock 7.1.2 (TOS212D) to LineageOS 14 (2017-09-11) without an intermediate downgrade to an old CM13 build
To do so, I rebooted the phone from stock 7.1.2 into the bootloader (adb reboot-bootloader)
I then booted into TWRP 3.1.1.0 (fastboot boot twrp-3.1.1-0-crackling.img)
I said no to the prompt for mounting /system read-write
I went to Wipe -> Advanced Wipe -> Ticked System and chose Repair or Change Filesystem.
I changed /system to EXT4
At this point, I then wiped all partitions except for my MicroSD card
Next, I flashed the latest LineageOS nightly (lineage-14.1-20170911-nightly-crackling-signed.zip), followed by OpenGApps (I chose 7.1, ARM64, pico)
At this point, if you reboot, it will loop back to the bootloader
As my final steps, I flashed Foxy Kernel 2.6 and Magisk 14, and rebooted
I believe the "magic" here is Magisk's patching of the boot loader to allow it to work, I believe that patches out some of the checks that are causing the phone to go back into the bootloader after installing LineageOS via TWRP over stock 7.1.X
Click to expand...
Click to collapse
anyone confirm please if above still works on TOS373K? or was updating the phone first a mistake?
Smiff3 said:
anyone confirm please if above still works on TOS373K? or was updating the phone first a mistake?
Click to expand...
Click to collapse
Yes it does still work.
It's even easier nowadays if you just want Oreo.
Flash or boot TWRP, reformat system as ext4 (so you don't have the 0MB problem) and then you can flash the Oreo crDroid zip file and it will boot instantly:
https://forum.xda-developers.com/wileyfox-swift/development/rom-crdroid-android-4-0-beta-1-t3688253
schmatzler said:
Yes it does still work.
It's even easier nowadays if you just want Oreo.
Flash or boot TWRP, reformat system as ext4 (so you don't have the 0MB problem) and then you can flash the Oreo crDroid zip file and it will boot instantly:
https://forum.xda-developers.com/wileyfox-swift/development/rom-crdroid-android-4-0-beta-1-t3688253
Click to expand...
Click to collapse
thanks, i missed this reply before sorry.
not sure if i want oreo.. how is it on this phone? do you use Gravitybox.. i'll ask over there! thanks.
where can i get ADB USB DRIVERS for Windows 8.1 64bit for my WileyFox Swift 1 ?
I had this device for two days now, one of the first things that I tried was to install a custom ROM and I was surprised of how hard it was to do, so after a lot of trial and error I managed to install those two ROMs so I wanted to share how I did it so nobody has to suffer like I
Okay so I have tried two methods, one worked for Pixel Experience and the other for Lineage OS, there are probably better ways to do this so be sure to reply to this thread if you find another ways to accomplish this!
IMPORTANT!:
1. I did the two of this methods with the stock ROM with a minimal setup (skipping wifi, no google login, no fingerprint, etc).
2.You need to have the bootloader unlocked.
3. Im not responsable if you brick your phone or lose your data, do the following steps if you know what you're doing and always back-up your data!!!
Files used:
TWRP link (Download both the img and the zip)
Pixel Experience link
LineageOS link
Gapps link
Magisk 20.1 link
Encryption patch (patch_no_fde10) link
Method 1 (Tested succesfully with Pixel Experience):
Thanks to ElSuperFullHD for creating an awesome guide in how to install Pixel Experience!
How to install Pixel Experience in Xiaomi mi a3 (Spanish guide)
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay) and reboot into recovery again (Long press Vol + when the device starts until you boot into recovery).
6. Go to advanced wipe Dalvic cache, Data and System.
7. Install Pixel Experience ROM and TWRP zip again and restart to system.
8. You're done, enjoy!
Method 2 (Tested succesfully with LineageOS):
Thanks to suschmania for your extremely helpful comment, I wouldnt have figured how to install LineageOS without him!
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. Once in TWRP copy TWRP recovery zip into the phone and wipe Dalvic cache, Data, Vendor and System.
6. Install the ROM and TWRP recovery zip (This will make the recovery to stay).
7. Reboot into recovery (twrp shows the warning no os installed, continue anyway).
8. The filesystem will be decrypted (All folders corrupted) dont worries, just go to advanced wipe and wipe internal data, once that's done copy Gapps, magisk and the encryption patch into the phone).
9. Flash Gapps, magisk (Optional) and encryption patch.
10. Reboot to system (It may take up to 10 minutes to start so give it time, if more than 10 minutes passes see step 11).
11. In case of bootlop boot back into recovery and format data (its the one where you need to write yes to format), after its done reboot to system again.
12. You're done, enjoy!
I hope this guide was helpful to you, good luck!
thanks so much for this! Been flashing since andriod 1.6 but couldnt wrap my dumb head around these dual partitions.
And is the same for miui.eu ?
raphae34 said:
And is the same for miui.eu ?
Click to expand...
Click to collapse
No. Follow the instructions in the OP there. They work.
Kaissner said:
I had this device for two days now, one of the first things that I tried was to install a custom ROM and I was surprised of how hard it was to do, so after a lot of trial and error I managed to install those two ROMs so I wanted to share how I did it so nobody has to suffer like I
Okay so I have tried two methods, one worked for Pixel Experience and the other for Lineage OS, there are probably better ways to do this so be sure to reply to this thread if you find another ways to accomplish this!
IMPORTANT!:
1. I did the two of this methods with the stock ROM with a minimal setup (skipping wifi, no google login, no fingerprint, etc).
2.You need to have the bootloader unlocked.
3. Im not responsable if you brick your phone or lose your data, do the following steps if you know what you're doing and always back-up your data!!!
Files used:
TWRP link (Download both the img and the zip)
Pixel Experience link
LineageOS link
Gapps link
Magisk 20.1 link
Encryption patch (patch_no_fde10) link
Method 1 (Tested succesfully with Pixel Experience):
Thanks to ElSuperFullHD for creating an awesome guide in how to install Pixel Experience!
How to install Pixel Experience in Xiaomi mi a3 (Spanish guide)
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay) and reboot into recovery again (Long press Vol + when the device starts until you boot into recovery).
6. Go to advanced wipe Dalvic cache, Data and System.
7. Install Pixel Experience ROM and TWRP zip again and restart to system.
8. You're done, enjoy!
Method 2 (Tested succesfully with LineageOS):
Thanks to suschmania for your extremely helpful comment, I wouldnt have figured how to install LineageOS without him!
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. Once in TWRP copy TWRP recovery zip into the phone and wipe Dalvic cache, Data, Vendor and System.
6. Install the ROM and TWRP recovery zip (This will make the recovery to stay).
7. Reboot into recovery (twrp shows the warning no os installed, continue anyway).
8. The filesystem will be decrypted (All folders corrupted) dont worries, just go to advanced wipe and wipe internal data, once that's done copy Gapps, magisk and the encryption patch into the phone).
9. Flash Gapps, magisk (Optional) and encryption patch.
10. Reboot to system (It may take up to 10 minutes to start so give it time, if more than 10 minutes passes see step 11).
11. In case of bootlop boot back into recovery and format data (its the one where you need to write yes to format), after its done reboot to system again.
12. You're done, enjoy!
I hope this guide was helpful to you, good luck!
Click to expand...
Click to collapse
The 1st method for Pixel Experience does not work for me, after following all the steps carefully, if i boot into system it boots me to fastboot everytime, or if I dont reboot to system (in TWRP after flashing everything) it only says no OS installed are you sure you want to continue, so any help?
Snjeky said:
The 1st method for Pixel Experience does not work for me, after following all the steps carefully, if i boot into system it boots me to fastboot everytime, or if I dont reboot to system (in TWRP after flashing everything) it only says no OS installed are you sure you want to continue, so any help?
Click to expand...
Click to collapse
the "no os installed" is normal, dont worries.
The installation method for pixel experience worked when I installed the old version, it was updated multiple times so probably the process changed, I will update the thread later
This dual slot fuking my mind up.
TWRP asking for password to decrypt data. while first boot in recovery.
also *unable to decrypt FBE device* error while formating data.
"couldnt able to flash Any ROM "unable to partition path/cache" error.
ps. flashed in slot a.
When I install twrp on fastboot it stuck there, I have Android 10 stock, is anything that I can do ? I try like 3 times and always the same
ManuMan99 said:
When I install twrp on fastboot it stuck there, I have Android 10 stock, is anything that I can do ? I try like 3 times and always the same
Click to expand...
Click to collapse
downgrade to android 9. apparently android 10 got some issues.
pradie said:
downgrade to android 9. apparently android 10 got some issues.
Click to expand...
Click to collapse
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
I apologize for not being precise. i had the same issue. downloaded and flashed android 9 Stock global ROM with mi flash tool. now it's booted correctly.
---------- Post added at 12:37 PM ---------- Previous post was at 12:37 PM ----------
garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
I apologize for not being precise. i had the same issue. downloaded and flashed android 9 Stock global ROM with mi flash tool. now it booted correctly.
Sapper Morton said:
Indeed, it's not as straight forward, but it's possible without losing Widevine L1 security level; read my experience here, I explained the steps I took ; so far, I came back to v11.0.8.0 QFQMIXM from v10.3.17.0 PFQEUXM after the downgrade, with no issues whatsoever (no format/wipe data); my DRM Keys and sensors remains intact.
Click to expand...
Click to collapse
Thank you I wouldn't have guessed that would work it seems too easy to be a fix but that's good news.
Thanks for that info
garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
Then what to do? I downgraded from Android 10 Stock to Android 9 Stock 3.13.0.PFQMIXM because I soft-bricked my phone. I Flashed the stock ROM using Mi Flash tool. It flashed OK but my MI A3 sensors are not working. Someone said Flash persist.img via TWRP but when I try to flash it asked me in which partition to flash.
Partitions available are:
bluetooth
modem
System Image
Dtbo
Vendor Image
splash
Boot
Install Recovery Ramdisk
I am confused where to flash. If this method isnt suitable as you said then guide me what to do. I have Global Fastboot ROM for Android 9 Version 3.16.0.PFQMIXM for Mi A3 available. Should I flash this using Mi Flash tool? Does it solve sensor issues or not? Please help.
vjrx88 said:
Then what to do? I downgraded from Android 10 Stock to Android 9 Stock 3.13.0.PFQMIXM because I soft-bricked my phone. I Flashed the stock ROM using Mi Flash tool. It flashed OK but my MI A3 sensors are not working. Someone said Flash persist.img via TWRP but when I try to flash it asked me in which partition to flash.
Partitions available are:
bluetooth
modem
System Image
Dtbo
Vendor Image
splash
Boot
Install Recovery Ramdisk
I am confused where to flash. If this method isnt suitable as you said then guide me what to do. I have Global Fastboot ROM for Android 9 Version 3.16.0.PFQMIXM for Mi A3 available. Should I flash this using Mi Flash tool? Does it solve sensor issues or not? Please help.
Click to expand...
Click to collapse
If you are on stock android 9 now then flash an android 10 custom rom and then downgrade to android 9 like you did. Downgrading from stock 10 to stock 9 causes big issues like you are having.
If you did flash persist.IMG you would have caused stuff in your device to break forever without any way of fixing it don't do it!!
garylawwd said:
If you are on stock android 9 now then flash an android 10 custom rom and then downgrade to android 9 like you did. Downgrading from stock 10 to stock 9 causes big issues like you are having.
If you did flash persist.IMG you would have caused stuff in your device to break forever without any way of fixing it don't do it!!
Click to expand...
Click to collapse
I updated it to Stock Android 10 OTA update using TWRP Recovery and re-flashed TWRP and Magisk ZIP using TWRP and now sensors and phone is working fine. I know Android 10 for Mi A3 have some bugs but I decided to live with it until Stable Android 10 update made available by Xiaomi. Flashing Custom Android 10 ROMs have mixed reviews and have bugs so I decided to stay on Stock.
I tried flashing persist.img by mounting Persist partition using TWRP before doing this but nothing happens and sensors didn't worked. Now they are working.
garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
No problem in downgrade ,, i Already downgraded. No bugs facing!
---------- Post added at 06:34 AM ---------- Previous post was at 06:32 AM ----------
vjrx88 said:
I updated it to Stock Android 10 OTA update using TWRP Recovery and re-flashed TWRP and Magisk ZIP using TWRP and now sensors and phone is working fine. I know Android 10 for Mi A3 have some bugs but I decided to live with it until Stable Android 10 update made available by Xiaomi. Flashing Custom Android 10 ROMs have mixed reviews and have bugs so I decided to stay on Stock.
I tried flashing persist.img by mounting Persist partition using TWRP before doing this but nothing happens and sensors didn't worked. Now they are working.
Click to expand...
Click to collapse
Lol i came back to 9 ,, untill stable comes or i will use pixel rom ?
Kaissner said:
I had this device for two days now, one of the first things that I tried was to install a custom ROM and I was surprised of how hard it was to do, so after a lot of trial and error I managed to install those two ROMs so I wanted to share how I did it so nobody has to suffer like I
Okay so I have tried two methods, one worked for Pixel Experience and the other for Lineage OS, there are probably better ways to do this so be sure to reply to this thread if you find another ways to accomplish this!
IMPORTANT!:
1. I did the two of this methods with the stock ROM with a minimal setup (skipping wifi, no google login, no fingerprint, etc).
2.You need to have the bootloader unlocked.
3. Im not responsable if you brick your phone or lose your data, do the following steps if you know what you're doing and always back-up your data!!!
Files used:
TWRP link (Download both the img and the zip)
Pixel Experience link
LineageOS link
Gapps link
Magisk 20.1 link
Encryption patch (patch_no_fde10) link
Method 1 (Tested succesfully with Pixel Experience):
Thanks to ElSuperFullHD for creating an awesome guide in how to install Pixel Experience!
How to install Pixel Experience in Xiaomi mi a3 (Spanish guide)
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay) and reboot into recovery again (Long press Vol + when the device starts until you boot into recovery).
6. Go to advanced wipe Dalvic cache, Data and System.
7. Install Pixel Experience ROM and TWRP zip again and restart to system.
8. You're done, enjoy!
Method 2 (Tested succesfully with LineageOS):
Thanks to suschmania for your extremely helpful comment, I wouldnt have figured how to install LineageOS without him!
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. Once in TWRP copy TWRP recovery zip into the phone and wipe Dalvic cache, Data, Vendor and System.
6. Install the ROM and TWRP recovery zip (This will make the recovery to stay).
7. Reboot into recovery (twrp shows the warning no os installed, continue anyway).
8. The filesystem will be decrypted (All folders corrupted) dont worries, just go to advanced wipe and wipe internal data, once that's done copy Gapps, magisk and the encryption patch into the phone).
9. Flash Gapps, magisk (Optional) and encryption patch.
10. Reboot to system (It may take up to 10 minutes to start so give it time, if more than 10 minutes passes see step 11).
11. In case of bootlop boot back into recovery and format data (its the one where you need to write yes to format), after its done reboot to system again.
12. You're done, enjoy!
I hope this guide was helpful to you, good luck!
Click to expand...
Click to collapse
EDIT: Solved it by flashing this inofficial TWRP: https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
I have a problem. I am stuck on fastboot. I followed the tutorial unto step 4:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp.img
target reported max download size of 803475456 bytes
sending 'boot_a' (39892 KB)...
OKAY [ 0.910s]
writing 'boot_a'...
OKAY [ 0.197s]
finished. total time: 1.111s
But after this the phone always reboots to fastboot, I can't boot into TWRP or the system. Plz help.
spring_roll said:
EDIT: Solved it by flashing this inofficial TWRP: https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
I have a problem. I am stuck on fastboot. I followed the tutorial unto step 4:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp.img
target reported max download size of 803475456 bytes
sending 'boot_a' (39892 KB)...
OKAY [ 0.910s]
writing 'boot_a'...
OKAY [ 0.197s]
finished. total time: 1.111s
But after this the phone always reboots to fastboot, I can't boot into TWRP or the system. Plz help.
Click to expand...
Click to collapse
I know you solved it but the reason the other twrp wasn't working for you is because it is built only for Android pie and I'm assuming you have Android 10. That's why you always booted to fastboot. The installer.zip will work with any Android version but the twrp.img files are built using kernels of a specific Android version
garylawwd said:
I know you solved it but the reason the other twrp wasn't working for you is because it is built only for Android pie and I'm assuming you have Android 10. That's why you always booted to fastboot. The installer.zip will work with any Android version but the twrp.img files are built using kernels of a specific Android version
Click to expand...
Click to collapse
Ok thx for the info.
Another question. I didn't understand step 5:
"5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay)"
Where do I have to move and flash the ZIP? I just skipped this step and now I have the ROM installed which I wanted (PE Plus).
Do I have to do something now or is TWRP installed properly now? Can I fetch this step later?
spring_roll said:
Ok thx for the info.
Another question. I didn't understand step 5:
"5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay)"
Where do I have to move and flash the ZIP? I just skipped this step and now I have the ROM installed which I wanted (PE Plus).
Do I have to do something now or is TWRP installed properly now? Can I fetch this step later?
Click to expand...
Click to collapse
For you I don't think twrp is installed now. Some ROMs have twrp built in but if not then you have to manually flash twrp every time you flash a ROM or it gets overwritten with stock recovery.
When you flash the twrp.img and boot twrp it isn't actually installed, you are running it in ram and when you reboot it goes out of ram and your left with an un-bootable slot due to your boot slot being messed up from flashing the twrp.img and twrp won't stay installed.
For it to be installed properly you need to flash twrp.zip which will patch your boot.img with twrp and install it.
But as I said everytime you flash a ROM this will overwrite twrp and it will be gone unless the twrp.zip is flashed in twrp before rebooting.
Not as easy as it used to be by just installing twrp once and it is there forever. The new era of Android
Hi everyone!
I've been testing installing Lineage 17.1 custom ROMs on merlin, here are the steps I followed plus a LOS 17.1.
I found out that this ROM works better than MIUI and its very stable as a daily driver.
Tested on Redmi Note 9 Global (merlin) - CPU (Helio G85) - ROM/RAM: 64GB/3GB, initialy flashed over MIUI 12.0.3 Global
This are the steps I followed:
Unlock bootloader (of course)
Backup all sensitive data (it maybe lost if things go wrong)
For you in case things go wrong, also download the exact fastboot rom of the MIUI version you are using from xiaomifirmwareupdater.com (it has to be fastboot ROM becouse it contains stock recovery)
Flash a TWRP with new MIUI kernel support
Download TWRP build by wzsx15, for example
Download a modifed vbmeta.img, like the one provided in this thread
Flash like this:
Bash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
Test TWRP, at least verify it can mount and read /data.
Wipe data, cache and dalvik
Flash LOS 17.1 for merlin (details below), or anything you want to test
Details about provided LOS 17.1:
LineageOS 17.1 - UNOFFICIAL | A10.
Released : 11/02/'21
By @CosmoFreak001 & @chcepizze
SElinux permissive
Changelog:
• Fixed VoLTE
• Fixed Brightness bug
• Fixed all major bugs
• Fixed Double tap to wake
• Fixed Offline Charging
Download
Source (build using generic kernel for Mediatek Helio G85)
Works at least over:
MIUI 12.0.4 Global and less
MIUI 12.0.1 Indonesia and less
--------------
⚠WARNING⚠
MIUI 12.0.5 Global (and 12.0.2 Indonesia) and any higher version, would probably need a downgrade.
--------------
In case things go wrong:
TWRP dosen't work correctly and now my system can't boot
Restore stock recovery, vbmeta and boot partition
Go to fastboot
Extract recovery.img file from your stock fastboot ROM and flash it like this
Code:
fastboot flash recovery recovery.img
Reboot, if system dosen't boot, go to next step
Extract vbmeta.img file from stock fastboot ROM and flash it like this
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Reboot, if it can't boot, go to next step
Extract boot.img file from your stock fastboot ROM and flash all (recovery, vbmeta and boot partition) it like this
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
TWRP ask's me for a passoword
It's the first PIN number of the lockscreen you set when you first run the system
My PIN doesn't work or my phone never had a PIN and still asks me for one
Maybe /data is not accesible (TWRP compatibility problem)
Try mounting /system and /vendor partition
Navigate through them and verify you can see files and folder
If TWRP is unable to mount any partition restore stock recovery partition
If TWRP can see and mount partitions other than /data:
You can format /data (you are losing ALL data including internal storage)
I don't wont to lose all my data!
Restore stock recovery
Good work, Please note that the rom does not boot on every vendor version, So include the list of the vendors working for rom, As far as I know, it has booted successfully on MIUI 12.0.3 Global and 12.0.1 Indonesia.
Communos said:
Good work, Please note that the rom does not boot on every vendor version, So include the list of the vendors working for rom, As far as I know, it has booted successfully on MIUI 12.0.3 Global and 12.0.1 Indonesia.
Click to expand...
Click to collapse
Thanks. You are right I will add those comments.
thanks for this
Hello members after a long daunting minutes ,hours and days asking for the procedures in this forum on how i can install the custom rom on the Redmi note 9 Merlin MT 6768 3GB Ram ,64GB Rom Global version MiUI 12.0.3.0 i have managed to to install the 17.1 lineage through some experiences, First thanks to the two members who have been of help namely SparXFusion and Ma269 after i have read their post on this forum. Here is what i did i was on MIUI v11.0.4.0 which i later updated to 12.0.3.0 for this to work . Below is the procedure which i have been following and i discovered that the TWRP files i downloaded works fine from v 11.0.4 to 12.0.4.0 PROCEDURE
1- Download the TWRP file from this site : https://mega.nz/file/SuZn2QqZ#jJ6xRku...
2- Download the ADB file from this site : https://androidmtk.com/download-minim..
3- Below command prompts
fastboot devices
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash misc misc.bin
fastboot boot recovery.img
Once boot in TWRP open Wipe/format then type yes. Then go to install to get the 17.1 lineage custom rom from internal or external storage if it was downloaded there . Then fine you are good to go
All in all i have noticed that to set the email its not working may the experts explain my observation.
Waiting to hear from some members the solution
One other question is where to get the Gapps for this rom 17.1 lineage merlin mt 6768
gruka said:
Hello members after a long daunting minutes ,hours and days asking for the procedures in this forum on how i can install the custom rom on the Redmi note 9 Merlin MT 6768 3GB Ram ,64GB Rom Global version MiUI 12.0.3.0 i have managed to to install the 17.1 lineage through some experiences, First thanks to the two members who have been of help namely SparXFusion and Ma269 after i have read their post on this forum. Here is what i did i was on MIUI v11.0.4.0 which i later updated to 12.0.3.0 for this to work . Below is the procedure which i have been following and i discovered that the TWRP files i downloaded works fine from v 11.0.4 to 12.0.4.0 PROCEDURE
1- Download the TWRP file from this site : https://mega.nz/file/SuZn2QqZ#jJ6xRku...
2- Download the ADB file from this site : https://androidmtk.com/download-minim..
3- Below command prompts
fastboot devices
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash misc misc.bin
fastboot boot recovery.img
Once boot in TWRP open Wipe/format then type yes. Then go to install to get the 17.1 lineage custom rom from internal or external storage if it was downloaded there . Then fine you are good to go
All in all i have noticed that to set the email its not working may the experts explain my observation.
Waiting to hear from some memmbers the solution
Click to expand...
Click to collapse
Misc.bin isn't necessary for flashing twrp,
And what do you mean by "that to set the email it's not working"?
when you put your email on the email app you never log in , and one other question is which is the best gapps for this rom 17,1 lineage merlin
gruka said:
when you put your email on the email app you never log in , and one other question is which is the best gapps for this rom 17,1 lineage merlin
Click to expand...
Click to collapse
Pico Open Gappa or flame Gapps basic, both are fine.
And it's the stock email app, I never used it, so I don't know about that.
Hello everybody,
I have phone Xiaomi Redmi Note 8 (2021)
I have succesfuly unlocked bootloader. I wish to use GSI installed via DSU Loader and i managed to boot default GSI room offered by system this way.
Also i have used app "DSU Sideloader" and succesfuly managed to boot lineageOS GSI.
The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted.
Is there any fix for this problem? I wish to have phone rooted AND use GSI
After countless hours of searching over internet i have not found topic related to this specific issue.
Also I have tried
fastboot flash --disable-verity --disable-verification boot boot.img
and modified vbmeta.img
fastboot --disable-verification flash vbmeta vbmeta.img
no difference
But i have no idea what is holding back boot.... any help would be much appreciated
GSI related info:
Treble and VNDK - device supported
Architecture ARM64
A/B operating system
Dynamic Partitions
Talking about working GSI is there anybody which managed to install GAPPS on GSI installed via DSU? Is that even possible? how without twrp recovery?
i know that GSIs with preinstalled gapps exists i just want modular approach and install just google apps which i use.
I have found that resizing GSI system partition could help flash gapps via Ex Kernel Manager directly from the phone.
My big question is if you can resize GSI system partition without TWRP? since Note 2021 does not support recovery, if yes how?
Or can you actually set bigger system partition than system image with this command ? --el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
(following manual steps for gsi installation)
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
what would be number for 20GB size in this command? --el KEY_USERDATA_SIZE 8589934592 how i can write it correctly?
i have enough space to assign big userdata partition.
CyraxMD said:
Is there any fix for this problem? I wish to have phone rooted AND use GSI
Click to expand...
Click to collapse
I wish to have at least a working GSI installed lol.. how did u manage to boot into fastbootd ?
fastboot reboot fastboot reboots into normal fastboot/bootloader on my linux machine..
vegan_monk said:
I wish to have at least a working GSI installed lol.. how did u manage to boot into fastbootd ?
fastboot reboot fastboot reboots into normal fastboot/bootloader on my linux machine..
Click to expand...
Click to collapse
was not neccessary, check this guide which i maked how to do it:
CyraxMD said:
was not neccessary, check this guide which i maked how to do it:
Click to expand...
Click to collapse
Nice work man. Surely makes life easier for many, but in my case:
I followed all of the steps. After the GSI installation i tapped on reboot on the notification field and it rebooted into fastboot. I can not enter the GSI aswell as the recovery. Only fastboot and MIUI ROM
I installed MIUI13 from official sources via ./flash_all.sh inside the MIUI13 Recovery folder some days ago. I've done this because i think i soft bricked my device or messed with the partitions before, because i tried to flash a system image directly to the 'super' partition, becasue no fastbootd.
vegan_monk said:
Nice work man. Surely makes life easier for many, but in my case:
I followed all of the steps. After the GSI installation i tapped on reboot on the notification field and it rebooted into fastboot. I can not enter the GSI aswell as the recovery. Only fastboot and MIUI ROM
I installed MIUI13 from official sources via ./flash_all.sh inside the MIUI13 Recovery folder some days ago. I've done this because i think i soft bricked my device or messed with the partitions before, because i tried to flash a system image directly to the 'super' partition, becasue no fastbootd.
Click to expand...
Click to collapse
thx mate,
asuming you are trying to do this on Note 8 2021
ensure that you have your bootloader unlocked and your original rom is NOT rooted. You can also before you do anything with GSI custom releases test official GSI which should be available to you via DSU (connect phone via wifi not data services)
Recovery is not supported for Note 8 2021 thats why i havent mess with it despite i would love to have it. Also in my case - recovery was not needed to load unofficial GSI (just pc with adb drivers and sdk platform tools latest version).
fastbootd is not required in this case either
in some cases modified vbmeta.img is required to make it work.
if you somehow soft-bricked your device try https://www.xiaomitool.com/V2/ that should help you recover back to normal state.
CyraxMD said:
thx mate,
asuming you are trying to do this on Note 8 2021
ensure that you have your bootloader unlocked and your original rom is NOT rooted. You can also before you do anything with GSI custom releases test official GSI which should be available to you via DSU (connect phone via wifi not data services)
Recovery is not supported for Note 8 2021 thats why i havent mess with it despite i would love to have it. Also in my case - recovery was not needed to load unofficial GSI (just pc with adb drivers and sdk platform tools latest version).
fastbootd is not required in this case either
in some cases modified vbmeta.img is required to make it work.
if you somehow soft-bricked your device try https://www.xiaomitool.com/V2/ that should help you recover back to normal state.
Click to expand...
Click to collapse
many thanks for your reply mate,
i managed to flash miui12.5 again with flah_all.sh with official sources fastboot ROM via terminal. now i have recovery again. my computer has the latest adb tools installed.
i tried your dsu loader method on miui12.5 again but sadly it says "installation failed". on miui13 it said "installation success" but could not boot into it. I'm a little bit confused rn lol. i tried the phh's AOSP arm64 AB vanilla and phh's AOSP arm64 AB VNDKlite vanilla
and yes, i have the 2021 biloba version of the note 8
vegan_monk said:
many thanks for your reply mate,
i managed to flash miui12.5 again with flah_all.sh with official sources fastboot ROM via terminal. now i have recovery again. my computer has the latest adb tools installed.
i tried your dsu loader method on miui12.5 again but sadly it says "installation failed". on miui13 it said "installation success" but could not boot into it. I'm a little bit confused rn lol. i tried the phh's AOSP arm64 AB vanilla and phh's AOSP arm64 AB VNDKlite vanilla
and yes, i have the 2021 biloba version of the note 8
Click to expand...
Click to collapse
hmm you said you have recovery? do you mean twrp or cwm? if thats the case i want it too
CyraxMD said:
hmm you said you have recovery? do you mean twrp or cwm? if thats the case i want it too
Click to expand...
Click to collapse
sorry to disappoint u mate but its just the miui recovery
GSI has better performance than MIUI? Could you tell the pros and cons that you have found?
CyraxMD said:
Hello everybody,
I have phone Xiaomi Redmi Note 8 (2021)
I have succesfuly unlocked bootloader. I wish to use GSI installed via DSU Loader and i managed to boot default GSI room offered by system this way.
Also i have used app "DSU Sideloader" and succesfuly managed to boot lineageOS GSI.
The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted.
Is there any fix for this problem? I wish to have phone rooted AND use GSI
After countless hours of searching over internet i have not found topic related to this specific issue.
Also I have tried
fastboot flash --disable-verity --disable-verification boot boot.img
and modified vbmeta.img
fastboot --disable-verification flash vbmeta vbmeta.img
no difference
But i have no idea what is holding back boot.... any help would be much appreciated
GSI related info:
Treble and VNDK - device supported
Architecture ARM64
A/B operating system
Dynamic Partitions
Talking about working GSI is there anybody which managed to install GAPPS on GSI installed via DSU? Is that even possible? how without twrp recovery?
i know that GSIs with preinstalled gapps exists i just want modular approach and install just google apps which i use.
Click to expand...
Click to collapse
After seeing your video I understand that you was able to fix your initial problem:
"The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted."
It seem that you have been able to fix that problem, havent you? Have you had any problem using rooted GSI lineage? I am very insterested in rooting my phone using a GSI rom. I am going to follow your tutorial.
thanks
I have the xiaomi redmi note 8 global version (4gb/64gb) with miui 12 and adroid 11. I have unlocked it and now i wanted to install twrp on it, but I can't. I 've tried the newest version (3.6), but also older ones and orangebox too. Some don't do anything (like the twrp 3.6), some boot on the miui recovery (like the orangebox) and some get stuck on the redmi/miui boot page. Any help?
PaulosK said:
I have the xiaomi redmi note 8 global version (4gb/64gb) with miui 12 and adroid 11. I have unlocked it and now i wanted to install twrp on it, but I can't. I 've tried the newest version (3.6), but also older ones and orangebox too. Some don't do anything (like the twrp 3.6), some boot on the miui recovery (like the orangebox) and some get stuck on the redmi/miui boot page. Any help?
Click to expand...
Click to collapse
-reboot to fastboot
-flash vbmeta using : (assuming the img is named vbmeta.img) see attached
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
-flash twrp
-reboot to recovery (NOT SYSTEM !) using vol+
-flash Ofox zip
-set : "aggresive stock recovery deactivation" in Ofox settings
-done