Database Users

[Q] Did I brick my Nexus 4?

Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil

I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?

ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.

Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.

aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).

aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.

You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app

try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688

Okay, thanks guys. I'm on it. Will let you know when I'm done.

That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd

I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?

aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.

chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images

aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.

chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:

Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!

Need some help please

Hi guys..
Few of you guys might already know me from around the forums. I know my ins and outs of android but today i am kinda stuck and i have not got a clue what to do. Here is the story.
Currently on my device i have a clear sd card. Only things i have on there is a slimkat build and gapps ready to flash. Problem is when i tried to make a backup it failed. Running TWRP recovery 2.6.0.0. Tried different things to get it working and nothing.
Now i tried to use a toolkit to be able to push the files to flash and get my phone going and still nothing it just goes back into recovery and nothing...Anyways another thing is adb is not working as it should...in recovery it recognizes my phone as connected but when in bootloader it does not
any help would be appreciated

Just some ideas here:
On device:
Try other version of TWRP or Multirom TWRP or CWM.
On PC:
Reinstall driver (Universal Naked Driver)

wcn said:
Just some ideas here:
On device:
Try other version of TWRP or Multirom TWRP or CWM.
On PC:
Reinstall driver (Universal Naked Driver)
Click to expand...
Click to collapse
kinda in the process reflashing stock factory settings again and see what happens..many thanks anyway...
is there anything wrong with TWRP? cause anything i do it fails and i have not got a clue why

There are mixtures of results of peoples using different versions of TWRP/MultiromTWRP/CWM and nobody had a dam* clue what/why causes the incompatibility. Btw, I'm on latest MultiromTWRP which works great for me flashing variants of roms. Anyway, happy reflashing.

why dont you update twrp to 2.6.3.3

rakludnet said:
why dont you update twrp to 2.6.3.3
Click to expand...
Click to collapse
i have..but even that one has given me troubles..the thing that seems to work is when you go into mounts just untick the system and everything seems to work okay..am just surprised that this is an issue though

Please Recovery Stock LG G PAD 7 LTE v410

Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a backup of Recovery
Sorry for my bad English.
thanks

exebuera said:
Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a back of Recovery
Sorry for my bad English.
thanks
Click to expand...
Click to collapse
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api

jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?

dreamtheater17 said:
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
Click to expand...
Click to collapse
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.

jason2678 said:
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
Click to expand...
Click to collapse
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it

Sorry I've never encountered the adb closed problem myself, but I have heard about it before. Some people have reported the following series of commands fixes it:
Code:
adb usb
adb devices
adb kill-server
adb start-server
The first two commands normally don't really do anything and its pretty obvious what the second two do, but some people have reported success doing this.
Some people have reported the closed error was fixed by updating their adb binary. If you're using the android-sdk update platform-tools, or if you're using a standalone adb consider looking for an update for it.
Good luck. That procedure to get things back to normal following using the kdz to restore sounds messy.

dreamtheater17 said:
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Click to expand...
Click to collapse
hi, i have the same problem than u, i wanna know if i can flash the US CELLULAR kdz for solve the partition issue? because i already flash the kdz test from ATT

jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?

mxpxboi said:
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
Click to expand...
Click to collapse
If you applied an OTA with a custom recovery installed it might soft brick your tablet, but I don't see why that would stop it from detecting and downloading the update. It is always safest to flash stock recovery, fully unroot, and undo any modifications you've made to /system before taking an OTA, but some devices are more picky than others. With what you're describing I'm afraid that even if you do unroot and flash stock recovery your tablet still won't find the OTA.
Do you have a nandroid backup of an unmodified stock ROM you could restore?
And just so you know that lollipop bootloader is not vulnerable to the bump exploit, so no custom recovery or ROMs if you get it to apply.

Whenever I type "reboot recovery" in terminal emulator, it boots straight to factory reset. I have tried this multiple times with both dd and flashify. Do you know what causes this? I'm downloading the OTA right now, I hope it doesn't wipe then too...

please help
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance

Devil911 said:
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Click to expand...
Click to collapse
Download the timmytim stock ROM, and extract the boot.img from it. There are probably quicker ways, but having the stock ROM on hand is a good idea.
Sent from my Amazon Fire using XDA Labs

Thank you...
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.

Devil911 said:
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Click to expand...
Click to collapse
The stock rooted is by timmytim ?
I forgot about deodexed, actually.
Glad you fixed boot, shame your tablet broke ?
Sent from my Amazon Fire using XDA Labs

Stuck On bootanimation

No matter what custom firmware i flash it always is stuck on the boot animation, Ive left it booting for 5 hours today and it never reached the setup screen, just constant booting, I erase EVERYTHING everytime I go to twrp, except for my internal and external storage. Aswell as If i flash/restore my stock rooted and unrooted firmware, it does boot, but NO wifi or data works, even with the removal and reinsertion of the simcard. Please help. If i didnt explain it well enough i can reply and add more detail.

