Related
This is a super simple method taken from Arcadia 310 on another thread.
This is assuming you have The Android SDK already installed and updated.
Download these files XoomRoot.zip HERE
and FASTBOOT for MAC - HERE
Unzip both archives into your ~/sdk/platform-tools folder.
I AM NOT RESPONSIBLE FOR YOU SCREWING UP YOUR DEVICE, THIS IS VOIDING YOUR WARRANTY ANYWAYS. HIT ME UP ON TWITTER OR HERE IF YOU NEED HELP OR HAVE QUESTION. ON TO DIRECTIONS.
Follow these steps: (After you have unzipped into your folder)
1. Follow the pre requisites above.
2. Open a terminal (located in the utilities folder)
3. Navigate to your sdk/platform-tools folder
Example: "cd /home/b16/Desktop/sdk/platform-tools" (no quotes)
4. Type "./adb devices" and make sure your Xoom shows up on the list.
This command will show you if your device is connected to the Android Debug Bridge.
5. Now type in "./adb reboot bootloader" (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
This will reboot your device into bootloader mode accepting fastboot commands.
6. I had to type "chmod 755 fastboot" first to get it to execute.
This will change the permissions of the FASTBOOT BINARY so it can execute.
7. Now type in "./fastboot oem unlock" and choose to unlock it. (wait for reboot)
This will make your device "Hackable" and will VOID your warranty, you can re-lock it later if you like using another guide on this forum. Located HERE.
8. Once it has rebooted type "adb reboot bootloader" and hit enter.
Now you are going back into bootloader mode to finish the job.
9. Once in bootloader mode type "./fastboot flash boot rootboot.img"
This is going to flash the boot image needed to have root working properly within the system.
10. Type "./fastboot reboot" (wait for reboot)
command wil now boot you back into Android.
11. Type "./adb remount"
We are now mounting the system partition in order to push the Super User binary.
12. Type "./adb push su /system/bin"
Does what it says. Pushes binary to system folder.
13. Type "./adb shell" You should now see a "#" sign.
This will put you into a root shell to change the permissions of files in the next step.
14. Type "chmod 4755 /system/bin/su"
You just changed the permissions of the super user binary to run properly.
15. Type "exit".
You will now be back in your home terminal ready to push the Super User Apk.
16. Type "./adb push Superuser.apk /system/app"
You should now have root acces! Enjoy!
Thanks for posting this. Another thing I did, because I use ADB quite frequently, was add the SDK tools to my path. For those that need help, it looks something like this:
Open Terminal and type echo 'export PATH=~/Downloads/android-sdk-mac_x86/tools:$PATH' >> ~/.profile
This only works if your SDK folder is in your Downloads folder inside your Home folder.
The next time you open a Terminal window, you can simply type adb remount or whatever you need without having to add the ./
Another bonus is this makes it much easier to keep kernels, ROMs, and modules out of your SDK tools folder, where they do not belong.
First off thanks for doing this... I figured out my n1 and I can do this too... I'm stuck at the chmod 775 line... I enter that command and its like I didn't enter it... after I proceed to fast boot OEM unlock it tells me that it can't be executed .. what am I doing wrong... God I hate being noobed out... I'm so close!!!
Sent from my Nexus One using XDA App
EDIT: got past that with the help of using fastboot-mac from htc's website... but now I'm stuck on getting the rootboot.img over
Morgan-Brants-Mac-minilatform-tools Chongo$ ./fastboot-mac flash boot rootboot.img
sending 'boot' (2902 KB)... OKAY
writing 'boot'... FAILED (remote: (0000000f))
Morgan-Brants-Mac-minilatform-tools Chongo$
EDIT2: Well it was due to my xoom being almost dead (not enough juice to flash)
on the other hand this was a refresher course and I now understand ADB a whole lot more... thank you for this educational piece I am now a tiger blood enfused SUPER USER
I am glad I could help, I have this tutorial on my website along with many other devices, http://rootzwiki.com if there is any other devices you would like to see
b16a2smith said:
I am glad I could help, I have this tutorial on my website along with many other devices, http://rootzwiki.com if there is any other devices you would like to see
Click to expand...
Click to collapse
Thanks.. ill let you know when I get a new phone.. should be soon
Sent from my Nexus One using XDA App
thanks for this. Cant wait to get mine on the 27th
wheeeler said:
Thanks for posting this. Another thing I did, because I use ADB quite frequently, was add the SDK tools to my path. For those that need help, it looks something like this:
Open Terminal and type echo 'export PATH=~/Downloads/android-sdk-mac_x86/tools:$PATH' >> ~/.profile
This only works if your SDK folder is in your Downloads folder inside your Home folder.
The next time you open a Terminal window, you can simply type adb remount or whatever you need without having to add the ./
Another bonus is this makes it much easier to keep kernels, ROMs, and modules out of your SDK tools folder, where they do not belong.
Click to expand...
Click to collapse
Well the default shell in a mac is bash so wouldn't be:
Code:
echo "export PATH=$HOME/bin/android-sdk-mac_x86/tools:$HOME/bin/android-sdk-mac_x86/platform-tools:$PATH" > .bash_profile
This is a video walkthru of rooting that happens to be on a Mac but the process is the same for Windows:
http://www.youtube.com/watch?v=4YkIw0y_Os4
im not sure if it is just me or not, but i get stuck at step 5 for some reason?
i type ./adb reboot bootloader it shuts down then turns on and i get stuck at "starting fastboot protocal support" it sits forever then i have to hold volume up and power to reboot and its fine, but cant ever get past that.
it no longer shows as attached device at that point either
Magenta you say.
chevyman46933 said:
im not sure if it is just me or not, but i get stuck at step 5 for some reason?
i type ./adb reboot bootloader it shuts down then turns on and i get stuck at "starting fastboot protocal support" it sits forever then i have to hold volume up and power to reboot and its fine, but cant ever get past that.
it no longer shows as attached device at that point either
Click to expand...
Click to collapse
can anyone help me?
OK, thanks for the initial post and outstanding directions. I've updated what you listed based on what I have seen on my mac. I've just been through this process now and everything is working great. I hope this helps.
1. Follow the pre requisites above.
* I also had to download the fastboot-mac file from the HTC site- http://developer.htc.com/adp.html
2. Open a terminal (located in the utilities folder)
3. Navigate to your sdk/platform-tools folder
Example: "cd /home/b16/Desktop/sdk/platform-tools" (no quotes)
4. Type "./adb devices" and make sure your Xoom shows up on the list.
This command will show you if your device is connected to the Android Debug Bridge.
goonmac-2: platform-tools goon$ ./adb devices
List of devices attached
028040c743e111d7 device
5. Now type in "./adb reboot bootloader" (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
This will reboot your device into bootloader mode accepting fastboot commands.
FYI - your xoom will just say "Starting..." but it is ready to accept the next step.
6. I had to type "chmod 755 fastboot" first to get it to execute.
This will change the permissions of the FASTBOOT BINARY so it can execute.
7. Now type in "./fastboot oem unlock" and choose to unlock it. (wait for reboot)
This will make your device "Hackable" and will VOID your warranty, you can re-lock it later if you like using another guide on this forum. Located HERE.
goonmac-2: platform-tools goon$ ./fastboot-mac oem unlock
... INFO To continue, follow instructions on the device's display...
OKAY
8. Once it has rebooted type "adb reboot bootloader" and hit enter.
Now you are going back into bootloader mode to finish the job.
*after the reboot, initially, I got this error:
goonmac-2: platform-tools goon$ ./adb reboot bootloader
error: device not found
when the reboot completes, you will come to the original setup screen. it is worth noting that you need to select the language and follow the on screen directions. Re-enter your account information etc. When you get to the desktop, your device will then be re-seen by your mac.
9. Once in bootloader mode type "./fastboot flash boot rootboot.img"
This is going to flash the boot image needed to have root working properly within the system.
* Again, need to use the fastboot-mac:
goonmac-2: platform-tools goon$ ./fastboot-mac flash boot rootboot.img
sending 'boot' (2902 KB)... OKAY
writing 'boot'... OKAY
10. Type "./fastboot reboot" (wait for reboot)
command wil now boot you back into Android.
* Again, need to use the fastboot-mac:
goonmac-2: platform-tools goon$ ./fastboot-mac reboot
rebooting...
11. Type "./adb remount"
We are now mounting the system partition in order to push the Super User binary.
no issues
goonmac-2: platform-tools goon$ ./adb remount
remount succeeded
12. Type "./adb push su /system/bin"
Does what it says. Pushes binary to system folder.
no issue
goonmac-2: platform-tools goon$ ./adb push su /system/bin
701 KB/s (26336 bytes in 0.036s)
13. Type "./adb shell" You should now see a "#" sign.
This will put you into a root shell to change the permissions of files in the next step.
no issue
goonmac-2: platform-tools goon$ ./adb shell
14. Type "chmod 4755 /system/bin/su"
You just changed the permissions of the super user binary to run properly.
no issue
# chmod 4755 /system/bin/su
15. Type "exit".
You will now be back in your home terminal ready to push the Super User Apk.
16. Type "./adb push Superuser.apk /system/app"
no issue
goonmac-2: platform-tools goon$ ./adb push Superuser.apk /system/app
1137 KB/s (196521 bytes in 0.168s)
still stuck at same step, after ./adb reboot fastboot i cant go any farther, the xoom just isnt connected to recieve and additional commands, heres a copy n paste from my terminal...
Mac-Users-Mac-mini:tools Home$ pwd
/Users/Home/desktop/sdk/platform-tools
Mac-Users-Mac-minilatform-tools Home$ ./adb devices
List of devices attached
161c10c94180d557 device
Mac-Users-Mac-minilatform-tools Home$ ./adb reboot bootloader
Mac-Users-Mac-minilatform-tools Home$ chmod 755 fastboot
Mac-Users-Mac-minilatform-tools Home$ ./fastboot oem unlock
-bash: ./fastboot: cannot execute binary file
Mac-Users-Mac-minilatform-tools Home$ ./adb devices
List of devices attached
Mac-Users-Mac-minilatform-tools Home$
any help/suggestions?
Are you using the Mac fastboot binary? I'm not by my computer right now, but I believe the Mac version is called fastboot-mac by default. Download it, make sure it's executable (chmod 755 fastboot-mac), then try fastboot-mac oem unlock. After you run adb reboot bootloader, you will lose your ADB connection, and your Xoom won't display anything but the boot logo and something about starting fastboot. This is your cue to unlock. Hope this helps.
Sent from my Xoom using XDA Premium App
wheeeler said:
Are you using the Mac fastboot binary? I'm not by my computer right now, but I believe the Mac version is called fastboot-mac by default. Download it, make sure it's executable (chmod 755 fastboot-mac), then try fastboot-mac oem unlock. After you run adb reboot bootloader, you will lose your ADB connection, and your Xoom won't display anything but the boot logo and something about starting fastboot. This is your cue to unlock. Hope this helps.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
that was exactly it, i was using the fastboot from another post, got the fastboot-mac from the website adn it works perfect!! thanks!!!
xoom unlocked, finally
thats why I amended the steps
1. Follow the pre requisites above.
* I also had to download the fastboot-mac file from the HTC site- http://developer.htc.com/adp.html
goon55 said:
thats why I amended the steps
1. Follow the pre requisites above.
* I also had to download the fastboot-mac file from the HTC site- http://developer.htc.com/adp.html
Click to expand...
Click to collapse
For some respason I didnt realize the difference between the two fastboots until he mentioned that and thankfully your ad was right above with the link to htc thanks to you guys im now have rooted and unlocked and overclocked my xoom and its incredible now! Thanks for the patience with me
I did a video that was done on my MAC in the MAC OS. If anyone wants a more visual way to see how this is performed. I follow all these steps exactly. I show how I set my environment PATH, and this actually is what tripped me up, because my user profile wasn't looking at the PATHs I originally setup, but all that is required is entering
echo 'export PATH=xyz:$PATH' >> ~/.bash_profile (this whole line )
Where 'xyz' is your path to the android-sdk/platform-tools/ from the root of your Hard Drive, for most Macs it should be ' /Users/[Ur User Name]/android-sdk/platform-tools '
http://www.youtube.com/watch?v=26EhGGOGUus
Hope this helps
I also have a WiFi Xoom Video Tutorial available available as well. Check it out.
http://www.youtube.com/watch?v=zC6J-hV6SM4
I try to go over common hiccups that I have seen some users have come across as well in the video.
I'm getting the following error:
./fastboot-mac flash boot rootboot.img
sending 'boot' (2902 KB)... ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (No such file or directory))
fastboot-mac is chmod 755, rootboot.img is there, alongside it, I'm in as root and it's still failing for me.
Edit: Nevermind. Right after pulling the reboot before the rootboot.img - or boot.img for wifi users - immediately go into the aforesaid command and it should work just fine.
Took me a couple of times.
Can you unroot on mac?
hi everybody
well i have a problem with the recovery of mt3gs the message is this when i tried to put the option Apply sdcard:update.zip
E:Can't open /cache/recovery/command
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
installation aborted
can you help me? please!
that means the stock recovery is rejecting the update.zip. Take the recovery image that I'm about to give you, then place it in the same directory as your fastboot. After this, boot into fastboot by either holding volume down + power or the back button + power, then press the power button again. Then go to your computer, and on the terminal or command prompt, type cd [the directory where fastboot is] and type fastboot flash recovery recovery.img! If it successfully flashes the recovery(which it should) then your recovery will be Clockworkmod.
Hitorijanae said:
that means the stock recovery is rejecting the update.zip. Take the recovery image that I'm about to give you, then place it in the same directory as your fastboot. After this, boot into fastboot by either holding volume down + power or the back button + power, then press the power button again. Then go to your computer, and on the terminal or command prompt, type cd [the directory where fastboot is] and type fastboot flash recovery recovery.img! If it successfully flashes the recovery(which it should) then your recovery will be Clockworkmod.
Click to expand...
Click to collapse
i don't know how can i use de adb?
i'm using the terminal and when i put
flash_image recovery /sdcard/recovery.img
the terminal said this:
mtd: read all-zero block at 0x0000000; skipping
error reading /sdcard/recovery.img
Have you installed the android sdk?
hey thanks guys for help me.
i was solved the problem, i install the spring file and the recovery appeared
Hitorijanae said:
that means the stock recovery is rejecting the update.zip. Take the recovery image that I'm about to give you, then place it in the same directory as your fastboot. After this, boot into fastboot by either holding volume down + power or the back button + power, then press the power button again. Then go to your computer, and on the terminal or command prompt, type cd [the directory where fastboot is] and type fastboot flash recovery recovery.img! If it successfully flashes the recovery(which it should) then your recovery will be Clockworkmod.
Click to expand...
Click to collapse
whats the version of this recovery img??
Help with my recovery
Please help me, I was trying to upgrade my mt3gs to ics so I flash a recovery on it, ever since then I can boot my phone into recovery mode. Please how can I solve this problem?.
Hi this might be a noobish question but i cant find the answer anywhare:
so here's the problem i was trying to fix a badly installed rom, so i wiped the phones storage I then tried to kick myself when i realized that i had just deleted my backup and all the data on the phones internal storage, so now i can only get onto fastboot and clockworkmod recovery 5.8.3.1.
So is there a way to flash a rom in fastboot usb, or mount the phones internal storage so i can copy in a rom zip?
I would be grateful for any help
There is an option in cwm to mount storage you can try that not sure if they work tho.
Sent from my HTC One X using XDA Premium HD app
malcovitch said:
There is an option in cwm to mount storage you can try that not sure if they work tho.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
It will not work.
What you can do other than flashing a RUU is:
Boot to fastboot
fastboot boot CWM_recovery_full name.img
Once it boot to recovery
adb shell
adb push rom_name.zip /sdcard
It will take some times to finish as the rom_name.zip is big.
Once complete, you can flash the rom_name.zip as usual
To make it easier, change the rom_name.zip to update.zip, so you can
adb push update.zip /sdcard
Thank you I have done as you said but i must be doing something wrong because i get this error:
C:\Documents and Settings\me\Desktop\Android>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # adb push update.zip /sdcard
adb push update.zip /sdcard
/sbin/sh: adb: not found
~ #
(The update.zip is Android_Revolution_HD-One_X_5.1.0.zip)
do you think it could be a problem with my adb.exe or something on the phone?
did you do the "fastboot boot CWM_recovery_full name.img"
going to recovery via hboot will not work.
you need to fastboot boot recovery
and it is adb devices , not adb shell... sorry
see this : http://forum.xda-developers.com/showpost.php?p=25774374&postcount=24
yes that's how i got to cwm as below
C:\Documents and Settings\me\Desktop\Android>fastboot boot recovery-clockwork
-touch-5.8.3.1-endeavoru.img
downloading 'boot.img'...
OKAY [ 0.771s]
booting...
OKAY [ 0.010s]
finished. total time: 0.781s
C:\Documents and Settings\me\Desktop\Android>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # adb push update.zip /sdcard
adb push update.zip /sdcard
/sbin/sh: adb: not found
~ #
River825 said:
yes that's how i got to cwm as below
C:\Documents and Settings\me\Desktop\Android>fastboot boot recovery-clockwork
-touch-5.8.3.1-endeavoru.img
downloading 'boot.img'...
OKAY [ 0.771s]
booting...
OKAY [ 0.010s]
finished. total time: 0.781s
C:\Documents and Settings\me\Desktop\Android>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # adb push update.zip /sdcard
adb push update.zip /sdcard
/sbin/sh: adb: not found
~ #
Click to expand...
Click to collapse
my bad
C:\Documents and Settings\me\Desktop\Android>adb shell
change to
C:\Documents and Settings\me\Desktop\Android>adb devices
Then adb push rom.zip /sdcard
ok i think that worked but when trying to find the zip in cwm i just get "no files were found", but in the command prompt it looks like it was copied to the sd card:
C:\Documents and Settings\me\Desktop\Android>adb devices
List of devices attached
HT23WW118450 recovery
C:\Documents and Settings\me\Desktop\Android>adb push update.zip /sdcard
1586 KB/s (577044654 bytes in 355.290s)
That's wierd.
You mean that when you click "choose zip from sdcard" you have nothing in sdcard ?
yes clockworkmod says that the sd is empty.
I'm going to try again with a smaller file and maybe try and access the sd with a different recovery
River825 said:
yes clockworkmod says that the sd is empty.
I'm going to try again with a smaller file and maybe try and access the sd with a different recovery
Click to expand...
Click to collapse
No. It won't work as sdcard need to be manually mounted first.... that's why I said something about adb shell earlier.
I'll do the testing now:
my step will be:
fastboot boot xx-recovery.img
adb devices
adb shell
mount sdcard
open another cmd prompt
adb push xxx.zip /sdcard
will let you know in a short while
Just tested: this should be the correct way... I can see my xxx.zip when I choose : choose zip from sdcard
*you need to mount the sdcard first before adb push
thank you it worked fine I downloaded the zip to the sd and flashed the rom in cwm, but it didn't work and now i cant boot into recovery it just shows the revery screen for 1/2 a second, and reboots into the bootloader i tried flashing different recovery images but they didn't work.
Is there some way to wipe the phone recovery?
River825 said:
thank you it worked fine I downloaded the zip to the sd and flashed the rom in cwm, but it didn't work and now i cant boot into recovery it just shows the revery screen for 1/2 a second, and reboots into the bootloader i tried flashing different recovery images but they didn't work.
Is there some way to wipe the phone recovery?
Click to expand...
Click to collapse
Do:
fastboot erase cache
fastboot reboot-bootloader
Then press power once to go to hboot then select recovery. It should work.
Thank you
Thank you so much for all your advice i've just successfully flashed a rom and got my phone working again i was starting to fear for my phone.
Thanks again for all your help
ckpv5, when I try to follow your steps, I get "error: device not found" when doing adb shell in the command prompt? How do I fix that?
(My problem is that I formatted everything like an idiot in my phone and the internal sdcard seems to be unmounted or something like that)
Sam.Lambert said:
ckpv5, when I try to follow your steps, I get "error: device not found" when doing adb shell in the command prompt? How do I fix that?
(My problem is that I formatted everything like an idiot in my phone and the internal sdcard seems to be unmounted or something like that)
Click to expand...
Click to collapse
If you're on stock ROM, you don't have to do all the step, just simply flash RUU.
ckpv5 said:
If you're on stock ROM, you don't have to do all the step, just simply flash RUU.
Click to expand...
Click to collapse
I don't have the executable RUU for the Rogers handset, I only have a zip containing a bunch of img files and the executable RUU for the AT&T version (which didn't work, gave me ERROR [131]: Customer ID error or something like that).
Which the zipped RUU for the Rogers handset, I tried flashing the recovery_signed.img and boot_signed.img, relocking the bootloader and then flashing the system.img file but it would give me an error saying data length too large or something like that.
I really don't know what to do anymore
Sam.Lambert said:
I don't have the executable RUU for the Rogers handset, I only have a zip containing a bunch of img files and the executable RUU for the AT&T version (which didn't work, gave me ERROR [131]: Customer ID error or something like that).
Which the zipped RUU for the Rogers handset, I tried flashing the recovery_signed.img and boot_signed.img, relocking the bootloader and then flashing the system.img file but it would give me an error saying data length too large or something like that.
I really don't know what to do anymore
Click to expand...
Click to collapse
Which custom recovery is working for for your set ? Is the one from One X dev section works for you ? If it is not, I'm afraid unable to help you.
Which custom ROM that you use before the brick ?
ckpv5 said:
Which custom recovery is working for for your set ? Is the one from One X dev section works for you ? If it is not, I'm afraid unable to help you.
Which custom ROM that you use before the brick ?
Click to expand...
Click to collapse
Pretty much the only one available for the Evita One X (this one doesn't work if that's the one you are talking about http://forum.xda-developers.com/showthread.php?t=1594819):
http://www.modaco.com/topic/354009-interim-clockworkmod-recovery-for-the-s4-based-one-x/
Also, I wasn't able to succesfully flash a custom ROM, when I tried to it just kept giving me random status errors in CWM, I'm starting to think the problem is the hardware and not the software since every solution I try is giving me errors related to unable to install/transfer/blahblah
Sam.Lambert said:
Pretty much the only one available for the Evita One X (this one doesn't work if that's the one you are talking about http://forum.xda-developers.com/showthread.php?t=1594819):
http://www.modaco.com/topic/354009-interim-clockworkmod-recovery-for-the-s4-based-one-x/
Also, I wasn't able to succesfully flash a custom ROM, when I tried to it just kept giving me random status errors in CWM, I'm starting to think the problem is the hardware and not the software since every solution I try is giving me errors related to unable to install/transfer/blahblah
Click to expand...
Click to collapse
So it seems that yours is not on tegra but S4. You need to find a solution for your problem here : http://forum.xda-developers.com/forumdisplay.php?f=1538
I am trying to install CWM on my bootloader locked Xperia S.
It's all went smoothly; downgraded to gingerbread, run the rooting process, currently on a confirmed rooted ICS. Ran RecoverX and for all intentions it installs correctly with no errors. I restart my phone and tap the Sony logo numerous times... and I've tried a countless amount of times now but it just continues on loading stock ICS. It's really starting to get on my nerves now. Does anyone have any idea why it's happening? or is there any adb commands to check if CWM is installed?
RecoverX says accept any SuperUser prompts on the screen, but none appear.
RecoverX log:
Starting adb...
Wait for the device...
Check if the device is correctly rooted...
Check if busybox is installed...
Push files...
Unzip files...
Chmod files to 755...
Run installation script...
Clear temp folder...
Installation complete
Click to expand...
Click to collapse
I've also tried the older adb method via the install.bat but that says this:
Step1 : Waiting for Device.
=============================================
OK
=============================================
Step2 : Sending some files.
=============================================
mkdir failed for /data/local/tmp/cwm, Not a directory
failed to copy 'chargemon' to '/data/local/tmp/cwm': Not a directory
failed to copy 'charger' to '/data/local/tmp/cwm': Not a directory
failed to copy 'recovery.tar' to '/data/local/tmp/cwm': Not a directory
failed to copy 'sh' to '/data/local/tmp/cwm': Not a directory
failed to copy 'step3.sh' to '/data/local/tmp/cwm': Not a directory
=============================================
Step3 : Setting up files system partition.
=============================================
Unable to chmod /data/local/tmp/cwm/sh: Not a directory
Unable to chmod /data/local/tmp/cwm/step3.sh: Not a directory
sh: /data/local/tmp/cwm/step3.sh: not found
rm failed for /data/local/tmp/cwm, Not a directory
Finished!
Click to expand...
Click to collapse
Even though I clearly have access to my phone via adb. Because it's been rooted... Grr!
Nobody have any idea? Spent around 12 hours trying to sort it out yesterday so I'm completely out of things to try
For search purposes I ended up fixing it by updating the flashtool drivers for the phone (ticked every Xperia S checkbox). Well, it was either that or perhaps updating BusyBox, which is highly unlikely as I tried pretty much every version of it yesterday.
I am not responsible for whatever may happen to you or your device when using this, Run this at your own risk!!
Requires unlocked bootloader!
Based on SuperSU - v4.46 (the binary updates from within the app later on)
I put together root installer script that comes with SU-binary/App with a insecure boot.img, everything is done over adb shell since we don't have a recovery right now but i will be working on it and already booted CWM
For current firmware:
LMY47D - root-boot
For past firmware:
LRX21V - root-boot
For past firmware:
LRX21M - root-boot
crappy video but simple demonstration :good:How to install:
Download the zip depending on your Nexus Player's firmware than extract & run root-boot.bat (Other operating system support coming soon for the installer script) Made on windows 7
Follow and read the on screen instruction carefully
Click to expand...
Click to collapse
SU app and binarys gets installed to /system/* directory's, The insecure boot.img gets installed to be able to access root adb shell and install those binarys
The root-boot boot.img is temporarily booted once during this process on the first boot of installation, it does not flash the boot.img
The previous boot.img before the installation is restored after SU is installed
Click to expand...
Click to collapse
Thanks @Chainfire for Superuser
My Donation Box
Troubleshooting:
Check to make sure your device gets picked up in adb before running the script - - - ADB Drivers
This tool uses an unlocked bootloader and i have not unlocked mine yet, does unlocking the bootloader wipe the device? - - - Yes unlocking the bootloader will wipe the device
After fastboot flashed the boot.img than rebooted to the home screen i continued the the script like the installation steps said but it returned "device not found" - - - As long as it shows transferring files a few seconds after than its fine, adb restarts at that moment which will than return "device not found" than it reconnects and transfers. if fastboot flashed than rebooted fine than adb shouldn't have an issue
Help! Something went wrong and im bootlooping but i dont want to loose all my saved data - - - Everything is fine, Download the factory zip from here for your android version than extract the zip and retrieve the system.img and copy it into a folder that contains adb/fastboot and boot your device into fastboot mode and do "fastboot flash system system.img" doing it this way wont wipe your "/data" partition leaving everything intact but will restore the system back to its defaults
(If you were to run the factory zip as an update than it would format everything)
I installed SU with this method but cant use adb commands on my device - - - Go into "Settings>About" and click on "Build" 7 times very fast and it will enable "Developer options" in the settings menu, Go back to the settings menu and open developer options (You may need to reboot if it doesnt show up immediately) and enable the "USB debugging" option
Ill be updating this as new version of lollipop get released
support for both firmwares are up, any issues let me know i tested them both though and everything looked okay
Reuploading, had a minor issue
Edit: LRX21M link back up, let me know if there's any issues
Whoa...
Let the games begin....
ftarules said:
Whoa...
Let the games begin....
Click to expand...
Click to collapse
yeup, after recovery i have a few system modification ideas for the settings apk i was considering
i do have other devices to worry about though so it may take some time
bunchies said:
I put together root installer script that comes with SU-binary/App with a insecure boot.img, everything is done over adb shell since we don't have a recovery right now but i will be working on it and already booted CWM
For current firmware:
LRX21V - root-boot
Click to expand...
Click to collapse
Working well, Thank you, after semi-manually adapting for working from Linux Mint.
I don't have permission to do "adb logcat" or "adb shell logcat" anymore though, unless I restart adbd as root.
mikereidis said:
Working well, Thank you, after semi-manually adapting for working from Linux Mint.
I don't have permission to do "adb logcat" or "adb shell logcat" anymore though, unless I restart adbd as root.
Click to expand...
Click to collapse
Use adb shell
than type su to use root adb shell
Since running the script everything seems all good except for using voice search. Anybody else having issues where voice search just closes?
Update: Erased and manually flashed the V firmware as I was on M and now it appears to be working correctly, not sure if this is going to be a problem with people stuck on M for now but you may want to think of upgrading your fimware.
Getting ADB device not found.. Anywhere I can download drivers from? I have the latest android-sdk
xReaper7x said:
Getting ADB device not found.. Anywhere I can download drivers from? I have the latest android-sdk
Click to expand...
Click to collapse
http://developer.android.com/sdk/win-usb.html
at what point, adb will restart about half way through and it shows it cant connect to device but it really is
but if your in fastboot and it cant connect to the device than thats an issue
i should note this in the OP
Subscribed for later. Awaiting someone else to port a recovery for this, I am lazy.
Snuzzo said:
Subscribed for later. Awaiting someone else to port a recovery for this, I am lazy.
Click to expand...
Click to collapse
lol Snuzzo :good: recovery coming soon
Links are down. Does anyone have a mirror of 21V?
prsterero said:
Links are down. Does anyone have a mirror of 21V?
Click to expand...
Click to collapse
Links are up, hosted on android file host
Can mirror in a bit if needed
bunchies said:
Links are up, hosted on android file host
Can mirror in a bit if needed
Click to expand...
Click to collapse
Looks like it's working now. Before I was getting that the file couldn't be found. Thanks I appreciate you releasing this I just got it unlocked so time to root and have some fun expanding the storage to 128gb
Alright so I just got around to running the script, and none of the commands work after booting back up. There's a failure for every rmdir and mkdir command that's used, so the device doesn't get rooted. I tried doing a adb remount, but the device isn't allowing that.
________________________________________________________
root-boot: By Bunchies @xda
________________________________________________________
________________________________________________________
Power off/unplug the device, hold the power button while
plugging in the device until you see the google logo and
than let go to enter fastboot mode
________________________________________________________
________________________________________________________
Plugin the device to a PC using a usb cable
________________________________________________________
Press any key to continue . . .
waiting for ADB
target reported max download size of 536870912 bytes
sending 'boot' (5424 KB)...
OKAY [ 1.357s]
writing 'boot'...
OKAY [ 1.515s]
finished. total time: 2.876s
rebooting...
finished. total time: 0.602s
When boot completes
and you see the launcher
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
rm: /system/bin/install-recovery.sh: Read-only file system
mkdir failed for /system/app/SuperSU, Read-only file system
mkdir failed for /system/bin/.ext, Read-only file system
failed to copy 'SuperSU/SuperSU.apk' to '/system/app/SuperSU/': Is a directory
failed to copy 'x86/su' to '/system/xbin/su': Read-only file system
failed to copy 'x86/supolicy' to '/system/xbin/supolicy': Read-only file system
failed to copy 'x86/libsupol.so' to '/system/lib/libsupol.so': Read-only file sy
stem
failed to copy 'x86/99SuperSUDaemon' to '/system/etc/init.d/99SuperSUDaemon': Re
ad-only file system
failed to copy 'x86/install-recovery.sh' to '/system/etc/install-recovery.sh': R
ead-only file system
cp: system/xbin/su: No such file or directory
cp: system/xbin/su: No such file or directory
cp: system/xbin/su: No such file or directory
cp: /system/xbin/sugote-mksh: Read-only file system
ln: /system/bin/su: Read-only file system
ln: /system/bin/install-recovery.sh: File exists
rm: /system/bin/app_process: Read-only file system
ln: /system/bin/app_process: File exists
mv: rename /system/bin/app_process32 to /system/bin/app_process32_original: Read
-only file system
ln: /system/bin/app_process32: File exists
cp: /system/bin/app_process32_original: No such file or directory
Unable to chmod /system/app/SuperSU: No such file or directory
Unable to chmod /system/app/SuperSU/SuperSU.apk: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/lib/libsupol.so: No such file or directory
Unable to chmod /system/bin/.ext: No such file or directory
Unable to chmod /system/bin/.ext/.su: No such file or directory
Unable to chmod /system/etc/init.d/99SuperSUDaemon: No such file or directory
Unable to chmod /system/xbin/daemonsu: No such file or directory
Unable to chmod /system/xbin/sugote: No such file or directory
Unable to chmod /system/xbin/sugote-mksh: No such file or directory
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chmod /system/xbin/supolicy: No such file or directory
Unable to chmod /system/bin/app_process32_original: No such file or directory
Unable to chmod /system/bin/app_process_init: No such file or directory
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: No such
file or directory
chcon: Could not label /system/bin/.ext/.su with ubject_r:system_file:s0: No
such file or directory
chcon: Could not label /system/lib/libsupol.so with ubject_r:system_file:s0:
No such file or directory
chcon: Could not label /system/etc/init.d/99SuperSUDaemon with ubject_r:syste
m_file:s0: No such file or directory
chcon: Could not label /system/bin/sh with ubject_r:system_file:s0: Read-onl
y file system
chcon: Could not label /system/xbin/sugote with ubject_r:zygote_exec:s0: No
such file or directory
chcon: Could not label /system/xbin/supolicy with ubject_r:system_file:s0: N
o such file or directory
chcon: Could not label /system/xbin/sugote-mksh with ubject_r:system_file:s0:
No such file or directory
chcon: Could not label /system/bin/app_process32_original with ubject_r:zygot
e_exec:s0: No such file or directory
chcon: Could not label /system/bin/app_process_init with ubject_r:system_file
:s0: No such file or directory
Finished, you can now exit the installer
Press any key to continue . . .
Edit: Fixed it! I had to manually do "adb root" then "adb remount" and remount succeeded that time and I was able to run the rest of the script and saw all the file transfers.
prsterero said:
Alright so I just got around to running the script, and none of the commands work after booting back up. There's a failure for every rmdir and mkdir command that's used, so the device doesn't get rooted. I tried doing a adb remount, but the device isn't allowing that.
Edit: Fixed it! I had to manually do "adb root" then "adb remount" and remount succeeded that time and I was able to run the rest of the script and saw all the file transfers.
Click to expand...
Click to collapse
Glad to hear that!
bunchies said:
Glad to hear that!
Click to expand...
Click to collapse
The first time around I got into the bootloop so I had to start over. Second time and it worked now it seems that I can't get apps to install through the adb install command. I'm mainly trying to get es file explorer and stick mount so I can use an external flash drive. Is it possible that the root method somehow nuked this functionality? I've already restarted the adb server numerous times, rebooted the player, turned debugging off and back on, etc. Even after all that it just sits after displaying the transfer rate and never finishes.
Edit: Nevermind. Looks like this issue also goes back to having to do adb root and adb remount. Gotta do it for everything apparently
prsterero said:
The first time around I got into the bootloop so I had to start over. Second time and it worked now it seems that I can't get apps to install through the adb install command. I'm mainly trying to get es file explorer and stick mount so I can use an external flash drive. Is it possible that the root method somehow nuked this functionality? I've already restarted the adb server numerous times, rebooted the player, turned debugging off and back on, etc. Even after all that it just sits after displaying the transfer rate and never finishes.
Edit: Nevermind. Looks like this issue also goes back to having to do adb root and adb remount. Gotta do it for everything apparently
Click to expand...
Click to collapse
Weird, windows 8?