Active Topics
-
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (3)
to SailfishOS by edp17 - 9 hrs, 55 mins ago -
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 1 day, 13 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 2 days, 2 hrs ago -
n770 youtube video (0)
to General by nmdv - 6 days, 1 hr ago - more...
| The Following User Says Thank You to juiceme For This Useful Post: | ||
 |
|
2015-03-09
, 14:19
|
|
Posts: 64 |
Thanked: 66 times |
Joined on Aug 2013
@ Tehran - Iran
|
#1282
|
Originally Posted by juiceme
Hi
So, he can load Harmattan just fine, but not Nitdroid?
Thanks
Yes, it seems that above sentence is completely true, except that in Settins->Device->Data storage->Application data shows something like this message: "is not available in mass storage mod".
Originally Posted by juiceme
he has done this successfully many times and just now started to fail
Is this first time he tries to boot Nitdroid, I mean has he ever before done this successifully and just now started to fail; or never had it work before?
Originally Posted by juiceme
Thanks a lot (like everytime)
The log on failing to mount /dev/mmcblk0p3 is suspicious, but I believe it has nothing to do with this problem if he can boot Harmattan OK; The kernels are anyway on /dev/mmcblk0p2 and the ubiboot config files on /dev/mmcblk0p1 so booting any OS should work just fine.
(And since /dev/mmcblk0p3 is the Harmattan /home mount, if Harmattan works then it sure is mounted correctly at OS boot...)
Originally Posted by juiceme
No unfortunately in this case your suggestion is wrong
Now if I am correct in thinking that he never managed to run Nitdroid before, then the problem is clear;
There is some problem in the Nitdroid setup, for example:
- the /sbin/preinit_nitdroid file is missing, or has not r&x attributes set
- the Nitdroid filesystem image has not been extracted correctly to /home/nitdroid/
- the nitdroid image is wrong or was corrupted at download
One other of our friends said the solution is flashing with box. Is it true?
Thank you very much
|
|
2015-03-09
, 17:08
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#1283
|
OK, then it really looks like there is some problem in the device flash memory, which also affects Harmattan.
Reflashing the device can help, but of course it is fairly drastic way to fix problems as it will wipe all user data from the device, hence I always suggest other possibilities first.
Of course there is always the rare possibility that there is some HW problem in the flash memory, in which case it may happen that the device cannot be flashed and will not work any longer after the flashing attempt...
Reflashing the device can help, but of course it is fairly drastic way to fix problems as it will wipe all user data from the device, hence I always suggest other possibilities first.
Of course there is always the rare possibility that there is some HW problem in the flash memory, in which case it may happen that the device cannot be flashed and will not work any longer after the flashing attempt...
| The Following User Says Thank You to juiceme For This Useful Post: | ||
|
|
2015-03-09
, 18:40
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#1284
|
Originally Posted by hrbani
Could you please ask your friend to run "/sbin/sfdisk -l" as root, I'd like to know what the partition layout looks like.
Hi
Thanks
Yes, it seems that above sentence is completely true, except that in Settins->Device->Data storage->Application data shows something like this message: "is not available in mass storage mod".
| The Following User Says Thank You to juiceme For This Useful Post: | ||
|
|
2015-03-11
, 10:50
|
|
Posts: 64 |
Thanked: 66 times |
Joined on Aug 2013
@ Tehran - Iran
|
#1285
|
Originally Posted by juiceme
Thank you very much
OK, then it really looks like there is some problem in the device flash memory, which also affects Harmattan.
Reflashing the device can help, but of course it is fairly drastic way to fix problems as it will wipe all user data from the device, hence I always suggest other possibilities first.
Of course there is always the rare possibility that there is some HW problem in the flash memory, in which case it may happen that the device cannot be flashed and will not work any longer after the flashing attempt...
as always a perfect and cute answer.
Originally Posted by juiceme
I attached his result.
Could you please ask your friend to run "/sbin/sfdisk -l" as root, I'd like to know what the partition layout looks like.
And one question that is mine:
I executed the command on my phone to see the result. Because, I had flashed my phone by MOSLO before flashing it by cracked Infinity Best (that flashs phones via USB cable without box). Also after flashing phone with Best, I haven't recieved "flashing is complete" message but the line on phone went to the end and doesn't any change in phone and best (and new message) for a long time. So I disconnected phone. After it had booted the camera show this message: "Camera doesn't work in mass storage mode" so I rebooted the phone and it was fixed. recently I changed the format of memory from fat to EXT2. This is the result:
Code:
sfdisk -l Disk /dev/mmcblk0: 1957120 cylinders, 4 heads, 16 sectors/track Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/mmcblk0p1 16 1760511 1760496 56335872 c W95 FAT32 (LBA) /dev/mmcblk0p2 1760512 1891583 131072 4194304 0 Empty /dev/mmcblk0p3 1891584 1957119 65536 2097152 83 Linux /dev/mmcblk0p4 0 - 0 0 0 Empty Disk /dev/dm-0: 0 cylinders, 0 heads, 0 sectors/track sfdisk: ERROR: sector 0 does not have an msdos signature /dev/dm-0: unrecognized partition table type No partitions found
Thanks a lot
with regards
| The Following User Says Thank You to hrbani For This Useful Post: | ||
|
|
2015-03-11
, 13:04
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#1286
|
Originally Posted by hrbani
His partition table looks exactly to the byte like it should.
I attached his result.
So if there is some problem then it is not shown in the partition table.
Originally Posted by hrbani
It looks like the partition types of your device are not correct; however seems there are no adverse effects. (not many software care about partition types, on mounting to external devices you might encounter some funny business
And one question that is mine:
I executed the command on my phone to see the result. Because, I had flashed my phone by MOSLO before flashing it by cracked Infinity Best (that flashs phones via USB cable without box). Also after flashing phone with Best, I haven't recieved "flashing is complete" message but the line on phone went to the end and doesn't any change in phone and best (and new message) for a long time. So I disconnected phone. After it had booted the camera show this message: "Camera doesn't work in mass storage mode" so I rebooted the phone and it was fixed. recently I changed the format of memory from fat to EXT2. This is the result:
)You might want to set the partition types to reflect to the actual filesystems present there.
| The Following User Says Thank You to juiceme For This Useful Post: | ||
|
|
2015-03-11
, 13:19
|
|
Posts: 64 |
Thanked: 66 times |
Joined on Aug 2013
@ Tehran - Iran
|
#1287
|
Originally Posted by juiceme
So what is your solution? A complete flashing with wiping?
His partition table looks exactly to the byte like it should.
So if there is some problem then it is not shown in the partition table.
Originally Posted by juiceme
Why?
It looks like the partition types of your device are not correct;
May I want you explain its ERROR? 
Originally Posted by juiceme
How could I set the partition types to reflect to the actual filesystems present there?
... however seems there are no adverse effects. (not many software care about partition types, on mounting to external devices you might encounter some funny business
You might want to set the partition types to reflect to the actual filesystems present there.
Thanks
| The Following User Says Thank You to hrbani For This Useful Post: | ||
|
|
2015-03-11
, 13:58
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#1288
|
Originally Posted by hrbani
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.
So what is your solution? A complete flashing with wiping?
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
Well it looks to me your mmcblk0p2 id is set to "empty" when it should be 83 "Linux"
Why?
How could I set the partition types to reflect to the actual filesystems present there?
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: | ||
|
|
2015-03-12
, 06:53
|
|
Posts: 64 |
Thanked: 66 times |
Joined on Aug 2013
@ Tehran - Iran
|
#1289
|
Originally Posted by juiceme
Thank you
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.
May I want you explain this:
Originally Posted by juiceme
some sore?
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.
Originally Posted by juiceme
Thanks
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.
And may I want you explain this:
Originally Posted by juiceme
some and how can I do it? By this method the memory is formatted and I need to back up my data before doing this and recovering data after it?
You can fix those either with sfdisk or fdisk in ubiboot repair mode. (of course being careful)
Originally Posted by juiceme
Thanks a lot
One other thing I forgot to mention earlier;
The camera being ... .
|
|
2015-03-12
, 08:04
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#1290
|
Originally Posted by hrbani
You mean the change of partition type?
some and how can I do it? By this method the memory is formatted and I need to back up my data before doing this and recovering data after it?
That does not require formatting or anything, it is just a flag change.
| The Following 2 Users Say Thank You to juiceme For This Useful Post: | ||
Is this first time he tries to boot Nitdroid, I mean has he ever before done this successifully and just now started to fail; or never had it work before?
The log on failing to mount /dev/mmcblk0p3 is suspicious, but I believe it has nothing to do with this problem if he can boot Harmattan OK; The kernels are anyway on /dev/mmcblk0p2 and the ubiboot config files on /dev/mmcblk0p1 so booting any OS should work just fine.
(And since /dev/mmcblk0p3 is the Harmattan /home mount, if Harmattan works then it sure is mounted correctly at OS boot...)
Now if I am correct in thinking that he never managed to run Nitdroid before, then the problem is clear;
There is some problem in the Nitdroid setup, for example: