yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] Auzy:
I'm going to call this rumor plausible at best.. Unofficially, I'm going to call it an unproven assumption until we actually see evidence, links and actual references (not vague evidence such as "it's somewhere in a schematic, somewhere over there"..

On the official Movinand page, there is a capacitor, and a link elsewhere states (as an opinion) that the capacitor may be there to ensure data is committed. However, you'll notice only the controller, not the Nand is backed by a capacitor in the upper link which means in that example, it can't be used for committing data, because the NAND seems to require power too. That diagram seems to suggest it's used for stabilisation.. The brochure doesn't mention anything either.

So, unless it's somewhere in the Samsung Galaxy S Service manual, or another link which says it actually exists, there is no proof.

Without further proof, at this point of time, this rumor seems to be comparable to Schroedinger's Cat, it may be dead or alive, but until it's taken out of the box, anything is a guess. Unless DamianGTO can actually PROVE otherwise, lets call it busted (it's better than having people running around promoting assumptions). I suspect the real problem here is that there are too many people on XDA repeating information without adequate evidence. As a community, it would be nice if we could bust/confirm this myth for good!
[Galaxy S I9000 Q&A, Help & Troubleshooting] DamianGto:
The problem is that im not the only one that has looked at this and all has come to same conclusion. If you dont want to belive in it its up to you.

I think ryanza, hardcore, supercurius........... has same view on it.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Auzy:
That's my point, I've seen a few people mention it, but not a single one seems to have posted evidence which proves it. It still doesn't change the fact, that even now when quizzed on it, those who have made the claim aren't actually proving it. If you had actually proven it to yourself once, surely rather than post a comment like "that's your opinion", you would have proven it?

I'm sorry, as mentioned, unless you are willing to post evidence which proves the matter, it seems like it is likely based on rumor.. At the moment, all evidence I posted points to it being non-credible, and I am unable to find accurate evidence (even after posting a link to the service manual for you to spot the page). Even worse, in your typical fashion, when asked "what schematics did you check?", you ignore the question. Your inability to prove such a system exists more likely proves it doesn't, than does.

Unless proven otherwise, rumor busted.. I will update a few posts where the capacitor was mentioned in the near future to acknowledge that. I'd like such a nice system to exist to ensure cache gets flushed to disk, but there is simply no evidence it exists. And I'd rather the rumor is changed from truth to "unproven", than for future XDA'ers to repeat it.
[Galaxy S I9000 Q&A, Help & Troubleshooting] DamianGto:
Do what you like. If you think i simple graphical pictures is prof for you its up to you.

Like i already say you need to look in the electronic schematic to se what things is and read what they used for.

So look there before you start to write all over xda.

**DamianGTO Steam kernel. 350MB Ram. 500HZ. ext2/jfs . js3 base**
[Galaxy S I9000 Q&A, Help & Troubleshooting] Auzy:
I've already tried.. I can't find it.. So look over it FOR ME and everyone else, and please find it for me, so everyone can learn. At least mention which schematics you checked, or give hints?

Further research shows the people posting it are: RyanZA, harrydg and yourself.. Supercurio and the others you mentioned NEVER seem to mention it (or I can't find the posts where they do). RyanZA posted it initially (but nobody questioned it), Harrydg and yourself replied to the same thread. And I think the reason you are reluctant to reply to the thread with details on how you know it to be true, is because you are simply relying on RyanZA's observations.

HOWEVER, whats clearly interesting is that DamianGTO said "True, but if you pull the battery you loose power, but the capacitor have power left to finish the task(often)." How do you know that? Because that is something you wont find in documentation..

As DamianGTO is simply telling everyone to "trust him", I will try contacting RyanZA and HarryDG to try to get to the bottom of this discussion. It would be interesting information to learn. To the community, the reason why it is important to see accurate evidence, is that it might change the way ROM's are developed.

If no accurate proof or even basic evidence in the form of links can be provided, then as a community, we should ensure we quash the rumour for good.
[Galaxy S I9000 Q&A, Help & Troubleshooting] DamianGto:
You can think what you like , but im not a service for you to get information you can find for yourself.

If its true or not it dont matter much when we do kernels. Its up to user to choose what he want to use.

If you want to be safe then don't customize your phone.

All people that flash the phone and use custom stuff know it can break so the have to flash it again.

That's why a backup is important.

If you don't trust ext2 for you think its not safe, then don't use it.

Its very simple.

Me and other that want speed and do have a own mind to think with will still use the file system we like.

Maby im right or Maby im wrong.

It still don't change anything.

It don't work less or better...

Tell my why you should use a file system you don't think it safe??

Don't you learn what things are before you use it??

It tells more who you are.

Edit: if im wrong then you just prove that ext2 is safe to use on all partition. After all i got zero problem with it on data and i know alot of people use it with the same results.

So thanks for the update:-P

Edit 2: well now did hardcore answer this and he and supercurius did test this out and come to the same conclusion that is alot safer on data then other places.

I did already know this.

So shall you start flamming them to?

All top developer maby is wrong??

**DamianGTO Steam kernel. 350MB Ram. 500HZ. ext2/jfs . js3 base**
[Galaxy S I9000 Q&A, Help & Troubleshooting] appagom:
Damian you say all this arguing doesn't matter because people will do what they want anyway. Well how about this crazy idea, maybe some people make decisions about what they "want" using information, so, hey.. maybe it does matter. I for one am interested in seeing if it's possible to have ext4 style safety with better performance and I don't believe ext2 does that just based on the SD block write argument alone. So, if I have information that there is a capacatior that can clean up non-ordered journal writes in ext4, then great. That means barriers=0 and data=writeback will be equivilant to barriers=1 and data=ordered on a non-backed device and that WOULD BE good to know.

However it deosn't mean ext2 is any safer. there has been no claim that any cleverness is being done after a power failure other than to simply continue writing whatever is stored in the movinand cache. ANY DC power regulator will have some capacitance, and will probably do that a little. Even an HD will probably get a ms extra write time from it's onboard cache after the AC cuts off, so what? Since whatever is stored there was abruptly truncated by the power loss to the CPU this wont help anything (unless the movinand is somehow smart about it and probably must be aware of how the fs works). Again, nobody has even so much as claimed this happens or acknowledged that it must.

Now it's one thing to say several of you have had good luck with ext2 (fine ) and quite another to keep saying well you can PROVE it because of different reasons and then dodge criticism of those reasons with other reasons.

Evidence from supercurio says the capacitor doesn't work for ext4 (which I'd be interested to know if it does), so I have no reason to believe it works for ext2 where most drive backup power schemes probably aren't even intended to help.

Fine you like ext2 anyway and it seems to work for you. THEN why don't you just SAY THAT in the first place.

That is NOT a defense for unproven ideas like that the capacitor helps for ext2, and certainly not a defense for any pretense that this is indisputable.

BTW hardcore posts options that are fastest or his favorite and calls them factually "optimal" without qualification. I allow some poetic license, but if you want to say I should rigorously trust this as a source for why the cap works (when one of those options can't possibly even be made up for by a cap), well no, sorry I don't.
[Galaxy S I9000 Q&A, Help & Troubleshooting] DamianGto:
Its up to you to believe what you want. But you ignore test that has been done by many people and its very clear that on data its alot harder to get file system corruption then on other partition.

Per design it very logical that its kind if safety on the data, to make sure the user data don't get wiped.

**DamianGTO Steam kernel. 350MB Ram. 500HZ. ext2/jfs . js3 base**
[Galaxy S I9000 Q&A, Help & Troubleshooting] appagom:
Well that's an obvious and functionaly meaningless statement.
[Galaxy S I9000 Q&A, Help & Troubleshooting] DamianGto:
And your sentence is better then?

It don't say anything to the subject.

There are persons here that ask things but they never accept anything. For they don't understand what it is.

OP did stop writhing for he did not understand and he was wrong. He did write in a couple of tread and top developer just sad they have tested it and it was safer on data. Like i do say..

**DamianGTO Steam kernel. 350MB Ram. 500HZ. ext2/jfs . js3 base**
[Galaxy S I9000 Q&A, Help & Troubleshooting] DamianGto:
Well you still don't get it?

You will not see it in a Samsung service manual. Why?

They don't need to have it.

You need to seek up through manufactured of the chip and see that.

The only thing you prove is you lack to understand things.

Also Steve jobs is not a developer. He never been, but he knows how he want things to work.

You say all top developer lie here. Just for you can't find the information you seek.

Right now you are just funny.

Its also you that misleading people that ext2 is unsafe on data. You ignore the fact many 10000+ use it on the phone without any problem

Don't forget that all that use oclf do use ext2.

So just stop your lies.

**DamianGTO Steam kernel. 350MB Ram. 500HZ. ext2/jfs . js3 base**
[Galaxy S I9000 Q&A, Help & Troubleshooting] Auzy:
WTF are you even talking about? I never said all top developers are fools. I simply said, some people don't test things, and even the best of developers can mess in.

In your useless bumblings, you now have said it wont be in the schematics and you must check the datasheets. HOW THE F*** can you know what the circuits are like without schematics?

Are you sure your facilities in your head are working correctly? YOU NEED TO BE BANNED FROM XDA!!! You have seemingly no means of knowing what caps are on there, and where they are located without schematics or opening the device, and even then, you need an oscilloscope to test if your claim is true.

To put it bluntly,

damianGTO CLEARLY LIED ABOUT TESTING THIS CLAIM

. He is not interested in furthering actual knowledge here on XDA. He is simply interested in seeming knowledgeable. Never, in all of his time at XDA has he ever proven any claim, the furthest he has ever gone in doing so, was posting SNR values for his GPS.

tl;dr: I believe this claim should be reset to "untested", and "plausible, but just as likely to be a lie". There is no proof it has been tested, and seems mostly untestable. DamianGTO should be banned from XDA. Admins need to step up and request he proves his claims, because the claims are becoming embedded in the development community and are actually pushing users/development offtrack.
[Galaxy S I9000 Q&A, Help & Troubleshooting] DamianGto:
Please. Its has been tested. Can't you read? Hardcore and supercurius did test the all partion on the phone and they did find that The data partition was safer then the rest.

Its not my foult that you don't understand that. And yes they are top.developer that you claim they don't know what they do.

You also claimed that gps was a hardware error and you could not get a working unit. You was wrong on that to.

If you have read anything the last 1-2 month then you should know i was right on that. The gps is better for most people. You can also tweak the driver and remove some debug code that is interfere with the reading of the gps unit.

If you don't like what i do and say then just stop reading it and bugging me with things you don't understand. I will not help you to get information you want.

The bottom line. Is your data safer on the data partion then the other partion?

The answer is YES..

That has been confirmed by me, hardcore, supercurius, ryanza and many more.

**DamianGTO Steam kernel. 350MB Ram. 500HZ. ext2/jfs . js3 base**
[Galaxy S I9000 Q&A, Help & Troubleshooting] DamianGto:
Well you ignored all other thing i did test and other. You wanted a 100% mytrack accurately on Google map. That don't exist.

Even if you make a 100% you still has the issues that the track will differ when you change different layer in Google map. This is known on Google and all other phones.

About this topic you still don't get it and you have still zero prof yourself that is wrong.

You still say Ext2 on data is very unsafe. That's a lie and you know it.

That's why you don't answer object that question.

You also ignore the fact of all 100.000+ downloads of oclf that use ext2 on a loopback on rts.

I know ryanza did have around 30-50 system user had reported to corrupted the system for them.

And that on every section 100.000 downloads.

If you know anything about file system you should know that's a very very good result.

I also know many use my kernels without any problem with ext2.

Do a test yourself and publish you test results. But you are to lazy and i guess it way over your head.

Do something for this community also. I do develop 2 kernels and a program. What the **** have you done more then whining???????

So stop crying and face the facts.

Im done with you and you are now on my ignore list.

**DamianGTO Steam kernel. 350MB Ram. 500HZ. ext2/jfs . js3 base**
[HD2 General] memstick:
-----------------------------------------------------------------------

SOLVED

Thanks to all the helpers; it turned out that this was the problem

-----------------------------------------------------------------------

Hello,

I've tried to search around for a solution to this problem for a few hours, so I'll dare to ask my question in a new thread ;)

To make things short! I'm trying to reset

absolutely everything

to the way it was when I got the phone; radio, stock ROM, bootloader etc because I experience trouble with the phone. The problems started after I used the HTC program from the HTC website to reinstall windows mobile (for the interested, more on that in the next section). I am now trying to flash LEOIMG.nbh to the phone via the bootloader - but nothing just plain happens. I am 120 % certain that I've done everything correctly - formatting SD card to FAT32, load LEOIMG.nbh to it (and not LEOIMG.nbh.nbh, or something else) - it just won't start, and displays the tri - color screen. Says something about 2.08 HSPL, so I think the bootloader version is correct.

So, for the interested - after using Android for a few days I decided I wanted to use WM because it's better for me. So as stated above, I used the HTC installer from the HTC website to install windows mobile over some custom ROM. But having trouble with the wifi, I think it didn't install the correct radio version - do you think I am correct? In any case, I decided I wanted to do it the correct way this time, and extract the RUU_signed file to SD card and go.

Some extra info...

When starting bootloader, it says

PB81100 HX-BC

SPL-2.08.HSPL 8G XE

0x05

CotullaHSPL 0x40

Numbers on HTC logo

R 2.15.50.14

G 15.42.50.11u

D 3.14.04666
[HD2 General] kurt-willems:
Just some questions;

- Witch stock Rom are you trying to flash over SD?

- Witch size is your SD-card?
[HD2 General] memstick:
The stock ROM I am trying to flash, I got from the HTC support website

*I was not alloved to post links to external website, but it was supposed to be here ;-))*

So I've downloaded the latest ROM upgrade (in Norwegian, "ROM oppgradering" on the site) using a norwegian serial number I found in another thread. I've opened it with winrar, and extracted the RUU_signed.nbh file.. Does this answer you question? In one of the tutorials to reset the phone said for me to "download a RUU_signed.nbh file from *here*", but there were so many different files in there... So I just downloaded the official newest ROM upgrade from the HTC website.

My SD card is of size 16 GB, but right now I just tried with another one of 2 GB size. No change........
[HD2 General] truc007:
Why do you used a serial number which is not yours? The phone is stollen? (just kidding)... As an advice, if you want to be sure to flash the correct ROM use your own serial number on the HTC website.

If you bought your phone in another country (I've done this... from a country I can't even read a word) then put back in the original language.

When back to "original" you can always flash again the hardspl then the ROM you like in Norvegian.

Anyway with the info provided the radio has not been flashed.

info: when you say the radio flash through WiFI... nothing will never be flashed via Internet (cable or WiFi). It's downloaded on your computer then (and only then) flashed to your device.

Question: could your phone can access the SD when in your actual OS?

Idea: flash back to WM6 via USB then try again. It seems you're doing all good but that the SD is not recognized.
[HD2 General] memstick:
To be honest, I used the serial number on the forum because I couldn't be arsed to remove the battery.... :-))

I think you've misunderstood me a bit; I've not tried to flash the phone over wifi...

So, any suggestions as to what could be the reason for the bootloader not starting LEOIMG.nbh?
[HD2 General] truc007:
That's a good reason!!!

No make sure your phone access the SD. You're actually under Anrdoid or WinMo? Honnestly I don't understand your problem (I mean I understand your problem but can't understand why... very usefull post so) :rolleyes:
[HD2 General] truc007:
euh... by the way. The only way to go out of the bootloader if you don't flash is to remove the battery no?:confused:
[HD2 General] memstick:
I'm trying not to get into reasons to make the post short and consise; suffice to say I got some troubles (memory leak, wifi) under winmo 6.5 after I've been doing some flashin. So I want everything back the way it was - radio, bootloader, winmo 6.5. Just as if I got it for the first time! I

think

after all the posts I've been reading this can be done by flashing that LEOIMG.nbh from som official stock rom with the bootloader.

BUT ---- the bootloader doesn't load LEOIMG.nbh!
[HD2 General] truc007:
You think 100% right.

I'll do the test on mine and post if it works or not (I'll only flash a radio, sorry but don't want to erase all my data).
[HD2 General] truc007:
Ok, I download radio 50.14 from here:

http://xdaforums.com/showthread.php?t=611787&highlight=radio

Rename exactly as you write in the post LEOIMG.nbh

Put on the

root

of my SD

Power the phone while holding vol down.

My phone asked directly if I want to update (so I pressed vol down to cancel).

You can try with the same file to see if the file you have is corrupted.

If it's the same... SD access problem??? So HW problem... not good.

You can try to reflash the HSPL just in case.
[HD2 General] truc007:
Don't know if it will help but my HSPL gives a different info:

PB81100 HX-BC

SPL-2.08HSPL 8G XE

0x05

CotullaHSPL 0x30

So all is the same except I have 0X30 and you 0x40

My HD2 is a European on (non-TMOUS).
[HD2 General] memstick:
Tried reflashing the HSPL. I noticed something interesting actually..

The screen flashes grey for about 100 ms! So when I enter bootloader with <vol down>, it shows tricolor screen, then flashes grey, then comes back into tricolor... Think I read something similar in another post...

Thanks for trying so hard to help mister! I don't know if it is my english or anything, but I'm trying to flash the entire stock ROM as described in another tutorial here (still can't post links...), not just the radio..

If I knew which radio was the correct one for me, I'd just flash that one instead, but I have not found any info on this anywhere..

I'll see if I can format the SDcard to FAT32 once more and try again..
[HD2 General] memstick:
Finally!

I did a complete format (not a quick one) in windows on my 2 GB card, and now it is working. Think the quick format thing was to blame for this.... As we've all been warned from before.

It's flashin' now, so I'll give you a holler if something else is up ;))
[HD2 General] truc007:
Good to hear that!

You learned me something with your format.
[Galaxy Tab  Android Development] acolwill:
Since we have a lot of users here with no real means of doing automated proper backups of their tabs outside of ClockworkMod, or manual backups using RotoBackup, I've decided to release my implementation of a backup routine to XDA.

It's based upon RotoBackup and thus requires full SU access on your Tab.

It also requires Heimdall and ADB to be working if you wish to restore a backup fully.

The routine currently only supports RFS filesystems, EXT4 support may be added later!

I have tested this as much as I can, and I do hope that it works for everyone who tries it.

It is windows only, however if someone wishes to redo the script as a shell script feel free!

--

Down to the attachments.

TaBackup.zip

- TaBackup.cmd : Full tab backup and restore script

- KernelBackup.cmd : Kernel backup and restore script

GTab-Heimdall_1.1.1.7z

- WORKING Heimdall 1.1.1 which is required if you wish to RESTORE

- WORKING USB drivers for DOWNLOAD MODE, required for Heimdall

Both freely available from https://github.com/Benjamin-Dobell/Heimdall

Extract the zip to a directory, preferred directories are;

C:\GalaxyTab\Backups for TaBackup.cmd

C:\GalaxyTab\KernelBackup for KernelBackup.cmd

You _can_ change these defaults by editing the script and changing line 8

You need ADB

WORKING

, either from the same directory as TaBackup, or from your system PATH

Due to the hasty modification of TaBackup last night to create KernelBackup, there is legacy code floating around which requires heimdall.exe to be present in the same directory as the backups... I may change this at a later date.

It IS possible to have both backup locations the same, e.g. C:\TaBackup

with both scripts in that directory, with Heimdall. You just have to remember which backup directory is just a kernel backup only.

--

Good luck, and happy hunting!

--

Changelogs:

TaBackup 0.5

First public release

Various logic fixes

Idiotic spelling mistake which prevented a restore!

KernelBackup 0.1

First public release
[Galaxy Tab  Android Development] acolwill:
Reserved for Future Use
[Galaxy Tab  Android Development] o_tiger:
Perfect - will try!
[Galaxy Tab  Android Development] cbb77:
Thanks! This saved me from creating a script myself. I am anal about backups so this is perfect. So far I have only tested the standard backup (it's running as I type this and then will test the Kernel as well. One thing to note, the script requires that you adb installed / path defined in your system variables. Originally it would not work for me as I continued to get unknown command. I have successfully used adb commands to execute the backup before, but only executed it straight from the directory where I had adb installed. Once I added the path to adb in my system variables then it worked great.
[Galaxy Tab  Android Development] acolwill:
Ah yes, ADB pathing :|

I may try and do some rudimentary checks in the scripts for ADB