yashsingh1/xdaforums huggingface dataset:
[Sony Ericsson XPERIA X10 Mini] wallcot:
how i can updata to 2.3 ??
[Sony Ericsson XPERIA X10 Mini] demoniacs:
ummm search the dev section?
[Sony Ericsson XPERIA X10 Mini] speedsys:
Have a look in the dev forums

Root, recovery, backup, flash :D

Cheers
[HTC One X] colobos:
Does anyone have or any links to good icon packs with alot of high quality icons?
[HTC One X] BeeDubz:OneX:
Yeah mate al put a link up later for the icons I'm using
[HTC One X] BeeDubz:OneX:
Heres them icons mate :)
[HTC One X] colobos:
Thank you
[HTC One X] SolusCado:
Check out www.iconfinder.com. A ton of icons you can use for everything.
[HTC One X] hd2neuling:
Here u can get 3D-Icons & more by tantin75 ;)

LG, Helmut
[HTC One X] rajitsingh:
I quite like this one:

http://wwalczyszyn.deviantart.com/gallery/#/d3aiidb

Haven't tested the pack on my HOX, though.
[HTC One X] derwinaero:
So is how did you add them in the sense launcher?
[HTC One X] hd2neuling:
With e.g. Desktop VisualizeR from PlayStore, tutorial by SeriouslyCrazy is in the first post in my link above (or 2nd link in my sig)

LG, Helmut
[HTC One X] mikep1993:
Do you use miui or still sense or stock?
[HTC One X] Gaurav93:
Finesse icons

Please check this out : http://gaurav93.deviantart.com/art/Finesse-Icon-Pack-321895463

Thank you :D
[HTC One X] ez2:
Checkout "droidicon" free in the play store

~Samsung Galaxy SIII (SPH-L710) - Blazer ROM v1.6 - TWRP~
[HTC One X] Sckank:
Really nice!!!

The one I found wasnt free.
[HTC One X] ez2:
My mistake, it was previously called "custom launcher icons" and I do believe it has always been a paid app but with it IMO

~Samsung Galaxy SIII (SPH-L710) - Blazer ROM v1.6 - TWRP~
[HTC One X] dragonesdenano:
My icons...from free google

http://db.tt/JIoU5CbI
[HTC One X] donmescobar:
Wallpapers

Hi!

How can I download the wallpapers from the icon packs( in Solstice HD I can apply the wallpaper but I can't download it)? Is there any way to do this?

Thanks
[Galaxy Note GT-N7000 General] androidindian:
More info and source credits here, thanks to codeworkx https://plus.google.com/111398485184813224730/posts/21pTYfTsCkB.

New Clarifications by Entropy : http://xdaforums.com/showpost.php?p=28416723&postcount=403 - Must Read.

To check whether your phone has the brick bug, download the Got Brickbug app from Chainfire: http://xdaforums.com/showthread.php?t=1693704

Also do read the article on xda for more info.: http://www.xda-developers.com/android/samsung-diligently-working-towards-hardbrick-fix/
[Galaxy Note GT-N7000 General] sc00by666:
Nice!
[Galaxy Note GT-N7000 General] prasad.adam:
That is a really good news after some time.
[Galaxy Note GT-N7000 General] calvincarlos:
Good news!

Looking forward to see how Samsung solve this nightmare
[Galaxy Note GT-N7000 General] gominolo2002:
How many time to fix this Samsung BUG? How maby people need ti brick our 600€? If samsung knows why no first before? Grrrrr...

All hard work its from XDA devs!!!! Thank you devs!!

Enviado desde mi GT-N7000 usando Tapatalk 2
[Galaxy Note GT-N7000 General] nandihno:
Hmmm don't want to get my hopes up

But hmmm ok let's hope saw but how do we know is true ?
[Galaxy Note GT-N7000 General] androidindian:
Teamhacksung dev codeworkx been in touch with Sammy guys so its genuine news...check link in op :-)
[Galaxy Note GT-N7000 General] jermitano:
at least we now have some hope...hopefully... :p
[Galaxy Note GT-N7000 General] ripnetuk:
So to be clear...

