Hello,
My Phone (Honor 6X BLN-AL10) is brick
Here the link: https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601
On Fastboot Mode show only PHONE Unlocked and on normaly Boot: func No 11 and 2
dload not working it show the message func no 11
recovery flash show me:
target max-download-size: 450MB
sending 'boot' (15840 KB)...
OKAY [ 0.542s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.579s
and recovery too.. what can i make now? oooh and with : fastboot -c "console=ttyHSL0,115200,n8" boot BOOT.img comes:
creating boot image...
creating boot image - 16222208 bytes
downloading 'boot.img'...
OKAY [ 0.507s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.739s
thx for your answer
What have done? Hwota first flash the twrp recovery.
Hi,
Yes i wanna upgrade my phone from emui 5 (Android 7) to emui 8 (Android Oreo)
Okey i follow this how to: https://forum.xda-developers.com/hon...or-6x-t3792601
But on TWRP Section my phone print error on partition i dont know which....
next Boot Installing dload twice and now bricked phone
dload not working the only thats work is download mode and HiSuite say not compatible phone
I dont know frp lock is on or off
Related
Hi.
I've been trying to flash twrp my Huawai Mate 8 for a couple of weeks. I keep getting the error I mentioned in the title. The bootloader is unlooked, frp is looked. USB debugging is enabled. OEM is grey.
Android version 7.0, emui version 5.0.1. I've been using the official twrp and used adb files and fastboot from other sources as well as official files. The phone is NOT rooted.
Here is the full message:
fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (22142 KB)...
OKAY [ 0.470s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.477s
I would appreciate any help as this problem has bugged me for so long by now. Thanks!!
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
plaese help me ,this is what happpens ,it goes "FAILED (remote: partition length get error)"
BLN-AL10 ,with system is android 9.0,pie...omni version 9-20190203-treble-HOMEMADE,,,get from openkirin
PSwhat happens in adb)
C:\Users\admin\Downloads\工具箱adb>fastboot flash recovery twrp-3.2.3-0-berlin.img
target reported max download size of 471859200 bytes
sending 'recovery' (25068 KB)...
OKAY [ 0.693s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.699s
If you're on EMUI 8 (and you surely are, because you're running a treble OS) the correct command to flash on recovery partition is now "fastboot flash recovery_ramdisk nameoftwrp.img".
On previous EMUI versions the command you tried was correct, but things are changed now so recovery partition is now intended as "recovery_ramdisk".
I wiped everything in trwp when I was going to install Lineage, I did the misstake to restart the recovery and now Im stuck in the bootlaoder.
I need to install the stoc firmware via fastboot/bootlaoder but can't find any img file, only zip file of the Stock firmware.
Is is possible to install a zip file via fastboot?
Fastboot recognize the phone when typing the commando fastboot devices, so I see the serial nr.
If I try to install twrp img both on boot and flash recovery commando I get this:
PS C:\Android> fastboot boot twrp-3.2.1-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.577s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.598s
PS C:\Android> fastboot flash recovery twrp-3.2.1-0-enchilada.img
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.574s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.579s
I have tried the MsmDownloadTool V4.0, but the deviced manager in windows doesn't find the Qualcom....
@Peterrrrr said:
I wiped everything in trwp when I was going to install Lineage, I did the misstake to restart the recovery and now Im stuck in the bootlaoder.
I need to install the stoc firmware via fastboot/bootlaoder but can't find any img file, only zip file of the Stock firmware.
Is is possible to install a zip file via fastboot?
Fastboot recognize the phone when typing the commando fastboot devices, so I see the serial nr.
If I try to install twrp img both on boot and flash recovery commando I get this:
PS C:\Android> fastboot boot twrp-3.2.1-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.577s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.598s
PS C:\Android> fastboot flash recovery twrp-3.2.1-0-enchilada.img
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.574s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.579s
I have tried the MsmDownloadTool V4.0, but the deviced manager in windows doesn't find the Qualcom....
Click to expand...
Click to collapse
I have never tried msmtool, but it sounds like a driver issue. Maybe take a closer look at their instructions
You can try these fastboot flashable stock roms.
You have few options to solve your issue. Now you are in slot B. You can change switch partition to A with fastboot. Try use: fastboot --set-active=a. It will switch to partition A and then try to boot/flash recovery. Also you have try to use fastboot roms with flashall.bat. There are few availaible in forum.
If you would like to use MSM you have to connect phone in proper mode to PC. Power off and hold Vol+ then connect. Also try to install latest Qualcomm drivers.
Msm tool
Download and use msm tool
trying to install twrp,the bootloader is already unlocked.
this is what happens:
fastboot flash recovery recovery.img
target reported max download size of 805263360 bytes
sending 'recovery' (34200 KB)...
OKAY [ 0.728s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.841s
fastboot boot recovery twrp.img also give a error
what is the solution ?
neozbr said:
trying to install twrp,the bootloader is already unlocked.
this is what happens:
fastboot flash recovery recovery.img
target reported max download size of 805263360 bytes
sending 'recovery' (34200 KB)...
OKAY [ 0.728s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.841s
fastboot boot recovery twrp.img also give a error
what is the solution ?
Click to expand...
Click to collapse
OK:
1. First you need to root the device. Follow this guide. You will use adb to patch the boot.img file of your current firmware.
2. After you have rooted, you can install the unofficial TWRP for Android 10 Moto G8 Plus from here. The zip file will install through magisk. Works fine; I tested it last night.