Database Info

GEM-702L - Partition Table - internal storage - 32 gig showing as 4 gig

Hello,
I just want to thank anyone in advance for taking their time in reading this and trying to assist.
My situation is that I have a Mediapad x2 702L which when I purchased it, it said it was unlocked.
I go to the recovery screen and it shows unlocked but I couldn't flash anything using adb got an error saying "adb failed (remote: command not allowed)"
so I downloaded dc-unlocker, when I used that I only had the option to FBR. well I did that several times after bricking my device and had to pay $15 each time for a flash to work.
I ended up spending like $90 on this and I was able to get my device unbricked flashed back to GEM 702L B003 stock firmware, that was the only way to get it to work.
from there I was able to get root and I attempted to use several flasher .apks to flash recovery to twrp because it would not work using adb, I would have it installed but then
after the reboot it would lose it. Now at this point My internal SD card is showing it only has 4 gig's of memory when it used to have 32gig's of memory.
if I go to terminal and check partitions I have so many
cat /proc/partitions
I am unable to take a screen shot on my phone to post either
but I was wondering if anybody has ever came across this
or could assist with helping me fix my partition table
Thank you again for all your assistance.

Factory Reset?

I'm unable to do that via dc locker gives me an error now due to the partition being off

USB debugging enabled to use ADB?

Thank you very much guys, I was able to put a copy of android 6.0 on the sd and install a local update then I was able to go back to factory settings and the issue was resolved.
Another thing I noticed is that I keep loosing TWRP?
I had it on there for like 10 minutes and flashed root and two different roms
and then when I tried to boot back into recovery it showed me the stock e-recovery
I had the X2-TWRP-3.0-2-BLACK-BLUE.img flashed for my TWRP.
any idea why I keep loosing it?

You Update Local over Stock Recovery,if you want install Twrp to Android 6.0 use this
https://drive.google.com/file/d/0B5I_q70mNuR4bXJTX3JmdzZZTWs/view?usp=sharing
and flash via fastboot

You can flash TWRP to recovery2 partion as well: For example
fastboot flash recovery2 X2-TWRP-3.0-2-BLACK-BLUE.img
Then keep USB connected when rebooting and holding VOLUME UP key.
This starts TWRP.
If you are not USB connected, the standard recovery will start.
This allows to do factory resets and firmware updates without flashing recovery.img for your version again.
A dload will overwrite the recovery2 partition with the "e-recovery". In this case you will have to flash twrp again.
It's not normal that you have to pay more than once for DC-unlocker booloader It's the same code. Maybe you used the option "Get unlock code"
This is a option for SIM locked phone, but not to unlock bootloader.
"Get bootloader code" is the correct one. You can write down it and use it again and again if neccessary. (I never had to unlock twice)
fastboot oem unlock xxxx does the unlocking. That's all.
I would write do DC-unlocker and ask for return the money.

Huawei honor 6x Bricked? Need help please.

