Develop Bugs

[Q] adb will not work for me...what gives???

To start off, yes I am a complete noob to this, so bear with me. I have been trying for hours to get the adb info to install on my computer so I can root with the new 2.2 method. I have Vista/32 bit and I have tried multiple ways to install, from guides here and you-tube and nothing will recognize the adb in cmd.exe. I have copied the sdk info into a tools folder like I'm supposed to, I think, and followed the instructions and all I get is that it is not recognized or not an executable file or whatever.... Can someone please offer some help here?? Thanks in advance

did you try to run abd from the /android-sdk/tools folder in the command prompt? and did you add the path to the enviroment variables?

I have tried to run it from the folder, and I thought I had it added but I'll double check...

OK, it's in the path now, but I still get a 'not recognized as an internal or external command, operable program or batch file.' I'm stuck in the mud, spinning my wheels....

I get the same thing with win7 I can get the command prompt android tools folder hit enter and it said 'not recognized as an internal or external command, operable program or batch file

Ooooh...I got it...had the cmd info in wrong folder...needed it in the same tools folder...thanks folks

Yeah, getting adb into your path is kinda hard the first few times. I add it to both of my Paths and then reboot. If you follow the documentation on the Android site, it usually works after a reboot.
To make sure its just a path issue, you go to your sdk folder and navigate to tools (in the command prompt, of course, which is done by "cd \path\to\sdk\tools\") and then typing adb. If that works, then you type adb devices and make sure your phone is found. If that works, then all you need to do is finish the path installation and reboot. That's usually how I get it. Once on your path, you can adb shell from any location on your computer, which is nice when you want to push files to your phone.

G2; How to initiate/ launch adb

ok,,,noob here.. but not a dummy. I want to load music on my sd card. I have downloaded everything I think I'm supposed to have.. SDK, adb, drivers eclipse java program...I'm running vista 32 and have created C:\program files\Android\android-sdk-windows. I have extracted all files I think all the drivers. I have spent some considerable time (wee hours ..) I can start the sdk .exe and the java eclipse but how do I use it to connect to my usb connected phone? I want to load data onto my sd card. BTW I have temprooted with VISIONary r14.
The cmd prompt window that comes up with the sdk .exe does not respond to typing in it. Commands typed into the computer's cmd prompt are not recognized. Or maybe I'm typing the wrong thing. I can't navigate to the android folder, to find my usb'd phone. I have read a lot of posts here trying to figure this out..I'm really at wits end anybody please help!!! I thought there'd be a desktop lauch icon..haha.

There's a guide for using ADB in the dev forum: http://forum.xda-developers.com/showthread.php?t=865685
If you are just trying to put music on your SD card though, I don't think you need to do all of this. Just mount the SD card once your phone is connected to your computer (there will be an option that appears in your notification drawer to do this). Your SD card will then show up as a drive on your computer...

I saw that guide..Step 4 doent apply on vista.."My Computer" and the path that is described is not on Vista, or anything similar. I can't "update your Path variable." It did not say HOW TO LAUNCH! What is it application that I need to work from for adb? I have read every post I could find here..and that one maybe four or 5 times. I want to use adb I can see and browse my SD card as drive F..thanks..I still want to run adb.. I cant type into the sdk cmd pane.

captmack007 said:
I saw that guide..Step 4 doent apply on vista.."My Computer" and the path that is described is not on Vista, or anything similar. I can't "update your Path variable." It did not say HOW TO LAUNCH! What is it application that I need to work from for adb? I have read every post I could find here..and that one maybe four or 5 times. I want to use adb I can see and browse my SD card as drive F..thanks..I still want to run adb.. I cant type into the sdk cmd pane.
Click to expand...
Click to collapse
Whoa whoa whoa! If all you want to do is load music on your phone and your using Windows, either just install Doubletwist on it. It's kind of like iTunes for everything. Or just make a music folder and load your music onto that. No adb needed.
Now, about adb; there is no program to run. You don't really need to set your path either, it just makes things easier. Just cd to the sdk tools folder.
Sent from my HTC Vision

It's not all i want to do...i should not have mentioned it.
cd to the ??
If I wish to make an adb command, what and where do I go/do to do that....on a vista puter....thnkx
I can see tghe adb android interface is there ...I figured out to right click on "computer" "manage", which opens Computer Manager. There in the left column is "Device Manager" clicked on that and I see the Android Phone listed, with subcatagory android adb interface. and down at the bottom under "Portable Devices" HTC is shown. All drivers are showing up and say they are functioning properly.
appreciate the help..

captmack007 said:
It's not all i want to do...i should not have mentioned it.
cd to the ??
appreciate the help..
Click to expand...
Click to collapse
Oh I see. You first mentioned simply putting music on your phone and the next thing you've got a full development emvironment! Lol!
Cd to the tools folder of the android sdk. (Bear with me as I haven't done this on windows in a good long while). For example, open command prompt, then type "cd C:\androidsdk\tools", where the androidsdk part is whatever the sdk is called.
Sent from my HTC Vision

Once you have the android sdk on your computer- change the folder name to something simple so typing is easier. You'll also want to edit the enviornment variables (google is your friend, but I'll post a link tomorrow to help). The latest sdk is missing a dll file - I'm sure one of us can upload it, I just don't remember which one it is right now.
Now that you've got that done open command prompt an type:
cd c:\where\you\put\it (the sdk)
Then type:
adb devices
Or
adb start-server
If you get an error it means you did something wrong.

"cd C:\androidsdk\tools
I'll ad that to the list of command that do nuttin...lol
I downloaded all the sh*t I was told in these threads to dowload...yeah..everything to create an app. lol
I still am waiting to read or be informed of the precise command line that will let me into adb... tfn

thks KCRic... I will give that a shot.. nice tip on renaming the folder..I did not type cd C: first.. (the tuts I've been rackin my brain on did not say that..
I had read that it was missing and found it downloaded it and put it in tools..
the edit the environment variables is what I can't find where to do that.. thanks.
I added the missingAdbWinApi.dll and AdbWinUsbApi.dll and Adb.exe (of course) into the tools folder...

I renamed the folder in Programs\Android..."android-sdk-windows" simply "sdk"
I typed in:
cd c:\program files\Android\sdk\tools
I got in..opened a port..gave me my phones serial #
so this is where adb commands are made? (stupid question perhaps)
I thought the other cmd screen that opens with the sdk.exe was it. And I cant type anything there anyway.

If you have got "adb devices" to show you your phone's serial number, then adb is working find, and you can start using the other adb commands.
Sent from my HTC Desire Z

captmack007 said:
I renamed the folder in Programs\Android..."android-sdk-windows" simply "sdk"
I typed in:
cd c:\program files\Android\sdk\tools
I got in..opened a port..gave me my phones serial #
so this is where adb commands are made? (stupid question perhaps)
I thought the other cmd screen that opens with the sdk.exe was it. And I cant type anything there anyway.
Click to expand...
Click to collapse
Just type "adb", no quotes, and that will give you an output of all the adb commands.

captmack007 said:
I renamed the folder in Programs\Android..."android-sdk-windows" simply "sdk"
I typed in:
cd c:\program files\Android\sdk\tools
I got in..opened a port..gave me my phones serial #
so this is where adb commands are made? (stupid question perhaps)
I thought the other cmd screen that opens with the sdk.exe was it. And I cant type anything there anyway.
Click to expand...
Click to collapse
Yeah you're up and running now. If you typed adb devices or adb usb and got it to list your phones serial # then it's connected and running.
As far as adb commands, you can type adb help to get a list of some and they're pretty easy. Some of them are:
adb push <path\to\file> <where\to\push> - copies files to your phone
adb pull <path\to\file> <where\to\put\it> - copies files from the phone to your computer
adb remount - remounts your device
adb reboot - self explanatory
adb install <path\to\file> - self explanatory
adb start-server - starts adb service
adb kill-server - kills adb process (I always type this in when I'm done, sometimes it doesn't terminate and causes issues)
adb shell <linux type command> - runs command in the device shell
adb shell [enter] - operates in the devices shell until you type {exit}
Once you enter the shell you can type {su} to enter superuser. All commands in the shell are in linux format so if you're unfamiliar with that then do some reading.
HERE is a link that should help with adb also.

KCRic said:
As far as adb commands, you can type adb help to get a list of some and they're pretty easy. Some of them are:
adb push <path\to\file> <where\to\push> - copies files to your phone
adb pull <path\to\file> <where\to\put\it> - copies files from the phone to your computer
adb remount - remounts your device
adb reboot - self explanatory
adb install <path\to\file> - self explanatory
adb start-server - starts adb service
adb kill-server - kills adb process (I always type this in when I'm done, sometimes it doesn't terminate and causes issues)
adb shell <linux type command> - runs command in the device shell
adb shell [enter] - operates in the devices shell until you type {exit}
Once you enter the shell you can type {su} to enter superuser. All commands in the shell are in linux format so if you're unfamiliar with that then do some reading.
HERE is a link that should help with adb also.
Click to expand...
Click to collapse
Apologies if you've seen it already, but most of that is covered in the adb guide on the dev forums, with that link also - http://forum.xda-developers.com/showthread.php?t=865685

Thanks for the great info... Now I'm standing at the gate (maybe the precipice..lol)
As far as completing the pathway...
I found (through excrutiating trial and error) the Vista path for step 4 on that tut.
So under "Environment Variables" there are two editable windows, and the bottom with the "Path" that the tut says to edit says to ad the path to the tools folder and the platform folders...
The question is, when I double click to edit the Path line,(C:\Program Files\JavaFX-sdk1.3....) it changes to a different path (~1C:\Program Files\Quicktime\QTSystem\
So am I to delete that line and ad a new path or ad to the Quicktime line..
ty

The existing path was probably just too long to show up on the screen (so you saw the beginning of the line initially and the end of the line when you tried to edit it). Just add a semi-colon and then the path you want to add. You don't want to delete what you already have there since it might mess with other software installed on you computer.
So for example:
...C:\Program Files\Quicktime\QTSystem\;C:\android-sdk-windows\tools

Quicktime and android are both separatefolders under program files... so....no.. that's not it. I don't even know why java showsthere... my sdk is in C:/Program Files/Android/sdk/tools...
p.s. how you do backslash on this keyboard....lol
Sent from my T-Mobile G2 using XDA App

The path is simply a listing of directories separated by semi-colons. When executing a command, Windows will check the local directory you are in first for the program, and then parse through the directories listed in your path. This is why this step is even needed (it allows you to run adb.exe from any directory instead of always having to change to the tools directory). This is also why I said it's not a good idea to simply delete what is already there. You just want to add the tools directory where adb.exe is located to the existing listing.
So in your case, the end of the path variable will look like this:
...C:\Program Files\Quicktime\QTSystem\;C:\Program Files\Android\sdk\tools
Alternatively, you could stick it in the beginning of the path (so double-click to edit the variable, hit Home to go to the beginning, and add the directory there with a semi-colon). It should look like this in your case:
C:\Program Files\Android\sdk\tools;C:\Program Files\JavaFX-sdk1.3...
And there is no backslash on the G2 hardware keyboard (as you noticed), but you can access it by hitting the Alt key and then space to pull up a dialog box of additional symbols.

Word of advice to anyone reading this:
When adding the adb to your path make sure and don't put a space after the the semicolan. When I set mine up I spent 4 hours trying to figure out why it wasn't working, and it was the stupid space lol.
I haven't looked at the wiki since I did it back in October so maybe they've updated it to be clearer but just want to throw it out there.
Sent from my HTC Vision using XDA App

Properly rooted?

I was trying to do the radio s off with visionary and something went wrong.
I downloaded visionary+ onto my Telus HTC Desire HD no problem, I had rooted it earlier and beleived that to be done correctly. I was getting ready to flash my radio and was going through the steps to do so when my problems began.
Now, all that happens is VISIONary+ keeps on rebooting. I have tried pulling the battery, I have tried to change my settings (re: usb debugging) but nothing seems to help.....all it does is continously shut back off and try to reboot.
Any help would be greatly appreciated.
Update: This issue has been resolved. I am now trying to figure out if my phone is properly rooted...go to page 2 in thread please

What is your build number in settings>about>software information? Anything higher (and including) than 1.7 will cause Visionary to fail. Then you have to downgrade first.

OK, that is my first mistake, my Build # is 1.84.61.2.
I will attempt the downgrade and report back here

I am at the downgrade prompt. When I put in the command "adb push psneuter /data/local/tmp" I get a message saying "'adb' is not recognized as an internal or external command, operable program or batch file"
What did I do wrong?

bleagues said:
I am at the downgrade prompt. When I put in the command "adb push psneuter /data/local/tmp" I get a message saying "'adb' is not recognized as an internal or external command, operable program or batch file"
What did I do wrong?
Click to expand...
Click to collapse
download android sdk first
http://developer.android.com/sdk/index.html
put your command to the folder .. for example if u extract to desktop with folder android, then go to command prompt, point to the folder first
e.g: "cd desktop" "cd android"
p/s: put the file inside the folder too

Thanks Hayday, this dosen't seem to help though.
I have the Android SDK in my C: drive and I have placed the "downgrade" folder inside of it. And I still get the same error of "adb' is not recognized as an internal or external command, operable program or batch file" when I type the "adb push psneuter /data/local/tmp"
Any other suggestions?
I believe it still may be a driver problem. I keep getting a message from HTC Sync that says "HTC sync port of ### is not responding. Please disconnect cable and reconnect after 10 seconds"
Can I use the program terminal emulator to do this directly on the phone?

does the folder have adb.exe in it ?
if you place the android sdk folder in c for example the folder name is "android" , you just go to cmd .. then type "cd c:/android/"
and then type "adb" ..
you must use the command inside c:/android .. not c:/android/Downgrade
to be safe, just copy everything in "Downgrade" folder and paste to android sdk folder too ..
btw, here is the full thread by jkoljo himself on how to downgrade.
http://forum.xda-developers.com/showthread.php?t=905003&highlight=downgrade

I have done exactly as you say, I have the "downgrade" folder inside of the "AndroidSDK" folder....and still get the exact same message of "'adb' is not recognized....."

I cannot post a question in that other thread because I have fewer than 10 posts. I will as soon as I get up to 10.

Download & install htc sync, this should include all the drivers you need.
I think you need net framework 3.xx installed as well.
Then in cmd, go to where you put the downgrade file (cd blah blah) - http://forum.xda-developers.com/attachment.php?attachmentid=483902&d=1294492245 - & then the command lines should work.

arlrb said:
Download & install htc sync, this should include all the drivers you need.
I think you need net framework 3.xx installed as well.
Then in cmd, go to where you put the downgrade file (cd blah blah) - http://forum.xda-developers.com/attachment.php?attachmentid=483902&d=1294492245 - & then the command lines should work.
Click to expand...
Click to collapse
oh forgot to mention. download and install htc sync for the driver.
http://www.htc.com/www/supportdownloadlist.aspx?p_id=324&act=sd&cat=all

bleagues said:
I have done exactly as you say, I have the "downgrade" folder inside of the "AndroidSDK" folder....and still get the exact same message of "'adb' is not recognized....."
Click to expand...
Click to collapse
adb.exe is found in platform-tools folder in the android-sdk folder.
Add it to your path. Eg: PATH=c:\android-sdk\platform-tools;%PATH%

Thanks arjunr, after a little bit of tinkering with some files and folders I got it!
Thanks!

Now that I have the proper build #, I want to make sure my phone is properly rooted......or do I have to re-root it?
Is there any way to check and see if my phone is properly rooted?
I had rooted it before I did the build downgrade, does this make a difference?
My phone out of the box was a HTC Desire HD by Telus. The rooting that I followed was the http://forum.xda-developers.com/showthread.php?t=954997"which is the "[GUIDE] Telus Desire HD - Rooting and Flashing" found here on this website

I am good to go, I am rooted and downgraded!

bleagues said:
I am good to go, I am rooted and downgraded!
Click to expand...
Click to collapse
yeah now you can proceed with s-off, and flash new roms if you like.

Heydayat, I seem to be having some issues with anything internet related. I have started another post at http://forum.xda-developers.com/showthread.php?t=1012754 can you take a look at this and see if you can help me?
Thanks
Update: I have fixed the issue at the other thread, it was my APN settings.
Thanks to all for the help

ADB Help

I cannot figure this out to save my life. I have downloaded and installed HTC Sync. I have the folder for android-sdk setup on my local drive. I added the environmental settings so I don't have to change directories each time.
I connect my phone with USB Debugging enabled, and then open command prompt. I change directories to E:\android-sdk\tools (My "E" drive is my default drive). Anytime I try and "Adb" command, it says that ADB isn't recognized as a command. I don't know why. Cannot figure it out to save my life.
I've attached some pictures so you can get a brief idea as to what I am talking about. I am on Windows 7 32 bit, if that makes any difference.

The first thing I noticed from your screenshot that is that you dont have adb application in your sdk tools folder.

adb has moved...try the platform-tools folder instead of just tools.

*Sigh*
I would miss something as simple as that. It's working now, thank you guys.
Edit:
One more question.. I am trying to install the "com.skype.raider-all-in-one-camwidth". I am assuming I need to use ADB to push it to the system files, but how do I go about doing that from CMD? Probably incredibly simple, but I'm lost again. Lol

dpilcher said:
adb has moved...try the platform-tools folder instead of just tools.
Click to expand...
Click to collapse
I wonder if the adb_has_moved.txt file in his screenshot might have given him a clue?!?

JimSmith94 said:
I wonder if the adb_has_moved.txt file in his screenshot might have given him a clue?!?
Click to expand...
Click to collapse
Lol I admitted it was something stupid to miss, forgive me.
Can anyone help me with the file pushing though? I am trying install that Skype .zip file, and I'm assuming it has to be pushed to the system area. Any clues as to how I go about that?

If you need to get it into system apps,
Adb push filename /system/app
Make sure you put a space between the end of the filename and the /
And make sure the file is located in the platform-tools folder.

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.