Develop Bugs

[Q] stuck on htc quietly brilliant screen

Hello everyone, I made a mistake (I am a big noob) and I don't know how to fix it.
I wanted to have fresh phone (real factory reset) to back-up and start over, so in recovery mode (interim one from paul) I wiped data, cache partition and I also formated cache,data, sdcard and system.
Now, I am stuck on htc quietly brilliant screen, I have access to hboot, recovery etc. I have been looking for a solution for 2 days without succes, I am sad.
Can someone help please ? thanks guys.

You wiped the system so there is no android on there!
Eirher download a new Rom and flash or relock bootloader and use ruu
Sent from my HTC One X using xda premium

Thanks sir, I'll try.

sotirios said:
Thanks sir, what can I do ? Which part I did wrong ? thanks again
Click to expand...
Click to collapse
The part you did wrong: It's true that you wipe (dalvik) cache and data before flashing a custom rom. That will perform a factory reset. Wiping system means deleting android itself, as stated before. That's what you did wrong.
Now, we can't know why you wanted to start all over again, but assuming you already flashed a custom recovery, you wanted to install a custom rom. Just go ahaed and do so, your problem will be fixed.

thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card

sotirios said:
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
Click to expand...
Click to collapse
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push path/to/custom/rom /sdcard
or for linux/mac:
sudo ./adb push path/to/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too

dobbi10k said:
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard
or for linux/mac:
sudo ./adb push pfad/zu/einer/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
Click to expand...
Click to collapse
That wont work as ADB does not work on any of the custom recoveries at the moment. Im stuck in the same situtation at the mo and as phone is branded cant get the RUU to reflash so just playing the waiting game until either ADB/USB mount available in recovery or S-Off available.

See my thread in development thread
http://forum.xda-developers.com/showthread.php?t=1599748
Sent from my HTC One X using XDA

Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.

"Eirher download a new Rom and flash"
I can't flash, my ssd is wiped too and i can't mount usb with this custom recovery
"That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard"
It doesn't work, it doesn't find my device, even with the adb devices command

sotirios said:
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
Click to expand...
Click to collapse
Go to development thread then shipped ruu ans download specific to ur phone. Follow and Job done
Sent from my HTC One X using XDA

Same problem here! I unfortunatly erase everything from my one x and i can't restore anything!! How can i solve it?? My device is unlocked but stay in s-on mode! Why? From fastboot i can't flash anything! Help!!

Hello folks, problem solved by following leejames instructions :
flash stock recovery
relock bootloader
use ruu
I'm so happy. Thanks.

Mee too!! Thanks a lot!! I'm very very very very very very very very very very very very very very happy!!
1 flash stock recovery
2 relock bootloader
3 use ruu
It works fine!!

I do exactly the same thing , but half way through the RUU process it gives me an error saying i need the correct RUU. anyone can help ?

All you have to do is grab an RUU, run it. now on your pc search for %temp%in there locate ROM.zip. Extract the boot.img and system.img. and push them thru fastboot
Code:
fastboot flash boot boot_signed.img
Code:
fastboot flash system system.img
Code:
adb reboot

i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.

mahdibassam said:
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
Click to expand...
Click to collapse
Is your bootloader unlocked?

When I do it with an unlocked bootloader the error changes to this:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s

Nobody can help me?!! ((

Factory reset is impossible

In short, I'm trying to factory reset the phone to it's default settings, but every attempt is met with a failed attempt. Here's the specs
HTC Incredible
Android 2.2
Locked
S-ON
Hboot 1.02.000
Software: 3.26.605.1
Baseband: 2.15.00.07.28
Upgrading using the RUU file, PB3120000_Incredible_C_hboot_1.02.0000_4.08.605.2.exe, does nothing because even when it says it succeeds, the software version is the same. Tried the PB31IMG.zip method doesn't work because I get the error, "Main version is older". Going into recovery mode and resetting from there does nothing either because that fails.
The closest method I've seen which resembles mine is from this thread, but because the phone is deactivated I can't access the market to download and install rom manager to fix what could be a corrupted recovery? On top of that, I spent over an hour working with SDK, and came to the conclusion that I'm out of my depth. If anyone could point me in the right directions.
Edit: Figured out I had the wrong zip file so when I finally got it to update to 4.08.605.2 image, the boot screen is stuck at "HTC Incredible" splash screen, so I'm to assume I bricked it?

S_K_I said:
In short, I'm trying to factory reset the phone to it's default settings, but every attempt is met with a failed attempt. Here's the specs
HTC Incredible
Android 2.2
Locked
S-ON
Hboot 1.02.000
Software: 3.26.605.1
Baseband: 2.15.00.07.28
Upgrading using the RUU file, PB3120000_Incredible_C_hboot_1.02.0000_4.08.605.2.exe, does nothing because even when it says it succeeds, the software version is the same. Tried the PB31IMG.zip method doesn't work because I get the error, "Main version is older". Going into recovery mode and resetting from there does nothing either because that fails.
The closest method I've seen which resembles mine is from this thread, but because the phone is deactivated I can't access the market to download and install rom manager to fix what could be a corrupted recovery? On top of that, I spent over an hour working with SDK, and came to the conclusion that I'm out of my depth. If anyone could point me in the right directions.
Edit: Figured out I had the wrong zip file so when I finally got it to update to 4.08.605.2 image, the boot screen is stuck at "HTC Incredible" splash screen, so I'm to assume I bricked it?
Click to expand...
Click to collapse
If you can get to hboot, its not bricked. Have you tried a factory reset from hboot since doing the update?

cmlusco said:
If you can get to hboot, its not bricked. Have you tried a factory reset from hboot since doing the update?
Click to expand...
Click to collapse
Yes, I can get to hboot, and unfortunately doing a factory reset from there didn't work either? What are my options now you think, since I ran out of ideas a while ago.

S_K_I said:
Yes, I can get to hboot, and unfortunately doing a factory reset from there didn't work either? What are my options now you think, since I ran out of ideas a while ago.
Click to expand...
Click to collapse
So am I out of options at this point, because I've exhausted every resource I could find.

S_K_I said:
So am I out of options at this point, because I've exhausted every resource I could find.
Click to expand...
Click to collapse
Try this ruu thru hboot http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip. If that dosent work i would unlock your bootloader with http://htcdev.com/bootloader. Then flash a custom recovery. Then from recovery try to do a full wipe and a flash of a rom.

How do I get access to the sim card from my computer and install the zip if the phone won't boat? Or is there a way I can still do this through hboot?

S_K_I said:
How do I get access to the sim card from my computer and install the zip if the phone won't boat? Or is there a way I can still do this through hboot?
Click to expand...
Click to collapse
Well to put the PB file on the sdcard you would need to remove it from the phone, and then use a pc to put the file on there. You would most likley need an adapter, as most card readers dont do micro sd. However you can use fastboot to flash a pb file. Place the PB file on your pc in the same folder as fastboot.exe. Then type the folowing one at a time.
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip PB31IMG.zip
Also unlocking the bootloader, and flashing a recovery only requires the use of fastboot.
EDIT: I guess i should have asked first if you have fastboot adb and their drivers setup on your pc? And if you know how to use them?

Sorry bout not mentioning I'm still a noob at this but for the most part I'm pretty tech savvy (just with iphones shhhh), I was in the middle of updating my progress, and I just finished installing SDK and recovery-clockwork-5.0.2.0-vivo.img, so now after installing the PB zip udate I got this message, "Failed (remote: 99 unknown fail)". What version of PB is this anyways?

S_K_I said:
Sorry bout not mentioning I'm still a noob at this but for the most part I'm pretty tech savvy (just with iphones shhhh), I was in the middle of updating my progress, and I just finished installing SDK and recovery-clockwork-5.0.2.0-vivo.img, so now after installing the PB zip udate I got this message, "Failed (remote: 99 unknown fail)". What version of PB is this anyways?
Click to expand...
Click to collapse
The latest 4.08.605.15. Wait that is not a correct recovery for this phone. So you are unlocked now? If so that is why the fastboot ruu failed, the bootloader must be locked.

Yea I googled it not too long ago and figured that out. So what's the right version then?

S_K_I said:
Yea I googled it not too long ago and figured that out. So what's the right version then?
Click to expand...
Click to collapse
CWM - http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/
Or
TWRP - http://dinc.does-it.net/Recoveries/TWRP_2.4.4.0/

I need to do some errands but I"ll be back in 30 minutes, Just letting you know in case you're waiting on me, but irregardless thanks for the help so far and I apologize having to put up with me. Bueno, ttys..

OK, I think I just made things worse. First off, I didn't know I shouldn't of unlocked it because now I instead of getting that error 99 when trying to mount the PB, I get the message saying, "bootloader err command error !!!" after I enter "fastboot oem rebootruu". And trying to mount it while it's unlocked I get the message, "FAILED (remote: not allowed)". Sad face all around. Also, those 2 links you gave me are broken or just aren't working for me, so I'll try to find other links in the mean time. But as far as re-locking the phone, I still get the same messages as above.

S_K_I said:
OK, I think I just made things worse. First off, I didn't know I shouldn't of unlocked it because now I instead of getting that error 99 when trying to mount the PB, I get the message saying, "bootloader err command error !!!" after I enter "fastboot oem rebootruu". And trying to mount it while it's unlocked I get the message, "FAILED (remote: not allowed)". Sad face all around. Also, those 2 links you gave me are broken or just aren't working for me, so I'll try to find other links in the mean time. But as far as re-locking the phone, I still get the same messages as above.
Click to expand...
Click to collapse
You can relock by typing in fastboot
Code:
fastboot oem lock
Or your saying you already tried that and it have an error?
The links should be working again.
---------- Post added at 10:34 PM ---------- Previous post was at 10:29 PM ----------
Wait, does your hboot still have the same info you posted earlier as far as software version and baseband? In othet words are you still on android 2.2? And do you have a working recovery now?

C:\Android>fastboot oem rebootruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.009s
C:\Android>fastboot flash zip PB31IMG.zip
sending 'zip' (3064 KB)...
OKAY [ 0.535s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.965s
This is while it's relocked btw.

S_K_I said:
C:\Android>fastboot oem rebootruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.009s
C:\Android>fastboot flash zip PB31IMG.zip
sending 'zip' (3064 KB)...
OKAY [ 0.535s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.965s
This is while it's relocked btw.
Click to expand...
Click to collapse
The RUU has to be capital letters in that first command. (fastboot rebootRUU)
Try with this one http://dinc.does-it.net/Stock_Images/4.08.605.2/PB31IMG.zip, i forgot that last one was built and not official.

S_K_I said:
C:\Android>fastboot oem rebootruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.009s
C:\Android>fastboot flash zip PB31IMG.zip
sending 'zip' (3064 KB)...
OKAY [ 0.535s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.965s
This is while it's relocked btw.
Click to expand...
Click to collapse
I got 4.08.605.2 installed, with radio 2.15.10.12.20. And if I understand you correctly regarding the recovery, I got clockwork installed and working.

S_K_I said:
I got 4.08.605.2 installed, with radio 2.15.10.12.20. And if I understand you correctly regarding the recovery, I got clockwork installed and working.
Click to expand...
Click to collapse
Well you could try thay ruu in the post above, or go to recovery, do a wipe, and flash a rom.
EDIT: To flash a rom thru recovery you would need to unlock again with the bin file.
---------- Post added at 10:50 PM ---------- Previous post was at 10:44 PM ----------
Lol we kind of have two different things going here, and they kind of conflict. So either stay locked and try that othet ruu, or unlock again and wipe and flash a rom with cwm.

Ok, it succesfully mounted that last image you linked to me. Only thing now after it finished on the command prompt, looking at the phone now and it's sitting there with the HTC logo, a black background, and a finished green bar. Should I just reboot it or keep waiting?

S_K_I said:
Ok, it succesfully mounted that last image you linked to me. Only thing now after it finished on the command prompt, looking at the phone now and it's sitting there with the HTC logo, a black background, and a finished green bar. Should I just reboot it or keep waiting?
Click to expand...
Click to collapse
Keep waiting, mabey for 10 15 min. It may take awile and reboot a few times.

[Q] Bricked ?? Please Please Please Help

Hi
I have tried going back to Sense stock after trying out GPE edition lollipop flavour.
Unfortunately somewhere along the way something has gone horrible wrong and I'm now stuck in a bootloop with a Red Triangle
My bootloader is currently locked, althougth I am S-Off. I can still access fastboot and RUU but the problem is when I try to flash standard or twrp recovery i get the following error message
From RUU
./fastboot flash recovery recov.img
target reported max download size of 1830711296 bytes
sending 'recovery' (16092 KB)...
OKAY [ 1.442s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.447s
So I currently have no os, no recovery and no way of loading a recovery back on as you can see above... am I screwed ???

Have now managed to put stock recovery back (via ruu) on and at the top of the screen it says entering recovery but never gets any further ...
Have tried again to install twrp ... no joy there what so ever

Dont' Worry I got the same problem but I fixed it!!
gsusx said:
Hi
I have tried going back to Sense stock after trying out GPE edition lollipop flavour.
Unfortunately somewhere along the way something has gone horrible wrong and I'm now stuck in a bootloop with a Red Triangle
My bootloader is currently locked, althougth I am S-Off. I can still access fastboot and RUU but the problem is when I try to flash standard or twrp recovery i get the following error message
From RUU
./fastboot flash recovery recov.img
target reported max download size of 1830711296 bytes
sending 'recovery' (16092 KB)...
OKAY [ 1.442s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.447s
So I currently have no os, no recovery and no way of loading a recovery back on as you can see above... am I screwed ???
Click to expand...
Click to collapse
Hi
Press power,volume up and down for 90 seconds.It will enter into bootloader.
Then press recovery. If it is not going to recovery,stay in the bootloader mode. Connect to the pc.
Download this software from this website.
http://www.hasoon2000.info/
Click your phone model.
(If it is HTC ONE M8 CLICK this link http://www.hasoon2000.info/?device=One%202014%20(M8))
Unzip it.
open the software.
Unlock the bootloader by following the step shown on the software.
After,
Click any recovery but I prefer TWRP.
Install custom rom and you are good to go

Absolute legend ... thank you !!!

writing 'bootloader_b'... FAILED

I try to re-flash my Pixel 2 XL but failed. The status is it reboot and reboot and......non-stop reboot.
I try to flash factory image on Recovery mode. it failed on bootloader. Below is the status on windows CMD.
----------------------------------------------
D:\Download\platform-tools-Flash>fastboot flash bootloader bootloader-taimen-tmz12a.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (36344 KB)...
OKAY [ 0.097s]
writing 'bootloader_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.107s
D:\Download\platform-tools-Flash>
------------------------------------------------
I can not use the new phone anymore, please help to check my problem. Thanks.

Have you performed in fastboot Mode, at any time, this command: "fastboot flashing unlock_critical" ? (Without " ")

You can't flash factory image in recovery, it has to be done in bootloader mode, also can you boot in bootloader? Is your bootloader locked or unlocked?

Beast38 said:
I try to re-flash my Pixel 2 XL but failed. The status is it reboot and reboot and......non-stop reboot. I try to flash factory image on Recovery mode. it failed on bootloader. Below is the status on windows CMD. I can not use the new phone anymore, please help to check my problem. Thanks.
Click to expand...
Click to collapse
Apparently you have not unlocked your bootloader (critical) correctly. There are two separate commands needed to fully unlock it. That and you can't flash images from Recovery mode, you flash while in Bootloader mode. Read and follow the directions found on the same page you downloaded the image from HERE.

Thanks all. I re-check all procedure and re-do all process. It finally works fine for now.
I can not sure which step went wrong. All I know is "unlock done" "root failed or not complete".

Rooting Motorola One Action w/ Android 10

I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.

[email protected] said:
I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.
Click to expand...
Click to collapse
Hi!!
I have a model XT2013-1. I was having the same problem as you, so I updated TROIKA-RETBR on 02/22/2020.
After updating, I did the procedure of this link "https://forum.xda-developers.com/one-action/how-to/twrp-magisk-root-motorola-one-action-t3975883", skipping the step "8.2- Now tap on Wipe> Format Data> Type Yes and go back to the home screen again. " This step gave me the looping error.
Now root works perfect !!

Thank you very much. I will try it.

BL1ND4D0 said:
Hi!!
I have a model XT2013-1. I was having the same problem as you, so I updated TROIKA-RETBR on 02/22/2020.
After updating, I did the procedure of this link "https://forum.xda-developers.com/one-action/how-to/twrp-magisk-root-motorola-one-action-t3975883", skipping the step "8.2- Now tap on Wipe> Format Data> Type Yes and go back to the home screen again. " This step gave me the looping error.
Now root works perfect !!
Click to expand...
Click to collapse
I am still getting the following error message. I have no idea why. Would you please help me what to do? Thank you very much.
fastboot flash recovery twrp.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (37524 KB) OKAY [ 1.209s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed

[email protected] said:
I am still getting the following error message. I have no idea why. Would you please help me what to do? Thank you very much.
fastboot flash recovery twrp.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (37524 KB) OKAY [ 1.209s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
It's A/B device so it doesn't have dedicated recovery partition. It's inside boot.img.
Use fastboot boot twrp.img
Once booted to twrp, you can use the twrp installer zip to flash twrp recovery ramdisk to your boot.img for permanent installation.

tys0n said:
It's A/B device so it doesn't have dedicated recovery partition. It's inside boot.img.
Use fastboot boot twrp.img
Once booted to twrp, you can use the twrp installer zip to flash twrp recovery ramdisk to your boot.img for permanent installation.
Click to expand...
Click to collapse
Thank you very much for your help. I tried but I was still getting the following error message.
fastboot boot twrp.img
Sending 'boot.img' (37524 KB) OKAY [ 0.990s]
Booting FAILED (remote: '')
fastboot: error: Command failed
Would you tell me what to do?

[email protected] said:
Thank you very much for your help. I tried but I was still getting the following error message.
fastboot boot twrp.img
Sending 'boot.img' (37524 KB) OKAY [ 0.990s]
Booting FAILED (remote: '')
fastboot: error: Command failed
Would you tell me what to do?
Click to expand...
Click to collapse
Did you follow all instructions from twrp thread. like flashing modified vbmeta and wipe data before booting twrp?
Also take a look at the original thread for one vision as it has a newer zip that contains only one modified vbmeta.img instead of two different ones in the older zip that is posted in one action's twrp thread.

I rooted using fastboot, I could never get into TWRP to flash anything.
In fastboot, I flashed the modified vbmeta.img, then flashed the magisk patched boot img file (I created this with magisk), then flashed the patched vbmeta.img file, then did a fastboot wipe.
Rebooted, set up the phone, installed magisk manager and opened, it needed to update some files. Rebooted, and the device was rooted.

goofball2k said:
I rooted using fastboot, I could never get into TWRP to flash anything.
In fastboot, I flashed the modified vbmeta.img, then flashed the magisk patched boot img file (I created this with magisk), then flashed the patched vbmeta.img file, then did a fastboot wipe.
Rebooted, set up the phone, installed magisk manager and opened, it needed to update some files. Rebooted, and the device was rooted.
Click to expand...
Click to collapse
Thank you very much for your input. You must be an expert! WOW! Sorry I am not that expert........ Would you mind explaining (1) how to modify vbmeta.img and (2) how to patch boot.img? It is very impressive to read what you have done, but sorry I am still a beginner. Also, when I flash, "fastboot flash (File Name)" ok?
Thank yuo very much for your help.

[email protected] said:
Thank you very much for your input. You must be an expert! WOW! Sorry I am not that expert........ Would you mind explaining (1) how to modify vbmeta.img and (2) how to patch boot.img? It is very impressive to read what you have done, but sorry I am still a beginner. Also, when I flash, "fastboot flash (File Name)" ok?
Thank yuo very much for your help.
Click to expand...
Click to collapse
You don't need to modify vbmeta.img. I am using the older version of the root Moto Vision package, which has a vbmeta.img file, and a patched vbmeta.img file.
For the modified boot img, I downloaded the full image from https://mirrors.lolinet.com/firmware/moto/troika/official/
Extract, and then take the boot.img file, you will want that saved to a phone that has Magisk installed.
Follow these instructions to patch
https://www.ytechb.com/how-to-patch-a-file-in-magisk-manager/
Once you have that, you will want that patched file into the fastboot directory on your computer. You will also want the vbmeta and the patched vbmeta img files (from the root moto vision package) in this directory. I have not used the updated version, I am using the older. I don't know about using the newer package which only has 1 vbmeta file.
Put your phone into fastboot mode.
Flash the vbmeta.img file, then the magisk patched boot file, then the vbmeta patched file. Then do a fastboot wipe of the phone.
Reboot the phone.
Set it up again, install magisk manager, then open it, and it should ask to configure. Let it do that, it should reboot and after that, you should be rooted.

[email protected] said:
I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.
Click to expand...
Click to collapse
I guess goofball2k detailed reply might have helped by now. On the other hand, I'm just curious to know that the next time you or anyone else for that matter face the same issue, please flash the stock firmware (using any of the Android 10 tools from here ) at that instance, then again start the same process and let me know whether you succeed or not (you will still have to execute the fastboot boot twrp command around 4-8 times, but during all these attempts, you should now get the success message, and after x number of attempts, you should succeed). So in short, if flashing the stock firmware after that error helps you out, do let me know

Thank you
binary**# said:
I guess goofball2k detailed reply might have helped by now. On the other hand, I'm just curious to know that the next time you or anyone else for that matter face the same issue, please flash the stock firmware (using any of the Android 10 tools from here ) at that instance, then again start the same process and let me know whether you succeed or not (you will still have to execute the fastboot boot twrp command around 4-8 times, but during all these attempts, you should now get the success message, and after x number of attempts, you should succeed). So in short, if flashing the stock firmware after that error helps you out, do let me know
Click to expand...
Click to collapse
Thank you very much for your input.

How are you!!
It doesn't leave me at all ... everything I want to flash throws the same error:
C:\platform-tools>fastboot boot vbmeta.img
creating boot image...
creating boot image - 6144 bytes
downloading 'boot.img'...
OKAY [ 0.013s]
booting...
FAILED (remote failure)
finished. total time: 0.184s
What can be?

Polnareff said:
How are you!!
It doesn't leave me at all ... everything I want to flash throws the same error:
C:\platform-tools>fastboot boot vbmeta.img
creating boot image...
creating boot image - 6144 bytes
downloading 'boot.img'...
OKAY [ 0.013s]
booting...
FAILED (remote failure)
finished. total time: 0.184s
What can be?
Click to expand...
Click to collapse
You aren't flashing, your command is trying to boot from vbmeta.img. You are missing the flashing command.