when i follow the steps to load lineage from the lineage wiki and I get to the heimdall part where I type heimdall print-pit i get the following error:
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...
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...
what can i do with this to fix it? Do i need to unlock the phone first? Has anyone had any success with this phone and loading lineage on it?
Related
How it started:
Okay, so I had some troubles getting botbrew (experimental) to install it's subcomponents so I had the bright idea to start fresh by:
Code:
# rm -rf /data/botbrew*
...without thoroughly checking the contents of the folder.
I later figured there were some symlinks to critical system files (or vise versa) within that directory because almost immediately multiple programs force closed such as the Android panel and there were FC windows on top of each other. *facepalm*
I tried to connect via adb and got this:
Code:
$ ./adblinux shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Rebooting leads to a persistent Samsung logo with adb response same as above. I can get into recovery mode though I'm not sure what, if anything, can be done in it to fix /system/.
I read elsewhere that the sh path is hardcoded:
http://forum.xda-developers.com/showthread.php?t=1877618
Luckily I have a "somewhat working" fallback device. However, is there any way to restore these files manually? There should still be a couple different copies of busybox on the device so... hopefully they could be leveraged to get it going again.
The first thing I did after seeing the failed adb connection was attempt to flash with several different stock roms using Odin, and then Heimdall for good measure, but they all failed with a junk message just prior to starting the flash (see attached example screenshot) while phone is in download mode.
[See next]
Update - Some Success.
I tried heimdall through the command line instead of the java GUI while specifying a PIT file and got a step further (yes!):
Code:
$ sudo heimdall flash --pit infuse.pit --factoryfs factoryfs.rfs
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
[webpage omitted]
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:
[webpage omitted]
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...
After it rebooted, I was able to shell in with adb! I notice that /system/bin/sh does exist now, /sdcard is not mounted and the device now reboots systematically in a short period of time.
Running su gets:
Code:
$ ./adblinux shell
$ su
[1] Segmentation fault su
Any suggestions going forward?
Thank you in advance,
Mark
Have tried this twice. Stock Galaxy Note 2 on Verizon, was rooted, did full unroot with SuperSU before this whole process. Running Windows 7 Home Premium x64. Submitted to pastebin, searched forums, but to no avail. Phone's still working, just failed unlock. Here's the log (with donation URLs removed because I'm pre-10 posts):
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2.
--Galaxy Note 2 Jailbreak-NoYouVerizon--
This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2. Put your device into ADB mode. Credit for this exploit goes to Lee Harrison
Rebooting into download mode
Waiting for Downoad Mode device.....Executing Heimdall command.
Heimdall v1.4 RC2
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...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Uploading PIT
PIT upload successful
Uploading BOOTLOADER
100%
BOOTLOADER upload successful
Uploading BOOT
100%
BOOT upload successful
Ending session...
Rebooting device...
Releasing device interface...
[Heimdall Success]
Your device should be rebooting into Android now.
Waiting for ADB device connection. When Windows 7 recognizes the device, we will continue. Don't touch anything.
mkdir failed for /data/local/tmp, File exists
Pushing dependencies
Pushing su binary...
2764 KB/s (96260 bytes in 0.034s)
Pushing SuperSU app...
3060 KB/s (996704 bytes in 0.318s)
Pushing Exynos-Abuse exploit
[CRITICAL]1
1
java.lang.ArrayIndexOutOfBoundsException: 1
java.lang.ArrayIndexOutOfBoundsException: 1
at CASUAL.CASUALInteraction.showUserCancelOption(CASUALInteraction.java:144)
at CASUAL.CASUALLanguage.commandHandler(CASUALLanguage.java:305)
at CASUAL.CASUALLanguage.beginScriptingHandler(CASUALLanguage.java:66)
at CASUAL.CASUALScriptParser$1.run(CASUALScriptParser.java:122)
at java.lang.Thread.run(Unknown Source)
A critical error was encoutered. Please copy the log from About>Show Log and report this issue
[CRITICAL]CASUAL scripting error
push "$ZIPFILEexynos-abuse" /data/local/tmp/
CASUAL scripting error
push "$ZIPFILEexynos-abuse" /data/local/tmp/
java.lang.RuntimeException: CASUAL scripting error
push "$ZIPFILEexynos-abuse" /data/local/tmp/
java.lang.RuntimeException: CASUAL scripting error
push "$ZIPFILEexynos-abuse" /data/local/tmp/
at CASUAL.CASUALLanguage.beginScriptingHandler(CASUALLanguage.java:73)
at CASUAL.CASUALScriptParser$1.run(CASUALScriptParser.java:122)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
at CASUAL.CASUALInteraction.showUserCancelOption(CASUALInteraction.java:144)
at CASUAL.CASUALLanguage.commandHandler(CASUALLanguage.java:305)
at CASUAL.CASUALLanguage.beginScriptingHandler(CASUALLanguage.java:66)
... 2 more
A critical error was encoutered. Please copy the log from About>Show Log and report this issue
CASUAL experienced an error while parsing command:
push "$ZIPFILEexynos-abuse" /data/local/tmp/
please report the above exception.
Script Complete
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Second try:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Rebooting into download mode
Waiting for Downoad Mode device.......Executing Heimdall command.
Heimdall v1.4 RC2
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...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Uploading PIT
PIT upload successful
Uploading BOOTLOADER
100%
BOOTLOADER upload successful
Uploading BOOT
100%
BOOT upload successful
Ending session...
Rebooting device...
Releasing device interface...
[Heimdall Success]
Your device should be rebooting into Android now.
Waiting for ADB device connection. When Windows 7 recognizes the device, we will continue. Don't touch anything.
mkdir failed for /data/local/tmp, File exists
Pushing dependencies
Pushing su binary...
371 KB/s (96260 bytes in 0.253s)
Pushing SuperSU app...
2796 KB/s (996704 bytes in 0.348s)
Pushing Exynos-Abuse exploit
[CRITICAL]1
1
java.lang.ArrayIndexOutOfBoundsException: 1
java.lang.ArrayIndexOutOfBoundsException: 1
at CASUAL.CASUALInteraction.showUserCancelOption(CASUALInteraction.java:144)
at CASUAL.CASUALLanguage.commandHandler(CASUALLanguage.java:305)
at CASUAL.CASUALLanguage.beginScriptingHandler(CASUALLanguage.java:66)
at CASUAL.CASUALScriptParser$1.run(CASUALScriptParser.java:122)
at java.lang.Thread.run(Unknown Source)
A critical error was encoutered. Please copy the log from About>Show Log and report this issue
[CRITICAL]CASUAL scripting error
push "$ZIPFILEexynos-abuse" /data/local/tmp/
CASUAL scripting error
push "$ZIPFILEexynos-abuse" /data/local/tmp/
java.lang.RuntimeException: CASUAL scripting error
push "$ZIPFILEexynos-abuse" /data/local/tmp/
java.lang.RuntimeException: CASUAL scripting error
push "$ZIPFILEexynos-abuse" /data/local/tmp/
at CASUAL.CASUALLanguage.beginScriptingHandler(CASUALLanguage.java:73)
at CASUAL.CASUALScriptParser$1.run(CASUALScriptParser.java:122)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
at CASUAL.CASUALInteraction.showUserCancelOption(CASUALInteraction.java:144)
at CASUAL.CASUALLanguage.commandHandler(CASUALLanguage.java:305)
at CASUAL.CASUALLanguage.beginScriptingHandler(CASUALLanguage.java:66)
... 2 more
A critical error was encoutered. Please copy the log from About>Show Log and report this issue
CASUAL experienced an error while parsing command:
push "$ZIPFILEexynos-abuse" /data/local/tmp/
please report the above exception.
Script Complete
I'm getting this same exact error. Have tried everything suggested and everything I could come up with to resolve it. Spent tons of time googling around looking for answers and no luck. Anybody have any ideas?
Hello,
I am trying to install custom recovery on my N8000 via Heimdall on Ubuntu 12.10
When trying to push the recovery using the following command
# sudo heimdall flash --recovery recovery-clockwork-6.0.2.7-n8000.img
I get this 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...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Protocol initialisation failed!
Releasing device interface...
Any ideas? The command mentioned above is the only command I tried.
Any help???
Below is what happens when running heimdall:
Trying to install CWM on a Samsung Galaxy Tab 2 SCH-I705 .... P3113.
[email protected]:~/Downloads$ sudo heimdall flash --RECOVERY recovery-clockwork-touch-6.0.2.3-p3113.img
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...
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...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
[email protected]:~/Downloads$
Any ideas on how to solve this problem?
Thanks,
dlw
INITIAL COMMUNIQUE:
...
"Samsung GALAXY CORE Prime"
("POWERED by android")
"metroPCS" ("t-mobile network")
"bong bong bong laa laa"
"buzz-buzz-buzz buzzzzzz"
(via usb cable to slackware--porteus variant: "Unable to open MTP device '[usb:001,013]'")
"buzz-buzz-buzz buzzzzzz"
("Unable to open MTP device '[usb:001,014]'")
"buzz-buzz-buzz buzzzzzz"
("Unable to open MTP device '[usb:001,015]'")
"buzz-buzz-buzz buzzzzzz"
("Unable to open MTP device '[usb:001,016]'")
"buzz-buzz-buzz" ...
...
System Recovery <3rd edition?> (up vol+pwr+home) appears normal for an os 5.1.1 Android.
(note: subject does not appreciate being called a "lollipop")
TRANSLATORS NOTES:
Android SM-G360T1, lmy47x.g360t1uvu1aofa, (unique s/n classified) not responding to Heimdall protocol...
Dreams of Replicant status wanning...
Suspect it (she?) is showing early stages of depression...
Z768G not so jealous now...suspect foul play ... >.> ... <.< ...
---
Heimdall output:
Code:
[email protected]:/mnt/sda3/.../prime# heimdall flash --RECOVERY /mnt/sda3/.../prime/TWRP/recovery.img --verbose
it's 3.0.2.0 i think
Code:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
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:
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...
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...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
[email protected]:/mnt/sda3/.../prime#
...
worth noting:
Code:
Manufacturer: "Sasmsung"
S/N: 0
Code:
ERROR: libusb...
Code:
MTP device '[usb:...
Code:
gingerbread man in spotlight...again...
...
any helpful tips for a more fruitful communication with this 'droid?