DeliriousHD said:
No matter what custom firmware i flash it always is stuck on the boot animation, Ive left it booting for 5 hours today and it never reached the setup screen, just constant booting, I erase EVERYTHING everytime I go to twrp, except for my internal and external storage. Aswell as If i flash/restore my stock rooted and unrooted firmware, it does boot, but NO wifi or data works, even with the removal and reinsertion of the simcard. Please help. If i didnt explain it well enough i can reply and add more detail.
Click to expand...
Click to collapse
You may have to follow this https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110 to get back to stock. There's a section about returning to stock without relocking the bootloader.

ccic2491 said:
You may have to follow this https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110 to get back to stock. There's a section about returning to stock without relocking the bootloader.
Click to expand...
Click to collapse
Ill try that. Ill report back if it works or fails.

ccic2491 said:
You may have to follow this https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110 to get back to stock. There's a section about returning to stock without relocking the bootloader.
Click to expand...
Click to collapse
It did not work, Keeps saying "Could not find 'meta-inf/com/google/android/update-binary' in zip file.

DeliriousHD said:
It did not work, Keeps saying "Could not find 'meta-inf/com/google/android/update-binary' in zip file.
Click to expand...
Click to collapse
One thing to try is formatting the internal storage to make sure you have a clean start. TWRP wipes /data without wiping userdata by default; to completely wipe the internal storage you have to go into the format data wipe where you must type "yes" to confirm instead of a slider. Sometimes leftover files can cause permissions problems and roms fail to boot. It is more common on other phones than this one, but I've seen some people report your problem before here too.
If you do this, obviously make sure you back up all the files you care about on internal storage to a microSD or off device. Also make sure you have rom/gapps to flash and a working TWRP backup stored on a microSD, or you've verified you can USB copy with MTP or adb push files from a computer to your phone before formatting. Don't find out after wiping and formatting that your computer is missing something it needs to copy files to your phone properly when your phone is booted into TWRP, test it first if you're going this route. Otherwise you could be stuck with a blank phone and nothing to flash on it.
I do this every once in a while just to keep internal storage from getting too cluttered from chronic flashing; just be careful about how you go about it.

Okay, I can try that.

jason2678 said:
One thing to try is formatting the internal storage to make sure you have a clean start. TWRP wipes /data without wiping userdata by default; to completely wipe the internal storage you have to go into the format data wipe where you must type "yes" to confirm instead of a slider. Sometimes leftover files can cause permissions problems and roms fail to boot. It is more common on other phones than this one, but I've seen some people report your problem before here too.
If you do this, obviously make sure you back up all the files you care about on internal storage to a microSD or off device. Also make sure you have rom/gapps to flash and a working TWRP backup stored on a microSD, or you've verified you can USB copy with MTP or adb push files from a computer to your phone before formatting. Don't find out after wiping and formatting that your computer is missing something it needs to copy files to your phone properly when your phone is booted into TWRP, test it first if you're going this route. Otherwise you could be stuck with a blank phone and nothing to flash on it.
I do this every once in a while just to keep internal storage from getting too cluttered from chronic flashing; just be careful about how you go about it.
Click to expand...
Click to collapse
I did this and its still stuck on boot. Im trying to flash AICP

DeliriousHD said:
I did this and its still stuck on boot. Im trying to flash AICP
Click to expand...
Click to collapse
It was worth a try. What bootloader and twrp version are you using?

jason2678 said:
It was worth a try. What bootloader and twrp version are you using?
Click to expand...
Click to collapse
regular bootloader for the xt1575 I havent chnged it, and twrp 3.0.2-0

DeliriousHD said:
regular bootloader for the xt1575 I havent chnged it, and twrp 3.0.2-0
Click to expand...
Click to collapse
TWRP 3.1 is out. I doubt that's your problem since you're flashing successfully and failing to boot, but updating recovery is something else to check off the list.
Are you on the L or M bootloader? It changed. Just looking for anything that might be causing the trouble.
Code:
getprop ro.bootloader
returns 0xA04C for me, and aicp is working good.

jason2678 said:
TWRP 3.1 is out. I doubt that's your problem since you're flashing successfully and failing to boot, but updating recovery is something else to check off the list.
Are you on the L or M bootloader? It changed. Just looking for anything that might be causing the trouble.
Code:
getprop to.bootloader
returns 0xA04C for me, and aicp is working good.
Click to expand...
Click to collapse
I think im on L but do i just put that in cmd when in bootloader? I also just updated twrp to 3.1 just now.
EDIT: I actually cant even do that in cmd.

DeliriousHD said:
I think im on L but do i just put that in cmd when in bootloader? I also just updated twrp to 3.1 just now.
Click to expand...
Click to collapse
Fastboot says what bootloader version you're on close to the little reclining robot, but I think it displays it a bit differently. A0.4C trailed by a date if I recall correctly.
You could enter that command in TWRP's built-in terminal. I think the terminal is under the Advanced menu. That should get you the same output.

