[4 April 2014]I haven't had time to play with my device or update fully the info in this post
Jhong2 has an updated post on how to get ubuntu working on the Asus T100
http://forum.xda-developers.com/showpost.php?p=51291244&postcount=181
http://www.jfwhome.com/2014/03/07/perfect-ubuntu-or-other-linux-on-the-asus-transformer-book-t100/
(do search for the specific topic headers to jump to them)
Post 1: Global Info
UEFI:
Bootloader auto-detection path:
Secure Boot
Partition Table for Live USB sticks:
How to boot from USB stick
Info for various operating systems:
Hardware info:/cpu/cpuinfo:
Post 2: <backup/ archived infomation>
Post 3: Files
grub2 2.00-13ubuntu3 (13.04 raring sources) compiled for grub-efi-ia32 (x86) - bootia32
---------------------------------------------------------------------------------------
Global information
for BIOS 214 (2013.09.25), version loaded on retail T100 units
UEFI:
Bootloader auto-detection path:
(bootloader is only 32-bit compatible)
/efi/BOOT/bootia32.efi
WILL NOT pick up the x64 location /efi/BOOT/bootx64.efi
Secure Boot
You should disable Secure Boot in UEFI/Setup-Utility-Menu-> Security tab-> Secure Boot Menu -> Disable
Partition Table for Live USB sticks:
GPT or MBR works
Use Rufus (works for Windows/Unix ISOs) or Windows 7 USB Download Tool (works for Windows 7 / Windows 8)
How to boot from USB stick
NOTE:
If you don't see the USB drive on the boot list or the UEFI/Setup-utility, this means you have a badly prepped USB live drive, or the boot-list/UEFI/Setup-utility was loaded before the USB drive was read.
If you are on the boot list, boot into UEFI/Setup-utility. Then, go to the last tab, save changes and restart while holding F2 (to force the next reboot to go back into UEFI/Setup-utility). If you still don't see the USB drive after doing this multiple times, then you have a badly prepped USB drive.
I find using Rufus (GPT for UEFI + FAT + 64 kb+ bootable disk using ISO Image) to consistently get a working bootable USB drive
Option 1a) Boot to UEFI USB drive from Windows (works only if your USB is correctly prepped)
Boot into Windows
Swipe from right, click on settings.
Click on Power. Press and hold the shift key, and then click on Restart
A Blue menu should show up. Click on Use a device->click on the device name (might not show up if USB isn't prepped properly)
Device should reboot into the USB
Option 1b) Boot to UEFI/Setup-Utility-menu from Windows (easiest, and almost no way to screw it up)
Boot into Windows
Swipe from right, click on settings.
Click on Power. Press and hold the shift key, and then click on Restart
A Blue menu should show up. Click on Troubleshoot-> Advanced Options-> UEFI Firmware Settings
Inside UEFI/Setup-Utility-menu, go to the last tab, and select the USB Drive
NOTE:
For options 2a and 2b, if you see the ASUS logo and circle loading icon, you either:
Pressed button (ESCAPE/F2) too late. Solution: Reboot and try again
Have Fast startup enabled, and did the steps with the device in shutdown mode. Windows will cache the kernel/other stuff, and you might not be able to get to UEFI. Solution: Reboot from Windows and try again(reboot does not trigger caching). Or disable Fast Startup
Option 2a) Boot to UEFI/Setup-Utility-menu
Inside Windows, restart system. Press and hold the F2 key
You should get into the Aptio Setup Utility screen
Inside UEFI/Setup-Utility-menu, go to the last tab, and select the USB Drive
Option 2b) Boot Menu
Inside Windows, restart system. When screen goes blank, press and hold the ESCAPE key (if you press it too early, Windows might interpret you as cancelling the restart process)
You should get a list of bootable devices
If you see the ASUS logo, you've pressed the ESCAPE key too late. Restart and retry
Info for various operating systems:
You should backup the recovery partition to a separate USB key. Alternatively, you can do it with this ASUS utility Backtracker that HatesForums pointed me to
Windows:
Windows 8.1
x86: (Status: Works but missing drivers)
Used Windows 7 USB Download Tool or Rufus to create bootable USB. Using en_windows_8_1_x86_dvd_2707392 from MSDN (x86 8.1 Regular & Pro ISO), able to install W8.1 x86 and boot to it (missing a few drivers, eg touch screen doesn't work, no sound). Windows is automatically activated without need for key. First boot had 25.7GB free out of 33.6GB.
x64: (Status: Not yet working)
Used Windows 7 USB Download Tool or Rufus to create bootable USB. ISO does not contain bootia32.efi. Copied that file from the x86 ISO to USB, able to boot, but the installer complains that the processor isn't 64-bit compatible
Windows 7
x86: (Status: unknown)
ISO does not contain efi
x64: (Status: unknown
ISO only contains x64 efi
Unix:
Ubuntu:
You need an EFI-compatible distro. For ubuntu, x64 EFI is enabled since 12.04-2. However, we'll need to include x86 EFI because our bootloader only reads x86 EFIs
13.04 x64 desktop- (Status: boots to GUI using fbdev)
Used Rufus(GPT for UEFI + FAT + 64 kb+ raring x64 as bootable disk using ISO Image) to create bootable USB. Copied over the bootia32 to /efi/boot/
there is a bug in VESA where it queries for a BIOS-only command and crashes. Forcing xserver to use fbdev fixes this problem
13.10 x64 desktop- (Status: boots to GUI using fbdev
Same problems as 13.04 x64 plus one addition efifb problem
see post for more details - touchscreen works, but no wifi
Android:
android-ia - (Status: No x86 UEFI bootloader)
Generic UEFI Installer android-4.2.2_r1-ia3 does not come with x86 UEFI bootloader. it does not use grub, so can't just use ubuntu's x86 grub2 efi. Need to compile it from source
android-x86 - (Status: Bootable but slow)
Uses grub, can piggy-back on the ubuntu x64 13.10 bootia.efi grub. Some workarounds needed, see this post
external/efitools/Android.mk
# TODO: support ia32 prebuilt
ifeq ($(TARGET_KERNEL_ARCH),x86_64)
arch_name := x86_64
Click to expand...
Click to collapse
/cpu/cpuinfo:
taken from a x64 13.04 live USB
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 55
model name : Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
stepping : 3
microcode : 0x312
cpu MHz : 1333.387
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 2666.77
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 55
model name : Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
stepping : 3
microcode : 0x312
cpu MHz : 1333.387
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 4
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 2666.77
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 55
model name : Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
stepping : 3
microcode : 0x312
cpu MHz : 1333.387
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 4
apicid : 4
initial apicid : 4
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 2666.77
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 55
model name : Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
stepping : 3
microcode : 0x312
cpu MHz : 1333.387
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
apicid : 6
initial apicid : 6
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 2666.77
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
Hardware info:
The microUSB slot is USB-HOST-capable (i.e. with a USB OTG cable or Y cable, you can connect a USB flash drive to the microUSB slot
Amazon.de and Asus.de posted a T100 version with 500GB drive on the keyboard base. No pictures yet
Internal eMMC, 108MB/s 44MB/s read/write on sequential. CrystalDiskMark here
External microSD(HC/XC) reader is NOT UHS-1 compatible. Someone over at liliputing comments posted his atto benchmark
64GB Samsung microSDXC card came in the mail today, I did some ATTO disk tests using the T100's built-in microSD reader and a USB 3.0 reader from Transcend.
Unfortunately, it looks like the built-in reader is connected via USB 2.0. It maxed out at 23.8 MB/s read and 17.2 MB/s write, while the USB 3.0 reader maxed out at 71.3 MB/s read and 21.3 MB/s write. The card is rated at 70 MB/s read and 20 MB/s write.
<backup/ archived infomation>
Files:
grub2 2.00-13ubuntu3 (13.04 raring sources) compiled for grub-efi-ia32 (x86) - bootia32
LINK | MIRROR | Instructions on compiling from source
<reserved 3>
paperWastage said:
ISO does not contain bootia32.efi. Copied that file from the x86 ISO, able to boot, but the installer complains that the processor isn't 64-bit compatible
Android:
Click to expand...
Click to collapse
odd: http://ark.intel.com/products/76759/
shouldnt be erroring about 64 bit, unless the 8.1 installer is checking the CPU ID, isn't recognising it (no idea why) and then presuming a lack of 64 bit support.
SixSixSevenSeven said:
odd: http://ark.intel.com/products/76759/
shouldnt be erroring about 64 bit, unless the 8.1 installer is checking the CPU ID, isn't recognising it (no idea why) and then presuming a lack of 64 bit support.
Click to expand...
Click to collapse
Perhaps the 32bit bootloader sends that the device is only booting in 32bit.
Seeing that I can boot to Ubuntu x64, the chip should be 64bit like how the Intel ark site says. I'll check the cpuinfo in Ubuntu to see what extensions it supports
Will also try to download WinPE and get the efi bootloader from there instead. Windows 7 x64 has efi x64 bootloader, but x86 doesn't have any efi bootloader
Compiling grub2-efi-ia32 (x86)
NOTE:
The instructions below are for raring 12.04.
The same instructions should work for other versions/sources/distros of grub2 as well.
The resulting binary should work with any *nix distros that use grub2
The resulting bootia32.efi should be placed on your USB drive at /EFI/BOOT/bootia32.efi
The grub-mkimage instruction basically packages the grub-efi AND the *.mod you specified into that bootia32.efi. You may need to tweak the list of *.mod that you include. You don't need to copy the *.mod onto the USB drive
-p /boot/grub tells grub-efi to look for the grub.cfg at /boot/grub/grub.conf (location that ubuntu uses). Other distros may use a different location.
Either recompile grub2-efi-ia32 with the right "-p" flag
Or copy your distro's grub.conf to /boot/grub/grub.cfg
Download grub2 sources for raring
https://launchpad.net/ubuntu/+source/grub2/2.00-13ubuntu3
apt-get install gcc bison flex
./configure --with-platform=efi --target=i386
make
#make GRUB EFI binary and mods
cd grub-core
../grub-mkimage -d . -o bootia32.efi -O i386-efi -p /boot/grub ntfs hfs appleldr boot cat efi_gop efi_uga elf fat hfsplus iso9660 linux keylayouts memdisk minicmd part_apple ext2 extcmd xfs xnu part_bsd part_gpt search search_fs_file chain btrfs loadbios loadenv lvm minix minix2 reiserfs memrw mmap msdospart scsi loopback
cp bootia32.efi to <USB DRIVE>/EFI/BOOT/
# might be missing some modules... but if i tried to compile all *.mod, I get an invalid stack frame during grub boot
Click to expand...
Click to collapse
Files:
grub2 2.00-13ubuntu3 (13.04 raring sources) compiled for grub-efi-ia32 (x86) - bootia32
LINK | MIRROR | Instructions on compiling from source
tried using that bootia32.efi to load Ubuntu 13.10 x64 ... (13.10 & 13.04 seem to use the same grub2-2.00 sources)
the grub menu shows up, but after selecting "Try Ubuntu", it flashes, menu continues showing up, nothing happens
then my Windows 8.1 OS got corrupted or something.... either boots to Windows message "Windows unable to start up properly", or it boots to login screen, then the screen goes haywire and popup boxes saying "illegal exception" or something
going to reinstall W8.1 x86 cleanly from a MSDN ISO/USB flash drive
got the logs from the semi-successful 13.04 x64 boot... will look through them and post them soon
ubuntu x64 13.04, debuging x-server issues
[ 36.591] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 36.597] (II) Module fbdev: vendor="X.Org Foundation"
[ 36.597] compiled for 1.12.99.902, module version = 0.4.3
[ 36.597] Module class: X.Org Video Driver
[ 36.597] ABI class: X.Org Video Driver, version 13.0
[ 36.597] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
Haswell Server (GT2+), Haswell SDV Desktop (GT1),
Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
Haswell ULT Server (GT1), Haswell ULT Server (GT2),
Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
Haswell CRW Server (GT2), Haswell CRW Server (GT2+),
ValleyView PO board
...
[ 36.762] (II) VESA(0): initializing int10
[ 36.763] (EE) VESA(0): V_BIOS address 0x0 out of rangefrom
http://www.redhat.com/archives/rhl-devel-list/2009-December/msg00372.html
looks like 13.04 is able to recognize and load the necessary drivers, but crashes because our UEFI-only computer doesn't have a BIOS portion... or maybe 13.04 is using older stuff
EDIT: or does that error even matter? trying to force x to configure itself
EDIT2: it matters because VESA is configured to be the default/fallback driver. With the V_BIOS issue, it won't work. Tried to force it to use fbdev driver, but no luck (it loads, but nothing shows up)
I deleted the vesa_drv.so from /usr/lib/xorg/modules/drivers/ , forced it to start using fbdev... works, very slowly of course
will try the intel driver later
(it's definitely the vesa BIOS bug that's stopping it from working on 13.04... will debug 13.10 later)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
<instructions below should be complete
got ubuntu 13.10 to boot to command prompt (with bootia32.efi and grub.cfg fixes below)
Rufus (GPT for UEFI + FAT + 64 kb+ 13.10 desktop x64 as bootable disk using ISO Image)
Note:
Good behavior:
After you select "Try Ubuntu" in grub, screen goes to blank, (?might appear as well) usb light disappears... wait < 30s, the screen should then show the logs and then cmd line)Bad Behavior:
After you select "Try Ubuntu" in grub, screen goes to blank, then the grub menu reappears (but nothing happens when you press arrow keys). (?might appear as well) usb light stays lighted. if you wait >5 minutes, nothing happens. just force reboot machine (hold power button), and reboot into windows, then UEFI and try again
/boot/grub/grub.cfg - replace with the text below
Code:
if loadfont /boot/grub/font.pf2 ; then
insmod efi_gop
insmod efi_uga
insmod gfxterm
terminal_output gfxterm
fi
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
menuentry "Try Ubuntu without installing" {
set gfxpayload=keep
linux /casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper text noacpi nomodeset --
initrd /casper/initrd.lz
}
menuentry "Install Ubuntu" {
set gfxpayload=keep
linux /casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --
initrd /casper/initrd.lz
}
menuentry "OEM install (for manufacturers)" {
set gfxpayload=keep
linux /casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash oem-config/enable=true --
initrd /casper/initrd.lz
}
menuentry "Check disc for defects" {
set gfxpayload=keep
linux /casper/vmlinuz.efi boot=casper integrity-check quiet splash --
initrd /casper/initrd.lz
}
(changes in grub is to disable efifb which causes screen flickering/corruption - video=vesa: off doesn't work, probably because vesa IS the fallback driver)
then boot. After you get to command line, remove the vesa_drv.so module from /usr/lib/xorg/modules/drivers/, type startx
touchscreen works on x64 13.10. still haven't had time to make x86 ISO work with bootia32.efi GRUB
For Android-x86 without EFI support, I wonder if this method courtesy of Tyler Swindell on Youtube would work. This is what he used to get Android-x86 booting on the Surface.
Alright guys, this is the Surface Pro running Android-x86. It was something we all saw coming. Past 2
nights, I have been trying hard to get Android-x86 to run on my Surface Pro since I saw how amazing it
ran on my desktop PC. If it would just boot, I could see just how great Android is on the Surface Pro. So
I got it to boot, and it was just as great as I expected it to be.
So why didn't it boot? I had Secure Boot off. Ubuntu boots, Windows 7 boots. Well what do all these
operating systems have in common? Their installers all include both BIOS and EFI boot loaders. What is
interesting about the Surface Pro is the UEFI chip was designed without legacy BIOS support. There is
no way to boot a BIOS-based boot loader.
I thought about it and how Ubuntu boots. I checked the files and I saw a EFI-based Grub boot loader.
All I had to do was drop in Android's files into an Android directory and add the boot entries. This
worked and Android booted thanks to the EFI-based Grub boot loader.
Everything works except no connectivity, no Wi-Fi or Bluetooth. Also the buttons could have better
functions such as the Windows button or the power button which just brings up a power menu. Overall
it's a great start, it's booting, and the drivers are there for mostly everything. It's fantastic.
This tutorial can be drastically simplified and improved. Keep in mind it was just to get it to work.
1. Download Android-x86 ISO and Ubuntu 12.10 x64 ISO.
2. Format a USB flash drive.
3. Using LiLil USB Creator, copy Ubuntu ISO to flash drive.
4. Create Android directory in flash drive. Extract Android ISO, copy initrd.img, kernel, ramdisk.img,
system.sfs to the Android directory.
5. Modify boot/grub/grub.cfg to add these entries:
submenu "Android" {
menuentry "Android" --class android --class linux --class os {
linux /android/kernel root=/dev/ram0 androidboot.hardware=android_x86 quiet video=1920x1080
dpi=145 i915downclock=1 i915.powersave=1 usbcore.autosuspend=2 SRC=/android/
initrd /android/initrd.img
}
menuentry "Android text output" --class android --class linux --class os {
linux /android/kernel root=/dev/ram0 androidboot.hardware=android_x86 video=1920x1080 dpi=145
i915downclock=1 i915.powersave=1 usbcore.autosuspend=2 SRC=/android/
initrd /android/initrd.img
}
menuentry "Android debug mode" --class android --class linux --class os {
linux /android/kernel root=/dev/ram0 androidboot.hardware=android_x86 video=1920x1080 dpi=145
i915downclock=1 i915.powersave=1 usbcore.autosuspend=2 SRC=/android/ DEBUG=1
initrd /android/initrd.img
}
}
6. Turn off Secure Boot and boot Android. Enjoy.
Click to expand...
Click to collapse
Sent from my DROID BIONIC using Tapatalk
spunker88 said:
For Android-x86 without EFI support, I wonder if this method courtesy of Tyler Swindell on Youtube would work. This is what he used to get Android-x86 booting on the Surface.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
that might work, forcing android-x86 to boot via grub.. thanks
been using android-ia, which doesn't use grub... uses another efitool, need to play with both android-x86 and android-ia later tonight
paperWastage said:
that might work, forcing android-x86 to boot via grub.. thanks
been using android-ia, which doesn't use grub... uses another efitool, need to play with both android-x86 and android-ia later tonight
Click to expand...
Click to collapse
Picking up on our conversation from SlickDeals.. I actually ended up buying one of these things and I was able to get an external hard drive recognized just by plugged into my usb OTG cable -- in windows. I even tried a USB mouse which worked perfectly.
Deltido said:
Picking up on our conversation from SlickDeals.. I actually ended up buying one of these things and I was able to get an external hard drive recognized just by plugged into my usb OTG cable -- in windows. I even tried a USB mouse which worked perfectly.
Click to expand...
Click to collapse
yeah, my usb otg cable works now in windows (detects flash drive). no idea why it didn;t work before (maybe I unpluged it too early while it was detecting/installing the usb driver?)
got android to boot up, but uglily
need 2 flash drives, and a USB-OTG cable(to be able to connect using the microUSB port)... a USB-hub should work too
(basically, you're piggying back off the ubuntu grub2 bootloader, to load the android kernel and other stuff)
used my (existing & currently working) ubuntu 13.10 x64 bootable USB (made via Rufus, GPT partition with bootia32.efi fix)
copied the contents of android-x86-4.3-20130725.iso into the USB:/android/
modified contents of grub.cfg as per the post by spunker88 with some changes to the resolution
second flash drive had dd if=android-x86-4.3-20130725.iso of=/dev/sdb1
without this second flash drive, the android boot sequence stops at "Detecting Android-x86" and "VFS: could not find a valid V7 on sda1". probably something to do with android/kernel not liking the first drive having FAT instead of ext2/3/4
grub.cfg - add to the end, and select this during grub
Code:
submenu "Android" {
menuentry "Android" --class android --class linux --class os {
linux /android/kernel root=/dev/ram0 androidboot.hardware=x86 video=1366x768 DEBUG=1 SRC=/android/
initrd /android/initrd.img
}
}
boot into USB, then grub, then select android.
android crashes to command line. forcing it to start (type exit twice), leads to the default android start screen, and eventually this
it is SUPER LAGGY. not usable
paperWastage said:
got android to boot up, but uglily
need 2 flash drives, and a USB-OTG cable(to be able to connect using the microUSB port)... a USB-hub should work too
(basically, you're piggying back off the ubuntu grub2 bootloader, to load the android kernel and other stuff)
used my (existing & currently working) ubuntu 13.10 x64 bootable USB (made via Rufus, GPT partition with bootia32.efi fix)
copied the contents of android-x86-4.3-20130725.iso into the USB:/android/
modified contents of grub.cfg as per the post by spunker88 with some changes to the resolution
second flash drive had dd if=android-x86-4.3-20130725.iso of=/dev/sdb1
without this second flash drive, the android boot sequence stops at "Detecting Android-x86" and "VFS: could not find a valid V7 on sda1". probably something to do with android/kernel not liking the first drive having FAT instead of ext2/3/4
grub.cfg - add to the end, and select this during grub
Code:
submenu "Android" {
menuentry "Android" --class android --class linux --class os {
linux /android/kernel root=/dev/ram0 androidboot.hardware=x86 video=1366x768 DEBUG=1 SRC=/android/
initrd /android/initrd.img
}
}
boot into USB, then grub, then select android.
android crashes to command line. forcing it to start (type exit twice), leads to the default android start screen, and eventually this
it is SUPER LAGGY. not usable
Click to expand...
Click to collapse
Progress!!
Although its unusable, it's nice to see android on this device. So what do you think needs to be done to get android usable on this?
costcutter said:
Progress!!
Although its unusable, it's nice to see android on this device. So what do you think needs to be done to get android usable on this?
Click to expand...
Click to collapse
for both ubuntu/android, first steps (since it's booting) is to get the graphics driver working. right now, ubuntu is using fbdev and android is (i think) using efifb... both are running at 800x600 and laggy....
either I fix the VESA bug, or find the correct intel driver for the new Bay Trail IGP and use it
then, install ubuntu/android properly on the device, and then debug the rest (instead of through a live USB where changes would not persist from every reboot)
I'm trying with Fedora 20 alpha, but not much luck so far.
Got the grub2-efi to work with your tutorial (and some digging), but once I start installing Fedora, it seems to freeze.
Gonna try ubuntu over the weekend.
probably the vesa bug as well (if you are trying to install via gui)
attempting to fully install ubuntu on system and boot from it.... the bootia32.efi / bootx64.efi / grubx64.efi is making a mess here...
managed to get Windows Bootloader AND ubuntu grub listed as boot options... grub has problems though, dumps me into grub shell
EDIT: Think it;s easiest for me to try installing EFI Shell, and tinker from there
http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Efi-shell
EDIT2: For Windows 8 64-bit, the error is "This 64-bit application couldn't load because your PC doesn't have a 64-bit processor"
Looks like we need to enable Virtualization in the UEFI/BIOS... but there isn't such an option (the cpu Z3740 does support VT-x)
Need Assistance in Modifying a BenQ T3 (Performance wise, Reducing Apps & Flashing)
Hello,
Before I begin explaining my predicament I would like to state that this is essentially my first post on this website so I apologize in advance if I am essentially breaching any forum policies or rules and regulations for that matter. The moderators can amend this post as they may see fit since I am not too familiar with how things work here. That said let me get straight into what I am hoping to achieve.
I have a Benq T3 Android phone that I would like to customize, upgrade, add new features, remove flagship (reads default phone) applications, since they're essentially hogging space on the phone, and I hardly use them & finally upgrade the said former to a new Android (custom) or standard OS if it's possible based on the details I will be posting below. With all this I would like a custom or simple boot up screen as well without the Benq logo flashing all over the screen every time I power on or restart the phone.
The purpose of this exercise is:
1) I need to push this phone to the maximum limits of its hardware capability, overclocking, optimizing RAM, increasing swap space etc (currently it's not fast enough for me)
2) Remove all unnecessary applications completely (Flipboard, Benq applications that are part of the phone, WPS office), all these are by default inside the phone and even though I have tried uninstalling them they only uninstall the updates and the application still sits in hogging the phone space, which is quite frustrating.
3) To see if any relatively latest Android version could be used with the acceleration (hypothetically) done in the above point (1).
4) Flashing a new ROM (if necessary) something that may actually make this phone a better version of itself.
What will I use this phone for (Once it is done)
1) Twitter (Main function)
2) Texting (Main function)
3) Whatsapp (Main function)
4) Newspaper Applications~Text Reading Mainly, some sort of Flash / HTML5 as well (Main Function)
5) PDF reading (Main Function)
6) Discussion Board Browsing (Main function)
7) Emails (Secondary Function) ~ Using an Email client (Also need recommendations of light Apps that might work on the new made over system)
8) Youtube (Secondary Function)
9) Soundcloud (Secondary Function)
10) Word Processing including Spreadsheet + Ppt stuff occasionally (Secondary Function)
VERY IMPORTANT ~ EVERYTHING OTHER THAN WHAT I HAVE WRITTEN NEEDS TO GO
VERY IMPORTANT ~ THIS PHONE IS ROOTED VIA KINGO ROOT ALREADY
What I have currently
1) A computer running Windows 7 Home Premium x64 bit, i5 Gen 2 with 6 GB DDR2 RAM - Dell Inspiron N5110
2) An internet connection of around 20-30 Mbps
3) No programming ability whatsoever (A complete Newbie while being a downright noob in such stuff)
4) 3 hours a day (at best) to understand, implement and get this over with ASAP
5) English as my first language
6) Nothing else I am afraid
Please note that my generic aim to customize this BenQ phone is in pursuits of attaining maximum performance that the phone can generate for me while running the basic apps that I have mentioned above.
----------------------------------------------------------------------------------------------------------
That said I will now proceed to mention all my phone's tidbits based on the information that I gathered via Aida64 application
----------------------------------------------------------------------------------------------------------
Code:
----------------------------------------------------------------------------------
System
----------------------------------------------------------------------------------
Manufacturer - BenQ
Model - BenQ T3
Board - MSM8926
Device - T3_17A
Hardware - QCom
Platform - msm8226
Product - T3_08
Installed RAM - 1 GB
Total Memory - 866 MB
Available Memory - 256 MB
Internal Storage (Total Space) - 2051 MB
Internal Storage (Free Space) - 732 MB
----------------------------------------------------------------------------------
android.hardware.bluetooth
android.hardware.bluetooth_le
android.hardware.camera
android.hardware.camera.any
android.hardware.camera.autofocus
android.hardware.camera.flash
android.hardware.faketouch
android.hardware.location
android.hardware.location.gps
android.hardware.location.network
android.hardware.microphone
android.hardware.screen.landscape
android.hardware.screen.protrait
android.hardware.sensor.accelerometer
android.hardware.sensor.compass
android.hardware.sensor.light
android.hardware.sensor.proximity
android.hardware.sensor.stepcounter
android.hardware.sensor.stepdetector
android.hardware.telephony
android.hardware.telephony.gsm
android.hardware.touchscreen
android.hardware.touchscreen.multitouch
android.hardware.touchscreen.multitouch.district
android.hardware.touchscreen.multitouch.jazzhand
android.hardware.usb.accessory
android.hardware.wifi
android.hardware.wifi.direct
android.software.app_widgets
android.software.device_admin
android.software.home_screen
android.software.input_methods
android.software.live_wallpaper
android.software.sip
android.software.sip.voip
com.nxp.mifare
mobi.qiss.preload.benq
mobi.qiss.preload.benqhome
Code:
----------------------------------------------------------------------------------
CPU
-----------------------------------------------------------------------------------
SoC Model - Quadcomm Snapdragon 400 (MSM8926)
Core Architecture - 4x ARM Cortex-A7 @ 1190 MHz
Manufacturing Process - 28 nm
Instruction Set - 32-bit ARMv7
CPU Revision - r0p3
CPU Cores - 4
CPU Clock Range - 300 - 1190 MHz
Core 1 Clock - 787 MHz
Core 2 Clock - 787 MHz
Core 3 Clock - 787 MHz
Core 4 Clock - (Sleeping)
CPU Utilization - 74%
Scaling Governor ondemand
CPU ABI - armeabi-v7a
CPU ABI2 - armeabi
AES - Not Supported
NEON - Supported
SHA1 - Not Supported
SHA2 - Not Supported
Code:
------------------------------------------------------------------------------------
DISPLAY
------------------------------------------------------------------------------------
Screen Resolution - 540 x 960
Screen Size - 56 mm x 99 mm
Screen Diagonal - 4.48 inches
Pixel Density - 246 dpi (hdpi)
xdpi / ydpi - 245 / 246 dpi
GPU Vendor - Qualcomm
GPU Renderer - Adreno 305
GPU ALUs - 24
Current GPU Clock - 320 MHz
CPU Clock Range - 200 - 450 MHz
GPU Utilization - 0%
Scaling Governor msm-adreno-tz
Refresh Rate - 62 Hz
Default Orientation - Portrait
OpenGL ES Version - 3.0
GPU Version - OpenGL ES 3.0 [email protected]
[email protected]
LNXBUILD_Nondeterminist
ic_AU+PATCH[ES]_msm8226
_LNX.LA.3.5.1_RB1_CL330
4448_release_ENGG
([email protected])
--------------------------------------------------------------------------------------
GL_AMD_compressed_ATC_texture
GL_AMD_performance_monitor
GL_AMD_program_binary_Z400
GL_EXT_debug_label
GL_EXT_debug_marker
GL_EXT_discard_framebuffer
GL_EXT_robustness
GL_EXT_texture_format_BGRA8888
GL_EXT_texture-type_2_10_10_10_REV
GL_NV_fence
GL_OES_compress_ETC1_RGB8_texture
GL_OES_depth_texture
GL_OES_depth24
GL_OES_EGL_image
GL_OES_EGL_image_external
GL_OES_element_index_uint
GL_OES_fbo_render_mipmap
GL_OES_fragment_precision_high
GL_OES_get_program_binary
GL_OES_packed_depth_stencil
GL_OES_depth_texture_cube_map
GL_OES_rgb8_rgba8
GL_OES_standard_derivatives
GL_OES_texture_3D
GL_OES_texture_float
GL_OES_texture_half_float
GL_OES_texture_half_float_linear
GL_OES_texture_npot
GL_OES_vertex_half_float
GL_OES_vertex_type_10_10_10_2
GL_OES_vertex_array_object
GL_QCOM_alpha_test
GL_QCOM_binning_control
GL_QCOM_driver_control
GL_QCOM_perform_global_mode
GL_QCOM_extended_get
GL_QCOM_extended_get2
GL_QCOM_tiled_rendering
GL_QCOM_writenly_rendering
GL_EXT_sRGB
GL_EXT_sRGB_write_control
GL_EXT_texture_sRGB_decode
GL_EXT_texture_filter_anisotropic
GL_EXT_multisampled_render_to_texture
GL_EXT_color_buffer_float
GL_EXT_color_buffer_half_float
Code:
--------------------------------------------------------------------------------
NETWORK
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
TELEPHONY
--------------------------------------------------------------------------------
Phone Type - GSM
SIM State - Absent
ICC Card - Not Present
---------------------------------------------------------------------------------
WIFI
---------------------------------------------------------------------------------
State - Enabled
SSID - DSC Network
BSSID - d4:6e:0e:ee:2c:6b
Hidden SSID - No
MAC Address - 1c:e1:92:1c:11:ba
Signal Strength - 47 dBm (Excellent)
Link Speed - 65 Mbps
Network ID - 3
Gateway - 192.168.0.1
Netmask - 255.255.255.0
DNS1 - 192.168.0.1
DHCP Lease Duration - 2 hours
Wi-Fi Aware - Not Supported
Wi-Fi Direct - Supported
Code:
--------------------------------------------------------------------------------
BATTERY
--------------------------------------------------------------------------------
Power Source - A/C Charger
Level - 67 %
Status - Charging
Health - Good
Technology - Li-ion
Temperature - 40.6 C
Voltage - 4.044 V
Capacity (Reported by Andorid) - 2520 mAh
Code:
--------------------------------------------------------------------------------
ANDROID
---------------------------------------------------------------------------------
Andriod Version - 4.4.2 (KitKat)
API Level - 19
Rooted Device - YES
Android ID - 63f50428151aae1c
Baseband - MPSS.DI.2.0.1.c1-00223-
M8926DAAAANAZM-1
Build ID - SWEP_GA31I17A_v01.057.03.g_08
Codename - REL
Fingerprint - BenQ/T3_08/T3_17A:4.4.2/
KVT49L/
SWEP_GA3I17A_v01.057.03
.g_08:user/release-keys
ID - KVT49L
Incremental - 376
Java Runtime Version - Android Runtime 0.9
Java VM Version - Dalvik 1.6.0
Java VM Heap Size - 96 MB
Kernel Architecture - armv7I
Kernel Version - 3.4.-g3104c58
([email protected]
)(gcc version 4.7 (GCC))
#1 SMP PREEMPT Thu Mar
12 10:52:17 CST 2015
Tags - release-keys
Type - User
Google Play Services Version - 11.5.09 (034-164803921)
OpenSSL Version - OpenSSL 1.0.1e 11 Feb 2013
ZLib Version - 1.2.8.f-linuxfoundation-
mods-v1
ICU CLDR - 23.0
ICU library Version - 51.1.0.1
ICU Unicode Version - 6.2
Android Language - English (United States)
Configured Time - Malaysia Time (UTC+08:00)
UpTime - 01:16:03
Code:
-----------------------------------------------------------------------------
DEVICES
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Rear Facing Camera
-----------------------------------------------------------------------------
Resolution - 8.0 MP (3264 x 2448)
Video Resolution - 2.1 MP (1920 x 1080)
Focal Length - 3.85 mm
Focus Modes - auto, infinity, macro,
continious-video,
continuous-picture
Video Snapshot - Supported
Video Stabilization - Not Supported
Zoom - Supported
Smooth Zoom - Not Supported
Auto Exposure Locking - Supported
Auto White Balance Locking - Supported
Flash - Supported
-----------------------------------------------------------------------------
Front-Facing Camera
-----------------------------------------------------------------------------
Resolution - 0.3 MP (640 x 480)
Video Resolution - 0.3 MP (640 x 480)
Focal length - 1.21 mm
Focus Modes - Fixed
Video Snapshot - Supported
Video Stabilization - Not Supported
Zoom - Supported
Smooth Zoom - Not Supported
Auto Exposure Locking - No Supported
Auto White Balance Locking - Not Supported
-----------------------------------------------------------------------------
OpenCL Device - QUALCOMM
Adreno(TM)
-----------------------------------------------------------------------------
Device name - QUALCOMM Adreno (TM)
Device Type - GPU
Device Vendor - QUALCOMM
Device Vendor ID - 0xBF4D3C4B
Device Version - OpenCL 1.1 Adreno(TM) 305
Device Profile - Embedded
Driver Version - OpenCL 1.1 QUALCOMM build:
LNXBUILD_Nondeterminist
ic_AU+PATCH[ES]_msm8226
_LNX.LA.3.5.1_RB1_CL330
448_release_ENGG
(CL3304448)
Build Date: 04/21/14 Mon
Local Branch:
Remote Branch: quic/
LNX.LA.3.5.1_RB1.1
Compiler E031.24.00.14
OpenCL C Version - OpenCL C1.1 Adreno(TM) 305
Clock Rate - 400 MHz
Compute Units - 1
Address Space Size - 32-bit
Max 2D Image Size - 4096 x 4096
Max 3D Image Size - 4096 x 4096 x 512
Max Samplers - 16
Max Work-Item Size - 256 x 256 x 256
Max Work Group Size - 256
Max Argument Size - 256 Bytes
Max Constant Buffer Size - 4 KB
Max Constant Arguments - 8
Max Printf Buffer Size - 1 MB
Native ISA Vector Widths - char1, short1, int1, half1, float1
Preferred Native Vector Widths - char1, short1, int1, long1, half1, float1
Profilling Timer Resolution - 1000 ns
OpenCl Library - /system/vendor/lib/libOpenCL.so
Global Memory - 443684 KB
Global Memory Cache - 8 KB (Read/Write, 64 Byte Line)
Local Memory - 8 KB
Max Memory Object Allocation Size - 443684 KB
Memory Base Address Alignment - 512-bit
Min Data Type Alignment - 64 Bytes
Command-Queue Out of Order Execution - Enabled
Command-Queue Profiling - Enabled
Compiler Available - Yes
Error Correction - Not Supported
Images - Supported
Kernel Execution - Supported
Linker Available - Yes
Linker-Endian Device - Yes
Native Kernel Execution - Not Supported
SVM Automics - Not Supported
SVM Coarse Grain Buffer - Not Supported
SVM Fine Grain System - Not Supported
Unified Memory - Yes
OpenCL Extension
cl_img_egl_image
cl_khr_byte_addressable_store
cl_khr_egl_event
cl_khr_fp16
cl_khr_gl_gl_sharing
cl_khr_global_int32_base_atomics
cl_khr_global_int32_extended_atomics
cl_khr_local_int32_base_atomics
cl_khr_local_int32_extended_atomics
cl_qcom_create_buffer_from_image
cl_qcom_ext_host_ptr
cl_qcom_ion_host_ptr
cl_qcom_limited_printf
cl_qcom_extended_images
-----------------------------------------------------------------------
OpenCL Device - QUALCOMM Krait(TM)
-----------------------------------------------------------------------
Device Name - QUALCOMM Krait(TM)
Device Type - CPU
Device Vendor - QUALCOMM
Device Vendor ID - 0xBF4D3C4B
Device Version - OpenCL 1.1. Krait(TM)
Device Profile - Embedded
Driver Version - OpenCl 1.1 QUALCOMM
build:
LNXBUILD_Nondeterminist
ic_AU+PATCH[ES]_msm8226
_LNX.LA.3.5.1_RB1_CL330
4448_release_ENGG
(CL3304448)
Build Date: 04/21/14 Mon
Local Branch:
Remote Branch: quic/
LNX.L.A.3.5.1_RB1.1
Compiler E031.24.00.14
OpenCL C Version - OpenCL C 1.1. Krait(TM)
Compute Units - 1
Address Space Size - 32-bit
Max 2D Image Size - 8192 x 8192
Max 3D Image Size - 2048 x 2048 x 2048
Max Samplers - 16
Max Work-Item Size - 1 x 1 x 1
Max Work-Group Size - 1
Max Argument Size - 256 bytes
Max Constant Buffer Size - 64 KB
Max Constant Buffer Size - 8
Native ISA Vector Widths - char16, short8,int4, long1, half8, float4
Preferred Native Vector Widths - char16, short16, int16, long1, half16,float16
OpenCL Library - /system/vendor/lib/libOpenCL.so
Global Memory - 443684 KB
Global Memory Cache - 1 MB (Read/Write, 64-byte
line)
Local Memory - 32 KB
Man Memory Object Allocation Size - 443684 KB
Memory Base Address Alignment - 1024-bit
Min Data Type Alignment - 128 bytes
Command-Queue Out of Order Execution - Enabled
Command-Queue Profiling - Enabled
Compiler Available - Yes
Error Correction - Not Supported
Images - Supported
Kernel Execution - Supported
Linker Available - Yes
Little-Edndian Device - Yes
Native Kernel Execution - Supported
SVM Atomics - Not Supported
SVM Coarse Grain Buffer - Not Supported
SVM Fine Grain Buffer - Not Supported
SVM Fine Grain System - Not Supported
United Memory - Yes
OpenCL Extensions
cl_khr_global_int32_base_atomics
cl_khr_global_int32_extended_atomics
cl_khr_local_int32_base_atomics
cl_khr_local_extended_atomics
cl_khr_byte_addressable_store
cles_khr_int64
cl_khr_fp16
No USB devices found.
No CUDA devices found.
No Vulkan devices found.
No PCI devices found.
Code:
----------------------------------------------------------------------------
THERMAL
----------------------------------------------------------------------------
tsens_tz_sensor0 - 42.0 C
tsens_tz_sensor1 - 43.0 C
tsens_tz_sensor2 - 42.0 C
tsens_tz_sensor3 - 42.0 C
tsens_tz_sensor4 - 41.0 C
tsens_tz_sensor5 - 43.0 C
ppm8226_tz - 38.7 C
pa_therm0 - 25.0 C
pa_therm1 - 25.0 C
Battery - 31.6 C
Ok, I did a bit of a mess up with the phone - Sorry! I tried removing the bloatware (BenQ software) using SuperUser app that I had installed previously after the KingoRoot and now the phone has lost it's systemUi
I see no icons on my screen and it takes very long to boot up the phone (heck most times it just gets stuck on the loading screen). I tried to do a master reset by pressing the power button + Volume down and cleaning all user data but everything I try seems to be in vain. The data was reset as I had to enter my google account and all flagship apps lost its updates but even so the result (i.e. no SystemUi) remains.
There seem to be no guides on this phone Model (BenQ - T3) at all on XDA forum or the internet for that matter.
Any suggestions on what can I do next ??
P.S. The phone has no SD card and this is just a Testing phone so I can play around with it as much as I can. Any help on the matter would be much appreciated.
Writing this after I've successfully troubleshooted and resurrected the phone to a much better state. Apparently in my haste to try out things I accidently damaged the launcher for my phone which totally messed up the User Interface.
Nearly three months of searching and reading various online material for my phone (still cannot find stock ROM) without avail I came back on XDA and posted this entire problem from scratch in the Noob Friendly Questions Thread.
Luckily a couple of blokes helped me out on the matter and I have managed to bring my phone back to a working state (typing this post from the XDA app itself on my BenQ)
If you want the reference to the conversation please visit the thread '[HELP THREAD] Ask ANY Question. by immortalneo' and start reading my post from page 4075 onwards.
Tools that I used to rectify this:
1) Adb and Fastboot drivers installed in the PC
2) Rooted BenQ T3 (if you haven't Rooted yet then just download KingoRoot, enable USB debugging and root the phone - Do a Google search and you'll find it pretty easy)
3) KitKat launcher apk app
At first I went into recovery mode and wiped clean the data and cache, this helped me boot into the phone after which I connected it to my PC (USB debugging on) and ran the following command:
Code:
Adb reboot bootloader
The phone then went into Fastboot mode and I had to further write this:
Code:
Fastboot oem unlock
The above command unlocked the bootloader after which I once again booted into the phone recovery and wiped clean the data and cache. When the boot up process was done I had to connect again to the PC (USB debugging on) and install the launcher by writing:
Code:
Adb install [launcher_name]
This repaired my UI and all the icons and screen windows came back to normal, my problem of being stuck at a normal boot up process also resolved once I reinstalled the launcher correctly!
Once the GUI came back I reentered my Google credentials, carefully uninstalled all bloat ware and unnecessary apps via Kingo Super user app and updated all the ones that I use on a daily basis.
I now will look to find TWRP or any custom recovery for my phone and Custom ROMs as well. If anyone can point me to the right direction then that would be highly appreciated !!!