Hi All
Apologies if this is in the wrong place or if it has been answered elsewhere, I have been searching all weekend, so hopefully not!
I have recently installed gingervillain v1.0 on my Desire, and wanted to remove some .APKs for programs I do not use, such as DSPManager.
In an effort to do this I have purchased the paid versions of Root Explorer and Titanium Backup. Using Root Explorer I have tried deleting the .APKs from system/app, but to no avail.
In Titanium Backup I have tried using the uninstall feature, but the apps in question, persisted.
So I began running searches in Google and found a few articles which claimed you could for example delete the .APKs in the ZIP archive close and resign, but I tried this several times and could not get it to work.
I have now downloaded the Android SDK and USB driver for ADB. But when attempting to utiilise ADB to delete the .APKs CMD returns "'adb' is not recognized as an internal or external command, operable program or batch file"
After searching the XDA forums i came across a post which stated I needed to amend the path under Environment Variables to the location of the ADB, which I have done (and rebooted my PC).
I am still receiving the ADB is not a ... statement, in CMD.
I am running windows 7 and have tried the above with and without HTC Sync installed.
Thanks in advance
I think you need to be S-Off to delete system apps whilst booted in Android. You can delete the apps from the zip file before you flash it.
GoogleJelly said:
I think you need to be S-Off to delete system apps whilst booted in Android. You can delete the apps from the zip file before you flash it.
Click to expand...
Click to collapse
Thanks Googlejelly, none of the articles i followed mentioned S-Off but I will look into it. Regarding the deletion of aps from the zip, is this something you have done yourself? Everytime I try too I get Error 0x80004005. I did unzip which allowed me to delete without the error, but after flashing the rom, I got stuck in a bootloop.
Sent from my HTC Desire using XDA App
for deleting anything on the system file itself, u def need s-off. i was on a sgs fascinate rooted which came witrh s-off included in its root. so when i came to a htc desire, i figured it would b the same. but it wasnt. u need to s-off to delete sysrem apks like google talk, file manager, etc
if you want to delete apps while android is running you need to be S-OFF.
you can also edit .zip before flashing.
since you get a bootloop you either delete something you should not OR you have to edit updater script (but since you wrote about GingerVillain i doubt it, so probably you just delete some important stuff)
dzumagos said:
if you want to delete apps while android is running you need to be S-OFF.
you can also edit .zip before flashing.
since you get a bootloop you either delete something you should not OR you have to edit updater script (but since you wrote about GingerVillain i doubt it, so probably you just delete some important stuff)
Click to expand...
Click to collapse
Thanks dzumagos. Do you know if I need to resign the zip, after editing? Also do you know why I might be getting the error which is stopping me from deleting the files in the zip?
Sent from my HTC Desire using XDA App
You shouldn't need to unzip the file to take out the apks, just use winzip to access the the zipped file, delete which apks you don't want then exit out of winzip and flash it, if you delete something important it'll probably loop.
I've done this with leedroid 2.3d and took out footprints,teeter,stocks and a couple of other apks, it flashed fine with no problems.
Actually, you don't need to be S-OFF to remove files from system. Can be done via ADB.
You must have the phone connected via recovery (better, since nothing is in use) with USB debugging on.
Run CMD as administrator, then change to the directory where you have the adb.exe (In my case c:\android-sdk-windows\tools\)
Then type in the command adb shell after you should get an information something like starting daemon.
Then type in mount /system
Now, you can remove files with the rm /system/app/(APPFILENAME).apk command.
When finished type umount /system then exit
If you need the list of files, then type ls in the command prompt.
Worked for me, S-ON.
Sent from my customized HTC Desire using TTP
nagypapi said:
Actually, you don't need to be S-OFF to remove files from system. Can be done via ADB.
You must have the phone connected via recovery (better, since nothing is in use) with USB debugging on.
Run CMD as administrator, then change to the directory where you have the adb.exe (In my case c:\android-sdk-windows\tools\)
Then type in the command adb shell after you should get an information something like starting daemon.
Then type in mount /system
Now, you can remove files with the rm /system/app/(APPFILENAME).apk command.
When finished type umount /system then exit
If you need the list of files, then type ls in the command prompt.
Worked for me, S-ON.
Sent from my customized HTC Desire using TTP
Click to expand...
Click to collapse
Would do this but for the aforementioned error.
Sent from my HTC Desire using XDA App
Tried it or not?
Because from what I read you are writing wrong commands.
Dont write adb if you are already in the shell, because that's not a valid command.
All I do is when I download a rom is open it using WinRar and delete the files straight from the archive. I don't extract the files from the archive, just edit it. I add my own font, notification sound, delete the boot animation and I delete some system apps that I don't use. This beats having to S-Off (I have it anyway) but it is a nice work around.
GoogleJelly said:
All I do is when I download a rom is open it using WinRar and delete the files straight from the archive. I don't extract the files from the archive, just edit it. I add my own font, notification sound, delete the boot animation and I delete some system apps that I don't use. This beats having to S-Off (I have it anyway) but it is a nice work around.
Click to expand...
Click to collapse
GoogleJelly - I did the following, uninstalled 7zip, installed winzip, right clicked the archive with the rom, selected "open with winzip", navigated to the system\app\ folder, right clicked DSPManager.apk, selected delete and got this... (see attached). It just freezes everytime and i get the (not responding) postfix
Perfectly willing to accept I am an idiot who has done something wrong. But I really do fail to see what.
Help, this is so frustrating!!!
nagypapi said:
Tried it or not?
Because from what I read you are writing wrong commands.
Dont write adb if you are already in the shell, because that's not a valid command.
Click to expand...
Click to collapse
Sorry nagypapi, you have lost this Noob! I will try to follow your suggestion again, and report back.
Thanks
I don't use Winzip, I use Winrar.
Solved - cannot delete apks
GoogleJelly said:
I don't use Winzip, I use Winrar.
Click to expand...
Click to collapse
That got it *feel like a tool* Thank you Googlejelly!! No More boot loops either.
madffrogs said:
You shouldn't need to unzip the file to take out the apks, just use winzip to access the the zipped file, delete which apks you don't want then exit out of winzip and flash it, if you delete something important it'll probably loop.
I've done this with leedroid 2.3d and took out footprints,teeter,stocks and a couple of other apks, it flashed fine with no problems.
Click to expand...
Click to collapse
Thanks, madffrogs, it work. In this case, I am just removing some 'excessive' files from a CyanogenMod files, and used 7zip.
Related
I rooted my HTC Magic today and I loaded the RAv1.1.0 custom rom. Its a great rom, but the ringtones are a bit boring and i really liked the htc ones. So i extracted the files from a Hero ROM and pushed it to my phone.
If anyone wants these media files, i have packaged them toagther and made a small python script to install it automatically for you, you just need to run just run push.py file.
Let me know how it goes, it works great for me
Cheers
spatali
PS: Reboot the system after running the script. Otherwise they wont show up until next reboot
Tutorial & .bat (for windows) by TikiiTorch
For people who don't have python install in Windows
1) extract the above .zip file into your "android-sdk-windows-1.5_r3\tools\" directory (wherever that might be)
2) get on your command line and cd to the "htc_media" directory you just created.
3) enter the following commands:
Code:
adb remount
adb push alarms /system/media/audio/alarms/
adb push ringtones /system/media/audio/rigntones/
adb reboot
Click to expand...
Click to collapse
or use push.bat in the zip
DOWNLOAD
Ringtones & Alarms
thanks TikiiTorch
didn't download. requires login to download.
Rroet said:
didn't download. requires login to download.
Click to expand...
Click to collapse
No it doesnt.. just click the request ticket link above the file... then do the same when it changes to download.
Thanks
Flashed the Drizzy TF3D rom and was seriously missing the stock notifications.
Thanks for tracking this down and sharing!
Any idea why now under ringtones it list every ring tone twice, yet there is only one copy of each file in the directory?
thanks
Okay never mind, I deleted them, rebooted, copied them back, rebooted and now only one is showing up. That was very strange.
So how does one go about installing these ringtones to the phone? A myTouch 3G specifically using Cyanogen's 4.0.1 ROM. I guess I'm a little confused as fas as running the python script itself....any help would be absolutely appreciated! Thanks everyone!
juanavila said:
So how does one go about installing these ringtones to the phone? A myTouch 3G specifically using Cyanogen's 4.0.1 ROM. I guess I'm a little confused as fas as running the python script itself....any help would be absolutely appreciated! Thanks everyone!
Click to expand...
Click to collapse
Im guessing you are on windows without python installed, so you will want to:
1) extract the above .zip file into your "android-sdk-windows-1.5_r3\tools\" directory (wherever that might be)
2) get on your command line and cd to the "htc_media" directory you just created.
3) enter the following commands:
Code:
adb remount
adb push alarms /system/media/audio/alarms/
adb push ringtones /system/media/audio/rigntones/
adb reboot
OR Download this zip (same as spatali's above but with my .bat file included) and double click the push.bat file thats in there.
Let me know...
@TikiiTorch this is great, i'll include your tut and .bat file in the first post
ps: I dint know push command works for entire folder ^^
i'm not an expert, but isn't the reboot commando:
Code:
adb shell reboot
unirox said:
i'm not an expert, but isn't the reboot commando:
Code:
adb shell reboot
Click to expand...
Click to collapse
Whoops, you're right. Re-upping now with the correct code.. Thanks unirox!
... upped .. OPs link above includes correct commands lol
--
@Spatali thank you, you did all the hard work!
Ringtones on sdcard
There is an easier way
Just create on your sdcard a "media\audio" folder and copy into it notifications, ringtones and alarms folder.
Disconnet your phone from the pc and new medias will be detected automatically
castorjunior said:
There is an easier way
Just create on your sdcard a "media\audio" folder and copy into it notifications, ringtones and alarms folder.
Disconnet your phone from the pc and new medias will be detected automatically
Click to expand...
Click to collapse
But with this method, don't those files remain on the SDCard rather then becoming part of the system?
TikiiTorch said:
1) extract the above .zip file into your "android-sdk-windows-1.5_r3\tools\" directory (wherever that might be)
2) get on your command line and cd to the "htc_media" directory you just created.
3) enter the following commands:
Code:
adb remount
adb push alarms /system/media/audio/alarms/
adb push ringtones /system/media/audio/rigntones/
adb reboot
Click to expand...
Click to collapse
I think you mean "adb push ringtones /system/media/audio/ringtones/"
(ringtones)
Cyalintz said:
I think you mean "adb push ringtones /system/media/audio/ringtones/"
(ringtones)
Click to expand...
Click to collapse
I fail... horribly...
yes, thanks, must have been a bad finger day
TikiiTorch said:
But with this method, don't those files remain on the SDCard rather then becoming part of the system?
Click to expand...
Click to collapse
You're right, the files remains on the sdcard but it doesn't really matters as they are detected and used automatically, the same way as if they are part of the system
how do i get on my "htc_media" directory i just created
castorjunior said:
You're right, the files remains on the sdcard but it doesn't really matters as they are detected and used automatically, the same way as if they are part of the system
Click to expand...
Click to collapse
if using SUFBS with root and mounting system RW, does it not write to system when copying file from sdcard folder to system/media/notifications?
lpasq said:
if using SUFBS with root and mounting system RW, does it not write to system when copying file from sdcard folder to system/media/notifications?
Click to expand...
Click to collapse
Yes, it would indeed move them there if you used the above method.
??
Guys which is the easiest method now ? I'll update the first post accordingly
spatali said:
Guys which is the easiest method now ? I'll update the first post accordingly
Click to expand...
Click to collapse
The easiest way, obviously would be to just put these files onto your SD and let the device recognize them.
If you want to properly replace these ringtones onto a ROM that does not have them, then what you have posted is the correct way.
I used to use "Root Explorer" on my hero to delete system apps before..doesn't seem to work anymore..
solution??
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
did you mount /system in rw mode? (it's ro by default)
U dont have write access to system partition in normal use if i read the tutorial right. U have to do it with an update.zip (editing the update script) or with adb both u have to do in recovery menu from modaco i think. Tell me if i am wrong.
Sry for my bad english
@cezarL yes I did
@xtcislove I wish u were wrong..seems like pain.. anyway to do it without a pc?
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Damn, you're right. Previously, I had deleted an .apk just to check if it's working, then reinstalled the app right away.
But I just tested now, it looks like after a reboot, the .apk magically reappears, and the application is running as usual
Damn, you're right. Previously, I had deleted an .apk just to check if it's working, then reinstalled the app right away.
But I just tested now, it looks like after a reboot, the .apk magically reappears, and the application is running as usual
Click to expand...
Click to collapse
ye..I'm sure it has something to do with the root limitations Paul mentioned in his rooting guide. hope it'll be fixed soon.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Try this: Boot in recovery menu and try the following commands:
adb remount
adb shell rm /system/app/APP.apk
adb shell rm /data/app/APP.apk
where APP.apk is the filename of the apk with the .apk extention, remember case-sensitive!
for example:
adb remount
adb shell rm /system/app/FriendStream.apk
adb shell rm /system/app/FriendStream.odex
take a look before if your app has a odex or try this: (here u need only one command)
adb remount
adb shell rm /system/app/*FriendStream*
Good luck and have fun =)
Edit: Just find a topic =)
hxxp://android.modaco.com/content/htc-hero-hero-modaco-com/297207/removal-of-apps-via-adb/#entry1124362
(replace hxxp with http)
I'm trying to do these things in windows at the moment. No issues getting in the recovery with the windows scripts. But when I try to open a ADB Shell after I've gone to recovery I can't really do anything with it and the recovery hangs (not controllable with the track pad).
Anyone can tell me what I'm doing wrong?
You're not doing anything wrong, from what I've seen opening a new adb instance on Windows will kill the server created by the .bat file used for recovery... which means the connection to the device is lost. I haven't looked into it further, but it might be fixeable somehow.
Ah I see, so basicly you undo the patched recovery by opening a new session. It does work properly under Linux then? I run ubuntu on my netbook so It's not a big issue anyway. Thanks for the tip, gonna try under linux now!
I'm having the same problems as:
http://android.modaco.com/content/h...co-com/307401/removing-sys-apps/#entry1256015
I removed a load of HTC widgets but I get strange entries on the widget menu. Anyone know how to get rid of these?
Also, I removed Stocks (.apk and .odex), now I get a force close on 'Accounts & sync'. Anyone know how to remove Stocks properly?
Cheers.
After running the bat file to get into recovery, start a new cmd prompt in windows and use again adb-nilezon for shell commands instead of ordinary adb, and it wont be killed.
This has worked for me atleast
blackadder1000 said:
Anyone know how to remove Stocks properly?
Click to expand...
Click to collapse
The best, foolproof, failsafe way is to remove them from the rom before installing it... and remember that some services are still required, weather you use them or not.
But, if a system app is already installed you need to remove:
the apk from /system/app
the data from /data/data/appname
the cache from /cache/dalvik-cache
Do not remove Accounts & Sync...
Thanks for the answer.
I guess now is a good time to bake my own ROM!
blackadder1000 said:
Thanks for the answer.
I guess now is a good time to bake my own ROM!
Click to expand...
Click to collapse
Yep, that's what I do... see my sig...
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
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.
This archive contains the missing apks and stickers that are lost when using the HTC Dev unlock tool.
You can install the apks inside manually, but the png files must be placed into /data/preload/ in order for the gallery app to find them.
Instructions for re-installation. (Busybox must be installed)
Code:
adb push preload.tgz /sdcard/
adb shell
su
cd /data/
tar -xvf /sdcard/preload.tgz
chown root:root /data/preload
chmod 771 /data/preload
chmod 644 /data/preload/*
pm install /data/preload/Flashlight.apk
pm install /data/preload/Calculator.apk
reboot
Download here: http://www.cheatersedge.org/android/m8/preload.tgz
Wow thanks. Did not even realize it was gone.
Sent from my HTC One_M8 using Tapatalk
FYI, wiping /data/ with TWRP erases these preloads as well.
Sent from my HTC One_M8 using Tapatalk
Hey I know this is not specifically related but everytime I remove an app via TB they come back upon reboot (T-Mobile Tv, Lookout, etc etc)
How do I stop them from coming back (delete for good)? Thanks
S-off or try http://forum.xda-developers.com/showthread.php?t=2702575
[Guide] How to have write protection disabled on boot with stock rom
Sent from my HTC One_M8 using Tapatalk
I am uploading a ROM right now that restores these files.
Weird, I'm HTCdev unlocked but I still have the flashlight app but calculator is gone. Weird.
Fenny said:
This archive contains the missing apks and stickers that are lost when using the HTC Dev unlock tool.
You can install the apks inside manually, but the png files must be placed into /data/preload/ in order for the gallery app to find them.
Instructions for re-installation. (Busybox must be installed)
Code:
adb push preload.tgz /sdcard/
adb shell
su
cd /data/
tar -xvf /sdcard/preload.tgz
chown root:root /data/preload
chmod 771 /data/preload
chmod 644 /data/preload/*
pm install /data/preload/Flashlight.apk
pm install /data/preload/Calculator.apk
reboot
Download here: http://www.cheatersedge.org/android/m8/preload.tgz
Click to expand...
Click to collapse
How would I go about executing these commands? I have tried a command prompt with the phone powered into the OS and with it in fastboot but continue to get device not recognized. Could I place the file on my phone and use terminal emulator?
ghettovirtuoso said:
How would I go about executing these commands? I have tried a command prompt with the phone powered into the OS and with it in fastboot but continue to get device not recognized. Could I place the file on my phone and use terminal emulator?
Click to expand...
Click to collapse
Problem fixed! I needed to update my adb tools, was working with outdate ones because they did everything I needed until now.
I tried the commands, but the tar command doesn't seem to work. Do I have to install something to make tar work?
I used Root Explorer to extract the files, then moved them to /data/preload, then changed the permissions using adb. I think I got it correct. How can I tell if the stickers are installed correctly? What uses them? I saw a comment about the gallery but I can't see where that uses them?
Thanks!
fclifton said:
I tried the commands, but the tar command doesn't seem to work. Do I have to install something to make tar work?
I used Root Explorer to extract the files, then moved them to /data/preload, then changed the permissions using adb. I think I got it correct. How can I tell if the stickers are installed correctly? What uses them? I saw a comment about the gallery but I can't see where that uses them?
Thanks!
Click to expand...
Click to collapse
Take a pic and edit it. If you can use the stickers you see in folder and the apps are install then I assume all went well.
Sent from my HTC One_M8 using XDA Free mobile app
ghettovirtuoso said:
Take a pic and edit it. If you can use the stickers you see in folder and the apps are install then I assume all went well.
Click to expand...
Click to collapse
Apparently all went well. I have the apps and the stickers work. :good:
What about tar? Should it have been available?
fclifton said:
Apparently all went well. I have the apps and the stickers work. :good:
What about tar? Should it have been available?
Click to expand...
Click to collapse
I know nothing of a tar. I'm not an expert. I was just able to follow the post. Sorry.
Sent from my HTC One_M8 using XDA Free mobile app
Couldn't install apps from adb
Everything in the op worked up to the point where I tried to install the Flashlight and Calculator apks. I got the following error-
pm install /data/preload/Flashlight.apk
pkg: /data/preload/Flashlight.apk
Failure [INSTALL_FAILED_INVALID_URI]
I was able to use a file manager to find the apks in the /data/preload/ folder and install them through android.
Is this enough to receive any OTAs? Would I need to convert them to system apps?