Related
OK, long story short. Came for the nexus 6 and nexus 6p to oneplus 3t. The 6p had to flash vendor.IMG after every new ROM flash. But what is this whole firmware thing in this device? I have tried to find answers before asking but, what should I DO and NOT DO to have a brick? Like, wanting to go from a nougat ROM to an Oreo ROM, but not sure how. And then if I wanted to go from a n/o ROM to a beta, not sure how...then if I wanted to downgrade from an o or beta ROM.......please help
Treat the OP3T pretty much the same as you would the Nexus 6. The only difference is, like you've discovered, that OnePlus provides firmware files rather than factory images.
The installation instructions for the different firmwares (stable and beta) are found in the first few posts of the respective threads:
https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
https://forum.xda-developers.com/oneplus-3t/how-to/coming-update-oos-based-7-1-t3564240
It's pretty much the same as flashing vendor image. OnePlus just simply offers Firmware images which flash the Modem and the Firmware.
If you're gonna be on OxygenOS and Custom OxygenOS ROMs then you wont need to worry about flashing the firmware. Some of the Custom ROMs such as Paranoid Android and PureFusionOS also flash the recommended firmware automatically.
However, others don't and require you to flash a particular fimware image manually. Usually the Firmware to be used would be mentioned on the ROM thread itself.
Once you've Unlocked the bootloader and flashed a custom recovery, The most common process for flashing ROMs which do not have an included firmwares goes as follows:
1. Reboot To Recovery
2. Wipe Cache & Dalvik Cache, System and Data Partitions
3. Flash Firmware
4. Flash ROM Zip
5. Flash GAPPS
6. Flash Magisk/SuperSU (Optional).
7. Reboot
And that's it.
That is the standard procedure for most of the ROMs, but, I'd advice reading the OP Instructions properly first in case theres anything different.
PS. For moving to Oreo from Nougat, follow the same, but be warned, If your current ROM is encrypted and the new one isn't you'll be locked out of your device until you flash the old ROM back OR wipe userdata with fastboot, which wipes the Internal Storage.
PPS. For moving from a Custom ROM to Oxygen OS, best way to go would be to flash the official recovery again and sideload the official ROM zip via ADB (In some cases, encryption still might cause the same issue as above)
Mizart said:
It's pretty much the same as flashing vendor image. OnePlus just simply offers Firmware images which flash the Modem and the Firmware.
If you're gonna be on OxygenOS and Custom OxygenOS ROMs then you wont need to worry about flashing the firmware. Some of the Custom ROMs such as Paranoid Android and PureFusionOS also flash the recommended firmware automatically.
However, others don't and require you to flash a particular fimware image manually. Usually the Firmware to be used would be mentioned on the ROM thread itself.
Once you've Unlocked the bootloader and flashed a custom recovery, The most common process for flashing ROMs which do not have an included firmwares goes as follows:
1. Reboot To Recovery
2. Wipe Cache & Dalvik Cache, System and Data Partitions
3. Flash Firmware
4. Flash ROM Zip
5. Flash GAPPS
6. Flash Magisk/SuperSU (Optional).
7. Reboot
And that's it.
That is the standard procedure for most of the ROMs, but, I'd advice reading the OP Instructions properly first in case theres anything different.
PS. For moving to Oreo from Nougat, follow the same, but be warned, If your current ROM is encrypted and the new one isn't you'll be locked out of your device until you flash the old ROM back OR wipe userdata with fastboot, which wipes the Internal Storage.
PPS. For moving from a Custom ROM to Oxygen OS, best way to go would be to flash the official recovery again and sideload the official ROM zip via ADB (In some cases, encryption still might cause the same issue as above)
Click to expand...
Click to collapse
That was very informative, thank you!!! Just one more question tho. What would happen if I didn't flash the correct firmware? Like, there is a RR ROM with custom sultan or something that looks like it needs a beta firmware, I'm not in beta firmware, so would I have any issues?
jamescable said:
That was very informative, thank you!!! Just one more question tho. What would happen if I didn't flash the correct firmware? Like, there is a RR ROM with custom sultan or something that looks like it needs a beta firmware, I'm not in beta firmware, so would I have any issues?
Click to expand...
Click to collapse
I'm not entirely sure but in most cases the ROM would simply refuse to flash. Like for RR, if you don't flash a correct firmware then the flashing returns an "Error 7" and the installation stops. But even if it does flash through, it would either not connect to a network or get stuck in a bootloop, but nothing too serious which you can't rectify.
Hi, fellows,
High need urgently help!
I was on stock Pie with all critical unlock, bootloader unlock and root too ... So I decide to change to a costume firmware.
Now I'm on twrp-installer-3.3.0-0-jasmine_sprout.zip with all the partitions decrypted and when I tried to flash a custom firmware like Havoc OS v2.4 or Pixel Experience ... Happen this error.
Step 1/2
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Havoc-OS-v2.4-20190502-jasmine_sprout-Official.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
Anyone can help me?
Thanks
nnexuss said:
Hi, fellows,
High need urgently help!
I was on stock Pie with all critical unlock, bootloader unlock and root too ... So I decide to change to a costume firmware.
Now I'm on twrp-installer-3.3.0-0-jasmine_sprout.zip with all the partitions decrypted and when I tried to flash a custom firmware like Havoc OS v2.4 or Pixel Experience ... Happen this error.
Anyone can help me?
Thanks
Click to expand...
Click to collapse
Try to use twrp 3.2.3 and follow this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
mma_1494 said:
Try to use twrp 3.2.3 and follow this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
I already tried this version but not the guide...
I'll try when I arrived at home
nnexuss said:
Hi, fellows,
High need urgently help!
I was on stock Pie with all critical unlock, bootloader unlock and root too ... So I decide to change to a costume firmware.
Now I'm on twrp-installer-3.3.0-0-jasmine_sprout.zip with all the partitions decrypted and when I tried to flash a custom firmware like Havoc OS v2.4 or Pixel Experience ... Happen this error.
Anyone can help me?
Thanks
Click to expand...
Click to collapse
Their is only one way to recover your phone just follow this step
1. Flash stock firmware(stock rom) vie fastboot using MI Flasher
this is bring back you phone and if you want to install custom rom then follow this
1. boot twrp
2. wipe all the data from slot A and B partition(internal storage as per you choice )
3. boot to slot B and copy past the custom rom file in slot B
4. flash that rom and boot to slot B and then flash Gaaps and other staff you want
5. reboot and enjoy.
NOTE: changing the slot require reboot twrp in simple words every time you change the slot you have to reboot the phone and boot again to twrp..
i hope this will work for you..:good:
If you don't have stock flash file then try from step 2. see whether it will work or not otherwise follow from beginning.
facing the same issue
i tried the same and getting the same error. even the twrp3.2.3.0 never worked while tried to flash that one more than 20 times, after flashing 3.2.3.0 my phone either boots normally or it gets completely power off. and if i try to boot into recovery using volume keys and power key , it boots in stock recovery. please help
Mine its ok now... i don´t know whats happen but suddenly it flash withou any problem.
See if it helps...
Make sure you're running a proper working Recovery
Flashing instructions:
Dirty flash (assuming you have rom on slot A):
1. Download all required files and place them to internal memory (ROM, twrp installer, gapps, magisk, ..)
2. Boot twrp to slot B and flash ROM and twrp installer
3. Reboot twrp to slot A and flash gapps (optional magisk)
4. Now reboot to system
Clean flash (assuming you have rom on slot A):
1. Download all required files and place them to internal memory (ROM, twrp installer, gapps, magisk, ..)
2. Boot twrp to A slot and wipe everything except for internal
3. Reboot twrp to B slot and flash ROM and twrp installer
4. Reboot twrp to slot A and flash gapps (optional magisk)
5. Now reboot to system
If you are coming from stock:
1. Download latest TWRP installer and image
2. Open cmd and type fastboot boot twrp.img (change twrp to its actual name)
3. You should be on slot A in twrp, if not change it and reboot to bootloader and repeat step 2.
4. Format data
5. Now follow instruction for clean flash
Click to expand...
Click to collapse
Credits: Fullbustah
I have this issue and none of the steps worked.
I got my device 2 days back and it was in Oreo. I tried to update to pie but the update keep failing. I unlocked the phone and flash latest official fastboot rom using mi_flash and installed magisk using this guide:
https://forum.xda-developers.com/mi-a2/how-to/unlock-bootloader-n-root-magisk-easy-t3856800
Everything went smooth.
Today I tried to go further and instal PE rom using this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Everything goes smooth until I boot to TWRP and try to flash the rom. It gave the error posted by OP. I have tried the following things since:
1. Try another two roms, same issue
2. Flash stock Pie using mi_flash then temp boot to TWRP latest version from 'a' partition, wipe everything, then boot from 'b' partition, wipe everything, try to flash. Same issue.
3. Install TWRP (it installed without any issue), reboot to installed TWRP, flash rom, same issue.
4. Try to flash with 'a' as active. Same issue.
5. All other possible combos (i think) of the above. In all cases everything goes as expected until I try to flash the rom.
Currently I have flashed the factory image back. Any help will be greatly appreciated.
Device variant: XT19121-2 James
Chipset: MSM8920
After repeated failed flashes I am on stock firmware using this guide. Phone boots and works normally right now, but I can't seem to flash any Custom ROMs on to my phone. I was using this post to flash Lineage OS 15.1, which worked successfully at first, but the WiFi wasn't working so I reflashed it. It still didn't work so I did it again, wiping Dalvik/Cache too. After the second flash attempt, my phone began to only flicker on and off. I made sure to always clean flash, factory resetting, wiping Cache and Dalvik, even formatting data, but no matter what I do it doesn't work. Also attempted other GSI images (arm, A-only) like AOSP, ResurrectionRemix and phhusson's Lineage OS 15.1 But they all failed too. I am using TWRP for James v 3.3.1 although I did also try other TWRP images like v 3.2.1 . But it makes no difference. Also used Magisk v19 like some guides suggested but whether I have Magisk or not, it doesn't work. Even made sure to push the fstab.qcom file to /vendor. Anytime a Custom ROM is flashed whether zip or GSI img it goes past the initial "bad key" or "N/A" screen and starts flickering on and off. Bootloader and TWRP works fine, but that's about it. Everytime a flash fails I go back to stock firmware (which always works) and try another ROM. I wonder why the first attempt worked but doesn't anymore even if I mirror the exact steps I took from stock. If anyone has any solutions I would be really grateful. Let me know if you need any more information.
have you taken any recent OTA updates?
mikeshutte said:
have you taken any recent OTA updates?
Click to expand...
Click to collapse
Nope. Still on the 8.0.0 version the stock firmware comes in.
tkhan7916 said:
Nope. Still on the 8.0.0 version the stock firmware comes in.
Click to expand...
Click to collapse
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
---------- Post added at 10:09 PM ---------- Previous post was at 09:59 PM ----------
tkhan7916 said:
Nope. Still on the 8.0.0 version the stock firmware comes in.
Click to expand...
Click to collapse
mikeshutte said:
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
Click to expand...
Click to collapse
I also just noticed you are using the latest version of TWRP 3.3.1. I'm not sure if you originally rooted and installed TWRP with the original patched version by Cody or not, but if so make sure with the new version that you format your data partition to f2fs. As this will ensure correct mounting of the data partition.
mikeshutte said:
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
Click to expand...
Click to collapse
Followed these steps exactly, including formatting the data partition to f2fs, and the same problem still persists. Screen just keeps turning on and off in a loop without booting into the ROM. I downloaded the Lineage OS 16.0 GSI A-only Arm version for reference.
I am having the same issue
Using XT1921-1
Latest TWRP
Have tried LOS 15, LOS 16, AOSP 8.1, AOSP 9.0
Have tried flashing in fastboot and TWRP
Have tried every combo of wipe/factory reset/format data and magisk flash possible
have tried stock recovery, have tried no verity, have tried stock boot.img
nothing works. only able to produce powered on (black and blank) screen that turns on and off for a minute before returning to bootloader
PLEASE HELP
think i might need a 8.0 GSI but cant find one anywhere
I eventually got RR to boot on the james xt-1921-3 I installed XT1921-3_JAMES_T_MPCS_8.0.0_OCPS27.91-150-5-1-3_cid21 as a base, then used boot and vendor partitions from JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC and it finally worked.
tkhan7916 said:
Followed these steps exactly, including formatting the data partition to f2fs, and the same problem still persists. Screen just keeps turning on and off in a loop without booting into the ROM. I downloaded the Lineage OS 16.0 GSI A-only Arm version for reference.
Click to expand...
Click to collapse
Message me, I'll host a TWRP backup for the XT-1921-3 that boots RR 6.1
Download the file from this post https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 , then using fastboot, flash the vendor and boot img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
then boot into recovery and flash the file from that post to disable dm-verity and force encrytion, after that flash magisk, then reboot to bootloader, at command prompt-
fastboot erase userdata
fastboot erase cache
fastboot reboot
that should get you booted - profit
mrbox23 said:
Message me, I'll host a TWRP backup for the XT-1921-3 that boots RR 6.1
Click to expand...
Click to collapse
Do you still have that back up by any chance and could ypu send it to me?
Since in my last post I made a complete mess out of my first time trying to root my K20 and install lineage I wanted to my make a separate post so that I can list all the steps I need to take to correctly setup my phone how I want it.
What I actually want
A rooted device
Lineage OS
Minimal excess files (A clean Install)
Current Steps
Unlock and flash recovery
Backup
Format Data! (It's important if you come from Miui)
Install Q Firmware + vendor
Install LineageOS followed by gapps
Reboot into system and setup device.
Reboot into recovery and flash magisk
Profit???
Feel free to tell me how stupid I am and what I need to add to the list or steps I should take to make this process better.
I also dont know if its possible to get recovery and rom on android 10 versions.
Thanks
Did these steps not work?
Sent from my Redmi K20 Pro using Tapatalk
BJack0 said:
Since in my last post I made a complete mess out of my first time trying to root my K20 and install lineage I wanted to my make a separate post so that I can list all the steps I need to take to correctly setup my phone how I want it.
What I actually want
A rooted device
Lineage OS
Minimal excess files (A clean Install)
Current Steps
Flash a custom recovery
Create a backup
Root???
Install LineageOS
Profit???
Feel free to tell me how stupid I am and what I need to add to the list or steps I should take to make this process better.
Thanks
Click to expand...
Click to collapse
1. Unlock and flash recovery
2. Backup
3. Format Data! (It's important if you come from Miui)
4. Install Q Firmware + vendor
5. Install LineageOS followed by gapps
6. Reboot into system and setup device.
7. Reboot into recovery and flash magisk
You could also check LOS thread: Here and here
Remember:
Chinese firmware: Widevine L3 and NFC support
Indian firmware: Widevine L1 but no NFC support
ishaqtkr said:
Did these steps not work?
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
They may work as it but I was just wondering if anyone could go into more detail or if there was a better approach and from what Kollachi said there clearly is a better way that what I said.
Since I'm in stock ROM and haven't ever flashed AOSP ROM in this phone I'll just back off lol
Sent from my Redmi K20 Pro using Tapatalk
Kollachi said:
1. Unlock and flash recovery
2. Backup
3. Format Data! (It's important if you come from Miui)
4. Install Q Firmware + vendor
5. Install LineageOS followed by gapps
6. Reboot into system and setup device.
7. Reboot into recovery and flash magisk
Click to expand...
Click to collapse
I like the details steps but I have a few questions.
(Unlock and flash recovery) From what I can tell there are two recovery's Orange fox and TWRP
(Format data) Just format data or are there other sections I should format/wipe
(Install Q Firmware + Vendor) I have no idea what Q firmware is or what vendor you are referring to
(Install Lineage + gapps) Is there a specific version from the Mi 9T pro since the official site doesn't list it
Any of the two recoveries will work. Q firmware means Android Q. Wile data/cache dalvik that's it. Regarding firmware, there's a clear topic of Lineage OS in K20 Pro forum which is still in unofficially state
Sent from my Redmi K20 Pro using Tapatalk
BJack0 said:
I like the details steps but I have a few questions.
(Unlock and flash recovery) From what I can tell there are two recovery's Orange fox and TWRP
(Format data) Just format data or are there other sections I should format/wipe
(Install Q Firmware + Vendor) I have no idea what Q firmware is or what vendor you are referring to
(Install Lineage + gapps) Is there a specific version from the Mi 9T pro since the official site doesn't list it
Click to expand...
Click to collapse
1. You can take what you want. Orangefox is based on TWRP.
2. Format data is needed if you come from miui. If you did it you are good to go. But it wouldn't be false to wipe system, dalvic, cache
3.https://downloads.akhilnarang.me/MIUI/raphael/ --> Take 10.4.6.0 or 10.4.8.0 (Android 10 = Q)
4. No there is no specific version.
BJack0 said:
I like the details steps but I have a few questions.
(Unlock and flash recovery) From what I can tell there are two recovery's Orange fox and TWRP
(Format data) Just format data or are there other sections I should format/wipe
(Install Q Firmware + Vendor) I have no idea what Q firmware is or what vendor you are referring to
(Install Lineage + gapps) Is there a specific version from the Mi 9T pro since the official site doesn't list it
Click to expand...
Click to collapse
I would recommend the latest TWRP from here
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
The dev is an official TWRP dev, so this version, or something very close to this, is likely to become official in the future.
OrangeFox is a heavily modified TWRP and has a lot of added functionality specific to MIUI. If you wanted to stay on stock MIUI, but debloat and have root, etc. then OF would be the better choice, as it has functionality that lets it play nicely with MIUI (it can remain installed when OTA updates are installed)
As someone new to flashing on Android, I would suggest downloading a 10.4.x fastboot ROM from the site I pointed to in your other post, then follow the same procedure to flash the ROM.
Make your choice based on Kollachi's info and what's important to you (HD Netflix - choose Indian, or a working NFC - choose Chinese)
However you MUST change the flash option to 'clean all'.
At this point you've got a nice squeaky clean starting point.
Boot into the ROM at least once, though it's not necessary to go through all the setup.
After that follow Kollachi's steps but you can now ignore the step to flash vendor and firmware as it's all part of the fastboot ROM already flashed.
Wipe cache and dalvik, format data.
There is no official LOS for this phone yet. Hopefully it will go official in the future.
For now just get the current Android 10 based LOS from here.
https://forum.xda-developers.com/k20-pro/development/rom-lineageos-17-0-t3976469/post80406191
Robbo.5000 said:
I would recommend the latest TWRP from here
The dev is an official TWRP dev, so this version, or something very close to this, is likely to become official in the future.
OrangeFox is a heavily modified TWRP and has a lot of added functionality specific to MIUI. If you wanted to stay on stock MIUI, but debloat and have root, etc. then OF would be the better choice, as it has functionality that lets it play nicely with MIUI (it can remain installed when OTA updates are installed)
As someone new to flashing on Android, I would suggest downloading a 10.4.x fastboot ROM from the site I pointed to in your other post, then follow the same procedure to flash the ROM.
Make your choice based on Kollachi's info and what's important to you (HD Netflix - choose Indian, or a working NFC - choose Chinese)
However you MUST change the flash option to 'clean all'.
At this point you've got a nice squeaky clean starting point.
Boot into the ROM at least once, though it's not necessary to go through all the setup.
After that follow Kollachi's steps but you can now ignore the step to flash vendor and firmware as it's all part of the fastboot ROM already flashed.
Wipe cache and dalvik, format data.
There is no official LOS for this phone yet. Hopefully it will go official in the future.
For now just get the current Android 10 based LOS from here.
Click to expand...
Click to collapse
When ever I think I have the process memories and I follow the steps on my screen I still somehow **** this up and I cant understand how.
My current steps include
Flash the fastboot with the ROM that you linked me in my first post
Flash the recovery with TWRP (Every time I have then tried going back into TWRP is failed to work and prompted the original MIUI recovery)
Install the TWRP zip from custom recovery to try and fix the issue above (Only had this work once on orangefox and then never had success again)
So now I try to just flash the recovery and boot to it using CMD and it works fine
Move the lineageOS files from my PC to the phone SDCard
If I wipe data and the caches as suggested then the lineageOS zip is now go and I am back to flashing the fastboot ROM to restart the process
I know this might seem like im either stupid or just not getting it but could you or anyone else please make a bullet pointed list with links to what I have to download in order to actually achieve this since I cant do anything correctly even when trying to follow the steps.
(Im going to sleep since I have been trying to do this for hours now and I will check reply's in the morning.
Thanks for the help so far EVERYONE
BJack0 said:
When ever I think I have the process memories and I follow the steps on my screen I still somehow **** this up and I cant understand how.
My current steps include
Flash the fastboot with the ROM that you linked me in my first post
Flash the recovery with TWRP (Every time I have then tried going back into TWRP is failed to work and prompted the original MIUI recovery)
Install the TWRP zip from custom recovery to try and fix the issue above (Only had this work once on orangefox and then never had success again)
So now I try to just flash the recovery and boot to it using CMD and it works fine
Move the lineageOS files from my PC to the phone SDCard
If I wipe data and the caches as suggested then the lineageOS zip is now go and I am back to flashing the fastboot ROM to restart the process
I know this might seem like im either stupid or just not getting it but could you or anyone else please make a bullet pointed list with links to what I have to download in order to actually achieve this since I cant do anything correctly even when trying to follow the steps.
(Im going to sleep since I have been trying to do this for hours now and I will check reply's in the morning.
Thanks for the help so far EVERYONE
Click to expand...
Click to collapse
I just told you what I have done and I'm running it so far without issues.
Robbo just said you should flash the whole Chinese or indian rom but I don't like his steps because:
1. File is much bigger
2. MiFlash is just meh
3. If you forgot to change the flash process you are bricked if you don't take the correct firmware for your phone.
Default option in Miflash is set to "Clean all and lock". Every time you use it, you will need to change it into "clean all" or something other.
Kollachi said:
I just told you what I have done and I'm running it so far without issues.
Robbo just said you should flash the whole Chinese or indian rom but I don't like his steps because:
1. File is much bigger
2. MiFlash is just meh
3. If you forgot to change the flash process you are bricked if you don't take the correct firmware for your phone.
Default option in Miflash is set to "Clean all and lock". Every time you use it, you will need to change it into "clean all" or something other.
Click to expand...
Click to collapse
Yes flashing the whole fastboot ROM does add the risk, if you forget to change the flash option, but you are guaranteed a clean slate and so less likely to have any niggling issues that nobody else has. I would bet large sums of money that many of the issues you see on here, where only one person has some problem and everyone else is fine, would be solved by fastboot flashing MIUI before installing the ROM of choice.
If you know what you're doing and know when you'll be OK with what you've got and know when it's best to start clean, then going with the vendor and firmware is easier.
But if your unsure and new to flashing on Android phones, I will always suggest go with the overkill and know you've got the clean slate to start with.
---------- Post added at 10:56 AM ---------- Previous post was at 10:36 AM ----------
BJack0 said:
When ever I think I have the process memories and I follow the steps on my screen I still somehow **** this up and I cant understand how.
My current steps include
Flash the fastboot with the ROM that you linked me in my first post
Flash the recovery with TWRP (Every time I have then tried going back into TWRP is failed to work and prompted the original MIUI recovery)
Install the TWRP zip from custom recovery to try and fix the issue above (Only had this work once on orangefox and then never had success again)
So now I try to just flash the recovery and boot to it using CMD and it works fine
Move the lineageOS files from my PC to the phone SDCard
If I wipe data and the caches as suggested then the lineageOS zip is now go and I am back to flashing the fastboot ROM to restart the process
I know this might seem like im either stupid or just not getting it but could you or anyone else please make a bullet pointed list with links to what I have to download in order to actually achieve this since I cant do anything correctly even when trying to follow the steps.
(Im going to sleep since I have been trying to do this for hours now and I will check reply's in the morning.
Thanks for the help so far EVERYONE
Click to expand...
Click to collapse
It's sounds like the main issue is stock recovery is being restored. This is something that MIUI will do when it boots up.
When you first install TWRP you cannot boot into MIUI before booting to TWRP as you instantly lose TWRP. So you need to boot into TWRP first in order to do something to prevent it being overwritten.
Options are
1
Code:
fastboot boot TWRP.img
2 Use the button combo whilst still in fastboot - power and vol+, hold both until the phone vibrates and the initial logo appears.
Now to keep TWRP you need to either flash a custom ROM, flash Magisk or flash the dm-verity script.
In your case you want to flash LOS, so now you've booted into TWRP go ahead and continue with the steps given.
Also, wait until after you've formatted data before copying everything over. You can access the phone as an MTP device when in TWRP, so you'll be able to connect it to a PC and drag everything across, or you can stick everything on a USB OTG pen, if you have one, TWRP can read data from them too.
It's sounds like the main issue is stock recovery is being restored. This is something that MIUI will do when it boots up.
When you first install TWRP you cannot boot into MIUI before booting to TWRP as you instantly lose TWRP. So you need to boot into TWRP first in order to do something to prevent it being overwritten.
Options are
1
Code:
fastboot boot TWRP.img
2 Use the button combo whilst still in fastboot - power and vol+, hold both until the phone vibrates and the initial logo appears.
Now to keep TWRP you need to either flash a custom ROM, flash Magisk or flash the dm-verity script.
In your case you want to flash LOS, so now you've booted into TWRP go ahead and continue with the steps given.
Also, wait until after you've formatted data before copying everything over. You can access the phone as an MTP device when in TWRP, so you'll be able to connect it to a PC and drag everything across, or you can stick everything on a USB OTG pen, if you have one, TWRP can read data from them too.
Click to expand...
Click to collapse
The exact problem I have is that I cant transfer any files to the device after formatting the data. I follow the steps correctly and I get into TWRP successfully and then everyone has told me to format the data then install lineage but I cant install the OS if formatting the data removes it.
Get device into fastboot
Flash revocery with TWRP
power the device off
hold volume up and power
boot into custom recovery
format data
move lineageOS onto my device
install lineageOS
reboot
done.
This is the list of exact actions I am doing with no results is there something I am missing or something that is in the wrong order.
BJack0 said:
The exact problem I have is that I cant transfer any files to the device after formatting the data. I follow the steps correctly and I get into TWRP successfully and then everyone has told me to format the data then install lineage but I cant install the OS if formatting the data removes it.
Get device into fastboot
Flash revocery with TWRP
power the device off
hold volume up and power
boot into custom recovery
format data
move lineageOS onto my device
install lineageOS
reboot
done.
This is the list of exact actions I am doing with no results is there something I am missing or something that is in the wrong order.
Click to expand...
Click to collapse
You connect your phone to computer while in recovery to transfer the OS zip
Sent from my Redmi K20 Pro using Tapatalk
BJack0 said:
The exact problem I have is that I cant transfer any files to the device after formatting the data. I follow the steps correctly and I get into TWRP successfully and then everyone has told me to format the data then install lineage but I cant install the OS if formatting the data removes it.
Get device into fastboot
Flash revocery with TWRP
power the device off
hold volume up and power
boot into custom recovery
format data
move lineageOS onto my device
install lineageOS
reboot
done.
This is the list of exact actions I am doing with no results is there something I am missing or something that is in the wrong order.
Click to expand...
Click to collapse
After format data, reboot your device into recovery again and transfer LOS, gapps and all files you need.
Format data kills the storage.
I always used to reboot from TWRP back in to TWRP after formatting data, but I've recently seen someone saying that they just unmount data then remount it again. I haven't tried it myself but it certainly makes sense and would be quicker too.
Robbo.5000 said:
I always used to reboot from TWRP back in to TWRP after formatting data, but I've recently seen someone saying that they just unmount data then remount it again. I haven't tried it myself but it certainly makes sense and would be quicker too.
Click to expand...
Click to collapse
Yes I did that and it worked, unmounting and remounting helps detect the storage in PC
Sent from my Redmi K20 Pro using Tapatalk
Robbo.5000 said:
I always used to reboot from TWRP back in to TWRP after formatting data, but I've recently seen someone saying that they just unmount data then remount it again. I haven't tried it myself but it certainly makes sense and would be quicker too.
Click to expand...
Click to collapse
Yes that works. Tried it myself but prefer to reboot into recovery again.:laugh:
Finally Successful
After a long post I have finally finished the process successfully. This was pretty educational for me since I didn't understand any of this at the start I would like to thank everyone who reply's and all the information that you have provided.
need help guys, i stuck in bootloop.
- fastboot rom global china V10.3.17.0 PFKCNXM
- fastboot twrp 3.3.1
- format data
- flash vendor image cn 10.4.6.0
- wipe cache/dalvik
- flash lineage os
- flash gapps nano
- reboot
- stuck bootloop
Hi togehter,
I had some problems with flashing new custom roms and ended up in a bootloop with not being able to boot to recovery. This could be solved by flashing the stock image with the xiaomi flash tool.
Before I will fu up again I would like to bring some light into the darkness.
When coming from Stock Rom:
1. Unlock Bootloader -> done successfully
2. Flashed TWRP Recovery -> done successfully but storage (data) was encrypted
3. Flashed Magisk via Recovery -> done successfully (storage still encrypted)
from here I was happy using the Stock Rom with Root.
Now I started messing things up:
Because there are a few things that bother me about the stock rom i wanted to use lineageOS/Pixel Experience. So I proceeded as following:
1. Backup my data (still have to enter key when starting twrp to decrypt the storage) -> done successfully
2. Flash LineageOS -> resulted in bootloop to TWRP
When entering twrp there was no query about the key and data where encrypted. Also the Backup was not accessible .
3. I used all in one tool to erase storage and decrypt data. -> successfully... Now i was able to place data on the internal storage again and start flashing a rom
4. Flashing LineageOS -> done successfully and able to boot into rom
Back to TWRP data was encrypted and I had to enter key.
5. Flashing remove force encryption script via twrp. -> done but now i was facing boot to black screen. TWRP was not working anymore.
Only way to get it work again, was flashing stock image.
Why is the data system always encrypted. This is rly annoying and backups don't work, because i can not encrypt them. Also, I can not put any files on the memory because it is encrypted.
I would rly like to try a custom rom, but I would also like to be able to go back to a backup. What have i done wrong?
You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.
SeppGoPro said:
Hi togehter,
.... What have i done wrong?
Click to expand...
Click to collapse
You need to format data (not just wipe data) in TWRP. Some people suggest before flashing a ROM and some say after, but I don't think it makes a great deal of difference either way.
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Then in TWRP wipe cache and dalvik, then format data.
Reboot into TWRP, or unmount and mount the data partition in TWRP so it correctly reads the data partition.
Copy across the ROM (and GApps if needed)
Them flash.
Boot into the ROM and you should be good.
After initial setup, if you want root, boot into TWRP and flash Magisk.
From here, if you've set a pin on the ROM, you'll be encrypted, but everything should still work normally. You should be able to access everything normally in TWRP and also perform backups. You should be able to got data across from/to a PC normally.
Turbine1991 said:
You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.
Click to expand...
Click to collapse
Not true in many ways.
There is need to flash no dm verity. It's one way of solving the issue, but it's not the only way. You should only do this if you know what it's for and if you know you want this.
AOSP ROMs are not unstable. I've been using them on mine for over 4 months. None are perfect and they have a few minor issues/bugs, but they are far from being considered unstable. I've never had shutdowns, reboots or FC'S.
Thanks for the replies.
Robbo.5000 said:
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Click to expand...
Click to collapse
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?
SeppGoPro said:
Thanks for the replies.
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?
Click to expand...
Click to collapse
Fastboot ROMs are official ROMs that are flashed through the Mi Flash Tool
, with the phone booted into fastboot mode and connected to the PC. They contains almost all partitions, including vendor and all firmware. They will be a .tgz file. They are mainly used as an almost failsafe way to recover the phone, should you mess things up. Flashing them will restore the phone to factory, so will lose TWRP, but you're guaranteed a clean starting point.
If, for example, you want to install Havoc 3, it is recommended to flash it on top of either China or India 10.4 vendor and firmware. So if you're phone is currently on global firmware, you would then need to flash, say, Chinese firmware and vendor flies, before flashing Havoc.
If you have been previously flashing other mods, such as 75Hz, screen refresh rate, for example, then you might choose to flash the official Chinese fastboot ROM, instead of just the firmware and vendor, to ensure that you've cleaned the phone of any mods, etc. In most cases you will be fine flashing firmware and vendor, though.
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.
Robbo.5000 said:
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.
Click to expand...
Click to collapse
So in this case, i can just flash this rom and there is no need of flashing a diffrent vendor or firmware.
So final question: I'm happy with the stock rom plus root. I would like to try a custom rom but I'm not willing to go through the whole installtion procedure again. Is there a way of making a backup and keeping it?
When I backup the stock rom right now, the backup will ne encrypted again...When I formate the data, all my data will be gone again ?