Skip navigation

Monthly Archives: July 2010

These are my previous N1 screenshots with ADW Launcher. Currently I’m using LauncherPro. Will upload the screenshots soon if I got time.

Advertisements

This time I post about installing Froyo into hTC HD2, thanks to my friend kasmankk who gave me a trust to poke his phone for this experiment. Credits also goes to HD GEEK from XDA Forum and addictivetips site for their comprehensive guidelines.

DISCLAIMER : This should NOT be attempted if you’re not comfortable messing with the system. I will not be held responsible if you brick your device. By following these steps, you agree to bear your own risk.

Original setup :

SPL : 1.42.0000
OS : 5.2.21869 (21869.5.0.82) Windows Mobile 6.5
Manila : 2.5.19211619.0
ROM : 1.66.707.1 (76641) WWE
ROM date : 01/12/10
Radio : 2.06.51.07
Protocol : 15.30.50.07U

Froyo prerequisites :

SPL : 2 or 3
ROM : Custom ROM (eg. ChuckyROM GTX + CHT 1.8.5 – 23128 ~ 2.10.1)
Radio : 2.08 ~ 2.12

I’ve decided to choose HardSPL 2.08 and Radio 2.12 for this test.

Steps taken :

1. Install HardSPL 2.08 GUIDE
2. Install radio 2.12 GUIDE
3. Install custom ROM (ChuckyROM) GUIDE
4. Download Froyo build here, extract and copy the Android folder and its contents into the SD card
5. Navigate to the Android folder in the device
6. Run CLRCAD.exe
7. Run haret.exe
8. Enjoy your Froyo!!!

New setup for Froyo :

SPL : 2.08.HSPL
OS : 5.2.23128 (23128.5.3.8) WinMo 6.5
Manila : 2.5.20161332.0
ROM : ChuckyROM WWE
ROM date : 21/07/10
Radio : 2.12.50.02_2
Protocol : 15.40.50.07U

Froyo port to HD2 is still in its early stage, thus few bugs exist. However I’m sure it’ll be solved soon…

Till then, the device will be returned to its rightful owner for him to play around with it.

OK kasmankk, what’s next? Root your Desire eh? 😉

Video :

Screenshots :

Recently I helped one of my friend updating his N1 to UV/OC kernel by pershoot. However we found a strange problem when the kernel image is being written to the device. I update lots of kernel before on my N1 but never encountered such issue like this. Here’s the error :

C:\Superboot>fastboot-windows flash zimage zImage
sending 'zimage' (2280 KB)... OKAY
writing 'zimage'... FAILED (remote: unknown fail)

C:\Superboot>


Tried a few kernel variants didn’t solve the problem. I end up re-flash the ROM without wipe. Fortunately it works! Kernel update was successfully done after that.

I’ve been waiting for CM6 released for quite sometimes now and as promised, Cyanogen and his team of developers has again amazed the Android world with their magic touch. This version was released on 11 July 2010, and I managed to update it soon after the news has been tweeted. Did the clean wipe before flashing it into my N1. Prior to this, i was using custom FRF91 r21 from PaulOBrien (MoDaCo) with pershoot 2.6.35-RC3 UV/OC kernel.

However, as expected, few bugs exists which need to be ironed out on the next release. The system dumped me with several FCs soon after all the backup apps being reinstalled. Running fix_permissions and moving all widgets apps to phone storage did some tricks, but not entirely solve the problem. The android.process.acore still randomly generates an FC. Looks like I’ve to google around to find out how to get rid of it. Any suggestion?

My advice, stay away from it if you don’t like the system intermittently greets you with annoying FC. Wait for stable version instead.

To me, I can’t resist the temptation of CM6 so probably I’ll stick with it until the next stable version released.