Database Develop

[Q] Help me: Verizon Samsung Galaxy Tab - full brick.

Hi all,
When re-flash the original ROM of my tab, follow link:
http://forum.xda-developers.com/showthread.php?t=967175
I don't read careful enough, I flash with Heimdall in Ubuntu, include boot.bin file (--primary-boot boot.bin). When success flash, my tab not run again. My battery is full (when began flash) but my tab not run, no live signal: no light, no signal to PC over cable.
What can I do? Should I take the my tab to producer for re-load bootloader?
Thank all.

If the flash went through fine then flashing a primary bootloader is fine as long as the bootloader is for your particular device. However my guess is that in this case the boot.bin you flashed was not designed for your particular tablet.
You can try a custom jig (search the forums), although I don't know if it will work with a busted primary bootloader. Otherwise you'll need to take the tablet back to Samsung and they'll fix it for you.

Benjamin Dobell said:
If the flash went through fine then flashing a primary bootloader is fine as long as the bootloader is for your particular device. However my guess is that in this case the boot.bin you flashed was not designed for your particular tablet.
You can try a custom jig (search the forums), although I don't know if it will work with a busted primary bootloader. Otherwise you'll need to take the tablet back to Samsung and they'll fix it for you.
Click to expand...
Click to collapse
Thank you.
Finish flash, Heimdall notify is success and auto re-boot my tab. But tab shutdown and .... die.
I was search by key "custom jig" and found some solutions, I will try tonight.
Thank you again.

Hello every body.
I have been tested all solution about baterry (included shock baterry), and my baterry is ok. But my tab still dead.

Hello everybody,
My tab can return to download mode now, repair by RIFF JTAG box.
Thank all.

I'm in the same situation. Battery ran out during Odin process. Now it won't acknowledge the Tab when plugged in. I've put it on charge but still nothing.

I am having the same problem, but my tab died in the middle of an odin, failed and now will not turn on. Can someone help me get it going again?

Hi,
Please PM me if you need help with this as I have the necessary tools and skill to revive hard bricked devices and can definitely JTAG any of the TAB variants and work with HTC and Galaxy Phones daily in terms of reviving hard bricks.

hard brick
Hi
after unsuccessful attempt to flash a ROM on my Samsung Galaxy Tab
there is no response from thedevice. It's completely dead. Can you fix
bootloader? Will I have to post the device? Im in UK
brgrds
Tim

Samsung Galaxy Tab (Sprint CDMA) full brick
Hi connexion2005
after unsuccessful attempt to flash a ROM on my Samsung Galaxy Tab
there is no response from thedevice. It's completely dead. Can you fix
bootloader? Will I have to post the device? Im in UK
brgrds
Tim

Hi Tim,
I've responded to your PM as well but I can fix your issue with my JTAG solution. Posting from the UK and getting back to you is no problem at all.
-Josh

Captivate unbrick guide with jtag?

Hello, i have a huge problem with a galaxy captivate. Neighbor brought me that phone to flash it because it was acting funny. I tried to use Heimdall to flash it but as soon as it was flashing the kernel it failed. To my surprise the phone got bricked in front of my eyes because of that. I know the Heimdall rom i was trying to flash does work because i flashed a Cappy yesterday with it. But i guess something went wrong with the laptop that bricked the phone. I have always flashed phones using Odin without a problem but, things happens sometimes i guess. Anyways, my question is if someone knows about a guide to unbrick via JTAG for that captivate. I own a RIFF box so if it helps i would appreciate.

I know I saw somewhere a small explanation on what is soldered. But in all honesty is easier to apply UBM.

UBm? Sorry for my ignorance but what is that?

By the way Puertorro, thats a nice flag lol....

UBM Jtag requires soldering 6 small points. UBM (if I understand correctly) is making a jumper between 2 spots. Can't say for sure, I've never attempted neither, my soldering skills are no where near close to do them lol.

Okay, found something in the forum. Will give it a try and ill let you guys know how it went at all.

Yeah thanks, found the thread. I work with a solder iron every single day and i have the equipment. Thanks buddy for your help... Appreciate that

