Hi everyone
Yesterday I've installed Android 6.0. Tesla ROM after downgrading to Stock Android 5.1. (Stock 6.0. was slow as hell)
When I was beginning to install Android 5.1. stock fastboot had said that it cant install gpt.bin file. I've read that it's possible to do the install without it. Restarting or turning on after completely successful install it shows every time the bootloader and I always have to press START. I've decided to install Tesla ROM thinking it will fix that. But the problem remains still. I've tried to re-lock my bootloader but it says Please fully flash the signed build before locking phone. What do I have to do now to fix it? Thanks in advance
Check your phone box, there is a sticker that should say "XT 1541 retXX" so you know wich region is right for your phone, then download the fw from the filefacory repo http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50 and flash it whit mfastbootV2
PS
Your phone have a dedicated section --> http://forum.xda-developers.com/2015-moto-g
edrpomidor said:
Hi everyone
Yesterday I've installed Android 6.0. Tesla ROM after downgrading to Stock Android 5.1. (Stock 6.0. was slow as hell)
When I was beginning to install Android 5.1. stock fastboot had said that it cant install gpt.bin file. I've read that it's possible to do the install without it. Restarting or turning on after completely successful install it shows every time the bootloader and I always have to press START. I've decided to install Tesla ROM thinking it will fix that. But the problem remains still. I've tried to re-lock my bootloader but it says Please fully flash the signed build before locking phone. What do I have to do now to fix it? Thanks in advance
Click to expand...
Click to collapse
Use mfastboot v2, and try to flash a 5.1 firmware from the same region (if your phone was from Latin America use retLA, if it's from asia use retasia, for the US use retUS, etc.)
benjausen said:
Use mfastboot v2, and try to flash a firmware FROM THE SAME REGION. Did you change motoboot.img? If so then skip 5.X gpt.bin and motoboot.img flashing.
Click to expand...
Click to collapse
No I didn't
deleted
benjausen said:
Use mfastboot v2, and try to flash a 5.1 firmware from the same region (if your phone was from Latin America use retLA, if it's from asia use retasia, for the US use retUS, etc.)
Click to expand...
Click to collapse
I've done everything you said (gpt.bin has been installed!), showing of bootloader is gone.
But the problem with blocking of bootloader exist yet... However, thanks
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.047s]
finished. total time: 0.052s
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.015s]
finished. total time: 0.017s
or in mfastboot-v2
C:\Users\\Desktop\Новая папка>mfastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\\Desktop\Новая папка>mfastboot oem lock
...
(bootloader) Please flash valid signed images just after lock begin
(bootloader) command!
OKAY [ 0.032s]
finished. total time: 0.035s
edrpomidor said:
I've done everything you said (gpt.bin has been installed!), showing of bootloader is gone.
But the problem with blocking of bootloader exist yet... However, thanks
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.047s]
finished. total time: 0.052s
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.015s]
finished. total time: 0.017s
or in mfastboot-v2
C:\Users\\Desktop\Новая папка>mfastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\\Desktop\Новая папка>mfastboot oem lock
...
(bootloader) Please flash valid signed images just after lock begin
(bootloader) command!
OKAY [ 0.032s]
finished. total time: 0.035s
Click to expand...
Click to collapse
Try to flash a 6.0 firmware for your region after the lock. Might not be the best, but at least you will have a working phone. It seems you relocked it, so you won't be able to use other images or to root and install custom ROMS. My XT1072 runs 6.0.1 CM13 and the touchscreen is lagged plus a reduced gaming perfomance, but the phone works.
benjausen said:
Try to flash a 6.0 firmware for your region after the lock. Might not be the best, but at least you will have a working phone. It seems you relocked it, so you won't be able to use other images or to root and install custom ROMS. My XT1072 runs 6.0.1 CM13 and the touchscreen is lagged plus a reduced gaming perfomance, but the phone works.
Click to expand...
Click to collapse
Now I have stock Android 6.0.1 RETEU XT1541, working phone with unlocked bootloader, so if I want, I can flash other ROMs.
edrpomidor said:
Now I have stock Android 6.0.1 RETEU XT1541, working phone with unlocked bootloader, so if I want, I can flash other ROMs.
Click to expand...
Click to collapse
Try flashing CM12.1 then.
Related
Hey guys, I did something really stupid.
I acquired an Atrix HD through a third party, network/sim unlocked it to work on T-Mobile, and tried to flash 4.1.2 Mexican Retail (MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX) through RSD Lite 6.1.5 after removing the getvar command and.. it failed half way. I forgot to unlock the bootloader before flashing.
Now I'm stuck and I've tried almost everything to fix it. I've searched Google and XDA, in the process I have downloaded Myth Tools, sirhoover_atrixhd_utility, motochopper, motopocalypse, and moto-fastboot, tried them all to the best of my knowledge and nothing is working. I've even edited the XML file to exclude the files it fails on.
Common errors I encounter:
Fastboot reason: Boot failure
Fastboot reason: Flash failure
Partition (boot) Security Version Downgraded
Preflash Validation Failed for boot
Partition (system) Security Version Downgraded
PIV black validation for system failed
Invalid PIV image: system
Worst part is, I can't unlock my bootloader because I need ADB to do so! Recovery will give me ADB but only to sideload (available on certain recoveries I've managed to flash). If you have any ideas or information that could assist me in getting my phone back to normal, whether that's unlocking the bootloader through fastboot or flashing a stock rom sucessfully, I would greatly appreciate it! :good:
You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Thanks for your reply
I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img
Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_bell-user-4.1.2-9.8.2Q-8_MB886_FFW-11-4-release-keys-BellMobility-CA
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC
I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..
DaveTheRave said:
Thanks for your reply
I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img
Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC
I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..
Click to expand...
Click to collapse
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.
Did you try re-downloading the firmware?
audit13 said:
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.
Did you try re-downloading the firmware?
Click to expand...
Click to collapse
Just tried re-downloading everything on a brand new Windows install on a different computer, still having problems.
No matter how hard I try, I cannot get boot.img or system.img to flash from any Stock firmware, whether it's AT&T, Mex, or Bell
Using snap-fastboot:
snap-fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.788s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
snap-fastboot flash system system.img
sending 'system' (30720 KB)...
OKAY [ 2.343s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
I'm going to try making a Motorola Factory cable in the meantime. Any other suggestions?
EDIT: Factory cable didn't help.. is there a way to generate a higher security version? No matter what, the bootloader always displays Partition (boot/system) Security Version Downgraded
I really don't want this to end up being a paperweight
Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?
Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?
I just got a new Atrix HD replacement and its showing firmware of 9.8.0Q-97_MB886_FFW-20 . Its not the same as the firmware available here: http://sbf.droid-developers.org/ .... I get the same error even after modifying the XML file in the SBF. Wonder if the last update caused an issue. Running into some similar issue with the replacement. Its not wanting to bootloader unlock.
Did you mount the system before installing?
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Sorry I've been MIA, been busy with work.
TabascoTX said:
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Click to expand...
Click to collapse
Thanks for the reply! I wished this worked for me. After completing the steps successfully, I get:
Partition (boot) Security Version Downgraded
Fastboot Reason: Boot Failure
Code:
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
fastboot oem fb_mode_set
...
OKAY [ 0.006s]
finished. total time: 0.006s
fastboot oem fb_mode_clear
...
OKAY [ 0.005s]
finished. total time: 0.005s
fastboot erase userdata
erasing 'userdata'...
OKAY [ 3.095s]
finished. total time: 3.095s
fastboot erase cache
erasing 'cache'...
OKAY [ 1.669s]
finished. total time: 1.669s
fastboot reboot
rebooting...
finished. total time: 0.005s
audit13 said:
Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?
Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?
Click to expand...
Click to collapse
That's exactly where I got my firmwares from. And to answer your question, I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.
DaveTheRave said:
...I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.
Click to expand...
Click to collapse
Try logging off and back on to see what happens. For me, using fastboot/adb commands on an x86 Win7 machine works more consistently than using an x64 Win7 machine.
TabascoTX said:
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Click to expand...
Click to collapse
When I run fastboot oem fb_mode_set, it just says "< waiting for any device >"
Sorry for the late reply. make sure you have adb installed and the drivers for the Atrix. Also,if possible and not in a boot loop or stuck in fastboot, device debugging should be enabled.
Boot problem
Hello here I have a problem and I made everything from my knowledge but It's not fixed.
I have a Motorola Droid Maxx X8 verison XI1080, version 4.4.4, built number SU4.21,
If I install or do something and I switch off and I turn on my phone it disappears as if it is never done and if I try to reinitialize the phone I have a error Fastboot Reason: Boot Failure
If I get the fastboot and I take recovery its said Boot up failed.
I did everything I flashed with RSD and I update it with Motorola update but still nothing we see that the flashing and the update works but on reboot Its has no effect on the phone its stays as if you did nothing.
Please help me! I look forward to a solution, I thank you more.
have u solved the problem
Please explain how u have solved the problem ,my moto g4 plus in same problems
hello bro
i have moto xt926 4.4.2
3 month ago unlock boot lodaer but now i need relock boot lodaer for new update please
who know instr to help me
nokia alkng said:
hello bro
i have moto xt926 4.4.2
3 month ago unlock boot lodaer but now i need relock boot lodaer for new update please
who know instr to help me
Click to expand...
Click to collapse
1. Wrong Forum, bro (here is Razr i)
2. Use ADB relock (pretty the same as ADB unlock you have done...)
5m00v3 said:
1. Wrong Forum, bro (here is Razr i)
2. Use ADB relock (pretty the same as ADB unlock you have done...)
Click to expand...
Click to collapse
please can you gave me instr how to plz
5m00v3 said:
1. Wrong Forum, bro (here is Razr i)
2. Use ADB relock (pretty the same as ADB unlock you have done...)
Click to expand...
Click to collapse
C:\android>fastboot reboot
rebooting...
finished. total time: 0.006s
C:\android>fastboot oem lock
< waiting for device >
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.011s]
finished. total time: 0.011s
C:\android>fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.010s]
finished. total time: 0.011s
C:\android>
i call to motorola support but not slove
oky no problem can you tell me how to install twrp for xt926 4.4.2 i try one by one but cant install twrp
nokia alkng said:
(bootloader) FAIL: Please run fastboot oem lock begin first!
Click to expand...
Click to collapse
did you try: fastboot oem lock begin
And for xt926, go to the section of this forum for your phone, there u find twrp instr and files: http://forum.xda-developers.com/droid-razr-hd
5m00v3 said:
did you try: fastboot oem lock begin
And for xt926, go to the section of this forum for your phone, there u find twrp instr and files: http://forum.xda-developers.com/droid-razr-hd
Click to expand...
Click to collapse
hi bro
yas i tried more
C:\android>fastboot reboot
rebooting...
finished. total time: 0.006s
C:\android>fastboot oem lock
< waiting for device >
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.011s]
finished. total time: 0.011s
C:\android>fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.010s]
finished. total time: 0.011s
nokia alkng said:
hi bro
yas i tried more
Click to expand...
Click to collapse
have a look into this batch file: http://forum.xda-developers.com/showpost.php?p=44430691&postcount=4
This is relock for Razr i, so DONT use it directly on your phone!
Look into the relock.bat file for ADB commands to relock...
---------- Post added at 04:08 PM ---------- Previous post was at 03:50 PM ----------
maybe you only need:
fastboot oem lock begin
fastboot oem lock
fastboot reboot
EDIT 3: Okay, just flashed a new kernel and the WiFi is working now. Must have been the stock kernel for some reason.
So all problems solved now
EDIT 2: Succesfully flashed the ROM, but unable to connect to Wifi. When I press the on button, it switches on for a second and then switches off again. Any idea guys why?
I've been trying to flash the stock ROM, but can't because as soon as I begin with the first step i.e fastboot flash partition gpt.bin, the following error is displayed- fastboot preflash validation failed.
Now I've been reading up on the forums here and a some have said that this error occurs when someone tries to downgrade. But I'm on the latest build and I don't know why this is happening?
Just so everyone knows, I'm unlocked and rooted.
Please, I need help since the ROM I'm on, which by itself is stock, is pretty much not working.
EDIT: The full message on fastboot is as follows
PHP:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.036s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.397s
And on the bootloader
PHP:
version downgraded for primary_gpt
mahendru1992 said:
I've been trying to flash the stock ROM, but can't because as soon as I begin with the first step i.e fastboot flash partition gpt.bin, the following error is displayed- fastboot preflash validation failed.
Now I've been reading up on the forums here and a some have said that this error occurs when someone tries to downgrade. But I'm on the latest build and I don't know why this is happening?
Just so everyone knows, I'm unlocked and rooted.
Please, I need help since the ROM I'm on, which by itself is stock, is pretty much not working.
EDIT: The full message on fastboot is as follows
PHP:
target reported max download size of 536870912 bytessending 'partition' (32 KB)...OKAY [ 0.036s]writing 'partition'...(bootloader) Preflash validation failedFAILED (remote failure)finished. total time: 0.397s
And on the bootloader
PHP:
version downgraded for primary_gpt
Click to expand...
Click to collapse
You can ignore gpt.bin and motoboot.bin. They won't flash if the same or lower version. Not a problem. Just continue flashing the other files.
doppelhelix said:
You can ignore gpt.bin and motoboot.bin. They won't flash if the same or lower version. Not a problem. Just continue flashing the other files.
Click to expand...
Click to collapse
Okay, thanks man, I successfully flashed the ROM. But now I have another problem. I'm not able to switch on my Wifi. When press the on button, it switches on for a micro sec and then switches off. Any idea why?
Don't know. Maybe a reboot. After that I would wipe dalvic, cache and data?
doppelhelix said:
Don't know. Maybe a reboot. After that I would wipe dalvic, cache and data?
Click to expand...
Click to collapse
I did better, a factory reset. Nada.
Would flashing a different kernel help?
Did you do a
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
This is a wififix for the kernel
doppelhelix said:
Did you do a
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
This is a wififix for the kernel
Click to expand...
Click to collapse
Oh I didn't know that this was a wifi fix, but yes I did perform the above steps as well.
But anyhow, I flashed a new kernel and it did solve the problem.
Thanks
doppelhelix said:
You can ignore gpt.bin and motoboot.bin. They won't flash if the same or lower version. Not a problem. Just continue flashing the other files.
Click to expand...
Click to collapse
Thanks 4 Your Help i been stuck whit that errors all night and now i have back on 4.4.4.
C:\Users\Raghavendra\Documents\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1F
F_SVC.xml>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.133s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.192s
pl help me i have the same problem..... but idk how to fix it...... plz help me asap... i have just unbricked my phone and tried to flash the brazillian 4.4.4....... i was already on this firmware before but when i tried to update to brazilian ota 5.0 my phone was bricked... now i have successfully unbricked it but i cant flash it to any rom cause of this problem...... if it the files prob?? should i get another rom?? pl help asap:crying::crying::crying::crying::crying::crying:
Raghavendra2k14 said:
C:\Users\Raghavendra\Documents\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1F
F_SVC.xml>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.133s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.192s
Click to expand...
Click to collapse
As you pointed out here: http://forum.xda-developers.com/showpost.php?p=57483947&postcount=115, your bootloader is locked. Please don't double-post. Forum Rules
pl help
doppelhelix said:
As you pointed out here: http://forum.xda-developers.com/showpost.php?p=57483947&postcount=115, your bootloader is locked. Please don't double-post. Forum Rules
Click to expand...
Click to collapse
when i try unlocking bootloader again it gives me me a error
C:\Users\Raghavendra\Desktop\platform-tools>fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [ 0.016s]
finished. total time: 0.016s
even if i put my old code it doesnt work... pl help..... but in this forum it tells us to flash the two files gpt.bin and motoboot.img but when i try to flash these they give me preflash validation error <remote failure> and display "version downgraded for primary_gpt" on the moto g
my bootloader is locked because it got hard bricked and i recently unbricked it.... the next step was to flash these two files but i get this preflash validation error <remote failure> and display "version downgraded for primary_gpt" on the moto g
pl help me
Raghavendra2k14 said:
when i try unlocking bootloader again it gives me me a error
C:\Users\Raghavendra\Desktop\platform-tools>fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [ 0.016s]
finished. total time: 0.016s
even if i put my old code it doesnt work... pl help..... but in this forum it tells us to flash the two files gpt.bin and motoboot.img but when i try to flash these they give me preflash validation error <remote failure> and display "version downgraded for primary_gpt" on the moto g
my bootloader is locked because it got hard bricked and i recently unbricked it.... the next step was to flash these two files but i get this preflash validation error <remote failure> and display "version downgraded for primary_gpt" on the moto g
pl help me
Click to expand...
Click to collapse
Didn't you read anything of the previous posts?
If you've unlocked your bootloader, and getting these errors, you can safely ignore them. Just carry on flashing the other files.
Carried on
I did carried on with the fastboot steps but I get this "UTAG "flashfail" is configured as fastboot" and I'm still stuck in Bootloader.
How do I change the Kernel?
Oh yeah, I updated to Lollipop about 20 days ago, worked fine until a few days back and suddenly I get these strange errors. What could be the cause though?
I have a UK XT1068 and have upgraded to Lollipop.
I've been trying to go back to stock so I can catch the stock OTA upgrade but the first two commands in the list don't seem to be working right i.e.
mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.109s]
writing 'partition'...
(bootloader) Preflash validation faile
FAILED (remote failure)
finished. total time: 0.422s
mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.172s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.469s
I'm using the stock ROM - RETGBALL_XT1068_4.4.4_KXB21.85-23_cid7_CFC.xml.
The rest of the commands do seem to work OK and the ROM seems to flash but I'm not sure everything is OK.
Also, I can't relock the boot loader, I get the following error:
mfastboot.exe oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
OKAY [ 0.013s]
finished. total time: 0.014s
mfastboot.exe oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.043s]
finished. total time: 0.044s
mfastboot.exe oem lock
...
(bootloader) sst lock failure!
OKAY [ 0.011s]
finished. total time: 0.012s
Any assistance would be greatly appreciated
Don't worry about it. Carry on with the rest of the commands. This is a pretty common error that has no effect.
Oh and you don't need to relock your bootloader to get an OTA.
mahendru1992 said:
Don't worry about it. Carry on with the rest of the commands. This is a pretty common error that has no effect.
Oh and you don't need to relock your bootloader to get an OTA.
Click to expand...
Click to collapse
Thanks for the info.
What does stop an OTA? I thought it was the unlocked bootloader?
podge3 said:
Thanks for the info.
What does stop an OTA? I thought it was the unlocked bootloader?
Click to expand...
Click to collapse
Anything not stock, for instance, a custom recovery or kernel.
If you've modified your system files, or disabled or uninstalled system apps, even that can prevent you from receiving an update.
mahendru1992 said:
Anything not stock, for instance, a custom recovery or kernel.
If you've modified your system files, or disabled or uninstalled system apps, even that can prevent you from receiving an update.
Click to expand...
Click to collapse
OK, thanks again.
Hey all, new poster but long time user of the site, just never needed an account until today lol. Anyways, just got a Pixel 5a5G that I am trying to install LineageOS on. I am following the instructions from here, and once I get to the point of flashing the vendor_boot partition, I receive this:
Code:
PS C:\Windows\system32> fastboot flash vendor_boot C:\Users\bobby\Downloads\vendor_boot.img
target reported max download size of 268435456 bytes
sending 'vendor_bootb' (98304 KB)...
OKAY [ 2.225s]
writing 'vendor_bootb'...
FAILED (remote: Not allowed to flash (vendor_bootb))
finished. total time: 2.307s
When running fastboost unlock bootloader, I receive this:
Code:
PS C:\Windows\system32> fastboot flashing unlock
...
(bootloader) Device already unlocked
OKAY [ 0.055s]
finished. total time: 0.056s
I have reflashed the stock firmware with the Android Flashing Tool to 13.0.0, both keeping the bootloader locked and unlocked. I have tried unlocking and relocking the bootloader. I used the utility's "full-flash" feature to flash both partitions, all to no avail. Research on here seems to point that the bootloader is locked, but fastboot says it isn't, settings is greyed out saying the bootloader is already unlocked, and fastboot mode on the phone says Device state: unlocked.
Any ideas?
Did you remove your screenlock and Google account before flashing?
Leberkuchen said:
Did you remove your screenlock and Google account before flashing?
Click to expand...
Click to collapse
Yes. I've flashed from a factory install with no passcode or account ever set. Same issue
From the output it's trying to write vendor_bootb??? Some combination of this should fix it:
-Make sure to use platform tools r33.0.3, the latest r34 has at least one known problem with fastboot and I don't trust it
-If you're using powershell you have to run the command as .\fastboot flash you can only run fastboot flash if you are in cmd
-Make sure both slots are on latest February firmware (probably not really necessary but a last ditch effort)