search

TeamWin / Team-Win-Recovery-Project

Core recovery files for the Team Win Recovery Project (T.W.R.P) - this is not up to date, please see https://github.com/TeamWin/android_bootable_recovery/
http://twrp.me
1.95k stars 741 forks source link

2.8.7.0 - m8 - /dev/block/mmcblk0p44 process ended with ERROR=1 #495

Open BSOD2600 opened 9 years ago

BSOD2600 commented 9 years ago

HTC One M8 Verizon, TWRP 2.8.7.0 (twrp-2.8.7.0-m8.img). On latest available firmware

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.12.20.1211
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.605.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f2489bd1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Used Online Nandroid Backup * ROOT (https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup) to make a backup from CM12.1 (cm-12.1-20150920-NIGHTLY-m8.zip).
In TWRP, wiped, installed a different ROM, did some testing in that ROM, back in TWRP wiped, and then restored the nandroid backup created an hour earlier. It appears to have failed to restore the boot partition. following pulled from recovery.log:

I:Restore filename is: boot.emmc.win
I:Restore file system is: 'emmc'.
Flashing Boot...
I:Flash command: 'dd bs=8388608 if='/data/media/0/TWRP/BACKUPS/HT4AHSFxxxx/2015-09-22--01-04-04_cm_m8-userdebug_5.1.1_LVY48F_197563fc86_test-keys/boot.emmc.win' of=/dev/block/mmcblk0p44'
dd: writing '/dev/block/mmcblk0p44': No space left on device
3+0 records in
2+0 records out
16777216 bytes (16.0MB) copied, 0.470242 seconds, 34.0MB/s
E:dd bs=8388608 if='/data/media/0/TWRP/BACKUPS/HT4AHSFxxxx/2015-09-22--01-04-04_cm_m8-userdebug_5.1.1_LVY48F_197563fc86_test-keys/boot.emmc.win' of=/dev/block/mmcblk0p44 process ended with ERROR=1
[Boot done (1 seconds)]

Rest of the restore didnt report any errors. Once I rebooted, it would only go into the bootloader and wouldnt boot back into CM12.1. Had to reflash CM12.1 over itself in order to properly boot.

CaptainThrowback commented 9 years ago

Seems like an issue with how the app backed up boot. Have you tried backing up boot in recovery directly? Do you have the same issue restoring it if you do? If not, the issue is the app, not TWRP.

BSOD2600 commented 9 years ago

With regards to the comments in http://gerrit.twrp.me/#/c/1043/1, mmcblk0p44 IS boot (not recovery). The partition sizes/names:

cat /proc/partitions
major minor  #blocks  name

 179        0   30535680 mmcblk0
 179        1       1024 mmcblk0p1
 179        2     121823 mmcblk0p2
 179        3         16 mmcblk0p3
 179        4       8192 mmcblk0p4
 179        5        256 mmcblk0p5
 179        6      24255 mmcblk0p6
 179        7        256 mmcblk0p7
 179        8        256 mmcblk0p8
 179        9       2048 mmcblk0p9
 179       10         32 mmcblk0p10
 179       11       4096 mmcblk0p11
 179       12       5120 mmcblk0p12
 179       13       1024 mmcblk0p13
 179       14         32 mmcblk0p14
 179       15       1024 mmcblk0p15
 259        0      61441 mmcblk0p16
 259        1       5120 mmcblk0p17
 259        2       8192 mmcblk0p18
 259        3       1536 mmcblk0p19
 259        4      76801 mmcblk0p20
 259        5       4096 mmcblk0p21
 259        6      51200 mmcblk0p22
 259        7      15359 mmcblk0p23
 259        8       1024 mmcblk0p24
 259        9       1536 mmcblk0p25
 259       10       1536 mmcblk0p26
 259       11      20480 mmcblk0p27
 259       12          4 mmcblk0p28
 259       13        256 mmcblk0p29
 259       14         16 mmcblk0p30
 259       15       1281 mmcblk0p31
 259       16         64 mmcblk0p32
 259       17       1024 mmcblk0p33
 259       18          1 mmcblk0p34
 259       19          8 mmcblk0p35
 259       20        256 mmcblk0p36
 259       21      25600 mmcblk0p37
 259       22        256 mmcblk0p38
 259       23      30720 mmcblk0p39
 259       24         10 mmcblk0p40
 259       25      10240 mmcblk0p41
 259       26      10240 mmcblk0p42
 259       27      26520 mmcblk0p43
 259       28      16384 mmcblk0p44
 259       29      24576 mmcblk0p45
 259       30      90112 mmcblk0p46
 259       31    2752512 mmcblk0p47
 259       32    1048576 mmcblk0p48
 259       33   25952256 mmcblk0p49
 179       16       4096 mmcblk0rpmb
 179       32   62367744 mmcblk1
 179       33   62366720 mmcblk1p1

ls /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root     root              2015-09-22 15:29 adsp -> /dev/block/mmcblk0p16
lrwxrwxrwx root     root              2015-09-22 15:29 board_info -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              2015-09-22 15:29 boot -> /dev/block/mmcblk0p44
lrwxrwxrwx root     root              2015-09-22 15:29 cache -> /dev/block/mmcblk0p48
lrwxrwxrwx root     root              2015-09-22 15:29 carrier -> /dev/block/mmcblk0p37
lrwxrwxrwx root     root              2015-09-22 15:29 cdma_record -> /dev/block/mmcblk0p33
lrwxrwxrwx root     root              2015-09-22 15:29 cir_img -> /dev/block/mmcblk0p40
lrwxrwxrwx root     root              2015-09-22 15:29 control -> /dev/block/mmcblk0p30
lrwxrwxrwx root     root              2015-09-22 15:29 custdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root     root              2015-09-22 15:29 ddr -> /dev/block/mmcblk0p14
lrwxrwxrwx root     root              2015-09-22 15:29 debug_config -> /dev/block/mmcblk0p28
lrwxrwxrwx root     root              2015-09-22 15:29 devlog -> /dev/block/mmcblk0p39
lrwxrwxrwx root     root              2015-09-22 15:29 dsps -> /dev/block/mmcblk0p15
lrwxrwxrwx root     root              2015-09-22 15:29 extra -> /dev/block/mmcblk0p32
lrwxrwxrwx root     root              2015-09-22 15:29 fataldevlog -> /dev/block/mmcblk0p27
lrwxrwxrwx root     root              2015-09-22 15:29 fsc -> /dev/block/mmcblk0p34
lrwxrwxrwx root     root              2015-09-22 15:29 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx root     root              2015-09-22 15:29 hboot -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              2015-09-22 15:29 local -> /dev/block/mmcblk0p31
lrwxrwxrwx root     root              2015-09-22 15:29 mfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              2015-09-22 15:29 misc -> /dev/block/mmcblk0p24
lrwxrwxrwx root     root              2015-09-22 15:29 modem_st1 -> /dev/block/mmcblk0p25
lrwxrwxrwx root     root              2015-09-22 15:29 modem_st2 -> /dev/block/mmcblk0p26
lrwxrwxrwx root     root              2015-09-22 15:29 pdata -> /dev/block/mmcblk0p29
lrwxrwxrwx root     root              2015-09-22 15:29 pg1fs -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              2015-09-22 15:29 pg2fs -> /dev/block/mmcblk0p6
lrwxrwxrwx root     root              2015-09-22 15:29 radio -> /dev/block/mmcblk0p20
lrwxrwxrwx root     root              2015-09-22 15:29 radio_config -> /dev/block/mmcblk0p18
lrwxrwxrwx root     root              2015-09-22 15:29 recovery -> /dev/block/mmcblk0p45
lrwxrwxrwx root     root              2015-09-22 15:29 reserve -> /dev/block/mmcblk0p43
lrwxrwxrwx root     root              2015-09-22 15:29 reserve_1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              2015-09-22 15:29 reserve_2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root     root              2015-09-22 15:29 reserve_3 -> /dev/block/mmcblk0p46
lrwxrwxrwx root     root              2015-09-22 15:29 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              2015-09-22 15:29 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              2015-09-22 15:29 sbl1_update -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              2015-09-22 15:29 sdi -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              2015-09-22 15:29 sensor_hub -> /dev/block/mmcblk0p38
lrwxrwxrwx root     root              2015-09-22 15:29 skylink -> /dev/block/mmcblk0p36
lrwxrwxrwx root     root              2015-09-22 15:29 sp1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root     root              2015-09-22 15:29 ssd -> /dev/block/mmcblk0p35
lrwxrwxrwx root     root              2015-09-22 15:29 system -> /dev/block/mmcblk0p47
lrwxrwxrwx root     root              2015-09-22 15:29 tool_diag -> /dev/block/mmcblk0p21
lrwxrwxrwx root     root              2015-09-22 15:29 tz -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              2015-09-22 15:29 userdata -> /dev/block/mmcblk0p49
lrwxrwxrwx root     root              2015-09-22 15:29 vzw_logger -> /dev/block/mmcblk0p42
lrwxrwxrwx root     root              2015-09-22 15:29 vzw_quality -> /dev/block/mmcblk0p41
lrwxrwxrwx root     root              2015-09-22 15:29 wcnss -> /dev/block/mmcblk0p17
lrwxrwxrwx root     root              2015-09-22 15:29 wifi -> /dev/block/mmcblk0p13

Yes, seems likely to be an app issue with why it made boot.emmc.win 27156480 bytes. I'll test directly in TWRP and see if the same issue occurs.