Database Info

Messed up internals?

Cannot copy anything into my nexus 5 it gives an error, device stopped responding or has been disconnected. I am in stock 4.4.4, i tried to reflash stock images but it takes a lot of time to flash image especially the system image. Takes more than 20 mins! I previously used adb push while in twrp but could not make the push so i had to (ctrl+c) to break it. What could be the problem?

Tried different cable / USB port / computer?

rootSU said:
Tried different cable / USB port / computer?
Click to expand...
Click to collapse
Checked different ports and USB cables.
The thing is right after I flash or reset via stock recovery I could copy into the phone, after a few tried especially after enabling/disabling usb debugging I get the error. I can open the memory and browse through the phone in the system but i simply cannot copy into it after the first 2-3 times.

gamer.11 said:
Checked different posts and USB cables.
The thing is right after I flash or reset via stock recovery I could copy into the phone, after a few tried especially after enabling/disabling usb debugging I get the error. I can open the memory and browse through the phone in the system but i simply cannot copy into it after the first 2-3 times.
Click to expand...
Click to collapse
Weird - really not sure. A full flashing factory would be my best advice, but if you cant do that...

rootSU said:
Weird - really not sure. A full flashing factory would be my best advice, but if you cant do that...
Click to expand...
Click to collapse
I'm returning back from lollipop to kitkat. I am sure the flashing of stock images do not take so much time. It takes forever for the system.img and userdata.img to flash both using flash-all.bat and doing them individually.

Are the time duration of the flashes proper? This is the 4th time I'm flashing, are the finish times reasonable this time?
Code:
sending 'bootloader' (2508 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
OKAY [ 0.499s]
finished. total time: 0.796s
rebooting into bootloader...
OKAY [ 0.062s]
finished. total time: 0.062s
sending 'radio' (45409 KB)...
OKAY [ 1.950s]
writing 'radio'...
OKAY [ 3.104s]
finished. total time: 5.054s
rebooting into bootloader...
OKAY [ 0.062s]
finished. total time: 0.062s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-2.0.50.1.17
Serial Number........: 047d536313afb183
--------------------------------------------
checking product...
OKAY [ 0.109s]
checking version-bootloader...
OKAY [ 0.094s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (8700 KB)...
OKAY [ 0.530s]
writing 'boot'...
OKAY [ 0.749s]
sending 'recovery' (9284 KB)...
OKAY [ 0.624s]
writing 'recovery'...
OKAY [ 0.780s]
erasing 'system'...
OKAY [ 0.905s]
sending 'system' (721400 KB)...
OKAY [ 29.437s]
writing 'system'...
OKAY [ 48.984s]
erasing 'userdata'...
OKAY [ 13.759s]
sending 'userdata' (139109 KB)...
OKAY [ 5.819s]
writing 'userdata'...
OKAY [ 9.344s]
erasing 'cache'...
OKAY [ 0.562s]
sending 'cache' (13348 KB)...
OKAY [ 0.764s]
writing 'cache'...
OKAY [ 1.061s]
rebooting...
finished. total time: 114.099s
Press any key to exit...
Edit: Still getting the error. This was easily fixable for devices with external storage but what about our?

gamer.11 said:
Are the time duration of the flashes proper? This is the 4th time I'm flashing, are the finish times reasonable this time?
Code:
sending 'bootloader' (2508 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
OKAY [ 0.499s]
finished. total time: 0.796s
rebooting into bootloader...
OKAY [ 0.062s]
finished. total time: 0.062s
sending 'radio' (45409 KB)...
OKAY [ 1.950s]
writing 'radio'...
OKAY [ 3.104s]
finished. total time: 5.054s
rebooting into bootloader...
OKAY [ 0.062s]
finished. total time: 0.062s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-2.0.50.1.17
Serial Number........: 047d536313afb183
--------------------------------------------
checking product...
OKAY [ 0.109s]
checking version-bootloader...
OKAY [ 0.094s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (8700 KB)...
OKAY [ 0.530s]
writing 'boot'...
OKAY [ 0.749s]
sending 'recovery' (9284 KB)...
OKAY [ 0.624s]
writing 'recovery'...
OKAY [ 0.780s]
erasing 'system'...
OKAY [ 0.905s]
sending 'system' (721400 KB)...
OKAY [ 29.437s]
writing 'system'...
OKAY [ 48.984s]
erasing 'userdata'...
OKAY [ 13.759s]
sending 'userdata' (139109 KB)...
OKAY [ 5.819s]
writing 'userdata'...
OKAY [ 9.344s]
erasing 'cache'...
OKAY [ 0.562s]
sending 'cache' (13348 KB)...
OKAY [ 0.764s]
writing 'cache'...
OKAY [ 1.061s]
rebooting...
finished. total time: 114.099s
Press any key to exit...
Edit: Still getting the error. This was easily fixable for devices with external storage but what about our?
Click to expand...
Click to collapse
Yes your times are good. Did you reboot the computer? I wonder if it is a driver issue. Maybe uninstall all drivers, reboot and try again?

rootSU said:
Yes your times are good. Did you reboot the computer? I wonder if it is a driver issue. Maybe uninstall all drivers, reboot and try again?
Click to expand...
Click to collapse
Will try that out too.

Nexus 5 won't turn on after trying a failed stock rom installation

So, here's the situation:
I flashed a custom ROM to my nexus 5 and was using it for the last few months. But today, I decided to rollback to latest stock ROM. And I double clicked "flash-all.sh" and it failed after few seconds. I could not see what happened so I again ran the executable under terminal and seen it failed again. I just remmebered that I hadn't unlocked the bootloader before running the script. Now, the phone is not turning on at all. It only vibrates if I hold the power button for some seconds, 6 seconds actually and if I hold the button for longer times, it keeps vibrating every 6 seconds.
I am not even getting the Google logo thing.
What can I do to resolve the issue?
EDIT 1:
I guese fastboot is working;
[email protected]:~/Hammerhead/hammerhead-lmy48b# nexus-fastboot flash bootloader bootloader-hammerhead-hhz12h.img
< waiting for device >
target reported max download size of 1073741824 bytes
sending 'bootloader' (3119 KB)...
OKAY [ 0.353s]
writing 'bootloader'...
OKAY [ 0.503s]
finished. total time: 0.856s
Click to expand...
Click to collapse

Is the back light of fhe screen turns on when the phone vibrate?
Tapatalk-kal küldve az én Nexus 5-el

bitdomo said:
Is the back light of fhe screen turns on when the phone vibrate?
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
yes, I just noticed that I can see the black and blank screen turning on on some occasions and a little light on it. But no, text or picture on it. However, It's turns on only when connected to PC.
But, I don't think it lights up every times when it vibrates though.
And I just tried to reflash everything using "flash-all.sh" and it seemed like it worked this time. Here's the log that I got:
[email protected]:~/Hammerhead/hammerhead-lmy48b# '/root/Hammerhead/hammerhead-lmy48b/flash-all.sh'
< waiting for device >
target reported max download size of 1073741824 bytes
sending 'bootloader' (3119 KB)...
OKAY [ 0.346s]
writing 'bootloader'...
OKAY [ 0.513s]
finished. total time: 0.859s
rebooting into bootloader...
OKAY [ 0.132s]
finished. total time: 0.132s
< waiting for device >
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 2.240s]
writing 'radio'...
OKAY [ 3.118s]
finished. total time: 5.358s
rebooting into bootloader...
OKAY [ 0.123s]
finished. total time: 0.123s
< waiting for device >
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: 0706e769344beb13
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8980 KB)...
OKAY [ 0.630s]
writing 'boot'...
OKAY [ 0.770s]
sending 'recovery' (9696 KB)...
OKAY [ 0.701s]
writing 'recovery'...
OKAY [ 0.808s]
erasing 'system'...
OKAY [ 1.122s]
sending 'system' (1021744 KB)...
OKAY [ 48.046s]
writing 'system'...
OKAY [ 68.594s]
erasing 'userdata'...
OKAY [ 6.578s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
sending 'userdata' (137318 KB)...
writing 'userdata'...
OKAY [ 16.029s]
erasing 'cache'...
OKAY [ 0.565s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 2.109s]
rebooting...
finished. total time: 146.777s
[email protected]:~/Hammerhead/hammerhead-lmy48b#
Click to expand...
Click to collapse
But, even after this the screen did not show anything at all. So, I pressed the power button and it vibrates and then I connected to wall charger and it just did the back light thing once and then light went off again.

stts510 said:
yes, I just noticed that I can see the black and blank screen turning on on some occasions and a little light on it. But no, text or picture on it. However, It's turns on only when connected to PC.
But, I don't think it lights up every times when it vibrates though.
And I just tried to reflash everything using "flash-all.sh" and it seemed like it worked this time. Here's the log that I got:
But, even after this the screen did not show anything at all. So, I pressed the power button and it vibrates and then I connected to wall charger and it just did the back light thing once and then light went off again.
Click to expand...
Click to collapse
I want to ask you to try out lg flashtool method, but I see you are using Linux. Do you have a windows PC? If you happen to have then please flash any stock rom with fastboot mode, but LMY48B. Because in LMY48B the download mode got disabled. Then check my signature you will find the guide for lg flashtool there

bitdomo said:
I want to ask you to try out lg flashtool method, but I see you are using Linux. Do you have a windows PC? If you happen to have then please flash any stock rom with fastboot mode, but LMY48B. Because in LMY48B the download mode got disabled. Then check my signature you will find the guide for lg flashtool there
Click to expand...
Click to collapse
yes. I can do that. Will post back the results.
I am gonna download LMY47I then. Will take some time.

bitdomo said:
I want to ask you to try out lg flashtool method, but I see you are using Linux. Do you have a windows PC? If you happen to have then please flash any stock rom with fastboot mode, but LMY48B. Because in LMY48B the download mode got disabled. Then check my signature you will find the guide for lg flashtool there
Click to expand...
Click to collapse
Ahh! this seems weird. I just made a call to the number that's still in the nexus 5 and I could hear it ringing. Also, I connected to windows PC and it appeared as "Nexus 5" under "Portable Devices" in devices manager. I can also access the internal memory of the devices via MTP.

hi ! do you try the nexus root toolkit ,i do sometime super wrong and with that i fix it and running like new

rantoca said:
hi ! do you try the nexus root toolkit ,i do sometime super wrong and with that i fix it and running like new
Click to expand...
Click to collapse
nexus root toolkit is probably just a GUI thing for what I have been trying under terminal, if I am not mistaken. So, I doubt that is gonna do anything.
bitdomo said:
I want to ask you to try out lg flashtool method
Click to expand...
Click to collapse
Just did that and that did not work either. Display is still blank. I did the flashing successfully according to the logs I got in LG flash tool.

Did you try volume down with power simultaneously before the phone boots up?

nitramus said:
Did you try volume down with power simultaneously before the phone boots up?
Click to expand...
Click to collapse
Indeed. And if you will see my second post's log file, you will know I have access to bootloader. Only thing is happening is nothing on the display, still display turns on.
Cleared cache, full reset from bootloader and recovery. No luck.
Any more answers???

My phone stopped working all of the sudden

Hello,
Yesterday around midnight my phone suddenly stopped working. I wasn't using it, it was just sitting on my desk and had been for at least half an hour.
When I boot it, it stays stuck on the boot animation.
Until yesterday it was running a custom built version of CM12.1 (from this thread: http://forum.xda-developers.com/goo...unofficial-cm12-cmhammerhead-nexus-5-t2938502)
With a ElementalX-N5-4.09 kernel.
I tried:
Reflashing the ROM
Wiping and Reflashing the ROM
Wiping and Reflashing the ROM, without ElementalX
Wiping and Flashing an older version
Wiping and formating of user data too + Reflashing
complete reset by doing fastboot oem lock/unlock
flashing of the factory image of Android 6
Each time the result is the same.
When the phone was still running cyanogen I had adb while it was booting (that's no longer the case) and I saw nothing striking ... it would have one (pc) screen worth of log (logcat) and then nothing it would just stop.
I couldn't spot anything in kernel logs either (dmesg/last_kmsg).
The recovery is working fine ... I was able to start an ssh server and use it... it's just android that won't boot...
any idea to turn my expensive paperweight back into a phone?

*Update*
I flashed Ubuntu touch and it's working fine.. flashed back Android and it's been showing me the boot animation for 30 minutes now...

After flashing stock ROM, are you erasing userdata and flashing userdata.img?

I've been using the flash-all.sh script so yes.
Here is the output after flashing LMY48M (5.1.1):
Code:
[email protected]:/.../hammerhead-lmy48m$ ./flash-all.sh
target reported max download size of 1073741824 bytes
sending 'bootloader' (3119 KB)...
OKAY [ 0.319s]
writing 'bootloader'...
OKAY [ 0.533s]
finished. total time: 0.852s
rebooting into bootloader...
OKAY [ 0.134s]
finished. total time: 0.134s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.711s]
writing 'radio'...
OKAY [ 3.111s]
finished. total time: 4.823s
rebooting into bootloader...
OKAY [ 0.137s]
finished. total time: 0.137s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: ****************
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8916 KB)...
OKAY [ 0.510s]
writing 'boot'...
OKAY [ 0.757s]
sending 'recovery' (9632 KB)...
OKAY [ 0.554s]
writing 'recovery'...
OKAY [ 0.807s]
erasing 'system'...
OKAY [ 1.053s]
sending 'system' (1021824 KB)...
OKAY [ 33.345s]
writing 'system'...
OKAY [ 68.316s]
erasing 'userdata'...
OKAY [ 6.439s]
[COLOR="Teal"]formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
sending 'userdata' (137318 KB)...
writing 'userdata'...
OKAY [ 14.056s][/COLOR]
erasing 'cache'...
OKAY [ 0.548s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.982s]
rebooting...
finished. total time: 129.192s

After using the script, try booting into stock recovery and performing another factory wipe of data and cache.
Or, before the first boot, try erasing and reflash img userdata.img file, boot into recovery, wipe again, and boot.

I tried that and it didn't work ...
However ... I flashed a kitkat factory image (4.4.4 KTU84P to be precise) ... and it works ...
Tomorow I'll try 6.0 again.

Still not much progress.
Kitkat is working but with no service ...
In kernel logs I can see this kind of things:
Code:
<3>[ 24.333162] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to locate mba.mdt
<3>[ 24.333211] smd_pkt_open failed on smd_pkt_dev id:0 - subsystem_get failed for modem
<3>[ 44.848682] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to locate mba.mdt
<3>[ 44.848937] smd_pkt_open failed on smd_pkt_dev id:0 - subsystem_get failed for modem
but I have no connectivity issue in ubuntu.
Also I noticed the hardware clock is set to 1970. I though this may be an issue.
I tried to set it to the correct date but it won't work:
Code:
localhost / # hwclock -w
hwclock: RTC_SET_TIME: Invalid argument
I tried this on a galaxy nexus and the hwclock is set at the correct date/time and the hwclock -w command works.

f4kill said:
Still not much progress.
Kitkat is working but with no service ...
In kernel logs I can see this kind of things:
Code:
<3>[ 24.333162] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to locate mba.mdt
<3>[ 24.333211] smd_pkt_open failed on smd_pkt_dev id:0 - subsystem_get failed for modem
<3>[ 44.848682] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to locate mba.mdt
<3>[ 44.848937] smd_pkt_open failed on smd_pkt_dev id:0 - subsystem_get failed for modem
but I have no connectivity issue in ubuntu.
Also I noticed the hardware clock is set to 1970. I though this may be an issue.
I tried to set it to the correct date but it won't work:
Code:
localhost / # hwclock -w
hwclock: RTC_SET_TIME: Invalid argument
I tried this on a galaxy nexus and the hwclock is set at the correct date/time and the hwclock -w command works.
Click to expand...
Click to collapse
Seems to me you now own an Ubuntu Phone. :silly:
Are you on the latest bootloader? I have a silly idea but it just might work. Install multiROM on your phone and try to install a custom stock based marshmallow rom, either as a primary or as a secondary. Good luck!

I had a nexus 5 with a broken screen, I salvaged the motherboard and now have a fully functional nexus in my pocket.
I also salvaged the camera because it was doing slightly better shots.
The second phone has a broken screen but still working so it would be nice to have it run android too
However I wanted to turn it into a small server, and had already done so with a chroot trick ... but now I'm thinking Ubuntu touch might be better suited for that
I might try tge multiROM option but I'm not too optimistic about it.
btw the hwclock thing was nothing, the other n5 had its clock in 1970 too and the same error.

My Phone might be bricked. Any help?

So I decided to flash the latest factory image available for the N5 today. I was running Build MOB30Y. I did it using Nexus Root Toolkit and I chose the 'No Wipe Mode', it says that it failed. Here's the exact error:
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.244s]
writing 'bootloader'...
OKAY [ 0.447s]
finished. total time: 0.693s
rebooting into bootloader...
OKAY [ 0.044s]
finished. total time: 0.046s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 1.541s]
writing 'radio'...
OKAY [ 3.086s]
finished. total time: 4.629s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.885s]
sending 'system' (842656 KB)...
OKAY [ 26.533s]
writing 'system'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 84.341s
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
error: file_write: write: No space left on device
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.507s]
sending 'cache' (2136 KB)...
OKAY [ 0.180s]
writing 'cache'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 0.969s
rebooting...
finished. total time: 0.003s
---------------------------------------------
Now when I boot up my phone it goes into the black screen with 'Google' on it then it turns off for a second then back to the Google screen and then it boots into custom recover (TWRP). What can I do to fix this? Thanks in advance.

Manually flash the ROM in fastboot.

audit13 said:
Manually flash the ROM in fastboot.
Click to expand...
Click to collapse
Is it possible to do that without wiping my data?

Yes, just don't flash userdata.img or wipe.
Before flashing, you might want to use twrp to back up data or copy files to your computer, then flash.

audit13 said:
Yes, just don't flash userdata.img or wipe.
Before flashing, you might want to use twrp to back up data or copy files to your computer, then flash.
Click to expand...
Click to collapse
Thanks! Hopefully this works. I've never done anything with fastboot though. I'll look it up later.

I have not used kits to flash stock rom, I always do it manually to learn the process.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

audit13 said:
I have not used kits to flash stock rom, I'm always do it manually to learn the process.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
Much appreciated! I think I'll start learning how to do things manually now. Thanks again.

audit13 said:
I have not used kits to flash stock rom, I'm always do it manually to learn the process.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
Thanks for everything! Everything is okay now.

Not being able to install ROM LOS 17. 1, stuck in TWRP

HI All , I need some help . Since I did manage to get a new battery for my broken n5, I decided to get onboarded with LOS17.1 .
Managed to get the 3.4 TWRP HH from @z3DD3r and followed the repartition process. However I am not able to enable adb, nor can I abd sideload , everytime I try to sideload I get an error 7.
Furthermore I cannot mount data partition , nor does the OTG cable work i.e. nothing comes up in my comp. I did install Google drivers / CWM USB drivers, and I do see Google nexus ADB interface popping up in the device manager(win10) however nothing gets listed as a storage/MTP device. I did try searching but not being able to get the solution . I am not able to move beyond this .
N5 doesnt have a sdcard slot either . Can any one advise how to get the LOS zip and gaps into the storage ? Only thing which is working is TWRP HH recovery from @z3DD3r. I will appreciate any help . Let me know if I need to post this in another thread. Thank you

I am not able to mount /cache and /system - it says failed when I wipe or format them .
I only have /data which can be mounted . I have searched and have seen that its to do with partition tables. Any way to get back the partition table done ?
I have checked the following links -
https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
and
https://forum.xda-developers.com/go...o-repairing-corrupted-data-partition-t2577447

quest2012 said:
I am not able to mount /cache and /system - it says failed when I wipe or format them .
(...)
Click to expand...
Click to collapse
Wipe -> Advanced Wipe -> Check "Cache" -> Repair or Change File System -> Repair File System
If that doesn't help, do it:
Wipe -> Advanced Wipe -> Check "Cache" -> Repair or Change File System -> Change File System
If your cache partition does not have ext4, set ext4.
If your cache has ext4, change it to FAT and restore it to ext4 when finished.
If something succeeds, repeat the steps for the system partition.
Good luck with the repair. :good:

Did You manage to find the solution?

Thanks , however with TWRP I get error 16 unable to repair system , same thing with cache , neither can I change the filesystem , since I think the partitions dont exist

Enteb27 said:
Did You manage to find the solution?
Click to expand...
Click to collapse
Nope, need a way to repartition as per stock .

I tried looking into various places and used the following site to get into the partition table using parted .
https://iwf1.com/how-to-re-partitio...ll-options-included-change-size-fs-type-etc/2
I followed instructions and found that cache, crypto and system partition were missing . Created the partitions and also managed to change the fs for two of them .
I referred to this page as well to know what partitions are available and what are their usual sizes.
https://forum.xda-developers.com/go...guide-repartition-nexus5-to-increase-t3509880
After all - I did a flash-all , it went through luckily . However somehow I am stuck in bootloop. Then I tried flashing twrp again , and my partitions are gone . Parted doesnt recognize my disk at all .
So close by yet so far
Log of flash all -
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.308s]
writing 'bootloader'...
OKAY [ 0.518s]
finished. total time: 0.830s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 2.036s]
writing 'radio'...
OKAY [ 3.126s]
finished. total time: 5.165s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 29146718208
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7115898
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1782368 inodes and 155902/7115898 blocks
Creating filesystem with parameters:
Size: 769654784
Block size: 4096
Blocks per group: 32768
Inodes per group: 7840
Inode size: 256
Journal blocks: 2936
Label:
Blocks: 187904
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/47040 inodes and 6087/187904 blocks
--------------------------------------------
Bootloader Version...: HHZ20h
Baseband Version.....: M8974A-2.0.50.2.30
Serial Number........: 0c35d79d02
--------------------------------------------
checking product...
OKAY [ 0.099s]
checking version-bootloader...
OKAY [ 0.099s]
checking version-baseband...
OKAY [ 0.099s]
sending 'boot' (9156 KB)...
OKAY [ 0.509s]
writing 'boot'...
OKAY [ 0.778s]
sending 'recovery' (10014 KB)...
OKAY [ 0.576s]
writing 'recovery'...
OKAY [ 0.828s]
erasing 'system'...
OKAY [ 1.486s]
sending 'system' (1020657 KB)...
OKAY [ 33.072s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 81.015s
Press any key to exit...

Finally managed to get into and redo parted , changed user fs to ext4. Ran flash all - boot.sig, recovery.sig, vendor img missing , however it ran successfully .
Tried to reboot , it booted up but got stuck at boot , the android 6 factory boot animation came up , but got stuck and switched off . Any workaround ?

Went into parted again - removed userdata partition and redid i.e. made a partition and changed the filesystem to ext4, then came out and flash-all stock , stuck in bootloop , is there any problem with the installation ?
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
OKAY [ 0.522s]
finished. total time: 0.832s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.017s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 1.630s]
writing 'radio'...
OKAY [ 3.129s]
finished. total time: 4.764s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 29146718208
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7115898
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1782368 inodes and 155902/7115898 blocks
Creating filesystem with parameters:
Size: 769654784
Block size: 4096
Blocks per group: 32768
Inodes per group: 7840
Inode size: 256
Journal blocks: 2936
Label:
Blocks: 187904
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/47040 inodes and 6087/187904 blocks
--------------------------------------------
Bootloader Version...: HHZ20h
Baseband Version.....: M8974A-2.0.50.2.30
Serial Number........: 0c35d79d02ba
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.097s]
checking version-baseband...
OKAY [ 0.097s]
sending 'boot' (9156 KB)...
OKAY [ 0.518s]
writing 'boot'...
OKAY [ 0.783s]
sending 'recovery' (10014 KB)...
OKAY [ 0.580s]
writing 'recovery'...
OKAY [ 0.823s]
erasing 'system'...
OKAY [ 1.433s]
sending 'system' (1020657 KB)...
OKAY [ 33.932s]
writing 'system'...
OKAY [ 68.950s]
erasing 'userdata'...
OKAY [ 13.845s]
sending 'userdata' (139105 KB)...
OKAY [ 4.599s]
writing 'userdata'...
OKAY [ 9.379s]
erasing 'cache'...
OKAY [ 0.668s]
sending 'cache' (13984 KB)...
OKAY [ 0.659s]
writing 'cache'...
OKAY [ 1.111s]
rebooting...
finished. total time: 138.050s
Press any key to exit...

Finally got all partitions working, being able to wipe all partitions through twrp.
All partitions are mounting
Factory image not booting, so trying crdroid 7.1.2
Installs pretty quickly the 350mb file.
However stuck with Google logo, not moving to the boot animation.
Any help will be appreciated.

Need to check power button , since that is also another issues which N5 users have faced and boot loop or getting stuck at boot solution has been replacing the power button/ switch

Closing the thread - Motherboard issue , thanks everyone for your help.