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?
Related
As promised, I've published my root exploit. It's possible that this exploit will wipe your /data partition. This did not happen on the two devices that have been successfully rooted, but I don't want any nasty surprises. Please back up your applications and data if you're worried about this. There is no risk of permanent damage to the device, but by running this exploit, you assume all responsibilty.
You can root your device with the following steps:
1. Ensure your device is in USB debugging mode, is connected to your PC, and that ADB works. Instructions on this are available in this thread:
http://forum.xda-developers.com/showthread.php?t=1327139
2. Download the exploit here:
http://vulnfactory.org/public/Sony_Tablet_S_Root_Windows.zip
3. Unzip the full contents of the zip.
4. Run "run.bat"
---
Full details on how the exploit works are posted here:
http://vulnfactory.org/blog/2012/02/08/rooting-the-sony-tablet-s/
I can't guarantee that this exploit will work after receiving an OTA update, including ICS. As always, when rooted, be cautious of accepting OTA updates unless you have received confirmation that the root exploit has not been patched.
If you pledged towards the bounty, details on how to donate are at the bottom of the above blog post.
Enjoy,
Dan Rosenberg (@djrbliss)
P.S. For those interested in reposting this, I have no affiliation with any forum (including XDA).
nice work!
What is the indicator of success?
I get to * daemon started successfully *, but nothing more.
@ejchis: Superuser.apk should be installed on your device and apps that needs root rights should work now (Titanium backup, AdwareBlock ect)
obicom said:
@ejchis: Superuser.apk should be installed on your device and apps that needs root rights should work now (Titanium backup, AdwareBlock ect)
Click to expand...
Click to collapse
Thanks. I'm not getting to that point for some reason. I think my adb is not functioning properly. I need to play with this some more. I've always been a terminal emulator guy, so I'm not particularly confident with my adb skills.
I can confirm that this works perfectly. Let's hope this is but the first step in making this an awesome device. Many thanks!!!
use the command "adb devices" you should see what looks like a serial number show up. If nothing shows up then you have a problem with your ADB drivers. You may just need to restart the computer.
Thank !!!
Rooted
.............
Awesome! Works great! THX!!
Works great ... full respect from my side .... well done ... !!
YOU ARE MY HERO !!!!
My adb was being funky. I found a post somewhere else through Google where someone had to rename their adb.exe file to adb.exe.exe, reboot their computer, and rename the file back to adb.exe. I did this as a stab in the dark, and my command prompt suddenly began working for me. Tablet is currently rebooting for a third time. I'm keeping my fingers crossed.
EDIT: SUCCESS! Thank you, djrbliss.
Great, thank you for this !
I tried to use the exploit after a factory reset, and I can't get it to work.
Code:
F:\Desktop\Sony_Tablet_S_Root_Windows>run.bat
[*]
[*] Sony Tablet S root script (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that ADB
[*] is working properly, and that your tablet is connected via USB.
[*]
[*] WARNING: This exploit may result in wiping your /data partition,
[*] causing you to lose any applications and data on your tablet.
[*] There should be no risk of permanent damage to your device, but
[*] by running this script you accept all responsibility.
[*]
[*] Press enter to root your tablet...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Pushing log flooder to device...
583 KB/s (5382 bytes in 0.009s)
[*] Preparing to append to packages.list...
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attempting to move system package library directory...
[+] System package com.google.android.location has uid 10029
[+] Flooding log...
[*] If you received any errors in the previous step, abort the exploit
[*] and try again. Otherwise, press any key to continue.
Press any key to continue . . .
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attempting to insert fake local.prop entry...
[+] Flooding log...
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attemping persistence...
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Cleaning up...
failed on '/data/data/com.google.android.location/lib.bak' - Permission denied
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
ADB works and debugging is enabled.
Got it working. Next step is CWM and then a nice fresh cup of awesomeness. Thanks Dan. Expect a donation your way.
Judah001 said:
Is anyone able to make a YouTube video for people like me who can’t seem to figure it out? That would be totally appreciated not only by me but I’m sure the rest of our tablet S community. Thanks for root!
Click to expand...
Click to collapse
OKay
rjsmith2007 said:
I tried to use the exploit after a factory reset, and I can't get it to work.
Code:
F:\Desktop\Sony_Tablet_S_Root_Windows>run.bat
[*]
[*] Sony Tablet S root script (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that ADB
[*] is working properly, and that your tablet is connected via USB.
[*]
[*] WARNING: This exploit may result in wiping your /data partition,
[*] causing you to lose any applications and data on your tablet.
[*] There should be no risk of permanent damage to your device, but
[*] by running this script you accept all responsibility.
[*]
[*] Press enter to root your tablet...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Pushing log flooder to device...
583 KB/s (5382 bytes in 0.009s)
[*] Preparing to append to packages.list...
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attempting to move system package library directory...
[+] System package com.google.android.location has uid 10029
[+] Flooding log...
[*] If you received any errors in the previous step, abort the exploit
[*] and try again. Otherwise, press any key to continue.
Press any key to continue . . .
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attempting to insert fake local.prop entry...
[+] Flooding log...
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attemping persistence...
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Cleaning up...
failed on '/data/data/com.google.android.location/lib.bak' - Permission denied
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
ADB works and debugging is enabled.
Click to expand...
Click to collapse
Try running the .bat file again, it happened to me first time, but when I tried it second time it worked.
05081983 said:
Try running the .bat file again, it happened to me first time, but when I tried it second time it worked.
Click to expand...
Click to collapse
When I run the bat file the second time, I get an error related to the files that the exploit handles:
Code:
[+] System package com.google.android.location has uid 10029
[+] Flooding log...
failed on '/data/data/com.google.android.location/lib' - Permission denied
link failed File exists[*]
Code:
F:\Desktop\Sony_Tablet_S_Root_Windows>run.bat
[*]
[*] Sony Tablet S root script (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that ADB
[*] is working properly, and that your tablet is connected via USB.
[*]
[*] WARNING: This exploit may result in wiping your /data partition,
[*] causing you to lose any applications and data on your tablet.
[*] There should be no risk of permanent damage to your device, but
[*] by running this script you accept all responsibility.
[*]
[*] Press enter to root your tablet...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Pushing log flooder to device...
656 KB/s (5382 bytes in 0.008s)
[*] Preparing to append to packages.list...
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attempting to move system package library directory...
[+] System package com.google.android.location has uid 10029
[+] Flooding log...
failed on '/data/data/com.google.android.location/lib' - Permission denied
link failed File exists
[*] If you received any errors in the previous step, abort the exploit
[*] and try again. Otherwise, press any key to continue.
Press any key to continue . . .
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attempting to insert fake local.prop entry...
[+] Flooding log...
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attemping persistence...
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Cleaning up...
failed on '/data/data/com.google.android.location/lib.bak' - Permission denied
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
F:\Desktop\Sony_Tablet_S_Root_Windows>
I guess it is not so "easy" to get CWM on the tablet. As I know, CWM is part of kernel and this is signed on the Sony Tablet S ....
@Dan:
Is it right and do you see a opportunity to get CWM on Tablet S?
rjsmith2007 said:
When I run the bat file the second time, I get an error related to the files that the exploit handles:
Code:
[+] System package com.google.android.location has uid 10029
[+] Flooding log...
failed on '/data/data/com.google.android.location/lib' - Permission denied
link failed File exists[*]
Click to expand...
Click to collapse
I just uploaded a new version of the exploit that should fix this problem. Just unzip it, execute "run.bat", and let me know how it goes.
If anyone has been having any problems with the exploit, please try the new version here:
http://vulnfactory.org/public/Sony_Tablet_S_Root_Windows.zip
djrbliss said:
I just uploaded a new version of the exploit that should fix this problem. Just unzip it, execute "run.bat", and let me know how it goes.
If anyone has been having any problems with the exploit, please try the new version here:
http://vulnfactory.org/public/Sony_Tablet_S_Root_Windows.zip
Click to expand...
Click to collapse
Thanks. I'll try it out now!
Edit: I'm still getting the same end result. Should I wait for the device to boot fully to the launcher, when it asks me to press a button before it continues?
Hei guys,
I just wanted to root my xmp with doomlords method, but it failes. Here's what the prompt says:
---------------------------------------------------------------
Xperia 2011 ICS Easy Rooting toolkit (v1.0)
created by DooMLoRD
"andorid emulator" trick
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using "andorid emulator" trick
(2) install Busybox (1.18.4)
(3) install SU files (ICS specific)
(4) do some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Developer Options\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Security)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Drücken Sie eine beliebige Taste . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- symlinking tmp directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- enabling emulator hack
/system/bin/sh: cannot create /data/local.prop: Permission denied
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2554 KB/s (1075144 bytes in 0.411s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
85 KB/s (439 bytes in 0.005s)
--- Free space on /system : 81788 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/bin/sh: /system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
--- rebooting
ALL DONE!!!
Drücken Sie eine beliebige Taste . . .
[/QUOTE
What did I do wrong? Please help me
Thx
Michael
Click to expand...
Click to collapse
Michi_optimus_me said:
Hei guys,
I just wanted to root my xmp with doomlords method, but it failes. Here's what the prompt says:
---------------------------------------------------------------
Xperia 2011 ICS Easy Rooting toolkit (v1.0)
created by DooMLoRD
"andorid emulator" trick
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using "andorid emulator" trick
(2) install Busybox (1.18.4)
(3) install SU files (ICS specific)
(4) do some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Developer Options\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Security)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Drücken Sie eine beliebige Taste . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- symlinking tmp directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
--- Rebooting
---
...........
What did I do wrong? Please help me
Thx
Michael
Click to expand...
Click to collapse
Come on buddy, let get ur bootloader unlocked(if it's locked) and this Thread will get to to root and CWM.
===>>>> http://forum.xda-developers.com/showthread.php?t=1694027
sorry for error
Click to expand...
Click to collapse
I have no problems and no got bootloops rooting ics using puppeth method
Sent from my SK17i using XDA
Read better. This method is only for 4.0.3 4.1.A.0.562 version and not 4.0.4 4.1.B.0.531
Sent from my Xperia Live using xda premium
I know i donwgraded to gb and updated using flashtool with no data wipe
Thx to all
I use AiO tool on Tablet P Android 3.2.1
and this is error I'm getting. Any idea what's wrong?
Thanks Much!!!
>>>>>>>>>>>>
[*] Attemping persistence...
remount failed: Operation not permitted
failed to copy 'files\su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
failed to copy 'files\tempsu' to '/system/bin/tempsu': Read-only file system
Unable to chmod /system/bin/tempsu: No such file or directory
Unable to chmod /system/bin/tempsu: No such file or directory
failed to copy 'files\busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'files\Superuser.apk' to '/system/app/Superuser.apk': Read-only f
ile system
[*] Cleaning up...
<<<<<<<<<<<<<<<<<<<<<<
Driver seems to be OK:
>>>>>>>>>>>>>>>>>>>
C:\Users\shlasasha\Desktop\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
4507046411fb2d7 device
<<<<<<<<<<<<<<<<<<<<<
What this means?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[*]*************[*]
[*] ADB Shell [*]
[*]*************[*]
Type EXIT to get out of shell
$ devices
devices
devices: permission denied
$
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
what kernel version you got?
is it build10?
weaponXandroid said:
what kernel version you got?
is it build10?
Click to expand...
Click to collapse
2.6.36.3
[email protected] #1
Additional info:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[*] Attempting to move system package library directory...
[+] System package com.android.providers.media has uid 10035
[+] Flooding log...
run-as: Package 'com.pwn.me' is unknown
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Does it mean I'm missing something?
Thanks!
Tried this thread:
http://forum.xda-developers.com/showthread.php?t=1487020
got the same error
also run Run.bat from here manually line by line with the same effect.
another try of this thread:
http://forum.xda-developers.com/showthread.php?t=1887447
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
C:\PhonesAndTablets\SonyP\Xperia_Tablet_Root>adb restore settings.ab
adb: unable to connect for backup
<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Google says it required ICS. is it really? I'm 3.2.1 and I didn't get Restore button on the device.
HELP:silly:
Got it !!!
There is another setting under "Applications->Development" "Allow mock locations"
It is not mentioned in any guides.
After I set that one ALLinONE worked.
Thanks everyone!!!
[#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.
Following these directions: http://wiki.cyanogenmod.org/w/Install_CM_for_xt926
Unlocking the bootloader on the Droid RAZR HD/RAZR HD MAXX (CDMA)
This unlock requires your device to be rooted. Do not proceed without a working su.
Download motopocalypse (credit to djrbliss).
Extract all files in the zip.
Windows only: install the latest Motorola USB drivers.
Enable USB debugging on the device and connect device to PC.
Windows: run the run.bat file.
Linux/OSX: ./run.sh
Your bootloader should now be unlocked, proceed to next section.
See attached for proof of root.
[email protected]:~$ cd /home/dlw/moto*
[email protected]:~/motopocalypse$ ls
adb.exe AdbWinUsbApi.dll recovery-clockwork-6.0.4.4-xt926.img unlock
adb.linux fastboot.exe run.bat
adb.osx fastboot.linux run.sh
AdbWinApi.dll fastboot.osx run.sh~
[email protected]:~/motopocalypse$ ./run.sh
[*]
[*] Motopocalypse: Motorola bootloader unlock script (Linux/OS X version)
[*] v1.0
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Supports the Motorola Razr HD, Razr M, Razr Maxx HD, and Atrix HD.
[*]
[*] Before continuing, ensure that your device has been rooted and you have
[*] a working su installation, that USB debugging is enabled,
[*] and that your phone is connected via USB.
[*]
[*] WARNING: This will permanently void the warranty on your device. This
[*] is not reversible. I am not responsible for any damage to your phone
[*] as a result using this tool.
[*]
[*] Press enter to unlock your bootloader...
[*]
chmod: cannot access ‘.adb.linux’: No such file or directory
./run.sh: line 64: .adb.linux: command not found
[*] Waiting for device...
./run.sh: line 67: .adb.linux: command not found
[*] Device found.
[*] Pushing unlock tool...
./run.sh: line 72: .adb.linux: command not found
./run.sh: line 73: .adb.linux: command not found
[*] Unlocking phone...
./run.sh: line 76: .adb.linux: command not found
[*] Cleaning up...
./run.sh: line 79: .adb.linux: command not found
[*] Unlocking complete. Rebooting into bootloader mode.
./run.sh: line 82: .adb.linux: command not found
[*] Press enter once the phone has rebooted into bootloader mode.
[*] Displaying bootloader variables:
./run.sh: line 88: ./fastboot.linux: No such file or directory
[*] Press enter to reboot and exit.
./run.sh: line 93: ./fastboot.linux: No such file or directory
./run.sh: line 94: .adb.linux: command not found
[email protected]:~/motopocalypse$
Why the above problem? adb.linux is in the same folder as run.sh.
TIA for any help.
dlw