Hi guys,
unfortunately I cannot post in developers forum, because I am a new member. Therefore I have to ask here:
I am running ICSunday Final Rom with LafreeV2 script.
After installing the permissions of the script are automatically set on rw-r-r. But in another forum I read, that the script has to be executed for working - i.E. the permissions have to be changed to rwxr-x.
That sounded rational for me, so I changed the permissions like that - but after rebooting I got stuck on Android-Screen! (in the end I restored a Nandroid backup...)
Can anyone tell me, how the permissions are set right and why my phone did not boot again after changing them?
Thanks in advance and greetz,
Sarah
Related
I asked this in the general Q&A thread because I feel it is an android issue, not a Note issue...but alas no one even replied, trying it out here. Please help!
RockZors said:
Hello all,
I have a Samsung Galaxy Note i717. I have installed a few ROM's, but recently I installed CM9 unofficial build. After it was installed, I noticed that my default.prop is only like 4 lines long. So I try and add stuff to it (I am rooted, and used RW mode in Root Explorer). I can close the file and save changes successfully, but when I reboot it is back to the way it was with the 4 lines. It is not only that though, any files i add to the "/" get deleted upon reboot.
Things I have tried:
ODIN to stock rom, still did not have a full default.prop
Tried many different ways to change file system (different programs)
Ran fix permissions in CWM and busybox installer script
All with no success. Is there anything else I can try to fix this and be able to edit my "/" and have changes take affect. Or has anyone had this issue before?
Thanks
Click to expand...
Click to collapse
I was wondering if anyone with an i717 could go into cwm, run a backup, and upload that somewhere so I can restore it. Keep in mind your personal data gets backed up also, so preferably someone with a fresh working install. I don't care what rom it is either.
Thanks for reading.
The default.prop should only be 4 lines..
Are you confusing it with the build.prop?
Wow well don't I feel stupid. That's exactly what it was. Thanks for helping me see the way!
Hi guys, before I start I'll say that I have searched all over the internet and here on the forums and I couldn't find my particular issue. Well the thing is that I edited the line in my build.prop "ro.build.version.codename=REL" to "ro.build.version.codename=L" so I could get the material design on the Google Now Launcher pulled from a Android L build here's the thread I got that app: http://forum.xda-developers.com/android/apps-games/app-android-lollipop-apps-launcher-apps-t2912905
I did that and now my device will boot up normally then I will reboot by itself then show the boot animation then repeat the same process again and again until I force the phone to recovery or fastboot.
By the way my device is the LG Optimus G (E970) running GEE 3 ROM 1.2 and TRWP 2.6.3.0 and I have a backup of the original build.prop on my PC. I don't want to lose my data and apps since I forgot to make a backup (silly me).
I would like to know if there is a way to push the build.prop file on my PC to my phone so I could just replace it, or create a flashable zip.
Please help me, and thanks in advance.
Nevermind. I managed to push the original build.prop file to /system set the correct permissions and now my phone is working again.
Admin feel free to delete or close this thread.
question
AntonyOrtega said:
Nevermind. I managed to push the original build.prop file to /system set the correct permissions and now my phone is working again.
Admin feel free to delete or close this thread.
Click to expand...
Click to collapse
how were you able to do it when you couldnt get past booting.
I'm working on a custom ROM, and I've been having very little trouble - very few problems are occurring, and I've written a number of scripts to automate everything for me. It's a stock-based ROM based on Samsung's KitKat 4.4.2 firmware.
The problem I'm having, is I don't know what permissions are vital. I could copy all of the permissions, and then strip out the ones I don't need after I've removed or changed files, and I could automate that, but that makes my updater-script roughly 3000 lines long - taking up unnecessary space.
I've looked at other ROMs, but what I want to know is whether there is any point having permissions set for everything. Obviously there needs to be permissions on some areas, but do all areas need permissions set?
How can I figure out what permissions I actually require? Or should I think about checking if everything in a folder has the same permissions, and then make that folder one recursive one (and keep working backwards from there until almost all permissions are conglomerated in recursive permission sets)?
Thank you very much and I hope you can help me.
furzewolf said:
I'm working on a custom ROM, and I've been having very little trouble - very few problems are occurring, and I've written a number of scripts to automate everything for me. It's a stock-based ROM based on Samsung's KitKat 4.4.2 firmware.
The problem I'm having, is I don't know what permissions are vital. I could copy all of the permissions, and then strip out the ones I don't need after I've removed or changed files, and I could automate that, but that makes my updater-script roughly 3000 lines long - taking up unnecessary space.
I've looked at other ROMs, but what I want to know is whether there is any point having permissions set for everything. Obviously there needs to be permissions on some areas, but do all areas need permissions set?
How can I figure out what permissions I actually require? Or should I think about checking if everything in a folder has the same permissions, and then make that folder one recursive one (and keep working backwards from there until almost all permissions are conglomerated in recursive permission sets)?
Thank you very much and I hope you can help me.
Click to expand...
Click to collapse
Take a look at the stock permissions and how they are set. In most updater scripts I've seen, unless there's a specific reason, individual permissions are not set, they are handled recursively through the partition or folder. I am fairly certain that all areas must have permissions set, if they weren't then the system wouldn't know what to do with the files (I have never tried to flash files with permissions not set, so I don't know if the system defaults to a permission set or not). The vast majority of files in your ROM will be rw-r--r-- (0644), so verify the permissions you need from the stock ROM and you should be ok.
Edit - Also, this is a good source of information when it comes to updater scripts.
Stryke_the_Orc said:
Take a look at the stock permissions and how they are set. In most updater scripts I've seen, unless there's a specific reason, individual permissions are not set, they are handled recursively through the partition or folder. I am fairly certain that all areas must have permissions set, if they weren't then the system wouldn't know what to do with the files (I have never tried to flash files with permissions not set, so I don't know if the system defaults to a permission set or not). The vast majority of files in your ROM will be rw-r--r-- (0644), so verify the permissions you need from the stock ROM and you should be ok.
Edit - Also, this is a good source of information when it comes to updater scripts.
Click to expand...
Click to collapse
I ended up realising that trying to recursively generate the permission script is a bit on the... scary side. So I just looked through all the permissions (thrice, to ensure correctness) and I've made a base file of permissions and a base file of symlinks for the stock ROM in question.
jeremywh7 has explained how to fix the issue with the ICSROM governor so that it runs with min 216Mhz and causes less heating - http://forum.xda-developers.com/showpost.php?p=58093061&postcount=1051
Here's the entire post -
Quote:
Originally Posted by jeremywh7
I just wanted to mention that I think I found the cause of ICSROM with the latest 3.1.10 kernel not running at 216MHz:
http://forum.xda-developers.com/show...postcount=1018
I have rebooted*, and its still working fine.
[*edit: forgot to update this post...a power off and cold boot does reset it. I've made an init.d script to fix it for now; will provide details later, as its now the wife's main phone.]
[...]
Better late than never, right? :-/ Here is the script I made as '/etc/init.d/01cpufreq' and set to chmod 755 (manually, using ES File Explorer, actually):
Code:
#!/system/bin/sh
#ramdisk cpu scaling min fix
chown root.root /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "216000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
I installed Universal Init.d (by Androguide.fr) to apply it at boot. I had to run the Test part w/ the tool set to Off, to enable SuperUser privileges. [Update: if you click a file to edit, it will also prompt for su, so that would be easier than running the test; K's July kernels don't support init.d obviously; I'm using kernel-2014_07_04_19_18_atrics.] After setting the tool On, and rebooting...voila, file permission fixed and min frequency 216 MHz.
Since I converted my old CM9-based Atrix to ICSROM (the reason I'm working on all this again), I recalled another mod, rain drop detect issue, for future reference:
http://forum.xda-developers.com/show...&postcount=117
Make sure to leave the extra character at the end the config line [ref: post 119].
Hope this helps...
Click to expand...
Click to collapse
Needless to say, I don't understand the instructions and I really want to be able to do this fix, so if anyone can help me, please let me know. How can I run this script?
aamil4u said:
jeremywh7 has explained how to fix the issue with the ICSROM governor so that it runs with min 216Mhz and causes less heating - http://forum.xda-developers.com/showpost.php?p=58093061&postcount=1051
Here's the entire post -
Needless to say, I don't understand the instructions and I really want to be able to do this fix, so if anyone can help me, please let me know. How can I run this script?
Click to expand...
Click to collapse
This is more like a how to use ES Explorer or Root Browser to put a script in a location and set permissions question and not what you asked
palmbeach05 said:
This is more like a how to use ES Explorer or Root Browser to put a script in a location and set permissions question and not what you asked
Click to expand...
Click to collapse
Thanks for the quick reply!
So basically I have to save this in a file and set permissions for it on a root explorer? I'm a bit of a noon in this, so I'd really appreciate if you could please explain this procedure in a noob-friendly way. What exactly should I do and what should the permissions be.
Thanks!
aamil4u said:
Thanks for the quick reply!
So basically I have to save this in a file and set permissions for it on a root explorer? I'm a bit of a noon in this, so I'd really appreciate if you could please explain this procedure in a noob-friendly way. What exactly should I do and what should the permissions be.
Thanks!
Click to expand...
Click to collapse
Actually you hit the nail on the head after i pointed out what i did in my last post. For permissions, i find it easier to manually change them instead of the chmod thing that it was talking about. For permissions, 755 the same as*rwxr-xr-x
Sent from my ATRIX HD using XDA Free mobile app
Okay. I got so far as that. But what should I name the file and what extension should I use? Am I supposed to replace a system file? Or is this a separate file I have to create? I'm not clear what he means by universal init.d, is it a file? What should I do with it?
Dude, you're seriously overcomplicating this. You're making it way more difficult than it needs to be, both for yourself and for XDA.
The post you quoted contains literally all the information you need, including all the questions you've asked in here. Just read it again.
I treid to edit this file to get better video/photo/audio quality a while back but when I did edit it and rebooted I was stuck in a boot loop.
I want to give it a go again but do not want to end up in a boot loop again if I can help it.
Is there settings I should not edit or permissions I need to set etc to stop a boot loop? What causes the bootloop in the first place? I would of thought that editing this file would stop the camera from working and not the whole phone but hey what do i know
Can anyone provide some insight?
Cheers
most likely permission error
permission should be rw-r-r (read,write for root, read for group, read for global) or 644 depending on what you are used to
anyway, before you make changes, backup system in TWRP then do your stuff
in case something went wrong, simply restore system and no probs