Page 9 of 9 « First 78 9
Reply
Thread Tools Search this Thread
juiceme is online now juiceme
01-31-2013 , 12:53 PM
Posts: 629 | Thanked: 805 times | Joined on May 2012 @ Finland
#81
Originally Posted by Wallace View Post
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
Allright, I see you got it working
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
Then, go to the mounted directory and make the backup:
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!
Okay, when you have done that, You will have three largish files in your home directory. All of the N9 content is backed up there as a snapshot of the device state.

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:
Wallace is offline Wallace
01-31-2013 , 01:26 PM
Posts: 116 | Thanked: 41 times | Joined on Aug 2009
#82
Originally Posted by juiceme View Post

The following steps depend on what you would do, but whatever you decide, all the stuff of the device is backed up now.
Thank You,

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:
juiceme is online now juiceme
01-31-2013 , 01:48 PM
Posts: 629 | Thanked: 805 times | Joined on May 2012 @ Finland
#83
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 2 Users Say Thank You to juiceme For This Useful Post:
juiceme is online now juiceme
01-31-2013 , 02:06 PM
Posts: 629 | Thanked: 805 times | Joined on May 2012 @ Finland
#84
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.
  • 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:
Wallace is offline Wallace
01-31-2013 , 03:57 PM
Posts: 116 | Thanked: 41 times | Joined on Aug 2009
#85
Originally Posted by juiceme View Post
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.
Doing something wrong because it stays in reboot loop with that big fulpage warning. Do I have to disconnect USB cable...
 

The Following User Says Thank You to Wallace For This Useful Post:
juiceme is online now juiceme
02-01-2013 , 01:57 AM
Posts: 629 | Thanked: 805 times | Joined on May 2012 @ Finland
#86
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.
 

The Following User Says Thank You to juiceme For This Useful Post:
Callum.Brierly's Avatar
Callum.Brierly is offline Callum.Brierly
04-22-2013 , 08:49 AM
Posts: 49 | Thanked: 17 times | Joined on Dec 2012 @ England
#87
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?
 

The Following User Says Thank You to Callum.Brierly For This Useful Post:
juiceme is online now juiceme
04-22-2013 , 09:05 AM
Posts: 629 | Thanked: 805 times | Joined on May 2012 @ Finland
#88
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.
 

The Following User Says Thank You to juiceme For This Useful Post:
Callum.Brierly's Avatar
Callum.Brierly is offline Callum.Brierly
04-22-2013 , 11:23 AM
Posts: 49 | Thanked: 17 times | Joined on Dec 2012 @ England
#89
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?
 
Callum.Brierly's Avatar
Callum.Brierly is offline Callum.Brierly
04-22-2013 , 11:28 AM
Posts: 49 | Thanked: 17 times | Joined on Dec 2012 @ England
#90
Okay, it's now stuck on the boot screen again...
 
Reply
Page 9 of 9 « First 78 9

Tags
nokia n9, reboot loop

« Previous Thread | Next Thread »
Thread Tools Search this Thread
Search this Thread:

Advanced Search

 
Forum Jump


All times are GMT -4. The time now is 05:29 AM.

Contact Us - Home - Archive - Top