Let's unbrick your phone - Guide (Soft Brick, Super Brick, Hard Brick, OTA Brick)

[arunm]

You can post all your communications here and if u want to catch me live use Gtalk.

Intrested to make ur mobile work again ...
Once u enter download mode ...
Please also let me know what made u bricked.

Did you flash an unsafe kernel ??

Prabhakar.R

As i said i was flashing a PIT file and it got stuck (usually PIT file flashing dosnt take more than 2 min but i did wait for 20 min while flashing that PIT)

So i had to intrupt it by removing the battery and when i did that i couldnt get my device enter in to download mode (Its not starting).

---------- Post added at 12:58 PM ---------- Previous post was at 12:54 PM ----------

Yes and I had succeeded once using some random method.
Why dont u try again step by step which I have posted above ...

I have a JIG which i ordered for my S2. when i tried it on my G note before i flashed this PIT. It did not reset the binary count to 0.

The same JIG has worked in reseting the binary count to 0 for my S2.


So if you have tried it did your binary count got to default value (0).

 

[prabhu1980]

And oh ya Yes! I have once succeeded connecting to odin with jig which was a dead note.
But i didnt note down the sequence.

OK s2 JIG = n7000 jig.


You have messed up with the bootloader.
You have 2 options
a) Jig
b) JTag.

Did u try this again ?

You referred to the method to remove yellow triangle.
I am referring a method with jig for forcing into odin.

 

[arunm]

And oh ya Yes! I have once succeeded connecting to odin with jig which was a dead note.
But i didnt note down the sequence.

You have messed up with the bootloader.
You have 2 options
a) Jig
b) JTag.

Did u try this again ?

You referred to the method to remove yellow triangle.
I am referring a method with jig for forcing into odin.

This means My device will have a blank screen but it will show up in the COM of PC-ODIN

Am i right ...

g talk

arunursluv

add me

 

[prabhu1980]

yes
but i dont remember the sequence how i forced into download mode.
I got lucky once.

Try the methods I have posted

 

[arunm]

And oh ya Yes! I have once succeeded connecting to odin with jig which was a dead note.
But i didnt note down the sequence.

OK s2 JIG = n7000 jig.


You have messed up with the bootloader.
You have 2 options
a) Jig
b) JTag.

Did u try this again ?

You referred to the method to remove yellow triangle.
I am referring a method with jig for forcing into odin.

JTag may mess up the mobile as its mandatory to open the device any short the battary pannel to the jTAG device (which is not available wth me).

All i have done is a software issue dont know y i cant fix it with a JIG.

 

[prabhu1980]

Hey In case if you fail connecting it to
odin, try reinstalling the Samsung USB drivers again.

You should get something like this, not exactly this.

 

[prabhu1980]

Did u try this again ?

 

[arunm]

Yes I have tried many times but its not working for me.

 

[shinzi]

hi~dear all
i got my note bricked,
cant go in download mode,i tried jig,hold 3button,jtag,and http://forum.xda-developers.com/showpost.php?p=28542939&postcount=56 or reinstalling the Samsung USB drivers

i dont know what i can do now... i am got a hard bricked?
sorry for my english~

 

[prabhu1980]

Try pressing vol button after fixing the jig.
There is only a narrow window of oppurtunity.
Still try.

Will post in detail later. Now on a long drive.

Sent from my GT-N7000 using XDA Premium HD app

 

[arunm]

hi~dear all
i got my note bricked,
cant go in download mode,i tried jig,hold 3button,jtag,and http://forum.xda-developers.com/showpost.php?p=28542939&postcount=56 or reinstalling the Samsung USB drivers

i dont know what i can do now... i am got a hard bricked?
sorry for my english~

what were you doing before it got bricked?

 

[shinzi]

what were you doing before it got bricked?

i had flash miui 2.7.6 and then i flash a kenerl（GL_NOTECORE_v1.3.tar）via pc odin, but my note stuck in miui logo,so i flash miui 2.7.6 again.
now i cant bootup and recovery or download mode

 

[prabhu1980]

IDEA 2:

a) Make sure you charge your dead phone (It may get charged even when it's dead, else manage one from your friend.)
b) Long press power button (15-20 seconds).
c) Remove battery for 5 seconds,
d) Plug in JIG,
e) Put battery back.
f) Wait for 40 seconds .................................................. ....... (Be Patient)
g) press power button for 5 seconds
h) Remove JIG,
m) Plug your USB and try connection to ODIN


Post details ....

 

[shinzi]

IDEA 2:

a) Make sure you charge your dead phone (It may get charged even when it's dead, else manage one from your friend.)
b) Long press power button (15-20 seconds).
c) Remove battery for 5 seconds,
d) Plug in JIG,
e) Put battery back.
f) Wait for 40 seconds .................................................. ....... (Be Patient)
g) press power button for 5 seconds
h) Remove JIG,
m) Plug your USB and try connection to ODIN


Post details ....

thank you ,but still can not go in download

 

[dusty_nz]

So got emmc brick.

Followed the instructions and moved the partitions on my phone. All good, Formatted and sweet.


Problem is I can flash kernel via odin but when I try to flash CWM rom I get errors.

ICS - just does not boot.

CM9 errors with assert failed on flash.

Using CWM 5.8.15. HAve gone back to CMW 5 and same issue.

Help.

DOH. First issue is I forgot to set the new partition names.
This is started with flashing the new 4.0.4 Rom.

 

[prabhu1980]

I need the following to help you better.

Current ROM :
Current Kernel :

 

[dusty_nz]

So got emmc brick.

Followed the instructions and moved the partitions on my phone. All good, Formatted and sweet.


Problem is I can flash kernel via odin but when I try to flash CWM rom I get errors.

ICS - just does not boot.

CM9 errors with assert failed on flash.

Using CWM 5.8.15. HAve gone back to CMW 5 and same issue.

Help.

DOH. First issue is I forgot to set the new partition names.
This is started with flashing the new 4.0.4 Rom.

Problem was solved. Forgot to set the partition names.

However the problem seems to be growing. re-partitioned. Performed a full read on the system drive, no errors. Flashed, 2nd reboot started getting some errors. Read test and more bad sectors.

The bad blocks seem to be growing. Is that possible? Will re-partition again and flash.

Trying to apply the latest 4.0.4 rom. German.

So understanding two things.
1: Don't try and flash ICS direct from ODIN if you have the Emmc bug?
2: Don't perform a factory reset from CWM if you currently have a ICS kernel flashed.

OK is flashing gingerberad from ODIN
Factory reset from CWM if GB kernel.

Thanks

 

[dusty_nz]

Issues continue.

Have performed the
dd if=/dev/block/mmcblk0p9 of=/dev/null read test on partitions 9,10,11. All good.

e2fsck -f -c –y /dev/block/mmcblk0p7 on partions 7 is good but 9 and 10 produce numerous errors, repeating the cmd same errors. Eg

Free inodes count wrong for group #4 (8180, counted=7798)
Fix? yes

Free inodes count wrong for group #5 (8190, counted=7495)
Fix? yes

Tried formatting in CWM (System and Data), Restarting and same errors!!

What am I missing. CWM 5.0.2.7

 

[dusty_nz]

Whole mess started with trying to flash via CWM the MidTEam 4.0.4 rom
Ok - Savings from EMMC bug. Starting at all turned to SH_T

Followed this thread for re-partitioning after confirming I/O errors reading partitions via ADB.

http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Flashed the
4pda_kernel.tar via Odin then rebooting into CWM. No errors.
Did a full read check on 7,9,10,11 and noted read errors on 9 and 10.
Removed 9,10,11 and repartitioned loosing 1/2 of my internal storage. Not a major.
Labeled and re-formated 9 & 10 in CWM. All ok.

rebooted (Pulled battery) and back into CWM. No errors and ADB all ok.
Wiped and cleared cache.
Flashed DarkyRom 3.4.1 via CWM. No errors.
Restarted and it just hangs with the yellow triangle. Accessing CWM and it complains of no cache drive.

re-flashed (nothing else) 4pda_kernel.tar and CWM seems to be fine again. Still won't boot thou.

Almost looks like an partition table error. Certain Kernels cannot read the partition table.

I also noticed that occasionally a partition check (DD read) would raise a i/o error but after a restart it would show ok. Also the System drive. First re-create raised a I/O error. Restarted the phone and re-created, All ok. No issues second time.
Faulty or not?

Help

 

[forest1971]

If you can post the current partition table it may help make things clearer. Cheers.