yashsingh1/xdaforums huggingface dataset:
[Tizen Software Development] adfree:
:o

Sorry, I have at the moment not much time...

And since I have Tizen SM-Z130 and access to Tizen Store...

I am not more sure, if I should kill my I9300 PCB for tests... :o :o :o

Risk is high, to kill Bootloader for nothing...

And I have not easy equipment to reanimate easily if I would fail...

As Info... I have RIFF Box at home...

:good:

I9300 is not supported during Security reason...

eMMC direct support is possible with OTHER Hardware solution...

200 Euro + ...

I am not willing to pay again such high price.. as my solder skills are very limited... :o :o :(

Because I have to solder wires to PCB myself... so best box in the world not help... If I can't do this... :D

Testpoints are sooooo tiny small... to damage PCB easily for ever...

As RIFF Box owner I will follow this "funny" post...

http://forum.gsmhosting.com/vbb/f634/riff-i-direct-emmc-support-1953207/

Maybe for few Euro I could upgrade... so I could check my solder skills again...

But no idea, if this feature ever will available for old RIFF Box...

legija nearly 1 year posted nothing.. absolute silence...

------------------

summary...

not much time

my skills are limited...

expensive tests...

I would start again... if I or someone else has good idea... what I could try...

Or maybe someone can confirm I9300 can execute unsigned Bootloader if using Tweezers method to restore sboot.bin...

Or maybe someone found signed sboot... maybe somewhere leaked...

Best Regards

---------- Post added at 03:19 AM ---------- Previous post was at 02:52 AM ----------

If you think I am joking...

Here few Pics...

http://forum.gsmhosting.com/vbb/f60...n7100-without-removing-emmc-pictures-1945278/

If I had such solder skills...

I would buy for 200 Euro eMMC solution..

Then it would be much easier to play with Bootloader and Security...

Maybe if eMMC fully erased... all Security disabled...

NO idea. :(

Best Regards
[Tizen Software Development] adfree:
:cool:

I have now RD-PQ for few stupid tests...

:cool:

Test 1.

Full dump...

dd if=/dev/mmcblk0 of=/sdcard/FULLdump.bin

I have 32 GB SDCard inside... so I hope 16 GB fits... because not found Format menu in Tizen 2.2 Firmware...

:confused:

Later more, if my dumps are ready...

Best Regards
[Tizen Software Development] adfree:
After little odyssee to find Drivers for SLP... :o (DL Mode)

I was able to flash my RD-PQ with:

RD-PQ-REF-RSA_2.2.0_RC11_WiFi.exe

Under Windows XP...

<ID:0/009> Added!!
<ID:0/009> Thor engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> NAND Write Start!!
<ID:0/009> u-boot-mmc.bin
<ID:0/009> s-boot-mmc.bin
<ID:0/009> uImage
<ID:0/009> modules.img
<ID:0/009> data.img
<ID:0/009> ums.img
<ID:0/009> platform.img
<ID:0/009> Removed!!
<ID:0/009> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Added!!

Next step is to check if Odin uses same protocol...

By stupid edit text string in Odin3...exe

Will prepare uimage or something else in TAR and check if Odin do something to RD-PQ...

Maybe THOR uses really other transfer prototcol...

:confused:

We will see. :D

Best Regards
[Tizen Software Development] adfree:
:confused:

I am not able to detect COM Port with Odin...

Tried different Versions...

1.0

1.85

3.04

3.07

Multiloader from bada detect RD-PQ COM Port...

:confused: :confused:

Short tried Heimdall...

https://github.com/Benjamin-Dobell/Heimdall/downloads

Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12

I have edited heimdall.exe to change THOR/ROHT string... instead ODIN and LOKE handshake...

Hmmmmmmmm...

http://xdaforums.com/showpost.php?p=40746815&postcount=3

2 years later and I wished I would know which Odin Version he tried... :rolleyes: :(

Best Regards
[Tizen Software Development] adfree:
:o

Stupid me has forgotten first start Odin, then connect... :rolleyes:

With modified Odin3 v1.85.exe I am now here:

<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)

Hmmm...

I have forgotten, because PIT file was only inside uboot... will check if dump have PIT on known position or it works different on RD-PQ...

Best Regards
[Tizen Software Development] adfree:
heimdall-suite-1.3.2-win32\Heimdall Suite>

heimdall download-pit --output test.pit
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
ERROR: Failed to access device. [COLOR="Red"][B]libusb error: -12[/B][/COLOR]

Somebody have experience with Heimdall and PIT dump?

Is Heimdall reading PIT including Signature?

For instance from I9300 with 256 Byte Signature?

I mean this RSA 2048 security thingie?

Thanx in advance.

Best Regards

Edit 1.

Not found solution, but seems I am not alone...

http://xdaforums.com/showthread.php?t=1574522&page=2
[Tizen Software Development] adfree:
Heimdall needs own driver(s)... so minimum to replace Samsung driver... with help of:

zadig.exe

So I was able to read out PIT file from I9300... seems including RSA 2048 Signature... :good:

heimdall download-pit --output test.pit

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...

Beginning session...
Session begun with device of type: 131072

Downloading device's PIT file...
PIT file download sucessful

Ending session...
Rebooting device...

With SM-Z130H and RD-PQ no luck...

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!

Best Regards
[Tizen Software Development] adfree:
4F44494E
640000000000000000000000..
640000000500000000001000..
640000000200000000041E00..
650000000100000000000000..
650000000200000000000000..

Sniffed Commands from SM-Z130... before PIT file is received.. from Odin...

Commands send 1024 Bytes to handset... I have again little problem... to sniff complete transfer... :rolleyes:

First Command is Handshake... ODIN as Hex Value... handset answers with LOKE in HEX...

Later I will check I9000 and/or I9300 to see differences how Odin get PIT info...

Best Regards
[Tizen Software Development] mapcuk:
adfree,

You mentioned migrate_2.3_bootloader.tar.gz

I've upgraded Tizen from 2.2 - > 2.3 and used migrate_2.3_bootloader.tar.gz for updating bootloader (description).

As Tizen 2.3 firmware for rd-pq is unstable I tried to rollback to 2.2 by following commands:

lthor Tizen_RD-PQ_System_20130716_1.tar

lthor tizen-2.2_20130719.3_RD-PQ.tar.gz

But during uploading lthor stopped on uploading 'uImage', the device froze I rebooted by long pressing power button.

Since that moment the device shows Tizen logo and does not boot. But I still can enter to download mode and upload firmware which everytime hangs on 'uImage' file uploading.

tar-files without uImage are flashed successfully.

Is there any chance to recover the device and rollback to Tizen 2.2.1 ? :confused:
[Tizen Software Development] adfree:
I have my first and only RD-PQ since 1 month.

And never updated via lthor. :o :o :o

I am absolute Linux Idiot... and Windows Fanboy... :D :o

Only 1 time updated in Windows XP with this:

RD-PQ-REF-RSA_2.2.0_RC11_WiFi.exe

http://xdaforums.com/showpost.php?p=63406918&postcount=27

RD_PQ_REF_RSA_2_2_0_RC11_WiFi.zip seems nowhere to find in Google...

I will try to search some infos...

If I remember correct... somewhere I saw 2 PIT files inside uboot...

Maybe partition layout is changed...

uImage is Kernel...

I'll try to collect more infos...

Best Regards
[Tizen Software Development] adfree:
Inside this package I can see params.bin...

This looks like PIT is update from Version 8 to Version 13... with help of params.bin...

You can find the PIT files inside u-boot-mmc.bin...

Attached files for study...

"We" could try to ask here:

https://developer.tizen.org/forums/sdk-ide/tizen-2.3-rd-pq-device?tab=active

If someone downgrade from 2.3 or 2.3.1 back to 2.2 in safe way...

:confused:

Best Regards
[Tizen Software Development] adfree:
2.1.0_public.exe
RD-PQ-REF-RSA_2.2.0_RC11_WiFi.exe

Both have same Version of Downloader... Thor One Click Download

Downloader ends at address:

0x6A1FF

Then TAR file 1 added...

Contains:

modules.img
s-boot-mmc.bin
u-boot-mmc.bin
uimage

Then TAR 2 follows... with:

data.img
platform.img
ums.img

Will check if between end of TAR 2 and end of file something like Security check...

A20600

This seems end of TAR part... then 488 Bytes left... most of them are 00...

Maybe CRC, file size...

First feeling end of file looks not secured... not hard...

Maybe I can simple add my own TAR file(s) to Windows THOR... :D

Best Regards
[Tizen Software Development] mapcuk:
[MENTION=1030585]adfree[/MENTION]

I think params.bin from migrate_2.3_bootloader.tar.gz is key for understanding what is changed.

I tried to read it by stings params.bin which looks like "config language".

But I can not understand it. There are some manipulations with environment, bootloader.

I've found another mention about successful rollback to 2.2.1. I asked him.

Most instructions for flashing, rooting are for Windows users. So I believe Windows is right choice here.
[Tizen Software Development] adfree:
:good:

Marco helped.

https://developer.tizen.org/forums/general-support/tizen-2.3-rd-pq-device-available

Thanx.

Lead to this:

http://download.tizen.org/releases/2.3/2.3-mobile/bootloader/

Best Regards
[Tizen Software Development] mapcuk:
[MENTION=1030585]adfree[/MENTION] yes, I have just finished flashing. It works!

1) lthor revert_2.2.1_bootloader.tar.gz

Linux Thor downloader, version 1.4

Authors: Jaehoon You <jaehoon.you@samsung.com>

USB port is detected : /dev/ttyACM0

revert_2.2.1_bootloader.tar.gz :

[u-boot-mmc.bin]	1024k

[params.bin]	4k

-------------------------

total :	1.00MB

Download files from revert_2.2.1_bootloader.tar.gz

[u-boot-mmc.bin]| sending 1024k/ 1024k 100% block 1 [avg 5.51 MB/s]

[params.bin] - sending 4k/ 4k 100% block 1 [avg 0.06 MB/s]

revert_2.2.1_bootloader.tar.gz completed

request target reboot : success

2) Flash 2.2.1 by the instruction.
[Tizen Software Development] mapcuk:
So tar archive is different from standard ?

It same approach as if lthor is used. And why it would be different? :o
[Tizen Software Development] adfree:
"Template"

If someone want try flashing RD-PQ with Windows only.

Tested few times successfully with RD-PQ with:

Win XP 32 bit :good:

Win 7 32 + 64 bit Tool starts... not tested with attached handset...

Win 8 seems incompatible. Flash Tool is older as 2 years...

This template is EMPTY and for study AND:

AT your OWN risk!

Details later...

[MENTION=566818]mapcuk[/MENTION]

If you and your RD-PQ are still alive.

And you are an Windows User...

We could do some practice together... so you understand maybe more, what I did or what I wanted to do...

Instead lthor under Linux to use...

P.S.:

In theory this should also work with TM1...

Best Regards
[Tizen Software Development] mapcuk:
I don't have Windows installed now. But I have one in VirtualBox. Doesn't it work there ?
[Tizen Software Development] adfree:
[MENTION=566818]mapcuk[/MENTION]

Thanx for fast feedback.

As Linux user it is easier for you to work with lthor.

For me it is very hard, to understand Linux... :o

...so I prefer Windows solution. :D

No idea, but better stay as Linux with lthor... to prevent trouble to your RD-PQ...

I never used VM solutions... my OS is ever on Hardware...

1 PC with XP

Second with Win 7... and...

With Win 8 I have only short experienced, then I deinstalled this Windows Version...

Best Regards
[Tizen Software Development] mapcuk:
[MENTION=1030585]adfree[/MENTION]

I've got Windows and my RD-PQ is still alive :)

Let's practice :)

I also installed Samsung driver and downloaded Odin.

It's look like Odin doesn't detect the device when I switched it to download mode. Android and Tizen download modes might be different.

But Odin shows something "Added .." when Tizen OS runs.

Also I'm able to load SLP bootloader by pressing Up+Down+Power.
[Tizen Software Development] adfree:
[MENTION=566818]mapcuk[/MENTION]

Cool. :cool:

1.

Forget Odin...

Not only handshake is different, also Commands...

Look here:

http://xdaforums.com/showpost.php?p=63478721&postcount=32

GT-I9300 Commands with ODIN looks similar...

First few Commands are 1024 Bytes long

THOR Commands are only 256 Bytes... an first Byte is:

0xCA

So THOR sents something with CA instead 64...

1a.

You could sniff Commands with Sniffer Tools... for USB.

I am using good old Portmon called Windows Tool.

1b.

Later I will short "demonstrate", how handshake could be self tested...

For instance with this Windows Tool...

http://xdaforums.com/showpost.php?p=48117152&postcount=34

