Hello guys, a brief introduction; All the Xiaomi devices running Miui roms out of the box have a dedicated firmware but I didn´t find for those based on Android One or atleast for Daisy.
Every rom requires a specific Firmware to work well so I´ll share the most used here.
This is intended to flash it as a base to avoid the tedious process to flash the whole rom through MiFlash tool.
But be advised although that some times could be required to do a clean flash through MiFlash tool, for some roms or to fix missed partitions being the case as happen too with all the rest of Xiaomi devices and some times flashing the firmware and the vendor from the same version through fastboot will be enough.
I hope that it´ll be useful, please hit thanks if it works, test it, report and share with others the results.
Download Link:
https://drive.google.com/open?id=1Bbt_aTOHABMYQQlVNTy7X0MVJBJoHqgJ
Dont work on daisy (android one)?:crying:
heyimvitor2 said:
Dont work on daisy (android one)?:crying:
Click to expand...
Click to collapse
They´re for Daisy, stock rom is Android One.
Are these just a repack of the fastboot ROMs available from xiaomi?
They are already listed here. And are .tar.gz rather than .zip
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
How to use it? Flash via twrp?
fastboot with miflash
a1291762 said:
Are these just a repack of the fastboot ROMs available from xiaomi?
They are already listed here. And are .tar.gz rather than .zip
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
Fastboot rom is the whole rom including system, userdata, and more as you know to be flashed through fastboot directly or using a tool like MiFlash but these are not a repack but a flashable zip the way that all the update process to switch to other rom can be done while in TWRP.
Cause all my previous devices were running Miui they had available firmwares and never need to flash all the rom as a base for custom roms and since I bought this device I missed this feature.
Here you have a reference what I´m talking about https://xiaomifirmwareupdater.com
prodang2509 said:
How to use it? Flash via twrp?
Click to expand...
Click to collapse
Yes, as any flashable zip, recommendable as first step (as a base) after to make the wipes and before the other required steps.
dochdoc said:
fastboot with miflash
Click to expand...
Click to collapse
Nope, zips can´t be flashed through fastboot.
https://docs.google.com/spreadsheets/d/1Uy6qouIV0WbVouK4X5PhmUz2quxfLguHDqSf6LYDBO8/edit#gid=0
here you have all flashable stock trough miflash/fastboot
SubwayChamp said:
these are a flashable zip the way that all the update process to switch to other rom can be done while in TWRP.
Click to expand...
Click to collapse
I'm used to the fastboot ROMs but these may prove useful... Is there a process for converting a fastboot ROM into a twrp-flashable ROM?
a1291762 said:
I'm used to the fastboot ROMs but these may prove useful... Is there a process for converting a fastboot ROM into a twrp-flashable ROM?
Click to expand...
Click to collapse
If you refer to the whole rom yes, it does. Other Xiaomi devices have a fastboot (tar) and also a recovery (zip) but TWRP must be adapted to work with.
Thank you for this, it is really helpful.
Last night I played with offains TWRP 3.3.1-0 and restored a firmware backup, but it only got deleted and restoring failed.
Then I flashed your 10.3.0 file and all is good. You also put a custom dark splash.img in it, which I really like (was too lazy to create my own). :good:
Firmware 10.0.15
SubwayChamp said:
Hello guys, a brief introduction; All the Xiaomi devices running Miui roms out of the box have a dedicated firmware but I didn´t find for those based on Android One or atleast for Daisy.
Every rom requires a specific Firmware to work well so I´ll share the most used here.
This is intended to flash it as a base to avoid the tedious process to flash the whole rom through MiFlash tool.
But be advised although that some times could be required to do a clean flash through MiFlash tool, for some roms or to fix missed partitions being the case as happen too with all the rest of Xiaomi devices and some times flashing the firmware and the vendor from the same version through fastboot will be enough.
I hope that it´ll be useful, please hit thanks if it works, test it, report and share with others the results.
Download Link:
https://drive.google.com/open?id=1Bbt_aTOHABMYQQlVNTy7X0MVJBJoHqgJ
Click to expand...
Click to collapse
Do you have also the newest firmware 10.0.15? I have a bug with screen rotation (not longer works after a few hours), i hope firmware 10.0.15 is the solution because because I read that a screen rotation error is known.
counti said:
Do you have also the newest firmware 10.0.15? I have a bug with screen rotation (not longer works after a few hours), i hope firmware 10.0.15 is the solution because because I read that a screen rotation error is known.
Click to expand...
Click to collapse
Firmware is based on major updates i.e. on fastboot global images (full rom) when all partitions are modified but is not included in OTA updates (incremental rom) when mostly only system and vendor (sometimes also kernel) receive modifications but all the other partitions remain untouched.
To better understanding the three next OTA updates (v10.0.14.0, v10.0.15.0 and v10.0.16.0) are using as base v10.0.13.0 firmware.
Just appear the next full rom I will upload it but hopefully it is 10.
Great Job !
SubwayChamp said:
Hello guys, a brief introduction; All the Xiaomi devices running Miui roms out of the box have a dedicated firmware but I didn´t find for those based on Android One or atleast for Daisy.
Every rom requires a specific Firmware to work well so I´ll share the most used here.
This is intended to flash it as a base to avoid the tedious process to flash the whole rom through MiFlash tool.
But be advised although that some times could be required to do a clean flash through MiFlash tool, for some roms or to fix missed partitions being the case as happen too with all the rest of Xiaomi devices and some times flashing the firmware and the vendor from the same version through fastboot will be enough.
I hope that it´ll be useful, please hit thanks if it works, test it, report and share with others the results.
Download Link:
https://drive.google.com/open?id=1Bbt_aTOHABMYQQlVNTy7X0MVJBJoHqgJ
Click to expand...
Click to collapse
Hello Dear SubwayChamp,
It Will Be Very Helpful For US. Thank You Once Again...
Thanks for updating this to 10.0.13.
I wanted to create my own file and have some questions about the file emmc_appsboot.mbn
1. The updater script flashes the above file as an img file. Is it ok to just rename the mbn file or is a program like HxD Hex Editor needed?
2. In your 10.0.13 version there is only the mbn file but not the img file, is that ok? In your 10.0.3 file there is only the img file and in 10.0.9 there are both, so I'm a little confused.
I am seeing a few custom Android 10 roms out there, with the Android 9 base firmware, is not better wait for the android 10 base firmware? and the source code for the kernel.
Pat750 said:
Thanks for updating this to 10.0.13.
I wanted to create my own file and have some questions about the file emmc_appsboot.mbn
1. The updater script flashes the above file as an img file. Is it ok to just rename the mbn file or is a program like HxD Hex Editor needed?
2. In your 10.0.13 version there is only the mbn file but not the img file, is that ok? In your 10.0.3 file there is only the img file and in 10.0.9 there are both, so I'm a little confused.
Click to expand...
Click to collapse
Hi, I switched to other devices since I uploaded these files, anyway thanks for notice that, there was an error on the typo in versions 9, 12 and 13.
Xiaomi fastboot ROMs are mirrored on a lot of sites and I don´t remember now from where I downloaded it and I duplicated from inside the version 10.0.9, it wasn´t right, now all the files were re-uploaded and corrected.
As per mbn files can´t be simply renamed as image, you can look inside and change some values with a HEX editor but is not a good idea to make this without a solid knowledge so it may get corrupted and flashing a corrupted bootloader can seriously brick your device anyway don´t worry about so no need to change nothing, TWRP will place the images in the right places/partitions as they´re originally inside the fastboot ROMs.
SubwayChamp said:
Hi, I switched to other devices since I uploaded these files, anyway thanks for notice that, there was an error on the typo in versions 9, 12 and 13.
Xiaomi fastboot ROMs are mirrored on a lot of sites and I don´t remember now from where I downloaded it and I duplicated from inside the version 10.0.9, it wasn´t right, now all the files were re-uploaded and corrected.
As per mbn files can´t be simply renamed as image, you can look inside and change some values with a HEX editor but is not a good idea to make this without a solid knowledge so it may get corrupted and flashing a corrupted bootloader can seriously brick your device anyway don´t worry about so no need to change nothing, TWRP will place the images in the right places/partitions as they´re originally inside the fastboot ROMs.
Click to expand...
Click to collapse
Thank you. I see the changes.
Good luck with your new device. You did some good things here and helped people a lot.
Related
Hi all I i eeded stock rom samsung M200s??
thank advance
samnang ouch said:
Hi all I i eeded stock rom samsung M200s??
thank advance
Click to expand...
Click to collapse
these are the factory images. be sure you get the one for m200....there are several devices on this page.
https://developers.google.com/android/nexus/images
Thank for reply but i need M200s not M200 .
Please Help
I Have a Korean Version of Nexus S (m200) flashed w/ custom Rom 4.2 Hellybean,
can someone help me Flash the Official Stock Rom 4.1 JellyBean please?
and another thing, if it is flashed does my phone still openline (all sim available)?
samnang ouch said:
Thank for reply but i need M200s not M200 .
Click to expand...
Click to collapse
No such thing exists. It's m200.
summereyes said:
I Have a Korean Version of Nexus S (m200) flashed w/ custom Rom 4.2 Hellybean,
can someone help me Flash the Official Stock Rom 4.1 JellyBean please?
and another thing, if it is flashed does my phone still openline (all sim available)?
Click to expand...
Click to collapse
Get that. And read the instructions.
hp420 said:
these are the factory images. be sure you get the one for m200....there are several devices on this page.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Get that. And read the instructions.[/QUOTE]
i already downloaded the factory image for my phone but, i dont know how to flash it please give some step by step procedure please
summereyes said:
Get that. And read the instructions.
Click to expand...
Click to collapse
i already downloaded the factory image for my phone but, i dont know how to flash it please give some step by step procedure please[/QUOTE]
You will find these files useful if you have used the Android Open-Source Project, flashed custom builds on your device, and wish to return that device to its factory state.
In order to use these files, you need to have the fastboot tool in your PATH. That tool is compiled as part of every configuration of the Android Open-Source Project and is the tool used to flash custom builds on your device. On GNU/Linux systems, this also implies that you have configured USB access as mentioned in the machine setup instructions.
Your device needs to be in fastboot mode, with the bootloader unlocked. The relevant key combinations and commands are documented on the page about building for devices.
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default.
After restoring a factory image, it is recommended that you lock the bootloader, for security reasons.
Click to expand...
Click to collapse
So, more or less
Have fastboot working
Boot in fastboot mode
Make sure you untar every file from the link above.
wipe data
fastboot -w update image-sojuk-JRO03E.zip
The stock ROM has a feature called verity, which ensures that the system partition is not modified. It uses a cryptographic signature to verify each sector on the partition. If any sector is modified, it is treated as corrupt.
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
In order to modify your system partition or recover from accidentally mounting your system partition read-write, you must download and flash the correct boot image using tuliptool.
You can find stock boot images with verity removed here:
US model, version 7.1.1 b12
md5=71428e4957763858f47bc9540e848d5e
US model, version 7.1.1 b14
md5=c6a67411e81f27d798eea035ddf4261e
EU model, version 7.1.1 b09
md5=ba210d332d3527b81f652dd0d2ce962e
i tried to see what would happen if i adb sideload supersu and my results came out that the went to zte screen and went into a bootloop didnt boot up but i have root priv in twrp....hmm. so i re-edl boot to after that i was able to boot back in to my android without root or supersu and twrp went back to normal aswell i was in the mood to test thankfully i was able to fix what ever had any issues
What would we need to provide for you to make one for v1.0.0B06?
I can make one for any firmware version. I just need the following:
* any relevant regional or model info.
* firmware version (including android version).
* the backup boot image, eg. from tuliptool.
parawizard said:
What would we need to provide for you to make one for v1.0.0B06?
Click to expand...
Click to collapse
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Depends how you root. I don't run stock so someone else should answer with details.
fallen00sniper said:
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Click to expand...
Click to collapse
tdm said:
Depends how you root. I don't run stock so someone else should answer with details.
Click to expand...
Click to collapse
i'm not a fan of the stock image, i do like to keep features which the stock seems devoid other than atmos which used to be hit or miss lol
i am sure someone out there likes the stock look, i used nova launcher and made things smaller, neater and tried to make it look a little better.
Done some experiments with SuperSU 2.82 (unsuccessfully, got bootloop).
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
Click to expand...
Click to collapse
And was able restore phone to work only with this EU boot.
Thanks, for making and publishing it!
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
bao_gg said:
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Click to expand...
Click to collapse
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Thank you tdm. You are awsome. I will provide you the checksums tomorrow.
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Yes that's exactly it.
TheSSJ said:
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Click to expand...
Click to collapse
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
I would suggest flashing the no verity boot just to avoid the headache
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
JoeGatto said:
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
Click to expand...
Click to collapse
tdm said:
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
Click to expand...
Click to collapse
Great. Looks like I'll be trying AOKP soon.
JoeGatto said:
Great. Looks like I'll be trying AOKP soon.
Click to expand...
Click to collapse
I've been running it for a couple of days and so far its great. No issues here
MrWhite0429 said:
I've been running it for a couple of days and so far its great. No issues here
Click to expand...
Click to collapse
You weren't kidding. Feels much faster than ZTE's ROM, and so refreshing as long as I've been looking at that MiFavor UI.
EDIT: Battery drain during standby.
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Hi tdm, my adb can not recognize the mini. And in order to get the partition info, I need to "boot into twrp" as the instruction says. But my recovery is STOCK not TWRP.
Anyway, if you can make a win32 Tuliptool, I can unlock the bootloader and flash the TWRP in. After that, I can flash any firmware that I want. Is it correct?
Hey all,
I love stock android! So when i read about OpenKirin I was excited. Did anyone use this to install LineageOS on our mate9 successful? What are your experiences?
I have another question as well: I changed my model to the MHA-L29, rooted with a custom recovery.
OpenKirin says it needs to have the stock one. Does anyone have a link to the stock MHA-L29 recovery and a guide on how to install it?
dekraan said:
Hey all,
I love stock android! So when i read about OpenKirin I was excited. Did anyone use this to install LineageOS on our mate9 successful? What are your experiences?
I have another question as well: I changed my model to the MHA-L29, rooted with a custom recovery.
OpenKirin says it needs to have the stock one. Does anyone have a link to the stock MHA-L29 recovery and a guide on how to install it?
Click to expand...
Click to collapse
First off, this thread probably belongs in Q/A.
Moving on:
I've run all 3 provided ROMs, Carbon as my daily driver and Lineage and RR for testing various things. They all work pretty well.
For stock recovery & ramdisk, download your current firmware (or if you've run other Treble ROMs as well, the version that corresponds to your current build number in Settings / System / About Phone) using Firmware Finder - you only need the main update.zip for this. You'll also need one of the utilities for extracting them. There's Huawei Update Extractor (I think that's what it's called anyway) for Windows, or https://github.com/marcominetti/split_updata.pl for Linux / Mac. Extract the ramdisk and recovery ramdisk images and there you go.
Installing those is a matter of rebooting into the bootloader and running:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash ramdisk ramdisk.img
(The name for recovery_ramdisk.img may vary a bit - the windows app will extract it as RECOVERY_RAMDIS.img.)
From there, just follow their instructions. If you have any problems, hit up the Telegram chat linked off the site, someone will be willing to help.
@irony_delerium, thank you very much. That sounds like something even I can do without too much problems
How do you like it, being on LineageOS?
dekraan said:
@irony_delerium, thank you very much. That sounds like something even I can do without too much problems
How do you like it, being on LineageOS?
Click to expand...
Click to collapse
Like I said in my original reply, my daily driver is Carbon; the Lineage builds I've only run briefly because NFC wasn't enabled, but the CarbonROM builds there have it. I use Google Pay every day, so it's kind of a requirement for me.
With that said, the only thing that's got issues for me is the camera app, and most of the blame for that is with Huawei. It generally works, but it'll close & restart often when switching modes or trying to start a recording.
I know there are various other minor issues with recording video in all 3, again because Huawei. (They put together bum codecs, and then patched the system side of the EMUI media stack to deal with the bum codecs, instead of fixing the codecs.)
Also worthy of mention (especially because I see people asking about this all the time): there is no VoLTE support. The devs are aware of it. Unless you're on a network that is pure LTE, it's mostly a non-issue. If you are, it's probably a deal breaker.
Getting on from there, they're all clean Android experiences, without the overbearing weight of EMUI. They don't try to pull some of the things EMUI did - the final breaking point for me was when it insisted on terminating apps in the background regardless of how much you might actually be using them. (In my case, AdGuard as a VPN service.)
Dear Sir
How Can I Revert to Stock Emui?
I am on Lineage baeta 4 ROM.
With Stock Recovery.
Tried Update and Hwota Methods but no Success.
I have Searched Everywhere.
Please Do A Step By Step Guide for Newbies.
Regards
talpur1 said:
Dear Sir
How Can I Revert to Stock Emui?
I am on Lineage baeta 4 ROM.
With Stock Recovery.
Tried Update and Hwota Methods but no Success.
I have Searched Everywhere.
Please Do A Step By Step Guide for Newbies.
Regards
Click to expand...
Click to collapse
Some comments before, Huawei Firmware Extractor. Extract system.img from the stock rom you used before flash Lineage.
Flash stock system.img in fastboot.
I have downloaded and tried to extract 4 roms but The Extractor tool is Giving error.
Its Giving invalid Hearder crc error.
talpur1 said:
I have downloaded and tried to extract 4 roms but The Extractor tool is Giving error.
Its Giving invalid Hearder crc error.
Click to expand...
Click to collapse
Go to settings in the app and disable CRC checking. (Bug in the app.)
I was on OldDroid's OpenKirin, but today switched to Carbon Beta 2 from https://openkirin.net/download/. This installed without problems and I did a hard reset as part of installation. The earlier version worked very well, except there were a few bugs. I haven't found any bugs in this ROM yet.
Random question: Does anyone know if it's safe to go from one build to another directly? I'm trying Lineage but would like to give Resurrection Remix a go. The instructions say that you should be coming from EMUI...
Thanks
jellmoo said:
Random question: Does anyone know if it's safe to go from one build to another directly? I'm trying Lineage but would like to give Resurrection Remix a go. The instructions say that you should be coming from EMUI...
Thanks
Click to expand...
Click to collapse
It's fine to go between them, provided you reload the stock ramdisk (if you installed Magisk) & factory reset before booting into the new ROM.
irony_delerium said:
It's fine to go between them, provided you reload the stock ramdisk (if you installed Magisk) & factory reset before booting into the new ROM.
Click to expand...
Click to collapse
You can switch between the Custom Roms. I always do. Backup your data on the data partition via USB to PC, go to TWRP do a factory reset and then install the new image via fastboot. Reboot and rejoice
mcc2005 said:
You can switch between the Custom Roms. I always do. Backup your data on the data partition via USB to PC, go to TWRP do a factory reset and then install the new image via fastboot. Reboot and rejoice
Click to expand...
Click to collapse
TWRP only works right on a Huawei device if you're either decrypted or running EMUI. (On a custom ROM, with an encrypted device, TWRP doesn't even start up - it locks up at the splash screen.)
Factory reset using stock recovery. Only using stock recovery. The OpenKirin team will not support any other configuration.
yes you are right. but there is still the possibility to do these things with a patched TWRP. I use this for my Mate 9 https://drive.google.com/file/d/1h50RJ6LNNSEVW9CS16C0NjeP7ZZNTECE/view?usp=sharing
mcc2005 said:
yes you are right. but there is still the possibility to do these things with a patched TWRP. I use this for my Mate 9 https://drive.google.com/file/d/1h50RJ6LNNSEVW9CS16C0NjeP7ZZNTECE/view?usp=sharing
Click to expand...
Click to collapse
And the reason why I say anything is because the 2 most common problems I see are:
1) "I'm on Jio, where's my VoLTE?"
2) "I used TWRP and (it's not working | I screwed up | it's broken)".
The response to the first is universally, go back to stock.
The second, restore your entire stock firmware and then follow the instructions exactly as they are written.
With root, you can back up your apps with Titanium. I haven't had good luck with backing up settings with Titanium and after attempting to restore settings, I usually wind up wasting an hour or two and then factory-resetting and just reinstalling the apps. Now I don't even bother backing up settings, but just back up my apps. Even then two or three seem to be botched but uninstalling/reinstalling those will fix that problem. (It isn't always the same ones, either; not sure what causes this). This approach avoids the pain of configuring apps, e.g. travel app usernames and passwords, as well as preserving messages and the like. The biggest nuisance for me is that I carry around 40 unread Amazon books, which have to be sent to the phone (and I'm not so good at remembering which ones I've already read out of the more than 500 in my account), and I carry a bunch of google offline maps, which have to be manually recreated. Lastpass helps with login information too.
In my most recent (Carbon B2) install, I didn't bother with the backup but installed everything fresh and I had a fully functioning phone with 99% of the configuration I like within 2 hours, since I'd been pretty careful to put all the passwords and so on for my roughly 80 apps into a secured text file, as well as backing up my Nova launcher settings.
Hi guy's I got a question if anyone can help me out
I'm on MHA-L29 8.0.0.360 (c567)
No custom rom but I got root with supersu
How can I install this carbon rom I try allready but twrp ask me on what partition I want to install the .img file and It shows bunch of it
I'm running twrp latest by pretoriano
Thank you very much guys
Caguayote said:
Hi guy's I got a question if anyone can help me out
I'm on MHA-L29 8.0.0.360 (c567)
No custom rom but I got root with supersu
How can I install this carbon rom I try allready but twrp ask me on what partition I want to install the .img file and It shows bunch of it
I'm running twrp latest by pretoriano
Thank you very much guys
Click to expand...
Click to collapse
Restore your stock ramdisk and recovery partitions. (I'd actually start with a full restore to stock firmware first: get your vendor patches in order. 8.0.0.369 is available for most phones on c567, 370 might be available.)
Factory reset using stock recovery. Flash with fastboot. Magisk for root & SafetyNet.
irony_delerium said:
Restore your stock ramdisk and recovery partitions. (I'd actually start with a full restore to stock firmware first: get your vendor patches in order. 8.0.0.369 is available for most phones on c567, 370 might be available.)
Factory reset using stock recovery. Flash with fastboot. Magisk for root & SafetyNet.
Click to expand...
Click to collapse
do you know where can i download the stock ramdisk and recovery partition for mate 9 i was running 8.0.0.369 sorry i put 360
im stuck on twrp splash screen and i cant go to access my backup file to restore and i only access fastboot mode
but my phone says unlocked then frp says lock thanks for all your help
Now i'm using android 7.0. based rom aur 2.3, if i want to install that stock android rom, do i have to flash android 8 based twrp?
Disclaimer: I don't know much about what I am doing, but I watched multiple tutorials and read articles.. would be really nice to get some help with that... hope you can bear with me
Hello, I am trying to root my Poco F2 Pro using Magisk.
I just wanted to the boot.img, so that I can modify it with Magisk, but I can't find the proper one (or... I am not sure whether this is the proper one).
On xiaomifirmwareupdater, I find the right MIUI version (V13.0.2.0.SJKEUXM); but it is the Recovery file, not the Fastboot file :/
When trying to download the ROM via the Phone (AboutPhone/MIUI-Version/Donwload latest package), the file is "corrupted" (I try to open it on my WIndows PC using Winrar, but it says it won't work)
Can someone help me, find the right fastboot ROM file please?
Or any other way, how to get to the boot.img, BUT without using the TWRP (I don't have it)?
Thank you very much and have a nice day
Quick update... I didn't want to risk flashing the wrong boot image... therefore downgraded to MIUI 12 (where there BOTH the Fastboot and recovery file are available).
same problem here, waiting for someone who can help
I will try this found it
in here
nice thank you!
LG_GR said:
Disclaimer: I don't know much about what I am doing, but I watched multiple tutorials and read articles.. would be really nice to get some help with that... hope you can bear with me
Hello, I am trying to root my Poco F2 Pro using Magisk.
I just wanted to the boot.img, so that I can modify it with Magisk, but I can't find the proper one (or... I am not sure whether this is the proper one).
On xiaomifirmwareupdater, I find the right MIUI version (V13.0.2.0.SJKEUXM); but it is the Recovery file, not the Fastboot file :/
When trying to download the ROM via the Phone (AboutPhone/MIUI-Version/Donwload latest package), the file is "corrupted" (I try to open it on my WIndows PC using Winrar, but it says it won't work)
Can someone help me, find the right fastboot ROM file please?
Or any other way, how to get to the boot.img, BUT without using the TWRP (I don't have it)?
Thank you very much and have a nice day
Click to expand...
Click to collapse
u can extract boot.img from recovery rom also no need for fastboot rom
Hello everyone, I have the OP9 china varient,
I've flashed custom ROMs in some devices in the past, specially on a Poco F1 and a Mi 11 Ultra (flashed MIUI.EU in it several times). With the OnePlus 9 the process with unlocking the bootloader was a bit different but I got it to work. But when it comes to custom ROMs installation, the end result is always a bricked device and I had to use MSM from OP9 pro to unbrick and then OP9 MSM to get the device back to normal. I've downgraded everytime to OxygenOS 11 but it didn't work. Can someone help me find out what am I doing wrong?
My procedure besides unlocking the bootloader was:
1. Install boot.img
2. From fastboot to recovery
3. Wipe everything (tried not doing it with the same result)
4. Install ROM via ADB (as an update)
5. Wipe everything (tried not doing it with the same result)
6. Reboot
7. Brick..
I've considered it being an ADB drivers problem, but the device is recognized in the computer as an ADB device so I don't think it is.
As I install through ADB, the CMD window keeps the percentage going up but on the device it never shows anything ROM related as it is being installed, just the final message saying steps 2/2 had been completed.
Thanks in advance, and happy flashing guys!
Change to slot A before flashing. Slot B just doesn't flash right most of the time. Sometimes the device still bricks despite doing everything right though and after the last one, I just went back to stock and stayed there. It's far less likely to brick if you're flashing slot A though in my experience.
You are making sure to use the posted recovery image with each ROM as well, right?
Try StagOS as it was the least problematic for me, both flashing and in terms of bugs. Go to slot A like I recommended and then follow the instructions including flashing the copy partitions zip.
EtherealRemnant said:
Change to slot A before flashing. Slot B just doesn't flash right most of the time. Sometimes the device still bricks despite doing everything right though and after the last one, I just went back to stock and stayed there. It's far less likely to brick if you're flashing slot A though in my experience.
You are making sure to use the posted recovery image with each ROM as well, right?
Try StagOS as it was the least problematic for me, both flashing and in terms of bugs. Go to slot A like I recommended and then follow the instructions including flashing the copy partitions zip.
Click to expand...
Click to collapse
Hey, I've only tried Nameless OS and EvolutionX.
The think I liked about the Poco F1 is that it had no Slot A/B mess (though I've heard A/B slot is better overall).
I'm pretty sure both recoveries went straight to slot A but I might be wrong.
To be fair, stock OOS12 is working fairly good. I just like to help developing custom ROMs and try new stuff. Next time I find time to mess with the phone I'll try StagOS as you suggested. Thank you for your time and opinion.
lleonardocruzz said:
Hey, I've only tried Nameless OS and EvolutionX.
The think I liked about the Poco F1 is that it had no Slot A/B mess (though I've heard A/B slot is better overall).
I'm pretty sure both recoveries went straight to slot A but I might be wrong.
To be fair, stock OOS12 is working fairly good. I just like to help developing custom ROMs and try new stuff. Next time I find time to mess with the phone I'll try StagOS as you suggested. Thank you for your time and opinion.
Click to expand...
Click to collapse
If you use the copy partitions zip before you flash and then you reboot recovery, you end up with both partitions having the same data before you flash and much less likelihood of a brick. Also, don't clear data after you flash, that caused me to reboot to fastboot when I was done flashing and at that point I couldn't recover the OS and had to use the MSM.
I am not a fan of the A/B system but I will say that my Pixel 3 XL didn't have this issue.
EtherealRemnant said:
If you use the copy partitions zip before you flash and then you reboot recovery, you end up with both partitions having the same data before you flash and much less likelihood of a brick. Also, don't clear data after you flash, that caused me to reboot to fastboot when I was done flashing and at that point I couldn't recover the OS and had to use the MSM.
I am not a fan of the A/B system but I will say that my Pixel 3 XL didn't have this issue.
Click to expand...
Click to collapse
I've never used copy partitions zip in any of my flashing attempts so it might fix my issue. I find it weird that it wasn't mentioned in any of the ROMs I tried but maybe it's something they assume people will do.
lleonardocruzz said:
I've never used copy partitions zip in any of my flashing attempts so it might fix my issue. I find it weird that it wasn't mentioned in any of the ROMs I tried but maybe it's something they assume people will do.
Click to expand...
Click to collapse
It's only mentioned in the Stag thread and I think Lineage too but it should work with every ROM since it's only a recovery script that copies the partitions.
lleonardocruzz said:
I've never used copy partitions zip in any of my flashing attempts so it might fix my issue. I find it weird that it wasn't mentioned in any of the ROMs I tried but maybe it's something they assume people will do.
Click to expand...
Click to collapse
Copy partitions is def what you need. Your using msm then trying to flash. If you took an ota or used copy partitions after msm. You will be all good. Oos has to be on both slots. This is your issue
mattie_49 said:
Copy partitions is def what you need. Your using msm then trying to flash. If you took an ota or used copy partitions after msm. You will be all good. Oos has to be on both slots. This is your issue
Click to expand...
Click to collapse
so, basically I need to have OOS11 and ensure it is in both slots (by copying the partitions) right? I'm feeling so dumb right now ahah I was going crazy over this
lleonardocruzz said:
so, basically I need to have OOS11 and ensure it is in both slots (by copying the partitions) right? I'm feeling so dumb right now ahah I was going crazy over this
Click to expand...
Click to collapse
It's easier to take an ota update to get oos on both slots truly. Go into system updates. Make sure it's A 11. Seamless updates . However you can do it get it done. Then flashing will be fine.
Can you tell me what is the easiest way to downgrade from A12 to A11 (latest OOS)? The only way I've found was through MSM. It is impossible to install A11 while already being on A12 through OTA right? You're helping me a lot btw, thank you
lleonardocruzz said:
Can you tell me what is the easiest way to downgrade from A12 to A11 (latest OOS)? The only way I've found was through MSM. It is impossible to install A11 while already being on A12 through OTA right? You're helping me a lot btw, thank you
Click to expand...
Click to collapse
There is a downgrade package posted in the forums here. You install the local upgrade APK and then flash the downgrade package.
[OnePlus 9][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
The link to the APK is in the post.
Haven't flashed required firmware in both slots.To do this,flashing copy partions before installing custom rom and then reboot phone to recovery to install custom rom.
mattie_49 said:
It's easier to take an ota update to get oos on both slots truly. Go into system updates. Make sure it's A 11. Seamless updates . However you can do it get it done. Then flashing will be fine.
Click to expand...
Click to collapse
EtherealRemnant said:
There is a downgrade package posted in the forums here. You install the local upgrade APK and then flash the downgrade package.
[OnePlus 9][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
The link to the APK is in the post.
Click to expand...
Click to collapse
cbrown666 said:
Haven't flashed required firmware in both slots.To do this,flashing copy partions before installing custom rom and then reboot phone to recovery to install custom rom.
Click to expand...
Click to collapse
I'm replying to everyone so that you know that I was successful. It was indeed a partition's problem. Sadly I didn't find the ROM as stable as OOS 12 or OOS 11 so I guess I'll stick with Oneplus software for the time being. Thank you so much for the help
lleonardocruzz said:
I'm replying to everyone so that you know that I was successful. It was indeed a partition's problem. Sadly I didn't find the ROM as stable as OOS 12 or OOS 11 so I guess I'll stick with Oneplus software for the time being. Thank you so much for the help
Click to expand...
Click to collapse
Glad that you got it sorted.
I found the same thing. I'm back on OOS12 C.48 with root. Browsing performance sucks with the CPU throttling they do, and they changed the way they do it so the fixes posted in the 9 Pro forum don't work anymore, but it's otherwise better than all the custom ROMs I tried and I don't have much to complain about.
EtherealRemnant said:
Glad that you got it sorted.
I found the same thing. I'm back on OOS12 C.48 with root. Browsing performance sucks with the CPU throttling they do, and they changed the way they do it so the fixes posted in the 9 Pro forum don't work anymore, but it's otherwise better than all the custom ROMs I tried and I don't have much to complain about.
Click to expand...
Click to collapse
I have to agree with both. I'm also a global unit op9 unlocked on C-48 rooted. Anything that is usually still maintained/updated and not deserted is better than custom. Cherry picking and flashing is overrated. Stock isn't bad at all. You guys enjoy your devices.