jason2678 said:
Fastboot says what bootloader version you're on close to the little reclining robot, but I think it displays it a bit differently. A0.4C trailed by a date if I recall correctly.
You could enter that command in TWRP's built-in terminal. I think the terminal is under the Advanced menu. That should get you the same output.
Click to expand...
Click to collapse
I just tried putting that into terminal and it does nothing.

jason2678 said:
Fastboot says what bootloader version you're on close to the little reclining robot, but I think it displays it a bit differently. A0.4C trailed by a date if I recall correctly.
You could enter that command in TWRP's built-in terminal. I think the terminal is under the Advanced menu. That should get you the same output.
Click to expand...
Click to collapse
also BL: A0.1C (SHA-E29F91E, 2015-7-28 16;16;36)

DeliriousHD said:
I just tried putting that into terminal and it does nothing.
Click to expand...
Click to collapse
Well that's odd

jason2678 said:
Well that's odd
Click to expand...
Click to collapse
In your code you put to not ro XD

jason2678 said:
Well that's odd
Click to expand...
Click to collapse
Mine is 0xa01C

DeliriousHD said:
also BL: A0.1C (SHA-E29F91E, 2015-7-28 16;16;36)
Click to expand...
Click to collapse
2015-7-28 date is definitely from lollipop. I'd suggest heading over to the firmware thread and grabbing the newest marshmallow full firmware update (I think the sept patch is the newest out there), fastboot flash all of that, then try again.

jason2678 said:
2015-7-28 date is definitely from lollipop. I'd suggest heading over to the firmware thread and grabbing the newest marshmallow full firmware update (I think the sept patch is the newest out there), fastboot flash all of that, then try again.
Click to expand...
Click to collapse
Which thread? I can go looking but ive been to so many its confusing how to use the files.

jason2678 said:
2015-7-28 date is definitely from lollipop. I'd suggest heading over to the firmware thread and grabbing the newest marshmallow full firmware update (I think the sept patch is the newest out there), fastboot flash all of that, then try again.
Click to expand...
Click to collapse
This thread https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833 Shows a couple firmwares. but idk if i should get MPH24.49-18 , MPH24.49-18-3 or MPH24.49-18-4

Phone won't boot?

Hello, I was trying to root my phone last night, I unlocked the boot loader that worked perfectly, easy. Nothing else went well, I was fighting with it TWRP for hours and then Magisk wouldn't install. I gave up on that and tried SuperSu... now the phone just stays on the loading screen instead of booting, It won't boot into recovery either just fastboot. Can it be fixed?

Your phone is soft bricked and can only boot to bootloader, correct?
The only solution is flashing the stock ROM of the device. You can get your device (Tissot) stock ROM from here.

I just got it to boot into TWRP, after it cycled a few times.

Well that may make it easier, you can try wiping dalvik cache then wiping data and see if that works. Needless to say wiping data is going to delete all your personal data, but since you're in TWRP recovery you can back it up.

Wiping it didn't work, I'm trying to use MiFlash I have downloaded "Tissot_9.0_V10.0.10.0.PDHMIXM_Fastboot" my phone is in fastboot. MiFlash detects it but when I try to flash I just get "can not found file flash_all_lock.bat"
How do you tell is MiFlash has successfully installed drivers, it gives me a window in Chinese?

If it's not working - I never thought it would anyway - then your only option is to flash stock ROM.
You can try using fastboot commands through cmd window, if it returns <waiting for device> or something similar then the driver isn't installed properly. Alternatively you can install the driver from here.

Thanks, it detects my phone. How would you recommend flashing the stock ROM? Do I need to use the same version the phone was running before?

galaxymini1 said:
Thanks, it detects my phone. How would you recommend flashing the stock ROM? Do I need to use the same version the phone was running before?
Click to expand...
Click to collapse
You can use any version as long as it is meant for your device. Flashing the latest version might be best option.
Happy to help.

I tried flashing it with TWRP but just got "no digest file found" I'll try again tomorrow.
This must be the most annoying thing I've done with electronics in years, nothing wants to work.

galaxymini1 said:
I tried flashing it with TWRP but just got "no digest file found" I'll try again tomorrow.
This must be the most annoying thing I've done with electronics in years, nothing wants to work.
Click to expand...
Click to collapse
Lemme guess, you have TWRP v3.2.2-0? Try flashing the latest version from here.

XDHx86 said:
Lemme guess, you have TWRP v3.2.2-0? Try flashing the latest version from here.
Click to expand...
Click to collapse
v3.2.1 anyway it's gone now, I got it booting with the guide on https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
probably the best written one I've found.
Now to try and root it again...

galaxymini1 said:
v3.2.1 anyway it's gone now, I got it booting with the guide on https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
probably the best written one I've found.
Now to try and root it again...
Click to expand...
Click to collapse
You can find that in an XDA revised article here.

I got TWRP and Magisk installed no problem. I don't know if I was just tired or it was the crap guides but nothing wanted to cooperate on my first attempt.
Thanks for all the help.