Database Develop

Unbrick lg lte 2 f160 lsk qhsusb_dload no recovery no download mode

I brick my lg f160k while flashing wrong kdz on it. It was in no download no recovery mode. Pc was showing qhsusb_dloade 9008. I searched alot over the internet to unbrick it but found nothing except a thread on veitnam site by a veitnamis developer. Thanks to him for this useful thread. With the help of this i unbrick my cell. It was very difficult to understand the thread while in Vietnam's language but i managed to do so with the help of google translator. I thought i should must share it on xda to English community for easy umderstading. Hit thanks if you get your phone back. And many thanks to veitnamis developer too....
1. Download the qualcom drivers and install it from given link.
https://app.box.com/s/5n42md550n4oxne04xttfz788cp0i4i3
Open device manager and ensure that you have correctly installed qualcom 9008 drivers. Remember the com port
2. Download and unzip this folder
https://app.box.com/s/zvvj2v87csuwmv93k7ztzevuiytyd0fi
You shall have a tool Boar Diag v3.99c folder and two folder named S and L.
3.IMPORTANT. You will have to choose folder S For F160K and S and for F160L and LV choose Folder L.
4. Now run the tool.
Check the 2 points on tool
1.Ap check
2.Emmc Test
In Ap chipset choose board
For F160s and F160k
D1L(MSM8960 SKDA)
FOR 160L
D1L(MSM8960 LV)
Select Com Port shown in device manager of your computer.
In TARGET DIR Choose the Folder of Named S or L according to your modal, As i told you earlier in step 3
Rest all should be unchecked
PRESS START
https://app.box.com/s/hr8y0cmzcond0jciemprl5jzr4rllggn
Now test will start and will take 10 seconds to complete
If this test run successfully AP and EMMC should show pass on tool window
5. In this step Now only uncheck
Emmc Test and then check the
Boot Image Restore and select ABOOT from drop down menu.
Only w points Checked.
Ap Check
Boot Img Restor
Rest all should be uncheck the same as in previous step.
PRESS START
https://app.box.com/s/w1r560py2bm2wwlbtch9bn7kh1bski2u
Now it will Test the AP CHECK and will write Boot image to your mobile.
It will take 10 to 15 seconds.
After successfully completion of this test you ll see download mode on your mobile. Or you may see an LG logo with a secure boot massege.
Important...
STEP 6 was not mentioned in orignal thread. I did this at my own and got my result.
6. If you dont see download mode or LG logo after completing step 5 even successfully completion shown ion tool, As in mine case on F160k. Then try step 5 with AP CHIPSET with D1L(MSM8960 RR&G)
rest same selection.
AND PRESS START.
I hope this will resolve your issue. As i did.
7. NOW ITS TIME TO FLASH LATEST KDZ FIRMWARE ACCORDING TO YOUR MoBILE Phone.
.
THATS ALL WHAT I HAVE FOR MY FRIENDS.
IF I HELPED YOU THEN PLZ PRAY FOR ME. THANKS ALOT

Thank you for providing the files! I have a bricked LG LTE2 F160K, which mode should I put the phone be?
My phone can still access download mode, and when I try to start up the tool, it just says "Failed during loading flash programmer"

bro if your download mode is working then you will have to flash kdz of your modal for f160k I think its 20k. you can find the latest kdz many sites. google it lg firmware you can find it on vietnam site lgviet.com

this programe is only for qhsusb_delod mode. no download no recovery state. if you have download mode then kdz is the way to unbrick

Help! "device was not found in dload trying flash programmer" i get this error

What kind of brick you have? Its qhsusb bulk mode. Then this guide will help you

what is "ion took"??
there are no "D1L(MSM8960 RR&G)" in the selection

muzammil457 said:
What kind of brick you have? Its qhsusb bulk mode. Then this guide will help you
Click to expand...
Click to collapse
test completed but my phone didn't enter to download mode
the driver name when i connect my LG is"QHSUSB_QLOAD"

why yu no reply??

Have you installed qualcm drivers first? If no then do it if yes then in board ap choose msm8960 it will work. But if doesnt then there is 1 more 8960 selection try that

Does this method works for a sony xperia ion which has the same problem????

ahamedlaheer said:
Does this method works for a sony xperia ion which has the same problem????
Click to expand...
Click to collapse
This programe is for qualcom devices. If your experia is qualcom based then it will work. But u need to find the files to flash doe your modalm I have loaded only f160 system files.

muzammil457 said:
Have you installed qualcm drivers first? If no then do it if yes then in board ap choose msm8960 it will work. But if doesnt then there is 1 more 8960 selection try that
Click to expand...
Click to collapse
yes i install it, i tried the other msm8960 but it doesn't work

Test point to force qhsusb-dload in LG F160s
mcycharles said:
Thank you for providing the files! I have a bricked LG LTE2 F160K, which mode should I put the phone be?
My phone can still access download mode, and when I try to start up the tool, it just says "Failed during loading flash programmer"
Click to expand...
Click to collapse
Dear all,
Can some one provide me the details of test points for LG F160s i want to force it, as m phone in dead alsmost,,,
i will b very thankful
Rizwan

Why u need to do that if u r not in hard brick state?

muzammil457 said:
I brick my lg f160k while flashing wrong kdz on it. It was in no download no recovery mode. Pc was showing qhsusb_dloade 9008. I searched alot over the internet to unbrick it but found nothing except a thread on veitnam site by a veitnamis developer. Thanks to him for this useful thread. With the help of this i unbrick my cell. It was very difficult to understand the thread while in Vietnam's language but i managed to do so with the help of google translator. I thought i should must share it on xda to English community for easy umderstading. Hit thanks if you get your phone back. And many thanks to veitnamis developer too....
1. Download the qualcom drivers and install it from given link.
https://app.box.com/s/5n42md550n4oxne04xttfz788cp0i4i3
Open device manager and ensure that you have correctly installed qualcom 9008 drivers. Remember the com port
2. Download and unzip this folder
https://app.box.com/s/zvvj2v87csuwmv93k7ztzevuiytyd0fi
You shall have a tool Boar Diag v3.99c folder and two folder named S and L.
3.IMPORTANT. You will have to choose folder S For F160K and S and for F160L and LV choose Folder L.
4. Now run the tool.
Check the 2 points on tool
1.Ap check
2.Emmc Test
In Ap chipset choose board
For F160s and F160k
D1L(MSM8960 SKDA)
FOR 160L
D1L(MSM8960 LV)
Select Com Port shown in device manager of your computer.
In TARGET DIR Choose the Folder of Named S or L according to your modal, As i told you earlier in step 3
Rest all should be unchecked
PRESS START
https://app.box.com/s/hr8y0cmzcond0jciemprl5jzr4rllggn
Now test will start and will take 10 seconds to complete
If this test run successfully AP and EMMC should show pass on tool window
5. In this step Now only uncheck
Emmc Test and then check the
Boot Image Restore and select ABOOT from drop down menu.
Only w points Checked.
Ap Check
Boot Img Restor
Rest all should be uncheck the same as in previous step.
PRESS START
https://app.box.com/s/w1r560py2bm2wwlbtch9bn7kh1bski2u
Now it will Test the AP CHECK and will write Boot image to your mobile.
It will take 10 to 15 seconds.
After successfully completion of this test you ll see download mode on your mobile. Or you may see an LG logo with a secure boot massege.
Important...
STEP 6 was not mentioned in orignal thread. I did this at my own and got my result.
6. If you dont see download mode or LG logo after completing step 5 even successfully completion shown ion tool, As in mine case on F160k. Then try step 5 with AP CHIPSET with D1L(MSM8960 RR&G)
rest same selection.
AND PRESS START.
I hope this will resolve your issue. As i did.
7. NOW ITS TIME TO FLASH LATEST KDZ FIRMWARE ACCORDING TO YOUR MoBILE Phone.
. THATS ALL WHAT I HAVE FOR MY FRIENDS.
I have F160L.i tried same as u mention,All proceger complete but no download mode no fastboot mode no LG logo.What to do now?still on qualcomm 9008
Click to expand...
Click to collapse

Hello all
If after restore aboot phone not power on
Need restore all this file: about, Backupgpt, boot, dbi, laf, Primarygpt, recovery, rpm, tz, sdl1, sdl2, sdl3 (one by one, not MIX!!!) and after restore last sdl3 power turn on!

muzammil457 said:
I brick my lg f160k while flashing wrong kdz on it. It was in no download no recovery mode. Pc was showing qhsusb_dloade 9008. I searched alot over the internet to unbrick it but found nothing except a thread on veitnam site by a veitnamis developer. Thanks to him for this useful thread. With the help of this i unbrick my cell. It was very difficult to understand the thread while in Vietnam's language but i managed to do so with the help of google translator. I thought i should must share it on xda to English community for easy umderstading. Hit thanks if you get your phone back. And many thanks to veitnamis developer too....
1. Download the qualcom drivers and install it from given link.
https://app.box.com/s/5n42md550n4oxne04xttfz788cp0i4i3
Open device manager and ensure that you have correctly installed qualcom 9008 drivers. Remember the com port
2. Download and unzip this folder
https://app.box.com/s/zvvj2v87csuwmv93k7ztzevuiytyd0fi
You shall have a tool Boar Diag v3.99c folder and two folder named S and L.
3.IMPORTANT. You will have to choose folder S For F160K and S and for F160L and LV choose Folder L.
4. Now run the tool.
Check the 2 points on tool
1.Ap check
2.Emmc Test
In Ap chipset choose board
For F160s and F160k
D1L(MSM8960 SKDA)
FOR 160L
D1L(MSM8960 LV)
Select Com Port shown in device manager of your computer.
In TARGET DIR Choose the Folder of Named S or L according to your modal, As i told you earlier in step 3
Rest all should be unchecked
PRESS START
https://app.box.com/s/hr8y0cmzcond0jciemprl5jzr4rllggn
Now test will start and will take 10 seconds to complete
If this test run successfully AP and EMMC should show pass on tool window
5. In this step Now only uncheck
Emmc Test and then check the
Boot Image Restore and select ABOOT from drop down menu.
Only w points Checked.
Ap Check
Boot Img Restor
Rest all should be uncheck the same as in previous step.
PRESS START
https://app.box.com/s/w1r560py2bm2wwlbtch9bn7kh1bski2u
Now it will Test the AP CHECK and will write Boot image to your mobile.
It will take 10 to 15 seconds.
After successfully completion of this test you ll see download mode on your mobile. Or you may see an LG logo with a secure boot massege.
Important...
STEP 6 was not mentioned in orignal thread. I did this at my own and got my result.
6. If you dont see download mode or LG logo after completing step 5 even successfully completion shown ion tool, As in mine case on F160k. Then try step 5 with AP CHIPSET with D1L(MSM8960 RR&G)
rest same selection.
AND PRESS START.
I hope this will resolve your issue. As i did.
7. NOW ITS TIME TO FLASH LATEST KDZ FIRMWARE ACCORDING TO YOUR MoBILE Phone.
.
THATS ALL WHAT I HAVE FOR MY FRIENDS.
IF I HELPED YOU THEN PLZ PRAY FOR ME. THANKS ALOT
Click to expand...
Click to collapse
any other link for qualcomm drivers?

Link is fine. U can download it from google.

Need some Help
My phone goes to Service Mode but not in Download mode.
Should i try this method?
And how i can find out my phone is S OR K OR L originally hardware based
Waiting for your answer .
My phone is dead since 1 month

[CLOSED]DNX mode BIOS flashing tool

@MikeChannon removed OP. please close
what? lol

hi ionioni,
many thanks for your tool. I could successfully create a signed bios file. During the flashing process, i believe, it shows no errors. But after a automatically reboot just the teclast logo appears.
I did a "RESTORE DEFAULT" and "SAVE AND RESET" but when i try to flash android with the mirek tool, it shows the same error message (get_path:344...) .
Do you have any suggestions what i can try to restore a working state?
Thank you.

the_dude_84 said:
During the flashing process, i believe, it shows no errors. But after a automatically reboot just the teclast logo appears
Click to expand...
Click to collapse
at the end of the bios flashing, before the reboot, did you received a "RESTORE COMPLETED! Rebooting the tab to load new BIOS!" message? if not, what messages you got when flashing? what are the steps you are doing? more details ... this tool job is to write a (user provided) bios file, not fixing specific stuff (other) on your tab
later edit: the error 'get_path:344' is normal to be shown. the x98 bootloader (efilinux file) will at first try to get a handle for the device (disk) it was started from, but when it is run directly from the bios, ie dnx mode (normally it loads/executes from his EFI partition on mmc) the call returns no handle (as it should) and this is causing the message. is a normal message if starting from dnx, what is not normal, is if after that the bootloader won't be able to load and execute the kernel from the passed boot image.

the tablet just restarts without such a message you named. I used my prevously saves bios with your tool and flash it. What steps i can do to convince the tablet to start the kernel?

Did you repair the saved BIOS before flash by this new tool?
You have to change from FE FE at 400Dh and 400Eh address to FF FF with a hex editor!

updated OP with v2 of the tool as it seems these x98 tabs are not having the most conforming EFI firmware in the bios (it 'forgets' the consistent mapped device so i hard-coded it in the tool, it would have map to the same path anyways as it is a consistent /virtual/ disk that is used as environment during the flashing, so this 'patch' just helps the non-conforming devices /such as x98 so far/ not limits)

blackbile said:
Did you repair the saved BIOS before flash by this new tool?
You have to change from FE FE at 400Dh and 400Eh address to FF FF with a hex editor!
Click to expand...
Click to collapse
do you know what those two bytes are about? can anyone say that he bricked his tab by flashing a FE FE bios? (i have flashed my bios back dozen times so far on my Lenovo and did not knew about this until read someplace on these posts so i checked my backup bios file and sure thing it did have the FE FE inside at that offset... i guess is something wrong with my tab since it did not bricked )
joke aside, i cannot say whether this IS or IS NOT true, but what i can say is that there were two users i assisted in flashing back their bios backup (on x98 models) and both had FE FE at that offset and they did NOT BRICKED ( @florent.m was on ant the other don't recall)... i wish i knew more about WHY this needs to be done, not just YOU MUST instructions... what i know is that area belongs to the nvram of TXE region (is the EFFSOSID partition of it) but since Intel takes care that no one has access to TXE related info i sure would be interested in someone saying what those two bytes are accounted for (and more of course)...
again someone who has a flash programmer can check easily and safely (i have but as i said i cannot hard-brick it )

I'm still not able to flash. I get this error message upon running fastboot boot image_name.img
Code:
INVALID size (7586586 bytes) for pushed package! This tool will only accept a (md5) BIOS file for input. You MUST run md5add.exe on your BIOS file and push the file it produces.
ABORTING
I did run md5add on the img and I did run fastboot boot on the image it produced (16 bytes larger than the original). What am I doing wrong?
BTW, by pushing does it mean that I have to run anything else besides those 2 commands on fastboot?

andrepd said:
I'm still not able to flash. I get this error message upon running fastboot boot image_name.img
Code:
INVALID size (7586586 bytes) for pushed package! This tool will only accept a (md5) BIOS file for input. You MUST run md5add.exe on your BIOS file and push the file it produces.
ABORTING
I did run md5add on the img and I did run fastboot boot on the image it produced (16 bytes larger than the original). What am I doing wrong?
BTW, by pushing does it mean that I have to run anything else besides those 2 commands on fastboot?
Click to expand...
Click to collapse
read the op again !!! and do exactly the steps detailed there!!! you need to use YOUR signed bios file generated with md5add ... instead you are WRONGLY!!! using some boot image file (luckily for you there is a size check too, otherwise you would have been flashing a kernel on your bios chip, oh boy...)
again:
the first instruction pushes the bios efi flasher tool
the second one pushes YOUR bios (signed) file that you want to flash on your bios chip. to make sure that the bios file that is wrote by the tool is not altered during the transfer i added the extra md5 signing step, so before it will start the effective flashing the efi tool will check the bios file received against the md5 signature appended (this step is normally not needed, but on some PC could be that the usb transfer misbehaves)

Thanks a lot for your efforts and help!!!

ionioni said:
read the op again !!! and do exactly the steps detailed there!!! you need to use YOUR signed bios file generated with md5add ... instead you are WRONGLY!!! using some boot image file (luckily for you there is a size check too, otherwise you would have been flashing a kernel on your bios chip, oh boy...)
again:
the first instruction pushes the bios efi flasher tool
the second one pushes YOUR bios (signed) file that you want to flash on your bios chip. to make sure that the bios file that is wrote by the tool is not altered during the transfer i added the extra md5 signing step, so before it will start the effective flashing the efi tool will check the bios file received against the md5 signature appended (this step is normally not needed, but on some PC could be that the usb transfer misbehaves)
Click to expand...
Click to collapse
But the image I'm flashing isn't even 7586586 bytes... I'm flashing with this tool as per this post http://forum.xda-developers.com/showpost.php?p=64854157&postcount=26 (img in the OP of that thread)
Sorry I'm a bit confused... Is that boot image the wrong one to flash then?

Thank you very much!
I think it worked and is waiting for input or is even done already, but I'm quite cautious now, so I don't want to press anything yet
It says:
FPT operation passed
_
Click to expand...
Click to collapse
In the flash.bat from another tool (TTT-Update the BIOS on your X98 Air II/3G to the latest dual boot version) it should write that status to a log file and continue with either flash passed or failed, but apparently it doesn't continue automatically in my case.
Hope anyone knows if it is safe to do anything. I've pressed the power button shortly as a confirmation command, but that doesn't do anything.

andrepd said:
But the image I'm flashing isn't even 7586586 bytes... I'm flashing with this tool as per this post http://forum.xda-developers.com/showpost.php?p=64854157&postcount=26 (img in the OP of that thread)
Sorry I'm a bit confused... Is that boot image the wrong one to flash then?
Click to expand...
Click to collapse
This is a DIFFERENT tool! that one you are refering to already has a BIOS file in it...
This one flashes a bios file YOU MUST provide!
Bolsnerk said:
Thank you very much!
I think it worked and is waiting for input or is even done already, but I'm quite cautious now, so I don't want to press anything yet
It says:
In the flash.bat from another tool (TTT-Update the BIOS on your X98 Air II/3G to the latest dual boot version) it should write that status to a log file and continue with either flash passed or failed, but apparently it doesn't continue automatically in my case.
Hope anyone knows if it is safe to do anything. I've pressed the power button shortly as a confirmation command, but that doesn't do anything.
Click to expand...
Click to collapse
As said on some x98 devices (having a specific bios?) it seems that after the bios is flashed 100% it hangs... not so much you can do but force a power off/reboot ... you should be fine

ionioni said:
This is a DIFFERENT tool! that one you are refering to already has a BIOS file in it...
This one flashes a bios file YOU MUST provide!
Click to expand...
Click to collapse
Okay, I got it working, phew, I was being a total noob and confusing everything. I took the dual boot BIOS, added the md5 hash with the tool you provided and flashed it with your tool. Everything went well. Thank you for your work and sorry for being a total moron

andrepd said:
Okay, I got it working, phew, I was being a total noob and confusing everything. I took the dual boot BIOS, added the md5 hash with the tool you provided and flashed it with your tool. Everything went well. Thank you for your work and sorry for being a total moron
Click to expand...
Click to collapse
Excellent!

ionioni said:
do you know what those two bytes are about? can anyone say that he bricked his tab by flashing a FE FE bios? (i have flashed my bios back dozen times so far on my Lenovo and did not knew about this until read someplace on these posts so i checked my backup bios file and sure thing it did have the FE FE inside at that offset... i guess is something wrong with my tab since it did not bricked )
joke aside, i cannot say whether this IS or IS NOT true, but what i can say is that there were two users i assisted in flashing back their bios backup (on x98 models) and both had FE FE at that offset and they did NOT BRICKED ( @florent.m was on ant the other don't recall)... i wish i knew more about WHY this needs to be done, not just YOU MUST instructions... what i know is that area belongs to the nvram of TXE region (is the EFFSOSID partition of it) but since Intel takes care that no one has access to TXE related info i sure would be interested in someone saying what those two bytes are accounted for (and more of course)...
again someone who has a flash programmer can check easily and safely (i have but as i said i cannot hard-brick it )
Click to expand...
Click to collapse
IonIoni,
All,
1st - thanks again for your tool, it saved my tablet (teclast C5J8)
2nd - yes the boot file I provided to Ionioni was untouched, a direct copy of the bios as dumped by mirek backup tool, and up to now, everything is working fine, either on android, or on Windows 10.
and when I say everything fine......I want to say as before..........the GPS is still not working (((((((
thanks a lot,
Cheers,
Florent

Holy moley, the last 24 hours have been intense, that is how old my x98 air iii is, and I have read over a thousand pages here on XDA in that time, i've also managed to soft brick it trying to flash a dual boot bios as per Techknights/Techtablets guides, not sure why or where exactly things went bad, now i'm stuck in a boot loop, red Chinese symbols with a tiny arrow beside it, but reading this gives me some hope, no idea how to follow the simple instructions above when you say..
" IMPORTANT: run the md5add tool on your bios file md5add.exe your_bios_file your_signed_bios_file. "
tried a few things and got nowhere, I tried to open the bios file that you said to place in the same folder as the other two files, with the md5add tool and a small window flashed on screen for a millisecond then disappeared, that's all no file was produced lol
Also not sure what this part means too..
"start in dnx mode and input:
fastboot flash osloader bios_flasher.efi.."
I can get into dnx mode ok but thats all how do I input anything?
My head is fried but I will stay up and try again, it's 5am (Ireland)
Am I missing an elephant in the room? like some other software the everyone else has already installed except noobs like me?

pilot error said:
Holy moley, the last 24 hours have been intense, that is how old my x98 air iii is, and I have read over a thousand pages here on XDA in that time, i've also managed to soft brick it trying to flash a dual boot bios as per Techknights/Techtablets guides, not sure why or where exactly things went bad, now i'm stuck in a boot loop, red Chinese symbols with a tiny arrow beside it, but reading this gives me some hope, no idea how to follow the simple instructions above when you say..
" IMPORTANT: run the md5add tool on your bios file md5add.exe your_bios_file your_signed_bios_file. "
tried a few things and got nowhere, I tried to open the bios file that you said to place in the same folder as the other two files, with the md5add tool and a small window flashed on screen for a millisecond then disappeared, that's all no file was produced lol
Also not sure what this part means too..
"start in dnx mode and input:
fastboot flash osloader bios_flasher.efi.."
I can get into dnx mode ok but thats all how do I input anything?
My head is fried but I will stay up and try again, it's 5am (Ireland)
Am I missing an elephant in the room? like some other software the everyone else has already installed except noobs like me?
Click to expand...
Click to collapse
i wonder how could the instructions in this op be more simple...
you must:
1. find a BIOS file for you model, make sure it is the CORRECT one or you might hard-brick when you flash it
2. sign the file using the md5add tool, this will create a new file, the signed bios file
3. start in dnx mode and load the efi bios flasher tool and then you bios signed file (the steps are in the op)

ionioni said:
i wonder how could the instructions in this op be more simple...
you must:
1. find a BIOS file for you model, make sure it is the CORRECT one or you might hard-brick when you flash it
2. sign the file using the md5add tool, this will create a new file, the signed bios file
3. start in dnx mode and load the efi bios flasher tool and then you bios signed file (the steps are in the op)
Click to expand...
Click to collapse
You know what ionioni, they may be simple to you, but this is my FIRST android tab, its only two days old and it's soft bricked on the very first try at bios flashing from following equally simple instructions from techtablets, flashing new bios from within android using update ifwi.apk, I did exactly that chose the 2.02 dual boot bios that everyone else used, copied it to internal storage and pressed the button.
That is all I did to ruin this tablet lol
What techtablets did NOT mention is he was already rooted on mirek190 v6, that is why my tab is softbricked, not because I chose the wrong files.
No idea how to do this step.. "sign the file using the md5add tool", when i search about it, the only results are back in here?
Can you point me in the right direction to learn about md5add?
Thnk you..

pilot error said:
You know what ionioni, they may be simple to you, but this is my FIRST android tab, its only two days old and it's soft bricked on the very first try at bios flashing from following equally simple instructions from techtablets, flashing new bios from within android using update ifwi.apk, I did exactly that chose the 2.02 dual boot bios that everyone else used, copied it to internal storage and pressed the button.
That is all I did to ruin this tablet lol
What techtablets did NOT mention is he was already rooted on mirek190 v6, that is why my tab is softbricked, not because I chose the wrong files.
No idea how to do this step.. "sign the file using the md5add tool", when i search about it, the only results are back in here?
Can you point me in the right direction to learn about md5add?
Thnk you..
Click to expand...
Click to collapse
i give you the tools and the how-to use them...
again, you need to do this:
1. FIND a bios file for your tab model, ask around and some other owner can point you at it, but take care as this is the file that will be programmed in your tablet so if it is not good you will HARD-BRICK (ask ten times before using it once)
2. after you have found the file, use the md5add tool to sign, if for eg the file is named some_bios_file.bin you can input at a command prompt:
md5add.exe some_bios_file.bin signed_bios.bin (the signed_bios.bin file will be generated)
3. start your tab in dnx mode and input:
fastboot flash osloader bios_flasher.efi
fastboot boot signed_bios.bin and this will start the flashing process... messages will be shown on your tab screen while progressing...
the md5add.exe and bios_flasher.efi files can be found in the attachment to the first post (op)
the bios file is your responsibility to find
when done if the bios file you used is correct you should be able to use again the tab (ie no more bootloop)
i must repeat: be careful what bios file you use, if it's a wrong one you can HARD-BRICK! ask around for that...

install update on root-ed phone // is there a way

hello everybody
i've rooted my moto E4 plus, using this guide:
https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-plus-guide-to-rooting-mediatek-t3668753
and everything worked well.. however - i would like to update my phone software, and i do not know what spell to cast now..
what is the best way to go now?
thanks

Restore stock firmware, that includes stock recovery.

ATTACK said:
Restore stock firmware, that includes stock recovery.
Click to expand...
Click to collapse
hi ATTACK, thanks for reply.
i've tried to restore scattered file (bunch of bin-s) using miracle box, but without success. it seams that miracle is not able to restore these files as phones firmware - or i am doing something wrong.
procedure:
i run miracle box, i choose adequate mtk version, i pick write mode, and select .txt (scatter file). in the same dir there are many .bin files..
what should i do?
thanks

vladimirnikolic said:
hi ATTACK, thanks for reply.
i've tried to restore scattered file (bunch of bin-s) using miracle box, but without success. it seams that miracle is not able to restore these files as phones firmware - or i am doing something wrong.
procedure:
i run miracle box, i choose adequate mtk version, i pick write mode, and select .txt (scatter file). in the same dir there are many .bin files..
what should i do?
thanks
Click to expand...
Click to collapse
i get messages:
Waiting for USB Port...
Set MediaTek PreLoader USB VCOM Port (COM7)
Please Hold "ON" to connect with the phone...
Connected to Phone.
CPU: MT6735 SW:0000 Ver: CB00
Downloading Boot8 ...
EMMC Size: 0x03A3E00000
Flash Type: EMMC
INT/EXT RAM Size: 0x0+0x0
Writing(Nand/eMMC)...
>>Error1: no 5A

.. update - i've tried with sp flash tool as well - but it seems that it cannot recognize the scattered file format. the software crashes when i try to load .txt file

Use fastboot to flash the .IMG files. There should be a guide somewhere. It's either here or in the Moto E4 fourm.

sp tools works fine form me.

[GUIDE] How to return to Stock/Flash Images with QFIL

Here is a step by step guide on how to flash the stock rom with QFIL and by extension any image.
Download and install the Qualcomm drivers from here
Download either of the firmware from here
Download the support files (Firehose/rawprogram0.xml/patch0.xml) here
Extract the firmware and support files to the same folder so you can easily access them like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8909.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram0.xml and then the patch0.xml when prompted.
Plug in your tablet
Run the following adb command "adb reboot edl" (Now the screen should be blank but the led light should be red)
If the text at the top of the QFIL application says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you didn't install the drivers properly.
Click the Download Button to begin flashing your device
So the above explains how to flash everything if you want to flash individual partitions you can edit your rawprogram0.xml to only include the ones you want. (patch0.xml stays the same) I have linked below 2 examples, one of them flashes just a boot.img and one that just flashes the recovery.img. But you aren't limited to those.
Recovery
Boot

Mine just in case

Awesome, thanks for this post! it will really help us in upcoming projects!

Managed to revive my phone using the B12 files but it crashes after completing system.img, I think the problem is userdata.img, my phone boots but I lost the imei and I don't know how to get it back, I'm still trying.

ZTE 971 not recognized by either QPST or QFIL
Thanks for all the detailed instructions. But my ZTE 971 is not visible to either qpst or qfil eventhough the phone shows in windows 8.1. In the Developer Options menu, I noticed Select USB Configuration, RNDIS (USB ethernet) option cannot be enabled. I wonder if this has anything to do with it. OEM unlocking, USB debbugging are already selected. Any suggestions, please? Thanks.
ps. I live in Turkey. I got this phone last year from AT&T and have unlocked the sim.

My PC is not detecting my ZTE MAVEN 3
I have installed all drives but still facing the issue. I am using it on Windows 10.

I flashed the B13 (ZPST tool shows my device as B13) with the QFIL like your guide says and it says all completed successfully and finishes, but now my phone went from only being able to boot EDL + FTM + Recovery, to now booting directly to EDL mode, which obviously means this guide completely screwed up my phone... Thanks.

Mega says that link for the driver is invalid, but the driver is included in your QPST download anyway.

000Nick said:
I flashed the B13 (ZPST tool shows my device as B13) with the QFIL like your guide says and it says all completed successfully and finishes, but now my phone went from only being able to boot EDL + FTM + Recovery, to now booting directly to EDL mode, which obviously means this guide completely screwed up my phone... Thanks.
Click to expand...
Click to collapse
solucionaste hermano
Mod edit:
you solved brother
Click to expand...
Click to collapse

it says qhsusb_bulk when I connect the the software is not working in the mobile and it is stuck at bootloader screen but I used the press both buttons to go to edl mode method and it said in the device manager a device connected with name : qhsusb_bulk
help pls

Hello All.
I am not able to get the following files
rawprogram.xml and patch.xml for LG G8x​Please help me to get this files ASAP as i have hard bricked the mobile, all partitions deleted

[blankflash.zip] Hard brick Moto G7 Plus after downgrade

Recently by accident I downgraded the operating system on my Moto G7 Plus device (XT1965-3) and hard bricked my phone. :crying:
It took me some days on checking different threads to come to a solution. I managed to create a blankflash file that finally recovered my bootloader so that I could get into fastboot mode and flash the latest OS.
For those who are faced with the same problem, I'd like to share my solution and hope it works for you as well.
When the phone is hard bricked, it do not boot, it stays in black screen. The good thing though is that by default it goes into Qualcomms EDL (Emergency DownLoad) mode.
When connecting your phone to the PC (e.g. Windows 10) you should see in the device manager under COM the following device:
Qualcomm HS-USB QDLoader 9008 (COM..)
If this do not show up, unplug the phone, press Power + VolumeDown for about 30 seconds and connect the device again.
If it still not works, you might search for the correct drivers.
Assuming you see the device as mentioned above, then you can do the blankflash.
Open a cmd window (ideally with Administrator rights)
Unzip the blankflash.zip View attachment blankflash.zip
Run blank-flash.bat
This should download the bootloader and your phone should get back to live (in fastboot mode)
After you have fixed the bootloader you can flash the latest OS with fastboot mode.
Download the latest version from: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unzip the ROM and add the following files to the same directory View attachment FastBootAddOnFiles.zip
Connect the phone in fastboot mode
Run flashfile.bat from a cmd window
Now the ROM is flashed to the phone
Hope this helps recovering your phone!

Does it work for the power of Moto g7?

Anyway this works on unlocked g7? I need a blank flash or something to revive my hard bricked device

is it possible to restore previously unlocked phone to out-of-the-box software and behaviour? specifically I would like to get rid of the bootloader warning and verity disabled message at boot. I wouldn't mind locking again

"Waiting for device"
Hi WinnieH.
First off, i would like to thank you for explaining the necessity of the blankflash to recover the bootloader.
But when i try the steps you suggested, nothing happens. I get stuck in the message "Waiting for device..."
I noticed that the main command in the bat file is just: ".\qboot.exe blank-flash %*".
Wouldn't be necessary a reference to the singleimage.bin file in this command? Or maybe is a file missing in the zip.
I appreciate some suggestion.
Thanks,
Marcos

mrufino said:
Hi WinnieH.
First off, i would like to thank you for explaining the necessity of the blankflash to recover the bootloader.
But when i try the steps you suggested, nothing happens. I get stuck in the message "Waiting for device..."
I noticed that the main command in the bat file is just: ".\qboot.exe blank-flash %*".
Wouldn't be necessary a reference to the singleimage.bin file in this command? Or maybe is a file missing in the zip.
I appreciate some suggestion.
Thanks,
Marcos
Click to expand...
Click to collapse
Sorry for late response.
if the message "Waiting for device ..." comes, then your phone is not recognized correctly. Your device when bricked should connect in Emergency Download (EDL) mode. You could see this when you go to the Windows Device Manager. Under the COM devices your phone should show up with the Qualcomm. If not, disconnect the phone for a minute and try it again.
If you have the driver not installed it, the installation video might help: https://www.youtube.com/watch?v=ezQJlBKN9hk
PS: The blank-flash.bat is fine. It will automatically use the singleimage.bin file
Hope you get your way

Thank you WinnieH for the response. (that was not late at all!).
I will try to install the driver; I was unable to connect in Emergency Download Mode.

mrufino said:
Thank you WinnieH for the response. (that was not late at all!).
I will try to install the driver; I was unable to connect in Emergency Download Mode.
Click to expand...
Click to collapse
Well, first of all thanks to WinnieH for this useful thread. It worked fine for my phone.
@mrufino Maybe you have to install the moto drivers. Or try a different pc. The phone was not detected on my first pc, on my other pc it was detected immediately.

WinnieH said:
Recently by accident I downgraded the operating system on my Moto G7 Plus device (XT1965-3) and hard bricked my phone. :crying:
It took me some days on checking different threads to come to a solution. I managed to create a blankflash file that finally recovered my bootloader so that I could get into fastboot mode and flash the latest OS.
For those who are faced with the same problem, I'd like to share my solution and hope it works for you as well.
When the phone is hard bricked, it do not boot, it stays in black screen. The good thing though is that by default it goes into Qualcomms EDL (Emergency DownLoad) mode.
When connecting your phone to the PC (e.g. Windows 10) you should see in the device manager under COM the following device:
Qualcomm HS-USB QDLoader 9008 (COM..)
If this do not show up, unplug the phone, press Power + VolumeDown for about 30 seconds and connect the device again.
If it still not works, you might search for the correct drivers.
Assuming you see the device as mentioned above, then you can do the blankflash.
Open a cmd window (ideally with Administrator rights)
Unzip the blankflash.zip View attachment 4810965
Run blank-flash.bat
This should download the bootloader and your phone should get back to live (in fastboot mode)
After you have fixed the bootloader you can flash the latest OS with fastboot mode.
Download the latest version from: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unzip the ROM and add the following files to the same directory View attachment 4810964
Connect the phone in fastboot mode
Run flashfile.bat from a cmd window
Now the ROM is flashed to the phone
Hope this helps recovering your phone!
Click to expand...
Click to collapse
Great post. Where did you find the singleimage for your phone? i've tryed to do with my G7 RIVER bricked, but unsuccessful need some help!

diegovmsouza said:
Great post. Where did you find the singleimage for your phone? i've tryed to do with my G7 RIVER bricked, but unsuccessful need some help!
Click to expand...
Click to collapse
Hello,
I did the image by myself. I used a older image of a G6 device and replace a number of elements in the image from the stockrom. With "star" you can delete and add files to the "singleimage.bin" archive. It took me some trials. Check on the latest STOCK ROM "XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" from https://mirrors.lolinet.com/firmware/moto/lake/official/RETEU/ and you should find the most important files (such as partition table: gpt.bin).
Hope it works for you
Regards
Winnie

WinnieH said:
Hello,
I did the image by myself. I used a older image of a G6 device and replace a number of elements in the image from the stockrom. With "star" you can delete and add files to the "singleimage.bin" archive. It took me some trials. Check on the latest STOCK ROM "XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" from https://mirrors.lolinet.com/firmware/moto/lake/official/RETEU/ and you should find the most important files (such as partition table: gpt.bin).
Hope it works for you
Regards
Winnie
Click to expand...
Click to collapse
Thanks for the answer. Trying to use "Star" I noticed that the files that are inside singleimage.bin are actually files that are inside bootloader.img right? How do I extract the bootloader.img file to use his files? I use linux but I have windows too.

diegovmsouza said:
Thanks for the answer. Trying to use "Star" I noticed that the files that are inside singleimage.bin are actually files that are inside bootloader.img right? How do I extract the bootloader.img file to use his files? I use linux but I have windows too.
Click to expand...
Click to collapse
Just use "star list bootloader.img" and you get all the relevant file.
Code:
star list ..\..\XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\bootloader.img
1 339968 md5:e4c77bb1f8862444bedb908067d5063d abl.elf
2 519296 md5:4b8eaa75b77eae4981604f7893bf7279 cmnlib.mbn
3 519296 md5:ac35656340c5f87037a64ce4f937b16c cmnlib64.mbn
4 2722 md5:d3ee34bff4d352a045b7e42b447666a7 default.xml
5 126080 md5:4590a7b21b0d70d4403fa95ad23a6e9d devcfg.mbn
6 38400 md5:27ba16d71e0d16c86423192d5615a25c gpt.bin
7 519296 md5:0582b648798303e0441930fd84a39b9a hyp.mbn
8 519296 md5:2686fd49e16e78a0e9ef2335104e96bc keymaster.mbn
9 125 md5:c3a63b25166c5fcac0cc1426bf44a271 pkg.xml
10 519296 md5:1437d90bab43816d4a3541b18edac61c pmic.elf
11 257152 md5:5e3b6f2cf09747bd3bac33023c2014a7 prov64.mbn
12 519296 md5:31ab4015a996f2ad6dd61c94076fea98 rpm.mbn
13 126080 md5:5054d3c7863d09d6333c509003548e4d storsec.mbn
14 2092160 md5:44a6f561bab5d2822066574e3d0116eb tz.mbn
15 3665024 md5:a2a5945cf2ae44cd95da3ee180480662 xbl.elf
16 172 md5:1fd033214e7e36c4134a927f1ce944f0 index.xml
17 606400 md5:4b6e1345d3fb9b347ce7fc6357def85a programmer.elf
Extract the files from the bootloader and replace them on the singleimage.bin and thats it.
e.g.
Code:
star delete abl.elf
star add abl.elf
Pressing thumbs

WinnieH said:
Just use "star list bootloader.img" and you get all the relevant file.
Code:
star list ..\..\XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\bootloader.img
1 339968 md5:e4c77bb1f8862444bedb908067d5063d abl.elf
2 519296 md5:4b8eaa75b77eae4981604f7893bf7279 cmnlib.mbn
3 519296 md5:ac35656340c5f87037a64ce4f937b16c cmnlib64.mbn
4 2722 md5:d3ee34bff4d352a045b7e42b447666a7 default.xml
5 126080 md5:4590a7b21b0d70d4403fa95ad23a6e9d devcfg.mbn
6 38400 md5:27ba16d71e0d16c86423192d5615a25c gpt.bin
7 519296 md5:0582b648798303e0441930fd84a39b9a hyp.mbn
8 519296 md5:2686fd49e16e78a0e9ef2335104e96bc keymaster.mbn
9 125 md5:c3a63b25166c5fcac0cc1426bf44a271 pkg.xml
10 519296 md5:1437d90bab43816d4a3541b18edac61c pmic.elf
11 257152 md5:5e3b6f2cf09747bd3bac33023c2014a7 prov64.mbn
12 519296 md5:31ab4015a996f2ad6dd61c94076fea98 rpm.mbn
13 126080 md5:5054d3c7863d09d6333c509003548e4d storsec.mbn
14 2092160 md5:44a6f561bab5d2822066574e3d0116eb tz.mbn
15 3665024 md5:a2a5945cf2ae44cd95da3ee180480662 xbl.elf
16 172 md5:1fd033214e7e36c4134a927f1ce944f0 index.xml
17 606400 md5:4b6e1345d3fb9b347ce7fc6357def85a programmer.elf
Extract the files from the bootloader and replace them on the singleimage.bin and thats it.
e.g.
Code:
star delete abl.elf
star add abl.elf
Pressing thumbs
Click to expand...
Click to collapse
thanks for listening. When I list the bootloader.iso file it returns me the following error: "Failed: simg_open () -> IO error". already extract the rom stock again, already downloaded it from scratch and the result is the same. When I extract the bootloader.iso file the same error occurs. what could it be? Can you help me extract these files? I am attaching the bootloader file of moto g7 river, if you can help me I will be immensely grateful.

diegovmsouza said:
thanks for listening. When I list the bootloader.iso file it returns me the following error: "Failed: simg_open () -> IO error". already extract the rom stock again, already downloaded it from scratch and the result is the same. When I extract the bootloader.iso file the same error occurs. what could it be? Can you help me extract these files? I am attaching the bootloader file of moto g7 river, if you can help me I will be immensely grateful.
Click to expand...
Click to collapse
Hello,
you are right. I should have written down how I created the singleimage.bin file. I replaced the following files in the singleimage.bin from the river stock rom version: XT1962-6_RIVER_RETEU_PPOS29.114-134-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (loaded from: https://mirrors.lolinet.com/firmware/moto/river/official/RETEU/)
gpt.bin
And changed the index.xml to the right CPU 632
You might to play around with the board id if it do not work (board id="204"). I hope the programmer file is the same for the G7 (processor type is slightly different: Snapdragon 632 instead of 636).
Give it a try with attached blankflashRiver.zip

WinnieH said:
Hello,
you are right. I should have written down how I created the singleimage.bin file. I replaced the following files in the singleimage.bin from the river stock rom version: XT1962-6_RIVER_RETEU_PPOS29.114-134-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (loaded from: https://mirrors.lolinet.com/firmware/moto/river/official/RETEU/)
gpt.bin
And changed the index.xml to the right CPU 632
You might to play around with the board id if it do not work (board id="204"). I hope the programmer file is the same for the G7 (processor type is slightly different: Snapdragon 632 instead of 636).
Give it a try with attached blankflashRiver.zip
Click to expand...
Click to collapse
Thanks for the help. the Programmer file isn't the same. After to work arround and beat my head over and over on the wall, I've took my phone to an authorized Motorola. For my surprise, as my phone shows oem_lock, they accepted on warranty. LOL. Now it's on repair and I'll catch tomorrow or another. Thanks for all. Thumbs up!

Rooting with patch security agost 2019
Hello
does this method work for the security patch of august 1, 2019?

does it works in moto g7 power? or others ways that qualcomm port not send error
I tryed in windows 7x64,10x64 without response, it shows me an error port just every time, qualcom usb drivers are shows correct ,
I cant continues with the fastboot part, people any advice?

diegovmsouza said:
Thanks for the answer. Trying to use "Star" I noticed that the files that are inside singleimage.bin are actually files that are inside bootloader.img right? How do I extract the bootloader.img file to use his files? I use linux but I have windows too.
Click to expand...
Click to collapse
Greetings Winnieh !, thanks for all the time and good information that you post,
I have doubts I would appreciate some advice, I have a motorola g7 power (ocean) tha's in hardbrick mode, I have already installed the correct qualcom drivers, the com port recognizes my device, but I cannot get the file blankflash.bat to load the phone to the moment executing it gives me an error:
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM3
[ 0.003] Detecting device
[ 2.218] ReadFile() failed, GetLastError()=0
[ 11.019] ERROR: sahara_greet_device()->device_open()->error opening device
[ 11.019] Check qboot_log.txt for more details
[ 11.019] Total time: 11.019s
FAILED: qb_flash_singleimage()->sahara_greet_device()->device_open()->error open
ing device
I realize that the blankflash.bat for the motog7 + version (river)
based on the blankflash file that you attached
I extracted the bootloader.img files from the stockrom of the motog7 power (ocean) XT1955-2 XT1955-2_OCEAN_AMX_9.0_PPO29.80-79_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml , so also delete and add all the files to the singleimpt.bin file - the gpt.bin file from stock rom copy and replace the one I saw in singleimage.bin
what you notice that index.xml refers to as "cpu.name: msm8953"
it also appears the same in the gpt.bin file, finally with the new singleimage.bin file compiled try to run the blankflash.bat again
unsuccessfully....
Could you tell me what are the mistakes that I can't solve?
i'm not a programmer just a bad lucky pal. if by chance have you a blankflash.bat for ocean version?, i'll really appreciate
Thank you! for your time

Hi WinnieH, I have a similar problem with a Moto G7 Power, can you tell me how I can create a blankflash for my specific model?

Lupask said:
is it possible to restore previously unlocked phone to out-of-the-box software and behaviour? specifically I would like to get rid of the bootloader warning and verity disabled message at boot. I wouldn't mind locking again
Click to expand...
Click to collapse
I have this exact same situation. did you find a solution to it?