For those of you who activated 2G-only mode in your Mobile Network Settings and can't use that menu anymore due to crashes, there is a relatively easy way to reverse this condition and bring back the menu functionality while untoggling 2G-only mode.
1. Make sure your ROM is rooted (should be the default state of Paulicat's ROM).
2. Use ESFileExplorer (or a similar root capable file manager) to backup the contents of the following directory:
/data/data/com.android.providers.settings/databases/...
(Note that the critical file to backup is 'settings.db', the journal and other files are not critical but should be copied just in case)
3. Make a copy of 'settings.db' in a temporary location
(You will edit this copy of the database)
4. Use an SQLite editor (I used SQLite Debug) to open the 'settings.db' file you copied previously
5. Open the 'global' table and find (by the 'name' column) the row with 'name' that is 'preferred_network_mode'
6. Update the 'value' of this row from '1' to '0'
7. Execute your transaction and commit the changes to the table
8. Close the db and re-open it to verify that your changes have persisted
9. Return to '/data/data/com.android.providers.settings/databases/...' and delete the entire content of that directory
10. Immediately copy and paste the edited 'settings.db' file into the '.../databases/...' directory
11. Immediately turn off and restart your phone
At this point, you should have changed your phone's network preference setting from 2G only back to 2G/3G. This will also allow you to access the Mobile networks settings menu again.
I didn't find this solution for months because I didn't realize that the Android global settings database was stored in the above directory. I hope posting this here might help someone.
Reference: http://forum.xda-developers.com/showthread.php?t=2230207 (You may follow the suggestion to make this change via adb)
Related
I have flashed it on my Note, it works well.
I in no way created this, just thought it may be worth while.
The operation of this template is based on the VillainTheme System for the ROM VillainROM.
Link: http://www.villainrom.co.uk/forum/sh...inTheme-System
Credits and thanks to all XDA team that collaborated on the original script: Doctorcete, Stericson, Matt and Seshy​
What is Universal Flasher Tool?
is a complete template that is used to create the simplest possible way a subject flashable from recovery without the need to include or edit files. apk.
This new method uses the file system implementation metamorph (just have to put files and folders on their respective routes), with the advantage that the system identifies and injected into their applications without the need for external application. The subjects are flashed directly from recovery.
What are the advantages of this method compared to metamorph or traditional flasheables issues?
Do not include. Apk complete, only the files you want to include in the subject.
A theme created with this template is valid for any rom, even among different phone roms (the tests have been performed with SGS2 and Nexus one).
Optionally, the template can include complete files if desired, can even be used to install applications not system.
Does not depend on external applications like metamorph because it flashes directly from recovery.
Operation of the template
at the end of the post are attached a number of considerations to take into account, but basically works like this:
Identify the applications that want to thematize and checks that exist in the rom. Once the check, the system compares folders that will be introduced as well as files and injects them into the apk as long as the new file exists within the apk. This has been thought well to avoid filling an apk with files that do not belong because they are from another rom or because you made a mistake when typing the name, for example.
Once injected the files takes a zipalign the apk to optimize RAM usage.
Alternatively, if the topic includes external files or copy them to install applications on your path.
At the same time to be using the item, the system will generate a backup of changed files and automatically creates a file. Zip flashable from recovery, in case something goes wrong or do not like changes to previous state.
Finally, it also generates a small log with the outcome of the whole process is recorded in SD to verify that all changes are properly implemented.
How to create and edit your own theme
Download the template from the attachment in this post or the link below.
Recommended Tools: 7zip to include files and browse the file system (you can also use winzip or winrar without problems) and Notepad + + or any other plain text editor to edit the name of the mod.
Once downloaded, open the template double-click will observe and folders inside a file in the root. Here's that are in each folder and how to create the theme.
MOD.config file: (new from version 3.0) is an editable text file (recommend Notepad + +) where in addition to establishing the name of the MOD to set different parameters of the template.
MOD_VERSION= Name (name of the mod to be displayed in the system properties after the name of the rom. Are cautioned not to put a name too long and try to avoid as far as possible in the blanks.
CLEAN_MORPHING = not (compare the new files before injection into the apk, only enter if the file already exists. Turning the option dramatically reduces speed)
V4_MORPHING = yes (support to manage compatibility with existing folders-v4 system in some applications).
DO_BACKUP = yes (enable or disable the creation of the flashable backup from recovery to restore the existing theme).
LOG_ENABLED = yes (enable or disable the creation of a log file with the results of the process).
SCREEN_LOG = yes (shows the process of recovery on the screen or not. important notices are always shown even if the option is disabled).
Optionally, you can set a different path for memory cards (no need to touch these lines in most cases, you should not touch):
default_internal_sdcard = / EMMC
default_external_sdcard = / sdcard
Optionally, you can add special commands to mount partitions (no need to modify these lines in most cases, you should not touch):
mount_system = mount / system
mount_data = mount / data
README.txt:
Includes some additional instructions on the operation and the license. Please read before using the template to create a theme (in English). Carteta / tools: is the folder where you have placed the scripts and binary files necessary to flash the issue and make subsequent restoration. You do not need to touch anything in this folder to edit the theme. From version 3.0 has been deleted because busybox binary is no longer involved in the process. folder / META-INF folder system which includes the signature file and the script to launch from recovery. It is recommended not to touch. Folder / MORPH: This is the template folder where files should be included with the theme. In turn, the folder is divided into two subfolders called / data (for applications theming system NO) and / system (for theming system and applications framework). In the / MORPH / system / app files are included for the applications and / MORPH / system / framework for the framework files. NOTE: NO application theming system in / MORPH / data / app / myapp.apk supposed to change the digital signature, so from that time can not be updated from the market or will you installed in the market (like if it had been installed by 'other means' non-statutory ...). Therefore, we do not recommend any downloaded application thematize the market. You are advised that the complaints do not come then ... For each application you want to thematize must open a new folder called / nombre.apk (eg / Contacts.apk if you want to change the system application Contacts.apk) . It is necessary to respect the use of upper / lower case. Within each of these folders you have to respect that there are logical paths within applications, so that the files would have to place them in folders named / res / drawable, res / drawable-hdpi, etc ... It is the same structure metamorph an issue, so any item is readily convertible metamorph simply dragging folders.
No need to create any control file or anything like . The system is responsible for reviewing the folders to see what applications you want tematitar.
Folder / Xtras / system:
in this folder is where, if desired, can include files or complete applications that you wish to flash in conjunction with the subject. For example, sound files, bootanimation, scripts, complete applications, etc ... Folder / Xtras / data: in this folder is where, if desired, can not add applications to be installed system during flashing. Folder / Xtras / sdcard: in this folder you can add files to make copied to the SD card, as packs of icons, sounds, videos, etc ... to take into account considerations
Always respect the use of uppercase / lowercase letters in the names of files or folders and logical paths located within the apps.
With this system the themes may be universal, although depending on the type of files a user input may cease to be:
If you only include image files theme is compatible with any rom from any phone.
If you also include. xml may only operate in one rom, but can still work on future updates of it.
If resources are included for translations (resources.arsc) the issue would only be valid for a particular rom.
The. Zip with the issue is not necessary for you to sign flashearse, and is valid for CW-Recovery and Recorevy-RA. If you do not have to remember signing off signature checking before flashing.
Original Thread:http://http://www.htcmania.com/showthread.php?t=258333
Also:http://forum.xda-developers.com/showthread.php?t=1474686
On the galaxy s 3 us version most of the recoverys are not reading the external sd so should I changed the mounts on the script?
Sent from my SGH-T999 using Tapatalk 2
Hello!
I have found a way to replace the standard dock mode app on titan to an app of your choice.
First of you will have to find the guid of the app you want to replace Dock mode with. For example i will use the GUID of spotify: ca8d6603-a9ae-4a05-8643-baad091ecdd1
!PLEASE NOTE THAT I DON`T TAKE ANY RESPONSIBILITY FOR ANY DAMAGE YOU DO TO YOUR PHONE!
1) First go to HKLM/Software/HTC/USBDriver/DockMode with a registry editor of your choice.
2) Here you need to change the Value named AccessoryDockModeGUID to the GUID of the GUID of the application you to popup when you put the phone in the cradle.
3)Open a file explorer of your choice(I used windows mobile device center) and go to "\Application Data\PUBLIC\DOCKMODE" and make a backup of the file named "DockMode".
4)Now open the file with a text editor. You will see the following: "3570f057-6c31-4751-a0a7-899820af6cf4 1 1".
5)In this file replace "3570f057-6c31-4751-a0a7-899820af6cf4" with the GUID of your app for this example "ca8d6603-a9ae-4a05-8643-baad091ecdd1".
6)You should now end up with something like this: "ca8d6603-a9ae-4a05-8643-baad091ecdd1 1 1"
7)Now save the file and reboot your phone!
I have attached the original DockMode file and the original DockMode GUID is: "3570f057-6c31-4751-a0a7-899820af6cf4" in case you forget to take a backup.
//Lajba
And for HTC Car mode app
1) First go to HKLM/Software/HTC/USBDriver/CarMode with a registry editor of your choice.
2) Here you need to change the Value named AccessoryCarModeGUID to the GUID of the GUID of the application you to popup when you put the phone in the cradle.
3)Open a file explorer of your choice(I used windows mobile device center) and go to "\Application Data\PUBLIC\CARMODE" and make a backup of the file named "CarMode".
4)Now open the file with a text editor. You will see the following: "0bfb1b34-aff6-4ac5-8952-9041fd94c760 1 1".
5)In this file replace "0bfb1b34-aff6-4ac5-8952-9041fd94c760" with the GUID of your app for this example "da8734ed-666a-4227-81ea-8fc937752d98".
6)You should now end up with something like this: "da8734ed-666a-4227-81ea-8fc937752d98 1 1"
7)Now save the file and reboot your phone!
Thanks. Just curious, what registry editors do you all prefer to use?
Have you ever installed a new rom, but completely forgot which notification sound you were using? I have a nandroid backup of the old rom, but really don't want to completely restore the rom just to figure out which sound I was using. Android stores this in a database, and I'll show you how to access that database. In hindsight, it may just be easier to restore the nandroid backup. But, this is how to do it using a nandroid backup.
I'll be using Ubuntu 12.04 to do this. I believe it can be done with Windows as well, though the commands and programs will differ. Again, this assumes that you don't remember what the filename was. If you do, you can just skip to step 7.
1. Copy your nandroid backup files to your computer. Specifically, the "data.ext4.tar" and any "data.ext4.tar.a", "data.ext4.tar.b", etc. files.
2. The files need to be combined together. Use the command "cat data.ext4.tar data.ext4.tar.a data.ext4.tar.b > data-combined.tar" or similar for your filenames. It combines all of your data.ext4.tar files into one new file, data-combined.tar. This should give you a working tar file. I got this step from http://forum.xda-developers.com/showthread.php?t=2194171.
3. Extract the data-combined tar file. If you're a super-cool linux hacker, you probably know some terminal command to do this, like tar -randomLettersHere (xzvf?). I just right clicked the tar file and selected "Extract Here".
4. Navigate to "./data/com.android.providers.settings/databases/settings.db" and open the file. I didn't have any program to read SQL databases, so I let Ubuntu installed the recommended one for me, called "Sqliteman".
5. Using the list on the left, go under Tables-System. You should see the contents of that table, which look like an excel spreadsheet. The row (or tuple) we're looking for has the field "name" equal to "ringtone" or "notification_sound", depending on which file you're trying to locate. You can scroll through the rows and look for those rows, or you can enter an SQL command in the top box and hit the green arrow to run it and filter just the ones we want. Try this-
Code:
select *
from system
where name='notification_sound' or name='ringtone';
This pulls up all the rows where "name" is exactly equal to either of those strings. You can also search for anything that contains those strings by using this syntax-
Code:
select *
from system
where name like '%notification%';
If you're looking for your ringtone, try a query that just contains "ringtone", like this-
Code:
select *
from system
where name like '%ringtone%';
(That pulled up the actual file for me under the name "ringtone_CONSTANT_PATH")
If you're using a different rom than that I was (or a different device), you might need to tweak what you look for. Try changing the strings you search for. What we're looking for is for the entry where "value" equals something like "content://media/internal/audio/media/238". It might have the word 'internal' instead of 'external'. Note that number at the end, which is some kind of media ID number.
6. Now, open the SQL file "./data/data/com.android.providers.media/databases/external.db" or "./data/data/com.android.providers.media/databases/internal.db" depending on whether the value in step 5 had the word internal or external. Find the row where "_id" equals the number at the end of your "value" string in step 5. You can scroll through the "files" table, or enter a query like this-
Code:
select *
from files
where _id='238';
The field "_data" should show the path for your file. For me, it was "/system/media/audio/notifications/S_Dew_drops.ogg". Oh, how I love you, Touchwiz...
7. Now you know where the file is. If your new rom doesn't have that ringtone/notification sound any more, you can probably retrieve it from two places. First, check the rom installation zip file (probably the easiest way) if it was an included sound. Open the installation zip file, and look in the path you found in step 6. The second way is to go through your Nandroid backup. Follow steps 1-3, but copy, combine, and extract your system.ext4.tar file(s). Again, just look in the same path from step 6, and it should be there. These paths are typically "/system/media/audio/notifications/" and "/system/media/audio/ringtones".
Enjoy your old, familiar sound again!
My Setup:
- clean installed sloane-5.2.1.0-rooted_r2 Image
- xposed-v86-sdk22-arm64.zip
- open_gapps-arm64-5.1-pico-20160710.zip
- Google Playstore (Copy a working Phonesky.apk to /System/priv-app/Phonesky and chmod 644)
- XposedInstaller_3.0_alpha4.apk
- HDXposed.apk
- Secure Settings
- Tasker
- Settings.apk from FireTuner
- Null Keyboard
1. Install Xposed+Installer, Tasker, Secure Settings (Dont forget to enable the Module in Xposed) and Null Keyboard
2. Install FireTuner on your PC. Let FireTuner download the Settings.apk.
When FireTuner tries to install the Settings.apk disable your network connection and copy the Settings.apk from %AppData%\Roaming\FireTuner to your Desktop.
Copy the Settings.apk to /System/priv-app/Settings on your FireTV2 and chmod 644
3. Activate Null Keyboard in Settings.apk
Attention!! There is no Mouse cursor in the Settings.apk, you have to try and hope that you hit the right settings
4. Open Tasker and Create a new Event "Monitor Start"
5. Create a new Task named "TaskerAccessibilityService"
6. Edit the created Task: Choose Plugin==>Secure Settings==>System+ Actions==>Accessibility Services and enable Tasker:MyAccessibilityService
7. Create a New Profile named "AltKeyboard" and choose your desired application
8. Create a new App Task named "StartAltKeyboard" and choose:
Plugin==>Secure Settings==>System+ Actions==> Input Method select "Null Keyboard" and save
9. Create a Exit Task named "StopAltKeyboard" (click on the green Arrow) choose:
Plugin==>Secure Settings==>System+ Actions==>Input Method, select "FireTV IME - Englisch (US)" and save.
Your FireTV will now switch to Null Keyboard in your chosen application and switch back to standard in other Applications.
This works pretty good. Thanks for the write up, been a while since I have used tasked/secure settings.
EDIT Wrong Thread
hi Everyone,
I'm sticked with the common issue of how to make writable the external SD.
I've read topics on the forum:
http://forum.xda-developers.com/desire-601/help/how-to-writable-external-sd-kitkat-t2877686
http://forum.xda-developers.com/desire-601/help/sd-card-permissions-off-t2833195
http://forum.xda-developers.com/showthread.php?t=2687734
Well ok, but I'm a noob so sometimes it's not clear, sometimes it's not working for me.
So let's explain:
- My device is rooted (it was made by a tech using TWRP if I'm right)
- SuperSU is installed
1/ I tried some apps like SDfix and Int-SDCard Write fix
> Result = KO
2/ I tried to manually modify the platform.xml file > sometimes the editor does not want to save the modification, sometimes it says OK but the file don't seem to be modified (the last modification date is still 2014). Permissions are: rw-r--r--
a. Using Rom Toolbox, I go the file and edit it with:
-FX TextEdit > Get a Warning = "This file is on read-only filesystem. You will not be able to save any changes unless you first remount it as read/write'
> Result = KO
- RB Text Editor: it seems i can edit it. Save the file without warning message 'Saved'. But once back on the /system/etc/permissions folder, nothing looks modified (not today's date). I can reopen the file and see the modification by the way. But once I reboot, I go back the my original issue.
> Result = KO
- ES Text editor: can't even save the file
> Result = KO
So what ?
I've seen this message coming along:
"if you are rooted then you doing something wrong (did you maybe forgot to mount system as R/W ?).
If you are unable to do modify platform.xml then you doing something wrong or yours device isnt rooted."
> At what moment is it possible to mount the system with R/W grants ?
I'm fed up with not being able to write on SD card....................
Thx in advance !!!!!
Opening a terminal on my phone:
- i can't 'cp file1.xml file2.xml' in /system/etc/permissions
- i can't 'chmod 644 file1.xml'
Each I get "Read-only file system"
Flash your stock kernel with insertcoin or kofilakernel