Hey there,
So I need to know all the necessary steps to properly install Andronix and Termux (F-Droid) by unlocking the bootloader. Do you know where I can find all the information about that for Galaxy s10?
Depends on WHICH S10 you have. Snapdragon CPU versions cannot really be unlocked. Exynos can. This forum is full of threads on how to do the Exynos, of course... I have a Snapdragon so I haven't spent much time learning it...
Ok thanks I have a snapdragon also so I guess I will do something else
I hear you - I have Snapdragon too, so I gave up ROM and rooting on this phone. Honestly, I don't miss it. I used to ROM and root all my previous phones, but I don't see the need to do that anymore.
I want to ssh my network from my phone using a vpn to access my router so I can wake on lan my server
You should be able to do that without root from the phone - ssh doesn't require root to run, and it's just a secure terminal. You can get an app to do that (I see plenty on the play store). As for VPN, again, you don't need root on the phone to do that - I have used OVPN many times from my phone without issue (and without root).
schwinn8 said:
You should be able to do that without root from the phone - ssh doesn't require root to run, and it's just a secure terminal. You can get an app to do that (I see plenty on the play store). As for VPN, again, you don't need root on the phone to do that - I have used OVPN many times from my phone without issue (and without root).
Click to expand...
Click to collapse
Ok thanks
Why is everybody so convinced that rooting will only be possible with an unlocked bootloader? if there were to be a kernel exploit which would gain us access to the block devices i would say it's possible to downgrade the bootloader or anything which is accessible by block devices like the recovery partition. Am i missing something here?
DaanNL said:
Why is everybody so convinced that rooting will only be possible with an unlocked bootloader? if there were to be a kernel exploit which would gain us access to the block devices i would say it's possible to downgrade the bootloader or anything which is accessible by block devices like the recovery partition. Am i missing something here?
Click to expand...
Click to collapse
If you have a solution to root a galaxy s10 snapdragon cpu I will read your comments on it. But I think I believe that is because of the articles in the internet are only mentioning that I need to unlock the bootloader.
Indirectelex said:
If you have a solution to root a galaxy s10 snapdragon cpu I will read your comments on it. But I think I believe that is because of the articles in the internet are only mentioning that I need to unlock the bootloader.
Click to expand...
Click to collapse
Yes, everybody is so convinced that you need to unlock the bootloader and i wonder why.... we don't need odin to flash, afaik as we can find a kernel exploit which would gain us root access we could set properties to enable the oem unlock option.... making it available and usable could be a different case..... some requirements need to be met. If we could access block devices we should be able to install magisk and root the device.
Indirectelex said:
If you have a solution to root a galaxy s10 snapdragon cpu I will read your comments on it. But I think I believe that is because of the articles in the internet are only mentioning that I need to unlock the bootloader.
Click to expand...
Click to collapse
I think i'm getting somewhere, don't know for sure... at first i was only able to flash CSC and now i'm able to flash every slot.... do you have the same results in odin?
DaanNL said:
I think i'm getting somewhere, don't know for sure... at first i was only able to flash CSC and now i'm able to flash every slot.... do you have the same results in odin?
Click to expand...
Click to collapse
I cant do tests on my galaxy s10 but I will on a Moto z2
we are so ****ed with the cellphones
Yeah, I need one too! I got a Galaxy S10 Plus Snapdragon. It's it's been 2 years since I have it and I can't find nobody that can teach me how to root it!!!
Because it cannot be rooted. US carriers have made that happen, and the manufacturers have had to keep doing it.
Many have tried, and on older BLs it can be done, but once you update you are stuck on a newer BL and cannot downgrade. If you root with the older BL, you cannot upgrade the BL either, because that will relock it.
If someone comes up with a way to do it, I'm all ears, as are many others... but with higher level crypto being implemented for this protection (ie, you need to know the crypto key!), it likely won't happen.
I have an idea but i don't know if it's possible, i tried but it seems corepatch isn't working.
I see a lot of topics about what's needed to unlock the bootloader, but if i look in the source code what is required to unlock the bootloader there's a lot of ro. properties which we can't set because we are not root.
As LSPatch can now communicate with Shizuku and gain system level access we might be able to disable system app verification (platform certificate, by extending CorePatch or maybe someone can write a signature verification disabler for lsposed). Then create an app which doesn't check for all these properties and initiates an OEM unlock and install it as system user./
Related
I have an ATT S5 (SM-G900A), completely stock, unrooted, updated to the latest 5.0 OTA update. My requirements for my phone are that it be able to pass Airwatch checks and that it be able to be encrypted (Personal device used at work). Some background first:
Last time I tried to play around with rooting, other mods, and whatnot was on my ATT S3 (I think I747?) and I discovered that an unspecified combination of rooting, installing a custom loader (CWM in my case) and installing a custom mod (Cyanogenmod at the time) made my phone unable to encrypt. At the time I was not required to use Airwatch, but encryption was required for my phone to connect to work, so I gave up on the whole lot.
I have now discovered that ATT, in their infinite wisdom, has replaced the S Voice drive mode with their own "ATT Drive Mode", and it's been verified they went so far as to remove the related APKs from the phone entirely. For those unaware, S Voice Drive mode is an feature of S Voice that (when turned on) reads out all callers and text messages, and then verbally prompts you for actions; reply, answer, ignore, etc. It allows fully hands free functionality. ATT Drive Mode, on the other hand, automatically kicks in whenever speeds of 20 MPH are detected (even if you're a passenger), rejects all calls and texts excluding a user-defined 5 person list, and essentially makes your phone useless anytime you're in a car. The goal is to "reduce texting and distracted driving", but as I'm on-call as part of my job and need to at least be aware of texts that come in within 10 minutes of receipt, it actually makes my drive much more dangerous. ATT Drive mode is a good idea for teens, perhaps, but i'm not a teen.
This brings me to my question: What are my options?
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
Honestly, the ideal solution would be something like the stock rom from the international version that would run on my ATT version...but I don't know if such a thing exists or is possible. I don't mind Samsung's cruft, but I do dislike ATT's lobotomizing of my phone to push their own little product that treats me like a kid. I know that I am less safe as a driver without the S Voice drive mode than I was with it.
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
sheaiden said:
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Waiting4MyAndroid said:
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Click to expand...
Click to collapse
Actually, while I greatly appreciate the fact that you took the time to reply (seriously! at least you took the time!), this is neither easy nor related to the questions I asked. If you look at my post, I'm not asking "how can I root", I'm asking three rather different questions:
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
In fact, I am unable to remain rooted (Airwatch; it's part of the post title), and the whole point and thrust of my question lies in the fact that I am looking to find out what affects encryption and what options I have as far as getting S Voice Drive mode on my phone while staying Airwatch compliant (not rooted). In addition, "if you can find the s voice drive app" is part of the problem too, as evidenced by the third question I asked above; I don't know where to find said app.
Does anyone know anything regarding what I was actually asking?
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
https://www.dropbox.com/s/oe7i2g81iuhjv38/S-Voice_Android_phone_J.apk?dl=0
Waiting4MyAndroid said:
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
Click to expand...
Click to collapse
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
sheaiden said:
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
Click to expand...
Click to collapse
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
OPOfreak said:
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
Click to expand...
Click to collapse
Interesting. I had been under the impression that I had seen people referring to installing clockworkmod or some similar thing on an S5, but I think I may be getting caught up in terminology; those are recoveries, aren't they? not bootloaders? Or perhaps people were posting about the other S5s with unlocked bootloaders. 15 different versions of S5, and I get stuck with the most apple-like of all the carriers....(in the sense of "you take what we give you and don't play with it!")
So, assuming I don't manage to get it installed via the link Waiting4MyAndroid was kind enough to post, I think that rules out anything other than the method of:
--wait for a root method to be established for the new OTA
--root, install the drive apk
--unroot, so I can encrypt and pass airwatch
Does anyone know if the old method of rooting broke encryption? and whether encryption was able to be performed after unrooting again?
Edit: Attempted to Sideload. Sadly, it is telling me "App not installed" (other sideloads do work; it's not the unknown sources setting). I'm thinking either the apk is marked for s4, and it's not compatible, or it's trying to overwrite files from the established svoice system, and that's not allowed. I suppose if someone has the drive apks from a tmobile S5 image or some such thing (same model, different carrier), then I could try again, but unfortunately this apk doesn't work. Thanks for the attempt, Waiting4MyAndroid!
So I actually don't have the S5, or any Samsung device for that matter, but a friend of mine does, and really wants to root their phone. I had no idea the AT&T S5 was so secure, but it's pretty interesting too. I've been researching for over 15 hours. I may not have been able to root his phone, but I think I have learned a couple things and maybe some possible root methods.
1.) Since using ODIN to downgrade would soft brick the phone, would it be possible to download the stock Lollipop update onto a computer, give the update super user access, replace the recovery with a custom one, or unlock the bootloader from the computer, then flash it through ODIN?
2.) Intercept any sort of OTA update, then alter it to flash a custom recovery or unlock bootloader? I don't know how you would go around this though.
3.) If someone hasn't taken the OTA update that patched the Stagefright exploit, could someone purposely use the exploit to allow installation of a custom recovery or even to unlock the bootloader since the Stagefright bug has super user access (or so I've heard).
Also, I'm sorry if these are stupid ideas. I know close to nothing about Samsung so everything I'm basing this off of is what I've read in the past 15 hours.
jsmithfms said:
So I actually don't have the S5, or any Samsung device for that matter, but a friend of mine does, and really wants to root their phone. I had no idea the AT&T S5 was so secure, but it's pretty interesting too. I've been researching for over 15 hours. I may not have been able to root his phone, but I think I have learned a couple things and maybe some possible root methods.
1.) Since using ODIN to downgrade would soft brick the phone, would it be possible to download the stock Lollipop update onto a computer, give the update super user access, replace the recovery with a custom one, or unlock the bootloader from the computer, then flash it through ODIN?
2.) Intercept any sort of OTA update, then alter it to flash a custom recovery or unlock bootloader? I don't know how you would go around this though.
3.) If someone hasn't taken the OTA update that patched the Stagefright exploit, could someone purposely use the exploit to allow installation of a custom recovery or even to unlock the bootloader since the Stagefright bug has super user access (or so I've heard).
Also, I'm sorry if these are stupid ideas. I know close to nothing about Samsung so everything I'm basing this off of is what I've read in the past 15 hours.
Click to expand...
Click to collapse
The issue is that AT&T (and Verizon) use an encrypted signature key to verify they are the correct unaltered files as well as the means to unlock the bootloader to allow the OTA. Without that key, the tasks you mention are near impossible. They are not stupid ideas at all..just very difficult with all the security checks included.
KennyG123 said:
The issue is that AT&T (and Verizon) use an encrypted signature key to verify they are the correct unaltered files as well as the means to unlock the bootloader to allow the OTA. Without that key, the tasks you mention are near impossible. They are not stupid ideas at all..just very difficult with all the security checks included.
Click to expand...
Click to collapse
Crap... well does anyone know how that encyption key is generated? Like, could I theoretically get an algorithm from a ROM?
Honestly for the time being I wouldn't bother with ROMS for that Device and carrier at the moment. Especially being that its someone elses device. Towelroot should be a good start. If Im not mistaken I don't think its supposed to trip knox.
Sent from my HTCEVODesign4G using XDA Free mobile app
jsmithfms said:
Crap... well does anyone know how that encyption key is generated? Like, could I theoretically get an algorithm from a ROM?
Click to expand...
Click to collapse
This is the riddle of the Sphinx my friend. I am sure the super devs have tried their best so far to crack it. It has been an ongoing effort to make phones more and more secure, not against the amateur developers and rooters, but against the hackers. These smartphones are now our personal computers, diaries, personal assistants, financial operator, and more. They basically are a person's (and business's) life. AT&T and Verizon have taken the big steps to appeal to the Exchange clients, corporate, government and military contracts. Even the general public want to know their phone is secure. This is what keeps me stuck on the Sprint network.
Have you tried Kingroot?
I successfully rooted my wife's AT&T S4 on OC3 lollipop (supposedly unrootable) with the desktop version. Mobile version didn't work but desktop did without a hiccup. Maybe it'll work on the S5.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Rockin' a l337 with Goldeneye v49.1 + Wanam Xposed and loving life on AT&T's 4G LTE network
S5 on lollipop has a new nasty boot loader.... it was a miracle on its own that they ever came up with safestrap to duck the boot loader on earlier versions of android
Hi developers.
Please do not hate me, but I have been looking for the answer and didn't see it anywhere. I just got Galaxy S8 verizon - G950USQU4CRE9 (it was a free gift from Verizon for their mistake) and I wanted to root it, but it seems that OEM unlock is missing in the developer menu, I have tried many things, not luck, so I thought I would ask you guys. IS there any chance to root it, or downgrade it to 7 and then root it?
Thank you very much for your answers and solutions
romanko258 said:
Hi developers.
Please do not hate me, but I have been looking for the answer and didn't see it anywhere. I just got Galaxy S8 verizon - G950USQU4CRE9 (it was a free gift from Verizon for their mistake) and I wanted to root it, but it seems that OEM unlock is missing in the developer menu, I have tried many things, not luck, so I thought I would ask you guys. IS there any chance to root it, or downgrade it to 7 and then root it?
Thank you very much for your answers and solutions
Click to expand...
Click to collapse
For future reference, when you are looking for how to root a specific device, the best thing to try is to do a Google search for:
"How to root (your specific model number)"
In your case it would be:
"How to root S8 SM G950U"
If you had done a search using your model number, you would have easily found this:
https://www.skyneel.com/root-samsung-galaxy-s8-sm-g950u
Remember, when you have a question about a certain device or if you want to know how to do something on a certain model number, it is always best to use the device's specific model number in your search terms along with the thing you're looking for or along with what you want to do to the device.
Sent from my LGL84VL using Tapatalk
Thank you
Thank you for your answer. Believe me I have tried it all, that is why I have chooses this form. In the link provided there is mention OEM unlock option, now this is what I do not have on my phone.
That is why I have posted the question. I read that snapdragon version is difficult to root, so I hoped to find the answer here, where there are lot of smart developers.
I am afraid to use the method described in the link because I have not unlocked the bootloader and I am not sure if that would work without it and if it will not brick the phone.
So, is the version irrelevant when looking for the root option? It is good enough to look just for G950US instead of G950USQU4CRE9? I know I have many questions, but I am just starting the path you already walked on.
romanko258 said:
Thank you for your answer. Believe me I have tried it all, that is why I have chooses this form. In the link provided there is mention OEM unlock option, now this is what I do not have on my phone.
That is why I have posted the question. I read that snapdragon version is difficult to root, so I hoped to find the answer here, where there are lot of smart developers.
I am afraid to use the method described in the link because I have not unlocked the bootloader and I am not sure if that would work without it and if it will not brick the phone.
So, is the version irrelevant when looking for the root option? It is good enough to look just for G950US instead of G950USQU4CRE9? I know I have many questions, but I am just starting the path you already walked on.
Click to expand...
Click to collapse
Usually, the model number in device settings or the model number behind battery should be enough, what you posted looks like the baseband or build number, there shouldn't be a need for the baseband or the build number unless there is more than one android version available for the device that are different from each other. In this case, the baseband or build number might make a difference if the method to root is different for each baseband/build number.
For example, some Samsung devices that use CF-autoroot have more than one android version/baseband/build number available, for some of these devices, the version of CF-autoroot is different, you can't use the CF-autoroot that is built to work with "this" version/baseband/build number on "that" version/baseband/build number.
If you're in doubt, check which version/baseband/build number that the CF-autoroot for your model number is built to work with, if it's different than the version/baseband/build number that is currently installed on your device, you can't use it.
Now, as for the OEM unlock option. Try disconnecting from mobile data and Wifi then remove your SIM card, then disable the telephone app on your device, then reboot the device, then check settings to see if you have the OEM unlock option.
Sent from my LGL84VL using Tapatalk
Thank you
Thank you for the explanation, it is clearer to me after your explanation
As per :Noa, as for the OEM unlock option. Try disconnecting from mobile data and Wifi then remove your SIM card, then disable the telephone app on your device, then reboot the device, then chrck settings to see if you have the OEM unlock option.
I have tried that and no luck.
SO it means that until I will have the option on my phone, I can NOT do anything regarding rooting the phone, correct? Maybe I should explain what I am looking for with the root option. I am not a developer at any means, I just like to have a control over the device, so that Being said and I want be able to remove any bloatware that I do not need.
Droidriven said:
Usually, the model number in device settings or the model number behind battery should be enough, what you posted looks like the baseband or build number, there shouldn't be a need for the baseband or the build number unless there is more than one android version available for the device that are different from each other. In this case, the baseband or build number might make a difference if the method to root is different for each baseband/build number.
For example, some Samsung devices that use CF-autoroot have more than one android version/baseband/build number available, for some of these devices, the version of CF-autoroot is different, you can't use the CF-autoroot that is built to work with "this" version/baseband/build number on "that" version/baseband/build number.
If you're in doubt, check which version/baseband/build number that the CF-autoroot for your model number is built to work with, if it's different than the version/baseband/build number that is currently installed on your device, you can't use it.
Noa, as for the OEM unlock option. Try disconnecting from mobile data and Wifi then remove your SIM card, then disable the telephone app on your device, then reboot the device, then chrck settings to see if you have the OEM unlock option.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
romanko258 said:
Thank you for the explanation, it is clearer to me after your explanation
As per :Noa, as for the OEM unlock option. Try disconnecting from mobile data and Wifi then remove your SIM card, then disable the telephone app on your device, then reboot the device, then chrck settings to see if you have the OEM unlock option.
I have tried that and no luck.
SO it means that until I will have the option on my phone, I can NOT do anything regarding rooting the phone, correct? Maybe I should explain what I am looking for with the root option. I am not a developer at any means, I just like to have a control over the device, so that Being said and I want be able to remove any bloatware that I do not need.
Click to expand...
Click to collapse
If you can't unlock the bootloader then your only chance is if one of the universal android apps for rooting android devices or one of the universal PC programs for rooting android devices just happens to work on your model.
Do some searches for:
"PC tools to root any android device"
Or
"Universal rooting apps for android"
There are many different android apps and PC programs for rooting android devices, try any and all android apps or PC programs designed for rooting that you can possibly find, maybe you'll get lucky.
Sent from my LGL84VL using Tapatalk
thanks again
thanks agin for your reply, I really appreciate it, I just tried I think all of them I have found, still no luck
Droidriven said:
If you can't unlock the bootloader then your only chance is if one of the universal android apps for rooting android devices or one of the universal PC programs for rooting android devices just happens to work on your model.
Do some searches for:
"PC tools to root any android device"
Or
"Universal rooting apps for android"
There are many different android apps and PC programs for rooting android devices, try any and all android apps or PC programs designed for rooting that you can possibly find, maybe you'll get lucky.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I guess I need to wait for OEM unlock option to appear on my phone, without it I can not do anything, Root genius was pretty close to 87% and then I got message that the phone is too solid to root
romanko258 said:
thanks agin for your reply, I really appreciate it, I just tried I think all of them I have found, still no luck
Click to expand...
Click to collapse
Mod Edit
romanko258 said:
I guess I need to wait for OEM unlock option to appear on my phone, without it I can not do anything, Root genius was pretty close to 87% and then I got message that the phone is too solid to root
Click to expand...
Click to collapse
there is no oem unlock on our devices we have bootloader locked phones Dude is not very smart and rolling off stock piles of crap
he needs to learn to search himself before making posts obviously
he is using a lg not even a samsung to post from
Depending on your firmware on your device now makes or breaks root
S8 bootloaders 1 and 2 only can be rooted 3 or higher no chance as of now and no downgrade possible
If the firmware you have listed in the title is correct you are on version 4 which is not rootable by anymeans need to get a different device
Thank you, I was suspicious about it as well, because I have researched it myself before I turned for the answer in here. The good neews is that my phone is not bricked and it works, and hopefully there will be root options sometime soon.
TheMadScientist said:
Mod Edit
there is no oem unlock on our devices we have bootloader locked phones Dude is not very smart and rolling off stock piles of crap
he needs to learn to search himself before making posts obviously
he is using a lg not even a samsung to post from
Depending on your firmware on your device now makes or breaks root
S8 bootloaders 1 and 2 only can be rooted 3 or higher no chance as of now and no downgrade possible
If the firmware you have listed in the title is correct you are on version 4 which is not rootable by anymeans need to get a different device
Click to expand...
Click to collapse
romanko258 said:
Thank you, I was suspicious about it as well, because I have researched it myself before I turned for the answer in here. The good neews is that my phone is not bricked and it works, and hopefully there will be root options sometime soon.
Click to expand...
Click to collapse
Sammy patched the only root method we had at the time
Im just glad you got the info before messing up the device Some people want to help but they dont know what is going on
TheMadScientist said:
Mod Edit
there is no oem unlock on our devices we have bootloader locked phones Dude is not very smart and rolling off stock piles of crap
he needs to learn to search himself before making posts obviously
he is using a lg not even a samsung to post from
Depending on your firmware on your device now makes or breaks root
S8 bootloaders 1 and 2 only can be rooted 3 or higher no chance as of now and no downgrade possible
If the firmware you have listed in the title is correct you are on version 4 which is not rootable by anymeans need to get a different device
Click to expand...
Click to collapse
Actually, I'm very familiar with CF autoroot.
I hate to break it to you but there are more than a few devices that can flash CF autoroot even though they have a LOCKED bootloader. Chainfire found a way around it on some devices, but those devices could only root via CF autoroot, they couldn't get TWRP at the same time. Granted, whether "this" or "that" device could use CF autoroot on locked bootloader is device specific, but that is where the user reads the CF Autoroot thread to see if their device meets that version of CF autoroots requirements, if it's one that can be used on locked bootloader, it will say so, if not, it will say that also.
Mod Edit
Also, if you look a few posts up, I actually posted the only possibilities to root if the bootloader could not be unlocked.
I understand where you're coming from though.
Sent from my LGL84VL using Tapatalk
Ok I have use the search feature and I am blind I cant find my question.
Can and how do we root the spring note 9?
I use to root my phones all the time but it's been over 5 years since I have done one and it appears that it has changed. I only need root so I can use android auto mirror function in my car. Thanks
Root does not yet exist for the carrier branded Note 9 in the US
Has this been solved yet?
Just look in the General Discussion section of the forum.
photolarry said:
Has this been solved yet?
Click to expand...
Click to collapse
yes and no lol.. to start i havent released anything yet.. i am only able to root on combo firmware which isnt much use to the masses.
system, vendor and odm partitions are protected and we need to write to these to root stock which seems impossible so far as any write operations crash device
i need root just to turn data on/off
elliwigy said:
yes and no lol.. to start i havent released anything yet.. i am only able to root on combo firmware which isnt much use to the masses.
system, vendor and odm partitions are protected and we need to write to these to root stock which seems impossible so far as any write operations crash device
Click to expand...
Click to collapse
what root method do you have?
i just need root to run some commands for data purposes.
QualcommCode said:
what root method do you have?
i just need root to run some commands for data purposes.
Click to expand...
Click to collapse
There are multiple threads discussing elliwigy's root method, but you just need to read this https://www.xda-developers.com/samsung-galaxy-note-9-proof-of-concept-root/ to know that it is not something you want to try on your daily driver. It is entirely impractical.
Is the Samsung Galaxy S20 FE 5G rootable?
yes it is, there are 2 or 3 threads where people go over the methods they followed
Just don't update it past rev 1 or 2. 1 to be safe.
How To Root Samsung Galaxy S20 FE (SM-G780F) & Install Magisk - NaldoTech
Follow the guide below to root your Samsung Galaxy S20 FE (Fan Edition) and install Magisk Manager. The developer behind Magisk, topjohnwu, released a Magisk
www.naldotech.com
bininga59 said:
How To Root Samsung Galaxy S20 FE (SM-G780F) & Install Magisk - NaldoTech
Follow the guide below to root your Samsung Galaxy S20 FE (Fan Edition) and install Magisk Manager. The developer behind Magisk, topjohnwu, released a Magisk
www.naldotech.com
Click to expand...
Click to collapse
Unfortunately that is for exynos. Not sure how many people need to know how to systemlessly root an exynos. Full root might be more useful for exynos users but good ol' snapdragon has everyone in a pickle (most everyone.)
Flucker08 said:
Unfortunately that is for exynos. Not sure how many people need to know how to systemlessly root an exynos. Full root might be more useful for exynos users but good ol' snapdragon has everyone in a pickle (most everyone.)
Click to expand...
Click to collapse
there's zero difference in how both models are rooted. systemless root has been the standard method for all androids for a long time now.
pinguluk said:
Is the Samsung Galaxy S20 FE 5G rootable?
Click to expand...
Click to collapse
Yeah almost every phone is rootable but it will either cost money or if you've updated your firmware then you'll have to wait until they figure out how to get past it, assuming they do, they always have just takes time. If you have updated your firmware you can look in to selling your device and buying one that hasn't been updated. I can give you more pointers on how to find phones that haven't been updated for cheap but that's only if your interested and no I'm not selling anything.
pinguluk said:
Is the Samsung Galaxy S20 FE 5G rootable?
Click to expand...
Click to collapse
Yeah almost every phone is rootable but it will either cost money or if you've updated your firmware then you'll have to wait until they figure out how to get past it, assuming they do, they always have just takes time. If you have updated your firmware you can look in to selling your device and buying one that hasn't been updated. I can give you more pointers on how to find phones that haven't been updated for cheap but that's only if your interested and no I'm not selling anything.
3mel said:
there's zero difference in how both models are rooted.
Click to expand...
Click to collapse
Oh really. So then why does snapdragon lock the bootloader while exynos doesn't? Not to mention a root that works on exynos won't necessarily work on snapdragon. I thought this was fairly well known.
What exactly are you referring to by model?
Flucker08 said:
Yeah almost every phone is rootable but it will either cost money or if you've updated your firmware then you'll have to wait until they figure out how to get past it, assuming they do, they always have just takes time. If you have updated your firmware you can look in to selling your device and buying one that hasn't been updated. I can give you more pointers on how to find phones that haven't been updated for cheap but that's only if your interested and no I'm not selling anything.
Oh really. So then why does snapdragon lock the bootloader while exynos doesn't? Not to mention a root that works on exynos won't necessarily work on snapdragon. I thought this was fairly well known.
What exactly are you referring to by model?
Click to expand...
Click to collapse
magisk doesn't have different versions for different devices and it's been the standard root method for a few years now. since version 22 how it works has changed for all new phones.
I'm on a snapdragon that didn't have a locked bootloader because that's only done in the US market (at the request of or to please US carriers I'm guessing). SM-G780 is a model number of the Exynos S20FE... SM-G781 is the Qualcomm, they both use the exact same method to obtain root.
3mel said:
there's zero difference in how both models are rooted. systemless root has been the standard method for all androids for a long time now.
Click to expand...
Click to collapse
I didn't see your other post. I'm not really in to getting in to these debates online not really my thing but I still use full root myself and systemless as well. They both have their pros and cons. I suppose I prefer to edit system files myself to overclock the device instead of depending on an app to do it for me.
There are lots of people still using full root. I think a long time in terms of electronics can be hard to pinpoint. I've used full root way more times than I've used systemless but I guess that's just because I've been doing it for a long time. I know some linux phones you can buy don't come with systemless root but only come with full root and they don't make systemless root phones off the shelf like they do full root for a reason. To each their own.
google and OEMs have made messing around with the system partition harder, it's read only now and overlays are how edits are mostly done. plus there are more apps that won't run if root is detected, systemless gives you the chance to evade that detection if you want it.
CF-autoroot is pretty much dead, the superSU app is owned by a private company and Chainfire had moved on.
have a read of this
Installation
The Magic Mask for Android
topjohnwu.github.io
this is rooting today, it's very different
3mel said:
google and OEMs have made messing around with the system partition harder, it's read only now and overlays are how edits are mostly done. plus there are more apps that won't run if root is detected, systemless gives you the chance to evade that detection if you want it.
CF-autoroot is pretty much dead, the superSU app is owned by a private company and Chainfire had moved on.
have a read of this
Installation
The Magic Mask for Android
topjohnwu.github.io
this is rooting today, it's very different
Click to expand...
Click to collapse
Oh thanks for the info. Yeah I've definitely used systemless. I did like it but of course there's nothing like doing it yourself. Although I rooted phones back in the day I've also used Magisk though I could've swore I was able to use vi and edit system files that would've been unreadable and definitely unwritable but I'm pretty sure I just changed the mount of whatever it was I was working on from ro to rw with 'mount -o remount,rw /' I'm to lazy to pull up Magisk I think I have it on a tablet somewhere. I probably also changed the file permissions with chmod or chown then chmod but I think there are some files you can't change using systemless now that I think about it hence the name systemless I dunno it's been awhile since I messed around with rooted phones.
After awhile you realize how vulnerable the device is after root and then when you think you can trust these apps that have root access then someone announces they found "_______" app pulling user information... I'm definitely not referring to any apps used anymore but it was the app people used before they used Magisk and it pretty much did the same thing but I wouldn't be surprised if newer root apps did the same.
Wait you said since SDK 22? Was systemless even around then? I don't think it was. I know it's been around for awhile but not that long.
I did find out something pretty funny when this guy was rooting people's phones and he had a contact in China... I was determined to find out who this Chinaman was. Well I don't think I should really say out of respect because he clearly didn't want people to know where he was from but yeah I guess I'll have to keep that to myself but it was pretty funny to say the least.
Also this was before rona so him being from wherever was irrelevant I just wanted to get it cheaper than what everyone else was paying. Turned out to be some old guy and unsurprisingly as you've assumed, not from China, or was he? He actually just unlocks phones and didn't acknowledge I even used the word root, he was thinking "oh no, they've found me."
@Flucker08 I meant since version22 of magisk not SDK22.
rooting with magisk used to be something you could do all from a custom recovery. now you have to download your firmware and patch it with magisk on your phone and then flash the patched image from PC
Hello
Please tell me, if i rooted Samsung s20 FE 5G ( Snapdragon ) can update new Firmware its Odin ? and not lost my all user data ? ( i hope to not must clear ) and rooted again ?
Please write, how to do it ?
after the first time rooting and unlocking the bootloader (so you could root) you wouldn't have to wipe again.
you would download the updated firmware, patch the AP file from your phone same as before and flash the downloaded firmware and patched AP all together in Odin @onken
if you select CSC_home for the CSC partition your user data will not be wiped !!
Hi
Ok, thanks for info @3mel
Please tell me yet, patch the AP i must prepare before flash new update firmware ?
onken said:
Hi
Ok, thanks for info @3mel
Please tell me yet, patch the AP i must prepare before flash new update firmware ?
Click to expand...
Click to collapse
yes, you download the update from somewhere. extract the AP file from the archive and copy to the phone. run magisk from the phone and wait till it's finished. copy the patched file back to your computer and use it along with the rest of the firmware files. again for CSC you MUST use the HOME_CSC file and not the regular CSC if you don't want the phone wiped.
that last part only applies when updating the phone, the first time you root you will have to wipe.
onken said:
Hi
Ok, thanks for info @3mel
Please tell me yet, patch the AP i must prepare before flash new update firmware ?
Click to expand...
Click to collapse
It is advised against updating after root. If you're on exynos I don't know but snapdragon it will make you lose root and no getting it back. It's said you can do it by removing the boot files from the firmware before flashing but I haven't tried just heard about it. Honestly you should just leave it. You aren't missing out on any amazing features. Most updates are security and if you're root you don't have much anyways.
All ok thanks for advice
3mel said:
yes, you download the update from somewhere. extract the AP file from the archive and copy to the phone. run magisk from the phone and wait till it's finished. copy the patched file back to your computer and use it along with the rest of the firmware files. again for CSC you MUST use the HOME_CSC file and not the regular CSC if you don't want the phone wiped.
that last part only applies when updating the phone, the first time you root you will have to wipe.
Click to expand...
Click to collapse
Hi @3mel
If I unlock, install twrp and root with magisk as per afaneh92's method, since I have twrp now, how much will the update method differ from what you mentioned here, if i don't want a wipe. If possible, can you please tell the steps in brief or provide a source? Sorry if this is not the right place for asking this.
I'm on SM-G781B/DS with OneUI 4.1(Android12).