Hello guys
I need your help, i'm working on a mod and a friend said me to modify the file: settings.db located in data/data/com.android.providers.settings/databases/settings.db
I only have to change "1" to "0" in the "secure" tab
for this I used Sql Lite browser for windows 7.
So i did it and saved the database, and then with root explorer replaced with the original settings.db but ....
I entered in a boot loop, why ?
I know for sure the "0" is a secure value, because used in a stock old rom
Why bootloop so? Have I to changed permissions to file?
Can please help me to do it without a new bootloop?
Thanks
Related
Hi all! I'm having an issue with my huawei Y200 phone. I wanted to place a .so file in system/lib dir, and I changed system/lib permissions. (I can't copy the .so file into system/lib after changing the permissions neither) The phone couldn't open any app, so I rebooted it, and now it keeps on bootlooping (into CWM), when I want to reboot it. I read that modifing system/lib permissions can often causes bootlooping, but I still don't know, how to fix it. I've tried Advanced/fix permissions in CWM, but no success. I'm asking for a competent, pls help me with solving this problem!
Greetings, nagymisike12
Perhaps, can I somehow set back system/lib dir permissions with adb commands? If so, pls let me know.
Anybody? Pls, help me, I haven't find the solution yet! :S
After installing TWRP and rooting the device, I followed this tutorial to modify the framework-res.apk file:
http://forum.xda-developers.com/showthread.php?t=2553963
I used the Android Multitool to handle the decompile and recompile and it seemed to all work as advertised.
So then I booted into recovery mode and pushed the updated framework-res.apk file over to the tablet via adb push and it reports a successful copy. But when I reboot the device, not only are the changes not showing up, but if I browse the tablet's /system/framework directory using ES FIle Explorer, the framework-res.apk file is still timestamped 11/16/2013, like it has never been updated.
What am I missing or doing wrong here? I've beat my head against the wall for hours on this and can't get it to take
thanks
Got it working!
snafu7x7 said:
After installing TWRP and rooting the device, I followed this tutorial to modify the framework-res.apk file:
http://forum.xda-developers.com/showthread.php?t=2553963
I used the Android Multitool to handle the decompile and recompile and it seemed to all work as advertised.
So then I booted into recovery mode and pushed the updated framework-res.apk file over to the tablet via adb push and it reports a successful copy. But when I reboot the device, not only are the changes not showing up, but if I browse the tablet's /system/framework directory using ES FIle Explorer, the framework-res.apk file is still timestamped 11/16/2013, like it has never been updated.
What am I missing or doing wrong here? I've beat my head against the wall for hours on this and can't get it to take
thanks
Click to expand...
Click to collapse
OK hopefully if you're having the same problem and stumble upon this post it will help you as well. As far as I can tell, the issue was because that framework-res file is marked read-only on the file system and for some reason even though ADB was reporting that it had transferred the file successfully I don't think it ever was. Here's how I resolved it.
1)power off the device
2)boot into TWRP
3)choose file-manager (under 'Advanced')
4)navigate to the /system/framework directory and select the framework-res.apk file
5)click the CHMOD 755 button to set the permissions to rwx
6)from your PC execute the ADB push command...for example if my framework-res.apk is in the same directory as ADB.exe
adb push framework-res.apk /system/framework/framework-res.apk
it should give you a message like 4109 KB/s (34859291 bytes in 8.284s) or something similar
7)return to the main menu of TWRP...choose Reboot then System
now the framework file reflects my changes
snafu7x7 said:
After installing TWRP and rooting the device, I followed this tutorial to modify the framework-res.apk file:
http://forum.xda-developers.com/showthread.php?t=2553963
I used the Android Multitool to handle the decompile and recompile and it seemed to all work as advertised.
So then I booted into recovery mode and pushed the updated framework-res.apk file over to the tablet via adb push and it reports a successful copy. But when I reboot the device, not only are the changes not showing up, but if I browse the tablet's /system/framework directory using ES FIle Explorer, the framework-res.apk file is still timestamped 11/16/2013, like it has never been updated.
What am I missing or doing wrong here? I've beat my head against the wall for hours on this and can't get it to take
thanks
Click to expand...
Click to collapse
Not sure which tab you have but if you have the 10" then you can install the latest Pimpdroid rom that had multiuser built in. It's not as elegant as the Samsung multiuser but does the job.
found a way to get it to work
You need
Stock Rom with root
busybox*installed
build.prop Editor ( playstore)
Open the Editor
Press add*on Top
Property name:
fw.max_users
Property key:
Number of users u like to have
Save it.
Restart tab.
Now u have an entry under settings which is called Users
There u can add a new One.
Inka thing which is bugging me is that only the First User has root Access.
But my girl is using the second User so its fine for me.
Sent from my HTC One using XDA Premium 4 mobile app
@sirbo36
Thanks a lot! Works perfect!
assetttt said:
Not sure which tab you have but if you have the 10" then you can install the latest Pimpdroid rom that had multiuser built in. It's not as elegant as the Samsung multiuser but does the job.
Click to expand...
Click to collapse
Pimpdroid ROM hasn't multi-user function.
Mine works great love this feature
did exactly this
Cant get this to work got it saved no user profile under setting help
---------- Post added at 07:07 PM ---------- Previous post was at 06:33 PM ----------
Attached is a screen shot of build prop
UPDATE: There is a much simpler solution that anyone can use without learning Linux commanline or file permissions. See this thread for details:
http://forum.xda-developers.com/showpost.php?p=54462957&postcount=13
WARNING: If you do not understand every step of these low-level Linux command-line technical instructions, then do not attempt this method or you may brick your phone! These instructions are written for people who understand android developer tools, Linux command-line tools, and file permissions. If you do not understand these Android development basics, then find another walkthrough.
I got my phone up and running and text messaging, 4G LTE data connectivity, and phone calls worked just fine, however, I noticed I was unable to send and receive MMS messages (picture messaging). I tried every solution I could find on the web for changing the APNs on my rooted LG Optimus G Pro E980, and by trial and error, I discovered the following solution:
The stock Android ROM supplied by AT&T for the Optimus G Pro - Android 4.4.2 (Build E98020G), has disabled the ability to add working APN settings through the system APN settings dialog by defaulting all new APNs to have the (apn) type="default,dun". The settings screen does not let you change this value, so you have to edit the values directly in the SQLite database.
None of the free SQLite-database-editors in the Android market were able to edit the read-only /data/data/com.android.providers.telephony/databases/telephony.db file (after following instructions for editing the APN in the database in the folder where it is stored).
So, using ES File Manager (search for "com.estrongs.android.pop" on google play), I copied it to my SD-Card, copied to my computer and edited it with SQLite Database Browser (a SourceForge project identified as sqlitebrowser).
VERY IMPORTANT: The permissions change when copying the file from your computer to the SDCARD and when copying it from the SDCARD to the /data/data/com.android.providers.telephony/databases/ folder. So, I had to set the permissions back to the original telephony.db permissions & owner. The permissions should match all of the other .db files in the /data/data/com.android.providers.telephony/databases/ folder, like so:
RW-RW----
VERY IMPORTANT:Change the file owner back to "radio" from "root". Change the group back to "radio" from "root". If you do not change the owner and group back to "radio" after you copy the telephony.db file back to the /data/data/com.android.providers.telephony/databases/telephony.db path, the phone.apk process will repeatedly crash until it restarts your phone (and your phone will keep rebooting until you delete the telephony.db file that has incorrect permissions or incorrect owner). To boot, the phone.apk runs under the "radio" group and needs the critical Android OS file: telephony.db to be owned and accessible by the "radio" group.
After creating an APN per Straight Talk's instructions, changing the type field in the carriers (APNs) record stored in the telephony.db, copying over the new telephony.db (and overwriting the original), changing the permissions & owner of the copied file, and rebooting the phone, I was able to send and receive text messages and picture messages (MMS) to myself.
Note: My phone came with the correct "Service Center Address" setting, because it was an AT&T branded phone before I brought it to Straight Talk. However, you may need to change this setting if you came from another carrier with your phone. The correct setting for Straight Talk customers on the AT&T LTE network should be (the same as it is for AT&T customers on an AT&T plan):
Code:
+13123149810
Although the /system/etc/apns-config.xml file has several, misleading APN values in it, this file is not used to store the APN records in Android 4.4.*. Instead, APNs are stored in the /data/data/com.android.providers.telephony/databases/telephony.db SQLite database.
Also, there is a rumor spreading around the internet that you cannot send MMS messages when your WIFI is connected (instead of a 4G LTE connection). That is false: my phone sends and receives MMS messages while the WIFI is connected.To make it easier for you to change your APN settings on your phone, I have attached my working telephony.db file. It contains only one APN record for Straight Talk on AT&T's LTE network. I deleted all of the other APN records from the database, per Straight Talk's APN instructions.
If you are curious, I also attached the database dump of the attached telephony.db, which was auto-generated by SQLite Database Browser. It is a text file called "telephony-dump.sql".
Hi, I tried this step by step and now my phone does nothing but crash repeatedly. Any way to fix this?
How to unbrick your phone if you missed steps in the instructions
l337m45732 said:
Hi, I tried this step by step and now my phone does nothing but crash repeatedly. Any way to fix this?
Click to expand...
Click to collapse
If you do not understand every step of the above low-level Linux command-line technical instructions, then do not attempt this method or you may brick your phone!
It sounds like a permissions issue - the android operating system is crashing because it does not have permission to read the critical OS file: telephony.db. Did you set the owner, group, and permissions on the telephony.db file correctly? If you are unable to change the permissions back on the telephony.db, then follow the instructions above to fix your problem:
ratkiley said:
VERY IMPORTANT: The permissions change both when copying it to and when copying it from the SD-Card. So, I had to set the permissions back to the original telephony.db permissions & owner, (matching the other .db files in the /data/data/com.android.providers.telephony/databases/ folder):
RW-RW----
VERY IMPORTANT:Change the file owner and group back to "radio" from "root". If you do not change the owner and group back after you copy the file back to the /data/data/com.android.providers.telephony/databases/telephony.db path, the phone.apk process will repeatedly crash until it restarts your phone (and your phone will keep rebooting until you delete the telephony.db file that is owned by "root").
Click to expand...
Click to collapse
If you don't know how to delete the telephony.db file, then you can flash the stock AT&T android Operating System image file to unbrick your phone. There are many tutorials and walkthroughs on this topic on xda developers. This walkthrough is pretty comprehensive:
http://forum.xda-developers.com/showpost.php?p=44983841&postcount=1
Hi
I know there may have been numerous threads on here and various websites setting out how to enable camera2API without root on Redmi Note 5 AI, however, I am struggling to get this installed to enable me to ultimately get the Google Camera app.
I have followed through the steps on this particular website (https://www.technobuzz.net/google-camera-redmi-note-5-pro/) to enable the camera2api and all seems to go well until I get to the step before 'adb shell' where nothing really happens. I have tried so many times and each time the result is the same. I am not sure where I have gone wrong. I have already had the phone unlocked from Xiaomi. I hope someone on here would be able to help me out on this.
Any help would be greatly appreciated.
Unlock bootloader
Install twrp
From twrp mount system partition
Disable system partition read only option
Copy build.prop file from /system/ and add these lines to build.prop file
persist.camera.HAL3.enabled=1
persist.camera.eis.enabled=1
Save build.prop file and copy updated buildprop file to /system/ file
SunilSuni said:
Unlock bootloader
Install twrp
From twrp mount system partition
Disable system partition read only option
Copy build.prop file from /system/ and add these lines to build.prop file
persist.camera.HAL3.enabled=1
persist.camera.eis.enabled=1
Save build.prop file and copy updated buildprop file to /system/ file
Click to expand...
Click to collapse
Hi, thanks for the reply.
Is there a detailed step by step guide to follow and links to download the relevant files ? Sorry, I'm not too savvy on technology.
As this post https://forum.xda-developers.com/showpost.php?p=78125891&postcount=43 describes, I modified mixer_paths_tavil.xml changing the AVC Volume value in attribute headphones-hifi-dac, from 15 to 6, in order to achieve the AUX volume values in normal mode
The file mixer_paths_tavil.xml is saved correctly. Then I mount /vendor read-only again and remount, and I check that the file remains changed with the modification done. The modification date timestamp reflects the change
But no effect in the sound
So I guess I should reboot the phone for the change takes into effect. But then, after the reboot, the mixer_paths_tavil.xml is again the original one without the changes (and the mofication date is Dec 31 2008, the original ...)
So how should I edit this file to keep the changes with the reboot?
I'm on Pie
Thanks in advance
I know with my v30 i changed values in mixer_paths tavil.xml set permissions reboot and I was all good but my lg g7 im still trying to unlock my bootloader with the instructions but after updating magisk manager I have no root to finish the rest of the commands. I wish I could edit this same file and see whats going on and why it wont stick after reboot.
I am also facing the sam issue my bootloader is unlocked and i am rooted on android 10. Changes dont stick after reboot.
First thing is make or edit magisk module to have this file changed. Second thing is make a file called service.sh (with permissions rw- r-- r-- or 0644)
In this file you need to write
Code:
killall audioserver
Explanation: Vendor partition in pie and android 10 is impossible to edit in case of LG G7. You need to have this file modified in magisk module with proper permissions and catalogs (vendor/etc). Even if you have audio related files modified in magisk module, there's second problem. Everything will be booted with default values. That's why you need service.sh with killall audioserver. This will reload all your audio related files at early stage of system boot, and new values will be applied.
ShuAK said:
I am also facing the sam issue my bootloader is unlocked and i am rooted on android 10. Changes dont stick after reboot.
Click to expand...
Click to collapse
Can you please tell me that how you rooted your device?
hasnawtahmed said:
Can you please tell me that how you rooted your device?
Click to expand...
Click to collapse
Are u bootloader unlocked? If not then follow this guide to unlock it.
https://forum.xda-developers.com/lg-g7-thinq/how-to/howto-updated-guide-to-unlock-t4168771
After that rooting is very simple process use QFIL to backup your boot_a img copy it to phone install magisk manager and and patch that file with magisk. Then write this img file to ur boot_a partition using QFIL and thats it.
ShuAK said:
Are u bootloader unlocked? If not then follow this guide to unlock it.
https://forum.xda-developers.com/lg-g7-thinq/how-to/howto-updated-guide-to-unlock-t4168771
After that rooting is very simple process use QFIL to backup your boot_a img copy it to phone install magisk manager and and patch that file with magisk. Then write this img file to ur boot_a partition using QFIL and thats it.
Click to expand...
Click to collapse
I have unlocked bootloader. Qfil gives an error something like firehose failed or download fail somethinh like that.
ShadoV90 said:
First thing is make or edit magisk module to have this file changed. Second thing is make a file called service.sh (with permissions rw- r-- r-- or 0644)
In this file you need to write
Code:
killall audioserver
Explanation: Vendor partition in pie and android 10 is impossible to edit in case of LG G7. You need to have this file modified in magisk module with proper permissions and catalogs (vendor/etc). Even if you have audio related files modified in magisk module, there's second problem. Everything will be booted with default values. That's why you need service.sh with killall audioserver. This will reload all your audio related files at early stage of system boot, and new values will be applied.
Click to expand...
Click to collapse
Where i create service.sh file?
@hasnawtahmed try another pc if u can coz i faced the same issue on my laptop i have windows 7 and i cannot access partition data but i have a windows 10 PC and in that i can easily access and modify.
ShuAK said:
First thing is make or edit magisk module to have this file changed. Second thing is make a file called service.sh (with permissions rw- r-- r-- or 0644)
In this file you need to write
Where i create service.sh file?
@hasnawtahmed try another pc if u can coz i faced the same issue on my laptop i have windows 7 and i cannot access partition data but i have a windows 10 PC and in that i can easily access and modify.
Click to expand...
Click to collapse
I'm also using a windows 10 pc
Then reinstall drivers
ShuAK said:
Where i create service.sh file?
@hasnawtahmed try another pc if u can coz i faced the same issue on my laptop i have windows 7 and i cannot access partition data but i have a windows 10 PC and in that i can easily access and modify.
Click to expand...
Click to collapse
You can create that file in main module catalog.
I created service.sh and copy it inside a dual speaker magisk module zip file.
Yep thnx man its working now sounds are too much lowder
ShuAK said:
I created service.sh and copy it inside a dual speaker magisk module zip file.
Yep thnx man its working now sounds are too much lowder
Click to expand...
Click to collapse
Would you mind to share the modified module? Thank you in advance