Hey guys,
Although Mi CC9e (laurus) has been released for some days, there's few discussion on this device. The reason why I bought laurus is because I think it will share a community with Mi A3 (laurel_sprout), and it's easier to get laurus in China (with 6GB RAM). And indeed, laurus use exactly the same kernel with laurel_sprout. Most people think laurus is A only and laurel_sprout is A/B, which is almost, but not entirely correct. Devices launched with Android 9 are mandatory to use system-as-root.
In previous versions of Android, devices that didn't support A/B updates could mount the system image under the /system directory. In Android 9, the root of the system image is mounted as the root of the device.
Click to expand...
Click to collapse
In short, laurus MUST flash A/B image instead of A only, just like Mi 9 (cepheus) and Mi Mix 3 (perseus).
I assume that your'phone is unlocked and you've configured ADB and Fastboot.
So, let's start.
1. Flash TWRP
Reboot your laurus to Fastboot with Power + Volume Down.
There's a available TWRP from Chinese developer LR.Team
Download Link
The batch script is in Chinese, but I'm sure you know what to do if you're familar with Fastboot.
Code:
fastboot flash recovery recovery-TWRP-3.3.1-0914-XIAOMI_CC9E-CN-wzsx150.img
2. Flash BeastROM 1.6
Although BeastROM 2.0 has released but I can't get it work. It just display Mi logo and then jump to Fastboot. Most other GSIs won't work as well, it dosen't boot at all. So the only choose is BeastROM 1.6 for laurel_sprout @mdeejay.
BeastROM 1.6
unzip it, and what we need to do is flash system.img ONLY.
Code:
fastboot flash system system.img
And then reboot to TWRP, wipe data partition.
Edited:
You can find your vbmeta in fastboot ROM of laurus.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This command is NOT NEEDED if you can disable dm-verity via magisk. You can't boot without disabling dm-verity (stuck on Logo). I don't know how it works. Need some help from devs.
3. Flash Magisk
You HAVE TO flash magisk, or it will stuck on boot animation.
You can do it by "Install Root" in Advanced of TWRP.
Or do it manually by flash Magisk.
4. Flash GApps (Optional)
OpenGApps
Just Flash it in TWRP, nothing more to say. Maybe you need to wipe data again.
I think everything is perfect for now, execpt it's Android 9 instead of 10. At least you can get most of features in Mi A3 and get rid of stupid MIUI
Some stupid idea: for people who wanna get MIUI in laurel_sprout, you can flash system.img in fastboot of laurus. I don't think it will work but it worth trying.
I've tried flashing laurel_sprout image into laurus, it can boot, but it won't work. Screen blinks and it get stuck on welcome page, touching works though.
Fastboot of laurus
Fastboot of laruel_sprout
For people who prefer stock A3 Android One ROM, Here is the method I've tested
con_sau_may_tinh said:
mi cc9e can use stock rom of mi a3 without root, this mean bank app will work perfect
1- flash full rom with miflash (any lower version will not boot) http://bigota.d.miui.com/V10.2.13.0...FMCNXM_20190830.0000.00_9.0_cn_fc9f51f46d.tgz
2- download rom of mi a3, extract file system.img only
http://bigota.d.miui.com/V10.3.4.0....0.PFQMIXM_20190815.0000.00_9.0_00838b4c0e.tgz
3- go to fastboot and flash (vbmeta of micc9e)
fastboot flash system system.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
Click to expand...
Click to collapse
i flash only system but, my phone stuck on fastboot mode
please help
vanly6.2 said:
i flash only system but, my phone stuck on fastboot mode
please help
Click to expand...
Click to collapse
Are your device Mi CC9e instead of Mi A3? Make sure you're flashing BeastROM 1.6 instead of 2.0 or you'll get stuck on fastboot. And maybe you need to format your data partition in TWRP.
Crosstyan said:
Are your device Mi CC9e instead of Mi A3? Make sure you're flashing BeastROM 1.6 instead of 2.0 or you'll get stuck on fastboot. And maybe you need to format your data partition in TWRP.
Click to expand...
Click to collapse
i has flash ok, but i can use finger, you have problem as me ?
vanly6.2 said:
i has flash ok, but i can use finger, you have problem as me ?
Click to expand...
Click to collapse
Fingerprint sensor works for me.
Can i back to miui if something wrong,or on bootloop
oska3 said:
Can i back to miui if something wrong,or on bootloop
Click to expand...
Click to collapse
Of course you can, just flash the fastboot ROM of laurus.
Stug on fastboot too
How i can go in twrp
oska3 said:
Stug on fastboot too
How i can go in twrp
Click to expand...
Click to collapse
Power and Volume up can make it boot into Recovery.
But if you flashed dtbo and vbmeta of BeastROM 1.6, or maybe you wipe your system partition. , it will be stuck at fastboot and cannot boot (or enter recovery)
One way to fix this is disable dm-verity, just use magisk, you can do it by "Install Root" in Advanced of TWRP. (Flashing magisk manully does the same job)
(However, you can't enter TWRP, so this won't work. )
Another way to disable dm-verity is flash vbmeta with --disable-verity --disable-verification, but I'm not sure whether it works.
Your best chioce is flash the fastboot ROM of laurus and do it again. Remerber to flash magisk in TWRP after flashing system.img, I made a mistake that magisk is not included in BeastROM and you must flash it to disable dm-verity or it will never boot.
im fix it and its ok now,how,i dont know
finaly miui gone,yyyuuhuu
If u update magisk and stug on bootloop,u can start on twrp and flash magisk manualy and reboot in beastrom again
---------- Post added at 09:32 PM ---------- Previous post was at 08:37 PM ----------
Just dont use or update to magisk 20,stug on bootloop
Crosstyan said:
Hey guys,
Although Mi CC9e (laurus) has been released for some days, there's few discussion on this device. The reason why I bought laurus is because I think it will share a community with Mi A3 (laurel_sprout), and it's easier to get laurus in China (with 6GB RAM). And indeed, laurus use exactly the same kernel with laurel_sprout. Most people think laurus is A only and laurel_sprout is A/B, which is almost, but not entirely correct. Devices launched with Android 9 are mandatory to use system-as-root.
In short, laurus MUST flash A/B image instead of A only, just like Mi 9 (cepheus) and Mi Mix 3 (perseus).
I assume that your'phone is unlocked and you've configured ADB and Fastboot.
So, let's start.
1. Flash TWRP
Reboot your laurus to Fastboot with Power + Volume Down.
There's a available TWRP from Chinese developer LR.Team
Download Link
The batch script is in Chinese, but I'm sure you know what to do if you're familar with Fastboot.
Code:
fastboot flash recovery recovery-TWRP-3.3.1-0914-XIAOMI_CC9E-CN-wzsx150.img
2. Flash BeastROM 1.6
Although BeastROM 2.0 has released but I can't get it work. It just display Mi logo and then jump to Fastboot. Most other GSIs won't work as well, it dosen't boot at all. So the only choose is BeastROM 1.6 for laurel_sprout @mdeejay.
BeastROM 1.6
unzip it, and what we need to do is flash system.img ONLY.
Code:
fastboot flash system system.img
And then reboot to TWRP, wipe data partition.
Edited:
You can find your vbmeta in fastboot ROM of laurus.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This command is NOT NEEDED if you can disable dm-verity via magisk. You can't boot without disabling dm-verity (stuck on Logo). I don't know how it works. Need some help from devs.
3. Flash Magisk
You HAVE TO flash magisk, or it will stuck on boot animation.
You can do it by "Install Root" in Advanced of TWRP.
Or do it manually by flash Magisk.
4. Flash GApps (Optional)
OpenGApps
Just Flash it in TWRP, nothing more to say. Maybe you need to wipe data again.
I think everything is perfect for now, execpt it's Android 9 instead of 10. At least you can get most of features in Mi A3 and get rid of stupid MIUI
Some stupid idea: for people who wanna get MIUI in laurel_sprout, you can flash system.img in fastboot of laurus. I don't think it will work but it worth trying.
I've tried flashing laurel_sprout image into laurus, it can boot, but it won't work. Screen blinks and it get stuck on welcome page, touching works though.
Fastboot of laurus
Fastboot of laruel_sprout
Click to expand...
Click to collapse
First of all, tks for getting the first not official rom for the cc9e! Really appreciated.
Can you please confirm if this rom has Spanish Language included? Tks!
im confirm,there is espanol language and almost all popular,and work like a charm
oska3 said:
im confirm,there is espanol language and almost all popular,and work like a charm
Click to expand...
Click to collapse
Tks buddy! I will try it
Thankyou heaps for for this post.
I will be back in 168hrs (mi unlock) to attempt （⌒▽⌒）.
help
1)i flash fastboot stocck laurus rom
2)then flash twrp (always use files that you provide in this thread)
3)then flash system.img
4)then reboot to twrp >format data>yes
5)then install magisk 19.4 and pico gapps
6)then repeat format data and reboot
but always phone stuck on "G" logo booting
also try to flash vbmeta from stock after 4)
also try without gapps
also try vbmeta from beast 1.6
nothing
please help me
what i do wrong
sorry for my bad english
Some of us Mi A3 users want to use Miui 11 from CC9e, how possible is that. Could you give a tutorial?
Android one is snappy on mi a3, with 6g ram on CC9e it will be really smooth.
Xiaomi Mi A3 - Неофициальные прошивки miui 10 port,4pda
aleksbrain said:
1)i flash fastboot stocck laurus rom
2)then flash twrp (always use files that you provide in this thread)
3)then flash system.img
4)then reboot to twrp >format data>yes
5)then install magisk 19.4 and pico gapps
6)then repeat format data and reboot
but always phone stuck on "G" logo booting
also try to flash vbmeta from stock after 4)
also try without gapps
also try vbmeta from beast 1.6
nothing
please help me
what i do wrong
sorry for my bad english
Click to expand...
Click to collapse
Try to use the root in Advanced tab of TWRP.
mi cc9e can use stock rom of mi a3 without root, this mean bank app will work perfect
1- flash full rom with miflash (any lower version will not boot) http://bigota.d.miui.com/V10.2.13.0...FMCNXM_20190830.0000.00_9.0_cn_fc9f51f46d.tgz
2- download rom of mi a3, extract file system.img only
http://bigota.d.miui.com/V10.3.4.0....0.PFQMIXM_20190815.0000.00_9.0_00838b4c0e.tgz
3- go to fastboot and flash (vbmeta of micc9e)
fastboot flash system system.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
Related
Hi,
I have a problem with a Moto G4. I tried to root the device and think I f***** up a bit.
After successfully installing TWRP I tried to install SuperSu using adb sideload and afterwards the device wouldn't boot anymore. Only fastboot and the recovery are still working. If I try to boot the device it just turns off. A factory reset didn't help.
I tried installing a LineageOS but nothing changed. It still boots into fastboot.
Can anybody help?
squanch123 said:
Hi,
I have a problem with a Moto G4. I tried to root the device and think I f***** up a bit.
After successfully installing TWRP I tried to install SuperSu using adb sideload and afterwards the device wouldn't boot anymore. Only fastboot and the recovery are still working. If I try to boot the device it just turns off. A factory reset didn't help.
I tried installing a LineageOS but nothing changed. It still boots into fastboot.
Can anybody help?
Click to expand...
Click to collapse
I forgot to say that I at first didn't install supersu systemless.
After I noticed that the device wouldn't boot anymore I tried installing it again systemless.
squanch123 said:
I forgot to say that I at first didn't install supersu systemless.
After I noticed that the device wouldn't boot anymore I tried installing it again systemless.
Click to expand...
Click to collapse
Hmm, did you wipe your system and data in TWRP before flashing LineageOS? You do not require root to flash LineageOS, just an unlocked bootloader and a compatible TWRP recovery (taking care to note if you need the 32 bit or 64 bit TWRP recovery for the respective custom ROM).
Also, with rooting on our G4/Plus, if you are on stock Nougat, you must flash a custom kernel (e.g. ElementalX) before you root. You'll otherwise experience the boot failures you're experiencing. Thus, to root on stock Nougat, unlock bootloader, flash/boot TWRP, backup, then flash ElementalX, then flash SuperSU/magisk.
Without knowing the current state of your device, I would suggest re-flashing your device with the stock firmware. Can you remember what stock firmware you had on your device before rooting initially?
echo92 said:
Hmm, did you wipe your system and data in TWRP before flashing LineageOS? You do not require root to flash LineageOS, just an unlocked bootloader and a compatible TWRP recovery (taking care to note if you need the 32 bit or 64 bit TWRP recovery for the respective custom ROM).
Also, with rooting on our G4/Plus, if you are on stock Nougat, you must flash a custom kernel (e.g. ElementalX) before you root. You'll otherwise experience the boot failures you're experiencing. Thus, to root on stock Nougat, unlock bootloader, flash/boot TWRP, backup, then flash ElementalX, then flash SuperSU/magisk.
Without knowing the current state of your device, I would suggest re-flashing your device with the stock firmware. Can you remember what stock firmware you had on your device before rooting initially?
Click to expand...
Click to collapse
Hi, thanks for your reply
Yes, I wiped system data and cache before flashing lineage. I just tried it again and I am still stuck in fastboot.
Unfortunately I don't remember the stock firmware version. Should I just try to flush the custom kernel and supersu afterwards?
squanch123 said:
Hi, thanks for your reply
Yes, I wiped system data and cache before flashing lineage. I just tried it again and I am still stuck in fastboot.
Unfortunately I don't remember the stock firmware version. Should I just try to flush the custom kernel and supersu afterwards?
Click to expand...
Click to collapse
Hmm, did you know if the flash of LineageOS reported okay within TWRP? Just out of interest, which TWRP and which build of LineageOS are you flashing (e.g. are you using the 32 bit TWRP or 64 bit TWRP, and are you flashing the 32 or 64 bit Lineage OS)?
That's confusing that even pressing 'start' in fastboot reboots your device rather than booting, even with a custom ROM... What happens if you boot to TWRP and try to reboot via TWRP? Is there a system to boot to?
Without the stock system on your device, there's no point to re-flashing the custom kernel/SuperSU, since you should have LineageOS on your device. Do you have a TWRP backup you could restore before you tried to root? If not, then what's your device model number (and if you can remember it, what software channel you're on, e.g. retus, reteu etc). ?
echo92 said:
Hmm, did you know if the flash of LineageOS reported okay within TWRP? Just out of interest, which TWRP and which build of LineageOS are you flashing (e.g. are you using the 32 bit TWRP or 64 bit TWRP, and are you flashing the 32 or 64 bit Lineage OS)?
That's confusing that even pressing 'start' in fastboot reboots your device rather than booting, even with a custom ROM... What happens if you boot to TWRP and try to reboot via TWRP? Is there a system to boot to?
Without the stock system on your device, there's no point to re-flashing the custom kernel/SuperSU, since you should have LineageOS on your device. Do you have a TWRP backup you could restore before you tried to root? If not, then what's your device model number (and if you can remember it, what software channel you're on, e.g. retus, reteu etc). ?
Click to expand...
Click to collapse
Yes, everything was ok with the flash.
I am using lineage-14.1-20180516-nightly-athene-signed and twrp-3.2.1-0-athene. I didn't see any options to choose between 32 and 64 bit. (Download pages: https://download.lineageos.org/athene#!name https://eu.dl.twrp.me/athene/)
It doesn't matter how I try to boot (powerbutton, fastboot, recovery) I always directly end up in fastboot.
No I don't have a backup. When I got the device it was resetted so I saw no point in making one :/ It is an XT1622 and it should be reteu.
squanch123 said:
Yes, everything was ok with the flash.
I am using lineage-14.1-20180516-nightly-athene-signed and twrp-3.2.1-0-athene. I didn't see any options to choose between 32 and 64 bit. (Download pages: https://download.lineageos.org/athene#!name https://eu.dl.twrp.me/athene/)
It doesn't matter how I try to boot (powerbutton, fastboot, recovery) I always directly end up in fastboot.
No I don't have a backup. When I got the device it was resetted so I saw no point in making one :/ It is an XT1622 and it should be reteu.
Click to expand...
Click to collapse
Okay, so they should both be 32 bit, so no worries there. There do seem to be a few reports of boot issues on the more recent official LineageOS builds https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101/page280 but I don't know if they are still existing on the build you've flashed.
As it's likely your device has been reset when you flashed LineageOS (I don't know if there are still files on your internal storage, which you can view in TWRP, so back up if you do have files), you may wish to look into a stock firmware flash. Here's the April 2018 NPJS25.93-14-18 firmware, which appears to be the build released to EU devices: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not have to re-lock your bootloader if you don't wish to - if you wish to leave your bootloader unlocked, then flash the stock firmware via fastboot with the following flashing commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Flashing these files via ADB should put a fresh copy of the latest firmware onto your device, which should then boot. If it does boot, then you can proceed with rooting (flash TWRP, then back up, then flash ElementalX or vegito, then flash SuperSU or magisk).
echo92 said:
Okay, so they should both be 32 bit, so no worries there. There do seem to be a few reports of boot issues on the more recent official LineageOS builds https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101/page280 but I don't know if they are still existing on the build you've flashed.
As it's likely your device has been reset when you flashed LineageOS (I don't know if there are still files on your internal storage, which you can view in TWRP, so back up if you do have files), you may wish to look into a stock firmware flash. Here's the April 2018 NPJS25.93-14-18 firmware, which appears to be the build released to EU devices: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not have to re-lock your bootloader if you don't wish to - if you wish to leave your bootloader unlocked, then flash the stock firmware via fastboot with the following flashing commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Flashing these files via ADB should put a fresh copy of the latest firmware onto your device, which should then boot. If it does boot, then you can proceed with rooting (flash TWRP, then back up, then flash ElementalX or vegito, then flash SuperSU or magisk).
Click to expand...
Click to collapse
Thanks for the help!
I can boot the stock rom and I have root access. However if I start or shut down the device it goes to fastboot. From there I can boot or shut down the device and everything seems to work Do you know how I can boot directly without fastboot?
squanch123 said:
Thanks for the help!
I can boot the stock rom and I have root access. However if I start or shut down the device it goes to fastboot. From there I can boot or shut down the device and everything seems to work Do you know how I can boot directly without fastboot?
Click to expand...
Click to collapse
Hmm, try booting back to the bootloader, attach your device to your computer, then open ADB. In ADB, type 'fastboot oem fb_mode_clear' without the quotes. Press enter to submit, then reboot and see if your device boots to system rather than to fastboot.
This command should clear fastboot mode (though useful when flashing).
echo92 said:
Hmm, try booting back to the bootloader, attach your device to your computer, then open ADB. In ADB, type 'fastboot oem fb_mode_clear' without the quotes. Press enter to submit, then reboot and see if your device boots to system rather than to fastboot.
This command should clear fastboot mode (though useful when flashing).
Click to expand...
Click to collapse
Yes that worked
Thank you very much for your help :victory:
every time I do the procedure to install the gcam with temporary root, when uninstalling the magisk, my mi a1 gets stuck in the "no command" screen, I saw in several sites that this happens when the magisk does not make a backup correct boot.img, has anyone gone through this?
die.henrique said:
every time I do the procedure to install the gcam with temporary root, when uninstalling the magisk, my mi a1 gets stuck in the "no command" screen, I saw in several sites that this happens when the magisk does not make a backup correct boot.img, has anyone gone through this?
Click to expand...
Click to collapse
Mine too, had to flash the original rom with mi flash. Get the og boot.img then when you're in fastboot mode type : "fastboot boot boot.img" the boot.img needs to be the stock unpatched boot image
emiljano539 said:
Mine too, had to flash the original rom with mi flash. Get the og boot.img then when you're in fastboot mode type : "fastboot boot boot.img" the boot.img needs to be the stock unpatched boot image
Click to expand...
Click to collapse
but will not this reset the device? can I flash the stock boot.img without erasing the data?
die.henrique said:
but will not this reset the device? can I flash the stock boot.img without erasing the data?
Click to expand...
Click to collapse
Yes, but you can keep the data by selecting to flash only the system.
And you can also flash only the stock boot.img with command "fastboot flash boot boot.img"
emiljano539 said:
Yes, but you can keep the data by selecting to flash only the system.
And you can also flash only the stock boot.img with command "fastboot flash boot boot.img"
Click to expand...
Click to collapse
Omg, thanks for the answers, just one more thing, the boot.img do I have to download from the internet or do a backup of my current device?
die.henrique said:
Omg, thanks for the answers, just one more thing, the boot.img do I have to download from the internet or do a backup of my current device?
Click to expand...
Click to collapse
You should download the boot.img for mi a1 which corresponds with your update. For ex. boot.img of january rom.
device not found in adb fasboot after uninstall magisk
emiljano539 said:
Mine too, had to flash the original rom with mi flash. Get the og boot.img then when you're in fastboot mode type : "fastboot boot boot.img" the boot.img needs to be the stock unpatched boot image
Click to expand...
Click to collapse
[HELP] after uninstalling magisk, my mi a2 stuck at no command and does not found in adb (device not listed in fastboot). what should i do? i want to flashboot.
caan90 said:
[HELP] after uninstalling magisk, my mi a2 stuck at no command and does not found in adb (device not listed in fastboot). what should i do? i want to flashboot.
Click to expand...
Click to collapse
Because you have lost the stock boot.img. find the stock boot img of your patch then flash it via fastboot directly
emiljano539 said:
Because you have lost the stock boot.img. find the stock boot img of your patch then flash it via fastboot directly
Click to expand...
Click to collapse
Thank you so much... it work.. my mi a2 just come back to life..
caan90 said:
Thank you so much... it work.. my mi a2 just come back to life..
Click to expand...
Click to collapse
I'm glad it worked. Make sure you leave a like in my comment if it was useful . Peace
my mi a2 is not detect in adb and in fastboot too what can i do
Hello,
I want to install the twrp-3.3.1-12-davinci-mauronofrio.img with modified_vbmeta.img. I have installed MIUI Global 11.0.4!
It´s not working, I get always a bootloop
why it´s not working?? Need help, thanks
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery twrp.img
Works for me every time. Verity breaks your boot for security reasons, so it needs disabled.
xer0o0x said:
Hello,
I want to install the twrp-3.3.1-12-davinci-mauronofrio.img with modified_vbmeta.img. I have installed MIUI Global 11.0.4!
It´s not working, I get always a bootloop
why it´s not working?? Need help, thanks
Click to expand...
Click to collapse
Or just use the official TWRP.
No need to modify anything:
https://eu.dl.twrp.me/davinci/
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 8 in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 8 to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 8
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash LOGO LOGO.img
fastboot flash modem modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
Branded devices is for example a Chinese version with HydrogenOS to which OxigenOS has been installed? If so, how can a branded device be recovered?
Thanks
Hi guys, i'm here again to ask for your support, actually with android 10 Google introduced a lot of changing, from dynamic partitions to the new keymaster 4 encryption/decryption. Teamwin is working hard to update TWRP but they will still take some time. Currently some things already work but there are difficulties in bringing them to the OnePlus 8/8 Pro, for example decryption already works but creates some problems on the OnePlus devices. That's why I decided to create a Paypal moneybox to be able to bring you the latest updates in the shortest time possible. As I have previously done, I assure you of a support of at least 2 years (within the limits of my possibilities). In addition to the TWRP I will improve the fastboot roms and add OnePlus 8/8 Pro to my TOOL ALL IN ONE (and maybe I will also bring the RevengeOS). By getting hold of a OnePlus 8 or 8 Pro I will also be able to improve the TWRP for OnePlus 7T and 7T Pro.
OnePlus 8/8 Pro PayPal MoneyBox: https://www.paypal.com/pools/c/8pfrIOL3Qa
If you are unable to participate in the PayPal moneybox, you can make a normal donation (perhaps specifying that it is for the moneybox), however all private donations that I will receive for this or other projects will be included in the moneybox.
Private PayPal Donations: https://www.paypal.me/MauronofrioTool
Why after flash it, it boot up to Qualcomm crashdump mode and how to fix?
sakun-ice said:
Branded devices is for example a Chinese version with HydrogenOS to which OxigenOS has been installed? If so, how can a branded device be recovered?
Thanks
Click to expand...
Click to collapse
I think unbranded devices mean the device bought from T-Mobile or Verizon. Nothing to do with chinese versiion flash oxygenOS, if I'm not wrong.
Can't seem to get this to work. I'm trying to flash a stock rom for my OnePlus 8 after bricking it during a rooting process.
The device' bootloader is obviously unlocked and i can get the phone into Fastboot mode and connected to my PC.
The only issue is when i execute the flash-all.bat file, it can't seem to flash any of the files and gives an error consisting of the message "FAILED (remote: 'Flashing is not allowed for Critical Partitions').
What to do guys? Can anyone help me out.
Does anyone know where to find mobile oneplus 8 5g tmobile from mine is bricked I had same error as post above
KJStar said:
Can't seem to get this to work. I'm trying to flash a stock rom for my OnePlus 8 after bricking it during a rooting process.
The device' bootloader is obviously unlocked and i can get the phone into Fastboot mode and connected to my PC.
The only issue is when i execute the flash-all.bat file, it can't seem to flash any of the files and gives an error consisting of the message "FAILED (remote: 'Flashing is not allowed for Critical Partitions').
What to do guys? Can anyone help me out.
Click to expand...
Click to collapse
Try to flash fastboot rom with "tool all in one),It worked for me.
I needed modem I forgot to fastboot reboot fastboot guy in post 6 that's all you need to do is reboot fastboot then flash all I was looking for different file
Never mind I fixed it by downloading ota and going to system updates in settings because fastboot won't flash to modem right
I am having issues flashing. flashing not allowed on critical partition. please help I tried to use the large address aware program but nothing has changed.
bluemoel said:
I am having issues flashing. flashing not allowed on critical partition. please help I tried to use the large address aware program but nothing has changed.
Click to expand...
Click to collapse
Make sure your on the latest update: 10.5.8
mauronofrio said:
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 8 in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 8 to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 8
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash LOGO LOGO.img
fastboot flash modem modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
Click to expand...
Click to collapse
Hi, do you know if patching with local update a Oxygen OS Europe release from a Global release may cause problems to the fingerprint? I have a IN2010 with the Global OxygenOS but I would like to switch to the European versione becasue I live in Italy like you
Why not flash reserve.img?
nnyd said:
Why not flash reserve.img?
Click to expand...
Click to collapse
Because it is placed in userdata and not in a dedicated partition
I have an issue trying to flash on fastboot. It's says I can't flash on critical partitions. Yes I know alot of people are saying that but what I haven't seen is this:
This is my problem:
Fastboot get device-info
(Bootloader) device unlocked:true
(Bootloader) device critical unlock: false
(Bootloader) charger screen enabled: true
I have already tried "fastboot flashing unlock_critical"
It says bootloader already unlocked. I then re lock bootloader which I know is not a good idea( reflash stock with msm tool) and it lock then I try unlock critical command again and it still says device critical unlock: false
i need help please ..
i tried this method not the latest version i tried the 10.5.4 global
so it gave me all failed and error to foramt and others
then it restart my phone to show me crashdump
what should i do ?
should i use latest version ?
i hope you replay fast .. thank you
Alucardo1 said:
i tried this method not the latest version i tried the 10.5.4 global
so it gave me all failed and error to foramt and others
then it restart my phone to show me crashdump
what should i do ?
should i use latest version ?
i hope you replay fast .. thank you
Click to expand...
Click to collapse
Try again with 10.5.7. When it reboot to recovery, let it continue to run till it reboots on its own.
Unbrick from fastboot method
I hope I can help someone since I spent the whole night trying various methods to unbrick my Oneplus 8 and only this one worked for me JUST FOR INTERNATIONAL VERSION
You must have the drivers installed (Adb & Fastboot)
You must have your phone with the bootloader unlocked
1.- Download the file
2.-Unzip it
inside you will find Flash-all.bat
3.-Enter Fastboot mode
4.-Double click on the Flash-all.bat command
5.-It will direct you to the recovery, select the English language and restart in fastboot mode so that the process continues, wait for it to finish flashing everything and ready, the phone restarts on the latest version
https://mega.nz/folder/8tpUSSrR#7wH4NX_ccr2a6Ub8LXpsEA
Donate Link to support my work
https://paypal.me/pakomorales?locale.x=es_XC
cannot relock bootloader on oneplus 8
bro thanks for fastboot room for oneplus 8,i flash your fastboot room 10.5.9 everthing ok,but i relocked to boot loader it the phone be correpted. what should i do ,
please help me.
Phone redmi 7a china variant. MIUI 12.5
My fathers phone suddenly bootloop in the middle of using, I use MI flash pro and flash using fastboot no luck, I used stock china rom miui 10, miui 12 global still no luck, i install TWRP 64 bit and flash recovery rom miui 12 and miui 10 still no luck i even flash custom PE still no luck , btw i use clean flashes wipe and format data. the phone just stock in redmi logo bootlooping, sometimes when i use fastboot flashes it work after i charge the phone but it wont last a couple of minutes and go black and bootloop again. i would like to ask what is wrong?, im not new in custom roms and phone tweakings but this trouble is pain.
My flash steps
NEW STEP for PINE only
1. format data and advance wipe vendor,internal,dalvik,data,system and cache
2. install rom and wipe cache, then format data again and reboot.
OLD STEP
1. advance wipe vendor,dalvik,data,system and cache
2. install rom wipe cache or skip and direct reboot.
download fastboot rom
Redmi 7A (pine) China Fastboot & Recovery ROM | XiaomiROM.com
Xiaomi Redmi 7A (pine) China official ROM, include stable, weekly and beta MIUI firmware which can be updated with Recovery and Fastboot (need mi …
xiaomirom.com
fextract and find vbmeta.img under images folder
Then
fastboot --disable-verity --disable-verification flash vbmeta C:\.../vbmeta.img
where "C:\.../vbmeta.img is replaced by the directory of vbmeta.img
LR7875 said:
download fastboot rom
Redmi 7A (pine) China Fastboot & Recovery ROM | XiaomiROM.com
Xiaomi Redmi 7A (pine) China official ROM, include stable, weekly and beta MIUI firmware which can be updated with Recovery and Fastboot (need mi …
xiaomirom.com
fextract and find vbmeta.img under images folder
Then
fastboot --disable-verity --disable-verification flash vbmeta C:\.../vbmeta.img
where "C:\.../vbmeta.img is replaced by the directory of vbmeta.img
Click to expand...
Click to collapse
thanks I'll try this..
LR7875 said:
download fastboot rom
Redmi 7A (pine) China Fastboot & Recovery ROM | XiaomiROM.com
Xiaomi Redmi 7A (pine) China official ROM, include stable, weekly and beta MIUI firmware which can be updated with Recovery and Fastboot (need mi …
xiaomirom.com
fextract and find vbmeta.img under images folder
Then
fastboot --disable-verity --disable-verification flash vbmeta C:\.../vbmeta.img
where "C:\.../vbmeta.img is replaced by the directory of vbmeta.img
Click to expand...
Click to collapse
btw , which first? do i flash the stock rom first then vbmeta.img ? thanks much appreciated.
Luffy83 said:
btw , which first? do i flash the stock rom first then vbmeta.img ? thanks much appreciated.
Click to expand...
Click to collapse
No no need flash stock ROM yet just flash the vbmeta, try flashing custom ROM and boot, if it does not work then try the stock rom
LR7875 said:
No no need flash stock ROM yet just flash the vbmeta, try flashing custom ROM and boot, if it does not work then try the stock rom
Click to expand...
Click to collapse
thanks ill try then, much appreciated
Luffy83 said:
thanks ill try then, much appreciated
Click to expand...
Click to collapse
I had the same problem. I explained what I did here: https://forum.xda-developers.com/t/...er-and-install-twrp-rom.4526205/post-87940671
I hope it helps if the method suggested by @LR7875 doesn't work haha