Related
I have used ADB in the past on my G1 and am now running into a problem on my G2. When I try to push a file to the SD card I get "permission denied". Any ideas?
example:
C:\android-sdk-windows\tools>adb shell
$ adb push su /sdcard/su
adb push su /sdcard/su
adb: permission denied
You need to go to the VISIONary when it show "permission deniedArrow", it will pop up something, choose "allow"
Are you sure I need root to push a file? In this guide to perm root (http://forum.xda-developers.com/showthread.php?t=834228) the first step is to disable or uninstall visionary.
I figured it out. You don't need to "adb shell" first
When I try to adb remount , I get a return of "remount failed: operation not permitted" does anyone no how to get adb to remount, I firtst run adb devices , and my phone serial number comes up but cant remount, can someone please help me get past this.
Lol u need to Su first after adb shell I see that u don't have a #
Sent from my HTC Vision using XDA App
The solution is to start ADB in root mode in command prompt...
Steps I did with my Galaxy S to add an App:
1. Connect phone to computer via USB in Debug Mode
2. Load command prompt and type: adb root
3. set read/write for system folder:
adb shell
su
Then type mount and find the location of system folder, in this case for me it's /dev/block/stl9
mount -o remount,rw /dev/block/stl9 /system
exit
exit
4. set your cmd prompt to folder where you have files to push/move onto phone i.e. f:\app or etc using f: and cd app for example
5. then to copy files to system/app folder by typing type: adb push <appfilename>.apk /system/app
Voila!
To remove an app do the following: adb shell rm /system/app/YourApplicationHere.apk
Simples
As a noob it took some time to figure this out with some help here and reading the help info after typing adb in prompt and the Eureka! moment came...
Hope this helps
Peter
ADB or term emu on device
HTC Vision 1.8 OC, CM7 RC1==HAPPY!!
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?
I used this two guides when trying to root my Desire Z
first installed Android_SDK
http://wiki.cyanogenmod.com/index.php?title=Howto:_Install_the_Android_SDK
and it works perfect, I can run command adb devices and my device is shown there.
the problem appear when I followed the second guide to downgrade the ROM
http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_Z:_Rooting#Downgrade_to_1.34.707.3
under that guide, there is some command must be done:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
Click to expand...
Click to collapse
and when I tried to run "adb push psneuter /data/local/tmp" the command prompt replay "cannot stat 'psneuter': No such file directory"
I already put the "psneuter" in same folder (platform-tools) with adb.exe on directory C: android-sdk-windows.
Anyone has the experience or familiar with this problem? please help
I already search the same problem on google, and find some user has the problem too, but still there is no solution or I already did and useless
Try to cd into the directory that contains adb.exe
Make sure you are in that directory of adb.exe
Example how mine is
cd C:
C: cd android-sdk-windows
C:/android-sdk-windows/> cd platform-tools
C:/android-sdk-windows/platform-toold/>
Then from there do adb comman
C:/android-sdk-windows/platform-tools/>adb push psneutor /data/local/tmp
And so forth and it should go through fine
If you setup sdk in enirovemnt where can run adb anywhere then there less and simple way
All you would have to do is adb push (drag the file into cmd window) /data/local/tmp
theSpam said:
Try to cd into the directory that contains adb.exe
Click to expand...
Click to collapse
ilostchild said:
Make sure you are in that directory of adb.exe
Example how mine is
cd C:
C: cd android-sdk-windows
C:/android-sdk-windows/> cd platform-tools
C:/android-sdk-windows/platform-toold/>
Then from there do adb comman
C:/android-sdk-windows/platform-tools/>adb push psneutor /data/local/tmp
And so forth and it should go through fine
If you setup sdk in enirovemnt where can run adb anywhere then there less and simple way
All you would have to do is adb push (drag the file into cmd window) /data/local/tmp
Click to expand...
Click to collapse
thanks bro, work when I drag the file to cmd
but stuck again when I follow step 7 & 8
7. On the computer, open terminal and run the following command:
adb reboot bootloader
8. Follow the on screen directions, on the HTC Desire Z, on flashing the 1.34.707.3 firmware.
Click to expand...
Click to collapse
can I also ask this question in this thread? or is there anybody have a free time to guide me
after you do those steps in command type adb reboot bootloader once again make sure your in the adb.exe directory
from there phone should reboot int bootloader (white screen) and it will do a check for the PCIMG after it will ask if you want to install update Vol for yes and VOl for no
ilostchild said:
after you do those steps in command type adb reboot bootloader once again make sure your in the adb.exe directory
from there phone should reboot int bootloader (white screen) and it will do a check for the PCIMG after it will ask if you want to install update Vol for yes and VOl for no
Click to expand...
Click to collapse
step 7 work fine, but phone only show bootloader and didn't ask to install update..
maybe stupid question but should i need to run RUU on my computer first after type adb reboot bootloader?
measn you dont have the PCIMG on sdcard
On the computer, open terminal and run the following commands:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
NOTE: You should have the "#" sign instead of the "$". If you do, you have temporary root, and can continue on.
/data/local/tmp/misc_version -s 1.33.405.5
exit
Copy the 1.34.707.3 firmware to the root of the SD card (NOT in any folders).
On the computer, open terminal and run the following command:
adb reboot bootloader
Follow the on screen directions, on the HTC Desire Z, on flashing the 1.34.707.3 firmware.
Once finished you can can continue to the next section.
Click to expand...
Click to collapse
Ok I got it, it because I copy the RUU on the sd card instead PCIMG.zip, my bad.
another question bro, how to backup my current build (1.82.707.1)? if i downgrade to 1.34.707.3, is not the current build will be replaced?
Vader™ said:
Ok I got it, it because I copy the RUU on the sd card instead PCIMG.zip, my bad.
another question bro, how to backup my current build (1.82.707.1)? if i downgrade to 1.34.707.3, is not the current build will be replaced?
Click to expand...
Click to collapse
need custom recovery to back up current rom sorry
ilostchild said:
need custom recovery to back up current rom sorry
Click to expand...
Click to collapse
is there anyway to do custom recovery without downgrade?
anyway thanks very much for helping me bro, really appreciate it.
umm not that i know of really if you can gain temp root you can back up your apps and all with titanium, but you want a full nandroid your gonna need a custom recovery, and the way your going allows you to downgrade to achive root and custom recovery
ilostchild said:
umm not that i know of really if you can gain temp root you can back up your apps and all with titanium, but you want a full nandroid your gonna need a custom recovery, and the way your going allows you to downgrade to achive root and custom recovery
Click to expand...
Click to collapse
I see, thanks again bro.
I successfully followed itiskonrad instructions how to brick your phone by copying framework-res.apk with ES Explorer.
The result was a soft brick, when phone would freeze at LG logo.
Hopefully at that point it can be accessed from PC with adb.
So here are the steps I took to unbrick it
Before you start, have a copy of working framework-res.apk in C:\ (path doesn't matter as long as you change it at command below:
1) re-root with SuperOneClick (v2.3.1.0). I had to do this because su command would fail.
2) open cmd and type in: adb shell it should show you either $ or # before the cursor. (how to install adb you can find on google)
3) type (each line separate command which you must finish by hitting ENTER key):
su
mount -oremount,rw /dev/block/mtdblock3 /system
exit
exit
adb push "C:\framework-res.apk" /system/framework-res.apk
adb reboot
Hello!
I bought already DZ and everything is fine, but the system of keyboard is pissed off So, I was thinking if is any way to change that when Im opening a phone automatically screen is turned on. I would like to change that, because sometimes when im taking him the phone is trying to open, because of best opening system Screen should turn on only if I will press the power button. Any idea how to resolve that? I'd really appreciate that.
root DZ
IM NOT RESPONSIBLE TO BRICKED DEVICE(S), APOCALYPSE, GLOBAL WARMING AND NUCLEAR WAR
IT WORKED 4ME BUT MAY NOT WORK 4YOU
Download: Attachments (unzip Root.zip to C:/htc/ directory, then copy PC10IMG.zip and .apk files to C:/htc/) PC10IMG.zip link has been dended to your XDA mailbox
Then:
unpack attachment to C:/htc (example)
copy System32.zip files to C:/Windows/System32/
TempRoot:
Run cmd and type:
Code:
adb push C:\htc\fre3vo /data/local/tmp
adb shell
chmod 777 /data/local/tmp/fre3vo/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
This will kick you srom the device shell , but dont worry and DO NOT reboot your device
Change Misc Version:
Code:
adb push C:\htc\misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
/data/local/tmp/misc_version -s 1.33.405.5
To get:
Code:
--set_version set. VERSION will be changed to: 1.33.405.5
Patching and backing up partition 17...
Then type:
Code:
sync
Now you must type this GOOD (fail=brick) (still in shell!!!):
Code:
dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
Then type:
Code:
exit
Then copy PC10IMG.zip package:
Code:
adb push C:/htc/PC10IMG.zip /sdcard/PC10IMG.zip
CMDline wont response for 6-10 minutes, its fine, its good
When finish type:
Code:
adb reboot bootloader
Wait until bootloader parse package and press VOL-UP
DO NOT POWER-OFF YOUR DEVICE (PLUG IT TO CHARGER)
When it finish, press POWER button to reboot
You dont must set up android
Switch on usb-debugging (settings/apps/develop)
then plug it to pc and type in cmd:
Code:
adb install C:\htc\AndroidTerm.apk
adb install C:\htc\TotalCommander.apk
adb push C:\htc\busybox /data/local/tmp/
adb push C:\htc\gfree /data/local/tmp/
adb push C:\htc\rage /data/local/tmp
adb push C:\htc\root /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/*
adb push C:\htc\su /sdcard/
adb push C:\htc\Superuser.apk /sdcard/
Then launch Terminal emulator and type:
Code:
/data/local/tmp/rage
to get
"forked xxxxxx childs"
Tap "menu" and select "reset term"
It will kill the terminal
Launch Terminal emulator again, but you will get error wit "force close" (force close it)
Launch Terminal Emulator again and type:
Code:
/data/local/tmp/gfree -f
/data/local/tmp/root
sync
close terminal emulator and launch Total Commander
Go to "system directory" and try to open /data
If succeed (Superuser request): TOU DID (S-OFF, Super-CID (no simlock), root)
You can use RootKeeper.apk to "survive" su binary when installing OTA update (you can root android 2.2 but no android 2.3.3)
Disable root keeper when making nandroid
When you have root you can modify it with flashing another rom
Please hit thanks button
I read that few times to be sure what ive got to do, so tommorow im gonna do the operation Man, you are awsome. In one time I will get root (im doing that from time, when i wrote that thread) and resolve of my unlocking problem Hope, that i will not get lost on that. Cant wait for tommorow..
unlocking DZ
I forgot about one thing: after /data/local/tmp/root you can get error, but it's fine too
If you dont want to check root with Tcmd type "su" in terminal