Database Users

Programs missing from market with RUU 2.1

I noticed earlier that m:zombie and m:vampire are not in the market. Any other programs that any of you have noticed are missing?

jlem26 said:
I noticed earlier that m:zombie and m:vampire are not in the market. Any other programs that any of you have noticed are missing?
Click to expand...
Click to collapse
it's because the ruu is signed with test keys, not the release keys, so not everything is showing up.

regaw_leinad said:
it's because the ruu is signed with test keys, not the release keys, so not everything is showing up.
Click to expand...
Click to collapse
That's what I figured but these are the only two apps I have seen missing so far. I was just wondering if anyone else came across more.

jlem26 said:
That's what I figured but these are the only two apps I have seen missing so far. I was just wondering if anyone else came across more.
Click to expand...
Click to collapse
Most of my purchased apps are gone, and they include Basketball, Toss It, Flight Control, and a few others..quite disappointed as I did the RUU install via the .exe file and so far, haven't found a way to undo it and go back to DamageControl 2.1...

spatel9114 said:
Most of my purchased apps are gone, and they include Basketball, Toss It, Flight Control, and a few others..quite disappointed as I did the RUU install via the .exe file and so far, haven't found a way to undo it and go back to DamageControl 2.1...
Click to expand...
Click to collapse
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....

Kcarpenter said:
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Click to expand...
Click to collapse
lol very,very true!

RUU has test-key. thats means no protected apps. You should have flashed one of the many roms based on this RUU(damage,fresh or darchlegend even though its based on the Legend RUU). There already set to go.

Anyway I can do that now?

Lol, not to sound like a jerk but we knew this. I started the thread because I was wondering if anyone else knew which programs were affected. The whole idea behind loading the RUU was to test it out. It would be great if everyone didn't come in here and tell us how we should have loaded a custom ROM. Most of us probably came from a custom ROM to this, like myself.

jlem26 said:
Lol, not to sound like a jerk but we knew this. I started the thread because I was wondering if anyone else knew which programs were affected. The whole idea behind loading the RUU was to test it out. It would be great if everyone didn't come in here and tell us how we should have loaded a custom ROM. Most of us probably came from a custom ROM to this, like myself.
Click to expand...
Click to collapse
Sorry, that was just your first post to the forum, and it had no implications that you knew how to do anything whatsoever. I was just going on what I read from your post. I was guessing you just joined and saw the RUU and flashed it. I am sorry.

regaw_leinad said:
Sorry, that was just your first post to the forum, and it had no implications that you knew how to do anything whatsoever. I was just going on what I read from your post. I was guessing you just joined and saw the RUU and flashed it. I am sorry.
Click to expand...
Click to collapse
Don't be sorry, I wasn't really aiming that at anyone in particular, I was just hoping to head off the thread turning into a point and laugh at the RUU users.

spatel9114 said:
Anyway I can do that now?
Click to expand...
Click to collapse
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image

Well I modified the build.prop last night and now all the apps are showing up in the market.

jlem26 said:
Well I modified the build.prop last night and now all the apps are showing up in the market.
Click to expand...
Click to collapse
Wow, is this easily done? I'm missing root manager, but otherwise am liking the leak (minus sprint crap).
Also.notice quick boot isn't working, but I'm sure its fixable, I just haven't looked or may not have the experience to get it going.

MILH0U5E said:
Wow, is this easily done? I'm missing root manager, but otherwise am liking the leak (minus sprint crap).
Also.notice quick boot isn't working, but I'm sure its fixable, I just haven't looked or may not have the experience to get it going.
Click to expand...
Click to collapse
Yeah it is pretty easy, just need to get your build.prop, then in wordpad, if using windows use wordpad not notepad, just have to make a few changes. After that you clear the market cache. When I did this last night, none of the protected apps showed up, however this morning they all did. So for reason it may take a bit to work right but it did work. Just checked and root manager is showing in my market too.
I'll just post one I found online. If you adb push this to /system/ it should work.

Kcarpenter said:
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Click to expand...
Click to collapse
@Kcarpenter, maybe dont post inflammatory stuff like this and instead be helpful and we wont have drama?
@Jlem
Good to see you got it going. You should share your build.prop (or link to instructions) so others that may have made the early (and quite risky) install of the RUU could get it going. That would be a nice thing to do
Personally I think you're crazy for trying that RUU!!! hahaha ! I'm glad someone did, and I hope it all works out for you.
edit:And you did! good work

