Develop Bugs

Help！i can‘t flash anything into my tablet. fastboot failed, remote: unsupported comm

Help！i can‘t flash anything into my tablet. fastboot failed, remote: unsupported comm
Good day everyone. Please help me. I am in Unicorn rom and I want to go back factory rom. I tried Nexus Tookit and ABD fastboot, but all of them errored out Fastboot failed, remote:unsupported command.
I cannot get into recovery.
Help me please.

Sway327 said:
Good day everyone. Please help me. I am in Unicorn rom and I want to go back factory rom. I tried Nexus Tookit and ABD fastboot, but all of them errored out Fastboot failed, remote:unsupported command.
I cannot get into recovery.
Help me please.
Click to expand...
Click to collapse
Are you sure that you can't reboot in twrp ..did you already try to do it manually ?
anyway if you want go back stock and you aren't able to use again NRT you need to flash manually a factory image from Google .Here is a the link with instructions ;
https://developers.google.com/android/nexus/images

if fastboot flash doesn't work you probably have fastboot locked.

brando56894 said:
if fastboot flash doesn't work you probably have fastboot locked.
Click to expand...
Click to collapse
Thanks mate. Do you know how to unlock fastboot?

ilpolpi65 said:
Are you sure that you can't reboot in twrp ..did you already try to do it manually ?
anyway if you want go back stock and you aren't able to use again NRT you need to flash manually a factory image from Google .Here is a the link with instructions ;
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thanks mate. Thanks for your reply. I tried mini ADB tool to flash it and got same result.
FAIL remote: unsupported command

Sway327 said:
Thanks mate. Thanks for your reply. I tried mini ADB tool to flash it and got same result.
FAIL remote: unsupported command
Click to expand...
Click to collapse
Are you able to get back into system? If so, run this command with an active ADB connection.
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1

Sway327 said:
Good day everyone. Please help me. I am in Unicorn rom and I want to go back factory rom. I tried Nexus Tookit and ABD fastboot, but all of them errored out Fastboot failed, remote:unsupported command.
I cannot get into recovery.
Help me please.
Click to expand...
Click to collapse
Hi, I was wondering if you were able to fix your tablet. I have this problem right now and haven't found any way of fixing it.

NYCHitman1 said:
Are you able to get back into system? If so, run this command with an active ADB connection.
Click to expand...
Click to collapse
Hi. I was wondering if you know how to fix this only through fastboot. I get the same "remote: unsupported command" message when flashing partitions and "remote: image verification failed" when using "fastboot boot twrp.img" command. Right now, I have no recovery and cannot boot to system. Locking and reunlocking bootloader doesn't change a thing and I do have the latest drivers.

viii_xvi said:
Hi. I was wondering if you know how to fix this only through fastboot. I get the same "remote: unsupported command" message when flashing partitions and "remote: image verification failed" when using "fastboot boot twrp.img" command. Right now, I have no recovery and cannot boot to system. Locking and reunlocking bootloader doesn't change a thing and I do have the latest drivers.
Click to expand...
Click to collapse
Did you get your tablet to work? I have the same problem

qAnAthemA said:
Did you get your tablet to work? I have the same problem
Click to expand...
Click to collapse
No, I haven't gotten it to work. As far as I know, there is only one way to fix it and it involves opening up the tablet, as per this post.

viii_xvi said:
No, I haven't gotten it to work. As far as I know, there is only one way to fix it and it involves opening up the tablet, as per this post.
Click to expand...
Click to collapse
Have you tried to ask Google for a USB bootable recovery + ZIP file ?

Recovery Screen Blank!