Can someone confirm the following is correct please?

I have a N7000 on official (german) ICS, with the dodgy mmc chip. I must have been lucky since ive flashed a bunch of roms (including CM9, back to gingerbread, then official ICS) without issue. Ive also done a few CWM backup and restores... phew!

1. Flashing anything from the phone itself (eg using mobile odin or CWM recovery) is a no-go (assuming it issues the erase command)

2. Flashing from the PC is OK ??? (via desktop ODIN)?

If 2 is untrue, how is sammy gonna issue an update (with the erase capability turned off) without bricking a load of phones during the update process? can they maybe provide a custom app which re-flashes the kernel without doing an erase first?

thanks

George
[Galaxy Note GT-N7000 General] nandihno:
Flashing is not the problem but wiping is

So if they release a new update then simply don't wipe on your ics but wipe only after you install the new update

If however you want to be extra careful like I am

Flash a gb rom via odin then wipe that then flash said ics update via Odin
[Galaxy Note GT-N7000 General] cyberpingu:
While there have been brickage reports using either PC Odin or CWM, there have been none regarding Odin Mobile Pro. So, when I flashed back GB, I used Odin mobile Pro. Everything went smooth.
[Galaxy Note GT-N7000 General] friedje:
//troll mode activated

It's just like Microsoft patching windows vista

//troll mode off
[Galaxy Note GT-N7000 General] GocaS6:
This is a true victory for XDA developers!

My deepest respect for all of you guys :thumbup:!!
[Galaxy Note GT-N7000 General] blue_panther9_9:
Are they releasing a fix for brickd phone or a prevention update?
[Galaxy Note GT-N7000 General] jenizaro:
Prevention.
[Galaxy Note GT-N7000 General] altae:
I really hope this mess will soon be over. Let's hope while they are resolving the brick bug they also take a look at the wakelock thing. Contrary to others I have encountered this problem very rarely (1 time so far). Nonetheless it would be nice to see a solution.

Sent from my Galaxy Note running ICS
[Galaxy Note GT-N7000 General] tribalkg:
Good news but given that we haven't seen ics roll out in all countries, who knows when this will get fixed.

Another thing that bugs me. Is there possibility that Samsung push the solution for this bug and carriers just ignore it and continue with pushing the infected ics?

I guess that all we need is just one good release and everyone can flash it.

Hope to see it soon.
[Galaxy Note GT-N7000 General] ashoksoft:
In all probability it might show a message over kies / OTA message asking to connect to kies on the comp .. and provide an update for kies desktop :) having 0din in it :)
[Galaxy Note GT-N7000 General] androidindian:
Update 14:56 CEST:

Patches will be out in form of new official ROMs and also sourcecode releases after testing, which might take some time.

Just updated op too
[Galaxy Note GT-N7000 General] SpyderTracks:
This is great news! Many thanks to entropy and chasmodo and all who've worked on this and sacrificed for us!

Also thanls to those who took it seriously.
[Galaxy Note GT-N7000 General] MR.change:
no of course every brand and every phone is prone to bricking ,but bare with me here for a moment :

why did the Note and E4GT made all the noise and not any other phones? there must be more bricks than average right?

also ,if we root the phone then wiped ,is it our fault if the emmc died due to the buggy 0x19 fw revision?

I mean take me for example , I flashed many ROMs and did several wipes ,the only time that I had an emmc malfunction was when I wiped on LPY .

as for the number being low ,there is a very good explanation for this , not every note owner will post here on XDA to let us know ,and the ones that are here on XDA are all scared/know better than to preform a wipe.

there are a few brave souls ,some of them survived ,some didn't ,then posted on xda to say that they bricked.

also a full stock user has likely updated via KIES and therefore less likely to wipe and encounter such issues ,I know that's what I did when I was a noob :D

I do hope this will (happily) end soon

cheers

I like your way of thinking , almost a Russian roulette eh?
[Galaxy Note GT-N7000 General] nCoder:
@Entropy could you please refer one example of a virgin stock phone having a hard-brick? All cases I investigated claiming that were hard-bricked on stock roms, are either not virgin stock roms, or it wasn't a hard-brick, or the brick was caused by other scenarios (not during factory reset)

Don't get me wrong. As you know I acknowledge there is definitely a problem in the emmc chip, and very familiar with your great work. But the scenario where this bug manifests was never clear to me.

As for the people that only now are jumping here to add noise, I'd ask again a bit of respect and recommend to search the forum for more information before flaming others that might know a bit more about the problem in discussion.

Cheers and respect.
[Galaxy Note GT-N7000 General] nuramohammed26:
All those insisting that nothing is wrong with official ICS is because they have not yet Brick their Gnote, if I brick my Gnote because i flashed a custom firmware that is my problem but if i flashed my Gnote and bricked it,then later i found out there is a 0.000001% that it's Samsung's fault(eMMC problem) then that is a whole different story.
[Galaxy Note GT-N7000 General] reinbeau:
Thread cleaned yet again

Gentlemen!

I have cleaned this thread again. Do not antagonize or pick at each other - this is a frustrating situation, we don't need to make it worse by arguing, the good information being posted will be lost in the dreck. Post if you have something informative to say, otherwise, don't post.
[Galaxy Note GT-N7000 General] nuramohammed26:
Something is wrong with Gnote ICS update,with or without root,with CWM or not.

@Entrophy I appreciate your work and i hope you find what you are looking for

---------- Post added at 12:07 AM ---------- Previous post was at 12:04 AM ----------

Thanks a million times for your intervention :D
[Galaxy Note GT-N7000 General] paiseleht:
There are 2 sides of the Galaxy Note coin.

One is that the virgin stock phones do not brick as easily as rooted/custom ROM phones. If one wants to be objective, one should accept that fact.

The other side of the coin is that all the Android logic encourages people to create custom ROMs. That side of the coin must be accepted also, by the Samsung too.

And as for the Entropy - perhaps you were too early in branding some that had different opions as idiots.
[Galaxy Note GT-N7000 General] plsoft:
GSMArena has posted about this bug in its news section. Read it here.
[Galaxy Note GT-N7000 General] MR.change:
yeah it looks like they heard us this time.

now I just hope things will go according to plan

thanks ,this thread was really starting to pick up heat:D

maybe ,but just remember one thing ,there are users who bricked by factory resetting ;) ,so it's not safe as well.

that be true ,but it's generally assumed to be safe

it's safe believe me ,even though LPY gave me issues , I wiped from CM9 multiple time later on with nandroid restore and my phone is still kicking .

also people with SOD problems are wiping all the time on cm9 ,and so far not a single brick reported.

so yes cm9 is the only thing guaranteed to work in this whole drama episode. :)

well let's see ,I bought my phone a GB virgin (with me being a total noob back then) ,then installed the prerooted JP1 by chainfire ,then flashed a couple more stock GB ROMs and installed JK mod and a few themes on them , then deodexed my phone (without flashing). all in two weeks so I guess I'm a very fast learner :cool:

then went ahead and flashed CM9 (with full wipe for the first time) and used it happily for a week ,then on my birthday:rolleyes: samsung released LPY and I had to try it so went ahead and flashed via mobile ODIN ,flashed LPY along with CF-root LPY kernel (which is basically just stock pre rooted) ,then booted into LPY and full wiped from (stock) recovery and all went well.

didn't like what I saw so decided to go back to CM9 ,fired up CWM ,preformed a nandroid restore (which wipes first)and it hanged on restoring system.

luckily however it had restored the cm9 kernel ,so I rebooted into that but the system partition was stuck no matter what .:eek:

to cut a story short ,I went on a frantic power on\power off cycles ,with taking the battery out as well every couple of times.

after about twelve failure attempts ,and skipping some heart beats :( ,system partition finally responded by a miracle (well it was my birthday after all :p) and the nandroid restore went ahead ,and viola the lovely cm9 boot animation appeared .

and all is well in the cm9 world ever since.

now you could of course argue that a first time wipe went successful because it was from Stock recovery ,and maybe you are right ,we have to see what entropy finds regarding this :rolleyes:

but that begs for the question (again) ,must we stop flashing and rooting because samsung doesn't want to fix the emmc bug?

agreed

also ,it's weird how this never got to the press (until now :D)
[Galaxy Note GT-N7000 General] M3TALLICA:
I did post review and tip there but it did not appear.
[Galaxy Note GT-N7000 General] cletusarrarr:
It has finally been posted.

http://www.gsmarena.com/samsung_responds_to_galaxy_s_ii___note_emmc_bug_problem-news-4394.php
[Galaxy Note GT-N7000 General] nuramohammed26:
Wow I saw the News alert in GSMarena,i think we are making progress :)
[Galaxy Note GT-N7000 General] @denny:
gotta love the wallpaper they used ...class:D
[Galaxy Note GT-N7000 General] waqas.sonic:
I am on one of the Dangerous EMMC's but have always wiped/flashed from safe kernels (Abyss etc), no issues what so ever !
[Galaxy Note GT-N7000 General] sangalaviral:
GSMArena should specify that wiping creates the problem. Not installing a custom rom.
[Galaxy Note GT-N7000 General] Entropy512:
Robotu was the first one. Whether he was rooted in /system DOES NOT MATTER because nothing in /system is used when booted into stock recovery. If he bricked on stock kernel/initramfs, then the stock kernel/initramfs is dangerous because SYSTEM PARTITION CONTENT DOES NOT MATTER.

Then there's fraad only a few posts back.
[Galaxy Note GT-N7000 General] musashiro:
still waiting on GB rooted.... i hope samsung provides the fix soon... at least before july..:D
[Galaxy Note GT-N7000 General] andreww88:
So, there is going to be a patch. So, our work is complete. Let's move on and wait for a fix from Samsung for official ROMs and the developers here can move forward with bigger and better things.
[Galaxy Note GT-N7000 General] Entropy512:
That's just a restatement of the same XDA portal article that started this thread. No new news.

Our work is nowhere near complete. They have still not provided any information that can be used to resurrect/repair damaged devices for example. There are other issues that some of the ERDs are trying to work with Samsung on too.
[Galaxy Note GT-N7000 General] MR.change:
yes true ,it's far from complete

besides ,GSMarena didn't even state everything correctly ,first they said

which is a direct miss quotation from Daniel Hillenbrand on Google+.

needless to say how wrong this is ,as it doesn't matter what kernel you flash to ,but rather what kernel you flash from.

and they completely skipped the fact that full stock also has this issue.

oh well ,I guess one shouldn't expect much better than this anyway ,at least now more people will be aware of this issue and thus refrain from wiping their phones.
[Galaxy Note GT-N7000 General] breckbit:
At least hardwareside, samsung keep on replacing bricked mobo´s with the same vulnerable eMMC chipset / 0x19 - as they did in my case. for my sake they replaced it as case of warranty.

is there any possibility at all - in case samsung develope it - to update the eMMC firmware?!
[Galaxy Note GT-N7000 General] MR.change:
why are you such a pessimist? :rolleyes:

Thank you for proving my point ,the recovery type has nothing to do with it ,it's samsung's kernel that is at fault here.

that's why I said assumed

well considering the fact that I changed many times to stock GB and back to cm9 ,wiping along the way proves your "assumptions" to be baseless ,LPY is the root of the problem not CM9 ,otherwise I would have a brick whenever I leave CM9 ,which is not the case.

besides ,I was fully booted on LPY and ran it for an hour before I decided to wipe again ,so any "changes" brought by CM9 were removed when I booted into stock LPY.

You love to speculate ,don't you?

no ,what I think is that the issue never reached high command yet ,and when it does ,the fix will be to simply remove the erase command from new stock kernels ,because updating the emmc fw is just not possible on the already manufactured\deployed units.
[Galaxy Note GT-N7000 General] mintu123:
samsung is being nice and fixing all these bricks because they are big company and they dont want upset users.mobo prob cost them $5 to make.if it was htc they would have gien them a finger.
[Galaxy Note GT-N7000 General] reinbeau:
Thread cleaned yet again

Again with the nonsense. There are very few here who actually know what they're talking about - why not just refrain from posting so the knowledge will be easy to find? Set your ego aside and think before you post. And if you see something that should be removed, hit the report button - do not respond to it, just let us clear it out.

Rank speculation will also be deleted - again, if you don't know, don't post.
[Galaxy Note GT-N7000 General] prasad.adam:
At the moment, there is a mystery around extremely low failure rate on virgin stock ROM vis-a-vis rooted ROM.

Entropy512 is working on unraveling the same. Hope he gets some concrete lead on the same. Patience till then.
[Galaxy Note GT-N7000 General] nuramohammed26:
@Entropy512..... We that already Bricked our Gnote are praying for you to find a solution so that people that have yet encounter this problem can actually find a solution if it happens.Please keep your head up and don't bother what other people say about this issue,The important thing is that this BUG exist, so lets SQUASH it.
[Galaxy Note GT-N7000 General] paiseleht:
With stock firmware the best you have is some bricked modules and even these are not purely stock (no matter what is complained).

With some custom methods it was/is 100% guarantee that "when you wipe you will brick".

So how come do some of you claim that there can not be any difference, that all is the same. Evidently all is not the same.

And besides, 0x19 may not be the correct identifier of "buggy" eMMC module. Yes, I know, the Google developer said so. And yes, it is so that almost all bricked devices have this identifier - firmware. Besides firmware each chip has something that allows the firmware work. This (the chip itself) may be different - maybe it is not documented, maybe the difference is subtle and somewhere else and maybe there is something else in the whole device configuration that makes all the difference. Yes, I have read the threads but actually these questions are not clearly answered (are not answered at all).

The problem would be 100% like it has been stated by some devs only IF the failure percentage would be the same with stock and nonstock wipes. But it is not.
[Galaxy Note GT-N7000 General] abhijit038:
Yes, you are right. Moreover, people here are not realizing that MVC of PCB and various other parameters of Galaxy nexus and Note differ substantially. Hence we can't say what's applicable in case of Galaxy Nexus would be in case of Note too.
[Galaxy Note GT-N7000 General] prasad.adam:
Even with affected custom ROM/kernel the probability of bricking is not 100% as is being implied.
[Galaxy Note GT-N7000 General] stoney73:
Its brilliant to have so many qualified, experienced proven experts in one forum that feel so comfortable giving informed advice. [Sarcasm/off]
[Galaxy Note GT-N7000 General] musashiro:
come on guys, even samsung acknowledge the issue and its on stock...

so stop bi*ching or the mods will close or clean the thread again...

stop acting like you are better than people who investigate thoroughly.
[Galaxy Note GT-N7000 General] prasad.adam:
Implying that GNexus and GNote being different phones, we should not be comparing them on eMMC issue, is well, naive.

Once Exynos-4012 based eMMC chip with fwrev 0x19 receives an erase command, it will intermittently lock itself up. Period.

