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

Is this Idea Working ?


  • Total voters
    93
  • Poll closed .

dusty_nz

Senior Member
May 5, 2008
465
11
0
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
Check partitions after restart
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 264MB 210MB ext4 CACHE
8 264MB 281MB 16.8MB MODEM
9 3322MB 4215MB 893MB ext4 FACTORYFS
10 4215MB 6362MB 2147MB ext4 DATAFS
11 6362MB 15.2GB 8838MB fat32 UMS msftres
12 15.2GB 15.8GB 537MB ext4 HIDDEN
 

forest1971

Senior Member
Apr 3, 2012
1,694
2,133
0
The partition table looks fine. Try to install one or two other roms. Should try gb and cm9 custom roms. If they do not work then try to repartition again leave out the area currently occupied by partition 9 and 10. See how it goes.
 
  • Like
Reactions: prabhu1980

dusty_nz

Senior Member
May 5, 2008
465
11
0
The partition table looks fine. Try to install one or two other roms. Should try gb and cm9 custom roms. If they do not work then try to repartition again leave out the area currently occupied by partition 9 and 10. See how it goes.
Eg push Partitions 9 and 10 further out. Will give that a go as well after trying a few more things. Might also try and delete the cache and move as well.

Have tried to flash CM9 from the current 4pda_kernel.tar kernel however get Assert Failed errors.

Checked I have the right version. Even disabled the scripts asserts. No go. Missing any tricks?

Just flashed Abyss 3.9 and that worked okay. Into CWM again. Still the same issue with CM9

Also, Trying to run ADB from any kernel other that the 4PDA one I get the following error trying to connect
- exec '/system/bin/sh' failed: No such file or directory (2) -
 
Last edited:

forest1971

Senior Member
Apr 3, 2012
1,694
2,133
0
The 4_pda kernel and abyss can work only with custom gb. For cm9, after installing rom you need to install a safe ics kernel such as franco or speedmode. It is important point. Mismatch kernel and rom will cause bootloop.
 
  • Like
Reactions: prabhu1980

dusty_nz

Senior Member
May 5, 2008
465
11
0
The 4_pda kernel and abyss can work only with custom gb. For cm9, after installing rom you need to install a safe ics kernel such as franco or speedmode. It is important point. Mismatch kernel and rom will cause bootloop.
So..
Starting where I am now.
Flash Franco Kernel
Restart into recovery
Flash CM9
reboot

??
 

dusty_nz

Senior Member
May 5, 2008
465
11
0
Yes. May also wipe cache and data/factory reset.
Hmm. Flashed the "Safe kernel referenced in the CM9 thread.

Flashed via Odin. Restarted into CWM.
Flashed CM9, No Assert error but hung.
Restarted and tried to wipe. Hung formatting Cache.

Looking like more issues with bad blocks.

Also ADB working again. Will work from here.

Thanks heaps Forest1971. Great having your assistance.

Might toos down till tomorrow night.
 

dusty_nz

Senior Member
May 5, 2008
465
11
0
Hmm. Flashed the "Safe kernel referenced in the CM9 thread.

Flashed via Odin. Restarted into CWM.
Flashed CM9, No Assert error but hung.
Restarted and tried to wipe. Hung formatting Cache.

Looking like more issues with bad blocks.

Also ADB working again. Will work from here.

Thanks heaps Forest1971. Great having your assistance.

Might tools down till tomorrow night.
Still plugging away.

Safe kernel is causing issues. Random reboots when in CWM
In ADB, I have repeat run the DD read on Cache and Factory partitions. 10 times each and no errors.

Managed a wipe, Davik cahe and cache partitions in CWM, Worked this time. Re applying CM9 but have the feeling it has hung on "Installing Update..."

.... It has just re-booted while trying to flash CM9

---------- Post added at 10:12 PM ---------- Previous post was at 09:34 PM ----------

Woohooo.
Looked like corrupted system partition.
Deleted and re-created in ADB. ("rm 9" then "mkpartfs primary ext2 3322 4215" then "name 9 FACTORYFS")
Back in CWM I was able to unmount system (Hung Prev)
Flashed CM9 and Apps.
Wipe

Rebooted.

Booted in, Have run through setup. Rebooting now. All good.

Must say thanks to Forest1971 who provided excellent guidance and quick responses which is great.
Also I can vouch for the Hard Brick recovery worked but it requires time and patience.
 
  • Like
Reactions: forest1971

84DGR

Senior Member
Oct 4, 2010
202
10
0
So I tried to update the Note GT-N7000 Monday, Worked well on stock ICS N7000DXLP9_N7000OLBLP6_N7000DXLP5_HOME.tar.md5 for a while yet after a while it couldnt read the Sim card, so I tried flashing a new Radio ROM through PC Odin, that didnt solve it either,

I read on rtGalaxyNote.com that the note could use any ROM from stock no matter the region. so I tried flashing a couple others,

this failed,

I installed Franco Kernel v10 and then tried to flash abyss kernel for the CWM to flash KingDroid v5.1. when i was doing this I noticed that the wipe/data was running extremely slow (30minutes and didnt do anything) so I rebooted and did it again this time after a while it did wipe it all, as it stated I then flashed the KingDroid v5.1 and it got to 7% through the install and rebooted. now i notice that there is a yellow triangle meaning @ the boot screen and it goes into a boot loop.

I thought i would put it back to stock yet this failed, I put it back in download mode and now the flash counter is at 5, so i tried to reset it with the ICSTESTKernel.tar and nothing, just keeps adding counters to this.

Long story short I cannot flash an original kernel, it will only flash Abyss, SpeedMod or CM9. and will not boot any ROMs,

Is there a way to reset this phone completely and start back at square one? any help would be great

these are the websites i have used,

http://forum.xda-developers.com/show....php?t=1424997
http://forum.xda-developers.com/show....php?t=1789397
http://forum.xda-developers.com/show...php?p=25781106
http://forum.xda-developers.com/show....php?t=1673072
http://forum.xda-developers.com/show....php?t=1659768
http://forum.xda-developers.com/show....php?t=1535025
http://forum.xda-developers.com/show...1663237&page=2
http://www.mediafire.com/?5bmrc6cf81w5mya
http://rootgalaxynote.com/galaxy-not...omtouchwiz-ux/

http://forum.xda-developers.com/show....php?t=1652831

I have been doing this for 3 days now and i'm fearful of this being Bricked

I have flashed ROMs and Kernels before yet this is weird

any help would be great

Cheers

84DGR
 

prabhu1980

Senior Member
Dec 13, 2009
288
127
0
Indore
Oh you tried flashing from stock ics . Can you please elaborate .. because if you even did a wipe with stock ICS kernel you are at risk. Now related to flashing the kernel I am surprised why you could only flash few kernels.
Can you try flashing glewarnes notecore kernel or alliance ROM fiectos kernel and let is know our progress.

Sent from my GT-N7000 using XDA Premium HD app
 

84DGR

Senior Member
Oct 4, 2010
202
10
0
Yeah I did... didn't think about a bad kernel however using forest1971 method it is back up and running. Yet the only problem is it will not read the simcard... it just keeps saying that there is no sim inserted


???? Ideas

Sent from my GT-N7000 using xda app-developers app
 

84DGR

Senior Member
Oct 4, 2010
202
10
0
I tried 5 sim cards all the same, it was like that before I flashed I think the reader is stuffed

Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
 

adv392

Senior Member
Feb 25, 2009
152
42
0
Sacramento
I recently saw the news about the super brick
anyway I had installed stock ICS using ODIN and now wanted to try the CM9.
I thought I would factory reset and start fresh, did a factory reset while using stock ICS from Settings->Backup and restore
Later read the news about the super brick. But my Note is working fine after factory reset (but the Got Brickbug? app says my chip is vulnerable to a brick, guess I was lucky?). Now I would like to install custom ROMs but scared to do it due to the super brick warning. I would like to know how to proceed. I would appreciate if anyone could write a small guide.
Thanks and Regards,
(have attached screen shots of "About Phone" and the app "Got Brickbug?")
 

Attachments

Rulinglionadi

Senior Member
Mar 30, 2012
752
221
0
27
INDIA
www.facebook.com
So I tried to update the Note GT-N7000 Monday, Worked well on stock ICS N7000DXLP9_N7000OLBLP6_N7000DXLP5_HOME.tar.md5 for a while yet after a while it couldnt read the Sim card, so I tried flashing a new Radio ROM through PC Odin, that didnt solve it either,

I read on rtGalaxyNote.com that the note could use any ROM from stock no matter the region. so I tried flashing a couple others,

this failed,

I installed Franco Kernel v10 and then tried to flash abyss kernel for the CWM to flash KingDroid v5.1. when i was doing this I noticed that the wipe/data was running extremely slow (30minutes and didnt do anything) so I rebooted and did it again this time after a while it did wipe it all, as it stated I then flashed the KingDroid v5.1 and it got to 7% through the install and rebooted. now i notice that there is a yellow triangle meaning @ the boot screen and it goes into a boot loop.

I thought i would put it back to stock yet this failed, I put it back in download mode and now the flash counter is at 5, so i tried to reset it with the ICSTESTKernel.tar and nothing, just keeps adding counters to this.

Long story short I cannot flash an original kernel, it will only flash Abyss, SpeedMod or CM9. and will not boot any ROMs,

Is there a way to reset this phone completely and start back at square one? any help would be great

these are the websites i have used,

http://forum.xda-developers.com/show....php?t=1424997
http://forum.xda-developers.com/show....php?t=1789397
http://forum.xda-developers.com/show...php?p=25781106
http://forum.xda-developers.com/show....php?t=1673072
http://forum.xda-developers.com/show....php?t=1659768
http://forum.xda-developers.com/show....php?t=1535025
http://forum.xda-developers.com/show...1663237&page=2
http://www.mediafire.com/?5bmrc6cf81w5mya
http://rootgalaxynote.com/galaxy-not...omtouchwiz-ux/

http://forum.xda-developers.com/show....php?t=1652831

I have been doing this for 3 days now and i'm fearful of this being Bricked

I have flashed ROMs and Kernels before yet this is weird

any help would be great

Cheers

84DGR

The videos in my sig will help you !! :cool:
 

CIkubage

Member
Aug 31, 2012
6
0
0
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 THE FOOLS 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
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.


: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


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

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:

My Note Originally comes with Gingebread version.
I've updated it to ICS 4.0.4.
Before I messed up and ended up with Soft Brick.
Now is my Note considered Gingerbread version or ICS version?