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 ?
Original thread.
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software. *This is not entirely true for Realme devices since bootloader unlock or custom rom flash via TWRP or fastboot does not void your warranty but rooting does.
* So I heard. But that's question of detail.
* Same statement for XDA.
[DETAILED DESCRIPTION]:
I've spent my whole afternoon testing. And found out there are way more well made gsi roms out there and theoretically all of them should work. First, you gotta read this one. Then pick a gsi rom. I recommend one that has everything (must be AB image) since we don't have a working twrp yet thus can't flash opengapps but if the image file contains it then it's good to go. Go there. Pick one. Make sure it has ab-gapps-su in it's name meaning it's A/B partition dependent treble rom. Gapps means it has gapps ofc. Su means it has built in superuser (that you can ignore later for you'll be replacing it with Magisk naturally). After picking a gsi rom image successfully you can download it to your external sd card and flash it via twrp (yes, that half ass twrp for rmq provided on xda) or you can flash it via fastboot flash system system.img. Wiping data, cache, dalvik, system is necessary before doing so. Also formatting data in twrp after flashing the system image helps a lot just as OP said. If you want to try out other gsi roms you must flash stock vendor image file and do the flashing circle again. If you don't flash stock rom or stock vendor img before doing so your new gsi rom won't be able to work with screen lock. At least that's what I got on 4 different gsi roms. And one more thing. These gsi systems doesn't seem to support exfat file system. Meaning they'll want to format your external sd card. This can by bypassed if you flash lineage os boot.img. And then Magisk and at last modified vbmeta.img for RMQ. That file will make realme vendor think nothing is changed and won't try to fck you over with recovery destroyed issue.
[Prerequisites]:
unlocked bootloader
twrp recovery
External SD card
[BUGS]:
Face unlock and fingerprint isn't present on gsi roms which means they cannot work
Screen lock issue in cases when you don't flash stock vendor.img before migrating from one custom rom, be it gsi or zip to system gsi.img
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM OTHER ROM]:
!! Most of these steps are precaution !!
Read these points carefully to have a basic knowledge what you're about to do
Pick a gsi image of your choice (official Android 9 Pie, especially AOSP is highly advised)
Put your image file onto your external SD card for your internal one will likely be erased
You should grab the appropriate vendor.img and boot.img files for your device by decompressing the 7z files
Get the modified vbmeta.img file for spoofing system to boot
Get Magisk
Get SuperSu remover(Beware! It also removes Magisk if installed)
Get Lineage OS boot.img
It's better to be safe than sorry so you better download whole rom package too
Put all these files onto your external SD card
Make sure you have your twrp recovery on your external SD card too
If you done everything well you should have these on your external SD: twrp, desired system gsi.img as AB variant, your vendor.img, modified vbmeta.img, stock boot.img, Lineage OS boot.img, color os flashable.ozip/zip, Magisk, SuperSu remover
Wipe system, data, dalvik, cache
Flash stock vendor.img as vendor
Flash system gsi.img as system
Flash lineage os boot.img as boot
Flash twrp.img as recovery
Flash modified vbmeta.img as vbmeta
Reboot to system (if the device reboots into recovery you'll have to format data sadly)
After reboot successful and you've done the initial google setup steps reboot to recovery and flash superuser unroot
Flash Magsik
Reboot, now you should have a working aosp like system as I do
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM COLOR OS]:
!! You could have the same files as above just to make sure but system gsi.img,vbmeta.img,SuperSu remover,Magisk and Lineage OS boot.img should be enough if everything goes as planned and system boots for first try !!
Read the frequently asked questions, step one previously
Get your desired system gsi.img
Put your system gsi.img, twrp.img, Magisk, SuperSu remover, vbmeta.img, Lineage OS boot.img onto your external SD card
Wipe data, system, cache, dalvik
Flash system gsi.img as system
Flash lineage os boot.img
Flash twrp.img as recovery
Flash vbmeta.img ad vbmeta
Reboot (if reboots to recovery you have to format data) then do the Android setup
Reboot to recovery
Flash SuperSu remover.zip
Flash Magisk.zip
Reboot
Now your device should have successfully booted up
In case the gsi rom would be stuck on boot logo then you may reboot back to recovery by holding down volume up + power button and flash permissiver_v5.zip. It helped me boot Pixel Experience gsi rom.
Update.:
As you already know development on realme devices suck beacuse of ****ty or incomplete sources, lack of developers interest and biggest reason is lack of community support.
Our man here @BabluS is a legendary developer of Asus Zenfone Max M1 Pro and is willing to compile stable ROMs for our device. But, he needs some donations to buy the device. He has already compiled Android 10 (PE) for our device which is 99% stable. To continue this tremendous work he needs to have the device in hand.
Reasons To Donate:
1. Official PixelExperience ROM
2. Official POSP ROM
3. Will maintain & provide public Device Trees/Sources (So anyone can compile ROMs)
4. More development for realme 5 Pro
Name : Baswanth Madhav Saladi
Donate Using UPI: [email protected]
Donate using Paypal : [email protected]
Send screenshots of payment to @orgasmtron
We have to reach 6-7k in total out of which we have collected 2.6k..
Keep donating & get closer to stable custom ROM experience. Kudos!
All the donations will be public.Anyone can view and verify them.All details will be transparent.
NOTE:
We will update money collection daily evening. All details will be transparent.
List of Donators will get updated here
CLICK HERE TO CHECK!
Has anybody got Android 10 working properly?
tonibm19 said:
Has anybody got Android 10 working properly?
Click to expand...
Click to collapse
Yes. Method is same.
greenys' said:
Yes. Method is same.
Click to expand...
Click to collapse
Yeah but I mean, everything is working fine?
Fingerprint? Camera?
tonibm19 said:
Yeah but I mean, everything is working fine?
Fingerprint? Camera?
Click to expand...
Click to collapse
Dunno. As I said I never tried Android Q. But I presume fingerprint is missing and I'm quite sure no 48mp camera is present either.
What GSI File for Realme 5 Pro
what type GSI Image for Realme 5 pro, A or AB type?
Tegarcs142 said:
what type GSI Image for Realme 5 pro, A or AB type?
Click to expand...
Click to collapse
AB. On Android 9 and above you must use AB variant. It doesn't matter whether or not does your device use seamless updates. If you try to flash A only variant your device won't boot.
I installed GSI resurrection remix on my Realme 5 Pro and when I trying install Gapps get error not enough system partition. So I use resize file system in twrp and it worked.
Tegarcs142 said:
I installed GSI resurrection remix on my Realme 5 Pro and when I trying install Gapps get error not enough system partition. So I use resize file system in twrp and it worked.
Click to expand...
Click to collapse
Nice. Which twrp did you use?
greenys' said:
Nice. Which twrp did you use?
Click to expand...
Click to collapse
3.3.1-0
Tegarcs142 said:
... So I use resize file system in twrp and it worked.
Click to expand...
Click to collapse
Hi, can you please tell me what option you clicked for resizing the system partition?
the steps you did.
I tried doing that but don't find the option in TWRP.
For better experience with using gsi make sure to check Screenshot resolution if it's lower than our Device
Change Resolution :
1) download termux app
https://play.google.com/store/apps/d...?id=com.termux
2) run commands:
su
wm size 1080x2340
3) reboot*device
Enjoy better experience with gsi
greenys' said:
Original thread.
[DETAILED DESCRIPTION]:
I've spent my whole afternoon testing. And found out there are way more well made gsi roms out there and theoretically all of them should work. First, you gotta read this one. Then pick a gsi rom. I recommend one that has everything (must be AB image) since we don't have a working twrp yet thus can't flash opengapps but if the image file contains it then it's good to go. Go there. Pick one. Make sure it has ab-gapps-su in it's name meaning it's A/B partition dependent treble rom. Gapps means it has gapps ofc. Su means it has built in superuser (that you can ignore later for you'll be replacing it with Magisk naturally). After picking a gsi rom image successfully you can download it to your external sd card and flash it via twrp (yes, that half ass twrp for rmq provided on xda) or you can flash it via fastboot flash system system.img. Wiping data, cache, dalvik, system is necessary before doing so. Also formatting data in twrp after flashing the system image helps a lot just as OP said. If you want to try out other gsi roms you must flash stock vendor image file and do the flashing circle again. If you don't flash stock rom or stock vendor img before doing so your new gsi rom won't be able to work with screen lock. At least that's what I got on 4 different gsi roms. And one more thing. These gsi systems doesn't seem to support exfat file system. Meaning they'll want to format your external sd card. This can by bypassed if you flash lineage os boot.img. And then Magisk and at last modified vbmeta.img for RMQ. That file will make realme vendor think nothing is changed and won't try to fck you over with recovery destroyed issue.
[Prerequisites]:
unlocked bootloader
twrp recovery
External SD card
[BUGS]:
Face unlock and fingerprint isn't present on gsi roms which means they cannot work
Screen lock issue in cases when you don't flash stock vendor.img before migrating from one custom rom, be it gsi or zip to system gsi.img
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM OTHER ROM]:
!! Most of these steps are precaution !!
Read these points carefully to have a basic knowledge what you're about to do
Pick a gsi image of your choice (official Android 9 Pie, especially AOSP is highly advised)
Put your image file onto your external SD card for your internal one will likely be erased
You should grab the appropriate vendor.img and boot.img files for your device by decompressing the 7z files
Get the modified vbmeta.img file for spoofing system to boot
Get Magisk
Get SuperSu remover(Beware! It also removes Magisk if installed)
Get Lineage OS boot.img
It's better to be safe than sorry so you better download whole rom package too
Put all these files onto your external SD card
Make sure you have your twrp recovery on your external SD card too
If you done everything well you should have these on your external SD: twrp, desired system gsi.img as AB variant, your vendor.img, modified vbmeta.img, stock boot.img, Lineage OS boot.img, color os flashable.ozip/zip, Magisk, SuperSu remover
Wipe system, data, dalvik, cache
Flash stock vendor.img as vendor
Flash system gsi.img as system
Flash lineage os boot.img as boot
Flash twrp.img as recovery
Flash modified vbmeta.img as vbmeta
Reboot to system (if the device reboots into recovery you'll have to format data sadly)
After reboot successful and you've done the initial google setup steps reboot to recovery and flash superuser unroot
Flash Magsik
Reboot, now you should have a working aosp like system as I do
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM COLOR OS]:
!! You could have the same files as above just to make sure but system gsi.img,vbmeta.img,SuperSu remover,Magisk and Lineage OS boot.img should be enough if everything goes as planned and system boots for first try !!
Read the frequently asked questions, step one previously
Get your desired system gsi.img
Put your system gsi.img, twrp.img, Magisk, SuperSu remover, vbmeta.img, Lineage OS boot.img onto your external SD card
Wipe data, system, cache, dalvik
Flash system gsi.img as system
Flash lineage os boot.img
Flash twrp.img as recovery
Flash vbmeta.img ad vbmeta
Reboot (if reboots to recovery you have to format data) then do the Android setup
Reboot to recovery
Flash SuperSu remover.zip
Flash Magisk.zip
Reboot
Now your device should have successfully booted up
In case the gsi rom would be stuck on boot logo then you may reboot back to recovery by holding down volume up + power button and flash permissiver_v5.zip. It helped me boot Pixel Experience gsi rom.
Click to expand...
Click to collapse
Hi
I wanna install fortnite on RMQ
Through epic games I should register a realme account (but I can do that only with a Chinese phone number which I don't have )
Any solution pls
Tarikooo said:
Hi
I wanna install fortnite on RMQ
Through epic games I should register a realme account (but I can do that only with a Chinese phone number which I don't have )
Any solution pls
Click to expand...
Click to collapse
Wth no. Idk. It's not even a gsi related thing. I have no idea sorry.
hi guys i tried flashing havoc 3.0 gsi, and it works great. which one gapps should i use?
Does fingerprint and face unlock work?
This method worked on global rm5p.
I tried to flash the GSI Miui Erfan, but when entered in the initial settings, the screen cannot be touched.
Salmankapuas said:
I tried to flash the GSI Miui Erfan, but when entered in the initial settings, the screen cannot be touched.
Click to expand...
Click to collapse
Don't bother with miui. Only aosp or caf.
i flashed GSI rom, pixel, OxygenOS but the system cannot boot, only stuck on boot loading screen, is that normal?? how do i fix it?
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
DISCLAIMERS:
This help is specific for MERLIN devices only !
(Xiaomi Redmi Note 9 and Xiaomi Redmi 10X 4G)
Keep atention. This is an UNOFFICIAL thread.
This thread was based on the thread by Agent_fabulous. Thank you very much !
DON'T ask by PM. If you have any question, reply to this thread.
Keep in mind, nothing is 100% perfect, so you need to read careful
and keep trying before to ask an already answered question.
Keep your backup files safe and secure ! If you can, encrypt them.
If you try to flash in "firmware upgrade" mode, bootloader will be LOCKED again !
Never try to flash in "format all" mode ! Otherwise, you will LOSE all secure and identifying infos for your device. Like IMEI and MAC.
Never try to share your backups or your security and privacy will be compromised.
USE AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR YOUR ACTIONS.
Sorry for my bad english.
GOOD LUCK
1. Where can I find official and untouched STOCK FIRMWARES ROMS?Here, you can find latest releases: https://xiaomifirmwareupdater.com/miui/merlin/Here, you can find archive of releases: https://xiaomifirmwareupdater.com/archive/miui/merlin/
2. Where can I find some useful tools?Xiaomitool: https://www.xiaomitool.com/V2/Miflashpro: https://miflashpro.com/Miflashtool: https://xiaomiflashtool.com/Sp Flash Tool: https://spflashtools.com/category/windowsMi PC Suite: http://pcsuite.mi.com/
3. There are useful tools for LINUX or Mac OS?Xiaomitool (Linux & MacOS): https://www.xiaomitool.com/V2/Sp Flash Tool (Linux): https://spflashtools.com/category/linux
4. My pc can't detect my phone. What to do?Probably, you need to install appropriate usb drivers.Try this: https://androidmtk.com/download-mtk-usb-all-drivers
5. Where can I find custom ROMs?Here, you can find the collection of custom ROMs for MERLIN: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4291423/
6. How can I root?First and obviously, you need to unlock your bootloader. Once you unlock your bootloader, you can root your device flashing magisk patched boot.img.Here, you can find magisk patched boot images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/KEEP ATENTION: you need to disable verification for vbmeta too.Here, you can find patched vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/
7. Where can I find TWRP & PBRP?There is only ONE recovery project with open source for MERLIN.But, there are other twrp and pbrp with closed source.If you use it, you can cause damages to your device, use at your own risk and DON'T ask about it.KEEP ATENTION: you need to IGNORE misc partition, if you flash the misc partition, your phone can be stucked in boot loop.Here, you can find recovery projects images: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227751/KEEP ATENTION: you need to disable verification for vbmeta too.Here, you can find patched vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/
8. How can I restore the state of UNLOCKED BOOTLOADER?You need to restore your backup of SECCFG partition.Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4220013/
9. How to make TWRP V11.0.4.0 work on MIUI V12.0.5.0 or higher?If you are using MIUI V12.0.5.0 or higher, TWRP V11.0.4.0 will not work.Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223077/You will need to flash an older LK partition.Here, you can find lk images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
10. How can I disable TWRP?You will need to flash original stock recovery.img.Here, you can find original stock recovery images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
11. How to flash using SP FLASH TOOL without EDL and authentication?If you want to use flash tool on MIUI V12.0.5.0 or higher, it will requires EDL and authentication.Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223089/
12. I am on MIUI V12.0.5.0 or higher, how can I flash using SP FLASH TOOL without EDL and authentication?You will need to flash an older PRELOADER binary.Here, you can find preloader binaries: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218929/
13. I am on MIUI V12.0.4.0 or lower, how can I flash using SP FLASH TOOL without EDL and authentication?You will need the specific DA (download-agent) file for it without authentication (#NoAuth #NoAuthentication #No-Auth #No-Authentication).Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209765/
14. How can I downgrade MIUI version?For downgrading your miui, you need unlocked bootloader.After unlocked bootloader, you can flash older firmware rom using fastboot or sp flash tool.
15. My phone is booting to a black screen after flashed misc partition together twrp. What to do?If your phone is booting to a black screen, you need to erase MISC partition.Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
16. My phone got bootlop after installed a Magisk module or Xposed module. How can I disable it?You will need to uninstall the module. You have two methods for this.For first method, you can disable Magisk (read question 17).For second method, you need to boot in emergency mode (rescue mode).For booting in emergency mode, you need to press Vol+ (volume up) after boot starts. (YES, I mean AFTER you see boot logo.)And then, you can uninstall the module.
17. My phone got bootlop after flashed Magisk. How can I disable it?You will need to flash original stock boot.img.Here, you can find original stock boot images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
18. My phone got bootloop, I am on MIUI V12.0.4.0 or lower and I can't enter in fastboot mode or recovery mode. What to do?You need to flash stock rom using sp flash tool.Please, read question 13.
19. My phone got bootloop, I am on MIUI V12.0.5.0 or higher and I can't enter in fastboot mode or recovery mode. What to do?For this, you will need to bypass authentication and flash in EDL mode with NO auth for FREE.Here, you can find the guide for bypassing EDL authenticated mode for FREE: https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/For this, you will need an authorized account for flashing in EDL mode.You need to go the service centre for professional assistance.Please, read this: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/
20. There is any other way for flashing or unbricking?Yes. You can try any useful tool (read question 2 and 3).But, this help is not for how use them.You can find a huge amount of videos in youtube about it.
21. I want to keep with original stock boot.img together TWRP, but TWRP is removed at every reboot. What to do?You will need to flash patched boot image without overwrite of recovery.Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209263/KEEP ATENTION: you need to disable verification for vbmeta too.Here, you can find patched vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/
22. Where can I find scatter files to flash using flash tool?Here, you can find scatter files: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223097/
23. Where can I find readback file to backup using flash tool?Here, you can find read back file: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223109/
24. How can I know what is working on my phone before installing?If you want to know what is working for MERLIN, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
25. How can I disable preinstalled apps without uninstalling them?You need to perform this in command line:pm disable-user --user 0 com.android.chrome(Change com.android.chrome to desired package name to disable.)
26. Where can I find source code of the kernel?Here, you can find the OFFICIAL source code of the kernel: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/merlin-r-oss and https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/lancelot-q-ossHere, you can find the OFFICIAL source code of the kernel modules: https://github.com/MiCode/MTK_kernel_modules/tree/merlin-r-oss and https://github.com/MiCode/MTK_kernel_modules/tree/lancelot-q-oss
27. Where can I find device tree and other sources codes of MT6768?-> https://github.com/Jebaitedneko/omni_device_xiaomi_merlin-> https://github.com/Redmi-MT6768/android_device_xiaomi_merlin-> https://github.com/Redmi-MT6768/android_kernel_xiaomi_mt6768-> https://github.com/Redmi-MT6768/android_vendor_xiaomi_merlin-> https://github.com/AndroidBlobs/device_xiaomi_merlin-> https://github.com/AndroidBlobs/vendor_xiaomi_merlin-> https://github.com/SparXFusion/android_device_xiaomi_merlin-> https://github.com/SparXFusion/android_kernel_redmi_mt6768-> https://github.com/JamieHoSzeYui/android_device_xiaomi_merlin-> https://github.com/surblazer/android_device_xiaomi_merlin-> https://github.com/surblazer/android_kernel_xiaomi_mt6768-> https://github.com/ZyCromerZ/android_kernel_xiaomi_mt6768-> https://github.com/Box-boi/android_kernel_xiaomi_mt6768-> https://github.com/Box-boi/omni_device_xiaomi_merlin-> https://github.com/Box-boi/android_device_xiaomi_merlin-> https://github.com/Box-boi/android_vendor_xiaomi_merlin-> https://sourceforge.net/projects/zyc-kernels/files/Merlin
28. How to pass SafetyNet?You will need to have Xposed installed. After it, everything you need to do is install HiddenCore-Module, active it on Xposed Manager and reboot.Here, you can find the HiddenCore-Module: https://repo.xposed.info/module/com.cofface.ivaderKEEP ATENTION: it is making android to keep on activity forever and never suspends screen.You can use the patched apk by Evengard: https://forum.xda-developers.com/t/hiddencore-module-what-was-it-doing.3903984/post-81982121.
29. How to disable ads (advertising)?You will need to have Xposed installed. After it, everything you need to do is install AdBlocker-Reborn, active it on Xposed Manager and reboot.Here, you can find the AdBlocker-Reborn: https://repo.xposed.info/module/com.aviraxp.adblocker.continuedKEEP ATENTION: some people said it can get troubles to google apps.
30. How to restore IMEI, Baseband, MAC, fix NVRAM WARNING and fix NVDATA CORRUPTED?KEEP ATENTION: never try to restore partitions from a different device, or you can brick and cause damages to your device.Here, you can find the guide: https://forum.xda-developers.com/t/...-on-merlin-redmi-note-9-redmi-10x-4g.4230423/
31. How to disable ads (advertising) without xposed?For unrooted devices, you need to perform this in command line:pm disable-user --user 0 com.miui.msa.globalFor rooted devices, you need to debloat your system and then remove the "MSA" app.
32. What should I backup before trying to customize my device?Here, you can find the list of what partitions you need to backup for avoiding mistakes without risking all of your device's identification details, like IMEI, WiFi MAC, Bluetooth MAC, calibration data, NVDATA, NVRAM, RADIO/MODEM/BASEBAND and others: https://forum.xda-developers.com/t/...lin-device-redmi-note-9-redmi-10x-4g.4229629/
33. How to bypass authentication and flash in EDL with NO auth for FREE?Here, you can find the guide for bypassing EDL authenticated mode for FREE: https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
34. How to install XPOSED?1. You need to unlock your bootloader.2. You need to root using Magisk.3. You need to install magisk manager.4. You need to install the magisk module: RIRU. (Only Riru in the name).5. You need to choose between EDXPOSED or LSPOSED and then install the magisk module: "Riru Edxposed" or "Riru Lsposed".6. You need to install the properly manager: "Edxposed Manager" or "Lsposed Manager".7. Reboot.Done. Enjoy !
35. How to remove and clear GOOGLE ACC and Mi ACC / MiCloud?Here, you can find the guide for removing google account and xiaomi account: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4233977/
36. How can I flash a CUSTOM ROM?Here, you can find the guide for flashing custom roms by c.whoopee: https://forum.xda-developers.com/t/...rom-on-a-redmi-note-9-global-variant.4234151/(Thanks to c.whoopee)Here, you can find the guide for installing a Lineage 17.1 ROM by ma259: https://forum.xda-developers.com/t/...eage-17-1-rom-in-redmi-note-9-merlin.4235003/(Thanks to ma259)
37. How to properly use the SP Flash Tool?Here, you can find the guide how to configure correctly the SPFlashTool: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4229937/Here, you can find common errors of the SPFlashTool: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
38. How to solve "LIB DA not match" error?Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
39. How to solve "PMT changed for the ROM" error?Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
40. How to solve "STATUS_BROM_CMD_STARTCMD_FAIL" error?Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
41. How to solve "STATUS_SEC_AUTH_FILE_NEEDED" error?Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
42. How to solve "STATUS_BROM_CMD_FAIL" error?Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
43. How to solve "STATUS_BROM_CMD_SEND_DA_FAIL" error?Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/44. Where can I find official ENGINEERING ROMs?Here, you can find ENGINEERING ROM V1: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227933/Here, you can find ENGINEERING ROM V2: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4246891/
45. Where can I find extracted FIRMWARES?Here, you can find the thread of the EXTRACTED FIRMWARE by yshalsager: https://forum.xda-developers.com/t/...-4g-redmi-note-9-merlin-auto-updated.4250261/Here, you can find latest releases: https://xiaomifirmwareupdater.com/firmware/merlin/Here, you can find archive of releases: https://xiaomifirmwareupdater.com/archive/firmware/merlin/
46. Where can I find extracted VENDORS?Here, you can find latest releases: https://xiaomifirmwareupdater.com/vendor/merlin/Here, you can find archive of releases: https://xiaomifirmwareupdater.com/archive/vendor/merlin/
47. How can I mount system RW (read-write) ?Here, you can find the guide and the script by lebigmac for mounting system as read-write (RW): https://forum.xda-developers.com/t/...unt-system-read-write-super-no_super.4247311/
48. How to write and recover the IMEI for SLOT 1 and SLOT 2?Here, we are discussing about the possibilities of how to recover the IMEI for SLOT1 and SLOT2: https://forum.xda-developers.com/t/...-in-merlin-redmi-note-9-redmi-10x-4g.4258779/Here, you can find md1img images of the baseband/modem/radio: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4258919/49. Where can I find custom KERNEL?-> https://sourceforge.net/projects/zyc-kernels/files/Merlin/-> https://github.com/JamieHoSzeYui/dream/releases-> MOD EDIT: Link Removed50. How to skip & avoid EDL auth bypass and FLASH in DOWNLOAD MODE?Here, you can find the guide: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4322631/
Full List of My Own Threads:
[V12.5.2.0][Android 11.0] New Update: Download Files for Merlin V12.5.2.0.RJOMIXM
https://forum.xda-developers.com/t/...-0-rjomixm-redmi-note-9-redmi-10x-4g.4357045/
[V12.5.1.0][Android 11.0] New Update: Download Files for Merlin V12.5.1.0.RJOMIXM
https://forum.xda-developers.com/t/...-0-rjomixm-redmi-note-9-redmi-10x-4g.4321093/
[V12.0.1.0][Android 11.0] New Update: Download Files for Merlin V12.0.1.0.RJOMIXM
https://forum.xda-developers.com/t/...-0-rjomixm-redmi-note-9-redmi-10x-4g.4295435/
[V12.0.8.0] New Update: Download Files for Merlin V12.0.8.0.QJOMIXM
https://forum.xda-developers.com/t/...-0-qjomixm-redmi-note-9-redmi-10x-4g.4285863/
[V12.0.7.0] New Update: Download Files for Merlin V12.0.7.0.QJOMIXM
https://forum.xda-developers.com/t/...-0-qjomixm-redmi-note-9-redmi-10x-4g.4245351/
[BOOT][PATCHED] Boot Image Partition without OVERWRITE OF RECOVERY for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209263/
[DA][FLASH] DA files for flashing to MERLIN using FLASH TOOL
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209765/
[V1][ENGINEERING][ROM] OFFICIAL Egineering Firmware for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227933/
[V2][ENGINEERING][ROM] OFFICIAL Egineering Firmware for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4246891/
[FAQ][GUIDE][HELP] Assistance Solution Centre for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
[DISCUSSION][ROM][CUSTOM] What is the BEST CUSTOM ROM for MERLIN ?
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4291423/
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE
https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
[GUIDE]How to properly solve the errors of the SP FLASH TOOL for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
[GUIDE] How to properly use the SP FLASH TOOL for MERLIN ?
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4229937/
[GUIDE] How to remove and clear GOOGLE ACC and Mi ACC / MiCloud for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4233977/
[GUIDE] How to restore IMEI, Baseband, MAC, fix NVRAM WARNING and fix NVDATA CORRUPTED on MERLIN ?
https://forum.xda-developers.com/t/...-on-merlin-redmi-note-9-redmi-10x-4g.4230423/
[GUIDE] What should I backup before trying to customize my MERLIN device ?
https://forum.xda-developers.com/t/...lin-device-redmi-note-9-redmi-10x-4g.4229629/
[GUIDE][FLASH] How to keep flashing without AUTH or EDL on V12.0.5.0 or higher MIUI versions in MERLIN ?
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223089/
[GUIDE][TWRP] How to keep TWRP V11.0.4.0 working on MIUI V12.0.5.0 or higher MIUI versions in MERLIN ?
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223077/
[DISCUSSION] How to write and recover the IMEI for SLOT 1 and SLOT 2 in MERLIN ?
https://forum.xda-developers.com/t/...-in-merlin-redmi-note-9-redmi-10x-4g.4258779/
[GUIDE][UNBRICK] How unbrick your bootloop in MERLIN after flashing TWRP
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
[GUIDE][UNLOCK] How to restore the state of UNLOCKED BOOTLOADER in MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4220013/
[LK][STOCK] LK Image Partition for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
[BASEBAND][STOCK][MD1IMG] MODEM Image Partition for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4258919/
[MAGISK][XPOSED] What is working for Magisk and Xposed in MERLIN ?
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
[PRELOADER][STOCK] PRELOADER Partition Binary for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218929/
[READBACK][FLASH] Read Back file for backuping using flash tool from MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223109/
[SCATTER][FLASH] Scatter file for flashing using flash tool to MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223097/
[STOCK][PATCHED] Boot, Vbmeta and Recovery: Images Partitions for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
[RECOVERY PROJECT] Collection of TWRP & PBRP & SHRP & ORANGEFOX for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227751/
[VBMETA][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/
[GUIDE] How to skip & avoid EDL auth bypass and FLASH in DOWNLOAD MODE for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4322631/
TWRP does work above 12.0.5, I have tested.
New build: https://tdrive.elytra8.workers.dev/image-new.img
Flash like you flash any other custom recovery.
For ADS in MIUI, using debloat tool and removing MSA does the job.
Communos said:
TWRP does work above 12.0.5, I have tested.
New build: https://tdrive.elytra8.workers.dev/image-new.img
Flash like you flash any other custom recovery.
For ADS in MIUI, using debloat tool and removing MSA does the job.
Click to expand...
Click to collapse
Thank you very much.
Both were added on FAQ & GUIDE.
Here, you can find unofficial recovery project with closed source: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227751/
Uhm... hello, newbie here and hopefully in the right thread.
I have a Redmi Note 9 and wanted to install LineageOS. What I have done so far:
Jumped through all the hoops to unlock the bootloader.
Since that erases all user data, I did not bother setting a password in the setup. Just went through it as quickly as possible.
Installed TWRP 12.0.6
Used that to install lineage-17.1-20210209-UNOFFICIAL-merlin.zip from here.
Result: The new system does not boot. I always end up in TWRP again. Even if I specifically go to Reboot -> System, it'll boot into recovery. I think the first boot fails and then it goes into recovery (if I power the device off and on again, it vibrates, the logo comes on, the screen goes black, it vibrates again, the logo shows again, and then I'm in TWRP).
What I have tried unsuccessfully:
Flashing the vbmeta from here.
Erasing the misc partition.
Flashing the old lk from here.
Closing the AVB2.0 after flash (with and without closing DM verity).
Wiping cache, dalvik, data, internal storage, and cache before reinstalling LOS.
Replacing TWRP with PBRP and trying again.
Probably some other things I don't remember. I've been chasing red herrings through this rabbit hole all day.
I also tried to install the ArrowOS build (from here), just to have one more datapoint. After that, the device boot-loops into the bootloader, and I have to manually go into recovery via VolUp+Power. This leads me to believe that it's not the LOS build at fault. It seems more likely that I am a moron and am doing something wrong. I just can't figure out what it is.
Any help would be appreciated.
MyBrainIsAStrainer said:
Uhm... hello, newbie here and hopefully in the right thread.
I have a Redmi Note 9 and wanted to install LineageOS. What I have done so far:
Jumped through all the hoops to unlock the bootloader.
Since that erases all user data, I did not bother setting a password in the setup. Just went through it as quickly as possible.
Installed TWRP 12.0.6
Used that to install lineage-17.1-20210209-UNOFFICIAL-merlin.zip from here.
Result: The new system does not boot. I always end up in TWRP again. Even if I specifically go to Reboot -> System, it'll boot into recovery. I think the first boot fails and then it goes into recovery (if I power the device off and on again, it vibrates, the logo comes on, the screen goes black, it vibrates again, the logo shows again, and then I'm in TWRP).
What I have tried unsuccessfully:
Flashing the vbmeta from here.
Erasing the misc partition.
Flashing the old lk from here.
Closing the AVB2.0 after flash (with and without closing DM verity).
Wiping cache, dalvik, data, internal storage, and cache before reinstalling LOS.
Replacing TWRP with PBRP and trying again.
Probably some other things I don't remember. I've been chasing red herrings through this rabbit hole all day.
I also tried to install the ArrowOS build (from here), just to have one more datapoint. After that, the device boot-loops into the bootloader, and I have to manually go into recovery via VolUp+Power. This leads me to believe that it's not the LOS build at fault. It seems more likely that I am a moron and am doing something wrong. I just can't figure out what it is.
Any help would be appreciated.
Click to expand...
Click to collapse
Hey, Custom roms for Redmi Note 9 need MIUI 12.0.1 Indonesia, or MIUI 12.0.3 global vendor.
Downgrade your phone to the specific MIUI vendor, and then try flashing custom rom.
Here's the link for global 12.0.3
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
And before you downgrade your miui version, please erase system and vendor to bypass anti roll back.
Use these commands after connecting device in fastboot mode:
fastboot reboot fastboot
fastboot erase system
fastboot erase vendor
fastboot reboot bootloader
Then flash the 12.0.3 global/12.0.1 Indonesia miui version through MiFlash.
Or
You could give flashing 12.0.1 Indonesia vendor in TWRP, and then flashing rom.
If after fastboot reboot fastboot it shows waiting for device, install this driver. https://drive.google.com/file/d/1JFYCZ3mu_Y_xpnS7QrmtwqOeFnWg6DO2/view?usp=sharing
Please note that you need to be on stock recovery for fastboot reboot fastboot to work.
Happy flashing
Thank you very much! With that info, I think I finally have it working!
I case it's helpful for future users, here are some issues I encountered along the way:
Communos said:
fastboot reboot fastboot
fastboot erase system
fastboot erase vendor
Click to expand...
Click to collapse
Code:
$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
$ fastboot erase system
erasing 'system'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.013s
$ fastboot erase vendor
erasing 'vendor'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.012s
Is that normal? I do have a partition named 'super' that I can see in the TWRP backup module. Judging from its size, that could be the system partition. I think there's also a vbmeta_system and vbmeta_vendor, did you mean those?
Then flash the 12.0.3 global/12.0.1 Indonesia miui version through MiFlash.
Or
You could give flashing 12.0.1 Indonesia vendor in TWRP, and then flashing rom.
Click to expand...
Click to collapse
Ok, so I downloaded the full ROM for 12.0.3 global. I'm using Linux, so MiFlash won't work. But the ROM archive I downloaded contained a bunch of partition images and a shell script that would flash them using the fastboot command. I just ran that script. Windows users probably could have run the .bat file that was also included. There were no errors. And after a reboot, MIUI started to boot and presented me with the setup procedure.
I did not complete the setup (I suspect it would have just auto-updated MIUI to something that would have caused problems again) and used the power button to go into the bootloader.
From there, I flashed TWRP again (since it got overwritten by the script mentioned above), went into recovery mode, and tried to install LOS again. First, flashing seemed to hang. The last messages in the log were:
Code:
Installing file '/external_sd/Download/lineage-17.1-20210209-UNOFFICIAL-merlin.zip'
Checking for Digest file...
Target: Redmi/merlin_eea/merlin:10/QP1A.190711.020/V11.0.2.0.QJOEUXM:user/release-leys
And that was it. The border around the progress bar was doing it's busy animation thing and after waiting for 10 minutes, I used the power button to reset the device.
The second attempt went through fine, and now I have LineageOS running on the device. I still need to play around with it some more to see if there are any issues, but the flashing itself seems to have worked.
Again, thank you for your help!
MyBrainIsAStrainer said:
Thank you very much! With that info, I think I finally have it working!
I case it's helpful for future users, here are some issues I encountered along the way:
Code:
$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
$ fastboot erase system
erasing 'system'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.013s
$ fastboot erase vendor
erasing 'vendor'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.012s
Is that normal? I do have a partition named 'super' that I can see in the TWRP backup module. Judging from its size, that could be the system partition. I think there's also a vbmeta_system and vbmeta_vendor, did you mean those?
Ok, so I downloaded the full ROM for 12.0.3 global. I'm using Linux, so MiFlash won't work. But the ROM archive I downloaded contained a bunch of partition images and a shell script that would flash them using the fastboot command. I just ran that script. Windows users probably could have run the .bat file that was also included. There were no errors. And after a reboot, MIUI started to boot and presented me with the setup procedure.
I did not complete the setup (I suspect it would have just auto-updated MIUI to something that would have caused problems again) and used the power button to go into the bootloader.
From there, I flashed TWRP again (since it got overwritten by the script mentioned above), went into recovery mode, and tried to install LOS again. First, flashing seemed to hang. The last messages in the log were:
Code:
Installing file '/external_sd/Download/lineage-17.1-20210209-UNOFFICIAL-merlin.zip'
Checking for Digest file...
Target: Redmi/merlin_eea/merlin:10/QP1A.190711.020/V11.0.2.0.QJOEUXM:user/release-leys
And that was it. The border around the progress bar was doing it's busy animation thing and after waiting for 10 minutes, I used the power button to reset the device.
The second attempt went through fine, and now I have LineageOS running on the device. I still need to play around with it some more to see if there are any issues, but the flashing itself seems to have worked.
Again, thank you for your help!
Click to expand...
Click to collapse
Oh you're using Linux, for Linux the commands is
/.fastboot reboot fastboot
Great to know you were able to flash successfuly. Note that first boot in all roms is a bootloop, you just have to force reboot after a minute of bootlogo showing up or so.
hi i flashed a wrong twrp and now the phone keeps bootlooping, cannot enter recovery or fastboot by power + vol (+ or -)
adb from computer doesn't detect
sp flash tool doesn't move when i hit "download" button
bootloader unlocked, root yes
pc notificates a device connection by sound
phone redmi note 9
thank you for the help really cannot figure it out
Kain105 said:
hi i flashed a wrong twrp and now the phone keeps bootlooping, cannot enter recovery or fastboot by power + vol (+ or -)
adb from computer doesn't detect
sp flash tool doesn't move when i hit "download" button
bootloader unlocked, root yes
pc notificates a device connection by sound
phone redmi note 9
thank you for the help really cannot figure it out
Click to expand...
Click to collapse
Apparentely, you need to flash in EDL mode.
So, you need to bypass the authentication in EDL mode first.
Read this: https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
Newbie Android user here, hopefully i’m on the correct thread...i have a Redmi Note 9 with MIUI Global version 11.0.5 and Magisk version 20.4.
I tried updating Magisk to the latest version using the direct install option but I keep getting an error. I was told I need manually patch the boot.img and flash it but I need to create a magisk_patch.img first from the boot.img.
I read some of the guides on this thread but I’m not sure which one to follow. Also the steps to create the magisk_patch.image shows I need to click the Install button on Magisk then Select and Patch a file. I only have the Update button on Magisk, can I use that instead?
Or if you have other suggestion how to fix my issue. I attached the error I’m getting when I’m updating Magisk.
Thank you in advance for the assistance.
E77en12 said:
Newbie Android user here, hopefully i’m on the correct thread...i have a Redmi Note 9 with MIUI Global version 11.0.5 and Magisk version 20.4.
I tried updating Magisk to the latest version using the direct install option but I keep getting an error. I was told I need manually patch the boot.img and flash it but I need to create a magisk_patch.img first from the boot.img.
I read some of the guides on this thread but I’m not sure which one to follow. Also the steps to create the magisk_patch.image shows I need to click the Install button on Magisk then Select and Patch a file. I only have the Update button on Magisk, can I use that instead?
Or if you have other suggestion how to fix my issue. I attached the error I’m getting when I’m updating Magisk.
Thank you in advance for the assistance.
Click to expand...
Click to collapse
You can't install the magisk using the direct option.
You need to the patch the boot.img file and then flash the magisk_patched.img using fastboot (or spflashtool).
VD171 said:
You can't install the magisk using the direct option.
You need to the patch the boot.img file and then flash the magisk_patched.img using fastboot (or spflashtool).
Click to expand...
Click to collapse
Thank you, it worked. Now my magisk is updated
E77en12 said:
Thank you, it worked. Now my magisk is updated
Click to expand...
Click to collapse
Good work, my friend.
You are welcome
HELP PLS
i first flashed the patched_magisk.img then i got in a twrp boot loop. When i try to reboot into the system i get back to twrp menu.
Then i panicked and went to WIPE and factory reseted,
but it got stuck again. Then i powered it off.
How do i get out of this? I wanted to flash the stock boot.img but the storage folders has strange names
EDIT:
i figured it out what i have done. The data was ecrypted so i formated the data. But now i have another problem:
I installed linageOS from here, but when want to reboot back to system it says
No OS Installed! Are you sure you wish to reboot? i don't undertand why the custom rom didn't install.
I just copied the .zip file with the custom rom in the phone and hit install in TWRP. What did i do wrong?
George528 said:
HELP PLS
i first flashed the patched_magisk.img then i got in a twrp boot loop. When i try to reboot into the system i get back to twrp menu.
Then i panicked and went to WIPE and factory reseted,
but it got stuck again. Then i powered it off.
How do i get out of this? I wanted to flash the stock boot.img but the storage folders has strange names
View attachment 5289089
EDIT:
i figured it out what i have done. The data was ecrypted so i formated the data. But now i have another problem:
I installed linageOS from here, but when want to reboot back to system it says
No OS Installed! Are you sure you wish to reboot? i don't undertand why the custom rom didn't install.
I just copied the .zip file with the custom rom in the phone and hit install in TWRP. What did i do wrong?
Click to expand...
Click to collapse
Did you flash the patched vbmeta too?
VD171 said:
Did you flash the patched vbmeta too?
Click to expand...
Click to collapse
do you have a full step-by-step guide for this? i am feeling lost rn. I only have your FAQ but it doesnt cover everything
George528 said:
do you have a full step-by-step guide for this? i am feeling lost rn. I only have your FAQ but it doesnt cover everything
Click to expand...
Click to collapse
Steps for flashing vbmeta are same for every device.
You may try to use the search.
Here, you can find patched vbmeta for MERLIN:
[VBMETA][IMG][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED VBMETA.IMG for MERLIN by VD171 For what do I need it ? If you try to flash any custom partition, your device can bricks or gets in bootloop. This patch with disabled verity and disabled verification avoid it and need to be flashed once...
forum.xda-developers.com
VD171 said:
Steps for flashing vbmeta are same for every device.
You may try to use the search.
Here, you can find patched vbmeta for MERLIN:
[VBMETA][IMG][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED VBMETA.IMG for MERLIN by VD171 For what do I need it ? If you try to flash any custom partition, your device can bricks or gets in bootloop. This patch with disabled verity and disabled verification avoid it and need to be flashed once...
forum.xda-developers.com
Click to expand...
Click to collapse
no, i mean a full guide for rooting from the beggining to end, for redmi note 9. For example i missed the vbmeta and this resulted in an error. Now i have to flash the stock firmware and wait for another 7 days for it to unlock. For newbies like me, this looks like a mess. If you don't have one, can you please create one? Do it for us, newcomers. Thanks
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