Related
I moved from an HD2 to the Evo this week (no more TMobile, woot!). I am very familiar with custom WMO ROMS, Hard SPL, blah blah...
I have nearly zero Android development, custom ROM knowledge, etc, however.
I'd like to flash a custom ROM based on the factory, without all the Sprint programs preloaded.
Clearly I need to root; I am on steady ground with that knowledge. After that? Not so clear. There doesn't seem to be a thread with the steps I need to proceed.
Any info would be invaluable, thanks!
(PS - side question: why does Android launch all sort of processes in the background seemingly at random?)
ifiweresolucky said:
I moved from an HD2 to the Evo this week (no more TMobile, woot!). I am very familiar with custom WMO ROMS, Hard SPL, blah blah...
I have nearly zero Android development, custom ROM knowledge, etc, however.
I'd like to flash a custom ROM based on the factory, without all the Sprint programs preloaded.
Clearly I need to root; I am on steady ground with that knowledge. After that? Not so clear. There doesn't seem to be a thread with the steps I need to proceed.
Any info would be invaluable, thanks!
(PS - side question: why does Android launch all sort of processes in the background seemingly at random?)
Click to expand...
Click to collapse
This should be in Q & A.. But unless someone creates a rom with the apps removed. Its easier to just do it yourself.
If you did toasts method of rooting. Boot into recovery and type this
adb remount
adb shell
cd /system/app
ls
This displays all apps on the phone. Do this to delete them.
rm NameOfApp.apk
rm NameOfApp.odex
It is caps sensitive and make sure you type the apk exactly as its written.
Jus10o said:
This should be in Q & A.. But unless someone creates a rom with the apps removed. Its easier to just do it yourself.
If you did toasts method of rooting. Boot into recovery and type this
adb remount
adb shell
cd /system/app
ls
This displays all apps on the phone. Do this to delete them.
rm NameOfApp.apk
rm NameOfApp.odex
It is caps sensitive and make sure you type the apk exactly as its written.
Click to expand...
Click to collapse
any reason adb remount isn't working for me? I do adb devices and my devices is there but when i type adb remount i get "remount faild: Invalid argument"
I started Toasts root directions, placing PC36IMG.zip on the base directory of the SD card. Shut down, loaded with the Vol Down and Power buttons. The bootloader checked the file on the SD card but then stopped on the white screen.
It seems it was supposed to proceed automatically? But I am dropped off with options on the white screen: FASTBOOT, RECOVERY, CLEAR STORAGE, SIMLOCK, and HBOOT USB.
Directions show Vol Up and Down for previous and next and Power for select.
Alright, I resolved this issue. I recopied the file to the SD card and made sure to eject drive before shutting the device down. Seemed to make all the difference! Proceeding with the remainder of Toast's directions now...
p-slim said:
any reason adb remount isn't working for me? I do adb devices and my devices is there but when i type adb remount i get "remount faild: Invalid argument"
Click to expand...
Click to collapse
I'm running in to the same issue...
rgordon3091 said:
I'm running in to the same issue...
Click to expand...
Click to collapse
i fixed it. you have to do this.
adb shell
mount /dev/block/mtdblock4 /system
cd /system/app
ls
Getting error trying to remove nascar..
Code:
rm Sprint_NASCAR.apk
rm failed for Sprint_NASCAR.apk, Directory not empty
Any ideas?
That's Linux trying to protect you. Essentially the rm command by default just removes one file at a time.
Try...
rm -r NameOfFolder
...to delete recursively.
Sent from my EVO 4G using Tapatalk
Go see the thread in the apps sub-forum about this. I have a post (#28, I believe) with the exact code to remove the bloatware. You can just copy any paste.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
nick325i said:
Getting error trying to remove nascar..
Code:
rm Sprint_NASCAR.apk
rm failed for Sprint_NASCAR.apk, Directory not empty
Any ideas?
Click to expand...
Click to collapse
you shouldn't have a problem deleting the apk, because an apk is not a directory.
i deleted it without the same message.
p-slim said:
i fixed it. you have to do this.
adb shell
mount /dev/block/mtdblock4 /system
cd /system/app
ls
Click to expand...
Click to collapse
'
hmmm i put im adb shell then i got a "#" so i put in "mount /dev/block/mtdblock4 /system"
and i got mount:mounting /dev/block/mtdblock4 /system failed: No such file or directory
so what did i do wrong?
Found the issue. Thanks all
Jus10o said:
This should be in Q & A.. But unless someone creates a rom with the apps removed. Its easier to just do it yourself.
If you did toasts method of rooting. Boot into recovery and type this
adb remount
adb shell
cd /system/app
ls
This displays all apps on the phone. Do this to delete them.
rm NameOfApp.apk
rm NameOfApp.odex
It is caps sensitive and make sure you type the apk exactly as its written.
Click to expand...
Click to collapse
By the way, when I "cd /system/app" and then "ls" I see only NamesOfApps.apk. There are displayed no *.odex files. Is that normal?
thread dead?
IDK if this threads still monitored by anyone, but here's my question: I don't use adb, but I just rused root explorer to locate sprint crap, and added a .bak to the end of all of them to essentially 'disable' them. Is this a safe method? Will Android system waste energy looking for them anymore (they no longer show in app tray, but are they still using resources) ? Thanks much.
scottspa74 said:
IDK if this threads still monitored by anyone, but here's my question: I don't use adb, but I just rused root explorer to locate sprint crap, and added a .bak to the end of all of them to essentially 'disable' them. Is this a safe method? Will Android system waste energy looking for them anymore (they no longer show in app tray, but are they still using resources) ? Thanks much.
Click to expand...
Click to collapse
I was just about to say something similar. I had uninstalled Nascar using Titanium Backup, and the found out that I cant do the 2.2 OTA unless its there. TB didn't have the ability to restore it for some reason, so I got an APK from XDA, and put it in the system/app folder via Root Explorer. Then, I had to reset the permissions to match the other APK's, and it showed up and launched perfectly. Even did an update. Much easier than all that adb stuff, I think.
I used system app uninstaller for a buck on the market.. Easy and all there with the icons for easy to find and delete sprint and gapps.
Sent from my PC36100 using XDA App
scottspa74 said:
IDK if this threads still monitored by anyone, but here's my question: I don't use adb, but I just rused root explorer to locate sprint crap, and added a .bak to the end of all of them to essentially 'disable' them. Is this a safe method? Will Android system waste energy looking for them anymore (they no longer show in app tray, but are they still using resources) ? Thanks much.
Click to expand...
Click to collapse
Thats a good way.. If something goes wrong just have to rename.
Sent from my PC36100 using XDA App
Flash this zip and it should remove most of the Sprint apps. It will back them up to /sdx on your SD card so if anything is removed that you want, it will still be there. It's signed to work with RA.
http://grathwohl.me/uploads/android/evo/Sprint-Apps-Remover-signed.zip
I've seen a few people reference my post, but my post was really just trying to ask if anyone knew if, now that I've renamed them, and they don't run, they shouldn't be using up resources? Right, is that correct, or am I wrong in thinkin this?
And thanks cosine83, that's a really helpful post for a lot of people.
is there a way to uninstall system apps like FLICKR service?
Maybe via console?
Via ADB with the phone in recovery.
adb shell mount /system
adb ls /system/app
then find the apk file you want to delete and:
adb shell rm /system/app/(app name here).apk
You can also delete the files before you install a new version of the ROM you're using. You can delete .apk files from the ROM.zip file to flash so when you flash it they wont install.
philje123 said:
Via ADB with the phone in recovery.
adb shell mount /system
adb ls /system/app
then find the apk file you want to delete and:
adb shell rm /system/app/(app name here).apk
Click to expand...
Click to collapse
you only have to put yourself in adb shell once,
adb shell
mount /system/
ls /system/app/
rm /system/app/xxxx.apk will do lol
btw roms with the new file overlay system can delete system apps normally now, using a file explorer!! ive done it
AndroHero said:
btw roms with the new file overlay system can delete system apps normally now, using a file explorer!! ive done it
Click to expand...
Click to collapse
sounds great
I use root explorer to do this
sent from my mind to yours using the power of suggestion
I'm in recovery and have no idea how to follow that instructions.
I see my options, don't see what you wrote.
Bump, sry
Sent from my HTC Desire using XDA App
Hi Guys,
I have rooted my Wildfire with AlphaRevX long time back and i tried many different ROMs.
Currently i have installed JokerDroid4.2 ROM.
When i start adb shell its going to normal user($) but not root(#) and when i type su in the shell its going to root(#).
So, when i want to push files to /system/app using adb push its throwing exception of permission denied.
I have seen many threads regarding this problem but couldnot find proper answer to my problem.
Workaround im using is pusing my files to /data/local and after getting root access using adb shell and su im moving it to /system/app
(OfCourse throughout the process /system is mounted as re-write)
Please solve my problem..
EDIT : I allowed the superuser to give permission to adb shell when i typed su command but when i use adb push its not asking me for permission from superuser.
Thanks,
Sandeep
You need to set permision /rw ,to system folder via root explore,then do adb push
bittu4u4ever said:
Hi Guys,
I have rooted my Wildfire with AlphaRevX long time back and i tried many different ROMs.
Currently i have installed JokerDroid4.2 ROM.
When i start adb shell its going to normal user($) but not root(#) and when i type su in the shell its going to root(#).
So, when i want to push files to /system/app using adb push its throwing exception of permission denied.
I have seen many threads regarding this problem but couldnot find proper answer to my problem.
Workaround im using is pusing my files to /data/local and after getting root access using adb shell and su im moving it to /system/app
(OfCourse throughout the process /system is mounted as re-write)
Please solve my problem..
EDIT : I allowed the superuser to give permission to adb shell when i typed su command but when i use adb push its not asking me for permission from superuser.
Thanks,
Sandeep
Click to expand...
Click to collapse
Sent from my Wildfire using XDA App
luxandroid said:
You need to set permision /rw ,to system folder via root explore,then do adb push
Sent from my Wildfire using XDA App
Click to expand...
Click to collapse
(OfCourse throughout the process /system is mounted as re-write)
Click to expand...
Click to collapse
As mentioned in my question i hav permission of rw(read-write) already throught the process..
I am using hell fire,pushed or pulled files but not as root user,just went to my tools folder where adb is and did adb push,try like that...
Sent from my Wildfire using XDA App
Have you already tried "adb remount"?
cobje said:
Have you already tried "adb remount"?
Click to expand...
Click to collapse
This should indeed solve all your problems. Just type that command, wait for the "remount succeeded" notification and than try to write in your system folders.
The reason is that your /system is not mounted as read/write (r/w) when you boot your phone, but as read-only (r/o). So afther the remount command /systemfiles will stay r/w, but when you reboot your phone, it will return r/o again.
Erwin
After rooting my Galaxy Nexus with Wug's Root Toolkit and sim unlocking with the Docomo hack, and then restoring my apps/data (can't recall if I restored from GN Toolkit or Root Toolkit), my camera app was messed up--could snap pix but they didn't save; and video always fc'ed. The solution turns out to be to rename or delete the DCIM folder. I couldn't delete--so I renamed. Now I am trying to delete that DCIM.old folder and contents (eating up 1+G on my storage), but cannot delete either individual files or the folder. I'm sure there is a simple solution, but I can't find it. Help (even with a condescending attitude ) much appreciated!
zzcat
If you use a file explorer, that has it's standard directory at / then all you need to do is navigate to /mnt/sdcard/ then make sure it's mounted as R/W and not R/O, if all that is the way I said it, you shouldn't have problems deleting anything, if so, use the ADB and type:
Code:
adb shell rm /mnt/sdcard/<Folder>
That should then do the trick
You could also try the following Apps:
- Rootexplorer (paid)
- Astro File Manager
familyguy59 said:
If you use a file explorer, that has it's standard directory at / then all you need to do is navigate to /mnt/sdcard/ then make sure it's mounted as R/W and not R/O, if all that is the way I said it, you shouldn't have problems deleting anything, if so, use the ADB and type:
Code:
adb shell rm /mnt/sdcard/<Folder>
That should then do the trick
Click to expand...
Click to collapse
FamilyGuy, thanks for the suggestion, the problem seems to be bad permissions and I can't figure out how to fix them. Tried the "fix permissions" from recovery, as well as when booted, to no avail.
Typing
adb shell rm -rf /[directory]
gives me "permission denied"
So tried
chmod 666 /sdcard/.../*
but get an "operation not permitted" message.
So I'm really stuck here...
familyguy59 said:
If you use a file explorer, that has it's standard directory at / then all you need to do is navigate to /mnt/sdcard/ then make sure it's mounted as R/W and not R/O, if all that is the way I said it, you shouldn't have problems deleting anything, if so, use the ADB and type:
Code:
adb shell rm /mnt/sdcard/<Folder>
That should then do the trick
Click to expand...
Click to collapse
Update: solved
boot into recovery mode
mount /data
adb shell
rm, rmdir etc. all work as expected from here, no need to chown or chmod anything
zz
I see you've solved this, but i thought i would throw this in anyway...
The easy way is to delete the files from /data/media
The sdcard directory is a symlink, so go to the true folder and you should have more success...
Sometimes the file ownerships get messed up after a cycle of recovering the OS and restoring files.
http://forum.xda-developers.com/showthread.php?t=1515291&page=2
If you have any other directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
This fixed it for me and others.
cmstlist said:
Sometimes the file ownerships get messed up after a cycle of recovering the OS and restoring files.
http://forum.xda-developers.com/showthread.php?t=1515291&page=2
If you have any other directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
This fixed it for me and others.
Click to expand...
Click to collapse
Thanks for this and other suggestions--my solution was trial and error, thrashing around in the dark (my unix command line chops are really, really rusty), and these are far more elegant. It's good to understand the underlying problem, your wisdom is appreciated.
Yes, permissions were messed up after rooting and applying a sim unlock hack, wiping and restoring from pre-unlock backup set. I see it so clearly now...
Problem can somebody help me?
Hello. I have a problem with my motorola defy+ running on gb 2.3.6 and is not ROOTED. Still he has an annoyng problem. After installing an aplication (not from the market) i saw that it didn't save data on the sd card. I uninstalled it and after a data factory reset i install apps such as temple run and Brother in Arms 2. At temple run it gave me this mesage
"File Access Problem Caution, unable to write files. This means your game progress can't be saved! Reason: Access to the path "/mnt/sdcard/Android/data/com.imangi.templerun/files/spaceholder.dat" is denied."
Also at Brother in Arms 2 the game didn't save. I rest the phone abouat 7-8 times.I changed the sd card. Note that the card was a 16 gb kingmax class 6 and put the 2 gb card that came with the phone. It all work smoothly. So what is the problem the sd card or the phone's software. Please answer i'm desparate and tired of wasting time.
This thread is about the Samsung Galaxy Nexus which has no external SD and uses a very different storage structure. I'm afraid we can't really help you here. Try the Defy forum.
Sent from my Galaxy Nexus using Tapatalk 2
zzcat said:
FamilyGuy, thanks for the suggestion, the problem seems to be bad permissions and I can't figure out how to fix them. Tried the "fix permissions" from recovery, as well as when booted, to no avail.
Typing
adb shell rm -rf /[directory]
gives me "permission denied"
So tried
chmod 666 /sdcard/.../*
but get an "operation not permitted" message.
So I'm really stuck here...
Click to expand...
Click to collapse
Before chmod the folder, you needed to be root by entering 'su' after 'adb shell' .
It worked from cwm, because cwm gives root access.
Linux/Android are all about permissions.
Sent from my i9250
cmstlist said:
Sometimes the file ownerships get messed up after a cycle of recovering the OS and restoring files.
http://forum.xda-developers.com/showthread.php?t=1515291&page=2
If you have any other directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
This fixed it for me and others.
Click to expand...
Click to collapse
I tried your theory, and it didn't work, still get the message" unable to change ownership permission denied, in recovery mode.
we are still trying to find a solution, here is the discussion: http://www.slatedroid.com/topic/32434-i-got-my-smartq-t20/page__st__260 on Post # 277
rocketero said:
I tried your theory, and it didn't work, still get the message" unable to change ownership permission denied, in recovery mode.
we are still trying to find a solution, here is the discussion: http://www.slatedroid.com/topic/32434-i-got-my-smartq-t20/page__st__260 on Post # 277
Click to expand...
Click to collapse
Sorry to hear that. It sounds like the problem you are having is with a completely different device, so I can't really say why this may be occurring - I don't know how your device's file system is structured. This advice is specifically for the Galaxy Nexus. If a version of CWM exists for your smartQme device, I can't speak to whether it works properly and interprets commands the same way ours does.
cmstlist said:
Sorry to hear that. It sounds like the problem you are having is with a completely different device, so I can't really say why this may be occurring - I don't know how your device's file system is structured. This advice is specifically for the Galaxy Nexus. If a version of CWM exists for your smartQme device, I can't speak to whether it works properly and interprets commands the same way ours does.
Click to expand...
Click to collapse
it's a 9.8 inches tablet branded named called "LePanII'. it has ICS now, before we had Honeycomb 3.2.1.
The manufacture of this tablet did such a bad partitioning that the /system partition was left only with merely 4MB of free space in it.
rocketero said:
it's a 9.8 inches tablet branded named called "LePanII'. it has ICS now, before we had Honeycomb 3.2.1.
The manufacture of this tablet did such a bad partitioning that the /system partition was left only with merely 4MB of free space in it.
Click to expand...
Click to collapse
Good luck with your issue. I doubt it's related to the one we were having on the GNex though.
cmstlist said:
Sometimes the file ownerships get messed up after a cycle of recovering the OS and restoring files.
http://forum.xda-developers.com/showthread.php?t=1515291&page=2
If you have any other directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
This fixed it for me and others.
Click to expand...
Click to collapse
Sorry if my question is dumb.
Does this command solve the problem for all the folders and sub-folders in sdcard? Thank you for your help!
Sent from my Galaxy Nexus
/data/media # chown -R media_rw.media_rw*
BusyBox v1.20.2-jb static (2012-10-25 21:29 +0100) multi-call binary.
Usage: chown [-RhLHP]... OWNER[<.|:>[GROUP]] FILE...
Change the owner and/or group of each FILE to OWNER and/or GROUP
-R Recurse
-h Affect symlinks instead of symlink targets
-L Traverse all symlinks to directories
-H Traverse symlinks on command line only
-P Don't traverse symlinks (default)
I got this after giving the commands from recovery in adb shell.
What does that mean?
Jar3112 said:
/data/media # chown -R media_rw.media_rw*
BusyBox v1.20.2-jb static (2012-10-25 21:29 +0100) multi-call binary.
Usage: chown [-RhLHP]... OWNER[<.|:>[GROUP]] FILE...
Change the owner and/or group of each FILE to OWNER and/or GROUP
-RRecurse
-hAffect symlinks instead of symlink targets
-LTraverse all symlinks to directories
-HTraverse symlinks on command line only
-PDon't traverse symlinks (default)
I got this after giving the commands from recovery in adb shell.
What does that mean?
Click to expand...
Click to collapse
OK solved, I forgot the space before the *!
Worked like a charm!!
Sent from my Galaxy Nexus
Was just wondering if there is a way to replace the framework with just using root without a custom recovery for the stock Rom?
On my s3 I couldn't do it with just root don't know if that would work on this or if I might have missed something.
Sent using xda premium.
re: install apks
TheArtiszan said:
Was just wondering if there is a way to replace the framework with just using root without a custom recovery for the stock Rom?
On my s3 I couldn't do it with just root don't know if that would work on this or if I might have missed something.
Sent using xda premium.
Click to expand...
Click to collapse
All you need is to be rooted, it does not matter if you have custom recovery or not.
You can install any apk's since you do not need to go into recovery to install apks.
When I tried with root only before on a different phone I used root explorer to replace.
But when I went to paste it in the folder the phone locked up and rebooted.
Was that not the right way to do it?
Maybe using adb terminal would be better and not cause it to lock and reboot when I paste over the existing framework-res.apk.
Being in the system directory causes some issue with being that is also a constant used file.
Sent using xda premium.
re: install apk
TheArtiszan said:
When I tried with root only before on a different phone I used root explorer to replace.
But when I went to paste it in the folder the phone locked up and rebooted.
Was that not the right way to do it?
Maybe using adb terminal would be better and not cause it to lock and reboot when I paste over the existing framework-res.apk.
Being in the system directory causes some issue with being that is also a constant used file.
Sent using xda premium.
Click to expand...
Click to collapse
The framework-res.apk should be installed like any other app
unless the OP of wherever you got it from gives instructions
to "copy" it to the /system/app folder.
Why not do it the default normal way? just double click on it
when you are in root explorer and it should install like any
other app. If it gives an error, then you can copy it.
If you "copy" it you have to fix permissions and you have to
change the attributes of the /system/app folder so it's "read and write".
NOTE: if there is an existing framework-res-apk in /system/app
delete it with root explorer before doing any of the above.
Framework-Res.apk must reside in system directory. /system/framework to be exact.
Easiest way to do it without locking up is with adb.
You were right OP that it locks up because it's consistently being used. When I make my mods and such to the framework, this is how I quickly get it to the device.
adb remount (if the kernel supports it in other words, anything but stock)
Turn phone screen on
Adb shell stop (your phone should now have a black screen. This command stops all running threads except the one for adb)
Adb push framework-Res.apk /system/framework
Adb shell chmod 644 /system/framework/framework-Res.apk
Adb shell start
You should now see the boot animation then the prompt "android is upgrading"
If you do not have adb remount option (it returns with permission denied)
Copy new framework Res apk to root of internal sd card.
Adb shell stop
Adb shell mount -o remount,rw /system
Adb shell cp /sdcard/framework-Res.apk /system/framework/framework-Res.apk
Adb shell chmod 644 /system/framework/framework-Res.apk
Adb shell start
Just a pointer, disregard my capitalization. Only capitalize when needed.
This method should get everything copied successfully. Any issues just post back!
Sent from my SGH-M919 using Tapatalk 2
Oh thank you very much.
I will give that a try and sounds exactly like what I was looking for.
Sent using xda premium.
Not sure if this is really relevant but...
When I had the samsung vibrant, I used root explorer to make a copy of my framework-res.apk. I extracted the entire thing, found my battery icon files, replaced them with different images given the same name, then repacked the file. Then I copied it back to the original folder to replace the original apk and my phone immediately shut off and rebooted. When it came back I had my new battery icon working just as I had hoped. I was rooted running stock.
Wait... Are you saying that I can simply copy the framework-res.apk from SlimKat and use it on a Google Play Edition ROM?
I'm going to try it!