Database Users

brick boot loader to black screen: no simple solution, simple prevention

Hi
So last night when I flashed my new created ROM with CWM, it seems like I ruined my boot loader, and from that I can't find the way to recover
SYMPTOMS:
- black screen
- power button doesn't do anything
- no button combination boots to download mode
- no charghing indication when connected to charger or USB
- no detection in the computer when connected to the USB
Is this the real black screen of death?
How did I get there?
I flashed a ROM through CWM, when it finished I selected reboot from CWM, and since then, all I see is black screen, no indication whatsoever to powering up.
I didn't try a USB JIG yet, but I will at Thursday (meet with a friend that has one)
as far as I understand the only way to recover from this is using a RIFF Box JTAG which requires, taking apart the phone, and soldering small wires to the board, and then reload the boot loader
Where do we go from here?
If it happened to you Please write down:
how did it happened to you?
what did you do to try to recover?
did you mange to recover?
if you did, how did you?
Why is this post so important to everyone?
Because if it didn't happen to you yet it might happen in your next CWM flashing.
So its very important to find a solution or at least the way to prevent it.
- update 31/12/2010 -
Cause
corrupted boot loader , bad sbl.bin flashing
Prevention:
do not flash roms/addons/fixes with sbl.bin
if you must flash sbl.bin, do it while you are sure that your USB configuration is perfect, and do it as less as possible.
Solution (for those who already bricked to black)
you're not gonna like it
find riffbox jtag....

marcelo.waisman said:
Hi
So last night when I flashed my new created ROM with CWM, it seems like I ruined my boot loader, and from that I can't find the way to recover
SYMPTOMS:
- black screen
- power button doesn't do anything
- no button combination boots to download mode
- no charghing indication when connected to charger or USB
- no detection in the computer when connected to the USB
Is this the real black screen of death?
How did I get there?
I flashed a ROM through CWM, when it finished I selected reboot from CWM, and since then, all I see is black screen, no indication whatsoever to powering up.
I didn't try a USB JIG yet, but I will at Thursday (meet with a friend that has one)
as far as I understand the only way to recover from this is using a RIFF Box JTAG which requires, taking apart the phone, and soldering small wires to the board, and then reload the boot loader
Where do we go from here?
If it happened to you Please write down:
how did it happened to you?
what did you do to try to recover?
did you mange to recover?
if you did, how did you?
Why is this post so important to everyone?
Because if it didn't happen to you yet it might happen in your next CWM flashing.
So its very important to find a solution or at least the way to prevent it.
BTW I think its a developers post, because we need developers creative way of thinking to find a solution
Click to expand...
Click to collapse
Happened to me too. I was tinkering with the Armani source to hopefully find something of use for Axura, and I bricked it. Same things happened to me. I called att and got a new one.

marcelo.waisman said:
Hi
So last night when I flashed my new created ROM with CWM, it seems like I ruined my boot loader, and from that I can't find the way to recover
SYMPTOMS:
- black screen
- power button doesn't do anything
- no button combination boots to download mode
- no charghing indication when connected to charger or USB
- no detection in the computer when connected to the USB
Is this the real black screen of death?
How did I get there?
I flashed a ROM through CWM, when it finished I selected reboot from CWM, and since then, all I see is black screen, no indication whatsoever to powering up.
I didn't try a USB JIG yet, but I will at Thursday (meet with a friend that has one)
as far as I understand the only way to recover from this is using a RIFF Box JTAG which requires, taking apart the phone, and soldering small wires to the board, and then reload the boot loader
Where do we go from here?
If it happened to you Please write down:
how did it happened to you?
what did you do to try to recover?
did you mange to recover?
if you did, how did you?
Why is this post so important to everyone?
Because if it didn't happen to you yet it might happen in your next CWM flashing.
So its very important to find a solution or at least the way to prevent it.
BTW I think its a developers post, because we need developers creative way of thinking to find a solution
Click to expand...
Click to collapse
Did you try removing battery and putting it back and then opening ODIN, holding the volume up/down and inserting the usb to bring it on the download mode. I guess I might have experience almost similar issue with one of the rom. I almost freaked out. Phone wont show if its charging. It wont mount on the pc. But tried all the possible method available several times including adb shell command. And finally I did hear the magical sound from window when the usb is connected and finally it did work.
Also try the adb method if it doesn't go into download mode using volume button combo.
Sent from my SAMSUNG-SGH-I897 using XDA App

Did u remove sbl.bin
Sent from my SAMSUNG-SGH-I897 using XDA App

Happened to me the first time I ran the OTA update from ATT. Paused the update, and when I resumed it - the phone though I finished downloading the JH7 update and tried to apply it.
It failed to apply and when it went to restart, it never powered on. No download mode, recovery, USB power, Odin, nothing. It was completely dead.
I got it replaced at the AT&T store.

If sbl.bin was removed or corrupted you should call the warranty center. Tell them ota update bricked your phone. Lol good luck
sent from my cappy running di11igaf's rom v2.5 at 1280mhz!!

I think it is just bad luck. I was once being careless and had the battery fall out of my phone while flashing, it interrupted the flash and I was still able to get in download mode to Odin it. Needless to say, I'll never flash again without the back cover on

bulletproof1013 said:
Did u remove sbl.bin
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yes i'ts probably a bad sbl.bin, but I didn't remove it I flashed a new one, most of the rom's do the same

yeah sounds like it...sry for your luck.but seems like its toast then. keep us posted

But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.

silverslotcar said:
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
Click to expand...
Click to collapse
There is a a way. Whenever you need to flash to stock you must use following stock. http://forum.xda-developers.com/showthread.php?t=818439
This is same as normal stock posted by DG except that it includes sbl.bin that we (1008) need. I use it everytime and 3 button combos for Download, Recovery work great.

silverslotcar said:
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
Click to expand...
Click to collapse
it seems like this is not my case
I'm still looking for other people who had my case, and recovered (even with the JTAG riff box) or at least find someone who know's what we shouldn't do, so we don't break our phones.
so whats batch 1008?

This happened to me last night. I was trying to flash the Darky port via CWM and during the flash it became unresponsive. I had to pull the battery. This caused 2 different things. Sometimes it would be a never ending loop of boot screens and then others it would just go into recovery where it wouldn't let me do anything.
From here luckily I was able to access download mode by using the "adb reboot download" command. So I then got into dl mode and tried to flash stock (not the 3 button fixed one) and it froze on FACTORYFS (or whatever it is). I had no choice but to pull the battery. Now it won't boot at all. So my assumption is it wiped the bootloader. I'm not 100% sure but I feel that the reason it stopped where it did was because I didn't run odin as admin on my Win7 pc. I read in another thread that someone had the same problem when they didn't do that either.
If you are in a pitch black room and you press power you can see your screen illuminate, it's just very dim.
I have batch 1008 if it makes any difference to anyone.
Either way I'm heading to the device support center in a half hour or so to try to get a replacement. I originally was going to make or order a jig but people are saying it only works if the bootloader is intact. I originally had hopes because one person claimed that they recovered a completely dead phone with it, but upon further reading all others could not. It seems like his phone may not have been completely bricked.
Update:
Just got back from the at&t device support center. They gave me a new phone without any hassle. They asked what was wrong with my phone and I told them that I was trying to update it and now it won't turn on. The guy tried a few combinations of button presses and tried hooking it up to a jig-like device. Nothing worked so he just gave me a refurbished phones. No questions asked. As I was walking out he said a few people have had the same issue so it's not a big deal.
Either way I thought this would help to realize that there is likely no way to get the phone to boot unless you have a jtag handy.

I don't feel safe to flash rom via CWM.
If you really want to do that, delete the bootloader inside the .zip

So i think i killed mine too
so i get black screen, two button combo gives me SEC S5PC110 Test B/d
I opened odin but nothing Is this toast?

