I rooted a NookColor with the AutoNooter for 1.0.1 (root, softkeys, google apps) and installed Ubuntu according to this guide. Then I updated to 1.1 (of course). I also have clockwork recovery with backups
Anyways, for some unknown reason: my friend was having problems signing into the market. So I had her erase and de-register. This also apparently removes root. So I used AutoNooter for 1.1. Everything seems to work fine except that YouTube wouldn't launch (which was fine because I signed into it before AutoNooter).
I then uninstalled and pushed YouTube on the device.
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell rm /system/app/Youtube.apk
adb push YouTube.apk /system
adb reboot
The old version of YouTube then worked just fine (didn't use "adb uninstall" because it didn't work). I then installed other non-market apps.
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p6 /data
adb shell rm /data/app/$APPNAME
adb push $APPNAME /data
adb reboot
Some of these apps wouldn't launch [ :'( ]. All of this was done using ADB over Wifi. Anyways, I tried to run bootubuntu (via ConnectBot) and it didn't work. So I figure I out to rerun the script "sh ./ubuntu.sh" and got several "chmod: operation not permitted" errors. I also ran "su" before each command for superuser permission of course. Therefore, I'm not able to boot ubuntu (even though it's still all on the sdcard).
So am I only partially rooted or what? Should I run AutoNooter for 1.1 again?
AVanover5 said:
I rooted a NookColor with the AutoNooter for 1.0.1 (root, softkeys, google apps) and installed Ubuntu according to this guide. Then I updated to 1.1 (of course). I also have clockwork recovery with backups
Anyways, for some unknown reason: my friend was having problems signing into the market. So I had her erase and de-register. This also apparently removes root. So I used AutoNooter for 1.1. Everything seems to work fine except that YouTube wouldn't launch (which was fine because I signed into it before AutoNooter).
I then uninstalled and pushed YouTube on the device.
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell rm /system/app/Youtube.apk
adb push YouTube.apk /system
adb reboot
The old version of YouTube then worked just fine (didn't use "adb uninstall" because it didn't work). I then installed other non-market apps.
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p6 /data
adb shell rm /data/app/$APPNAME
adb push $APPNAME /data
adb reboot
Some of these apps wouldn't launch [ :'( ]. All of this was done using ADB over Wifi. Anyways, I tried to run bootubuntu (via ConnectBot) and it didn't work. So I figure I out to rerun the script "sh ./ubuntu.sh" and got several "chmod: operation not permitted" errors. I also ran "su" before each command for superuser permission of course. Therefore, I'm not able to boot ubuntu (even though it's still all on the sdcard).
So am I only partially rooted or what? Should I run AutoNooter for 1.1 again?
Click to expand...
Click to collapse
First off:
Changing the ROM =/= "rooting". Stop confusing people.
Also, is your friend on ubuntu, or just you? I don't see a correlation.
ace7196 said:
First off:
Changing the ROM =/= "rooting". Stop confusing people.
Also, is your friend on ubuntu, or just you? I don't see a correlation.
Click to expand...
Click to collapse
I realize that. Autonooter does, in fact, root the device. It's my friends.
SOLVED
The NookColor has been sleeping for a while (because I ate dinner) and Ubuntu now works >.< I'm not sure what's up with the apps, but maybe they'll install and launch now. I'll try clearing their caches and what not as well. If anyone has suggestions, feel free to post them.
AVanover5 said:
I realize that. Autonooter does, in fact, root the device. It's my friends.
Click to expand...
Click to collapse
So you running ubuntu has nothing to do with anything? Cool.
Run autonooter again. If apps don't show, just install them from system/app folder. Also fix permissions.
ace7196 said:
So you running ubuntu has nothing to do with anything? Cool.
Run autonooter again. If apps don't show, just install them from system/app folder. Also fix permissions.
Click to expand...
Click to collapse
No, Ubuntu runs off of the SD through VNC. It's not a ROM. I've fixed it already anyways...
ace7196 said:
So you running ubuntu has nothing to do with anything? Cool.
Run autonooter again. If apps don't show, just install them from system/app folder. Also fix permissions.
Click to expand...
Click to collapse
I'm having similar problems with my HTC first But I'm not good w/ coding, so it's a user defect. I can't chmod and so I can't get the device to stay rooted. Some apps can get su and many cannot. Superuser also cannot get su. ??? Any advice?
Related
I am running custom rom Rooted 2.1 v0.3.
Ever since flashing to the custom rom, when i try to push a file, such as:
adb push bootanimation.zip /system/media
I get the error:
Failed to copy.... Read-only file system.
I didn't have this error before flashing to the rom. Does this have something to do with superuser whitelist?
I have tired:
mount -oremount,rw /dev/block/mtdblock3 /system
and it didn't work and I tired:
adb remount
winch returned:
Operation not permitted.
This is ticking me off since I didn't have this problem until flashing the rom.
EDIT: Now if I try:
adb push bootanimation.zip /system/media,
I get:
Permission denied.
This is crazy.
I need help also. Rooting for first time and trying to get recovery.img on and keep getting read only errors. Tried remount to no avail. Help please
su
mount -o rw,remount /Dev/block/mtdblock3 /system
file system is case sensitive!
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
p.s.
make sure you have developer mode enabled "settings" and accept su permissions. Also have BusyBox
fKngFtd said:
su
mount -o rw,remount /Dev/block/mtdblock3 /system
file system is case sensitive!
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
p.s.
make sure you have developer mode enabled "settings" and accept su permissions. Also have BusyBox
Click to expand...
Click to collapse
...it's a lowercase d in dev.
mount -o rw,remount /dev/block/mtdblock3 /system
n2imagination said:
I need help also. Rooting for first time and trying to get recovery.img on and keep getting read only errors. Tried remount to no avail. Help please
Click to expand...
Click to collapse
I had the same problem. From what I could tell, I had the wrong ADB driver somehow. So I downloaded the drivers from the HTC website and went to device manager (Win7) and updated the driver software which fixed the problem. But I think i just lucked out when i stumbled onto that, I feel a blind retard with epilepsy trying to draw a circle on an etch-a-sketch when I'm doing things like rooting. But, it couldn't hurt to try it.
fKngFtd said:
su
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
Click to expand...
Click to collapse
adb install -l whatever.apk (from tools dir in sdk)
`mods said:
I am running custom rom Rooted 2.1 v0.3.
Ever since flashing to the custom rom, when i try to push a file, such as:
adb push bootanimation.zip /system/media
I get the error:
Failed to copy.... Read-only file system.
I didn't have this error before flashing to the rom. Does this have something to do with superuser whitelist?
I have tired:
mount -oremount,rw /dev/block/mtdblock3 /system
and it didn't work and I tired:
adb remount
winch returned:
Operation not permitted.
This is ticking me off since I didn't have this problem until flashing the rom.
EDIT: Now if I try:
adb push bootanimation.zip /system/media,
I get:
Permission denied.
This is crazy.
Click to expand...
Click to collapse
Did you ever get this fixed? I have the same problem!
I have the same problem also. I've been using SDK just fine for over a month or two, and now that I'm on V3, no worky. Somethings obviously going on. But what?!
LexusBrian400 said:
I have the same problem also. I've been using SDK just fine for over a month or two, and now that I'm on V3, no worky. Somethings obviously going on. But what?!
Click to expand...
Click to collapse
I think the proper permissions were not set for this ROM. Hopefully jcase can modify the file and re-upload the ROM =)
at least that's what I've gathered... someone PLEASE correct me if I'm wrong
edit: I looked at the script file and it seems like rw permissions are set properly???
jcase - any insight?
I personally get a bunch of "Out of memory" errors when trying to follow the recovery walk-through.
post baleeted
So I'm rooted and downloaded Super User app from market. I have a bunch of root apps but the only app listed in the super user app is Titanium. Any reason why the other rooted apps (Set Cpu, Minfree Manager, etc.) aren't listed?
Have they asked for superuser?
Via EVO on 4G with XDA App
awenthol said:
Have they asked for superuser?
Via EVO on 4G with XDA App
Click to expand...
Click to collapse
No it doesn't
Sent from my CM6 powered device
krazyflipj said:
No it doesn't
Sent from my CM6 powered device
Click to expand...
Click to collapse
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.
richse said:
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.
Click to expand...
Click to collapse
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...
krazyflipj said:
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...
Click to expand...
Click to collapse
What root did you use? I did mine manually so there may be some differences if you used a one click.
Edit: I just looked at noobnl's one click root and it uses the same script that contains the line:
#copies busybox su
cat /system/bin/jk-su > /sdx/su
so it should definitely be there even if you used his one click.
When you run the command "ls -l /system/bin/jk-su" what do you get?
I get this:
ls -l /system/bin/jk-su
-rwsr-sr-x root root 26264 2010-09-18 06:10 jk-su
Please delete
krazyflipj said:
Please delete
Click to expand...
Click to collapse
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.
richse said:
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.
Click to expand...
Click to collapse
Hey Richse, I'm trying to get this to work but it isn't.
rose1 said:
Hey Richse, I'm trying to get this to work but it isn't.
Click to expand...
Click to collapse
can you give me more information, what errors are you getting or what exactly is happening?
richse said:
can you give me more information, what errors are you getting or what exactly is happening?
Click to expand...
Click to collapse
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.
rose1 said:
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.
Click to expand...
Click to collapse
I'm not sure why cp doesn't work, it just means copy. An alternative to try is to delete jk-su and replace it with the su you updated. Use these commands in place of the cp command:
rm /system/bin/jk-su
cat /system/bin/su > /system/bin/jk-su
Make sure you do this after updating su in the superuser app and without rebooting in between. Let me know if you have any problems.
followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"
spdwiz18 said:
followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"
Click to expand...
Click to collapse
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?
richse said:
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?
Click to expand...
Click to collapse
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!
spdwiz18 said:
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!
Click to expand...
Click to collapse
I doubt you need to update root. The root I used was the original manual method by joeykrim. The one click just automates that method. There is no reason why you should have to reboot multiple times to get this working. You basically just replaced a file with a similar file and the script that was installed when you rooted uses that file to create a new su every time you reboot. Personally, I would wipe to stock with Odin and then use the manual root method to make sure nothing funny is going on with your phone. When you rebooted and the su was "original" you didn't lose root, it just meant that superuser wouldn't work. For now, as long as the 2.3.1 -ef sticks around superuser will work just fine. As an alternative you could try noobnl's newest stuff. Looks like he made it compatible with superuser, so I think that would negate the need to use this type of fix. I'm not sure what he did to add the compatibility but you could probably ask him.
if you flash noobnl's latest kernel, it includes superuser and it works perfectly.
rose1 said:
if you flash noobnl's latest kernel, it includes superuser and it works perfectly.
Click to expand...
Click to collapse
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.
richse said:
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.
Click to expand...
Click to collapse
Very true. I didn't think about that.
I have latest Noobls kernel flashed on top of DI07 and this fix did not work.First thing that dint work is i never got SuperUser prompt after i typed su in adb shell,i got su in windows but no prompt on the phone.
To make it short i did the whole procedure from BetterTerminal(now i got su prompt) rebooted and back to same problem.Man,this been bugin me for two days now,sometimes i reboot the phone and i have root permissions then i reboot again and they are gone!
Big question is:is everybody on Epic have same issue or is it just on certain phones,kernels or roms?
should i flash it. i dont have root
WOW! i cant believe no one has replied to you.
if you take a look at the first post with the topic
[ROM] Official AOSP 2.2 OTA
but you mentioned you dont have root. so try installing alogcat from the marketplace and capture the whole deal. then you can email directly from the app.
logcat isnt going to do much, it prefetches the files, need to pull the update.zip from adb
ok, so i havnt gotten the notice yet.
but need a bit of help prepping for when i do.
i have the android sdk installed on my desktop, and can create a virtual device etc...
but when i open the cmd prompt and try to run adb devices it says it is populating a list but i see no results or no file created.
so i tried just running adb logcat and it stops at waiting for device.
any pointers. im running win7x64 ultimate
well, i screwed it up. i removed the usb drivers and set it to debugging mode and got it working.
so i am able to run adb shell etc...
once i get the notice ill be ready to do an adb pull
adb shell
su
cd /cache/
ls
adb pull /cache/<package_name>.zip .
sepiid said:
well, i screwed it up. i removed the usb drivers and set it to debugging mode and got it working.
so i am able to run adb shell etc...
once i get the notice ill be ready to do an adb pull
adb shell
su
cd /cache/
ls
adb pull /cache/<package_name>.zip .
Click to expand...
Click to collapse
but how do you know the new radio and spl update name?
you should get that by running su then "cd /cache/ ; ls"
right now i have
download-1.apk
downloadfile.apk
recovery
lost+found
so after it is precached i run that "cd cache/ ; ls" i should have another file or two in there
that would be the file you run adb pull /cache/*.*
a tad bit of help, as a test i am trying to do
adb pull cache/downloadfile.apk d:\
but i get
remote object 'cache/downloadfile.apk' does not exist
i also tried adb pull /cache/downloadfile.apk d:\
and get the same.
edit:
tried doing a adb push
D:\android-sdk-windows\tools>adb push d:\test.txt /cache
failed to copy 'd:\test.txt' to '/cache/test.txt': Permission denied
so i dont have permission to put anything there, which means i likely dont have permission to pull from there
D:\android-sdk-windows\tools>adb pull /cache/downloadfile.apk d:\
remote object '/cache/downloadfile.apk' does not exist
so i opened another cmd prompt and and did an adb shell
su
and i am su
so while the other window was open and i was su i tried the same commands again and got the same results.
edit2:
D:\android-sdk-windows\tools>adb shell ls /cache
opendir failed, Permission denied
so it is definately a su/permissions issue.
Are you rooted? If not use Universal Androot.
*anticipation*
sepiid said:
a tad bit of help, as a test i am trying to do
adb pull cache/downloadfile.apk d:\
but i get
remote object 'cache/downloadfile.apk' does not exist
i also tried adb pull /cache/downloadfile.apk d:\
and get the same.
edit:
tried doing a adb push
D:\android-sdk-windows\tools>adb push d:\test.txt /cache
failed to copy 'd:\test.txt' to '/cache/test.txt': Permission denied
so i dont have permission to put anything there, which means i likely dont have permission to pull from there
D:\android-sdk-windows\tools>adb pull /cache/downloadfile.apk d:\
remote object '/cache/downloadfile.apk' does not exist
so i opened another cmd prompt and and did an adb shell
su
and i am su
so while the other window was open and i was su i tried the same commands again and got the same results.
edit2:
D:\android-sdk-windows\tools>adb shell ls /cache
opendir failed, Permission denied
so it is definately a su/permissions issue.
Click to expand...
Click to collapse
Here do this:
First if you have root, open up terminal or cmd prompt if you are on windows:
adb shell
su
mount -o rw,remount yaffs2 /cache
chmod 777 /cache
that will change the permissions allowing for read and write.
Now exit out of shell and just adb pull /cache/
That will pull everything out of the cache partition.
BAM!!! perfect!
i new it was permissions related. just couldnt figure out the "mount -o rw,remount yaffs2 /cache" part. might i ask you to break that down for me? at least the yaffs2 part.
thanks!
so once the update hits i am ready to grab the files.
callmeradical said:
Here do this:
First if you have root, open up terminal or cmd prompt if you are on windows:
adb shell
su
mount -o rw,remount yaffs2 /cache
chmod 777 /cache
that will change the permissions allowing for read and write.
Now exit out of shell and just adb pull /cache/
That will pull everything out of the cache partition.
Click to expand...
Click to collapse
So the YAFFS2 part of the code I put up there is designating the file system in which we are reading/writing.
YAFFS2 is the most popular and widely used format for flash memory.
please allow me.
yaffs2 is a filesystem type. /cache is of course the directory. -o is for option.
rw: read/write
remount: remount /cache again with new option.
sepiid said:
BAM!!! perfect!
i new it was permissions related. just couldnt figure out the "mount -o rw,remount yaffs2 /cache" part. might i ask you to break that down for me? at least the yaffs2 part.
thanks!
so once the update hits i am ready to grab the files.
Click to expand...
Click to collapse
Oh yeah and BTW, you can change the permissions back if you want after your done, otherwise I believe you can just reboot the phone and it fixes it, not entirely sure, I was trying to rewrite my default.prop to get adb remount to work with stock 1.6 rooted, but I am getting and access denied issue.
perfect was about to ask what the -o was but i tried mount --help and mount -h both resulted in nothing. then you reply sharpt71
thanks again all.
i am now ready to pull the update and upload once i get the update. hopefully soon!
Rather than the remounting and chmoding so you can adb pull.
You could probably get away with
Code:
su
cp /cache/<whatever> /sdcard
Then mount the SD card or put it in a card reader.
SilverSurfR said:
Rather than the remounting and chmoding so you can adb pull.
You could probably get away with
Code:
su
cp /cache/<whatever> /sdcard
Then mount the SD card or put it in a card reader.
Click to expand...
Click to collapse
You probably could I just know that this is a sure fire way to grab everything in cache directly to the machine, otherwise if you aren't next to a machine you could probably do a copy like you said.
My 2nd update failed, do you guys think the files are still in my cache?
hey guys,
how would i go about removing apps from an installed custom rom?
ive tried titanium back... doesnt work, tried pulling the apps from the pack nothing,
ive tried root exploits and it just sends your phone into an almost
"paperweight"
like state,
any further moves i can do to remove various bits ? there as some things i just genuinely dont want.
Telling which rom and which apps might help
[ROM] Pays-ROM HD SPARTA v1.0 [ULTRA LIGHT] [19/NOV/10]
[ROM] Pays-ROM HD SPARTA v1.0 [ULTRA LIGHT]
i cant list the apps i want to remove as im off to work, but can you do some background work into it for me??
fkofilee said:
[ROM] Pays-ROM HD SPARTA v1.0 [ULTRA LIGHT]
i cant list the apps i want to remove as im off to work, but can you do some background work into it for me??
Click to expand...
Click to collapse
Have you tried doing it from terminal?
Code:
adb remount
adb shell
su
cd /system/app
ls *
rm INSERTANNOYINGAPPNAMEHERE
reboot
adb pull is not for deleting apps. It is for copying the app to your computer.
when i say pull... lol. i mean removing them from the system completely
fkofilee said:
when i say pull... lol. i mean removing them from the system completely
Click to expand...
Click to collapse
I've just discovered there are issues where /system isn't getting wiped correctly prior to a new rom being flashed. Keep getting apps from other roms and such sitting in my /system folder even after a wipe and flash - at this stage I assume CWM is bugged? Could be your issue is related.
nope the ADB coding doesnt work as its almost like there is a PERMANENT R/w lock on the section i need to remove apps from
unfortunately the issues AERNT related, as ive wiped everything before, these apps are pre installed on the ROM. What does me with this is that the root exploit to remove these apps as in Titanium backup ... just turns the phone into a very expensive paperweight till the battery is remove
weather apps (widgets etc,)
Twitter apps , teet and various other bits i want to remove
fkofilee said:
unfortunately the issues AERNT related, as ive wiped everything before, these apps are pre installed on the ROM. What does me with this is that the root exploit to remove these apps as in Titanium backup ... just turns the phone into a very expensive paperweight till the battery is remove
weather apps (widgets etc,)
Twitter apps , teet and various other bits i want to remove
Click to expand...
Click to collapse
Get a new rom ???
hmm flash a new rom??this is the most refined rom i can find for DHD.
for that reason its more of a hassle to flash new roms
I would rather crack it, mind you i might be really thick asking this. that code you gave me have i got to get the adb.exe from android SDK and do this via a cmd.exe window on my pc or have i got to do it on my phone via termnial emulator.
how weird!!!... i used to terminal emulator to allow su (I.E to give system SU Permissions and now i can remove the apps ) haha
Shocked!!
Admin Please close & Deleted Thread.
fkofilee said:
hmm flash a new rom??this is the most refined rom i can find for DHD.
for that reason its more of a hassle to flash new roms
I would rather crack it, mind you i might be really thick asking this. that code you gave me have i got to get the adb.exe from android SDK and do this via a cmd.exe window on my pc or have i got to do it on my phone via termnial emulator.
Click to expand...
Click to collapse
Yes from the android sdk. It *should* work from a terminal emulator as well if you run these commands first to mount the /system/app directory as read/write:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
chmod 777 /system/app
Other option would be to use the root explorer app, it is a paid app though well worth it.
dr.m0x said:
Yes from the android sdk. It *should* work from a terminal emulator as well if you run these commands first to mount the /system/app directory as read/write:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
chmod 777 /system/app
Other option would be to use the root explorer app, it is a paid app though well worth it.
Click to expand...
Click to collapse
Weird thing is i tried root explorer , and it still wouldnt R/W the app folder... but as i said now solved... slightly weird though that i completely missed that lil bit on the su permissions for the system directly.
fkofilee said:
Weird thing is i tried root explorer , and it still wouldnt R/W the app folder... but as i said now solved... slightly weird though that i completely missed that lil bit on the su permissions for the system directly.
Click to expand...
Click to collapse
Yeah you ninja'd my last post
Glad to hear you're gtg now.
but mind you the mount script i ran and it didnt work lol.... maybe i did them the wrong way round, (Raise SU first then do mount cmd??)
dr.m0x said:
Have you tried doing it from terminal?
Code:
adb remount
adb shell
su
cd /system/app
ls *
rm INSERTANNOYINGAPPNAMEHERE
reboot
adb pull is not for deleting apps. It is for copying the app to your computer.
Click to expand...
Click to collapse
Works. Thanks!
Ok.... I have googled them all and done a search on this website and have found nothing that is similar to my situation. I hate when people ask questions that are found in other forums and would not want to do the same... but I don't feel my situation is in the realm of that.
I followed all the basic ways of rooting and none worked for me. I did the Visionary (ver 14) root and root.zip (/root to sdcard), etc.... didn't work.
Finally Id/l Visionary for temp root.... and I followed http://forum.xda-developers.com/showthread.php?t=858996.
I got S=OFF, but had to 'sync' in terminal 5 or 6 times to be able to get su to work.
I finally get su to work (# instead of $ in terminal) and all the programs that require root to work do as they are supposed to. The main issue I have, is that without running visionary (with R/W access), I cannot delete files without it warning that I have read only access.
I thought if I had root access, I wouldn't need to set up Write access.
Once I run visionary, and delete *.apk files that came with my phone, they do stay away perm.
I just want to know if there is a way to keep the R/W access without visionary since I know I am in root.....
Root access is a separate entity from S-off, and that a separate entity from /system partition read/write mounting. That partition is read/only at boot. You can make it writable with adb, with Root Explorer, or with a linux mount command.
HTC Glacier running CM7 #33
root explorer has a button to push to mount r/w, or if you have adb setup you can plug in your phohne and type
adb remount
and you'll be r/w
or you can use terminal emulator and type
su
mount-o,remount -rw /dev/block/mmcblk0p25 /system
exit
and you'll be r/w
option94 said:
...
su
mount-o,remount -rw /dev/block/mmcblk0p25 /system
exit
and you'll be r/w
Click to expand...
Click to collapse
I see two typos in the command. There should be a space between mount and -o, and no comma between the -o and remount. Thus:
Code:
# mount -o remount -rw /dev/block/mmcblk0p25 /system
Of course, "adb remount" from a nearby PC is so much easier.
Thanks. I just woke up when i started typing that.
and the , will work with no space. Both methods are fine.
Thanks guys!
On another note, do either one of you know if you can mount the phones system folder as a drive on Vista like you would be able to do with the SD Card?
Im not talking with adb shell... More like using Windows Explorer
Nope. Only the "external" SD card can be mounted via USB, sorry.
This might be what your looking for.
adb commander
option94 said:
This might be what your looking for.
adb commander
Click to expand...
Click to collapse
That is close enough. Thanks option!