Related
Wondering if it's possible to re-lock the bootloader. Would it be the same as a Nexus device?
bootloopz said:
Wondering if it's possible to re-lock the bootloader. Would it be the same as a Nexus device?
Click to expand...
Click to collapse
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
tw1tch175 said:
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
Click to expand...
Click to collapse
I know this is an older post but I've been unable to find the instructions for re-locking the bootloader. Any help would be appreciated.
I had the electrify m, the RAZR m for us cellular, and I unlocked it through Motorola. I was giving it to someone else and wanted to relock it and never found any instructions to do so. I contacted Motorola and they said once it was unlocked the was no way to relock. I would guess it's the same with the moto x.
Sent from my XT1055 using Tapatalk
fastboot oem lock doesn't work?
It does. Fastboot OEM lock. Just go back to signed software before, m Kay ? Else you won't boot
Sent from my XT1058 using xda app-developers app
I tried it with my electrify m and it wouldn't work.
Sent from my XT1055 using Tapatalk
https://plus.google.com/110773150384694258853/posts/XUF8UP9iVfi
Here's how from p3droid
tw1tch175 said:
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
Click to expand...
Click to collapse
Has anyone tried re-locking a non-dev Moto X? If so, does it get rid of the "bootloader unlocked, warranty void" message that you get every time u boot ur phone?
mschumacher69 said:
Has anyone tried re-locking a non-dev Moto X? If so, does it get rid of the "bootloader unlocked, warranty void" message that you get every time u boot ur phone?
Click to expand...
Click to collapse
Makes no difference, even when you flash the sbf firmware the logo warning still pops up, so you're best just flashing a new logo.bin file . you'll find them in the themes section, fastboot flash logo (name).bin and your done. If you need to rsdlite at any time in the future, just remove the line flash logo bin from the XML file
Sent on my Moto X
flashallthetime said:
Makes no difference, even when you flash the sbf firmware the logo warning still pops up, so you're best just flashing a new logo.bin file . you'll find them in the themes section, fastboot flash logo (name).bin and your done. If you need to rsdlite at any time in the future, just remove the line flash logo bin from the XML file
Click to expand...
Click to collapse
Even if u re-lock the bootloader?
bootloopz said:
Wondering if it's possible to re-lock the bootloader. Would it be the same as a Nexus device?
Click to expand...
Click to collapse
tw1tch175 said:
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
Click to expand...
Click to collapse
planktoid said:
It does. Fastboot OEM lock. Just go back to signed software before, m Kay ? Else you won't boot
Click to expand...
Click to collapse
Has anyone tried re-locking the bootloader of their Moto X??
mschumacher69 said:
Has anyone tried re-locking the bootloader of their Moto X??
Click to expand...
Click to collapse
Does not work for me. I get:
No valid PIV block in SP for system
chaoslimits said:
Does not work for me. I get:
No valid PIV block in SP for system
Click to expand...
Click to collapse
Did u try re-locking on your model/carrier stock rom, a stock rom from another model/carrier or a custom rom?
Thanks
mschumacher69 said:
Did u try re-locking on your model/carrier stock rom, a stock rom from another model/carrier or a custom rom?
Thanks
Click to expand...
Click to collapse
Went back to stock 4.4 via RSD Lite then tried to relock.
chaoslimits said:
Went back to stock 4.4 via RSD Lite then tried to relock.
Click to expand...
Click to collapse
Which model/carrier do u have?
mschumacher69 said:
Which model/carrier do u have?
Click to expand...
Click to collapse
Vzw Dev Edition
chaoslimits said:
Vzw Dev Edition
Click to expand...
Click to collapse
Have u tried this?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
mschumacher69 said:
Have u tried this?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Click to expand...
Click to collapse
Yes. That (minus userdata removal) is what RSD Lite does. I tried with fastboot and mfastboot as well.
chaoslimits said:
Yes. That (minus userdata removal) is what RSD Lite does. I tried with fastboot and mfastboot as well.
Click to expand...
Click to collapse
Weird. So is ur phone bricked now or it just did not lock?
So I unlocked my moto X, made a change from XT1097 to XT1095 and installed stock 4.4.4 Pure edition firmware. So far it worked perfectly, then I got an OTA update to 5.0, installed it and after that I had no carrier signal (IMEI was gone and Baseband too).
I have the IMEI number and serial for my device, but I didn't do the backup of the EFS folder. What can I do to fix this?
http://forum.xda-developers.com/showthread.php?t=2972693 I don't know if this can help you or not I'm assuming you've already seen it
mikeboballen said:
http://forum.xda-developers.com/showthread.php?t=2972693 I don't know if this can help you or not I'm assuming you've already seen it
Click to expand...
Click to collapse
That was the guide I was following, which led to this somehow.
I'm thinking about re-locking and un-rooting now so I'll have a shot at the warranty claim.
Good luck man hope it all works out for you
ccarrionc said:
So I unlocked my moto X, made a change from XT1097 to XT1095 and installed stock 4.4.4 Pure edition firmware. So far it worked perfectly, then I got an OTA update to 5.0, installed it and after that I had no carrier signal (IMEI was gone and Baseband too).
I have the IMEI number and serial for my device, but I didn't do the backup of the EFS folder. What can I do to fix this?
Click to expand...
Click to collapse
On this Nexus 6 thread some people had success flashing back to stock modems/baseband - these would be the commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
http://forum.xda-developers.com/nexus-6/help/imei-repair-t3000420
Then if that doesn't work then this:
http://forum.xda-developers.com/showthread.php?t=1960918
Then there is this:
http://forum.xda-developers.com/showpost.php?p=26827676&postcount=4512"
JulesJam said:
On this Nexus 6 thread some people had success flashing back to stock modems/baseband - these would be the commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
http://forum.xda-developers.com/nexus-6/help/imei-repair-t3000420
Then if that doesn't work then this:
http://forum.xda-developers.com/showthread.php?t=1960918
Then there is this:
http://forum.xda-developers.com/showpost.php?p=26827676&postcount=4512"
Click to expand...
Click to collapse
Thanks, but nothing worked. I'm starting to wonder if it might be a hardware issue...
ccarrionc said:
Thanks, but nothing worked. I'm starting to wonder if it might be a hardware issue...
Click to expand...
Click to collapse
Did you try this method using QPST?
http://forum.xda-developers.com/showthread.php?t=1960918
JulesJam said:
Did you try this method using QPST?
http://forum.xda-developers.com/showthread.php?t=1960918
Click to expand...
Click to collapse
I did, but I couldn't get the software to recognize my phone, it does seem kinda outdated (2012). Used QPST 2.7.
ccarrionc said:
I did, but I couldn't get the software to recognize my phone, it does seem kinda outdated (2012). Used QPST 2.7.
Click to expand...
Click to collapse
Sounds like you need to get a warranty replacement. It could be a hardware problem but even if it is not, they really need to make these phones less easy to eff up.
The IMEI is on the efs partition that we cannot even flash so I don't know how they can get messed up by the consumer but obviously they do. Someone on the N6 thread was saying it is a Qualcomm issue.
JulesJam said:
Sounds like you need to get a warranty replacement. It could be a hardware problem but even if it is not, they really need to make these phones less easy to eff up.
The IMEI is on the efs partition that we cannot even flash so I don't know how they can get messed up by the consumer but obviously they do. Someone on the N6 thread was saying it is a Qualcomm issue.
Click to expand...
Click to collapse
If I can't get the unlocked bootloader warning to go off, then I'm done for I think.
Unless people at the support center don't bother restarting it or anything... fingers crossed.
Plan B is to hardbrick it somehow so no one can turn it on and see my mess, haha.
ccarrionc said:
If I can't get the unlocked bootloader warning to go off, then I'm done for I think.
Click to expand...
Click to collapse
That is possible - there are plenty of threads on how to do that.
But even once you relock, your status code will be locked 2, not locked 0 so they can tell from the device. Also, you had to get an unlock code directly from them so if your device didn't qualify for bootloader unlock with maintaining your warranty, then they will know from that too.
Also, your qe will likely show 0/1 even though you unrooted. You can see the qe in stock recovery.
---------- Post added at 03:49 AM ---------- Previous post was at 03:46 AM ----------
ccarrionc said:
Unless people at the support center don't bother restarting it or anything... fingers crossed.
Click to expand...
Click to collapse
They will know b/c you got an unlock code to unlock it.
ccarrionc said:
Plan B is to hardbrick it somehow so no one can turn it on and see my mess, haha.
Click to expand...
Click to collapse
I would check the warranty status online. Even if the warranty is void, they may be able to repair the phone for a reasonable price if you don't hard brick it.
JulesJam said:
That is possible - there are plenty of threads on how to do that.
But even once you relock, your status code will be locked 2, not locked 0 so they can tell from the device. Also, you had to get an unlock code directly from them so if your device didn't qualify for bootloader unlock with maintaining your warranty, then they will know from that too.
Also, your qe will likely show 0/1 even though you unrooted. You can see the qe in stock recovery.
Click to expand...
Click to collapse
So the only way is getting the phone to not be able to turn on at all? Is there any known way to get off with it?
You need to flash an image from your original provider and it will work fine again. Right now you have an incompatible modem and as a result you will have no IMEI/mobile data or wifi as the radio portion of the phone is disabled.
ccarrionc said:
So the only way is getting the phone to not be able to turn on at all? Is there any known way to get off with it?
Click to expand...
Click to collapse
No, they have you in the database as having requested an unlock code.
ccarrionc said:
So I unlocked my moto X, made a change from XT1097 to XT1095 and installed stock 4.4.4 Pure edition firmware. So far it worked perfectly, then I got an OTA update to 5.0, installed it and after that I had no carrier signal (IMEI was gone and Baseband too).
I have the IMEI number and serial for my device, but I didn't do the backup of the EFS folder. What can I do to fix this?
Click to expand...
Click to collapse
As someone post above. You need the stock modem of your phone model, but in your case any xt1097 will work just flash using the Fastboot mode steps and everything will be fine. I have a post on the general section "guide to convert 1097 to 1095" there you can find all the possible scenarios.
Good luck.
Steve-x said:
You need to flash an image from your original provider and it will work fine again. Right now you have an incompatible modem and as a result you will have no IMEI/mobile data or wifi as the radio portion of the phone is disabled.
Click to expand...
Click to collapse
That is what I said above but he said he tried it and it didn't work.
OP - you need to make sure you are flashing the right files - you need to flash the modem/baseband files for your device (XT1097).
JulesJam said:
That is what I said above but he said he tried it and it didn't work.
OP - you need to make sure you are flashing the right files - you need to flash the modem/baseband files for your device (XT1097).
Click to expand...
Click to collapse
I am 100% sure the files used were not the correct ones.
juliospinoza said:
As someone post above. You need the stock modem of your phone model, but in your case any xt1097 will work just flash using the Fastboot mode steps and everything will be fine. I have a post on the general section "guide to convert 1097 to 1095" there you can find all the possible scenarios.
Good luck.
Click to expand...
Click to collapse
I was following your guide, everything was fine until the OTA update came up. Is there anyway to get back to the xt1097 firmware I had before? It was 4.4.4 with Telcel.
ccarrionc said:
I was following your guide, everything was fine until the OTA update came up. Is there anyway to get back to the xt1097 firmware I had before? It was 4.4.4 with Telcel.
Click to expand...
Click to collapse
What was the exact version you had before? For future reference you shouldn't flash firmware from another provider unless you have original firmware to reflash if you experience an issue.
Steve-x said:
What was the exact version you had before? For future reference you shouldn't flash firmware from another provider unless you have original firmware to reflash if you experience an issue.
Click to expand...
Click to collapse
Found a firmware from my original provider, everything is back to normal (except now I have the different status code in the fastboot screen).
For future reference, I just installed the previous firmware through fastboot (with mfastboot, of course). IMEI was recognized again and baseband too.
I had a rooted (magisk) X4 (google_fi) with twrp 3.2.1. I removed root and reflashed the stock rom (OPW27.1) and relocked the bootloader.
Everything works fine even the OTA updates (I OTA'd back up to OPWS27.1.3, but there is an annoying yellow startup screen that displays "My device has loaded a different operating system." From what I read it's because the ROM isn't digitally signed? Is that correct?
Any way to remove this screen on startup?
**FYI this is not the unlocked bootloader screen this is something else.
Thanks.
Ok so google pay won't work. It says I have an unlocked bootloader and/or custom software. I have a stock rom, recovery, bootloader, and the bootloader is locked. Shouldn't it work? I never had this problem after flashing stock and relocking my old Moto X Pure.
ptn107 said:
reflashed the stock rom (OPW27.1)
Click to expand...
Click to collapse
I am not able to help with removing the boot message you're seeing, but is that copy of the stock rom you flashed still available and is it for Android One/Fi?
Yes and yes.
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
did you managed to remove the message? I'm having the same problem
My theory:
You've flashed an original signed stock rom, but that stock rom signature is not the same of the bootloader.
CypherPotato said:
My theory:
You've flashed an original signed stock rom, but that stock rom signature is not the same of the bootloader.
Click to expand...
Click to collapse
Hi, I have the same problem and I have flashed the rom of this post. How could it be solved?. Thanks.
ptn107 said:
Yes and yes.
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Does this help?
jsis83 said:
Hi, I have the same problem and I have flashed the rom of this post. How could it be solved?. Thanks.
Click to expand...
Click to collapse
How have u flashed it?
My payton bootloader is blocked and I can't unlock it.
How did u unlocked your bootloader?
CypherPotato said:
How have u flashed it?
My payton bootloader is blocked and I can't unlock it.
How did u unlocked your bootloader?
Click to expand...
Click to collapse
https://www.getdroidtips.com/unlock-bootloader-moto-x4/
CypherPotato said:
My theory:
You've flashed an original signed stock rom, but that stock rom signature is not the same of the bootloader.
Click to expand...
Click to collapse
How to solve this?
so are we all mad? I've googled for hours, it seems to be you need a factory image of our phones to correct this problem.
figured it out, you need to supply your own keystore to remove the message in fastboot
https://youtu.be/OfWFmhucWlg?t=15m33s
how do you match rom to the correct bootloader? I've installed the 8.0.0 rom I get the same boot error as stated above. I'm trying to get everything back to stock to get the 8.1 update
we would need a factory image, that Motorola never will provide..
squanchy said:
we would need a factory image, that Motorola never will provide..
Click to expand...
Click to collapse
Isn't this exactly that?
https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
jhedfors said:
Isn't this exactly that?
https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
Click to expand...
Click to collapse
if it was a real factory image it would contain a developer keystore in the image, and people wouldn't get the yellow bootloader warning message..
Like I get from all these images posted on this Forum.
If the Keystore doesn't match your original phones Hardware Keystore, it uses the Image's keystore instead. A factory Image, has no keystore or sometimes a universal keystore, and you won't get the mentioned error.
I obtained all this information just watching a Android Developer talk about Verified Booting, but it never goes into detail how to remedy this issue. So unless I spend hours and hours learning how to re-compile an image from source, or figure out where my keystore is located, I'll be stuck with this message.
Because each manufacturer is different, they don't always follow the same Practices.
Hi, is there anyone who fix it finally? I have exactly the same problem. After update on Pie, the message "verity mode is set to disable" is displayed while booting. I'm desperate, I really don't know how to fix it. I tried almost everything
PlaviiCZ said:
Hi, is there anyone who fix it finally? I have exactly the same problem. After update on Pie, the message "verity mode is set to disable" is displayed while booting. I'm desperate, I really don't know how to fix it. I tried almost everything
Click to expand...
Click to collapse
You can't just ignore it? It does not affect functionality.
ptn107 said:
You can't just ignore it? It does not affect functionality.
Click to expand...
Click to collapse
I think it does, Google Pay cannot add my debet card cause it says "Your device is rooted or customized".
https://twrp.me/motorola/motorolamotoonepower.html
__NOT TESTED YET__
testing version of lineage 16: https://androidfilehost.com/?w=files&flid=283156
HOW TO FLASH:
boot twrp with fastboot: http://build.twrp.me/twrp-3.2.3-1-chef.img
SUPPPPPERRRR IMPORTANNNNTTTTTTTTT flash copy-partitions-AB.zip (if you don't device will brick) : https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
flash lineage
reboot
find more info in moto x4 lineage thread : https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
STOCK FIRMWARES to restore back to stock : https://mirrors.lolinet.com/firmware/moto/chef/
report bugs to me with logcat
Hey, thanks a ton for the ROM but how to unlock the bootloader?
And also, we do not have the device yet. It is supposed to go on sale on 5th October!
Hello guys is that possible get china version P30 Note and install One power firmware on it? thanks.
ITMASTER said:
Hello guys is that possible get china version P30 Note and install One power firmware on it? thanks.
Click to expand...
Click to collapse
Possibly "Yes", if the hardware is same, firmware will install, (I dont know about the modem firmware though). But no OTA for you.
You can give it a try...
Ok I will get an chinese version soon. Then we can see. it has an model number XT1942-1. whats the one power model number??
ITMASTER said:
Ok I will get an chinese version soon. Then we can see. it has an model number XT1942-1. whats the one power model number??
Click to expand...
Click to collapse
I will try to find it for you if possible now, but I will buy the device on 5th of October. Hoping to help you more once I get my hands on!
All I know that the device name is "chef" and/or "chef_sprout".
smyaknti said:
I will try to find it for you if possible now, but I will buy the device on 5th of October. Hoping to help you more once I get my hands on!
All I know that the device name is "chef" and/or "chef_sprout".
Click to expand...
Click to collapse
Thanks bro )) I will have my device on hands not soon then Oct 20 so we can see.
smyaknti said:
Hey, thanks a ton for the ROM but how to unlock the bootloader?
And also, we do not have the device yet. It is supposed to go on sale on 5th October!
Click to expand...
Click to collapse
just run the command on adb in fastboot mode
_fastboot oem unlock_
Bristow Xavier said:
just run the command on adb in fastboot mode
_fastboot oem unlock_
Click to expand...
Click to collapse
But the last motorola device I unlocked required a key to unlock the bootloader, which was exclusively tied to my device and my motorola account. They have strict warranty regulations refarding unlocking. How is it different this time?
smyaknti said:
But the last motorola device I unlocked required a key to unlock the bootloader, which was exclusively tied to my device and my motorola account. They have strict warranty regulations refarding unlocking. How is it different this time?
Click to expand...
Click to collapse
since it's an Andoid One device...:laugh:
Bristow Xavier said:
since it's an Andoid One device...:laugh:
Click to expand...
Click to collapse
Erm, okay. Lets see. I didn't find proper evidence on how it was supposed to be done in the moto x4 android one variant. Can you provide any thread or site having the guide? ?
erfanoabdi said:
__NOT TESTED YET__
testing version of lineage 16: https://androidfilehost.com/?w=files&flid=283156
HOW TO FLASH:
boot twrp with fastboot
SUPPPPPERRRR IMPORTANNNNTTTTTTTTT flash copy-partitions-AB.zip (if you don't device will brick) : https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
flash lineage
reboot
find more info in moto x4 lineage thread : https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
STOCK FIRMWARES to restore back to stock : https://mirrors.lolinet.com/firmware/moto/chef/
report bugs to me with logcat
Click to expand...
Click to collapse
i was really surprised and happy to learn that you are actually the official maintainer of Lineage OS for payton, so i was curious if
you're going to buy this device and develop roms.
I've avoided Moto devices past year because the specs and high price which reflected on the development(in the price range i could afford), it wasn't much. but this device has really good specs so i hope developers like you get on board so noobs like me will have better functioning roms.
does unlocking the bl erase user data?
Deleted
SOMEONE PLEASE HELP ME OUT
i unlocked boot loader and flashed twrp
but somehow i could not boot into it with hardware key combos, but adb commands
i could boot into my system then, but to fix the twrp problem i flashed twrp again from twrp
now the phone boots into twrp with hardware keys but not to the system anymore
even if i press reboot to system from twrp, it still reboots into twrp the next boot
For further queries and help, development join here
t.me/MotoOnePower
funeralfog said:
SOMEONE PLEASE HELP ME OUT
i unlocked boot loader and flashed twrp
but somehow i could not boot into it with hardware key combos, but adb commands
i could boot into my system then, but to fix the twrp problem i flashed twrp again from twrp
now the phone boots into twrp with hardware keys but not to the system anymore
even if i press reboot to system from twrp, it still reboots into twrp the next boot
Click to expand...
Click to collapse
In twrp , reboot menu choose Power Off option & and try On ur ph hope its work for you
funeralfog said:
SOMEONE PLEASE HELP ME OUT
i unlocked boot loader and flashed twrp
but somehow i could not boot into it with hardware key combos, but adb commands
i could boot into my system then, but to fix the twrp problem i flashed twrp again from twrp
now the phone boots into twrp with hardware keys but not to the system anymore
even if i press reboot to system from twrp, it still reboots into twrp the next boot
Click to expand...
Click to collapse
You're on the One Power or P30 Note?
mitu725 said:
In twrp , reboot menu choose Power Off option & and try On ur ph hope its work for you
Click to expand...
Click to collapse
Didn't
---------- Post added at 05:46 AM ---------- Previous post was at 05:46 AM ----------
smyaknti said:
You're on the One Power or P30 Note?
Click to expand...
Click to collapse
One power
Hello everyone, everything good?
How do I access EDL mode on the moto z3 play, please?
Thank you,
Josenil Santana
josenilsantana said:
Hello everyone, everything good?
How do I access EDL mode on the moto z3 play, please?
Thank you,
Josenil Santana
Click to expand...
Click to collapse
Is the bootloader unlocked?
Sent from my Moto E (4) using Tapatalk
Unfortunately not, I made a mistake when flashing the rom stock, the script contained the command to block the bootloader before the rom stock ended the process.
sd_shadow said:
Is the bootloader unlocked?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
josenilsantana said:
Unfortunately not, I made a mistake when flashing the rom stock, the script contained the command to block the bootloader before the rom stock ended the process.
Click to expand...
Click to collapse
if you have stock boot (unaltered by Magisk) try LMSA.
I just went through a nightmare, and LMSA saved my phone. But it would only work if my bl was stock.
considering how your BL is locked, I think you can recover your phone in LMSA, then unlock it and chew bubblegum.
Unfortunately not. The LMSA recognizes the cell phone but does not flash stock ROM. I will have to send for technical assistance. Crying. Thanks for listening.
kewlzter said:
if you have stock boot (unaltered by Magisk) try LMSA.
I just went through a nightmare, and LMSA saved my phone. But it would only work if my bl was stock.
considering how your BL is locked, I think you can recover your phone in LMSA, then unlock it and chew bubblegum.
Click to expand...
Click to collapse
josenilsantana said:
Unfortunately not. The LMSA recognizes the cell phone but does not flash stock ROM. I will have to send for technical assistance. Crying. Thanks for listening.
Click to expand...
Click to collapse
can you sideload the firmware?
I don't have stock recovery working
kewlzter said:
can you sideload the firmware?
Click to expand...
Click to collapse
Did you get into EDL mode? I have my moto z3 play XT1929-6 with the booloader of the XT1929-4 and I get an error when trying to update it with LMSA or fastboot
YggCraft said:
Did you get into EDL mode? I have my moto z3 play XT1929-6 with the booloader of the XT1929-4 and I get an error when trying to update it with LMSA or fastboot
Click to expand...
Click to collapse
I had to flash bootloader and recovery from the downloaded LMSA firmware zip, then LMSA worked fine.