Well, its late at night or early in the morning however it might be said lol.... But im happy to say that the Captivate is alive and running again. Thanks for all your help and those impresive tools that you guys are able to develop.

enelyam said:
Well, its late at night or early in the morning however it might be said lol.... But im happy to say that the Captivate is alive and running again. Thanks for all your help and those impresive tools that you guys are able to develop.
Click to expand...
Click to collapse
what problem did you have actually? I think I bricked my friend's (like you did your neighbour's lol) captivate. It was actually 2.2.. I used Odin to flash it back to 2.1 JF6..everything went well..and the Odin also showed 'pass'..but it won't reboot..it boots..shows the at&t logo..then boots again..and it repeats..can't go to either download mode or recovery mode..tried many combinations of buttons..but of no use to that phone..
what should i do?

wvufan21 said:
what problem did you have actually? I think I bricked my friend's (like you did your neighbour's lol) captivate. It was actually 2.2.. I used Odin to flash it back to 2.1 JF6..everything went well..and the Odin also showed 'pass'..but it won't reboot..it boots..shows the at&t logo..then boots again..and it repeats..can't go to either download mode or recovery mode..tried many combinations of buttons..but of no use to that phone..
what should i do?
Click to expand...
Click to collapse
Now you are soft bricked. That phone is probably a newer build number and dislikes JF6 1 click.
Sent from my ICS powered Captivate using Tapatalk

wvufan21 said:
what problem did you have actually? I think I bricked my friend's (like you did your neighbour's lol) captivate. It was actually 2.2.. I used Odin to flash it back to 2.1 JF6..everything went well..and the Odin also showed 'pass'..but it won't reboot..it boots..shows the at&t logo..then boots again..and it repeats..can't go to either download mode or recovery mode..tried many combinations of buttons..but of no use to that phone..
what should i do?
Click to expand...
Click to collapse
take out battery, put in usb from phone to PC, hold both volume buttons, put battery back in.
Download!

[Q] Easy guide to JTAG without using expensive box

So yeah, I bricked my Samsung Galaxy Ace with the wrong kernel through Clock Work Recovery, chose reboot option, screen turned black.
I have tried all the button combos, with inserting battery method and all of that, I even bought a USB Jig but to no avail. The furthest I've come to entering Download Mode(button combinations, to then flash with Odin) is that the computer is detecting the samsung galaxy ace as a modem(If I do not press the button combinations the computer detects nothing at all) and I cannot establish connection with the phone with Odin nor adb shell.
I have searched these forums a few hours a week the last two weeks and the only possible option seems to be JTAG unbrick. I have no money to get me a 100$ jtag-box just to resurrect this phone, so my question is this:
Is there any other way that Is cheap and not too advanced for a tech newbie like myself to unbrick the phone? I have no problem with soldering, but my question is, is there any other module(or would a simple jtag cable work?) to access the phones internal workings?
Or maybe there is another way to save this phone? Please post if you have experiance!
No, I have no warranty left on the phone, and no I do not want to leave it to some jtag service. That is not the problem.
Help/tricks greatly appreciated!

I had the exact same delema I kept plugging the phone into the c in download.mode and in the end my computer rexonized it ans was able to flash back to stock phone resets every now and then but other than that works fine I now use in rooted fully stock on.not.running the risk
Sent from my GT-S5830 using xda app-developers app

chooky536 said:
I had the exact same delema I kept plugging the phone into the c in download.mode and in the end my computer rexonized it ans was able to flash back to stock phone resets every now and then but other than that works fine I now use in rooted fully stock on.not.running the risk
Click to expand...
Click to collapse
Was the screen black when you flashed It through Odin aswell? Cause all Im getting from Odin is "setting up connection..." and there it stops. Did I miss something?

Wrong kernel as in?
Another device? A jig "might" help you...
*emphasise the 'might'*

