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

[Q] Possible Brick. Help needed.

Hi XDA- love your stuff. Have used these communities for 8 different devices - never with an issue. Sad to say my first was on a nexus.
Used WUGs toolkit to unlock my phone last week. Installed the drivers according to the instructions. Clicked "Unlock" and followed all the prompts, and that's as far as I got.
The handset rebooted to the "Upgrade Andoid" graphic, and when I pressed VOL/UP the prompt at the bottom displayed "Formatting /data". This continued the first time for about 12 hours (I went to bed and woke up with it).
Next day I searched every thread that might relate to my issue. Unrooting threads, flash-all.bat for 4.4.4 and 5.0. Attempted sideloads in ADB. Fastbooted the **** out of it. Used e2fsck thinking the partitions needed repairing and even that failed. No love anywhere.
Wondering if you guys could guide me through getting back to square one and how to get my phone running again. It's still got a lot of love to give and I'm not ready to give up on it yet.
When I run Flash-all.bat for 4.4.4 or 5.0 the scripts fail at "erasing cache". I've left it for over an hour and it's just stuck.
In fastboot if I run just the code on it's own it works fine. But when flashing through fastboot something fails.
I've loaded TWRP to try and see anything in there and to get adb shell working, but in TWRP it's unable to mount "/Data", "/Cache", and "storage". The total internal storage as reported by TWRP is 0MB.
When I go into WIPE - the following partitions are
System - 1009MB.
Data - 0MB
Davlik Cache - Invalid Partition
Internal Stor. - Invalid Partition
Cache - 0MB
If it makes a difference (which I wouldn't think it should) I was running 4.4.4 vanilla (unrooted/unlocked) in ART runtime.
Thanks in advance for the help - let me know if there's any other information I can supply to help you help me.

Sneddy32 said:
Hi XDA- love your stuff. Have used these communities for 8 different devices - never with an issue. Sad to say my first was on a nexus.
Used WUGs toolkit to unlock my phone last week. Installed the drivers according to the instructions. Clicked "Unlock" and followed all the prompts, and that's as far as I got.
The handset rebooted to the "Upgrade Andoid" graphic, and when I pressed VOL/UP the prompt at the bottom displayed "Formatting /data". This continued the first time for about 12 hours (I went to bed and woke up with it).
Next day I searched every thread that might relate to my issue. Unrooting threads, flash-all.bat for 4.4.4 and 5.0. Attempted sideloads in ADB. Fastbooted the **** out of it. Used e2fsck thinking the partitions needed repairing and even that failed. No love anywhere.
Wondering if you guys could guide me through getting back to square one and how to get my phone running again. It's still got a lot of love to give and I'm not ready to give up on it yet.
When I run Flash-all.bat for 4.4.4 or 5.0 the scripts fail at "erasing cache". I've left it for over an hour and it's just stuck.
In fastboot if I run just the code on it's own it works fine. But when flashing through fastboot something fails.
I've loaded TWRP to try and see anything in there and to get adb shell working, but in TWRP it's unable to mount "/Data", "/Cache", and "storage". The total internal storage as reported by TWRP is 0MB.
When I go into WIPE - the following partitions are
System - 1009MB.
Data - 0MB
Davlik Cache - Invalid Partition
Internal Stor. - Invalid Partition
Cache - 0MB
If it makes a difference (which I wouldn't think it should) I was running 4.4.4 vanilla (unrooted/unlocked) in ART runtime.
Thanks in advance for the help - let me know if there's any other information I can supply to help you help me.
Click to expand...
Click to collapse
What is the output of fastboot flash cache cache.img ?
You may need to flash cache.img and stock recovery.inmg and then try a manual wipe of /cache via stock recovery.

Sneddy32 said:
Hi XDA- love your stuff. Have used these communities for 8 different devices - never with an issue. Sad to say my first was on a nexus.
Used WUGs toolkit to unlock my phone last week. Installed the drivers according to the instructions. Clicked "Unlock" and followed all the prompts, and that's as far as I got.
The handset rebooted to the "Upgrade Andoid" graphic, and when I pressed VOL/UP the prompt at the bottom displayed "Formatting /data". This continued the first time for about 12 hours (I went to bed and woke up with it).
Next day I searched every thread that might relate to my issue. Unrooting threads, flash-all.bat for 4.4.4 and 5.0. Attempted sideloads in ADB. Fastbooted the **** out of it. Used e2fsck thinking the partitions needed repairing and even that failed. No love anywhere.
Wondering if you guys could guide me through getting back to square one and how to get my phone running again. It's still got a lot of love to give and I'm not ready to give up on it yet.
When I run Flash-all.bat for 4.4.4 or 5.0 the scripts fail at "erasing cache". I've left it for over an hour and it's just stuck.
In fastboot if I run just the code on it's own it works fine. But when flashing through fastboot something fails.
I've loaded TWRP to try and see anything in there and to get adb shell working, but in TWRP it's unable to mount "/Data", "/Cache", and "storage". The total internal storage as reported by TWRP is 0MB.
When I go into WIPE - the following partitions are
System - 1009MB.
Data - 0MB
Davlik Cache - Invalid Partition
Internal Stor. - Invalid Partition
Cache - 0MB
If it makes a difference (which I wouldn't think it should) I was running 4.4.4 vanilla (unrooted/unlocked) in ART runtime.
Thanks in advance for the help - let me know if there's any other information I can supply to help you help me.
Click to expand...
Click to collapse
Try what rootSU said to do and avoid using toolkits in the future. It seems that about 95% of the "help I bricked my phone!" threads stem from using toolkits.
Sent from my iPhone 6 using Tapatalk

In the past I've never used toolkits but figured by now they might be fairly reliable. Big mistake.
rootSU said:
What is the output of fastboot flash cache cache.img ?
You may need to flash cache.img and stock recovery.inmg and then try a manual wipe of /cache via stock recovery.
Click to expand...
Click to collapse
Is this what you mean?
Code:
c:\android-sdk\platform-tools>fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.577s]
sending 'cache' <13348 KB>...
OKAY [ 0.639s]
writing 'cache'...
OKAY [ 1.086s]
finished. total time: 2.305s
Booted into stock recovery - cache wipe complete. Rebooted and phone went into the Android Updating graphic (wiggly ears & cog). Just a cache partition wipe or factory reset?
Should I now attempt flashall.bat??
I'm using the LRX21o from the Google Dev website. I'm guessing at this point it makes no difference?

Yeah that's what I meant. Looks successful.
Next I guess flashing everything is next step.

So nothing changed, and I decided to give flash-all.bat another go. Same thing. Stalled on 'erasing cache'.
When I forced reboot the error "Too many links" came up.
I went back in and flashed cache.img thinking I might be able to finish off the job. No love. Back to the updating graphic.
Now when I try to go into recovery to start again it just goes into the upgrading graphic.

Bump...?

Return it.

Phone Stuck on Cyanogen Logo

I was charging my phone when I noticed it restarted itself and then now it's stuck on the Cyanogen Logo screen.
I've gone into Recovery, pressed wipe data/factory reset but nothing actually happens. A bunch of stuff shows up saying
E:failed to mount / cache (Invalid argument)
E:Can't mount / cache / recovery /last install
E: can't open /cache recovery/last install
I tried pressing wipe cache partition, same thing
I pressed wipe media, same thing.
Reboot to bootloader, it just stuck on Fastboot logo.
I havn't done anything to the phone such as rooting or unlocking bootloader. I just left the phone as it is and only did system updates provided by Cyanogen.
Any idea?

megamonkey said:
I was charging my phone when I noticed it restarted itself and then now it's stuck on the Cyanogen Logo screen.
I've gone into Recovery, pressed wipe data/factory reset but nothing actually happens. A bunch of stuff shows up saying
E:failed to mount / cache (Invalid argument)
E:Can't mount / cache / recovery /last install
E: can't open /cache recovery/last install
I tried pressing wipe cache partition, same thing
I pressed wipe media, same thing.
Reboot to bootloader, it just stuck on Fastboot logo.
I havn't done anything to the phone such as rooting or unlocking bootloader. I just left the phone as it is and only did system updates provided by Cyanogen.
Any idea?
Click to expand...
Click to collapse
You probably have a corrupt persist partition. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
You'll need to unlock your bootloader, which will wipe your device, but it's the only way. I have a guide here that explains how to unlock it (also how to install adb/fastboot and the drivers). Once you've unlocked your bootloader, put the persist file in your fastboot folder, open a command prompt from within your fastboot folder (shift + right click, then select open command prompt here), and issue these commands:
Code:
fastboot erase persist
fastboot flash persist persist.img
Once it's done flashing you can try rebooting your phone. If it still doesn't boot you'll have to go back to my guide and follow the instructions in section 8 to flash the stock images.

There's no way of saving my photos is there? I assume no...but might as well ask.
Thanks so much for the help!

megamonkey said:
There's no way of saving my photos is there? I assume no...but might as well ask.
Thanks so much for the help!
Click to expand...
Click to collapse
Unfortunately not if you can't boot into the OS.

I typed: fastboot oem unlock
It says OKAY
So when I type: fastboot oem device-info
<bootloader> Device tampered:true
<bootloader> Device unocked: false
<bootloader> Charger screen enabled: false
I assume something went wrong?

megamonkey said:
I typed: fastboot oem unlock
It says OKAY
So when I type: fastboot oem device-info
<bootloader> Device tampered:true
<bootloader> Device unocked: false
<bootloader> Charger screen enabled: false
I assume something went wrong?
Click to expand...
Click to collapse
Yeah, this happens sometimes. I can only suggest you try again in the hope that it works, without the bootloader unlocked there's gonna be nothing you can really do.

So I keep typing it till it shows true for "Device unlocked"?
I typed it 4 times now....it still doesn't say Device Unlocked True...

megamonkey said:
So I keep typing it till it shows true for "Device unlocked"?
I typed it 4 times now....it still doesn't say Device Unlocked True...
Click to expand...
Click to collapse
It isn't going to work. You're only other option is to try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
I know you're not hard-bricked but this is likely your only chance to get the phone working again.

Heisenberg said:
It isn't going to work. You're only other option is to try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
I know you're not hard-bricked but this is likely your only chance to get the phone working again.
Click to expand...
Click to collapse
I'll try doing all over again one last time. But I was reading the guide you gave me, it says it won't work on soft-brick, will it still work tho?

megamonkey said:
I'll try doing all over again one last time. But I was reading the guide you gave me, it says it won't work on soft-brick, will it still work tho?
Click to expand...
Click to collapse
I'm pretty sure others in similar situations to you have used it, I could be wrong.

Heisenberg said:
I'm pretty sure others in similar situations to you have used it, I could be wrong.
Click to expand...
Click to collapse
I tried using the method but I'm not sure why it isn't working. I ran the program and it gave me a few problems letting me know what's wrong with my phone:
userdata_64G.img: FAILED
boot.img: FAILED
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED
I'm running near the end where nothing is going my way and I may need to either ask someone to attempt to fix it or buy a new phone...

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

Can only boot into bootloader

Woke up this morning and phone stuck on animation screen. I can boot into bootloader and select recovery but TWRP does not load. It only just cycles through the boot animation. I tried re-flashing TWRP with fastboot and it said it was successful but will still not boot recovery. It just cycles through the boot animation screen.
Any ideas? Any way to save photos? I can only use fastboot and not adb I assume.
This is a XT1254

Raistlen0 said:
Woke up this morning and phone stuck on animation screen. I can boot into bootloader and select recovery but TWRP does not load. It only just cycles through the boot animation. I tried re-flashing TWRP with fastboot and it said it was successful but will still not boot recovery. It just cycles through the boot animation screen.
Any ideas? Any way to save photos? I can only use fastboot and not adb I assume.
Click to expand...
Click to collapse
Try booting from TWRP loaded on your PC.
fastboot boot TWRP.img (where "TWRP" is whatever you have named your copy of TWRP in your ADB folder).
You can actually boot to TWRP this way without even installing TWRP. Think of it as "temporary" TWRP. I've done it to make a copy of an stock firmware image where stock recovery is still installed.

Thanks. Looks like phone got wet somehow. After dryng out it will boot into recovery but it says no OS present and shows the SD card empty except for a twrp folder. Guess i will have to reimage ROM and see what happens.

same issue, where you using LOS 7 ?
Was running LOS 7, and suddenly one day was stuck on bootloop.
TWRP loaded once tried to reflash LOS with the existuing files in the user download, but after reboot then no TWRP
Further attempts to install TWRP with no sucees, also noyticed cache fs was not posible to mount/clear, attempted to clear the other fs and now none loads
The suggested hardbrick solution from https://forum.xda-developers.com/moto-maxx/general/tuto-unbrick-xt1225-100-t3483623 fails when loading any version of gpt
C:\MAXX-Unbrick Kit2\2.Unbrick>mfastboot.exe flash partition gpt6s1.bin
< waiting for device >
sending 'partition' (32 KB)...
OKAY [ 0.235s]
writing 'partition'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.626s
Click to expand...
Click to collapse
From what I read i need to flash the same gpt but no idea how to get it.
Also fastboot commands seems to work but not the adb nor the RSD lite

Raistlen0 said:
Any ideas? Any way to save photos? I can only use fastboot and not adb I assume.
This is a XT1254
Click to expand...
Click to collapse
Go to https://photos.google.com/. Your photos may already by there. In some countries like U.S. all your photos are automatically backed up if you give the app permission. I set it to back up when I'm on my home wi-fi network. I also have automatic picture back up with Dropbox and Amazon Prime photos.
You can also choose which folders the apps pull photos from -- not just the "camera" folders, but even Download, WhatsApp, and others if you wish.

Raistlen0 said:
Thanks. Looks like phone got wet somehow. After dryng out it will boot into recovery but it says no OS present and shows the SD card empty except for a twrp folder. Guess i will have to reimage ROM and see what happens.
Click to expand...
Click to collapse
Were you able to reimage it, for mine it was not possible, I kept focused on the corrupted got.bin, but then looked it even further, and seems eMMC corruption.
Any gas that I wrote on it got damaged, even the bootlogo is corrupted now ( showing only half of it, replacing it completes but still showing old image) it is a shame as camera/screen worked great, but without adding, there is not really much that can be done.
If your target is to recover the data, by all means do not try to reimage it, boot into recovery and try mounting the data partition, once done you can either transfer your files using ADB, or by mounting a thumb drive with an org adapter and copy them from terminal emulator on the TWRP