Hello, I need help what happens is that my F3 I changed the rom and recently came out an update of evolution X and after that update I started with a problem what happens is that the signal goes away and when that happens the phone restarts and sometimes happens often coming to restart more than 10 times in 5 minutes.
alguien 1.5 said:
Hello, I need help what happens is that my F3 I changed the rom and recently came out an update of evolution X and after that update I started with a problem what happens is that the signal goes away and when that happens the phone restarts and sometimes happens often coming to restart more than 10 times in 5 minutes.
Click to expand...
Click to collapse
Hi, Are you using the correct firmware for your region,
i use V14.0.2.0 TKHINXM_13, my F3 is a EEA EU Version,
how old was your Original Evo-X rom, Did you try posting your issue on the Evo-X Thread.
Aggelos (the Evo-X DEV) suggested the correct firmware and also to format data if coming from a older version of Evo-X.
I am a Evo-X patron and the rom is amazing, i always update via TWRP Recovery and not by OTA as i loose custom recovery.
johnr64 said:
Hi, Are you using the correct firmware for your region,
i use V14.0.2.0 TKHINXM_13, my F3 is a EEA EU Version,
how old was your Original Evo-X rom, Did you try posting your issue on the Evo-X Thread.
Aggelos (the Evo-X DEV) suggested the correct firmware and also to format data if coming from a older version of Evo-X.
I am a Evo-X patron and the rom is amazing, i always update via TWRP Recovery and not by OTA as i loose custom recovery.
Click to expand...
Click to collapse
thank you very much for the help, the last update I installed it from the previous update so it was not very old and I tried to go back to the previous update but still the same failure.and my recovery is orange fox because recently I had twrp but it failed me
alguien 1.5 said:
thank you very much for the help, the last update I installed it from the previous update so it was not very old and I tried to go back to the previous update but still the same failure.and my recovery is orange fox because recently I had twrp but it failed me
Click to expand...
Click to collapse
Hi,
I would back up your "Apps and there Data" using DataBackup.apk and save them to a safe place, i use a OTG Adaptor, install "Temporary Recovery" I use TWRP, make TWRP Permanent, Format Data and see if it helps,
I put all the programs i use when switching between roms into the TR folder,
____________________________________________________________________________
From a previous post below:
Hi,
Boot your F3 into fastboot mode and connect to a PC,
Download "Temporary Recovery" and unzip, run the "RUN ME Temporary TWRP A13-Orange Fox Recovery.bat" file and choose TWRP.
Once rebooted select: Advanced from within TWRP and tap "Flash current TWRP", copy over the included Magisk files into the internal memory (I use a OTG adaptor and USB Stick), install Magisk V26.1.apk, when in recovery you can install Magisk as a .apk format.
Included are the files i use when switching between roms, included are the latest, Magisk V26.1 and Magisk Delta, it also includes the latest versions of TRWP/OrangeFox recovery and other goodies,
I hope it helps
Related
I was looking for a TWRP for the Xiaomi Mi Mix 2. I've found a chinese board where a user called YouLinw compiled TWRP for us. According to him and the users there (Google Translator) it seems to work. Can't test it by now, because my Xiaomi Mi Mix 2 isn't shipped right now. It was really tricky to register in this chinese board and then to download the file. You can download it yourself in the board and for all other users I made a mirror with no registration.
There's now a new english TWRP from Xiaomi.eu.
I don't take any responsibilities for this file. If you break or damage your phone, it's your fault!
The recovery is in chinese - but you shuold be able to use it with screenshots in your language.
Download: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=12
Credits: https://xiaomi.eu/community/threads/twrp-3-1-1-for-xiaomi-mix-2.41634/
Installation:
Unlock your phone - http://en.miui.com/unlock/
Download TWRP from the link above
Flash over Fastboot
Hope you like it.
Great find! Any idea what version of SuperSU can be used to root The device ?
In this chinese board there's something written like, that SuperSu 2.82 is suitable for the Mix 2 (without guarantee).
PJF16 said:
I was looking for a TWRP for the Xiaomi Mi Mix 2. I've found a chinese board where a user called YouLinw compiled TWRP for us. According to him and the users there (Google Translator) it seems to work. Can't test it by now, because my Xiaomi Mi Mix 2 isn't shipped right now. It was really tricky to register in this chinese board and then to download the file. You can download it yourself in the board and for all other users I made a mirror with no registration.
I don't take any responsibilities for this file. If you break or damage your phone, it's your fault!
The recovery is in chinese - but you shuold be able to use it with screenshots in your language.
Credits & Download: http://bbs.zhiyoo.com/.php?mod=viewthread&tid=13431779&extra=page=1&page=1&state=1
Download (Mirror): https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=11
Installation:
Unlock your phone - http://en.miui.com/unlock/
Download TWRP from the link above
Flash over Fastboot
Hope you like it.
Click to expand...
Click to collapse
I find another TWRP under mi-globe.com You can try to download at below link:
https://www.filehost.com/?fid=817550096634801044
I added now a new TWRP from a Xiaomi.eu Founder.
Xiaomi.eu released rom for Mi Mix 2, it's called chiron. TWRP as the linked it, here. Might be the same as the OP linked tho.
Should work. My phone arrives next week i will test it.
Yes, it's the same (also see Credits).
PJF16 said:
I added now a new TWRP from a Xiaomi.eu Founder.
Click to expand...
Click to collapse
Me too comes to me next week. I will try it.
Hello guys,
I've flash with fastboot TWRP for my mix2 but when i restarted with fasboot on TWRP it ask me for a password.
Second point : I have no access to files like the xiaomi.eu rom stored on my phone.
anyone faced these issue and is there any solution ? (the bootloader is well unlocked)
ANd when i restart in recovery my phone with power and vol + button, i have the xiaomi recovery and not TWRP.
It is strange, no ??
Thanks for your help
PJF16 said:
In this chinese board there's something written like, that SuperSu 2.82 is suitable for the Mix 2 (without guarantee).
Click to expand...
Click to collapse
Can confirm, superSU 2.82 works on Xiaomi EU rom version 7.9.22
unable to mount /system after nadroid backup
TWRP installed fine and experienced no issues until I made a full Nandroid backup. After the backup I have issues flashing because the device is unable to mount /system . busy or in use error.
So now I wait until official TWRP.
If you are having any twrp issues just reboot into twrp and the issues will be gone. Try again!
Dust2Dust said:
TWRP installed fine and experienced no issues until I made a full Nandroid backup. After the backup I have issues flashing because the device is unable to mount /system . busy or in use error.
So now I wait until official TWRP.
Click to expand...
Click to collapse
Same here
***TAPATALKING***
Is this recovery work on Xiaomi Miui 9 beta rom....?
brunsman6229 said:
Is this recovery work on Xiaomi Miui 9 beta rom....?
Click to expand...
Click to collapse
I am using TWRP with the EU beta 9.
真的假的？
tnt3400 said:
真的假的？
Click to expand...
Click to collapse
English please.
MementoM said:
For the life of me I cannot get this TWRP to do anything. My phone came with Global 8.5 Stable. I confirmed my bootloader is unlocked. I flashed the TWRP and booted it, it boots fine but trying to backup anything I get Failed to unmount "/system" (Device or resource busy). I tried to reboot back into TWRP still same problem, I tried to reflash TWRP through both fastboot and TWRP image installer. I downloaded the EU rom and tried to flash it and it also failed to flash. OEM unlock is checked, USB debugging is on. TWRP gets over written with the Mi Mix recovery whenever I boot back into system, it doesn't ask me if I want to modify anything when it first boots. Why is this giving me so much trouble I've never encountered this problem with TWRP. Any Advice?.
Thanks much
Click to expand...
Click to collapse
There is still no official TWRP available. I always do a full wipe factory reset and manual wipe everything before flashing anything. I also get the errors, but I've never tried to restore a backup because I usually just do clean installs each time because the ROMs available right now aren't stable enough for daily use.
The trick for EU rom is complete wipe than boot back into TWRP and try flashing. You will get 2 errors but will install fine. You can install USB drive or transfer EU rom through mtp via TWRP.
I'll do it like @allrockedout
It seems this TWRP is more beta than stable :-/
Also check the "Mount" button and uncheck the option to open all partitions readonly.
Then reboot TWRP. Last but not least before performing any flash operations (ROM or Magisk/SU-Stuff) check all partitions as marked - then do your flash work
i also miss some more partition that are available to other devices like EFS.
Did anyone know about another TWRP version or devs that are working on one?
raupe said:
I'll do it like @allrockedout
It seems this TWRP is more beta than stable :-/
Also check the "Mount" button and uncheck the option to open all partitions readonly.
Then reboot TWRP. Last but not least before performing any flash operations (ROM or Magisk/SU-Stuff) check all partitions as marked - then do your flash work
i also miss some more partition that are available to other devices like EFS.
Did anyone know about another TWRP version or devs that are working on one?
Click to expand...
Click to collapse
I recommend twrp by @IceMan_it https://www.movilesdualsim.com/index.php?threads/180006
For backup and Restore (with EFS!) with Linux 64 bit https://www.movilesdualsim.com...rilinguee.180989/#post-2060493
Credit: @IceMan_it
Inviato dal mio Mi Note 2 utilizzando Tapatalk
Good evening guys
I have a Xiaomi 5s stock rom MIUI9 with TWRP 3.2 (capricorn)
I was using the old supersu.apk to have root privilegs. I remove it completly to install the Magisk but I'm getting error 1
Follow the pictures...
As you can see I have the unlock boot, twrp, stock rom and not rooted... Tried others topics and tips to install the Magisk but It wont work...
What should I do?
(Xiaomi forum I saw a guy he installed the stock rom and full restored and he continues with error:1)
Resolution:
Change TWRP 3.2.1-1 to TWRP ZCX
Download stock rom (same as you're using)
Open the .iso with winrar or other software
Get the boot.img and put it in smartphone sdcard
Reboot in the recovery mod
Select install and change to install a IMG
Select boot.img and the partition BOOT
Install the magisk (feel free to put any version, I used v14)
Reboot and enjoy! :laugh:
PS: You dont need to unistall first your root because it'll be replaced when you install the stock boot.
Use magisk 15.2, make sure zip file not corrupt.
Even better use TWRP 3.2.1.1 and flash Magisk 16. That combination has some serious bugs ironed out.
BajinganTengik said:
Use magisk 15.2, make sure zip file not corrupt.
Click to expand...
Click to collapse
I tried with Magisk 15.3 and failed, same error. (ERROR:1)
8166uy said:
Even better use TWRP 3.2.1.1 and flash Magisk 16. That combination has some serious bugs ironed out.
Click to expand...
Click to collapse
I'm using the TWRP 3.2.1-1 is the same thing, I saw in Xiaomi Forum about the TWRP ZCX but I dont know what is the difference...
Does anyone have a fix to it?
Resolved, tip in the first post.
You could try the Xiaomi.eu ROM which has better support for rooting and adds some polish to MIUI (and also implements every weekly beta release of the official repo). Does require a clean install though.
8166uy said:
You could try the Xiaomi.eu ROM which has better support for rooting and adds some polish to MIUI (and also implements every weekly beta release of the official repo). Does require a clean install though.
Click to expand...
Click to collapse
Thank you for your advise, but I prefer the stock rom, btw I already fixed it too xD
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
try to flash stock boot.img and recovery.img
sonn3 said:
try to flash stock boot.img and recovery.img
Click to expand...
Click to collapse
Same issue. So how would we go about flashing properly?
Search for recovery.img and boot.img in stock rom and flash in fastboot mode.
mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
Did you select close avb 2.0 in twrp and factory reset?
mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
We would need further details on which device (region) which MIUI version (number, android, region) you were on when you attempted to install Magisk. Of course we assume here you had unlocked your bootloader first, otherwise any attempt to flash anything will result in bootloop.
Many have successfully rooted on Android 9 regardless of MIUI version.
Complication often comes with Chineses devices from what I read, Global not so much so if you are on Global device consider yourself lucky
Easiest root is probably to flash LR team TWRP If you can still access fastboot mode (voloume - + power) version 09.24 or 11.04 if you are on Android 9 or version 12.10 if you are on Android 10. Note that you probably have more chances of success being on Android 9.
And use the root feature from WITHIN that TWRP to install root on your device.
You have a complete guide of the steps to reproduce here:
Guide
I have tested on Android 9, EEA device, EEA rom MIUI 11.0.2.0 and it works without an issue if you follow the guide provided above.
If you still want to manually flash Magisk from any other recovery, make sure to use version 19.04 which seems to have the higher odds of success (update afterward from Manager).
Also as mentioned by @wang1chung do not forget to close avb 2.0.
Myself I also had RM Force encrypt option used (just in case) even if not mentionned in the thread.
But unlike what was suggested in those threads I did not wipe data.
That said since I do not want to have TWRP to stick for now, I actually want it to automatically be replaced by stock recovery all went fine for me, and Magisk is there.
And when I need TWRP for something I just flash it again and do my stuff.
Hope this helps.
Good luck!
Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?
allxdadev said:
Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?
Click to expand...
Click to collapse
Personally I used the hassle-free method pressing the button to root directly from within the LR-TWRP (09.24, or 11.04 on Android 9 MIUI), swiped, then pressed that other provided button to close AVB 2.0, swiped and it worked on first attempt.
Of course TWRP got replaced on first reboot by system recovery, but I dont care as I do not want it to stick on my device. I just flash it again when I need it.
Magisk stayed, updated it from Manager (well manager updated first to that new ugly theme.... yurk!), then Magisk updated, no problem.
Note that I am on EU Phone running EEA MIUI 11.0.2.0. You might get a different outcome with other devices/roms.
Side note, LR-TWRP 09.24 installs Magisk 19.04 which has been reported numerous time to work on most Android 9 MIUI regional versions. LR-TWRP 11.04 howevers installs Magisk 20.0 fyi.
Hope this helps,
Regards,
regarding the thread title, i had the same problem. right when i was about to retart everything all over from 0, i was glad i was able to just go into twrp and just unroot. rebooted and it started as if nothing hsppended. now i jjust gotta find which module made me bootloop.
try this n give us the result
So I've long been had PE (Pixel Experience) installed on my phone and I've never had any issues flashing recovery, not even in the CFW days. But I noticed there was an update to PE last month and decided I should update it. The instructions are clean, you must start fresh (format data, system, dalvik, etc..) so prior to attempting to install PE, first order of business is to get a newer recovery. Simple right? I tried flashing the twrp that was listed in the instrucitons, I tried Orange Fox, which worked only once but hasn't since. So if figured, ok, too many issues, let me start from scratch. I fastboot flashed my phone using the last Miui firmware I had on my phone. Didn't wan't the newer firmware getting in the way with whatever new locks they may have installed. Flashing to factory using fastboot went without a hitch. I first opted to save my data, but that failed at boot, so I did a flash-all.bat and that got me to a pristine factory from Miui 11 Android 9. Enabled USB Debug and Relaxed USB App upload secruity settings and now I should be able to boot into the bootloader and Flash any recovery right? No such luck. Flashed the latest and even a version prior of TWRP and Orange fox and they just don't boot. When I hold the Vol Up + Power it boots showing the Redmi logo and just when it's suppoed to show the splash screen of whatever recovery I'm trying, it simply reboots and I'm sure the miui os already restored the original factory so I try flashing again and no dice. I've flashed and tried to boot probably 50 times by now. Only once did I get a little ray of hope when I flashed Orange fox after doing a clean fastboot rom flash and I simply got 3 menu choices asking to boot to recovery, bootloader ,or system. I of course chose recovery and FAIL it just went black screen and rebooted to system! OK, so frustrated, I went and downloaded the latest firmware from Mi and for sure, whever it has that's preventing booting into recovery for sure will get erased and started from scratch, especially cuz I'm going from Miui11 Android 9 all the way up to Miui 12.5 Android 11 right? After re-enableing the developer setting and adjusting the settings and making sure my computer is authorized on the phone I rebooted to the bootloader, flashed Orange Fox and FAIL! still no joy. WTF?!? This is getting frustrating. What am I doing wrong? What can I do to try and fix this?
Tin_Man_0 said:
So I've long been had PE (Pixel Experience) installed on my phone and I've never had any issues flashing recovery, not even in the CFW days. But I noticed there was an update to PE last month and decided I should update it. The instructions are clean, you must start fresh (format data, system, dalvik, etc..) so prior to attempting to install PE, first order of business is to get a newer recovery. Simple right? I tried flashing the twrp that was listed in the instrucitons, I tried Orange Fox, which worked only once but hasn't since. So if figured, ok, too many issues, let me start from scratch. I fastboot flashed my phone using the last Miui firmware I had on my phone. Didn't wan't the newer firmware getting in the way with whatever new locks they may have installed. Flashing to factory using fastboot went without a hitch. I first opted to save my data, but that failed at boot, so I did a flash-all.bat and that got me to a pristine factory from Miui 11 Android 9. Enabled USB Debug and Relaxed USB App upload secruity settings and now I should be able to boot into the bootloader and Flash any recovery right? No such luck. Flashed the latest and even a version prior of TWRP and Orange fox and they just don't boot. When I hold the Vol Up + Power it boots showing the Redmi logo and just when it's suppoed to show the splash screen of whatever recovery I'm trying, it simply reboots and I'm sure the miui os already restored the original factory so I try flashing again and no dice. I've flashed and tried to boot probably 50 times by now. Only once did I get a little ray of hope when I flashed Orange fox after doing a clean fastboot rom flash and I simply got 3 menu choices asking to boot to recovery, bootloader ,or system. I of course chose recovery and FAIL it just went black screen and rebooted to system! OK, so frustrated, I went and downloaded the latest firmware from Mi and for sure, whever it has that's preventing booting into recovery for sure will get erased and started from scratch, especially cuz I'm going from Miui11 Android 9 all the way up to Miui 12.5 Android 11 right? After re-enableing the developer setting and adjusting the settings and making sure my computer is authorized on the phone I rebooted to the bootloader, flashed Orange Fox and FAIL! still no joy. WTF?!? This is getting frustrating. What am I doing wrong? What can I do to try and fix this?
Click to expand...
Click to collapse
OK, your one sentence text is a bit difficult to read but I'll try to explain the best I can (there might be errors).
You can split the custom recoveries into two types. CFW and non-CFW.
You can split the custom ROMs into two types. CFW and non-CFW.
CFW recoveries have to go hand in hand with CFW custom ROMs.
non-CFW recoveries have to go hand in hand with non-CFW custom ROMs.
What about stock MIUI? That depends on the custom recovery. The developer usually states which ROMs the recovery is designed for (if CFW or non-CFW; if stock MIUI 12.0.x or stock MIUI 12.5.x; etc). If you mix a CFW recovery with a non-CFW custom ROM you'll probably have issues.
If you install a compatible recovery for MIUI 12.5.x and simply let MIUI boot into system it erases the custom recovery, which means you have to install the custom recovery again and boot straight into it. That's why some recoveries have extras to prevent its erasure (you'll have to research this).
This video below should contain everything you need.
Compass.
Compass Linux said:
OK, your one sentence text is a bit difficult to read but I'll try to explain the best I can (there might be errors).
You can split the custom recoveries into two types. CFW and non-CFW.
You can split the custom ROMs into two types. CFW and non-CFW.
CFW recoveries have to go hand in hand with CFW custom ROMs.
non-CFW recoveries have to go hand in hand with non-CFW custom ROMs.
What about stock MIUI? That depends on the custom recovery. The developer usually states which ROMs the recovery is designed for (if CFW or non-CFW; if stock MIUI 12.0.x or stock MIUI 12.5.x; etc). If you mix a CFW recovery with a non-CFW custom ROM you'll probably have issues.
If you install a compatible recovery for MIUI 12.5.x and simply let MIUI boot into system it erases the custom recovery, which means you have to install the custom recovery again and boot straight into it. That's why some recoveries have extras to prevent its erasure (you'll have to research this).
This video below should contain everything you need.
Compass.
Click to expand...
Click to collapse
Way ahead of you my friend. I got off of CFW roms several versions ago. BUT I think I found what the problem may have been. The official TWRP gives instructions to disable AVB via fastboot flashing vbmeta with the following command. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. I'm guessing the custom TWRP or Orange fox are supposed to have that command built into it or something cuz they didn't mention it in their instructions to flash the roms. Unfortuately I upgraded to MIUI 12.5 Android 11 and Xaiomi appears to have added some new locks because I'm reading reports from other users that attempting to flash custom recovery roms on MIUI 12.5 is resulting in bootloops. Sigh, just my luck. Stuck until further notice. BTW, once upgraded to 12.5 there's no flashing previous versions either. Exactly what I was originally trying to avoid, but I needed a working phone, so I'm on stock again for the time being.
Tin_Man_0 said:
Way ahead of you my friend. I got off of CFW roms several versions ago. BUT I think I found what the problem may have been. The official TWRP gives instructions to disable AVB via fastboot flashing vbmeta with the following command. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. I'm guessing the custom TWRP or Orange fox are supposed to have that command built into it or something cuz they didn't mention it in their instructions to flash the roms. Unfortuately I upgraded to MIUI 12.5 Android 11 and Xaiomi appears to have added some new locks because I'm reading reports from other users that attempting to flash custom recovery roms on MIUI 12.5 is resulting in bootloops. Sigh, just my luck. Stuck until further notice. BTW, once upgraded to 12.5 there's no flashing previous versions either. Exactly what I was originally trying to avoid, but I needed a working phone, so I'm on stock again for the time being.
Click to expand...
Click to collapse
You might like this MIUI 12.5.x mod:
Updated version of the mod (11/08/2021): MOD EDIT: Link Removed
Downgrade MIUI 12.5.x to MIUI 12.0.x via TWRP:
Good luck!
Compass.
Compass Linux said:
You might like this MIUI 12.5.x mod:
Updated version of the mod (11/08/2021): MOD EDIT: Link Removed
Downgrade MIUI 12.5.x to MIUI 12.0.x via TWRP:
Good luck!
Compass.
Click to expand...
Click to collapse
Thanks! I'll give these a try, but what I was looking for and don't see where exactly to download is that batch file and version of twrp that was show on the video. They launched a batch file and adb waited for the phone and then off it went. I assume that these some extra little steps added to the batch file besides the "fastboot flash recovery recovery.img" routine? Also, the moded ROM looks intresting from the pling page. Can if just copy the "flash_all.bat" from Miui's fastboot firmware installer and drop it in santosh's moded firmware files list? That would be just way to convenient, but keeping my fingers crossed lol.
Tin_Man_0 said:
Thanks! I'll give these a try, but what I was looking for and don't see where exactly to download is that batch file and version of twrp that was show on the video. They launched a batch file and adb waited for the phone and then off it went. I assume that these some extra little steps added to the batch file besides the "fastboot flash recovery recovery.img" routine? Also, the moded ROM looks intresting from the pling page. Can if just copy the "flash_all.bat" from Miui's fastboot firmware installer and drop it in santosh's moded firmware files list? That would be just way to convenient, but keeping my fingers crossed lol.
Click to expand...
Click to collapse
On MIUI 12 Android 10: MOD EDIT: Link Removed
On MIUI 12.5 Android 11: MOD EDIT: Link Removed
The batch and twrp are inside each fastboot zip.
Yeah, don't mix flash_all.bat from a stock MIUI with any custom ROM.
Compass.
Yes! You are the man! Finally. It took every try too ciz I had even found a BRP Twrp, just one version prior to the link you provied Ver 2.7 and that still failed. Tried it a couple dozen which ways too. But this last one finally did the trick. I noticed they went and hid all the files and left only the batch files to launch. I'm guessing people were trying to use the files the wrong way lol. So one last question, cuz I got TWRP running now on my phone and I'm wondering if it'll still be there if I reboot it? I assume this twrp automatically kills the MIUI recovery restore from attempting to take back the recovery?
Tin_Man_0 said:
Yes! You are the man! Finally. It took every try too ciz I had even found a BRP Twrp, just one version prior to the link you provied Ver 2.7 and that still failed. Tried it a couple dozen which ways too. But this last one finally did the trick. I noticed they went and hid all the files and left only the batch files to launch. I'm guessing people were trying to use the files the wrong way lol. So one last question, cuz I got TWRP running now on my phone and I'm wondering if it'll still be there if I reboot it? I assume this twrp automatically kills the MIUI recovery restore from attempting to take back the recovery?
Click to expand...
Click to collapse
I haven't tested either of those recoveries myself but both should survive a MIUI reboot (I've downloaded both recoveries and looking at the files inside they should stay).
The first video I posted covers TWRP for both MIUI 12.0.x and MIUI 12.5.x.
User Alice! got TWRP to be permanent (she's on stock MIUI): https://forum.xda-developers.com/t/cant-flash-custom-recovery.4318347/
Compass.
Flashable firmware / modem / baseband / RIL only (no full ROM).
Basically, it's a set of firmware/modem/baseband/RIL extracted from the OxygenOS Full ROM update payload and packed into a custom recovery flashable ZIP. Useful for users of a custom ROM, since the firmware/modem/baseband/RIL is never updated on most custom ROMs and thus becomes outdated. Those who use OxygenOS don't need this, since the firmware/modem/baseband/RIL is also updated with OTAs.
Important
If you have a OnePlus Nord (avicii) AC01AA, AC01BA or AC01DA and a custom ROM installed, feel free to proceed. However, I recommend making a backup before and get the unbrick tool from here, just in case.
Flash it with any (custom) recovery. It's not necessary to delete, wipe or format anything before or after installation.
Note: Packages are not signed.
Check the baseband version with: Settings → About phone → Android version → Baseband version
For OnePlus Nord - avicii - Android 12 based ROMs:
VersionModelDownload link11 F.20 AC01AAGlobalOnePlus_Nord_11-F-20-AC01AA_global_firmware.zip11 F.20 AC01BAEuropeOnePlus_Nord_11-F-20-AC01BA_europe_firmware.zip11 F.20 AC01DAIndiaOnePlus_Nord_11-F-20-AC01DA_india_firmware.zip
Baseband version after update: Q_V1_P14 or: MPSS.HI.2.5-01081-SAIPAN_GEN_PACK-1.7761.62_VENDOR
For OnePlus Nord - avicii - Android 10 and 11 based ROMs:
VersionModelDownload link11.1.10.10 AC01AAGlobalOnePlus_Nord_11-1-10-10-AC01AA_global_firmware.zip11.1.11.11 AC01BAEuropeOnePlus_Nord_11-1-11-11-AC01BA_europe_firmware.zip11.1.10.10 AC01DAIndiaOnePlus_Nord_11-1-10-10-AC01DA_india_firmware.zip
Baseband version after update: MPSS.HI.2.0.c9-00023-SAIPAN_GEN_PACK-1.422164.2.446371.2
Last Updated: 2023-06-04
Reserved 1
Reserved 2
Reserved 3
Great work! Thanks for the contribution.
can u plz update latest beta 2 recovery & boot img, got stuck on latest oos12 beta when tried to flash custom recovery as no custom recovery for oos12 beta right now, thanks in advance
Thank you for your work!
I guess this maybe does not work with the LineageOS recovery? I tried to sideload using apply from ADB in the LineageOS recovery, but I keep getting the following error
"E3004: This package is for "OnePlus Nord" devices; this is a "".
hermesjconrad said:
Thank you for your work!
I guess this maybe does not work with the LineageOS recovery? I tried to sideload using apply from ADB in the LineageOS recovery, but I keep getting the following error
"E3004: This package is for "OnePlus Nord" devices; this is a "".
Click to expand...
Click to collapse
I have included a safeguard so that these files cannot be accidentally installed on a device other than the Nord. But for some reason the LOS developers decided to name the device differently in LOS 17 recovery. In LOS 18 (or alternatively Orange Fox) recovery everything should work fine.
So I have removed this protection for now until an official LOS 18 or 19 is released. Download the appropriate package again and try to flash it again, it should now be able to be flashed with adb sideload.
Worked like a charm with the removed control, thank you very much Doc Sniper!
Straying slighty off-topic, would OrangeFox be the recovery that you'd recommend instead of LOS 17.1 default? Or rather TWRP?
vikd007 said:
can u plz update latest beta 2 recovery & boot img, got stuck on latest oos12 beta when tried to flash custom recovery as no custom recovery for oos12 beta right now, thanks in advance
Click to expand...
Click to collapse
Sorry, but I don't quite understand the problem? These packages update the firmware if you have a custom ROM installed. But since the OxygenOS Open Betas are official packages, they include the firmware anyway and these packages here are kind of useless for you.
But even if the packages were of use to you, neither the boot nor the recovery image is included.
I can offer to extract the two images so you can install them with fastboot flash, please send me the download link to the corresponding ROM and I'll see what I can do.
hermesjconrad said:
Worked like a charm with the removed control, thank you very much Doc Sniper!
Straying slighty off-topic, would OrangeFox be the recovery that you'd recommend instead of LOS 17.1 default? Or rather TWRP?
Click to expand...
Click to collapse
LOS recovery is totally OK if you only want to perform updates. But if you want to make backups and restore or want to get to the data partition, then it is no longer sufficient. Unfortunately there is still no official TWRP, so I use Orange Fox and it works great with the unofficial LOS 18, but you have to look in the Orange Fox thread there is a link to a newer version than the one in the opening post (see post 81 on page 5).
sniperle said:
Sorry, but I don't quite understand the problem? These packages update the firmware if you have a custom ROM installed. But since the OxygenOS Open Betas are official packages, they include the firmware anyway and these packages here are kind of useless for you.
But even if the packages were of use to you, neither the boot nor the recovery image is included.
I can offer to extract the two images so you can install them with fastboot flash, please send me the download link to the corresponding ROM and I'll see what I can do.
Click to expand...
Click to collapse
thanks for prompt revert bro, i was on stock latest beta was trying to flash custom recovery but no custom recovery support oos 12 beta for so stuck on bootloop so asked for help if i can get latest boot and recovery img, but somehow a trick worked and finally on custom rom... thanks bro and appreciate ur work
vikd007 said:
thanks for prompt revert bro, i was on stock latest beta was trying to flash custom recovery but no custom recovery support oos 12 beta for so stuck on bootloop so asked for help if i can get latest boot and recovery img, but somehow a trick worked and finally on custom rom... thanks bro and appreciate ur work
Click to expand...
Click to collapse
Good to hear your phone is working again.
If you ever have a bootloop again because your recovery doesn't start, you can also start a recovery from the computer via fastboot.
In short: Download the recovery image to your computer. Then connect the phone with a usb-cable. Then start the phone in fastboot mode. Then upload and start the recovery from the computer with "fastboot boot name_of_recovery_image.img".
Doc Sniper said:
Good to hear your phone is working again.
If you ever have a bootloop again because your recovery doesn't start, you can also start a recovery from the computer via fastboot.
In short: Download the recovery image to your computer. Then connect the phone with a usb-cable. Then start the phone in fastboot mode. Then upload and start the recovery from the computer with "fastboot boot name_of_recovery_image.img".
Click to expand...
Click to collapse
problem was there is no recovery for oos beta 12 as of now and no latest boot image
Managed to bork my phone by trying to upgrade magisk, managed to unbork by changing boot slots with fastboot, really neat.
Wanted to say thank you for providing the latest update file. Didn't need it in particular, but cool to have it and know it is available!
vikd007 said:
thanks for prompt revert bro, i was on stock latest beta was trying to flash custom recovery but no custom recovery support oos 12 beta for so stuck on bootloop so asked for help if i can get latest boot and recovery img, but somehow a trick worked and finally on custom rom... thanks bro and appreciate ur work
Click to expand...
Click to collapse
I faced the same issue.. want to move on to a custom ROM but have 2 questions:
1. Does the phone loose Widevine L1 upon bootloader unlock on OOS12? I know i have to stop the phone from booting up after bootloader unlock and directly install the custom ROM, but i got stuck due to the recovery problem.
2. Does the custom ROM work good after this?
Hi,
Thank you for your work.
Unfortunately, update with LOS recovery doesn't work (LOS 19.1 recovery).
It says "Signature verification failed, error 21".
I have Magisk installed if it means anything in this case.
blorkraider said:
Unfortunately, update with LOS recovery doesn't work (LOS 19.1 recovery).
It says "Signature verification failed, error 21".
Click to expand...
Click to collapse
The ZIP files are not signed hence the message. But as far as I know, LOS-Recovery can also flash unsigned ZIPs. When the message appears, you can switch to yes with the volume buttons and then confirm with the power button. Then the ZIP should be installed.
Now that OOS12 is available for all regions can you post the modem files from those? It seems 12 unlocks 5G in some countries.
mythos_ said:
Now that OOS12 is available for all regions can you post the modem files from those? It seems 12 unlocks 5G in some countries.
Click to expand...
Click to collapse
According to the official Oneplus site, version 11 is still the current release version. Can you send me a download link to the release version of OOS 12? Thanks.