Database Info

Need help

I rooted my cool with one click method and tried to flashed the latest tiamat kernel for SD card capabilities got as far as the and remount step and got to the step where you adb push the kernels system files and it didn't work it said file location doesn't exist now my WiFi doesn't work I'm sorry this is just one big sentence but I need help.
Sent from my PC36100 using XDA Premium App

Do you mean it can't find the files on your computer? Easiest fix is to copy all files in every subdirectory of the ZIP archive into one folder and run the adb commands from there.

My cmd is c:/users/(nam
Sent from my PC36100 using XDA Premium App

E)/ and I put the kernels system files there and adb pushed the file name and location and it still didn't work
Sent from my PC36100 using XDA Premium App

does your cmd window look anything like the attached file?

put single qoutes around your C:\ path like this 'C:\path\to\kernel\file'

When starting to type out a file name in the command prompt, pressing the TAB key will try to fill in the title. It ensures that you've got quotes around everything too if needed.
Like if I wanted to list the C:\Program Files folder, I'd type "dir C:\progr" and hit tab after going that far. It'll fill in what it can. Just keep typing to help it along as you press tab.

I copied and pasted what the instructions said about the kernel my CMD directory isn't c temp its c users (computer name)
Sent from my PC36100 using XDA Premium App

blackroseimmortal09 said:
I copied and pasted what the instructions said about the kernel my CMD directory isn't c temp its c users (computer name)
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
OK, let's try it this way. I packed you all the files of the Tiamat 1.3.1 into an archive that does not create subdirectories. Please follow the steps below:
connect the Xoom
create a directory on C: called "temp"
extract all files from the archive found here to c:\temp\
Start cmd (command prompt)
Simply copy and paste the next steps, line by line:
Code:
cd C:\temp\
adb shell
mkdir /data/media/sdcard2
exit
adb reboot bootloader
(wait until Motorola logo shows)
Code:
fastboot flash boot boot.img
fastboot reboot
(wait for reboot)
Code:
adb remount
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push vold.fstab /system/etc/vold.fstab
adb reboot
Please let me know if that works for ya!

Never mind root my xoom got updated with the latest tiamat kernel with SD card support thanks anyways
Sent from my PC36100 using XDA Premium App

[Tutorial] Building CyanogenMod for G2x

My other tutorial for building CM for Nexus One
Last tested on 8/8/2011
This tutorial is basically my Nexus One tutorial altered to support the G2x. This tutorial requires a basic to intermediate knowledge of linux terminal commands. First you will need to be running the latest CM nightly. Then you will need to install Ubuntu 11.04. This tutorial will work for if you are running Ubuntu in a virtual machine and if you installed it to your hard drive. I have tested this by installing it to my hard drive and in a virtual machine, but I have not tried it in Wubi but it should work. You need 11.04 64 bit.
How to install Ubuntu: https://help.ubuntu.com/community/Installation
After you have installed Ububtu, make sure that your OS is up to date. You can do that by running the Update Manager from the System>Administration menu. Once that is completed, go to Applications>Accessories and open Terminal.
Now you will be setting up your build environment.
Next lets open a terminal. Copy and paste the following into terminal.
(Copy from this tutorial with control+c and paste in terminal with control+shift+v)
Code:
sudo apt-get update && sudo apt-get install git-core gnupg flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev gitg qt3-dev-tools libqt3-mt-dev eclipse valgrind pngcrush schedtool
Code:
sudo add-apt-repository ppa:ferramroberto/java && sudo apt-get update && sudo apt-get install sun-java6-jdk && sudo update-java-alternatives -s java-6-sun
Now you will be installing ADB
Download the sdk from the android website (use the Linux download) http://developer.android.com/sdk/index.html
extract the sdk to your ~/ directory (home directory). So you should be able to go to a terminal and cd ~/AndroidSDK/platform-tools to access your platform-tools folder in your sdk. After that, update your android sdk by opening terminal and run:
Code:
~/AndroidSDK/tools/./android
Open the terminal, and type gedit .bashrc and at the top of the file, paste this (replacing user with your username)
Code:
#AndroidDev PATH
export PATH=${PATH}:/home/user/AndroidSDK/platform-tools
export PATH=${PATH}:/home/user/AndroidSDK/tools
This will make ADB, Fastboot and DDMS available from the terminal on next login.
Now, to make the device available to normal users, open a terminal and type
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
Then paste
Code:
SUBSYSTEMS == "usb", ATTRS {idVendor} == "18d1", ATTRS {idProduct} == "4E11", MODE = "0666"
SUBSYSTEMS == "usb", ATTRS {idVendor} == "18d1", ATTRS {idProduct} == "4e12", MODE = "0666"
SUBSYSTEMS == "usb", ATTRS {idVendor} == "0bb4", ATTRS {idProduct} == "0FFF", MODE = "0666"
SUBSYSTEM=="usb",ATTRS(idVendor)=="18d1",SYMLINK+="android_adb",MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666"
Save and exit.
Ensure that the rules are executable:
Code:
sudo chmod a+rx /etc/udev/rules.d/*
Then type
Code:
sudo restart udev
You should restart your computer (or virtual machine) right now to ensure that everything is running properly.
Note: idVendor may vary. Use lsusb from the terminal, look for your Android device and replace “0bb4″ with the first 4 characters after “ID”.
If ADB is still not working, read http://forum.xda-developers.com/showthread.php?t=533 and http://alan.lamielle.net/2010/01/22/nexus-one-usb-in-ubuntu-9-10
You should now have a fully working android build environment.
Now before you begin getting and building the source, make sure that you are on the latest CM7 nightly and have the latest gapps from Rom Manager.
Now to setup the CyanogenMod build environment and to build it
Enter the following lines in terminal:
Code:
cd ~/
mkdir -p ~/bin
mkdir -p ~/cm7
cd ~/bin
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
cd ~/
chmod a+x ~/bin/repo
PATH="$HOME/bin:$PATH"
PATH="$HOME/AndroidSDK/platform-tools:$PATH"
PATH="$HOME/AndroidSDK/tools:$PATH"
cd ~/cm7
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
Press enter and enter the information it asks for.
The next command will download all of the CM source. It will take at least a few hours or more depending on your internet speed.
Code:
repo sync -j16
After the sync, plug your phone in, and run adb devices and if your phone is listed, continue. Otherwise, go back and make sure you have properly installed adb and the drivers.
Plug your phone in, copy the following commands into terminal, and press enter.
Code:
cd ~/cm7/device/lge/p999/
./extract-files.sh
cd ~/cm7/vendor/cyanogen/
./get-rommanager
./get-google-files
now you your CM build environment is complete.
Warning: Building CM pushes your computer to the max your cpu can handle. Make sure that your computer can handle compiling CM. If It cannot, DO NOT DO THIS.
To build, just run(use this command every time you want to build CM):
**** Here is a new updated command to build CM****
Code:
cd ~/cm7 && make clean && repo sync -j6 && . build/envsetup.sh && brunch p999
If you come across any problems while syncing use repo sync -f -j6 -d and it will force sync and override any changes made to the source on your computer.
and it will make an update.zip in ~/cm7/out/target/product/p999/update-cm-7.1.0-RC1-G2x-signed.zip (or whatever the latest RC is)
Congratulations you have just compiled CyanogenMod for the G2x!
Possible causes if the build fails:
1. Make sure you followed the directions precisely.
2. Try all three of the build commands.
3. If you changed any of the code, make sure it has no errors. Open it up in eclipse and check for errors.
4. Search Google and XDA.
**If you are getting a problem with getting the gapps, it it because of the CM gapps mirror system.
1. download and install the latest gapps
2. plug your phone in and run:
Code:
~/cm7/vendor/cyanogen/./extract-google-files
Sources:
http://developer.android.com/sdk/index.html
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_passion
http://www.lineardroid.co.uk/2010/07/configure-build-environment/
http://www.lineardroid.co.uk/2010/04/how-to-set-up-adb-in-ubuntu/
http://forum.xda-developers.com/showthread.php?t=533090
http://alan.lamielle.net/2010/01/22/nexus-one-usb-in-ubuntu-9-10
http://forum.xda-developers.com/showthread.php?t=704561
Be sure to thank if this was helpful!

reserved...

reserved...

that's good. Thank you

Nice... Ive been always wondering how to do that... Time to start tonight
Any news if there is some kind of an online kitchen for the g2x that is not cm7 based?

Very nice. Thanks for updating your guide for the G2x.

OSError: [Errno 2] No such file or directory
Hey there. I'm going through your how to here and I came into an error pasted below. I'm very new to all this but am very eager learn. Can you shed some light on what is happening? Thanks a ton!
[email protected]:~/cm7$ repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
Traceback (most recent call last):
File "/home/dubntz/bin/repo", line 603, in <module>
main(sys.argv[1:])
File "/home/dubntz/bin/repo", line 570, in main
_Init(args)
File "/home/dubntz/bin/repo", line 184, in _Init
_CheckGitVersion()
File "/home/dubntz/bin/repo", line 213, in _CheckGitVersion
proc = subprocess.Popen(cmd, stdout=subprocess.PIPE)
File "/usr/lib/python2.7/subprocess.py", line 672, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1213, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
[email protected]:~/cm7$

Install git.

I followed all of your steps but am getting the adb not found or whatever error when trying to run adb devices, or any adb command for that matter. I tried as root, and as a normal user and nothing worked.
Anyone else have this issue?

*black*silva* said:
I followed all of your steps but am getting the adb not found or whatever error when trying to run adb devices, or any adb command for that matter. I tried as root, and as a normal user and nothing worked.
Anyone else have this issue?
Click to expand...
Click to collapse
First, make sure that you did downloaded and extracted the Linux version of the Android SDK. Second, verify that the path to the directory where the adb command is correct. Third, check if the adb command is indeed present in that directory. If it's not in platform-tools directory then you need to run the ./android command and update the SDK.
Sent from my LG-P999 using XDA App

joackie27 said:
First, make sure that you did downloaded and extracted the Linux version of the Android SDK. Second, verify that the path to the directory where the adb command is correct. Third, check if the adb command is indeed present in that directory. If it's not in platform-tools directory then you need to run the ./android command and update the SDK.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I downloaded and extracted my SDK to my home folder, and when i checked to see if the adb command was there it was not, so i am now getting everything i think i need from running the android command. Could it be because im on 32 bit? And it says you need 64? Or is that only to compile? I'd like to compile but i really just want ADB working.

*black*silva* said:
I downloaded and extracted my SDK to my home folder, and when i checked to see if the adb command was there it was not, so i am now getting everything i think i need from running the android command. Could it be because im on 32 bit? And it says you need 64? Or is that only to compile? I'd like to compile but i really just want ADB working.
Click to expand...
Click to collapse
I don't think it had to do with you being on a 32 bit. I think it had to do with the archive file not really having the adb command. You have to update the SDK first to get it. I may be wrong but if you want, you can inspect the contents of the archive file that you've downloaded to verify if it's really there. I've experienced the same thing that's why I was able to addressed your issues earlier.
If you want to compile then you need the 64 bit version as stated by the OP.
Sent from my LG-P999 using XDA App

i updated and installed all the things i needed and now ADB works perfect. Now i might try compiling. Thanks joackie27 for the help.

*black*silva* said:
i updated and installed all the things i needed and now ADB works perfect. Now i might try compiling. Thanks joackie27 for the help.
Click to expand...
Click to collapse
You're welcome! That's what the XDA community (help one another) is all about.
I wouldn't even try compiling not unless you've got the 64 bit version. I think it became a requirement with Gingerbread.
Sent from my LG-P999 using XDA App

joackie27 said:
You're welcome! That's what the XDA community (help one another) is all about.
I wouldn't even try compiling not unless you've got the 64 bit version. I think it became a requirement with Gingerbread.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
alright. thanks. i have already ran everything and all i have let to do is run the last code to compile it, so im going to and just gunna see what happens. if it works great. if not, i will always have chris to do it for me lol.
O and BTW for the code,
Code:
cd ~/cm7/device/htc/p999/
you will need to change it to
Code:
cd ~/cm7/device/lge/p999/
because HTC did not make the p999, LG did. but other than that everything has gone smooth.

*black*silva* said:
alright. thanks. i have already ran everything and all i have let to do is run the last code to compile it, so im going to and just gunna see what happens. if it works great. if not, i will always have chris to do it for me lol.
O and BTW for the code,
Code:
cd ~/cm7/device/htc/p999/
you will need to change it to
Code:
cd ~/cm7/device/lge/p999/
because HTC did not make the p999, LG did. but other than that everything has gone smooth.
Click to expand...
Click to collapse
Yeah I caught that one too. And after cloning the git repository for CM7, you can definitely see that there's no p999 directory under htc. And lastly, as you've pointed out p999 was from lge (LG Electronics).

joackie27 said:
Yeah I caught that one too. And after cloning the git repository for CM7, you can definitely see that there's no p999 directory under htc. And lastly, as you've pointed out p999 was from lge (LG Electronics).
Click to expand...
Click to collapse
yeah that how i got it to. And i dont really recommend using 32 bit because the guide says to use 64 but i already had 32 installed and didnt want to wipe that partition and reinstall 64 bit so i tried compiling on 32 bit and it worked fine. had no problems at all with compiling it or flashing it. But im just giving that information out for anyone who wants to compile and already has 32.

*black*silva* said:
yeah that how i got it to. And i dont really recommend using 32 bit because the guide says to use 64 but i already had 32 installed and didnt want to wipe that partition and reinstall 64 bit so i tried compiling on 32 bit and it worked fine. had no problems at all with compiling it or flashing it. But im just giving that information out for anyone who wants to compile and already has 32.
Click to expand...
Click to collapse
It worked fine on 32 bit for you? When i was getting all the files for the build environment it couldn't find some of the files while I was using 32bit like lib32ncursers or whatever, there were 4 of them.

brian6685 said:
It worked fine on 32 bit for you? When i was getting all the files for the build environment it couldn't find some of the files while I was using 32bit like lib32ncursers or whatever, there were 4 of them.
Click to expand...
Click to collapse
yup. everything worked perfectly fine for me. Although when i got my build environment i got them here...
http://forum.xda-developers.com/showthread.php?t=915435
I did not get any errors. And my ROM is running great!

*black*silva* said:
alright. thanks. i have already ran everything and all i have let to do is run the last code to compile it, so im going to and just gunna see what happens. if it works great. if not, i will always have chris to do it for me lol.
O and BTW for the code,
Code:
cd ~/cm7/device/htc/p999/
you will need to change it to
Code:
cd ~/cm7/device/lge/p999/
because HTC did not make the p999, LG did. but other than that everything has gone smooth.
Click to expand...
Click to collapse
Thanks. Changed it.

Root Help

I'm having trouble with step 4 of the rooting guide. The command prompt says:
data/local/gingerbreakBB: not found
Where should I place the files from the zip? Inside the platform-tools folder? Or inside a different folder?
Thanks in advance for helping a noob.

You need to put all of those files in the platform-tools folder or wherever advanced is located
Sent from my HTC Eva 4G using Tapatalk

Jocelyn said:
You need to put all of those files in the platform-tools folder or wherever advanced is located
Sent from my HTC Eva 4G using Tapatalk
Click to expand...
Click to collapse
All the files were in the platform-tools folder originally. Just making sure because it isn't working.

Cory1234 said:
All the files were in the platform-tools folder originally. Just making sure because it isn't working.
Click to expand...
Click to collapse
Did you change directories in Cprompt/terminal?
PS advanced above = adb silly spellchecker
Sent from my HTC Eva 4G using Tapatalk

Jocelyn said:
Did you change directories in Cprompt/terminal?
PS advanced above = adb silly spellchecker
Sent from my HTC Eva 4G using Tapatalk
Click to expand...
Click to collapse
Do you mean like to: C:\program files (x86)\android\android-sdk\platform-tools
??
I'm going to reinstall everything one more time.

Ok I got step 4 to go through, but I didn't get a number. When I try to redo step 4 it gives me this error: "cannot copy boomsh.: Permission denied.
What should I be looking for after step 4?

Cory1234 said:
Ok I got step 4 to go through, but I didn't get a number. When I try to redo step 4 it gives me this error: "cannot copy boomsh.: Permission denied.
What should I be looking for after step 4?
Click to expand...
Click to collapse
You need to remove them and start over
run these two lines then start from step 1
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
after step 4 if it successfully install you'll see a
[!] dance forever my only one
#
Also remember step 4 is actually a two lines process
run adb shell {Enter}
/data/local/gingerbreakBB {Enter}
Don't forget to open a DIFFERENT terminal window for steps 7-9

baseballfanz said:
You need to remove them and start over
run these two lines then start from step 1
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
after step 4 if it successfully install you'll see a
[!] dance forever my only one
#
Also remember step 4 is actually a two lines process
run adb shell {Enter}
/data/local/gingerbreakBB {Enter}
Don't forget to open a DIFFERENT terminal window for steps 7-9
Click to expand...
Click to collapse
Thanks. I got that info earlier by using google . Now I'm stuck on step 9. I am in a new terminal window. The output I receive after entering "md5sum cwm_blob_retransfer" is "md5sum is not recognized as an internal or external command, etc.
I also tried md5sums as another member commented on. Still no go.
This is starting to get frustrating..Jailbreaking was simple compared to this.

Anyone have any ideas?
Edit: Dur, Finally got it. Apparently, some of the files had write protection on them for some reason, which was causing all the problems. Thanks everyone for the help.

[GUIDE] Installing ADB/SDK and How to make a logcat

I'm doing this simple guide on how to achieve a logcat when an issue is received
It's very simple but some people on here don't know how to do one.
1. Download Android SDK from here:
Code:
http://developer.android.com/sdk/index.html
2. Extract Android SDK to any area
3. Once Android SDK is extracted, be sure to put the path and download Android SDK Tools:
Examples:
Windows
Open your start menu, right click on 'My Computer' and select 'Properties'
Once another window opens go to 'Advanced settings'
Followed by selecting 'Environmental Variables'
Look for PATH and enter the following:
Code:
C:\Android-sdk-windows; C:\Android-sdk-windows\platform-tools; C:\Android-sdk-windows\tools;
Now java will need to be installed
Go to the following link:
Code:
http://www.java.com/en/
Go into Android SDK folder and open 'SDK Manager.exe'
Only check 'Android SDK Tools' and Android SDK Platform-tools
Linux
Go into your Home folder and Press CTRL+H (This is done to show hidden folders and files)
Look for the file '.bashrc'
Open it and put the following or similar:
Code:
export PATH=$PATH:~/android/sdk
export PATH=$PATH:~/android/sdk/platform-tools
export PATH=$PATH:~/android/sdk/tools
You will need to add something for any devices to be recognized:
Open terminal and enter:
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
Enter the following in the file:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Now save and close the file, in terminal enter:
Code:
sudo chmod +x /etc/udev/rules.d/51-android.rules
Now you will need to install java
Open terminal and enter:
Code:
sudo add-apt-repository ppa:ferramroberto/java
sudo apt-get update
sudo apt-get install sun-java6-jdk sun-java6-jre sun-java6-plugin
Now that everything is installed
Open terminal either type:
Code:
android
OR, if that doesn't work
Code:
cd ~/android/sdk/tools
./android
4. How to do a logcat:
This is very simple as now you have installed Android SDK and ADB
First connect the device via USB to your computer
Be sure to have usb debugging enabled
To verify the device is connected type:
Code:
adb devices
Windows
Open Command Prompt
Enter the following (Yes there's a space in between the '>'):
Code:
adb logcat > logcat.txt
Linux
Open Terminal
Enter the following (Yes there's a space in between the '>'):
Code:
adb logcat > logcat.txt
*The logcat.txt is your logcat that you can copy and paste for developers
5. Now that you've created a logcat copy and paste it to:
http://pastebin.com/

Now if someone in any sensation development thread ask you how do create a logcat
Be sure to give them the link to this guide
Thanks

blahbl4hblah said:
Now if someone in any sensation development thread ask you how do create a logcat
Be sure to give them the link to this guide
Thanks
Click to expand...
Click to collapse
Should keep it in your sig too. Good work.

aNYthing24 said:
Should keep it in your sig too. Good work.
Click to expand...
Click to collapse
Good point
I'm tired of people reporting issues and there's no logcat
Now they have no excuse

Be sure to read step by step everyone

blahbl4hblah said:
Now you will need to install java
Open terminal and enter:
Code:
sudo add-apt-repository ppa:ferramroberto/java
sudo apt-get update
sudo apt-get install sun-java6-jdk sun-java6-jre sun-java6-plugin
Click to expand...
Click to collapse
Why not OpenJDK? The Android stuff works fine with it

TamCore said:
Why not OpenJDK? The Android stuff works fine with it
Click to expand...
Click to collapse
When it comes to just adb I don't really care for openjdk but when it comes to compiling a rom I don't want it near my pc
Sent from my HTC Sensation

When I write
adb logcat > logcat.txt
answer is:
Access is denied. Why?

Can you post a screen shot of what you are doing?

GhostXSeries said:
Can you post a screen shot of what you are doing?
Click to expand...
Click to collapse
[Q]First do "adb logcat" then do "adb logcat > logcat.txt" ?
......
and this "Access is denied" is disappear.
now I am waiting to finish "adb logcat" then I well do "adb logcat > logcat.txt".
If doesn't Work I will post a screen shot
---------- Post added at 01:07 PM ---------- Previous post was at 12:42 PM ----------
what is this? :|
https://www.dropbox.com/s/9ubqfwhevpfetqi/Loop.bmp

GhostXSeries said:
Can you post a screen shot of what you are doing?
Click to expand...
Click to collapse
May be, but I don't see the point since it's an EASY GUIDE.
Adb logcat part tells you before to open terminal.
Is that really hard to follow?
Sent from my Sensation

azoz123456 said:
When I write
adb logcat > logcat.txt
answer is:
Access is denied. Why?
Click to expand...
Click to collapse
Probably because you didn't enable us debugging in your phone
Sent from my Sensation

azoz123456 said:
[Q]First do "adb logcat" then do "adb logcat > logcat.txt" ?
......
and this "Access is denied" is disappear.
now I am waiting to finish "adb logcat" then I well do "adb logcat > logcat.txt".
If doesn't Work I will post a screen shot
---------- Post added at 01:07 PM ---------- Previous post was at 12:42 PM ----------
what is this? :|
https://www.dropbox.com/s/9ubqfwhevpfetqi/Loop.bmp
Click to expand...
Click to collapse
You sir don't follow instructions do you?
I said do adb logcat > logcat.txt for a reason. It's to save your logcat to a text file to give developers of your issues
Sent from my Sensation

blahbl4hblah said:
May be, but I don't see the point since it's an EASY GUIDE.
Adb logcat part tells you before to open terminal.
Is that really hard to follow?
Sent from my Sensation
Click to expand...
Click to collapse
sorry
This is what I did:Here
blahbl4hblah said:
Probably because you didn't enable us debugging in your phone
Sent from my Sensation
Click to expand...
Click to collapse
I do it bro.
blahbl4hblah said:
You sir don't follow instructions do you?
I said do adb logcat > logcat.txt for a reason. It's to save your logcat to a text file to give developers of your issues
Sent from my Sensation
Click to expand...
Click to collapse
I do every thing.
My phone is Incredible s.
S-OFF & Rooted $ I have recovery
now I am use this ROM:
[ROM] ★ TSM UltimateKangBang v3.5 Rev. C ★ ICS 4.0.3 • Sense 4.0a • Updated 12/06/12
and I need the adb logcat because I am going to learn how to port ROM HTC one V to my Inc s.
I am use this thread :
http://forum.xda-developers.com/showthread.php?t=1222746
and this:
http://forum.xda-developers.com/showthread.php?t=1563857(although
but the result is:
ROM successfully insulted when I do reboot stay in HTC page.
......................................................
[Q] When I port ROM from ONE v to my phone, must be use ROM ICS4.0 or I can use any ROM "2.3.5"?!
because I use RUU stock for my phone." When I do porting"
[Q] how time take to finsh " adb logcat"?!
I know my English is bad sorry
I hope you get the point

Oh now I see what you did wrong, you didn't put any spaces in between the '>'
Try it with the spaces
adb logcat > logcat.txt
Click to expand...
Click to collapse
Just so I'll be more specific and make this 'noob proof' I'll update it
I'm in a good mood XD

After I enter "adb logcat > logcat.txt" nothing happens. ADB recognizes my devices. I have debugging enabled. It does say adb server is out of date, if that means anything.
Running 8-10-2012 tamcore nightly on HTC sensation. with tamcore kernel. Boot loader is locked with S-off. if that means anything.

how do you do one without a computer
Sent from my HTC Sensation using xda app-developers app

melo563 said:
how do you do one without a computer
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
Look in the market. But those aren't as reliable
Sent from my Sensation

Paste bin says my log cat is too big. How can I fix this?
Sent from my HTC Sensation using xda premium

Hello, I'm having some trouble on win 7 . when i type in cmd adb devices i get adb is not recognized as a internal or external command. i installed the sdk manager in c\Android , installed java and i changed the environment variables to, path c:\Android-sdk-windows etc.... per the instructions. but i did something wrong since it's not working...i could use some help.... Thanks...

Problem in setting up build enviroment

I have used this guide to setup my build enviroment on hackintosh http://forum.xda-developers.com/showthread.php?t=2510898
but whenever i make a new repo folder by using "mkdir -p ~/.bin"
and following it "curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo"
i get a error that bin/repo folder is not found please help me i'm a noob i this

You've created a directory called ".bin" (hidden) yet you're curling in "bin" which you didn't create in the previous step.
I wouldn't have expected you to create ".bin" in the first step
Sent from my Nexus 5 using Tapatalk

yto5 said:
I have used this guide to setup my build enviroment on hackintosh http://forum.xda-developers.com/showthread.php?t=2510898
but whenever i make a new repo folder by using "mkdir -p ~/.bin"
and following it "curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo"
i get a error that bin/repo folder is not found please help me i'm a noob i this
Click to expand...
Click to collapse
rootSU said:
You've created a directory called ".bin" (hidden) yet you're curling in "bin" which you didn't create in the previous step.
I wouldn't have expected you to create ".bin" in the first step
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
In other words, what rootSU is saying is that you need to download (what you are "curling") the 'repo' binary into an existing folder.
This is basic GNU, actually.
On the first command, you're creating ~/.bin, but on the second, repo gets downloaded into ~/bin/, which doesn't exist.

beekay201 said:
In other words, what rootSU is saying is that you need to download (what you are "curling") the 'repo' binary into an existing folder.
This is basic GNU, actually.
On the first command, you're creating ~/.bin, but on the second, repo gets downloaded into ~/bin/, which doesn't exist.
Click to expand...
Click to collapse
Yep, that's exactly what I'm saying. Thanks.
".bin" is not "bin"