Prawesome said:
Wrong kernel as in?
Another device? A jig "might" help you...
*emphasise the 'might'*
Click to expand...
Click to collapse
Yeah, I got ahold of a Jig tried on my friends Samsung S2, and It did not work. I don't remember what I tried to flash it with, It was through clockworkmod and I was going to flash with rafaels kernel but must have got ahold of the wrong one in his SkyDrive map. Anyayws, I applied the .zip and chose reboot and all went permanently black.
Anyone have experiance in UART-Jigs and whatnot?

P7320 Any Hope ?

We have a AT&T LTE 8.9 which I now deduce is a P7320 model. A year back when I got the 8.9, I rooted it, CWMed and installed a a AOKP ROM and it has been running great since. However, last week I swapped it for another device with my brother who decided I should put it back to the stock ROM so that he could ebay it.
Well with all the timeliness and hectic mode of the festive season, I failed to research thoroughly and flashed it a stock P7300/P7310 ROM. Which rendered it completely dead. It would not respond to anything, power/vol+, power/vol-, power/both vols, usb to pc, usb to wall with no charging icon e.g. Odin doesn't even see it. The only sign of life if that, is that it shows up as an error with QHUSUB_DLOAD in device manager.
Right now, I have the power button taped down to see if I can get anywhere draining the battery. You would think that Odin should at least see it? Is this the end of my tab?

bdbx18 said:
We have a AT&T LTE 8.9 which I now deduce is a P7320 model. A year back when I got the 8.9, I rooted it, CWMed and installed a a AOKP ROM and it has been running great since. However, last week I swapped it for another device with my brother who decided I should put it back to the stock ROM so that he could ebay it.
Well with all the timeliness and hectic mode of the festive season, I failed to research thoroughly and flashed it a stock P7300/P7310 ROM. Which rendered it completely dead. It would not respond to anything, power/vol+, power/vol-, power/both vols, usb to pc, usb to wall with no charging icon e.g. Odin doesn't even see it. The only sign of life if that, is that it shows up as an error with QHUSUB_DLOAD in device manager.
Right now, I have the power button taped down to see if I can get anywhere draining the battery. You would think that Odin should at least see it? Is this the end of my tab?
Click to expand...
Click to collapse
First of all, is your tab booting to AOSP now ??
if not can you see the [Samsung Galaxy Tab Logo], and after what did that happened (is it after you flashed a P7300 Stock ROM??)??
have you ever flashed stock ROM through odin before??
can you at least enter the recovery (CWM)??? cuz that would make things easier
we should know these things before we can help

omarainea said:
First of all, is your tab booting to AOSP now ??
if not can you see the [Samsung Galaxy Tab Logo], and after what did that happened (is it after you flashed a P7300 Stock ROM??)??
have you ever flashed stock ROM through odin before??
can you at least enter the recovery (CWM)??? cuz that would make things easier
we should know these things before we can help
Click to expand...
Click to collapse
The tab is non-responsive to *anything*. It won't boot, tethered or not, after the incorrect stock rom flash. I cannot get into recovery and odin does not see it. I have had a blank screen since.
Yes, I am somewhat familiar with odin/fastload/adb and various other tools for my android phones. Prior to this deadly flash, I had used odin to install cwm and a ROM on it. However, at this point, odin cannot see the tab either.

bdbx18 said:
The tab is non-responsive to *anything*. It won't boot, tethered or not, after the incorrect stock rom flash. I cannot get into recovery and odin does not see it. I have had a blank screen since.
Yes, I am somewhat familiar with odin/fastload/adb and various other tools for my android phones. Prior to this deadly flash, I had used odin to install cwm and a ROM on it. However, at this point, odin cannot see the tab either.
Click to expand...
Click to collapse
I assume that the problem is caused from the bootloader incompatibility
so you're saying that you can't enter the download mode or CWM
and your computer can't recognize your tab through adb connection ether
if this is exactly the case, then I don't think anyone can help you
maybe you should try to take your tab to any close samsung branch
Good luck

