Database Users

[Q] pls help anyone has got any solution to this problem?

http://forum.xda-developers.com/showthread.php?p=32877250#post32877250
Here is a part of log from RSD lite:
04/22/12 01:53:07 Multi upgrade started for 1 phones
04/22/12 01:53:07 [Device ID: 0] Flashing phone.
04/22/12 01:53:20 ERROR: Phone[0000]: Error sending TI ROM data packet request. Device API Error: 0xE003009F - on device ID 0.
04/22/12 01:53:20 ERROR: Flash failure: Phone[0000]: Error sending TI ROM data packet request. Device API Error: 0xE003009F (Error Code: e003009f),
Detailed Error Details: Direction of the Error=1000, Command Value=0, Code Group Number=No Codegroup - on device ID 0.
04/22/12 01:53:20 [Device ID: 0] Phone[0000]: Error sending TI ROM data packet request. Device API Error: 0xE003009F
04/22/12 01:53:20 ERROR: Failed flashing process. - on device ID 0.
04/22/12 01:53:20 Multi upgrade finished.

[R&D] Android bootloader on ATIV S

Introduction
After realizing that Samsumg uses the same keys to sign Android and WP8 binaries and that ATIV S has the same hardware as Snapdragon S4 SGS3, I thought about flashing SGS3 bootloader and them have access to ODIN which would permit a new set of possibilities.
Flashing ABOOT
The first step is flashing Samsumg signed ABOOT from SGS3, it's based on the (L)ittle (K)ernel and provides ODIN and fastboot.
The current issue, is flashing the ABOOT partition on top of the UEFI one from ATIV S. For this we have two possibilities:
Reverse engineer the SMD format
Create a new flasher software based on the existing one
The SMD format
Reversing SMD format seems easiest, for this I created smdc, an SMD compiler which takes a "recipe" as input.
smdc can be found at the end of this thread on GitHub.
Note: All offsets and values are based on the GT-I8750_XXBME1_R_SIGNED ROM which can be found on the forums.
Header format:
Code:
struct SMDHeader
{
CHAR Magic[16]; // Magic - 'WP8_EMMC_MainOS' 00
CHAR DeviceName[16]; // Device Name - 'GT-I8750_SIGN' 00 00 00
QWORD EndOffset; // Offset of the last byte in the file
DWORD Unknown1; // 0x16161616
DWORD PartitionCount; // Number of partitions in the "partition table"
QWORD DataStartAddress; // Offset of the data of the first partition in the file
CHAR Version[8]; // ROM Version - 'BME1' 00 00 00 00
CHAR Unknown2[16]; // Unknown
CHAR Hash[16]; // Hash of the entire file with this field zeroed
};
After the header comes the "partition table" which starts at 0x200.
Partition Table Entry format:
Code:
struct PTEntry
{
CHAR Name[16]; // Partition name
DWORD NandAddress; // Address at the eMMC
DWORD NandSize; // Size in block of 512 bytes on the eMMC
DWORD DataOffset; // Offset of the data in the file
DWORD DataSize; // Size of the data in the file
DWORD IsPresentSignature; // Not sure, name taken from WOLF smd-tool - 0x1F1F1F1F
DWORD PartitionIndex; // Index of the partition, starts at 0
DWORD FileSystem; // Not sure, name taken from WOLF smd-tool
DWORD Zero; // Unknown
CHAR Hash[16]; // MD5 hash of the partition data in the file
};
At 0x30C00, starts the signature blocks, each take 0x8000 bytes and starts with Ra000FF.
Take note that this isn't Ra000FF container format used in older phones.
Current format:
Code:
struct HashEntry
{
CHAR Magic[8]; // Magic - 'Ra000FF' 0B
DWORD Size; // Size of block¹ minus 0xA4
// Unknown fields until 0x20, zeroes until 0x64
};
¹: The "block" is the bytes starting at 0x64 that lasts until all bytes become 0
Links
GitHub repository: https://github.com/greenboxal/AtivKangTools

Reserved.

Code:
Open WP8 SMD image at : D:\!WP8\Ativ_S\FirmWare\GT-I8750_ XXBME1\test_I8750.wp8
Open WP8 SMD image at : D:\!WP8\Ativ_S\FirmWare\GT-I8750_OXXAMB1_P.csc
[Channel 0] Start Download Success !!
[Channel 0] Start AskSamsungUEFIDwonloadVersion !!
[Channel 0] UEFI version is 10 !!
[Channel 0] Start AskSecurityType !!
[Channel 0] Device Security Enable and Secure Binary!!
[Channel 0] Start AskDeviceType !!
[Channel 0] AskDeviceType is Product !!
[Channel 0] Channel Write CSC data Start!!
[Channel 0] Channel Write SER CSC data Success!!
[Channel 0] SetChecksumResultPass Success !!
[Channel 0] Channel Get GPT info !!
[Channel 0] Channel Get GPT WritePartitionData !!
[Channel 0] Channel Get SBL1 info !!
[Channel 0] Channel Get SBL1 WritePartitionData !!
[Channel 0] Channel SBL1 Write fail !!
[Channel 0] Binary Download complete!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Maybe a bug in the program disassembly SMD-tool from
-W_O_L_F-

Still needs to research and implement the hash block writing.

thought you might find this intereting.. http://forum.xda-developers.com/showthread.php?t=2345860
There is a really detailed post around here if you look for QDL mode (Qualcomm Download Mode). I was tinking about doin something like this on my 8x

Booting from SD would solve all problems, but I don't know how to force brick my ROM.
Also I don't know how to reach QDL.

spavlin said:
Code:
Open WP8 SMD image at : D:\!WP8\Ativ_S\FirmWare\GT-I8750_ XXBME1\test_I8750.wp8
Open WP8 SMD image at : D:\!WP8\Ativ_S\FirmWare\GT-I8750_OXXAMB1_P.csc
[Channel 0] Start Download Success !!
[Channel 0] Start AskSamsungUEFIDwonloadVersion !!
[Channel 0] UEFI version is 10 !!
[Channel 0] Start AskSecurityType !!
[Channel 0] Device Security Enable and Secure Binary!!
[Channel 0] Start AskDeviceType !!
[Channel 0] AskDeviceType is Product !!
[Channel 0] Channel Write CSC data Start!!
[Channel 0] Channel Write SER CSC data Success!!
[Channel 0] SetChecksumResultPass Success !!
[Channel 0] Channel Get GPT info !!
[Channel 0] Channel Get GPT WritePartitionData !!
[Channel 0] Channel Get SBL1 info !!
[Channel 0] Channel Get SBL1 WritePartitionData !!
[Channel 0] Channel SBL1 Write fail !!
[Channel 0] Binary Download complete!!
View attachment 2394557
Maybe a bug in the program disassembly SMD-tool from
-W_O_L_F-
Click to expand...
Click to collapse
SBL1 has broken signature

Actually it doesn't have a signature attached on the SMD, I didn't implement it yet

Wow, What an interesting new It sounds like a second "HD2", and if it really happen, it would be even hotter with wp8.

greenboxal said:
Booting from SD would solve all problems, but I don't know how to force brick my ROM.
Also I don't know how to reach QDL.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=820275 might help...you can try using the resistor jig.

any update of this project?

Isn't easier to make the contrary (gs3 with wp8)?

coroneta said:
any update of this project?
Click to expand...
Click to collapse
I'm currently working on my final exams, soon I'll be back on the project
gigsaw said:
Isn't easier to make the contrary (gs3 with wp8)?
Click to expand...
Click to collapse
Theoretically yes, but if I need to change something on Android to run on ATIV S I can do it easily, on the other side, WP8 isn't open source, so we can't do it without involving binary patching.
Also, I only have an ATIV S.

Do you have any progress?
Sent from my GT-I8750 using Tapatalk

Was anybody able to flash android on ativ s?

Just gonna call @GoodDayToDie here. He might know something.

3dsxlboy said:
Just gonna call @GoodDayToDie here. He might know something.
Click to expand...
Click to collapse
could we just ****ing stop bumping this thread?
The devs will post here if any progress is made, we don't need some random brony to constantly ask devs for any progress.
if you want an android device you should've bought one instead of buying the ativ s.

dude even Lumia 520 hav Qualcomm snapdragon S4+ so r u saying that would to be possible to run android on it? and it hav adreno 305 witch is the same of moto G

Luiz Guilherme Pereira said:
dude even Lumia 520 hav Qualcomm snapdragon S4+ so r u saying that would to be possible to run android on it? and it hav adreno 305 witch is the same of moto G
Click to expand...
Click to collapse
Never possible due to secure bootloaders. Even you cant flash any WP Rom on Nokia.

help not work autofocus camera

sorry for my english, I use Google translator, please help with the problem
some owners when upgrading from version 5 to 6 android started having problems with auto-focus camera
Today I discovered by chance that I had, instead of sony samsung camera module is a module
It seems that's the problem
my guess is that in 6 android support partially excluded Samsung camera module and autofocus therefore fails
or perhaps the driver of the stabilizer is not working with Samsung camera module
-- [email protected]:/ $ dmesg |grep imx
[ 8.818759][11-22_09:56:44 UTC] msm_sensor_match_id: imx214: read id failed
[ 8.898692][11-22_09:56:44 UTC] msm_sensor_match_id: imx214: read id failed
[ 8.978688][11-22_09:56:44 UTC] msm_sensor_match_id: imx214: read id failed
[ 9.015926][11-22_09:56:45 UTC] imx214 power up failed
[ 9.058758][11-22_09:56:45 UTC] msm_sensor_match_id: imx214_ofilm: read id failed
[ 9.138354][11-22_09:56:45 UTC] msm_sensor_match_id: imx214_ofilm: read id failed
[ 9.217741][11-22_09:56:45 UTC] msm_sensor_match_id: imx214_ofilm: read id failed
[ 9.255949][11-22_09:56:45 UTC] imx214_ofilm power up failed
[email protected]:/ $ dmesg |grep s5k3
[ 9.278436][11-22_09:56:45 UTC] s5k3m2_ofilm: module_id=0x10
[ 9.278444][11-22_09:56:45 UTC] msm_sensor_match_id:s5k3m2_ofilm module id: 0x10 expected id 0x10:
[ 9.278450][11-22_09:56:45 UTC] s5k3m2_ofilm probe succeeded
[ 65.685932][11-22_09:57:41 UTC] s5k3m2_ofilm: module_id=0x10
[ 65.685945][11-22_09:57:41 UTC] msm_sensor_match_id:s5k3m2_ofilm module id: 0x10 expected id 0x10:
[ 65.750562][11-22_09:57:41 UTC] s5k3m2_ofilm: module_id=0x10

I have the same problem with the camera, very bad focus, the front camera is better in most of the cases.
I have tried a lot of other camera app but nothing

Debugging issues with OmniROM build for Galaxy Tab Active 2

Hi,
I've been working on the Galaxy Tab Active 2 for some time now.
Managed to successfully build TWRP recovery for the device using the Omni sources (Big thanks to TWRP dev team).
I'm trying to build the entire rom now and flash it using TWRP.
Right now, I have successful builds giving me a ZIP file which I'm able to flash. Problem is that after the flash I get a solid frozen black screen and nothing happens.
The installation process was as follows:
1. Installed stock rom
2. Installed TWRP
3. got to recovery and wiped/formatted device
4. moved ZIP file to internal storage using adb
5. installed ZIP file
6. Wiped cache + Dalvik
Ideas?

Shedaim said:
Hi,
I've been working on the Galaxy Tab Active 2 for some time now.
Managed to successfully build TWRP recovery for the device using the Omni sources (Big thanks to TWRP dev team).
I'm trying to build the entire rom now and flash it using TWRP.
Right now, I have successful builds giving me a ZIP file which I'm able to flash. Problem is that after the flash I get a solid frozen black screen and nothing happens.
The installation process was as follows:
1. Installed stock rom
2. Installed TWRP
3. got to recovery and wiped/formatted device
4. moved ZIP file to internal storage using adb
5. installed ZIP file
6. Wiped cache + Dalvik
Ideas?
Click to expand...
Click to collapse
Could be kernel or ROM related. Try first to read kernel logs from /sys/fs/pstore after direct reboot to recovery.

golden-guy said:
Could be kernel or ROM related. Try first to read kernel logs from /sys/fs/pstore after direct reboot to recovery.
Click to expand...
Click to collapse
I have two files on pstore, one of them is encrypted and the other has two lines:
Code:
/sbin/recovery Failed to get encryption policy for /efs/recovery: Not a typewriter
I pooled dmesg through twrp recovery "Copy logs" option and got some disturbing errors, but I'm not sure they are related:
Code:
<13>[ 2.482250] [1: init: 1] init: (Initializing SELinux enforcing took 0.07s.)
<13>[ 2.485142] [5: init: 1] init: init second stage started!
<13>[ 2.490138] [5: init: 1] init: Running restorecon...
<11>[ 2.555696] [5: init: 1] init: waitpid failed: No child processes
<11>[ 2.556399] [5: init: 1] init: property_set("ro.ril.hsxpa", "1") failed
<11>[ 2.556422] [5: init: 1] init: property_set("ro.ril.gprsclass", "10") failed
<13>[ 2.556512] [5: init: 1] init: (Loading properties from /default.prop took 0.00s.)
<11>[ 2.557046] [5: init: 1] init: /init.rc: 13: invalid keyword 'setcon'
<11>[ 2.557197] [5: init: 1] init: /init.rc: 63: invalid keyword 'load_all_props'
<11>[ 2.557397] [5: init: 1] init: could not import file '/init.recovery.logd.rc' from '/init.rc': No such file or directory
<13>[ 2.557594] [5: init: 1] init: (Parsing /init.recovery.usb.rc took 0.00s.)
<13>[ 2.557660] [5: init: 1] init: (Parsing /init.recovery.service.rc took 0.00s.)
<11>[ 2.557696] [5: init: 1] init: could not import file '/init.recovery.vold_decrypt.rc' from '/init.rc': No such file or directory
<11>[ 2.557730] [5: init: 1] init: could not import file '/init.recovery.samsungexynos7870.rc' from '/init.rc': No such file or directory
<13>[ 2.557753] [5: init: 1] init: (Parsing /init.rc took 0.00s.)
<13>[ 2.557893] [5: init: 1] init: write_file: Unable to write to '/sys/fs/selinux/checkreqprot': Permission denied
<13>[ 2.557963] [5: init: 1] init: Starting service 'ueventd'...
<13>[ 2.558331] [5: init: 1] init: Starting service 'healthd'...
<13>[ 2.558659] [5: init: 1] init: Waiting for /dev/.coldboot_done...
I'll try fixing those errors, but I don't believe it'll fix my main problem.

Shedaim said:
I have two files on pstore, one of them is encrypted and the other has two lines:
Code:
/sbin/recovery Failed to get encryption policy for /efs/recovery: Not a typewriter
I pooled dmesg through twrp recovery "Copy logs" option and got some disturbing errors, but I'm not sure they are related:
Code:
<13>[ 2.482250] [1: init: 1] init: (Initializing SELinux enforcing took 0.07s.)
<13>[ 2.485142] [5: init: 1] init: init second stage started!
<13>[ 2.490138] [5: init: 1] init: Running restorecon...
<11>[ 2.555696] [5: init: 1] init: waitpid failed: No child processes
<11>[ 2.556399] [5: init: 1] init: property_set("ro.ril.hsxpa", "1") failed
<11>[ 2.556422] [5: init: 1] init: property_set("ro.ril.gprsclass", "10") failed
<13>[ 2.556512] [5: init: 1] init: (Loading properties from /default.prop took 0.00s.)
<11>[ 2.557046] [5: init: 1] init: /init.rc: 13: invalid keyword 'setcon'
<11>[ 2.557197] [5: init: 1] init: /init.rc: 63: invalid keyword 'load_all_props'
<11>[ 2.557397] [5: init: 1] init: could not import file '/init.recovery.logd.rc' from '/init.rc': No such file or directory
<13>[ 2.557594] [5: init: 1] init: (Parsing /init.recovery.usb.rc took 0.00s.)
<13>[ 2.557660] [5: init: 1] init: (Parsing /init.recovery.service.rc took 0.00s.)
<11>[ 2.557696] [5: init: 1] init: could not import file '/init.recovery.vold_decrypt.rc' from '/init.rc': No such file or directory
<11>[ 2.557730] [5: init: 1] init: could not import file '/init.recovery.samsungexynos7870.rc' from '/init.rc': No such file or directory
<13>[ 2.557753] [5: init: 1] init: (Parsing /init.rc took 0.00s.)
<13>[ 2.557893] [5: init: 1] init: write_file: Unable to write to '/sys/fs/selinux/checkreqprot': Permission denied
<13>[ 2.557963] [5: init: 1] init: Starting service 'ueventd'...
<13>[ 2.558331] [5: init: 1] init: Starting service 'healthd'...
<13>[ 2.558659] [5: init: 1] init: Waiting for /dev/.coldboot_done...
I'll try fixing those errors, but I don't believe it'll fix my main problem.
Click to expand...
Click to collapse
You should definitely do your bringup with permissive selinux. Just when everything is working, fix all remaining denials and switch to enforcing.
Ah, this is just recovery logs. Still, worth to check for your build.

golden-guy said:
You should definitely do your bringup with permissive selinux. Just when everything is working, fix all remaining denials and switch to enforcing.
Ah, this is just recovery logs. Still, worth to check for your build.
Click to expand...
Click to collapse
Do you have a good guide to boot with permissive mode? I've tried some flags in the device's kernel config, but all get overwritten at boot.
Well, those are the kernel logs taken from the recovery.
EDIT: tried changing selinux flags in kernel config file + changed EXTRA_CFLAGS += -DCONFIG_ALWAYS_ENFORCE to false in kernel/security/selinux/Makefile.
problem is that if I do that, TWRP get's stuck in a bootloop.

Shedaim said:
Do you have a good guide to boot with permissive mode? I've tried some flags in the device's kernel config, but all get overwritten at boot.
Well, those are the kernel logs taken from the recovery.
EDIT: tried changing selinux flags in kernel config file + changed EXTRA_CFLAGS += -DCONFIG_ALWAYS_ENFORCE to false in kernel/security/selinux/Makefile.
problem is that if I do that, TWRP get's stuck in a bootloop.
Click to expand...
Click to collapse
Normally, you set this in BOARD_KERNEL_CMDLINE in your BoardConfig.mk and it does apply. Best check some other (Samsung) device trees and kernel configs.

golden-guy said:
Normally, you set this in BOARD_KERNEL_CMDLINE in your BoardConfig.mk and it does apply. Best check some other (Samsung) device trees and kernel configs.
Click to expand...
Click to collapse
can't put anything on the BOARD_KERNEL_CMDLINE for exynos devices.

@golden-guy
Care to take a look at my github? I may be missing something. https://github.com/Shedaim/gtactive2lte.git
The kernel's configuration I'm using is in the following path: /kernel/arch/arm64/configs/exynos7870-gtactive2lte_eur_open_defconfig
I tried creating only the kernel and put inside stock boot.img replacing stock zImage, but it automatically boots to recovery after failed boot.
If I try to build the rom with version 1 recovery.fstab, I successfully get the zip file, but I got these warnings/prints:
Code:
Package OTA: /home/roni/Full_Omni/out/target/product/gtactive2lte/omni_gtactive2lte-ota-eng.root.zip
/efs: unknown option "flags=display=EFS;backup=1"
/data: unknown option "flags=encryptable=footer;length=-20480"
/modem: unknown option "flags=display=MODEM"
/preload: unknown option "flags=display="Preload";wipeingui;backup=1"
/external_sdcard: unknown option "flags=display="Micro"
/usb-otg: unknown option "flags=display="USB-OTG";storage;wipeingui;removable"
unzipping target target-files...
running: unzip -o -q /home/roni/Full_Omni/out/target/product/gtactive2lte/obj/PACKAGING/target_files_intermediates/omni_gtactive2lte-target_files-eng.root.zip -d /tmp/targetfiles-5NhyYa
/efs: unknown option "flags=display=EFS;backup=1"
/data: unknown option "flags=encryptable=footer;length=-20480"
/modem: unknown option "flags=display=MODEM"
/preload: unknown option "flags=display="Preload";wipeingui;backup=1"
/external_sdcard: unknown option "flags=display="Micro"
/usb-otg: unknown option "flags=display="USB-OTG";storage;wipeingui;removable"

Shedaim said:
@golden-guy
Care to take a look at my github? I may be missing something. https://github.com/Shedaim/gtactive2lte.git
The kernel's configuration I'm using is in the following path: /kernel/arch/arm64/configs/exynos7870-gtactive2lte_eur_open_defconfig
I tried creating only the kernel and put inside stock boot.img replacing stock zImage, but it automatically boots to recovery after failed boot.
If I try to build the rom with version 1 recovery.fstab, I successfully get the zip file, but I got these warnings/prints:
Click to expand...
Click to collapse
You got to find out how to make a permissive kernel for Sammy devices, I won't do that research for you. Also if pstore is empty, you might need to enable this in defconfig first.
Btw, kernel repo need to be seperate from device tree.

golden-guy said:
You got to find out how to make a permissive kernel for Sammy devices, I won't do that research for you. Also if pstore is empty, you might need to enable this in defconfig first.
Btw, kernel repo need to be seperate from device tree.
Click to expand...
Click to collapse
It may be best practice to have it separated, but I see no wrong in linking the TARGET_KERNEL_SOURCE to the device tree. I mean, it's just a path.
Hmm, I think it is loading in permissive mode (see last line). This is a log taken from recovery, which was built using the same tree and kernel configuration.
Code:
MODEL_NAME:{{SM-T395}}
eMMC_SERIAL_NUMBER:{{150100414A5444345200DB205BCAC461}}
[Debug Info.]
S-BOOT : VERSION_-+J0
SecureOS : 32 (MB)
blk_bread: MMC mode
- read_bl1
blk_bread_bootsector: MMC mode
Verify_Signature_With_Signingtype 0x45820130 [email protected], [email protected]
pit_check_signature (PIT) valid.
blk_bread: MMC mode
PARAM ENV VERSION: v1.0..
RECOVERY IS NOT SEANDROID ENFORCING
RECOVERY IS NOT SEANDROID ENFORCING
ATAG_CMDLINE: 103 54410009 'console=ram loglevel=4 bootmode=2 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c ess_setup=0x46000000 [email protected] [email protected] s3cfb.bootloaderfb=0x67000000 sysscope=0xee000000 lcdtype=812552 consoleblank=0 vmalloc=384m sec_debug.reset_reason=6 sec_reset.reset_reason=6 ehci_hcd.park=3 oops=panic pmic_info=27 ccic_info=1 cordon=eeeb5ced9430d2cfe0bf16a079f70608 connie=SM-T395_OPEN_EUR_63e3f4ca8271d4c7e2d2c3239cb7fb2e androidboot.emmc_checksum=3 androidboot.sales.param.offset=7340572 sales_code=ILO androidboot.odin_download=1 androidboot.bootloader=T395JXU1AQJ2 androidboot.selinux=enforcing androidboot.security_mode=1526595585 androidboot.ucs_mode=0 androidboot.hw_rev=4 androidboot.hardware=samsungexynos7870 androidboot.warranty_bit=1 androidboot.hmac_mismatch=0 androidboot.sec_atd.tty=/dev/ttySAC2 androidboot.serialno=5200db205bcac461 snd_soc_core.pmdown_time=1000 androidboot.verifiedbootstate=orange reserve-fimc=0 firmware_class.path=/vendor/firmware'
param logs:
<6>[ 0.000000] [0: swapper: 0] Initializing cgroup subsys cpu
<6>[ 0.000000] [0: swapper: 0] Initializing cgroup subsys cpuacct
<5>[ 0.000000] [0: swapper: 0] Linux version 3.18.14 ([email protected]) (gcc version 4.9 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Sun Jul 29 16:36:16 IDT 2018
<4>[ 0.000000] [0: swapper: 0] CPU: AArch64 Processor [410fd034] revision 4
<6>[ 0.000000] [0: swapper: 0] Detected VIPT I-cache on CPU0
<6>[ 0.000000] [0: swapper: 0] alternative: enabling workaround for ARM erratum 845719
<6>[ 0.000000] [0: swapper: 0] [ECT] Address 90000000, Size 14000setup_bootmode: boot_mode is 0
<4>[ 0.000000] [0: swapper: 0] setup_bootmode: boot_mode is 2
<6>[ 0.000000] [0: swapper: 0] dsim: --- Parse LCD TYPE ---
<6>[ 0.000000] [0: swapper: 0] dsim: LCDTYPE : 000c6608
<4>[ 0.000000] [0: swapper: 0] val = 49
<6>[ 0.000000] [0: swapper: 0] Security Boot Mode
<3>[ 0.000000] [0: swapper: 0] modem_if_reserved_mem_setup: memory reserved: paddr=4026531840, t_size=125829120
<6>[ 0.000000] [0: swapper: 0] Reserved memory: initialized node modem_if, compatible id exynos7870,modem_if
<3>[ 0.000000] [0: swapper: 0] deliver_cp_reserved_mem_setup: memory reserved: paddr=4026527744, t_size=4096
<6>[ 0.000000] [0: swapper: 0] Reserved memory: initialized node dram_init, compatible id exynos7870,deliver_cp
<6>[ 0.000000] [0: swapper: 0] cma: CMA: reserved 8 MiB at 80000000
<6>[ 0.000000] [0: swapper: 0] CMA memory[1]: crypto:0x800000
<6>[ 0.000000] [0: swapper: 0] Reserved memory: initialized node crypto, compatible id exynos8890-ion,crypto
<6>[ 0.000000] [0: swapper: 0] cma: CMA: reserved 4 MiB at 80800000
<6>[ 0.000000] [0: swapper: 0] CMA memory[2]: video_fw:0x400000
<6>[ 0.000000] [0: swapper: 0] Reserved memory: initialized node video_fw, compatible id exynos8890-ion,vfw
<6>[ 0.000000] [0: swapper: 0] cma: CMA: reserved 4 MiB at 80c00000
<6>[ 0.000000] [0: swapper: 0] CMA memory[7]: video_nfw:0x400000
<6>[ 0.000000] [0: swapper: 0] Reserved memory: initialized node video_nfw, compatible id exynos8890-ion,vnfw
<6>[ 0.000000] [0: swapper: 0] cma: CMA: reserved 16 MiB at 81000000
<6>[ 0.000000] [0: swapper: 0] CMA memory[3]: video_stream:0x1000000
<6>[ 0.000000] [0: swapper: 0] Reserved memory: initialized node video_stream, compatible id exynos8890-ion,vstream
<6>[ 0.000000] [0: swapper: 0] cma: CMA: reserved 84 MiB at 82000000
<6>[ 0.000000] [0: swapper: 0] CMA memory[5]: video_frame:0x5400000
<6>[ 0.000000] [0: swapper: 0] Reserved memory: initialized node video_frame, compatible id exynos8890-ion,vframe
<6>[ 0.000000] [0: swapper: 0] cma: CMA: reserved 28 MiB at 87400000
<6>[ 0.000000] [0: swapper: 0] CMA memory[6]: video_scaler:0x1c00000
<6>[ 0.000000] [0: swapper: 0] Reserved memory: initialized node video_scaler, compatible id exynos8890-ion,vscaler
<6>[ 0.000000] [0: swapper: 0] cma: CMA: reserved 16 MiB at ff000000
<7>[ 0.000000] [0: swapper: 0] On node 0 totalpages: 776192
<7>[ 0.000000] [0: swapper: 0] DMA zone: 10752 pages used for memmap
<7>[ 0.000000] [0: swapper: 0] DMA zone: 0 pages reserved
<7>[ 0.000000] [0: swapper: 0] DMA zone: 776192 pages, LIFO batch:31
<6>[ 0.000000] [0: swapper: 0] psci: probing for conduit method from DT.
<6>[ 0.000000] [0: swapper: 0] psci: Using PSCI v0.1 Function IDs from DT
<6>[ 0.000000] [0: swapper: 0] PERCPU: Embedded 14 pages/cpu @ffffffc0beed1000 s18752 r8192 d30400 u57344
<7>[ 0.000000] [0: swapper: 0] pcpu-alloc: s18752 r8192 d30400 u57344 alloc=14*4096
<7>[ 0.000000] [0: swapper: 0] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7
<4>[ 0.000000] [0: swapper: 0] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 765440
Kernel command line: console=ram loglevel=4 bootmode=2 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c ess_setup=0x46000000 [email protected] [email protected] s3cfb.bootloaderfb=0x67000000 sysscope=0xee000000 lcdtype=812552 consoleblank=0 vmalloc=384m sec_debug.reset_reason=6 sec_reset.reset_reason=6 ehci_hcd.park=3 oops=panic pmic_info=27 ccic_info=1 cordon=eeeb5ced9430d2cfe0bf16a079f70608 connie=SM-T395_OPEN_EUR_63e3f4ca8271d4c7e2d2c3239cb7fb2e androidboot.emmc_checksum=3 androidboot.sales.param.offset=7340572 sales_code=ILO androidboot.odin_download=1 androidboot.bootloader=T395JXU1AQJ2 androidboot.selinux=enforcing androidboot.security_mode=1526595585 androidboot.ucs_mode=0 androidboot.hw_rev=4 androidboot.hardware=samsungexynos7870 androidboot.warranty_bit=1 androidboot.hmac_mismatch=0 androidboot.sec_atd.tty=/dev/ttySAC2 androidboot.serialno=5200db205bcac461 snd_soc_core.pmdown_time=1000 androidboot.v<6>[ 0.000000] [0: swapper: 0] ../../../../../../device/samsung/gtactive2lte/kernel/drivers/staging/samsung/sec_debug.c: Reserved Mem(0x40000000, 0x1000) - Success
<0>[ 0.000000] [0: swapper: 0] sec_debug: set magic code (0x66262564)
<6>[ 0.000000] [0: swapper: 0] exynos-snapshot: try to reserve dedicated memory : 0x46000000, 0x1000000
<6>[ 0.000000] [0: swapper: 0] exynos-snapshot: memory reserved complete : 0x46000000, 0x1000000
<6>[ 0.000000] [0: swapper: 0] sec_debug: GetLog support (mark:0xffffffc000f25938, klog: 0xffffffc006800000)
<6>[ 0.000000] [0: swapper: 0] tima :sec_tima_log_setup, base:47002000, size:200000
<6>[ 0.000000] [0: swapper: 0] RKP :tima_setup_rkp_mem, base:52300000, size:40000
<6>[ 0.000000] [0: swapper: 0] RKP :tima_setup_rkp_mem, base:52400000, size:7000
<6>[ 0.000000] [0: swapper: 0] RKP :tima_setup_rkp_mem, base:4da00000, size:300000
<6>[ 0.000000] [0: swapper: 0] RKP :tima_setup_rkp_mem, base:52407000, size:1000
<6>[ 0.000000] [0: swapper: 0] RKP :tima_setup_rkp_mem, base:52408000, size:5f8000
<6>[ 0.000000] [0: swapper: 0] RKP :tima_setup_rkp_mem, base:4dd00000, size:100000
<6>[ 0.000000] [0: swapper: 0] sec_avc_log_setup: *sec_avc_log_ptr:5cc8 sec_avc_log_buf:ffffffc007204000 sec_log_size:0x40000
<6>[ 0.000000] [0: swapper: 0] sec_avc_log_setup: no old log found
<6>[ 0.000000] [0: swapper: 0] set_switch_sel: switch_sel: 0x01b
<6>[ 0.000000] [0: swapper: 0] set_ccic_info: ccic_info: 0x0001
<1>[ 0.000000] [0: swapper: 0] vmm_init
<1>[ 0.000000] [0: swapper: 0] bin 0xffffffc000da4000, 0x4a808
<1>[ 0.000000] [0: swapper: 0] ram 0xffffffc00dd00000, 0x100000
<1>[ 0.000000] [0: swapper: 0] vmm, 312176
<1>[ 0.000000] [0: swapper: 0] vmm_translate
<1>[ 0.000000] [0: swapper: 0] vmm_translate
<1>[ 0.000000] [0: swapper: 0] vmm_entry
<1>[ 0.000000] [0: swapper: 0] vmm entry point: 000000004dd01290
<1>[ 0.000000] [0: swapper: 0] vmm(000000004dd00000, 0x100000): 0
<6>[ 0.000000] [0: swapper: 0] PID hash table entries: 4096 (order: 3, 32768 bytes)
<6>[ 0.000000] [0: swapper: 0] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
<6>[ 0.000000] [0: swapper: 0] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
<4>[ 0.000000] [0: swapper: 0] Memory: 2693600K/3104768K available (9152K kernel code, 1037K rwdata, 4616K rodata, 408K init, 2885K bss, 411168K reserved)
<5>[ 0.000000] [0: swapper: 0] Virtual kernel memory layout:
<5>[ 0.000000] [0: swapper: 0] vmalloc : 0xffffff8000000000 - 0xffffffbdffff0000 ( 247 GB)
<5>[ 0.000000] [0: swapper: 0] vmemmap : 0xffffffbe00000000 - 0xffffffbfc0000000 ( 7 GB maximum)
<5>[ 0.000000] [0: swapper: 0] 0xffffffbe00e00000 - 0xffffffbe03800000 ( 42 MB actual)
<5>[ 0.000000] [0: swapper: 0] PCI I/O : 0xffffffbffa000000 - 0xffffffbffb000000 ( 16 MB)
<5>[ 0.000000] [0: swapper: 0] fixed : 0xffffffbffbdfe000 - 0xffffffbffbdff000 ( 4 KB)
<5>[ 0.000000] [0: swapper: 0] modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB)
<5>[ 0.000000] [0: swapper: 0] memory : 0xffffffc000000000 - 0xffffffc0c0000000 ( 3072 MB)
<5>[ 0.000000] [0: swapper: 0] .init : 0xffffffc000df3000 - 0xffffffc000e59000 ( 408 KB)
<6>[ 0.000000] [0: swapper: 0] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
<6>[ 0.000000] [0: swapper/0: 0] Preemptible hierarchical RCU implementation.
<6>[ 0.000000] [0: swapper/0: 0] NR_IRQS:64 nr_irqs:64 0
<6>[ 0.000000] [0: swapper/0: 0] ========================================
<6>[ 0.000000] [0: swapper/0: 0] =
<6>[ 0.000000] [0: swapper/0: 0] = [ECT] current version is TEST VERSION!!
<6>[ 0.000000] [0: swapper/0: 0] = Please be aware that error can be happen.
<6>[ 0.000000] [0: swapper/0: 0] = [VERSION] : 1001
<6>[ 0.000000] [0: swapper/0: 0] =
<6>[ 0.000000] [0: swapper/0: 0] ========================================
<6>[ 0.000000] [0: swapper/0: 0] asv_table_ver : 5
<6>[ 0.000000] [0: swapper/0: 0] fused_grp : 1
<6>[ 0.000000] [0: swapper/0: 0] cpucl0_asv_group : 7
<6>[ 0.000000] [0: swapper/0: 0] cpucl1_asv_group : 7
<6>[ 0.000000] [0: swapper/0: 0] g3d_asv_group : 7
<6>[ 0.000000] [0: swapper/0: 0] mif_asv_group : 7
<6>[ 0.000000] [0: swapper/0: 0] int_asv_group : 7
<6>[ 0.000000] [0: swapper/0: 0] disp_asv_group : 5
<3>[ 0.000000] [0: swapper/0: 0] cal_dfs_get_rate : dvfs_cam reference count is zero
<3>[ 0.000000] [0: swapper/0: 0] cal_dfs_get_rate : dvfs_disp reference count is zero
<6>[ 0.000000] [0: swapper/0: 0] EXYNOS7870: Clock setup completed
<6>[ 0.000000] [0: swapper/0: 0] Exynos: pwm: clock setup completed
<6>[ 0.000000] [0: swapper/0: 0] arch_timer_init: arch_timer is used only clocksource
<6>[ 0.000000] [0: swapper/0: 0] Architected cp15 timer(s) running at 26.00MHz (virt).
<6>[ 0.000004] [0: swapper/0: 0] sched_clock: 56 bits at 26MHz, resolution 38ns, wraps every 2643056787456ns
<6>[ 0.002320] [0: swapper/0: 0] Enable console clock to add reference count
<6>[ 0.002352] [0: swapper/0: 0] Calibrating delay loop (skipped), value calculated using timer frequency.. 52.00 BogoMIPS (lpj=260000)
<6>[ 0.002364] [0: swapper/0: 0] pid_max: default: 32768 minimum: 301
<6>[ 0.005573] [0: swapper/0: 0] Security Framework initialized
<6>[ 0.005590] [0: swapper/0: 0] SELinux: Initializing.
<7>[ 0.005628] [0: swapper/0: 0] SELinux: Starting in [B]permissive [/B]mode

