FORUMS
Remove All Ads from XDA

 View Poll Results: Is this Idea Working ?

Working
 
39 Vote(s)
41.94%
Need Improvements
 
30 Vote(s)
32.26%
Need Alternate Idead
 
13 Vote(s)
13.98%
Don't Waste Our Time
 
23 Vote(s)
24.73%

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

283 posts
Thanks Meter: 118
 
Post Reply Email Thread
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) Soft Brick - Stuck at Samsung Logo [Added BootLoop here]
b) Super Brick - Stuck at flashing Factoryfs.IMG in ODIN . Also called as EMMC Bug....
c) 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 .....

CM12 Brick
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

SOFT BRICKS

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


SUPER BRICKS

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 SUPER BRICK

OTA BRICKS

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 SUPER BRICK
The Following 37 Users Say Thank You to prabhu1980 For This Useful Post: [ View ] Gift prabhu1980 Ad-Free
 
 
16th May 2012, 07:28 AM |#2  
Senior Member
Thanks Meter: 91
 
More
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
The Following User Says Thank You to Zamboney For This Useful Post: [ View ] Gift Zamboney Ad-Free
16th May 2012, 07:37 AM |#3  
prabhu1980's Avatar
OP Senior Member
Flag Indore
Thanks Meter: 118
 
More
Sure I will gift her my Samsung Galaxy Tab ( which I got it repaired due to water entry; She poured water on it )
She Loves Playing with my Tab.
The Following User Says Thank You to prabhu1980 For This Useful Post: [ View ] Gift prabhu1980 Ad-Free
16th May 2012, 07:42 AM |#4  
musashiro's Avatar
Senior Member
Flag Tarlac
Thanks Meter: 89
 
More
sorry, i don't mean to criticize your method but...

if your eMMC is already dead or corrupted, how is this method gonna revive the note??
The Following User Says Thank You to musashiro For This Useful Post: [ View ] Gift musashiro Ad-Free
16th May 2012, 07:46 AM |#5  
prabhu1980's Avatar
OP Senior Member
Flag Indore
Thanks Meter: 118
 
More
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.
The Following User Says Thank You to prabhu1980 For This Useful Post: [ View ] Gift prabhu1980 Ad-Free
16th May 2012, 09:06 AM |#6  
Princeomi's Avatar
Senior Member
Thanks Meter: 25
 
More
Quote:
Originally Posted by prabhu1980

b) Download the following (Importantly the .pit file)

[B][COLOR="red"]PIT: Q1_20110914_16GB.pit

I had a feeling that the partitions are messed up by the kernel and restoring it by pit would help, as it worked for a few people. Anyway here are the pit files
The Following 4 Users Say Thank You to Princeomi For This Useful Post: [ View ] Gift Princeomi Ad-Free
16th May 2012, 09:33 AM |#7  
Senior Member
Flag Pune
Thanks Meter: 98
 
More
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.
The Following User Says Thank You to anilisanil For This Useful Post: [ View ] Gift anilisanil Ad-Free
16th May 2012, 09:39 AM |#8  
prabhu1980's Avatar
OP Senior Member
Flag Indore
Thanks Meter: 118
 
More
Wink
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.

Quote:

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 !!!

Quote:

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.
16th May 2012, 09:41 AM |#9  
chasmodo's Avatar
Senior Member
Flag Novi Sad
Thanks Meter: 41,308
 
More
Quote:
Originally Posted by prabhu1980

Did you try the method posted above while using the JIG ?

I did when my Note got bricked, and it didn't help one little bit.
16th May 2012, 09:54 AM |#10  
prabhu1980's Avatar
OP Senior Member
Flag Indore
Thanks Meter: 118
 
More
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"
The Following 2 Users Say Thank You to prabhu1980 For This Useful Post: [ View ] Gift prabhu1980 Ad-Free
16th May 2012, 10:01 AM |#11  
Senior Member
Flag Pune
Thanks Meter: 98
 
More
Quote:
Originally Posted by prabhu1980

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!
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes