Database Info

[Q] No longer able to boot into ClockworkMod Recovery after latest ROM flash.

After flashing the latest ROM I was messing around with (WajkIUI 2.1.6) the phone would crash and reboot within 30 seconds of booting up. The previous ROM that was running was FAUXMIUI_RG2xV2.0.0 (01/08/2011 [v2.0.0]OVERCLOCK) that was stable except for when I’d turn wi-fi on after being off for 8 hours or so phone would reboot.
I figured I would boot into ClockworkMod Recovery and restore one of the nandroid backups, I tried booting into recovery I found out that I could not. When I hold the volume down and press the power button I see the screen that says software update (like when flashing with OneClickRecoveryFlasher).
Whenever I flash a new ROM I will Wipe data/factory reset, wipe cache partition, and then wipe dalvik before installing zip. I’ve always run cyanogenmod nighties; FAUXMIUI_RG2xV2.0.0 was the first MIUI ROM I’ve used.
When I run OneClickRecoveryFlasher, I do not see any errors on the command prompt so I am assuming it was successful, or at least thinks it was.
I tried to Restore LG G2x Stock Recovery using OneClickRecoveryFlasher and then flashing v5.0.2.0 and still no ClockworkMod Recovery, also tried v4.0.1.5 and still no ClockworkMod Recover.
I then tried http://forum.xda-developers.com/showthread.php?t=1248644 and with that I was able to get back to stock 2.3.3, tried to use OneClickRecoveryFlasher to flash ClockworkMod, still no go.
I tried LG Mobile Update and that proceeded to install something, not really sure what the update was, after the update finished, phone rebooted into stock 2.3.3. Shut the phone down and tried to flash ClockworkMod and still nothing.
I did a hard reset following http://mobilephonerepairguides.blogspot.com/2011/04/lg-g2x-hard-reset.html
I also tried http://forum.xda-developers.com/showthread.php?t=1183168, that got me to stock 2.3.3 but I still could not boot in to ClockwordMod Recovery.
I’m having a hell of a time wrapping my head around what I screwed up. Did I somehow destroy the recovery partition, is that possible? Any ideas what I broke and how to fix it? Can I used adb to view the partition table, would that tell me if something was corrupt?
Any help and ideas would be appreciated, I have tried doing my due diligence and I apologize if I missed something obvious.
Thanks,
-Matt

Faux never made a miui
Did you nvflashed recovery? If no then do that first.
NVIDIA NEVER AGAIN!

If you did the LG Updater it returned your phone to stock everything, including recovery. You need to use NVFlash (One Click method okay) to reflash CWM and then you should be good to go.

When the phone is completely off, hold volume down, then hold the power button and don't let go of both until the second lg logo.
If you hold volume down too early it'll give you the software update screen.

Well that's embarrassing, thanks buru898 that did the trick and got me into CWM Recovery. I never remember holding the power button for that long but it worked and I'll remember that for next time.
Thanks

fcisco13 said:
Faux never made a miui
Did you nvflashed recovery? If no then do that first.
NVIDIA NEVER AGAIN!
Click to expand...
Click to collapse
Sorry, I only wrote in the actual zip file name, I meant RG2x-MIUI v2.1.6-MultiLang/Powered by Faux Kernels CM v0.4.8(01/08/2012)[v2.0.0].
Thanks

[Q] Stuck in bootloop, recover files

