Develop Bugs

[Q] ADB: permission denied

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!!

[Q] Simple Root for EB13

Is there a simple, non-CWM flashing one-click root for stock EB13 Epics (I just want to tether to my rooted nook)?
I ask because a few months back I rooted my DI18 Epic with a "One Click Root" and, for some reason, all my apps became unlinked from the android market, and nothing I did worked to restore their connections. After a few hours of panic, I unrooted using the accompanying "One Click Unrooter," and the problem went away.
Then, I noticed my bluetooth was't working. I took it to the Sprint store, they ordered me a replacement phone, and then wouldn't exchange it because CWM was on my current phone. I got them to exchange it eventually, but I felt like a complete dumbass for not knowing it didn't come off in the one-click-unrooting process.
So, is there a way to just get root? And then is there a simple way to get rid of it (uninstall SU and such as well) in case I have to exchange the hardware?
I've read a lot of stuff about flashing stock with Odin, but all the dl links for Odin are 404'd, and I'd rather not have to go back to fresh stock every time I need to take my phone in. What's your advice?

SuperOneClick v1.7 worked for me.

Trickee360 said:
Is there a simple, non-CWM flashing one-click root for stock EB13 Epics (I just want to tether to my rooted nook)?
Click to expand...
Click to collapse
I don't know about "one-click", z4root might work, but there's anecdotal reports of it not working on Android 2.2.1. The one-click w/CWM redirector is the easiest way to root and definitely recommended if you want to do anything more advanced (ROMs, etc.). You can always return to stock everything with Odin.
That said, if all you want is root and nothing more, the manual version is relatively simple. It's really just three steps:
Use an exploit (rageagainstthecage-arm5.bin) to get "temporary root" (an ADB root shell).
Install Superuser's su binary to /system/xbin with the appropriate permissions (root.shell 4755).
Sideload Superuser.apk as a regular program, or download it from the market.
In which case "unrooting" is trivial. Just delete /system/xbin/su with root-explorer or something, and after remove Superuser via "Manage applications".
A while back I wrote up semi-detailed directions for doing this. They should work on EB13 with some modification. Here's some notes for EB13:
"rageagainstthecage-arm5.bin", "su", and "Superuser.apk" are all included in the one click package, that's the easiest place to get them.
Actually running "rageagainstthecage-arm5.bin" is the trickest part. There's a few ways to do it, and due to the nature of the exploit, sometimes only one or two of them will work for anyone. You can tell it works if on the next run of "adb shell" you get a "#" prompt instead of "$". Try these three ways in order until one of them works:
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb shell /data/local/tmp/rageagainstthecage-arm5.bin
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb shell (press return, and type below at the "$" prompt):
/data/local/tmp/rageagainstthecage-arm5.bin
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb push root.sh /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb shell chmod 755 /data/local/tmp/root.sh
adb shell /data/local/tmp/root.sh
With the last method's root.sh from the one-click package.
Once you have root, and have verified such by getting a "#" prompt with "adb shell", then run:
Code:
adb shell rm /data/local/tmp/rageagainstthecage-arm5.bin
adb shell rm /data/local/tmp/root.sh
adb shell mount -wo remount /dev/block/stl9 /system
adb push su /system/xbin
adb shell chmod 4755 /system/xbin/su
adb shell mount -ro remount /dev/block/stl9 /system
adb install Superuser.apk
If you do nothing more, OTA updates should apply just fine. The only caveat is that /system/xbin/su will lose the appropraite permissions, so Superuser will no longer work. To restore it, do the same steps above to regain "temporary root", then run:
Code:
adb shell rm /data/local/tmp/rageagainstthecage-arm5.bin
adb shell rm /data/local/tmp/root.sh
adb shell mount -wo remount /dev/block/stl9 /system
adb shell chmod 4755 /system/xbin/su
adb shell mount -ro remount /dev/block/stl9 /system
You shouldn't have to push a new "su" binary since it's already there, and similarly, you don't need to reinstall Superuser.

Cant Run ADB Commands

Im trying to downgrade my Desire Z. Using this code:
Code:
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
When i type:
adb push psneuter /data/local/tmp
I get this message:
cannot stat 'psneuter': No such file or directory
I then tried to push the same file if i added .txt at the end of psneuter.
This still did not work.
I then typed cd [directory] and tried it (without .txt) and it still did not work.
I then tried it with .txt and it works.
So i had to cd the directory and then add the file extension? Guessing this isn't normal, but i could deal with it.
However when i got to the third line, i don't know the file extension of misc_version, so i was unable to continue. Can anyone shed some light please? What am i doing wrong or what haven't i done?
Thanks

NthZ said:
Im trying to downgrade my Desire Z. Using this code:
Code:
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
When i type:
adb push psneuter /data/local/tmp
I get this message:
cannot stat 'psneuter': No such file or directory
I then tried to push the same file if i added .txt at the end of psneuter.
This still did not work.
I then typed cd [directory] and tried it (without .txt) and it still did not work.
I then tried it with .txt and it works.
So i had to cd the directory and then add the file extension? Guessing this isn't normal, but i could deal with it.
However when i got to the third line, i don't know the file extension of misc_version, so i was unable to continue. Can anyone shed some light please? What am i doing wrong or what haven't i done?
Thanks
Click to expand...
Click to collapse
Sounds like you didn't set your path; either set a path to adb or make sure all the files are in the same directory of adb and run the commands from that directory
Sent from my T-Mobile G2 using XDA App

OriginalGabriel said:
Sounds like you didn't set your path; either set a path to adb or make sure all the files are in the same directory of adb and run the commands from that directory
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
i thought i did set a path though. and it doesn't explain why i need to add the file extension...or is that normal?
can you remind me how to set a path please? i went to computer and path>edit then added the directory of platform-tools and tools to the list. is that all thats needed? where should i save the files such as psneuter?
thanks

All I do is rip out the needed adb files and put them in a folder on my dekstop. Then you can push the files you need to your device.
Sent from my SCH-I500 using Tapatalk

NthZ said:
i thought i did set a path though. and it doesn't explain why i need to add the file extension...or is that normal?
can you remind me how to set a path please? i went to computer and path>edit then added the directory of platform-tools and tools to the list. is that all thats needed? where should i save the files such as psneuter?
thanks
Click to expand...
Click to collapse
Sounds like you added the path correctly; if you did, you should be able to run adb from anywhere. It doesn't matter where the files are on your computer, what matters is that you're running the commands from that folder.
For example, if all the files are in C:\root_files then when you open up a command prompt, you need to type 'cd C:\root_files', hit enter and then run the adb commands from there.
Sent from my T-Mobile G2 using XDA App

Can you not drag and drop the files into the terminal in Windows like you can on Mac?

thanks for all the comments. will have another go tomorrow.
i made another thread but no one has answered, my desire z is running android 2.2.1. do i need to downgrade to 2.2, then 1.74, then 1.34 to root it, or can i go straight from 2.2.1 to 1.34?
Thanks

The 2.2.1 is android version, not sense version.
You need to downgrade to 1.34 sense version, which is also running 2.2 I think.
-Nipqer

i solved the above problem but now have a new problem.
After i typed "adb shell /data/local/tmp/psneuter"
to try and get temporary root, i got this message: /data/local/tmp/psneuter: permission denied
I googled about a bit and tried another command:
C:\Root_Files>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 0755 psneuter
chmod 0755 psneuter
$ ./psneuter
./psneuter
property service neutered.
killing adbd. (should restart in a second or two)
Then tried adb shell again.
It granted me root access, but i figured i'd try and stick to the tutorial i was on.
so i went back and typed adb shell /data/local/tmp/psneuter again, and now i get this message:
mmap() failed. Operation not permitted
however if i typed "adb shell" i get #.

[HOWTO] (Manually) Rooting the Kindle Fire 2 with a Mac

Firstly, Merry Christmas!
Note: This worked on version 10.2.4
I received a Kindle Fire 2 today and since then I've been trying to get it rooted, now that I have I though I'd share it here for other people who might be in the same situation.
This is really just a remixing of the tool made by Bin4ry (http://forum.xda-developers.com/show....php?t=1886460) but I couldn't get the script to run on my Mac...
Step 0 - Preparing
You must enable ADB and Unknown App sources from Settings.
Settings > More > Security > Enable ADB
Settings > More > Device > Allow Installation of Applications
Step 1 is to get that tool from here. and extract it somewhere you'll remember.
Step 2 (you can skip this if you already have the android SDK platform-tools in your PATH)
If you don't have the android SDK or adb installed just add the 'stuff' folder from the tool to your path.
In terminal run
Code:
export PATH=$PATH:/path/to/extracted/tool/stuff/
Step 3 - Push the required files
It's probably easiest if you change into the stuff folder first...
Code:
cd /Users/x/Downloads/Root_with_Restore_by_Bin4ry_v18.7z\ Folder/stuff
Then run the following...
Code:
adb push busybox /data/local/tmp/.
adb push su /data/local/tmp/.
adb push Superuser.apk /data/local/tmp/.
adb push ric /data/local/tmp/ric
Then you need to run an adb shell to set some permissions
Code:
adb shell
(you should get a prompt like [email protected]:/)
Run
Code:
chmod 755 /data/local/tmp/busybox
exit
Step 4 - Rooting
This requires another terminal window. Check that you can run adb from there as well (running adb should print the usage information)
In the first window run:
Code:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > /dev/null
In the other run
Code:
adb restore fakebackup.ab
You should get a prompt on your Kindle, hit the restore my data button. As you do so the command in the first window should stop (or a few seconds later - if it doesn't stop it and re-run both commands again.)
You can now close the second window!
Run
Code:
adb reboot
, your Kindle should reboot though the screen will be blinking repeatedly (flashing between the lockscreen and the boot animation) don't worry about that as it will be fixed in a sec.
Step 5 - Cleaning Up
Run
Code:
adb shell
If all was successful you should see the prompt change to [email protected]:/
If it did, continue otherwise go back to step 4.
Run these
Code:
/data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/ric /system/bin/ric
chmod 755 /system/bin/ric
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su
chmod 655 /system/app/Superuser.apk
chmod 755 /system/xbin/busybox
rm /data/local.prop
reboot
Your Kindle will restart and SuperSU will be available under Apps, your now free to do as you please, though you could follow with Step 3 on this thread to get Google Apps etc working.
Update: a short guide to installing the Play store can be found here.

This worked almost perfect for me but I couldn't get it to run adb commands from the stuff folder so I dumped its contents (minus the adb stuff) into the platform-tools in the android SDK and from then on everything went great. Thanks so much.

didthis work for 10.2.4 users out there
does this work for 10.2.4

worked!
Great work, congratulations and thanks! I'd like to make some comments tho regarding some typos and suggestions.
1.- I'd suggest to install the android SDK as, in fact, adb commands didn't work from the stuff folder. Add a line to .bash_profile with the export PATH command to make permanent access to the adb shell.
2.- Push files from the Root_with_Restore_by_Bin4ry_v18 folder, not the .7z file.
3.- The command is, e.g., adb push busybox /data/local/tmp/ instead of adb push busybox /data/local/tmp/.
4.- In Step 5 the command /data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su is twice so you'll get an error the second time you execute it.
Also congratulations for instructions on how to install PlayStore - here pay attention to the names playstore.apk and servicesframework.apk which in fact are plstore3.10.10.apk and GoogleServicesFramework.apk respectively -
Once again thanks for your work.

gorganzolia said:
does this work for 10.2.4
Click to expand...
Click to collapse
Yes this worked for 10.2.4

10.2.6
Does this work with 10.2.6?

it worked
Tried it this morning on 10.2.6 and it worked woohoo now how do you stop it from automatically updating
Found out how to stop those automatic updates here http://forum.xda-developers.com/showthread.php?t=2086450

Unlocking DZ ONLY by power button? :)

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