Related
Hey guys, I just checked my At&t GS5 for updates and I had an available update to take. It was approximately 295 MB and it changed the bootloader from OC4 to OF2, however, my android version is still 5.0.
I've searched xda, I've called At&t, and I've been on Google and I cannot find anything on today's small update that changed my bootloader from OC4 to OF2.
My question is this:
Does anybody know what the current version of lollipop is supposed to be for the At&t galaxy s5 SM-G900A, and does anybody know why AT&T would push out such a small update that changes the bootloader? I'm not trying to root- when I get back into rooting, I'll use a non carrier branded phone or a model without a locked bootloader.
I realize that 5.1.1 is confirmed on the att galaxy s5 at some point, but I'm very confused about today's update that I took. I'm still on android 5.0 and I keep hitting brick walls regarding the SM-G900A, it's current version of lollipop, and what this update that I received today that changed my bootloader /build from OC4 to OF2.
Will someone please explain how this works? If they updated the bootloader today, 7/1 /15, and I'm still on 5.0, could it mean that 5.1 is around the corner?
I'm asking because I've never seen an update that changed the build number and bootloader, but didn't change the android version running on the phone.
Thanks yall.
No information on the update, if I were to guess this is to patch the Samsung Keyboard vulnerability.
Though it's over 200MB and I'm probably completely wrong
Maybe I can dream that AT&T decrypted the bootloader?
It's weird...Im on 5.0 but not on the OC4 bootloader any longer...it wasn't a very big update.
M2490311, Would you mind checking to see if it did patch the keyboard vulnerability?
To check to see if you're vulnerable to this exploit:
Download a terminal emulator from the play store and type:
Code:
ls -l /system/app/SamsungIME*
If you see a line that looks like:
Code:
-rw-r--r-- root root 7243414 2008-08-01 07:00 SamsungIME.apk
and the date is older than July 1, 2015 , it did not patch the vulnerability.
Also, if you do check to see if it was patched, could you take a screenshot of the terminal?
Code:
About this update:
Real Upgrade from OC4 to OF2
Thanks AT&T
Looks like it's been patched up, date changed but it's still old.
http://i.imgur.com/MYghs6Q.png
TheBadgers said:
M2490311, Would you mind checking to see if it did patch the keyboard vulnerability?
To check to see if you're vulnerable to this exploit:
Download a terminal emulator from the play store and type:
Code:
ls -l /system/app/SamsungIME*
If you see a line that looks like:
Code:
-rw-r--r-- root root 7243414 2008-08-01 07:00 SamsungIME.apk
and the date is older than July 1, 2015 , it did not patch the vulnerability.
Also, if you do check to see if it was patched, could you take a screenshot of the terminal?
Click to expand...
Click to collapse
I downloaded the terminal emulator and entered the exact code you provided and it kicks back with "not found."
M2490311 said:
I downloaded the terminal emulator and entered the exact code you provided and it kicks back with "not found."
Click to expand...
Click to collapse
Could you provide a screenshot?
Thanks AT&T
Looks like it's been patched up, date changed but it's still old.
Click to expand...
Click to collapse
Even if it's not the same date, as long as it's older than 2015, I think the vulnerability should still be active. Taken from NowSecure's website,"While Samsung began providing a patch to mobile network operators in early 2015, it is unknown if the carriers have provided the patch to the devices on their network." So it appears that Samsung themselves didn't even start working on a patch until 2015.
See attached.
ssn713 said:
I'm guessing it's been patched.
Click to expand...
Click to collapse
Whelp. Unfortunately in your case, it does appear to be patched. From what I've read, Samsung developed a patch for it in early 2015, which lines up with the "Date Modified" for your apk
QuillOmega0 said:
Maybe I can dream that AT&T decrypted the bootloader?
Click to expand...
Click to collapse
I would like to hear from someone that took the update to confirm or deny this part.
Mostlikely, wishfull thinking/dream.. but would be nice
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Sorry for the delay in responding. I entered both values posted earlier using the android terminal emulator, and this is what I am getting:
Sorry about the repeat screenshots, I couldn't tell them apart by thumbnails. I hope this helps and again, I apologize for the delay for the poster requesting screenshots
So now my question is what does this mean. It's my understanding (I may be wrong but I keep seeing conflicting info that's not up to date when I search it) that at this point in time, you can't Odin back from 5.0 to 4.4.2 or 4.4.4. I'm also under the impression that root is either nonexistent with the GS5 SM-900A or its a tedious process that isn't simple like towelroot. I wonder if this is going to affect root ability, and downgrade ability to attain root as well.
But then again, I was running the Sickness v6 on my s4 and safesstrap literally just ceased to work and my phone bricked itself. The entire OS crashed so I went to the att store, upgraded to the s5 and they reflashed the s4. But on my s5, Knox isn't capable of being device admin, and my s5 acts as though it's been rooted. I use a different security suite than knox, but I recall reading that if you root and flash a custom rom, and have the official stock firmware put back on, that knox won't work on your phone. This s5 has not been rooted unfortunately but the knox thing is making me wonder if something on my SD card transmitted an STD.
I think I'll be sick if root was attained with ease and I missed it by a mile in my searches on the OC4 bootloader and now that I'm on OF2, I'm screwed if I want root.
That is strange that it's not found.. I'm sorry I don't know what to make of it. I would have expected to see it updated but not missing
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
M2490311 said:
Sorry for the delay in responding. I entered both values posted earlier using the android terminal emulator, and this is what I am getting:
Sorry about the repeat screenshots, I couldn't tell them apart by thumbnails. I hope this helps and again, I apologize for the delay for the poster requesting screenshots
Click to expand...
Click to collapse
I think you're substituting 1's (the number) where you should be putting l's (the letter).
adam_ky said:
That is strange that it's not found.. I'm sorry I don't know what to make of it. I would have expected to see it updated but not missing
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
You know what? I think that I can get back into rooting if I complain about this s5 that's under warranty, and get a replacement that is on kitkat, and I can just work my way back up to an L based TouchWiz rom on the replacement.
My knox is weird....it's like it wasn't baked in, and is only available for download on Google play, and I have a few apps that are not visible on the google play store on other devices. Unless I'm losing my mind. I have Contra Evolution that's Konami based and if I search it on the store, its gone, but it's still in my saved apps. I'm gonna feel really dumb if I'm rooted and don't know it.
ssn713 said:
I think you're substituting 1's (the number) where you should be putting l's (the letter).
Click to expand...
Click to collapse
Ohhhhhhhhhhhhh.....
Hold on.
Well not having Knox "baked in" is a good thing. I'm sure there are ways to see if u are rooted. I think there is an app to check it
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Still getting a whole lot of nothing I guess...
adam_ky said:
Well not having Knox "baked in" is a good thing. I'm sure there are ways to see if u are rooted. I think there is an app to check it
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Totally, I'm definitely not going to complain about it because those knox updates are annoying and almost intrusive to the experience. I have at least 20 root apps that I've paid for so I'm going to see what joeykrim has to say lol
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
the guy who unlocked the bootloader on Verizon's s5 variant has released a document detailing what I believe is the procedure. Could this open the door for ATT's variant to be unlocked?
https://twitter.com/firewaterdevs/status/713906161834192896
http://theroot.ninja/disclosures/SAMDUNK_1.0-03262016.pdf
sensei22 said:
the guy who unlocked the bootloader on Verizon's s5 variant has released a document detailing what I believe is the procedure. Could this open the door for ATT's variant to be unlocked?
https://twitter.com/firewaterdevs/status/713906161834192896
http://theroot.ninja/disclosures/SAMDUNK_1.0-03262016.pdf
Click to expand...
Click to collapse
Possibly, based on what I read from it though it needs the string from the dev-edition device, they have that with the Verizon version so it's easy to get, we only have the one, so I think(speculation) it would be trivial at best to repeat this in our model since we don't even know what to set the CID to to make it reflect that of the 'dev edition', I don't think we're getting a towelroot from this at least[emoji14]
Sent from my SAMSUNG-SM-G900A using Tapatalk
I'm going to take a guess that the Verizon and AT&T phones are both unlockable via the same method. I don't even know how to run Samdunk.. Phone or PC? (Can't be Phone if we have no root access :/)
this really seems promising, i still love my s5 and would like to have the bootloader unlocked at some point.
I wouldn't get your hopes up. That unlock requires root which means anyone on 5.0 or above already is SOL, even IF that method worked on AT&T.
You cant root 5.1.1 on atnt because root modifys the system partition.You can still gain hardware access if theres an exploit you just cant modify the system partition(or the device wont turn on again after a full power-down) because it is checksumed on every boot. (and you cant remove this because it is in the kernel that is signature checked on every boot(and the user and system partitions aren't mounted yet so you cant run a hack to get around it))
This does not mess with the system partition so you could run a kernel exploit and this right after with out rooting.
For the cid use the tmobile s5 cid it is bootloader unlocked right from the store and has the same hardware(gsm modem).
Although my atnt device has 11 toshiba memory and all atnt devices might.
Guicrith said:
You cant root 5.1.1 on atnt because root modifys the system partition.You can still gain hardware access if theres an exploit you just cant modify the system partition(or the device wont turn on again after a full power-down) because it is checksumed on every boot. (and you cant remove this because it is in the kernel that is signature checked on every boot(and the user and system partitions aren't mounted yet so you cant run a hack to get around it))
This does not mess with the system partition so you could run a kernel exploit and this right after with out rooting.
For the cid use the tmobile s5 cid it is bootloader unlocked right from the store and has the same hardware(gsm modem).
Although my atnt device has 11 toshiba memory and all atnt devices might.
Click to expand...
Click to collapse
My att s5 has 15 for the first 2 digits of the Cid.
Guicrith said:
You cant root 5.1.1 on atnt because root modifys the system partition.You can still gain hardware access if theres an exploit you just cant modify the system partition(or the device wont turn on again after a full power-down) because it is checksumed on every boot. (and you cant remove this because it is in the kernel that is signature checked on every boot(and the user and system partitions aren't mounted yet so you cant run a hack to get around it))
This does not mess with the system partition so you could run a kernel exploit and this right after with out rooting.
For the cid use the tmobile s5 cid it is bootloader unlocked right from the store and has the same hardware(gsm modem).
Although my atnt device has 11 toshiba memory and all atnt devices might.
Click to expand...
Click to collapse
Mine is 15, I may be willing to be the guinea pig for this as long as it's not a 100% brick. I'm not entirely sure about the tmo s5 simply having the same hardware will make it work, if something like that was the case why did Verizon folks have to wait for someone with the dev Verizon s5 to upload their aboot?
Sent from my SAMSUNG-SM-G900A using Tapatalk
Anyone here willing to risk bricking their device with a 15 series chip pm me!
I saw on a thread maybe the Verizon s5 bootloader unlocking thread a post about copying your original boot chain to an SD card so incase you brick you can still boot the original boot chain off of your SD. Apparently your SD has to be class 10. Just more food for thought.
How do I check my cid? I'm tempted to test as I have the S7 now. But if this works, I may very well return the S7 due to locked bootloader.
TehPirate_ said:
How do I check my cid? I'm tempted to test as I have the S7 now. But if this works, I may very well return the S7 due to locked bootloader.
Click to expand...
Click to collapse
Brickbug emmc from play store. Still not clear if we can make it work, it should and can, but I think we're missing the att 'dev edition'(maybe factory has it with this?) aboot as just using the Verizon one doesn't seem to work.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Rakuu said:
Brickbug emmc from play store. Still not clear if we can make it work, it should and can, but I think we're missing the att 'dev edition'(maybe factory has it with this?) aboot as just using the Verizon one doesn't seem to work.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
Shame, mines Toshiba (11)
I just want to let everyone know that I've been involved with the thread over at Verizon and guinea pigged for us. I do have an active, however that shouldn't matter. At the moment, you can run both methods and it will appear to be successful, even changing the Cid, but it doesn't unlock the bootloader.
So for now, we're out of luck.
N4styN1ghtm4r3 said:
I just want to let everyone know that I've been involved with the thread over at Verizon and guinea pigged for us. I do have an active, however that shouldn't matter. At the moment, you can run both methods and it will appear to be successful, even changing the Cid, but it doesn't unlock the bootloader.
So for now, we're out of luck.
Click to expand...
Click to collapse
Damn, I was hoping this would pan out as I have a CID that starts with 15. Checked yesterday when advised in the TMS5 3.0 thread. I got this s5 from Samsung insights so I was hoping that'd help but it's At&t branded with locked bootloader. Waiting patiently for an option to unlock bootloader as I don't plan to get a new phone anytime soon.
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme
joshua14 said:
Damn, I was hoping this would pan out as I have a CID that starts with 15. Checked yesterday when advised in the TMS5 3.0 thread. I got this s5 from Samsung insights so I was hoping that'd help but it's At&t branded with locked bootloader. Waiting patiently for an option to unlock bootloader as I don't plan to get a new phone anytime soon.
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme
Click to expand...
Click to collapse
If you're comfortable doing this kind of stuff, then you can try without risking anything. Nobody with an original s5 has tried it, only me, but again, mine is an active. That may or may not be the reason it didn't work for me, but if somebody with an original s5 wants to try, that would give us a definitive answer.
I did both methods and everything went fine, with no errors. It simply didn't unlock. So feel free to give it a shot, you'll just have to restore your old Cid if it fails, which is no big deal. The only thing I'd give a heads up on, is both methods erase your SD card, so use a spare SD card or back up your files from it somewhere else.
Good luck if you try!!
N4styN1ghtm4r3 said:
If you're comfortable doing this kind of stuff, then you can try without risking anything. Nobody with an original s5 has tried it, only me, but again, mine is an active. That may or may not be the reason it didn't work for me, but if somebody with an original s5 wants to try, that would give us a definitive answer.
I did both methods and everything went fine, with no errors. It simply didn't unlock. So feel free to give it a shot, you'll just have to restore your old Cid if it fails, which is no big deal. The only thing I'd give a heads up on, is both methods erase your SD card, so use a spare SD card or back up your files from it somewhere else.
Good luck if you try!!
Click to expand...
Click to collapse
This will be something to try for the weekend. I have backups for both SS and FF so as long as I don't risk full bricking then I'm game. I have a few spare sd cards too. I never took any OTA updates, the first one that tried getting pushed on me while still within the 6 month insights program I rooted with TowelRoot and froze with TB. Other than that I didn't do much else until more recently to go to Muniz_ri 5.0 keeproot and then to TMS5-3.0-TMBUILD. I was hoping of convincing At&t to unlock the bootloader along with the sim unlock since they don't have any rights to this phone. I still have my Next plan s5 thru them so I can toy with this one, just don't want to end up completely bricking either. I have 2 S3 that I put full custom CM builds on for the kids to play with, just turned off root. Lol
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme
joshua14 said:
This will be something to try for the weekend. I have backups for both SS and FF so as long as I don't risk full bricking then I'm game. I have a few spare sd cards too. I never took any OTA updates, the first one that tried getting pushed on me while still within the 6 month insights program I rooted with TowelRoot and froze with TB. Other than that I didn't do much else until more recently to go to Muniz_ri 5.0 keeproot and then to TMS5-3.0-TMBUILD. I was hoping of convincing At&t to unlock the bootloader along with the sim unlock since they don't have any rights to this phone. I still have my Next plan s5 thru them so I can toy with this one, just don't want to end up completely bricking either. I have 2 S3 that I put full custom CM builds on for the kids to play with, just turned off root. Lol
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme
Click to expand...
Click to collapse
Yea like I said, as long as you follow the steps closely, there isn't a chance of bricking, it just won't unlock. Let us know when you give it a shot!
Still don't work as of yet...maybe never. The main thread on this is here:
http://forum.xda-developers.com/ver...locking-galaxys-s5-bootloader-t3337909/page77
samccfl99 said:
Still don't work as of yet...maybe never. The main thread on this is here:
http://forum.xda-developers.com/ver...locking-galaxys-s5-bootloader-t3337909/page77
Click to expand...
Click to collapse
It's likely to be never unless we get the proper CID, which as about a needle in a haystack to guess as the bootloader key.
Sent from my SAMSUNG-SM-G900A using Tapatalk
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
I had been looking for a new phone for awhile. Settled on a Note 9 because I wanted to try using the S Pen for work and dislike the Note 10 design. However, they are still sold at full price where I live, so I bought one secondhand. Everything seems generally fine with it, minus some freezing or weird reactions when it charges for awhile or restarts. But I have been skeptical of throwing passwords (personal and for work) on it to this point. Thats because I read an article about potential root level or firmware level spyware that remains after a reset.
I did a reset AND even took it to an official service center to flash new firmware (but they said they cannot do it there, but they did some kind of more advanced reset?). I checked my Knox counter in the Download menu and it reads 0x00000, maybe more or less zeros. Samsung pass, pay, health, and secure folder all seem to work (I can register for them, use the bio sensor). That all sounds like it has not been tampered with in any way, correct?
Thanks for the help.
IqD said:
I had been looking for a new phone for awhile. Settled on a Note 9 because I wanted to try using the S Pen for work and dislike the Note 10 design. However, they are still sold at full price where I live, so I bought one secondhand. Everything seems generally fine with it, minus some freezing or weird reactions when it charges for awhile or restarts. But I have been skeptical of throwing passwords (personal and for work) on it to this point. Thats because I read an article about potential root level or firmware level spyware that remains after a reset.
I did a reset AND even took it to an official service center to flash new firmware (but they said they cannot do it there, but they did some kind of more advanced reset?). I checked my Knox counter in the Download menu and it reads 0x00000, maybe more or less zeros. Samsung pass, pay, health, and secure folder all seem to work (I can register for them, use the bio sensor). That all sounds like it has not been tampered with in any way, correct?
Thanks for the help.
Click to expand...
Click to collapse
What's the model number?
Sm-n960n. Korean exynos model, 512gb.
IqD said:
Sm-n960n. Korean exynos model, 512gb.
Click to expand...
Click to collapse
If you are worried about remaining spyware of files, download the latest rom from sammobile and then flash with odin.
Just simply search how to use sammobile or how to use odin if you need help. Hundreds of years have posted how good and answered those questions already
I used to flip phones up until a couple years ago. I've bought and sold hundreds, maybe thousands of used phones, most of which had my accounts on them at one point and time. I think as long as the phone is running official firmware, isn't bootloader unlocked/rooted, and you've reset it, it should be fine. Of course you run the risk that someone has hacked it, installed spyware at the system level, and somehow overwritten the status to show as official such that the spyware persists even after a reset, but that's highly unlikely.
Sent from my SM-N960U using Tapatalk
Bober_is_a_troll said:
If you are worried about remaining spyware of files, download the latest rom from sammobile and then flash with odin.
Just simply search how to use sammobile or how to use odin if you need help. Hundreds of years have posted how good and answered those questions already
Click to expand...
Click to collapse
Thanks for the idea. I considered this but would like to avoid just because sammobile is unofficial, so it would still leave me slightly apprehensive even if everyone is using it.
Everything I read seems to suggest that the phone was never rooted if all of the Samsung apps work and the Download KNOX counter is 0x0. Just wanting to confirm by someone more knowledgeable about this.
joshw0000 said:
I used to flip phones up until a couple years ago. I've bought and sold hundreds, maybe thousands of used phones, most of which had my accounts on them at one point and time. I think as long as the phone is running official firmware, isn't bootloader unlocked/rooted, and you've reset it, it should be fine. Of course you run the risk that someone has hacked it, installed spyware at the system level, and somehow overwritten the status to show as official such that the spyware persists even after a reset, but that's highly unlikely.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Thanks. I don't think it has ever been unlocked or rooted, but is there a guaranteed way to know?
IqD said:
Thanks for the idea. I considered this but would like to avoid just because sammobile is unofficial, so it would still leave me slightly apprehensive even if everyone is using it.
Everything I read seems to suggest that the phone was never rooted if all of the Samsung apps work and the Download KNOX counter is 0x0. Just wanting to confirm by someone more knowledgeable about this.
Thanks. I don't think it has ever been unlocked or rooted, but is there a guaranteed way to know?
Click to expand...
Click to collapse
Go to settings > about phone > status and it should say "official". That would tell you if the phones operating system has been modified (rooted). As far as checking for bootloader unlock, I'm not sure on Samsung's but on a Google Pixel once the bootloader is unlocked it'll show an unlocked lock on the bootscreen every time that you reboot the phone. North American snapdragon variants of Note 9's do not have an unlockable bootloader so if your phone is a carrier branded phone, the bootloader can't be unlocked. You can Google your model # to figure out which one you have.
You can also check that all functions work properly. Typically apps like Samsung Pay won't work if the phone is rooted. There are ways around that where you can trick the phone into thinking it's not rooted to get those apps to work so, again, that's not a full proof way to check. For example, I'm using an AT&T variant that's been sim unlocked and flashed with Verizon firmware and it works 100% like a Verizon phone.
I'd say, reboot the phone. If you don't see an unlocked icon it's probably not unlocked. Go into settings and take note of your model #
Then go online and research about Odin and flashing official firmware via your computer. Download the latest official firmware for your phone, flash it using Odin, and then you'll know that there's no spyware on your phone. That would essentially be the equivalent of wiping a computer and reinstalling Windows.
Sent from my SM-N960U using Tapatalk
joshw0000 said:
Go to settings > about phone > status and it should say "official". That would tell you if the phones operating system has been modified (rooted). As far as checking for bootloader unlock, I'm not sure on Samsung's but on a Google Pixel once the bootloader is unlocked it'll show an unlocked lock on the bootscreen every time that you reboot the phone. North American snapdragon variants of Note 9's do not have an unlockable bootloader so if your phone is a carrier branded phone, the bootloader can't be unlocked. You can Google your model # to figure out which one you have.
You can also check that all functions work properly. Typically apps like Samsung Pay won't work if the phone is rooted. There are ways around that where you can trick the phone into thinking it's not rooted to get those apps to work so, again, that's not a full proof way to check. For example, I'm using an AT&T variant that's been sim unlocked and flashed with Verizon firmware and it works 100% like a Verizon phone.
I'd say, reboot the phone. If you don't see an unlocked icon it's probably not unlocked. Go into settings and take note of your model #
Then go online and research about Odin and flashing official firmware via your computer. Download the latest official firmware for your phone, flash it using Odin, and then you'll know that there's no spyware on your phone. That would essentially be the equivalent of wiping a computer and reinstalling Windows.
Click to expand...
Click to collapse
yeah.. i whouldint fall for that system/status official crap. as you can see in the screenshot i posted from my rooted n960n.
the only real way is to check if knox is tripped is in DL mode( turn phone off. hold bixby and vol down button while inserting a usb cable hooked to a computer.).
also flashing a stock firmware on an FRP locked phone wont do **** if someone has had their accounts logged in/registered on it and have not reset it correctly.
surprised you dont know this.
IqD said:
Sm-n960n. Korean exynos model, 512gb.
Click to expand...
Click to collapse
FYI - This phone does have an unlockable bootloader.
I'd recommend using Bobby's advice and flash the latest firmware with Odin. If the phone is not already on the latest update, you could flash one firmware less than current and then let the phone download and install an OTA to the current version. You'll know that its official if the phone successfully downloads and installs the OTA.
Sent from my SM-N960U using Tapatalk
---------- Post added at 07:35 PM ---------- Previous post was at 07:31 PM ----------
bober10113 said:
yeah.. i whouldint fall for that system/status official crap. as you can see in the screenshot i posted from my rooted n960n.
the only real way is to check if knox is tripped is in DL mode( turn phone off. hold bixby and vol down button while inserting a usb cable hooked to a computer.).
also flashing a stock firmware on an FRP locked phone wont do **** if someone has had their accounts logged in/registered on it and have not reset it correctly.
surprised you dont know this.
Click to expand...
Click to collapse
Not sure why you're trying to call me out when I clearly said there are ways for it show official if it's rooted. Also, no one said anything about FRP. If the phone was FRP locked they wouldn't be able to use it at all... Unless you know how to remove an FRP lock, which I do. At that point the phone would work/be a normal phone.
Sent from my SM-N960U using Tapatalk
joshw0000 said:
FYI - This phone does have an unlockable bootloader.
I'd recommend using Bobby's advice and flash the latest firmware with Odin. If the phone is not already on the latest update, you could flash one firmware less than current and then let the phone download and install an OTA to the current version. You'll know that its official if the phone successfully downloads and installs the OTA.
Sent from my SM-N960U using Tapatalk
---------- Post added at 07:35 PM ---------- Previous post was at 07:31 PM ----------
Not sure why you're trying to call me out when I clearly said there are ways for it show official if it's rooted. Also, no one said anything about FRP. If the phone was FRP locked they wouldn't be able to use it at all... Unless you know how to remove an FRP lock, which I do. At that point the phone would work/be a normal phone.
Click to expand...
Click to collapse
point taken on the FRP lock but the real point I was making is that the system status is bogus:
joshw0000 said:
Go to settings > about phone > status and it should say "official". That would tell you if the phones operating system has been modified (rooted).
Click to expand...
Click to collapse
bober10113 said:
point taken on the FRP lock but the real point I was making is that the system status is bogus:
Click to expand...
Click to collapse
You obviously didn't read the entire comment:
"There are ways around that where you can trick the phone into thinking it's not rooted to get those apps to work so, again, that's not a full proof way to check."
Or this comment:
" I used to flip phones up until a couple years ago. I've bought and sold hundreds, maybe thousands of used phones, most of which had my accounts on them at one point and time. I think as long as the phone is running official firmware, isn't bootloader unlocked/rooted, and you've reset it, it should be fine. Of course you run the risk that someone has hacked it, installed spyware at the system level, and somehow overwritten the status to show as official such that the spyware persists even after a reset, but that's highly unlikely."
There are a lot of ways to check. I pointed out some of the simpler ways. None of which are truly bullet proof. Hell, back in the day we could reset knox counters so if someone is going to the extreme to install some spyware and they're smart enough to install anything that would persist a factory reset, even checking knox isn't a full proof method.
And your screenshot really doesn't tell me anything. It's possible to have an unlocked bootloader AND official firmware at the same time. The operating system and bootloader are two different things. It's only when you modify the system that you have to hack the status to make it say official.
Sent from my SM-N960U using Tapatalk
joshw0000 said:
You obviously didn't read the entire comment:
"There are ways around that where you can trick the phone into thinking it's not rooted to get those apps to work so, again, that's not a full proof way to check."
There are a lot of ways to check. I pointed out some of the simpler ways. None of which are truly bullet proof. Hell, back in the day we could reset knox counters so if someone is going to the extreme to install some spyware and they're smart enough to install anything that would persist a factory reset, even checking knox isn't a full proof method.
Click to expand...
Click to collapse
fine but i mean, why ask a user to validate the state of their device via the worst possible method of them all?
he even already posted in OP that he went to DL mode to check the knox fuse status so would supersede by far the need to check via software/status.
edit
and the photo of my device status was just a way to show how i know device actual status and bootlaoder state aren't linked. especialy when rooted devices can spoof software status but none cane spoof fuse state in DL mode. so not sure why you are trying to convince me of something i just proved. u can say u agree next time.
bober10113 said:
fine but i mean, why ask a user to validate the state of their device via the worst possible method of them all?
he even already posted in OP that he went to DL mode to check the knox fuse status so would supersede by far the need to check via software/status.
Click to expand...
Click to collapse
No actually he didn't. He never said he went to DL mode, he just said the knox counter says 0x0. That can be checked via apps from the phone. If the phone was rooted, it could be manipulated to show 0x0 when it's really not.
You're focusing on one sentence dude. Get your panties out of a wod and read the whole comment.
Sent from my SM-N960U using Tapatalk
joshw0000 said:
No actually he didn't. He never said he went to DL mode, he just said the knox counter says 0x0. That can be checked via apps from the phone. If the phone was rooted, it could be manipulated to show 0x0 when it's really not.
You're focusing on one sentence dude. Get your panties out of a wod and read the whole comment.
Click to expand...
Click to collapse
lol. but i did read he went to download menu which i think we can interpret it as download mode. but hey i might wrong. can you show me anywhere in the OS where download menu is?
IqD said:
I checked my Knox counter in the Download menu and it reads 0x00000, maybe more or less zeros.
Click to expand...
Click to collapse
bober10113 said:
lol. but i did read he went to download menu which i think we can interpret it as download mode. but hey i might wrong. can you show me anywhere in the OS where download menu is?
Click to expand...
Click to collapse
What a troll.
Sent from my SM-N960U using Tapatalk
joshw0000 said:
What a troll.
Click to expand...
Click to collapse
that's the spirit!
bober10113 said:
lol. but i did read he went to download menu which i think we can interpret it as download mode. but hey i might wrong. can you show me anywhere in the OS where download menu is?
Click to expand...
Click to collapse
joshw0000 said:
No actually he didn't. He never said he went to DL mode, he just said the knox counter says 0x0. That can be checked via apps from the phone. If the phone was rooted, it could be manipulated to show 0x0 when it's really not.
You're focusing on one sentence dude. Get your panties out of a wod and read the whole comment.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Sorry for the confusion. I was referring to the Download mode by hitting the mentioned buttons on restart. The KNOX reads 0x0000. Also, it says OEM Lock: On. Then you are both saying the phone is safe?
Also, when I first got it, it did find an update OTA and installed it.
IqD said:
Sorry for the confusion. I was referring to the Download mode by hitting the mentioned buttons on restart. The KNOX reads 0x0000. Also, it says OEM Lock: On. Then you are both saying the phone is safe?
Also, when I first got it, it did find an update OTA and installed it.
Click to expand...
Click to collapse
no confusion on my part. i read and understood you correctly the 1st time around.
at first glance your device looks ok but...
additionally, there are ways to check if the device is off a lease with a ESN check. meaning if someone sold you a device still on contract. some sell contractual phones and after a period of time they will get blacklisted since the contract is never payed off fully. so device would appear to work fine and one day they just stop getting a signal and esn/imei get blacklisted.
side note:
surprised that this was not brought up earlier in the conversation as a factor to watch out for by some "experianced in the field flipping devices" user instead of stating the obvious like device status and the unreliable means to check it. especialy since, said user stated buying and selling hundred and even thousands of phones...!? ESN state would be no. 1 in the check list if things to watch out for.
anyways back to the current case, there are ESN/IMEI check services in the web to see status of device: stolen, still on contract...etc. i cannot provide any suggestion to these services unfortunately. this is something you need to check yourself or ask around.
good luck
IqD said:
I had been looking for a new phone for awhile. Settled on a Note 9 because I wanted to try using the S Pen for work and dislike the Note 10 design. However, they are still sold at full price where I live, so I bought one secondhand. Everything seems generally fine with it, minus some freezing or weird reactions when it charges for awhile or restarts. But I have been skeptical of throwing passwords (personal and for work) on it to this point. Thats because I read an article about potential root level or firmware level spyware that remains after a reset.
I did a reset AND even took it to an official service center to flash new firmware (but they said they cannot do it there, but they did some kind of more advanced reset?). I checked my Knox counter in the Download menu and it reads 0x00000, maybe more or less zeros. Samsung pass, pay, health, and secure folder all seem to work (I can register for them, use the bio sensor). That all sounds like it has not been tampered with in any way, correct?
Thanks for the help.
Click to expand...
Click to collapse
Reading this thread I've come to the conclusion that you should sell your rootable and boot unlockable device and buy a locked down USA model.
Thank me later. Least you'll be able to sleep well now.
Sent from my SM-G975U using Tapatalk
IqD said:
Sorry for the confusion. I was referring to the Download mode by hitting the mentioned buttons on restart. The KNOX reads 0x0000. Also, it says OEM Lock: On. Then you are both saying the phone is safe?
Also, when I first got it, it did find an update OTA and installed it.
Click to expand...
Click to collapse
It's about as safe, in terms of spyware, as you'll ever get from a used phone. I would assume you checked the ESN before buying it but if not, run a check with swappa.com/esn and checkesnfree.com to make sure it's clean. Screenshot the results and save them. Depending on your carrier you can likely run a check on their website and/or call support and ask them as well. As with any unlocked phone, know that you may not get all of the features that a carrier branded phone would have (i.e. I couldn't get WiFi calling working on a Korean S10 on Verizon).
Sent from my SM-N960U using Tapatalk