Database Develop

[Q] Ultra-Mega Brick

I've had my Note for some time, and now i think i super bricked it, here's the thing:
It was on the charger and i was using TeamViewer as a remote for my pc, it was heating quite alot, but it was holding up,
so i turned off the app, wifi, turned on power saving, and left it on charger through the night, when i woke up i tried to unlock the screen but nothing happened, so i tried to turn it on, it showed the Samsung Logo + the flash sign thing, and then the Paranoid Android boot anim, and then it just turned off.
I then thought it was something with the rom wrong so i got in the DL mode, or what's it called, it worked, but i dont know how to operate odin so i left that and went into the recovery and tried to reflash the rom from my sd card, but mid flashing it just froze, and after a few seconds it turned off, i tried booting into the os, nothing, then tried recovery, it was working, than tried to flash again, but same thing, freeze, turn off after few seconds, and after that, nothing, no samsung logo, no dl mode, no recovery, nothing, i see a small horizontal line when i try to turn it on but it just blinks for a fraction of a second, so i was thinking the cpu or gpu, or whatever, was cooked, then i plugged the charger in and the battery screen turned on, i responded to locking the screen and unlocking.
I got it from the repair shop a few hours ago and they say that they MAYBE can repair it, so i'm coming here seeking help,
I'm thinking that the NAND or eMMC or whatever memory that has the os and kernel on it is corrupted, so, is there a way to flash it with some third-party hardware, like you do on consoles for pirating purposes...
If that is possible please tell me what hardware do i need to directly flash a kernal/os/rom onto its main memory.
Thank you in advance!

In your case I would:
Find odin.
Find Samsung fastboot/recovery drivers
Find a stock samsung rom in Odin format.
Find philz kernel in recovery flash format.
With Odin, flash stock rom. Find tutorials for it, it's easy. Install the samsung drivers if need be.
If the device boots, let it boot, copy philz kernel to sdcard root.
reboot to recovery (power up + home + power combo)
flash philz kernel
reboot
let it boot
reboot to recovery
flash Custom rom

I would go with a charged battery first. For some reason I feel there is no juice left. You also could have corrupted the system and data partitions by flashing. So if you get to recovery after inserting a charged battery, then boot into recovery mode, format system, data and cache. Then install a new rom.

But for odin i need to go to DL mode first, right?
Becouse i cant access even that.

What happens when you try ?
Also, nokiamodeln91 is correct. Does the battery image show up when charging powered off?

Okay, i can get into odin.
Now what?

Flash a stock(ish) rom. Read about what you're doing.

So, i managed to get a stock rom on it, but i still cant boot into anything, except odin.
When i connect it to a pc i see the battery charging a few seconds then it boots into recovery on its own, i wiped data/factory reset, and wiped cache, but still cant get to os, what next?

Rochendil said:
So, i managed to get a stock rom on it, but i still cant boot into anything, except odin.
When i connect it to a pc i see the battery charging a few seconds then it boots into recovery on its own, i wiped data/factory reset, and wiped cache, but still cant get to os, what next?
Click to expand...
Click to collapse
Paste Odin logs and which rom did you flash?

