So, here is the problem i am facing with my moto E
I followed the tutorials from this site and had flashed my MOTO E to stock ROM 3-4 times due to different reasons, i was successfully able to do that using the STOCK ROM that i had for android kitkat 4.4.4. Last month i updated my moto E to android lollipop. After that it kept asking me to install a 12MB update which i tried installing quite some times but was not able to install. It showed some error while installing the same. So, i started ignoring that. A couple of days ago i once again tried to install that update and after installing the update when the phone turned on, it logged on into FASTBOOT MENU saying:
hab check failed for boot
failed to validate boot image
Fastboot reason: Fall-through from normal boot mode
So, i thought Flashing it once again might solve the issue. When i tried flashing it, on the command screen it gives ERROR for 4 files i.e. boot.img, system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2 saying::
<bootloader> invalid signed image
<bootloader> preflash validation failed
And on my phone screen it says "Invalid PIV signed image"
For all other instructions it says OKAY
Now it is again and again turning ON into this fastboot mode only...
Since i already had flashed my moto using the same custom rom , i think the files must be okay...
PLEASE HELP :'(
Why did you flashed 4.4.4 and then ota updated to 5.1 ? This process should've bricked your device in the first place.
Anyway 5.1 stock image files are available, did you tried flashing them? (fastboot mode)
-z3r0- said:
Why did you flashed 4.4.4 and then ota updated to 5.1 ? This process should've bricked your device in the first place.
Anyway 5.1 stock image files are available, did you tried flashing them? (fastboot mode)
Click to expand...
Click to collapse
sorry, i didn't knew that i shouldn't update my phone after installing the stock rom. No i haven't tried flashing my phone with android 5.1 stock file, i thought maybe flashing my phone with android 4.4.4 will downgrade my phone back to kitkat. Will try it now...will be helpful to me if you could get me a link for android 5.1 stock file as well, i tried finding the same, but it says for moto e2 which comes originally with lollipop but mine comes with android 4.4, its so confusing for me which stock file to download....
thanks for the help
Here : http://forum.xda-developers.com/showthread.php?t=2755857
"RetailDSDS" - Is for Indian version
-z3r0- said:
Here : http://forum.xda-developers.com/showthread.php?t=2755857
"RetailDSDS" - Is for Indian version
Click to expand...
Click to collapse
tried it, still giving the same error, preflash validation error :'(
Related
Hi there,
My moto e 2nd gen got stuck in bootloader and won't boot.
The monitor displays as below:
**********************************************
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
EROOR: Failed to pass validation, backup fastboot
Fastboot Reason: Fall-through from normal boot mode
BL:
Baseband: M8916_2020629.41.03.21.51R SURNIA_RECTA_CUS
Product/Variant: surnia XT1527 8GB P3
Serial Number:
CPU:
eMMC:
DRAM
Console [NULL]: null
Battery OK
Device is LOCKED. Status Code: 0
Software status: Official
Connect USB Data cable
**************************************************
In the Recovery Mode display, I see "qe 0/0" which I learned from the other thread that it means the device has never been rooted.
Below is how this happened;
I used the app called KingRoot.
But the app says failed to root the device.
My phone acted weird so I uninstalled KingRoot.
Then I tried to remove the .exe file of KingRoot but failed somehow.
Right after I just turned on some secure feature (which warns the user that the app may be harmful?) of the device, the device went black and displayed the bootloader screen.
Below is what I have done so far:
Wipe cache partition (successful), then Reboot the system (Failed)
Wipe data/factory reset (successful), then Reboot the system(Failed)
Apply update from ADB with the stock Rom I found in the [http://firmware.center/firmware/Motorola/Moto E (2nd gen-2015)/Stock/XT1527/] but received error as below,
***********************************************
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong.
E:signature verification failed.
Installation failed.
************************************************
Then, I flashed three image files (recovery, boot, bootloader) using fastboot command (without unlocking bootloader).
I did not use the bootloader unlocking command.
So I thought the flashing would failed but somehow succeeded only with recovery.imag.
I believe my device has never been rooted and the bootloader has never been unlocked.
Is it possible that KingRoot has modified some system files even when the device has never been rooted and the bootloader has never been unlocked?
And how can I fix my bricked moto e?
Could someone help me out on this please? :crying:
quicksand99999 said:
Hi there,
Click to expand...
Click to collapse
Flash stock firmware. BTW you asked in the wrong thread. This is for moto e1
drs22 said:
Flash stock firmware. BTW you asked in the wrong thread. This is for moto e1
Click to expand...
Click to collapse
Hi Thank you for the reply and pointing-out.
I re-posted the thread in E 2015.
Regarding flashing stock rom, I flashed three image files and two of them failed due to the older version.
Is it possible to flash the entire files without unlocking the bootloader?
I have got marshmallow stock rom and have never tried to flash.
Hope you reply me back in my thread in Moto E 2015 forum.
Hi experts!
Is there an available factory image of the latest firmware for griffin xt1650-03 for download? I unlocked my boot loader and tried to flash custom firmware now I am stuck in boot loop. My phone was nougat and updated via OTA last week before I decided to unlock boot loader. I tried loading the latest image I got from firmware.center but I am getting Downgrade version and verification failed when flashing stock partition and not loader. Please help
Note: I did this my wifi became unusable after my last OTA (mac 02:00:00:00) and thought using custom firmware would help
And I did not make a back up
Get it in fastboot mode, flash TWRP and root it. That might work.
I am in exactly the same position as OP, although I have successfully installed TWRP and have open bootloader from which I can boot into TWRP no probs. I didnt do a backup (will never again make this error!!)
The problem arises when I try to flash (any) files over to device I get the "Downgrade version and verification failed" like OP when flashing stock Telus rom (telus phone) or any other rom/files.
Rebooting brings me back to the moto unlocked bootloader page (horrible!) and the only way out is to get key combo or fastboot into bootloader/recovery etc.
Tried flashing multiple images as whole or bit by bit, always get the same bad validation message. Finding it hard to believe this 700dollar phone is a brick after literally following MotoS own 'unlock your bootloader' instructions. Never had issues like this on OPO, S6, S7, LG etc.
PC shows android device connected, nothing in the two empty folders that appear. TWRP confirms I have no OS installed and throws me back to bootloader.Wondering if locking bootloader again will allow me to install 'stock' ROM or at least recovery? I have reached my android knowledge limit and am not sure where to go from here, any help much appreciated!
OK. This happened to me. The way that I solved it was by flashing the RETUS NPL86.25.15 and then flashing the OTA 25.17-3-3 through twrp. Although I think I could've saved the headache if the original instructions included flashing the OEM.bin but anyways. That's what I did. Hope it helps.
Thanks. I did try flashing the oem.bin but got partition name error.
Can you link to the files you mention I think it's a kernel and then an OTA image? Thanks again in advance.
What I mean is that when I first started flashing the RETUS rom the instructions skipped that part so I ended up flashing most of the file system without something so it would never boot but it wouldn't loop it'd just hang. So basically you flash everything and then include the OEM.bin after you do the system chunks
So i got my Honor 5x yesterday and thought i would install a custom rom on it since people are recommending it.
Its my first time so i followed guids. I installed adb and fastboot and managed to get TWRP 3.1.1-0- on it.
Btw, i have a Honor 5x
Model KIW-L21
I am able to get into the recovery TWRP. I made a backup and saved the folder "BACKUPS" on my PC.
I then downloaded LineageOS from their Homepage: download (DOT) lineageos (DOT) org/kiwi
I downloaded the latest version. I also downloaded Gapps from Opengapps.org. I downloaded ARM64 version 7.1
I wiped my phone completely and copied the two zip files on the phone. I went to "install", selected LineageOS zip and added Gapps. i swiped right to install and the installation stopped with ERROR 7
I tried to download older versions of LineageOS but the same thing happens. ERROR 7
I then downloaded an olderversion of CM13 with GAPPS 6.0. Again, Error 7
I downloaded XENON HD ZIP from here: mirrors (DOT) c0urier (DOT) net/android/teamhorizon/N/Official/kiwi/
Error 7
I downloaded ASOP from here: downloads (DOT) aospextended (DOT) com/kiwi/
Error 7
I looked up Error 7 and its says it is a security check that figures out, that the ROM is not compatible with the Phone. Some guy told me that this happens a lot and that i should use another rom.
I looked for a solution on youtube and found a guy who said that i can do the following:
Unzip the ROM on your pc, go into \META-INF\com\google\android and open the updater script with Notepad++. Delete the first two lines that says asserts, save, close it again and zip the whole package again.
I copied the new, modifiled rom on the phone with the GAPPS and installed it. This time ERROR 7 didnt appear. GAPPS were also installed. When i boot my device i get in the loading screen from Lineage for about 5-10 minutes. After that, it just restarts and restarts and restarts. I can't get out of the boot loop since I can't remove my battery. when I press VOL UP I come back the TWRP and can wipe the phone again.
I tried that with 3 different LineageOS ROMS and one XENON HD ROM.
I also get into a boot loop where my phone just restarts and restarts and restarts.
I tried to get my backup working so I copied the folder "BACKUPS" on my phone and went to restore in TWRP. but... i found nothing there?
I am super frustrated since my phone is basically dead and I have no idea what I can do.
BTW, every site calls my phone "KIWI" but my model number is "KIW-L21"
As mentioned in Los 14.1 thread (& should be mentioned in all threads), "ROM Firmware Required: No VoLTE firmware! (B360, B370, ...)". You must downgrade your stock rom to B350 at least, before try playing with custom roms (only for kiwi, of course).
Non VoLTE Marshmallow firmware is required. As said by @mauam get in there and have the same process repeated
Thank you for your replies.
The only thing i could find was this thread: https://forum.xda-developers.com/ho...-lineageos-14-1-pre-official-kiw-l24-t3528488
It said there:
Important note:
Stock Firmware B360 and B370 are known to cause bootloops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
All others might work, please do not ask in here how to up- or downgrade!
It doesnt mentioned what that mean and even said "dont ask in here how to downgrade"
I have no idea what all that means. I dont know what stock firmware is, what version i have or how i could downgrade it. I can access TWRP, but still have no OS on it.
edit: this is the full log:
Updateing partition details...
... done
Full SElinux support is present.
MTP Enabled
Installing zip file '/sdcard/lineage-14.1-20170816-nightly-kiwi-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Comparing TZ version TZ.BF.3.0.C3-00025 to TZ.BF.3.0.C3-00022") =="1"
assert failed: kiwi.verify_trustzone("TZ.BF.3.0.C3-00025") == "1"
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-14.1-20170816-nightly-kiwi-signed.zip'
Updating parition details...
...done
Click to expand...
Click to collapse
When i edit the zip file and delete the first two line of the updater scripter with notepad++ as i mentioned above, i can install these ROMS, but they wont boot / are in an infinite Bootloop
So on which firmware you were before flashing Los
PalakMi said:
So on which firmware you were before flashing Los
Click to expand...
Click to collapse
how do i check that?
I was able to get the backup running. So I am back to EMUI 3.1 / Android 5.1.1. Here is a screenshot from my phones status: i.imgur (DOT) com/rCnuOpX.png
Activehannes said:
how do i check that?
I was able to get the backup running. So I am back to EMUI 3.1 / Android 5.1.1. Here is a screenshot from my phones status: i.imgur (DOT) com/rCnuOpX.png
Click to expand...
Click to collapse
Just go to about phone
PalakMi said:
Just go to about phone
Click to expand...
Click to collapse
I did and posted a screenshot above
is it Build number "KIW-L21C432B160"
so... B160?
update:
I just downloaded this:
NEW KIW-L21 C432B350 - D003
from this thread: https://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
I was going to unzip it, copy the "dload" folder on my device, go the the updater and run the "local update package".
And then my phone will be on android 6.0 with b350, right?
The next step would be to start the phone in the recovery TWRP, go to wipe --> advance wipe and select everything (system, data, cache etc). after that i copy the latest Kiwi lineage OS zip rom on my device with the GAPPS 7.1 and try to install them again via TWRP 3.1.1?
Is this right?
I just wanna ask because my phone doesnt work for 2 days now and i dont want to brick it completely. cant afford a new one
Update to marshmallow first (any update before b360, like b320)
Update to marshmallow first (any update before b360, like b320)
Click to expand...
Click to collapse
when i go to the "updater" and and search for a new update it says that there is none. My phone is still on EMUI 3.1/android 5.1.1/b160. Do i need to manually download another firmware? so a B320 patch first (with the dload folder and local upgrade package) and after that the B350 upgrade?
Try manual ota here or search here. If no luck use XDA search bar &/or Google. Good luck.
Activehannes said:
when i go to the "updater" and and search for a new update it says that there is none. My phone is still on EMUI 3.1/android 5.1.1/b160. Do i need to manually download another firmware? so a B320 patch first (with the dload folder and local upgrade package) and after that the B350 upgrade?
Click to expand...
Click to collapse
Try any marshmallow update before b360.
If it didn't work, try the above post.
so i followed this guide: https://forum.xda-developers.com/honor-5x/how-to/manual-ota-update-guide-update-app-t3445976
he describes 2 methods.
I wasnt able to find a B320 update for KIW L21, only for KIW L22 which is the Indian device I think. so I downloaded KIW L21 B330 Denmark. I unzipped the file and copied the dload folder on my device,
i went to update --> menu --> local update --> UPDATE.APP
my phone restarts into TWRP and does nothing. I know that I need the EMUI stock recovery, not TWRP, but no matter how many times I do this, it always restarts into TWRP.
i also tried the other method.
I shut down my phone, press VOLUP and VOLDOWN and Power. The phone goes into the the "honor" loading screen and restats after a few seconds. and restart again and again. If i release the power button before it restarts, it just boots into the system. If I shut it down and hold VOLUP and Power it boots into TWRP. I tried so many different compinations, but i cant get my phone into the EMUI Stock recovery. I read in the other XDA thread, that i need to unlock my phone. So i tried that. i went adb reboot bootloader --> fastboot oem relock CODE. the console did its magic but my phone is still unlocked. And now i cant repeat that command. when i go again into the bootloader and type fastboot oem relock it says:
PS C:\adb> adb devices
List of devices attached
W6HDU17610003396 device
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot oem relock 1524319619165116
...
FAILED (remote: Image verify failed,relock fail)
finished. total time: 1.810s
PS C:\adb> adb devices
List of devices attached
PS C:\adb>
Click to expand...
Click to collapse
So, i still have b160 / android 5.1 on my phone :/ can anyone figure out what went wrong?
Activehannes said:
so i followed this guide: https://forum.xda-developers.com/honor-5x/how-to/manual-ota-update-guide-update-app-t3445976
he describes 2 methods.
I wasnt able to find a B320 update for KIW L21, only for KIW L22 which is the Indian device I think. so I downloaded KIW L21 B330 Denmark. I unzipped the file and copied the dload folder on my device,
i went to update --> menu --> local update --> UPDATE.APP
my phone restarts into TWRP and does nothing. I know that I need the EMUI stock recovery, not TWRP, but no matter how many times I do this, it always restarts into TWRP.
i also tried the other method.
I shut down my phone, press VOLUP and VOLDOWN and Power. The phone goes into the the "honor" loading screen and restats after a few seconds. and restart again and again. If i release the power button before it restarts, it just boots into the system. If I shut it down and hold VOLUP and Power it boots into TWRP. I tried so many different compinations, but i cant get my phone into the EMUI Stock recovery. I read in the other XDA thread, that i need to unlock my phone. So i tried that. i went adb reboot bootloader --> fastboot oem relock CODE. the console did its magic but my phone is still unlocked. And now i cant repeat that command. when i go again into the bootloader and type fastboot oem relock it says:
So, i still have b160 / android 5.1 on my phone :/ can anyone figure out what went wrong?
Click to expand...
Click to collapse
May be i can help u with this .
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
hey did you get it fixed and can you please send the link to the stock rom
yayjk said:
hey did you get it fixed and can you please send the link to the stock rom
Click to expand...
Click to collapse
TRY ASKING THE QUESTION ON THIS THREAD
https://forum.xda-developers.com/android/help/how-to-make-simple-android-apps-qna-t3776780
---------- Post added at 05:00 PM ---------- Previous post was at 05:00 PM ----------
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
TRY ASKING IN THIS THREAD
https://forum.xda-developers.com/android/help/how-to-make-simple-android-apps-qna-t3776780
How to Unbrick Lenovo K8 Plus 4GB
Hi All
I tried many stock roms and many versions of SP flash tool but none helped me to unbrick my lenovo k8 plus (4gb ram).
I was trying to downgrade it to Naugat from Oreo but it shows same error every time.
Error is (SP Flash tool version latest 5.18)
" Error_Status_Sec_Insufficient_Buffer( 0xC002004B)
[Hint]:
Verified boot is enabled.
Please download signed image (md1img-verified.img) or disable verified boot."
Plzzz help same problem
Enabled verified boot ...how to disabled
Same problem my lenovo k8plus
Enabled verified boot ...how to disabled
You need to use "Lenovo Moto Smart Assistant" instead of SPFlash tool to flash and you will be good to go. You can get the tool from the Lenovo official website.
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
Try with Lenovo Moto Smart Assistant. I too have bricked my phone... but I've successfully started my phone using this tool. you will get official signed ROM from here.
you can use LMSA tool to rescue,90% sucessfully ,don't use splashtool beacause it's many error if you choose wrong version
Had the same problem. Can confirm Lenovo's tool sucessfully recovers ohone from bricked state. A lifesaver!
Downloaded from https://lenovomobilesupport.lenovo.com/br/pt/downloads/ds101291-rescue-and-smart-assistant-lmsa
then updated to version 5.9.2.4 from inside the app itself
Sorry if this is posted in the wrong place but I could not find anywhere to post it by following Help threads I just went round and round in circles. Hi I am fairly new to phone modding. I updated my moto e XT1524 to LineageOS 16.1 some months ago. Yesterday I decided to update to 17.1. I followed the instruction to install. I have wiped phone and ran fastboot adb as instructed. I keep gettting -This packeage is for XT1514,XT1524,XT1526......... ect and error7. I have ammended the updater-script as detailed in the "How to fix error 7 " document but the rom will still not load. same error message. I have now noticed that * Required * firmware version must be based on Marshmallow on the Installation section on the main forum page. Can someone help me get the phone back to stock rom or any other rom for that matter. I can get the phone into recovery mode and I have TWRP installed i aslo have SDK tools installed on PC.
@rddxda
TWRP can't be used to flash Stock ROMs. In your case you need QFIL ( read: Qualcomm Flash Image Loader ) to flash a Stock ROM, and also the Motorola USB driver installed on PC.
jwoegerbauer said:
@rddxda
TWRP can't be used to flash Stock ROMs. In your case you need QFIL ( read: Qualcomm Flash Image Loader ) to flash a Stock ROM, and also the Motorola USB driver installed on PC.
Click to expand...
Click to collapse
Thanks for your help, could you please help a little further as I cannot find a stock rom. I have been on the motorola site and followed a few links on the internet but only to find the file is no longer available. Any idea where I can get a stock rom from or can I use QFIL to load a non stock rom?
I have found a stock rom XT1524_SURNIA_RETEUALL_5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml.zip this is not an mbn file, however if I open the zip folder there is a fsg.mbn file in there along with boot, bootloader gpt.bin etc. Is this the file to use with QFIL. Sorry to be a pain but I don't want to make the situation worse.
Also can you tell me if restoring to stock rom will this re-lock the bootloader?
UPDATE: First of all thank-you for all your help - I have learned a lot over the past 6 days (that's how long I have been trying to fix it). I flashed lineage-17.1-20200814-recovery-surnia and then sideloaded adb sideload lineage-17.1surnia.zip. Phone now rebooted in normal mode and showing on PC now OK. So old Moto E XT1524 on Lineage OS 17.1.