Related
Hi !!
First, i tried to flash Resurrection Remix ROM but i stucked in BOOTLOOP
And then i flashed latest stock rom Version: V9.5.9.0.ODHMIFA using mi flash but i had a problem that when i wan to connect to WiFi it will say save then disable but never connect so i flashed the stock rom again and i still getting the WiFi problem and i flashed the rom for the third time and i got stuck in weird BOOTLOOP, the device will start normally but after few minutes it will restart over and over and over, so what should i do ? can anyone help me ?
that's all and i'm sorry if my english is bad
SooMi22 said:
Hi !!
First, i tried to flash Resurrection Remix ROM but i stucked in BOOTLOOP
And then i flashed latest stock rom Version: V9.5.9.0.ODHMIFA using mi flash but i had a problem that when i wan to connect to WiFi it will say save then disable but never connect so i flashed the stock rom again and i still getting the WiFi problem and i flashed the rom for the third time and i got stuck in weird BOOTLOOP, the device will start normally but after few minutes it will restart over and over and over, so what should i do ? can anyone help me ?
that's all and i'm sorry if my english is bad
Click to expand...
Click to collapse
if u want to use custom rom just follow proper steps and it will install.
-unlock bootloader (which i assume u already have)
-fastboot boot latest twrp
-do a full wipe and reboot to bootloader.
-again fastboot boot the latest twrp
-now copy rom,gapps,magisk(mandatory) and twrp installer(optional)
-install rom and twrp installer only
-reboot to booatloader and fastboot boot twrp again or if u installed twrp installer just reboot to recovery.
-now flash magisk and gapps
-reboot system
By mistake if u flashed factory.bat then read this : https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190
if your phone is rebooting after every 60 sec then u most probably corrupted /persist. Don't worry custom roms will work without any problem as they don't touch persist.
did you by chance used flash_factory.bat in mi flash tool ?
anshu945 said:
if u want to use custom rom just follow proper steps and it will install.
-unlock bootloader (which i assume u already have)
-fastboot boot latest twrp
-do a full wipe and reboot to bootloader.
-again fastboot boot the latest twrp
-now copy rom,gapps,magisk(mandatory) and twrp installer(optional)
-install rom and twrp installer only
-reboot to booatloader and fastboot boot twrp again or if u installed twrp installer just reboot to recovery.
-now flash magisk and gapps
-reboot system
also if u want to use stock rom read this : https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190
if your phone is rebooting after every 60 sec then u most probably corrupted /persist. Don't worry custom roms will work without any problem as they don't touch persist.
also did you by chance used flash_factory.bat in mi flash tool ?
Click to expand...
Click to collapse
thank you for help
i will try to use custom rom and i hope it will work
and i did use flash_all_lock_crc.bat in mi flash tool then i'm start getting the restart problem with unread sim card
use flash_all_lock.bat only or flash all except storage.bat or flash_all.bat .except these nothing else.
flash custom rom or flash_all_lock.bat in mi flash tool (it will work work most probably).
anshu945 said:
if u want to use custom rom just follow proper steps and it will install.
-unlock bootloader (which i assume u already have)
-fastboot boot latest twrp
-do a full wipe and reboot to bootloader.
-again fastboot boot the latest twrp
-now copy rom,gapps,magisk(mandatory) and twrp installer(optional)
-install rom and twrp installer only
-reboot to booatloader and fastboot boot twrp again or if u installed twrp installer just reboot to recovery.
-now flash magisk and gapps
-reboot system
also if u want to use stock rom read this : https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190
if your phone is rebooting after every 60 sec then u most probably corrupted /persist. Don't worry custom roms will work without any problem as they don't touch persist.
also did you by chance used flash_factory.bat in mi flash tool ?
Click to expand...
Click to collapse
problem solved !!
first, i tried to flash custom rom with your steps but it didn't work for me, getting stock in boot logo
then i tried the solution in thread u give me, i flashed tissot_images_7.8.23_7.1 via mi flash tool then i restored restore persist partition and everything work great !!
wifi and sim card works fine, thanks man for your help :good:
great, just keep in mind not to flash factory.bat or any other bat files except the three i mentioned above.
anshu945 said:
great, just keep in mind not to flash factory.bat or any other bat files except the three i mentioned above.
Click to expand...
Click to collapse
ok i will, thanks again
anshu945 said:
great, just keep in mind not to flash factory.bat or any other bat files except the three i mentioned above.
Click to expand...
Click to collapse
sorry for bothering, but now i have 'no service' issue, the phone read the sim but it shows that i have no service
do u have any idea to fix this ?
SooMi22 said:
sorry for bothering, but now i have 'no service' issue, the phone read the sim but it shows that i have no service
do u have any idea to fix this ?
Click to expand...
Click to collapse
now to recover imei follow the same guide above, if u have trouble editing qcn let me know.
hi, i need some help with reflashing the stock rom
its always stuck on pushing the system neither manual nor using mi flash.
here i attached the log file, wish it help in some way.
littlecrap said:
hi, i need some help with reflashing the stock rom
its always stuck on pushing the system neither manual nor using mi flash.
here i attached the log file, wish it help in some way.
Click to expand...
Click to collapse
you followed this guide?
YayJohn said:
you followed this guide?
Click to expand...
Click to collapse
no i dont follow the guide you mentioned, i dont know whats wrong but its always stuck in writing system b
the log says its ok but no further action.
littlecrap said:
no i dont follow the guide you mentioned, i dont know whats wrong but its always stuck in writing system b
the log says its ok but no further action.
Click to expand...
Click to collapse
You can try following the guide I sent u but if it doesn't work I can't help you
I ve done a nadroid of all the system on my oneplus 6t and wiped the system and internal storage and i forgot that the nandroid exists on the internal storage as im used to my old phone... currently i m stuck on TWRP any help ? i m panicking
I have mounted the storage MTP but all i see is this:
https://imgur.com/a/14rbdo9
https://imgur.com/ZVBwTRj
I m not sure i can copy anything into it.
Shady282 said:
I ve done a nadroid of all the system on my oneplus 6t and wiped the system and internal storage and i forgot that the nandroid exists on the internal storage as im used to my old phone... currently i m stuck on TWRP any help ? i m panicking
I have mounted the storage MTP but all i see is this:
https://imgur.com/a/14rbdo9
https://imgur.com/ZVBwTRj
I m not sure i can copy anything into it.
Click to expand...
Click to collapse
Adb sideload full ROM in TWRP with adb push *file* /sdcard
Wipe everything again and reinstall a full OOS zip found here in the forums. Make sure you install it to both slots, once you flash the full rom zip, flash TWRP again, reboot twrp and then reboot to system. You'll have to set everything up again unfortunately. My advice would be after you make a nandroid, copy it to a PC so that when you go to wipe everything, you can copy everything back and go from there or do what I do and buy a USB Type-C flash drive and when you go to make a backup, just backup to the flash drive. Or worst case use the MSM Download Tool to start fresh. Just make sure if you have the T-Mobile 6T to use the MSM specifically for the T-Mobile version.
I keep all of my important files like ROM's, recovery, Kernels, and backups on a 128gb SanDisk Ultra Fit 3.1 and use a Samsung OTG adapter. They can be had on eBay or Amazon for about $25. 32gb for $10, 64gb for $15-20, and 128gb for $20-25.
Do as Mikex8593 said or just flash the system partition of a fastboot rom
fastboot flash system system.img
oskarvlc said:
Do as Mikex8593 said or just flash the system partition of a fastboot rom
fastboot flash system system.img
Click to expand...
Click to collapse
I tried to sideload through TWRP and it failed every time I tried "total xfr: 1.00x.
I was thinking that maybe I should flash stock recovery and from stock recovery to flash the whole OOS Rom as i downloaded from OnePlus website?
Also i was looking at this thread " https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516"
and was wondering about the Fastboot roms, can I just flash it through fastboot and get the phone back working, since TWRP not working.
I m a bit newbie in this and learning my way through.
Thank you for your patience
TheKnux said:
Wipe everything again and reinstall a full OOS zip found here in the forums. Make sure you install it to both slots, once you flash the full rom zip, flash TWRP again, reboot twrp and then reboot to system. You'll have to set everything up again unfortunately. My advice would be after you make a nandroid, copy it to a PC so that when you go to wipe everything, you can copy everything back and go from there or do what I do and buy a USB Type-C flash drive and when you go to make a backup, just backup to the flash drive. Or worst case use the MSM Download Tool to start fresh. Just make sure if you have the T-Mobile 6T to use the MSM specifically for the T-Mobile version.
I keep all of my important files like ROM's, recovery, Kernels, and backups on a 128gb SanDisk Ultra Fit 3.1 and use a Samsung OTG adapter. They can be had on eBay or Amazon for about $25. 32gb for $10, 64gb for $15-20, and 128gb for $20-25.
Click to expand...
Click to collapse
Can you please explain what do you mean by installing it on both slots?
Edit: i Have just discovered the slots on TWRP which is something new to me and googling/trying to understand it.
isn't it possible to flash everything back using fastboot or stock recovery?
TWRP have failed in side-loading the stock rom zip I installed from oneplus website.
Yes, i was thinking of the same, I should get a USB type-C it is a must.
Thank you a lot for your help.
Shady282 said:
Can you please explain what do you mean by installing it on both slots?
isn't it possible to flash everything back using fastboot or stock recovery?
TWRP have failed in side-loading the stock rom zip I installed from oneplus website.
Yes, i was thinking of the same, I should get a USB type-C it is a must.
Thank you a lot for your help.
Click to expand...
Click to collapse
While you're booted into TWRP, if it boots to Slot A, install OOS to A, then change to Slot B and flash OOS to B. PM me if you need help. I'll try and help as best as I can.
TheKnux said:
While you're booted into TWRP, if it boots to Slot A, install OOS to A, then change to Slot B and flash OOS to B. PM me if you need help. I'll try and help as best as I can.
Click to expand...
Click to collapse
I have just decided to go to sleep, and in twrp i tried to click power off. The phone ended up in bootloop... then i tried to boot into bootloader. and then few more minutes the phone just booted in OOS Rom and started the setup process as new Rom.
Which is weird, I don't know what happened.
Also i have lost the TWRP recovery
I m not sure if it is related, to me clicking on slots A - B or so.
Shady282 said:
I have just decided to go to sleep, and in twrp i tried to click power off. The phone ended up in bootloop... then i tried to boot into bootloader. and then few more minutes the phone just booted in OOS Rom and started the setup process as new Rom.
Which is weird, I don't know what happened.
Also i have lost the TWRP recovery
I m not sure if it is related, to me clicking on slots A - B or so.
Click to expand...
Click to collapse
That's the point of slots, if your ROM is screwed in active slot and can't boot, at next boot the other slot will be set and tried. If there's a working ROM on it it's good. And if in the other slot no custom recovery is present you lose it
That's why I don't understand why people recommend to flash the same ROM on both slots, it goes on the contrary of the slot philosophy. The only understandable case is when you need to have up to date vendor official partitions before flashing a custom ROM: there the ROM Dev can recommend to flash official OOS twice. But it's not the case till now in the few custom ROM I've seen around
Sounds like you might have been making it too complicated. You can sideload the ROM, or just transfer the ROM to the phone and load it. The phone will be seen by the OS as a MTP device when TWRP is up and running.
When you are in slot A and you install the factory ROM it is automatically installed to slot B and vice versa. You need to immediately install the TWRP recovery to keep TWRP as the ROM will overwrite your recovery with the stock recovery. Then you need to reboot to recovery again, this would put to the opposite slot where your "new" ROM is installed, and let you install Magisk. If you want to update this the original slot just install the ROM and TWRP again. Reboot to recovery again. No need to specify slots, unless you didn't want to change something in the other slot for some reason (like a dual boot or something)
At this point just fast boot the TWRP image and re-run the TWRP installer to get TWRP back and it sounds like you're all set.
OhioYJ said:
Sounds like you might have been making it too complicated. You can sideload the ROM, or just transfer the ROM to the phone and load it. The phone will be seen by the OS as a MTP device when TWRP is up and running.
When you are in slot A and you install the factory ROM it is automatically installed to slot B and vice versa. You need to immediately install the TWRP recovery to keep TWRP as the ROM will overwrite your recovery with the stock recovery. Then you need to reboot to recovery again, this would put to the opposite slot where your "new" ROM is installed, and let you install Magisk. If you want to update this the original slot just install the ROM and TWRP again. Reboot to recovery again. No need to specify slots, unless you didn't want to change something in the other slot for some reason (like a dual boot or something)
At this point just fast boot the TWRP image and re-run the TWRP installer to get TWRP back and it sounds like you're all set.
Click to expand...
Click to collapse
Hi, I tried to copy the zip file through MTP but it didn't work, the internal storage on PC looked empty and was not mentioning any size of the storage, and when I try to copy and past a file, the copy process gets stuck on 0% forever.
Sideloading didn't work too. The CMD on PC reached 47% and then gave an error of total xfr:1.00x. when i tried to flash the stock rom zip file from oneplus website.
I had TWRP latest official one, i m not sure if it has issues.
Is there a way to validate that the stock rom files and all are still all working fine? Maybe re-flash the stock rom through stock recovery since TWRP is gone?
Also regarding the slot A and Slot B, i have never flashed anything except root through TWRP. So it could be when i wiped it wiped the empty slot. But the system is back at to zero and setup as new.
try this
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
I was on beta 3 and decided to flash a new version of OOS. I flashed 9.0.11 -> reflashed TWRP and magisk but when I rebooted, it went straight back to TWRP.
I had to switch to a different slot and the phone booted to OOS beta 3 again. Tried to flash 9.0.11 and reflashed beta 3 again but the same thing happened.
Then i swiped everything except for USB storage and Internal Storage in TWRP and now the phone is without OS.
I rebooted to TWRP and now TWRP lost the encryption and I can't flash anything anymore.
Does anybody know how to recover from this?
I'm using the official TWRP build.
Dont panic just download a fast boot rom for version 9.0.11 and run it from fastboot using terminal. Then you will need to flash Magisk in order to have root access.
devam1995 said:
Dont panic just download a fast boot rom for version 9.0.11 and run it from fastboot using terminal. Then you will need to flash Magisk in order to have root access.
Click to expand...
Click to collapse
How do you do that using the terminal? I tried following this topic https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516 but I got this error
https://imgur.com/wy1immW
TWRP still can't flash OOS
So I was able to boot the phone up again using MSMdownloadTool but the problem still persist. I was supposed to be at OOS 9.0.11 but upon checking I found out I was still on open beta 3. Tried to flash 9.0.11 via TWRP and the same thing happened. I was on slot B so when I flashed OOS and rebooted, it rebooted to slot A and brought me straight back to TWRP. It won't boot again until I switch back to slot B to boot and slot B was still on open beta 3. Any thoughts?
twistingthai said:
So I was able to boot the phone up again using MSMdownloadTool but the problem still persist. I was supposed to be at OOS 9.0.11 but upon checking I found out I was still on open beta 3. Tried to flash 9.0.11 via TWRP and the same thing happened. I was on slot B so when I flashed OOS and rebooted, it rebooted to slot A and brought me straight back to TWRP. It won't boot again until I switch back to slot B to boot and slot B was still on open beta 3. Any thoughts?
Click to expand...
Click to collapse
Flash a patched
Code:
boot.img
when I got the problem, I did that and it worked, booted me to system but if that doesn't work then you have to flash Magisk.
twistingthai said:
So I was able to boot the phone up again using MSMdownloadTool but the problem still persist. I was supposed to be at OOS 9.0.11 but upon checking I found out I was still on open beta 3. Tried to flash 9.0.11 via TWRP and the same thing happened. I was on slot B so when I flashed OOS and rebooted, it rebooted to slot A and brought me straight back to TWRP. It won't boot again until I switch back to slot B to boot and slot B was still on open beta 3. Any thoughts?
Click to expand...
Click to collapse
This phone has A/B partitions and is able to store a backup version of the OS so if a new installed version doesn't boot it will revert back to the old one.
When Flashing, you need to flash "BOTH" slots.
If you used the MSM tool to boot, you just booted and not flashed.
The MSM tool will flash your phone, restore the stock recovery and relic the bootloader. It will look like it came out of the box.
I don't know how to get you from wrapped around the axle except to tell you to run the MSM tool and let it wipe the phone and get you back to stock. You can then unlock the BL again and install TWRP, etc if you like.
twistingthai said:
I was on beta 3 and decided to flash a new version of OOS. I flashed 9.0.11 -> reflashed TWRP and magisk but when I rebooted, it went straight back to TWRP.
I had to switch to a different slot and the phone booted to OOS beta 3 again. Tried to flash 9.0.11 and reflashed beta 3 again but the same thing happened.
Then i swiped everything except for USB storage and Internal Storage in TWRP and now the phone is without OS.
I rebooted to TWRP and now TWRP lost the encryption and I can't flash anything anymore.
Does anybody know how to recover from this?
I'm using the official TWRP build.
Click to expand...
Click to collapse
You are booting into TWRP because you did not format your data partition. When flashing OOS, you need to not only wipe data, but also under the Wipe menu, select format data. It should prompt you to type "yes".
parker.stephens said:
You are booting into TWRP because you did not format your data partition. When flashing OOS, you need to not only wipe data, but also under the Wipe menu, select format data. It should prompt you to type "yes".
Click to expand...
Click to collapse
This! Thanks to you I was able to flash OOS again. But do I need to format the data everytime I flash OOS because it will be a pain . This is the first time I had to format data when updating OOS. Thanks alot.
twistingthai said:
This! Thanks to you I was able to flash OOS again. But do I need to format the data everytime I flash OOS because it will be a pain . This is the first time I had to format data when updating OOS. Thanks alot.
Click to expand...
Click to collapse
Glad to help. I was sick of having to put the device into Qualcomm mode just to get it to boot up, then I decided to try reformatting data and it worked.
For the past 24+ hours I've been trying to flash a few custom roms on my UNLOCKED BOOTLOADER OP6T, but the phone TURNS OFF a few seconds after the boot sequence/animation.
I've read about the A/B slots and tried the Roms' flashing instructions, along with a few suggestions from others, but I cannot get any Custom Rom on my phone...
Here are the steps I've taken to flash (a few times I tried different things that I'll put in parenthesis). Is there anything ya'll see that I'm doing wrong?:
Starting from OOS 10.3.2 Fastboot Recovery and all required files on an OTG USB Drive
fastboot to TWRP....img
Confirmed I'm on Slot A
Wipe Data/Dalvik
Install OOS...zip (10.3.2)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
(Format Data)
Confirmed I'm on Slot B
Install OOS...zip (10.3.2)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
Confirmed I'm on Slot A
Install Xtended (v8 4/13)
(Wipe Data/Cache)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
Confirmed I'm on Slot B
Install Xtended (v8 4/13)
(Wipe Data/Cache)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
Confirmed I'm on Slot A
Install GAPPS (Arm64 10.0 Nano)
(Format Data)
Reboot System
My Guide for Lineage, however it will work for most AOSP based ROMs.
I assume you arent manually switching slots. Don't, there is no need, in fact dont worry about it. Slots will switch automatically after flashing a ROM when you reboot recovery. There is no cache partition, stop wiping this, its not doing anything. There are two slots, but only one data partition that is shared, there isnt a reason to keep wiping it.
On most instructions adding or removing steps will make things not work. Unfortunately for this device there is a lot of out dated information and information that just doesnt work. My guide has been tested with 10.3.3, and the latest version of LOS, however if you have a T-Mobile 6T you are on your own. (I have a regular 6T)
OhioYJ said:
My Guide for Lineage, however it will work for most AOSP based ROMs.
I assume you arent manually switching slots. Don't, there is no need, in fact dont worry about it. Slots will switch automatically after flashing a ROM when you reboot recovery. There is no cache partition, stop wiping this, its not doing anything. There are two slots, but only one data partition that is shared, there isnt a reason to keep wiping it.
On most instructions adding or removing steps will make things not work. Unfortunately for this device there is a lot of out dated information and information that just doesnt work. My guide has been tested with 10.3.3, and the latest version of LOS, however if you have a T-Mobile 6T you are on your own. (I have a regular 6T)
Click to expand...
Click to collapse
Thanks for the comment! I just followed your guide, but still seeing the boot animation for a few seconds, then the phone vibrates and turns off.
For kicks, I decided to Format Data and I see the boot animation longer, all the way to the end when it's about to start Android, but then it vibrates and shuts off. Strange.
I'm thinking there is something different about my phone... It's a global, unlocked version and I've rooted/flashed hundreds of roms over the years on various devices, so all of this should be a piece of cake................. Thanks!
oooscasianooo said:
Thanks for the comment! I just followed your guide, but still seeing the boot animation for a few seconds, then the phone vibrates and turns off.
For kicks, I decided to Format Data and I see the boot animation longer, all the way to the end when it's about to start Android, but then it vibrates and shuts off. Strange.
I'm thinking there is something different about my phone... It's a global, unlocked version and I've rooted/flashed hundreds of roms over the years on various devices, so all of this should be a piece of cake................. Thanks!
Click to expand...
Click to collapse
Have you tried without Gapps?
After the shutdown go back to twrp and extract the content of /sys/fs/pstore/* and upload the files here.
onliner said:
After the shutdown go back to twrp and extract the content of /sys/fs/pstore/* and upload the files here.
Click to expand...
Click to collapse
Thanks. I actually gave up and setup stock OOS again, so it took a while to get a TWRP backup, etc. etc.
So after the backup, I installed Xtended + TWRP, reboot to recovery, installed Xtended + TWRP, wiped dalvik, and reboot to system.
Boot animation shut down issue as usual.
Afterwards, I copied the pstore folder (attached zip).
Thanks!
onliner said:
After the shutdown go back to twrp and extract the content of /sys/fs/pstore/* and upload the files here.
Click to expand...
Click to collapse
Anything in the logs I can look for?
This is driving me crazy. I flashed MIUI just fine (because it had the .bat file that does everything for you). Essentially it's doing the same thing as flashing OOS & Rom on A/B, right?
Just tried flashing the newest Xtended Rom (May 11th), same issue. Phone vibrates and completely turns off while the boot animation is running.
OhioYJ said:
My Guide for Lineage, however it will work for most AOSP based ROMs.
I assume you arent manually switching slots. Don't, there is no need, in fact dont worry about it. Slots will switch automatically after flashing a ROM when you reboot recovery. There is no cache partition, stop wiping this, its not doing anything. There are two slots, but only one data partition that is shared, there isnt a reason to keep wiping it.
On most instructions adding or removing steps will make things not work. Unfortunately for this device there is a lot of out dated information and information that just doesnt work. My guide has been tested with 10.3.3, and the latest version of LOS, however if you have a T-Mobile 6T you are on your own. (I have a regular 6T)
Click to expand...
Click to collapse
If you have a TMobile 6t I can confirm I have had to manually change the slots during the flashing process to get custom ROMs installed.
mrmcshagbag said:
If you have a TMobile 6t I can confirm I have had to manually change the slots during the flashing process to get custom ROMs installed.
Click to expand...
Click to collapse
I found out that I do have the T-Mobile version that the seller flashed to International Software haha
When I reboot to recovery, I do see that the slots are being changed though.
Would you mind post the exact steps you took to successfully flash a ROM/GAPPS?
oooscasianooo said:
I found out that I do have the T-Mobile version that the seller flashed to International Software haha
When I reboot to recovery, I do see that the slots are being changed though.
Would you mind post the exact steps you took to successfully flash a ROM/GAPPS?
Click to expand...
Click to collapse
Fastboot boot TWRP Marion version
Flash oos
Flash Marion TWRP zip
Check my slot
Reboot recovery
Changed slot since it didn't change
Reboot recovery
Flash oos
Flash Marion TWRP zip
Changed slot
Reboot recovery
Flash custom rom
Flash Marion TWRP zip
Change slot
Reboot recovery
Flash gapps
Flash magisk 20.4
Reboot to system
Those are the steps I had to take before I finally got a custom rom to work. I tried doing the methods posted which would have probably worked if the slots were changing on there own but they weren't for me.
mrmcshagbag said:
Fastboot boot TWRP Marion version
Flash oos
Flash Marion TWRP zip
Check my slot
Reboot recovery
Changed slot since it didn't change
Reboot recovery
Flash oos
Flash Marion TWRP zip
Changed slot
Reboot recovery
Flash custom rom
Flash Marion TWRP zip
Change slot
Reboot recovery
Flash gapps
Flash magisk 20.4
Reboot to system
Those are the steps I had to take before I finally got a custom rom to work. I tried doing the methods posted which would have probably worked if the slots were changing on there own but they weren't for me.
Click to expand...
Click to collapse
Thanks! Do you mean the "mauronofrio" version?
oooscasianooo said:
Thanks! Do you mean the "mauronofrio" version?
Click to expand...
Click to collapse
Yes couldn't remember the exact name but I knew you would be able to find it haha
mrmcshagbag said:
Yes couldn't remember the exact name but I knew you would be able to find it haha
Click to expand...
Click to collapse
hahaha thanks! I was thinking, "is there a T-Mobile version of TWRP?!" haha!
There was MIUI installed in my device and i wanted to install MIUI 12 so for which i had to unlock the device and install twrp..
Every thing was fine till then...
I went to advanced wipe and accidentally wiped the internal storage mount.. and FRD the device but still i was in twrp when i was trying to paste the custom while connected the device to the laptop it could not transfer...so i decided to re install twrp thought it might work...as i had done the same thing in the past...but this time my device is stuck in the fastboot mode and now im not able to install and recovery image like twrp or orange fox recover.. and not even shut down..
Some one pls help could not afford a new device right now..
Prasad.aditya21 said:
There was MIUI installed in my device and i wanted to install MIUI 12 so for which i had to unlock the device and install twrp..
Every thing was fine till then...
I went to advanced wipe and accidentally wiped the internal storage mount.. and FRD the device but still i was in twrp when i was trying to paste the custom while connected the device to the laptop it could not transfer...so i decided to re install twrp thought it might work...as i had done the same thing in the past...but this time my device is stuck in the fastboot mode and now im not able to install and recovery image like twrp or orange fox recover.. and not even shut down..
Some one pls help could not afford a new device right now..
Click to expand...
Click to collapse
You should flash vbmeta.img of your current version of miui before you wipe it all.
flamedrops said:
You should flash vbmeta.img of your current version of miui before you wipe it all.
Click to expand...
Click to collapse
But right now the flash is done so...what are the other options to bring my phone back to live..
Flash vbmeta.img is fastboot, by ADB command
Just like flashing recovery
Prasad.aditya21 said:
But right now the flash is done so...what are the other options to bring my phone back to live..
Click to expand...
Click to collapse
If vbmeta flash didn't improve your situation, you must flash a fastboot official rom via Miflash tool.
If new to this use Miflashpro latest, it will guide you in the rom choice and download.
Prasad.aditya21 said:
But right now the flash is done so...what are the other options to bring my phone back to live..
Click to expand...
Click to collapse
If the custom recovery will shown, then you can easily manage to flash ROM back wipe dalvic/cache, cache, data, system and format data type yes. And so you can flash ROM as brand new. But take note everything on your device will wipe including photos and files. But it is the way to get back your phone to life.
1 - Download this and unrar
2-enter fastboot
3-run Flash_TWRP.bat and follow instruction