Database Info

[Q] replacing the H+ icon

Ive been messing around in the framework for a little while now, replacing icons and such. I have managed to replace all my notification icons with custom ones that i am making, but i cant seem to find the H+ icon. all the other ones are in drawable-hdpi(3g h ect)
can someone please shed some light on this

gjc5500 said:
Ive been messing around in the framework for a little while now, replacing icons and such. I have managed to replace all my notification icons with custom ones that i am making, but i cant seem to find the H+ icon. all the other ones are in drawable-hdpi(3g h ect)
can someone please shed some light on this
Click to expand...
Click to collapse
They are in the rosie. Apk
Sent from my Inspire 4G using XDA Premium App

Were in Rosie.API are they? I found some + icons but not the h+ ones

I believe they are actually in framework-res.apk.

Gene Poole said:
I believe they are actually in framework-res.apk.
Click to expand...
Click to collapse
Negative they are definetly in the Rosie.apk unless they changed the location in sense 3.0. It should be in the same folder as it would be in framwork-res.apk.
Sent from my Inspire 4G using XDA Premium App

SystemUI.apk (system/app). I change mine all the time.
*Drawable-HDPI, btw

Simba501 said:
SystemUI.apk (system/app). I change mine all the time.
*Drawable-HDPI, btw
Click to expand...
Click to collapse
thats on a non inspire based rom correct?

Every time i edit an icon in frameworkres.apk i get a bootloop. What am i doin wrong?
Sent from my Inspire 4G using XDA Premium App

gho5t82 said:
Every time i edit an icon in frameworkres.apk i get a bootloop. What am i doin wrong?
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
Are you unpakcing the apk, if not when you are putting new things in do you have it set to store?

mudknot2005 said:
thats on a non inspire based rom correct?
Click to expand...
Click to collapse
Any ROM that has a SystemUI.apk.
In any instance where there isn't one, those icons are in the framework-res.apk.

Im not unpacking it. What do u mean by having it set to store?
Sent from my Inspire 4G using XDA Premium App

gho5t82 said:
Every time i edit an icon in frameworkres.apk i get a bootloop. What am i doin wrong?
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
Hard to tell. What are you using to change the icons?

Simba501 said:
Hard to tell. What are you using to change the icons?
Click to expand...
Click to collapse
I was trying to drag some icons from coredroid to virtuous unity's framework and systemui.apk's, using 7zip.

gho5t82 said:
I was trying to drag some icons from coredroid to virtuous unity's framework and systemui.apk's, using 7zip.
Click to expand...
Click to collapse
You'll need to be on a laptop/pc to do this method. Before you get started, make sure you have a backup of the apk you're modding (placed on the sd card somewhere). Also wouldn't hurt to make a nandroid. In the event where you need to revert the old apk back, skip to the steps regarding moving the apk to the original folder.
Download APK manager, open it, place the desired system apk into the "place here for modding", run the script, and select the "don't clear out current projects" option.
Near the top you'll see "extract apk". Select this option, wait for it finish, and navigate to the original apk manager folder. Here you'll see a new folder, "out". This is where the apk you extracted is. Navigate to res > drawable-hdpi and replace the desired icons. Make sure the new icons are named to exactly what you're replacing (you should get a "do you want to overwrite" dialog). They should also be sized to what the original file is (or close to it). Once you're done, back out back to the apk manager folder. Run the script again, select optimize images, wait for it to finish, then run zip apk, then 1 (for system app). Your new apk will be in the "place here for modding" folder under the name of "repackaged-unsigned" apk. You'll need to put this on your sd card, move it to "system" first (this will allow you to change permissions), rename it to the original system apk that you're replacing. Change the permissions to rw-r-r (accessible in root explorer by long pressing the file and selecting permissions - first two boxes on the first line and only the first box on the next two lines). From here, move it into the folder where it's replacing the original apk, you should get a "do you want to overwrite", select yes. Scroll down to verify the apk has the correct permissions and that the last modified date is showing as recently. If you don't get an "overwrite" prompt, you need to move it back and correctly name it until you do get the prompt. Lastly, reboot. In some situations (e.g., modifying the Mms apk or other system applications), it would help if you cleared cache and dalvik cache (boot will take a long time). You should see your changes. Seems like a lot but it's very simple. Good luck.
Sent from the most interesting device in the world.

Simba501 said:
Unfortunately, it's not that simple. Seems as though the apk may be losing its system signature (when you edit it like that). You'll need to be on a laptop/pc to do this. Before you get started, make sure you have a backup of the apk you're modding (placed on the sd card somewhere). Also wouldn't hurt to make a nandroid. In the event where you need to revert the old apk back, skip to the steps regarding moving the apk to the original folder.
Download APK manager, open it, place the desired system apk into the "place here for modding", run the script, and select the "don't clear out current projects" option.
Near the top you'll see "extract apk". Select this option, wait for it finish, and navigate to the original apk manager folder. Here you'll see a new folder, "out". This is where the apk you extracted is. Navigate to res > drawable-hdpi and replace the desired icons. Make sure the new icons are named to exactly what you're replacing (you should get a "do you want to overwrite" dialog). They should also be sized to what the original file is (or close to it). Once you're done, back out back to the apk manager folder. Run the script again, select optimize images, wait for it to finish, then run zip apk, then 1 (for system app). Your new apk will be in the "place here for modding" folder under the name of "repackaged-unsigned" apk. You'll need to put this on your sd card, move it to "system" first (this will allow you to change permissions), rename it to the original system apk that you're replacing. Change the permissions to rw-r-r (accessible in root explorer by long pressing the file and selecting permissions - first two boxes on the first line and only the first box on the next two lines). From here, move it into the folder where it's replacing the original apk, you should get a "do you want to overwrite", select yes. Scroll down to verify the apk has the correct permissions and that the last modified date is showing as recently. If you don't get an "overwrite" prompt, you need to move it back and correctly name it until you do get the prompt. Lastly, reboot. It would help if you cleared cache and dalvik cache (boot will take a long time). You should see your changes. Seems like a lot but it's very simple. Good luck.
Sent from the most interesting device in the world.
Click to expand...
Click to collapse
Thank you very much for the detailed instructions, i will try this asap!

gho5t82 said:
Thank you very much for the detailed instructions, i will try this asap!
Click to expand...
Click to collapse
Good luck! Report back!
Sent from the most interesting device in the world.

Simba501 said:
Good luck! Report back!
Sent from the most interesting device in the world.
Click to expand...
Click to collapse
I keep getting adb not found messages when i run the script. I have adb installed through sdk.

So I checked system/app and there is not a systemui.apk. I haven't been able to find that apk anywhere.

gho5t82 said:
I keep getting adb not found messages when i run the script. I have adb installed through sdk.
Click to expand...
Click to collapse
Manually check via a root explorer on your phone. If you have one, entering it in adb is probably case sensitive. You'd have to enter it exactly as it appears. What ROM are you using?
Sent from the most interesting device in the world.

gjc5500 said:
So I checked system/app and there is not a systemui.apk. I haven't been able to find that apk anywhere.
Click to expand...
Click to collapse
What ROM are you using?
Sent from the most interesting device in the world.

[Q] Build.prop tweaks don't stick, reset when I reboot

Hi,
I'm pretty sure this problem could be common to all rooted devices, so I'm posting it in the general Q&A.
Basically, I would like to experiment with some build.prop tweaks I found around other XDA topics. I'm sure all of you know about the general tweaking of the said file, so I won't get into too much detail about it.
However, the changes just don't stick. They reset to default every time I reboot, as if the build.prop file never changed. So, how do I make them stick?
Phone details:
Phone: Xperia X8
ROM: FroyoPro v2.5
Kernel: Stock (can't unlock the bootloader, unfortunately)

Are you saving before exiting?

XperienceD said:
Are you saving before exiting?
Click to expand...
Click to collapse
Of course! I even double-check if the changes were still there by opening the modified build.prop after the work is done. For the changes I used Root Browser Lite with the Text Editor pre-installed inside. This method does work well, as I used it to modify hw_config parameters related to governors a couple of weeks back.
I've read somewhere that sometimes changes aren't possible if the kernel is stock. Could that be the case here?
If not, are there any other methods I could use to modify build.prop?

xWhiskey said:
Of course! I even double-check if the changes were still there by opening the modified build.prop after the work is done. For the changes I used Root Browser Lite with the Text Editor pre-installed inside. This method does work well, as I used it to modify hw_config parameters related to governors a couple of weeks back.
I've read somewhere that sometimes changes aren't possible if the kernel is stock. Could that be the case here?
If not, are there any other methods I could use to modify build.prop?
Click to expand...
Click to collapse
A quick google caused me to find this thread and I too am having the same problem. I'm currently trying to edit my build.prop to unlock games which say they are incompatible. I'm using ES File Explorer and the built in text editor to edit and save the .prop file, I check if the changes have saved before rebooting my phone but when I turn it back on it has reverted back to stock.

sircrisp said:
A quick google caused me to find this thread and I too am having the same problem. I'm currently trying to edit my build.prop to unlock games which say they are incompatible. I'm using ES File Explorer and the built in text editor to edit and save the .prop file, I check if the changes have saved before rebooting my phone but when I turn it back on it has reverted back to stock.
Click to expand...
Click to collapse
Check if your ROM has a dual build.prop file. If one exists in system/bin, you ought to edit that one for the change to stick. This solved the issue for me, and might solve it for you.
If it isn't there, try using search, and if you find another one somewhere else then try editing that one. A simple matter, but apparently easily missed

xWhiskey said:
Check if your ROM has a dual build.prop file. If one exists in system/bin, you ought to edit that one for the change to stick. This solved the issue for me, and might solve it for you.
If it isn't there, try using search, and if you find another one somewhere else then try editing that one. A simple matter, but apparently easily missed
Click to expand...
Click to collapse
I'm here to wake this thread up, because I'm having this same issue and I can't seem to find any duplicate build.prop file...
Anyone having a good suggestion for me please give it, all assistance is welcome.
Android version 4.4.4
Galaxy Note Edge
Sent from my SM-N915P using Tapatalk 2

me too have the same problem , please some dev or expert help with these problem

You install root explorer and mount as r/w and copy the build.prop into your sd card (the unmoded one) and connect your phone to your pc and turn on usb copy file transfer or something like that. In your pc go into your sd and open your copied build.prop with notepad and mod it as you like. After that go into your root explorer and replace it with your original build.prop. Try on not bricking your phone bcz i bricked mine like that when i put a lot mods on it haha, make a cwm backup or if you know how to unbrick it in every case Hope i helped
Be sure its mounted as r/w otherwise you will not be able to do anything to system files.
Use the original root explorer or Andro Zip is recommeded by me
Sent from my GT-S5830i using XDA Free mobile app

Are you setting the file permissions correctly as rw-r--r-- ??

[/COLOR]
flexton said:
You install root explorer and mount as r/w and copy the build.prop into your sd card (the unmoded one) and connect your phone to your pc and turn on usb copy file transfer or something like that. In your pc go into your sd and open your copied build.prop with notepad and mod it as you like. After that go into your root explorer and replace it with your original build.prop. Try on not bricking your phone bcz i bricked mine like that when i put a lot mods on it haha, make a cwm backup or if you know how to unbrick it in every case Hope i helped
Be sure its mounted as r/w otherwise you will not be able to do anything to system files.
Use the original root explorer or Andro Zip is recommeded by me
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
samsungrockz said:
Are you setting the file permissions correctly as rw-r--r-- ??
Click to expand...
Click to collapse
thank u for answering but sorry guys to say this , it's not the way of editing it , or the permission , when i make changes they are saved correctly and the device apply the changes in the start of the first boot after these changes are made , but during the boot (after applying the changes) the device restore the stock build.prop , so when the device finishes boot up the changes are applyed but the build.prop (i cheked it) is back to stock , this mean another boot & the changes are gone , :crying: :crying: no matter how many times or changes u do they are applyed only for the first boot after they are made

Maybe it has some stock security feed, try to go to custom roms i dont now what else can you do
Sent from my GT-S5830i using XDA Free mobile app

flexton said:
Maybe it has some stock security feed, try to go to custom roms i dont now what else can you do
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
it my first ported rom -porting by replacing files ,not expert work- and i'm having this problem

Kico.MMK said:
it my first ported rom -porting by replacing files ,not expert work- and i'm having this problem
Click to expand...
Click to collapse
Try finding your device on xda and look for a custom rom that someone more expirienced than you if it doesnt work i dont know what will
Sent from my GT-S5830i using XDA Free mobile app

flexton said:
Try finding your device on xda and look for a custom rom that someone more expirienced than you if it doesnt work i dont know what will
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
thanks for the advice , actually i did that but you know there is always something to be fixed :silly:

I have the same issue with my Vodafone Smart Ultra 6. I have root and system has read write access according to ES File Explorer. But any app that has root privileges, writes just fine without errors. However, if I close the app and load it again, or reboot, any changes are lost. So if I remove a system app using a root uninstaller it will say the app has been uninstalled. But it's still there. Drives me insane.

Exactly the same on the Smart Ultra 6.
Was hard enough to get it rooted but seems any changes to the system partition/file system just don't stick. Short of putting a custom rom on it I'm stuck for ideas.
I'd love to know what causes this behaviour.

Any updates here? I just started running into this after updating to the 7.1.1 January factory image on my 5x. The weird thing is when i reboot in TWRP it all looks fine but when I look at my system directory from Android the boot-from-recovery.p is still there and my build.prop changes aren't...push TWRP again, boot to recovery read build.prop and it's my edited version. wtf?

I have found a solution which works in my case.
Edit build prop using any root explorer and save it.
Now once again edit the file with different root explorer app like amaze or es explorer with some comment line like
#comment
and save it.
Now it should prevent the build prop from resetting after a reboot.

I have the same problem: after reboot all the changes are gone....
ashd63 said:
I have found a solution which works in my case.
Edit build prop using any root explorer and save it.
Now once again edit the file with different root explorer app like amaze or es explorer with some comment line like
#comment
and save it.
Now it should prevent the build prop from resetting after a reboot.
Click to expand...
Click to collapse
It's not working for me ☹
---------- Post added at 09:43 AM ---------- Previous post was at 09:30 AM ----------
Is it normal that my build.prop has the permissions -rw------ ?
This could be the problem.

ullie4404 said:
I have the same problem: after reboot all the changes are gone....
It's not working for me ☹
---------- Post added at 09:43 AM ---------- Previous post was at 09:30 AM ----------
Is it normal that my build.prop has the permissions -rw------ ?
This could be the problem.
Click to expand...
Click to collapse
Did you ever find the solution to this? I'm having the same problem..all changes reset with every reboot and the file's permission is like -rw-----

[Q] Multi-view Hack HELP!!

Can someone help me out with the Multi-view hack to add all apps?...I just used the editing method for adding all apps to the multi-view window. All the steps went fine, but now that I'm done I can't get Multi-view to work AT ALL! I enabled it, held the back button down over and over and it does absolutley NOTHING. I am on stock 4.1.1, rooted with unlocked bootloader and I have a nandroid backup that I made just before attempting this, but since everything else on my Note 2 is still working I'm waiting and hoping that someone out there knows what's going on and has a fix for it.
Here are the steps that I took:
----------------------------------------------------------------------------------------------------------------------------------------
1. Download modified odex file (multiwindow.zip) by hairdewx (mirror), and extract services.odex FlashBarService.odex files. After that copy both files into your device.
2. Get file manager app that can open the system apps, such as ES File Explorer or Root Explorer that can be found on Play Store.
3. Mount the system partition as Read/Write (R/W).Mount to R/W and Replace Files
4. Copy and replace “FlashBarService.odex” to “/system/app” folder, as well as “services.odex” to “/system/framework” folder. If you have difficulty to replace services.odex, reboot your device. In case you experiencing bootloop after replacing services.odex, then you need to pull out and reinsert the battery, if the bootloops remains, just flash the root image with ODIN to fix it.
5. Reboot your Galaxy Note II.
6. Open the file manager again, delete “com.sec.android.app.FlashBarService” from “/data/data” folder, then reboot once again.
7. (Optional) Open “/data/data” folder again, if you find the “/flashbar” folder, just delete it.
Now you should have been able to add any apps to the Multi Window bars on Verizon Galaxy Note 2, and also run two applications at the same time (MultiView). If you can’t find an edit button, it’s likely that you on 240 DPI, just switching back to 320 DPI, edit button will reappears.
-----------------------------------------------------------------------------------------------------------------------------------------
That's it. I did all of these steps with no problems but as mentioned, now I can't get Multiview to work at all. I have tried restarting several times and also did a battery pull but no luck. Please HELP!
Edited...PROBLEM SOLVED AFTER FACTORY DATA RESET. Thanks.

Tethering on At&t Stock 4.4.2 Software Version D85010f

Is there a way to get tethering to work without using something like FoxFi?
I tried the method posted here: http://forum.xda-developers.com/lg-g3/general/enable-tethering-lg-g3-d850-t2814367 but I have a different settings.db file with no tether_entitlement_check_state.
The same was true when I tried on version D85010d.

jiexi said:
Is there a way to get tethering to work without using something like FoxFi?
I tried the method posted here: http://forum.xda-developers.com/lg-g3/general/enable-tethering-lg-g3-d850-t2814367 but I have a different settings.db file with no tether_entitlement_check_state.
The same was true when I tried on version D85010d.
Click to expand...
Click to collapse
root and mod the flags
In your SQLite Editor, click on the FILES tab and look for the path: /data/data/com.android.providers.settings/databases/SETTINGS.DB/SYSTEM
DO SEARCH OF SYSTEM FOR ‘TETHER’
I HAVE ‘TETHERING TIME 600000, CHANGE TO 0
I HAVE TETHER ENTITLEMENT 5, CHANGE TO 0
this came from xda. i keep it handy in a note
did you make sure to first run the tether setup first, before doing the mod? that puts the entries into the correct file.

Yes I did run the tether first for it to initialize the file, as per the instructions.
I was able to find the two values and changed them both. However after I restarted my phone it went into a boot loop.
I flashed a recovery and then tried just changing tether_entitlement to 0, but the same thing happens.
Is there anything else I should try?

Also, there were some things I noticed and I'm not sure if they make a difference.
1)
instead of having the directory path
data>data>com.android.provider.settings>system>databases>settings.db
I have just
data>data>com.android.provider.settings>databases>settings.db
2)
SQLite Editor does not have root access. It never prompts me to give root access, nor do I see a way to manually grant it through SuperSU.
However, other apps like Root Browser were prompted and do have root access.
I did a work around by copying settings.db to sdcard to change the values, then copying it back.
Any more help will be greatly appreciated.

jiexi said:
Also, there were some things I noticed and I'm not sure if they make a difference.
1)
instead of having the directory path
data>data>com.android.provider.settings>system>databases>settings.db
I have just
data>data>com.android.provider.settings>databases>settings.db
2)
SQLite Editor does not have root access. It never prompts me to give root access, nor do I see a way to manually grant it through SuperSU.
However, other apps like Root Browser were prompted and do have root access.
I did a work around by copying settings.db to sdcard to change the values, then copying it back.
Any more help will be greatly appreciated.
Click to expand...
Click to collapse
after you make the changes to the file, make sure you set the permissions or you will boot loop

JeffDC said:
after you make the changes to the file, make sure you set the permissions or you will boot loop
Click to expand...
Click to collapse
I ended up using another database editor, but that was most likely the problem.
Thanks.

jiexi said:
I ended up using another database editor, but that was most likely the problem.
Thanks.
Click to expand...
Click to collapse
Yes., exactly. You must use and editor which can handle the entire file, and not truncate the file when you save it. I use 920 text editor

[GUIDE]How to fix Wi-Fi not connecting/forgetting network

-Warning-
This was only tested by me yet, worked like a charm in my SM-G935F from Brazil with
Android MM 6.0.1
Build Number: MMB29K.G935FXXU1BPLB
Do it at your own risk​
Well, since I rooted my S7 Edge, I noticed that it's Wi-Fi wasn't working right, it didn't save the networks I had previously connected, and took a lot of time to recognize the networks when you turned on Wi-Fi, and after searching and searching for a while, finally found out how to fix it.
Requirements
- Phone must be rooted.
- Es File Explorer(you can download it on Play Store or download the .apk file)
I used ES File Explorer because it's easy to enable Root Explorer, but you can use any other file explorer if you want(since it enable you to use Root Explorer)
It's a easy process, but you need to be careful because any pass you follow incorrectly can brick your device(I guess).
So once you installed ES File Explorer, open it and click on the menu(upper left side), scroll down and enable the Root Explorer option, then go to your internal storage main folder(" / "), scroll down and enter the system folder, in this folder, you will find a txt archive named "build.prop", backup this archive, open it and tap options then edit.
You will:
1. Find the line "ro.securestorage.support=true";
2. Change true to false;
2. Save in the system folder;
3. Reboot the phone.
PS: If you haven't enabled the Root Explorer option, you will not be able to save the file.
If it don't work, replace the build.prop archive you backed up previously in the system folder.

Nice guide. But it probably won't work on Nougat, you need to replace secure storage libs with ones from Superkernel.

kykint said:
Nice guide. But it probably won't work on Nougat, you need to replace secure storage libs with ones from Superkernel.
Click to expand...
Click to collapse
Appreciate you like it!
Yeah, already expected that, but as I said, I only tested it with MM, still waiting for the official release of Nougat for my region.

guuimauricio said:
Appreciate you like it!
Yeah, already expected that, but as I said, I only tested it with MM, still waiting for the official release of Nougat for my region.
Click to expand...
Click to collapse
Nougat still hasn't been released in your region? jesus... Work, Samsung!

Delete

I want know the KNOX 0*1 how to fix 0*0. or use xposed hide it! let my phone look at no fusing. tks!