Hello.
Today my oneplus one was suddenly stuck in bootloop. This happened in the middle of the day when I rebooted my phone. My phone was running the latest update that came OTA (stock lollipop). Whenever I boot my phone it starts loading and suddenly a Chrome (browser) window appears for 1 second and tries to load a website. Afterwards my lock screen pop ups for 1 seconds and it starts to reboot. During the lockscreen I tried to unlock my phone as soon as possible, but it just reboots. (Any ideas about this weird problem?)
I CAN boot it in recovery mode by holding volume-down button and power button.
I CAN boot it in fastboot mode by holding volume-up button and power button.
Perhaps a factory reset will do the trick, but I don't have a backup of my files (because this happened so suddenly without me trying to flash/customize my phone). My first priority is recovering my files, because most solutions will end up in me losing every file. Unfortunately I've found little possibility to do this during the bootloop problem. I've tried to flash TWRP because it could make backups of my phone. I tried it through ADB/Fastboot, but it failed because my device is not unlocked (I can't go to settings and put my phone in developer mode and debugging mode). So I've read somewhere that unlocking my phone (bootloader?) through ADB will wipe my phone, which is exactly what I don't want.
Also I've tried this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
But It also failed because my device was not unlocked.
Did I miss some steps somewhere or did I read something wrong?
Hopefully anybody has an idea to either fix the bootloop without losing my data, or finding a way to recover my files before wiping the phone.
Thank you.

RightHanded said:
Hello.
Today my oneplus one was suddenly stuck in bootloop. This happened in the middle of the day when I rebooted my phone. My phone was running the latest update that came OTA (stock lollipop). Whenever I boot my phone it starts loading and suddenly a Chrome (browser) window appears for 1 second and tries to load a website. Afterwards my lock screen pop ups for 1 seconds and it starts to reboot. During the lockscreen I tried to unlock my phone as soon as possible, but it just reboots. (Any ideas about this weird problem?)
I CAN boot it in recovery mode by holding volume-down button and power button.
I CAN boot it in fastboot mode by holding volume-up button and power button.
Perhaps a factory reset will do the trick, but I don't have a backup of my files (because this happened so suddenly without me trying to flash/customize my phone). My first priority is recovering my files, because most solutions will end up in me losing every file. Unfortunately I've found little possibility to do this during the bootloop problem. I've tried to flash TWRP because it could make backups of my phone. I tried it through ADB/Fastboot, but it failed because my device is not unlocked (I can't go to settings and put my phone in developer mode and debugging mode). So I've read somewhere that unlocking my phone (bootloader?) through ADB will wipe my phone, which is exactly what I don't want.
Also I've tried this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
But It also failed because my device was not unlocked.
Did I miss some steps somewhere or did I read something wrong?
Hopefully anybody has an idea to either fix the bootloop without losing my data, or finding a way to recover my files before wiping the phone.
Thank you.
Click to expand...
Click to collapse
Unfortunately you might be stuck in a catch-22 situation here. In order to access the files you'd need to unlock the bootloader, but in doing so you'd lose those files. Without usb debugging already enabled I can't see a way out of this.

Decided to unlock the bootloader through ADB. (bye bye data)
After I've unlocked it, I've tried installing TWRP.
Some minor problems occured but I can finally boot into TWRP through volume-down button + power button.
I've decided to download the stock ROM i've found on the OPO forums.
Couldn't acces my phone through normal methods, so I had to use ADB to push the files into my phone.
Installing the file through TWRP, wiped cache/dalvik and installed super user before rebooting.
After rebooting my phone is stuck on the boot screen now. (This also happened before I installed TWRP on my phone)
I've also tried this method: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also no succes. I'm stuck in the bootscreen where it says 'cyanogen'.
EDIT: Managed to fix it eventually through: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061 (part 2) writing the command in TWRP.
Phone finally boots normally again.

RightHanded said:
Decided to unlock the bootloader through ADB. (bye bye data)
After I've unlocked it, I've tried installing TWRP.
Some minor problems occured but I can finally boot into TWRP through volume-down button + power button.
I've decided to download the stock ROM i've found on the OPO forums.
Couldn't acces my phone through normal methods, so I had to use ADB to push the files into my phone.
Installing the file through TWRP, wiped cache/dalvik and installed super user before rebooting.
After rebooting my phone is stuck on the boot screen now. (This also happened before I installed TWRP on my phone)
I've also tried this method: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also no succes. I'm stuck in the bootscreen where it says 'cyanogen'.
Any other way to fix this problem?
Click to expand...
Click to collapse
Exactly what did you flash? Full filename please. No errors occurred?

Heisenberg said:
Exactly what did you flash? Full filename please. No errors occurred?
Click to expand...
Click to collapse
Hopefully the stock cyanogen OS.
First I've tried to flash cyanogenmod 12 through TWRP (file is found here: https://forums.oneplus.net/threads/cm12s-yng1tas17l-installation-guide-review-change-log.304615/)
Afterwards I was still stuck in bootscreen, so I've looked for another solution.
Which made me find this guide: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
After flashing this file (probably the same thing) the problem still remained.
Eventually after multiple wipes/factory resets (which did not solve the problem) I've entered the command in TWRP and after reboot it finally worked again.
So I basically flashed my phone twice, once through TWRPS and the other through the batch file (perhaps ADB?).
Also no errors occured which stopped the flashing and commands. Did have to reinstall TWRP and reboot instantly in it by holding the volume down button multiple times. This doesnt happen anymore though.
Only had to install google apps for CM12 (gapps), for which I used TWRP in recovery mode.
Currently reinstalling most apps on my phone and no problems yet.

[Q] Can't boot into recovery?

So, I got my new OnePlus One today and I tried to get CM12 onto it. I was following the [GUIDE] How to Install CM12 on the OnePlus One- Android Lollipop/5.0 on the OPO forums, and everything went well until I tried to get the TWRP on there. I flashed the recovery and rebooted the phone. I turned it off and then tried to boot it into recovery but it doesn't, it just hangs at the OPO logo until I hard-restart it.
I've tried factory resetting it and doing
fastboot oem unlock
but nothing happened. The factory reset pretty much just reset the phone. I think I might've messed up the kernel. How do I fix it?
EDIT 1: I've tried reflashing twrp recoveries and nothing. When I hold power+volume down, it powers on, shows the one plus logo, then reboots and just goes to the lockscreen.
UPDATE 1: I managed to manually flash all the CM12 files and use lollipop. I haven't tried the recovery yet but I'll keep you guys updated (if any of you even care).
UPDATE 2: Apparently flashing CM12 made the recovery work. Everything works as it should and the OTA to the most recent CM12 worked perfectly.

You're probably doing the button combo wrong. Hold volume down, then hold power (so you're holding them together), when you see the boot logo let go of power but keep holding volume down until you reach recovery.

Heisenberg said:
You're probably doing the button combo wrong. Hold volume down, then hold power (so you're holding them together), when you see the boot logo let go of power but keep holding volume down until you reach recovery.
Click to expand...
Click to collapse
I was curios and enabled advanced reboot to try and boot into recovery and it worked (after I had flashed CM12). Everything's working now.

SDCore said:
UPDATE 1: I managed to manually flash all the CM12 files and use lollipop. I haven't tried the recovery yet but I'll keep you guys updated (if any of you even care).
Click to expand...
Click to collapse
How did you manually flash CM12? I think I'm having the same trouble you were having. I used the oneplus toolbox from the forum to unlock the bootloader, then flash the TWRP, but no luck in getting into recovery mode. It just boot loops with the oneplus logo until I release the volume down button at which point it then boots to the lock screen.

Heisenberg said:
You're probably doing the button combo wrong. Hold volume down, then hold power (so you're holding them together), when you see the boot logo let go of power but keep holding volume down until you reach recovery.
Click to expand...
Click to collapse
@Heisenberg I'm also having trouble getting into recovery. I've tried the different button combos (power + vol down; power + vol down and release power) as well as the advance reboot options to get into recovery, but they all fail. I get the 1+ logo and after I let go of the volume down button the screen goes black and boots again to the 1+ screen and then to the lockscreen. It's almost like it doesn't recognize the recovery. I tried putting the stock recovery back on using the image in the OnePlus One toolkit folder, but that one doesn't work either. In addition to unchecking the "CM Recovery Update", are there any other settings that could be causing problems?
For background info, I initially used the toolkit interface to unlock the bootloader and then flash the recovery. The bootloader unlocked with no issue...it wiped my device and I was in sync with the "How to root" video posted by alex.inthi. I got sidetracked after the (seemingly) successful flash of TWRP onto the phone I kept getting booted into the Cyanogen recovery. I realized out that I needed to uncheck the setting to keep it from overwriting TWRP and after that was not able to boot into recovery. After finding your beginners guide (thanks, by the way, very well written) I tried using fastboot from the command line as you show, but still no luck.
Thanks in advance for any help...

bellino13 said:
I used the oneplus toolbox from the forum to unlock the bootloader, then flash the TWRP, but no luck in getting into recovery mode. It just boot loops with the oneplus logo until I release the volume down button at which point it then boots to the lock screen.
Click to expand...
Click to collapse
bellino13 said:
@Heisenberg I'm also having trouble getting into recovery. I've tried the different button combos (power + vol down; power + vol down and release power) as well as the advance reboot options to get into recovery, but they all fail. I get the 1+ logo and after I let go of the volume down button the screen goes black and boots again to the 1+ screen and then to the lockscreen. It's almost like it doesn't recognize the recovery. I tried putting the stock recovery back on using the image in the OnePlus One toolkit folder, but that one doesn't work either. In addition to unchecking the "CM Recovery Update", are there any other settings that could be causing problems?
For background info, I initially used the toolkit interface to unlock the bootloader and then flash the recovery. The bootloader unlocked with no issue...it wiped my device and I was in sync with the "How to root" video posted by alex.inthi. I got sidetracked after the (seemingly) successful flash of TWRP onto the phone I kept getting booted into the Cyanogen recovery. I realized out that I needed to uncheck the setting to keep it from overwriting TWRP and after that was not able to boot into recovery. After finding your beginners guide (thanks, by the way, very well written) I tried using fastboot from the command line as you show, but still no luck.
Click to expand...
Click to collapse
Okay, I must have been having a special kind of moment - I've got TWRP 2.8.7.0 running on my handset now. I may have been holding the volume down button too long, or it may be that I was using an older version of TWRP, but I'm going to go with the former. I've also been able to successfully flash and boot into Philz 6.59.2

Having the same problem
I am having the exact same problem and cannot seem to find a solution. Recovery screen just doesn't appear, but goes to lockscreen.
Tried erasing, flashing both twrp, philz etc., but nothing works. The phone doesn't recognize the recovery status. Advanced booting does the same.
Update CM-recovery is checked off, phone is unlocked. I've followed every step of the big guide down to every detail.
Is manually flashing the 12.1 ROM the only way and in that case: is it hard for a relative newcomer?

stuck in loop, possibly a different kind of loop

I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.

atomkrieg said:
I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.
Click to expand...
Click to collapse
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk

soupysoup said:
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.

atomkrieg said:
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.
Click to expand...
Click to collapse
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk

soupysoup said:
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
in the end fastboot, since i coulndt see how i could copy the img over to install via twrp
im pretty sure the button is fine, since it was cycling from the ota update install, then was working fine unlocking the bootloader, but after the flash, it crapped the bed.

Different problem
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go

siddhu007 said:
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go
Click to expand...
Click to collapse
ok, took it into a shop, got the power button fixed. It must have been on the way out because literally one minute it worked and the second it didnt. now i think ive got it narrowed down. it's saying it's unable to mount /persist. ive tried the various fixes:
e2fsck/dev/block/platform/msm_sdcc.1/by-name/persist
and
make_ext4fs/dev/block/platform/msm_sdcc.1/by-name/persist
but all i get is a not found error. not sure what to do from here on.

success!! i ended up stumbling on a bit how to restore the persist partition i didnt try. got a custom rom installs and everything works. thanks to everyone who tried to help!!

stuck in bootloop while flashing cataclysm rom
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..

