[solved] softbrick - Stuck in fastboot after wiping phone in TWRP - Redmi K20 / Xiaomi Mi 9T Questions & Answers

My solution lives here https://forum.xda-developers.com/showpost.php?p=80875357&postcount=3
EDIT: original post below
all started with me wanting paranoid android. flashed 9.9.25 blobs too & hads some bugs. so i wiped everything like I would rooting any other androind phone and now phone only boots to fastboot.
my ARB is 1 if that matters, how can i fix this please?
So I've tried
flashing recovery
rebooting to recovery
flashing a stock ROM in miflash

Hello,
What did you wipe?
Do you already tried to flash a fastboot rom ?
Edit: sorry read later about miflash; do you wiped the persist partition?

Claudio67 said:
Hello,
What did you wipe?
Do you already tried to flash a fastboot rom ?
Edit: sorry read later about miflash; do you wiped the persist partition?
Click to expand...
Click to collapse
sorry, been too busy with work and missed this. after 48 of brick, I followed farhan20 guide he posted here
the miflash software actually did not work at all for me, i let that run for 30 minutes (way too long) and just unplugged eventually and went thru the guide above. after that was able to get into TWRP and then flash my fav havoc OS. life is good again.
Hopefully this can help anyone stuck in fastboot with a soft brick on their hands

Related

Stuck on bootlogo whenever flashing a cm13 rom

Regardless of what recovery I used, (yash28, regalstreak, official twrp) or even starting from the scratch( flashing stock OxygenOS using the Oneplus tools) and then reflashing the recovery, my attempts to succesfully load into a ROM has been futile. As of now, I am pretty much unable to boot into any recovery, and I am stuck using the stock OxygenOS. I tried flashing modem, first attempt was clean flashing the new modem, then flashing it dirty after flashing my rom, I tried doing the same thing with the old modem, my attempts have been futile. If anyone could shed light in this situation, it would be great, I would hate to be stuck using the stock OxygenOS rom, and not try out the great roms that are developed. I can however flash oxygenOS stock rom.
i have the same problem and i cant find any solution i thought of starting fromt he scratch as it didnt help u it might not help me too
Have the same, I've done everything. I've made the phone full stock again and still won't boot.
I have finally found the solution to my own problem
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
So now youre able to flash CM13 without bootloops?
yousuf.shareef said:
So now youre able to flash CM13 without bootloops?
Click to expand...
Click to collapse
Yep! Also make sure you are using official TWRP (https://dl.twrp.me/oneplus2/) Good luck.
abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
FINALLY! Thank you!! Ive been stuck all day without getting ANY MM ROM to boot,. and this ...thing...fixed it! Thanks again
Finally someone found the answer! Unfortunately I wiped whole internal memory and forgot to take backup of whatsapp backup so i lost that. Oh well, all works good now, thank you!
JudderArts said:
Finally someone found the answer! Unfortunately I wiped whole internal memory and forgot to take backup of whatsapp backup so i lost that. Oh well, all works good now, thank you!
Click to expand...
Click to collapse
Dont forget to thank people.
abhisek1994 said:
Dont forget to thank people.
Click to expand...
Click to collapse
JudderArts said:
thank you!
Click to expand...
Click to collapse
That's exactly what I did.
I think i faced the same problem, im using h2os 6.0.1 close beta, with twrp 3.0, but without rooting. I can restore my rom tru twrp without problem. But my try to flash grarak cm13 and new mokee os 6.0 ended up with bootloops, both stuck at oneplus logo
abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
Do you have to go back to the stock rom before flashing persist and then install cm13? or can i do it while i am on the boot logo screen...i tried going into fastboot while stuck on the boot logo (which i was able to) and flashed persist and rebooted but it is still stuck on the boot logo screen
muthukumarc said:
Do you have to go back to the stock rom before flashing persist and then install cm13? or can i do it while i am on the boot logo screen...i tried going into fastboot while stuck on the boot logo (which i was able to) and flashed persist and rebooted but it is still stuck on the boot logo screen
Click to expand...
Click to collapse
You have to downgrade fastboot/bootloader to the Lollipop one (just flash the usual revert_to_lollipop.zip found in these forums as usual).

I need your help guys. (bricked nexus 6p)

Okay, so I've been reading XDA for a while now to root my devices and install custom ROMs and its been incredibly helpful. However I have a huge issue with my nexus 6p and can't find a way to solve it.
Here goes....
I bought it of eBay a few months ago and unlocked the boot loader and rooted the phone plus i also installed twrp and made a nandroid backup. I then installed pure nexus rom and the phone was working incredibly well.
Fast forward to this week, I decided I wanted to upgrade to cm13, since I missed the cm theme engine. So I Wiped my device clean using twrp. And installed cm 13 and the gapps then rebooted.
The phone booted perfectly but on the optimising apps screen it would reboot and tell me to enter the password that I originally had on the pure nexus ROM. After doing so it would re optimise the apps but would crash and reboot. It was doing this continuously.
Twrp also asked for this password on every boot before it let me see the main recovery menu.
So then I took the logical next step and decided to wipe the phone clean again using twrp. Seeing as my password seemed to not clear the first time.
After the wipe, I decided to use the original nandroid backup to restore my device as the password thing was still showing up. And cm 13 was still not installing. Neither was pure nexus.
Okay this is where it went downhill. I hit restore and had everything checked. The process was going well but instead of the restore completing and twrp saying it was successful. It crashed halfway and rebooted.
Since then its stuck in a bootloop. Its on the google splash screen and then reboots to the google splash screen continuously. And does not boot to the os.
On another note. The bootloader is still unlocked. The recovery works. And so does adb/fastboot. So I wouldn't consider it hard bricked.
Here's what I've tried so far:
I've used the wugfresh root toolkit to flash stock and unroot the phone. With softbrick checked. Still nothing. Phone boots to the splash screen and then reboots to the splash screen.
I then reflashed twrp 3.0.2-1 . which worked And its not asking for my password anymore.
Again I tried restoring from my nandroid and it crashed midway which makes me think the nandroid backup is/was corrupted causing the issue in the first place?
I've also tried to just restore and Flash twrp again and then install pure nexus ROM. And still nothing?
I can also still mount my phone to the PC and copy and remove files.
On another note I find it interesting that although the ROM is installed. And the storage bar on my PC is partially filled showing that it clearly has a ROM installed. The phone does not have the standard android file system. Just the twrp backup folder and that's it.
I would be honoured if you could help me out here. And get my 6p up and running again.
Thank you . [emoji45]
I would suggest you flash the factory stock system image using fastboot to get your 6P back up and running.
If you don't have the factory image they can be downloaded from here
Extract the factory image then use fastboot to flash
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Check out this guide which has all the information you need, especially around device encryption and flashing roms. Lastly gaining root is as simple as flashing SuperSU or Phh's SuperUser in TWRP.
I hope that helps, let me know if you get stuck.
Yea just flash stock image I had this happen to me before and flashing stock image fixed it.
Thanks guys. I'm going to read the guide and try it out. Then let you know how it all goes. Fingers crossed it all works
Sent from my ONE A2003 using Tapatalk
im_Zak said:
Thanks guys. I'm going to read the guide and try it out. Then let you know how it all goes. Fingers crossed it all works
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
FYI don't backup efs partition with that version of twrp. It's a known issue.
i did not realize that twrp had that issue
And guys, I followed the fastboot process by the letter and although everything worked well. The nexus 6p is still bootlooping on the google splash screen and not going any further. :crying:
What should I do? i've added the cmd window screenshot so you guys can have a look.
Try this thread:
http://forum.xda-developers.com/and...r-bootloop-t3454938/post68872362#post68872362
I worked for me when I was having issues. If it worked for you, please make sure to thank the OP in the thread.
this looks promising. thank you. i'll have a go now. might need your help if i get stuck somewhere though :good:
pctechdroid said:
Try this thread:
http://forum.xda-developers.com/and...r-bootloop-t3454938/post68872362#post68872362
I worked for me when I was having issues. If it worked for you, please make sure to thank the OP in the thread.
Click to expand...
Click to collapse
Thank you so so much dude. After countless hours trying everything to get my nexus 6p up and running to no avail this post did the trick.
Respect!!?✌✌??
im_Zak said:
Thank you so so much dude. After countless hours trying everything to get my nexus 6p up and running to no avail this post did the trick.
Respect!!
Click to expand...
Click to collapse
Upgrade to TWRP 3.0.2-2 real quick. You didn't need that guide(in terms of his nandroid) but I am glad it worked. Just need to wipe efs partition using adb commands.
I see. And I have upgraded to the latest twrp so hopefully it doesn't not happen again
Sent from my ONE A2003 using Tapatalk
im_Zak said:
I see. And I have upgraded to the latest twrp so hopefully it doesn't not happen again
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Good deal!!! There's a build that's unofficial of 3.0.2-3 that you can also jump onto. The current version 3.0.2-2 has a bug with backups on Android N. There was a comprehensive post that someone made about the issues with the different versions but I cannot find it for the life of me.
Jammol said:
Good deal!!! There's a build that's unofficial of 3.0.2-3 that you can also jump onto. The current version 3.0.2-2 has a bug with backups on Android N. There was a comprehensive post that someone made about the issues with the different versions but I cannot find it for the life of me.
Click to expand...
Click to collapse
Thanks for the heads up!

zuk z1 bootloop when flashing any rom

i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Boot and recovery partitions
Sounds like you messed up boot and recovery sections. Since you can boot up successfully, you may try to flash back to ZUI which changes these two sections completely. If it's not a solution for you, I think the only way to repair is completely format including kernel, system and partitions. You can find the tutorial on Website.
...
you can fix it just use TOOL_ZUK_Z1_ENG_0.0.6
Try flashing COS 12.1 via fastboot.
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
Hi!! I've flashed the NucleaRom too and for a couple of weeks it worked just fine. However one day, out of nowhere, the phone, while still on and working, restarted itself and entered a bootloop. After a few days it restarted normally and lasted a couple of hours but then it all started again. The BIG issue here is that when the phone enters in this bootloop where it remains on for about 15 seconds, it does it either in the system or the recovery/fastboot. I've managed to install two other ROMs via TWRP, when it miraculously remained turned on, but the problem persisted.
Is there a chance your problem was similar? How did you manage to flash via QFIL? I can't enter into that "emergency" or "download mode" in order to flash.
Many thanks in advance
i think that the problem is in the bootloader itself you should try flashing the latest os u have used and instal ordinary unofical lineage nightly (you can find everywhere) by this way your bootloader will be updated to 7.1 after that you can install any software i was having same problem when trying to migrate to lineage os
unable to install Custom ROM's
hi ,,
even i had the same problem like recovery was not accepting any ROMS... if we flash it ll go to recovery again and again,
and later i have flashed CM 13 with image file,, it worked and gone to recovery and updated the update to lineage OS 14.1 with Gapps..
hope it might help u...
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
i am continuously on the boot loop! how to get rid of it?
plz help its been 4 hrs, i think i am in trouble! any possible solutions!!!!
U can try one thing.... Install cm13 with flash file and then restart - - & go to recovery select install update and select lineage 14 and G apps... I did like this . And it worked....

Mi 9T Hard Brick After MIUI11 Test

I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device still refuses to boot past the MI screen. If I try to boot into TWRP, my device gets stuck at the TWRP splash screen, no matter which version it is. Does anyone know what I can do or try at this point? Thanks.
So do I, first time I successfully instal first beta v25 miui 11, and than when the v26 comes, stupidly, i flash it from twrp, it tells me that i succeed installing that zip, and than i wipe art and cache and reboot system, but what next i know, my phone brick, i can not instal anyrom, from mi flash tool, or from anywhere. I did everything and still can not fix the problem.
Anyway, you still can enterin TWRP UI, after waiting about 10 to 30 minutes, because after intalling that rom, automatically your data format change from ext4 to f2fs, and twrp will need a lot of time to read your disk.
But, even after doing anything in twrp, still can not make my phone successfully boot into system.
And theres moun I/O error everytime i tried to wipe everything, or fix disk, or change disk format. Everything... and i just dont know what to do anymore.
So may be you can wait patiently until you can entering twrp ui, and please lemme know if you know how to fix this problem
Soapy! said:
I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device still refuses to boot past the MI screen. If I try to boot into TWRP, my device gets stuck at the TWRP splash screen, no matter which version it is. Does anyone know what I can do or try at this point? Thanks.
Click to expand...
Click to collapse
i have experience that, then i flash the twrp chinese version and it works.
@flamedrops which one if i may know? I tried 3.3.1-0916-redmi_k20-CN and still not work ?
Soapy! said:
I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device still refuses to boot past the MI screen. If I try to boot into TWRP, my device gets stuck at the TWRP splash screen, no matter which version it is. Does anyone know what I can do or try at this point? Thanks.
Click to expand...
Click to collapse
I got exactly the same problem after installing miui 11rom. Installing firmware via fastboot was unsuccessful. God, help us ...
---------- Post added at 07:44 AM ---------- Previous post was at 07:33 AM ----------
Arif Ferdian said:
So do I, first time I successfully instal first beta v25 miui 11, and than when the v26 comes, stupidly, i flash it from twrp, it tells me that i succeed installing that zip, and than i wipe art and cache and reboot system, but what next i know, my phone brick, i can not instal anyrom, from mi flash tool, or from anywhere. I did everything and still can not fix the problem.
Anyway, you still can enterin TWRP UI, after waiting about 10 to 30 minutes, because after intalling that rom, automatically your data format change from ext4 to f2fs, and twrp will need a lot of time to read your disk.
But, even after doing anything in twrp, still can not make my phone successfully boot into system.
And theres moun I/O error everytime i tried to wipe everything, or fix disk, or change disk format. Everything... and i just dont know what to do anymore.
So may be you can wait patiently until you can entering twrp ui, and please lemme know if you know how to fix this problem
Click to expand...
Click to collapse
Just the exact same problem as mine. If you know anything about how to solve this problem, please tell us.
I had the same problem with a miui 10 weekly beta but unfortunately I wasn't able to fix it but lucky me my phone was still in a return period so I returned it back to Amazon and got my money back since then I have always stayed away from beta ROMs . I tried everything but it wasn't booting pass the mi logo as you said
flamedrops said:
i have experience that, then i flash the twrp chinese version and it works.
Click to expand...
Click to collapse
Benfatica said:
I had the same problem with a miui 10 weekly beta but unfortunately I wasn't able to fix it but lucky me my phone was still in a return period so I returned it back to Amazon and got my money back since then I have always stayed away from beta ROMs . I tried everything but it wasn't booting pass the mi logo as you said
Click to expand...
Click to collapse
Ahhhh yes, i was thinking to using my guaranteed card, as i still can relock bootliader with mi flash tools, already trying anything for couples day with zero result, and im giving up hahaha
Arif Ferdian said:
Ahhhh yes, i was thinking to using my guaranteed card, as i still can relock bootliader with mi flash tools, already trying anything for couples day with zero result, and im giving up hahaha
Click to expand...
Click to collapse
did you really reboot it using adb reboot twrp? and reboot system on twrp using twrp cn version?
Yap @flamedrops i already do, and even tried all the TWRP version that exist, and also reflash many Rom, from stock, eu, ct, aosp, miui 11 25, miui 11 26, i flash from adb sideload, from twrp via usb otg, via miflash tool,
I flash boot.img, etc
Still no result.
Already tried everything that i could thinking about
flamedrops said:
did you really reboot it using adb reboot twrp? and reboot system on twrp using twrp cn version?
Click to expand...
Click to collapse
This LR. TEAM is twrp cn version right? And in fact, this version hardly booting to twrp ui version after this problem, easier to entering twrp ui with the ugly themed greek version
Arif Ferdian said:
This LR. TEAM is twrp cn version right? And in fact, this version hardly booting to twrp ui version after this problem, easier to entering twrp ui with the ugly themed greek version
Click to expand...
Click to collapse
ok, yes thats it. have you tried to flash magisk?
@flamedrops not yet, i never tried to flash magisk yet, ill tried next time i could pass twrp splash screen
flamedrops said:
i have experience that, then i flash the twrp chinese version and it works.
Click to expand...
Click to collapse
Can you list your steps to fix this? My data and cache partitions are 0kb and i get i/o errors too.
I have persist problems after installing muiu 11 over the los16.
Thinking about relock it and sens it back to aliexpress seller.
@mvha just go into fastboot mode, and flash persist.img from stock fastboot rom,
With command : fastboot flash persist persist.img
Thats all
Arif Ferdian said:
So do I, first time I successfully instal first beta v25 miui 11, and than when the v26 comes, stupidly, i flash it from twrp, it tells me that i succeed installing that zip, and than i wipe art and cache and reboot system, but what next i know, my phone brick, i can not instal anyrom, from mi flash tool, or from anywhere. I did everything and still can not fix the problem.
Anyway, you still can enterin TWRP UI, after waiting about 10 to 30 minutes, because after intalling that rom, automatically your data format change from ext4 to f2fs, and twrp will need a lot of time to read your disk.
But, even after doing anything in twrp, still can not make my phone successfully boot into system.
And theres moun I/O error everytime i tried to wipe everything, or fix disk, or change disk format. Everything... and i just dont know what to do anymore.
So may be you can wait patiently until you can entering twrp ui, and please lemme know if you know how to fix this problem
Click to expand...
Click to collapse
This makes sense as I remember trying to boot into stock recovery early in the morning. I woke up and it finally booted, but the recovery was in Chinese. I will give 4PDA TWRP about an hour and see what I can do. Thanks.
Soapy! said:
This makes sense as I remember trying to boot into stock recovery early in the morning. I woke up and it finally booted, but the recovery was in Chinese. I will give 4PDA TWRP about an hour and see what I can do. Thanks.
Click to expand...
Click to collapse
If you can not use 4pda, i suggest u to use greek one, thats twrp version the must successfully booting in my experiences
I am thankful that I saw this before updating to newest miui 11
flamedrops said:
ok, yes thats it. have you tried to flash magisk?
Click to expand...
Click to collapse
Can not flash magisk, etc hahahhahaa
Arif Ferdian said:
If you can not use 4pda, i suggest u to use greek one, thats twrp version the must successfully booting in my experiences
Click to expand...
Click to collapse
After you used the Greek twrp did you manage to solve the problem?

Bootloop after flashing magisk - now bootloop after wipe and flashing miui11?

So after a long battle with flashing magisk that resulted in a bootloop everytime I was only able to boot again after flashing the magiskuninstaller. I decided to flash magisk again, flash dmverityencryption disabler and format data as some users suggested.
Now i'm stuck in a full on bootlop.
I decided to wipe everything and just flash the latest miui11 (11.0.4.0) cause that fixed my problems last time. But this time i'm still stuck in a bootloop after flashing the rom. I also noticed that the persist partition is missing for some reason, not sure if it's supposed to be like this. Luckily the phone still boots to orangefox recovery so hopefully I can fix this.
Any advice guys?
beybus said:
So after a long battle with flashing magisk that resulted in a bootloop everytime I was only able to boot again after flashing the magiskuninstaller. I decided to flash magisk again, flash dmverityencryption disabler and format data as some users suggested.
Now i'm stuck in a full on bootlop.
I decided to wipe everything and just flash the latest miui11 (11.0.4.0) cause that fixed my problems last time. But this time i'm still stuck in a bootloop after flashing the rom. I also noticed that the persist partition is missing for some reason, not sure if it's supposed to be like this. Luckily the phone still boots to orangefox recovery so hopefully I can fix this.
Any advice guys?
Click to expand...
Click to collapse
U flash the 11.0.4.0 fastboot rom or over twrp?
joke19 said:
U flash the 11.0.4.0 fastboot rom or over twrp?
Click to expand...
Click to collapse
Thanks for the answer. So far I only tried flashing over twrp, should I download the fastboot version and try with miflash?
Yes but look that u don't lock ur bootloader
joke19 said:
Yes but look that u don't lock ur bootloader
Click to expand...
Click to collapse
Okay, after using the miflash tool the phone boots up again. Now i'll fastboot the orangefox recovery. How do I got about flashing magisk after that so I avoid bootloop again?
beybus said:
Okay, after using the miflash tool the phone boots up again. Now i'll fastboot the orangefox recovery. How do I got about flashing magisk after that so I avoid bootloop again?
Click to expand...
Click to collapse
Backup and test. Normally no problem, only by updates with old modules

Categories

Resources