yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] BrunoWestone:
The ultimate TEST

Ok my friends, i'm back with more news !!!!!

3 Phones, 2 Jtag Box's (Riff and Z3X) lots of patience and faith…

1st Phone - Knoxed with couter voided 0x1:

(3 tries)

eMMC Full erase - successfully

Writing Boot files - successfully with XXUAME2, XXUDMHB or XXUEMJ3

Phone turning one - Unsuccessfully

Download mode - …nope

Only enter download mode again when i write the XXEMJ5 boot files (knoxed Bootloader)

Result : Counter remains 0x1

2nd Phone: - Also Knoxed with counter voided

Full 0x0000000000 to 0x0003AB4000 erase - successfully (Full Chip)

Writing Boot files - successfully with XXUAME2, XXUDMHB or XXUEMJ3

Phone turning one - Unsuccessfully

Download mode - …nope

Only enter download mode again when i write the XXEMJ5 boot files (knoxed Bootloader)

And guess what… Result : Counter remains 0x1

3nd Phone: - 4.2.2 Un-knoxed bootloader

eMMC Full erase - successfully

Writing Boot files - successfully with XXUAME2, XXUDMHB or XXUEMJ3

Phone turning one - Unsuccessfully

Download mode - …Successfully

Enter download mode with every boot file

Result : Bootloader successfully downgraded from a non-knoxed one to a non-knoxed boot loader ( pretty much the same as nothing accomplished...

Now there is 2 viable options here:

1st - I mess up with this

or

2nd - This won't reset knox at all

You decide witch one it is and let me know, please

Regards,
[Galaxy S 4 General] note2nooby:
I lurk a lot on jtag forum , but i guess it wont work ... nobody confirmed it already over there so i guess its hidden somewhere else not in the emmc.

so no download mode ..

and this tool i guess its no way to flash to emmc things ... things like pda phone csc

you do it like this right ?

0) format

1) pit file, (check repartition)

2) boot loader,

3) Pda,

4) phone,

5) csc.

Edit : and you use 1,99 version of the software ?

Edit : what you trying to do is brand new, its only month or two old , this whole 4.3, give it some time.

on one side is good to know knox is so hard to knock out , at least our devices are ,,protected''
[Galaxy S 4 General] vim1:
WHat tool you use for full erase chip ?
[Galaxy S 4 General] chudy_85:
[MENTION=5584002]BrunoWestone[/MENTION]

Do you try do it nandbackup from non knoxed emmc and put to emmc with knox to 0x1 when you erase emmc ???
[Galaxy S 4 General] bungadudu:
NoName retracted his obvious statement.

Knox can't be reseted with jtag!

(at least for the moment!)

http://forum.gsmhosting.com/vbb/showthread.php?p=10053668
[Galaxy S 4 General] vpwrf:
What happened to the attachment links? Why does it say "Invalid Attachment specified"?

EDIT: Links fixed.
[Galaxy S 4 General] mahmoud007:
you should check Nand Erease all and use pit file for your device and check re-partition on odin after you erease full memory

otherwise device wont recognize the Rom and where to install .. and your Efs file would be gone .which is big problem if you didn't back it up
[Galaxy S 4 General] mayotube:
Okay. The point is... Knox cant be reset for the moment.

But maybe it is possible to downgrade a S4 with knox 0x0 to old bootloader?

Bruno only tried to downgrade knox warranty voided phones.

Just could be nice if NoName would buy an S4 and will try to downgrade by himself.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 General] ozzyblack:
I Have a jtag from the S2 time shall i try.
[Galaxy S 4 General] OzGurKan:
stupid me...got the phone with 4.2.2 stock. no updates available (i9505) tested a lot of custom roms, then i said : lets try 4.3 stock ...now i have KNOX :)) didnt have it before :P

at least is 0x0 so its not void

PS. If i root and install a custom rom , flag becomes 0x1 ? or i must update bootloader etc ?
[Galaxy S 4 General] Irwenzhao:
Custom ROMs will trip it. Rooting may or may not trip the flag depending on what method u use.

Smack that Thanks button if I helped!

KitKat came in on my OmniROM, running on my Note 2.

Sent from a small country called Singapore.

P.S. Time for school, not much time for XDA :(
[Galaxy S 4 General] kenshiroSG24:
Knox reset

If samsung can reset the knox flag then there must be a way to reset it ourselves. Either get our hands on the software they use or just take your phone back to them each time you want to reset it!!!
[Galaxy S 4 General] BrunoWestone:
See, I told you mate !!

Samsung 1 - 0 Rerst of the world
[Galaxy S 4 General] BrunoWestone:
You're right mate. There is several reports of people that gets the phones reseted in 3 minutes in Samsung centers. But let me tell you that is still a big secret how they do it. I have a good friend in Samsung (LCD Area) and he doesn't know how the guys from software do it.

I can tell you that on of the biggest client of the company i work for here in UK is a Samsung official Service centre and they don't have any instruction on how to reset knox.

Samsung is keeping the secret in a very secure safe (maybe they have they're own knox container with the secret inside… lol)

Anyway, the story of mobile technologies tell us that there is no such things as secrets that last forever inside the headquarters of a Major retailer as Samsung. It is simple as they fire the wrong guy and the world will know how they do it.

I'm working with mobile phones since 1996, so believe me: WE WILL HAVE THE SOLUTION !

Its just a matter of time….

Best Regards,
[Galaxy S 4 General] mahmoud007:
Knox

so this is what happen on my GT-I9505 after nand erase all checked with pit file and repartition checked and efs backup for cautious reasons and install 4.2.2 rebuild original rom ... device wont start up .. so i go to recovery mode and it was successfully back to 4.2.2 recovery

this is what i found :

i did wipe data/factory reset

but when i tried to wipe cache partition it forces device to restart without my control !!! never happen on 4.3 recovery mode .

so i restarted & entered recovery mode again ... normally the red code would be gone since i format the data partition

but the wipe cache partition still reboots when i try to format !!

any thoughts ??

could be related to the KWV counter since 4.2.2 does not have it !!
[Galaxy S 4 General] BrunoWestone:
Did you backup your EFS Folder ?

You erase Nand with ODIN ?

I don't want to scare you but that is not a good sign….
[Galaxy S 4 General] mahmoud007:
umm did you read the post correctly ??

my device still working and rooted

im trying to figure out modem problem but i thought this would be interested for kwv research

cache wipe is not working after downgrade and there is a reason
[Galaxy S 4 General] :
Try to flash a low level firmware with PIT file and "Re-Partition", but without "NAND erase all", then everything should work fine again.

Gesendet von meinem Nexus 5 mit Tapatalk 2
[Galaxy S 4 General] BrunoWestone:
Maybe i get it all wrong, but you are unable to wipe cache thats correct ?

So, put the EFS folder backup on the phone and it should be ok.
[Galaxy S 4 General] chudy_85:
When i have 4.2.2 i have that same When do it wipe cache. You have new bootloader 4.3 and tell me when you do it wipe data/factory reset do you have errors?

Wysłane z mojego GT-I9505 przy użyciu Tapatalka
[Galaxy S 4 General] Ekizov:
Do you know exactly what is efs

Hardly anyone will give it here
[Galaxy S 4 General] fstorm:
It contains things such as the IMEI. No one really should give away their efs...

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S 4 General] Ekizov:
exactly what I'm saying
[Galaxy S 4 General] fstorm:
Sorry I misread that

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S 4 General] mahmoud007:
Knox

if someone have i9505 4.2.2 JB rooted

install busybox

install terminal or use adb

and write these codes :

# su
# dd if=/dev/block/mmcblk0p6 of=/storage/sdcard0/aboot.mbn
# dd if=/dev/block/mmcblk0p8 of=/storage/sdcard0/tz.mbn

and then go to phone memory then youll find aboot.mbn & tz.mbn files

please send them to me or post it on forum
[Galaxy S 4 General] chudy_85:
why you need this file from smartfone??? I ask you because this file you have in room for odin when you open tar file
[Galaxy S 4 General] mahmoud007:
I need them for some tests

Dont worry it contains no personal data
[Galaxy S 4 General] :
He is extracting bootloader and other boot partition of 4.2.2 probably he will extract 4.3's too then do something.Good idea :good:
[Galaxy S 4 General] sangalaviral:
I will post both the files here soon

---------- Post added at 10:44 PM ---------- Previous post was at 10:26 PM ----------

https://www.dropbox.com/sh/xkkphshyatzocv7/OIZVTSeKXa
[Galaxy S 4 General] mahmoud007:
knox

unfortunately it didn't work

but since we know its an secure storage that have all the secrets about this counter and eMMC writing issue

doesn't Linux mainly treats storage's "whatever secure or non secure " doesn't treat them as devices ??

and they must have mounted point ??

where is that mounted point of the secure storage ?

i could swear when i first purchased my device my storage was 16 gb and it says that on the storage info on settings .

it was the first thing i noticed ,after knowing storage issues and decreasing in the past , i thought that issue was fixed !!

but i didn't looked at it when i upgraded , never thought about doing some research about the new upgrade .

but it was 16 gb before upgrading !!
[Galaxy S 4 General] mahmoud007:
since that knox is hidden secure storage .. what if it has different file system beside ext ??

odin cant reach ??

EDIT:

this is a picture from eMMC check ... it gives me the real size of my memory !!

what is going on ??
[Galaxy S 4 General] sangalaviral:
Without Knox.
[Galaxy S 4 General] mahmoud007:
im almost there

i just found the fully main storage mount point and it looks like its not mounted at all !!

i suspect its been divided ..

the mount point for the full emmc storage is /dev/block/mmcblk0

even tho its not mounted ... i couldn't mount it to mnt at all

i get this error : device or resource busy

and whats the story of zram0 mount point ?? what is it for ??

i feel like im reaching in
[Galaxy S 4 General] bungadudu:
Lol

This is a lame research thread :-|

I guess there is a 50/1 raport between simple chit chat/already responded to questions and a actual data/work/ideas on how to reset knox.

I'll just say it one more time: this is a research thread!

For noobish questions and discussion about knox see this threads:

http://xdaforums.com/showthread.php?t=2504258

http://xdaforums.com/showthread.php?t=2517816
[Galaxy S 4 General] mahmoud007:
is there a way to use any mkfs 's command to format i9505 emmc back to scratch on download or recovery mode " while emmc shut " ??

i did my backups on efs and everything important + have repartition pit file ... now im looking for a way to get rued of the secret partition and see what'll happen

can't do nothing while device is running

if anyone knows how to use adb to patch script's to run on recovery mode or odin please let me know
[Galaxy S 4 General] leeheejinlove:
the analysis of bootloader for knox

Hi, I saw an article in Chinese that contains the analysis of bootloader for knox.

Anyone who can not understand Chinese please use google translation for reading.

Android系统典型bootloader分析

博文作者：firewings

发布日期：2014-01-02

阅读次数：1110

博文内容：

1、bootloader是什么？

简单地说，bootloader 就是在操作系统内核运行之前运行的一段小程序。通过这段小程序，我们可以初始化硬件设备、建立内存空间的映射图，从而将系统的软硬件环境带到一个合适的状态，以便为最终调用操作系统内核准备好正确的环境。

Android系统基于Linux，所以bootloader部分也是与传统的嵌入式设备上运行的Linux没有什么区别。由于除Google外的大部分Android厂商都没有提供bootloader的源代码，所以分析手机设备的bootloader需要使用逆向工程的手段，当然由于有了Google官方的开源bootloader代码做参考，能让分析工作轻松不少。本文中使用的分析工具为IDA 6.5，针对的手机设备为N9006，固件版本为N9006ZCUDMK2。

2、bootloader典型结构

这部分会以高通MSM8960为例子介绍下Bootloader的典型结构。

高通MSM8960中包含多个运算单元，分别负责引导过程中的不同功能，sbl1的代码负责加载sbl2，sbl2加载tz和sbl3，sbl3加载apppsbl，appsbl加载HLOS。

图1 SecureBoot 3.0 的Code Flow

图2 MSM8960引导过程简化流程图

3、Note3的bootloader结构分析

国行版Note3（N9006）使用的CPU是MSM8974，它的bootloader结构与典型的MSM8960差不多，最大的区别就是把sbl1,sbl2,sbl3整合进了一个文件sbl1中，TrustZone和APPSBL都由sbl1进行验证和加载，以下为几个主要功能的加载代码分析。

sbl1的功能是对硬件进行初始化并加载其他模块，需要加载的模块信息按顺序保存在sbl1中，对应每个模块的数据是一段大小为0x64字节的模块信息数据内，sbl1中有一个循环负责验证和加载所有需要的其他模块（tz，rpm，wdt，appsbl），加载代码会根据模块信息内的数据调用不同的加载器加载和验证的代码，具体代码如下图。

图3 sbl1中循环加载全部模块的代码

图4 sbl1中对待加载模块进行验证

图5 TZ模块信息数据

图6 APPSBL模块信息数据

固件包里的tz.mbn是加载在TrustZone中的模块，模块格式为elf，这个模块中的代码和系统其他模块代码运行在互相隔离的区域内，权限也比其他模块更高，三星KNOX的很多底层安全特性也是在这部分中实现，关于TrustZone的更多资料可以参考arm官方的说明。

固件包里的aboot.mbn就是APPSBL模块，模块格式为bin，文件最前面的0x28字节的头部描述了bin的加载地址等信息，后面的数据就是实际加载到内存中的映像，整个bootloader中这个模块的代码量最大（很大一部分是openssl的代码），linux内核的验证和加载（正常启动和Recovery模式），ODIN模式等等代码都包含在这个模块内。

图7 aboot.mbn文件头

图8 根据按键和共享内存中的数据确定引导模式

图9 三星特有的ODIN刷机模式代码

4、Note3的bootloader中KNOX系统的底层代码初步分析

Note3提供了一个企业安全套装KNOX，这个系统包含了底层的Customizable Secure Boot和TrustZone-based Integrity Measurement Architecture(TIMA，目前为2.0版本)，系统层的SecurityEnhancements for Android（SE-Android）和应用层的Samsung KNOX Container，Encrypted File System（EFS），Virtual Private Network（VPN），其中Customizable Secure Boot和TIMA的代码包含在Bootloader的aboot.mbn，tz.mbn，NON-HLOS.bin中，功能为保障加载的内核在加载时和运行期的完整性。

通过前面的分析，我们已经知道了tz.mbn和aboot.mbn在加载时已经由sbl1验证过完整性，tz.mbn加载后会在CPU的安全环境下运行，从高权限的隔离区域内对系统的完整性进行监控，而负责加载android内核的aboot.mbn中包含对内核的完整性检测，三星在bootloader每一部分的结尾都会加上自己的签名，加载前会对签名进行验证，以保障系统未被修改过。

图10 tz.mbn中初始化TIMA系统的的代码

图11 aboot.mbn中对内核是否使用SEANDROID进行验证

当任何一部分检测代码发现系统异常状况后，就会调用SMC指令通知TrustZone中运行的TIMA系统设置fuse为系统完整性被破坏，此fuse数据一旦被设置后没有办法被重置，系统也无法再次进入KNOX系统。

图12 加载内核前对内核签名和TIMA的测点进行验证

图13 系统完整性检测失败后设置fuse值

当以上所有检测都通过后，bootloader会把内核复制到指定的内存地址并跳到内核的入口继续执行，到此，就进入了系统内核代码的范畴，bootloader的使命也就完成了，跳到linux内核入口的代码见图14。

图14 内核加载和校验完成后跳到内核的入口点继续执行

另外，除了这两个模块外Modem固件相关的NON-HLOS.bin中也有大量TIMA系统相关的文件，由于TIMA系统包含大量硬件相关代码（使用三星猎户座CPU的N900中TIMA系统的实现与高通CPU的N9006差别很大），如果需要进行进一步的分析TIMA在modem中的行为，需要对TrustZone，modem工作方式等有更多了解。

图15 NON-HLOS.bin中包含的大量TIMA相关文件
[Galaxy S 4 General] bungadudu:
The original post (for↑) also containing images - http://www.2cto.com/Article/201401/269759.html

Another Chinese blog with a few similar articles - http://blog.csdn.net/Fybon/article/category/1841937
[Galaxy S 4 General] leeheejinlove:
Thanks.I just registered this new name and can not send the URL link.
[Galaxy S 4 General] mahmoud007:
hello

i was tracing mmcblk0 and what partitions have inside and i found this :

it seems that mmcblk0 contain mmcblk0p1 & mmcblk0p1 countains mmcblk0p1p1 + mmcblk0p1p2 + mmcblk0p1p3 + mmcblk0p1p4

but device wont show them at all ... still they appear in fdisk logo !!

this shows after

umount /sys/fs/selinux
[Galaxy S 4 General] mythi:
if i was sammy i would place the KNOX container in the EFS :cyclops: , just a guess !
[Galaxy S 4 General] mahmoud007:
in my guess what happen when you format via oden even if you press nand erase all you still wont touch more than 9 gb space of your emmc "the available partition" and the known system partitions .

that if you have 16 gb device , i think knox takes another partition that never mounted on device nor usb ... the only thing can mount knox partition is knox it self ... so my guess is knox partition is like efs partition " not inside efs .. its only my opinion .

but i like and hate the idea about keeping forcible backup partitions for the new rom inside knox that load up every start up ... which explains why my wifi does not work .. and explain why i cant brick my device after nand erase
[Galaxy S 4 General] mythi:
yeap , that seams more understandable ... but if if and if the knox partition is like an efs partition it can be mounted and readed some how ... but the problem is where is that partition and what's the nature of it ... or maybe the the sbl2.bin or sbl3.bin contain the container (i targeted sbl2 and sbl3 because i think sbl1 is the android bootloader which is loaded once the device is started then loads sbl2 which is a second half of the android bootloader or the KNOX bootloader (sammy bootloader) and then sbl2 checks the knox container in it or in sbl3 after this cycle it gives the value to sbl4 which i think is download mode) , also the bootloader partition(s) can't be directly accessed from a running system thus gives the need of using a jig to write / read there .

please correct any wrong info i have
[Galaxy S 4 General] BrunoWestone:
it wont work at all….
[Galaxy S 4 General] mahmoud007:
these all the showing partitions which this app found :

as showing alot of partitions are not mounted and they been taking mass of our storage

and mmcblk0 main storage eMMC is not mounted at all !!
[Galaxy S 4 General] phr3ncj:
[MENTION=5605778]mahmoud007[/MENTION]: maybe u can crosscompile a statically linked "parted" for arm and push it via adb and try to manually format some partitions from running device or from recovery mode, but probably seandroid would block access to some partitions.

Inviato dal mio SM-N9005 utilizzando Tapatalk

---------- Post added at 06:49 AM ---------- Previous post was at 06:16 AM ----------

some pdfs on emmc: jedec.org/sites/default/files/Victor_Tsai.pdf

linaro.org/documents/download/c81422ba114a6ea8d2be2120bd7aafb24fbb972b2e670

in the first one, it talks about two reset mode for emmc and types of write protection.

in the second one, it explains how rpbm is accessed.

if i have understood correctly, the problem is the emmc, not seandroid, so we have to trigger reset of emmc itself somehow and then reflash a whole rom.

what do you think about folks?

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy S 4 General] mahmoud007:
i already stopped seandroid ... but seems that hidden storage do a backup for some partitions like bootloader partitions every time your phone restart and keep them safe from being changed

those documents you gave are true ... but the method that how emmc works can be reseted by formatting the emmc ... but on samsung its another story ... there gotta be a way to reset it without device screws open
[Galaxy S 4 General] phr3ncj:
sammy has the key to talks to rpmb: if we dont have that key, we cannot do in the sammy way. so or we fake addr of rpmb somehow (on bounty 3d on sm-n9005 forum, someone said that with a particolar .pit and rom his phone was unable to activate the flag, but i dont know if this was confirmed) or we have to trigger internal reset of emmc to format all including rpmb. i dont see any other ways. btw ppl from that famous jtag are now working on this and he confirmed that (on exynos) the flag is surely on rpmb.

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy S 4 General] mahmoud007:
yes i do suspect its a pit file have that hidden partition identified

but we need to know the format of that partition"file system" and location and name

actually i could be more careless about the counter ... i just want my wifi and bluetooth actually run after getting back to the previous version .

and to do that i gotta reach that hidden partition and remove what i suspect is a backup files for the 4.3 rom that i think are exist on that hidden partition and which i believe prevents us from doing system changes .. other wise i dont care .. ill never upgrade again
[Galaxy S 4 General] ryanbg:
A properly structured qseecom command into TrustZone can mount rpmb. Iotctl was patched to read/write rpmb, but it reads/write data frames differently, which I'm not really familiar with.
[Galaxy S 4 General] phr3ncj:
[MENTION=5605778]mahmoud007[/MENTION]: see this -> pjc.me.uk/efi-gpt/

parted is better than fdisk, but u have to crosscompile for arm and statically link it because i don't think busybox have it. for crosscompiling u have to use an arm toolchain (e.g. i have one taken from emdebian testing repository for debian users -> wiki.debian.org/EmdebianToolchain) and get all dependencies of parted via xapt, i.e. # xapt -a armel -m <package>, then tell gcc that u want it statically link it.

OT: all remember that that rpmb is 'secure' because it was not made by sammy, it's in the emmc standard, and we know that sammy is not always good about security, e.g. think about device /dev/exynos-mem on my previous i9300: it was shipped officially for a long time with 777 permission and it allowed to freely access to EVERYONE in r/w mode to ALL memory of the phone!
[Galaxy S 4 General] mahmoud007:
yes i tried to edit busybox to install that applet from my linux but it doesn't work

would be nice if there was a debian based terminal as apk

even some of the busybox command are not complete ... its like toys

but i liked the s3 for that, even my previous s3 have that status 777 i thought it happen because of the su process and custom recovery
[Galaxy S 4 General] phr3ncj:
[MENTION=5605778]mahmoud007[/MENTION] if i find some free time in these days maybe i'll try to crosscompile parted for you.

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy S 4 General] dpeddi:
it seems that eMMC Tool 2.0 Lite (ATF Plus)

Supports Reading and Writing to USER AREA, BOOT1, BOOT2, RPMB, GP1, GP2, GP3 or GP4 Partition

h**p://forum.gsmhosting.com/vbb/f609/atf-v10-00-jtag-emmc-update-public-disccusion-thread-1692076/

If someone have this box It might interesting to solder to emmc and test this tool...
[Galaxy S 4 General] Bordo_Bereli51:
After i downgraded from 4.4.2 to 4.2.2, my wifi and bluetooth is working, only sound is bricked.

I tooked from 4.4.2 firmware file the sbl1.mbn, sbl2.mbn, sbl3.mbn, tz.mbn, rpm.mbn and aboot.mbn and repacked to .tar file with the 4.2.2 firmware files boot.img, cache.img.ext4, hidden.img.ext4, modem.bin, NON-HLOS.bin, recovery.img and system.img.ext4.

After then, when it was done with flashing, I changed in build.prop ro.securestorage.support=true to ro.securestorage.support=false and my wifi works like the in 4.4.2 firmware
[Galaxy S 4 General] BrunoWestone:
I have the Box and i will test it.

I'll post the result later.
[Galaxy S 4 General] BrunoWestone:
Maybe i should began by trying to dump the full RPMB from a Unknoxed phone. What do you think dpeddi ?

Ideas guys ?!?
[Galaxy S 4 General] ryanbg:
Options 14 and 15. Still working on acquiring r/w on rpmb.

Also, provisioning option gives you two choices:

Production

Test
[Galaxy S 4 General] dpeddi:
Yes good idea... but I don't know if they mean rpmb protectrd area or rpmb partition with rpmb firmware...

If you have both knoxed and unknoxed device please compare efs partition too. What is wv.keys? On my knoxed device that file seems empty.. maybe wv mean warranty void and should be full?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 General] mahmoud007:
you cant change build.prob !! can you ??

i tried to change it but it cancel the changes i make every time i close it !!

its like this file either an alias file .. or worse .
[Galaxy S 4 General] mahmoud007:
i dont know what about you but for me .. samsung as an android idea did fall down ... its more like mac now

this will be my last device from samzink, maybe ill go to htc .. they still support freedom to create , explore and control your own device "root or not " i hope , and great hardware match for samzink devices.
[Galaxy S 4 General] mahmoud007:
ohh ok soo i was able to disable knox .. damn why i didnt try that before lol

i upgraded to 4.3 and find out that this version is 360 degree is different from 4.2.2 and previous androids " thats why i was soo mad " lol

its really different and very new thats why half of my favorite program wasn't running on it and i was furious lol

yea i guess i have to adapt with it

im sure new sdk tools will come out soon
[Galaxy S 4 General] Bordo_Bereli51:
Root your 4.2.2 go to play store download busy box and install busy box files reboot the phone

now download from play store build.prop editor

then you can change ro.securstorage to false
[Galaxy S 4 General] mahmoud007:
Wow I didnt know such an app does exist!!

Ill downgrade again later after I get home and see results ... thanks
[Galaxy S 4 General] vim1:
Shure but it diesnt contain boot1 boot2 and rpmb partitions
[Galaxy S 4 General] MemoryController:
How did you get uart output? Resistor value or?
[Galaxy S 4 General] mahmoud007:
sorry guys

i sold my device without much loss yesterday and like i said that was my last Samsung and will never get back to it

if they still counting on the same method by the memory and device
[Galaxy S 4 General] ryanbg:
Run tima_dump_log

It lives in system/bin so no worries.
[Galaxy S 4 General] vim1:
Anybody need QFUSES dump before and after phone got an knox bit ?

Отправлено из моего iPad используя Tapatalk HD