Related
•••••• Qualcomm Moto E (4th Gen) Perry ••••••
Factory Firmware & Flashing/Restoration Guide
MetroPCS / T-Mobile Moto E4 (XT1765)
OVERVIEW:
This guide provides factory firmware for both the MetroPCS and T-Mobile branded variants of the Moto E4 Perry (xt1765). While these two packages appear to be similar and multi-compatible, I do not own the xt1765 and cannot confirm this. So, to be safe, use only the firmware package for your branded carrier. This guide can be used to repair a device which is buggy, unstable, or stuck in a boot loop. Likewise, device owners wishing to restore their device to an unmodified, stock factory state will also find this guide beneficial. Installing this firmware will remove any custom mods from your device, such as root binaries, BusyBox binaries, Xposed framework, etc. Also, force encryption and verified boot (dm-verity/avb) will be enabled. If you have TWRP custom recovery installed, it will be replaced by the stock recovery image.
DISCLAIMER:
You are using this guide and flashing firmware to your device solely at your own risk. While these firmwares have been tested and confirmed to work on their respective variants, by proceeding further, you are absolving me of any liability or responsibility in the event you brick your device or otherwise render it inoperable. Follow the simple instructions carefully and things should go smoothly.
SPECIFICATIONS:
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
•MetroPCS Moto E4 (xt1765) Perry
•Android Version: 7.1.1 Nougat
•Build No. NCQS26.69-64-3
•System Version: 26.261.9.perry_metropcs.en.US
•Radio Version: M8917TMO_18.08.04.18R
•Security Patch Level: March 1, 2018
•Kernel Version: Linux 3.18.31-perf
•Build Date: March 16, 2018
•Firmware Package Size: 1.36 GB
•Download Link: https://drive.google.com/file/d/17sJS8VpxSAHupqiqJQQb4wa1jHIP61uT/view?usp=drivesdk
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
•T-Mobile Moto E4 (xt1765) Perry
•Android Version: 7.1.1 Nougat
•Build No. NCQS26.69-64-6
•System Version: 26.271.7.perry_tmo.tmo.en.US
•Radio Version: M8917TMO_18.08.04.18.01R
•Security Patch Level: May 1, 2018
•Kernel Version: Linux 3.18.31-perf
•Build Date: May 2, 2018
•Firmware Package Size: 1.33 GB
•Download Link: https://drive.google.com/file/d/1C21fgdBVn6hhPtAo5yult-PdB6DSr4HS/view?usp=drivesdk
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
REQUIREMENTS:
This guide assumes that you have the latest version of the Minimal ADB & Fastboot utilities installed on your PC or laptop. If you do not, you can download the latest version, v1.4.3, from this MediaFire link: http://www.mediafire.com/file/ccnnv843a20tqbn/minimal_adb_fastboot_v1.4.3.zip It is also a good idea to have at least a rudimentary understanding of fastboot command line execution. There are some excellent guides here on XDA which outline the subjects of fastboot mode & fastboot commands.
In addition, to ensure that up-to-date USB device drivers are installed on your PC, download & install the latest Motorola Device Manager. You can get the latest version directly from this Motorola support link: https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222
NOTE:
Because these are factory firmware packages, in theory, xt1765 owners should be able to flash these packages, using the below instructions, to devices with a locked bootloader. Please note, however, that these firmwares were leaked by the manufacturer and may or may not be digitally signed by the OEM. In sum, I cannot confirm whether these firmwares will flash to a locked bootloader device. I can only confirm that the firmware will install normally on a device with an unlocked bootloader. As confirmation becomes available from other members in this regard, I will add the info to this thread.
On a second note, flashing this factory firmware does not re-lock an already unlocked bootloader. Also, contrary to popular misbelief, re-locking your bootloader IS NOT required in order for your device to be able to install OTA update packages. To enable your device to install OTA updates, you need only install the firmware package for your variant using the below instructions.
WARNING: The below instructions include a command for wiping your /userdata partition (fastboot erase userdata) which will effectively wipe all of your saved files, photos, videos, app data and other media. This is recommended for a clean install of the firmware, and to ensure optimal results. However, if you are stuck in a boot loop, for example, and have important files saved to internal storage that you want to try and salvage, simply skip over the "fastboot erase userdata" command and give it a try.
INSTRUCTIONS:
• 1. Download the firmware package for your branded carrier on your PC or laptop. Extract the contents of the package to your ADB/Fastboot directory;
• 2. Boot your device into fastboot mode and connect your device to your PC with the OEM or a quality equivalent micro USB to USB sync cable;
• 3. Open a command window in the path of your ADB/Fastboot directory and execute:
fastboot devices
If your device and PC are properly connected, the command window will return an alphanumeric value synonymous of your device serial number;
• 4. Once a proper connection has been established, execute the following commands, preferably in this order:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
Done. Now execute:
fastboot reboot
Upon reboot, your device should be restored to unmodified stock condition, and your device will be capable of installing pending or future OTA update packages.
Thanks for posting this! Looks very comprehensive and nOObproof.... I'm going to try this out in the next few days and I will report back if I had any trouble following the instructions and let your know if I feel anything needs to be clarified. I don't foresee having any problems with this though. I appreciate you and your hard work to put this together
AesopRock127 said:
Thanks for posting this! Looks very comprehensive and nOObproof.... I'm going to try this out in the next few days and I will report back if I had any trouble following the instructions and let your know if I feel anything needs to be clarified. I don't foresee having any problems with this though. I appreciate you and your hard work to put this together
Click to expand...
Click to collapse
No problem. I've been reading a lot of posts of members needing more up-to-date xt1765 stock firmware, so I hope it helps some members. These are the same instructions and structural format that I use on all of my Moto/Lenovo firmware threads. The order of the command lines are set out exactly the same as those used in certified Motorola/Lenovo service centers. If you follow the instructions to the letter, there is no doubt that you'll have your device fully restored to stock factory condition.
When I have the time to do so, I'll use these firmwares with my Android Kitchen to cook up TWRP flashable stock ROMs for the MetroPCS & T-Mobile xt1765 models.
MotoJunkie01 said:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
My question is if i want to keep twrp as my recovery is it as simple as not running the command fastboot flash recovery recovery.img?
AesopRock127 said:
My question is if i want to keep twrp as my recovery is it as simple as not running the command fastboot flash recovery recovery.img?
Click to expand...
Click to collapse
Yes. It is that simple. Just be advised that an OTA will not install normally unless stock recovery is in place. The OTA installation script runs checksums for stock recovery.
The best policy is to flash the firmware in full, install any pending OTAs while running unmodified stock, then reinstall TWRP once you're up to date on the latest firmware build.
MotoJunkie01 said:
Yes. It is that simple. Just be advised that an OTA will not install normally unless stock recovery is in place. The OTA installation script runs checksums for stock recovery.
The best policy is to flash the firmware in full, install any pending OTAs while running unmodified stock, then reinstall TWRP once you're up to date on the latest firmware build.
Click to expand...
Click to collapse
Shiiiiiit I didn't think about that I have an update I'm going to try to do it if it doesn't work guess I'll redo the full process all over again..... By the way I pmd you
EDIT: 69-64-6 updated no problem And immediately offered me 69-64-9 so maybe these updates aren't large enough to worry about twrp instead of stock recovery? Only time will tell I guess
Sent from my Motorola XT1765 using XDA Labs
AesopRock127 said:
Shiiiiiit I didn't think about that I have an update I'm going to try to do it if it doesn't work guess I'll redo the full process all over again..... By the way I pmd you
EDIT: 69-64-6 updated no problem And immediately offered me 69-64-9 so maybe these updates aren't large enough to worry about twrp instead of stock recovery? Only time will tell I guess
Click to expand...
Click to collapse
To simplify things, just keep installing OTAs until you are on the current build. Then, reinstall TWRP. You shouldn't have to redo the whole thing as long as you haven't mounted system as r/w in TWRP. And as long as you haven't flashed Magisk or SuperSU for root. Just reboot into fastboot and flash the stock recovery and OTAs should be fine.
so i know im a pain in the ass but i followed this guide with no issues and updated fully before installing twrp and root and then couldnt install xposed and ran into a bootloop so decided to go nuclear and start over. My only issue now is after fully following this guide again my OTA updates are failing in stock recovery and when i reboot i get tons of tmobile and moto app FC issues and it says im fully updated even though i started on 69-64-3 and it failed in stock recovery it still says im on 69-64-6 and ive been on 69-64-9 before so not only do i know im not fully updatedd but these FC are driving me nuts. Trying again but does anyone have any clues what could be causing my issues? im having a lot of problems with noverity flashing right and getting the newest twrp to flash instead of only temp boot as well and i feel these issues are all cnnected somehow. I might go back to RR if possible because i was able to get my phone the way i wanted on there for the most part im not sure why stock is giving me such issues? Unfrotunately i cant provide any logs or anything because i am retrying this guide again and see how it goes and didnt think until after the fact to post this
AesopRock127 said:
so i know im a pain in the ass but i followed this guide with no issues and updated fully before installing twrp and root and then couldnt install xposed and ran into a bootloop so decided to go nuclear and start over. My only issue now is after fully following this guide again my OTA updates are failing in stock recovery and when i reboot i get tons of tmobile and moto app FC issues and it says im fully updated even though i started on 69-64-3 and it failed in stock recovery it still says im on 69-64-6 and ive been on 69-64-9 before so not only do i know im not fully updatedd but these FC are driving me nuts. Trying again but does anyone have any clues what could be causing my issues? im having a lot of problems with noverity flashing right and getting the newest twrp to flash instead of only temp boot as well and i feel these issues are all cnnected somehow. I might go back to RR if possible because i was able to get my phone the way i wanted on there for the most part im not sure why stock is giving me such issues? Unfrotunately i cant provide any logs or anything because i am retrying this guide again and see how it goes and didnt think until after the fact to post this
Click to expand...
Click to collapse
Follow the instructions exactly, but avoid gpt.bin and bootloader.img. Those will fail as they are supposed to, so no need in trying them. Otherwise you should be fully stock on reboot and your device should install OTAs normally.
If that particular problem persists, file corruption within the firmware package could be the culprit. Try downloading the firmware again (delete the other from your PC) and start over from scratch.
MotoJunkie01 said:
Follow the instructions exactly, but avoid gpt.bin and bootloader.img. Those will fail as they are supposed to, so no need in trying them. Otherwise you should be fully stock on reboot and your device should install OTAs normally.
If that particular problem persists, file corruption within the firmware package could be the culprit. Try downloading the firmware again (delete the other from your PC) and start over from scratch.
Click to expand...
Click to collapse
Ok thanks. I will try redownloading if it persists but is there any log or anything that would help out in identifying the problem if it still persists after a redownloading of the firmware? It's annoying that stock recovery says error! With no code to help identify the issue
AesopRock127 said:
Ok thanks. I will try redownloading if it persists but is there any log or anything that would help out in identifying the problem if it still persists after a redownloading of the firmware? It's annoying that stock recovery says error! With no code to help identify the issue
Click to expand...
Click to collapse
When stock recovery says ERROR during installation of an OTA, the problem is with the checksums. In other words, the OTA installer is telling stock recovery that you are not running an unmodified stock setup. You can get an error like that from just mounting /system or /oem as r/w. The installer checks your /boot, /recovery, /system and /oem partitions to make sure they are untouched, unmodified stock.
Also, @AesopRock127, there is a quicker and simpler method to install stock firmware to a Moto/Lenovo device called RSD Lite. You can Google for the basic instructions.
Here's a link to RSD Lite v6.2.4: https://drive.google.com/file/d/1MwZPdifKVpR4ZTsE3SSNAFBNr6KU29wY/view?usp=drivesdk
MotoJunkie01 said:
Also, @AesopRock127, there is a quicker and simpler method to install stock firmware to a Moto/Lenovo device called RSD Lite. You can Google for the basic instructions.
Here's a link to RSD Lite v6.2.4: https://drive.google.com/file/d/1MwZPdifKVpR4ZTsE3SSNAFBNr6KU29wY/view?usp=drivesdk
Click to expand...
Click to collapse
Okay so I redid this and the updates are sticking like you said I must have changed something and made it non-stock.... So I do not need the RSD Lite as of yet but I did download it. Looking into it it seems that I may use it to root my device when I get to that point? For now I'm just setting everything up the way I like it and fully intalling stock updates before I get into TWRP and rooting. The goal is a up to date stock, rooted, debloated, and running Xposed and gravitybox. Last time everything went smoothly until I hit xposed. I think it's due to my crappy understanding of selinux permissions, encryption and dm verity.... The best thing about struggling to install stuff like this is it gives you an opportunity to learn. In the past I've been able to follow guides and everything worked as stated so I had no need to get technical and delve into some of the things I've needed to on my xt1765. Thank God for XDA and helpful people like @MotoJunkie01 or I would have hit this phone with a Sledge hammer or chop it in half with a chop saw like I did with the Samsung j3 ?
AesopRock127 said:
Okay so I redid this and the updates are sticking like you said I must have changed something and made it non-stock.... So I do not need the RSD Lite as of yet but I did download it. Looking into it it seems that I may use it to root my device when I get to that point? For now I'm just setting everything up the way I like it and fully intalling stock updates before I get into TWRP and rooting. The goal is a up to date stock, rooted, debloated, and running Xposed and gravitybox. Last time everything went smoothly until I hit xposed. I think it's due to my crappy understanding of selinux permissions, encryption and dm verity.... The best thing about struggling to install stuff like this is it gives you an opportunity to learn. In the past I've been able to follow guides and everything worked as stated so I had no need to get technical and delve into some of the things I've needed to on my xt1765. Thank God for XDA and helpful people like @MotoJunkie01 or I would have hit this phone with a Sledge hammer or chop it in half with a chop saw like I did with the Samsung j3 ?
Click to expand...
Click to collapse
That's good news. I intend on making a TWRP flashable stock ROM for the xt1765 in the very near future. Once you are on the latest stock build, if you could make a TWRP backup of your system image and boot image and upload them, I could use the images to cook up an up-to-date stock ROM for the xt1765.
MotoJunkie01 said:
That's good news. I intend on making a TWRP flashable stock ROM for the xt1765 in the very near future. Once you are on the latest stock build, if you could make a TWRP backup of your system image and boot image and upload them, I could use the images to cook up an up-to-date stock ROM for the xt1765.
Click to expand...
Click to collapse
Absolutely. will do this ASAP. Seems best if I do nothing except boot into TWRP and make the backup? Or can I flash it and it will still work? Basically is the stock recovery needed or can I flash TWRP before I make the backup
so system and boot only or system, system image, and boot? making one now with both systems and one with just normal system since im not sure which you need and dont want to give you to much **** to sift through. also does data need to be decrypted for this to be helpful to you? sorry dont know much about it but am willing to help lol
AesopRock127 said:
Absolutely. will do this ASAP. Seems best if I do nothing except boot into TWRP and make the backup? Or can I flash it and it will still work? Basically is the stock recovery needed or can I flash TWRP before I make the backup
so system and boot only or system, system image, and boot? making one now with both systems and one with just normal system since im not sure which you need and dont want to give you to much **** to sift through. also does data need to be decrypted for this to be helpful to you? sorry dont know much about it but am willing to help lol
Click to expand...
Click to collapse
System image and boot backup with TWRP. Encryption of data isn't relevant to the backups. Whether you boot into TWRP or flash TWRP ....either will work
@MotoJunkie01 Nanodroid backup of encrypted fully uptodate stock system and boot.img only https://ufile.io/b0x6q
uploading the one with the system image too
MotoJunkie01 said:
Follow the instructions exactly, but avoid gpt.bin and bootloader.img. Those will fail as they are supposed to, so no need in trying them. Otherwise you should be fully stock on reboot and your device should install OTAs normally.
If that particular problem persists, file corruption within the firmware package could be the culprit. Try downloading the firmware again (delete the other from your PC) and start over from scratch.
Click to expand...
Click to collapse
Also verify checksums (MD5, SHA-1, etc) when offered. Fastest way to validate large file integrity. As a matter of practice I never flash critical partitions sans checksum validation.
Davey126 said:
Also verify checksums (MD5, SHA-1, etc) when offered. Fastest way to validate large file integrity. As a matter of practice I never flash critical partitions sans checksum validation.
Click to expand...
Click to collapse
Excellent point. A corrupt flash to a critical partition can equal lights out -- the proverbial hard brick.
Hi all, I've asked this question here ( https://forum.xda-developers.com/9-lite/help/how-update-project-treble-gsi-image-t3851002 ) also but am hoping this forum is more specific to my needs. I'll repeat the question here perhaps i'll have better luck with an answer !
there's a lot about installing gsi images on various phones that support project treble but i cannot find anything about how you update them. I installed OmniRom beta3, via fastboot, on my H9L and 3 days later they put out an update. The rom works fine and i set it up to my preference with magisk and it even shows up as Play certified, so all is good. However, with the update I prefer not to go through the whole magisk uninstall/install again. Anyone here knows how you would update an existing gsi images ? If I use fastboot to load the new update wouldn't that erase everything again, as stated on the openkirin.net installation instructions here ( https://openkirin.net/user_guide/openkirin-rom-installation-instructions/ ) ? or could i just fastboot the new beta3.1 over beta3 and just not do a factory reset as recommended ?
If a factory reset is essential everytime then this basically means we have to rebuild everything everytime there is an update ! I hope not.
Weird everyone writes about installation and no one thinks about updates ?
xzyk said:
Hi all, I've asked this question here ( https://forum.xda-developers.com/9-lite/help/how-update-project-treble-gsi-image-t3851002 ) also but am hoping this forum is more specific to my needs. I'll repeat the question here perhaps i'll have better luck with an answer !
there's a lot about installing gsi images on various phones that support project treble but i cannot find anything about how you update them. I installed OmniRom beta3, via fastboot, on my H9L and 3 days later they put out an update. The rom works fine and i set it up to my preference with magisk and it even shows up as Play certified, so all is good. However, with the update I prefer not to go through the whole magisk uninstall/install again. Anyone here knows how you would update an existing gsi images ? If I use fastboot to load the new update wouldn't that erase everything again, as stated on the openkirin.net installation instructions here ( https://openkirin.net/user_guide/openkirin-rom-installation-instructions/ ) ? or could i just fastboot the new beta3.1 over beta3 and just not do a factory reset as recommended ?
If a factory reset is essential everytime then this basically means we have to rebuild everything everytime there is an update ! I hope not.
Weird everyone writes about installation and no one thinks about updates ?
Click to expand...
Click to collapse
Just reboot to recovery flash update wipe cache and dalvik if u want.reboot
marcukial said:
Just reboot to recovery flash update wipe cache and dalvik if u want.reboot
Click to expand...
Click to collapse
How do you flash .img image through factory recovery ? If you read the openkirin instructions their gsi images are all in .img format and supported only when flashed through factory recovery. TWRP recovery is not an option for me as this phone is not well supported through it. Thanks anyway.
xzyk said:
How do you flash .img image through factory recovery ? If you read the openkirin instructions their gsi images are all in .img format and supported only when flashed through factory recovery. TWRP recovery is not an option for me as this phone is not well supported through it. Thanks anyway.
Click to expand...
Click to collapse
Just do the same thing you did to flash the GSI in fastboot.
Code:
fastboot flash system system.img
You don't need to do any wipes, but it's a good idea to wipe cache from the stock recovery after updating.
Hi,
i was looking for the same question to update the gsi files.
But how can I update the other files that Huawei provides, is this necessary with Trebe or do i need only update the system.img?
I tried this Tutorial 2, but there is everytime a factory reset.
https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286
regards
bacardi
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.
Hi everyone (pardon my English)
I have a Redmi Note 8 Global, and I am willing to install Custom ROM's on it.
I have read and watched several info about this subject, but there are some aspects I am not so clear about it.
I've never done it before, so first I need to dissipate some doubts. I'll appreciate your guidance.
My phone has the bootloader unlocked, and I have successful flashed it with MIUI Official fastboot ROMs three times with Mi Flash. First time with 12.0.6.0, months later with 12.5.1.0 and last time with 11.0.12.0 (and at present I'am still on 11.0.12.0).
Here there are my concerns and doubts:
- Decryption: Is it beneficial ? Mandatory ? Reversible ? What do you recommends ?
- Rooting: Is it beneficial ? Mandatory ? Reversible ? What do you recommends ?
- Is difficult to me to determine which Recovery to choose: TWRP, or Orange Fox ?
- Which Custom ROM for starting, based on Smoothness, Battery life, and Full functionalities: Pixel Experience 12, or Arrow OS 12 ?
- Can I install any Custom ROM no matter which one I have installed at the time ? For example: Going from Official MIUI 11.0.12.0 to Custom Pixel Experinece 12 ?
- Which are the real probabilities of soft or hard brick to happen during the process, and how to avoid it ?
- Is case of the worst scenario of soft or hard brick, can that be fixable ?
- Any direction to a concise detailed guide starting from the installation of the Custom Recovery to the Custom ROM flashing ?
- Is this hole Custom ROM flashing process completely reversible to the original factory state of the phone, if I want it someday ?
Thank you a lot in advanced, and pardon these so many questions. I really want it but don't want to messing up.
1. It is not beneficial, not mandatory, reversible, don't recommend
2. It's completely upto you
3. Go for OrangeFox
4. Pixel Experience 12. Using this rom as my daily driver. Super smooth
5. Yes you can do it anytime you wish.
6. Soft brick : It's like the phone is trying to boot but failing (somewhat like bootloop. Or sometimes if you shutdown your phone while it is flashing a rom then the software will be corrupted and you will see a message "Your system has been destroyed" this means the phone has been soft bricked and you can fix it just by flashing the MIUI rom using the MiFlash tool.
Hard brick: Your are fu***d up man. Your phone is now a piece of brick. To avoid this please make sure to check whether you are flashing the rom which is built for your phone. Like you have a ginkgo device (Codename for Redmi Note 8) but you flashed the rom built for curtana (Code name for Redmi Note 9) then your phone will be hardbricked and you can never ever use that motherboard
7. Like I said you can always fix a soft bricked phone but never a hard bricked one
8. You can always search youtube. As you have seen the Pixel experience just go to site https://wiki.pixelexperience.org/devices/ginkgo/install/
This guide is only for flashing pixel experience in ginkgo device
9. You can go back to MIUI anytime and again comeback to custom rom anytime you want
Evil_Hunter said:
1. It is not beneficial, not mandatory, reversible, don't recommend
2. It's completely upto you
3. Go for OrangeFox
4. Pixel Experience 12. Using this rom as my daily driver. Super smooth
5. Yes you can do it anytime you wish.
6. Soft brick : It's like the phone is trying to boot but failing (somewhat like bootloop. Or sometimes if you shutdown your phone while it is flashing a rom then the software will be corrupted and you will see a message "Your system has been destroyed" this means the phone has been soft bricked and you can fix it just by flashing the MIUI rom using the MiFlash tool.
Hard brick: Your are fu***d up man. Your phone is now a piece of brick. To avoid this please make sure to check whether you are flashing the rom which is built for your phone. Like you have a ginkgo device (Codename for Redmi Note 8) but you flashed the rom built for curtana (Code name for Redmi Note 9) then your phone will be hardbricked and you can never ever use that motherboard
7. Like I said you can always fix a soft bricked phone but never a hard bricked one
8. You can always search youtube. As you have seen the Pixel experience just go to site https://wiki.pixelexperience.org/devices/ginkgo/install/
This guide is only for flashing pixel experience in ginkgo device
9. You can go back to MIUI anytime and again comeback to custom rom anytime you want
Click to expand...
Click to collapse
Well, I don't know how to thank you enough. So, simply: THANKS VERY MUCH. That was a perfect and detailed answer. Thanks for your time and effort.
Just to be more precise about Questions 1 and 2: Do custom ROMs will work just fine on encrypted and non rooted phones?, I'm asking because i've seen some tutorials with decryption as a part of the process. I am intrigue and I wonder what are the Pros and Cons of decryption?
And with Question 6: So it is a fact that Soft brick is 100% fixable; and Hard brick only happens if I flash a Custom ROM of another phone model. So Hard brick will never happen as long as I always use the appropriate Custom ROM, right? Or there is more there?
Thanks a lot again.
lhn53 said:
Well, I don't know how to thank you enough. So, simply: THANKS VERY MUCH. That was a perfect and detailed answer. Thanks for your time and effort.
Just to be more precise about Questions 1 and 2: Do custom ROMs will work just fine on encrypted and non rooted phones?, I'm asking because i've seen some tutorials with decryption as a part of the process. I am intrigue and I wonder what are the Pros and Cons of decryption?
And with Question 6: So it is a fact that Soft brick is 100% fixable; and Hard brick only happens if I flash a Custom ROM of another phone model. So Hard brick will never happen as long as I always use the appropriate Custom ROM, right? Or there is more there?
Thanks a lot again.
Click to expand...
Click to collapse
Yes. I have my phone encrypted and not rooted and it is working just fine
Every developer of any custom rom gives a detailed guide about how to flash that rom. Follow that guide step by step and your phone will be safe
lhn53 said:
Hi everyone (pardon my English)
I have a Redmi Note 8 Global, and I am willing to install Custom ROM's on it.
I have read and watched several info about this subject, but there are some aspects I am not so clear about it.
I've never done it before, so first I need to dissipate some doubts. I'll appreciate your guidance.
My phone has the bootloader unlocked, and I have successful flashed it with MIUI Official fastboot ROMs three times with Mi Flash. First time with 12.0.6.0, months later with 12.5.1.0 and last time with 11.0.12.0 (and at present I'am still on 11.0.12.0).
Here there are my concerns and doubts:
- Decryption: Is it beneficial ? Mandatory ? Reversible ? What do you recommends ?
- Rooting: Is it beneficial ? Mandatory ? Reversible ? What do you recommends ?
- Is difficult to me to determine which Recovery to choose: TWRP, or Orange Fox ?
- Which Custom ROM for starting, based on Smoothness, Battery life, and Full functionalities: Pixel Experience 12, or Arrow OS 12 ?
- Can I install any Custom ROM no matter which one I have installed at the time ? For example: Going from Official MIUI 11.0.12.0 to Custom Pixel Experinece 12 ?
- Which are the real probabilities of soft or hard brick to happen during the process, and how to avoid it ?
- Is case of the worst scenario of soft or hard brick, can that be fixable ?
- Any direction to a concise detailed guide starting from the installation of the Custom Recovery to the Custom ROM flashing ?
- Is this hole Custom ROM flashing process completely reversible to the original factory state of the phone, if I want it someday ?
Thank you a lot in advanced, and pardon these so many questions. I really want it but don't want to messing up.
Click to expand...
Click to collapse
1. Yes, it's beneficial in case your phone got stolen at least your data is secured, add more with pattern and fingerprints. Always go for enforcing rom and kernel for even more secure.
2. Depends: if you mostly work with secure apps such banking, no it's not. However some custom roms don't pass CTS, you'll have to root to gain it (it's needed for most banking apps)
3. Orange fox is preferable, though others like PBR, or official twrp is also good. It's just matter of preferences. Always get the clean one with source .
4. Official Lineageos is always the best path to taste open source android, since it's totally backed by open source community: no ads ridden links, clean source, guaranteed weekly build, etc.
5. Yes you can. Clean data is must (and format if you're encrypted) every time you switch between roms and between version (11 to 12, vice versa) or the rom's maintainer told you to do so.
6. Minimal. Just make backup your persist and efs partition using your recovery and you're good to go, but it very rarely happens.
7. Soft brick: forget to wipe/format data when flashing other roms, flashed bad kernel, etc. Hard brick mostly because doing some stupid stuff (flash wrong rom device with their firmware) or bad things happen unexpected (battery off during flash, etc)
8. Many from wiki pages on lineageos to youtube videos. In short: unlocked bootloader, flash recovery, backup, backup, backup, flash roms, format data
9. Yes, unless you did stupid stuff and made a hard brick, then it's EDL only
Well, thank you very much again to everyone. I really appreciate it, cause I'm really new to this, and I want to be the best prepared I can before doing this.
At the end, I know the path to take is custom ROM if I want to keep my RN8 the most updated possible.
I really didn't like the Officials MIUI 12 and MIUI 12.5 ROMs (even after fastboot them). Not for having a bad interface but for bad optimization in general. That's my humble opinion and experience with them. I ended up with MIUI 11 / Android 9... XD
(again, please pardon my English)
Doing some research I've found different guides that leads me to more questions:
- Catches my attention that in this guide: OFFICIAL Arrow OS Android 12 STABLE Redmi Note 8/8T (
),
the person flashed the original MIUI Firmware first. Why he did that? What are the differences between ROM and Firmware? Is it always necessary?
- Regarding the flashing of Orange Fox Recovery. In some videos I saw that the person doing the guide flashed the recovery in Windows with ADB commands and that's it. But in others guides I see the person flashing the recovery in Windows with ADB commands, then restart the phone and enter orange fox and flashed orange fox again within the proper Orange Fox. Which is the right way to do it?
- Regarding flashing ROMs: In other guides the person says that you have to Wipe/Clear Data before and after the ROM flashing. Others says is only before, and other says is only after. Which is the right way?
- Last but not least: I saw two Pixels Customs ROM: "PixelExperience", and "PixelOS". Which one is the most convenience?
Sorry again for so many question but as you can see it is confusing.
THANKS A LOT ...AGAIN !!!
lhn53 said:
Doing some research I've found different guides that leads me to more questions:
- Catches my attention that in this guide: OFFICIAL Arrow OS Android 12 STABLE Redmi Note 8/8T (
),
the person flashed the original MIUI Firmware first. Why he did that? What are the differences between ROM and Firmware? Is it always necessary?
- Regarding the flashing of Orange Fox Recovery. In some videos I saw that the person doing the guide flashed the recovery in Windows with ADB commands and that's it. But in others guides I see the person flashing the recovery in Windows with ADB commands, then restart the phone and enter orange fox and flashed orange fox again within the proper Orange Fox. Which is the right way to do it?
- Regarding flashing ROMs: In other guides the person says that you have to Wipe/Clear Data before and after the ROM flashing. Others says is only before, and other says is only after. Which is the right way?
- Last but not least: I saw two Pixels Customs ROM: "PixelExperience", and "PixelOS". Which one is the most convenience?
Sorry again for so many question but as you can see it is confusing.
THANKS A LOT ...AGAIN !!!
Click to expand...
Click to collapse
1. You have to flash firmware because the firmware contains the files of your wireless network. If you don't flash this your wireless network will not work
2. Let me make this clear. Many custom roms have a tendency to replace the custom recovery you flashed with the custom roms own recovery. If you just flash the custom recovery using ADB then the custom rom will replace the custom recovery with its own one. Like if you flash the orange fox and then flash pixel experience without flashing the orange fox again then pixel experience will wipe orange fox and then flash the PE recovery.
But if you install orange fox recovery through ADB and then enter orange fox and flash orangefox again you are just permanently turning off the option that the custom rom will change your custom recovery and put there custom recovery
3. As you are using a Xiaomi phone you have to wipe Dalvik, System, Vendor, Cache, Data before flashing the rom. Then after flashing the rom you have to format data / clear the data partition otherwise the phone will stuck in bootloop
4. Pixel OS and Pixel Experience are both somewhat alike. They try to bring the fluid performance and look of Pixel phones in a non pixel device. But many people prefer the Pixel Expereince rom. But trust me. Pixel OS is also good
Evil_Hunter said:
1. You have to flash firmware because the firmware contains the files of your wireless network. If you don't flash this your wireless network will not work
2. Let me make this clear. Many custom roms have a tendency to replace the custom recovery you flashed with the custom roms own recovery. If you just flash the custom recovery using ADB then the custom rom will replace the custom recovery with its own one. Like if you flash the orange fox and then flash pixel experience without flashing the orange fox again then pixel experience will wipe orange fox and then flash the PE recovery.
But if you install orange fox recovery through ADB and then enter orange fox and flash orangefox again you are just permanently turning off the option that the custom rom will change your custom recovery and put there custom recovery
3. As you are using a Xiaomi phone you have to wipe Dalvik, System, Vendor, Cache, Data before flashing the rom. Then after flashing the rom you have to format data / clear the data partition otherwise the phone will stuck in bootloop
4. Pixel OS and Pixel Experience are both somewhat alike. They try to bring the fluid performance and look of Pixel phones in a non pixel device. But many people prefer the Pixel Expereince rom. But trust me. Pixel OS is also good
Click to expand...
Click to collapse
Thanks again for such a good explanation. I appreciated.
Pardon me, but about the Firmware flashing is still kind of unclear for me, cause I didn't see this mentioned on many guides I've seen, only in that one I posted, and triggers my doubt.
About this:
- Do I always have to flash the firmware before the custom or original ROM?
- In which scenario is this necessary?
- If it is. Which version of firmware I need for every custom ROM I'll try? I mean, for example, LineageOS is Andorid 10, so do Firmware of MIUI 12 is needed?, Or if ArrowOS so do Firmware of MIUi 12.5 is needed? Etc etc.
Hope I could explain myself cause of my bad English.
Thanks a lot again and again.
Evil_Hunter said:
Let me make this clear. Many custom roms have a tendency to replace the custom recovery you flashed with the custom roms own recovery. If you just flash the custom recovery using ADB then the custom rom will replace the custom recovery with its own one. Like if you flash the orange fox and then flash pixel experience without flashing the orange fox again then pixel experience will wipe orange fox and then flash the PE recovery.
Click to expand...
Click to collapse
There is no such thing with custom roms
Only Official miui roms (and some few that come with "Recovery" file inside the zip) does that
so check the zip first ...
1st time you want to flash the recovery = flash "vbmeta" then Ofox and select :
"aggresive stock recovery deactivation" in Ofox settings
lhn53 said:
- Do I always have to flash the firmware before the custom or original ROM?
Click to expand...
Click to collapse
No
lhn53 said:
- In which scenario is this necessary?
Click to expand...
Click to collapse
FW have drivers for cam/Bt/wifi ...
you have to flash if you change Android version, for exp
from A? to A10 = flash A10 FW
from A? to A11 = flash A11 FW
lhn53 said:
- Which version of firmware
Click to expand...
Click to collapse
If you have Ginkgo = flash Ginkgo
If you have Willow = flash Willow
(don't make mistake with fw ! you will break your device)
i didn't read everything (too much) just follow the clean flash steps and you will be fine
stay away from A12 (not very stable)
A11 is resource hungry
i suggest using A10 (RRos or MSM Ext or Superior) (i use RRos)
loopypalm said:
There is no such thing with custom roms
Only Official miui roms (and some few that come with "Recovery" file inside the zip) does that
so check the zip first ...
1st time you want to flash the recovery = flash "vbmeta" then Ofox and select :
"aggresive stock recovery deactivation" in Ofox settings
No
FW have drivers for cam/Bt/wifi ...
you have to flash if you change Android version, for exp
from A? to A10 = flash A10 FW
from A? to A11 = flash A11 FW
If you have Ginkgo = flash Ginkgo
If you have Willow = flash Willow
(don't make mistake with fw ! you will break your device)
i didn't read everything (too much) just follow the clean flash steps and you will be fine
stay away from A12 (not very stable)
A11 is resource hungry
i suggest using A10 (RRos or MSM Ext or Superior) (i use RRos)
Click to expand...
Click to collapse
Perfect. Thanks a lot to all.
And LineageOS? Is it worth it?
So for example, if I want LineageOS 17.1 (that is A10), I have to flash first MIUI latest FW based on A10? And which version of MIUI FW do I need, the last one? For that example would be 12.0.6.0. isn't it? ...and so on with other Custom ROMs?
Is this site for that matters...?:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
lhn53 said:
And LineageOS? Is it worth it?
Click to expand...
Click to collapse
Lineage17 is A10 and that's it (nothing more)
RRos = Lineage + customization (both based on the same exact thing)
lhn53 said:
So for example, if I want LineageOS 17.1 (that is A10), I have to flash first MIUI latest FW based on A10?
Click to expand...
Click to collapse
Yes, latest stable
lhn53 said:
And which version of MIUI FW do I need, the last one? For that example would be 12.0.6.0. isn't it? ...and
Click to expand...
Click to collapse
Yes
lhn53 said:
so on with other Custom ROMs?
Click to expand...
Click to collapse
Only If you change Android version
if from A10 to A10 = no need
lhn53 said:
is this site for that matters...?:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Click to expand...
Click to collapse
Redmi note 8 = Ginkgo
Redmi note 8 "T" =Willow
loopypalm said:
Lineage17 is A10 and that's it (nothing more)
RRos = Lineage + customization (both based on the same exact thing)
Yes, latest stable
Yes
Only If you change Android version
if from A10 to A10 = no need
Redmi note 8 = Ginkgo
Redmi note 8 "T" =Willow
Click to expand...
Click to collapse
Hi, I reiterate my thanks to everyone for the help.
It is evident you prefer RRos. I'll take it into account.
Now it is clear that the FW has to be the same Android version as the ROM:
1- But the latest MIUI for the RN8 is based on A11, so what FW do you use for the A12 ROMs? The FW of MIUI 12.5.1.0?
2- Do you have to flash the FW every time you install a new ROM, or only if you change the version of Android?
3- This matter of flashing the FW do I have to do it in a specific way, or is it handled by Orange Fox as the ROM?
4- I am currently using MIUI 11.0.12.0 Android 9. If I want to install RRos which is based on A10, do I have to flash MIUI 12.0.6.0 FW first?
I'm planing on using OrangeFox... Starting from the fact that I only have the Bootloader unlocked, is it too much to ask if you would write me a concise and simple guide on how to achieve this? Or point me to one as alike as possible to my case?
I know that time is gold, and I do not want to abuse your time, so I will appreciate any help you can provide. I am grateful already for all the help shown so far.
THANKS
lhn53 said:
1- But the ...
so what FW do you use for the A12 ROMs?
Click to expand...
Click to collapse
It looks like you look for problems
lhn53 said:
2- Do you have to flash the FW every time you install a new ROM, or only if you change the version of Android?
Click to expand...
Click to collapse
Re read what i wrote previously
lhn53 said:
3- This matter of flashing the FW do I have to do it in a specific way, or is it handled by Orange Fox as the ROM?
Click to expand...
Click to collapse
Same as the rom, flash like any zip
lhn53 said:
4- I am currently using MIUI 11.0.12.0 Android 9. If I want to install RRos which is based on A10, do I have to flash MIUI 12.0.6.0 FW first?
Click to expand...
Click to collapse
you serious ?
lhn53 said:
Starting from the fact that I only have the Bootloader unlocked
Click to expand...
Click to collapse
-Reboot
-hold Vol- to go to fastboot
-flash vbmeta using : (assuming the img is named vbmeta.img)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(you can find vbmeta it in any A10 rom zip)
-flash twrp
-reboot to recovery (NOT SYSTEM !) using vol+
-flash Ofox zip
-set : "aggresive stock recovery deactivation" in Ofox settings
-clean flash the rom as already mentioned
-done
loopypalm said:
It looks like you look for problems
Re read what i wrote previously
Same as the rom, flash like any zip
you serious ?
-Reboot
-hold Vol- to go to fastboot
-flash vbmeta using : (assuming the img is named vbmeta.img)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(you can find vbmeta it in any A10 rom zip)
-flash twrp
-reboot to recovery (NOT SYSTEM !) using vol+
-flash Ofox zip
-set : "aggresive stock recovery deactivation" in Ofox settings
-clean flash the rom as already mentioned
-done
Click to expand...
Click to collapse
Thanks a lot.
loopypalm said:
you serious ?
Click to expand...
Click to collapse
Yes. I have to say I'm taking really serious regarding all about this process. Believe me, I have to minimized as much that is possible the risks on breaking my phone. It is REALLY expensive buying or fixing it where I life. I need to double check every important aspect, and try to understand the more I can about this. I don't like too much learning things mechanically, if I can learn the logic behind.
Pardon me all If I bothered you any how. Wasn't my intention.
Really appreciate the guide and help that everybody give me here. Thanks
lhn53 said:
Yes. I have to say I'm taking ...
Click to expand...
Click to collapse
The question has been answered like 3 times
Re read what i wrote
loopypalm said:
The question has been answered like 3 times
Re read what i wrote
Click to expand...
Click to collapse
Well, yes, you are right. I asked about the FW flashing process various times.
But, see, I've been investigating to changing the ROM of my phone for various days, and for that I watched some videos tutorials and guides in sites.
When I thought I was almost ready to start, I found a video where a person was flashing a Custom ROM and first flashed a Firmware and then the ROM (I mentioned this before). And in my case that video was the 1st time where I was hearding the term "firmware" in a Custom ROM flashing guide. Sawing that, I was like: Whaaaat? Then because of it I had to postergate the flashing of my phone and keep digging, cause I knew that the "firmware" is really important in every electronic equipment. Messing with it is dangerous.
I admit again the constants askings about FW, ...sorry about that. What I have just explained here were the true cause. I just needed to be more sure.
So I ended up here at XDA searching for learning and to clear doubts.
Thx u and everyone for your patient. I'll try not to bother too often.
@lhn53 : if you're that unsure, my advice would be to proceed cautiously and step-by-step, ensuring you can back out any major ****-up.
- Get MiFlash and the appropriate recovery stock ROM (in the worst case scenario, it will allow you to revert back to stock);
- Set up a custom recovery, ensure that it sticks, then familiarize yourself with it (you have multiple choices: TWRP, OrangeFox and PBRP);
- Choose the custom ROM you want to flash and read all related resources at least twice; then,
- Try to follow the procedure explained by the developer to the point, so if anything goes awry you can point to where it diverged;
- That applies to changing or updating firmware, just go with what the dev says on first instance;
- Finally, trust loopypalm, he knows what he's talking about and has been here longer than most.
Hi, thanks for replaying pnin and of course loopypalm, and everybody helping here.
It's just that when you see searching the WEB so many criteria and some differ from each other, doubts grow in a newbie like me. As I mentioned before there are many tutorials in the web where they do not mention the firmware as part of the steps and less about vbmeta.
For me It seemed quite simple at first but now I see it has more important steps to take into account.
pnin said:
- Get MiFlash and the appropriate recovery stock ROM (in the worst case scenario, it will allow you to revert back to stock);
Click to expand...
Click to collapse
...yes, I have MiFlash and various fastboot versions of the stock ROM storaged here.
pnin said:
- Choose the custom ROM you want to flash and read all related resources at least twice; then,
Click to expand...
Click to collapse
Yes, I guess I'll use first the ones with A10 (as advised here).
pnin said:
- Finally, trust loopypalm, he knows what he's talking about and has been here longer than most.
Click to expand...
Click to collapse
Agreed, thx.
pnin said:
- Set up a custom recovery, ensure that it sticks, then familiarize yourself with it (you have multiple choices: TWRP, OrangeFox and PBRP);
Click to expand...
Click to collapse
...with "sticks" I guess you are meaning what loopypalm said before: (...
1st time you want to flash the recovery = flash "vbmeta" then Ofox and select :
"aggresive stock recovery deactivation" in Ofox settings...)
Regarding vbmeta I have some questions (please be patient):
I've search about it, and I see It's like the Secure Boot of Windows.
I have seen various criteria: I saw people saying it is not needed in all RN8, and some says it does, for avoiding bootloop, etc. IMHO I guess that it is better to do it. Right? (...my intention is only of clarifying).
- The vbmeta.img file that is needed is the one inside Xiaomi's fastboot stock ROM compressed file. Is it?
- Is it necessary to flash vbmeta on every installation of a new ROM, or only when it is based on a different Android version?
- In case I want to return to Stock MIUI, this vbmeta step will not be necessary. Ins't? As I have understood, this is done simply with MiFlash..., Or first is it convenient to wipe some data or partitions with Custom Recovery? How would be exactly?
Please remember, I am trying to understand as much as I can about the whole process. In cases like these I like to learn by logic whenever is possible. Thanks a LOT once again.
lhn53 said:
- The vbmeta.img file that is needed is the one inside Xiaomi's fastboot stock ROM compressed file. Is it?
Click to expand...
Click to collapse
Please I only need to know this about vbmeta.
That plus everything that you have described me before, I think would be already all the basis that is needed to start.
Thanks you in advance.
(I'v been using Google Translate for helping me redacting all that I post. Pardon my bad English)
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.