Database Info

[Q] white settings menu

Hi guys, been using this great phone.for.2 months already. Used a couple of roms in the past but returned to rooted, locked bootloader stock rom with the latest update. I just had a question is it possible to make the settings menu white witout being deodexed? Or at least without modification of system files. Please.note I do not have any sort of recovery installed. Just rooted so I can use greenify and Uninstal bloatware. I really like the white menu, been searching and only foind it in custom.roms. anyway I can do that on stock? thanks in advance. I've decided to.use.stock as I could.find lots.of.bugs.on the.custom roms. Aand.I really like the stock ui. ANY advice?

Hey mate, sorry to inform you but I think you have to deodex. However I think there is another way, I understand you prefer clean stock rom, I can't unlock my bootloader and it is indeed the fastest rom do the following, search on the themes and apps for Honami white settings and you will find a port that even has cpu control.
Go to your apps folder (use root Explorer); delete your settings and settings.odex, and now copy the files you downloaded from the port and copy them with correct permissions. Then reboot and I think you are all done. Also search for an app or way do delete your cache, including dalvik so you avoid errors. I'm thinking about doing this myself so try it and tell me if something went wrong so I can help

Missing Wifi Calling in settings

I seem to be missing the wifi calling settings in my phone. (it should be above the Wifi Settings, but it is not). I tried following the steps here: http://forum.xda-developers.com/galaxy-s6-edge/general/quick-guide-enabling-hidden-features-t3087506
and added the xml line in features.xml (i added it inside the features block, i'm sure i did it correctly). restarted the phone, and nothing. I am stock rooted, using ping pong root, with no modifications. (i only needed root to restore google authenticator, which i can't be bother to reset all my totp tokens..a bit annoying there's no way to restore them)
anyway, any reason why i don't have the option to begin with? or why i can't seem to enable it?
Any help would be amazing. thanks.

I had the same problem a long time ago. Didn't have the option and was messing with the features. xml folder to no avail. What I ended up doing was flashing stock firmware and basically copy and paste the XML file to my backup. That worked for me

Can't edit build.prop

I've lost the ability to change DPI all of a sudden. I had no problems at all,but I installed a cm based rom, changed DPI on that fine, but afterwards I moved to a stock based rom and I haven't been able to change since.
Texdroider says it will be changed but doesn't apply after boot, and when I try to edit the build.prop, it says it can't save.
Tried to edit permissions but not won't allow me.
Restored to a flashable stock rom, still the same.
Restored to a UK ftf file, still the same.
Seriously run out of ideas, so I come to you for help...

reanimatednerd said:
I've lost the ability to change DPI all of a sudden. I had no problems at all,but I installed a cm based rom, changed DPI on that fine, but afterwards I moved to a stock based rom and I haven't been able to change since.
Texdroider says it will be changed but doesn't apply after boot, and when I try to edit the build.prop, it says it can't save.
Tried to edit permissions but not won't allow me.
Restored to a flashable stock rom, still the same.
Restored to a UK ftf file, still the same.
Seriously run out of ideas, so I come to you for help...
Click to expand...
Click to collapse
Try to isolate the problem :
- recovery running ok?
- root (SuperSU) ok?
- can mount /system RW in recovery?
- can mount /system RW in shell (adb or terminal) when booted?
Sent from my D6603 using Tapatalk

reanimatednerd said:
I've lost the ability to change DPI all of a sudden. I had no problems at all,but I installed a cm based rom, changed DPI on that fine, but afterwards I moved to a stock based rom and I haven't been able to change since.
Texdroider says it will be changed but doesn't apply after boot, and when I try to edit the build.prop, it says it can't save.
Tried to edit permissions but not won't allow me.
Restored to a flashable stock rom, still the same.
Restored to a UK ftf file, still the same.
Seriously run out of ideas, so I come to you for help...
Click to expand...
Click to collapse
Try using this app to edit build.prop: Root Explorer.

Doesn't flashing a stock rom lose root?

heywheelie said:
Doesn't flashing a stock rom lose root?
Click to expand...
Click to collapse
Of course it does, if you don't flash already pre-rooted one in recovery.

ondrejvaroscak said:
Of course it does, if you don't flash already pre-rooted one in recovery.
Click to expand...
Click to collapse
that was my point. The OP flashed a stock rom then wondered why he couldn't edit the build.prop file. He needs root to edit that file.

Modify system then unroot

I'm trying to make modifications to the system such as moving an app to system Adblock and edit for hotspot. But when I unroot by flashing another kernel these changes are lost. What am I missing?
At the end of the day I wants my mods to be applied to system but not be rooted.

Anyone with any ideas?

build.prop modification caused loss of root, now stuck with bad build.prop

Hello,
I have a rooted Samsung Galaxy Note 3. I was experimenting with the build.prop file, having made a backup of the original version of it. After making some changes to the build.prop file and rebooting the device, the vast majority of the apps stopped working and what is worse, I somehow lost my root access. My original plan was to revert to the original version of the build.prop file if things didn't work as expected but now all I have is read-only access to the /system folder and I can't edit the build.prop file or replace it with the backup of the original I made. I also tried accessing the filesystem via an adb shell, but I still only get read-only access to the system areas. The problem is now 95% of my apps crash before they even start and I can't even run SuperSU, or playstore. I have Total Commander installed, and it is one of the very few apps that work, but again, I only get read-only access to the system area. All I need to do is delete the problem build.prop file and rename the backup file oldbuild.prop file, but how do I re-gain read/write access to the /system folder??
I would truly appreciate any help, ideas or advice
Thanks a lot
PS. I do not have a custom recovery installed. Just the Samsung stock recovery

memrah said:
Hello,
I have a rooted Samsung Galaxy Note 3. I was experimenting with the build.prop file, having made a backup of the original version of it. After making some changes to the build.prop file and rebooting the device, the vast majority of the apps stopped working and what is worse, I somehow lost my root access. My original plan was to revert to the original version of the build.prop file if things didn't work as expected but now all I have is read-only access to the /system folder and I can't edit the build.prop file or replace it with the backup of the original I made. I also tried accessing the filesystem via an adb shell, but I still only get read-only access to the system areas. The problem is now 95% of my apps crash before they even start and I can't even run SuperSU, or playstore. I have Total Commander installed, and it is one of the very few apps that work, but again, I only get read-only access to the system area. All I need to do is delete the problem build.prop file and rename the backup file oldbuild.prop file, but how do I re-gain read/write access to the /system folder??
I would truly appreciate any help, ideas or advice
Thanks a lot
PS. I do not have a custom recovery installed. Just the Samsung stock recovery
Click to expand...
Click to collapse
The solution would be flashing twrp, then using its build in terminal or adb shell to replace the infected build.prop

-Hope- said:
The solution would be flashing twrp, then using its build in terminal or adb shell to replace the infected build.prop
Click to expand...
Click to collapse
Thanks for your answer. I did manage to revert to the correct build.prop file and get rid the bad one. For some reason though, when I restarted my phone it is now getting stuck at the Samsung logo screen with a pulsing blue status LED. I know for a fact that the build.prop file is the correct/original one. So I'm clueless about what might be causing it to get stuck during boot. Any ideas or suggestions? Thanks in advance.

memrah said:
Thanks for your answer. I did manage to revert to the correct build.prop file and get rid the bad one. For some reason though, when I restarted my phone it is now getting stuck at the Samsung logo screen with a pulsing blue status LED. I know for a fact that the build.prop file is the correct/original one. So I'm clueless about what might be causing it to get stuck during boot. Any ideas or suggestions? Thanks in advance.
Click to expand...
Click to collapse
Clear cache

-Hope- said:
Clear cache
Click to expand...
Click to collapse
-Hope-, Thanks a lot for your help. I tried clearing the cache, didn't work. Tried a factory reset via Recovery mode, didn't work, so I think I will need to flash the ROM. Do you know where I can download a stock factory ROM for the Note3 that is unmodified and not tampered with (malware free), just the way Samsung released it?
Once again, thanks a lot for your help

memrah said:
-Hope-, Thanks a lot for your help. I tried clearing the cache, didn't work. Tried a factory reset via Recovery mode, didn't work, so I think I will need to flash the ROM. Do you know where I can download a stock factory ROM for the Note3 that is unmodified and not tampered with (malware free), just the way Samsung released it?
Once again, thanks a lot for your help
Click to expand...
Click to collapse
Updato.com
Sammobile.com < official site

Thanks. I flashed my Note3 with stock Lollipop ROM downloaded from Sammobile.