Bricked using a Heimdall dump HELP

[andytof46]

Hi I REALLY NEED HELP NOW!!!!!!

I was using heimdall and just doing a dump with

heimdall dump  --chip-type NAND  --chip-id 0  --output hdump2.img

So I was watch my file size grow steadily but surely and I accidentally kicked my usb plug out....... Well all I get now is the black screen of death.......

I know 100% I can still communicate with my device, as I ran the command again and it got up to about 450~470 Mb and it said bad read!!!!!

I'm guessing something has become corrupted but i'm also assuming if I can read my TAB's image then I should be able to write to it.... hopefully

What should I do.......
The tab has on it Stock Australian Optus Rom - Don't know if it's locked Lickley to be though
I have the overcome rom, humber kernel image,

but what command would I use and what would I need to re flash to get it working again apart from send it back to Samsung.

Actually just plugged in after a good nights sleep and running heimdall says it can't find a compatible device....... I'm Bricked then hey?

 

[btyork]

It's possible the device has a low battery, which is why it wont recognize it. Are you sure it has a charge? If/When you plug it into the wall, does the batter icon show up?

Can you get into any boot mode? (Recovery[Doubtful] or Download)?

*edit* also, this kind of question goes in the Q&A forum, if we're lucky, a dev will move it for you though.

 

[andytof46]

sorry bout the section

Hi there again, she's charged and still not recognised off to samsung we go

 

[GANJDROID]

Have you tried to repartition via Odin?

Sent from inside a whale.

 

[daml]

---as far as i know--- dumping isnt supported. well its not that. it just never worked. it sets a state on your device, dumps then sets the state back. dumping doesnt work so that state is never set back afterwards.

happens in odin too, not a heimdall problem.

contact the heimdall developer he can tell you what you need to do.