Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

My S2 does not Boot at all may be HARDBRICKED :'(

OP akhil17kr

19th January 2014, 05:50 PM   |  #1  
akhil17kr's Avatar
OP Senior Member
Flag gurgaon
Thanks Meter: 26
 
338 posts
Join Date:Joined: Oct 2011
More
Okay... initially i was on Custom Rom Jellybam based on Jellybean 4.2.1 with Siyah Kernel V5 sync.

I want to upgrade to Kitkat 4.4

so i downloaded all the required files , made nandroid backup , reboot the phone and started transferring all ROM files into internal SD card Sdcard0
I am doing all this is Linux Mint..
It started transferring and got stuck 33.2%
so i removed the cable and try it again and this time again it stucked again
and my phone reboots automatically ..
Samsung logo main screen shows and loading starts but after completing loading bar .. it Freezes there and i cannot boot into recovery either..

SO on searching on goggle for solutions .. it states that i have to flash kernel again through ODIN again in order to access recovery to do Factory Reset..
SO i did the same flashed siyah kernel v4.1.5
it shows its successfully flashed BUT on reboot it shows Yellow triangle and freezes there and i still cannot access recovery and it also freezes on battery charge animation

So i again try to flash using ODIN this time again with siyah kernel 6.b5
and still same problem ,, so pull out battery and leave for 5 minutes and again boot phone in download mode and flash again using odin siyah kernel 6.0b5 and upon Reboot PHONE does not Boot.. I was literally Shocked and i try to pull out battery .. put back in and Try to charge but it shows no animation nor it is going in download mode.


Please HELP ..
Suggest me some ways because 1 year before I've replaced the motherboard due to same problem caused by factory reset in stock ICS rom when There was Hard Brick problem in Stock ICS roms..but it was in warranty so there was no problem but this time its out of warranty..

I didn't do anything wrong and still it got HARD BRICKED and still not have a clue what went wrong ??
19th January 2014, 06:05 PM   |  #2  
Senior Member
Thanks Meter: 3,210
 
7,087 posts
Join Date:Joined: Nov 2011
No booting at all = nothing anyone here can do = replace motherboard or get a new phone (JTAG also very unlikely to work).
19th January 2014, 06:16 PM   |  #3  
akhil17kr's Avatar
OP Senior Member
Flag gurgaon
Thanks Meter: 26
 
338 posts
Join Date:Joined: Oct 2011
More
Quote:
Originally Posted by MistahBungle

No booting at all = nothing anyone here can do = replace motherboard or get a new phone (JTAG also very unlikely to work).

i know. this.. its TOO scary to hear this thing..
If anything is possible ?? Anything ??
i will give every info you needed..
19th January 2014, 06:28 PM   |  #4  
Senior Member
Thanks Meter: 3,210
 
7,087 posts
Join Date:Joined: Nov 2011
And what exactly do you expect people here to suggest ? If the phone won't boot you can:-

*Try a jig (0.0000000001% chance of working, but try it if you like torturing yourself with false hope)
*Try a JTAG if the person who tries is prepared to do it on the basis of 'you only pay them if the JTAG is successful' (also 0.0000000001% chance of working, try this if you like torturing yourself with false hope even more)
*Replace the motherboard; 99.99% chance of successfully fixing the phone provided there's nothing else wrong hardware-wise
19th January 2014, 07:22 PM   |  #5  
akhil17kr's Avatar
OP Senior Member
Flag gurgaon
Thanks Meter: 26
 
338 posts
Join Date:Joined: Oct 2011
More
Quote:
Originally Posted by MistahBungle

And what exactly do you expect people here to suggest ? If the phone won't boot you can:-

*Try a jig (0.0000000001% chance of working, but try it if you like torturing yourself with false hope)
*Try a JTAG if the person who tries is prepared to do it on the basis of 'you only pay them if the JTAG is successful' (also 0.0000000001% chance of working, try this if you like torturing yourself with false hope even more)
*Replace the motherboard; 99.99% chance of successfully fixing the phone provided there's nothing else wrong hardware-wise

