Tab bricked(?) by trying to flash stock Android 2.3.3

RFZ

Member
Jan 7, 2009
40
0
0
Hi,
got a Samsung Galaxy Tab GT-P1000 with Stock Android 2.2 FROYO.XWJMK.
I wanted to install Andoid 4.x/5.x but only found guides telling me to install "original" Android 2.3.3 first.
So I found a Download containing "Android 2.3.3 Gingerbread [XXJQ1]", "gt-p1000_mr.pit", "GB_Stock_Safe_v5", "Odin3_v1.7" and "JPZ Modem" (europe).
Trying to follow these instructions ( https://www.youtube.com/watch?v=iI79j97R4qw ) I booted the device into Download-Mode by pressing VOL_DOWN + POWER.
I selected the files in odin as described ( screenshot: https://pl.vc/4ehx3 ) and connected the device. It showed up as COM5 so I hit start.
It immediately failed after a fraction of a second. A second try didn't even start the process:

Code:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/005> Removed!!
I powered the device off. Since then, it doesn't boot up. All I get is a white outlined mobile connected to a pc with a yellow exclamation mark like this: http://forum.xda-developers.com/showthread.php?t=2258444
I cannot enter download mode (VOL_DOWN+POWER) or recovery (VOL_UP + POWER).
However, it still gets recognized by odin in this state.

Any ideas?
 

Attachments

RFZ

Member
Jan 7, 2009
40
0
0
btw. I just found out that Odin may have failed because windows was always using a standard microsoft virtual com port driver for the device. I now selected the driver manually from the Samsung Kies installation folder but I got three to choose of:
SAMSUNG Mobile USB Serial Port
SAMSUNG Mobile USB OBEX Serial Port
SAMSUNG Mobile USB At command Port
Guess the first one should be correct? Can someone please confirm that?
 

RFZ

Member
Jan 7, 2009
40
0
0
Okay, I've now selected "SAMSUNG Mobile USB Serial Port" by hand... (screenshot 1)
Odin now is able to continue after SetupConnection for the first time ever. Now it fails on "Re-Partition operation failed" without "Re-Partition" being checked. (screenshot 2)
Should I enable "Re-Partition"? I'm trying to flash stock Android 2.3 now which I've downloaded from sammobile ( http://www.sammobile.com/firmwares/download/3296/P1000XWJQ8_P1000DBTJQ1_DBT/ ).

Considering I've used a wrong driver before... Is it somehow possible that the device got bricked not by me failing to flash correctly, but by Odin trying to communicate with the device using the wrong driver?

Btw. the microsoft default driver is only selected by Windows 10 by default. Windows 8.1 and earlier won't install a driver for this device by default...
 

Attachments

RFZ

Member
Jan 7, 2009
40
0
0
Well... Tried heimdall (ui), read pit successfully, closed and rebooted. Device boots fine again - nothing flashed.
Guess just
Code:
heimdall close-pc-screen
would have done the trick.