Database Develop

Unbrick BIOS-Softbrick on X98 Air m5c5 withouth EEPROM Flasher - courtesy of ionioni

Good evening gents,
Since I broke my BIOS on my m5c5 by flashing the wrong one with Tecknights Tutorial, I was desperately trying to get back to the working BIOS.
Thanks to ionioni we have a way to unbrick our devices (as long as they still boot into dnx).
I accidentally flashed the wrong BIOS on to my X98 Air iii (m5c5) and thought i bricked it beyond repair (except opening it up and flashing it with EEPROM Clip).
Now we have a solution to flash the DUAL BOOT - BIOS to the m5c5 through dnx mode:
WARNING: EVERYTHING YOU DO, YOU DO AT YOUR OWN RISK! Only tested on m5c5! Using it on other devices can HARDBRICK!!!
IMPORTANT: DO NOT CUT THE USB OR POWER AND WATCH OUT THAT THERE IS ENOUGH POWER IN THE ACCU.
1. Copy the following files into your fastboot directory on your pc:
https://anonfiles.com/file/28e5e4990eee25d74ff4d6cc99fdb548
2. Boot the device into dnx/fastboot (pressing power and Vol+/Vol- at the same time)
3. Plug the device in via usb, open up a command prompt in your fastboot directory and type the following:
fastboot devices #Check if device is recognized
fastboot flash osloader efilinux.efi #Push Efiloader onto device
fastboot boot bios_restore_m5c5.img #restores the dual boot bios
4. Wait for reboot. There is now a 100 second timer in case of second guesses and afterwards update notifications during the flash. It takes between 3-5 Minutes. DO NOT FORCE REBOOT it WILL HARDBRICK
Be happy to have unbricked your BIOS. And thank ionioni !! PM him if you have any questions!

Fastboot boot --> that instruction not flashing anyting only booting partition to ram .
What is doing that img ? I'm curious .

mirek190 said:
Fastboot boot --> that instruction not flashing anyting only booting partition to ram .
What is doing that img ? I'm curious .
Click to expand...
Click to collapse
it flashes the bios @mirco446 gave me (also asked him and sent me the droidboot.img from the stock)
i used the droidboot.img sent as a base and modified it (included in it the bios sent together with the intel FPT binary for writing a bios file) and it just boots and runs when boot is completed the binary to flash the bios file (this is why one should NOT reset or power off the device after it enters the fastboot boot command as this could result in a partially written bios and this translates to HARD-BRICK). at the end it reboots to load the new bios
normally should also output some messages but for some reason it doesnt capture the framebuffer device and since i don't own the device i cannot 'debug' to check on why... but this is only a minor issue (not having status messages), so one just needs to wait a few minutes until the device reboots confirming that the bios was wrote.
nothing fancy

Interesting ... thanks for explanation .

And he did it for C5J8 too, mine is alive too.

hello i have the same problem with my m5c5 but it don't work for me.
i have this message:
entering dnx mode.
waiting for fastboot command.... efilinux [ 0.000449] ERROR[get_parth:334] couldn't find boot device handle.

Good drivers?

i use driver from TecKnight's Teclast Tutorials series.
i try under linux and same problem.
[email protected] ~/Téléchargements $ sudo fastboot devices
Baytrail02D31E57 fastboot
[email protected] ~/Téléchargements $ sudo fastboot flash osloader efilinux.efi
sending 'osloader' (2463 KB)...
OKAY [ 0.109s]
writing 'osloader'...
OKAY [ 0.008s]
finished. total time: 0.117s
[email protected] ~/Téléchargements $ sudo fastboot boot restore_bios_m5c5.img
downloading 'boot.img'...
OKAY [ 0.791s]
booting...
OKAY [ 0.003s]
finished. total time: 0.794s
tablet wait ~30s and restart on red logo and bootloop.
i upload my original bios but not dual boot:
https://drive.google.com/open?id=0B_A8FEPnUL61WHQ4RzAxOXpzZGM
edit: problem solved for me thank you ionioni!!!!!

bosondehiggs said:
i upload my original bios but not dual boot:
https://drive.google.com/open?id=0B_A8FEPnUL61WHQ4RzAxOXpzZGM
Click to expand...
Click to collapse
i won't invest anymore time in this. already tried this below stuff... not working
seems that it doesn't boot the image at all, this could be due to an existing IA32 bios (post a link to the bios you flashed so i can check)
until then...
you can try again and skip the first 'fastboot flash osloader efilinux.efi' if it still doesn't work replace the efilinux.efi file with one from a x86 older rom
no matter what wait until the tab reboots by itself after you enter the 'fastboot boot' command(~30-40 seconds if it cannot boot, at most 5 minutes if it does, in this case it will also flash your bios)

ionioni said:
i cannot access the share you posted (make it public)
seems that it doesn't boot the image at all, this could be due to an existing IA32 bios (post a link to the bios you flashed so i can check)
until then...
you can try again and skip the first 'fastboot flash osloader efilinux.efi' if it still doesn't work replace the efilinux.efi file with one from a x86 older rom
no matter what wait until the tab reboots by itself after you enter the 'fastboot boot' command(~30-40 seconds if it cannot boot, at most 5 minutes if it does, in this case it will also flash your bios)
Click to expand...
Click to collapse
Hi, can you make one for c6j7?

Hi,
I have exact same problem as bosondehiggs. "couldn't find boot device handle." when I try to flash the restore bios.img. I used the file with the link at top of thread.
Any idea?
Thanks for your help

Hi,
the same problem to me on my Teclast Air III !!
I hope anyone who solved the problem can help us ...
Thx a lot
Alex

Try my idea, maybe help you: http://forum.xda-developers.com/showpost.php?p=64725703&postcount=26

Hi,
thank you Blackbile. Now its working... :good:
Alex

those who cannot restore, see here http://forum.xda-developers.com/showpost.php?p=64736792&postcount=36

acnic said:
Hi,
thank you Blackbile. Now its working... :good:
Alex
Click to expand...
Click to collapse
But what was the solution?????

I booted into BIOS and did what you have written and press restore defaults. Then i flashed again the efilinux and the restore bios. I had the same error and no reboot from the tablet! After waiting 10 minutes i decided to press the Power Button and bling there it is...
Now i have dual boot, but only Mireks Rom installed.
The next days i will try to install Windows, too.
I hope there are no problems again.
Thx for your help...
Alex

I flashed my M5C6 softbricked with the BIOS for C5J8 (2.05c) from the other post and it works now my tablet. The only problem I had me too is that the system doesn't reboot automatically after flashing process like @acnic so after 7 minutes I rebooted manually (with all my fingers crossed), finally the tablet has started like usual (I did the restore default settings into BIOS).
Now the only "problem" I had is that when I shutdown the system from Android or W10, I can't restart with power button so I need to press 10s before to can start the system again, Someone have an idea of this behaviour?
Many thanks again for your incredible work and support!!
Santi
Enviado desde mi SM-G900FD

Gitantos: http://forum.xda-developers.com/x98-air/help/x98-air-3g-doest-power-t3287417
*****************
How did you bricked?
While the restoring happened, did you see messages on the screen as I posted in my thread?

