Active Topics
-
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (9)
to SailfishOS by biketool - 9 hrs, 59 mins ago -
[Announce] coderus unrestricted system-ui (297)
to MeeGo / Harmattan by nieldk - 6 days, 15 hrs ago - more...
|
2007-07-06
, 07:06
|
|
Posts: 58 |
Thanked: 2 times |
Joined on Jun 2007
|
#2
|
you dont need a pc- ue the kernel flasher on his page that he suggested.
|
|
2007-07-06
, 10:53
|
|
Posts: 5 |
Thanked: 0 times |
Joined on Jul 2007
|
#3
|
Originally Posted by robbh66
really? well call me a noob then shows what i know
you dont need a pc- ue the kernel flasher on his page that
he suggested.
i am still trying to figure out how to load an application without the application manager so i suppose that was part of the problem
thanks for your help
|
|
2007-07-06
, 14:51
|
|
Posts: 58 |
Thanked: 2 times |
Joined on Jun 2007
|
#4
|
You need:
osso-Xterm
becomeroot
unzip
tar (but this might be installed by default)
Install Xterm, become root, and unzip from the application manager (you need to add the right repositories).
Download kernel_flasher.tgz from his site and whichever firmare you wish (the absolute newest version is "experimental" in his own words and can be found at http://fanoush.wz.cz/maemo/zImage-yuv420)
I'm very new to linux (770 forces you to learn the basics) so i might have missed something here but it will basically go like this in terminal:
That should cover it all. If something is wrong don't worry about it messing something up - generally the command just wont work at all.
If someone wanted to explain to me why (and how you're supposed to know) that you use the "./" before the kernel_flash that'd be great. Also why is there a "." before documents?
osso-Xterm
becomeroot
unzip
tar (but this might be installed by default)
Install Xterm, become root, and unzip from the application manager (you need to add the right repositories).
Download kernel_flasher.tgz from his site and whichever firmare you wish (the absolute newest version is "experimental" in his own words and can be found at http://fanoush.wz.cz/maemo/zImage-yuv420)
I'm very new to linux (770 forces you to learn the basics) so i might have missed something here but it will basically go like this in terminal:
Code:
# sudo gainroot # cd /home/users/MyDocs/.documents/ # tar zxvf kernel_flasher.tgz # unzip <zImagename.zip> <-- Step only needed if the zImage is zipped! # cd kernel_flasher # ./kernel_flash /home/users/MyDocs/.documents/<zImagename>
If someone wanted to explain to me why (and how you're supposed to know) that you use the "./" before the kernel_flash that'd be great. Also why is there a "." before documents?
|
|
2007-07-06
, 23:15
|
|
Posts: 5 |
Thanked: 0 times |
Joined on Jul 2007
|
#5
|
thanks for your help...
I was able to get it to work after reading another thread, but life would have been a lot easier had I seen this first
I was able to get it to work after reading another thread, but life would have been a lot easier had I seen this first
|
|
2007-07-07
, 05:43
|
|
Posts: 10 |
Thanked: 0 times |
Joined on Jul 2007
|
#6
|
I believe the '.' before documents is because it's hidden. Hidden files and folders are preceded by '.'
For some reason I don't know of, "./" tells Linux that whatever after "./" is an executable. EG "./foo" tells Linux to run "foo" as an executable file.
Last edited by BcNexus; 2007-07-07 at 06:06. Reason: Clarification
For some reason I don't know of, "./" tells Linux that whatever after "./" is an executable. EG "./foo" tells Linux to run "foo" as an executable file.
Last edited by BcNexus; 2007-07-07 at 06:06. Reason: Clarification
|
|
2007-08-03
, 18:12
|
|
Posts: 14 |
Thanked: 0 times |
Joined on Aug 2007
|
#7
|
Originally Posted by robbh66
Everything was going well until the last line command it says that image is not found. any ideas? I have the zImage-yuv420 saved to the documents folder
You need:
osso-Xterm
becomeroot
unzip
tar (but this might be installed by default)
Install Xterm, become root, and unzip from the application manager (you need to add the right repositories).
Download kernel_flasher.tgz from his site and whichever firmare you wish (the absolute newest version is "experimental" in his own words and can be found at http://fanoush.wz.cz/maemo/zImage-yuv420)
I'm very new to linux (770 forces you to learn the basics) so i might have missed something here but it will basically go like this in terminal:
That should cover it all. If something is wrong don't worry about it messing something up - generally the command just wont work at all.Code:# sudo gainroot # cd /home/users/MyDocs/.documents/ # tar zxvf kernel_flasher.tgz # unzip <zImagename.zip> <-- Step only needed if the zImage is zipped! # cd kernel_flasher # ./kernel_flash /home/users/MyDocs/.documents/<zImagename>
If someone wanted to explain to me why (and how you're supposed to know) that you use the "./" before the kernel_flash that'd be great. Also why is there a "." before documents?
|
|
2007-08-03
, 18:28
|
|
Posts: 1 |
Thanked: 0 times |
Joined on Jul 2007
|
#8
|
Originally Posted by BcNexus
As a security measure, you have to specify absolute (full) paths for executables that aren't in your PATH environment variable.
I believe the '.' before documents is because it's hidden. Hidden files and folders are preceded by '.'
For some reason I don't know of, "./" tells Linux that whatever after "./" is an executable. EG "./foo" tells Linux to run "foo" as an executable file.
For example, your PATH variable might contain something like "/usr/bin", which would mean that executables in /usr/bin can be run just by typing their name.
However, when you are accessing other places (for example, a user's home directory or a remote network site), you don't want people to be able to override your commands. For example, someone could put a file in their directory called "ls" - chances are someone would probably end up running it.
Forcing you to specify absolute paths eliminates this problem. The admin would have to type "./ls" rather than "ls", which makes it clear that he/she is running THIS executable.
FYI, executables also need to have the execute permission set. You can do this using the command "chmod +x <FILENAME>". If you write scripts (shell scripts, Perl, Python, etc.) and want to run them from the command line as if they were executables, this is how you do it (you also have to add the shebang to the top of the file).
The problem is I can't for the life of me figure out how to do this with a windows pc. I can completely change the software using the nokia update wizard, but this doesn't seem to allow for changing just kernels.
I set up a cd bootable linux set up, but couldn't get it to connect to the internet or recognize a usb connection(so I couldn't access the needed info/files or the 770).
Any ideas? Thanks