hi guys - i need some assistance here please??
I cannot seem to download the pit file from my galaxy s5 sm-900f
Please could i get some assistance?
[DEBUG]native search /usr/local/bin/heimdall
Usage: heimdall <action> <action arguments>
Action: close-pc-screen
Arguments: [--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]
[--usb-log-level <none/error/warning/debug>]
Description: Attempts to get rid off the "connect phone to PC" screen.
Action: detect
Arguments: [--verbose] [--stdout-errors]
[--usb-log-level <none/error/warning/debug>]
Description: Indicates whether or not a download mode device can be detected.
Action: download-pit
Arguments: --output <filename> [--verbose] [--no-reboot] [--stdout-errors]
[--delay <ms>] [--usb-log-level <none/error/warning/debug>]
Description: Downloads the connected device's PIT file to the specified
output file.
Action: flash
Arguments:
--repartition --pit <filename>
--<partition name>|--<partition identifier> <filename> [...]
[--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]
[--usb-log-level <none/error/warning/debug>]
or:
--<partition name>|--<partition identifier> <filename> [...]
[--pit <filename>]
[--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]
[--usb-log-level <none/error/warning/debug>]
Description: Flashes one or more firmware files to your phone. Partition names
(or identifiers) can be obtained by executing the print-pit action.
WARNING: If you're repartitioning it's strongly recommended you specify
all files at your disposal.
Action: help
Description: Displays this dialogue.
Action: info
Description: Displays information about Heimdall.
Action: print-pit
Arguments: [--file <filename>] [--verbose] [--no-reboot] [--stdout-errors]
[--delay <ms>] [--usb-log-level <none/error/warning/debug>]
Description: Prints the contents of a PIT file in a human readable format. If
a filename is not provided then Heimdall retrieves the PIT file from the
connected device.
Action: version
Description: Displays the version number of this binary.
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[VERBOSE]Starting: mode:Heimdall
Connected:true
[DEBUG]Beginning MandatoryThread counter.casual-dev.com
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]State Change Detected, The new state is: 1
[DEBUG]Device Connected
[DEBUG]@stateConnected
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[INTERACTION][SHOWYESNO] Titleo you want me to obtain a PIT for you?
Message:This application requires what is known as a` 'PIT file'. The PIT file tells the application where to place files on your device. If you don't have a PIT file, we can obtain one from your device
press:
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[VERBOSE]obtaining pit
[VERBOSE]showing information message object
[INTERACTION][SHOWINFORMATION] Title:You will need to restart your device in Download Mode.
Message:In order to obtain a PIT file, the device will be rebooted. Once it reboots, you will need to put it back into download mode.\\n\\nPro-Tip: hold the download mode combination and press OK to dismiss this dislog to reboot into download mode immediately
press: Empty
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[VERBOSE]Done with message object
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall download-pit --output /tmp/CASUALbrandon-2014-10-20-19.19.48/part.pit
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[ERROR]permissions elevation required
[DEBUG]Executing ELEVATED Heimdall Command: "/usr/local/bin/heimdall" "download-pit" "--output" "/tmp/CASUALbrandon-2014-10-20-19.19.48/part.pit"
[DEBUG]Write Finished
[DEBUG]Setting executable /tmp/CASUALbrandon-2014-10-20-19.19.48/ElevateScript.sh. Result=true
[DEBUG]###Elevating Command: "/usr/local/bin/heimdall" "download-pit" "--output" "/tmp/CASUALbrandon-2014-10-20-19.19.48/part.pit" ###
[DEBUG]###executing real-time command: gksudo###
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[VERBOSE]Did not find pit
[INTERACTION][SHOWERROR] Title:Could not obtain pit.
Message:We could not obtain the pit file. We tried, but it didn't work.
press: Empty
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG][TRANSLATION][English]@interactionPastebinError
[INTERACTION][TEXTINPUT] Title:Error Submission System.
Message:We will submit your log to the CASUAL-Automated Pastebin. Developers can take a look at it to figure out what's going on.\\n\\nPlease enter your XDA-Developers username in the area below, then click 'Ok'.
press: Any String
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
[DEBUG]Run Heimdall from DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
[VERBOSE]Heimdall Device detected!
Related
As I try various approaches to get my S5 (AT&T) downgraded, I decided to see if Heimdall/Jodin could help. Heimdall-frontend and Jodin want to download a pit file from the phone. Neither of them succeed in doing this. Here's what I get when I try Heimdall:
Code:
$ sudo heimdall print-pit --no-reboot
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
By the way, I use Debian Linux. I've tried using Odin through VirtualBox running Win7, but it fails to detect the phone. I get a two-note sequence when I tell VirtualBox to attach the phone. I have the Samsung USB drivers installed. Win7 sees the phone, but Odin won't.
Hi,
I've got a I9301I with build KOT49H.I9301IXXSAPG5
Cannot root it:
Kingroot crashes instantly with VerifyError exception
Heimdall cannot retrieve PIT from phone in download mode
Heimdall log:
Code:
$ heimdall print-pit --usb-log-level info --verbose
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Some devices may take up to 2 minutes to respond.
Please be patient!
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Session begun.
Downloading device's PIT file...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
....
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
....
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send end session packet!
Releasing device interface...
I was able to read the I8730 (already rooted) pit without problems using the same cable and usb port.
Any idea? did they close all backdoors so rooting isn't possible anymore?
thanks
It is a new firmware. We have to wait for us to be root or return to a previous firmware.
Install a custom recovey...
sahilkhan9557 said:
Install a custom recovey...
Click to expand...
Click to collapse
how, if neither rooting apps nor reading PIT from download mode work? could you provide a PIT file?
JPT223 said:
how, if neither rooting apps nor reading PIT from download mode work? could you provide a PIT file?
Click to expand...
Click to collapse
U just need to flash twrp.zip using odin
Was an unknown problem with heimdall. using odin on windows 7 it worked. thanks
JPT223 said:
Was an unknown problem with heimdall. using odin on windows 7 it worked. thanks
Click to expand...
Click to collapse
root plese help
Dears,
I'm trying to do a full NAND backup on Windows with rkflashtool 5.1 (I can succeed on Ubuntu, but on Windows I have several errors).
Drivers are OK because I can read and write NAND with any other tools, but I need rkflashtool because it's the only one I know able to read and write the whole NAND to a single file from command line.
I'm on Windows 10 x64 build 1607.
On NU3001-01-H (CPU RK3188) NAND size is 7456MB with 512kB blocks, so
7456MB x 1024 = 7634944kB
7634944kB / 512kB = 14912 blocks = 0x3A40 blocks
Running as user or admin
rkflashtool r 0x0 0x3A40 > dump.bin
or
rkflashtool r 0 14912 > dump.bin
I'm returned
C:\Users\TSS\Downloads\SCS\Tools\Windows\rkflashto ol-5.1-win32-bin>rkflashtool.exe r 0x0 0x3A40 > dump.bin
rkflashtool: info: rkflashtool v5.1
libusb: 0.000000 warning [init_device] could not get node connection information for device '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non corretto.
libusb: 0.000000 error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer connected!
libusb: 0.015627 error [init_device] device '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer connected!
libusb: 0.062504 warning [init_device] could not get node connection information for device '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non corretto.
libusb: 0.062504 error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer connected!
libusb: 0.062504 error [init_device] device '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer connected!
libusb: 0.078130 warning [init_device] could not get node connection information for device '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non corretto.
libusb: 0.093755 error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer connected!
libusb: 0.093755 error [init_device] device '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer connected!
libusb: 0.109382 warning [init_device] could not get node connection information for device '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non corretto.
libusb: 0.109382 error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer connected!
libusb: 0.125008 error [init_device] device '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer connected!
libusb: 0.140633 warning [init_device] could not get node connection information for device '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non corretto.
libusb: 0.140633 error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer connected!
libusb: 0.140633 error [init_device] device '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer connected!
libusb: 0.156259 warning [init_device] could not get node connection information for device '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non corretto.
libusb: 0.171886 error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer connected!
libusb: 0.171886 error [init_device] device '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer connected!
rkflashtool: fatal: cannot open device
I really don't know what to do.
Any suggestions?
Thanks and best regards
How did you get ur pc to detect ur HU ?
Hi there.
I simply powered it on with reset hole pressed, then I had drivers installed and checked it's correctly listed in the devices manager.
Thanks.
Dang wish it wasnt that easy lol.
Ok guess my unit is trashed
My pc wont recognize it and it wont power on at all.
Hi Guys .
I want to Flash Lenovo A6000 plus phone because it is dead and nothing is coming on screen when we power on .
I have downloaded a stock ROM file named " Lenovo_A6000_L_S054_150915_8G_ROW " and trying to flash it with QFIL software but when i click on " Download " button after connecting device to computer , it is giving error
"Validating Application Configuration
Load APP Configuration
COM:-1
SAHARA:True
SAHARA:G:\software\Lenovo a6000 plus flash file\A6000_L_S054_150915_8G_ROW\Lenovo_A6000_L_S054_150915_8G_ROW\Firmware\validated_emmc_firehose_8916.mbn
SEARCHPATH:G:\software\Lenovo a6000 plus flash file\A6000_L_S054_150915_8G_ROW\Lenovo_A6000_L_S054_150915_8G_ROW\Firmware
RAWPROGRAM:
rawprogram_unsparse.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
READBACKMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: G:\software\Lenovo a6000 plus flash file\A6000_L_S054_150915_8G_ROW\Lenovo_A6000_L_S054_150915_8G_ROW\Firmware
RAWPROGRAM file path: G:\software\Lenovo a6000 plus flash file\A6000_L_S054_150915_8G_ROW\Lenovo_A6000_L_S054_150915_8G_ROW\Firmware\rawprogram_unsparse.xml
PATCH file path:G:\software\Lenovo a6000 plus flash file\A6000_L_S054_150915_8G_ROW\Lenovo_A6000_L_S054_150915_8G_ROW\Firmware\patch0.xml
Programmer Path:G:\software\Lenovo a6000 plus flash file\A6000_L_S054_150915_8G_ROW\Lenovo_A6000_L_S054_150915_8G_ROW\Firmware\validated_emmc_firehose_8916.mbn
Start Download
Program Path:G:\software\Lenovo a6000 plus flash file\A6000_L_S054_150915_8G_ROW\Lenovo_A6000_L_S054_150915_8G_ROW\Firmware\validated_emmc_firehose_8916.mbn
COM Port number:4
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:True
Use Verbose:False
COM Port number:4
Sending NOP
FireHose Log: Validation is enabled.
FireHose Log: ERROR: length < sizeof(eighty_byte_header_type) || hash_position_address == NULL
FireHose Log: ERROR: Failed to authenticate Digital Signature
FireHose Log: Resetting validation state
Invalid response NAK
NOP: Fail Code: 13
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:FireHose Fail Failed to send Firehose NOP to the phone.
Finish Download
"
Please can anyone help me that what is the problem and why the flashing is not done and why this error coming . Is there any problem in stock Rom file or any other issue ?
Hi Everyone,
I need to update my firmware software of Samsung G. A5 at least Android 7.0 or something better like Lineage 16.
Samsung Galaxy A5,
Android Version 6.0.1,
Module SM-A500FU,
Baseband Version A500FUXXU1CPI2.
If I try under Ubuntu Linux, I get those results.
Code:
$ adb shell
[email protected]:/ $ getprop ro.bootloader
A500FUXXU1CSB1
Code:
adb reboot bootloader //this command works and It reboots. I could see in my cellphone display "Downloading... Do not turn off target"
$ fastboot flash recovery recovery.img
< waiting for any device >
Code:
$ fastboot reboot
< waiting for any device >
how can we be a root user?
Code:
[email protected]:/sdcard/Download/open_gapps-arm-7.1-micro $ ./installer.sh
/system/bin/sh: ./installer.sh: can't execute: Permission denied
Code:
$ heimdall flash --RECOVERY recovery.img --no-reboot // recovery.img comes from untar twrp_20190427_a5ultexx.tar file
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
. glassechidna . com . au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
glassechidna.com . a u/d onate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
I downloaded those files.
lineage-16.0-20190427-UNOFFICIAL-a5.zip
open_gapps-arm-7.1-micro.zip
open_gapps-arm-9.0-nano-20191123.zip
twrp_20190427_a5ultexx.tar
This is the Canadian update schedule.
We're nearing the end of March, so did the Pie update actually materialize for the Galaxy A5? Can anyone confirm/deny?