• XDA Forums have been migrated to XenForo. We are aware of several issues including missing threads, logins not working, and more. To discuss, use this thread.
  • If you are experiencing issues logging in, we migrated and software and made it more secure. We recommend trying to reset your password.

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

Is this Idea Working ?


  • Total voters
    0
  • Poll closed .

prabhu1980

New member
Dec 13, 2009
288
127
0
Indore
BRICKED USERS GUIDE.......

First you need to know that this guide is trying to help you..
I cannot take any responsibility for your brick getting harder ....

.....IGNORE ALL WHO SAID NOT TO WASTE THEIR TIME .....
....... The poll was for a different post related to emmc bug where i suggested a workaround for the emmc bug , which I edited several times....


There are three types of bricks for N7000
a) :eek: Soft Brick - Stuck at Samsung Logo [Added BootLoop here]
b) :eek: Super Brick - Stuck at flashing Factoryfs.IMG in ODIN . Also called as EMMC Bug....
c) :mad: Hard Brick - Sorry Unrecoverable by this guide. Try THIS
d) Dead Brick - No charging battery sign also - Mostly = Hard Brick ; But there is a window of possibility by a JIG.
e) OTA Brick - A rare kind of Soft Brick which people have encountered due to updating OTA on a rooted Stock ROM.
f) CM12 Brick - A Brick I and another XDA Mate encountered when CM12 encountered a /data write error. Worst is ODIN Flashing Fails .....

:eek: CM12 Brick :eek:
CM12 Brick

Error Details : Flashing JB Kernel in ODIN Fails ...
Received Response from LOKE FLashing Failed ....

a) Download the PIT file
b) Flash in Odin
c) After SUCESSFULLY Flashing Pit File
d) Flash ICS KERNEL (SPEEDMOD KERNEL) USING ODIN
e) Now go to Recovery and Flash your Favorite Philz Kernel

:eek: SOFT BRICKS :eek:

I will try to describe ways to get Soft Bricked so that you can compare.....
You have messed with the system file. Remember the Blue Screen of windows.

==> 1. Deleting any system file .odex
==> 2. Moving from GB or ICS to CM/AOSP/AOKP Roms without following instructions or vice versa
==> 3. Flashing incomplete ROMS (did not check MD5 - Google it How to check)
==> 4. Flashing an incompetent kernel (oh I didnt read instructions)
==> 5. Many other methods
==> 6. JB BootLoop


Now you have to return to normal state. But beware there is a emmc bug which is going to interfere our correction process. Oops ! It hurts. There is no safe way as on date for ICS except there are Safe Kernels Claimed.

Pray to your favorite god or luck or better pray even if you are an atheist.

RECOVERY STYLE 1 : [ODIN]
GINGERBREAD VERSION

1) Use ODIN

2) Uninstall Samsung KIES. It interferes with the ODIN flashing.
You should have the ADB/USB Drivers
Just in case you don't have them, here are the Samsung USB drivers

3) Download the AbyssKernel 4.2 for ODIN.

Incase it fails u can use 3.9 version too.

4) Wipe Data/Cache/Dalvik.

5) FLASH THE ROOTED KJ4 kernel From PC ODIN - Kernel Link
TRY FLASHING THE STOCK ROM in PDA Try the Oldest Stock ROM - KJ4 click me

Remember to Run ODIN in Admin mode (Right Click and Run even if you are an Admin)

6) Head to Dr Ketan Thread for Rooting...

ICS VERSION

1) Use ODIN

2) Uninstall Samsung KIES. It interferes with the ODIN flashing.
You should have the ADB/USB Drivers
Just in case you don't have them, here are the Samsung USB drivers

3) Download the AbyssKernel 4.2 for ODIN.

Incase it fails u can use 3.9 version too.

4) Wipe Data/Cache/Dalvik

5) FLASH ANY ics rooted rom in Abyss Recovery which has a safe kernel


Remember to Run ODIN in Admin mode (Right Click and Run even if you are an Admin)

RECOVERY STYLE 2 : [CWM]

ICS and GINGERBREAD USERS

a) Go to CWM
b) Flash Abyss Kernel 3.9 or 4.2 [Touch version] or Hydracore latest version.
c) Do data/ factory reset.
d) Flash with your favorite ICS / GB /AOSP/ AOKP/PA/CM9/CM10


[BOOTLOOP JB Leak / Official]

ODIN Version

a) Download Stock JB from Dr Ketans Thread
b) Install Tar file via ODIN in PDA
c) Reboot
d) Root as in Dr Ketans Guide
e) Install Custom ROM from CWM if you need

