Hi guys, so sorry for my bad english but i try t explain my problem. One week ago my device is blocked with a led blue and black screen and it dont go in noone mode but only in (i think is that) EDL MODE. I just changr driver of device by pc to work from 900E in HS-USB Qloader 9008. Qfil see device with that driver but dont flash nothing with error ''SAHARA FAIL''. I put one image to allow see you the error. i try all way also with miflash that give me the ''sahara rear end error with status 9 miflash''.
I hope that you help me because i have a lot of documents and image of my work on device. Thx very much.
{
"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"
}
Edl mode specific in one thing. You can start flashing only a few seconds after going into edl. After that qfil will still show phone in edl but flash will fail.
Oriwen said:
Edl mode specific in one thing. You can start flashing only a few seconds after going into edl. After that qfil will still show phone in edl but flash will fail.
Click to expand...
Click to collapse
Yeah this i know, i start download as soon as i connect smartphone to pc. dont work
Restart to edl, connect and flash in shortest possible interval, have everything set-up in qfil in advance. Only connecting to pc is not enough.
mode edl with modified usb
Oriwen said:
Restart to edl, connect and flash in shortest possible interval, have everything set-up in qfil in advance. Only connecting to pc is not enough.
Click to expand...
Click to collapse
Hi, a few days ago i modified a normal cable usb to create rhe cable for edl and work go be fine. now i try flash but there is another error by miflash. in internet dont exit this error so now i dont know what i can i do. thx for answer.
today i had the same issue, qcomm hs-usb 900E,i want to go to the 9008 qlaoder, i don't want to do the driver change, i saw many bad comments about that, i want to try the deepflash cable, i saw some youtube videos about that, can someone tell me if it works on zuk z2 pro, cuz, i saw only threats about zuk z2
i succeeded in puting the phone on qloader mode, but now, i'm have the same issue as you, the device doesn't want to flash the 1.9 rom, even with putting the files in c: path, i don't know what to do :/
Related
On Sony's site, it says to install the android_winusb.inf-file after holding the volume up and inserting the USB but when I do that, Windows says it couldn't install the driver, and then the phones blue LED turns orange. Someone mentioned I need to install the Flashtool drivers first but I can't find it, can someone help?
EDIT: I managed to find the flashtool drivers and I installed it, and still, when I try to install the driver for fastboot, it says it wasn't able to. What do I do?
This is what happens when I try to install the drivers through device manager
{
"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"
}
Try to get the proper drivers with PC companion. After getting the right drivers you will be able to proceed unlocking your phone.
Sent with Tapatalk
eawert said:
Try to get the proper drivers with PC companion. After getting the right drivers you will be able to proceed unlocking your phone.
Sent with Tapatalk
Click to expand...
Click to collapse
So install PC companion > Flashtool drivers > Fastboot?
I tried installing PC Companion and even after, when I tried to install the android_winusb.inf-file it shows the same thing as I mentioned above
EDIT;
Okay, so I think I managed to figure it out, incase someone else has this problem, here's what I did;
Download Flashtool, go to C:\Flashtool\drivers, click the exe file to install the drivers, when it asks what drivers to install choose the "Xperia TX" and the "Fastboot" drivers. Then, press the volume up button and insert the USB and it'll say the fastboot drivers installed correctly and then you can proceed with unlocking your bootloader!
trojan92 said:
EDIT;
Okay, so I think I managed to figure it out, incase someone else has this problem, here's what I did;
Download Flashtool, go to C:\Flashtool\drivers, click the exe file to install the drivers, when it asks what drivers to install choose the "Xperia TX" and the "Fastboot" drivers. Then, press the volume up button and insert the USB and it'll say the fastboot drivers installed correctly and then you can proceed with unlocking your bootloader!
Click to expand...
Click to collapse
This worked for me!
Hi guys,
I'm trying to upgrade to v20a version but I can't get into s/w mod. I did everything as described in this thread. When I plug in the usb cable to my pc, the phone is vibrating and I'm just seeing colored pixels.
I've upgraded and downgraded my phone a few times with the method. Why It's not working now? What am I doing wrong?
I've plugged in my phone without battery.
I held down the volume - and power buttons
KoreaFAN said:
Hi guys,
I'm trying to upgrade to v20a version but I can't get into s/w mod. I did everything as described in this thread. When I plug in the usb cable to my pc, the phone is vibrating and I'm just seeing colored pixels.
I've upgraded and downgraded my phone a few times with the method. Why It's not working now? What am I doing wrong?
I've plugged in my phone without battery.
I held down the volume - and power buttons
Click to expand...
Click to collapse
Maybe you're nervous, just press VOL- and connect the phone to the cable, no power button, thats to enter in recovery when battery is on the phone
If you find yourself in a bootloop or a security error after flash...
See this:
http://forum.xda-developers.com/showpost.php?p=38838927&postcount=7
RuedasLocas said:
Maybe you're nervous, just press VOL- and connect the phone to the cable, no power button, thats to enter in recovery when battery is on the phone
If you find yourself in a bootloop or a security error after flash...
See this:
http://forum.xda-developers.com/showpost.php?p=38838927&postcount=7
Click to expand...
Click to collapse
this is the problem http://youtu.be/1CYxc4mMKaA I've tried with battery and only vol - but kdz flashing tool couldn't detect the phone.
There are two lg modem in the Device Manager and I've disabled them
{
"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 should I do to fix this thing?
KoreaFAN said:
this is the problem http://youtu.be/1CYxc4mMKaA I've tried with battery and only vol - but kdz flashing tool couldn't detect the phone.
There are two lg modem in the Device Manager and I've disabled them
View attachment 1786592
what should I do to fix this thing?
Click to expand...
Click to collapse
To use kdz files you need to connect without battery.
To use .dz (LGFlash tool) you need to connect with the battery on.
I Have Glaxy Tab P1000, installed cm10.1 in it..
i tried to restock my tab with odin and battery ran out in the middle of flashing...
now the state of tab is
it shows phone-computer link screen.. only when i am charging it MOstly It keeps on blinking
removing the charger would turn off the screen imidiately.. 1 in 50 times it stays and can be connected to computer but it wont get recognized by pc
tried to use one click unbrick and odin..( pc just dont show any device connected)
i just cant power on the tab without a charger.. no matter how many keys combinations and time durations.. :/
all i can see is the screen i am posting below
{
"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"
}
Try to boot to download mode (after reinstalling the drivers)
Reflash firmware you are looking for via kies or odin. I ADVISE to look for stock firmware, before flashing any custom roms.
Sent from my tab
nirvana97 said:
Try to boot to download mode (after reinstalling the drivers)
Reflash firmware you are looking for via kies or odin. I ADVISE to look for stock firmware, before flashing any custom roms.
Sent from my tab
Click to expand...
Click to collapse
I am not able to put it into download mode.. the most i can do is just wait for it to stop blinking and quickly put usb into pc... but any software niether oneclick unroot nor odin would show any sign of connection of new device!!
pushkardua said:
I am not able to put it into download mode.. the most i can do is just wait for it to stop blinking and quickly put usb into pc... but any software niether oneclick unroot nor odin would show any sign of connection of new device!!
Click to expand...
Click to collapse
The drivers are probably not installed, or need to be reinstalled.
First, you should try using the zadig.exe driver installer that comes with the Heimdall bundle (just Heimdall, not OneClickUnbrick). Plug in the Tab, Click Options -> List All Devices, then click Samsung USB Composite Device and install the driver. That should most likely make it detectable by OneClickUnbrick.
If that doesn't work, try downloading the Samsung USB Driver for Mobile Phones or Samsung Kies to install the needed drivers.
Finally, you can try getting the drivers to install automatically by plugging in the Tab, then going to your Windows system tray, right-clicking Safely Remove Hardware and opening Devices and Printers. From there, you should try to find your Tab's device listing (it's usually Samsung USB Composite Device), right-click it, and select Remove Device. Then unplug the Tab and plug it in again.
So recently I decided to dust off my Captivate and install a custom recovery on it using Heimdall. I installed the drivers from Zadig and was preparing to flash the recovery when I had to take a break. After plugging the device back in (in download mode) a few hours later, re-installing the drivers, and attempting to flash for the first time, I got an error telling me that no compatible device in download mode was detected. I reconnected the Captivate and went back to Zadig AND Device Manager in Windows to see what was up, and the phone didn't show up in either. I toggled "Hidden devices" in Device Manager and finally got something:
{
"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"
}
As you can see, it failed to connect. I disconnected and reconnected my device multiple times in both normal and download mode, and sometimes it wouldn't show up at all, even with "Hidden devices" on. Whether or not it showed up didn't seem to follow any pattern. I have even tried on multiple Windows machines at this point, getting the same result every time. My phone is working just fine besides this one issue and running the stock ROM. Any help would be appreciated!
j0sh1ng said:
So recently I decided to dust off my Captivate and install a custom recovery on it using Heimdall. I installed the drivers from Zadig and was preparing to flash the recovery when I had to take a break. After plugging the device back in (in download mode) a few hours later, re-installing the drivers, and attempting to flash for the first time, I got an error telling me that no compatible device in download mode was detected. I reconnected the Captivate and went back to Zadig AND Device Manager in Windows to see what was up, and the phone didn't show up in either. I toggled "Hidden devices" in Device Manager and finally got something:
As you can see, it failed to connect. I disconnected and reconnected my device multiple times in both normal and download mode, and sometimes it wouldn't show up at all, even with "Hidden devices" on. Whether or not it showed up didn't seem to follow any pattern. I have even tried on multiple Windows machines at this point, getting the same result every time. My phone is working just fine besides this one issue and running the stock ROM. Any help would be appreciated!
Click to expand...
Click to collapse
Do you have USB debugging enabled?
Sent from my SCH-I535 using Tapatalk
Hello everyone, last night I tried to do the conversion of an Mi A2 using the qifl in fedora 30. In the middle of the process, after giving the command sudo qifl --debug prog_emmc_firehose_Sdm660_ddr.elf rawprogram0.xml patch0.xml, I do not know if by bug in the program or problem in the cable, the computer lost the connection to the cell phone while sending the system. Now it only turns on and stays on the Mi screen and also in fastboot mode, but in none of these modes is it recognized by the computer. Seeing some tutorials here in xda, I also tried the test point method to enter EDL mode, but I do not know if it is a problem or if I am not aware, because it also does not enter, usually or nothing happens or the Mi screen appears when I insert the USB cable.
Could someone give me a light?
{
"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 apologize for probable errors in English)
Try using another computer, and connect your phone via FAstboot, remember to install all the drivers.
kiukirimas said:
Try using another computer, and connect your phone via FAstboot, remember to install all the drivers.
Click to expand...
Click to collapse
i tried, my laptop running fedora 30 and my mom desktop w/ Win10
platinumlayer said:
i tried, my laptop running fedora 30 and my mom desktop w/ Win10
Click to expand...
Click to collapse
I have only worked on Windows for flashing phones, on my experience once te phones powers up, it could be fixed, The only thing I could imagine is that your problem occurred due to bad connection between the computer and your phone.
Since you had already installed all the fastboot drivers and changed your computer and Operative systems, could think about using a diferent cable, if it works ok on other phones (prove it using usb transfer, cable can charge the phone and still be defective) if your cable is ok, try connecting your phone via fastboot, and move the cable on your connection port, cuz it could be another problem with it and try listening if the computer sounds like an usb is connected. Hope you can solve your problem.