Database Users

Le Eco & Qualcom Toolkit [Toolkit][Windows]

Hey Guys, Welcome to Another Brand New Tool For All Le Eco Devices and Maybe For all Other MTK or Qualcomm running devices (if you know what is ADB / Fastboot and basic stuff regarding it, Then you can use it onto every single android device)
{
"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"
}
What is This?
This is basically a Software for Le Devices, from which you can easily able to Unlock bootloader, flash TWRP, Root, install mods and many many things.
Is This Safe to Use?
Absolutely Yes!
Features :
View features from here
Requirements :
1. Dot Net framework must be greater than 3.5
2. Visual C++ Redistributable package
3. Any Windows version
Credits :
1. To "Rishabh Rao" Who is the original maker of this tool (check out here) - Thanks Bros:laugh:
2. To Androidlib .Net Library (Check out here)
3. To my Best AndroidCtrl and AndroidCtrlUI THE BEST and Very thanks to his creator who helped me a lot (here)
4. To All things I have used in my tool (really appreciated there work):laugh:
Some Snappies!! :cyclops:
All Views Downloads HERE :
Like my Work Do Support and Share this Tool to every Le User you Know, Hit THANKS Button too:angel:

Hi. Sorry if this has been asked before, but i am one of the small number of ppl who purchased the LeMax Pro X910 and bricked the phone while trying to install a Le Max 2 rom (was told both devices could use same rom) and now the device is in an eternal Qualcomm Qfil 9008 state, and the screen never turns on. I was told by a very knowledgeable person that the phone is probably stuck in a ramdump state. Can this tool help in such cases? Thanks for your contribution.

JohnnySJ said:
Hi. Sorry if this has been asked before, but i am one of the small number of ppl who purchased the LeMax Pro X910 and bricked the phone while trying to install a Le Max 2 rom (was told both devices could use same rom) and now the device is in an eternal Qualcomm Qfil 9008 state, and the screen never turns on. I was told by a very knowledgeable person that the phone is probably stuck in a ramdump state. Can this tool help in such cases? Thanks for your contribution.
Click to expand...
Click to collapse
Ya you can use it for flashing stock ROM...go to the root tab from the drop down list select stock ROM and browse the stock ROM from it..then connect ur phone to PC in fastboot but first unlock it by normal method use LE 2 method to do that...then click on update button ...to flash the stock ROM in fastboot

Tried it but unfortunately the tool requires the phone to be recognized via adb, and our bricked phones are in a special Qualcom QFil 9008 Loader Mode. So no luck.

JohnnySJ said:
Tried it but unfortunately the tool requires the phone to be recognized via adb, and our bricked phones are in a special Qualcom QFil 9008 Loader Mode. So no luck.
Click to expand...
Click to collapse
Oh..**** man... Sorry bro.. That my tool won't helps you coz I don't have any LE eco devices to make this tool.. All I did is with my knowledge and some Qualcomm chipsets resources.. That's it..I think I need to study more about le devices....anyways thank you for using it. ...and one sec loader mode means what ..similar to fastboot mode or bit different... Kinda..

leeco-x820-max-2-super-unbrick-guide
This tutorial solves the same problem that your smartphone has, only on the x820 model, but it can help in some way.

rcfree said:
leeco-x820-max-2-super-unbrick-guide
This tutorial solves the same problem that your smartphone has, only on the x820 model, but it can help in some way.
Click to expand...
Click to collapse
Ohh could you describe more, then i will integrate it in the toolkit.. Updates ?

i probably hard bricked a1 open for any ideas ( only launch in edl mode)

Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

onursewimli said:
Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
Click to expand...
Click to collapse
Oh, I know that feeling of having bricked one beloved device or at least thinking it is bricked. So I did some new year's digging for you and maybe found a way to help.
Assuming your bootloader is still unlocked and it is really the EDL mode (at least it sounds a lot like it reading the info you have provided) you should have still some good chances.
Please follow this tutorial found here: http://en.miui.com/thread-294318-1-1.html
And for flashing the firmware you are looking for, please have a look at my thread over here, which leads you to the best suited download package of version 7.12.19, that I could find:
https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
So give it a go, good luck & please provide your feedback here.
Maybe it can help others too
Edit: I guess the part which is probably the most important is the qualcomm driver

hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.

onursewimli said:
hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.
Click to expand...
Click to collapse
Did they fixed it? Without any cost?

lumia 520 bricked after flash of android and now showing android in drivers

my lumia 520 is bricked after flash of android but is vibrating and and connecting to pc but showing android in device managment. any solutions?
not detected by cmd or windows device recovery tool.

janjuaalpha said:
my lumia 520 is bricked after flash of android but is vibrating and and connecting to pc but showing android in device managment. any solutions?
not detected by cmd or windows device recovery tool.
Click to expand...
Click to collapse
Try to get into recovery by press the power button and volume + at the same time
If you can get to recovery , you can try it again , or comeback Windows Phone

Ryonic said:
Try to get into recovery by press the power button and volume + at the same time
If you can get to recovery , you can try it again , or comeback Windows Phone
Click to expand...
Click to collapse
it vibrates but shows only android i have tried every key combination.

janjuaalpha said:
it vibrates but shows only android i have tried every key combination.
Click to expand...
Click to collapse
Do you flash the rom yet?, or just install bootloader and recovery?
If your device get bricked after run the uefi2lk.cmd , tell me and i will show you the way to fix it
P/s : Sorry about my bad english skill

i flashed bootloader and recovery and my nokia bricked after that

Ryonic said:
Do you flash the rom yet?, or just install bootloader and recovery?
If your device get bricked after run the uefi2lk.cmd , tell me and i will show you the way to fix it
P/s : Sorry about my bad english skill[
hello plzzz i went restore my nokia lumai 520 andrio TO windows i have backup flash plzzzz send me tuto or video plzzzzzzz
Click to expand...
Click to collapse

janjuaalpha said:
my lumia 520 is bricked after flash of android but is vibrating and and connecting to pc but showing android in device managment. any solutions?
not detected by cmd or windows device recovery tool.
Click to expand...
Click to collapse
You phong is working,just need flash recovery

Ryonic said:
Do you flash the rom yet?, or just install bootloader and recovery?
If your device get bricked after run the uefi2lk.cmd , tell me and i will show you the way to fix it
P/s : Sorry about my bad english skill
Click to expand...
Click to collapse
no i just flashed recovery but tried to flash rom but not sucessful

I'm having a really similar issue that I've had for nearly a whole year after flashing Android. I myself am trying to roll back to WP 8.1 however I cannot flash the hex file (emergency) back.
{
"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"
}
Also I want to point this out, Lumia 520/521 devices have issues with reading and writing as explained here

So you install the recovery of android already? , if that so , you can't used this way to roll back to WP 8.1
P/s: I've met a lot of error when try to install android on my lumia 520 , and finally , i can't touch or do anything in TWRP because my digitizer is not original . So I rollback to windows 8.1 and sell it
Use should used this tutorial : https://forum.xda-developers.com/no...nt/restore-windows-phone-8-installed-t3608223
You need to have a backup , if you don't , you have to stick with android.
I think all the error when install android on lumia 520/521/525 could all be fixed , except when you have a samsung emmc :fingers-crossed:

Try to enter recovery with fastboot. Connect the Phone to the PC, and open fastboot in cmd and type this:
fastboot oem reboot-recovery
If you installed successfully the recovery, it will appear in the phone. (It may take 30 seconds or less in appear)

Seems people aren't getting the message
Issue Identification:
Although our investigation is not complete, we’d like to share some initial insight into what we’ve uncovered:
Data writing size & speed: It was discovered that some devices are having trouble accepting the recovery image data being flashed. The blocks of data were too large for some devices to handle, and the memory on the device was having trouble with the speed at which the data was being written. In short, devices were getting too much data, too quickly. This would cause the failure as the new software is corrupted.
Small portion of 520/521 devices affected: As we reviewed logs and worked through issue reproduction, we identified the subset of affected 520/521 devices that may encounter this issue. There is no direct way for an end-user to check their device unfortunately, however it is positive news that not all units would experience this issue.
Click to expand...
Click to collapse

janjuaalpha said:
my lumia 520 is bricked after flash of android but is vibrating and and connecting to pc but showing android in device managment. any solutions?
not detected by cmd or windows device recovery tool.
Click to expand...
Click to collapse
Hi I solve it by installing the Compositive ADB interface driver manually, after this the uefi2lk.cmd detects it and completes the installation of twrp .... the bad thing is that there is still no solution for the micro sd, the chip reading , and the camera and the installation of google play services would be excellent if this could be solved at the moment the only thing I have for solution is to return the movila windows thanks to the help :crying::crying::good:

kristiano646 said:
Hi I solve it by installing the Compositive ADB interface driver manually, after this the uefi2lk.cmd detects it and completes the installation of twrp .... the bad thing is that there is still no solution for the micro sd, the chip reading , and the camera and the installation of google play services would be excellent if this could be solved at the moment the only thing I have for solution is to return the movila windows thanks to the help :crying::crying::good:
Click to expand...
Click to collapse
could you please provide me with the drivers? i cant make uefi2lk ro recognize my phone

Ryonic said:
Do you flash the rom yet?, or just install bootloader and recovery?
If your device get bricked after run the uefi2lk.cmd , tell me and i will show you the way to fix it
P/s : Sorry about my bad english skill
Click to expand...
Click to collapse
Hello. My device bricked after run uefi2lk.cmd and don't detecting with any key combinations. I have backup. Please,help me.

thinhx2 said:
You phong is working,just need flash recovery
Click to expand...
Click to collapse
How to do it?
---------- Post added at 02:43 AM ---------- Previous post was at 02:36 AM ----------
Ryonic said:
Do you flash the rom yet?, or just install bootloader and recovery?
If your device get bricked after run the uefi2lk.cmd , tell me and i will show you the way to fix it
P/s : Sorry about my bad english skill
Click to expand...
Click to collapse
What to do?

thinhx2 said:
You phong is working,just need flash recovery
Click to expand...
Click to collapse
hi, i also having similar issue but in my case i have run uefi2lk.cmd command and after that my phone was bricked......
it only shows android in device manager but can not be detected by windows devide recovery tool or cmd......
will you please let me know the solution in detail as i am a beginner in that kind of works....

adityachoudhary368 said:
hi, i also having similar issue but in my case i have run uefi2lk.cmd command and after that my phone was bricked......
it only shows android in device manager but can not be detected by windows devide recovery tool or cmd......
will you please let me know the solution in detail as i am a beginner in that kind of works....
Click to expand...
Click to collapse
Use fastboot,flash twrp for it,install android

My device is stuck in a boot loop on the first load of Lineage OS 13, nothing on my computer can pick up the phone so I can't fastboot or anything like that. I'm a bit stumped, does anyone have any insight?

G6 hard bricked

Firstly I'd like to say HELLO as I'm new user of forum
Yesterday I've hardbricked my G6. I was sure that I got H870 so I downloaded cfw for that model and when I tried to flash it via TWRP it showed that I got H872 version and it can't be flashed as it is for H870. I downloaded H872 cfw, flashed it with nor problem and thats all. Phone is not turning on, only thing that I can do with it is to plug it via cable to PC and see that in Devices Manager there is Quectel QDloader 9008 (COMxx). I've done more than 15h of research and I've found solution to wake it up with BoardDiag tool. I got ready extracted .TOT file but when I try to start whole proccedure I got "device was not found in dload trying flash programmer" error. In similar threads only solution I've found is opening phone and connecting 2 pins but I can't (and don't want to) open it. Is there any other method that can help me wake it up? Many thanks in advance, this stuff makes me crazy and I'm unable to use phone (don't have spare one )
{
"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"
}

LG up and uppercut to flash stock KDZ file.

basicreece said:
LG up and uppercut to flash stock KDZ file.
Click to expand...
Click to collapse
Thank you for your answer. Unfortunally LGUP is not recognizing any device (just empty list, not unrecognized device)

When I hardbricked my LG G3 it happened the same. The only solution was making a shortcut in the procesor. It is not really difficult, the only problem is you need to open up the phone.

mprovi_15 said:
When I hardbricked my LG G3 it happened the same. The only solution was making a shortcut in the procesor. It is not really difficult, the only problem is you need to open up the phone.
Click to expand...
Click to collapse
G6 got unremoveable battery so I can't open it :/
Is there any other sollution?

Sernio said:
G6 got unremoveable battery so I can't open it :/
Is there any other sollution?
Click to expand...
Click to collapse
Are you using uppercut with lg up? LG UP on its own wont find the G6, you need uppercut installed and run via this to find your device.
If your computer is finding the device I cant see why uppercut wouldn't.

basicreece said:
Are you using uppercut with lg up? LG UP on its own wont find the G6, you need uppercut installed and run via this to find your device.
If your computer is finding the device I cant see why uppercut wouldn't.
Click to expand...
Click to collapse
I have Uppercut v1.0.0.0 and it shows that 'There is no handset connected. Please, connect a handset(s)'
My LG UP version is 1.14.3
Drivers are of course installed (LG-Mobile-Driver_v4.2.0.0)
edit: if somebody knows how to do it and wants to help, I could share my TeamViewer data

ADB and fastboot installed?
Tried booting to recovery?

Hello there,
unfortunately your phone = scrap metal now.
Your only hope would be if some box vendor like infinity or octoplus, has managed crack the bootloader of your particular phone.
See if you can get service/remote service from anyone (or a business) who owns such box. Some msm8996 devices are supported it seems.
The current leaked versions of BoardDiag does not work on newer SoC's.

askermk2000 said:
Hello there,
unfortunately your phone = scrap metal now.
Your only hope would be if some box vendor like infinity or octoplus, has managed crack the bootloader of your particular phone.
See if you can get service/remote service from anyone (or a business) who owns such box. Some msm8996 devices are supported it seems.
The current leaked versions of BoardDiag does not work on newer SoC's.
Click to expand...
Click to collapse
Why do you thing it's a 'scrap metal' now? PC detects it, my only issue is dload mode error which I can't get rid of.

Sernio said:
Why do you thing it's a 'scrap metal' now? PC detects it, my only issue is dload mode error which I can't get rid of.
Click to expand...
Click to collapse
Can you enter download mode or bootloader mode on the phone?. Does ADB sees your phone as connected device? Can you post some pictures.

Dejan Kruljac said:
Can you enter download mode or bootloader mode on the phone?. Does ADB sees your phone as connected device? Can you post some pictures.
Click to expand...
Click to collapse
I can't enter nothing, phone got black screen and does not react to anything. It is charging (battery died tonight, I connected it to charger for 2 hours and now PC is detecting it) and it's only this. All screenshots I could do are posted in my 1st post (quectel qdloader 9008 in devices menager)

Sernio said:
I can't enter nothing, phone got black screen and does not react to anything. It is charging (battery died tonight, I connected it to charger for 2 hours and now PC is detecting it) and it's only this. All screenshots I could do are posted in my 1st post (quectel qdloader 9008 in devices menager)
Click to expand...
Click to collapse
Try asking for help in Telegram group.. There's some people that might help you if this is fixable.
https://t.me/joinchat/ElHlskRW3-pd7_qdDRZQhw

https://forum.xda-developers.com/tmobile-g6/how-to/reward-donation-hard-brick-lg-g6-h872-t3776163 for all people with hard brick

I dont understand, how did you hard brick your phone?

https://www.google.ca/amp/s/forum.x...opment/guide-fixing-hard-bricks-t3403868/amp/
You also need G6 tot files as the guides tot files are for the L70 I believe.

Were you able to solve your problem? I am in a similar situation (see below)
"After trying to update my LG G6 (H870DS) via LG Bridge I got a bootloop issue, with no possibility to go out (even a hard reset was impossible to perform). Then I tried to flash the device using LG Up and stock KDZ file, which result in a cryptic error message in my PC, and a device sudden death. Phone it´s 100% dead, LG Bridge/ LG Up don´t detect the phone, I can´t turn it on (not even download mode). I tried to charge the phone, it becames slightly hot (hope signal?).
I can't even find the qualcomm device in the windows device manager. I think I tried to flash the wrong KDZ File:
I flashed H870DS10m_00_OPEN_HK_DS_OP_1019.kdz
and now I think that the correct kdz File for my H870DS HONG KONG was: H870DS10b_00_OPEN_HK_DS_OP_0406.kdz
Uppercut and ADB are not detecting my G6 either.
The thing is that, for several reasons, I have no warranty, that means I have nothing to lose and I am ready to open the phone, shortcircuit the processor or whatever it could work. Any suguestions what to do now in order to bring the phone back to live?"

i fix my hard brick qualcomm 9008 with octoplus pro jtag on my h871, nobody know how to fix hard brick for any lg g6..and this is horrible! and i ask my self how is that possible that we cannot found a solution for debrick the lg and after how is that possible that there isn't any kdz for the h871 model

if the device it's not even recognized in my PC, do you think your method will work? Bootloader is locked (everything it's stock)

Hello,
LG Service repaired my phone as varranty.

Need some help for a bricked pure

I have not touched this phone in a year, so forgive me if im rusty.
I embarked on a project of compiling slimroms 7.1.2 for this device a year ago, and made a rom that made it onto the device. Now, Here is my mistake. At the time when i built the rom, the nougat bootloader for this device was not out yet(i think, as my bootloader is on a0.4d aka dated 2016-11-30) Giddy that i had finally built a custom rom that worked, i hurriedly flashed the device through the recovery(twrp at the time) and thats when the issues happened. The device will not charge past 1 percent, and in an effort to fix, without knowing that my outdated bootloader was the issue, i decided that installing stock recovery was the best option. BIG MISTAKE. as i now cannot flash anything in recovery. i keep getting signature verification failures and what not.
With that backstory out of the way, here is my issue. I cannot flash anything in fastboot, because when i connect the device to windows i get
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
Yes i have updated the drivers and when i install the motorola drivers manually i get this:
Code:
This device cannot start. (Code 10)
A request for the USB device descriptor failed.
this is the single most thing that is keeping me from reviving this device. I have tried using linux, but the device just doesnt show up. I have tried multiple usb cables. so i know thats not the issue. any help would be very appreciated.
UPDATE: i have done some digging around and no loader files are working. (using a 32gig class 10 microsd). Also, It is on stock recovery so i cannot flash anything other than stock images, which if i am correct, none are recovery flashable, only the otas are. When i try to flash an ota it doesnt work because it is expecting stock apps in system, which are not there since i am on a slimrom rom.
TLDR: i have stock bootloader and recovery, (24.49-18-8/4) but have a non rooted slimrom 7.1.2 which shows up in windows as get device descriptor failed(unknown device). if there was a way to root slimrom 7.1 without usb and with stock recovery that would help alot.

Have you tried the method to revive the phone in Qualcom mode (error 9008)?

mr_5kool said:
Have you tried the method to revive the phone in Qualcom mode (error 9008)?
Click to expand...
Click to collapse
Can you link me to a thread that has that info please?
When I am in bootloader and hit the power button on the qcom option my phone just boots into the slimroms option with no change in the USB side

Here you are
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860

mr_5kool said:
Here you are
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
Click to expand...
Click to collapse
So my issue is worse than that. It shows up on the computer as "device descriptor get failed" so I am unableble to use that method unless I can force it into qdloader mode

Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA

mr_5kool said:
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
Click to expand...
Click to collapse
When i try to install this driver, it says that it is incompatable for my device
I will try again when i get home tomorrow though

mr_5kool said:
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
Click to expand...
Click to collapse
Alright, When i try to install this driver i get this
View attachment 4594365
And this is the error i have on any machine
View attachment 4594369

{
"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"
}
I don't know what happened to your PC. But it is successfully installed here. The worst problem we (mosy of us) had met was error 9008. If your phone cannot be solved by this way, I'm sorry that I can't help much!

mr_5kool said:
I don't know what happened to your PC. But it is successfully installed here. The worst problem we (mosy of us) had met was error 9008. If your phone cannot be solved by this way, I'm sorry that I can't help much!
Click to expand...
Click to collapse
its quite alright. i think that i bricked the phone while trying to use an unsupported bootloader, therefore bricking the mainboard
Its noones fault but my own, so i will chalk this one up to a loss lol