[#nexusmultitoolp1]
If you like it, you might consider donating.
DOWNLOADS
Source Code - Github
[#nexusmultitoolp2]
XDA:DevDB Information
Nexus Multitool, Tool/Utility for the Nexus 9
Contributors
photonicgeek, photonicgeek
Version Information
Status: Beta
Current Beta Version: 0.10
Beta Release Date: 2014-11-23
Created 2014-11-20
Last Updated 2014-11-24
[#nmchangelog]
Reserved for stuff. Maybe.
Looks like a nice tool, thanks very much ?
Pushed out another update!
Is there anything you guys want to see this utility do?
I currently have these features planned:
Custom ROM downloads for different devices (OmniROM, Paranoid Android, Cyanogenmod, etc.)
Disable forced encryption on the Nexus 9 and Nexus 6
Sounds great, downloading will try it out asap.
Windows version?
Edit: Nevermind. I see there is another toolbox in the forum compiled for windows.
Sent from my Nexus 9 using XDA Free mobile app
Hi,
This tools seems to be very interesting.
I tried it on my Nexus 9 following instruction (download, chmod) but when I open the script I have this message:
"This is not a Nexus device. This utility only supports Nexus devices.
Press [Enter] to exit the script."
I don't know if I am missing some thing.
The Nexus 9 is connected through USB. Developper options are active with USB debugging. I tried also with Nexus 9 in bootloader fastboot USB but same results.
Thank you for your help
Bye
Didi666 said:
Hi,
This tools seems to be very interesting.
I tried it on my Nexus 9 following instruction (download, chmod) but when I open the script I have this message:
"This is not a Nexus device. This utility only supports Nexus devices.
Press [Enter] to exit the script."
I don't know if I am missing some thing.
The Nexus 9 is connected through USB. Developper options are active with USB debugging. I tried also with Nexus 9 in bootloader fastboot USB but same results.
Thank you for your help
Bye
Click to expand...
Click to collapse
That's odd, because even trying it now with my Nexus 9 it still works. Can you run
On a Mac:
Code:
~/Nexus-Multitool/all/tools/mac-adb shell getprop ro.product.model
~/Nexus-Multitool/all/tools/mac-adb shell getprop ro.product.name
On Linux:
Code:
~/Nexus-Multitool/all/tools/linux-i386-adb shell getprop ro.product.model
~/Nexus-Multitool/all/tools/linux-i386-adb shell getprop ro.product.name
And paste the results here?
NOTE: You need the device plugged in for it to work.
Nice tool
Will try it out
I'm on a Mac too and have run into the same
"This is not a Nexus device. This utility only supports Nexus devices."
I do have adb working on my Mac on my desktop. I know how to connect that way.
Out of curiosity I wanted to see this run on my Mac as there's just not much out there.
Ran the script after chmod.
In looking not all directories are created, particularly the adb-mac directory within the tools folder .
The only thing there is wget.
Code:
Connecting to device and reading device information.
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 101: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 102: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 103: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 104: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 105: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 106: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 107: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 108: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
So running the lines you requested above fails as the file/folder does not exist.
I'm your average Mac user and generally do not get to far into running .sh files.
I was able to chmod it and get it to run but ended with it's not a nexus device.
jmjm003 said:
I'm on a Mac too and have run into the same
"This is not a Nexus device. This utility only supports Nexus devices."
I do have adb working on my Mac on my desktop. I know how to connect that way.
Out of curiosity I wanted to see this run on my Mac as there's just not much out there.
Ran the script after chmod.
In looking not all directories are created, particularly the adb-mac directory within the tools folder .
The only thing there is wget.
Code:
Connecting to device and reading device information.
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 101: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 102: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 103: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 104: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 105: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 106: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 107: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 108: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
So running the lines you requested above fails as the file/folder does not exist.
I'm your average Mac user and generally do not get to far into running .sh files.
I was able to chmod it and get it to run but ended with it's not a nexus device.
Click to expand...
Click to collapse
Oh god, I found the issue. I think. I'm uploading v0.11 now! And it was a single simple line of code!
v0.11 ends the same for me as 10 did.
jmjm003 said:
v0.11 ends the same for me as 10 did.
Click to expand...
Click to collapse
Try deleting the entire ~/Nexus-Multitool directory.
It worked after doing that. I didn't test it any further right now as I'm not ready to redo everything today.
Looks promising and I appreciate the work.
jmjm003 said:
It worked after doing that. I didn't test it any further right now as I'm not ready to redo everything today.
Looks promising and I appreciate the work.
Click to expand...
Click to collapse
Ok, Let me know how it turns out!
I used it to do a backup and then it transferred it to my laptop. That worked fine.
Being a Mac user, it's nice to have something to do the process for me.
jmjm003 said:
I used it to do a backup and then it transferred it to my laptop. That worked fine.
Being a Mac user, it's nice to have something to do the process for me.
Click to expand...
Click to collapse
That's what I set out to do!
hi photonicgeek,
I retry to launch the script 0.11 (mac user) and I get same problem as jmjm003. But I think I did not catch what to do by "Try deleting the entire ~/Nexus-Multitool directory."
I try to delet the file et redownload it but still same results.
Code:
Connecting to device and reading device information.
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 102: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 103: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 104: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 105: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 106: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 107: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 108: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 109: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
Thank you for your help
---------- Post added at 08:48 PM ---------- Previous post was at 08:34 PM ----------
Sorry I catch it now and it work well. Great tool. Thank you.
Didi666 said:
hi photonicgeek,
I retry to launch the script 0.11 (mac user) and I get same problem as jmjm003. But I think I did not catch what to do by "Try deleting the entire ~/Nexus-Multitool directory."
I try to delet the file et redownload it but still same results.
Code:
Connecting to device and reading device information.
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 102: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 103: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 104: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 105: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 106: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 107: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 108: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 109: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
Thank you for your help
Click to expand...
Click to collapse
Yeah, i know whats wrong, and I'm trying to push an update, but XDA is having issues with accepting uploads. Run these commands:
Code:
xcode-select --install
rm -rf ~/Nexus-Multitool
Then run the script again.
Related
Hey guys. I am attempting to install Ubuntu on my rooted Samsung Infuse 4G. I have consulted several how-to articles here and elsewhere, but after several hours of work I am still stuck on the final lines of code in the terminal emulator app that a YouTube tutorial suggested. Below is the code that I have entered thus far, and the error code at the bottom of the list:
-----------------
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at AndroLinux.com ,G2Hacks.com and NexusOneHacks.net
To enter the Ubuntu Linux console just type 'bootubuntu'
# bootubuntu
losetup: /dev/block/loop1/sdcard/ubuntu/ubuntu.img: Not a directory
mount: Invalid argument
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
Setting localhost on /etc/hosts
bootubuntu: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Ubuntu
failed.
failed.
failed.
failed.
losetup: /dev/loop1: Device or resource busy
# bootubuntu
mknod: /dev/loop1: File exists
losetup: /dev/block/loop1/sdcard/ubuntu/ubuntu.img: Not a directory
mount: Invalid argument
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
Setting localhost on /etc/hosts
bootubuntu: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Ubuntu
failed.
failed.
failed.
failed.
losetup: /dev/loop1: Device or resource busy
#
---------------------
I have tried two different installation methods. The first one focused on accessing the advanced shell through Windows Command Prompt. This didn't work because the prompt froze after I typed in "advanced shell" (several attempts brought same results) .
I then tried the "easy" version that involved the terminal emulator app in the place of the command prompt. Assumedly, if I can resolve this last issue without causing any more, I should be able to access Ubuntu through Android VNC. It may be important to note that the time before last when I typed in the above code, I got a different error code. That error read: losetup: /dev/loop1: no such device or address. I don't know what made it change.
I can provide further info if needed. Can anyone plz help?
Sent from my SAMSUNG-SGH-I997 using XDA App
Sent from my SAMSUNG-SGH-I997 using XDA App
Sorry, as far as I know there is currently no way to install Ubuntu on the Infuse 4G. But I'll be working on a rom for it and I'll contact you if it works.
Sorry.
Sent from my SGH-I997 using xda premium
calvinllyman said:
Hey guys. I am attempting to install Ubuntu on my rooted Samsung Infuse 4G. I have consulted several how-to articles here and elsewhere, but after several hours of work I am still stuck on the final lines of code in the terminal emulator app that a YouTube tutorial suggested. Below is the code that I have entered thus far, and the error code at the bottom of the list:
-----------------
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at AndroLinux.com ,G2Hacks.com and NexusOneHacks.net
To enter the Ubuntu Linux console just type 'bootubuntu'
# bootubuntu
losetup: /dev/block/loop1/sdcard/ubuntu/ubuntu.img: Not a directory
mount: Invalid argument
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
Setting localhost on /etc/hosts
bootubuntu: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Ubuntu
failed.
failed.
failed.
failed.
losetup: /dev/loop1: Device or resource busy
# bootubuntu
mknod: /dev/loop1: File exists
losetup: /dev/block/loop1/sdcard/ubuntu/ubuntu.img: Not a directory
mount: Invalid argument
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
Setting localhost on /etc/hosts
bootubuntu: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Ubuntu
failed.
failed.
failed.
failed.
losetup: /dev/loop1: Device or resource busy
#
---------------------
Click to expand...
Click to collapse
OK. While you can't do it on the infuse. Ever. You could get the lg optimus g which once Ubuntu touch gets CDMA will get Ubuntu touch soon after!
Sent from my LG-LS970 using xda app-developers app
Has anyone had any success in booting Backtrack 5 on their Nexus 10?
I just unlocked, rooted, and added the cyanogenmod to my phone.
But I can't seem to get backtrack to launch, and get the below errors:
[email protected]:/ # su
[email protected]:/ # cd /sdcard/bt5
[email protected]:/sdcard/bt5 # sh bootbt
mkdir failed for -p, File exists
Loop device exists
ioctl LOOP_SET_FD failed: Device or resource busy
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
net.ipv4.ip_forward = 1
bootbt[23]: can't create /data/local/mnt/etc/resolv.conf: No such file or directory
bootbt[24]: can't create /data/local/mnt/etc/hosts: No such file or directory
chroot: can't execute '/bin/bash': No such file or directory
Shutting down BackTrack ARM For Xoom
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: Invalid argument
1|[email protected]:/sdcard/bt5 #
Click to expand...
Click to collapse
and I basically followed these steps.
http://back-track-linux.blogspot.com/2012/10/install-backtrack-on-android-tablet.html
I'd guess that the script they're using to start it isn't set up for the path storage is mounted to on the N10. I'd check myself, but it seems you need to download the whole thing to just get the script, and I"m not doing that.
If that's the case, it should be a pretty easy fix.
I know this an old thread but i would try
Code:
cd /storage/emulated/legacy/bt5/
hello
i have samsung galaxy s2 I9100
i want to run backtrack 5 on the phone but i have a problem with this command " sh bootbt "
i searched for it in this forum but didnt find the solution for it.
Code:
[email protected]:/ $ su
[email protected]:/ # cd sdcard/BT5
[email protected]:/sdcard/BT5 # sh bootbt
open backing file failed: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
net.ipv4.ip_forward = 1
bootbt: line 23: can't create /data/local/mnt/etc/resolv.conf: nonexistent directory
bootbt: line 24: can't create /data/local/mnt/etc/hosts: nonexistent directory
chroot: can't execute '/bin/bash': No such file or directory
Shutting down BackTrack ARM For Xoom
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: Invalid argument
1|[email protected]:/sdcard/BT5 #
some information about the phone:
Android version
4.1.2
Basseband version:
I9100XXLS8
Kernel Version:
[email protected]
Build number:
JZO54K.I9100XWLSD
- the phone is rooted
- busybox is installed and updated
so how i can fix this problem?
There is a thread about backtrack.Theres also something about using backtrack in the hackers handbook app.
theunderling said:
There is a thread about backtrack.Theres also something about using backtrack in the hackers handbook app.
Click to expand...
Click to collapse
thanks.. ur post was very helpful
Can you give the thread link plz.....
Here you go (Google search 'XDA Backtrack SGS2').
Alright. I'm attempting to get backtrack running. Obviously. Here's my terminal thus far.
[email protected]:/ $ su
[email protected]:/ # cd sdcard/BT5 # sh bootbt
[email protected]:/sdcard/BT5 # sh bootbt
Loop device exists
open backing file failed: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
net.ipv4.ip_forward = 1
bootbt[23]: can't create /data/local/mnt/etc/resolv.conf: No such file or directory
bootbt[24]: can't create /data/local/mnt/etc/hosts: No such file or directory
chroot: can't execute '/bin/bash': No such file or directory
Shutting down BackTrack ARM For Xoom
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: Invalid argument
1|[email protected]:/sdcard/BT5 #
As you can see. I have superuser rights and the file exists in that area. So I'm not sure why it won't work.
I'm running CyanogenMod 10.1.2 and I have busy box smart installed using the Terminal Emulator. Downloaded backtrack 5 arm version from the website itself and extracted it to sdcard/BT5
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
ryno9100 said:
Alright. I'm attempting to get backtrack running. Obviously. Here's my terminal thus far.
[email protected]:/ $ su
[email protected]:/ # cd sdcard/BT5 # sh bootbt
[email protected]:/sdcard/BT5 # sh bootbt
Loop device exists
open backing file failed: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
net.ipv4.ip_forward = 1
bootbt[23]: can't create /data/local/mnt/etc/resolv.conf: No such file or directory
bootbt[24]: can't create /data/local/mnt/etc/hosts: No such file or directory
chroot: can't execute '/bin/bash': No such file or directory
Shutting down BackTrack ARM For Xoom
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: Invalid argument
1|[email protected]:/sdcard/BT5 #
As you can see. I have superuser rights and the file exists in that area. So I'm not sure why it won't work.
I'm running CyanogenMod 10.1.2 and I have busy box smart installed using the Terminal Emulator. Downloaded backtrack 5 arm version from the website itself and extracted it to sdcard/BT5
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Did you make it? How?
mdorey said:
Did you make it? How?
Click to expand...
Click to collapse
I did makeit. I deleted my backtrack files and redownloaded them. It either didn't fullydownload, or a file got corrupted in the process,but once I redownloaded it, it worked fine!
Im attempting to root my Galaxy S4 using saferoot as detailed here: http://forum.xda-developers.com/showthread.php?t=2565758&page=172
Android Version is 4.3
Build Version: VRUEMK2
Kernel Version 3.4.0
Here is the output I get:
Code:
./install.sh
--- Samsung i545 VRUEMJ7 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---
./install.sh: 11: [: X: unexpected operator
[*] Testing adb usability
Plug in your phone and press ENTER to continue ..../install.sh: 67: read: arg count
./install.sh: 68: ./install.sh: files/adb.linux: not found
Watch your phone. If you see the "Allow USB debugging" prompt,
tap on the "Always allow from this computer" checkbox,
then tap OK.
If this script appears to be stuck at "Waiting for your phone to appear",
then you should try unplugging and re-plugging it to get the
permission prompt for USB debugging to appear.
If you've already done that, you should tap on the USB icon
in the notifications area that says "Connected as a media device".
On the "USB computer connection" page, switch between
"Camera" and "Media Device" to see if the device appears.
[*] Waiting for your phone to appear...
Watch your phone. Unlock it and give permission for the install to run.
./install.sh: 85: ./install.sh: files/adb.linux: not found
[*] Your phone is detected and ready for rooting.
[*] Sending files to your device...
./install.sh: 92: [: missing ]
./install.sh: 95: ./install.sh: files/adb.linux: not found
./install.sh: 96: [: missing ]
[*] Starting rooting program.
./install.sh: 99: ./install.sh: files/adb.linux: not found
[*] Checking if rooting succeeded
./install.sh: 102: ./install.sh: files/adb.linux: not found
[*] Unfortunately, rooting failed. Cleaning up.
./install.sh: 105: ./install.sh: files/adb.linux: not found
./install.sh: 106: ./install.sh: files/adb.linux: not found
./install.sh: 107: [: missing ]
./install.sh: 108: ./install.sh: files/adb.linux: not found
./install.sh: 109: ./install.sh: files/adb.linux: not found
--- All Finished ---
I set permissions to 777 for all files and subdirectories. files/adb.linux is where it should be.
Can anybody help?
Anybody?
nlhaines12 said:
Anybody?
Click to expand...
Click to collapse
Don't push via ADB; run the script on a Windows PC. Read the OP.........
http://forum.xda-developers.com/showthread.php?t=2565758
cbmggm said:
Don't push via ADB; run the script on a Windows PC. Read the OP.........
http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
Read the OP and there are directions for Linux/Mac OS. Why would I need windows?
nlhaines12 said:
Read the OP and there are directions for Linux/Mac OS. Why would I need windows?
Click to expand...
Click to collapse
He assumed you had pushed the saferoot files directly to your phone and attempted to run them on it.
If you are using an actual computer, then the problem is your shell/interpreter. Try running the script by opening a terminal, cd to the extracted directory, and then "bash install.sh".
Ah, that makes sense, thanks a ton. Maybe this is a noobish question, but why doesn't the install.sh file just contain the hashbang line at the beginning?
nlhaines12 said:
Ah, that makes sense, thanks a ton. Maybe this is a noobish question, but why doesn't the install.sh file just contain the hashbang line at the beginning?
Click to expand...
Click to collapse
Tried running the install script with "bash install.sh", and it works a but better, but I'm still getting the same file not found error.
Code:
--- Samsung i545 VRUEMJ7 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---
Do you want to install Busybox on your device [Y/N]? y
[*] Testing adb usability
Plug in your phone and press ENTER to continue ...
install.sh: line 68: files/adb.linux: No such file or directory
Watch your phone. If you see the "Allow USB debugging" prompt,
tap on the "Always allow from this computer" checkbox,
then tap OK.
If this script appears to be stuck at "Waiting for your phone to appear",
then you should try unplugging and re-plugging it to get the
permission prompt for USB debugging to appear.
If you've already done that, you should tap on the USB icon
in the notifications area that says "Connected as a media device".
On the "USB computer connection" page, switch between
"Camera" and "Media Device" to see if the device appears.
[*] Waiting for your phone to appear...
Watch your phone. Unlock it and give permission for the install to run.
install.sh: line 85: files/adb.linux: No such file or directory
[*] Your phone is detected and ready for rooting.
[*] Sending files to your device...
install.sh: line 92: [: missing `]'
install.sh: line 95: files/adb.linux: No such file or directory
install.sh: line 96: [: missing `]'
[*] Starting rooting program.
install.sh: line 99: files/adb.linux: No such file or directory
[*] Checking if rooting succeeded
install.sh: line 102: files/adb.linux: No such file or directory
[*] Unfortunately, rooting failed. Cleaning up.
install.sh: line 105: files/adb.linux: No such file or directory
install.sh: line 106: files/adb.linux: No such file or directory
install.sh: line 107: [: missing `]'
install.sh: line 108: files/adb.linux: No such file or directory
install.sh: line 109: files/adb.linux: No such file or directory
--- All Finished ---
What do you get if you run, from the saferoot directory "files/adb.linux"?
It looks like the rest of the script is working now, so you might just try downloading adb from the sdk and replacing files/adb.linux with a symlink to it.
im having this same problem. I dont know what a symlink is, im kind of a programming noob. Did anyone figure out how make this work?