Database Info

Nexus 5 won't boot and won't make a backup in TWRP

Hi!
So my Nexus 5 ran into a problem. In the morning it worked fine and I shut it off when I came to school. When I tried powering it back on it showed the PIN entry screen but soon shut off. I tried turning it back on for a couple of times and it showed just that boot animation with color circles. But every once in a while the screen turned white and then continued with the animation. It looked like it was missing a frame or something. Now it just won't boot to Android. It shows the Google logo but it stays there. If it is unplugged it will shut off soon, but if it is connected to my computer it is just stuck there.
I can access TWRP 2.6.3.4 I have on my phone through fastboot but that's kinda it. I searched for a while and found the best thing to do is to restore the phone. But first I want to do a backup (I don't have any, but I will have them from now on). I have some photos on my phone I want to keep. Here comes the next problem: I am unable to do a backup. When I tap backup in TWRP I have checked System, Data and Boot. I slide to back up but it shows some errors:
Updating partition details...
E: Unable to open '/cache/recovery/.version
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/persist'
E: Unable to mount '/firmware'
E: Unable to mount '/system'
* Total number of partitions to back up: 3
* Total size of all data: 2651MB
* Availible space: 14544MB
[BACKUP STARTED]
* Backup Folder: /data/media/0/TWRP/BACKUPS/04
E: Unable to create folder: /data/media/0/TWRP
E: Failed to make backup folder.
The last three lines, except the last one are cut off (I think). If I tap on reboot system shown under this windows it asks me if I want to install Super-SU as if I wasn't rooted. It says so.
So, what to do? I want to keep everything the same (settings, apps, photos...) I have music on my computer so I don't need to back it up. Is that possible? What seems to be the problem?
I am running Android 4.4.2 Kitkat on my Nexus 5 32gb from Canada. I live in Europe and my uncle from Canada bought it, so warranty is no good for me.

First of all clear cache/dalvic cache and try rebooting the phone and see whether OS is booted or not. If that doesn't help, flash the lastet Philz touch recovery and see whether the partitions are being mounted or not...
Since you're able to get to the bootloader, it's a soft brick.. .

Ok, thanks... I am pretty new to android I have no idea how to clear cache. Do I go to wipe then to advanced wipe and check cache and dalvik cache and wipe it so? What if I also clear data? Does that delete everything on my phone?
Edit: So I did that. It says wipe was successful. Here is the log:
Updating partition details...
E: Unable to open '/cache/recovery/.version'
Wiping Dalvik Cache Directories...
Cleaned: /data/dalvik-cache...
-- Dalvik Cache Directories Wipe Complete!
Formatting Cache using make_ext4fs function.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount '/firmware'
My phone still only shows the Google screen and turns off soon (10 seconds or so). What is that Philz thingy?

hofko said:
Ok, thanks... I am pretty new to android I have no idea how to clear cache. Do I go to wipe then to advanced wipe and check cache and dalvik cache and wipe it so? What if I also clear data? Does that delete everything on my phone?
Click to expand...
Click to collapse
Go to mount and check the cache and data. Then go to Wipe>advanced wipe>dalvik cache and cache
and if u clear data it will clear the apps but not what is in the internal memory.
Edit- do as @rootSU is saying.

Sometimes a simple fastboot flash cache.img fixes it
Sent from my Nexus 5 using Tapatalk

rootSU said:
Sometimes a simple fastboot flash cache.img fixes it
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
So, how do I do that? I tried googling it for a bit and I find everything a bit confusing. I want to be sure what am I doing with my phone when it is in this state.
Edit: I tried what varuntis1993 said and it showed that boot animation and shut off. It did that only once. I don't know.

@hofko this thread may help.

hofko said:
So, how do I do that?
Click to expand...
Click to collapse
If you're rooted, you should already know how to do this as you use fastboot during the rooting process.
Read the stickies in general and q&a. Together they contain all the information you need
Sent from my Nexus 5 using Tapatalk

Ok, I want through those threads and found out how to flash cache.img. But my phone is still not working. The first time it showed the boot animation with some white lines going through the screen sometimes as I described earlier. It shut off soon. Now it shows the boot animation for a bit, gets stuck on it and shuts off after a while.
When flashing it shows this:
erasing 'cache'
OKAY [ 0.480s]
sending 'cache' (133348 KB)...
OKAY [ 0.751s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 45.242s
Is there anything else I can do? Can I just get the pictures off my phone and install stock KitKat on it?

hofko said:
Ok, I want through those threads and found out how to flash cache.img. But my phone is still not working. The first time it showed the boot animation with some white lines going through the screen sometimes as I described earlier. It shut off soon. Now it shows the boot animation for a bit, gets stuck on it and shuts off after a while.
When flashing it shows this:
erasing 'cache'
OKAY [ 0.480s]
sending 'cache' (133348 KB)...
OKAY [ 0.751s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 45.242s
Is there anything else I can do? Can I just get the pictures off my phone and install stock KitKat on it?
Click to expand...
Click to collapse
can u access ur internal memory using the file manager of twrp?
Try using adb pull
or u can also use an otg cable and copy and paste the folder to usb.

hofko said:
Ok, I want through those threads and found out how to flash cache.img. But my phone is still not working. The first time it showed the boot animation with some white lines going through the screen sometimes as I described earlier. It shut off soon. Now it shows the boot animation for a bit, gets stuck on it and shuts off after a while.
When flashing it shows this:
erasing 'cache'
OKAY [ 0.480s]
sending 'cache' (133348 KB)...
OKAY [ 0.751s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 45.242s
Is there anything else I can do? Can I just get the pictures off my phone and install stock KitKat on it?
Click to expand...
Click to collapse
It is a dead flashchip. RMA it.
Tapatalk-kal küldve az én Nexus 5-el

bitdomo said:
It is a dead flashchip. RMA it.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Oh noo... Really??? I can't RMA it, I got it from Canada and I'm from Europe.

hofko said:
Oh noo... Really??? I can't RMA it, I got it from Canada and I'm from Europe.
Click to expand...
Click to collapse
Have you used toolkit for rooting? Because it's always better to root it manually using fastboot commands than using toolkits.
Also try this tutorial but I highly doubt if its will work for you
http://forum.xda-developers.com/showthread.php?t=2577447

hofko said:
Oh noo... Really??? I can't RMA it, I got it from Canada and I'm from Europe.
Click to expand...
Click to collapse
FAILED (remote: flash write failure)
I'm afraid this means that the flashchip has died. You could try flashing a new custom rom and see whether it boots or not, but I have my doubts.
Give it a few tries and in the mean time find a place where they repair the parts. If you give it to LG/google, they will most probably charge you for the whole mobo/battery which means you're better off buying a new device.

Now I really do think there's something wrong.with the chip. When I tried to adb pull it some pictures it gave me this message:
failed to copy: '/sdcard/DCIM/Camera' to 'C:/Users/.../Photos': I/O Error.
Is this what I think it is?
But I can find the actual pictures in the storage of the phone in twrp file manager. So...

hofko said:
Now I really do think there's something wrong.with the chip. When I tried to adb pull it some pictures it gave me this message:
failed to copy: '/sdcard/DCIM/Camera' to 'C:/Users/.../Photos': I/O Error.
Is this what I think it is?
But I can find the actual pictures in the storage of the phone in twrp file manager. So...
Click to expand...
Click to collapse
U said some of the files, so were some files copied?

No. None.
I am now trying to just flash stock Android using this guide http://www.droidviews.com/how-to-restoreunroot-nexus-5-by-flashing-factory-images/
When flashing the boot.img and system.img I got the same error I had before: FAILED (remote write failure). Everything else seemed okay. Now I am doing step 10 on the guide which is erasing the cache. This has been going on for quite some time and I presume I should just leave it do it's job as some people had some issues when ending this processby force.
What to do? I am getting a bit panicky.

hofko said:
Now I really do think there's something wrong.with the chip. When I tried to adb pull it some pictures it gave me this message:
failed to copy: '/sdcard/DCIM/Camera' to 'C:/Users/.../Photos': I/O Error.
Is this what I think it is?
But I can find the actual pictures in the storage of the phone in twrp file manager. So...
Click to expand...
Click to collapse
Whatt???? That's great.
How about you start from scratch? does you device come up with adb devices ?
Is Platform-tools and usb driver correctly installed?
Since you can access storage from recovery, why don't you download a custom rom and transfer the rom to your device via OTG cable and flash it?
You can even backup your data using the OTG cable!

Post it to Canada and ask your Uncle to RMA it.

vin4yak said:
Whatt???? That's great.
How about you start from scratch? does you device come up with adb devices ?
Is Platform-tools and usb driver correctly installed?
Since you can access storage from recovery, why don't you download a custom rom and transfer the rom to your device via OTG cable and flash it?
You can even backup your data using the OTG cable!
Click to expand...
Click to collapse
Well I can try starting from scratch, but my Nexus has been erasing cache for almost an hour. Can I just stop that?
My OTG cable just doesn't work for some reason. I works on my Nexus 7 2012 version.
I am already in the process of reinstalling stock android so i don't really know if I even have twrp installed now...
rootSU said:
Post it to Canada and ask your Uncle to RMA it.
Click to expand...
Click to collapse
Will they do that? I mean I have unlocked bootloader and a rooted phone...

Made fault while trying to root the Oneplus One

Hello!
I was following this guide to root my new Oneplus One: highonandroid (.) com/android-smartphones/how-to-root-oneplus-one/ My operating system is Debian, thought it would be easier on that one since I don't have to install drivers.
Everything worked until Step 9 where I had to do this: "sudo ./fastboot-linux flash recovery openrecovery-twrp-2.7.1.1-bacon.img". I get this error message:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (0 KB)...
FAILED ()
finished, total time: 0.000s
Then I tried the next command: "sudo ./fastboot-linux erase cache" This one worked... :silly: :silly:
Now my phone takes forever to boot, i.e. it doesn't. Only fastboot works...
I tried it on a Mac as well.. but I just get the message "device loading" or something like that. What can I do to fix this? I have no idea.

Rosteox said:
Hello!
I was following this guide to root my new Oneplus One: highonandroid (.) com/android-smartphones/how-to-root-oneplus-one/ My operating system is Debian, thought it would be easier on that one since I don't have to install drivers.
Everything worked until Step 9 where I had to do this: "sudo ./fastboot-linux flash recovery openrecovery-twrp-2.7.1.1-bacon.img". I get this error message:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (0 KB)...
FAILED ()
finished, total time: 0.000s
Then I tried the next command: "sudo ./fastboot-linux erase cache" This one worked... :silly: :silly:
Now my phone takes forever to boot, i.e. it doesn't.
I tried it on a Mac as well.. but I just get the message "device loading" or something like that. What can I do to fix this? I have no idea.
Click to expand...
Click to collapse
Is your one plus unlocked?

lolitsryan96 said:
Is your one plus unlocked?
Click to expand...
Click to collapse
Yes, everything excluding step 9 was successful.

Rosteox said:
Yes, everything excluding step 9 was successful.
Click to expand...
Click to collapse
ok I am confused so you went to a different site to root but came to xda to ask how to fix it? Have you asked over there as well. Also I am assuming that those are commands for a Mac? If so may I suggest you do some searching for a mac tutorial here in xda and a mac tutorial on how to fully restore. You may need to push imgs back to your phone.
9 Steps for rooting seem a little excessive for this phone

playya said:
ok I am confused so you went to a different site to root but came to xda to ask how to fix it? Have you asked over there as well. Also I am assuming that those are commands for a Mac? If so may I suggest you do some searching for a mac tutorial here in xda and a mac tutorial on how to fully restore. You may need to push imgs back to your phone.
9 Steps for rooting seem a little excessive for this phone
Click to expand...
Click to collapse
How can I recover the whole operating system? I just want it to work again. :/
Edit: It works again. I did a reset by pressing Volume down + Power. Sorry...

Rosteox said:
How can I recover the whole operating system? I just want it to work again. :/
Edit: It works again. I did a reset by pressing Volume down + Power. Sorry...
Click to expand...
Click to collapse
Glad you got it working take it easy and stay away from toolkits... Lol

And stay away from other sites.
Transmitted via Bacon

[Q] fastboot erase system FAILED

I've been having trouble with my HTC One M8. It seems to have started when I flashed CM 12.1. Now I get messages about the SystemUI failing.
So, I tried to restore a nandroid. No luck -- I get errors when I try to do the factory reset.
I've also tried using FASTBOOT erase system, but I get the "FAILED (remote: not allowed)" message.
I can see the correct device number when I do FASTBOOT devices.
Any suggestions? At this point I'd just like to wipe it clean and start over, but I can't even do that.

tgreenstein said:
I've been having trouble with my HTC One M8. It seems to have started when I flashed CM 12.1. Now I get messages about the SystemUI failing.
So, I tried to restore a nandroid. No luck -- I get errors when I try to do the factory reset.
I've also tried using FASTBOOT erase system, but I get the "FAILED (remote: not allowed)" message.
I can see the correct device number when I do FASTBOOT devices.
Any suggestions? At this point I'd just like to wipe it clean and start over, but I can't even do that.
Click to expand...
Click to collapse
Try
Fastboot oem task 29
Then continue.

dottat said:
Try
Fastboot oem task 29
Then continue.
Click to expand...
Click to collapse
Still can't do a factory reset. "oem task 29" gave me a INFOFormat BINFS and copy [17.124s] finished.
Is there something else I need to do?

tgreenstein said:
Still can't do a factory reset. "oem task 29" gave me a INFOFormat BINFS and copy [17.124s] finished.
Is there something else I need to do?
Click to expand...
Click to collapse
Flash ruu now.

dottat said:
Flash ruu now.
Click to expand...
Click to collapse
Thanks! I'm back in business.

dottat said:
Try
Fastboot oem task 29
Then continue.
Click to expand...
Click to collapse
First off, thanks on behalf of the entire community for all the help I've seen you give people here. It never ceases to amaze me how much of a community forms around something as seemingly insignificant as a phone.
Now, what on God's green earth is the oem task 29 command? That's one I haven't seen before and I can't find a reference to explain it.

cntryby429 said:
First off, thanks on behalf of the entire community for all the help I've seen you give people here. It never ceases to amaze me how much of a community forms around something as seemingly insignificant as a phone.
Now, what on God's green earth is the oem task 29 command? That's one I haven't seen before and I can't find a reference to explain it.
Click to expand...
Click to collapse
Format binary file system.
All three ext4 partitions get formatted.
System/cache/data

tgreenstein said:
I've been having trouble with my HTC One M8. It seems to have started when I flashed CM 12.1. Now I get messages about the SystemUI failing.
So, I tried to restore a nandroid. No luck -- I get errors when I try to do the factory reset.
I've also tried using FASTBOOT erase system, but I get the "FAILED (remote: not allowed)" message.
I can see the correct device number when I do FASTBOOT devices.
Any suggestions? At this point I'd just like to wipe it clean and start over, but I can't even do that.
Click to expand...
Click to collapse
I have this same error with my redmi note 9s
I also tried to do the wipe with twrp and the system option does not appear

Fastboot FAILED (remote: failed to erase partition )

I have OPO 64GB and unlocked via fastboot. Every fastboot command related to flash or erase or format gave same error, unable to erase or write the partition.
I was able to fastboot boot <custom_recovery.img> into TWRP 2.7 I believe but TWRP gives errors, unable to mount <partition>, etc. Any command in TWRP results into a failure to mount or write.
I tried ADB Sideload <zip> and at 12% it rebooted back into Cyanogen Mod ready logo.
TWRP only runs if I boot to it via fastboot, it can't write to the bootloader via fastboot. One strange thing under TWRP storage it shows Internal Storage 0MB and USB-OTG 0MB, the partitions also show 0MB excep for system, but can't format anything or resize.
I feels like there is no storage in this device, is this something that can be fixed or is this a DOA device? It was working fine and a Cyanogen update ran and bricked it!
When I try to fastboot flash I get this error, fail to write. I even tried the OnePlusRestoreTool and it fails to write to the phone.
fastboot flash recovery twrp3.img
target reported max download size of 1073741824 bytes
sending 'recovery' (13326 KB)...
OKAY [ 0.422s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.479s
Thoughts?
Thank You

It seems that your partitions are corrupt.
I had the same issue and solved it by restoreing completley to stock Rom. There must be a thread for this anywhere out, if not download a fastboot image from cyanogen support site extract it and try to flash it.

That is what I was leaning towards, but in every solution to restore the stock ROM I have to use fastboot and fastboot just fails to write anything. I can't even get TWRP to stick, fails to write every time. I tried the OnePlusRestoreTool but the driver installs ok but the tool can't find the phone, tried 2 different PCs. I was hoping for another solution other than fastboot or the OnePlusRestoreTool, I searched but could not find another method, I was hoping someone could point me in the right direction.
Thanks

newpop1_android said:
I have OPO 64GB and unlocked via fastboot. Every fastboot command related to flash or erase or format gave same error, unable to erase or write the partition.
I was able to fastboot boot <custom_recovery.img> into TWRP 2.7 I believe but TWRP gives errors, unable to mount <partition>, etc. Any command in TWRP results into a failure to mount or write.
I tried ADB Sideload <zip> and at 12% it rebooted back into Cyanogen Mod ready logo.
TWRP only runs if I boot to it via fastboot, it can't write to the bootloader via fastboot. One strange thing under TWRP storage it shows Internal Storage 0MB and USB-OTG 0MB, the partitions also show 0MB excep for system, but can't format anything or resize.
I feels like there is no storage in this device, is this something that can be fixed or is this a DOA device? It was working fine and a Cyanogen update ran and bricked it!
When I try to fastboot flash I get this error, fail to write. I even tried the OnePlusRestoreTool and it fails to write to the phone.
fastboot flash recovery twrp3.img
target reported max download size of 1073741824 bytes
sending 'recovery' (13326 KB)...
OKAY [ 0.422s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.479s
Thoughts?
Thank You
Click to expand...
Click to collapse
Try this

geowolf1000 said:
Try this
Click to expand...
Click to collapse
So I tried the link but also their method uses FastBoot and FastBoot fails to write to the OPO every time no matter what, see below. I can put TWRP in memory but can't write to the SD I guess. Any tool that can reformat the storage and put it back together since FastBoot and ADB can't write to it?
Thx
target reported max download size of 1073741824 bytes
sending 'persist' (4244 KB)...
OKAY [ 0.137s]
writing 'persist'...
FAILED (remote: flash write failure)
finished. total time: 5.208s

Has a second method from terminal
Run command from twrp rerminal
Στάλθηκε από το A0001 μου χρησιμοποιώντας Tapatalk

Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work

Chinaroad said:
Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work
Click to expand...
Click to collapse
He tried that one, but as the PC doesn't detect his phone that ain't gonna work...
@newpop1_android could you sent me a PM, I'll try to resolve your issue in a teamviewer session.

Chinaroad said:
Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work
Click to expand...
Click to collapse
Hello, so I managed to get an older PC to do all this in as well and tried another PC anyway. I ran the color.zip install, drivers installed OK and phone is detected, I ran the Msm8974DownloadTool.exe and it found the phone in COM3, I see a progress bar in one file, the image file and then it reboots the phone but it comes back to the Cyanogen splash screen and it does not go anywhere, so I reboot it again manually power+VUp and the tool finds it again and tries to send the *same* file again, and then I tried this loop at least 10 times.
I conclude that it is unable to write the image to the cell, same symptom I encountered with Fastboot flash boot img. Does this mean that the cell is bricked since nothing can write to the SD?

Do the progressbars you see in Msm8974DownloadTool.exe become green?
Maybe see there:
http://www.technobuzz.net/guide-to-recover-from-hard-bricked-oneplus-one/
It is nearly the same like the one posted before, but has some screenshots.
After doing this color OS should boot up, not cyanogen os.
If only one image file is "flashed", check if your color.zip is downloaded correctly
Hope this helps

Flo9818 said:
Do the progressbars you see in Msm8974DownloadTool.exe become green?
Maybe see there:
http://www.technobuzz.net/guide-to-recover-from-hard-bricked-oneplus-one/
It is nearly the same like the one posted before, but has some screenshots.
After doing this color OS should boot up, not cyanogen os.
Hope this helps
Click to expand...
Click to collapse
Hello, not really, it does one file and then I see progress bar move on the first file, progress bar finished and then the phone boots to the cyanogen screen again, then i tried again, it still shows the same file again. It does not save the file, fails to write pretty much, same thing as fastboot.

There should be serveral progressbars. One for each image in color.zip. Try to reinstall the qualcomm 2012 drivers.
Have you restarted your PC?

Flo9818 said:
There should be serveral progressbars. One for each image in color.zip. Try to reinstall the qualcomm 2012 drivers.
Click to expand...
Click to collapse
I actually did that and tried one plus one as well, I also tried the other unbrick toll as well with other drivers. The phone is recognized no problem, but nothing can write to it, just like fastbook flash , write denied every time.

Restarted your PC after qualcomm driver install?
Maybe there be driver problems related to win10.
Also check
fastboot oem device-info if your bootloader is really unlocked

Flo9818 said:
Restarted your PC after qualcomm driver install?
Maybe there be driver problems related to win10.
Also check
fastboot oem device-info if your bootloader is really unlocked
Click to expand...
Click to collapse
It won't work, his device is not recognized by adb or fastboot.
My device is in the same state, I rebooted it and it hard bricked, I tried using the ColorOS flash tool but, when I start it, it is stuck in a loop trying to flash "8974_msimage.mbn", any solution would be appreciated, because I hard bricked it in the first day after receiving my OPO (I bought an used one).
I already tried on two different computers, the same issue happens, I also tried to find a fix, but everyone that had this issue never replied, so I think this state is really THE hard brick, with no ways to go back to the original state.
@newpop1_android did you find a solution for your problem?

MrPowerGamerBR said:
It won't work, his device is not recognized by adb or fastboot.
My device is in the same state, I rebooted it and it hard bricked, I tried using the ColorOS flash tool but, when I start it, it is stuck in a loop trying to flash "8974_msimage.mbn", any solution would be appreciated, because I hard bricked it in the first day after receiving my OPO (I bought an used one).
I already tried on two different computers, the same issue happens, I also tried to find a fix, but everyone that had this issue never replied, so I think this state is really THE hard brick, with no ways to go back to the original state.
@newpop1_android did you find a solution for your problem?
Click to expand...
Click to collapse
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?

Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
Yes, I did.
I also tried that tool before, same issue.

Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
The problem is that the device gets disconnected when flashing for some reason. I tried two different drivers, both didn't work.
I'm willing to pay 5$ to someone who can fix this issue for me.

MrPowerGamerBR said:
The problem is that the device gets disconnected when flashing for some reason. I tried two different drivers, both didn't work.
I'm willing to pay 5$ to someone who can fix this issue for me.
Click to expand...
Click to collapse
Which Windows Version do you use? I would try with win7. With win 8.1 and 10 you have to disable driver verification.
Have you disabled your antivirus?
Have you disabled UAC?
Maybe another USB cable?
If all this does not work see here:
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/

Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
Flo9818 said:
Which Windows Version do you use? I would try with win7. With win 8.1 and 10 you have to disable driver verification.
Have you disabled your antivirus?
Have you disabled UAC?
Maybe another USB cable?
If all this does not work see here:
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
Click to expand...
Click to collapse
Windows 7, but Windows 7 also needs to disable driver verification.
I don't use any antivirus.
No, but I ran the tool as administrator.
I already tried that, I tried with the original cable that came with the device and my Moto G 2014 cable, same issue on both.
It isn't a missing driver issue tho, Qualcomm drivers are installed and working because the ColorOS flash tool detects the device.
Anyway, thanks for helping

Bootloop on Motorola Moto G4 Play (Verizon) XT1609

I would like to recover the ROM on this Android this device it keeps bootlooping I tryed to Root the Device and I did a factory reset on it after I did a root... I thought everything was going find and it started to keep reloading the logo (Moto)...
I basically tried everything to recover the ROM on it using the following programs...
ADB Setup
MFastBoot (Error Message with Bootloader)
it seems to be locked device I can't seem to unlock the device... I seen someone that you don't have to have it unlock it to install TWRP or something....
Am all new to this stuff and I just got my phone I did not want anything happen to this phone for important use I would like to get this phone back up and running again...
Thanks

Moto G4 Play XT1609 Bootloop after rooting
travisbrown9201 said:
I would like to recover the ROM on this Android this device it keeps bootlooping I tryed to Root the Device and I did a factory reset on it after I did a root... I thought everything was going find and it started to keep reloading the logo (Moto)...
I basically tried everything to recover the ROM on it using the following programs...
ADB Setup
MFastBoot (Error Message with Bootloader)
it seems to be locked device I can't seem to unlock the device... I seen someone that you don't have to have it unlock it to install TWRP or something....
Am all new to this stuff and I just got my phone I did not want anything happen to this phone for important use I would like to get this phone back up and running again...
Thanks
Click to expand...
Click to collapse
Am in the same boat. My Verizon Moto G4 Play XT1609 Bootloops after rooting and restarting. I have tried all else including repairing via Verizon Upgrade Assistant tool with no success (Ugrade Assistant tool detected my phone, flashed latest firmware and cleared user data only for the phone to resume bootloop :crying.
I had to try Upgrade Assistant tool since this model does not qualified for bootloader unlocking ("fastboot getvar all" returned cid: 0x0002)
I trust that all hope is not lost, having confidence someone would turn up something somehow :laugh:
So, any help would be appreciated.

Re-run autoinitroot and then follow the instructions to unroot, thats all!

conquesoextra said:
Re-run autoinitroot and then follow the instructions to unroot, thats all!
Click to expand...
Click to collapse
Thanks too much! you just saved my Motorola!

bullracing said:
Thanks too much! you just saved my Motorola!
Click to expand...
Click to collapse
Hi,
I asked a related question in https://forum.xda-developers.com/g4-play/help on 4/9 and have yet to receive any responses. I didn't see this question before. It looks like a very similar situation to mine.
My XT1609 also is bootlooping and the bootloader also is locked, so I assume that this is why I'm getting "Preflash validation failed" errors when I try to download stock images to it. I found harpia_vzw_oem_vzw_user_7.1.1_NPI26.48-38_48_release-keys-cid2_vzw.tar.gz through this site and have been attempting to use Linux/fastboot to download images from the tar. I am able to download and reflash one of the images, logo.img, but I get the prevalidation errors for everything else I've tried.
I'm not familiar with mfastboot or autoinitroot. Can someone tell me where I can get these and how to use them? Should I just need to use autoinitroot to fix the bootlooping or does this somehow allow me to flash images to the phone?
Thanks!

thalwegz said:
Hi,
I asked a related question in https://forum.xda-developers.com/g4-play/help on 4/9 and have yet to receive any responses. I didn't see this question before. It looks like a very similar situation to mine.
My XT1609 also is bootlooping and the bootloader also is locked, so I assume that this is why I'm getting "Preflash validation failed" errors when I try to download stock images to it. I found harpia_vzw_oem_vzw_user_7.1.1_NPI26.48-38_48_release-keys-cid2_vzw.tar.gz through this site and have been attempting to use Linux/fastboot to download images from the tar. I am able to download and reflash one of the images, logo.img, but I get the prevalidation errors for everything else I've tried.
I'm not familiar with mfastboot or autoinitroot. Can someone tell me where I can get these and how to use them? Should I just need to use autoinitroot to fix the bootlooping or does this somehow allow me to flash images to the phone?
Thanks!
Click to expand...
Click to collapse
Hi, again
I was able to download the autoinitroot package from http://downloads.codefi.re/autoprime/Motorola/autoinitroot/XT1609 and extract and run the Linux version of the script. Here's what happened:
2102d sudo ./auto#initroot.linux.sh
#initroot and cve-2016-10277 by https://twitter.com/roeehay
magisk by https://twitter.com/topjohnwu
auto#initroot by https://twitter.com/@utoprime
.
..
...
....to uninstall auto#initroot, press <any> key within 3 seconds
...
..
.
-start auto#initroot
-send fastboot oem config fsg-id a initrd=0x91000000,2064196
...
FAILED (remote failure)
finished. total time: 0.017s
-send fastboot flash initroot xt1609_harpia_vzw_mpis24.241-2.35-1-17.initroot
target max-download-size: 256MB
sending 'initroot' (19531 KB)...
OKAY [ 24.421s]
writing 'initroot'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 24.431s
-send fastboot continue
resuming boot...
OKAY [ 0.097s]
finished. total time: 0.097s
-finish moto boot
I have Android 7.1.1 installed on my phone, the stock Verizon OTA version. Could there be an incompatibility between this initroot image and the other software on the phone?
Thanks