Database Info

[Q]Galaxy S5 Problem

First off, I want to apologize if I've put this in the wrong place or if something is not in accordance to the rules for posting. I am new to this website and have a bugger of a problem. I would like to edit something in my galaxy S5's SM-G900A settings.db file, but understand being rooted is required to do this. I decided I wanted to too late, and now lollipop and my phone model are the reason that there is not any sort of root for my phone at the moment. I am not willing to backup, downgrade, root, edit, then use a special thing to update to lollipop keep root access. I have read of ADB and JVM and was wondering if anyone could tell me of any way I could gain access to and edit my phones settings.db file on lollipop without rooting, I know JVM and ADB may be viable but I know nothing of how to. Any other methods or suggestions are welcome. Thanks for reading this!

[Q] How to root Acer Iconia A1-713 manually?

Has anyone created a method to root Acer a1-713 manually?
Those one click methods are really crude also I don't even know what's happening in there.
If anyone knows it please help me.

Dreadful man said:
Has anyone created a method to root Acer a1-713 manually?
Those one click methods are really crude also I don't even know what's happening in there.
If anyone knows it please help me.
Click to expand...
Click to collapse
Some said that Kingroot worked for them in this Q&A thread -> http://forum.xda-developers.com/chef-central/android/root-recovery-acer-iconia-tab-7-a1-713-t2851573

JnFrks said:
Some said that Kingroot worked for them in this Q&A thread -> http://forum.xda-developers.com/chef-central/android/root-recovery-acer-iconia-tab-7-a1-713-t2851573
Click to expand...
Click to collapse
Well it didn't for me. Also I want to know what I am doing with my tab and not just know that tapping this button will root my tab.

Have you ever tried to look at this site -> http://www.oneclickroot.com/device/acer-iconia-a1-713/. They featured this one-click rooting and it seems they can be trusted. I've downloaded and installed their software so no worries. Well, I'm also using a one-click root utility and it's always working. (just sayin')
The process of rooting a device is too complicated for those who don't have knowledge in Linux (like me), so your question about manually is out.
http://www.oneclickroot.com/device/acer-iconia-a1-713/

Well this one click root website was also a waste of time and didn't work either .
I may have to wait a little bit more before dumping this thread.

Rooting an android device basically means (for me) granting You (as the user) to do whatever you want to your device's system, hardware, etc. But what does root will actually do to your device that will cause you to obtain that superuser access? It's because of the "su" (Switch User) file used by Android and other UNIX-based systems that allows a process of switching of a user to be the superuser (or root user) that has access to the commands and file system, meaning those processes that requires root permission (root access or superuser access) need to invoke su. So basically the process of rooting will just push this su, a binary executable file, to the file system so that you can switch to the root user to give root permissions... And the Superuser application is just optional, but really required for some reasons, it serves as the "gatekeeper" of the su binary so when a certain command or application that invokes su will prompt the user by the Superuser app first before granting the root permission since becoming the root user can do whatever to the system which means it can cause the device to malfunction, etc... So what do you mean by manually?
Sorry for what I'd just suggest you that OneClickRoot waste your time...
Oh, there's a bad news after spending time searching how to root your device, read the news here -> [GUIDE] Firmwares, ROMs, CWM, Root - Acer Iconia (MTK) Tablets [ⒶⒸⒺⓇ ⒹⒺⓋⒾⓁⓈ]
Can't find a best way to root your Acer.

Well thanks for enlightening me on the topic, I hadn't really understood what really is su..
By manually I meant by using computer and tinkering with the files hands on.
Oh, and you needn't to be sorry since everything I tried didn't work. Sometimes I had root till the app was open while sometimes it existed until the next reboot.
Also looked at the link you gave and well, what can I say, it really is bad news and there sure is the risk of bricking my device.
Well thanks for taking your time.

[Completed] Need some help regarding manual rooting using ADB to place the files. ReRooting phone

Okay so I've had this phone for little over 10 months now and within that time I've managed to achieve root (unreliable but it works at the very least) in that time as well as learned a fair amount about Linux and android alike (Not a whole lot but I know some stuff) though I've now come to the point of I actually want to give my phone a proper root instead of this faulty solution I have currently. I (barely) managed to get my phone rooted using Kingoroot and I've played plenty with my phones' innards in that time, removed system apps, added my own selection to the system but some apps in my phone that use root don't work even with root permission granted which is why I'm wanting to replace Kingoroot with ChainFires' SuperSU binaries, could anybody help me with simple instructions for someone who doesn't actually know very much regarding how root and SU bins work inside of android? My phone's using 4.4.2 kitkat.
Just a few disclaimers first to get misconceptions out the way:
1. I do not have a custom recovery nor is one available for my phone (Samsung galaxy young 2 (SM-S130H) for those who want to know)
2. I'm currently unable to use the internet on my phone as I lack Wi-Fi to do so (router is dead) so I'm manually installing app packages through ADB, so if something needs an internet connection on my phone it's not going to work for me, for now..PC still has net access.
3. I have access to ADB shells' SU but not ADB root so I hope you don't need that from me.
4. This phone does not have a fastboot mode. (That I can find anyway..) Only a download mode from what I've found.
Can anybody help me out with telling me what I'll need to be doing in regards to getting this done?

Hi Mc Fow1er
Thank you for using XDA Assist
As we do not have an specific forum dedicated for your device yet, our experts at the below forum should be able to help you. Please be welcome to post over in there.
Android Q&A, Help & Troubleshooting
Nice regards and good luck.
.
Mc Fow1er said:
Okay so I've had this phone for little over 10 months now and within that time I've managed to achieve root (unreliable but it works at the very least) in that time as well as learned a fair amount about Linux and android alike (Not a whole lot but I know some stuff) though I've now come to the point of I actually want to give my phone a proper root instead of this faulty solution I have currently. I (barely) managed to get my phone rooted using Kingoroot and I've played plenty with my phones' innards in that time, removed system apps, added my own selection to the system but some apps in my phone that use root don't work even with root permission granted which is why I'm wanting to replace Kingoroot with ChainFires' SuperSU binaries, could anybody help me with simple instructions for someone who doesn't actually know very much regarding how root and SU bins work inside of android? My phone's using 4.4.2 kitkat.
Just a few disclaimers first to get misconceptions out the way:
1. I do not have a custom recovery nor is one available for my phone (Samsung galaxy young 2 (SM-S130H) for those who want to know)
2. I'm currently unable to use the internet on my phone as I lack Wi-Fi to do so (router is dead) so I'm manually installing app packages through ADB, so if something needs an internet connection on my phone it's not going to work for me, for now..PC still has net access.
3. I have access to ADB shells' SU but not ADB root so I hope you don't need that from me.
4. This phone does not have a fastboot mode. (That I can find anyway..) Only a download mode from what I've found.
Can anybody help me out with telling me what I'll need to be doing in regards to getting this done?
Click to expand...
Click to collapse

[Completed] about non rooted devices

hi guys,
first, i m all time thankful to these developer guys, you make mobile world so genius, yeah it was never genius,
second, something i learn and something i want to learn more is about android always, but here is my question below that is really important. i don't know if it really make sense or not but i would like to know your opinion.
question :- i see there is a way to push files into device without rooting it. is it secure? it is safe? i guess yes. than how can i push titanium backup(data only) of particular app into my device?
example : - i myself after learning lot about apk tool and all that, modded "whatsapp" successfully and which is out of this world according to me, lately i cam to know there is already one called whatsapp GB, but mine is mine. (right now i don't have rooted device so couldn't send screenshot), but what i am trying to figure out is, i can install my modded apk on my non-rooted device and can run it either, problem comes when it is about registering number, what i really thought that if i can push titanium backup of my modded whatsapp.apk (data only - taken perviously when i had rooted device) to this non rooted device via ADB, than i didn't need to root my device ever, and so for any other app that is modded by me or any developers can be executed on non rooted device.
pros - if this is possible than i guess People won't need to root device, will not loose warranties, will not loose device by bricking it, will get out of a procedure of root methods, no one will ask more about root method, soft brick, hard brick, boot loader issues and many more questions like that i guess.
there will left only one tutorial than if this is possible and it will be like this - how to use adb?(step by step : beginner to black hat).
if this is possible than what we need? proper method of how to use adb, most of people easily can learn how to use adb but most of tutorial misses some points like how to push file by changing r/w permission, and where to put new data backup or files in device like some tutorial i have seen gives only command line but people actually don't know where to put the file like /data/data and than what?
Developers and Rooted device owner will become God in fact in this case because they can lead the rest in right path.
is this possible? or am i ridiculously making no sense?

joy.julep said:
hi guys,
first, i m all time thankful to these developer guys, you make mobile world so genius, yeah it was never genius,
second, something i learn and something i want to learn more is about android always, but here is my question below that is really important. i don't know if it really make sense or not but i would like to know your opinion.
question :- i see there is a way to push files into device without rooting it. is it secure? it is safe? i guess yes. than how can i push titanium backup(data only) of particular app into my device?
example : - i myself after learning lot about apk tool and all that, modded "whatsapp" successfully and which is out of this world according to me, lately i cam to know there is already one called whatsapp GB, but mine is mine. (right now i don't have rooted device so couldn't send screenshot), but what i am trying to figure out is, i can install my modded apk on my non-rooted device and can run it either, problem comes when it is about registering number, what i really thought that if i can push titanium backup of my modded whatsapp.apk (data only - taken perviously when i had rooted device) to this non rooted device via ADB, than i didn't need to root my device ever, and so for any other app that is modded by me or any developers can be executed on non rooted device.
pros - if this is possible than i guess People won't need to root device, will not loose warranties, will not loose device by bricking it, will get out of a procedure of root methods, no one will ask more about root method, soft brick, hard brick, boot loader issues and many more questions like that i guess.
there will left only one tutorial than if this is possible and it will be like this - how to use adb?(step by step : beginner to black hat).
if this is possible than what we need? proper method of how to use adb, most of people easily can learn how to use adb but most of tutorial misses some points like how to push file by changing r/w permission, and where to put new data backup or files in device like some tutorial i have seen gives only command line but people actually don't know where to put the file like /data/data and than what?
Developers and Rooted device owner will become God in fact in this case because they can lead the rest in right path.
is this possible? or am i ridiculously making no sense?
Click to expand...
Click to collapse
Hello,
Please post your query here Ask any Query Newbie Friendly with all relevant details, the experts there maybe able to assist you.
-Vatsal

