Database Develop

Bricked phone.

Hello, i was given a blu R1 HD prime phone that was bricked by one of my relatives, according to him, he tried to do a format all + download on this phone, which as far as im aware, is a death flag, so i have here this bricked phone, i installed mrmazak's prime 6.1 no nv.zip file on this phone, but it still gives me the TOOL DL IMAGE FAIL, error i've heard a lot about, i also saw him saying "THIS IS NOT THE PACKAGE YOU NEED" in which case i can do nothing but ask, whats the correct package to get this bad boy up and running again? thanks beforehand.
PS: The phone is 8gb/1gb ram ver. was on ver 6.1, amazon before the brick, no OTA's.

Shinnazuka0411 said:
Hello, i was given a blu R1 HD prime phone that was bricked by one of my relatives, according to him, he tried to do a format all + download on this phone, which as far as im aware, is a death flag, so i have here this bricked phone, i installed mrmazak's prime 6.1 no nv.zip file on this phone, but it still gives me the TOOL DL IMAGE FAIL, error i've heard a lot about, i also saw him saying "THIS IS NOT THE PACKAGE YOU NEED" in which case i can do nothing but ask, whats the correct package to get this bad boy up and running again? thanks beforehand.
PS: The phone is 8gb/1gb ram ver. was on ver 6.1, amazon before the brick, no OTA's.
Click to expand...
Click to collapse
For a device that was format all. Will need more partitions than are in that package you tried. Also I have tried to work with someone else who had the 8gb size device, we could not get past that error.
I do recall that the last last person got a new board for his phone and pulled the images from it to share. There is a link in the main thread somewhere. But , well even when he tried to restore his own backup from good device to the one with do error, it did not work.
NVM
I remembered it wrong. He tried to pull it, but could not do it.
Look through this thread. Maybe you can try to follow the advice I gave him, and it may work for you.
https://forum.xda-developers.com/r1...-blu-r1-hd-t3440261/post76482224#post76482224

Well, from this mess in english, i can kind of attempt to understand that he tried to install v17 backup, and it didnt work due to the PMT CHANGED FOR THIS ROM, then he somewhere got a .bin backup for miracle?, and then silence, i dont know what else you tried suggesting to him since his english was so bad, i cant follow the steps, on another note, got that .bin backup? maybe ill try flashing it with miracle tool and praying that it'll work. Also, which V17 should i use, NVRAM or NONV

Shinnazuka0411 said:
Well, from this mess in english, i can kind of attempt to understand that he tried to install v17 backup, and it didnt work due to the PMT CHANGED FOR THIS ROM, then he somewhere got a .bin backup for miracle?, and then silence, i dont know what else you tried suggesting to him since his english was so bad, i cant follow the steps, on another note, got that .bin backup? maybe ill try flashing it with miracle tool and praying that it'll work. Also, which V17 should i use, NVRAM or NONV
Click to expand...
Click to collapse
There is now a "repair rom" listed in an mtk support group I try to follow. I have not checked it out yet, but maybe it will help. Let me open this on PC to search for the link
this one was labled v6.4 firmware http://www.mediafire.com/file/6kys9896445l5sm/SP_Flash_Tool_BLU_R0010UU_V6.4_Firmware.zip/file
this is labled as a repair firmware http://www.mediafire.com/file/il54pxuvpkargtr/BLU_R1_HD_R0030UU_REPAIR_MT6735.rar/file
I would have you look at those , first i suppose.
if it does not work I do have backups made from miricle-box, but they are not uploaded anywhere right now.

Real appreciated, will keep you updated, if anything works ill post it here.

Alright, i tried the 6.4 rom, it didnt work, i had it already, i also tried to install the "repair firmware" but in the v5.1628.00.000 version of my SPFT it shows me "SP FLASH TOOL ERROR: (8417) THE LOAD SCATTER FILE IS INVALID", then i try on another version (v5.1744 & v5.1804), then tells me STATUS_SCATTER_FILE_INVALID (0xC00300001), i tried the fix copypasting the hashtags and general settings on top for both cases but that didnt work, i noticed the scatter file looks really weird, not like most of the ones posted here or elsewhere, its just a bunch of rows and not organized in the slightest, maybe i need to try using the scatter for my 8gb/1gb ram? since R0030UU is the 16gb/2gb ram's model code
---------------------------------------------------------------------------------------------------------------------------------------------------------------EDIT: Tried mixed and matching the every file from the MT6735 repair firmware with the ones it didnt have from the prime 6.1 rom whilist using said 6.1 scatter, still on TOOL DL IMAGE FAIL

Shinnazuka0411 said:
Alright, i tried the 6.4 rom, it didnt work, i had it already, i also tried to install the "repair firmware" but in the v5.1628.00.000 version of my SPFT it shows me "SP FLASH TOOL ERROR: (8417) THE LOAD SCATTER FILE IS INVALID", then i try on another version (v5.1744 & v5.1804), then tells me STATUS_SCATTER_FILE_INVALID (0xC00300001), i tried the fix copypasting the hashtags and general settings on top for both cases but that didnt work, i noticed the scatter file looks really weird, not like most of the ones posted here or elsewhere, its just a bunch of rows and not organized in the slightest, maybe i need to try using the scatter for my 8gb/1gb ram? since R0030UU is the 16gb/2gb ram's model code
---------------------------------------------------------------------------------------------------------------------------------------------------------------EDIT: Tried mixed and matching the every file from the MT6735 repair firmware with the ones it didnt have from the prime 6.1 rom whilist using said 6.1 scatter, still on TOOL DL IMAGE FAIL
Click to expand...
Click to collapse
all I can do is share the backup from miricle-box that I have.
https://www.androidfilehost.com/?fid=5862345805528042536

Just trying to catch up, so bricked phone that wont format correct? Do you have twrp on it?

mrmazak said:
all I can do is share the backup from miricle-box that I have.
androidfilehost/?fid=5862345805528042536
Click to expand...
Click to collapse
Hi, this work on BLU R0030UU 2GB/16GB or R0010UU??

TavoStyle said:
Hi, this work on BLU R0030UU 2GB/16GB or R0010UU??
Click to expand...
Click to collapse
This is from 16gb so the R0030uu

mrmazak said:
This is from 16gb so the R0030uu
Click to expand...
Click to collapse
Hi!, I am from Venezuela, I apologize for my English, I am using the Google translator ...
I tried to put the software but the following error appears
{
"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"
}

TavoStyle said:
Hi!, I am from Venezuela, I apologize for my English, I am using the Google translator ...
I tried to put the software but the following error appears
Click to expand...
Click to collapse
Hello,
two issues.
first, the backup has scatter file formatted for use in miracle box, not sp flash tool.
next, The preloader on any updated phone has been changed and does not work to flash anymore.
So, what is / was version on your phone , so I can know if it should be able to work or not?
\

mrmazak said:
Hello,
two issues.
first, the backup has scatter file formatted for use in miracle box, not sp flash tool.
next, The preloader on any updated phone has been changed and does not work to flash anymore.
So, what is / was version on your phone , so I can know if it should be able to work or not?
\
Click to expand...
Click to collapse
First: If I use Miracle Box Crack 2.27A, can it work? (Would I have to disconnect and connect the battery to start the phone again?)
Next: I unchecked the Preloader because once I leave a brick as a phone to leave marked that option
Version: (Screen OLD, Now is in BLU Screen) (Ohhh I never UPDATE the software, I never use ROOT, I never use debloat...)

TavoStyle said:
First: If I use Miracle Box Crack 2.27A, can it work? (Would I have to disconnect and connect the battery to start the phone again?)
Next: I unchecked the Preloader because once I leave a brick as a phone to leave marked that option
Version: (Screen OLD, Now is in BLU Screen) (Ohhh I never UPDATE the software, I never use ROOT, I never use debloat...)
Click to expand...
Click to collapse
Most important part (custom build number) is missing from screen shot.

mrmazak said:
Most important part (custom build number) is missing from screen shot.
Click to expand...
Click to collapse
I just discovered something very crazy, I do not understand anything
In the recovery logs...
https://youtu.be/-sMubZoduig

TavoStyle said:
I just discovered something very crazy, I do not understand anything
In the recovery logs...
https://youtu.be/-sMubZoduig
Click to expand...
Click to collapse
so your build number is 6.6
you may be able to unlock.
But is phone still alive?

mrmazak said:
so your build number is 6.6
you may be able to unlock.
But is phone still alive?
Click to expand...
Click to collapse
My phone is stuck in the BLU logo

TavoStyle said:
My phone is stuck in the BLU logo
Click to expand...
Click to collapse
if it is still locked bootloader, and stock recovery fails to wipe data and / or cache. I do not have idea how to fix.\

Bricked BLU R1 HD
mrmazak said:
if it is still locked bootloader, and stock recovery fails to wipe data and / or cache. I do not have idea how to fix.\
Click to expand...
Click to collapse
Hi Mr Mazak
I had purchased non prime version of BLU R1 HD. I updated to the latest version via OTA. I had my phone rooted with super su and now wanted to try Magisk. After the reboot I had reinstalled the twrp recovery and did a format of all data on my phone. I am trying to install twrp but when I power on my device it is stuck on the boot loading screen. I have tried hold power button and volume down simultaneously and it reboots but gets stuck on the logo.
I tried using the sp flash tool to restore my phone to stock but it did not work. Get error S_BROM_DOWNLOAD_FAIL. 7d
My bootloader is unlocked.
Tried using adb commands but when I connect to the phone and run adb commands it says no authorisation.
If I can install twrp on the device then I will be able to install the rom from rootjunky, not sure if you require more info.
Awaiting your ananlys
Kind Regards

ismailf007 said:
Hi Mr Mazak
I had purchased non prime version of BLU R1 HD. I updated to the latest version via OTA.
Click to expand...
Click to collapse
The latest ota blocks the use of sp flash tool. And the kernel exploit used previouls. But now there is new exploit. But you cannot boot so that is mutt point now
ismailf007 said:
I had my phone rooted with super su and now wanted to try Magisk. After the reboot I had reinstalled the twrp recovery and did a format of all data on my phone.
Click to expand...
Click to collapse
Did you only format the data partition or whole device.?
ismailf007 said:
I am trying to install twrp but when I power on my device it is stuck on the boot loading screen.
Click to expand...
Click to collapse
This confuses me. You just said you had twrp already. Now you have trouble to I stall it.
ismailf007 said:
I have tried hold power button and volume down simultaneously and it reboots but gets stuck on the logo.
Click to expand...
Click to collapse
Did you use / try volume up?
ismailf007 said:
I tried using the sp flash tool to restore my phone to stock but it did not work. Get error S_BROM_DOWNLOAD_FAIL. 7d
My bootloader is unlocked.
Click to expand...
Click to collapse
From what you say.
1. You had working phone with SU root.
2. You have twrp installed
3. You wiped / formated with twrp
4. You now only boot to a logo screen. No recovery, or bootloader?

Phone bricked after trying to update to android 6

Hello, I have the LG G4 H811 (S/W: V10d, written on back of the phone) version. After buying the phone, I tried to update to marshmallow from lollipop using LG Bridge as the automatic update wasn't coming to my phone. After the process was apparently completed my phone isn't turning on anymore. Tried power button, volume up+down+power etc. But not working. no charging sign.
When connecting the phone to pc through usb, most of the times it doesn't find anything ("unknown usb device" or something). Once in a while it finds as "Qualcomm HS-USB QDLOADER 9008" in device manager. ( P.S. It finds as "Qualcomm HS-USB QDLOADER 9008" if I remove and insert the battery for the first time)
Now I've surfed the net for a few hours and found various potential solutions. Was trying this solution first: boycracked dot com/2016/08/04/how-to-unbrick-updates-firmware-flashing-any-lg-android-devices-using-kdz-updater-tools/
(Can't copy direct link being a new member. please replace the "dot")
But the method is not working. Showing "extract file error" when i select the .kdz file and click "launch software update"
Should I try this method: androidmtk dot com/use-qualcomm-flash-image-loader-qfil
By the way, Do I need a specific .kdz file (stock firmware) for the V10d variant? If so, I haven't found it after searching for hours and was trying different .kdz files (all for H811 though). If I need the specific file please give me some link where I can find it. So far the model number(H811) isn't matching when i find a V10d version.
I'll try to use the SD card fix once I manage a card and card reader: forum dot xda-developers.com/tmobile-g4/general/lg-g4-h811-complete-unbrick-guide-100-t3461629
Still I would need the specifc .kdz file I guess for V10d version??
Also if possible please give me the link to a method which is apparently most successful as it seems to be a old problem.
My phone is virtually brand new and am feeling a bit helpless. Please help me by giving some effective solutions. Thanks in advance.
Update: FWIW I followed this link: forum dot gsmhosting.com/vbb/f779/unbrick-lg-g4-brick-hs-usb-qdloader-9008-without-box-2211744/
I apparently succeeded in finishing the operation (didn't use jumper method. Pressed volume up+down method)
But after it showed "succeed", nothing seems to have changed. But seems like the phone is shown as "Qualcomm HS-USB QDLOADER 9008" every time I connect it to PC. Before doing this operation, I had to remove battery and insert again to show it that way. Otherwise it showed "unknown usb device"
But seeing that nothing substantial happening, i tried to follow the same process again. But this time it showed error "Unable to download flash programmer using Sahara protocol"
I don't know what's happening, but just describing the process so that it might be easier for experienced guys to understand.

Why not just use LGUP to flash the Android 6.0 Marshmallow .kdz as a "Referb" and be done with it?
Get the Android 6.0 Marshmallow .kdz for your phone model here:
http://storagecow.eu/index.php?dir=Xda/LG+G4/
Look for T-Mobile H811.
Get LGUP here. LGUP is better than the LG Flash Tool (IMO) and it's easier to use. Don't let the instructions deter you. It's simpler than it looks.
https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Instructions:
1. Connect USB cable to PC.
2. Power off phone and then hold Vol. Up while connecting the USB cable to phone.
3. Your LG G4 should now be in Download Mode.
4. Start LGUP.
5. It should detect your phone. If it does, you will see something like this:
{
"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"
}
6. Select "Upgrade" and then use the "...." to select the .kdz for your phone.
7. Now decide if you want to do a full wipe and flash (Refurbish), or upgrade to a higher version of Android (Upgrade) and keep all of your files and settings.
8. Hit "Start" and wait for it to finish. It may restart your phone a few times. Be patient.
9. You can check the percentage under "Progress".
10. It will let you know when it's done.

Gurren Lagann said:
Why not just use LGUP to flash the Android 6.0 Marshmallow .kdz as a "Referb" and be done with it?
Get the Android 6.0 Marshmallow .kdz for your phone model here:
http://storagecow.eu/index.php?dir=Xda/LG+G4/
Look for T-Mobile H811.
Click to expand...
Click to collapse
Which H811 version should I use? As I asked do I need to use the specific version my phone had before being bricked? (I don't remember which but the default version written on the back of the phone is V10d)
Gurren Lagann said:
Get LGUP here. LGUP is better than the LG Flash Tool (IMO) and it's easier to use. Don't let the instructions deter you. It's simpler than it looks.
https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Click to expand...
Click to collapse
LGUP couldn't detect my phone. I can't remember if I used volume up when connecting but I've tried similar things when trying to different softwares and it wasnt working.
I've given it to a repair shop. After they removed the battery and plugged in two wires from some device to the back of the phone it did turn on but the lg logo came and showing probably error 1006. The repaired said the phone isn't coming to the 'download mode'.
Then they initally tried downloading some h811 dump file and installing it. But failed. Now they're saying they'll need to use JTAG box to fix it.

I just remember now, after buying the phone from some guy, I factory reset it. Now when I opened chrome, some att dot com website was showing as default homepage. That website started loading by default. What does it mean???
Does it mean the phone already had at&t(H810) firmware installed? But when powering on the phone it shows T-mobile logo and H811 is written on the back of the phone(after popping out the back cover) multiple places.
The repairer says the phone is refurbished( (I also think so). So two things can happen:
1. The motherboard was originally H811 but a H810 motherboad and H810 firmware were installed on the phone upon refurbishment. In that case why would it show the T-mobile logo when the phone starts?? Also it showed "H811" in Android (About Phone>>Model number)
2. The motherboard is still H811, but somehow H810 firmware was installed on the phone. Is it possible??? If it is then when I tried to do official update using LG Bridge, maybe LG Bridge thought the phone firmware is H811 and tried to install H811 firmware over a H810 one and the phone got bricked.
What do you think guys?? Any expert suggestion will be highly helpful... As I do feel like knowing which installing the proper firmware(H810 or H811) will take the phone back to life.

Sounds like a Frankenstein device. You can't recover it with using the wrong files. Jtag or not.
Identify the real model first (mainboard FRONT)
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Sounds like a Frankenstein device. You can't recover it with using the wrong files. Jtag or not.
Identify the real model first (mainboard FRONT)
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
So I've to install the firmware(.kdz) according to the model no. written on the motherboard, no matter what other firmware was installed when the phone was running?
Another question, when running normal, it showed "H811" as model number in "About phone" section. Is it possible that the motherboard is NOT H811 but a H811 firmware was installed on it during refurbishment?
Btw, where is the model no. written on the mainboard? Here's a link of the phone teardown: https://www.ifixit.com/Teardown/LG+G4+Teardown/42705
Please give me the link of the picture where it's showing the model no.

onikett said:
So I've to install the firmware(.kdz) according to the model no. written on the motherboard, no matter what other firmware was installed when the phone was running?
Another question, when running normal, it showed "H811" as model number in "About phone" section. Is it possible that the motherboard is NOT H811 but a H811 firmware was installed on it during refurbishment?
Btw, where is the model no. written on the mainboard? Here's a link of the phone teardown: https://www.ifixit.com/Teardown/LG+G4+Teardown/42705
Please give me the link of the picture where it's showing the model no.
Click to expand...
Click to collapse
Frankenstein is what we call a device which is refurbished in a hackish way:
https://forum.xda-developers.com/g4/general/unlock-unlock-lg-g4-device-usu-t3760451/post75817533
---> FAQ 21
So yes I can even let your device say it's an iPhone in android settings, download mode or almost anywhere. It's just code. And yes it's easy.
You can also just flash parts of another ROM if you know how and what so it does not brick or blow fuses. Dangerous when you don't understand how the g4 works internally but the refurbish ppl know what they do to fake the device enough so the average one do not see a diff.
You just have to follow that link in the above FAQ 21 and disassemble the mainboard and on the front you will see it.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Frankenstein is what we call a device which is refurbished in a hackish way:
https://forum.xda-developers.com/g4/general/unlock-unlock-lg-g4-device-usu-t3760451/post75817533
---> FAQ 21
So yes I can even let your device say it's an iPhone in android settings, download mode or almost anywhere. It's just code. And yes it's easy.
You can also just flash parts of another ROM if you know how and what so it does not brick or blow fuses. Dangerous when you don't understand how the g4 works internally but the refurbish ppl know what they do to fake the device enough so the average one do not see a diff.
You just have to follow that link in the above FAQ 21 and disassemble the mainboard and on the front you will see it.
Click to expand...
Click to collapse
Thanks.
1. Do I have to use the .kdz compatible with the actual model number written on the mainboard?
2. Should I use LGUP procedure mentioned in an above post (by Gurren Lagann)?
2. How to know what version of .kdz do I have to install? I heard if the installed version is a downgrade from the actual version (before the phone was bricked), it will not work.
3. If LGUP can't detect my phone due to it being totally hard bricked, what procedure should I follow to install the new .kdz?
I'm not an expert on the intricacies of Android OS. So please answer the questions elaborately.

Dont Try to Update 6.0, if dont wont bricked 9008 mode

[ROM][STOCK] Stock Firmware Packages (For Expanded EDL Tools)

Stock Firmware Packages
Yes, they are finally here! This thread is for stock firmware packages.
These packages are specifically made to be installed with this EDL tool: https://forum.xda-developers.com/ax...n-10-pro-5g-expanded-edl-tools-fixes-t4174667
READ THE WARNINGS IN THAT THREAD BEFORE USING THE TOOLS
These packages are UNOFFICIAL unless marked otherwise. ZTE has not released stock firmware packages for most phones and versions.​
How to install an EDL firmware package:
Note: These packages are specifically made for the EDL tools, not MiFlash or anything else.
1. Install the latest version of the EDL tools (in this thread)
2. Download a firmware package from this thread.
3. Unpack the firmware archive into the tool directory "Firmware_Package_Restore"
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -​Just for example - the script would be located in:​"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"​And the firmware files would be in:​"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"​4. Put phone in EDL mode and run Load Programmer
5. Run a backup of your phone! Even if it isn't booting.
6. Run whichever "Write Firmware vX to Y.ps1" you want (X = firmware version, Y = A or B partition) (If you don't know which partition is currently booting, just install both.)
7. Wait for the install to finish ("done")
8. Start the phone (hold the power button until it resets, or run the Reset script)
9. You might see a few bootloops and then the phone ask you to do a factory reset / system wipe.
10. If the phone does not boot - look in the tools thread for how to use the Fix Bootable tool and try that.
11. Done.
Firmware Package Downloads:
~~~ A2020U (US Version) (Non-5G) ~~~
Firmware Version: 1.10 (GEN_NA_A2020U_PROV1.10)
Android: 9 (Pie)
Source: UNOFFICIAL (bobthenormal)
Download: Axon10Pro A2020U EDL Firmware v1.10(A9)
(If you downloaded this firmware before 12/9/2020 the script had an error, re-download the firmware or simply replace the script files with these ones: Firmware 1.10 Script Fix)
Thanks:
@djkuz for the original EDL tool for Axon 7
@Unjustified Dev for his port of the tool and tons of other work
@rafyvitto for a ton of ROMs and his stock B12 backup
and @eKeith for requesting the firmware enough times I finally bothered to make it =P

Please keep issues with the firmware here, and issues with the EDL tools in that thread.
I will upload firmware versions for A2020U: 1.11, 1.13, 2.09 (A10) (locked and unlocked). I just need to get time to actually test these out to make sure they work.
I didn't test the 1.10 version either but it should work and some people are stuck on A10 without it so I'm trying to post it quickly.
If anyone can wants the tools or firmware packages like these for their phone version (EU, CN, whatever non-A2020U Non-5G) and can volunteer their phone/time, PM me - I can't do them myself as I don't have those phones, but I can give safe instructions on what to do so that I can change make a version of the tools for those phones.

Hi i want the Firmware for zte axon 10 pro 5g 6ram
Details in photo
{
"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"
}
Axon 10 Pro (Non-5G) EDL Tool - Flash / Backup / Restore/ Bootloader Unlock
Axon 10 EDL Tool BAT-program for Flash / Backup / Restore/ Bootloader Unlock Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program !!! Special...
forum.xda-developers.com
My post

amooor said:
Hi i want the Firmware for zte axon 10 pro 5g 6ram
Details in photo
View attachment 5146295
Axon 10 Pro (Non-5G) EDL Tool - Flash / Backup / Restore/ Bootloader Unlock
Axon 10 EDL Tool BAT-program for Flash / Backup / Restore/ Bootloader Unlock Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program !!! Special...
forum.xda-developers.com
My post
Click to expand...
Click to collapse
I'd suggesta new thread. I haven't seen anyone with that phone or a firmware package for it. If you can find someone that has your phone with stock firmware who is willing to do a little work, I'll tell them what to do to make it.

bobthenormal said:
I'd suggesta new thread. I haven't seen anyone with that phone or a firmware package for it. If you can find someone that has your phone with stock firmware who is willing to do a little work, I'll tell them what to do to make it.
Click to expand...
Click to collapse
Am sure 100% the problem is Firmware.
Do you know why because the holder tray for your ZTE Axon 10 Pro 5g in my phone is making for 1 sim like oneplus 7t in t-mobile if you unlocked and change the holder tray to hybrid dual sim it will work

Hello, I tried to use your tools to restore my phone since its on the European version and my sim card doesn't work (its US). The Write Firmware v1.10 to A tells me that COMPort is not found even though I already launched the load programmer script and see a COMPort file in the folder. Any ideas on what I can do? Thank you for your time!

los95 said:
Hello, I tried to use your tools to restore my phone since its on the European version and my sim card doesn't work (its US). The Write Firmware v1.10 to A tells me that COMPort is not found even though I already launched the load programmer script and see a COMPort file in the folder. Any ideas on what I can do? Thank you for your time!
Click to expand...
Click to collapse
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -
Just for example - the script would be located in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"
And the firmware files would be in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"

bobthenormal said:
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -
Just for example - the script would be located in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"
And the firmware files would be in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"
Click to expand...
Click to collapse
Thanks for the response! I will try it on Tuesday as I have finals. Will update to see what happens.

Okay I tried it again with the steps and now its giving me this.
https://pastebin.com/LwbK3vf7
It tells me that it can't find the files even though I have put the folder in that directory. Sorry for being ignorant I thought this wouldn't be too bad since I used to root Samsung devices.
Update:
I downloaded the new version of the edl tools and it still can't find the firmware files. Here is the log.
https://pastebin.com/LRuXEx0y
Another Update:
Sorry for the updates just wanted to see if I can fix it but I figured out why it didn't find the files.
For some reason, it would try to find the files inside the Firmware_Package_Restore instead of its own folder.
Now, I am getting another error that is says that my device is not on the port although I put it in edl mode. Perhaps I am doing something wrong? Here is another log with this error.
https://pastebin.com/ZtXwhUB0

los95 said:
Okay I tried it again with the steps and now its giving me this.
https://pastebin.com/LwbK3vf7
It tells me that it can't find the files even though I have put the folder in that directory. Sorry for being ignorant I thought this wouldn't be too bad since I used to root Samsung devices.
Update:
I downloaded the new version of the edl tools and it still can't find the firmware files. Here is the log.
https://pastebin.com/LRuXEx0y
Another Update:
Sorry for the updates just wanted to see if I can fix it but I figured out why it didn't find the files.
For some reason, it would try to find the files inside the Firmware_Package_Restore instead of its own folder.
View attachment 5152479
Now, I am getting another error that is says that my device is not on the port although I put it in edl mode. Perhaps I am doing something wrong? Here is another log with this error.
https://pastebin.com/ZtXwhUB0
Click to expand...
Click to collapse
Hey! Thanks for attaching the log, that was perfect for finding the issue right away. The script is building the search_path incorrectly, here's corrected copies of the scripts. I'll update and re-upload the full firmware zip file as soon as I get a chance, but just replace the ones you have with these.
EDIT: Ah, yes hold on I'll take a look at the second issue. Sorry about that, didn't have a chance to test these.
So, the new problem appears to be something with the COM port communication. I have to get going in a minute but a few suggestions to try:
Reboot your phone into EDL then run the loader/firmware scripts right away. Sometimes the ports kind of time out.
Open Device Manager in windows and open the "Ports" list and make sure you see your phone on there. Edit the COMPort file to have the right one, or delete it to force the script to re-check if it's trying to connect to the wrong one.
Check the drivers - the tools have the stock A2020U drivers included, might need to reinstall them especially if you install drivers for other phones.
See if any of those help, let me know how it goes.

bobthenormal said:
Hey! Thanks for attaching the log, that was perfect for finding the issue right away. The script is building the search_path incorrectly, here's corrected copies of the scripts. I'll update and re-upload the full firmware zip file as soon as I get a chance, but just replace the ones you have with these.
EDIT: Ah, yes hold on I'll take a look at the second issue. Sorry about that, didn't have a chance to test these.
So, the new problem appears to be something with the COM port communication. I have to get going in a minute but a few suggestions to try:
Reboot your phone into EDL then run the loader/firmware scripts right away. Sometimes the ports kind of time out.
Open Device Manager in windows and open the "Ports" list and make sure you see your phone on there. Edit the COMPort file to have the right one, or delete it to force the script to re-check if it's trying to connect to the wrong one.
Check the drivers - the tools have the stock A2020U drivers included, might need to reinstall them especially if you install drivers for other phones.
See if any of those help, let me know how it goes.
Click to expand...
Click to collapse
Thanks I will try this.
Edit:
I ended up deleting the com port file, ran Load Programmer, and the scripted worked. However, when it finished and I go back to boot my phone (I had to use the other edl tool and asked it to unlock the google FRP since I don't know another method to boot it back to normal) it boot back to the old rom it had. Its like it didn't write anything to the phone although the script did show me it was doing its job and end with a success. Any ideas? Here is my phone with the same firmware still installed after using the script.
Update:
I decided to use the write firmware to b instead and now it is American. Thank you for all the hard work I thought I had to carry two phones with me everywhere lol. Now I have another question. When I reboot my phone, a message pops up saying that the phone is unlocked and to either press the power button to pause or continue. I read in the threads that this means that fast boot is disabled. Is there anyway I can get fast boot back?

los95 said:
Thanks I will try this.
Edit:
I ended up deleting the com port file, ran Load Programmer, and the scripted worked. However, when it finished and I go back to boot my phone (I had to use the other edl tool and asked it to unlock the google FRP since I don't know another method to boot it back to normal) it boot back to the old rom it had. Its like it didn't write anything to the phone although the script did show me it was doing its job and end with a success. Any ideas? Here is my phone with the same firmware still installed after using the script.
View attachment 5153355
Update:
I decided to use the write firmware to b instead and now it is American. Thank you for all the hard work I thought I had to carry two phones with me everywhere lol. Now I have another question. When I reboot my phone, a message pops up saying that the phone is unlocked and to either press the power button to pause or continue. I read in the threads that this means that fast boot is disabled. Is there anyway I can get fast boot back?
Click to expand...
Click to collapse
Nice! Super glad that it worked.
That A/B issue is why I considered just making the script automatically install it to both A and B. The only way I can tell which side is booting is to go into fastboot, which I find annoying. But if you install a ROM to A while you're booting from B, you won't see it obviously, so I generally just flash both sides at the same time since I always have full backups of both anyway.
As for that message, it sort-of means fastboot is disabled - it pops up when:
1. the bootloader is unlocked
AND
2. the stock bootloader is installed
So to get rid of the message you can either re-lock the phone OR install Unjustified Dev's patched bootloader. And since the stock bootloader does not have fastboot, the only way to have it is to install the unlocked bootloader.
You can do that either through the old tool ("unlock" the phone again), or through mine by running "write_UD-bootloader.ps1" in the Write_Unlocked_Bootloader_and_FRP folder.

bobthenormal said:
Nice! Super glad that it worked.
That A/B issue is why I considered just making the script automatically install it to both A and B. The only way I can tell which side is booting is to go into fastboot, which I find annoying. But if you install a ROM to A while you're booting from B, you won't see it obviously, so I generally just flash both sides at the same time since I always have full backups of both anyway.
As for that message, it sort-of means fastboot is disabled - it pops up when:
1. the bootloader is unlocked
AND
2. the stock bootloader is installed
So to get rid of the message you can either re-lock the phone OR install Unjustified Dev's patched bootloader. And since the stock bootloader does not have fastboot, the only way to have it is to install the unlocked bootloader.
You can do that either through the old tool ("unlock" the phone again), or through mine by running "write_UD-bootloader.ps1" in the Write_Unlocked_Bootloader_and_FRP folder.
Click to expand...
Click to collapse
Thanks for the great help. Now I have installed twrp and will most likely just put magisk and keep the stock rom as I am now terrified on installing a custom rom since it lead to me to a lot of trouble. Maybe I will touch lineage later on but for now I will just have twrp and root.

los95 said:
Thanks for the great help. Now I have installed twrp and will most likely just put magisk and keep the stock rom as I am now terrified on installing a custom rom since it lead to me to a lot of trouble. Maybe I will touch lineage later on but for now I will just have twrp and root.
Click to expand...
Click to collapse
You're welcome!
I wouldn't be afraid of doing custom roms once you do a full backup of your working phone with my tools! If you have the 256gb phone you can add the userdata backup to that and really have everything including settings, apps, and data. Then if anything goes wrong you just do a full restore back to exactly where you were.
I haven't been trying custom ROMs because I just don't have the hours to spend trying them out and re-configuring each one to find out which I want to use, otherwise I definitely would. The stock ROM is really kinda poop (I'm on A10).
Also, if you try flashing a custom ROM and it doesn't boot after you install it - before assuming it didn't work and restoring, FIRST try the "Fix bootable" tool. Some ROMs get installed to a different partition than they were made from, so they have that flag for which partition they think they are installed on. When it doesn't match it won't boot. Good luck!

bobthenormal said:
You're welcome!
I wouldn't be afraid of doing custom roms once you do a full backup of your working phone with my tools! If you have the 256gb phone you can add the userdata backup to that and really have everything including settings, apps, and data. Then if anything goes wrong you just do a full restore back to exactly where you were.
I haven't been trying custom ROMs because I just don't have the hours to spend trying them out and re-configuring each one to find out which I want to use, otherwise I definitely would. The stock ROM is really kinda poop (I'm on A10).
Also, if you try flashing a custom ROM and it doesn't boot after you install it - before assuming it didn't work and restoring, FIRST try the "Fix bootable" tool. Some ROMs get installed to a different partition than they were made from, so they have that flag for which partition they think they are installed on. When it doesn't match it won't boot. Good luck!
Click to expand...
Click to collapse
Thanks for the tip! I forgot to mention something strange about the reset from edl tool. When I was turning my phone back to American, I tried to use that and it gave me an error saying this
{ERROR: Command line argument 'reset=' is not recognized as a valid option}
On the shell window it shows different options and there is one that says reset but without = sign. I'm not sure if its some typo but wanted to let you know.

los95 said:
Thanks for the tip! I forgot to mention something strange about the reset from edl tool. When I was turning my phone back to American, I tried to use that and it gave me an error saying this
{ERROR: Command line argument 'reset=' is not recognized as a valid option}
On the shell window it shows different options and there is one that says reset but without = sign. I'm not sure if its some typo but wanted to let you know.
Click to expand...
Click to collapse
Ah that is weird! I must have forgot to save some changes to that script, it's supposed to use the XML file. Fixed that and threw on a script with a long delay ( version 1.1d now)
Thanks for pointing that out.. my quality control guy is slacking! (I'm the quality control guy...)
Lemme know if you find any other ones.

bobthenormal said:
Ah that is weird! I must have forgot to save some changes to that script, it's supposed to use the XML file. Fixed that and threw on a script with a long delay ( version 1.1d now)
Thanks for pointing that out.. my quality control guy is slacking! (I'm the quality control guy...)
Lemme know if you find any other ones.
Click to expand...
Click to collapse
Sorry for all the replies I just want to be sure everything is fine with the backup tool. I did the full back up and it looks like it worked but I was getting warnings that the files it was looking for returned as null. Is that supposed to happen? Here is the link with the log.
backup_all log - Pastebin.com

los95 said:
Sorry for all the replies I just want to be sure everything is fine with the backup tool. I did the full back up and it looks like it worked but I was getting warnings that the files it was looking for returned as null. Is that supposed to happen? Here is the link with the log.
backup_all log - Pastebin.com
Click to expand...
Click to collapse
Oh whew, you scared me if there was a problem with backup_all
That's the one I was especially careful about since I got burned by the original EDL backup tool.
No worries about bringing up potential issues, I can't guarantee the tools don't mess up anyone's phone but I'd still feel terrible if they did so I appreciate the "bug testing".
The warnings there are all good even though they look scary.
If you look in the log, you see the files are attempt to read (and returned NULL) first, then once it has gone through all of them it repeats the list. The way the EDL interface works is kind of odd. It doesn't take a "read" command, it takes a "write" command "reversed", so it executes it like a write command sort of. That means it looks for the files to "write" first to prepare, even though it doesn't actually use them (except to overwrite them if they do exist).
It makes sense from a programming perspective, efficient and saves ROM.

Hi, I am back again. Magisk had an update and after it was installed, the phone wouldn't boot up anymore. It just stayed at the bootloader and I had to wipe it and installed the original firmware as for some unknown reason, my backup is not there. I tried using the restore tool and it couldn't find my back up. I checked the specific files folders to see if the backup was there and nothing was found. The good thing is that the phone can be brought back life even if I have to start fresh ( I don't mind it to be honest since I don't use a lot of apps). This inspired me to install lineage but the link on that thread is broken. Someone asked the OP of the thread about it but I think he hasn't been active for a while. Do you by any chance have the lineage rom file? Sorry for asking but I don't know where to look. Thanks for reading!

los95 said:
Hi, I am back again. Magisk had an update and after it was installed, the phone wouldn't boot up anymore. It just stayed at the bootloader and I had to wipe it and installed the original firmware as for some unknown reason, my backup is not there. I tried using the restore tool and it couldn't find my back up. I checked the specific files folders to see if the backup was there and nothing was found. The good thing is that the phone can be brought back life even if I have to start fresh ( I don't mind it to be honest since I don't use a lot of apps). This inspired me to install lineage but the link on that thread is broken. Someone asked the OP of the thread about it but I think he hasn't been active for a while. Do you by any chance have the lineage rom file? Sorry for asking but I don't know where to look. Thanks for reading!
Click to expand...
Click to collapse
Damn that's not good. You checked in the Backup tool folder for the backups?
They would be named "backup_all-critical-(date/time)" and "backup_all-non-critical-(date/time)"
The Restore tool doesn't automatically try to find backups, you have to move the backup files you want to restore into the restore directories (critical to critical, non-critical to non-critical).
It's not super user friendly, but it's a ton of extra work to make it search for backups and pop up a menu and such. Hopefully that's the issue, but if not I'd like to know if you figure out why the backups aren't there.
I *think* I have the lineage ROM... but I can't upload it right now, on slow internet! Might be a few weeks before I get back, if rafy hasn't uploaded it by then I'll upload it.
Also, the magisk update - I've had that happen on several phones too where it tries to update itself and bricks, so I'm really careful about when I do updates. Not sure if there's a safe method, maybe uninstalling magisk and reinstalling the new version.

.

MediaPad M3 UN-BRICK, RESTORE, ROLLBACK and RESCUE for BTV variants.

Here is a collection of files for the BTV-W09, BTV-DL09 and BTV-L0j. They are somewhat organized and contain firmware, board software, roll back packages with instructions and a poor quality un-edited video of how to flash with IDT successfully. The image for test point location is good for w09 and dl09. I don't know if they are the same on the l0j from Japan or not. Should you truly need a file for the BTV variants of the M3, leave a reply to let me know what it is and I'll see what I can do.
DISCLAMER:
There are other Huawei firmware and board software within this thread. Any use of them is at your own risk, although if you're here you've already screwed something up, whether you believe yourself to be at fault or not.
Flashing board software is a last resort and should not be done unless all other methods have been exhausted. Only flash board software when there are no other alternatives.
https://www.mediafire.com/folder/43cwcl8hih2u2/MediaPad_M3_(BTV-W09,L0J,DL09)
BTV-W09 Stock Firmware
https://drive.google.com/file/d/16UhYMILV83C6MwdVqmwYKDf0JA6LOAV5/view?usp=sharing
https://drive.google.com/file/d/1g7-rNMGzIRCpKelj2GNdPvhORAmC3z8R/view?usp=sharing
https://drive.google.com/file/d/1oAwRv3F08SnAhpkBXw4m_elVhmtg3ie2/view?usp=sharing
https://drive.google.com/file/d/17Ck8zaKlqfP4FmJSRUuM8fNUETY-2-sU/view?usp=sharing

Hi! There's any chance something like this for CPN-L09 version? I would be very happy for this, but I think not just me.
Beren

Barahir's son Beren said:
Hi! There's any chance something like this for CPN-L09 version? I would be very happy for this, but I think not just me.
Beren
Click to expand...
Click to collapse
What are you needing ? Board Software I do have for CPN-L09 and can get others.

Barahir's son Beren said:
Hi! There's any chance something like this for CPN-L09 version? I would be very happy for this, but I think not just me.
Beren
Click to expand...
Click to collapse
Here's board software for CPN-L09
CPN-L09C500B028_Board Software_general_7.0.0_r1_EMUI5.1_05022FWM
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

tek3195 said:
Here's board software for CPN-L09
CPN-L09C500B028_Board Software_general_7.0.0_r1_EMUI5.1_05022FWM
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Please, do you have the same files for BAH-AL00/BAH-L09 ?
I have been struggling for a few months to repair my tablet but I didn't find anywhere the right file ( prog_emmc_firehose_8937_ddr.mbn ) for my tablet .
Or I can use the files from CPN-L09 ?
Thank you very very much in advanced !

tek3195, I already tried with CPN files but I have always error with :" Sahara protocol error" , "Uploading Image using Sahara protocol failed" ... I'm using QFIL as administrator with Antivirus disabled & Airplane mode enabled on my laptop and nothing changed about Sahara protocol error, and even I used "emmcdl.exe -p COM5 -f prog_emmc_firehose_8937_ddr.mbn -x rawprogram0.xml" - also without success !
Anyway, I think the battery is close to 0 and there are very poor chances to repair it.

tek3195 said:
What are you needing ? Board Software I do have for CPN-L09 and can get others.
Click to expand...
Click to collapse
Hi!
Thanks for your quick reply. I need a working solution to take back to factory firmware. I tried it many times, but I haven't succeeded, I always got a recovery screen or bootloop. Is it possible with your files and method?
Beren

Barahir's son Beren said:
Hi!
Thanks for your quick reply. I need a working solution to take back to factory firmware. I tried it many times, but I haven't succeeded, I always got a recovery screen or bootloop. Is it possible with your files and method?
Beren
Click to expand...
Click to collapse
Sure, you have all what you need there, just use Qualcomm Flash Image Loader ( QFIL Tool )

surdu_petru said:
Please, do you have the same files for BAH-AL00/BAH-L09 ?
I have been struggling for a few months to repair my tablet but I didn't find anywhere the right file ( prog_emmc_firehose_8937_ddr.mbn ) for my tablet .
Or I can use the files from CPN-L09 ?
Thank you very very much in advanced !
Click to expand...
Click to collapse
I wouldn't try cpn on bah, even with same firehose loader it shouldnt work.If it did flash it may make a hard to recover brick.
I can get BAH2-AL00 or BAH-L09. Which one would you like ? I can't find one for BAH-AL00

surdu_petru said:
tek3195, I already tried with CPN files but I have always error with :" Sahara protocol error" , "Uploading Image using Sahara protocol failed" ... I'm using QFIL as administrator with Antivirus disabled & Airplane mode enabled on my laptop and nothing changed about Sahara protocol error, and even I used "emmcdl.exe -p COM5 -f prog_emmc_firehose_8937_ddr.mbn -x rawprogram0.xml" - also without success !
Anyway, I think the battery is close to 0 and there are very poor chances to repair it.
Click to expand...
Click to collapse
I haven't flashed qualcomm in a while but the error may be from wrong software if using CPN on a BAH. Anyway, I can get BAH-L09 and Iwill have to dig around and find another tool for flashing Huawei/Qualcomm. I hve it but can't remember the name of it right now. It's a lot simpler than QFIL.

tek3195 said:
I wouldn't try cpn on bah, even with same firehose loader it shouldnt work.If it did flash it may make a hard to recover brick.
I can get BAH2-AL00 or BAH-L09. Which one would you like ? I can't find one for BAH-AL00
Click to expand...
Click to collapse
On the back side of my tablet it has a label and it says BTV-AL00, but on the settings the menu it says BTV-L09 !
Anyway, I guess I can't recover my device as battery seems to be almost empty and when the QFIL start to make some operations, the device seems to turn off frequently ( at least the drivers keep disconnecting and reconnecting itself )
Thank you very much in advanced !
EDIT:
I managed to brick my device by flashed a wrong TZ.img via TWRP !
I know it was stupid of me, but now I have nothing to do with it!

surdu_petru said:
On the back side of my tablet it has a label and it says BTV-AL00, but on the settings the menu it says BTV-L09 !
Anyway, I guess I can't recover my device as battery seems to be almost empty and when the QFIL start to make some operations, the device seems to turn off frequently ( at least the drivers keep disconnecting and reconnecting itself )
Thank you very much in advanced !
EDIT:
I managed to brick my device by flashed a wrong TZ.img via TWRP !
I know it was stupid of me, but now I have nothing to do with it!
Click to expand...
Click to collapse
Is it BAH-L09 or BTV-L09 ? I have bah-l09 uploading now, it has board software and a rollback update.app in it along with other release documentation. I can't remember if the Huawei tool I'm looking for needs battery or not. Seems like it flashes without it.

I really don't know if it's Al00 or L09 .... as I said on the back it has a label with BAH-AL00 and something written in Chinese but the getprop it say : BAH-L09 !
Also it's working with kernel compiled from Huawei BAH-L09 source code ... but this it's not so relevant as also CPN devices are working with BAH-L09 source code !
EDIT :
Yes, we talk about Huawei MediaPad M3 Lite 10 / BAH-L09 !

@surdu_petru here is folder with board software and tools for BAH-L09. Still haven't found the other tool I was looking for.

Ok, I'll try right now, Thanks !

tek3195
Thank you very much for your help! Unfortunately, for unknown reasons my device can't stay connected on edl mode - so there is no way to flash something via edl mode !
Tthe device seems to communicate successfully only immediately after it has been connected via usb - in edl mode ... unfortunately, a few seconds later the device can no longer be detected !
Tested with : "emmcdl -p COM15 -info'' - and working only one time ( as soon as the device has been connected ) - and if I tried the same command for the second time, there is no device detected like into the picture !
{
"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"
}

surdu_petru said:
tek3195
Thank you very much for your help! Unfortunately, for unknown reasons my device can't stay connected on edl mode - so there is no way to flash something via edl mode !
Tthe device seems to communicate successfully only immediately after it has been connected via usb - in edl mode ... unfortunately, a few seconds later the device can no longer be detected !
Tested with : "emmcdl -p COM15 -info'' - and working only one time ( as soon as the device has been connected ) - and if I tried the same command for the second time, there is no device detected like into the picture !
Click to expand...
Click to collapse
It looks like it is still connected and recognized in 9008 mode even after invalid handle status. Different software to flash it with would be my thought. I am not very well versed in Windows and have a Sigma Key Huawei Edition that takes the hard work out of most issues like this one. However, there are free software that will fix it I believe, it's just a matter of finding the right one and then a version of it thst supports msm8937. QPST or QFIL that I see in background I have never had any luck with other than one Lenovo tablet. I will look for the one tool that I have had good luck with in the past. I can't remember the name but I will know it when I see it.

tek3195 said:
It looks like it is still connected and recognized in 9008 mode even after invalid handle status. Different software to flash it with would be my thought. I am not very well versed in Windows and have a Sigma Key Huawei Edition that takes the hard work out of most issues like this one. However, there are free software that will fix it I believe, it's just a matter of finding the right one and then a version of it thst supports msm8937. QPST or QFIL that I see in background I have never had any luck with other than one Lenovo tablet. I will look for the one tool that I have had good luck with in the past. I can't remember the name but I will know it when I see it.
Click to expand...
Click to collapse
It will be awesome if you can get me the right tool for flash, as I already tried a lot of tools and non working, thanks !

@surdu_petru here is the one that I have had best luck with. There should be a "how to use" file with it.
https://www.mediafire.com/file/w8ql6u0ue2usb7e/Huiye_Download_Tool_v2.2.zip/file

tek3195 said:
@surdu_petru here is the one that I have had best luck with. There should be a "how to use" file with it.
https://www.mediafire.com/file/w8ql6u0ue2usb7e/Huiye_Download_Tool_v2.2.zip/file
Click to expand...
Click to collapse
Thank you very much for your help.
I guess that I have the same connectivity issues also with this Tool :

Help needed, 'Your device has failed a routine safety check and will not boot.' after relocking BL

Hello everyone,
so I'll try and explain step by step what I, inexperienced guy, did, because from what I see I did absolutely everything to brick my V40... BUT maybe someone know what can I do to avoid having beautiful red paperweight.
I wanted to get HavocOS 3.5 on my phone. Until today I had stock Android 10, flashed by LGUP.
So in order to get the Havoc, I unlocked the bootloader the official way, thru LG developers site. Then I tried to get TWRP working and it might be the problem (more on that later). So, in order to get TWRP one of the steps was to fastboot boot TWRP-judypn-boot.img. I did that but didn't know that to do next (cause when I did it the phone booted normally and I didn't fully understood what now), so I abandoned the idea and just loaded the backup from LG Mobile Switch. But, then I realized that with having unlocked bootloader I won't be able to use google pay, so after some reading I found out that Magisk might be the answer (it wasn't) so I managed to get Magisk root on my device. When I found out that it didn't help with google pay i tried to do what others on forum warned me not to - RElock the bootloader using 'fastboot oem lock'. And now it has locked bootloader. But also now of course the phone is rather bricked in a way that: I can enter both fastboot mode and download mode but: trying fastboot something I get the info that it is not possible in Lock State, and when trying to just flash kdz of that stock android 10 that I started with, the LGUP says error 'error 0x6004 crossDL' and below that it mentions 'judypn_lao_eea>@judypn_lao_co' so probably that first fastbooted img now prevents it from beign flashed. So now I cannot fastboot or flash anything, and trying to boot the phone gives me error "Your device has failed a routine safety check and will not boot." and also sometimes, below 'All slots are unbootable'.
I know that I screw up multiple times, first time not recognizing that unlocking BL would cut off a function crucial for me, but is there a way to fix all this?

AnDevil said:
Hello everyone,
so I'll try and explain step by step what I, inexperienced guy, did, because from what I see I did absolutely everything to brick my V40... BUT maybe someone know what can I do to avoid having beautiful red paperweight.
I wanted to get HavocOS 3.5 on my phone. Until today I had stock Android 10, flashed by LGUP.
So in order to get the Havoc, I unlocked the bootloader the official way, thru L<brevity>imes, first time not recognizing that unlocking BL would cut off a function crucial for me, but is there a way to fix all this?
Click to expand...
Click to collapse
Sounds kind of messy. Two things to know; 1) u most certainly can have google pay working on v40 w/10. I just added it on my (orig at&t) korean 10 30e / rooted / magisk / twrp. And 2) u should never ever try to relock the bootloader unless you just flashed a stock kdz to the device (completely unmodified, don't even choose language when it boots).
So the prob is what to do now. I'd first try to use fastboot to switch slots and see if the other side boots? And if that doesn't work / achieve what you want, then use lgup with dll version 1.14 to do the 'cross flash' (the 1.16 version doesn't work for that). Be sure to do a part DL (if u do the crossflash), then do a refurbish with the same kdz just after the part DL (of course you let the part DL complete, just shut it off after it boots all the way), then do refurb.
Ideally, what are u trying to accomplish?
cheers

Well, for now I would want to have bootloader locked, stock Android 10 on there. I'm probably going to leave the modding cause of the mess I've made - especially that I don't have much free time to tinker with phone when things go bad (and also as You can see I don't have enough experience to do so).
Right, so back to the point. How do you switch slots in fastboot? If by 'fastboot set_active a' (or b), then the result is 'not possible in lock state'. And for the other part (with LGUP and crossflashing), can You provide some kind of idiot-proof tutorial for that? Which files should I download and try to flash on the phone?

OK, i *think* that I partly know what to do. Unlike You wrote, the 1.14 LGUP doesn't let me do anything with phone, saying that it needs at least 1.16 to work. When I downloaded 1.16 (the one with which I flashed the android 10 back in september, from the topic https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/unread) I click on the 'PARTITION DL' option and after 4% it asks me to select a partition. And here I don't know that to select, because there are so many options and I'm afraid to move with any of them to not screw things up even more.
Oh, and the file which I try to flash is stock european android 10, 30b.

AnDevil said:
OK, i *think* that I partly know what to do. Unlike You wrote, the 1.14 LGUP doesn't let me do anything with phone, saying that it needs at least 1.16 to work. When I downloaded 1.16 (the one with which I flashed the android 10 back in september, from the topic https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/unread) I click on the 'PARTITION DL' option and after 4% it asks me to select a partition. And here I don't know that to select, because there are so many options and I'm afraid to move with any of them to not screw things up even more.
Oh, and the file which I try to flash is stock european android 10, 30b.
Click to expand...
Click to collapse
Okay, just so that it's clear, you do want to use 1.14 when going from 8 or 9 to 10. 1.16 won't recognize the older OS.
But, if you'd have done 1.16 Part DL from the beginning, it would have worked, as you've discovered. When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them).
Because you want to flash ebw 30b, there shouldn't be any reason to select all partitions. But I'd suggest (again), after doing the part DL, let the phone reboot of course, to complete. Then just shut it off and go back to LGUP and do a refurbish this time of the exact same kdz.
good luck

Ok, now I'm confused
I always used the 1.16, never the 1.14. And before I had tinker with phone I already had Android 10 installed (which I installed via 1.16). I Think that someone made a patch for 1.16 to work with Android 9 when I made that transition.
Ok so You wrote that
"When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them)"
and below that You wrote
"there shouldn't be any reason to select all partitions"
so that part I don't understand.
Is it:
1. Connect phone in download mode to LGUP 1.16
2. Choose 'partition DL' And select all of them
3. Let it finish and the phone will reboot
4. Right when it boots to welcome screen shut it off
5. Enter download mode once again
6. Flash with 'refurbish' the 30b software
Are these steps correct?

AnDevil said:
Ok, now I'm confused
I always used the 1.16, never the 1.14. And before I had tinker with phone I already had Android 10 installed (which I installed via 1.16). I Think that someone made a patch for 1.16 to work with Android 9 when I made that transition.
Ok so You wrote that
"When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them)"
and below that You wrote
"there shouldn't be any reason to select all partitions"
so that part I don't understand.
Is it:
1. Connect phone in download mode to LGUP 1.16
2. Choose 'partition DL' And select all of them
3. Let it finish and the phone will reboot
4. Right when it boots to welcome screen shut it off
5. Enter download mode once again
6. Flash with 'refurbish' the 30b software
Are these steps correct?
Click to expand...
Click to collapse
Sorry yes, that should have been 'there shouldn't be any reason NOT to select all partitions' (I think that's what the 'context' of the whole comment implied').
Yes, those steps are correct.
I think the confusion about lgup is around this; 1.14 is used if u need to 'cross flash' (going to diff OS). If you're not cross flashing then 1.16 will work. I think most people are cross flashing due to desire to get rid of bloatware and / or wanting to move to A10 when their OS doesn't have it or the kdz is unavailable.
you are in a somewhat unusual circumstance, having the only version of v40 that lg actually allows legit unlocking. So you never cross flashed (had to re read to realize that, it's that uncommon).
good luck

OK, so unfortunately it didn't help, giving the same error as when I try to 'refurbish'.
{
"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"
}
So it has to do something with me fastbooting the TWRP img (it's indicated by the name of it).
Seems to me that I should change the img for a stock one (if there is one that's stock) but then again, fastboot probably will end in error 'not possible in lock state' as I tried to fastboot other img's and it gave me that error.

AnDevil said:
OK, so unfortunately it didn't help, giving the same error as when I try to 'refurbish'.
View attachment 5190441
So it has to do something with me fastbooting the TWRP img (it's indicated by the name of it).
Seems to me that I should change the img for a stock one (if there is one that's stock) but then again, fastboot probably will end in error 'not possible in lock state' as I tried to fastboot other img's and it gave me that error.
Click to expand...
Click to collapse
So here's what I'd suggest, because you have an ebw version, which I believe has dual sim, and many many have had issues with those and losing the dual sim capability (very frustrating and difficult to get back).
Go to the v40 rom forum and Markus (los developer), put in the first post of his lineage rom an invite to the lgv40 tele gram group. Use that and join tele group and there are a lot of international users there, they can guide you with this problem (they have and use that specific device, among others).
If you want to do more reading on this, follow this link. It's the lg firmware dl page and do a search from the top for 'judy'. You'll see others have had the same error you're getting, and used lgup 1.15 command line to get around it.
I don't think it's because of what u flashed with fastboot (twrp), judypn is the name of the device, not specific to twrp.
So join the tele group and also (here on xda) look in the thread about 'unlocking all devices - except t-mo'. Not to unlock it, but to learn to use qfil. You will probably need that.
cheers

Ok, definitely will do that. Thank You very much for Your help