Related
Hello! I am Ukrainian, and my level of English is quite low.
I have a VK810 in the "brick" in the OS is seen as RELINK HS-USB QDLoader 9008
I read the manual how to do "unbrick" and I need a file * .tot for the VK810.
Someone can help me with this problem?
P.S. for a more correct spelling, I use Google translator.
Hi! Sorry to say I haven't found a TOT file for the VK810, only KDZs. When I used intense Googling, I found a website where someone was offering to sell a TOT file for the VK810 for $500, which is crazy. If I ever come across a TOT, I'll post it in these sections - probably add it to my KDZ, IMG and OTA thread in my signature below.
Edit: Maybe it's only $10 for the TOT, and another $10 for the VK810 .DLL - which might be the same DLL as what comes with the KDZs. I've also heard that at least on the VS985 G3, there's such a thing as a generic DLL, which might be necessary for a device that no longer knows what device it is. Here's the link/site: http://www.lgbbs.com:41/thread-838-1-1.html. If posting this is against XDA rules, let me know and I'll take it down. Hmmmm.....
They also supposedly have the service manual for the VK810.
Edit 2: @autoprime says the site is legit, even if ethically questionable: http://forum.xda-developers.com/showpost.php?p=50224097&postcount=128
Hi! I know for this site, but the price of the file is too big. Perhaps someone this file is in the public domain and he will share with everyone, because this problem can happen to everyone.
VEZU4IJ said:
Hi! I know for this site, but the price of the file is too big. Perhaps someone this file is in the public domain and he will share with everyone, because this problem can happen to everyone.
Click to expand...
Click to collapse
According to that site, only one person has paid for to get that file. All my Google efforts couldn't find a TOT anywhere else. If anyone else does have the TOT, or even the one person who bought it on that site, there's unfortunately not a large chance that they'll both be on XDA and come across your question.
Sorry mate.
Hi everyone
i want to know what's the differnet between RELINK HS-USB QDLoader 9008 and Qualcomm HS-USB QDLoader 9008 ?
i have same problem for my LG G3 D850 :crying:
thanks for advence :good::good:
khalidou
Have u found the difference? I have the same issue here
stigmata4 said:
khalidou
Have u found the difference? I have the same issue here
Click to expand...
Click to collapse
no bro
still my LG G3 dead
khalidou said:
no bro
still my LG G3 dead
Click to expand...
Click to collapse
Sorry for that. I wish u lucky.
I'll send mine for warranty...
roirraW "edor" ehT said:
Hi! Sorry to say I haven't found a TOT file for the VK810, only KDZs. When I used intense Googling, I found a website where someone was offering to sell a TOT file for the VK810 for $500, which is crazy. If I ever come across a TOT, I'll post it in these sections - probably add it to my KDZ, IMG and OTA thread in my signature below.
Edit: Maybe it's only $10 for the TOT, and another $10 for the VK810 .DLL - which might be the same DLL as what comes with the KDZs. I've also heard that at least on the VS985 G3, there's such a thing as a generic DLL, which might be necessary for a device that no longer knows what device it is. Here's the link/site: http://www.lgbbs.com:41/thread-838-1-1.html. If posting this is against XDA rules, let me know and I'll take it down. Hmmmm.....
They also supposedly have the service manual for the VK810.
Edit 2: @autoprime says the site is legit, even if ethically questionable: http://forum.xda-developers.com/showpost.php?p=50224097&postcount=128
Click to expand...
Click to collapse
My pad now stuck at Download logo/mod . I already tried the lg flash tool 2014 and the offical LG Mobile tool. Both programs recognize the tab but unable to flash the file ( got disconnection error ) . Any idea ? TIA
The only resort left is the TOT method, but I am not sure it will work and i gotta spend $20 for the TOT and DLL file
abced123 said:
My pad now stuck at Download logo/mod . I already tried the lg flash tool 2014 and the offical LG Mobile tool. Both programs recognize the tab but unable to flash the file ( got disconnection error ) . Any idea ? TIA
The only resort left is the TOT method, but I am not sure it will work and i gotta spend $20 for the TOT and DLL file
Click to expand...
Click to collapse
If it doesn't work with LG Flash Tool 2014, you'd probably have the same trouble with the TOT, but that's just my guess.
Did you reboot your PC after installing the drivers (with the tablet disconnected)? Using the original USB cable and with a USB 2.0 port on the PC? Try a different USB 2.0 port? The first time you connect it to a different USB 2.0 port, it'll re-load the driver you previously installed so make sure and keep checking in Device Manager for when the driver is actually finished loading. Can take up to 10 minutes.
If those don't solve it, trying a different PC sometimes makes the difference. What version of Windows are you running?
Good luck!
VEZU4IJ said:
Hello! I am Ukrainian, and my level of English is quite low.
I have a VK810 in the "brick" in the OS is seen as RELINK HS-USB QDLoader 9008
I read the manual how to do "unbrick" and I need a file * .tot for the VK810.
Someone can help me with this problem?
P.S. for a more correct spelling, I use Google translator.
Click to expand...
Click to collapse
Could you revive your device? I need help with the same.
Tks.
Hi,
I got a G4 H815 from a friend. He tried to install a custom firmware and killed the G4.
I see the G4 in the device manager as a qualcomm HS-USB QDloader 9008, but nothing more.
With the LGFlash Tool: It will transfer the files, but after 8 seconds it fails caus of missing download mode.
With LGUP, after I changed the driver to an LG USB COM Port, it connected but at Model: Unknown model. And stopped
I think, I have to install first a bootloader on the device, but how?
Someone can help pls?
midwayhero said:
Hi,
I got a G4 H815 from a friend. He tried to install a custom firmware and killed the G4.
I see the G4 in the device manager as a qualcomm HS-USB QDloader 9008, but nothing more.
With the LGFlash Tool: It will transfer the files, but after 8 seconds it fails caus of missing download modus.
With LGUP, after I changed the driver to an LG USB COM Port, it connected but at Model: Unknown model. And stopped
I think, I have to install first a bootloader on the device, but how?
Someone can help pls?
Click to expand...
Click to collapse
1) Did you put your phone in download mode before using LGUP?
2) You can install custom recovery using adb commands if your bootloader is unlocked.
rlamba said:
1) Did you put your phone in download mode before using LGUP?
2) You can install custom recovery using adb commands if your bootloader is unlocked.
Click to expand...
Click to collapse
The problem is: It´s dead!
no bootloader, no download mode, no recovery...
The phone is clean.
That´s the big issue.
There is one solution I read with a dump/bin file here at xda...
But I don´t know if it is the right file for the 815, it says yes but...
My plan is, to dump a file via SD-Card to activate the download mode. But I need someone who can say to me " Thats the way, and these are the files you need to"
midwayhero said:
The problem is: It´s dead!
no bootloader, no download mode, no recovery...
The phone is clean.
That´s the big issue.
There is one solution I read with a dump/bin file here at xda...
But I don´t know if it is the right file for the 815, it says yes but...
My plan is, to dump a file via SD-Card to activate the download mode. But I need someone who can say to me " Thats the way, and these are the files you need to"
Click to expand...
Click to collapse
Well for H815 we cant assure SD card will work
The only way is via Medusa pro Emmc repair if you need help pm me maybe i may help you[emoji4]
midwayhero said:
The problem is: It´s dead!
no bootloader, no download mode, no recovery...
The phone is clean.
That´s the big issue.
There is one solution I read with a dump/bin file here at xda...
But I don´t know if it is the right file for the 815, it says yes but...
My plan is, to dump a file via SD-Card to activate the download mode. But I need someone who can say to me " Thats the way, and these are the files you need to"
Click to expand...
Click to collapse
Try this dump!
It worked for me
dev8987.tiwari said:
Well for H815 we cant assure SD card will work
The only way is via Medusa pro Emmc repair if you need help pm me maybe i may help you[emoji4]
Click to expand...
Click to collapse
Thanks a lot, I will come back to your offer. Just wanna give the SD-Card solution one chance
-gloim- said:
Try this dump!
It worked for me
Click to expand...
Click to collapse
Thanks, you got a PM
Hello, Iam having a bricked Google Pixel XL 128GB with black screen, no fastboot, no recovery(phone only detected as HS-USB QDLoader 9008).
Is there anyway to unbrick the phone?
What was your setup before this happened? What were you trying to do before this happened?
chapelfreak said:
What was your setup before this happened? What were you trying to do before this happened?
Click to expand...
Click to collapse
Bad Flash on OTA update
Hey... Actually, there's no easy way to get the pixel back up and running. I tried to read a bit about the issue on different phones. I'm not sure it could be of some use for our device.. It also involves, either having someone to pull a full backup of his phone for you which you'll have to find... Or finding special Qualcomm files and firmware used for flashing using Qualcomm tool QFIL... I haven't found Qualcomm files/firmware on the internet yet... And i'm not 100% sure the first solution would work either, since we have now different system partitions.
If you don't have any warranty on your phone, you could try it. Otherwise, send it back. There's likely no way to recover personnal datas anyway...
Also about getting out of EDL mode, i've read in the N6P forum, someone saying you'll have to push the power button for no less than 40 seconds. Try it maybe and try to reboot into bootloader afterward...
Good luck...
5.1 said:
Hey... Actually, there's no easy way to get the pixel back up and running. I tried to read a bit about the issue on different phones. I'm not sure it could be of some use for our device.. It also involves, either having someone to pull a full backup of his phone for you which you'll have to find... Or finding special Qualcomm files and firmware used for flashing using Qualcomm tool QFIL... I haven't found Qualcomm files/firmware on the internet yet... And i'm not 100% sure the first solution would work either, since we have now different system partitions.
If you don't have any warranty on your phone, you could try it. Otherwise, send it back. There's likely no way to recover personnal datas anyway...
Also about getting out of EDL mode, i've read in the N6P forum, someone saying you'll have to push the power button for no less than 40 seconds. Try it maybe and try to reboot into bootloader afterward...
Good luck...
Click to expand...
Click to collapse
I tried QFIL, MSMToolDownloader(from OnePlus 3T), MiFlash, etc. They all ask RawProgramm0.xml, Patch0.xml, MSM8996..mbn, and xxx_firehose_emmc_8996.xxx specifically for our Google Pixel XL 128GB. None of them are available yet.
droidan said:
I tried QFIL, MSMToolDownloader(from OnePlus 3T), MiFlash, etc. They all ask RawProgramm0.xml, Patch0.xml, MSM8996..mbn, and xxx_firehose_emmc_8996.xxx specifically for our Google Pixel XL 128GB. None of them are available yet.
Click to expand...
Click to collapse
Yeah I haven't found anything either. I think it will take some time before someone share those.
Check this thread:
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This part:
2. REVIVING YOUR YU BACK
2.a NEW "Qualcomm HS-USB QDLoader 9008" MODE
As I said earlier, since our phone has a different partition layout, I don't know if the same process can be achieved. Also you'll have to pull the IMG from a working device.
You don't have a valid warranty?
5.1 said:
Yeah I haven't found anything either. I think it will take some time before someone share those.
Check this thread:
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This part:
2. REVIVING YOUR YU BACK
2.a NEW "Qualcomm HS-USB QDLoader 9008" MODE
As I said earlier, since our phone has a different partition layout, I don't know if the same process can be achieved. Also you'll have to pull the IMG from a working device.
You don't have a valid warranty?
Click to expand...
Click to collapse
Thank you for your reply and information.
I believe I have an OLD 9008 mode.
Here's what I have found:
1. The 8996 firehose is specific to the device. Other 8996 version do not work. (Oneplus 3T, ZUK, Xiaomi, LEECO)
2. Quote from Ghassani on Le Pro3 bricked thread:
"Since it was suggested to contact me about this issue, I am going to answer here what I told the OP through email:
This is a hard brick. Meaning, you probably flashed a wrong SBL partition, or you flashed in the wrong order, or in the wrong mode.
When this happens, and the device has secure boot enabled (which all production devices do) you only have two options:
1) Using a signed recovery programmer to send via emergency mode (Sahara mode), then transferring to that programmers protocol (streaming DLOAD or the newer firehose). From there you can recover the emmc.
2) JTAG on the emmc for direct recovery.
It is easy to find these programmer files, both signed and unsigned. The problem is each device is using a different private key generated by the OEM to build the SoC. Without a properly signed programmer, Sahara will reject the programmer and go into a no-interrupt loop until you power cycle the device. Pretty much all OEMs do not give out these files. The ones you can find floating around for various devices are generally leaked, or rarely given out by the OEM. For most devices, JTAG is the only option.
I have a small collection of both signed and unsigned programmer files on this github repository:
https://github.com/ghassani/openpst-assets
If anyone has properly signed files for devices I do not have, please send them in to me and I can add them or you can put in a pull request directly to the repository and add it that way."
Hopefully someone from Google/HTC can share those 3 files.(eMMc_firehose_8996.elf, rawprogram0.xml and patch0.xml for Google Pixel XL 128GB)
Or maybe I can ask Google assistant to leak the files..lol
droidan said:
Bad Flash on OTA update
Click to expand...
Click to collapse
What does that mean? Were you rooted, unlocked? If so return the device, no?
droidan said:
I tried QFIL, MSMToolDownloader(from OnePlus 3T), MiFlash, etc. They all ask RawProgramm0.xml, Patch0.xml, MSM8996..mbn, and xxx_firehose_emmc_8996.xxx specifically for our Google Pixel XL 128GB. None of them are available yet.
Click to expand...
Click to collapse
Sent from my Pixel using XDA-Developers Legacy app
droidan said:
Thank you for your reply and information.
I believe I have an OLD 9008 mode.
Here's what I have found:
1. The 8996 firehose is specific to the device. Other 8996 version do not work. (Oneplus 3T, ZUK, Xiaomi, LEECO)
2. Quote from Ghassani on Le Pro3 bricked thread:
"Since it was suggested to contact me about this issue, I am going to answer here what I told the OP through email:
This is a hard brick. Meaning, you probably flashed a wrong SBL partition, or you flashed in the wrong order, or in the wrong mode.
When this happens, and the device has secure boot enabled (which all production devices do) you only have two options:
1) Using a signed recovery programmer to send via emergency mode (Sahara mode), then transferring to that programmers protocol (streaming DLOAD or the newer firehose). From there you can recover the emmc.
2) JTAG on the emmc for direct recovery.
It is easy to find these programmer files, both signed and unsigned. The problem is each device is using a different private key generated by the OEM to build the SoC. Without a properly signed programmer, Sahara will reject the programmer and go into a no-interrupt loop until you power cycle the device. Pretty much all OEMs do not give out these files. The ones you can find floating around for various devices are generally leaked, or rarely given out by the OEM. For most devices, JTAG is the only option.
I have a small collection of both signed and unsigned programmer files on this github repository:
https://github.com/ghassani/openpst-assets
If anyone has properly signed files for devices I do not have, please send them in to me and I can add them or you can put in a pull request directly to the repository and add it that way."
Hopefully someone from Google/HTC can share those 3 files.(eMMc_firehose_8996.elf, rawprogram0.xml and patch0.xml for Google Pixel XL 128GB)
Or maybe I can ask Google assistant to leak the files..lol
Click to expand...
Click to collapse
Yeah, unless someone leaks official programmer, you are SOL...
Good luck... :good:
Hi guys,
I've opened a similar thread on google forum - related to pixel 128gb being bricked and in chipset download mode.
If there are enough bricked pixels out there perhaps google will (hopefully) share those files?
Cheers,
Dan
The deluge of bricked Pixels resulting from the Oreo update continues...
I did, however, find these pages posted in the last couple weeks, and wondering if they're the answer to the Q's posted earlier ITT (sry I'm too new to post live links, so you'll have to paste these):
- androidauthority.com/download-android-8-0-oreo-794622/
- androidauthority.com/install-android-oreo-758342/
- developers.google.com/android/ota
Earlier ITT, posters were saying that they couldn't find the firmware or other files that would allow someone to recover from the hard-bricked state...but are those 'official' factory images and OTAs what they were saying they needed, but which they couldn't find at the time? In short, might we now actually have the files necessary to save our bricked Pixels without engaging in Macguyvering that would void the warranty?
Out of curiosity, was your bootloader locked prior to running into this issue?
Pain-N-Panic said:
Out of curiosity, was your bootloader locked prior to running into this issue?
Click to expand...
Click to collapse
I assume so...I bought the Pixel directly from Google, so assumed I was getting the purest Android installation possible / no provider bloatware etc...if i'm not mistaken, the bootloader would have been Locked when I initially received the phone, right?...if so, then yes it would still have been locked when it bricked, as I didn't take any actions to unlock it (nor would i know how)
hopefully files will be shared soon for sure it is exists
I have the same problem and all I can do is rma.
Is it possible to pull the files from a working pixel?
I wonder if the files in question would hold the key to VZW Pixel XL customers to somehow use /find an exploit to gain temp root to ultimately unlock their bootloader.
mattwheat said:
I wonder if the files in question would hold the key to VZW Pixel XL customers to somehow use /find an exploit to gain temp root to ultimately unlock their bootloader.
Click to expand...
Click to collapse
Maybe that's why they aren't giving the files
This happened to mine as well
Went from 8.0 to 8.1 - wiped data and re-locked bootloader. Ran fine for two days then powered down and now I'm in this qualcomm mode. Thankfully I purchased the 2-year through Google. Unfortunately their support is dogsh**.
Update: Ok Google's support rep was actually pretty solid but their system is awful. I'm already on a refurb and it doesn't have the IMEI printed on the sim tray. Either way they worked it out and I'm down $80 for the deductible.
I have the same problem
Dear all, my quick story overwiev:
I have G4 H815 10H
Heat sink upgrade due to bootloop was done week ago and was ok
Wanted make software update to Nougat from 5.1 Lolipop and then some problems comes out
For this puprose wanted gain Root access, so
went through out https://forum.xda-developers.com/g4...t-tmo-vzw-intl-variants-soon-root-lg-t3164765 , but with 1 mistake, I've download T-Mobile H811 10H Version instead of H815 version and run
dd if=/data/media/0/system.rooted.H81110h.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
After this got Security error #11
So went to Stock Frimware flashing KDZ procedure https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
I've decided to flash Europe General H81510B_00.kdz file
but..... now this phone doesn't boot. I can see only Qualcomm hs-usb qdloader 9008 in my device manager.
I know that some of you guys (@TheMadScientist @steadfasterX) are able to unbrick this, really please help.
krzakx said:
Dear all, my quick story overwiev:
I have G4 H815 10H
Heat sink upgrade due to bootloop was done week ago and was ok
went through out https://forum.xda-developers.com/g4...t-tmo-vzw-intl-variants-soon-root-lg-t3164765 , but with 1 mistake, I've download T-Mobile H811 10H Version instead of H815 version and run
dd if=/data/media/0/system.rooted.H81110h.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
So went to Stock Frimware flashing KDZ procedure https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
I've decided to flash Europe General H81510B_00.kdz file
but..... now this phone doesn't boot. I can see only Qualcomm hs-usb qdloader 9008 in my device manager.
I know that some of you guys (@TheMadScientist @steadfasterX) are able to unbrick this, really please help.
Click to expand...
Click to collapse
Well.. You have corrupted the partition table as you used the wrong seek value. The procedure there is EXTREMELY risky and that's one reason why.
You need qfil in that mode. Download this file:
http://droid.binbash.it:8008/unbricking/qfil/h815/G4-h815_fullunbrick_working_7a3ae5809224d.zip
Install qpst and the drivers file from the software folder and after that start qfil. Select the prog_emmc_firehose file from the flashing folder in qfil and select the rawprogramm0 and patch0 file before clicking download.
After succeeded try download mode again and flash any h815 kdz again.
If that doesn't work you either have to wait until I'm back from vacation or find someone else with a box (e.g. infinity) to fix the gpt.
Sent from my LG-H815 using XDA Labs
steadfasterX thanks for your effort! Going to try it morning.
By the meantime maybe @TheMadScientist can say something from his experience?
How about SD card unbricking method https://forum.xda-developers.com/g4/help/unbrick-lg-g4-h811-9008-qualcomm-t3456417
I've tried once but it dosen't work.
Thanks in advance.
krzakx said:
steadfasterX thanks for your effort! Going to try it morning.
By the meantime maybe @TheMadScientist can say something from his experience?
How about SD card unbricking method https://forum.xda-developers.com/g4/help/unbrick-lg-g4-h811-9008-qualcomm-t3456417
I've tried once but it dosen't work.
Thanks in advance.
Click to expand...
Click to collapse
Guys I just studied it I ever actually had to unbrick mine. I studied in help for others so I don't know how much help I would exactly be
krzakx said:
steadfasterX thanks for your effort! Going to try it morning.
By the meantime maybe @TheMadScientist can say something from his experience?
How about SD card unbricking method https://forum.xda-developers.com/g4/help/unbrick-lg-g4-h811-9008-qualcomm-t3456417
I've tried once but it dosen't work.
Thanks in advance.
Click to expand...
Click to collapse
Yes that way is possible too. The only way it worked for me is by using dd to flash the gpt to the external sdcard and then flashing the bootloader stack plus laf. Quite easy if you have some Linux experience. But if not... you need a proper guide..
maybe there is a working h815 image out there as well but the one you're referring to is for the h811.... OMG you haven't used that one did you??? H811 has ARB!!! If you don't know what that means read https://bit.do/antirollg4 and ASK before using files not related to your model.
I'm very interested what SALT would tell us about your ARB once the device is working again....
Sent from my LG-H815 using XDA Labs
I have some base linux experience, (Debian) so no "handle follow guide" would be needed.
Yes, I have used H811 file, that was my mistake . I've exactly used this file http://downloads.codefi.re/thecubed/lg_g4/lef/h81110h.tar.gz from this topic https://forum.xda-developers.com/g4...t-tmo-vzw-intl-variants-soon-root-lg-t3164765 ,
Dear steadfasterX , please take one more time overlook for my situation and think about wright steps. Waiting for yours advices.
Best regards.
krzakx said:
I have some base linux experience, (Debian) so no "handle follow guide" would be needed.
Yes, I have used H811 file, that was my mistake . I've exactly used this file http://downloads.codefi.re/thecubed/lg_g4/lef/h81110h.tar.gz from this topic https://forum.xda-developers.com/g4...t-tmo-vzw-intl-variants-soon-root-lg-t3164765 ,
Dear steadfasterX , please take one more time overlook for my situation and think about wright steps. Waiting for yours advices.
Best regards.
Click to expand...
Click to collapse
No I was talking about the sdcard files. Flashing the h811 system file will not increase ARB (as said you corrupted the gpt though) but when you flash the h811(which you linked in your second post!) files to write the sdcard and then trying to boot from the sdcard it very likely will increase the ARB.
Ok so you haven't used the sdcard method yet?
Then try that one:
https://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853
Again try to boot to download mode with that and flash a h815 kdz. You MAY have luck but it depends. Give it a try.
Sent from my LG-H815 using XDA Labs
krzakx said:
Dear all, my quick story overwiev:
Click to expand...
Click to collapse
In the photo of your phone in download mode, it identifies as an LG-H810 running H81010o.
If I may ask, where did you get this phone from?
terence.tan said:
In the photo of your phone in download mode, it identifies as an LG-H810 running H81010o.
If I may ask, where did you get this phone from?
Click to expand...
Click to collapse
Dear @terence.tan you've asked good question.
So phone is from China seller, additionally I've made some photos of motherboard and got confused as you can see there VS986_MAIN_1.0 oh no... is all so mixed up.
Unfortunately do not have system.img back up eh.... stupid me.
SD Card method doesn't work.
Now I am think if I should go this method
https://forum.xda-developers.com/g4/help/lg-g4-vs986-super-hard-brick-unbrick-fw-t3666784
it's only idea because my motherboard seems to be VS968 labeled, but let me ask you guys as specialists.
Waiting for answer. Thanks.
One more question regarding SD Card method guys,
I've just prepared SD card fallowing this topic https://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853 , but it doesn't work.
Just for confirmation here you can se parted print, can you check please If I've burned SD Card image properly?
https://hastebin.com/inimikipux.sql
Thanks
Hi there! So you have a phone with a VS986 main board, which identifies as an H810, which was sold to you as an H815. (Which you have flashed with H811 software.)
The seller of your phone in China has done something strange to make this all work, we don't know what.
I'm sure you will understand, it will be very difficult for anyone to tell you exactly what to do.
The sdcard unbrick you tried didn't work because it has the boot stack files for H815, which require a phone with ARB version 0. I suspect you will need to copy either the VS986 or H810 boot stack files to your sdcard for it to work. (I don't know which, only the seller knows...)
However trying alternate boot stacks has a chance to increment your ARB; you should consider the consequences and not use anything with a high ARB before trying lower ones...
steadfasterX said:
Well.. You have corrupted the partition table as you used the wrong seek value. The procedure there is EXTREMELY risky and that's one reason why.
You need qfil in that mode. Download this file:
http://droid.binbash.it:8008/unbricking/qfil/h815/G4-h815_fullunbrick_working_7a3ae5809224d.zip
Install qpst and the drivers file from the software folder and after that start qfil. Select the prog_emmc_firehose file from the flashing folder in qfil and select the rawprogramm0 and patch0 file before clicking download.
After succeeded try download mode again and flash any h815 kdz again.
If that doesn't work you either have to wait until I'm back from vacation or find someone else with a box (e.g. infinity) to fix the gpt.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I'm literally praying to the Android Gods that this works. If it doesn't then I am truly truly lost...
Wish me luck!
Ugh!
I get this...
Sending NOP
ReadFile last error: 0
Response is NULL
NOP: Fail Code: 14
Unable to send FireHose NOP. Device is not in FireHose mode!
Download Fail:FireHose Fail FireHose Fail: Failed to send FireHose NOP to the phone.
Finish Download
Man, This LG is kicking my ass!
Any suggestions?
donniegalaxy2 said:
Ugh!
I get this...
Sending NOP
ReadFile last error: 0
Response is NULL
NOP: Fail Code: 14
Unable to send FireHose NOP. Device is not in FireHose mode!
Download Fail:FireHose Fail FireHose Fail: Failed to send FireHose NOP to the phone.
Finish Download
Man, This LG is kicking my ass!
Any suggestions?
Click to expand...
Click to collapse
Having just these problems on qfil with my h815 did you found a solution?
sr.arenisca said:
Having just these problems on qfil with my h815 did you found a solution?
Click to expand...
Click to collapse
No solution found by me!!! I gave up and sold the phone to ecoATM!
So i have recently bought a red magic 5g from Aliexpress. Thanks to xda i have rooted it successfully but by mistake, I have updated the phone and now the phone is bricked. I have used Jerry's tool to unbrick it but that didn't work, I have disassembled the phone for edl but still no hopes.
I think my phone is Chinese so I need Chinese unbrick tool. Can anyone help me with this?
arjun_m4 said:
So i have recently bought a red magic 5g from Aliexpress. Thanks to xda i have rooted it successfully but by mistake, I have updated the phone and now the phone is bricked. I have used Jerry's tool to unbrick it but that didn't work, I have disassembled the phone for edl but still no hopes.
I think my phone is Chinese so I need Chinese unbrick tool. Can anyone help me with this?
Click to expand...
Click to collapse
Chinese and global have same tool and same chip and people have succeeded to unbrick chinese ones with this tool. But generally the issue is the usb port/computer/usb cable. You dont have to open your phone.. Just continue to try other computers..but before everything i would suggest you to check if your phone is actually hard bricked or have you put it to edl mode etc.. But you can be sure ...there is johnny tool and jerry tool and they both work.there is nothing else
Sent from my LM-G850 using Tapatalk
Thanks but i have tried both the tools and that didn't help at all. The device doest boot and just connects to the pc using HS-USB QDLoader 9008 protocol.
arjun_m4 said:
Thanks but i have tried both the tools and that didn't help at all. The device doest boot and just connects to the pc using HS-USB QDLoader 9008 protocol.
Click to expand...
Click to collapse
Ok... Then try to continue to change pc , cable, usb port until it works.there is no other option. These tool are too much picky about these 3 things.
Sent from my LM-G850 using Tapatalk
i have tested it on 3 pc's. Jerry's tool seems stuck at Downloading Software image... and jhonny's tools gives me ack count error.
arjun_m4 said:
i have tested it on 3 pc's. Jerry's tool seems stuck at Downloading Software image... and jhonny's tools gives me ack count error.
Click to expand...
Click to collapse
Ok then contact the telegram people. Cant share link.sorry
Sent from my LM-G850 using Tapatalk
Thanks. Is it possible i can have your telegram id so I can contact you regarding this issue ?
arjun_m4 said:
Thanks. Is it possible i can have your telegram id so I can contact you regarding this issue ?
Click to expand...
Click to collapse
Sorry i changed device so i am not even active in that group or anything related to the phone..i saw you searching for chinese tool..so i answered. That group is available in a lot of place and they are very helpful..check with them..sorry couldn't help
Sent from my LM-G850 using Tapatalk