astboot flash boot boot.img
sending 'boot' (12288kb)....
OKAY....
writing 'boot'....
FAILED (remote: image is not a boot image)
kuken_91 said:
astboot flash boot boot.img
sending 'boot' (12288kb)....
OKAY....
writing 'boot'....
FAILED (remote: image is not a boot image)
Click to expand...
Click to collapse
seems like you are writing a wrong boot.img
make sure you have the right file!
you can only flash boot.img if you have unlocked your bootloader,
that means you can install a custom recovery, make a backup, and flash SlimStock U10, that way your phone works again.
Related
When I try flash a recovery image using the command prompt I receive the following error:
fastboot flash recovery recovery.img
sending 'recovery' (8956 KB)...
OKAY [ 1.105s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.355s
How to resolve error?
Akio8 said:
When I try flash a recovery image using the command prompt I receive the following error:
fastboot flash recovery recovery.img
sending 'recovery' (8956 KB)...
OKAY [ 1.105s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.355s
How to resolve error?
Click to expand...
Click to collapse
Have you successfully unlocked the bootloader ?
Which recovery image are you trying to flash ?
htc_one_mini_m4 said:
Have you successfully unlocked the bootloader ?
Which recovery image are you trying to flash ?
Click to expand...
Click to collapse
Yes the bootloader is unlocked. I'm trying to flash philz-touch-6.26.1-m4.img
Akio8 said:
Yes the bootloader is unlocked. I'm trying to flash philz-touch-6.26.1-m4.img
Click to expand...
Click to collapse
Can you try flashing TWRP 2.7.1.1 instead ? ( Just to see if it's a general issue or something related to your image file )
htc_one_mini_m4 said:
Can you try flashing TWRP 2.7.1.1 instead ? ( Just to see if it's a general issue or something related to your image file )
Click to expand...
Click to collapse
It's a general issue it doesn't matter what image I try to flash
Akio8 said:
It's a general issue it doesn't matter what image I try to flash
Click to expand...
Click to collapse
So, you're stuck with the stock recovery or with a custom one ?
I'd try to install an unsecured kernel + ROM like Jmz's and try flashing a new recovery after that.
Not sure if it would work, just my thoughts and gut says that it might
Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!
if you have the boot backup then restore it.
venugopalu007 said:
if you have the boot backup then restore it.
Click to expand...
Click to collapse
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.
if you cannot find the boot.img
just do a rollback bro
here is the link
first dload this
http://download-c.huawei.com/download/downloadCenter?downloadId=94070&version=376169&siteCode=de-h
and this now
if your device is BLN-L21C432B151 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v84712/f1/full/update.zip
or BLN-L21C185B131 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v75593/f1/full/update.zip
I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img
Stinks said:
I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img
Click to expand...
Click to collapse
The guide from "cyberkey.in/how-to-root-honor-6x-100-working/" is simply wrong when it comes to flashing the twrp recovery. If you really followed this guide completely then you flashed the recovery to the boot partition.
Use "fastboot flash recovery twrp.img" to flash the recovery.
You will still have to flash the boot image to your boot partition then (fastboot flash boot boot.img).
Stinks said:
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.
Click to expand...
Click to collapse
Use fastboot flash recovery twrpname.img to flash the recovery
Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.
V
Stinks said:
Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.
Click to expand...
Click to collapse
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.
venugopalu007 said:
V
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.
Click to expand...
Click to collapse
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
Bro y this ,just do a rollback .
Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
I recommend you to download firmware files only from the official honor website or by using the huawei firmware finder(https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146)
In this case try to use huawei firmware finder to get the right stock version for your phone. Download these two files: e.g. update.zip & update_full_BLN-L21_hw_eu.zip.
Export the following image files: recovery, system, boot and cust.
The try to flash them:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
If flashing a partition via fastboot fails then it is usually because it's the wrong image or just not made for your phone.
Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.
Stinks said:
Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.
Click to expand...
Click to collapse
Glad you revived your phone
question
​
Stinks said:
Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!
Click to expand...
Click to collapse
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.
[email protected] said:
question
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.
Click to expand...
Click to collapse
did you solve your issue.....I have same problem now
nokiasatyam said:
did you solve your issue.....I have same problem now
Click to expand...
Click to collapse
Hello, could you be more specific about your problem? I'll be able to help you.
Brief Explanation:
From the screen on which you're stuck, press and hold power button for about 10 seconds to forcibly restart your device. when you see the same screen again, immediately press and hold volume up button(for about 3 seconds) to boot to eRecovery.
> Choose shut down option on eRecovery. press and hold vol down button and insert the charging cable to boot to fastboot.
> Press and hold power and volume up button to boot to recovery. (You could do this even from fastboot screen and the screen you're stuck at).
I successfully unlocked the bootloader, flashed TWRP, and installed SuperSU, but now I sold my Mate 9, and the guy would like it back to stock. I extracted RECOVERY.img (the stock recovery) from Update.zip, and used the command: fastboot flash recovery_ramdisk RECOVERY.img and got this output:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (54884 KB)...
OKAY [ 1.749s]
writing 'recovery_ramdisk'...
FAILED (remote: partition error)
finished. total time: 1.796s
Any suggestions come to mind what I may be doing wrong?
No, you can not do that. You can use erecovery to back stock or use dload method (https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656)
gazavn said:
No, you can not do that. You can use erecovery to back stock or use dload method (https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656)
Click to expand...
Click to collapse
With all due respect, don't think all that is necessary. I have been following this comprehensive guide:
https://forum.xda-developers.com/mate-9/how-to/hacking-customizing-managing-huawei-t3589996
and this fellow says I should be able to simply extract the recovery.img from update.zip, and fastboot flash it. If I'm not mistaken you are talking about rebranding it as if I were going to update the phone. I'm not trying to be combative, just seems like a lot of monkeying around...
UPDATE:
I was using the wrong image. I had confused an UPDATE.APP from a different file. Plus I had an olde version of HuaWei Update Extractor. The correct .img file was labeled recovery_ramdis.img, I had been trying RECOVERY.img.
So I have been trying to flash the Pixel Factory Image, I have used the most recent SDK Platform Tools and I still can't get past the boot loop. I also have tried to flash the TWRP recovery but I am getting this:
Code:
C:\Users\MyName\Documents\Pixel\minimal_adb_fastboot_1.4.3_portable>fastboot flash recovery twrp-3.3.0-0-sailfish.img
target reported max download size of 536870912 bytes
sending 'recovery' (31000 KB)...
OKAY [ 0.828s]
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 0.938s
I have even tried but the bootloop is still there:
Code:
PS C:\Users\MyName\Documents\Pixel\minimal_adb_fastboot_1.4.3_portable> ./fastboot boot twrp-3.3.0-0-sailfish.img
downloading 'boot.img'...
OKAY [ 0.727s]
booting...
OKAY [ 1.010s]
finished. total time: 1.740s
There are a couple things wrong here:
Pixels don't have a recovery partition, everything happens in the boot one (root, twrp, custom kernel)
The first command in the first code block you wrote is wrong because the recovery partition is not there. In case you wanna flash a stock boot image, maybe for recover your device faulty kernel/twrp etc, without have to reflash the whole rom, the command should be "fastboot flash boot boot.img"
The command you sent in the second code block (./fastboot boot twrp-3.3.0-0-sailfish.img) in fact is correct because you just boot the twrp image (= no errors).
But when you wanna flash the recovery, you have to boot the twrp img and when it booted you have to flash the twrp.zip that you can download from the official site from the twrp screen, not the .img
Hope this helps
I'll add that you should also use the official platform-tools downloaded from Google. The minimal (and other alternatives) can give you problems when trying to flash.
The latest platform-tools is here. Note that Google hasn't updated the changelog, and the latest version is actually 28.0.3, not 28.0.2.
For TWRP, you need both the latest .img and .zip files from here, and transfer the .zip file to the Pixel. Use the boot command to boot from the .img, then from within the temporarily-booted TWRP install the .zip file.
after unlocking my bootloader i tried to flash magisk.zip in fastboot mode by typing fastboot flash boot magisk.zip
now im stuck in fastboot mode. Enter reason: boot failure
with oneplus devices you can always go back to stock with msm tool. is there anything like that for pixel devices? or did i just turn my new phone into a shiny new paper weight?
barbosa212 said:
after unlocking my bootloader i tried to flash magisk.zip in fastboot mode by typing fastboot flash boot magisk.zip
now im stuck in fastboot mode. Enter reason: boot failure
with oneplus devices you can always go back to stock with msm tool. is there anything like that for pixel devices? or did i just turn my new phone into a shiny new paper weight?
Click to expand...
Click to collapse
To root you flash the patched boot image (the one you patched in Magisk), not magisk.zip.
Try flashing the stock boot image to get back to normal and then flash the patched boot image in fastboot.
See this guide.
Lughnasadh said:
To root you flash the patched boot image (the one you patched in Magisk), not magisk.zip.
Try flashing the stock boot image to get back to normal and then flash the patched boot image in fastboot.
See this guide.
Click to expand...
Click to collapse
Sending 'boot_a' (65536 KB) OKAY [ 1.715s]
Writing 'boot_a' (bootloader) unable to update boot image: use unmerged...
OKAY [ 0.144s]
Finished. Total time: 1.897s
now im at "waiting for rescue commands..." what do?
barbosa212 said:
Sending 'boot_a' (65536 KB) OKAY [ 1.715s]
Writing 'boot_a' (bootloader) unable to update boot image: use unmerged...
OKAY [ 0.144s]
Finished. Total time: 1.897s
now im at "waiting for rescue commands..." what do?
Click to expand...
Click to collapse
i held the power button until it rebooted successfully. Thank you so much
barbosa212 said:
i held the power button until it rebooted successfully. Thank you so much
Click to expand...
Click to collapse
If you want to root/flash, I recommend PixelFlasher. A simple and effective tool and saves you from trouble!