Active Topics

 


Reply
Thread Tools
Texrat's Avatar
Posts: 11,700 | Thanked: 10,045 times | Joined on Jun 2006 @ North Texas, USA
#481
Originally Posted by Aisu View Post
Does that sound like a lawsuit or what?
No. The "cease and desist" or takedown order comes before lawsuit.

NOTE: that is not an official corporate statement!!!!
__________________
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
 
qwerty12's Avatar
Posts: 4,274 | Thanked: 5,358 times | Joined on Sep 2007 @ Looking at y'all and sighing
#482
Originally Posted by Benson View Post
I'd think using the tools from Fanoush's initfs_flasher would work fine...

I'd copy initfs_flash, and make a modded version that doesn't start with the current initfs, but with the image, and then does the same stuff; while it's stopped waiting for input, you can muck around in the initrd directory, and then it'll jffs2 it back up and flash it.

Am I missing something? Is the initrd in a different format not readily extractable to a raw fs image?
I thought about that but decided it wouldn't work.

initfs flasher grabs initfs from the already flashed initfs. Defeats point when you cant flash image to rip...

Also, loop device doesn't exist on n800 afaik and the modules to emulate an mtd are not available for n800.
 
Benson's Avatar
Posts: 4,930 | Thanked: 2,272 times | Joined on Oct 2007
#483
Well, I got /dev/loop[0-7] here... BTW, thanks for that kernel info! I grabbed Fanoush's.
 
qwerty12's Avatar
Posts: 4,274 | Thanked: 5,358 times | Joined on Sep 2007 @ Looking at y'all and sighing
#484
I don't see no losetup

Besides, you need modules to emulate an mtd device too. Like nokia, I don't see the point in compiling them. I compiled mtd-utils thanks to fanoush's source so you can remake the image at least on the device.
(actually, initfs flasher has tool needed too)

No problems
 
maba's Avatar
Posts: 38 | Thanked: 10 times | Joined on Mar 2006
#485
I'm running diablo, but I'm running it with chinook's kernel and initfs. When I flash diablo's kernel my N810 won't boot, it just shows the NOKIA image for a while and then it dies (no progressbar or anything).. Also, "About product" in Control Panel shows <unknown> version. If someone would point me in the right direction to get diablo's kernel and initfs working, I'd be very grateful.
 
Benson's Avatar
Posts: 4,930 | Thanked: 2,272 times | Joined on Oct 2007
#486
Originally Posted by qwerty12 View Post
I don't see no losetup

Besides, you need modules to emulate an mtd device too. Like nokia, I don't see the point in compiling them. I compiled mtd-utils thanks to fanoush's source so you can remake the image at least on the device.
(actually, initfs flasher has tool needed too)

No problems
Hmm... Funny; it looks like mount -o loop used to work (OS2007, PB used it for XFCE at least), but doesn't now. I even tried chrooting to an extracted initfs. Still no good. I'm not sure if mount -o loop uses losetup, or if something else is wrong (perhaps pertaining to mtd emulation; I had thought that was an alternative, not a corequisite). Oh, well, I'll look at it more when I get irritated enough . (Maybe it works from Debian... but I probably still need to compile the mtd stuff.)

Be nice if you could post a tar of the initial contents of the Diablo initfs, but I suppose Reggie and Qim would rather you didn't...

Originally Posted by maba View Post
I'm running diablo, but I'm running it with chinook's kernel and initfs. When I flash diablo's kernel my N810 won't boot, it just shows the NOKIA image for a while and then it dies (no progressbar or anything).. Also, "About product" in Control Panel shows <unknown> version. If someone would point me in the right direction to get diablo's kernel and initfs working, I'd be very grateful.
You need to get hold of a tar of the Diablo initfs. You can do that any of three general ways:
  • With a Glock (to threaten or barter, your call.)
  • On the device, like I was trying. It seems rather troublesome, but you will be lauded as a hero if you can post kernel modules that let us all tear Diablo initfses to pieces and build them back up our own ways.
  • Or you could do it on a desktop, as Faheem outlined.
Once you got that, it's pretty straightforward; read through the initfs_flash script and you'll see what it's doing. Modify that procedure as needed...
Or do the stripping, bundling and even flashing, if you like, from the desktop.

Dunno about the kernel; the new kernel, I'd have thought, would just work...
 
gnuite's Avatar
Posts: 1,245 | Thanked: 421 times | Joined on Dec 2005
#487
Originally Posted by Benson View Post
Hmm... Funny; it looks like mount -o loop used to work (OS2007, PB used it for XFCE at least), but doesn't now. I even tried chrooting to an extracted initfs. Still no good. I'm not sure if mount -o loop uses losetup, or if something else is wrong (perhaps pertaining to mtd emulation; I had thought that was an alternative, not a corequisite). Oh, well, I'll look at it more when I get irritated enough . (Maybe it works from Debian... but I probably still need to compile the mtd stuff.)
Loopback was the first thing I tried, but I got the same results you did - no dice. It probably needs losetup, which (as qwerty12 observed) is not on the device.

I also tried Fanoush's initfs_flasher stuff, but ran into the same problems qwerty12 mentioned - it operates directly on the device's initfs partition, probably to get around the loopback problem. So that would require flashing the image onto the initfs partition, which (of course) is the whole problem in the first place.

I considered dd'ing the jffs2 file to one of the other partitions (like a memory card), and we'd be able to rip files out (either manually or with a modified initfs_flasher), but then we'd still need mkjffs2 in order to re-jffs2 the contents into a size small enough to fit onto the N8x0's initfs partition.

In the end, it's probably easier to just do it all on the desktop.
 

The Following User Says Thank You to gnuite For This Useful Post:
gnuite's Avatar
Posts: 1,245 | Thanked: 421 times | Joined on Dec 2005
#488
How hard is it to re-partition the device's internal flash to give the initfs partition enough space to hold the larger jffs2 image? It's only around 300k too large; I don't mind sacrificing it. Anybody know how to do that? Do we need an entire Fiasco image for that to work?
 
Benson's Avatar
Posts: 4,930 | Thanked: 2,272 times | Joined on Oct 2007
#489
Well, if you've got initfs_flasher, it's got mkfs.jffs2 and what-not. That idea of slamming it on a mmc partition... yeah! (I think you solved it.)

(For me, doing it on a desktop's not easier, because my Linux desktop is unfortunately deprived of internet access (and ~50 miles away). LiveCDs aren't fun for that kinda work, in my experience.)

Last edited by Benson; 2008-05-15 at 20:17.
 
qwerty12's Avatar
Posts: 4,274 | Thanked: 5,358 times | Joined on Sep 2007 @ Looking at y'all and sighing
#490
Remember, you probably still need something to emulate the mtd device unles mount -o jffs2 /dev/mmcetc works straight.

mtdram is out. johnx with 1gb ram couldn't mount diablo initfs, i could with 2gb ram.
mtd2block sounds like it would work.

fanoush posted me a bug which made his partition start location later but he had to compile custom kernel to point to new place and never fixed it afaik

Last edited by qwerty12; 2008-05-15 at 20:29.
 
Reply


 
Forum Jump


All times are GMT. The time now is 22:36.