Been working on this for a few days but I am running out of ideas. I originally consulted @nkk71 privately about this but we've been unable to find anything to resolve the issue. Hopefully, someone has experienced this before or has a fix, if this is not a hardware issue.
I have a m7att that appears to be unable to flash newer recoveries. It only seems to accept certain old versions and I haven't been able to exactly pinpoint why, this is my last resort before trying to go through the trouble in reviewing github commits for the recovery updates. Before you say "fastboot erase cache"; yes, I've done that hundreds of times (literally).
I can run adb commands in certain recoveries even when they are frozen on "Entering recovery..." screen. See the table I posted below under the adb? column for more info on which.
symptoms
- Can't flash certain recoveries (see list, especially newer ones)
- fastboot commands sometimes/very seldom lag or don't carry through (or I'm just impatient to wait and I just rebooted the bootloader)
- fastboot sometimes shows hbootpreupdate: 11 randomly while parsing commands (e.g. on fastboot getvar all)
status of the m7
- S-off, rooted
- fastboot getvar all info
- emmc chip info:
Partition info and other misc, just in case maybe something is off about this one
Here's a list of the result of all the recoveries I've tried so far on the L firmware (7.15.401.1)

What I've tried:
- Pastebin of typical process, this one was with 7.15 firmware. http://pastebin.com/wwM2GYdR
- Various FW, 1.29.401.12 up to 6.09.401.5 official firmware (current ROM)
- RUU'ed with 1.26.502.10, (was originally on 1.26.502.05 at bone stock)
- Flashed a stock firmware/recovery (1.26.502.10 , 6.09.401.5, 7.15.401.1) and then tried custom recovery right after
- @nkk71 & @cschmitt misc partition corruption guide.
Attached in this post is the original mmcblk0p19 (rename the file) from this mainboard.
(tags: @Danny201281 @clsA maybe you guys might have seen something similar to this before)
I have a m7att that appears to be unable to flash newer recoveries. It only seems to accept certain old versions and I haven't been able to exactly pinpoint why, this is my last resort before trying to go through the trouble in reviewing github commits for the recovery updates. Before you say "fastboot erase cache"; yes, I've done that hundreds of times (literally).
I can run adb commands in certain recoveries even when they are frozen on "Entering recovery..." screen. See the table I posted below under the adb? column for more info on which.
symptoms
- Can't flash certain recoveries (see list, especially newer ones)
- fastboot commands sometimes/very seldom lag or don't carry through (or I'm just impatient to wait and I just rebooted the bootloader)
- fastboot sometimes shows hbootpreupdate: 11 randomly while parsing commands (e.g. on fastboot getvar all)
status of the m7
- S-off, rooted
- fastboot getvar all info
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 4T.33.3218.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.15.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4235mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.132sPartition info and other misc, just in case maybe something is off about this one
Here's a list of the result of all the recoveries I've tried so far on the L firmware (7.15.401.1)

What I've tried:
- Pastebin of typical process, this one was with 7.15 firmware. http://pastebin.com/wwM2GYdR
- Various FW, 1.29.401.12 up to 6.09.401.5 official firmware (current ROM)
- RUU'ed with 1.26.502.10, (was originally on 1.26.502.05 at bone stock)
- Flashed a stock firmware/recovery (1.26.502.10 , 6.09.401.5, 7.15.401.1) and then tried custom recovery right after
- @nkk71 & @cschmitt misc partition corruption guide.
Attached in this post is the original mmcblk0p19 (rename the file) from this mainboard.
(tags: @Danny201281 @clsA maybe you guys might have seen something similar to this before)
Aucun commentaire:
Enregistrer un commentaire