Monthly Archives: June 2010

AT&T Nexus One to Froyo

Posted on by

It’s been a while after T-mobile one got Frozen Yogurt. However, it’s time to end since Google started pushing Froyo OTA update since last week. I got 2 OTA updates, but they both failed to complete the update. Why? because I rooted my EPE54B. Thus, OTA will not do the job nicely.

How? you can do all manual update =) As of now, Google released FRF85B. For whom you might not understand, all T-mobile and AT&T, which have their own build number, will have to same build, FRFxx. When Google first released Froyo to T-mobile Nexus One, it’s like FRF50. However, not it’s FRF85B which is official.

Update procedure: it will be 2 path for rooted N1 and unrooted N1.

1. For unrooted N1, EPE54B, you just grab images of your build below.

2. Rename the file to update.zip and copy to root directory of SD.

3. Reboot your N1 to recovery mode by holding volume down + power. You will get into HBoot/Fastboot mode.

4. Use volume up/down to select menu and power to select “recovery.” N1 will reboot again to /!\ page. That’s fine. Then, you have to get into recovery mode by holding power and press volume up.

5. You will see Android system recovery;you now can use your trackball to select any option. Choose apply sdcard:update.zip

6. Wait until reboot and have fun with Frozen Yogurt.

 

For rooted N1, you will have to take rougher route. You actually have many ways to do so. Custom ROM like Modaco or else, for example. However, I just prefer to have original ROM with root access. You can follow these steps to do so:

1. go back to original image.

2. update as unrooted N1 steps above

3. root FRF85B

For the first step, you need to download original image, here. Please check md5 too. Then you have to extract boot.img, recovery.img out to your android-sdk tools directory (c:\android-sdk\tools for me) Now you are ready to copy old image to replace superboot one by fastbooting. You have to get to Fastboot mode and check if it’s Fastbook USB which is indicated connection between N1 and computer.

c:\android-sdk\tools> fastboot devices  // to check if computer sees N1
c:\android-sdk\tools> fastboot erase userdata
c:\android-sdk\tools> fastboot erase cache

This 2 steps above are optional and if you use Amon_RA’s recovery, you will have to get into recovery mode to wipe those.

c:\android-sdk\tools> fastboot flash boot boot.img
c:\android-sdk\tools> fastboot flash recovery recovery.img
c:\android-sdk\tools> fastboot reboot

That would be all set for returning back to original image =) (well, not exactly true since we didn’t care about system.img and userdata.img which the update doesn’t bother.)

For the last step, download superboot image here. Then rename to update.zip and apply sdcard:update.zip in recovery mode like when you did with updating Froyo image.

Now you will be very happy AT&T Froyo Nexus One like I am.

 

Note: FRF85B root update.zip didn’t do the trick for me since it’s error while updating. If you face the same situation, just ask. You can do a manual way also =)

Popularity: 6% [?]

How to automatically share calendar to all users in Google apps

Posted on by

Answer: none, AFAIK. You might argue that you can just add user manually or share calendar by XML, iCal, or even HTML link. That’s just like the way regular Google account can do. What is good about Google apps then?

1. You can set your accout’s calendar to share with everyone in the organization. That would work too and it’s pretty easy to for others to add since that calendar has a name as your email account. But I bet you wouldn’t want to share what is yours to others, would you?

2. Add new calendar, then set share to everyone and share the link. It’s a bit harder then the first option, but that works.

What is a drawback of these two options? It’s pain in the ass if you want everyone that shares the calendar to add/edit too. You have to add each of the manually individually. In short, if you want then to just see, either of these is OK, but not for collaborate.

How? You think Google leave this out really, huh? No, they have a way for that.

[yourdomainname]_@domain.calendar.google.com

That’s the only one calendar ID that anybody can add, and everyone has full permissions! Anyone in the Google Apps can just put this ID to “add a coworker’s calendar” then simply “enter.” It will go to your calendar easily. For the sake of privacy? people outside your Google apps won’t be able to even see.

I would love to have more choices, but so far I have yet to find other ways. If you know any other, please share =)

Added [the day later]

The easier way, and probably better way, is using group. You have to create group then add users or add all. When you want to share, just add team email to the calendar. Google will send out invitation email to anyone in the group automatically. The calendar ID will be like [domain]_[calendar.ID]@group.domain.calendar.google.com and this works similar to domain.calendar.google.com—outsider can’t access in any way.

Popularity: 9% [?]

Live: sign in with a single-use code

Posted on by

single-use codeMicrosoft might not be trend setter anymore these days, but they are working hard to be back. That’s for sure. Live Mail or hotmail is one of popular email in the world, regardless of how good it is. Once in a while I get in my account to check if there is any of my mail, besides loads of junk. Then I noticed something new, single-use code ??

 

It’s just like one-time password; use it and throw away. That’s for anyone who are concerned about leaking password on public network/computer. Yes, it’s pretty good idea, but is it practical? So I tried.

image

Above is what I got. My Google Voice number might be the cause of the issue, but if that’s the case, Microsoft should give up this option also.

Moreover, I hope to see Microsoft back in the game, but so far, Live Mail? ie? Zune HD?, Windows Phone 7? Windows Embedded Compact 7? I still don’t see a bright future for those yet. Firstly, they should have easier & more consistency name LOL.

Popularity: 17% [?]