yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] Robotu:
That is what i hoped, and i put it useful links to where the experienced devs are, in the galaxy note threads, but after a wile i realized something very sad, that many (though not all) from here on xda, devs, moderator, contributor, do not have that pourpouse in the first place, here is a place full of drugs and weed, an incurable ones, the pourpouse is to keep them self busy no matter what, if will ever reach that point when every thing work fine and is nothing there to improve (at least for a while), that will not be a good moment for this people, they will not could sit down and relax, wach a movie, take a walk in the park, maybe even make some sex, admiring the nature..... They are not here to improve, they are here only to keep theme self busy in the first place, for a while they gave it some attention to this I/O bug..., but after some time thay have returned to there drugs and weeds. Man i am not joking, i know what i am saying, just i do not have enough english with me to be more comprehensiv...
[Galaxy Note GT-N7000 General] uggies:
Ok. So I installed the kernel uploaded by matiasg85, and now adb shell can be run without mounting system! So i umounted everything on recovery (efs, cache, system, data, sdcard and emmc), and was also able to run adb shell command.

The rm9 and rm10 worked, but for some reason writting parts fails.

Any help please?
[Galaxy Note GT-N7000 General] forest1971:
This seems to be the case someone experience before. So he change the size for partition 9 from 281 to 900 and it work.

Then create partition 10 from 2100 to 3322. See how it goes.

Need to experiment a bit with different choices of partition size and location since we are still trying to locate the faulty area to avoid it.

In another case of some post above Cescomanto already identify he has (some blocks error about the 21xx blocks to 25xx block). so can also be a suggestion to avoid that area. In the case of Cescomanto I would create partition 9 from 281 to 1000 then partition 10 from 1000 to 2099.

In the case of drnull (in another device thread) he has to reduce the size of sdcard (ums partition) to give good areas for factoryfs and datafs and it worked for him. We have a large 12gb ums so reducing it be 2gb would not be too much? (Note: in this case should make sure you have back-up sdcard contents or should accept to loose it ).

But your case may be different. Just try some options. Hope it work out.
[Galaxy Note GT-N7000 General] uggies:
Thanks for the heads up :) from 281 to 800 worked like a charm

Nevertheless, after that, I am stuck at converting the factoryfs partition into ext4 format.

I get this

I have checked it through 'print' command, but it is in ext2 format
[Galaxy Note GT-N7000 General] forest1971:
Maybe you have unmount too many things? In the original guide from the post I read he suggest only need to unmount cache and data using commands in adb shell.

Maybe you should try the process again. This time run

adb shell

umount /cache

see if it works.

Then maybe also: "umount /data"

Its worked for me perfectly that way when I was re-partitioning another device using this method.

Otherwise try to mount emmc in the cwm?
[Galaxy Note GT-N7000 General] uggies:
Yea, tried and now it worked :)

But when I run

e2fsck -fDp /dev/block/mmcblk0p9 command,

it says WARNING: running this command might cause severe damage

Continue(y/n)?

should i?
[Galaxy Note GT-N7000 General] prabhu1980:
:) Dear Forest1971

Can we use mk2efs command with -c option for checking errors ??

Can we do it and see if the partition is clean.

I havent followed the thread for 2 days.

Sorry for that. But need ur help.

---------- Post added at 07:36 AM ---------- Previous post was at 07:30 AM ----------

Me Forest1971,

I have found a new tool mk2efs in cwm.

Can we find out what -c option will do for checking the partition.
[Galaxy Note GT-N7000 General] forest1971:
I did not see that warning when I did with another device.

The issue we have encounter when working with another device is:

-------

If e2fsck complains that it needs to be run manually, you should omit the -p flag. This happened to me the second time I ran through this process, but the first time it did not. I'm not entirely sure why. In that case, the e2fsck commands simply become:

~ # e2fsck -fD /dev/block/mmcblk0p9

Which will cause it to ask if you want to fix the group descriptors. Just answer 'Y' and let it run through.

-----------

Your warning seems to be different. I guess do not have many choice but to take risk with it? It has worked for me perfectly before in the other device. (I guess the worse case scenario is to have Mobo replacement :) ?).

---------- Post added at 01:43 PM ---------- Previous post was at 01:38 PM ----------

Thanks Prabhu for your passion and effort to help solve this case. It feel good that we have a small group working together and supporting one another to find a solution and it feel good that way :). Some people have thrown in very good suggestions and tools for us to trouble-shoot so far.

About the -c option I see in some post that effort trying to fix the faulty area does not have any results. It just freeze when trying to fix the error. So I guess we should now just try to avoid the faulty area and see how it goes first.

cheers,
[Galaxy Note GT-N7000 General] uggies:
Ok that worked out :) Now the same thing happens for the 10th partition... should I resize it as well?

Cheers to you too Forest1971
[Galaxy Note GT-N7000 General] forest1971:
for the 10 now I suggest it goes from 900 to 2099.

see if it works.

Edit: No I Forgot it. Actually you should go for 2110 to 3322.

Since you have tried 1174 to 2100 and it does not work.

If the above does not work then try: 2510 - 3322
[Galaxy Note GT-N7000 General] prabhu1980:
Forest1971

The Google Engineer also speaks about full wipe as a solution for this.

He says he has to find out if he can share the tool.

One thing I can tell you is that we are on the right direction. But we have to find a tool for the arm processor.

Your idea of repartition is great.

I am waiting to see how it works.

But any idea of tool for full wipe ??

I think we have a messed up filesystem when the wipe command is issued in CWM.

or By ODIN.

Hence we have to have an entirely different tool which can wipe from scratch.

Like we do a quick format and complete format.

the formating should take care / repair the bad sectors and store it in the table, like scandisk works for windows.
[Galaxy Note GT-N7000 General] uggies:
1174 - 2100 : failed at 1%

2510 - 3322 : failed at 85 % (? WHYYYY)
[Galaxy Note GT-N7000 General] forest1971:
That operation is quite complicated then you have to rebuild all partition and then flash bootloader, kernel,...Also there maybe also X-loader before bootloader and some hidden partition we do not know what it hold. I guess only some top experts in Note forum can attempt with that...and may also need support from the the company...

---------- Post added at 02:23 PM ---------- Previous post was at 02:21 PM ----------

Because there are faulty blocks in those areas.

Now please try 2000-3000
[Galaxy Note GT-N7000 General] uggies:
Does not even show up percentage and promts error message. So I just keep try this and find non-faulty area?
[Galaxy Note GT-N7000 General] forest1971:
Try 2400-3100

If it does not work we just have to rm 11 and use some space of the sdcard (ums).

The the case from drnull for your information some guiding light:

Quote from drnull:

-----

EDIT:

I'm still playing with parted and creating different sized partitions. It seems anytime I make a partition down into the 1070MB-3070MB range, it locks up. I.e., the following parted commands all lockup:

Code:

mkpartfs DATAFS ext2 1070MB 3070MB

mkpartfs DATAFS ext2 1090MB 3070MB

mkpartfs DATAFS ext2 2090MB 3070MB

But this one worked:

Code:

mkpartfs DATAFS ext2 923MB 1066MB

But it's way too small.

So now I've tried removing 11 which was:

Code:

11 3070MB 15.4GB 12.4GB fat32 UMS

And giving 10 some of that "good" region of the MMC, and giving 11 back the rest:

Code:

mkpartfs DATAFS ext2 3070MB 5217MB

mkpartfs UMS fat32 5218MB 12.4GB

That seemed to work.

--------

unquote
[Galaxy Note GT-N7000 General] uggies:
Finally, I managed to get datafs !!!!

I used 'print' command just to check, but for some reason, factoryfs has no file system? maybe I should do rm 9 and do the process again?
[Galaxy Note GT-N7000 General] prabhu1980:
Forest1971 can you please issue a command to check only bad blocks and log into a log file.

I am back in an hour to discuss about other tools and similar issues faced.
[Galaxy Note GT-N7000 General] forest1971:
Yes, good progress. cheers! You may also try to have 281 to 999 or to 1100. May be it works then will have some more space for factoryfs.

---------- Post added at 02:42 PM ---------- Previous post was at 02:41 PM ----------

Hi Prabhu: I only know the check command under parted. But drnull has wrote he got it all freeze when the try to scan and fix the fault. So I think will not try with that approach. cheers.
[Galaxy Note GT-N7000 General] uggies:
Finally everything is in place.

Before I flash anything, can you please check if factoryfs and datafs looks about right?
[Galaxy Note GT-N7000 General] forest1971:
Yes, it looks good :). The name of partition is now in lower case letter. Shouldn't be a problem but take note of that in case.

Please noted that you have only 610mb for the system. It will hold most of roms though.

I guess someone mention abyssnote 3.9 is a good kernel. You should go for that one.

than try to see if computer can mount sdcard. In that case I guess better install rom from cmw (after abyssnote has been install successfully). I guess maybe try with rocket rom or some other custom gb roms first, before trying with stock gb.

We have gone quite some distance.
[Galaxy Note GT-N7000 General] uggies:
... What the hell. I cant flash kernel via odin now ....
[Galaxy Note GT-N7000 General] anilisanil:
Great going guys. It is high time you change the title of this thread to something more meaningful now!!

---------- Post added at 01:34 PM ---------- Previous post was at 01:32 PM ----------

What is the error message? Try flashing only the PIT first, may be you want to try flashing the boot loader too.

Never mind, first tell us the symptoms.
[Galaxy Note GT-N7000 General] forest1971:
No do not mess with PIT.

try to find a zip file kernel and flash it through the current cwm.

---------- Post added at 03:10 PM ---------- Previous post was at 03:06 PM ----------

Or try again with odin and with another kernel tar file somewhere. But do now use PIT since it will reverse partition to original and undo our work.

---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------

What is the error message? Try flashing only the PIT first, may be you want to try flashing the boot loader too.[/QUOTE]

From my reading we should try not to flash bootloader unless it is necessary. Since if thing goes wrong with bootloader will cause the device to unbootable and will need JIG to boot. That is complicated.
[Galaxy Note GT-N7000 General] anilisanil:
OK. But if we changed the partition tables, it is kind of obvious that we will not be able to flash like before, right?

I mean how does the Odin knows where and how to write to? Did we do anything to tell the system that the new partition is so-and-so?
[Galaxy Note GT-N7000 General] forest1971:
Hi: I guess the number and name of the partition is still the same so it should be recognized.

Still. I would suggest using cwm to flash since we have had problem with flashing odin.

Abyssnote is originally packed for cwm so it is more convenient.

Links for download abyssnote, just incase.

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

cheers
[Galaxy Note GT-N7000 General] uggies:
First trial on flashing kernel, the green bar went up to the end, but it just did not finish. So I unplugged and reboot into download mode

Second trial, flashed with no problem.... LOL sorry

And now I am flashing Stock GB ROM without PIT file but only PDA. Wish me luck please :)

UPDATE: It is still stuck at the edge of factoryfs... just like before. DAMM !!
[Galaxy Note GT-N7000 General] forest1971:
Try to flash rom with CWM. NOw you have gb kernel so it is safe to flash using cwm.

Also I was also suspecting the abyssnote kernel in the tar format not sure it is a good one. I think better download a abyssnote kernel in zip format and then install it through cwm.

I have downloaded abyssnote 3.9 from the site and attached in the post. Hope you will give it a try with cwm.
[Galaxy Note GT-N7000 General] prabhu1980:
Dear Forest1971

I understood why u didnt go for mk2efs.

Thanks ..

But in case we are not out of this by resizing I recommend to format the partition using a low level command.

mke2fs -t ext4 -b 4096 /dev/block/mmcblk0pxx

and before trying this I would suggest Logging into a file the result of scandisk.

We may need a brave guy to test this as there is a case of freeze.

Forest1971 : I have a basic query.

a) Where are the partition information stored ??

b) is there any command equivalent to debugfs in android.

c) Bad Blocks when found the command issued is to save the data. Hence it might have freezed failing so.

d) I think We need a low level format wipe as indicated above with block size and complete restructuring.

Please throw light.....

---------- Post added at 09:41 AM ---------- Previous post was at 09:37 AM ----------

Forest1971 :

Please also Let me know if the MBR is stumped.

Normally if problems are like this, the MBR has been taken for a ride.

Sorry If i am not framing my queries properly.

Read this http://www.techrepublic.com/article/saving-and-restoring-the-partition-table/1055302

and this ...

http://askubuntu.com/questions/18826/is-it-possible-to-reset-the-badblocks
[Galaxy Note GT-N7000 General] forest1971:
We still have the last option to resize sdcard and use some of that space for factoryfs and datafs (which drnull have done successfully to recover his phone).

I do not have clue with the other options yet but guess other members are also attempting to work out?
[Galaxy Note GT-N7000 General] uggies:
Yessssssss it finally boots into cm9 !!!!!!!!!!!!!!!!!!

Holy fuuuuuuuu !!! I cant explain how excited i am!!!! 2 full days of working !!!!!!!

Omfg thanks heaps especially forest1971 !!!!!!!!!!!

Wowowo i still cant believe this

Update : I dont know why ... but it freezes every 5 seconds and I have to reboot every time.... BUT I AM STILL EXCITED

Update 2: I can see that it freezes everytime its preparing my internal sd card... is it ok to wipe sd card?
[Galaxy Note GT-N7000 General] stoney73:
Nicely done to you and Forest1971, been following this thread since it began. :)
[Galaxy Note GT-N7000 General] forest1971:
Great Job! WOW!

I am very happy too :D.
[Galaxy Note GT-N7000 General] uggies:
Is it Ok to wipe /sdcard ? I cannot mount SDcard even in recovery.
[Galaxy Note GT-N7000 General] Robotu:
Great job guys!!! Ive been watching you, this is a proof that there is a solution but the the profys prefer to ignore that. Ive been one thanks to each one in this topic.
[Galaxy Note GT-N7000 General] forest1971:
That can be the issue with the rom. I have read through many thread which user complaint of not having usb storage mode recognized which is because of many reasons of rom design and some checks somewhere.

I actually would like to recommend go back to a more stable gb rom such as rocket, darky... or stock before attempting with cm9 (unless you have been using c9 for long time now).

So that is an issue that require different intervention specific to the rom. The respective rom thread often give the answers to those problem.

How about the problem with reboot?

cheers
[Galaxy Note GT-N7000 General] anilisanil:
So here comes the Phoenix!!

Awesome people!!

Now please change the thread title.
[Galaxy Note GT-N7000 General] uggies:
It keeps on rebooting because mounting sd card fails.

I once tried to flash darky ROM 3.4.1, but installation stopped and the phone rebooted itself. I will have a go again.

Formatting /sdcard wouldnt be harmful would it?

P.S. What does /efs do? I cannot mount this on recovery
[Galaxy Note GT-N7000 General] prabhu1980:
He is our Neo

Forest1971 kudos to u.
[Galaxy Note GT-N7000 General] anilisanil:
EFS has the IMEI number, serial number, mac addresses of your network components among other things. Without that your phone would be like Jason Bourne in Bourne Identity.
[Galaxy Note GT-N7000 General] forest1971:
With GB kernel it is safe to format card. But the problem of mounting is often with the rom. So give it some try.

By the way which kernel have you been using right now?.
[Galaxy Note GT-N7000 General] uggies:
Would there be any major problems if I dont have this part mounted?

By the way, what is your opinion on wiping /sdcard on recovery?
[Galaxy Note GT-N7000 General] uggies:
I was on Abyssnote kernel, but since now I am on CM9, it cm9 i guess.

I will install Abyssnote kernel back and then install the Dark ROM and see how it goes.

Stay tuned
[Galaxy Note GT-N7000 General] anilisanil:
Yes you could do a wipe while on any GB kernel or official CM9 kernel.
[Galaxy Note GT-N7000 General] forest1971:
Should wipe while using GB kernel.

Avoid anything ics at the moment. Please
[Galaxy Note GT-N7000 General] uggies:
So far, I have flashed Abyssnote kernel via odin and then flashed darkrom via CMW.

It was all running ok up unill the last part : installing extra apps ...

Then it promted a message : error in sdcard/darkrom3.4.1 Installation aborted.

Might have to try and re download the ROM

Update: by the way, is there anyway to fix the efs part? that might be causing the problem..

Update 2: Tried wiping /sdcard on recovery and it promted done message, but my sdcard data remains unchanged.. LOL

NVM. It turns out that it wipes out external storage data.... not internal ....
[Galaxy Note GT-N7000 General] anilisanil:
You can try formatting options from advanced or mounts and storage
[Galaxy Note GT-N7000 General] prabhu1980:
Uggies : Can you add Super Bricked in the post header to catch more attention ...

You have your Internal SD and External SD.

Can I know what you are refering to ??

Edit : Oops Anilisanil is faster on replies. I am a lazy goose.
[Galaxy Note GT-N7000 General] uggies:
There is no such option ...

Done :)

And I meant internal sdcard
[Galaxy Note GT-N7000 General] forest1971:
It is ok to wipe external. That mean you have deleted the data on your sdcard.

But please refrain from further wiping and do not wipe the internal sdcard.

Follow the rom installation carefully from the respective rom site. Then you should be safe.

Also I guess you should now take time, read more about the rom you will use and take one step at a time to fully recover your Note.

Cheers
[Galaxy Note GT-N7000 General] JamieD81:
i really wish people would stop calling "SOFTBRICKS" superbricks, a superbrick is something we cant fix yet, a softbrick is what this fix's.

got my hopes up :( ohwell back in the box it goes LOL
[Galaxy Note GT-N7000 General] anilisanil:
Did you even read through?
[Galaxy Note GT-N7000 General] prabhu1980:
Remove your SD Card and let us know what is happening !!!
[Galaxy Note GT-N7000 General] Robotu:
Yes man, that was a good one, that is what i felt from the beginning, that this is only a soft brick.
[Galaxy Note GT-N7000 General] prabhu1980:
Jamie You are out of this thread.

Please read through and let us know ur comments.

The portion damaged by the EMMC BUG was called as a Superbrick.

Forest1971 and Uggies has been successful in a workaround this issue.

You call it as a SOFT HARD AND SUPER AND new names like Supreme.

To us Brick is a Brick and we try to solve it listening to others.

I hope you will excuse us if we were wrong

!!!

But for now emmc bug has a work around.....

Robotu :

I think till problem is solved a super brick is a super brick.

If one puts efforts to solve it and after it gets solved we call it as a soft brick.

Hmm...Not good ....
[Galaxy Note GT-N7000 General] JamieD81:
yes i read post #12 through, now the title of the thread is even misleading to us with real superbricks rather then the softbrick that was fixed here.

super bricks have no access to cwm no access to adb, no access to downloadmode. hence SUPERbrick.
[Galaxy Note GT-N7000 General] forest1971:
This is the XDA highlight article about EFS on Samsung device and it has link to download the application for backup those important information.

I guess it is still there in your phone. Then use the tool to back it up.

http://www.xda-developers.com/android/backup-and-restore-your-efs-folder-on-samsung-devices/
[Galaxy Note GT-N7000 General] anilisanil:
Oh like that. That is your definition.

As per Entropy (who coined the word) a Superbrick is something whose eMMC is fried due to I/O bug(essentially locked up emmc or a particular partition going berserk). Because of this, even though one might have access to download mode and CWM, we cannot write to /factoryfs because the partition is corrupted.

Until recently, there was no fix for this, not even JTAG. But these guys tried repartitioning and succeeded. I am not too sure what has to be done if your download mode is inaccessible.
[Galaxy Note GT-N7000 General] prabhu1980:
Please read through the entire thread, he was stuck at factoryfs.img
[Galaxy Note GT-N7000 General] Robotu:
Guys, we should not get stocked in definitions and names, but rather concentrate to solve this issues. Though we shoulld use another name for this issue to give back a hope to all guys that bricked there phone, and for no other reasons...
[Galaxy Note GT-N7000 General] forest1971:
I guess maybe name it: how to fix the problems caused by faulty partitions?

Not so important though. Let the Mods decide on a suitable name :).

cheers,
[Galaxy Note GT-N7000 General] prabhu1980:
Yep !! I will coin factoryfs.img partition issue as a "Supreme Brick" or "Forest Unbricking process for a Supreme Brick"

Hope noone will come and kill me for coining this.

Ha ha ha ! Very happy for you Forest1971.
[Galaxy Note GT-N7000 General] JamieD81:
thats a waste of my time when all the info anyone needs to know is in post #1 and #12 nicely summed up.

what you guys have is a SOFTBRICK its been known as that since samsung android phones came out. why entropy decided to call it something different in beyond me.

it should have just been left the way it has been since sgs1 came out

SOFTBRICK *what you guys have*

HARDBRICK *what i have and some others*

less confusion.
[Galaxy Note GT-N7000 General] uggies:
Just realized that emmc is the internal storage..

But I have been told that wiping emmc would result in complete brick ... damm i cannot risk that AGAIN.

Btw can anyone find a stock or safe gb ROM that can be flashed through cwm? I cannot find it :( I must be blind.
[Galaxy Note GT-N7000 General] anilisanil:
What do you call the bricks that resulted from angelom's fiasco?

Edit: Samsung replaced my MOBO, because they could not resurrect the phone even with a JTAG.

I had a softbrick as per you, with access to download mode and recovery. May be you should make yourself more informed about the issue, before jumping to any conclusion at all!
[Galaxy Note GT-N7000 General] JamieD81:
dunno i wasnt dumb enough to jump on it :P

were they revived bricks or dead bricks?

easy to categorize them

if its completely un-usable *black screen no matter what button combo or jig you use* Its a HARDBRICK

if you can get to download mode or recovery with a chance to save it, its a SOFTBRICK.
[Galaxy Note GT-N7000 General] prabhu1980:
ANIL HE MADE IT CLEAR

I LL ELAOBORATE IT FOR YOU.

SOFT BRICKS - If you can solve it

HARD BRICKS - If you can't - Spend $200 at SSC.

Simple ANIL ! Lets wait for some MODS and DEVS to see this thread.

His #1 post clearly states the issue.

But Mr Jamie,

If you are hard bricked and u r on ur way to SSC why dont u give a try with the adb shell.

I know u will say that adb shell will not enter (Have you tried .. I did it once ....Jig helps .....)