samsung galaxy s9 root android 10 exynos

Hello, is there a way to root the phone where everything works now (Bluetooth, Face ID, etc.)?

I would very much like to see this answered. I've seen some application-specific instructions such as this reddit thread for enabling Samsung Health, and I've read about hiding the fact that the phone is rooted from apps by using MagiskHide, but it's not clear whether this works for all apps and features or just some. There's also this recently updated guide to rooting that claims:
Magisk is a highly advanced way of rooting android systemless-ly. This means that Magisk root android without changing or modifying the system partition. Hence you can receive OTA updates, run apps that require to pass Google’s SafetyNet tests.
Click to expand...
Click to collapse
However, many hacks that sound good when you read about them in advance run into snags and gotchas once you actually get into implementing them, and I'm hesitant to just give it a try and see how it works out when tripping Knox is irreversible and if things stop working you can't get them back by flashing the stock ROM.
I'd be grateful if anyone who has actual experience on this subject could vouch for being able to re-enable all lost functionality after rooting or to not lose it in the first place, or whether even some lost functionality can be enabled (and if so, what have you been able to get working and what haven't you? I don't know about OP, but to me the most important ones are Secure Folder and Samsung Health).
Also, does anyone have experience with retaining Knox-sensitive functionality on rooted S9 Exynos with Android 11 (either rooting after upgrading to 11, or rooting first and retaining root when upgrading)?

@bis225
IMO noone needs Magisk to root a device's Android. Rooting Android means having the SU-binary present on Android - a ~100KB file - nothing else. Copying SU-binary onto Android allows you to temporariy give you root access when needed.

jwoegerbauer said:
@bis225
IMO noone needs Magisk to root a device's Android. Rooting Android means having the SU-binary present on Android - a ~100KB file - nothing else. Copying SU-binary onto Android allows you to temporariy give you root access when needed.
Click to expand...
Click to collapse
I'm not sure I understand what you're saying. Are you telling me that you can simply copy the file onto an unrooted phone, and voila, you can gain root access?? Can you point to information about what to do and how this works? It runs contrary to everything I've ever read on the subject.
To the best of my understanding, in order to install su binary unto an unrooted phone you need to install a custom recovery, and use that to flash the su binary onto the phone. I thought the idea of Magisk was to provide root access without modifying system files so that SafetyNet can't detect that the system has been modified. Unless I'm missing something there's no disadvantage to rooting with Magisk, only advantages, but regardless, I don't see how it makes a difference with respect to this topic. Installing a custom recovery is what trips Knox and prevents some features and apps from working, so it doesn't really matter what root method you use if you have to use a custom recovery to install it.
If you know of a way to root a Galaxy S9 without using a custom recovery or tripping Knox and that can't be detected by SafetyNet, please elaborate.

Rooting Android simply means to add a ( hidden ) user called root ( AKA super-user ) who has ALL rights to Android's file system.
For example from within ADB you activate this user and let run him any command what requires to have ALL rights - assumed the SU-binary is located in /sdcard
Code:
adb shell "/sdcard/su -c '<command-here>'"
AFAIK Magisk installs the SU-binary in /data/adb/magisk/busybox, but I may err.

@jwoegerbauer
But I didn't ask what rooting means. Unfortunately, this doesn't answer any of my questions.

I think I clearly expressed that neither a Custom Revovery nor Magisk itself is needed to have root, that simply copying SU-binary to Android's user-space is enough.
If you want to root via Magisk then do it.
Personally never would do it this way.

jwoegerbauer said:
I think I clearly expressed that neither a Custom Revovery nor Magisk itself is needed to have root, that simply copying SU-binary to Android's user-space is enough.
If you want to root via Magisk then do it.
Personally never would do it this way.
Click to expand...
Click to collapse
This really seems contrary to everything I've read, and this Stack Exchange thread specifically explains why that wouldn't work, but if you say you have experience with this and it works for you, I'm certainly willing to give it a try and see how far it gets me. Do you know where a copy of the su binary can be obtained? All my searches for su binary lead to the supersu APK and instructions for installing it by flashing, or something along those lines. I can't find an su executable that can just be copied to internal storage as-is anywhere.