Database Users

Totally bricked my Samsung Galaxy Tab P-i9000

Hello - I urgently need help with my Samsung Galaxy Tab.
I flashed a wrong PIT/PDA & what happened is:
- my Galaxy Tab does not reboot at all
- the flashlight in the back suddenly switched ON automatically
No matter how long I press the Power Button, the device switches off just for one second, and then the flashlight switches ON again - but no reboot.
I cannot get into download mode / when I try to use commands with Odin, it only says: error: device not found.
Odin does show my device ([COM:4]), it appears as: Added // only the download mode does not work!
When I tried to start SuperOneClick, trying to Unroot, it is stuck with: "Waiting for device"
Weirdly, though, my netbook does install the drivers automatically when I plug it in. Which means, my netbook can "read" the device.
Does anyone here know how I could make the extreme Hard Reset, without having to reboot?
--------------------------
If you think this post should rather go to the Developers section, please feel free to move it // I am thankful for any help

Have you tried connecting to it with ADB to see if you can reach it at this level (apart from with SuperOneClick)? Try installing the Droid Explorer application on your Windows PC and see if it will recognise your Tab. If it will you should be able to initiate a reset from the Droid Explorer UI. If it won't I would suggest that you are hard bricked and it will have to visit Samsung. Good luck!

Hello,
thank you for your advice.
adb does not detect my device ..
and, unfortunately, neither does Droid Explorer
Just find it so strange that ODIN does ..
but like you said -
I am also afraid, that this is a "hard brick" & I will go see the retailer tomorrow.
Thank you, though, for offering help.

QueenAmy said:
Hello,
thank you for your advice.
adb does not detect my device ..
and, unfortunately, neither does Droid Explorer
Just find it so strange that ODIN does ..
but like you said -
I am also afraid, that this is a "hard brick" & I will go see the retailer tomorrow.
Thank you, though, for offering help.
Click to expand...
Click to collapse
If Odin sees it, its not bricked. What image is on the LCD when Odin sees it, or is it blank?

rotohammer said:
If Odin sees it, its not bricked. What image is on the LCD when Odin sees it, or is it blank?
Click to expand...
Click to collapse
I guess the problem here is that even if Odin sees the USB device connected, if the Tab won't go into download mode then it's as good as bricked. With the SGS you can construct a USB jig with a 301k resistor between pins 4 and 5 of the micro USB to push the device into download mode if it won't respond any other way. I wonder if a similar thing would work for the Tab... Sounds like a challenge for someone who has two Tabs and doesn't mind experimenting a bit with one of them.

bdl1969 said:
I guess the problem here is that even if Odin sees the USB device connected, if the Tab won't go into download mode then it's as good as bricked. With the SGS you can construct a USB jig with a 301k resistor between pins 4 and 5 of the micro USB to push the device into download mode if it won't respond any other way. I wonder if a similar thing would work for the Tab... Sounds like a challenge for someone who has two Tabs and doesn't mind experimenting a bit with one of them.
Click to expand...
Click to collapse
lol, I'll get my cheap Chinese Tab cables this week and hack one up to test.
My guess is that Odin will only see the Tab when it is in download mode. Id try flashing it in that state and find out for sure. It sure cant hurt.

You went to your retailer?I have exactly the same problem!!

First of all - THANK YOU for having started this discussion.
Yes, I went to the retailer. My Galaxy Tab is with Samsung Technical Support now; will keep you posted.
To answer some earlier questions, yes ODIN did recognize my Tab; but the screen on the Tab remained totally black. Only this strange "flash" light on the back kept glowing.
rotohammer, if you really get to test what you mentioned before, I'd be interested to hear what happened - but, personally I would not recommend it, unless you are sure you want to risk completely ruining your dear Tab.

studio54 said:
You went to your retailer?I have exactly the same problem!!
Click to expand...
Click to collapse
I did ... and less than 2 weeks later ..
Update:
13-Jan-2011
Today noon I got a call from my retailer my Galaxy Tab was ready to be picked up & I was really lucky: my retailer said the repair would normally cost EUR 650.-
.. as I had damaged the whole mainboard ..
but as the Tab was less than 1 month old, they were so kind to do it w/in my warranty - so I did not have to pay for it.
I'm very relieved, as you can imagine.
Got my Galaxy Tab back with a brand-new mainboard, everything is working well &
I sure learned my lesson.
I will not flash the Galaxy Tab again.
Only because Galaxy Tab and Galaxy i9000 are both on Froyo, it does NOT mean that you can flash the same software!
I wanted to apply the 3 button combo fix on my Galaxy Tab but apparently it does not work!

Bricked mine as well, but mine is a weird case
I bring up the weirdest case of bricking so far, i was on an official Arabic (P1000JPJK2)Firmware, and i noticed a new Arabic release on SamsungFirmware.com (P1000JPJM3) i downloaded it and downloaded the .pit file, Started Odin v1.7 and unchecked repartition, selected the PDA and the pit and started the processes, odin finished and Reseted the device and give me the green light with the word PASS, however, the my p1000 decided to reboot into download mode automatically, so i rebooted the device manually and got stock in the Samsung Logo and keeps looping. so i decided to go back to my previous Rom but it will always fail and i would have to reboot my tab and it will show the good ol' Phon-PC logos, however, odin would see it and would flash anything i want. i tried flashing various versions of rom's but they would all fail... i tried repartition checked and unchecked and nothing worked, so lastly i decided to flash the .pit file alone and that worked and got me back to where i was stuck in the Samsung logo loop and no ROM would be flashed through Odin BUT the (P1000JPJM3) but it still will not boot! and funny enough i took it to sammy's repair shop and they told me to come pick it up in a few hours but they told me that they failed to repair it and they would need to keep it till tomorrow, but they guy was not that optimistic about getting it repaired and to make things worse i couldn't get unrooted so there is a good chance that there will be no warranty... does this mean that i bricked it for good? please help me.

phone will not turn on after restore with Heimdall

my phone will not turn on after successfully performed a restore backup with Heimdall
the backup are the Original from Factory....
whats happen i try to charge my phone, and the screen doest show any sign of life
it doestn boot it doesnt charge, it cannot opened by me
heeeeeeeeeeeeelllppppp

If Heimdall didn't give you any errors then the flash went through fine. Are you sure that you flashed files that were meant for your particular model of Galaxy Tab?
Given the information you've given about the device not turning on or responding at all, it seems as though you've flashed a bootloader that was not designed for your device. You can try create a custom jig and it may be able to boot your device into download mode using the backup secondary bootloader. If that doesn't work then the only other fix is a JTAG fix which is best performed by Samsung themself.

i put in First Boot Loader
boot.bin
i Put on Secondary Boot Loader
Sbl.bin
any mistakes here? these files are recovered from my Tab with Roto BackUp
any chance to do it in da house and not from Samsung Warranty?
Benjamin Dobell said:
You can try create a custom jig and it may be able to boot your device into download mode using the backup secondary bootloader.
Click to expand...
Click to collapse
HOW to do IT ??? explain me more steps

i found this video for make cable for samsung captative......
http://www.youtube.com/watch?v=Rdn5GoRjhn0
what type of cable i need to do the same on my Tab???
anyone can tell me any steps please??

Maybe try this:
http://forum.xda-developers.com/showthread.php?t=885919&highlight=reset+battery

interesting information but i need to research much more
http://forum.xda-developers.com/showthread.php?t=819551
Reediting:
I try with Android SDK and ADB reading this little tutorial
http://mingersoft.com/blog/2010/09/samsung-galaxy-s-why-download-and-recovery-modes-are-missing/
When I plug it into my computer it tries to install a driver for "SEC S5PC110 Test B/D"
any one have a copy of this driver, or can create one for this proposit????

Does the device power on and show anything on the screen? If the Tab won't even turn on then you are bricked but not to worry.. I did the same to mine, and samsung has repaired the device and its on its way home to me today.

i think the better idea is call samsung, wait 2 or 3 weeks.......
but i want know more about some info posted in this thread
perhaps, how and where are the first person whit this Driver, or the first or second with a custom cable jig Compatible with Galaxy Tab and can post where are the steps to do it in da home

HEIMDALL bricked my phone

Hi,
I just tried this command on my i9000
heimdall dump --chip-type NAND --chip-id 0 --output ttt1
It bricked my phone. I thought this was going to be a read only function, but it seems to have written something bad to my phone.
It is displaying the phone ! computer picture.
The computer does not see a usb device when the phone is connected and download mode is not reachable.

You should use a USB JIG to get into Download Mode again and reflash a stock rom with Odin/Heimdall!
Sent from my SGS with Simply 3.0 RC2 ROM

midas5 said:
Hi,
I just tried this command on my i9000
heimdall dump --chip-type NAND --chip-id 0 --output ttt1
It bricked my phone. I thought this was going to be a read only function, but it seems to have written something bad to my phone.
It is displaying the phone ! computer picture.
The computer does not see a usb device when the phone is connected and download mode is not reachable.
Click to expand...
Click to collapse
Take the battery out for 10 min. and place it back, see then if the phone can be started.

midas5 said:
Hi,
I just tried this command on my i9000
heimdall dump --chip-type NAND --chip-id 0 --output ttt1
It bricked my phone. I thought this was going to be a read only function, but it seems to have written something bad to my phone.
It is displaying the phone ! computer picture.
The computer does not see a usb device when the phone is connected and download mode is not reachable.
Click to expand...
Click to collapse
Dumping doesn't work unfortunately. As far as I know I haven't implemented anything incorrectly as Odin fails as well. I think the secondary boot loader on the device just can't dump properly. There is a note about this if you run "heimdall --help".
The operation is essentially read-only except for a flag that the secondary bootloader sets when you start an operation. The flag is unset when the operation finishes succesfully but the problem is when attempting to dump the phone eventually stops responding. So to fix this you need to put your device in download mode, possibly with a custom jig, then run "heimdall close-pc-screen". This command will just unset the flag so that your phone is able to boot normally, no personal data will be lost.

Benjamin Dobell,
Thank you very much. All is not lost then.
I just have to wait for the cable I just ordered off ebay to arrive so that I can turn it into a jig.
How about a feature request for the heimdall code.
Add into the help text on heimdall that
"Note: dump can brick your phone, so have a 301k jig ready before your try it."

Benjamin Dobell,
I used the jig as you directed, and it worked. I have my phone back with all its contents.
Thank you

midas5 said:
Benjamin Dobell,
I used the jig as you directed, and it worked. I have my phone back with all its contents.
Thank you
Click to expand...
Click to collapse
Great to hear. I'll also include a better warning in the next update, whenever I finally get the time to finish it

Unbricked a Hard Bricked Captivate - Truly Invincible Phone - No JTAG

Past few days were the worst for me as I had Hard Bricked my Captivate.
*** History*** (You may skip this is you wish)
This all started few days ago, like every cappy owner I too had a craze of testing different Roms, untill i settled for RemICS. But soon after a month I got bored and moved to Nostalgic 6.2. The rom looks good, but then when I called someone, there was a lot of static on the line and the other person could not hear me. So I decided to try a different modem, so I installed a different modem and things went back to normal.
Later I found another post on XDA, a comparision table for different modems on captivate. So i wanted to give a try, & this is when things started to get rough.
I installed a few modems and then found that my mobile would not get any network signal. So I planned to use ODIN One-Click (I897UCJF6-final-OCD-REV0) and go back to factory. I used ODIN and was able to go back to factory and everything was back to normal.
***When & How I Messed up my Cappy***
As I was back to Factory (2.1) I wanted to upgrade it to GingerBread. I used Samsung Kies to update it to 2.2 Froyo and while this happened, Kies downloaded the firmware, however while flashing the phone it was stuck at 3% and was there for about 4 hours and wouldnt move further, and the screen was solid green and no images or characters. So I took the risk and manually killed Kies and rebooted the phone. Now the phone would come to AT&T screen and was stuck there, tried the firmware update again and still had the same issue. This is when I decided to go back to Factory using ODIN. Used Odin to flash the phone again and it wouldnt move ahead of Factoryfs.rfs and would be stuck there for hours. So I took the risk and disconnected the cable (I know there is a risk of hard brick, but I trust this phone so much and was impatient to give it another go) and restarted the process. It again did the same thing, but this time the phone shutdown and was on a Black Dead screen. I disconnected the phone and tried to put it to download mode and it wouldnt work. The phone would just not show any signs of life. Connected the charger to check if there is any display and still had a dead screen & no sound. ODin would not recognise the phone anymore and no signs of any PCI device in device manager. Even tried Heimdal and still no go. Tried this for the whole day and i was preety satisfied that this might need JTAG.
I had also left a post for connexion2005 on http://forum.xda-developers.com/showthread.php?t=1041042
By now I had started to surf ebay looking for another Cappy or Infuse. All the signs that the phone gave me were of a Hard Bricked Captivate. However I did notice that if I reseat the battery and then try to power ON the phone, there was no sign of life, but after leaving it for 20 minutes the phone would get a little warm. So I knew that the phone was still alive, just a no video/no post kind of situation.
It was 11:00 pm when it just struck to me that I should try Linux, as there was a faint possibility that Linux may recognise the phone if it was in any kind of life mode.
So i grabbed a copy of Ubuntu and installed it on the same laptop, where the phone showed no life and used the same usb cable. Well once the OS was installed all I did was tried using the Vol UP + Vol Down + USB to put it into download mode and to my surprize the phone immediately went into Download Mode and there was display. :good::good::good::laugh::good::good::good:
Then I just flashed the phone with ODIN and went back to factory........ and everything is back to normal. :laugh::laugh::laugh:
I wouldnt be trying to brick the phone again, but if anyone has a hard bricked phone can definately try this and hopefully should be able to boot back. Please let me know if it wokred for you.
I am not sure if this is the right section to post this but, definately it worked for me where the phone showed all the symptoms of a Hard Bricked Cappy. If the moderators feel it should move to a different section, please feel free to move it.
I am now convinced that Captivate is Immortal...... :angel:\m/:angel:
Please use the Thanks:good: button if this worked for you.:good:
I may not be able to recreate the issue and havent captured any images, but if you have a dead cappy, you can definitely try this and let me know.

Glad your phone got fixed, thanks for taking the time to write it. I'd suggest moving it to captivate general though. This is the development thread.

You didn't have a hard bricked cappy. You had a soft bricked cappy. A hard bricked cappy is when the primary and secondary bootloaders get corrupted, this also breaks download mode. You interrupted the odin process when it was at factoryfs, which is a long time after it's already successfully installed bootloaders.
The fact it booted right into download mode shows us that it had simply been soft bricked the whole time. This has nothing to do with linux, Kies had installed its own USB drivers that do not support the proper communication with the phone in download mode, this is why when you tried to odin it was being so fussy - it was using Kies USB drivers.
A simple removal of kies, installation of the correct samsung USB drivers, and plugging your phone into a different USB port even would have allowed odin to flash properly. This is why when you went into linux it worked right off the bat, because you didn't have kies and kies drivers in linux.
The captivate is far from immortal - I invite you to see what happens when you interrupt an odin session while it is flashing boot.bin and sbl.bin - you'll have yourself a real hard brick very quickly

fohdeesha said:
The captivate is far from immortal - I invite you to see what happens when you interrupt an odin session while it is flashing boot.bin and sbl.bin - you'll have yourself a real hard brick very quickly
Click to expand...
Click to collapse
believe it or not my cable got pulled out right in the middle of the factoryfs and since i cud still enter download mode i tried it again and then my power got cut in boot.bin part, and i was actually still able to boot into download mode even when nothing showed up on my screen, all i did was first pull the battery, hold the down and up volume button, insert usb into phone and insert battery, and somehow it booted into download mode according to odin, so idk the phone may not be invincible, but its close

fohdeesha said:
You didn't have a hard bricked cappy. You had a soft bricked cappy. A hard bricked cappy is when the primary and secondary bootloaders get corrupted, this also breaks download mode. You interrupted the odin process when it was at factoryfs, which is a long time after it's already successfully installed bootloaders.
The fact it booted right into download mode shows us that it had simply been soft bricked the whole time. This has nothing to do with linux, Kies had installed its own USB drivers that do not support the proper communication with the phone in download mode, this is why when you tried to odin it was being so fussy - it was using Kies USB drivers.
A simple removal of kies, installation of the correct samsung USB drivers, and plugging your phone into a different USB port even would have allowed odin to flash properly. This is why when you went into linux it worked right off the bat, because you didn't have kies and kies drivers in linux.
The captivate is far from immortal - I invite you to see what happens when you interrupt an odin session while it is flashing boot.bin and sbl.bin - you'll have yourself a real hard brick very quickly
Click to expand...
Click to collapse
And unbrickable mod fixes this. Therefore the captivate is pretty much immortal. You can even take a hard bricked cappy, do the unbrickable mod once it's already broken, and still have it return to working order.
Way say you now?