When it was stuck in the loop, I had to hold vol up and down with the power button (wait a few secs until it was completely off) then reboot holding down + power till it opened the bootloader. if that doesnt work, try reflashing the bootloader via fastboot. I only found out i couldnt mount the persist partition by looking at the terminal window in twrp after trying to install a rom which kept it in the boot loop. I then used the cmd: make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist to rebuild it.

jpau11 said:
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..
Click to expand...
Click to collapse
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.

audit13 said:
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.
Click to expand...
Click to collapse
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!

jpau11 said:
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!
Click to expand...
Click to collapse
Great to hear it. Congratulations:good:

Phone is not power up?

I flashed cwm recovery over TWRP from this link below . now phone is not power on?
http://androidhost.org/hUhuh
Any suggestion. :crying:

sanrajbhar said:
I flashed cwm recovery over TWRP from this link below . now phone is not power on?
http://androidhost.org/hUhuh
Any suggestion. :crying:
Click to expand...
Click to collapse
Press volume down while powering on. Does the bootloader appear? If it does, use
Code:
fastboot flash recovery NAMEOFTWRPIMAGE.img
Code:
fastboot boot NAMEOFTWRPIMAGE.img
Backup your data, reboot to bootloader and flash stock ROM before proceeding to flash a custom ROM (or try flashing the custom one directly).

xMotoDA said:
Press volume down while powering on. Does the bootloader appear? If it does, use
Code:
fastboot flash recovery NAMEOFTWRPIMAGE.img
Code:
fastboot boot NAMEOFTWRPIMAGE.img
Backup your data, reboot to bootloader and flash stock ROM before proceeding to flash a custom ROM (or try flashing the custom one directly).
Click to expand...
Click to collapse
I tried volume down with power button but it does not working, no bootloader or sceen on. can I assume now nothing can be done.
My phone was rooted and installed with AOSP rom .

sanrajbhar said:
I tried volume down with power button but it does not working, no bootloader or sceen on. can I assume now nothing can be done.
My phone was rooted and installed with AOSP rom .
Click to expand...
Click to collapse
I have a similar issue, as my phone also cannot turn on and I have TWRP recovery.
I had rooted my phone with SuperSU and unlocked the bootloader via motorola's tool. But then due to SafetyNet, apps such as Snapchat wouldn't work (cant log in), and I couldn't download Netflix (totally a huge issue).
So I decided to try switching to Magisk instead, as I heard that uses systemless root that doesnt trip Safety Net. While uninstalling SuperSU (using the built in feature for full removal), I was able to uninstall SuperSU and unroot my phone, but was not able to restore the stock boot image in the process. It was at this point I made a NANdroid backup in case I stuffed anything up.
Because of this, I was unable to flash Magisk via the TWRP recovery, so I downloaded a previous version of the firmware from January to flash back to from here. After flashing this and also wiping the user data, my phone booted up fine and worked, and appeared to be in normal condition.
However, then I elected to download and install the firmware update. This all went well, and was installing, until just at the end of the process, when the phone turned off. It had over 60% battery at the time.
At this point in time I'm still unable to get it to boot up, even into recovery or fastboot mode, so I cant really do anything, or restore my NANdroid backup.
If I plug it into my laptop, and hold the power + volume button down for a period of time, I can hear the USB connected tone (Windows 10), which then switches to a disconnected tone and a "USB device malfunctioned" error message pops up.
I tried leaving it unplugged all of last night just in case it was stuck in a boot loop or something so the screen couldn't display anything, in order to flatten the battery, but obviously I couldn't tell any difference. I'm currently now trying to have it plugged into power for an extended period of time just in case it is actually just flat. The current condition is just a black screen as if there was no power at all, with no lights or anything, regardless of a charger being connected, with the buttons not doing anything (I've attempted holding down the power and volume down buttons together for at least 2 minutes to no effect)
Any help would be greatly appreciated.
My specs: Moto G Turbo (2015), model XT1557, running Android 6.0.1. Can't remember exactly, but it previously had the latest firmware available before I tried flashing the January firmware.