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
Related
http://forum.xda-developers.com/showthread.php?t=1819660 Followed instructions here, no joy. Log following.
Notes: It detects busybox is running and wants me to clean, I take option 2 as detailed in the instructions and it proceeds to run option one. When I hit the second step in the commands to run (./photon-torpedo.sh) it gives me this error:
Unfortunatly your going have to enter some shell commands here
Not to worry though it only five commands press enter after each one
1 -- Enter at the first $ cd /data/tmp
2 -- Enter at the second $ ./photon-torpedo.sh
3 -- Enter at the first # ./kill-su.sh
4 -- Enter at the second # exit
5 -- Enter at the next $ exit
Once you are done the script will finish up and reboot your phone.
$ cd /data/tmp
cd /data/tmp
$ .photon-torpedo.sh
.photon-torpedo.sh
.photon-torpedo.sh: not found
$ ./photon-torpedo.sh
./photon-torpedo.sh
ERROR: ld.so: object 'libpcprofile.so' cannot be loaded as audit interface: unde
fined symbol: la_version; ignored.
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
ddxSigGiveUp: Closing log
./photon-torpedo.sh: line 5: /lib/libphoton-torpedo.so: Permission denied
ERROR: ld.so: object 'libphoton-torpedo.so' cannot be loaded as audit interface:
invalid ELF header; ignored.
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
ddxSigGiveUp: Closing log
$
-Fails to give root access while running the torpedo as far as I can tell.
(would post to the thread this pertains to but I do not have enough posts to do so apparently)
In addition: this was previously rooted on a older version of the firmware, which one I cannot remember. Current BusyBox is 1.17.1 su is running binary v3.0(11) permissions are -rwxr-xr-x rootshell /system/bin/su
Alright everyone, my first time posting on here as I've spent the past two weeks googling and googling and googling and to no avail
I have a very generic China brand Android 2.3.6 phone with an MT6573 ARMv6 processor. It's a great phone for its value (I bought it for under $40) but it has very low RAM and was hoping to use a Swap file on my SD card with SD-Booster in order to improve it's performance. So I've tried every single rooting method I can find, but not of them work for one reason: I cannot ADB anything.... ANYTHING properly.
For example, running psneuter on SuperOneClick gives this output (truncated):
Code:
export TEMPRANDOM=35445;export PS1=END:$TEMPRANDOM;ls -l /system/xbin/su
export PS1=""
/system/xbin/su: No such file or directory
END:35445
export TEMPRANDOM=61084;export PS1=END:$TEMPRANDOM;ls -l /system/bin/su
export PS1=""
/system/bin/su: No such file or directory
END:61084
export TEMPRANDOM=27372;export PS1=END:$TEMPRANDOM;chmod 755 /data/local/tmp/busybox
export PS1=""
Unable to chmod /data/local/tmp/busybox: Not a directory
see, every time I tried to chmod or push or export or any other ADB command, it keeps saying "no such file" or "not a directory" and so I don't know what's going on! Every script I've found on xda requires some ADB command and so I don't even know of zergrush or gingerbreak or psneuter can even work on my phone! I read that it may be due to the wrong ADB drivers, so I've even tried the universal adb driver installer from adbdriver(dot)com and still no dice.
I'm very new to Android and a fast learner, so please, any help or pointers in the right direction would be greatly appreciated! If you need any additional information from/about my phone, please ask and I'll provide.
Thanks in advance.
[can someone delete that post, I made a mistake, sorry q_q]
Also I don't necessarily need a script; some (slightly) detailed instructions on how to manually do it a would do me well too! I'd love to learn!
Update on what I'm doing: I've tried instead to adb with Ubuntu using Wubi. lsusb recognized my device as a Google device and I updated my Android rules file accordingly, restarted udev, but still "adb devices" turns up empty and now lsusb doesn't even recognize my device... this is getting really frustrating
okay, so, I've opened up every .bat script I can find and gone through it line by line, and this is where it fails, every time:
trying to write to the /system/ directory
the following lines of code always fail:
Code:
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
mount: permission denied (are you root?)
and
Code:
adb remount
remount failed: Operation not permitted
so basically, I'm stuck. without mounting the system directory I cannot get root.... and every time I try to mount, it seems to say I need root and NO WHERE online can I find a way to solve this problem.... here's what I'm running again:
Android version: 2.3.6
Build number ALPS.GB.FDD2.MP.V4.8
Kernel Version: 2.6.35.7 [email protected] #2 Mon Nov 12 18:006:21 CST 2012
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?
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
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?