Hi,
I have a unlocked bootloader and a rooted phone(OnePlus3). I was clean flashing to a newer cm14 nightly on my oneplus 3 when I discovered a while later that my phone wouldn't boot into recovery mode. After flashing TWRP recovery, I booted onto my phone and selected recovery in the advanced reboot menu however it started to flash into fastboot whether i tried to fboot into recovery or into fastboot. So i, maybe mistakenly(i'm not sure), flashed stock recovery in command prompt and now there seems to be ,arginal improvement as I think a recovery mode may exist however the screen is blank so i have to power off by holding the button for a couple of seconds before anything appears on the screen and it does but only for fastboot and booting onto the system. Please help, I want to revert to Stock Oxygen OS with TWRP recovery but am unable to do do. I find it imperative for this to get resolved as my phone doesn't have gapps and doesn't offer much use beyond browsing. Any help would be massively appreciated.
Thanks!
P.S I apologise, in advance, if i have broken any forum rules; please tell me if I have so i will know not to do so again
P.P.S I may not understand some procedures or terms mentioned so please explain fully what to do as if I'm a complete noobie

I'm not quite understanding your situation. Can you get into fastboot or adb mode or no?
You can also skip right to http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700 and follow Method 2.
On a side note, what version of TWRP were you on? You need to be on the modified TWRP, not the official TWRP, for official 14.1 nightlies.

Hw4ng3r said:
I'm not quite understanding your situation. Can you get into fastboot or adb mode or no?
You can also skip right to http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700 and follow Method 2.
Click to expand...
Click to collapse
Yes i can get into fastboot mode on my phone but the problem present is recovery mode has a blank screen . And command prompt recognises my phone when I type fastboot devices.

Log_0 said:
Yes i can get into fastboot mode on my phone but the problem present is recovery mode has a blank screen . And command prompt recognises my phone when I type fastboot devices.
Click to expand...
Click to collapse
I'm guessing you're running official TWRP? Official 14.1 nightlies needs the modified TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21065. If you have fastboot access, you should be able to flash this version.

Hw4ng3r said:
I'm guessing you're running official TWRP? Official 14.1 nightlies needs the modified TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21065. If you have fastboot access, you should be able to flash this version.
Click to expand...
Click to collapse
By official TWRP, you mean? I don't understand that since i have no visible recovery. And thanks for the modified version... Never knew about that. Hopefully this works.
Thanks!

Log_0 said:
By official TWRP, you mean? I don't understand that since i have no visible recovery. And thanks for the modified version... Never knew about that. Hopefully this works.
Thanks!
Click to expand...
Click to collapse
Just the version that is "officially" released by TeamWin. I believe current official version is 3.0.2-1

Hw4ng3r said:
I'm guessing you're running official TWRP? Official 14.1 nightlies needs the modified TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21065. If you have fastboot access, you should be able to flash this version.
Click to expand...
Click to collapse
Thanks so much! It worked!!!
Really, thank you:laugh::laugh:

Log_0 said:
Thanks so much! It worked!!!
Really, thank you:laugh::laugh:
Click to expand...
Click to collapse
Glad to hear!
Enjoy the phone!

I destroyed my phone

I use flashfire to flash OTA but fails. Now I cannot boot system and recovery. At the same time, I didn't enable OEM unlocking, so cannot flash stock image.
What should I do?
 @xunholyx

Try to RMA

zyf0330 said:
I use flashfire to flash OTA but fails. Now I cannot boot system and recovery. At the same time, I didn't enable OEM unlocking, so cannot flash stock image.
What should I do?
@xunholyx
Click to expand...
Click to collapse
Sorry to hear that. Don't know if this will help, but it's worth a shot. If you RMA it, you are essentially telling Google that you messed up, but want them to replace it because of user error. Don't know if they'll go for that. Like the ol saying goes...you break it, you buy it
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

Badger50 said:
Sorry to hear that. Don't know if this will help, but it's worth a shot. If you RMA it, you are essentially telling Google that you messed up, but want them to replace it because of user error. Don't know if they'll go for that. Like the ol saying goes...you break it, you buy it
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Even if pay for fix, it is acceptable. It is a fact that I do wrong thing, and I am willing to pay for it.
But if can find a easy way except RMA is better.
Overall, please some advice about how to solve this. Thanks.

