yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] MohElShafei:
Dear forest1971,

I hope you are doing fine and everything is ok.

I'm posting this comment after getting really very very disappointed and confusing of what my SGN is doing to me. Now I'm able to locate the bad blocks .. and I'm surly out of these blocks in the currently eMMC structure. I did everything to make sure that FACTORYFS, DATAFS, and UMS partitions are in clear blocks, even though, random restarts, freezing, and hanging all the time.

Note: RECOVERY, CACHE, and KERNEL are also in clear blocks (after running the Partition Scanner app).

I also did a check that certainly made me sure that the I'm in a clear area in UMS. I mounted my SGN in the PC after flashing a ROM, then I copied to/from anything in the UMS partition till its full (more than a time) and it works like a charm, with no hangs at all. That made me certain that these blocks are OK. Even though, it hangs!!!!!. In addition I did the following checks:

Run the Partition Scanner app and shows no errors at all (from hg42 post)

Did the DD command scan method, and shows no errors in all partitions (from your post)

Did the e2fsck check method, and shows no errors (from your post)

I can wipe all partitions in Recovery without any errors or hangs at all

I can install all types of roms without errors, no hangs in FACTORYFS image in odin at all

Now I'm about to go mad, everything is fine, I'm out of bad blocks, even though; freezing all the time and Force Close !!!!!!!!!!!!!!! WHY??

I noticed also that ICS stock ROM installed without the Lock Screen, strange!!!

Is there any explanation of what my phone is doing?

Thanks a lot for your efforts.

Mohamed
[Galaxy Note GT-N7000 General] forest1971:
Hi, i am doing fine. Tks.

About the issues facing, please refer to my reply in the other thread. Cheers.

Sent from my phone
[Galaxy Note GT-N7000 General] MohElShafei:
Thank you a lot forest1971 for your interest and for your reply. I got your response .. thanks a lot my friend .. you rock always :)

Wish you a wonderful day :)

Regards,

Mohamed
[Galaxy Note GT-N7000 General] Stevoxda:
I wasn't using any custom rom

I have Galaxy Note N7000

i was running stock ICS 4.0.4 (open Germany) [N7000XXLRK_N7000DBTLRK_DBT]

My phone was rooted but with no custom binary counts.

I install beat audio driver and I count restart my phone. it was stuck on the samsung screen

I didnt have any back up so i tried to use Odin and re-flash my stock ICS firmware but its stuck at NAND write start!!!

I have read so many threads but it hasn't helped. it seems like almost everyone is using custom roms

i even got one binary count follow the tutorial on this thread after i flashed a kernel (4pda_kernel.tar) http://xdaforums.com/show...7&postcount=12

Ive also tried stock gingerbread still stock there..

My phone is able to enter recovery mode or download mode or stock in the samsung screen..

PLEASE help me
[Galaxy Note GT-N7000 General] hg42:
This is a thing I am wondering about.

Though many have better results with GB and cm9, I cannot think of any way how an ICS ROM should be worse than GB after a brick.

I got the feeling that it's a matter of probability, which let's ICS hit the problem more often than others.

So, would you please try my partition scanner (the infinite variant) to check if your partitions are really brick free now?

Let it run many cycles, e.g. several hundreds of cycles or may be overnight, but please check if it's getting hotter and hotter, then a long run may be critical for your phone and you should stop the test.

---------- Post added at 11:29 PM ---------- Previous post was at 11:19 PM ----------

please note, if you hit a bricked block, the whole emmc is totally locked up and unusable until you reboot.

So any following error isn't real, it's only a follow up of the first error.

Always keep this in mind when trying to find logical relations in the behavior.

---------- Post added at 11:37 PM ---------- Previous post was at 11:29 PM ----------

this may be an emmc brick, because you were on stock ICS and I assume someone did a wipe (you or some script).

To check this, please try my emmc scanner

You could try the find_brick_start and if that finds a brick (which means you get a freeze) you can use the find_brick_end variant to locate the end of the bricked blocks, if any.

PS: please don't quote such a long post completely
[Galaxy Note GT-N7000 General] forest1971:
Stevoxda:

How are you going with your Note?

If you still need help then will need to tell us if your aim is to get help from service center or to try to fix it on your own then we can advice a more suitable strategy. Best.
[Galaxy Note GT-N7000 General] gx3k:
Hi guys, hope you can help.

I installed CleaNote ROM and it worked fine (restored all my apps via titanium backup) then I rebooted to recovery and installed NoteCore 14 kernel and 15toggle zip which was recommended for the ROM. Now i am stuck in white boot up GT-N7000 screen and cannot go back to recovery mode. I can only go to download mode.

Any ideas? Thanks :)

EDIT: Sorry if off topic, I'll be moving to this thread for help. Thanks :)
[Galaxy Note GT-N7000 General] prabhu1980:
Yes this is off the topic.

Stuck at boot animation is just a softbrick.

Reinstall gl notecore kernel with odin incase your vol up + home +power does not take u to recovery.

Also v14 takes 30s to load recovery mode. Pls wait....

Reinstall rom without wipe and then upgrade ur kernel.
[Galaxy Note GT-N7000 General] No.01:
help my Note!
[Galaxy Note GT-N7000 General] forest1971:
Hi,

Once the scan encounter the faulty blocks it often cause the chip to freeze. then it will not allow command to run properly. You should restart phone again then you will be able to remove 10 and 11.

btw, hg42 has designed a very useful scan tool that can tell exactly where the faulty blocks are. You should try that tool as well:

http://xdaforums.com/showthread.php?t=1823918

use the emmc_find_brick_start and emmc find_brick_end to locate the faulty area.

Then you can use pit file or manual method to re-partition to leave the faulty area unused.

Cheers,
[Galaxy Note GT-N7000 General] No.01:
The scan with emmc works long time.. first works very fast then becomes slower and didn't stop!

Q: what does MiB and MB means and the numbers behind it in scanning?

can you show or tell me by steps after scanning what should I do, am a beginner in fixing devices.
[Galaxy Note GT-N7000 General] forest1971:
The scanner freeze which confirm you have bad blocks in the emmc. If you can get the find_brick_start and find_brick_end to work then can identify clearly the faulty area. If cannot get that done then just need to try manually different ranges in the emmc.

I remember you encounter freeze with datafs but not with factoryfs. Therefore, should try to create factoryfs in the same place and with the same size.

Then remove and recreate datafs and UMS from 3322 mb up.

from your previous post it seems you could not create datafs. It is often because you have created it in an area that has bad block. Should move to the next range.

In some cases the command : (parted) mkpartfs primary ext2 <begin> <end> does not work for some (unknown) reason. Then you should try to use the command below to create an empty partition:

(parted) mkpart primary <begin> <end>

then name the partition the way explained in the guide and use CWM to format it.

Let us know how it goes. Cheers,
[Galaxy Note GT-N7000 General] No.01:
maybe here's the problem when print in cmd, that in 10 datafs File System there's no "ext4" !!

http://xdaforums.com/attachment.php?attachmentid=1292736&stc=1&d=1346354071

Becuase I did the steps, but nothing different happened just stuck at datafs.. I did the re-partition and I changed the range and it done, but still stuck at datafs in odin!
[Galaxy Note GT-N7000 General] forest1971:
It is always useful to post partition table so that we know where you are in the process. From the screen shot attached, you have created partition 10 in the same place as before brick. So it will not work because the brick/faulty area is still inside this partition. Follow the steps below and tell us how it goes.

1. flash original pit file from Dr Ketan (thanks to Dr Ketan)

http://d-h.st/FVh

This is to make sure partition 9 is restored to original stage/size

2. connect in adb and using parted to remove 10 and 11 only (leave 9 alone) and start making partition 10 from 3322 mb:

Code:

(parted) mkpartfs primary ext2 3322 5469

(parted) mkpartfs primary fat32 5469 15200

(parted) name 10 DATAFS

(parted) name 11 UMS

Then go into CWM, go to mount and storage menu and format system and format data.

3. recheck partitions using dd:

code:

~ # dd if=/dev/block/mmcblk0p9 of=/dev/null

~ # dd if=/dev/block/mmcblk0p10 of=/dev/null

~ # dd if=/dev/block/mmcblk0p11 of=/dev/null

if they run smoothly and report something like" in out copied" it means the partitions are fine.

Then you should be able to flash rom as usual. Should use GB rom first. if stock rom do not work then try custom gb rom from here.

See how it goes. cheers.
[Galaxy Note GT-N7000 General] No.01:
I'm trying now, but can I change the (end) number mkpartfs primary ext2 3322

5469

cause it freeze when re-partition!

and it asked me many times and I answers retry 3 or more times, if I changed the number on what basis I put it?

