Hey all,
This is my first time rooting, so please let me know if I need to provide more info. I will gladly do it!
As the title says, I'm trying to root my Galaxy Tab Pro Wifi (SM-T520), and I'm following picassowifi's guide: wiki.cyanogen mod.org/w/Install_CM_for_picassowifi (sorry for the link, as this is my first post, I can't post a link). I'm on Windows 7, and I'm getting stuck at the first part--flashing recovery. When I use the "heimdall flash --RECOVERY" command, I get stuck at "Initialising Protocol" for an indefinite amount of time. I've spent around 4 hours reading threads of people with similar problems, but none of their solutions work for me. I'm not very familiar with the PIT files, so that may be part of my problem . Anyway, below what I've taken from CMD:
C:\Users\Christopher Robin\Desktop\New folder>heimdall flash --RECOVERY clockwor
kmodrecovery.6051.picassowifi.img --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
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:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
C:\Users\Christopher Robin\Desktop\New folder>heimdall print-pit --verbose
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
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:
Initialising connection...
Detecting device...
libusbx: error [auto_claim] could not auto-claim any interface
length: 18
device class: 2
S/N: 0
VIDID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
ERROR: Failed to retrieve config descriptor
C:\Users\Christopher Robin\Desktop\New folder>
C:\Users\Christopher Robin\Desktop\New folder>heimdall print-pit
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
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:
Initialising connection...
Detecting device...
ERROR: Failed to retrieve config descriptor
C:\Users\Christopher Robin\Desktop\New folder>
Any help is much appreciated! Thanks!
Related
Installing CM 10.1 fails on running heimdall with "Protocol initialisation failed!"
I got an n7100 device and following the instructions on the CM n7100 page exactly
Driver installation is a success but the heimdall recovery from the "recovery-clockwork-6.0.1.9-n7100.img" file fails.
This is the output:
-----------------------------------
Heimdall v1.4 RC1
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
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:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to send data!Releasing device interface...
-----------------------------------
Please help.
TIA
I have a verizon S4 mini that I rooted with towelroot. I'd like to try cyanogenmod so I followed the instructions here...
http://wiki.cyanogenmod.org/w/Install_CM_for_serranoltexx
When I run heimdall (on arch linux and windows) I get the following error...
Heimdall v1.4.0
Copyright (c) 2010-2013, 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
VIDID: 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...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
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...
PIT file download successful.
Uploading RECOVERY
0%
16%
33%
49%
66%
83%
99%
100%
ERROR: Failed to unpack received packet.
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Releasing device interface...
Re-attaching kernel driver...
Has this happened to anyone else?
If I recall correctly, some people have mentioned to solve some issues by running heimdall as root, for whatever reason. Have you tried heimdall-frontend as well?
I have an SM-T210 I tried to flash CWM 6.0.49 using the instructions here:
http://forum.xda-developers.com/showthread.php?t=2433853
However after doing that and failed according to Odin Tab won´t get out of Firmware upgrade encountered an issue, blah, blah, blah. After the first attempt to flash Odin cannot get pass the Setup connection stage.
It is not a HW issue since the Samsung service center guys got it back in shape in less that an hour. I´m using a VM under Fusion for Mac OSX for everything. I have used that before for another Android phones and worked just fine.
I have tried changing 5 different cables, no luck.
I have tried changing port on the MAC, no luck.
Please help!
Odin and Heimdall are not Wirkung with Mac Osystems,also und er VM.
Heimdall also not working
Seems that Heimdall is also not working:
[ mitrejo : ~/Downloads ]$ sudo heimdall flash --recovery recovery.img --verbose
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
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:
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "SAMSUNG USB"
Serial No: "SAMSUNG USB SERIAL"
length: 18
device class: 2
S/N: 3
VIDID: 04E8:685D
bcdDevice: 0000
iMan:iProd:iSer: 1:2:3
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
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: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
libusbx: error [get_endpoints] error getting pipe information for pipe 1: unknown error
libusbx: error [darwin_set_interface_altsetting] could not build endpoint table
ERROR: Setting up interface failed!
Releasing device interface...
mktrejo said:
Seems that Heimdall is also not working:
[ mitrejo : ~/Downloads ]$ sudo heimdall flash --recovery recovery.img --verbose
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
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:
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "SAMSUNG USB"
Serial No: "SAMSUNG USB SERIAL"
length: 18
device class: 2
S/N: 3
VIDID: 04E8:685D
bcdDevice: 0000
iMan:iProd:iSer: 1:2:3
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
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: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
libusbx: error [get_endpoints] error getting pipe information for pipe 1: unknown error
libusbx: error [darwin_set_interface_altsetting] could not build endpoint table
ERROR: Setting up interface failed!
Releasing device interface...
Click to expand...
Click to collapse
You need a Windows OS for Odin and Heimdall.
Has anyone got jOdin or Heimdall to work with this device? I'm on OS X and I can't seem to get the libusb bundled with Heimdall to work with my device.
when I run heimdall print-pit --verbose --no-reboot I get:
Code:
Jamess-MBP:~ jamescarroll$ heimdall print-pit --verbose --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, 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: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
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: 83
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: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #2 failed. Result: -7
WARNING: Control transfer #3 failed. Result: -7
WARNING: Control transfer #4 failed. Result: -7
WARNING: Control transfer #5 failed. Result: -7
WARNING: Control transfer #6 failed. Result: -1
ERROR: Failed to send data: "ODIN"
Releasing device interface...
It didn't work for me. I just opened my VMware instance of Windows 8. LOL
dc/dc said:
It didn't work for me. I just opened my VMware instance of Windows 8. LOL
Click to expand...
Click to collapse
You have odin working in a VM? I didn't think you could do that....
I've been messing with it but odin always crashes.
jamcar said:
You have odin working in a VM? I didn't think you could do that....
I've been messing with it but odin always crashes.
Click to expand...
Click to collapse
Yep. You just have to make sure to select the tickbox for all drivers of the phone to always connect to Windows instead of Mac.
Hey,
I am running into the problem of installing a custom recovery on the Galaxy Tab 10.1 pro wifi with the most recent updates installed.
I have tried to install twrp using Haimdall on both ubuntu (chromebook with chrouton) and a mac. Both times I have used version 1.4.
No matter what usb cable, computer or usb prot I use, I keep getting the same errors:
Code:
Macintosh-2:~ Teun$ sudo heimdall flash --RECOVERY Downloads/Chrome/twrp-2.8.6.0-picassowifi.img --no-reboot --verbose
Heimdall v1.4.0
Copyright (c) 2010-2013, 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: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
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: 83
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: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #2 failed. Result: -7
WARNING: Control transfer #3 failed. Result: -7
WARNING: Control transfer #4 failed. Result: -7
WARNING: Control transfer #5 failed. Result: -7
WARNING: Control transfer #6 failed. Result: -1
ERROR: Failed to send data: "ODIN"
Releasing device interface...
If I use print-pit I het a similar failure:
Code:
Macintosh-2:~ Teun$ sudo heimdall print-pit --verbose
Password:
Heimdall v1.4.0
Copyright (c) 2010-2013, 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: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
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: 83
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: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #2 failed. Result: -7
WARNING: Control transfer #3 failed. Result: -7
WARNING: Control transfer #4 failed. Result: -7
WARNING: Control transfer #5 failed. Result: -7
WARNING: Control transfer #6 failed. Result: -1
ERROR: Failed to send data: "ODIN"
Releasing device interface...
I've looked online, but couldn't find what these specific error codes mean. I also noticed that I don't get an error for the first control transfer. I don't have access to a Windows machine any time soon, so I can't use ODIN. I've tried https://jodin3.casual-dev.com/ as well, but that web app doesn't even seem to detect the tablet at all. Any idea's? I'd be super thankful!
Update: got myself a windows pc and installed twrp using odin. Works fine now.