Database Info

[Q] SOLVED Problem flashing CyanogenMod 9.1.0 Stable

I rooted my MT4GS a few months ago but stuck with the stock ROM. I decided I wanted to try out the CyanogenMod 9.1 ICS ROM. I followed the following steps:
1) Installed ROM Manager.
2) ROM Manager indicated a newer version of ClockworkMod Recovery and I installed it (5.0.2.7).
3) Using ROM Manager, did a full backup of the current ROM. All went well.
4) Using ROM Manager, downloaded and installed CyanogenMod 9.1.0 stable-doubleshot. I specified to wipe the data and cache partitions. The installation seemed to go normally.
When the phone rebooted, it was stuck at the logo screen. Had to remove the battery to turn it off. Tried a couple times, still the same.
Since I had the backup, I decided I would use CWM to restore the old ROM.
When I boot into recovery mode, it shows CWM 5.0.2.7, but whatever option I try to choose from the recovery menu, The screen just goes blank with the CWM logo in the middle and nothing else happens. Hitting the power button returns me to the menu, but no option works, even power down or reboot. It just goes back to the CWM logo again and I have to remove the battery to shut it down.
So, I thought I would try using fastboot to flash the ROM again. When I boot the phone into the boot loader and select fastboot, then plug the phone in via USB, nothing happens. Windows does not see the phone and ADB or fastboot don't see it either. It's not a driver issue, as the computer is still setup from when the computer was rooted and I connect the phone all the time with no problems.
When the phone is off and plugged into USB or the charger, I still get the charging light, though it goes off after about 10 seconds, then comes back on and cycles like that.
Is there anything I can try at this point, or is my phone bricked? It seems like I followed all the steps correctly. Is there an update.zip I can put in the root folder and see if it picks it up?
Any help would be appreciated.

brucehvn said:
I rooted my MT4GS a few months ago but stuck with the stock ROM. I decided I wanted to try out the CyanogenMod 9.1 ICS ROM. I followed the following steps
...
Click to expand...
Click to collapse
Ok, after rebooting Windows, I was able to get the USB connection to the phone to work in fastboot. It seems I missed the step described in this thread:
http://forum.xda-developers.com/showthread.php?t=1508556
which states with S-ON you must flash the boot.img separately. I did that via fastboot and the phone boots into cyanogenmod now.
However, I still seem to have the issue with clockwordmod recovery. As long as I do the recovery functions from rom manager, everything is fine, but when I manually boot into the recovery menu, I get the same behavior of any choice from the menu just blanks the screen except for the CWM logo and nothing happens. I tried reflashing the recovery image using fastboot, but still no go.

brucehvn said:
However, I still seem to have the issue with clockwordmod recovery. As long as I do the recovery functions from rom manager, everything is fine, but when I manually boot into the recovery menu, I get the same behavior of any choice from the menu just blanks the screen except for the CWM logo and nothing happens. I tried reflashing the recovery image using fastboot, but still no go.
Click to expand...
Click to collapse
This is solved also. Seems on the MT4GS, the trackball is the selection button. The power button appears to only be a back button.

What a thread! Two nicely phrased problem definitions, two well explained solutions, and all from the same guy. Sorry we weren't able to help directly, but you obviously found the answers you needed elsewhere in the forum. And you updated the title as well to show it was solved. Thanks.

[Q] Recovery Boot Loop Problem

Had a problem. Hope someone with experience can give me a few answers.
Nave new t-mobile Note 3, SM-N900T. Stock 4.4.2 KitKat Touchwiz rooted.
Rooted to enable SDFix to use SD card as I want to use it.
Everything great! No problems.
Thought it would be wise to have a Nanoid backup.
Opened Rom Manager and made One change in prefrences. I set it for external SD card storage. (mistake?)
Went to 'Backup current Rom' in Rom manager, started it and it started to reboot. Shut down and restarted in a 'Recovery' boot loop??
No matter what I did, Tried holding power, up volume and home button, nothing. Boot loop continued. Removed battery, waited, as soon as I re-installed battery it instantly went back into recovery boot loop.
I don't know what I did, I kept removing battery and trying again and again and all of a sudden, it booted up back to KitKat and now everything is working great again. No problem on any standard reboot.
What happened? I have used this same set up on my S3 and never had a problem.
I would like to backup the current setup for any future problems. But now, I'm afraid to even try.
I removed Rom Manager and re-installed. Made sure that the storage location was reset to internal and it should be OK??
What did I do when I got out of the Recovery boot loop??
So, afraid to try again. Don't want the boot loop again.

