[Q] How can i fix DATAFS particion?''

---

Hi all.
i´ve flash the last ics firmware with bootloader pit repartition an all the file. all that thing go wonderfull. i whant to go back to my kingdroid rom doing fullwipe. i reboot into recovery and i flash a cwm temporary. i go to wipe cache dalvik but data got stuck. i pull out the battery and i´ll see that the phone its stuck into bootloop. i tryed to flash a stock gingerbread, a stock ics a custom rom and avery thing go stuck in odin pc on DATAFS. can i fix it??

Originally Posted by Dr.Taly

Hi all.
i´ve flash the last ics firmware with bootloader pit repartition an all the file. all that thing go wonderfull. i whant to go back to my kingdroid rom doing fullwipe. i reboot into recovery and i flash a cwm temporary. i go to wipe cache dalvik but data got stuck. i pull out the battery and i´ll see that the phone its stuck into bootloop. i tryed to flash a stock gingerbread, a stock ics a custom rom and avery thing go stuck in odin pc on DATAFS. can i fix it??

Why don't you ask Entropy512 in a PM? He's best qualified to give you an answer to your question.
Everything else you're likely to get here would be pure conjecture.

It would be nice to know however, was it LPF of LPY.
and while, yes, entropy knows a lot of things, not all samsung flashers are dumbots that can not systematically analyze such information.

If he has bootloader on this, cant i sound like its LPF ?
If so its sounds like the same problems Ficeto from darky team had on LPY ?

Originally Posted by opsakas

It would be nice to know however, was it LPF of LPY.
and while, yes, entropy knows a lot of things, not all samsung flashers are dumbots that can not systematically analyze such information.

Why don't you systematically analyze the information and offer us a viable way of getting out of the superbrick situations?
I freely admit that I am a dumbot when it comes to that, and could use some help.

Well, statement about bootloader does not mean anything. It is an assumption and thus not reliable in such situation. People do mix files, intentionally, unintentionally, and by chance.
But then again, we all know what is in common with 99.9% of hardbricks.
And the 'reported' few cases of bricking on stock fw - is it sure that these phones were never-ever flashed with anything else than stock?

But as for devs, i have to stress one thing. The higher the price of failure, the more we tend to find culprits outside of our own circles. And it is human. One of the toughest things to admit is always admitting one's own part in unwanted results.

In other words, you don't know squat, but are offering general philosophical musings instead.

What i am thinking... Is it that in Germany the service centers are really overcrowded these days? I do not have information, but if that would have been the case, some information would be even here in XDA.
And with the stock fw brick - with every flash there is risk for small percentage of failure. Perhaps that was the one.
It seems that there may be almost identical functions for handling file system. Perhaps in raw level and perhaps there is only one function but it depends of the parameters.
What it seems to me is that custom roms are working just abit too fast. Perhaps with stock ther is no chance for the error show out.
And going into dark side, i personally have met with several serious computer and related malfunctions during last week. The sun activity or something else similar may cause undesired effects where tolerances are too tight. The 32 k of zeroes might be written not by random but by some input that may depend on things that creators of the chip could not foresee - but nevertheless exists.

For practical considerations i assume the custom roms allow the note to execute some functions too fast.

---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------

There is one word and that is responsibility. You might want to think about it.

---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------

Well, statement about bootloader does not mean anything. It is an assumption and thus not reliable in such situation. People do mix files, intentionally, unintentionally, and by chance.
But then again, we all know what is in common with 99.9% of hardbricks.
And the 'reported' few cases of bricking on stock fw - is it sure that these phones were never-ever flashed with anything else than stock?

But as for devs, i have to stress one thing. The higher the price of failure, the more we tend to find culprits outside of our own circles. And it is human. One of the toughest things to admit is always admitting one's own part in unwanted results.