Re: What do we know about Diablo (Maemo 4.1) ?
 

No. The "cease and desist" or takedown order comes before lawsuit.

NOTE: that is not an official corporate statement!!!!

Re: What do we know about Diablo (Maemo 4.1) ?
 

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.

Re: What do we know about Diablo (Maemo 4.1) ?
 

Well, I got /dev/loop[0-7] here... BTW, thanks for that kernel info! I grabbed Fanoush's.

Re: What do we know about Diablo (Maemo 4.1) ?
 

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 :)

Re: What do we know about Diablo (Maemo 4.1) ?
 

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. :)

Re: What do we know about Diablo (Maemo 4.1) ?
 

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...

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...

Re: What do we know about Diablo (Maemo 4.1) ?
 

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.

Re: What do we know about Diablo (Maemo 4.1) ?
 

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?

Re: What do we know about Diablo (Maemo 4.1) ?
 

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.)

Re: What do we know about Diablo (Maemo 4.1) ?
 

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 :p

Re: What do we know about Diablo (Maemo 4.1) ?
 

Also, remember I've already ripped it. A pm can go a long way ;)

I've also manually added fanoush's bootmenu to the diablo initfs. (diff job, not replaceing job ;))

Re: What do we know about Diablo (Maemo 4.1) ?
 

Yeah, and as one of the Order, I'll probably be sending you such a PM, once I'm decently content with things on a Chinook initfs...

Re: What do we know about Diablo (Maemo 4.1) ?
 

Hehe, as much as I sound cocky, conceited and arrogant, I usually am willing to share what I show off (being reasonable of course)

Re: What do we know about Diablo (Maemo 4.1) ?
 

You guys already have outdated stuff. :p

Re: What do we know about Diablo (Maemo 4.1) ?
 

Quick Benson, get the rat poison!

I'll go down to Texas and find out the secret...

Re: What do we know about Diablo (Maemo 4.1) ?
 

He's got N1500... or so so.

Re: What do we know about Diablo (Maemo 4.1) ?
 

I just meant Diablo.

/me burrows down

Re: What do we know about Diablo (Maemo 4.1) ?
 

hehe....<filler>

Re: What do we know about Diablo (Maemo 4.1) ?
 

Thanks for the image, qwerty12, but it didn't work. My device still won't display any initfs information on boot-up. I wonder if I'm missing a step.

When you guys did your apt-get install, was it clean? The one issue I get is that multiple instances of hildon-desktop get started, which looks weird, and my XTerm only gets half the horizontal screen (except when full-screen). Did that happen to you guys?

To re-cap, here are the steps I took in my last attempt (don't try these, people, they don't work for me):

1. Re-flash my N810 with the latest official firmware.
2. Put the device in R&D mode (--enable-rd).
3. Disable the lifeguard reset (--set-rd-flags=no-lifeguard-reset).
4. Do initial setup (language, table name, etc.)
5. Remove contents of MyDocs (the pre-installed MP3s, videos, etc.), leaving about 160MB free in the root partition.
6. Modify /etc/apt/sources.list.d/whatever-it's-called to replace all instances of "chinook" with "diablo" and to add the username/password for the updates repository.
7. apt-get -d install osso-software-version-rx44-unlocked (download only, at first, just in case)
8. apt-get install osso-software-version-rx44-unlocked
9. (Notice another instance of hildon-desktop starting...)
10. Answer "Y" to a couple of "Take the new version or keep the old version of this config file" prompts.
11. When the install completes, remove the initfs image.
12. flash-and-reboot
13. Wait as my N810 turns off, tries to boot, and fails to boot.

Most recently, after running those steps, I tried to use flasher-3.0 to re-flash the initfs partition with a stripped Diablo version, and that didn't work. I've also tried all of those same steps, except for the flash-and-reboot (thus using the chinook initfs and kernel), with the same effect.

Anything wrong with these steps, guys? Has anyone gotten this working on an N810 yet? Maybe I should try an N800 first....

Re: What do we know about Diablo (Maemo 4.1) ?
 

Does this mean that they're not propogating Diablo updates through the repository anymore? Are they avoiding the repository now, thanks to people like us? Need we investigate alternatives for getting updates?

Re: What do we know about Diablo (Maemo 4.1) ?
 

No... he means that he has the newer image that was just compiled... and not finished any internal testing yet.

Re: What do we know about Diablo (Maemo 4.1) ?
 

And CRASHES!!!! :D

Well, it makes us feel better to think so.

Re: What do we know about Diablo (Maemo 4.1) ?
 

No crashes yet.

I can't believe this took me so damned long :cool:

http://tablethacker.com/temporary/Screenshot.png

Re: What do we know about Diablo (Maemo 4.1) ?
 

Aisu, you got your N810 working on Diablo, right? Did you use the same procedure that I outlined a few posts back (page 50) ? Or did you have to do anything special to get it working on N810?

Re: What do we know about Diablo (Maemo 4.1) ?
 

I did a clean reflash. (I forgot to disable the lifeguard the first try :()

Then, I changed every instance of Chinook in hildon's list to Diablo, even the extras to be safe... And, that's about it. Oh, and I flashed the kernel afterwards. Mine got caught in a loop, but only needed a good kernel. (I used the one out with rotation support.)

Hope it helps!!!

Re: What do we know about Diablo (Maemo 4.1) ?
 

You only need to change the tableteer update repo to Diablo. The rest of them can be left as is, though you may or may not benefit from adding a Diablo Extras alongside Chinook Extras (though there's nothing in Diablo Extras worth mentioning at the moment).

Re: What do we know about Diablo (Maemo 4.1) ?
 

My APT sources list doesn't even list the extras repository. There are only three lines.

Am I missing something?

Re: What do we know about Diablo (Maemo 4.1) ?
 

No, no. That was just me being paranoid and silly. Extras does nothing.

After changing your repos. Please run

as root. But DO NOT say yes yet. Just post what it says. You can do that over SSH as long as you DON'T say yes. Oh, if on N810, change rx34 to rx44

Re: What do we know about Diablo (Maemo 4.1) ?
 

Okay, I ran through my procedure again. Every time I try it, it seems to go differently, which goes against every ounce of common sense in my engineering brain. This time, during the install, I got some strange "cannot remove /usr/share directory - not empty" errors, followed by some "out of space" errors (even though I had plenty of space in my root partition. This stopped the install, and an "apt-get -f install" instructed me to run "dpkg --configure -a", at which point it then resumed.

When it finished, I skipped the flash-and-reboot step, and now it boots fine. I have no idea how "clean" my file system is, and the obsessive-compulsive part of me wants very badly to retry the process from the beginning, but I'm afraid I'll never be able to get it to boot again. So I'll stick with what I have now unless/until I run into issues.

Thanks for the help, everyone.

Re: What do we know about Diablo (Maemo 4.1) ?
 

I do believe you need a signature reflective of that accomplishment :D

Re: What do we know about Diablo (Maemo 4.1) ?
 

Sounds about like it went for me, and my install works fine.

/me shrugs

Re: What do we know about Diablo (Maemo 4.1) ?
 

I wonder why I didn't get that behavior the first four times I tried. :) Ahh, well, if it works for you, I'll stick with it. I love that modest is now the default email client. (Yes, it has its problems, but it works great with gmail's IMAP interface.)

Re: What do we know about Diablo (Maemo 4.1) ?
 

Hang on gnuite!

Even if I had those answers I could not share them, sorry. My teaser was mainly to hint that work continues... so don't make too many hard-and-fast assumptions.

Re: What do we know about Diablo (Maemo 4.1) ?
 

Aisu, earlier you mentioned having problems with the diablo initfs and/or kernel with your N810. I just tried to flash-and-reboot, and the kernel is definitely causing my N810 to stop booting. Have you managed to reflash with the diablo initfs or kernel?

Or do they only work with the N800?

Re: What do we know about Diablo (Maemo 4.1) ?
 

If you're going to teaser, you have to be ready to accept the wild misinterpretations that your teasers may yield. :)

Re: What do we know about Diablo (Maemo 4.1) ?
 

Yeah, but I have elected to accept them only begrudgingly. :p

Re: What do we know about Diablo (Maemo 4.1) ?
 

I was talking to Maba on IRC. His N810 will not boot with the N810 kernel but my ripped Diablo initfs and chinook kernel work together :/

Oh yeah, I've got a static binary of 0xFFFF if anyone wants to dump their clean Diablo rootfs to make a flashable file with flasher-3.0 :/ (not to share it)

Re: What do we know about Diablo (Maemo 4.1) ?
 

If there are no complains when running apt-get -f install, then you have no problems.

Re: What do we know about Diablo (Maemo 4.1) ?
 

No initfs problem. Had some kernel trouble, though.

I just grabbed the kernel from here. Works perfectly with Diablo, and I get a nice new feature :D

Just test it first, like it says there, before you actually install.

Re: What do we know about Diablo (Maemo 4.1) ?
 

Some updates... It seem that the app uses active internet connection (WiFi usually) to keep AGPS data up to date. If that is not currently available, there is an option to use cell phone packet data connection as a backup.

I did test the fix time today after almost a week of not using GPS: At the very beginning GPS status showed ~10 visible satellites right away. After about a minute of waiting I got a fix. This is indeed promising... :) But need to test more to come into more firm conclusions. :rolleyes: