Ive had problems writing to system and such for ever and recently i went into the bootloader to do stuff and i saw knox kernel lock is still 0 (as in in a stock state) i was wondering if disabling knox somehow would fix this issue, and if so how?
it also says "write protection enable" help please
I want to install a aosp rom on my Z1 compact.
My Z1 compact is running and i am trying to unlock the bootloader. I have entered *#*#7378423#*# which says i cant unlock the bootloader.
Is there any other method to unlock the bootloader?
No, bad luck.
Do you think it will be possible in the future?
325i. said:
Do you think it will be possible in the future?
Click to expand...
Click to collapse
Who knows, it's a tiring subject, so either return your Phone and buy a SimFree Phone or keep it in the hope that maybe you'll be able to, but don't hold your breath.
2ndBoot method possible?
For some Android phones with a locked bootloader, for example Motorola Defy, a "2nd boot" method has been used to use custom roms.
The way I understand it, this leaves the stock kernel in place, so that the locked bootloader can boot the stock kernel that it insists on.
Using root permissions, the system is modified so that at some stage in the stock boot process, the boot process restarts with a possibly different, modified kernel and the definitely different, custom userspace system, for example AOSP.
Has this been done with Xperia devices, especially the Z1C?
Defyner said:
For some Android phones with a locked bootloader, for example Motorola Defy, a "2nd boot" method has been used to use custom roms.
The way I understand it, this leaves the stock kernel in place, so that the locked bootloader can boot the stock kernel that it insists on.
Using root permissions, the system is modified so that at some stage in the stock boot process, the boot process restarts with a possibly different, modified kernel and the definitely different, custom userspace system, for example AOSP.
Has this been done with Xperia devices, especially the Z1C?
Click to expand...
Click to collapse
This is extremely difficult to accomplish unless the kernel supports loading kernel modules on the fly, and the Z1C stock kernel doesn't. In fact, most devices don't these days since it enables things like this once the security of the ROM is compromised.
@325i. You will most likely (like 99.99%) never be able to unlock your current Z1C, return it and get an unlockable one, or change your mind about wanting to unlock it.
Hello all! I have just acquired a Note 10.1 2014 Edition! However, the one thing that's sort of bothering me is the lack of root. I also have a Note 3 that's rooted and it's amazing, so I would like that experience on my new tablet as well. My only fear is KNOX; Because my model is the Wi-Fi (P600) edition, there is no version of a root that keeps the KNOX flag at 0x0. With that said, I have a few questions:
1. If I root my tablet, is there any chance of me later on upgrading the system software of my device (Say, Lollipop later on when it's released)? I know OTA is out of the question when rooted.
2. Other than the KNOX applications, does the KNOX flag limit the usage of my device in any other way (for example, Miracast, HDCP, etc.)?
3. How limited am it to software changes on my phone with the KNOX flag enabled (I'm not talking apps, but system changes like bootloader, firmware, recovery, etc. Essentially, would I be able to install a custom bootloader and/or recovery after my KNOX flag is set to 0x1?)?
I have tried looking up the answers to these questions, but the sources I found have confused me. I'm not worried about my warranty either.
I also like to see those questions answered
computerlife22 said:
1. If I root my tablet, is there any chance of me later on upgrading the system software of my device (Say, Lollipop later on when it's released)? I know OTA is out of the question when rooted.
2. Other than the KNOX applications, does the KNOX flag limit the usage of my device in any other way (for example, Miracast, HDCP, etc.)?
3. How limited am it to software changes on my phone with the KNOX flag enabled (I'm not talking apps, but system changes like bootloader, firmware, recovery, etc. Essentially, would I be able to install a custom bootloader and/or recovery after my KNOX flag is set to 0x1?)?
Click to expand...
Click to collapse
1.) Odds are we will see 5.0-based ROMs before an OTA update for our specific device, so don't worry. On a previous tablet, I went from 3.2 to an OTA 4.0, then rooted and flashed a 4.1 ROM (CM10). The great part is, Toshiba never pushed anything past a horribly buggy 4.0 for it. Not only can you upgrade your software in the future, you'll have better options, more options, and (in all liklihood) earlier access.
2.) Not that I know of. I'm running all of my apps perfectly and have only had one feature not work on an Xposed module (hide WiFi on Wanam Xposed module), though I can't attribute that to KNOX in any way.
3.) I've never tried installing a custom bootloader or recovery, so unfortunately I can't answer that with any degree of certainty.
computerlife22 said:
1. If I root my tablet, is there any chance of me later on upgrading the system software of my device (Say, Lollipop later on when it's released)? I know OTA is out of the question when rooted.
Click to expand...
Click to collapse
Yes. You can always upgrade by downloading firmware via a site like sammobile.com and flashing that via ODIN, or using Kies to automatically download the latest firmware and flash it to your device. Either of those methods will result in you losing root. If a root method exists for the updated firmware, you can re-root.
computerlife22 said:
2. Other than the KNOX applications, does the KNOX flag limit the usage of my device in any other way (for example, Miracast, HDCP, etc.)?
Click to expand...
Click to collapse
No. Screen mirroring (and possibly other features, but that's the only one I know of) will refuse to work if you have a custom recovery installed. You can get around this by reflashing stock recovery, or making an edit to a system file.
computerlife22 said:
3. How limited am it to software changes on my phone with the KNOX flag enabled (I'm not talking apps, but system changes like bootloader, firmware, recovery, etc. Essentially, would I be able to install a custom bootloader and/or recovery after my KNOX flag is set to 0x1?)?
Click to expand...
Click to collapse
I don't believe there are any custom bootloaders available, but you can flash a custom ROM/recovery easily.
Decided to root... but how?
Okay, thanks guys. I've decided that I would like to take the plunge and root my tablet. However, I'm confused on how I should. What method should I use to root my tablet? I'm running KitKat 4.4.2 version NI1.
Would this still work?
http://forum.xda-developers.com/showthread.php?t=2490805
Here you go, step by step.
There are also YouTube videos on rooting our tablets (albeit with different files for an earlier version) that show you the process. I like using them when rooting devices so I can visualize the steps and actually see how it's done rather than just reading about it.
Closed per OP request
I'm trying to install custom roms on my phone but can't due to this stupid "Enforcing" problem that exists in my android phone. I tried the terminal way (Sentenforce 0), but no luck! So I tried disabling the SElinux by installing a custom kernel but am getting red text during boot that says "Kernel is not SEandroid enforcing". What exactly is that? I have root, but I also have knox apps that I removed. However, I am unsure if it is the KNOX that is preventing the SElinux from being changed from enforcing to permissive. Is it? If I go to my settings, and go to "About Phone", I see the knox info.
KNOX version:
KNOX 2.4
SE for android 2.3.0
TIMA 3.0
Container 2.4.0
and so-forth.
My android INFO:
5.0.2 Lollipop
ARM64
Odexed
ART runtime
Carrier is Straight Talk.
Model is SM-S906L
Did I not remove all the knox apps? Or is part of the KNOX embedded into the Kernel? Anything I should modify to disable the KNOX entirely?? And what about the permissions for the Kernel?
So what is going on???? Is it the KNOX that's preventing SElinux from being changed to permissive? I would really appreciate it if someone could figure this out! I don't know everything about Android so I really need some help. :silly:
I have a Samsung Galaxy Tab S 10.5 LTE (T805), running the stock Lollipop 5.0.2 (XA1BOJ1) and rooted with CF-Auto-Root.
Now I know that after rooting encryption is more or less not possible, what I am not sure about is if it is possible to encrypt the device (both the internal and external storage) after reflashing the stock ROM (whether Lollipop or Marshmallow, in case there are differences) and not rooting the device (and keeping it not rooted).
Anyone knows for sure..?
TIA
P.S. In case it's possible, is un-rooting sufficient or do I have to flash the stock ROM..? (I am asking because of I don't have to reflash I would keep at least some of the changes that I did to the OS while rooted, like for example the edits in some config files which grant me full acess to the SD, to mute the camera sound and so on)