Hey,
I could install Kitkat 4.4.2 EMUI 3.0: Cofface Custom Recovery, but could find any os what would install from zip. Getting error 7
today I tried to flash TWRP-3.0.2-r4 for the 4C. So I unlocked the bootloader flashed the new recovery img and then restarted and couldn't access the recovery menu. It freezes right at the Huawei logo.
Then I tried to flash the latest 4C android, so I extracted the boot.img, recovery.img and system.img from the update.app.
Flashing was successful I guess?
Code:
λ fastboot flash boot boot.img
target reported max download size of 524288000 bytes
sending 'boot' (23486 KB)...
OKAY [ 0.527s]
writing 'boot'...
OKAY [ 1.566s]
finished. total time: 2.098s
λ fastboot flash recovery RECOVERY.img
target reported max download size of 524288000 bytes
sending 'recovery' (33548 KB)...
OKAY [ 0.753s]
writing 'recovery'...
OKAY [ 1.742s]
finished. total time: 2.501s
λ fastboot flash system SYSTEM.img
target reported max download size of 524288000 bytes
sending sparse 'system' (510886 KB)...
OKAY [ 12.234s]
writing 'system'...
OKAY [ 12.280s]
sending sparse 'system' (497530 KB)...
OKAY [ 12.190s]
writing 'system'...
OKAY [ 11.563s]
sending sparse 'system' (511911 KB)...
OKAY [ 12.414s]
writing 'system'...
OKAY [ 12.407s]
sending sparse 'system' (509238 KB)...
OKAY [ 12.379s]
writing 'system'...
OKAY [ 12.039s]
sending sparse 'system' (362252 KB)...
OKAY [ 8.826s]
writing 'system'...
OKAY [ 8.523s]
finished. total time: 114.883s
But I tried to boot into the stock recovery but it freezes at the huawei logo again and I can't boot into android either.
After that I tried to erase the cache and userdata but I am getting the message that I am not allowed to do so.
Code:
λ fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.005s
Does anybody knows a workaround or a possible fix ?
Regards Artur
any updates ??
Up up..
Help guys
Related
HI.
recently ive want to install ubuntu touch on my opo but i cant. then i want to roll back into the cyanogen os and its stuck on cyanogen boot animation. i just can install oxygen os that i hate it!
please help me to roll back into the cyanogen os 12.1
files i have download
modem :YNG1TAS0YL_Extras.zip
Full-oxygen-04-04-15-Bacon-modem-flashable.zip
XNPH33R_Extras.zip
roms : cm-12.0-YNG1TAS17L-bacon-signed.zip
cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip
oxygenos_1.0.0
i use ubuntu on my pc
my recovery is twrp
dirtylife2011 said:
HI.
recently ive want to install ubuntu touch on my opo but i cant. then i want to roll back into the cyanogen os and its stuck on cyanogen boot animation. i just can install oxygen os that i hate it!
please help me to roll back into the cyanogen os 12.1
files i have download
modem :YNG1TAS0YL_Extras.zip
Full-oxygen-04-04-15-Bacon-modem-flashable.zip
XNPH33R_Extras.zip
roms : cm-12.0-YNG1TAS17L-bacon-signed.zip
cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip
oxygenos_1.0.0
i use ubuntu on my pc
my recovery is twrp
Click to expand...
Click to collapse
Flash the stock images with fastboot. See section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
PS. It's the "cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip" one that you'll use.
Heisenberg said:
Flash the stock images with fastboot. See section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
PS. It's the "cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip" one that you'll use.
Click to expand...
Click to collapse
I use that thread to flash my phone and install both of YNG1TAS2I3 and next ver YOG...-fastboot.ZIP and its stuck on logo . then i flash both version for recovery and its stuck on logi again. Help me
dirtylife2011 said:
I use that thread to flash my phone and install both of YNG1TAS2I3 and next ver YOG...-fastboot.ZIP and its stuck on logo . then i flash both version for recovery and its stuck on logi again. Help me
Click to expand...
Click to collapse
Please try again and copy/paste the text from the command prompt here so I can see.
Heisenberg said:
Please try again and copy/paste the text from the command prompt here so I can see.
Click to expand...
Click to collapse
here you are.
Code:
~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 2.682s]
writing 'modem'...
OKAY [ 0.962s]
finished. total time: 3.644s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash sbl1 sbl1.mbn
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.018s]
finished. total time: 0.031s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash dbi sdi.mbn
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.003s]
writing 'dbi'...
OKAY [ 0.011s]
finished. total time: 0.014s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.020s]
writing 'aboot'...
OKAY [ 0.015s]
finished. total time: 0.035s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash rpm rpm.mbn
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.017s]
finished. total time: 0.026s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash tz tz.mbn
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.015s]
writing 'tz'...
OKAY [ 0.014s]
finished. total time: 0.029s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash LOGO logo.bin
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.015s]
writing 'LOGO'...
OKAY [ 0.028s]
finished. total time: 0.043s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.476s]
writing 'oppostanvbk'...
OKAY [ 0.188s]
finished. total time: 0.665s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (6494 KB)...
OKAY [ 0.301s]
writing 'boot'...
OKAY [ 0.121s]
finished. total time: 0.422s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.107s]
sending 'cache' (10432 KB)...
OKAY [ 0.485s]
writing 'cache'...
OKAY [ 0.217s]
finished. total time: 0.810s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9120 KB)...
OKAY [ 0.425s]
writing 'recovery'...
OKAY [ 0.169s]
finished. total time: 0.594s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.402s]
sending 'system' (1034756 KB)...
OKAY [ 47.980s]
writing 'system'...
OKAY [ 22.148s]
finished. total time: 70.530s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash userdata userdata_64G.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 3.516s]
sending 'userdata' (141075 KB)...
OKAY [ 6.575s]
writing 'userdata'...
OKAY [ 3.205s]
finished. total time: 13.297s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot reboot
rebooting...
dirtylife2011 said:
here you are.
Code:
~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 2.682s]
writing 'modem'...
OKAY [ 0.962s]
finished. total time: 3.644s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash sbl1 sbl1.mbn
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.018s]
finished. total time: 0.031s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash dbi sdi.mbn
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.003s]
writing 'dbi'...
OKAY [ 0.011s]
finished. total time: 0.014s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.020s]
writing 'aboot'...
OKAY [ 0.015s]
finished. total time: 0.035s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash rpm rpm.mbn
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.017s]
finished. total time: 0.026s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash tz tz.mbn
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.015s]
writing 'tz'...
OKAY [ 0.014s]
finished. total time: 0.029s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash LOGO logo.bin
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.015s]
writing 'LOGO'...
OKAY [ 0.028s]
finished. total time: 0.043s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.476s]
writing 'oppostanvbk'...
OKAY [ 0.188s]
finished. total time: 0.665s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (6494 KB)...
OKAY [ 0.301s]
writing 'boot'...
OKAY [ 0.121s]
finished. total time: 0.422s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.107s]
sending 'cache' (10432 KB)...
OKAY [ 0.485s]
writing 'cache'...
OKAY [ 0.217s]
finished. total time: 0.810s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9120 KB)...
OKAY [ 0.425s]
writing 'recovery'...
OKAY [ 0.169s]
finished. total time: 0.594s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.402s]
sending 'system' (1034756 KB)...
OKAY [ 47.980s]
writing 'system'...
OKAY [ 22.148s]
finished. total time: 70.530s
[email protected]alihk-VPCEB3MFX:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash userdata userdata_64G.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 3.516s]
sending 'userdata' (141075 KB)...
OKAY [ 6.575s]
writing 'userdata'...
OKAY [ 3.205s]
finished. total time: 13.297s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot reboot
rebooting...
Click to expand...
Click to collapse
Hmm, can you boot into recovery?
Heisenberg said:
Hmm, can you boot into recovery?
Click to expand...
Click to collapse
yes .now its boot to cyanogen recovery
dirtylife2011 said:
yes .now its boot to cyanogen recovery
Click to expand...
Click to collapse
Ok, you can flash one of the official zips. You already have this one:
cm-12.0-YNG1TAS17L-bacon-signed.zip
So flash that with the stock recovery.
Heisenberg said:
Ok, you can flash one of the official zips. You already have this one:
cm-12.0-YNG1TAS17L-bacon-signed.zip
So flash that with the stock recovery.
Click to expand...
Click to collapse
only when i install cyanogen it says "patching system unconditionaly...."
is that okay??
and its not work again.
dirtylife2011 said:
only when i install cyanogen it says "patching system unconditionaly...."
is that okay??
and its not work again.
Click to expand...
Click to collapse
Yes that message is normal. Did the flash succeed or fail?
deleted
Heisenberg said:
Yes that message is normal. Did the flash succeed or fail?
Click to expand...
Click to collapse
in cyanogen recovery there is no message that its succeed or failed
but in twrp its succeed.
but all of installation section is already up to date. and its done very fast!
dirtylife2011 said:
in cyanogen recovery there is no message that its succeed or failed
but in twrp its succeed.
but all of installation section is already up to date. and its done very fast!
Click to expand...
Click to collapse
Ok, your persist partition might be corrupt. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/edit?usp=docslist_api
Use fastboot to do the following:
Code:
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
If it still doesn't boot after that, try flashing the stock images again with fastboot. If it still won't boot after that I'm out of ideas and you'll need to start the RMA process with OnePlus.
Heisenberg said:
Ok, your persist partition might be corrupt. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/edit?usp=docslist_api
Use fastboot to do the following:
Code:
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
If it still doesn't boot after that, try flashing the stock images again with fastboot. If it still won't boot after that I'm out of ideas and you'll need to start the RMA process with OnePlus.
Click to expand...
Click to collapse
thank you for step by step help....
and sorry for my bad English language
Heisenberg said:
Ok, your persist partition might be corrupt. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/edit?usp=docslist_api
Use fastboot to do the following:
Code:
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
If it still doesn't boot after that, try flashing the stock images again with fastboot. If it still won't boot after that I'm out of ideas and you'll need to start the RMA process with OnePlus.
Click to expand...
Click to collapse
Its Worked!!!
Thanks!!!
Its The final Way
In my country We call adept final impact
dirtylife2011 said:
Its Worked!!!
Thanks!!!
Its The final Way
In my country We call adept final impact
Click to expand...
Click to collapse
Oh hell yeah!! Awesome news
Thank you so much for this guide to fixing a corrupt persist.img. I just learned how to use cmd.exe and fastboot to flash this to my phone that was messed up. This guide saved my phone!!
Ok. Today after i updated my honor 8 to EMUI 5.0 my root was gone. I went and tried rooting my system again and when i was in TWRP i acidentally deleted EVERYTHING on the device (dont ask me how i can be so retarded). I then tried to find a solution on how to unbrick my Honor 8.
After downloading the stock firmware for Honor 8 and trying to flash it onto my device i ran into a problem. When i tried flashing cust.img, and system.img it just didnt work. Here are the results.
Code:
target reported max download size of 471859200 bytes
sending 'boot' (15464 KB)...
OKAY [ 0.330s]
writing 'boot'...
OKAY [ 0.371s]
finished. total time: 0.703s
target reported max download size of 471859200 bytes
sending 'cust' (433554 KB)...
OKAY [ 9.281s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 9.292s
target reported max download size of 471859200 bytes
sending 'recovery' (36996 KB)...
OKAY [ 0.789s]
writing 'recovery'...
OKAY [ 0.871s]
finished. total time: 1.662s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (435393 KB)...
OKAY [ 9.902s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 9.942s
As you can see it says "FAILED (remote: sparse flash write failure)" when i try to flash system.img. Does anyone know how i can fix this or is my Honor 8 fully bricked and do i have to buy a new one now?
Also, my bootloader is unlocked.
Little searching wouldn't hurt. https://forum.xda-developers.com/honor-8/how-to/guide-fix-boot-loop-bricked-honor-8-t3545202
Somehow I couldn't copy my music to my phone. Decided to check it out...
So the system image is using 109GB instead of 5-10GB as it should
Running the latest factory images NOF26V, freshly installed
Code:
finished. total time: 1.235s
MacBook-Pro-2:android iichel$ ./fastboot flash bootloader bootloader-sailfish-8996-012001-1611091517.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32980 KB)...
OKAY [ 0.843s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 15.964s]
finished. total time: 16.807s
MacBook-Pro-2:android iichel$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
MacBook-Pro-2:android iichel$ ./fastboot flash radio radio-sailfish-8996-012511-1611190200.img
target reported max download size of 536870912 bytes
sending 'radio_a' (57192 KB)...
OKAY [ 1.403s]
writing 'radio_a'...
OKAY [ 0.910s]
finished. total time: 2.314s
MacBook-Pro-2:android iichel$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
MacBook-Pro-2:android iichel$ ./fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24801 KB)...
OKAY [ 0.652s]
writing 'boot_a'...
OKAY [ 0.611s]
finished. total time: 1.263s
MacBook-Pro-2:android iichel$ ./fastboot flash cache cache.img
error: cannot load 'cache.img'
MacBook-Pro-2:android iichel$ ./fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system_a'...
OKAY [ 0.995s]
sending sparse 'system_a' 1/4 (515466 KB)...
OKAY [ 15.869s]
writing 'system_a' 1/4...
OKAY [ 7.944s]
sending sparse 'system_a' 2/4 (495893 KB)...
OKAY [ 15.867s]
writing 'system_a' 2/4...
OKAY [ 10.045s]
sending sparse 'system_a' 3/4 (507843 KB)...
OKAY [ 15.358s]
writing 'system_a' 3/4...
OKAY [ 7.454s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 0.904s]
writing 'system_a' 4/4...
OKAY [ 0.651s]
finished. total time: 75.089s
MacBook-Pro-2:android iichel$ ./fastboot flash system_b system_other.img
target reported max download size of 536870912 bytes
erasing 'system_b'...
OKAY [ 1.043s]
sending sparse 'system_b' 1/4 (517080 KB)...
OKAY [ 14.369s]
writing 'system_b' 1/4...
OKAY [ 4.792s]
sending sparse 'system_b' 2/4 (514384 KB)...
OKAY [ 14.517s]
writing 'system_b' 2/4...
OKAY [ 4.998s]
sending sparse 'system_b' 3/4 (524287 KB)...
OKAY [ 14.612s]
writing 'system_b' 3/4...
OKAY [ 4.540s]
sending sparse 'system_b' 4/4 (85786 KB)...
OKAY [ 2.549s]
writing 'system_b' 4/4...
OKAY [ 1.201s]
finished. total time: 62.622s
MacBook-Pro-2:android iichel$ ./fastboot flash vendor vendor.img
target reported max download size of 536870912 bytes
erasing 'vendor_a'...
OKAY [ 0.503s]
sending 'vendor_a' (235186 KB)...
OKAY [ 5.849s]
writing 'vendor_a'...
OKAY [ 6.707s]
finished. total time: 13.060s
MacBook-Pro-2:android iichel$ ./fastboot flash modem modem.img
target reported max download size of 536870912 bytes
sending 'modem_a' (57184 KB)...
OKAY [ 1.431s]
writing 'modem_a'...
OKAY [ 0.849s]
finished. total time: 2.280s
MacBook-Pro-2:android iichel$ ./fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 29.416s]
sending 'userdata' (136402 KB)...
OKAY [ 3.444s]
writing 'userdata'...
OKAY [ 1.159s]
finished. total time: 34.019s
MacBook-Pro-2:android iichel$ ./fastboot reboot
rebooting...
Found a similar thread, but a factory reset didn't fix my issue either:
https://forum.xda-developers.com/pixel/help/7-1-1-taking-109gb-storage-t3522967
Pluisje89 said:
Somehow I couldn't copy my music to my phone. Decided to check it out...
So the system image is using 109GB instead of 5-10GB as it should
Running the latest factory images NOF26V, freshly installed
Code:
finished. total time: 1.235s
MacBook-Pro-2:android iichel$ ./fastboot flash bootloader bootloader-sailfish-8996-012001-1611091517.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32980 KB)...
OKAY [ 0.843s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 15.964s]
finished. total time: 16.807s
MacBook-Pro-2:android iichel$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
MacBook-Pro-2:android iichel$ ./fastboot flash radio radio-sailfish-8996-012511-1611190200.img
target reported max download size of 536870912 bytes
sending 'radio_a' (57192 KB)...
OKAY [ 1.403s]
writing 'radio_a'...
OKAY [ 0.910s]
finished. total time: 2.314s
MacBook-Pro-2:android iichel$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
MacBook-Pro-2:android iichel$ ./fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24801 KB)...
OKAY [ 0.652s]
writing 'boot_a'...
OKAY [ 0.611s]
finished. total time: 1.263s
MacBook-Pro-2:android iichel$ ./fastboot flash cache cache.img
error: cannot load 'cache.img'
MacBook-Pro-2:android iichel$ ./fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system_a'...
OKAY [ 0.995s]
sending sparse 'system_a' 1/4 (515466 KB)...
OKAY [ 15.869s]
writing 'system_a' 1/4...
OKAY [ 7.944s]
sending sparse 'system_a' 2/4 (495893 KB)...
OKAY [ 15.867s]
writing 'system_a' 2/4...
OKAY [ 10.045s]
sending sparse 'system_a' 3/4 (507843 KB)...
OKAY [ 15.358s]
writing 'system_a' 3/4...
OKAY [ 7.454s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 0.904s]
writing 'system_a' 4/4...
OKAY [ 0.651s]
finished. total time: 75.089s
MacBook-Pro-2:android iichel$ ./fastboot flash system_b system_other.img
target reported max download size of 536870912 bytes
erasing 'system_b'...
OKAY [ 1.043s]
sending sparse 'system_b' 1/4 (517080 KB)...
OKAY [ 14.369s]
writing 'system_b' 1/4...
OKAY [ 4.792s]
sending sparse 'system_b' 2/4 (514384 KB)...
OKAY [ 14.517s]
writing 'system_b' 2/4...
OKAY [ 4.998s]
sending sparse 'system_b' 3/4 (524287 KB)...
OKAY [ 14.612s]
writing 'system_b' 3/4...
OKAY [ 4.540s]
sending sparse 'system_b' 4/4 (85786 KB)...
OKAY [ 2.549s]
writing 'system_b' 4/4...
OKAY [ 1.201s]
finished. total time: 62.622s
MacBook-Pro-2:android iichel$ ./fastboot flash vendor vendor.img
target reported max download size of 536870912 bytes
erasing 'vendor_a'...
OKAY [ 0.503s]
sending 'vendor_a' (235186 KB)...
OKAY [ 5.849s]
writing 'vendor_a'...
OKAY [ 6.707s]
finished. total time: 13.060s
MacBook-Pro-2:android iichel$ ./fastboot flash modem modem.img
target reported max download size of 536870912 bytes
sending 'modem_a' (57184 KB)...
OKAY [ 1.431s]
writing 'modem_a'...
OKAY [ 0.849s]
finished. total time: 2.280s
MacBook-Pro-2:android iichel$ ./fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 29.416s]
sending 'userdata' (136402 KB)...
OKAY [ 3.444s]
writing 'userdata'...
OKAY [ 1.159s]
finished. total time: 34.019s
MacBook-Pro-2:android iichel$ ./fastboot reboot
rebooting...
Found a similar thread, but a factory reset didn't fix my issue either:
https://forum.xda-developers.com/pixel/help/7-1-1-taking-109gb-storage-t3522967
Click to expand...
Click to collapse
That only seems to add up to 4 GB. Open up a root Explorer and see what it tells you.
Hallo,
Please, I need help with a bricked Huawei Honor 6.
I have almost no knowledge about unbricking and the like.
I tried to update my Smartphone Firmware and used Huawei Update Extractor
combined with cmd Commands.
My Smartphone is in an eternal bootloop and I can only access Fastboot&Rescue Mode.
I ve tried to install another firmware, but there is this command lines in CMD (Huawei Fastboot Flasher):
C:\Users\Kevin und Christina\Documents\Huawei Fastboot Flasher GSM HELP\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending sparse 'cust' (459730 KB)...
OKAY [ 48.349s]
writing 'cust'...
OKAY [ 16.092s]
sending sparse 'cust' (16208 KB)...
OKAY [ 1.711s]
writing 'cust'...
OKAY [ 0.532s]
finished. total time: 66.689s
C:\Users\Kevin und Christina\Documents\Huawei Fastboot Flasher GSM HELP\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.416s]
writing 'recovery'...
OKAY [ 0.439s]
finished. total time: 1.857s
C:\Users\Kevin und Christina\Documents\Huawei Fastboot Flasher GSM HELP\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (10596 KB)...
OKAY [ 1.091s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.102s
C:\Users\Kevin und Christina\Documents\Huawei Fastboot Flasher GSM HELP\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (431287 KB)...
OKAY [ 45.667s]
writing 'system'...
OKAY [ 16.017s]
sending sparse 'system' (446975 KB)...
Can some one of u see what's wrong and how to solve this problem? There is one FAILED line and maybe that's the Problem?
In my fastboot mode there I can read in red letters: PHONE Unlocked.
As I said, there is only one mode possible to enter, holding Volume up and then I get into Fastboot&Rescue Mode.
Unfortunately I've got almost zero flashing knowledge.
Pls help me.
Hello,
several weeks ago I bricked my oneplus 6 during the approach to install lineage 16.0. I also tried to fix it, based on some articles I found, but without success.
Error - most likely I have coincidently wiped the partitions a/b...
A) So, some weeks later I want to bring it back to life. Current status following the lineage instructions:
1) unlocking bootloader
is unlocked
2) temporarily booting a customer recovery using fastboot
- sudo ./fastboot devices
977d3806 fastboot
- sudo ./fastboot flash boot ~/Downloads/oneplus6/twrp/twrp-3.2.3-1-enchilada.img
target reported max download size of 536870912 bytes
sending 'boot_a' (28728 KB)...
OKAY [ 1.076s]
writing 'boot_a'...
OKAY [ 0.115s]
finished. total time: 1.192s
Result: power off, automatic reboot, nothing happens - only dark screen and white light close to front camera
Result: power off, volume down + power, same result
B) Alternative
- sudo ./fastboot boot ~/Downloads/oneplus6/twrp/twrp-3.2.3-1-enchilada.img
downloading 'boot.img'...
OKAY [ 1.037s]
booting...
OKAY [ 0.077s]
finished. total time: 1.114s
Result: automatic power off, automatic reboot, nothing happens - only dark screen and white light close to front camera
C) I also tried [ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6 – also without success. Basically everything seemed to be ok but after the end I had to manually reboot it: nothing happens - only dark screen and white light close to front camera.
Flashing looked good:
target reported max download size of 536870912 bytes
sending 'aop_a' (180 KB)...
OKAY [ 0.015s]
writing 'aop_a'...
OKAY [ 0.004s]
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'aop_b' (180 KB)...
OKAY [ 0.014s]
writing 'aop_b'...
OKAY [ 0.007s]
finished. total time: 0.021s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (748 KB)...
OKAY [ 0.030s]
writing 'bluetooth_a'...
OKAY [ 0.007s]
finished. total time: 0.037s
target reported max download size of 536870912 bytes
sending 'bluetooth_b' (748 KB)...
OKAY [ 0.029s]
writing 'bluetooth_b'...
OKAY [ 0.010s]
finished. total time: 0.039s
target reported max download size of 536870912 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 2.259s]
writing 'boot_a'...
OKAY [ 0.252s]
finished. total time: 2.511s
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 2.075s]
writing 'boot_b'...
OKAY [ 0.272s]
finished. total time: 2.347s
target reported max download size of 536870912 bytes
sending 'dsp_a' (32768 KB)...
OKAY [ 1.088s]
writing 'dsp_a'...
OKAY [ 0.143s]
finished. total time: 1.231s
target reported max download size of 536870912 bytes
sending 'dsp_b' (32768 KB)...
OKAY [ 1.178s]
writing 'dsp_b'...
OKAY [ 0.127s]
finished. total time: 1.305s
target reported max download size of 536870912 bytes
sending 'dtbo_a' (8192 KB)...
OKAY [ 0.279s]
writing 'dtbo_a'...
OKAY [ 0.045s]
finished. total time: 0.324s
target reported max download size of 536870912 bytes
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.277s]
writing 'dtbo_b'...
OKAY [ 0.031s]
finished. total time: 0.308s
target reported max download size of 536870912 bytes
sending 'fw_4j1ed_a' (344 KB)...
OKAY [ 0.017s]
writing 'fw_4j1ed_a'...
OKAY [ 0.005s]
finished. total time: 0.022s
target reported max download size of 536870912 bytes
sending 'fw_4j1ed_b' (344 KB)...
OKAY [ 0.018s]
writing 'fw_4j1ed_b'...
OKAY [ 0.006s]
finished. total time: 0.024s
target reported max download size of 536870912 bytes
sending 'fw_4u1ea_a' (344 KB)...
OKAY [ 0.015s]
writing 'fw_4u1ea_a'...
OKAY [ 0.005s]
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'fw_4u1ea_b' (344 KB)...
OKAY [ 0.018s]
writing 'fw_4u1ea_b'...
OKAY [ 0.007s]
finished. total time: 0.025s
target reported max download size of 536870912 bytes
sending 'modem_a' (120916 KB)...
OKAY [ 4.347s]
writing 'modem_a'...
OKAY [ 0.598s]
finished. total time: 4.945s
target reported max download size of 536870912 bytes
sending 'modem_b' (120916 KB)...
OKAY [ 4.249s]
writing 'modem_b'...
OKAY [ 0.640s]
finished. total time: 4.889s
target reported max download size of 536870912 bytes
sending 'oem_stanvbk' (952 KB)...
OKAY [ 0.037s]
writing 'oem_stanvbk'...
OKAY [ 0.009s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
sending 'qupfw_a' (64 KB)...
OKAY [ 0.011s]
writing 'qupfw_a'...
OKAY [ 0.005s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'qupfw_b' (64 KB)...
OKAY [ 0.006s]
writing 'qupfw_b'...
OKAY [ 0.004s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'storsec_a' (24 KB)...
OKAY [ 0.003s]
writing 'storsec_a'...
OKAY [ 0.004s]
finished. total time: 0.007s
target reported max download size of 536870912 bytes
sending 'storsec_b' (24 KB)...
OKAY [ 0.010s]
writing 'storsec_b'...
OKAY [ 0.005s]
finished. total time: 0.015s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
erasing 'system_a'...
OKAY [ 0.137s]
sending sparse 'system_a' 1/6 (460753 KB)...
OKAY [ 15.731s]
writing 'system_a' 1/6...
OKAY [ 0.003s]
sending sparse 'system_a' 2/6 (524285 KB)...
OKAY [ 21.336s]
writing 'system_a' 2/6...
OKAY [ 0.007s]
sending sparse 'system_a' 3/6 (508111 KB)...
OKAY [ 18.622s]
writing 'system_a' 3/6...
OKAY [ 0.007s]
sending sparse 'system_a' 4/6 (482530 KB)...
OKAY [ 18.322s]
writing 'system_a' 4/6...
OKAY [ 0.005s]
sending sparse 'system_a' 5/6 (481413 KB)...
OKAY [ 17.874s]
writing 'system_a' 5/6...
OKAY [ 0.006s]
sending sparse 'system_a' 6/6 (218712 KB)...
OKAY [ 9.743s]
writing 'system_a' 6/6...
OKAY [ 0.006s]
finished. total time: 101.799s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'system_b' 1/6 (460753 KB)...
OKAY [ 16.083s]
writing 'system_b' 1/6...
OKAY [ 0.006s]
sending sparse 'system_b' 2/6 (524285 KB)...
OKAY [ 20.273s]
writing 'system_b' 2/6...
OKAY [ 0.006s]
sending sparse 'system_b' 3/6 (508111 KB)...
OKAY [ 18.702s]
writing 'system_b' 3/6...
OKAY [ 0.007s]
sending sparse 'system_b' 4/6 (482530 KB)...
OKAY [ 18.282s]
writing 'system_b' 4/6...
OKAY [ 0.017s]
sending sparse 'system_b' 5/6 (481413 KB)...
OKAY [ 17.782s]
writing 'system_b' 5/6...
OKAY [ 0.006s]
sending sparse 'system_b' 6/6 (218712 KB)...
OKAY [ 9.483s]
writing 'system_b' 6/6...
OKAY [ 0.007s]
finished. total time: 100.653s
target reported max download size of 536870912 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.006s]
writing 'vbmeta_a'...
OKAY [ 0.005s]
finished. total time: 0.011s
target reported max download size of 536870912 bytes
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.011s]
writing 'vbmeta_b'...
OKAY [ 0.005s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_a' 1/2 (521885 KB)...
OKAY [ 17.719s]
writing 'vendor_a' 1/2...
OKAY [ 0.005s]
sending sparse 'vendor_a' 2/2 (265685 KB)...
OKAY [ 12.415s]
writing 'vendor_a' 2/2...
OKAY [ 0.006s]
finished. total time: 30.145s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_b' 1/2 (521885 KB)...
OKAY [ 17.638s]
writing 'vendor_b' 1/2...
OKAY [ 0.006s]
sending sparse 'vendor_b' 2/2 (265685 KB)...
OKAY [ 12.434s]
writing 'vendor_b' 2/2...
OKAY [ 0.005s]
finished. total time: 30.083s
target reported max download size of 536870912 bytes
sending 'LOGO_a' (3160 KB)...
OKAY [ 0.100s]
writing 'LOGO_a'...
OKAY [ 0.028s]
finished. total time: 0.128s
target reported max download size of 536870912 bytes
sending 'LOGO_b' (3160 KB)...
OKAY [ 0.106s]
writing 'LOGO_b'...
OKAY [ 0.027s]
finished. total time: 0.133s
Any idea what I can do with my bricked OnePlus6?
Thanks Martin
Follow this thread https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 to recover your device and looks like the same as what it looks like when you first bought it.
I have had the same issue while trying to install LineageOS 17 and AOSiP, haven't tried any other rom. I booted to twrp, flashed rom and flashed twrp zip and I tried to reboot into twrp, it didn't boot instead gave black screen and white LED. I repeated the process after restoring using msmtool multiple times yet no solution.
I had a similar problem, I fixed it by flashing the "criticals" partitions from this thread. You need TWRP access to do it. The OP says they used that thread but it doesn't look like they flashed "criticals". I'm not sure if whatever msmdownloadtool flashes includes these critical partitions or not.
Also, one of my slots was working OK, the other one wasn't. Some low-level partitions had got corrupted on the other one and it was this one I was (initially) booting into, leading to the white LED, black screen. I was able to fix things temporarily by changing the active slot like this:
Code:
fastboot getvar current-slot
then you can change it to the other slot with
Code:
fastboot --set-active={"a" or "b" whichever isn't active}
fastboot reboot {recovery|bootloader}
That may get you TWRP or even full Android access. However you should be able to boot TWRP from fastboot anyway.
tiga016 said:
Follow this thread https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 to recover your device and looks like the same as what it looks like when you first bought it.
Click to expand...
Click to collapse
Thank you, I will try this - after getting a Win pc.
PS Twrp is not working...
+1 for MSM Download Tool
martinforum said:
Thank you, I will try this - after getting a Win pc.
PS Twrp is not working...
Click to expand...
Click to collapse
Use blu_spark twrp 9.101
martinforum said:
Thank you, I will try this - after getting a Win pc.
PS Twrp is not working...
Click to expand...
Click to collapse
With a Win-PC it was working and the factory rom is working again. Now twrp (org and blue) are not working...
Again unbrick was successful!
I bought a used OP6 that bricked when I applied the latest OTA, so I had to figure out what was wrong and get it working again. This is my first A/B phone. I worked out the steps below to unbrick the phone and get it on the latest OxygenOS, so I thought I could share this process with others in the same dire situation I was in.
Current as of 2019-11-12
Based on https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Download:
MsmDownloadTool V4.0 International (with Oxygen OS 5.1.5) https://mega.nz/#F!CfBG0IgZ!Gmnu6B-a7yFyvMLNw_pz8w
Qualcomm driver: https://androidfilehost.com/?fid=24052804347798730
Latest full OS from OnePlus (Oxygen 9.09 currently): https://www.oneplus.com/support/softwareupgrade/details?code=8
Notes:
The MSM tool is for writing the base configuration, below recovery and fastboot.
These instructions worked on Win 7 x64 and Win 10 x64.
ADB and fastboot must be installed on PC.
OTA must bring phone to the same version as the downloaded OOS (for example, OTA must update to 9.09, and download must be OOS 9.09).
This process will return the phone to stock OOS (with stock recovery).
Unzip the Qualcomm driver and MSM Tool packages into their own folders on the PC
Install Qualcomm driver (only needed the 1st time on the PC):
Boot the phone into Bootloader
Go to Device Manager on PC and uninstall the Qualcomm entry under COM Ports
Unplug phone and power it down
Enter test mode on PC (to keep Win from installing default drivers): cmd prompt, enter "bcdedit /set testsigning on", reboot PC
Boot phone: press power and then Vol Up for at least 5 seconds (to enter basic config mode), plug into PC
Device Manager, look for "US8_BULK", Update Driver with extracted Qualcomm folder, new entry in Device Manager should be a Qualcomm COM port (YT video: https://www.youtube.com/watch?v=PpLvmID1wdI)Run MSM Tool as Administrator, click Start, let process run until Complete, reboot phone
Run OTA updates on phone
Reboot to System
Reboot to Bootloader
Check active slot:
Command: "fastboot getvar all", look for "(bootloader) current-slot:x" entry and note a or bReboot to System
Update other slot:
Copy downloaded OnePlus OS zip file to phone Internal Memory
Go to Settings > System > System Updates
Tap "gear" (settings) icon in upper-right corner, select "Local upgrade"
Select copied file, and "Install Now"Reboot to System
Reboot to Fastboot and verify that slot is different than previous check
Choose desired slot (optional):
Command: "fastboot set_active other"Reboot to System
Exit test mode on PC: Cmd prompt, enter "bcdedit /set testsigning off", reboot PC
Troubleshooting:
For "Sahara" error in MSM Tool, unplug, power on, power off, hold Vol Up for 5 seconds, plug in again