yashsingh1/xdaforums huggingface dataset:
[Bada Software and Hacking General] adfree:
My S8600/I9001...

# cd sys
cd sys
# ls
ls
fs
devices
dev
bus
class
firmware
kernel
power
module
block
# cd devices
cd devices
# ls
ls
platform
system
virtual
i2c-4
i2c-6
i2c-7
i2c-0
i2c-1
i2c-2
i2c-3
# cd virtual
cd virtual
# ls
ls
gpio
vtconsole
sec
bdi
net
misc
mem
tty
vc
sdio_al_test
smdpkt
oncrpc
audlpa
aclset
gammaset
graphics
msm_vidc_reg
msm_vidc_dec
msm_vidc_enc
msm_rotator
block
input
switch
jack
vibetonz
timed_output
usb_composite
diag
key
touch
gemini
jig
sound
pdp
# cd sec
cd sec
# ls
ls
switch
sec_lcd
ts
qt602240_noise_test
qt602240_atcom_test
sec_cam
dpram
#

I am trying to find correct path/Command ...

:confused:

For "S2"...

http://xdaforums.com/showpost.php?p=33750478&postcount=1

adb shell cat /sys/devices/virtual/sec/sec_touchscreen/tsp_touchtype

How to correct Command for I9001?

:confused:

So I could check also my I8150 and so on...

Thanx in advance.

Best Regards

Edit 1.

Maybe something like this...

adb shell cat /sys/devices/virtual/sec/ts/[B]*[/B]
1.0

32
/sys/devices/virtual/sec/ts/power: invalid length
/sys/devices/virtual/sec/ts/subsystem: invalid length

* as Joker... to find what I don't know where it is... :D

adb shell cat /sys/devices/virtual/sec/switch/*
/sys/devices/virtual/sec/switch/power: invalid length
/sys/devices/virtual/sec/switch/subsystem: invalid length
USB Switch : PDA_AP
USB_STATE_CONFIGURED

adb shell cat /sys/devices/virtual/sec/sec_lcd/*
1
SMD_S6E63M0
/sys/devices/virtual/sec/sec_lcd/power: invalid length
/sys/devices/virtual/sec/sec_lcd/subsystem: invalid length

adb shell cat /sys/devices/virtual/sec/qt602240_noise_test/*
/sys/devices/virtual/sec/qt602240_noise_test/power: invalid length
0
0
0
0
0
-0, 0, 0, 208
16384
16384
16384
16384
16384
0 , 191 , 16384, 208
32
/sys/devices/virtual/sec/qt602240_noise_test/subsystem: invalid length

adb shell cat /sys/devices/virtual/sec/qt602240_atcom_test/*
/sys/devices/virtual/sec/qt602240_atcom_test/power: invalid length
PASS
16
16
OK
/sys/devices/virtual/sec/qt602240_atcom_test/subsystem: invalid length

adb shell cat /sys/devices/virtual/sec/sec_cam/*
LSI_S5K4ECGX_CE147
/sys/devices/virtual/sec/sec_cam/power: invalid length
/sys/devices/virtual/sec/sec_cam/subsystem: invalid length

adb shell cat /sys/devices/virtual/sec/dpram/*

Uuupsi, restart/reboot...
[Bada Software and Hacking General] ghoslslender124:
Only for you: I make many question because i dont know many more things than you - But Want Help :)
[Bada Software and Hacking General] adfree:
Back to research...

About Touch driver in I9001 source and maybe in S8600 used mXT224E...

So first look it seems not impossible to add mXT224E Code to mXT224 (I9001) source...

Check attached files...

Taken from SGH-I997

https://github.com/TeamRefuse/android_kernel_samsung_dempsey

And from I9001 source code...

I have NO idea if more files mandatory...

Will check "include" stuff...

Compare files with Total Commander for instance...

Best Regards
[Bada Software and Hacking General] adfree:
Oh, result... :cyclops:

Tested.

Only Volume - for step down...

No second key... :(

Funny... no idea why Android Control XP can take Screenshot... shows something with offline...

So old wrong method used... to capture screen...

Maybe someone knows, how to change keys in recovery.img ...

Is it in RAMDISK or in zImage?

Keylayout I mean...

Thanx in advance.

Best Regards
[Bada Software and Hacking General] BenzoX:
Quite strange that more key work with some version and not the other... Are they all i9001 files ?

I would say zImage, key driver should be in the same file as mosts of drivers (board-ariesve.c).

Keylayout tought...

Here is (probably) how key are handled in CWM recovery

Link with keyevent probably in android_device

Now, is it in RAMdisk or zImage...? Maybe possible to extract ramdisk and see what is inside...
[Bada Software and Hacking General] adfree:
I will try to ask Developer of these CWM Versions...

cwm-6037-ariesve-patched-alireza7991.zip
cwm-6037-ariesve-alireza7991.zip

Maybe he can help to find where keylayout is for CWM Recovery...

Meanwhile I check my downloaded sources...

GT-I8150B_GB_Opensource.zip
GT-I8150T_Opensource.zip
GT-I8150_CHN_CHN(1).zip
GT-I8150_CHN_CHN.zip
GT-I8150_HK.zip
[B]GT-I8150_Opensource(1).zip[/B]
GT-I8150_Opensource(2).zip
GT-I8150_Opensource.zip
SGH-I847_ATT_Opensource.zip
[B]SGH-I847_Opensource_Update1.zip[/B]
SPH-M840_BST_JB_Opensource.zip
SPH-M840_NA_JB_Opensource.zip
SPH-M950_ICS_Opensource(1).zip
SPH-M950_ICS_Opensource.zip
SPH-M950_ICS_Opensource_Update1.zip
SPH-M950_JB_Opensource.zip
SPH-M950_NA_JB_Opensource.zip

Really funny... I can find mXT224E drivers in I8150 and I847 Kernel sources...

This means not, I8150 or I847 uses this Chip... but sources available in these packages...

Best Regards
[Bada Software and Hacking General] mirhl:
So.. I am a bit late but it's better than never

Speaking of #714 I remember when systemUI crashed the notification bar on the top of the phone disappered until the service restarted

and besides adb reboot bootloader(#713), the variant "adb reboot-bootloader" " is also in use.. even though I don't know what's the difference between the two

then I just wanted to hint testing touch drivers (if ever) in TWRP recovery for simplicity (faster boot)
[Bada Software and Hacking General] adfree:
Recovery aka recovery.img have some problems...

1.

Recovery is not reachable via Key Combinations...

Only via 2 ways...

1.1

recovery.img is on position of boot.img...

So normal boot start recovery.img at 0x0900 0000... instead boot.img

Sideeffects...

In this Mode/Position...

cwm-6037-ariesve-patched-alireza7991.zip
cwm-6037-ariesve-alireza7991.zip

Both tested version have only 70 seconds... before Reboot... :rolleyes:

recovery.img seems bad for fully ADB support...

Many things not online...

for instance

adb shell [B]getevent[/B]

:rolleyes:

1.2.

You can write recovery.img via JTAG or simple via Odin to correct position:

0x0B00 0000

But then you need normal start... 70 seconds +

adb reboot recovery

70 seconds + :rolleyes:

If recovery is as recovery started, then no reboot... so you have plenty of time...

1.3

Or you could write recovery.img to both position...

0x0900 0000

and

0x0B00 0000

Then you can work via Keys... instead ADB Command...

I mean click click select under advanced in menu...

Best Regards
[Bada Software and Hacking General] adfree:
:D

Not realized before, that I9001 and I9000 have 1:1 same Display...

So it looks like I have spareparts...

First I thought it is only look a like...

Clicking around in Source Code from Samsung...

kernel/arch/arm/configs

So hundrets of devices inside...

[B]GT-I8150[/B]
ancora_rev00_defconfig

CONFIG_TOUCHSCREEN_MELFAS_MCS8000=y
CONFIG_TOUCHSCREEN_MELFAS_FIRMWARE_UPDATE=y

[B]GT-I9001[/B]
ariesve_rev00_defconfig

CONFIG_TOUCHSCREEN_QT602240=y
((means MXT224))

[B]SGH-I847[/B]
apache_rev00_defconfig

CONFIG_TOUCHSCREEN_[B]MXT224[/B]=y

[B]SPH-M840[/B]
ray_defconfig

CONFIG_TOUCHSCREEN_TMA140=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_UINPUT=y
CONFIG_INPUT_GPIO=y

[B]SPH-950[/B]
icon00_defconfig

CONFIG_KEYBOARD_CYPRESS_TOUCH=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_UINPUT=y
CONFIG_INPUT_GPIO=y
CONFIG_VIBETONZ=y

For SGH-I847 MXT224E sources inside...

Maybe idea with recovery.img is not soooo bad...

Need I847 recovery.img with Touch support...

Long time ago I have tested this one:

apache_cwm_6.0.2.8.zip

And was wondering why I can see Screen...

Because I9001 and I847 have not same Screen...

Stock Kernel from I847 deliver black screen... on my S8600... so I think also black on I9001...

Best Regards

Edit 1.

Found something for SGH-I847 "Rugby"

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

Will test if I see something on Display and/or Touch...
[Bada Software and Hacking General] adfree:
Tested recovery.img from I847...

apache-twrp-2.5.0.0.zip

Look at Screenshots

If at boot.img position... 0x0900 0000

and at recovery.img position 0x0B00 0000

So it is really difference between those both "modes"... start normal and start into recovery kernel...

No luck with Touch input... :(

My journey through source codes from Samsung...

kconfig file in touchscreen folder... from I847...

#
# Touchscreen driver configuration
#
menuconfig INPUT_TOUCHSCREEN
bool "Touchscreens"
help
Say Y here, and a list of supported touchscreens will be displayed.
This option doesn't affect the kernel.

If unsure, say Y.

if INPUT_TOUCHSCREEN

.
..
...

config TOUCHSCREEN_QT602240
tristate "QT602240 I2C Touchscreen"
depends on I2C
help
Say Y here if you have the AT42QT602240/ATMXT224 I2C touchscreen
connected to your system.

If unsure, say N.

To compile this driver as a module, choose M here: the
module will be called qt602240_ts.

config TOUCHSCREEN_MXT224
tristate "MXT224 I2C Touchscreen"
depends on I2C
help
Say Y here if you have the MXT224/[B]MXT224E[/B] I2C touchscreen
connected to your system.

If unsure, say N.

To compile this driver as a module, choose M here: the
module will be called mxt224-ts.

Maybe research would be easier, if we know for sure if SGH-I847 uses mxt224E or also mxt224 only...

:confused:

http://www.ebay.com/itm/Samsung-Rug...e_Replacement_Parts_Tools&hash=item23352678e0

See Picture... No idea why LCD shows something... but here I can see why Keys are different...

Attached defconfig files from I8150 sources...

Maybe oleg_k allready identified all important Hardwareparts/driver...

We should compare again....

http://xdaforums.com/showpost.php?p=37187490&postcount=6

And inside his latest kernel source... also s8600_defconfig...

Maybe this helps... little bit...

Will try to find answer about I847 Touch...

If mxt224 or mxt224E...

About Keys in recovery.img ... I've got fast answer:

http://xdaforums.com/showpost.php?p=55173245&postcount=23

Thanx alireza7991

Best Regards

Edit 1.

I847 Rugby related...

http://it.aliexpress.com/item/free-...splay-Screen-with-Touch-Screen/579151007.html

Maybe here:

http://www.etradesupply.com/oem-samsung-rugby-smart-sgh-i847-lcd-screen-and-digitizer-assembly.html

Edit 2.

Hmmm... looks like after 224 is something...

Maybe I847 uses really mxt224E... not sure yet...

My request also here:

http://xdaforums.com/showpost.php?p=55207462&postcount=200
[Bada Software and Hacking General] BenzoX:
In Oleg sources you can see

"CONFIG_TOUCHSCREEN_ATMEL_MXT=m"

but in AriesVE it's "is not set" and it's the CONFIG_TOUCHSCREEN_QT602240=y that is compiled.

Maybe try to build a kernel whith ATMEL_MTX=m or y and comment the QT602240...

But after that you probably need to configure touchscreen calibration in AriesVE main code and maybe some stuff about GPIO if they differ from i9001..

The swipe to unlock on TWRP is the screen you usually get after waiting some time, or after pressing lock/unlock.
[Bada Software and Hacking General] adfree:
:D

:o

Will check again... never used before.

I have only read about brightness bug and was wondering... because I can see nearly nothing on screen...

If this recovery.img is executed from 0x0900 0000... then maybe 10 seconds before reboot... very fast...

I will check more, because few interesting things for me inside...

Sorry, I am Linux noob... and Android noobnoobnoob... :o

So few things are very hard for me to use and to understand...

Best Regards

Edit 1.

Checked again with open eyes...

If normal boot... then only short 5 seconds menu is visible... then reboot...

If as recovery booted... then after these 5 seconds dark/black... and if I press lock key/power then I can see very dark Swipe to unlock...

Interesting for me, because never seen before:

adb shell
~ # ←[6n

~ # ←[6nls
ls
ARIESVE.rle init supersu
and-sec init.rc sys
cache lib system
charging.rle nobrightness tmp
data proc ueventd.goldfish.rc
default.prop res ueventd.qcom.rc
dev root ueventd.rc
etc sbin
external_sd sdcard
~ # ←[6n

:confused:

How they achieved this... ?

? if not root

# root

But the other Chars?

Will try again to flash full I847 Firmware... I have forgotten the result... maybe restart or something else...

If not maybe I can see something over ADB and Screencapture...

Before I will try this recovery:

http://rootzwiki.com/topic/27265-recovery-cwmr-5504-for-samsung-sghi847-rugby-smart/

As it seems source also here:

https://github.com/utkanos/android_device_samsung_SGHI847

Maybe 1 day I know then, why stock I847 Firmware nothing visible on Screen...

And custom stuff I can see on my S8600/I9001...

:confused:

Maybe they included also I9001 Display driver... :confused: :confused:

Edit 2.

Interesting thread about I847... here are also links to sources:

http://xdaforums.com/showthread.php?t=1940632
[Bada Software and Hacking General] thanaphits:
้Help me plz

I flash files SMD_I9001DXKF3_I9001DXKF3_CL312878_REV00_user_low_ship_EMMC.smd AND AriesVE.ops to wave 3 no download mode and no port on notebook how to do : D
[Bada Software and Hacking General] adfree:
SMD_I9001DXKF3_I9001DXKF3_CL312878_REV00_user_low_ ship_EMMC.smd

Please. I was sure that I told NOT using other Firmwares...

Because HIGH risk to brick...

Only this for tests:

http://xdaforums.com/showpost.php?p=55128930&postcount=740

REASON for this.

1.

EMMCBOOT.MBN only 1 Version work...

Other Version failed!!!

So it is deadly to use TAR or SMD packages where Bootloaders inside...

2.

amss.mbn is taken from I847...

[MENTION=6008474]thanaphits[/MENTION]

WAIT!!!

I will download your SMD_I9001DXKF3_I9001DXKF3_CL312878_REV00_user_low_ ship_EMMC.smd, then I can tell you. If you have more Schwein als V... and maybe with luck ADB ...

OTherwise you have NO luck and you need JTAG...

Again, wait. Do nothing.

Best Regards

Edit 1.

I have problems to find Download Link...

Link to SMD_I9001DXKF3_I9001DXKF3_CL312878_REV00_user_low_ ship_EMMC.smd is where ?

:confused:

Not found on Sammobile...

Edit 2.

Maybe this here...

http://www.4shared.com/rar/rvSIwie6/i9001_dxkf3_i9001dxkf3_cl31287.html

I need 30 minutes for download and check file...

Edit 3.

Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> SMD Download mode...
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> partition.bin download..
<1> 1/11 Finished.
[COLOR="Red"]<1> dbl.mbn download..[/COLOR]
<1> 2/11 Finished.
[COLOR="Red"]<1> osbl.mbn download..[/COLOR]
<1> 3/11 Finished.
[COLOR="Red"]<1> amss.mbn download..[/COLOR]
<1> 4/11 Finished.
[COLOR="Red"][B]<1> EMMCBOOT.MBN download..[/B][/COLOR]
<1> 5/11 Finished.
<1> adsp.mbn download..
<1> 6/11 Finished.
<1> boot.img download..
<1> 7/11 Finished.
<1> system.ext4 download..
<1> 8/11 Finished.
<1> cache.ext4 download..
<1> 9/11 Finished.
<1> recovery.img download..
<1> 10/11 Finished.
<1> persist.ext4 download..
<1> 11/11 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
<1> PASS!!!
<0> Destroy instant..
<0> Killed timer

Alternate you open

SMD_I9001DXKF3_I9001DXKF3_CL312878_REV00_user_low_ ship_EMMC.smd

Sorry, EMMCBOOT.MBN was inside... you killed working EMMCBOOT.MBN...

So only Samsung Logo short... Reboot, Samsung Logo... Reboot...

NO Key Combination nor Download Mode JIG work.

You have NO luck.

Sorry.

To reanimate JTAG Hardware is needed.
[Bada Software and Hacking General] adfree:
[MENTION=6008474]thanaphits[/MENTION]

Maybe you have more luck...

Try to reach Qualcomm Mode to work with QPST again...

Please. Now read CAREFULLY.

1.

Remove USB cable

NO cable inside S8600.

2.

You have only 2 keys...

Power

Volume -

3.

HOLD Power Key...

You should see black screen... if power is holding/pressed...

Then release and hold Volume -

Try few times...

If you nothing pressed and no Samsung Logo visible...

Then attach USB cable and check if Qualcomm driver are visible...

Use then QPST...

Good luck.

Best Regards
[Bada Software and Hacking General] adfree:
Found old Pics from S8600 PCB...

Taken from here.

Wave_III_MainBoard_Pics.zip

Thanx...

http://xdaforums.com/showpost.php?p=24633792&postcount=18

Reuploaded...

http://www.mediafire.com/download/m9t84usnl14p5l0/Wave_III_MainBoard_Pics.zip

But still need Picture from ATMEL Chip to be 100 % sure it is mxt224E ...

Btw...

http://www.ebay.de/itm/Samsung-I900...e_Replacement_Parts_Tools&hash=item4acfa7c36e

Perfect would be in this Quality... for blind people like me... :D

Hmmmm. My tests with I847 kernel not really deliver answer... only more Questions...

1.

I see nothing on Display...

But f. again situation where I am not able to make Screenshots... :rolleyes:

But ADB work...

:rolleyes:

2.

I have fully flashed I847 Firmware...

I847UCLH4_I847ATTLH4_I847UCLH4_HOME.tar.md5

But getevent shows nothing if I play with Display...

:confused:

One idea is to compile I847 with I9001 display settings/driver... :D

Like few I847 custom recovery.img can do... they show correct on Display...

Something else...

apache-twrp-2.5.0.0.zip

This recovery.img shows battery status... see attached Screenshot...

Could be correct...

This is I847 Recovery and I see this on Display, without ADB...

Best Regards

Edit 1.

Will try to check custom recovery with this Command:

adb pull /proc/config.gz

To check if defconfig is modified...
[Bada Software and Hacking General] thanaphits:
@adfree

I can't to reach Qualcomm Mode to work with QPST but So only Samsung Logo short... Reboot, Samsung Logo... Reboot... always :crying:
[Bada Software and Hacking General] thanaphits:
@AdFree

View attachment 2924051 :d
[Bada Software and Hacking General] adfree:
[MENTION=6008474]thanaphits[/MENTION]

Summary...

Power key restart S8600 if you hold few seconds...

Count to 30 or longer...

Hold Power Key to reset/restart

1

2

3

.

.

.

30

Release Power Key

BE fast and hold Volume - for few seconds...

Or try press fast Power key again... this time short...

You can also try other key combination...

But main key is the power key

Volume - is detected...

I am not sure, if Volume + can help...

You could try to hold both keys...

Volume +

AND

Volume -

Also you can try with USB cable attached or without...

You have only 2, maximum 3 keys are working now on S8600

[B]Power Key[/B] = I am 100 % sure
[B]Volume -[/B] = I am 100 % sure
Volume + = not sure, but getevent detect if pressed...

Middle key = nothing, I am 100 % sure

You could also remove battery for few seconds or minutes...

Then start again.

If no luck... :o

Question 1. Lesson 1.

Hold only Power Key

As long you hold, Samsung Logo is not visible...

Hold 30 seconds... no Samsung Logo

Hold 1 minute... no Samsung Logo

Hold 2 minutes... no Samsung Logo

Is this correct?

Yes or no?

This is your only chance to reanimate your S8600... to reach Qualcomm driver... QPST

Otherwise only JTAG... :(

But I am sure, that key combination could reach Qualcomm/QPST Mode...

Good luck.

Best Regards

Edit 1.

[MENTION=6008474]thanaphits[/MENTION]

I have flashed again my S8600 to this Firmware...

Yes, I had problems this time with Volume -

But maybe found another way... because working for me...

Now only 1 key...

Hold Power key

Display must be black, no light on keys...

No USB cable

Then short release power key...

Then press fast/quick and often Power key...

Power
Power
Power
Power
Power
Power
.
.
.

Short and fast...

No joke. Press Power key more then 1 time, rapidly...

If screen black and no Samsung Logo... attach to PC with USB cable...

Hopefully this work also for you.

Best Regards

Edit 2.

Tested few times.

This is successfully for me.

Only with Power key.

I hope this is also working for you.

Good luck.
[Bada Software and Hacking General] adfree:
I am trying to find internal Pictures with good resolution... sharp enough to read text... on Chips...

I am tooo lazy to open and kill my own devices...

Perfect example:

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

:good:

FCC Photos sometimes bad quality... anyway... for info:

GT-S8600

https://apps.fcc.gov/oetcf/eas/repo...e=N&application_id=697900&fcc_id='A3LGTS8600'

SHW-M410 (korean S8600)

https://apps.fcc.gov/oetcf/eas/repo...me=N&application_id=160674&fcc_id=A3LSHWM410K

GT-I9001

https://apps.fcc.gov/oetcf/eas/repo...ame=N&application_id=228773&fcc_id=A3LGTI9001

GT-I8150

https://apps.fcc.gov/oetcf/eas/repo...ame=N&application_id=486487&fcc_id=A3LGTI8150

SGH-I847

https://apps.fcc.gov/oetcf/eas/repo...ame=N&application_id=391536&fcc_id=A3LSGHI847

Here unconfirmed overview...

http://xdaforums.com/showpost.php?p=54230944&postcount=540

Best Regards
[Bada Software and Hacking General] ghoslslender124:
[MENTION=1030585]adfree[/MENTION]

I need I9001 KERNEL source what you can compile. Have small idea about Touchscreen, because have small info from Oleg_k (He is Alive)
[Bada Software and Hacking General] adfree:
http://xdaforums.com/showpost.php?p=55120354&postcount=737

I9001 Kernel sources 90 MB... Download Link.

http://xdaforums.com/showpost.php?p=37187490&postcount=6

Inside oleg_k kernel sources...

https://github.com/Oleg-k/kernel_source_s8600/tree/master/arch/arm/configs

Maybe this could help to fix few issues...

icon00_defconfig seems this device/model

http://xdaforums.com/showpost.php?p=45552014

prevail00-perf_defconfig

:confused:

vital2refresh-perf_defconfig

:confused: :confused:

Best Regards

Edit 1.

Checked again I9001 kernel sources...

SIMPLE text search for text string:

mxt22e

NO nope... ZERO ...0 hits

oleg_k sources result, kernel_source_s8600-master:

kernel_source_s8600-master\kernel_source_s8600-master\arch\arm\mach-msm\board-8930.c

kernel_source_s8600-master\kernel_source_s8600-master\drivers\input\touchscreen\atmel_mxt_ts.c

Will try later compare if from SGH-I847 or elsewhere..

For now my focus would be on I9001 and SGH-I847 defconfig...

ariesve_rev00_defconfig
apache_rev00_defconfig

Maybe later I will try to compile I847 sources, because mxt224E for sure inside...

with defconfig from I9001:

ariesve_rev00_defconfig

With only 1 modification in defconfig...

# CONFIG_TOUCHSCREEN_QT602240 is not set
[B]CONFIG_TOUCHSCREEN_MXT224=y[/B]
[Bada Software and Hacking General] adfree:
Few hours and hints later...

Search in Internet...

mxt224E visible in SGH-I847...

http://www.globaldirectparts.com/Samsung-Rugby-Smart-SGH-I847-LCD-Assembly-p/smsng6114790-qs.htm

S8600 Chip good visible here, also mxt224E:

http://www.aliexpress.com/item/Orig...mbly-For-Samsung-Wave-3-S8600/1602036020.html

Best Regards
[Bada Software and Hacking General] BenzoX:
Hi adfree

Oleg said something about copying the driver/touchscreen folder from his sources and try to compile.

Maybe we can try it, but i think it also need to change some stuff in defconfig

Could you try to use this defconfig, (or change in AriesVE defconfig the touchscreen from QT602240 to Atmel ? )

I can do it and give you zImage, but i want to make sure to have a working configuration at first :

I used samsung stock sources (you uploaded) with toolchain provided in link in Readme, but i had to use arm-none-eabi- and not arm-none-linux-gnueabi- since it wasn't present in given toolchain.

After that, does it need default defconfig or the one taken from here ?

If you managed to get any "homemade compiled" kernel working, please tell me if my setup is good.