U8110 Android 2.1 ROM

[Guest]

I'm new here, so please excuse my lack of understanding.

Why are everyone so impatient for BigBear to release this rom when Huawei is going to release the official 2.1 update in a week or so?

(if they manage to keep their promise.)

Edited May 8, 2010 by Guest

[Guest Rem1x]

I dont think that this is the way to think of it.. Maybe he wants to prove himself, show you nonbelievers that he can, not that he'll give up. Hes running into problems, so give him a break.

Yeah, give him a break.

If you followed the OpenPandora project you'd know all about waiting, and the failures that come before something amazing :P

(having had £217 in the project since 03/10/2008(when it all started, we still don't have the thing), I'm biased :D)

Edited May 8, 2010 by Rem1x

[Guest DanWilson]

I'm new here, so please excuse my lack of understanding.

Why are everyone so impatient for BigBear to release this rom when Huawei is going to release the official 2.1 update in a week or so?

(if they manage to keep their promise.)

We are so impatient because Huawei may not stick to the promise, or T-Mobile may delay it. And, who wants to be on 1.5 any longer than they have to be? :P

[Guest davbren]

:P

Why's that epic?

Why your username isn't "DerHofmeister" I don't know...

[Guest DanWilson]

Is it bedtime in Austria or is BigBear just hiding?

[Guest BigBearMDC]

Okay guys, I'm not a dev, and I never said that I'm a dev.

But I wouldn't say that all of my projects failed ultimately, I mean the MT driver is working, I can read the coordinates of the second touchpoint, the problem is that the HW doesn't deliver them, so they stay at zero (or 256).

I just had a very quick look at the overclocking thing, I only tried it once, and I have to say that I knew that it wouldn't work because the structure of the driver itself was different.

The Hero ROM port was really too much for my first project, my knowledge was just too little, as it is now.

But how do you think all the devs started?

I don't think that the learned it in 2 hours...

Learning-by-doing is my motto.

And in this special case, I know exactly what I'm doing.

And I know what the problem is, so please, just give me some time to resolve this problems.

I already have an update.zip ready that should work perfect on the Pulse, but I haven't got the chance to try it as I just can't reapply the dec update.

The problem is that the version string of the current ROM is not in the upgradeable versions of the dec update (how should it, it has been released later).

I know that I'm maybe not the best person to do this task, but I think I've proven enough that I really take care of my projects, and I really want to learn.

Then maybe one day I will be a real dev, with the righr supporters.

So please, just hold on, I'm working eagerly on getting this working.

By the way, no news yet.

I'm not at home right now, but don't worry, Huawei SWAT is ridiculous, they don't even manage to stop me when I'm on my motorcycle :P

Greetings,

BigBear

Edited May 8, 2010 by BigBearMDC

[Guest eckengucker1]

Du bist sehr positiv!

in ogni caso :P

[Guest DanWilson]

Okay guys, I'm not a dev, and I never said that I'm a dev.

But I wouldn't say that all of my projects failed ultimately, I mean the MT driver is working, I can read the coordinates of the second touchpoint, the problem is that the HW doesn't deliver them, so they stay at zero (or 256).

I just had a very quick look at the overclocking thing, I only tried it once, and I have to say that I knew that it wouldn't work because the structure of the driver itself was different.

The Hero ROM port was really too much for my first project, my knowledge was just too little, as it is now.

But how do you think all the devs started?

I don't think that the learned it in 2 hours...

Learning-by-doing is my motto.

And in this special case, I know exactly what I'm doing.

And I know what the problem is, so please, just give me some time to resolve this problems.

I already have an update.zip ready that should work perfect on the Pulse, but I haven't got the chance to try it as I just can't reapply the dec update.

The problem is that the version string of the current ROM is not in the upgradeable versions of the dec update (how should it, it has been released later).

I know that I'm maybe not the best person to do this task, but I think I've proven enough that I really take care of my projects, and I really want to learn.

Then maybe one day I will be a real dev, with the righr supporters.

So please, just hold on, I'm working eagerly on getting this working.

Greetings,

BigBear

I'll try it for you!

:P

(Hold on, cant you just add the version string to the december update / MoDaCo Rom?)

Edited May 8, 2010 by DanWilson

[Guest BigBearMDC]

I'll try it for you!

:P

Well, you're already on my list of possible probands :D

[Guest BigBearMDC]

(Hold on, cant you just add the version string to the december update / MoDaCo Rom?)

Yeah, that's what I tried, but there are checksums in that UPDATA.APP, which won't match anymore when I edit something in the file :P

[Guest DanWilson]

Well, you're already on my list of possible probands :D

Wait - What?

Proband, or propositus, is a term used most often in medical genetics and other medical fields to denote a particular subject (person or animal) being studied or reported on.

I dont want drugged!!! :P

[Guest BigBearMDC]

The next thing I will try is to reflash the system image with the rooted build.prop file.

[Guest DanWilson]

Yeah, that's what I tried, but there are checksums in that UPDATA.APP, which won't match anymore when I edit something in the file :P

Is there no way to update the checksums? Or is that asking waay to much?

[Guest BigBearMDC]

Wait - What?

I dont want drugged!!! :P

:P

LoL

Leo dictionary isn't the best place to look up words :P

You're on the list of my test-persons :D

[Guest Rem1x]

Okay guys, I'm not a dev, and I never said that I'm a dev.

But I wouldn't say that all of my projects failed ultimately, I mean the MT driver is working, I can read the coordinates of the second touchpoint, the problem is that the HW doesn't deliver them, so they stay at zero (or 256).

I just had a very quick look at the overclocking thing, I only tried it once, and I have to say that I knew that it wouldn't work because the structure of the driver itself was different.

The Hero ROM port was really too much for my first project, my knowledge was just too little, as it is now.

But how do you think all the devs started?

I don't think that the learned it in 2 hours...

Learning-by-doing is my motto.

And in this special case, I know exactly what I'm doing.

And I know what the problem is, so please, just give me some time to resolve this problems.

I already have an update.zip ready that should work perfect on the Pulse, but I haven't got the chance to try it as I just can't reapply the dec update.

The problem is that the version string of the current ROM is not in the upgradeable versions of the dec update (how should it, it has been released later).

I know that I'm maybe not the best person to do this task, but I think I've proven enough that I really take care of my projects, and I really want to learn.

Then maybe one day I will be a real dev, with the righr supporters.

So please, just hold on, I'm working eagerly on getting this working.

By the way, no news yet.

I'm not at home right now, but don't worry, Huawei SWAT is ridiculous, they don't even manage to stop me when I'm on my motorcycle :P

Greetings,

BigBear

I'll try it too :D

And you are a dev! Stop being silly, you developed the Multitouch, you're getting 2.1 rooted! You're one of the most important of the Pulse community!

[Guest BigBearMDC]

Is there no way to update the checksums? Or is that asking waay to much?

There is sure a way to do this, but I don't know how.

I had a look at it with a HEX editor and already changed the version string but ... HELL, that's a 130 MBs large file!

Damn it :P

[Guest DanWilson]

:P

LoL

Leo dictionary isn't the best place to look up words :P

You're on the list of my test-persons :P

Ah. I feel honored. I mean, I've never been one for speeches but... :D

[Guest Blake Loring]

There is sure a way to do this, but I don't know how.

I had a look at it with a HEX editor and already changed the version string but ... HELL, that's a 130 MBs large file!

Damn it :P

Can't you work out the checksum of the original file and then search for that set of bytes in a hex editor, that will give you the offset needed to find and modify the checksum (So after your mods are done you can move to that offset + how many bytes you have added or removed and then edit it.)

[Guest BigBearMDC]

Okay guys, I'll leave you for now.

I'll report back my new findings in a few hours.

I need some time for thinking :D

See you all later :P

Edited May 8, 2010 by BigBearMDC

[Guest shisan]

Okay guys, I'm not a dev, and I never said that I'm a dev.

But I wouldn't say that all of my projects failed ultimately, I mean the MT driver is working, I can read the coordinates of the second touchpoint, the problem is that the HW doesn't deliver them, so they stay at zero (or 256).

I just had a very quick look at the overclocking thing, I only tried it once, and I have to say that I knew that it wouldn't work because the structure of the driver itself was different.

The Hero ROM port was really too much for my first project, my knowledge was just too little, as it is now.

But how do you think all the devs started?

I don't think that the learned it in 2 hours...

Learning-by-doing is my motto.

And in this special case, I know exactly what I'm doing.

And I know what the problem is, so please, just give me some time to resolve this problems.

I already have an update.zip ready that should work perfect on the Pulse, but I haven't got the chance to try it as I just can't reapply the dec update.

The problem is that the version string of the current ROM is not in the upgradeable versions of the dec update (how should it, it has been released later).

I know that I'm maybe not the best person to do this task, but I think I've proven enough that I really take care of my projects, and I really want to learn.

Then maybe one day I will be a real dev, with the righr supporters.

So please, just hold on, I'm working eagerly on getting this working.

By the way, no news yet.

I'm not at home right now, but don't worry, Huawei SWAT is ridiculous, they don't even manage to stop me when I'm on my motorcycle :P

Greetings,

BigBear

come on!

keep trying!

[Guest BigBearMDC]

Can't you work out the checksum of the original file and then search for that set of bytes in a hex editor, that will give you the offset needed to find and modify the checksum (So after your mods are done you can move to that offset + how many bytes you have added or removed and then edit it.)

That was my first thought too, but I A) don't know what format that checksum has (I suspect it to be a base64 MD5) and B ) don't know how to generate it.

I know ho to generate a base64 MD5, I wrote my own application that does this, but I think there are different checksums for each file and a checksum for the whole archive.

I already asked McSpoon, as he developed the split_updata script, but he couldn't help me either :P

Edited May 8, 2010 by BigBearMDC

[Guest BigBearMDC]

come on!

keep trying!

Don't worry, I'll never give up :P

[Guest dodge-167]

I think that you need to change name of this topic... :P

[Guest DanWilson]

I think that you need to change name of this topic... :P

I think we need a new one... :D

[Guest dodge-167]

I think we need a new one... :P

Or that, i think that your option will be probably better... :D