[Guide]How to revive your bricked Gnote

[forest1971]

Hi



Anyway - as promised, here is my table

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 6362MB 8509MB 2147MB ext2 DATAFS
11 8509MB 15.2GB 4691MB fat32 UMS msftres
12 15.2GB 15.8GB 537MB ext4 HIDDEN

No it's all good that we share experience to learn from one another. These numbers we can easily mistake them.

Yeah, you lost quite some space of UMS and partition 10 is still ext2. It should still work work but maybe better to convert it back to ext4 again. (or this is the table before you converted).

Indeed in your case the PIT file from hg42 will not work since you also have some bad blocks inside the former UMS/sdcard. It needs manual re-partition.

Your sharing has been very helpful. cheers.

 

[smack_t]

No it's all good that we share experience to learn from one another. These numbers we can easily mistake them.

Yeah, you lost quite some space of UMS and partition 10 is still ext2. It should still work work but maybe better to convert it back to ext4 again. (or this is the table before you converted).

Indeed in your case the PIT file from hg42 will not work since you also have some bad blocks inside the former UMS/sdcard. It needs manual re-partition.

Your sharing has been very helpful. cheers.

oh.. good catch.. it is still ext2. Ill convert and see if it works.
EDIT: I guess it was a copy before i converted to ext4. Just checked DATAFS, it is ext4. I was making copies of the table every step to make sure i did everything correctly. I guess i forgot to make a copy at the very end. UMS is fat32 - i think ill leave it as it is, dont wanna change anything, since its all working and i dont want to go back to using my xperia arc if i mess something up

 

[shumi93]

easy fix bricked G-NOTE

By hoping that it helps someone, for me that worked without probleme.

Link : http://www.android.gs/easily-fix-bricked-samsung-galaxy-note-n7000/

Enjoy

 

[forest1971]

What is the command to scan the partitions if it is fine. I do that because I may overlook the error message and somehow the partitions was created successfully.
Thanks!

If you like to check if a partition has bad block or not you can use the tools that already come with the kernel. Use the code below.

If you like to check partition 7, which is cache, for example then run:

code:
~ # e2fsck -c /dev/block/mmcblk0p7

You can do the same with 9, 10.

(Note: e2fsck should be run after umount /cache and umount /system and umount /data)

For partition 11 you can check using parted (since e2fsck cannot handle fat32)

code:
(parted) check 11

if it does not return any error the partition 11 is probably fine.

I will update the guide with these.

cheers.

 

[serpent2005]

By hoping that it helps someone, for me that worked without probleme.

Link : http://www.android.gs/easily-fix-bricked-samsung-galaxy-note-n7000/

Enjoy

Did you use the patched pit?

 

[xiaojian24]

hi, does anyone knows how to update /etc/fstab/ back to the note after reviving, i got a lot of problems with tt, i think it causes a lot of fc on my phone, thanks

 

[serpent2005]

Yes. Thats what i mean.

I noticed the same thing after first unbrick that only customs roms would flash and not any stock. I then checked each part starting with modem and noticed more issues so i parted the entire thing again offsetting by 1gig. tried stock using odin right after, stock LC1, and magic - it worked and unpacked without issue.

Sent from my GT-N7000 using XDA

I was also able to flash stock GB ROM but the phone has endless loop at samsung logo. Did you have this issue?

EDIT: When the phone reboots (after flashing stock ROM via Odin) it goes into Android recovery and begins to install some packages. It fails with this error: E:Error in /cache/recovery/sec_csc.zip (Status 7)

 

[metalcerb]

I don't know what happens in my note, i am running ICS Kingdroid v2.1 and i try to flash 2.3.6 Checkrom V6, but the flashing process freeze. Know i am not able to flash (always have freezes), but i have acess to cwm and download mode. Now i try to flash the oficial 2.3.6 THP Portugal by odin but process freeze again. Can someone help me ?

 

[smack_t]

I don't know what happens in my note, i am running ICS Kingdroid v2.1 and i try to flash 2.3.6 Checkrom V6, but the flashing process freeze. Know i am not able to flash (always have freezes), but i have acess to cwm and download mode. Now i try to flash the oficial 2.3.6 THP Portugal by odin but process freeze again. Can someone help me ?

Did you flash a custom kernel before flashing V6?

Sent from my GT-N7000 using XDA

 

[metalcerb]

No, i only copy he checkrom file to sdcard, reboot to cwm, do a full wipe and flash zip from sd card.

After that, i am not able to flash anithing, i always have freeze.

 

[smack_t]

No, i only copy he checkrom file to sdcard, reboot to cwm, do a full wipe and flash zip from sd card.

After that, i am not able to flash anithing, i always have freeze.

Sorry to hear that man.
Try to follow the procedure on this post (page 2). Except just create the partition as it is now. Just see if you have any corruption issues.

However, dont stress too much, the fact you can get into download mode means its not over yet

---------- Post added at 02:18 AM ---------- Previous post was at 02:11 AM ----------

I was also able to flash stock GB ROM but the phone has endless loop at samsung logo. Did you have this issue?

EDIT: When the phone reboots (after flashing stock ROM via Odin) it goes into Android recovery and begins to install some packages. It fails with this error: E:Error in /cache/recovery/sec_csc.zip (Status 7)

Can you try going into recovery and mounting cache and see if you have any errors ? If you cannot mount it, there maybe something wrong with cache. See page 2 on how to re-part it.

 

[metalcerb]

I know, but after the brick i was so happy when saw the download mode working and cmw.. But now i'm not so happy, i can´t flash nothing in cwm neither download mode with odin, i try flash last 2.3.6 THP Portugal but have no sucess.

Now if i want go to cmw i have this message :

Firmware upgrade encountered an issue. Please select recovery mode in kies & try again..

Nothing work now, but samsung repair service cannot see nothing wrong cwm don´t appear and binary count download is NO.. Tomorrow in the mornig i go to samsung service.

 

[smack_t]

I know, but after the brick i was so happy when saw the download mode working and cmw.. But now i'm not so happy, i can´t flash nothing in cwm neither download mode with odin, i try flash last 2.3.6 THP Portugal but have no sucess.

Now if i want go to cmw i have this message :

Firmware upgrade encountered an issue. Please select recovery mode in kies & try again..

Nothing work now, but samsung repair service cannot see nothing wrong cwm don´t appear and binary count download is NO.. Tomorrow in the mornig i go to samsung service.

Yes - Samsung Service is the best option! - Cheers.

 

[metalcerb]

Donwload mode continues to working, but fail when i try to flash GB oficial thp portugal but fail to.

 

[apurvapatel]

sending to SSC to claim warrenty

Update...

Since my UMS partition was continuesly throwing up bad sectors everytime I tried to install any ROM or tried to re-partition, I have decided to send the phone to the Samsung Service Center.

To prepare the phone to send it to the SSC, I did the following steps

• flashed the 4pda_kernel.tar to get adb

• got in adb shell and removed partition 9,10 and 11

• flashed ICSKernelTest.tar to remove the yellow triangle and the counts

• flashed stock_kernel_N7000DDLB2.tar to remove the custom kernel's recovery

• and finally I flashed DDLB2 rom via odin. It freezes at the factoryfs write.

Now my Note says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"

Phone gets into the download mode, doesnt get in recovery.

Hopefully this has removed all the traces of rooting, custom recovery, custom roms and since there are no partitions at all, it should also remove traces of re-partitioning.

---------- Post added at 07:50 AM ---------- Previous post was at 07:48 AM ----------

Donwload mode continues to working, but fail when i try to flash GB oficial thp portugal but fail to.

I suggest you flash a stock kernel on your phone, just in case. It would remove traces of custom recovery, if there are any.

 

[metalcerb]

I need to find one stock kernel to flash..

---------- Post added at 04:01 AM ---------- Previous post was at 03:49 AM ----------

I flash with sucess this file - N7000-XEO-N7000XXLC1 Kernel

Now i try again flash by odin last GB oficial Portugal, but i have same error in odin ( ID:0/003> factoryfs.img ).

 

[serpent2005]

This thread has been especially useful for helping me to recover from superbrick. Just want to personally thank forest1971, smack_t, and Shumi93 for their assistance.

I had a lot of kernels on my sd card and I mistakenly wiped with an unsafe ICS kernel. Found this thread and followed the instructions posted in the link in the OP to forest1971's tutorial on repartitioning. Those instructions allowed my Note to successfully load (via CWM) and run a custom GB ROM. But I was not completely happy because I wanted to run stock ICS and I couldn't flash any stock GB or ICS using Odin (desktop and mobile). Then I ran across Shumi93's post (link) which linked to an article about unbricking from superbrick using a PIT file. Followed the instructions in that post and used the provided pit named Q1_20110914_16GB-patched.pit along with stock GB ROM N7000DXKL1 and it worked!! After this I was able to use Odin to flash stock ICS ROM N7000XXLQ2 and now my phone is back to the way it was before the superbrick . I've restored all of my applications using TitaniumBackup and everything is behaving well.

I spent a few hours partitioning and repartitioning my phone before trying the PIT method so I have no idea if it was the combination of partitioning and the PIT method that caused this goodness.

My phone did go from having about 12GB of useable space to about 8GB of useable space. Not a big deal for me because I put most of my stuff on the external SD card.

 

[smack_t]

This thread has been especially useful for helping me to recover from superbrick. Just want to personally thank forest1971, smack_t, and Shumi93 for their assistance.

I had a lot of kernels on my sd card and I mistakenly wiped with an unsafe ICS kernel. Found this thread and followed the instructions posted in the link in the OP to forest1971's tutorial on repartitioning. Those instructions allowed my Note to successfully load (via CWM) and run a custom GB ROM. But I was not completely happy because I wanted to run stock ICS and I couldn't flash any stock GB or ICS using Odin (desktop and mobile). Then I ran across Shumi93's post (link) which linked to an article about unbricking from superbrick using a PIT file. Followed the instructions in that post and used the provided pit named Q1_20110914_16GB-patched.pit along with stock GB ROM N7000DXKL1 and it worked!! After this I was able to use Odin to flash stock ICS ROM N7000XXLQ2 and now my phone is back to the way it was before the superbrick . I've restored all of my applications using TitaniumBackup and everything is behaving well.

I spent a few hours partitioning and repartitioning my phone before trying the PIT method so I have no idea if it was the combination of partitioning and the PIT method that caused this goodness.

My phone did go from having about 12GB of useable space to about 8GB of useable space. Not a big deal for me because I put most of my stuff on the external SD card.

Good stuff man. Glad you are up an running. This thread and all its contributors were extremely helpful in getting my gnote unbricked too! Awesome stuff

 

[shumi93]

Yep i used patched pit for my 16Gb G-NOTE.

 

[serpent2005]

Yep i used patched pit for my 16Gb G-NOTE.

Thanks. I downloaded the ZIP file expecting to find 2 PIT files in there (1 for 16-GB and 1 for 32 GB). Found out there are a boatload of them with no explanation as to what the files are for. I ended up trying the "unpatched" 16-GB PIT file first. When that didn't work I tried the patched 16-GB PIT file and that worked.