yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] Dryblow:
hi, on the LRQ firmware, fixed it?

p.s. sorry for my english.
[Galaxy Note GT-N7000 General] :
so cool, maybe walkthrought photos?
[Galaxy Note GT-N7000 General] friedje:
There has been a bug in mobile odin and the latest roms. It caused the /cache to corrupt and I think most flash-hangs reported lately came from this problem. Chainfire updated MO since..

---------- Post added at 08:32 PM ---------- Previous post was at 08:23 PM ----------

Somehow, i don't think so....

But then again I might be paranoid lol :)

But someone asking on a sunday where to buy the chip and if it is maybe a sandisk.. and 2 days later not only he ordered and received the chip, but also replaced and reflashed it... I have a hard time believing it in such a short timespan.

However if it's done, that would be good news for the community. If there is enough space then it could be an option to get the chip desoldered and then resolder a socket for the replacement chip.
[Galaxy Note GT-N7000 General] :
I had the mobile Odin hang with lrq... was fine with PC Odin
[Galaxy Note GT-N7000 General] fleurdelisxliv:
So ive read a few things on this is it even safe to do a factory reset?

MARBLE WHITE GALAXY SIII
[Galaxy Note GT-N7000 General] PaulF8080:
Are you insisting there is a microprocessor on the chip that executes FW even though the implementation is unknown.to you? I think we have language problem. I view a controller as logic that controls some external signals. An embedded controller does the same except the signals are internal. You can buy micro controllers(not embedded controllers) that control slow signals and they just microprocessors with a lot of I/O pins. Not all controllers have are cpus. There is exynos/arm FW on the eMMC. Surely you are not saying there is a cpu on the eMMC chip that executes FW arm code. Here is where the language comes in. Sometimes there is code implemented in the silicon, but that is call microcode not FW in my world. Even microcode is too slow for high speed signals.

I am a retired engineer who did debug for a very long time and I am sorry, I can't seem to stop. :) Please note: I always use "guess" instead of "fact"(an old debugger habit). I am glad my i717 is safe, thanks.
[Galaxy Note GT-N7000 General] :
I am pretty gullible I guess
[Galaxy Note GT-N7000 General] PaulF8080:
It's the Sanddisk guy? That seals it. Good catch! I pointed out to him that there no sector marks on a ram disk. Being paranoid explains a reply to one of my posts. You have no way of knowing who people are here, I guess.
[Galaxy Note GT-N7000 General] friedje:
Although this is off topic, Firmware = Microcode.

So I don't see the point in spending 23453455445643 posts on insisting that

we DON'T call it firmware but microcode. by definition firmware IS microcode that bridges between actual software calls and the underlying hardware.

Now it doesn't matter if this is inside a CPU, a GPU, an Embedded controller or even an Electronic Toiletflusher.
[Galaxy Note GT-N7000 General] Entropy512:
Also note that eMMC stands for "embedded MMC" - For all practical purposes, it is an MMC/SD card but in a BGA package with some additional features to take advantage of the fact that it is a fixed installation with extra pins available.

We also know that almost all SD/MMC cards on the market use embedded controllers that execute some sort of firmware (they are clearly NOT an FPGA and , as the above poster stated, almost surely not a CPLD because you couldn't fit stuff like this in a CPLD), often on a separate die from the NAND flash memory - see http://www.bunniestudios.com/blog/?page_id=1022

We also know for a fact that these chips can have their firmware updated, however the exact method of updating the firmware is unknown AND the update method is known to be unreliable/dangerous when performed in-system.
[Galaxy Note GT-N7000 General] letters_to_cleo:
Isn't the eMMC have some form of embedded memory controller that optimized to take advantage of specific NAND flash performance features, including program and read cachings? I read somewhere that it 's even possible to boot directly from eMMC... if so, then I would suffice that this embedded memory controller(block-level interface/error management and wear-leveler) is the one controlling and handling the chip itself?
[Galaxy Note GT-N7000 General] PaulF8080:
I guess I can give a technical response without revealing secrets. I was called an RTLer. RTL is register transfer logic described in a hardware description language HDL. I used Verilog HDL at the end of my career.

Here is some pseudo code that can easily be converted to Verilog:

Case of State
Idle:
Case of eMMC_cmd
Wipe:
State = InitWipe
more commands ...
end case
more states ...
end case

The synthesizer would generate tens of transistors. Why anyone would use hundreds of thousands of transistors for a cpu core and associated FW to do the same thing(interpret emmc commands) is very unlikely, but not impossible, in my opinion.

As a side note the chip I worked on also added an on chip memory controller and they just grabbed the RTL from the chip set people.

As far as the 2 hex digit chip revision, Intel would name the revisions, too. eg. 0x05 could be called "B1 step"

The only reason I brought up the FW issue is that an embedded programmer was discussing his guesses. It was very interesting to me until he got side tracked to "what if the eMMC FW got corrupted".
[Galaxy Note GT-N7000 General] musashiro:
This thing should be fixed on JB, if not on ICS
[Galaxy Note GT-N7000 General] Entropy512:
Yes. The eMMC does a lot of abstraction to hide some of the painful aspects of working directly with NAND and making it easy to work with.

Yes, it is possible to boot directly from eMMC - that is what our device does, as do all GalaxyS2 devices onwards. (GS1 devices had some raw NAND and an eMMC chip.)

As in the link above, most MMC/SD chips actually have two dies - one for the NAND and one for the controller.

And I agree with jetmarc - the wear levelling algorithms used for MMC/SD/eMMC are complex enough that it would be next to impossible to maintain as FPGA or CPLD code. All of the evidence points to an embedded microcontroller, and some of the analysis of that wear leveller patch indicates it's probably ARM.

Hmm.. Good thought, I should take a look at one of the recent JB leaks for another device, the nature of Samsung's recent patch is that they can put it in a common source repo, would be interesting to see if there's evidence of it in their binaries.
[Galaxy Note GT-N7000 General] musashiro:
recent leaks for s3 should be ok right?
[Galaxy Note GT-N7000 General] PaulF8080:
I miss technical discussions so I am having fun and learning alot from you guys, especially enrtropy. I have been on both sides of the RTLer vs. Software engineer debate so I take no offense. First, I prefer TI's definition of eMMC. http://processors.wiki.ti.com/index.php/Android_gingerbread_eMMC_booting

SRAM is embedded storage so SRAM fits the long definition. SRAM can use very low leakage transistors so static power is low and dynamic power is virtually non-existent.

I have read about NAND flash wearing out and it's work arounds. My very first thought was that wiping 16gb might have a probability of breaking more bits than the ECC can correct. My first job at Intel involved writing an ECC test. You adding the flash leveling as a reason for an on chip cpu caught me off guard. I was thinking the flash was separate(someone suggesting it had it's own die). I may get back to you.

As far as an ARM7 core. I can give you a couple of reasons for not using it. It uses a lot of power. Cell phones run on batteries. :). I also worked in HVM testing, high volume manufacturing. Every second of test time costs money when you are talking millions of chips. Getting full test coverage on an ARM7 would be unacceptable.

Since I have learned so much from entropy, I will return the favor. HDL synthesizers generate a net list of connected components, like AND, OR, flops etc. PLDs are un-synthesized ROM like blocks for things like op code decoders.

"XSR was defined by programmers and can't be implemented in RTL" was good one. I wish could still talk to some of my old coworkers. They might appreciate that.
[Galaxy Note GT-N7000 General] friedje:
S3 JB roms are unlikely to be patched, since the FW itself doesn't have this particular problem.
[Galaxy Note GT-N7000 General] :
if there is evidence other then a random person not bricking device.
[Galaxy Note GT-N7000 General] alvinasnow:
Moderator, would be better if the Title of Topic is changed now to "Discussion Forum on eMMC repair" instead of "Samsung working on eMMC brickbug Fix". Hundreds of XDA members including myself are checkin out on this Topic every monring for a possible development, which now seems a far cry. Forgive me for everything, i readily realize that Seniors owe us nothing and we are not supposed to be disrespectful, however the fact remains that a hope has kept us bound and frozen... we can't flash roms, we can't sell phones, we can't replace boards.. Gosh, i have gone way too far :P

Entropy Sir, C'mon at least revive our hopes with something :)
[Galaxy Note GT-N7000 General] PaulF8080:
I had realized I went way way off topic and had planned on stopping. Your post gives me a chance to apologize before l go. Sorry, but it was fun, though. Good luck. Paul
[Galaxy Note GT-N7000 General] dekelm8:
Hi.

I have one more N7000 to fix (own to my friend that make the same mistake like i did) with the same emmc problem.

I ordered one more chip, and after the holidays here (approx two weeks) i'll back to work and i'll make a video that show how i'm replacing the chip, and flash it with my riffbox...

(and maybe i mad a mistake when i talked about the "sector" issue, but the point was "if it's possible to make FULL format to the F*#^king emmc chip, and not just wipe the data".)

and if you don't any skills except click on keyboard.

So you can keep and write posts, and looking for solution from (Sucks) Samsung... when i fixed my phone for 70€...

So have nice day, and good luck with your emmc waiting
[Galaxy Note GT-N7000 General] Entropy512:
S3 is immune and always has been - its chip is not defective.

As far as I can tell, all Samsung devices newly released in 2012 are immune, whether due to a new generation of eMMC chips (S3 family) with new model numbers, or new eMMC firmware on an affected model (SGH-I717 with VYL00M fwrev 0x25). The Galaxy Nexus seems to be the transition point - it's the first device to receive upgraded eMMC firmware, I717 was the second, all newer devices seem to be on a new generation of eMMC models.

Interestingly, Samsung's storage/memory division is selling older chips to other companies - Acer A700 is a fairly new device but has old (defective) Samsung eMMC.
[Galaxy Note GT-N7000 General] friedje:
I wonder what they sold to Apple for their Iphone-5 :D:p
[Galaxy Note GT-N7000 General] Mario1968:
Hi Entropy512, if not exist a patch for the eMMC brick bug, but exist any full new firmware (0x25) is possible to make a patch that (after having a full dump of the new firmware) swap the eMMC firmware in sram at every boot?

Please don't flame me if this is a strange question:)

Thank you

Mario

Inviato dal mio Galaxy S2 con Tapatalk2®

XWLPF Stock

Siyah 4.1.5

Jkay V14.1
[Galaxy Note GT-N7000 General] Entropy512:
Possible? Maybe.

Do we have enough documentation to do it safely? No.
[Galaxy Note GT-N7000 General] Mario1968:
What do you mean for safely? If I ever bricked my phone I'm very happy to flash a kernel with this kind of patch (swap old firmware with new firmware in sram at every boot) to revive my phone and maybe to definitively repair (what happen if I'll do a full wipe while using new firmware in eMMC with bricked blocks? Maybe fixing those blocks?) And if this patch don't works and can't do this magic I can still use my phone without the patch and the pit method to exclude bricked blocks from partitions maybe.

Correct me if I'm wrong

Thank you

Mario

Inviato dal mio Galaxy S2 con Tapatalk2®

XWLPF Stock

Siyah 4.1.5

Jkay V14.1
[Galaxy Note GT-N7000 General] Entropy512:
If you've suffered damage already, swapping the firmware in SRAM won't help you. Swapping firmware in SRAM *could* make a chip immune - but we'd kill a ton of chips trying to develop something like that, and we already have more robust methods of protecting devices.
[Galaxy Note GT-N7000 General] Mario1968:
Thank you Entropy512 for clarifying to me this thing, but what is the robust method you've mentioned, the mmc_cap_erase disabled or what else?

Thank you again for your posts

Mario

Inviato dal mio Galaxy S2 con Tapatalk2®

XWLPF Stock

Siyah 4.1.5

Jkay V14.1
[Galaxy Note GT-N7000 General] Eric-Mod:
Hi guys, look : http://www.sammobile.com/2012/09/19...e-code-for-lte-samsung-galaxy-s-iii-gt-i9305/ ;)

Gesendet von meinem GT-N7000 mit Tapatalk 2
[Galaxy Note GT-N7000 General] kitrax59:
http://xdaforums.com/showpost.php?p=31752724&postcount=1189

;)
[Galaxy Note GT-N7000 General] Entropy512:
mmc_cap_erase disabled, also BOARD_SUPPRESS_EMMC_WIPE when building recovery/update-binaries
[Galaxy Note GT-N7000 General] NIK3SH:
Need Guidance

Hello,

My phone is running XWLPT, XXLQ6 firmware (Screenshot attached)

It is not rooted.

As well I haven't flash anything custom in it. All is official by Samsung.

I am having Android system recovery 3e (Screenshot attached).

So please suggest me is my phone eMMC is faulty and may lead to hardbrick if I do factory data reset from Settings>Backup & Reset>Factory Data Reset ?

I just want to do Factory data Reset from Settings.

I don't want to do any Nandroid Backup,Wipe Cache Partition, Root my phone or any other advanced task.

Please suggest me safest way.
[Galaxy Note GT-N7000 General] :
Refer to the following forum and run the got brickbug app to see of you are affected

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