omarainea said:
I assume that the problem is caused from the bootloader incompatibility
so you're saying that you can't enter the download mode or CWM
and your computer can't recognize your tab through adb connection ether
if this is exactly the case, then I don't think anyone can help you
maybe you should try to take your tab to any close samsung branch
Good luck
Click to expand...
Click to collapse
You can get JTAG for about $40 so not that bad:
http://www.youtube.com/watch?v=BgL5vWRwh5k#t=22
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-tab-8-9-jtag-brick-repair/

[Q] Kernel mess up or what?

Hi peep's!
Hope someone can help me. I've been installing lots of roms and found one i liked but then i got too big for my boots (i think). I decided to try the Miui v4 rom yesterday and it was ok apart from swap support so i thought i'd be clever and install the Kernel from "Super Stock". After searching i found it was called "Thunderkernel 2.2". So i installed it via cwm and it booted to a black screen.
I've now tried everything with odin. It detects the phone if i take battery out, hold "vol up + down, home and power and put battery in but it sticks at setup connection. I can even unplug the phone and plug back in and it recognises it after doing the battery trick but still sticks at setup connection. I've tried reinstalling drivers, tried all the odins and shut down everything that may interfere with com's but to no avail. I thought a wrong kernel would at most stop the rom from booting, i never dreamed it would hard brick my phone.
So is this the end of my ace? is it worth me buying a usb jig?

This is pretty much what happened to me last year. I would advise the users to stay away from miui ROM as they may cause problem with some phone. Your device is bricked . jig may fix it but it depends on your luck

Falcon G said:
This is pretty much what happened to me last year. I would advise the users to stay away from miui ROM as they may cause problem with some phone. Your device is bricked . jig may fix it but it depends on your luck
Click to expand...
Click to collapse
I pretty much thought that'd be the case, i suppose i may as well try the jig as they're only cheap. Wish i'd just stuck with super stock. I was actually enjoying the ace for the first time it wasn't just a phone to me, at stock it was very limited. Oh well . Picked up an xperia m now but would be nice to get the ace working for my 3 sim. I'll post if it works or not, incase anyone else runs into the same problem. Thanks for the reply!

Way333 said:
I pretty much thought that'd be the case, i suppose i may as well try the jig as they're only cheap. Wish i'd just stuck with super stock. I was actually enjoying the ace for the first time it wasn't just a phone to me, at stock it was very limited. Oh well . Picked up an xperia m now but would be nice to get the ace working for my 3 sim. I'll post if it works or not, incase anyone else runs into the same problem. Thanks for the reply!
Click to expand...
Click to collapse
Hmm yeah I felt the same way. It really sucks that I installed a bad rom.
All the best though. And yeah do post your results here [emoji6]

Way333 said:
Hi peep's!
Hope someone can help me. I've been installing lots of roms and found one i liked but then i got too big for my boots (i think). I decided to try the Miui v4 rom yesterday and it was ok apart from swap support so i thought i'd be clever and install the Kernel from "Super Stock". After searching i found it was called "Thunderkernel 2.2". So i installed it via cwm and it booted to a black screen.
I've now tried everything with odin. It detects the phone if i take battery out, hold "vol up + down, home and power and put battery in but it sticks at setup connection. I can even unplug the phone and plug back in and it recognises it after doing the battery trick but still sticks at setup connection. I've tried reinstalling drivers, tried all the odins and shut down everything that may interfere with com's but to no avail. I thought a wrong kernel would at most stop the rom from booting, i never dreamed it would hard brick my phone.
So is this the end of my ace? is it worth me buying a usb jig?
Click to expand...
Click to collapse
Where did you find the Thunderkernel 2.2?...
@Falcon G @Way333 AFAIK there is NOT Thundebolt kernel for GT-S5830 but rather GT-S5830i
That means that you flashed an INCOMPATIBLE KERNEL!!! if you flasehd the thunderboltkernel 2.2
Thunderboltkernel is only for GT-S5830i be carefull with it mates!

