Hi.
I just bought used Nexus 5. Everything worked flawlessly until I managed to discharge the battery to 0%. When charging, the phone started looping at the "Google" screen, rebooting every ~2 seconds. (I left it like that for full duration of charging, about 2 hours). It continued rebooting after unplugging charger cable. I think i fixed it by mashing the power button few times.
Now, I'm unable to boot system, mount any of the partitions or load any images in fastboot mode...
Recovery takes few minutes to load but shows 100% battery.
Device info:
* hammerhead D821(E) 32GB
* HW Version: rev_11
* Bootloader version: HHZ20h
* Lock State - Unlocked
* Secure Boot - Enabled
* Device tampered: true
* Device Unlocked: true
* off-mode-charge: true
Issues:
* permanent boot loop when loading system (i even left it overnight to check if it eventually loads - 10h+ no luck)
* TWRP takes few minutes to load and works really slow. no partitions can be mounted. ADB shell works (i don't know any commands).
* Flashing factory image fails. fastboot uploading okay. writing fails (FAILED (remote: flash write failure))
Edit:
* I'm able to load stock recovery via fastboot boot recovery.img (.img from google factory images).
Errors:
Code:
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
Per this thread, flashing cache.img in fastboot fails:
Code:
fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.210s]
sending 'cache' (13348 KB)...
OKAY [ 0.629s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 1.023s
Edit2:
Per this thread, reapairing data gives error:
Code:
adb shell
~ # [6ne2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/platform/msm_sdcc.1/by-name/userdata: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
yes
e2fsck: unable to set superblock flags on /dev/block/platform/msm_sdcc.1/by-name/userdata
/dev/block/platform/msm_sdcc.1/by-name/userdata: ********** WARNING: Filesystem still has errors **********
Doing the same operation, but directly from TWRP:
Code:
sbin/e2fsck -fp /dev/block/mmcblk0p28 process ended with ERROR: 4
Unable to repair Data.
In TWRP:
Looks like I can mount /system - it doesn't throw any errors.
Mounting MTP freezes TWRP, but doesn't throw any errors. On PC, device is visible, but no memory.
Mounting /Data freezes TWRP for few seconds and throws error (failed to mount /data (Invalid argument))
Mounting /cache freezes TWRP briefly and throws error (failed to mount /cache (Invalid argument))
Mounting /persist throws error (failed to mount /persist (Invalid argument))
"Select Storage" shows "Internal Storage (0mb)"
Is my memory chip really dead? Could it be due to hidden flaw in my phone? Could it all break by just draining battery to 0%?
Some screenshots attached:
Is my eMMC chip fried?
Have you tried to flash stock via Nexus Root Toolkit? Wug's toolkit should help you out.
Rondeau7 said:
Have you tried to flash stock via Nexus Root Toolkit? Wug's toolkit should help you out.
Click to expand...
Click to collapse
Code:
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.507s
rebooting into bootloader...
OKAY [ 0.120s]
finished. total time: 0.122s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 1.609s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.835s
rebooting into bootloader...
OKAY [ 0.112s]
finished. total time: 0.113s
target reported max download size of 1073741824 bytes
sending 'boot' (9156 KB)...
OKAY [ 0.493s]
writing 'boot'...
OKAY [ 0.762s]
finished. total time: 1.258s
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.210s]
sending 'cache' (13348 KB)...
OKAY [ 0.629s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 1.023s
target reported max download size of 1073741824 bytes
sending 'recovery' (10014 KB)...
OKAY [ 0.522s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.704s
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.117s
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
target reported max download size of 1073741824 bytes
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.158s
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
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.211s
rebooting...
finished. total time: 0.002s
Failed. I think I know why - these partitions are invisible / not existent / corrupted... picture in description.
Is there some way to try reformat / repartition the eMMC chip?
MarcysVonEylau said:
Code:
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.507s
rebooting into bootloader...
OKAY [ 0.120s]
finished. total time: 0.122s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 1.609s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.835s
rebooting into bootloader...
OKAY [ 0.112s]
finished. total time: 0.113s
target reported max download size of 1073741824 bytes
sending 'boot' (9156 KB)...
OKAY [ 0.493s]
writing 'boot'...
OKAY [ 0.762s]
finished. total time: 1.258s
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.210s]
sending 'cache' (13348 KB)...
OKAY [ 0.629s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 1.023s
target reported max download size of 1073741824 bytes
sending 'recovery' (10014 KB)...
OKAY [ 0.522s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.704s
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.117s
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
target reported max download size of 1073741824 bytes
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.158s
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
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.211s
rebooting...
finished. total time: 0.002s
Failed. I think I know why - these partitions are invisible / not existent / corrupted... picture in description.
Is there some way to try reformat / repartition the eMMC chip?
Click to expand...
Click to collapse
https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
Saw this before. The thing is I I cannot get the device to show up as "Qualcomm HS-USB QDLoader 9008", or anything COM port-y. In fastboot it shows up like that:
Edit: I read more about it. Looks like a solution, but how to enter that mode?
Follow the directions on the guide from that link.
Okay, then you must help me. I get stuck at step 3:
Select the Com Port you see in Device manager
Click to expand...
Click to collapse
My device doesn't show up as a COM device.
Same error here. Did you get it sort out?
---------- Post added at 03:52 AM ---------- Previous post was at 03:08 AM ----------
MarcysVonEylau said:
Okay, then you must help me. I get stuck at step 3:
My device doesn't show up as a COM device.
Click to expand...
Click to collapse
You have to turn the device off and then press volume up + volume down + Power.
You should be looking at the device manager while pressing the buttons.
When it appears under PORTS let go the buttons.
By the way it did not fix our problem.
It didn't work for me. Nevermind, the phone is in service undergoing memory replacement.
I owe you all an update. Memory replacement didn't work. Most likely the memory controller in the processor itself is fried. Bricked.
what is to be done? you can throw it away?
I also have a nexus 5 who died today,suddenly. I was dowloading an update from google play and just freeze.
On restart, only show the google logo and stay that way. I can enter fastboot mode and tried to reflash with Wug Nexus Toolkit but without succes. It gives me the same errors like in you're post above.
What should I do? :/
Yes, in my case it's absolutely bricked. I don't think a software update would brick it in the same way though. I cannot assist you, but keep trying
Well, I managed to revive him! As i said before it was stuck on Google logo and I could only enter on fastboot mode. Recovery wasn't working. The phone had unlocked bootloader before the brick.
What I did:
1. Open Nexus Root Toolkit v 2.1.9
2. Advanced Utilities > Launch
3. Started the phone on Fastboot mode (volume down + power button) and connect to pc
4. First I tried to boot Custom Recovery temporarily and I saw it was working.
5. Fastboot Erase > checked all!
6. Closed the window
7. Flash Stock + Unroot with current status: Soft-Bricked|Bootloop
8. All finished ok! Single problem: operation wipes all user data and can't be recovered.
Hope this helps someone!
Related
Hi guys,
I woke up to find my Nexus off, still plugged in, which was strange. When i tried to turn it on, the Google Logo appeared, then the 4 Dots as per Marshmallow Boot animation...only they remained there 35 mins after I attempted to put on the phone.
I figured something was up with the boot, so I left it for a while after restarting, but and it was still stuck.
Since then I've tried reloading Stock Roms, (From KitKat to Marshmallow), installing custom recovery and trying anything I could find online to try to get this to work, but sadly I haven't been able to.
If i try to Reset, I get failed messages on some partitions.
I'll attach some logs showing the messages from some of these attempts.
Can anyone assist or help diagnose?
Attempt at Flashing KitKat with Nexus Root Toolkit
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target reported max download size of 1073741824 bytes
sending 'bootloader' (2508 KB)...
OKAY [ 0.285s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.487s
rebooting into bootloader...
OKAY [ 0.129s]
finished. total time: 0.130s
target reported max download size of 1073741824 bytes
sending 'radio' (45409 KB)...
OKAY [ 1.627s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.854s
rebooting into bootloader...
OKAY [ 0.119s]
finished. total time: 0.120s
target reported max download size of 1073741824 bytes
sending 'boot' (8700 KB)...
OKAY [ 0.494s]
writing 'boot'...
OKAY [ 0.733s]
finished. total time: 1.230s
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.211s]
sending 'cache' (13348 KB)...
OKAY [ 0.629s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 1.023s
target reported max download size of 1073741824 bytes
sending 'recovery' (9284 KB)...
OKAY [ 0.504s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.687s
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.115s
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
target reported max download size of 1073741824 bytes
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.186s
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
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.214s
rebooting...
finished. total time: 0.003s
If you require more information, ask and I will provide where I can.
did you try to flash the factory image?
Inviato dal mio P6000 Pro utilizzando Tapatalk
Terfysgol said:
did you try to flash the factory image?
Inviato dal mio P6000 Pro utilizzando Tapatalk
Click to expand...
Click to collapse
Yup, I tried flashing Stock Roms aka Factory Images for KitKat, Lollipop and Marshmallow as indicated in my original post.
Did you flash the userdata.img file and immediately boot to recovery to perform a factory wipe before booting the rom for the first time?
audit13 said:
Did you flash the userdata.img file and immediately boot to recovery to perform a factory wipe before booting the rom for the first time?
Click to expand...
Click to collapse
I did, and this also produces the Fails as before.
Could be a failed emmc issue.
If erasing the cachce, userdata, and factory reset don't work, it doesn't look good for the memory chip.
audit13 said:
Could be a failed emmc issue.
If erasing the cachce, userdata, and factory reset don't work, it doesn't look good for the memory chip.
Click to expand...
Click to collapse
I'm beginning to think this may be the case
Have you got an old nandroid that you know that works?
Inviato dal mio P6000 Pro utilizzando Tapatalk
I had similar issue but at least I could boot into bootloader to do this :
http://forum.xda-developers.com/showthread.php?t=2513701
I had the failed also then went to step 2 and did that:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader C:\image-hammerhead-krt16m\bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:\image-hammerhead-krt16m\radio.img
fastboot reboot-bootloader
fastboot flash system C:\image-hammerhead-krt16m\system.img
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
(Note: this command will wipe your device (including \sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:\image-hammerhead-krt16m\boot.img
fastboot flash recovery C:\image-hammerhead-krt16m\recovery.img
*tip* Substitute lastest images by dragging and dropping them into cmd window, tip** hit arrow up on keypad to enter in last text to save a bunch of typing
It took FOREVER to boot but it did come back. BUT I have weird fc's and rando0m turn offs so I suspect new phone is coming.
I did phone the google and they connected me with LG for a repair option which will come back in max 9 days but I think even 100 bucks or whatever the cost ( they will phone with tally ) is more than the phone is worth.
Read the whole of the link I sent and Thank abaaaabbbb63 for his work
YMMV HTH
Zo0
Hi everybody. First at all i'm french, so sorry for my english.
My nexus 5 won't boot, i'm stuck at the animated bootanimation.
I've tried a wipe but in my recovery, i've got "no command" and the phone reboot automatically within 6 or 10 seconds.
The hold power then push vol + and then release power... no reaction and reboot.
So here it is, the time to flash stock but during the process, can't erase cache, and userdata. Also failed flash cache and userdata.
System boot bootloader and recovery successfuly flashed but no changes.
I've tried to flash recovery only and succes but no change still on recovery stock and no command.
So what's wrong with this phone.
Does somebody encountered this problem and solved it ? Any idea or advice please.
Thanks
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.509s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.126s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.613s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.839s
rebooting into bootloader...
OKAY [ 0.119s]
finished. total time: 0.120s
target reported max download size of 1073741824 bytes
sending 'boot' (9146 KB)...
OKAY [ 0.492s]
writing 'boot'...
OKAY [ 0.762s]
finished. total time: 1.256s
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.211s]
sending 'cache' (13348 KB)...
OKAY [ 0.629s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 1.024s
target reported max download size of 1073741824 bytes
sending 'recovery' (10004 KB)...
OKAY [ 0.521s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.704s
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.123s
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
target reported max download size of 1073741824 bytes
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.170s
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
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.212s
rebooting...
finished. total time: 0.002s
i'm also have the same problem with my nexus 5 ! any news any solutions ?
unlock ur bootloader if not unlocked -_-
then flash custom recovery{latest twrp recommended}
then flash a custom rom if the rom dosent flash then go in advance menu and mount System,data,cache,and firmware . then try flash a custom rom again!
PHONE BOOTS UP
if these steps dnt work then bad eMMC CHIP OR IT CAN BE DEAD
pranavmali, my bootloader unlocked so can i flash latest twrp without rooting my device ?
Yes u can install custom recovery without root:
Boot into bootloader and connect ur phone to PC
Then flash the recovery via fastboot (adb not supported when ur in bootloader mode)eg.
fastboot flash recovery (name on recovery).img
After that type
fasboot reboot recovery
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.
please, help
nexus 5 turn on, but no UNBRIK
i try NRT, UNIFIELD , flashtools ( no conect )
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.210s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.416s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 1.562s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.792s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
target reported max download size of 1073741824 bytes
sending 'boot' (9156 KB)...
OKAY [ 0.411s]
writing 'boot'...
OKAY [ 0.764s]
finished. total time: 1.176s
target reported max download size of 1073741824 bytes
sending 'recovery' (10014 KB)...
OKAY [ 0.429s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.615s
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 36.369s
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
see images in link
http://imgur.com/a/kX1YE
Is the bootloader unlocked? If yes, relock the bootloader, and reboot the phone back into download mode. If the bootloader is unlocked again, the memory chip is damaged and can be fixed with a motherboard replacement.
Have you tried flashing a stock KK ROM?
audit13 said:
Is the bootloader unlocked? If yes, relock the bootloader, and reboot the phone back into download mode. If the bootloader is unlocked again, the memory chip is damaged and can be fixed with a motherboard replacement.
Have you tried flashing a stock KK ROM?
Click to expand...
Click to collapse
how to enter download mode ? only bootlooader lock enter ??
Download or fastboot mode is the screen where you unlock or relock the bootloader.
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.