[05.09.2012] Got Brickbug ? v1.2
[Galaxy Note GT-N7000 General] NIK3SH:
It is showing something like this...
[Galaxy Note GT-N7000 General] SpyderTracks:
So that means you have an unsafe emmc chip with the mmc_caperase command built in. The only safe method to perform wipes is to install a safe kernel such as Hydracore or phillz with mobile odin, and then perform wipes.
[Galaxy Note GT-N7000 General] NIK3SH:
Mobile Odin requires root.

And my device runs completely stock and default by Samsung, like i just purchased it...

---------- Post added at 03:03 PM ---------- Previous post was at 02:55 PM ----------

Sorry to bother.

But reading so much threads belonging to this Brick issue.

I found one comment stating that if you are using stock recovery (i.e. Android Recovery 3e) and factory reset your device without using CWM then it will not brick device.

You can find that thread here.

Its not true ?

And as I am not having Root so do I need to flash kernal using Windows PC Odin3_v3.04 ?

And Siyah-s2-v4.1.5.tar is safe to use for this bricking issue ?
[Galaxy Note GT-N7000 General] Spiralzz:
Yes, although I doubt there has been a case REPORTED of bricking from stock recovery, Entropy has clearly stated that even the stock recovery can cause a brick.

Yes, flash the siyah kernel (.tar) file via Odin.
[Galaxy Note GT-N7000 General] shoey63:
Use Philz kernel. Its flashable from stock and safe to wipe on
[Galaxy Note GT-N7000 General] NIK3SH:
Need Confirmation

Thanx for your reply.

So now I will have to follow,

Go To Download mode and install Siyah-s2-v4.1.5.tar using PC Odin3_v3.04 and thats all.

After flashing this siyah kernal, do I need to wipe data or I can use directly after rebooting ?

And do I need to change my ROM or I can use this Official Stock ROM (4.0.4) after installing Siyah kernal ?
[Galaxy Note GT-N7000 General] Spiralzz:
Yes that's the process. You don't need to wipe anything. You can use that kernel with the stock rom and any custom rom.
[Galaxy Note GT-N7000 General] NIK3SH:
Also one more thing.

After installing this siyah kernel, can I use Samsung OTA updates when it will launch JB 4.1.1 in November ?
[Galaxy Note GT-N7000 General] Spiralzz:
Yes, I believe so.

Please ask further questions in the Q&A thread for the Galaxy SII as this thread is only for a specific topic (no offense).
[Galaxy Note GT-N7000 General] reinbeau:
This. This is not a Q&A thread. No more on this discussion.
[Galaxy Note GT-N7000 General] shoey63:
With reinbeau's permission, I would like to pose a few questions that I feel are relevant to brickbug.

In Ubuntu, I ran

Entropy's strings command on "recovery" file in cwm-touch-philz-6.0.1.4-i9100.zip, and it shows this:-

ubuntu@ubuntu:~/Desktop/binary$ strings recovery |grep MMC

warning: %s: Wipe via secure discard suppressed due to bug in EMMC firmware

And on "update-binary" in same file results in this message:-

ubuntu@ubuntu:~/Desktop/binary$ strings update-binary |grep MMC

warning: %s: Wipe via secure discard suppressed due to bug in EMMC firmware

EMMC

EMMC:

So I would like to ask the following:-

1) Is this "Temp" recovery safe to do wipes and flash update.zips with format commands, even if u are on stock ICS kernel?

2) Is update binary still active once file is flashed?

3) If wipe via secure discard is suppressed what type of formatting actually occurs?

4) Is it the same sort of wipe that occurs in GB kernels and ICS ones with eMMC_CAP_DISABLED?

5) Just how many types of erase are there in Samsung phone Nand? Obviously the dangerous "secure", the almost as dangerous "non-secure"

and the slightly dodgy "recursive-delete" What else?

Just trying to learn, that's all. If some-one with greater knowledge than I can enlighten me on these matters, I would be greatly appreciative.
[Galaxy Note GT-N7000 General] shoey63:
Great tutorial! Thanks:)
[Galaxy Note GT-N7000 General] alvinasnow:
Wait was worth it. Thanx for the hopes. I dont wanna visit again to find "Samsung Working on the Emmc Brickbug". Good education though, learnt many things. Thanx.:silly:
[Galaxy Note GT-N7000 General] NIK3SH:
Need Help

Hello,

I need help.

My phone got stuck at Samsung Logo.

I dont know what happen, but I was playing NFS MW Cracked version and click on Garage Icon to purchase Car.

As I click on that button, my phone restarted with Samsung Logo and since then it is stucked at Samsung Logo and Not going ahead.

My Phone is running insane chip, stock recovery and Stock 4.0.4 firmware (Screenshot attached).

I can go in Recovery mode, Download mode as well charge my Phone in offline mode.

Please help me what should I do as I even cant factory reset my phone. Cause if I do that it will be bricked (eMMC Brick).

Please help me.
[Galaxy Note GT-N7000 General] shoey63:
Please post in Q&A. and delete from this thread.You will get help there:)
[Galaxy Note GT-N7000 General] :
Good news from Samsung!

Today i came back from Samsung Service Center in here from Oporto, Portugal and well.. it seems that Samsung as implemented new chips on the GT-N7000 :D

Brought my Note with it's forth motherboard! God bless warranties and my free Note :D

Had to take a photo of the screen because i don't have my SPen with me to take a screenshot! :good:
[Galaxy Note GT-N7000 General] domnic79:
There r other options to tk screenshots.

Swipe ur hand over d screen & it takes screen shot.

Or

Menu + power.
[Galaxy Note GT-N7000 General] desaipa:
Got some relief

Its good to hear about samsung is working on it. :D

My phone emmc check is showing

eMMC Chip

type VYL00M

date 08/2011

CID:

FwRev: 0x19

Brick Bug?

YES, Insane chip.
[Galaxy Note GT-N7000 General] stayhard:
I hard bricked my s2 when I tried to flash from official samsung 4.x.x.

So is this fix going to fix my phone or is it only for those who hasent bricked?
[Galaxy Note GT-N7000 General] :
Only changing the motherboard will save you ;)
[Galaxy Note GT-N7000 General] shoey63:
@zylor. Would you mind reliving the experience of how you bricked 4 times? (Painful I know - but would be Educational to other users)
[Galaxy Note GT-N7000 General] nigi73:
So v3uoom is safe? My note has this chip from new :)

Gotbrickbug says unknown chip :confused:
[Galaxy Note GT-N7000 General] :
1st hard brick i learned the hard way: LPY leak hardbrick.. formatted on CWM and the phone died!

2d hardbrick i thought i was using a safe kernel when i was gonna flash paranoidandroid from ::indie:: but without knowing it ::indie:: was using an unsafe binary to update so it triggered the brick bug and because of my hardbrick and some others paranoidandroid thread was closed for almost 2 days just to get to the issue and the update-binary was updated to not trigger the brickbug and cyanogenmod also used an updated update-binary to avoid possible hardbricks to users in XDA :D

3rd time i dunno why but my bootloader got messed up so i went there and thought to myself:" I will go to the samsung service center and they will possibly give me a safe chip! "

4rth and last time:" Bricked when i was rooting it from the 3rd time and by mistake i formatted in unsafe stock kernel and hardbricked!

So by now i have a safe chip so no hardbricks for me :D

The most important step was my second hardbrick which really helped the community :highfive:

The revision of yours is not known yet! Mine is known to be safe! But i won't risk it.. that's for sure :D
[Galaxy Note GT-N7000 General] nigi73:
I found the same app for check as you used in screen-shot, and my note is safe as well - we have the same chip.:victory:
[Galaxy Note GT-N7000 General] :
Awesome news :D
[Galaxy Note GT-N7000 General] Gugelhupf:
I also have the V3UOOM chip, and the same results shown in both apps. I don't trust it either, so I'm using PhilZ Kernel. I was happy with the modified ICS kernel, because the stock has great battery life, and CWM is mandatory for me.

Cheers, Markus
[Galaxy Note GT-N7000 General] Sonic_AFB:
my sgs2 i9100p nfc have the same chip, it's 100% secure flash any kernel or rom with im?
[Galaxy Note GT-N7000 General] jj_95nano:
Newer GS2 with sane VIS00M chip.

So if my GS2 has a VIS00M chip dated 05/12 (FwRev: 0x09)... can I flash LEAKED firmwares, and kernels with MMC_CAP_ERASE?? :confused:

Chainfire's app says my phone has SANE chip. I bought this GS2 pretty recently...(maybe a month back).

The memory test took 550s for me:eek:

I'm asking 'cause I want to flash the leaked JB firmware and in case its buggy, I would wipe and go back to GB.

:fingers-crossed:

EDIT: I noticed some GS2 users, hence I posted here... In case it's irrelevant in N7000 forums, please delete my post.
[Galaxy Note GT-N7000 General] :
My question for people asking this type of question- is it really worth the risk? Wouldn't you rather just be on a safe kernel before doing such?