Hi guys, i've got this problem.
I tried to update with twrp my p20 (europe, EML-L29 C432) to emui 9 and it bricked.
Before trying it, i have done a backup with twrp.
The fastboot mode works, the recovery not, it worked for a bit but the touch doesn't.
I tried flashing everything, from 8.0 and from 9.0.
I flashed
cust worked
system worked
recovery_ramdisk worked
recovery_vbmeta worked
recovery_vendor worked
then i tried to flash vendor and ramdisk
FAILED (remote: Command not allowed).
Now the P20 is in bootloop, and goes to erecovery after a few reboots. I tried factory reset and other things from recovery, nothing is working.
Any solutions? I just want to flash vendor and ramdisk i think it can work if just the command is allowed...
EDIT:
Finally solved after few days, i used the tool beta downy and it have done everything.
Thx to all.
did you try download a full package from e-recovery to unbrick ?
doktor29 said:
did you try download a full package from e-recovery to unbrick ?
Click to expand...
Click to collapse
Yes, tried.
I don't remember the exact error but it's like "system failed" something like that...
The eRecovery it's emui 9.0
i tried to flash the eRecovery emui 8.0 but same error, Command not allowed.
I'm pretty stucked
I had the same problem, just download this androidhost. ru /1iPy (sorry I can't post any link) and copy the dload folder in an ext formatted usb, delete the eml-l09 folder (if is there), plug it in the phone and boot it with the volume up and volume down buttons pressed, it will perform an update to emui 9. Sorry for my bad English, I'm Italian. If you have any trouble reply
hydrosh said:
I had the same problem, just download this androidhost. ru /1iPy (sorry I can't post any link) and copy the dload folder in an ext formatted usb, delete the eml-l09 folder (if is there), plug it in the phone and boot it with the volume up and volume down buttons pressed, it will perform an update to emui 9. Sorry for my bad English, I'm Italian. If you have any trouble reply
Click to expand...
Click to collapse
Fine
can 't enter phone on upgrade mode
Related
I have totally failed to rebrand my FRD-AL10 (EMUI 5, Nougat) to FRD-L19 (because I was hoping to get rid of all the apps/functions/messages in Chinese) by following the steps listed on another thread.
I did eventually manage to get it to identify as FRD-L19 but when it did boot up it had no stock keyboard only voice commands and the phone was unusable . it said it was Android 7, model FRD-L19 and build number was nrd90m test keys?
I tried to update with the latest FRD-L19 update.app by copying it into the dload and vol up+vol down +power buttons press but the update failed and since then I am stuck with the phone refusing to boot, or to boot into twrp recovery.
It hangs at the booting now orange letters screen (It says "Your device is booting now...." and nothing more happens.
If I hold vol up and power up, it hangs at "Your device is booting now...."
If I wait until it says I can press vol up for Erecovery it goes into Huawei erecovery and that tries to download latest version update by wifi, it connects to wifi but says "Getting package info failed".
If I go to reboot from erecovery it goes back to the Your device is booting now.... and stops.
I can shutdown from erecovery (but if its still plugged in it goes straight back to "Your device is booting now...")
From shutdown (and unplugged from USB) - if I hold vol up+ vol down + power it goes to EMUI Installing update then Software Install failed. The update package does not exist. Please download the package again. Reboot system now.
I don't know how to put an alternative update package into dload when I can only use fastboot mode and nothing else?
I can do that by shutting it own from erecovery shut down page and holding down volume and power up.
I assume I need to go back to stock firmware for FRD-AL10 like this one from another thread FRD-AL10_C00B135_Firmware_China_Nonspecific_Android 6.0_EMUI 4.1_05013LBP
and not version 7.0 stock rom for FLD-L19???
Anyway, I unzipped that and use Huawei extractor tool to extract Boot.img, cust.img, recovery.img and sys.img as suggested on this thread.
I can fastboot flash 3 of those but the cust.img fails to flash with "partition error"
I also tried to fastboot format user data but the command failed FAILED (remote: Command not allowed)
I don't think its possible to use the unbrick function of huawei multitool because I can't get into recovery mode?
I don't think I can get a different copy of update.app file into the dload folder internal memory and use the vol up+ vol down +power buttons because I can no longer get the phone to boot to system.
The fastboot screen says PHONE Unlocked
FRP Unlock
Would be very grateful for suggestions on what I should be doing to unbrick this, please. Sorry for being a stupid newbie.... and I honestly have been reading these threads day and night for 2 days but am still stuck!!
Thanks
Edit: is part of the answer to try to flash a different version of twrp again? So I have to put the right version of twrp.img into my adb folder and then fastboot flash recovery twrp*****.img ? Then I might be able to fastboot boot recovery ? Or if twrp works I can flash the right stock rom? (which one? given I was trying to rebrand)
Or if I could somehow get back system to boot, I could use adb push to put the correct update.app into dload on internal memory and use the vol up+ vol down +power???
Bro first flash the compitable twrp
For nougat flash this twrp https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Follow my rebranding guide in guide and threads there is zip for frd19 flash that one
Here is my guide link https://forum.xda-developers.com/honor-8/how-to/guide-honor-8-to-frd-l19-t3632220
Rommco05 said:
Is better following venugopalu method
Click to expand...
Click to collapse
Yes , becasue my zip contains oem restore if the devcie dont have oem it will restore and successfully restore the device
venugopalu007 said:
Bro first flash the compitable twrp
For nougat flash this twrp https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Follow my rebranding guide in guide and threads there is zip for frd19 flash that one
Here is my guide link https://forum.xda-developers.com/honor-8/how-to/guide-honor-8-to-frd-l19-t3632220
Click to expand...
Click to collapse
Thank you
That was the twrp had success with before..... but everything seemed to go wrong at step 5 of the debranding guide. Where I was supposed to do a data wipe when the device immediately rebooted after installing the zip?
Then I was confused about whether I needed to put the firmware update file into sdcard/dload or not and whether it should be internal memory /close instead. And whether the firmware was correct when it said Android 6 when the phone said it was android 7????
And then there was no keyboard only google voice.....
But I will definitely start by trying to flash that twrp again... and if that can work... then the L19 Rom from your debranding guide again. And let you know.
Thanks
venugopalu007 said:
Bro first flash the compitable twrp
For nougat flash this twrp https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Follow my rebranding guide in guide and threads there is zip for frd19 flash that one
Here is my guide link https://forum.xda-developers.com/honor-8/how-to/guide-honor-8-to-frd-l19-t3632220
Click to expand...
Click to collapse
Thank you
That was the twrp had success with before..... but everything seemed to go wrong at step 5 of the debranding guide. Where I was supposed to do a data wipe when the device immediately rebooted after installing the zip?
Then I was confused about whether I needed to put the firmware update file into sdcard/dload or not and whether it should be internal memory /close instead. And whether the firmware was correct when it said Android 6 when the phone said it was android 7????
And then there was no keyboard only google voice.....
But I will definitely start by trying to flash that twrp again... and if that can work... then the L19 Rom from your debranding guide again. And let you know.
Thanks
So held down power which started the reboot and enabled me to press vol up to enter erecovery and choose shut down.
then volume down whilst connecting usb to PC to put into fastboot mode
then copy your file twrp-3.1.1-1-frd.img to minimal adb directory on my pc
then in minimal adb: fastboot flash recovery twrp-3.1.1-1-frd.img
I have got that far.
Then do I fastboot reboot?
and hope it boots to system so I can copy over the zip file from my pc with file explorer and then
do I adb reboot recovery (to get into twrp)?
then install the FRD-L19C432B131-hw-eu-OPU_TWRP_FRD.zip file using twrp? (or do you mean another method of installing that rom)?
then still in twrp I do Wipe: format user data?
then do I reboot to system?
At what point do I need to copy the update.app to sdcard\dload and use the vol up+ vol down + power to install the update?
Thanks again
Agatha_honor 8 said:
Thank you
That was the twrp had success with before..... but everything seemed to go wrong at step 5 of the debranding guide. Where I was supposed to do a data wipe when the device immediately rebooted after installing the zip?
Then I was confused about whether I needed to put the firmware update file into sdcard/dload or not and whether it should be internal memory /close instead. And whether the firmware was correct when it said Android 6 when the phone said it was android 7????
And then there was no keyboard only google voice.....
But I will definitely start by trying to flash that twrp again... and if that can work... then the L19 Rom from your debranding guide again. And let you know.
Thanks
Click to expand...
Click to collapse
After twrp sucess you have to biot the device it will works normal but you have to go reboot to recovery and do a factory wipe and shutdown then after doebload the official firmware of frd19 which is mm and dlaod the update.app and three buttons trick it will update and relock the bootloader and update to EMUI 5 by the phone updater app in settings
I got this far:
So held down power which started the reboot and enabled me to press vol up to enter erecovery and choose shut down.
then volume down whilst connecting usb to PC to put into fastboot mode
then copy your file twrp-3.1.1-1-frd.img to minimal adb directory on my pc
then in minimal adb: fastboot flash recovery twrp-3.1.1-1-frd.img
then I rebooted and got back to the screen where system fails to load "Your device is booting now"
So I pressed power off and then held down volume up but it boots only to erecovery so I pressed shut down and decided I needed to unplug usb.
I tried again with holding down volume up and powering up and managed to boot into twrp.
In twrp I do wipe: swipe to factory reset.
Twrp says Failed to mount '/cust' (invalid argument)
and Failed to mount '/system' (invalid argument)
with windows explorer on my pc and the phone in twrp I can only see the /sdcard but I can see the FRD-L19C432B131-hw-eu-OPU_TWRP_FRD.zip is there.
So in twrp I go to install and I try to flash FRD-L19C432B131-hw-eu-OPU_TWRP_FRD.zip from /external_sd (with the zip signature check and reboot after install boxes unchecked)
It starts to write UPDATE.APP..... Completed! script succeeded....
E: unknown command []]
updating partition details....
Failed to mount /cust (invalid argument)
Failed to mount /data (device or resource busy)
Failed to mount /system (invalid argument)
Failed to mount /product (invalid argument)
I try to wipe data and get the same Failed to mount messages
I down load Honor 8_Firmware_FRD-L19_Android 6.0_EMUI 4.1_C432B131_United Kingdom .zip on my pc and unzip it.
I copy the dload folder including update.app to Honor 8:microSDcard
Then I went to power off in twrp so I could do the 3 button load from dload but twrp says "No OS installed! Are you sure you want to power off?"
So I'm not sure? Please can you help again?
Agatha_honor 8 said:
I got this far:
So held down power which started the reboot and enabled me to press vol up to enter erecovery and choose shut down.
then volume down whilst connecting usb to PC to put into fastboot mode
then copy your file twrp-3.1.1-1-frd.img to minimal adb directory on my pc
then in minimal adb: fastboot flash recovery twrp-3.1.1-1-frd.img
then I rebooted and got back to the screen where system fails to load "Your device is booting now"
So I pressed power off and then held down volume up but it boots only to erecovery so I pressed shut down and decided I needed to unplug usb.
I tried again with holding down volume up and powering up and managed to boot into twrp.
In twrp I do wipe: swipe to factory reset.
Twrp says Failed to mount '/cust' (invalid argument)
and Failed to mount '/system' (invalid argument)
with windows explorer on my pc and the phone in twrp I can only see the /sdcard but I can see the FRD-L19C432B131-hw-eu-OPU_TWRP_FRD.zip is there.
So in twrp I go to install and I try to flash FRD-L19C432B131-hw-eu-OPU_TWRP_FRD.zip from /external_sd (with the zip signature check and reboot after install boxes unchecked)
It starts to write UPDATE.APP..... Completed! script succeeded....
E: unknown command []]
updating partition details....
Failed to mount /cust (invalid argument)
Failed to mount /data (device or resource busy)
Failed to mount /system (invalid argument)
Failed to mount /product (invalid argument)
I try to wipe data and get the same Failed to mount messages
I down load Honor 8_Firmware_FRD-L19_Android 6.0_EMUI 4.1_C432B131_United Kingdom .zip on my pc and unzip it.
I copy the dload folder including update.app to Honor 8:microSDcard
Then I went to power off in twrp so I could do the 3 button load from dload but twrp says "No OS installed! Are you sure you want to power off?"
So I'm not sure? Please can you help again?
Click to expand...
Click to collapse
bro neglet the mount issues after update.app write sucess reboot the phone once and let it boot comoletly .after that dload the offical ROM of frd l19 . and do a reset in stock recovery.
Ok so I rebooted and EMUI said it was doing a factory reset
then the phone booted up with asking me for language, wifi password
then it wants to do a quick update FRD-L19432B360 2.83 GB so I hit quick update.
then it reboots like a normal set up and the keyboard works and everything looks ok. It says that the build number is FRD-L19432B360
Do I still need to do the dload?
Thank you so much - I would never have got this far otherwise!
Agatha_honor 8 said:
Ok so I rebooted and EMUI said it was doing a factory reset
then the phone booted up with asking me for language, wifi password
then it wants to do a quick update FRD-L19432B360 2.83 GB so I hit quick update.
then it reboots like a normal set up and the keyboard works and everything looks ok. It says that the build number is FRD-L19432B360
Do I still need to do the dload?
Thank you so much - I would never have got this far otherwise!
Click to expand...
Click to collapse
No bro not needed , enjoy the device .
Add the fixed tag to the thread.:highfive:
---------- Post added at 03:22 PM ---------- Previous post was at 03:18 PM ----------
Bro but i will suggest you to from marshmallow go directly to the new update of nougat using firmware finder because, the update from b360 is stopped, sh!t huawei server stopped the update idk y , many people also stucked in b360 , so my idea is just go to latest update in firmware finder from marshmallow.
Any help just reply.
If you got another update from b360 just neglet my above steps and go on . Enjoy.
It was ok today when it wanted to update to B389. Now I'm stuck back with only erecovery again.
I can get back into fastboot and unlock the phone again and I put on twrp again and got back into it but
I'm confused about which firmware I need to flash
The latest version for FRD L19 in firmware finder is B392 and I would need the 3 files - update.zip, update_full_FRD-L19_hw_eu.zip and update_data_full_public.zip and to flash all 3 - I tried that but got a lot of errors and it won't boot
But I need to flash something or put on the MM dload/MM update you posted first? do I go back to the B131 MM you linked before first? Then I somehow update to the B392?
I'm so sorry to keep asking stupid questions!!
Agatha_honor 8 said:
It was ok today when it wanted to update to B389. Now I'm stuck back with only erecovery again.
I can get back into fastboot and unlock the phone again and I put on twrp again and got back into it but
I'm confused about which firmware I need to flash
The latest version for FRD L19 in firmware finder is B392 and I would need the 3 files - update.zip, update_full_FRD-L19_hw_eu.zip and update_data_full_public.zip and to flash all 3 - I tried that but got a lot of errors and it won't boot
But I need to flash something or put on the MM dload/MM update you posted first? do I go back to the B131 MM you linked before first? Then I somehow update to the B392?
I'm so sorry to keep asking stupid questions!!
Click to expand...
Click to collapse
Flash this first update_full_FRD-L19_hw_eu.zip
And then flash update.zip .
If after flashing reboot got strucked in blue screen just format factory resey in recovery.
I flashed update_full_FRD-L19_hw_eu.zip
And then flash update.zip .
They both failed with error 7?
So I went back to your B131 and my phone is unbricked but this time I didn't accept B360.
But how do I get to the latest Nougat?
From Firmware Finder I thought it was B392 for L19CB432 but maybe its B384 for L19C10??
Agatha_honor 8 said:
I flashed update_full_FRD-L19_hw_eu.zip
And then flash update.zip .
They both failed with error 7?
So I went back to your B131 and my phone is unbricked but this time I didn't accept B360.
But how do I get to the latest Nougat?
From Firmware Finder I thought it was B392 for L19CB432 but maybe its B384 for L19C10??
Click to expand...
Click to collapse
Strange
So just update to nougat via system app , later try to flash the zips through twrp and give atry
Ok thanks updated to b360 again via system app so build number is showing FRD-L19432B360
then oem unlock then flash twrp then tried to twrp flash B392 for L19CB432 update_full_FRD-L19_hw_eu.zip but twrp says "E: unknown command [errno]
update_huawei_pkg_from_ota.zip: update package from zip failed
Updated process ended with Error:7
Error installing zip file '/external_sd/update_full_FRD_hw_eu.zip '
Agatha_honor 8 said:
Ok thanks updated to b360 again via system app so build number is showing FRD-L19432B360
then oem unlock then flash twrp then tried to twrp flash B392 for L19CB432 update_full_FRD-L19_hw_eu.zip but twrp says "E: unknown command [errno]
update_huawei_pkg_from_ota.zip: update package from zip failed
Updated process ended with Error:7
Error installing zip file '/external_sd/update_full_FRD_hw_eu.zip '
Click to expand...
Click to collapse
The problem is in b392 they are not flashable , decrease the version try all because idk y the zips are not flashing , in my version frdl02 they are flashed successfully without any issue.
Agatha_honor 8 said:
Ok so I rebooted and EMUI said it was doing a factory reset
then the phone booted up with asking me for language, wifi password
then it wants to do a quick update FRD-L19432B360 2.83 GB so I hit quick update.
then it reboots like a normal set up and the keyboard works and everything looks ok. It says that the build number is FRD-L19432B360
Do I still need to do the dload?
Thank you so much - I would never have got this far otherwise!
Click to expand...
Click to collapse
I Need This Firmware Plz FRD-L19432B360
I Tried To Find Full Package But Could Not Find
I Need Help Plz
Thanks Anticipation
Model: BLN L-24
I am stuck in error mode with
Func NO: 11 (recovery image)
Error NO: 2 (failed load!)
I have tried to re-flash several custom recovery I have used in the past, however none seem to work and end with the same result.
I have also tried flashing the stock recovery2.img from the Update.app for my model, but that also doesn't work and ends with a FAILED (remote: Partition Error)
I have run into troubles before, but I'm stumped with this one, I can at least still boot into fastboot.
Any help would be appreciated.
Hyperweasle said:
Model: BLN L-24
I am stuck in error mode with
Func NO: 11 (recovery image)
Error NO: 2 (failed load!)
I have tried to re-flash several custom recovery I have used in the past, however none seem to work and end with the same result.
I have also tried flashing the stock recovery2.img from the Update.app for my model, but that also doesn't work and ends with a FAILED (remote: Partition Error)
I have run into troubles before, but I'm stumped with this one, I can at least still boot into fastboot.
Any help would be appreciated.
Click to expand...
Click to collapse
What's your Android version. What were you trying to do. What recoveries have you tried and what's the command you're using. I had the same error yesterday because I flashed wrong TWRP. Fixed it by reflashing correct image.
Mannan Qamar said:
What's your Android version. What were you trying to do. What recoveries have you tried and what's the command you're using. I had the same error yesterday because I flashed wrong TWRP. Fixed it by reflashing correct image.
Click to expand...
Click to collapse
The version was Android 8 Oreo
I started out trying to go back to EMUI 8.0 from Open Kirin RROS Beta 2. So I followed this guide https://forum.xda-developers.com/honor-6x/how-to/update-bln-l22c675-emui-5-x-x-to-emui-8-t3819317
I tried the TWRP from download in the guide that was in the HWOTA8_BLN folder along with the TWRP from here https://forum.xda-developers.com/honor-6x/development/rom-emui-8-0-0-honor-6x-dual-sim-t3794079
The command I was using to flash the recoveries I believe is correct also which is the fastboot flash recovery_ramdisk "name of image" command. That command will flash successfully with the custom recoveries, however it will still bring up the error mode despite pressing +vol button.
The stock recoveries I extracted from the update.app file, I downloaded from here: https://pro-teammt.ru/firmware-database/?firmware_model=bln-L24&firmware_page=0. Which are the stock recoveries that end up with the FAILED (remote: Partition Error) Message.
Hyperweasle said:
The version was Android 8 Oreo
I started out trying to go back to EMUI 8.0 from Open Kirin RROS Beta 2. So I followed this guide https://forum.xda-developers.com/honor-6x/how-to/update-bln-l22c675-emui-5-x-x-to-emui-8-t3819317
I tried the TWRP from download in the guide that was in the HWOTA8_BLN folder along with the TWRP from here https://forum.xda-developers.com/honor-6x/development/rom-emui-8-0-0-honor-6x-dual-sim-t3794079
The command I was using to flash the recoveries I believe is correct also which is the fastboot flash recovery_ramdisk "name of image" command. That command will flash successfully with the custom recoveries, however it will still bring up the error mode despite pressing +vol button.
The stock recoveries I extracted from the update.app file, I downloaded from here: https://pro-teammt.ru/firmware-database/?firmware_model=bln-L24&firmware_page=0. Which are the stock recoveries that end up with the FAILED (remote: Partition Error) Message.
Click to expand...
Click to collapse
You tried to use HWOTA 8 to go back to stock? Dude. Use Hurupdater. Now, to fix. First of all search XDA for TWRP for hi6250. You can use Elemental but try this one first. Flash it via PowerShell. Does that give any errors? Now once it's flashed, don't reboot. Disconnect phone from PC and hold Volume Up and Power button simultaneously. You should boot into TWRP. What does bootloader say. Phone Locked or Unlocked? What about FRP? The stock recovery didn't work cause you used the BLN-L24 one which is for EMUI 5. You're on EMUI 8. Try to boot into TWRP
Mannan Qamar said:
You tried to use HWOTA 8 to go back to stock? Dude. Use Hurupdater. Now, to fix. First of all search XDA for TWRP for hi6250. You can use Elemental but try this one first. Flash it via PowerShell. Does that give any errors? Now once it's flashed, don't reboot. Disconnect phone from PC and hold Volume Up and Power button simultaneously. You should boot into TWRP. What does bootloader say. Phone Locked or Unlocked? What about FRP? The stock recovery didn't work cause you used the BLN-L24 one which is for EMUI 5. You're on EMUI 8. Try to boot into TWRP
Click to expand...
Click to collapse
https://forum.xda-developers.com/p8.../recovery-twrp-3-2-3-0-huawei-hi6250-t3859959
Ok so I flashed this one with Powershell, and it didn't show up any errors. However I still can't seem to boot into recovery and it continues to show up error mode, even while doing as you say and pressing the vol+ and power in fastboot. Also both FRP and Phone are unlocked
Hyperweasle said:
https://forum.xda-developers.com/p8.../recovery-twrp-3-2-3-0-huawei-hi6250-t3859959
Ok so I flashed this one with Powershell, and it didn't show up any errors. However I still can't seem to boot into recovery and it continues to show up error mode, even while doing as you say and pressing the vol+ and power in fastboot. Also both FRP and Phone are unlocked
Click to expand...
Click to collapse
Use Huawei multi tool 8 to unbrick your device it's easier and just use the firmware that you were in before
Hyperweasle said:
https://forum.xda-developers.com/p8.../recovery-twrp-3-2-3-0-huawei-hi6250-t3859959
Ok so I flashed this one with Powershell, and it didn't show up any errors. However I still can't seem to boot into recovery and it continues to show up error mode, even while doing as you say and pressing the vol+ and power in fastboot. Also both FRP and Phone are unlocked
Click to expand...
Click to collapse
Try Dload
hamid1999 said:
Use Huawei multi tool 8 to unbrick your device it's easier and just use the firmware that you were in before
Click to expand...
Click to collapse
Mannan Qamar said:
Try Dload
Click to expand...
Click to collapse
I tried both of those things and still couldn't get it working.
dload doesn't pop up and multi tool fails to flash the recovery_ramdisk.img when trying to unbrick it.
I do remember before any of this happened that I was having a problem with my internal storage as I didn't have access to it. All file mangers I tried couldn't access it and showed it up as blank and TWRP showed it with 0mb.
I have a feeling that my internal storage is screwed up and that's why all attempt to flash anything have failed. I may just have face the fact that it's dead.
Hyperweasle said:
I tried both of those things and still couldn't get it working.
dload doesn't pop up and multi tool fails to flash the recovery_ramdisk.img when trying to unbrick it.
I do remember before any of this happened that I was having a problem with my internal storage as I didn't have access to it. All file mangers I tried couldn't access it and showed it up as blank and TWRP showed it with 0mb.
I have a feeling that my internal storage is screwed up and that's why all attempt to flash anything have failed. I may just have face the fact that it's dead.
Click to expand...
Click to collapse
As long as it turns on it isn't dead. Did you try DC unlocker? That often works. Try it and if it fails go to service center and play dumb. Say it happened like this after a update.
Edit. Let it power off. When it turns on hold Volume Up
Ok, so I had oreo in my 6x indian variant, and wanted to flash elemental OS V8. But for some reason the TWRP was not able to access the data partition. And when I read somewhere in XDA (in other device's forum) that changing the file system from f2fs to ext4 can help and did so and it worked. I could access my internal storage and everything on TWRP. But I didn't change the file system back to f2fs and sideloaded the elemental 8. It worked find and I installed it. When rebooting it got into bootloop. After that I tried to get into the TWRP but didn't work. I flashed the TWRP again which said flashed OK, but when I tried to enter it took me to the stock recovery. When I tried the dload method with the nougat B360 version, it gave me blank screen with red led blinking and nothing working after that. I tried dload with the oreo file which gave me back the stock recovery and erecovery, but again flashing TWRP didn't work. After dload, it reboots to erecovery and asks me to wipe data partition since it is severely corrupt but says factory reset failed. In some cases it does go factory reset but doesn't boot into OS. Since I do not have access to TWRP I am not able to bring it back. I had got into this situations before but the dload always worked. Maybe now it isn't because I am on Oreo and the partitions are different from Nougat? I also tried formatting/erasing partitions from fastboot but gives me error/ remote command not allowed. I also tried Multi-Tool8 and used the unbrick option. but doesn't work it gives me all flashed, and when i flash the oreo files gives me all flashed Error#1, Complete, Something went wrong and bootloops again or gives me blank screens.
I have attached a screenshot of my device info. If anyone could help me breath life into it.
casperskie said:
Ok, so I had oreo in my 6x indian variant, and wanted to flash elemental OS V8. But for some reason the TWRP was not able to access the data partition. And when I read somewhere in XDA (in other device's forum) that changing the file system from f2fs to ext4 can help and did so and it worked. I could access my internal storage and everything on TWRP. But I didn't change the file system back to f2fs and sideloaded the elemental 8. It worked find and I installed it. When rebooting it got into bootloop. After that I tried to get into the TWRP but didn't work. I flashed the TWRP again which said flashed OK, but when I tried to enter it took me to the stock recovery. When I tried the dload method with the nougat B360 version, it gave me blank screen with red led blinking and nothing working after that. I tried dload with the oreo file which gave me back the stock recovery and erecovery, but again flashing TWRP didn't work. After dload, it reboots to erecovery and asks me to wipe data partition since it is severely corrupt but says factory reset failed. In some cases it does go factory reset but doesn't boot into OS. Since I do not have access to TWRP I am not able to bring it back. I had got into this situations before but the dload always worked. Maybe now it isn't because I am on Oreo and the partitions are different from Nougat? I also tried formatting/erasing partitions from fastboot but gives me error/ remote command not allowed. I also tried Multi-Tool8 and used the unbrick option. but doesn't work it gives me all flashed, and when i flash the oreo files gives me all flashed Error#1, Complete, Something went wrong and bootloops again or gives me blank screens.
I have attached a screenshot of my device info. If anyone could help me breath life into it.
Click to expand...
Click to collapse
What command you use to flash TWRP? And what image are you trying to flash? Try this. In Fastboot flash RECOVERY-V2.img (Elemental ROM TWRP) via command.
fastboot flash recovery_ramdisk RECOVERY-V2.img
After it's flashed, press and Hold Power and Volume Up till you see Honor logo then let go. It Should boot to TWRP. If not then extract the Uodate.zip (the large one) and you will get Update.app and using Huawei Update Extractor extract System.img, Ramdisk.img and Recovery_ramdisk.img then boot phone to fastboot and flash them manually as
fastboot flash boot boot.img
fastboot flash recovery_ramdisk Recovery_ramdis.img
And,
fastboot flash system system.img
This should work. It's a boot error.
I was in same mode in fastboot when i updated to Oreo and it was b340 which saved me from this via dload. You give it a try.
You may not be able to flash twrp now as your BL me be locked after dload.
Mannan Qamar said:
What command you use to flash TWRP? And what image are you trying to flash? Try this. In Fastboot flash RECOVERY-V2.img (Elemental ROM TWRP) via command.
fastboot flash recovery_ramdisk RECOVERY-V2.img
After it's flashed, press and Hold Power and Volume Up till you see Honor logo then let go. It Should boot to TWRP. If not then extract the Uodate.zip (the large one) and you will get Update.app and using Huawei Update Extractor extract System.img, Ramdisk.img and Recovery_ramdisk.img then boot phone to fastboot and flash them manually as
fastboot flash boot boot.img
fastboot flash recovery_ramdisk Recovery_ramdis.img
And,
fastboot flash system system.img
This should work. It's a boot error.
Click to expand...
Click to collapse
I did try that but from the unbrick option from Multi-Tool. And also there are two recovery images in the UPDATE.APP and I don't know which one to flash. When I tried from the Multi-Tool, it says you're trying to flash the wrong image. Also I think the boot partition in oreo is ramdisk? I am not sure... because there is no boot image in the unbrick option. Although I didn't try flashing them individually. I will try it and let you know. Thanks.
shashank1320 said:
I was in same mode in fastboot when i updated to Oreo and it was b340 which saved me from this via dload. You give it a try.
You may not be able to flash twrp now as your BL me be locked after dload.
Click to expand...
Click to collapse
I actually relocked and unlocked the bootloader again, just to be sure. But will try the B340 one, didn't try that. Thanks for the links will check them out
casperskie said:
I did try that but from the unbrick option from Multi-Tool. And also there are two recovery images in the UPDATE.APP and I don't know which one to flash. When I tried from the Multi-Tool, it says you're trying to flash the wrong image. Also I think the boot partition in oreo is ramdisk? I am not sure... because there is no boot image in the unbrick option. Although I didn't try flashing them individually. I will try it and let you know. Thanks.
Click to expand...
Click to collapse
Yes, boot is ramdisk in oreo and recovery is ramdisk_recovery.
shashank1320 said:
I was in same mode in fastboot when i updated to Oreo and it was b340 which saved me from this via dload. You give it a try.
You may not be able to flash twrp now as your BL me be locked after dload.
Click to expand...
Click to collapse
So the B340 dload didn't work for me. Gives the same results. Always boots into erecovery and then fails to factory reset. Also the phone doesn't get switched on or boot into recovery without connecting to the USB. Only when it is connected it works, that too after 5-10 mins after I press the Power button or the Recovery key combination. And I used a 4GB memory card, could this be the reason the dload didn't work?
casperskie said:
So the B340 dload didn't work for me. Gives the same results. Always boots into erecovery and then fails to factory reset. Also the phone doesn't get switched on or boot into recovery without connecting to the USB. Only when it is connected it works, that too after 5-10 mins after I press the Power button or the Recovery key combination. And I used a 4GB memory card, could this be the reason the dload didn't work?
Click to expand...
Click to collapse
You may need 8 GB SD card if you have or can borrow and see if that helps. Whats the size of update.app file?
casperskie said:
I did try that but from the unbrick option from Multi-Tool. And also there are two recovery images in the UPDATE.APP and I don't know which one to flash. When I tried from the Multi-Tool, it says you're trying to flash the wrong image. Also I think the boot partition in oreo is ramdisk? I am not sure... because there is no boot image in the unbrick option. Although I didn't try flashing them individually. I will try it and let you know. Thanks.
Click to expand...
Click to collapse
Nope flashing the files individually also doesn't work. it's all the same.
shashank1320 said:
You may need 8 GB SD card if you have or can borrow and see if that helps. Whats the size of update.app file?
Click to expand...
Click to collapse
Something around 3.3 GB. There's only some 250mb left in the card when I copy the update.app
casperskie said:
Something around 3.3 GB. There's only some 250mb left in the card when I copy the update.app
Click to expand...
Click to collapse
May be you can try with 8 gb once if it is easily available for you
Hi, so none of the methods work. But I could get back to TWRP for Elemental Rom. Still flashing roms from TWRP doesn't boot me in. And now the dload screen doesn't appear when I press the combination. All I have is fastboot mode, erecovery and TWRP installed. But none of the methods work. I am not able to figure what I am doing wrong!!
Try hurupdater.
http://https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
0.3 for nougat or 0.4 for oreo (in my case works)
And remember format data in first time
You need the firmware for your 6x...
Good luck!
hey i am in the same situation as yours, all i am able to boot into is fastboot, nothing beyond that is working, i have the extracted update.app for oreo , the last system i flashed was emui oreo , and nothing else is working i have tried all the options suggested.
could someone guide me on the actual steps needed to flash the .img files as i'm unable to boot into recovery of twrp or openkirin
any help will be appreciated.
ppawan said:
hey i am in the same situation as yours, all i am able to boot into is fastboot, nothing beyond that is working, i have the extracted update.app for oreo , the last system i flashed was emui oreo , and nothing else is working i have tried all the options suggested.
could someone guide me on the actual steps needed to flash the .img files as i'm unable to boot into recovery of twrp or openkirin
any help will be appreciated.
Click to expand...
Click to collapse
Just dload the b340 image of nougat and back to nougat.
Hi people,
I need some help here and I hope anybody got an idea to get my FRD-L09 (C432 - on B521 base with OpenKirin's RROS Oreo) to work again somehow.
Situation is: After a failed attempt to upgrade the firmware base to B562 my device is now bootlooping, and goes into eRecovery, after one or two tries to boot, which is then offering to "Download and recovery". That fails at getting package info ("Getting package info failed").
Next I tried to install full OTA-PV package (extracted UPDATE.APP) via dload folder on my SD - that fails at 5 % ("Software install failed!"). For this I took the service ROM from this thread (see post #24 for Oreo version) and version B521 for FRD-L09C432 from firmware finder.
I also tried to get into TWRP 3.2.0 from Huawei Multi-Tool by TeamMT but this suddenly reboots after a few seconds everytime - so this is also useless (I tried several TWRP versions I found - maybe 'bootcomplete=false'?). I hoped to flash the extracted .img files with it.
Flashing the extracted .img files (specially the vendor image, because I think I destroyed it somehow) via fastboot also fails with error "command not allowed". Replacing the eRecovery with TWRP is also not possible (not allowed).
Flashing to system, recovery_ramdisk, kernel etc. via fastboot is possible without any problems - which shows that bootloader and frp are both unlocked.
Info btw: in this few seconds in TWRP I could see that vendor partition cannot be mounted - which shows that it's likely an error on this partition.
Is there any way to flash any "other" (vendor) partition via fastboot? Or do you guys have any ideas to this what I can try - except for bringing this thing to service center for repair :silly:? And please ask, if something is not clear or I forgot to give any info.
Any help is very appreciated.
cypher187 said:
Any help is very appreciated.
Click to expand...
Click to collapse
Okay, I brought it back to life again.
TWRP by Pretoriano80 and zxz0O0 for BKL (Honor view 10) (link) worked and let me flash firmware again. I used HuRU to flash B562 - and now it's booting again.
Soo... what can I do next to mess up my device :silly:
And note for me: HiSuite, eRecovery and 'update via dload' are all useless in case of a problem.
cypher187 said:
Okay, I brought it back to life again.
TWRP by Pretoriano80 and zxz0O0 for BKL (Honor view 10) (link) worked and let me flash firmware again. I used HuRU to flash B562 - and now it's booting again.
Soo... what can I do next to mess up my device :silly:
And note for me: HiSuite, eRecovery and 'update via dload' are all useless in case of a problem.
Click to expand...
Click to collapse
In my case eRecovery save my a*s 2 times
ScardracS said:
In my case eRecovery save my a*s 2 times
Click to expand...
Click to collapse
Usually dload did the job well for me. I don't know why it didn't in that case.
But I'm still looking for an easy way to upgrade the firmware base for future use (in case we get some) :laugh:
Next time just use HiSuite windows version with Firmware Finder's DNS trick to flash any stock ROM version what you need, only works with version 5.0.2.300. I've got the same issue and recoered by this method ease.
You can download it here.
Under AICP14 i had significant problems with Bluetooth, so I'm back to the latest pie version via erecovery ... all right. Then in preparation for root in TWRP noticed that data is again encrypted. So reset to factory settings via twrp, rebooted into the TWRP3.2.3-3 and formatted data with yes. Thereafter, on the screen was "formatting done," but down the blue animation was still running around, about 10 minutes, apparently hung. Since I could not do anything else, power button long pressed and booted again into the TWRP, but the hangs at the entrance screen, probably clear in the unsuccessful attempt to decrypt data. The Erecovery with the ability to restore the system and the stock recovery is not reachable for me, with everything I've tried. Fastboot is still to reach ... When booting the device will always hang at the inscription "The device is booted" ...has someone an idea? ? Thanks for thinking!
How to restore erecovery? It was pie, latest version installed from erecovery on the device before this crash...
Flash the erecovery partition. Extract the IMG from the update.zip file and flash the same.
shashank1320 said:
Flash the erecovery partition. Extract the IMG from the update.zip file and flash the same.
Click to expand...
Click to collapse
Got an error trying to extract:
borisku said:
Got an error trying to extract:
Click to expand...
Click to collapse
Go to settings and disable checksum or some verification. Dont remember the exact one but its there in setting
shashank1320 said:
Go to settings and disable checksum or some verification. Dont remember the exact one but its there in setting
Click to expand...
Click to collapse
I Managed to extract ERECOVERY_RAMDI.img and ERECOVERY_RAMDI.img header... i also extracted SYSTEM.img/header and RECOVERY_RAMDIS.img/header frum the update.app
Is it correcht to follow this syntax:
fastboot flash erecovery_ramdisk ERECOVERY_RAMDI.img
to reflash the erecovery? btw. i dont know the exact version of the firmware i installed, it was yesterday i think it had been BKL-L09 (9.0.0.233) C432E4R1P12 , but i cant find that as an update.zip. So i took BKL-L09C432E4R1P8B108-log (9.0.0.108) and extracted the files from there...
borisku said:
I Managed to extract ERECOVERY_RAMDI.img and ERECOVERY_RAMDI.img header... i also extracted SYSTEM.img/header and RECOVERY_RAMDIS.img/header frum the update.app
Is it correcht to follow this syntax:
fastboot flash erecovery_ramdisk ERECOVERY_RAMDI.img
to reflash the erecovery? btw. i dont know the exact version of the firmware i installed, it was yesterday i think it had been BKL-L09 (9.0.0.233) C432E4R1P12 , but i cant find that as an update.zip. So i took BKL-L09C432E4R1P8B108-log (9.0.0.108) and extracted the files from there...
Click to expand...
Click to collapse
As long as it is pie erecovery, it should work fine. Yes, flash that file.
shashank1320 said:
As long as it is pie erecovery, it should work fine. Yes, flash that file.
Click to expand...
Click to collapse
No success:
sending erecovery_ramdisk (32768KB)
okay [0.707s]
writing 'erecovery_ramdisk
FAILED (remote: command not allowed)
or should i flash to recovery_ramdisk not to Erecovery_ramdisk?
borisku said:
No success:
sending erecovery_ramdisk (32768KB)
okay [0.707s]
writing 'erecovery_ramdisk
FAILED (remote: command not allowed)
Click to expand...
Click to collapse
Is your bootloader still unlocked? There was a guide i posted in v10 section for going back to stock if that's what you are interested.
shashank1320 said:
Is your bootloader still unlocked? There was a guide i posted in v10 section for going back to stock if that's what you are interested.
Click to expand...
Click to collapse
Phone unlocked
FRP unlock
i try to come back to erecovery to install latest Emui 9, and from that point i want to return to AICP14...
@edit: I got it following this post:
https://forum.xda-developers.com/showpost.php?p=78752217&postcount=22
i reached erecovery and i´m installing 9.0.0233 via wifi.... hope it wil run til its completed
The most ****ty problem comes if you want to remove the idiotic encryption via formatting data partition in twrp with the red "yes" ...
Thanks to shashank1320!