I had this exact problem over thanksgiving weekend. My phone was was was hard bricked I was getting the "phone + computer" it took some effort to get it into download but I got it there and when I was recovering with odin the connection got lost the screen went blue and then nothing. It was dead totally unresponsive no charging or boot screen nothing but once I got a black screen with redlines. After a lot of attempts to revive it I gave up called ATT warranty for a replacement. Luckily I opted for the slow mail service and kept reading. Yesterday I saw the above post and now I can say "yes even now your phone is not bricked even though it does NOTHING"
step 1) first thing I did was charge the battery with my replacement phone as the bricked phone was no longer able to charge the battery
step 2) open odin1 click and hooked up the usb to the phone and computer no battery
step 3) inserted the battery holding only volume up+down
step 4) "BOOM" download mode and a happy dance
I posted this in the"read before flashing" thread there are other people who have recovered from this and now I think that the extra trick to this is getting a 100% battery you need this to flash, and state the phone is in now wont charge a battery.
hope this sound encouraging

silverslotcar said:
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
Click to expand...
Click to collapse
It's odd because I keep seeing people saying things like this. I, too, have a 1008 Captivate. My button combos have worked from day one and Odin one click has never messed that up. Maybe I'm just lucky?
Sent from my SAMSUNG-SGH-I897 using XDA App

RKight said:
It's odd because I keep seeing people saying things like this. I, too, have a 1008 Captivate. My button combos have worked from day one and Odin one click has never messed that up. Maybe I'm just lucky?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I believe there's a "fixed" 1008 batch. Not all 1008s are going to have the problem.

norcal einstein said:
I believe there's a "fixed" 1008 batch. Not all 1008s are going to have the problem.
Click to expand...
Click to collapse
Yeah it's either that or just a misconception spread by the community. Both my old captivate and replacement were 1008. I have been able to get into recovery via the power+volume combination. I was also able to get into dl mode using the vol+insert usb combination.
It's possible I just got lucky on both but who knows.

I, and many others have a 1008 that don't go into download or recovery via the button combos without fixing sbl.bin.
Sent from my SAMSUNG-SGH-I897 using XDA App

Bricked tab after honeycomb rom instalation

Hi, i got a problem with my 10:1 tab. Today i tried to install honeycomb rom using clockworkmod recovery and after the installation and rooting my tab there was a question should flash boot be fixed because the new one will replace other without going back so new flash and root from honeycomb could take it place and i said no to fixing it, second after my tab went off black and it not reacting to anything including trying to power on and get into recovery mode and i tried to push all the buttons and nothing works. Odin doesnt recognize the tab and if i plug it to charger or pc there is no response. The only thing i realized is i heard a plug in usb sound when i connect tab to pc and try to pull the power on button for like 5 seconds i hear plug in and second later plug out usb sound. What can i do to make it works again? I cannot give it to guaranty and all i can do is by myself

Send it to Samsung for a repair.

i cant, i have no guarantee all i can do is by myself, what can i do?

Did you try to hold power button a little longer ? Like 10 or 30sec. This works for some devices
Sent from my GT-P3110 using xda premium

Pull back cover off (use google to figure out how to do so), unplug battery for a few seconds. Plug battery back in. Press and hold power + vol down to try to get into ODIN.

There is no honeycomb rom for these tabs. What did you try to install? Link me.

Holding power button gives nothing, i tried ever combination for a couple minutes and not working. I tried to remove battery yesterday but it was connected via cables and there was no way to remove it without cutting out cables as far as i seen, if anyone can know how i can remove battery then let mw know because i can't find anything ever the internet. I downloaded HoneyVillain_1.2 from here http://forum.xda-developers.com/showthread.php?t=1138115. I tried to plug tab to charger today but after 10 hours it didn't worked at all, still got black screen with no reaction to buttons ;/

Hello
bad news - I killed my P5100 2 months ago and I can't repair it. I have same problem - I can hear plug on / plug off sound in Windows. But i have installed drivers and found that this is OMAP4430 device was connected/disconnected each time. And I can't do anything with my Tab.
I have took my Tab to official Samsung service and I've received answer that it is not repairable - only full replacement of internal board possible, and it costs 300$.
And I have tried to unofficial services and they tells me what my problem. Bootloader was corrupted and device can't start. So it is impossible to repair bootloader because it is protected in Galaxy Tab 2 and they proposed me to replace internal flash memory chip.
So I have dead Tab and wait for ability to programmatically repair my Tab
You can see my thread here http://forum.xda-developers.com/showthread.php?t=1908949, maybe it will be helpful for you

