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
Related
I flashed a modified 44s ota over a 33r ROM (stock) file to my device and lost the ability to boot. Whenever I try to flash via fastboot I get the error: "FAILED (remote: partition table doesn't exist)"
Does anyone have a way of repairing this? Would love to start using this device again. Thanks in advance :good:
emmanuel_baez said:
I flashed a modified 44s ota over a 33r ROM (stock) file to my device and lost the ability to boot. Whenever I try to flash via fastboot I get the error: "FAILED (remote: partition table doesn't exist)"
Does anyone have a way of repairing this? Would love to start using this device again. Thanks in advance :good:
Click to expand...
Click to collapse
Do this at your own risk:
Go into fastboot and flash 38R. (Available at current time on cygen's site) Flash everything including userdata. Reboot and you should be at the home screen. Then when you are here ota update through settings. Not recommended to modify ota, just do it after the ota if possible. (You might have to unlock the bootloader to follow this guide)
skyguy126 said:
Do this at your own risk:
Go into fastboot and flash 38R. (Available at current time on cygen's site) Flash everything including userdata. Reboot and you should be at the home screen. Then when you are here ota update through settings. Not recommended to modify ota, just do it after the ota if possible. (You might have to unlock the bootloader to follow this guide)
Click to expand...
Click to collapse
I don't think that's going to work, he's borked his partitions. And the modified OTA wasn't technically the problem. The problem is that he flashed an OTA on top of an incorrect preceding build. It should have gone 33>38>44 but instead went 33>44. Because it was a modified OTA with a modified installer script, the safeguard that would normally stop such a mistake from happening had been disabled. Modified OTA's are perfectly fine, as long as you take them in the right sequence.
Transmitted via Bacon
He still has access to fastboot which means he can reflash stock firmware.
Not with borked partitions.
Transmitted via Bacon
timmaaa said:
Not with borked partitions.
Transmitted via Bacon
Click to expand...
Click to collapse
Shouldn't it work with the Official signed 44s Fastboot Image that was released yesterday by Cyanogen?
Not if the partitions are borked. It can't flash to a partition table that doesn't exist. It's like trying to serve dinner onto thin air, it has nowhere to go.
Transmitted via Bacon
And there will be no way to repartition? Guess that something like using parted should work on nand, assumed the right partition tables are known...
It's possible, but getting it done can be tricky. I myself have zero experience in trying to repartition.
Transmitted via Bacon
Note to self: triple check the version numbers before flashing lol
Sorry op I have no constructive feedback
Sent from my A0001 using XDA Free mobile app
timmaaa said:
I don't think that's going to work, he's borked his partitions. And the modified OTA wasn't technically the problem. The problem is that he flashed an OTA on top of an incorrect preceding build. It should have gone 33>38>44 but instead went 33>44. Because it was a modified OTA with a modified installer script, the safeguard that would normally stop such a mistake from happening had been disabled. Modified OTA's are perfectly fine, as long as you take them in the right sequence.
Transmitted via Bacon
Click to expand...
Click to collapse
@timmaaa you were correct I attempted that and it failed. I resolved my problem by flashing calkulin's stock mod 44s. I've come across another issue now. Occasionally the devices screen won't come on at all. I'll have to completely reboot the phone for it to work. Is this an issue on 44s or is there another problem under the hood?
emmanuel_baez said:
@timmaaa you were correct I attempted that and it failed. I resolved my problem by flashing calkulin's stock mod 44s. I've come across another issue now. Occasionally the devices screen won't come on at all. I'll have to completely reboot the phone for it to work. Is this an issue on 44s or is there another problem under the hood?
Click to expand...
Click to collapse
I am running CM11 nightlies, and this issue happens to me (and also on my nexus 5 using milestone builds) ONLY when I am using the Ondemand governor. If you're using that, try changing and see what happens.
Ah yes I am using ondemand. I switched it from interactive last night. Didn't think of that thanks I'll test it.
Sent from my A0001 using XDA Free mobile app
emmanuel_baez said:
Ah yes I am using ondemand. I switched it from interactive last night. Didn't think of that thanks I'll test it.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Please make sure to report back, could be valuable info. I haven't found anyone else discussing this potential cause of the problem, but others do seem to have it.
Sent from my A0001 using XDA Free mobile app
So far it hasn't done it since I changed back to interactive.
Sent from my A0001 using XDA Free mobile app
Hello,
I need some help with a Oneplus One that is stuck on the Cyanogen boot image. I bought this for cheap thinking that I could fix it, but 3 hours later still no luck. I have access to TWRP and Fastboot, which made me hopeful, but no access to the storage on the device.
1. TWRP: I can’t mount /data, /cache/ persist (shows E:Unable to mount ‘/data’, etc). I can mount /firmware or /system.
Trying to sideload a bunch of different roms gives me this in the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload cm12.zip
loading: 'cm12.zip'* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
2. Fastboot: trying to flash individual files with fastboot gives me “remote: flash write failure”. I’ve also gotten a “partition table doesn’t exist” error.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I tried these directions and got this:
Code:
target reported max download size of 1073741824 bytes
sending 'modem' (57361 KB)...
OKAY [ 1.802s]
writing 'modem'...
FAILED (remote: flash write failure)
finished. total time: 6.860s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
FAILED (remote: flash write failure)
finished. total time: 5.076s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.005s]
writing 'dbi'...
FAILED (remote: flash write failure)
finished. total time: 5.064s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.019s]
writing 'aboot'...
FAILED (remote: flash write failure)
finished. total time: 5.077s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.014s
target reported max download size of 1073741824 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.010s]
writing 'rpm'...
FAILED (remote: flash write failure)
finished. total time: 5.067s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
target reported max download size of 1073741824 bytes
sending 'tz' (321 KB)...
OKAY [ 0.015s]
writing 'tz'...
FAILED (remote: flash write failure)
finished. total time: 5.071s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.014s]
writing 'LOGO'...
FAILED (remote: flash write failure)
finished. total time: 5.070s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.326s]
writing 'oppostanvbk'...
FAILED (remote: flash write failure)
finished. total time: 5.394s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
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: 59914792960
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14627635
Block groups: 447
Reserved block group size: 1024
Created filesystem with 11/3661824 inodes and 275906/14627635 blocks
Cannot read image.
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 56d36153
--------------------------------------------
checking product...
OKAY [ 0.003s]
sending 'boot' (6372 KB)...
OKAY [ 0.205s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 5.297s
Press any key to exit...
From what I've read, I think Heisenberg will say that the partitions are borked, but I'm hoping I'm a little luckier than others who do not have access to fastboot or twrp. Any suggestions?
majzoob said:
Hello,
I need some help with a Oneplus One that is stuck on the Cyanogen boot image. I bought this for cheap thinking that I could fix it, but 3 hours later still no luck. I have access to TWRP and Fastboot, which made me hopeful, but no access to the storage on the device.
1. TWRP: I can’t mount /data, /cache/ persist (shows E:Unable to mount ‘/data’, etc). I can mount /firmware or /system.
Trying to sideload a bunch of different roms gives me this in the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload cm12.zip
loading: 'cm12.zip'* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
2. Fastboot: trying to flash individual files with fastboot gives me “remote: flash write failure”. I’ve also gotten a “partition table doesn’t exist” error.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I tried these directions and got this:
Code:
target reported max download size of 1073741824 bytes
sending 'modem' (57361 KB)...
OKAY [ 1.802s]
writing 'modem'...
FAILED (remote: flash write failure)
finished. total time: 6.860s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
FAILED (remote: flash write failure)
finished. total time: 5.076s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.005s]
writing 'dbi'...
FAILED (remote: flash write failure)
finished. total time: 5.064s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.019s]
writing 'aboot'...
FAILED (remote: flash write failure)
finished. total time: 5.077s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.014s
target reported max download size of 1073741824 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.010s]
writing 'rpm'...
FAILED (remote: flash write failure)
finished. total time: 5.067s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
target reported max download size of 1073741824 bytes
sending 'tz' (321 KB)...
OKAY [ 0.015s]
writing 'tz'...
FAILED (remote: flash write failure)
finished. total time: 5.071s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.014s]
writing 'LOGO'...
FAILED (remote: flash write failure)
finished. total time: 5.070s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.326s]
writing 'oppostanvbk'...
FAILED (remote: flash write failure)
finished. total time: 5.394s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
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: 59914792960
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14627635
Block groups: 447
Reserved block group size: 1024
Created filesystem with 11/3661824 inodes and 275906/14627635 blocks
Cannot read image.
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 56d36153
--------------------------------------------
checking product...
OKAY [ 0.003s]
sending 'boot' (6372 KB)...
OKAY [ 0.205s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 5.297s
Press any key to exit...
From what I've read, I think Heisenberg will say that the partitions are borked, but I'm hoping I'm a little luckier than others who do not have access to fastboot or twrp. Any suggestions?
Click to expand...
Click to collapse
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
try OTG cable ... ?
Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
I messed up my One by deleting stuff I should not have... it would not read the internal "sd card" memory at all... so nothing would flash to the phone. I had fastboot and TWRP working. I tried this kit and it only partially worked for me, but did get recovery going. What I did get to work is by connecting an on-the-go cable to it and put the files to flash on a flash drive. The phone will find it in TWRP if you set it up to read the OTG cable. Then flash away something that will boot up... then go from there with the ROM you want to use. Using the Caulkin's ROM mentioned earlier will get it at least running. This worked for me, and may work for you too.
Jimmy Rudedog said:
I messed up my One by deleting stuff I should not have... it would not read the internal "sd card" memory at all... so nothing would flash to the phone. I had fastboot and TWRP working. I tried this kit and it only partially worked for me. What I did get to work is by connecting an on-the-go cable to it and put the files to flash on it. The phone will find it in TWRP if you set it up to read the OTG cable. Then flash away something that will boot up... then go from there with the ROM you want to use. Using the Caulkin's ROM mentioned earlier will get it at least running. This worked for me, and may work for you too.
Click to expand...
Click to collapse
That won't work in this situation, he hasn't merely deleted everything, the partition table is borked.
Thanks for the reply. I'd previously read that, but thought it didn't apply because I have fastboot and recovery. I'm trying it now, but I can't get the device to show up in Device Manager. The phone goes to the charger screen when connected and it shows up as MTP USB Device. I tried seeing if it would show up on the downloadtool.exe he mentions, but no go.
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.
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!