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.
I bought a g4 near a week ago and it says on the back sticker that its H811 but when i entered download mode it was korean and i found something mentioning f500 any way i flashed 20r kdz for h811 and phone bricked(9008 mode)then i used ls991 mbn file to use in QFIL and revive my phone now when i flash any kdz for h811 phone bricks and i have to flash mbn files again however the phone boots up but no camera no imei no baseband im very confused can anyone help?
Any chance that flashing f500l tot file revive the phone?
Thanks.
shamescool said:
I bought a g4 near a week ago and it says on the back sticker that its H811 but when i entered download mode it was korean and i found something mentioning f500 any way i flashed 20r kdz for h811 and phone bricked(9008 mode)then i used ls991 mbn file to use in QFIL and revive my phone now when i flash any kdz for h811 phone bricks and i have to flash mbn files again however the phone boots up but no camera no imei no baseband im very confused can anyone help?
Any chance that flashing f500l tot file revive the phone?
Thanks.
Click to expand...
Click to collapse
may have to dissassmble the device and find out what motherboards on it weve seen cases like this before and its not easy i would return it and say wtf
TheMadScientist420 said:
may have to dissassmble the device and find out what motherboards on it weve seen cases like this before and its not easy i would return it and say wtf
Click to expand...
Click to collapse
you would say there is a chance to recover it or not?does it worth it?
Thanks for reply
shamescool said:
you would say there is a chance to recover it or not?does it worth it?
Thanks for reply
Click to expand...
Click to collapse
In my opinion no its not worth the hassle but ot only takes 5 mine to check ot 2. Unless its got the bootloop issue or hard bricked its fixable. But how determined are you.
TheMadScientist420 said:
In my opinion no its not worth the hassle but ot only takes 5 mine to check ot 2. Unless its got the bootloop issue or hard bricked its fixable. But how determined are you.
Click to expand...
Click to collapse
my phone boots up completely but no baseband no imei or anything and that infamous 9008 brick is fixable with ls991 laf.img and 8992.mbn and etc... files and here is my next approaches please if you have enough aknowledge guide me with these options i have or add any if something came on your mind:
1.Flashing a ls991 model kdz and see what comes out(probably not doable,lgup may not let me flash it)
2.while surfing through the forums and threads i found the exact H811 10N Laf.img and i will replace it with ls991's and will use QFIL to correct the partitions and then my phone would be fixed(im too scared for this one...maybe my phone is a refurbished F500...who knows? :fingers-crossed: )
3.Maybe finding and flashing F500 laf.img fix the phone but a HUGE problem i am facing:where to find that file?
Note:All i am trying to do is to fix this phone by software approaches and disassembling the phone is out of my options for now(only will do if none of above fix it properly)
So with all of that what would you do if you be in my shoes?:cyclops:
Always hated LG and admired Sony but i started to hate xperia x series because of weak development so i bought this one for around 100$ in your currency.:laugh:
Id send it back.
TheMadScientist420 said:
Id send it back.
Click to expand...
Click to collapse
My curiousity will kill me someday
I believe i can fix it and beside that learning new things about lg devices is interesting since i bought it for only 100 bucks from an old pal who does nt know what actually smart phone is:laugh:
Anyway i learnt how to extract laf from kdz files and im going to test both f500l and h811 and pray:cyclops:
if i fix it properly i would make a thread to share my experience with this refurbished(dont know actually if it is)
phone and help people who brick their refurbished phone and dont know how to fix it
shamescool said:
My curiousity will kill me someday
I believe i can fix it and beside that learning new things about lg devices is interesting since i bought it for only 100 bucks from an old pal who does nt know what actually smart phone is:laugh:
Anyway i learnt how to extract laf from kdz files and im going to test both f500l and h811 and pray:cyclops:
if i fix it properly i would make a thread to share my experience with this refurbished(dont know actually if it is)
phone and help people who brick their refurbished phone and dont know how to fix it
Click to expand...
Click to collapse
i use the old wilcracks diag toot and lg firware extractor to extract any bins u need
TheMadScientist420 said:
i use the old wilcracks diag toot and lg firware extractor to extract any bins u need
Click to expand...
Click to collapse
then i will use them to crack open kdz from both H811 and F500L firmwares to flash laf and other messed up files with fastboot
but im wondering which one should i try first because im concerned if i flash wrong files then there will be even no 9008 mode to use QFIL and get back to very first step...
What is going to happen exactly when i flash another varient's laf? will it kill the phone completely or will there be any 9008?
Thanks for those apps you mentioned btw:good:
shamescool said:
then i will use them to crack open kdz from both H811 and F500L firmwares to flash laf and other messed up files with fastboot
but im wondering which one should i try first because im concerned if i flash wrong files then there will be even no 9008 mode to use QFIL and get back to very first step...
What is going to happen exactly when i flash another varient's laf? will it kill the phone completely or will there be any 9008?
Thanks for those apps you mentioned btw:good:
Click to expand...
Click to collapse
yea ive been using em since g2.and i use em on all lgs . diag tool is for flashing but at the bottom u can extract
i get my own .dlls for lgg2 flash tool and i flash orig g4 firmware with it still.
if i could find the tot would for g5.
now if u break 9008 jtag i think is the only fix i dont know the pin outs or if the g4 even supports that like the g3 and 2. thats why i say take device apart its fricken easy there should be a sticker on the mother board or stamps that say the mbs model and go from there
TheMadScientist420 said:
yea ive been using em since g2.and i use em on all lgs . diag tool is for flashing but at the bottom u can extract
i get my own .dlls for lgg2 flash tool and i flash orig g4 firmware with it still.
if i could find the tot would for g5.
now if u break 9008 jtag i think is the only fix i dont know the pin outs or if the g4 even supports that like the g3 and 2. thats why i say take device apart its fricken easy there should be a sticker on the mother board or stamps that say the mbs model and go from there
Click to expand...
Click to collapse
dissembled the phone and it was f500l as expected so i decided to go with f500 laf.img and then my phone got fixed up completely ive even replaced modem and other h811 things except for system now my phone is working perfect again and im going to flash a stock based rom's system.img (10N) with fastboot
Thanks for your precious info once again:cyclops:
shamescool said:
dissembled the phone and it was f500l as expected so i decided to go with f500 laf.img and then my phone got fixed up completely ive even replaced modem and other h811 things except for system now my phone is working perfect again and im going to flash a stock based rom's system.img (10N) with fastboot
Thanks for your precious info once again:cyclops:
Click to expand...
Click to collapse
These guys will piece these things together and mislabel crap. Just to make a dollar. Im glad to see ure good to go.
TheMadScientist420 said:
These guys will piece these things together and mislabel crap. Just to make a dollar. Im glad to see ure good to go.
Click to expand...
Click to collapse
Actually LG devices are very easy to disassemble so people like them wont put so much effort to refurbish LG phones and earn themselves some easy money.
And believe me Iran is the heaven of refurbished and chinese phones
Mostly because many cant afford to buy their phones and other stuff from trusted sellers and they buy them with no warranty(or guarranty)from third party sellers.
Actually they have a place for themselves in downtown(Aladdin building).
But i wanted a flagship LG device to learn more about it and i got it for a couple of bucks so it really didnt matter if my G4 didnt work as expected.
But its always a pleasure to make some mystery and try to crack the case by yourself :laugh:
shamescool said:
Actually LG devices are very easy to disassemble so people like them wont put so much effort to refurbish LG phones and earn themselves some easy money.
And believe me Iran is the heaven of refurbished and chinese phones
Mostly because many cant afford to buy their phones and other stuff from trusted sellers and they buy them with no warranty(or guarranty)from third party sellers.
Actually they have a place for themselves in downtown(Aladdin building).
But i wanted a flagship LG device to learn more about it and i got it for a couple of bucks so it really didnt matter if my G4 didnt work as expected.
But its always a pleasure to make some mystery and try to crack the case by yourself :laugh:
Click to expand...
Click to collapse
the whole lg g series is a wonderful device for do it your self i have owned a g2 g3 g4 and now g5 even thought i said i would never by lg again after g4 i got a stylo3 and my wife sports a stylo 2
im working on a us cellular s5 now as we speak and i sometimes run my gs6 edge nut not much since i got g5.
TheMadScientist420 said:
the whole lg g series is a wonderful device for do it your self i have owned a g2 g3 g4 and now g5 even thought i said i would never by lg again after g4 i got a stylo3 and my wife sports a stylo 2
im working on a us cellular s5 now as we speak and i sometimes run my gs6 edge nut not much since i got g5.
Click to expand...
Click to collapse
of course they are great but hardware faults are pretty big deal but for me sony z series were better right until z3+ .for now im happy with my htc u11 and im not going to unlock it or anything.
maybe i use g4 as my secondary device instead of xperia z2.
its a shame that sony is not in its golden age (2011-2013) anymore...
will make a thread to help people like me to unbrick their refurbished device
Thanks for everything
Hi guys;
So i bought a second hand unlocked D851 ( TMOBILE) with kitkat (cloudy rom) wanted to upgrade it to lolipop but i hard bricked it then used board diag program to bring it back to life but i extracted a d850 rom TOT since the d851 didnt work so now my lg g3 is at&t and permenantly locked ,been trying for a week now to unlocked it for nothing then I read somewhere in this forum that its easy to unlock the d851 using the tmobile app. so is there any way to change it back to D851.
Anyone has any idea?!!
how u use the board diag cuz im stock in qualcomm hs-usb qdloader 9008 and the threadt is closed now
ipus89 said:
how u use the board diag cuz im stock in qualcomm hs-usb qdloader 9008 and the threadt is closed now
Click to expand...
Click to collapse
Try this thread... it is still open & active: https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
startswithPendswithOOH said:
Try this thread... it is still open & active: https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Click to expand...
Click to collapse
how about my problem??!!!
nice8man said:
how about my problem??!!!
Click to expand...
Click to collapse
1)What do you mean permanently locked...carrier/sim, mcafee security, something else? If it's carrier you can order a sim unlock code off of ebay for @$4.00 us, or use any other sim unlock services out there.
2)If you changed a d851 to a d850 using board diag and manually loading the partitions - then why not extract a d851 tot and do the same thing?
startswithPendswithOOH said:
1)What do you mean permanently locked...carrier/sim, mcafee security, something else? If it's carrier you can order a sim unlock code off of ebay for @$4.00 us, or use any other sim unlock services out there.
2)If you changed a d851 to a d850 using board diag and manually loading the partitions - then why not extract a d851 tot and do the same thing?
Click to expand...
Click to collapse
thank you for the reply.
1- its carrier unlock + i have no online wallet and i cant get one
2- thats what im looking for is there a way to manually load d851 partitions i mean when i loaded d850 partitions my phone was in dload mode ( hard bricked) do i have to hard unbrick now again?
by the way i can search for other carriers and i find mine under rat:GSM but i m unable to connect to it .
nice8man said:
thank you for the reply.
1- its carrier unlock + i have no online wallet and i cant get one
2- thats what im looking for is there a way to manually load d851 partitions i mean when i loaded d850 partitions my phone was in dload mode ( hard bricked) do i have to hard unbrick now again?
by the way i can search for other carriers and i find mine under rat:GSM but i m unable to connect to it .
Click to expand...
Click to collapse
1) I don't know of a free way to get an unlock code, so if you can't order one you're probably stuck. Pay a friend who can order one for you?
2) If we're on the same page here and you previously used the board diag tool then that should work again. Hard brick usually shows up in your device manager as qualcomm 9008 instead of an lg device, so to get back to that condition you would have to open the phone up and short a pin -
follow the guide in the link I posted before and you should be good to go. I don't have links for any d851 tot files though...sorry, not my variant.
startswithPendswithOOH said:
1) I don't know of a free way to get an unlock code, so if you can't order one you're probably stuck. Pay a friend who can order one for you?
2) If we're on the same page here and you previously used the board diag tool then that should work again. Hard brick usually shows up in your device manager as qualcomm 9008 instead of an lg device, so to get back to that condition you would have to open the phone up and short a pin -
follow the guide in the link I posted before and you should be good to go. I don't have links for any d851 tot files though...sorry, not my variant.
Click to expand...
Click to collapse
so i need to hard brick my phone again?
nice8man said:
so i need to hard brick my phone again?
Click to expand...
Click to collapse
Unfortunately...I think so. If you were to try and use the lg flash tool and try and tot a d851 file into a d850 it'll probably throw some errors - model check, for ex - and won't flash. You can try and see for yourself if you'd like...here's a link for a couple tools; the 1st is kdz method, second is tot: https://forum.xda-developers.com/showthread.php?t=2785089
To brick it again follow guide I linked( https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359), short that 2nd jtag pin in the pic for @5 seconds, plug in the usb, and it should go to qualcomm 9008. You already know how to do the rest as far as loading partitions and such, and if you don't the guide will tell you what to do.
Good luck :good:
startswithPendswithOOH said:
Unfortunately...I think so. If you were to try and use the lg flash tool and try and tot a d851 file into a d850 it'll probably throw some errors - model check, for ex - and won't flash. You can try and see for yourself if you'd like...here's a link for a couple tools; the 1st is kdz method, second is tot: https://forum.xda-developers.com/showthread.php?t=2785089
To brick it again follow guide I linked( https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359), short that 2nd jtag pin in the pic for @5 seconds, plug in the usb, and it should go to qualcomm 9008. You already know how to do the rest as far as loading partitions and such, and if you don't the guide will tell you what to do.
Good luck :good:
Click to expand...
Click to collapse
the link you attached is for mobiles that are already hard bricked mine is not
nice8man said:
the link you attached is for mobiles that are already hard bricked mine is not
Click to expand...
Click to collapse
Yeah....and?
Re-read your previous post where you asked if you'll have to brick it again.
I said yes, and gave you a link on how to do it. Did you read the link? My guess would be no, since the 1st 4 steps tell you how to brick it and enter qualcomm9008 mode.
You're on your own now. Good luck. And you're welcome for the time I spent trying to help you.
startswithPendswithOOH said:
Yeah....and?
Re-read your previous post where you asked if you'll have to brick it again.
I said yes, and gave you a link on how to do it. Did you read the link? My guess would be no, since the 1st 4 steps tell you how to brick it and enter qualcomm9008 mode.
You're on your own now. Good luck. And you're welcome for the time I spent trying to help you.
Click to expand...
Click to collapse
Thank you for your replies man i really appriciate it...i have read that topic like 5 times; maybe i dont understand english very well but when i read the title LG G3 Hard Brick Recovery+ Required Materials:Bricked LG G3 i thought he meant that this topic is for people that has thier phone bricked and need to recover them.
nice8man said:
Thank you for your replies man i really appriciate it...i have read that topic like 5 times; maybe i dont understand english very well but when i read the title LG G3 Hard Brick Recovery+ Required Materials:Bricked LG G3 i thought he meant that this topic is for people that has thier phone bricked and need to recover them.
Click to expand...
Click to collapse
It's cool. Yes the guide is for already bricked phones, but what I was trying to say is since you have a functional phone rt now you're gonna have to brick it, and by brick it I mean qualcomm9008 mode, and that's what the 1st part of the guide shows you how to do by shorting out the pin. Once you get to Qualcomm mode you can then use the board diag tool and load your partitions that you extracted from the tot and hopefully get back to your original d851 phone and get back up and running. Does that make more sense?
Again...good luck
startswithPendswithOOH said:
It's cool. Yes the guide is for already bricked phones, but what I was trying to say is since you have a functional phone rt now you're gonna have to brick it, and by brick it I mean qualcomm9008 mode, and that's what the 1st part of the guide shows you how to do by shorting out the pin. Once you get to Qualcomm mode you can then use the board diag tool and load your partitions that you extracted from the tot and hopefully get back to your original d851 phone and get back up and running. Does that make more sense?
Again...good luck
Click to expand...
Click to collapse
I did not know that you can hard brick the phone by shorting the pins; thank you.
startswithPendswithOOH said:
It's cool. Yes the guide is for already bricked phones, but what I was trying to say is since you have a functional phone rt now you're gonna have to brick it, and by brick it I mean qualcomm9008 mode, and that's what the 1st part of the guide shows you how to do by shorting out the pin. Once you get to Qualcomm mode you can then use the board diag tool and load your partitions that you extracted from the tot and hopefully get back to your original d851 phone and get back up and running. Does that make more sense?
Again...good luck
Click to expand...
Click to collapse
I hard bricked it again and then extracted another D851 tot and then loaded all the necessary partitions but the phone still on qload mode i copied the sbl1.mbm of the D850 and tried them with D851 partitions the phone revived but not in download mode.
I managed tp recover all partitions and the phone is on dowloading mode but still detected as d850 so i have the dll cross error everytime i try to flash a rom even with using the custon dll file.
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!
Like several others, I have been trying to recover a MotoG5 with BlankFlash, but all the files I tried gave an error, because I believe they were made based on different ROM distributions. I would like to know how to develop ... What exists in singleimage.bin ... how is "qboot.exe" done ...
Does anyone here have this knowledge to share? Someone who has done something like that?
rada80 said:
Like several others, I have been trying to recover a MotoG5 with BlankFlash, but all the files I tried gave an error, because I believe they were made based on different ROM distributions. I would like to know how to develop ... What exists in singleimage.bin ... how is "qboot.exe" done ...
Does anyone here have this knowledge to share? Someone who has done something like that?
Click to expand...
Click to collapse
I have two news for you!
First: Welcome to the group of fu** with Moto g5 xt1672 / 70 ... locked in the led.
Second: There is 1 whole month that I'm trying and neither jtag worked.
Here in Brazil I already took the device in several specialists and already tried several tutorials, all without success.
There is one I sent shortly to a member here on the forum.
This tutorial I enivei believe I did not understand right as it is done because the bastard of the videio does not know how to explain correctly or I'm kind of dumb to try.
I can not send links here because I am new to the forum, if you want you can send me an email in which I forward youtube links for you to try:
[email protected]
good luck!! If you find out let us know!
comment
silasmvg said:
I have two news for you!
First: Welcome to the group of fu** with Moto g5 xt1672 / 70 ... locked in the led.
Second: There is 1 whole month that I'm trying and neither jtag worked.
Here in Brazil I already took the device in several specialists and already tried several tutorials, all without success.
There is one I sent shortly to a member here on the forum.
This tutorial I enivei believe I did not understand right as it is done because the bastard of the videio does not know how to explain correctly or I'm kind of dumb to try.
I can not send links here because I am new to the forum, if you want you can send me an email in which I forward youtube links for you to try:
[email protected]
good luck!! If you find out let us know!
Click to expand...
Click to collapse
I have an xt1671 device that suffered hardbrik if they manage to run the blankflash with success agalon know so I can revive my device thanks
tengo un dispositivo xt1671 que sufrio hardbrik si logran ejecutar el blankflash con exito agalon saber para que pueda revivir mi dispositivo gracias
There's a way to restore the bootloader, however, a very specific stock rom will have to be flashed from fastboot afterwards, which I don't know of.
To the best of my knowledge, I don't think you can develop blankflashes.
1)Blankflashes are digitally signed by the OEM, and likely are not usable if you edit them (as that breaks the signatures).
2)Singleimage.bin appears to contain the various bootloader images, with an accompanying XML file (I guess hex locations of the images in the singleimage.bin), and GPT.bin, whereas qboot.exe seems to handle the communication and verification (from looking at other blankflash logs).
a)Qboot.exe appears to contact your device via Sahara protocol (to attempt to reach the primary bootloader) https://github.com/openpst/sahara and seems to verify the CPU and device.
b)If the CPU and device are verified, the programmer is then loaded and sent to your device to verify the bootloader version on your device. Presumably, this step is to prevent you from flashing older bootloaders and possibly opening security holes https://forum.xda-developers.com/showpost.php?p=62191317&postcount=2112 If the programmer is satisfied your bootloader is not newer than the blankflash bootloader, it then opens the firehose connection to begin downloading and flashing a new bootloader to your device.
It seems that from the blankflashes I've noted, most of the failures seem to happen with 2b) - i.e. the programmer verification or with 2a), the blankflash just can't communicate with your device. With 2b), that may fail if your corrupted bootloader is newer than the blankflash bootloader - it'll just reject the flash or hang at 'waiting for firehose'. As mentioned here, though, https://github.com/openpst/sahara you'd need updated/new blankflash files with an updated programmer specific to the Motorola MSM8937 platform. Getting those files is quite difficult - OEMs like Motorola do not like giving them out (most of the blankflashes we have on XDA are old leaks), presumably as having a signed blankflash that can access the bootloader may be a security risk (as this Aleph article may demonstrate https://alephsecurity.com/2018/01/22/qualcomm-edl-1/ ) However, without a proper programmer, then the bootloader images may not flash onto your device.
You may wish to look into either a G5S or G6 Play blankflash if they are around, as they are based on the Snapdragon 430. I do not know if their bootloaders are compatible with the G5, so I cannot recommend to flash/attempt to flash a blankflash not meant for your device. Failing that, your other options are to pay for a motherboard repair or to invest in a new device.
echo92 said:
To the best of my knowledge, I don't think you can develop blankflashes.
1)Blankflashes are digitally signed by the OEM, and likely are not usable if you edit them (as that breaks the signatures).
2)Singleimage.bin appears to contain the various bootloader images, with an accompanying XML file (I guess hex locations of the images in the singleimage.bin), and GPT.bin, whereas qboot.exe seems to handle the communication and verification (from looking at other blankflash logs).
a)Qboot.exe appears to contact your device via Sahara protocol (to attempt to reach the primary bootloader) https://github.com/openpst/sahara and seems to verify the CPU and device.
b)If the CPU and device are verified, the programmer is then loaded and sent to your device to verify the bootloader version on your device. Presumably, this step is to prevent you from flashing older bootloaders and possibly opening security holes https://forum.xda-developers.com/showpost.php?p=62191317&postcount=2112 If the programmer is satisfied your bootloader is not newer than the blankflash bootloader, it then opens the firehose connection to begin downloading and flashing a new bootloader to your device.
It seems that from the blankflashes I've noted, most of the failures seem to happen with 2b) - i.e. the programmer verification or with 2a), the blankflash just can't communicate with your device. With 2b), that may fail if your corrupted bootloader is newer than the blankflash bootloader - it'll just reject the flash or hang at 'waiting for firehose'. As mentioned here, though, https://github.com/openpst/sahara you'd need updated/new blankflash files with an updated programmer specific to the Motorola MSM8937 platform. Getting those files is quite difficult - OEMs like Motorola do not like giving them out (most of the blankflashes we have on XDA are old leaks), presumably as having a signed blankflash that can access the bootloader may be a security risk (as this Aleph article may demonstrate https://alephsecurity.com/2018/01/22/qualcomm-edl-1/ ) However, without a proper programmer, then the bootloader images may not flash onto your device.
You may wish to look into either a G5S or G6 Play blankflash if they are around, as they are based on the Snapdragon 430. I do not know if their bootloaders are compatible with the G5, so I cannot recommend to flash/attempt to flash a blankflash not meant for your device. Failing that, your other options are to pay for a motherboard repair or to invest in a new device.
Click to expand...
Click to collapse
You are very correct and I agree with you! By the jtag I managed to do all this, but the error occurs in the signature and I do not know to do the correct programming.
The way I found it is to wait for the leak of this oem.
silasmvg said:
You are very correct and I agree with you! By the jtag I managed to do all this, but the error occurs in the signature and I do not know to do the correct programming.
The way I found it is to wait for the leak of this oem.
Click to expand...
Click to collapse
, I own a Moto G5 XT1677 which i bought in Nov. 2017. Got android 8.1 Oreo update in Oct 2018. I was playing PUBG on 30 Dec 2018 and suddenly my screen freez and no button was responsive. I removed the battery and reinserted and tried powering it on but no response. Tried chargring but only a led on side of speaker was blinking. I tried by pressing vol+ and vol- and power button together/ vol- and power button ALSO for short time and more than 3 mins too but still coludnot get any response from phone. I tried flashing in every possible way by downloadin the cedric stock file from XDA but could not revive the phone (since cannot get that flashing/fastboot screen). I WAS ONLY GETTING TO SEE HS-USB qdLoader 9008 diagnostic (COM 4) port in QFIL tool on my laptop and cannot get anything to proceed to use that port. I sent it to service center and they were saying that they cannot get the boot loader on phone. Before that they were saying motherboard issues then said Power IC issue fir which again motherboard is to be replaced and the price was exceeding the price of the phone.
I WANT TO GIVE A FINAL TRY AS THE PHONE IS JUST 1 YEAR AND 1 MONTH OLD. NEED SOME EXPERT ADVICE TO REVIVE THE PHONE. PLEASE HELP ME AS CANNOT AFFORD TO A NEW ONE NOW.
HIMANSHU SWAIN said:
, I own a Moto G5 XT1677 which i bought in Nov. 2017. Got android 8.1 Oreo update in Oct 2018. I was playing PUBG on 30 Dec 2018 and suddenly my screen freez and no button was responsive. I removed the battery and reinserted and tried powering it on but no response. Tried chargring but only a led on side of speaker was blinking. I tried by pressing vol+ and vol- and power button together/ vol- and power button ALSO for short time and more than 3 mins too but still coludnot get any response from phone. I tried flashing in every possible way by downloadin the cedric stock file from XDA but could not revive the phone (since cannot get that flashing/fastboot screen). I WAS ONLY GETTING TO SEE HS-USB qdLoader 9008 diagnostic (COM 4) port in QFIL tool on my laptop and cannot get anything to proceed to use that port. I sent it to service center and they were saying that they cannot get the boot loader on phone. Before that they were saying motherboard issues then said Power IC issue fir which again motherboard is to be replaced and the price was exceeding the price of the phone.
I WANT TO GIVE A FINAL TRY AS THE PHONE IS JUST 1 YEAR AND 1 MONTH OLD. NEED SOME EXPERT ADVICE TO REVIVE THE PHONE. PLEASE HELP ME AS CANNOT AFFORD TO A NEW ONE NOW.
Click to expand...
Click to collapse
You can revive your device from this thread
https://forum.xda-developers.com/g5...-run-morning-post-image-t3776012/post76190059
And use this mmcblk0 file from here:-
https://drive.google.com/file/d/1Nw50H-XCsrxsFXdBeyo_a0CV4WGcZDIJ/view?usp=drivesdk