FrostX26 said:
Holding power button gives nothing, i tried ever combination for a couple minutes and not working. I tried to remove battery yesterday but it was connected via cables and there was no way to remove it without cutting out cables as far as i seen, if anyone can know how i can remove battery then let mw know because i can't find anything ever the internet. I downloaded HoneyVillain_1.2 from here http://forum.xda-developers.com/showthread.php?t=1138115. I tried to plug tab to charger today but after 10 hours it didn't worked at all, still got black screen with no reaction to buttons ;/
Click to expand...
Click to collapse
I honestly believe that the Rom you downloaded is for the acer ionica!
See xda has created separate forums for each phone because you can't use one phones rom for another! Yet you flashed that!
There s nothing you can do other than sending your phone for repair!
Sent from my GT-P3100 using Tapatalk 2

Ok so i installed wrong rom for my tab right? Is there something i can do to repair it by myself?

FrostX26 said:
Ok so i installed wrong rom for my tab right? Is there something i can do to repair it by myself?
Click to expand...
Click to collapse
No. Its a paper weight now and you could have prevented this by reading.

If you can't get it into Download Mode, then the only options are to send it to Samsung to fix it, or find some loose papers.

Hey guys, thanks for the answers so far I would like to know if every type of tablet brick can be unbricked? I mean if there is no brick that couldn't be unbricked by using cables and garage methods

FrostX26 said:
Hey guys, thanks for the answers so far I would like to know if every type of tablet brick can be unbricked? I mean if there is no brick that couldn't be unbricked by using cables and garage methods
Click to expand...
Click to collapse
http://www.jtagbox.com/jtag-news/ri...tab-2-101-unbrick-dead-boot-repair-supported/
I don't know how much support you'll get to follow this method but if nothing else will work it's worth a try.
As far as this tablet being unbrickable, that's only true if you don't intentionally flash something that was made for a completely different tablet...
Sent from my GT-P5110 using XDA Premium HD app

Well that's the point, I flashed with rom made for different tablet and it's dead now My question was if any brick could be repaired if i'll give it to someone with all the right tools to resurrect it, or there are certain bricks that can't be repaired no matter what tools and skills the person who attempt it have?

FrostX26 said:
Well that's the point, I flashed with rom made for different tablet and it's dead now My question was if any brick could be repaired if i'll give it to someone with all the right tools to resurrect it, or there are certain bricks that can't be repaired no matter what tools and skills the person who attempt it have?
Click to expand...
Click to collapse
Check my post again for the link as that's the only method that shows up on Google search for this tab.

does odin recognize your tablet?

Is it a tab 2. In your op it just said tab 10:1. Not tab 2. Just making sure as this is the tab 2
sent from MY BAD A$$ ET4G

I might be able to help u
Alright i had the problem recently and heres what i did to fix it If you can get into download mode ur all good from there. To get into download mode hold the power button and up on the volume rocker, if u get a message saying flashing roms is dangerous blah blah blah then press down on the volume rocker to enter download mode. Odin will recognize it if its in download mode, also what model is ur galaxy tab? Also if its a 10 inch model GT5113 i have the stock rom file for it so i could send it to u

Some helpful Info
Maybe you should have said yes? because after all you can't be too carefull , maybe there was something wrong with the rom. If the system asks you if you want to fix ALWAYS say YES. You should have said yes. Why did you say no ?! all right now to the fixing part. PLEASE NOTE I'M NOT AN EXPERT IN ROOTING BUT I'LL GIVE IT A GO. I think that if you can, then power it up and press the VOLUME UP key while holding the power button. From the menu choose recovery and factory reset your device. If it's possible reset rom to default. It should work if not then Post a reply saying not and I'll see what else can be found. Hold on tight for now!There is a Optional thing you can do if the above doesn't work: that is, if possible, you can un-root your tablet with an app from the market. If all of the above is impossible to do, and you cant even power your tab on, it's as useful as a brick, a black screen. Then I'm afraid it's a hard brick fopr you, boyo.
---------- Post added at 03:48 PM ---------- Previous post was at 03:41 PM ----------
FrostX26 said:
Hey guys, thanks for the answers so far I would like to know if every type of tablet brick can be unbricked? I mean if there is no brick that couldn't be unbricked by using cables and garage methods
Click to expand...
Click to collapse
Sorry for my previous post, didn't read the whole forum! Stupid me! ok now there are only two types of brick. Soft brick and hard brick. Soft brick can be fixed, Hard brick - Not quite. And as you said, you flashed a rom for a different tab, maybe thats a compatibility issue. If you want a new os, honeycomb to be exact. You can always upgrade, just search 'honeycomb upgrade'.