blackbile said:
Gitantos: http://forum.xda-developers.com/x98-air/help/x98-air-3g-doest-power-t3287417
*****************
How did you bricked?
While the restoring happened, did you see messages on the screen as I posted in my thread?
Click to expand...
Click to collapse
Hello blackbile, I bricked using the flashing method from Techknight's. I have unbricked with your guide (BIOS from C5J8)
Enviado desde mi SM-G900FD

[Q] Bricked Zuk Z2 Pro (Z2121)

Hello everyone,
I bricked my Z2 Pro and after hours of searching and trying to fix it by flashing stock ROM via EDL I'm desperate so I would be grateful for any help.
My Z2 came with some custom ROM from shop with 1.9 version on it without OTA so I decided to flash it with different ROM. I unlocked the bootloader, flashed TWRP and SU, but flashing Gedeon ROM via TWRP ended with an error (error code 7 or 11 if I remember correctly). So I decided to flash stock ROM following
this guide.
QFIL recognized the device correctly as Qualcomm HS-USB QDLoader 9008, but I kept receiving this error:
02:20:14: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
02:20:14: ERROR: function: sahara_main:854 Sahara protocol error
02:20:14: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
So I followed this guide that recommends to use MiFlash instead of QFIL.
After few unsuccessful updates (it wasn't able to open the port) it finally finished downloading the ROM (2.0.057 ST) with this message at the end: The operation completed successfully.(0x00000000: ApplyPatch sector NUM_DISK_SECTORS-1., offset 16, value CRC32(NUM_DISK_SECTORS-1.,92), size 4)
It took about 55s.
However after I unplugged Z2 from the USB cable and hit the power button, nothing happened. Since the update the screen is off, the LED light is off. Even if I hold the power off button for one minute.
When I plugged the phone back, it was still recognized as QDloader 9008, so it is apparently stuck in the EDL mode.
I tried all stock ROMs from here multiple times with the same result. Multiple times with the "successful update" message, but nothing happens.
EDIT: Now, after few tries the of the same process it is not even updating the ROM at all. It says "Open serial port failed" and afterwards "Missing hello packet, try to recover" (I waited about 5 min, but the message didn't change).
Please help
I hope for a solution without the need to unplug the battery, but if it will be necessary, I will do it.
Thank you!

Creshaw said:
Hello everyone,
I bricked my Z2 Pro and after hours of searching and trying to fix it by flashing stock ROM via EDL I'm desperate so I would be grateful for any help.
My Z2 came with some custom ROM from shop with 1.9 version on it without OTA so I decided to flash it with different ROM. I unlocked the bootloader, flashed TWRP and SU, but flashing Gedeon ROM via TWRP ended with an error (error code 7 or 11 if I remember correctly). So I decided to flash stock ROM following
this guide.
After few unsuccessful updates (although it recognized the device correctly as Qualcomm HS-USB QDLoader 9008, it wasn't able to access it via the relevant port) it finally updated the ROM (2.0.057 ST) with successful message at the end (the flash itself took about 55s). However after I unplugged Z2 from the USB cable and hit the power button, nothing happened. The screen is off, the LED light is off. Even if I hold the power off button for one minute.
When I plugged the phone back, it was still recognized as QDloader 9008, so it is apparently stuck in the EDL mode.
I tried all stock ROMs from here multiple times with the same result. Still successful update, but nothing happens.
Please help
I hope for a solution without the need to unplug the battery, but if it will be necessary, I would do it.
Thank you!
Click to expand...
Click to collapse
Can you verify if you followed step 1.1.2.
1.1.2 If you opend QFIL swich to the FireHoseConfiguration and enter the following settings:

syedtahir16 said:
Can you verify if you followed step 1.1.2.
1.1.2 If you opend QFIL swich to the FireHoseConfiguration and enter the following settings:
Click to expand...
Click to collapse
Yes, everything step by step. I even have the same version of QFIL (QPST is build 437 instead of suggested 434 - I suppose that won't be causing any problem). I tried to reboot my PC, different USB ports, reinstall drivers (as I previously had Lenovo USB driver and before the flash I installed the ZUK driver as well as without the ZUK drivers it wasn't recognized as QDLoader).

Zukfans.eu
Btw I'm unable to sign up to zukfans.eu to place my question there as well as. It asks for CAPTCHA verification, however there is no CAPTCHA shown, only the verification question "what zuk have you ?". I filled in there 'ZUK Z2 Pro', copied the question in there etc., used 4 different broswers on 2 devices and networks, no luck. And it is not possible to log in via FB as well.

I was working on it until 4AM last night and today I completely forgot to describe the important part about MiFlash
Please see in the original post.
Thanks for your your reply!

Creshaw said:
I was working on it until 4AM last night and today I completely forgot to describe the important part about MiFlash
Please see in the original post.
Thanks for your your reply!
Click to expand...
Click to collapse
I'm not sure about Miflash. I used QFIL.
Also, I wrote a small tutorial. See if that helps:
http://zukfans.eu/community/threads...rom-zuk-z2-pro-z2121-only.57/page-8#post-7282
If you are unable to use that link. Below is an extract:
"The QFIL zip contained the ROM twice. so you can load the contents.xml from the parent folder or the other folder within the zip too.
Make sure you extract the ROM in a short part i.e. "C:\Z2Pro\
1) Firstly, the tricky part having the tool recognize the qualcomm port.
Solution: Uninstall the tool, USB drivers (i.e. Zuk drivers), any existing qualcomm drivers.
Reboot.
Install Zuk drivers.
Install the tool. (According to the guide, the tool will also install the drivers for qualcomm, but for some reason it did not)
Install the qualcomm drivers.
2) Fortunately, my phone was not bricked. So I could easily get into edl mode using "adb reboot edl"
3) While trying to get this to work, some RELINK driver was installed instead of qualcomm. Uninstall that if you see that.
4) Anyway, back to our troubleshooting. So you would think that you are all set and your qualcomm port should be recognized, but no. It failed to recognize. So try this:
Reboot PC.
Reboot Phone.
5) Now Proceed. Hopefully by now you have see your qualcomm port. Great.
6) This is the trickiest part. You need to click on the "Download Content" "IMMEDIATELY" "AS SOON AS" you hit enter on "adb reboot edl".
[Image]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7) Yay. You see very nice progress in the little progress section on QFIL. You think you'ved nailed it.. But no, you could again end up getting another error. (Unfortunately I forgot to get a screenshot). Anyway, you would see this multiple times, that the "File access is very slow"; I'm not sure if only I received that error or if it is generic.
8) When you get an error at this point. Try a different port. Luckily, I got it to work on my second attempt on another attempt.
My review on the stock ROM:
Honestly, the custom ROM installed by the seller worked way better for me. This stock ROM had a lot of chinese apps (which of course I can uninstall). But somehow, the custom ROM from the seller felt better. Luckily I had a nandroid backup and I went back to it. The only drawback apart from OTA, being on the latest etc etc is that I cannot use the heartrate sensor (which is no big deal for me).
I guess I'll wait for another AOSP or another custom ROM or probably something with Android N before I upgrade again.
Hope this helps."

Thanks for getting back to me. I remember reading this before, however I cannot apply it to the current situation (but I tried anyway).
However there is an update to share. After some time I was able to go through the full download via MiFlash as before (with the 'successful' message) and moreover, flashing via QFIL finally started to produce something promising, however at the end it showed this message (no change to the state of the phone):
View attachment 131237287087498319.log
Next try showed the same error message as before:
View attachment 131237297946525488.log

SOLVED!
Hallelujah! After many many many tries (just doing the same over and over and over) the stock ROM (2.0.048) was finally uploaded (using QFIL)!
I was trying to hold power off and/or volume buttons while and after connecting to PC just to try different things and maybe that helped as well.
If someone will experience the same issue as me, I have one advice - don't loose your faith, don't give up!
And if you are thinking about flashing via MiFlash, simply just don't.

Creshaw said:
Hallelujah! After many many many tries (just doing the same over and over and over) the stock ROM (2.0.048) was finally uploaded (using QFIL)!
I was trying to hold power off and/or volume buttons while and after connecting to PC just to try different things and maybe that helped as well.
If someone will experience the same issue as me, I have one advice - don't loose your faith, don't give up!
And if you are thinking about flashing via MiFlash, simply just don't.
Click to expand...
Click to collapse
Glad you got it figured out! Enjoy your Z2 Pro

Hello there, I'm having a similar problem that the owner of this thread had, but the difference is that the adb doesn't detects my device.
I've tried to reinstall all the drivers, and downloaded the Android SDK tools, but still doesn't works...
Any idea about what to do? The device is with the screen in black, no led blinks or anything like that, and when connected to the PC, only detrects the Qualcomm 9008 port...
Thank you in advance.

Now after some research, I found out that the "ADB interface" is not showing in Windows device manager
I tried to install it manually, but can't find a way to get it working, and after the flash, USB debugging was set on, so can't figure out what could be happening...
Is it possible it's completely dead?
Any idea?

--

Thanks to valuable help from Emmaus and DanRO from zukfans.eu I managed to render my phone operable once more and now it runs flawlessly. This recovery is a life-saver for anyone experiencing bricking or malfunction issues:
https://yadi.sk/d/DfTYl-jz3Cxg76
_The first thing to do is to enter fastboot menu (pressing vol rockers will help)
_Then you will need to unlock bootloader with the dedicated commands:
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
fastboot -i 0x2b4c oem unlock-go
For noobs or newcomers: Be informed that you will need the OEM bootloader image from ZUK website through giving your credential and phone's serial number for unlocking, you can see the instructions on the forum or by googling it.
_After unlocking your bootloader you should flash the aforementioned and link-given recovery with the following commands:
fastboot -i 0x2b4c flash recovery twrp_name.img
(Replace "twrp_name" with the name of the downloaded image and without quotes)
_Once you successfully enter TWRP Recovery menu, you can either flash a TWRP-flashable file or else, by tapping reboot button you can select EDL (9008) option to open 9008 port on QPST for being able to flash any official firmware.
_Check your internal storage on flashing TWRP-flashable ROMs. In my case, after I flashed recovery and then a CM-based ROM (AICP), I saw that the phone had only a 9GB-size as internal storage. If you happen to face the same issue, just flash an official firmware on QPST, as this problem occurs due to bad partitioning, at least that is what it seems.
Ask anything for any further details.
Thanks.

Can't power off....help!
Hi all.
My Z2 Plus is old 4 day! Buyed from Gearbest, i flashed the latest stock CN Firmware with QFIL, unlocked bootloader, installed CN TWRP and flashed GizRom 1.1 from Franck076,
After this, i backupped all from TWRP and flashed Francko76 Global v7 and Mokee Official 7.1.1 for test. To return to normal use, i restored the backup GizChina Rom 1.1 and i rebooted.
DISASTER!
My Zuk Z2 screen is black, no flashing led, it's vibrate every 25/30 seconds andt there's no way that i can power off! I read so many guides to unbrick, but all say that the phone is switched off. In every tested so it continues to vibrate...
Please, help me!

Also I am Now Bricked
When Z2Pro was hung up during QFIL connection with EDL mode, It cannot but wait until battery empty because it does not reaction to the reboot with the VOL PowerBtn's switch either.
if Disassemble the Z2pro then remove buttery,maybe re-QFIL.
Anyone,want you to tell me if you know the method for reboot z2pro.whthout Disassemble it.

maofedeli said:
Hi all.
My Z2 Plus is old 4 day! Buyed from Gearbest, i flashed the latest stock CN Firmware with QFIL, unlocked bootloader, installed CN TWRP and flashed GizRom 1.1 from Franck076,
After this, i backupped all from TWRP and flashed Francko76 Global v7 and Mokee Official 7.1.1 for test. To return to normal use, i restored the backup GizChina Rom 1.1 and i rebooted.
DISASTER!
My Zuk Z2 screen is black, no flashing led, it's vibrate every 25/30 seconds andt there's no way that i can power off! I read so many guides to unbrick, but all say that the phone is switched off. In every tested so it continues to vibrate...
Please, help me!
Click to expand...
Click to collapse
Have you figured out a way?

Hi all,
received a Z2 pro, flashed with multi language rom, without OTA upgrades. When sim inserted, there was no connection to the network. After several attempts, i decided to send it back.
Ordered from another shop a new 2 ro, ( i know, very stupid to try twice) and this time, when tried to flash it from multi language rom, with an official one, it was bricked. Deep flash trick and.....
Tried several times to open HS-USB QDloader 9008 and once every 20 times it was a success. But, Sahara error all the time in qfil and hallo packet error in miflash. I'm out of ideas,.... Do you hve any?

Guys,
My ZUK Z2 Pro (bootloader unlocked) after finish loading the entire system (android) and appear the home screen, it reboots itself. When its boot it connected to PC, it does not reboot and after 5s I can remove cable and use it without problems. If the cable is in charge adapter, it also has the same problem.
Summary: I always need to turn on it connected in PC (with drivers installed) and wait 5s after finished loading all OS + startup APPs to not reboot alone. I install TWRP for good but no change to install custom ROM as it comes in loop after loading bootloader. Only ROMs that are stock, installed using QFIL works.
Do you have any idea?
Btw: I was using Mokee Rom without problems but after starting somes Frameworks apps te rom bricked out.

No 9008
Hello, i am new here and posted a reply in a different place. I think the wrong thread, so i will write here too.
I have a Zuk Z2 Pro. Unlocked bootloader, TWRP (twrp-3.2.1-0-z2_row.img) and installed several roms to try out. Then i read about a new ZUI and wanted to flash it. But, i made a mistake and now my phone is bricked. I read all about unbricking and flashing wit QFIL, but (and like others) my pc does not recognize my phone anymore. I can not work with adb (windows commands) and in QFIL i can not get the needed 9008 port. I installed all the needed stuff, but nothing.
Can someone help me out please. I already followed all the stept in some tutorials, but i get stuck with this 9008, which will not appear.
Phone does not start up. Recovery is gone, only menu with fastboot, recovery etc. is there. And the ZUI screen (from the rom i wanted to install) but the screen does not respond anymore, so i can not begin with setting the phone.
Is there a solution so i can flash with QFIL?
Or another solution?
Thanks,
Alex
Update 18-03-2018
This worked for me to get the needed 9008 port for flashing with QFIL:
- Open QFIL
- Phone must be off
- Connect usb cable to pc (not to phone yet)
- press volume up + power button and immediately connect usb cable to phone
- phone will vibrate 3 time (screen stays black/off)
- pc recognizes phone (there is this familiar sound of your pc)
- In QFIL you wil see port 9008
- just flash and wait till it's done
Off course you must have drivers etc installed on your pc, all the needed stuff for flashing. Don't forget to charge you phone.

I bricked my lenovo z2 plus, it is not booting to ROM or fastboot, it only vibrates after I hold the power button, and keeps vibrating every 10 sec, can anybody help me??

[GUIDE] Unbrick Tool for OnePlus 5 with OOS 9.0.9 & OOS 9.0.11 (Untouched full stock)

[GUIDE] Unbrick Tool for OnePlus 5 with OOS 9.0.9 & OOS 9.0.11 (Untouched full stock)
Hello Everyone !!​
=>A hard bricked OP5 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP5 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP5 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.
=>The solution for OP5 hardbrick is similar to OP3,OP3T- you just need a Qualcomm driver and a recovery package.it'll help to get out from one of the most weird state of the phone.(file is exact file from OnePlus)
METHOD​
This method is easy to use and flashes OxygenOS 5.1.7 and OxygenOS 9.0.9 on your phone. It wipes all your data and restores all partitions to stock. It will work in any condition unless it is a hardware damage.
Step 1 :- DOWNLOADS :-
OOS 9.0.9: https://mega.nz/file/O4dGFI4b#mbqq8VqUiPwoN85ajTV-H2pDNccD58-ccejQnTQHIBE
OOS 9.0.11:https://mega.nz/file/ekUURaII#FPoezmYL1hPJUkb2Hf90ZqW07iEaCza6etnTPSKJOos
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
How to Make the device show as Qualcomm 9008​
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)Download this :- http://www.mediafire.com/file/4aqwyi3g1d6wc67/Qualcomm+1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
P.S.: I found the fix for bootloader menu which was changing after flashing through this tool. Just flash the zip in the recovery from the link below after flashing the rom through this tool, and you are good to go.
Please boot your device, set it up then go back to recovery and flash this file.
https://mega.nz/file/n10kkKCQ#LmCm_TDDyZ9cdZPf2pk0mSSV1bgvZflENQG0ubl15SY
NOTE: When the tool gives the "Sahara error", DON'T DISCONNECT THE PHONE from your PC, and press vol up and power button. It maybe seem stupid as a fix but generally it works.
IMP NOTE: There is a quick update, recently I also got stuck at param processing while flashing my device. So uploading the tool which works well. Here is the link. https://mega.nz/file/C1Nw3Cyb#znHfATPuRN4rAy1ZnDO4kMcftEkQ1P6enGxRGSiBh2E
IMP NOTE: There is a quick update, the tool is updated with latest TREBLE OS.
CREDITS​ @vasu97 - for helping and motivating me to create this thread
@Mar-cel - for bootloader fix zip
Click thanks IF i helped you

Where did you get this file, after I restored it, the bootblock unlock menu changed, is that normal?

Yes it is normal, mine also changed. May be they changed something in latest tool

Hi! First of all, thx for this post. I am getting Error 258 when i execute the tool. I am getting " Qualcomm HS-USB QDLoader 9008" in device manager, is that right? When i'm executing the program, he begins to download cache.img, and then stop and shows me this error :T Gonna send some pics to better ilustrate it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you help me? Thx again.
EDIT: I forgot to mention that my cellphone turns on the led, in color green, when the tool starts to running.

cidsantiago said:
Hi! First of all, thx for this post. I am getting Error 258 when i execute the tool. I am getting " Qualcomm HS-USB QDLoader 9008" in device manager, is that right? When i'm executing the program, he begins to download cache.img, and then stop and shows me this error :T Gonna send some pics to better ilustrate it.
Can you help me? Thx again.
EDIT: I forgot to mention that my cellphone turns on the led, in color green, when the tool starts to running.
Click to expand...
Click to collapse
hv u tried running this tool as administrator abd ur fone shud not turn on any of the led while flashing.. if u r on twrp try format data .. and then try flashing it thru tool.. or may be its bad download at ur side. redownload again.. and try

cidsantiago said:
Hi! First of all, thx for this post. I am getting Error 258 when i execute the tool. I am getting " Qualcomm HS-USB QDLoader 9008" in device manager, is that right? When i'm executing the program, he begins to download cache.img, and then stop and shows me this error :T Gonna send some pics to better ilustrate it.
View attachment 4445915
View attachment 4445916
Can you help me? Thx again.
EDIT: I forgot to mention that my cellphone turns on the led, in color green, when the tool starts to running.
Click to expand...
Click to collapse
Don't worry about green led light while flashing with tool its normal behavior, and about error...maybe because of bad download for sure,try attaching your phone again or check the drivers again...and look at the firs comment - seems like tool is working fine.

djnim said:
hv u tried running this tool as administrator abd ur fone shud not turn on any of the led while flashing.. if u r on twrp try format data .. and then try flashing it thru tool.. or may be its bad download at ur side. redownload again.. and try
Click to expand...
Click to collapse
Yes, i ran it as administrator. M phone was totally bricked, i only got signal in him when i connected at the PC. But i always had this error :T I downloaded it at least 5 times, and got always the same results.
vasu97 said:
Don't worry about green led light while flashing with tool its normal behavior, and about error...maybe because of bad download for sure,try attaching your phone again or check the drivers again...and look at the firs comment - seems like tool is working fine.
Click to expand...
Click to collapse
I did it all, believe me. Reinstalled the drivers multiples times, differents PCS, differents USB ports... I think it was a hardware problem.
I already sent my phone to RMA, so i think it was solved, one way or another But thanks for your replies

cidsantiago said:
Yes, i ran it as administrator. M phone was totally bricked, i only got signal in him when i connected at the PC. But i always had this error :T I downloaded it at least 5 times, and got always the same results.
I did it all, believe me. Reinstalled the drivers multiples times, differents PCS, differents USB ports... I think it was a hardware problem.
I already sent my phone to RMA, so i think it was solved, one way or another But thanks for your replies
Click to expand...
Click to collapse
ohh.. i got tensed as it is my very first thread .

best method to return sotck complete

Thanks for the clear instructions, you have just saved my phone

Dude, thanks for the guide. But kindly check your links in the post. Some are dead ( especially : the mediafire link you gave at last )

Hi
Thank you so much !

AnDrOiDnEoV said:
Dude, thanks for the guide. But kindly check your links in the post. Some are dead ( especially : the mediafire link you gave at last )
Click to expand...
Click to collapse
That's correct. The right link is this: http://www.mediafire.com/file/4aqwyi3g1d6wc67/Qualcomm+1.00.11.rar

Hi, thanks for making this guide with such clear instructions!
I've done every step according to the guide, but I keep facing this issue:
Just to clarify I did run it as administrator.

Are you going to update (5.1.2)?

esedix02 said:
Are you going to update (5.1.2)?
Click to expand...
Click to collapse
If i Get it then yes for sure

Op updated with the bootloader fix, which helps to revert to old bootloader menu.

Op updated with new tool which includes OOS 5.1.2.

Mate she worked a charm! I wasn't bricked but wanted to restore to full stock after issues with open beta rims, firmware and AOSP roms. Was the simplest way to achieve a fresh start

it downloads the ROM while flashing? Or ROM is included in given link by OP?

Maze Alpha X Bootloop Problem [SOLVED]

Hello everybody please help me. I tried to Root my phone I unlocked the phone while getting help from “dreambo” then I unlocked the phone and download twrp recovery then when I tried to start phone it only showed me recovery menu sistem was not opening then tried to chech “dreambo” again then i saw a picture (picture 1) there I wrote “fastboot flash recovery boot.alpha.x.img” instead of “fastboot flash boot boot.alpha.x.img” and now phones recovery didnt open and become bootloop it shows logo then turn off (video 1) then i cant able to to put phone into “bootloader mode” . I know this phone doesn’t have stock rom how can i fix this phone ?
dreambo Thread: Root and TWRP 3.2.1 for Maze Alpha X 6/64
(picture 1)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(video 1)​
video link: https://youtu.be/QYMCOQiExMg
Originally Posted
dreambo said:
I am almost sure that you have flashed the recovery image in the boot partition !
You have do that fastboot flash boot recovery.img instead of fastboot flash recovery recovery.img
To have your phone working, just flash the attached boot.img : fastboot flash boot boot.alpha.x.img
Click to expand...
Click to collapse
Edit: Way to solve Problem:
Stive very thanks to my friend after a long time I fixed the phone. In order to do UNBRICK phone download this from link and than put phone into charge than connect phone to computer with usb and open "Flash tool" program than add “MT6757_Android_scatterr.txt” file than put it “Frimware Upgrade” than download and wait until it finished.
Stive87 said:
Unbrick Maze Alpha X 6/64GB only phone is black screen and phone is total brick (format all partition).
https://drive.google.com/file/d/12t3MHsAWBlXyKm_ktJt9GKqZ9sOrFRVi/view
Rom is no official :
System : official rom for Maze Alpha B6/64GB . (! no update after - OTA !!),
boot, logo and recovery is normal (copy from original my phone).
Good luck.
Sorry for bad english, my french ^^
Click to expand...
Click to collapse
Stive87 said:
https://drive.google.com/file/d/12t3MHsAWBlXyKm_ktJt9GKqZ9sOrFRVi/view?usp=drivesdk
full rom V03 6/64GB Rom Ofifcial Stock
https://drive.google.com/file/d/1WjXKj8abnghy_OjfUW5TYkAppjWg0amH/view?usp=sharing
Click to expand...
Click to collapse
Thanks to everyone who helped!!

help please

rafaello21 said:
help please
Click to expand...
Click to collapse
Became interested in this phone since I found a 6/128 model for 160$. If fastboot is failing (maybe because of the different partition size?) I'd go with SPFlashTool: if I remember well phone only need to be swithed off when you start downloading the image, therefore it goes well with bootloping if you choose the right moment

matteo.de-leo said:
Became interested in this phone since I found a 6/128 model for 160$. If fastboot is failing (maybe because of the different partition size?) I'd go with SPFlashTool: if I remember well phone only need to be swithed off when you start downloading the image, therefore it goes well with bootloping if you choose the right moment
Click to expand...
Click to collapse
I bought it 170$ when it was on discount no matter what i do “bootloader mode” not works because of the error that i did and no one helps

rafaello21 said:
I bought it 170$ when it was on discount no matter what i do “bootloader mode” not works because of the error that i did and no one helps
Click to expand...
Click to collapse
That's exactly what I'm saying: SPFlashTool doesn't require your phone to be in fastboot mode, only to be switched of when you plug it in. I had the same problem with an Archos Sense 55S after treying to root it. I wasn't able to enter neither fastboot or recovery mode, therefore I flashed the stock rom with SPFT

matteo.de-leo said:
That's exactly what I'm saying: SPFlashTool doesn't require your phone to be in fastboot mode, only to be switched of when you plug it in. I had the same problem with an Archos Sense 55S after treying to root it. I wasn't able to enter neither fastboot or recovery mode, therefore I flashed the stock rom with SPFT
Click to expand...
Click to collapse
I would do it if i have Stock rom ? i am very disappointed because of bought this phone how is it possible that phone doesnt have stock rom is there any possibility to fix this without stock rom?

rafaello21 said:
I would do it if i have Stock rom i am very disappointed because of bought this phone how is it possible that phone doesnt have stock rom is there any possibility to fix this without stock rom?
Click to expand...
Click to collapse
Which model are you using, the 6/64 or the 6/128?
For the former you can use a TWRP Backup done by @dreambo in order to restore at least the boot and and recovery partition
https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575
while for the latter a link in this post (https://forum.xda-developers.com/maze-alpha/development/original-rom-t3720714) is given ( eventually as soon as my phone arrives I can dump the image):
Option 1) https://drive.google.com/drive/folde...ZyDQFgygsdkei2
Option 2) http://bit.ly/2GKcmYe

matteo.de-leo said:
Which model are you using, the 6/64 or the 6/128?
For the former you can use a TWRP Backup done by @dreambo in order to restore at least the boot and and recovery partition
https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575
while for the latter a link in this post (https://forum.xda-developers.com/maze-alpha/development/original-rom-t3720714) is given ( eventually as soon as my phone arrives I can dump the image):
Option 1) https://drive.google.com/drive/folde...ZyDQFgygsdkei2
Option 2) http://bit.ly/2GKcmYe
Click to expand...
Click to collapse
Hi, can i use this to restore my phone? And do you know how? I did a search in the web but didn't fin any solution.

ttl1982 said:
Hi, can i use this to restore my phone? And do you know how? I did a search in the web but didn't fin any solution.
Click to expand...
Click to collapse
Hi ttl1982, before giving an answer I should know what are we talking about. Is it the same phone? And which version? What is the current situation (bootlooping into TWRP, bootlooping into Android)? Even assuming we're still talking about the Maze Alpha X, there are still too much variables!

matteo.de-leo said:
Which model are you using, the 6/64 or the 6/128?
For the former you can use a TWRP Backup done by @dreambo in order to restore at least the boot and and recovery partition
https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575
while for the latter a link in this post (https://forum.xda-developers.com/maze-alpha/development/original-rom-t3720714) is given ( eventually as soon as my phone arrives I can dump the image):
Option 1) https://drive.google.com/drive/folde...ZyDQFgygsdkei2
Option 2) http://bit.ly/2GKcmYe
Click to expand...
Click to collapse
I have Maze Alpha X 6/64 model. If “bootloader mode” doesnt open how can i install ‘twrp’ ? About Thread article i read everything but my only problem is my phone dont open “bootloader mode”. And only solution is stock rom i think than you need SPFlashTool to install it. Maybe you know better than me how can i install “twrp” without opening “bootloader mode” ? I wrote above why this happened.
I click Power and Vol+ buttons as i show in the video phone turn of but doesn’t open “bootloader mode”

