Hello all
Since nobody helped me with my mate 9, which did no sign of life, i started searching...on the mainboard.
I found the tespoint that gave me access to board, loaded fastboot in the ram, and now my MATE 9 shows in the fastboot devices.
This, i think ,is a big step for MATE 9 phones, which we might brick.
OK, so here is what i need. If it work, i promise that in maximum 1 day after testing this, i will post a guide for unbrick.
Code:
C:\Users\MONSTER>fastboot flash boot F:\dload\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (16208 KB)...
OKAY [ 0.549s]
writing 'boot'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 0.680s
This is the error style i got,when flashing boot,recovery,fastboot,and others.
Flashing system,product,vendor,vector, works.
As @Tkkg1994 posted here, https://forum.xda-developers.com/showpost.php?p=70410219&postcount=454
vrl.img really exists (i never heard of,and firstly,i thought that is URL.img ) )and may have something to do with partition table or smth like that.
I would need as many as partitions possible, since i have only those extracted from update.app.
So,please,anyone, if have time,try to help.
PS: @duraaraa - sir, i'm disturbing you again. but again,i think you can help.
What do you need, and how to help you?
Gesendet von meinem MHA-L29 mit Tapatalk
i need those img's
verlist.img
vrl.img
vrl_backup.img
dts.img
dtx.img
version.img
isp_boot.img
patch.img
persist.img
secure_storage.img
splash2.img
But i admit,that i have no idea how to get them from a working phone.Maybe others can help here.
I also have no idea how @Tkkg1994 obtained this partition list.
Hmm, the some are included in update.app , which can be extracted. But this is a basic thing you already know.
Indeed the most are not in updated.app like vrl.img dtx, version, isp, pathch persist etc. Maybe they are temporary build during update process.
well...with those in update.app already tried,they solve nothing,even if flashing is ok.
something is missing...
and btw....who seen before this error?
flash write prim vrl failure
Monster.Kali said:
I would need as many as partitions possible, since i have only those extracted from update.app.
Click to expand...
Click to collapse
You should have a clear understanding what is the purpose of these partitions, and how they are used.
If you are loading code into RAM directly (over debug UART or whatever), then it is possible to load Linux kernel (zImage)
with any custom ramdisk (+busybox). At this point "fastboot" is completely redundant, because flashing can be
done by 'cat foo.img > /dev/sdcNN'.
user4774 said:
You should have a clear understanding what is the purpose of these partitions, and how they are used.
If you are loading code into RAM directly (over debug UART or whatever), then it is possible to load Linux kernel (zImage)
with any custom ramdisk (+busybox). At this point "fastboot" is completely redundant, because flashing can be
done by 'cat foo.img > /dev/sdcNN'.
Click to expand...
Click to collapse
well, i don't have that clear understanding. i'm a noob.
imagine that at work, (gsm repair shop)i'm helped by software and hardware tools.
i never did that before,to load something into ram for x reason.
so right now, i try to learn things, and to bring my phone back to life.
what i tried to do,was like that. if i broke internal partitions,that after restart killed my phone, now i'm trying to get them back,maybe they solve something.
in ram, i loaded fastboot image and xloader.
that gave me access to fastboot.
until some clear instructions, i keep trying.
Monster.Kali said:
now i'm trying to get them back,maybe they solve something.
Click to expand...
Click to collapse
vrl and vrl_backup are first 2 partitions on /dev/sdd (/dev/block/sdd1 and /dev/block/sdd2)
Code:
Number Start (sector) End (sector) Size Name
1 128 255 512K vrl
2 256 383 512K vrl_backup
I have dumped them to the SD card with 'cat /dev/block/sdd1 > /storage/sdcard1/D1' and 'cat /dev/block/sdd2 > /storage/sdcard1/D2'
The contents seems to be identical
Code:
# md5sum /storage/sdcard1/D1
06da2cbdf74659d24430114c104e08b8 /storage/sdcard1/D1
# md5sum /storage/sdcard1/D2
06da2cbdf74659d24430114c104e08b8 /storage/sdcard1/D2
fastboot (aka bootloader) is the partition /dev/sdd24
Code:
24 151552 154623 12.0M fastboot_a
and the xloader is on a different 4MB "disk" /dev/sda
Code:
# fdisk -l /dev/block/sda
Note: sector size is 4096 (not 512)
Disk /dev/block/sda: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 1 heads, 8 sectors/track
Units: cylinders of 8 * 4096 = 32768 bytes
Disk /dev/block/sda doesn't contain a valid partition table
user4774 said:
vrl and vrl_backup are first 2 partitions on /dev/sdd (/dev/block/sdd1 and /dev/block/sdd2)
Code:
Number Start (sector) End (sector) Size Name
1 128 255 512K vrl
2 256 383 512K vrl_backup
I have dumped them to the SD card with 'cat /dev/block/sdd1 > /storage/sdcard1/D1' and 'cat /dev/block/sdd2 > /storage/sdcard1/D2'
The contents seems to be identical
Code:
# md5sum /storage/sdcard1/NEW/D1
06da2cbdf74659d24430114c104e08b8 /storage/sdcard1/D1
# md5sum /storage/sdcard1/NEW/D2
06da2cbdf74659d24430114c104e08b8 /storage/sdcard1/D2
Click to expand...
Click to collapse
that's good.
it would be easier to do what i want, with cat, as you said.
i would follow partitions profile by tkkg1994, and write them to emmc.
but since i have only fastboot.....
Monster.Kali said:
but since i have only fastboot.....
Click to expand...
Click to collapse
Check which partitions you can extract from the full ROM/UPDATE.APP.
For your reference, my MHAL29C432 has 4 "scsi" disks /dev/sda (4MB xloader), /dev/sdb (4MB unused), /dev/sdc (frp stuff)
Code:
# fdisk -l /dev/block/sdc
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sdc: 16384 sectors, 64.0M
Logical sector size: 4096
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 2047
Number Start (sector) End (sector) Size Name
1 128 255 512K frp
2 256 767 2048K persist
3 768 2047 5120K reserved1
and /dev/sdd
Code:
# fdisk -l /dev/block/sdd
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sdd: 124928000 sectors, 576M
Logical sector size: 4096
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15615999
Number Start (sector) End (sector) Size Name
1 128 255 512K vrl
2 256 383 512K vrl_backup
3 384 2559 8704K modem_secure
4 2560 4095 6144K nvme
5 4096 20479 64.0M oeminfo
6 20480 28671 32.0M secure_storage
7 28672 36863 32.0M modem_om
8 36864 37887 4096K modemnvm_factory
9 37888 38911 4096K modemnvm_backup
10 38912 41983 12.0M modemnvm_img
11 41984 43007 4096K modemnvm_system
12 43008 63487 80.0M splash2
13 63488 129023 256M cache
14 129024 129535 2048K bootfail_info
15 129536 130047 2048K misc
16 130048 138239 32.0M reserved2
17 138240 139263 4096K reserved10
18 139264 141311 8192K hisee_fs
19 141312 145407 16.0M dfx
20 145408 149503 16.0M rrecord
21 149504 149567 256K fw_lpm3_a
22 149568 150527 3840K reserved3_a
23 150528 151551 4096K hisee_img_a
24 151552 154623 12.0M fastboot_a
25 154624 155647 4096K vector_a
26 155648 156159 2048K isp_boot_a
27 156160 159743 14.0M isp_firmware_a
28 159744 162815 12.0M fw_hifi_a
29 162816 164863 8192K teeos_a
30 164864 181247 64.0M recovery2_a
31 181248 185343 16.0M sensorhub_a
32 185344 193535 32.0M boot_a
33 193536 209919 64.0M recovery_a
34 209920 214015 16.0M dts_a
35 214016 214527 2048K trustfirmware_a
36 214528 228863 56.0M modem_fw_a
37 228864 241663 50.0M reserved4_a
38 241664 262143 80.0M modemnvm_update_a
39 262144 270335 32.0M patch_a
40 270336 278527 32.0M version_a
41 278528 479231 784M vendor_a
42 479232 528383 192M product_a
43 528384 577535 192M cust_a
44 577536 1777663 4688M system_a
45 1777664 1810431 128M reserved5
46 1810432 15615999 52.6G userdata
ok
got all missing img files from update.app with 7zip, not with update extractor.
on some of them, i have different sizes
here is the log of fastboot.
many of them flashed ok.
some not.
Code:
C:\Users\MONSTER>fastboot flash hisee_fs F:\dload\UPDATE\hisee_fs.img
target reported max download size of 471859200 bytes
sending 'hisee_fs' (8192 KB)...
OKAY [ 0.288s]
writing 'hisee_fs'...
OKAY [ 0.092s]
finished. total time: 0.386s
C:\Users\MONSTER>fastboot flash dfx F:\dload\UPDATE\dfx.img
target reported max download size of 471859200 bytes
sending 'dfx' (16384 KB)...
OKAY [ 0.561s]
writing 'dfx'...
OKAY [ 0.161s]
finished. total time: 0.728s
C:\Users\MONSTER>fastboot flash rrecord F:\dload\UPDATE\rrecord.img
target reported max download size of 471859200 bytes
sending 'rrecord' (16384 KB)...
OKAY [ 0.562s]
writing 'rrecord'...
OKAY [ 0.157s]
finished. total time: 0.725s
C:\Users\MONSTER>fastboot flash fw_lpm3_a F:\dload\UPDATE\fw_lpm3_a.img
target reported max download size of 471859200 bytes
sending 'fw_lpm3_a' (256 KB)...
OKAY [ 0.017s]
writing 'fw_lpm3_a'...
FAILED (remote: image verification error)
finished. total time: 0.061s
C:\Users\MONSTER>fastboot flash fw_lpm3 F:\dload\UPDATE\fw_lpm3_a.img
target reported max download size of 471859200 bytes
sending 'fw_lpm3' (256 KB)...
OKAY [ 0.015s]
writing 'fw_lpm3'...
FAILED (remote: image verification error)
finished. total time: 0.059s
C:\Users\MONSTER>fastboot flash reserved3_a F:\dload\UPDATE\reserved3_a.img
target reported max download size of 471859200 bytes
sending 'reserved3_a' (3840 KB)...
OKAY [ 0.136s]
writing 'reserved3_a'...
OKAY [ 0.056s]
finished. total time: 0.198s
C:\Users\MONSTER>fastboot flash hisee_img_a F:\dload\UPDATE\hisee_img_a.img
target reported max download size of 471859200 bytes
sending 'hisee_img_a' (4096 KB)...
OKAY [ 0.141s]
writing 'hisee_img_a'...
OKAY [ 0.058s]
finished. total time: 0.205s
C:\Users\MONSTER>fastboot flash fastboot_a F:\dload\UPDATE\fastboot_a.img
target reported max download size of 471859200 bytes
sending 'fastboot_a' (12288 KB)...
OKAY [ 0.423s]
writing 'fastboot_a'...
FAILED (remote: image verification error)
finished. total time: 0.466s
C:\Users\MONSTER>fastboot flash vector_a F:\dload\UPDATE\vector_a.img
target reported max download size of 471859200 bytes
sending 'vector_a' (4096 KB)...
OKAY [ 0.145s]
writing 'vector_a'...
FAILED (remote: image verification error)
finished. total time: 0.189s
C:\Users\MONSTER>fastboot flash vector F:\dload\UPDATE\vector_a.img
target reported max download size of 471859200 bytes
sending 'vector' (4096 KB)...
OKAY [ 0.145s]
writing 'vector'...
FAILED (remote: image verification error)
finished. total time: 0.189s
C:\Users\MONSTER>fastboot flash isp_boot_a F:\dload\UPDATE\isp_boot_a.img
target reported max download size of 471859200 bytes
sending 'isp_boot_a' (2048 KB)...
OKAY [ 0.074s]
writing 'isp_boot_a'...
OKAY [ 0.055s]
finished. total time: 0.135s
C:\Users\MONSTER>fastboot flash isp_firmware_a F:\dload\UPDATE\isp_firmware_a.im
g
target reported max download size of 471859200 bytes
sending 'isp_firmware_a' (14336 KB)...
OKAY [ 0.494s]
writing 'isp_firmware_a'...
FAILED (remote: image verification error)
finished. total time: 0.539s
C:\Users\MONSTER>fastboot flash fw_hifi_a F:\dload\UPDATE\fw_hifi_a.img
target reported max download size of 471859200 bytes
sending 'fw_hifi_a' (12288 KB)...
OKAY [ 0.424s]
writing 'fw_hifi_a'...
FAILED (remote: image verification error)
finished. total time: 0.467s
C:\Users\MONSTER>fastboot flash teeos_a F:\dload\UPDATE\teeos_a.img
target reported max download size of 471859200 bytes
sending 'teeos_a' (8192 KB)...
OKAY [ 0.286s]
writing 'teeos_a'...
FAILED (remote: image verification error)
finished. total time: 0.329s
C:\Users\MONSTER>fastboot flash recovery2_a F:\dload\UPDATE\recovery2_a.img
target reported max download size of 471859200 bytes
sending 'recovery2_a' (65536 KB)...
OKAY [ 2.230s]
writing 'recovery2_a'...
FAILED (remote: image verification error)
finished. total time: 2.273s
C:\Users\MONSTER>fastboot flash dts_a F:\dload\UPDATE\dts_a.img
target reported max download size of 471859200 bytes
sending 'dts_a' (16384 KB)...
OKAY [ 0.562s]
writing 'dts_a'...
FAILED (remote: image verification error)
finished. total time: 0.603s
C:\Users\MONSTER>fastboot flash trustfirmware_a F:\dload\UPDATE\trustfirmware_a.
img
target reported max download size of 471859200 bytes
sending 'trustfirmware_a' (2048 KB)...
OKAY [ 0.077s]
writing 'trustfirmware_a'...
FAILED (remote: image verification error)
finished. total time: 0.123s
C:\Users\MONSTER>fastboot flash modem_fw_a F:\dload\UPDATE\modem_fw_a.img
target reported max download size of 471859200 bytes
sending 'modem_fw_a' (57344 KB)...
OKAY [ 1.943s]
writing 'modem_fw_a'...
FAILED (remote: image verification error)
finished. total time: 1.988s
C:\Users\MONSTER>fastboot flash reserved4_a F:\dload\UPDATE\reserved4_a.img
target reported max download size of 471859200 bytes
sending 'reserved4_a' (51200 KB)...
OKAY [ 1.743s]
writing 'reserved4_a'...
OKAY [ 0.413s]
finished. total time: 2.162s
C:\Users\MONSTER>fastboot flash modemnvm_update_a F:\dload\UPDATE\modemnvm_updat
e_a.img
target reported max download size of 471859200 bytes
sending 'modemnvm_update_a' (81920 KB)...
OKAY [ 2.762s]
writing 'modemnvm_update_a'...
OKAY [ 0.648s]
finished. total time: 3.416s
C:\Users\MONSTER>fastboot flash patch_a F:\dload\UPDATE\patch_a.img
target reported max download size of 471859200 bytes
sending 'patch_a' (32768 KB)...
OKAY [ 1.117s]
writing 'patch_a'...
OKAY [ 0.275s]
finished. total time: 1.398s
C:\Users\MONSTER>fastboot flash version_a F:\dload\UPDATE\version_a.img F:\dload
\UPDATE\version_a.img
target reported max download size of 471859200 bytes
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\MONSTER>fastboot flash vendor_a F:\dload\UPDATE\vendor_a.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_a' (460726 KB)...
OKAY [ 16.785s]
writing 'vendor_a'...
OKAY [ 4.661s]
sending sparse 'vendor_a' (340470 KB)...
OKAY [ 12.505s]
writing 'vendor_a'...
OKAY [ 3.312s]
finished. total time: 37.272s
C:\Users\MONSTER>fastboot flash product_a F:\dload\UPDATE\product_a.img
target reported max download size of 471859200 bytes
sending 'product_a' (196608 KB)...
OKAY [ 6.675s]
writing 'product_a'...
OKAY [ 1.536s]
finished. total time: 8.218s
C:\Users\MONSTER>fastboot flash cust_a F:\dload\UPDATE\cust_a.img
target reported max download size of 471859200 bytes
sending 'cust_a' (196608 KB)...
OKAY [ 6.705s]
writing 'cust_a'...
OKAY [ 1.507s]
finished. total time: 8.218s
C:\Users\MONSTER>fastboot flash system_a F:\dload\UPDATE\system_a.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1070983688 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 593316360 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 112839176 is not a multiple of t
he block size 4096
sending sparse 'system_a' (457291 KB)...
error: write_sparse_skip_chunk: don't care size 1070983688 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 1070983688 is not a multiple of
the block size 4096
OKAY [ 16.816s]
writing 'system_a'...
FAILED (remote: sparse flash write failure)
finished. total time: 22.552s
C:\Users\MONSTER>fastboot flash frp F:\dload\UPDATE\frp.img
target reported max download size of 471859200 bytes
sending 'frp' (512 KB)...
OKAY [ 0.025s]
writing 'frp'...
OKAY [ 0.022s]
finished. total time: 0.052s
C:\Users\MONSTER>fastboot flash persist F:\dload\UPDATE\persist.img
target reported max download size of 471859200 bytes
sending 'persist' (2048 KB)...
OKAY [ 0.075s]
writing 'persist'...
FAILED (remote: partition length get error)
finished. total time: 0.093s
C:\Users\MONSTER>fastboot flash reserved1 F:\dload\UPDATE\reserved1.img
target reported max download size of 471859200 bytes
sending 'reserved1' (5120 KB)...
OKAY [ 0.182s]
writing 'reserved1'...
FAILED (remote: partition length get error)
finished. total time: 0.204s
C:\Users\MONSTER>fastboot reboot
any idea of some img to load into ram?
or is there a method, that, allows me to flash files on emmc, over serial port?
i mean, serial port allows me to load them into ram.
but i wonder if it's capable to see the emmc.
@user4774 - i noticed that, flashing img's in the order that you gave me, beginning with vrl and vrl_backup, the write prim vrl failed error is gone.
so all of them,in that log,are flashed in order.
@ajsmsg78 - sir, i saw your no force encription boot image, and wanted to ask if you could help me with some file to load into ram, but which is capable to accept some others commands, excluding fastboot
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!