Related
I updated my phone to Nexus to 5.1 last night and it got stuck in the boot animation but I figured it would be done when I woke up. Much to my dismay that was not the case so I tried to factory reset and now I get this message that says "No OS found." Tried to plug it up to the computer but it won't connect. I think it may have something to do with the OEM Lock but I cant fix that without the phone turning on. Please help!
How exactly did you upgrade your phone?
Sent from my Benzo'd Google N6 on VZ
lostnthought said:
I updated my phone to Nexus to 5.1 last night and it got stuck in the boot animation but I figured it would be done when I woke up. Much to my dismay that was not the case so I tried to factory reset and now I get this message that says "No OS found." Tried to plug it up to the computer but it won't connect. I think it may have something to do with the OEM Lock but I cant fix that without the phone turning on. Please help!
Click to expand...
Click to collapse
Please provide more info. Stock or custom recovery?
Evolution_Freak said:
Please provide more info. Stock or custom recovery?
Click to expand...
Click to collapse
Custom Recovery.. TWRP v2.8.2
lostnthought said:
Custom Recovery.. TWRP v2.8.2
Click to expand...
Click to collapse
From bootloader, enter the following fastboot commands:
fastboot format cache
fastboot format userdata
This should allow you to get back into TWRP and flash a ROM.
DebianDog said:
How exactly did you upgrade your phone?
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
This may sound silly but I'm not 100% sure. A system notification had been on my screen for over two weeks saying that I had a system update to 5.1 and I finally decided to download and install said update and then it sent me to recovery mode. I don't know why I did but I hit fix permissions.. Just fiddling trying to figure everything out and this is where we are.
Evolution_Freak said:
From bootloader, enter the following fastboot commands:
fastboot format cache
fastboot format userdata
This should allow you to get back into TWRP and flash a ROM.
Click to expand...
Click to collapse
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
lostnthought said:
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
Click to expand...
Click to collapse
I'm not asking you to boot to recovery. Boot to bootloader.
lostnthought said:
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
Click to expand...
Click to collapse
move a rom via a computer to your phone. either connect the recovery to your computer and move it, or connect to a computer and adb push it to your phone.
Sorry, I guess I misread your post. I thought you said can't get to recovery. From TWRP you should be able to enable MTP transfer. Then your PC should see it and you can transfer files as @simms22 suggested.
lostnthought said:
"No OS found."
Click to expand...
Click to collapse
From TWRP, perhaps you wiped the System partition? Heh, I did that just last night... woops... "round 2"!
As a side note, if you're trying to use adb/fastboot from Windows... I had nothing but problems myself, even with the proper drivers. At worst, I had to open the Device Manager, find the phone, and force-install ("update") the driver to Android->Composite USB Device before it would be recognized. Absurd, but pains of working from Windows. (Conversely, I've had pain-free experiences from OSX and Ubuntu.)
vormund said:
From TWRP, perhaps you wiped the System partition? Heh, I did that just last night... woops... "round 2"!
As a side note, if you're trying to use adb/fastboot from Windows... I had nothing but problems myself, even with the proper drivers. At worst, I had to open the Device Manager, find the phone, and force-install ("update") the driver to Android->Composite USB Device before it would be recognized. Absurd, but pains of working from Windows. (Conversely, I've had pain-free experiences from OSX and Ubuntu.)
Click to expand...
Click to collapse
you dont need adb to move anything to your phone when using twrp. just connect to twrp using the mtp option.
Hello,
I have my G watch R for a week and because there was no update, i've tried to install it by myself after reading some posts on XDA.
I've tried that :
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot flash recovery filename.img)
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
All this works until the "sideload" part because ADB can't see my watch when it's on recovery mode.
So i have locked again the bootloader and i thought to give up, when yesterday, OTA arrived...
But it hasn't worked : a bar has loaded and it arrived on a red triangle with an exclamation mark, i've clicked on it and i had the recovery mode menu (reboot, install from adb, etc)
What can I do to make work this OTA ?
Thanx for help !
have you tried to flash the original recovery?
Yes, I've tried several times, I think that is why i can't update with OTA.
But is there a solution ? Is it possible to reinstall original recovery and will it solve my problem ?
Or must I install the update with ADB ? Because I still don't know how make the watch recognized when in recovery mode (not even recognized with a yellow triangle, like it was unplugged )
I had the same problem but with 4.4w.2 and I solved it flashing the stock recovery. unfortunately I can not find your recovery version, I would have linked. to manually update do not know ... I'm sorry. Find your recovery and flash it!
Thanx for your answer,
I thought to do that, but I neither have found 44w1 stock, i'm trying with 44w2 stock and it doesn't work.
I'll try to find 44w1 stock, thanx for confirmation about this way.
So, while I can't find 44w1 stock (i think nobody has uploaded it on the internet because nobody wants to put 44w1 on his watch ^^ ), I've tried TWRP Recovery
When I try to launch the 5.5.1 zip install , I have this error message on the watch in TWRP Recovery :
"this package is for device: lenok. this device is dory"
I've made some research and found that Dory is for G Watch and not for G Watch R, so what ?
I don't understand...
Anyway, if someone knows where to find 44w1 stock...
Did you enabled the debugging mode and gave permission for it on the watch?
sounds like you are missing the ADB drivers on your PC
and be careful with sideloading the update to select the correct one, e.g. the last update is an incremental one and won't flash on 4.4 (or if you get it to flash, it will probably not worke)
good luck!
Have a look here... http://4pda.ru/forum/lofiversion/index.php?t647135-20.html.
It's not English, but the links are all there. I recently updated a watch from 4.4 to 5.11 using these images. Put the watch into Bootloader and install the ADB drivers, then start with 4.4w2 and work your way up. It takes time as you'll need to restart the watch each time.
Genna7 said:
Did you enabled the debugging mode and gave permission for it on the watch?
Click to expand...
Click to collapse
Yes I did : I could flash a recovery because I've given permission and enabled debugging mode
2k4ever said:
sounds like you are missing the ADB drivers on your PC
and be careful with sideloading the update to select the correct one, e.g. the last update is an incremental one and won't flash on 4.4 (or if you get it to flash, it will probably not worke)
good luck!
Click to expand...
Click to collapse
No I'm not, same answer : I could flash a recovery without any problem : it's only when I'm on recovery that I can't communicate with the watch : It's working when android wear is started and when I'm on bootload. Thanx for the warning
dunjamon said:
Have a look here... *url*
It's not English, but the links are all there. I recently updated a watch from 4.4 to 5.11 using these images. Put the watch into Bootloader and install the ADB drivers, then start with 4.4w2 and work your way up. It takes time as you'll need to restart the watch each time.
Click to expand...
Click to collapse
Thank you but i have all those images, I think I need 44w1 recovery and only this one
Thank you all
what happens if you just flash the 4.4w2 full image? I remember there being issues with the 4.4 recovery and I had to manually update to the 5.0.1 recovery before then upgrading further.
edit...what drivers are you using? I think you need the adb composite ones and not the normal adb ones.
I'm using the naked ones I think.
What image are you talking about ? System or recovery ?
Ze_Pend said:
I'm using the naked ones I think.
What image are you talking about ? System or recovery ?
Click to expand...
Click to collapse
The OTA ones from my link.
Ze_Pend said:
Yes I did : I could flash a recovery because I've given permission and enabled debugging mode
No I'm not, same answer : I could flash a recovery without any problem : it's only when I'm on recovery that I can't communicate with the watch : It's working when android wear is started and when I'm on bootload. Thanx for the warning
Click to expand...
Click to collapse
flashing a recovery happens in fastboot mode, which requires an unlocked bootloader, but not enabling the debugging mode
sideloading however happens (once the recovery has been loaded) through ADB - and ADB requires the right drivers on your PC as well as the right tools/developer environment
try to connect your normally booted watch to your PC and run
PHP:
adb devices
if that lists your watch, you are good to go, otherwise ADB isn't set up properly
The watch is listed by adb devices when on work mode or in bootloader mode, but not when in recovery mode.
That's what I said first
dunjamon said:
The OTA ones from my link.
Click to expand...
Click to collapse
Either I can't if with 44w2 recovery, or it says ""this package is for device: lenok. this device is dory" if with TWRP recovery.
Ze_Pend said:
Either I can't if with 44w2 recovery, or it says ""this package is for device: lenok. this device is dory" if with TWRP recovery.
Click to expand...
Click to collapse
Do you have the G Watch R (round) or the G Watch (Square)?
"The watch is listed by adb devices when on work mode or in bootloader mode, but not when in recovery mode."
I had this problem too. When you're in recovery mode you have to open the windows device manager and windows should tell you something about an uninstalled driver. You need to right click this device and install the adb drivers.
Yesterday a LG L Fino was brought to me for repair.It makes an error on boot.The error is the boot certificate verify error.I cannot fix this!
I tried booting in recovery,gives me the boot screen,then the error,black screen.
I tried download mode,same.
I even tried flashing it,but LG Flash Tool does not recognize it.When i connect the phone a whole alphabet of drives would appear with LG Logos on them.I was able to only open one of them,the size was 64MB and it stored a image folder.Device manager recognizes the phone as QHSUSB_BULK and a ton of Unknown Devices would appear,after that they disappear and the phone will be recognized as LGE AndroidNet USB Serial Port(COM4).Thank you :angel:
filipkosteski said:
Yesterday a LG L Fino was brought to me for repair.It makes an error on boot.The error is the boot certificate verify error.I cannot fix this!
I tried booting in recovery,gives me the boot screen,then the error,black screen.
I tried download mode,same.
I even tried flashing it,but LG Flash Tool does not recognize it.When i connect the phone a whole alphabet of drives would appear with LG Logos on them.I was able to only open one of them,the size was 64MB and it stored a image folder.Device manager recognizes the phone as QHSUSB_BULK and a ton of Unknown Devices would appear,after that they disappear and the phone will be recognized as LGE AndroidNet USB Serial Port(COM4).Thank you :angel:
Click to expand...
Click to collapse
Will the device boot to fastboot? Does the device respond to adb commands?
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Will the device boot to fastboot? Does the device respond to adb commands?
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Sorry i was inactive,but the LG L Fino is gone now i do not need help.Thank you
Droidriven said:
Will the device boot to fastboot? Does the device respond to adb commands?
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Hi, I have the same problem, here is the picture of my screen.
I have tried to follow these steps, but my phone cannot enter Secure boot mode.
Any idea what can I do?
thanks
ndr113 said:
Hi, I have the same problem, here is the picture of my screen.
I have tried to follow these steps, but my phone cannot enter Secure boot mode.
Any idea what can I do?
thanks
Click to expand...
Click to collapse
Hey there
I have a LG L90 D410 (Similar Qualcomm Device)
And I faced the same issue after a bad flash.
Did you flash anything?
Does the LG logo show up?
Please answer the above questions so I would be able to solve your problem
Gaptain4 said:
Hey there
I have a LG L90 D410 (Similar Qualcomm Device)
And I faced the same issue after a bad flash.
Did you flash anything?
Does the LG logo show up?
Please answer the above questions so I would be able to solve your problem
Click to expand...
Click to collapse
Hello sir!
I have never flash the phone. The first problem that I have seen was after one restart, it won't boot the os, I have seen the LG logo and after that it keeps reboots again. I have entered in recovery mode and wipe all data, but it didn't help. After that I started to see the message above(error) and that's all. My battery is completely empty and cannot charge it because the phone doesn't charge.
ndr113 said:
Hello sir!
I have never flash the phone. The first problem that I have seen was after one restart, it won't boot the os, I have seen the LG logo and after that it keeps reboots again. I have entered in recovery mode and wipe all data, but it didn't help. After that I started to see the message above(error) and that's all. My battery is completely empty and cannot charge it because the phone doesn't charge.
Click to expand...
Click to collapse
Hey there did you use advanced wipe to clear your data or was it factory reset.
If the LG Logo shows up and then the error comes then you can enter download mode by switching off the phone and then hold volume up key and at the same time insert a usb. You would enter download mode. If you enter the mode you can flash a KDZ
Gaptain4 here at your service :fingers-crossed:
Gaptain4 said:
Hey there did you use advanced wipe to clear your data or was it factory reset.
If the LG Logo shows up and then the error comes then you can enter download mode by switching off the phone and then hold volume up key and at the same time insert a usb. You would enter download mode. If you enter the mode you can flash a KDZ
Or If you want custom rom only,enter into recovery mode.
Then click wipe and then advanced wipe.
Check data
Check System
Check Dalvik/art
Check Cache.
And then Press install and download the suitable rom for you phone.
If you cannot resolve the problem contact me again
Gaptain4 here at your service :fingers-crossed:
Click to expand...
Click to collapse
No, they didn't use advanced wipe because they don't have a custom recovery installed. If you read their post more carefully, you'll see where they said that they never flashed the device, this means they have stock recovery, not custom recovery. None of what you posted helps them.
Sent from my LGL84VL using Tapatalk
Droidriven said:
No, they didn't use advanced wipe because they don't have a custom recovery installed. If you read their post more carefully, you'll see where they said that they never flashed the device, this means they have stock recovery, not custom recovery. None of what you posted helps them.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hey there thank for informing me.
He can still enter into download mode and flash kdz using flash tool
Custom Rom cannot be flashed
But a stock rom can be flashed and can be fixed.
Its a soft brick so he can surely flash a stock rom and recover his phone :fingers-crossed:\
When you try to charge your phone it doesn't show the charging status
But when you completely drain your battery to 0% it will show 0% and shows charging and you can confirm that it is charging
hi everyone
i have a LG L25
and i think i messed up flashing it using TWRP.
it stuck in FIRMWARE UPDATE screen and i cant access its TWRP mode
please help me
Marclance said:
hi everyone
i have a LG L25
and i think i messed up flashing it using TWRP.
it stuck in FIRMWARE UPDATE screen and i cant access its TWRP mode
please help me
Click to expand...
Click to collapse
Did you try to flash a stock update using TWRP?
If so, that is the problem. Stock updates can't be applied to a rooted device or a device that has TWRP installed, any one or both of these will interfere with applying the update. You can only apply stock updates to devices that have an unmodified system partition(no root, no Xposed) and have stock recovery, stock recovery is required for applying stock updates.
If this is what you did, your only option to fix this is to flash your full stock firmware. Do a Google search for:
"Return to stock (your model number)"
If the tools and files exist for your device, that should find it.
Sent from my LGL84VL using Tapatalk
Hi to everyone, i have an problem with my old moto g 2014, i can't restore it to stock firmware.
When i try to flash stock firmware through fastboot everything is alright but if i reboot it he is stuck in bootlogo screen.
I've used the commands below and attach the logs.
Some one can help me to restore my titan please?
P.S. Sorry for english
Crix.Ful92 said:
Hi to everyone, i have an problem with my old moto g 2014, i can't restore it to stock firmware.
When i try to flash stock firmware through fastboot everything is alright but if i reboot it he is stuck in bootlogo screen.
I've used the commands below and attach the logs.
Some one can help me to restore my titan please?
P.S. Sorry for english
Click to expand...
Click to collapse
To which version did you try to upgrade?
You need to use a special mfastboot rather than normal fastboot.
https://forum.xda-developers.com/mo...unix-mfastboot-linux-mac-os-x-how-to-t2941888
avrockz11 said:
To which version did you try to upgrade?
Click to expand...
Click to collapse
To last 6.0 official firmware
Crix.Ful92 said:
To last 6.0 official firmware
Click to expand...
Click to collapse
Try the above link by meganukebmp
I've tried with fastboot linked by meganukebmp but it doesn't work
It's better if you install the stock android 5 then sideload the update to android 6
Syberclone said:
It's better if you install the stock android 5 then sideload the update to android 6
Click to expand...
Click to collapse
Another error
Another one
Are you using the fastboot device command first to make sure your phone is being detected ?
Are you using a batch command or are you entering each command manually ?
It seems like you are missing a step ??
Syberclone said:
Are you using the fastboot device command first to make sure your phone is being detected ?
Are you using a batch command or are you entering each command manually ?
It seems like you are missing a step ??
Click to expand...
Click to collapse
- Are you using the fastboot device command first to make sure your phone is being detected ? YES, MY DEVICE IS RECOGNIZED
- Are you using a batch command or are you entering each command manually ? I INSERT THE COMMAND MANUALLY
- It seems like you are missing a step ?? NOPE, NEVER MISS A STEP
Crix.Ful92 said:
- Are you using the fastboot device command first to make sure your phone is being detected ? YES, MY DEVICE IS RECOGNIZED
- Are you using a batch command or are you entering each command manually ? I INSERT THE COMMAND MANUALLY
- It seems like you are missing a step ?? NOPE, NEVER MISS A STEP
Click to expand...
Click to collapse
Use easy installer. Go to YouTube...search how to restore xt1068(i know yours is xt1080 but do it)the video is by ashwin tech. The first comment has a link to it. Download and put it in the extracted folder of the stock ROM files and click on easy installer.bat
The sequence is 1,3,5,4. Click these numbers and voila!
What file format is the Rom ? What are you using to flash the Rom ?
Hopefully CMKdaGreat has you on the right path
I can't connect my Moto G2 to windows computer, the connection only work with my MacBook Pro
I have installed Motorola Driver and fastboot
Crix.Ful92 said:
I can't connect my Moto G2 to windows computer, the connection only work with my MacBook Pro
I have installed Motorola Driver and fastboot
Click to expand...
Click to collapse
Did you connect your phone without being in fastboot first ?
Make sure you use the administrator command window in the folder that has all the boot.img, rom etc
Crix.Ful92 said:
I can't connect my Moto G2 to windows computer, the connection only work with my MacBook Pro
I have installed Motorola Driver and fastboot
Click to expand...
Click to collapse
Go to Device manager
Go to universal bus something
Update each driver in it
Might solve the problem
Syberclone said:
Did you connect your phone without being in fastboot first ?
Make sure you use the administrator command window in the folder that has all the boot.img, rom etc
Click to expand...
Click to collapse
I can connect only with fastboot mode because the phone does not boot with OS, it only boots into fastboot or recovery (twrp 3.1.1-1)
Crix.Ful92 said:
I can connect only with fastboot mode because the phone does not boot with OS, it only boots into fastboot or recovery (twrp 3.1.1-1)
Click to expand...
Click to collapse
Did you try connecting with the administrator command window ? Some 123 options for rom installation are done with a batch (bat) or execution (exe) files in windows ...also what version of windows are you running ?
I recovered my Moto G from a boot loop after kingroot caused p inblems
Try here ..
https://forum.xda-developers.com/showthread.php?t=2580060
I have the same problem as you with my XT1068, I tried all possible solutions posted here and nothing ...
Did you solved this problem?
My device is bricked coming from a custom ROM in this forum.. I'm not gonna bash the ROM or developer... The thing installs its own custom recovery. I tried to switch ROMs, but could not. Somehow I have managed to brick my phone to the point that it only boots into fast boot mode. I've seen several little guides and snippets here and there but none are truly direct and to the point of how to recover the phone back to stock. I'm not a developer nor do I know how to use command prompt or powershell or linux. I can use the mi flash tool, but always get error missing install.bat?
Robbie D said:
My device is bricked coming from a custom ROM in this forum.. I'm not gonna bash the ROM or developer... The thing installs its own custom recovery. I tried to switch ROMs, but could not. Somehow I have managed to brick my phone to the point that it only boots into fast boot mode. I've seen several little guides and snippets here and there but none are truly direct and to the point of how to recover the phone back to stock. I'm not a developer nor do I know how to use command prompt or powershell or linux. I can use the mi flash tool, but always get error missing install.bat?
Click to expand...
Click to collapse
I would suggest side loading TWRP via adb in fastboot, at least you'll get recover back and can start from there.
I have tried to do that.. for some reason it doesn't work. I've tried several methods exactly as suggested. They always fail..
edit : grammar.. using cheap phone till I can get my sweet restored and working again.
Robbie D said:
I have tried to do that.. for dinner reason it doesn't work. I've tried several methods exactly as suggested. They always fail..
Click to expand...
Click to collapse
When in fastboot mode and connected via the USB cable, in command prompt when you type "fastboot devices" and press enter does your device show up?
Robbie D said:
I have tried to do that.. for dinner reason it doesn't work. I've tried several methods exactly as suggested. They always fail..
Click to expand...
Click to collapse
Further to what I said above, try this method
Xavind said:
When in fastboot mode and connected via the USB cable, in command prompt when you type "fastboot devices" and press enter does your device show up?
Click to expand...
Click to collapse
no.. nothing happens
Robbie D said:
no.. nothing happens
Click to expand...
Click to collapse
Adb should be in root path c
It should be started with admin rights and of course the drivers for the phone should be installed before
I can do that tomorrow...I spent 6 hours effen with it today and pretty frustrated..
Robbie D said:
I can do that tomorrow...I spent 6 hours effen with it today and pretty frustrated..
Click to expand...
Click to collapse
Xiaomi Redmi Note 10 Pro USB Drivers | Device Drivers
The drivers to connect/unlock the Xiaomi Redmi Note 10 Pro smart phone to backup,tether, network and more are below. Be aware if you are looking to unlock the bootloader or other advanced software functions it most likely will void any existing warranty. Also Functions used at the fastboot...
oemdrivers.com
Robbie D said:
I can do that tomorrow...I spent 6 hours effen with it today and pretty frustrated..
Click to expand...
Click to collapse
update drivers , then pc should read fastboot.
download and then flash recovery using
fastboot flash recovery (***).img
through recovery install rom again
I hope you watched the video I added to the thread. Launch command prompt in the folder you have adb in. Drivers are key though
Finally got back to this and made sure to put all of the files in c: drive... It shows something on a port, but no devices..
I connected my cheap moto g play and it shows up. I guess that eliminates bad cable and possibly phone is literally Perma bricked?
Xavind said:
I hope you watched the video I added to the thread. Launch command prompt in the folder you have adb in. Drivers are key though
Click to expand...
Click to collapse
I did watch it several times. I was doing everything you did, step by step... Had to pause,rewind, etc... Several times. The only step you didn't really specify was putting it all on c:\drive... Very helpful video and much appreciated.
Robbie D said:
I did watch it several times. I was doing everything you did, step by step... Had to pause,rewind, etc... Several times. The only step you didn't really specify was putting it all on c:\drive... Very helpful video and much appreciated.
Click to expand...
Click to collapse
Did you solved it now or not?
Which drivers you've installed?
Robbie D said:
I did watch it several times. I was doing everything you did, step by step... Had to pause,rewind, etc... Several times. The only step you didn't really specify was putting it all on c:\drive... Very helpful video and much appreciated.
Click to expand...
Click to collapse
Did you solved it now or not?
Which drivers you've installed?
No.. Still bricked! I installed the driver's that were linked in the video and I had them installed from when it was working properly.. Drivers aren't the issue.. I'm not sure what to try next.
Robbie D said:
No.. Still bricked! I installed the driver's that were linked in the video and I had them installed from when it was working properly.. Drivers aren't the issue.. I'm not sure what to try next.
Click to expand...
Click to collapse
Try to connect the phone again
If Adb fastboot devices not working then leave phone connected and restart the phone to fastboot again via phone buttons and if restarted fastboot mode try again to adb fastboot devices
Laptapper said:
Try to connect the phone again
If Adb fastboot devices not working then leave phone connected and restart the phone to fastboot again via phone buttons and if restarted fastboot mode try again to adb fastboot devices
Click to expand...
Click to collapse
Did you look at the photos in my previous 2 posts? The first shows something is there, but doesn't give a device name or number.. The 2nd shows my moto g play and it is identified by fastboot devices... I think the entire storage, including any factory recovery or images are all completely gone..