Hello all
A friend of mine has a Huawei Honor 6 H60-L12.
He tried to do a firmware update and he bricked the phone.
I bought it and I am desperately trying to recover it.
Here is what I know about the phone:
It had Android 5.1.1
It had Emui 3.1 and was trying to upgrade to 4.0
(Probably was rooted)
It is H60-L12
No matter what I do, I cannot enter recovery mode with the 3 button trick.
I can anytime enter Fastboot mode.
I tried to unbrick it with HONOR Multi-Tool, everything seems to work alright, but flashing boot.img fails. After unbrick I should enter recovery mode but it does not work, phone remains stuck with the Honor logo.
Computer connects to phone in Fastboot mode, Multi-tool and fastboot command works, I also have the drivers installed.
I know that after bricking the rooted phone, I should restore it and remove root before upgrade but I cannot get there.
Please advise
Best regards,
Janos
janos666 said:
Hello all
A friend of mine has a Huawei Honor 6 H60-L12.
He tried to do a firmware update and he bricked the phone.
I bought it and I am desperately trying to recover it.
Here is what I know about the phone:
It had Android 5.1.1
It had Emui 3.1 and was trying to upgrade to 4.0
(Probably was rooted)
It is H60-L12
No matter what I do, I cannot enter recovery mode with the 3 button trick.
I can anytime enter Fastboot mode.
I tried to unbrick it with HONOR Multi-Tool, everything seems to work alright, but flashing boot.img fails. After unbrick I should enter recovery mode but it does not work, phone remains stuck with the Honor logo.
Computer connects to phone in Fastboot mode, Multi-tool and fastboot command works, I also have the drivers installed.
I know that after bricking the rooted phone, I should restore it and remove root before upgrade but I cannot get there.
Please advise
Best regards,
Janos
Click to expand...
Click to collapse
Instead of using the honor multi tool, why don't you use the Android SDK platform tools and connect to your phone through adb. You can solve any problem using that. You have to do everything manually but it works and never disappoints as long as you can enter fastboot mode.
Download android SDK and install it. Run the program and only choose platform tools to download. You don't need anything else
Download the latest firmware for your phone and unzip it to get dload folder which will have an update.app in it.
Download Huawei update extractor and open update.app in it.
Extract recovery, boot, Cust and system images from update.app and save them to the platform tools folder.
Flash them using adb and then do a forced update.
Will work wonders. If you need any help or need more info, please let me know.
Hello muradulislam
First of all, thank you for trying to help me.
I tried something similar to your suggestion but I still have problems.
Let me explain.
My phone is H60-L12
Latest stable firmware which I found is this one:
H60-L02-L12_EMUI3.1_Android5.1_C00B535.zip
I extracted the boot, cust, recovery and system images with Huawei update extractor.
My device is detected in fastboot mode, fastboot devices gives me this result:
c:\adb>fastboot devices
F6CDU15117010953 fastboot
When I try to flash the boot.img, it gives me this error:
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (10274 KB)...
OKAY [ 1.092s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.135s
I tried to continue with the rest but I think this is useless.
Please tell me what to do.
Best regards,
Janos
janos666 said:
Hello muradulislam
First of all, thank you for trying to help me.
I tried something similar to your suggestion but I still have problems.
Let me explain.
My phone is H60-L12
Latest stable firmware which I found is this one:
H60-L02-L12_EMUI3.1_Android5.1_C00B535.zip
I extracted the boot, cust, recovery and system images with Huawei update extractor.
My device is detected in fastboot mode, fastboot devices gives me this result:
c:\adb>fastboot devices
F6CDU15117010953 fastboot
When I try to flash the boot.img, it gives me this error:
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (10274 KB)...
OKAY [ 1.092s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.135s
I tried to continue with the rest but I think this is useless.
Please tell me what to do.
Best regards,
Janos
Click to expand...
Click to collapse
My expertise are quite limited but may be, just may be (wishful thinking), you can to flash the twrp recovery specific for your phone. Boot into that and flash a custom ROM from there.
It may not work as I guess, boot.img is needed before entering recovery but give it a try. It never hurts.
Come on, guys!
There must be somebody who can help me.
Guillermo, panamera2011 and muradulislam tried to help me and I want to thank you for their patience.
Problem is, that I am still missing something.
There are 2 weeks now, each day after work I try to revive this phone.
These are the facts I know:
Tried the programs on 4 different machines, Windows 7, Windows 8.1, Windows 10, 32 bit and 64 bit versions.
Tried different sets of drivers (the one from Android SDK, the Universal ADB drivers, the ones installed by multi-tool)
Result is always the same.
I can flash anytime, any version of cust.img recovery.img and system.img but I can flash only the boot.img which is resulting from an EMUI2.3 or EMUI3.0 package.
If I try to flash boot.img from EMUI3.1 or EMUI4.0, I get the following error:
sending 'boot' (10274 KB)...
OKAY [ 1.103s]
writing 'boot'...
FAILED (remote: flash write failure)
Click to expand...
Click to collapse
I tried flashing different stock or CWM or TWRP recoveries. They all are written correctly, but I cannot enter any recovery mode.
Someone advised me to try to flash fastboot.img. It is not working, gives error.
I have already many hours and maybe hundreds of firmware writes, I downloaded around 100 GB of firmwares....
There must be an idea how to save this phone.
I am open to any decent advice.
Best regards,
Janos
janos666 said:
Come on, guys!
There must be somebody who can help me.
Guillermo, panamera2011 and muradulislam tried to help me and I want to thank you for their patience.
Problem is, that I am still missing something.
There are 2 weeks now, each day after work I try to revive this phone.
These are the facts I know:
Tried the programs on 4 different machines, Windows 7, Windows 8.1, Windows 10, 32 bit and 64 bit versions.
Tried different sets of drivers (the one from Android SDK, the Universal ADB drivers, the ones installed by multi-tool)
Result is always the same.
I can flash anytime, any version of cust.img recovery.img and system.img but I can flash only the boot.img which is resulting from an EMUI2.3 or EMUI3.0 package.
If I try to flash boot.img from EMUI3.1 or EMUI4.0, I get the following error:
sending 'boot' (10274 KB)...
OKAY [ 1.103s]
writing 'boot'...
FAILED (remote: flash write failure)
I tried flashing different stock or CWM or TWRP recoveries. They all are written correctly, but I cannot enter any recovery mode.
Someone advised me to try to flash fastboot.img. It is not working, gives error.
I have already many hours and maybe hundreds of firmware writes, I downloaded around 100 GB of firmwares....
There must be an idea how to save this phone.
I am open to any decent advice.
Best regards,
Janos
Click to expand...
Click to collapse
@DigiGoon
You can flash boot.img from emui 2.3 or 3.0? If its written correctly then may be you can try to boot into that emui version by flashing Cust, system and recovery from the same firmware?
Your last hope is Huawei customer service.
Yes, I can flash cust, recovery and system from the same EMUI2.3 or 3.0 package, but I am still unable to boot recovery.
Unfortunately, Huawei customer service will not help me because phone is H60-L12 (Chinese version) and they don't provide support only for L04
janos666 said:
Yes, I can flash cust, recovery and system from the same EMUI2.3 or 3.0 package, but I am still unable to boot recovery.
Unfortunately, Huawei customer service will not help me because phone is H60-L12 (Chinese version) and they don't provide support only for L04
Click to expand...
Click to collapse
Well, I have mentioned DigiGoon in the previous reply. May be he can help a bit.
@janos666
You can always put your desired boot.img in a flashable zip, and flash it via TWRP recovery.
Hi DigiGoon!
No, I cannot, because I was never able to access any kind of recovery
janos666 said:
Hi DigiGoon!
No, I cannot, because I was never able to access any kind of recovery
Click to expand...
Click to collapse
You can't mix LP and MM ROMs and IMG files. If you want to downgrade, for example, from MM to LP you must use B800 transitional package.
So you must use IMG files from last installed working ROM.
muradulislam said:
@DigiGoon
You can flash boot.img from emui 2.3 or 3.0? If its written correctly then may be you can try to boot into that emui version by flashing Cust, system and recovery from the same firmware?
Your last hope is Huawei customer service.
Click to expand...
Click to collapse
zinko_pt said:
You can't mix LP and MM ROMs and IMG files. If you want to downgrade, for example, from MM to LP you must use B800 transitional package.
So you must use IMG files from last installed working ROM.
Click to expand...
Click to collapse
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.
janos666 said:
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.
Click to expand...
Click to collapse
Sure. I would go from there as I sometimes mixed boot.img from LP or MM and always got bootloop. I would stick to IMG files from last installed ROM.
janos666 said:
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.
Click to expand...
Click to collapse
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?
DigiGoon said:
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?
Click to expand...
Click to collapse
Hi DigiGoon !
Sorry, which one is the flash transition package?
Which parts to flash from it?
Which is notification LED? I can see only one red LED blinking sometimes, but only when battery is low.
DigiGoon said:
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?
Click to expand...
Click to collapse
Isn't there an option to flash all img files from fastboot?
P.S. I just got new info from the guy who flashed it first time. He says he tried to write version:
H60-L02-L12_emui3.1_android5.1_c00B535
Is there such thing as "not correctly unlocked" or "partially unlocked" bootloader?
When i try to write some parts of the firmware, i get the following error:
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
Normally this would mean that the bootloader is NOT unlocked, but anyway i test it, it says unlocked.
If i type fastboot oem get-bootinfo, i get the following result:
c:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.005s
Click to expand...
Click to collapse
Also the fastboot screen displays in red "PHONE UNLOCKED"
I can write some parts of the firmware, but not the fastboot.img, and boot.img only from EMUI2.3 or EMUI3.0
Please help me
janos666 said:
Is there such thing as "not correctly unlocked" or "partially unlocked" bootloader?
When i try to write some parts of the firmware, i get the following error:
FAILED (remote: Command not allowed)
Normally this would mean that the bootloader is NOT unlocked, but anyway i test it, it says unlocked.
If i type fastboot oem get-bootinfo, i get the following result:
c:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.005s
Also the fastboot screen displays in red "PHONE UNLOCKED"
I can write some parts of the firmware, but not the fastboot.img, and boot.img only from EMUI2.3 or EMUI3.0
Please help me
Click to expand...
Click to collapse
Some threads mention of locking and unlocking your device again. Give that a try. May help...
muradulislam said:
Some threads mention of locking and unlocking your device again. Give that a try. May help...
Click to expand...
Click to collapse
I don't have the unlock code that's why I cannot try to relock it... And in this state I cannot get the necessary info to obtain the unlock code.
Anyway, when I tried to unlock with a bogus unlock code (1234567812345678), it gave me an error something like this:
Command failed, bootloader already unlocked.
janos666 said:
I don't have the unlock code that's why I cannot try to relock it... And in this state I cannot get the necessary info to obtain the unlock code.
Anyway, when I tried to unlock with a bogus unlock code (1234567812345678), it gave me an error something like this:
Command failed, bootloader already unlocked.
Click to expand...
Click to collapse
The info you are missing is device id, another user got his device id using Huawei hacker toolkit v 1.4, his model was h60-L02. May be you can give it a try.
You have to lock it before trying to unlock again.
Fastboot OEM lock xxxxxxxxxxxxxxxx...
Related
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,
rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?
therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?
heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,
Bump!
Does anyone have any other suggestion please?
Thanks,
Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!
Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.
I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?
I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..
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).
Hi my friends
I update my mate 9 to Oreo beta. its cool.
now I want install TWRP Recovery, but in installation through fastboot, I faced with this error:
failed (remote: partition length get error)
please help me. I cannot install recovery.
thanks
where did you get the Oreo beta?
I believe the beta can be downloaded through their web site as a limited tester. My understanding of flashing recovery onto the new Android build is that you'll need a newest version of twrp to work for oreo. Most the time the new updates will mess around with the internal storage space.
ystokar said:
where did you get the Oreo beta?
Click to expand...
Click to collapse
You can get it via FH.
vang2k said:
I believe the beta can be downloaded through their web site as a limited tester.
Click to expand...
Click to collapse
The 250 users quota has long been filled unfortunately.
Sent from my MHA-L29 using XDA Labs
martin2007 said:
Hi my friends
I update my mate 9 to Oreo beta. its cool.
now I want install TWRP Recovery, but in installation through fastboot, I faced with this error:
failed (remote: partition length get error)
please help me. I cannot install recovery.
thanks
Click to expand...
Click to collapse
The recovery partitions are different in Android O. There is no working TWRP yet.
If you want to downgrade, however, there will be a solution soon.
Here is the solution (forwad)
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei. This will also work for the Mate 10, Mate 10 Pro, Mate 10 Porsche and other EMUI 8 devices.
It´s just a preliminary build so I can´t promise anything/everything will work! Keep that in mind. I´m not responsible if you brick your device.
DOWNLOAD LINK:
https://drive.google.com/file/d/0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei...id_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you´ve got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don´t mess around too much with TWRP, to be sure you don´t brick your system!
fairyland4ever said:
Here is the solution (forwad)
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei. This will also work for the Mate 10, Mate 10 Pro, Mate 10 Porsche and other EMUI 8 devices.
It´s just a preliminary build so I can´t promise anything/everything will work! Keep that in mind. I´m not responsible if you brick your device.
DOWNLOAD LINK:
https://drive.google.com/file/d/0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei...id_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you´ve got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don´t mess around too much with TWRP, to be sure you don´t brick your system!
Click to expand...
Click to collapse
It worked, I have TWRP, but my PC does not connect to ADB. I tried reinstalling all the drivers but it does not even make any sound when I connect it to USB
fairyland4ever said:
Here is the solution (forwad)
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei. This will also work for the Mate 10, Mate 10 Pro, Mate 10 Porsche and other EMUI 8 devices.
It´s just a preliminary build so I can´t promise anything/everything will work! Keep that in mind. I´m not responsible if you brick your device.
DOWNLOAD LINK:
https://drive.google.com/file/d/0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei...id_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you´ve got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don´t mess around too much with TWRP, to be sure you don´t brick your system!
Click to expand...
Click to collapse
great, that worked well. now - with the changed partition table, would you recommend rooting the phone with either of these methods: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986 ?
Dear friend, i have same issue, kindly tell me how to change partition table?
Hi, I also have Mate 9 L09 and have exact same error message:
fastboot flash recovery twrpo.img
target reported max download size of 471859200 bytes
sending 'recovery' (26982 KB)...
OKAY [ 0.579s]
writing 'recovery'...
FAILED (remote: partition length get error)
UPDATE:
OK, I managed it by myself, haha.
For anyone else with same issue.
Since Oreo: Partition names have changed.
Use this command: fastboot flash recovery_ramdisk RECOVERY.img
"recovery" changed to "recovery_ramdisk" now.
finished. total time: 0.600s
I downloaded that special TWRP recovery image, but still get the same message. Does not work for me, any new solution available?
tobyffm said:
Hi, I also have Mate 9 L09 and have exact same error message:
fastboot flash recovery twrpo.img
target reported max download size of 471859200 bytes
sending 'recovery' (26982 KB)...
OKAY [ 0.579s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.600s
I downloaded that special TWRP recovery image, but still get the same message. Does not work for me, any new solution available?
Click to expand...
Click to collapse
You need to flash to recovery_ramdisk. Fastboot flash recovery_ramdisk twrpo.img
Hi there , so if we want to flash Oreo through fastboot , what could be the commands lines please ?
as ie : fastboot flash boot boot.img or boot_ramdisk / boot_kernel boot.img ? and so on ..
the complete list of commands, would any 1 pass it over here please ? thanks a bunch
FuM8 said:
Hi there , so if we want to flash Oreo through fastboot , what could be the commands lines please ?
as ie : fastboot flash boot boot.img or boot_ramdisk / boot_kernel boot.img ? and so on ..
the complete list of commands, would any 1 pass it over here please ? thanks a bunch
Click to expand...
Click to collapse
Well. You can flash most partitions. If you extract imgs from an oreo update.app you get the complete list (though some can't be flashed, like erecovery_*.img).
If you extract ramdisk (boot ramdisk) from update.app you flash it as fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img
To extract in Huawei Update Extractor you need to go to settings and disable checksum, it won't extract because something is up with erecovery_ramdis.img (it's misspelled too).
thank you for your reply @ ante0
Something else please .. as I tried and failed to update from MHA-L09-c432198 to Oreo I now get a bootloop error 14 iom3 , I saw on another thread some solutions, which dont work for me as I just cannot boot into twrp because of my battery not charging, even in download / recovery mode... battery three months old... and always working good
What I need to know is how can I either get my twrp saved system back through fastboot or else how can I flash - again only by fastboot mean - the stock firmware of my c432b198 or ...? as i need to flash boot, recovery, cust & system , how can I do so while there is no CUST img in extracted data (seems to be inside the data img itself).
Or else how can do A COMPLETE FORMAT of my internal storage ? the command , any1 i do, give either "not allowed" or partition lengh etc"
any way I can use fastboot to get out of this bootloop iom3 error 14 which don't let my battery charge a little ?
I'm a little much confused and do apology for that. Any help is desesperated needed .
So what is the boot image or the boot partition now called in OREO? I am trying to unbrick my Honor 9 and had Oreo L09-B321 on it before. The only thing I am missing is to successfully flash boot since I am also getting the "partition length error" when I use fastboot boot BOOT.img.
overflyer said:
So what is the boot image or the boot partition now called in OREO? I am trying to unbrick my Honor 9 and had Oreo L09-B321 on it before. The only thing I am missing is to successfully flash boot since I am also getting the "partition length error" when I use fastboot boot BOOT.img.
Click to expand...
Click to collapse
I think ramdisk is the boot partition in oreo, so you have to use fastboot flash ramdisk RAMDISK.img.
YASS
tobyffm said:
Hi, I also have Mate 9 L09 and have exact same error message:
fastboot flash recovery twrpo.img
target reported max download size of 471859200 bytes
sending 'recovery' (26982 KB)...
OKAY [ 0.579s]
writing 'recovery'...
FAILED (remote: partition length get error)
UPDATE:
OK, I managed it by myself, haha.
For anyone else with same issue.
Since Oreo: Partition names have changed.
Use this command: fastboot flash recovery_ramdisk RECOVERY.img
"recovery" changed to "recovery_ramdisk" now.
finished. total time: 0.600s
I downloaded that special TWRP recovery image, but still get the same message. Does not work for me, any new solution available?
Click to expand...
Click to collapse
Worked like a charm. Thanks.
****ty ADB
i have adb drivers installed but if i enter: fastboot flash recovery_ramdisk RECOVERY.img it says cannot load RECOVERY.img
still stuck
tothl74 said:
I think ramdisk is the boot partition in oreo, so you have to use fastboot flash ramdisk RAMDISK.img.
Click to expand...
Click to collapse
i still get folowing error
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (34634 KB)...
OKAY [ 1.214s]
writing 'recovery_ramdisk'...
FAILED (remote: partition error)
finished. total time: 1.235s
i have tried all three commands
fastboot flash recovery twrp_Honor_7x.img
fastboot flash recovery_ramdisk twrp_Honor_7x.img
fastboot flash ramdisk twrp_Honor_7x.img
i cant flash!! same error!!!
failed remote partition lenght get error
I have a strange problem with my brand new Mi Mix 2s.
My procedure from the beginning:
Unlook using tool from Xiaomi. For this I had to wait 72h.
Subsequently, the unlooking was considered successful.
For this I used my notebook with Windows7 (no VM).
Now I got the needed files and want to start with the installation of TWRP.
I also use my notebook but with Linux, my everyday operating system.
I have set the phone to fastboot mode (vol-down + power).
With fastboot devices you can find the phone. But commands like flash or boot end in a frozen console.
Unusual. Now I try it again in Windows7 (dualboot). The same problem.
Then I try the Windows10 game computer of my son.
The commands are confirmed as successful.
But in fact nothing happens. Nothing is flashed and I am not in the TWRP to boot.
Here the console output:
Code:
#[twrp.ing = twrp-3.2.3-0-polaris.img]
F:\platform-tools>fastboot boot twrp.img
creating boot image...
creating boot image - 43386880 bytes
Downloading 'boot.img' OKAY [ 0.914s]
booting OKAY [ 0.071s]
Finished. Total time: 1.051s
#[black screen]
F:\platform-tools>fastboot devices
19cf4510 fastboot
F:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (42368 KB) OKAY [ 0.951s]
Writing 'recovery' OKAY [ 0.201s]
Finished. Total time: 1.165s
F:\platform-tools>fastboot devices
19cf4510 fastboot
F:\platform-tools>fastboot boot twrp.img
creating boot image...
creating boot image - 43386880 bytes
Downloading 'boot.img' OKAY [ 0.910s]
booting FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
Finished. Total time: 1.009s
F:\platform-tools>fastboot devices
19cf4510 fastboot
F:\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.004s
#[reboot]
Unfortunately, I am not aware of any possibilities to solve the problem further.
Does anyone have suggestions or ideas?
Which TWRP are you flashing? Are you sure that it is the proper file for mix 2s?
What happens when you reboot the phone after flashing recovery with vol+ and power?
Flash twrp then restart manually holding vol+ and power buttons.
malimukk said:
Which TWRP are you flashing? Are you sure that it is the proper file for mix 2s?
What happens when you reboot the phone after flashing recovery with vol+ and power?
Flash twrp then restart manually holding vol+ and power buttons.
Click to expand...
Click to collapse
Yes. It is this version: https://eu.dl.twrp.me/polaris/
I have tried your tip. Does not work either.
Can it be helpful to close the bootloader and perform unloocking again?
How is the usual way to lock the device again? Using fastboot, or are there other solutions?
Can I really reopen the bootloader afterwards?
Can someone confirm that multiple opening is possible with the MIunlock tool?
yabow said:
Can it be helpful to close the bootloader and perform unloocking again?
How is the usual way to lock the device again? Using fastboot, or are there other solutions?
Can I really reopen the bootloader afterwards?
Can someone confirm that multiple opening is possible with the MIunlock tool?
Click to expand...
Click to collapse
Yes you can unlock again. I've done it myself.
I am not sure what is happening in your situation. Which MIUI version are you running?
I'd suggest you to flash a more recent version of MIUI with the Mi Flash tool.
Perhaps MIUI developer 8.12.27 version.
Let it boot to system after flashing
Then turn off, flash twrp, disconnect cable,
reboot from fastboot with Power and Vol+
No other ideas honestly
malimukk said:
Yes you can unlock again. I've done it myself.
I am not sure what is happening in your situation. Which MIUI version are you running?
I'd suggest you to flash a more recent version of MIUI with the Mi Flash tool.
Perhaps MIUI developer 8.12.27 version.
Let it boot to system after flashing
Then turn off, flash twrp, disconnect cable,
reboot from fastboot with Power and Vol+
No other ideas honestly
Click to expand...
Click to collapse
I have
MIUI-Version 10.2.1.0 GLOBAL
Model M1803D5XA
and using
fastboot version 28.0.1-4986621
on Windows10
I have tried with Linux, but here the comandline hangs and nothing happends...
Do you think i have to use a developer ROM? This can be a problem?
yabow said:
I have
MIUI-Version 10.2.1.0 GLOBAL
Model M1803D5XA
and using
fastboot version 28.0.1-4986621
on Windows10
I have tried with Linux, but here the comandline hangs and nothing happends...
Do you think i have to use a developer ROM? This can be a problem?
Click to expand...
Click to collapse
For me sometimes fastboot just does not want to work on my laptop, then I switch usb ports and it magically works again. It is usually an issue on the PC. try abother cable as well. You cab also try to uninstall your adb/fastboot drivers and install these: https://forum.xda-developers.com/showthread.php?t=2588979
Preferably on the Windows10 machine you have, as it seems closest to working.
Miui version should not be relevant, but it might be that yours is somehow messed up. I would suggest you to avoid using the mi flash tool for now as it uses fastboot to flash the different images and it might cause other issues as clearly fastboot is somehow broken. You can try to update to a dev rom thorough the phone update app?
Btw when you do fastboot boot twrp.img you have to keep the cable plugged in
Didn't change anything. Damn it.
check this
read this page (need a translater)
in MiMix2s_Xiaomi.eu_Firmware yoo find a install_TWRP.bat in folder 02_TWRP
exchange and rename your new twrp to the name in the folder
https://tradingshenzhen.com/de/cont...sh-tutorial-global-firmware-xiaomieu-firmware
So, I tried some TWRP versions (v15, v14, and others) to get the black-screen error again and again. Version v8 finally allowed me to boot into TWRP. Yeah!
Before I closed the bootloader,
got a message about a destroyed device,
reloaded the stock-ROM with MI-flash,
booted TWRP v8 from this thread,
only saw cryptic files and just used an OTG adapter to install more *imgs and *zips.
Not everything works as it should yet, but it will...
Thanks for your help.
yabow said:
So, I tried some TWRP versions (v15, v14, and others) to get the black-screen error again and again. Version v8 finally allowed me to boot into TWRP. Yeah!
Before I closed the bootloader,
got a message about a destroyed device,
reloaded the stock-ROM with MI-flash,
booted TWRP v8 from this thread,
only saw cryptic files and just used an OTG adapter to install more *imgs and *zips.
Not everything works as it should yet, but it will...
Thanks for your help.
Click to expand...
Click to collapse
Your storage is encrypted, that's why you have the "cryptic files".
TWRP v8 can not decrypt your storage, the latest version can though
My OnePlus 7 Pro keep booting into fastboot mode. Neither I can access recovery nor can start the phone. It's always comes back to recovery.
Please help me getting it done.
Bootloader is unlocked.
You haven't given enough info, tell us step by step how your "Bootloader is unlocked".
We would need to know if you did it properly, you probably need to go into the recovery and perform a "Full wipe". Unlocking the bootloader usually does that anyway.
The normal method is:
Enabled developer settings by pressing the version number in the about section 7 times and entering your pin
Copy the adb developer folder from the mounted OnePlus driver partition you usually get on your computer when attaching the phone, into a folder on your hard drive, and enable adb in developer settings.
In developer settings enable "OEM unlocking"
Reboot into fastboot mode
Open a command window (with admin privileges) in the folder you copied to your hard drive (In Windows, hold down shift and right click inside the folder, then click "Open Command Window..."
Run the command "fastboot oem unlock"
Accept the prompt shown on the phone
This will wipe the phone back to factory reset so ensure you have backed up your data, although you should be doing that before you even start.
Flash the appropriate TWRP recovery partition (which afaik isn't even available yet so I'm not sure why you would unlock the bootloader so soon to be honest
If you didn't perform those steps or performed them in the wrong order then you've done it wrong.
Performing a factory reset in the recovery partition may get it booting again but it's hard to know with the minimal information you've provided.
Although again, why are you unlocking the bootloader when there hasn't been a TWRP version released yet? You won't be able to flash anything, not even Magisk.
I've unlocked bootloader by command of OEM unlocking.
After than the unlock, I rebooted it's again And installed some Magisk file, which made it stuck at fastboot.
I can't access the Recovery nor can restart Phone.
All I can do is switched it off And get back into fastboot again after.
Yeah, you can't flash things with the default recovery (That's just made for flashing the default builds), that's most likely why. Magisk was made to be flashed with TWRP.
Did you use the test TWRP here? If so, then go to that thread for help.
If you can get into the OnePlus recovery you could maybe grab a build from here and flash the default rom back, then start again using the guide I showed you but, tbh, I would wait until a good TWRP build is established and Magisk is confirmed to be working.
That thread also looks like it has the default recovery image too so you can flash that back on the phone with :
fastboot flash recovery filename (Just put the recovery image into the same folder as your adb.exe and fastboot.exe
Then see if you can reboot into it and flash the stock rom back on from the same thread.
How can I get things done back, all I've is fastboot.
It's a New set, please help (
dmishra639 said:
How can I get things done back, all I've is fastboot.
It's a New set, please help (
Click to expand...
Click to collapse
If you have fastboot, I've just told you how to get the default recovery back in above.
---------- Post added at 05:45 PM ---------- Previous post was at 05:28 PM ----------
Reading that thread again, flashing recovery is not as simple as it used to be due to the A/B partition model used now, so you'll need to read the instructions shown for recovery. My guess is that you didn't read them properly and flashed the recovery to the wrong partition. If you have flashed that TWRP then you need to seek support in that thread.
It's not gonna work with me,
Even if I'll download the zip file it's only flashable with a Twrp or Stock recovery. As stock recovery is not working.
Even if I'll try to flash a Twrp recovery it's showing up an error to me :
PS C:\adb> fastboot devices
420bdc60 fastboot
PS C:\adb> fastboot boot C:\adb\recovery.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.636s
PS C:\adb> fastboot flash recovery C:\adb\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (18828 KB)...
OKAY [ 0.575s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.580s
PS C:\adb>
dmishra639 said:
It's not gonna work with me,
Even if I'll download the zip file it's only flashable with a Twrp or Stock recovery. As stock recovery is not working.
Even if I'll try to flash a Twrp recovery it's showing up an error to me :
PS C:\adb> fastboot devices
420bdc60 fastboot
PS C:\adb> fastboot boot C:\adb\recovery.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.636s
PS C:\adb> fastboot flash recovery C:\adb\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (18828 KB)...
OKAY [ 0.575s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.580s
PS C:\adb>
Click to expand...
Click to collapse
This will sound stupid, but I had similar issues with the pixel and it was due to drivers and the port. Tried from a different machine and worked. Do you have the luxury to do so ?
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
dmishra639 said:
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
Click to expand...
Click to collapse
Grab this fastboot rom and flash...
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Why are you trying to flash recovery partitions when they don't exist on this device? Recovery is on the boot partition.
dmishra639 said:
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
Click to expand...
Click to collapse
Since you are familiar with custom rom,unlocked bootloader etc you should had known already that you must NOT flash any kind Magisk staff without having proper and functional twrp.
Even if it flashed successful that doesn't mean will work after reboot and normal restart.
That why you've brick your device.
And on the other hand with A/B partition things has changed dramatically evolving all custom made staff and how they works.
Oneplus device not work the same way as Xiaomi you've described.
Sent from my iPad using Tapatalk Pro
LLStarks said:
Why are you trying to flash recovery partitions when they don't exist on this device? Recovery is on the boot partition.
Click to expand...
Click to collapse
paatha13 said:
Since you are familiar with custom rom,unlocked bootloader etc you should had known already that you must NOT flash any kind Magisk staff without having proper and functional twrp.
Even if it flashed successful that doesn't mean will work after reboot and normal restart.
That why you've brick your device.
And on the other hand with A/B partition things has changed dramatically evolving all custom made staff and how they works.
Oneplus device not work the same way as Xiaomi you've described.
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
Any post that describe exactly what changed? I havent flashed custom roms/kernels in close to two years due to OOS being satisfying enough. What I have done is fastboot into twrp and flash magisk(I believe). Will I still be able to do that with OP7 Pro?
dmishra639 said:
My OnePlus 7 Pro keep booting into fastboot mode. Neither I can access recovery nor can start the phone. It's always comes back to recovery.
Please help me getting it done.
Bootloader is unlocked.
Click to expand...
Click to collapse
I forget the command, but change the boot slot and try to reboot.
tech_head said:
I forget the command, but change the boot slot and try to reboot.
Click to expand...
Click to collapse
Fastboot flash boot C://path/to/recovery.img
SysAdmNj said:
Any post that describe exactly what changed? I havent flashed custom roms/kernels in close to two years due to OOS being satisfying enough. What I have done is fastboot into twrp and flash magisk(I believe). Will I still be able to do that with OP7 Pro?
Click to expand...
Click to collapse
You can read over here on 6T device details of how thing work with A/B partition.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
https://twrp.me/oneplus/oneplus6t.html
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Also follow this thread about 7 Pro situation and how well work over time
[RECOVERY][3.3.1-2][guacamole]Unofficial TWRP recovery for OnePlus 7 Pro(Testing)
Sent from my iPad using Tapatalk Pro
joemossjr said:
Fastboot flash boot C://path/to/recovery.img
Click to expand...
Click to collapse
Man, thank you so much
You literally made my day,
Wht I've did wrong in a flow was I had given the command: fastboot flash boot and the magisk location.
That was a stupidity, all I forgot was the command.
Now I used the same command and then used oxygen os fastboot flashable all bat file, as suggested by a member.
And here's my phone back. )
Thanks
In case, I'm completely New to OnePlus
It someone suggest me how to Root OnePlus 7 Pro normally, cuz I've to edit the build prop due to some reason.
My bootloader is unlocked but can't flash custom recovery.
dmishra639 said:
In case, I'm completely New to OnePlus
It someone suggest me how to Root OnePlus 7 Pro normally, cuz I've to edit the build prop due to some reason.
My bootloader is unlocked but can't flash custom recovery.
Click to expand...
Click to collapse
I remember when I edit the buildi prob on my v20 to be recognized as a pixel so google assistant can work and that bricked my device.
Robert235 said:
I remember when I edit the buildi prob on my v20 to be recognized as a pixel so google assistant can work and that bricked my device.
Click to expand...
Click to collapse
Man I've a 2gb daily add on (for 3 months), which will only gonna work with my previous device (Redmi note 5 pro).
So, I've to change OnePlus as Note 5 Pro as same.
I've did that tons of time on my past phone,it never did a brick TBH.