Database Develop

My last question

So im installing 4.1.9999
Im following this steps, but
1- Perform a Backup......nandroid, etc
2- Download: http://developer.htc.com/adp.html#s3 Android 1.6 Recovery Image. This isn't the type of recovery image we know. It's HTCs version of an update.zip
3- Download my ROM. Posted Below
4- Mount your phone and place BOTH 1.6 Image and my ROM on your SD Card.
5- Reboot into recovery mode *Home+Power*
6- WIPE!!!! This will allow google apps to function, correctly.
7- Apply sdcard:choose zip *PICK dream_devphone_userdebug-ota-14721.zip* from the list
ALLOW IT TO INSTALL FIRST.....you will see the "unbox" image.........then it will automatically reboot HOLD HOME button while it reboots.
8- Apply sdcard:choose zip *Pick cm-4.1.99-signed.zip* from the list.
9- Reboot!
-When I applied "dream_devphone_userdebug-ota-14721.zip" i kept holding home.. during the whole installation.. and my phone never rebooted.
-so should I reboot it and press home to install the other .zip , or should I just install it now?

Your not suppose to hold home the entire time thru out the installation, just when it reboots. I would just flash that again and do it over.

ugh really?
you didnt read. it didnt say hold it during installation. it said hold it during reboot...which you dont really hafta do
flash htc. when it puts you back to your recovery, flash CM. when it puts you back to recovery again, reboot. when you get back to recovery again (not having to hold home at all) reboot again and let it load.

i never even reboot between htc and cm flashes. i am hardcore.

Hey guys, I got an error when applying "dream_devphone_userdebug-ota-14721.zip" again
E: Multiple firmware images
E: Can't store radio image
Installation Aborted
Click to expand...
Click to collapse
How can I fix this?

david1171 said:
i never even reboot between htc and cm flashes. i am hardcore.
Click to expand...
Click to collapse
Yes you are.
{
"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"
}

Hey guys, I got an error when applying "dream_devphone_userdebug-ota-14721.zip" again
E: Multiple firmware images
E: Can't store radio image
Installation Aborted
Click to expand...
Click to collapse

What recovery do you have?

And I'm talking bout your regular recovery not the htc 1.6 one

supremeteam256 said:
And I'm talking bout your regular recovery not the htc 1.6 one
Click to expand...
Click to collapse
It says "android system recovery <2>"
..okay so i decided to do this:
I rebooted the phone and re-applied the (dream_devphone_userdebug-ota-14721.zip)
so I did this.. and I was SUPER READY for when the little package installer came up to hit HOME button, but instead everything installed and the phone never rebooted lol
so im back on home screen
should I apply 4.1.9999.zip now?

supremeteam256 said:
And I'm talking bout your regular recovery not the htc 1.6 one
Click to expand...
Click to collapse
..........
ROFL

xologist said:
It says "android system recovery <2>"
..okay so i decided to do this:
I rebooted the phone and re-applied the (dream_devphone_userdebug-ota-14721.zip)
so I did this.. and I was SUPER READY for when the little package installer came up to hit HOME button, but instead everything installed and the phone never rebooted lol
so im back on home screen
should I apply 4.1.9999.zip now?
Click to expand...
Click to collapse
I'm confused, so the phone never rebooted but the phone is on you main screen of your phone.

i mean i still have not gone to home screen.. that would be dumb
everything i said above i meant on the recovery.
ill re-phrease it
okay so i decided to do this:
I rebooted the phone to recovery and re-applied the (dream_devphone_userdebug-ota-14721.zip)
so I did that.. and I was SUPER READY for when the little package installer came up to hit HOME button, but instead the "dream_devphone_userdebug-ota-14721.zip" installed and the phone never rebooted.. keeping me on the home screen of the recovery.
so im back on recovery screen
should I apply 4.1.9999.zip now?

yes, go ahead flash the rom and reboot

seriously....go download the 1 click 999 flash and then upgrade to 9999 afterwards. 2 totally separate flashes.

knowfear said:
seriously....go download the 1 click 999 flash and then upgrade to 9999 afterwards. 2 totally separate flashes.
Click to expand...
Click to collapse
i have never seen it so hard to wipe, flash, flash, reboot in my life.

xologist said:
i mean i still have not gone to home screen.. that would be dumb
Click to expand...
Click to collapse
Gahhhhhh....
You're my hero

i lost so many iq points reading this
i was gone for two days...wtf happened to xda

B-man007 said:
i lost so many iq points reading this
i was gone for two days...wtf happened to xda
Click to expand...
Click to collapse
Exactly thats what happens. Don't miss two days again otherwise this will keep happening.

[Q] my xperia x1 start in bootloader mode

hu every body my xperia x1 start in bootloader mode every times i start it i try to flash it and still the same probleme can any one help :crying::crying:

no :crying:

samisou said:
no :crying:
Click to expand...
Click to collapse
try to charging your batery with desktop charger first,, i think it cannot start flashing coz your batery is not enough/sufficient
sorry for ma bad english

You should try a sdcard based flash... just put a rom image named kovsimg.nbh in the root of the card and wait. if after the flash you phone still booting on spl mode, try opening you phone and clean the volume keys and camera button.... maybe there is a stucked button

connect the phone to a USB, run the command line fastboot reboot

I think what he means LK Bootloader (blue text).

romanck said:
I think what he means LK Bootloader (blue text).
Click to expand...
Click to collapse
Hello, I also have a problem on my X1, I wanted to run andorid on my phone, but everytime I run HaRET in WM or using LK and entering recovery, my phone keep on reboot automatically. One thing that I know is my camera button cannot respond when pressed. I assume that the button is stucked. How can I un-stuck the button? I already tried to clean it but still not working.

BrianXP7 said:
Most likely your camera button really is stuck but I think it might loop into recovery due to a certain "Reboot to Recovery" signal. Did you ever successfully ran Android or at least installed it properly?
Click to expand...
Click to collapse
NO, I have not, because all the android I wanted to run will make the phone reboot, both with HaRET.exe or with LK recovery.
After installing the LK recovery, if I didn't half push the camera button, the phone is only stuck in fastboot mode (but there is still no ROM inside my phone), when I halfpush my camera button, the phone reboot itself.
Do you ever have any experience with stuck camera button? Or the problem is just the same for instance in your normal phone, holding the camera button while entering the recovery will send the reboot signal to the phone?
Anyway, where is the "Reboot to Recovery" signal come form?
===UPDATED===
I already cleaned my camera button, so that it can operates normally, but still have the reboot problem when trying to enter the recovery. The strange things is when I view my device information, it only shows that my ram is 128MB instead of 256MB. Strange, any idea?

BrianXP7 said:
This is very strange. Try reflashing ClockworkMod Recovery.
Click to expand...
Click to collapse
I don't know then, I already tried to reflash the CWM, reflashing to stock WM, stock radio and stock SPL, but it still in 128MB memory status. The handset just cannot boot normally without pushing the reset button 1 times.
I attached the picture in case you are courious:
{
"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"
}

solved
BrianXP7 said:
Sorry. I can think of anything that may have caused this. I'll get back to you when I found something.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
No problem my friend, after doing this things, my problem is solved:
1. reflash the stock rom
2. reflash stock spl
3. pull out the baterry, put the phone without battery the whole night.
After reinsert the battery, the phone can boot normally without needing to push the reset button, and the RAM shows 256MB. Everything boots normally, not stuck in any bootloader stuff anymore.

Stuck on bootloop - unrooted, S-ON, Unlocked, Tampered

Hi all... My device just went on bootloop. Last evening battery was drowned so I reached home and plugged it to charger and its on bootloop since then.. now fastboot screen is coming automatically on power on.
Screen is showing this:
{
"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"
}
Don't know what to do as this device is not rooted or unlocked.

sumit77seo said:
Hi all... My device just went on bootloop. Last evening battery was drowned so I reached home and plugged it to charger and its on bootloop since then.. now fastboot screen is coming automatically on power on.
Screen is showing this:
Don't know what to do as this device is not rooted or unlocked.
Click to expand...
Click to collapse
You can try
Code:
fastboot erase cache
then a factory reset
otherwise you'll have to flash the 7.21.707.21 RUU to reset your phone back to stock. The ruu will wipe everything from your phone.
File and instructions here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

alray said:
You can try
Code:
fastboot erase cache
then a factory reset
otherwise you'll have to flash the 7.21.707.21 RUU to reset your phone back to stock. The ruu will wipe everything from your phone.
File and instructions here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
Thanks I did all that... and I recovered successfully.. but after setting up... I just ran the older backup of my phone... and now its completely dead... No charging... no flashboot screen... nothing... completely dead.... But when plugged into system... After pressing power+vol down for 10 sec will make ding sound like its booting.... but nothing on phone... not even LED... Is my phone completely dead...

sumit77seo said:
Thanks I did all that... and I recovered successfully.. but after setting up... I just ran the older backup of my phone... and now its completely dead... No charging... no flashboot screen... nothing... completely dead.... But when plugged into system... After pressing power+vol down for 10 sec will make ding sound like its booting.... but nothing on phone... not even LED... Is my phone completely dead...
Click to expand...
Click to collapse
Sounds like your backup was corrupted or a mod inside the backup was no good for the device. Leave phone on the charger for a while and hopefully the juice will awaken it from it's sleep. Otherwise consider it bricked.
Sent from my C525c using Tapatalk

SHM said:
Sounds like your backup was corrupted or a mod inside the backup was no good for the device. Leave phone on the charger for a while and hopefully the juice will awaken it from it's sleep. Otherwise consider it bricked.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Ok I will plug into the wall charger for 2-3 hours. What do you mean by bricked. So can't we unbrick it?? As I have heard somewhere no device can be bricked fully. As my device is not in warranty, the HTC guys will charge me much more... Can't we do anything?

sumit77seo said:
Ok I will plug into the wall charger for 2-3 hours. What do you mean by bricked. So can't we unbrick it?? As I have heard somewhere no device can be bricked fully. As my device is not in warranty, the HTC guys will charge me much more... Can't we do anything?
Click to expand...
Click to collapse
There are two types of bricks. Soft and Hard. Soft brick typically means you have access to your device in some way to some degree that which would allow you to recover the device promptly. An example of a soft brick would be to corrupt your partitions and neither the recovery or system works. Even if by installing a custom recovery. But access to rebootRUU still makes it plausible to restore everything assuming one has access to that RUU (this example is HTC specific).
A hard brick would be a scenario where nothing is accessible. System, recovery, bootloader, etc. Meaning there is no feasible way to gain the needed access to restore your device in some fashion so that it will work again.
Both types of bricks exist and both types of bricks are easily possible. Although, a hard brick is very unlikely to be seen by most since most typically have some sort of knowledge as to what they are doing prior to doing it. An example for a Hard Brick would be to attempt to reverse engineer the bootloader, make an error that goes unnoticed, and apply the mod with this fatal error to the device thus resulting in the device failing to boot at all.
Sent from my C525c using Tapatalk

SHM said:
There are two types of bricks. Soft and Hard.
Click to expand...
Click to collapse
though i tend to agree with you, but there are more than two types... i can think of at least four (not sure atm if i can think of more),
from mild, soft, hard, or just not-bricked-but-not-bootable either bricks
but when it goes from "Last evening battery was drowned so I reached home and plugged it to charger and its on bootloop since then" ... i wasnt flashing my phone or anything else, it just happened, then 99% of the time it's a hardware problem, and wont be fixed without changing the motherboard.

nkk71 said:
though i tend to agree with you, but there are more than two types... i can think of at least four (not sure atm if i can think of more),
from mild, soft, hard, or just not-bricked-but-not-bootable either bricks
but when it goes from "Last evening battery was drowned so I reached home and plugged it to charger and its on bootloop since then" ... i wasnt flashing my phone or anything else, it just happened, then 99% of the time it's a hardware problem, and wont be fixed without changing the motherboard.
Click to expand...
Click to collapse
A hardware issue could definitely be the cause. Thanks for bringing that up. As of there being four types... I believe there is really only two. Soft (still have access to some degree whether it be the recovery or just fastboot for example), hard (absolutely no access), and boot loops (Everything is operable but something as small as a file not having proper permissions), but could honestly be debatable so lets just agree just to agree lol.
With that said, I experienced a soft brick last weekend. I was converting my device to f2fs and borked my partitions after twrp abruptly crashed on me. Had no access to the recovery, system, and so on - it all failed to boot or respond in any way. I did however still have access to fastboot which allowed me to use my decrypted RUU. If not for that, my phone would be nothing more than a paperweight.
Sent from my C525c using Tapatalk

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?

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.