I can't seem to edit any files in /system (the one I particularly want to edit is in the UI sound). Is anyone able to help me out?
I'm running Chroma (July 7th update) with Elite Kernel.
RedInuYasha said:
I can't seem to edit any files in /system (the one I particularly want to edit is in the UI sound). Is anyone able to help me out?
I'm running Chroma (July 7th update) with Elite Kernel.
Click to expand...
Click to collapse
Which app are you using to modify /system?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Which app are you using to modify /system?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I was using Solid Explorer. I tried everything I could find online and none of it worked. So I just un-rooted and basically went back to stock. Then re-rooted my phone and now it seems to work just fine.
RedInuYasha said:
I was using Solid Explorer. I tried everything I could find online and none of it worked. So I just un-rooted and basically went back to stock. Then re-rooted my phone and now it seems to work just fine.
Click to expand...
Click to collapse
Cool, whatever works!
Sent from my Nexus 5X using Tapatalk
Related
Is there a way to consolidate/merge the important files in these neverending iterations of files?
Why does the file system work like this?
Is there a way to prep before flashing a new rom to make it not happen, because I am a serial flasher. :laugh:
Thanks in advance.
Looks like somebody neglected to update their recovery to a version that's compatible with 4.2 before flashing roms a few times.
Update your recovery to the latest version and then copy everything from the last nested 0 folder to data/media/0, and then delete the nested 0 folders contained therein.
Sent from my Nexus 7 using Tapatalk HD
Now go to bed without dinner!
Sent from my Nexus 7 using xda premium
annoyingduck said:
Now go to bed without dinner!
Click to expand...
Click to collapse
...yes and think about what you've done! Loool.
Sent from my Nexus 7 using XDA Premium HD app
najaboy said:
Looks like somebody neglected to update their recovery to a version that's compatible with 4.2 before flashing roms a few times.
Update your recovery to the latest version and then copy everything from the last nested 0 folder to data/media/0, and then delete the nested 0 folders contained therein.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Naaahhhh, neglecting would indicate I knew and chose to procrastinate or something
Thanks, I had read the cause was 4.2, but not that updating recovery fixed the issue. Works like a charm now.
Anyone managed this successfully? I changed the build.prop to 160dpi, how tablet then refuses to boot. Reflashed 4.2.2, miss my lower dpi!
On stock rom by the way.
Sent from my Nexus 7 using XDA Premium HD app
Have you tried using a utility like this to make the changes?
rifraf1 said:
Have you tried using a utility like this to make the changes?
Click to expand...
Click to collapse
Yeah, tried root toolbox pro and build.prop editor, they dont seem to gain access to the file to change it. Have you had any luck with it?
Give it a try..
https://play.google.com/store/apps/...251bGwsMSwxLDEwOSwibHYubjNvLmxjZGRlbnNpdHkiXQ
Don't forget to love the thanks button if I help you.
Hasn't worked since 4.0, used to use it on my s2!
Sent from my Nexus 7 using XDA Premium HD app
OK, in case anyone else runs into this, remember to change the permissions back to 644 after you have made your changes!
Sent from my Nexus 7 using XDA Premium HD app
herghost said:
Anyone managed this successfully? I changed the build.prop to 160dpi, how tablet then refuses to boot. Reflashed 4.2.2, miss my lower dpi!
Click to expand...
Click to collapse
I managed to change my dpi to 160 with no issues. I actually prefer it on 177.
Sent from my HTC Sensation 4G using xda app-developers app
Hello There
I am really sorry if this has been answered before.
I used to have CM10 on my nexus but i went back to stock because I did not like how many of the apps because "incompatible" or saying my device was not qualified to run this app but it was when it was stock Nexus 4.
Anyways, do I just copy the build prop from a stock rom and use it with CM10 or is there just a few lines to modify in the build prop when CM10 is flashed. Any info was definitely be appreciated. THANKS!
You shouldn't have to modify the build prop on the cm rom you flash cause it comes with it already setup. What are you trying to modify?
Sent from my Nexus 4 using Xparent Cyan Tapatalk 2
eqjunkie829 said:
You shouldn't have to modify the build prop on the cm rom you flash cause it comes with it already setup. What are you trying to modify?
Sent from my Nexus 4 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Sorry, just as an example, I can use Hulu Plus with the stock rom, but when I use CM10 its not "compatible" and will not play.
raysurrx7 said:
Sorry, just as an example, I can use Hulu Plus with the stock rom, but when I use CM10 its not "compatible" and will not play.
Click to expand...
Click to collapse
Thats because root is detected. No build.prop edits will fix that.
mbh87 said:
Thats because root is detected. No build.prop edits will fix that.
Click to expand...
Click to collapse
Not the issue because I am currently rooted with stock rom and I can still watch hulu plus.
raysurrx7 said:
Hello There
I am really sorry if this has been answered before.
I used to have CM10 on my nexus but i went back to stock because I did not like how many of the apps because "incompatible" or saying my device was not qualified to run this app but it was when it was stock Nexus 4.
Anyways, do I just copy the build prop from a stock rom and use it with CM10 or is there just a few lines to modify in the build prop when CM10 is flashed. Any info was definitely be appreciated. THANKS!
Click to expand...
Click to collapse
Did you happen to change the DPI from 320?
Sent from my Nexus 4 using xda premium
nbeebe24 said:
Did you happen to change the DPI from 320?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I didnt make any changes to the DPI.
Just wanted to get the word out to everybody that cyanogen is now building official nightly builds for our device. Just head over to get.cm and grab one of the builds for our device, flo.
Sent from my Nexus 7 using xda premium
I'll probably be installing this as soon as my tablet gets in, seeing how well my phone (d2can; running d2att) has been taking CM10.2. I'll let everyone know how it goes.
Sweet. Thanks for letting us know. I'm flashing it right now =)
Is a full wipe required, coming from 10.1?
Just installed and it appears that the ROM doesn't think I've got root access, I can't even do anything that requires root. When I go and restore my backup of cleanrom 1.3 I've got root access again
Sent from my Nexus 7 using xda app-developers app
Wubbz said:
Just installed and it appears that the ROM doesn't think I've got root access, I can't even do anything that requires root. When I go and restore my backup of cleanrom 1.3 I've got root access again
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
go to developers option and enable root for adb and apps
Wubbz said:
Just installed and it appears that the ROM doesn't think I've got root access, I can't even do anything that requires root. When I go and restore my backup of cleanrom 1.3 I've got root access again
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Developer Options > Root Access > Apps and ADB
Is anyone else having trouble restoring with Titanium Backup? I can't for the life of me get backups from non-CM to restore when I flash CM.
No official thread in the Original Development forum?
Sent from my One X
Artood2s said:
No official thread in the Original Development forum?
Sent from my One X
Click to expand...
Click to collapse
yeah, wut?
Artood2s said:
No official thread in the Original Development forum?
Sent from my One X
Click to expand...
Click to collapse
bobloadmire said:
yeah, wut?
Click to expand...
Click to collapse
I believe its because an official maintainer hasn't been selected yet, or at least they haven't announced one yet.
Sent from my Nexus 7 using xda premium
jeremysv said:
Is a full wipe required, coming from 10.1?
Click to expand...
Click to collapse
Wait what?
Sent from my Nexus 4 using xda app-developers app
It is great ROM let my new Nexus 7 get much higher score than stock from either Antutu or Quadrant.
Sent from my TapaTalk 2 on Nexus 7 (2013)
taitony said:
It is great ROM let my new Nexus 7 get much higher score than stock from either Antutu or Quadrant.
Sent from my TapaTalk 2 on Nexus 7 (2013)
Click to expand...
Click to collapse
I got 5500stock. Much better. Don't know why.
Sent from my Nexus 7 using Tapatalk 4
Knolly said:
Is anyone else having trouble restoring with Titanium Backup? I can't for the life of me get backups from non-CM to restore when I flash CM.
Click to expand...
Click to collapse
What problems are you having restoring?
Knolly said:
Is anyone else having trouble restoring with Titanium Backup? I can't for the life of me get backups from non-CM to restore when I flash CM.
Click to expand...
Click to collapse
You have to move your tiBU folder onto legacy/ from 0/
Look at my screenshot. Go to Preferences and set your backup folder to this location... Minus the /!Ready2Flash/TitaniumBackup part. That's my personal folder location.
jeremysv said:
Is a full wipe required, coming from 10.1?
Click to expand...
Click to collapse
Wrong section. Think you took a wrong turn at Mako and went past Grouper, straight to Flo.
mjwhirly said:
Just wanted to get the word out to everybody that cyanogen is now building official nightly builds for our device. Just head over to get.cm and grab one of the builds for our device, flo.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Just askin... Is there a simbug in this 4.3 builds?
And is it quit stable or do i need to wait a bit longer because of multiple bugs?
Error Report:
Stock work well with NetGear PTV3000 for WiFi Display via Miracast. This CM 10.2 connected but TV screen keep on black.
freeza said:
What problems are you having restoring?
Click to expand...
Click to collapse
It is perpetually stuck at 0% and I've tried fudging with a number of settings.
Covart said:
You have to move your tiBU folder onto legacy/ from 0/
Look at my screenshot. Go to Preferences and set your backup folder to this location... Minus the /!Ready2Flash/TitaniumBackup part. That's my personal folder location.
Click to expand...
Click to collapse
...haven't tried fudging with that setting. Very strange, many thanks for this! I'll try it out as soon as I get home.
Hey all--just wondering why I can't seem to delete the com.teamkang.fauxclock folder from mnt/shell/emulated directory.
I've moved on to a new ROM & I'm trying out a new kernel; no longer have fauxclock app installed. Don't see why I can't remove it now. Any help?
Sent from my Nexus 4 using Tapatalk 4
sspyed said:
Hey all--just wondering why I can't seem to delete the com.teamkang.fauxclock folder from mnt/shell/emulated directory.
I've moved on to a new ROM & I'm trying out a new kernel; no longer have fauxclock app installed. Don't see why I can't remove it now. Any help?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
you have to delete it in the twrp recovery
[email protected] said:
you have to delete it in the twrp recovery
Click to expand...
Click to collapse
Really??? geez, why is that???
hotnikkelz said:
Really??? geez, why is that???
Click to expand...
Click to collapse
Haha--my thoughts exactly. I've always used CWM since Gingerbread, so I'm wondering if there's any other way?
Okay so I got over myself and flashed TWRP. Now I'm looking at the file manager and I can't find the mnt directory anywhere, so I still can't get rid of the fauxclock folder from mnt/shell/emulated.
Any help?
Sent from my Nexus 4 using Tapatalk 4