[Q] GT-I9500 soft bricked??

My friend has a GT-I9500 that gets stuck at the Samsung logo when booting and the status led is blue blinking slowly.... We have verified that it is not a fake through Sammy. The problem is that the phone will not go into download mode... We can get into recovery, but not download. Odin will not recognize the phone in either state (boot loop or recovery). I have read the threads about shorting the jumpers, but when we took the phone apart, it does not look like the pics (that sounded really noob...) and we were not able to locate the correct pins to jump... We ordered a jig off of ebay and it will be here soon, but does anybody have any other ideas??
Thanks for the input ahead of time!

mcookmpd said:
My friend has a GT-I9500 that gets stuck at the Samsung logo when booting and the status led is blue blinking slowly.... We have verified that it is not a fake through Sammy. The problem is that the phone will not go into download mode... We can get into recovery, but not download. Odin will not recognize the phone in either state (boot loop or recovery). I have read the threads about shorting the jumpers, but when we took the phone apart, it does not look like the pics (that sounded really noob...) and we were not able to locate the correct pins to jump... We ordered a jig off of ebay and it will be here soon, but does anybody have any other ideas??
Thanks for the input ahead of time!
Click to expand...
Click to collapse
Next time use this help thread: http://forum.xda-developers.com/forumdisplay.php?f=2164
and search bricked and u will end up with this: http://forum.xda-developers.com/showthread.php?t=2265477
I got my phone once it a bootloop, reflashed Rom and done.Dont know if u flashed a rom

Tunestwo said:
Next time use this help thread: http://forum.xda-developers.com/forumdisplay.php?f=2164
and search bricked and u will end up with this: http://forum.xda-developers.com/showthread.php?t=2265477
I got my phone once it a bootloop, reflashed Rom and done.Dont know if u flashed a rom
Click to expand...
Click to collapse
Yep....read that one before. The problem is I can't do step 1.....download mode. Down + home + pwr won't take the phone into download mode, it simply turns it on.

Try using terminal.
Type :
su
reboot download
I know in twrp recovery there is also an option to boot to download mode.
Best of luck
Sent from my SGH-I337M

Hardbricked my samsung galaxy s4

Hey,
I bought a second hand samsung galaxy s4 a few days ago and i didn't notice that the bootloader was locked, so i tried to root my phone and it succeeded but then i accidentally removed my batterij before rebooting and now my phone won't turn on anymore.
I already tried to press all buttons but it won't go on.
Can somebody help me please?

please specify "I already tried to press all buttons but it won't go on."

ChrisDiM said:
Hey,
I bought a second hand samsung galaxy s4 a few days ago and i didn't notice that the bootloader was locked, so i tried to root my phone and it succeeded but then i accidentally removed my batterij before rebooting and now my phone won't turn on anymore.
I already tried to press all buttons but it won't go on.
Can somebody help me please?
Click to expand...
Click to collapse
Hi,
Please be more descriptive. Does the splash screen appear? Can you go into Download Mode? What do you mean by "I already tried to press all buttons"? Also, when exactly did you remove your battery? There are many points there that can bring you a hardbrick, however, it can be nothing more than a softbrick as well...
Provide this further info and then I may try helping .
~Lord

XxLordxX said:
Hi,
Please be more descriptive. Does the splash screen appear? Can you go into Download Mode? What do you mean by "I already tried to press all buttons"? Also, when exactly did you remove your battery? There are many points there that can bring you a hardbrick, however, it can be nothing more than a softbrick as well...
Provide this further info and then I may try helping .
~Lord
Click to expand...
Click to collapse
Thanks for your reply, the splash screen doesn't appear and i can't get into any mode. It doesn't react in any way. Before this happend i installed the app; RegionLockAway and tried to unlock my boatloader. Thats when i accidentally removed my battery and i can't turn it on since then.

*BUMP*

well if you cant even enter download mode ive got bad news
Sent from my GT-I9505 using XDA Premium 4 mobile app

is there no way to bring this phone ''back to life'' ?

No, I believe it's perma bricked if you can't even get into download mode

Well when something like happened to my s2, i used a usb jig to get it back to life.
But that was in the case of a soft brick.
Still you can try on the GS4.
I AM NOT SURE IF THE JIG WOULD WORK.
But you can always try.
Thank me if it worked by any chance
Sent from my GT-I9500 using XDA Free mobile app

Hi,
It does look like a hard brick like you mentioned, so that means the only way to save it is a JTAG, when my S4 stayed in a similar way nothing worked, except for JTAG.
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505

No acess to the recovery mode on Samsung

So I have a Samsung Galaxy Gran Prime Duos G530BT and I was installing the TWRP recovery mode on it, the app asked for restart the phone to test the recovery mode, but when I restarted it the phone didn't boot anymore. He just vibrate and nothing appers on the screen.
I can't even get acess to the recovery mode to fix it. Can someone help me?
(I try to use the flash tool since he doesn't boot, but the stock room don't have any scatterd file...)

something similar happend to me..
rxxern said:
So I have a Samsung Gran Prime Duos GM-530BT and I was installing the TWRP recovery mode on it, the app asked for restart the phone to test the recovery mode, but when I restarted it the phone didn't boot anymore. He just vibrate and nothing appers on the screen.
I can't even get acess to the recovery mode to fix it. Can someone help me?
(I try to use the flash tool since he doesn't boot, but the stock room don't have any scatterd file...)
Click to expand...
Click to collapse
same as yours but mine has logo displayed and i cant turn on or put in recovery mode can you please message me if you find a way to fix it?

HyperVenoms said:
same as yours but mine has logo displayed and i cant turn on or put in recovery mode can you please message me if you find a way to fix it?
Click to expand...
Click to collapse
Yeah, sure!
This might be stupid, but did you try use Odin? Since your logo appears, I think you're in a better condicion then me, lol.

No but i found a solution
rxxern said:
Yeah, sure!
This might be stupid, but did you try use Odin? Since your logo appears, I think you're in a better condicion then me, lol.
Click to expand...
Click to collapse
ok so i couldnt put it into recovery mode or anything it was stuck so i took out the battery then held volume down power and home then pressed down to restart device and it came on successfully i hope this also works for you

rxxern said:
So I have a Samsung Gran Prime Duos GM-530BT and I was installing the TWRP recovery mode on it, the app asked for restart the phone to test the recovery mode, but when I restarted it the phone didn't boot anymore. He just vibrate and nothing appers on the screen.
I can't even get acess to the recovery mode to fix it. Can someone help me?
(I try to use the flash tool since he doesn't boot, but the stock room don't have any scatterd file...)
Click to expand...
Click to collapse
Try to download its stockrom boot it into download mode not recovery since recovery doesnt work any more i think its volume - if not + ,power button and Home button then dow load ODIN and flash the it so as to guarentee it to boot up again.
link for the devices stock rom
#https://docs.google.com/uc?id=0B7pEcClQW-2JenF1cW9jb05OVlk&export=download
thanks enjoy!!

No that lucky
HyperVenoms said:
ok so i couldnt put it into recovery mode or anything it was stuck so i took out the battery then held volume down power and home then pressed down to restart device and it came on successfully i hope this also works for you
Click to expand...
Click to collapse
So lucky! I can't do that to mine, when I put the battery out and try to do this, my phone has no response. ):

