Hi all,
I am very new XDA, just want to know if anyone has ideas of building ICS into glide?
I am a developer, but I have very rare experience on building android and put it into real device, it would be good if someone could let me help the development =)
Sent from my SAMSUNG-SGH-I927R using XDA App
I believe the first step would be to build a Gingerbread version as the driver can be extracted from the current ROM, I have set up a linux box for that and sync the CM7 repo. but as they do not support this device, the extract file does not work and I am stuck at this point,
I am not a specialist but am still trying to find a solution, not very easy though
CarpeNoctem said:
I believe the first step would be to build a Gingerbread version as the driver can be extracted from the current ROM, I have set up a linux box for that and sync the CM7 repo. but as they do not support this device, the extract file does not work and I am stuck at this point,
I am not a specialist but am still trying to find a solution, not very easy though
Click to expand...
Click to collapse
Actually, will the drivers for gingerbread compatible to ICS?
And will the official kernel source code work for AOSP build(gingerbread)?
I am thinking to reuse some of the source code.
Sent from my SAMSUNG-SGH-I927R using XDA App
joshua_tam said:
Actually, will the drivers for gingerbread compatible to ICS?
And will the official kernel source code work for AOSP build(gingerbread)?
I am thinking to reuse some of the source code.
Sent from my SAMSUNG-SGH-I927R using XDA App
Click to expand...
Click to collapse
If my understanding is correct the drivers may not work and the kernel should
But again I am no expert, just reading alot and trying to get it
EDIT: it is not really the drivers but the proprietary libraries
CarpeNoctem said:
If my understanding is correct the drivers may not work and the kernel should
But again I am no expert, just reading alot and trying to get it
EDIT: it is not really the drivers but the proprietary libraries
Click to expand...
Click to collapse
Yup, I remember that when I tried to build CM for G1, I have to extract those libraries.
I remember that it was just a script that use ADB to pull some files from the device, and it is straight forward if we want to write one,
but the question is, which file is needed?
joshua_tam said:
Yup, I remember that when I tried to build CM for G1, I have to extract those libraries.
I remember that it was just a script that use ADB to pull some files from the device, and it is straight forward if we want to write one,
but the question is, which file is needed?
Click to expand...
Click to collapse
indeed ! Thant is the question I am fighting with for more than a week now
Do you think we can take reference to some of the existing supported device (such as Galaxy S II) for the files?
I think the structure could be similar (same Touchwiz?), though they are not the same in hardware(glide use Tegra 2 but S II does not).
Sent from my SAMSUNG-SGH-I927R using XDA App
I started referencing the extract_files of galaxys2, and I found that some of the files are missing, I paste is just for you to look
those commented out are the missing files, I stopped searching at a line # Stopped Here
Code:
#!/bin/sh
# Copyright (C) 2010 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
DEVICE=galaxysglide
COMMON=c1-common
MANUFACTURER=samsung
mkdir -p ../../../vendor/$MANUFACTURER/$DEVICE/proprietary
mkdir -p ../../../vendor/$MANUFACTURER/$COMMON/proprietary
mkdir -p ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio
mkdir -p ../../../vendor/$MANUFACTURER/$COMMON/proprietary/cameradata
mkdir -p ../../../vendor/$MANUFACTURER/$COMMON/proprietary/egl
mkdir -p ../../../vendor/$MANUFACTURER/$COMMON/proprietary/firmware
mkdir -p ../../../vendor/$MANUFACTURER/$COMMON/proprietary/hw
mkdir -p ../../../vendor/$MANUFACTURER/$COMMON/proprietary/keychars
mkdir -p ../../../vendor/$MANUFACTURER/$COMMON/proprietary/wifi
mkdir -p ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging
# galaxysglide
# c1-common
adb pull /system/lib/libActionShot.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libActionShot.so
adb pull /system/lib/libakm.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libakm.so
adb pull /system/lib/libarccamera.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libarccamera.so
adb pull /system/lib/libcamera_client.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libcamera_client.so
adb pull /system/lib/libcameraservice.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libcameraservice.so
adb pull /system/lib/libcamera.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libcamera.so
adb pull /system/lib/libcaps.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libcaps.so
adb pull /system/lib/libEGL.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libEGL.so
adb pull /system/lib/libexif.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libexif.so
#adb pull /system/lib/libfimc.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libfimc.so
#adb pull /system/lib/libfimg.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libfimg.so
adb pull /system/lib/libGLESv1_CM.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libGLESv1_CM.so
adb pull /system/lib/libGLESv2.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libGLESv2.so
#adb pull /system/lib/libMali.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libMali.so
adb pull /system/lib/libOpenSLES.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libOpenSLES.so
adb pull /system/lib/libPanoraMax3.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libPanoraMax3.so
adb pull /system/lib/libril.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libril.so
#adb pull /system/lib/libs5pjpeg.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libs5pjpeg.so
adb pull /system/lib/libseccameraadaptor.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libseccameraadaptor.so
adb pull /system/lib/libseccamera.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libseccamera.so
adb pull /system/lib/libsecjpegarcsoft.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libsecjpegarcsoft.so
adb pull /system/lib/libsecjpegboard.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libsecjpegboard.so
adb pull /system/lib/libsecjpeginterface.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libsecjpeginterface.so
adb pull /system/lib/libsecril-client.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libsecril-client.so
adb pull /system/lib/libsec-ril.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libsec-ril.so
#adb pull /system/lib/libtvoutcec.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libtvoutcec.so
#adb pull /system/lib/libtvoutddc.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libtvoutddc.so
#adb pull /system/lib/libtvoutedid.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libtvoutedid.so
adb pull /system/lib/lib_tvoutengine.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/lib_tvoutengine.so
#adb pull /system/lib/libtvoutfimc.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libtvoutfimc.so
#adb pull /system/lib/libtvoutfimg.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libtvoutfimg.so
#adb pull /system/lib/libtvouthdmi.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libtvouthdmi.so
adb pull /system/lib/libtvout_jni.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libtvout_jni.so
adb pull /system/lib/libtvoutservice.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libtvoutservice.so
adb pull /system/lib/libtvout.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/libtvout.so
adb pull /system/bin/BCM4330B1_002.001.003.0419.0450.hcd ../../../vendor/$MANUFACTURER/$COMMON/proprietary/BCM4330B1_002.001.003.0419.0450.hcd
adb pull /system/bin/rild ../../../vendor/$MANUFACTURER/$COMMON/proprietary/rild
adb pull /system/bin/tvoutserver ../../../vendor/$MANUFACTURER/$COMMON/proprietary/tvoutserver
#adb pull /system/cameradata/datapattern_420sp.yuv ../../../vendor/$MANUFACTURER/$COMMON/proprietary/cameradata/datapattern_420sp.yuv
#adb pull /system/cameradata/datapattern_front_420sp.yuv ../../../vendor/$MANUFACTURER/$COMMON/proprietary/cameradata/datapattern_front_420sp.yuv
adb pull /system/lib/egl/libEGL_tegra.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/egl/libEGL_tegra.so
adb pull /system/lib/egl/libGLES_android.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/egl/libGLES_android.so
adb pull /system/lib/egl/libGLESv1_CM_tegra.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/egl/libGLESv1_CM_tegra.so
adb pull /system/lib/egl/libGLESv2_tegra.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/egl/libGLESv2_tegra.so
#adb pull /system/etc/firmware/qt602240.fw ../../../vendor/$MANUFACTURER/$COMMON/proprietary/firmware/qt602240.fw
#adb pull /system/etc/firmware/RS_M5LS_OB.bin ../../../vendor/$MANUFACTURER/$COMMON/proprietary/firmware/RS_M5LS_OB.bin
#adb pull /system/etc/firmware/RS_M5LS_OC.bin ../../../vendor/$MANUFACTURER/$COMMON/proprietary/firmware/RS_M5LS_OC.bin
#adb pull /system/etc/firmware/RS_M5LS_OE.bin ../../../vendor/$MANUFACTURER/$COMMON/proprietary/firmware/RS_M5LS_OE.bin
#adb pull /system/etc/firmware/RS_M5LS_TB.bin ../../../vendor/$MANUFACTURER/$COMMON/proprietary/firmware/RS_M5LS_TB.bin
#adb pull /system/vendor/firmware/mfc_fw.bin ../../../vendor/$MANUFACTURER/$COMMON/proprietary/firmware/mfc_fw.bin
#adb pull /system/lib/hw/acoustics.default.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/hw/acoustics.default.so
# Stopped here
adb pull /system/lib/hw/alsa.default.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/hw/alsa.default.so
adb pull /system/lib/hw/copybit.smdkv310.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/hw/copybit.GT-I9100.so
adb pull /system/lib/hw/vendor-gps.smdkv310.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/hw/gps.GT-I9100.so
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/hw/gralloc.default.so
adb pull /system/lib/hw/gralloc.smdkv310.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/hw/gralloc.GT-I9100.so
adb pull /system/usr/keychars/Broadcom_Bluetooth_HID.kcm.bin ../../../vendor/$MANUFACTURER/$COMMON/proprietary/keychars/Broadcom_Bluetooth_HID.kcm.bin
adb pull /system/usr/keychars/qwerty2.kcm.bin ../../../vendor/$MANUFACTURER/$COMMON/proprietary/keychars/qwerty2.kcm.bin
adb pull /system/usr/keychars/qwerty.kcm.bin ../../../vendor/$MANUFACTURER/$COMMON/proprietary/keychars/qwerty.kcm.bin
adb pull /system/usr/keychars/sec_key.kcm.bin ../../../vendor/$MANUFACTURER/$COMMON/proprietary/keychars/sec_key.kcm.bin
adb pull /system/usr/keychars/sec_touchkey.kcm.bin ../../../vendor/$MANUFACTURER/$COMMON/proprietary/keychars/sec_touchkey.kcm.bin
adb pull /system/vendor/firmware/bcm4330_aps.bin ../../../vendor/$MANUFACTURER/$COMMON/proprietary/wifi/bcm4330_aps.bin
adb pull /system/vendor/firmware/bcm4330_mfg.bin ../../../vendor/$MANUFACTURER/$COMMON/proprietary/wifi/bcm4330_mfg.bin
adb pull /system/vendor/firmware/bcm4330_sta.bin ../../../vendor/$MANUFACTURER/$COMMON/proprietary/wifi/bcm4330_sta.bin
adb pull /system/bin/alsa_amixer ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/alsa_amixer
adb pull /system/bin/alsa_aplay ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/alsa_aplay
adb pull /system/bin/alsa_ctl ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/alsa_ctl
adb pull /system/bin/alsa_ucm ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/alsa_ucm
adb pull /system/lib/libasound.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/libasound.so
adb pull /system/lib/libaudio.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/libaudio.so
adb pull /system/lib/libaudioeffect_jni.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/libaudioeffect_jni.so
adb pull /system/lib/libaudiohw_op.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/libaudiohw_op.so
adb pull /system/lib/libaudiohw_sf.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/libaudiohw_sf.so
adb pull /system/lib/libaudiopolicy.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/libaudiopolicy.so
adb pull /system/lib/liblvvefs.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/liblvvefs.so
adb pull /system/lib/libmediayamaha.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/libmediayamaha.so
adb pull /system/lib/libmediayamaha_jni.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/libmediayamaha_jni.so
adb pull /system/lib/libmediayamahaservice.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/libmediayamahaservice.so
adb pull /system/lib/libmediayamaha_tuning_jni.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/libmediayamaha_tuning_jni.so
adb pull /system/lib/libsamsungAcousticeq.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/libsamsungAcousticeq.so
adb pull /system/lib/lib_Samsung_Acoustic_Module_Llite.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/lib_Samsung_Acoustic_Module_Llite.so
adb pull /system/lib/lib_Samsung_Resampler.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/lib_Samsung_Resampler.so
adb pull /system/lib/libsamsungSoundbooster.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/libsamsungSoundbooster.so
adb pull /system/lib/lib_Samsung_Sound_Booster.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/lib_Samsung_Sound_Booster.so
adb pull /system/lib/libsoundalive.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/libsoundalive.so
adb pull /system/lib/libsoundpool.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/libsoundpool.so
adb pull /system/lib/libSR_AudioIn.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/libSR_AudioIn.so
adb pull /system/lib/libyamahasrc.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/audio/libyamahasrc.so
adb pull /system/bin/charging_mode ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/charging_mode
adb pull /system/bin/playlpm ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/playlpm
adb pull /system/lib/libQmageDecoder.so ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/libQmageDecoder.so
adb pull /system/media/battery_batteryerror.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_batteryerror.qmg
adb pull /system/media/battery_charging_5.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_5.qmg
adb pull /system/media/battery_charging_10.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_10.qmg
adb pull /system/media/battery_charging_15.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_15.qmg
adb pull /system/media/battery_charging_20.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_20.qmg
adb pull /system/media/battery_charging_25.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_25.qmg
adb pull /system/media/battery_charging_30.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_30.qmg
adb pull /system/media/battery_charging_35.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_35.qmg
adb pull /system/media/battery_charging_40.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_40.qmg
adb pull /system/media/battery_charging_45.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_45.qmg
adb pull /system/media/battery_charging_50.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_50.qmg
adb pull /system/media/battery_charging_55.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_55.qmg
adb pull /system/media/battery_charging_60.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_60.qmg
adb pull /system/media/battery_charging_65.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_65.qmg
adb pull /system/media/battery_charging_70.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_70.qmg
adb pull /system/media/battery_charging_75.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_75.qmg
adb pull /system/media/battery_charging_80.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_80.qmg
adb pull /system/media/battery_charging_85.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_85.qmg
adb pull /system/media/battery_charging_90.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_90.qmg
adb pull /system/media/battery_charging_95.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_95.qmg
adb pull /system/media/battery_charging_100.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_charging_100.qmg
adb pull /system/media/battery_error.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/battery_error.qmg
adb pull /system/media/chargingwarning.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/chargingwarning.qmg
adb pull /system/media/Disconnected.qmg ../../../vendor/$MANUFACTURER/$COMMON/proprietary/offmode_charging/Disconnected.qmg
Any progress on getting this phone to team hacksung?
Related
I followed this thread:
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/17766-how-full-root-evo-4g-mac-3.html
I went through all the steps and I'm exhausted since I spent like 2 hours doing this rooting process.
Now someone PLEASE tell me before I gouge my eyes out and skull **** myself if I achieved root.
Am I supposed to see a new icon indicating that I rooted? I don't see anything that says Super Agent but I followed those instructions to a T.
Right now I'm restoring my apps back on and I'm going to be very pissed if I'm thinking what I'm thinking. By the way I searched Google and someone on a forum said that if you cab download wireless tether from market then you're rooted. I was able to download it but does that really mean I am or did that just apply to that particular android phone?
open up a terminal or command line window.
run your adb program, with the following command line
mac
./adb shell
windows
adb shell
(or however you invoked it during the rooting process)
if your prompt looks like
Code:
#
you win.
else, you lose.
edit:
you'll only see superuser permissions if you install the app, not sure where to get it from as when i flash new roms they're preinstalled.
i suggest going on to flash a recovery image, so you can flash other ROMS with ease.
Thankfully I saw the # sign so that means I'm good. How do I go about starting to remove the apps I don't need anymore?
I have to research recovery roms because I don't have the patience to do it today.
just go flash a new ROM that has all the junk removed and save yourself the trouble.
i here there are programs that will do this for you as well, btu i dont know em off hand
gqstatus0685 said:
Thankfully I saw the # sign so that means I'm good. How do I go about starting to remove the apps I don't need anymore?
I have to research recovery roms because I don't have the patience to do it today.
Click to expand...
Click to collapse
1. Reboot in to recovery, so that /system will be writeable.
2. Launch an adb shell and navigate to /system/app:
Code:
./adb shell
# cd /system/app
3. Delete the programs you don't want by using the rm (remove) command:
Code:
# rm Flickr.apk
4. Reboot the device.
If you want to err on the side of caution, you can move the programs to your SD card, or your computer, so that you can restore them if needed:
Move to SD card:
Code:
./adb shell
# mkdir /sdcard/apkbackup
# mv /system/app/Flickr.apk /sdcard/apkbackup
Restore from SD card:
Code:
./adb shell
# mv /sdcrd/apkbackup/Flickr.apk /System/app
Backup to your computer:
Code:
./adb pull /system/app/Flickr.apk ~/Desktop/Flickr.apk
./adb shell
# rm /system/app/Flickr.apk
Restore from your computer:
Code:
./adb push ~/Desktop/Flickr.apk /system/app/Flickr.apk
Have fun!
cent
Need lil help with adb... reinstalled all drivers and reinstalled android sdk and install all tools/updates.. still giving me same no adb errors.. Im nand unlock with engineering bootloader.
wasd321 said:
Need lil help with adb... reinstalled all drivers and reinstalled android sdk and install all tools/updates.. still giving me same no adb errors.. Im nand unlock with engineering bootloader.
Click to expand...
Click to collapse
Your problem is that you're entering adb commands inside shell.
Once you see the # sign, after typing adb shell, that means that the adb commands will no longer work. So, your commands that begin with adb will NOT work if you see the # sign..
Also, for commands like adb devices and remount, they need to be run outside of shell or rather from your AndroidSDK\tools PATH directly.
This will work:
Code:
C:\android-sdk\tools:
adb remount
adb devices
adb shell
This won't work:
Code:
C:\android-sdk\tools:
# adb remount
# adb devices
# adb shell
Notice the # sign (this happens when you type adb shell), this means you're now root and now using shell -- you cannot run the adb commands inside shell, you have to instead use Linux commands, or specifically commands from BusyBox.
Just to clarify: Some commands can be sent outside of the shell, but they have to be preceded by "adb". For example:
Code:
adb reboot recovery
Others will only work inside of the shell, like ls, mv, cd, and so forth. Search for an adb command listing (you do have a Google phone, after all) and it may help to familiarize yourself with basic Linux terminal commands as well - a lot of them are accepted by adb.
SilverZero said:
Just to clarify: Some commands can be sent outside of the shell, but they have to be preceded by "adb". For example:
Code:
adb reboot recovery
Others will only work inside of the shell, like ls, mv, cd, and so forth. Search for an adb command listing (you do have a Google phone, after all) and it may help to familiarize yourself with basic Linux terminal commands as well - a lot of them are accepted by adb.
Click to expand...
Click to collapse
Yea, I was aware of this, just decided not to mention it. Thanks for pointing it out though.
I must be stupid or something cause I'm stuck on getting this to work. Can someone help me finalize setting up adb shell?
This is where I am so far:
I have installed phone driver and Android SDK. In SDK have installed packages API 2 through 8, usb driver package 3, etc.
What do I need to do when opening SDK manager? My phone is in tether mode but it just sits there. What am I not doing?
Thanks.
No love from the community on this one??
I'm a little confused.
When you set the evo to usb debugging and open a command prompt, cd to your sdk/tools dir, enter "adb devices" does your evo show up? It should be listed as a serial #.
Yes.....an HT### serial comes up which I am assuming is the phone. Guessing I can now just run the commands I need and it will communicate with the phone?
My confusion was that I was running the SDK Manager.exe and expecting it to find my phone and produce the adb shell.
Ok! You should be good to go. Just enter "adb shell" and you are set.
Good deal....thx.
Ok....thought I had this working. However, when in adb shell any commands I put in tells me "adb: not found".
What do I need to do from this point?
Let me clarify this.....
When I list devices it does find my phone. But, when issuing the adb shell command and trying to enter anything from the "#" prompt it always says "adb: not found".
I must be missing a step or something.
I'm kind of confused, mostly because I don't know what it is you're doing in a shell, but once you're in the shell and you get the # sign, there's no need to type in adb before your commands, for example, from the command line you would navigate to your tools folder. For me it would be
cd AndroidSDK/tools
./adb shell
Some jibber jabber about daemon starting
#
From then on I could run whatever command I planned on running in the shell like
echo 1 > /sys/class/leds/flashlight/brightness
And not
./adb echo 1 > /sys/class/leds/flashlight/brightness
CCallahan said:
Let me clarify this.....
When I list devices it does find my phone. But, when issuing the adb shell command and trying to enter anything from the "#" prompt it always says "adb: not found".
I must be missing a step or something.
Click to expand...
Click to collapse
What exactly are you trying to accomplish? Then we can determine what's going on.
I'm running Myn's RLS4 and am trying to change the power bar in the notifications.
Trying to follow the instructions in this link: http://forum.xda-developers.com/showthread.php?t=836721
OK. What part are you getting stuck at?
Edit: for this code, you do not need to be in the ADB shell:
Code:
adb remount
adb push widget.txt /system/customize/
adb reboot
You just need to cd to your tools folder of the SDK in your command prompt.
CCallahan said:
I'm running Myn's RLS4 and am trying to change the power bar in the notifications.
Trying to follow the instructions in this link: http://forum.xda-developers.com/showthread.php?t=836721
Click to expand...
Click to collapse
The commands he has given here
Code:
adb remount adb push widget.txt /system/customize/ adb reboot
do not require you to be in an adb shell, you just open up the command window do an adb remount then type in his commands one by one and male sure you have the .txt file that specifies what widgets you're going to use is in the tools folder of your AndroidSDK folder so that adb can locate and push it to its respective directory.
Ok...that worked.
Knew I was doing something wrong. Was trying to run those commands from the adb shell....makes sense that it could not find adb.
Thanks.
i have no adb shell at all can anyone help?
When someone says this
Code:
adb remount
adb push ApexLauncher.apk /system/app
What does that mean and how do i do it
slimpickins said:
When someone says this
Code:
adb remount
adb push ApexLauncher.apk /system/app
What does that mean and how do i do it
Click to expand...
Click to collapse
It means you need adb installed which is a package that is Dowloaded through the android sdk available on Google developers Website.
Adb is an interface tool for interacting with android via terminal.
Once these are setup you can run those commands.
Hi,
I am in the platform-tools folder but the push command won't work.
See screenshot.
Odd..
aassaf said:
Hi,
I am in the platform-tools folder but the push command won't work.
See screenshot.
Odd..
Click to expand...
Click to collapse
looking at your screenshot your entering a second > sign before adb and thats whats causing the problem. replicated your issue on my pc by adding a second > before adb
for example your setup says
c:/adt/sdk/platform-tools>>adb push llama_events /sdcard/llama/
it should say
c:/adt/sdk/platform-tools>adb push llama_events /sdcard/llama/
Run these commands 1 after another, copy and paste:
Code:
adb kill-server
adb connect 192.168.1.144
adb push keyboard.xml /sdcard/android/data/org.xbmc.xbmc/files/.xbmc/userdata/keymaps
adb push Llama /sdcard/Llama/
Many thanks
What an idiot i am :laugh:
roligov said:
Run these commands 1 after another, copy and paste:
Code:
adb kill-server
adb connect 192.168.1.144
adb push keyboard.xml /sdcard/android/data/org.xbmc.xbmc/files/.xbmc/userdata/keymaps
adb push Llama /sdcard/Llama/
Click to expand...
Click to collapse