Database Develop

Permissions /system/csc/

I have downgraded from JPK to JM8. When recovery runs I get an errormessage about "can not access /system/csc", not exact words but I think I've understood it right. I have checked it with ADB and I have permissions set to "drwxr-xr-x root root csc" and in /system/csc I have "-rw-r--r-- root root" on all files. It seems a little strange that my permissions are set to that in the folder. Are those permissions correct?

It's not related to JPK at all. JM8 expects multi-CSC and the XEE CSC is not. There is no problems at all connected to that error, so you can safely ignore it.
If you're like me though, and hate to see it, there's a really easy way to make it go away. Create the following 2 directories (root required):
/system/csc/XEE
/system/csc/XEE/system
Simple as that.

Ok. Will do that. I'm looking for a reason to why I can't flash docs rommod onto my phone. I can't get any further than to the S on black background hearing bootsound but the phone doesn't boot up to a ui. Thought the message could be a clue to that problem

did you do a factory reset in recovery?

When do I have to do that factory reset? I have tried to do it after the slimmod flash. Should I do it before flashing the mod? Now I have oclf installed. Do I have to remove it before trying again?

I have done a clean install of JM8. Installed OCLF, rooted, installed RomManager and clockworkmod recovery. Pushed extreme superslim to internal sdcard. Rebooted into recovery. Did a factory reset and wipe of cache. Installed zip from sdcard. ONLY DIFFERENCE IS THAT MY CLOCK SHOWES TWO HOURS TO EARLY. What am I doing wrong?

Install fresh jm8 push docs update.zip to sdcard and apply it. Then install those rest...
Sent from my GT-I9000 using XDA App

At last! After to more resets and flashes I have Extreme Slim on my device and I really likes it. Big applause to doc. Happy HTC:ing.

mickeko said:
It's not related to JPK at all. JM8 expects multi-CSC and the XEE CSC is not. There is no problems at all connected to that error, so you can safely ignore it.
If you're like me though, and hate to see it, there's a really easy way to make it go away. Create the following 2 directories (root required):
/system/csc/XEE
/system/csc/XEE/system
Simple as that.
Click to expand...
Click to collapse
I noticed with this you had to change the permissions for these foders using a program such as root explorer. Tick all boxes. Well, that's the only way I got rid of the error.
Also case sensative..

/system is usually mounted a read-only, you have to remount it like this from terminal emulator (rooted of course)
$ su
$ mount -o remount,rw /system
then run
$ mount
you should see /system mounted as 'rw'

[Q] Confused w/ busybox

This is the account of my foolishness and I advice everyone not to follow it.:::
1.installed Linux installer std and complete Linux installer from play store.
2.when the 2nd app failed to unmount and GUI crashed showing some errors with busybox, followed 3rd step.
3. found the embedded busybox from 1st app n directly placed it in /system /xbin
4. the original busybox is gone n everything is fine but got too many errors in reading root directory of phone. None of the file manager is showing me root.
5. I'm suspecting that it has done something wrong with my cwm recovery as well for which I can't take a chance of bricking my phone.
6. NOW I need kind advice of u ppl on how to confirm the presence of recovery.img or whatever it should be to recover my cwm backed up data.

boot into recovery, if recovery do not boot then pull battery and start the mobile it will start normally, download busybox installer from play store (the one from stephen)
install busybox through the app(busybox problem will be solved)
download tass recovery cwm.tar file and flash with odin you will get cwm recovery back

did it
I've already tried busybox installers. non of them worked cause the whole root directory is unreadable to any of my apps except diskusage n similar things those show memory occupied.

then you should flash firmware and root again

Superuser
maybe update superuser binary?

solved
chmod 777 path name n got busybox 1.12

You lost root access because there is no busybox. Reflash the ROM. Easy way out.

nothing lost at all just replaced.
as I've stated the command above u, it was just a busybox w/0 permissions. I was getting permission denied.
thanks to Gael péron for his Help.

[Q] -viperboy- HTC One Disable system rw flash fail

Just got HTC One launch day.
Immediately began work on rooting the phone. Installed TWRP and got root access for the most part, but found that this did not give rw access to the system partition.
Found viperboy's post regarding this issue. When I tried to flash the zip file "Sprint_One_Root_Disable_System_RW_Protection.zip" the phone rebooted. After, SuperSU was no longer installed nor was su for root access. TWRP is now no longer able to flash anything at all. The phone still works fine but I seem to be back to ground zero.
Just hoping someone else has encountered this.
- Update -
Upon further exploring I found that all the files were pushed to the android system and that the su file still exists in /system/xbin/, but There is no longer permission to run said command. I tried manually re-pushing all the files but no change.
It seems if anything (even TWRP) tries to access the system partition the phone reboots.

[Q] Help with 498 Error under Ginger Yoshi 1.5

