Database Info

[Q] Unfortunely "process_name" has stopped...

When I'm trying to turn on my Nexus 5 i get an error (in the title) and phone starts to reboot! Many people say : "clear app data", but how do i clear cache when i can't run the phone. It happened when my Nexus started to update system by itself without my touches to 4.4.3. I tried to do Wipe, but it doesn't make sense on phone's system and my TWRP asking for password (http://forum.xda-developers.com/google-nexus-5/help/twrp-password-t2511049) this helps to wipe, but doesn't solve problem with "Unfortunely bla-bla......" and inf.rebooting.
Phone's Description:
Android 4.4.2 before phone started to update by itself
Rooted
TWRP - custom recovery

Just flash 4.4.4 stock with fastboot. You'll be on the latest and issue should be gone.

KJ said:
Just flash 4.4.4 stock with fastboot. You'll be on the latest and issue should be gone.
Click to expand...
Click to collapse
now i have bootlop and message box with "Android is updating....Start apps" and reboot again and again. What should i do?

cwclasses said:
now i have bootlop and message box with "Android is updating....Start apps" and reboot again and again. What should i do?
Click to expand...
Click to collapse
tried to reflash img instead existing.
Output:
Userdata - Failed
Boot - OK
System - Failed
Recovery - Failed
Maybe i have to use adb commands and push something into the phone's memory, something like new ROM, Recovery or something else?

This is a guide for flashing stock.....has all the info you need. Make sure to follow it step by step.
http://forum.xda-developers.com/showthread.php?t=2513701

KJ said:
This is a guide for flashing stock.....has all the info you need. Make sure to follow it step by step.
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
it doesn't work, OMG my new nexus5......seems to be completely soft brocken:crying:

cwclasses said:
it doesn't work, OMG my new nexus5......seems to be completely soft brocken:crying:
Click to expand...
Click to collapse
Which part doesn't work?

by the issues , your emmc is bad, replace it

PsychDrummer said:
Which part doesn't work?
Click to expand...
Click to collapse
When i try to flash it messages me:
sending 'system' (209158 KB)...
OKAY [ 27.414s]
writing 'system'...
FAILED (remote: image update error)
finished. total time: 51.147s

TF700 stuck in Boot loop ... have access to bootloader

Hi,
I've posted on this topic on transformerforums website but have not had any success (despite valiant attempts from the guys on the forums).
I am unable to post the link here, please PM me for a link to my original post.
Basically my TF700T got stuck in a bootloop. I have unlocked the bootloader but have not flashed it so it's on stock ROM. I have not been able to flash a recovery ROM and am at a dead end as to what to do.
I am able to get to bootloader and I when I run
Code:
fastboot devices
I get the following output
Code:
015d2a506733f618 fastboot
Which all seems correct. I have access to the tablet when connected to my pc.
When I try to flash the recovery rom, it takes a very short amount of time and on my tablet the device hangs (i.e the RCK icon is no longer flashing). I have checked the blob, it is the correct one and the MD5 hash is correct.
Code:
C:\androidsdk\platform-tools>fastboot -i 0x0B05 flash recovery twrp-2.7.1.1-tf700t.blob
sending 'recovery' (6894 KB)...
OKAY [ 0.868s]
writing 'recovery'...
OKAY [ 0.089s]
finished. total time: 0.958s
I can get back into the bootloader if I restart again but attempting to flash it results in a hang.
I have tried to insert an sd with the stock ROM and boot in RCK mode but this has not worked either.
Has anyone any suggestions as to what to do?
The tablet is 2 years old now so not under warranty.
thanks in advance.

anyone have any suggestions?
I'm going on holidays on Thursday and would really love to get this resolved before I go.

deleted

Shameless bump .... are my only options to return this to the manufacturer?
Anyone any suggestions, do you need more info from me?

What you did looks correct, only the short time for "writing" looks suspicious. Try the fastboot command again, but replace "recovery" with "staging", maybe that works better. At the next reboot you should see a blue progress bar on the boot screen for a few seconds and it should reboot again.

Hi,
Thanks for the reply.
I tried as you suggested and looks like the same results. I'm doing this in windows 7 and have opened the command prompt as Administrator.
Code:
C:\adb>fastboot -i 0x0B05 flash staging twrp-2.7.1.1-tf700t.blob
sending 'staging' (6894 KB)...
OKAY [ 0.869s]
writing 'staging'...
OKAY [ 0.084s]
finished. total time: 0.955s
Is there any way I get get logs from the tablet itself?

I had been thinking was this a permissions thing although I am able to run
Code:
fastboot boot
Code:
fastboot boot-bootloader
and they work correctly. So I do have access but for some reason the partition is not getting flashed correctly.
Does anyone know what the partitions are used for?
I assume the system partition is used for the actual system image but what is the staging partition used for?

knoxor said:
I had been thinking was this a permissions thing although I am able to run
Code:
fastboot boot
Code:
fastboot boot-bootloader
and they work correctly. So I do have access but for some reason the partition is not getting flashed correctly.
Does anyone know what the partitions are used for?
I assume the system partition is used for the actual system image but what is the staging partition used for?
Click to expand...
Click to collapse
When blobs are written to the staging partition, on next boot. the bootloader flashes the contents to the relevant partitions (i.e., kernel, system, bootloader)

knoxor said:
Hi,
Thanks for the reply.
I tried as you suggested and looks like the same results. I'm doing this in windows 7 and have opened the command prompt as Administrator.
Code:
C:\adb>fastboot -i 0x0B05 flash staging twrp-2.7.1.1-tf700t.blob
sending 'staging' (6894 KB)...
OKAY [ 0.869s]
writing 'staging'...
OKAY [ 0.084s]
finished. total time: 0.955s
Is there any way I get get logs from the tablet itself?
Click to expand...
Click to collapse
Hi sbdags,
So it looks like I'm stuck at this point. The above command seems to work but the time for flashing the recovery blob to staging seems very short which probably indicates that this has not happened correctly. After the above command, on next boot when selecting RCK from the bootloader menu the tablet attempts to perform the update but then I get the android error screen (android dude on his back and error message).
Any suggestions as to what I can do next?
thanks
Paul

knoxor said:
Hi sbdags,
So it looks like I'm stuck at this point. The above command seems to work but the time for flashing the recovery blob to staging seems very short which probably indicates that this has not happened correctly. After the above command, on next boot when selecting RCK from the bootloader menu the tablet attempts to perform the update but then I get the android error screen (android dude on his back and error message).
Any suggestions as to what I can do next?
thanks
Paul
Click to expand...
Click to collapse
Well shoot me a PM, Lets see if we can find a solution to your issue ...
Thx Josh

bump again.
Is there anyone there who can help me on this please ?

knoxor said:
Is there anyone there who can help me on this please ?
Click to expand...
Click to collapse
I don't think I can help you, but can you post the build number of your bootloader? I remember someone had a bootloader for the TF300 on his TF700 and was then unable to flash blobs.

_that said:
I don't think I can help you, but can you post the build number of your bootloader? I remember someone had a bootloader for the TF300 on his TF700 and was then unable to flash blobs.
Click to expand...
Click to collapse
Hi, I fairly sure I have the correct bootloader (WW_epad-10.6.1.14.10-20130801 A03).
Just to clarify, this is a stock rom I have on the tab. I have it unlocked but not rooted.
thanks

knoxor said:
Hi, I fairly sure I have the correct bootloader (WW_epad-10.6.1.14.10-20130801 A03).
Just to clarify, this is a stock rom I have on the tab. I have it unlocked but not rooted.
thanks
Click to expand...
Click to collapse
Your bootloader is ok.
Did you PM Josh? What did you guys try?
If he couldn't help you, I doubt I can...
Aside from the suggestions I gave you on the Transformer Forum, I'm stumped...
So again:
Do not use USB 3.0 ports
Uninstall the fastboot drivers and use the one from here: http://forum.xda-developers.com/showthread.php?t=2646279
Check the fastboot.exe version and see if you can find a later one.
That's all I can think of right now....

berndblb said:
Your bootloader is ok.
Did you PM Josh? What did you guys try?
If he couldn't help you, I doubt I can...
Aside from the suggestions I gave you on the Transformer Forum, I'm stumped...
So again:
Do not use USB 3.0 ports
Uninstall the fastboot drivers and use the one from here: http://forum.xda-developers.com/showthread.php?t=2646279
Check the fastboot.exe version and see if you can find a later one.
That's all I can think of right now....
Click to expand...
Click to collapse
Yes I contacted Josh and shared my desktop with him one evening. We didn't resolve it. I've tried the flashing on 3 different computers.
One of them is an old laptop running ubuntu that I know only has USB2 ports on it.
The only thing I can think of is that I lost my original charger/cable but I spent the extra money to get an OEM one again so I hope that is not
the issue.
Could the cable be the issue??

knoxor said:
Yes I contacted Josh and shared my desktop with him one evening. We didn't resolve it. I've tried the flashing on 3 different computers.
One of them is an old laptop running ubuntu that I know only has USB2 ports on it.
The only thing I can think of is that I lost my original charger/cable but I spent the extra money to get an OEM one again so I hope that is not
the issue.
Could the cable be the issue??
Click to expand...
Click to collapse
If you got the charger from anywhere else but Asus - yes, that could be the issue. And the only one left I can think of....

No fastboot, No recovery, No adb and LG Flash Tool also doesn't work!

Ok I've been spending my Saturday on this for 9 hours straight now. Damn!
It started with trying to clean install resurrection remix rom (I had lollipop RR but I wanted to clean install a new version). I went full retard and deleted everything then I had nothing to flash and I couldn't connect to device with adb from windows 10.
I went to linux and I could use adb there. I booted into recovery (TWRP 2.7) and sideloaded new RR rom. It started to work!
Then I went beyond full retarded and tried to upgrade the TWRP itself to 2.8.6 and I tried different things that didn't work except one that was an app that took care of it but then it could not boot normally.
I did some more idiotic things til I ended up with a brick that the only way I could feel some communication with it (!) was with Download mode (press vol +) in DemiGod Crash Handler and LG flash tools!
Nothing else works (no adb, no fastboot, no recovery). It gives secure booting error (boot certificate verify) when it tries to boot (or into recovery) and gives Critical Error that I can either reboot or go to Dload mode!
By the way from the beginning I couldn't use fastboot!
also LG flash tools give model information check fail error!
I remember some weird stuff like using dd to copy some image partitions (I didn't have fastboot). I also remember doing rm -rf * somewhere =)) and a lot of playing around with TWRP!
I would really appreciate some help getting out of this mess!

_Rooz_ said:
Ok I've been spending my Saturday on this for 9 hours straight now. Damn!
It started with trying to clean install resurrection remix rom (I had lollipop RR but I wanted to clean install a new version). I went full retard and deleted everything then I had nothing to flash and I couldn't connect to device with adb from windows 10.
I went to linux and I could use adb there. I booted into recovery (TWRP 2.7) and sideloaded new RR rom. It started to work!
Then I went beyond full retarded and tried to upgrade the TWRP itself to 2.8.6 and I tried different things that didn't work except one that was an app that took care of it but then it could not boot normally.
I did some more idiotic things til I ended up with a brick that the only way I could feel some communication with it (!) was with Download mode (press vol +) in DemiGod Crash Handler and LG flash tools!
Nothing else works (no adb, no fastboot, no recovery). It gives secure booting error (boot certificate verify) when it tries to boot (or into recovery) and gives Critical Error that I can either reboot or go to Dload mode!
By the way from the beginning I couldn't use fastboot!
also LG flash tools give model information check fail error!
I remember some weird stuff like using dd to copy some image partitions (I didn't have fastboot). I also remember doing rm -rf * somewhere =)) and a lot of playing around with TWRP!
I would really appreciate some help getting out of this mess!
Click to expand...
Click to collapse
This will help with flash tool
http://forum.xda-developers.com/showthread.php?p=56961336
Sent from my LGLS991 using Tapatalk

Swetnes said:
This will help with flash tool
http://forum.xda-developers.com/showthread.php?p=56961336
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
Thanks I think I made some progress but it is not working yet!
Instead of changing to D800, I zeroed out the bytes corresponding to number (because I was getting error CrossDL [] to [D800]) and it moved one step forward!
Now it stops at "Change to DL mode" (can't change to download mode - 00000064).
It may be related that it can't read PID and IMEI off my phone!
Also that refurbish term might need some attention (I got it from ebay but I don't recall anything saying it is refurbished and it was an att seller emptying their stock of g2s).
Again, I don't (can't) go to Dload mode by pressing volume up and plugging in. A critical error page comes up when I turn on the phone that has 2 options: vol+ for Dload and vol- for reboot.
That's all I can think of as of now!
Froms the log file:
[ 1:23:21] SubProcess Name : DiagDload
[ 1:23:21] [T000003] 00 00 7E ...
[ 1:23:21] [T000004] 3A A1 6E 7E :.n.
[ 1:23:26] Response packet time out 5000 milisec
[ 1:23:26] CBasicCom::SendRecvPacket, PACKET_ERROR code = 1460 Msg => This operation returned because the timeout period expired.
[ 1:23:26] Error! CCmdProcess::ExecuteCommand() �� SendRecvPacket()
[ 1:23:26] Can't change to download mode
[ 1:23:26] RefurbishProcess() Error.
[ 1:23:26] �ڡ� ERROR REASON : LAF_ERROR_CHANGE_DLOAD_F
[ 1:23:26] CComPort::ClosePort, Closed Port Successfully for COM 41
[ 1:23:26] CBasicComControl::Close, the port(COM41) is closed successfully
[ 1:23:26] RunProcess() is fail.
[ 1:23:26] CBasicComControl::IsConnected, the port(COM41) connection is not detected
[ 1:23:26] [ 1:23:26] Can't change to download mode
[ 1:23:26] DoDownload() Exception
Click to expand...
Click to collapse

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