Develop Bugs

Java JDK,Android SDK and resigning APK's

WINDOWS 7
Thought i would make a noob friendly guide on setting all these up..should make it easier foor noobs to have some fun
To make it more noob friendly i will include pictures
Download Java JDK HERE
Android SDK HERE
And Testsign.zip View attachment testsign.zip
Install Java JDK by double clicking the JDK file you downloaded
Now goto My Computer > Local Disk (C:\) and create a folder called Android and open it.....Create another folder called androidSDK (NO SPACES!)
Extract the Android SDK you downloaded into the AndroidSDK folder there should now be 5 folders in there....)FIG(A)add-ons,docs,platform,usb_driver and tools...
Go into tools and keep it open...the top bar will say something like C:\Android\androidSDK click this top bar and copy it ALL!FIG(A)
Now you need to add the tools folder to your path....
Right click my computer > Properties > Advanced system settings > Enviroment variables
In the system variables box (the lower one) find the path it should be the 5th one down (under OS) highlight path and click edit....
Now go to the end of that line and put a ; there..Then paste the line you copied earlier..
Your path should now look like FIG(B)
now make a Tea/Coffee/Grab a beer or whatever
Back to your tools folder now...Remember that Testsign.zip? Well extract it into your tools folder please.
Next click start (win7 logo in your taskbar) and type CMD it should say command prompt.exe double click it!
Now is the test! Type autosign and hit enter (not hard obviously) If it says XDA in huge letters you are laughing! If not drag and drop Autosign.bat from your tools folder into the CMD window and press enter.
type 1 > enter > yes
2 > enter > yes
3 > enter > yes (enter means press enter not type it.just in case your such a noob you dont know your own keyboard)
You should now be able to resign .apk files by right clicking, if that doesnt work you can type autosign in a cmd window and do option (4) to manually sign.
To install drivers for your android device.......
Check adb debugging is enabled on your phone and plug the bad boy in,go to device manager (right click my computer) find ADB (it will probably have a warning sign) right click that and direct the install to your USB_DRIVER folder
Open up Command prompt (CMD.EXE) type adb devices should say something like HT01GL902119 device
Now i think you are all done!! Please dont hesitate to ask if you have problems i have subscribed to this thread so can answer pretty quickly

Linux.....Coming soon
Saved for linux method

Saved for winxp if i reinstall my laptop

Saved for creating update.zip tutorial

Thank you very much!
If I use this method to sign a modified apk file on my Windows 7 PC,
will installing the apk via File Manager on my phone, cause infinite boot loop?
Stericsson is mentioning here that this could happen.

I dont really know i have always installed apk's (/system/app) via update.zip and have never edited 3rd party apk's(/data/app) to need to sign.
What apk's are you installing?

It's OK! I slightly edited ADW Launcher (just the highlight element in fact)
to match the Xperia (Rachael UI) interface.
It worked just fine, no problems at all!
Thank you again!

Nice guide!

brilliant guide, although i am stuck at the last hurdle. Where can i find device manager? its not in the menu when i right click on computer.

Right click My Computer
then properties>device manager
if that doesnt work it will be in control panel > Add Hardware i believe.

will you do the update.zip tutorial ? because I think that I will need it soon thanks

It is something I have been hunting for a long time. Thx for great work.

steps 2 and 3 are giving me error

Thank you very much. Precise and easy to follow.
Cheers

I'm attempting to install JDK now and don't seem to be doing something right. I'm pretty sure it's changed a bit since this thread began. Any chance someone can assist me? I'm looking to go through the Headfirst Java textbook.

Installed Android SDK, wont work!

Can anyone help? Ive installed the SDK, ive installed the Java stuff, but when I try to open the SDK Manager it opens and closes instantly. I try running through command line and nothing happens.
Am I missing something? On 32 bit windows XP

Assuming you have admin rights on the machine...
Have you tried installing to a different location - like the root of C:
When you d/l the files, did you click properties, and in the bottom of the pane, did it indicate the files were blocked and did you unblock them?
Have you tried uninstalling the current, d/l them again and reinstalling?

Not sure how much this will help, but when I tried running SDK I ended up finding out after doing lots of research, getting some help and everything that it wasn't working properly because I downloaded the wrong version for my PC. Be sure you downloaded the correct SDK for your PC because that will play a big role in the program running correctly.

Re: Installed Android SDK, wont work!
If you used the exe then you need to run your advanced commands from "platform-tools" not the normal "tools" folder. You will see adb files in the currect folder.
/programfiles/android-adk-windows/platform-tools
It will me something like that

I'm not at the point where I can run advanced commands, I can't get the application to open AT ALL so I can't even download any versions of the Android OS etc.

DroidHam said:
but when I try to open the SDK Manager it opens and closes instantly.
Click to expand...
Click to collapse
...be more specific.
when you try to open the SDK manager, I assume you mean in Eclipse?
are you following these directions?
http://developer.android.com/sdk/installing.html

Im not using Eclipse, I just want to open the Android Emulator. I had done this before in windows without much hassle but now I cant get it to open

DroidHam said:
Im not using Eclipse, I just want to open the Android Emulator. I had done this before in windows without much hassle but now I cant get it to open
Click to expand...
Click to collapse
well you have to use eclipse to create an AVD (android virtual device).
Just follow the directions On the link I gave you. once you got eclipse all set up.
[[ this is the eclipse i'm running 3.6.1 classic: http://www.eclipse.org/downloads/do....6.1-201009090800/eclipse-SDK-3.6.1-win32.zip ]]
Click on WINDOW->Android SDK and AVD Manager.
Create a New AVD. Give it a name (something simple, short, all lowercase is best. I named the latest one gingerbread) and select the target (api version)
set an SD card, resolution, etc...etc....
once its created, you have to launch emulator from a command prompt and the AVD switch to specify an android virtual device.
in dos, navigate to the SDK\tools directory, and run
emulator -avd gingerbread
or whatever you named your avd. got it?

ill give it a shot, thanks

ADB.exe

Sorry for the noob question but when I download the latests SDK there is no ADB.exe file in the tools directory anymore.
How do I start ADB with the latest SDK release?

hav0c said:
Sorry for the noob question but when I download the latests SDK there is no ADB.exe file in the tools directory anymore.
How do I start ADB with the latest SDK release?
Click to expand...
Click to collapse
What are your folders once extracted? It will be in one of them!

do you mean it was there an now its gone??
also have you hooked up phone(charge only) to usb, opened command prompt and type adb devices to see if adb starts? cause it may just be placed in different folder in sdk. think it does in new sdk but can't remember which folder doh .

This is the content of my tools folder:
Code:
cat ls.txt
android
ant
apkbuilder
ddms
dmtracedump
draw9patch
emulator
etc1tool
hierarchyviewer
hprof-conv
layoutopt
lib
ls.txt
mksdcard
monkeyrunner
NOTICE.txt
proguard
source.properties
sqlite3
traceview
zipalign
(Same content in my SDK folder in Windows. No ADB.exe..)

have you try to run adb in cmd.exe ?
have a look in platform-tools folder it were im finding adb but im on linux mint right now but should be same

I don't have that folder.
If I download the SDK (zip) from http://developer.android.com/sdk/index.html adb.exe is not in it..
Is that the same for you guys?

hav0c said:
I don't have that folder.
If I download the SDK (zip) from http://developer.android.com/sdk/index.html adb.exe is not in it..
Is that the same for you guys?
Click to expand...
Click to collapse
no thats were i downloaded from, both windows and linux hold on il go into windows an have a look but have you try running adb you can only start it in command prompt (cmd.exe) if your using windows xp. just right click in any windows from menu choose command prompt,plug phone to usb,make sure you have usb debugging on in phone(setting>application >development) and then type adb devices and see itf adb starts for you.
try doing this.

yeah its in platform-tools folder and you can find this in the main folder of the android-sdk-windows folder
check it out it there

Platform-tools doesn't come with the sdk by default if I recall correctly. You need to run the sdk manager and select it as an optional component to download. I'm a long way from my computer right now so I can't double check for you sorry.
Sent from my performance enhanced Desire HD.

dr.m0x said:
Platform-tools doesn't come with the sdk by default if I recall correctly. You need to run the sdk manager and select it as an optional component to download. I'm a long way from my computer right now so I can't double check for you sorry.
Sent from my performance enhanced Desire HD.
Click to expand...
Click to collapse
I do believe your correct.
Sent from my Desire HD using XDA App

dr.m0x said:
Platform-tools doesn't come with the sdk by default if I recall correctly. You need to run the sdk manager and select it as an optional component to download. I'm a long way from my computer right now so I can't double check for you sorry.
Sent from my performance enhanced Desire HD.
Click to expand...
Click to collapse
lol prob why can't find it

It's not there (even after update all)
Thanks anyway..

Looks like it's all change since the version I downloaded when I got my Hero last year.
Taken from the SDK Readme in the latest SDK download, confirming what has been said above:
Welcome to the Android SDK!
The Android SDK archive now only contains the tools. It no longer comes
populated with a specific Android platform or Google add-on. Instead you
use the SDK Manager to install or update SDK components such as platforms,
tools, add-ons, and documentation.
In order to start developing applications, you must install at least one
version of the Android platform using the SDK Manager.
This requires an Internet connection, so if you plan to use the SDK
offline, please make sure to download the necessary components while online.
To start the SDK Manager, please execute the program "SDK Setup.exe".
From the command-line you can also directly trigger an update by
executing:
tools\android.bat update sdk
For more information, please consult the Android web site at
http://developer.android.com
Click to expand...
Click to collapse

hav0c said:
Sorry for the noob question but when I download the latests SDK there is no ADB.exe file in the tools directory anymore.
How do I start ADB with the latest SDK release?
Click to expand...
Click to collapse
there is a adb_blabla.txt file with tells you how you can find adb.exe

aivilon said:
there is a adb_blabla.txt file with tells you how you can find adb.exe
Click to expand...
Click to collapse
I reckon he's probably worked that out in the last nine months
//sent from my Desire HD using Tapatalk; all errors entirely intentional.

Is someone going to just solve the mystery?
Lots of talk
So bottom line, will someone just solve the mystery.
1) If it is installed with SDK where is it and why does search not find it.
2) If it is NOT installed where do we get it.
Thanks

paulckruger said:
Lots of talk
So bottom line, will someone just solve the mystery.
1) If it is installed with SDK where is it and why does search not find it.
2) If it is NOT installed where do we get it.
Thanks
Click to expand...
Click to collapse
You have to install platform tools from "sdk manager.exe".....adb will be under the platform-tools folder after that
Sent from my HTC Inspire 4G using Tapatalk

paulckruger said:
Lots of talk
So bottom line, will someone just solve the mystery.
1) If it is installed with SDK where is it and why does search not find it.
2) If it is NOT installed where do we get it.
Thanks
Click to expand...
Click to collapse
Don't search for it. Go to the directory and look for it. Windows search is a joke

zelendel said:
Don't search for it. Go to the directory and look for it. Windows search is a joke
Click to expand...
Click to collapse
I have done that as well and find to trace of that file? I use a third party search which is better than windows search...does not exist c:/android/***** which is the install directory for the SDK.
Again...if it is not there where do I get it?

paulckruger said:
I have done that as well and find to trace of that file? I use a third party search which is better than windows search...does not exist c:/android/***** which is the install directory for the SDK.
Again...if it is not there where do I get it?
Click to expand...
Click to collapse
As already stated, it is not installed with the SDK by default. In the tools folder there's a text file called "adb_has_moved.txt" which tells you that you need to launch the SDK and install "Android SDK Platform-tools" to get it. Like chrisz5z said.

ADB Help with one part!

So I'm reading through the guide "ADB For Noobs" and I'M STUCK. I can't figure out this one part... it says
Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools"
I'm confused what I'm supposed to add.... Can someone direct me please?
I'm using windows xp btw.

Guide to fixing a soft brick after editing build.prop

I've noticed several users having trouble with their phone when editing the build.prop. They will edit the file, reboot, anxious to use Google Wallet, and be greeted with a black screen of death. Their heart will jump in their throat and they think... "Oh no... I didn't nandroid backup... What's a nandroid backup anyway?" No worries! I have the solution for all of you. Hopefully this short guide will get you going again.
I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.
You also need the naked ADB drivers if you're a Windows user... Here http://forum.xda-developers.com/showthread.php?t=1379875
Once you reboot your phone into recovery: Open start menu, right click on Computer, click properties. This will open the system panel. Top left, click device manager. Somewhere along there, see if you see your device name (something like "Samsung-SGH_I747") with an exclamation point or question mark. Double click it if it does. Click update driver in the window that opened. Click "Browse My Computer...." "Let me pick..." "All devices / next"... "Browse". Now go find where you downloaded and extracted the naked driver zip. Open the folder and double click on one of the available .ini files. You'll get some compatibility warnings, just continue.
Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.

Thanks, worked like a charm on my SII. And I finally have ADB set up for any future hiccups!

ibanezbass said:
I've noticed several users having trouble with their phone when editing the build.prop. They will edit the file, reboot, anxious to use Google Wallet, and be greeted with a black screen of death. Their heart will jump in their throat and they think... "Oh no... I didn't nandroid backup... What's a nandroid backup anyway?" No worries! I have the solution for all of you. Hopefully this short guide will get you going again.
I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.
You also need the naked ADB drivers if you're a Windows user... Here http://forum.xda-developers.com/showthread.php?t=1379875
Once you reboot your phone into recovery: Open start menu, right click on Computer, click properties. This will open the system panel. Top left, click device manager. Somewhere along there, see if you see your device name (something like "Samsung-SGH_I747") with an exclamation point or question mark. Double click it if it does. Click update driver in the window that opened. Click "Browse My Computer...." "Let me pick..." "All devices / next"... "Browse". Now go find where you downloaded and extracted the naked driver zip. Open the folder and double click on one of the available .ini files. You'll get some compatibility warnings, just continue.
Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Click to expand...
Click to collapse
I'm having the same issue; I did the above procedures (using a Mac) but every time I type "adb shell", I get this:
"-bash: adb: command not found"
Help, please....
Thanks!

Nevermind, I figured it out.

good write up, thank you

Seems to be only when you use a gnex as build prop.
HTC jewel works great
I had two softbricks worked great
Sent from my SAMSUNG-SGH-I747 using xda premium

very helpful. Thanks!

This doesn't do anything for me. It still shows rw-rw-rw after running that command in adb. Any other ideas?
It also seems like it doesn't modify any of the files at all. I even tried renaming because i have a build.prop.bak file that i want to use and it doesn't seem to rename it.
[update] I am using the Odin method just to reflash it to the stock rom. I have moved on from this useless method.

Hi i just edited the /system/build.prop
for able to play gameloft games
now my tablet cant boot
i use this room : http://forum.xda-developers.com/show....php?t=1816795
i tried your method
i got this error
>adb shell
error: device not found
what can i do i don't want lose data
i tried to recovery mode and normal booted mode no lucks

please help. ican't find my device in device manager

Thank You !!!!!!!
Thank You, Thank You, Thank You, Thank You, Thank You, Thank You - I was hours away from taking my phone back ... I found my build.prop file with 0 bytes but fortunately I already had a build.prop.bak in there. I'm fairly certain I softbricked my phone by not following the instructions closely on rahpyqui utube Google Wallet process. Thanks SO MUCH!

isn't just easier to re-install the ROM you are running? You don't loose any settings.

unable to chmod build.prop
Help me!!
Error: unable to chmod build.prop: Operation not permitted

lyrictenor1 said:
Nevermind, I figured it out.
Click to expand...
Click to collapse
I'm having the same problem, how did you solve it?

IMEI unknown - invalid
I have problem with IMEI ,no sim cards work in lenovo A660.I have done some factory resets and tried all possible solutions referred in xda forums but none worked.DOu think that build.prop could cuz problem to the IMEI somehow? i had to overwrite a build.prop file from a friendly site because i couldnt use 160 characters in sms and they said that this would help.BUt now , no IMEI.Can anyone help?

Thank you for the info:highfive::highfive:

Help!!!
How do I boot my Xperia S into Recovery Mode? Do I have to press the power button + VOL UP Button so that the LED gets blue?
Anyways I did it that way, expecting it to be in Recovery Mode, but when I run the adb shell it says "Device not found." Can somebody help?:crying::crying::crying:
I guess its because I didnt install the naked drivers but I cant do it because I wont find my device in the device manager... Why not?

Very nice guide, thanks!!!:victory:

THANK YOU!

permission denied
I am getting this when starting adb shell
- exec '/system/bin/sh' failed: Permission denied (13)
is this just a driver issue as I installed the naked driver and rebooted after.