Hello,
my S4A I9295 was shiped with Android 4.2 in 2013, so it came with a KNOX-free bootloader.
Because of incompatibility issues between some roms and this old 4.2 bootloader, today i installed a official Samsung update package* with odin, to bring my phones bootloader up to date. This update lifted my bootloader to a newer version, which is now compatible to Kitkat 4.4.2 base stock roms.
* 2014 June Germany 4.4.2 / I9295XXUCNE5_I9295DBTCNE1_DBT.zip / I9295XXUCNE5_I9295DBTCNE1_I9295XXUCNE5_HOME.tar.md 5
After i have installed, booted and tested this official Samsung installation, i booted to download mode, flashed PhilZ 6.57.9 custom recovery and flashed a custom rom again.
I assumed, that KNOX status is now 0x1 , but it is still 0x0. :fingers-crossed:
Why is KNOX still 0x0 in download mode? Its nothing i would complain about, but i though custom recovery and a modified (stock) rom will automatically result in KNOX 0x1?
my S4A I9295 was shiped with Android 4.2 in 2013, so it came with a KNOX-free bootloader.
Because of incompatibility issues between some roms and this old 4.2 bootloader, today i installed a official Samsung update package* with odin, to bring my phones bootloader up to date. This update lifted my bootloader to a newer version, which is now compatible to Kitkat 4.4.2 base stock roms.
* 2014 June Germany 4.4.2 / I9295XXUCNE5_I9295DBTCNE1_DBT.zip / I9295XXUCNE5_I9295DBTCNE1_I9295XXUCNE5_HOME.tar.md 5
After i have installed, booted and tested this official Samsung installation, i booted to download mode, flashed PhilZ 6.57.9 custom recovery and flashed a custom rom again.
I assumed, that KNOX status is now 0x1 , but it is still 0x0. :fingers-crossed:
Why is KNOX still 0x0 in download mode? Its nothing i would complain about, but i though custom recovery and a modified (stock) rom will automatically result in KNOX 0x1?
Aucun commentaire:
Enregistrer un commentaire