Wednesday, October 31, 2018

Google Apps error report and workaround

S sent me the following:

FYI, for future reference. 

Was trying to create a new email Id in Google Apps. 

Clicking on the 'Users' menu item in the Admin panel of Google Apps, repeatedly gave "Error 400, URL is not available error" described here. Tried the steps described there.  

Finally, I could get there and create the same only through the Plain-HTML Gmail interface. Nothing else worked.

Friday, October 26, 2018

google group permissions for Google Apps domain

Reply to a query from one of my colleagues, who had an issue with some users on a domain getting the message: "You only have read-only access to groups outside of your domain. Contact your domain administrator for more information."

(The actual domain names have been changed :)

Whoever is the admin for your whateveritwas.extension domain in Google Apps, has to enable access.

I believe that whateveritwas.extension was set as a domain alias for anotherdomain.com in Google Apps? I see an email thread where I suggested that this was a possibility. In that case, webmaster@anotherdomain.com would be the admin.

After logging on to webmaster@anotherdomain.com , go to the administrative console at
https://admin.google.com/Dashboard

According to this page,
https://productforums.google.com/forum/#!msg/apps/6wYszBdjuaI/W1cJcvxAf50J

"From the administrative console select the Organizations& Users tab, then click on Services. Scroll down to Google Groups and turn it on."

Wednesday, October 24, 2018

install EOS utility without CD

I seem to have misplaced the EOS Utility CD for the Canon 1100D camera I used in the lab. Tried this method to install for a student -

https://www.youtube.com/watch?v=VTLISryqbSc

Creating a registry key under
HKEY_LOCAL_MACHINE ->  Software ->  WOW6432Node
(Right-click, New -> Key)
Canon
(Right-click, New -> Key)
EOS Utility

This did not work for the latest version of EOS Utility, but did work for an earlier version. 

Thursday, October 04, 2018

flashing a custom ROM on a Samsung Galaxy Grand Quattro - i8552

A gave me a Samsung Galaxy Grand Quattro - model i8552, also known by many other names like Win Duos and so on -
https://www.gsmarena.com/samsung_galaxy_win_i8550-5392.php

This was for use at our exhibit of Universe2go.

The stock Samsung had Android 4.1, and Universe2go needed at least 4.2. So, I started on the journey to flash a custom ROM on the device. It took me 3-5 hours over 3-5 days because of conflicting instructions and things not going as planned. The things which delayed me turned out to be

  1. loose USB cable. A good fit for the USB cable, and a good cable, is a must before doing any flashing.
  2. lack of clear instructions on how exactly the buttons need to be pressed to go into download mode on this particular model, and terribly written instructions in general,
  3. and many broken links and links to paid file hosts. Downloaded files from androidfilehost.com instead, using the filenames given. 
Finally after I finished the process, found that universe2go is laggy on this device, so I won't be using this device after all. Documenting the method which worked - took less than fifteen minutes excluding time taken to download the ROM images - 

1. Downloaded TWRP recovery image,    

2. Downloaded the custom ROM, saved on the phone's SD card by moved it to the phone SD card using Airdroid. Can be either internal memory or extra SD card, doesn't matter. Could have downloaded on the phone directly also. (I tried these ROMs below - 
https://forum.xda-developers.com/grand-quattro/development/rom-trans-k-rom-transwin-v4-rom-t2912032
which is actually just a skin on the existing 4.1 kernel and wrongly reports as 4.4 - so universe2go does not run ...
and also lineageOS 13,
https://forum.xda-developers.com/grand-quattro/orig-development/rom-lineage-os-13-grand-quattro-t3541777
which crashes a lot. This one ran universe2go, but the screen refreshes were at 5 fps or so, not usable. Also tried this one,
https://forum.xda-developers.com/grand-quattro/orig-development/rom-carbon-rom-gt-i8552-delos3geur-t3628076
which says that the sensors work. But installing GApps causes crashes. GApps is supposed to be the version of the OS and ARM pico version - ie ARM 4.4 pico for this carbon, etc from opengapps.org . Also, it does not shut down cleanly. And universe2go crashes.)


