Database Develop

[Q] Stuck in a reboot loop, can't get into recovery, what to do?

I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!

brasstongue said:
I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!
Click to expand...
Click to collapse
Can u get into bootloader?? Press power + vol down??

brasstongue said:
After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols.
Click to expand...
Click to collapse
that means your firmware is either in a state of limbo, or you corrupted one of your partitions.
so I decided to try to reflash the stock ROM, using the RUU zip found here. Due to some problem
Click to expand...
Click to collapse
which ruu, and what was the problem
But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM.
Click to expand...
Click to collapse
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt

Thanks for the reply.
nkk71 said:
which ruu, and what was the problem
Click to expand...
Click to collapse
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
nkk71 said:
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
Click to expand...
Click to collapse
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
nkk71 said:
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
Click to expand...
Click to collapse
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
nkk71 said:
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
Click to expand...
Click to collapse
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
nkk71 said:
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt
Click to expand...
Click to collapse
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>

brasstongue said:
Thanks for the reply.
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>
Click to expand...
Click to collapse
my bad, thought I read Sprint, not sure if Sprint and Verizon use same recovery, but that doesn't really matter now
unless you can get to bootloader, you're stuck, sorry.
If your pc does see "fastboot devices" then it must be in bootloader and flashing a ruu.zip (if available) could (that's a very big could) get the device working again.

Stuck in bootloop, can't enter Bootloader after unlock

Hi XDA,
I currently have an issue with my One, I'm stuck at the white HTC-screen where it says "powered by android" at the bottom, I can't get into the bootloader, no matter what I try (I've tried every combination there is, multiple times) the PC detects an Android ADB Interface, but it says "unauthorized".
This happened after I unlocked my bootloader regularly via the HTC Dev-method.
If I type "adb reboot bootloader" into a command prompt, it says "error: device unauthorized. Please check the confirmation dialog on your device." but there is nothing on my screen other than the splash-logo.
Is there anything I could do?
Thanks in advance for your time and help.
edit:
I just noticed that the softkeys don't flash when I hold down the power-button, not sure if this helps you determine the error.

No ideas? :/

HeavyHDx said:
Hi XDA,
I currently have an issue with my One, I'm stuck at the white HTC-screen where it says "powered by android" at the bottom, I can't get into the bootloader, no matter what I try (I've tried every combination there is, multiple times) the PC detects an Android ADB Interface, but it says "unauthorized".
This happened after I unlocked my bootloader regularly via the HTC Dev-method.
If I type "adb reboot bootloader" into a command prompt, it says "error: device unauthorized. Please check the confirmation dialog on your device." but there is nothing on my screen other than the splash-logo.
Is there anything I could do?
Thanks in advance for your time and help.
edit:
I just noticed that the softkeys don't flash when I hold down the power-button, not sure if this helps you determine the error.
Click to expand...
Click to collapse
This is a long shot, try Ubuntu/Linux. You can boot into it without installing Linux on your computer and it handles ADB & Fastboot more smoothly. Read and follow FAQ Q5, you must install Ubuntu 12.04 for these procedures to work. If you install the newest version, there are several more steps. Just scroll down the first page and near the bottom there is a link to older versions. If you get fastboot working, then I would try a fastboot erase cache first with fastboot reboot to see if the problem is resolved. If that didn't work then try to get back to bootloader and select factory reset.

majmoz said:
This is a long shot, try Ubuntu/Linux. You can boot into it without installing Linux on your computer and it handles ADB & Fastboot more smoothly. Read and follow FAQ Q5, you must install Ubuntu 12.04 for these procedures to work. If you install the newest version, there are several more steps. Just scroll down the first page and near the bottom there is a link to older versions. If you get fastboot working, then I would try a fastboot erase cache first with fastboot reboot to see if the problem is resolved. If that didn't work then try to get back to bootloader and select factory reset.
Click to expand...
Click to collapse
The problem is that I can't enter the bootloader, so Fastboot won't work.

HeavyHDx said:
The problem is that I can't enter the bootloader, so Fastboot won't work.
Click to expand...
Click to collapse
The other problem is that your phone is not recognized by Windows. If Ubuntu recognizes your phone, then you may be able to use the adb reboot bootloader command. It is a shot in the dark but if it works then great, if not you are in the same place you are now.
If you are S-OFF then try to find a RUU to run, if you are S-ON then you can not run a RUU with an unlocked bootloader.

majmoz said:
The other problem is that your phone is not recognized by Windows. If Ubuntu recognizes your phone, then you may be able to use the adb reboot bootloader command. It is a shot in the dark but if it works then great, if not you are in the same place you are now.
If you are S-OFF then try to find a RUU to run, if you are S-ON then you can not run a RUU with an unlocked bootloader.
Click to expand...
Click to collapse
I don't think using Ubuntu will resolve the "unauthorized"-issue, but It's worth a try, thanks!

Did you try holding the power button under a bright light? Make sure the ambient light sensor (two ports in upper left corner) is exposed.

iElvis said:
Did you try holding the power button under a bright light? Make sure the ambient light sensor (two ports in upper left corner) is exposed.
Click to expand...
Click to collapse
Yep, tried that too, didn't help :/

Has it been stuck at that white screen all this time? You may need to wait until the battery dies and see if it will reboot properly from there.

iElvis said:
Has it been stuck at that white screen all this time? You may need to wait until the battery dies and see if it will reboot properly from there.
Click to expand...
Click to collapse
I left it there for about an hour, no change.
There also isn't anything to boot into, I wiped /system/ and /data/ before unlocking the bootloader.
I was trying to get S-Off and it didn't work with CyanogenMod, so I locked the bootloader and tried to install an RUU and of course, that doesn't work if you don't have S-Off, so I wanted to unlock it again and install a sense based ROM after that, but that's where I got stuck in this bootloop.
In retrospect, it probably was really stupid to wipe those partitions before. Not sure what I was thinking at the time :/
I'll try Ubuntu tomorrow and I'll try it with a brighter light, maybe that works. Otherwise I just have to send it in. Worst that could happen is that they somehow get into the bootloader and discover that it says Tampered, but at that point they can just send it back and with a working bootloader I can fix it myself.

HeavyHDx said:
I left it there for about an hour, no change.
There also isn't anything to boot into, I wiped /system/ and /data/ before unlocking the bootloader.
I was trying to get S-Off and it didn't work with CyanogenMod, so I locked the bootloader and tried to install an RUU and of course, that doesn't work if you don't have S-Off, so I wanted to unlock it again and install a sense based ROM after that, but that's where I got stuck in this bootloop.
In retrospect, it probably was really stupid to wipe those partitions before. Not sure what I was thinking at the time :/
I'll try Ubuntu tomorrow and I'll try it with a brighter light, maybe that works. Otherwise I just have to send it in. Worst that could happen is that they somehow get into the bootloader and discover that it says Tampered, but at that point they can just send it back and with a working bootloader I can fix it myself.
Click to expand...
Click to collapse
Sorry, I was thinking that if you ran it down, then plugged it in, you might be able to get into the bootloader.

Battery's full right now, do you think it will get empty over night?

HeavyHDx said:
Battery's full right now, do you think it will get empty over night?
Click to expand...
Click to collapse
hold the power plus volume down for about 20 seconds when the phone shuts off and comes back on continue holding the buttons till it goes off for a second time. Then let go of power and continue to hold volume down. This has got me into the bootloader many time's. Do this in a well lit room or under a lamp.

HeavyHDx said:
Battery's full right now, do you think it will get empty over night?
Click to expand...
Click to collapse
If it's stuck on the white screen, yeah that should run it down pretty quickly.
But I'm thinking now this might be a bit risky. It will stay on until the battery dies completely instead of shutting down properly. Normally, the system will shut down with a little bit of charge left because if the battery goes completely dead, it may not be able to restart.
I'd try your other ideas first, and if you're ready to return it, give this a shot.

clsA said:
hold the power plus volume down for about 20 seconds when the phone shuts off and comes back on continue holding the buttons till it goes off for a second time. Then let go of power and continue to hold volume down. This has got me into the bootloader many time's. Do this in a well lit room or under a lamp.
Click to expand...
Click to collapse
If I release the power-button when the screen turns black the second time, it just stays off.
It's almost as if the volume-buttons aren't recognized at all :/
@iElvis okay then that'll be my last resort.

HeavyHDx said:
If I release the power-button when the screen turns black the second time, it just stays off.
It's almost as if the volume-buttons aren't recognized at all :/
@iElvis okay then that'll be my last resort.
Click to expand...
Click to collapse
well running the battery dead will not be any different than the shutdown you just did. did you continue to hold volume down and hit the power again after the shut down ? is the usb plugged in this hole time or no?

clsA said:
well running the battery dead will not be any different than the shutdown you just did. did you continue to hold volume down and hit the power again after the shut down ?
Click to expand...
Click to collapse
Yep, I held the button all the time, tried waiting longer and everything, I have already played around with combinations a fair bit before posting this, nothing seemed to work.
Why can't HTC have something like USB Jigs? :/ It's so convenient to just plug this thing in and be in download-mode, regardless how f*cked up your software is.

HeavyHDx said:
Yep, I held the button all the time, tried waiting longer and everything, I have already played around with combinations a fair bit before posting this, nothing seemed to work.
Why can't HTC have something like USB Jigs? :/ It's so convenient to just plug this thing in and be in download-mode, regardless how f*cked up your software is.
Click to expand...
Click to collapse
ok I wish you luck

clsA said:
ok I wish you luck
Click to expand...
Click to collapse
Thanks I just got this thing back from a 2 week repair because the volume-buttons wouldn't work, barely had it a day and now I can send it back again My own fault, but still annoying...

HeavyHDx said:
Thanks I just got this thing back from a 2 week repair because the volume-buttons wouldn't work, barely had it a day and now I can send it back again My own fault, but still annoying...
Click to expand...
Click to collapse
Update:
The place where I sent it to just messaged me this:
http://imgur.com/npdyLgO
I'm curious, how did they manage to get the bootloader working again? Is there another method for getting into the bootloader, other than pressing the buttons?
They want 218€ for fixing it (lol) so I obviously told them to send it back without fixing it, after all I can do that myself if the bootloader works.
Edit:
just got it back, Bootloader works now.

black screen ???

lg g2 vsw980
when i trun on my phone its coming black no logo nothing work
but
if i put it in pc its coming to me many drives
how i fix it ?
i cant see anything its fully black and cant do anythings
how its coming to me like this ?
i install custom recovery and i told twrp goto recovery mode its coming to me like this
please help me to fix it

any idea to fix it ?

What happens if you long press the power button?

if i click on the power its only light and black screen then i dont know be off or on becouse there is no logo

I'm having the same issue. I rooted my phone over a year ago and have been changing ROMs on it. The last one I installed was Cloudy and after a few weeks I noticed my 4g stopped working. Thought it was a SIM card, but it was replaced and Verizon said it's because I'm rooted. I was running some fast boot commands and after one of the(not sure which one) my phone only boots to a black screen. If you hold the power button down you can feel it vibrate like it's turning on but it doesn't, can't boot in to any mode. Once it connects to the pc it maps like 6 drives and it's asking me to Format. Under one drive it has an Image folder with some random files. If you go to device manager it show as qhsusb_bulk. I'm pretty sure I'm screwed. I tried running fastboot via command line, but every command says <waiting for device>. In the meantime I had to switch to my old Thunderbolt.

did you fix it and how to fix it please help me

http://forum.xda-developers.com/showthread.php?t=2582142

smr1619 said:
I'm having the same issue. I rooted my phone over a year ago and have been changing ROMs on it. The last one I installed was Cloudy and after a few weeks I noticed my 4g stopped working. Thought it was a SIM card, but it was replaced and Verizon said it's because I'm rooted. I was running some fast boot commands and after one of the(not sure which one) my phone only boots to a black screen. If you hold the power button down you can feel it vibrate like it's turning on but it doesn't, can't boot in to any mode. Once it connects to the pc it maps like 6 drives and it's asking me to Format. Under one drive it has an Image folder with some random files. If you go to device manager it show as qhsusb_bulk. I'm pretty sure I'm screwed. I tried running fastboot via command line, but every command says <waiting for device>. In the meantime I had to switch to my old Thunderbolt.
Click to expand...
Click to collapse
I'm in the same situation. My screen is black. pressing buttons the phone would vibrate and red led shows but can't get into download nor fastboot mode anymore.

http://forum.xda-developers.com/lg-g2/general/unbrick-lg-g2-qhsusbbulkqualcomm-9006-t2939627

smr1619 said:
http://forum.xda-developers.com/lg-g2/general/unbrick-lg-g2-qhsusbbulkqualcomm-9006-t2939627
Click to expand...
Click to collapse
Thanks for the link but I don't have linux pc

i followed these steps on my phone on a Windows pc. After I got my phone to come up I had to use the lg flash tool and then it updated my phone to the latest andriod OS

any other way to fix my problem ???
please iam doing everything but it not work for me
right now iam install new ubuntu to fix my problem

Soft-Bricked Moto G (2014) won't move beyond Fastboot

Hey guys!
So I've got an issue I'm struggling with on the Moto G (2014). First I'll tell you as much as I can about the phone: I bought it from the Motorola website, so I think it's running whatever the stock firmware is. Also, it's the 8 GB US model and isn't tied to any carrier. (I have it on T-Mobile, but got it directly from Motorola. I was trying to figure out what the firmware is but the closest I've been able to get is by running the Motorola Device Manager app while the phone is in fastboot mode. It says there are no available updates for: 21.11.17.titan_retuaws.retuaws.en.us The bootloader is locked and the phone is not rooted. It's pure stock, though it might have automatically gotten an OTA update to the latest official release, I can't be sure because I bought it for someone else.
Okay, so the problem. I'd bought the phone for my dad and set it up and it worked fine for about two months. Yesterday, he came by my place and asked if I could take a look at it because it was stuck on one screen and since there was no removable battery, he didn't know how to reset it. The screen it was stuck on is the boot screen where the Motorola logo is supposed to come up. It was up, but the bottom half of the logo was stretched to the side and pixelated so my first reaction was "crap, he hit it against something and there's damage to the screen." But there was no visible damage to the screen anywhere (neither from a hard hit or from pressure) and he's got the flip case for it and he said it hadn't been hit or anything.
I tried to power it down by holding down the power button, but as soon as it went off, it tried to start up again. A bootloop that always froze on that messed up Motorola boot screen. I set it on the charger for a bit and let it run through the loop a few times and at one point it got as far as the "world" screen where it shows a cartoon planet. This extended down past where the weird stretch happened on the motorola graphic and it was perfectly clear so I realized there was no damage to the screen, just some sort of boot error.
So then I tried booting into fastboot (hold both volume buttons down along with the power button for a few seconds, release) and I was able to get into fastboot. I tried scrolling down to recovery and then hitting the volume up key to select it but the second I hit the volume up key (the selection key in this mode) it reboots the phone. It doesn't go into the recovery screen, just turns off the phone. I tried this for the "Factory" (reset) option, for the "Normal Powerup" option, and the others. Instead of getting anything different, selecting any of them turns the phone off and nothing happens. The computer is recognizing that there's a device connected to it when I have the phone plugged in via usb in fastboot to my Windows 8 laptop. It also appears that I can enter commands in fastboot. (Though I'm not sure what to put in to fix this so I'm turning to you guys.)
So I can't figure out what's wrong. I've got some experience in flashing roms, both manually and with some of the tools, but haven't had to deal with what I'm assuming is a soft brick before.
Can anyone offer any help?
Thanks very much.

Watch this video and try again
https://www.youtube.com/watch?v=vf2sOPoE2b4

Roldorf said:
Watch this video and try again
https://www.youtube.com/watch?v=vf2sOPoE2b4
Click to expand...
Click to collapse
Unfortunately that didn't work. I was able to click the "restore to factory" part and it seemed to do that but I tried it again with the "wipe cache partition" and it just reset. I tried to restart normally and nothing happened. I will start boot and go to the Motorola logo but will always fail there, no matter what I try.

I'm still stuck with the soft-bricked phone. Any help going from Fastboot to somehow getting it to work?
(As I stated in the OP, the recovery options don't work. It seems only the Fastboot area is working.)

try to reflash the rom via fastboot, using the commands on 4.2 on this thread
if you have fastboot working they must work and re-flash the stock rom and everything back to stock...
to have the XML zip of yours rom search in here and download the file regards yours model and OS version that you wanna...
download, very slow download, unzip, to the some folder of mfastboot and give the commands a try... :good:

This is how to solve *ANY* softbrick on the Moto G 2014 (2nd Gen Moto G)
Try unlocking your bootloader with the given instructions on Motorola's website. You can flash a recovery like TWRP or CWM using mfastboot-v2. After flashing the recovery you can reinstall a custom ROM or stock ROM to fix the soft brick. ADB is only available if you enabled USB debugging although it will allow few commands. Using mfastboot-v2 after unlocking the bootloader will play the main factor in resolving the soft brick.:laugh::good:

eyhajee said:
Try unlocking your bootloader with the given instructions on Motorola's website. You can flash a recovery like TWRP or CWM using mfastboot-v2. After flashing the recovery you can reinstall a custom ROM or stock ROM to fix the soft brick. ADB is only available if you enabled USB debugging although it will allow few commands. Using mfastboot-v2 after unlocking the bootloader will play the main factor in resolving the soft brick.:laugh::good:
Click to expand...
Click to collapse
hello eyhajee.
My Moto G 2014 xt1068, running on Android 5.0.2 has some softbrick issue.
I have unlocked its bootloader, rooted it, unrooted it and while I was trying to lock its bootoader, I forgot to enable USB debugging and now it's stuck on fastboot mode.
So I wanna ask that can flashing a custom ROM turn my phone on??

I think so. If you are able to run some basic commands you should be able to flash it to emergency mode.

Please help me to unbrick my G5S Plus

Hi guys,
I got a G5S+, which got stuck the other day.
It was booting, showing the blue Motorola screen but ended up with a lying down android with a red questionmark and saying 'no command'.
I read through a couple of threads and finally decided, I need to flash stock again.
I did not have switched on USB debugging and so on, as the phone was quite new to me.
I decided to run with that tutorial here:
https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
Which seemed to be the right one.
Said so, booted into bootloader, installed the driver on my Win10 PC and ran through the steps.
I gut stuck on 'fastboot flash system system.img_sparsechunk.3' (15mins waiting..... after the steps before required about 12 Sec each) and needed to disconnect and connect the phone again.
Started with the same command and it worked.
Anyway when I got to the command 'fastboot flash system system.img_sparsechunk.5' I realized in the Potter Retail, there is no such file (neither there is 6 or 7).
I skipped the commands and continued.
When it came to rebooting the phone disconnected and thats it.
Since then I am not able to turn my phone back on.
Sometimes there seems to be a small notofication led showing up when trying to turn on the phone.
And you can hear the USB connect sound when I connect it to my computer.
Did anyone of you guys experience the same issue or has an idea what to do?
I have no idea what I shall so.
Best regards,
Matt

Which stock ROM did you flash? I'm hoping that following that guide, you flashed a stock ROM for sanders (i.e. the codename for Moto G5S Plus) and not for potter (codename for G5 Plus), which appear to be not compatible with each other.
Your original issue appears to be your device is booting into the stock recovery (which the start of is the 'no recovery' screen).
Do you know what model number or retail software channel, or the software build you had on your device before it failed? If so, we may be able to flash the correct sanders stock ROM to your device and get it going again. Another user appears to have gotten their device working when they incorrectly flashed the potter stock ROM and not sanders. https://forum.xda-developers.com/moto-g5s-plus/help/bricked-moto-g5s-plus-t3747064 Ideally you will want to flash the correct stock ROM for your device.

Oha damn you are right.
I am an idiot and tried to flash Potter to a G5S Plus.
Oh boy. I should not flash a cellphone after a long day at work.
I had the latest safety update installed and the latest release.
I am not sure though which software that used to be.
Unbelievable.....
Anyway, so my screen does not show anything anymore.
I guess the display driver dows not work or something like that.
The cellphone is still working I think, as the USB sound still appears.
Does anyone have an idea what to do if the screen stays black.
I still cannot believe it.....
Thanks though for your help!
EDIT: fastboot still reckognizes the phone. I guess this is good.
But the command 'fastboot oem fb_mode_set' runs into an error.
Edit2:
I skipped the first command and everything ran through (with some error messages though).
I hope it works now.
Device is currently rebooting and showing the blue motorola screen.
Lucky me.....

Okay, at least your device is booting now (ish)... I saw your other post and was wondering if you were able to boot from the bootloader.
1)Boot to fastboot (probably easiest by powering off your device, then hold down power and volume down keys until your device boots).
2)Once in the fastboot menu (with details about your device, like bootloader version), check that 'Start' is selected, and press the Power button to select. If 'Start' is not showing, use the volume keys to scroll through the options until 'Start' appears. Sometimes, this booting via fastboot bypasses an auto-boot to recovery mode.
Failing that, if you're on the 'no command' screen, then hold down the power button and tap the volume up key. Release both and it should let you into the recovery menu. Then, you can try to reboot to system.

Hi there,
I ran through all the steps you said.
But I ended up having the same issue. I always get back to the broken droid.
Is there a way to flash a completely new ROM to the device in its current condition?
I don't mind having a customrom, but I want to get it working again.
Thanks!
Matt

I solved my problem:
It was the SD card. I cannot believe it.
I got myself another G5S Plus and swapped everything:
Same issue.
So I removed the memory card and all good again.
I am quite sad though not having figured that out earlier, becoz all my data is lost now....
Thanks for your help though!