Does anyone know if qualcomm flash can flash image without oem unlocking?

zyf0330 said:
I use flashfire to flash OTA but fails. Now I cannot boot system and recovery. At the same time, I didn't enable OEM unlocking, so cannot flash stock image.
What should I do?
@xunholyx
Click to expand...
Click to collapse
Flashfire is a root app. It will not run without root. I think maybe you've left out a few details. Have you attempted to fastboot boot TWRP? I don't know if it will work but it's worth a try. Without access to Recovery, you can't even sideload a rescue OTA.

v12xke said:
Flashfire is a root app. It will not run without root. I think maybe you've left out a few details. Have you attempted to fastboot boot TWRP? I don't know if it will work but it's worth a try. Without access to Recovery, you can't even sideload a rescue OTA.
Click to expand...
Click to collapse
I must have forgot some what I did.
At first, I can boot twrp, but I do wipe then change slot in it. So now I am in slot which has no system and recovery, and cannot change slot in fastboot too. So I cannot do sideload.
I just don't know I can do sideload to fix when bootloader locked. And after I know it, I cannot boot recovery.?

zyf0330 said:
I must have forgot some what I did.
At first, I can boot twrp, but I do wipe then change slot in it. So now I am in slot which has no system and recovery, and cannot change slot in fastboot too. So I cannot do sideload.
I just don't know I can do sideload to fix when bootloader locked. And after I know it, I cannot boot recovery.
Click to expand...
Click to collapse
I asked if you have tried to fastboot BOOT twrp, not flash it. Put twrp.img in your ADB folder and "fastboot boot twrp.img". BTW if you have recovery, you can sideload an OTA. You can't flash a full image, but you can sideload a full OTA.
Edit: I suggest you study the new fastboot commands. It is possible to set A or B active.

