Hi all,
i'm very happy to finally see our hated boot loader unlocked!
By the way i was following the_laser steps to unlock it but i'm on a GNU/Linux machine
(Archlinux) so i tried the Virtualbox way noticing that "s1tool" for checking if the phone
is unlockable or not works fine but the batch "msm7227_semc.cmd" isn't at all (maybe
"adb" doesn't communicate very well through Virtualbox USB virtualization, i don't know),
so i port the batch as a shell script and it works.
It's not good to keep it in my laptop so here it is:
Code:
#!/bin/sh
#
# msm7227_semc.sh - a simple step-by-step port of msm7227_semc.cmd
# by [email protected]
#
# 2011 - Alessandro "ff0000.it" Massignan
#
COUNT=0
function error ()
{
MESSAGE=$1
echo "Error: ${MESSAGE}"
exit 1
}
function step ()
{
COUNT=$(( COUNT + 1 ))
MESSAGE=$1
printf "\n${COUNT}. ${MESSAGE}"
read
}
cat <<EOF
******************************************************
*** Process requires standard Android 2.x firmware ***
*** -= now it's up to you! ;-) =- ***
******************************************************
EOF
step "searching for 'adb' executable"
_WHICH=`which which 2>/dev/null` || { error "Missing tool: which"; }
_ADB=`${_WHICH} adb 2>/dev/null` || { error "Missing tool: adb"; }
step "getting root priviledges"
echo "waiting for device..."
$_ADB wait-for-device
echo "pushing exploit..."
$_ADB push bootTools/rageagainstthecage /data/local/tmp/expl || \
{ error "Failed to push the exploit"; }
$_ADB shell "chmod 777 /data/local/tmp/expl" || \
{ error "Failed to change permission on exploit"; }
echo "executing exploit..."
$_ADB shell "/data/local/tmp/expl" || \
{ error "Failed to execute the exploit"; }
echo "waiting for device..."
$_ADB wait-for-device
step "removing NAND MPU restrictions via SEMC backdoor (this is permanent)"
$_ADB push bootTools/fixPart /data/local/tmp/fixPart || \
{ error "Failed to push the backdoor"; }
$_ADB shell "chmod 777 /data/local/tmp/fixPart" || \
{ error "Failed to change permission on backdoor"; }
$_ADB shell "/data/local/tmp/fixPart" || \
{ error "Failed to execute the backdoor"; }
echo "Rebooting..."
$_ADB shell reboot
echo "Waiting for device..."
$_ADB wait-for-device
step "re-getting root priviledges (wait for complete boot process)"
$_ADB shell "/data/local/tmp/expl" || { exit 1; }
echo "Waiting..."
$_ADB wait-for-device
step "getting access to semcboot area"
$_ADB push bootTools/mapper_2.6.29.ko /data/local/tmp/mapper_2.6.29.ko || \
{ error "Failed to push maper module"; }
$_ADB shell "chmod 777 /data/local/tmp/mapper_2.6.29.ko" || \
{ error "Failed to change permission on mapper module"; }
$_ADB shell insmod /data/local/tmp/mapper_2.6.29.ko || \
{ "Failed to load maper module into kernel"; }
step "writing semcboot"
$_ADB push my7227bootwrite_semcSL /data/local/tmp/my7227bootwrite_semcSL || \
{ error "Failed to push semcbooti data"; }
$_ADB shell "chmod 777 /data/local/tmp/my7227bootwrite_semcSL" || \
{ error "Failed to change permission on semcboot data"; }
$_ADB shell "/data/local/tmp/my7227bootwrite_semcSL" || \
{ error "Failed to execute semcboot data"; }
step "All done."
exit 0
copy this one and put it as msm7227_semc.sh in msm7227 directory (the one you obtain extracting the archive built by the_laser, http://forum.xda-developers.com/showthread.php?t=1254225), enter the directory
and execute it:
Code:
[email protected]:msm7227# sh ./msm7227_semc.sh
******************************************************
*** Process requires standard Android 2.x firmware ***
*** -= now it's up to you! ;-) =- ***
******************************************************
1. searching for 'adb' executable
2. getting root priviledges
waiting for device...
pushing exploit...
2324 KB/s (585731 bytes in 0.246s)
executing exploit...
waiting for device...
3. removing NAND MPU restrictions via SEMC backdoor (this is permanent)
12 KB/s (3087 bytes in 0.240s)
success
Rebooting...
Waiting for device...
4. re-getting root priviledges (wait for complete boot process)
Waiting...
5. getting access to semcboot area
154 KB/s (8064 bytes in 0.051s)
6. writing semcboot
1294 KB/s (596916 bytes in 0.450s)
successfully wrote 0003ff00
7. All done.
[email protected]:msm7227#
*** each step has to be confirmed by pressing a key ***
It requires "adb" executable in one of the directory listed in $PATH variable.
It works for me so it has to work for you ;-)
Happy unlocking and endless kudos to the_laser ,
ff0000
THANK YOU! Im on linux and had to use my rubbishy windows machine to do bl unlock also QEMU might be better for USB as the android emulator runs it and that works fine
Sent from my U20i using XDA App
x10man said:
THANK YOU! Im on linux and had to use my rubbishy windows machine to do bl unlock also QEMU might be better for USB as the android emulator runs it and that works fine
Sent from my U20i using XDA App
Click to expand...
Click to collapse
It's been a (long) while since i don't use Qemu (maybe i could give it a chance ;-)... the annoying thing is that folks here at XDA isn't so Opensource-proned and don't tend to share their sources :-/, for this unlocking procedure you've to bow down to Windows for the s1tool and that's so-so-so-so-so-so-so-so-so boring... on the other hand if s1tool's sources is available, someone could port it to GNU/Linux in order to have a complete platform independent task... but that's only my point of view i don't want to mess up with great gifts we receive from XDA
Cheers,
ff0000
Yeah its kinda sad that androids based off of linux but most of its utilities are windoze.... Yeah on sources it is useful to release but sometimes not
Sent from my U20i using XDA App
x10man said:
Yeah its kinda sad that androids based off of linux but most of its utilities are windoze.... Yeah on sources it is useful to release but sometimes not
Sent from my U20i using XDA App
Click to expand...
Click to collapse
I think sharing informations (in this case code sources) is always good to give people the opportunity to learn so to evolve... and i have no relationship with Richard Stallman at all! :-DDD
SteveBallmer said:
Monkey Dance to you! (me no like that idea oo oo ah ah!)
Click to expand...
Click to collapse
thats all i have to say to this.
Sorry. One off troll plus it was a jab at ballmer
Anyway have you tried asking the_laser for sources? He may give you them if you say you are porting to linux
Sent from my U20i using XDA App
x10man said:
Sorry. One off troll plus it was a jab at ballmer
Anyway have you tried asking the_laser for sources? He may give you them if you say you are porting to linux
Sent from my U20i using XDA App
Click to expand...
Click to collapse
No problem mate, i still can't do the monkey dance X-D... i should try in a drunken state X-DDD...
I asked him to include the script in the msm7227 package but it'd be better to ask the source of s1tool so i could totally port (if i'm able to ).
By the way, do any of you try my script?!? Is it working?
Thanks x10man,
ff0000.it
Cool man! I'll give it a shot. You should link to the original thread though
kissmyarch said:
Cool man! I'll give it a shot. You should link to the original thread though
Click to expand...
Click to collapse
Thanks mate,
in these day i'll see if it could be included in the_laser's package but first i've to be sure to be able to port s1tool or we stay with a foot on Windows and the other on GNU/Linux and that's not good
And what about flashtool? Is there a linux alternative? because I'm using it through Virtualbox and it's a little bit annoying.
Sorry I can't try your script since I've already unlocked... but thanks anyway.
ambrosiosanchez said:
And what about flashtool? Is there a linux alternative? because I'm using it through Virtualbox and it's a little bit annoying.
Sorry I can't try your script since I've already unlocked... but thanks anyway.
Click to expand...
Click to collapse
You could use Flashtool in GNU/Linux with Mono, but i never try it (however that's another annoying point)
I run the script on my unlocked phone and it worked fine (the_laser told me that i could run it how many times i want to) ;-)
But guys flashtool is on java! So you run it by
Code:
java -jar flashtool.jar
I've done it before
Oh and ff0000.it could you please include in your first post the download links of what we need to run with your script?
It's nice to have them all in one place rather than searching among several posts. Thanks!
i cant do a full unlock test but i can test on already unlocked if its ok and off topic i am able to do the monkey dance quite well btw there is a hilarious vid on utube called best of ballmer watch it. soooo funny LINUX FTW! btw what distro u on im either openSUSE or crunchbang depends on mood im in
kissmyarch said:
But guys flashtool is on java! So you run it by
Code:
java -jar flashtool.jar
I've done it before
Oh and ff0000.it could you please include in your first post the download links of what we need to run with your script?
It's nice to have them all in one place rather than searching among several posts. Thanks!
Click to expand...
Click to collapse
You're totally right... i was writing about Flashtool and thinking about SuperOneClick... my moronic brain has stricken again!
I added the link to the unlocking guide that has the link to the package ;-)
kissmyarch said:
But guys flashtool is on java! So you run it by
Code:
java -jar flashtool.jar
I've done it before
Oh and ff0000.it could you please include in your first post the download links of what we need to run with your script?
It's nice to have them all in one place rather than searching among several posts. Thanks!
Click to expand...
Click to collapse
Thanks! much easier than Virtualbox
Great! I just had to change the top line to #!/bin/bash (syntacs error with the sh interpreter) and run the script as root.
Knives & Forks
WHAT IS IT?
Knives & Forks is a set of Android tools for everyone. Every operating system, every device.
This cross-platform Android toolkit, written in Python, that is designed to work in Linux, Mac OS X or Windows. I wanted to create something that was unique, and offered a consistent and feature-filled set of tools for Android devs no matter what operating system they use, and for as many Android devices as possible.
WHAT DOES IT DO?
I just started work on this project, so it doesn't do very much yet. Right now we are just focusing on getting drivers and adb installed for as many devices as we can on all three platforms. Once we have adb working for everyone, the real fun can begin as we start to add more device tools that will make use of adb, such as rooting. Eventually ROM customization tools will be added, but we are focusing on device tools and cross-platform compatibility at this time.
View the changelog to see a list of included drivers. The only device that I can confirm is compatible with this script in Linux, Mac OS X, and Windows is the Samsung Galaxy S II, Sprint Epic 4G Touch. This just so happens to be my personal phone, but as I gather feedback I will create an official list of supported devices.
WHERE DO I GET IT?
This project is now being hosted by the Android Creative Syndicate. An up to date link to the most current version of the script, installation instructions for Linux, Max OS , and Windows, and other information can be found HERE. Registration is not required at the ACS forum to download or view installation instructions. You are free to reply in the thread you are reading right now if you don't want to register for another forum.
I HAVE IT INSTALLED, NOW WHAT?
You should be able to open up your terminal application (or command prompt) and run some adb commands. In the future we will be automating adb commands for you, but for now you can try the following as a simple test:
Code:
adb reboot
If everything worked, your Android device should reboot. For further reading on what you can do with adb you can read THIS PAGE.
HOW TO SUPPORT THIS PROJECT
FEEDBACK
Download my script, test it, let me know what happens. Let me know what other features/tools I should add.
THANKS
Hit the thanks button if you like what I'm doing here.
DONATIONS - I don't currently have a link to send me money, but I could quickly set something up if somebody decides they want to help me feed my kid. I am recently unemployed, but I am not relying on my scripting skills to feed my family. Save your cash for a more worthy project, or tuck it away and wait until the project turns into something amazing.
INFORMATION
TELL ME ABOUT YOUR ANDROID DEVICES!
If my script isn't getting adb setup for your device, let me know where to download the correct Windows driver and/or what udev rules I need to add in Linux.
The next phase of this project will be automating the rooting process. If you know the process for rooting your device, please share the details.
HOW TO REPLY TO THIS THREAD
Please do not reply by saying something like "This looks awesome, I'm going to download it now!".
Just download it, test it out, and then tell me about it.
If my script works for you, please don't post something like "It worked for me, this is the best thing since sliced bread!".
At the moment all my script will do is install adb and drivers for your device. In order to test please uninstall any drivers you may have already installed, run my script, then reply with the following information:
Operating System (including version and 32-bit or 64-bit architecture)
Android Device
If you open up a terminal/command prompt window and enter the following command, does your device reboot? If not, do you receive any error messages (while running that command or at any phase of running the Kinves & Forks script)?
Code:
adb reboot
CHANGELOG
Code:
------------------------------------------------------------------------------------
Knives & Forks: Changelog
------------------------------------------------------------------------------------
The most current version is available for download from:
http://knivesandforks.info/releases/knives-and-forks-current.php
**** 12.02.04 ****
http://knivesandforks.info/releases/knives-and-forks-12.02.04.php
- LINUX CHANGES:
-- "python2" is now called by "Knives-and-Forks-Linux.sh" instead of "python" on Arch.
- This prevents starting the script with Python 3, which results in errors.
-- Changes to "scripts/linux/install-adb-linux.sh":
- "su" will be used if "sudo" is not installed, or user doesn't have permissions to use it.
- Added 32-bit libs for more 64-bit distros:
- Arch (new in this release)
- CentOS (new in this release)
- Debian
- Fedora (new in this release)
- Ubuntu, Kubuntu, Xubuntu
- Added Debian version of '/etc/udev/rules.d/99-android.rules'
- Added '/lib/udev/rules.d/92-permissions.rules' for Debian.
This should fix permissions, allowing adb to run without sudo or su.
- WINDOWS CHANGES:
-- Fixed a couple of missing quotes which were breaking things under Windows XP
- "%userprofile%" was coming back as "c:\documents" instead of "c:\documents and settings\username" in a couple of places
-- "c:\python27" is now the only directory where we look for python.exe
- It is faster to download and install Python to "c:\Python27" than it is to search for it elsewhere.
- This will also prevent issues where Python 3 was installed instead of Python 2, since the script currently gives errors under Python 3.
-- Updated amd64 and x86 versions of setx.exe for updating system PATH on XP/VISTA/7
-- PATH is updated with adb.exe location after Python is installed.
-- The computer will now reboot after updating the PATH, to make sure it will be updated before running the main program.
**** 12.01.27 ****
http://knivesandforks.info/releases/knives-and-forks-12.01.27.php
- GENERAL CHANGES:
-- After adb is installed, adb will reset the android device by running "adb reboot" instead of displaying a list of attached devices with "adb devices".
adb was occasionally reporting no devices were attached, when they infact were. When this happened "adb reboot" still worked, so it is a better test to see if adb is setup properly.
-- Friendlier messages during adb install and testing
-- Added a startup check to make sure the script is running from the correct directory
-- Removed empty Project directory, as it is not being used yet.
- LINUX CHANGES:
-- Added support for "lxterminal" and "urxvt" in "Knifes-and-Forks-Linux.sh"
-- Changed idVendors for Linux udev rules to lowercase instead of uppercase.
- WINDOWS CHANGES:
-- Startup script searches for python in "C:\Program Files (x86)" then "C:\Program Files" and "c:\" last.
-- Drivers should now install even if the language is not English
-- Added drivers for Casio C771 G'zOne Commando
-- Added LG drivers
-- Replaced setx.exe
**** 12.01.25 ****
http://knivesandforks.info/releases/knives-and-forks-12.01.25.php
- Replaced "Knives-and-Forks-Mac.sh" with "Knives-and-Forks-Mac.app".
Starting the script on a Mac should now be as simple as double-clicking the new .app file.
**** 12.01.24 ****
http://knivesandforks.info/releases/knives-and-forks-12.01.24.php
- Fixed a typo which caused the script to crash when viewing the credits screen.
- Smarter python fix for Windows users.
-- "C:\" and all sub-directories are searched for python.exe.
-- If python is not not found, it will be downloaded from python.org and installed to c:\python27.
-- If python is found (in "C:\python27", "c:\python", "c:\xyz123", "c:\program files\python27" or in any directory with any name anywhere on drive c:) the main menu script will launch.
- Added changelog.txt to the release .zip file.
**** 12.01.23 ****
http://knivesandforks.info/releases/knives-and-forks-12.01.23.php
- Minor update to fix Python installation for Windows users, which was causing the script not to launch.
**** 12.01.22 ****
(FIRST PUBLIC RELEASE)
http://knivesandforks.info/releases/knives-and-forks-12.01.22.php
- Added option to install adb & fastboot for Linux, Windows, Mac
- Added Linux drivers for:
-- ACER
-- ASUS
-- DELL
-- FOXCONN
-- GARMIN-ASUS
-- Google
-- Hisense
-- HTC
-- HUAWEI
-- K-TOUCH
-- KT Tech
-- KYOCERA
-- LENEVO
-- LG
-- MOTOROLA
-- NEC
-- NOOK
-- NVIDIA
-- OTGV
-- PANTECH
-- PEGATRON
-- PHILIPS
-- PMC-SIERRA
-- QUALCOMM
-- SK TELESYS
-- SAMSUNG
-- SHARP
-- SONY ERICSSON
-- TOSHIBA
-- ZTE
- Added Mac drivers for:
-- Nothing. According to Google, "It just works." Let me know if they are right.
- Added a custom Windows installer with drivers for:
-- GOOGLE
-- HTC
-- HUAWEI
-- SAMSUNG
WHERE DID THE OLD POSTS GO?
In an attempt to reduce unnecessary clutter in my original thread, I created supporting threads in each Android device forum. The whole reason behind posting so many times was to keep certain information in the Chef Central post, and certain information out of it in an effort to reduce clutter. Who wants to read through 50 pages of how this, that, and the other thing is or isn't working on devices that you don't own? That system appeared to work very well, but apparently I broke the rules by posting in every Android device forum.
Learn from my mistakes, don't post similarly worded posts all over the place!
ATTENTION PYTHON PROGRAMMERS:
Any idea on what I can do to make the Python files work in Python 2 and Python 3? I have only tested in Python 2.7.2, but I have received reports that Python 3 gives errors. I'm not really doing anything all that fancy, so I'm not sure if something is just a matter or new syntax or something else needs to be imported or what. Any help would be appreciated.
The next release will call "python2" for Arch Linux users since "python" will use python 3.
ATTENTION LINUX USERS:
I am currently testing my Knives & Forks script in some virtual machines using VirtualBox, as well as my local Xubuntu installation.
For distro specific things (installing 32-bit libs, udev changes, etc) in the next release I will be detecting the distro using the following code:
Code:
echo " -- DETECTING LINUX DISTRO --"
if [ "`cat /etc/issue | grep Arch | wc -l`" == "1" ]; then
DISTRO_NAME="Arch"
elif [ "`cat /etc/issue | grep Cent | wc -l`" == "1" ]; then
DISTRO_NAME="CentOS"
elif [ "`cat /etc/issue | grep Debian | wc -l`" == "1" ]; then
DISTRO_NAME="Debian"
elif [ "`cat /etc/issue | grep Fedora | wc -l`" == "1" ]; then
DISTRO_NAME="Fedora"
elif [ "`cat /etc/issue | grep Ubuntu | wc -l`" == "1" ]; then
# DETECTS UBUNTU, KUBUNTU, XUBUNTU, ETC
DISTRO_NAME="Ubuntu"
else
DISTRO_NAME="UNKNOWN"
fi
echo " - $DISTRO_NAME"
Please let me know what other distros your using and if you are able to find the name using the "/etc/issue" method I am using in the above if statements.
I wrote a bash function to check if sudo is installed, and then to see if the current user has permissions to use sudo. If sudo is not installed, or if the current user does not have permission to use it, su will be used instead. This will be included in my next update, but I wanted to post it here first:
Code:
echo " -- CHECKING TO SEE IF 'SUDO' IS INSTALLED --"
CURRENT_USER=$USER
USE_SUDO="NO"
if [ -f "/usr/bin/sudo" ]; then
echo " - 'sudo' is installed."
echo ""
echo " -- CHECKING FOR PERMISSION TO USE 'SUDO' --"
echo ""
echo " If prompted, enter the password for the user '$CURRENT_USER'."
echo ""
if [ "$(sudo whoami)" != "root" ]; then
echo ""
echo " - Sorry, '$CURRENT_USER' does not have permission to use 'sudo'."
echo " - 'su' will be uses instead of 'sudo'."
echo ""
else
echo " - '$CURRENT_USER' has permission to use 'sudo'."
USE_SUDO="YES"
echo ""
fi
else
echo " - 'sudo' is not installed."
echo " - 'su' will be used instead of 'sudo'."
echo ""
fi
DO_SU()
{
echo ""
if [ $USE_SUDO == "YES" ]; then
# echo " -- USING 'SUDO' TO RUN '$1' --"
echo ""
echo " If prompted, enter the password for the user '$CURRENT_USER'."
echo ""
sudo $1
else
# echo " -- USING 'SU' TO RUN '$1' --"
echo ""
echo " If prompted, enter the password for the user 'root'."
echo ""
su -c "$1"
fi
echo ""
}
# EXAMPLE USAGE OF THE DO_SU() FUNCTION:
# NOTE THAT THE COMMAND TO RUN WITH SU OR SUDO HAS TO BE IN QUOTES
DO_SU "whoami"
I also found out why debian users were being forced to use sudo or su in order to use adb. The next release will include this fix, but for those who might be interested in making this change manually:
Open "/lib/udev/rules.d/91-permissions.rules" as root (su or sudo) in your favorite text editor and find this line
Code:
usbfs-like devices SUBSYSTEM==”usb”, ENV{DEVTYPE}==”usb_device”, \ MODE=”0664″
Change MODE to "0666"
Code:
usbfs-like devices SUBSYSTEM==”usb”, ENV{DEVTYPE}==”usb_device”, \ [B]MODE=”0666“[/B]
Instead of replacing or modifying your "/lib/udev/rules.d/91-permissions.rules" file, the next version of my script will actually create a "/lib/udev/rules.d/92-permissions.rules" for Debian users that contains only the following:
Code:
# usbfs-like devices
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", \
MODE="0666"
This file will load right after the 91-permissions.rules and replace just the usbfs-like devices settings. I'm just doing this with my script so I don't accidently break anything on your system. If you are making the changes manually, editing the 91-permissions.rules file should be all you need to do.
Save your changes and then restart udev as root (using sudo or su)
Code:
/etc/init.d/udev restart
-- or --
Code:
service udev restart
This assumes of course that you already have a working udev rule for your android device, and that adb is working only with su or sudo currently. Once this change is made you should be able to use adb without being forced to use su or sudo.
First post updated with latest release, version 12.02.04.
Lots of changes for XP and various Linux distros. See changelog for more information, but things should work better in Arch, CentOS, Debian, Fedora, and Ubuntu (including Kubuntu, Xubuntu, etc).
Hi, I just downloaded the latest file (12.02.04) but it's only 4 KB.
Could you check please?
Thank you!
Trying to unzip the file in Ubuntu 11.10 and this what I get:
Archive: knives-and-forks-12.02.04.zip
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of knives-and-forks-12.02.04.zip or
knives-and-forks-12.02.04.zip.zip, and cannot find knives-and-forks-12.02.04.zip.ZIP, period.
Any help?
I had a typo in the .zip filename, so if you tried to download the file yesterday you basically just downloaded an error message that the .php counter script gave when it couldn't find the file. I will have to take a look at that later because it is supposed to display the message not make you download it.
The problem is now fixed, sorry about that.
Thanks for update.
Downloaded and installed.
Now I can adb from linux.
Have one more question. I hope you can help me with that as well.
I don't see my device (E4GT) as external hard drive or USB drive when debuging is on to copy files to it.
When debuging is off it shows 2 Android devices but when I click on them I'm getting this message:
Error initializing camera: -60: Could not lock the device
Any ideas?
My guess is maybe they didn't get unmounted properly that last time you had it plugged in, but I have no idea why you would get an error message about the camera. I have not seen that one.
Try installing Dropbox and backing up anything important, then formatting the sdcard and try mounting again.
Maybe somebody else has had that error and has a better idea,
I'll try to format sd card tonight when I get home.
But what would be the problem with internal storage?
And what should or could I try to proper mount it?
agat63 said:
I'll try to format sd card tonight when I get home.
But what would be the problem with internal storage?
And what should or could I try to proper mount it?
Click to expand...
Click to collapse
First thing to check is that it isn't ROM related. Boot into recovery and try to mount as a usb drive and see if it works or not. If it does, I would say wipe and flash another ROM. If it doesn't work from recovery, then it could be a result of not unmounting before unplugging from your computer.
Sometimes if you have your phone mounted as a USB drive, or even just a regular flash drive, and it you unplug it before it is done unmounting (or if you don't use the safely remove hardward feature of Windows) the filesystem can get trashed. It hasn't happened alot with me, and I have seen the problem happen mostly when a flash drive is unplugged before the OS can finish writing to it.
After you get all of your important stuff backed up somewhere like dropbox, reboot into your recovery and repartition the sd card and/or your internal storage, whatever is giving you the problem. When you reboot into android you should be able to use it as normal, and dropbox should automatically copy everything back that you backed up.
This problem isn't really related to my script, so I if you can't get the issue resolved make a new post in Android QA or somewhere else. PM me if you post elsewhere and I can see if I can help you out there.
I didn't mean to say that the problem is related to your script.
Your script works just fine and I'm able to adb.
I'm kinda new to linux and still learning it.
I needed help and advise for how to connect phone to pc in linux.
It works in windows for me.
When I get on my PC I'm gnats give this awhirl. Ad for your mounting disk drives if ur on any ics rom it wont and I don't know how to enlighten me someone but if its gingerb then make sure u mount with the phones option when u plug in on ur handset ther should be some kind of way to switch between teather, disk and charge only? Wat fone u got?
Does this knife and forks compile? What does it do? Sorry to sound like a knob.
Sent from my GT-I9100 using XDA Premium App
This worked for my att gs2.
Sent from my GT-I9100 using Tapatalk
By using the Android Font you are violating their copyright rules. But you are free to modify the Android Robot, as long as you refer to them and say that you have permission.
Bad-Wolf said:
By using the Android Font you are violating their copyright rules. But you are free to modify the Android Robot, as long as you refer to them and say that you have permission.
Click to expand...
Click to collapse
The post where I found the font said it was an Android logo inspired font, and not the actual android logo font.
I have changed the font I'm using, and have updated my logo graphic to fight off any further concerns.
Colliebudz said:
Does this knife and forks compile? What does it do? Sorry to sound like a knob.
Click to expand...
Click to collapse
At the moment it simply automates getting adb setup on Linux, Mac, and Linux.
I have plans to add support for device rooting next, followed by some other adb commands, then rom customization tools as the last stage of development.
Pushing files to the phone, running shell commands, etc, requires that adb is setup properly, so that is where the focus is at right now. Getting the adb & driver installation scripts setup to run on all three platforms is also helping take care of some general troubleshooting, which is good to get out of the way before the main script gets tons of extra features.
All of this info should be in the first post, I'll try to clarify things when I make the next update.
Waddle said:
This worked for my att gs2.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Thanks for the feedback. What OS?
Im trying to jailbreak my phone with Adam's casual. I havent been able to get it to work and he asks for the log if it is not working. I am not new to rooting or romming, I just dont post in xda so I am unable to post in the development section. Can someone get my log over to him so I can figure out why I cant get mine to work. I am rooted and running casual on windows xp 64 bit machine
Thanks
[/CODE]
Created Folder:C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\
Picking Jar File:/C:/Users/brandi/Desktop/CASUAL-BackAtchaVerizon-Revision311b%20(1).jar
Found Windows Computer
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\Elevate.exe
File verified.
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\adb.exe
File verified.
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\AdbWinApi.dll
File verified.
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\AdbWinUsbApi.dll
File verified.
sleeping for Windows ADB start
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\-adb_usb.ini
File verified.
###executing: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\adb.exe###
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
Found: WindowsLinux Galaxy Note 2 Jailbreak
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
Control Change requested but lock is set.
OMFGWOOT GUI running!
This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2.
Searching for scripts
Updating Scripts for UI
From Resource: true
State Change Detected, The new state is: 1
State Connected
--WindowsLinux Galaxy Note 2 Jailbreak--
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
Exiting comboBoxUpdate()
Extracting archive....
Unzipping Superuser.apk
Control Change requested but lock is set.
Unzipping boot.img
Unzipping busybox
Unzipping dependentinstaller.sh
Unzipping exploit
Unzipping exynos-abuse
Unzipping recoverThis
Unzipping rootGN.sh
Unzipping su
Unzipping swagBoot
Unzipping viewmem
Controls Enabled status: true
State Change Detected, The new state is: 1
State Connected
Controls Enabled status: true
StartButtonActionPerformed() Script Activated
Script known as WindowsLinux Galaxy Note 2 Jailbreak is running
Controls Enabled status: false
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
Selected resourceWindowsLinux Galaxy Note 2 Jailbreak
Lines in Script 75
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
***WEB VERSION***[Ljava.lang.String;@1553d18
Identification: VERIZON GNOTE
ScriptRevision: 2
CASUALRevision: 308
URL: http://forum.xda-developers.com/showthread.php?t=2118348
Server Message: UPDATE: removing limits on Mac for testing purposes
Current Version 1 requires update to version 2
Script is out of date. See http://forum.xda-developers.com/showthread.php?t=2118348 for more information. Updating.
UPDATE: removing limits on Mac for testing purposes
Created Folder:C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\SCRIPTS\
Downloading Updates
Downloading http://android-casual.googlecode.co...IPTS/WindowsLinux Galaxy Note 2 Jailbreak.scr
To: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\/SCRIPTS/WindowsLinux Galaxy Note 2 Jailbreak.scr
... Update Sucessful! MD5s verified!
Associated Script WindowsLinux Galaxy Note 2 Jailbreak with #0WindowsLinux Galaxy Note 2 Jailbreak
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
Selected fileC:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\SCRIPTS\WindowsLinux Galaxy Note 2 Jailbreak
Lines in Script 65
Reading [email protected]
new command: $USERCANCELOPTION Are you sure?, This is your only warning.\n You will be Unlocked and Rooted. Your device will\n reboot once and then again into Odin mode. CASUAL\n will then flash the Back Atcha Verizon Odin Bootloader\n package for you.
SCRIPT COMMAND:$USERCANCELOPTION Are you sure?, This is your only warning.\n You will be Unlocked and Rooted. Your device will\n reboot once and then again into Odin mode. CASUAL\n will then flash the Back Atcha Verizon Odin Bootloader\n package for you.
COMMAND processed - C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\adb.exe Are you sure?, This is your only warning.
You will be Unlocked and Rooted. Your device will
reboot once and then again into Odin mode. CASUAL
will then flash the Back Atcha Verizon Odin Bootloader
package for you.
new command: $ECHO Rebooting into download mode
SCRIPT COMMAND:$ECHO Rebooting into download mode
Received ECHO command$ECHO Rebooting into download mode
Rebooting into download mode
new command:
new command:
new command:
new command: $ADB reboot download
SCRIPT COMMAND:$ADB reboot download
sending
###executing: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\adb.exe###
return from ADB:
new command: $HEIMDALL flash --8 "$ZIPFILEboot.img"
SCRIPT COMMAND:$HEIMDALL flash --8 "$ZIPFILEboot.img"
Expanded $ZIPFILE: $HEIMDALL flash --8 "C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\WindowsLinux Galaxy Note 2 Jailbreak\boot.img"
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\libusb-1.0.dll
File verified.
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\heimdall.exe
File verified.
detected!
###executing real-time command: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\heimdall.exe###
WindowsLinux Galaxy Note 2 Jailbreak.scrWaiting for Downoad Mode device.Heimdall v1.4 RC2
Copyright (c) 2010-2012, 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...
Heimdall v1.4 RC2
Copyright (c) 2010-2012, 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...
ERROR: Failed to access device. libusb error: -12
Installing drivers
Driver Problems suck. Lemme make it easy.
1. Check that your device is download mode and connected up.
2. Select the one that says ---Gadget Serial--- in the main window
3. Click ---install driver---.
4. Close out zadig and use CASUAL.Note: the USB port which you install this driver will be converted
to use Heimdall instead of Odin for download mode. It only affects
ONE usb port.
Downloading https://android-casual.googlecode.com/svn/trunk/repo/zadig.exe
To: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\zadig.exe
Downloading https://android-casual.googlecode.com/svn/trunk/repo/zadig.ini
To: zadig.ini
###executing: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\Elevate.exe###
###executing real-time command: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\heimdall.exe###
ERROR: Failed to access device. libusb error: -12Open-Source Heimdall DriversOpen-Source Heimdall Drivers configHeimdall v1.4 RC2
Copyright (c) 2010-2012, 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...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Releasing device interface...
Heimdall v1.4 RC2
Copyright (c) 2010-2012, 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...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Releasing device interface...
ERROR: Protocol initialisation failed!
new command:
new command:
new command: $ECHO Your device should be rebooting into Android now.
SCRIPT COMMAND:$ECHO Your device should be rebooting into Android now.
Received ECHO command$ECHO Your device should be rebooting into Android now.
Your device should be rebooting into Android now.
new command: $ADB wait-for-device
SCRIPT COMMAND:$ADB wait-for-device
sending
###executing: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\adb.exe###
Code:
He's said xp isn't supported. That's why it isn't working. Try to find a more up to date computer
Sent from my SCH-I605 using Tapatalk 2
kintwofan said:
He's said xp isn't supported. That's why it isn't working. Try to find a more up to date computer
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Please, please send log again, this wasn't done on an xp machine this was done on windows 7 64 bit. I originally tried it on an xp machine at home and it didn't do anything it just stayed on the download screen so I took it to work and ran it on windows 7 64 bit and it still wouldn't work but did go a lot further and produced this log. I typed that by mistake. Thank you for your help
brandi1693 said:
Please, please send log again, this wasn't done on an xp machine this was done on windows 7 64 bit. I originally tried it on an xp machine at home and it didn't do anything it just stayed on the download screen so I took it to work and ran it on windows 7 64 bit and it still wouldn't work but did go a lot further and produced this log. I typed that by mistake. Thank you for your help
Click to expand...
Click to collapse
You know you can pm him
Sent from my SCH-I605 using xda app-developers app
Bfitz26 said:
You know you can pm him
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
No I didn't know, I have lurked around xda for years now but never posted or responded. How do I pm him?
find his thread for his jailbreaking procedure click on his name then there should be a option to message him simple bud
Bfitz26 said:
find his thread for his jailbreaking procedure click on his name then there should be a option to message him simple bud
Click to expand...
Click to collapse
Thank you everyone for your help, I finally got the bootloader unlocked. No need to send the log to Adam
brandi1693 said:
Thank you everyone for your help, I finally got the bootloader unlocked. No need to send the log to Adam
Click to expand...
Click to collapse
I'm having trouble with Casual as well, it reboots my phone into download then hangs. I don't even get a chance for errors to happen! I thought it was my drivers at first, but everything is loaded just fine. Does anyone else have this problem? I'm on a WIN7 64bit, going to try linux tonight when I get off of work.
I am very interested in whether Linux works for you. Please post your results. Thank you!
Sent from my SCH-I605 using Tapatalk 2
randy6675 said:
I am very interested in whether Linux works for you. Please post your results. Thank you!
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Ubuntu worked just fine, but when I flashed a rom in twrp I got the triangle, so maybe it didnt work correctly.
Unfortunately, I have to go in early so I cant mess with it again until tomorrow, just restored back to stock and updating all my apps.
Hello friends!
I am using Termux in order to run ruby.
I installed ruby successfully with "apt" command, and it functions fine.
Current ruby version:
Code:
$ ruby -v
ruby 2.3.3p222 (2016-11-21 revision 56859) [arm-linux-androideabi]
The problem is, I can't really install gems. I tried to install bettercap for the experiment, but it failed. This is what I get:
Code:
$ gem install bettercap
Fetching: colorize-0.8.1.gem (100%)
Successfully installed colorize-0.8.1
Fetching: network_interface-0.0.1.gem (100%)
Building native extensions. This could take a while...
ERROR: Error installing bettercap:
ERROR: Failed to build gem native extension.
current directory: /data/data/com.termux/files/usr/lib/ruby/gems/2.3.0/gems/network_interface-0.0.1/ext/network_interface_ext
/data/data/com.termux/files/usr/bin/ruby -r ./siteconf20161129-14856-1cclchu.rb extconf.rb
mkmf.rb can't find header files for ruby at /data/data/com.termux/files/usr/lib/ruby/include/ruby.h
extconf failed, exit code 1
Gem files will remain installed in /data/data/com.termux/files/usr/lib/ruby/gems/2.3.0/gems/network_interface-0.0.1 for inspection.
Results logged to /data/data/com.termux/files/usr/lib/ruby/gems/2.3.0/extensions/arm-linux/2.3.0/network_interface-0.0.1/gem_make.out
I found some instructions if I ran "gem help install" but I couldn't really understand what to do in order to fix that.
Can anyone help me to solve this? BTW I have a rooted device so I can use "su" and "sudo" and all that stuff...
Thanks for people who answer~
FurySh0ck said:
Code:
mkmf.rb can't find header files for ruby at /data/data/com.termux/files/usr/lib/ruby/include/ruby.h
Click to expand...
Click to collapse
You can install ruby.h with:
Code:
apt install ruby-dev
.
fornwall said:
You can install ruby.h with: .
Click to expand...
Click to collapse
I installed ruby-dev but it still won't work. It tells me it saved a log file which contains the explanation to the failure. I'll post the whole code, but please pay attention to the last part of it:
Code:
apt install bettercap
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package bettercap
$ gem install bettercap
Building native extensions. This could take a while...
ERROR: Error installing bettercap:
ERROR: Failed to build gem native extension.
current directory: /data/data/com.termux/files/usr/lib/ruby/gems/2.3.0/gems/network_interface-0.0.1/ext/network_interface_ext
/data/data/com.termux/files/usr/bin/ruby -r ./siteconf20161206-31345-1xerjr9.rb extconf.rb
[*] Running checks for netifaces code...
[*] Warning : this platform as not been tested
checking for getifaddrs()... *** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.
Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/data/data/com.termux/files/usr/bin/$(RUBY_BASE_NAME)
/data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:456:in `try_do': The compiler failed to generate an executable file. (RuntimeError)
You have to install development tools first.
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:541:in `try_link0'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:556:in `try_link'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:765:in `try_func'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:1051:in `block in have_func'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:942:in `block in checking_for'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:350:in `block (2 levels) in postpone'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:320:in `open'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:350:in `block in postpone'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:320:in `open'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:346:in `postpone'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:941:in `checking_for'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:1050:in `have_func'
from extconf.rb:43:in `<main>'
To see why this extension failed to compile, please check the mkmf.log which can be found here:
/data/data/com.termux/files/usr/lib/ruby/gems/2.3.0/extensions/arm-linux/2.3.0/network_interface-0.0.1/mkmf.log
extconf failed, exit code 1
Gem files will remain installed in /data/data/com.termux/files/usr/lib/ruby/gems/2.3.0/gems/network_interface-0.0.1 for inspection.
Results logged to /data/data/com.termux/files/usr/lib/ruby/gems/2.3.0/extensions/arm-linux/2.3.0/network_interface-0.0.1/gem_make.out
Any solutions in mind?
BTW Thanks for your time, I appreciate anyone who tries to help.