Viper The Ripper said:
Where did you find the Thunderkernel 2.2?...
@Falcon G @Way333 AFAIK there is NOT Thundebolt kernel for GT-S5830 but rather GT-S5830i
That means that you flashed an INCOMPATIBLE KERNEL!!! if you flasehd the thunderboltkernel 2.2
Thunderboltkernel is only for GT-S5830i be carefull with it mates!
Click to expand...
Click to collapse
Yeah i thought it strange! All things seemed to add up to it being the wrong kernel. Went wrong after kernel flash was fine b4. If the rom wasn't gonna work with a kernel for the device it wouldn't brick the phone would it, the rom just wouldn't boot, unless the kernel is the wrong one for the device. Thanks for clearing that up! I'm usually good with studying first and not making mistakes.Oh well live and learn.

Viper The Ripper said:
Where did you find the Thunderkernel 2.2?...
@Falcon G @Way333 AFAIK there is NOT Thundebolt kernel for GT-S5830 but rather GT-S5830i
That means that you flashed an INCOMPATIBLE KERNEL!!! if you flasehd the thunderboltkernel 2.2
Thunderboltkernel is only for GT-S5830i be carefull with it mates!
Click to expand...
Click to collapse
Hi I didn't flashed the thundrbolt kernel.I just flashed this Rom. http://forum.xda-developers.com/showthread.php?t=2280553&page=25
It gave me an error while flashing. I even wiped completely and then flashed another cm11 Rom. But when I rebooted it just became dead

@Falcon G @Viper The Ripper
Ok I received the jig and It never worked. I tried the standard way and I tried doing all sorts of things but to no avail.
A few days ago I found a guide to a procedure for the s5570 (below) which blames drivers for the "setup connection" error and I thought the same would be applicable to the ace. I know the procedure well now as I've done it so many times and all goes well until the point where the odin drivers are supposed to configure, they never do. The guy who wrote the guide no longer responds as he changed phones.
Several people reported success with their s5570's. I wondered if anyone here may be familiar with the procedure and able to help?
http://androidforums.com/threads/tutorial-unbrick-mini-s5570-bricked-with-black-screen.407866/

Way333 said:
@Falcon G @Viper The Ripper
Ok I received the jig and It never worked. I tried the standard way and I tried doing all sorts of things but to no avail.
A few days ago I found a guide to a procedure for the s5570 (below) which blames drivers for the "setup connection" error and I thought the same would be applicable to the ace. I know the procedure well now as I've done it so many times and all goes well until the point where the odin drivers are supposed to configure, they never do. The guy who wrote the guide no longer responds as he changed phones.
Several people reported success with their s5570's. I wondered if anyone here may be familiar with the procedure and able to help?
http://androidforums.com/threads/tutorial-unbrick-mini-s5570-bricked-with-black-screen.407866/
Click to expand...
Click to collapse
Hi I couldn't even get my phone to get recognized in the devices and printers menu. I don't really think it could be done with samsung drivers.
But hey did your PC recognized your device?

Way333 said:
@Falcon G @Viper The Ripper
Ok I received the jig and It never worked. I tried the standard way and I tried doing all sorts of things but to no avail.
A few days ago I found a guide to a procedure for the s5570 (below) which blames drivers for the "setup connection" error and I thought the same would be applicable to the ace. I know the procedure well now as I've done it so many times and all goes well until the point where the odin drivers are supposed to configure, they never do. The guy who wrote the guide no longer responds as he changed phones.
Several people reported success with their s5570's. I wondered if anyone here may be familiar with the procedure and able to help?
http://androidforums.com/threads/tutorial-unbrick-mini-s5570-bricked-with-black-screen.407866/
Click to expand...
Click to collapse
Ouh!! , I'm sorry mate

Falcon G said:
Hi I couldn't even get my phone to get recognized in the devices and printers menu. I don't really think it could be done with samsung drivers.
But hey did your PC recognized your device?
Click to expand...
Click to collapse
Sorry m8 been real busy. Yeah my pc recognizes it but i have to hold all the buttons down and slip in the battery. Comes up yellow in the coms box in odin and shows in the devices and printers menu without the caution sign. I can do that whole process but it's just the odin drivers part that doesn't happen for me. So still sits on setup connection It was a long shot but worth a try
I wish now i'd never strayed from here. I used google to find that kernel. If i'd have never done that i wouldn't be in this situation!