Hi everyone,
recently I decided to increase the strength of notification LED, by editing
Code:
/system/sys/class/leds/amber/pwm_coefficient
and
Code:
/system/sys/class/leds/green/pwm_coefficient
values from 5 to 250.
The problem is, whenever I edit those files and save changes upon exiting text editor - changes are not being saved, and I see that only when I open the file again and see the starting value of 5.
I am on Lolipop 5.0.1 GPe, rooted, busybox and I was mounting /system, rw thru Terminal Emulator, 3rd party apps and fx Explorer's built-in solution.
Any help would be much appreciated.
voolandis said:
Hi everyone,
recently I decided to increase the strength of notification LED, by editing
Code:
/system/sys/class/leds/amber/pwm_coefficient
and
Code:
/system/sys/class/leds/green/pwm_coefficient
values from 5 to 250.
The problem is, whenever I edit those files and save changes upon exiting text editor - changes are not being saved, and I see that only when I open the file again and see the starting value of 5.
I am on Lolipop 5.0.1 GPe, rooted, busybox and I was mounting /system, rw thru Terminal Emulator, 3rd party apps and fx Explorer's built-in solution.
Any help would be much appreciated.
Click to expand...
Click to collapse
/system in write protected by the kernel so you must use a custom kernel with /system write permission (unsecured kernel) or push your modified files from a custom recovery.
Btw modifying /system files will probably prevent you to install future ota updates.
@alray
It there any workarount for upcoming OTAs, I don't think update procedure going to change that much to prevent us from cracking-up them files?
Also, any recomandation for kernel in this case?
voolandis said:
@alray
It there any workarount for upcoming OTAs,
Click to expand...
Click to collapse
Going back to 100% stock rom (/system)
Also, any recomandation for kernel in this case?
Click to expand...
Click to collapse
Every kernel that have /system write protection disabled
ElementalX will do the job
Related
adb shell, sqllite, build prop...Any other non-tech major people around here a little lost?
I'm rooted. I don't want the new update. I can follow directions but would be more comfortable if some basic instruction were written. Treat me like I'm 10.
It looks like the best way to do this is as follows:
"From this thread:
http://forum.xda-developers.com/showthread.php?t=874871
Attached is a working sqlite3 binary.
Copy it to /system/bin
(I transfered it to my SD, then used rootexplorer (mount R/W) to copy into /system/bin))
you will now be able to edit sqlite databases on the nook itself.
--------------------------------------------------------------------------------
Attached Files sqlite3.7z (11.9 KB, 56 views)
--------------------------------------------------------------------------------
In your terminal:
$ adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
$ sqlite3 devicemanager.db
sqlite> update registry set value='manual' where name='com.bn.device.fota.mode';
sqlite> .q
$ adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
$ adb reboot
"
Do I unzip the attached binary and paste that into the location or the .zip as a whole? What do I use as a terminal?
I've been flashing my DROID since day one but the NC development circle has been far from entry level user-friendly. Any help would be appreciated.
you can do it on windows too.
1) pull/get/copy the.db file from your phone to your pc
2) update the database file using sqlitebrowser. I.e run the sql command "update ......". Close sqlitebrowser.
3)push/put/copy the updated .db file to the same location overwriting the original.
britoso said:
you can do it on windows too.
1) pull/get/copy the.db file from your phone to your pc
2) update the database file using sqlitebrowser. I.e run the sql command "update ......". Close sqlitebrowser.
3)push/put/copy the updated .db file to the same location overwriting the original.
Click to expand...
Click to collapse
Progress. However...
I got SQLite on my PC. I found the devicemanager file on my NC, pasted it to my SD card for transfer over to my PC for editing. I trasnferred the file over to my PC for editing. I open SQLite but have no idea how to use it.
I just did this today using sqlite editor only!!! Its a GUI so it real simple to use.
1.Install the apk
2.reboot
3.go to extras and launch sqlite editor
4.allow it, give it the permision it needs
5.look for DeviceManagerService
6.click on devicemanager.db
7.click on registry
8.look for _id 7, name>>>> "com.bn.device.fota.mode"
9.scroll to the right and click and hold value field "auto", until a little pop up shows and select edit field
10. Change the value from auto to manual
11. Save
Done!!!
If you need the apk here is a link I just made
?d=LTSQDZ65 for megaupload (sure u guys can piece it together!)
Let me know if it helped anyone!
Yes, we totally need another thread on this. I must note that pushing the build.prop in my thread and my two Nook Colors have not updated. Dunno about this method or others. Caveat emptor!
This is exactly what I was looking for. Thank you. Very simple.
Sent from my NC using XDA App
Thanks for breaking it down for us, nookme.
Do we need to do this if we are operating from an SD bootable Froyo or CM7 ROM?
tablo said:
Thanks for breaking it down for us, nookme.
Do we need to do this if we are operating from an SD bootable Froyo or CM7 ROM?
Click to expand...
Click to collapse
In theory it should work for both, whether its a soft root mod or simply a bootable sd card that emulates froyo... It's a matter of just having root access and changing a registry setting on the device itself. Hope this shines some light! happy rooting ppl
Not noobie enough for me, sigh
So, if I have followed these directions from an earlier post have I messed something up? Not blocked updates at all? I don't understand the directions in this thread. What happens if I don't block the update? There must be a lot of people like me who had the technical skills to manage the root process but don't understand all of your coded instructions. I read in another thread that I should do a Titanium backup. How does that help after an update? Will market aps that have already been downloaded still work? Will everything revert to stock? Could someone explain what we should expect? Thanks!
To disable OTA (over the air) updates:
Change the name of this file: otacerts.zip to anything else
To do this, get root explorer ($3) from the market
Run root explorer
Go to etc/security/otacerts.zip
Hit the little mount button near the top to change r/w to r/o
Rename the file otacerts.zip to otacerts.zip_DISABLED_OTA_UPDATES
Hit the little mount button again to change r/o back to r/w
Droiddict said:
So, if I have followed these directions from an earlier post have I messed something up? Not blocked updates at all? I don't understand the directions in this thread. What happens if I don't block the update? There must be a lot of people like me who had the technical skills to manage the root process but don't understand all of your coded instructions. I read in another thread that I should do a Titanium backup. How does that help after an update? Will market aps that have already been downloaded still work? Will everything revert to stock? Could someone explain what we should expect? Thanks!
To disable OTA (over the air) updates:
Change the name of this file: otacerts.zip to anything else
To do this, get root explorer ($3) from the market
Run root explorer
Go to etc/security/otacerts.zip
Hit the little mount button near the top to change r/w to r/o
Rename the file otacerts.zip to otacerts.zip_DISABLED_OTA_UPDATES
Hit the little mount button again to change r/o back to r/w
Click to expand...
Click to collapse
If you read this >> http://forum.xda-developers.com/showthread.php?t=1007551
you will see that the sqlite method is used by many and is the simplest way too, again this is a GUI, so no shell command line... How can this be difficult??
Just follow my steps... it works
I have had nothing but problems with my rooted NOOK Color due to B&N auto updates. I followed your instructions and now I hope my problems are resolved and my NOOK Color will never update again.
Thank you
Hi,
I hope this is the write location for my post.
I have a HTC ONE rooted, android 4.3
I have a problem with my GPS: it doesn't lock any satellite. Reading on forum, I found that the problem may be the setting of gps.conf file in /system/etc.
In fact, checking it, I found that the NTP_SERVER set was for north.america, while I'm in Europe.
I would like to modify or replace it, but I'm experiencing some problem. Using Root Browser it seems to be able to modify it, but after rebooting the device it is exactly the same before the editing. I tried using other editors as ES File Explorer, but when I try to modify the file, it says "read only file system".
It makes me thing that also the other editor is not able to modify the file, since after reboot it is actually un-edited.
What do you think? how can I actually write in file system and actually modify gps.conf?
Thank you in advance
Let me add another detail: I tried to create a new empty file in the same folder with Root Browser. It seems to be able to create it, but after rebooting the device it desappears..so I guess I actually can't modify/write in the file system..
aerosmike said:
Hi,
I hope this is the write location for my post.
I have a HTC ONE rooted, android 4.3
I have a problem with my GPS: it doesn't lock any satellite. Reading on forum, I found that the problem may be the setting of gps.conf file in /system/etc.
In fact, checking it, I found that the NTP_SERVER set was for north.america, while I'm in Europe.
I would like to modify or replace it, but I'm experiencing some problem. Using Root Browser it seems to be able to modify it, but after rebooting the device it is exactly the same before the editing. I tried using other editors as ES File Explorer, but when I try to modify the file, it says "read only file system".
It makes me thing that also the other editor is not able to modify the file, since after reboot it is actually un-edited.
What do you think? how can I actually write in file system and actually modify gps.conf?
Thank you in advance
Let me add another detail: I tried to create a new empty file in the same folder with Root Browser. It seems to be able to create it, but after rebooting the device it desappears..so I guess I actually can't modify/write in the file system..
Click to expand...
Click to collapse
You need an unsecured kernel (/system writable) to write to /system partition of the htc one, not only root.. Otherwise, all changes will be reverted at reboot like you are experiencing.
Kernels for htc one here
And note that modifying/deleting files in /system will probably prevent you to install future ota unless you revert the change you have made. There is a md5 checksum of many files in /system before the ota installs. If the md5 cheksum doesn't match then the ota will not install. This might not apply to the .conf file you want to edit but just in case, make a backup of that file before. So if the next ota fail, you'll know why.
alray said:
You need an unsecured kernel (/system writable) to write to /system partition of the htc one, not only root.. Otherwise, all changes will be reverted at reboot like you are experiencing.
Kernels for htc one here
And note that modifying/deleting files in /system will probably prevent you to install future ota unless you revert the change you have made. There is a md5 checksum of many files in /system before the ota installs. If the md5 cheksum doesn't match then the ota will not install. This might not apply to the .conf file you want to edit but just in case, make a backup of that file before. So if the next ota fail, you'll know why.
Click to expand...
Click to collapse
Thank you very much
Apologies if this has already been covered but a quick search turned up nothing. I recently rooted and was wondering if there was any resource to describe the ins and outs of the chromecast shell. Specifically I wanted to know if there is a way to define a custom start up script. For the moment I would just like to auto update the PATH env variable to include my own bin directory on /data with some of the more useful busybox commands symlinked and maybe add some cooler stuff later. I've done something similar in dd-wrt with a special nvram variable to point to a script, but I don't know if there is an equivalent here. Thanks.
bobcat987 said:
Apologies if this has already been covered but a quick search turned up nothing. I recently rooted and was wondering if there was any resource to describe the ins and outs of the chromecast shell. Specifically I wanted to know if there is a way to define a custom start up script. For the moment I would just like to auto update the PATH env variable to include my own bin directory on /data with some of the more useful busybox commands symlinked and maybe add some cooler stuff later. I've done something similar in dd-wrt with a special nvram variable to point to a script, but I don't know if there is an equivalent here. Thanks.
Click to expand...
Click to collapse
I think we need to edit /init.rc
but it's write protected =/
bobcat987 said:
Apologies if this has already been covered but a quick search turned up nothing. I recently rooted and was wondering if there was any resource to describe the ins and outs of the chromecast shell. Specifically I wanted to know if there is a way to define a custom start up script. For the moment I would just like to auto update the PATH env variable to include my own bin directory on /data with some of the more useful busybox commands symlinked and maybe add some cooler stuff later. I've done something similar in dd-wrt with a special nvram variable to point to a script, but I don't know if there is an equivalent here. Thanks.
Click to expand...
Click to collapse
Mape0661 said:
I think we need to edit /init.rc
but it's write protected =/
Click to expand...
Click to collapse
You can, but you would have to do the modifications with an extracted system image, re-squashfs it back up, and then flash it back to the device.
Thanks for the replies. If I'm feeling bold this weekend I'll take a look at creating a one-off /system for this.
bobcat987 said:
Thanks for the replies. If I'm feeling bold this weekend I'll take a look at creating a one-off /system for this.
Click to expand...
Click to collapse
I've been writing some, gonna post it later on git if you want to see it.
mostly stuff to make it easy to start ftp, samba etc.
/mape
ddggttff3 said:
You can, but you would have to do the modifications with an extracted system image, re-squashfs it back up, and then flash it back to the device.
Click to expand...
Click to collapse
Seeing this you guys are making me think (always dangerous!)
Is it possible to code and inject an on device player app that could be inserted into the system (similar to Netflix) that could be triggered by another app for local playback without the need for an Internet connection?
Something like that would really increase the streaming capability for areas where Internet connection is not available.
And if the right code is found could even give local streams DHT capability if we had the ability to add those codecs to the player system.
ddggttff3 said:
You can, but you would have to do the modifications with an extracted system image, re-squashfs it back up, and then flash it back to the device.
Click to expand...
Click to collapse
I've been looking at system.img from 19084.001.zip
it seems it only got this then I unsquashfs it
[email protected]:~/squashfs-root# ls
bin boot chrome etc lib netflix res usr
I'm I looking in the wrong file?
Mape0661 said:
I've been looking at system.img from 19084.001.zip
it seems it only got this then I unsquashfs it
[email protected]:~/squashfs-root# ls
bin boot chrome etc lib netflix res usr
I'm I looking in the wrong file?
Click to expand...
Click to collapse
if you want to modify init.rc, then you need to extract the initramfs from the kernel, modify it, repackage the initramfs, compile the kernel from src (as the default one is signed, and can't be merged with a modified initramfs), and then merge the compiled kernel with the initramfs you modified.
ddggttff3 said:
if you want to modify init.rc, then you need to extract the initramfs from the kernel, modify it, repackage the initramfs, compile the kernel from src (as the default one is signed, and can't be merged with a modified initramfs), and then merge the compiled kernel with the initramfs you modified.
Click to expand...
Click to collapse
Looks like this gonna be my "children are sleeping" project for some time .-)
Well I extracted initramfs from boot.img and mounted it with cpio. At least I'm looking at the right files. I have never compiled a kernel for this kind of devices before (only for my computer) and I having trubble to cross compile, my arm compiled programs wont run on CC.
Do you got some good pages I can read and learn this stuff from?
Hey Folks!
I'm working on my newest Project called "Fluence HD Patch".
Basicly it will just add the content from my Fluence HD ROM to any excisting/flashed ROM, but now the Problem...
The Content which i add always to my ROMs forces a Bootloop after flashing as Stand alone. Included in a ROM there is no Problem. Changed the Updater Script a lot of times, but no success yet...
Hope anyone can help me!? This **** brakes my Neck!
Thanks in advance!
Did you edit it with something other than Notepad++
Miustone said:
Hey Folks!
I'm working on my newest Project called "Fluence HD Patch".
Basicly it will just add the content from my Fluence HD ROM to any excisting/flashed ROM, but now the Problem...
The Content which i add always to my ROMs forces a Bootloop after flashing as Stand alone. Included in a ROM there is no Problem. Changed the Updater Script a lot of times, but no success yet...
Hope anyone can help me!? This **** brakes my Neck!
Thanks in advance!
Click to expand...
Click to collapse
If experiencing a bootloop, does restoring the original build.prop and setting 0644 permissions through TWRP's File Manager allow the device to fully boot? If yes, then it must be an entry or a permissions issue. My next step in that case would be to flash the Fluence Patch to force the bootloop, boot to TWRP, mount System, set permissions to 0644 for the patched build.prop, and reboot. If the bootloop persists then there is certainly something inside causing it. Is there a single entry added that you didn't incorporate in one of your previous roms?
Also, the only other changes from flashing the patch is a build.prop backup and a tweak.prop on /sdcard, right? The next step in this scenario I would do after experiencing that second bootloop after ensuring the patched build.prop had 0644 permissions would be deleting both of those files that were added to /sdcard through TWRP's File Manager, assuming I had made my own copy of the original build.prop on /sdcard before the very first flash of the patch. If that doesn't allow the device to boot then there is something in the patched build.prop.
Edit*
After reading your Fluence Patch thread it is clear you are talking about the Full Patch causing the bootloop issue and not the one in the thread at the moment. I'll take a look if you want to send me a copy. The META-INF folder and any script(s) used during installation might be enough but not positive. :good:
ronaldheld said:
Did you edit it with something other than Notepad++
Click to expand...
Click to collapse
Nope, I'm using only Notepad++ ? The Zip flashs also successful...
guitardedhero said:
If experiencing a bootloop, does restoring the original build.prop and setting 0644 permissions through TWRP's File Manager allow the device to fully boot? If yes, then it must be an entry or a permissions issue. My next step in that case would be to flash the Fluence Patch to force the bootloop, boot to TWRP, mount System, set permissions to 0644 for the patched build.prop, and reboot. If the bootloop persists then there is certainly something inside causing it. Is there a single entry added that you didn't incorporate in one of your previous roms?
Also, the only other changes from flashing the patch is a build.prop backup and a tweak.prop on /sdcard, right? The next step in this scenario I would do after experiencing that second bootloop after ensuring the patched build.prop had 0644 permissions would be deleting both of those files that were added to /sdcard through TWRP's File Manager, assuming I had made my own copy of the original build.prop on /sdcard before the very first flash of the patch. If that doesn't allow the device to boot then there is something in the patched build.prop.
Edit*
After reading your Fluence Patch thread it is clear you are talking about the Full Patch causing the bootloop issue and not the one in the thread at the moment. I'll take a look if you want to send me a copy. The META-INF folder and any script(s) used during installation might be enough but not positive. :good:
Click to expand...
Click to collapse
Thanks for the Reply Man! As you suggested right in Your edit, the build.prop is just fine for now... I will upload the patch content after waking up completely... Was a hard night ?
Your help is much appreciated! Thanks again! :angel:
hi.I rooted the phone using magisk, it was installed and apparently rooted, but I have a problem with root file programs like root explorer or es file manager. The problem is that the rw mount does not work or I even have trouble installing busybox.
my phone : redmi note 10 pro
miui version : 12.5.8 and 12.5.9
android version : 11
magiak version : 23
I don't know deeply this case, but it was told that mounting r/w is not possible in recent Androids for system partitions.
However this is Magisk benefit that you put your files to it's tree and Magisk overmounts original files, I guess it does it using option "mount --bind".
You put file into /data/adb/modules/<module_name>/system/etc/<exemplary file> and after reboot you see it under /system/etc/.
At least the above path was checked personally by me by changing /system/etc/gps_psds.conf file to my own.
F308 said:
I don't know deeply this case, but it was told that mounting r/w is not possible in recent Androids for system partitions.
However this is Magisk benefit that you put your files to it's tree and Magisk overmounts original files, I guess it does it using option "mount --bind".
You put file into /data/adb/modules/<module_name>/system/etc/<exemplary file> and after reboot you see it under /system/etc/.
At least the above path was checked personally by me by changing /system/etc/gps_psds.conf file to my own.
Click to expand...
Click to collapse
I want to install a program as a system, but it is not possible without rw mount, do you know the solution?
I presume you have at least one Magisk module installed.
Put it into /data/adb/modules/<any_Magisk_module_name>/PATH_WHERE_YOU_WANT_TO_HAVE_IT/.
If wanted directories don't exist - create them.
Reboot.
Check.
Maybe tune permissions to make file executable.
Report result here.
F308 said:
I presume you have at least one Magisk module installed.
Put it into /data/adb/modules/<any_Magisk_module_name>/PATH_WHERE_YOU_WANT_TO_HAVE_IT/.
If wanted directories don't exist - create them.
Reboot.
Check.
Maybe tune permissions to make file executable.
Report result here.
Click to expand...
Click to collapse
I have no problem installing the module. My problem is accessing the system / app folder and making changes.
What changes do you want to perform?
Change one or more of files there, right?
If so - I repeat.
Put your modified file(s) under /data/adb/modules/<any_installed_Magisk_module_name>/system/app/ and reboot.
F308 said:
What changes do you want to perform?
Change one or more of files there, right?
If so - I repeat.
Put your modified file(s) under /data/adb/modules/<any_installed_Magisk_module_name>/system/app/ and reboot.
Click to expand...
Click to collapse
I do not want to install the module, I want to move an apk file to the system/app folder that is installed as a system and can not be deleted
I wasted my time.
Good luck.
I devoted a while to check that I was right suggesting what I suggested.