yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] hg42:
emmc-scanner update: signed zips (hopefully)

please look for update of emmc-scanner thread:

* the zips should now be signed.

* those with stock recovery, please report failure and success.
[Galaxy Note GT-N7000 General] aDEO:
Thank you hg42,

I do really appreciate your efforts!

The output from stock recovery was: Signature verification Failed.

Then I have flashed the CWM and "120818-171018-emmc_scan_all_partitions_once.zip" didn't find bad blocks.

However I still have some "power button issues" (on hold, the power menu did not appear, but the phone just turned off). This strange behaviour is only with stock ICS, but not with stock GB rom.

Regards,

aDEO
[Galaxy Note GT-N7000 General] hg42:
so I have to dig further into the signing. I assume I have to use test signatures instead of my own keys.

I think it was mentioned somewhere that this might have to do with problems in efs partition.

There also was a solution.

EDIT: in this post

Apart from that, do you have a generic IMEI now?
[Galaxy Note GT-N7000 General] hg42:
(this is an answer to a post in the emmc-scanner thread)

You can look inside the txt file for the PIT (here N7000_16GB_Q1_20110914-patched-regain-0262144-kB.pit).

There the lower section has lines like this:

...
10 MODEM 516096 32768 = 16384 kB
unused 548864 5414912 = 2707456 kB
11 FACTORYFS 5963776 1744896 = 872448 kB
12 DATAFS 7708672 4194304 = 2097152 kB
...

look at the "unused" line (which is your lost space, so the last number tells how much you loose, here 2707456 kB).

The bricked area must be completely inside it, so no bricked block will be used ever again.

The blocks are 512 here, so the unused area runs from 548864*512=281MB up to the start of the following partition 5963776*512=3053MB.

So this PIT isn't ok, because 3053MB < 3065MB.

So the standard pit has to be used:

unused 548864 5939200 = 2969600 kB
11 FACTORYFS 6488064 1744896 = 872448 kB

6488064*512 = 3321MB which is ok.

281MB--------------unused--------------------3321MB
834MB---------brick-----------3064MB

These conditions have to be met:

StartOfUnused < StartOfBrick and EndOfBrick < EndOfUnused
[Galaxy Note GT-N7000 General] Mario1968:
Hi hg42, I would to suggest to all the user having this kind of issue with the power button and the lock screen, to backup their EFS partition before to apply this fix and verify that their own Imei was exactly the same as before the issue.

Thank you for your work on this brick bug fix!

PS I've never bricked my S2 (for now:D) but I'm very interested in the fix you have developed.:thumbup:

Inviato dal mio Galaxy S2 con Tapatalk2®

XWLPF Stock

Siyah 4.1 beta 6

Jkay V14.1
[Galaxy Note GT-N7000 General] aDEO:
Dear hg42,

I have checked the IMEI last night and it was corrupted (starting and ending with zeroes). However the suggested fix from Odia didn't fix anything in my case:

# echo -n ON > /efs/imei/keystr
# reboot

Then I restored my old EFS backup with kTool from the Google Play as follow:

1) I have restored the IMG format of my EFS backup and it didn't fix my issues at all (same wrong IMEI with zeroes + power button instant shut down + missing lock screen)

2) Finally I have restored back the TAR backup and after the restart - WOW!!! Everything was at its place! :)

These days I will play a bit more with the your scanner to find out the best beginning and end of the bricked area. So please, let me know if you want me to test something.

Thank you very much for your hard work!

Best regards,

aDEO
[Galaxy Note GT-N7000 General] tannykim:
I do have same IMEI and I do not have any issue with IMEI.

However, I am still have issue with random freeze and lock screen does not work.

Anyone have same issue with me?
[Galaxy Note GT-N7000 General] hg42:
Did you try the fix Mario posted?

I think it is unrelated to a corrupted/generic imei.

But as Mario said, run an efs backup first
[Galaxy Note GT-N7000 General] Mario1968:
Hi tannykim, have you try the fix from XDA Link?

Regards

Mario

Inviato dal mio Galaxy S2 con Tapatalk2®

XWLPF Stock

Siyah 4.1 beta 6

Jkay V14.1
[Galaxy Note GT-N7000 General] tannykim:
I can not understand Mario.

Why you keep saying I can find way to fix this issue with that link?

I read and search all EFS associated issue, and everything related with IMEI and Baseband...... I do not have any issue once it turn on. However, if I try to use Note and apps and dialer and some more work with Phone it freeze and stop. Do you still believe this happen because I have issue with EFS?

I know you try to help but if you do not have exact information please do not throw that. I had bad experience with this and I got bricked since someone just throw un-confirmed information.

Thank you
[Galaxy Note GT-N7000 General] aamirleo55:
my Galaxy Note is bricked, i cant access to recovery and download mode.

what should i do now ? and i dont know how to access download mode via adb.

plzz help me in it
[Galaxy Note GT-N7000 General] tannykim:
You case will be super brick which can help by JTAG Brick repair.

However, if you did not have binary count, then you can send that to Samsung service.

If you had custom ROM and binary count you may not get service from Samsung.

In that case http://mobiletechvideos.mybigcommerce.com/ they can help you
[Galaxy Note GT-N7000 General] hg42:
the post was in the emmc scanner thread, but I think it belongs to this thread.

that's a behavior I can only speculate about.

My Note's emmc brick has constant start and end addresses (MB at which block is located), but I think at the beginning of my live with the brick it changed start address once.

There are some reports of other people who have occasional freezes after reviving their phone.

So there might be a random process involved, perhaps the assignment of bad blocks by the wear leveler, that's where the brick is to be located.

This assignment process should only be triggered by write operations. That may be the reason why the "indefinitely" partition scanner tool can perform many cycles without any freeze, but the problem isn't gone away (some report so).

That said, I guess, I would use the find_brick_end tool like you used the find_brick_start tool. I assume there will be changes to start and end address for some time. Hopefully the addresses stabilize after some time (no address change).

I guess, between the scans should come write operations to internal sd.
[Galaxy Note GT-N7000 General] aDEO:
Dear hg42,

Thanks to your scanners I was able to find the start and end of the new bad blocks hole :(

emmc_find_brick_start : 2147MB
emmc_find_brick_end : 3222MB

Which means that I have to create a new unused hole as follow:

Start = 2198528
End = 3299328
Size = 1100800 (1075MB)

Now I am planning to correct current PIT (i9100_u1_02_20110310_emmc_EXT4-patched-big-bricked+0524288-kB) by using your pit structure.

So I have to offset partition-block-start and partition-block-count in the way that the current affected partition and all partitions after it to be behind that hole. Is that correct?

Best regards,

aDEO
[Galaxy Note GT-N7000 General] Mario1968:
Hi tannykim, the fix I've posted is ONLY for the lock screen and power button issue, not for the occasional freeze you have.

Sorry if those posts can't help you, good luck to revive and fix your device.

Mario

Inviato dal mio Galaxy S2 con Tapatalk2®

XWLPF Stock

Siyah 4.1 beta 6

Jkay V14.1
[Galaxy Note GT-N7000 General] hg42:
I think *your* information is missing exactness.

I also asked you *if* you have applied this fix or not.

You didn't really answer. From your posts I got the feeling you are thinking the thing doesn't have to do with your problems.

I think you *may* have more than one problem. One of them (lock screen) may have to do with this issue.

This fix

echo -n ON > /efs/imei/keystr

does nothing but write the two letters "ON" into the file.

So you should simple confirm

* if the file exists and has proper permissions (rw-rw-r-- 1001:radio)

* if the file contains only the string "ON", size should be 2 Bytes

This doesn't hurt.

But if these conditions aren't fullfilled, you should probably apply the simple fix.

If you already checked this, you could have answered with your results.

Note, this not directly has to do with having this or that IMEI.

Apart from that, having the same IMEI as before the brick doesn't mean it's the correct IMEI.

You should compare your current IMEI against the stickers (under your battery, and I think also on your phone's package).

Also, EFS contains many files, each of which can have several mysterious effects (not many people seem to know about, including me).

So I would check if the files look reasonable.
[Galaxy Note GT-N7000 General] hg42:
I am so sorry...I told bullsh*t here:

the numbers are block counts, with each 512 byte for this phone.

Unfortunately I used kB in calculatioons, which was plain wrong.

We see the 512 byte size e.g. on this line:

11 FACTORYFS 3342336 1744896 = 872448 kB

because 1744896 * 512 = 1744896 * 1024/ 2 = 872448 kB

The first MB after the brick is at 3065MB which is block number 6130000.

Start of bricked area is at 834MB which is block number 1668000.

N7000_16GB_Q1_20110914-patched-standard.pit is at 6488064, which is ok.

The next smaller one is N7000_16GB_Q1_20110914-patched-regain-0262144-kB.pit which has 5963776 which is in the bricked area, so this pit cannot be used.

I changed the post above to be correct.

@biostar: So your former PIT was wrong...
[Galaxy Note GT-N7000 General] tannykim:
I do not know how can I put my issue and information with more exactness.

I did states clearly I do not have any issue with Lock button.

Also, I read and search all thread about EFS, and there will be some un-known conditions of this issue but current issue is related with lock and power button function and mine does not have any issue with this.

Also, I check my EFS file and it is fine.

Thus I strongly believe my hang and random freeze is not related with EFS.

Thank you
[Galaxy Note GT-N7000 General] Mario1968:
You have posted that issue in previous post and now is gone?

I'm not understand you:confused: but if this issue is not your case simply ignore my suggestions.

Regards.

Mario

Inviato dal mio Galaxy S2 con Tapatalk2®

XWLPF Stock

Siyah 4.1 beta 6

Jkay V14.1
[Galaxy Note GT-N7000 General] tannykim:
As you put RED, lock screen does not work, which mean it lock and lock screen hang and does not come out.

I did not states Lock button does not work.

Please do not waste your time.
[Galaxy Note GT-N7000 General] eecmp:
thanks it work for me , excellent !!!!!!!!!!:laugh:
[Galaxy Note GT-N7000 General] Mario1968:
I think someone else can fix their issues with the suggestion I've post, then I'm do not waste my time at all, maybe you are wasting your time writing this kind of uninformative posts.

@hg42

Sorry for this kind of post.

Mario

Inviato dal mio Galaxy S2 con Tapatalk2®

XWLPF Stock

Siyah 4.1 beta 6

Jkay V14.1
[Galaxy Note GT-N7000 General] MohElShafei:
Dear hg42,

Yesterday, my SGN was insane, mad, and really acting in a very very strange behavior. Therefore, I though it would be better to report all the issues I faced, hopping that it might help you while developing solutions.

I used the Partition Scanner app (the latest files you updated) (twice), and the result every time was: It hangs at the 803 MB from start, and from end, it hangs at 6077 MB. Therefore, I repartitioning my SGN using the (N7000_16GB_Q1_20110914-patched-big-bricked+3145728-kB) file to the following scheme:

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

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

I'm now surly out of bad blocks and the FACTORYFS, DATAFS, and UMS partitions are in clear blocks, even though;

random restarts, freezing, and hanging all the time

The surprise that nearly made me go CRAZY is that I was trying to wipe the UMS partition from the 4pda_kernel.tar kernel, and every time I wipe the UMS partition it says that the formatting is successfully done, but when I try to install the ROM and log in to check that there are no files in the UMS partition, I was shocked that all previous ROM files are there!!!!!!!!!!!!!!. I wiped almost 6 times using this Kernel, CM9 Kernel, thor-kernel-v0.14-GNOTE.zip Kernel, and AbyssNotekernel42CWTouchOriginalLogo Kernel, and every time, it says done successfully, and when I check. trarararaaaaaaaaa .. ALL FILES ARE STILL THERE !!!! .. as I'm doing nothing!!!.

Note: Just to clarify things to you, I was formatting the UMS, not the SD Card. I know that there places are changing from Kernel to another, but I know I was formatting the UMS. And to make sure that I'm correct, I removed the SD Card, and I was formatting everything. and the surprise was still there ... all files still there!!

I used different .PIT files, and the files were still there!. The only thing worked for me is that I removed the UMS partition using the rm command, then created ext2 instead of fat32, it stopped during that process, then I created it again as a fat32. Now and only now .. it is CLEAR !!!!!!!!!! .. very very very strange!

Is there any explanation of what my phone is doing? .. I begin to feel that Bricking is not only about Bad Blocks.. The phone itself becomes CRAZY and does not follow any rules. I feel it is something related to the Chip Firmware that made it that crazy.

Thanks a lot for your efforts hg42, and sorry for disturbance, but I thought what I faced needs to be reported :)

Kind regards,

Mohamed
[Galaxy Note GT-N7000 General] hg42:
well done!

not needed if you use the partition scanner...(all-partitions-once)

so you're with isitme and tannykim

strange!

what do you mean with "previous rom files"?

The rom installs to system, so which files do you mean?

anyway the partition should be smty after formatting.

did you check if the repartitioning worked for each pit (via parted)?

I think, emmc brick is about damaged administration structures in the flash chip.

This probably can create very mysterious behavior.

you're right, very useful information
[Galaxy Note GT-N7000 General] hg42:
perhaps you can also try the new write scanner, would like to see if it freezes. Try at least 64000MB.
[Galaxy Note GT-N7000 General] MohElShafei:
First of all thank you for the replay.

I flashed a CM9 rom before. It was working with 50% hanging, but suddenly it hangs rapidly and refused to start again, so I thought I must first format all traces of this rom in all partitions before start installing a new one. So after several formats, all the old ROM files in the UMS partition were there intact !! until I changed the file system type to ext2, then going back to fat32.

Yes, that what I was doing every time. I was always checking with the ported command to see that I'm ok with the new partition scheme.

I'm running the new app now. In addition, I removed my internal SD Card to make sure that I'm checking the internal memory. Will report once it finishes.

Thank you.
[Galaxy Note GT-N7000 General] MohElShafei:
Hi hg42,

I left the new write scanner running till it reaches 240000 with no errors, then I restarted the SGN myself as it appears that it does not show any errors and it is just running. What do you think??

Regards,

Mohamed
[Galaxy Note GT-N7000 General] vfusion393:
Hello hg42,

I tried to update with mobile odin to the latest DXLR5 4.04 from ICS-LRG 4.04 / CF-LRG Kernel. Phone rebooted after upgrading but stuck at Samsung Logo.

Tried to recover image with CWMR but to no avail. Also tried various methods to flash phone with other stock ROMs (GB & ICS) with PC Odin but always stuck at Nand Start Write. Long story.....phone bricked.

Finally, use your standard Pit File and managed to flash the ICS-LR5 stock. Have been using the phone for the past 2 days without any negative effect with Speedmod Kernel k3-13.

Lost about 3GB but I can live with that, as it saves me the hassle to go to Samsung Service to get a replacement.

I would like to thank you and also others for taking the time to share your knowledge with us. Thanks again..
[Galaxy Note GT-N7000 General] hg42:
I don't see exactly why changing the file system first made it work. May be the format failed (unexpected and uncaught by the formatting program) because of the former contents.

Such situations often trigger paths through the program code, which never occur in standard situations and are therefore untested or even never thought about.

Which kind of format did you use? recovery? parted? some mkfs*?
[Galaxy Note GT-N7000 General] hg42:
The tool is very speculative.

I wanted to get the wear leveler busy to trigger some new behavior from which we may deduce more understanding about the internals of the emmc problem.

I also hoped to trigger some self healing process of the wear leveler (e.g. rewriting of structures can fix problems sometimes). But this was even more speculative.

But please test thoroughly before shouting hurrah...

It may be an intermediate effect.
[Galaxy Note GT-N7000 General] kirta89:
Help :(

Please Help :(

I have download rom (3.2) for my region. I have download pits-N7000_16GB

I start Odin, Then I add "N7000_16GB_Q1_20110914-patched-standard.pit"

and my Rom (Please See The attach file)

but in my phone screen comes this error:

--Coping media files...

--Wiping cache...

Formating / cache

Cache wipe complete.

--Updating application...

E: Failed to mount /data (Unknown error: 0)

E: install_application_for_costomer: Can't mount /data

your storage not prepared yet, please use UI menu For format and Reboot actions

-

copy aplication failed

Please help me :(
[Galaxy Note GT-N7000 General] MohElShafei:
I used the Recovery to format the partition, go into the recovery mode, then from there I wiped the emmc.

So do you need me to start working with the SGN - as it is normal - after the scan I did, and see if it hangs again??. Till now and since yesterday, it didn't hang at all. maybe that scan fixed it. Wish it stays that way. Will report once anything occur

Thanks.

Mohamed
[Galaxy Note GT-N7000 General] unclekeg:
one click fails even after your unbrick procedure

Hg42 Thanks for all your help. I followed your simple instructions on how to install regular pit file and rom eg30. It odins just fine. reboots fine. e4gtauto.exe works fine, ie option a and c work like champs. I am rooted wjth cwm. reboot into clockwork and use your zips to check partions and they pass fine. format cache and clear data... reboot. try to execute one click full el29 restore and it fails... now phone will not boot again... have to reodin yiur pit and rom and start over.... what am I doing wrong? should one click not work?

Thanks again,

keg

UPDATE: After repitting and odin eg30 rom. i installed some apps to write to the partition (a theory I got from another thread) . i then rebooted into CWM and formatted partion, system and emmc. Rebooted into downloading mode and attempted to odin the official samsung D710USEL29_D710USEL29_SPR.zip which contains HOME_SPH-D710_CL852097_user.tar.md5. Result was failure . please see log for any clues. Why can't I get any rom to install?

<ID:0/006> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> HOME_SPH-D710_CL852097_user.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/006> Odin v.3 engine (ID:6)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Get PIT for mapping..

<ID:0/006> Firmware update start..

<ID:0/006> boot.bin

<ID:0/006> NAND Write Start!!

<ID:0/006> Sbl.bin

<ID:0/006> zImage

<ID:0/006> factoryfs.img

<ID:0/006> hidden.img

<ID:0/006> recovery.bin

<ID:0/006>

<ID:0/006> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Galaxy Note GT-N7000 General] hg42:
sorry, please read the thread starter first, it should be obvious, which steps you ommitted...
[Galaxy Note GT-N7000 General] kirta89:
I'm trying this meethod:

* (re)boot to download mode (hold Vol-Down + Home + Power until you arrive there [20-30 seconds], then Vol-Up)

* flash a patched PIT in Odin

* flash a known good ROM via Odin (especially not a faulty stock ICS ROMs)

* reboot into recovery (hold Vol-Up + Home + Power until you arrive there [20-30 seconds])

* check the partitions (see section "checking all partitions" below)

* switch off the phone (something like "power off" in recovery)

* remove external sdcard (to be sure not to format it afterwards)

* boot recovery (hold Vol-Up + Home + Power until you arrive there [20-30 seconds])

* format cache

* format data

* format internal SD

I have download

>> pits-N7000_16GB.zip (There is many PITS-which one can I use?)

and

>> 3.2 Rom (N7000DXLC2_N7000OLBLC2_XEV)

I wonder what is: "DataWorkShop-pit-structure.zip" File?

is it important for this ^ method?
[Galaxy Note GT-N7000 General] hg42:
thanks.

Yes, use it as normal and pray :)

Would be nice, if it works now, I'll keep my fingers crossed.

In Germany we would say:

"man soll den Tag nicht vor dem Abend loben"

which I would translate to (word by word):

"don't praise the day before the evening",

leo translates it to:

"don't count you chickens before they hatch"
[Galaxy Note GT-N7000 General] hg42:
did you format these three?

If /data cannot be mounted, you seem to have a problem with "format data"

Use the partition scanner to determine start and end of brick.

Then select appropriate pit.

DataWorkShop can be used to visualize pits. Not needed.
[Galaxy Note GT-N7000 General] mmola:
One would think that months after this bug surfaced no one would be dumb enough to do a factory wipe with LQ5 on a SGS2. Well, it turns out I am.

hg42, you have saved my phone. I cannot stress how thankful I am for that. Instead of trying, I will contribute what I have learned during the resurrection of my little one. Take into account that everything I say from now on cannot be directly applied to your non-SGS2 phone, and even if you have a SGS2 maybe you should not do anything based on these findings if you do not understand what they mean.

1. The standard-patched PIT file was not enough in my case. I had some bad block just past the "standard" limit, it would seem. Using the big-bricked PIT with the smallest number sufficed for me. I guess I could try to optimize the final size of my UMS partition, but I don't think it's worth the time, as hg42 points out.

2. I did not flash a stock ROM after repartitioning. I don't think I'll flash a stock ROM ever again. I instead flashed CM9 Odin version (do *not* use your CWM for flashing after repartitioning, lest you brick another ~3GB of your internal memory).

3. Flashing Odin CM9 seems to leave you with an unformatted UMS partition (/dev/block/mmcblk0p11 in my case, you can check which one is the UMS partition using adb while in recovery and parted to print the partition tables). As a result, /mnt/sdcard is not mountable, i.e. you are lacking internal storage, and trying to format it in recovery leads to error messages ("unable to mount /emmc" in my case, my mountpoints are reversed). To fix this without flashing a stock ROM:

3.1 I booted the phone into CM9 and enabled ADB root mode in the developer options.

3.2 I connected via adb as root.

3.3 I run "$ newfs_msdos /dev/block/mmcblk0p11".

3.4 Just to be sure, I restarted in recovery. Now CWM was able to mount /emmc (again, that's reversed, in my recovery /emmc refers to the internal storage. Just to be on the safe side, as hg42 has pointed out a thousand times, just extract your external SD card).

4. Reboot phone, enjoy my 9.01GB left of internal SD card. And thankful for them!

Best ;)