Summary: Started root, didn't complete it (?), then update downloaded.
I began root process last night--my first try--using Towelroot. When I pressed the "Make it Rain" button, I got an error message that my device was not supported (I don't recall the exact words). Using Android 4.4.4.
I've not found a way to continue this, although I see some alternate methods in another thread.
What is apparently going to be a 2-hour over Wifi update from AT&T, is in process. Are there any problems regarding this and proceeding with the root process?
halfmybrain said:
Summary: Started root, didn't complete it (?), then update downloaded.
I began root process last night--my first try--using Towelroot. When I pressed the "Make it Rain" button, I got an error message that my device was not supported (I don't recall the exact words). Using Android 4.4.4.
I've not found a way to continue this, although I see some alternate methods in another thread.
What is apparently going to be a 2-hour over Wifi update from AT&T, is in process. Are there any problems regarding this and proceeding with the root process?
Click to expand...
Click to collapse
You started two threads asking the same question and your answer is in the AT&T General threads
http://forum.xda-developers.com/showthread.php?t=3076803
I did not start two threads with the same question. They were related but distinct., and the second one quoted the first for CONTEXT but the question was different.
They both regarded partial root. One regarded the major upgrade [4.4.4 --> 5.0], the other regarded an SD card. Thanks, and I will look where you pointed me and hope the answers are specific, like my questions were.
OPOfreak said:
You started two threads asking the same question and your answer is in the AT&T General threads
http://forum.xda-developers.com/showthread.php?t=3076803
Click to expand...
Click to collapse
OPOfreak said:
You started two threads asking the same question and your answer is in the AT&T General threads
http://forum.xda-developers.com/showthread.php?t=3076803
Click to expand...
Click to collapse
I do not see answers to my questions in General AT&T. I'm new here, but I am trying to follow basic forum etiquette. 1. Only one question initiated per thread. 2. Post to the forum that fits best. I feel my post fits under troubleshooting. I'm not just asking out of curiosity, I've put myself into two corners (as I see it). One is, partially rooted my phone then updating my software. The other is, how is my SD card related to the root--should it be (have been) installed prior to my attempt to root. I am here combining my issues in one post to show my belief that they are troubleshooting issues AND I need help before I proceed.
Perhaps there's an underlying question, and I hope I get some feedback. Have I indeed partially rooted, if I got as far as Towelroot's "Make it Rain" command but (not supported) it did not go further? Thanks so much in advance, I'm sure "newbie" would be a compliment.
halfmybrain said:
I do not see answers to my questions in General AT&T. I'm new here, but I am trying to follow basic forum etiquette. 1. Only one question initiated per thread. 2. Post to the forum that fits best. I feel my post fits under troubleshooting. I'm not just asking out of curiosity, I've put myself into two corners (as I see it). One is, partially rooted my phone then updating my software. The other is, how is my SD card related to the root--should it be (have been) installed prior to my attempt to root. I am here combining my issues in one post to show my belief that they are troubleshooting issues AND I need help before I proceed.
Perhaps there's an underlying question, and I hope I get some feedback. Have I indeed partially rooted, if I got as far as Towelroot's "Make it Rain" command but (not supported) it did not go further? Thanks so much in advance, I'm sure "newbie" would be a compliment.
Click to expand...
Click to collapse
If you pressed make it rain and then it said device not supported you're not rooted
Not sure? Download Root checker from Playstore
Good afternoon I bought a Nexus 6 but unfortunately has over the version 7.0 and I would like to put over the older the 5.0 lollipop that I could do that by step guide?
This is a developer web site NOT a hold my hand and teach me everything for free website
Learn about your phone, and you will see how to do it
Short answer: You will need to download the appropriate image found here: https://developers.google.com/android/images and use the "fastboot" command (with the phone in bootloader mode) to flash everything EXCEPT the older bootloader.
@wase4711 - A bit harsh on your answer.... The OP did ask in the appropriate forum in which the top sticky states: "This is a noob-friendly thread, so ask whatever you like"
@jbaumert: He asked in the appropriate forum, but made his own thread rather than post his question in the Noob-friendly Q and A thread. Thus he is fair game.
As for the OP, some of us don't spoonfeed here. Read, read some more, and take time to understand things before you attempt to modify the device. Otherwise you could end up with a shiny paperweight.
Why though?
Marshmallow > Nougat > Lollipop
I GUARANTEE you, the OP has NO CLUE as to what he is doing, nor will he have any idea on how to use Fastboot, or any other commands..
and thanks, @Strephon Alkhalikoi for acknowledging that he did NOT ask in the "n00b friendly" thread..at least some of us left here still do read before they post:good::good:
I'm always baffled by people taking backward steps like this. It's normal that a newer version brings new features and better security, though I appreciate that some people have an understandable reason for the step back - better perceived battery life, for example, or Xposed not existing for the new build. But "I want to go back two steps" without stating any reason? Bizarre. @ccypruss000 - why?
Hello everyone
I have an s8+ and i have been trying to achieve System-Mode root on my S8+ with no luck, after flashing the supersu with SYSTEMLESS=FALSE option, it get stuck on the samsung boot animation
I have tried everything from flashing multiple SuperSU Versions to flashing custom Permissive Roms with no success, have anyone achieved this with the S8+ ?
My goal is the survival of the SU binaries after wipe
lastandroidgeek said:
Hello everyone. I have an s8+ and i have been trying to achieve System-Mode root on my S8+ with no luck,.....
Click to expand...
Click to collapse
I don't have this device but, I'm thinking that the your best bet is to take a look at the following thread and, if needed, post your question within it that's specific to your question.
https://forum.xda-developers.com/showthread.php?t=3286120
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
I don't have this device but, I'm thinking that the your best bet is to take a look at the following thread and, if needed, post your question within it that's specific to your question.
https://forum.xda-developers.com/showthread.php?t=3286120
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Yea i read all that thread previously, what they are saying basically is that System-Mode can't be achieved anymore, i even tried imaging the Boot partition with the SELinux patch after systemless root, reflashing SuperSU with system-mode then rewriting the backed up Boot partition and also had no success, it's really frustrating.
lastandroidgeek said:
Yea i read all that thread previously, what they are saying basically is that System-Mode can't be achieved anymore,......
Click to expand...
Click to collapse
Have you tried asking within one of the Root Guides located on the device dedicated area of the forum for the S8+?
Or even the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3586299
With the limited information here, maybe a member with this specific device may be able to provide you with some guidance.
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
Have you tried asking within one of the Root Guides located on the device dedicated area of the forum for the S8+?
Or even the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3586299
With the limited information here, maybe a member with this specific device may be able to provide you with some guidance.
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Just did that, thank you for your help
Ibuprophen said:
Have you tried asking within one of the Root Guides located on the device dedicated area of the forum for the S8+?
Or even the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3586299
With the limited information here, maybe a member with this specific device may be able to provide you with some guidance.
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Hey, i found a solution
After days of digging and searching and with no reply on other threads on xda i finally found the solution for anyone wondering how to achieve this,
1- First you have to have any custom rom and the reason for this is to have all stock security patches removed/disabled otherwise your SU binaries will survive root but when executing them after Factory Reset, it will just hang and won't execute
2- Flash your SuperSU with the following option executed in TWRP recovery as pointed out by "ChainFire"
Factory reset protection / survival
With the FRP setting enabled (default on the Pixel, manually enable by doing echo "FRP=true">>/data/.supersu in a root shell for other devices), systemless root will survive a factory reset (/data wipe). Note that any updates to the su binaries installed by Play Store updates to SuperSU will be lost.
3- After that, you can safely wipe your device and the SU binaries will survive without the SuperSU app, thus giving you SU execution without prompt
Thank you @Ibuprophen for the assistance
Hello everyone,
I have to say I am completely lost regarding the whole rooting process for the XZ1C. I usually manage to get where I want just by carefully reading the forums, but with this device, I feel overwhelmed by information. And I sometimes feel like what I am reading contradicts what I though I understood from previous reads...
I will try to sum up what I know so far.
First of all, I have a just-out-of-the-box Sony model G8441 with firmware 47.1.A.12.179 / Oreo 8.0.0 (never been connected to the outside world yet), and I want to properly root the device and install TWRP with no loss of feature.
What I think I understand:
To root, I first need to unlock the bootloader, which seems to be a trivial operation. However, this will break some functionalities due to DRM keys being erased. Once it is done, there is no way, ever, to get them back. There are however ways to "trick" DRM-related functionalities into believing DRM keys are still there.
Alternatively, there seems to be a way to backup the DRM keys prior to unlocking the BL, and this backup can somehow be reused and injected back into the unlocked device. If true, then this would certainly be a preferable method than the previous one, which would then be obsolete. However, it obviously doesn't look obsolete when I read the related topics, so I must be missing something...
Another thing I noted (but do not quite understand): There are ROMs for this device that "include" a DRM fix.
Last important thing I read: there is a paid "do-it-all" tool which takes my locked device and, with one click, makes it unlocked - rooted - DRM-fixed - TWRP-enabled. Now that sounds really good! Maybe too good?
As far as i know (but I learn new stuff every day on this topic) this DRM stuff is the main difficulty here. I understand that the rest of the process (root + TWRP) will be much simpler (although I'm old-school and completly missed all this magisk trend...!)
What I don't understand:
I read that some people downgrade to Oreo to be able to root properly, and at the same time, I read that Pie removed the restrictions on unlocked bootloader. So I still have no idea if I should connect and receive Sony updates, or avoid them.
Another thing I don't get, is how many ways do we have to root this thing? In the past, I was used to see, for a specific device, always one major and widly used rooting method. Here I fail to identify it...
What I think I will do:
1. Backup TA partition with j4nn's tool. This will probably imply flashing an older firmware right? Is there any link that could help me with this flashing process? (I only know Odin - did I mention old-school?) I saw this page for generic sony Z devices, but the thread is from 2013 and now closed. Is it still up-to-date or is there a newer thread?
2. Unlock bootloader and restore TA partition.
3. Wait for Sony updates? Or should I first hide unlock status?
3bis. Alternaltively to waiting for updates, maybe I can just flash the latest build? (47.2.A.8.24 if I am not mistaken)
4. Flash modpunk's TWRP.
5. Flash janjan's Boot.img to get root functionalities?
Alternaltively to all the above (except maybe step 1 that I will probably do in any case), buy the paid all-in-one tool (Xperifix), plug, click and wait... But will I really end up the same as with the manual way?
I saw a few other methods in the forums but it seems my brain is currently refusing to bring them back...
That's all I have right now. I would really appreciate if you guys could share some insight and tell me what you think about this, whether there are missing steps, useless steps, incorrectly ordered steps, silly steps, or if I'm just completely wrong about the whole thing.
Feel free also to correct me on the assumptions I made at the beginning.
Thank you very much for reading this repulsive piece of text.
SunJu22 said:
I would really appreciate if you guys could share some insight and tell me what you think about this
Click to expand...
Click to collapse
By the looks of it you have done a great deal of research on the project.
Yes, go down the route of backing up your TA partition first, but that is not a small step in itself, it's pretty complicated and if you get that working then the rest of the project will be a breeze.
You don't say what version of firmware you want to end up on. If you want to end up on Pie then forget the DRMfix . But if you're staying on Oreo and can't be bothered with lots of files & flashing, then this is the easy way out, I bought the paid version and can verify it works.
More recently I ended up janjan's kernel (Oreo build). Hidden root (Google Pay works), lots of performance tweaks, DRM completely working.
It's unlikely that anyone will bother making a DRM fix for Pie as the camera works and there are only a couple of other features that get disabled.
It sounds like you're not the sort of person who's only going to read the first couple of pages of a thread (or the last) flash the xxxxxx and then complain when it's broken.
The people on the forum here are very helpful and if you go into any of the threads you mentioned in your post with a question, you'll get a reply.
Good luck.
I agree, there is a lot of information out there and different methods of achieving what you want - very confusing if you have not been following the threads since the beginning.
In my opinion, the preferred method is j4nn's method outlined here: https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
Use that post as your main guide (the final step in that guide, #13, is how you will achieve root). You will use Newflasher to flash the various firmwares along the way (this is linked from j4nn's procedure in step #2). User munted made a very detailed pdf file that fills in some of the details on j4nn's procedure - see the following post and download the pdf attached: https://forum.xda-developers.com/showpost.php?p=78255334&postcount=382
Most of the other methods out there came before j4nn's work - they didn't include DRM backup/restore.
If you follow j4nn's procedure, you won't need to use the janjan kernel as you assumed - janjan method is different and does not overlap with j4nn.
SunJu22 said:
Feel free also to correct me on the assumptions I made at the beginning.
Click to expand...
Click to collapse
Sorry, I didn't point out that I was one of the early 'jumpers' who unlocked their bootloader without any backups, so I have been forced into always using fixes and all the information I have is based on having to fix your phone for it to work, but that's all changed now. I'm so out of date :-/
@camaro322hp is right, if you follow j4nn's method correctly you'll be rooted with no DRM loss. All of the other stuff is not required.
Thank you Digesteve and camaro322hp for your help.
From what I understand the XZ1C didn't get as much love as other devices, thus there was a long period of tinkering before a "do-it-all guide" could be considered "the" solution. That could explain all these different approaches that are proposed. Like you said camaro322hp it's rather difficult to jump on this train, and I can only guess how interesting this ride has been.
Anyway, I didn't see that the TA backup thread from j4nn also encompassed all the information I needed; I am glad to finally know that there is indeed a centralized "do-it-all guide" . To make it easier for XZ1C newcomers, I think j4nn should update his opening post to make this clearer.
Since I managed to grab the attention of 2 XZ1C power users, I would like to ask you: Did you keep stock? Did you try alternative ROMs? Do you like some of them? Do you prefer Oreo or Pie?
For information, the most up-to-date experience I have on a Android phone is my LG90 with CyanogenMod 11 (KitKat 4.4.4! Yes sir!). I heard that it's becoming less and less useful to flash a custom ROM due to major OS improvements, but I would still enjoy the simplest and lightest Android possible.
SunJu22 said:
Did you keep stock? Did you try alternative ROMs?
Click to expand...
Click to collapse
I've always been on stock, the camera is an important part of what I want from my phone and although there's lots of alternative camera apps, there's no competition to the stock camera app. Then I theme it black with swift installer and just uninstall or freeze any apps I don't want with Titanium Backup. I have stuck with Oreo, everything works perfect and I remember seeing so many people jumping to 9 then wanting to go back to 8 because they didn't like it. Something about changing the way the drop down menu works, among other things, but having never installed it, I'm not the person to comment on if it's any good or not.
I have been watching the XZ1c thread and Lineage is gaining ground, it even has a stock camera now. I would have thought something like that with miniGapps is going to be pretty lightweight and very similar to your carbon rom of before. At the moment this is based on 8, but is working well. Depends how keen you are to move to Pie.
Thank you Digesteve.
One thing I still don't understand. Part of the process is to hide unlock status. If I do this, FOTA will be applied and I will automatically end up on Pie, right? Should I skip this step if I want Oreo?
EDIT: when you say "a stock camera", you mean the Sony camera?
@SunJu22 I've stuck with the Sony ROM. A rooted stock ROM meets all my needs, so I've never felt the need to experiment with custom ROMs. There are some custom options out there that people seem fairly happy with, so if that's your thing, I'd encourage it.
Without going into too much detail, I'm still on Oreo for the moment, for a variety of reasons, but I don't know of anything that would keep me from recommending Pie.
One thing you should note is that once you unlock, there is no going back. AFAIK there is no known or working method to relock the bootloader.
SunJu22 said:
FOTA will be applied and I will automatically end up on Pie, right? Should I skip this step if I want Oreo?
EDIT: when you say "a stock camera", you mean the Sony camera?
Click to expand...
Click to collapse
Yes, I'm not entirely sure why having your rooted phone try and update itself is an advantage, but something I'd recomend avoiding.
Stock camera is the Sony camera, yes.
Thank you everyone, I believe I now have enough information to jump into this with confidence. The adventure begins, and will be reported in this thread for future reference, in the hope that it will help others like me!
Well, I am a bit sad... I wanted to report my "adventure" here in detail, but I'm afraid I have nothing to say.
Indeed, following the procedure from j4nn with a printed copy of munted's awesome guide, I managed to do all I wanted on the first attempt.
I don't have anything to add to this guide, everyone wanting to root their XZ1C can do it just by reading the opening post from j4nn and the mentioned guide. It takes a bit of time but nothing complicated thanks to the clear and detailed explanations.
I now have a fully functional rooted XZ1C (including camera) on Pie with Magisk root and TWRP.
Thank you all again from pointing me to the right direction.
I however have a slight disappointment. I wanted to start with Oreo and make an Nandroid backup before moving to Pie, but I didn't find Oreo builds on Xperifirm. So I jumped straight to Pie.
In case I want to test Oreo, I read that a downgrade is more complicated than an upgrade, but apart from the fact that a factory reset is needed for downgrade, I couldn't find an explanation for this. Any idea?
Last but not least: I looked for the latest Oreo build version number but couldn't find it. Do you guys know what it is and where I can download it?
I guess this will be all for this thread after this. Although it is very convenient to have my own thread to ask questions rather than finding the relevant page for each one, I don't want to annoy you too much...
EDIT: Please ignore the last question. I found out last Oreo build is 47.1.A.16.20, and I found the files via the download link in the opening post of the Lineage thread.
SunJu22 said:
In case I want to test Oreo, I read that a downgrade is more complicated than an upgrade, but apart from the fact that a factory reset is needed for downgrade, I couldn't find an explanation for this. Any idea? Lineage thread.
Click to expand...
Click to collapse
There is an easy solution to downgrade:
Newflasher
Hi, I've been thinking about rooting my XZ1c for a long time now. So, do I understand correctly that the ONLY disadvantage compared to non-rooted device is not possible to receive the OTA updates from Sony anymore?
mEREHAIGE said:
Hi, I've been thinking about rooting my XZ1c for a long time now. So, do I understand correctly that the ONLY disadvantage compared to non-rooted device is not possible to receive the OTA updates from Sony anymore?
Click to expand...
Click to collapse
No, you can flash a kernel to hide the bootloader unlock flag, this will mean that you will receive OTA updates, although depending on how you're rooted an update will most likely break your phone, so not that useful.
*made a thread*
Thanks--rooted withOUT adventure too
Very happily rooted now. Just wanted to say a quick thanks and add a few notes:
1. j4nn's renoroot to enable TA key backup and restore is fantastic. My advice: use and donate
2. munted's guide is excellent. clear and thorough...a rare combination.
3. do expect that renoroot may need to be restarted a couple of times. it took me 3 or 4 attempts to get temp root to pull the TA keys, although it took only 1 effort to get root back to restore.
4. topjohnwu's magisk is, of course, a key component to all this. Thx and $s there too.
I did a few things slightly differently/additionally than SunJu22.
5. I am on T-Mobile US, so I opted to create a hybrid Pie FW to get wifi calling and VoLTE. There are a number of discussions on this. I did it by combining the vendor**.sin and system**.sin files from custom-CH FW with the other files from custom-US FW. Of course (a) use IDENTICAL release numbers only, e.g. 47.A.2.10.28 w/ 47.A.2.10.28 and (b) you still need to delete .TA and persist files from the hybrid before you flash it.
Note: I don't really care about these features, but I have *heard* that T-mobile won't allow BYOD on their band-12 sites if they don't have VoLTE. Don't know if it is true (or where it is true) but figured why not?
6. I decided (for now, at least) to leave boot and recovery stock. So, I am using fastboot to run TWRP or a rooted kernel. Thanks again to j4nn for the method.
Note: I don't plan on allowing FOTA upgrades---I just like passing all the security checks and being able to *see* if updates are available.
That's all. Fine work in development and guides has made life simple and happy for me
kirkzp said:
Very happily rooted now. Just wanted to say a quick thanks and add a few notes:
1. j4nn's renoroot to enable TA key backup and restore is fantastic. My advice: use and donate
2. munted's guide is excellent. clear and thorough...a rare combination.
3. do expect that renoroot may need to be restarted a couple of times. it took me 3 or 4 attempts to get temp root to pull the TA keys, although it took only 1 effort to get root back to restore.
4. topjohnwu's magisk is, of course, a key component to all this. Thx and $s there too.
I did a few things slightly differently/additionally than SunJu22.
5. I am on T-Mobile US, so I opted to create a hybrid Pie FW to get wifi calling and VoLTE. There are a number of discussions on this. I did it by combining the vendor**.sin and system**.sin files from custom-CH FW with the other files from custom-US FW. Of course (a) use IDENTICAL release numbers only, e.g. 47.A.2.10.28 w/ 47.A.2.10.28 and (b) you still need to delete .TA and persist files from the hybrid before you flash it.
Note: I don't really care about these features, but I have *heard* that T-mobile won't allow BYOD on their band-12 sites if they don't have VoLTE. Don't know if it is true (or where it is true) but figured why not?
6. I decided (for now, at least) to leave boot and recovery stock. So, I am using fastboot to run TWRP or a rooted kernel. Thanks again to j4nn for the method.
Note: I don't plan on allowing FOTA upgrades---I just like passing all the security checks and being able to *see* if updates are available.
That's all. Fine work in development and guides has made life simple and happy for me
Click to expand...
Click to collapse
Now riddle me this cause I'm on Tmo USA as well and I did the hybrid work fine as well but heres the question, does googlepay and banking apps still work with a unlocked bootloader or did you flash a modified kernel to hide the unlocked status.
Sitting on the fence about unlocking mine so I can do a full nandroid before trying out some gsi pie roms infact this is the first phone I haven't unlocked or least put twrp on since my samsung sidekick 4g o.o
kernel with hide-unlock
T_Tank said:
Now riddle me this cause I'm on Tmo USA as well and I did the hybrid work fine as well but heres the question, does googlepay and banking apps still work with a unlocked bootloader or did you flash a modified kernel to hide the unlocked status.
Sitting on the fence about unlocking mine so I can do a full nandroid before trying out some gsi pie roms infact this is the first phone I haven't unlocked or least put twrp on since my samsung sidekick 4g o.o
Click to expand...
Click to collapse
Full disclosure: I don't use Google pay or too many banking apps, so YMMV. But, I am using j4nn's kernel with unlock hidden. (See link in my note 6.) You can flash this, or you can leave in your stock kernel and merely fastboot to this. From what I have seen, it hides most - if not all -- indicators that the phone is rooted and the BL in unlocked.
Does somebody has :
G8441_1310-7123_47.1.A.16.20-R7B_Customized_CE1.ftf ?
Only backup i did not make, and its gone from XperiFirm.
Still have the feeling battery life was better in Oreo, and would be nice for experimenting.
Would be nice.
Thanks in advance.
Hello,
My daughter accidentally deleted an audio record file of a S8 SM-G950FD with Android Pie (9).
After reading some post, it seems that I need to get a image file from internal memory with user data and files using dd command line and after that use a recover software to get the deleted files.
Ok, but occurs that to run the dd command line the cell phone needs to be rooted and here is my question:
If I follow the root proccess and install a TWRP, Magisk, etc, does it will keep the user files intact?
Does the root process will erase different partion other than user data?
Regards
The act of rooting itself does not erase userdata, however unlocking the bootloader does.
It's been a couple years since I've touched a Samsung device, so you'll want to check the rooting guides for your specific phone. Pretty sure any of the guides will clearly outline this and answer any questions you may have.
Hopefully someone will correct me if I am wrong
Also, why are you posting this in the Android Auto forum? You might get better answers in the Samsung forums.
stokedcrf said:
The act of rooting itself does not erase userdata, however unlocking the bootloader does.
It's been a couple years since I've touched a Samsung device, so you'll want to check the rooting guides for your specific phone. Pretty sure any of the guides will clearly outline this and answer any questions you may have.
Hopefully someone will correct me if I am wrong
Also, why are you posting this in the Android Auto forum? You might get better answers in the Samsung forums.
Click to expand...
Click to collapse
Thanks for advise stokedcrf, I will post o Samsung forum and ask for rooting guides for the phone.