Also, install ADB drivers. See if you have ADB debug enabled (shouldn't have)
There's a minimalistic adb packaged that could be usefull, try to run adb logcat

nokiamodeln91 said:
Paste Odin logs and which rom did you flash?
Click to expand...
Click to collapse
Its some indian GB rom, the only rom i could get, all the others are either on slow premium hosting sites or hot-file.
The flashing went well, i think, everything passed and was green, im not sure how to get the logs after i closed odin.
daedric said:
Also, install ADB drivers. See if you have ADB debug enabled (shouldn't have)
There's a minimalistic adb packaged that could be usefull, try to run adb logcat
Click to expand...
Click to collapse
I've installed adb drivers and the program, but where should the phone be when i try to adb to it, because when its in odin the adb device command does not detect it, and i cant get into the os to check usb debug?

Try ADB when it's failing to boot.

How? What to type, what keys on the phone to hold?
What to do?

leave it charging for a hour or so, then try to turn it on normaly.

So after i flashed a stock rom i got into some weird boot-loop, charging logo-->recovery logo-->charging-->recovery... and so on, until it somehow booted into recovery, sometimes, without any input whatsoever, and now it got out of that loop and is just on charging screen without blinking.
oh and i tried a brand new battery, which was empty (0.7V) vs my original samsung battery which i charged with external charger outside the phone when i thought it wouldn't charge it.
so to sum it up, first i thought that my battery was drained and charged it externally, but it didn't help, i believe the battery is fine, and charged, i tried it with some load it voltage dropped from 3.9V to 3.3V with ~50ohm resistor, i think that is fine, although i'm not sure.
The brand new battery that i bought was at 0.7V before charging, and when i inserted it into the phone and connected the charger no charging logo appeared, the phone was heating slightly and after 12-14 hours of charging, with the phone off of course (because there was no other state for it then), it still showed 0.7V.
oh and before, on the original battery that is currently running, the charging logo was blinking, i think it was trying to get into recovery, but there was no recovery.
PS: by the time i wrote this it got into the weird charge>recovery>charge>rec... boot loop again...
this post is a mess, as i'm writing a bunch of things that come up that may be important...
please ask if you don't understand what i just wrote up here.
EDIT: it got out of the loop again, dunno how long that will last...

Not a mess.
Ok, let's get facts. Is recovery a image with a "Android" laying down ?
When you flash something via Odin, on the first boot it MUST go into recovery and finish flashing something (CSC i believe)
That's what it must be trying.
So.. debug.
Does it do that loop thing UNPLUGGED?

when its unplugged nothing works, no odin, no recovery, nothing.
it booted into recovery, it showed something like CSC pass or something everything was good, the phone was completly working, just that it was recovery, and not the os that i want to get.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This logo, without the text below.

That's the recovery logo, probably the stock recovery (3e).
Can you force it to boot to recovery ? (and stay there ?)

i dont think so. maybe flashing the rom again and it getting there on its own, like i got there in the first place. so, what to do when i get into recovery?

Nothing... wait 4/5 seconds and it should reboot and this time boot properly.

[Q] Help needed: tried to install Cyanogen 11, can't boot.

Hello all! So, I tried to install CM11, the one on this post.
Went into CWM, did Wipe data factory reset and formatted /system. when I tried installing the rom, it said operation aborted and it could not install it. No biggie, the post says to install cm10.2 before doing so.
So i Powered the phone off to copy the file over to the SD. To my surprise, now I can't get into CWM, Philz, TWRP, fastboot or flashmode. Whenever I press the back pin to power the phone off, it turns back on automatically before I have time to press the key and connect the USB cable. Furthermore, when I manage to do it quick enouhg, the green led lights up, but it fades away after 10ish seconds only to display the sony logo again, and a "can't recognize USB device" popup comes up in my PC. I've used flashtool with this same pc in the past, so I don't know what that is about. Also, whenever I try installng flashtool drivers again, just in case 2 things happen:
there is no xperia SP device listed and whatever i select it fails to install.
What can I do now? I had 4.3 with the eXistenZ Ultra ROM before all of this.
Damm, this is the first time this happens to me, I've been swapping roms for ever, and this is not even the first phone i do this in, had a galaxy s2 and a wildfire S before. I feel like such a noob
UPDATE!:
So I finally managed to fix it. I posted this after about 8-9 hours of trying to get into fastboot on the 3 different pcs in my household, all had the drivers at some point and i've worked with them and fastboot and this same phone previously, so I figured they'd still work. They didn't, I couldnot even get SUS to work. So i went to a 4th PC, installed SUS and the needed drivers and it only took like 40 minutes worth of tries. I'm in the software download part of the SUS, i'll keep this updated!
UPDATE2!:
So, it finished downloading but it suddenly disconnected, tried again for about 10 minutes and then got it going again. Downloaded the second time and installed it successfully. Leaving this up for future reference!
Bottomline: if you can't get into flashmode, try on as many PCs as you have available for at least 30 minutes each.

Don't use flash tools just install CM11 with CWM or something, use doomlord kernel to get CWM and install CM11 zip that's it.
Sorry locked boot loader didn't read it correctly don't use my advice .

Th3Duck said:
Don't use flash tools just install CM11 with CWM or something, use doomlord kernel to get CWM and install CM11 zip that's it.
Sorry locked boot loader didn't read it correctly don't use my advice .
Click to expand...
Click to collapse
No problem, it kinda sorted itself out by brute force connections :> Dammed sony, locking the bootloaders for real. I even got the sim unlock code from my phone company and it's still not bootloader unlockable at the phone settings, even though i can now get any sim i want in it -.-

I believe I have bricked my HTC One Mini 2?

Was at work using both my company phone (iPhone 5) and my personal phone (HTC One Mini 2) just fine. Put my personal phone away to get on with actual work and came home at around 5:30'ish. Played a bit ("a bit") until about 9/10pm (I think?) whereby I looked for my phone to just check things like WhatsApp and Snapchat and the phone wasn't turning on when I was holding the power button. I just thought to myself "huh, the battery must be dead" and put it to charge and the charging LED (as well as the charging screen with the "do not distribute outside htc blabla" dev screen) displayed so I just assume it's charging as per usual. Fast forward to about 1am, I have finished using my computer and decide to hop into bed. I go to turn on my phone by first powering down with power, vol up and vol down (as usual) and then try to boot the phone up. It boots as normal up until the O/S loading screen with a pac-man boot animation (I have PAC ROM installed) whereby it will freeze on the "game over" image of the boot animation and then proceed to go to a black screen. I thought to myself "hm, must be a mistake or something" and try it again to no avail. So I then go into recovery to do a fresh install and I try to wipe the phone and I do a factory reset in twrp, but upon trying to format data, the progress bar doesn't move (and so I left it overnight as I couldn't be bothered to wait). Upon leaving it overnight (1am to 7am) to format the data, I wake up to see that the progress bar hadn't moved at all from 0%. I then just thought "maybe the phone has actually formatted it but hasn't updated the image on screen so me being the dumbo I am, decided to force shut down the phone (with power, volup and voldown) and upon trying to boot the phone up again, it displays the HTC logo with the red writing, tries to boot into the O/S, fails, and then tries to boot into recovery and gets stuck in a boot loop (it will show the twrp logo and then a black screen, twrp logo and then black screen etc.). I have tried to flash twrp again (without first removing the twrp currently on it) but I was wondering what I could do in this situation. I am able to access the bootmenu (for hboot and fastboot) but nothing else.
TL;DR: I think I bricked my HTC One Mini 2. Came home, charged phone and phone got stuck at boot animation. Wiped phone in recovery, it got stuck on formatting data and now It can't boot into the O/S since it's wiped and it can't boot into Recovery for whatever reason.

DistincTHD said:
blah blah
Click to expand...
Click to collapse
This is not Facebook, go straight to the point.
Did you install a different kernel?

kativiti said:
This is not Facebook, go straight to the point.
Did you install a different kernel?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.

DistincTHD said:
[IMG="HTC Dev Message"]
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
Click to expand...
Click to collapse
Oops, Just realised you meant the whole post, not just the blah blah bit within the post. But yeah what I did, I explained above and in the original post. I basically just told a story to give a better idea of what generally happened before the phone just pooped out on me.

DistincTHD said:
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
Click to expand...
Click to collapse
Something its corrupted so try to reinstall everything using the files from this post plus your choosen ROM.
When rebooting phone unplug USB cable.

kativiti said:
Something its corrupted so try to reinstall everything using the files from this post plus your choosen ROM.
When rebooting phone unplug USB cable.
Click to expand...
Click to collapse
I can't access twrp recovery but I do have fastboot enabled and working and I can access the boot menu so how would I go about wiping everything before re-flashing the recovery and then re-installing the o/s and everything else?

Just tried to first erase everything before installing and it's locking me out of the phone? It's telling me that an administrator console is unable to erase the system or its data so I'm quite stumped at the moment

DistincTHD said:
Just tried to first erase everything before installing and it's locking me out of the phone? It's telling me that an administrator console is unable to erase the system or its data so I'm quite stumped at the moment
Click to expand...
Click to collapse
you don't need to do all that.
try to flash twrp. (if OK use it to wipe everything)
If NOT ok flash stock recovery and unlock bootloader( yes again, this will wipe your phone and fix permissions)
Then you can do all you want.
Good luck.
let me know...

kativiti said:
you don't need to do all that.
try to flash twrp. (if OK use it to wipe everything)
If NOT ok flash stock recovery and unlock bootloader( yes again, this will wipe your phone and fix permissions)
Then you can do all you want.
Good luck.
let me know...
Click to expand...
Click to collapse
Right, so before I read that message, I flashed stock recovery and tried to reformat data and now It won't let be get into the boot menu and the HTC dev writing is gone (so I think it's locked again). On top of this, it just keeps booting into the reformatting data screen and just ends up hanging so I think I will let the battery drain or something (no idea how long it would take, probably days) and then try again from there. Pretty sure it is bricked now though lol welp. Is there any way to cancel a format?

Sony Xperia SP stuck on Sony logo screen, can't open recovery, flashtool also fails

Having gotten a spare Xperia SP, I decided to venture into the realm of flashing custom ROMs. This was the first time I did anything of this sort with an Android device. So, here is what I did to it today:
At first, I successfully rooted, installed recovery and flashed CM12. After fiddling with it for about an hour and not finding anything super exciting, I decided to try out other ROMs. I did a facotry reset, wiped the data and cache, and was about to flash CM11 (I forgot that it required an unlocked bootloader, which I don't have, and the recovery console told me so). Maybe at this point I should have just reflashed CM12, but I chose (not even sure why at this point) to exit recovery instead. After this, the phone keeps getting stuck on the Sony logo (although on the second attempt to turn it on, it did display a screen showing that wrench icon, indicating some sort of configuration activity going on, but never moved past that either). I tried flashing two different stock ftf roms with flashtool, both fail with this error: Processing of system.sin finished with errors. One of them will cause the phone to shut off after about a minute on the logo instead of remaining stuck on it indefinitely.
Maybe I should mention that this phone did not exactly work flawlessly for some time, even before I started experimenting with it. Here are the main things that I can remember it doing:
-Lags on even the basic functions, apps often crashing, despite doing a very recent hard reset.
-Battery drains very fast sometimes (like going from 55% to 0 in about 2 hours with almost no usage).
-A few months ago, it would periodically freeze and reboot itself, but that problem seemed to disappear with time.
Did I do something stupid to that phone, or are there internal/hardware problems that have manifested themselves in this way? I won't be horribly upset if I killed it (after all, knowing that something of this sort may happen was exactly the reason why I was not doing all this on my main phone), but I certainly would like to get it back up and running.

Download Flashtool v0.9.18.6 from official site.
Option 1: Flash stock.
or,
Option 2: Flash tangerine-7.1.elf via 'fastboot mode' to directly get TWRP, then flash any ROM you want.
https://dl.cubeserver.eu/TechnoSparks/tangerine-stuffs/tangerine-7.1.elf

nandan21 said:
Download Flashtool v0.9.18.6 from official site.
Option 1: Flash stock.
or,
Option 2: Flash tangerine-7.1.elf via 'fastboot mode' to directly get TWRP, then flash any ROM you want.
]
Click to expand...
Click to collapse
Thank you for your reply. I have a few questions:
I downloaded the flashtool version that you mentioned (from the official site), but avast detected malware in it. Should version 9.19.8, the one I tried yesterday, work fine?
What is exactly considered "stock rom"? Is it exclusively the version your phone came with, or is it firmware of any version/carrier branding, as longs as it is made for your phone model by the manufacuter?
It looks like my phone actually won't stay in flash mode. I select fastboot mode in flashtool, a window pops up asking me to plug in the phone. I press the volume down button and plug it in, the LED glows bright green, but nothing happens in flashtool. After a few seconds, the LED goes red and the Sony logo appears on the phones screen (as if it was going to turn on), and my computer makes a sound as if the phone was ejected. The phone shuts off a minute later, goes into flash mode again, and the cycle repeats.

UPDATE
Nevermind everything I wrote before, I was able to successfully re-flash stock. Turns out I did in fact have some crappy version of flashtool that didn't work, and I found anolder version without malware.
Strangely, the infected flashtool version was the one I dowloaded from the official site... Something is fishy here.
Anyways, thanks a bunch for your help!

MrDroid15 said:
Thank you for your reply. I have a few questions:
I downloaded the flashtool version that you mentioned (from the official site), but avast detected malware in it. Should version 9.19.8, the one I tried yesterday, work fine?
What is exactly considered "stock rom"? Is it exclusively the version your phone came with, or is it firmware of any version/carrier branding, as longs as it is made for your phone model by the manufacuter?
It looks like my phone actually won't stay in flash mode. I select fastboot mode in flashtool, a window pops up asking me to plug in the phone. I press the volume down button and plug it in, the LED glows bright green, but nothing happens in flashtool. After a few seconds, the LED goes red and the Sony logo appears on the phones screen (as if it was going to turn on), and my computer makes a sound as if the phone was ejected. The phone shuts off a minute later, goes into flash mode again, and the cycle repeats.
Click to expand...
Click to collapse
Use flashtool 0.9.19.8 because that is what everyone is recommending now, Stock rom defines as what it originally comes from your phone which is manufactured by sony. To get into fastboot mode turn off your phone by taking off the cover off your xperia sp and use a pin or pen to press into a small dot and you will get 3 vibrations.
This guide is not written by me, so give credit to chris10286
Step 1. Download a kernel with twrp embedded im sure I used dooms kernel as far as I remember. There are many others just do a simple google of xperia sp kernel with recovery.
Step 2 . take phone case off the back hold button in on lower bottom for 10 seconds you will get 3 vibrations . good leave it at that.
Step 4 . open flashtool let it load completely. Now plug USB into your phone also have it into your PC ! Whilst plugging in hold down volume button to enter flashmode your phone should be green . hold up for fast boot mode which is blue either too let's you flash a kernel but fast boot mode requires "elf" kernel.
Step 5. Locate kernel install and then boot phone up whilst press the volume up button as its booting recovery mode will be accessed now flash rom of your choice or use Sony PC suite to go back to stock. Make sure you have stock kernel and bootloader locked or else it won't let you..
Use this thread to help you since i had the similar problem which involved my phone: http://forum.xda-developers.com/showthread.php?p=63660062#post63660062
If none of my methods work please ask zenith to help you or ask anyone in the xperia sp forum to help you since im not a developer but ran into a similar problem to yours.
I hope this helps you out in someway as it did me good luck.
Thanks Nandan

Thank you, I very much appreciate that you took the time to write this long post to help me out. As I mentioned in an earlier post, I found a solution to my problem - by using flashtool 9.18.6 (the one that wasn't working was actually newer).

Nexus 6 not turning on

Hello i bought a replacement screen for my phone about a month ago because everything was still working except the screen was broken from cracks. As i was about to replace the screen i noticed my phone is now not turning on at all even on charge. No red light, nothing. Is it possible the battery just needs to be replaced or is the phone completely dead?

Try charging it for a few hours on a low power charger like a computer USB port.
When the battery gets very depleted, it can have trouble taking a charge from a faster charger.

ktmom said:
Try charging it for a few hours on a low power charger like a computer USB port.
When the battery gets very depleted, it can have trouble taking a charge from a faster charger.
Click to expand...
Click to collapse
Hi, i tried to charge it using the PC but it didn't change anything. Would it be worth it getting a new battery to test if it still works?

I guess that's a decision you have to make. Is the expenses of the battery worth the risk that something else is wrong. It's possible the power button assembly has a problem. It's possible the USB port is worn, damaged or dirty.

Paperweight now? Having a different issue but potentially fatal??
My nexus 6 has been my faithful companion for many years, and now, though it is not my main phone, is used as my bedside companion for many uses. I boot it up one day and it gives some sort of "file encryption error" and then would not boot. I downloaded a fresh rom and adp to try to wipe it and just get it back to any working state, but nothing seems to work. What am I doing wrong?? (see photos attached)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

archos5005 said:
My nexus 6 has been my faithful companion for many years, and now, though it is not my main phone, is used as my bedside companion for many uses. I boot it up one day and it gives some sort of "file encryption error" and then would not boot. I downloaded a fresh rom and adp to try to wipe it and just get it back to any working state, but nothing seems to work. What am I doing wrong?? (see photos attached)
Click to expand...
Click to collapse
Let's start with some basics. It looks like the phone is stock (not bootloader unlocked).
What version was on the device before the problem?
Can you boot to recovery? (With the phone powered off, press and hold Volume Down, then press and hold Power)
Try sideloading an OTA the same as your current version. They are available on the Full OTA Images for Nexus and Pixel Devices page. The instructions there are solid.
If your not sure what was on the device, use the newest release.
Based on your photo, the device is not unlocked. You won't be able to Fastboot flash anything if you can't unlock it which requires the OEM unlocking to be enabled in developers options. Since you can't boot, you are stuck there.
It's quite possible the eemc has failed and the device is damaged.
BTW; your images are not showing up because the use of the IMG tag is wrong. There should not be anything inside the brackets with the tag (e.g. ="error"). The link does go between the opening and closing tags as you have it.
In the future, it also is a good idea to start your own thread, instead of burying a question inside a unrelated thread.

ktmom said:
What version was on the device before the problem?
pretty sure it is the latest (for that model) Android 7.1.1
Can you boot to recovery? (With the phone powered off, press and hold Volume Down, then press and hold Power)
I can get to the screen that shows the green android man lying with his compartment open. Is that recovery? It seems that everytime I try an option, it does not "do" anything. E.g., factory reset just won't let me do it. It just doesn't work [is this a symptom of emmc memory just being damaged? I know on PC's, a total reformat can isolate bad sectors...]
Try sideloading an OTA the same as your current version. They are available on the Full OTA Images for Nexus and Pixel Devices[/URL] page. The instructions there are solid.
I think I've followed that, (see the second picture) but again those commands don't seem to "do" what the commands usually should do. Like I need a tougher solution--willing to totally wipe everything and reformat and start anew, like a low level format.
Based on your photo, the device is not unlocked. You won't be able to Fastboot flash anything if you can't unlock it which requires the OEM unlocking to be enabled in developers options. Since you can't boot, you are stuck there.
It's quite possible the eemc has failed and the device is damaged.
I think I tried unlocking it, but same thing it didn't "work" either that, or I'm just doing it totally wrong [is it not the command "fastboot flashing unlock"??].
Click to expand...
Click to collapse
Thanks in advance. I just don't want to accept that it was working great one day and then turning it on the next day the flash memory is just TOTALLY bad, you know?

When a you boot to recovery, then get the "no command screen" press and hold Power then press and release Volume Up. If you can get to recovery, do a factory reset.
Unlocking the bootloader won't work unless you have already enabled OEM unlock in the developer options when booted to system. I said this earlier.
ADB won't work unless the kernel is booted. ADB only works when booted to recovery or fully booted to system.
Unless the bootloader is unlocked, Fastboot doesn't get you anything.
If you get to recovery and a factory reset doesn't solve your problems, do an OTA sideload using the link I gave you before.
Please Do Not bury your comments within the wipe of someone else's post. It makes it impossible to follow the conversation. Just respond below the quoted post.