rspilot1 said:
Had a problem. Hope someone with experience can give me a few answers.
Nave new t-mobile Note 3, SM-N900T. Stock 4.4.2 KitKat Touchwiz rooted.
Rooted to enable SDFix to use SD card as I want to use it.
Everything great! No problems.
Thought it would be wise to have a Nanoid backup.
Opened Rom Manager and made One change in prefrences. I set it for external SD card storage. (mistake?)
Went to 'Backup current Rom' in Rom manager, started it and it started to reboot. Shut down and restarted in a 'Recovery' boot loop??
No matter what I did, Tried holding power, up volume and home button, nothing. Boot loop continued. Removed battery, waited, as soon as I re-installed battery it instantly went back into recovery boot loop.
I don't know what I did, I kept removing battery and trying again and again and all of a sudden, it booted up back to KitKat and now everything is working great again. No problem on any standard reboot.
What happened? I have used this same set up on my S3 and never had a problem.
I would like to backup the current setup for any future problems. But now, I'm afraid to even try.
I removed Rom Manager and re-installed. Made sure that the storage location was reset to internal and it should be OK??
What did I do when I got out of the Recovery boot loop??
So, afraid to try again. Don't want the boot loop again.
Click to expand...
Click to collapse
Hi. What recovery are you using?
If you haven't installed a custom recovery, then that explains your issue. Basically, the app scheduled a custom recovery script which kept failing in the stock recovery. You should normally be able to reboot into the system holding the power button, thus skipping going to recovery. This also resets the recovery script so everything is back to normal.
Nandroid is normally only possible using a custom recovery like TWRP or CWM.
I saw that you might be able to perform a Nandroid without restarting the phone (so without a custom recovery) using this app: https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup&hl=en
I have never tried it. Looks promising though.
But please note that you won't be able to restore the backup without a custom recovery.
EDIT: If you do have a custom recovery, why not boot in recovery mode and make the backup from there?
Cheers

Recovery Boot Loop Problem
I have CWM installed. Setup thru Rom Manager as I have done before on other phones.
Tried it again, same thing. Over and over. Constant reboot. Dosen't matter if I hold the power button or try different ways, same thing.
It says: Recovery booting
Recovery is not seandroid enforcing
Set warranty bit:recovery
If I remove battery and wait a couple of minutes, I can install battery and it dosen't start till I hold power button.
So I held volume down, home button and power button and booted into download mode. From there I cancelled and it rebooted normally.
Everything I've read on boot loops always say 'boot into recovery'. I only wish I could. That's the bootloop.
Any idea on what's wrong?
Thank you for your time and trouble.

rspilot1 said:
I have CWM installed. Setup thru Rom Manager as I have done before on other phones.
Tried it again, same thing. Over and over. Constant reboot. Dosen't matter if I hold the power button or try different ways, same thing.
It says: Recovery booting
Recovery is not seandroid enforcing
Set warranty bit:recovery
If I remove battery and wait a couple of minutes, I can install battery and it dosen't start till I hold power button.
So I held volume down, home button and power button and booted into download mode. From there I cancelled and it rebooted normally.
Everything I've read on boot loops always say 'boot into recovery'. I only wish I could. That's the bootloop.
Any idea on what's wrong?
Thank you for your time and trouble.
Click to expand...
Click to collapse
Have you tried booting directly into recovery?
So just shut off your phone and then open it by holding volume up + home + power. It should boot into recovery. If it doesn't, I recommend installing cwm or TWRP using Odin instead of Rom manager.
Might be a problem with your current recovery.
Sent from my GT-I9505

