13 replies to this topic

[wdfowty]

Froyo with a little WD40 in the gears!

Presenting WD40M0D! This is my first rom, so I still need feedback. (feel free to let me know in this thread)


What's inside?
*Built from AOSP (last sync 7/27/10)
*Stock Froyo kernel
*Rooted boot partition with "adb remount" permission
*Superuser 2.2.2 from ChainsDD
*Added busybox and bash
*Custom yellow bootanimation by JHPadu

What I'm planning:
*LeoParts
*Tweaks from CM source
*Faster kernel (won't be oc'd)



Download: (IMPORTANT!!! READ THIS POST TO FIX SUPERUSER.APK!)
http://www.mediafire...PHA2-signed.zip

Radio: (You MUST have a Froyo radio!)
4.06: http://www.mediafire.com/?kgk8rirjmgy (fastboot flash radio radio.img)
5.08: http://www.mediafire.com/?og2folywjny
(*NOTE*: Either radio will work, I have used both. If you have issues with network switching or wifi on 5.08, try 4.06)


Installation:
1. NANDROID BACKUP
2. Install radio, either via recovery or fastboot
3. Wipe data/cache, and Dalvik cache
4. Flash the WD40M0D-signed.zip via recovery
5. Enjoy!


Thanks to (no order): Google, dsixda, ChainsDD, JHPadu, stampere, KingKlick, Rsotbiemrptsonr, leonnib4
(if I left you out, please let me know)

Edited by wdfowty, 05 August 2010 - 08:15 PM.

[wdfowty]

Changelog:

7/29/10
*Initial release (alpha 1)
*updated gapps link

8/04/10
*Using new updater-script format, thanks to leonnib4 for the help
*Integrated gapps

Edited by wdfowty, 05 August 2010 - 08:09 PM.

[micronian]

Any possibility of making the ActiveSync client's user-agent customizable?

[wdfowty]

micronian, on Jul 31 2010, 10:35, said:

Any possibility of making the ActiveSync client's user-agent customizable?

Customizable in what respect? I'm not quite sure what you mean.

[Denver Pedro]

I get an error when installing this ROM... any advice?

I'm trying to find a good and very recent AOSP build to try and resolve a known issue with Client Cert connectivity in FroYo.  Google has confirmed a fix but it hasn't been OTA released yet and even the latest CM6 release doesn't seem to address my issue.  So I'd love to try this ROM to see if it incorporates the fix (which Google has released to AOSP per this link: http://android.git.k...7c157904908c156 )

So I'd love to be able to get this to work.  I have the FroYo radio installed (4.06.00.12.7), I did a factory reset and wiped cache and dalvik cache prior to attempting the install.  The following is the error I get when trying to install this:

Copying files...
E: Error in installbusybox
(Status 32256)
E: Failure at line 28:

Installation aborted.

Thanks for any help.

-Pete

[wdfowty]

I want to try to recreate the issue on my phone.

I need to know what rom you were on before this, which kernel, which recovery you are using, and the md5 sum of the update zip.

Try re-downloading to see if the problem persists.

Edited by wdfowty, 02 August 2010 - 06:51 PM.

[Denver Pedro]

wdfowty, on Aug 2 2010, 11:23, said:

I want to try to recreate the issue on my phone.

I need to know what rom you were on before this, which kernel, which recovery you are using, and the md5 sum of the update zip.

Try re-downloading to see if the problem persists.

I was on CyanogenMod 5.0.8-N1 (well still am, I've reverted back to it for now).  I have the Amon-RA recovery installed (1.7.0.1 Cyanogen version) and as previously mentioned I'm on the FroYo radio (version 4.06.00.12.7).  I did a full wipe (user data/factory reset as well as cache and Dalvik cache) prior to the install, I did NOT re-install the radio prior to the update ZIP file.

MD5 of the update ZIP file is:  MD5 (WD40M0D-alpha1-signed.zip) = c5204a01e0e7548c6eb84dc05c273d4a

I'll try re-downloading and re-installing if you think that will help.

Thanks,
Pete.

[wdfowty]

Denver Pedro, on Aug 2 2010, 12:48, said:

I was on CyanogenMod 5.0.8-N1 (well still am, I've reverted back to it for now).  I have the Amon-RA recovery installed (1.7.0.1 Cyanogen version) and as previously mentioned I'm on the FroYo radio (version 4.06.00.12.7).  I did a full wipe (user data/factory reset as well as cache and Dalvik cache) prior to the install, I did NOT re-install the radio prior to the update ZIP file.

MD5 of the update ZIP file is:  MD5 (WD40M0D-alpha1-signed.zip) = c5204a01e0e7548c6eb84dc05c273d4a

I'll try re-downloading and re-installing if you think that will help.

Thanks,
Pete.

Here's what I need from you: Boot into recovery, scroll to Other -> Move recovery.log to SD. Upload it to pastebin and send me a link please.

Have you tried any other Froyo roms? Seems like there may be a script issue when going from 2.1 to 2.2...Will research. In the meantime, try fastboot update method.

Power phone on while pressing trackball.

fastboot update /path/to/WD40M0D.zip

Edited by wdfowty, 02 August 2010 - 09:14 PM.

[Denver Pedro]

wdfowty, on Aug 2 2010, 13:35, said:

Here's what I need from you: Boot into recovery, scroll to Other -> Move recovery.log to SD. Upload it to pastebin and send me a link please.

Have you tried any other Froyo roms? Seems like there may be a script issue when going from 2.1 to 2.2...Will research. In the meantime, try fastboot update method.

Power phone on while pressing trackball.

fastboot update /path/to/WD40M0D.zip

Here's the link to the logs:  http://pastebin.com/miZzNTT5

Also, I tried the fastboot update and it failed indicating the zip file was missing some components (I didn't have time to write down the exact error, if you want it I'll try and re-install and capture the exact error).  If I remember correctly it was missing some sort of manifest (either by name or by the name of the file it was clear it was a manifest of sorts).

I hope that helps.

Thanks,
Pete.

[Denver Pedro]

Denver Pedro, on Aug 2 2010, 18:15, said:

Here's the link to the logs:  http://pastebin.com/miZzNTT5

Also, I tried the fastboot update and it failed indicating the zip file was missing some components (I didn't have time to write down the exact error, if you want it I'll try and re-install and capture the exact error).  If I remember correctly it was missing some sort of manifest (either by name or by the name of the file it was clear it was a manifest of sorts).

I hope that helps.

Thanks,
Pete.

The error messages I get during the fastboot install are:

archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt

Hopefully that helps as well.

-Pete

[wdfowty]

Denver Pedro, on Aug 2 2010, 19:18, said:

The error messages I get during the fastboot install are:

archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt

Hopefully that helps as well.

-Pete

I consulted with KingKlick and I think it's all figured out. I'll make some changes and upload a beta tomorrow.

[Denver Pedro]

wdfowty, on Aug 2 2010, 22:12, said:

I consulted with KingKlick and I think it's all figured out. I'll make some changes and upload a beta tomorrow.

Awesome, I'd love to test it out.

Thanks

[wdfowty]

Denver Pedro, on Aug 3 2010, 14:11, said:

Awesome, I'd love to test it out.

Thanks

Sorry, wasn't around today to make tweaks. Tomorrow (technically today lol) for sure

[wdfowty]

Ok, it's flashable now. The update script was completely overhauled. Let me know if any more issues arise


ATTENTION! To fix SuperUser.apk, follow these instructions:

Download this: http://www.mediafire...s33c81qgzabj/sh

adb remount

adb push /path/to/sh /system/bin

adb reboot

To test if it worked, type in terminal:

adb shell

I'll add this to my update.zip and upload after the weekend. Gone camping

Edited by wdfowty, 05 August 2010 - 07:09 PM.