Related
Hi.
I have a cracked screen (soon to be fixed) Dell Streak 5.
When I connect it to my PC it detects it as USB Input device and install the driver for it.
If I try to change the driver and use QDL Tool Windows says the @location does not have hardware information). I tried Windows 7 and XP with the same results.
MAC and Linux detects it as Qualcomm but there is nothing I can do as there is no ADB server nor FASTBOOT.
The only post regarding this does not have any replies so I dont know what to do.
Best Regards.
Anyone knows? A little help would be appreciated.
where did you get the drivers?
Maybe you can get the dell drivers or load the SDK for android it will install drivers too.
What is the end result you want?
alperin1 said:
where did you get the drivers?
Maybe you can get the dell drivers or load the SDK for android it will install drivers too.
What is the end result you want?
Click to expand...
Click to collapse
I have Android SDK installed, which works properly with other phones.
My question is why does my Streak is recognized as a USB Input Device?
Is it normal?
To get my streak working I had to install dell drivers (got it via here just click on downloads tab and install software but don't launch program after drivers have installed http://www.unlockstreak.com/pages/d...?ref=874b1d7212afe8cc4672f2f53d9976c12a5ea0e5).
After this I launched QDL Tool held vol up and inserted usb cable which launched Qualcomm HS-USB 9002 driver which won't be found, you need to go to drivers which should be in a folder that comes with QDL Tool.
So should go as Drivers - Driver_2.067 - Win 32 (or 64 if your running a 64 bit system) - Whatever OS you are running - qcser - Select 2nd option of Qualcomm Drivers and search for Qualcomm HS-USB 9002 should install when you double click on it and should be ready to go.
Check if QDL Tool has recognised driver via communications port if not close down and reopen.
Click on RUN if driver success and should start restoring Streak, should know when complete as it goes green when done and good.
Note: When installing driver have to manually install it so a case of Update Driver, Browse my computer, Let Me pick, Have Disk, Browse when it shows path to select, then go to path whever QDL is extracted (eg Desktop) and follow folder paths above to get it installed.
Hope this is clear and also hope it helps!!! Good Luck
passion8059 said:
To get my streak working I had to install dell drivers (got it via here just click on downloads tab and install software but don't launch program after drivers have installed http://www.unlockstreak.com/pages/d...?ref=874b1d7212afe8cc4672f2f53d9976c12a5ea0e5).
After this I launched QDL Tool held vol up and inserted usb cable which launched Qualcomm HS-USB 9002 driver which won't be found, you need to go to drivers which should be in a folder that comes with QDL Tool.
So should go as Drivers - Driver_2.067 - Win 32 (or 64 if your running a 64 bit system) - Whatever OS you are running - qcser - Select 2nd option of Qualcomm Drivers and search for Qualcomm HS-USB 9002 should install when you double click on it and should be ready to go.
Check if QDL Tool has recognised driver via communications port if not close down and reopen.
Click on RUN if driver success and should start restoring Streak, should know when complete as it goes green when done and good.
Note: When installing driver have to manually install it so a case of Update Driver, Browse my computer, Let Me pick, Have Disk, Browse when it shows path to select, then go to path whever QDL is extracted (eg Desktop) and follow folder paths above to get it installed.
Hope this is clear and also hope it helps!!! Good Luck
Click to expand...
Click to collapse
Thanks for your info but it's not helping.
It seems than something else was damaged when I cracked the screen because it never detects "Qualcom..."
Best Regards.
Hi I recomend taking your sd card out and put that directly into your pc and if you cant do that maybe borrow a friends smartphone or card reader.
Sent from my Dell Streak using XDA Premium App
stevepork said:
Hi I recomend taking your sd card out and put that directly into your pc and if you cant do that maybe borrow a friends smartphone or card reader.
Sent from my Dell Streak using XDA Premium App
Click to expand...
Click to collapse
Problem fixed!!
The phon had the Volume and Power Flex ripped off, so the phone did not power.
I replaced it and the phone is running now.
Best Regards and thanks to you all.
PLEASE! I need to load a new ROM into my MT6575 phone using Smart Phone Flash tool.
I've installed the Mediatek drivers on 4 different computers in my house (Vista, Window 7, Windows 7 64bit, Windows 8) and I cant get ANY of them to work!!
When I look under Ports (COM and LPT) in Device Manager, I ALWAYS get: This device cannot start. (Code 10)
WHAT is going on!! I've wasted so much time with this problem.
johnnysnavely said:
PLEASE! I need to load a new ROM into my MT6575 phone using Smart Phone Flash tool.
I've installed the Mediatek drivers on 4 different computers in my house (Vista, Window 7, Windows 7 64bit, Windows 8) and I cant get ANY of them to work!!
When I look under Ports (COM and LPT) in Device Manager, I ALWAYS get: This device cannot start. (Code 10)
WHAT is going on!! I've wasted so much time with this problem.
Click to expand...
Click to collapse
your not the only one with this problem i have it too with same mt6575 someone help please
Need to uninstall device and reinstall drivers
If you google, "Code 10", you will find that on a Windows system it is an error code generated by the Device Manager "because it can not start a device". In a nut shell, the most likely cause for this is because the device was not properly installed with the right drivers.
If you are running Windows, you can try to use the attached file called USBReview to see what device that is as you know it is your phone. Basically, with this program you can remove all the old drivers and start all the driver installation again.
Try to find your phone either here on xda, on the web or contact your phone's manufacturer - you need drivers!!!
Good luck, Mr. Phelps.
johnnysnavely said:
PLEASE! I need to load a new ROM into my MT6575 phone using Smart Phone Flash tool.
I've installed the Mediatek drivers on 4 different computers in my house (Vista, Window 7, Windows 7 64bit, Windows 8) and I cant get ANY of them to work!!
When I look under Ports (COM and LPT) in Device Manager, I ALWAYS get: This device cannot start. (Code 10)
WHAT is going on!! I've wasted so much time with this problem.
Click to expand...
Click to collapse
ronbo76 said:
If you google, "Code 10", you will find that on a Windows system it is an error code generated by the Device Manager "because it can not start a device". In a nut shell, the most likely cause for this is because the device was not properly installed with the right drivers.
If you are running Windows, you can try to use the attached file called USBReview to see what device that is as you know it is your phone. Basically, with this program you can remove all the old drivers and start all the driver installation again.
Try to find your phone either here on xda, on the web or contact your phone's manufacturer - you need drivers!!!
Good luck, Mr. Phelps.
Click to expand...
Click to collapse
Your USB program does give a lot of information I have never seen before, but I still haven't been able to figure out how to get the driver to load.
thanks, John
I'm having the same problem installing the MT6575 USB VCOM drivers. Is there a workaround to get this installed? I"m using WIN 6 64bit
johnnysnavely said:
PLEASE! I need to load a new ROM into my MT6575 phone using Smart Phone Flash tool.
I've installed the Mediatek drivers on 4 different computers in my house (Vista, Window 7, Windows 7 64bit, Windows 8) and I cant get ANY of them to work!!
When I look under Ports (COM and LPT) in Device Manager, I ALWAYS get: This device cannot start. (Code 10)
WHAT is going on!! I've wasted so much time with this problem.
Click to expand...
Click to collapse
This is what worked for me after lot of experimenting and searching:
- get MTK6575 drivers (for instance from Bruno Martins where he writes about flashing mtk6575 - google: MT6575 flashing tutorial bruno
- Start c/windows/system32/hdwwiz.exe (as admin)
- Click next
- Manually select hardware
- List all devices
- Select the driver (for example usb2ser_Win764.inf)
- from the List select "MediaTek Preloader USB VCOM Port"
(or you can install other drivers from the list if Preloader is not enough..)
On another computer I solved it by installing whole Android SDK, checked my android system and installed updated for SDK (approx. 2 GB) and it installed correct drivers automatically.
Also you can experiment with using another usb port..
Please write here if it helped.
ivy13 said:
This is what worked for me after lot of experimenting and searching:
- get MTK6575 drivers (for instance from Bruno Martins where he writes about flashing mtk6575 - google: MT6575 flashing tutorial bruno
- Start c/windows/system32/hdwwiz.exe (as admin)
- Click next
- Manually select hardware
- List all devices
- Select the driver (for example usb2ser_Win764.inf)
- from the List select "MediaTek Preloader USB VCOM Port"
(or you can install other drivers from the list if Preloader is not enough..)
On another computer I solved it by installing whole Android SDK, checked my android system and installed updated for SDK (approx. 2 GB) and it installed correct drivers automatically.
Also you can experiment with using another usb port..
Please write here if it helped.
Click to expand...
Click to collapse
Tried your first method but still get Code 10 error. Could not understand your second method. Please help. Me device is Qmobile Noir A2
hye.. any progress? am having the same issue.. just for MTK6575 com port driver
Just made my Amoi N820 work
So happy
You get Code 10 becouse your windows couldn't recognize the driver but that's irrelevant becouse flashing will work
No solution?
Any solution on this problem?
I've this china mt6575 galaxy s3 clone and got rooted using CF Root.Got ADB composite driver successfully installed in my pc (using win7 32-bit).When I install preloader usb vcom driver, i'm also facing this 'code 10' issue.Until now I can't install CWM in my phone.(the Flash Tool cannot detect my device).i try to install/push CWM using Terminal Emulator but nothing seems to change .when reboot into recovery mode the same stock recovery appear.Any help please?
orion~X said:
Any solution on this problem?
I've this china mt6575 galaxy s3 clone and got rooted using CF Root.Got ADB composite driver successfully installed in my pc (using win7 32-bit).When I install preloader usb vcom driver, i'm also facing this 'code 10' issue.Until now I can't install CWM in my phone.(the Flash Tool cannot detect my device).i try to install/push CWM using Terminal Emulator but nothing seems to change .when reboot into recovery mode the same stock recovery appear.Any help please?
Click to expand...
Click to collapse
i have thet problem to.
is ther solution?
I HAVE SOLUTION FOR THIS PROBLEM!!
Just ignore the error Code 10! Start the SPFlashtool and load the scatterfile, click on download and connect your switch off Phone with the computer. It will work fine.
Having the Same Problem
I understand I can ignore it and it works on that part, however I'm trying to root my phone now and it's not recognising that I have attached a device to the computer. Please need help to solve the problem. Have the drivers but can't get it without code 10
Hi.
me test for me not work.
iphone 4s.
plz help me.
hihi2u2 said:
I understand I can ignore it and it works on that part, however I'm trying to root my phone now and it's not recognising that I have attached a device to the computer. Please need help to solve the problem. Have the drivers but can't get it without code 10
Click to expand...
Click to collapse
Did you ever get this problem solved as I have the same issue with an MTK 6592 chip based phone?
I have the same problem too.
Installation of Media Tek preloaded drivers gives me Code 10 error.
Has anyone found the solution?
my phone is totally dead without power now after I tried to flash with SP Flash tool using correct ROM. I noticed in device manager that there is a CODE 10 error in mediatek preloader usb driver.. is this the culprit? my phone can no longer be detected now in SPFlash or MTK Droid tools... so hopeless... this is a brandnew phone I bought to be given as gift to my cousin...
I did it! I did it! I did it!
The solution is... we need not MediaTek USB VCOM (Android) (USB\VID_0BB4&PID_0005&MI_02), but PreLoader USB VCOM Port (USB\Vid_0e8d&Pid_2000) !
I have MTK6582 (KingSing S2), the host - WinXPx64.
It looks like my phone (and, maybe, other MTK devices too) have several engineering modes.
I have spent several hours trying to get working VID_0BB4&PID_0005&MI_02, which is exposed, if device is turned on while holding VOL- pressed. In this mode some strange factory mode with nonfunctional menu items is displayed on the screen. But to activate mode with Vid_0e8d&Pid_2000 some trickery is necessary.
Sometimes this USB interface starts repeatedly to appear and disappear every half-second in infinitive loop. I had such situation once, when connected turned off phone to USB cable with battery removed.
I just literally catched MT65xx Preloader by double clicking on it in windows device manager and pressing "install drivers" in it's properties. I have used Driver_Auto_Installer_v1.1236.00\SmartPhoneDriver\x64\Infs\usbvcom.inf from http://spflashtool.com/download/Driver_Auto_Installer_v1.1236.00.zip. DriverVer = 12/24/2011, 2.0000.0.0
After clicking "Read Back" in Flash Tool this insane loop stopped and program started to function as intended.
This interface could also appear once and for very short moment, if turned off phone (with battery inserted) is just connected to host. Also it could be seen again, if power button is pressed. If "Download" or "Read Back" is not pressed in advance in Flash Tool, than boot will continue after smaller than a second pause (if device is functional).
I don't know if running Install.bat (from archive I have given above) is necessary. It didn't installed driver when Vid_0e8d&Pid_2000 wasn't active, but, I guess, running it during short blinks would give the same effect.
Also, I don't know, if advice given in comment#6 in this thread four years ago would work. Maybe, the fault was in older version of driver (DriverVer=05/30/2011,1.1123.0).
Another reason could be that necessary USB interface disappears before windows manages to install driver for it for the first time. Possibly, only if "catched" in device manager, user could manually assign driver to it.
I've been struggling with my UMI Rome for days. It has/had the black screen problem, sometimes won't enter recovery mode, sometimes wouldn't allow charge, sometimes works just fine (yesterday). Last night i mistakenly cut off power during a battery recharge. -- today it has all the above problems (bricked) so I am trying doing a flashing again using the tutorials and tools on the Tehnotone.com site. Sintetix's reply above helps me at least have a better clue on what is going on. Wish me luck! BTW, I am using a Dell Windows 10 pc. (Results to be reported here.)
Sintetix said:
The solution is... we need not MediaTek USB VCOM (Android) (USB\VID_0BB4&PID_0005&MI_02), but PreLoader USB VCOM Port (USB\Vid_0e8d&Pid_2000) !
I have MTK6582 (KingSing S2), the host - WinXPx64.
It looks like my phone (and, maybe, other MTK devices too) have several engineering modes.
I have spent several hours trying to get working VID_0BB4&PID_0005&MI_02, which is exposed, if device is turned on while holding VOL- pressed. In this mode some strange factory mode with nonfunctional menu items is displayed on the screen. But to activate mode with Vid_0e8d&Pid_2000 some trickery is necessary.
Sometimes this USB interface starts repeatedly to appear and disappear every half-second in infinitive loop. I had such situation once, when connected turned off phone to USB cable with battery removed.
I just literally catched MT65xx Preloader by double clicking on it in windows device manager and pressing "install drivers" in it's properties. I have used Driver_Auto_Installer_v1.1236.00\SmartPhoneDriver\x64\Infs\usbvcom.inf from http://spflashtool.com/download/Driver_Auto_Installer_v1.1236.00.zip. DriverVer = 12/24/2011, 2.0000.0.0
After clicking "Read Back" in Flash Tool this insane loop stopped and program started to function as intended.
This interface could also appear once and for very short moment, if turned off phone (with battery inserted) is just connected to host. Also it could be seen again, if power button is pressed. If "Download" or "Read Back" is not pressed in advance in Flash Tool, than boot will continue after smaller than a second pause (if device is functional).
I don't know if running Install.bat (from archive I have given above) is necessary. It didn't installed driver when Vid_0e8d&Pid_2000 wasn't active, but, I guess, running it during short blinks would give the same effect.
Also, I don't know, if advice given in comment#6 in this thread four years ago would work. Maybe, the fault was in older version of driver (DriverVer=05/30/2011,1.1123.0).
Another reason could be that necessary USB interface disappears before windows manages to install driver for it for the first time. Possibly, only if "catched" in device manager, user could manually assign driver to it.
Click to expand...
Click to collapse
I tried what you said. It wouldn't install properly. It kept saying error (code 10) and showed in device management with a caution sign every time I installed the driver. I disabled the forced driver signature thingamabop but it still does it. I guess I'm screwed. Has anyone else fixed this?
Hello,
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
Thanks
----How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
petoxxx said:
Hello,
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
Thanks
----How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
Click to expand...
Click to collapse
mine is not working i think mine is bricked completly
bricked my mobile...Help!!!!
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
sivakarthick said:
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
Click to expand...
Click to collapse
The thread called 'Problem with huawei vision' still seems to be active. You may want to try asking your question over there.
Huawei (u8850) unbricked
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
how to turn off huawei u8850 completely
hey,could you please help me.i am stuck on huawei logo.how can i turn off the phone completely.i cant remove the battery obviously.the above trick isnot working.plz.help me
bikeshrt said:
hey,could you please help me.i am stuck on huawei logo.how can i turn off the phone completely.i cant remove the battery obviously.the above trick isnot working.plz.help me
Click to expand...
Click to collapse
it's actually not difficult to remove the battery...
but i read somewhere the 'volume-up + power for five seconds' will hard restart, but re-press power immediately will then turn it off (not tested myself; the back of mine is already off at the moment.)
Anyone here interested in developing a 3.x kernel? seems other phones with msm8255 have successfully got one...
u8850 power off
btsimonh said:
but i read somewhere the 'volume-up + power for five seconds' will hard restart, but re-press power immediately will then turn it off (not tested myself; the back of mine is already off at the moment.)
Click to expand...
Click to collapse
now i have tried it, and no success.
However, what i have found to work - if your non-boot is actually booting the kernel, but failing to initialise the phone, then you can still use adb with it... I ran adb shell, and then used 'poweroff' to power off my phone, which then meant i could boot into CWM recovery....
i HAVE THE SAME PROBLEME? PLEASE CAN U HELP ME TO SOLVE IT BY GIVING ME DETAILS.
it is working, thank you bro
btsimonh said:
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
Click to expand...
Click to collapse
it is working thanks bro
Stock rom download plz.
btsimonh said:
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
Click to expand...
Click to collapse
HOLY GOD! F**K ME!!! I finally did it! THANKS A LOT, BRO! YOU'RE AWESOME!!!
Hi,
I tried converting my Dell Venue 8 into a dev-edition device by following the official Dell instructions. I was able to flash boot, recovery and system images but when I rebooted the device, all I see is black screen with a USB icon on it. Please suggest a fix if you came across this.
hey
http://forum.xda-developers.com/showpost.php?p=51090040&postcount=2
Use this
Open part1.bat
Plug your device
And push power button
If closed cmd your device is reboot
And flash part2.bat
rb512 said:
Hi,
I tried converting my Dell Venue 8 into a dev-edition device by following the official Dell instructions. I was able to flash boot, recovery and system images but when I rebooted the device, all I see is black screen with a USB icon on it. Please suggest a fix if you came across this.
Click to expand...
Click to collapse
You need to flash the firmware first using the xftsk and isoc. This will unlock the bootloader to boot an unsigned boot.img. Follow the instructions provided in "Dell Tablet Install Instructions.docx" and you will be able to revive the system.
No luck
rperi3679 said:
You need to flash the firmware first using the xftsk and isoc. This will unlock the bootloader to boot an unsigned boot.img. Follow the instructions provided in "Dell Tablet Install Instructions.docx" and you will be able to revive the system.
Click to expand...
Click to collapse
Well, windows can't detect my tablet anymore. Neither adb devices or fastboot devices show anything. Also, under device manager, my tablet shows as CLOVERVIEW. If I reboot in bootloader, it shows as Android-Phone. I tried updating my drivers again, but that didn't work either.
rb512 said:
Well, windows can't detect my tablet anymore. Neither adb devices or fastboot devices show anything. Also, under device manager, my tablet shows as CLOVERVIEW. If I reboot in bootloader, it shows as Android-Phone. I tried updating my drivers again, but that didn't work either.
Click to expand...
Click to collapse
Try re-enabling the developer mode on the tablet.
bshankar7546 said:
Try re-enabling the developer mode on the tablet.
Click to expand...
Click to collapse
Well, dev mode is on. I can see the device from my linux machine, but not from windows.
rb512 said:
Well, dev mode is on. I can see the device from my linux machine, but not from windows.
Click to expand...
Click to collapse
New instructions are updated in the dell website. I am assuming that your tablet is still in a bricked state. In order to revive the tablet,
a) make sure you install the xftsk and isoc drivers on your windows machine.
b) unplug usb cable of device from the computer.
c) unzip the downloaded files and run the setup_part1_xfstk.bat.
d) now plug in the usb cable from tablet into your computer.
This will flash the firmware on the device and you will get into fastboot mode. IN case the tablet does not get flashed repeat steps b, c and d.
From the fastboot window go to reboot and likely the tablet will boot up. Let us know how it went. If you get stuck then post the screen shot of where you got stuck and will try to help.
Thanks, still no luck
rperi3679 said:
New instructions are updated in the dell website. I am assuming that your tablet is still in a bricked state. In order to revive the tablet,
a) make sure you install the xftsk and isoc drivers on your windows machine.
b) unplug usb cable of device from the computer.
c) unzip the downloaded files and run the setup_part1_xfstk.bat.
d) now plug in the usb cable from tablet into your computer.
This will flash the firmware on the device and you will get into fastboot mode. IN case the tablet does not get flashed repeat steps b, c and d.
From the fastboot window go to reboot and likely the tablet will boot up. Let us know how it went. If you get stuck then post the screen shot of where you got stuck and will try to help.
Click to expand...
Click to collapse
Thanks, but xfstk cannot find my device anymore. I can still get into fastboot and push the img files. Please see attached screenshots.
Dell Venue 8 successfully rooted!
I spoke with social-design-concepts and he helped solve my problem. It turns out my xfstk version (1.0.2) was incorrect, he sent the right one and I was able to unlock the bootloader and flash my tablet. It's rooted and working fine now.
Attached is the xfstk version used by social-design-concepts.
rb512 said:
I spoke with social-design-concepts and he helped solve my problem. It turns out my xfstk version (1.0.2) was incorrect, he sent the right one and I was able to unlock the bootloader and flash my tablet. It's rooted and working fine now.
Attached is the xfstk version used by social-design-concepts.
Click to expand...
Click to collapse
The correct version of xfstk is now part of the updated zip package on dell website. It was inadvertently left out of the package. GLad to see that you are now rooted. Also note that the kernel sources are posted and you can build your own kernel and flash it since this process unlocked the bootloader also.
rperi3679 said:
The correct version of xfstk is now part of the updated zip package on dell website. It was inadvertently left out of the package. GLad to see that you are now rooted. Also note that the kernel sources are posted and you can build your own kernel and flash it since this process unlocked the bootloader also.
Click to expand...
Click to collapse
I'm having a hell of a time with this.
The version included in the Dell package is 1.0.3
However you are saying I need to use 1.0.2 ?
I am having no luck, every time it will not detect my device.
Also the other issue is that the included xFSTK-downloader-setup-1.4.2 will not work. Both Windows 8.1 and Windows 7 say its invalid and will not install it. So I found a version of xfstk-dldr-solo.exe from the internet to use.
So my issue is either the wrong iSOC drivers or the wrong xFSTK version or both.
Either way, the provided Dell instructions do not work.
Any ideas?
Scotty_T said:
I'm having a hell of a time with this.
The version included in the Dell package is 1.0.3
However you are saying I need to use 1.0.2 ?
I am having no luck, every time it will not detect my device.
Also the other issue is that the included xFSTK-downloader-setup-1.4.2 will not work. Both Windows 8.1 and Windows 7 say its invalid and will not install it. So I found a version of xfstk-dldr-solo.exe from the internet to use.
So my issue is either the wrong iSOC drivers or the wrong xFSTK version or both.
Either way, the provided Dell instructions do not work.
Any ideas?
Click to expand...
Click to collapse
First of all, Dell's instructions didn't work for me either, so I used the version from social-design-concepts, who also packed in supeSU in the system image. He's zipped the modified files and you can find it here :
http://forum.xda-developers.com/show...40&postcount=2
Once you download that version, you can proceed with these steps.
1) Flash the tablet (i.e. run step2.bat) first. This will soft brick your tablet (you'll see a USB icon as attached in my previous post), but don't panic.
2) Next, unplug your tablet from your machine, uninstall all versions of xfstk-iSoc drivers and install the one attached in my post. Once done, you'll see Cloverview Plus Device under iSoc Intel Driver in your Device Manager.
3) Unplug the tablet if it's already connected to your pc, run step1.bat, plug your tablet back in to your pc and your tablet's bootloader will be unlocked.
4) Reboot your tablet in bootloader (Hold down power and volume down) and run step2.bat
This will root your tablet and install android 4.3.
I've tested this on two Dell Venue 8 tablets running 4.2.2 and it worked like a charm.
rb512 said:
First of all, Dell's instructions didn't work for me either, so I used the version from social-design-concepts, who also packed in supeSU in the system image. He's zipped the modified files and you can find it here :
http://forum.xda-developers.com/show...40&postcount=2
Once you download that version, you can proceed with these steps.
1) Flash the tablet (i.e. run step2.bat) first. This will soft brick your tablet (you'll see a USB icon as attached in my previous post), but don't panic.
2) Next, unplug your tablet from your machine, uninstall all versions of xfstk-iSoc drivers and install the one attached in my post. Once done, you'll see Cloverview Plus Device under iSoc Intel Driver in your Device Manager.
3) Unplug the tablet if it's already connected to your pc, run step1.bat, plug your tablet back in to your pc and your tablet's bootloader will be unlocked.
4) Reboot your tablet in bootloader (Hold down power and volume down) and run step2.bat
This will root your tablet and install android 4.3.
I've tested this on two Dell Venue 8 tablets running 4.2.2 and it worked like a charm.
Click to expand...
Click to collapse
FINALLY - it worked.
Appreciate the help
Scotty_T said:
FINALLY - it worked.
Appreciate the help
Click to expand...
Click to collapse
yep, no problem!
rb512 said:
First of all, Dell's instructions didn't work for me either, so I used the version from social-design-concepts, who also packed in supeSU in the system image. He's zipped the modified files and you can find it here :
http://forum.xda-developers.com/show...40&postcount=2
Once you download that version, you can proceed with these steps.
1) Flash the tablet (i.e. run step2.bat) first. This will soft brick your tablet (you'll see a USB icon as attached in my previous post), but don't panic.
2) Next, unplug your tablet from your machine, uninstall all versions of xfstk-iSoc drivers and install the one attached in my post. Once done, you'll see Cloverview Plus Device under iSoc Intel Driver in your Device Manager.
3) Unplug the tablet if it's already connected to your pc, run step1.bat, plug your tablet back in to your pc and your tablet's bootloader will be unlocked.
4) Reboot your tablet in bootloader (Hold down power and volume down) and run step2.bat
This will root your tablet and install android 4.3.
I've tested this on two Dell Venue 8 tablets running 4.2.2 and it worked like a charm.
Click to expand...
Click to collapse
Right, so at some point tonight I've gone and screwed up, and now i'm stuck. I've followed the instructions here, but I keep encountering the same error I was earlier.
This is right after the firmware download, the device is showing a usb symbol. Everytime I try to run step1_setup_xfstk this happens. A bit after that's shut down, my device goes to an Intel Inside screen until I shut it down. Can anybody tell me where I went wrong and how to fix it?
What is your xfstk-iSoc version?
rb512 said:
What is your xfstk-iSoc version?
Click to expand...
Click to collapse
I downloaded and installed the 1.0.2 version attached to your april 5th post. Actual version listed in the ISoc driver properties is 11.0.0.0
pleaaaseeee
hello friend am from Ecuador . I have the Same Problem I would like to know a way to revive my tablet 3830
rb512 said:
First of all, Dell's instructions didn't work for me either, so I used the version from social-design-concepts, who also packed in supeSU in the system image. He's zipped the modified files and you can find it here :
http://forum.xda-developers.com/show...40&postcount=2
Once you download that version, you can proceed with these steps.
1) Flash the tablet (i.e. run step2.bat) first. This will soft brick your tablet (you'll see a USB icon as attached in my previous post), but don't panic.
2) Next, unplug your tablet from your machine, uninstall all versions of xfstk-iSoc drivers and install the one attached in my post. Once done, you'll see Cloverview Plus Device under iSoc Intel Driver in your Device Manager.
3) Unplug the tablet if it's already connected to your pc, run step1.bat, plug your tablet back in to your pc and your tablet's bootloader will be unlocked.
4) Reboot your tablet in bootloader (Hold down power and volume down) and run step2.bat
This will root your tablet and install android 4.3.
I've tested this on two Dell Venue 8 tablets running 4.2.2 and it worked like a charm.
Click to expand...
Click to collapse
Link does not work. Where I can download these files?
Dell Venue 8 3840
I have the Dell Venue 8 3840 and I am trying to follow Dells instructions based on this post http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
I can see my device in ADB or Fastboot depending on how I boot but after clicking Begin Download in xFSTK_downloader_1.5.1 nothing happens. The instructions in the thread and "http://forum.xda-developers.com/showpost.php?p=51090040&postcount=2" are for the 3840; I do not think they will work for the 3840, I am correct?, and do you have any ideas on how to get my 3840 to root? In the post referenced above How to root Android 4.4.4 on the Dell Venue 3840 (Merrifield) Tablet is says to try this
Note on XFSTK: if you have trouble getting XFSTK to download properly, try:
Turn off the device (hold power button for 10 seconds.)
Press the Start Download button in XFSTK.
With USB cable connected, turn tablet on with Power + Volume Up.
When I do this Power+Volume Up the device will not power on.
Thanks for any help Mike
Hi all, I will try to be as detailed as possible.
I have a MetroPCS LG MS323 which I bought as a second phone to use when I travel as my regular phone is CDMA and I wanted a GSM phone that I could use with a sim card. While on an overseas trip I paid a cellphone place to unlock the phone so I could use other carriers' sim card, it was working fine since then. However, as I don't use the phone on a regular basis it ended up sitting and the battery lost its charge. When I tried to charge it by usb, it started bootlooping (vibrate, LG logo, repeat). After that I pulled the battery and charged it using an external charger. The phone is not rooted. I tried the factory reset key combo, but it gets stuck on the screen which says factory reset processing........ endlessly. I tried to download kdz file and flash with LG flash tool but phone cannot get into download mode. When I press vol key and plug usb cable, it says LOADING.......... press volum up key until download mode starts But it gets stuck there and download mode never starts.
I downloaded adb and fastboot to a Windows 7 laptop, and LG drivers, but when I connect phone and open a terminal adb devices shows no phone connected.
I also downloaded Laf.img for this phone and Laf recovery tool for Windows but again I cannot seem to get computer to see the phone. If I try to use the tool it says "waiting for device"
One difficulty is to trying to plug phone to computer the right way.
Most of the threads say to have phone in battery charge mode with usb debugging enabled, but I can't select any settings if the phone is bricked.
If I just plug the phone to usb when it is turned off it shows a picture of battery but no sign of charging, and computer doesn't detect phone.
If I plug phone to usb first, then hold vol and power key the LG logo will go black and it vibrates, in that case sometimes the Windows laptop will see 2 folders, verinfo and image.
When I plug usb cable to Linux computer and phone is off, same thing just picture of battery but terminal only shows sda1 sda2 sda3 etc no sdb no sdc just like not detected.
If I hold vol down then plug usb it vibrates and stuck on LG logo.
I have also tried to plug usb, then press vol down and power until phone vibrates, then try to let go buttons before LG logo shows up. but it doesn't mount.
If I hold vol up and power, then plug usb. it vibrates and goes to LG logo.
Last night somehow I got it to mount on the linux computer but the file manager was going crazy opening multiple windows and a list of folders would show up for a second, disappear and reappear as if the system was trying to read the folders but having difficulty. Today I am not able to get it to mount.
I have downloaded a linux livecd with adb and fastboot, I haven't tried it yet because I am not sure the path to flash an img file from a different directory on the hard drive on the windows laptop.
I have downloaded aboot.img but don't know how I can flash it if I can't see the phone on any computers.
I have spent days searching for solutions but have not seen the exact same problem, other threads suggest things but often the symptoms are slightly different or with a different phone. So, first of all I need to know what kind of brick I have, because other solutions I have seen posted for completely black screen, or phone detected as qhsusb qualcomm etc. which seems like a different problem.
So the 2 main things are 1, to know which kind of brick because many of the solutions I see posted seem like a different problem.
second, what is the best way to plug to computer so I can see the phone?
I burned a live CD of FWUL and ran adb from linux, still says adb devices nothing shows up. usb cable is plugged in and phone is turned off. Am I doing this wrong? I held down power and vol down until phone vibrates and LG logo appears. adb devices - "list of devices attached" still has nothing showing.. I don't know why even in Linux I can't see any device attached. Also I tried with pressing vol up and power until phone vibrates.
ls /dev/sd* only shows sda sda1 sda2 etc
I have also looked at past threads about unlocking the L70 bootloader, but the bootloader.zip no longer links and the phone does not have busybox installed.
I tried to see it Windows Device Manager but it does not show up anywhere.
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
equitube said:
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
Click to expand...
Click to collapse
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
A tiny bit of progress to report, after getting a perfect timing to release the power and vol down keys I was finally able to connect to Windows machine. while waiting for drivers to install it was detected as QHSUSB_BULK in device manager, after drivers loaded now it is listed as LGE AndroidNet USB Serial {port (COM4). However when I run adb I still cannot see an attached device. I will look at solutions for the specific type of brick problem which has now been identified.
fofopuka said:
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
Click to expand...
Click to collapse
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
equitube said:
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
Click to expand...
Click to collapse
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
fofopuka said:
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
Click to expand...
Click to collapse
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
equitube said:
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
Click to expand...
Click to collapse
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
fofopuka said:
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
Click to expand...
Click to collapse
Of course, I had forgotten about that. In order to use fastboot, most flashing tools, you HAVE to have USB debugging on.
There are occasional ways around this, though they are few. I do seem to recall oding it on that LG Leon. OR it may have been a Moto e or G, let me look back at previous threads i've asked for help in.
(Hmm, perhaps taking notes, or just leaving a webcam running while I'm doing a new device might be valuable in the future, I think with remarkable hindsight.) :cyclops:
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
And no, you can't do anything to Android files in Windows, except see them. they are generally a different file system
One of the difficulties is just plugging it to a PC. 9 out of 10 times it is not recognized and nothing happens. So far the only way that seems to occasionally work is to plug the usb cable to the Windows 7 laptop, hold vol down and power, release both as soon as it vibrates. Most of the time I can't get it timed exactly right, but if I'm lucky sometimes Windows will detect the usb connection by following these steps. If I try on a Linux machine nothing happens, phone stays invisible. The most I've gotten with Linux is to charge the battery, but will not mount.
It is just a stock phone, not rooted, no busybox, no developer options enabled.