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.
I do not want it i'm perfectly fine with my phone the way it is I get great battery life my wifi tether works great and i have read up on all these forms there is no way of getting the update without losing something.Either root or wimax or something so i don't want the update yet everyday it keeps popping up how can i stop this? And is there anybody out there that is not running any rom that has got the update successfully and not lose anything preferable with unrevoked 2?
auau465121 said:
I do not want it i'm perfectly fine with my phone the way it is I get great battery life my wifi tether works great and i have read up on all these forms there is no way of getting the update without losing something.Either root or wimax or something so i don't want the update yet everyday it keeps popping up how can i stop this? And is there anybody out there that is not running any rom that has got the update successfully and not lose anything preferable with unrevoked 2?
Click to expand...
Click to collapse
This has been posted before but here's a quick rundown.
1. First, you need a root method that allows you to modify the /system directory. I prefer Toast's but I think Unrevoked2 allows this as well.
2. Download the android sdk. Open a command prompt, cd into the directory you extracted it in and type in the following:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.old
Reboot and tada. You'll never see a popup again.
It would Be nice to find an answer for your question too.. (never mind "chuckhriczko" answered just before me posting )
But incase you care I also got the message on my phone and my wife's phone while running ROM OMJ 1.4r.. but only got it once no repeats I installed ROM Fresh 0.5.3 on both phones yesterday and I have not been asked to do the update on either phone and I have rebooted the phones multiple times..
Take care..
P.S.
chuckhriczko
Thank you for the info..
This has been posted before but here's a quick rundown.
1. First, you need a root method that allows you to modify the /system directory. I prefer Toast's but I think Unrevoked2 allows this as well.
2. Download the android sdk. Open a command prompt, cd into the directory you extracted it in and type in the following:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.old
Reboot and tada. You'll never see a popup again.
Click to expand...
Click to collapse
Thanks trying now
It would Be nice to find an answer for your question too.. (never mind "chuckhriczko" answered just before me posting )
Click to expand...
Click to collapse
yeah but thanks
Maybe I'm missing something, but why can't you just go into:
System Updates -> HTC Software Update
and uncheck "Scheduled Check"
Clarification: I did not think about this myself!
I just found it in a post in Modaco explaining how to Unroot a Droid X and it worked for my Galaxy S as well, so I thought it should be worth posting, as I wanted to unroot my Galaxy S and failed to find a good method.
So First, I'm not responsible for any damage caused to your phone.
Anything you are doing is solely your responsibility.
Second, ALL credit goes to the user itsluy from Modaco who wrote this.
This is the link, by the way:
http://androidforums.com/motorola-droid/39303-factory-reset-updates-apps-root.html#post294672
These are the instructions:
While you still have root go to terminal emulator and run the following:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
sync
reboot
*****end of instructions****
I would like to emphasize that you HAVE to type EXACTLY what it says.
Before every new row you obviously need to press enter.
If you're doing it right, you shouldn't be seeing any messages of any kind during the process.
A good way of making sure it works is after you have removed Superuser.apk, type the command ls and then make sure it doesn't appear in the list.
Then, of course, continue as usual.
I repeat, you have to type exactly what it says, if not it will not work.
For example, there's a space between modblock3 and /system .
Another example is that you have to write Superuser.apk with a capital s.
Once again, it is all thanks to itsluy from modaco and I'm not responsible for any of the damages this process may cause.
I would be happy to hear comments (hopefully good ones)
Itay
Sounds good mate, but you do know you can just use One click unroot application instead?
still this may come in handy for others!
itaykoren said:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Haha, what? You can probably leave off the 'mount' lines... /system on SGS is already rw.
Yes, Mambo04, I know that you can use the one click root/unroot, but this method is very useful for those who already have root access.
In addition, the comments regarding that unroot process are a mixed bag.
For me, it's much more comfortable to do it this way as I don't need to download any files as opposed to the one click root/unroot process (besides Terminal Emulator that most people already have) and also don't need to connect it to a computer (as opposed to the second root/unroot method).
Eventually, I think writing several lines of dictated code is much easier and takes less time to do, so I personally think it's a very good method.
What do you guys think?
RyanZA ,
thanks for your response.
Actually I did try without the 'mount' lines and it didn't work.
At least for me on stock jf3.
Perhaps on other firmwares it's different...
itaykoren said:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Itay
Click to expand...
Click to collapse
SGS actually does not use yaffs2.... So Impretty sure this fix isnt "proper"
I guess you're right.
Then again, I no longer have root access, so "if it ain't broken, don't fix it..."
Worked for me also.
I'm glad to hear...
If anyone else uses this, please feel free to comment so that we know of any problems with it, as so far I have not found any, and I think it's the one of the easiest ways to safely unroot
THANKS! you saved me a Butt-Ton of headache. I work for bell, and i kind of rooted/lagfixed a store unit prior to activating it, the customer who got it would have been ecstatic. but the warranty is an issue. Is it possible to do the lagfix and then remove superuser permission so the phone is totally fixed and still warrantyable?
I don't know for sure if it's possible so I don't want to make any statements...
I guess it also depends on what this provider defines as a violation of the warranty.
There's been rumors that Vodafone UK, for example, does not consider rooting a Galaxy S as a violation of the warranty terms. But again, this has not been confirmed, and I guess most providers do consider it as a violation.
Also, hopefully the lag issue will be fixed in future official updates, so if warranty is a big issue, it mind be better to wait, or apply the lagfix and remove it before taking it to be repaired (if the state of the device allows it...)
Hi, thanks for posting this unroot method, just a couple of questions;
1. If I run this, then do a factory reset will the phone remain unrooted? or will it revert back to rooted as I applied root using update.zip.
2. Is it safe to delete the update.zip from my internal sd after applying this?
Thanks.
hi skink666,
1. After you run this successfully, you are unrooted, so if you do a factory reset, you will remain unrooted (you can easily verify this by checking your apps and making sure the "Superuser Permissions" app is not there).
2. The update.zip file that you use in order to root your device can be deleted once you have successfully gained root access. So, you can even delete it before applying this unroot method, not to mention afterwards.
You might want to keep a copy of it on your computer in case you want to root again.
Thanks for the info, will give it a try
Is this method working on froyo xxjpy with voodoo kernel?
I haven't tried, but you're more than welcome...
I am getting a permission denied when I try to run "adb remount".
I am running the netarchy rooted ROM.
I am Unrevoked3 and Unrevoked Forever.
So my NAND is unlocked and I am rooted. Why does it still say Permission Denied?
Install the latest version of SuperUser (look in the Market). When you try to do adb remount, or su in adb shell, look at your phone. There'll be a popup asking for permission.
AzN1337c0d3r said:
I am getting a permission denied when I try to run "adb remount".
I am running the netarchy rooted ROM.
I am Unrevoked3 and Unrevoked Forever.
So my NAND is unlocked and I am rooted. Why does it still say Permission Denied?
Click to expand...
Click to collapse
In Netarchy's kernel thread he mentions something about unrevoked 3 not giving full access to root, not sure if he was just referring to the NAND or what but that may have something to do with it. If all else fails you can always go back and try rooting it manually without unrevoked.
just out of curiosity, what does your name mean? The last part looks like coder but what is azn 1337?
xHausx said:
In Netarchy's kernel thread he mentions something about unrevoked 3 not giving full access to root, not sure if he was just referring to the NAND or what but that may have something to do with it. If all else fails you can always go back and try rooting it manually without unrevoked.
just out of curiosity, what does your name mean? The last part looks like coder but what is azn 1337?
Click to expand...
Click to collapse
My leetspeak is a little rusty, but I think 1337 is 'leet' as in "elite"....and I'm guessing the young man is of Asian descent.
drmacinyasha said:
Install the latest version of SuperUser (look in the Market). When you try to do adb remount, or su in adb shell, look at your phone. There'll be a popup asking for permission.
Click to expand...
Click to collapse
Installed latest version of SuperUser.
"adb remount" still saying permission denied.
"adb shell su" did ask me for permission however.
xHausx said:
In Netarchy's kernel thread he mentions something about unrevoked 3 not giving full access to root, not sure if he was just referring to the NAND or what but that may have something to do with it. If all else fails you can always go back and try rooting it manually without unrevoked.
Click to expand...
Click to collapse
I thought Unrevoked Forever took care of the NAND not getting unlocked. It says on their website that it unlocks NAND.
Anyways, the whole reason why I went with unrevoked is because I could keep PRI 1.40_003. I had lost it when I manually rooted and had to go back to stock and then unrevoked to get it back.
I am having the same issues. I am unrevoked3 and unrevoked forever. It is always telling me either device not found or remote not allowed. As far as I can tell all of my drivers are up to date, I am fully rooted with nand unlocked, and the problem didn't start until just recently. Everything worked fine before. I will try to download an updated Superuser app and give some feedback on that when I get off work.
On a side note, does Busybox have anything to do with this sort of matter?
Sent from my regaw rooted EVO.
My problem appears to be a software/OS issue. When I wipe everything and install a stock 2.2 system, I am able to "adb remount".
My guess is that something is continually accessing the /system partition and holding a lock on it.
Does anyone know how I might check for this?
Just to clarify: yes, Unrevoked Forever does unlock NAND.
The issue must be with the rom? Try a different superuser/su...
AzN1337c0d3r said:
Installed latest version of SuperUser.
"adb remount" still saying permission denied.
"adb shell su" did ask me for permission however.
Click to expand...
Click to collapse
Mmmkay, your problem is either:
1) NAND is locked still (unlikely).
2) ROM is not set up to have shells be root by default (likely).
To test, open adb shell. If you see a $, then it's #2. If you see a #, then it's probably #1. To be extra sure, if you're seeing a $, type "su" then enter, approve the su request, then do "mount -o remount,rw /system", followed by "mkdir /system/testymctest". If you get a permission error, then your NAND is not unlocked.
drmacinyasha said:
Mmmkay, your problem is either:
1) NAND is locked still (unlikely).
2) ROM is not set up to have shells be root by default (likely).
To test, open adb shell. If you see a $, then it's #2. If you see a #, then it's probably #1. To be extra sure, if you're seeing a $, type "su" then enter, approve the su request, then do "mount -o remount,rw /system", followed by "mkdir /system/testymctest". If you get a permission error, then your NAND is not unlocked.
Click to expand...
Click to collapse
Thank you so much for the info. I have been searching high and low for a straight answer on this. Even though its not fixed I am much happier knowing what the issue is. Again thank you.
When I ran your test I got a $ which as you said means it is a conflict with my current ROM. So, if I flash a different ROM than I should be squared away yes? Again many thanks.
Sent from my regaw rooted EVO.
drmacinyasha said:
Mmmkay, your problem is either:
1) NAND is locked still (unlikely).
2) ROM is not set up to have shells be root by default (likely).
Click to expand...
Click to collapse
It says clearly SHIP S-OFF on my bootloader. This is the way to tell if you are Unrevoked Forever.
To test, open adb shell. If you see a $, then it's #2. If you see a #, then it's probably #1. To be extra sure, if you're seeing a $, type "su" then enter, approve the su request, then do "mount -o remount,rw /system", followed by "mkdir /system/testymctest". If you get a permission error, then your NAND is not unlocked.
Click to expand...
Click to collapse
Everything is as you described. It is #2. and when I do the "mount -o remount,rw /system" I get permission denied.
I'm not sure how Root Explorer works, but I assume it obtains root permissions and then run the mount command as you have described above.
My NAND is unlocked, I can get to it via Root Explorer and mount it as r/w and then access it through shell. However, if I don't use Root Explorer and try the command through the shell, it doesn't work.
It seems almost like I am not getting SU permissions even though my shell changes to a #.
AzN1337c0d3r said:
It says clearly SHIP S-OFF on my bootloader. This is the way to tell if you are Unrevoked Forever.
Everything is as you described. It is #2. and when I do the "mount -o remount,rw /system" I get permission denied.
I'm not sure how Root Explorer works, but I assume it obtains root permissions and then run the mount command as you have described above.
My NAND is unlocked, I can get to it via Root Explorer and mount it as r/w and then access it through shell. However, if I don't use Root Explorer and try the command through the shell, it doesn't work.
It seems almost like I am not getting SU permissions even though my shell changes to a #.
Click to expand...
Click to collapse
Hrm... Are you sure you have the latest version of ChrisDD's SuperUser from the Market, and then opened up its settings tab to make sure there's the latest su executable? That's the only thing I can think of.
drmacinyasha said:
Hrm... Are you sure you have the latest version of ChrisDD's SuperUser from the Market, and then opened up its settings tab to make sure there's the latest su executable? That's the only thing I can think of.
Click to expand...
Click to collapse
Yup I did exactly that.
It's some app I installed that is doing this. I nandroided my current config, reflashed the netarchy 2.2 rooted rom and was able to get access.
Then when I installed all the rest of my apps, I suddenly lost access.
Tommorow I will start fresh again and try apps one by one.
now i got # what else
Well I was wondering if there was a way to get the original Swype Keyboard on a MIUI ROM. My friend told me about flashing it but I dont know how and where to get the file for it. Please help me, the Swype Keyboard BETA has issues and I want the original keyboard. Please post links..
If you got a nand back up you can use swype restorer
Or get one of the stock roms un zip it and take out the swype.apk and libswypecore.so and push them into the phone
I'll make it easy for ya:
adb shell
su
mount -o rw,remount /system
mv /sdcard/Swype.apk /system/app \\NOTE: use "cp" instead of "mv" if you want to keep the file on your sdcard as a backup for future use or whatever
chmod 644 /system/app/Swype.apk
mv /sdcard/libSwypeCore.so /system/lib \\NOTE: use "cp" instead of "mv" if you want to keep the file on your sdcard as a backup for future use or whatever
chmod 644 /system/lib/libSwypeCore.so
reboot
Click to expand...
Click to collapse
after your reboot, go to your language&keyboard settings, Swype should be available now.
EDIT: cleanup
pmcqueen said:
I'll make it easy for ya:
download attached files and push them to /sdcard/
(NOTE: before you move the libSwypeCore.so.zip, rename it to just libSwypeCore.so - I had to add .zip to be able to attach it here)
then run the following commands from ADB (or terminal emulator, you just don't need the adb shell command in that case):
after your reboot, go to your language&keyboard settings, Swype should be available now.
Click to expand...
Click to collapse
After " mv /sdcard/libSwypeCore.so /system/lib" I get the error " mv: can't rename '/sdcard/libSwypeCore.so': No such file or directory "
Please help!
I AM VS4 said:
After " mv /sdcard/libSwypeCore.so /system/lib" I get the error " mv: can't rename '/sdcard/libSwypeCore.so': No such file or directory "
Please help!
Click to expand...
Click to collapse
before moving libSwypeCore.so.zip from your PC to your phone, did you remove the .zip? sounds like it still thinks it's a zip to me.
how do I do that when it wont let me open the zip folder?
EDIT: cleanup
Thanks alot! It worked!! ;P
But the thing is that this Swype wont work! Everytime I swype a word a blue box flashes around it! Please help with this issue too!
did you reboot?
if so and it's still doing it, try clearing Swype data and rebooting again. if you're still having issues after that, let me know and I'll find a different apk for you to try.
yo im all for help and all but your really not allowed to distribute swype, its in the form rules, even if the phone had it, you would have to get it from your own phone, or as said get it from a stock rom,
Thanks for this post. My question no longer really has anything to do with Swype. Now its personal!! lol
When I copy and paste the
mount -o rw,remount /system​
command, it comes up showing the options for mount instead of executing the command. Is there by chance a syntax error in the typing or am I missing something?
Thanks
look in the market there is a app called remount you can use that to mount the system to read or read/write
Thank you!!!
Strange. Tried Remount app, no dice. Tried mount command, yet it still gives me a cross-link error when I try to run the "mv" command. I read that this error is due to the fact that it isn't mounted properly (I'm a complete noob at this stuff). The thing that puzzles me is I type
mount -o rw,remount /system and it always comes back with
Usage: mount [-r] [-w] [-o options] [-t type] device directory
which leads me to think there's some kind of syntax error.
It's to the point now that I just want to know why it isn't working as described in the post.
ok try this
mount -o remount,rw /dev/block/mtdblock3 /system
Thanks for the advice. I used the command you posted and it allowed me r/w access. But (there always seems to be a but...) when I tried to move files with the mv command I got a cross link error.
I ended up simply using the move function from root explorer (once I figured out what I was trying to do). Worked well.
ilostchild said:
yo im all for help and all but your really not allowed to distribute swype, its in the form rules, even if the phone had it, you would have to get it from your own phone, or as said get it from a stock rom,
Click to expand...
Click to collapse
Guess you didn't read the rules to well. If a custom rom is made for a device that has swype it can be included in rom
Just get swype from the website
Sent from my T-Mobile G2 using XDA Premium App
Spastic909 said:
Guess you didn't read the rules to well. If a custom rom is made for a device that has swype it can be included in rom
Just get swype from the website
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
That's if them rom itself came from the stock kernal, not from asop kernal, think why cyanogen doesn't include it in his roms? But we are allowed to bring it back from our back up that has it,