How to get access to root filesystem (or fix permissions)? - Sony Xperia Z Ultra

I'm trying to copy some files to the root of my Ultra 6833 filesystem but I keep getting a "no space" error. I searched a bit and found out that this may be caused by either permissions needing to be fixed or a device specific restriction that has to be removed.
Well I can't find "fix permissions" option in CWM recovery or ROM Manager anymore. Can someone please point me in the right direction to fix this thanks.
Edit: Sorry brainfart happened - I can use fix permissions in ROM Manager (not Toolbox) - but that hasn't fixed the issue.
I'm using PAC 12-13-13 firmware if that makes a difference.
Edit: Sorry fixed it ... forgot you had to mount the partition. Maybe I should go back to bed?

diji1 said:
I'm trying to copy some files to the root of my Ultra 6833 filesystem but I keep getting a "no space" error. I searched a bit and found out that this may be caused by either permissions needing to be fixed or a device specific restriction that has to be removed.
Well I can't find "fix permissions" option in CWM recovery or ROM Manager anymore. Can someone please point me in the right direction to fix this thanks.
Edit: Sorry brainfart happened - I can use fix permissions in ROM Manager (not Toolbox) - but that hasn't fixed the issue.
I'm using PAC 12-13-13 firmware if that makes a difference.
Edit: Sorry fixed it ... forgot you had to mount the partition. Maybe I should go back to bed?
Click to expand...
Click to collapse
Lols... Brainfarts aside, I personally love to see people's processes written like this, makes me giggle. Well done for sorting it and this is a good guide for others should they face the same issue.
Sent from my C6833 using XDA Premium 4 mobile app

Related

[Q] ClockworkMod Feature