v12xke said:
I asked if you have tried to fastboot BOOT twrp, not flash it. Put twrp.img in your ADB folder and "fastboot boot twrp.img". BTW if you have recovery, you can sideload an OTA. You can't flash a full image, but you can sideload a full OTA.
Edit: I suggest you study the new fastboot commands. It is possible to set A or B active.[/QUOTE
Sounds about right fasboot twrp . That has saved many phones.
If you can't figure out what to do pay a Dev to use TeamViewer to help you out.
I did that 5 years ago until I understood
ADB commands
Click to expand...
Click to collapse

boot, set active, flash, flashing of fastboot all don't work, because bootloader is locked.

Just reread your post. You can save you phone. You need latest platform tools from Google. Then 8.1 ota image from Google. Learn fastboot commands.
When people start to jump ahead and push,click,touch things they shouldn't you end up here.
Fyi all files for easy reference should be in the plat-forms tools folder.
Download them now.
So let's start:
Fastboot --set-active=_a will set to "a" partition, usually not bootable
Fastboot --set-active=_b will set to "b" partition, usually bootable
Try this:
Boot boatloader (pwr button and volume down same time from phone off state)
Fastboot --set-active=_a
On phone scroll to recovery factory reset
Then
Boot boatloader (pwr button and volume down same time from phone off state)
Fastboot --set-active=_b
On phone scroll to recovery factory reset
If USB debugging wasn't turned on, boot to recovery and and side load 8.1 ota.
Follow instructions in recovery side load menu
I think it's "adb sideload filename.ota.zip"
Factory reset after boot
Or just get platform tools and 8.0/8.1 imagine depends on what you are on and restore. Probably won't work since OEM/debugging not switched on.
If you get it up and running unlock the phone to help you in the future. Yes both OEM and critical.
Good luck

matt1313 said:
Just reread your post...
Click to expand...
Click to collapse
Well, maybe you missed OP's post #10. Locked bootloader and no recovery mode = dead in the water.

v12xke said:
Well, maybe you missed OP's post #10. Locked bootloader and no recovery mode = dead in the water.
Click to expand...
Click to collapse
I read it. He wasn't to clear.
Which phone? Unlocked version or Verizon version
Which platform tools
Windows, mac, or Linux
What does the bootloader screen say?
Fastboot devices what does it say??
There is a lot of possibilities. Messing with partions usually causes errors. Though from reading sounds like ot can be fixed.

matt1313 said:
I read it. He wasn't to clear.
Which phone? Unlocked version or Verizon version
Which platform tools
Windows, mac, or Linux
What does the bootloader screen say?
Fastboot devices what does it say??
There is a lot of possibilities. Messing with partions usually causes errors. Though from reading sounds like ot can be fixed.
Click to expand...
Click to collapse
I'm on same boat with him.. Unlocked version, latest platform tools, Windows 10, Bootloader says "Locked", fastboot devices show serial no. and good works.. But fixing is not possible... Locked bootloader and not accessible recovery... All known fastboot commands return with "........ not allowed in Lock State".. RMA seems one way for us..

[email protected] said:
I'm on same boat with him.. Unlocked version, latest platform tools, Windows 10, Bootloader says "Locked", fastboot devices show serial no. and good works.. But fixing is not possible... Locked bootloader and not accessible recovery... All known fastboot commands return with "........ not allowed in Lock State".. RMA seems one way for us..
Click to expand...
Click to collapse
Why can't you get to recovery? Stock recovery?
If so sideload ota

matt1313 said:
Why can't you get to recovery? Stock recovery?
If so sideload ota
Click to expand...
Click to collapse
Stock.. Because all possible accessing process to recovery ending with " Can't find valid operating system. The device will not restart". Same issue with sideload ota.. "Flashing is not allowed in lock state"... I have not felt so helpless for a long time.. What a chance..

matt1313 said:
I read it. He wasn't to clear.
Which phone? Unlocked version or Verizon version
Which platform tools
Windows, mac, or Linux
What does the bootloader screen say?
Fastboot devices what does it say??
There is a lot of possibilities. Messing with partions usually causes errors. Though from reading sounds like ot can be fixed.
Click to expand...
Click to collapse
The only thing that matters is that the bootloader is locked (no fastboot is possible) and no recovery mode (no adb is possible). Done. OP is from China where there is no RMA, so he is "extra" S.O.L. I recognize you are wanting to help, but those are the facts.

I understand he is more then likely SOL but I have time and want to try to help. Xmas miracle!!!! lol
what happens when you start the phone what does it say?
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
zyf0330 said:
I must have forgot some what I did.
At first, I can boot twrp, but I do wipe then change slot in it. So now I am in slot which has no system and recovery, and cannot change slot in fastboot too. So I cannot do sideload.
I just don't know I can do sideload to fix when bootloader locked. And after I know it, I cannot boot recovery.
Click to expand...
Click to collapse
If your locked how did you boot TWRP?
what did you wipe in TWRP?
Can you get to it again and select slot B?

Wait until just after Christmas, then contact Google and say you got it as a present and it says no operating system when it turns on. They're RMA it.

matt1313 said:
I understand he is more then likely SOL but I have time and want to try to help. Xmas miracle!!!! lol
what happens when you start the phone what does it say?
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
If your locked how did you boot TWRP?
what did you wipe in TWRP?
Can you get to it again and select slot B?
Click to expand...
Click to collapse
As I said, phone is booting only one screen that says "Can't find valid operating system. The device will not restart"..

[Moto X4] Boot Loop after Update to lineage-16.0-20200325, adb unauthorized

Hi, I have a bit of a problem:
I have a Moto X4 that's happily been running LineageOS for a while now. Today, I tried updating to the latest/last 16.0 nightly using the LOS updater. Since then, the device is stuck on the LOS boot animation and won't boot further.
I can boot into Recovery, but when I try to connect using adb I get "error: device unauthorized.". After googling this error message I find tutorials telling be to deactivate USB debugging or answer on-screen prompts, neither of which is possible since I can't boot the device to get into those setting or see any prompts.
Any ideas?
-M

xoth said:
Hi, I have a bit of a problem:
I have a Moto X4 that's happily been running LineageOS for a while now. Today, I tried updating to the latest/last 16.0 nightly using the LOS updater. Since then, the device is stuck on the LOS boot animation and won't boot further.
I can boot into Recovery, but when I try to connect using adb I get "error: device unauthorized.". After googling this error message I find tutorials telling be to deactivate USB debugging or answer on-screen prompts, neither of which is possible since I can't boot the device to get into those setting or see any prompts.
Any ideas?
-M
Click to expand...
Click to collapse
Magisk installed?
Can you boot into download mode?

kurtn said:
Magisk installed?
Click to expand...
Click to collapse
No, what's that?
Can you boot into download mode?
Click to expand...
Click to collapse
Well, if I boot up the device holding power and volume down it goes into the fastboot mode where I can then choose "Start", "Boot Recovery", etc. Is that the mode you mean?

xoth said:
No, what's that?
Well, if I boot up the device holding power and volume down it goes into the fastboot mode where I can then choose "Start", "Boot Recovery", etc. Is that the mode you mean?
Click to expand...
Click to collapse
Yes, sorry. From there you can install stock ROM or twrp.

kurtn said:
Yes, sorry. From there you can install stock ROM or twrp.
Click to expand...
Click to collapse
Don't I need a working (ie. not stuck on "unauthorized") adb for this? Or am I missing something?
(Sry for the many questions.)

xoth said:
Don't I need a working (ie. not stuck on "unauthorized") adb for this? Or am I missing something?
(Sry for the many questions.)
Click to expand...
Click to collapse
In fastboot mode you don't need adb. You need fastboot.

kurtn said:
In fastboot mode you don't need adb. You need fastboot.
Click to expand...
Click to collapse
Ooooooh, ok! Yeah, that makes sense. (In my head fastboot was always something using adb, not something completely different.)
Ok, so I should be able to fastboot to something like twrp, hopefully make a backup there, and then try and flash something else on it? I'll see if I manage that, thanks! :fingers-crossed:

kurtn said:
In fastboot mode you don't need adb. You need fastboot.
Click to expand...
Click to collapse
Ok, Update and new problem:
I successfully fastbooted into twrp (Once I tried another cable because the first one wouldn't... *grumble*) but when I tried to mount the data partition to make a backup before flashing, it prompted me for the pattern but despite given the correct pattern it didn't decrypt.
Since fastboot works I could just flash stock but I'd hoped to safe some stuff first.
Any ideas what might be the issue here?

xoth said:
Ok, Update and new problem:
I successfully fastbooted into twrp (Once I tried another cable because the first one wouldn't... *grumble*) but when I tried to mount the data partition to make a backup before flashing, it prompted me for the pattern but despite given the correct pattern it didn't decrypt.
Since fastboot works I could just flash stock but I'd hoped to safe some stuff first.
Any ideas what might be the issue here?
Click to expand...
Click to collapse
So you e crypted your phone. Good thing: no-one can access your data. Bad thing- you can't either

kurtn said:
So you e crypted your phone. Good thing: no-one can access your data. Bad thing- you can't either
Click to expand...
Click to collapse
Very funny. Dying of laughter over here...
But seriously, this is LOS regular file encryption, I know the correct pattern, so I'd expect something mature like TWRP to be able to mount that. But all I've found so far are open bug tickets of this happening over a range of devices.

Quick Update: I managed to get my device running again using the following steps:
1. Fastboot into twrp.
2. Go to Advanced -> ADB Sideload and activate it there.
3. Sideload an earlier LOS 16.0 nightly. (In my case, I used 16.0-20200322-nightly-payton-signed.zip.)
4. Reboot.
5. Do all the backups.

Can't boot into recovery

Hi to everyone!
I recently bought a second-hand Redmi Note 8 Pro, did a factory reset and started working on it! I found some problems, such as:
1) Google Pay doesn't work; when I try to add a credit card it says something about my phone being rooted etc.
2) I can't connect to public WiFi's through their webpage (without a normal password directly), as it won't load the respective page.
3) I can't update MIUI version as it says "Couldn't verify update".
4) I can't login into Xiaomi Services (Cloud).
I did some searching and came to the conclusion that if I root my phone maybe I can find workarounds for the above. So I tried getting into rooting.
Every tutorial started with unlocking the bootloader, but in dev options OEM Unlock is greyed out with the switch off and it says "Bootloader already unlocked". So, first step clear (right...?).
The next step is to reboot into fastboot mode and through some hacker-like commands in cmd to flash a recovery image, which I did successfully (according to screen indications and such...).
BUT!
Although everything seems perfect, my phone won't reboot into recovery, neither Mi's nor TWRP. I've tried every way (from cmd and with volume buttons etc) and many older versions, it just won't load!
It just reboots into Redmi screen (it has an unlocked locker at the top), then a little black, then again this screen, then MIUI screen, then PIN screen etc.
What should I do? Thank you in advance!

SotJake said:
Hi to everyone!
I recently bought a second-hand Redmi Note 8 Pro, did a factory reset and started working on it! I found some problems, such as:
1) Google Pay doesn't work; when I try to add a credit card it says something about my phone being rooted etc.
2) I can't connect to public WiFi's through their webpage (without a normal password directly), as it won't load the respective page.
3) I can't update MIUI version as it says "Couldn't verify update".
4) I can't login into Xiaomi Services (Cloud).
I did some searching and came to the conclusion that if I root my phone maybe I can find workarounds for the above. So I tried getting into rooting.
Every tutorial started with unlocking the bootloader, but in dev options OEM Unlock is greyed out with the switch off and it says "Bootloader already unlocked". So, first step clear (right...?).
The next step is to reboot into fastboot mode and through some hacker-like commands in cmd to flash a recovery image, which I did successfully (according to screen indications and such...).
BUT!
Although everything seems perfect, my phone won't reboot into recovery, neither Mi's nor TWRP. I've tried every way (from cmd and with volume buttons etc) and many older versions, it just won't load!
It just reboots into Redmi screen (it has an unlocked locker at the top), then a little black, then again this screen, then MIUI screen, then PIN screen etc.
What should I do? Thank you in advance!
Click to expand...
Click to collapse
Try a Fastboot rom
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

NOSS8 said:
Try a Fastboot rom
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
Hi! Thanks for answering! Since I'm super new to this may I ask? Should I try a fastboot rom or a recovery rom? Also, is it mandatory to click "Clean all" at the bottom? I don't want to wipe my data if that's possible. If I click "save user data" what will happen?

SotJake said:
Hi! Thanks for answering! Since I'm super new to this may I ask? Should I try a fastboot rom or a recovery rom? Also, is it mandatory to click "Clean all" at the bottom? I don't want to wipe my data if that's possible. If I click "save user data" what will happen?
Click to expand...
Click to collapse
Fastboot rom(read the tutorial)
In your case, perform a clean flash(clean all).
you can use https://c.mi.com/thread-3049986-1-1.html for data.

NOSS8 said:
Fastboot rom(read the tutorial)
In your case, perform a clean flash(clean all).
you can use https://c.mi.com/thread-3049986-1-1.html for data.
Click to expand...
Click to collapse
You seem sure that it will work. What exactly am I doing with this to the phone?

SotJake said:
You seem sure that it will work. What exactly am I doing with this to the phone?
Click to expand...
Click to collapse
"The next step is to reboot into fastboot mode and through some hacker-like commands in cmd to flash a recovery image, which I did successfully"
What CMD?
important:
what is the code name of your phone?
begonia or begoniain?

NOSS8 said:
"The next step is to reboot into fastboot mode and through some hacker-like commands in cmd to flash a recovery image, which I did successfully"
What CMD?
important:
what is the code name of your phone?
begonia or begoniain?
Click to expand...
Click to collapse
1) Every root tutorial says I must go in a folder (platform-tools) and open the cmd to put some commands.
2) How do I see that?

SotJake said:
1) Every root tutorial says I must go in a folder (platform-tools) and open the cmd to put some commands.
2) How do I see that?
Click to expand...
Click to collapse
I don't understand, you say
"which I did successfully"

NOSS8 said:
I don't understand, you say
"which I did successfully"
Click to expand...
Click to collapse
Yeah, according to what I should be doing and what the screen should show I did it successfully. The problem is that my phone doesn't boot into recovery!

SotJake said:
Yeah, according to what I should be doing and what the screen should show I did it successfully. The problem is that my phone doesn't boot into recovery!
Click to expand...
Click to collapse
Why do you want it to boot into recovery?

NOSS8 said:
Why do you want it to boot into recovery?
Click to expand...
Click to collapse
I'm following this guide to root my phone!

SotJake said:
I'm following this guide to root my phone!
Click to expand...
Click to collapse
Make sure your phone is a BEGONIA version.
Install https://developer.android.com/studio/releases/platform-tools
Twrp https://androidfilehost.com/?w=files&flid=318205
Put the twrp into the folder of platform-tools.
Rename the img to twrp.img
phone in Fasboot mode
CMD or Power shell
.\fastboot flash recovery twrp.img
then
Press and hold Volume Up key and Power key simultaneously
When you feel a vibration release the Power key but continue holding the Volume Up key.
or
.\fastboot boot twrp.img

NOSS8 said:
Make sure your phone is a BEGONIA version.
Install https://developer.android.com/studio/releases/platform-tools
Twrp https://androidfilehost.com/?w=files&flid=318205
Put the twrp into the folder of platform-tools.
Rename the img to twrp.img
phone in Fasboot mode
CMD or Power shell
.\fastboot flash recovery twrp.img
then
Press and hold Volume Up key and Power key simultaneously
When you feel a vibration release the Power key but continue holding the Volume Up key.
or
.\fastboot boot twrp.img
Click to expand...
Click to collapse
That's what I'm trying to tell! I have done all this, but it won't boot into twrp after all.

SotJake said:
That's what I'm trying to tell! I have done all this, but it won't boot into twrp after all.
Click to expand...
Click to collapse
is your phone a BEGONIA version?
Post the twrp flash screenshot.

NOSS8 said:
is your phone a BEGONIA version?
Post the twrp flash screenshot.
Click to expand...
Click to collapse
How can I see my phone's version?
What screenshot? I'm telling you, it won't boot into twrp!!!

SotJake said:
How can I see my phone's version?
What screenshot? I'm telling you, it won't boot into twrp!!!
Click to expand...
Click to collapse
SotJake said:
How can I see my phone's version?
Click to expand...
Click to collapse
Post your rom version like V13.0.7.0.RGKMIXM
SotJake said:
What screenshot? I'm telling you, it won't boot into twrp!!!
Click to expand...
Click to collapse
When you use cmd for flashing Twrp.

NOSS8 said:
Post your rom version like V13.0.7.0.RGKMIXM
When you use cmd for flashing Twrp.
Click to expand...
Click to collapse
MIUI V12.5.5.0.RGGMIXM
I'll try to do it once again and post it to you, although I don't really see the point. Do you want a video with the whole process?

SotJake said:
MIUI V12.5.5.0.RGGMIXM
I'll try to do it once again and post it to you, although I don't really see the point. Do you want a video with the whole process?
Click to expand...
Click to collapse
is your phone have NFC?
Yes post video.

NOSS8 said:
is your phone have NFC?
Yes post video.
Click to expand...
Click to collapse
yes it does, although it doesn't seem to work

SotJake said:
yes it does, although it doesn't seem to work
Click to expand...
Click to collapse
ok you have a BEGONIA.
Try to flash the latest rom whith this tool
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Why:
to reset your phone and be sure that it is well unlocked.