Recovery Boot Loop Problem
andreiav said:
Have you tried booting directly into recovery?
So just shut off your phone and then open it by holding volume up + home + power. It should boot into recovery. If it doesn't, I recommend installing cwm or TWRP using Odin instead of Rom manager.
Might be a problem with your current recovery.
Sent from my GT-I9505
Click to expand...
Click to collapse
Yes, I tried. Does the same thing.
I've never used Odin. All the info I've read mentioned downloading USB drivers and using different .tar files. Checking this and that.
Nothing I've ever done.
No experience with it.
Never had a reason before to use it.
Every instruction website I've read all seem to be different.
I'm gonna have to find out, huh? lol
I've got Odin on my computer, and have the CWM 6 zipped file.
Will do some research.
Thanks

rspilot1 said:
Yes, I tried. Does the same thing.
I've never used Odin. All the info I've read mentioned downloading USB drivers and using different .tar files. Checking this and that.
Nothing I've ever done.
No experience with it.
Never had a reason before to use it.
Every instruction website I've read all seem to be different.
I'm gonna have to find out, huh? lol
I've got Odin on my computer, and have the CWM 6 zipped file.
Will do some research.
Thanks
Click to expand...
Click to collapse
No problem.
A few tips with odin:
-If you have Kies installed, you don't need to install other drivers.
-The file you flash with Odin should have tar or tar.md5 extension
-you have to activate USB debugging from developer options.
-boot your phone into download mode
-run Odin as administrator
-connect your phone. you should see the text Added in Odin. If don't see it, you need drivers.
-you should make sure only auto reboot and f. Reset time are checked
-you should put the file in Pda or Ap(if using latest version)
Click start and wait until it finishes. It will restart itself if you checked auto reboot.
That's about it. It's very safe and easy to use.
Watch some videos on YouTube. You will definitely find some.
Cheers
Sent from my GT-I9505

Recovery Boot Loop Problem
andreiav said:
No problem.
A few tips with odin:
-If you have Kies installed, you don't need to install other drivers.
-The file you flash with Odin should have tar or tar.md5 extension
-you have to activate USB debugging from developer options.
-boot your phone into download mode
-run Odin as administrator
-connect your phone. you should see the text Added in Odin. If don't see it, you need drivers.
-you should make sure only auto reboot and f. Reset time are checked
-you should put the file in Pda or Ap(if using latest version)
Click start and wait until it finishes. It will restart itself if you checked auto reboot.
That's about it. It's very safe and easy to use.
Watch some videos on YouTube. You will definitely find some.
Cheers
Sent from my GT-I9505
Click to expand...
Click to collapse
Thank you, that answered some questions.
you've been a great help.

Recovery Boot Loop Problem
rspilot1 said:
Thank you, that answered some questions.
you've been a great help.
Click to expand...
Click to collapse
Update: The install of CWM with Odin seemed to be successful. Still have same problem.
I believe the problem must be somewhere else.
Something is stopping the recovery boot. More research ahead.
When I find out more, will post here and give update.

rspilot1 said:
Update: The install of CWM with Odin seemed to be successful. Still have same problem.
I believe the problem must be somewhere else.
Something is stopping the recovery boot. More research ahead.
When I find out more, will post here and give update.
Click to expand...
Click to collapse
Strange. You could try TWRP instead of CWM. I use TWRP and really like it:
Here is the download link for your device: http://www.techerrata.com/file/twrp2/hltetmo/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
This is the Odin flashable recovery.
Here is TWRP page: http://teamw.in/project/twrp2/
EDIT: One more thing. Are these the exact steps you are following when booting into recovery?
"To access recovery mode on your Note 3, turn off the device and press Volume Up+Home+Power buttons at the same time for about 4-6 seconds. When the screen lights up and you see the Samsung logo, release the Power button but keep Volume Up+Home keys pressed until you see the recovery menu screen"
Cheers

Recovery Boot Loop Problem
andreiav said:
Strange. You could try TWRP instead of CWM. I use TWRP and really like it:
Here is the download link for your device: http://www.techerrata.com/file/twrp2/hltetmo/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
This is the Odin flashable recovery.
Here is TWRP page: http://teamw.in/project/twrp2/
EDIT: One more thing. Are these the exact steps you are following when booting into recovery?
"To access recovery mode on your Note 3, turn off the device and press Volume Up+Home+Power buttons at the same time for about 4-6 seconds. When the screen lights up and you see the Samsung logo, release the Power button but keep Volume Up+Home keys pressed until you see the recovery menu screen"
Cheers
Click to expand...
Click to collapse
Yes, if I use the buttons, the download mode comes up saying 'Boot failed'. That's holding the vol. button 'up'. If I hold vol. down, it loads download mode correctly.
If I try to enter recovery thru Rom Manager, Recovery tries to start and the boot loop starts. ??
I may try TWRP. I've heard a lot about it.
Thanks for the links.

Recovery Boot Loop Problem
rspilot1 said:
Yes, if I use the buttons, the download mode comes up saying 'Boot failed'. That's holding the vol. button 'up'. If I hold vol. down, it loads download mode correctly.
If I try to enter recovery thru Rom Manager, Recovery tries to start and the boot loop starts. ??
I may try TWRP. I've heard a lot about it.
Thanks for the links.
Click to expand...
Click to collapse
Is changing over to TWRP as simple as installing CWM on Odin??
Just install and try?

rspilot1 said:
Is changing over to TWRP as simple as installing CWM on Odin??
Just install and try?
Click to expand...
Click to collapse
Yep. 5 minutes process at most
Sent from my GT-I9505

Recovery Boot Loop Problem
andreiav said:
Yep. 5 minutes process at most
Sent from my GT-I9505
Click to expand...
Click to collapse
Success!! TWRP works!!
Installed with Odin and it started up fine. Backed up system on my Ext. SD card and rebooted back to OS.
Perfect!
Don't know what happened to CWM but problem is solved thanks to your help.
If your ever in Winter Haven, Fl area, I'll buy you a steak dinner.
Thank you.

rspilot1 said:
Success!! TWRP works!!
Installed with Odin and it started up fine. Backed up system on my Ext. SD card and rebooted back to OS.
Perfect!
Don't know what happened to CWM but problem is solved thanks to your help.
If your ever in Winter Haven, Fl area, I'll buy you a steak dinner.
Thank you.
Click to expand...
Click to collapse
Awesome! Really glad it worked.
Cheers!
Sent from my GT-I9505

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:

[EMERGENCY] Bricked Nexus 5 Cant Boot Into Recovery Mode

Hi there, having just the old casual phone crisis. I was running cyanogenmod 12.1 for awhile and decided to finally upgrade to a nougat 7.1 build.
I tried using this one https://forum.xda-developers.com/google-nexus-5/development/rom-dark-rom-t3492150 using adb sideload as I had tried a earlier one and the gapps messed up so I wasn't able to put twrp back on the phone. The rom said it had installed successfully but I wasn't able to sideload gapps, I kept getting an error status 255. I went ahead and just tried to load the rom without gapps and see if I could install it slowly through APKs. I managed to get past the initial android load and the services started up, and it got in an endless crash loop because the phone service wouldn't start. So I went to try and flash another rom and was going to delete the cache. When I went to delete the cache the phone hung for about an hour so I tried to just reset it into recovery mode again.
Now when I hold the power button and volume down key to into fastboot mode I can. I have access to the initial screen with the four options, but when I try to start recovery mode or start the phone my screen goes black, and it'll flash the dead android symbol with the error saying unable to mount cache, it only flashes it for like half a second then goes black and repeats every 10-15 seconds.
I tried holding power down, doing volume up, and letting go to do a hard factory reset but it does nothing. I also can't seem to access the adb sideloading anymore, I'm very scared that it's hard bricked, is there anything I can do at all to fix this.

Flash a new version of the recovery via fastboot. Then do a full wipe. After that install the ROM only! Reboot recovery (not system but recovery) then reflash the ROM (no wipe) and add everything else. Hope this helps you out.

The phone may not boot the ROM without wiping data if installing a 7.1 ROM over a 5.1.1 ROM.

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.