Root and installing Recovery ROM on LG D855 (G3) for custom ROM

If you have a updated LG G3 e.g. LP or MM, you may find getting root access is quite hard. I have found a way to root it and install custom ROM.

Disclaimer: I will NOT be responsible for any damage on your D855 G3 on trying method in this article. Try on your own risk.

Before you go, you have following ready:

1. LG Flash Tool
2. LG D855 firmware (v10b 4.4.2) 
3. Strump tool  <- br="" d855="" firmware="" for="" initial="" release="" still="" work="">
4. LG G3 855 modem (21C) 
5. TWRP recovery rom 
6. a PC with adb tool installed (e.g. Ubnutu 15.10 or Windows 10 with Android SDK installed) 

Step:

1. Boot D855 to download mode (power off -> press vol up and connect USB to PC)
2. Run LG Flash Tool to flash 4.4.2 firmware
3. Install Strump and run Strump tool (reboot D855 afterwards)
4. enable USB debug mode
5. install SuperSU from Google Play 
6. copy TWRP image to SD Card of D855 e.g. adb push /storage/ external_SD/
7. enter D855 shell i.e. "adb shell"
8. change to super user i.e. "su"
9. dd if= of=/dev/block/platform/msm_sdcc.1/by-name/recovery
10. boot to recovery mode(in TWRP now)
11. Flash 21C modem by TWRP
12. reboot to TWRP
13. you can flash LP or MM custom ROM now 

 credit : 
hyelton  xda developer (flash stock rom steps)
jcase xda developer  (strump tool)
step_han (provide flashable modems) 

LG (flash tool)
TeamWin (recovery rom developer)


 This is the way what I tried to flash custom ROM on D855 with LP stock ROM installed.
 
 

Minor difference in vCenter Single Sign On (SSO) server 5.5 deployment

Starting from vCenter 5.1, there is a new component called vCenter Single Sign-On server to simply the authentication across multiple vCenter servers. There is 3 deployment modes as following in vCenter 5.5 :

The first one is very simple. This is the starting point for your to deploy 1st vCenter SSO server.
The 2nd and 3rd one are easily confused as both of them need you to specified "Partner Host name" and password of administrator@vsphere.local.

For "High Availability", this deployment mode requires same Site.

 "MultiSite" mode requires different site name.

The remaining installation steps are the same. The difference is somehow interesting and help you to differentiate "High Availability" and "MultiSite" mode.

Also, in the installation summary, "Multisite" requires configure a new Lookup service while High Available mode does not need that.  This imply that, in "MultiSite" mode, vCenters in each site are registered to different SSO.

Any comment are welcome.

Managing KVM Virtual Machine using virsh

libvirt is a powerful tool kit for KVM and Xen virtual machine management. This blog does not intend to explain libvirt deeply but we provide some useful commands for KVM  daily operation.

Before using libvirt tool, you need to install in on your KVM hypervisor. OS is Ubuntu 14.04 in this example.

                  apt-get install libvirt-bin



 There are some commonly used options:

 create a virtual machine(e.g. server1) using a xml configuration file:

                   virsh define  server1.xml

find out what virtual machine created (you will use the names here for other operation):

                   virsh list --all 

boot up a virtual machine:

                   virsh start server1

shutdown a virtual machine:

                   virsh shutdown server1

Cold power down a virtual machine:

                   virsh destroy server1

remove a virtual machine:

                   virsh undefine server1

Instead of managing the virtual machine locally,you can also use virsh command to manage virtual remotely. Example:

                   virsh -c qemu+ssh://root@/system list --all 

This will show you all virtual machines created on remote KVM server. Notes: you may be prompted for root password if you have not been authorized on the remote KVM server using ssh-copy-id

                   ssh-copy-id root@ 


Comment is always welcome :)

                 

Upgrading Ubuntu Server 12.04 LTS to 14.04

Ubuntu 14.04 LTS (long term support) is released on 17 Apr 2014. For production users, it is the time to consider upgrading 12.04 to 14.04.

Ubuntu LTS version is released every 2 years. People would like to deploy LTS version in production since the support period is five years which is much longer than other like 13.04 or 13.10. Only 6 month. !

Let 's begin the upgrade process.

Warning: You are advised to backup the existing server before upgrade !

We demonstrate the process in ssh session.

Ensure your Ubuntu server can access internet.

Ensure your current version. You can find it easily by logging in.

 

Remember to add "-d". Otherwise, you will get a message "No new release found"

Note: For LTS version, upgrade message come out when there is "point version" release e.g. 14.04.1 by default. "-d" means upgrade to development release including 14.04. If you upgrade Ubuntu from 13.04 or 13.10, no "-d" is required.

 

Type "Y" and press "Enter"

 

press "Enter" 

 

Updating the repo.

 

Type "Y" to begin installation.

leave default unless you need to disable password authentication for account root.

 

 

Installation in process...

 

Select "Yes" unless you want to be prompted for tons of questions.

 

If modified configuration file found, you will be asked to keep it or not.

 

Example, our Ubuntu 12.04 is a KVM server with qemu.conf modified. 

 

Type "Y" to remove replaced deb packages

 

Type "Y" to reboot the server.

After reboot and login again, you will find the new version is up and running.

If your Ubuntu server is installed with other applications, it is the time for you to confirm it if they are functioning properly in version 14.04.

Comment is always welcome :)

 

 

 

 

 

 

 

XenDesktop Controller in-place Upgrade from version 5.6 to 7.5

When a new version of a product released, people always ask, "Can I upgrade to this new version ?"

For XenDesktop 5.6 users, answer is yes as long as your license Subscription Advantage expiration date cover the product "burn-in" date. You can find this information here.

Product upgrade does not imply vertical upgrade is possible.  Fortunately, XenDesktop 5.6 can be upgraded to 7.5 directly (technically possible). 

Warning: in-place upgrade is a one-way operation and risky, back up database and XenDesktop controllers first.

This article will demonstrate how to upgrade a XenDesktop delivery controller ("the core component"). Other components like Provisioning Server is not the topic here.

First, autorun the XenDesktop 7.5 installation media.

 

Click "Upgrade" 

 Agree the license agreement.

 

Read the words carefully.

Remember: you have been warned.

Click "Next"

 

Click "Upgrade"

 

You may need to boot machine to continue.

log on again after reboot and wait....

Click "Finish"

After Delivery Controller upgrade, you need to start upgrade the Site.

Notes: try auto upgrade unless SQL server is out of your control.

 

Click "Upgrade"

Wait...

Click "Finish"

 If there are multiple delivery controllers, also upgrade them. Procedures are the same except upgrade the site since it is upgraded already.

 

Up to now, the other upgraded controller cannot function properly until registration is completed. Click "Perform registration" 

 

Click "OK"

After upgrade all controllers, it is the time to upgrade the Virtual Desktop Agent(VDA)  5.6 to 7.5 

After VDA is upgraded, you can upgrade Delivery Group.

 

Click "Upgrade"

The option of "Upgrade Delivery Group" when you select a Delivery Group in Citrix Studio (formerly known as Desktop Studio).

If your XenDesktop environment is complex e.g. Provisioning Servers are deployed, please read the component upgrade logic flow at Citrix edocs carefully.

Comment is always welcome. Cheers :)