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.

[APP] VM Heap Tool 2.4.1 [28/02/12]

Description
I wrote a small application to allow easily changing the VM heap size (no more adb pull, edit, adb push). People on CM ROMs may be familiar with a similar option, but here is a little tool for those who are not running CM. As it modifies a variable which can affect the stability of the system, be careful with how you use it More about the VM heap size is written in the application itself. And of course, if I made any mistakes or if something is incorrect please correct me.
Requirements
root
system write
busybox (1.17.x recommended)
Appearing In
Japanese Jellyfish (ZTE Blade/Orange San Francisco)
If you wish to bundle this application in your firmware feel free to, but let me know if you do and please link back to this page
Download (Android Market):
{
"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"
}
Translating VM Heap Tool
English files which can be translated have been attached (txt files), and the following fields which I will mention do not need to be translated. Once you translate something you may just attach the files in your post or add them in code tags. Of course please mention the language that you translated it to so I can appropriately add it to the application and update.
Do not translate: heapSizeUnit, aboutHeap, defaultHeap, currentHeap, version, thread, heapSizeValues. These just hold key values which should not be translated. Also please don't translate "RPLACE" inside the texts, as this is replaced inside the application on run-time.
Values are stored as
Code:
<string name="aboutHeapTitle">What is the heap?</string>
where the string's name is clearly defined, "aboutHeapTitle", and the value which should be translated is inside the <> and </> tags. Values which are used in similar situations will have a common prefix, for example:
"progress..." - used on a progress dialog to display the message
"toast..." - the little grey messages that you get at the bottom of your screen and with which you can't interact
"dialog..." - used as the title on a dialog box
and so on...
Thank you to all those who are willing to help, your contributions will be noted

great app, wont have to manually erstart on droid inc. wont restart when pushing the button.

ACD168 said:
great app, wont have to manually erstart on droid inc. wont restart when pushing the button.
Click to expand...
Click to collapse
Thanks, so the Incredible has the same problem as the Desire then... If you install ROM Manager it will restart. I'm afraid that has something to do with superuser and how the phone is rooted (correct me if I'm wrong), so some devices will restart while others will not. Sadly Google doesn't allow applications to restart the device, so it has to be done in a roundabout way which may not always work...

Awesome, now everyone can break apps by lowering the heap below the expected 24 megs!

khaytsus said:
Awesome, now everyone can break apps by lowering the heap below the expected 24 megs!
Click to expand...
Click to collapse
Yes, but I hope that most people will be smarter and try to use something like 32

The "apply" and "quit" box cover the "new heap size" box on hTC Hero

skymera said:
The "apply" and "quit" box cover the "new heap size" box on hTC Hero
Click to expand...
Click to collapse
OK, thanks for letting me know. I'll see what I can do about it, but for now you can use your trackpad (or w/e it's called) to move the focus on the button and press it.

skymera said:
The "apply" and "quit" box cover the "new heap size" box on hTC Hero
Click to expand...
Click to collapse
Should be fixed now with version 1.1, as well as support for Android 1.6 and above. Apologies that it took so long.
Icon help, anyone...?

Very nicely done!!!
Thanx!!!

The app is force closing on startup on a rooted orange San Francisco (ZTE-Blade) with stock rom.
Andy.

g1dtf said:
The app is force closing on startup on a rooted orange San Francisco (ZTE-Blade) with stock rom.
Andy.
Click to expand...
Click to collapse
Do any other rooted apps crash, such as Root Explorer, ROM Manager, etc?

Rom Manager and System App Remover both run ok, not got Root Explorer so can't try that.
Andy.

martino2k6 said:
Do any other rooted apps crash, such as Root Explorer, ROM Manager, etc?
Click to expand...
Click to collapse
Forced close for me to on ZTE-Blade Stock/Root.

What happens if you write the following two commands in a terminal emulator or adb?
Code:
ls /system/bin/su
ls /system/xbin/su

If you have rooted the san fran with stock rom and this will not work, root again. Worked for me no probs, even if it says you are rooted. Just root again. It appears that when the San Fran is turned off then on, it unroots (with original rom" Well, that is what I have found after testing. I have stock rom rooted and have picked out all the Orange "tat"
Hope that helps.

System Write Required
Just tried running the app, but ran into an error: "System write required". I have root, adb is installed and recognize Android is read only by default, so I assume that I have to change permissions to include write?

Guilden_NL said:
Just tried running the app, but ran into an error: "System write required". I have root, adb is installed and recognize Android is read only by default, so I assume that I have to change permissions to include write?
Click to expand...
Click to collapse
You can't change that without using a rooting method which unlocks NAND on your device. The application already remounted the partition to write, but wasn't able to write to it because you most likely don't have NAND unlocked.

martino2k6 said:
You can't change that without using a rooting method which unlocks NAND on your device. The application already remounted the partition to write, but wasn't able to write to it because you most likely don't have NAND unlocked.
Click to expand...
Click to collapse
Well guess us Slide owners can't use this until we have s-off. No system r/w for us yet

No love on the MyTouch 3G getting NAND unlocked for Write. Ah well, the MT3G is truly a dog so I am not going to spend anymore time with it. It'll do the job for now, and I use the Nexus One as my main phone anyway.
Thanks for the tip though! At least I know where the issue is on this device.

kapslock4 said:
If you have rooted the san fran with stock rom and this will not work, root again. Worked for me no probs, even if it says you are rooted. Just root again. It appears that when the San Fran is turned off then on, it unroots (with original rom" Well, that is what I have found after testing. I have stock rom rooted and have picked out all the Orange "tat"
Hope that helps.
Click to expand...
Click to collapse
Didn't work but used clockwork and installed custom ROM and worked
Sent from my BladeVillain using XDA App

[APP][4.4][ROOT] SDFix: Modify device permissions to allow apps to write to MicroSD

ROOT ACCESS IS REQUIRED.
I've written a simple app which modifies KitKat devices to allow user-installed applications to write to the MicroSD card on devices with two storage locations.
Background information on the underlying problem is available here: https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn Please ensure you understand the problem and that your device has it before installing this app. This app is quite useless if your device doesn't suffer this issue.
[[[[ THIS IS A BETA RELEASE. WHILE I HAVE TESTED THIS ON MULTIPLE DEVICES MANY TIMES, PLEASE RESTRICT YOUR USE OF THIS APP TO DEVICES YOU HAVE THE ABILITY TO REFLASH FROM SCRATCH. I do not expect this to occur, but this is release #1 of this app, and it modifies a configuration file as root. That said, my test devices still work even when I deliberately corrupted and deleted the target file in testing. ]]]]
This app is entirely free. It doesn't have any ads, (but it does have a few Play Store links on its final screen to my other free apps).
Screenshots:
{
"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"
}
It will be going on the Play Store pending your feedback, but I wanted to post it here first. Please let me know if you encounter any issues.
How it works: The /system/etc/permissions/platform.xml is modified to specify that all applications which have the WRITE_EXTERNAL_STORAGE permission are registered as members of the Android UNIX group "media_rw". Membership in this group is necessary to write to the MicroSD card.
In Android 4.3, most all devices granted access to the media_rw group to apps. In Android 4.4, they do not. This app simply restores the old behavior. From what I've observed this method (granting permission via platform.xml), also appears to be the preferred means of restoring SD card access on XDA and elsewhere.
This app is designed to abort if it sees absolutely anything that it does not expect. Please let me know if the app does not work for you, and what type of device/ROM/etc you're using. If the modification is unnecessary (due to media_rw access being already present) this app will make no modification.
The original platform.xml will be backed up in /system/etc/permissions as "platform.xml.original-pre-sdfix" (unless that file already exists).
Download
Play Store: https://play.google.com/store/apps/details?id=nextapp.sdfix
Direct download: http://android.nextapp.com/sdfix/r7/SDFix_r7.apk
The installed app is named "NextApp SDFix".

(Reserved)

Awesome!! Will try, hope it will work
Edit:
Sorry but how can i test it?
When downloading something from dolphin and next -browser it doesnt show sdcard1
Have a break, Have a KitKat (powered Samsung Galaxy S²)

erdal67 said:
Awesome!! Will try, hope it will work
Edit:
Sorry but how can i test it?
When downloading something from dolphin and next -browser it doesnt show sdcard1
Have a break, Have a KitKat (powered Samsung Galaxy S²)
Click to expand...
Click to collapse
Most ROMs won't have this problem, it 's generally only an issue with factory firmware on KitKat (e.g. TouchWiz updates to KitKat). What ROM are you running?
The free version of FX File Explorer (links in my signature) should show both media card and internal storage if everything works, and you should be able to create a new folder under the "media card" catalog. If MicroSD access if prevented, attempting to create a new folder under "media card" will fail.

Got the issue on my TabPro 8.4, pending for maintenance so can't root yet, but really great thanks for saving the day.
Sent from my SM-T320 using xda app-developers app

Thanks, all good on SM9005 stock Kit Kat

Now available on the Play Store: https://play.google.com/store/apps/details?id=nextapp.sdfix

Thanks for this free app.
I'm going to visit your other apps.

Nice work !!
Nice work !! Working on my S4 I337M

Thank you for your app, but you should modify it to clearly state that the device requires a reboot for the changes to take affect ( apop up or something because nobody will read the text after "Completed"), you can also make a button to reboot it directly.
That's my input. Thank you again.

Does anyone has the original platform.xml file for i9505..... I edited it but kept no backup.....

Congrats on your front page story!
Fix Your SDCard Issue On KitKat http://www.xda-developers.com/android/fix-your-sdcard-issue-on-kitkat/

Thanks ,I'm trying now

tliebeck said:
I've written a simple app which modifies KitKat devices to allow user-installed applications to write to the MicroSD card on devices with two storage locations.
Click to expand...
Click to collapse
Thanks!

Cool app. Thanks.

Nice!!!
Thanks for this good job

Worked perfectly, thank you!!
Sent from my SM-N900T using Tapatalk

On stock Note 3 KitKat rom I have a crash when the please wait text pops up. Tell me if you need some kinda logs. Just tell me where they are and I will post them.
Okey I found the cause... I had edited the file and I deleted them and all was fixed. Sorry!

Since this requires root access I assume it will not work with AT&T 4.4.2 1337 NB1 builds? :crying: or did I miss a root process for that build? Thanks

hene193 said:
On stock Note 3 KitKat rom I have a crash when the please wait text pops up. Tell me if you need some kinda logs. Just tell me where they are and I will post them.
Okey I found the cause... I had edited the file and I deleted them and all was fixed. Sorry!
Click to expand...
Click to collapse
If you can make it crash, would greatly appreciate a logcat. Either just do "adb logcat > log.txt" and send me the output, or use a logcat app from the Play Store. Definitely don't want it to crash/force close under any circumstance, it's supposed to be friendlier than that.
The critical section of the logcat data should contain "nextapp.sdfix" and have a stack trace in it.
A stack trace looks like this:
Code:
java.lang.IllegalArgumentException: Invalid code point: -2147482938
at java.lang.Character.checkValidCodePoint(Character.java:1591)
at java.lang.Character.toChars(Character.java:2056)
at java.lang.String.<init>(String.java:537)
at com.android.inputmethod.latin.RichInputConnection.sendKeyEvent(RichInputConnection.java:392)
at
Thanks for the report, but don't tear your phone apart trying to reproduce it.

[root] chuwi v10hd 3g

Hello ,
I find a way to root this very good tablet , the "CHUWI V10HD 3G 64GO" dual boot windows 8.1/android 4.4.2 and 4.4.4.
I have followed this website : http://tablette-chinoise.net/rooter-toutes-les-tablette-intel-x86-avec-supersu-t7014
Frist you need to download the rooting kit : http://ul.to/71jrzvgy
and the intel adb driver : IntelAndroidDrvSetup1.9.0.zip
On your computer ,unzip the "IntelAndroidDrvSetup1.9.0.zip" and run the .exe to install the driver
connect your tablet to your computer , and boot the tablet on android
On android ,activate the "Usb debug mode" from the developper menu
On your computer unzip the "Root-tablette-chinoise.net.rar" and launch the "3 Root-tablette-chinoise.net.bat"
follow the instrunction on your screen , and yeah it's done !!:highfive:
hope it helps.
mirrors:
Root-tablette-chinoise.net.rar
http://uptobox.com/egez2zpy2lls
IntelAndroidDrvSetup1.9.0.zip
http://uptobox.com/d3mmycfutzzt

funregis said:
Hello ,
I find a way to root this very good tablet , the "CHUWI V10HD 3G 64GO" dual boot windows 8.1/android 4.4.2 and 4.4.4.
I have followed this website : http://tablette-chinoise.net/rooter-toutes-les-tablette-intel-x86-avec-supersu-t7014
Frist you need to download the rooting kit : Root-tablette-chinoise.net.rar
and the intel adb driver : IntelAndroidDrvSetup1.9.0.zip
On your computer ,unzip the "IntelAndroidDrvSetup1.9.0.zip" and run the .exe to install the driver
connect your tablet to your computer , and boot the tablet on android
On your computer unzip the "Root-tablette-chinoise.net.rar" and launch the "3 Root-tablette-chinoise.net.bat"
follow the instrunction on your screen , and yeah it's done !!:highfive:
hope it helps.
Click to expand...
Click to collapse
can you please upload the rooting kit and adb drivers to xda servers or mediafire or mega. uploaded.to is not the most convienient. have to wait 3 hours to get the next filr

suspect008 said:
can you please upload the rooting kit and adb drivers to xda servers or mediafire or mega. uploaded.to is not the most convienient. have to wait 3 hours to get the next filr
Click to expand...
Click to collapse
I have added uptobox

funregis said:
I have added uptobox
Click to expand...
Click to collapse
thak you very much for fast action. hope to be in touch. any issues so far with the device? I only had it for 2 days but could not try it.

It's working fine. The battery is the only weak point.

funregis said:
It's working fine. The battery is the only weak point.
Click to expand...
Click to collapse
Yep noticed that, but its expected running a x86 processor and powerful hardware. Idle drain in android is higher than windows.
anyways, funregis, I cant get root with your script. I got drivers installed and adb works fine. it gets detected and device responds to adb commands. but root script is not working as intended.
I get lot of missing files messages in the script window. here I attach screen shot as I cant copy it.
can you recheck the script in bat file. I see that you are trying to copy the files to temp folder in devices data partition but I think im not seeing the source is declared correctly. so no file is being copied. im not much of a script guy so I dont know for sure exactly. can you help me.
Edit : checked, script seems to be correct.
{
"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"
}

suspect008 said:
Yep noticed that, but its expected running a x86 processor and powerful hardware. Idle drain in android is higher than windows.
anyways, funregis, I cant get root with your script. I got drivers installed and adb works fine. it gets detected and device responds to adb commands. but root script is not working as intended.
I get lot of missing files messages in the script window. here I attach screen shot as I cant copy it.
can you recheck the script in bat file. I see that you are trying to copy the files to temp folder in devices data partition but I think im not seeing the source is declared correctly. so no file is being copied. im not much of a script guy so I dont know for sure exactly. can you help me.
Edit : checked, script seems to be correct.
View attachment 3349402
Click to expand...
Click to collapse
Have you set your tablet in "debug USB mode" from the developper menu on android ? I forgot to write this on the guide

funregis said:
Have you set your tablet in "debug USB mode" from the developper menu on android ? I forgot to write this on the guide
Click to expand...
Click to collapse
yep thats the basics right.
Your script works. I executed commands manually. all work fine. all the files get pushed and every command is in right way when executed manually. but just after the tab restart, all things get reset. im not sure about a workaround on this situation. do you have any idea?
I ve set usb debugging and drivers installed correctly and adb works fine.

suspect008 said:
yep thats the basics right.
Your script works. I executed commands manually. all work fine. all the files get pushed and every command is in right way when executed manually. but just after the tab restart, all things get reset. im not sure about a workaround on this situation. do you have any idea?
I ve set usb debugging and drivers installed correctly and adb works fine.
Click to expand...
Click to collapse
Strange it worked for me on android 4.4.2 and 4.4.4 , no idea of the problem if all command worked
When you launch the .bat have you "0/root" as id in the first prompt ?
I've uploaded the rooting kit with english translation (it can helps or not...)

funregis said:
Strange it worked for me on android 4.4.2 and 4.4.4 , no idea of the problem if all command worked
When you launch the .bat have you "0/root" as id in the first prompt ?
I've uploaded the rooting kit with english translation (it can helps or not...)
Click to expand...
Click to collapse
Yes ID is "0/root". its still the same as screen shot when ran the script bat file. im gonna try manual method again and without rebooting I will update the su binaries

Got the root
I achieved the root. just I had to manually push the files and everything. and without reboot I updated the binaries and now it sticks. so thank you for help and files.

Nice

OK, dudes. CONFIRMED ROOT android 4.4.4 with MOTOCHOPPER thanks to morlock8k's link: http://www.mediafire.com/?f4lipgd1hh3jug2

[STABLE] ADB and Fastboot Installer for Windows - Small size and extremely fast

The really small and blazing fast ADB and Fastboot installer for Windows
{
"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"
}
Apart from many other installers widely available on XDA, they all had two things missing; ability to fetch latest version automatically and be really small in size. Well, I have loads of free time so I started working on this small nifty installer for ADB and Fastboot for Windows. What sets it apart from the all other installers?
** FEATURES **
Installer entirely coded in C++ and uses default Win32 APIs
Compatible with all versions of Microsoft Windows later than Windows XP
Really small size (146 kB installer + 1 MB adb / fastboot zip)
Latest version of ADB downloaded automatically from Github Repository and installed system-wide
Seamless install of ADB/Fastboot drivers (Google only for now)
Fully Open Source
** REQUIREMENTS **
Microsoft Windows Vista or later
Active Internet connection
Administrative privileges
** DOWNLOADS **
installer-version-1.2-stable: https://github.com/hackslashX/ADB-F...ster/versions/adb_fastboot_installer-1.2s.exe (146 kB size; adb package will be downloaded separately)
** SOURCE CODE **
For all my Open Source software fans: https://github.com/hackslashX/ADB-Fastboot-Installer-for-Windows/tree/master/source

ADB version update 1.0.39-r3db08f2c6889-android has been successfully pushed to the GitHub repository. Simply rerun the installer to automatically download and install the latest version.

Great, thank you... you saved me

a noob question: where does it install adb ? i try the command "adb devices" in terminal but it says following
Code:
C:\Users\John>adb devices
'adb' is not recognized as an internal or external command,
operable program or batch file.
i also saw in C: drive but no folder like android or adb ?
i just want to access my adb shell for my nougat device on my pc win7.
thanks in advance

Mr.LOVER said:
a noob question: where does it install adb ? i try the command "adb devices" in terminal but it says following
i also saw in C: drive but no folder like android or adb ?
i just want to access my adb shell for my nougat device on my pc win7.
thanks in advance
Click to expand...
Click to collapse
It installs it to C:\Windows\adb.exe.
Did you run the installer as administrator and did the installation completed successfully. You also must be connected to internet during installation.

your installer is recognised as a trojan: https://www.virustotal.com/de/file/...45688791ea9abed7b75386e0/analysis/1505028376/

Cyagon said:
your installer is recognised as a trojan: https://www.virustotal.com/de/file/...45688791ea9abed7b75386e0/analysis/1505028376/
Click to expand...
Click to collapse
The installer is fully open source. You can check the source code and rest assured there is no Trojan. Even compile it for yourself

Bitdefendender removes what I assume to be the temporary download of an ADB file. Any way we can fix that?

Mattwmaster58 said:
Bitdefendender removes what I assume to be the temporary download of an ADB file. Any way we can fix that?
Click to expand...
Click to collapse
I'll test it on Bitdefender today to check if it is really the case. The only reason why antivirus detects it as a suspicious file is because it copies all files to Windows directory

hackslash said:
I'll test it on Bitdefender today to check if it is really the case. The only reason why antivirus detects it as a suspicious file is because it copies all files to Windows directory
Click to expand...
Click to collapse
Could you stick the files somewhere safe (but unsuspicious) then add that to PATH?

Mattwmaster58 said:
Could you stick the files somewhere safe (but unsuspicious) then add that to PATH?
Click to expand...
Click to collapse
Yep, can be easily done. I'll implement this functionality in the weekends.

Hi there, I just wanted to stop by and say thanks for developing this. All the other quick installers seem to be abandoned, and the newest versions of adb do actually make a difference. For example, it used to be that a pull would skip files with certain characters, and I believe they've ironed that out now. I am going to download this and give it a shot asap.
Thanks again.

hackslash said:
Yep, can be easily done. I'll implement this functionality in the weekends.
Click to expand...
Click to collapse
Any news about that?
Also, could you add in your installer adb/fastboot generic drivers?
Thanks in advance

provolinoo said:
Any news about that?
Also, could you add in your installer adb/fastboot generic drivers?
Thanks in advance
Click to expand...
Click to collapse
Maybe dev abandon?

codename:acero said:
Maybe dev abandon?
Click to expand...
Click to collapse
Not abandoned. I'll rewrite it within this week. Extremely sorry for the delay.

Thank you. Ill be waiting.

hackslash said:
Not abandoned. I'll rewrite it within this week. Extremely sorry for the delay.
Click to expand...
Click to collapse
No need to be sorry, it's something you do for free and we can't complain
Thanks a lot for your time and support

provolinoo said:
No need to be sorry, it's something you do for free and we can't complain
Thanks a lot for your time and support
Click to expand...
Click to collapse
I've already added support for installation on non Windows directory and updating the Path variable system-wide to allow using adb from any command prompt.
What's left now is to add support for downloading and installing drivers on the go. I already have silent packages for Huawei, Samsung and Google drivers. Will add the support for it too as soon as I get free this Friday after my exams.

New update 0.3-b
- Remove installation of adb directly to Windows directory.
- Installed now in C:\hcX-af directory with system-wide PATH variable automatically updated so that you can run adb from anywhere
- Updated adb and fastboot version
Download Link:https://github.com/hackslashX/ADB-F...ster/versions/adb_fastboot_installer-0.3b.exe
After installation if you're unable to use adb, please logoff or reboot your PC for changes to take affect.

Duplicate