Hi
So bear with me - my question may be simple, however I'm at a loss, and countless hours of searching xda and the web in general has gotten me nowhere.
The task at hand, in all its simplicity is to install a custom rom - CM13 to be precise. Now the weapon of choice, as with past models (S2, S3, S3 minis etc), is to flash the recovery, copy the zip to SDCARD, and install it via recovery... simple... or no not really it appears.
I have installed ADB, and I can communicate with the phone fine here, reboot it to download mode etc. Now - at the very time it goes into download mode, its game over. Fastboot will not recognize the device, and whatever commands being used, it will be stuck in "<waiting for device>". Heimdall will not complete a print-pit command, regardless of driver instantiated using Zadig, however the outcome varies to some degree. Odin detects the phone using Samsung USB drivers and Naked Universal USB drivers, it will even proceed to flash the recovery, and deem the flash succesful, however nothing has happened in reality (and I do think the flash runs rather quick, in comparison to the time it normally uses - if memory serves me well - it IS a few days since I did this last time). The system status DID change to Custom in download mode after Odin flash tho'.
Now to the details:
-----------------------------
OS Used: Windows 8.1 x64
Heimdall error messages:
============
Using WinUSB:
libusbx: error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_01#6&30F7B376&0&0001 ' is no longer connected!
libusbx: error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_02#6&30F7B376&0&0002 ' is no longer connected!
libusbx: error [windows_transfer_callback] detected I/O error 87: [87] The parameter is incorrect.
Using libusbK (only visible with verbose parameter):
WARNING: Control transfer #6 failed. Result: -9
ERROR: libusb error -7 whilst sending packet. Retrying...
Finally bailing with unable to download PIT
Using libusb0 (still only visible with verbose parameter):
WARNING: Control transfer #6 failed. Result: -1
ERROR: libusb error -7 whilst sending packet. Retrying...
Finally bailing with unable to download PIT
Fastboot simply doesn't recognize the device at all.
Odin recognizes the phone, flashes the recovery and reports succes, but the recovery is not active (I'm suspecting a silent flash failure somehow).
Recovery image used flashing with Odin: twrp-3.0.2-2-klte.img.tar
Steps taken to try and remediate:
- Different USB ports.
- (Many) different USB cables.
- Another PC with USB 2.0 ports. (Still Win 8.1 x64)
- Various versions of Samsung USB drivers
- Naked Universal drivers
- Various versions of Odin.
Download mode shows the following data:
Product Name: SM-G900F
Current Binary: Custom (This changed after flashing with ODIN)
System Status: Custom (This changed after flashing with ODIN)
Knox Warranty Void: 0x0
Qualcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download : Enable
UDC START
I havent had the balls to try and do a complete stock firmware flash with Odin, since the connection seems unstable at best.
Additional info: I originally thought it was system specific (my combination of OS and USB drivers), however attaching a Galaxy S3 Mini works like a charm - Heimdall prints PIT without any issue at all.
Aight... I'm absolutely at a loss here... any help will be greatly appreciated.
- Cheers
So bear with me - my question may be simple, however I'm at a loss, and countless hours of searching xda and the web in general has gotten me nowhere.
The task at hand, in all its simplicity is to install a custom rom - CM13 to be precise. Now the weapon of choice, as with past models (S2, S3, S3 minis etc), is to flash the recovery, copy the zip to SDCARD, and install it via recovery... simple... or no not really it appears.
I have installed ADB, and I can communicate with the phone fine here, reboot it to download mode etc. Now - at the very time it goes into download mode, its game over. Fastboot will not recognize the device, and whatever commands being used, it will be stuck in "<waiting for device>". Heimdall will not complete a print-pit command, regardless of driver instantiated using Zadig, however the outcome varies to some degree. Odin detects the phone using Samsung USB drivers and Naked Universal USB drivers, it will even proceed to flash the recovery, and deem the flash succesful, however nothing has happened in reality (and I do think the flash runs rather quick, in comparison to the time it normally uses - if memory serves me well - it IS a few days since I did this last time). The system status DID change to Custom in download mode after Odin flash tho'.
Now to the details:
-----------------------------
OS Used: Windows 8.1 x64
Heimdall error messages:
============
Using WinUSB:
libusbx: error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_01#6&30F7B376&0&0001 ' is no longer connected!
libusbx: error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_02#6&30F7B376&0&0002 ' is no longer connected!
libusbx: error [windows_transfer_callback] detected I/O error 87: [87] The parameter is incorrect.
Using libusbK (only visible with verbose parameter):
WARNING: Control transfer #6 failed. Result: -9
ERROR: libusb error -7 whilst sending packet. Retrying...
Finally bailing with unable to download PIT
Using libusb0 (still only visible with verbose parameter):
WARNING: Control transfer #6 failed. Result: -1
ERROR: libusb error -7 whilst sending packet. Retrying...
Finally bailing with unable to download PIT
Fastboot simply doesn't recognize the device at all.
Odin recognizes the phone, flashes the recovery and reports succes, but the recovery is not active (I'm suspecting a silent flash failure somehow).
Recovery image used flashing with Odin: twrp-3.0.2-2-klte.img.tar
Steps taken to try and remediate:
- Different USB ports.
- (Many) different USB cables.
- Another PC with USB 2.0 ports. (Still Win 8.1 x64)
- Various versions of Samsung USB drivers
- Naked Universal drivers
- Various versions of Odin.
Download mode shows the following data:
Product Name: SM-G900F
Current Binary: Custom (This changed after flashing with ODIN)
System Status: Custom (This changed after flashing with ODIN)
Knox Warranty Void: 0x0
Qualcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download : Enable
UDC START
I havent had the balls to try and do a complete stock firmware flash with Odin, since the connection seems unstable at best.
Additional info: I originally thought it was system specific (my combination of OS and USB drivers), however attaching a Galaxy S3 Mini works like a charm - Heimdall prints PIT without any issue at all.
Aight... I'm absolutely at a loss here... any help will be greatly appreciated.
- Cheers
from xda-developers http://ift.tt/2aTJz4d
via IFTTT
No comments:
Post a Comment