Arisenhavok91 said:
Way say you now?
Click to expand...
Click to collapse
What*
I would say of course JTAG'ing a hardbrick is capable of unbricking it, same for about any other device in the world with volatile memory based firmware. this is not a magical new discovery.
They aren't called hard bricks because they become impossible to recover, corrupting bootloaders is called a hardbrick because it takes HARDware modification to fix, not software utilizing the preexisting hardware. Anything else? Anyone else have some wonderful insider info as to how linux can make download mode magically appear? I'm loving the knowledge in here, really. If you're going to spread misinformation, we please ask that you do it in the correct subforum.

Of course, I argued that the Samsung Captivate is "immortal" due to it's ability to be resurrected at times when even a JTAG would fail.
So back to my point of you saying "the captivate is far from immortal" - what say you now?
Edit: If you can't take someone poking fun as such, please don't bother to respond. I won't look back at this even if you do reply, so please, take a chill pill... or some midol.

Arisenhavok91 said:
So back to my point of you saying "the captivate is far from immortal" - what say you now?
Click to expand...
Click to collapse
I would continue to say the captivate is far from immortal, in the same context as my original post you seem so excited to quote - in a software recoverable situation. We are not talking about JTAG and hardware modification anywhere in this thread. he was claiming the captivate is immortal in regards to all situations being software recoverable by magically switching to a different OS, if you could please put on your reading comprehension and context goggles the pieces of the puzzle might start coming together. Also, do not ask questions you won't bother reading the answer to. Thanks!

I say the captivate is pretty much inmortal! xD even without power button ive been using it with no problem and getting into DLmode.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app

[i9505]I think I've hard bricked my phone

Hi guys,
So apparently I did a very stupid thing today. I have a MAC and a Windows 7 on my bootcamp. I've downloaded the firmware for my country (Philippines) from sammobile link: http://hotfile.com/dl/234886746/526112d/GLB-I9505XXUBMG5-20130710140005.zip.html.
I've used heimdall(basically odin for linux/MAC) and if you're familiar with it you actually need to extract the .tar files and flash them one by one on heimdall whereas on odin you just put it on PDA.
Here's what exactly what I did:
1. Booted to download mode(obviously)
2. I then fired up heimdall and added the pit file which I've downloaded from my device. Again if you're familiar with heimdall, you actually need the pit file everytime you flash unlike odin.
3. This is the part where I think I've screwed something up, I've flashed these files which I've extracted from the MG5 .tar file:
- modem.bin
- NON-HLOS.bin
- boot.img
- recovery.img
- aboot.mbn
- cache.img.ext4
- hidden.img.ext4
- rpm.mbn
- sbl2.mbn
- sbl3.mbn
- system.img.ext4
- tz.mbn
According to heimdall the flash was successful and immediately exited download mode. This is the part when the phone was supposed to reboot but it didn't. The blue led was lit and the phone is not rebooting at all so I manually rebooted it via the power button. Now the phone is not booting at all. Literally no power.
I cannot enter recovery mode and the worse part, I cannot enter that damn download mode to try and re-flash the firmware again. The phone has about 90% charge left before I rebooted manually. Also the phone is not charging. I mean even if it's turned off it should charge with the charging animation to indicate that it's charging or the led is lit up, but in this case there was no led lit up nor the charging animation.
I'm quite frustrated right now and I know I should have used ODIN considering that I have bootcamp with Win 7 installed, but I did it for testing purposes and I paid the price and ended up with a $650 brick
Now I know I'm screwed and have probably voided my warranty by doing all this but I just wanna know where did it go wrong or is there something else that I could do before I send it for repairs?

Honestly ... Go back to shop and tell them that Kies told you that there is an update ... and after the phone havent start ...
Or try like this:
Pull out the battery
Plug USB
Hold volume up
and plug the battery
Should see it.. if not try with JIG to enter in download mode

spinky360 said:
Honestly ... Go back to shop and tell them that Kies told you that there is an update ... and after the phone havent start ...
Or try like this:
Pull out the battery
Plug USB
Hold volume up
and plug the battery
Should see it.. if not try with JIG to enter in download mode
Click to expand...
Click to collapse
Yeah I'll go to the shop tomorrow, just wanting to know if there is something else that can be done as the repairs could take months.
There'll be no way for them to know what actually happened and if I'm lucky I would still have warranty and not pay any single cent lol. I'm guessing that they'll replace the motherboard or sumthin. Thank you anyway I'll try that

perhaps your file is corrupted.
even if redownload the firmware and use odin to check the MD5 sum.
you must do your self a JIG usb dongle to force the download mode on your phone.
hope that help you.

mkh.mourad said:
perhaps your file is corrupted.
even if redownload the firmware and use odin to check the MD5 sum.
you must do your self a JIG usb dongle to force the download mode on your phone.
hope that help you.
Click to expand...
Click to collapse
Maybe, but I'm pretty sure it won't hard brick the phone even if it's corrupted. Worst case scenario is that it would be a soft brick. Jig will probably work but I don't have access to it.
Something might have gone wrong on the way I've flashed it via heimdall. I've probably messed up and accidentally flashed the wrong pit(but I'm pretty sure I didn't) or probably the bootloader. Anyway I'll just save myself the trouble and just send the damn phone for repairs and suck up the 1 month wait. I just hope that they won't void my warranty. Not much I can do really.

chickentuna said:
Maybe, but I'm pretty sure it won't hard brick the phone even if it's corrupted. Worst case scenario is that it would be a soft brick. Jig will probably work but I don't have access to it.
Something might have gone wrong on the way I've flashed it via heimdall. I've probably messed up and accidentally flashed the wrong pit(but I'm pretty sure I didn't) or probably the bootloader. Anyway I'll just save myself the trouble and just send the damn phone for repairs and suck up the 1 month wait. I just hope that they won't void my warranty. Not much I can do really.
Click to expand...
Click to collapse
Take an usb cable and make a JIG... Less then 1 min to make it
Sent from my GT-I9505 using xda app-developers app

chickentuna said:
Maybe, but I'm pretty sure it won't hard brick the phone even if it's corrupted. Worst case scenario is that it would be a soft brick. Jig will probably work but I don't have access to it.
Something might have gone wrong on the way I've flashed it via heimdall. I've probably messed up and accidentally flashed the wrong pit(but I'm pretty sure I didn't) or probably the bootloader. Anyway I'll just save myself the trouble and just send the damn phone for repairs and suck up the 1 month wait. I just hope that they won't void my warranty. Not much I can do really.
Click to expand...
Click to collapse
---Repair dead boot I9505 via usb cable---
QHUSB Qualcomm driver download

samersh72 said:
---Repair dead boot I9505 via usb cable---
QHUSB Qualcomm driver download
Click to expand...
Click to collapse
This is just in case that his pc is geting signal from phone
Sent from my GT-I9505 using xda app-developers app

spinky360 said:
This is just in case that his pc is geting signal from phone
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
it will help also to get into download mode :good:

samersh72 said:
it will help also to get into download mode :good:
Click to expand...
Click to collapse
If his eMMC is not giving signal to start QHUSB ... Is useless
Sent from my GT-I9505 using xda app-developers app

samersh72 said:
---Repair dead boot I9505 via usb cable---
QHUSB Qualcomm driver download
Click to expand...
Click to collapse
Thanks but it didn't work. It gave me a little hope though no harm in trying. Really not sure if jig will work but one thing is for sure, I now have a $650 paper weight.
I just hope that the samsung guys won't be able to bring this back to life. I hope that they just replace the motherboard straight away because if they are able to resurrect the phone, I'm screwed. They will find out that I've modified it. Worse part is I will need to shoulder the repair costs which I wouldn't want if they void the warranty
Sent from my Galaxy Nexus using Tapatalk 4