It doesn't matter which PCB/Bus it resides on or what other components there are on the board. It is almost analogous to, all thugs behaving themselves, sensing a super-cop in the town. Doesn't happen in reality!
[Galaxy Note GT-N7000 General] reinbeau:
The problem is you don't know. You are clogging up an informational thread with conjecture and your opinion, none of which will aid in fixing the problem.	This is why the other thread was closed. Final warning before this thread too is locked.

Sent from a state of Serendipity
[Galaxy Note GT-N7000 General] prasad.adam:
The irony is that he doesn't see any problem whatsoever. So, where is the question of aiding in fixing the problem.
[Galaxy Note GT-N7000 General] oka1:
From the Moderator

To all in the thread---

The Emmc Bug is a known issue and has been for awhile. Please stop with innuendo and hearsay (that means don't post like you know when you do not). Stick to facts do not post speculative crap.

I posted a system dump of Tmobile Beta phone with 4.03ICS on it 7 weeks ago. It was running flawlessly. Case and point.

As Moderators we cannot prevent you from doing what you feel like, but we can will manage flawed information such as some of these postings... as they do not help improve the situation but rather...... create greater risk. If flaming starts as a result from 1/2 baked misinformation postings... we will close the thread...... Be Respectful, be accurate.

Before flashing anything....... REALLY DO YOUR HOMEWORK....... read, read, cross reference...... then if you are comfortable, then flash away........ remembering if it bricks... it is ONLY You....... to blame.......

oka1 (moderator)
[Galaxy Note GT-N7000 General] PoisonWolf:
Finally, a moderator comes in and clears up the BS being spewed from members with no experience in this field other than clairvoyant BS.

Thank you so very much for this.

---------- Post added at 11:08 AM ---------- Previous post was at 11:06 AM ----------

Reinbeau, why can't you just bar these ppl from this particular topic? Or give them an infraction or something?

It's really getting tiring to see these ppl take potshots at still trying to convey pure BS in telling folks that it is safe on stock ROMs. They hop on the ill-informed bandwagon, still trying to preach his crap to other users.

I hope nobody takes his posts seriously. It is dangerous and seriously misguided.

I mean, seriously, the "profundity" of some members on this matter is utterly astounding /sarcasm.
[Galaxy Note GT-N7000 General] friedje:
@Arobase :

Forget about GB, even though the CAP ERASE is enabled, it is never called in GB.

Google only uses it for wiping since ICS..

Forget about the External SD being driven by sdhci.c, it doesn't use the same controller as the EMMC.

That way you can focus on a smaller part of the source code :)
[Galaxy Note GT-N7000 General] garwynn:
In addition to Entropy's post... While he is talking to one person I'm still working this from another direction. Letter went to R&D in Texas to ask about this and should reach them on Monday.

Based on the trend I should get some sort of response... Whether it is what we are hoping for or not - the eMMC information and controller patch - will remain unknown until then.

E4GT source should drop soon and help give some hints until Entropy is authorized to release info. Let's hope that comes soon too. Good luck!
[Galaxy Note GT-N7000 General] Entropy512:
One thing to note: T989 sources dropped with MMC_CAP_ERASE removed from msm_sdcc.c (their equivalent of our mshci.c) - One of the T989 devs (or one of the Skyrocket devs, it's almost identical to T989) used https://github.com/Entropy512/n7000_erasetest_kernel/commit/c9b5be55339417831a507de9e41a0493113c8076 and found that ERASE attempts were blocked at a higher level (which is consistent with MMC_CAP_ERASE remove - this code will never even get called if MMC_CAP_ERASE is removed.)

So it looks like the T989 had the MMC_CAP_ERASE treatment at the last minute - as T989 and Skyrocket leaks were triggering the bug.
[Galaxy Note GT-N7000 General] reinbeau:
Above is the only kind of reply that matters. The utter malarkey posted by those merely speculating does nothing but clutter up the thread. I'm mobile for now, I'll clean this mess out again when I get home.

Sent from a state of Serendipity