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?
Related
Geniuses of the internet!
I am in desperate need of help.
Basically yesterday morning I was greeted with an update notification and being none the wiser I just accepted and thought everything would be ok. Silly me.
Since then my phone has done nothing but boot loop. First to the black screen with Google and the unlocked pad lock, but after some playing I now have a white Warning Bootloader Unlocked message.
I have tried flashing a stock ROM or two with Fastboot and some tools but I cant get the sodding thing to boot up.
Whenever I try to Fastboot files to my phone, the first few files always fail with the same warning
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 0.140s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.447s
It might be worth mentioning that this was a Virgin Mobile phone which I flashed to GPe.
So now all I want is to flash my phone to a stock GPe ROM and get the bloody thing working again.
PLEASE HELP!
Ross
Update #1
I flashed Philz to the phone but when trying to sideload the rom, I get a error: device not found message. Fastboot picks up the phone find, I am using minimal ADB and Fastboot install and I have all the latest USB drivers from Motorola.
Also the two files that fail from Fastboot leave a message on the phone
version downgraded for primary_gpt and version downgraded for tz
Still wont boot though.
Update #2
I installed the SDK and tried sideloading and still no dice
Update #3
I found a gpt.bin file in these forums that now does flash, but the motoboot.img still fails
Hi!
I have been using CyanogenMod on my Moto G since October 2016 and now I have upgraded to an unofficial LineageOS 14.1 build. Because of its bad reliablity, I'd like to downgrade back to stock Lollipop ROM.
I downloaded the .xml.zip file for my XT1541 2GB, the standard European one. By the way I wanted to relock the bootloader, so I started:
Code:
mfastboot oem lock begin
mfastboot flash partition gpt.bin
Here I had the first issue: mfastboot could send the file but it couldn't be written. The error thrown:
Code:
sending 'partition' (32 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.436s
I went straight on:
Code:
mfastboot flash bootloader bootloader.img
...
mfastboot system system.img_sparsechunk.0
The last fatal error:
Code:
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
I did it again, skipping the oem lock commands. Now the phone is bootable and fully operating, but still no luck for relocking the bootloader.
How can I restore to factory status by reverting to original OS and standard locked bootloader?
Maybe flash the full stock including the bootloader
I dont own this device
Avoid flashing the bootloader and gpt.bin and why do you want to relock your bootloader? Your warranty will still be voided.
make sure. u are flashing the same version of lollipop which is used before. if u were in mm . u can search for another thread i xda for downgrading
Do a "fastboot getvar all" and check the bootloader version, make sure the version you are flashing is the same or newer than what getvar shows and it will work.
Also, flash it first to make sure it works, then do it again and lock... if you something goes really wrong and lock takes, which is extremely unlikely, you are totally screwed.
Hi, I'm new to Moto G forum but have followed TF300T forum to flash my Asus TF300 successfully with custom roms.
I am having problem flashing twrp, when I flash TWRP twrp-3.0.2-2-falcon.img or twrp-3.1.1-0-falcon.img flashing reports
C:\Users\Mark> fastboot flash recovery twrp-3.0.2-2-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (9526 KB)...
OKAY [ 0.329s]
writing 'recovery'...
OKAY [ 0.546s]
finished. total time: 0.889s
Seems ok I thought, but when I try to reboot into recovery all I get is a dead android with message No command.
Phone is Moto G 1032 running stock 5.1 Android. It does still boot into system.
Unlocking bootloader seemed to be incomplete,
I tried to unlock my Moto G using the standard way suggested on Motorola site, by passing the command - fastboot oem unlock <unlock code> to fastboot screen via command prompt. Got the below messages on command prompt.
(bootloader) Failed to erase partition
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 10.225s
After that, screen on phone showed the message - UNLOCK...
& got stuck on that. I switched off & started again in Fastboot mode. On the screen it said - Device is UNLOCKED. Status Code: 3
However anther user had same problem but was able to flash TWRP successfully.
Thanks in advance
SOLVED
Used Moto G 2014 ToolKit, Tool/Utility for the Moto G 2014 by luca020400 and this worked.
Not sure what I did wrong but many thanks to luca020400
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.
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