Here's something i've always wondered about clockworkmod, what does the "fix permissions" do?
i've tried to google, and i've only seen threads about people having issues and how they should run the "fix permissions" in clockwork.
It fixes permissions, which sometimes fixes force closes.
briankao1992 said:
It fixes permissions, which sometimes fixes force closes.
Click to expand...
Click to collapse
permissions of what? I know it fixes permissions (otherwise they wouldn't call it "fix permissions"). And i know it can help w/ FC, but what permissions does it fix?
geoffcorey said:
Here's something i've always wondered about clockworkmod, what does the "fix permissions" do?
i've tried to google, and i've only seen threads about people having issues and how they should run the "fix permissions" in clockwork.
Click to expand...
Click to collapse
When you download your apps, it will tell what all information it will try to access, data services, phone calls etc. Fix permissions, sets this permissions back for those, so that they have access to all the info they need to perform correctly.
This was really needed for way back in the day with phones like the g1 where we would use a partition of our sd cards to store our apps to free memory. Not really needed now.
chichu_9 said:
When you download your apps, it will tell what all information it will try to access, data services, phone calls etc. Fix permissions, sets this permissions back for those, so that they have access to all the info they need to perform correctly.
Click to expand...
Click to collapse
s15274n said:
This was really needed for way back in the day with phones like the g1 where we would use a partition of our sd cards to store our apps to free memory. Not really needed now.
Click to expand...
Click to collapse
oh i see, well thanks for the info!

[Fixed] Fix Permissions (With Rom Manager and Without)

Make no mistake, I do not condone the use of Rom Manager due to our neglect.
Still, it has its purposes. I have fixed the "Fix Permissions" function. Do NOT install the market version!
Install this one instead. It may not work with Rom Manager Premium license. (I can live with that).
This has only been tested with superclean.
RomManager.apk
Fr just the script (run via adb shell or terminal emulator)
http://dl.dropbox.com/u/2056318/update-template/fxpms.zip
Install via clockwork, then run fxpms. Requires superuser permissions.
adrynalyne said:
Make no mistake, I do not condone the use of Rom Manager due to our neglect.
Still, it has its purposes. I have fixed the "Fix Permissions" function. Do NOT install the market version!
Install this one instead. It may not work with Rom Manager Premium license. (I can live with that).
This has only been tested with superclean.
RomManager.apk
Fr just the script (run via adb shell or terminal emulator)
http://dl.dropbox.com/u/2056318/update-template/fxpms.zip
Install via clockwork, then run fxpms. Requires superuser permissions.
Click to expand...
Click to collapse
Ok stpiid question. Do I have to do all of this or just install the apk?
Either or, but not both. That would be silly.
That's what I thought. Thanks. And this will work in cwm also?
Thanks, does this include the battstat fix as well?
Can't get the apk to install.
Other forums show that you need to uninstall the market ROM Manager before installing this one. That's how I did, uninstall, then install through root explorer or super manager.
Thanks man works!
Sent from my SCH-I500 using XDA App
Worked like a charm, installed through astro. Great work as always adrynalyne.
when do you sleep man your a beast! thanks a ton!
Had to uninstall the liscence. Duh
What was wrong with it to begin with? I just ran it on my phone about an hour before seeing this post. Did it not do what it's supposed to do?
Anyone running Froyo had issues with it. It would run in 1 second which obviously is too fast. It was not fixing any permissions. Just acting like it was.
Will it still not work in clockworkmod? I flashed the zip and still couldn't run it. Runs in Rom manager t though
Sorry for being ignorant, but exactly what permissions is the permissions fix supposed to fix, and why would I need to apply such a fix?
Edit: Nevermind, was having a hard time finding this answer on Google, but I finally found it. Looks like it just simply reapplies all proper permissions to system app files to fix FC errors and such, presumably in the event that you are messing with the system files and the permissions get messed up on them. I'm guessing I'll never need this function unless I start manually changing system files around or something.
ivorycruncher said:
... I'm guessing I'll never need this function unless I start manually changing system files around or something.
Click to expand...
Click to collapse
Such as, for example, deleting batterystats.bin
Another Fascinating post by my XDA app...
jmcintire said:
Such as, for example, deleting batterystats.bin
Another Fascinating post by my XDA app...
Click to expand...
Click to collapse
Doubtful, seeing as it's kind of hard to change permissions on something you've deleted.
Posted from my EB01 SuperClean Fascinate with Voodoo
dalrym05 said:
Will it still not work in clockworkmod? I flashed the zip and still couldn't run it. Runs in Rom manager t though
Click to expand...
Click to collapse
I'm curious about this as well.
Thanks for all of the hard work so far!
ivorycruncher said:
Doubtful, seeing as it's kind of hard to change permissions on something you've deleted.
Posted from my EB01 SuperClean Fascinate with Voodoo
Click to expand...
Click to collapse
Wouldn't deleting any system file like that affect the permissions on other apps, making it necessary to fix the permissions every time? Besides, the system rebuilds batterystats.bin from scratch immediately after it's been deleted.
Another Fascinating post by my XDA App
How on earth would deleting one file affect permissions on other files? That just doesn't happen. As for the file getting recreated, the OS should be smart enough to set the correct permissions on it.
The only time I can see this being necessary is if things don't work right after installing a new rom, or if you manually change apks or other system files. I've messed around with system files before, and never once had to fix any permissions, probably because I always took care to set the correct permissions manually when doing so.
Posted from my EB01 SuperClean Fascinate with Voodoo

[SOLVED][Q] Low Storage Space Warning

I had flashed RootBox, the most recent one, and I started getting Low Storage Space warnings after every reboot. I thought reflashing might solve this problem, so I did the following :
1. In recovery, Wipe Data/ Factory reset
2. Wipe Cache
3. Wipe Dalvik Cache
4. Format /system
5. then Flashed SlimBean 4.2.2 v1 Stable
Now, again I am getting the same problem, I haven't installed many apps though, the list of apps installed are:
1.Chrome
2.Download All Files
3.ES File Explorer
4.Titanium Backup
5.instagram
6.Maps
7.jetAudioPlus
8.MX Player
9.ROM Toolbox
10.Viber
11.WhatsApp
12.YMail
That's All...
I don't know what problem might be.. I have also searched a lot, in XDA as well as Google. but no suitable solution.
Anyone can help me solve this.??
guru_iyer said:
I had flashed RootBox, the most recent one, and I started getting Low Storage Space warnings after every reboot. I thought reflashing might solve this problem, so I did the following :
1. In recovery, Wipe Data/ Factory reset
2. Wipe Cache
3. Wipe Dalvik Cache
4. Format /system
5. then Flashed SlimBean 4.2.2 v1 Stable
Now, again I am getting the same problem, I haven't installed many apps though, the list of apps installed are:
1.Chrome
2.Download All Files
3.ES File Explorer
4.Titanium Backup
5.instagram
6.Maps
7.jetAudioPlus
8.MX Player
9.ROM Toolbox
10.Viber
11.WhatsApp
12.YMail
That's All...
I don't know what problem might be.. I have also searched a lot, in XDA as well as Google. but no suitable solution.
Anyone can help me solve this.??
Click to expand...
Click to collapse
Its viber thats causing your problem look here http://forum.xda-developers.com/showthread.php?t=2117444 under the letter S for storage. I found this answer in 15 seconds under the root box thread. Please look at rom threads for solutions before posting.
Viber Low Storage error when pressing "Hold to Talk"
gaosphappy said:
Its viber thats causing your problem look here http://forum.xda-developers.com/showthread.php?t=2117444 under the letter S for storage. I found this answer in 15 seconds under the root box thread. Please look at rom threads for solutions before posting.
Click to expand...
Click to collapse
None of the suggestions in this thread worked for me. Including the alternative thread you suggested.
Although my problem has very similar symptoms - the cause (and therefore the solution) is different.
Symptoms: Viber (version 4.1.1) gave me a "Low Storage Space" message whenever I pressed the "Hold and Talk" button.
My Solution: I discovered that there was a file called "_ptt_id_counter" in folder /data/data/com.viber.voip that had incorrect uid/gid.
The uid/gid were not the same as every other file and folder in this subtree.
I guess that "ptt" means "press to talk". I also guess that the id_counter (4 bytes in size) is probably a long integer and should be able to be
both written and read. The permissions were only 600 on the file. So, I used adb to chown the uid & gid to be the same as the other files/folders.
It then worked.
I am not an Android programmer. However, I have worked with Unix since 1982 and Linux since 1997.
I also tried booting into recovery and running permissions check/fix. But, I guess there isn't a manifest that specifies what the correct file permissions should be? (I haven't got that far in my OO learning).
I think the culprit that (somehow) caused the error was the Backup app I was using. (Ultimate Backup by Jrummy) but, I can't be sure and I don't want to "point the finger".
If someone could please tell me where in an APK one could locate a "spec"/"layout" of what files should have what permissions - it would be helpful. I know that uid/gid doesn't need to be specified generally because each app runs in it's own sandbox and the uid/gid is set to that of the owning pid. But, there must be something somewhere that specifies what the "chmod" permissions are. Isn't there?
If not - then I just have to assume it's a memory corruption and (perhaps) related to the CM11 Nightly that I am using. But, I am a Newbie and I am not permitted to post in that forum (yet).
-----------------------------------------------------------------
Phone: HTC Desire HD
Rom: Daily driver - unofficial CM11 by Mustaavalkosta.
Radio: 12.69a.60.29U_26.17.14.11_M

Sola - keyboard process being killed

I tried to resolve this problem in general help discusion but no luck.
Here's the problem:
I have xperia sola white - really unhappy with very slow laggy stock rom .54, so I flashed ultimate rom v11.
First time I did it, I had no problem but keyboard which is after few minute after restart started to keep disappearing... I found out, that I'm not the only one having this problem, tried to solve with locking it in memory, change OOM after restart to -17,.... nothing so far helped.
Now I tried second shot, fresh ftf stock .54 and everything carefully flash again, guess how it end up. At first I was really happy, because it looked like problem solved, but today I'm chating on fb and that piece of... started to do it again.
Maybe it started to do this problem after I changed QWERTY to QWERTZ and downloaded czech vocabulary. Dunno, today I'm gonna experiment with it.
Maybe the problem isn't in ROM, maybe the problem is keyboard it self. Is there any way (maybe in terminal,...) how to figure out, why the process crashed?
Or please is there anyone who experienced similar problem and solved it? When I was listing xda, I found out, there are many of us dealing with this
Did you try to replace the keyboard to stock?
Actually it¨s what I¨m trying to do right now, but there is another problem (as allways), root explorer won't let me mount as R/W in system folder. Trying to bypass it somehow.... with something ... I let you know, thx for (any) respond
Dutch9177 said:
Actually it¨s what I¨m trying to do right now, but there is another problem (as allways), root explorer won't let me mount as R/W in system folder. Trying to bypass it somehow.... with something ... I let you know, thx for (any) respond
Click to expand...
Click to collapse
Won't let you mount RW why? Does it has root privilages?
I don't know, this phone is killing me :/
Yes, app aks for permission root, I give it access and still it shows that I'm in R/o mode
->
This is interesting, I can't even mount /system/ in cwm, wtf?
edit:
Tried different kernel, now it let me in
Dutch9177 said:
I don't know, this phone is killing me :/
Yes, app aks for permission root, I give it access and still it shows that I'm in R/o mode
->
This is interesting, I can't even mount /system/ in cwm, wtf?
Click to expand...
Click to collapse
Anything else that needs root works?
This custom kernel or stock?
I was using Phantom kernel, different kernel did the work... So now I deleted old kb and replaced it by stock kb from ics and guess what happend . I guess I need JB keyboard. Looking for it right now
So honami kb deleted, installed stock kb and google kb. If the problem was the keyboard, you probably won't hear from me anymore
Thank you for help
note:
please don't lock this topic, I have this feeling that this is not the end
I'm on stock kb and google kb... Problem remains, any idea?
I'll try to dump some log later, maybe someone would be wise from it.

Updating Problem With My Device

Hi everyone I'm having some issues when updating my phone to a new version of android, the phone I have is the Huawei Ascend P2 this morning there was an update available to install to I downloaded it and proceeded to install but during the installation process I got an error and the update was aborted, I tried this several time with the same result I get assert failed: apply_patch_check I know there have been threads about this before and I tried following some of the steps but it never resolved the issue. I have rooted my phone and deleted the browser from my phone using root app delete as it was slow and useless. I saw a guide on there that that required me to download the apk for the app causing the issue and to place it back into the system/app directory I did that but the issue still remains. I also saw another guide that said I have to edit something I tried to follow it but as I'm not so android savvy I didn't understand it and was unable to try it for myself. Any help would be much appreciated from you guys, I know some of you may be annoyed at me by posting a thread about an issue that has been solved before and for that I appologise I have tried some of the suggestions made but still unable to resolve this, any help or assistance would be greatly appreciated.
The error I get is assert failed: apply_patch_check("/system/app/Browser.apk
I have the same problem, an update was released for my phone but it fails the check because of the build.prob. you could try to backup your phone and the do a factory reset on the phone
Factory reset is not going to make the Browser app work.
When you moved it into the /system/app folder, do you remember if you changed the permissions? Since it is a system app, it needs to have different permissions than a regular app from the Play Store. It'd be simple to test - Does the app show up in the app drawer? Can you open it? If not, you either have the wrong version of the Browser.apk or you have not set the permissions to: RW-R-R.
For the build.prop issue - Are you rooted? Have you made any changes to it or installed any apps that would adjust it? This could be for anything from changing the wifi scan interval to memory management apps. If so, then you can grab an unchanged one and copy it to your phone, set permissions, and reboot. Have to make sure it is the right one, or it won't boot at all and you'd need to restore the entire phone. If you have CWM or TWRP then definitely nandroid before attempting anything like that. If you don't understand any of this, then best to get some help and do not attempt yourself.
I havê changed it yes.thats WY i need an unchanged one to compare it.and i AM Also rooted.
Sent from my HUAWEI P2-6011 using XDA Free mobile app
xixorro said:
I havê changed it yes.thats WY i need an unchanged one to compare it.and i AM Also rooted.
Sent from my HUAWEI P2-6011 using XDA Free mobile app
Click to expand...
Click to collapse
How did you change it? Most tools that edit the build.prop also create a backup. You might search for it with a root explorer. Typically, it'd be labeled like:
build.prop.bak
If that's the case, then rename the modded version and remove the .bak off the original, make sure the permissions are set still and reboot. Other than that, you'll just have to hope someone responds to your request in the P2 thread.
Cant i do a full phone repair? My old Sony had that feature from the PC. It completely erased everything and flash a stock ROM
Sent from my HUAWEI P2-6011 using XDA Free mobile app
I think the only way that they released to the public for updates is the update.app way. I'm sure they have a tool @ a service center. Dunno why they wouldn't put it out. But this is why you don't make changes to the system without backing it up. I take it you don't remember what you changed in the build.prop, just to undo it?

Categories

Resources