Untrusted software found on mass memory?

Oh no, I see that recent firmware versions prevent access to the mass memory in data transfer mode.

I guess I'm stuffed then.

Is there a way of solving this problem?

It must be a common problem.

Retty wrote:Oh no, I see that recent firmware versions prevent access to the mass memory in data transfer mode.

In Mass Storage mode (with USB data cable) your PC can display the entire contents of any memory cards or the N95-8GB mass memory. This will show up as a new PC drive letter.
This is not somethng Nokia are likely to remove with any firmware upgrade (but they could do so just to prove me wrong!)

You probably need to go the your PC's control-panel and set Folder-Options to [I][I]show hidden and system files[/I][/I], then you should be able to see Private folder etc.

When these games are JAVA based , install Nokia MIDlet Restorer : http://europe.nokia.com/get-support-and-software/product-support/nokia-n95-8gb/software
After running MIDlet Restorer , you'll find the App's icons back under Installations . In case you want to delete them , you can do this by highlighting the Icon > Options > Delete

😊 Regards jApi NL

jApi NL wrote:When these games are JAVA based , install Nokia MIDlet Restorer : http://europe.nokia.com/get-support-and-software/product-support/nokia-n95-8gb/software
After running MIDlet Restorer , you'll find the App's icons back under Installations . In case you want to delete them , you can do this by highlighting the Icon > Options > Delete

😊 Regards jApi NL

Thanks Dez and jApi NL.

I trid the MIDlet Restorer and it did restore the apps - but it hasn't solved the "untrusted software problem".

I definitely cannot access the "private" directory on the mass memory. Can anyone help?

I connect the phone using the "PC Suite" option that the phone displays when I connect the usb. I can see the mass memory drive but the "private" folder is not there. I have made sure that hidden/system files are displayed but I can't see the folder.

If I use "Data transfer" I get a message sayingt hat it will not be possible to access mass memory during the transfer process. It can not then be accessed.

Is there a way of solving this problem without formatting the mass memory?

In fact would formatting the mass memory even solve the problem?

Retty wrote:
If I use "Data transfer" I get a message sayingt hat it will not be possible to access mass memory during the transfer process. It can not then be accessed.

I think this message comes up when a running app is locking some files. You can't access Mass Memory if some running app is using it.

Have you changed your message store to masss memory? If so, change the store back to internal memory.

Make a list (using applications Manager) of all apps installed in Mass Memory and then work out which ones run automatically at phone boot-up. Stop/disable those apps temporarily.
Apps like virus checkers, call managers, call recording, 3rd-party email apps, auto-profile, auto-theme, task-managers, etc. usually run at all times in the background.

PC Suite file manager will never display system folders like private, so you need to get Mass Memory/Data Transfer mode working and browse from your PC, or put the memory card in a PC card reader and access it from there.

If you are trying to access the private folder in internal memory, then you will need to use an app like X-Plore or Fexplorer, running on the phone itself.

The other option

dez_borders wrote:I think this message comes up when a running app is locking some files. You can't access Mass Memory if some running app is using it.

Have you changed your message store to masss memory? If so, change the store back to internal memory.

Make a list (using applications Manager) of all apps installed in Mass Memory and then work out which ones run automatically at phone boot-up. Stop/disable those apps temporarily.
Apps like virus checkers, call managers, call recording, 3rd-party email apps, auto-profile, auto-theme, task-managers, etc. usually run at all times in the background.

PC Suite file manager will never display system folders like private, so you need to get Mass Memory/Data Transfer mode working and browse from your PC, or put the memory card in a PC card reader and access it from there.

If you are trying to access the private folder in internal memory, then you will need to use an app like X-Plore or Fexplorer, running on the phone itself.

The other option

Thanks.

I've now tried everything I can think of except formatting the memory - and there's no guarantee that will work.

The message store is set to internal memory.

There are only a few programs installed on the mass memory - I've removed the few others that were there. The ones I have left are:

Snakes
ActivityMonitor
NSTAActivityServer
RDAccelerometer
MIDletRestorer
and two untrusted Java games (which aren't going to run on start up).

When I connect in Data Transfer/mass memory mode I get a message telling me "USB data transfer mode activated. Mass memory may not be used during this time."

I can't access the mass memory to even back it up before I try to reformat.

Is there another way of accessing the private folder on the mass memory?

Retty wrote:NSTAActivityServer
.
.
.
I can't access the mass memory to even back it up before I try to reformat.

Is there another way of accessing the private folder on the mass memory?

Any app containing the word server as part of it's name probably runs all the time in the background, locking Mass Memoryas in-use. Try uninstalling that.

PC Suite and File Manager don't show hidden or system folders, but 3rd party apps like F-explorer or X-Plore do. They are both FREE.

dez_borders wrote:Any app containing the word server as part of it's name probably runs all the time in the background, locking Mass Memoryas in-use. Try uninstalling that.

PC Suite and File Manager don't show hidden or system folders, but 3rd party apps like F-explorer or X-Plore do. They are both FREE.

Thank you.

I uninstalled it - it warned me that other apps might not work correctly if I did - but it still has not solved the problem.

I now only have Snakes (!), RDAccelerometer, MIDletRestorer and two Java games on the device. None of these, surely, activate at start up.

I don't think I'm going to find a solution to this and I'm starting to conclude that there may be a hardware problem of some sort (the distinction between software and hardware seems less clear than it should be with this device and software installation problems can cause unsolvable problems it seems).

Also a bit disillusioned with the Symbian OS. I don't want to mention Windows but at least with that OS this wouldn't happen (there would be a way of simply looking at and intercepting startup processes).

I've lost a lot of the apps I had installed and the problem still isn't fixed.

I suspect even formatting the mass memory isn't going to solve it - just a feeling.

Did you try a hard reset ? You can try *#7370# or " Vulcan Death Grip " , see this thread : http://www.allaboutsymbian.com/forum//forum/thread/81021/
Private Folder you cannot change anyway , unless illegal .

😊 Regards jApi NL

jApi NL wrote:Did you try a hard reset ? You can try *#7370# or " Vulcan Death Grip " , see this thread : http://www.allaboutsymbian.com/forum//forum/thread/81021/
Private Folder you cannot change anyway , unless illegal .

😊 Regards jApi NL

I'm getting nowhere fast.

I now have nothing on the mass memory and I'm still getting the "installing" and "untrusted software found" error. And mass memory is still not available in data transfer mode.

I tried *#7370# and it didn't solve the problem either.

If I had known about these sorts of problems to be honest I would have stuck with Windows. It really is bad that this os lacks troubleshooting features - there's no way of knowing which process is causing the problem! Crazy!

What can I do next - reformat mass memory before trying a reflash?

That sounds like a nuclear option.

Is there a hack I can use to try and manually delete the problem?

Retty wrote:I'm getting nowhere fast.

I now have nothing on the mass memory and I'm still getting the "installing" and "untrusted software found" error. And mass memory is still not available in data transfer mode.

I tried *#7370# and it didn't solve the problem either.

If I had known about these sorts of problems to be honest I would have stuck with Windows. It really is bad that this os lacks troubleshooting features - there's no way of knowing which process is causing the problem! Crazy!

What can I do next - reformat mass memory before trying a reflash?

That sounds like a nuclear option.

Is there a hack I can use to try and manually delete the problem?

Hmm, curious. If I try to format mass memory I get a message telling me "mass memory in use by another application. Format anyway".

It doesn't bother to tell me which application is using it!

But how can an application be using mass memory if there is not application on the mass memory?

Could it be a virus?

Retty wrote:If I had known about these sorts of problems to be honest I would have stuck with Windows. It really is bad that this os lacks troubleshooting features - there's no way of knowing which process is causing the problem! Crazy!

I'm sorry you are still having problems, despite the best efforts of several forum users to help you.
However, your problem does seem quite unusual/rare, and it's totally unfair of you to blame the entire O/S.

I don't think re-flashing the firmware will help, but there's no hard you trying. (but don't restore a backup afterwards!)

If you have formatted both the Mass Memory and Internal memory or if the vulcan-death-grip (total reset) doesn't help, then you may indeed have a hardware issue.
Providing you have not de-branded your firmware (invalidating the warranty), you can take or mail the handset to an NCC for free repair.

dez_borders wrote:I'm sorry you are still having problems, despite the best efforts of several forum users to help you.
However, your problem does seem quite unusual/rare, and it's totally unfair of you to blame the entire O/S.

I don't think re-flashing the firmware will help, but there's no hard you trying. (but don't restore a backup afterwards!)

If you have formatted both the Mass Memory and Internal memory or if the vulcan-death-grip (total reset) doesn't help, then you may indeed have a hardware issue.
Providing you have not de-branded your firmware (invalidating the warranty), you can take or mail the handset to an NCC for free repair.

Thanks.

You say format the Internal memory - I can't see an option to do that (is that the *# reset?)

I did come across a post by someone else about a year ago who seemed to be having a similar problem - they couldn't find a solution either and said that that they were sending it for repair.

Is there any way that I can access the private directory without being able to connect in mass memory mode?

This is getting crazy. I installed Fexplorer and sure enough I can see the "private" folder listed on the mass memory - but when I try to enter the folder the Fexplorer application exits. The only folder it will not let me get inside is the private folder! :con?

The big problem is not that the "installing" and "untrusted software" error displays on start-up (this would be just an annoyance) but that I can't access the phone in "mass memory" usb mode.

I'm sure there's a software process kicking in at start-up that's causing this problem but I can't think of a way of finding it.

Retty wrote:You say format the Internal memory - I can't see an option to do that (is that the *# reset?)

Is there any way that I can access the private directory without being able to connect in mass memory mode?

format internal memory with *#7370#

You really should be able to access the mass memory's private folder using Fexplorer. There is a good chance you have a hardware fault after all.

dez_borders wrote:format internal memory with *#7370#

You really should be able to access the mass memory's private folder using Fexplorer. There is a good chance you have a hardware fault after all.

I've managed to banish the "installing" and "untrusted software" message on start-up.

I manually removed (using app manager) all the progs I could then formatted the mass memory then formatted the internal memory.

No choice - I've lost all the progs I had on the mass memory and the internal memory (including one I paid �50/$90 for).

But - I still can't access mass memory in data transfer mode. I still get a message telling me "... mass memory may not be used".

I strongly suspect that there is an item of software in the v31 firmware which is using the mass memory and preventing connections. There seems to be a lot going on at startup including the awful "My Nokia" adware prog which I can't remove. I bet this is the same reason Fexplorer exits when trying to access the private folder.

It is odd because in every other way mass memory is accessible.

Other people must be having this problem *if* it is not a hardware problem. And as you say it could be.

It's still in warranty so I think I will get it checked.

If the service centre can repair it in hosue it would be good to know how. I think this must be a common problem and maybe down to the fact that corrupt installations can cause os software problems which cannot be easily corrected by the end user.

I don't know if there's going to be an update beyond v31 - which is now nearly a year old.

The firmware seems to be stable in other respects but this problem is more than just a nuisance.

Has anyone managed to solve the "mass memory may not be accessed..." problem?

last question before I get it repaired 😞

I've read that Fexplorer does not allow access to the private folder - it only shows the name of the private folder when viewing the root directory. Is this the case?

I've had a look in some of the other system directories and, wow, is there a lot of historical baggage in them - all sorts of file fragments from orphan apps and probably other things too.

I guess that the some of the files in these directories are causing the problems.

Neither hard reset nor mass memory format nor flashing can restore the phone to virgin factory state - by clearing out all of these files.

I guess (or hope) that a service centre will be able to but who knows.

I'm just glad I didn't unbrand the phone.

Retty wrote:I've lost all the progs I had on the mass memory and the internal memory (including one I paid �50/$90 for).

But - I still can't access mass memory in data transfer mode. I still get a message telling me "... mass memory may not be used".

I strongly suspect that there is an item of software in the v31 firmware which Has anyone managed to solve the "mass memory may not be accessed..." problem?

Contact the company you bought the $90 app from, they should be able to send you a new install file/serial number Free.

I doubt your issue is a firmware security enhancement, or this thread would have 100s of Me Too! responsed from other owners - but there are not.

I think you're next move would be to have the handset checked under warranty.

Best of luck, let us know what happens.

Retty wrote:
I've read that Fexplorer does not allow access to the private folder - it only shows the name of the private folder when viewing the root directory. Is this the case?

In the past, Fexplorer could read all folders and files, but not write/delete inside a systems folder.

@retty . However it would be peculiar , I was thinking a security setting could interfere with the mass memory connection .
1) I don't know for the N95 8GB , but the other Phones have a password security for MassMemory . If so , disable the password .
2) most weird , but worth a try : disable Remote Lock (by sending SMS) in : Phone and SIM security . And reboot Phone . I have been reading this issue sometime ago , it worked on a problematic Phone .
Maybe it helps .....

😊 Regards jApi NL

Thanks again!

This is getting silly - it's certainly some sort of software installation/process problem.

I've tried plugging the phone in to an old Windows 2000 workstation and, sure enough, the message flashes on the screen "mass memory may not be used during this time".

Yet the phone contents is readable as a Windows drive!

I've tried it again with XP, Vista and Windows 7 (three PCs in total including the Windows 2000 one) and it is only readable on the Windows 2000 PC.

:con?

Retty wrote:Thanks again!

This is getting silly - it's certainly some sort of software installation/process problem.

I've tried plugging the phone in to an old Windows 2000 workstation and, sure enough, the message flashes on the screen "mass memory may not be used during this time".

Yet the phone contents is readable as a Windows drive!

I've tried it again with XP, Vista and Windows 7 (three PCs in total including the Windows 2000 one) and it is only readable on the Windows 2000 PC.

:con?

Wow, connecting the device to the Windows 2000 PC seems to have corrected the problem! 😮

It must have been some sort of software problem although quite what I don't know: accessing the "private" folder using the Windows 2000 PC seems to have allowed the phone to connect using XP, Vista and Windows 7.

I still get the "mass memory may not be accessed" message but despite this it is available.

I'll approach this device with caution in the future in terms of what I install on it.

I think the Symbian OS is a bit fragile because unlike Windows the system files aren't easy to fix when something goes wrong.

I still don't really know what happened for this problem to correct itself.

Thanks for posting your "solution" . It's right not to touch the Symbian firmware , I think , unless being a develloper . So I am still wondering from the beginning why you wanted to de/edit the private folder . No answer needed btw !
Anyway some software shoul be the reason , but I am glad you are be able to access the massmemory allright .

😊 Regards jApi NL

Retty wrote:
I think the Symbian OS is a bit fragile because unlike Windows the system files aren't easy to fix when something goes wrong.

If mass memory works fine on one PC and not on others, then it would have to be an issue with the PC O/S or PC drivers and not the phone's OS.

dez_borders wrote:If mass memory works fine on one PC and not on others, then it would have to be an issue with the PC O/S or PC drivers and not the phone's OS.

Thanks jApi NL and Des.

Part of the reason why I was trying to access the private directory was because most of the solutions to the "untrusted" software problem suggest that this is the way forward - deleting a theme folder from the directory.

This wasn't my problem. Uninstalling everything from mass memory and from internal memory (except essentials) didn't solve the untrusted software problem. Even formatting mass memory didn't solve the problem by itself. Formatting mass memory, wiping everything (other than essential software) from the phone memory and resetting the phone eventually (oddly after a number of attempts) removed the untrusted software problem.

In terms of the connection problem. It's very logical to think that the problem was with the XP/Vista/Windows 7 drivers rather than with the phone itself. The fact is though that once the Windows 2000 PC connected to the phone all of the other OSs (on two different PCs) were also able to connect. Nothing else changed.

It was only after the Windows 2000 connection that I notice that the "untrusted software" problem had gone - I wonder if there was a connection between the two.

I do think that it is more difficult for end users to solve Symbian problems than it is to solve Windows Mobile problems

It is a great device and given that I don't need touch screen it does everything I want and need. Its processor power and 3d graphics are also better than the N97 which means that there is no incentive to "upgrade".

I would recommend Symbian but I think Windows is easier to troubleshoot.

I'm just glad I didn't de-brand the phone because if I had needed a repair I would have been out of luck.

Retty wrote: The fact is though that once the Windows 2000 PC connected to the phone all of the other OSs (on two different PCs) were also able to connect. Nothing else changed.

It was only after the Windows 2000 connection that I notice that the "untrusted software" problem had gone - I wonder if there was a connection between the two.

Although the problem went away after a W2000 connection, I think you may have already uninstalled most of your apps and formatted mass memory etc?

Anyhow, glad you have now resolved the issue. 😉