http://xdaforums.com/attachment.php?attachmentid=1293489&stc=1&d=1346390791
[Galaxy Note GT-N7000 General] forest1971:
OK. In that case need first to power off and on the phone (since the chip often lock up when the damage part is touched).

Then go to adb parted again.

then

(parted) mkpartfs primary ext2 5470 7617

If still not work then power off and on the phone again, then try with another range like

(parted) mkpartfs primary ext2 7617 9764

and just need to move up that way until parted is happy to create the partition 10. Then the remaining area of memory will be for partition 11 (UMS).

Let's go step by step and see how it goes.

Added more options:

if [ (parted) mkpartfs primary ext2 5470 7617 ] does not work then may also try

(parted) mkpart primary 5470 7617

(parted) name 10 DATAFS

then go into CWM and format data. if CWM can format data successfully it is good. Then continue with making the UMS.
[Galaxy Note GT-N7000 General] No.01:
This is the image after doing what you said (mkpart primary 5470 7617) without ext2 with format/data.

and still stuck at datafs!

I did the scan with dd and it's fine no faulty blocks.

where's the problem then?!

note: I tried flashing from recovery but it stuck at animation logo!(Kingdroid and CM9 roms)

And Thank you very much for your care :)
[Galaxy Note GT-N7000 General] forest1971:
Have you also checked again partition 9 using dd, just to make sure it is fine too? If the partitions are all fault free then should be able to install rom. Try both custom gb and stock gb (from dr.ketan thread). Cheers.

Sent from my phone
[Galaxy Note GT-N7000 General] raz-or:
Hi forest,

hope you can help, trying to repair a friends bricked note, have tried flashing stock gb / ics, get a fail on datafs,

scanning for partition errors tells me 10/11 have a problem

i then ran e2fsck as per your instructions but it runs for hours and then i think either recovery crashes or cmd, it appears to come across bad blocks and then force overwrites them

ran for 9 hours the first time and then for 16hours the second time,

im not sure if e2fsck is correcting anything and does the process need to run again or does it retain some of the work it did?

am close to giving up and just re-partioning and losing the 3gb!

any help is appreciated. ta.
[Galaxy Note GT-N7000 General] forest1971:
Hi,

If I understand correctly, you have already been able to get the device revived and running. That is very good!

The loss of 3gb of space is not so much and can be easily compensated by an external sdcard. e2fsck can only repair minor file system corruptions. It seems it cannot fix the damage caused by emmc bug kernel. So just have to live with the loss space. cheers.
[Galaxy Note GT-N7000 General] No.01:
I'd scan all partitions 7,9,10 and 11 they're fine free faulty blocks but.. the same thing happens to me!!! by flashing gb (wipe) stock rom still freezes at datafs :confused: ..and I tried to flash a rom from one pda file, it completed then freezes at samsung logo.:mad:

About Dr Ketan custom gb rom thread can you give me the link pls.:(

And thank you so much.
[Galaxy Note GT-N7000 General] forest1971:
In the case you have been able to flash a rom successfully from one file in pda, then try to go into recovery, wipe cache, dalvik cache and data. See if that help it to boot properly.

The links for stock rom from dr.kentan is below. GB rom is in second post.

http://xdaforums.com/showthread.php?t=1424997

cheer,
[Galaxy Note GT-N7000 General] No.01:
Ok, I did wipe cache and data as you said but I didn't found dalvik cache, so.. it stuck now at "installing applications...." maybe from 15min!!

what should I do?
[Galaxy Note GT-N7000 General] forest1971:
Just try to stop the process, restart the phone. see how it goes.

Have you tried to install a custom gb rom such as darky rom, rocket rom, checkrom yet?
[Galaxy Note GT-N7000 General] No.01:
:D:

Finally my phone works.

Thank you bro very very much ;)
[Galaxy Note GT-N7000 General] forest1971:
Wow! I feel good too. It was rather difficult :). what was the rom that worked for you?
[Galaxy Note GT-N7000 General] No.01:
ICS 4.0.4 German version.
[Galaxy Note GT-N7000 General] forest1971:
Ics stock kernel is not safe so should use a safe kernel such as Notecore. Cheers.

Sent from my phone
[Galaxy Note GT-N7000 General] hg42:
I want to note, that I have updated the pit thread with new pits and instructions to take advantage of the emmc scanner tools.

Finding the correct pit should be easy now.
[Galaxy Note GT-N7000 General] raz-or:
hello,

