Related
What do you guys use to access the system folder on your PC?
Basically, I want to have a play with a few of the files etc, but how do I get them (eg. Rosie.apk) onto the PC?
Is there software to do this, or do I have to use command line?
Many Thanks
You can pull the files from the phone by using the "adb pull [FILE]" command from the command line.
You'll have to have HTC Sync drivers and ADB on your system before that.
Is this the only way/easiest way? I'm asumming to send back I would use "adb push"?
Ease is a relative term so I cant judge on that basis.. Personally I find using the command line rather easy and fun.
Another possible way would be to use an app like Root Explorer on the phone to copy the system files on to the sdcard and then access the card via PC. (More cumbersome I think)
And you're right.. "adb push [FILE] [PATH]" is the command to send the file back to the phone. Try typing just "adb" and hit enter to see a list of commands and their usages.
Stuck at the first hurdle....
I've got the ADB on C:\ root
I open command prompt, type cd c:\adb
This puts me into the abd directory OK.
I type adb, and it adb is not a recognised command???
You sure you've got adb.exe and the dlls in that same directory?
I've attached a zip for you. Extract it and double-click on StartHere.bat, you'll get a command window and you can start using adb right away.
Cheers, I must have had a missing .dll
download Samba app: http://forum.xda-developers.com/showpost.php?p=8239139&postcount=128
this gives you access to the sdcard only, so to get access to system follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?p=18722729#post18722729
it works a treat! and is very easy! just be careful what you play with, using adb pull and push is safer
I agree that command line is the best way, but if you really want a GUI, then QtADB is pretty good:
http://qtadb.wordpress.com/
http://forum.xda-developers.com/showthread.php?t=683223
It's really just a graphical front end to adb.exe, but makes it easy to push or pull files to or from the phone. The only thing I haven't spotted is how to adjust permissions on files on the phone.
preacher65 said:
I agree that command line is the best way, but if you really want a GUI, then QtADB is pretty good:
http://qtadb.wordpress.com/
http://forum.xda-developers.com/showthread.php?t=683223
It's really just a graphical front end to adb.exe, but makes it easy to push or pull files to or from the phone. The only thing I haven't spotted is how to adjust permissions on files on the phone.
Click to expand...
Click to collapse
I didn't know about that.. I'll try that too. (Although I still think I'll end up to command line usage again)
Btw, APK Manager is quite useful if you're planning to mod some apk files like framework-res etc.. I use to make minor image changes to my ROMs..
if4ct0r said:
I didn't know about that.. I'll try that too. (Although I still think I'll end up to command line usage again)
Btw, APK Manager is quite useful if you're planning to mod some apk files like framework-res etc.. I use to make minor image changes to my ROMs..
Click to expand...
Click to collapse
Yep, I use the command line for 95% of stuff too - but then I'm old school and like the level of control command line gives.
But QtADB is useful if you want to move lots of files about, and as a bonus it has good logcat functions. Plus the support in the thread is pretty good as well. The guy really cares about his app, so I like to let people know about it.
APK Manager is awesome as well, though lately I've been going hardcore and doing everything apktool related from the command line as well!
I need some help accesing the system folder
Hey guys I am pretty new to android, I had been dealing with WebOS devices, I recently gotten a irulu a20 (all winner device) android 4.2.2 and wanted to improve the gaming performance and followed this instructions http://forum.xda-developers.com/showthread.php?t=2329080 and now my tablet does not stop popping a message saying "unfortunately System UI has stopped" and does not let me do anything or select anything. One of my friends did a wipe data/hard reset on it and still giving me the same issue with the same message, and what is worst I don't see the root browser icon (I guess due to the hard reset) so I don't know if my tablet still rooted or it is bricked. Please help and thank you to those who reply
I realize the phone uses MTP now which IMO is a complete downgrade from the whole Android experience when it comes to moving the files you want.
Right now, I'm trying to figure out how to move a 1.5 GB file (Nandroid backup) to my desktop without going over wi-fi since that will take... I don't even know how long. I let it sit for about 35 minutes, and it only got to about 90 MB.
I have 3 freaking folders I need to view to get my Nandroids, but I can't get to them due to the fact that I can't access them any other way than Wi-Fi. Seriously, what can I do to make these stupid folders show up in MTP?! I've tried moving them and renaming them and putting them in different directories that show up in Windows, and I can't see them at all.
What do I have to honestly do? This is just ridiculous.
you could always use "adb pull". It'll be slow (that's just how ADB is) but you'll be able to do it.
use it like this:
Code:
adb pull <Nandroid File> <to this directory>
for example:
Code:
adb pull /sdcard/thisfile.zip thisfolder
will create a folder named "thisfolder" in your platform-tools folder (where ADB is located) with thisfile.zip inside it.
martonikaj said:
you could always use "adb pull". It'll be slow (that's just how ADB is) but you'll be able to do it.
use it like this:
Code:
adb pull <Nandroid File> <to this directory>
for example:
Code:
adb pull /sdcard/thisfile.zip thisfolder
will create a folder named "thisfolder" in your platform-tools folder (where ADB is located) with thisfile.zip inside it.
Click to expand...
Click to collapse
+1
Sent from my Galaxy Nexus using xda premium
Sorry for posting stupid questions: Even windows based apps like myphoneexplorer don´t work, do they?
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.
So, I have been theming a few aspects of my phone (very minor), but one thing I had wanted was to completely remove the statusbar as I really wanted that extra space, and I found it was very unneeded for my frame.
I did some Googling till I found a couple of sources, and dove in. A few stressful hours later, I had no status bar, but could still use gestures from Nova / Pie to access it when I wanted to.
I am not the greatest at explaining things, but hopefully I will convey the steps on how to do this easily.
Pre-Reqs:
1) ADB installed on Computer
2) Windows
-That's what I used. I'm sure it's possible to use a Mac, but this guide is solely for Windows
3) Rooted
-Not tested on non-rooted
4) 7zip (I found it worked better than winRAR for this)
5) Download this file: http://www.speedyshare.com/n6ahB/download/resources.arsc
-This file is the file with all the measurements inside it that is taken from my Note 2
-Click the file name on the very top of the link to start the download. Tricky Ads
Because the file I edited contained very basic sizing, dpi, etc information, it should work on any custom ROM that is 4.1.2 or 4.2.2. I am currently running Team Whomps 4.1.2 ROM (V. 4.2).
The file that I edited should in no way brick your phone. Worst case scenario, it may cause boot loops. But, as always, I am not responsible for what happens to your phone if it does burst into flames, or any other negative scenario.
Steps:
Optional (Recommended): Make a nandroid backup before proceeding)
1) Boot your phone into recovery and make sure your system / root is mounted to your computer on your recovery screen
2) Connect your phone to your Windows PC
3) First, make sure it is showing up on ADB by opening up command prompt on your PC, and type "adb devices" - without quotes
-If it doesn't show up, make sure drivers, etc, are installed and don't continue until it shows up
-If it DOES show up, please continue
4) Change directories to your C drive by typing in command prompt: "cd / " without quotes, and a space in between the 'cd' and '/'
5) Now type the following commands in command prompt:
Code:
adb remount
adb pull /system/framework/framework-res.apk
(Once it fully transfers the ~24Mb, Continue)
adb shell
cd /system/framework/
rm framework-res.apk
Now, you have the framework-res.apk file on your computer's C Drive, and have removed it from your device. Close the command prompt.
6) Make a backup of this framework-res.apk file just in case this doesn't work for you, you can push your old framework back to your device.
7) Right click on the framework-res.apk file, and click "Open Archive"
-I don't recommend extracting it, then rebuilding it, as that caused boot loops for me. So, just open the archive so you can see the inside of the file
8) Click on the "resources.arsc" and delete it from the archive.
9) Drag the "resources.arsc" that I PROVIDED into the archive. It should give you a prompt, asking if you are sure to add it. Click Yes.
10) Exit out of 7zip. Now we need to push this file back on our device.
11) Upon up command prompt, and type the following commands:
Code:
adb push framework-res.apk /system/framework/
adb shell
cd /system/framework/
chown 0.0 framework-res.apk
chmod 0644 framework-res.apk
This sets the permissions on the apk file, and pushes it to where it is supposed to be on your device.
12) Close command prompt, and on your device wipe cache/dalvik
13) Reboot
The first time you boot, it will take a little longer than normal. It may freeze for about 5 seconds when loading apps. Just give it a minute.
If you have waited longer than 5 minutes, then reboot into recovery and "Fix Permissions" and reboot again.
If it still doesn't work, then let me know and I'll post a guide on how to modify your own "resources.arsc" file from your own "framework-res.apk" file. You will have to repeat the above steps, deleting the "framework-res.apk" file on your device, and then pushing the "framework-res.apk" file that you had backed up back onto your device. Then everything should be back to how it was.
Let me know if this helped anyone! . I know that statusbar was driving me crazy, personally.
REMEMBER, because the status bar is no longer "Click-Able" - you can't pull it down anymore. You have to use PIE / Gestures / Apps to force pull it down in order to go to your Toggles, etc.
BUGS:
The only bugs I have experienced after a day with this MOD, is that once you use PIE / Gestures / Etc to pull down the notification bar, you can no longer push it back up by flinging it. Instead, you have to hit the "Back" button. Not a huge deal, but thought I'd mention it. I think if I adjust the DPI of my screen to account for the loss of the status bar (which had a width of 25 units), it may work again.
Reserved in case I add additional information
This is very interesting, but only something I would really want with the stock rom. I'll have to do some testing then....
rawdikrik said:
This is very interesting, but only something I would really want with the stock rom. I'll have to do some testing then....
Click to expand...
Click to collapse
I personally love it.
Here is how my screen looks with no status bar on a couple apps. I like the extra space.
It would be good with auto hide! !!!
Sent from my Atari
Hi
I have attached my resources.arsc. Could you help me with how I can mod this.
Thanks in advance.
Do ever know some app which could see data on watches? I find only "File Manager For Android Wear" but it could see only file on sw on watches but how to copy/paste/delete files form/to watches to/from PC or android?
Adb would work.
ADB commands
Thank you for answer but I don´t know right commands or functions for ADB please could you help me with this?
Thank you very much.
Certainly,
So, first you have to enable adb on the watch. To do so, go to settings then about then tap the build number a bunch of times. Then, go to developer settings and enable adb debugging.
Then you need to set up adb on your computer. It is a little involved, but there are directions online. I can help with this, but is a topic for another post. Let me know if you need it.
Okay, you have adb and you have enabled it on the watch.
Now, just plug the watch into the computer. If you are on Windows and did not add adb to your path, open the platform-tools folder in Windows explorer. Type cmd in the explorer bar and it should open a terminal window.
Okay, now the commands are easy. I have not done this on the watch yet, but this should work.
First, to ensure that adb is working, type...
Code:
adb devices
You should see a string which represents your watch.
It may say unauthorized. If so, look at your watch, and authorize adb.
Code:
adb ls /
This will list the contents of your root directory.
Unless you are rooted, you cannot write to this folder, but you can now read the contents of the watch. I am assuming you want to put music or some such on your watch, so navigate to your sdcard...
Code:
adb ls /sdcard/
And you should see the contents of your sdcard (even though your watch does not have an sdcard, it should have a partition on the internal memory called sdcard). This is where you can put your files.
If you are new to terminal, you can easily get back to the last commands by pressing the up arrow at the prompt.
Now, once you find a place to put your digital goodies, you can run this command.
Code:
Adb push (local file, files, or folders) (folder on the watch where you want them to live)/
replace the words in parenthesis as well as the parenthesis, with the full paths. There are shortcuts here too.
Use the up arrow to get the path on the watch, and then...
You can drag a file from Windows explorer to the terminal window to get the local path. Drop it before the path on the watch.
Let me know if this does not work or you have questions...
Good luck.
Leko
Edit: I tried it and modified my instructions based on the specifics of our watch. This does work.
Thanks
This is exactly what I want to know Great work. Thanks a lot.
Total Commander plugin
It works great I am Total Commander user and plugin is alredy exist
http://forum.xda-developers.com/showthread.php?t=2105707
Wonderful! I am glad it helped. Total commander is an excellent idea. Now we have a gui way to do this.