Active Topics
-
List of well performing apps on Leste (35)
to Maemo 7 / Leste by smatkovi - 23 hrs, 47 mins ago -
Porting apps to Leste (43)
to Maemo 7 / Leste by teroyk - 1 day, 6 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (13)
to SailfishOS by edp17 - 1 day, 21 hrs ago -
Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (79)
to SailfishOS by edp17 - 1 day, 21 hrs ago -
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 2 days, 3 hrs ago -
Maemo repository (5)
to Community by dredlok706 - 4 days, 22 hrs ago -
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 5 days, 1 hr ago - more...
 |
bradvesp |
2017-09-13
, 23:04
|
|
Posts: 71 |
Thanked: 112 times |
Joined on Aug 2010
@ USA
|
#1
|
The permissions to MyDocs files changed this morning to root without my authorization. I don't have root access set up on the system without flashing to R & D Mode (really I thought it would prevent this kinda tampering). Any idea about commands to change the permissions back to a lower level user? My usb port's broken and I don't seem to be able to use the flasher.
| The Following User Says Thank You to bradvesp For This Useful Post: | ||
 |
|
2017-09-14
, 04:51
|
|
Posts: 6,453 |
Thanked: 20,983 times |
Joined on Sep 2012
@ UK
|
#3
|
You don't need R&D to get root access. Just install rootsh. But what do you mean your permissions changed? How did you find out?
The most likely cause is a file system corruption. The OS then mounts the volume as read only, giving only root the write access. Since MyDocs is FAT, the usual remedy is attaching it to a Windows PC in Mass Storage mode and running a disk check on the PC. You could try fsck on the phone but that is less likely to guarantee a success. In some cases it may make the situation worse.
The most likely cause is a file system corruption. The OS then mounts the volume as read only, giving only root the write access. Since MyDocs is FAT, the usual remedy is attaching it to a Windows PC in Mass Storage mode and running a disk check on the PC. You could try fsck on the phone but that is less likely to guarantee a success. In some cases it may make the situation worse.
__________________
Русский военный корабль, иди нахуй!
Русский военный корабль, иди нахуй!
| The Following 4 Users Say Thank You to pichlo For This Useful Post: | ||
|
|
2017-09-14
, 20:28
|
|
Posts: 71 |
Thanked: 112 times |
Joined on Aug 2010
@ USA
|
#4
|
Originally Posted by sicelo
I wasn't able to save anything to the folders there.
MyDocs is FAT by default ... so i wouldn't worry about permissions. What problem is it causing you?
It seemed to have fixed itself. Maybe after turning the N900 off to change the battery. The permissions read as user:root. It was root:root for a time.
| The Following User Says Thank You to bradvesp For This Useful Post: | ||
|
|
2017-09-14
, 20:34
|
|
Posts: 71 |
Thanked: 112 times |
Joined on Aug 2010
@ USA
|
#5
|
Originally Posted by pichlo
I think that's exactly what happened. I've assumed the corruption was cause by someone trying to tamper with it, tunnel into it, reset permissions, or otherwise access it.
You don't need R&D to get root access. Just install rootsh. But what do you mean your permissions changed? How did you find out?
The most likely cause is a file system corruption. The OS then mounts the volume as read only, giving only root the write access. Since MyDocs is FAT, the usual remedy is attaching it to a Windows PC in Mass Storage mode and running a disk check on the PC. You could try fsck on the phone but that is less likely to guarantee a success. In some cases it may make the situation worse.
Yeah, I recall now something about FAT systems not having permissions. I downloaded software called "Hamster Filer" that gives the following file details: Name, Size, Modified, Owner, Permissions. I was wrong when I've stated "permissions". The details I've mentioned were listed as "Owner".
| The Following User Says Thank You to bradvesp For This Useful Post: | ||
|
|
2017-09-15
, 06:30
|
|
Posts: 6,453 |
Thanked: 20,983 times |
Joined on Sep 2012
@ UK
|
#6
|
Originally Posted by bradvesp
Although remotely possible, it is highly unlikely. The most common cause of FS corruption is an unclean interruption of a write operation. A sudden shutdown or reboot - or a surprise removal of a USB storage. That is why you have to remove cleanly. A dodgy USB port can easily cause problems like this.
I've assumed the corruption was cause by someone trying to tamper with it, tunnel into it, reset permissions, or otherwise access it.
__________________
Русский военный корабль, иди нахуй!
Русский военный корабль, иди нахуй!
|
|
2017-09-15
, 18:31
|
|
Posts: 71 |
Thanked: 112 times |
Joined on Aug 2010
@ USA
|
#7
|
Originally Posted by pichlo
Thanks for the info.
Although remotely possible, it is highly unlikely. The most common cause of FS corruption is an unclean interruption of a write operation. A sudden shutdown or reboot - or a surprise removal of a USB storage. That is why you have to remove cleanly. A dodgy USB port can easily cause problems like this.
Before it happened I was downloading a file from a fairly reputable organization via WiFi. So, the problem wasn't caused by a usb issue. I've downloaded files from there before without any problems.
I'm concerned the problem was cause at the local level (at the WiFi router in my apartment).
| The Following User Says Thank You to bradvesp For This Useful Post: | ||