Shedaim said:
It may be best practice to have it separated, but I see no wrong in linking the TARGET_KERNEL_SOURCE to the device tree. I mean, it's just a path.
Hmm, I think it is loading in permissive mode (see last line). This is a log taken from recovery, which was built using the same tree and kernel configuration.
Click to expand...
Click to collapse
Enable this first: https://github.com/Shedaim/gtactive...nos7870-gtactive2lte_eur_open_defconfig#L4189
Then grab console logs via twrp.
Seriously, you definitely should split up your repos. There's good reason to keep that modular. Make it right from the beginning, or don't do it at all.

I cannot install any app because I've uninstalled system guard app [rooted device]

By running logcat while attempting to re-install the guard app (com.miui.guardprovider), I see the followin error (FYI I see this error when installing any app):
Code:
[ 01-21 03:49:18.090 1462: 2549 I/ActivityManager ]
START u0 {dat=file:///storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk cmp=com.google.android.packageinstaller/com.android.packageinstaller.InstallAppProgress (has extras)} from uid 10023 on display 0
[ 01-21 03:49:18.095 1462: 2549 D/ActivityTrigger ]
ActivityTrigger activityPauseTrigger
[ 01-21 03:49:18.098 3467: 3501 I/Finsky ]
[25] com.google.android.finsky.bo.an.run(6): Stats for Executor: NotificationAssistDatabaseManager [email protected][Running, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 6]
[ 01-21 03:49:18.106 1462: 2301 I/Timeline ]
Timeline: App_transition_ready time:1710168
[ 01-21 03:49:18.120 11313:11313 W/ResourceType ]
No package identifier when getting name for resource number 0x00000000
[ 01-21 03:49:18.124 1462: 2507 W/ResourceType ]
No package identifier when getting name for resource number 0x00000000
[ 01-21 03:49:18.125 1462: 2507 W/ ]
Unable to open '/storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk': Permission denied
[ 01-21 03:49:18.125 1462: 2507 W/zipro ]
Error opening archive /storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk: I/O Error
[ 01-21 03:49:18.125 1462: 2507 D/asset ]
failed to open Zip archive '/storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk'
[ 01-21 03:49:18.129 2724: 2724 W/ContextImpl ]
Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:788 android.content.ContextWrapper.sendBroadcast:411 android.content.ContextWrapper.sendBroadcast:411 com.miui.permcenter.install.PackageVerificationRecevier.ar:-1 com.miui.permcenter.install.PackageVerificationRecevier.onReceive:-1
[ 01-21 03:49:18.135 1462: 2332 W/ActivityManager ]
cann't getContentProviderImpl: guard, cpi is null.
[ 01-21 03:49:18.135 2724: 9453 E/ActivityThread ]
Failed to find provider info for guard
[ 01-21 03:49:18.135 2724: 9453 E/PackageVerifyedRecevier ]
parseApk
java.lang.IllegalArgumentException: Unknown URI content://guard
at android.content.ContentResolver.call(ContentResolver.java:1424)
at com.miui.permcenter.install.q.doInBackground(Unknown Source)
at com.miui.permcenter.install.q.doInBackground(Unknown Source)
at android.os.AsyncTask$2.call(AsyncTask.java:295)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
[ 01-21 03:49:18.135 2724: 9453 D/PackageVerifyedRecevier ]
verify package /storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk info: null
[ 01-21 03:49:18.135 2724: 9453 D/PackageVerifyedRecevier ]
verify package /storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk finish false
[ 01-21 03:49:18.136 1462: 2507 I/com.android.server.pm.PackageManagerServiceInjector ]
MIUILOG- INSTALL_FAILED_VERIFICATION_FAILURE uid: 10023 pkg : com.google.android.packageinstaller
[ 01-21 03:49:18.138 9998: 9998 D/PackageVerificationReceiver ]
PackageVerificationReceiver onReceive:Intent { act=com.miui.global.packageinstaller.action.verifypackage flg=0x10 cmp=com.miui.global.packageinstaller/.PackageVerificationReceiver }
Would it be possible to skip resolving the content://guard link? I've already tried to go to Settings -> System apps settings -> Security -> Security scan and unchecked the "Scan before installing" button, but the error is still the same :/
Any ideas how to fix this?
Btw, I've tried to post this to the development section, but I was rejected due to the fresh account, so that's why I'm writing here.

Dirty flash the ROM means just wipe catches and dalvic catches and flash ROM zip again.