YP-R1 Modded Firmware 4.00

[ichimaru.gin]

yep, installed with no problem , and it's working great!

uhm, so you have ever reported this to SAMSUNG R&D? Sad to hear that it can't be fixed, guess i have to bear with this issue

[CrowdAds]

[Lorenz092]

Originally Posted by ichimaru.gin

yep, installed with no problem , and it's working great!

uhm, so you have ever reported this to SAMSUNG R&D? Sad to hear that it can't be fixed, guess i have to bear with this issue

Good that you installed it without problems

Indeed samsung isn't willing to fix remaining bugs at all. Discontinued products!

[ichimaru.gin]

Originally Posted by Lorenz092

Good that you installed it without problems

Indeed samsung isn't willing to fix remaining bugs at all. Discontinued products!

yes, i'm having fun with it right now

Is R1 already discontinued? so there will be no more FW update after the latest 3.07 ?
yea, they (samsung) wll not pay for the R&D team to work on discontinued product

[lebellium]

The R1 has been discontinued for more or less 1 year yet (I got my R1 sample/prototype in July 2009 if I remember well so quite a long time ago!). Its successor is the R2 since October 2011.

The R&D made two firmwares 3.10 and 3.11 after the 3.07 to fix minor issues (music search bug etc) but for some reasons they were never released and will never be released on the Samsung website. I have them but can't share them.
Thus, just enjoy firmware 4.00
Now you won't experience anything new on your R1....unless Lorenzo gets one and work on a Rockbox port?

[ichimaru.gin]

Originally Posted by lebellium

The R1 has been discontinued for more or less 1 year yet (I got my R1 sample/prototype in July 2009 if I remember well so quite a long time ago!). Its successor is the R2 since October 2011.

The R&D made two firmwares 3.10 and 3.11 after the 3.07 to fix minor issues (music search bug etc) but for some reasons they were never released and will never be released on the Samsung website. I have them but can't share them.
Thus, just enjoy firmware 4.00
Now you won't experience anything new on your R1....unless Lorenzo gets one and work on a Rockbox port?

I see.. even though there are still few available in the market, they're just old stock ones.

whoa, so you have the new FW, cool. Yea, I'll be and will always stick with FW 4.00, mainly because of DRK, because I'm a bit careless tho..

an R1 with rockbox will be great! right Lorenzo? but is it possible??
I almost bought an R0 to be rockboxed, but I decided to buy R1 instead.
now you mentioned it, i'm curious on how R0 sounds when it is rocboxed
do they use same audio chip? what do you think Lebellium?

[lebellium]

The R1 is probably rockboxable too as it's very close to the R0. The main differences are the screen and the audio chip ( http://anythingbutipod.com/forum/showthread.php?t=64069 ) .
But for a Rockbox port a motivated developer owning the device is required

[ichimaru.gin]

great compilation of specification you have there lebellium
so R1 uses wolfson chip, nice!

yea, unfortunately lorenzo doesn't have an R1 with him
R1 has done a great job for its sound quality, perhaps if it is rockboxed, the sound will be even better

[Gyotto]

Hi guys, I'm Alberto from Verona. ITALY

I have a BIGGG Problem

I upgraded to your modded firmware 4.00, the battery was 100%.
When I restart the device, it boots and stands on your "SAFE MODE" screen, and does not start.
I can run in safe mode, work on "GHOST" and "ROOT" directories, tryed to use (rename) clean_database in the ../root/drk/, restarting the device, but nothing happens and noway to unstuck it from your "SAFE MODE" screen.

Tryed also "delete_settings", but same result.

Please note that when I run in "safe mode" (by starting + pressing volume +) I can see al folders and modify them, but to power off the device I have to use the "RESET" button, just cannot from the power button.

Please help meeeeee i'm afraid my 9 years old daughter will kill me tomorrow morning

[lebellium]

So you claim that when you power it on while it's not connected to the computer, it only displays the safe mode screen?!

Very strange issue
Try formating the device. If that doesn't work either, please contact Lorenzo, he's the Italian developer of this fw and maybe has better ideas

PS: it's normal you need to press reset to power off the device after using Safe Mode, there is no auto-shutdown

[Gyotto]

thanx Lebellion for your super quick reply

I formatted with windows at FAT32 4096 the R1 folder but nothing, same issue, stucked on SAFE MODE screen.

Also tryed to reinstall the modded 4.00 FW, but no news...

[Lorenz092]

I just hope you press the reset hole
no, of course I'm jocking. As I replied via PM and hw upgrade forum, I have no idea of what it could be exactly the very very strange, issue!
Technically it's a readout of the button module: it triggers safe mode when it read the character \x01 or \x02 (don't remember yet). So this means you should probably try to actually press this button (volume down or up) and le me know!

[ads43]

Hi

My YP-r1 gets stuck on the R1 logo when I boot up.

In the past I have drained the battery, and played with the reset button to get round the problem. However this is not working at the moment.

I have the modded 4.0 firmware on it and I can get into Safe Mode.

I have tried the DRK method above to unbrick. I have also formatted and re-installed the 4.0 firmware with no luck.

Does anyone have any suggestions how I can get it to work again?

Thanks in advance

[lebellium]

Did you try the manual method instead of DRK? That means removing the Sysdata folder from the hidden memory (if you put a modified sysdata there) as well as deleting the "Db" folder and the "EntryList.ent" file.

[ads43]

Originally Posted by lebellium

Did you try the manual method instead of DRK? That means removing the Sysdata folder from the hidden memory (if you put a modified sysdata there) as well as deleting the "Db" folder and the "EntryList.ent" file.

Yes. I don't have the sysdata folder, and I have tried deleting those.

[Lorenz092]

Originally Posted by ads43

Yes. I don't have the sysdata folder, and I have tried deleting those.

Uhm the only thing I suggest is to reformat both internal storage and hidden memory, this solved the issue for a user!

EDIT: to add some details. I remember this guy tested a script I've sent him and starting the OF application got "Segmentation fault", that is, all and nothing. Formatting the memory solved the issue. But only the internal memory, as you correctly did. Not the hidden one, so I'm not sure it will help.
BTW BTW -> hope you formatted it in FAT32 not NTFS Also if the starting script should format it automatically in case of mounting failure...

[ads43]

Too late - I formatted the ghost drive!

Nothing has changed - I am still getting stuck on the R1 logo.

Yes - I formatted in FAT32 (the R1 drive that is)

[Lorenz092]

Originally Posted by ads43

Too late - I formatted the ghost drive!

Nothing has changed - I am still getting stuck on the R1 logo.

Yes - I formatted in FAT32 (the R1 drive that is)

I forward here what I tried with the other guy:

Your problem is really odd. So to test out what's going wrong, I'll send you this script.
you need to create a folder called "scripts" and into it another folder "log" (!! Case sensitive !!)
So having

R1 root
->Music
->...
->scripts
---->log
->...

In the folder scripts put the file in attachment, turn off R1 completely (reset it) and start it again!

So of course then tell me everything you saw and please send me the output of the script (that you find into log)

Thanks in advance, with that I can understand a bit more what's the problem, possibly!

Hey! Now that I see you were the user I helped, weren't you?
Anyway try that (again? ) and send me back the output!

[ads43]

PM sent

[ads43]

Originally Posted by Lorenz092

I forward here what I tried with the other guy:

Hey! Now that I see you were the user I helped, weren't you?
Anyway try that (again? ) and send me back the output!

Please can you PM me your e-mail address so I can send the output file.

Thanks

[Lorenz092]

Okay the problem is awkward. I post there the strange part:

M0001 1890.000 -1.-1 TIMEMGR > Boot System Time : 2000/1/1 0:9:37 M0001 1890.000 --.--.-1.-1: FATAL > ASSERTION_CHECK((tmptm1 = pDate->year - 1900) < BASE_YEAR) || (tmptm1 > MAX_YEAR)) == 0 failed. (file ../../../../../MP3_Muon/Source/Core/TimeMgr/TimeMgr.c, line 80) System Asserted

It seems there is a problem with the year loool pff the only thing I advise is trying to fully empty the battery or so, really no idea! Uhm ... or trying to play with hwclock command and set date. ATM no idea, and no time too! pff...strange!