Later more...

2.

RD-PQ SLP bootloader...

:o

At the moment I have 0 idea what we could do with it...

It seems no Com Port is detected or other kind of driver? Something like MTP?

3.

About my "Template"...

If you tell me, which RD-PQ Firmware you want flash with Windows, we could do it "together"... instead I upload whole file... :o

For instance tizen-2.3.1-mobile_20150921.1_mobile_target.tar or tizen-2.3-mobile_20150812.1_mobile_target.tar ?

Or any other TAR file...

I am using WinHex... but every HEX Editor should work... which can handle 1500 MB file...

Best Regards
[Tizen Software Development] adfree:
http://download.tizen.org/prerelease/tizen/mobile/

:confused:

Here for instance:

http://download.tizen.org/prereleas...0151110.4.20151110.144250/images/arm-wayland/

Any idea what here is...

I can see RD-PQ in filename...

Will download...

Best Regards
[Tizen Software Development] mapcuk:
[MENTION=1030585]adfree[/MENTION],

FYI

About Odin there is an alternative tool heimdall ( source )

Lthor source is available

Let's try to flash 2.3 firmware. During it I can try to sniff.

As I understand without lthor and in Windows?

What tool should I install?

What is next step then?

I don't know about those new images on tizen server. They published them just today. How did you find it so fast? :)
[Tizen Software Development] adfree:
C:\sdb>sdb shell
sh-4.3$ su
Password:
bash-4.3# cat /etc/*-release
NAME=Tizen
VERSION="3.0.0 (Tizen3/Mobile)"
ID=tizen
VERSION_ID=3.0.0
PRETTY_NAME="Tizen 3.0.0 (Tizen3/Mobile)"
ANSI_COLOR="0;36"
CPE_NAME="cpe:/o:tizen:tizen:3.0.0"
BUILD_ID=tizen-mobile_20151110.4.20151110.144250_mobile-wayland-armv7l-n4
Tizen3/Mobile 3.0.0 (arm)
VERSION = 3.0.0
CODENAME = Next
BUILD_ID=tizen-mobile_20151110.4.20151110.144250_mobile-wayland-armv7l-n4
Tizen3/Mobile 3.0.0 (arm)
VERSION = 3.0.0
CODENAME = Next
BUILD_ID=tizen-mobile_20151110.4.20151110.144250_mobile-wayland-armv7l-n4
bash-4.3#

Interesting...

Now I know why I was not able to find text string 2.4.0 :rolleyes:

Because it seems Tizen 3... :D

On my RD-PQ...

bash-4.3# cat /proc/version
Linux version 3.10.60-24.7-arm-trats2 (abuild@w24) (gcc version 4.9 (Tizen) ) #1 SMP PREEMPT Thu Nov 5 03:19:13 UTC 2015
bash-4.3#

But at the moment useless for me, as I can't see anything on my screen... :D :o

Best Regards
[Tizen Software Development] adfree:
About device...

I saw this is also on TM1 not working...

So I did little research on my RD-PQ and SDK Emulator... to understand why it fails... :rolleyes:

On 2.2.1 it works. :good:

No idea if on all Versions from 2.2.x but this I have tested:

RD-PQ-REF-RSA_2.2.0_RC11_WiFi.exe

With SDB you can play...

navigate to path:

usr/apps/org.tizen.setting

You can start "app" via:

launch_app org.tizen.setting

2.2.1 seems different... but in 2.3.1 it is easier to identify...

Check bin and lib folder...

In bin folder:

setting-about-efl

But this seems "dummy"... no idea...

But playing with lib folder is funny... :D

If you remove libsetting-about-efl.so then something like "unsupported" is visible... if you click About device...

rm libsetting-about-efl.so

I have short tested to replace... :D

Short ...

mv libsetting-storage-efl.so libsetting-about-efl.so

Now Storage window is visible... if I click About...

Will check the other *.so files...

libsetting-about-efl.so libsetting-password-efl.so
libsetting-developeroption-efl.so libsetting-phone-efl.so
libsetting-display-efl.so libsetting-profile-efl.so
libsetting-fileview-efl.so libsetting-reset-efl.so
libsetting-flightmode-efl.so libsetting-ringtone-efl.so
libsetting-font-efl.so libsetting-security-efl.so
libsetting-locktype-efl.so libsetting-storage-efl.so
libsetting-manage-applications-efl.so libsetting-time-efl.so
libsetting-network-efl.so

...

Edit 1...

""Worked""... I mean I see something... :D

mv libsetting-flightmode-efl.so libsetting-about-efl.so
mv libsetting-font-efl.so libsetting-about-efl.so
mv libsetting-reset-efl.so libsetting-about-efl.so
mv libsetting-security-efl.so libsetting-about-efl.so
mv libsetting-network-efl.so libsetting-about-efl.so
mv libsetting-locktype-efl.so libsetting-about-efl.so
mv libsetting-password-efl.so libsetting-about-efl.so
mv libsetting-profile-efl.so libsetting-about-efl.so

At your own risk!

Only for study...

Best Regards
[Tizen Software Development] adfree:
[MENTION=566818]mapcuk[/MENTION]

Totally forgotten you helped me 1 year ago... :good:

Many thanx.

http://xdaforums.com/showpost.php?p=55514573&postcount=36

About flashing RD-PQ with Windows + Tool...

My Example... :D

http://xdaforums.com/showpost.php?p=63847621&postcount=37

Step 1.

revert_2.2.1_bootloader.tar.gz

Unpack to:

revert_2.2.1_bootloader.tar

Step 2.

Be sure you have now revert_2.2.1_bootloader.tar and not 2 files...

Rename into .bin for easier use in HEX Editor...

Check filesize... end of file...

00101800

Step 3.

Reverse order 00101800:

[B]00181000[/B]

Big Indian little Indian...

This you can find in my Example... 0x00181000...

Near end of file...

Step 4.

You can see my Template...

http://xdaforums.com/showpost.php?p=63617312&postcount=42

TAR file is inserted at 0x6A200

Step 5.

Filesize correction at end of file... at offset:

0x46583250

Best Regards
[Tizen Software Development] mapcuk:
[MENTION=1030585]adfree[/MENTION]

You are more than welcome! :)

What did you do with dump.bin after?

I guess you extracted sboot and uboot bootloaders? Aren't they encoded some how? Is it possible to read asm?

I did

gunzip -k revert_2.2.1_bootloader.tar.gz
du -b revert_2.2.1_bootloader.tar
1054720	revert_2.2.1_bootloader.tar
hd revert_2.2.1_bootloader.tar | tail -n3
00101400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00101800

hd shows that the file ends on address 00101800

But I don't understand where to put this address (in little endian format) ? Just add at the tail of revert_2.2.1_bootloader.tar file or replace last 4 bytes?

Recent days I was thinking about how to install android on RD-PQ device.

So I have some questions:

Is it possible to run Android with existen uImage kernel? I guess not but why?

PIT (partition distribution) of RD-PQ is different from Samsung SIII with Android?

Where is Download Mode ? Is it separate partition? Who starts Download Mode: sboot or uboot?

I compared params.bin from migrate and revert archives. The difference only in 2 variables: pit_ver, ver

< pit_ver=13
---
> pit_ver=8
30c30
< ver=U-Boot 2011.03 accepted/tizen/2.3/wearable/20141031.071205-1-g61220ee (Nov 25 2014 - 23:11:35)
---
> ver=U-Boot 2011.03 accepted/tizen/2.3/wearable/20141031.071205-dirty (Nov 25 2014 - 18:28:32)

pit_ver looks like PIT file version. So PIT file itself should be in u-boot-mmc.bin, right?
[Tizen Software Development] adfree:
http://xdaforums.com/showpost.php?p=64118457&postcount=38

My theory about simple rename seems wrong... :o :crying:

In the next days I will try to reanimate my Victim... :crying: :o

Best Regards
[Tizen Software Development] adfree:
I need more time & brain... :D

But maybe I have luck... :o

Short compared my RD-PQ with I9300 PCB...

RD-PQ PCB revision is newer...

But first impression... I can read GT-I9300 on RD-PQ PCB...

Compared with this... "GT-I8800"

http://xdaforums.com/showpost.php?p=51724095&postcount=58

Later my other side from PCB...

Best Regards
[Tizen Software Development] adfree:
i9300_SD_card_boot

http://forum.gsmhosting.com/vbb/f777/if-you-want-make-samsung-s3-i9300-boot-card-look-here-1696292/

Looks like this...

https://www.youtube.com/watch?v=AGNxKaGq2lY

I think this I will try first...

Because Tweezer action seems very hard to perform... for me. :o

Power on and so on without kill something... if you have only battery and no special equipment...

Selfmade UART cable I have...

Later I will check theory...

Best Regards
[Tizen Software Development] adfree:
Still no luck with reanimation... :o :(

Used 32 GB SD...

Used XP...

My selfmade UART cable has hopefully correct Resistor...

Tested 3 times...

First attempt:

- plug in UART cable

- then Battery...

waited 10 minutes...

result nothing... nothing on Display and nothing in Terminal Tool... :(

Second attempt...

First battery... then UART cable...

Same result... nothing...

Third attempt...

Somebody wrote about 301 K ohms resistor... like in Download Mode Jig...

http://forum.gsmhosting.com/vbb/f777/if-you-want-make-samsung-s3-i9300-boot-card-look-here-1696292/

Nothing... :o :crying:

For Tweezers action I am scared... because this is soooooo tiny and I have only battery... :o

https://www.youtube.com/watch?v=jOCmT5JYaNU

Maybe I would buy this one...

https://www.conrad.de/de/labornetzg...c-0-3-a-45-w-anzahl-ausgaenge-1-x-393647.html

But 70 Euro... :o

For this money I could buy maybe new RD-PQ... :D :o :(

I have short checked my 32 GB SD... will test maybe first in I9300 with T-Flash function in Odin...

As I can remember few or 1 SD card not worked...

Not all SD cards supported...

Best Regards

Edit 1.

Hmmmmm... DL Jig seems also possible... but also here not using Battery...

https://www.youtube.com/watch?v=A3sxh9eKodM

110 seconds...

https://www.youtube.com/watch?v=DJ8uNpSsgQM

Edit 2.

Will try to collect input for my little brain again...

http://xdaforums.com/galaxy-s3/general/samsung-s3-i9300-note2-n7100-i9500-s4-t2647558

http://xdaforums.com/galaxy-s3/general/galaxy-s-iii-gt-i9300-hard-brick-fix-t1916796
[Tizen Software Development] adfree:
Seems the 32 GB SD card was wrong idea... :rolleyes:

I have 4 GB SanDisk... seems "better"...

But still no luck with SD Recovery...

Harhar funny...

Seems I have tried nearly 2 years ago to reanimate I9300 PCB with tweezers...

http://xdaforums.com/showpost.php?p=50690538&postcount=251

Without luck... :o

To check the other components and to prevent damage... I have removed RD-PQ PCB...

And inserted working GT-I9300 PCB...

Display work + Touch work + Touchkeys

Seems all working with Android + GT-I9300 PCB.

Now I could proceed with dead PCB and tweezers... with Display... or maybe without...

But less risk to damage more...

I have enough spareparts... and many broken Displays... :rolleyes:

I will try something like this again...

http://dl-1.va.us.xda-developers.co....JPG?key=ofCTwDBW8_t04JYdJIk4Sw&ts=1449639365

So in theory I can insert battery... and use tweezers at the same time...

With my 2 left hands... :D

Best Regards