I installed Ginger Yoshi 1.5 on my Android Dev Phone 1 by following these instructions:
http://forum.xda-developers.com/showthread.php?t=1178665
I found that most things are working, but I cannot install CoPilot GPS (28MB)
Error 498 in Google Play seems to mean the /cache partition is too small. My cache partition is 27MB.
I tried redirecting /cache to larger place with Cache Fixer 1.1
The "Data" option doesn't succeed in expanding the cache.
The "Tmpfs" option successfully makes the cache bigger, but it makes Play force close when I try to install the app.
I Tried using CacheDownload2SD 1.7.1, but it doesn't do anything
I got a message saying my su binary should be updated. I don't know if that is related or not.
I tried updating the SuperUser su binary from 2.3.2-efgh to 3.1.1
su Binary Updater says "Make sure new su works... fail!"
When I try again, su Binary Updater says "Copying su to /system... fail!"
When I try yet again, su Binary Updater again says "Copying su to /system... fail!"
I used Root Checker to verify root access. The phone is properly rooted. I don't know if this issue is related
I've considered downloading an apk and manually installing it. That should work, but then Google Play wouldn't let me know when an update became available. Any ideas on how to solve the problem? Does anyone know why Cache Fixer and CacheDownload2SD dont' work? Can anyone see why the su binary won't update? I've spent all day clearing caches, rebooting, and attempting installs. Why does Google Play need to download to such a tiny partition?

@IMSargon if your /cache partition is too small then you need to use custom MTD.

HTCDreamOn said:
@IMSargon if your /cache partition is too small then you need to use custom MTD.
Click to expand...
Click to collapse
Thanks for that. I certainly have some more reading before I fully understand the topic. When I upgraded to Ginger Yoshi 1.5, I changed from DangerSPL to hboot-1.33.0013d which gives practically the same partition sizes, except /cache is 27MB instead of 30MB, which is why I didn't have this problem before.
So you're saying I can flash to this custom bootloader to increase my cache size (decreasing /system and/or /data accordingly), install the GPS app, then flash back for normal operation? It sounds like a risky proposition. Is there no way to permanently or temporarily redirect the location to which Play downloads APKs? Such solutions appear to exist (Cache Fixer, etc), but they don't seem to work for me (why?).

No, if you change partition sizes you will be wiping those partitions. Maybe a better option is to do it just once but bind mount to sdcard, see the link htcdreamon gave for more info on this
Sent from my Nexus 4 using xda premium

demkantor said:
No, if you change partition sizes you will be wiping those partitions.
Click to expand...
Click to collapse
This is a relief to hear. It sounded like they would just redefine the partition boundaries with the data in place and hope for the best. I was wondering how that worked. After re-reading, the instruction do call for wiping the partitions and re-flashing the ROM.
demkantor said:
Maybe a better option is to do it just once but bind mount to sdcard, see the link htcdreamon gave for more info on this
Click to expand...
Click to collapse
That would work, and it's something I'll seriously consider once I have a chance to read all the documentation. It seems to me, though, that I should be able to unmount and remount elsewhere the /cache partition on a live system from the command line. Any reason I should not attempt that?

If you want to resolve your problem then follow these steps
- Clean your Device Cache
- Erase Market Data
- Scan your Device for Viruses
- Restore Smartphone to Factory Settings
I also have tutorial like article where you will find all the solution steps to fix the error here is the link:
optimum-systems.com/2013/04/error-498-in-android.html
I hope you will resolve your problem

I tried making a folder under /sdcard, removing /cache, and replacing it with a symlink to the folder in /sdcard. That didn't work for a number of reasons. Firstly, mkdir was missing, which was a pain. I just made the directories with File Manager on the phone - I'll fix that later. Then it wouldn't let me change the ownership of the target directory on the sdcard, even though I was root. When I tried downloading my app, Play force closed.
My next idea was to put the folder in /sd-ext, which is my next largest partition. This is an ext4 partition on the sdcard. I created a folder there. Then I deleted /cache/download and created a symlink to my folder in /sd-ext. I didn't have any problems changing permissions this time. For whatever reason, Play did not force close, and successfully installed the app.
I'll write what I did here, but I'll pretend mkdir worked.
Code:
rm /cache/download
mkdir /sd-ext/download
chown system:cache download
ln -s /sd-ext/download /cache/download
chown -h system:cache /cache/download
I'd expect this setup to survive a reboot, so maybe you want to delete the symlink and remake the original folder to set things back to normal. If not, only apps that use /cache/download are effected, so you might as well leave it. Just clean that folder out every so often.

Bricked Note5. In TWRP Recovery 3.0. Need to delete folder in /system/app. Error:1

[SOLVED] - Apparently, I lost the ability to *read* also. When I went into TWRP, I must have clicked the "keep the system read-only" button. That would prevent me from deleting files/folders. I hereby select one card from the Smacktard pile.
Evening all,
Sprint Note 5, Rooted.
Tried to manually make an application a "System App". This is what happens when you give a monkey the *tools* but not the *brains*. I'm plenty technical, but I've not done this before.
I installed an app, then went into the data\apps directory and copied the entire application's folder into \system\app.
When I rebooted, the phone gets stuck on the Sprint LTE screen.
When I boot into TWRP, and into Advanced / File Manager, then go into the offending directory, I get the following:
File Operation Complete
Failed
rm -rf "/system/app/com.incorporateapps.fakegps.fre-1" processes ended with ERROR: 1​I get similar messages when I chmod, delete, move, or rename.
Any assistance you could provide would be MUCH appreciated. I'm bricked and cannot work until I get my phone back.
Thanks!
Pete

have you tried to flash stock rom or another rom ?