Failed To Create The Account. Please Try Again Later

I'm an avid Android fan. Also, I love to tinker. So when I bought the HTC One, the first thing I did was to have its Bootloader unlocked and the S-OFFed. This just opened up a lot of opportunities for me to do with the device. So after having converted the device to a Google Edition device and played with the Android 4.3 update, I tried my luck with the new 4.3 Developer Edition RUU which was released for the HTC One. Like and idiot, I relocked the bootloader and flashed the RUU. But after observing some considerable drain in standby mode, I wanted to root the device. Had to generate a new Unlock_token.bin from HTC since it was a new HBOOT at 1.55. Unlocking the bootlaoder resulted in clearing up the entire device. So, in the midst of the setting up the phone, I decide that while the phone is syncing - which would take a while on my slow wi-fi, I thought of disabling the system apps that I wont be using.

So when this activity was done, I configured my Google Apps Mail account which was done in a jiffy. Moving on to the Exchange Active Sync account, which usually takes a minute to sync, kept on giving me the "Failed To Create The Account. Please Try Again Later". Googling for it didnt give me any results, let alone positive ones. It had become annoying. Though today was a Sunday, some work was stuck. Thought of re-installing the RUU or going back to the Google Edition one. I was lost!

Then it happened, somewhere it just clicked! There are 4 options available when we setup the sync for the Exchange Active Sync account. Calender, Contacts, Mail and Tasks. I just realized that I had disabled the system tasks app, which was causing an exception when I tried to set up the sync. So this is something that I experienced and solved. No one online had posted if this was ever the case when they ever faced this particular error. 

Note : Sadly ADB wasn't detecting my device but fastboot is working fine. Hence couldn't analyze an logcat logs. my bad.

Sunday Fixing

That would be the best and shortest way to describe my day. Right from 12:00 am in the morning, I have been fixing various issues with the devices I own. These include the new Dell Laptop, the Xoom tablet and the Galaxy S2. The galaxy S2 didn’t have any issues as such, but I was just trying out various different ROMS on the device and then pretty much lost it with the MIUI. Very very annoying and ugly interface for me, thankfully I had done a nandroid backup of the CM7.1 nightly I was running. So that was that. The SGS issues were at 4:00am.

Now coming to the windows installation on my machine, that is the new dell laptop, I had blown up the MBR. What happened was that I wanted to try out the MAC OSx on my laptop. But do go ahead with it, I first had to remove the linux installation on the machine and reclaim the drive space. Once that was done, it was all easy, atleast supposed to be easy to just boot into windows recovery using the Windows Home Premium boot disk that I had. But somehow it just wouldn’t boot into windows. I was quick to give up on it and downloaded an image from the web which could be made out to a Windows boot disk. Turns out, that image was only for installation of windows 7 and not for any recovery activities. Annoyed me a lot, but then, I had to go back to the earlier disk and it finally worked. So when all this was done, it was already 3:00am and so started playing with the Galaxy S2.

And finally, the Xoom. This was in the late afternoon today. I was using this tiamati Rom on it, which pretty much labelled the tablet as a Verizon Xoom and any update that Google pushed to it would brick it. So I just went back, i.e. tried to go back to the earlier stock build of Xoom which I had nandroided. I was in for a surprise when I did this, the wifi wouldn’t just start, let alone scan and connect. So I again went online to look for a stock rom. Found a rooted one, downloaded it but sadly, this one had another issue. Again it was with wifi, the drivers installed or something about the wifi module was so wrong that it would scan the networks but never accept any DHCP ip addresses and also wouldn’t let me set any on the tablet. So downloaded the retail copy of the ROM from the Motorola Dev site and then had to manually flash the system, boot and other images onto the Xoom using fastboot. Fortunately it worked alright.

So till the internet from plusnet is properly installed here, have to stick to the 3 unlimited internet plan. Bad weekend, but on the plus side, 28 more work days till I finally get to back HOME!