Develop Bugs

[Q] Bootloader locked. Screwed?

I've got a new t807a from AT&T. According to the "about device" settings page, SE is "enforcing." My understanding is that this conclusively indicates that my bootloader is locked. It's currently running Android version 4.4.2, build number kot49h.T807aucu1ank1
I don't need a custom ROM and I don't care about tripping my knox counter (per se). I just want root. I've asked this in several relevant threads this week and gotten contradictory responses. Is there or is there not currently a method to root my tablet?
If not: is there hope? This is a great tablet but I can't live with the bloat for 18 months until I can afford a replacement. I CAN still return it and eat the 70-dollar "restocking" fee.
Thanks in advance.

Just because it is enforcing, does not mean it is locked.
The s6 shows enforcing and for the T-Mobile version can be rooted with autoroot and trip Knox.

TheArtiszan said:
Just because it is enforcing, does not mean it is locked.
The s6 shows enforcing and for the T-Mobile version can be rooted with autoroot and trip Knox.
Click to expand...
Click to collapse
So what does that mean for my t807a?

thorvindr said:
So what does that mean for my t807a?
Click to expand...
Click to collapse
Locked bootloader aside, root can be achieved. Check the Dev pages for specifics/updates but this is the auto page link. You'll see the 807 is being tested but check back there often to monitor progress.

skeeterpro said:
Locked bootloader aside, root can be achieved. Check the Dev pages for specifics/updates but this is the auto page link. You'll see the 807 is being tested but check back there often to monitor progress.
Click to expand...
Click to collapse
Thanks. I have been following that. Just hoping someone knows something I don't I suppose.

ATT=Locked Bootloader which there's not going to be root or anything. Same goes for Verizon. SE enforcing is Selinux. Most devices have that including my Tab S 10.5 WiFi with unlocked bootloader. SE is an protections or somesort (google it).
Since you have a locked bootloader, it will fail to flash modfied stuff to get root. It will only flash stock images. So you may have to return it. Just remember, don't buy from att or Verizon. Buy an unlocked model or Tmobile. Hope this helps!

DUHAsianSKILLZ said:
ATT=Locked Bootloader which there's not going to be root or anything. Same goes for Verizon. SE enforcing is Selinux. Most devices have that including my Tab S 10.5 WiFi with unlocked bootloader. SE is an protections or somesort (google it).
Since you have a locked bootloader, it will fail to flash modfied stuff to get root. It will only flash stock images. So you may have to return it. Just remember, don't buy from att or Verizon. Buy an unlocked model or Tmobile. Hope this helps!
Click to expand...
Click to collapse
I think you're telling me there's no way to unlock the bootloader and root is therefore completely unattainable. Is that right? If it's just a matter of "we haven't cracked it yet," I can be patient. But if you're saying there's really no hope, I'm going to be far less patient.
Is there no software solution (ie towelroot) that might help me get root without having to get past the bootloader?

thorvindr said:
I think you're telling me there's no way to unlock the bootloader and root is therefore completely unattainable. Is that right? If it's just a matter of "we haven't cracked it yet," I can be patient. But if you're saying there's really no hope, I'm going to be far less patient.
Is there no software solution (ie towelroot) that might help me get root without having to get past the bootloader?
Click to expand...
Click to collapse
Its a matter "we haven't cracked it" and no one is working on it. So basically almost to no hope and the odds of getting root or unlocking the Bootloader is really really low. There's no software solution like towel root that will get root or anything that doesn't mess with bootloader.
So there's no hope (unless some breakthrough happens).

DUHAsianSKILLZ said:
Its a matter "we haven't cracked it" and no one is working on it. So basically almost to no hope and the odds of getting root or unlocking the Bootloader is really really low. There's no software solution like towel root that will get root or anything that doesn't mess with bootloader.
So there's no hope (unless some breakthrough happens).
Click to expand...
Click to collapse
Well that blows. I guess that's what I get for buying off-the-rack.

Is this info outdated?
info outdated?
I've got an easy working root on my t807A with kingroot. And yet there seems to be no custom roms available for it.
Slightly out of topic, does anyone have a install to SDcard solution? Nothing I find seems to work