rafaello21 said:
I have Maze Alpha X 6/64 model. If “bootloader mode” doesnt open how can i install ‘twrp’ ? About Thread article i read everything but my only problem is my phone dont open “bootloader mode”. And only solution is stock rom i think than you need SPFlashTool to install it. Maybe you know better than me how can i install “twrp” without opening “bootloader mode” ? I wrote above why this happened.
I click Power and Vol+ buttons as i show in the video phone turn of but doesn’t open “bootloader mode”
Click to expand...
Click to collapse
No, even in the case you just want to boot into TWRP (and be able to use one of the backups provided in that post) you need to access fastboot mode. during bootlooping does your PC find the device with the "adb devices" command (namely, as soon as your phone boots up you'd spam this command via terminal)?

matteo.de-leo said:
Hi ttl1982, before giving an answer I should know what are we talking about. Is it the same phone? And which version? What is the current situation (bootlooping into TWRP, bootlooping into Android)? Even assuming we're still talking about the Maze Alpha X, there are still too much variables!
Click to expand...
Click to collapse
Hi, Thanks for your quick response. I will share some more info like you asked.
- Phone: Maze Alpha X
- Version: 6GB RAM/128GB Storage
- Current situation: It won't start at all (when connected to Windows PC i get the 'USB device not recognized' error, so it does see something)
My idea is the following:
- Install recovery with SPK flashtool
- Restore with backup (i have this from another thread) or the system dump.
The above does not work because i do not have the correct preloader file (so SPK flash tool does recognize the phone?).
ADB is not recognizing the phone, so it can't be done that way (as far as my knowledge goes).
I asked Maze several times to provide me the original rom but i get zero response, no matter on what channel i ask them.

matteo.de-leo said:
No, even in the case you just want to boot into TWRP (and be able to use one of the backups provided in that post) you need to access fastboot mode. during bootlooping does your PC find the device with the "adb devices" command (namely, as soon as your phone boots up you'd spam this command via terminal)?
Click to expand...
Click to collapse
I will try but phone turn off and one very quick. Is 1-2 seconds enough for doing what you are saying ? Twrp flash i have to do ? Is there any phone and have similar problem like this ? Can help with help of Video ? And i will try what you said and back to you thanks

ttl1982 said:
Hi, Thanks for your quick response. I will share some more info like you asked.
- Phone: Maze Alpha X
- Version: 6GB RAM/128GB Storage
- Current situation: It won't start at all (when connected to Windows PC i get the 'USB device not recognized' error, so it does see something)
I got this phone from my nephew. He broke it because he flashed the Maze Alpha (not X) 4GB RAM/64GB storage rom on it because he had TWRP bootloops.
My idea is the following:
- Install recovery with SPK flashtool
- Restore with backup (i have this from another thread) or the system dump.
The above does not work because i do not have the correct preloader file (so SPK flash tool does recognize the phone?).
ADB is not recognizing the phone, so it can't be done that way (as far as my knowledge goes).
I asked Maze several times to provide me the original rom but i get zero response, no matter on what channel i ask them.
Click to expand...
Click to collapse
I also wrote them several times about stock rom but they didn’t answer me i think company only think about money. Do we have to throw our phone to garbage because of one wrong thing ? What should i do ?

ttl1982 said:
My idea is the following:
- Install recovery with SPK flashtool
- Restore with backup (i have this from another thread) or the system dump.
Click to expand...
Click to collapse
Yes I was thinking the same. Eventually you do not need to install the recovery, restoring the bootloader should be enough: if the bootloader is already unlocked you can just boot into TWRP and from there restoring the backup previously copied into a SD card.
The above does not work because i do not have the correct preloader file (so SPK flash tool does recognize the phone?).
Click to expand...
Click to collapse
Why do you say you don't have the right one? Did SPFlashTool return you some error?
I asked Maze several times to provide me the original rom but i get zero response, no matter on what channel i ask them.
Click to expand...
Click to collapse
Well AFAIK Maze is completely done, no surprise if they do not answer. I'm reasonably sure that there's a way to dump these files from a working phone, if I'm right I'll try with mine

matteo.de-leo said:
No, even in the case you just want to boot into TWRP (and be able to use one of the backups provided in that post) you need to access fastboot mode. during bootlooping does your PC find the device with the "adb devices" command (namely, as soon as your phone boots up you'd spam this command via terminal)?
Click to expand...
Click to collapse
I tried when I click Power and Vol+ it does bootloop.But the only way to put phone into “bootloader mode” you need SPFlashTool. I dont know what can i do now. When phone was bootlooping i wrote several times “adb devices” but nothing happened

matteo.de-leo said:
Yes I was thinking the same. Eventually you do not need to install the recovery, restoring the bootloader should be enough: if the bootloader is already unlocked you can just boot into TWRP and from there restoring the backup previously copied into a SD card.
I will try this, maybe that works.
Why do you say you don't have the right one? Did SPFlashTool return you some error?
Yes, it says 'status preloader invalid'
Well AFAIK Maze is completely done, no surprise if they do not answer. I'm reasonably sure that there's a way to dump these files from a working phone, if I'm right I'll try with mine
Click to expand...
Click to collapse
That explains a lot. But it is still not acceptable to answer no one imo
---------- Post added at 10:48 PM ---------- Previous post was at 10:34 PM ----------
matteo.de-leo said:
Yes I was thinking the same. Eventually you do not need to install the recovery, restoring the bootloader should be enough: if the bootloader is already unlocked you can just boot into TWRP and from there restoring the backup previously copied into a SD card.
Why do you say you don't have the right one? Did SPFlashTool return you some error?
Well AFAIK Maze is completely done, no surprise if they do not answer. I'm reasonably sure that there's a way to dump these files from a working phone, if I'm right I'll try with mine
Click to expand...
Click to collapse
ttl1982 said:
That explains a lot. But it is still not acceptable to answer no one imo
Click to expand...
Click to collapse
I now get another error when flashing boot.img:
ERROR: STATUS_BROM_CMD_STARTCMD_FAIL

ttl1982 said:
ERROR: STATUS_BROM_CMD_STARTCMD_FAIL
Click to expand...
Click to collapse
As reported by another user on this website: https://forum.hovatek.com/thread-21351.html
The device attempted to power on before SP flash tool could flash files to it
Click to expand...
Click to collapse
Phone must be plugged (while switched off) to the USB port after having given the Download order to SP
---------- Post added at 09:38 PM ---------- Previous post was at 09:34 PM ----------
By the way, it seems that this very website (in particular here https://forum.hovatek.com/thread-468.html) hosts a guide to dump a Mediatek firmware SPFlashTool compatible, together with the necessary files, but guess what? You need to register in order to download them, something that I'll definitely do if it just lets me

ttl1982 said:
I now get another error when flashing boot.img:
Click to expand...
Click to collapse
Which boot.img you chose ?
matteo.de-leo said:
Phone must be plugged (while switched off) to the USB port after having given the Download order to SP
Click to expand...
Click to collapse
What should i do exactly to use SPFlashTool ? What alternative ? When I connect my phone to pc it turn off turn on then power volume + and - buttons randomly and than turn on turn off stoped now it looks like this in the picture . Than i checked “adb devices” it says “waiting for devices”. The thing that “dreambo” shared “boot.alpha.x.img” and can i adjust this with SPFlashTool and install it ?

rafaello21 said:
Which boot.img you chose ?
What should i do exactly to use SPFlashTool ? What alternative ? When I connect my phone to pc it turn off turn on then power volume + and - buttons randomly and than turn on turn off stoped now it looks like this in the picture . Than i checked “adb devices” it says “waiting for devices”. The thing that “dreambo” shared “boot.alpha.x.img” and can i adjust this with SPFlashTool and install it ?
View attachment 4518023
Click to expand...
Click to collapse
I have used the exact same boot.img as you did.

P9 Lite [VNS-l31] [HARD BRICKED] [CORRUPT PARTITIONS] EDL UNBRICKING

Hi,
Hoping to get some help from the Huawei Dev community here on XDA.
POPPING MY CHERRY - 1st HARD-BRICKED DEVICE
Doesn't feel very good!!!!
So I was trying to upgrade my old VNS-L31 from Android 6 to 7 or install a custom ROM due to some apps no longer having support for Android 6.
Dload method failed.
Was on C16 somehow (supposed to be on C185). Tried to flash new OEM_info which is where the problems started. Initially my DATA partition got corrupted, not sure exactly where it happend but I suspect it happend while I was trying to fastboot flash the newer Android 7 stock system cust etc images.
No TWRP posted here on XDA worked - tried 9 of em NON WORKED
So I was stuck at 3.0.2-0 that worked from SRKToolkit way back when I first rooted it.
After the data partition get corrupted it all went down hill. Nothing worked to fix the partition.
No Dload method worked (finding stock roms for this thing proved a massive challenge so I was stuck with trying what I could find)
After flashing new C432 oem_info and custom.bin I I got bootloop and tried the following stock roms with dload
- C4432B172
- C432B413
- C432B130
- C432B172
Non worked, complaining about incompatible versions.
Stock recovery also couldn't fix the data partition
eRecovery couldn't find a ROM ( I think cuz huawei doesn't have the ROMs on their servers anymore (neither C185, C16 or C432 got a ROM on eRecovery).
With no other options remaining I was forced to try and fix the data partition manually ( this is where the device got hard bricked ).
So I used parted and deleted the userdata partition -> re-created it and added it to the /etc/fstab.
Using this post as a reference: [DEV][ Expand System Partition To 4GB - P9 Lite ]
Note: parted said the primary GPT partition table was corrupt. It said the backup GPT partition table would be used.
As soon as I rebooted from TWRP I got black screen everywhere and the only mode the phone would go into was fastboot.
Tried everything there to get the device back but with a corrupt partition table I knew I was farting into the wind.
After that failed I knew this device was basically dead and the ONLY, ONLY way to unbrick it would be to try EDL test points.
Ok so I got the phone open and got into EDL Qualcomm HS-USB QDLoader 9008 mode (OLD mode it seems -> No storage device detected).
PotatoNV detects the device now as a EVA-L19C432B166 (I have no idea how that happend, I have no ROMs that has that BUILD).
I have QPST and QFIL but lack the programmer file and basic knowledge of how this type of flashing works.
So this is where I'm at - I think I might as well throw this thing in the trash bin but since I got the opportunity now to work with QFIL and try everything to unbrick this thing and gain some knowledge about how EDL mode works I'm thinking I might as well play around with it.
Any advise/Help with this would be GREATLY appreciated.
PS: interestingly PotatoNV generated a NEW unlock code for me now - cant believe I payed DC-unlocker to get me an unlock code for this phone.
So PotatoNV generated a new code not the old I had - and it worked to unlock the bootloader
@-Alf-

gh0stza said:
Hi,
Hoping to get some help from the Huawei Dev community here on XDA.
POPPING MY CHERRY - 1st HARD-BRICKED DEVICE
Doesn't feel very good!!!!
So I was trying to upgrade my old VNS-L31 from Android 6 to 7 or install a custom ROM due to some apps no longer having support for Android 6.
Dload method failed.
Was on C16 somehow (supposed to be on C185). Tried to flash new OEM_info which is where the problems started. Initially my DATA partition got corrupted, not sure exactly where it happend but I suspect it happend while I was trying to fastboot flash the newer Android 7 stock system cust etc images.
No TWRP posted here on XDA worked - tried 9 of em NON WORKED
So I was stuck at 3.0.2-0 that worked from SRKToolkit way back when I first rooted it.
After the data partition get corrupted it all went down hill. Nothing worked to fix the partition.
No Dload method worked (finding stock roms for this thing proved a massive challenge so I was stuck with trying what I could find)
After flashing new C432 oem_info and custom.bin I I got bootloop and tried the following stock roms with dload
- C4432B172
- C432B413
- C432B130
- C432B172
Non worked, complaining about incompatible versions.
Stock recovery also couldn't fix the data partition
eRecovery couldn't find a ROM ( I think cuz huawei doesn't have the ROMs on their servers anymore (neither C185, C16 or C432 got a ROM on eRecovery).
With no other options remaining I was forced to try and fix the data partition manually ( this is where the device got hard bricked ).
So I used parted and deleted the userdata partition -> re-created it and added it to the /etc/fstab.
Using this post as a reference: [DEV][ Expand System Partition To 4GB - P9 Lite ]
Note: parted said the primary GPT partition table was corrupt. It said the backup GPT partition table would be used.
As soon as I rebooted from TWRP I got black screen everywhere and the only mode the phone would go into was fastboot.
Tried everything there to get the device back but with a corrupt partition table I knew I was farting into the wind.
After that failed I knew this device was basically dead and the ONLY, ONLY way to unbrick it would be to try EDL test points.
Ok so I got the phone open and got into EDL Qualcomm HS-USB QDLoader 9008 mode (OLD mode it seems -> No storage device detected).
PotatoNV detects the device now as a EVA-L19C432B166 (I have no idea how that happend, I have no ROMs that has that BUILD).
I have QPST and QFIL but lack the programmer file and basic knowledge of how this type of flashing works.
So this is where I'm at - I think I might as well throw this thing in the trash bin but since I got the opportunity now to work with QFIL and try everything to unbrick this thing and gain some knowledge about how EDL mode works I'm thinking I might as well play around with it.
Any advise/Help with this would be GREATLY appreciated.
PS: interestingly PotatoNV generated a NEW unlock code for me now - cant believe I payed DC-unlocker to get me an unlock code for this phone.
So PotatoNV generated a new code not the old I had - and it worked to unlock the bootloader
@-Alf-
Click to expand...
Click to collapse
Hello,
in fastboot mode (if possible) run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post results.

-Alf- said:
Hello,
in fastboot mode (if possible) run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post results.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Product model should be VNS-L31 - And it was before the partition got corrupted
EVA-L19 I think is the plain P9
Vendor country was C16 and then I flashed C432 (hw/eu) through TWRP
Ah **** ... just realized the OEMInfo I flashed was the L19 ( attaching it ) - the device worked after the flash though but it couldn't have helped with the dload version mismatch.
L19c432b182-oeminfo-custom.bin_flash.zip

gh0stza said:
View attachment 5723589
Product model should be VNS-L31 - And it was before the partition got corrupted
EVA-L19 I think is the plain P9
Vendor country was C16 and then I flashed C432 (hw/eu) through TWRP
Ah **** ... just realized the OEMInfo I flashed was the L19 ( attaching it ) - the device worked after the flash though but it couldn't have helped with the dload version mismatch.
L19c432b182-oeminfo-custom.bin_flash.zip
Click to expand...
Click to collapse
Try the following:
1. Download vns-l31c432b370
Link (2 .zip files - update.zip and update_data_full_VNS-L31_hw_eu.zip)
2. Download oeminfo l31c432
Link
3. Install TWRP 3.0.2.0, flash C432 oeminfo.zip file, DON'T REBOOT, go back in TWRP menu, flash update.zip , go back again and flash update_data_full_VNS-L31_hw_eu.zip.
4. In TWRP select Reboot recovery and do Factory reset.
I can't give you any better advice.

-Alf- said:
Try the following:
1. Download vns-l31c432b370
Link (2 .zip files - update.zip and update_data_full_VNS-L31_hw_eu.zip)
2. Download oeminfo l31c432
Link
3. Install TWRP 3.0.2.0, flash C432 oeminfo.zip file, DON'T REBOOT, go back in TWRP menu, flash update.zip , go back again and flash update_data_full_VNS-L31_hw_eu.zip.
4. In TWRP select Reboot recovery and do Factory reset.
I can't give you any better advice.
Click to expand...
Click to collapse
And I really appreciate it but I only have black screen rememeber...
No recovery, no eRecovery, no TWRP no nothing. The PC detects a fastboot device and I can send fastboot commands but that's it, apart from the EDL mode.
So whatever fix, it has to happen either in fastboot or EDL.
I need a programmer firehose file and some advise on how to use QFIL properly, or a solution in fastboot ( which I think is unlikely )
Thanks @-Alf=

gh0stza said:
And I really appreciate it but I only have black screen rememeber...
Click to expand...
Click to collapse
My bad, sorry

-Alf- said:
My bad, sorry
Click to expand...
Click to collapse
But ur spot on with those files man.
Wish I spoke to you before I bricked the damn thing.
This is all on me ( and a little bit on Huawei for making an easy-brickable-device )
I knew messing around with the partition table would be dangerous, but I had no other options left after the primary GPT partition table got corrupt. Or atleast I thought I had no other choice, in retro-spect I would have tried a thousand other things before I modified the partition table directly.
Let this be a lesson for anyone else stumbling unto this thread...
It just feels like such a waste... There is nothing physically wrong with the device but almost zero chance of reviving it without the programmer files from huawei ( which I will prob never get )
PS: Maybe I can use some other firehose file...
Take a look at this site I found: https://www.leakite.com/?s=Qualcomm+Programmer
Maybe one of these programmer files are similar enough to use???
Anyone got an idea?

gh0stza said:
and a little bit on Huawei for making an easy-brickable-device
Click to expand...
Click to collapse
Huawei devices seem to be fairly indestructible, as long as the Bootloader is open, imo. If you don't mix apples and oranges, of course .

-Alf- said:
Huawei devices seem to be fairly indestructible, as long as the Bootloader is open, imo. If you don't mix apples and oranges, of course .
Click to expand...
Click to collapse
Well interestingly, almost every time I dload'ed some firmware (even though it failed) it relocked my bootloader.
If I didn't have a bootloader unlock key, I would have had troubles much earlier.
Note: This is why I am very sceptical about paying DC-Unlocker a bunch of money to unlock my bootloader without giving me a key (That's the only way according to them on the P20 Pro - I assume they use some exploit on android 7-9; 10+ they say is not possible).
Then again... after I opened it up and used test points (for the first time, mind you) I discovered this model's bootloader is soooooo damn easy to crack with PotatoNV. Even HARD-BRICKED PotatoNV still gave me an unlock key.
Plus the back cover basically just pops right off -> 8 screws and 2 connectors later and it's unlocked
Credit to: Andrey Smirnoff
This makes me wonder if the P20 Pro would be just as easy ( I have one of those too, that I haven't been able to unlock yet )

I've messed around with the system partition table the first time and also messed up. Then tried to repair it by flashing the stock firmware, thinking it would reconstruct/replace my bad changes to /system and it only made it lock the bootloader. Thankfully PotatoNV indeed came to the rescue. So after flashing some different firmwares/twrp eventually it booted to the stock rom and I was then able to expand the system partition and rock the LOS on the vns-l31.
So I indeed feel for you when you're going down this lane. Unfortunately, I don't have much to add but I'm genuinely curious how you can fix the phone out of this situation. If you ever find a solution that wasn't posted here I'd appreciate if you could then give us an update on how you solved it. This is the kind of stuff I'd love to learn.

Phantom Thief said:
I've messed around with the system partition table the first time and also messed up. Then tried to repair it by flashing the stock firmware, thinking it would reconstruct/replace my bad changes to /system and it only made it lock the bootloader. Thankfully PotatoNV indeed came to the rescue. So after flashing some different firmwares/twrp eventually it booted to the stock rom and I was then able to expand the system partition and rock the LOS on the vns-l31.
So I indeed feel for you when you're going down this lane. Unfortunately, I don't have much to add but I'm genuinely curious how you can fix the phone out of this situation. If you ever find a solution that wasn't posted here I'd appreciate if you could then give us an update on how you solved it. This is the kind of stuff I'd love to learn.
Click to expand...
Click to collapse
Hi Phantom,
Thnx for the suggestion, will try flashing a couple img's later and hope for the best.
Else I'm still convinced I can fix it through EDL.
Will give updates here if I can achieve anything.
If you get any info on flashing through EDL, do let me know please.

gh0stza said:
This makes me wonder if the P20 Pro would be just as easy ( I have one of those too, that I haven't been able to unlock yet )
Click to expand...
Click to collapse
As usual with my luck: https://en.wikipedia.org/wiki/Huawei_P20
The P20 Pro(CLT-L09) has a Kirin 970 SoC, not supported by PotatoNV.
So HCU-Client it is...
Which also means downgrading from EMUI 12.0.0 - here we go again!

-Alf- said:
Try the following:
1. Download vns-l31c432b370
Link (2 .zip files - update.zip and update_data_full_VNS-L31_hw_eu.zip)
2. Download oeminfo l31c432
Link
3. Install TWRP 3.0.2.0, flash C432 oeminfo.zip file, DON'T REBOOT, go back in TWRP menu, flash update.zip , go back again and flash update_data_full_VNS-L31_hw_eu.zip.
4. In TWRP select Reboot recovery and do Factory reset.
I can't give you any better advice.
Click to expand...
Click to collapse
Thank you very much