Database Info

Metamorph not working

Well I am trying to install metamorph on my girlfriends rooted EVO to give her the modified notification bar but when I try to open it it says there is not enough space on /system. There is plenty of space both on the phone and sd card, tried re-installing with no luck. This never happened when I used it on my phone.
Is there any other way other than adb to install that modified notification bar?

I had the same issue with metamorph, fixed it by using root explorer to mount /system as RW. Make sure you remount it as RO after you reinstall metamorph
Sent from my PC36100 using XDA App

Yeah I read about that method but I am being kind of cheap lol Is there not another way?

punkerEVO said:
I had the same issue with metamorph, fixed it by using root explorer to mount /system as RW. Make sure you remount it as RO after you reinstall metamorph
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well looks like that will be the only way then. Is there a guide on how to do this exactly?

Still cant get this to work...

Just keep trying it, mine said that the first two times and when I tried again it was working. Its seems to be a bug or something, keep trying.

Tried numerous times over the past 3 weeks. Also tried root explorer by mounting /system as rw and nothing.

What info?
Anyone have a solution yet?

Did you run busy box before mounting as RW?
Sent from my PC36100 using XDA App

VOODOOTRIP said:
Did you run busy box before mounting as RW?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
How exactly do I do that? Doesnt CM6.1 come with it or do I install via titanium backup?
And do I just go into root explorer, mount, and then exit and then try to open metamorph again?

In hboot at the top does it say s off? I had this sort of problem before and found out that I had s on.(not sure how it came back on though) if that is the case there is an update.zip in the unrevoked thread that will fix it.

Ill check when I have the phone again later (its my girlfriends). Used the new unrevoked to root it.

cheyne1 said:
In hboot at the top does it say s off? I had this sort of problem before and found out that I had s on.(not sure how it came back on though) if that is the case there is an update.zip in the unrevoked thread that will fix it.
Click to expand...
Click to collapse
That did it. Thank you!

I had this same problem.
If you manualy open the apk and put the zip and zipalign into system/xbin it will fix your problem
Sent from my slutty assistant. (HTC incredible)

synisterwolf said:
I had this same problem.
If you manualy open the apk and put the zip and zipalign into system/xbin it will fix your problem
Sent from my slutty assistant. (HTC incredible)
Click to expand...
Click to collapse
Once I flashed unrevoked forever to s-off it started up just fine.

[Q] issue with root explorer

Okay, so I know i'll probably get chewed out b/c this has probably been asked before but here goes
I am using Huawei Ascend through metro pcs. I updated last night from 2.1 to 2.2. I've rooted using gingerbreak. However NOTHING I do allows me to remove the pre loaded metro crap. I loaded root explorer per someone on heres advice, and mounted it to r/w however when I click the folder to get to the apps it says it is in r/o. It doesn't matter how many times I click it, it will not change to r/w.
I also tried deleting them with titanium back up...but it wont let me.

Those are temporary mounts of RO to RW. I use SUFBS like RE but does more and you can quickly change your system from RO to RW, but when you close the app it goes back to RO.

I was literally just coming back to update this. I figured it out. You have to use Root Explorer 2.16. Once I loaded that it worked fine with 0 problems! Thanks for the response though

[Q] Unknown error code during application install: "-110"

I'm getting this error when I try to install any app.
I can't seem to install/update any app.
What could be the cause? I tried rebooting, deleting market cache, etc, but it doesn't work..
-Solved-

Solved how?

Yeah, thanks for helping others out...

Experiencing this very issues on a rooted Desire HD on Mike's great Android_Revolution_HD-4G_6.1.1 ROM - clean install but certain market apps, quidco, we7 are two that generate it - they throw up this very error, if you close it and re-install the app it then installs without issue but completely fails to run - really frustrating - anyone have any ideas on a fix?
If I figure it out I'll post my fix.

Reflash ROM, delete dalvik cache, delete Market cache (Settings -> Applications -> Manage applications -> Market -> Clear cache), and reflash kernel (if you use custom kernel).
That seemed to have worked for me.

Jungbum - Thanks.
I did a full wipe and clean rom install, titanium backup to put all apps and sys data back and all is fine now. =)
Not sure why it went screwy!

The Media Container Service 2.2 is the culprit. Unfreeze it (for those using Titanium Backup) or someone post the .apk so folks can reinstall it. I found this out while getting rid of AT&T bloatware and trying to minimize the apps that start on boot.
Hope this helps!

Solved
I solved it by copying "DefaultContainerService.apk" back to the /system/app/
folder and Im able to download from "Market" again smoothly without any error
happened before.

i put the defaultcontainer apk back but i still get the error. i tired clicking on the apk, installing it but says unsuccessful. any other ways to install the defaultcontainer apk

hey guys. i resetted my phone and now i dont know how to do this coz i cant install anything in my phone. so i cant use the titanium buckup and stuff coz i cant even download it. question.. how can i put "DefaultContainerService.apk" if i dont have any file managers. ?

hi. I have the same problem with error 110.
the service com.android.defcontainer.DefaultContainerService.apk was frozen on Package Access Helper in System Tuner Pro
Mabe is useful for someone

Disable encryption
I had this problem on my HTC Wildfire S (this thread showed up when I was looking for a solution)
Anyway, every time I tried to install an app from the Market, I got this unknown error -110 message and the install would fail, however if I attempted to download and install the same app again after the error popped up it would install correctly.
I stopped getting this problem after I disabled encryption of the internal memory from the settings.
So if anyone else is facing this problem, you might want to check if the encryption setting is causing any problems
(Menu > Settings > Storage > Internal storage : Storage encryption)

Clearing the Dakvil cache via Titanium backup app and clearing the market cache (via settings>application>Managed app> and selecting the Market or google play app) seemed to solve it for me using B63M phone Gingerbread 2.3.5.
I was trying to update my app (whatsapp) and I got the error 120 thingy, now its fine after the cache wipes.
However here is the DefaultContainerService.apk attached.
Cheers

Had this problem too.
Problem was: me freezeng theackage acces helper.
After unfreeze installing apps seems to work

Solved!
Not sure what, but one these things worked for me; I have culled these instructions from various sites including XDA.
1. settings -> applications -> manage applications -> market,Market Updater, Download Manager etc. -> uninstall updates, clear Cache ;
2. Unmount your SD card and reboot
3. Clearing the Dalvik cache via Titanium backup app
4. If you are rooted, use ROM Manager to fix permissions; reboot
5. I solved it by copying "DefaultContainerService.apk" back to the /system/app/
folder using root app ES File Manager and I was able to download from "Market" again smoothly without any error
happened before.I downloaded "DefaultContainerService.apk" from here:
http://forum.xda-developers.com/attachment.php?attachmentid=1179676&d=1341537886
Keep trying. Good Luck! :good:
Sangram

Error 110
I kept getting an error code 110 on the Nexus 7 and tried all the quick fixes, clearing cache, clearing data, etc but none worked. What I wound up doing is a hard reset. This worked fine and I can download apps again. I could do this because I had a back up of my tablet and so it was simple to just reinstall after. If you don't back up I'm very sorry but you may find a reason to after this. Hope this helps.

I just thought I'd post this to hopefully help out anyone who may have this same problem. I literally tried for 24 hours+ straight with no sleep trying to get my phone (Motorola XT860 a.k.a. Milestone 3) to be able to install apps again... after everything else failed (factory reset, data/cache clearing, SD card unmount/mounting, formatting my internal storage and SD card, deleting the .android_secure file/folder, etc. etc.), I finally installed RSDLite and the Bell SBF and then flashed it and it worked! Hopefully this helps someone! Cheers
p.s. this is my first post, so I can't provide DL links for RSDLite and the SBF, but they're pretty easy to find. If you can't find them, PM me and I'll send them to you.
p.p.s. eff you, "unknown error -110"!!!
p.p.p.s. just noticed this was in the nexus s forum, but it was the first google result that popped up when I searched for the 110 error... buy ya, basically my post applies to all android phones, so just flash the stock software for your provider/specific phone and it should fix the installation error. Good luck!

This may be an inactive thread, but the solution of re-installing DefaultContainerService.apk worked for me.
My phone is the Kyocera Hydro, and I guess for some reason I removed that by accident.
Thanks!

Error Code 101
Hi,
Samsung Galaxy S Rooted
Downloaded DefaultPackageContainer.apk and put it in my phone's sdcard
In adb shell command running as super user (#) I try to copy the DefaultContainerService.apk file to /system/app but I get an error:
cat /sdcard/DefaultContainerService.apk > /system/app/DefaultContainerServicek
cannot create /system/app/DefaultContainerService.apk: read-only file system
so I run the following command but it doesn't work as nothing happens
# mount -o remount,rw /system
mount -o remount,rw /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Is like I am using the wrong options but no idea what I am missing. Any help is much appreciated.

Copying files
Solved issue below by executing as superuser
mount -o remount,rw -t yaffs /dev/block/st19 /system
and then
cat /sdcard/DefaultContainerService.apk > /system/app/DefaultContainerService.apk
Just executing mount will give you the details to replace /dev/block/st19 with whatever your phone uses
Cahaza said:
Hi,
Samsung Galaxy S Rooted
Downloaded DefaultPackageContainer.apk and put it in my phone's sdcard
In adb shell command running as super user (#) I try to copy the DefaultContainerService.apk file to /system/app but I get an error:
cat /sdcard/DefaultContainerService.apk > /system/app/DefaultContainerServicek
cannot create /system/app/DefaultContainerService.apk: read-only file system
so I run the following command but it doesn't work as nothing happens
# mount -o remount,rw /system
mount -o remount,rw /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Is like I am using the wrong options but no idea what I am missing. Any help is much appreciated.
Click to expand...
Click to collapse

[Q] Wrong SU Permissions Warning in TB

Hi,
I rotted my phone on 2.3.5 and followed manual upgrade process to get 2.3.6 and indeed it worked fine with keeping root.
Of late, when ever I run TitaniumBackup it give me warning as
"Your ROM is rooted but SU binary has non-optimal access rights, which may cause problems
Titanium Backup Pro can fix this problem automatically in many cases. Do you want to proceed? "
When I say "Yes. do it", it gives me message as
"Access rights on "SU" binary was succesfully corrected from "0:0:[4755]" to "0:0:6755" " and asks to restart for apply changes.
Once it restarted it didn't seems to apply changes and asks me same question when I re-open TB.
I understand it has something with access rights files but not sure how to fix this. [we moved SU to diff path to keep root, is that causing issues?] Can someone help me.
Thank you.

Did you upgrade to root using adding 'chmod 4755' to mount_ext3.sh ?

Shaliuno said:
Did you upgrade to root using adding 'chmod 4755' to mount_ext3.sh ?
Click to expand...
Click to collapse
I think so, used below method.
go to /system/bin/
open in text editor – mount_ext3.sh
add the 3 following lines to the very bottom
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 4755 /system/app/Superuser.apk
I did used ES File explorer to perform this. I also read posts mentioning the problem because of ES, how ever I performed this earlier even before complaints and never had problem as it stayed Rooted, so left as it is.
I also installed SU updated from market as I had problems with updating SU binaries.

Not sure but that is the problem I guess.
On every start this script is executed and besides its normal function, it also changes permissions to maintain root. Titanium changes these permissions but upon restarting all reverts back.
Strange thing is I also got Titanium and it doesn't say anything.
Or maybe ES Explorer really messed something up, so the root stays but something ese like Titanium doesnt like it

Shaliuno said:
Not sure but that is the problem I guess.
On every start this script is executed and besides its normal function, it also changes permissions to maintain root. Titanium changes these permissions but upon restarting all reverts back.
Strange thing is I also got Titanium and it doesn't say anything.
Or maybe ES Explorer really messed something up, so the root stays but something ese like Titanium doesnt like it
Click to expand...
Click to collapse
That is correct, I still see Superuser and TB says as Root Access OK in first screen. So Root seems fine with all restarts but not the access settings.
As far as ES File explorer, I used that for editing but once I knew its rooted in 2.3.6 I removed root access from ES File explorer.
not sure as this needs to be fixed. TB does have option, so we could mute the notification about access permanently but I kind of like to make sure this isn't causing some other issue.

sazhagianambi said:
That is correct, I still see Superuser and TB says as Root Access OK in first screen. So Root seems fine with all restarts but not the access settings.
As far as ES File explorer, I used that for editing but once I knew its rooted in 2.3.6 I removed root access from ES File explorer.
not sure as this needs to be fixed. TB does have option, so we could mute the notification about access permanently but I kind of like to make sure this isn't causing some other issue.
Click to expand...
Click to collapse
Don't worry about what TB says.... 6755 is a security hole that you do not want to leave open.... I would use something else.... I am a UNIX/Linux guy by trade, so I am telling you that 4755 is what it should be... Use root explorer and ROM manager instead of TB, I have had way to many issues with TB in the past.

Could you tell please what kind of issues you had?
Im using TB for backing up apps+data and freezing stock/old ones I dont use. Dont want to get by suprise if it goes mad

Thank you!
jimbridgman said:
Don't worry about what TB says.... 6755 is a security hole that you do not want to leave open.... I would use something else.... I am a UNIX/Linux guy by trade, so I am telling you that 4755 is what it should be... Use root explorer and ROM manager instead of TB, I have had way to many issues with TB in the past.
Click to expand...
Click to collapse
Thank you Jim for clearing up, may be I should setup ignore warning then.

Shaliuno said:
Could you tell please what kind of issues you had?
Im using TB for backing up apps+data and freezing stock/old ones I dont use. Dont want to get by suprise if it goes mad
Click to expand...
Click to collapse
TB can and has messed up backups, frozen apps come unfrozen at the worst times, it has a minimal busybox, it has broken root before, it is just more of a headache than anything else... there are several apps that will give much better results.
For freezing apps, try modaco's eazy freezy
For backups, use ROM manager, way more successfull, and VERY stable and tested, and the backups it uses are the same that most manufactures deliver in the fxz and updates, since they are saved in img files, and they can be restored from a default recovery if you really are stuck, and can not even get into it on boot...
For busybox, there are two really good ones, I personally use busybox installer from JRummy16, also the one from Stephen (stericson) is really good too, and I have used it, but had an issue with a version several versions ago, and switched.
I am not bashing TB in any way, so no flames, if you like it.... This is just my experience and I have been using android since 1.4-1.5 version, and I have seen a lot of things....

[Q] How do I temporarily "unroot" device?

Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G

Questions belong in Q&A. Moved

artisticcheese said:
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Click to expand...
Click to collapse
i cant c y u would have to unroot, it shouldnt matter as apps dont care if it is rooted or unrooted, correction some apps u have to b rooted to work properly.
do u actually get an error message when trying to install an app
the only way is to restore back to stock, or if u just rooted ur stock firmware, meaning u didnt flash a rom, u can try flashing the system.img file, that might work but i never heard of any1 doing that

Yes, application refuses to work telling me that "rooted" phones are not supported. So basically it installs, checks if phone is rooted and refuses to proceed. I hoped I can flash something in CMW to temporarely unroot, then run application, let it do it one time thing (I need to run this application only once successfully) and then I root back in CWM again.

artisticcheese said:
Yes, application refuses to work telling me that "rooted" phones are not supported. So basically it installs, checks if phone is rooted and refuses to proceed. I hoped I can flash something in CMW to temporarely unroot, then run application, let it do it one time thing (I need to run this application only once successfully) and then I root back in CWM again.
Click to expand...
Click to collapse
dont think there is a temporary unroot method, going back to stock was the true method to unrooting, which app were u trying to install.
u can trying going back to stock, installing app, let it do its thing, backup with tibu or some other backup, reroot and then restore backup of app.....maybe wont work as restoring a backup is actually reinstalling the app
edit: try this i havent so try at ur own risk http://www.thespicygadgematics.com/2012/06/how-to-easily-unroot-any-android-phone.html it seems easy enough, i didnt think it was possible but it seems to b

artisticcheese said:
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Click to expand...
Click to collapse
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.

cschmitt said:
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
Click to expand...
Click to collapse
thats deleting the app the rooted the phone, but does it actually undo the rooting process, the system files the app changed to make it rooted r still there, the way to check is if u do delete su app, c if root explorer can can mount ur system folder to r/w, or op can c if it the app does install after deleting su.
actually u need su to grant su, so that might not b a good test

cschmitt said:
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
Click to expand...
Click to collapse
Thanks,
How do I root back after that though?

vincom said:
thats deleting the app the rooted the phone, but does it actually undo the rooting process, the system files the app changed to make it rooted r still there, the way to check is if u do delete su app, c if root explorer can can mount ur system folder to r/w, or op can c if it the app does install after deleting su.
actually u need su to grant su, so that might not b a good test
Click to expand...
Click to collapse
The superuser cwm zip installs su and superuser.apk, that's it. There are no other modified apps.
You can remove busy box also if you like, but it's not much use without su.

artisticcheese said:
Thanks,
How do I root back after that though?
Click to expand...
Click to collapse
Flash superuser zip in cwm.

cschmitt said:
The superuser cwm zip installs su and superuser.apk, that's it. There are no other modified apps.
You can remove busy box also if you like, but it's not much use without su.
Click to expand...
Click to collapse
kool. i learn something everyday

There is cool app in Playstore (free) which allows rooting/unrooting with no reboots and other complicated steps
FYI
https://play.google.com/store/apps/...51bGwsMSwxLDMsImV1LmNoYWluZmlyZS5zdXBlcnN1Il0

Voodoo OTA can do a temp unroot as well. The Flixter app will not allow you to stream movis on a rooted phone. I used Voodoo to temp unroot then went back into Flixter and it started to play the movie.

I use an app called Temp root remover
It allows you to temporarly unroot and reroot in a matter of seconds