Android on HD2 updates + ROMs + Builds - Page 13

ultra2 · #1 (**permalink**) 08-04-2010, 05:00 AM

thanks for the 2.2 clarification. I tried mattcfroyorc1.3a yesturday and ran fine until the phone was rebooted a couple times, it would stop on an error stating the rootfs needed to be unzipped. I guess I'm at a loss how this was bootable a few times, then semed to be unusable. I'm now running mattcfroyorc1.4 which was just released, and is working fine so far, but haven't rebooted the phone any. I have tried the patched root fs files in post #2, but still came up with the same message. Any ideas? Thanks for all the info on such a neat website!

**orangekid** · #2 (**permalink**) 08-04-2010, 09:12 AM

Quote:

Originally Posted by ultra2

thanks for the 2.2 clarification. I tried mattcfroyorc1.3a yesturday and ran fine until the phone was rebooted a couple times, it would stop on an error stating the rootfs needed to be unzipped. I guess I'm at a loss how this was bootable a few times, then semed to be unusable. I'm now running mattcfroyorc1.4 which was just released, and is working fine so far, but haven't rebooted the phone any. I have tried the patched root fs files in post #2, but still came up with the same message. Any ideas? Thanks for all the info on such a neat website!

those patched rootFS files were made specifically for the builds mentioned, so using them on mattcfroyo won't work. He needs to make a rooted rootFS for his ROM

mgioia2 · #3 (**permalink**) 08-04-2010, 10:32 AM

Just reinstalled Darkstone 1.7 and after the first call i got i had sleep of death...ugh...

Call quality was GREAT though with Cutolla's newest zImage...just wish i could figure out this SOD crap...

**orangekid** · #4 (**permalink**) 08-04-2010, 12:14 PM

Quote:

Originally Posted by mgioia2

Just reinstalled Darkstone 1.7 and after the first call i got i had sleep of death...ugh...

Call quality was GREAT though with Cutolla's newest zImage...just wish i could figure out this SOD crap...

why did you install Darkstone v1?

btw its not *.7, this extension is .7z so it looks that way,

here's what you should do:

1) delete all your android builds and files from your SD

2) download dardstone desire v5 from post 2

3) extract it to root of you SD card

4) boot android

5) turn off your phone

6) turn it on to winmo in "disk mode"

7) replace the zimage with cotullas new one from Aug 3, replace the rootFS file with the rooted one from post 2 for Desire v5

boot up Android

should work fine now. Use setCPU to tweak your processor settings, it makes a difference on battery drain and speed.

Download Autokiller and tweak memory settings (I use extreme) to speed up your fun! You should have no SOD.

mgioia2 · #5 (**permalink**) 08-04-2010, 12:45 PM

Quote:

Originally Posted by orangekid

why did you install Darkstone v1?

btw its not *.7, this extension is .7z so it looks that way,

here's what you should do:

1) delete all your android builds and files from your SD

2) download dardstone desire v5 from post 2

3) extract it to root of you SD card

4) boot android

5) turn off your phone

6) turn it on to winmo in "disk mode"

7) replace the zimage with cotullas new one from Aug 3, replace the rootFS file with the rooted one from post 2 for Desire v5

boot up Android

should work fine now. Use setCPU to tweak your processor settings, it makes a difference on battery drain and speed.

Download Autokiller and tweak memory settings (I use extreme) to speed up your fun! You should have no SOD.

Well V1 is his Froyo ROM (from the 26th), V5 is the old 2.1 W/Sense ROM...i may try that one again anyway, it did give me less problems in general and i do prefer Sense...

EDIT: I keep going back to the Froyo build because it recognized the PC and has file transfer capabilities...couldn't remember if DarkStone V5 did?

CaliCL9 · #6 (**permalink**) 08-05-2010, 06:46 PM

im using the new data.img it works great..

ultra2 · #7 (**permalink**) 08-05-2010, 08:50 PM

Spimonkey's 1.4 working great!

ultra2 · #8 (**permalink**) 08-06-2010, 04:54 AM

Ok, jokes on me, this morning's boot up of phone has the same message, "can't find rootfs, please un zip". The file is there, but must be corrupt. I'm missing something here, is windows doing something to the sd that's not allowing Android to boot?

mgioia2 · #9 (**permalink**) 08-06-2010, 07:45 AM

Quote:

Originally Posted by ultra2

Ok, jokes on me, this morning's boot up of phone has the same message, "can't find rootfs, please un zip". The file is there, but must be corrupt. I'm missing something here, is windows doing something to the sd that's not allowing Android to boot?

It just gets corrupted somehow, this isn't a perfect port yet.

Best build so far is the Darkstone V5, there are a few of us who have run it for days switching back and forth and not getting that error. Everytime i try to run the Froyo 2.2 builds i get that error.

mgioia2 · #10 (**permalink**) 08-06-2010, 07:47 AM

Okay so i've been running the 512MB data.img and the 384MB zImage and i have to say is DAMN Android can be a lot faster!

The 512 data.img i've ran for a couple more days and it tends to get unresponsive every now and then...if you just let it set for 4-5 seconds it picks right back up and keeps going though...

The 384 zImage hasn't done anything negative that i've seen but the responsiveness has gone through the roof! From what i read Cotulla is working on a 500MB zImage to be released soon!