CWM Version

Understanding the issue now. So Prefer ODIN version now.


END :) SOFT BRICK :)


:eek: SUPER BRICKS :eek:

Hmm ... I understand your despair. My friend forest has written a wonderful guide to retrieve you out.
If you are confirmed that you are a Super Brick

Head to this thread ......

But .... Just before heading to Mr Forests Thread May be you are not a Super brick ...
There are few who had the same symptoms of a Super Brick but successfully recovered without the Forest1971 workaround.

RECOVERY STYLE 1 : START HERE

IMPORTANT NOTE : Remove your SD Card and SIM CARD Please
Run ODIN IN ADMIN Mode

a) Now you have to repartition your Note
b) Download the following (Importantly the .pit file)

PIT: Q1_20110914_16GB.pit (Only for users with 16GB Internal SDCard) 32 GB users Please Google ur file.
PDA: CODE_N7000xxxxx_CL627135_REV02_user_low_ship.tar.m d5
PHONE: MODEM_N7000xxxxx_REV_05_CL1067428.tar.md5
CSC: GT-N7000-MULTI-CSC-Oxxxxx.tar.md5


Thanks PrinceOMI & DuckBoot for the download links (PIT Files)
Stock ROM & Pit File Flashing Thread

c) Check these options: Re-Partition, Auto Reboot, and F. Reset Time.
d) Flash thru PC Odin (All the files, particularly the PIT file)

SUCCESS .... GOOD FOR YOU .... Only 2% reported success using this style (I ask you not to Thank me but to write here in this thread if you are successful. Many users do not care..)

RECOVERY STYLE 2 : START HERE

Working on it .... Not able to proceed. Ideas dropped.

END :angel: SUPER BRICK :angel:

:cyclops: OTA BRICKS :cyclops:

I will try to describe ways to get OTA Bricked (very rare)

a) Installed the OTA for ICS ROM Indian Version LPA on a rooted ROM.

Some thing has messed up with your .odex files and you get force closes or Stuck at Samsung LOGO

1) ODIN Method
a) go to Download Mode (Power Button + Vol down + Home)

b) Flash the ICS ROM posted in Dr.Ketan Thread in the PDA

Remember that options are ticked according to this image.
Donot tick repartition.
You can root it by Heading to Dr Ketans thread.

2) CWM Method (Custom Firmware - Closest to LPA ROM)
a) go to Download Mode (Power Button + Vol up + Home)

b) Flash the ROM close to LPA without any Reset or Wiping.
This will endup with a custom ROM Clea Note (LPA Rooted)

END :highfive: SUPER BRICK :highfive:
 
Last edited:

Zamboney

New member
Feb 20, 2012
475
88
0
Dude, that's really sad. You should've gotten your girl her presents before repairing. It's not her fault you flashed custom ROMs.

Sent from my superior GT-N7000 using Tapatalk
 
  • Like
Reactions: morassteam

prabhu1980

New member
Dec 13, 2009
288
127
0
Indore
I got my Note connected to PC Odin (when it was superbricked) once which I could not replicate again.

Since I got it connected anybody else would by the above procedure.

I always believe that Software Problems can be solved by tweaking Softwares; not by replacing the motherboard; I did it once but I missed How I did it.
 
Last edited:
  • Like
Reactions: morassteam

anilisanil

New member
Mar 1, 2012
517
95
0
Pune
I like optimists, but I hate to see them when they fail :(

superbrick is when the portion to which ROM gets written is fried due to the bug.

AND, JTAG JIG is different from micro USB JIG.

While I appreciate your gesture to trying help others, wrong information is unwelcome. Also, even if you are able to connect to PC odin after everything, this method does not tell how to make it flash the ROM.

Thanks anyway.

From a bricked user who tried everything to resurrect the note but failed.
 
  • Like
Reactions: howard bamber

prabhu1980

New member
Dec 13, 2009
288
127
0
Indore
Corrected My Post about JTAG (I am not a perfectionist and please allow unintented mistakes)
But I got connected once to PC Odin.
Were you able to connect it ??
Did you try the method posted above while using the JIG ?

You are right !! This method will be OK till PC Odin.
But once you are able to connect; lets try Step 2 and Step 3 (added after some research)

Lets get it connected first.

Getting Fried
- Does Flashing Fry your ROM ? Comeon Man Its a Software BUG and it should be possible to recover.
How many times we have fried Windows and Linux and played with Boot Partitions for Multiple OS.
Something should be possible. Please throw some light and help the Superbrick users. Donot demotivate.
Find Ways to Come out of this bugging bug.
I am not a software developer but ur comments will drive me to become one Thanks !!!

While I appreciate your gesture to trying help others, wrong information is unwelcome.
Boss !! What I am doing here is just a try before replacing your motherboard ! Hope it will harm no one.
 
Last edited:

prabhu1980

New member
Dec 13, 2009
288
127
0
Indore
I wrote this because I got connected to PC Odin after the Black Screen.
Did you got connected and still unable to recover ??
We should somehow be able to connect it to PC.
Any alternate suggestions Chasmodo .

We have to find a way out of this Brick Issue.
Please help !! (I dont think I can brick to find a way out
If required please make a bounty for the developers to revive from this situation.

My Feeling is "Whatëver bad happened to me should never occur to anyone else"
 
Last edited:

anilisanil

New member
Mar 1, 2012
517
95
0
Pune
I wrote this because I got connected to PC Odin after the Black Screen.
I understand your intenstions, but eMMC is fried (i/o bug which might allow excess voltage while wiping or corrupting NAND) no one knows what the reason is yet, but all we know is the partition where the ROM gets written to get corrupted and hence you cannot flash any ROM onto it, no matter what you do!
 

prabhu1980

New member
Dec 13, 2009
288
127
0
Indore
eMMC Bug which will allow excess voltage damaging the ROM . Thats Frying ....
Thats Poor Hardware right ??

But we dont know what's the BUG. Coz had we known we could have corrected it.

Were you able to connect to PC Odin when you had a blackscreen ??
 

chasmodo

New member
Dec 28, 2011
12,406
41,141
0
Novi Sad
I wrote this because I got connected to PC Odin after the Black Screen.
Did you got connected and still unable to recover ??
We should somehow be able to connect it to PC.
Any alternate suggestions Chasmodo .

We have to find a way out of this Brick Issue.
Please help !! (I dont think I can brick to find a way out
If required please make a bounty for the developers to revive from this situation.

My Feeling is "Whatëver bad happened to me should never occur to anyone else"
You found your way out of a situation caused by the Repack Rom, not by the LPY one.

LPY bricks seem to do physical damage to your EMMC chip, so connecting your
Note to the PC will do no good. PC Odin flash will fail because of the damaged EMMC blocks.

There's a lot of bricked users who can get into Download and/or Recovery mode,
but ALL their flashes still fail. See this: http://forum.xda-developers.com/showthread.php?t=1653290

I fear the Note community will be remembering this LPY debacle for a long, long time. There's no known cure for now.:(
 
Last edited:
  • Like
Reactions: Crash

prabhu1980

New member
Dec 13, 2009
288
127
0
Indore
LPY bricks seem to do physical damage to your EMMC chip
It seems or Is it confirmed damage ??

Please dont think I am pulling too hard. May be if Emmc is getting damaged why not replace Emmc chip instead of the whole motherboard. I got my Motherboard replaced..

If Partitions are getting fried then Why cant we re partition it ?
 

prabhu1980

New member
Dec 13, 2009
288
127
0
Indore
I understand your intenstions, but eMMC is fried (i/o bug which might allow excess voltage while wiping or corrupting NAND) no one knows what the reason is yet, but all we know is the partition where the ROM gets written to get corrupted and hence you cannot flash any ROM onto it, no matter what you do!
Did you re-partition your ROM ??

If you had done it. Can we have a re partition (modified PIT) for LPY to overcome the area corrupted ??
There are ways to repartition . Included Step 3 in my post.

You may be right !! But I am just looking for a solution like you ....
But since you are using words like MIGHT and MAY I m still guessing solutions may exist.
Please read this Thread http://forum.xda-developers.com/showthread.php?p=26167317#post26167317
 
Last edited:

anilisanil

New member
Mar 1, 2012
517
95
0
Pune
Looks like there is one success case jpturibio

Please look into this. Try Try until u succeed.
I really have no idea. Samsung service guys even tried JTAG my device, but the whole thing conked off while JTAG and they replaced my device under warranty.

So if a JTAG could not restore my phone, how would I know if flashing repetitively would help. Anyway, I am glad it worked for someone, and I get a feeling that we would soon be finding some solution to this plague!
 

prabhu1980

New member
Dec 13, 2009
288
127
0
Indore
Please look into this !! Factory.RFS users.

Dont get demotivated. Many have gone past this in several forums (Google it and See)
Many have success cases.

We have to evolve a method , so please post to help me solve this issue.