Hi guys I want to install keyboardmanager by installing from /sys/app try as I may i just can't move any apk into the root sys folder. Have read write permission in the folder but after paste or copy request the file remains on the sd. Can copy files from sd to /.
Have searched and searched but can't find out why I can move files to this path. I need access as would like to remove some stock apps also.
Rooted with evoke and am running a desire with cyanogen 6.1.0 stable and clockwork mod recovery 2.5.0.7
Any help would be much appreciated.
Q&ASent from my GT-P1000 using XDA App
Are you S-OFF?
If not you do not truly have RW access, just the appearance of it in File Explorer.
Try booting into recovery and using adb to move it, or go through the steps to S-OFF.
Try copying it to /system/app/
Not /sys/app/...wrong place.
Mercianary: I think he used sys as short for system.
To answer the question. The desire is nandlocked so even with root you can't write to system while it is booted. You need to hack the phone on bootloader level (get s-off) to gain this write access.
@cwakerly From what i understand, you are trying to install an apk from your sd card to /system/app while the phone is on and running? As suggested above, you cannot do this via a File Explorer app unless you have full root to the /system partition (S-OFF). Try it via ADB instead and follow these steps:
Perform a Nandroid backup first just incase anything were to go wrong.
1. You need to have USB Debugging enabled, HTC Sync and Android SDK installed (http://developer.android.com/sdk/index.html).
2. To get adb running on the Windows OS platform, for example, download & extract the Android SDK to the following path: C:\android-sdk-windows.
3. Turn on your phone and connect it to your PC via a USB port, and then boot into Recovery mode..
4. Instead of placing the apk onto the SD card, place it into C:\android-sdk-windows\tools in Windows.
5. Open command prompt and type cd C:\android-sdk-windows\tools, hit enter.
6. Type adb shell mount /system, then hit enter, to mount the /system partition.
7. Type adb push keyboardmanager.apk /system/app, hit enter.
8. Type adb reboot.
Let me know if that is what you meant and if it works for you.
Hey guys thanks so much for suggestions will try them and let you know if it works
Sent from my HTC Desire using XDA App
hi i have installed sdk, htc sync and java plug ins.
using command line when i try to run adb shell mount /system command i get the following error message:
'adb' is not recognised as an internal or external command. operable program or batch file.
any ideas what's happing here?
Have you navigated to the tools folder of the sdk?
Mine is C:\android-sdk-windows\tools
Yours maybe something similar....
Sent from my HTC Desire using XDA App
cwakerly said:
hi i have installed sdk, htc sync and java plug ins.
using command line when i try to run adb shell mount /system command i get the following error message:
'adb' is not recognised as an internal or external command. operable program or batch file.
any ideas what's happing here?
Click to expand...
Click to collapse
try it in smaller chunks, type adb shell, you will then get a # sign, now type mount /system
hi have navigated to tools folder of sdk, still the same error message. when i type adb shell i get the same error!
If you have latest sdk you need the "other" tools folder. I'm not at my pc so I'm not sure the exact name.
Sent from my HTC Desire using Tapatalk
if you haven't got it done yet use this update.zip
open the zip then put the apk you want to install in /system/app then zip it back up. it wont be signed so turn off signature verification in recovery before you flash it.
Hurray using the update zip worked!! Thank you everyone for your help on this
Have a great Christmas.
Craig
Sent from my HTC Desire using XDA App
Related
i was tolf to move this here this is a question ,,,idk how to do step 5..it has to do with movin file to sd card im guessing..idk help me?
help me root my phone i dont understand this im really f'd up this is like dsa adveture
ok here is the problklmemo
"Step 5: Plug your phone into the computer via USB, Make sure that the connection type in the Notification Pull-Down Bar is "Charge Only", not "Disk Drive" or else this won't work.
If your computer asks you to restart after the new drivers were installed, do that now
Once ready, type these commands in cmd prompt from your adb tools directory.
Code:
adb push unrevoked-forever.zip /sdcard/
adb push flash_image /data/local/
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb push mtd-eng.img /sdcard/
adb push PC36IMG.zip /sdcard/"
oksssssss now..one person say i right click on tools and open cmd,,,so i dids that
then i type it in and its doesnt work..it says adb or abd waterver it is is not a command and its not reconixed...help me please!!!thanjs
i have windows 7 64 bit
Did you do ALL of this first?
Step 1: Download the Android SDK here
Step 2: Extract the Android SDK zip. Move the contents of the extracted zip to C:\
Your Android tools folder path should now be C:\android-sdk-windows\tools
Step 3: Download HTC Sync 2.0.40 here
Run the installer. Move on once installed. If reboot is required, do so and then move on.
Download my evo-root.zip.
It contains a few files necessary to root the EVO.
Unzip the contents of the zip to your android sdk tools folder.
Download the unrevoked-forever.zip
Place this zip in your tools folder as well, as a zip, not extracted.
Download this PC36IMG.zip (This is the same as running an RUU, so it will delete all of your user data when we use it later in the guide, so backup everything you want to save on your phone first)
Put this zip in your sdk tools folder as well, as a zip, not extracted.
After unzipping the contents of evo-root.zip to your android sdk tools folder and placing the PC36IMG.zip and unrevoked-forever.zip in the folder, move on.
Click to expand...
Click to collapse
You need to change the directory to your tools fold so that the computer can execute advanced commands. Look for a thread about setting up adb. In the thread it will tell you the steps to do so. I would post this for you however I do not have access to a computer and I am use to using advanced on a Mac.
Sent from my PC36100
nebenezer said:
Did you do ALL of this first?
Click to expand...
Click to collapse
yes i did i had no problems untill step 5
Read my post in the thread you created in development.
So everything gone fine till I try to push the framework-res.apk to my phone.
adb push framework-rez.apk /system/framework/
'adb' is not a recongnized as an internal or external command,
know I understand what that means but I installed SDK manager and had no cmd in there so I just used Command Prompt. If that is all of my problem how to I get SDK cmd? It didnt install when I installed the problem.
Omnicide said:
So everything gone fine till I try to push the framework-res.apk to my phone.
adb push framework-rez.apk /system/framework/
'adb' is not a recongnized as an internal or external command,
know I understand what that means but I installed SDK manager and had no cmd in there so I just used Command Prompt. If that is all of my problem how to I get SDK cmd? It didnt install when I installed the problem.
Click to expand...
Click to collapse
It's not enough to just install SDK manager, you also have to install ADB if you want to interface with your phone through your computer. You shouldn't have to go through SDK manager to use ADB once you have it installed, it should work straight through windows command prompt.
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
That will walk you through installing adb. Good luck.
yoft1 said:
It's not enough to just install SDK manager, you also have to install ADB if you want to interface with your phone through your computer. You shouldn't have to go through SDK manager to use ADB once you have it installed, it should work straight through windows command prompt.
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
That will walk you through installing adb. Good luck.
Click to expand...
Click to collapse
Well thank you that helped me get pass that issue. Now how do I change the permissions on my phones framework-res.apk?
The error I have now is
"failed to copy 'framework-res.apk' to '/system/framework/framework-res.apl': Read-only file system."
I can't seem to figure a way around this.
Omnicide said:
Well thank you that helped me get pass that issue. Now how do I change the permissions on my phones framework-res.apk?
The error I have now is
"failed to copy 'framework-res.apk' to '/system/framework/framework-res.apl': Read-only file system."
I can't seem to figure a way around this.
Click to expand...
Click to collapse
I had that issue too, how I bypass it is to boot to CWM, go to "mounts and storage", then mount /system (and /data if that's relevant to what you're pushing). Others have used a line of code to mount the system from the PC end, but I find this easier to do through the phone.
yoft1 said:
I had that issue too, how I bypass it is to boot to CWM, go to "mounts and storage", then mount /system (and /data if that's relevant to what you're pushing). Others have used a line of code to mount the system from the PC end, but I find this easier to do through the phone.
Click to expand...
Click to collapse
Thank you that did the trick
Go to the system32 folder on your c drive and copy cmd from there to your tools folder in the sdk.
Now when you want to push, put the files you want to push in the tools folder and then open up the cmd that you placed in that folder, then run the push command.
Sent from my Galaxy Nexus using xda premium
Master&Slave™ said:
Go to the system32 folder on your c drive and copy cmd from there to your tools folder in the sdk.
Now when you want to push, put the files you want to push in the tools folder and then open up the cmd that you placed in that folder, then run the push command.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks ill give that a try in morning. That would be a better then how im doing it now my stuff is in all random folder and locations to get it to work.
Sent from my SGH-T989 using xda premium
Omnicide said:
Thanks ill give that a try in morning. That would be a better then how im doing it now my stuff is in all random folder and locations to get it to work.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
That's actually how I do it so it should work for you. Good luck
Sent from my Galaxy Nexus using xda premium
Master&Slave™ said:
That's actually how I do it so it should work for you. Good luck
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It worked for the file being in that folder and all. But I still have to do it in recovery and unmount system. I still get the read-only error
I wanted to change my device model, so I copied build.prop from another mobile to my mobile. I am already rooted. But unfortunately I did not change the o.s. from gingerbread to froyo in build.prop ( I have android 2.2 FROYO) When I rebooted, there were many errors. It is now showing no sim card. Mobile network search gives error. Effectively, I can not use the mobile. Terminal emulator, X-plore etc. stopped working. Only Rom toolkit free version works and astro file manager works. Other programs are forcefully closed. Needles to say, I must replace new build.prop with new one.
Using adb I can only pull files but can not write as it is in read only mode.
adb root and adb remount works only if you are in recovery mode ? Y mobile does not have any custom recovery so when I boot in recovery mode it hangs.
Superuser has installed su in system\bin directory. But from adb shell I can use su also. It gives permission denied error. Hence I can not remount the system.
I have read similar threads and found that on some mobiles adb root or adb shell su works but on some not.
I am using Vista 32 bit with admin rights, still can not use root in adb.
Please tell me, how can I mount system read-write. I can not install root explore as google play and even internet is not working.
Please help.
maheshchavan said:
Using adb I can only pull files but can not write as it is in read only mode.
Click to expand...
Click to collapse
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
ruscan.calin said:
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
Click to expand...
Click to collapse
OMG ruscan.calin i COULD KISS YOU! I had tried to change my OG EVO 4G's buildprop file to another phone so that I could purchase & download an incompatible Google Play app. However after I restarted the phone wouldn't start! It would boot into my rooted HTC EVO 4G Android 2.3.3 and HTC Sense 2.1 but it would get stuck on the wallpaper with just the notification bar at the top and all buttons would be frozen. However I noticed when I plugged in my phone to my computer via usb the computer recognized it. I always keep my phone with USB debugging enabled so I thought I should be good right? I have spent the last 4 hours trying to install and setup adb with no real previous experience with it. I am familiar with dos from years ago and that helped me as it's basic procedure, commands, etc. Then I found out how to install the HTC drivers which I needed and then download the Android SDK with adb that's included which many guides show easily. I started the command prompt (cmd), typed my adb devices command and hurray it showed my phone! I connected and quickly navigated to the build.prop system folder! Luckily when I changed the file I made a bak backup and left it in the same folder. Now the main issue was figuring out how to change the naming of the files which I did via usual adb commands (mv build.prop.bak build.prop). But then to no avail I couldn't get it to write due to it being a system read only folder! Arg! Then I found your post on here, above, and typed it in simply leaving out the adb push portion and replacing that with the mv file command instead and first changing the name of the bad file and then replacing the bak file as the good copy! I exited back to the adb main and unplugged my phone. Moment of truth and man was everything flashing through my head at once! I booted up and YESSSSSSSSSSSSSS, it worked! I went back into root explorer and got rid of the offending leftovers and I've learned my lesson! I just don't want to think about what would have happened if I hadn't found this post. Thank you and if anyone else makes this hug mistake let me know and maybe I can help. Moral of the story don't mess with the build.prop or any system folder unless you know what you're doing! Thanks again!
Quick Guide to Fix Android "build.prop" Issues:
1. Find and download USB drivers for your phone by model or type (HTC EVO 4G's HTC Fastboot drivers): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
2. Download and install Android SDK and choose adb: http://developer.android.com/sdk/index.html
Guide: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
3. Run a command prompt from the "c:/program files/android/android-sdk/platform-tools/" directory. I had to copy the command prompt to get it to open there but sometimes a right-click action will do it. The guide below will help just navigate down to "Using ADB" and skip the rest.
Guide: http://www.howtogeek.com/114667/how...y-default-move-almost-any-app-to-the-sd-card/
4. Once you open the command prompt and you're in the "c:/program files/android/android-sdk/platform-tools/" foler type "adb devices" and your device should appear. If it does move on to next step.
5. Then type adb shell and use the ls command to see directories. Then you'll need to navigate to the system folder by typing "cd system" and then type "ls" to look around in the directory (similar to "dir" in DOS). You should now see the bad build.prop file.
6. You'll need to rename the file or push a correct version. First you need to use the "adb shell" command again and then "su" and finally "mount -o rw,remount /dev/block/mmcblk0p1 /system" to make the directory writable (see ruscan.calin post above for additional info).
Note: I only had to rename my build.prop as I already had my old one in the same system folder. You may have to copy the bad build.prop to your computer, edit it and then push it back to the same system directory. These directions are only for renaming files in the same folder. For the info on how to copy the file to your computer and push it back to your phone go to step *10 below or use the guide below it.
7. I already had the bad build.prop in the system directory with my old one which I had named build.prop.bak. If you have this too simply rename by changing the name first of the bad file to anything by typing "mv build.prop build.prop.bad" or similar.
8. Next rename the build.prop.bak to build.prop by typing "mv build.prop.bak build.prop". Everything should go smoothly and move onto the next step.
9. Finally, If no error messages are found, simply type "adb reboot" or "adb shell reboot" (Depending which version of ADB you have). You should be done, your phone will reboot like normal (working, lol) and everything should be working again! YAY!
*10. To copy the build.prop to your phone type "adb pull /system/build.prop c:\" and the file should be placed in the main c:/ directory on your computer. Navigate to the root (c:/) directory and then right click and "open with" the "build.prop" file using a notepad or other file editor. Then use the text editor (Notepad, etc) to change back what you originally changed to mess everything up. There is tons of stuff on the net to let you know what to fill back in depending on your phone model/type. Or it's possible to get a previous version from an old Nandroid backup or similar. Save the changed text file and make sure its named the same "build.prop" and make sure it's still in the root directory (If you're having issues on this step or just want more insight check out the guides and threads below for more help).
Guide 1: http://androidforums.com/admire-all...p-computer-not-phone-using-root-explorer.html
Guide 2: http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Guide 3: http://forums.androidcentral.com/sp...-replaced-build-prop-phone-wont-start-up.html
*11. We've already made the directory writable in step 6 so we simply need to push the file back to the phone. If any error message appear re-do step 6 to make writable again. Otherwise push the modified file back to the phone by typing "adb push c:\build.prop /system/". Back to step 9 above! Yay!
If anyone wants to help cleanup this quick guide or make any changes feel free. I just wanted something so that if anyone else has this issue they won't have to worry or search forever to find a solution. OMG it's 2:30AM, to bed... I ride! LOL
Enjoy,
5th :highfive:
THANK YOU!!! Totally saved me today.
One thing that I noticed. After pushing the correct build.prop, I had to fully power down, then turn back on my Razr for it to load up the fixed build.prop.
error message,Help please
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
jigarpattani said:
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
Click to expand...
Click to collapse
What step are you on? What phone do you have? More info please?
i am have problem whit my pantech flex i need to use the build.prop.bak but when i type the su it stay in blank do nothing any ideas pls help
ehy there hope someone can help me...i have an archos 97b platinum, messed up with build.prop. So i pulled out and restored but can't push in any way. I have a cwm installed, tablet rooted but i alwais got "permission denied" at push command. Other error is operation not permitted" if i try remount command from adb. i can do mount -o rw,remount /dev/block/mtdblock7 /system but after that push still give me permission denied.
any suggestion?
http://imgur.com/FDLp4fl
i open a 2nd cmd, give the mount -o rw,remount /dev/block/mtdblock7 /system , and system is now rw, but from the first cmd when i give "push build.prop /system (or /system/build.prop) it will always return me permission denied
help
dev.block
i want to view to dev/block using adb shell #
eg . what block is boot.img
what block is recovery.img
what block is system.img
what block is cache.ing
adb shell getprop mtd is not work . Pls Help Me & sent to mail [email protected]
I have a major problem but i think there is a way to fix it, i just cant figure it out. i was adding google wallet on my rooted s3 and when reverting the build.prop file to its original form, i just copied and pasted the backup and renamed it to the original build.prop to replace the new one using root explorer. my phone does not boot up now i get the samsung startup screen and it shuts off. i could get into cwm recovery mode. any way to fix the build.prop without being able to fully boot the phone? i am on a mac but i could have access to a pc tomorrow if i need.
Its simple if u have a backup. I have not heard of anyway of getting to build.prop thru recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium
You need to restore from backup (nandroid) or start over if you don't have a backup..
Did you copy the original file to ur sd card then back over?
Chances are you did.. I did the same thing lol.. And when u do that it doesn't save original permissions of the file.
The reason the wallet post says to use root explorer is because it saves the file in the same folder permissions and all and you can just rename it back.
Sorry dude u are sol.. Restore from back up or flash a new rom and start over.
Sent from my SAMSUNG-SGH-I747 using xda premium
Get into recovery, do a factory reset.
mrhaley30705 said:
Get into recovery, do a factory reset.
Click to expand...
Click to collapse
Any resolution. I have the same problem.
mrhaley30705 said:
Get into recovery, do a factory reset.
Click to expand...
Click to collapse
I don't think that would work, as far as I know a factory reset only wipes data and cache. The build.prop is part of the system, so it will not change.
Sent from my SPH-D710 using xda premium
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
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.
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.
Side note--> twrp recovery has a built in terminal and the ability to copy/paste files from internal and external SD cards. Not so sure about changing permissions easily....but through the built in terminal....might be able to load what you need (plus twrp flashable found in android dev forum) on external SD card with an adapter on a computer. Flash twrp and transfer files or use built in terminal to change perms. Good luck....
I know editing build props with es file explorer will cause That.
Sent from my SAMSUNG-SGH-I747 using xda premium
Fixed it!
Thanks everyone for your help, i feel like an idiot for not replying to anyone i didnt have it set up to notify me of replies, i figured out it was the build prop that was messed up, im not sure how this worked but i figured i would try to root again and flash the root files using the simple root steps using odin and it actually fixed the file and booted up fine! i appreciate everyones help and hope this thread helps other people because i know many people screw this up the same way i did. (i will never do anything like this without doing a nandroid backup again). THANKS AGAIN!
thanks but..
ibanezbass said:
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
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.
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
So the problem with this route was that for some reason the device was not being recognized by adb, i dont know why, i thought it was a driver issue but once i fixed the phone, i was able to get adb access, so i guess that boot error was preventing it from getting recognized (which i didnt understand because my friend screwed up like me the next day and was able to adb.) but finally fixed it a few days later after trying many things and the fix for some reason was a simple process with odin, i think this article shows what i did, i dont remember exactly tho - http://smartphonefix.blogspot.com/2...r-Recover-Bricked-ATT-Galaxy-S3-SGH-I747.html
ibanezbass said:
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
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.
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
Okay, I got the adb shell to run, but I run into this snag:
"Unable to chmod build.prop: Operation not permitted"
Anyone know what this means?
prior to running that command, type su then hit enter
If I made a CWM flashable unedited build.prop from a stock SGS3 rom would that help anyone? It just seems easier than all those ADB commands assuming you can still access recovery.
stratatak7 said:
If I made a CWM flashable unedited build.prop from a stock SGS3 rom would that help anyone? It just seems easier than all those ADB commands assuming you can still access recovery.
Click to expand...
Click to collapse
I'm sure that'll probably helpful to a lot of people. Unfortunately, I'm using the stock recovery so it probably wouldn't help me...
lyrictenor1 said:
I'm sure that'll probably helpful to a lot of people. Unfortunately, I'm using the stock recovery so it probably wouldn't help me...
Click to expand...
Click to collapse
If you're not comfortable with ADB: You should try to flash recovery (recommended TWRP but at this point take anything you can get) from ODIN. I know I've seen it around here somewhere. Once you do that, then flash the attached file.
This will flash in CWM/TWRP etc. I haven't tested it, so send me a PM if it doesn't work and I'll fix it up.
Edit: I've located the proper recovery file for you to flash. It's cwm, but you flash this with ODIN. Download it from here http://k0nane.info/rom/ecm/CWM-Recovery-LTE-SGS3-v5.tar.md5 . ODIN will increase your flash counter, but Chainfire's Triangle Away app takes care of that like it never happened. Odin can be found in the development thread. If you want to automate this process even further just download the qcom toolkit which walks you through the process of installing recovery. I hope this helps.
Lastly, here's the latest TWRP image file with ADB instructions. Short, sweet and simple. http://teamw.in/project/twrp2/104
crammer04 said:
I have a major problem but i think there is a way to fix it, i just cant figure it out. i was adding google wallet on my rooted s3 and when reverting the build.prop file to its original form, i just copied and pasted the backup and renamed it to the original build.prop to replace the new one using root explorer. my phone does not boot up now i get the samsung startup screen and it shuts off. i could get into cwm recovery mode. any way to fix the build.prop without being able to fully boot the phone? i am on a mac but i could have access to a pc tomorrow if i need.
Click to expand...
Click to collapse
_________________________________________________________________________________________________________________
If you got no back up give us your phone information one of us can send you one I have aTT D2att you
?
Its all in my sig get mobile odin bellow, get the tar for which ever recovery you got. I got all three. CWM, CWM Touch and TWRP for d2att (only) if different phone then use other ones.
Thats my build prop im D2att SG3 ok so just make sure. But you can grab mobile odin bellow and fix it.
_________________________________________
Just get mobile odin HERE
and flash your reocvery there CWM, TWRP, CWM TOUCH... all of them latest all in my sig bro
Here is all drop box to get any of the recoverys --------------------> Recoverys Drop Box
Get mobile odin Here along with the s3 kernal extension its all in here -----------------------> Mobile Odin
If you get hardware id missing error install these old samsung dricers this is a bonus, don't update it ----------------> Hardware ID samsung driver fix
__________________________________________________________
S3 build prop here --------------> here
Mobile odin is simple if download zip in my drop box just install it (or get it form market) download the driver you need (in my drop box) or go mobile odin thread and find it if your on a different phone. Rest is simple just load what your going to flash click the OPEN FILE option in mobile odin click tar and run it.
_________________________________________________________
Get android comander. You can mod build prop easy with it its nice GUI for installing programs or uninstalling or backups or moving files around. awesome try out here --------------------------------> ANDROID COMANDER
need anything else?
---------- Post added at 09:42 PM ---------- Previous post was at 09:20 PM ----------
lyrictenor1 said:
Okay, I got the adb shell to run, but I run into this snag:
"Unable to chmod build.prop: Operation not permitted"
Anyone know what this means?
Click to expand...
Click to collapse
Tiy need to remount system Read Write i don't think its a SU problem it could be but normaly you already got su i forget comand in adv its mount system -r i beleive. I dunno I run a script that mounts it for me let me check it out real fast
---------- Post added at 09:48 PM ---------- Previous post was at 09:42 PM ----------
crammer04 said:
So the problem with this route was that for some reason the device was not being recognized by adb, i dont know why, i thought it was a driver issue but once i fixed the phone, i was able to get adb access, so i guess that boot error was preventing it from getting recognized (which i didnt understand because my friend screwed up like me the next day and was able to adb.) but finally fixed it a few days later after trying many things and the fix for some reason was a simple process with odin, i think this article shows what i did, i dont remember exactly tho - http://smartphonefix.blogspot.com/2...r-Recover-Bricked-ATT-Galaxy-S3-SGH-I747.html
Click to expand...
Click to collapse
Just so you no a common problem when doing commands you forget to do it just trying help didn't know fixed
#!/system/bin/sh
busybox mount -o remount,rw /system
My build.prop got messed up while trying to install Google Wallet on my rooted sg3 and my phone became soft bricked. I had to reinstall the stock jellybean ROM with root that I had been running before this happened, through Odin. Solved my problem. Never got wallet to work though.
Sent from my Amazon Kindle Fire2 using xda app-developers app
Would this work on S3 T-Mobile T-999?
stratatak7 said:
If you're not comfortable with ADB: You should try to flash recovery (recommended TWRP but at this point take anything you can get) from ODIN. I know I've seen it around here somewhere. Once you do that, then flash the attached file.
This will flash in CWM/TWRP etc. I haven't tested it, so send me a PM if it doesn't work and I'll fix it up.
Edit: I've located the proper recovery file for you to flash. It's cwm, but you flash this with ODIN. Download it from here http://k0nane.info/rom/ecm/CWM-Recovery-LTE-SGS3-v5.tar.md5 . ODIN will increase your flash counter, but Chainfire's Triangle Away app takes care of that like it never happened. Odin can be found in the development thread. If you want to automate this process even further just download the qcom toolkit which walks you through the process of installing recovery. I hope this helps.
Lastly, here's the latest TWRP image file with ADB instructions. Short, sweet and simple. http://teamw.in/project/twrp2/104
Click to expand...
Click to collapse
I am having the same problem.... as the person above... Will this .Tar file below work for S3 T-Mobile T-999? Can you make one for that phone?
Thanks for your help!!
Boosoth1st said:
I am having the same problem.... as the person above... Will this .Tar file below work for S3 T-Mobile T-999? Can you make one for that phone?
Thanks for your help!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1746682
Try downloading the toolkit from there. It should contain the necessary T-Mobile files. If you are having an issue, please PM me. Make sure you flash the right one! Be careful and read the whole thread.
So, my problem is that I have recently unlocked the bootloader on my HTC One X using my Mac and the very helpful guide provided on this YouTube link
http://youtu.be/8Y3VbFJIwWU
No problems with the process in that video and I've gotten to the end with the phone bootloader definitely.
My problem is that I've then attempted to install a custom ROM from the SD card. Again, this seems to work fine, but upon reboot I'm immediately hit with a continual pop-up 'unfortunately, the process com.android.phone has stopped' with the only option to press ok. It loops continuously.
I suspect I may have to reinstall the ROM onto the SD card, but this is my problem. I cannot get my phone's USB access to work on my Mac as I am stuck with the above pop-up preventing me. I can't seem to access it via Recovery either.
Can I use fastboot to 'flash' over the *.img or *.zip of a new ROM to get it onto the SD card? Stuck with a phone I can't use otherwise. :crying:
Thanks.
Mount usb storage from the recovery.
Sent from my HTC One X using xda app-developers app
or while in recovery type
Code:
adb push rom.zip sdcard/
Thanks for that, athulele . :good:
I have tried that. On a Mac, for USB access requires that I use software called 'Android File Transfer' rather than the way Windows would do it. That software doesn't kick in via Recovery mounting. So, I'm going to need a different approach.
Since I have Windows installed via Bootcamp, I think I'll try to connect the phone up via Windows and see whether I can access the SD card via USB using that route.
Any other help is most welcome.
you do not need that file, just boot into recovery and type the command above... it's the easiest way
matt95 said:
you do not need that file, just boot into recovery and type the command above... it's the easiest way
Click to expand...
Click to collapse
Having booted into recovery, using Terminal on my Mac and typing
adb push sentinelrom_v4_30_endeavoru.zip sdcard/
gives the following message:
-bash: adb: command not found
Am I doing something wrong here?
well, have you got the sdk installed on your mac?
matt95 said:
well, have you got the sdk installed on your mac?
Click to expand...
Click to collapse
I've now downloaded the sdk for mac. It's a adt bundle folder with many files inside. I've installed 'Eclipse' but I'm still getting the same message as before from the Terminal. What else do I need to do here?
Im not into macs .... but don't you need to enter sudo commands before the adb/fastboot commands ?
no, he only needs to navigate to the adb directory with the terminal and then type
Code:
./adb push rom.zip sdcard/
matt95 said:
no, he only needs to navigate to the adb directory with the terminal and then type
Code:
./adb push rom.zip sdcard/
Click to expand...
Click to collapse
Hi matt95
I'm grateful for the help you are giving me here. I've found the adb file within the following downloaded directory path:
act-bundle-mac-x86_64-20130219 - sdk - platform-tools - adb
When I changed directory in Terminal to this path and ensured the specific rom.zip was also in that path, Terminal is still giving me this:
./adb push sentinelrom_v4_30_endeavoru.zip sdcard/
-bash: ./adb: No such file or directory
I must be doing something not right. Please help further.
that's strange, could you provide me the platform-tools folder and the rom.zip folder? i'll write down what you exactly have to write...
matt95 said:
that's strange, could you provide me the platform-tools folder and the rom.zip folder? i'll write down what you exactly have to write...
Click to expand...
Click to collapse
Folder contents as described.
Thanks.
ok now i need their directory, for ex. /User/yourusernane/Docuemnts/ecc ecc......
matt95 said:
ok now i need their directory, for ex. /User/yourusernane/Docuemnts/ecc ecc......
Click to expand...
Click to collapse
/Users/srafferty73/Downloads/adt-bundle-mac-x86_64-20130219/sdk/platform-tools
and
/Users/srafferty73/Downloads/adt-bundle-mac-x86_64-20130219/sdk/platform-tools/sentinelrom_v4_30_endeavoru
Thanks.
ok, now open the therminal ans type
Code:
cd /Users/srafferty73/Downloads/adt-bundle-mac-x86_64-20130219/sdk/platform-tools
./adb push (drag the rom.zip into terminal) sdcard/
now it should work
matt95 said:
ok, now open the therminal ans type
Code:
cd /Users/srafferty73/Downloads/adt-bundle-mac-x86_64-20130219/sdk/platform-tools
./adb push (drag the rom.zip into terminal) sdcard/
now it should work
Click to expand...
Click to collapse
Slowly making progress. Latest Terminal message after doing that reads 'error: device not found'.
I am using ClockworMod Recovery v5.8.2.7 and have clicked on 'mount /sdcard'. I have tried to 'mount USB storage' but am getting an error message which reads 'E: Unable to open ums lunfile (No such file or directory).'
What should I do next?
Thanks.
fingerbob said:
Slowly making progress. Latest Terminal message after doing that reads 'error: device not found'.
I am using ClockworMod Recovery v5.8.2.7 and have clicked on 'mount /sdcard'. I have tried to 'mount USB storage' but am getting an error message which reads 'E: Unable to open ums lunfile (No such file or directory).'
What should I do next?
Thanks.
Click to expand...
Click to collapse
Flash a newer recovery.
Mr Hofs said:
Flash a newer recovery.
Click to expand...
Click to collapse
I managed to find a copy of ClockworkMod Recovery v5.8.4.0 and flashed this as advised. This has somehow enabled the USB facility on my phone to start working again and I can replace the ROM I've downloaded onto it.
I just tried reinstalling the ROM I had again, but once again got the original message stated in my first post. I'm about to now try a different ROM to see if that makes any difference.
:good: