I have seen some rooting instructions that included instructions for obtaining a bootloader unlock code from Motorola and some instructions that do not. It was then unclear to me about the necessity for that step.
My phone had been updated to QPR30.80-58-3 so I patched the boot.img file from a downloaded ROM for that release. I thought I would try flashing without going through the unlock code process. I ended up with the error message below. For reference, I get the same error message if I try to flash boot_a or boot_b. Would this likely be because I did not enter an unlock code?
C:\adb>fastboot flash boot magisk_patched.img
Sending 'boot_b' (12140 KB) OKAY [ 0.317s]
Writing 'boot_b' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
For what it's worth, I bought my Stylus from Best Buy.
Thanks.
You need to unlock your phone first.
johnjingle said:
You need to unlock your phone first.
Click to expand...
Click to collapse
Indeed I did. I did not get the Warning! Bootloader Unlocked screen like the general instructions said but I did see that a status on the bootloader screen changed from oem_locked (if I recall that correctly) to flashing_unlocked. I was then able to flash boot.img.
Related
Applied for unlocking at http://en.miui.com/unlock/ and got this:
Apply for unlocking permissions
Sorry, your application has been rejected.
The more active your Mi Account is, the more likely your application will get approved.
Reapply>>
So no way to get unlock code!
Then tried: https://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
And it seemed to work, could flash TWRP and CM 13.1
Had problems with radio, tried flashing radio, now I'm stuck in fastboot, can't boot to recovery or anything else, loops back to fastboot.
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.062s]
finished. total time: 0.063s
Any attempt to flash I get: "Partition flashing is not allowed"
Any ideas or should I just enter the "How far can you toss your Xiaomi MI4c contest"?
Your bootloader is re-locked. Follow the unlock procedure again, maybe you flashed the new bootloader.
BTW you don't have to flash the whole rom to change the bootloader, you can just extract it from firmware in zip and run:
fastboot flash aboot emmc_appsboot.mbn
Ydraulikos said:
Your bootloader is re-locked. Follow the unlock procedure again, maybe you flashed the new bootloader.
BTW you don't have to flash the whole rom to change the bootloader, you can just extract it from firmware in zip and run:
fastboot flash aboot emmc_appsboot.mbn
Click to expand...
Click to collapse
Thank you friend Ydraulikos, I have tried flashing boot and recovery before, but I have not tried your version.
Unfortunately this was the result:
C:\adb\images>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (469 KB)...
OKAY [ 0.036s]
writing 'aboot'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 0.083s
SOLVED!
Things looked pretty hopeless, two days without a phone, but managed to return to MIUI 7.1.6.7 and can proceed from here. I'm not saying this is the righ method, it worked for me and perhaps can help others in a similar situation. Have read a lot of posts in the last two days so please forgive me if I can not give credit to all the people whose advice helped, so thank you xda!
Installed QDLoader HS-USB Driver_64bit_Setup recommended in one of the posts and rechecked my drivers in general.
One command that seemed to be promising was "fastboot oem edl"
However, when my phone went to edl mode it was no longer accessible for fastboot <waiting for device>
On advice of another post I downloaded MiFlash2015.10.28.0 and libra_images_6.1.7_20151221.0000.11_5.1.*.tar.gz
From the command line typed "fastboot oem edl" and with MiFlash flashed MIUI 6.1.7, had to choose the "Flash all except data and storage" option as other options gave me a memory error message. Flashing went okay!
So my phone is back in business now!
I rooted my xt2013, where can I get some bootlogo to remove the unlocked bootloader message?
You can't, it's part of the baked-in device security. The bootloader is loaded after the bootloader unlocked message and there have been very few instances of being able to hide that message on any device. It's there for a reason to make sure your device can't be secretly unlocked without you knowing. Making it easily hideable would defeat the purpose.
Can you not just find a replacement logo_a and logo_b files and flash them?
I am having same issue with my rooted Hyper
jharkness316 said:
Can you not just find a replacement logo_a and logo_b files and flash them?
I am having same issue with my rooted Hyper
Click to expand...
Click to collapse
It seems that it doesn't work on the Motorola One Action (troika) - it worked in the past on my old Moto G4 Play and Moto G6:
fastboot flash logo logo.bin
But on troika I get the following error message:
>>>fastboot flash logo white_logo.bin
(bootloader) is-logical:logo_a: not found
Sending 'logo_a' (876 KB) OKAY [ 0.249s]
Writing 'logo_a' (bootloader) validation image failed
FAILED (remote: '')
fastboot: error: Command failed
I have no solution - anyone have one?
Good news!
Motorola One Action just got an official TWRP version.
See here:
https://twrp.me/motorola/motorolaoneaction.html
Thanks to @kaneawk who is the maintainer!
gracias
Fain11 said:
Good news!
Motorola One Action just got an official TWRP version.
See here:
Thanks to @kaneawk who is the maintainer!
Click to expand...
Click to collapse
This didn't work for me, I tried to follow the instructions on the twrp page, and it worked until fastboot boot twrp.img where i get:
Sending 'boot.img' (42324 KB) OKAY [ 1.017s]
Booting FAILED (remote: '')
fastboot: error: Command failed
And when I look at bootloader logs on my phone, it says: Validation Image Failed
FullofAwe said:
This didn't work for me, I tried to follow the instructions on the twrp page, and it worked until fastboot boot twrp.img where i get:
Sending 'boot.img' (42324 KB) OKAY [ 1.017s]
Booting FAILED (remote: '')
fastboot: error: Command failed
And when I look at bootloader logs on my phone, it says: Validation Image Failed
Click to expand...
Click to collapse
Did u unlocked your bootloader?
Fain11 said:
Did u unlocked your bootloader?
Click to expand...
Click to collapse
I did... And it still is.
FullofAwe said:
This didn't work for me, I tried to follow the instructions on the twrp page, and it worked until fastboot boot twrp.img where i get:
Sending 'boot.img' (42324 KB) OKAY [ 1.017s]
Booting FAILED (remote: '')
fastboot: error: Command failed
And when I look at bootloader logs on my phone, it says: Validation Image Failed
Click to expand...
Click to collapse
Firstly flash v-meta IMG then flash twrp IMG.
sharma.keshav153 said:
Firstly flash v-meta IMG then flash twrp IMG.
Click to expand...
Click to collapse
wut is v-meta
Having Problem restoring backup
Hi @Fain11,
I have installed TWRP 3.4.0.0 for moto one action from magisk module then I made backups without any problem.
With the Official TWRP, if I want to root, should install Disable_Dm-Verity_ForceEncrypt after flash Magisk-v20.4 ?
Is it possible to root with Magisk and keeping encryption ?
Each time I boot Recovery it's asking me for password user's "0" for data decryption ? ..., anybody knows what it's is ?
I'm having an XT2013-4 running August RETAIL firmware.
/Regards
...
After flashing a stock rom back to my Moto One Action, whenever i try and boot from the .img file, I get this error:
Sending 'boot.img' (42324 KB) OKAY [ 0.974s]
Booting FAILED (remote: '')
fastboot: error: Command failed
Sounds like you're missing the vbmeta patch file. You need to flash it first to resolve this error.
TheDudestPriest504 said:
After flashing a stock rom back to my Moto One Action, whenever i try and boot from the .img file, I get this error:
Sending 'boot.img' (42324 KB) OKAY [ 0.974s]
Booting FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
go to some dev for help on xda
Hello all , since the rise of dmverify and vmbeta.img, i thought its really more difficult to root a phone and install custom roms.
I need a new phone to install andrax over it.
Which one should i buy for you ? I read that HTC is developer compliant ???
If phone's bootloader can get unlocked, then with a simple Fastboot command AVB ( DM-verity ) can get disabled
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
where it's enough to pass an empty vbmeta.img.
It doesn't work with an empty vbmeta.img, but i didn't get this sequence of options to worked before.
I'll get a try with some recovery img and other things.
Anyway actually i got this :
FAILED (File is too large to download)
So now, its not enough to pass en ampty vbmeta.img
i'm trying to do it on an unisoc spd sp9863a device.
Android 9 pie, with bootloader locked.
I heard a modified version of fastboot is needed, to unlock it, with some private keys needed from manufacturer.
I don't get theses, so it didn't work either.
Thats why, i'm asking wich phone could i buy to get 100% sure, it will unlock easy and i'll can install andrax over it.
The idea of passing through dm verity with an empty vbmeta.img is interesting.
I didn't knew android coud be bypassed so easily , i have to read much to understand the underlying scheme of it.
And now i can assure you it doesn't work, since i just did it with a real vbmeta from original firmware :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta-sign.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (1024 KB) OKAY [ 0.033s]
Writing 'vbmeta' FAILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')
fastboot: error: Command failed
i read some stanges post over internet, some people thought its possible to recode fastboot from sources, and to modify its behaviour than it would force flashing even if lock flag is locked.
I have time to try all the ways possible, but meantime i really want to install andrax over a phone to get a try on it.
I'm sure my actual phone ( a wiko y80 unisoc) is very well protected, and can't be defeated without private keys
MaxwellFiltre said:
It doesn't work with an empty vbmeta.img, but i didn't get this sequence of options to worked before.
I'll get a try with some recovery img and other things.
Anyway actually i got this :
FAILED (File is too large to download)
So now, its not enough to pass en ampty vbmeta.img
Click to expand...
Click to collapse
You are WRONG. You either have to create a blank vbmeta.img by means of AVBtool at your own or simply use the one attached: it's your decision.
jwoegerbauer said:
You are WRONG. You either have to create a blank vbmeta.img by means of AVBtool at your own or simply use the one attached: it's your decision.
Click to expand...
Click to collapse
I would very like to be wrong, but i'm not.
Just tried with your vbmeta, and i tried with the one official from wiko
All i got =>
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (0 KB) OKAY [ 0.001s]
Writing 'vbmeta' FAILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')
fastboot: error: Command failed
The bootloader is locked
MaxwellFiltre said:
I would very like to be wrong, but i'm not.
Just tried with your vbmeta, and i tried with the one official from wiko
All i got =>
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (0 KB) OKAY [ 0.001s]
Writing 'vbmeta' FAILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')
fastboot: error: Command failed
The bootloader is locked
Click to expand...
Click to collapse
I wasn't aware of fact that you obviously don't know that device's bootloader must got unlocked as 1st thing of all things if you want to deal with device's bootloader ( i.e run Fastboot commands ).
Sure, thats why the subject of this topic is "Which phone buy to root andrax, when bootloader is unlockable?"
Thank you for your cooperation.
Hi, just so you know, I am very new to this so please excuse any dumb mistakes I may have done.
I got a stock ROM for my device from LMSA and I am attempting to flash it using fastboot. The first problem I came across while trying to do this, which I still don't know how to fix, is that whenever I try to flash my bootloader with bootloader.img, I get this:
C:\Users\spong\OneDrive\Documents\platform-tools>fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.342s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
I've searched online for answers on how to fix it, and I came to threads like this which told me to try to just keep going with the rest of the flashes, which I then tried. After, I tried entering recovery mode. I got a no command error, so I went back to fastboot to try to just start my phone with the start option, in which I got a bootloop where it first, sent me to the Motorola screen for a couple seconds, showed me a warning about my unlocked bootloader, went back to the Motorola screen for 10-20 seconds, then turned my screen black for a second, and started over again. This happens for a long time until, finally, I get an error message saying: (color corresponding)
Boot failed. Press POWER KEY to Retry
Your device didn't start up successfully.
Follow these instructions if the failure cannot be recovered after retrying.
If this is a Verizon device, please use Software Repair Assistant on your computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
If this is not a Verizon device or Software Repair Assistant did not help for any reason, please contact customer care center for further assistant.
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
Click to expand...
Click to collapse
I'm using T-Mobile on my device, so it isn't locked to Verizon or using Verizon (my phone is unlocked carrier), so I decided to try to flash boot_a and boot_b with my boot.img:
C:\Users\spong\OneDrive\Documents\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.504s]
Writing 'boot_a' OKAY [ 0.512s]
Finished. Total time: 2.020s
C:\Users\spong\OneDrive\Documents\platform-tools>fastboot flash boot_b boot.img
Sending 'boot_b' (65536 KB) OKAY [ 1.504s]
Writing 'boot_b' OKAY [ 0.506s]
Finished. Total time: 2.014s
Click to expand...
Click to collapse
Doing this changed nothing.
I honestly do not know what to do, since I can't find any help online anywhere for my specific scenario. I found this forum of someone having a really similar problem with me, but they never fixed it and just decided to flash a stock ROM, which is what I was already doing.
Any solution, and I mean any, will help.
Here is the ROM that I was trying to flash, and here is my "fastboot getvar all" txt file.
I have similar issue here. Please if anyone knows how to manage this