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!

[Q] HP Zeen C150 Tablet

Anybody have one of these? I recently got my hand on one, and the estation c1650 printer also, and wondering if there is anybody else with on, would like root, and or wipe the device and get ride of the stupid hp touchsmart UI. it would be a dream to run a galaxy tab rom or something. I though i saw a galaxy tab floating around? a system dump maybe? But any help would be appreciated.

HP Zeen
OK, I managed to use the latest Android (2.3) SDK usb drivers to get the windows to recognize the device. I could copy files to/from the SD card.
USB\VID_03F0&PID_9F11&REV_0223&MI_01
USB\VID_03F0&PID_9F11&MI_01
To get it to work, I had to edit the inf file at location:
"[SDK PATH]\google-usb_driver\android_winusb.inf" and add the following information:
;FOR ZEEN
%SingleAdbInterface% = USB_Install, USB\VID_03F0&PID_9F11&REV_0223&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_03F0&PID_9F11&MI_01
ADB currently will not recognize the device. I'm not sure what's messed up. Calling HP now to see about proper USB drivers.

Zeen
OK, HP says the USB drivers for the zeen come with the printer and even though I plugged in the first time it didn't work, the second time it did and Win 7 recognized it as a HP zeen. Ran the disk install in between.
That said ADB still has no idea. Fresh eclipse SDK install. Any thoughts on how to get ADB to recognize it?

Let's keep this thread alive. I got the drivers installed with your help. Can't get adb to see mine either. There has to be something we are missing. I think this device is similar to the pandigital novel so I have been reading over there. I will keep working.

Apparently, some firmwares seem to disable "adb" service...
Nice to hear someone else is out there trying. I found the following in a different post about the galaxy s, tried it with the Z4root, and while the command seems to take, it didn't work to get ADB. I tried it on a couple of different machines, let me know if it works for you. Also, when I called HP about the drivers they (at least the support techs) didn't know squat about android. Not helpful.
"Apparently, some firmwares seem to disable "adb" service on the Galaxy S.
So in case you run into this problem (adb unable to see the device) what you will need is to modify /default.prop on the SGS.
Here is what I had originally:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.debuggable=0
persist.service.adb.enable=0
To enable ADB on SGS
1. Run on the device: setprop persist.service.adb.enable 1 to temporarily switch it on.
2. pull /default.props with adb and modify the "ro.secure=0" and "persist.service.adb.enable=1"
2. mount -o remount,rw rootfs /
3. push modified default.props back to /
In more detail:
1. Root your device (see FAQ sticky post)
2. Install shell emulator on the device
3. In shell emulator, enable ADB (not sure if you need to run "su" before that):
setprop persist.service.adb.enable 1
4. Now, you should be able to connect to the device with ADB (temporarily). If not, make sure your udev rules (for Linux: /etc/udev/rules.d/51-android.rules) are smth like:
SUBSYSTEM=="usb|usb_device", ATTRS{idVendor}=="04e8", MODE="0666"
5. To make the change permanent:
adb pull /default.props .
(this will copy default props to local directory)
6. Modify the two properties as follows:
ro.secure=0
persist.service.adb.enable=1
7. Re-mount the root filesystem on the device in read-write mode (requires "su" before that):
mount -o remount,rw rootfs /
8. Now overwrite the /default.props on the device with modified one:
adb push default.props /default.props"

Okay, z4root did give me root access. I installed root explorer and terminal emulator. I am trying to find adb wireless so I can see if we can adb into the device using that. I think if I can i can install the market on the zeen

RootExplorer
Got a link to the RootExplorer APK? When temporarily rooted, I tried to install the market APK and got the finger. Did you perma-root or just do temporary?
I don't know anything about wireless ADB. What's the story with that? (admittedly, I'm a developer but getting up to speed on hacking the thing open).

I dont think I am aloud to post the root explorer apk. Wireless adb is just supposed to let you use adb without plugging anything in. Unfortunately, it says my device isnt rooted when trying to run it. Im gonna keep playing around with it.

Hey can you try to run adb over wifi. Just hook up your zeen to wifi and your pc and run adb like normal, but when you first run it type "adb connect xxx.xxx.xxx:5554
replace xxx with your zeen ip address. See if it lets you connect like that.

all the zeen but the adb drivers are in the zeen itself your just useing and uncapatable cable so it wont install usb driver and masstorage ones with out the proper cable, the adb drivers you will only get when useing sdk tool and has to be in debuging mode and pluse it has to have the correct cords like useing a samsung usb with a motorolla usb and sry i faild english and hate typeing so to lazy to do spell check like any one else will u get my giff the adb driver will install same time sdk will just its kinda tricky getting access to them and makething them work, a good way to test is plug in your w.e droid and go to your cpu cmd window, and type adb shell if it finds you droid then your golden but if not then bad cable or not in debuggin mode and have to have sdk installed and packages installed that come with it....

untile you can take the h p block of the android makret it wil never install or wont install properly more or less a complete rom will come out in like 3-5 months with the market on it and idk if the printing app will still be there but trust me you wont get it but there are 3 other alterative markets out there and 4shared.com has not let no one down............

if you want the android market on the hp tablet for the zeen or any other tablet that people are haveing a problem get anything and don't like yam or black market or any of that b.s g0od t0 4shared.kom and download a apk file with the name applanet and you should install the version 2.7.3 and i tried all the other version some will install and some wont but so far this one install and has 92 percent of the real adroid market and looks just like the market i found everything from root explorer to romanger and every app i seen in my droid i found on there and updates trust me if you want a g0od makret, well i just gave you the answer, n0w s0me one make 2.2 work on this thing, i have one to donate, [email protected] for some work to be done

Thanks for the tip on the Android Market! I installed it on mine and it works

How did you install market?
Sent from my Desire HD using XDA App

Anyone still working on the some development for this device? Thanks in advance!

There are various threads around xda with people trying bits and pieces. Slow progress though!

Okay thanks.

anthonbob said:
Anyone still working on the some development for this device? Thanks in advance!
Click to expand...
Click to collapse
Yes I will continue development after my exam will open in August an development thread to collect the knowledge of developers and not to sit weeks trying to get some information about the device and try to get adb working on Linux like I did
Gesendet von meinem Skate mit Tapatalk 4 Beta

Rooting Droid

I am trying to root my droid and i am getting stuck at this point
here is the time line of events
1. rooted successfully via easy root a really long time ago
2. after an ota update i receive an error when i attempt to reflash the phone or back up the rom anything that requires super user permissions fails saying "permission denied"
here i am now haha

After running RATC, you're not getting root UID (0), and you're staying in adb shell, so it's normal that adb devices command isn't working.
However, the real problem I see here is that RATC isn't working. Are you sure that you're using correct exploit - is RATC working on your FW version? Maybe you have to use psneuter...

sorry could you possibly put that in layman's terms im some what technical but im some what new to android stuff
UPDATE: nvm the above how do i figure the FW version ive looked in the about section of the phone but it doesnt seem to be there whats the best way to obtain the FW version?

I don't own Droid but same principles more or less should be same for all Android phones. So, to simplify it:
Basically, when you execute RATC (rage_against_the_cage) exploit, adb shell should disconnect and you should be thrown back to Windows' CMD prompt and adb shell should get root permissions. But in your case this isn't happening, adb doesn't restart and RATC isn't working.
Can you try with SuperOneClick v.1.6.3?

i was looking at that ill go ahead and try that

still a no go i attached some screen shots

Which Android version have you got? 1.6 or 2.1? Try with psneuter exploit.

i rooted with unRevocked3, on htc. very easy!!!!

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.

[Q] Updated to JB, and a few issues started happening...

I updated to Jellybean last night, and was in the process of rooting it and installing CWM again. I plug the pad into my computer, and realized that it's not being recognized by my computer. It's not even charging it! However, when I attach the wire to the wall adapter, it's charging. When I plug it into my comptuer, and if the pad's screen is on sleep, it autowakes it though.
I tried using someone else's cable and the same issue still occurs. Is there a way I can install CWM on my pad and root it without using adb commands on my computer? because that could be my only solution now. Unless, there's a way I can get it to recognize on my computer.
P.S. I had root+CWM installed when I was on ICS.

BUMP.
No one else has this issue? I'm 99% sure its my port, but how can i ota fastboot and flash cwm and root?

Caduceus46 said:
I updated to Jellybean last night, and was in the process of rooting it and installing CWM again. I plug the pad into my computer, and realized that it's not being recognized by my computer. It's not even charging it! However, when I attach the wire to the wall adapter, it's charging. When I plug it into my comptuer, and if the pad's screen is on sleep, it autowakes it though.
I tried using someone else's cable and the same issue still occurs. Is there a way I can install CWM on my pad and root it without using adb commands on my computer? because that could be my only solution now. Unless, there's a way I can get it to recognize on my computer.
P.S. I had root+CWM installed when I was on ICS.
Click to expand...
Click to collapse
It's a problem that some users have, and in my mind it was not resolved.
But If you want to install your recovery, you can do with TWRP recovery and Terminal Emulator app (play store)
You should search if you can make it by the same process for CWM, apparently no, cause you need fastboot.
Try this : [GUIDE] Help for flash more faster when you use Fastboot Line Command maybe you've got a problem with your fastboot. I don't know.
It's an easy installation of fastboot.

Caduceus46 said:
BUMP.
No one else has this issue? I'm 99% sure its my port, but how can i ota fastboot and flash cwm and root?
Click to expand...
Click to collapse
There is an option to allow ADB over network, but I haven't experimented with it. If you were adventurous, you could try it and let the community know what happens?
In the ROM I'm running (Baked Blackbean #5, Android 4.1.1 and based on CyanogenMOD) you can select this option by going to Settings-->Developer Options--->"ADB over network"
I just attempted to do this, and it worked rather flawlessly. Enable ADB over network, and it will give you the IP address of your device (in my case, 172.16.1.22:5555).
Then, follow the steps below. This assumes you have a rooted device. To do the terminal commands on my tablet, I use the "Terminal Emulator" program, free from the Market.
This is really simple.
First make sure you are rooted. Download a terminal emulator from market (there are lots that are free). Make sure that your android is connected to your WiFi and get the WiFi IP address. Open the terminal program and type:
su
setprop service.adb.tcp.port 5555
stop adbd
start adbd
Now go to your computer (assuming that you are using windows) create a shortcut on the desktop for "cmd.exe" (without the quotations).
Right click on the cmd shortcut and choose "Run as Administrator"
Change to your android-sdk-windows\tools folder
Type:
adb connect ***wifi.ip.address***:5555
(example: adb connect 192.168.0.105:5555)
adb should now say that you are connected. Note: if you are too fast to give the connect command it may fail. so try at least 2 times 5 seconds apart before you say this doesn't work.
Click to expand...
Click to collapse
To put the device back to USB, once you get it working (because ADB over network is NOT SECURE):
And you can disable it and return ADB to listening on USB with
setprop service.adb.tcp.port -1
stop adbd
start adbd
Click to expand...
Click to collapse
Got this information from: Here
I do want to note that all I did was verify that ADB is detected over wifi. When I type 'adb devices' on my Windows 7 PC, it detects the IP address of my tablet, which indicates the two devices are communicating correctly. I didn't try pushing/pulling files since I have no need for that, but hopefully this helps you.

I will try next week (cause I'm off @t work) this process, just for seen if it works well.
I don't need it, but it's interesting to know this.
The post which speak about this use is in N1 forum => here -> Post #22.
But it's more complete here : How can I connect to Android with ADB over TCP?
Apps which are automate this process :
- adbWireless - no updated since Sept 5 - 2010 - You need root access
- WiFi ADB - You need root access - Updated September 29, 2012
- ADB WiFi - Updated August 27, 2012 - You need root access
Well done @opethfan89 :good:

philos64 said:
I will try next week (cause I'm off @t work) this process, just for seen if it works well.
I don't need it, but it's interesting to know this.
The post which speak about this use is in N1 forum => here -> Post #22.
But it's more complete here : How can I connect to Android with ADB over TCP?
Apps which are automate this process :
- adbWireless - no updated since Sept 5 - 2010 - You need root access
- WiFi ADB - You need root access - Updated September 29, 2012
- ADB WiFi - Updated August 27, 2012 - You need root access
Well done @opethfan89 :good:
Click to expand...
Click to collapse
Thanks!!
Sent from my Transformer Pad TF300T using xda app-developers app

@opethfan89, ADB over network will probably not work for me because I don't have root anymore. Appreciate the help :good:
@Philos64, thank you for your post as well. I will try that sometime this week and let you know the results as well.

Oh wait, I don't think that method will work. I will need su permission to flash twrp. I don't have root anymore either

Caduceus46 said:
Oh wait, I don't think that method will work. I will need su permission to flash twrp. I don't have root anymore either
Click to expand...
Click to collapse
Perhaps I'm wrong, but you don't need root to be able to flash a custom recovery, since the recovery operates outside of the Android OS (and root only affects app permissions within the OS). You would just need fastboot to be able to flash the recovery. Do you have the proper drivers installed on your computer? Can you try different USB ports? Maybe a USB hub? Try it on a different computer to, just to process of eliminate any kinks between the tablet and the physical connection of the USB cable.
Sent from my Transformer Pad TF300T using xda app-developers app