out of options
marwachacha said:
Try to download its stockrom boot it into download mode not recovery since recovery doesnt work any more i think its volume - if not + ,power button and Home button then dow load ODIN and flash the it so as to guarentee it to boot up again.
link for the devices stock rom
thanks enjoy!!
Click to expand...
Click to collapse
Thanks for the tip, but I really think I hard brick my phone, he just vibrate when the battery is on, when I try to turn him on just with the charger I get no response, my computer cannot ever reconize him. An since it's a national model there isn't much support for it on the internet (now I do regret getting him). I opened him to try force the reconization, but I don't find the force preloader mode test point and there is no way I can get a JTAG on Brazil.
TWRP Recovery Mode f*** me really hard this time.
Now if someone could help me finding the colo/kolo/whatever point on my phone I would really appreciated.

rxxern said:
Thanks for the tip, but I really think I hard brick my phone, he just vibrate when the battery is on, when I try to turn him on just with the charger I get no response, my computer cannot ever reconize him. An since it's a national model there isn't much support for it on the internet (now I do regret getting him). I opened him to try force the reconization, but I don't find the force preloader mode test point and there is no way I can get a JTAG on Brazil.
TWRP Recovery Mode f*** me really hard this time.
Now if someone could help me finding the colo/kolo/whatever point on my phone I would really appreciated.
Click to expand...
Click to collapse
Am not much sure if ti is hard bricked since you sayed that it vibrates lets look how much characteristics of a bricked device of which it posseses so as to conmfirm that it is hard bricked.
Soft Brick - Struck inBoot loop
2. Super Brick - Stuck atflashing Factoryfs.IMG in ODIN . Also called as EMMC Bug
3. Hard Brick -Dead / Costly Paper weights
4. Dead Brick - No chargingbattery sign also - Mostly = Hard Brick; But there is a window of possibilityby a USB JIG for SamsungPhones.
5. OTA Brick - Encountereddue to updating OTA on a rooted Stock ROM
6. CM12 Brick - when CM12encountered a /data write error. Worst is ODIN Flashing Fails
7. Pixel Salad: This is a problemof the graphics unit or the screen which fails to display correctly the imageand put instead random colored pixels on some areas of the screen or the wholescreen. It’s hard to even let the other members know what you are facing sinceyour screenshots would be just clean as it would have been. This also requiresa need for hardware checking if reflashing ROM doesn't work.
Soft brick means a temporary problem, which could be fixed. Soft brick usuallyoccurs after installing custom rom(s) or incorrect installation procedure whichinstallation/manipulation of files like permission settings, erasing systemfiles that is not compatible with each phone.
SOFT BRICKED
PHYSICAL CHARACTERISTICS TO MENTION FEW ARE
Phone struck on OEM logo.
Phone struck on a ROM logo "bootanimation"
The phone does not simply power up
or any other you can add up
HARD BRICKED
PHYSICAL CHARACTERISTICS TO MENTION FEW ARE
· No signs that can turn on directly
· The Charging won't work.
· Phone not detected when connected to a PC
· The LED's do not light up immediately
· No Sound / Vibrate
· Your phone completely off (Paper Weight)
Simply put it cannot be repaired using SEUS, FLASHTOOL, ODIN or even PC COMPANION.

marwachacha said:
Am not much sure if ti is hard bricked since you sayed that it vibrates lets look how much characteristics of a bricked device of which it posseses so as to conmfirm that it is hard bricked.
Soft Brick - Struck inBoot loop
2. Super Brick - Stuck atflashing Factoryfs.IMG in ODIN . Also called as EMMC Bug
3. Hard Brick -Dead / Costly Paper weights
4. Dead Brick - No chargingbattery sign also - Mostly = Hard Brick; But there is a window of possibilityby a USB JIG for SamsungPhones.
5. OTA Brick - Encountereddue to updating OTA on a rooted Stock ROM
6. CM12 Brick - when CM12encountered a /data write error. Worst is ODIN Flashing Fails
7. Pixel Salad: This is a problemof the graphics unit or the screen which fails to display correctly the imageand put instead random colored pixels on some areas of the screen or the wholescreen. It’s hard to even let the other members know what you are facing sinceyour screenshots would be just clean as it would have been. This also requiresa need for hardware checking if reflashing ROM doesn't work.
Soft brick means a temporary problem, which could be fixed. Soft brick usuallyoccurs after installing custom rom(s) or incorrect installation procedure whichinstallation/manipulation of files like permission settings, erasing systemfiles that is not compatible with each phone.
SOFT BRICKED
PHYSICAL CHARACTERISTICS TO MENTION FEW ARE
Phone struck on OEM logo.
Phone struck on a ROM logo "bootanimation"
The phone does not simply power up
or any other you can add up
HARD BRICKED
PHYSICAL CHARACTERISTICS TO MENTION FEW ARE
· No signs that can turn on directly
· The Charging won't work.
· Phone not detected when connected to a PC
· The LED's do not light up immediately
· No Sound / Vibrate
· Your phone completely off (Paper Weight)
Simply put it cannot be repaired using SEUS, FLASHTOOL, ODIN or even PC COMPANION.
Click to expand...
Click to collapse
Even if it's not hard bricked I had no idea on how bring him into life again, since the only signal of life he gives me is the vibration with the battery on.
It could make my computer detect him it would be much easier.

hmmm
rxxern said:
Even if it's not hard bricked I had no idea on how bring him into life again, since the only signal of life he gives me is the vibration with the battery on.
It could make my computer detect him it would be much easier.
Click to expand...
Click to collapse
this may sound dumb but maybe your screen is broke i highly doubt it because of what happened but if you can feel the vibrations but not see the screen then maybe its the screen. There will probably be a way to fix it but im unsure. Its funny how you call your phone him

HyperVenoms said:
this may sound dumb but maybe your screen is broke i highly doubt it because of what happened but if you can feel the vibrations but not see the screen then maybe its the screen. There will probably be a way to fix it but im unsure. Its funny how you call your phone him
Click to expand...
Click to collapse
I didn't mention this but the screen also blinks when is vibrating so... And if It was the screen the computer should reconized the phone, shouldn't?
Haha, english it's not my native language, so I get confuse sometimes, and i don't know calling it him sounds more right for me (?????).

rxxern said:
Even if it's not hard bricked I had no idea on how bring him into life again, since the only signal of life he gives me is the vibration with the battery on.
It could make my computer detect him it would be much easier.
Click to expand...
Click to collapse
rxxern said:
I didn't mention this but the screen also blinks when is vibrating so... And if It was the screen the computer should reconized the phone, shouldn't?
Haha, english it's not my native language, so I get confuse sometimes, and i don't know calling it him sounds more right for me (?????).
Click to expand...
Click to collapse
haha ok, i habe no idea what to do wiith your phone try searching other threads maybe ???

rxxern said:
I didn't mention this but the screen also blinks when is vibrating so... And if It was the screen the computer should reconized the phone, shouldn't?
Haha, english it's not my native language, so I get confuse sometimes, and i don't know calling it him sounds more right for me (?????).
Click to expand...
Click to collapse
also in advance try to change the usb cable which you are using to connect (him) with your computer as well as try different Pc's may Be yours might have some usb port drivers corrupted also try to install the ADB interface drivers in your pc so as you can enhance your Pc detect the devices even if they are powered off gues it will work still i have hope with your (him) buddy!!!

Nothing better than xda.

I am having the same problem with my G530BT. Managed to solve ?
rxxern said:
So I have a Samsung Galaxy Gran Prime Duos G530BT and I was installing the TWRP recovery mode on it, the app asked for restart the phone to test the recovery mode, but when I restarted it the phone didn't boot anymore. He just vibrate and nothing appers on the screen.
I can't even get acess to the recovery mode to fix it. Can someone help me?
(I try to use the flash tool since he doesn't boot, but the stock room don't have any scatterd file...)
Click to expand...
Click to collapse
I am having the same problem with my G530BT. Managed to solve ?

Raphaelfla said:
I am having the same problem with my G530BT. Managed to solve ?
Click to expand...
Click to collapse
Ow, one year latter I don't think this will help you anymore, but just in case someone has the same question: I didn't solve the problem, I took it to the Samsung assistence and discover that the motherboard was damaged, they would have to replace it.