Database Info

Problems with ADB

Trying to do some push/pull and do the new lag fix to no avail. After adb devices, the phone shows up as attached, but after adb remount I get "remount failed: No such file or directory" I'm not able to execute a push or pull command, and therefore I'm not able to run the lag fix.
I have USB Debugging selected, and I was able to delete the bloatware via adb shell, but none of the other commands go through for me...

Which version of Windows are you running?

Windows 7 64 bit

Still haven't found a fix to this, so I'll post up what I'm inputting and what I'm getting in return.
Here is the code I use to get into ADB and then attempt a remount:
Code:
cd C:\android-sdk-windows
cd tools
adb remount
remount failed: No such file or directory
When I try to push and/or pull, I get this:
Code:
adb push ./smoothcalendar.apk /system/app
failed to copy './smoothcalendar.apk' to '/system/app/smoothcalendar.apk': Permission denied
I've tried adb kill-server, then adb remount with the same issues.

currently experiencing the same problem...

Do you have BusyBox Installer installed on your phone? I believe you have to have it installed in order to use Android SDK.

I've got Busybox 1.17.1 on mine.

I'm wondering, is this a problem at the computer level or at the phone level? I know the Vibrant had some issues with push/pull, but I see some stuff here in the dev thread (lagfixes, sideloader stuff) that if I run from my computer attempt push/pull commands that fail and therefore the thing I'm running (lagfix most recently) doesn't actually work and I'm stuck with a slower phone.
If its a phone issues, I can just exchange it under warranty, since I'm out of my 30 days. But I'm hoping it's not as I'd like to keep this one that other than this has worked great for me.

When I first starting using ADB, I was connecting my phone like when I was using Windows Explorer to muck around on it. I had mounted the usb connection in the notification window. I kept getting errors when I tried to push/pull. I reconnected once and forgot to mount the usb connection and everything worked perfectly. Make sure the usb debugging is check marked in Applications in settings. Try to do the push/pull without using remount command and don't click on the USB connected notification option when you plug it in. I'm really new at this linux stuff so I could be wrong. I'm just trying to share my experience in hopes that maybe you're doing the same things I was doing before I stumbled onto the right way to do it.

Hmm, odd, I've tried that very method many times before, to no avail.
I try it just now, and having no problems with push or pull. Works for me! Thanks!

adb help for noob

I posted this in another thread but got no response, this thread (http://forum.xda-developers.com/showthread.php?t=502010&page=35)
maybe a new thread will help.
So this is my first venture into the whole ABD thing. I am trying to install the framework mod from Tazz for the HTC music player (as listed here: http://forum.xda-developers.com/show...5594&page=1277 post 12768).
Tazz mentions to “push this http://www.multiupload.com/1WWHXAUN6W
to system/ect/permissions then download and install htc music”
So, running my trusty Win7 machine I downloaded the SDK from the android development site, inserted the correct line in the path and viola, I can enter the CMD prompt and run the adb command successfully. Adb and adb shell both seem to work.
I followed the instructions from here: http://androidforums.com/developer-1...-commands.html and here: http://forum.xda-developers.com/showthread.php?t=502010 for the install.
My problem comes in when I try to push the file to the phone.
Fisrt dumb question is: what phone mode should I be in when running the adb? Standard running mode or booted to recovery? (I thought I read something about being in recovery but at that point it was all a blur).
I have the USB Debugging turned on so I think I am ok there.
I installed the SDK to my C:\Android directory.
I saved Tazz’s file to my C:\Android\Tools directory.
Here is my cmd text (maybe this is where I went wrong):
In the cmd window I CD’d to the C:\Android\Tools directory
adb push com.framework.htc.xml system/ect/permissions
After making sure that I was in the correct dir and all files were also located in the correct dir I am still getting an error, file or directory not found, or something like that.
Sorry for the long post. I figured this would be a good first step (my first adb experience) as it seems pretty benign in terms of me bricking anything but offering a good learning opportunity.
I am running a rooted Eris (KaosFroyo v36).
In looking things thru maybe I need a USB driver for the Eris?
any help is appreciated,
oh, my cmd prompt looks like sh-2# (or something like that)
Thanks

While it may be that you still need to download the appropriate drivers, it seems you are able to get root access so, this is likely not the case.
There are two things which stand out as potential issues in the steps you described. Fortunately, both are super easy.
First and foremost, make sure you have mounted the phone as "read-write."After you have cd'd to the tools folder type "adb remount" (without the quotes) and press enter. If successful, it should respond with "remount succeeded." Congrats, you have now mounted the phone as read-write.
Next, I see errors with your command. There should be a "/" before "system" and it should be "etc" not "ect." Specifically, your command should be:
adb push com.framework.htc.xml /system/etc/permissions/
[The above command of course, assumes that the name of the file you are pushing is indeed named "com.framework.htc.xml" and is in your tools folder.] You'll know it worked if the response in your command prompt indicates the speed and time it took for the push to take. For example, "1234kbps in 3.4 seconds". If you see something resembling that you should be all set. At this point you can reboot your phone and your changes should be in effect. Either unplug and reboot manually or just type "adb reboot" (without the quotes) and press enter.
In regard to your question about whether the phone can be in standard running mode or recovery... It depends on the level of root of the phone but, fully rooted and nand unlocked phones can be adb'd while in standard running mode. My EVO can and it is very likely your Eris can too.

I see
thanks OK.
typo's aside in the thread, my command was missing the / as you have described it. I also did not know about the remount thing. In my reading I thought that was just for the sd card. I will try and put all the pieces together when I get home tonight.
You are correct in that is the name of the file and I do have it in the /tools directory.
Thanks for the help, baby steps (I am learning)

No problem. We are/were all noobs at one point in our lives.
The term "mounting" has slightly different contextual meanings which can be confusing. First off, the /system/ folder is already "mounted" while using adb, however, it is mounted as read-only. So, if you are ever trying to push something to the phone and get an error back that says "mounted as read-only" you'll now know what went wrong. Simply type "adb remount"
and it puts the /system/ folder into read-write mode.
Bear in mind that upon phone reboot the /system/ folder automatically remounts into read-only mode so if you reboot and try to push another file you'll need to remember to "adb remount" again.
With regard to the sdcard "mounting" refers to whether the phone (sdcard) is mounted as a disk drive on your computer. You'll find that if this is the case many adb commands won't work because the sdcard can't be accessed by the phone while mounted on the computer. Therefore, always remember to connect your phone as "Charge Only" when adb'ing.

got it
That did the trick, worked like a charm. Thanks for the help and pointers. I have now pushed my first file...yeah for me!!
Thanks for your help and time.

glad your push worked
I am still trying to get SDK/ADB to connect to my Milestone XT720 phone. Have no idea of why they won't. Have tried all the usual suspects but nothing as of yet. NEED HELP!

[Q] Adb Problems

I have a droid x2, and im using the same computer I used for my fascinate/charge. I themed on my fasc/charge and adb worked fine, I could push pull remount, you name it. Now with this x2 everything but adb pull doesnt work. I am rooted, im running a custom rom, I have all the updated drivers, My paths are correct cuz im using the same computer, everytime I adb push I get permission denied, and if I go to adb remount I get Operation not permitted. Im not sure what the problem is.

Uninstall drivers, install easytether/pdanet drivers, plug phone in and let install. Try the micro sd adaptor that came with the phone.

Possible fix
I ran in to a Bionic where even the drivers from Moto and the ADB related ones ALL INSTALLED EVERYTHING was good adb devices picked up the phone but anytime I tried to push or pull I got permission denied. I even tried running adb shell then su then running adb push still to no avail.
MY QUICK FIX...
I rebooted the phone in to recovery adb reboot recovery [if it will take the command].
WAIT as it will need to install drivers again when recovery loads [I am using the official Open Source CWR].
Those all installed again with no issues.
Then you need to go to either mounts and storage or advanced>mounts and storage [forgert off hand]. I chose to mount EVERYTHING, but you prolly only need the sdcard-ext [top option not bottom USB mount]
Then when I ran adb push low and behold it went through with no issues.
Once that was done I restarted [this time bootloader per pathsaver steps] and proceeded to flash via RSD.
When this completes and I am able to test I will see how it reacts when I load in to OS after re-flash [via default RSD image not a custom ROM] and I get everything running.

problem
I can not istaliram, where can I find a detailed explanation?

Newbie help with rooting Asus Transformer Prime via ViperMOD

I have never rooted an android device before and this is my first time. The reason I'm rooting is so I can enable the Virtuous Prime ROM (the guide for Virtuous Prime suggested to use ViperMOD to root first)
[ROOT] [TOOL][Updated 2.22.12]viperMOD PrimeTime v4.5 | Auto Root/Unroot/Busybox/CMW - xda-developers
^I'm following the instructions from the link above word for word. So far I've met the following Criteria:
-Enabled USB Debugging
-Running build 9.4.2.15
-Have "ASUS Android Composite ADB Interface" drivers installed and updated
I downloaded the ViperMOD 4.5 zip and extracted it to my PC. I opened the folder and right clicked on "viperMOD Primer Tool v4.5 - copy.bat". A cmd popped up with several different options; I pressed 1 to root, and pressed enter to skip the following two prompts (that ask if USB debugging is enabled and asus usb drivers are installed).
The CMD then showed the following message:
*daemon not running. starting it now on port 5037*
*daemon started successfully*
However the CMD just stopped there. It didn't show the following flood of text that should show up when rooting w/ ViperMod (like shown in this video: http://www.youtube.com/watch?v=C3OQkxmUyLc at 2:35)
I'm not sure if I'm missing something here. The guide however did say that I needed to "Kill Asus Sync and Splashtop" though I'm not exactly sure what it means by "kill". I don't have Splashtop running on my Prime nor Splashtop remote running on my PC. I also don't have ASUS Sync software installed on my PC and I disabled Auto-Sync on my Prime (HOWEVER, the ASUS Sync icon is still visible in my Prime's notification bar when I connect it via USB to my PC).
Any advice?

I had a similar problem
I tried to use superoneclick to root my Samsung Gravity and it hung on waiting for phone. I used the adb commands to load the zergRush exploit. So you need to find which exploit works on your phone, adb push the exploit, busybox, and su to your phone and use adb shell to do the root.
** DISCLAIMER: I'm pulling this command sequence out of my memory... you should find a better guide but this stuff may give you clues as to what to google for, or if you're familiar with shell you may see the gist of what you're trying to do **
The commands will look something like this:
adb push exploitfilename
adb push busybox.apk
adb push su
adb shell
chmod 755 exploitfilename
./exploitfilename
(wait for the exploit to finish)
pm install busybox.apk
pm install su.apk
reboot
Once it rebooted, I installed terminal through the market so I could do cool stuf like so:
su
mount -o remount,rw /dev/whateverdevhasyoursystemfolder /system
rm /system/app/Vendorgarbagebloatapp.apk
and so forth. Knowledge of linux and shell commands is your friend here for sure. Basically, you should know what you're doing or don't do it. I'm no fan of one-clicks for anything like this, it's too hard to figure out what went wrong if it goes wrong, plus this way you can learn new skills.

Can't seem to run Vipermod
I am trying to run vipermod on my computer but when I try to run it, it flashes on the screen for less than a second and then re-closes.
For a little extra info I have a tf101 running the 9.2.1.17 build
My computer is running the window 8 developers copy( no i'm not a dev just love testing new things before most other people.)
I've tried running it as an admin and in compatibility mode but have had no success as of yet any help would be greatly appreciated.

sasori563 said:
I am trying to run vipermod on my computer but when I try to run it, it flashes on the screen for less than a second and then re-closes.
For a little extra info I have a tf101 running the 9.2.1.17 build
My computer is running the window 8 developers copy( no i'm not a dev just love testing new things before most other people.)
I've tried running it as an admin and in compatibility mode but have had no success as of yet any help would be greatly appreciated.
Click to expand...
Click to collapse
U should tried on another comp with windows seven imo

I would if i had one but my laptop got stolen so my only computer besides my desktop is my transformer, Are their any .bat files out their that i can use to run it from? I found out that its a problem with windows 8 not allowing .exe files to open command prompts, but if its a .bat file it will run.

[SOLVED] Problems rooting using debugfs method

Hi everyone, I've been doing a good bit of googling and found nothing yet, so if this has been asked before I'm very sorry but I haven't yet seen anyone on the forum with the exact same issue. I actually updated to JB OTA when I first got the device in Canada (US version), when I got back to the UK I decided to root, but then found out that you can't on JB, luckily I managed to downgrade to ICS V9.4.5.30 downloaded from the ASUS website! I was not able to downgrade to an earlier version however, stock recovery wouldn't allow it so NVFLASH root method is out the window... Now I would prefer not to unlock my bootloader for now.
When running debugfs.bin 1 click root method, on my desktop (not run as admin) it says:
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
*daemon started successfully *
'find" is not a recognized as an internal or external command, operable program or batch file.
Less than half a second later it just closes down.
When run as admin, it does the same thing and instead of closing down it goes back to the first screen where you can select what method you want to use.
On my netbook it runs and just stops at daemon started successfully, the tablet has no response and debugfs just stays on that screen till I close it down.
Both my computers have all the correct drivers and the latest version of debugfs running, both are windows 7 Ultimate 64-bit.
Please help me as my Infinity is just sitting around doing nothing as when I downgraded to ICS all 190 apps I installed were wiped too, and obviously there's no point me reinstalling any apps till I get this bad boy rooted...
Many thanks in advance!

Make sure you're connecting to a USB 2.0 port, not 3.0, on your computer.
Try not to use any intervening USB hub.
Try to make sure that you're using the back ports on a desktop machine as sometimes the front ports and be a bit sketchy.
Reboot both tablet and computer before starting, and as always, make sure the tablet has USB debugging enabled.

only my netbook has usb 3.0 and I used the 2.0 port, I will now try the back ports of my desktop, I didn't use any extensions or usb hubs, I have debugging and unknown sources checked. I have tried the restarting already, which I'll do right now again... thanks though..

Code:
@adb kill-server
@adb wait-for-device
@adb shell mount | find " /system" | call RootDebugfs.bat x
That is where you're system is tripping up. For some odd reason when it runs that part of the script, it trips up.
It's not a device not found error, b/c it would 1) say that, and 2) never make it to that last line, just hang at the previous line. Yet when I connect my Infinity it works perfectly fine on mine. For some reason the command "find /system" is not working correctly on your system after performing the shell mount command.
Do you have the Android SDK installed on your system?

Android SDK and Java DK were not installed, just installed them still exactly the same issue, haven't rebooted since installing them though
Is there a way I could use Linux to root, as I do have Linux Mint running?
johnlgalt said:
Code:
@adb kill-server
@adb wait-for-device
@adb shell mount | find " /system" | call RootDebugfs.bat x
That is where you're system is tripping up. For some odd reason when it runs that part of the script, it trips up.
It's not a device not found error, b/c it would 1) say that, and 2) never make it to that last line, just hang at the previous line. Yet when I connect my Infinity it works perfectly fine on mine. For some reason the command "find /system" is not working correctly on your system after performing the shell mount command.
Do you have the Android SDK installed on your system?
Click to expand...
Click to collapse

I dunno why it is not working then. What you're doing is exactly what I did *successfully* to root my Infinity and then take the JB upgrade ans restore root.
I have another file called Infnity Root that you can try: check your PMs for the link

johnlgalt said:
I dunno why it is not working then. What you're doing is exactly what I did *successfully* to root my Infinity and then take the JB upgrade ans restore root.
I have another file called Infnity Root that you can try: check your PMs for the link
Click to expand...
Click to collapse
Thanks so much anyway! I've already tried that file, it's exactly the same

Yeah, it looked very similar, but it included more things in the actual Download like the drivers.
Not sure why it is not working - can you run those three commands in a command prompt window and see what you get?

well they say 3's a magic number, computer number 3 worked! For some reason something on my desktop and netbook was causing the root to fail, now I'm updating to jb ota... Thanks for the quick responses otherwise I would have assumed the problem was with the tablet and not my machines...

Glad you got it working. Quite possibly an antivirus program, firewall, or other such problem.