View Single Post
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#1288
Originally Posted by hrbani View Post
So what is your solution? A complete flashing with wiping?
Yes, flashing will probably correct the problem unless it is a HW problem. In that case all bets are off, and it is even possible that after flashing attempt the device will not work at all any more.

Until some months ago I would have recommended flashing as a normal but a bit overkill solution. However lately there have been some cases of HW problems that make the device unflashable. Also as Microsoft is no longer intrested in repairing or replacing the devices I have to say that flashing is to be done on own responsibility...


Originally Posted by hrbani View Post
Why? May I want you explain its ERROR?

How could I set the partition types to reflect to the actual filesystems present there?
Well it looks to me your mmcblk0p2 id is set to "empty" when it should be 83 "Linux"
Also you mention that you have changed thr FS on your mmcblk0p1 to ext2 but it still says "W95 FAT32" in the partition type.

You can fix those either with sfdisk or fdisk in ubiboot repair mode. (of course being careful)

One other thing I forgot to mention earlier;
The camera being unable to mount. There's a daemon that handles USB disk mount and umount based on the FS export mode (usbmoded) so that apps that need access to the exportable partitions like camera and music player behave consistently.
Sometimes it may get confused and not mount MyDocs even when USB is not connected. Restarting usbmoded or manually triggering USB mode change fixes it OK.
 

The Following User Says Thank You to juiceme For This Useful Post: