Help Nexus 5 stuck in the start up screen

[jGagliarde]

Actually, I just looked it up. I never really paid much attention to stock recovery. It looks like that does indeed allow adb shell access and the op may be able to pull the files down after all.

@JGagaliarde, while in recovery, select the apply update from ADB option and then try the adb devices command. If that works, we can perhaps save your ass files.

I've hidden the numbers because I'm not really sure it's safe to post it in the internet haha

 

[Incakola]

I've hidden the numbers because I'm not really sure it's safe to post it in the internet haha

Yeah, it is good that you do this because it is possible to rewrite the S/N

If you follow-up on what lunatic59 posted you should be able to use these commands:

adb pull /sdcard/DCIM/ or adb pull /sdcard/DCIM/Camera/

 

[jGagliarde]

I tried both. All I get is "error: closed". But I don't know if I've done it right.
All I did was type adb devices and then adb pull /sdcard/DCIM/
Is this all I should do?

After I select apply update from adb, in the bottom of the screen it reads: Now send the package you want to apply to the device with "adb sideload <filename>"...
So maybe we can try the zip to wipe dalvik and cache?

 

[Incakola]

I tried both. All I get is "error: closed". But I don't know if I've done it right.
All I did was type adb devices and then adb pull /sdcard/DCIM/
Is this all I should do?

After I select apply update from adb, in the bottom of the screen it reads: Now send the package you want to apply to the device with "adb sideload <filename>"...
So maybe we can try the zip to wipe dalvik and cache?

Hmm maybe without the "/" at the end of the last folder directory. That error: closed massage could mean that your adb drivers need to be updated/re-installed (if sideload mode is not detected in the list devices command) or that the command is not allowed in the current state of the device.

 

[lunatic59]

okay, just for argument's sake type the following into the command prompt ...

adb shell ls /sdcard/DCIM/Camera

and see if it can at least see the files

 

[jGagliarde]

Same error for everything.

 

[lunatic59]

okay (stupid Google) it looks like the sideload option ONLY lets you sideload apps and updates. I'm running out of ideas here.

 

[Incakola]

What formats are updates? tgz or zip?

 

[lunatic59]

Sideloads are .zip. If you are flashing with fastboot, they are .tgz (I think )

 

[codesplice]

Was your device ever encrypted by chance?

 

[jGagliarde]

Was your device ever encrypted by chance?

Well I have never done anything like that in the device so I'd say no.

 

[codesplice]

I just ask because the TWRP password prompt (and subsequent inability to mount any file systems) is "normal" behavior for encrypted device. I wonder if the series of bootloops resulted in some manner of data corruption that prevents the recovery from access the data?

Forgive me if it's been mentioned already, but your best bet is probably going to be flashing the factory image as a whole. That will also wipe/format the filesystems to eliminate any errors. You'll lose your data, but it sounds like that data is inaccessible anyway, and it should at least get you booting again.

 

[lunatic59]

The OP was completely stock, no root or unlocked bootloader and updated from Kit Kat to Lollipop using the OTA. If I'm not mistaken, the OTA does not encrypt unencrypted devices so if he wasn't encrypted to begin with, he wouldn't be now.

At least we know Android security works.

 

[Incakola]

Since it's looking bad already, I tried testing a flashable zip to wipe caches and it seemed to work on clearing it but your stock recovery is having problems mounting these partitions so it may not work for you. You may need to rename it "update."

 

[jGagliarde]

I just ask because the TWRP password prompt (and subsequent inability to mount any file systems) is "normal" behavior for encrypted device. I wonder if the series of bootloops resulted in some manner of data corruption that prevents the recovery from access the data?

Forgive me if it's been mentioned already, but your best bet is probably going to be flashing the factory image as a whole. That will also wipe/format the filesystems to eliminate any errors. You'll lose your data, but it sounds like that data is inaccessible anyway, and it should at least get you booting again.

I seems like that's the only option. We were just trying to recover my data before doing the factory reset. I just got my hopes up when Inkacola mentioned that it might be possible to make a .zip that will probably correct the errors and keep the data, but maybe that's very difficult to do.

 

[lunatic59]

Since it's looking bad already, I tried testing a flashable zip to wipe caches and it seemed to work on clearing it but your stock recovery is having problems mounting these partitions so it may not work for you.

Since we're getting closer to a complete wipe, it's worth a try.

 

[jGagliarde]

Since it's looking bad already, I tried testing a flashable zip to wipe caches and it seemed to work on clearing it but your stock recovery is having problems mounting these partitions so it may not work for you. You may need to rename it "update."

And how do I do that? haha

 

[Incakola]

And how do I do that? haha

Go back to the same setup you had before when trying those adb commands. Have the recovery set to adb mode (apply update), then open cmd again in the same directory as files in plateform-tools. Move the test.zip in there as well (rename it update), then on cmd type "adb devices" make your phone is detected, then "adb sideload update.zip."

 

[jGagliarde]

It does not work. "Total xfer: 0.00x".
And in the device:
E:failed to mount /cache (Invalid argument)
E: failed to mount /cache
E: failed to set up expected mounts for install; aborting
Instalation aborted.
And a wall of E: failed etc etc

It seems like there is no other option. I'll lose all my data. Even so, I would like to say that I can't thank you all enough for what you did. I didn't even know there were such helpful people out here. Thank you very much for everything.

Is it to much to ask how do I do the factory reset? Is it just by selecting "wipe data/factory reset" and it's done?

 

[codesplice]

Is it to much to ask how do I do the factory reset? Is it just by selecting "wipe data/factory reset" and it's done?

You can try that, but I'm not sure that it will fix any file system corruption. I'd try that first, but if that fails you'll probably need to do the whole factory image thing. Here's a handy guide on that: http://androidforums.com/android-sy...e-how-flash-nexus-factory-image-manually.html

 

[jGagliarde]

You can try that, but I'm not sure that it will fix any file system corruption. I'd try that first, but if that fails you'll probably need to do the whole factory image thing. Here's a handy guide on that: http://androidforums.com/android-sy...e-how-flash-nexus-factory-image-manually.html

Thank you. I'll let you all know how it goes.

 

[codesplice]

We're all rooting for you!

 

[lunatic59]

We're all rooting for you!

Pun intended?

 

[jGagliarde]

We're all rooting for you!

As you imagined, the factory reset didn't work. I'll try flashing the factory image.
I was reading the steps and this scared the shit out of me.
Step 9: We will now flash the bootloader. It is important that you do not disconnect the device or mess with it during this step or else you hard brick the device.

Wish me luck.

 

[codesplice]

Pun intended?

Pun is always intended.

As you imagined, the factory reset didn't work. I'll try flashing the factory image.
I was reading the steps and this scared the shit out of me.
Step 9: We will now flash the bootloader. It is important that you do not disconnect the device or mess with it during this step or else you hard brick the device.

Wish me luck.

Eh, don't be too scared - flashing the bootloader is a super-quick process that will be over in a second or two.

No pressure though!