its not running as i still cannot boot past 'samsung galaxy note n7000' so still stuck there im afraid, but am sure my factoryfs is ok its just the datafs

will try hg42 method to get start and end points and then try your repartition method.

btw has anyone reported a fix just using e2fsck?
[Galaxy Note GT-N7000 General] forest1971:
Hi should use the scanner to find start and end of the brick area. Then it will easy to choose the best repartition way. If factoryfs is ok then using manual method can help save some more space. In case both factoryfs and datafs is damaged then using pit method is more simple and effective. E2fsck will help when the damage is caused by other reason but not emmc bug. Cheers.

Sent from my phone
[Galaxy Note GT-N7000 General] No.01:
hi froest..

yesterday I've fix my note, but it became restarting by itself many times and its on ginger bread rom!

then I tried to flash another roms but it stuck at samsung logo, I did wiping data but it freeze at installing applications then I reboot it but still stuck at installing applications! I've reboot it many times but the same result.
[Galaxy Note GT-N7000 General] forest1971:
Not a good sign: we have encountered some cases of random freeze with unknown reasons so far.

Above is one issue. But now you have encountered the problem of not being able to install and boot: I suspect there are bad blocks in the current datafs partition. (One thing is that you have install stock ics which has unsafe kerenel. With that unsafe rom we can make mistake and trigger the emmc bug again at some point. but the bad block can also be unstable and can grow some more).

I would do a few things below:

1. Just repartition again datafs to leave more space unused. calculate the number to make sure the size of datafs is 2147 mb (use the end number to subtract by start number when creating partitions. You can remove partition 10 and 11 and make partition 10 from 7617 to 9764).

And/or do more diagnostic to find bad blocks:

2. use dd to to scan again all 12 partitions. just change the partition number in the dd command.

3. use the scanner from hg42 again to identify the exact location of start and end of bad blocks. I remember you did it before and it did not work, but there is no harm to try again. try the find_brick_start and find_brick_end zip files. You may need to try them a few times. (just download and copy the scanner zip files into the internal sdcard, boot into CWM and flash the files and it will run). Once you have the number of start and end of bad blocks then we can choose the best way to re-partition using a pit file or manual way.

Let try those and see how things go. cheers.
[Galaxy Note GT-N7000 General] thelonite:
my note running ics 4.0.4 just crashed while updating a game called shadow era

then it wont pass through the samsung logo or in my case the netcore kernel android logo

checked the CWM everything was unmounted

went to odin and did a reflash with stock ICS 4.0.4

its stuck at 1/4 factoryfs

this phone got bricked once and got revivied with forests guide

im currently stumped...

added: successful flash of ICS 4.0.4 via PC ODIN but still stuck at samsung logo.

added: then suddenly it worked... currently initializing stuff... wonder if this will continue to work....
[Galaxy Note GT-N7000 General] forest1971:
Hi just to connect adb and use dd command to check partitions to see if the current partitions have bad blocks. Then repartition again to leave the bad blocks unused.

Should also make use of new scanner by hg42 to find start and end of faulty blocks and consider using custom pit files well. Let me know if you have problem doing repartition. Cheers.

Sent from my phone
[Galaxy Note GT-N7000 General] thelonite:
its currently working after 40 minutes

im still stumped
[Galaxy Note GT-N7000 General] No.01:
Thank you very much, I will try to repartition again
[Galaxy Note GT-N7000 General] No.01:
I did the repartition now, but can I restore the phone memory size cause it became so small 5GB!

And sends force close messages many times and stuck then reboot by itself!

I did wipe data and cache but same thing happens!

re-partition solved my first problem, but it made some problems to my phone!!:crying:
[Galaxy Note GT-N7000 General] forest1971:
Should try to change rom. Some people get better results using cm9 rom (such as nightlies). Also should try some custom gb roms. Best.

Sent from my phone
[Galaxy Note GT-N7000 General] uggies:
Wow.. Forest1971... I have to say I am amazed by your effort and will to help people. It has been nearly three months since I created this thread and myself has not been following this thread. On the other hand, you kind sir has been consistant and replied to all people asking for help. I would certainly donate if you provide your paypal account.

On behalf of all people, thank you for all your help. You are our savior :)
[Galaxy Note GT-N7000 General] forest1971:
Hi Uggies! good to see you posting again in our thread. It is very nice offer of you for donation :)! Btw, it will be a bit troublesome for you to send and for me to receive it so I will consider already receiving it from you. Thanks :).

We have been able to help some people to revive their brick Note so I feel happy being helpful. It's like a hobby. Still, in some cases there are problems with random force close and we do not know clearly the reason yet.

Please sometime revisit our thread, giving help or have some chit-chat if you have time. cheers.
[Galaxy Note GT-N7000 General] uggies:
I will try and visit from now on. Not sure if I can help people out like you though haha.
[Galaxy Note GT-N7000 General] PatrickNkamgnia:
Problem with my GNote after change the DPI

Hi All,

Hope I am in the good place to present my problem (i'm new in the forum and I'm just learning the "how to").

Yesterday I've rooted my Gnote (GTN7000 XXLPT - ICS just installed from OTA update). It was the paradise before i decide to instal "DPI change" ...

I set the DPI from 160 to 240 and then save + reboot ... Till that moment, my GNote stuck on the launching logo (Samsung Galaxy Note N7000).

I'm not an expert of Android (the proof ...) and I'm looking for the safest and easiest (step by step) solution to revive my GNote.

I know that XDA is an expert forum and therefore I please every of you that will see my request to help me ...

Ps: A part from the root I have applied no other manipulation on the phone (even the setup of the debuger mode).

Your kind help with this will be saving for me, given that there is no repair / after sale service available in my country.
[Galaxy Note GT-N7000 General] forest1971:
Your may not be an emmc bug brick, still ics kernel is unsafe. So the safest way is to flash a gb stock rom using pc. You can find links for dl from dr.ketan thread. Cheers.

Sent from my phone
[Galaxy Note GT-N7000 General] v.cecchetto:
Hi to all, this is my first post! :)

A little help for noobs like me about partition. You need a terminal, I suggest Terminal IDE, and root privilege for analyze your phone memory at low level.

To begin, a panoramic view of the memory:

$ su
# parted /dev/block/mmcblk0 print

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 281MB 1174MB 893MB ext4 FACTORYFS
10 1174MB 3322MB 2147MB ext4 DATAFS
11 3322MB 15.2GB 11.9GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN

better using sectors instead of megabytes, remember every sector is 512 B long, or half a KB:

# parted /dev/block/mmcblk0 unit s print

Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 30777344s
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 8192s 49151s 40960s ext4 EFS
2 49152s 51711s 2560s SBL1
3 53248s 55807s 2560s SBL2
4 57344s 73727s 16384s PARAM
5 73728s 90111s 16384s KERNEL
6 90112s 106495s 16384s RECOVERY
7 106496s 516095s 409600s ext4 CACHE
8 516096s 548863s 32768s MODEM
9 548864s 2293759s 1744896s ext4 FACTORYFS
10 2293760s 6488063s 4194304s ext4 DATAFS
11 6488064s 29720575s 23232512s fat32 UMS
12 29720576s 30769151s 1048576s ext4 HIDDEN

Before the beginning of the first partition we have 8192 sectors that are used to store MBR, GPT, PIT and BOOTLOADER.

Start with the MBR at sector 0 or better I indicate its position with LBA 0 (en.wikipedia.org/wiki/Logical_block_addressing)

# hd -n512 -s0b /dev/block/mmcblk0

0000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
*
00001c0: 00 00 ee 00 00 00 01 00 00 00 ff 9f d5 01 00 00 ................
00001d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00001e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00001f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa ..............U.

to understand it: en.wikipedia.org/wiki/Master_boot_record

My analysis:

[512 B]	-------- MBR --------

+446	[00 ... 00]	Bootstrap Code Area: no code at all!

Partition entry 1:

+1	[00]	Boot Indicator: non bootable

+3	[00 ..]	CHS Starting values: Cylynder, Head, Sectors, old system to indicate a position, nowday LBA is preferred: 0

+1	[ee]	Partition-type: efi

+3	[00 ..]	CHS Ending values: 0

+4	[01 00 00 00]	LBA Starting Sector: 1

+4	[ff 9f d5 01]	Partition Size (in sectors): 0x1d59fff = 30777343 sectors = 30777343 * 512 / 10^9 = 15,75 GB

Partition entry 2:

+16	[00 ..]

Partition entry 3:

+16	[00 ..]

Partition entry 4:

+16	[00 ..]

+2	[55 aa]	Magic Number

To summarize it indicate a global BIG! partition covering all the 16GB flash memory. Why? I saw 12 partition before? Because of GPT!!!

... continue if someone is interested :fingers-crossed: