[Galaxy Tab General] cx5:
Hi spacemoose1

Thanks for link and as always, thanks for honeycomb port. I would like to ascertain the definition of BRICK? with your help, if I may.

(disclaimer: pls forgive my wrong terms or exagerated explanation, but most importantly, pls correct me if I'm wrong)

BRICKed = software total lost, must use JTAG to force revive it, Samsung has it, or buy from web supplier around 300 USD ??? 500 USD ???

JTAG is a device to push software into all newly borned IC. I.E. when factory make IC, it's empty software inside, hence has a special device to push voltage into all sections of the IC, then force the code in.

Another term is ???CRASH??? or ???HANG???, (I don't know) anyway is not BRICKed, hence a reflash can recover it.

Samsung uses proprietary method a lot, not follow conventional, make usb driver very complex. USB driver install EXE around 15MB to 28MB depends on version, ALL work the same.

but, when the device = sgt7 in different state/condition, the driver must RE-ESTABLISH again, or else cannot work.

I.E.

state 1 = "OPERATIONAL"device in android operation, normal use, surf web, phone call etc

state 2 = "SLEEP" device powered off, show battery big icon charging when powered by charger

state 3 = RECOVERY mode

state 4 = DOWNLOAD mode - this is one of the way to FORCE flash to recover, as long as bootloader and something still intact

state 5 = PHONE-!-PC mode

stage 6 = "COMA" device powered off, NO show of battery big icon, even when charger supplied. Don't panic, let it charge fully 4 hours from 2 amperes supply, 10 hours from PC 500mA. It will start again !!!. Battery big icon will appear around 30% battery charged, I know because that's what I saw. I didn't check when it's in 10% or 20%. The 1st time I check was already 30% up from no-boot or no respone.

User need to plug device into PC during each of the state above at least once, in order for various flashing functions to work.

i.e. when it's a newly arrived device, usually install the usb driver 1st, with device state in android OS running properly, then plug in to USB and see "new device detected" installing, pls wait. Finished.

But when flashing via Odin using state 4 = DOWNLOAD mode, user may experience no connection, no COM3 or something. Because device must be unplugged in USB, power-up in state 4 = DOWNLOAD mode, plug in USB, "new device detected" installing = RE-ESTABLISH, done. UNPLUG USB, replug in usb, then COM3 appears FLASH will be succesfull.

same goes for other state.

p.s. many users reported BRICKed but then recovered WITHOUT JTAG is misleading beginners, hence should rename the term to ???CRASH??? or ???HANG???. although some previously use "SEMI-brick", which is acceptable.

stage 3 = ClockWorkMod flashing (super convenient, especially on the move without PC)

stage 4 = Odin / Heimdall both works (still convenient and easy :) )

stage 5 = Odin / Heimdall both works (still convenient and easy :) )

???CRASH??? or ???HANG??? or "SEMI-brick" is usually SUCCESFULLY recovered via restock+

PIT

(final disclaimer, incase above is correct and help and is copied, pls correct whatever mistakes found, feel free.)

*** Thanks for all those who taught me my mistakes *** devs and fellow forumers