yashsingh1/xdaforums huggingface dataset:
[Bada Software and Hacking General] adfree:
[MENTION=5540748]BenzoX[/MENTION]

Thanx.

Give me 1 or 2 days... for "usefull" answers... please.

This is result from user Gunter33:

http://www.handy-faq.de/forum/bada_..._badadroid_support_thread-35.html#post2911662

I have only 1 time compiled and working zImage...

Compared with working Version from Gunter33 I know/understand now... compiled Binary (zImage) not need to be 1:1 Byteclone... to be working Kernel.

For second time I need to prepare few things... like how to log make "result"...

Not tested yet... :o

make -k > build.log 2>&1

I need whole screen output in single file... to check...

My plan for next week/this months...

Several attempts with Linux and Compiler...

Best Regards
[Bada Software and Hacking General] adis1313:
[MENTION=1030585]adfree[/MENTION], use tee to save logs. For example "make | tee ../log.txt". :) I had to leave for few days, so couldn't work on atmel driver. There is few things that you should now about it. I will tell you later. :)
[Bada Software and Hacking General] Ghostv33:
wave 3

bro will my wave 3 eventually get android?? :( :confused: :confused:
[Bada Software and Hacking General] mirhl:
Between a year or two? Maybe
[Bada Software and Hacking General] adfree:
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: »include/generated/mach-types.h« ist bereits aktualisiert.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
GZIP arch/arm/boot/compressed/piggy.gzip
AS arch/arm/boot/compressed/piggy.gzip.o
SHIPPED arch/arm/boot/compressed/lib1funcs.S
AS arch/arm/boot/compressed/lib1funcs.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
Building modules, stage 2.
MODPOST 25 modules

:confused:

This seems to work...

But I have no idea yet, why make not start from scratch?

What I need to delete or rename?

Meanwhile I will unpack GT-I9001_Kernel.tar.gz again, to be sure, Compiler start from 0...

Before I will try with I847 Kernel and ariesve_rev00_defconfig...

Best Regards

Edit 1.

Extracted again GT-I9001_Kernel.tar.gz... to have clean working folder...

[B]make ariesve_rev00_defconfig[/B]

Here is some output... I will copy&paste next time...

This time I've used, no output on Screen... but hopefully later result in 1 file.

[B]make -k > build.log 2>&1[/B]

Now I am waiting for result...

Edit 2.

After 16 minutes my Kernel is ready...

Compressed zImage AND uncompressed 8 MB Kernel Image.

zImage to compare makes not really sense... because Compression used... :rolleyes:

Uncompressd 8 MB Kernel Image is funny... for instance timestamps...

I can see them, compared my first Kernel and now my second, without changed Bytes...

Attached is my Logfile from "make" Command...

[B]make -k > build.log 2>&1[/B]

Seems good decision, because maybe all output redirected into file and my Screen is clean...

"tee" seems not to cach all stuff shown on Screen... like Errors/warnings...

Edit 3.

[MENTION=5540748]BenzoX[/MENTION]

I have this downloaded:

www.codesourcery.com/sgpp/lite/arm/...09-51-arm-none-eabi-i686-pc-linux-gnu.tar.bz2

I can upload my edited makefile, because I made first big mistake... I thought this is folder name not filename or ... something like this...

About defconfig... self generated work:

[B]make ariesve_rev00_defconfig[/B]

Attached file is log of make Command... with original unmodified sources...

Edit 4.

Now new attempt with SGH-I847_ATT_Kernel.tar.gz with ariesve_rev00_defconfig...

Then I can hopefully test zImage... if it would working...

If yes, then next attempt with modified ariesve_rev00_defconfig...

# CONFIG_TOUCHSCREEN_QT602240 is not set
[B]CONFIG_TOUCHSCREEN_MXT224=y[/B]

Because I847 uses MXT224E sources... I hope...

Edit 5.

Hmmm... no idea yet why, but seems to many errors... so no zImage...

Will later attach Logfile...

Now I will check second I847 package... maybe here more luck:

Kernel.tar.gz
[Bada Software and Hacking General] adfree:
[MENTION=6008474]thanaphits[/MENTION]

Problem solved?

Your S8600 is alive again?

:confused:

Please feedback.

Best Regards
[Bada Software and Hacking General] adfree:
"New" idea...

drivers/input/touchscreen/qt602240_ts.[B]o[/B]

Maybe the copy and paste "Power" work with allready compiled "Object" files *.o

I can see they are not deleted after proper compiled zImage in my I9001 Kernel folder...

So I will try compile I847 Kernel... then copy *.o from touchscreen folder...

Best Regards
[Bada Software and Hacking General] BenzoX:
Make will only compile changes, in order to gain a lot of time.

Do "make clean" and then make the config and make to have full output.

Renaming is a bad idea, and modifying defconfig is not enough to make stuff work... There is issue with virtual key as soon as i try to compile without the qt touchscreen, and i don't know how to solve...

Tried Oleg files but no success, and he use his own main code (board-s8600.c and not board-ariesve.c) which is probably not based on board-ariesve.c (file is very different, and probably have good gpios, drivers...)

Also 4 other files : board-s8600-wlan.c (looks like wifi), board-s8600-keypad.c (key driver ?) and board-s8600-regulator.c (something about voltage) and timpani_profile_7x30_s8600.h (sound stuff ?)

But i'm not skilled enough to adapt it or even to identify whole touchscreen stuff...

Oleg code is quite different, and copy pasting without adapting some lines have i think few chances of success...

Having the files is one thing, but there is different version of files (with Oleg touchscreen files it's not working even if i don't touch to defconfig, which mean some ariesVE specific stuff is not present in his code)

Maybe possible to identify from what device is his board-s8600.c from at first, maybe we have different base device.
[Bada Software and Hacking General] adfree:
I have successfully compiled I847 sources... normal without modification...

All *.o files are alive and zImage + uncompressed Image...

Now I have to copy these 2 folders from my Linux Debian Notebook... to my Windows PC... looks like 3000 MB...

So I can better search and analyze with my beloved XP... :D

Later more...

Best Regards

Edit 1.

So I have now from I9001 :

drivers/input/touchscreen/qt602240_ts.o

And from I847 :

drivers/input/touchscreen/atmel_mxt_ts.o

Later I can try to identify these Object data into kernel Image...

In touchscreen folder also some kind of Makefile inside...

#
# Makefile for the touchscreen drivers.
#

# Each configuration option enables a list of files.

wm97xx-ts-y := wm97xx-core.o

obj-$(CONFIG_TOUCHSCREEN_88PM860X)	+= 88pm860x-ts.o
obj-$(CONFIG_TOUCHSCREEN_AD7877)	+= ad7877.o
obj-$(CONFIG_TOUCHSCREEN_AD7879)	+= ad7879.o
obj-$(CONFIG_TOUCHSCREEN_ADS7846)	+= ads7846.o
obj-$(CONFIG_TOUCHSCREEN_ATMEL_TSADCC)	+= atmel_tsadcc.o
obj-$(CONFIG_TOUCHSCREEN_BITSY)	+= h3600_ts_input.o
obj-$(CONFIG_TOUCHSCREEN_CYPRESS_TMG)	+= cy8c_tmg_ts.o
obj-$(CONFIG_TOUCHSCREEN_DYNAPRO)	+= dynapro.o
obj-$(CONFIG_TOUCHSCREEN_CYPRESS_TMG)	+= cy8c_tmg_ts.o
obj-$(CONFIG_TOUCHSCREEN_HAMPSHIRE)	+= hampshire.o
obj-$(CONFIG_TOUCHSCREEN_GUNZE)	+= gunze.o
obj-$(CONFIG_TOUCHSCREEN_EETI)	+= eeti_ts.o
obj-$(CONFIG_TOUCHSCREEN_ELAN_I2C_8232) += elan8232_i2c.o
obj-$(CONFIG_TOUCHSCREEN_ELO)	+= elo.o
obj-$(CONFIG_TOUCHSCREEN_FUJITSU)	+= fujitsu_ts.o
obj-$(CONFIG_TOUCHSCREEN_INEXIO)	+= inexio.o
obj-$(CONFIG_TOUCHSCREEN_MC13783)	+= mc13783_ts.o
obj-$(CONFIG_TOUCHSCREEN_MCS5000)	+= mcs5000_ts.o
obj-$(CONFIG_TOUCHSCREEN_MIGOR)	+= migor_ts.o
obj-$(CONFIG_TOUCHSCREEN_MTOUCH)	+= mtouch.o
obj-$(CONFIG_TOUCHSCREEN_MK712)	+= mk712.o
obj-$(CONFIG_TOUCHSCREEN_MSM)	+= msm_ts.o
obj-$(CONFIG_TOUCHSCREEN_HP600)	+= hp680_ts_input.o
obj-$(CONFIG_TOUCHSCREEN_HP7XX)	+= jornada720_ts.o
obj-$(CONFIG_TOUCHSCREEN_HTCPEN)	+= htcpen.o
obj-$(CONFIG_TOUCHSCREEN_USB_COMPOSITE)	+= usbtouchscreen.o
obj-$(CONFIG_TOUCHSCREEN_PCAP)	+= pcap_ts.o
obj-$(CONFIG_TOUCHSCREEN_PENMOUNT)	+= penmount.o
obj-$(CONFIG_TOUCHSCREEN_QT602240)	+= qt602240_ts.o
.
.
.

I need some time for some tests after some time for analzye...
[Bada Software and Hacking General] ghoslslender124:
[MENTION=1030585]adfree[/MENTION]

Surprise. Oleg is alive and want help!

He also trying to compile his kernel source, he said that he updated source but i cant see it.. all files from 29 May.. If he give me any info: I write it here.
[Bada Software and Hacking General] adfree:
Wenn keiner was macht, kann nix bei rauskommen.

Gründe sind unterschiedlich weswegen da keiner Bock drauf hat.

Das hält mich aber nicht davon ab. Ab und zu meine Gedanken hier aufzuschreiben...

S8600, S8500, S8530 sind nach wie vor schöne, preiswerte Übungsobjekte.

Einige Sache sind schon seit über 10 Jahren in der Handywelt angewendet worden... andere halt auch in den modernen und auch noch nachfolgenden Geräten...

Wie S5...

Best Regards
[Bada Software and Hacking General] adfree:
Btw...

http://xdaforums.com/showpost.php?p=43776560&postcount=12

Please, be carefully. Dangerous...

Maybe something similar is for I9001 available...

:confused:

Best Regards

Edit 1.

Google Search... for QHSUSB_DLOAD

http://xdaforums.com/showthread.php?t=1627897
[Bada Software and Hacking General] mailrok:
Thank you for your efforts, very grateful that that is still trying to shed light in the achievement and do not throw attempts to achieve its :o

With respect to you

Спасибо за старания, очень благодарен то что до сих пор пытаитесь пролить достижение в свет и не бросаите попыток добиться своего :o

С Уважением к вам
[Bada Software and Hacking General] mailrok:
Maybe it will be interesting , found in one forum :

There is a tube - ZTEV881 Blade +

It has the following toppings :

Processor : Qualcomm Snapdragon S2 MSM8255T 1.4 GHz;

Graphics : Adreno 205 ;

Operating System : Android 2.3.5;

Memory (RAM): 512 MB ;

Built-in Memory : 4GB ;

Screen size: 3.8 inches ;

Display Type : TFT, capacitive screen , multi-touch 5 points ;

Resolution : 800x480;

Support : microSD card up to 32GB ;

1 slot for SIM- card : GSM 900/1800/1900MHz, UMTS: 900/2100MHz;

Network : Wi-Fi 802.11 b / g / n;

Bluetooth: v2.1;

Navigation : yes , full- satellite GPS;

Camera: 5 megapixel ;

Gravity sensor : yes ;

Battery Capacity: 1500 mAh ;

Seems to me that the filling is almost identical to our S8600 aka Wave3.
[Bada Software and Hacking General] adfree:
I have now opened/disassembled my first S8600.

Surprice number 1.

It seems to have Waterdamage...

This could be 1 reason why this f. phone randomly pressed End button...

So it was nearly unusable... all Apps shut down...

Only with luck I was able to play MC3 with starting ever and ever again... :rolleyes:

Surprice 2 could be.

That JTAG testpoints are not exceed my solderskills... :angel:

Testpoints look big enough to solder wires...

Then I can play with RIFF JTAG and try for instance GT-I9001 Firmware.

I hope I manage this test in this week...

Before I will do some practise again with soldering...

I have only 1 try, not to damage something... :o

Best Regards

Edit 1.

Soldered 8 wires to S8600...

RIFF JTAG work. :cool:

Now I dump first my 4 GB memory... for Backup...

This will take an while... :o

Then I have to check few other things... before I will erase something...
[Bada Software and Hacking General] adfree:
http://xdaforums.com/showpost.php?p=51525611&postcount=126

Hmm...

I can write I9001 stuff, but for now I can't see if I made some stupid mistakes...

Need more tests... more knowledge...

My S8500 JTAG knowledge is different to S8600 JTAG eMMC stuff...

Later I will check if I can reproduce what oleg_k achieved...

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

Now I'm understanding little bit more...

Read carefully this post:

http://xdaforums.com/showpost.php?p=37200735&postcount=7

Translation for my little brain...

His Bootloader EMMCBOOT.mbn from bootloader.tar is on location of appsboot.mbn

appsboot.mbn is written into eMMC at 0x4500000

I have added few spare Bytes to fit RIFF JTAG convention... and flashed only EMMCBOOT.mbn... to XXKJC or some other bada mix, I have forgotten now...

Then I can see short battery Icon on Display, like Charging... then red Screen, like empty bada... then see Picture... :D

So 1 task could be, to find way to flash appsboot.mbn with content of EMMCBOOT.mbn...

Need more time for more tests...

Best Regards

Edit 1.

Interesting, Windows detect and ask for Android driver... :confused:

Also interesting, Download Mode of bada still active... it seems.

I'm flashing now full bada Firmware, to check if it is working...

Edit 2.

Successfully back to bada with only Multiloader... from Download Mode.
[Bada Software and Hacking General] adfree:
I have written 256 MB of 7 GB I9001 dump...

30 minutes...

I can see Samsung Logo... restart/reboot cycle...

no UART

no DL Mode, tested with Key combo and JIG

Next attempt is 512 MB... and so on.

Maximum 4 GB is writeable from 7 GB I9001 dump...

Best Regards
[Bada Software and Hacking General] adfree:
Last few days no time... but now. :o

Short tested...

appsboot.mbn can't be used in ETC of Multiloader...

In Originial unmodified state... later will try if correct address would help...

Now only 0x49 as address visible...

Now I am trying to write 4000 MB of 7000 MB I9001 JTAG dump...

Maybe in 10 hours I have result...

I have short tested QPST etc... if Bootchain is destroyed and S8600 use QHSUSB Driver...

Maybe it is possible to use eMMC App from QPST in Combination with XML files from S8600_JTAG_120125.zip

Best Regards

Edit 1.

Memo to me... maybe later usefull...

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

http://xdaforums.com/showthread.php?t=1666106&page=2

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

Goal/reason for QPST...

1.

Maybe much faster as with JTAG RIFF and easier to handle...

At the moment 4000 MB write is hell slow... 6 hours +

2.

If we could use QPST...

Then in theory easy to kill S8600 bada Bootloader chain, to work with QPST...

For now I have to wait many hours... my RIFF JTAG is working and write 4000 MB...
[Bada Software and Hacking General] adfree:
Memo to me...

As base Firmware XXKJC... because Full Firmware with Bootfiles etc...

Stupid me lost few hours, because XXKI9 is same like XXKI5... not for retail... :rolleyes:

My own 4000 MB Backup dump takes 12 hours to write back... :eek:

The 2 others I have... 1 with 4000 MB and the other 1000 MB...

The IMEI problem...

This could be also the problem with I9001 dump... because I saw nothing more, as text/logo Samsung then Reboot...

Next steps...

Game A.

Modification of appsboot.mbn to check, if I am able to generate valid file for Multiloader...

Game B.

Find way to kill Bootchain, to force QHSUSB Driver...

Then playing with QPST eMMC App...

Best Regards

Edit 1.

First few tries with WaveRemaker and appsboot.mbn

Boot Binary Download Start Ch[0]
Pbl 24.6KB OK[0.2s]
AppsBoot 338.7KB OK[0.6s]
ERR : NAK_BAD_SEC_CODE 0
ERR : OemSbl Erase

Need some time...
[Bada Software and Hacking General] adfree:
I'm trying to mix Bootfiles...

V1

partition.bin from XXKI9

all others from XXKJC

Boot Binary Download Start Ch[0]
Pbl 24.6KB OK[0.2s]
AppsBoot 338.7KB OK[0.6s]
OemSbl 1757.7KB OK[2.8s]
Dbl 229.4KB OK[0.4s]
All files complete[4.7s]

S8600 alive and booting proper...

Later more...

Best Regards

Edit 1.

V2

dbl.bin + partition.bin from XXKI9

Boot Binary Download Start Ch[0]
Pbl 24.6KB OK[0.2s]
AppsBoot 338.7KB OK[0.6s]
OemSbl 1757.7KB OK[3.2s]
Dbl 229.4KB OK[0.4s]
All files complete[5.0s]

S8600 alive

V3

dbl.bin + partition.bin + osbl.bin from XXKI9

Boot Binary Download Start Ch[0]
Pbl 24.6KB OK[0.2s]
AppsBoot 338.7KB OK[0.5s]
ERR : NAK_BAD_SEC_CODE 0
Error : OemSbl Write [0.3s]
ERR : NAK_BAD_SEC_CODE 0
ERR : NAK_BAD_SEC_CODE 0

V4

dbl.bin + partition.bin + appsboot.mbn from XXKI9

Boot Binary Download Start Ch[0]
Pbl 24.6KB OK[0.2s]
AppsBoot 338.7KB OK[0.6s]
OemSbl 1757.7KB OK[2.7s]
Dbl 229.4KB OK[0.4s]
All files complete[4.6s]

S8600 alive

V5

Again tried all files of XXKI9...

Boot Binary Download Start Ch[0]
Pbl 24.6KB OK[0.2s]
AppsBoot 338.7KB OK[0.5s]
ERR : NAK_BAD_SEC_CODE 0
Error : OemSbl Write [0.3s]
ERR : NAK_BAD_SEC_CODE 0
ERR : NAK_BAD_SEC_CODE 0

So something is in osbl.bin...

:confused:

V6 short tried to modify partition.bin...

Result...

Boot Binary Download Start Ch[0]
ERR : NAK_BAD_SEC_CODE 0
Error : Pbl Write [0.2s]
ERR : NAK_FLASH_ERROR 0
[Bada Software and Hacking General] adfree:
I will concentrate on this Qualcomm thingie...

1.

With JTAG easy to force Emergency Download QHSUSB...

Easy to overwrite 1 Byte... after 512 Byte MBR...

[B]D1[/B]DC4B843410D7735A430B7D

These few Bytes I have seen also from other handsets...

MBR seems for every S8600 1:1 same... (first 512 Byte).

Will try to find alternate way... with Multiloader...

2.

Attached is RAM dump... maybe usefull stuff inside... for study.

Looks like PBL... :confused:

RAMdumpS8600v4.zip

0xFFFE6000	Length 0x0001A000

Best Regards
[Bada Software and Hacking General] adfree:
http://forum.gsmhosting.com/vbb/f83/how-convert-bin-into-hex-qpst-840472/

:D

Maybe I need this again to understand content of ENPRG7x30.hex and NPRG7x30.hex

E means maybe Emergency... in ENPRG7x30.hex

This looks interesting too...

http://forums.wpcentral.com/huawei-ascend-w1/229445-those-who-get-their-w1-market-locked-china.html

Best Regards
[Bada Software and Hacking General] adfree:
Maybe I have found way, to kill Bootchain with Multiloader... :angel:

Tested with XXKI9 Bootfile...

WARNING!!!!!!

DON'T do this, if you have not JTAG for repair.

Repair steps with Software (QPST eMMC App) not finished yet.

Short description... DANGER

osbl.bin

Change first Byte into something else...

I have changed into FF...

Remove MD5 check...

Flash with Multiloader... Result looks like this:

Boot Binary Download Start Ch[0]
Pbl 24.6KB OK[0.1s]
AppsBoot 338.7KB OK[0.5s]
[B]OemSbl 1758.8KB OK[2.1s][/B]
ERR : NAK_BAD_SEC_CODE 0
ERR : Dbl Erase

Peng, S8600 now ask for Qualcomm QHSUSB Driver... :D

Will try with XXKJC Bootfiles... later more.

Best Regards

Edit 1.

Tested succesfully with XXKI9 and XXKJC Bootfiles...
[Bada Software and Hacking General] adfree:
Hmm.

Will check other Qualcomm drivers... forgotten where I found old one...

New package has Cert inside...

Taken from here:

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

:confused:

============== How to Add Test Certificate ===============

Test certificate may need to be applied to Windows
before installing the USB host driver. A same certificate
will only need to be added once. Follow the steps listed
below to add test certificate to the system under test.

1. Launch Windows Explorer and locate the certificate
file qcusbtest.cer

2. Right-click on qcusbtest.cer and choose Install Certificate.

3. Follow instructions and place the certificate in the
following certificate stores:
Trusted Publishers
Trusted Root Certification Authorities
Step 1 through 3 will need to be repeated to place the certificate
in more than one certificate stores.

4. On Windows Vista, open a Command Prompt with "Run as
administrator" and issue the following command:
bcdedit -set testsigning on

For pre-Vista Windows versions, skip this step.

5. Reboot the system.

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

Hmm...

With new "Driver" I stuck here:

Bad is, Youtube Videos seems offline ablut fix this problem for Karbonn A9...

Hmmm...

Will try from scratch...

S8600...

It seems dbl.bin is first content after 512 Byte MBR in eMMC...

http://xdaforums.com/showpost.php?p=51881668&postcount=73

This seems inside DBL...

D1DC4B843410D7735A430B7D

So 2 ways to force QHSUSB Driver...

1.

Kill DBL ...

or

2.

OSBL

Will try to check if there are differences...

3.

About S8600 in "QHSUSB Mode"...

It seems to understand Standard Reset Command...

Tested with QPST Memory Debug App...

S8600 restart...

Also I was able to see restart with some other file combination in eMMC ...

Will test again...

I will erase 0x0 to 0x500000... complete, with MBR...

Before I was tooo wimpy to "erase" from address 0...

I've left MBR

Best Regards
[Bada Software and Hacking General] adfree:
Uuupsi, stupid me was clicking around...

Need before to read what this option is... :o

Before tested with JTAG RIFF to overwrite/erase 0 - 0x500000...

With file FFFFFffffffffffffffff...

And checked ...

It is possible.

Maybe later I will try to overwrite whole 4 GB... with empty FF content... to check if write protected areas exist...

Best Regards

Edit 1.

Search results by Google about:

qualcomm qfprom

http://xdaforums.com/showthread.php?t=1856327&page=2

Edit 2.

Little step forward...

Sending image...
Downloading programmer
Software Download failed with error "Could Not Communicate with Flash Programmer"
Image send complete. Check main window for error messages.

And XP finds "something", but I have choosed MPRG8X25.hex...

Will check again with files from S8600:

NPRG7x30.hex
ENPRG7x30.hex

Best Regards
[Bada Software and Hacking General] adfree:
http://androidforums.com/4190389-post38.html

Maybe "we" could find other devices... with these Bootloaders in Intel HEX Format...

NPRG7x30.hex
ENPRG7x30.hex

Best Regards
[Bada Software and Hacking General] adfree:
Uupsi... :laugh:

Short tried again with JTAG RIFF and Resurrection Button...

Maybe I have not seen this first tests... or maybe this time more luck...

I9001 Driver installed and Odin find my S8600...

On Display I see nothing...

Now Odin hangs here:

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
[B]<1> setup connection...[/B]

Maybe I will test again Fulldump... maybe more luck this time...

Best Regards
[Bada Software and Hacking General] adfree:
Thanx.

Every help is welcome. :good:

Best Regards
[Bada Software and Hacking General] thanaphits:
@AdFree

My S8600 no alive . and i hold power Key

Hold 30 seconds... So only Samsung Logo short... Reboot, Samsung Logo... Reboot... always

Hold 1 minute... So only Samsung Logo short... Reboot, Samsung Logo... Reboot... always

Hold 2 minutes... So only Samsung Logo short... Reboot, Samsung Logo... Reboot... always

Hold 3 minutes... So only Samsung Logo short... Reboot, Samsung Logo... Reboot... always

Hold 4 minutes... So only Samsung Logo short... Reboot, Samsung Logo... Reboot... always

I remove battery for 1.. minutes... So only Samsung Logo short... Reboot, Samsung Logo... Reboot... always

AND remove battery for 2.. minutes screen black and no Samsung Logo... attach to PC with USB cable to s8600

So only Samsung Logo always :crying:

Best Regards
[Bada Software and Hacking General] adfree:
[MENTION=6008474]thanaphits[/MENTION]

But you tried to press Power key rapidly often?

Press Power
Press Power
Press Power
Press Power
.
.
.
.

http://xdaforums.com/showpost.php?p=55238400&postcount=764

Only 1 key to press : Power key

NO USB cable

Press

Release

Press

Release

Click

Click

Click

Click

FAST FASTER fast as you can... its timing.

With my left hand I hold my S8600.

With my right hand... I need 3 fingers... thumb on Power key.

I hold and press rapidly with my thumb only...

No idea how else to translate... I am not able to write in vietnamese Language...

In German:

Nur die Power Taste, ohne USB Kabel...

Halten... um den Reset auszulösen. Das kann 30 Sekunden dauern...

Jedenfalls bleibt bei gehaltener Power Taste das Bild schwarz und es kommt kein Samsung Logo...

Dann schnell hintereinander die Power Taste drücken...

Bei mir gehts mit dem Daumen der rechten Hand... Zeige und Mittelfinger sind bloß als Stütze... und die linke Pfote hält das S8600...

Best Regards

Edit 1.

[MENTION=6008474]thanaphits[/MENTION]

Please look at this Video... I have not found other...

http://www.youtube.com/watch?v=bqAYI_HxEmI

Press Power key repeatedly on S8600.

In Video he pressed F1 repeatedly...