Arnova 10 G2 Custom ROM by Finless Version 1.3

[Finless]

Hang on... download server is being worked on and is down right now.....
It will be up REAL SOON!

Bob

[ttz642t]

kasty not using ext4

The ext4 file system that Fenice was kind enough to share is rocking the house! Unlike other ROMs out there (cough... ummm... kasty) claiming to be ext4, they are NOT. The recovery system on reboot after flash formats everything ext3 anyway so it's BS.... This time around we will have real ext4 because the recovery system has now been modified.... And let me tell you. It's way faster!

Bob

I'm interested to know why it's not ext4 when mount says so:

# mount
/dev/block/mtdblock8 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mtdblock6 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data= ordered 0 0
/dev/block/mtdblock5 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data= ordered 0 0

BTW: Why not co-operate on the next rom ?

[Finless]

ttz642t, here is the deal. It's pretty simple.
The ext4 insmod kernel .ko files will mount an ext3 even if the mount command says -t ext4. It just does the right thing!

Trust me I have done EXTENSIVE testing on this. Format system.img as EXT3 with the boot.img init.rc saying mount as ext4 and it will still work! The .ko module figures it out regardless of the -t stating to mount as ext4. Then when recovery system starts after a flash and does it's thing... It formats everything as ext3 anyway! ONLY way to make it right... mod the recovery system that does the formatting!

Now here is the BEST PART Want to see if your truly EXT4. Make the system.img as a ext4 format. I know you know how to do that. Watch how it WILL NOT BOOT.......

Without a new recovery system that formats cache and data as ext4 properly after a flash, the ONLY benefit your getting is the .ko kernel mod is a little faster in processing even an ext3 formatted partition.

Watch my new ROM... Cache, data, system, etc will be true ext4. A hell of a lot of work went into this to make it happen properly!!!! Like 5 days! Fenice is the king behind this but to make it work on other ROMs other than the 7G2.... Took some work on my part as well.

I am sure Admin at Acrtablet will rip our work and make a Kasty ROM with NO... and I mean NO work on his own and put his name on it. I just don't feel that is right. I know Fenice says go for it, etc... But I know Admin will take my ROM directly and do NOTHING VALUE ADDED and put his freakin name on it. THAT is ashame! Open Source is "source". Understand the word "source".... Taking others binary work or ROM and removing all indications of the originals authors work... Is NOT OPEN SOURCE! It's business stealing!

OK OK.... Off my Rant.

Anyway ttz642t, do some ext4 formatting of system.img and test yourself. You will see you cant boot a system.img formatted ext4. So then you know. With Kasty ROM, the only way you will get the Arnova to boot is system.img formatted as ext3! But.. as I said. My ROM 1.4 will have the way!

Bob

[Finless]

BTW: Why not co-operate on the next rom ?

FYI Tell Jim at Arctablet to "not" say he does not support my ROM. He does this because of our requirement here to have an account before you download. How is that different than almost any site out there? We do it because it's to stop SPAMMERS, BOT attacks, rip off sites etc, etc. We have to do that! It's like no choice.!!!

Anyway I understand your ask. It's like... WHY NOT SHARE and make 1 ROM that has all the best. I am game! Why not ask Acrtablet why they are not game? He will take my ROM.... RIP everything out of it thats mine, and call it Kasty ROM? I will be honest here... My opinion.... Site advertising is driving that person NOTHING ELSE.... Oh... other than getting free tablets from Archos and Arnova to do what I think are LAME review videos!

Sorry NO THANKS.... Thats why Will James and I started this place and trust me it will be VERY different!

Bob

[register]

you can always release your unfinished rom as beta
great job youre doing and many thanks for your efforts
dont waste your time in gossip and such who did what and how - nothing stays hidden in the internet

[Finless]

You know.... you are RIGHT! I should not spend time on BS.....

Time to move on! Thanks for reminding me

Bob

[shortcircuit]

copyright protection in your future roms

Hi Bob,

Is there anyway you can protect your hardwork via some copyright clause and stopping anyone doing the same again with your 1.4 version of Rom.

Might also be worth approaching Archos to incorporate your work in future firmwares and generating some revenues for your services.


Thanks for your Rom v1.3. Installed and worked straight away and found no issues.

Keep up the good work.

[snakekiller]

Hang on... download server is being worked on and is down right now.....
It will be up REAL SOON!

Bob

Any chance for today

[HaroldG]

Hi Bob,

Is there anyway you can protect your hardwork via some copyright clause and stopping anyone doing the same again with your 1.4 version of Rom.

Might also be worth approaching Archos to incorporate your work in future firmwares and generating some revenues for your services.


Thanks for your Rom v1.3. Installed and worked straight away and found no issues.

Keep up the good work.

That would be completely antithetical to the Android Open Source Project, and probably violate other intellectual property rights in the process. Besides, since it's all based upon Google's Android, you probably can't protect it anyway. Also, consider the fact that you need to concern yourself with IP rights in the USA, in Europe, in Asia, where IP laws vary substantially.

I'd like to see a lot less of the Jim v. Finless bashing. You guys do your own thing and eventually if you decide to kiss and make up we'll all be better off for it. Otherwise, I'd prefer to see it off the boards.

[Finless]

Well I know it 's open source but lets look at Motorola. They are signing the boot.img which means if you change it, it wont boot. The device has to talk to Motorola to check signage and authorize the ROM. So in fact they are protecting the ROM from being modified. This is exactly how Apple does it with iOS. So not sure they are breaking any laws by protecting thier work or stopping modifications. To date the only (latest) Motorola devices that have been hacked were done through finding an exploit in the OS to get a back door in.
I do not plan to do that as it PO'es people anyway. People have been asking Motorola to stop doing it. Motorola says they have to due to Verison (yea right).

Bob

[ttz642t]

Well I know it 's open source but lets look at Motorola. They are signing the boot.img which means if you change it, it wont boot. People have been asking Motorola to stop doing it. Motorola says they have to due to Verison (yea right).

Bob

Carriers often want their phones tied to their network and with their chosen apps for many reasons, eg: prevent phone using voip (they want the call revenue), support issues (keep all the phones the same), licensing issues (eg if manufacture hasn't licensed some service they can't provide it and should show they have attemplted to limit its adoption).

I doubt manufacturers want to limit & customise the phones as it just increases manufacturing costs & setup, often a phone ends up carrying all the customisations for the world (eating up rom).

[petrus]

Open Source Spirit

Well I know it 's open source but lets look at Motorola. They are signing the boot.img which means if you change it, it wont boot. The device has to talk to Motorola to check signage and authorize the ROM. So in fact they are protecting the ROM from being modified. This is exactly how Apple does it with iOS. So not sure they are breaking any laws by protecting thier work or stopping modifications. To date the only (latest) Motorola devices that have been hacked were done through finding an exploit in the OS to get a back door in.
I do not plan to do that as it PO'es people anyway. People have been asking Motorola to stop doing it. Motorola says they have to due to Verison (yea right).

Bob

Hi,

First of all, a Great thanks for the amazing work you did.
I first went to "the other guy who's name is not to be told" and didn't manage to update with the poor directions that were given there.

I agree that his site doesn't seem fair, as it seems to imply that his rom is a new version of yours, which is not maintained anymore. That is simply bad. I think it is because he is mad at you, and he really thinks he is the good guy.

And simply because he puts a 2.0 version number where you are only 1.3 is why people think his rom is better.

But with a little search, we finally come here to find useful instructions on how to flash. And here, we can learn that your rom is better. That's the point.

I think your fight at first seems like an ego fight (that's what i thought from your posts on his site) but if you didn't complain on his site, I would never have come here, which I'm glad I did.

I'm looking forward to 1.4 very bad, as it seems to kick ass. But I cant' wait, so I will try 1.3 first, which seems really worth the assle.

For now, I had a hard fight to put the tablet in revovery mode, and then another even worse fight with win7 to install the drivers.

For now, I just gave up with win7 on my desktop. I think that the front usb acts like a hub. So I will try with my win7 laptop. Maybe it will detect the tablet in recovery mode better (as I didn't connect them yet).

So, I hope you won't be too upset with your work being hijacked. That's part of the game with open source. But in my opinion it is better than having a powerful company sue you for violating their licensed products and make you totally stop developping for free.

Thank you again, and I hope to get 1.4 soon. I'll try 1.3 right now.

PS : sorry for my english. I'm french, and lazy

[petrus]

Another Brick in the wall

So, I'm a little less optimistic here. I just bricked my device. Everything went well, before I flashed the rom, it just told me that it failed, then, I cannot even turn the tablet on. It is still recognized when I put it in recovery mode but every action fails, then, even flashing the original rom.Is there something I can do? Can I send you some log file?

[snakekiller]

So, I'm a little less optimistic here. I just bricked my device. Everything went well, before I flashed the rom, it just told me that it failed, then, I cannot even turn the tablet on. It is still recognized when I put it in recovery mode but every action fails, then, even flashing the original rom.Is there something I can do? Can I send you some log file?

Did you click first one erase....
And then on run.
I now from my android phone if you could in recovery mode than its not bricked.

[Finless]

Yes make sure you EraseIDB and make sure you selected the loader check box.

When you say it failed. What failed? Where was the message showing up? If after flash you got a formatting data or cache failure message on the tablet then you either did not eraseIDB or you did not update the loader to 2.08 by clicking the loader box.

Bob