any one had this command from adb before????
/sbin/sh: exec: line 1: logcat: not found
I am facing the same to logcat from Recovery. Anyone can help?
most probably the system partition is not mounted, logcat doesn't included in the path or even doesn't exist
Wrong place
Sent from MARVEL
Probably you have not set the Android SDK directory in your PATH. Are you using Linux?
R u porting roms and the log came for porting?
yup, I got this same error ... Any suggestions to fix this??
Im in my first porting of a custom rom. And I'm stuck in a boot loop. Need to take a logcat now, but stuck with this error now.
Im on windows 8.1, have android sdk installed
Related
Hi there, i was trying to run Debian on my pro, but i cant install it! i try two methods, the Linux installer Beta 1.7 (say kernel dosnt have ext and loop support) and the SU terminal emulator way (cant chmod to 4755 any file, even using the su command - from here: http://www.talkandroid.com/android-forums/android-development/1091-install-debian-android.html )...
My pro is ROOTED with latest z4root, i even do a factory repair with pc companion...
Any advice???
Regards!
I tried this as well... no loop is no loop ( required for chroot type runs )
works on a Samsung i5700 I have at work tho...
thnx for the reply, so i can add loop and the ext thing? or we need a custom kernel? , what rom have the samsung?, in other hand i dont know why i cant chmod the files, even using root explorer! regards...
needs a new kernel yes.
i5700 is running samdroid cooked ( forget which version, but added multitouch )
damn :/
now why i cant chmod the files using su terminal emulator or root explorer? maybe is because my sdcard is formated in fat32, regards!
fat32 knows nothing about *nix style permissions, in a way though... all files on a fat32 are set 0777, but not really... heh
For what it's worth, I've just had Debian running in a chroot on my X10 Mini Pro, using the instructions at talkandroid.com, as mentioned by the original poster. Sorry, but as a new poster, I'm not allowed to link directly to those directions. This is with stock ROM, upgraded to Android 2.1, rooted with SuperOneClick.
A few modifications are necessary to make it work. I'm going to try to describe what I've done, but I am working backwards, so it's entirely possible that I'll leave something out and you could suffer disastrous consequences. So please be sure you back up all crucial data before proceeding, and be prepared to accept the possibility that your phone could be destroyed in the process.
First of all, the instructions tell you to run scripts from your SD card, which isn't going to work unless the card has a partition with a Linux-compatible file system. I suggest following the directions as far as step 4. Then replace the "bootdeb" file in the "debian" directory with the modified version attached to this post. Rename it "bootdeb". Then you will have to run the following commands manually, preferably using adb shell, but it can be done in a terminal on the phone. Either way, using the ash shell helps by providing command completion and history.
As root (su):
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
mkdir /data/local/mnt
cd /sdcard/debian
cp bootdeb /data/local/bin #note: you may need to mkdir /data/local/bin first
cd /data/local/bin/
chmod 4777 bootdeb
You should now be able to run the bootdeb script to start up Debian.
The installation file says, "Be sure to run /scripts/onetime.sh as root from the shell after your FIRST 'boot'." This will prompt you to set a root password.
At this point, the Debian installation is command line only and root only. The image file needs to be resized before much can be added.
The other files in the Debian directory may be useful, but they all need to be modified before they can be used.
This is only a beginning. I don't know that I'm likely to get very far with it, so anyone else who's inclined to jump in and make this work better is welcome to do so!
edit: correcting grammatical error
Just in case anyone else shares my obsession -- I mean interest in getting Debian to run on an X10 Mini Pro, I thought I should report my progress. Or lack thereof.
Actually, as I said in the previous post, command line Debian works, and that's a lot of power to have available. But it would be nice to get X working, despite the lack of video drivers.
There's a lot of information out there about setting up X with a VNC server on an Android phone, then running a VNC client to access the graphic environment. The source of most accounts seems to be a thread at the androidfanatic forums, with the title "Gnome, KDE, IceWM or LXDE Desktop on your Android!"
(Sorry, I'm still too new at this to be allowed to post links, so this is the only way I can indicate where to find the information.)
I've tried lots of variations on those directions, trying to adapt them to the X10 Mini Pro. And I've had a little success. I can get to the Icewm or LXDE desktop and run the terminal program, but I can't start any programs that use X. Invariably, I get this error:
Error: Can't open display: :1.0
I've run out of ideas, so I'm taking a break from the project. If anyone else is interested enough to try, good luck to you!
For what it's worth, the most recent and comprehensive account of running Debian with X on Android phones appears to be at lanrat.com, in the "android" directory, filename "debian".
@RobbH
Very interesting! I'm waiting a new 8gb card so that I try it! Should you come up with any new progress please report here
So as the title suggests whenever I run the crackin.bat file in order to prepare my legend to be downgraded, it always displays the
cr--rw---- 1 1001 2002 90 line instead of the needed crwxrwxrwx 1 1001 2002 90 line.
I have looked everywhere to find a solution to this problem yet no matter where I look, everybody seems to be able to fix this by just either turning off and on their phone or wiping it. But I have tried all of those and, I have also tried doing this step on a different computer and reinstalling the needed files yet to no avail.
So if anybody has a possible workaround please do share it so I can finally root my phone after many tedious hours.
Sorry for the noob question and many thanks in advanced to anyone who can help me.
Azaruc said:
- Get visionary+
- Temproot your legend with it
- Use commandline with adb on your pc to flash misc1-2.img.
type the following commands from the folder where you have adb;
Code:
adb shell
su
accept the notification on your phone if one comes up
and then in the command line type this;
Code:
/data/local/flash_image misc /data/local/misc1-2.img
That should be enough to make it possible to run the 1.31 RUU.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=11863394&postcount=2
Ahh, thank you. I had come across that before but i just didn't think that it would help! Silly me.
Ok, is there an IRC chat for the legend somewhere, im STILL getting this error. I can't find visionary+ anywhere where im sure enough its not going to mess up my phone, and i aparently am missing the files needed however none of the guides have downloads of everything i need.
PLEASE can someone help me? im so confused nothing is making sense. I get to copying files from DxDrx but that is nonexistant, what am i missing?
Ok, i got passed this step by doing these steps
1: download visonary here
http://forum.xda-developers.com/atta...3&d=1290501865
or here
http://content.modaco.net/dropzone/com.modaco.visionaryplus.r13.apk
or you can get it off the market
Then download hack4legend here http://www.multiupload.com/I3ZALKWB6A and unzip it somewhere (this is adb and the rooting tools)
2: install and open up visonary on your phone and do a temp root on your phone.
3: open up cmd and type in the following
cd "your hack4legend path here but with out the "" "
adb shell
su
4: after you do that on your computer you should see a notification on your phone come up, it might take a little. Accept it.
5: type this into the command promt
/data/local/flash_image misc /data/local/misc1-2.img
6: run the 1.31 RUU and your good.
Hope this helps
Unreal_628 said:
Ok, i got passed this step by doing these steps
5: type this into the command promt
/data/local/flash_image misc /data/local/misc1-2.img
Click to expand...
Click to collapse
/data/local/flash_image: not found
what am i doing wrong? i had to copy the contents of hack4legend to my adb folder so i have adb, is that it? do i have to change the drectory somewhere?
Mmm, if their is a platform tools sub folder in the android sdk try putting the hack 4 legend in there and re trying. It will either have to go in there or the tools sub folder in the android sdk.
And also make sure that when you use the cd command make sure to not just go to the android ask folder but into the platform - tools/tools depending on where you put your hack, try putting it in both and using different paths. Also you might wanna try updating the adb module "android sdk platform - tools revision 3" through the sdk manager.
And as allways make sure you have usb debugging on and have your phone connected to the computer through charge mode only.
Hi,
It take me a bit of time to find how to flash a kernel using fastboot on os X. Therefore I've decided to add a new post about that on XDA for those who want/need to use fastboot on mac os X.
Example given for a Sony Xperia ARC LT15i. This should work for any SE device but will need different vendor ID value for another Brand.
Installation
- Download and extract Android SDK (let's say on the Desktop for the rest of the explanation…)
- Add "Android SDK Platform-Tools" with android SDK Manager
- Download fastboot for mac here http://www.mediafire.com/?0nwuina1ydi
- extract it in android-sdk/platform-tools/
Configuration
Next you need to update the PATH for tools/ and platform-tools/ folder.
- Open Terminal app and type
Code:
nano ~/.bash_profile
- Add the following two lines and change the (username) with the name of your mac os X account name :
Code:
export PATH=${PATH}:/Users/(username)/Desktop/android-sdk/tools
export PATH=${PATH}:/Users/(username)/Desktop/android-sdk/platform-tools
- Save by typing Control+X and then Y
From now you can use fastboot command on your mac os X
The only thing to know is that you will need to use the "i" argument to specify the vendor id of the phone
Code:
./fastboot-mac -i 0xfce flash boot boot.img
Here is the official vendor IDs list http://developer.android.com/guide/developing/device.html#VendorIds but the SE one is not exactly the same and I don't know why
This help have been made using the following sources:
- http://blog.wapnet.nl/2011/05/setup-adb-and-fastboot-with-android-sdk-on-mac-osx/
- http://forum.xda-developers.com/showthread.php?t=1280516
Feel free to add specific vendor IDs
I've followed these instructions and entered the following command:
Code:
fastboot-mac -i 04E8 oem unlock
But I'm still met with the error...
Code:
-bash: fastboot-mac: command not found
What am I STILL doing wrong?? Any help is greatly appreciated!
as said you have not st the path correctly.. try that.. or try with running the command from the folder where you have the file fastboot-mac..
Sent from my HTC One V using Tapatalk 2
I tried the above and I got:
./fastboot-mac -i 0xfce flash boot boot.img
error: cannot load 'boot.img'
Any suggestions?
it doesnt work, waste of time...
It does work. If it isn't working for you its a user error or bad downloads. Instead of posting something like this where no one can help you since we don't know what the problem is, try posting what the results are when you type the commands and include the commands that you enter. THEN we could possibly help you.
Sent from my Inspire 4G
JellyTime R_29
@randomblame
Don't hesitate to say thanks
chmod
theandroidguy2012 said:
It does work. If it isn't working for you its a user error or bad downloads. Instead of posting something like this where no one can help you since we don't know what the problem is, try posting what the results are when you type the commands and include the commands that you enter. THEN we could possibly help you.
Sent from my Inspire 4G
JellyTime R_29
@randomblame
Don't hesitate to say thanks
Click to expand...
Click to collapse
i just tried this and it's worked:
Code:
chmod 777 fastboot-mac
./fastboot-mac command
make sure you are on current directory where fastboot-mac is located
it worked, thanks!
was doing fastboot reboot for like 5 mins.
You saved my day. SILLY MAC
Hi I am having nothing but troubles I don't suppose anyone could help? I just cannot seem to get fastboot working on my mac I tried installing andoir studio and the separate platform-tools folder. Nothing works. I tried your instructions and whenever I try any commands I always get command not found.
Tried this but my device is still not recognized in fastboot mode just says waiting for device even if I give vendor id also. I have kenzo
Hey guys, so I am having a very odd problem with adb push. I am a bit of a newb with this stuff, but I am trying to root my phone (Samsung Stratosphere), which has been kind of an undertaking so far. I am following the tutorial on androidcentral, but on the step where I need to execute "adb push su/system/bin" I encountered this error.
It just prints the man file, like I didn't even say 'push'. I have zero idea why this happens, since it doesn't happen with any other adb commands, just push. Can you guys help me out? I have no idea what I'm doing wrong, and the oddness of the error suggests to me that it's just something I don't know about because I haven't ever done this before.
I appreciate any suggestions you might have at this point.
NearlyNoon said:
Hey guys, so I am having a very odd problem with adb push. I am a bit of a newb with this stuff, but I am trying to root my phone (Samsung Stratosphere), which has been kind of an undertaking so far. I am following the tutorial on androidcentral, but on the step where I need to execute "adb push su/system/bin" I encountered this error.
It just prints the man file, like I didn't even say 'push'. I have zero idea why this happens, since it doesn't happen with any other adb commands, just push. Can you guys help me out? I have no idea what I'm doing wrong, and the oddness of the error suggests to me that it's just something I don't know about because I haven't ever done this before.
I appreciate any suggestions you might have at this point.
Click to expand...
Click to collapse
From what you mentioned its a syntax error for the ADB push command. You did:
Code:
adb push su/system/bin
When the correct syntax would be:
Code:
adb push su /system/bin
There should be a space in between su and the /system/bin path. Also make sure the su binary is located in the folder where you have ADB and Fastboot. The syntax for the ADB command adb push in general is:
Code:
adb push <file> <path you want to push file to on your device>
Again note the space in between the file parameter and path to push the file to your device parameter. Let me know if you still have questions I'll be happy to help.
Sent from my SCH-I535 using xda premium
Thanks so much! You were totally right, it was a syntax error.
okay so trying to build from source FFOS for the ZTE Open C and keep getting the same error even tried switching Ubuntu Distro to 14.04.1 from 14.10 tried google and didnt come up with much of anything on the subject short of many people experiance this issue it seems but nobody gets it resolved and if they do they dont post on how they did it
Pulling "trace_util"
cp: cannot stat ‘../../../backup-flame/system/bin/trace_util’: No such file or directory
Failed to pull trace_util. Giving up.
> Build failed! <
above is the error i get any help is appreciated
Franzferdinan51 said:
okay so trying to build from source FFOS for the ZTE Open C and keep getting the same error even tried switching Ubuntu Distro to 14.04.1 from 14.10 tried google and didnt come up with much of anything on the subject short of many people experiance this issue it seems but nobody gets it resolved and if they do they dont post on how they did it
Pulling "trace_util"
cp: cannot stat ‘../../../backup-flame/system/bin/trace_util’: No such file or directory
Failed to pull trace_util. Giving up.
> Build failed! <
above is the error i get any help is appreciated
Click to expand...
Click to collapse
Follow up to this ive did a little searching my self and included in the init.target.rc is a NFC area that seems to be the "Root" of the problem but unfortunatly thats all the information ive come across so please anyone that has information how to bypass this error or fix it , i whould be very greatful
fixxed but still issues
Franzferdinan51 said:
Follow up to this ive did a little searching my self and included in the init.target.rc is a NFC area that seems to be the "Root" of the problem but unfortunatly thats all the information ive come across so please anyone that has information how to bypass this error or fix it , i whould be very greatful
Click to expand...
Click to collapse
okay so for those of you who ever run into this issue this is how to bypass unforunatly after flashing i still run into errors on ./flash.sh fails to erase userdata but well start from the top and leave that for others since im almost positive that error is due to me not doing something correct
okay so basically its pretty simple go too the link and copy openc.xml at the link below and attached for easy access
https://bugzilla.mozilla.org/attachment.cgi?id=8429932
https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C
then follow the directions listed but to keep it simple for those of you whom dont want to look to far
Clean up the B2G directory, removing the unneeded directories:
rm -rf objdir-gecko/ out/ backup-flame/
Now configure Firefox OS with the following command: (Note that the path cannot contain spaces, otherwise it won't work).
./config.sh flame /PATH/TO/openc.xml
You can then build the Gecko component and Flash it to your phone using the following:
./build.sh gecko
./flash.sh gecko
You should now upgrade Gaia as well, so the upgraded version of Gecko works with the version of Gaia on the device:
cd gaia
make reset-gaia
and thats how i fixxed it unfortunatly like i said when i got to ./flash.sh the whole build it fails at user data
but once again pretty sure thats only me if anyone has information on this let me know please
all credit from this goes to mozilla i just decided to post it in an easy location for everyone who runs into this
thank you mozilla developers