Database Info

[Tools][Windows]

Hey all.
Have been doing Android dev for a short time, but Windows dev for a while.
I wrote myself two little .bat (batch) files for making a couple things quicker for me. These are crude little batches, nothing complicated here.
The first is LogcatBat, which is a little batch file for viewing logcat on your PC using the ADB binaries.
The second is ShellBat, which opens up an Android shell terminal on your PC connected to your phone through ADB as well.
Now, as stated before, THESE FILES ARE CRUDE. There isn't any support for them, and if you use them you do so at your OWN RISK. This is pretty simple stuff, but it can be used for HARM IF YOU'RE STUPID...
...So, don't be.
Now, you have to right click and save these files as .bat files - just clicking the links will generate the text of the batch commands. Also keep in mind these two files assume that your android directory is at C:\android-sdk-windows\tools. If they are not, email me, and tell me the location of your ADB folder so I can remake the file for you. Or, you can edit them yourself (this is Open Source, of course :wink:.
LogcatBat
ShellBat
My email: [email protected]

Well I guess that it will help a handful of noobs out there.
Most of the script (I'd say about 98%) is ascii art.

LOL I had to throw in a little "sumpin' sumpin'" more than what I used it for daily.
And it's TARGETED towards noobs, because I am one myself.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Also, those who download this PLEASE comment/reply to this to let me know how you like, dislike, or just what's up!

You might include instructions for customizing the directory structure, ex mine is c:\android and I have modded my path var to include the location of adb and fastboot.
Sorry, I should have continued reading. Still instructions and maybe how to set up path might be useful.

Cool to see more batch scripts, i love em as u can tell from my signature. They're so simple yet so powerful. Heres a tip to improve em, u can use errorlevel's to check if adb is in the $path. If its not in the path u cud perhaps ask for user-input to the directory where his/her sdk directory is and "cd" to that before executing commands.
Let me know if u need any help, im no pro but ive been working with them for a while now. Refer to my apk manager script, the top few lines are where i check if java/adb are installed on ur system.

Daneshm90 said:
Let me know if u need any help, im no pro but ive been working with them for a while now. Refer to my apk manager script, the top few lines are where i check if java/adb are installed on ur system.
Click to expand...
Click to collapse
Would you possibly wanna work with me on these? I mean, for my own end I don't care how they are, but if we could provide an actually nice work product that would be really cool!

mooch777 said:
Would you possibly wanna work with me on these? I mean, for my own end I don't care how they are, but if we could provide an actually nice work product that would be really cool!
Click to expand...
Click to collapse
Well i already include anything i can think of to apk manager. But if u propose an awesome idea that doesnt already exist, then yea for sure. Otherwise my help offer still exists.

Daneshm90 said:
Well i already include anything i can think of to apk manager. But if u propose an awesome idea that doesnt already exist, then yea for sure. Otherwise my help offer still exists.
Click to expand...
Click to collapse
Actually I used your script and found that I don't have Java installed. But when I installed the latest 1.6 JDK, they still can't detect it! May I know why?

JokerAce said:
Actually I used your script and found that I don't have Java installed. But when I installed the latest 1.6 JDK, they still can't detect it! May I know why?
Click to expand...
Click to collapse
If u can go to command prompt and type
java -version
if u see command not found, then java is not in ur path. If u do find it however, im intrigued as to why apk manager is complaining, in any case ignore the complaint.
Fyi, redirect any issues to its thread on the g1 forums, i dont wanna hijack this thread/easier to manage 1 thread instead of 2.

[Q] Trying to Root. Just aint happening

Hi guys,
Just got my SNS and have been lurking on here trying to figure out how to ROOT it. There are plenty of guides, and I was using this one
http://forum.xda-developers.com/showthread.php?t=895545
For some reason, and at risk of sounding like an idiiot, SDK doesnt have fastboot (or I cant find it) and I cant even use Command Prompt to execute any commands such as "ADB Devices". It also wont let me change the driver to Android Bootloader Interface in Device Manager.
I basically need to start from scratch and Im tearing my hair out trying to figure it out. Sorry about the FRAT
Cheers

Bertrum said:
Hi guys,
Just got my SNS and have been lurking on here trying to figure out how to ROOT it. There are plenty of guides, and I was using this one
http://forum.xda-developers.com/showthread.php?t=895545
For some reason, and at risk of sounding like an idiiot, SDK doesnt have fastboot (or I cant find it) and I cant even use Command Prompt to execute any commands such as "ADB Devices". It also wont let me change the driver to Android Bootloader Interface in Device Manager.
I basically need to start from scratch and Im tearing my hair out trying to figure it out. Sorry about the FRAT
Cheers
Click to expand...
Click to collapse
http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
I liked this guide. First time rooting.
On command prompt, you have to go to the Android\android-sdk\tools folder then execute those fastboot command.
Your command prompt probably says C:\Users\Your User Name.. [I have Windows 7]
Type 'cd..' (without ' ') until your line says C:\>
Then type the following cd Program Files\Android\android-sdk\tools
It could be Program Files (x86) not Program Files.. depends which bit you have. You can type those fastboot command from there.

Thanks for that info. Worked a treat right upto the part where I have to put the clockwork image on. command prompt keeps saying it cannot load it. Any ideas?

Bertrum said:
Thanks for that info. Worked a treat right upto the part where I have to put the clockwork image on. command prompt keeps saying it cannot load it. Any ideas?
Click to expand...
Click to collapse
Did you download ClockWorkMod img and paste it into android-sdk\tools folder? You can do that my opening My Computer folder -> C:\ -> Program Files -> Android -> android-sdk -> tools folder.
Then open command prompt and type like that. I just did the first line for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yours could be Program Files, not Program Files (x86) though. I downloaded 32-bit version accidentally and I didn't wanted to do it over.
After that you use your Nexus S to boot into bootloader [which the instruction says] and continue on.

thanks all sorted now. now to reinstall all my data as i didnt root straight away. ha!
Thanks for all your help.

Bertrum said:
thanks all sorted now. now to reinstall all my data as i didnt root straight away. ha!
Thanks for all your help.
Click to expand...
Click to collapse
I'm glad I helped. I had hard time rooting yesterday but it's all good now

I finished everything last night. All unlocked and rooted. Also running CM7 rc2 with the n14 kernel.
Its soo fast compared to my old blackberry and my friends galaxy.
Many thanks to the people who worked on the roms and kernels. Your knowledge astounds me.
Sent from my Nexus S using XDA Premium App

Help... Trying to flash the newest Tiamat kernal and Clockwork Mod

When I rooted, I used the one click method and worked like a charm. Now, I would like to learn how to flash the files via adb. I am a novice user of adb but have used it.
Right now, I am trying to flash the recovery.img file. Here is what I am getting:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have the recovery.img file in my /platform-tools folder. When I go to devices, I see my xoom listed and I do screen shots all the time using the ddms.bat file.
Can anyone tell my why my xoom will not let me flash files? I tried this a few weeks ago with the first Tiamat SDCard enabled kernal and it said the same thing, it wouldn't let me flash the file.
Thanks!

Your not actually changing direcotry into the correct directory. so when you call the fastboot command it's looking in the current directory of "c:\Users\Marc" instead.
cd \Program Files(x86)\Android\android-skd\platformtools
adb reboot bootloader
fastboot flash recovory recovory.img

Did you open the command line from the same folder you have the file you want to use? If not, open the folder you have recovery.img and the other files you will be using are in and hold the shift key on the keyboard and right click on the mouse. Then left click on "open command window here". Then run your adb commands.
Sent from my Xoom using XDA Premium App

Thanks guys, Ill try again.

ghoticov said:
When I rooted, I used the one click method and worked like a charm. Now, I would like to learn how to flash the files via adb. I am a novice user of adb but have used it.
Right now, I am trying to flash the recovery.img file. Here is what I am getting:
I have the recovery.img file in my /platform-tools folder. When I go to devices, I see my xoom listed and I do screen shots all the time using the ddms.bat file.
Can anyone tell my why my xoom will not let me flash files? I tried this a few weeks ago with the first Tiamat SDCard enabled kernal and it said the same thing, it wouldn't let me flash the file.
Thanks!
Click to expand...
Click to collapse
*FACEPALM*

jase33 said:
Did you open the command line from the same folder you have the file you want to use? If not, open the folder you have recovery.img and the other files you will be using are in and hold the shift key on the keyboard and right click on the mouse. Then left click on "open command window here". Then run your adb commands.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Does this work using Vista? I do not see the option to "open command window here".

Duh, nevermind... I figured it all out. I was putting a \ after platform-tools so it wasn't actually opening the folder where the recovery.img file was. Told you I was a novice. But I am getting it!

This is why one-clicks are the root of evil. If you would have done it manually from the start, you would have already known what to do here . Also since you posted this in development, i'm looking forward to the release, although i'm unsure what you are releasing at this point...

Ok people... Let's be mature here and not flame other users. This is supposed to be a community, not a war zone. If something is posted in the wrong section, or there's a post that breaks forum rules, drop me a pm or report the post. Thanks!
And this belongs in q and a... Since this is a question. Thread moved.
Please follow forum rules and post in the correct section.

damn, I must have missed some good flaming post! Lol

dont feel too bad
hehe I was doing the same thing for a 1/2 hour before I realized that the recovery.img wasn't even in the same folder...got that sorted out tho..

[MOD] ROOT [ACS] Skyrocket Easy Root - Windows/Mac/Linux

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Shabbypenguin and the Android Creative Syndicate
present to you
Easy Root 1.0​
This software is licensed under the WTFPL
/* This program is free software. It comes without any warranty, to
* the extent permitted by applicable law. You can redistribute it
* and/or modify it under the terms of the Do What The F*** You Want
* To Public License, Version 2, as published by Sam Hocevar. See
* http://sam.zoy.org/wtfpl/COPYING for more details. */
Click to expand...
Click to collapse
what this means is simple, you can do whatever you want with this software
Instructions are simple, this uses revolutionary's awesome zergrush exploit its just a slightly modified script from my transform-ultra AIO. anyways yall might be wondering why a sprint guy is here giving yall this, well its cuz my good buddy k0nane (the one currently working on removing ciq for yall) asked me to stop by the irc channel last night. we got some of the partitions mapped out and he told me that you guys can use zergRush so here ya have it
set usb debugging on (settings > applications > development > USB debugging)
Install teh drivers
plug in your phone and let teh drivers FULLY INSTALL
extract the entire root zip file (dont just pull what you want out of it, it doesnt work like that)
run the included batch file/sh file depending on your os
linux users i know youve got it handled but for you mac users that dont understand how to do anything more then dump money in apples pockets there is a readme in there
DOWNLOAD​
also to make things easier for editing i have included a nice lil script
in shell or terminal use this command
# remount rw
Click to expand...
Click to collapse
it will allow r/w access to /system
enjoy
version 2.0 will flash cwm for ya, just need to figure out a safe way to do it

Cool. Reserved.

fixed - was a permissions issue on my end.

fixed - was a permissions issue on my end.

please try re-running it again, if it says zerglings didnt leave anything interesting thats teh exploit failing

fixed - was a permissions issue on my end.

no adb is finding your phone, otherwise the exploit wouldnt run. its just odd that they arent leaving anything interesting. not sure why its not running the way it should, other people on this forum have said they used zergrush just fine, the reason why i posted this is so that you can have it done via script and have busybox and a remount script thrown in there.
here i had originally posted teh file with my old copy of zergrush, i had since updated teh zip with the latest from revolutionary. i reverted back to the old one try downloading it again and see where that gets ya

I ran it as administrator this time and it looks different, but I still get message about SU not found, even after rebooting phone.

ok well that time is because you didnt run it with adb.exe in teh folder

Hmm will def try this later tonight

Well, I'm sure I may be doing something wrong.
But I simply set my phone to usb-debugging and plugged in the usb cable.
Then extracted your zipped up folder and then right-click-run-as-administrator on root.bat.
ADB.exe is definitely in the same folder structure as root.bat.

hm well join the irc channel when youu get a chance we can work on this as bit more

If you are running windows vista or windows 7 and you are just right-clicking on the bat and running as administrator you are not running the adb.exe as an administrator. You should right-click on cmd.exe in the start menu, select run as administrator then navigate to the folder extracted. For instance if you saved the file in your users downloads folder then navigate to: x:\users\[user name]\downloads\Skyrocket-Easy-Root and then type root.bat and press enter. This will allow the root.bat to call adb.exe properly and will execute the process.
Hope this helps.

PlagueBoy said:
If you are running windows vista or windows 7 and you are just right-clicking on the bat and running as administrator you are not running the adb.exe as an administrator. You should right-click on cmd.exe in the start menu, select run as administrator then navigate to the folder extracted. For instance if you saved the file in your users downloads folder then navigate to: x:\users\[user name]\downloads\Skyrocket-Easy-Root and then type root.bat and press enter. This will allow the root.bat to call adb.exe properly and will execute the process.
Hope this helps.
Click to expand...
Click to collapse
Windows 7.
That did the trick, it worked great and I'm rooted. Thanks to both of you!
---------- Post added at 12:32 PM ---------- Previous post was at 12:31 PM ----------
Plague Boy... one post in four years and it got a "Thank You".
You're batting 100%!

Glad I could help. One post in four years yes, I signed up for this site a long time ago and then promptly joined the dark side by purchasing an iPhone about a week after that. After all these years I have wandered back and can hopefully be more of more use as I learn the Android OS.

Worked perfectly for me. Quick the lengthy root process (err rather how long it takes, its just 1 click lol), but mint!

cant get it to work says something about boomsh being denied

kornklown69 said:
cant get it to work says something about boomsh being denied
Click to expand...
Click to collapse
That's left over from when I was working with you, come by IRC later and I'll get you cleaned up.

k0nane said:
That's left over from when I was working with you, come by IRC later and I'll get you cleaned up.
Click to expand...
Click to collapse
Superoneclick root worked thanx k0nane
Sent from my SAMSUNG-SGH-I727 using xda premium

[FAQ] VanirAOSP Q&A & discussion Thread

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey guys,since VanirAOSP is the best ROM ever,i wanted to make a Discussion thread here,because the Development thread has low activity and we shouldn't fill it with spam.
WHAT TO DISCUSS HERE:
-Bugs
-Features
-Development
-Other Things related to Vanir
-The original development thread can be found here
Personally,i think that Vanir is pretty underrated here on Moto G section,and i think that more people could try it and say their thoughts,because i've tried many many ROM's through my history here on XDA,and i've never been so satisfied. The ROM is as it's title says; Clean,Fast and organized. But that's just me and my two cents, Try it yourself and say your thoughts here!
The bug posting tutorial is the post below,and connecting your phone through ADB is two posts below,if you need something else explained don't hesitate to ask!

Repost:::
[SIZE="+2"]How to report bugs, the proper way ![/SIZE]
http://therealmofu.com/wp/?p=644
Credit:: by TheRealMofu
Credits:
Indirect for his guide
FuzzyMeep Two for his Windows Logcat Tool
B][SIZE="+2"]These are the options for reporting a bug:[/SIZE]​[/B]
[SIZE="+1"]Section 1 | Logcat:[/SIZE]
This log should almost always be included just because it provides more info than just saying something doesn’t work. It will essentially tell you which apps are crashing and why and it also gives output of what they’re doing. (Your system is running through apps, the dialer, wireless radio’s, etc are all ran through apps.) so, if something is general, like a system force close, please just include a logcat.
How to get a logcat:
Well, this is REALLY simple, all you need to do is just get adb up and running (google how to do that, I don’t feel like writing a ‘how to use adb’ tutorial for everyone’s phone.) and then type
Code:
adb logcat
then you just right click, select, and paste to
http://pastebin.com/
http://logcat.us/
http://paste.ubuntu.com/
and provide the link in the thread/post.
It’s really that simple!
For Windows users i found an self explaining noob friendly program called Windows Logcat tool 4.0
[SIZE="+1"]Section 2 | Dmesg:[/SIZE]
This is getting into issues such as wifi not working, sleep of death, etc. Basically, things that make us go “OH F***” when we use our devices. Note: You will need adb access for this to work, same as logcat.
What this will do is get us live kernel output so we can know things like “What driver is the kernel loading {or not loading for that matter}” and similar things. This is linux, so kernel output is important if a hardware aspect isn’t working right.
How to get a dmesg:
This is simple as well, no matter what operating system you’re on (mac, windows, linux) just type
Code:
adb shell dmesg > dmesg.txt
and then it will have written the output to a .txt file in your current directory. Either paste the contents to the thread, or attach it to your post.
You can also get the dmesg by using terminal emulator. Instead though, you dont type adb shell, you need to also include it to somewhere you will be able to save it. Like /sdcard so, the command goes
Code:
dmesg > /sdcard/dmesg.txt
Just get it off your sdcard and get the contents to the developer!
[SIZE="+1"]Section 3 | last_kmsg:[/SIZE]
Ok, the last thing is last_kmsg. When android kernels crash, they right to last_kmsg so then you can find out what’s going on. This is usually for issues such as random reboots and other various kernel panic symptoms. A kernel panic happens when the kernel tries to do something it can’t. It doesn’t mean wrong permissions, it could just have errored out on something and died which can cause a few things. Anyway, developers REALLY need this if debugging a kernel because it gives us a viable way to see WHAT it’s trying to do instead of trying to guess what it is trying to do
How to get a last_kmsg:
This is super simple and the same on all phones no matter what, what you need is adb up and running (or terminal emulator) and either in adb shell, or terminal emulator just type
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
or you can do
Code:
adb shell cat /proc/last_kmsg > kmsg.txt
and that will write it to your current working directory from cmd.
And hhp_211 posted this in his thread,and i copied it from him,i hope he won't mind,so thanks @hhp_211

[SIZE="+2"]
Connecting your device through adb on Windows/Ubuntu:[/SIZE]​
[SIZE="+1"]Windows:[/SIZE]
On your PC you need to be logged in as an administrator for doin this and make sure that you activated “USB Debugging” in Settings/Developer Options on your phone !!!
Connect your phone with the USB cable to the PC and select MTP mode
Open the Windows command prompt, which you also can open through pressing Win + R on your keyboard
Now type:
Code:
cmd
Now change into the folder you installed adb, for example:
cd c:\adb
Now were we are in the correct folder, type:
Code:
adb
Now you see a lot of commands appering, and when done, type:
Code:
adb devices
and your phone (Device-ID) should be listed in there, that’s it
[SIZE="+1"]Ubuntu:[/SIZE]
Make sure that you activated “USB Debugging” in Settings/Developer Options on your phone !!!
Connect your phone with the USB cable to the PC and select MTP mode
In terminal type:
Code:
cd (TOOLS_PATH)/android-tools
Then issue the following:
Code:
./adb devices
That’s it
Again,thanks to @hhp_211

Reserved 3 to be shure.