Active Topics
-
Firefox with Leste (5)
to Maemo 7 / Leste by teroyk - 1 day ago -
Handbook (2)
to Maemo 7 / Leste by teroyk - 1 day, 23 hrs ago - more...
|
2013-01-31
, 16:53
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#82
|
Originally Posted by Wallace
Allright, I see you got it working
Ok, how to back up?
Disk /dev/sda: 640.1 GB, 640135028736 bytes
255 päätä, 63 sektoria/ura, 77825 sylinteriä, yhteensä 1250263728 sektoria
Yksiköt = 1 * 512 = 512 -tavuiset sektorit
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Levyn tunniste: 0xde82bd27
Laite Käynn Alku Loppu Lohkot Id Järjestelmä
/dev/sda1 63 2047 992+ 42 SFS
/dev/sda2 * 2048 409599 203776 42 SFS
/dev/sda3 409600 613320703 306455552 42 SFS
/dev/sda4 613320704 1250261679 318470488 42 SFS
Disk /dev/sdb: 64.1 GB, 64130908160 bytes
4 päätä, 16 sektoria/ura, 1957120 sylinteriä, yhteensä 125255680 sektoria
Yksiköt = 1 * 512 = 512 -tavuiset sektorit
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Levyn tunniste: 0x00000000
Laite Käynn Alku Loppu Lohkot Id Järjestelmä
/dev/sdb1 1024 112672767 56335872 c W95 FAT32 (LBA)
/dev/sdb2 112672768 121061375 4194304 0 Tyhjä
/dev/sdb3 121061376 125255679 2097152 83 Linux
Now, your /dev/sdb drives are the partitions from the device:
/dev/sdb1 is MyDocs
/dev/sdb2 is /root
/dev/sdb3 is /home
You need to create tar files for backup, and you need to do that as root so that the permissions are kept correctly.
Did your system mount the partitions automatically? If not, then you need to mount them manually, for example:
Code:
sudo mkdir /mnt/mydocs sudo mount /dev/sdb1 /mnt/mydocs sudo mkdir /mnt/root sudo mount /dev/sdb2 /mnt/root sudo mkdir /mnt/home sudo mount /dev/sdb1 /mnt/home
Code:
sudo su ## this is done to get root permissions... cd /mnt/mydocs ## or to the correct directory, whatever... ## now I am assuming that your homedir is /home/wallace... tar -cvf ~wallace/mydocs.tar . ## then, when it's been done, do the other partitions: cd /mnt/root tar -cvf ~wallace/root.tar . cd /mnt/home tar -cvf ~wallace/home.tar . ## Note that there is a single dot (.) as the last character on ## the tar statement... Do not forget that!
The following steps depend on what you would do, but whatever you decide, all the stuff of the device is backed up now.
| The Following User Says Thank You to juiceme For This Useful Post: | ||
|
|
2013-01-31
, 17:26
|
|
Posts: 175 |
Thanked: 81 times |
Joined on Aug 2009
|
#83
|
Originally Posted by juiceme
Thank You,
The following steps depend on what you would do, but whatever you decide, all the stuff of the device is backed up now.
I do not want to flash (for now), only replace /etc/X11/xorg.conf.d/nokia.conf configurating external keyboards file or remove one line from it.
I do not know how to unmount the roofs drive so I can boot...
| The Following User Says Thank You to Wallace For This Useful Post: | ||
|
|
2013-01-31
, 17:48
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#84
|
The command to unmount is "sudo umount /dev/sdb1", and same for sdb2 and sdb3.
Not that of course you must not be in the directory when umounting.
After that, just reboot.
Not that of course you must not be in the directory when umounting.
After that, just reboot.
|
|
2013-01-31
, 18:06
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#85
|
Now, what happens when you boot the device, you will get the so called "big scary warning", the device knows that you have used open mode rescue kernel, and each time you boot you will see the warning.
It is completely harmless, though, even as it says something about voiding your warranty.
What I suggest you would like to do, is the following; It is fairly easy to remove the warning forever, and also set your device to open mode for best performance and tweakability.
It is completely harmless, though, even as it says something about voiding your warranty.
What I suggest you would like to do, is the following; It is fairly easy to remove the warning forever, and also set your device to open mode for best performance and tweakability.
- 1.) First you need to flash the devide totally clean, using the rootfs+emmc flashing. Aftre this the device is in "totally clean state"
- 2.) then, you should disable the "big-scary-warning" forever. This must be done when device is clean as it cannot be done in open mode.
- 3.) After that, you should flash the open mode "aegis-neutering" kernel which gives you capability to run real root.
- 4.) Then, boot again the device with the rescue kernel and restore the backups from tarfiles. This way all your previous settings, files and applications are restored.
- 5.) Last thing to do, remove the few aegis files that store your saved passwords. You need to regenerate these with new open mode keys.
| The Following User Says Thank You to juiceme For This Useful Post: | ||
|
|
2013-01-31
, 19:57
|
|
Posts: 175 |
Thanked: 81 times |
Joined on Aug 2009
|
#86
|
Originally Posted by juiceme
Doing something wrong because it stays in reboot loop with that big fulpage warning. Do I have to disconnect USB cable...
The command to unmount is "sudo umount /dev/sdb1", and same for sdb2 and sdb3.
Not that of course you must not be in the directory when umounting.
After that, just reboot.
| The Following User Says Thank You to Wallace For This Useful Post: | ||
|
|
2013-02-01
, 05:57
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#87
|
Yes, when you boot the device after using rescue kernel, you need to remove the USB cable first.
Which warning is it, is it the MALF warning or the Openmode warning?
If the device shows the MALF warning you need to check for the file "/var/malf" from the root partition (/dev/sdb2). If that is present it means that in boot phase the device has detected that a file has been modified.
The way it is done, is that most of the important binaries and configuration files are hashed and the hash is stored to a refhash list file. (that's /var/lib/aegis/refhashlist)
When the device boots, it will check the hashes of that list against the files, and if there is a difference it will show the MALF warning and refuse tpo boot.
Even if you change back the file you modified, the "/var/malf" may not be removed and the device will again show the warning on the second boot... that's why you need to rehash the modified files and remove the /var/malf file to get the device to boot.
Using open mode is so much simpler, there is no need to worry about MALFfing the device while tuning something.
Which warning is it, is it the MALF warning or the Openmode warning?
If the device shows the MALF warning you need to check for the file "/var/malf" from the root partition (/dev/sdb2). If that is present it means that in boot phase the device has detected that a file has been modified.
The way it is done, is that most of the important binaries and configuration files are hashed and the hash is stored to a refhash list file. (that's /var/lib/aegis/refhashlist)
When the device boots, it will check the hashes of that list against the files, and if there is a difference it will show the MALF warning and refuse tpo boot.
Even if you change back the file you modified, the "/var/malf" may not be removed and the device will again show the warning on the second boot... that's why you need to rehash the modified files and remove the /var/malf file to get the device to boot.
Using open mode is so much simpler, there is no need to worry about MALFfing the device while tuning something.
 |
|
2013-04-22
, 12:49
|
|
Posts: 60 |
Thanked: 34 times |
Joined on Dec 2012
@ St Helens, England.
|
#88
|
Is there any chance that enabling and disabling rd mode will ruin the phone? I don't really understand some of things people are saying in this post. It's probably just me being paranoid but I'm worried that if this method doesn't work, then reflashing won't work.
Also, do I keep the phone plugged in after enabling rd mode when it boots? And then do I disable it while the phone is turned on after I've reverted the tweak? Or do I turn the phone of then disable rd mode?
Also, do I keep the phone plugged in after enabling rd mode when it boots? And then do I disable it while the phone is turned on after I've reverted the tweak? Or do I turn the phone of then disable rd mode?
| The Following User Says Thank You to Callum.Brierly For This Useful Post: | ||
|
|
2013-04-22
, 13:05
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#89
|
Please specify what do you mean by rd mode 
There are various r'n'd flags that can be activated, it would be helpful to know what are you meaning to do...
Most propably you cannot "ruin your device" by whatever you are trying, there are only few sure ways to kill your N9 and most of those are related to playing with CAL.
There are various r'n'd flags that can be activated, it would be helpful to know what are you meaning to do...
Most propably you cannot "ruin your device" by whatever you are trying, there are only few sure ways to kill your N9 and most of those are related to playing with CAL.
| The Following User Says Thank You to juiceme For This Useful Post: | ||
|
|
2013-04-22
, 15:23
|
|
Posts: 60 |
Thanked: 34 times |
Joined on Dec 2012
@ St Helens, England.
|
#90
|
I ran the command 'flasher --enable-rd-mode --set-rd-flags=no-lifeguard-reset' and now my phone is just stuck with a wrench icon on the screen, what do I do? Do I unplug it and then try and boot up?
 |
| Tags |
| nokia n9, reboot loop |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
|
All times are GMT. The time now is 10:29.
Ok, how to back up?
Or I do not want to flash only remove one line from /etc/X11/xorg.conf.d/nokia.conf configurating external keyboards. I do not know how to unmount the roofs drive....
Disk /dev/sda: 640.1 GB, 640135028736 bytes
255 päätä, 63 sektoria/ura, 77825 sylinteriä, yhteensä 1250263728 sektoria
Yksiköt = 1 * 512 = 512 -tavuiset sektorit
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Levyn tunniste: 0xde82bd27
Laite Käynn Alku Loppu Lohkot Id Järjestelmä
/dev/sda1 63 2047 992+ 42 SFS
/dev/sda2 * 2048 409599 203776 42 SFS
/dev/sda3 409600 613320703 306455552 42 SFS
/dev/sda4 613320704 1250261679 318470488 42 SFS
Disk /dev/sdb: 64.1 GB, 64130908160 bytes
4 päätä, 16 sektoria/ura, 1957120 sylinteriä, yhteensä 125255680 sektoria
Yksiköt = 1 * 512 = 512 -tavuiset sektorit
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Levyn tunniste: 0x00000000
Laite Käynn Alku Loppu Lohkot Id Järjestelmä
/dev/sdb1 1024 112672767 56335872 c W95 FAT32 (LBA)
/dev/sdb2 112672768 121061375 4194304 0 Tyhjä
/dev/sdb3 121061376 125255679 2097152 83 Linux
Last edited by Wallace; 2013-01-31 at 17:19.