[TOOL] ADB Gui - Also flashes radios [08/01/11] - Android Apps and Games

For all you guys constantly flashing kernels,
I have made a little app to make sure that all command are typed in correctly & to make it a little easier.
You can find it here.
http://minooch.com
Let me know if you think I can make any improvements.
I've only tested it with my N1, but there is no reason why it wouldn't work on other android phones - its just using adb & fastboot. Having said that, it will obviously need the AndroidSDK installed (well partly) & the only other requirement is .NET 2.0 or up.
I finally got around to posting the new version - Version 1.0.1 - The main feature that has been added is synchronise. For example, you can select a folder full of music on your PC & it will copy all the music to your phone (if it's not already on there), & if there is music on your phone thats not on your pc that will copy over as well.
26/05/10 - Small change - Version 1.0.2 - ADB location is now saved in registry
17/08/10 - Version 1.0.3 - Added flash radio (via fastboot) - It will reboot into the bootloader, flash the radio & then reboot the phone
30/08/10 - Version 1.0.4 - Added a donate link
25/11/10 - Version 1.1 - It now has the option to verify the MD5 before flashing a radio
08/01/11 - Version 1.2 - Language can now be changed - Language.lang has the values of all labels, buttons & comboboxes
Known Bugs: (wth synchronise)
If a folder has a space in its name, it's contents won't sync properly (currently working on a solution)
If you delete a file/folder on your phone/pc (not both) it will be copied back next time you sync (not sure how to fix)
The destination folder must exist already (/sdcard/music or where ever you choose), but obviously not the folders what will synced they will be created
Cheers,
Minooch
Feel free to donate

Nice work. Looks like it will make things easier for inexperienced users...which I am not sure is a good or bad thing.
Also, you might want to add "adb reboot recovery". I know I use it fairly often.
(make it "adb wait-for-device reboot recovery". This way, if your phone is bootlooping due to you having not installed bcm4329, you can access recovery for adb push options to fix the bootloop)

rcxquake said:
Nice work. Looks like it will make things easier for inexperienced users...which I am not sure is a good or bad thing.
Also, you might want to add "adb reboot recovery". I know I use it fairly often.
(make it "adb wait-for-device reboot recovery". This way, if your phone is bootlooping due to you having not installed bcm4329, you can access recovery for adb push options to fix the bootloop)
Click to expand...
Click to collapse
didn't know that command will add it now. - edit: Done
Cheers,
Minooch

I'm happy with ADB so not going to be using this (don't mean that the way it sounds!) but just thought if the user is pushing the .ko over adb, will they need and "adb remount" option as well?

yep you will need to remount - but that is automatic.
Using my tool, it takes less steps & is faster

great tool! thumbs up!

Great tool. Any chance for a Wipe Cache/Dalvik Cache option? A lot of times this will fix a bootloop when flashing different kernels on top of eachother. I understand it's in the recovery but this could speed up the process even more.

mikroN1 said:
Great tool. Any chance for a Wipe Cache/Dalvik Cache option? A lot of times this will fix a bootloop when flashing different kernels on top of eachother. I understand it's in the recovery but this could speed up the process even more.
Click to expand...
Click to collapse
Thanks,
Will have a look into it.

looks like a nice tool.. gonna give it a try
good work man

Hey man I'd have to say that I'm getting used to the command line that I nearly forgot there's something in the world called GUI It's really a great tool for lazy guys like me (even I've written a simple shell script). Good job!

Thread hasn't been bumped in awhile. You still working on this Minooch? I was wondering if you could have it save your ADB location? Maybe have it save settings to an .ini file.

MikroN1,
I will add that later today when I get home from work.
Cheers.

Can you please kindly provide the manual instruction, as I'm not the professional user, even I don't know much the ADB command codes, so please instruct the functions of the buttons.

mikroN1 said:
Thread hasn't been bumped in awhile. You still working on this Minooch? I was wondering if you could have it save your ADB location? Maybe have it save settings to an .ini file.
Click to expand...
Click to collapse
mikroN1,
It nows saves the ADB location to registry
devil126 said:
Can you please kindly provide the manual instruction, as I'm not the professional user, even I don't know much the ADB command codes, so please instruct the functions of the buttons.
Click to expand...
Click to collapse
I'm a little confussed by what you want. Are you wanting a manual for ADB GUI or how to use ADB?

This is very good. Downloading now.

New Version - 1.0.3
Added flashing radio via fastboot
It will reboot into the bootloader, flash the radio & then reboot the phone

using ADB sync for sqlite DB
Hi,
I am fairly new to Android / ADB and i have found ADB as a great tool.
My requirement is to sync a sqlite DATABASE (from my PC and on device), i am not sure how should i go ahead with this, gave couple of tries but not able to get anything
Can anyone please suggest me possible ways to fix up this issue. If this is not possible please give me any alternate (i believe this is possible).
Any help in this regard would be highly appreciated.
Thanks in advance.

BTT
asinghma said:
Hi,
I am fairly new to Android / ADB and i have found ADB as a great tool.
My requirement is to sync a sqlite DATABASE (from my PC and on device), i am not sure how should i go ahead with this, gave couple of tries but not able to get anything
Can anyone please suggest me possible ways to fix up this issue. If this is not possible please give me any alternate (i believe this is possible).
Any help in this regard would be highly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Bringing this thread to top.
Can anyone provide the source for ADB sync (prob from ADB_GUI tool)
Thanks,

Think you should add a donate button somewhere in your app too!

Vulpix said:
Think you should add a donate button somewhere in your app too!
Click to expand...
Click to collapse
Done Feel free to be the first to donate
Oh, If you would like me to add any features, let me know

Related

**UPDATE**SuperG1-Computer 9/8/09 4:03am

Here is basic program for your windows computer that just does basic stuff.
It can reboot your phone to wherever you want like recovery, bootloader.
It will wipe your ext2/3 from recovery if you choose and it will repair your ext2/3.
This is still beta, so far everything that is on the app works. But when I say beta I mean I still to implement alot more features so just use it and then tell me what you guys want. I am working on implementing switchrom into it.
This is just about 3 hours of work so you will see alot more in the future.
Screenshots Below!
*(For those of you wondering it is writen in a mix of C++,vb.net,python,and MS-DOS)*
Twitter: http://twitter.com/kickfliprock13
** Oh I forgot to mention you need to have adb set up for this to work if you don't have it set up than it wont work. So if you want to set up just go here: http://punk-in.com/driver_vista.html
changelog:
9/8/09: Added a link to tell you how to install usb drivers for your phone
Added links to our twitter's and plurk's
Fixed a few small bugs
Sped it up a little
doesn't work. tried all your buttons. only one that said anything that made sense was the connect button saying that it was successfully connected. used them both with mounted and unmounted.
adb needed
you must have adb copied to system32 or have the path set up, sorry I forgot to mention that. and then when you plug your phone in click connect and then when it says that it has successfully connected than use the other commands. but everything uses adb so you need it!
Instead You can Add the ADB files into the program & provide a "Install Necessary Files" Button Which will copy the ADB & Fastboot files into the system32 folder of the User From the Inside Of the Program & its UI
Lastly Good Work...
fantasic! works like a charm.
no criticisms as such, but maybe the layout could be improved a bit (i appreciate you did in 3 hours )
anyway, very handy little program!
This sounds like an awesome project. i will play with it and let you know what i find.
Keep it up!
If any of you guys want to help out with it just send me a pm and I will send you myC++ folder. I took an entire C++ course in like 3 days so my brain is kinda forgetting some of the simpler stuff!
Nice work, it'll be a great tool to use. Keeping my eye on this project, I can only imagine all the modifications that'll be made for it.
Wipe is a basic deletion of ext3
What command are you using for fixing ext3?
Wipe is a basic deletion of ext3
What command are you using for fixing ext3?
I am using the repair filesystem command that cyanogen put into his recovery image

[UTIL][PC][15.10.2010] ADB Magic v1.0

This is a BETA version and will have issues
About
I got tired of using ADB by hand for a lot of operations, and thought well hey let's write something for that. I know about DDMS and ADB Explorer, but they aren't always exactly what I want/need.
BETA
Yeah this is a beta version and will have issues.. No warranty, use at your own risk, etc. I'll try to update this in the future. I have a lot of ideas of things to add/improve/fix still.
Requirements and Recommendations
- Required: .Net 3.5 framework
- Required: A working "adb shell" setup
- Recommended: writable /sdcard
- Recommended: root (via su) - note that a lot of things should work without root, but I haven't done any extensive testing on that
- Recommended: busybox
Features
- (also root) Explorer
--- View / Edit files directly in Notepad (optionally converting dos<->unix newlines)
--- Retrieve / add / replace files
--- Rename / delete/ chmod/ chown / checksum
--- New directory / symlink
- Locate (find all filenames matching a certain string)
- ADB shell
- ADB logcat
- ADB (command log)
- Packages
--- Install package (system copy, user copy, ADB install, with or without ODEX, etc)
--- List / backup / remove user and system packages
Retrieving / viewing / editing / replacing / adding files all use workarounds to be able to do this to files that cannot be directly pushed/pulled by ADB, but this functionality does depend on busybox being available.
Donate!
Donations appreciated, you can do so here: http://www.jongma.org/dx.php
Install
Extract the ZIP and put the EXE in the same folder where you have ADB. Also make sure your phone is working with the normal "adb shell" command.
Usage notes
- Please make sure your device is connected in USB debug mode before using ADB Magic !
- Please make sure you do not have the SD cards mounted to your PC !
- This has been developed only with a Galaxy S, so I'm not sure how well it'll work with other devices
Download
<< 1.0, 625
Awesomesause, i would recommend reposting in the android dev forum
edit: should have read ur post xD...
New version and moved ...
I have to say i tryed it on my x10,, and great works good, this program has lots of promise, Thank you and top marks for the work so far keep it up...
Works fine on my X10i. Great work. Very promising.
crap no linux version
nice utility,It works well for the Evo
very nice....works on droid
Thanks for this really useful program. It works great on my X10i.
very nice! works with xdandroid on tp1.
Absolutly great, thank you very very much for this! Extremly helpful!
This is pure awesome, thank you!
Updated to 0.9, now works with ROMs with the latest busybox
Found an issue
Hey, ive found you cant ctrl+c in shell, when i was testing my bootanimation;
#bootanimation
you usually hit crtl+c to stop, in this case I could not, so I had to restart the phone.
Otherwise, looking really good so far hey! Keep up the good work!
Super cool. Mad Props.
HI Chainfire!
I love this app, it's great! I've stumbled across a problem though... I upgraded from JPC to JPK on the weekend and since then it hasn't been working, even after going back to JG4. All the times I've tried it, I've been rooted. It comes up with an error box that just says ! in it.
I haven't changed any of the adb files, and I can also use adb shell manually. Any ideas?
Haven't flashed to JPK yet so no idea, but I'll see once I do
No worries!.
I moved it then ran ADBMagic so it could look for ADB, then put ADB back and selected it, still no luck. Also, I flashed back to JG4 then rooted and it still wouldn't work.
I also noticed that for some reason, it can't start the ADB server and issue the toolbox ls -l / command, even with busybox installed but it CAN see the live logging.
I'm stumped :S
-edit-
I got ADB File Explorer and tested it again. It works, but can't read all directories as it's not able to get su priveliges. I seem to remember the first time I used ADBMagic that SuperUser on the phone asked to allow ADBMagic... am I right or remembering badly? If so, it's not asking me to allow it anymore, across the different roms/roots. Strange.
OK, don't worry about my problem at the moment mate, it seems it's the symptom of a larger problem not associated with your program
Nitephyre said:
OK, don't worry about my problem at the moment mate, it seems it's the symptom of a larger problem not associated with your program
Click to expand...
Click to collapse
Care to elaborate on what this is? I'm having the same problem on my Rooted Captivate JH7, and I need it for the Jupiter GPSfix.

[GUIDE][10/5/10]Comprehensive Guide to Rooting, Flashing, and Android Basics!

1.0 – WELCOME AND DISCLAIMER
So, it seems like a lot of people are having problems with their new Samsung Epic 4G. I thought I'd take a minute and throw together a little comprehensive guide on, well, everything. I'll be updating this periodically, so be sure to check it out.
I'll also be working on formatting it to improve readability... I'm not so good with this markup language that forums make you use, so bear with me. If I can figure out some basic tricks, we'll be in business.
And, just so you know, this is just a guide. As long as you follow it and do research, everything should go fine. That being said, I am not responsible for what happens to your phone. This is all elective and I am not forcing you to do any of this. You brick your phone, you own up to it. I'm only trying make it as easy as possible for your to avoid that.
2.0 – GETTING STARTED
New to Android? Need to root? Just got your phone? Not totally clear on everything? Start here. Even if you have experience with Android, had your Epic since day one, or whatever, you'll still want to check this section out.
2.1 – TERMINOLOGY
First of all, you need to familiarize yourself with the terminology. This is vital to understanding what you are doing, so I'll outline as many as I can.
Brick – Not a term that should be thrown around as much as it is. If you have a bricked device, it is worthless. Like, completely. It is literally as useful as a brick. You CANNOT fix a brick. Everything else is just just breakage.
Root – a)This term comes from Linux/UNIX. To obtain root access means that you have elevated privileges. Look at this like administrator rights in Windows. It's what allows you to run custom software and access administrator setting in Android.
b)The uppermost folder. Such as “/”, “C:\” , et cetera.
Rooting – Gaining elevated root admin access.
Kernel – A kernel is the base of an operating system. For Android, it's where all the drivers and system information resides. A custom kernel can contain undervolting instructions, overclocking instructions, and many other battery-saving, power-giving, phone-enhancing features. There are several options, so make sure you do your research and choose the kernel that offers what you are looking for.
Shell – The shell is the part that you see. It's the interface that interacts and allows you to interact with the kernel.
ROM – A ROM is the combination of a kernel and a shell. Think of this like an operating system.
Dev – Dev is short for developer. These are the people who spend their days and nights writing code and bug testing to bring you the ROMs you love. These guys are the reason you're here, so show your appreciation!
Chef – Chefs and devs are essentially the same thing.
Recovery – A system that allows basic phone function. You can flash from this, clear data, and do very basic debugging. As long as you can boot to this, your phone is NOT bricked.
Flashing – The act of installing a ROM or fix to your phone through recovery.
Wiping – The act of performing a factory reset or cache clear from recovery. Your settings are gone, your apps are gone, your phone is as it was when you you got (to an extent). Formats /system/. This is not reversible.
CPU – Central Processing Unit. The brain of the phone. All data travels through this at some point.
Overclocking – Pushing your CPU to its limits. The CPU has a stock clock speed (1GHz for the Epic), and overclocking is pushing it past that.
Undervolting – Making the phone use less power. This saves battery.
AOSP – Android Open Source Project. Frequently referred to as “Vanilla”. The actual people who make Android. Go here for more information.
Theme – A cosmetic change to the user interface.
One-Click – A script or program that does everything for you.
Busybox – A collection of scripts that allow deeper editing of the system while it is running.
Remount – An easy method of mounting /system/ for writing.
Stock – Samsung-released, no editing, as-is stuff. Basically, how the phone came.
OTA – Over the air. Updates that automatically come to your phone, through your service.
adb – “Android Debug Bridge” A debug program for accessing your phone.
deODEX – Combining the ODEX file and the APK files for all the items in the /system/ folder. Allows for easier theming and customizing.
FC/Force Close – When a program or app crashes.
2.2 – WHY SHOULD I ROOT MY PHONE?
Rooting offers several great things including, but certainly not limited to, access to hidden features, total customization, better battery life, and overclocking. It gives you control over the device that you paid money for in the first place. The devs here are great at finding features that the manufacturers left out or disabled and making them work.
It also is a great hobby. Even if you aren't a developer yourself, flashing ROMs and trying out new features can be a lot of fun and definitely kill boredom. And who knows? Maybe you'll end up learning something and start coding yourself.
2.3 – ROOTING
Great! Now you know some words! So, what next? Well, we need to achieve root access on your phone. There are a few ways to accomplish this on the Epic. Please note that the one-click methods are hit and miss and are affected by several factors, including computer speed, cable, USB ports, and, for all intents and purposes, random chance. I HIGHLY recommend you open the .bat files and run every command in adb manually. I'll update this guide, eventually, with how to do this.
If you're running Windows, you're going to need the drivers for this phone. Install them BEFORE connecting your phone to your computer. You can get them here:
32-bit: Click here
64-bit: Click here
You'll also need to put your phone into debug mode. After you turn this on, you can just leave it on. To do this, go to settings, and then to applications, then to development, and then tick the “USB debugging” check box.
I also recommend using a cable other than Samsung's cable that came with the phone. Really, that cable is hardly good for anything more than charging. It's low quality and has caused a lot of users more than a headache. If you are unable to get another cable for whatever reason, run each command individually from adb. Check the section about adb and the Android SDK later in the guide for more information on how to do that.
2.3.1 – The Jokeyrim temporary root with noobnl's one-click script method – DO FIRST
Let it be known that I don't recommend relying on this method. It's janky and can cause problems once you get deeper into Android modification. Use it to get your remount scripts and then quickly do the kernel mods in the steps in 2.3.2.
Go here and download the .zip file. Extract the .zip contents to your desktop. Open the folder, run “run.bat” and let it go.
NOTE: This is just root, this is temporary, and this DOES NOT give you access to a recovery. All this will allow you to do is run applications that require root or busybox and adds the remount script.
2.3.2 – The rooted kernel and recovery method method – DO SECOND
I do recommend that you use this method. This gives you true, permanent root.
There are a couple of ways to do this. I actually suggest you follow both guides, too. This will help prevent you ever getting to Samsung's stock recovery, which is worthless for your purpose.
The first is noobnl's recovery method, and definitely the one you should do first. You can find it here. Download the .zip file and extract its contents to your desktop. There is an issue with this .bat file, so you're going to have to do some extra steps. With adb (go to the section about the Android SDK and adb further in the guide if you do not know what this is) and type:
Code:
adb shell
su
remount rw
exit
exit
(the two 'exits' is not a typo)
After running those commands, open your extracted folder and run the run.bat file. Should be smooth sailing.
The second is koush's method. koush's thread is here, but I that's a complicated method. After you do noobnl's method above, go to this thread and download the .zip from that. Put that .zip on the root of your SD card. Boot into the Clockwork recovery by turning the phone off, holding down the camera button, the volume down button, and pressing the power button until the phone turns on. Once in there, do this:
1. BACK UP YOUR PHONE. I cannot emphasize this enough. Backups are sooo important in your Android modding quest. Backup and do it often. (Backup and restore → Backup).
2. Go to “Flash zip from SD card”
3. Choose zip from sd card
4. Select the zip we put there earlier
5. Click “Yes”
6. Let it do its thing
Once you've done this, you need to boot into the phone, go to the market, and download “ROM Manager”. From that, click “Flash recovery” (the top option) and select the Epic. This will take a minute. From this point on, you can use ROM Manager to boot into the Clockwork Recovery.
2.3 – FLASHING ROMS/KERNELS/FIXES
This is the fun stuff. This is why you're here. Now that you have root and a recovery, we can get some work done. First, you have to select a ROM that you want. Always pick a ROM that is designed for the Epic. ROMs designed from other phones can and will brick your phone!
You can find ROMs for the Epic in the Epic 4G Android Development section of XDA. Do some research to each ROM to make sure it's what you want. If you want a kernel, make sure your ROM supports other kernels and that the kernel supports your ROM.
Once you've picked your ROM, put it on the root of your sd card and then boot into Clockwork Recovery using your method of choice, then:
1. BACKUP. I seriously cannot stress this enough.
2. Wipe everything. Factory reset and clear cache.
3. Go to “Flash zip from SD card”
4. Choose zip
5. Choose “Yes”
6. Let it run
7. -OPTIONAL- To ensure it worked, repeat steps 2-6. This is just to make sure everything worked. Problems with this can be intermittent and this helps to avoid them.
8. Reboot.
3.0 – ERRORS
Stuff goes wrong. You have to understand, EVERYTHING in this is experimental. The devs here do not have access to EVERYTHING that is required to make these phones work and have to guess at some things and, basically, just do their best (And their best is pretty damn good!).
Basically, just be sure you have backups that you can restore from, and this will all be fine.
3.1 – BLACK SCREEN
Oh no! I flashed ROM X and now my phone won't boot and I hate everything!!!
Worry not! As long as you can boot in to recovery, you have nothing to fear. Just restore the backup that I told you to make and you're back in business. Easy fix.
3.2 – CONSTANT FORCE CLOSES
You boot up your phone and are immediately greeted with force closes. Chances are that you didn't wipe OR that the ROM you're using isn't ready for show time. Again, just restore your backup from Clockwork.
3.2 – CAN'T GET TO RECOVERY, CAN GET TO DOWNLOAD MODE
Well, looks like you'll be returning your phone to stock using Odin. Read later on in the guide how to use Odin in the section about Odin.
3.4 – PHONE WON'T TURN ON AT ALL
Welcome to bricksville, population you. Sorry, but you're phone is a $500 paperweight... Probably shouldn't have flashed that GSM ROM, huh? Not even Odin can save you at this point...
4.0 – THE ANDROID SDK AND ADB
The Android SDK (Standard Developer Kit) is a tool freely available to everyone. You can find it here and it is available for Linux, Mac, and Windows.
4.1 – INSTALLING THE SDK
So, the first step is going to be how to install the SDK on your system. I have experience with Linux and Windows, so that's what I have for now. If someone with a Mac can help write the set up instructions for that, I'd be very appreciative.
4.1.1 – Windows
First, download android-sdk_r07-windows.zip from here to your Desktop. Once it has downloaded, double-click the file and extract it to the root of your C:\ drive (this is optional, but it will make things a lot easier in the future). Rename the extracted folder “android-sdk-windows” to just “android” to make your life easier.
Open the new folder, then run the SDK Manager. If you run into an error about Java, go to java.com and get the latest version of the Java JRE (pretty much just click whatever the biggest “download” button is that you first see).
Once you have the SDK open, it will ask you to install packages. Just tick the “Accept All” radio button on the bottom right and press install. Depending on your internet connection, this can take a long time. Just be patient. Once they are all installed, you're good to go.
How you use adb is simple. Open a command prompt (press the Windows key + r and type “cmd” in the box that shows up, or go to Start → All Programs → Accessories → Command Prompt) and type in “cd C:\android\tools\” and type your commands (list of common commands at the end of this section.
-OPTIONAL- This step is optional, but HIGHLY recommended. Now that we have the SDK set up, we're going to adb to the Windows paths so that you can use adb from anywhere you can open a command prompt.
First, click the start menu and then right-click “My Computer” (Just “Computer” in Vista and 7. You'll also need to click the “Advanced System Setting” on the left side of the window that appears.). Click “Properties” and the Properties window appears. Now, click on the “Advanced” tab and the the “Environment Variables” button. A new window appears with two scrollable boxes. In the lower box, scroll until you find a “path” option and select it. Click “Edit” underneath the box. Move your cursor to the very end (Press END on your keyboard, just to be safe) and type “;C:\android\tools\”” (That leading semi-colon is important and may already be there. Check to be sure).
And you're done! Open a command prompt and type “adb devices” and see what comes up. If a list of devices (phones; will be empty if your phone isn't connected in debug mode) comes up, you've succeeded! Congrats.
4.1.2 – Linux
I use Ubuntu personally, but most of this information should be universal. If anyone running anything else sees anything missing or wrong with other distributions, let me know and I'll update or fix it.
First, you need to acquire the SDK. The file is android-sdk_r07-linux_x86.tgz from this site. Once downloaded, extract the contained folder to your home folder (/home/*USERNAME*, using your username) and rename the folder “android' for later ease of use.
Use terminal and cd to the android folder your created. Use the command “tools/android update sdk” to make the SDK updater come up. Just tick “Accept all” in the bottom right and then click install. This can take a while depending on your internet connection.
Once you have all of the files installed, you're ready to use adb. Using terminal, navigate to /home/user/android/tools and type (For Ubuntu):
Code:
sudo chmod 777 adb
This will allow the adb file to be read as an executable. Note that this only has to be done once. Then, use this code:
Code:
sudo ./adb start-server
(replace 'sudo' for 'su' for distros other than Ubuntu)
This is necessary every time you use adb (in Ubuntu, at least). You only have to do it once per session, but if the adb process is ever killed during your session, you must do it again. I've just gotten into the habit of doing it every time I log into my computer. You could also create a boot script that does this for you... which I've been meaning to get around to. After you have the process running, you won't have to use su/sudo or ./ to use adb.
Note that one-click scripts written for Windows will have to be opened and run manually. There are scripts for Linux floating around, but I can't seem to find the thread.
-OPTIONAL- This isn't a needed step, but you'll probably want to do it. Here we're going to add adb to the paths folder so that after you have started the process as an administrator, you can run it from any folder.
Open terminal and use these commands:
Code:
echo $PATH (should return the directories associated with $PATH)
export PATH=$PATH:/home/user/android/tools (replace with path to your tools directory, you may need to add 'sudo' or 'su' to the beginning of this cmd)
echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
Once done, you're set. Once you have the process started, you can run adb commands from any terminal window.
4.1.3 – Mac OS
-I don't own a Mac, never have, and I have zero experience with Mac and Android... If someone else can help with this section, I'd appreciate it -
4.2 ADB COMMANDS
This isn't a complete list, but it should be enough to get you by for your purpose.
adb shell – opens a terminal on your phone. Terminal is like the command prompt of Linux.
adb push – pushes a file to the phone. The syntax is ”abd push *file location on your PC* *Location you want it on your phone*”
adb pull – pulls a file from your phone. The syntax is “adb pull *file location on the phone* *location to be placed on your PC*
adb shell rm – deletes a file from your phone. The syntax is “adb shell rm *location and name of the file to be deleted*. NOTE: adb shell rm -r is a recursive deletion and can cause damage to your ROM and phone. Make sure you know what you are doing if told to do an rm -r.
adb devices – lists all connected Android phones.​
5.0 - ODIN
(I don't have a ton of experience with Odin, so if someone can refine this section, let me know and I'll update it)
Odin is a tool that was created for previous Samsung phones. It is a powerful tool and very useful for saving your phone from many malfunctions. As long as you can boot your phone into download mode (Hold down the “1” key on the slide-out keyboard while powering the phone on) you can almost always save your phone.
That said, Odin is also fairly experimental in its implementation on the Epic. There have been several reports of failed flashes and intermittent errors. This guide will hopefully help prevent that from happening.
5.1 – SETTING IT UP
If you haven't already, you need to get the drivers for the phone. Install them BEFORE Odin and before connecting your phone to your computer. You can get them here:
32-bit: Click here
64-bit: Click here
After that, you're going to need to get Odin. You can find that, as well as a basic guide and the stock files from noobnl, here (External link to SDX). Odin is the .rar file from the first link fo the post.
5.2 - USING ODIN
After you have it downloaded, extract the files somewhere (I recommend a folder on your desktop). From the extracted files, double-click “Odin3_v1.0.exe” and the Odin window opens. Have it completely ready to go before connecting your phone. Put all your files in the spots they belong (refer to the post where you got the Odin files for instructions on that... it seems to vary a lot depending on the purpose). Make sure that no other check boxes are ticked besides “Debug En.” and “Auto-reboot”. All the others can have very negative effects.
Before connecting your phone, put it into download mode by holding down the “1” key on your slide-out keyboard while powering the phone up. Once it is in download mode, connect the phone. The first box in Odin should come up as something akin to “COM4”. If it doesn't say exactly that, don't worry. Make sure all your files are placed correctly, and then click “Start”. It should take up to a few minutes, so be patient. Cutting this process off early can have negative effects. When it is finished, the phone should reboot.
6.0 – CLOSURE
I hope this guide helped you. If you have any questions, you can contact me, but I can't guarantee I can help you. Most devs are willing to help, too, so you can shoot them a PM and they'll try to get back to you.
Good luck and happy flashing!!
[Update Log]
*10-5-2010 - Added sections for Odin and adb/Android SDK. Updated sections, fixed typos and mistakes, reorganized a little. Fixed links.
None of those links are working for me. I get sent to a page with a message saying "Sorry, we can't find "xn--http-fb7a". We suggest that you check the spelling of the web address or search above."
Thanks a bunch, this was a very useful tutorial on the basics and for me helped out greatly with understanding where and what you need to do to be getting the best out of these awsome phones!
blasted across the interwebs by the Epic 4g!
Lonewuhf said:
None of those links are working for me. I get sent to a page with a message saying "Sorry, we can't find "xn--http-fb7a". We suggest that you check the spelling qof the web address or search above."
Click to expand...
Click to collapse
Weird. I just went through and checked them all and everything is working on my end. All the URLs are correct. Maybe try clearing your browser cache?
DevinXtreme said:
Weird. I just went through and checked them all and everything is working on my end. All the URLs are correct. Maybe try clearing your browser cache?
Click to expand...
Click to collapse
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/
dwyw42 said:
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/
Click to expand...
Click to collapse
That is so weird... It's showing up like that for me now, too. I've checked the source, and it stills is showing the right links in my post.... It's something on XDA's end right now... I'll look into getting it to work a little later.
Good work! This should be a sticky!
Sent from my Epic 4G
dwyw42 said:
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/
Click to expand...
Click to collapse
yeah same here, i just cleared everything before "forum" from address bar and page loaded.
You might wanna ad that you need done battery life when flashing a kernal. If your phone dies during the flash your phone will be a useless brick.
You might also wanna adds the odin steps for flashing back to stock
Sent from my SPH-D700 using XDA App
mysteryemotionz said:
You might wanna ad that you need done battery life when flashing a kernal. If your phone dies during the flash your phone will be a useless brick.
You might also wanna adds the odin steps for flashing back to stock
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Unless whatever you're flashing messes with the recovery partition, an incomplete flash shouldn't cause a brick. As long as you can boot to recovery or download mode, you can save your phone.
And I'm working on an Odin section for my next update to this. A lot of things will be added next time I update the main post.
Sent from my SPH-D700 using XDA App
i've got the first part of your guide done by completing noobnl's method but i cant get koush's method down. you say to hold down the volume, camera, and power buttons to boot into clockwork recovery, but it seems like it goes into the stock samsung recovery? how do i get the clockwork recovery?
The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.
dsummey30 said:
The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=770388
for the proper thread
^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App
bitbang3r said:
^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Same with me. I selected "Flash ClockworkMod Recovery" and after a number of tries it was successful. Yet when I boot with the 3 buttons it still goes into the stock recovery.
you might wanna add how to set adb
Spunkzz said:
i've got the first part of your guide done by completing noobnl's method but i cant get koush's method down. you say to hold down the volume, camera, and power buttons to boot into clockwork recovery, but it seems like it goes into the stock samsung recovery? how do i get the clockwork recovery?
Click to expand...
Click to collapse
bitbang3r said:
^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Vanquish46 said:
Same with me. I selected "Flash ClockworkMod Recovery" and after a number of tries it was successful. Yet when I boot with the 3 buttons it still goes into the stock recovery.
Click to expand...
Click to collapse
I think I know the issue here. It's that /system/ isn't being mounted as rw. Run the jokeyrim root method and then go into adb and type this:
Code:
adb shell
su
remount rw
exit
exit
If you don't know how to use adb, just wait until a little later tomorrow. I've got a whole section about it to add to the guide, but I don't have it completed yet (did some work on my laptop in the middle of writing it, forgot to reconnect my WLAN card and was baffled for most of the day...)
dsummey30 said:
The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.
Click to expand...
Click to collapse
Sorry about that. Should be fixed now. Thanks for pointing it out
mysteryemotionz said:
you might wanna add how to set adb
Click to expand...
Click to collapse
All in the works I expect to have the guide updated early tomorrow, if not tonight.
Updated the guide with a lot of new info. Two new sections for adb/the SDK and Odin as well as a general update to the whole thing. Some of the sections changed (HARD and EASY mode are now both required, unfortunately...) and some things got a little moved around.
Also, all of the links should now work correctly. Something about the way XDA was handling quotations... So I just stripped them all from the forum code stuff...
If anyone has any experience with Mac, I could use your help for the adb/SDK section, and I could also use some help from someone more experience with Odin for that part.
Thanks, guys! I really hope this guide helps some people.
not to be a pain Devin but the two links for noobnl's programs goes to the same page for the easy and hard method don't know if that's right or not but wanted to point it out to you.
Thanks again for the great guide.
David

[Tool]Noob proof(ish) android helper

Hello people who are interested, I created a program!!!! This program is mainly for beginners since they don't know adb commands (including fastboot), but I use this program just to make it easier on me, especially as an easier way to do backups. How it works is that once you hit the execute (or similar) button it just puts the properly formatted command into the command prompt.
I have to put this part in so that someone doesn't sue me or something because they accidentally bricked their phone or tablet from my program and I'm pretty sure that it isn't my program's, but I'd be more than glad to help, but back to the subject: I am not responsible for any and all damages done to your phone due directly because of my program or whatever you've used my program for. I'd be glad to help you with any problems, but I only have limited knowledge of Android, so I'll probably end up just telling you somewhere you could go to maybe find the answer, if I can.
One of the last things I want to do is thank Hashcode because without him I wouldn't have gotten into android as much because he's basically the only person who will work with Kindle as he's made numerous advances with it, making it a tablet I actually like. THANKS HASHCODE.
PLEEEEZ pm me, post a reply, or thank me if you use this at all and like it, if you don't I'll probably end up destroying any evidence of it (except my own copy) and plus it'll make me feel happy that I'm actually helping people by making this. If you tell me any suggestions you have, I will try to work it in if at all possible, but no guarantees.
Download for v2.0 attached. Download link (dropbox) for v1.1 at bottom.
Features of v1.1:
FireFlash installer (with necessary files)
easy adb connect
restore with boot, recovery, and system .img's
moving of .zips
moving of files
Unlock device walk through for HTC phones
Flash .zips with adb sideload
Flash file into a partition using fastboot
Install .apks
Root with Restore
Install Drivers
Able to set colors of the command prompt window
Features of v3.1
fixed adb sideload not working at all
Improved backup (Now it's checkboxes not radio buttons and asks if you want to overwrite if the custom named backup already exists)
Features of the future (features that may appear in future versions):
Root with Restore in program form (will need permission from Bin4ry)
Driver installer (will just link to the program that's already packaged in the program)
HTC unlock walkthrough
ability to save configuration in fastboot (saves variables and maybe partition)
remember last session (text boxes will already be filled in with previous info)
An installer (only if its requested by people, since I'd have to learn how to make the installer)
if you'd like to see other features added, I'm open to suggestions (pm me or post right here on the thread)
Dropbox Links for v1.1:
.zip download
.exe (self extracting 7z) download No uncompression program needed!:victory:
Note: Sorry about not updating in a while, I'm actually having a life this summer so I might actually update this LESS until school gets back in, unless people tell me to update it more (Pleeez tell me, I realllllllly would like to know if I'm helping people, it would make my day!)
Beta!
This area is for BETA!!
Current features in beta:
NONE! No beta right now, but v4.0 beta will be coming soon
Click to expand...
Click to collapse
Soon updating will become more regular as school is letting out this week. If you want to see my source code, I'd be glad to post my vb solution, but at this point it would just take up time I don't have much of.

Stuck uploading APK to Lineage 18 ROM (read to the end)

Preamble​I oft find in various forums that people are so filled with the milk of human kindness that they just can't wait to help, ( or may gain a few more badges~) ignoring everything but the heading.
And in doing so ask foolish questions.
So, please DO READ to the end.
UPDATE
Thanks to @ jwoegerbauer I now know I can't install the Lantern APK via recovery. I must use ADB which I have previously tried but failed.
Obviously, therefore I do not know what I am doing with ADB.
My tasks focus now is to install Lantern APK via ADB with the devices , tools and systems already mentioned. (below)
Unless someone, somewhere knows where I can find a Lantern ZIP file which I can flash. (seems I am good at that now at least~)
Please DO read everything below ladies and gents, my sense of humour and patience does have a limit~
Mobile Device Details​Samsung note 3 originally 9006 Chinese ROM
Rooted via Odin to 9005
Upgraded to Lineage ROM 18
Uploaded pico Gapps
Uploaded Magisk v23
Desktop Machine
Asus P5BSE / Core2 Duo E4400 @ 2.00GHz / 4GB ram / 2TB storage / Linix; Zorin Core 15.3
Project in brief​To install Lantern. (getlantern.org)
Lantern is usually installed via Google play store.
Google is blocked in China.
Downloaded Lantern APK to upload to phone via recovery from SD card.
Recovery does not show the APK in the SD card.
Stuck.
Further info - useful?​During one of my many attempts to install Lineage following a blog, I wiped the disk in error.
I also suspect I removed the backup of the original Samsung system as when I tried to reboot, TWRP mentioned there was no O/S.
Nothing I could do restored the original.
What was it Macbeth said about being in blood stepped so far?
On my final install of Lineage 18 I seem now to have their Recovery, not TWRP.
I am happy with that, seems no big deal for me, I was able to successfully install the new OS + Gapps. And it is one less APP to install
I also have Magisk installed, the device is in dev mode and - seemingly rooted. (although the App does not explicitly say so)
Using a borrowed SIM card I can connect to the China mobile network system.
I now have a fully functional, working , English language device with Lineage 18.
Brilliant!
My last task is to figure out how to get the Lantern App sorted.
I have downloaded the APK from their official site, several others as well as a supposedly zip file.
Saved to SD card, visible when viewed on Linux, invisible when card is installed in mobile.
I really do not know quite how to proceed from here.
If I have missed anything, sorry, please ask.
Huge thanks to RAIZ from this forum for getting me to this stage and the guys who made Lineage 18 so darn easy to install and seemingly impossible to mess up.
And boy oh boy, believe me, I have really tried over the past few months~!
thebic said:
Mobile Device Details​Samsung note 3 originally 9006 Chinese ROM
Rooted via Odin to 9005
Upgraded to Lineage ROM 18
Uploaded pico Gapps
Uploaded Magisk v23
Desktop Machine
Asus P5BSE / Core2 Duo E4400 @ 2.00GHz / 4GB ram / 2TB storage / Linix; Zorin Core 15.3
Project in brief​To install Lantern. (getlantern.org)
Lantern is usually installed via Google play store.
Google is blocked in China.
Downloaded Lantern APK to upload to phone via recovery from SD card.
Recovery does not show the APK in the SD card.
Stuck.
Further info - useful?​During one of my attempts to install Lineage following a blog, I wiped the disk in error.
I also suspect I removed the backup of the original Samsung system as when I tried to reboot, TWRP mentioned there was no O/S.
Nothing I could do restored the original.
What was it Macbeth said about being in blood stepped so far?
On my final install of Lineage 18 I seem now to have their Recovery, not TWRP.
Seems no big deal for me, I was able to successfully install the new OS + Gapps.
I also have Magisk installed, the device is in dev mode and - seemingly rooted. (although the App does not explicitly say so)
Using a borrowed SIM card I can connect to the China mobile network system.
I now have a fully functional, working , English language device with Lineage 18.
Brilliant!
My last task is to figure out how to get the Lantern App sorted.
I have downloaded the APK from their official site, several others as well as a supposedly zip file.
Saved to SD card, visible when viewed on Linux, invisible when card is installed in mobile.
I really do not know quite how to proceed from here.
If I have missed anything, sorry, please ask.
Huge thanks to RAIZ from this forum for getting me to this stage and the guys who made Lineage 18 so darn easy to install and seemingly impossible to mess up.
And boy oh boy, believe me, I have really tried over the past few months~!
Click to expand...
Click to collapse
What recovery are you using? Have you tried different recoveries?
What version of twrp are you running?
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Code:
adb devices
adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
Yeah you could use adb sideload in twrp.
jwoegerbauer said:
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Click to expand...
Click to collapse
Hehe, I can verify your first statement!
Do you have a link you can direct me to please as to how to do it via ADB in Lineage recovery as I did try that (side loading) via TWRP and it threw back an error. I can't recall but I think it was permissions or similar?
Sorry, I forgot to mention that in my post.
Thx for your constructive feedback - much appreciated.
P
Re-read my cited post: I've edited it.
jwoegerbauer said:
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Code:
adb devices
adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
Click to expand...
Click to collapse
Ohhhhh Kayyyyyy - coping.
Just.
You have added code?
Before I go ahead and destroy New York, I use that where?
How?
and errr... why?
I am guessing in Terminal, but I am not really sure what I am trying to achieve here.
Sorry, not arguing or being difficult, I just find it helps me if I know what EXPECTED outcomes are. Just in case it isn't what I should expect. :>(
Thx for your patience.
p
I think the understandable answer is given here:
adb install - Android ADB Shell Commands Manual
adbshell.com
Of course it's required ADB got installed on Windows computer if not done yet: if not then you may use the installer script linked to in my signature.
jwoegerbauer said:
I think the understandable answer is given here:
adb install - Android ADB Shell Commands Manual
adbshell.com
Of course it's required ADB got installed on Windows computer if not done yet: if not then you may use the installer script linked to in my signature.
Click to expand...
Click to collapse
Thx not so helpful.
I've edited my post with a preamble, please check it when you have time.
Have a nice weekend.
thebic said:
Thx not so helpful.
I've edited my post with a preamble, please check it when you have time.
Have a nice weekend.
Click to expand...
Click to collapse
[email protected]:~$ adb install test.apk
can't find 'test.apk' to install
[email protected]:~$
I seem to be going in ever decreasing circles.
Please help me out- what is protocol.
Do I keep updating my progress - or lack of- here, in this dialogue, or should I continue to update my original post?
Which one best communicates to everyone where I am at?
Cheers
thebic said:
[email protected]:~$ adb install test.apk
can't find 'test.apk' to install
[email protected]:~$
Click to expand...
Click to collapse
You forgot to add the exact file directory.
Keno_I said:
You forgot to add the exact file directory.
Click to expand...
Click to collapse
Did it work after adding the file directory?
You are right.
I am not sure how this forum works, so it was more of a post to jwoegerbauer.
Anyway, even opening the folder with terminal and using adb install lantern-installer failed with a CLOSE error message. I guess that meant close as in shut not closes as in almost!
I can, using Lineageos recovery access ADP on my phone with the instruction: " now send the package you want to apply to the device with "adb sideload <filename>"
However that triggers a screed of data in terminal which, frankly, is well beyond my rudimentary level of comprehension.
I have tried following 3 other on line tuts which suggest using ADB on my computer. All goes well until the instruction: <adb devices> which returns:
$ adb devices
List of devices attached
In other words, computer can't find phone!
I initially tried it in DOWLOAD mode, with the usual "download in progress, do not disconnect source."
Then reading the tuts again, none mentioned download mode so I tried with just the device attached to the machine in normal phone usage mode. Checked that SAMSUNG was visible and I could open the folders but again failed. ( sorry I forget what that error message was)
So far the most positive has been the direct ADB via Lineageos, but I have no idea where to go from there.
It is knocking on 37* here, too hot to think so I am taking a break.
Thx for your latest efforts.
Cheers
P
OK Finally!
[email protected]:~$ adb devices
List of devices attached
438f904d device
[email protected]:~$ adb install /home/bicyu/Sam-upgrade/lantern-installer/lantern-installer.apk
Performing Streamed Install
Success
[email protected]:~$
I have read so many posts all end with the <adb devices> and on each one I see zilch.
So, for anyone else in this boat, here is my solution.
In developer OPTIONS on your LINEAGEos device scroll down to
DEFAULT USB CONFIGURATION​Very likely it is set to FILE TRANSFER - mine was.
Change it to USB TETHERING
Then enter < adb devices> in terminal.
You should then see your Android listed.
Proceed with: adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
You should see a SUCCESS flag!
NOTES: This works in Lineageos ROM on Linux, ( Ubuntu / Zorin O/S)
I dunno about others.
You need to have dev options activated.
Change the USB setting back when done, otherwise it tends to mess up your Internet! (did mine anyway!)
This is the best background tut to ADB I found.
He talks about a USB3 bug which, apparently, creates the same problem - maybe THAT is your issue? It was that article which put me on the USB CONFIG train.
Hope this helps someone.
A REALLY HUGE thank you to jwoegerbauer for putting me
on the right track - wrong train, - but right track.
Cheers mate!
Glad to hear you solved it.
Only to have mentioned it, there is a workaround - as always because many ways leads to Rome:
Copy the APK of interest onto MicroSD-card, plug the card into phone, afterwards using any File Manager application that is installed on phone, navigate to the location on MicroSD where the APK file is located and finally double-click on the APK file: this will install the APK.
Yep! Well good luck
jwoegerbauer said:
Glad to here you solved it.
Only to have mentioned it, there is a workaround - as always because many ways leads to Rome:
Copy the APK of interest onto MicroSD-card, plug the card into phone, afterwards using any File Manager application that is installed on phone, navigate to the location on MicroSD where the APK file is located and finally double-click on the APK file: this will install the APK.
Click to expand...
Click to collapse
NOW he tells me!
That was where I began 2+ weeks back, downloading to SD card and trying to find a way inside the phone to do it. Never thought of File Manager! Duh~
Take care buddy, enjoy your weekend, wherever you are.
p
thebic said:
NOW he tells me!
That was where I began 2+ weeks back, downloading to SD card and trying to find a way inside the phone to do it. Never thought of File Manager! Duh~
Take care buddy, enjoy your weekend, wherever you are.
p
Click to expand...
Click to collapse
Aroma File Manager, how nostalgic~
Now to wait till a mod closes this post

Categories

Resources