3. Installed heimdall with
sudo apt-get install heimdall-flash heimdall-flash-frontend
On Windows, Odin is supposed to do the job, but was stumped by not seeing the device. Probably some driver install issue. 

4. Download the PIT file from the phone using heimdall, following the instructions at

Utilities tab, Download PIT, choose save as destination, Download. 

5. Power down the phone, wait 10-15 seconds to allow it to power down completely. Then boot into Download mode by continuously pressing Home + Vol Down + Power buttons, and when the phone vibrates, after it finishes vibrating, releasing the Power button, keeping the other two buttons pressed until the warning screen appears. (This part in bold is the technique which stumped me.) As the warning screen says, press Vol Up to go into Download mode. 

6.  Following the instructions in this link,
flash the TWRP img file downloaded in step 1 - 
Flash tab - choose the PIT file downloaded in the previous step - click Add - choose Recovery in the dropdown menu, choose No Reboot. Then start. 

7. A blue progress bar on the phone shows when the flashing is done - should take only 10 seconds or so once it starts. Then remove the battery, put it back. This would have installed the TWRP - Team Win Recovery Project - custom recovery software which would allow the flashing of custom (unsigned) ROMs. 

8. Now boot into Recovery by continuously pressing Home + Vol Up + Power buttons, and when the phone vibrates, after it finishes vibrating, releasing the Power button, keeping the other two buttons pressed until the TWRP screen appears. TWRP is easy to use, and has a touch interface.

9. Choose to Wipe (factory reset - this is generally safer, though not always necessary) and then Install - choosing the ROM downloaded in step 2. After the installer says it is done, remove the battery, put it back, and reboot. Done.

Will try to restore the stock ROM -
https://forum.xda-developers.com/showthread.php?t=2433941
and then maybe unroot etc,
https://forum.xda-developers.com/showthread.php?t=2494471

Edit: Finally restored stock ROM from

TransK ROM had play store and other apps crashes, maybe since it reports it is Android 4.4 in spite of being 4.1.

The actual sequence of steps I followed, with many missteps, was something like this -

(Samsung Galaxy Quattro 18552

1. Root with Framaroot

2. Update downloaded from

3. ADB all in one from

4. TWRP install via 

5. TWRP via recovery flashable link at

6. Installed TWRP Manager, then copied over recovery.img using airdroid, then using TWRP Manager, "recovered". 

7. Manager did not install TWRP, so using Flashify,
But Flashify not responding.

8. Installed CWM instead

9. Downloaded files from androidhost via google instead of the links in above.

10. (I was continuing to press the vol + power + home buttons after the vibrate also, hence phone was booting into normal mode)

11. Finally entered download mode with adb

12. Loose contact USB, problems. 

13. Driver issues on Windows with fastboot, so Linux.

14. just sudo apt-get install android-tools-adb android-tools-fastboot

15. lsusb shows Samsung

16.  adb devices showed
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
71ba1f19    device

17. Then did via
adb method.
But again, waiting for device at fastboot flash

18. So, trying 

lsusb gave
Bus 002 Device 008: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)

But still no fastboot.

19, Tried adding as per

adb works, fastboot waiting for device.

20. Try with android sdk install. Downloaded tools.

21. Trying this, 

lsusb in download mode gave different id
Bus 002 Device 011: ID 04e8:685d Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (Download mode)
Bus 002 Device 003: ID 046

Apparently, Samsung devices need heimdall and do not work with the fastboot tool.  

method worked to get into download mode, and get pit file.

23. heimdall

24. To boot into recovery, vol up + pow + home, leave pow when vibrates

25. from Twrp, selected install, and chose the trans-k rom. 

26/. Wipe cache/dalvik, as per

27. pull out battery, put it back, boot as normal. )

Edit: Some more trial and error in getting back to Stock ROM. See main section above for
assert error

downloaded stock from
But did not work with TWRP. Will probably need to use an external removable sdcard since I formatted the system partition and the device does not boot.