Related
So i messed up when trying to update my watch and somehow deleted the firmware so my watch bootloops upon start-up, any way to fix this?
Im have the same problem. Im stuck in bootloop after trying to flash custom kernel. I can not rech recovery. Not original recovery or TWRP. Fastboot works. What to do?
Is there any restore image to flasH?
Here are three solutions in one answer, because you did not give quite enough info.
First, try holding the button on boot up. Hopefully that will get you into usb mode. If it works, download the sony software, and go to the help section, and download and install the update.
Option two,
Code:
adb reboot recovery
Or, download the version of twrp for your build as well as your original image, and use fastboot.
Code:
Fastboot boot twrp.img
then use twrp to install the factory zip. You can do this directly in fastboot too, but it is more difficult because fastboot only installs each image separately. If I knew what versions of software you had, I could help you find the images you need.
I have tried both fastboot flash and fastboot boot for both original recovery and also TWRP, but non of the recoverys will boot, not even with Fastboot boot.
The command lines says OK on my PC, It is getting downloaded, and it says it is booting / flashed [OKAY].
But all I get on my Smartwatch 3 is bootloop.
My Smartwatch 3 is OEM unlocked. I even tried to lock it, and unlock it again.
I have full contact with fastboot on my PC, all the commands are taken in and seems to work, but my smartwatch won't boot no system or no recoverys. Only USB-mode and Fastboot mode...
I have also tried to clear cache and userdata in fastboot after OEM Unlock.
I will try the Sony Software now. That is my last way out I Think.
The Sony PC Companion software from sony's website worked for me to save my smartwatch from bootloops . I just did a update and installed it over what was already on the smartwatch.
Thanks lekofraggle for quick answeres. I had no idea the PC Companion had this feature.
SimDroid, I am glad that helped. If it hadn't, the next step would be to flash an image through fastboot. That would be scary, because it sounds like your boot loader was corrupt. It's nice to know the usb and PcCompanion piece still worked. Another reason this watch is incredible.
Cheers.
does anyone have a download for the original (5.0.2 im guessing) ROM for this watch? I want off the rubbish 5.1.1 update before i am forced to sell the watch due to the terrible battery
The smartwatch works as it should now, original recovery and everything is back!
So, if i may go back to where it started?
I noticed now that I flashed the custom kernel for the watch built for wrong firmware. Im on 5.1.1, and there doesnt seem to be a developed shared kernel with all four cores unlocked for it.
Im also interested in where I can find those images to flash via fastboot as you mentioned lekofraggle
Can anyone help me with this? I got TWRP RC and this is my first thing I've done to my pixel XL .... I go to cmd prompt...
Typed:
Fastboot boot twrp.img
Flashes TWRP logo like it's failing to load. I should mention I am in the android beta program with it. I wouldn't be against rolling back at this point since my phone reset all my data (if I knew how). I'm on NPG05E
Downloading public release OTA now
reflash recovery didn't help?
and if you solve problem please share solution
I had to download a stock image and fastboot that one ... then I could proceed. A bit of a hassle but much quicker than waiting for the OTA to install me back to 7.1.1
while following these instructions in the youtube video named Moto G6 2018 Install Twrp & Root Easy Tutorial 757 or 12:44 at this part i must have downloaded the wrong file since my build model is XT1922-9 type M373B could someone help me resolve me issue so i can fix my phone and finish the root cause my phone refuses to boot
Provide more info about your device including device variant, os version. More info the better so we know how to help you.
Jleeblanch said:
Provide more info about your device including device variant, os version. More info the better so we know how to help you.
Click to expand...
Click to collapse
It's a moto g6 play android 8 or it still turns on but it's stuck on the bootloader screen and I need help fixing that and finishing the rooting of my phone
kc02141994 said:
It's a moto g6 play android 8 or it still turns on but it's stuck on the bootloader screen and I need help fixing that and finishing the rooting of my phone
Click to expand...
Click to collapse
I figured out that much from your first post, I was referring to which variant specifically (ex: 192x-x) and do you know what the stock factory firmware version is?
Jleeblanch said:
I figured out that much from your first post, I was referring to which variant specifically (ex: 192x-x) and do you know what the stock factory firmware version is?
Click to expand...
Click to collapse
i dont know but all i know is my phones build model is XT1922-9 TYPE M373B the phone still turns on but it goes to the bootloader menu with the error message start up failed your device didint start up successfully use the sofware repair assistant on your computer to repair your device connect your device to your computer to get the software repair assistant AP fastboot flash mode secure error failed to load kernal fastboot reason fall through from normal boot i want to fix my phone and finish rooting it so i can use the wifi tether app and i dont know what to do which is why im asking for help i followed the instructions from that video but i downloaded and put in the wrong file i think my phone can be finished rooting and fixed so if i could just get the file i need i can finish rooting and use my phone again
kc02141994 said:
i dont know but all i know is my phones build model is XT1922-9 TYPE M373B the phone still turns on but it goes to the bootloader menu with the error message start up failed your device didint start up successfully use the sofware repair assistant on your computer to repair your device connect your device to your computer to get the software repair assistant AP fastboot flash mode secure error failed to load kernal fastboot reason fall through from normal boot i want to fix my phone and finish rooting it so i can use the wifi tether app and i dont know what to do which is why im asking for help i followed the instructions from that video but i downloaded and put in the wrong file i think my phone can be finished rooting and fixed so if i could just get the file i need i can finish rooting and use my phone again
Click to expand...
Click to collapse
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Jleeblanch said:
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Click to expand...
Click to collapse
ok that problem solved now im stuck on an infinite bootloop after i do the parts where the guy says wipe then download those files from the sd card and when i reboot the phone it does says N/A on the top left and starts boot looping
Jleeblanch said:
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Click to expand...
Click to collapse
i really need help on this i cant finish the root i dont know what im doing wrong im up to the part in the video i watched and after i finished doing that part it begins infinite rebooting and i dont know what to do i installed the right file did everything he did but instead of getting the message in the center i get N/A on the top left and then infinite reboots
Jleeblanch said:
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Click to expand...
Click to collapse
new problem i cant install magiks and now it says theres no OS installed this phone is seriously screwed up and its one of my only sources of internet
kc02141994 said:
new problem i cant install magiks and now it says theres no OS installed this phone is seriously screwed up and its one of my only sources of internet
Click to expand...
Click to collapse
Ok, well we're getting somewhere at least. Sounds like you have the right boot.img at the very least. Now we need to find you the right stock firmware (or even at minimum a system.img and vendor.img from some else with the same device).
I'll look around to see what I can find.
Next thing I need from you is to connect your device to the computer and reboot to bootloader and get me the output of..
Code:
fastboot getvar all
and copy/paste it to https://hastebin.com or copy/paste it to a text file and upload the text file as an attachment here (or wherever you want and post the link) so I can review it. That should tell me what I need to know to help you a little better. Do NOT just copy/paste the output into a post please.
Hello everyone,
My Mi A2 Lite just died today. I was on stock 8.1 rooted and suddenly it freezes so I rebooted it and I got stuck on Android One logo WITHOUT ANY animation.
I tried to boot into recovery via adb but I get stuck on TWRP logo. I tried to flash fastboot image but nothing changes....
I really need help because I'm out of options
pocchio said:
Hello everyone,
My Mi A2 Lite just died today. I was on stock 8.1 rooted and suddenly it freezes so I rebooted it and I got stuck on Android One logo WITHOUT ANY animation.
I tried to boot into recovery via adb but I get stuck on TWRP logo. I tried to flash fastboot image but nothing changes....
I really need help because I'm out of options
Click to expand...
Click to collapse
Two quick questions:
1.The phone died on its self without your intervention or...?
2.Have you tried to flash the stock firmware via MiFlash , while the phone is in edl mode(the command is: fastboot oem edl)?
1) yes, it got stuck so I rebooted it
2) I tried flashing with MiFlash tool in fastboot mode. When I connect it in fastboot edl the mi flash tool sees it as COM and therefore I’m not able to flash it.
I’m I doing something wrong?
pocchio said:
Hello everyone,
My Mi A2 Lite just died today. I was on stock 8.1 rooted and suddenly it freezes so I rebooted it and I got stuck on Android One logo WITHOUT ANY animation.
I tried to boot into recovery via adb but I get stuck on TWRP logo. I tried to flash fastboot image but nothing changes....
I really need help because I'm out of options
Click to expand...
Click to collapse
pocchio said:
1) yes, it got stuck so I rebooted it
2) I tried flashing with MiFlash tool in fastboot mode. When I connect it in fastboot edl the mi flash tool sees it as COM and therefore I’m not able to flash it.
I’m I doing something wrong?
Click to expand...
Click to collapse
I think you are confusing some things here; adb is not an option now so you can´t boot device normally and also you said "fastboot edl" but they are different modes.
While in fastboot how did you try booting to TWRP image? (you said through adb but this is not right)
Can you get to fastboot? (hold vol down while booting, should see a rabbit on the screen)
pocchio said:
1) yes, it got stuck so I rebooted it
2) I tried flashing with MiFlash tool in fastboot mode. When I connect it in fastboot edl the mi flash tool sees it as COM and therefore I’m not able to flash it.
I’m I doing something wrong?
Click to expand...
Click to collapse
When your phone is in EDL mode(you won't be seeing any logo on your phone ,only black screen) it's absolutely normal to see the device as COM port , because the device is in another factory mode. And there is no problem flashing stock ,when your phone is seen as COM port. So if you can't flash the stock firmware in fastboot mode or EDL mode , maybe you have a hardware issue. To be sure -take a screenshot of the error in MiFalsh when the phone is in edl Mode (seen as a COM port) and you try to flash the stock firmware.
Ok, I understand the difference between EDL (black screen) and Fastboot mode. I can get in both mode. I tried to flash fastboot stock rom (taken from the thread in xda) and everything goes smoothly, but it stays in fastboot mode at the end and when I send the command fastboot reboot it gets stuck again on the Android One logo (no animation).
When I tried the EDL mode, mi flash returns something missing (I will post the screenshot asap) and it seems like is not the right thing I'm trying to flash or something similar (I will post more information as soon as I can). (I'm trying to flash the same fastboot roms found in xda)
So, just to make sure I'm doing the right thing, where I can find the stock firmware to flash?
Thanks again for your help!
pocchio said:
Ok, I understand the difference between EDL (black screen) and Fastboot mode. I can get in both mode. I tried to flash fastboot stock rom (taken from the thread in xda) and everything goes smoothly, but it stays in fastboot mode at the end and when I send the command fastboot reboot it gets stuck again on the Android One logo (no animation).
When I tried the EDL mode, mi flash returns something missing (I will post the screenshot asap) and it seems like is not the right thing I'm trying to flash or something similar (I will post more information as soon as I can). (I'm trying to flash the same fastboot roms found in xda)
So, just to make sure I'm doing the right thing, where I can find the stock firmware to flash?
Thanks again for your help!
Click to expand...
Click to collapse
Here is the stock firmware from Xiaomi site:
https://en.miui.com/getrom-354.html?m=yes&mobile=2
Don't worry that it says MIUI , the firmware is Android One , they just forgot to change the name from MIUI to Android One , I have already tried it ,and I can confirm that it's 100% stock Android One firmware , good luck!
Ok I performed the flash but the error i get is new.
I get the error ACK count don't match!
I tried the version
daisy_global_images_V10.0.9.0.PDLMIXM_20190514.0000.00_9.0_f9d0c739e0.tgz
pocchio said:
Ok I performed the flash but the error i get is new.
I get the error ACK count don't match!
I tried the version
daisy_global_images_V10.0.9.0.PDLMIXM_20190514.0000.00_9.0_f9d0c739e0.tgz
Click to expand...
Click to collapse
I will give a solution in a minute
EDIT: Are you sure your bootloader is unlocked? (fastboot oem unlock)
You have two choices , you need to find an older version of MiFlash beta , i'll give you a video :
https://m.youtube.com/watch?v=-7O1Svib14g
In the video description you can find a link for the MiFlash beta ,I hope it helps.
If not , you'll have to consider the Testpoint unbrick method , there are several guides.
OK, thanks to the use of the BETA version I was able to flash the rom but unfortunately I still get the same AndroidOne logo without any animation....
I really don't know what to do now...
Yes the bootloader is unlocked and I checked with fastboot getvar
pocchio said:
OK, thanks to the use of the BETA version I was able to flash the rom but unfortunately I still get the same AndroidOne logo without any animation....
I really don't know what to do now...
Yes the bootloader is unlocked and I checked with fastboot getvar
Click to expand...
Click to collapse
Ok , it totally sound like some kind of hardware issue with the storage . Is there any way to boot in TWRP ?
Download the TWRP version 3.3.3-1 offain and try to boot with it (fastboot boot recovery(the name of the recovery).IMG) and wait until the TWRP logo disappear. Wait at least 1 minute if the logo doesn't disappear , then in my opinion , you have a hardware problem , if you succeed to booting in TWRP download the GM 1.1 version from this thread :
https://forum.xda-developers.com/mi-a2-lite/development/9-miui-rom-t3960704
and flash it via TWRP. Then reboot and leave the phone without touching at least 10 minutes (until you see some movement like on the bottom of the screen , there will be a MI logo , right above the logo if you see 3 dots moving , then you're saved . From there we can proceed , but if you can't flash even this rom , if nothing helps. I hope you have a warranty , reflash the stock rom with the option flash_all_lock and go to your warranty service center.
EDIT: I googled and found another issue, that might be causing this strange situation: You may got scammed , and the device might not be a Mi A2 Lite , but rebranded Redmi 6X. See this thread:
http://en.miui.com/thread-5984082-1-1.html
If your phone is displayed "Wayne" ,not "Daisy" ,then you'll have to flash a Redmi 6X firmware to get rid of the bootloop
nikoman1987 said:
Ok , it totally sound like some kind of hardware issue with the storage . Is there any way to boot in TWRP ?
Download the TWRP version 3.3.3-1 offain and try to boot with it (fastboot boot recovery(the name of the recovery).IMG) and wait until the TWRP logo disappear. Wait at least 1 minute if the logo doesn't disappear , then in my opinion , you have a hardware problem , if you succeed to booting in TWRP download the GM 1.1 version from this thread :
https://forum.xda-developers.com/mi-a2-lite/development/9-miui-rom-t3960704
and flash it via TWRP. Then reboot and leave the phone without touching at least 10 minutes (until you see some movement like on the bottom of the screen , there will be a MI logo , right above the logo if you see 3 dots moving , then you're saved . From there we can proceed , but if you can't flash even this rom , if nothing helps. I hope you have a warranty , reflash the stock rom with the option flash_all_lock and go to your warranty service center.
EDIT: I googled and found another issue, that might be causing this strange situation: You may got scammed , and the device might not be a Mi A2 Lite , but rebranded Redmi 6X. See this thread:
http://en.miui.com/thread-5984082-1-1.html
If your phone is displayed "Wayne" ,not "Daisy" ,then you'll have to flash a Redmi 6X firmware to get rid of the bootloop
Click to expand...
Click to collapse
I will now try your solution, I just tried the testpoint unbrick method but still same problem.
The output from fastboot getvar all shows a DAISY bootloader. Where I can see the real name of the device to see if it is a Mi 6X?
pocchio said:
I will now try your solution, I just tried the testpoint unbrick method but still same problem.
The output from fastboot getvar all shows a DAISY bootloader. Where I can see the real name of the device to see if it is a Mi 6X?
Click to expand...
Click to collapse
the command is: fastboot oem get-product-model
nikoman1987 said:
the command is: fastboot oem get-product-model
Click to expand...
Click to collapse
Unfortunately I get unknown command.
Additionally when I try to boot the TWRP I get stuck at logo forever....
pocchio said:
Unfortunately I get unknown command.
Additionally when I try to boot the TWRP I get stuck at logo forever....
Click to expand...
Click to collapse
tried the command too, it doesn't work.
So test point doesn't work too.. That's bad news
EDIT: fastboot getvar product command works , you can try it
And another question , have you tried to boot with patched boot.IMG ?
It seems indeed some hardware problem... Is there any way I can try to boot something from the SD card? (In order to rule out the storage problem....
pocchio said:
It seems indeed some hardware problem... Is there any way I can try to boot something from the SD card? (In order to rule out the storage problem....
Click to expand...
Click to collapse
You need a recovery to flash , which has a specific partition in the phone storage. You can flash only via fastboot . You need to boot into recovery , so try with a patched boot image for your version of the rom
---------- Post added at 02:47 PM ---------- Previous post was at 02:38 PM ----------
pocchio said:
It seems indeed some hardware problem... Is there any way I can try to boot something from the SD card? (In order to rule out the storage problem....
Click to expand...
Click to collapse
So the last resort , we'll try to flash the ROM that I have mentioned before via fastboot. Place the zip file GM 1.1 in your PC (it has to be in the same directory as your adb and fastboot tools)
then open cmd and run the command
fastboot flash (the full name of the zip).zip
and hit enter
maybe that will solve it
And if this doesn't help again... type these fastboot commands :
fastboot format userdata
fastboot format system
fastboot format cache
fastboot format vendor
fastboot format recovery
fastboot format boot
then try again to reflash the stock rom (first try in edl mode ,if this doesn't do anything ,you'll have to format everything via fastboot commands again ,and try to flash the ROM in fastboot mode)
And if this doesn't help too... Then you're free to hit that ? in the ground hahahah (just kidding)
Tried both these two last but nothig works, I always get the same problem.
I just saw your comment on patched boot, can you elaborate a little bit on this?
I'm honestly very close to throw it in the trash
pocchio said:
Tried both these two last but nothig works, I always get the same problem.
I just saw your comment on patched boot, can you elaborate a little bit on this?
I'm honestly very close to throw it in the trash
Click to expand...
Click to collapse
which version of the firmware you are flashing? 10.0.9.0 or another version , so I can send you a link and walk you through the procedure.
And when you flashed the GM 1.1 the boot screen didn't changed from Android one? (the GM 1.1 version is a MIUI stock port and has to change your boot screen to black screen with white MI logo on it) It is very important to know
One of my friends told me to try this: just open the directory of the stock firmware , navigate to flash_all.bat and run the bat file (NOT THE FLASH_ALL_LOCK!!!) and wait for the end of the process. He had a similar problem , and it worked. He explained that for any reason , the recovery was the problem , because it was flashed in the boot partition. When you use flash_all.bat The file will erase all partitions and rewrite them. MiFlash won't , so try that
I recently found a moto g5 in one of my fellow "old tech" drawers and decided to turn it on, it was on the
1. May 2018
Security patch on nougat, I decided to use the inbuilt system updater to go to Oreo, and now....it crashes during flashing process after about 25-30% completion,
Now im guessing boot or System is not properly installed due to the zip file having aborted mid-flash
Recovery doesn't properly boot as that is used to install the update and thus imidiately goes to doing that
Also, it hang up during installation on random times, it basically has a record of 2mins of not crashing whilst still being stuck on 30%
I got it to "boot" when trying factory mode, yeah it crashed mid boot animation...not a help
Any suggestions? EDL mode maybe?
Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778
If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop
TheFixItMan said:
Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778
If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop
Click to expand...
Click to collapse
SOMEHOW it just decided to boot, I have never seen such behaviour, even on my g5s which I had for a while, (and am currently daily driving to school if it wasn't closed....NEVER
Maybe I'll unlock it and try somehow recreating it? Well it's in physically rough shape but all components inside are fine...so that can't be the reason....?
My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?
anonymous724 said:
My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?
Click to expand...
Click to collapse
Flash the stock rom and boot the device. But this will format the device.
To save data, remove the command fastboot erase userdata
Fastboot erase customisation.
Apps may be gone, but files In internal storage will be safe, like download,photos, music.
riyan65 said:
Flash the stock rom and boot the device. But this will format the device.
To save data, remove the command fastboot erase userdata
Fastboot erase customisation.
Apps may be gone, but files In internal storage will be safe, like download,photos, music.
Click to expand...
Click to collapse
no luck on this front, gets to the passcode screen, write in passcode then motorola logo shows and screen keeps on turning off and on.
Thanks for the effort though, much appreciated
Mine is similar to yours. Initially was on permanent loop of the following:
1. Boot to moto g splash screen... Repeat
2. Boot to lock screen then usually a few loops of 1. (after entering the patter or left Idle)
The phone initially didnt have any developer options enabled.
I wiped cache using recovery mode. Restarted and pretty much the same thing except that it would on rare occasions actually fully boot up usually only last a few minutes before cycling between steps 1 and 2 above.
I used those rare boot ups to backup all files and enable any USB debugging /oem unlock (incase I need to use a solution dependent on these being enabled.)
Factory resetted it and its still the same with the random successful boot amongst the numerous failed ones.
I managed to hook it up to Lenovo's Lmsa and flash the latest ROM. Now I get a lot more successful boots but still loops every so often. The downside is that I can no longer do any functions that make use of the audio/ mic/ video (can take pictures). If I do then it will crash and loop.
The hardware test on the LMSA passed for every component before flashing to the latest version. Post update it predictably fails on the audio/ mic components.
I guess I'll have to go back to the old version to see I get the audio back.