maemo.org - Talk
Page 33 of 35 « First 233132 33 3435
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)
-   -   Introducing ubiboot N9 (multiboot OS loader) (https://talk.maemo.org/showthread.php?t=89345)

juiceme 2015-03-08 18:02
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by hrbani (Post 1463440)
Hi :)
There is my friend Ubiboot.log and Ubiboot.conf and screenshot from /boot/ and /home/user/MyDocs/boot/.
He couldn't boot Nitdroid, he says the phone goes off after selecting any kernel for nitdroid.
I think kernels and Ubiboot config and ... are true (from blow selection of log)

Am I true?

What is the solution? A complete flash with full wipe the memory?

Thanks a lot
So, he can load Harmattan just fine, but not Nitdroid?
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:
  • 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

hrbani 2015-03-09 14:19
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by juiceme (Post 1463447)
So, he can load Harmattan just fine, but not Nitdroid?
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".

Quote:
Originally Posted by juiceme (Post 1463447)
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?
he has done this successfully many times and just now started to fail :(

Quote:
Originally Posted by juiceme (Post 1463447)
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...)
Thanks a lot (like everytime)

Quote:
Originally Posted by juiceme (Post 1463447)
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
No unfortunately in this case your suggestion is wrong :(

One other of our friends said the solution is flashing with box. Is it true?

Thank you very much :)

juiceme 2015-03-09 17:08
Re: Introducing ubiboot N9 (multiboot OS loader)
 
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... :(

juiceme 2015-03-09 18:40
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by hrbani (Post 1463531)
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".
Could you please ask your friend to run "/sbin/sfdisk -l" as root, I'd like to know what the partition layout looks like.

hrbani 2015-03-11 10:50
Re: Introducing ubiboot N9 (multiboot OS loader)
 
2 Attachment(s)
Quote:
Originally Posted by juiceme (Post 1463547)
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...
Thank you very much :) as always a perfect and cute answer.

Quote:
Originally Posted by juiceme (Post 1463562)
Could you please ask your friend to run "/sbin/sfdisk -l" as root, I'd like to know what the partition layout looks like.
I attached his result.


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
The phone is working good and it hasn't ERROR like y friend's phone. Does my phone has any problem?

Thanks a lot
with regards

juiceme 2015-03-11 13:04
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by hrbani (Post 1463715)
I attached his result.
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.


Quote:
Originally Posted by hrbani (Post 1463715)
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:
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 :D)

You might want to set the partition types to reflect to the actual filesystems present there.

hrbani 2015-03-11 13:19
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by juiceme (Post 1463724)
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.
So what is your solution? A complete flashing with wiping?

Quote:
Originally Posted by juiceme (Post 1463724)
It looks like the partition types of your device are not correct;
Why? :D May I want you explain its ERROR? :o:p

Quote:
Originally Posted by juiceme (Post 1463724)
... 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 :D)

You might want to set the partition types to reflect to the actual filesystems present there.
How could I set the partition types to reflect to the actual filesystems present there?

Thanks :)

juiceme 2015-03-11 13:58
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by hrbani (Post 1463726)
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... :(


Quote:
Originally Posted by hrbani (Post 1463726)
Why? :D May I want you explain its ERROR? :o:p

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.

hrbani 2015-03-12 06:53
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by juiceme (Post 1463727)
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.
Thank you :)


May I want you explain this:
Quote:
Originally Posted by juiceme (Post 1463727)
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.
some sore?



Quote:
Originally Posted by juiceme (Post 1463727)
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.
Thanks :)


And may I want you explain this:
Quote:
Originally Posted by juiceme (Post 1463727)
You can fix those either with sfdisk or fdisk in ubiboot repair mode. (of course being careful) :)
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? :o :p


Quote:
Originally Posted by juiceme (Post 1463727)
One other thing I forgot to mention earlier;
The camera being ... .
Thanks a lot :)

juiceme 2015-03-12 08:04
Re: Introducing ubiboot N9 (multiboot OS loader)
 
:(
Quote:
Originally Posted by hrbani (Post 1463803)


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? :o :p
You mean the change of partition type?
That does not require formatting or anything, it is just a flag change.

hrbani 2015-03-12 12:41
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by juiceme (Post 1463806)
:(

You mean the change of partition type?
That does not require formatting or anything, it is just a flag change.
Yes I mean fixing these problems:
Quote:
Originally Posted by juiceme (Post 1463806)
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.
How I can fix it? I'm sorry that I have not enough knowledge to fix it with anyway
Quote:
Originally Posted by juiceme (Post 1463806)
You can fix those either with sfdisk or fdisk in ubiboot repair mode. (of course being careful)
Thanks

hedayat 2015-03-13 08:23
Re: Introducing ubiboot N9 (multiboot OS loader)
 
To change the partition type using fdisk (I mean the one you can usually find in GNU/Linux OSes), you can run fdisk and then use command 't' to change the type to Linux, for which you should enter '83' (83 is the partition type for regular Linux partitions).

n950 2015-03-30 11:17
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Where can i find Ubuntu OS for ubiboot for my n950?

How to install sailfish OS too with ubiboot?

I have installed zImage_2.6.32.54-ubiboot-02_301013.

coderus 2015-03-30 12:21
Re: Introducing ubiboot N9 (multiboot OS loader)
 
there is no ubuntu for N9, and sailfish installing same way as nemo: repartition and extract image.

n950 2015-03-30 12:36
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by coderus (Post 1465343)
there is no ubuntu for N9, and sailfish installing same way as nemo: repartition and extract image.
Ok but if i want to install nemo and sailfish how can i do?

Nemo is in Alt_OS
Sailfish where?

juiceme 2015-03-30 13:01
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by n950 (Post 1465346)
Ok but if i want to install nemo and sailfish how can i do?

Nemo is in Alt_OS
Sailfish where?
Then you need to repartition the device, just like when you repartitioned it before, when you chipped ALT_OS off from MyDocs.

For example, I have 6 different usable partitions on my device which is the maximum you can do with old-dos-style partitioning to physical and logical partitions.

coderus 2015-03-30 13:04
Re: Introducing ubiboot N9 (multiboot OS loader)
 
juiceme, what about stuff for booting from an image, not partition?

coderus 2015-03-30 13:04
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by n950 (Post 1465346)
Ok but if i want to install nemo and sailfish how can i do?

Nemo is in Alt_OS
Sailfish where?
Alt_OS is just a label of partition

hedayat 2015-03-30 19:16
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by coderus (Post 1465356)
juiceme, what about stuff for booting from an image, not partition?
http://talk.maemo.org/showthread.php?p=1443705
I boot both SFOS and Nemo from image files without touching my partition table (not an 'interesting' idea for a 16GB N9).

juiceme 2015-03-31 08:20
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by coderus (Post 1465356)
juiceme, what about stuff for booting from an image, not partition?
Yes, it is also possible to do that, using the clever hack by @hedayat.

I meant to integrate that into the mainline ubiboot but for the usual reasons of not having enough time have not managed to do it yet :o

n950 2015-04-08 17:46
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Hello,

Where can i download zImage_adb_usb please?

Boxeri 2015-04-10 05:43
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Hello

Somehow during the night my battery had rune out. Now I can't get the phone to start up, presumably because of not having enough power.

The bigger problem is that I can't seem to charge even through Flasher because of ubiboot. I always gives me the following flashing error and just starts up the ubiboot green concole view.
Code:
miika@Desktop ~/Työpöytä/Flashing/059J187 $ flasher -f -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin
flasher 3.12.1 (Oct  5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Suitable USB interface (bootloader/phonet) not found, waiting...
USB device found at bus 001, device address 019.
Device identifier: (null) (SN: N/A)
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
miika@Desktop ~/Työpöytä/Flashing/059J187 $ flasher -a DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin -k zImage_2.6.32.54-ubiboot-02_301013 --flash-only=kernel -f -R
flasher 3.12.1 (Oct  5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Picked ape-algo from a FIASCO file
Suitable USB interface (bootloader/phonet) not found, waiting...
USB device found at bus 001, device address 021.
Device identifier: (null) (SN: N/A)
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted
Error claiming USB interface: Operation not permitted

Any advice how I could be able to charge it? I have tried examples from this topic for example.

http://talk.maemo.org/showthread.php?t=87709


EDIT: Just realized that it is Linux priviledge problem and added Sudo. It says it is now charging and the battery indeed was at Zero. Hopefully this will get it running now.

peterleinchen 2015-04-10 06:40
Re: Introducing ubiboot N9 (multiboot OS loader)
 
flasher is claiming an USB interface and therefore need to be run with root rights.
Please try either logged in as root
'flasher -i'
or
'sudo flasher -i'.

I would like you to test above command to check whether battery really gets loaded with 'flasher -i'. Keep it connected for at least 30 minutes and disconnect/start up.
If that does not work you still may try above, but I would use
'flasher -f -F firmware.bin --flash-only=kernel'

Boxeri 2015-04-10 06:53
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by peterleinchen (Post 1466297)
flasher is claiming an USB interface and therefore need to be run with root rights.
Please try either logged in as root
'flasher -i'
or
'sudo flasher -i'.

I would like you to test above command to check whether battery really gets loaded with 'flasher -i'. Keep it connected for at least 30 minutes and disconnect/start up.
If that does not work you still may try above, but I would use
'flasher -f -F firmware.bin --flash-only=kernel'
Didn't notice my Edit at the end of the post ;)

I realized the same thing you wrote. It was because of root rights. To the rest of your writing. I had already tried all of those. They doesn't work. Didn't try for 30 minutes though, but for 10minutes did and nothing.

juiceme 2015-04-10 10:13
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Ubiboot does not hinder charging-by-flasher.

death_ghost 2015-06-15 13:17
Re: Introducing ubiboot N9 (multiboot OS loader)
 
after i flashed the ubiboot kernel i got "boot menu script not found!"

cpio and config file in the same directory ( /home/user/MyDocs/boot )
and cpio name is the same as in config file
so where is the problem ?
PS: there is no log file created

Thanks in advance

peterleinchen 2015-06-15 20:04
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Hmm, only thing I can think of right now:
what kernel (version) did you flash? Maybe an older version that did not yet support booting from MyDocs (vFat mmcblk0p1)?
That would explain that message and non-presence of log.

I think I have flashed zImage_2.6.32.54-ubiboot-02_301013

death_ghost 2015-06-15 21:29
Re: Introducing ubiboot N9 (multiboot OS loader)
 
it's zImage_2.6.32.54-ubiboot-02_301013

juiceme 2015-06-16 09:16
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by death_ghost (Post 1473625)
after i flashed the ubiboot kernel i got "boot menu script not found!"

cpio and config file in the same directory ( /home/user/MyDocs/boot )
and cpio name is the same as in config file
so where is the problem ?
PS: there is no log file created

Thanks in advance
well, there sure should be a log file. Two log files in fact.

In your ubiboot.conf there's a pair of keys that define the log file location. Unless you have changed the defaults, they are:
G_LOGFILE_PARTITION="1"
G_LOGFILE_DIRECTORY="/boot"

Now, depending on how you have partitioned your device the log file locations can change of course. Normally partition_1 is MyDocs so the log files will be created to the same directory as your ubiboot.conf and cpio are. Howevwer, if you have something else in your device they might be in different location.

death_ghost 2015-06-16 10:00
Re: Introducing ubiboot N9 (multiboot OS loader)
 
1 Attachment(s)
you can see my partitions and my ubiboot.conf file

http://m56.imgup.net/2015-06-16d224.png

juiceme 2015-06-16 11:12
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by death_ghost (Post 1473693)
you can see my partitions and my ubiboot.conf file
Looks OK to me.
And you really get no log files to your /home/user/MyDocs/boot/ after booting with ubiboot??

What exactly happens when you boot the device, you get the green-text screen OK, with the boot message and then finally end up with "boot menu script not found!" error?

Did you try to boot with USB cable connected, can you telnet to the device and check what's happening inside?

pasko 2015-08-12 21:14
Re: Backup/restore with ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by peterleinchen (Post 1383746)
Short tutorial to backup full device with ubiboot (for console enthusiasts only :)):

- power down device

- connect USB to device and PC (be it Linux or Windoze flavor)

- wait for maintenance mode screen
at this time you should notice also mounted drive(s) on PC,
on Windoze only p1, on Linux all partitions (according to your ubiboot.conf)
do NOT touch that drive under Windoze yet

- open a console on PC and telnet/ssh into N9

- create some mount points
mkdir /mnt/p1
mkdir /mnt/p2
mkdir /mnt/p3
mkdir /mnt/px #for other partitions you might have

- mount MyDocs read-write, rootfs (p2) and home (p3) read-only
mount -w -t vfat /dev/mmcblk0p1 /mnt/p1
mount -r -t ext4 /dev/mmcblk0p2 /mnt/p2
mount -r -t ext4 /dev/mmcblk0p3 /mnt/p3

- tar up rootfs and home on MyDocs
cd /mnt/p2
tar -cvf /mnt/p1/p2.tar *
cd /mnt/p3
tar -cvf /mnt/p1/p3.tar *

you may also use
tar -cvzf /mnt/p1/pX.tar.gz *
for compressed tar, but it will take ages...

- now unmount all
umount /mnt/p1
umount /mnt/p2
umount /mnt/p3

- if you like, grab the tar files on N9/MyDocs NOW via the mounted drive from PC (do this first at this stage/unmounting as MyDocs seems mountable twice from PC and from N9, read access should not get you into trouble, but concurrent write access may do so, to the extent of fully broken file system)

That's it. Full backup of device done under Windoze with the help of ubiboot maintenance mode.
For Linux you may do it the same way or just directly mount and tar from PC.

Thanks again to juiceme for providing such wonderful tool!


Just thought I write it down, even all above is obvious. ;)
Maybe worth to add to wiki or Readme?



--
Restore:

- power down device

- connect USB to device and PC (be it Linux or Windoze flavor)

- wait for maintenance mode screen
at this time you should notice also mounted drive(s) on PC,
on Windoze only p1, on Linux all partitions (according to your ubiboot.conf)
do NOT touch that drive under Windoze yet

- open a console on PC and telnet/ssh into N9

- create some mount points
mkdir /mnt/p1
mkdir /mnt/p2
mkdir /mnt/p3
mkdir /mnt/px #for other partitions you might have

- mount MyDocs read-only, rootfs (p2) and home (p3) read-write
mount -r -t vfat /dev/mmcblk0p1 /mnt/p1
mount -w -t ext4 /dev/mmcblk0p2 /mnt/p2
mount -w -t ext4 /dev/mmcblk0p3 /mnt/p3

- untar rootfs and home from MyDocs
cd /mnt/p2
rm -fr *
tar -xvf /mnt/p1/p2.tar
cd /mnt/p3
rm -fr *
tar -xvf /mnt/p1/p3.tar

if you have compressed tar.gz, use
tar -xvzf /mnt/p1/pX.tar.gz

- now unmount all
umount /mnt/p1
umount /mnt/p2
umount /mnt/p3

If you need to copy the backup from PC back to N9 first, then do it as first step before mounting.

Disclaimer: verified the restore up to now only to copy Harmattan root from p2 to p5 and it worked. So I am convinced, this will work.

Hi.
Maybe a bit offtopic (and surely outdated) replay, but I just want to confirm this method just works.
I have tested it in my backup device (with openmode kernel) and so far it is working flawlessly.
However I have a pair of questions to ask:
1.- Can I do this procedure in a device without openmode kernel? My main device is not flashed with openmode :).
2.- Given that only the ubiboot kernel is flashed to export the partitions: Can I skip the ubiboot installation process (i.e: will it work just flashing the ubiboot kernel, making the backup and then reflashing the stock kernel)?

Regards.

juiceme 2015-08-13 04:21
Re: Backup/restore with ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by pasko (Post 1479356)
However I have a pair of questions to ask:
1.- Can I do this procedure in a device without openmode kernel? My main device is not flashed with openmode :).
2.- Given that only the ubiboot kernel is flashed to export the partitions: Can I skip the ubiboot installation process (i.e: will it work just flashing the ubiboot kernel, making the backup and then reflashing the stock kernel)?
Hi!

I'll answer the second question first :)

Yes, if you use ubiboot kernel just to backup/restore your device, you do not need to install it, just flashing the kernel is enough. Even better, you do not need to flash the kernel at all, it is enough that you boot it with flasher, no permanent flashing required.
This way you do not need to reflash it again, just boot it after backup and it will use the original kernel.

Then the first question;
In theory the backup method works also with a device without open mode kernel, however note that when you boot it even once with something else than nokia-signed kernel the device will be set to open mode and remains so until you fully reflash it with nokia-signed package.
What this means is that your device will be in open mode without an open mode kernel; you lose ability to do some things, for example device lock will not work any more.

pasko 2015-08-13 08:08
Re: Backup/restore with ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by juiceme (Post 1479370)
Hi!
Then the first question;
In theory the backup method works also with a device without open mode kernel, however note that when you boot it even once with something else than nokia-signed kernel the device will be set to open mode and remains so until you fully reflash it with nokia-signed package.
What this means is that your device will be in open mode without an open mode kernel; you lose ability to do some things, for example device lock will not work any more.
Hi.
One more question :)
When you say "fully reflash it with nokia-signed package" you mean the whole vanilla package? Or is it enough to just reflash the stock kernel after the backup? (There's a "slight" difference, you know) ;)

Regards.

juiceme 2015-08-13 08:44
Re: Backup/restore with ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by pasko (Post 1479385)
Hi.
One more question :)
When you say "fully reflash it with nokia-signed package" you mean the whole vanilla package? Or is it enough to just reflash the stock kernel after the backup? (There's a "slight" difference, you know) ;)

Regards.
No, reflashing the kernel is not enough. You need to reflash the whole firmware.

How it works; when you flash a non-signed kernel the flasher (or actually the APE algo) detects that and disables access to the protected parts of system in the boot phase. This change is pernamently one-way, and can be undone only if APE flashes the whole firmaware with signed packages, not just the kernel.

Rationale for that is easy to understand, yet it remains predominantly evil... :eek:
If it was allowed to run unsigned kernel and then return back to stock kernel with device still in protected mode, then it would be possible to make any kind of modifications to the system and retain them when in protected mode.... (something that device manufacturers do not like to see done)

SO there is easy rule-of-thumb; if, for whatever reason, your device for a split second enters open mode it stays in open mode until you fully reflash it with original sibned packages :(

[*] there are ways to get around this, but they are not easy and require either special tools or utilize some lesser known weaknesses of the system. Hence I will not discuss them here...

pasko 2015-08-13 10:02
Re: Backup/restore with ubiboot N9 (multiboot OS loader)
 
Hi.

Thank you for the information, Juiceme.
I think i'll refrain myself for a while..... ;)
Regards.

Boxeri 2015-09-04 08:12
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Decided to flash my spare N9 with ubiboot for harmattan and nitroid. Can't find the zImage_e-yes_nitdroid+l2fi kernel that is to be used with Ubiboot anywhere from the web. Anyone have it?

juiceme 2015-09-04 14:30
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by Boxeri (Post 1481061)
Decided to flash my spare N9 with ubiboot for harmattan and nitroid. Can't find the zImage_e-yes_nitdroid+l2fi kernel that is to be used with Ubiboot anywhere from the web. Anyone have it?
I probably have it, tucked somewhere.
I'll check when I get home later today.

juiceme 2015-09-04 18:46
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Here it is: http://www.swagman.org/juice/zImage_nitdroid+l2fix
MD5sum is ad06d746727fb7c243ee8c845b181f30

marmistrz 2016-01-03 19:55
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Juiceme,

can you please properly document all the steps needed to boot another OS which is not any of the built-in ones? It's basically trial and error with the current documentation.


All times are GMT. The time now is 04:10.
Page 33 of 35 « First 233132 33 3435
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8