Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (6)
to General by Kalatti - 4 days, 16 hrs ago - more...
djselbeck |
2013-12-20
, 21:19
|
|
Posts: 113 |
Thanked: 303 times |
Joined on Dec 2013
@ Germany
|
#61
|
I've successfully booted my own compiled kernel right now. But at the moment I've some problems with initrd but should figure it out sooner or later
| The Following 13 Users Say Thank You to djselbeck For This Useful Post: | ||
Iryus, JiiHoo, Jordi, juiceme, maluka, MartinK, mattaustin, Nekron, Oblomow, reinob, richardski, Watchmaker | ||
|
|
2013-12-20
, 21:39
|
|
Posts: 7 |
Thanked: 95 times |
Joined on Dec 2013
@ Finland
|
#62
|
Originally Posted by djselbeck
This should be how to create a boot.img.
I've successfully booted my own compiled kernel right now. But at the moment I've some problems with initrd but should figure it out sooner or later
https://github.com/KonstaT/sailfisho...oot-img.sh#L17
Looks like there's only a dummy ramdisk inside boot.img. Have you btw dumped the original boot partition from the device? Or at least could someone upload the kernel config (/proc/config.gz) from an actual device? It should be quite close to boston_mer_defconfig but still not exactly.
According to this, there's also a tool for flashing partitions in the system.
https://github.com/KonstaT/sailfisho...bootimg-sbj.sh
Edit. Oh wow, my posts are moderated before publishing for some reason. This message appearead here several days (~week?) later. Seriously, wtf?! If I've done something to deserve a post ban - then just issue one, but this is just ridiculous.
Last edited by Konsta; 2013-12-28 at 11:07.
| The Following 2 Users Say Thank You to Konsta For This Useful Post: | ||
|
|
2013-12-20
, 22:52
|
|
Posts: 113 |
Thanked: 303 times |
Joined on Dec 2013
@ Germany
|
#63
|
It is working now. I'm preparing an easy guide with an image.
As I'm typing this, I'm backing up my mmcblk0p* partitions.
The best thing, you don't even have to modify your recovery partition
I've written the guide here: https://wiki.merproject.org/wiki/Sai...prebuilt_image
As you can see I'm really not good at this kind of stuff. If some one with some skill in mediawiki wants to improve feel free. For questions use this thread or write me a pm.
Please be careful, I won't take any responsibility for your actions. This guide is for users who know what they are doing
Last edited by djselbeck; 2013-12-20 at 23:51.
As I'm typing this, I'm backing up my mmcblk0p* partitions.
The best thing, you don't even have to modify your recovery partition
I've written the guide here: https://wiki.merproject.org/wiki/Sai...prebuilt_image
As you can see I'm really not good at this kind of stuff. If some one with some skill in mediawiki wants to improve feel free. For questions use this thread or write me a pm.
Please be careful, I won't take any responsibility for your actions. This guide is for users who know what they are doing
Last edited by djselbeck; 2013-12-20 at 23:51.
|
|
2013-12-21
, 08:17
|
|
Posts: 11 |
Thanked: 1 time |
Joined on Aug 2013
|
#64
|
Originally Posted by rainisto
Hello rainisto
Maybe you didn't understand when Stskeeps said that stay with developer mode and root.
Did you try as root to run: "dd if=recovery.img of=/dev/disk/by-partlabel/recovery" while beeing logged inside Jolla phone shell?
I am trying to contact you but do not have private message privileges on this forum for some reason. Can you please email me?
allegation at gmail.com
Thank you.
|
|
2013-12-21
, 16:34
|
|
Posts: 25 |
Thanked: 99 times |
Joined on Apr 2013
|
#65
|
Thank you very much for the instructions. I was able to boot your image. I also added some missing details I discovered on the way to the Wiki.
For a real fastboot recovery image, I would appreciate support for ssh and also NFS. Then we could copy the files directly to the host instead of going through the SD card.
For a real fastboot recovery image, I would appreciate support for ssh and also NFS. Then we could copy the files directly to the host instead of going through the SD card.
 |
|
2013-12-21
, 22:17
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#66
|
I was able to dualboot mine, too.
Actually I booted the stock kernel but with a different rootfs, you do not need to do any changes to the kernel configuration since you can override the command line when mkbootimg'ing.
The stock kernel image, cmdline and initramfs are stored in /boot/boot.img (this is in mkbootimg format). There are several (Android) programs around to "unmkbootimg" this and get the raw kernel images et all. Also, the format is simple enough to decode manually. The stock kernel cmdline, stored in this file, is:
(Presumably should match what you get on a live SbJ's /proc/cmdline)
Some comments to the wiki page https://wiki.merproject.org/wiki/ind.../Backup_Device that may be interesting if creating your own bootimgs:
EDIT: I've now changed the above wiki page (section "Build your own image"). Waiting for feedback if you're trying to build your own images!
Last edited by javispedro; 2013-12-22 at 00:54.
Actually I booted the stock kernel but with a different rootfs, you do not need to do any changes to the kernel configuration since you can override the command line when mkbootimg'ing.
The stock kernel image, cmdline and initramfs are stored in /boot/boot.img (this is in mkbootimg format). There are several (Android) programs around to "unmkbootimg" this and get the raw kernel images et all. Also, the format is simple enough to decode manually. The stock kernel cmdline, stored in this file, is:
Code:
init=/sbin/preinit root=/dev/mmcblk0p28 rootfstype=btrfs rootflags=recovery noinitrd androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 maxcpus=2
Some comments to the wiki page https://wiki.merproject.org/wiki/ind.../Backup_Device that may be interesting if creating your own bootimgs:
- You do not really need to edit CONFIG_CMDLINE or set CONFIG_CMDLINE_FORCE. Passing a valid cmdline (via --cmdline 'init=/linuxrc ...') to mkbootimg is enough and this is the way the builtin kernel does this. However, this is mostly personal preference.
- You can use standard Linux tools to build the initramfs such as "cpio -H newc". It can be gzipped.
- You do need to set the same offsets the stock boot.img uses to mkbootimg, i.e. ensure you pass the following to mkbootimg (along with kernel and ramdisk options): " Otherwise you'll get instant reboot.Code:
--base 0x00000000 --pagesize 2048 --kernel_offset 0x80208000 --ramdisk_offset 0x82200000 --second_offset 0x81100000 --tags_offset 0x80200100 --board ''
EDIT: I've now changed the above wiki page (section "Build your own image"). Waiting for feedback if you're trying to build your own images!
Last edited by javispedro; 2013-12-22 at 00:54.
|
|
2013-12-22
, 11:01
|
|
Posts: 113 |
Thanked: 303 times |
Joined on Dec 2013
@ Germany
|
#67
|
Hello,
I've tried building the bootimage with an extra ramdisk but so far only got instant reboot, so I decided to include it directly into the kernel.
Did you actually had success including a ramdisk with mkbootimg?
I think you need to specify an offset to the kernel, which declares the location of the image. Something like
but I had no time so far trying that out.
My first priority was to provide an fast solution to backup your device
. Now I have some time and will look into it and include an ssh server for example.
Edit: Ramdisk inclusion with boot.img worked. I've no idea why it did'nt last time I tried. Perhaps because it was already very late and I'm tired So this is clearly the preferred method over init inclusion in kernel image.
Last edited by djselbeck; 2013-12-22 at 13:40.
I've tried building the bootimage with an extra ramdisk but so far only got instant reboot, so I decided to include it directly into the kernel.
Did you actually had success including a ramdisk with mkbootimg?
I think you need to specify an offset to the kernel, which declares the location of the image. Something like
Code:
initrd=0x02200000
My first priority was to provide an fast solution to backup your device
. Now I have some time and will look into it and include an ssh server for example.Edit: Ramdisk inclusion with boot.img worked. I've no idea why it did'nt last time I tried. Perhaps because it was already very late and I'm tired
So this is clearly the preferred method over init inclusion in kernel image.
Last edited by djselbeck; 2013-12-22 at 13:40.
| The Following 6 Users Say Thank You to djselbeck For This Useful Post: | ||
|
|
2013-12-22
, 14:32
|
|
Posts: 25 |
Thanked: 99 times |
Joined on Apr 2013
|
#68
|
I think it would be interesting to know whether these partitions are actually the same for all devices or if they contain anything specific for each phone. So here are SHA1 checksums of my backups.
I left out partition 28, the root filesystem, because everyone has definitely made their own changes on that already.
Please let me know if yours differ from mine above.
Code:
$ sha1sum mmcblk0p{1..27}.img
edd6071d386ed1d60a541a06e0eb081c381296b7 mmcblk0p1.img
ccb9f2c0184df67deff69df328a78d04ab0fd805 mmcblk0p2.img
a07548e01946ba3490d8d0898a7f2027890f2021 mmcblk0p3.img
41e2c4bbe9433b14dfa4c95b99e09245faf0c8e7 mmcblk0p4.img
31ebbbadb5686cf54d4f3760f7f39d007e87e501 mmcblk0p5.img
e904aa58289574f74753fa5a810551676ccdaefe mmcblk0p6.img
32507ad14ccec38defa20fa9261d9b612b6e39f9 mmcblk0p7.img
cfdf75b00346c48c7afd80647003f41e1d9fce0f mmcblk0p8.img
0b7620536530c70d3b7f7fca794a11b3ee3b560c mmcblk0p9.img
aff661e1c1b4b0bea1d71c6d6bc0ec67c4842d61 mmcblk0p10.img
4277b8ef0cd6e0e094b5d266a455555d56881c79 mmcblk0p11.img
e5da449e911e5109c07bd5790bba98b8e177e07d mmcblk0p12.img
ab7066450ff20db47b84a4c04d17234f1a2ee41e mmcblk0p13.img
4a2678e8344d53fea59bd884c5059808eff6c215 mmcblk0p14.img
9cb3b5879a41ec2807bcd348d7272b2c5810853b mmcblk0p15.img
16b918c87b4c88caaaf4141a8e9ffa07e2619f42 mmcblk0p16.img
edb50610c434463c34d454a45cb8ce60d19cbd7b mmcblk0p17.img
f6d80fcc3f4b0d6601c54d507e57a29a852628c1 mmcblk0p18.img
3fdbe058350c93e3f76c038f57165abb7f32f10f mmcblk0p19.img
cbc76425d05c9725640ce16246316babf0c68212 mmcblk0p20.img
e965227e6200655f4fbde5e74df13f2e10c3bbbe mmcblk0p21.img
5fde1cce603e6566d20da811c9c8bcccb044d4ae mmcblk0p22.img
5fde1cce603e6566d20da811c9c8bcccb044d4ae mmcblk0p23.img
4298f4bad2bae957adf2fe4034e82fdc85f40f77 mmcblk0p24.img
f9f05976f9056069c08c5dfca34c20f0ef69a4dd mmcblk0p25.img
03e6fb7a7034b064a876da4d0c8c88373849f0b5 mmcblk0p26.img
723302098b1e619e83bd6726096e15fcd6bd8402 mmcblk0p27.img
Please let me know if yours differ from mine above.
| The Following User Says Thank You to Raim For This Useful Post: | ||
|
|
2013-12-22
, 14:35
|
|
Posts: 113 |
Thanked: 303 times |
Joined on Dec 2013
@ Germany
|
#69
|
Yep, actually a lot differ:
Code:
fd13511082820e36c0cada61862457152bc8483c mmcblk0p1 9fe01a1d7b38c861a80a5d4d9b583c3b83c35efc mmcblk0p2 f7f47d862fb74e4f955c0746f13e2ee585a02763 mmcblk0p3 e3d31adfd70df23fc32f464a5a60f34e59996e40 mmcblk0p4 82b5c51a77de9d7e10daae5eb8095d760dc5739e mmcblk0p5 e904aa58289574f74753fa5a810551676ccdaefe mmcblk0p6 32507ad14ccec38defa20fa9261d9b612b6e39f9 mmcblk0p7 0a2d9e671eb8d04994e76d31456262f12130304b mmcblk0p8 1a54de676c5131972d85a43e8c741805e0d40f37 mmcblk0p9 458b24477074c08ca267c1f7d0f7352373a7b5b7 mmcblk0p10 64accf1c268db9329c53641417c132cc45d5b343 mmcblk0p11 e5da449e911e5109c07bd5790bba98b8e177e07d mmcblk0p12 ab7066450ff20db47b84a4c04d17234f1a2ee41e mmcblk0p13 4a2678e8344d53fea59bd884c5059808eff6c215 mmcblk0p14 9cb3b5879a41ec2807bcd348d7272b2c5810853b mmcblk0p15 16b918c87b4c88caaaf4141a8e9ffa07e2619f42 mmcblk0p16 edb50610c434463c34d454a45cb8ce60d19cbd7b mmcblk0p17 f6d80fcc3f4b0d6601c54d507e57a29a852628c1 mmcblk0p18 342de6a26abfe7e09545f73d6aeba44d3e04cc53 mmcblk0p19 cbc76425d05c9725640ce16246316babf0c68212 mmcblk0p20 3ad9c7b30a8843f7bb40529f5ba648d821485599 mmcblk0p21 5fde1cce603e6566d20da811c9c8bcccb044d4ae mmcblk0p22 5fde1cce603e6566d20da811c9c8bcccb044d4ae mmcblk0p23 04d6bd9172e1885430fb533d6caf089a322df5c6 mmcblk0p24 c196035601266d43bf8dcb7f3d4add13fe58af99 mmcblk0p25 03e6fb7a7034b064a876da4d0c8c88373849f0b5 mmcblk0p26 f2434a34119e15865d101a350ae0da24216c4448 mmcblk0p27
|
|
2013-12-22
, 14:55
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#70
|
So dissapointed with the wireless support (no monitor mode/injection)
Does anyone have a clue to which card is in the device ?
Does anyone have a clue to which card is in the device ?
Code:
[nemo@localhost ~]$ sudo iw list Wiphy phy0 Band 1: Capabilities: 0x9030 HT20 Static SM Power Save RX Greenfield RX HT20 SGI No RX STBC Max AMSDU length: 3839 bytes DSSS/CCK HT40 L-SIG TXOP protection Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 16 usec (0x07) HT TX/RX MCS rate indexes supported: 0-7 Frequencies: * 2412 MHz [1] (30.0 dBm) * 2417 MHz [2] (30.0 dBm) * 2422 MHz [3] (30.0 dBm) * 2427 MHz [4] (30.0 dBm) * 2432 MHz [5] (30.0 dBm) * 2437 MHz [6] (30.0 dBm) * 2442 MHz [7] (30.0 dBm) * 2447 MHz [8] (30.0 dBm) * 2452 MHz [9] (30.0 dBm) * 2457 MHz [10] (30.0 dBm) * 2462 MHz [11] (30.0 dBm) * 2467 MHz [12] (30.0 dBm) * 2472 MHz [13] (30.0 dBm) * 2484 MHz [14] (30.0 dBm) Bitrates (non-HT): * 1.0 Mbps * 2.0 Mbps * 5.5 Mbps * 11.0 Mbps * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps max # scan SSIDs: 9 max scan IEs length: 200 bytes Coverage class: 0 (up to 0m) Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP (00-0f-ac:4) * WPI-SMS4 (00-14-72:1) Available Antennas: TX 0 RX 0 Supported interface modes: * IBSS * managed * AP * P2P-client * P2P-GO software interface modes (can always be added): interface combinations are not supported Supported commands: * new_interface * set_interface * new_key * new_beacon * new_station * set_bss * join_ibss * set_pmksa * del_pmksa * flush_pmksa * remain_on_channel * action * frame_wait_cancel * set_channel * connect * disconnect Supported TX frame types: * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 Supported RX frame types: * managed: 0x40 0xd0 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * P2P-client: 0x40 0xd0 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 Device supports roaming.
| The Following 2 Users Say Thank You to For This Useful Post: | ||