JMVPSlash said:
info outdated?
I've got an easy working root on my t807A with kingroot. And yet there seems to be no custom roms available for it.
Slightly out of topic, does anyone have a install to SDcard solution? Nothing I find seems to work
Click to expand...
Click to collapse
The built-in app manager lets you move apps to SD but I also have not found a solution to install directly to SD (without repartitioning the card). After several months of despair, I'm just now checking back to see if there's been any development on the bootloader front. It appears not. You can get root with Kingroot (also check out supersume, if that's still around, to replace kingroot's su app with supersu) but apparently the bootloader being locked prevents any non-official ROM from booting.

Any way to secure a rooted phone? Does root break things?

I am considering this phone as a replacement for Note 7, so I have some questions about root.
Does it break Android Pay, and if so, is it permanent? Like does it fry "secure element?" Or can one root, install adblock .hosts, but then reverse the effect?
Also, if the phone is rooted, can it still be secured? So, if I lose my phone, can someone plug it into usb and flash/wipe data? Or can it be secured, so that it could only be tampered by the owner?
Thanks.

nabbed said:
I am considering this phone as a replacement for Note 7, so I have some questions about root.
Does it break Android Pay, and if so, is it permanent? Like does it fry "secure element?" Or can one root, install adblock .hosts, but then reverse the effect?
Also, if the phone is rooted, can it still be secured? So, if I lose my phone, can someone plug it into usb and flash/wipe data? Or can it be secured, so that it could only be tampered by the owner?
Thanks.
Click to expand...
Click to collapse
Gentle bump.

At the current moment there's currently no root yet (although Chainfire did got seamless root working with boot image mods but is still working on getting everything done) and there's currently no custom recovery.
Also, Google hasn't used SE for the longest time since Verizon and other carriers has been locking out that chip on the SIM card for a long time. Instead they do some sort of emulation of sort which is stored in the data encrypted so if you ever wipe your phone you don't have to worry about the SE being all jacked up without unregistering it first.
In terms of being able to use Android Pay, it does check to see if the bootloader is unlocked but there's already a kernel out that bypasses that check and I'm able to use it just fine so even if you are rooted I'm sure you could just use that kernel and it'll still work (I'm not able to test with root since the root isn't publicly available yet but usually you can go into SuperSU and tell it to hide su and android pay should still work if it does check to see if su is installed on top of the bootloader being unlocked). So there's always ways around it.

Root & Rom Advice from the Ground Up

I need some help and I've looked all over but the information is fragmented and there is too many unfamiliar acronyms used which make it incredibly difficult for some like myself to catch up. So for the benefit of others who may be new I wanted to get some additional guidance.
I got the Pixel XL Google Version
Objectives:
1. Root with the ability to hide root so other apps will work
2. Native Mobile Hotspot
3. The ability to easily receive android updates without having to reflash etc..
4. Stay close to stock if possible, but willing to explore other options as long as security is trusted, and has good
compatibility.
5. Security is a concern, I tried a rom in the past with a Galaxy S4 and swear it had a backdoor installed in the rom.
What do you guys recommend? And how do I go about doing it?
Thank you!

If security is truly a concern you will not unlock your bootloader and root your phone.
Otherwise it all depends on which version phone you have, Verizon or Google?

1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.

mikaole said:
1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
I have the Pixel XL - Google Version
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.
Click to expand...
Click to collapse
My point about security really was that it's quite possible a ROM could have a backdoor. That a side..
Root is not a big security issue for me as long as the rom is trusted etc..
Shouldn't I be able to turn root off then be able to update and turn it back on again?

jadensmith said:
1. Root with the ability to hide root so other apps will work
Click to expand...
Click to collapse
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
3. The ability to easily receive android updates without having to reflash etc.
Click to expand...
Click to collapse
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
jadensmith said:
Shouldn't I be able to turn root off then be able to update and turn it back on again?
Click to expand...
Click to collapse
While reading I got the impression that I might be able to uninstall SuperSU and use the OTA update, but that didn't work with SuperSU the times I tried it, so I presume something SuperSU changed or something I did with root must have caused the update to fail. I haven't read the Magisk threads as much, yet I've seen that other SuperSU users also indicate that OTA updates no longer worked for them after rooting the phone.

alluringreality said:
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
That didn't work with SuperSU the times I tried it, so I presumed that something I did with root must have caused the update to fail to install.
Click to expand...
Click to collapse
Wow thanks for the great reply! It's so refreshing!
What do you mean by root one slot?

The phone has two "slots" for Android. The basic idea is that you have two copies of Android on the phone that share the same user data. On a stock phone it's intended to allow for less noticeable updates, and it also can allow the phone to fall back to the previous software version if something goes wrong with an update. On the May update my phone did automatically switch between slots, due to what is discussed in the second link below. The first link below gives some information and additional links to discussion about the slots on these phones.
http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

Is it possible to keep stock or near stock and just have root with the ability to hide root, and hotspot?
That's all I really need. What would be the best way to to do this?

side effects root and unlocked bootloader

Probably been asked thousand times before but I want to get a samsung A7050FN specific answer to this query.
What features and functions would stop working once I unlock bootloader and root with the mentioned procedure on A70 thread?
This phone is near perfect for everyday driver except It needs some Titanium backup and viper4android along with few minor UI tweaks.
If some nice smartsian provide a list, I can peace fully proceed with rooting and bootloader unlocking

secure folder will stop working, also you will need to update your device with Odin.

Since Knox will be tripped, you won't be able to use "Knox features" like Secure Folder (there's 3rd party apps that do the same), Samsung Flox, Samsung Pay (if applicable), Samsung Pass, Samsung Health (there's a workaround for this one?). I've also read there could be problems with some apps like banking and Netflix. (Magisk hide root status feature is your friend) . If you're outside the EU tripping Knox will also void warranty.

xomikron said:
Since Knox will be tripped, you won't be able to use "Knox features" like Secure Folder (there's 3rd party apps that do the same), Samsung Flox, Samsung Pay (if applicable), Samsung Pass, Samsung Health (there's a workaround for this one?). I've also read there could be problems with some apps like banking and Netflix. (Magisk hide root status feature is your friend) . If you're outside the EU tripping Knox will also void warranty.
Click to expand...
Click to collapse
Don't care about secure folder or Samsung pay or warranty or loosing ability to update OTA. I can use odin for that
Can samsung pass and health be bypassed via the technique of changing ro.xxxx.tima= 1 to 0 in build prop file?
Don't use Netflix so don't care. Nor use any banking apps
Would fingerprint, face unlock, ar emoji and other camera features and Samsung themes kepp working?
Once you are rooted and your bootloader is unlocked does your boot screen changes to show tripped knox etc?

I rooted my A705MN. Samsung health does not work for me after tima change to 0. I read somewhere that you would have to modify the apk somehow. Never looked into it too much. You can read about it here https://forum.xda-developers.com/s10-plus/how-to/guide-samsung-health-root-device-t3946881
I am bummed that about the secure folder. I used it a lot with my unrooted S8. You can modify the build.prop to pass the SafetyNet check to be able to use banking and Netflix apps again.
Edit: here is another place to read https://forum.xda-developers.com/galaxy-s9/how-to/guide-s-health-knox-0x1-t3843483

fizzingbees said:
Don't care about secure folder or Samsung pay or warranty or loosing ability to update OTA. I can use odin for that
Can samsung pass and health be bypassed via the technique of changing ro.xxxx.tima= 1 to 0 in build prop file?
Don't use Netflix so don't care. Nor use any banking apps
Would fingerprint, face unlock, ar emoji and other camera features and Samsung themes kepp working?
Once you are rooted and your bootloader is unlocked does your boot screen changes to show tripped knox etc?
Click to expand...
Click to collapse
Samsung Pass uses biometrics to log-in and such, it won't work if the device is rooted. I don't know of any bypasses but I've found this https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977
I don't see why emoji and general camera features would stop working, they're not really security features, not that the stock camera is very useful. GCam is a better option for photography.
For now, I haven't rooted my device. From my understanding to enter a rooted state with Magisk you need to turn on your phone with a certain key combination, otherwise I don't think anything is displayed when the phone boots, why is that important?

banking? so like logging on to chase online app may not work if i unlock boot and root? that would be just dumb, i mean my nexus 6 was rooted and custom rom-ed and chase worked

xomikron said:
Samsung Pass uses biometrics to log-in and such, it won't work if the device is rooted. I don't know of any bypasses but I've found this https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977
I don't see why emoji and general camera features would stop working, they're not really security features, not that the stock camera is very useful. GCam is a better option for photography.
For now, I haven't rooted my device. From my understanding to enter a rooted state with Magisk you need to turn on your phone with a certain key combination, otherwise I don't think anything is displayed when the phone boots, why is that important?
Click to expand...
Click to collapse
Our Samsung A70 is very finicky with root and unlocked bootloader. And the rooting method we use is not so very official and stable for us.
So we need to use a certain key combination to keep root and magisk app when rebooting phone.
You mentioned gcam. Which version and config file are you using?

leo5111 said:
banking? so like logging on to chase online app may not work if i unlock boot and root? that would be just dumb, i mean my nexus 6 was rooted and custom rom-ed and chase worked
Click to expand...
Click to collapse
Actually its a security feature.
Many banking and enterprise applications don't work if your bootloader is compromised and your system rooted. They believe that by rooting and gaining administrative status, any hacker can bypass banking app security thereby compromising consumer safety

cealaska said:
I rooted my A705MN. Samsung health does not work for me after tima change to 0. I read somewhere that you would have to modify the apk somehow. Never looked into it too much. You can read about it here https://forum.xda-developers.com/s10-plus/how-to/guide-samsung-health-root-device-t3946881
I am bummed that about the secure folder. I used it a lot with my unrooted S8. You can modify the build.prop to pass the SafetyNet check to be able to use banking and Netflix apps again.
Edit: here is another place to read https://forum.xda-developers.com/galaxy-s9/how-to/guide-s-health-knox-0x1-t3843483
Click to expand...
Click to collapse
It's not like a70 has heart rate sensor and oximeter that I will. Be mad about Samsung health.
Still Samsung makes very stupid decision sometimes.

back to previous statement i NEVER have rooted my phone and then Chase app didnt work, so trying to see before bothering to try and root...EDIT...anyone here with rooted a70 and chase mobile app does it work? that and paypal

fizzingbees said:
It's not like a70 has heart rate sensor and oximeter that I will. Be mad about Samsung health.
Still Samsung makes very stupid decision sometimes.
Click to expand...
Click to collapse
I never really used Samsung Health with my unrooted S8. Fingerprint reader does not work to unlock my rooted A70 on Q (Android 10). It accepts the fingerprint but does not unlock the phone. It goes into a loop where it locks the phone again even I press the fingerprint sensor. I hate the ultrasonic reader lol. Does not work with screen protectors to prevent it from being scratched.
Can't use private mode in Samsung Internet anymore A lot of the features from Samsung seems to be disabled after tripping Knox. I used to love Samsung but with rooting now is a pain in the neck. The build.prop is different than 9 which sucks because I liked "overclocking" kind of making the CPU use all cores, it is not there anymore in Q. I am not sure that the Net improvements hacks for the build prop works anymore. Internet connection does not seem to be as fast for me as 9 was. Edit: I am not sure why the hell we can't use them because it erases the phone when we unlock the bootloader. Even if we re-flash stock they will not work because efuse is already tripped.
back to previous statement i NEVER have rooted my phone and then Chase app didnt work, so trying to see before bothering to try and root...EDIT...anyone here with rooted a70 and chase mobile app does it work? that and paypal
Click to expand...
Click to collapse
I am sorry I do not use those apps. You will have to edit your build.prop to get it to pass the SafetyCheck most likely. If Chase still does not work for you unrooted try contact their support and see if they can help you make it work. I am not liking rooted Q as much as rooted 9 was.

Okay so it means that t rooting and unlocking bootloader leads to Samsung secure folder, Samsung health, Samsung pay, secure login, banking apps and Netflix not working anymore.
Moreover specifically for A70, rebooting phone require specific key combination.
What about boot screen? Does it show any new text after rooting?
My note 4 after rooting shows kernal booting system or kernal booting recovery which is indication thst device has been tempered with.

I have a problem with the making phone calls after rooting. The sounds leak out as if it's on speaker (when it's not) and when on speaker it makes a very shape echo in the back ground.
P.S. havoc os

M.Sam90 said:
I have a problem with the making phone calls after rooting. The sounds leak out as if it's on speaker (when it's not) and when on speaker it makes a very shape echo in the back ground.
P.S. havoc os
Click to expand...
Click to collapse
Turn off voice enhancement in call settings. Or noise reduction in call settings
These settings are known to cause echo or static noise issues during call.
Also try turning off any sound mods you may have done after rooting
Report this issue at hovac os thread. Maybe it's a known issue with that Rom

Headset and sound issues
fizzingbees said:
Turn off voice enhancement in call settings. Or noise reduction in call settings
These settings are known to cause echo or static noise issues during call.
Also try turning off any sound mods you may have done after rooting
Report this issue at hovac os thread. Maybe it's a known issue with that Rom
Click to expand...
Click to collapse
Thanks for the reply but the issues is still the same any other adjustments to recommend ?

fizzingbees said:
Don't care about secure folder or Samsung pay or warranty or loosing ability to update OTA. I can use odin for that
Can samsung pass and health be bypassed via the technique of changing ro.xxxx.tima= 1 to 0 in build prop file?
Don't use Netflix so don't care. Nor use any banking apps
Would fingerprint, face unlock, ar emoji and other camera features and Samsung themes kepp working?
Once you are rooted and your bootloader is unlocked does your boot screen changes to show tripped knox etc?
Click to expand...
Click to collapse
fizzingbees said:
Our Samsung A70 is very finicky with root and unlocked bootloader. And the rooting method we use is not so very official and stable for us.
So we need to use a certain key combination to keep root and magisk app when rebooting phone.
You mentioned gcam. Which version and config file are you using?
Click to expand...
Click to collapse
Sorry for the late reply. I'm using GCam version 7.3.018 by Urnx05 (v1.4) with the config file by dotsx, you can check the file in Telegram by joining the group from this link.

xomikron said:
Sorry for the late reply. I'm using GCam version 7.3.018 by Urnx05 (v1.4) with the config file by dotsx, you can check the file in Telegram by joining the group from this link.
Click to expand...
Click to collapse
Can you kindly post direct link to gcam apk here along with config file as attachment

M.Sam90 said:
Thanks for the reply but the issues is still the same any other adjustments to recommend ?
Click to expand...
Click to collapse
Ask this question in havoc OS thread.
They can help you better than us

xomikron said:
Sorry for the late reply. I'm using GCam version 7.3.018 by Urnx05 (v1.4) with the config file by dotsx, you can check the file in Telegram by joining the group from this link.
Click to expand...
Click to collapse
I found your version but the auxiliary cameras cause the app to crash.
How do you fix this. Any help

(Question) rooting and back to stock

Hi guys
It’s been awhile since I had a Samsung phone
Anyhow I remember that if you are rooting your phone I will not be able to go back to stock and keep receiving updates regularly and also the user will not be able to use any Samsung service since there is some security on the device board
I wonder if it’s still the situation in galaxy s21 series
thanks

Yes OTA updates will be disabled for the rooted device. But you can easily install them if you so wish without loosing root by temporarily removing root without rebooting the device. Follow this guide for full process.
As for the services, I didn't hear about a service that's disabled by rooting. But if it happens you can easily replace said services by downloading alternatives or using specific modules in magisk manager.

Thank you
I’m asking because if I will ever want to sell the device it will be impossible

sagiag said:
Thank you
I’m asking because if I will ever want to sell the device it will be impossible
Click to expand...
Click to collapse
Not at all.
You can just do this:
Unroot.
Remove Samsung and google account.
Flash stock ROM [Optional, unless you flashed a custom ROM]
Lock the bootloader.
And that's it you can sell it as just lightly used.

I think you wouldn't be able to use Secure Folder after root.

dalanik said:
I think you wouldn't be able to use Secure Folder after root.
Click to expand...
Click to collapse
Knox is disabled after rooting, similarly anything knox dependant will be disabled as well. I thought he meant some other services like samsung health or other bloatware.