Kcarpenter said:
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Click to expand...
Click to collapse
+1 Truth.
I have a feeling many people will do this.

danknee said:
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
Click to expand...
Click to collapse
Alright, so when I go to do that, I get an error "Read-Only File System"..How can I make it read/write?

spatel9114 said:
Alright, so when I go to do that, I get an error "Read-Only File System"..How can I make it read/write?
Click to expand...
Click to collapse
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

jlem26 said:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
or adb remount first.

Can we try EVO's new root method for 1.49?

Ran across this thread in the evo section, seeing how we also have htc's flash lite. It made me hopeful of attaining root. Ive tried every card mentioned as being successful on three different systems:-(
http://forum.xda-developers.com/showthread.php?t=718889

bowtieduece said:
Ran across this thread in the evo section, seeing how we also have htc's flash lite. It made me hopeful of attaining root. Ive tried every card mentioned as being successful on three different systems:-(
http://forum.xda-developers.com/showthread.php?t=718889
Click to expand...
Click to collapse
Even though I didn't really think it would work, I gave it a shot anyway. Naturally, it was unsuccessful. The Eris take FOREVER to load that website, and it never triggers the shell script to ask for a reload, therefore permission is denied for the second part when you reboot with adb shell.
Interesting exploit, though. I wonder if there is some way to modify it for the Eris. Maybe you could contact the devs.

Really, nobody else is interested in this?

MyFixofAndroid said:
Yep that's what I expected. Yea there's gotta be someone here that can do the changes to the EVO files so they work with Eris, and upload the proper files to file sites and have us downloading in no time, so we can get root finally. Yes please anyone here up and willing
Click to expand...
Click to collapse
Toastcfh used to do some work for the Eris someone may want to start there since he provided what looks to be a pretty main part of the EVO root.

sickbox said:
Toastcfh used to do some work for the Eris someone may want to start there since he provided what looks to be a pretty main part of the EVO root.
Click to expand...
Click to collapse
Thanks for the tip. I sent him a PM. Will report back when I find something.

Anyone with an Eris can help out - rooted or unrooted.
I looked at those scripts last night - what seems like the necessary conditions for the beginning of the exploit (part1) are:
(1) there is a directory read/write/traversal permission security flaw in the data area for flash-lite;
(2) apparently, when flash-lite is running it must have root privilege at a moment when it performs a file "chmod" operation
So, an unprivileged user goes in, and makes a symlink (at the correct moment in time) in flash-lite's data area that points to a mtd partition - moments later, flash-lite "chmods" what it thinks is a file in it's data area, but instead, it is chmod'ing the target of a symlink - the normally protected mtd partition.
This allows use of flash_image to write whatever is wanted to that partition - even as an unprivileged user.
It should be easy enough for someone with Linux/Unix command line scripting experience to test to see if these conditions prevail on the Eris. You don't even need to be root - make your symlink point to something in /data/local if you are worried about something bad happening to a mtd partition. Chmod it initially to 600, and see if it get's changed by flash-lite when (and if) you drop the symlink into place.
I would do it, but I've got to go buy all the parts for ( & build) a new computer (no dev station as of last night ).
bftb0

bftb0 said:
Anyone with an Eris can help out - rooted or unrooted.
bftb0
Click to expand...
Click to collapse
Thank you for the detailed explanation. I'll have a look at the scripts, though it's more about learning new things for me, as this exceeds the current state of my unix knowledge. Hope others with more immediate knowledge of the subject will take a crack at it.

The shell script points to sharedobjects within /data/data/com.android.browser/flashlite, but sharedobjects, nor any folder for that matter, exists within that directory on the Eris. Is there a different place this could point; does the Eris have the same objects stored in a different location?

UPDATE: I'm searching my filesystem on my Eris right now to find it. I will report back later with results.
Also If we find a sharedobjects folder (and the right one) then we can point the script in the proper direction and have root very soon.

MyFixofAndroid said:
Maybe the "sharedobjects" folder and other missing folders are really on the Eris, one of you should look for them. Use ASTRO or a different file manager and search most of the whole filesystem and see if you can find "sharedobjects" on your Erises.
In the meantime I'll try the same thing. Maybe there's a search engine for the file system of the Eris that you can get in the Android Market, that would do the trick. A file and/or folder search engine.
If we find a sharedobjects folder (and the right one) then we can point the script in the proper direction and have root very soon.
Click to expand...
Click to collapse
From what I see (and this may just be my eris), the directory probably does exist but we can't touch it:
ls -l
...
drwxrwx--x system system 2010-04-15 02:23 data
...
No read or write permissions to the directory using adb or Astro.
I do have permissions for /sdcard/data on my Eris:
d---rwxr-x system sdcard_rw 2010-06-26 13:26 data
but it doesn't contain the referenced folders and I don't think the browser downloads temporary files to the SD card.

I checked on my other Eris which is rooted. It seems that these may be the directories that we are looking for. However I don't find anything in an app-cache directory.
# find / -name *flashlite
find / -name *flashlite
/data/data/com.android.browser/flashlite
find: /proc/851: No such file or directory
# find / -name com.android.browser
find / -name com.android.browser
/data/data/com.android.browser

Well this appears to be the deal breaker then. Because non-root users of Eris cannot access /data as non-root, they cannot see anything in app-cache, and therefore cannot root yet, at least with this particular method unless there's another way to do it.
We should think of a way to still exploit Flash Lite on Eris, but use a different folder/folders in the Part? scripts that they point to for the operations of the script. This may be possible to do, however, still unlikely to work, and it is still going to be hard at this point.
But does anyone want to give my modified EVO method but for Eris a try? One of you should, so that we can root this thing and get it over with.

jimbonj said:
From what I see (and this may just be my eris), the directory probably does exist but we can't touch it:
ls -l
...
drwxrwx--x system system 2010-04-15 02:23 data
...
No read or write permissions to the directory using adb or Astro.
I do have permissions for /sdcard/data on my Eris:
d---rwxr-x system sdcard_rw 2010-06-26 13:26 data
but it doesn't contain the referenced folders and I don't think the browser downloads temporary files to the SD card.
Click to expand...
Click to collapse
I dont think we would need read write permissions to begin with to use this root, if we had them to start we would be rooted
Because is he using a exploit in flash lite to write to a restricted folder, hes not just found a folder where the permissions aren't set correctly.
If flash lite can invoke admin access and we can exploit it there should be a way to root this.
I am going to the bar going to get some beers for my friends birthday, when I get home I am going to see if I can modify this into an eris root

Yeah JVWARD!
On your rooting effort, all the better, try modifying it for Eris and let all of us know if you succeed, hope you can, so we can get root too. Keep trying it with different changes until you get it to work.
Thanks.

You are able to cd directly into /data/data/com.android.browser/ and then ls, so all hope may not be lost yet. The flashlite directory does not show up, I'm guessing because I haven't used my browser yet so I need to try and get to a flash site and see if it is created. I'm having some problems with the touch screen my leak Eris right now that I'm trying to fix right now if anyone else wants to give it a shot.

You are able to cd directly into /data/data/com.android.browser/ and then ls, so all hope may not be lost yet. The flashlite directory does not show up, I'm guessing because I haven't used my browser yet so I need to try and get to a flash site and see if it is created. I'm having some problems with the touch screen my leak Eris right now that I'm trying to fix right now if anyone else wants to give it a shot.
Click to expand...
Click to collapse
Yes sickbox, by all means, keep trying stuff, and finding that "flashlite" directory etc. till you get it to root. Hope your touchscreen returns to normal, and that you can create the directory that you mentioned in your previous post by using a flash site.

Hey guys, I know this is a tall order, but I want to help. Any chance you could do a "step by step" set of instructions, or at least copy & paste the Evo instructions with the appropriate changes to try this on the Eris? I'm still not rooted, and the SD card Timing root method isn't working for me. I'd like to try something different.

hey can someone with a rooted Eris using a an almost 100% stock Rom setup dump there file system and post it. Anyone using a highly customized Rom don't bother.
Sent from my Eris using Tapatalk

lostpilot28 said:
Hey guys, I know this is a tall order, but I want to help. Any chance you could do a "step by step" set of instructions, or at least copy & paste the Evo instructions with the appropriate changes to try this on the Eris? I'm still not rooted, and the SD card Timing root method isn't working for me. I'd like to try something different.
Click to expand...
Click to collapse
Link to the Evo instructions is in the OP. Currently working to see if it's possible on the Eris, so that's a no-go for now.
Stay tuned.

Team,
I've been working with the scripts with the awesome folks on IRC and have currently gotten thus far:
Part1 - http://pastebin.com/FUJWM3zW
Part2 - http://pastebin.com/6h07zrdm
I believe at this point I've screwed up my FlashLite plugin with my testing, so I'm going to try to recover that and keep moving along.
LR

How to confirm I have unrooted?

Okay unfortunately 5 mins after rooting my phone I noticed my replacement Vibrant has a bad screen. I used the one-click program to root, so I did the same thing to unroot. I downloaded ROM Manager after I unrooted to confirm the phone was unrooted and ROM Manager seems to think so (it told me to root my phone).
However, I am wondering if there is any way to *confirm* my phone has been unrooted (i.e. manually look for the root files and make sure they are not there)? I ask because I reset my phone to factory settings after unrooting, but updated.zip and chromemod folder were still present when I looked under files, which sort of scared me into thinking T-Mobile may be able to detect I had rooted.
Thanks for all the help and wish me luck for my *third* Vibrant.

DarkAgent said:
Okay unfortunately 5 mins after rooting my phone I noticed my replacement Vibrant has a bad screen. I used the one-click program to root, so I did the same thing to unroot. I downloaded ROM Manager after I unrooted to confirm the phone was unrooted and ROM Manager seems to think so (it told me to root my phone).
However, I am wondering if there is any way to *confirm* my phone has been unrooted (i.e. manually look for the root files and make sure they are not there)? I ask because I reset my phone to factory settings after unrooting, but updated.zip and chromemod folder were still present when I looked under files, which sort of scared me into thinking T-Mobile may be able to detect I had rooted.
Thanks for all the help and wish me luck for my *third* Vibrant.
Click to expand...
Click to collapse
You can test this to un-root.
https://www.dropbox.com/s/pyg5sypm9qto7rw/Galaxysroot.apk
I wrote it today. with help.
its posted on another thread.

Erm.. couldn't you just download Terminal Emulator (if it already isn't installed) and type in: "su" (without quotations)

zephiK said:
Erm.. couldn't you just download Terminal Emulator (if it already isn't installed) and type in: "su" (without quotations)
Click to expand...
Click to collapse
^^I second this, if you are not rooted, you will get a "su not found" type of error.
Also in this thread http://forum.xda-developers.com/showthread.php?t=728471 you will find
How to unroot
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
you could also do it from adb.

rhcp0112345 thanks for the app but I think the su way sounds easier.
Thanks zephiK and d_bot! I did the su thing and got a "su not found" error so I guess I am good.

Lakjin said:
rhcp0112345 thanks for the app but I think the su way sounds easier.
Thanks zephiK and d_bot! I did the su thing and got a "su not found" error so I guess I am good.
Click to expand...
Click to collapse
Yep, no su, no root

New to Andriod, sry for noob question, What are the benefits to Root, What changes on your phone??

30Glock said:
New to Andriod, sry for noob question, What are the benefits to Root, What changes on your phone??
Click to expand...
Click to collapse
Well, I know there will probably be a lot of people freaking out on me, but from how I use my phone the only use I've had so far is using cachemate to clear cache, and possibly modding the look of the os. I personally used to it to remove the annoying tmo boot and shutdown sounds/video.

30Glock said:
New to Andriod, sry for noob question, What are the benefits to Root, What changes on your phone??
Click to expand...
Click to collapse
Welcome to Android 30Glock
the main benefit of rooting is to be able to remove bloat-ware. Bloatware plagues the vibrant. Besides that there are other things you can do like custom roms(not many for the vibrant but they will come), with custom roms comes custom themes, also you can increase you cpu frequency. There are a few awesome apps out there that require root (Titanium Backup).
Basically think of it as you have just been given a new windows machine at work, and the admin gave you User permissions, so yeah you can do some cool stuff, but to really get in and have some fun you need admin permissions. To root/unroot this phone it is jaw dropping easy! Thank you samsung. Thank you DEVS!

Install Root Explorer and try to navigate to your system folder.

Moved to general section.

[Q] .sh script help

Hey guys, need some help with this one from some of you with more android/linux experience than me.
In my continuing quest to make Blackhole as customizable as possible I've been working on a way for users to easily install paid apps (legally downloaded of course), and stuff that I don't have available in rom manager in one easy step at the same time the rom is installed. In pursuit of this goal I've found that it's possible for the update-script file inside a clockworkmod zip to call a script in the zip as well. I've gotten it to say it's run the script, but it doesn't do what it's supposed to. here's what i've got:
#! /bin/
busybox cp /sdcard/app/* /system/app/
When I type the command into a terminal on the phone it works. When I open an adb shell and type "bash install.sh" it works. But when I get the update.zip to run the script, or run it in root explorer it just says it's run it, but doesn't do anything.
Is there something I'm missing about how to call the script? Do I need to somehow add the bash program to the zip file so it can run the script right? Has anyone ever done something like this who can point me in the right direction?

do you have an output you can show us?
Sent from my SCH-I500 using XDA App

This is a shot in the dark but does writing to /system/app require root permissions? It could be that you've given your terminal app root, so it runs under su. But when the script is being executed it does not have root and fails, but perhaps the output is being held back a bit and you're not seeing the permission denied.

Steve_ ?!
whoa, didn't expect it to be you of all people
Anyhoo, this is a bit off topic, but I've got a small request, can you somehow make BlackHole 2.4 an option on Rom manager? I don't have DL09 so I can't use 3.0, but I really like the ability to select everything to customize, instead of me going and installing one thing at a time....

Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.

wizang said:
This is a shot in the dark but does writing to /system/app require root permissions? It could be that you've given your terminal app root, so it runs under su. But when the script is being executed it does not have root and fails, but perhaps the output is being held back a bit and you're not seeing the permission denied.
Click to expand...
Click to collapse
Could very well be, it's not showing me any output when i run it the two ways it doesn't work, just says it's been run.
vegittoss15 said:
Steve_ ?!
whoa, didn't expect it to be you of all people
Anyhoo, this is a bit off topic, but I've got a small request, can you somehow make BlackHole 2.4 an option on Rom manager? I don't have DL09 so I can't use 3.0, but I really like the ability to select everything to customize, instead of me going and installing one thing at a time....
Click to expand...
Click to collapse
Haha, caught me. I was trying to remain incognito Yeah, i'll get 2.4 loaded back up on rom manager for you today. But if you flash 3.0 it will upgrade you to DL09 and the DJ05 kernels and modem are compatible, or at least no one i know of has had issues.
imnuts said:
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
Click to expand...
Click to collapse
sdcard is mounted when you go to recovery, because it's got to access the update.zip file on it to install anything. I'll try your code, do you know what to put after SYSTEM: to make it go to the /app directory? thanks for the idea, it's a different way to go, i didn't think about the fact the update-script could access the device if you don't use the "package" tag.

Don't you need to add "sh" to the bin directory and define the script as so:
#! /bin/sh
if you want it to execute properly..

dcow90 said:
Don't you need to add "sh" to the bin directory and define the script as so:
#! /bin/sh
if you want it to execute properly..
Click to expand...
Click to collapse
normally yes, but there doesn't seem to be a /bin/sh directory on my fascinate, only /bin and that's where the cp and mv and cat, etc. are.

I made a script to do this forever ago on my G1 when it first came out... Let me see if I can find it.

This has been done lots of times before. If you look around on xda there are some backup scripts which do the same thing.
Sent from my SCH-I500

imnuts said:
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
Click to expand...
Click to collapse
Well I gave that a shot, and i think it could work, but the recovery wouldnt do it. it says "non-package source path not yet supported" good idea tho.
yutsoku said:
I made a script to do this forever ago on my G1 when it first came out... Let me see if I can find it.
Click to expand...
Click to collapse
If you can that would be great.
n0yd said:
This has been done lots of times before. If you look around on xda there are some backup scripts which do the same thing.
Sent from my SCH-I500
Click to expand...
Click to collapse
I spent a good bit of time searching and most of the scripts I found were much more complex than what i need, or were written to run on a computer, which i've already done.

sonofskywalker3 said:
normally yes, but there doesn't seem to be a /bin/sh directory on my fascinate, only /bin and that's where the cp and mv and cat, etc. are.
Click to expand...
Click to collapse
Thats not the point. You need to set a shell interpreter, not a path. Cwm uses busybox sh, which is in /bin in recovery mode. Google search shebang
Sent from my SCH-I500 using XDA App

jt1134 said:
Thats not the point. You need to set a shell interpreter, not a path. Cwm uses busybox sh, which is in /bin in recovery mode. Google search shebang
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Going to go ahead and parade my stupidity in front of everyone here:
so does that mean i'm right using #! /bin/ or that it should be #! /bin/sh/ or something else entirely? I'm so confused.

sonofskywalker3 said:
Going to go ahead and parade my stupidity in front of everyone here:
so does that mean i'm right using #! /bin/ or that it should be #! /bin/sh/ or something else entirely? I'm so confused.
Click to expand...
Click to collapse
#!/bin/sh for scripts in recovery. #!/system/bin/sh for scripts in android.
Sent from my SCH-I500 using XDA App

God Mode? (solved)

How can I activate God Mode on a rooted XOOM? I want to nullify some stock apps, but Root Explorer is saying they are read only.
Thanks.

[edit] Changed the thread question.

LOL. I didn't know we were playing Quake.
What do you mean by god mode. You already have root. That's all you should need.
Sent from my Nexus One using XDA App

lol.
That might not be the correct term, and it may require a custom rom. Not sure, but on Project Elite for the OG Droid, there's an option under General>System called God Mode that gives you full access to files on the system. That may just be what Actngrezy calls it in PE.
I just want to rename some of the apps that were included on the XOOM. Specifically, I want to nullify the Quick Office apk so I can install the NI Adam version. When I navigate to the apk in Root Explorer, I get an error telling me it's a read only file. I never got that error with the Droid. I can change whatever I want to on that device.

Did you click on mount r/w in root explorer

arrtoodeetoo said:
How can I activate God Mode on a rooted XOOM? I want to nullify some stock apps, but Root Explorer is saying they are read only.
Thanks.
Click to expand...
Click to collapse
Did you install superuser? if so make sure you have allowed root explorer in it. Then on the top left hand side in root explorer hit mount r/w

arrtoodeetoo said:
lol.
That might not be the correct term, and it may require a custom rom. Not sure, but on Project Elite for the OG Droid, there's an option under General>System called God Mode that gives you full access to files on the system. That may just be what Actngrezy calls it in PE.
I just want to rename some of the apps that were included on the XOOM. Specifically, I want to nullify the Quick Office apk so I can install the NI Adam version. When I navigate to the apk in Root Explorer, I get an error telling me it's a read only file. I never got that error with the Droid. I can change whatever I want to on that device.
Click to expand...
Click to collapse
Im just visiting the forum to steal a few files to compare with atrix , how ever if i read your cleverly phrased question correctly and you are trying to remove/freeze some apps that came on the Xoom and you are getting read only error its because to modify anything in the /system dir you need to
1. back up anything you might remove via adb pull or via adb shell cp
2. adb shell
3.su
4. mount -o rw,remount (what ever the path to zoom block is i dont know cause i dont have one ) exp /dev/block/mmcblk0p12 /system
from there you can remove what ever you want out of system dir
5. exp. rm /system/app/quickoffice.apk

Thanks! I never noticed that button before. lol.

you can also get a system uninstaller in the market that will do it for you just the same, I usually use that in case there is more included than just the apk file

PaulG1488 said:
Did you click on mount r/w in root explorer
Click to expand...
Click to collapse
x 2
Sent from my Xoom using XDA Premium App

I thought about the uninstaller thing, but I'd rather not uninstall anything that came on the XOOM just in case. I just add an extra .null at the end of the apk (and associated files, which are easy to find) in case I need to restore them.
For instance, the NI Quick Office app force closes when you just breathe on the freaking tablet, so I had to restore the default one.