Related
Hello community
I think i bricked my P8 MAX.
What i did, rooted the phone with Kingroot, altered the Dualwindow file.
Three days ago i tried to install B209 and now it won´t boot up.
I always stay at the animated Huawei Logo.
erecovery is not able to load a Firmware and when i try to do something in Fastbbot, i always get remote command not allowed. In Fastboot it says PHONE Unlocked....
Any suggestions?
audiaudi said:
Hello community
I think i bricked my P8 MAX.
What i did, rooted the phone with Kingroot, altered the Dualwindow file.
Three days ago i tried to install B209 and now it won´t boot up.
I always stay at the animated Huawei Logo.
erecovery is not able to load a Firmware and when i try to do something in Fastbbot, i always get remote command not allowed. In Fastboot it says PHONE Unlocked....
Any suggestions?
Click to expand...
Click to collapse
Which Rom where installed before you updated to B209?
Hirs_E_Fruit said:
Which Rom where installed before you updated to B209?
Click to expand...
Click to collapse
B029
audiaudi said:
B029
Click to expand...
Click to collapse
Stock B029 with Stock Recovery?
OTA Update from B029 to B209?
Stock b029 with stock recovery
Rooted
B209 update through dload folder
I downloaded the b209 form kangvip thread, but the regular one.
audiaudi said:
Stock b029 with stock recovery
Rooted
B209 update through dload folder
I downloaded the b209 form kangvip thread, but the regular one.
Click to expand...
Click to collapse
You never got your Phon to start full into OS after update?
Nope
Does anybody know, why i always get remote command not allowed when using fastboot?
audiaudi said:
Does anybody know, why i always get remote command not allowed when using fastboot?
Click to expand...
Click to collapse
hey you only need flash these files from update.app
boot
cust
recovery
cache
system
reboot and when Android is finish booting copy the update.app to /dload in internal storage and reset factory... then... upgrade from internal storage... BACKUP you NVRAM contents but no lost IMEI how is my case
I can't....
fastboot flash boot boot.img
I get: remote command not allowed
do you have the BOOTLOADER UNLOCK ?..
fastboot oem unlock CODE
??
audiaudi said:
I can't....
fastboot flash boot boot.img
I get: remote command not allowed
Click to expand...
Click to collapse
On the screen it shows phone unlocked but i don't know if it's true cause I didn't unlock so it must have been unlocked before.
And i can't get an umlock code through the Huawei site cause i haven't the huawei id on the phone long enough and know, obviously i can't....
audiaudi said:
On the screen it shows phone unlocked but i don't know if it's true cause I didn't unlock so it must have been unlocked before.
And i can't get an umlock code through the Huawei site cause i haven't the huawei id on the phone long enough and know, obviously i can't....
Click to expand...
Click to collapse
I unlock bootloader with a paid tool..( dont say the name this tool... ), cost to 5 dlls USA
audiaudi said:
Hello community
I think i bricked my P8 MAX.
What i did, rooted the phone with Kingroot, altered the Dualwindow file.
Three days ago i tried to install B209 and now it won´t boot up.
I always stay at the animated Huawei Logo.
erecovery is not able to load a Firmware and when i try to do something in Fastbbot, i always get remote command not allowed. In Fastboot it says PHONE Unlocked....
Any suggestions?
Click to expand...
Click to collapse
Try this version of fastboot...
https://drive.google.com/folderview?id=0B5I_q70mNuR4bWp5Wl9LOGdFQnc
ajsmsg78 said:
Try this version of fastboot...
https://drive.google.com/folderview?id=0B5I_q70mNuR4bWp5Wl9LOGdFQnc
Click to expand...
Click to collapse
The same...
C:\test>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (23406 KB)...
OKAY [ 0.511s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.529s
you extract the img files with a profile ??? I use the unknow... other... and mmmm you probe the names of file and partition are diferent ?
fastboot flash boot BOOT.IMG ...(name of file exactly )
same problem in here...
someone can help us?
FAILED (remote: Command not allowed)
same problem here.. please help us
Huawei P8 Max DAV703 Android 6.0 EMUI 4.0 64 GB chinese variant trying to convert to EU
Well I hope that it isn't completely FUBAR.. I know there has to be a way, but i forget how.
No fastboot, no adb support.. no recovery, no bootloader.. fastboot was only available through software.
I have hard reset which has reset it to bootloop, and I have system upgrade that whatever I do, crashes at 5%
Basically, I bricked my Huawei.
I partially rooted it with kingoroot without doing anything..
but other apps saw it as unrooted so i was going to do the proper way, unlock bootloader, etc..
Then I discovered the Huawei SRK tool for bootloader/kernel/recovery etc.
Checked if my bootloader was unlocked, it was..
restarted the phone, it was fine
Then I was going to flash the recovery, and that's when it went into a bootloop
Like always.. just the logo shows, and if i try to turn it off, it restarts.
Huawei P8 Max DAV703 Android 6.0 EMUI 4.0
hard reset works - pressiing vol up down and power pushes it into hard reset but it stays in bootloop.
usb in, vol down power - puts into update mode which stops at 5% with error.
My next idea would be to try and extract the necessary files and try to use the Huawei update extractor tool
but after trying many update files, I can't find the one that would work, unless it will just keep crashing at 5% always.
Would anyone know what I could do in this situation?
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.
After updating TWRP using TWRP it self i can't boot into custom recovery again the phone just stays loading forever, the phone is also wiped so no custom image or stock image and i cant use it since even in fastboot it just keeps saying "FAILED (remote: Command not allowed)".
The phone on FASTBOOT mode says:
Phone unlocked
but says FRP lock
maybe that is the problem? if so how can i solve it? i really want to make my honor 8 work again so thanks for your help!
Ps. Sorry for my bad English
RicardoVs said:
After updating TWRP using TWRP it self i can't boot into custom recovery again the phone just stays loading forever, the phone is also wiped so no custom image or stock image and i cant use it since even in fastboot it just keeps saying "FAILED (remote: Command not allowed)".
The phone on FASTBOOT mode says:
Phone unlocked
but says FRP lock
maybe that is the problem? if so how can i solve it? i really want to make my honor 8 work again so thanks for your help!
Ps. Sorry for my bad English
Click to expand...
Click to collapse
What android version are you on? Have you tried flashing stock recovery? Which twrp are you using? Are sure that you did not flash twrp on the wrong partition?
PremiumBlaze said:
What android version are you on? Have you tried flashing stock recovery? Which twrp are you using? Are sure that you did not flash twrp on the wrong partition?
Click to expand...
Click to collapse
I was using Paranoid android 7.1 i believe but i wiped the phone so there is no Android at all at the moment, i tried updating to the latest twrp since i was getting error 7 trying to flash the stock room, stock recovery just says "failed to get information from the server" every time and for last i did flash it in the right partition, every comand i execute in fastboot it gives me that error and it's also important to mention that i can't find my phone in "adb devices" only in "fastboot devices". I saw some people using the Dload get the stock system back maybe thats an option? i dont know i feel completely lost.
Thanks for the reply
RicardoVs said:
I was using Paranoid android 7.1 i believe but i wiped the phone so there is no Android at all at the moment, i tried updating to the latest twrp since i was getting error 7 trying to flash the stock room, stock recovery just says "failed to get information from the server" every time and for last i did flash it in the right partition, every comand i execute in fastboot it gives me that error and it's also important to mention that i can't find my phone in "adb devices" only in "fastboot devices". I saw some people using the Dload get the stock system back maybe thats an option? i dont know i feel completely lost.
Thanks for the reply
Click to expand...
Click to collapse
Are you able to boot inside TWRP at this moment? And also what is this "latest twrp" that you said that your were flashing. I believe if the TWRP stays loading forever, it means that it does not work for the device.
Make sure your trying to flash this TWRP for nougat:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563/amp/
PremiumBlaze said:
Are you able to boot inside TWRP at this moment? And also what is this "latest twrp" that you said that your were flashing. I believe if the TWRP stays loading forever, it means that it does not work for the device.
Make sure your trying to flash this TWRP for nougat:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563/amp/
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-1-frd.img
target reported max download size of 471859200 bytes
sending 'recovery' (25188 KB)...
OKAY [ 0.538s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.546s
RicardoVs said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-1-frd.img
target reported max download size of 471859200 bytes
sending 'recovery' (25188 KB)...
OKAY [ 0.538s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.546s
Click to expand...
Click to collapse
Have you tried dload yet?
PremiumBlaze said:
Have you tried dload yet?
Click to expand...
Click to collapse
No, what do I need to do? What files should I put in the Dload folder? I never used that method and didn't manage to find information online
RicardoVs said:
No, what do I need to do? What files should I put in the Dload folder? I never used that method and didn't manage to find information online
Click to expand...
Click to collapse
1. Download the update.zip of the stock rom
2. Extract the update.zip of the stock rom
3. Make a folder named "dload" on your sdcard
4. Place the UPDATE.APP on the dload folder
5. Press volume up + volume down + power button until Huawei logo appears
PremiumBlaze said:
1. Download the update.zip of the stock rom
2. Extract the update.zip of the stock rom
3. Make a folder named "dload" on your sdcard
4. Place the UPDATE.APP on the dload folder
5. Press volume up + volume down + power button until Huawei logo appears
Click to expand...
Click to collapse
Ok, i already had the files so i did everything and it didnt work "Software install failed!"
RicardoVs said:
Ok, i already had the files so i did everything and it didnt work "Software install failed!"
Click to expand...
Click to collapse
In the old nougat days, Ive had the same problem. As I always say, dont use twrp on honor 8. They all suck! Anyways, did you tried eRecovery?
Or you should be able to dload a proper firmware in all cases. You just need to find the right package. It fixed me the same problem in the past.
Braiteyy said:
In the old nougat days, Ive had the same problem. As I always say, dont use twrp on honor 8. They all suck! Anyways, did you tried eRecovery?
Or you should be able to dload a proper firmware in all cases. You just need to find the right package. It fixed me the same problem in the past.
Click to expand...
Click to collapse
I got the update.zip for my specific FRD device but still... it failed... im starting to think there is no way so fix this
RicardoVs said:
I got the update.zip for my specific FRD device but still... it failed... im starting to think there is no way so fix this
Click to expand...
Click to collapse
Dont loose hope man! There is a way to fix it every time. Just try another full ota package with same vendor as you are running rn.
Braiteyy said:
Dont loose hope man! There is a way to fix it every time. Just try another full ota package with same vendor as you are running rn.
Click to expand...
Click to collapse
I tried every single file for my FRD-L09C432B405 on Team mt and nothing :/
Do i need to delete everything on the sd card and leave only de dload folder? Maybe i need to format it in an specific format?
No, you dont need to format your sd card. I am gonna help you tomorrow. I am going to sleep rn. See you! need to format it in an specific format?[/QUOTE]
RicardoVs said:
I tried every single file for my FRD-L09C432B405 on Team mt and nothing :/
Do i need to delete everything on the sd card and leave only de dload folder? Maybe i need to format it in an specific format?
Click to expand...
Click to collapse
I realised you said that you updated your TWRP and you cant get in. Did you tried different buttons? I remember some of twrps had volume up + power button and some had volume down and power button and some had vol up and down and power button. Try everything. The frp lock is probably because it somehow disabled oem unlocking by itself. I am gonna try to find a link for latest nougat for you. Good luck man!
EDIT: You should try to relock yor bootloader and unlock it again.
Here are the links: http://update.dbankcdn.com/TDS/data/files/p3/s15/G1774/g1755/v208402/f1/full/update.zip
http://update.dbankcdn.com/TDS/data...l/FRD-L09_hw_eu/update_full_FRD-L09_hw_eu.zip
http://update.dbankcdn.com/TDS/data...02/f1/full/public/update_data_full_public.zip
RicardoVs said:
I tried every single file for my FRD-L09C432B405 on Team mt and nothing :/
Do i need to delete everything on the sd card and leave only de dload folder? Maybe i need to format it in an specific format?
Click to expand...
Click to collapse
Could you try to follow this guide to see if it works:
https://www.stechguide.com/downgrade-honor-8-from-nougat-to-marshmallow/
It may lead your to marshmallow but hopefully it makes the device works. You are going to need the B131 update.zip and flashing rollback package (the site has rollback package download) using dload first before flashing the B131's update.app using dload.
So basically:
1. Flash the rollback package's update.app using dload
2. Flash update.app from B131's update.zip using dload
Once your in marshmallow, you can go back to nougat because there should be at least a twrp for honor 8 marshmallow somewhere around xda
PremiumBlaze said:
Could you try to follow this guide to see if it works:
https://www.stechguide.com/downgrade-honor-8-from-nougat-to-marshmallow/
It may lead your to marshmallow but hopefully it makes the device works. You are going to need the B131 update.zip and flashing rollback package (the site has rollback package download) using dload first before flashing the B131's update.app using dload.
I am really sure that this would work because I tried it before and I was able to go to Marshmallow without any software install fails using dload.
So basically:
1. Flash the rollback package's update.app using dload
2. Flash update.app from B131's update.zip using dload
Once your in marshmallow, you can go back to nougat because there should be at least a twrp for honor 8 marshmallow somewhere around xda
Click to expand...
Click to collapse
The rollback package worked but not the B131, i tried to flash the update.app for my android the B405 as well but nothing...
RicardoVs said:
The rollback package worked but not the B131, i tried to flash the update.app for my android the B405 as well but nothing...
Click to expand...
Click to collapse
I thought this is gonna happen. It happened to me too. I just dont ****in remmember how did I make dload work.
delete
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
hey i can help ! which version of twrp are you trying to flash ?
lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Venkata Lochan Nune said:
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Click to expand...
Click to collapse
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
My bad , I thought the update website to be huawei's official one(something like update.hicloud and all isn't it?). Well, thanks for the information but I still prefer gsi. It's buttery smooth .
And one more thing, if you follow the youtube video I mentioned, you don't need any gsi. You can get your device back on stock EMUI 5.
King_of_Android said:
hey i can help ! which version of twrp are you trying to flash ?
Click to expand...
Click to collapse
Hey I have a doubt... Will the recoveries we find in twrp official website / app work on EMUI 8? I wanted to try them but I'm afraid I might brick my device again. Getting it back is a hectic thing and I already had to face it thrice. LOL .
King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
lmaohelp said:
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
Click to expand...
Click to collapse
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Venkata Lochan Nune said:
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Click to expand...
Click to collapse
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
lmaohelp said:
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
Click to expand...
Click to collapse
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Venkata Lochan Nune said:
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Click to expand...
Click to collapse
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
lmaohelp said:
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
Click to expand...
Click to collapse
I'm attaching one that works with emui 8 try using it (Remember you have to flash it to recovery_ramdisk).
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
speedson said:
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
Click to expand...
Click to collapse
His problem us with twrp.
He can only access fastboot but isn't able to flash twrp...
Venkata Lochan Nune said:
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
Click to expand...
Click to collapse
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
lmaohelp said:
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
Click to expand...
Click to collapse
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Venkata Lochan Nune said:
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Yup, I tried that as well, and it told me "invalid command"
lmaohelp said:
Yup, I tried that as well, and it told me "invalid command"
Click to expand...
Click to collapse
Well as you said, you partitions must have been really messed up. I have no other ideas except the test point method.
Are you trying anything else?
Ok we have some option that could help you...
Im read in the 4PDA (the russian XDA xD) forum that it should be possible to flash the oeminfo by fastboot command. So just download the HWOTA_BLN_Eng and expand it. Then go to 7 or 8 Folder and there you go to oeminfo folder. There you choose the right one for your Device and local area...for example BLN-L21 (Device) C432 (European Area)
Extract the file to your desktop and rename it to BLN-L21C432.img
--->be sure that you have the right Device driver installed and the right ADB driver for your device to<---
ok now Copy and Paste the BLN-L21C432.img to ADB folder and start command with admin rights
start the phone into fastboot mode
--->bootloader must be unlocked<---
in the command
fastboot flash oeminfo BLN-L21C432.img
wait for the result and it can not hurt to pray a bit in this moment...hihi
if this have success...you type in command
fastboot reboot
wait to the screen you can press 3 seconds Vol+ to go into erecovery....connect to wlan and it should work step by step like it should.
after download and recover the stock rom reboot and go again to erecover by press Vol+ for 3 seconds and now go to the second option...wipe data/factory reset and write yes+enter
in stock recovery wipe Data after that wipe Cache...reboot and wait that system boot the initial boot for first setup.
If this will not working...tell me what honor 6x you have and wich local area you are from and wich firmware you stock had before you doing wronng
good luck bro
solong
speedson