i'll go to samsung care tomorrow but i am still wondering what happened wrong as i did nothing wrong at all then still how it hardbricked ??
20th January 2014, 06:59 AM   |  #6  
AndDiSa's Avatar
Senior Member
Flag Heidelberg
Thanks Meter: 345
 
1,608 posts
Join Date:Joined: Dec 2009
... probably you only need to flash a correct running ROM. Did you try to flash an original Samsung firmware? Did you wipe data before starting the new ROM? Otherwise there is a big chance for a bootloop.

Sent from my Nexus 7 using xda app-developers app
20th January 2014, 07:50 AM   |  #7  
akhil17kr's Avatar
OP Senior Member
Flag gurgaon
Thanks Meter: 26
 
338 posts
Join Date:Joined: Oct 2011
More
Quote:
Originally Posted by AndDiSa

... probably you only need to flash a correct running ROM. Did you try to flash an original Samsung firmware? Did you wipe data before starting the new ROM? Otherwise there is a big chance for a bootloop.

Sent from my Nexus 7 using xda app-developers app

the guide suggest to flash kernel so that i can wipe/data factory reset .. i tried that with odin but phone does not boot and freezes at Samsung logo when loading bar finishes... so i thought to flash stock ics rom but before doing that after flashing kernel again it reboot and hard bricked... and does not boot after all even in download mode..
So this happens after i flashed kernel 3rd time and i still have no clue why did it happened..
and customer care asks it would costs at least Rs.8,000 or $133 to replace a Motherboard.. which is too costly...

can anyone suggest me any other things.. ay alternatives ??
20th January 2014, 08:33 AM   |  #8  
Senior Member
Thanks Meter: 3,210
 
7,087 posts
Join Date:Joined: Nov 2011
There are no other alternatives. Just because you refuse to accept reality doesn't make it anything less than reality.

And isn't it wonderful to see people still not reading threads & suggesting stuff that's impossible: 'probably you only need to flash a correct running ROM'. I mean, seriously ? The OP has already stated on multiple occasions that the phone will not boot. At all. How do you propose he flash 'a correct running rom' exactly ?
20th January 2014, 08:49 AM   |  #9  
akhil17kr's Avatar
OP Senior Member
Flag gurgaon
Thanks Meter: 26
 
338 posts
Join Date:Joined: Oct 2011
More
Quote:
Originally Posted by MistahBungle

There are no other alternatives. Just because you refuse to accept reality doesn't make it anything less than reality.

And isn't it wonderful to see people still not reading threads & suggesting stuff that's impossible: 'probably you only need to flash a correct running ROM'. I mean, seriously ? The OP has already stated on multiple occasions that the phone will not boot. At all. How do you propose he flash 'a correct running rom' exactly ?

hahah... i know .. people are sometimes too lazy to read ..

I just need to know.. what's wrong happened so that it will not happen next time..
20th January 2014, 09:14 AM   |  #10  
Senior Member
Thanks Meter: 3,210
 
7,087 posts
Join Date:Joined: Nov 2011
Honestly ? That's almost impossible to say. Best guesses based on what you've told us are you simply got a bad flash, which is a small possibility (maybe 1 in 10,000) with any given flash. Or, I've had a theory based on instances like this I've seen on here over the past two yrs which involves the connection between phone & PC being broken for a split second during the flash (possibly caused by less than reliable USB ports on the PC or something else intermittent on the PC side), but not long enough for the disconnection to 'register' on the PC-side like it normally does when an external device is disconnected (you get that exclamation sound & a notification that the device has been disconnected in your taskbar).

It doesn't sound like you did anything 'wrong', put it that way. So I'm not sure there's a whole lot you can do to avoid it in future. Unfortunately, that's the risk all of us take whenever we flash stuff to our phones; every single flash (even CWM ones) involves that small risk (due to the nature of the NAND; having a write abruptly interrupted partway through can 'scramble' it) and the only way you can mitigate that 100% is to not flash anything at all.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes