maemo.org - Talk

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)

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


All times are GMT. The time now is 03:44.

vBulletin® Version 3.8.8