Database Info

[Q] Bootloop with acess to Recovery

I've been using Cromi-X 4.7 since Mid to Late summer for my daily and have had zero issues. Last night however, my TF300 chirped to let me know I had an email, I turned the screen on and then it began bootlooping. I do have access to Recovery, and I've tried wiping and flashing a few other ROMs that I had on my SD card, but they all make it as far as the splash screen then freeze and reboot. So I'm a little confused as to where to go from here.
Recovery: TWRP v2.5.0.0
ww_epad-10.6.1.27.1-20130711
Any advice would be much appreciated. Thanks!

cresco299 said:
I've been using Cromi-X 4.7 since Mid to Late summer for my daily and have had zero issues. Last night however, my TF300 chirped to let me know I had an email, I turned the screen on and then it began bootlooping. I do have access to Recovery, and I've tried wiping and flashing a few other ROMs that I had on my SD card, but they all make it as far as the splash screen then freeze and reboot. So I'm a little confused as to where to go from here.
Recovery: TWRP v2.5.0.0
ww_epad-10.6.1.27.1-20130711
Any advice would be much appreciated. Thanks!
Click to expand...
Click to collapse
If you can use recovery, I suppose you can use fastboot too?
Try the following:
fastboot erase misc
fastboot erase staging
fastboot reboot
If that won't work, look for Buster99's script to erase everything and reflash stock Asus ROM. Fixed issues for a lot of people allowing you a fresh start.
Sent from my TF300T using Tapatalk

f69m said:
If you can use recovery, I suppose you can use fastboot too?
Try the following:
fastboot erase misc
fastboot erase staging
fastboot reboot
If that won't work, look for Buster99's script to erase everything and reflash stock Asus ROM. Fixed issues for a lot of people allowing you a fresh start.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Thankyou! I had to re-educate myself on Fastboot but once that was done I was able to try your suggestions. Your first one did not do the trick, but Buster99's got me most of the way. I had to reflash the TWRP near the end of his process to get it to work for me.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash recovery C:\Users\Jeff\Downloads\twrp-2.5.0.0-JB.blob (THIS IS THE LINE I ADDED)
fastboot -i 0x0B05 flash system C:\Users\Jeff\Documents\WW_epad-user-10.6.1.15.3\blob
fastboot -i 0x0B05 reboot
So maybe my recovery was messed up? At anyrate, it looks like I'm back in action. For anyone who needs to follow how all this was done, there is a good fastboot tutorial here. and here is the link to Buster99's solution.
Thankyou for pointing me in the right direction f69m!

cresco299 said:
Thankyou! I had to re-educate myself on Fastboot but once that was done I was able to try your suggestions. Your first one did not do the trick, but Buster99's got me most of the way. I had to reflash the TWRP near the end of his process to get it to work for me.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash recovery C:\Users\Jeff\Downloads\twrp-2.5.0.0-JB.blob (THIS IS THE LINE I ADDED)
fastboot -i 0x0B05 flash system C:\Users\Jeff\Documents\WW_epad-user-10.6.1.15.3\blob
fastboot -i 0x0B05 reboot
So maybe my recovery was messed up? At anyrate, it looks like I'm back in action. For anyone who needs to follow how all this was done, there is a good fastboot tutorial here. and here is the link to Buster99's solution.
Thankyou for pointing me in the right direction f69m!
Click to expand...
Click to collapse
Oops, careful!
You are using the wrong recovery.
For the bootloaders coming with 10.6.* ROMs you need to use TWRP -42.
Don't use -jb, that is for the older 10.4.* bootloaders.
Sent from my TF300T using Tapatalk

f69m said:
Oops, careful!
You are using the wrong recovery.
For the bootloaders coming with 10.6.* ROMs you need to use TWRP -42.
Don't use -jb, that is for the older 10.4.* bootloaders.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
That would explain why I had to reinstall an updated TWRP to access recovery. I know just enough to make my self dangerous
Thank you again.

[Q] In dire need of help, stuck with no ROM on phone :(

Hello all,
as the title says, I'm stuck in TWRP recovery after wiping my rom to revert to stock... then realising that the recovery doesn't recognise the image as it's a .tgz file.
I've tried to ADB into it, but no such luck, I just get error: device not found.
Does anyone know a way I can fix this?
I've also tried the adb sideload feature of TWRP to no avail.
Thanks in advanced guys.

Flash the factory image through fastboot. Download and run flash-all.bat (something along those lines)
Sent from my Nexus 5 using Tapatalk

Go to bootloader and run "fastboot devices" and see whether your device gets detected or not? If it does, then flash the factory images. System and boot img files would do the job.
If it doesn't then you need to fix the adb, fastboot issues first. Follow these threads:
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339
If you have an OTG cable with you, you can directly flash the rom from a usb stick!

tangosierra_ said:
Flash the factory image through fastboot. Download and run flash-all.bat (something along those lines)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
'fastboot is not recognised as an internal or external command, operable program or batch file.'
Also, i'm trying this from the PC just to be clear, as I can't boot my phone lol.
soon as i run flash-all.bat i get the error i put on the first line

Dixi1801 said:
'fastboot is not recognised as an internal or external command, operable program or batch file.'
Also, i'm trying this from the PC just to be clear, as I can't boot my phone lol.
soon as i run flash-all.bat i get the error i put on the first line
Click to expand...
Click to collapse
You havent got fastboot installed.
Go to teh link in my signature.... Then go to section 1b, 1

usb/otg
Dixi1801 said:
Hello all,
as the title says, I'm stuck in TWRP recovery after wiping my rom to revert to stock... then realising that the recovery doesn't recognise the image as it's a .tgz file.
I've tried to ADB into it, but no such luck, I just get error: device not found.
Does anyone know a way I can fix this?
I've also tried the adb sideload feature of TWRP to no avail.
Thanks in advanced guys.[/QUOT
Download any compatible rom to a usb/otg..mount from TRWP and your good to go..Happens to me once..Just download any compatible roms just to bring up your phone..
Click to expand...
Click to collapse

Dixi1801 said:
'fastboot is not recognised as an internal or external command, operable program or batch file.'
Also, i'm trying this from the PC just to be clear, as I can't boot my phone lol.
soon as i run flash-all.bat i get the error i put on the first line
Click to expand...
Click to collapse
remove all old drivers and restart
install http://forum.xda-developers.com/showthread.php?p=42407269&__utma=248941774.1031819907.1403635167.1403781687.1403790944.7&__utmb=248941774.1.10.1403790944&__utmc=248941774&__utmx=-&__utmz=248941774.1403790944.7.7.utmcsr=google|utmccn=%28organic%29|utmcmd=organic|utmctr=%28not%20provided%29&__utmv=-&__utmk=239174656
place the android sdk windows file attached here in c: drive
now start cmd prompt and type
Code:
cd c:\android-sdk-windows\platform-tools
now proceed with fastboot command in this order
Code:
fastboot flash bootloader C:/hammerhead-ktu84m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/hammerhead-ktu84m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/hammerhead-ktu84m/system.img
fastboot flash userdata C:/hammerhead-ktu84m/userdata.img
fastboot flash boot C:/hammerhead-ktu84m/boot.img
fastboot flash recovery C:/hammerhead-ktu84m/recovery.img
fastboot erase cache
note:remember to extract the factory stock image till u see these files attached and place it in C: drive and yes the built name should be same as yours of 4.4.4 then KTU84P inplace of ktu84m

shhbz said:
remove all old drivers and restart
install http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=239174656
place the android sdk windows file attached here in c: drive
now start cmd prompt and type
Code:
cd c:\android-sdk-windows\platform-tools
now proceed with fastboot command in this order
Code:
fastboot flash bootloader C:/hammerhead-ktu84m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/hammerhead-ktu84m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/hammerhead-ktu84m/system.img
fastboot flash userdata C:/hammerhead-ktu84m/userdata.img
fastboot flash boot C:/hammerhead-ktu84m/boot.img
fastboot flash recovery C:/hammerhead-ktu84m/recovery.img
fastboot erase cache
note:remember to extract the factory stock image till u see these files attached and place it in C: drive and yes the built name should be same as yours of 4.4.4 then KTU84P inplace of ktu84m
Click to expand...
Click to collapse
Too Long. 15 second installer is the best way to get adb and fastboot. See previous post
Sent from my Nexus 5 using Tapatalk

rootSU said:
Too Long. 15 second installer is the best way to get adb and fastboot. See previous post
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
was unable to find link to 15 second installer as what i remember was the minimal adb and fastboot and both works great and flash-all.bat script does not work evrytime so just wanted the guy to be sure the he type the commands in right direction instead getting error cant find and stuff

shhbz said:
was unable to find link to 15 second installer as what i remember was the minimal adb and fastboot and both works great
Click to expand...
Click to collapse
1b1 in the link in my signature.
Minimal is fine but you have to manually add to environment variables or cd to the directory but that's all done with the 15 seconds one.
Sent from my Nexus 5 using Tapatalk

Thanks for the help guys.
RootSU, you saved me haha, was sat at work stressing trying to sort the mess I made out!
I'm all stock now... But the screen keeps going off because of the proximity sensor haha -_-
Thanks again though. Can always count on a Yorkshireman

The important thing is to remain calm and know it can be fixed
Sent from my Nexus 5 using Tapatalk

OnePlus one stuck at boot screen, please help!

FIxed with this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
My 64gb OnePlus One does not boot anymore.
I wiped system, data, cache, and dalvik and then flashed the 9/20 cm nightly, gapps, and supersu. The device rebooted and I saw the CM loading circle. However, next time I looked at the device, it was back at the Oneplus boot screen. After this, I have never been able to get it past this screen.
I have tried flashing the stock image using this guide (steps 1-3), as well as downloading the fastboot image from cnygn.com and flashing each img from fastboot using these commands:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Additionally I have tried flashing CM11 from TWRP, which still results in the same problem. I am able to access and use fastboot and twrp just fine.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
EDIT: I managed to install ColorOS with this guide, and it boots fine. However, I need CM with Google Play so after trying to get cm11s 33r with this guide, I'm back at square one with the phone not getting past the boot screen. Any ideas?

Hi so i guess you don't have a backup in the device,sometimes the easiest way to fix things is the right way just download this tool the one for your device 16/32gb the second version(v.2) put your phone in fastboot mode and hit cm update in the tool.
---------- Post added at 06:29 AM ---------- Previous post was at 06:26 AM ----------
http://www.youtube.com/watch?app=desktop&persist_app=1&v=5O2e_R_TbVg

android.345 said:
My 64gb OnePlus One does not boot anymore.
Click to expand...
Click to collapse
Your phone goes in fastboot mode, so you shouldn't even think it could be lost forever.
The guide you're following is the right one, so just make sure you are following it correctly. I assume you unlocked your bootloader before starting the first flashing that soft-bricked your phone, so you should be good to go.
You should just need to do everything that's in the guide you linked, except the 4th step (you don't need to lock the bootloader). Flash the factory images and just reboot (don't flash/wipe/whatever anything else), it should be fine. Make sure you're flashing the right ones though, for example, since you have the 64GB version, you have to flash the userdata image for the 64GB OPO.
I don't think you should look for "1-click" toolkits, they can be more harmful than good since you don't know what you're actually doing.

bradipovsky said:
Your phone goes in fastboot mode, so you shouldn't even think it could be lost forever.
The guide you're following is the right one, so just make sure you are following it correctly. I assume you unlocked your bootloader before starting the first flashing that soft-bricked your phone, so you should be good to go.
Click to expand...
Click to collapse
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'

android.345 said:
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
Click to expand...
Click to collapse
Sorry but I'm no expert and I'm already out of ideas... The only thing that might be wrong in what you're doing is that I remember the file "userdata.img" being for the 16GB version, the one for the 64GB was called "userdata_64.img" or something like that. I don't know if this can be the problem in your case though.
I have no experience in using fastboot on Windows, so I don't know if there can be a driver problem that doesn't pop up while you try to flash.
If I were you the next things I would try are:
- See if TWRP lets you mount OTG storage, that way you can just flash a new ROM
- Double check your adb/fastboot installation (do any commands work? Does "fastboot reboot" work?)
Anyway please keep in mind I'm just guessing, you may want to wait for someone with some more experience to drop by...

bradipovsky said:
Sorry but I'm no expert and I'm already out of ideas... The only thing that might be wrong in what you're doing is that I remember the file "userdata.img" being for the 16GB version, the one for the 64GB was called "userdata_64.img" or something like that. I don't know if this can be the problem in your case though.
I have no experience in using fastboot on Windows, so I don't know if there can be a driver problem that doesn't pop up while you try to flash.
If I were you the next things I would try are:
- See if TWRP lets you mount OTG storage, that way you can just flash a new ROM
- Double check your adb/fastboot installation (do any commands work? Does "fastboot reboot" work?)
Anyway please keep in mind I'm just guessing, you may want to wait for someone with some more experience to drop by...
Click to expand...
Click to collapse
Do take a look at the update I have posted regarding ColorOS. Flashing a new rom from TWRP does not help. All fastboot commands work.
Also, I have been flashing userdata_64g.img

android.345 said:
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
Click to expand...
Click to collapse
Same problem for me too. Device worked for a week with SOD-s that 2 days ago just rebooted and stay in the loop of logo 1+.. ??

{Solved} [Help] Return Back to Stock

So I tried to return back to stock with the Factory Images and I keep running into a problem. It won't let me and now I am stuck in a bootloop. I tried the flash-all script provided by Google and it failed after flashing the Bootloader and Radio. I also tried the toolkit located in the Development section and I get the same thing!
Any help would be great. I am used to flashing from command line but now there are so many img. I don't know which is what.
Edit:
I downloaded the new ADB and Fastboot drivers from Google and then I was able to restore my phone with Google's flash-all script.

I have not done it yet, but here is my recommendation. Reboot the phone into bootloader. Check the active slot (a or b). Let's assume a is active. These should get your back to stock.
fastboot flash boot_a boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
If you want it back to a brand new phone (not setup) then add the below as well.
fastboot flash userdata userdata.img

Make sure your adb drivers are up to date. You need sdk version 25. 24 and older has issues with the new partitions.

dbrohrer said:
Make sure your adb drivers are up to date. You need sdk version 25. 24 and older has issues with the new partitions.
Click to expand...
Click to collapse
Yeah, that actually worked for me.

Moto G4 play harpia stock firmware.

I figured that since the Motorola web site doesn't have the firmware for this yet I would post a link to my Dropbox so others have access to the firmware. This is for us cellular Moto g4 play xt1607 not sure if it will work for devices on a different carrier. If someone could make a backup of their current rom and test it out to let us all know if it does that would be great. Please hit the thanks button if this helps anyone. https://www.dropbox.com/s/i6jsafelq...y-DEFAULT_regulatory-DEFAULT_CFC.xml.zip?dl=0
This must be flashed with fastboot. If you do not know how to flash with fastboot there are tons of how to videos if you google it.
BACKUP YOUR DEVICE TO SD CARD OR PC BEFORE DOING ANYTHING!!!!!
DISCLAIMER: FLASHING ANYTHING TO YOUR PHONE HAS RISKS. IF YOU DO NOT KNOW WHAT YOU ARE DOING AND YOU HAVE JUST PURCHASED YOUR PHONE AND HAVE NOT UNLOCKED THE BOOTLOADER STOP!!!!! DO NOT CONTINUE. IM NOT SURE WHAT THE EFFECTS WILL BE IF YOU TRY FLASHING WITH A LOCKED BOOTLOADER, IT COULD BRICK YOUR DEVICE!!!!! I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED BY FLASHING THIS FIRMWARE. IF YOU DID SOMETHING WRONG AND DONT FOLLOW INSTRUCTIONS THAN THATS YOUR OWN T.S.

Just in case you can't use google, for some crazy reason, put phone into bootloader mode then on PC download and install minimal fastboot and adb then download firmware, unzip firmware to desktop then open that file and click on a blank spot then hold shift and right click on that blank spot then click open command window here. In that command window type
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img sparsechunk.0
fastboot flash system system.img sparsechunk.1
fastboot flash system system.img sparsechunk.2
fastboot flash system system.img sparsechunk.3
fastboot flash system system.img sparsechunk.4
fastboot flash system system.img sparsechunk.5
fastboot flash system system.img sparsechunk.6
fastboot flash system system.img sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clog
fastboot oem fb_mode_clear
fastboot reboot
If you are running windows 10 you can copy all lines and paste to the command window and it will do all without having to type every line one by one, not sure if it works the same on windows 8.1, 8 or 7 but it does on 10 just remember to hit enter after it completes and you see fastboot reboot on the command window for some reason it doesn't do this for you. That's all there is to it it's very easy. After the device has rebooted you will be at 100% stock with a completely de-bloated rom! This should work on any xt1607, but please be safe and make a backup on sd card or PC before doing anything. If you are still having issues I will have my 4 year old come to your house to bring you to school. Happy flashing everyone and please hit the thanks button if this helps.

I have tried following your instructions so that i can restore my us cellular xt1607 back to stock but all i get are failed (data transfer failure (unknown error)) messages.not really sure what the issue is. I am using minimal fastboot and adb 1.4. Any help would be greatly appreciated.
DanHutchins said:
Just in case you can't use google, for some crazy reason, put phone into bootloader mode then on PC download and install minimal fastboot and adb then unzip firmware to desktop then open that file and click on a blank spot then hold shift and right click on that blank spot then click open command window here. In that command window type
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img sparsechunk.0
fastboot flash system system.img sparsechunk.1
fastboot flash system system.img sparsechunk.2
fastboot flash system system.img sparsechunk.3
fastboot flash system system.img sparsechunk.4
fastboot flash system system.img sparsechunk.5
fastboot flash system system.img sparsechunk.6
fastboot flash system system.img sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clog
fastboot oem fb_mode_clear
fastboot reboot
If you are running windows 10 you can copy all lines and paste to the command window and it will do all without having to type every line one by one, not sure if it works the same on windows 8.1, 8 or 7 but it does on 10 just remember to hit enter after it completes and you see fastboot reboot on the command window for some reason it doesn't do this for you. That's all there is to it it's very easy. After the device has rebooted you will be at 100% stock with a completely de-bloated rom! This should work on any xt1607, but please be safe and make a backup on sd card or PC before doing anything. If you are still having issues I will have my 4 year old come to your house to bring you to school. Happy flashing everyone and please hit the thanks button if this helps.
Click to expand...
Click to collapse

jestyr8 said:
I have tried following your instructions so that i can restore my us cellular xt1607 back to stock but all i get are failed (data transfer failure (unknown error)) messages.not really sure what the issue is. I am using minimal fastboot and adb 1.4. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Is the bootloader unlocked?

jestyr8 said:
I have tried following your instructions so that i can restore my us cellular xt1607 back to stock but all i get are failed (data transfer failure (unknown error)) messages.not really sure what the issue is. I am using minimal fastboot and adb 1.4. Any help would be greatly appreciated.
Click to expand...
Click to collapse
What command gives the error?

I am unlocked and root with twrp and su installed and working. Unfortunately, I forgot the cardinal rule of making a backup before rooting. phone is working but having some issues. As far as which command is giving me the issues.
fb_mode_set is fine. but after that I get.
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
DanHutchins said:
Is the bootloader unlocked?
Click to expand...
Click to collapse

jestyr8 said:
I am unlocked and root with twrp and su installed and working. Unfortunately, I forgot the cardinal rule of making a backup before rooting. phone is working but having some issues. As far as which command is giving me the issues.
fb_mode_set is fine. but after that I get.
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
Click to expand...
Click to collapse
Not sure. Did you make sure USB debugging is active for file transfer?

jestyr8 said:
I am unlocked and root with twrp and su installed and working. Unfortunately, I forgot the cardinal rule of making a backup before rooting. phone is working but having some issues. As far as which command is giving me the issues.
fb_mode_set is fine. but after that I get.
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
Click to expand...
Click to collapse
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.

II seem to be going backwards.
Heres the steps i had been following..that now no longer seem to work. with phone running....plug in, run minimal adb...check for devices with adb devices command...device is listed...then use adb reboot bootloader. from there I started using your list of commands to flash the phone. however after the first command to set fastboot mode all I get are errors. now for some reason adb isn't even seeing my phone.
DanHutchins said:
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
Click to expand...
Click to collapse

jestyr8 said:
II seem to be going backwards.
Heres the steps i had been following..that now no longer seem to work. with phone running....plug in, run minimal adb...check for devices with adb devices command...device is listed...then use adb reboot bootloader. from there I started using your list of commands to flash the phone. however after the first command to set fastboot mode all I get are errors. now for some reason adb isn't even seeing my phone.
Click to expand...
Click to collapse
That's because if you unplug the phone from the PC then plug it back in it defaults the USB debugging to charge only. If you get into twrp you can still put a custom ROM in root of phone to flash in twrp. I would try that then try to install the stock again. Be sure to have debugging set to file transfer.

I've been doing that...I'll give squids CM13 rom a shot as it is the only rom out there and see if that works. Thanks for your help. I really wasn't expecting such a quick response on a Saturday morning..I'll let you know how it goes
DanHutchins said:
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
Click to expand...
Click to collapse

jestyr8 said:
I've been doing that...I'll give squids CM13 rom a shot as it is the only rom out there and see if that works. Thanks for your help. I really wasn't expecting such a quick response on a Saturday morning..I'll let you know how it goes
Click to expand...
Click to collapse
Please do as of now that's the best I can do. Everything worked fine for me. I have flashed the same file many times on my g4 play

jestyr8 said:
I've been doing that...I'll give squids CM13 rom a shot as it is the only rom out there and see if that works. Thanks for your help. I really wasn't expecting such a quick response on a Saturday morning..I'll let you know how it goes
Click to expand...
Click to collapse
Were you able to get back to stock?

DanHutchins said:
Were you able to get back to stock?
Click to expand...
Click to collapse
Haven't gotten back to stock yet, but did get cm13 running with no issues. I'm still playing with it to try and see what's up. Since I've gotten cm13 running I'm undecided on staying with it and upgrading to cm14 when it's ported or continue trying to go back to stock and getting nougat thru that way.

jestyr8 said:
Haven't gotten back to stock yet, but did get cm13 running with no issues. I'm still playing with it to try and see what's up. Since I've gotten cm13 running I'm undecided on staying with it and upgrading to cm14 when it's ported or continue trying to go back to stock and getting nougat thru that way.
Click to expand...
Click to collapse
I like cm13 there just aren't any real good themes for free. I don't mind donating to a dev. but if I can't test it out to see if I like it or not I don't want to pay.

I'm using the material glass theme along with stealth icons, i like it a lot

jestyr8 said:
I'm using the material glass theme along with stealth icons, i like it a lot
Click to expand...
Click to collapse
Looks cool.

DanHutchins said:
Looks cool.
Click to expand...
Click to collapse
So just further update. Got as far as fastboot partition gpt.bin. after that it just gives me transfer failed errors. So I guess I am just going to stick with cm13 since that is running good. at least until someone makes a flashable zip of the stock firmware. I have never tried any dev work with android, so while I know it is possible to make a flashable zip out of these files it is way beyond my skills and knowledge. Thanks Dan for your help and fast response time.

jestyr8 said:
So just further update. Got as far as fastboot partition gpt.bin. after that it just gives me transfer failed errors. So I guess I am just going to stick with cm13 since that is running good. at least until someone makes a flashable zip of the stock firmware. I have never tried any dev work with android, so while I know it is possible to make a flashable zip out of these files it is way beyond my skills and knowledge. Thanks Dan for your help and fast response time.
Click to expand...
Click to collapse
No problem, ask around for anyone able to make it flash able with twrp I'm sure someone can or at least give you instructions on how to do it.

USB debugging to file transfer
DanHutchins said:
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
Click to expand...
Click to collapse
Where/how to "change debugging to file transfer" on Win-7?
Thanks!
Until now, my only experience was flashing a recovery image to Moto E2 with command:
Code:
fastboot flash recovery twrp.img
Neither I have to change "USB debugging to file transfer", nor I needed to use command
Code:
fastboot oem fb_mode_set
Is that something new and specific to Moto G Play 4th Gen?
Edit:
I have just unlocked the bootloader of my new Moto G4 Play and flashed a new logo file with command:
Code:
fastboot flash logo logo.bin
Still puzzled by "change debugging to file transfer"