Disabling Sansa e200 firmware's obnoxious database refreshing

[JEJ]

The FAQ mentions that to disable the refreshing every time you boot the OF, you can:

Download the latest version of sansapatcher and any version of the Sansa original firmware below v1.03.XX. You can use the one dated October 20th, 2007 here. Now connect the Sansa to your PC (make sure it's in MSC mode) and execute the following commands in the command line (Start -> Run -> cmd for Windows users). Make sure that the filenames are correct and both sansapatcher and the .mi4 file are in the same folder. After you are done, SAFELY remove your Sansa. Database-refresh will only be deactivated when you boot into the OF via USB-connection with no microSD card inserted.

sansapatcher.exe -of PP5022.mi4
sansapatcher.exe -d
sansapatcher.exe --install

I researched this PP5022.mi4 file and it appears to me that it is only for the Rhapsody models. Am I right? If I am wrong, where can I get this file?

[Chronon]

Try here:
http://daniel.haxx.se/sansa/mi4.html

[MarcGuay]

What makes you think it's for the Rhapsody models?  It's in a folder called "e200", next to a folder called "e200R".  The reason I ask is because I put that link in the FAQ and hope it's correct.

[ryran]

If you're having so much problems I would think going in and setting the SYSTEM directory to be read-only would be a much easier solution...

[MarcGuay]

Does that method work on the e200 as well?

[ryran]

Ah. I have a c200 and I thought I had read on the wiki faq that it works for both, but now I see that it doesn't actually say that. So I don't know.

[JEJ]

I searched these forums and everytime there was the PP5022.mi4 file, the Rhapsody was emtioned so that's what made me think so. Ok if it works for all e200 models i am going to try it.

[ThaCrip]

i tried that on my e250 and it bricked it... i had to use the 'recovery mode' part of the sansa and use a original firmware file ( http://daniel.haxx.se/sansa/e200/1.02.15a.mi4 ) in order to get it working again as it would constant reboot cycle after doing the method described above.

lesson learned = dont try this lol

p.s. http://www.rockbox.org/twiki/bin/view/Main/SansaE200Unbrick#Recovery_Mode ... that's what i had to use in order to get it working again.

[Chronon]

ThaCrip: I will test this procedure out shortly on my e280.

Now that you have properly downgraded to version 1.02.15a does the bootloader properly disable the OF's database rebuild?  I never had to do anything special for this to work because my Sansa e280's firmware is already 1.02.xx. 

[ThaCrip]

yeah i think the database is automatically disabled now after i reinstalled rockbox with bootloader etc etc.

cause my firmware that came with my refurbished one was 1.02.18A.

[robin0800]

I Think The Problem Is Despite the good intensions of the wiki page the diferent firmwares behave differently and what works for one gets broken in the other.
As no change logs exist this problem is not helped.
On the c200 page there is a firmware table that is a part solution to the above problem.
It is indended to fill it in to show which firmware does what.

[Chronon]

Can you clarify what you mean, robin0800?  What do you mean by "what works for one gets broken in the other"?  Are you referring to the existence of different hardware versions for the e200?  (E.g. some units have no FM tuner.)

I will have to test at a later time.  I seem to have misplaced my Sansa at the moment.   

[robin0800]

Are you referring to the existence of different hardware versions for the e200?  (E.g. some units have no FM tuner.)

No this is a problem, at least on the c200, of different firmwares behaving differently.
I'm hopeful that when file transfer & charging is fixed the OF will not be needed and all these problems will disappear.

[Chronon]

I seem to be missing your point slightly.  It sounds like you're saying that "upgrading" to certain versions of the Sandisk firmware will result in the endless boot cycle.  I was not aware of this.

[robin0800]

There are many problems, C200, 1.01.05 and 1.01.06 have no usb setting, 1.01.07 will not boot with a microhdsc fitted 1.01.06 has no problem with this.
Hence the table in the FAQ thou its not up to date.