Hi guys I have a OP 7 pro bricked (boot loop), I try everything to un bricked, that is why I ask for any help. I use msm tool and install several zips but when the tool finish it still have the same problem, I can access to the fastboot mode but my bootloader is locked, so I cannot try the fastboot method cause my pc won't recognize when I connect my phone in this mode (I think that's because I need to have enable usb debugging).
I've got bad news, if your bootloader is locked and MSM tool fails you will most likely have to send it in as it will no longer be easily fixable, I unfortunately had this same issue on my OnePlus 8 and learnt the hard way.
You said that you "cannot try the fastboot method" because your PC won't recognize your phone... did you install Oneplus fastboot drivers correctly? You should be able to access your phone in fastboot, even with bootloader locked.
Try with another PC too. Just my 2 cents, sorry if this doesn't help you...
lauchiebeans said:
I've got bad news, if your bootloader is locked and MSM tool fails you will most likely have to send it in as it will no longer be easily fixable, I unfortunately had this same issue on my OnePlus 8 and learnt the hard way.
Click to expand...
Click to collapse
Launchiebeans thanks for take your time to answer, where did you send it, did you repair yours
jonsat said:
You said that you "cannot try the fastboot method" because your PC won't recognize your phone... did you install Oneplus fastboot drivers correctly? You should be able to access your phone in fastboot, even with bootloader locked.
Try with another PC too. Just my 2 cents, sorry if this doesn't help you...
Click to expand...
Click to collapse
First thank you for your time.
I though that too, but i didn't do it , maybe is because I read that in order to use this method (fastboot), oem unlock and usb debugging have to be enable on my OP 7 PRO
Ps: today I'll try again whit another pc, maybe it works, I think the Qualcomm drivers, adb drivers and OP drivers are a nightmare, who knows how many I've been downloaded those in order to make everything right
Sorry for my English I'm from Costa Rica
Sounds like he is stuck o. The older firmware that don't recognize oem unlock command. Not doing the developer preview upgrade then Ota out to regular firmware. Kinda sounds like what I started out on this t mobile one
TheMadScientist said:
Sounds like he is stuck o. The older firmware that don't recognize oem unlock command. Not doing the developer preview upgrade then Ota out to regular firmware. Kinda sounds like what I started out on this t mobile one
Click to expand...
Click to collapse
Hi MadScientist do you hav the same prob? Didi you solved?. Like I said I think the fastboot method to unbrick doesn't work for me because we need to have oem unlock and usb debugging enable on the OP. I will use another pc to discard
Ps: don't know what you mean with "older firmware"
Since I don't remember what version of firmware I have I try the older 9.5.3 to 10... On oxigen. Even i read that someone resolve his problem installing the Chinese version (hidrogenOs) I don't remember the exact name
cirmendoza said:
Hi MadScientist do you hav the same prob? Didi you solved?. Like I said I think the fastboot method to unbrick doesn't work for me because we need to have oem unlock and usb debugging enable on the OP. I will use another pc to discard
Ps: don't know what you mean with "older firmware"
Since I don't remember what version of firmware I have I try the older 9.5.3 to 10... On oxigen. Even i read that someone resolve his problem installing the Chinese version (hidrogenOs) I don't remember the exact name
Click to expand...
Click to collapse
Nm I read your post wrong. I thought you just couldn't get oem unlock enabled
cirmendoza said:
Launchiebeans thanks for take your time to answer, where did you send it, did you repair yours
Click to expand...
Click to collapse
I Ended up sending it to OnePlus and the repair was free as it was a software issue.
Related
So today i decided to downgrade from V10.2.1.0.PEEMIXM to V10.0.11.0.PEEMIFH because i was having serious battery issues on V10.2.1.0.
I should have looked into it more carefully but nope, my dumb ass decided to install the older ROM version via the Updater in Settings and it bricked my device in the process.
Now my device is stuck on boot with the message "The system has been destroyed. Press power button to shutdown".
I have the global version with the bootloader locked. The only thing i have access to now is fastboot.
Any ways i can recover from this? Any help is greatlyyy appreciated.
You can try to unlock bootloader with fastboot mode, but i'm not sure that works because the system has been destroyed and your account has been destryed too. I think, the best for you, is to send it in warranty for repair. I have bricked a Redmi Note 4 like that and even with the test point method, he has never work again.
boxof said:
So today i decided to downgrade from V10.2.1.0.PEEMIXM to V10.0.11.0.PEEMIFH because i was having serious battery issues on V10.2.1.0.
I should have looked into it more carefully but nope, my dumb ass decided to install the older ROM version via the Updater in Settings and it bricked my device in the process.
Now my device is stuck on boot with the message "The system has been destroyed. Press power button to shutdown".
I have the global version with the bootloader locked. The only thing i have access to now is fastboot.
Any ways i can recover from this? Any help is greatlyyy appreciated.
Click to expand...
Click to collapse
If you can find the fastboot version of the ROM you were on before downgrading just flash it with miflash
Azev said:
You can try to unlock bootloader with fastboot mode, but i'm not sure that works because the system has been destroyed and your account has been destryed too. I think, the best for you, is to send it in warranty for repair. I have bricked a Redmi Note 4 like that and even with the test point method, he has never work again.
Click to expand...
Click to collapse
Fortunately for me i was able to unlock the bootloader. Likely because i registered my device since i first got it (about 1 month now), so i think i must have met the wait time requirement and it was fine that i couldn't access the system.
Mackay53 said:
If you can find the fastboot version of the ROM you were on before downgrading just flash it with miflash
Click to expand...
Click to collapse
I tried miflash the first time with my bootloader still locked but miflash refused to work with a locked bootloader.
So i tried again with my bootlocker unlocked and it worked as expected.
Lesson learnt. All is well again and i'm able to keep my bootloader locked with the "flash_all_lock" option.
Thank you so much for all the help!
boxof said:
Fortunately for me i was able to unlock the bootloader. Likely because i registered my device since i first got it (about 1 month now), so i think i must have met the wait time requirement and it was fine that i couldn't access the system.
I tried miflash the first time with my bootloader still locked but miflash refused to work with a locked bootloader.
So i tried again with my bootlocker unlocked and it worked as expected.
Lesson learnt. All is well again and i'm able to keep my bootloader locked with the "flash_all_lock" option.
Thank you so much for all the help!
Click to expand...
Click to collapse
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
nsynsy said:
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
Click to expand...
Click to collapse
Unless you have got unlock permission and linked phone to account you can't unlock.
Unlock like how you would normally - put the phone into fastboot, connect it to your PC, and run the mi unlock tool. For this to work, hopefully you have associated your device to a mi account and have met the unlock requirements ie. surpassed the waiting period. Otherwise you're out of luck as there is no other ways (that i know of) to register the device now as you can't get into the system.
As a last resort you can try opening up the back of the phone and flash new firmware using the test point if unlocking is not possible. I'm not sure how or where the testing point is located exactly, but it's a possible solution that i found while researching when my device was bricked. Good luck!
nsynsy said:
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
Click to expand...
Click to collapse
u say u can only access to fastboot..
How about pressing volume up and power button? can u enter in stock mi recovery with mi assistant options?
Hello,
I couldn't unlock the bootloader as the OEM unlocking's disabled and i can't access system! Everything's erased!
Any help????
A bit more info might be helpful mate.
What did you do to arrive at the situation you are in?
Can your pc see your device via ADB and if so what are you using: latest platform tools or toolkit?
Can you boot to stock recovery or bootloader?
Without any of the above info its going to be extremely difficult for anyone to give any kind of answer.
junglism93 said:
A bit more info might be helpful mate.
What did you do to arrive at the situation you are in?
Can your pc see your device via ADB and if so what are you using: latest platform tools or toolkit?
Can you boot to stock recovery or bootloader?
Without any of the above info its going to be extremely difficult for anyone to give any kind of answer.
Click to expand...
Click to collapse
The device isn't recognized via ADB.
I can boot to Bootloader
The phone was working fine with the latest google stock android 10, i decided to lock the bootloader cuz the phone was getting overheated so i thought it'd be a good idea to lock the bootloader. Prior to do that, it asked me to erase everything! I erased everything and when i tried to reinstall the stock image it asked me to unlock the bootloader!!
The problem is that USB debugging isn't enabled and the phone is empty with no system!
eldeen said:
The device isn't recognized via ADB.
I can boot to Bootloader
The phone was working fine with the latest google stock android 10, i decided to lock the bootloader cuz the phone was getting overheated so i thought it'd be a good idea to lock the bootloader. Prior to do that, it asked me to erase everything! I erased everything and when i tried to reinstall the stock image it asked me to unlock the bootloader!!
The problem is that USB debugging isn't enabled and the phone is empty with no system!
Click to expand...
Click to collapse
Ouch! That's a right old situation you have there mate, with no OS installed a locked bootloader and no ADB function I'd have to say your phone is non recoverable!
Sorry mate but I can't see anyway out of that lot.
Maybe someone else a bit more knowledgeable might chip in but I'm deffo out of ideas.
junglism93 said:
Ouch! That's a right old situation you have there mate, with no OS installed a locked bootloader and no ADB function I'd have to say your phone is non recoverable!
Sorry mate but I can't see anyway out of that lot.
Maybe someone else a bit more knowledgeable might chip in but I'm deffo out of ideas.
Click to expand...
Click to collapse
Thanks for help anyway,
But there must a solution to this! I mean my phone isn't under warranty and I'm willing to go for paid services to unlock the bootloader!
eldeen said:
Thanks for help anyway,
But there must a solution to this! I mean my phone isn't under warranty and I'm willing to go for paid services to unlock the bootloader!
Click to expand...
Click to collapse
Try switching slots, assuming the pixel is an A/B device. Maybe you still have a bootable system in your other slot and I don't think you need an unlocked bootloader to switch slots
AndroidNazi said:
Try switching slots, assuming the pixel is an A/B device. Maybe you still have a bootable system in your other slot and I don't think you need an unlocked bootloader to switch slots
Click to expand...
Click to collapse
Thanks for help, but could you please show me how to do that?
eldeen said:
Thanks for help, but could you please show me how to do that?
Click to expand...
Click to collapse
Make sure you have the latest fastboot. On the bootloader your phone will either say "slot a" or "slot b" and you should type "fastboot --set-active=b" if you are on slot a or "fastboot --set-active=a" if you are on slot b
still didn't fix the problem... any probable solutions please?
Hi community
First Thanks to the people who take time to help, and admin that create that forum. Im always glad to see that s there is still people caring about helping each other
I come to you cause I spent the last 2 days trying to fix my brand new phone.
Brand : Xiaomi
Model : Mi ultra
My Computer : MacBook Air
Problem : "The system has been destroy"
Other problem :
- USB debugging OFF (not able to access to the phone in any way)
- Bootloader Locked
How its happen :
After installing an EU Rom, I re locked the boot loader using Adb... And it crashed.
I tried almost everything you find on internet using a Mac and till now nothing worked.
I tried to unlock the boot loader using ADB, which one the only thing who seems to be working and I got an error message saying that the Miunlocktools was too old ... ?
The token was available, as I already unlock it.
Does anyone know how I can switch ON the debugging mode without accessing my phone, or Unlock the boot loader using my Mac.
It seems there is solution possible but using windows computer, and tbh I will not buy a computer just for that.. for the moment
Thanks in advance to everyone
PS : I will offer 50USD straight in BTC to the one who will provide me the solution that will help me to fix it
Locking / unlocking a phone's bootloader is done by means of Fastboot, not ADB.
ADB & Fastboot are 2 completely different things. Don't confuse them.
AFAIK you can't enable ADB ( USB debugging ) from outside, this can only get enabled from inside ( Android Settings -> Developer options ) unless one creates/provides a flashable, properly signed ZIP that contains the code ( read: update-binary script ) to rewrite device's build.prop file entries accordingly.
BTW: A locked bootloader always tries to run device's Stock ROM.
Thanks for your quick answer. In other word, is it possible ? I am looking for what you say.
If I rewrite it, will I be able to switch it ON then ?
Im not at all a professional , that's my first step in this "world". It seems difficult, I will need to read a lot I think
What do you think about the EDL cable also, do you think it can work ?
thxx
Kayzers0ze said:
What do you think about the EDL cable also, do you think it can work ?
Click to expand...
Click to collapse
IDK.
Never have bricked a phone. And I never owned a Xiaomi device.
locking a bootloader (at least in xiaomi phones )results in the phone being reformatted and the stock rom is installed
also try installing the newest version of miunlock https://en.miui.com/unlock/download_en.html
you might have to wait 7 days or less or more or might not have to
historys said:
locking a bootloader (at least in xiaomi phones )results in the phone being reformatted and the stock rom is installed
also try installing the newest version of miunlock https://en.miui.com/unlock/download_en.html
you might have to wait 7 days or less or more or might not have to
Click to expand...
Click to collapse
Hi
I re locked the boot loader myself so I unlocked it before
Thats the version I have but in the terminal I got a message saying version is too old...
I am trying to unlock my nord ce 2 bootloader but everytime I try to access bootloader mode, it says something like Unlock_Verify_device ok and then reboots
how can I unlock the bootloader? Same happens on my nord 2. Oem unlocking is enabled and I have no selection of advanched startup options. I have magisk boot.img to flash
Can't say I experienced that myself. The message you got looks promising. The 'unlock_verify_device ok' message means you're getting to fastboot. But I'm not sure why it's rebooting. Do you have enough time to run the command 'fastboot devices'?
Also, what version is your firmware?
Here is the guide I used when I was unlocking the bootloader: https://www.droidwin.com/how-to-unlock-bootloader-on-oneplus-nord-ce-2/
I am running android 12 beta on oxygenos
Edit: fastboot doesn´t even find the device
Oh, now it tells that serial is not match. what's going on?
so? Can anyone help? Phone keeps saying that serial is not match and then reboots. Is this phone just a joke or something? Gonna buy samsung if yes.
What model is your phone? I wasn't aware of the Android 12 beta being available for the Nord CE 2. Another thing to try is this tutorial to manually install the OnePlus drivers: https://www.droidwin.com/fix-android-device-not-showing-in-fastboot-mode/
Was looking on the nord ce 1 xda Forum. It's only recently that a few roms and twrp are starting to appear, so there is hope. IMO oneplus need to take £$50 off the price, more users = more chance of getting more development
mr_munch said:
Can't say I experienced that myself. The message you got looks promising. The 'unlock_verify_device ok' message means you're getting to fastboot. But I'm not sure why it's rebooting. Do you have enough time to run the command 'fastboot devices'?
Also, what version is your firmware?
Here is the guide I used when I was unlocking the bootloader: https://www.droidwin.com/how-to-unlock-bootloader-on-oneplus-nord-ce-2/
Click to expand...
Click to collapse
I don't have fastboot on my device Nord ce 2 ..when I type fastboot reboot bootloader then it directly reboot into my device ..Please somebody help me.Im on current Android 12.1 version
neilop7 said:
I don't have fastboot on my device Nord ce 2 ..when I type fastboot reboot bootloader then it directly reboot into my device ..Please somebody help me.Im on current Android 12.1 version
Click to expand...
Click to collapse
Fastboot is stuffed on this device. There's no longer a way to make fastboot work.
burningcreation said:
Fastboot is stuffed on this device. There's no longer a way to make fastboot work.
Click to expand...
Click to collapse
I wanna unlock bootloader..is there any way to unlock ?
neilop7 said:
I wanna unlock bootloader..is there any way to unlock ?
Click to expand...
Click to collapse
No unfortunately.
burningcreation said:
No unfortunately.
Click to expand...
Click to collapse
Did you able to unlock bootloader?
neilop7 said:
Did you able to unlock bootloader?
Click to expand...
Click to collapse
No I am not able to unlock the bootloader either. There is currently nothing we can do.
Hi everyone, any update on this? Did someone manage to unlock the bootloader?
If I'm not mistaken. You can rollback to android 11 to get it back.
I'm currently facing the same problem, so I tried rolling back and have downloaded over 20 rollback zips now, and extracted them. All won't work, it reboots in recovery. And it is like fastboot just doesn't exist. So yeah they probably messed it up.
I'm so sad, I switched from Iphone to Oneplus partly because of the rooting options. So sad
Can I do this trough adb or not?
NiekKamer0105 said:
I'm currently facing the same problem, so I tried rolling back and have downloaded over 20 rollback zips now, and extracted them. All won't work, it reboots in recovery. And it is like fastboot just doesn't exist. So yeah they probably messed it up.
I'm so sad, I switched from Iphone to Oneplus partly because of the rooting options. So sad
Can I do this trough adb or not?
Click to expand...
Click to collapse
You don't extract it though. You just rename it by removing the _Rollback at the end.
See here: https://droidwin.com/downgrade-oneplus-nord-ce-2-from-android-12-to-android-11/
Hello.
Recently i flashed this: ROM in my Redmi 10C, and now I can't unlock the bootloader to flash it back to the stock ROM. Its not exactly bricked, but I can't root it. Why do I need to root it? Because you can do all the fun things only if you have root of course!
My question is:
Is the Redmi 10C going to let me flash it through EDL mode with QPST/QFIL (Qualcomm emergency tools for dumdums like me)
Or am I forced to go to someone with an authorized MI account (and that person can flash it). Alternatively, can I get my MI account authorized, or at least borrow one only for this.
Thank you for reading, and good day to you.
dthslce42 said:
Hello.
Recently i flashed this: ROM in my Redmi 10C, and now I can't unlock the bootloader to flash it back to the stock ROM. Its not exactly bricked, but I can't root it. Why do I need to root it? Because you can do all the fun things only if you have root of course!
My question is:
Is the Redmi 10C going to let me flash it through EDL mode with QPST/QFIL (Qualcomm emergency tools for dumdums like me)
Or am I forced to go to someone with an authorized MI account (and that person can flash it). Alternatively, can I get my MI account authorized, or at least borrow one only for this.
Thank you for reading, and good day to you.
Click to expand...
Click to collapse
First, be absolutely sure, which model, exactly is your device, check the code name of your device, and which ROM suits for it.
Still, not clear, how did you get to flash a custom ROM, with the bootloader locked?
TThThank you f
SubwayChamp said:
First, be absolutely sure, which model, exactly is your device, check the code name of your device, and which ROM suits for it.
Still, not clear, how did you get to flash a custom ROM, with the bootloader locked?
Click to expand...
Click to collapse
Thank you for answering. I apologize, the bootloader isn't locked. It's just that I cannot check the OEM unlock option (it's greyed out, on the system i installed).
First. I rooted my redmi 10c (still had the stock/default ROM)
Then. I proceeded to flash it (with twrp) with the ROM I quoted before. Although I suspect it didn't completed installation, because it doesn't have some features that all ROMs have (thank god it still has networking & basic telephony functions). And now i cannot root it, because i can't check 'OEM unlock' option.
I researched thoroughly and the only way I see fit (at the moment) is to use the EDL mode and the official 'MI Flash Pro tool'.
BUT according to various sources, the Redmi 10c falls in the category of models that need an Authorized MI Account (log into the official tool) to properly flash a system through EDL mode.
I want to restore it to the stock/default ROM. But to do that through EDL i need an authorized account.
My doubt is simple: do I really need the 'MI Flash Tool Pro' ? Or can I just enter EDL mode, use QPST/QFIL (also an official tool) and do it without the need to log in? (authorized).
Thank you for keeping up!
dthslce42 said:
TThThank you f
Thank you for answering. I apologize, the bootloader isn't locked. It's just that I cannot check the OEM unlock option (it's greyed out, on the system i installed).
First. I rooted my redmi 10c (still had the stock/default ROM)
Then. I proceeded to flash it (with twrp) with the ROM I quoted before. Although I suspect it didn't completed installation, because it doesn't have some features that all ROMs have (thank god it still has networking & basic telephony functions). And now i cannot root it, because i can't check 'OEM unlock' option.
I researched thoroughly and the only way I see fit (at the moment) is to use the EDL mode and the official 'MI Flash Pro tool'.
BUT according to various sources, the Redmi 10c falls in the category of models that need an Authorized MI Account (log into the official tool) to properly flash a system through EDL mode.
I want to restore it to the stock/default ROM. But to do that through EDL i need an authorized account.
My doubt is simple: do I really need the 'MI Flash Tool Pro' ? Or can I just enter EDL mode, use QPST/QFIL (also an official tool) and do it without the need to log in? (authorized).
Thank you for keeping up!
Click to expand...
Click to collapse
There are some confusing concepts here.
Firstly, a locked device doesn´t admit custom images, OK, I must assume you know that, next, if you didn´t expressly re-locked it, then it remains unlocked, the toggle unlock OEM grayed out, is not a problem, always that it is checked, it means your device is still unlocked.
Anyway, if the doubt persists, can you provide some screenshots.
SubwayChamp said:
There are some confusing concepts here.
Firstly, a locked device doesn´t admit custom images, OK, I must assume you know that, next, if you didn´t expressly re-locked it, then it remains unlocked, the toggle unlock OEM grayed out, is not a problem, always that it is checked, it means your device is still unlocked.
Anyway, if the doubt persists, can you provide some screenshots.
Click to expand...
Click to collapse
Mmm, i assumed the the device was still unlocked because it should persist (after you flash it any number of times you want). That, and when I restart it it shows an 'unlocked' padlock icon.
I'm going to post some screenshots.
Pic 2: the 'OEM unlock' should appear with the other debugging (Depuración) options, it doesn't.
Pic 1: it only appears when I search for it, when i tap on it it doesn't do anything.
(Sorry for the Spanish)
dthslce42 said:
Pic 2: the 'OEM unlock' should appear with the other debugging (Depuración) options, it doesn't.
Pic 1: it only appears when I search for it, when i tap on it it doesn't do anything.
(Sorry for the Spanish)
Click to expand...
Click to collapse
I guess you want to referring to OEM unlock toggle, that it´s not present. Again, that the toggle is not present, doesn´t mean, your bootloader is locked, most probably, the ROM you´re actually on is not showing, and nothing more, strange, but as it is.
So, you can do what you want, as the bootloader is unlocked.
You can be absolutely sure, by sending device to fastboot mode and doing fastboot oem device-info
SubwayChamp said:
I guess you want to referring to OEM unlock toggle, that it´s not present. Again, that the toggle is not present, doesn´t mean, your bootloader is locked, most probably, the ROM you´re actually on is not showing, and nothing more, strange, but as it is.
So, you can do what you want, as the bootloader is unlocked.
You can be absolutely sure, by sending device to fastboot mode and doing fastboot oem device-info
Click to expand...
Click to collapse
Mmmmm. I forgot to clarify... It doesn't even let me transfer files trough USB. So fastboot mode is locked(?). You could say that the phone is kinda bricked. Since I have 0 clues on how to change the ROM.
But back to the core of this thread.
Is it advisable to use any of the tools: QPST/QFIL(Qualcomm), in EDL mode to change the ROM.
I ask here because i hope someone knows if using the Qualcomm tools is gonna work.
Since xiaomi tools ABSOLUTELY require an authorized account to complete the process (and not hardbrick the phone pls).
dthslce42 said:
Mmmmm. I forgot to clarify... It doesn't even let me transfer files trough USB. So fastboot mode is locked(?). You could say that the phone is kinda bricked. Since I have 0 clues on how to change the ROM.
But back to the core of this thread.
Is it advisable to use any of the tools: QPST/QFIL(Qualcomm), in EDL mode to change the ROM.
I ask here because i hope someone knows if using the Qualcomm tools is gonna work.
Since xiaomi tools ABSOLUTELY require an authorized account to complete the process (and not hardbrick the phone pls).
Click to expand...
Click to collapse
Man, please, put all the attention, to both, to me, and to your words. I don´t understand at all, why you say you´re bricked or something, or you say, you don´t know how to put another ROM onto your device when you already flashed in the past a custom ROM, Why you should use Qfil/QPST or other of those unbricking tool, if...
Your device has the bootloader UNLOCKED and you DON´T need to put the Xiaomi ROM into your device, an authorized account is needed when you need to flash the OFFICIAL ROM, not for any other custom ROM, in your case, you can flash any other custom ROM as you already did it in the past.
Better tell me:
1-Can your device be power on?
2-Can your device enter to TWRP, and/or fastboot mode?
3-What exactly do you want to achieve right now?
"1-Can your device be power on?"
Yes.
"2-Can your device enter to TWRP, and/or fastboot mode?"
It can enter fastboot mode. But not TWRP, it was erased. I didn't realize until it was too late.
"3-What exactly do you want to achieve right now?"
Either change to other ROM. Or reinstall the current one. But I don't know how.
dthslce42 said:
"1-Can your device be power on?"
Yes.
"2-Can your device enter to TWRP, and/or fastboot mode?"
It can enter fastboot mode. But not TWRP, it was erased. I didn't realize until it was too late.
"3-What exactly do you want to achieve right now?"
Either change to other ROM. Or reinstall the current one. But I don't know how.
Click to expand...
Click to collapse
Ok, if you have a fastboot mode working fine, then you just have to reinstall the recovery available for your device, as you did it once, then, rebooting to it, just flash the ROM available for your device. Jut repeat that process.
SubwayChamp said:
Ok, if you have a fastboot mode working fine, then you just have to reinstall the recovery available for your device, as you did it once, then, rebooting to it, just flash the ROM available for your device. Jut repeat that process.
Click to expand...
Click to collapse
I'm really grateful mate. What you told me about the EDL mode (that i can install any ROM with the Qualcomm tool, as long as it's not the official from Xiaomi) was really helpful. Thank you!
The phone can enter fastboot mode, but it's not recognized by any PC. (That's why I say the 'OEM unlock' option it's the most likely culprit) so -i think- it cannot be done that way.
All drivers were installed (automatically, the unlock tool has an option to scan and install the correct drivers, and manually)
dthslce42 said:
I'm really grateful mate. What you told me about the EDL mode (that i can install any ROM with the Qualcomm tool, as long as it's not the official from Xiaomi) was really helpful. Thank you!
The phone can enter fastboot mode, but it's not recognized by any PC. (That's why I say the 'OEM unlock' option it's the most likely culprit) so -i think- it cannot be done that way.
All drivers were installed (automatically, the unlock tool has an option to scan and install the correct drivers, and manually)
Click to expand...
Click to collapse
OK, from what I understood, you want to follow the guidelines provided, I mean, flash the TWRP again using fastboot, then boot to it, and from there can flash any custom ROM...
If I´m right, and this is correct, you are feeling that you´re stuck in fastboot mode but the device is not recognized as of now...
Unlock tool and also the Xiaomi Unlock tool or even the Xiaomi (Pro) tool, has the correct fastboot drivers for any Xiaomi device, BUT, the issue is "simply" that you have to "call" that specific drivers and "match" it to your device, the right drivers are already there, from within a long list of all of the device (compatible or not) drivers...
I mean, you just have to connect your device in fastboot mode, you have to see, either the Xiaomi bunny (in older devices) or the fastboot legend into your screen, then just update the drivers...
Keep the device manager windows opened in a part of your PC, and check the changes when you connect your device, then you have to see, some driver that appeared, and update it from the list following something like the images I´ll upload, the guide I made is to update EDL drivers, but apply the part you need, in order to get Android Bootloader Interface, note that your device has not to be listed under Port COM like in EDL.
When you uncheck this option, then you can find it from the list.