Hello all,
First of all I looked for a (sub) forum for the Honor 6x BLN-L21, but I can't seem to find it. If a admin/mod thinks this post should be placed elsewhere, feel free to move it.
Ok, now on to the problem I'm having with my Honor 6X (BLN-L21 All model)...
The phone is running the stock B361 firmware, I've unlocked the bootloader with the code I got from Huawei, installed TWRP and rooted the phone, all was working just fine.
Then, last Month y (sep 24, 2017) there was an OTA update to B373 available, tried to install it but it failed (nothing was installed btw, it never got to then point where the OTA did anything, phone would just reboot).
So after some searching and in a lapse of judgement I decided to (re)lock the bootloader thinking that was what kept the update from installing (command: sudo fastboot oem relock <code>).
And that's where my problem gets in.
Now I have a phone which only can only get into:
1.) Huawei eRecovery: Only options I have in eRecovery are: "Download latest version and recovery", "Reboot" and "Shutdown". No option to reset to factory or anything like that. "Download latest version and recovery" fails everytime, stating: "Failed to get package info from server". Gave my phone a static DHCP lease and even put it in DMZ on the router (just in case NAT/firewall was interfering), but that didn't help at all. Rebooting or shutdown will just put the phone back into eRecovery as soon as it's booted.
2.) Emergency/EDL: This is the mode where you're supposed to put the firmware you want to flash in the "dload" folder on sd-card. Tried that too, but it gets to about 5% and fails (tried B360, B371 and B373 update files, none work). When the phone gets into this mode it's also available to ADB. However, something seems to have changed dramaticly as I no longer seem to have any permissions on the phone. "adb devices" shows my phone but it also says "unauthorised". As soon as I try to do anything that requires root priviledges (like: "adb root" or "adb shell") I get an error stating: "This adb server's $ADB_VENDOR_KEYS is not set". Clearly that means there's an issue regarding the .pub keys on client/host side not being the same. Since I cannot pull anything from, or push anything to, my phone I don't know how I can fix this... And since I'm getting this message on the same machine that I used to flash TWRP on the phone earlier (which worked just fine), it seems to me this problem exists on the phone-side.
3.) Fastboot & rescue: fastboot finds my phone just fine, yet it flatout refuses all meaningful commands (only basic commands like reboot work) with the error: "FAILED (remote: Command not allowed)". Some searching tells me this is because the bootloader is locked and that's exactly what my phone shows on it's screen when it's in fastboot mode: "PHONE Relocked" and "FRP Lock". However fastboot command: "fastboot oem get-bootinfo" returns: "(bootloader) unlocked". This confuses me, a lot; if the bootloader is unlocked then what is preventing me from flashing anything? Trying to unlock the bootloader again through fastboot (fastboot oem unlock <code> / fastboot oem unlock "<code>") gives the "FAILED (remote: Command not allowed)" error. Trying to lock the bootloader again (fastboot oem relock <code> / fastboot oem relock "<code>") gives error: "FAILED (remote: stat not match)". Obviously I cannot flash anything from fastboot anymore.
Trying to recovery in HiSuite (newest version) doesn't work either, it just tells my my phone isn't supported, even though it does detect my phone when it's in fastboot mode.
Nothing has been flashed, so this is not a case of a flash gone wrong, it just looks like I'm locked out of my own phone and for the life of me I cannot figure out how to get back in. And there's no way to boot into system anymore, so I cannot check/change "OEM Unlock" and "ADB Debugging" settings in the phone developers options
.
Any help/advice would be greatly appreciated! I'm stuck, Huawei customer service only tells me to do a factory reset, which I can't, and when I tell them that's not possible all becomes awfully quiet on their end (they don't respond to my mails anymore). I simply can't think of anything I could try to fix this, spend the last 5 days searching the web but nothing seems to work. Maybe some Android-guru's have some suggestions (I'm certainly open to suggestions! ).
Thanks in advance.
Edit: Tried some fastboot commands with regards to "FRP Unlock", command: "sudo fastboot oem frp-unlock" returns: "FAILED (remote: oem_frp_check_password failed! Error = -1)" not sure what password is required here to be honest and "sudo fastboot oem frp-erase" returns: "FAILED (remote: Command not allowed!)".

This adb server's $ADB_VENDOR_KEYS is not set"- is when your USB debugging is either not enabled or havent accepted the RSA keys. (faced this on ELIte v^)
FRP unlock comamnd wont work as your USB debugging is disabled and hence OEM unlock option is disabled as well.
Manually flashing any .img wont work as FRP is locked.
Only way to restore is dload or service center.

I have the same phone with exactly the same problem ......
any solution ????

aamszia said:
I have the same phone with exactly the same problem ......
any solution ????
Click to expand...
Click to collapse
Are you on stock rom or custom?
What are you trying and what is the result?
Build number?
What all you tried?

shashank1320 said:
Are you on stock rom or custom?
What are you trying and what is the result?
Build number?
What all you tried?
Click to expand...
Click to collapse
Well phone is repaired ( by Sigma KEY Fastboot flashing ) ( Update.app )
B361
First flashed " update_data_full_BLN-L21_hw_meafnaf.zip " by Fastboot
than update.zip ( 1.55 GB ) Dload by SDCARD ....
now its repaired ..

aamszia said:
Well phone is repaired ( by Sigma KEY Fastboot flashing ) ( Update.app )
B361
First flashed " update_data_full_BLN-L21_hw_meafnaf.zip " by Fastboot
than update.zip ( 1.55 GB ) Dload by SDCARD ....
now its repaired ..
Click to expand...
Click to collapse
i want to try this what command you use with the fastboot ? i have a bricked honor 6x andi think its the only thing i have not tried yet please help

i have not use any commands ..
i have used sigma key software .. ( PAID BOX ) ..

well we booted the phone up. we dloaded the firmware BLN-L21C432B360 for the european model. it booted up fine, but now shows nrdm90 teskeys and generic a15. he dloaded the data folder but still its on nrdm 90 test keys. any solution. or try b361 now? @shashank1320

Nithin.15 said:
well we booted the phone up. we dloaded the firmware BLN-L21C432B360 for the european model. it booted up fine, but now shows nrdm90 teskeys and generic a15. he dloaded the data folder but still its on nrdm 90 test keys. any solution. or try b361 now? @shashank1320
Click to expand...
Click to collapse
Ok. Now flash the oeminfo file for BLN-L21 and it will reset the phone with correct formware and device details.

shashank1320 said:
Ok. Now flash the oeminfo file for BLN-L21 and it will reset the phone with correct formware and device details.
Click to expand...
Click to collapse
well oeminfo or the data zip via dload ?

Nithin.15 said:
well oeminfo or the data zip via dload ?
Click to expand...
Click to collapse
Oeminfo via multi tool ir twrp.data file is for regaining the updater app, theme, clock etc but oeminfo will fix your issue of generic device or nrd-test keys.

shashank1320 said:
Oeminfo via multi tool ir twrp.data file is for regaining the updater app, theme, clock multi tool got it.
Click to expand...
Click to collapse

Need help restoring OS/ROM on FRD-L14

I have a Honor 8/FRD-L14 (US model) which I purchased a couple months back. I decided I wanted to root it, so I unlocked the bootloader, installed TWRP (version 3.1.1-1 for FRD-L14) and magisk. To cut to the chase, a lot of my apps didn't work after restoring my backup so I thought I would start over from scratch.
So I had the brilliant idea to wipe all my partitions in TWRP, thinking it would be easy to restore from a blank slate. Nope.
I have obtained a copy of B389 (FRD-L14C567B389b) firmware, both update.zip and update_full_FRD-L14_hw_usa.zip. The first is about 1.3 GB, and the latter is 683 MB..
Here's what I can do:
1. I can unlock and "oem relock" the phone, using TWRP or stock recovery as appropriate.
2. I can boot into Huawei eRecovery, but it always reports "Getting package info failed". It's done this all along.
3. I can boot into TWRP, and attempt to sideload. If I try to sideload the larger "update.zip", it fails immediately. If I try to sideload the smaller "update_full_FRD-L14_hw_usa.zip", it fails at 50%. In both cases the display shows the following:
Code:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Starting ADB sideload feature...
Installing zip file '/sideload/package.zip'
Verifying current userdata...
mountencrypt: failed to mount /data: No such file or directory
Removing unneeded files...
Patching userdata files...
Removing empty directories...
Unpacking data new files...
add link type file...
write radio image...
check_write_data_to_partition,write data error
[COLOR="red"]E:unknown command [errno][/COLOR]
update_huawei_pkg_from_ota_zip: update package from zip failed
[COLOR="Red"]Updater process ended with ERROR: 7[/COLOR]
4. I can "fastboot flash" system SYSTEM.img, boot BOOT.img, cust CUST.img, and recovery RECOVERY.img extracted from the UPDATE.APPs mentioned earlier.
5. HiSuite restore reports that my device is not supported, whether locked or relocked.
6. I have a 128 GB SDXC, and I have attempted to load the two UPDATE.APP files from the aforementioned zip files. Either UPDATE.app, whether placed at root level or in a directory called "dload", gives the same error when trying the 3-button flash function: "Software install failed!", always at 5%.
At no point have I been able to actually boot the OS. If I do not select one of the various recovery modes, the phone never progresses past the unlocked warning message with orange text. (If the phone is locked, it warns that it has "failed verification" with red text, but still won't proceed.)
It really seems like I must simply be doing something wrong here. Apparently I have all the tools I should need available and functional. And yet, I cannot restore the phone to stock firmware.
* Does anyone know what I'm doing wrong? And, does anyone know anything about whether I should be using some particular firmware version for this, and if so which one?
* Is the problem the /data directory? How do I repair/restore that?

marshaul said:
I have a Honor 8/FRD-L14 (US model) which I purchased a couple months back. I decided I wanted to root it, so I unlocked the bootloader, installed TWRP (version 3.1.1-1 for FRD-L14) and magisk. To cut to the chase, a lot of my apps didn't work after restoring my backup so I thought I would start over from scratch.
So I had the brilliant idea to wipe all my partitions in TWRP, thinking it would be easy to restore from a blank slate. Nope.
I have obtained a copy of B389 (FRD-L14C567B389b) firmware, both update.zip and update_full_FRD-L14_hw_usa.zip. The first is about 1.3 GB, and the latter is 683 MB..
Here's what I can do:
1. I can unlock and "oem relock" the phone, using TWRP or stock recovery as appropriate.
2. I can boot into Huawei eRecovery, but it always reports "Getting package info failed". It's done this all along.
3. I can boot into TWRP, and attempt to sideload. If I try to sideload the larger "update.zip", it fails immediately. If I try to sideload the smaller "update_full_FRD-L14_hw_usa.zip", it fails at 50%. In both cases the display shows the following:
4. I can "fastboot flash" system SYSTEM.img, boot BOOT.img, cust CUST.img, and recovery RECOVERY.img extracted from the UPDATE.APPs mentioned earlier.
5. HiSuite restore reports that my device is not supported, whether locked or relocked.
6. I have a 128 GB SDXC, and I have attempted to load the two UPDATE.APP files from the aforementioned zip files. Either UPDATE.app, whether placed at root level or in a directory called "dload", gives the same error when trying the 3-button flash function: "Software install failed!", always at 5%.
At no point have I been able to actually boot the OS. If I do not select one of the various recovery modes, the phone never progresses past the unlocked warning message with orange text. (If the phone is locked, it warns that it has "failed verification" with red text, but still won't proceed.)
It really seems like I must simply be doing something wrong here. Apparently I have all the tools I should need available and functional. And yet, I cannot restore the phone to stock firmware.
* Does anyone know what I'm doing wrong? And, does anyone know anything about whether I should be using some particular firmware version for this, and if so which one?
* Is the problem the /data directory? How do I repair/restore that?
Click to expand...
Click to collapse
I had written this guide a long time back. It didn't recieve any attention but holds true for your device. If you restore by rollback you can relock the bootloader with the "LOCKED" status rather than the "RELOCKED" which means your warranty won't be void.
Here's the guide:
https://forum.xda-developers.com/honor-8/how-to/restoring-relocking-bricked-frd-l04-t3666360
The only difference is download the rollback packages from this thread:
https://forum.xda-developers.com/ho...users-how-to-restore-downgrade-t3537433/page1
Sent from my Honor 8 using XDA Labs

Thanks for the response.
Is there any reason I should rollback to the version you discuss?
I looked at the backup I made before unlocking, and it was FRD-L14C567B391. So I downloaded this and have been attempting to use it.
Flashing the recovery.img and attempting to 3-button install UPDATE.app doesn't work. It does the same thing it's done all along: immediately stops at 5%.
If I attempt to sideload this I do get a new error (I'll share it when I get home).
BTW, is every android phone so fussy about this stuff? I will never consider this platform again after how unwilling it seems to do basic restore procedures -- not sure if that's just Huawei or all androids. Either way there's really no excuse -- just flash the damn software and try to run it.

marshaul said:
Thanks for the response.
Is there any reason I should rollback to the version you discuss?
I looked at the backup I made before unlocking, and it was FRD-L14C567B391. So I downloaded this and have been attempting to use it.
Flashing the recovery.img and attempting to 3-button install UPDATE.app doesn't work. It does the same thing it's done all along: immediately stops at 5%.
If I attempt to sideload this I do get a new error (I'll share it when I get home).
BTW, is every android phone so fussy about this stuff? I will never consider this platform again after how unwilling it seems to do basic restore procedures -- not sure if that's just Huawei or all androids. Either way there's really no excuse -- just flash the damn software and try to run it.
Click to expand...
Click to collapse
Nope this is only on Huawei phones. The reason I recommend the rollback process is because it helps you restore your phone to the state you bought it (Including a "LOCKED" not "RELOCKED" bootloader). A TWRP flash will get you on the stock ROM but future OTAs might be a pain and safetynet will not pass without Magisk. Using this method you will be on the right recovery and latest firmware with everything official. Also if you have warranty this method restores it.
On phones from Google, Samsung, etc restoring is insanely simple. Huawei doesn't encourage third party development.
Sent from my Honor 8 using XDA Labs

[SOLVED] Please help! Bricked my Huawei NXT-L29C432B582 running on Android 8.0

Update:
I've got my phone back thanks to this post! https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
--------------------------------------[/B]-----------------------------------------------------------------------------------------------------------------------------------------------
I successfully upgraded my NXT-L29 to Oreo, using the files in this post: https://forum.xda-developers.com/mate-8/general/discussion-oreo-huawei-mate-8-t3785320
(Only difference: used another TWRP version - twrp-3.1.1-1-next.img - since the one in this post didn’t work).
Though my phone worked, it was unrooted again and I tried to solve it by flashing TWRP again. It didn’t work, so I tried flashing TWRP-3.1.0-EMUI-5.0.img. Here’s where everything went wrong.
I get:
ERROR MODE, Please update system again!"
Error! Func: NO: 11 (recovery image)
Error NO: 2 (load failed!)
Here’s what I still can do:
- Get into Fastboot – Bootloader and FRP both Unlocked
- Use ADB
- Get into eRovery
- Get into EMUI update
- Flash TWRP, SYSTEM.img and BOOT.img
What I can’t do:
- Access my phone – get or one of the two yellow messages or Error Mode or Fastboot
- Connect to HiSuite
- Acces Wipe Partion, Factory Settings
- Boot into TWRP
- Flash any Recovery (partition: (length) error, or Cannot load Recovery). No matter what command I try. Fastboot flash recovery_ramdisk RECOVERY.img doesn’t work either.
- Find a RAMDISK.img in the Update.app. Flashing the SYSTEM, CUST and BOOT.img won’t do the trick with rebooting volume up + volume down + power. EMUI update states: Software install failed!
- Use eRovery. Recovery fails every time after 7%
- Find the current Build Number, since there’s no way of getting passed the two yellow messages or Error Mode or Fastboot
I’ve been up till 5 in the morning, trying to solve this without success. Think I’ve tried a 100 commands and methods. Is there anyone who has a solution? I’m really desperate by now.

HQuinn said:
I successfully upgraded my NXT-L29 to Oreo, using the files in this post: https://forum.xda-developers.com/mate-8/general/discussion-oreo-huawei-mate-8-t3785320
(Only difference: used another TWRP version - twrp-3.1.1-1-next.img - since the one in this post didn’t work).
Though my phone worked, it was unrooted again and I tried to solve it by flashing TWRP again. It didn’t work, so I tried flashing TWRP-3.1.0-EMUI-5.0.img. Here’s where everything went wrong.
I get:
ERROR MODE, Please update system again!"
Error! Func: NO: 11 (recovery image)
Error NO: 2 (load failed!)
Here’s what I still can do:
- Get into Fastboot – Bootloader and FRP both Unlocked
- Use ADB
- Get into eRovery
- Get into EMUI update
- Flash TWRP, SYSTEM.img and BOOT.img
What I can’t do:
- Access my phone – get or one of the two yellow messages or Error Mode or Fastboot
- Connect to HiSuite
- Acces Wipe Partion, Factory Settings
- Boot into TWRP
- Flash any Recovery (partition: (length) error, or Cannot load Recovery). No matter what command I try. Fastboot flash recovery_ramdisk RECOVERY.img doesn’t work either.
- Find a RAMDISK.img in the Update.app. Flashing the SYSTEM, CUST and BOOT.img won’t do the trick with rebooting volume up + volume down + power. EMUI update states: Software install failed!
- Use eRovery. Recovery fails every time after 7%
- Find the current Build Number, since there’s no way of getting passed the two yellow messages or Error Mode or Fastboot
I’ve been up till 5 in the morning, trying to solve this without success. Think I’ve tried a 100 commands and methods. Is there anyone who has a solution? I’m really desperate by now.
Click to expand...
Click to collapse
Hi.
According to your post, you flashed TWRP-3.1.0-EMUI-5.0.img then got the problems .
Did you try to flash stock recovery by adb?
You can find it in original ROM files

afromoh said:
Hi.
According to your post, you flashed TWRP-3.1.0-EMUI-5.0.img then got the problems .
Did you try to flash stock recovery by adb?
You can find it in original ROM files
Click to expand...
Click to collapse
Yes, I've tried that about a million times. Everything worked, except flashing the (stock) recovery.
I'm really sorry for my late reply. I've been very ill. Luckily the problem is solved and I've got my phone back. Thanks to Georgian51 who suggested this post: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279.
That did the trick! Thanks for your reply

Help unbricking Honor 6x L-24

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