After testing Blisspop I wanted go back to CM12.1.1-nightly. I made a factory reset and restored a nandroid backup in TWRP.
But then my OPO didn't start any more. I can't go into recovery, but into fastboot.
I tried to flash TWRP again, but got an error message.
C:\adb>fastboot flash recovery twrp-2.28.6.1-bacon.img
target reported max download size of 1073741824 bytes
sending 'recovery' <10344KB>...
OKAY [ 0.345s]
writing 'recovery'...
FAILED <remote: partition table doesn't exist>
finished. total time: 0.366s
HELP, PLEASE!
Hi folks,
Here is a resumé of what i've tried so far
Actual symptoms : Cyanogenmod logo with animation looping (no bootloop)
I've access to fastboot and philz recovery (but errors are shown, see below)
I've got the phone as it is, no idea of what the previous owner has done.
Can someone help me ?
I tried to unbrick using various methods :
ColosOS : device is displayed as FORGE HS-USB QDLOader 9008 or Qualcomm HS-USB QDLOader 9008
OPO recovery tool 1.1 : connected to com5, 8974_msimage.mbn: OK
that's the only thing shown, then the OPO vibrates and nothing happen
Flash zip bacon 33R and 44S via OTG => error status 7
Code:
Installing : /storage/usbdisk/cm-11.0-XNPH44S-bacon-signed-fastboot.zip
E: Can't mount /cache/recovery/last_install
E: faile to open last_install : File exists
Finding update package
Opening update Package
Installation update
Installation aborted
Code:
[U]Errors when booting Philz Recovery :[/U]
E: could not mount /data to setup /data/media path!
E: Can 't mount /cache/recovery/command
E: Can 't mount /cache/recovery/log
E: Can 't open /cache/recovery/log
E: Cannon mount path for settings file :/data/philz-touch/phils-touch6.ini
E: Can 't mount /cache/recovery/last_log
E: Can 't open /cache/recovery/log
E: Can 't mount /cache/recovery/last_install
E: Can 't open /cache/recovery/last_install
[U]Logs :[/U]
W; failed to mount /dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 (File exists)
mount : mounting /dev/block/platform/msm_sdcc.1/by-name/cache on /cache failed : Invalid argument
Code:
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.007s]
finished. total time: 0.008s
OnePlus One ZIP with 3 bats and fastboot :
Code:
######### This patch is Created by ONEPLUS Technical Support. #######
###### This patch should only be used for ONEPLUS ONE 64GB Global Version. ####
#
...
OKAY [ 0.003s]
finished. total time: 0.003s
erasing 'persist'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.065s
target reported max download size of 536870912 bytes
sending 'persist' (4244 KB)...
OKAY [ 0.138s]
writing 'persist'...
FAILED (remote: flash write failure)
finished. total time: 5.221s
erasing 'reserve4'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.065s
target reported max download size of 536870912 bytes
sending 'reserve4' (5176 KB)...
OKAY [ 0.167s]
writing 'reserve4'...
FAILED (remote: flash write failure)
finished. total time: 5.251s
target reported max download size of 536870912 bytes
sending 'boot' (5578 KB)...
OKAY [ 0.181s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 5.232s
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.064s
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.065s
target reported max download size of 536870912 bytes
sending 'recovery' (7510 KB)...
OKAY [ 0.243s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.295s
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.064s
target reported max download size of 536870912 bytes
sending 'modem' (56337 KB)...
OKAY [ 1.800s]
writing 'modem'...
FAILED (remote: flash write failure)
finished. total time: 6.851s
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
FAILED (remote: flash write failure)
finished. total time: 5.065s
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.004s]
writing 'dbi'...
FAILED (remote: flash write failure)
finished. total time: 5.056s
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.015s]
writing 'aboot'...
FAILED (remote: flash write failure)
finished. total time: 5.067s
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.010s]
writing 'rpm'...
FAILED (remote: flash write failure)
finished. total time: 5.062s
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.013s]
writing 'tz'...
FAILED (remote: flash write failure)
finished. total time: 5.064s
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.308s]
writing 'LOGO'...
FAILED (remote: flash write failure)
finished. total time: 5.361s
rebooting...
finished. total time: 0.005s
It is done Now :)
Appuyez sur une touche pour continuer...
I would ask for trying twrp recovery and trying flashing a ROM...
If that did not help, there is a thread for unbricking the oneplus using Qualcomm drivers, in which adb is not required.... try it and many have recovered their device... I'll post the the thread link, once I get to a laptop.
#HappyFlashing#
DrNinjaa said:
I would ask for trying twrp recovery and trying flashing a ROM...
If that did not help, there is a thread for unbricking the oneplus using Qualcomm drivers, in which adb is not required.... try it and many have recovered their device... I'll post the the thread link, once I get to a laptop.
Click to expand...
Click to collapse
Hi DrNinjaa,
Already tried to boot twrp and flash rom using OTG USB to get the zip, nothing happens, got an error status 7 ...
Using the qualcomm drivers and OPO Recovery tool did not work, like I said, the phone is detected, then flash begins, then a red message (but in chinese UTF8) appears, then a sahara error ...
DrNinjaa said:
I would ask for trying twrp recovery and trying flashing a ROM...
If that did not help, there is a thread for unbricking the oneplus using Qualcomm drivers, in which adb is not required.... try it and many have recovered their device... I'll post the the thread link, once I get to a laptop.
#HappyFlashing#
Click to expand...
Click to collapse
Qiou said:
Hi DrNinjaa,
Already tried to boot twrp and flash rom using OTG USB to get the zip, nothing happens, got an error status 7 ...
Using the qualcomm drivers and OPO Recovery tool did not work, like I said, the phone is detected, then flash begins, then a red message (but in chinese UTF8) appears, then a sahara error ...
Click to expand...
Click to collapse
Seems the guy you buy the phone has relock bootloader
In kitkat that was problem ....
Qiou said:
Hi DrNinjaa,
Already tried to boot twrp and flash rom using OTG USB to get the zip, nothing happens, got an error status 7 ...
Using the qualcomm drivers and OPO Recovery tool did not work, like I said, the phone is detected, then flash begins, then a red message (but in chinese UTF8) appears, then a sahara error ...
Click to expand...
Click to collapse
Status 7 message is due to improper twrp recovery..... flash the latest.... and unlock the bootloader once again.... may be that will help.
Really want to help u.... because, once i had bricked my device and lost efs also, and I know how bad it feels .... but thanks to my backups, i was saved...
#HappyFlashing#
@DrNinjaa
Actually, I can't flash a new recovery, when I try with fastboot, I get an error (flash write failure) and also when I try to erase it.
Qiou said:
@DrNinjaa
Actually, I can't flash a new recovery, when I try with fastboot, I get an error (flash write failure) and also when I try to erase it.
Click to expand...
Click to collapse
im having this exact problem... anyone managed to find a fix? Even putting it back to stock doesn't work!
Hey guys
having some problem flashing a stock system.img to my phone. I try to get back to Mashmellow to get my phone back to stock. Currently its rooted and unlocked.
I downloaded the following zip:
Honor 8_Firmware_FRD-L09_Android 6.0_EMUI 4.1_C432B131_Western Europe.zip
I unzipped it and extracted all Images from the UPDATE.APP file.
Flashing cust.img, recovery.img, and recovery2.img is no problem. Problem is when flashing system.img
It always says
Code:
[[email protected] honor8]# fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (435393 KB)...
OKAY [ 11.022s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 11.056s
[[email protected] honor8]#
[[email protected] honor8]# fastboot --version
fastboot version 7.1.1_r13
Phone is unlocked
FRP is unlocked
Flashing recovery works:
Code:
[[email protected] Downloads]# fastboot flash recovery twrp-3.1.0-0-frd.img
target reported max download size of 471859200 bytes
sending 'recovery' (24884 KB)...
OKAY [ 0.630s]
writing 'recovery'...
OKAY [ 0.327s]
finished. total time: 0.957s
TWRP tells me, that it cannot mount system. When restoring a backup with TWRP it works: it writes the system to the flash.
After restore I can reboot into Android again. Unfortunately I tried to installe the latest OTA (B380) which bricked my camera for some reason and makes the system itself kinda buggy.
Does anyone have an idea, how I get out of this situation?
Current Version: FRD-L09C432B360
It won't work this way. I wasted so much time trying. You have to use the rollback procedure to get your phone working again. Search the forum for it, it's been documented pretty well. Good luck
OK so I tried to upadte to OREO with Hurupdater and something went wrong.
So I installed a rollback package - OK
Then tried to install MM and I entered in ERROR MODE
I get Func NO: 8 (hifi image)
Error no: 1 (security verify failed!)
Then I was able to enter in Fastboot recovery mode (after fully discharging the battery).
At this point I unlock the bootloader
fastboot OEM UNLOCK "UNLOCK CODE"
ok
I use Huawei update extractor to get boot, cust, recovery, system and user data from FRD-L04 MM Fw 4.1 found here
https://forum.xda-developers.com/honor-8/how-to/guide-comprehensive-method-to-unbrick-t3632998
I tried to flash cust and recovery but the processes failed (see below)
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (252389 KB)...
OKAY [ 5.428s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 5.441s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (36976 KB)...
OKAY [ 0.796s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.825s
Any idea what I am doing wrong?
I heard that in Oreo partitions are different. That might explain the problem but on the other side I flashed a MM rollback already.
Please HELP!!!
Thx
Anyone?
https://forum.xda-developers.com/honor-8/how-to/guide-flashing-unapproved-firmwares-t3668306
i have a huawei p8 lite ALE-L21 with unlocked bootloader, i am trying to flash stock rom but when i start flashing system.img i get this error
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'system' 1/3 (460798 KB)...
OKAY [ 21.245s]
writing 'system' 1/3...
FAILED (unknown status code)
finished. total time: 21.268s
context: i flashed twrp and it did not boot, so i am trying to reflash stock tom